Updated: 4/4-2017
There have been a lot of issues, where people cannot connect correctly, with the SSL VPN client.
When you look into the logfiles, you typically see this:
Tue Jul 07 07:49:09 2015 TEST ROUTES: 0/0 succeeded len=4 ret=0 a=0 u/d=down
Tue Jul 07 07:49:09 2015 Route: Waiting for TUN/TAP interface to come up…
Tue Jul 07 07:49:13 2015 TEST ROUTES: 0/0 succeeded len=4 ret=0 a=0 u/d=down
Tue Jul 07 07:49:13 2015 Route: Waiting for TUN/TAP interface to come up…
Tue Jul 07 07:49:14 2015 TEST ROUTES: 0/0 succeeded len=4 ret=0 a=0 u/d=down
Tue Jul 07 07:49:14 2015 Route: Waiting for TUN/TAP interface to come up…
There have been reported several workarounds/fixes for this, but this issue actually lies behind the NDIS driver provided by OpenVPN, which is the same client the Sophos UTM uses.
While waiting for Sophos to come up with a new version of their client (Presently they are at version 2.1), you can get things running by downloading the openvpn TAP Windows driver here:
https://swupdate.openvpn.org/community/releases/tap-windows-9.21.2.exe
Summarize:
1) Close all active VPN tunnels
2) Download and install the TAP driver above or from OpenVPN.
3) Right-click on this file: C:\Program Files (x86)\Sophos\Sophos SSL VPN Client\bin\openvpn-gui.exe and choose properties -> compatibility – > run as administrator -> Press OK
4) Reboot PC and try again
Source: https://community.openvpn.net/openvpn/ticket/316
If this does not solve the problems, try to reset WinSock in Windows, with theese steps:
- Command prompt with administrative rights!
- Type “netsh winsock reset catalog” – Enter
- Type “netsh int ipv4 reset reset.log” – Enter
- Reboot the machine
Let me hear the results 🙂
