Windows 2000 Pro Hangs after login

[sirbrakness]

Here is my problem. I installed Windows 2000 Pro on my user's laptops (IBM Thinkpad T-23) when they are connected to the network they can login just fine. However, when disconnected from the network they can login but it will take 3 - 5 minutes for the desktop to appear. I am not really sure why this is happening. Most of my laptop users can logon remotly fine without issue but two of these types of situations have popped up. Please if anyone can point me in a direction it would be much appreciated!

 

[Firm]

Are they using a docking station when logging on to the network?

 

[echoecho]

At what point is it taking the longest. I have found that when my laptops are off the network it takes a while at applying security settings.

 

[pbxman]

Yeah - it sounds like they are trying to loginto the domain when they are not connected to it...so DHCP fails, and they end up using their cached credentials. In that case - you have a few options, but i'd create a local "undocked" account for them to loginto when not on the network. This is very simple to do, and when they logon at CTRL+ALT+DEL - instead of choosing the "domain" under their username/password - they can choose the actual PC name to loginto instead.

There are other ways to do this, but I believe this is one of the easiest.
Pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[sirbrakness]

All of my remote users have local profiles. When they are off my network they login using their net user name and passwords and they do not change their domain name. They are fine with that login process. This is only occuring on three machines, two IBM Thinkoad t-23 and a thinkpad 700? I am boggled. They are docked at work and undocked at home!

>Corey

 

[sirbrakness]

AH I Found the issue. There is a program we use called PCOM. For IBM Sessions. It is causing this error. Thanks for the help. . .going to resolve this now!

>Corey