You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -282,7 +282,7 @@ This error message occurs if the client can't access http://crl3.digicert.com/ss
282
282
283
283
Check the proxy server settings, make sure that the client can access http://crl3.digicert.com/ssca-sha2-g1.crl and http://crl4.digicert.com/ssca-sha2-g1.crl.
284
284
285
-
## VPN Client Error: The connection was prevented because of a policy configured on your RAS/VPN server. (Error 812)
285
+
## VPN client error: The connection was prevented because of a policy configured on your RAS/VPN server. (Error 812)
286
286
287
287
### Cause
288
288
@@ -298,7 +298,7 @@ Make sure that RADIUS server is configured correctly. For More information, see
298
298
299
299
Root certificate hasn't been installed. The root certificate is installed in the client's **Trusted certificates** store.
300
300
301
-
## VPN Client Error: The remote connection was not made because the attempted VPN tunnels failed. (Error 800)
301
+
## VPN client error: The remote connection was not made because the attempted VPN tunnels failed. (Error 800)
302
302
303
303
### Cause
304
304
@@ -314,7 +314,38 @@ Update the NIC driver:
314
314
1. If Windows doesn't find a new driver, you can try looking for one on the device manufacturer's website and follow their instructions.
315
315
1. Restart the computer and try the connection again.
316
316
317
-
## VPN Client Error: Dialing VPN connection \<VPN Connection Name\>, Status = VPN Platform did not trigger connection
317
+
## <aname="entra-expired"></a>VPN client error: Your authentication with Microsoft Entra has expired
318
+
319
+
If you're using Microsoft Entra ID authentication, you might encounter the following error:
320
+
321
+
**Your authentication with Microsoft Entra has expired so you need to re-authenticate to acquire a new token. Please try connecting again. Authentication policies and timeout are configured by your administrator in Entra tenant.**
322
+
323
+
### Cause
324
+
325
+
The point-to-site connection is disconnected because the current refresh token has expired or becomes invalid. New access tokens can’t be fetched for authenticating the user.
326
+
327
+
When an Azure VPN Client tries to establish connection with an Azure VPN gateway using Microsoft Entra ID authentication, an access token is required to authenticate the user. This token gets renewed approximately every hour. A valid access token can only be issued when the user has a valid refresh token. If the user doesn’t have a valid refresh token, the connection gets disconnected.
328
+
329
+
The refresh token can show as expired/invalid due to several reasons. You can check User Entra sign-in logs for debugging. See [Microsoft Entra sign-in logs](/entra/identity/monitoring-health/concept-sign-ins).
330
+
331
+
***Refresh token has expired**
332
+
333
+
* The default lifetime for the refresh tokens is 90 days. After 90 days, users need to reconnect to get a new refresh token.
334
+
* Entra tenant admins can add conditional access policies for sign-in frequency that trigger periodic reauthentication every 'X' hrs. (Refresh token will expire in 'X' hrs). By using custom conditional access policies, users are forced use an interactive sign-in every 'X' hrs. For more information, see [Refresh tokens in the Microsoft identity platform](/entra/identity-platform/refresh-tokens) and [Configure adaptive session lifetime policies](/entra/identity/conditional-access/howto-conditional-access-session-lifetime).
335
+
336
+
***Refresh token is invalid**
337
+
338
+
* The user has been removed from tenant.
339
+
* The user's credentials have changed.
340
+
* Sessions have been revoked by the Entra tenant Admin.
341
+
* The device has become noncompliant (if it’s a managed device).
342
+
* Other Entra policies configured by Entra Admins that require users to periodically use interactive sign-in.
343
+
344
+
### Solution
345
+
346
+
In these scenarios, users need to reconnect. This triggers an interactive sign-in process in Microsoft Entra that issues a new refresh token and access token.
347
+
348
+
## VPN client error: Dialing VPN connection \<VPN Connection Name\>, Status = VPN Platform did not trigger connection
318
349
319
350
You might also see the following error in Event Viewer from RasClient: "The user \<User\> dialed a connection named \<VPN Connection Name\> which has failed. The error code returned on failure is 1460."
0 commit comments