Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a router opened up to allow Remote Desktop to one of the machines. It works if I try to connect from outside the network. If I however am inside the LAN and try to connect using the WAN IP address it doesn't work. Why?

share|improve this question
up vote 5 down vote accepted

You need to have NAT reflection enabled if your router/firewall supports it. This allows you to access internal servers by public IP. Otherwise, you need to use private IP addresses when accessing internal servers.

share|improve this answer
Why won't it let me access internal machines via the public IP? Why doesn't it just go out to the internet and back in again? – CJ7 Feb 11 '12 at 13:57
@Craig.. the reason for the behavior you see is exactly as Khaled mentions. Most inexpensive routers for not provide this capacity. Some do but don't enable it by default. – Tim Brigham Feb 11 '12 at 14:04
@CraigJ: Public IPs are directed to the default gateway which is your router. Then, the router will forward them to the outside if not configured to route them back in. – Khaled Feb 11 '12 at 14:46

Your Answer


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.