- common problems virtual private network
Virtual Private network or VPN is an effective way to achieve secure network connections. Although professional organizations, offices and other institutions normally use virtual private network services, they can also be accessed via the home network. VPNs have grown in popularity and are seen as an essential element of any network system. Therefore, users should be aware of problems that are usually associated with VPN
We discuss the common problems associated with VPN and their troubleshooting tips below.
Instead of accepting, the connection is rejected
- It must be checked using the Ping command, if the IP address of the VPN server accessible or not. ICMP messages either to or from the VPN server fail to get delivered in packet filtering right and accordingly can result Ping to stop working.
- remote access and routing services on the VPN server must be verified.
- If the VPN connections used for remote access, you should check that the VPN server can allow remote access. It should also verify that the VPN server is able to support the request of a routing line in case of router connection to the router.
- For inbound remote access, L2TP and PPTP ports to be enabled in the remote access connections. For inbound and outbound demand access connections, L2TP and PPTP ports must be enabled on the router to router connections.
- At least one similar authentication method should be used by the VPN server, VPN client with a single remote access policy.
- at least one similar method of encryption should be used by the VPN server, VPN client with a remote access policy.
- should verify that the LAN used by the VPN client protocols should enable remote access on the VPN server for remote access connections.
- should be checked if all L2TP or PPTP VPN ports on the server have been used or not.
- It must be verified that the VPN client credentials as a domain name, password and username are correct and if the VPN server can validate.
to be rejected, the connection is accepted
should check that the connection settings should not be allowed by access policy from a distance. The remote access permission by connection attempt parameters should be rejected by the remote access user account permission.
can not reach places that are far from the VPN server
- If VPN for remote access, it should check if the protocol can enable routing. Also the option "Entire Network" must be selected so that the LAN protocols can be used by the VPN clients.
- If VPN for remote access, the VPN server's IP address pools should be verified.
- in case of router connection to VPN router supporting the exchange of traffic in both directions, two-way routes should be checked.
- There should not be any / IP TCP packet filters in the profile properties of the remote access policy that is used by VPN connection on the VPN server, as these can prevent receiving / sending of TCP / IP traffic.
- There should not be any filters TCP / IP packet numbering in the application interfaces that can prevent receiving / sending traffic.
0 Komentar