Some Appropriate Solution for troubleshooting The VPNs

Hi guys. here I`ve provided some usefull hints for those administrators who works with Virtual Private Network

verify that on the VPN server enough port have been configured in Port node for the relevant VPN typ needed (pptp-L2tp) and that not all available ports re currently being used

verify that the remote access server option is enabled on the server propertise in the .

General tab in the Routing And Remote Access console

. Verify that the VPN connection has the appropriate permissions through dial-in ..

properties of the user account and remote access policies

. Verify that the VPN client, the remote access server, and the remote access policy ..

are configured to use at least one common authentication protocol

. Verify that the VPN client, the remote access server, and the remote access policy ..

are configured to use at least one common encryption strength

. Verify that the remote access server (or RADIUS server) computer is a member of ..

the RAS And IAS Servers security group in the local domain

. Verify that the settings of the remote access policy profile are not in conflict with ..

properties of the remote access server

. Verify that, if MS-CHAP v1 is being used as the authentication protocol, the user ..

password does not exceed 14 characters

Troubleshooting Router-to-Router VPNs

Use the following checklist to troubleshoot router-to-router VPNs

. Verify that at each end of the VPN connection, both the Router option and the LAN .

And Demand-Dial Routing option are selected on the General tab of server properties

in the Routing And Remote Access console

. Verify that on each remote access server, the Enable IP Routing option is .

on the IP tab of server properties in the Routing And Remote Access console

. Verify that on each remote access server, enough ports have been configured in .).

the Ports node for the relevant VPN type needed (PPTP or L2TP

. Verify that, for each demand-dial interface created for the VPN connection,

selected the option in the Demand-Dial Interface Wizard to route IP traffic over

that demand-dial interface

. Verify that you have created static routes on each remote access server so that traffic ..

destined for the opposite network is associated with the appropriate VPN interface

. Verify that on each remote access server, the dial-out credentials of the locally configured demand-dial interface match the name of the remote answering interface

and also match a user account name and password in the remote domai

. Verify that each demand-dial (VPN) interface, answering remote access server, and.

answering remote access policy are configured to use at least one common

authentication protocol and one common encryption strength

. Verify that the remote access connection has the appropriate permissions

dial-in properties of the user account (corresponding to the name of the demanddial

interface) and through remote access policies

. Verify that at each end of the VPN connection, the remote access server (

RADIUS server) computer is a member of the RAS And IAS Servers security group

in the local domain

. Verify that on each remote access server, the settings of the remote access policy

profile are not in conflict with properties of the remote access server

Configuring VPN Types

. . . . . . . :