Article ID: 233340 - Last Review: February 27, 2007 - Revision: 1.3

Event ID 20100 on Server When SecurID Client Is Not Authenticated

This article was previously published under Q233340
Expand all | Collapse all

SUMMARY

A client may not be successfully authenticated on a Windows NT 4.0 RAS server using the Security Dynamics Secure Windows NT Domain Access system if the user's SecurID user name and Windows NT user name do not match. The Security Dynamics Secure Windows NT Domain Access system consists of the ACE/Server and a SecurID authenticator. SecurID authenticators can be in many different form factors, including smart cards, hand-held hardware tokens and key fobs, and software tokens.

When this occurs, event ID 20100 is generated on the Windows NT Server that attempted to authenticate the user:
Event ID: 20100
Source: Router
Description: The user was authenticated as user name 1 by the third party security host module but was authenticated as user name 2 by the RAS security. The user has been disconnected.

MORE INFORMATION

For more information about the Security Dynamics Secure Windows NT Domain Access system, see the Security Dynamics Web site at:
http://www.securitydynamics.com (http://www.securitydynamics.com)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

APPLIES TO
  • Microsoft Windows 98 Standard Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
Keywords: 
kbdialup kbinfo kbnetwork KB233340
 

Article Translations

 

Related Support Centers