Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Mapped Drive Shows Disconnected, But Isn't

Posted on 2007-11-29
Medium Priority
Last Modified: 2008-03-30
That is it.  The Public Share, mapped to Z: on the client computer, shows as a 'Disconnected Network Drive' ... however, it can be opened, used, written to, etc.  Strange?!!?
Question by:jigdog
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
LVL 31

Expert Comment

ID: 20373766
try the following
net config server /autodisconnect:-1

Author Comment

ID: 20373776
Try this on the server or on the client?
LVL 31

Expert Comment

ID: 20373828
on the client but i'n not sure if this works...cause the kb article is for w2k and nt4...

see here: http://support.microsoft.com/kb/138365/de
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.


Accepted Solution

geniph earned 150 total points
ID: 20386321
This is actually not an uncommon problem.  I was seeing this a lot on domains that had one DC that was intermittently not responding.  Generally, the solution for me has been to promote another server to DC and demote the one that's having communication issues (look for a lot of directory service errors indicating replication problems).

I didn't have a lot of luck with the autodisconnect setting in my environment; getting rid of a flaky DC was more effective.  The only time this particular issue caused us a problem was with specific applications that required an "always-available" connection; they saw that drive as actually disconnected, even though clicking on it reconnects it, and the application would fail.

Author Comment

ID: 21241239
Looks like it is some sort of bug in MS networking.  It eventually just went away.  Thanks everyone!

Expert Comment

ID: 22253085
I have been fighting this issue for a long time, and nothing seemed to work until today.  I have a series of steps and reasons why this happens.  I found a solution for Vista machines on an SBS domain.
Reasons why this happens:
1. You are running a custom user script from AD Profile while Domain policy is calling a different script at logon.  Ex: Profile calls: employee.bat  Domain Policy calls: SBS_LOGIN_SCRIPT.bat  both scripts have the same mapped drive: net use x: \\server\share  mapping to the same drive letter.
2. You are creating an auto connection in AD Profile to a drive being mapped by login scripting.
There are a lot out there, but I have not seen this series of steps yet.
1. Check your domain policy and AD Profile for conflicting scripts.  If you have a logon script, either add it to domain policy or AD to make them match.
2. MS KB: http://support.microsoft.com/kb/932463  I deleted all the mount points.  This seemed to work best.
3. Remove your machine from the network.  Unplug it or turn wireless off and restart so it can NOT pull anything from the network.
4. Once you login on stored credentials check Windows Explorer to make sure there are no mapped drives showing.
5. If there are no mapped drives showing, plug the machine back in or turn wireless on to access the network.
6. Start-->run-->cmd  gpupdate /force
7. If asked to logoff, choose yes.
8. Log in and check to see if the correct drives are showing and all are connected.
I have seen this not work with the gpupdate...if it does not, repeat steps 1-5.  Instead of using gpupdate, manually run the login script:
Once all drives map successfully, you are fixed.

Author Comment

ID: 22253230
Thanks for the update ... I have found MANY issues lately are related to Symantec software.  I have since been moving all of my my clients to ESET's NOD32 antivirus and receive feedback of better running machines overall.

Expert Comment

ID: 22253392
I should have mentioned this is a solution for those not using Symantec AV.  I believe it was the 9.1 version that would cause this behavior on XP based machines.  You do have an excellent point when mentioning the Symantec error with mapped drives, as I have seen that error as well many times.  I have heard many positive reviews from Network Admins with ESET's product as well as Grisoft's AVG AV.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question