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 trying to set up Routing and Remote Access on Windows Server 2008 R2, I have a network connection that I want to share the internet from to another private network.

The server has two NICs which are configured as follows:

External NIC (Dynamically assigned by ISP)
Internal NIC

I have set the external NIC to be the public interface and enabled NAT on it in the RRAS MMC and set the internal NIC to be a private interface. I have also set up the DNS forwarding or whatever it is in the NAT section.

From a client (IP: I can ping the server and access files on it, when I try to browse the web with the default gateway set to the internal NIC ip I end up getting a 404 page which is returned from the ISPs default gateway. I'm guessing it's something to do with the double NAT possibly. Pinging the ISPs default gateway from the private network recieves replies, as does pinging the external nic ip from the private network.

I've disabled and reconfigured RRAS multiple times and that doesn't seem to have made a difference, so can anyone tell me what I'm doing wrong?


UPDATE: Apparently I was wrong earlier when I said I couldn't ping the ISPs gateway, I can. I can also ping the external nic ip from a client on the private network. Heres a copy of the NAT mapping table which suggests its talking to some servers at Apple I believe. http://i.imgur.com/jfZ3f.png

share|improve this question
Can the machine that can't reach the Internet ping –  David Schwartz Sep 9 '12 at 2:12
Yes, It can ping, it can also ping the ISP gateway at which I made the mistake of saying earlier it couldn't. –  Jack Sep 9 '12 at 15:08

Your Answer


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

Browse other questions tagged or ask your own question.