Question : Problem: Essential to be "multihomed"?

Hi all,

I wanted to know if it was essential to have a multihomed VPN server in order for EVERYTHING to work successfully?

I have managed to get my VPN set up, authenticating is fine, as is browsing network resources on the VPN server (still need to check the machines behind the VPN). I can ping the VPN server happily too.

As of now my server has just one NIC with a public IP 81.x.x.x (255.255.255.248), I have also applied a private IP 192.168.0.20 (255.255.255.0) to the SAME NIC in advanced properties. Should these be separated to differing NIC's?

The VPN server is dishing out IP's to VPN clients in the range 192.168.0.21-192.168.0.25 from a pool.

At this moment I can't browse the internet while connected to the VPN and wondered if the above question was the issue? Do I need to add a route to the RRAS server so it knows where to point the traffic should I require internet access while connected to the VPN? If so, what do I add and where?

Answer : Problem: Essential to be "multihomed"?

All you have to do to allow Internet browsing while connected to the VPN is uncheck the "Use Default Gateway on Remote Network" option in your VPN connection on the client.  You'll still be able to access your private network, but your default gateway will now point to the Internet.

If you have other IP networks that the client needs to route to in your private network, just add the routes to your DHCP scope and those'll work too.

Hope this helps.