very odd disconnected Network Drive....Help!!!

Domain Version: Windows 2003

Operating System on Workstation: Windows XP SP2

User has her H: drive mapped to her home folder on the file server. This is
achieved through her user object in Active Directory.

As the day goes on her H: drive which usually is described as “Username on
\\Servername H:” says instead, “Disconnected Network Drive” and has no red x
through it like a normal disconnected drive has. When the icon is
double-clicked, it shows all folders in the drive and is totally accessible.
It never reverts back to its original path. If you right click the icon, the
disconnect choice is there in the menu. If that is selected it comes back
with an error “Cannot find path” or something very close to that. If you try
to remap the drive either from the GUI or the command line, it says that the
path cannot be found. Again, if the icon is double-clicked it is accessible.


A logoff-logon does no good. Only a reboot will put it back to its original
state, then only time will tell when it happens again. I changed the
configuration in Active Directory to map to the J: drive instead and this
lasted for about a month and it is now doing it again. The user is not a
happy camper and is the president’s wife. The drive is completely useable
when she executes save as but she has to know what to look for. This is not
acceptable to her. This is the only computer in the domain that this is
happening to.

Network drives will disconnect themselves over idle time and are shown with
a red X. A simple double-click will restore them in this case. When a share
is down that you are mapped to, the disconnected drive will stay in its
disconnected state with the red X across it. The original mapping is there.
I have never seen a disconnected drive replace the UNC path with
“Disconnected Network Drive”.

Anybody got any clues?????


--
Paul W

you may want to run this command on your Win2k3 server:
net config server /autodisconnect:-1

read this KB http://support.microsoft.com/kb/297684/EN-US/ for further
details (<snip> wasting server resources on unused sessions).

I think you've got something else going on there, the above may just make
customer 'happy'.
Verify duplex/speed settings (make it all AUTO/AUTO) all the way from
workstation to server, i.e Wkstation NIC - switch port ....switch port -
Srvr NIC.
Check drivers / power savings settings on workstation.
Try different NIC / switch port / check cabling.


"Paul W" <PaulW@discussions.microsoft.com> wrote in message
news:AE4BAFDD-4611-4FF1-992A-267ED6DA29A6@microsoft.com...
> Domain Version: Windows 2003
>
> Operating System on Workstation: Windows XP SP2
>
> User has her H: drive mapped to her home folder on the file server. This
> is
> achieved through her user object in Active Directory.
>
> As the day goes on her H: drive which usually is described as "Username on
> \\Servername H:" says instead, "Disconnected Network Drive" and has no red
> x
> through it like a normal disconnected drive has. When the icon is
> double-clicked, it shows all folders in the drive and is totally
> accessible.
> It never reverts back to its original path. If you right click the icon,
> the
> disconnect choice is there in the menu. If that is selected it comes back
> with an error "Cannot find path" or something very close to that. If you
> try
> to remap the drive either from the GUI or the command line, it says that
> the
> path cannot be found. Again, if the icon is double-clicked it is
> accessible.
>
>
> A logoff-logon does no good. Only a reboot will put it back to its
> original
> state, then only time will tell when it happens again. I changed the
> configuration in Active Directory to map to the J: drive instead and this
> lasted for about a month and it is now doing it again. The user is not a
> happy camper and is the president's wife. The drive is completely useable
> when she executes save as but she has to know what to look for. This is
> not
> acceptable to her. This is the only computer in the domain that this is
> happening to.
>
> Network drives will disconnect themselves over idle time and are shown
> with
> a red X. A simple double-click will restore them in this case. When a
> share
> is down that you are mapped to, the disconnected drive will stay in its
> disconnected state with the red X across it. The original mapping is
> there.
> I have never seen a disconnected drive replace the UNC path with
> "Disconnected Network Drive".
>
> Anybody got any clues?????
>
>
> --
> Paul W