All clients now login to my 2003 Active Directory. All
the XP clients have the most recent SP installed too.
I did some surfing last night and found some info about
this problem. The fix recommended stopping the WebClient
service. After stopping this service the initial delay
seems to have disappeared.
Anyone have any more info about this issue? Why it
occurs? Is there a timeout "ticket" setting for XP
clients using active directory? Is there a new security
feature in XP that causes this (encryption, IPSec?)?
Any additional info is much appreciated!
Woody
>-----Original Message-----
>Do the clients log on to the win 2003 domain?
>If not then try following:
>WinXP by default tries to contact domain controller
>for authentication, while connecting to a mapped network
drive
>and if the client has not logged on to the domain, it
waits for about 30
>sec. time out, before connecting the network drive.
>This problem is solved in the WinXP service Pack,
>Appling the SP to win XP clients may solve this problem.
>
>Sharad
>
>"Woody" <(E-Mail Removed)> wrote in
message
>news:03fb01c3ce56$3f6663d0$(E-Mail Removed)...
>> Hello,
>>
>> I recently moved a Win 2000 file server into my Win
2003
>> Active Directory domain. Ever since moving the file
>> server my Windows XP clients experience an initial
delay
>> when they try to connect to the mapped drives on the
file
>> server. The delay is for about 25 seconds and then the
>> clients can browse the directory structure at normal
>> speeds. I've noticed that if the client doesn't connect
>> to the drive within 20 minutes or so and tries to
>> reconnect the same delay transpires. Reconnects within
>> the 20 minute windows do not experience the delay.
>>
>> This problem is not happening on my 2000 and NT
>> workstation clients.
>>
>> I think it might have something to do with the Local
>> Security Settings and a time out setting?
>>
>> Has anyone seen this problem and know of setting that
can
>> corrects the initial delay (authentication?)?
>>
>> Thanks!
>>
>> Woody
>
>
>.
>
|