Multiple drive mappings appearing during the day

[adilley]

I have an intermittent problem that affects some PCs, some of the time. Each PC runs a login script that sets up various common mappings. Over the course of the day however, some PCs then replicate these standard mappings across the remaining letters of the alphabet.

For example, the login script sets H drive to be a common drive, using the following command:

net use h: \\swnt1\data /persistent:no

The problematic machines will also have

o: \\swnt1\data
p: \\swnt1\data
q: \\swnt1\data

etc, taking up all remaining available letters.

Has anyone seen/fixed this problem before?

thanks in advance
Andrew

 

[grimmy]

Andrew,
Yes we had this program a long time ago and do not have it any more but I cannot quite remember what the fix was. I take it that you are running NT4. What version of Service Pack are you running on your clients?

Cheers....grimmy

 

[Whitemtntn]

Did anyone ever map those letters to that directory? Maybe awhile back, without the /persistant:no switch? Perhaps they were mapped when someone was sitting at those PCs.
You can try adding to the beginning of your logon script...

net use * /d /y

to make sure you are starting fresh. This will delete any mappings that are lingering.
-WhiteMtntn

 

[Julie1967]

I had this problem, but not with a logon script. I installed office 2000 to run from network using office 2000 on my nt server(run from network) I installed office on workstations from administrative share on NT server using mapped network drive. I had mapped
E: \\server\office admin point. The problem is evertime I opened word, outlook or excel from workstation I would get multiple mappings. f: \\server\office admin point
g:\\server\office\admin point.

I fixed this by re-installing office 200o on the workstations using the unc name instead of the letter drive mapping. I did this by going through network neighborhood to install office 2000 instead of installing it through the mapped network drive. tHis is a problem with NT see following: article in microsoft: Q150604 (do a search for it)