If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

SonicWALL TZ 170

Need some help from the greater experts on what I'm doing wrong here. Here's the scenario:

Office LAN with two gateways (one DSL, the other T1), each protected by an older SonicWALL hardware firewall.

Just purchased a new SonicWALL TZ 170 to review for possibly replacing the old SonicWALL units.

So I have a test box set up in my office that's connected to our LAN. I plugged the SonicWALL into a switch here in my office that's connected to the LAN and placed the test box behind it.

The SonicWALL has successfully receive both a WAN and LAN IP, so it looks like all the connections are working well.

Configuration isn't set yet to block any traffic.

But here's where it gets wierd:

The box behind the TZ 170 cannot ping any other box on the network. Likewise, no computers on the LAN can ping the test box behind the firewall. In fact, they can't even ping the firewall itself.

The firewall, though it shows itself as being connected to the WAN, cannot connect to the Internet to download updates and whatnot. I get the message "DNS lookup failed, please check your DNS server settings".

So, two questions:

(1) What could I be doing wrong? It sees the LAN, sees the WAN, but no connection to the outside world or any other machines?

(2) Would this problem disappear once I connect it directly to the router? Will that make things easier?

1. make sure that your new firewall doesn't try to act as any kind of server... and is ready to recieve dynamic IP

2. make sure that the ADC/PDC gives correct information via DHCP... you should have it set up as PDC and make all DNS requests go throught it (after that... you can resolve them from you ISP router or any static IP you've got)

edit: win2k servers are picky bastards about controlling everything... the AD depends on it

3. restart shutdown your DHCP services and make sure that the IP pool is big enough ... ****... enlarge it even more

i think that (if the switch is ok) this is a simple matter of chaining the devices properly. hope this helps ...let us know what it was

Attaching it to the router fixed the problem. Now all boxes on the LAN can to talk to each other, the WAN, and the firewall with no problems.

But now, I have a new problem!

Ever since the new firewall was put in, our DSL has slowed down. It seems something's clogging at the firewall. So I tried to access the DSL router's web panel, and instead it timed out and never connected.

Interesting.

So after some detective work, I decided to plug a laptop directly into the router, thus bypassing the firewall. Entered the IP into my web browser again, and sure enough, it connected and logged me right on.

So evidently the firewall is blocking web access from any machine within the LAN to the router.