Slow Browsing Mapped Drive

[Guest]

I have a problem that is making me crazy. I can access a mapped drive held
on a server and everything works fine. If the mapped drive is idle for about
10 minutes, then I go to browse the drive, I can open it, but as soon as I
open a subfolder or any file there is approximately a 10-15 second delay.

And... I feel if I hear one more suggestion about a misconfigured antivirus
program or installing Windows updates my head just might explode. Obviously
Explorer is performing some background process on the network share. I would
like to know what function it is performing and how on earth do I disable it.

Here are the facts:

Workstation: Fully patched Windows XP Pro SP2. (Antivirus program disabled)
Server: Fully patched Windows 2000 Server SP4.

Thanks,
Ryan

 

[Guest]

NET USE shows the shares are disconnected. After investigating further, it
looks like I can change the time for autodisconnect on the server using the
NET CONFIG SERVER command... defaults to 15 minutes.

Why is it taking so long to connect to the shares, then?

 

[Guest]

RESOLVED

Forgot to mention, I have the Netware Client installed (v. 4.91).

I performed an Ethereal trace while mapping a network share drive.
Workstation did a DNS lookup first, then performed a bunch of SLP lookups.
The SLP lookups took approx 12 seconds, then finally the NBNS lookup to our
WINS server where the computer name resolved.

The SLP requests were being sent to 224.0.1.22 (the multicast address), so I
checked the SLP settings in the Netware client. Under Advanced Settings, SLP
Active Discovery, I turned it OFF. This prevents the WS from performing SLP
multicasts.

I rebooted and tested again... now everything seems to be mapping and
connecting fast on both sides (Netware & MS).