XP and server 2003

Been trying for a while to solve an issue where a host
running XP SP1 connecting to resourses on a Win2k or
Win2k3 server takes about 20-25 seconds for the requested
resouce to become available. E.G., XP host hits a folder
in Windows Explorer, and contents of folder do not show up
in right pane for 20-25 seconds.

Anyway, the problem cleared up last week for all XP hosts,
and the only change I made to the server was a setting in
DNS. I changed it to accept only secure updates, where it
had been set to accept secure and nonsecure. Coincidence,
or could this have been the cause of the problem? If so,
please explain how.

Hello,
I don't see how setting DNS to secure updates only would have made a difference here, but I guess everything is possible.
Please check the following KB article for some other possibilities:
Files on Network Shares Open Slowly or Read-Only or You Receive an Error WGID:374
ID: 814112
http://support.microsoft.com/?id=814112

--------------------
>From: "Rich Long" <(E-Mail Removed)>
>Sender: "Rich Long" <(E-Mail Removed)>
>Subject: XP and server 2003
>Date: Mon, 26 Apr 2004 13:01:34 -0700
>
>Been trying for a while to solve an issue where a host
>running XP SP1 connecting to resourses on a Win2k or
>Win2k3 server takes about 20-25 seconds for the requested
>resouce to become available. E.G., XP host hits a folder
>in Windows Explorer, and contents of folder do not show up
>in right pane for 20-25 seconds.
>
>Anyway, the problem cleared up last week for all XP hosts,
>and the only change I made to the server was a setting in
>DNS. I changed it to accept only secure updates, where it
>had been set to accept secure and nonsecure. Coincidence,
>or could this have been the cause of the problem? If so,
>please explain how.
>

--
Sergio Moreno
Microsoft Windows Networking

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.