Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 8163 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

SSl VPN Can't connect after computer goes into suspend

RChadwick
I'm running the latest 9.210-20, and my PC is running Windows 8.1. The SSL VPN connects fine, but if the computer goes into suspend while the VPN is connected, the connection is 'broken'. When I reconnect, the little traffic light shows green, and I get a 'Connected' message. However, there is no VPN connection. Disconnecting and reconnecting doesn't help. Rebooting the PC doesn't help. Oddly, connecting with another device (One of my Android devices) works fine, even though the username and password is the same as on the PC. Once, this fixed itself eventually. Another time, I had to reboot the UTM before it would work again. Is there a setting to get the session to time out properly, or some other fix or workaround for this behavior?
Thanks!


This thread was automatically locked due to age.
Parents
  • 0
    On the 'Settings' tab, have you selected 'Allow multiple concurrent connections per user'?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    It was originally checked, but when I was having problems, I noticed it, and thinking it might be insecure, I unchecked it. I re-checked it last night, and tried to connect. The first time failed, but without doing anything else (Rebooting, disabling users, etc), it connected fine on the second try. 

    Also, before connecting these last 2 times, I downloaded and reinstalled the latest client from the UTM. 

    Also, I can tell by timing if it will work. If the time between trying to connect, and the time it says 'Connected' is about 10 seconds, the connection works. When the connection doesn't work, the connect time is about 30 seconds.
Reply
  • 0 in reply to BAlfson
    It was originally checked, but when I was having problems, I noticed it, and thinking it might be insecure, I unchecked it. I re-checked it last night, and tried to connect. The first time failed, but without doing anything else (Rebooting, disabling users, etc), it connected fine on the second try. 

    Also, before connecting these last 2 times, I downloaded and reinstalled the latest client from the UTM. 

    Also, I can tell by timing if it will work. If the time between trying to connect, and the time it says 'Connected' is about 10 seconds, the connection works. When the connection doesn't work, the connect time is about 30 seconds.
Children
No Data
Unfiltered HTML