Mapped drives appear disconnected

T

Tony Dewar

When booting XP, the mapped drives do not automatically
reconnect upon rebooting. I get a message that ' not all
your drives have connected' or something like that. The
map drive letter remains, however I have to go into
windows explorer and double-click the mapped drive a
couple time before it will come up. I have had this
happen on several computers. Certainly there must be a
remedy for this. I have downloades all available critial
and recommended updates as well. any suggestions.
(e-mail address removed)
Thanks AMD- mcse, ccna, ccda
 
D

Derek

Tony,
I've posted this exact same question, as have others,
numerous times to no avail. Most often the reponses have
been around using the NET USE... command with or without
the /persistent:yes parameter, but it makes no
difference. This is a huge issue, especially when you
have applications that require the nw drive mapping to
appear so they can run on startup! I do not have this
issue with my Win2000 or Win98SE systems, just XP. MS
must know about this issue, but they sure aren't
acknowledging it.

Cheers
Derek
 
P

Pat \(MSFT\)

Hi Tony,

When you map the drive originally, how are you doing this? Are you doing
this via Explorer, or the command line? Also, when you reboot, or log off
then log on, are you logging on as the same user?

There are several things that could be causing what you are seeing. One is
not having the persistent mapping set up (which you are probably doing),
logging on as a different user, the share you are mapped to is offline,
network connectivity issues etc...

If this problem persists and you cannot get an answer, you could always
create a batch file that will connect to the drive at logon time as well.

Thanks,
 
D

Derek

Hi Pat,

I've tried using batch files to no avail. In an earlier
post, I mentioned that I believe it's a timing thing on XP
bootup that prevents the batch files from working, almost
as if there's another process that needs to compelete
prior to drives being made 'active'. Any ideas?

Thanks,
Derek
 
J

John Saitta

Gentelmen,

this apper to be a known problem with XP take a look at
KB812933 for details on getting the hotfix. (which I do
not believe is included in any service pack)

Thanks
John
 
P

Pat \(MSFT\)

Derek,

If you put the batch file in the Startup group, it should run regardless.
By the time you have booted, the TCPIP stack will have been loaded, as
should the drivers for your NIC, so that shouldn't be the problem. I cannot
see any reason why your batch files wouldn't run if you have them in the
startup group.

Also, have you tried the command line version? Something like:

"net use z: \\machine\share /persistent:yes"

You can also try this by adding your credentials at the end as well in case
that is the problem:

"net use z: \\machine\share /persistent:yes /u:domain\user <password>"
 
T

Tony Dewar

Thanks Derek, and all others...
I also have seen this issue over and over again...
partictularly in peer-to-peer. I was just hoping there was
a fix for this by now, and maybe somehow I have just over
looked it.
Something as simple as this should not have stayed an
issue for this long. Frankly, having to type in the 'net
use' command to get a share to 'persist' is ridiculous#@!
And the KB812933 article (which I read before I posted
this 'RFH' request for help, and was the only close
relative I could find.)also seems a bit of a stretch to
solve this issue. Then with the caveat 'You might have to
pay for a fix,' is a bit disappointing. I sincerely
appreciate everybody's help. Again thanks....
But I can't but help the feeling that Microsoft does not
attack all of 'its problems' with the same vigor except in
the direction it wants everyone to follow.
Tony Dewar MCSE,CCNA,CCDA
(e-mail address removed)
 
D

Derek

Thanks for the suggestions Pat. It's not that the batch
files don't run, it's just that the mapped drives
aren't 'active' on bootup (they appear but have the
red 'x' through them) until I click on them to open them
up. I've tried the command line version in the batch
files, and on their own. Mapping them isn't the problem;
making them reconnect and active at bootup is the issue.
I'll try adding the credentials, although I only have one
user defined and no password, so I don't know if this will
work.

Cheers
Derek
 
D

Derek

I'm with you Tony!

Cheers
Derek
-----Original Message-----
Thanks Derek, and all others...
I also have seen this issue over and over again...
partictularly in peer-to-peer. I was just hoping there was
a fix for this by now, and maybe somehow I have just over
looked it.
Something as simple as this should not have stayed an
issue for this long. Frankly, having to type in the 'net
use' command to get a share to 'persist' is ridiculous#@!
And the KB812933 article (which I read before I posted
this 'RFH' request for help, and was the only close
relative I could find.)also seems a bit of a stretch to
solve this issue. Then with the caveat 'You might have to
pay for a fix,' is a bit disappointing. I sincerely
appreciate everybody's help. Again thanks....
But I can't but help the feeling that Microsoft does not
attack all of 'its problems' with the same vigor except in
the direction it wants everyone to follow.
Tony Dewar MCSE,CCNA,CCDA
(e-mail address removed)

.
 
D

DrydenMaker

I too am having this problem.
I have a batch file that uses several map statements like:
net use r: \\fileserver\share password /user:user /persistent:no
AND
net use r: \\fileserver\share /persistent:no
As well as using /persistent:yes

So what happens is when I loggin, I open windows explorer, and I have
no extra drive mappings. I can type m:\ in the address bar and it
goes there, but it doesnt show up on its own. So now we go to the
shell and type net use and get the following:

M:\>net use
New connections will not be remembered.


Status Local Remote Network

-------------------------------------------------------------------------------
OK I: \\fileserver\ADS Microsoft Windows
Network
OK L: \\fileserver\LIBRARY Microsoft Windows
Network
OK M: \\fileserver\users\user Microsoft Windows
Network
OK N: \\fileserver\COMMON Microsoft Windows
Network
OK O: \\fileserver\share Microsoft Windows Network
OK R: \\fileserver\www Microsoft Windows
Network
OK T: \\fileserver\APPS Microsoft Windows
Network
OK U: \\fileserver\dryden Microsoft Windows
Network
OK V: \\fileserver\apple Microsoft Windows
Network
OK W: \\fileserver\fileshare Microsoft Windows
Network
OK X: \\fileserver\www Microsoft Windows
Network
OK Y: \\fileserver\PANTHER Microsoft Windows
Network
OK Z: \\fileserver\www Microsoft Windows
Network
The command completed successfully.


M:\>


This has been an ongoing problem, and I think I have seen it with NT
also.
We are logging into AD in non-native mode with various clients:
NT(obviously), 2k, XP. I have seen several postings arround several
groups: (microsoft.public.windowsxp.general and
microsoft.public.windowsxp.network_web) that have gone unanswered.

please excuse my spelling.
-Alton Crossley
Nogahide BootStrap
 
D

DrydenMaker

I too am having this problem.
I have a batch file that uses several map statements like:
net use r: \\fileserver\share password /user:user /persistent:no
AND
net use r: \\fileserver\share /persistent:no
As well as using /persistent:yes

So what happens is when I loggin, I open windows explorer, and I have
no extra drive mappings. I can type m:\ in the address bar and it
goes there, but it doesnt show up on its own. So now we go to the
shell and type net use and get the following:

M:\>net use
New connections will not be remembered.


Status Local Remote Network

-------------------------------------------------------------------------------
OK I: \\fileserver\ADS Microsoft Windows
Network
OK L: \\fileserver\LIBRARY Microsoft Windows
Network
OK M: \\fileserver\users\user Microsoft Windows
Network
OK N: \\fileserver\COMMON Microsoft Windows
Network
OK O: \\fileserver\share Microsoft Windows Network
OK R: \\fileserver\www Microsoft Windows
Network
OK T: \\fileserver\APPS Microsoft Windows
Network
OK U: \\fileserver\dryden Microsoft Windows
Network
OK V: \\fileserver\apple Microsoft Windows
Network
OK W: \\fileserver\fileshare Microsoft Windows
Network
OK X: \\fileserver\www Microsoft Windows
Network
OK Y: \\fileserver\PANTHER Microsoft Windows
Network
OK Z: \\fileserver\www Microsoft Windows
Network
The command completed successfully.


M:\>


This has been an ongoing problem, and I think I have seen it with NT
also.
We are logging into AD in non-native mode with various clients:
NT(obviously), 2k, XP. I have seen several postings arround several
groups: (microsoft.public.windowsxp.general and
microsoft.public.windowsxp.network_web) that have gone unanswered.

please excuse my spelling.
-Alton Crossley
Nogahide BootStrap
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top