Hello, we encountered similar problems. The client does not look stable also.
Few of employees encountered a problems with VPN connection establishment on win10.
Having issues with Azure VPN client on all windows 10 Enterprise computers
When our users log into Azure VPN it will not allow them to log in. There are different errors that we get which are below:
- Connecting to VPN server failed with exception: A socket operation was attempted to an unreachable host
- The operation was canceled by the user
- Failure in acquiring AAD token: Keyset does not exist.
We do have Multi-factor authentication setup for all users
We have noticed every time an update from Microsoft or a WiFi wireless network driver that updated azure VPN stops working. How we have noticed this is all users will be working and all of a sudden one day it stops working. We have uninstalled azure and reinstalled it and still no go. We have googled the errors and some says a driver, or Microsoft updates.
Once we update either Microsoft updates, or the Dell driver for our WiFi wireless network card Azure works again.
On some computers that doesn't need the update or the network drivers they work. On other computers that doesn't work we are being forced to update both Microsoft updates, or the driver and it appears to work.
We have also went to Device manager and expand network adapters and uninstalled WAN mini ports and scan for hardware changes to bring them back and that sometimes works
I maybe wrong about the Microsoft updates or the driver. However, I believe Azure is looking for something in the computer like the registry that it requires in order for it to work.
My question I have is what is azure looking for in the update or the driver in order for the Azure client to work? or what is it needing without us having to go through the updates every time?
-
Krzysztof Świdrak 166 Reputation points
2023-01-30T13:59:38.33+00:00
1 additional answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more