Re: Authentication process extremely long...



Adde wrote:

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
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User
.



Relevant Pages

  • Re: Event 533: User not allowed to logon at this computer
    ... When this happens see if only that user is unable to logon to the "domain" ... or this happens to all domain users trying to logon from that workstation. ... computers are configured correctly for dns and have network connectivity to ... netdiag and dcdiag on the domain controllers and check Event Viewer on both ...
    (microsoft.public.security)
  • Re: Slow logon Windows2000
    ... Can you create new user account in domain and try to logon with it to ... Do you have this problem only on one Windows 2000 computer or all Windows ... >> Application logs? ... >>>> Slow logon problems are usually related to DNS miss configuration. ...
    (microsoft.public.windows.server.general)
  • Re: Name resolution issues on W2K Pro
    ... Workstation 1 can not resolve any names on the internet. ... > able to ping the router and the ISP's 2 DNS servers. ... > the windows client fixed this. ... Which Windows client are you talking about here? ...
    (microsoft.public.win2000.dns)
  • Re: Domain not available
    ... this is a Windows 2003 Server. ... It also appears that my DNS is hosed on the ... The workstation can log in IF it is rebooted and you immediately log in. ... computers on the network, and if you cannot determine that it is set ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... the logon locally or deny logon locally user rights in a domain level Group ... the computer is configured correctly as far as DNS in that it points only to ... domain controllers as it's preferred and secondary DNS servers in tcp/ip ... myself out of a Win2K Pro workstation by messing around with a Group ...
    (microsoft.public.win2000.security)