Hello there,

Thank you for contacting the Sophos Community.

This is a known issue and fixed on Sophos Connect 2.2, no ETA at this time.

Regards,

emmosophos it this really a known issue which is beeing fixed in SC 2.2 on or is this just "known" by some people? Can you post the NC ID please?

The latest Sophos known issues list Sophos_KIL_2022-02-11.xlsx still does not list this issue.

We thought about rolling out SC with IPsec but it has less flexibility compared to SSL configs. The only major disadvantage is the failing login with space in the password for SSL VPN, which works when using IPsec VPN. Same VPN client, though.

Hello LHerzog,

Thank you for reaching out.

Sure, it would be NCL-1319 might be coming out as a different NC when Sophos Connect 2.2 comes out as there are a couple of NCs that overlap.

Regards,

Hello LHerzog,

Thank you for reaching out.

Sure, it would be NCL-1319 might be coming out as a different NC when Sophos Connect 2.2 comes out as there are a couple of NCs that overlap.

Regards,