Solved

Mapped Drive Shows Disconnected, But Isn't

Posted on 2007-11-29
8
2,827 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
Comment Utility
try the following
net config server /autodisconnect:-1
0
 

Author Comment

by:jigdog
Comment Utility
Try this on the server or on the client?
0
 
LVL 31

Expert Comment

by:merowinger
Comment Utility
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
 
LVL 2

Accepted Solution

by:
geniph earned 50 total points
Comment Utility
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
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 

Author Comment

by:jigdog
Comment Utility
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
Comment Utility
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
Comment Utility
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
Comment Utility
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

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

This article is in response to a question (http://www.experts-exchange.com/Networking/Network_Management/Network_Analysis/Q_28230497.html) here at Experts Exchange. The Original Poster (OP) requires a utility that will accept a list of IP addresses …
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…

763 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now