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

Sophos SSL VPN Connection Error- The system tried to join a drive to directory on joined drive."

Hello,
We installed Sophos Unified Threat Management (UTM) 9 Home Edition on our AWS instance several years ago.
Everything has been working normally since the time of installation few years ago, but now we are experiencing an error

ERROR
"TCP: connect to [AF_INET] failed, will try again in 5 seconds. The system tried to join a drive to directory on joined drive."
See attached screenshot

NOTE:
1- We have not made any changes to the firewall settings or the firewall server settings in the distant past.
2- We have already restarted the firewall server twice to see if the server restart will solve the root cause of the problem. The restart did not solve the root cause of the problem
3- We have already restarted our windows 10 laptop twice to see if the laptop restart will solve the root cause of the problem. The restart did not solve the root cause of the problem
3- We are getting the same issue on our other laptops and desktop machines that we use to login to the SSL VPN

AWS
We already contacted AWS technical and network support. They have checked everything on their end and they are saying tgat everything is working normally with the VPC as well as the instance and the security rules. AWS tean recommended that we contact SOPHOS and seek assistance

 

We will appreciate any and all help as we have been struggling with this issue for over a week now



This thread was automatically locked due to age.
Parents
  • Privet Mac and welcome to the UTM Community!

    There was no attachment - where are you seeing this error message?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Hi Bob,

    Thanks for the reply. Please see the attached screenshot. We have marked out private information such as IP address etc

    Any ideas as to what is the root cause of this problem?

  • Mac, let's look at both the client and server logs for a single connection.  Disable the SSL VPN Profile in the UTM and start the SSL VPN Live Log. Once lines begin to appear, enable the Profile and then try to connect from a client.

    Instead of screen caps, copy and paste the lines from the logs.  If you prefer, obfuscate IPs like 84.XX.YY.121, 10.X.Y.100, 192.168.X.200 and 172.2X.Y.51.  That lets us see immediately which IPs are local and which are identical or just in the same subnet.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Was this resolved? I have encountered this error off and on for years, seemingly at random...

  • Not sure if the same pertains to you, but I have a new ISP and my Sophos is behind a NAT.  I had to open a NAT for TCP 8443 to my Sophos.
    Hope this helps!

Reply Children
No Data