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

There are two pages in D-Link router to setup access to internal network from outside: Port Forwarding and Virtual Server. Both allows to map external port to internal one, except latter page also allows to change port.

I found that if I have service in my internal network and set it up in any of two pages, I can easily access it from outside.

But if it try to access my internal service from inside by external IP address, I succeed only if service is setup by Virtual Server page.


Is this D-Link bug or that behavior should occur because of Internet protocols? In latter case please provide some explanations.

share|improve this question
up vote 2 down vote accepted

You need NAT loopback, also known as NAT reflection, NAT hairpinning, and possibly a few other names.

There is a good explaination on wikipedia of what NAT lookback does and why it's needed in your case.

Basically without it, your router isn't expecting requests destined for your public IP to come from the LAN, and the address translation doesn't work properly.

This post confirms that D-link routers only setup NAT loopback on the virtual server entries, not the port forwarding entries.

share|improve this answer

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.