Discussion Locked

Additional Drives (F:\) being Generated!

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running Win NT Workstation 4.0 on an NT Server running BackOffice and NT Server 4.0. Throughout the day additional network drives are being intermittently generated on several NT Workstations. (G:,H:,I;,J:.....etc)These drives do not exist on my server. What is causing this? Bad Hub?(am using twisted pair)Bad NIC? Software? This does NOT happen on Win/95 workstations.

11 replies

by cmurphy-mcse

I had this same problem a little while back. My problem was with word and excel 97, when the user went to use a template off of the assigned network drive it would create a new drive letter just as it is happening to you. What i did was apply the latest service pack and ran a patch for word and excel and it worked fine after that. You can find the patch for word and the latest service pack on microsofts website.

by syscokid

One culprit may be Findfast. If it's in your startup folder, delete it, and/or disable it in Control Panel.

by dbowlin

This is partly a service pack issue, and partly a design issue.

Shortcuts set up on NT are set up with a UNC path embedded in the background. For example, say you have a shortcut for a document on your F drive and the path in the shortcut is f:\documents\word.doc, and the F drive is located on NTSERVER1, the shortcut will be actually set up to \\NTSERVER1\documents\word.doc. There is no way to edit this at the shortcut level. Since the shortcut is actually using the UNC path to find the file, another drive may be set up on your computer to satisfy the UNC call. I personally prefer my paths to be absolute, not UNC, I find it gives me more control. In order to make the shortcuts follow the path they were given follow these steps:

Start System Policy Manager on your PDC.

Enable: Default User\Windows NT Shell\Restrictins\Disable Link file tracking

After setting your policies and deploying them properly on your PDC and BDC's and your users log off and back on their pathsshould follow the drive letter paths rather than UNC and the problem of random drive creation should go away.

Microsoft has a series of articles on this issue, and how to use the policy editor as well as other solutions. Check out article Q158682 in the MS knowledge base for more info and links to other explanations.

I hope this helps, good luck.

by blitzer

Hi,

Combine previous posts and you should fix your problem, the way we resolved ours was, added a registry entry which disables the use of UNC, you can also do this through Pol.Ed., and a must, apply SPK5, up to you if you want to go onto SPK6.

Daniel.

This discussion is closed to new replies.