Red X on Network Drive, but works completely fine.
-
This questions has been asked over and over again in various forums. But I could not find The Fix, only work around. We have our Network drive mapped via GPO. Previously, our network drives were mapped via login batch script. It was hideous. The GPO mapped drive looks much more cleaner, but recently we encounter some PC will have Red X on their network drives... but they all are still accessible. What gives? DNS? :S
-
So I found this link to Microsoft fix for auto disconnect. Is it related to the red X ?
Registry Editor***WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Use Registry Editor to increase the default time-out period. To do this, follow these steps, and then quit Registry Editor:
NOTE: You cannot use this method to turn off the autodisconnect feature of the Server service. You can only use this method to change the default time-out period for the autodisconnect feature.
Click Start, click Run, type regedit (Windows 2000 or Windows Server 2003) or type regedt32 (Windows NT 4.0), and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
In the right pane, click the autodisconnect value, and then on the Edit menu, click Modify. If the autodisconnect value does not exist, follow these steps:
On the Edit menu, point to New, and then click REG_DWORD.
Type autodisconnect, and then press ENTER.
On the Edit menu, click Modify.
Click Hexadecimal.
In the Value data box, type ffffffff, and then click OK.*** -
I have this on my machine.
I just go through and click them when I need them. Wakes them up.
-
@BRRABill said:
I have this on my machine.
I just go through and click them when I need them. Wakes them up.
It's a hit or miss for me. Right now even after clicking it, it still mark RED X, but accessible. It is annoying to some users. Others they just don't care as long as no error pop up.
-
LOL I had a user get this this morning and they called. I told them to just try it anyway.
In her case, it's likely because she puts her computer to sleep and moves between locations. The share is only available when she is in a specific location. It worked as soon as she tried it.
-
I take my laptop home every night, so same here.
-
It's normal.. I've never seen GPO drive maps not do it. It just show an X unless there's an active session open with the SMB share to that user.
-
I always get it. It's annoying. I always thought it was because it takes a while for the network card driver to kick-in and connect to the network, so Windows thinks it's not connected. By the time the PC is connected to the network, it's too late and the red X has already been put in place.
-
Yeah, we used to get it loads, happened on a domain with loads of VLAN's - seemed to be that the GPO would say to map before the connection was fully established, especially for users on higher VLAN's...Users realised if they clicked them 99% of the time they would connect though so no major dramas...
