Authentication process extremely long...

[Guest]

Authentication process after the password has been entered when logging on to
Windows XP Pro in a domain environment can take up to several minutes instead
of the instant logon you would expect!

I only have a problem with one computer in the domain and it does not matter
if the computer is connected to the network or not. Once logged on after
several minutes of waiting I can log off and then log back on again and then
it will authenticate instantly!?

If I logon using the same user name but on a different computer the logon
process is instant, which would suggest there is a local problem on that one
specific computer!

Any suggestions on how to troubleshoot and fix the problem? The computer is
running Windows XP Pro with SP2 and all the patches in a W2k server
environment with all the patches as well.

Thanks,

Adde

 

[Malke]

Authentication process after the password has been entered when
logging on to Windows XP Pro in a domain environment can take up to
several minutes instead of the instant logon you would expect!

I only have a problem with one computer in the domain and it does not
matter if the computer is connected to the network or not. Once logged
on after several minutes of waiting I can log off and then log back on
again and then it will authenticate instantly!?

If I logon using the same user name but on a different computer the
logon process is instant, which would suggest there is a local problem
on that one specific computer!

Any suggestions on how to troubleshoot and fix the problem? The
computer is running Windows XP Pro with SP2 and all the patches in a
W2k server environment with all the patches as well.

Check the DNS settings on the workstation. Long login times are
generally because the DNS is set incorrectly. The server should only
look to itself for DNS with a forward lookup set for Internet access.
Workstations should only look to the server for DNS.

If DNS is set correctly, look to see what network resources the
workstation tries to automatically connect to. The resource may be set
incorrect on the workstation - or not exist - and this would cause a
timeout.

Malke