Guest User!

You are not Sophos Staff.

Thread Info
  • Locked Locked
  • Replies 13 replies
  • Subscribers 5 subscribers
  • Views 34768 views
  • Users 0 members are here
Options
Suggested
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

Since the last Update Windows 10 and Sophos VPN doesn't work

PRad

After Update our Sophos Appliance to the latest 9.4 version, the VPN with Windows 10 doesn't work.

Windows 7 works perfekt no Problem, but ohn windows 10 the VPN connect, but no RDP connection possible!

Has anyone the same problem?

regards Peter



This thread was automatically locked due to age.
Parents

  • Yep. I implemented a temporary workaround by changing /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf as such:

    # push 'route-gateway 10.242.2.1'
    push "route 0.0.0.0 0.0.0.0 10.242.2.1"

    And then ran:

    /var/mdw/scripts/openvpn restart

    Reconnected the SSL VPN, and all is well.

  • in reply to TimDufrane

    Unknown said:

    Yep. I implemented a temporary workaround by changing /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf as such:

    # push 'route-gateway 10.242.2.1'
    push "route 0.0.0.0 0.0.0.0 10.242.2.1"

    And then ran:

    /var/mdw/scripts/openvpn restart

    Reconnected the SSL VPN, and all is well.

    You are a star. Won't this set the default route, though, and make *all* requests go through the tunnel? I modified the command to just route requests to the remote internal subnet:

    push 'route 192.168.5.0 255.255.255.0 10.242.2.1'

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

  • in reply to MatthewArciniega1

    Matthew said:

    Tim Dufrane

    Yep. I implemented a temporary workaround by changing /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf as such:

    # push 'route-gateway 10.242.2.1'
    push "route 0.0.0.0 0.0.0.0 10.242.2.1"

    And then ran:

    /var/mdw/scripts/openvpn restart

    Reconnected the SSL VPN, and all is well.

    You are a star. Won't this set the default route, though, and make *all* requests go through the tunnel? I modified the command to just route requests to the remote internal subnet:

    push 'route 192.168.5.0 255.255.255.0 10.242.2.1'

    Hi Matt,

    Yes, that will cause it to become the default route. For my situation that's the desired effect. The basic command, as you found, can get as granular as you want with multiple routes. However, keep in mind this will apply to all users - if you have specific users who need more specific routes, their individual configs can be modified through /var/sec/chroot-openvpn/etc/openvpn/conf.d/username.

Reply
  • in reply to MatthewArciniega1

    Matthew said:

    Tim Dufrane

    Yep. I implemented a temporary workaround by changing /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf as such:

    # push 'route-gateway 10.242.2.1'
    push "route 0.0.0.0 0.0.0.0 10.242.2.1"

    And then ran:

    /var/mdw/scripts/openvpn restart

    Reconnected the SSL VPN, and all is well.

    You are a star. Won't this set the default route, though, and make *all* requests go through the tunnel? I modified the command to just route requests to the remote internal subnet:

    push 'route 192.168.5.0 255.255.255.0 10.242.2.1'

    Hi Matt,

    Yes, that will cause it to become the default route. For my situation that's the desired effect. The basic command, as you found, can get as granular as you want with multiple routes. However, keep in mind this will apply to all users - if you have specific users who need more specific routes, their individual configs can be modified through /var/sec/chroot-openvpn/etc/openvpn/conf.d/username.

Children
No Data
Unfiltered HTML