Re: Disconnected Network Drives can't be remapped or removed - Help!

Ryan,

Hmm, haven't heard of this before but here is something that sounds like it
MIGHT help you out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;172975

-Jeff

"Ryan" <Ryan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D1B9FD0D-928F-423D-9152-9C055312A809@xxxxxxxxxxxxxxxx
>I have an XP pro machine purchased not too long ago, doesn't appear to be
> infected (we have several virus and spyware apps on it) and when the user
> opens Windows Explorer he sees many mapped shares that give him a status
> of
> "Disconnected Network Drive" He does have two other shares that work fine
> and give a proper status. I believe these map to a different server
> though.
>
> The "disconnected network drive" shares all seem to point to the same
> folder
> and if he clicks on them he can view the contents of that share. He is
> supposed to have a share called \\bdnt4\company that maps to the drive
> letter
> f. Instead he gets f mapping to that folder along with every other letter
> in
> the alphabet after f mapping to that company folder as well. They all say
> disconnected.
>
> The F: mapping goes to a company folder share on an SBS 2000 premium
> server
> with sp4, and it has a very large timeout set for network connections as
> suggested in
> http://support.microsoft.com/default.aspx?scid=kb;en-us;297684
> The other two shares that show up fine are mapped to a 2000 terminal
> server
> with sp4, without the timeout increased beyond 15mins.
>
> There are no logon scripts creating these mappings, they were done through
> Windows Explorer. Disconnecting in Windows Explorer gives me "The network
> connection
> could not be found" If I try to remap I get "The local device name is
> already in use"
>
> I've also tried many variations of the net use commands and have even used
> net use * /delete which has no affect on the disconnected mappings.
> Trying to use net use to delete the individual shares just says:
> The network connection could not be found.
> More help is available by typing NET HELPMSG 2250
>
> Reconnecting via net use gives me:
> System error 85 has occured
> The local device name is already in use
>
> I've seen many others with the same or very similar issue and all
> solutions
> (if they actually worked for anyone) haven't had a positive effect for me.
> Others have also noticed this happening to shares that no longer exist.
> In
> my case they do exist, and this "disconnected network drive" issue occurs
> while logged on as that user or as the domain admin.
>
> This has only been happening recently. Last friday the disconnected
> network
> share f: also replicated to x,y,and z. Now its every letter in the
> alphabet
> after f. This is happening on a new PC purchased a not that long ago and
> it
> has automatic updates enabled (thought that may be of interest since I've
> read that others believe it to be caused by an Xp update)
>
> I have also looked at:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;318370 (this
> share
> allows more than one user to connect at a time and the server has sp4
> already)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;812933 (already
> have sp4 with latest updates on server and xp2 with all latest updates on
> the
> xp pro machine)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;283492
> (connecting
> to a 2000 share, not 95/98, and I have the passwords set up in Xp Stored
> User
> Names and Passwords)
>
> Besides having many annoying disconnected shares mapping to the same
> folder,
> this disconnect status is giving the user some problems when accessing
> that
> share from apps like Autocad. I've read that some apps won't access a
> shared
> folder unless its status is basically fully connected, and I believe that
> the "disconnected network drive" status is why he's having problems
> accessing
> his data from some apps.
>
> I don't want any help saying to create some logon scripts, especially with
> net use commands because net use commands aren't doing anything for me,
> and
> yes, I have rebooted after every change so this won't be fixed by a simple
> reboot. So... Can anyone help me?


.