Driver Update. Free Online Tools. Support Center. IObit Forums. Multiple Languages. Language Help Us Translate. Driver Booster Free No. Fix the Network is connecting but Icon Shows Red X Problem on Windows Sometimes, we may notice that there is a red "X" showing on the network icon, which means that my computer is disconnected.
Method one: Check for Component Services 1. Method two: Check your Network Adapter The red cross mark issue can also be caused by the Network Adapter due to more than one connections on your computer. Method three: Check Network Driver Conditions In some cases, besides what we have mentioned above, the red cross mark on network icon may be a driver problem.
Subscribe to IObit. It seems the scripts run firstly, then the computer connect to the network, therefore it shows the Red X. It's an expected behavior.
After the computer connect to internet, try refresh Windows Explorer, will those Red-x disappear? I suspect your network connection maybe not stable recently. You can check the Event Viewer to see if there's any connection fail events. Refreshing the windows explorer doesn't connect the drives, I do have to click them.
The network connection is a wired stable connection. But for the moment I'm looking into the switches because it could have something to do with a spanning-tree configuration at switching level. But I need to do some more tests for that.
The problems only started occurring after switching to cisc switches and spanning tree. I suggest you also contact Cisco support to further look at this issue. Since I cannot test this on my side, it's hard to troubleshoot the problem. I've tried all these suggestions, but to no avail. I've also tried the following script, which only maps one drive automatically, but if I double click the. Count-1 Step 2 objNetwork.
RemoveNetworkDrive colDrives. Item i Next objNetwork. Then GoTo "Change when the computer sleeps". You may need to click on "change settings that are currently unavailable" to make changes below.
The hard drive will go to sleep after 3 hours of non-use. Make longer if needed. I don't know if all 4 changes above are needed - but one of these changes seem to be working on five of our new computers that were putting the Red X on the connected Network drives.
I hope someone at Microsoft puts this information out to the public —. I can be reached at Many thanks to TBone for the link. With the hotfix, we were rid of the problem. Needed to install on both client and server, as described in the article. Even after I posted the hotfix post in April, I still had issues. I ended up having to set my GP setting for 30 sec as described here:. I've painfully researched this problem for months trying every solution from login scripts, batch files, schedules, mapdrive, net use, group policy drive maps, a Microsoft hotfix etc but time and again the drives come up with the dreaded red X when I boot up, along with a tray message telling me that it could not reconnect all my network drives.
Some research told me to ignore it, it wasn't a problem but in my case where I'm copying music to my NAS the software just would not recognise the drives without me going in to explorer and "waking up" the drive first, a time consuming and frustrating exercise.
Frankly I was at the point giving in to the problem and waiting for the next service pack. This morning however I had an epiphany.
I created a folder in each of my mapped drives with a tiny txt file in it in my case called sync. I then rebooted and hoped. Voila, no tray message telling me it couldn't connect and no red X. My audio and video software works perfectly and many reboots later it is still working perfectly. I know it is a sort of workaround but I hope this works for you too. This problem has been a constant pain since I first mapped the drives.
Time now to move on to the next item in event viewer Hey there, it's now and the problem still persists even in Windows Google brought me to this thread and it seems there is still no real practicable, full working and permanent solution.
Moreover the problem occurs on some of my computers and on others not, even if they are on the same Windows build. There is also still no real statement why this actually occurs just the network timing thing. I really think Microsoft should fix this issue because it's a shame that in it's still not possible to integrate shares and reconnect them correctly on startup. Obviously the default behaviour does not work all the time and I have noticed this on each Windows version to some degree.
Also the proposed registry hack s available on the internet did not work for me and yes I have tried many of them. Long talk short I've now enough and therefore I created a working solution which I will now share with you.
To keep the post short and don't duplicate information please visit the project page and read through what it does and how you can use it to never ever bother with manual network share or drive reconnections. It uses basic network commands like ping and net use to reestablish shares. Feel free to test or contribute. Network Share Reconnecter or go to Github and search for "network share reconnecter".
I hope this helps some of you, at least it helps me because I also use it on all of my Windows machines with great success :. Reported issue from Microsfot. Office Office Exchange Server. Not an IT pro? Windows Client. On the Client Side Fixing this issue on the client side involves the registry change.
On the Sever Side If you are network admin who has the rights to change the server settings, you can turns off the autodisconnect feature of the server service on the server side so that all workstations that have the network map drive to the server can keep the connection live as long as they want to.
Thanks for solving my problem. Thanks David for pointing it out. You are definitely right. I needed this fix again and yours was the first post I found. After that restart your PC…Check whether the mapped drive is connected or not… Hope it works…. Please enter your comment!
0コメント