Drive Mappings Ghosting 1

[Ealesie]

I have several machines running Window NT Workstation 4 - SP5 that during the day drives mappings appear unrequested.<br>
<br>
I am using login scripts to map three drives (NET USE command) to shares on the server, and by the end of the day some machines have 15-20 drives mapped to these same shares.<br>
<br>
Does anyone have any clues ???

 

[dxd]

Are all 3 shares being repeated?<br>
<br>
I have found that some applications may map drives themselves, regardless of whether the mapping is already there.<br>
<br>
If you are running an application that gets information from your network, whether it is database, documents, or whatever, I would begin my troubleshooting there.<br>
<br>
It would be very easy to determine. Once one of these apps is run take a gander at your drive mappings to see if there are any new ones.

 

[EuanPirie]

I had heard a rumour that this was related to having Administrator rights, do the users of these machines have that so that I can kill that theory? We had a similar problem and it was because all the users in question had admin rights.

 

[EuanPirie]

Thanks for your reply, but most of the users do not have Admin rights.<br>
<br>
Ealsie

 

[Lehtoant]

Several reasons: FastFind, UNC vs. drive letters..<br>
Check:<br>
<A HREF="

http://support.microsoft.com/support/kb/articles/Q150/6/04.ASP?LNG=ENG&SA=ALLKB&FR=0"

TARGET="_new">

http://support.microsoft.com/support/kb/articles/Q150/6/04.ASP?LNG=ENG&SA=ALLKB&FR=0</A><br>

<br>
Changing shortcuts to UNC helped me.<br>
<br>
Al

 

[Ianco]

Sounds like the NET Use command is mapping the drives &quot;persistent&quot;, which means that the PC remembers the connections so that the mapping does not have to be done next time the user logs on.&nbsp;&nbsp;Then, the user logs off sometime during the day and then logs back on.&nbsp;&nbsp;The persistent connections are automatically mapped to the previous drive letters, the logon script then maps 3 more drive letters and now the user has 6 drive letters mapped.<br>Could be?<br>Good luck<br>Ianco

 

[thorswolf]

I've had the same problem occur on our network. Throughout the day, one particular mapped drive would replicate itself ad nauseum for no reason whatsoever. In the end, we blew the contents of a key in the registry that controls persistent connections. It worked for us, may work for you. I'll try to dig up that key for you.<br><br>Yves

 

[Ealesie]

Thanks all for your help - the suggestion from link <A HREF="

http://support.microsoft.com/support/kb/articles/Q150/6/04.ASP?LNG=ENG&SA=ALLKB&FR=0"

TARGET="_new">

http://support.microsoft.com/support/kb/articles/Q150/6/04.ASP?LNG=ENG&SA=ALLKB&FR=0</A>

seem to have cured the problem (Office 97 find fast)<br><br>

 

[smcmilla]

I am also finding the same problem on a PC in my office. The user has WinNT 4.0 with SP6a and Office 2000. Removing findfast has not resolved the issue. Will try other options in the MS KB.

 

[SirLee]

The Findfast of Office 97 is something I never ever install again on any PC. The only thing it really does good is slow down the machine by half. Have you noticed that the Harddisk is constantly running if findfast is installed?

It might not be of the same impact as 3 Years ago but the slowdown can still be noticed with todays machines.