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 the following setup:


Server A has two NIC's - one connected to each switch. Server B just has a NIC connected to the internal switch.

Server A and Server B can both ping each other. But when I open a web browser on Server B to access the internet, or to ping an external IP address (e.g.,, the packets aren't routed through Server A.

Both machines run Windows Server 2008. I tried Routing and Remote Access using a NAT configuration, selecting the external NIC as the "internet" connection, but Server B is still unable to ping any external IP addresses.

What are my options for granting server B access to the internet via Server A?

Edit: IPFire turned out to be a great solution.

share|improve this question
My setup seems similar to this, however, RRAS does not seem to forward any requests:… – Paul Stovell Jul 8 '11 at 15:11
up vote 2 down vote accepted

This appears to be a terrible architecture overall but if you insist on doing this you just need to install some form of proxy on server A then point to it from your applications on server B - that or design it right of course.

share|improve this answer
Thanks for your constructive feedback. Can you explain what "doing it right" might look like? – Paul Stovell Jul 8 '11 at 15:21
Well, using a router and/or firewall to do routing and/or firewalling. – Chopper3 Jul 8 '11 at 15:23
The switches are vSwitches in an ESXi box. The external switch is mapped to the physical network card, the internal switch has no physical NIC. So server A will play the part of a router and/or firewall. Windows Server has a firewall, and has a role called "routing and remote access", so it seemed like a good enough fit for routing and/or firewalling. But I'm open to alternatives. – Paul Stovell Jul 8 '11 at 15:28
So why isn't Server B just connected to the external switch too then? I'm not sure the Windows Firewall and RRAS is what you really need, I know there's a lot of guys on here that use the pfsense vm appliance. It's a router and firewall that you'd put between the outside world and your servers, really reckon it's worth a look. – Chopper3 Jul 8 '11 at 15:38
Thanks to your suggestions I looked at a few Linux firewall/router distributions. I ended up trying IPFire, and within 20 minutes I had working what I spent a day trying to make work with Windows Server. Props! – Paul Stovell Jul 9 '11 at 14:36

Not very highend but ICS + Network Bridge might work?

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.