The information in this article applies to:
SYMPTOMSWhen you use a Windows 95/98 Dial-Up Networking (DUN) client to dial a Windows NT Remote Access Service (RAS) server and you attempt to log on to a Windows NT domain, your logon scripts may not run and you may receive the following error message: In addition, when you attempt to gain access to a network share, you may receive the following error message:
CAUSEThis behavior occurs when both TCP/IP and the IPX/SPX compatible protocol are installed on a Windows 95/98 client, and both protocols are enabled for the dial-up connection. The IPX/SPX Netlogon requests may reach the primary domain controller (PDC) before the TCP/IP Netlogon requests. RESOLUTIONTo resolve this issue, "unbind" Client for Microsoft Networks from the IPX/SPX protocol on the Windows 95/98 client:
MORE INFORMATION
When the PDC is configured for both TCP/IP and the IPX/SPX compatible protocol, the PDC responds only to the first Netlogon request it receives, regardless of other protocols configured on the server. Because the IPX/SPX Netlogon request arrives before the TCP/IP Netlogon request, the server responds with an IPX/SPX type 20 broadcast. By default, the RAS server does not forward IPX/SPX type 20 broadcast packets to the client unless two-way broadcasting of type 20 packets (NetBIOS over IPX) is enabled on the RAS server.
Q173607 Client Not Authenticated by Domain Through RAS Member ServerAuditing successful logon and logoff attempts at the PDC shows the user successfully logged on, and a Network Monitor capture shows the IPX/SPX Netlogon requests arriving first. Additional query words:
Keywords : |
Last Reviewed: July 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |