15:47:57:280: CRYPT_E_NO_REVOCATION_CHECK will not be ignored If you're using Routing and Remote Access, and Routing and Remote Access is configured for Windows Authentication (not Radius authentication), you see this behavior on the Routing and Remote Access server. If you're using IAS as your Radius server for authentication, you see this behavior on the IAS server. If you enable verbose logging on the server that is running IAS or Routing and Remote Access (for example, by running the netsh ras set tracing * enable command), information similar to the following one is displayed in the Rastls.log file that is generated when a client tries to authenticate. When you view the System log in Event Viewer on the client computer, the following event is displayed. This article provides a solution to an issue where clients can't authenticate with a server after you obtain a new certificate to replace an expired certificate on the server.Īpplies to: Windows 10 - all editions, Windows Server 2012 R2 Original KB number: 822406 SymptomsĪfter you replace an expired certificate with a new certificate on a server that is running Microsoft Internet Authentication Service (IAS) or Routing and Remote Access, clients that have Extensible Authentication Protocol-Transport Layer Security (EAP-TLS) configured to verify the server's certificate can no longer authenticate with the server.

Wurst client gives error while using