Discussion Locked

win XP login too long on a 2k server

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

I have a windows 2000 server providing DNS and shares (plus centralized backups, web server and a few other services),on a small LAN which also has net access through a router+cable modem. (It's a public school with 4 computer sciences classrooms and about 50 PC's)
Everything works fine on the domain IF the workstations have win95 or 98 or ME installed.

If I move any PC to winXP pro, I give up waiting for the machine to log on to the server. (although everything else on the networks keeps working just fine)
The messages "logging on to server" , "validating user", "accessing network shares", are well over 5 minutes apart from each other.

I've browsed MS knowledge base searching for "problems accessing win 2000 server from a XP workstation" but to no avail.

Perhaps it's too obvious and I just can't see it.

I really need for academic purphoses do upgrade the clients. Any suggestion?

8 replies

by ctmoore1998

I'm betting that when you change the PC to XP that you are using the same name as the old PC this will result in the problem that you are facing. You must manage your 2000 DNS and WINS if you want to do this 'flushing' them of the old system info, or change the name of the XP system slightly such as workstation1 becomes wkstation1 or some such. To do this on existing XP first remove them from the domain as their old name,join a workgroup then rename the workstation,reboot again then go throughthe network wizard to rejoin the domain this should fix the slow login problem. (this can also occur to XP machines that were fine logging on then sp1 is installed and the loggon becomes excessive I would remove the machine from the domain install sp1 then rejoin the domain to prevent this problem)

by ntproenca

I'm going to try it anyway.
But I don't think that's the answer.
New teachers at the school log on the server with laptops with Win XP (i.e. machines that never logged on to the server) and the same problem occurs. They just configure the domain name, etc., and the gateway address to get internet access and they have the same problem.

I found an article on MS site saying that if your domain on the server did not end with a correct TLD that would "confuse" XP clients and they would indeffinately browse the network looking for the server with the TLD DNS. But this is not the case.

Can I do a full trace of the log on to the domain process, both on the client and on the server?

by justanadmin

I could be a problem relating to name resolution. Here are a couple of things I would suggest trying.

1. Create an lmhosts file on one of the XP machines (located in C:\\system32\drivers\etc). In the lmhosts file, make the following entry, substituting your domain controller information.

192.168.1.1 my_dc #PRE #DOM:

#PRE #DOM:

2. Run a packet sniffer such as Ethereal (which isfree) and see what sort of packets are being sent out on the network during the log on phase. This may give you a better idea of what is happening during the delay.

Hopefully one of these options will help! Good luck!

by ntproenca

What didn't help me was to climb the networking ladder to make things better and then having to go downstairs to use an old and slow process to make things work.
Thanks Microsoft.

This discussion is closed to new replies.