I am using SSL VPN within our company with a UTM220.
When a company laptop is trying to connect via VPN, it often fails the first time with
TEST ROUTES: 0/0 succeeded len=4 ret=0 a=0 u/d=down
Route: Waiting for TUN/TAP interface to come up...
.
.
.
MANAGEMENT: >STATE:1426590695,ADD_ROUTES,,,
C:\Windows\system32\route.exe ADD MASK 255.255.255.255 192.168.1.1
Route addition via service succeeded
C:\Windows\system32\route.exe ADD 10.242.2.1 MASK 255.255.255.255 10.242.2.5
Warning: route gateway is not reachable on any active network adapters: 10.242.2.5
Route addition via service failed
C:\Windows\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 10.242.2.5
Warning: route gateway is not reachable on any active network adapters: 10.242.2.5
Route addition via service failed
C:\Windows\system32\route.exe ADD 192.168.30.0 MASK 255.255.255.0 10.242.2.5
Warning: route gateway is not reachable on any active network adapters: 10.242.2.5
Route addition via service failed
at the end of the VPN log it says:
Initialization Sequence Completed With Errors ( see openvpn.net/faq.html
when you disconnect and reconnect, then it is mostly working and the Initialization Sequence" says "completed" and all routes could be added properly.
This problem exists on every company laptop.
This weekend I reinstalled my laptop and the error seems to be gone. The laptop was readded to the domain and I reinstalled every patch which was offered through my WSUS.
Everytime I connect, it says " sequence completed" and my VPN is working properly.
But what the hell is wrong with the other computers? what is different?
Every user is Admin on his machine so permissions should not be a problem. I also did not configure anything like "start as Administrator" on my machine.
On different websites you can read some solutions which did not help me yet (e.g. set "Media Status" in the device manager to "always connected").
Does anyone have an idea what can be wrong?
This thread was automatically locked due to age.
