Are you using login scripts to map the drives? You can deploy the registry through GPO as others have stated, just make sure the change doesn't open your computers for security vulnerabilities with this registry change. There's a couple of ways to do this.
If the registry key is required this can be pushed out via group policy. You would set the registry key up within here and it would push it out. We set up each of the mappings and apply it to our staff OU. If you go down this route make sure you click on "Run in logged on users security context" as we have found it doesn't work without this. Oh, and just to cover all of the bases, make sure you have the latest Windows 10 administrative templates!
To continue this discussion, please ask a new question. 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. No more messages popping up and needing to click on the folder in explorer to ensure the drive is connected.
This probably won't help the OP, but may help other folks that are trying an internet search on this problem. Open Control panel - user Account -manage your credentials -Add a windows credential-. 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 As well all know this problem has not been fixed. I tried to sync the file through sync center but get an error folder can't be synchronized because it resides on a remote drive. What can I do to fix the problem with a mapped drive that won't reconnect on boot up.
I put my credentials in manager still no luck. Does anyone have a fix. I have tried everything suggested, connected with the name of the device as well as the IP address. I do have it at a static IP. The local device name is already in use. The network path was not found. Once we know our mapping cmd line is good, save to notepad, One can use echo off at the start but not absolutely needed, placing pause at the end will keep the Cmd screen open, this file will open and close fast, if you want to see what is happening add pause Make certain the first part of the line is the start, place the cursor behind the word "net" and hit back space until it there are no spaces at the start.
Once all is good save as map. Now when you log into your PC, that file will excute, mapping the drive. If your using a lap top and your not on the network which this file is attempting to map, you should recieve an error, if you place pause at the end it will show otherwise the cmd window will go away.
There are a few other ways to have this file execute on login, this is the simplest way. We have the same problem at work.
Extensive googling has shown that this is an on-going problem not related to any WD device, and we don't have any WD devices. Here is the only solution I have found that works.
A bit of a pain, but it works. Details of the batch file are already discussed above, so I won't repeat them. On the link that starts your application e. Also note the icon. Use Net. Set it as Persistent. And, no, doing so won't cure the problem! The icon you want is probably in the executable file that the Target you saved points to.
Navigate the dialog to that file and select the icon. Sometimes you will get a message that the drive is in use. If so, it is already mapped. Just select the appropriate Y or N. When the dialog is exiting after your program is finished , when it tries to unmap, you may get a dialog that files are open.
I have found that this tends to not be true, despite the message. You can click Y or N. The next time the dialog is run it will try to unmap the drive, so either way it's not a problem. The benefit of this approach is that for non-techies, everything pretty much looks and works as expected.
They click on the link they usually click on, and they don't have to remember any weird ritual to get the program to work. From everything I can tell with this issue it is a problem between Windows and Nix environments.
Another Issue is with windows not remembering my login credentials for my Linux server shares. This is what happens when you try to corner the market, and don't get me started with windows not dual booting with Linux unless you install windows first and Linux second. You need to Login to your Western Digital Drive. Select Security and Set the proper permissions.
Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:.
Archived Forums. Windows 7 Networking. Sign in to vote. I have read a lot of posts on this, but here is my problem. I am using Windows 7. The drive is mapped correctly. I have added credentials through the credentials manager in the Control Panel. The credentials are being remembered after logoff, shut-down and re-boot. If I shut-down and re-boot immediately, or, perhaps, within a 12 hour period, the machine will reconnect to the mapped drive at logon.
However, if more than 12 hours elapses between shut-down and re-boot, I get the now-very-familiar "could not connect to all network drives" message and both folders of the NAS are shown to be disconnected in Computer. Of course, a click on the correct folder will connect.
That is a pain, and the rest of my family that uses this computer will not remember to do this every time. It becomes quite a mess if iTunes is loaded with the NAS disconnected, since the music library obviously will not load and will then need to be re-selected the next time the program is started. I do not expect the other family members to be able to remember each of these steps. Thus, does anyone know each and every thing that must be done in Windows 7 to ensure that the mapped network drive will perpetually reconnect at logon?
I say "each and every thing" because I have found that this is a highly iterative process. I keep discovering additional steps that need to be taken upon further and further "research.
Thanks in advance. Saturday, December 26, PM. Thursday, December 31, AM. Tuesday, December 29, AM. As I recall, they use a Linux system with samba. I could be wrong but I think I uncovered that when I was having the same problem.
I just gave up using the World Book. Not only would the drive disconnect but the computers couldn't find the device on the network anymore. It would just fall off the network but if I unplugged the power from it and restarted it it would become accessible for a short while.
It now collects dust. I was going to remove the tandem GB drive and use them else where but never got around to it. The bottom line is your not a victim of the Microsoft server side mapped resource time out dilemma. Tuesday, December 29, PM. Cory: Based on your response, I posted a variation my original message onto a WD forum. WD's official "support," whether by phone or by e-mail, is not real helpful. They blamed Windows for the problem, offered no real solution and only perpetuated the infinite loop to nowhere that is experienced by many people trying to solve what should be a simple problem.
A Google search of "reconnect mapped drive" yields a whole of complaining about mapped drives that do not reconnect at logon.
I have tried many suggestions, none of which have yet to solve the problem. Hi guys, I was having this problem with some vista machine, here is the fix I got from microsoft. It is some king of update but it works just fine. Look at it hope it works.
Thursday, December 31, PM. Does not apply, its just for vista. By marking a post as Answered, or Helpful you help others find the answer faster. Friday, January 1, AM. Arthur: I have tried this several times, to no avail. The information concerning the "net use" command is somewhat ambiguous, and I may have written it incorrectly. If we assume the following which do not correspond to the actual information on the system , how would the "net use" command look: Drive letter: z Server: Sunday, January 10, PM.
Tuesday, January 12, AM. Network address: Wednesday, January 13, AM. Arthur: It is still not working. I have re-written the command several different times, in several different ways.
I checked the option "If the task fails, restart every" 1 minute. The task, however, does not restart, according to the log. I am running a very simple network here. The computer logs onto the network every time on start-up, without any issue at all. I have disabled "power save" in the NAS, so it is not hibernating, This has been going on since September.
Sometimes files, folders, and subfolders in Windows can be hidden. When this happens, users cannot see them at all, even when they go to select the appropriate drive letter. This is what happens when files or folders are hidden on the NAS drives, and it can easily happen to mapped network drives.
Once you have finished this process, all hidden drives, folders, and files should appear in their original location. Step 1. Download and run AnyRecover software and select the network drive that you would like to restore files from. The program will start to scan for your deleted, missing, or hidden files. Step 3. Once finished scanning you will see a list of all your recovered files, folders, and documents.
0コメント