VPN Common error Guide
Below you can find the most common errors using the VPN connection provided by Rego Consulting
1. The VPN process failed to start. The port is already in use by another process
Description: Another VPN/Application/Process is using the port the VPN connection needs.
Troubleshooting Steps:
***Note that you should not be connected to a Corporate VPN account while performing these tests***
Test 1: Restart
Restart the computer
Keeping all other programs closed, launch the AWS VPN Client
Attempt to Connect to your Profile
Pass: This means another VPN/Application/Process you started previously used this port. You will need to identify what that is and make sure only one is running at a time. Use the method in Test 3 as a way to identify.
Test 2: Different Network
Using a separate network than your Office network (such as a home network), launch the AWS VPN Client
Configure the Profile if you haven’t already
Press connect
Pass: The Network you were on previously prevented you from connecting. Work with your Helpdesk to resolve the connection issue.
Test 3: Identify Port Usage
If the previous tests fail, this will help identify the issue. Work with your Helpdesk if you are unable to run the command yourself.
Open CMD as an Administrator
Type this command: netstat -bano
Look for a Local Address ending in :8096 or :35001.
Note the Name of the Protocol (the name is in brackets above the line with the Port Number) and the PID.
Open Task Manger
Go to the Details tab
Find the PID that matches the PID from step 4. That is the process using the Port in question.
Work with your helpdesk to see if this is a necessary process and next steps.
Test 4: Alternate VPN Client
Use this test if you need to configure proxy settings in order to connect to the VPN.
Navigate to the OpenVPN Connect website (here) and download the client
Install the OpenVPN Connect Client. On Driver Selection, make sure to pick TAP
Open OpenVPN Connect and click through the pop ups for first installation
Once on the Import Profile screen, click File
Browse for the .ovpn file used for the AWS VPN client
Name the Profile appropriately, then click Add
If you need to add a proxy, click the Edit icon next to the Profile.
Click Add Proxy and configure appropriately
Click On next to the new Profile
Work with your Helpdesk if you need assistance installing the software
2. VPN connection process quits unexpectedly
Description: While connecting to the VPN, the client quits unexpectedly.
Troubleshooting:
This indicates that the TAP Driver is missing. To fix, follow the steps below:
Navigate to the OpenVPN Connect website (here) and download the client
Install the OpenVPN Connect Client. On Driver Selection, make sure to pick TAP
Once the installation is complete, open AWS VPN Client.
Attempt to connect to and verify that the VPN doesn’t close.
3. AWS VPN Client doesn’t launch
Description: A more recent version of the .NET Framework (4.7.2 or later) is needed. This error is generally on Windows 7 machines
Troubleshooting:
This indicates that the .NET Framework is not up to date. To fix, follow the steps below:
Open the AWS VPN Client installer
Select Repair
Once the Repair is finished, attempt to open the VPN Client.
If it fails, uninstall the AWS VPN Client
Restart your machine
Open the AWS VPN Client installer and install the client again.
Open the AWS VPN Client to verify you can open and use it.