Resolving WIN2003 VPN server connections cannot access the extranet

Companies need to use a VPN server to meet the needs of the field Project department to connect to the company, so I used the WIN2003 server to do VPN services (no time to study 2008,2003 more familiar).

According to the previous Setup method, the VPN service was successfully set up, but when the field Project department was connected to the company, it was found that the extranet could not be connected, which caused inconvenience to some machines which needed to connect both VPN and extranet.

According to the network above method, is the VPN connection ' in the remote network using the default gateway ' before the hook off can be, but for ordinary users, set up more difficult, after all, many people are not professional it, even if the notice may not have the actual effect.

So how can you complete the connection without making any additional settings (just to set up how to connect)?

When checking the router settings, suddenly saw a name-nat, since the router itself has this, then as the server WIN2003 should have this, after all, the router itself is also a computer without a monitor but with the operating system of the host. One of the applications of NAT technology is a one-to-many service.

Then reset the WIN2003, in the customization in addition to the "VPN service" to select the ' nat/Firewall ' also selected.

But after the service restarts, the ' internal ' and ' local connection ' are added to the ' nat/Basic Firewall '. Then open the ' Local Area Connection ' property, on the ' nat/Basic Firewall ' tab, connect the ' public interface to the Internet ' and select ' Enable NAT on this interface '. Restart the service.