The file should be run at a regular but not at an elevated command prompt because it should be run at the same privilege as Windows Explorer:. All workarounds should be executed in standard user security context. Executing scripts in an elevated security context will prevent mapped drivers from being available in the standard user context. This workaround works only for the device that has network access at logon. If the device has not established a network connection by the time of logon, the startup script won't automatically reconnect network drives.
Neil Laplink. Get answers from your peers along with millions of IT pros who visit Spiceworks. Popular Topics in Windows 7. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Matt Sep 30, at UTC. Remy Sep 30, at UTC. Thai Pepper. DanaR This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Gary Sep 30, at UTC. Lamen Sep 30, at UTC. Yahtzee Sep 30, at UTC.
Remy wrote: It's just windows getting ahead of itself. Instant Joel wrote: Remy wrote: It's just windows getting ahead of itself. Matt wrote: Instant Joel wrote: Remy wrote: It's just windows getting ahead of itself. Is this for your mapped drives or everyone on your network?
Doughnut This person is a verified professional. Netzer Apr 25, at UTC. This was the solution that appears to have helped quite a few people. Exit Registry Editor, and then restart the computer.
Simpuhl This person is a verified professional. I tried this, no help. I have an SSD and it literally just loads way too fast. 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. 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. When you talk about "navigating", I'm assuming you're talking about a File Open dialog or somesuch. If that's not what you're using, try mapped drives and UNC paths with a common file dialog opened from your VB6 app. Show 1 more comment. Active Oldest Votes. Right-click EnableLinkedConnections, and then click Modify.
In the Value data box, type 1, and then click OK. Exit Registry Editor, and then restart the computer. Improve this answer. Motes Motes 3, 1 1 gold badge 22 22 silver badges 22 22 bronze badges. Add a comment. But this fails on Vista and later due to Session 0 Isolation! I believe that's what you are after here. Community Bot 1 1 1 silver badge.
Bob77 Bob77 13k 1 1 gold badge 26 26 silver badges 37 37 bronze badges. Thank you for your input. In this case the drive mappings were initially instituted as local mappings by the logged-in user. I assumed that may be causing the issue and then had the network support people set the user up to configure the mappings to be set by either GPO as you suggest or via login script.
In either case the result is the same. The logged in user can see and navigate to the mapped drives and has access to all files using Explorer or via the command-line. However, the VB6 application can neither "see" or access the shares at runtime. Generally the login script only sets mappings for the unelevated user logging on.
Exactly what credentials does the VB6 program run with?
0コメント