Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 31 subscribers
  • Views 4615 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 does not connect after upgrade to SFOS 18.0.3 MR-3

April Beachy

We upgraded one of our Firewalls to SFOS 18.0.3 MR-3 from 18.0.1 MR1 and our SSL VPN clients quit working.

We get the error:

the system tried to join a drive to a directory on a joined drive

Any thoughts on the cause?



This thread was automatically locked due to age.
Parents
  • 0

    Hi all. just throwing my tuppence worth in. 

    I'm on 18.0.1 MR1,  I had this same problem and although I have not found the easy fix, I feel the problem is something to do with the PCs.. 

    I'm also only experiencing this on DELL machines, and the fix for me was to reinstall windows (wipe hard drive, fresh install) and the problem goes away. so using the same sslVPN installer, same firewall (nothing has changed)  I'd already tried to remove all recent windows and DELL updates to no effect. but a full re-install sorted it. (10 Pcs/ 1 laptop had the same issue).

  • 0 in reply to David Harrison1

    I am not wiping a couple dozen laptops.  A roll back of the firewall firmware fixed the issue. I guess I will log a ticket and see if I can get any support for the issue.  Now is not the time to break VPNs with all of workforce having remote access because of COVID and working from home at least once a week.

  • 0 in reply to April Beachy

    from what I read about that "Bad encapsulated packet length from peer" followed by strange packet size value, maybe related to Userportal available from public internet on port 443 and SSL VPN server listening on 443 as well.

    Sophos devices, UTM and XG, have ever had problems with this configuration. Never the less this is the default configuration of the machines.

    So my experience with this is since UTM 8.x to use a different port for userportal. This is also what support recently confirmed after userportal became inaccessible from one day to an other without change in V18 MR1.

    If you have time to test - disable userportal from WAN and try again to connect a client or change the port of userportal generally.

Reply
  • 0 in reply to April Beachy

    from what I read about that "Bad encapsulated packet length from peer" followed by strange packet size value, maybe related to Userportal available from public internet on port 443 and SSL VPN server listening on 443 as well.

    Sophos devices, UTM and XG, have ever had problems with this configuration. Never the less this is the default configuration of the machines.

    So my experience with this is since UTM 8.x to use a different port for userportal. This is also what support recently confirmed after userportal became inaccessible from one day to an other without change in V18 MR1.

    If you have time to test - disable userportal from WAN and try again to connect a client or change the port of userportal generally.

Children