An Error Occured While Reconnecting To
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 30 Sep 2016 05:48:50 GMT by s_hv902 (squid/3.5.20)
Windows XP Join the Community! Creating your account only takes a few minutes. Join Now Hi All, I am having problem with re-mapping network drives automatically from windows XP client computers to a windows 7 share folder. This setup was working fine until few weeks an error occurred while reconnecting to network drive windows 7 ago. But there are no problems for windows 7 client computers to remap network share folders
An Error Occurred While Reconnecting To Microsoft Windows Network
automatically. Disconnecting and remapping the network drive works on windows XP client computers. I tried different drive letter, but still returned same error. The an error occurred while reconnecting to drive error says An error occurred while reconnecting L: to \\serverename\sharename Microsoft Windows Network: The local device name is already in use. This connection has not been restored. Microsoft website says this is due to windows xp's lack of ability to store http://answers.microsoft.com/en-us/windows/forum/windows_vista-networking/shared-drives-not-reconnecting-error-an-error-has/9481b1a5-11ce-4703-a770-a5e8a58d0676 credential information and the solution is remapping the network drive after logoff and logon. So is there any way to remap the network automatically on computer startup? Many Thanks. Reply Subscribe View Best Answer RELATED TOPICS: Network Drive Mapping Help Network Drive Mapping Issue Can't delete Network Drive Mapping!   12 Replies Serrano OP Helpful Post Johndroid Aug 21, 2013 at 8:27 UTC You could make a batch file to run on start-up or remote in to run it, https://community.spiceworks.com/topic/372611-network-drive-mapping-problem there is a guide here from Spiceworks on creating a batch file to map network drives: http://community.spiceworks.com/how_to/show/1487-how-to-create-a-batch-file-for-network-drive-mapping 0 Jalapeno OP Helpful Post jeeves555 Aug 21, 2013 at 10:10 UTC As John has said, a batch file is the best way to do this, especially in a logon script. I put net use /delete x: at the top too, replace x: with your drive names just to make sure they're disconnected. 0 Habanero OP Best Answer David1618 Aug 21, 2013 at 12:00 UTC If you're on XP home, then there is no ability to automatically connect network drives without authentication. If you have the network drives persistently mapped, then the problem could be that you need to disconnect the drives before you connect them. There are different ways of doing this depending on how you're mapping the drives... In a VBS script, it would a a line like objNetwork.RemoveNetworkDrive "q:" In a batch file it would be something like net use k: /delete XP pro can store credential information. I've not used it in this environment. 0 Thai Pepper OP Matt Bartle Aug 21, 2013 at 2:02 UTC I've seen that error and been able to fix it with ipconfig /flushdns, ipconfig /registerdns. In my case it had nothing to do with credentials. 0 Datil OP James for Microsoft Aug 22, 2013 at 12:31 UTC Brand Representative for Microso
we highly recommend that you visit our Guide for New Members. Solved: Microsoft Windows Network Error Discussion in 'Networking' started by beginHack, Nov https://forums.techguy.org/threads/solved-microsoft-windows-network-error.1025275/ 3, 2011. Thread Status: Not open for further replies. Advertisement beginHack Thread Starter Joined: Jul 2, 2009 Messages: 5 I have a server computer running Windows Server 2008 R2 Standard operating system with 4 client computers connected to the network running Windows 7 Professional operating system. All worked great yesterday. This morning, one of the client computers encountered this error: An error occurred while reconnecting an error F: to \\SERVER\Data Microsoft Windows Network: The user name could not be found. This connection has not been restored. No updates or changes have occured between yesterday and today and the three other client computers have no similar problems. Just this one client has the error. Any suggestions on what to do? beginHack, Nov 3, 2011 #1 Sponsor LagunaGTO Account Closed Joined: Jan 27, while reconnecting to 2011 Messages: 139 How are they authenticating to the server? Go to Control Panel and click on Credential Manager - is anything listed under Windows Credentials? LagunaGTO, Nov 3, 2011 #2 beginHack Thread Starter Joined: Jul 2, 2009 Messages: 5 Thank you for the reply LagunaGTO. There is nothing listed in the Credential Manager. LagunaGTO, I originally checked the Credential manager on the server and not on the problem computer. Had I checked it on the correct computer, I might have had the solution sooner. Thank you for your help. beginHack, Nov 3, 2011 #3 LagunaGTO Account Closed Joined: Jan 27, 2011 Messages: 139 Can you ping the server? Is this a domain? If so, can you log in as someone else and access the server? LagunaGTO, Nov 3, 2011 #4 beginHack Thread Starter Joined: Jul 2, 2009 Messages: 5 Yes I can ping the server and other computers connected to the network from the problem computer. The computer is connected to a domain and the computer gets the same results if someone else logs on with a different user name. The new user name can not connect to the network from th