L2 Vpn Common Configuration Issues

The Routing and Remote Gain access to snap-in lives within the Microsoft Management Console, called the MMC. There are several ways to access the MMC. You can choose the console from the Start menu's Programs choices, within the Administrative Tools folder within Windows server's Control Panel or by typing mmc at a command prompt.

As Tech, Republic's Brandon Vigliarolo demonstrates within his video at the start of this post, the Solutions console displays the status of the Routing and Remote Access entry. From within the Providers console and with the Routing and Remote Gain access to entry highlighted, you can click Start the Service or right-click the entry and select Restart.

Often the VPN client and VPN server are set to utilizing different authentication approaches. Confirm whether an authentication error is the problem by opening the server console. Another technique of accessing the MMC is to type Control+R to open a command timely in which you can type mmc and hit Get in or click OK.

If the entry isn't present, click File, select Add/Remove Snap-in, pick the Routing and Remote Gain access to alternative from the choices and click Add, then OK. With the Routing and Remote Gain access to snap-in added, right-click on the VPN server and click Characteristics. Then, evaluate the Security tab to validate the authentication approach.

Troubleshooting And Known Issues

Guarantee the VPN client is set to the authentication approach specified within the Security tab. Usually the items simply evaluated are accountable for most VPN connection refusal errors.

Each Web-based VPN connection generally utilizes 2 different IP addresses for the VPN client computer. This is the IP address that's utilized to develop the preliminary TCP/IP connection to the VPN server over the Web.

This IP address usually has the same subnet as the local network and thus enables the customer to interact with the local network. When you established the VPN server, you must configure a DHCP server to designate addresses to customers, or you can create a bank of IP addresses to assign to clients directly from the VPN server.

If this alternative is chosen and the efficient remote access policy is set to permit remote access, the user will have the ability to connect to the VPN. I have actually been unable to re-create the scenario personally, I have actually heard reports that a bug exists in older Windows servers that can cause the connection to be accepted even if the effective remote gain access to policy is set to deny a user's connection.

Vpn Errors - Common Codes And Messages

Another typical VPN issue is that a connection is successfully established however the remote user is not able to access the network beyond the VPN server. By far, the most common cause of this problem is that permission hasn't been given for the user to access the entire network. To enable a user to access the whole network, go to the Routing and Remote Access console and right-click on the VPN server that's having the problem.

At the top of the IP tab is an Enable IP Routing check box. If this check box is made it possible for, VPN users will have the ability to access the remainder of the network, assuming network firewall softwares and security-as-a-service settings allow. If the checkbox is not selected, these users will be able to access only the VPN server, however nothing beyond.

For instance, if a user is dialing straight into the VPN server, it's normally best to configure a fixed route in between the customer and the server. You can configure a fixed route by going to the Dial In tab of the user's homes sheet in Active Directory Users and Computers and selecting the Apply A Static Route check box.

Click the Include Route button and after that enter the location IP address and network mask in the area provided. The metric should be left at 1. If you're utilizing a DHCP server to designate IP addresses to customers, there are a number of other issues that could trigger users not to be able to go beyond the VPN server.

Secure Ssl Vpn - Troubleshooting Guide

If the DHCP server assigns the user an IP address that is already in usage elsewhere on the network, Windows will discover the conflict and avoid the user from accessing the remainder of the network. Another typical problem is the user not receiving an address at all. The majority of the time, if the DHCP server can't assign the user an IP address, the connection will not make it this far.

254.x. x range. If the customer is assigned an address in a range that's not present within the system's routing tables, the user will be not able to navigate the network beyond the VPN server. Other issues can contribute to this issue, too. Ensure the resources the user is trying to access are in fact on the network to which the user is connecting.

A VPN connection to the other subnet might, in fact, be required. A firewall program or security as a service solution might likewise be to blame, so don't forget to examine those solutions' settings, if such components are present in between the VPN server and the resources the user looks for to reach.

The first possibility is that one or more of the routers included is carrying out IP package filtering. I suggest inspecting the client, the server and any makers in between for IP package filters.