Re: 2min or more delay longing on to domain with XP Pro SP2

Tech-Archive recommends: Fix windows errors by optimizing your registry



When you say that things changed with the fast logon optimization disabled,
and that it just greys out the logon dialog, I have to say this feels more like a
basic network issue than any AD configuration problem. Certainly not DNS,
certainly not Kerberos, time sync, machine account, etc. All of these exhibit
different symptoms that what you're reporting.

First eliminate the usual suspects: what comes to mind immediately in
no particular order are: malware infections, parallel Netware client, 3rd-party
firewall, VPN client software, corrupt WINS or bad WINS IP, nonsense in
HOSTS/LMHOSTS. You may be able to grind out a few more. I'd also
do a "netsh winsock reset" just to be safe.

Next, you can try backing out the recent critical updates or hardware
driver updates. If you have a restore point before this started happening that
might be the easiest way.

After ruling out any of that I'd probably next try simply installing a different
model/mfr NIC (which gets you a different driver), tie the workstation to a
different switch port and see what happens.

If that doesn't lead to a solution, try installing a clean XP SP2 to a
different folder, join that to the domain and if it works OK, build
it up to the existing config. with updates, s/w and configuration. At some point
you'll find the cause of the problem.

The alternative is to put in a sniffer or capture traffic and deconstruct what
is going on. This is too painful to really contemplate at this point.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.

"Enkidu" <enkidu.com@xxxxxxxxxxxxxx> wrote in message news:42faf9a6$1@xxxxxxxxxxxxxxxxxxxxxx
> geodas wrote:
> >
>> I enter the password, click "OK" and the login prompt sits
> > there grayed out for over 2 min.
>>
>> I have tried disabling the fast login option using the Local
> > GP. When I did that and shutdown and rebooted twice it took
> > over two minutes to even get the otpion to logon. It simply
> > sat there initiating the network and computer policies etc.
>>
>> I have tried removing and re-adding the PC account with no
> > success either.
>>
>> As for logging, do you simply mean EVENT Viewer logging or
> > apps in general. I have verified that no other app is logging
> > any info.
>>
>> DNS seems to be working since I am able to access anything
> > I need on the network including the Sysvol.
>>
>> My suffix search order list shows the domain my PC account
> > is a member of first and then the root for our enterprise.
> > I have a total of 6 entries in my DNS suffix search order
> > for various domains.
>>
> In the NICs what is the DNS information? Do you supply the DNS server information by DHCP?
>
> Cheers,
>
> Cliff
>
> --
>
> Barzoomian the Martian - http://barzoomian.blogspot.com


.



Relevant Pages

  • Re: Domain name at logon differs from the name of the domain
    ... In DNS manager right click on the zone, and look at "Allow Dynamic Updates" ... > but attempting to logon to it brings the error "no domain ... >>NetBIOS domain name, as this is part of SAM logon name. ... >>Microsoft MVP Windows Server - Active Directory ...
    (microsoft.public.win2000.active_directory)
  • Re: Please wait while the domain list is created
    ... Delayed logons are often a dns issue in that the computer is having a ... that W2K/XP Pro domain computers point ONLY to domain controllers running ... netdiag and dcdiag should be helpful to you. ... policy that can cause very long logon times and/or logon failures. ...
    (microsoft.public.windows.server.networking)
  • Re: Event 5774 /DNS errors/Latest updates
    ... it too is handling DNS as well as all ... Upon a reboot, the FIRST ... Subsequent logon by other workstations are all doomed. ... the commands you ...
    (microsoft.public.win2000.dns)
  • Re: Event 5774 /DNS errors/Latest updates
    ... > Yes, this is a router. ... it too is handling DNS as well as all ... all clients or disable DHCP on the router and configure DHCP on the server ... Subsequent logon by other workstations are all doomed. ...
    (microsoft.public.win2000.dns)
  • Re: GPO only applies after gpupdate /force
    ... Logon in client workstations. ... Windows 2000 clients, in that Windows XP waits for the network to be fully ... 305293 Description of the Windows XP Professional Fast Logon Optimization ...
    (microsoft.public.windows.server.sbs)