Since the last Update Windows 10 and Sophos VPN doesn't work

Hi

Very sorry for the troubles caused.

This issue is being caused by users being configured multiple times in one remote access profile. So, if you configure Joe directly and Joe is also member of a group which is configured for the same profile you run into this bug. It is also triggered by the same user being member of multiple groups which are configured for SSL VPN remote access.

You can fix the issue by removing the duplication and configure each user only once. I know that might be difficult with backend groups or comlex setups, but maybe it works for you. We are investigating what caused this regression.

d12fk said:

This issue is being caused by users being configured multiple times in one remote access profile. So, if you configure Joe directly and Joe is also member of a group which is configured for the same profile you run into this bug. It is also triggered by the same user being member of multiple groups which are configured for SSL VPN remote access.

This issue happens (for us, at least) even when the user is *not* configured multiple times in the same remote access profile.

d12fk said:

This issue is being caused by users being configured multiple times in one remote access profile. So, if you configure Joe directly and Joe is also member of a group which is configured for the same profile you run into this bug. It is also triggered by the same user being member of multiple groups which are configured for SSL VPN remote access.

This issue happens (for us, at least) even when the user is *not* configured multiple times in the same remote access profile.

In my case the problem was the username with "ö".

In the last years there was no problem with it.

regards Peter

Matthew said:

This issue happens (for us, at least) even when the user is *not* configured multiple times in the same remote access profile.

I've heared (but have not checked) that the issue also happens when the same user is configured in two or more profiles.

PRad said:

In my case the problem was the username with "ö".

In the last years there was no problem with it.

And you shouldn't have one. However, this kind of problem is different. Will test this later today. Thanks.

I cannot confirm the issue with umlauts in user names. Configured a user "jörg" and configuration for that user was written fine.

Can also not confirm the issue happening if the same user is configured in more than one profile unless the two profiles also define the same local network.

So, to work around this issue please make sure that the same user doesn't have the same network configured twice (or more). As soon as the accumulated networks over all profiles have duplicates in them, these duplicates will not be pushed.

As a workaround you could define sub- or supernets instead and use them in the different profiles, i.e. 192.168.0.0/24 in one and 192.168.0.0/25 and 192.168.0.128/25 in the other. When a user is only present in one profile but multiple times you could resolve the user duplication in that very profile.

I plan for fixing this issue in the coming days, so it will be part of the next UTM 9.4 update.

Again sorry for the troubles, we'll make sure this sort of issue will not happen again.