Reflexion will be End-of-life on March 31,2023. See Sophos Reflexion EoL FAQs to learn more.
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.
Incorrect login credentials?
XG 19.5 GA 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz 16GB Memory | 500GB SSD HDD | GB Ethernet x5
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
Yes, you're right. What a bug.....
Hope this will be fixed.
Many thanks for this help.
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.
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
You and me both, pal, you and me, both.
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 ...
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 :)