Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!
Cannot ping external IP/web address from LAN, yet can access site fine
Embarking on a trip down the rabbit hole that started with Wordpress but is ending up with crazy DNS issues - hoping someone can help! My LAN network is set up with a Windows 2003 box which hosts DNS, a 10.5.6 Mac server which hosts our website, DHCP, and other various things, all behind a Netgear FVX538 firewall box.
The Mac server hosts our Wordpress website - recently I had been trying to start hosting a podcast for the Wordpress blog. Wordpress normally supports auto enclosures of media files, but that wasn't working, which I thought was strange. After much searching and testing, I realized that something was amiss with DNS that was most likely causing the issue.
I can ACCESS my website from the LAN (both on the server it's being hosted from and other computers in the LAN) but PINGING either the external IP or the domain name doesn't work. It pings for one entry, spits back the IP address, then stops with no other error message or notification of any kind. I can ping other external sites just fine, and can ping internal IP addresses just fine as well.
I'm not sure if this is a DNS problem, although it seems safe to say that it is. And because I've noticed no other issues, I'm not really sure where to begin in figure out what the problem is. It seems that there's some issue going on with internal DNS, so if anyone has advice of what I should look for, please let me know!
The Mac server hosts our Wordpress website - recently I had been trying to start hosting a podcast for the Wordpress blog. Wordpress normally supports auto enclosures of media files, but that wasn't working, which I thought was strange. After much searching and testing, I realized that something was amiss with DNS that was most likely causing the issue.
I can ACCESS my website from the LAN (both on the server it's being hosted from and other computers in the LAN) but PINGING either the external IP or the domain name doesn't work. It pings for one entry, spits back the IP address, then stops with no other error message or notification of any kind. I can ping other external sites just fine, and can ping internal IP addresses just fine as well.
I'm not sure if this is a DNS problem, although it seems safe to say that it is. And because I've noticed no other issues, I'm not really sure where to begin in figure out what the problem is. It seems that there's some issue going on with internal DNS, so if anyone has advice of what I should look for, please let me know!
Asked:
3-
3
1 Solution
That diagram is basically what we have. I have the router/firewall box set up with the ISPs DNS server, then an internal DNS server hosted on the Windows 2003 box. And yes, my firewall is using NAT to get outside the server.
Okay, so clients inside won't be able to access on the public IP because it just gets horribly confused trying to route the requests.
The traditional answer is to create a zone on the internal DNS server that will provide clients inside the network with a private IP address for the domain name in question. This only works if all your internal clients use that internal DNS server.
I've blogged about this in the past, so I hope you'll forgive me pasting the link rather than rewriting my instructions for it :)
http://www.highorbit.co.uk/?p=459
Chris
I will try those instructions - thanks - but I may have figured out something else. Tried switching out the Netgear firewall to our old Symantex VPN/100 and lo and behold, everything started working again - enclosures, pinging, the whole nine yards. So I guess when I was setting up the Netgear I missed a setting, any thoughts as to what that might be, or should I do your DNS suggestions first (with the Netgear) and see if that works first?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
If you're getting the correct IP Address back in response to a request for a name then DNS is done and out of the picture.
However, your server is hosted inside your network in this scenario?
That is you have something like this:
Internet ----- Router ----- Switch ----- Clients
|
Server
And you use NAT to get a public IP address from outside your network to your Server?
If so, then no, clients will not be able to access the server using the public IP (and therefore also won't be able to using the public name which presumably resolves to that IP). If that is true, do you have a DNS server inside your network as well?
Chris