Article ID: 151744
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Network Client 3.1
This article was previously published under Q151744
SYMPTOMS
A Network Client 3.0 computer cannot communicate with a Windows NT server using NWLink as the only protocol. A trace shows that the server does not respond to any client requests.
CAUSE
Assuming that IPX/SPX has been loaded on the server, the problem may be related to direct hosting. To communicate with a Windows NT Server by means of NWLink (IPX), the Network Client 3.0 needs direct hosting enabled on the server. This is normally enabled by default, but can be disabled.
RESOLUTION
Enable direct hosting at the server.
- In Control Panel, double-click the Network icon, and click Bindings.
- Select the Server.
- Either:
- If the line "Server->Nwlink Ipx/Spx Compatible" (without quotes) is there but disabled, select the line and click Enable. Click OK and quit Network Settings.
- If the line is not there, remove and reinstall the IPX/SPX compatible transport. This will enable direct hosting by default.
Alternatively, remove NWLink on the client and use another protocol.
Keywords: KB151744
