I realize that there are alot of discussions that sort of touch on this
subject however I have gone through alot of troubleshooting and have found
nothing that can fix the problem so far.

The network drives are simply not disconnecting any way any how when the
user simply logs into the network, ie logging out then logging back in. A
Reboot clears the connections and the login works fine mapped drives etc.
work fine. From there if I clear or disconnect the drives using either
explorer or a net use * /del the drive letters still show up but show up as
disconnected, if I try to map them back they do not work, it comes back and
indicates that the drive letter is already in use.

I have found nothing other than a reboot to have the drives come back. I
have gone through all of the articles like the persistent:no to attempt the
turn the persistent drive mapping off and this seems to make the initial
login worse (After a reboot) the drives show up as disconnected right off the
bat.

I have gone through and looked through AD to find another spot that drive
mappings could be assigned - in conflict and there is nothing else there.
I have gone through various nic drivers, and checked the switch logs to see
if there is anything there that could help with what is going on and there is
nothing.

I have gone into the registry to remove the
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\DesktopProcess=1 and actually put it back in to see if this would help. It does not.

It is pretty apparent from all of my trouble shooting it is that the drives
are not disconnecting on logout, and it is a pain because I like to have them
leave the machines on at night or just log off to use wSus server to push
updates in the evening. I have to tell them to reboot.

Maybe I am incorrect in saying this but it should simply work, and is
becoming increasingly frustrating.

Thanks
MFLR

MFLR wrote:
>
> The network drives are simply not disconnecting any way any how when the
> user simply logs into the network, ie logging out then logging back in. A
> Reboot clears the connections and the login works fine mapped drives etc.
> work fine. From there if I clear or disconnect the drives using either
> explorer or a net use * /del the drive letters still show up but show up as
> disconnected,
<snip>


I ran into this same issue recently - I feel your pain!

This WSH script will disconnect and then Map the drives properly:

http://www.ss64.com/wsh/drivemap.txt

Save it as DriveMap.vbs

'Usage
' cscript DriveMap.vbs <drive> <fileshare> //NoLogo

e.g.
cscript DriveMap.vbs H: \\MyServer\MyShare //NoLogo

Thank you,

It does appear to have helped.


"Simon Sheppard" wrote:

> MFLR wrote:
> >
> > The network drives are simply not disconnecting any way any how when the
> > user simply logs into the network, ie logging out then logging back in. A
> > Reboot clears the connections and the login works fine mapped drives etc.
> > work fine. From there if I clear or disconnect the drives using either
> > explorer or a net use * /del the drive letters still show up but show up as
> > disconnected,
> <snip>
>
>
> I ran into this same issue recently - I feel your pain!
>
> This WSH script will disconnect and then Map the drives properly:
>
> http://www.ss64.com/wsh/drivemap.txt
>
> Save it as DriveMap.vbs
>
> 'Usage
> ' cscript DriveMap.vbs <drive> <fileshare> //NoLogo
>
> e.g.
> cscript DriveMap.vbs H: \\MyServer\MyShare //NoLogo
>
>
>

Tried it but it did not help the problem I am having is mostly the same on a
fresh boot of the computer I do not have any problems but if the user logs
off and an other users logs on and then logs off the next user logging in get
two or more disconnected network drives I have set all workstations to run a
netlogin.bat file at start up and have updated all symantec products and
windows xp updates but I still get disconnected drives.

Tech Support Tuckerton Police Department

"MFLR" wrote:

> Thank you,
>
> It does appear to have helped.
>
>
> "Simon Sheppard" wrote:
>
> > MFLR wrote:
> > >
> > > The network drives are simply not disconnecting any way any how when the
> > > user simply logs into the network, ie logging out then logging back in. A
> > > Reboot clears the connections and the login works fine mapped drives etc.
> > > work fine. From there if I clear or disconnect the drives using either
> > > explorer or a net use * /del the drive letters still show up but show up as
> > > disconnected,
> > <snip>
> >
> >
> > I ran into this same issue recently - I feel your pain!
> >
> > This WSH script will disconnect and then Map the drives properly:
> >
> > http://www.ss64.com/wsh/drivemap.txt
> >
> > Save it as DriveMap.vbs
> >
> > 'Usage
> > ' cscript DriveMap.vbs <drive> <fileshare> //NoLogo
> >
> > e.g.
> > cscript DriveMap.vbs H: \\MyServer\MyShare //NoLogo
> >
> >
> >

Fitzco wrote:
> Tried it but it did not help the problem I am having is mostly the same on a
> fresh boot of the computer I do not have any problems but if the user logs
> off and an other users logs on and then logs off the next user logging in get
> two or more disconnected network drives I have set all workstations to run a
> netlogin.bat file at start up and have updated all symantec products and
> windows xp updates but I still get disconnected drives.
>
> Tech Support Tuckerton Police Department

If you are running the script at bootup, it's possible that it's running
before the network (TCP/IP) has fully loaded.

I suggest running it at login for each user
- as an experiment copy the script to the C: drive and get a user to
run it manually
- does that work?

Simon Sheppard

"Simon Sheppard" wrote:

> Fitzco wrote:
> > Tried it but it did not help the problem I am having is mostly the same on a
> > fresh boot of the computer I do not have any problems but if the user logs
> > off and an other users logs on and then logs off the next user logging in get
> > two or more disconnected network drives I have set all workstations to run a
> > netlogin.bat file at start up and have updated all symantec products and
> > windows xp updates but I still get disconnected drives.
> >
> > Tech Support Tuckerton Police Department
>
> If you are running the script at bootup, it's possible that it's running
> before the network (TCP/IP) has fully loaded.
>
> I suggest running it at login for each user
> - as an experiment copy the script to the C: drive and get a user to
> run it manually
> - does that work?
>
> Simon Sheppard
It is set to run as the user logs in not boot up if I rerun the file after
the user has logged in it is ok for the first user and the second user but if
you go to a third user or back to the first user you start getting
disconnected drives which can only be cleared by restarting the computer.

Tech Support Tuckerton Police Department

I have been playing around with this a little more and it is still leaving
the drives disconnected! It only seems to happen on the Xp machines. my other
2003 server maps and disconnects just fine.

"Fitzco" wrote:

>
>
> "Simon Sheppard" wrote:
>
> > Fitzco wrote:
> > > Tried it but it did not help the problem I am having is mostly the same on a
> > > fresh boot of the computer I do not have any problems but if the user logs
> > > off and an other users logs on and then logs off the next user logging in get
> > > two or more disconnected network drives I have set all workstations to run a
> > > netlogin.bat file at start up and have updated all symantec products and
> > > windows xp updates but I still get disconnected drives.
> > >
> > > Tech Support Tuckerton Police Department
> >
> > If you are running the script at bootup, it's possible that it's running
> > before the network (TCP/IP) has fully loaded.
> >
> > I suggest running it at login for each user
> > - as an experiment copy the script to the C: drive and get a user to
> > run it manually
> > - does that work?
> >
> > Simon Sheppard
> It is set to run as the user logs in not boot up if I rerun the file after
> the user has logged in it is ok for the first user and the second user but if
> you go to a third user or back to the first user you start getting
> disconnected drives which can only be cleared by restarting the computer.
>
> Tech Support Tuckerton Police Department