Delayed logons are often a dns issue in that the computer is having a
problem finding a domain controller and may be ultimately logging on with
cached credentials. I would verify that your dns is configured correctly in
that W2K/XP Pro domain computers point ONLY to domain controllers running
dns and having the AD domain zone as their preferred dns servers. ISP dns
servers in the list can often be the cause of delayed logons as the computer
tries to locate the domain _srv records on it. The link below explaines
proper dns configuration in an Active Directory domain.
http://support.microsoft.com/default...en-us%3B291382
Another possibility is there is a problem with domain controller or
controllers in their dns configuration and/or replication. The support tools
netdiag and dcdiag should be helpful to you. I would run first netdiag and
then dcdiag on your domain controllers looking for any failed
tests/errors/warnings that may help pinpoint the problem. Netdiag can also
be used on domain member computers. In particular look for failed
tests/warnings/errors for dns, dclist, kerberos, and trust/secure channel.
Also check the Event Viewer of domain controllers and domain computer for
any pertinent errors and try to ping the domain controller, preferred dns
servers from the domain client by IP address and fully qualified domain name
to establish basic connectivity. If you have enabled an require or request
ipsec policy in your domain without exempting domain controllers from the
policy that can cause very long logon times and/or logon failures. The
netdiag test will show if an ipsec policy has been assigned. The /v switch
will show much more detailed info for netdaig and dcdiag if problems are
found. --- Steve
"OLSH College" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Your response is correct but does not solve my problem.
> Firstly if I do just re-hit ctrl+alt+del each time it does go away but it
> then often takes an exteneded amount of time to complete the logon process
> so does not save time overall and sometime it will just not logon at all.
> It seems better to wait for whatever it is doing during the "Please
> wait...." and then logon normally.
> More importantly I did not have this problem in the past. And now that I
> do
> have it Syamantec Ghost also seems to have problems automatically joining
> imaged clients to the domain - so I suspect the issues are realted.
>
> Thank you for your response but I would like to get to the bottom of what
> is
> actually occurring.
>
>
> <(E-Mail Removed)> wrote in message
> news:5Vtbd.3550$(E-Mail Removed) t...
>> the "domian list being created" is an annoying bug in xp. as soon as you
> see
>> the message hit ctrl+alt+del, that will get rid of the message. now when
> you
>> select the domain you might see it again... hit ctrl alt del again, logon
> to
>> the domain, and it shouldnt happen anymore
>>
>>
>> "OLSH College" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > Hi.
>> >
>> > recently whenever I join a client to the domain it seems to work fine
>> > until
>> > the required restart.
>> > At this point when I try to select the domain to logon to (as opposed
>> > to
>> > the
>> > local PC) I get the message is a small window "please wait while the
>> > domain
>> > list is created".
>> > This can take quite a few minutes to go away but then the drop down
>> > list
>> > is
>> > still showing the local PC, when I drop it down and click the domain
>> > (there
>> > is only one) the same message appears again. Again it take from a
>> > couple
>> > to
>> > like 10 minutes to go away and then I can continure to log on fine.
>> > If after restarting the PC I just leave it for 5 or 10 minutes before
>> > trying
>> > to logon to the domain it seem to be fine - that is, it does not show
> the
>> > message at all.
>> > After logging into the domain the first time this message does not
> appear
>> > again - I can select the local PC or the domin just fine.
>> > This did not happen until recently and I don't think anything
> siginificant
>> > about the domain or the network has changed.
>> > I am concerned that it is pointing to something going wrong somewhere.
>> > Also Ghosting from the console now seems to have trouble joining
>> > clients
>> > to
>> > the domain - 3/4 will fail - but not all! I suspect that the issues may
> be
>> > realted.
>> >
>> > Any thought?
>> >
>> >
>>
>>
>
>