Solved

Mapped Drive Shows Disconnected, But Isn't

Posted on 2007-11-29
8
2,912 Views
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?!!?
0
Comment
Question by:jigdog
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 31

Expert Comment

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

Author Comment

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

Expert Comment

by:merowinger
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
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 2

Accepted Solution

by:
geniph earned 50 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.
0
 

Author Comment

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

Expert Comment

by:datadrew
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.
Solution:
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:
start-->run
\\servername\sysvol\domain.local\scripts\loginscript.bat
Once all drives map successfully, you are fixed.
0
 

Author Comment

by:jigdog
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.
0
 
LVL 3

Expert Comment

by:datadrew
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.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

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

Resolve DNS query failed errors for Exchange
An article on effective troubleshooting
This tutorial gives a high-level tour of the interface of Marketo (a marketing automation tool to help businesses track and engage prospective customers and drive them to purchase). You will see the main areas including Marketing Activities, Design …
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…

770 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