An Error Has Occurred While Reconnecting
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 29 Sep 2016 21:28:05 GMT by s_hv972 (squid/3.5.20)
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create an error occurred while reconnecting to drive microsoft windows network a Freelance Project Hire for a Full Time Job Ways to an error occurred while reconnecting local device name is already in use Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services
An Error Occurred While Reconnecting Multiple Connections To A Server
Groups Website Testing Store Headlines Experts Exchange > Questions > an error occurred while reconnecting the local device name is already in use This connection has not been restored. http://answers.microsoft.com/en-us/windows/forum/windows_vista-networking/shared-drives-not-reconnecting-error-an-error-has/9481b1a5-11ce-4703-a770-a5e8a58d0676 Want to Advertise Here? Solved an error occurred while reconnecting the local device name is already in use This connection has not been restored. Posted on 2009-10-09 Server Software Windows Server 2008 Server Hardware 1 Verified Solution 13 Comments 2,567 Views Last Modified: 2013-12-02 Hey all!, We've recently installed a windows 2008 x64 server at our second location. https://www.experts-exchange.com/questions/24800160/an-error-occurred-while-reconnecting-the-local-device-name-is-already-in-use-This-connection-has-not-been-restored.html This is the only server at the location. We have T1's between our first and second locations. Our first location has one large file server, however Instead of pulling large CADfile across the 1.5 mb line, we store the CAD files pertinent to the users of the second location on this new server. The files are being accesses via a drive mapped to a folder on this server. Recently a few users have been complaining of receiving the following message in the middle of editing a CAD project that references multiple (up to 15 or more) files on this server. : an error occurred while reconnecting the local device name is already in use This connection has not been restored. as well as this error: Connection was lost to file during this session. There may have been a network failure. Select OK in Save As Dialog to attempt to save to original name or chose a new name. I've tried quite a few things so far with no success: - The
Microsoft 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 https://community.spiceworks.com/topic/372611-network-drive-mapping-problem 7 share folder. This setup was working fine until few weeks ago. But there are http://www.pcreview.co.uk/threads/an-error-occurred-while-reconnecting-p-to-file-server-data-microsoft-windows-network-the-local.2434250/ no problems for windows 7 client computers to remap network share folders automatically. Disconnecting and remapping the network drive works on windows XP client computers. I tried different drive letter, but still returned same error. The 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 an error not been restored. Microsoft website says this is due to windows xp's lack of ability to store 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 occurred while reconnecting 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, 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'v
Mar 9, 2006. Guest Hi, I've seen countless posts about this message and have not been able to pinpoint the issue. We have multiple Windows 2000 client workstations on a LAN within the same subnet(203.57.228.X) as teh Windows 2003 server. We authenticate to an NT4 PDC w/ a logon script(below) on the same network.(203.57.228.X) Logon script on PDC: @if not "%ECHO%"=="" echo %ECHO% set NETSW=/yes if "%OS%"=="Windows_NT" set NETSW=/persistent:no %NETSW% if exist x:*.* net use x: /delete net use x: \\servername\sharename %NETSW% net use h: /home net use k: \\