W2K Logging in issue

[Gabriel2010]

Hello,
After applying all the latest updates to a Windows 2000 professional system (via Windows Update), when user logs in to domain, it takes a while to fully get his desktop. User logging in to domain & about 10 computers.
Looks like something broke.
Thanks for any ideas guys


Glad to be here!

 

[ChicagoTechNet]

quoted from

http://www.chicagotech.net/

Slow logon to windows domain

Possible solutions:
1) check DNS settings.
2) It is better to use its using the same DNS as the server i.e. local DNS not internet DNS.
3) Check for logon scripts for any errors.
4) Check Event Viewer for any errors, especially GPO's errors that could be causing the delay.
5) Check any errors on event viewer.

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[Gabriel2010]

Thanks!
Unfortunately, I have no access to Event Viewer logs as I trying to help a friend.
An LMHOST & host file were created & it seems to be working fine. Also, netbios over TCP was enabled.
Thanks agaiN!

Glad to be here!

 

[1101001100110101]

does your friend have folder redirection/roaming profile enabled? if so it could be configured incorrectly and is caching more information then needed to the server. everytime he tries to login it has to re-load all the data and settings.

 

[coffytan]

I face this problem long time ago, then solution i used was on the hosts and lmhosts files. However, recently, there are another pc faced this problem again. I had check on both the files and the content inside is accurate.
ChicagoTechNet, you mention to set the DNS to the domain DNS. However, if I do it this way, the pc will not be able to connect to internet anymore. What can I do so that the pc can connect to the internet as well??
Thanks.

 

[mlichstein]

ChicagoTechNet, you mention to set the DNS to the domain DNS. However, if I do it this way, the pc will not be able to connect to internet anymore. What can I do so that the pc can connect to the internet as well??"

You need to configure forwarders on the domain controller. Open the DNS console, right click on the server, properties, forwarders tab.

Enter the IP addresses of your ISPs DNS servers. Workstations on your domain should only point to your DNS servers hosting the AD zone (usually DCs). They should not have external DNS addresses at all, not even as secondary or tertiary name servers.