Win 2000 slow logon to domain

[ET]

Hi,

Our company has recently installed a number of new computers with Windows
2000 Professional installed. After pressing Ctrl-Alt-Del and enter his/her
password, it took more than 2 minutes for the desktop to appear. However the
same user can logon using some older machines and the logon time is quite
fast (may take a few seconds).

Would anyone know what is wrong with the new machines? Would it be a setup
problem?

Thanks.

 

[Pegasus \(MVP\)]

Hi,

Our company has recently installed a number of new computers with Windows
2000 Professional installed. After pressing Ctrl-Alt-Del and enter his/her
password, it took more than 2 minutes for the desktop to appear. However the
same user can logon using some older machines and the logon time is quite
fast (may take a few seconds).

Would anyone know what is wrong with the new machines? Would it be a setup
problem?

Thanks.

You don't say if you work in a workgroup or in a domain environment.
If it is the latter then I suspect that the DNS settings in your IP
configuration are incorrect. The new machines have trouble locating
the domain controller.

 

[ET]

Yes it is logging into a domain environment. And from time to time users are
unable to see their mapped drives (using net use to map) and I have to do
either of the following:
use net use to map again; or rejoin the domain using the same computer.

However when I look at the ipconfig /all the settings are all ok. DNS server
is pointing to the one we have, and using ping command I can ping the DNS
server. Is there any way to trouble-shoot this problem?
Thx again

 

[Pegasus \(MVP\)]

When you have the problem on a particular machine, run
this command from a Command Prompt:

net user ET /domain

If the machine has a problem reaching the domain controller
then this command will be very slow to run, or it will fail.

You can execute this command even before somebody logs
on, by hopping on to the problem PC with psexec.exe
(www.sysinternals.com).

 

[ET]

Thx. Will try it.

When you have the problem on a particular machine, run
this command from a Command Prompt:

net user ET /domain

If the machine has a problem reaching the domain controller
then this command will be very slow to run, or it will fail.

You can execute this command even before somebody logs
on, by hopping on to the problem PC with psexec.exe
(www.sysinternals.com).