Comments
-
Hi @netwatch2077 No, we haven't found a real conclusion. They suggested that the users were using the IP instead of the URL which leads to this error (you can try it yourself). Not sure whether this is the real cause as I've witnessed users logging in using the URL and receiving this same error. Anyway, we are now 1 month…
-
Hello @"james.carson" Thanks for your reply. Indeed I started to write a powershell script to install it. Still have to search how to deploy this through intune. For other's interest; it looks like this: Set-ExecutionPolicy -ExecutionPolicy Bypass -scope processstop-process -name 'wgsslvpnsrc' -Forcestop-process -name…
-
Hi @"james.carson" Thanks for your suggestion, I've submitted a support case. @John_Sells I've checked and the clients are using the correct FQDN as configured in the saml configuration (i.e. https://connect.company.com). When they encounter this error and immediately try again with the same paramaters, it does succeeds so…
-
@"james.carson" & @Bruce_Briggs Thanks for the helpfull tips! I overlooked the function of having a policy specific for VPN users/groups. I'm more used to the old-fashioned way of using source IP's etc. Thanks!
-
Ok thanks, any other possibility to achieve my use case? I.e. assign Policies to specific VPN clients. My first thought was to add a new SSL VPN interface, but AFAIK you can only have 1. Maybe I could use another way of mobile VPN (ipsec, L2TP...)?
-
OK thanks for the extra information, this makes me feel more comfortable about the security of my environment.
-
Thanks for your response. So If I read the last comment of your link well; watchguard is using an old version of openvpn but is patching it themselves (e.g. for security issues)?
-
Ok thanks for the clarification. I was a bit suspiscious as the openvpn version included in the watchguard mobile VPN client (12.7.2) dates already from 2018 (!!) which made me thinking about how safe watchguard vpn setup is. Maybe I change the watchguard clients with an up-to-date versions of openvpn in the future. FYI,…