Win2K Startup Issues

[tel1jag]

Win2k Startup Help
I am having a strange problem with my Windows 2000 laptop. It has been happening for a couple of weeks now and I can't figure it out.

When I first boot and I am connected to a network, either mine at home, at work, or at a client the "Loading your personal settings" screen stays up about 5 minutes. This happens with a regular PCMCIA ethernet and a wireless ethernet card. Again, this happens on several different networks.

If I boot and my network cable is not plugged in, the machine goes right throught the "Loading your personal settings" thing in a few seconds. So this rules out profile size.

Also, I am only running TCP/IP and this happens on several networks so it can't be a PDC or DNS issue.

I had tried adding NETBUI which didn't help so I removed it.

Finally, this is a somewhat new problem and there has been NO new hardware added. Also, I have removed any new software added in the last few weeks. Also, I have completely removed TCP/IP and re-installed it.

I am running a Win2k SP3.

Any ideas? Cause I am stumped.


Thanks.

--Jeff

 

[wookalar]

Is your laptop a member of a domain? It sounds like it is looking for a domain server to get the profile from everytime you connect it to a network. When not connected, it simply loads the local profile on the machine. You could remove it from the domain, or if you need the domain to access one of your networks then it would be better to unplug the cable during bootup when connecting to the other networks.

 

[tel1jag]

The only troubling thing is that this, more or less, recent behavior. My system has not always taken so long. I would say that is started about 3 weeks ago or so.

Thanks for your reply and any other ideas would be welcome.

--Jeff

 

[Mrtony123]

I had the same problem with a laptop running W2K connecting to our W2k Server. Try uninstalling the TCP/IP protocol and the network client. Shut down and reboot the machine off the network with the cable disconnected, then reinstall the protocol and client. Shut down and reboot with the network cable reattached and back on the network. It fixed my problem. Something got corrupted in the protocol or client installation. Good luck.