Discussion Locked

Win XP slow to log to a Win NT 4 server

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Currently we have connected about fifty pc's running windows xp to a server which is running windows nt4. When logging in to this server the windows xp machine is very slow and sometimes fails to log in. Trying to open a folder in this server is also a nightmare.

Can someone help me with this problem because my users are really frustrated with it.

Thanks

God Bless

2 replies

by quintar51

Hi,

Do you have WINS installed on the Server?

Win XP clients use DNS to resolve names, but when on an NT network, which doesn't use DNS as its primary name resolver, you'll need a WINS server.

Once you installed the WINS service on the NT machine, you'll need to configure the TCP/IP properties of all your XP clients to use the same server as their WINS server.

take a look here for more info:
https://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winntas/tips/techrep/wins.asp

by rsanchezp

U may want to try the following situation. This is a familiar problem on a Windows 200 Server or XP Domain as well.

CHeck the following link that I have found through my research

You may experience extremely long delays (up to 5 minutes) when logging into domains using Windows XP Pro. This is caused by the asyncronous loading of networking during the boot up process. This speeds up the login process in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready.

To disable this "feature" and restore your domain logons to their normal speed, open the MMC and add the group policy snap-in. Under Computer Configuration-->Administrative Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED.

This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command,non-XP systems will ignore it in a domain distributed group policy.

This discussion is closed to new replies.