Event Id | 20276 |
Source | RemoteAccess |
Description | CoId=%1: Layer=%2: SubLayer=%3: The connection attempt failed on port: %4 because of the authentication protocol selected. Check to see if the authentication protocol is supported in the operating systems at the client and server ends of the connection |
Event Information | According to Microsoft : Cause : This event is logged when the connection attempt failed on port because of the authentication protocol selected. Resolution : Correct the mismatch in client and server configuration parameters Possible resolution: Check that the remote access client connection is configured with the same connection parameters as the remote access server. For example, Microsoft Challenge Handshake Authentication Protocol (MS-CHAP) version 1 is not supported in the Windows Vista operating system. MS-CHAP version 2 should be used instead because it provides better security. However, Network Policy Server (NPS) supports and can be configured to use MS-CHAPv1 or MS-CHAPv2. There is a potential mismatch in this case with authentication protocols in the client and server configuration parameters. In this case, on the client computer running Windows Vista, change the authentication protocol configuration parameter from MSCHAPv1 to MSCHAPv2, and attempt to re-establish the connection. Verify : To verify that the remote access server can accept connections, establish a remote access connection from a client computer. To create a VPN connection:
|
Reference Links | Event ID 20276 from RemoteAccess |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.