Slow User Login to domain

[ew456]

I have several labs of computers reporting to one domain controller. It is a windows 2000 server domain controller. We have users that login to the workstations. These users are not admins and the user policy is set so that these users are very restricted (ex. no access to C:/ or desktop). The only reason we have user logins is
1. so we know what user is logging in to a computer
2. Each user has a shared folder that only they have access to and can store files. We map to this folder

We absolutely have no reason or need for a personal my documents, etc. or anything else that comes with a user profile. The problem we have is that we don't have extremely fast machines, but they are 900 mhz machines, but the login time for these users, especially if they haven't logged into that computer previously, is a long time (sometimes 3+ min). After login the computer runs normally and is fast. Is there any way to shorten this login time. Any hints or suggestions will be very much appriciated. Keep in mind we don't need a local user profile for really any reason is there a way we can get rid of that? The users profile according to a win2k workstation is only somewhere around 512kb, so why is it taking so long? We are planning to goto win2k3 server this summer if that can help at all. Thanks in advance.

 

[nsantin]

Slow logons are typically due to DNS issues not user profiles.

 

[ew456]

Thanks for the reply. So are you saying that it should definately not take 3+ min. to login? Like is said, after the initial first time login, it usually takes about a min. to login.

 

[Seaspray0]

One source of delay:
Check the DHCP for a setting that automatically registers the computer in DNS. You only need that setting for computer OS's that don't do this (NT, 95, et). If the DHCP does this, then the security on the record belongs to DHCP. When the client follows and attempts to register as well, it can't. This can cause a delay.

Another source of delay:
Your DHCP hands out more than one DNS server to use and one of these belongs to your ISP. You should always point your clients to your DNS servers and let your DNS server forward to the ISP for internet resolution. The reason is because your ISP's dns server doesn't host a secondary of your corporate dns zone.


Start, Help. You'll be surprised what's there. A+/MCP/MCSE/MCDBA

 

[nsantin]

The first time an account logs into a computer for the 1st time it will take a little longer to create the user profiles and such. Afterwords it should be quick. You can also speed this up if you use a Mandatory profile which gets loaded instead of having windows create a new profile for the user accounts

Like Seaspray0, make sure you have configured your network to ONLY use your server as the DNS server. Setup your ISP DNS server as a forwarder on your local DNS server on your server.