Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm having a really bizarre problem while using No-IP. I can access the server fine from clients not on the local network and local and remote clients can ping the server just fine. I get the same results using our No-IP name as well as the current IP address directly.

This has completely baffled me - any help would be greatly appreciated.

share|improve this question
add comment

1 Answer

up vote 3 down vote accepted

You're trying to access a server on your LAN by using a public IP address (or a name that resolves to a public IP address) that's assigned to your LAN's edge firewall. That fact that it's working from outside the firewall, but not inside, makes me think that your firewall's NAT implementation is probably to blame.

When that doesn't work, the usual cause is that the edge firewall doesn't support "hairpin NAT" or "hairpinning". This, basically, means that the edge firewall isn't capable of receiving a request from its LAN port bound for the IP address assigned to the WAN port and "turning it back around" to the LAN. Many NAT devices do support this, but many also don't. What kind of NAT / edge firewall device are you using?

If you determine that your edge firewall doesn't support hairpin NAT a second-best choice is to create a DNS zone on your LAN DNS server corresponding to the public name of the server, but resolving the server to a LAN IP address. Clients on the LAN will resolve the server's public name as a LAN IP address (since they're using the LAN DNS server), but Internet clients (who don't have access to your LAN DNS server or, indeed, even know about it) will continue to resolve the server's public name to the public IP address.

share|improve this answer
    
Thanks a lot - it's a [very] small office setup here, and we just have a home-style DSL modem at the edge, which fortunately has an option to add DNS entries. –  Alex S Aug 5 '10 at 23:45
    
@Shadow: If you've got a local server machine (or a PC that is powered-on in a stable and predicable manner) you might go the route of running a local DNS server (and possibly DHCP server if your edge firewall is doing DHCP and won't support passing out an DNS server IP address other than the ISP's DNS servers). There are several no-cost and open source DHCP and DNS server offerings that you could run (on Windows, even!). I suppose you could modify the HOSTS file on each PC, too, but I'd never actually recommend that... –  Evan Anderson Aug 6 '10 at 0:06
    
this is a known issue with most of the Cisco firewalls I've dealt with (PIX & ASA). –  Greeblesnort Aug 8 '10 at 5:02
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.