When a certain user navigates to a client folder on a mapped drive (R:, for example), Explorer will pause for about 15 seconds before displaying any contents. Then, once it does display the subfolders, the hourglass will pop up constantly every 3 to 5 seconds and stay like that (which will hang) for about 2 seconds. It is almost like it is polling the contents of the drive, but no one else is experiencing this. We've even gone to Tools/ View/ Advanced settings and unchecked the setting that says "Automatically search for network folders and printers", but no luck. I've read other threads, but we don't have PGP service running, nor the WIA service running, and we have run Spybot, Hijack This, and ran a Norton scan, but nothing. Any ideas? Thanks!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Windows Explorer Hangs on a Network/Mapped Drive 1
- Thread starter mdcr
- Start date
-
1
- #2
Open the registry editor.
Go to
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace
Export this key (in order to back it up, just in case) and then delete the key called:
{D6277990-4C6A-11CF-8D87-00AA0060F5BF} (Task Scheduler).
Close the registry.
Go to
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace
Export this key (in order to back it up, just in case) and then delete the key called:
{D6277990-4C6A-11CF-8D87-00AA0060F5BF} (Task Scheduler).
Close the registry.
- Thread starter
- #3
Followed those instructions, but it did not help. Thought the problem might have been on the server side, but no other users are having this problem. User has no non-existent network drives that are still mapped, no non-existing printers, login script reconnects that client drive every morning....
Follow every linked article here:
My first action would be to either update the drivers for the network adapter, or replace it.
My first action would be to either update the drivers for the network adapter, or replace it.
- Thread starter
- #5
Possible resolution (working so far at least):
We updated the driver, or, more aptly, re-installed a driver from the NIC's manufacturer website, and went back into that network drive - no hourglass. In retrospect, was the NIC constantly requesting information, and because the folder was so big (60Gb), it was more noticeable than on other drives/folders? Don't know, but it looks to be fixed so far...Thanks bcastner
We updated the driver, or, more aptly, re-installed a driver from the NIC's manufacturer website, and went back into that network drive - no hourglass. In retrospect, was the NIC constantly requesting information, and because the folder was so big (60Gb), it was more noticeable than on other drives/folders? Don't know, but it looks to be fixed so far...Thanks bcastner
mdcr,
Upgrading the NIC driver was absolutely the first thing to try. And sourcing the driver from the chipset manufacturer rather than the OEM gladdens my heart. For both wired and wireless I buy chipsets and ignore the OEM reseller branding.
Two links, and a last thought. The toughest customers out there for NICs are the peer-to-peer folks. I always watch the file sharing forums to identify future issues. See if any of the following may help you in the future or others:
Last thought: if behind a NAT router, keep its firmware absolutely up to date.
Best,
Bill
Upgrading the NIC driver was absolutely the first thing to try. And sourcing the driver from the chipset manufacturer rather than the OEM gladdens my heart. For both wired and wireless I buy chipsets and ignore the OEM reseller branding.
Two links, and a last thought. The toughest customers out there for NICs are the peer-to-peer folks. I always watch the file sharing forums to identify future issues. See if any of the following may help you in the future or others:
Last thought: if behind a NAT router, keep its firmware absolutely up to date.
Best,
Bill
- Status
Similar threads
