Network Drive has red X and and claims it is disconnected (doesn't exist) but i can see and access files and folders
When I log off of my machine and log back on, Windows has trouble reconnecting my network drive right away. By the time I open explorer and click on the mapped drive i can see the files, but the drive shows that it is disconnected regardless. Normally this would not be a problem because all my files can still be accessed through the drive no problem, however a key program that must be used by my office, QuickBooks, refuses to accept that the drive is not actually disconnected. If I reboot my machine the problem goes away temporarily, until i log out and in. This is happening with several of the machines in my office. Other machines however are having no problems with it, and the problem doesn't seem to care which policy group the user or computer is in. -I am running Windows 7 Professional 32-bit on all my machines. -The server where the mapped is Windows Server 2008 -I have tried changing group policy to start the computer after network is configured on the client machine Removing the S: Through Hkey_Local_Machine Removing mousepoint through hkey_local_machine ensuring the atuodisconnect was turned off and a host of other things i can't think of at the moment..... HELP! PS. since i posted this the first time on Microsoft Answers (which then redirected me here) i have tried mapping the folder i want to connect to with a different letter and mapping the letter to a different folder. It seems the disconnecting issue is following the Letter (S in my case) rather than the folder. I don't know if this means S: is corrupt or if there is some program that forces whatever S: is connected to, to think it is disconnected after the computer is running for a small period of time and no one is logged on. Is there a way to monitor what is trying to access the S:?
January 11th, 2011 5:40pm

Hi, You may try to disable the firewall to have a test. Also, you may refer the following link to modify the default time-out period. http://support.microsoft.com/kb/297684 If you want to monitor what program access the folder at that time. You can use Audit Object Policy to achieve your purpose. For details information, please refer to the following link: http://technet.microsoft.com/en-us/library/cc776774(WS.10).aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
January 13th, 2011 3:58am

Thank you for your response. I already changed the default timeout period so that would not be an issue, but it did not resolve my problem. Just to be clear, because that article describes a situation in which the drive reconnects quickly, my drive is not "reconnecting". I am able to see all my files and access certain files (such as pdf or doc) but the drive still displays as disconnected and QuickBooks won't allow me to open my files as long as the computer thinks it is disconnected. I also can't delete the mapping without going into the registry each time this occurs. The second article was pertaining to Server 2003, we are running 2008. Regardless the policy is already in place to track access attempts (success and failures) for objects. It does not audit access attempts to my files. I have read that if i want audit to a particular file or folder i need to go to the properties of that folder and allow auditing but I don't want to know what is attempting to access \\server\folder_in_question. I want to know on the individual computer what is trying to access "S:" since no matter where i map that letter, the problem occurs.
January 13th, 2011 2:41pm

Hi, Do you have any Anti-Virus software? If have, please termporarily remove it. Then try to manually map this drive, does this issue persists? It is a known issue and should be fixed in SP1. Thanks for understanding.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
January 18th, 2011 8:52pm

Tried that on Monday and reinstalled yesterday. It seems the problem was a faulty install of TrendMicro on the infected machines. After installing TrendMicro correctly and removing the mappings through the registry for the last time, they now are functioning properly and all is well. Thank you very much!
January 19th, 2011 4:34pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics