Discussion Locked

"Phantom" Drive Mapping

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Win2K desktop system. One (and only one) network drive mapping, performed by the login script, seems to "clone" itself without my doing anything. When I log in I have one network drive mapped to a particular network share. By midday I mighthave four (all mapped to the same share, but with different, sequential drive letters). If I do nothing, by the end of the day, all of my "spare" network drives are consumed with this "phantom" drive mapping. I've had this happen before with a WinNTworkstation and had no solution then, either.

Any suggestions on a solution (and the cause)?

3 replies

by curlergirl

MS keeps claiming that this problem has been solved, but it still crops up once in a while. Turn off Find Fast - that usually fixes the problem. This is actually caused by the fact that the OS is so "smart" that when it tries to find a resource that requires a mapped drive, but the drive that is mapped is not accessible, it will map another drive letter automatically. You can force it NOT to do that by changing a registry key, if turning off Find Fast doesn't work:
HKLM/Software/Microsoft/Windows/Current Version/Policies/Explorer
ADD a Value: LinkResolveIgnoreLinkInfo
Data: 1

Hope this helps!

by rwyatt365

So far, no "phantom" mapped drives today (having turned off Find Fast). I'll give it another day, but I'd rate this a "success"

This discussion is closed to new replies.