Laptops have 5 network drives with the same names?!

irishluck

Member
We just started experiencing this about 2 months ago and so far only happen on two different computer.

We've got two network drives on our network. One is through my Desktop PC and another as a Portable Snap drive.

The computers get shut off every night before leaving. When they are turned on in the morning. When file explorer is opened, 2 of the laptops decide to put up 5-10 network drives with the same name but on different letters.

One of the network drives we have is called "publicshare1" on the w: drive letter.

The computer in our shipping room decided to make 9 more drives with that same name on different letters.

Ive got a screen shot of one that happened this morning.

Can anyone tell me why this is doing this?
This time it looks like it put a whole bunch of "IMAGES" in the public pictures folder.
 
Last edited:
Do you tell the drives to reconnect on logon? If so, try turning that off and see what happens, as it may seem to detect that the drives do not exist on the client when they actually do, and so make duplicates.
 
Do you tell the drives to reconnect on logon? If so, try turning that off and see what happens, as it may seem to detect that the drives do not exist on the client when they actually do, and so make duplicates.

I do beleive all of the computers (all 10) say to reconnect at login, but only 2 computers make multiple drives like that above.
 
Doing a quick google search, I found this:

If a file is trying to be accessed, it may duplicate network drives...
I have seen this behavior with NT4 so this may or may not apply...

The problem was a desktop icon for a program on a network drive. The drive
specified by the icon was not mapped or mapped to a different letter. Every
time the program was run it added a new mapped drive. Deleting the icon and
recreating it with the proper mapping solved the problem.

It seemed to be a bit of a bug in how NT resolved references to unmapped
drives - i.e. Icon points to S:\Program\Joe.exe, no S drive mapped, NT
"knows" that the share name is //server/programs/ so it maps that share to
the next available drive letter - G: for example - and then runs the
program. The next time the program is run, still no S drive maps H: and runs
and so on

It is most likely an application that is causing it from what I have read. What programs do you run that run files off of the network?
 
Back
Top