Firstly, I am putting down everything here I tried that didn't work as it might also be of use to someone. If you have the same problem as I described here, you should do everything here.
I then logged onto the machine that had the folder I wanted to share thru RCP. Then I accessed a share folder on my PC. Now, when this session was alive, I opened up Computer Management and I opened the "shared folders" and sessions and saw the computer I was trying to connected, connecting to me.
Again the thinking was this would flush something out. After, I did all this it worked. I am not sure exactly what step fixed it. I was under too much time pressure to keep checkeding after I changed anything. When you are on the services applet make sure the service "Workstation" is running and is set to start atomatically. Double check your login name and password credentials to ensure they match on both the computer you are connecting from and the one you are attempting to connect to.
I encountered the same problem and got 0x when I was connecting to server. I spent hours and hours struggling with it. At last I found the solution.
Make sure Client for Microsoft Networks have been installed. If not, use the Install button to install it. If the credentials to access the remote machine changed, it is possible that Windows is still referring to the old credentials. Make sure those match too! You said you have Microsoft Security Essentials installed. I had a very similar problem and wrote a tutorial with a simple fix I found: disable the Network Inspection System which seems to cause conflicts with simple network sharing features.
I noticed Offline Files were enabled, and the status bar in Windows Explorer bottom was saying that I was working offline. I had a similar but different problem. Two Win 7 machines, one could access the shared drives on it, the other could not. Two networks with a VPN between them. Dont know if its too late for this, but I found a solution in my case. I ended up enabling all the sharing options under "Change advanced sharing settings" I then right clicked on my computer then hit the manage button.
This brought me into Computer management, i then expanded the shared folder, then clicked on the shares section. This did alot of things for me, it allowed me to redefine an absolute list of sharing folder i had a lot of sharing folders stuck in limbo, which I could now unsure. I right clicked on the drive i was having issues with, in my case E: drive. This opened up drive properties.
I clicked on the Security tab, then clicked on the Edit button. I the add button, then added a user called "guests" press ok, then goe down to the permissions section and click allow on everything. Also, if you just wanted one computer to connect, IE your laptop to your desktop you desktop being the computer that is sharing the drive then add the name of your laptop to this list.
After several hours of fooling around with this issue, it seemed to be a full version install of AVG antivirus due to an accidental installation of the evaluation version. Nuked it, and up and running perfectly. I am confident that there was a security setting in AVG that I could have simply disabled, but I do not care to reinstall it to find out. Found yet another way to try to resolve this - When trying to change the WorkGroup name to see if resetting it would help - I got a pop up message that stated the exact same computer name was used elsewhere on the network.
I changed the computer name and everything began working properly. Problem is in the "6to4 adapter" to view it goto Device Manager, click View and select Show hidden devices — expend Network Adapters — check the status of 6TO4 adapter. Also need to install this patch from microsoft.
Include Patch from Microsoft, 6to4 Adopter remover and batchfile. Shares from my Win7 Pro bit computer became inaccessible from my Vista Home bit computer that worked just fine with the earlier network. Network only, nothing else changed. Not sure just why this approach worked or what vulnerabilities have been opened up to hackers though.
Sign up to join this community. 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. It is extremely frustrating. It should not be that difficult. Any other suggestions? Wednesday, January 13, PM. That does not work, either. Plus, it would not save time since I can click Computer and then click the un-connected drive to connect.
I would, however, like it to connect automatically on start up. Friday, January 15, AM. One other thing, I disabled all firewalls to see if that might be the problem. It is not. The drive is still not reconnecting at start-up. At this point, it is not reconnecting at all. Bungle 0. Hi Jeffrey, I was looking for a cleaner alternative to the task scheduler solution proposed, so after some research, I wrote a small executable that solves the 'disconnected network drive on startup' issue, at least for me.
I'd be interested if it solves it for you as well. Edited by Mr. Bungle Sunday, March 7, PM added hyerlink. Sunday, March 7, PM. Cheers, Rhys. Friday, March 19, AM. Wednesday, March 31, AM. Bungle: The only things of which I can think that have changed recently are the Windows 7 updates that I have downloaded recently. Thursday, April 1, AM. I have exactly the same problem and have a WD 1tb NAS drive blue rings Sometimes it works perfect, but if I log off and log back on, or come back from hibernate it will give an error saying cannot connect to network drive.
I will try the Zorn Fix and see if it works Thursday, April 1, PM. I found that mine as software related. As soon as I uninstalled Zonealarm and installed a new firewall the problem went away Tuesday, April 13, PM. Jeffry From the net use link someone put up before, I created a file in notepad called reconnect. The contents of that are. Worked every time so far. Saturday, May 8, PM. Win 7 Pro bit on a Dell OptiPlex Wednesday, June 9, PM. Is this icon or its functional equivalent not available in Windows 7?
Tuesday, June 15, AM. To All, Here is what I have found. Hopes this helps everyone and Hope MS reads this and looks into it.. You know have the info on how to recreate the problem. Wednesday, July 7, AM. I've tried a multitude of things such as: downgrading the authentication level local GPO telling Avast 5 to ignore my mapped drive letters both on-demand scan and shield configs setting the DNS boxes not to sleep the hard disk none of which made a difference. Thursday, August 5, PM.
My compliments for your efforts. Could mucking around in Credentials Manager have changed something? Monday, January 3, PM. Over to Microsoft. Tuesday, January 4, PM. Tuesday, February 8, PM. Thursday, March 3, AM. Having a work around for users on a network to connect to a persistent drive is unacceptable in a business environment. Microsoft needs to look at this and fix it. Not every company has the need to script mapped drives to every user, so there should be a way to do it on an individual basis without having to use a backdoor method.
It would be really nice for a Microsoft representative to respond with either the reason it is designed this way, or an admission that it is broken and being fixed. Thursday, March 31, PM. 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.
Maybe not pretty or elegant but it worked for us. Tuesday, April 12, AM. Monday, May 2, PM. I can state that it has worked for me for more that a year. Phasr Phasr1 Sonoran Desert. Monday, July 18, PM. It's been a few months so I'm just 'pinging' this thread to see if anything new has come about I'm assuming NOT because it's happening to me also. On a VPN connection, network drives only wake up if I click into them. Friday, December 2, PM. Thursday, December 8, PM. Hi: I have sort of a similar problem, wondering if you ever got it resolved.
Anyone have a solution to this? Thanks in advance, Lance. Saturday, February 11, PM. JeffryR All I can say is thanks to this forom, it spurred me to try another approach, and it is working. That worked perfectly for me. Thanks very much. Wednesday, March 7, PM. Hi all I've tried all of the suggested solutions, apart from creating batch files to get this working Microsoft, please treat this issue with far more severity 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" It is driving end users mad with frustration. Tuesday, April 10, PM. Friday, May 25, PM. Seems to be working. Thanks, and good karma to you.
Monday, July 23, AM. It's the same problem with Windows 8, still not fixed. Monday, September 3, AM. My problem is on a network drive. We have login scripts that map several other network drives but this one is not included. I add manually and it works for the day. The next time they need it usually 2 weeks later it doesn't reconnect. And I cannot reconnect it until I remove the entry in credentials manager under vault.
I remove it from the vault and remap it and it works fine that day- repeat again 2 weeks later. Anyone have any ideas? I tried the batch file, setting in account settings.
Nothing in this post has helped. I can't therefore it is MS. Monday, September 24, PM. Robberbobbles put me onto it. No 'x's and faied reconnects! Don't be tempted to 'edit' the credentials- that doesn't seem to work. Delete them and make new ones. Edited by restorer-john Thursday, September 27, PM. Thursday, September 27, PM. Wednesday, October 3, PM.
I found the answer today - and have been looking for months. Go to Control Panel - under System settings - GoTo Power Settings Then GoTo "Change when the computer sleeps" Here is where you find "Change Advanced Power Settings" Click it You may need to click on "change settings that are currently unavailable" to make changes below 1 uncheck Hard disk - and change settings for the hard disk " while plugged in " to minutes. I can be reached at Scott. Wednesday, October 17, AM. Sunday, December 9, AM.
Can you repost the executable file. I have tried everything on this thread and beyond to no avail. The same sometimes applies to other external devices. If you have a laptop, does it happen if you leave your laptop at work?
I'm guessing that you only see it when you connect to another network and windows has to reestablish the connection when you get back to work. It doesn't have time to connect to the domain before the mapped drives policy hits.
I know it makes some people go nutty, but since there is no real problem I have never investigated a solution. The problem for me is that it is a real problem. When this message appears, my shortcuts to files on my servers do not work. I wish people would stop saying this.
If you have something that relies on that connection, it is a major problem. I've only ever come across one application that requires mapped drives to connect. For the rest we use UNC paths.
So, yes, it can be a problem, but you can usually use the UNC instead of drive letter. If it is the latter and you are using windows r2 try Group Policy Preferences If the application requires connection to shared files etc, I can see this being a problem. To mitigate this one, you could set your network connection to come up automatically, but delayed as previously stated. This isn't potentially a fix, more a work around, but should stop the application freaking out when required files etc aren't available.
In most situations I've seen the problem is simply a false report, and the first attempt to actually USE the drive works fine and corrects the windows error display. If it actually requires something special to connect to that drive after the computer has fully booted then you are looking at a different issue than I am talking about.
For what I'm discussing you can just click on the drive or access something in it and it works fine. For example, we use a mapped drive for an application here, nearly every pc uses this and nearly every time they display that message on a cold boot. I have yet to have it actually be an issue.
I get the same thing at home with mapped drives. Generally I only see it in this form meaning a false negative report when using a computer with a faster than usual boot process. At home I've got an SSD in the main machine and here at the office they're small Lenovos that never quite turn off unless you disconnect their power. So even off they still retain much of Windows in memory and boot rapidly. As far as I know this is a bug in Windows.
The connection is there but there is a red cross at the network drive. Mostly you would think it's not connected, but it is. Only Windows is fooling you a bit. We have the same problem with our laptops. I heard its a common issue. This is a known issue with Windows. It starts trying to connect to drives before it tries to fully connect to the actual network I think someone from MS should chime in on this one.
0コメント