Routing and Remote Access Event ID 20100 (172512)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Server 4.0
- Microsoft Routing and Remote Access Service Update for Windows NT Server 4.0
This article was previously published under Q172512 SYMPTOMS
After you install the Routing and Remote Access (RRAS) Update for Windows
NT 4.0 on your Windows NT 4.0 RAS server, Dial-Up Networking (DUN) clients
may not be able to connect to your RAS server when using third party
security authentication; one such product is SecurID from Security
Dynamics. You may also note the following event log message in the event
viewer on the RRAS server:
Event ID: 20100
Source: Router
Description: The user was authenticated as %1 by the third party
security host module but was authenticated as %2 by the RAS
security. The user has been disconnected.
Where %1 and %2 are variables that represent user names. NOTE: In Windows 2000 you receive Event ID 20096, where the source is RemoteAccess, but the text is the same.
RESOLUTION
Obtain the Routing & Remote Access Service Hotfix Update mentioned below. To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed this to be a problem in Routing and Remote Access
Update for Windows NT Server version 4.0. This problem was corrected in
the Routing & Remote Access Service Hotfix Update. You can obtain this
update from Microsoft's World Wide Web Site on the Internet at the
following location:
NOTE: Because the Microsoft Web site is regularly updated, the site
address may change without notice. If this occurs, link to the Microsoft
home page at the following address:
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Modification Type: | Minor | Last Reviewed: | 7/16/2004 |
---|
Keywords: | kb3rdparty kbbug kberrmsg kbfix kbnetwork KB172512 |
---|
|