Unable to connect: Client services errors

Important: This troubleshooting guide is for Windows users. Log file or diagnostics messages for other platforms can be found here.

If you see any of the four following error messages in your connection log:

Error 1:
TCP: connect to 78.129.233.74:10086 failed, will try again in 5 seconds: Network is unreachable (WSAENETUNREACH)
SIGTERM[soft,init_instance] received, process exiting

Error 2:
NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address Local Area Connection 2 dhcp
Failed to configure the DHCP service. The interface may be disconnected.
The system cannot find the file specified.
ERROR: netsh command failed: returned error code 1
NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address Local Area Connection 2 dhcp
Failed to configure the DHCP service. The interface may be disconnected.
The system cannot find the file specified.

Error 3:
Route: Waiting for TUN/TAP interface to come up...
TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Route: Waiting for TUN/TAP interface to come up...
TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Route: Waiting for TUN/TAP interface to come up...
TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

Error 4:
C:\Windows\system32\route.exe ADD 180.150.157.8 MASK 255.255.255.255 192.168.0.1
The route addition failed: The object already exists.
C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.25.12.209 OK!
C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.25.12.209 OK!
C:\Windows\system32\route.exe ADD 10.25.0.1 MASK 255.255.255.255 10.25.12.209 OK!
Initialization Sequence Completed
[server] Inactivity timeout (--ping-restart), restarting
TCP/UDP: Closing socket

Restart your machine to refresh the non-responding services. After that, launch ExpressVPN and connect to a server location.

If restarting your machine does not solve the problem, follow the steps below to perform a Winsock reset:

Step 1: Click Start > All Programs > Accessories

Step 2: For Windows Vista or higher, right-click on Command Prompt and then choose Run as Administrator to launch the prompt with full administrative privileges.

For Windows XP, just click on Command Prompt directly.

Step 3: In the Command Prompt, enter the following commands:

netsh int ip reset logfile.txt

followed by

netsh winsock reset catalog

Step 4: Restart your machine. Restart your machine. After that, launch ExpressVPN and connect to a server location.

If performing a Winsock reset does not solve the problem, follow the steps below to restart DHCP Services:

Step 1: Click Start > Run (or Window Key + R on your keyboard) and enter

services.msc

Then click OK.

Step 2: On the Services list, double-click on DHCP Client.

Step 3: Set the Startup Type to “Automatic”

If the Service’s status is “Stopped”,  click on Start to get the service running.

If the Service’s status is already on “Started”, click on Stop first and then Start again to re-start it.

Step 4: Close the Services control panel and then try connecting to ExpressVPN again.

Note: If you still encounter connection issues, please try manually setting your DNS to our recommended servers and also ensure that you don’t have any antivirus filters hindering your VPN connection. You can also contact the ExpressVPN Support Team for immediate assistance.

Back to top