The information in this article applies to:
SYMPTOMSWhen you use Dial-Up Networking in Windows 95 to dial into a remote network, you may receive the following error message when the remote Microsoft Windows NT server attempts to validate you: After you receive this error message, the dial-up client may still be attached to the network (but without authentication) and may have access to some resources on the domain. In some cases, connectivity is not established at all. CAUSE
This error message occurs when the TCP/IP protocol (specifically,
Vnbt.386) is not completely bound to the redirector (Vredir) before
the logon request occurs. The DOMAINNAME<1ch> name query request is never sent to the WINS server; therefore, the Windows 95 client never finds a domain controller that can validate its logon.
RESOLUTIONThis issue is resolved by the following updated file for Windows 95 and OEM Service Release 1 (OSR1):
This file is included in the self-extracting RASUPD.EXE file.
This issue is resolved by the following updated file for Windows 95 OEM Service Release 2 (OSR2) and 2.1:
This file is included in the self-extracting RAS2UPD.EXE file.
The following files are available for download from the Microsoft Software Library. Click the file names below to download the files: Rasupd.exe Ras2upd.exeRelease Date: Jan-30-1997 For more information about how to download files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base: Q119591 How to Obtain Microsoft Support Files from Online Services STATUSThis issue is resolved in Microsoft Windows 98. MORE INFORMATIONThis issue is also discussed in the following article in the Microsoft Knowledge Base: Q150053 Erratic Domain Logon from Windows 95 Dial-Up Networking Additional query words: timeout
Keywords : kberrmsg kbfile kbnetwork dun win95 |
Last Reviewed: January 3, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |