Shows drives f to z as disconnected

[My Boss's Secretary]

This started right after the latest Windows Security update ( week of 10 15
dec 2007) was downloaded and installed, although it could be a conincidence.

I have a problem with several winxpsp2 clients on a w2k3 domain. All drive
letters from F: to Z: are mapped to the same server share and are labelled as
diconected but still access the same share mostly that is the first share
gets mapped to all other drive letters.

 

[My Boss's Secretary]

Opps forget to say they clients are XP Professional ! Fully patched ! No
scripts are run, just (normally ) mapped 3 server drives with the
Explorer/tools/ map drive / reconnect at login. Hope this additional info
helps. Our IT guys are stumped ! !

My Boss's Secretary . ..

 

[Leythos]

I have a problem with several winxpsp2 clients on a w2k3 domain. All drive
letters from F: to Z: are mapped to the same server share and are labelled as
diconected but still access the same share mostly that is the first share
gets mapped to all other drive letters.

I've seen the same thing since the start of the month. We have a small
shop with 150 users/computers, all on a Win 2003 Std R2 and all
updates/sp's and even tried all of the MS Hot fixes related to this,
even the ones you have to request.

Strange thing is that it's not machine specific, once it happens it will
always happen to the same user on the same machine, but other users that
might use that machine may not experience it.

Disjoining the computers from the domain, creating a new account, does
not resolve it. The Security event log often shows a logon failure, but
the user is still permitted to login and even their logon script, that
deletes all mapped drives and remaps them, runs fine without error.

This is really annoying and time consuming.

If the users double click on the disconnected share they can still
access it, and then pressing F5 (refresh) shows it's connected again,
until later that day or the next day.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
(e-mail address removed) (remove 999 for proper email address)

 

[SG]

Hi,

What Security update was it and can you uninstall it?

--
All the best,
SG
How to Write a Newsgroup Post:
http://www.elephantboycomputers.com/page2.html#Usenet
Need your OEM Restore Disk?
http://restoredisks.com/

 

[My Boss's Secretary]

Our IT guy fixed it. . .. here is what he did.

he manually removed each "disconnected drive" using;

1. Click Start, and then click Run.

2. In the Open box, type cmd.

3. Type net use x: /delete, where x: is the drive letter of the shared
resource.

then before doing a restart he ran an Registery Cleaning program ( PCtools
Registry Mechanic) and it corrected all the found registry errors. Then he
did a restart, and all the drives ( f to Z ) were NO Longer Displayed. So
far ( several hours ) they have NOT come back.

I'll give our IT guy a BIG "ATTA BOY" for this one ! !

 

[Leythos]

Our IT guy fixed it. . .. here is what he did.

he manually removed each "disconnected drive" using;

1. Click Start, and then click Run.

2. In the Open box, type cmd.

3. Type net use x: /delete, where x: is the drive letter of the shared
resource.

then before doing a restart he ran an Registery Cleaning program ( PCtools
Registry Mechanic) and it corrected all the found registry errors. Then he
did a restart, and all the drives ( f to Z ) were NO Longer Displayed. So
far ( several hours ) they have NOT come back.

I'll give our IT guy a BIG "ATTA BOY" for this one ! !

Let us know if it's still fixed after a couple days and a couple
reboots. I had, without cleaning the registry, fixed it several times,
without it returning for a day or so, at least that's what I though.

I don't like registry cleaners, but, if you've not seen disconnected for
several days, please post back and let us know.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
(e-mail address removed) (remove 999 for proper email address)

 

[My Boss's Secretary]

Will do. . .. will keep this thread updated for 1 week. Problem was fixed at
approx 10 AM local time, and after three reboots and the C.O.B.( close of
business approx 17:00) today , the problem had not returned. Keeping
fingers crossed. . .

 

[Leythos]

Will do. . .. will keep this thread updated for 1 week. Problem was fixed at
approx 10 AM local time, and after three reboots and the C.O.B.( close of
business approx 17:00) today , the problem had not returned. Keeping
fingers crossed. . .

Any idea what key in the registry was the problem.

I'm willing to bet that our systems are only alike in the area of
Windows updates and XP Prof install, the software and AV would most
likely be different. All of our networks are behind layers of firewalls
and we don't allow users to load anything, CD's are disabled and no USB
access...

Thanks

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
(e-mail address removed) (remove 999 for proper email address)

 

[My Boss's Secretary]

Situation report. . . .

After 1 full day of no returned disconnected drives, I'm sorry to report
that after this mornings boot up, they all came back ! ! drives f throu z
show up as disconnected drives, and if you click on ANY of them, they ALL
take to to the one real mapped drive / folder.

Come on guys, lots of smart folks out there, somebody has to know a fix for
this ! ! !

 

[My Boss's Secretary]

Additional info. . ..

this seems NOT to be user profile related, as when the sysadm logged in he
too saw drives f hrou z as disconnected. Then he had another user log on and
that (normal ) user also saw all drives as disconnected ( f throu z )

 

[chiprenn]

Having the same/similar problem. Also started about Nov 20, 2007.
I'll provide my take...maybe it'll help fire up some brain cells!

Running W2003, and XP clients. Users will have a 'Disconnected
Network Drive' for a drive that should be mapped in the login script.
Sometimes they will still be able to access the file system. Other
times they can access files EXCEPT for Access databases. Then, they
get a 'This file is outside the trusted zone' error.

And even at other times, although we only have 5 mapped drives, EVERY
alphabet letter will show a Disconnected network drive. Clicking on
these will redirect to one of the existing shares.

A reboot clears it up - until the next logoff/logon. Thought it was a
corruption in the Roaming Profiles, but after creation of a new
Roaming Profile the problem reappears after a few days. Also, this
issue is occurring for users without a roaming profile.

The logon script has worked for quite a while (years) and it has not
been changed. MS updates are handled by a WSUS server internally, and
have not pushed any updates recently as i try to troubleshoot this.

Can't figure this out! Any ideas?

 

[Weinie]

In our case, this ws caused by Symantec AV. Remove that POS, and the problem
goes away.

 

[Dan DeCoursey]

POS? what is that ??

In our case, this ws caused by Symantec AV. Remove that POS, and the problem
goes away.

 

[Muehe]

Same thing has been happening in our shop for over a month now -- still
looking for a solution.
Not every computer, actually probably less than 10% of them are having the
problem.

 

[Angie]

We are also running SAV. When we had the said problem, I uninstalled SAV. It
seemed to have fixed the 'disconnected network drive' problem. But then after
a week or two after, the problem returns...

 

[Jonny]

Fix for 'disconnected network drive' problem:

Open regedit, look for below key. Change "NoNetCrawling" from 0 -> 1.
Restart computer and your problem is solved
Merry Christmas and HNY


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"NoNetCrawling"=dword:00000001

Regards
Jonny Larsson

 

[Angie]

Unfortunately, resolution was a no go. Back to square one...

Fix for 'disconnected network drive' problem:

Open regedit, look for below key. Change "NoNetCrawling" from 0 -> 1.
Restart computer and your problem is solved
Merry Christmas and HNY


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"NoNetCrawling"=dword:00000001

Regards
Jonny Larsson

We are also running SAV. When we had the said problem, I uninstalled SAV. It
seemed to have fixed the 'disconnected network drive' problem. But then after
a week or two after, the problem returns...

 

[Angie]

Well after 2 months of searching, I have *possibly* come up with a solution.
Observation is still underway, but everything 'seems' to be going well.

I will go through the steps that I went through. Hopefully, one of these
will be a solution:

1. Uninstalled 10.0 and upgraded 10.2 clients --> worked for a couple of
days and the disconnected network drives reappeared.

2. Removed
HKEY_CURRENT_USER\Sofware\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 registry key, then rebooted --> worked for some people, not for others.

3. Start --> run --> MSCONFIG --> services tab --> check 'Hide all Microsoft
services' --> this then displayed all 3rd party services --> uncheck
'Symantec Antivirus' --> Reboot -> Log on and off several times to see if the
problem is there. If the problem is there, then it is not SAV. If it is,
you're problem lies within the Symantec AntiVirus.

4. Finally lodged call with Symantec --> told me to upgrade system centre to
latest version and depoly new AV to clients. This did not work.

5. Waited for Symantec to call back...they did not...so I went and started
investigated myself again.

6. Disabled the startup scan in Symantec System Centre, rebooted clients and
VOILA!!! Users no longer get 'Disconnected Network Drives' *touchwood*
To do this, go onto Symantec System Centre--> in the heirarchy, right-click
on you primary server --> All tasks --> Symantec AntiVirus --> Client
Adminsitrator Only Options --> Scans tab --> uncheck 'Run startupscans when
user logs in' --> click ok until you are finished. Make sure to get the
clients to reboot. Hopefully problem should go away.

Like I said earlier, everything is still under observations - so I do not
guarantee anything. I know how frustrating it is to try and get a fix for
this so I wish you all good luck.

Unfortunately, resolution was a no go. Back to square one...

Fix for 'disconnected network drive' problem:

Open regedit, look for below key. Change "NoNetCrawling" from 0 -> 1.
Restart computer and your problem is solved
Merry Christmas and HNY


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"NoNetCrawling"=dword:00000001

Regards
Jonny Larsson

We are also running SAV. When we had the said problem, I uninstalled SAV. It
seemed to have fixed the 'disconnected network drive' problem. But then after
a week or two after, the problem returns...

:


In our case, this ws caused by Symantec AV. Remove that POS, and the problem
goes away.


--
Joe


:

Having the same/similar problem. Also started about Nov 20, 2007.
I'll provide my take...maybe it'll help fire up some brain cells!

Running W2003, and XP clients. Users will have a 'Disconnected
Network Drive' for a drive that should be mapped in the login script.
Sometimes they will still be able to access the file system. Other
times they can access files EXCEPT for Access databases. Then, they
get a 'This file is outside the trusted zone' error.

And even at other times, although we only have 5 mapped drives, EVERY
alphabet letter will show a Disconnected network drive. Clicking on
these will redirect to one of the existing shares.

A reboot clears it up - until the next logoff/logon. Thought it was a
corruption in the Roaming Profiles, but after creation of a new
Roaming Profile the problem reappears after a few days. Also, this
issue is occurring for users without a roaming profile.

The logon script has worked for quite a while (years) and it has not
been changed. MS updates are handled by a WSUS server internally, and
have not pushed any updates recently as i try to troubleshoot this.

Can't figure this out! Any ideas?