Authentication failed because the client found that a stronger authentication protocol is available. Try connecting again.
Auth2ECDSAP256CAName: %1!s! Auth2ECDSAP256CertMapping: %2!s! Auth2ECDSAP256CertType: %3!s! Auth2ECDSAP256HealthCert: %4!s! ...
Auth2ECDSAP384CAName: %1!s! Auth2ECDSAP384CertMapping: %2!s! Auth2ECDSAP384CertType: %3!s! Auth2ECDSAP384HealthCert: %4!s! ...
Authenticate messages if authentication level for calls (on Security Property Page) is not NONE. This is Windows 2000 behavior. ...
Authentication failed because the client can't support any of the authentication protocol versions received from the server. ...
Authentication failed because the client found that a stronger authentication protocol is available. Try connecting again. ...
Authentication failed because the server is requesting the client's real identity, but the client can only provide a pseudonym. ...
Authentication failed because there's a problem with the attributes in the authentication request message received from the ...
Authentication failed due to a user account restriction or requirement that was not followed. For example, the user account ...
Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user ...