Discussion Locked

Multiple drive mappings.

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

I have an NT40,SP6a,WS. When the user logs, he gets drives that start mapping by themselves. They end up filling all drive letters, and sometimes overwrite existing drive letters that were mapped permenately by the user. How do I stop this from happening?

Bra-k

10 replies

by nicholasp

we need more info.
Have you tried logging into the same ws with a different userid?

There may be something wrong with this profile

by bra-k

This happens with any user that logs in, and also does not happen as soon as you login but over the course of the day it add more mappings.

by syscokid

I have frequently seen this happen when Microsoft FindFast is running. Try removing FindFast and se if that helps.

by nettek

Answer two is correct in that FindFast can cause this. Remove FindFast from the startup folder. Then go to Control Panel -> FindFast. Highlight each Index, and then from the Index menu choose Delete. Then select Close and Stop.

There may be another cause that was a known problem in NTWS SP4 and earlier. It can also be caused when someone searches for a file. If, when searching, the operating system comes across a shortcut that points to a network share it will automatically map a drive tothe share. Installing SP5 or 6a should resolve the problem.

by dbowlin

The find fast issue is common to this problem. Another cause can be the way document paths and shortcuts are made by NT. By default shortcuts are mapped to a UNC path, rather than the drive listed in the shortcut target. For some reason, even though an appropriate drive mapping exists, the UNC creates a new one. This can be prevented at the server with server policies. I don't remember the exact path to the policy, but the policy turns off UNC mapping on shortcuts, and makes the shortcut targets absolute the the actual drive mapping. I have found this policy extremely useful for load balancing as well. I have moved entire directories to different servers/volumes with this policy in force. Without this policy active, the shortcuts would look for, and fail to find, the file in the old locations.

Good luck,

This discussion is closed to new replies.