[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 714
  • Last Modified:

unable to get to the internet behind tz 100

unable to get out from behind the firewall TZ 100, can ping www.google.com for diagnostics, and site to site vpn works
0
dwaynem2345
Asked:
dwaynem2345
  • 6
  • 3
  • 2
  • +2
1 Solution
 
jimponderCommented:
On your domain controller: ipconfig /flushdns.
Do you have a rule in place that allow lan to wan traffic?  Is it enabled?
0
 
dwaynem2345Author Commented:
lan to wan any
0
 
dwaynem2345Author Commented:
it is a small office home office and no domain controller
0
The eGuide to Automating Firewall Change Control

Today‚Äôs IT environment is constantly changing, which affects security policies and firewall rules. Discover tips to help you embrace this change through process improvement & identify areas where automation & actionable intelligence can enhance both security and business agility.

 
Randy DownsOWNERCommented:
Do you mean no access to the web? :80 ?
0
 
dwaynem2345Author Commented:
correct...I can through diagnostics, just cant from any machine i hook up to it....I can even get into the firewall remotely, very odd.
0
 
avilovCommented:
*I am not familiar with that firewall*

in general you need two rules: incoming and outgoing. "lan to wan any" is one, what is the other?

something like "wan to lan ..."
0
 
jimponderCommented:
how about wan to lan any?  Put that in place and verify the firewall is the problem.  
0
 
dwaynem2345Author Commented:
i did that...and still no go....but like i said, site to site vpn works just fine.
0
 
avilovCommented:
what is your routing table looks like on that firewall?

do you have a router in front of firewall? does it have correct default route?
0
 
Randy DownsOWNERCommented:
0
 
digitapCommented:
site to site vpn is going to use IP not DNS so we at least now that your internet is up. the fact that you can ping www.google.com says DNS is resolving properly.

go to system > diagnostics of your sonicwall and select Ping from the drop down. choose 4.2.2.2 first. if that pings properly, ping www.google.com. if it pings successfully, then ping www.ibm.com or whatever. if it pings successfully, then your sonicwall is resolving DNS properly.

if you aren't able to ping those devices properly from a workstation then you've got an internal DNS resolution issue. how are your internal hosts resolving DNS? is it from a central server? if you replace the DNS server IP of one of your workstations with 4.2.2.2, is it able to get to internet hosts by name?

also, when you added the WAN > LAN Any on your firewall, you opened up your firewall to the internet. you want to delete that firewall rule or change it immediately!
0
 
dwaynem2345Author Commented:
i did disable that rule already, i can get to the internet from the firewall, just nothing that is directly hooked  up to it.
0
 
digitapCommented:
ok...change the DNS server IP of one of your workstations to use 4.2.2.2 and try to get to the internet. can you ping 4.2.2.2 from one of your workstations behind the tz100?
0
 
dwaynem2345Author Commented:
i cannot ping that
0
 
digitapCommented:
ok...it seems like a routing issue. compare the IP address of the LAN interface of your tz100 to the gateway IP of the workstation that is unable to ping 4.2.2.2? is there a difference? what's handling IP assignments, an internal Windows DHCP server or the sonicwall?
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 6
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now