Win 2K "Forgets" Networked Drive Mapping

  • Thread starter Thread starter Clueless in Seattle
  • Start date Start date
C

Clueless in Seattle

Why does Windows keep "forgetting" it's mapped drives?

I'm wondering if it's something I'm doing, or something being done by
some software I'm running. Or could it just be that Win 2K is, like
me, getting old and becoming forgetful? ;o)

I have just two computers, a desktop and a laptop, connected via a
peer-to-peer network.

The desktop is a Micron brand and the laptop is a Sony VAIO brand.

I've chosen the drive letters "M" and "V," respectively, to represent
the C: drives of the Micron and VAIO computers. So on the Micron, I
map the drive of the networked VAIO as V: and on the VAIO I map the
drive on the Micron as M:

Trouble is, the mappings only "stick" for a few days, and then one
morning, like this morning for example, when I boot up my computers,
one or both of the mappings has just vanished, and I have to map them
all over again.

As I was typing this, it occurred to me that the problem might be that
I've chosen drive letters that are not the next ones in the
alphabetical sequence. For example, on the Micron, I have D: drive
for zip disks and an E: drive for CDs. I'm wondering if the problem
is that in choosing the letter name for the VAIO drive I skipped from
the letter "E" all the way down to the letter "V," leaving something
like 16 or so unused drive letters in between.

I have to admit that that explanation seems a bit far-fetched to me.
But with Windows, it seems, anything is possible.

Any ideas on how I could get the mapped drive letters of "M" and "V"
to stick once-and-for-all?
 
Hello Clueless,

net use M: \\micron\sharename or \\micron\volume /Persistent:YES

net use V: \\vaio\sharename or \\vaio\volume /Persistent:YES

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
 
net use M: \\micron\sharename or \\micron\volume /Persistent:YES

net use V: \\vaio\sharename or \\vaio\volume /Persistent:YES
Click to expand...

I'm guessing that I'll need to copy one of those strings and then
paste it in somewhere in the network configuration. Did I get that
right.

But I haven't a clue where exactly it should go.

In the meantime, since remapping the VAIO drive to V: this morning on
the Micron, I now get repeated error messages saying:

An error occurred while reconnection to V: to \\Vaio\VAIO
Microsoft Windows Network: The local device name is already in
use.
This connection has not been restored.

I wonder if rebooting might help.

I'm in a frantic rush to get some presents wrapped and get over to my
brother's house, so I guess I'll have to deal with this tomorrow.

Thanks for the help. I'll check back tomorrow morning.

Will in Seattle
a.k.a. "Clueless"
 
Hello Clueless,

From the command line run "net use" without the quotes. It will show you
all existing mappings. With "net use /delete" you can delete all mappings
and start new ones.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
 
From the command line run "net use" without the quotes. It will show you
all existing mappings. With "net use /delete" you can delete all mappings
and start new ones.
Click to expand...

Hi again, Meinolf!

Yes, you're right, you did already reply to my question, but my memory
has gotten so bad these days that I had no recollection of having
posted it. (Could it have been all the Celebration Ale on xmas eve?)

I'll give your proposed fix a try. But I have to confess that it
puzzles me why I would want to delete my mappings when my problem
seems to be that Win2K is peremptorily deleting them.

So, are you saying that if I delete all mappings at the command prompt
level, then the create new ones, the new ones will be more likely to
"stick"?

Should I try to map the drives at the command prompt level too?

If so, would you mind posting the commands I'll need to know?

Will in Seattle
a.k.a. "Clueless"
 
Back
Top