Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 17 replies
  • Subscribers 7 subscribers
  • Views 7096 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

Sophos Connect Authentication failed | Sophos VPN SSL Client works

Erik Puscher

Hello,

since the last firewall update we are forced to use the new Sophos Connect.

Sadly there are connection problems with this client.

I can properly connect via the old VPN SSL Client. If i uninstall it and install Sophos Connect the authentication fail.

I didn't change anything on the firewall (UTM9 SG210) yet.

What i see in the logs is maybe a problem with ad authentication.

Via the old client it searches and find our first dc and establish the connection (ip is an example)

severity="info" sys="System" sub="auth" name="Trying 192.168.0.1 (adirectory)"

Via the new client it goes through the entire list of DC Server and finally failes

severity="info" sys="System" sub="auth" name="Trying 192.168.0.1 (adirectory)"

severity="info" sys="System" sub="auth" name="Trying 192.168.0.2 (adirectory)"

severity="info" sys="System" sub="auth" name="Trying 192.168.0.3 (adirectory)"

Do i have to change anything regarding the ad connectivity with the new client?

I don't want to exclude the old ones in any way.



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to Vivek Jagad

    Thanks to Vivek we found the problem.

    We use passwords with space witch where never a problem with the old client. But they are with the new one.

    I don't now why they changed this. Exclude characters from passport possibilities is never a good thing. And it harms our company password policy.

Children
Unfiltered HTML