Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

User's need to suddenly run SSL VPN as admin

We have been using Sophos UTM 9.3 for well over a year now, a pair of SG210 in an active/passive standby.  We have been using the SSL VPN for remote access on our user's machines.  This has been working fine until recently for a few users, which are now required to "Run as Administrator"  If they try to connect the process fails to add the routes and assign the IP to the TAP adapter.

Again, this has just popped up out of the blue.  The users have always been local admins on their machines.  Mix of Win7, 8/8.1 and 10.

Snippet of log..

-----------------------------------
Fri Apr 22 16:06:44 2016 ERROR: Windows route add command failed [adaptive]: returned error code 1
Fri Apr 22 16:06:44 2016 C:\windows\system32\route.exe ADD 10.2.0.0 MASK 255.255.0.0 192.168.251.21
Fri Apr 22 16:06:44 2016 ROUTE: route addition failed using CreateIpForwardEntry: Access is denied.   [status=5 if_index=3]
Fri Apr 22 16:06:44 2016 Route addition via IPAPI failed [adaptive]
Fri Apr 22 16:06:44 2016 Route addition fallback to route.exe
Fri Apr 22 16:06:44 2016 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
-----------------------------------

We've tried adding them to the [Network Configuration Operators] group in Windows with no luck.

Thanks for any ideas.

-Nate



This thread was automatically locked due to age.
Parents
  • I can confirm this, and I have submitted the issue to Sophos support, who are also confirming it. 

    On Windows machines, you can manually add the required route to your internal network in the OpenVPN config file. Disconnect the VPN client. Open the following file in a text editor: "C:\Program Files (x86)\Sophos\Sophos SSL VPN Client\config\[your user name]@home.vortx.com\[your user name]@home.vortx.com.ovpn"

    Add the following line:  

    route [internal subnet] [mask] [VPN gateway]

    For example: route 192.168.5.0 255.255.255.0 10.242.2.1

    Reconnect, and it should work. This will have to do until Sophos issues a fix. For other OS types, we may be out of luck for the time being.

    Matthew

    -----------------------
    SG210/UTM 9.407-3

Reply
  • I can confirm this, and I have submitted the issue to Sophos support, who are also confirming it. 

    On Windows machines, you can manually add the required route to your internal network in the OpenVPN config file. Disconnect the VPN client. Open the following file in a text editor: "C:\Program Files (x86)\Sophos\Sophos SSL VPN Client\config\[your user name]@home.vortx.com\[your user name]@home.vortx.com.ovpn"

    Add the following line:  

    route [internal subnet] [mask] [VPN gateway]

    For example: route 192.168.5.0 255.255.255.0 10.242.2.1

    Reconnect, and it should work. This will have to do until Sophos issues a fix. For other OS types, we may be out of luck for the time being.

    Matthew

    -----------------------
    SG210/UTM 9.407-3

Children
No Data