Open the Metro screen and type "command" which will automatically open the search bar. Right-click on Command Prompt and choose Run as administrator at the bottom of the screen. Click Start and type "command" in the search box. Right-click on Command Prompt and choose Run as administrator.
Note: Windows XP must have Service Pack 2 or later installed in order for these three commands to work properly. What does this say.. Microsoft needs to look at Windows 7 reconnection attempt commands for idle connection and see what signal is being sent to the resource to say wake up and reconnect me because it's not working..
This is a great step forward in cornering the issue. Hopefully this will help MS in coming figuring out a fix, on the Windows 7 side. I tried Zorn MapDrive and it didn't work. Then I mucked around with Credential Manager not making any changes but it worked. Then I uninstalled MapDrive and it still worked and hasn't failed since???!!! Running MapDrive manually from the Desktop, which is where I moved the shortcut from the Startup folder, didn't work.
I am having the same problem, Windows 7 x64, I am connected over VPN and can connect to shares on multiple servers, I will restart the computer and reconnect again to VPN and some shares will connect while others will not.
Sometimes clicking on one share on the same server will unlock the other share I am mapped to on the same server. Definitely a Windows 7 problem. Get on it MS, my company might just go all Mac if this continues.
Arthur, I found that the approach you suggested did not work as I, and many others, had hoped. What I did is to use the following command in a batch file:.
If the batch file is placed on the desktop, one can execute the command as needed, or immediately upon booting. If a programmable keyboard is used the batch file can be executed when tied to on of the "My Favorites" key.
Additionally, I can also disconnect a network drive quite easily without the red X displayed in Explorer. If Microsoft ever gets to the point that the Credential Manager works as it should maybe a work-around will no longer be necessary. Who knows?? I have had similar issues to all of the above ones.
As with many people I found that by opening my computer and then opening the mapped network drive would cause immediate re-connect with no dramas. As a simple workaround I created shortcuts to the mapped drives and then placed those shortcuts into Start Programs startup.
The net result is that everytime a user starts up windows everything will load and then the shortcut will be activated, thereby restoring the network drive connection. This does result in an explorer window popping open to display the contents of the network drive, but one click to close the open window and everyone can carry on as normal.
I agree. This issue was driving me crazy. I tried all sorts of things. I'd make a single change - document it and if problem was not fixed I'd usually undo the change and move on to the next change. I finally just quit doing my VPN connection but then I knew that eventually I'd have to connect up again. So, just for the heck of it I wrote a short batch file that would change to my network drives then sleep for 2 minutes and then change to my network drives again, over and over. This has been working great.
I cannot, with any certainty, state that my approach below is a solution. I, of course, made the necessary additions to the credentials manager, and mapped the drive s. This has worked for me, and maybe it will help someone else. This is on a Windows Server domain. The shared drives are on Server R2 x64 and every time the Win7 machines reboot, the mapped drives show as disconnected. Any shortcuts to documents on said drives will not work until the user manually dbl-clicks on the network drives and establishes the connection.
If it's truly an issue where Win7 attempts to connect before the a network connection is made, it would seem simple enough for MS to add a delay to that. I do run a logon. Perhaps a delay in the logon. I'll give it a shot and see. I may have a part resolution for you however.
It turns out that in the NAS the "workgroup" has to be named the same as all of your computers in order to stay visible, and to wake up on activity. So mine is always visible now, and I have mapped drives to it for file backups, my only remaining issue, is that I set folder access permissions, and pass words for each user who will be using this NAS in order to store files and backup thier computer to it. Every time that my Windows 7 machine is shut down, and restarted, it forgets the password and I get the error network drive could not be reconnected.
I have to click on the drive, enter my user ID and password and then it reconnects. Not a big deal, but it prevent my scheduled backups from running automatically. I have checked of the remember credentials box each time, but shutting down causes the dredentials to be lost so I am looking for a way, other than removing the password protection, to force the retention of the credentials.
The problem with checking the save credentials box is it was adding the computer name to the front of the user ID and making the NAS reject the User ID as invalid. So creating a credential forced it to use that one I think.
I have four Windows 7 machines and only one has displayed this problen but creating a new credential from the user account section has sorted it.
As several people have suggested, this is a timing issue between the time it takes for Win7 to connect to the network, and the time taken for the mapped drives to try and establish a connection, resulting in the red x's. Users shouldn't have to double click the disconnected drive to establish the connection, they didn't have to in XP. This is just a backwards step.
Please, please suggest a way that we can all adjust the timing values for this very, very annoying "quirk". The reason I was looking here for a fix was because I have recently taken delivery of a nice new Lenovo x and lo and behold its the drive mapping problem I've had and fixed, and forgotten that I had fixed this issue at least times in the past on Windows7 machines I have setup, and it got the point where I had to make a note to myself in an email I could later search and find to solve the problem You'll probably need to open Notepad first as Admin before it will let you save the file, then add a clean line somewhere above the first line to look something like; " Just insert the IP address of the NAS make sure its statically assigned by your router , the device name from your Credentials Manager and then the PRE to make sure its pre-assigned and is there from the the get go.
Three years on, Microsoft still hasn't fixed this. I just bought a new desktop, and I'm having the same problem. Anyway, I did as you suggested, Robberbobbles, and screwed around with Credentials. I had already set it up as static. After reading everything on this I could and coming up with my own theory 'before' messing around with 'fixes', I have found something that appears to work for me today. I cannot check whether the fix will hold into the future- yet, but it is repeatable and can be demonstrated.
Essentially as many have pointed out, win7 tries to connect to network resources before it has full network connection or at least that is how it looks and the mapped drive seems to be hit with a red 'x' and yet it is mysteriously, actually able to be accessed. My credentials were corrected with persistency at 'enterprise' etc and that solved some of the connectivity issues early on, but the red 'x' would still appear every time a full reboot was undertaken.
Then it dawned on me. It is the IP to Device Name resolution that is causing the issue. Win7 doesn't actually know or remember and would need to confirm it all anyway before connecting. It doesn't have the network connection in anycase We all know that the OS has network connection long before it tells us.
I was having this same issue and my fix was to sync the time of the server who's share I was connecting to the time of the client. The time was off by 10 minutes. After both times were synced the share connected successfully. 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 So for example, if your user name is Mike and the ip address of the network drive is If you do not know your computer name or ip address, look for where it says "Domain" in the log in box.
That is your computer name or ip address for the network drive. And make sure you check the box that says remember credentials. If this solves your problem, let Microsoft know how they should hire us young guys in the USA instead of hiring people from other countries or out sourcing our jobs to other countries.
How much is enough Mr. All machines connected all Network Drives correctly at boot-up. Windows 7 machines started to fail to connect the network drives at logon. Various "fixes" were tried, including setting Group Policy to "wait for network before logon" to no avail. At least some if not all the WIN7 machines failed to connect on boot. Logging off and back on again allowed a successful connection, as did clicking the drives in Computer.
Why is the GP "wait for network to be ready before logon" being ignored? Can anyone in Microsoft answer? I am still running WIN server on an old, very slow machine and this reconnects all drives perfectly every time, as does XP on newish "fast" machines with the same spec as those running WIN7. Then running a commandline program which read from NAS, paused the output, crashed that program, terminated using Task Manager, now drives no longer connecting. Seems some cleanup didn't happen when the task crashed.
Right now my four mapped drivess blink from red to green to red constantly. I had a long time ago issues with DHCP leases expiring prematurely from a Netgear router, trashed copy jobs in progress, also messed up drive mappings. Sounds a bit like some out-of-order condition that doesn't reproduce with Microsofts favorite scripting test tools is causing the problem to not show up in their regression testing.
Maybe someone can point out a way to completely reset the network stack without uninstalling the driver. I did try some "net" commands but it doesn't allow me to. I had the problem along the same lines.
All the various work-arounds and "fixes" did not resolve my issue, but I finally got it solved as per below. Mapped networked drives from my Windows Home Server would stay mapped on clients Windows 7 computers but required clicking on them in Explorer to "connect" them after every reboot. When rebooting, the window always popped up telling me network drives were not connected and a red X showed in Windows Explorer. This is a different issue than the connection being lost while logged on - i.
Once I clicked on the folder and it was "connected" it never lost connectivity to the mapped drive. My fix was to make the usernames and passwords on WHS and the client computers the exact same.
Once I did this then the mapped drives always connect after a reboot. Its awesum God Bless You!!! Notify me when new comments are added. Cancel reply to comment. Repairing a PC can sometimes be expensive. That is why we offer free basic in-shop diagnostics. Give one of our professional and experienced technicians a call at , and let's see what we can do for you. Here at Geeks in Phoenix , we take pride in providing excellent customer service. We aim to give the highest quality of service from computer repair , virus removal , and data recovery.
Repairing a computer can be time-consuming. That is why we base our in-shop service on the time we work on your computer , not the time it takes for your computer to work! From running memory checking software to scanning for viruses , these are processes that can take some time. If refreshing the IP address isn't enough to fix a connection issue, you can also perform a network reboot on your home network.
Open Start 2. Type in command prompt 3. Click Command Prompt 4. Wait for five minutes. Did this summary help you? Yes No. Log in Social login does not work in incognito and private browsers. Please log in with your username or email to continue.
No account yet? Create an account. Edit this Article. We use cookies to make wikiHow great. By using our site, you agree to our cookie policy. Cookie Settings. Learn why people trust wikiHow. Download Article Explore this Article methods. Tips and Warnings. Related Articles.
Article Summary. Method 1. Type in command prompt. This will search your computer for the Command Prompt app. Type in ipconfig. This command finds and displays your computer's IP information. Doing so runs the command. You should see some information appear in the Command Prompt window after a brief delay. Review your current IP address.
0コメント