VPN: Site to Site and Remote Access Switched to Sophos Connect - Now the SSL Remote Access isn't working anymore

UTM Firewall requires membership for participation - click to join

Our current Support phone numbers for India will cease functioning as of October 31, 2023. Click here to find the new phone number

Sophos UTM: Decommissioning of obsolete URL categorization services CFFS. Click here for important info.

Thread Info

State Verified Answer
Locked Locked
Replies 8 replies
Subscribers 7 subscribers
Views 3572 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

Switched to Sophos Connect - Now the SSL Remote Access isn't working anymore

Detlef Follmer1 over 1 year ago

The environment:

Firewall: Sophos UTM 9, Model SG330, Firmware 9.710-1

Remote Access (SSL) running more than 2 years now - with the Sophos SSL VPN Client on a HP Elitebook with Windows 10 Pro.

I setup another HP Elitebook (same Model) with Windows 10 Pro

Of course I installed Sophos Connect (Version 2.1.20.0309) and now I can't login to the VPN. Reason 'AUTH FAILED'

Just to make it weird:

The login using the 'old' VPN Client is still working properly.

Any ideas?

This thread was automatically locked due to age.

Top Replies

Kevin Cooke1 over 1 year ago +2 verified

Do you have a space in the password? the current version of connect does not work for SSL VPN when there is a space in the password

0 Amodin over 1 year ago

Incorrect login credentials?

PFSense Plus 23.05 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
16GB Memory | 500GB SSD HDD | Fiber Conn (awaiting ATT Fiber)
(Former Sophos UTM Veteran, XG Rookie)
Cancel
Vote Up 0 Vote Down

Cancel
+1 Kevin Cooke1 over 1 year ago

Do you have a space in the password? the current version of connect does not work for SSL VPN when there is a space in the password
Cancel
Vote Up +2 Vote Down

Cancel
0 Detlef Follmer1 over 1 year ago in reply to Kevin Cooke1

Yes, you're right. What a bug.....

Hope this will be fixed.

Many thanks for this help.
Cancel
Vote Up 0 Vote Down

Cancel
0 Kevin Cooke1 over 1 year ago in reply to Detlef Follmer1

The last update I received from my account manager back in December was "space support within a password will be added in Sophos Connect 2.3" - but he was unable to provide an ETA on it.
Cancel
Vote Up 0 Vote Down

Cancel
0 Amodin over 1 year ago in reply to Kevin Cooke1

They still need to get 2.2 out the door to fix the DNS bug in 2.1, lol.

Never-ending, I wish I had gotten into software development early in my years to make that money. ;P

PFSense Plus 23.05 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
16GB Memory | 500GB SSD HDD | Fiber Conn (awaiting ATT Fiber)
(Former Sophos UTM Veteran, XG Rookie)
Cancel
Vote Up 0 Vote Down

Cancel
0 Dominik Wagner over 1 year ago in reply to Amodin

You and me both, pal, you and me, both.
Cancel
Vote Up 0 Vote Down

Cancel

0 SaxdaAnhalta over 1 year ago in reply to Kevin Cooke1

try a # at the beginning of the password, that's also interesting... it took weeks for the support to confirm that it's also a small problem ;-)

that was 12.2020 ...

0 Albeck over 1 year ago in reply to Kevin Cooke1

I think there are even more "special characters" that does not work with the new Sophos Connect Client.

From my experience a user had to change her password because she was using " " ".

IT Stuff: Please use strong passwords.

Users: Sure, will do!

Sophos: Sry I cant log you in..your password is too complex :)
Cancel
Vote Up 0 Vote Down

Cancel