takes 15to 20 minutes to load personal setting in 1

[case27]

hello, please help
I make be overlooking a simple a solution, it takes 15 to 20 minutes to load personal setting in win2000 pro. once the end user has entered his or her password in order to login to the network. this is only happening to 3 of my end users out of 600, which are hitting the same server. I think i have tried everything, pinging, tracert, verified their accounts,network traffic, profiles and everything appears to be find. what am i overlooking?

 

[BIS]

DNS?

 

[ntwrkadmn]

Disconnect the network cable and log on, this will use the locally stored password. If the computer still takes awhile you know it's someting local on the client computer. Since others can log on and don't have the long wait time it's probably local. Have you compared settings with the computers that work? DNS or WINS, could be WINS because it's a local nertwork. Check DNS also.

 

[case27]

thanks I'll try that.

 

[ntwrkadmn]

Something else to consider, what services are starting at startup? An engineering department I support doesn't use NAV because it doesn't work with the software they use to test IC chips but McAffee works fine. After log on go to task manager and see what process is taking awhile to load.

 

[ntwrkadmn]

Is there any application log files reporting an application hanging, check event viewer. Sometimes you'll see a report about an application hanging. Also check system log files.

 

[case27]

Yes, I checked the application log file and error stated, windows cannot determine the user and computer name.

 

[chriseubank]

Have you tried cleaning out all of the temp folders, internet history, cache, etc?



Chris

 

[case27]

yes, done that

 

[ntwrkadmn]

Try this, delete the computer account in AD, also place the computer in a workgroup. Recreate the computer account in AD and add the computer back. Sometimes the SID on the computer becomes corrupt and the server and computer have a hard time communicating.

Also check the "Enable Netbios over TCP/IP" in the WINS settings or the default "use NetBios from DHCP server".

 

[case27]

it worked thanks ntwrkadmin