J
joar
One of the laptops at work uses appr. 2 minutes while trying to log on
to the computer when no network is present. The XP-client is a member
of a w2k-domain. Login when the domain is available takes virtually no
time (10 secs.). I realize that XP has to figure out that the DC is
not available, but the other 20 (or so) clients at work logs in at
about 30 secs. when no network is present. I've tried to statically
define both DNS (the one residing on the DC and the ISP) and WINS.
Nothing seems to help. We don't use roaming profiles. Two questions
for you folks:
1) Is it possible to speed up the process in which XP tries to
discover the DC?
2) What is the procedure XP follows when trying to logon? (I really
don't get why it takes so long for XP to discover that the DC is gone)
Thanks!
to the computer when no network is present. The XP-client is a member
of a w2k-domain. Login when the domain is available takes virtually no
time (10 secs.). I realize that XP has to figure out that the DC is
not available, but the other 20 (or so) clients at work logs in at
about 30 secs. when no network is present. I've tried to statically
define both DNS (the one residing on the DC and the ISP) and WINS.
Nothing seems to help. We don't use roaming profiles. Two questions
for you folks:
1) Is it possible to speed up the process in which XP tries to
discover the DC?
2) What is the procedure XP follows when trying to logon? (I really
don't get why it takes so long for XP to discover that the DC is gone)
Thanks!