Routing and Remote Access Event ID 20100Last reviewed: December 12, 1997Article ID: Q172512 |
The information in this article applies to:
SYMPTOMSAfter 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.
RESOLUTIONObtain the Routing & Remote Access Service Hotfix Update mentioned below.
STATUSMicrosoft 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:
http://www.microsoft.com/communications/routing&ras.htmNOTE: Because the Microsoft Web site is constantly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address:
http://www.microsoft.com/ MORE INFORMATIONThe third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. Keywords : kbbug4.00 kbfix4.00 ntnetserv ntrouter NTSrv kb3rdparty kberrmsg kbnetwork Version : WinNT:4.0 Platform : winnt Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |