Ryan,
I have been experiencing the same problems. Our environment: Win XP
Pro SP2 clients on WIN Server 2003 (pre-SP1). Drives mapped in bat
file at logon with net share commands using persistent-no parm. Has
not solved problem.

Have referred to Microsoft articles mentioned in your post as well as
knowledge base articles 271183, 308337, 890413. Have recently tried
setting GPO in Computer Config-Admin Temp-System for Run logon scripts
synchronously and Always wait for the network at computer startup and
logon. Have checked desktop shortcuts for improper drive mappings.
None of these has completely solved the problem.

Noticed new behavior this week: Abitrary network drive assignment to
requested mapped network share as you have described in your post.
Only consistent resolution is to restart computer.

Bottom line: XP clients (whether locally attached computer or remote
user using Terminal Services to access network) do not always get
network drives reconnected status and letter mapped to disconnected
drive may not be requested drive mapping. Pattern seems to be
inconsistent and irrelevant to user status.

NancyMc

Ryan Wrote:
> 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://tinyurl.com/28se5
> 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://tinyurl.com/azx3f (this share
> allows more than one user to connect at a time and the server has sp4
> already)
> http://tinyurl.com/75p45 (already
> have sp4 with latest updates on server and xp2 with all latest updates
> on the
> xp pro machine)
> http://tinyurl.com/anfl9 (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?


--
NancyMc

I have yet to find a solution, but just an update - the original machine that
was having these random mappings was only running xp sp1. This machine is
now on service pack 2 with all latest updates and still has the same issue.

This isn't a consistent problem in the sense that it starts when the pc
boots... sometimes it takes a while and slowly all drive letters magically
get used up.

I have removed the entries in the registry and althought he registy was
clean of any reference to the network share I still have the mappings and can
not remove them. I'm at a complete loss with this one.

I'm seen people suggesting to set up a new user profile in case the current
one is corrupt but any user, including domain/enterprise admin, gets these
mappings on these haywire machines.

Listen Up Microsoft... Your customers need you!

I have been having a simlar issue. I applied a GPO to the XP machine
and used a startup script for the machine through the GPO. The script
is a .bat file using a net use command. This seemed to give the same
result as what you are seeing. The name of the mapped drive is
disconnected Network Drive and the description is the same. Any
thoughts on this??

Mike

Willis68nova Wrote:
> I have been having a simlar issue. I applied a GPO to the XP machine
> and used a startup script for the machine through the GPO. The script
> is a .bat file using a net use command. This seemed to give the same
> result as what you are seeing. The name of the mapped drive is
> disconnected Network Drive and the description is the same. Any
> thoughts on this??
>
> Mike
I had this same problem for months and the solution was head
slappingly simple; Just change the Policy for the mapped drive script
to run under User Config rather than Computer Config. After the policy
updated itself on the machine, the problem went away,
Carrie


--
ctd727

I have a similar problem.

My problem with Win XP SP2 is that I receive a "disconnected network drive"
notification when trying to access the home folder. It is always the home
folder which is set not in a script but in Active Directory (Users and
Computers Snapin Profile-->Home Folder-->Connect z: SOME_UNC_PATH). If the
system is restarted the user can log in and use their home folder just fine.

This does not seem to happen all the time, only when a particular uaser uogs
into the same computer ahead of them, uses it for awhile and then logs out.

This seems very similar to
http://support.microsoft.com/default...b;en-us;330519 but not quite.


I also had cacheing enabled on the share that hosted the roaming profiles
folders but that has now been turned off.

Anyone have any ideas?




"ctd727" wrote:

>
> Willis68nova Wrote:
> > I have been having a simlar issue. I applied a GPO to the XP machine
> > and used a startup script for the machine through the GPO. The script
> > is a .bat file using a net use command. This seemed to give the same
> > result as what you are seeing. The name of the mapped drive is
> > disconnected Network Drive and the description is the same. Any
> > thoughts on this??
> >
> > Mike
> I had this same problem for months and the solution was head
> slappingly simple; Just change the Policy for the mapped drive script
> to run under User Config rather than Computer Config. After the policy
> updated itself on the machine, the problem went away,
> Carrie
>
>
> --
> ctd727
>

I have verified that it is data in the roaming profile that is causeing this
pronblem. Anyone have any tips on how to fix or clean the roaming profile?

"The_Canuck" wrote:

> I have a similar problem.
>
> My problem with Win XP SP2 is that I receive a "disconnected network drive"
> notification when trying to access the home folder. It is always the home
> folder which is set not in a script but in Active Directory (Users and
> Computers Snapin Profile-->Home Folder-->Connect z: SOME_UNC_PATH). If the
> system is restarted the user can log in and use their home folder just fine.
>
> This does not seem to happen all the time, only when a particular uaser uogs
> into the same computer ahead of them, uses it for awhile and then logs out.
>
> This seems very similar to
> http://support.microsoft.com/default...b;en-us;330519 but not quite.
>
>
> I also had cacheing enabled on the share that hosted the roaming profiles
> folders but that has now been turned off.
>
> Anyone have any ideas?
>
>
>
>
> "ctd727" wrote:
>
> >
> > Willis68nova Wrote:
> > > I have been having a simlar issue. I applied a GPO to the XP machine
> > > and used a startup script for the machine through the GPO. The script
> > > is a .bat file using a net use command. This seemed to give the same
> > > result as what you are seeing. The name of the mapped drive is
> > > disconnected Network Drive and the description is the same. Any
> > > thoughts on this??
> > >
> > > Mike
> > I had this same problem for months and the solution was head
> > slappingly simple; Just change the Policy for the mapped drive script
> > to run under User Config rather than Computer Config. After the policy
> > updated itself on the machine, the problem went away,
> > Carrie
> >
> >
> > --
> > ctd727
> >

I am having the exact same problem as Ryan - I've tried multiple things
& I can't get rid of the "Disconnected Network Drive" from my XP Pro
XP2 machine. It's only happening to one computer in my domain (60+
workstations), & I'm not sure why. I get the same results in Windows
Explorer & from a command line w/ net use. Has anyone solved this
issue yet?

The cacheing issue fixed problem 1 of 2 for me. I still see this problem
that you describe. Is the problem repeatable for you? For me it is not.
Once a day on a different workstation or a different user. (50 ws and 250
users)

Funny thing for me is only the home folder mapped from the Active Directory
Users and Computers snapin is affected. All other shares are available that
are mapped via login scripts.

"jdieckmann@valleycountyhospital.org" wrote:

> I am having the exact same problem as Ryan - I've tried multiple things
> & I can't get rid of the "Disconnected Network Drive" from my XP Pro
> XP2 machine. It's only happening to one computer in my domain (60+
> workstations), & I'm not sure why. I get the same results in Windows
> Explorer & from a command line w/ net use. Has anyone solved this
> issue yet?
>
>

I just found the answer that fixed my issue. I unjoined & rejoined the
PC to the network. The exact steps I took were:

1. Unjoin PC from AD domain & join WORKGROUP instead.
2. Rename PC (I had already planned on doing this).
3. Rejoin PC to AD domain.

Once I logged onto the PC as the user the "Disconnected Network Drive"
was gone & I was able to remap the drive w/ the proper path. I'm not
sure if renaming the PC had anything to do w/ it or not, but you might
try an unjoin/rejoin to see if that works.

That only works because you are getting a new profile.

I've had the same exact problems on Win2k and WinXP. I would wipe the machine
clean of any profiles and then recreate them but this still did not work.

Has anyone resolved this issue yet?

"tiredofit@gmail.com" wrote:

> That only works because you are getting a new profile.
>
>

There is a SAV (Symantec Antivirus Corporate Edition 10) issue as documented
here:

http://service1.symantec.com/SUPPORT...= bar_sch_nam

I implemented the fix on the domain controller and after one week I see no
improvement.

Just to clarify my disconnected nework drive is happening only for the users
home folder as specified in ADUC (Active Directory Users And Computers) tool.
We are using the drive letter of z:

Another thing we are toying with is moving the drive letter from z: to U:.
(Z is the last drive that can be used is the reasoniing.)

The other thing I am chasing down is userprofiles. I am going to try to
chase down the userprofile cleanup tool as specified herwe.

Note we are using Roaminng profiles with 50 of or 250 users. Is everyone
else too?




"ScottA" wrote:

Sorry I meant to include the UPHClean to cleanup the userprofiles in the
above post

"The_Canuck" wrote:

Any solution to this yet. Have the same issue here but only happens in a TS
session or logging directly onto the server. Endusers dont see the issue. I
tried the NAV fix and it didnt help. Only goes away if i reboot the server
and then 18 hours later the problem comes back. This is a serious issue here
as the CIO want an answer to this from me and I dont have one.

"The_Canuck" wrote:

Rborias wrote:

I tried the symantec fix and it didnt work. I can uninstall and reinstall
and about 2 hours later I get disconnect newotrk drive errors. I know its a
symantec issue now as it only happens when I install it. As for symantec
they are no help at all at this point. I am about to dump their product and
go towards something else.

Wow this is a long post I have solved almost all my problems:

GPO change to wait for network at login
SAV 10 fix
Install UPHClean utility from MS
Moved z: mapped drives to U:



"Rborias" wrote: