Route VPN Clients Through NAT
Most of us use the MMC to administer Windows 2000 RRAS. But what happens when you need to route an incoming VPN client back to the net and you’re using NAT with private, non-routable addresses? Users of the company’s VPN used complain about losing internet access while using VPN. The usual way to avoid this is to have the user go to the advanced TCP/IP properties of the VPN connection and uncheck the box that says Use default gateway on remote network.
Unfortunately, not all users can follow instructions, or are willing to do so. Adding the internal interface to NAT puts an end to that issue (but does raise security concerns, so that has to be taken into consideration) and that’s where the NETSHELL command can help.
If you take a look of the interfaces available under the IP routing section of the RRAS console on a Windows 2000 server, you’ll generally see the NIC’s listed, the loopback interface, and a card called the internal interface. That internal connection is the virtual interface that VPN clients connect to, and you’ll notice that you can’t add it to the NAT protocol via the GUI. Time for the command line.
Open the command prompt, type NETSH to open the NETSHELL program. Now type
Read the Best Personal and Business Tech without Ads
Staying updated on what is happening in the technology sector is important to your career and your personal life but ads can make reading news, distracting. With Thurrott Premium, you can enjoy the best coverage in tech without the annoying ads.
routing ip nat add interface internal private
Done. You’ll now notice that the internal interface is listed under the NAT protocol. At this point, VPN clients can now route to the net as well as your LAN. You can configure all RRAS functions using the netsh command, but personally I only use it for this purpose.
With Windows Server 2003, Microsoft has added the ability to add the internal interface to the NAT protocol via the GUI.