Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 Windows 2008 R2 server with a single NIC which is set up as a VPN server. I want my VPN users to be able to route all their internet traffic through this server once they have connected. I tried adding a local loopback adapter to compensate for the other NIC (adding the VPN's IP to the loopback interface) but that trick didn't work since I'm more of a developer than a sysadmin.

Any ideas how this can be achieved?

share|improve this question
Somebody else might be able to chime in here but doesn't Routing and Remote Access VPN default to a bridged VPN configuration? i.e. a virtual interface is assigned on the VPN server and this is also the gateway of the VPN clients, and all traffic is bridged onto the LAN this way? – gravyface Aug 27 '12 at 22:06
The routing seems to work within the local network. For example, once I'm connected to the VPN, I can ping other interfaces of the server that are using different subnets than the one used by the VPN. I don't know if it's worth noting that the single NIC is configured with four other static/public IP address. It's confusing. – Zishan Aug 27 '12 at 22:19
Umm, yeah, that sounds... odd. – gravyface Aug 27 '12 at 23:22
Odd, nothing. That sounds downright cruel. I wouldn't know where to begin, except by adding another NIC, or a proper piece of network gear... or pouring myself a stiff drink. – HopelessN00b Aug 28 '12 at 14:15
Or perhaps a virtual/emulated network interface could do the trick? (other than MS local loopback adapter). – Zishan Aug 28 '12 at 14:19

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.