| Event Id | 20152 |
| Source | RemoteAccess |
| Description | The currently configured authentication provider failed to load and initialize successfully. The parameter is incorrect. |
| Event Information | Explanation: The Routing and Remote Access service is not available because the authentication provider failed to load and start. Possible causes include: If the Routing and Remote Access service is configured for RADIUS authentication: a. The file rasrad.dll might be missing from the %SystemRoot%\system32 folder. b. The RADIUS server name might be misspelled. c. The RADIUS server might not be running. If the Routing and Remote Access service is configured for Windows Authentication, the local Internet Authentication Service (IAS) might not have started. User Action: To ensure that the authentication provider can load and start, first determine whether the Routing or Remote Access service should be configured for RADIUS authentication or for Windows Authentication. Then do one of the following: a. If the service should be configured for RADIUS, confirm that the RADIUS server name is spelled correctly and that the server is available. b. If the service is configured for Windows Authentication, look for IAS-specific events in Event Viewer on the local computer and correct any errors. c. If the service should be configured for Windows Authentication but is not, use the Routing and Remote Access snap-in or the Netsh command-line utility to reconfigure it. For more information about this event click on the link given below to a Microsoft article. |
| Reference Links | You
cannot start the Routing and Remote Access service on a Windows 2000
Server-based computer or on a Windows Server 2003-based computer For more information. |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.