Net Use System Error 85 Windows Xp
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 04:26:04 GMT by s_wx1157 (squid/3.5.20)
19, 20113 Share 0 0 Windows provideNet use command to mapor disconnect network drive. Type the following command in the command prompt (Start > Run > {type} cmd {enter}) NET
Hklm\system\currentcontrolset\control\sessionmanager\protectionmode
USE [drive] [shared path location] /persistent:no system error 53 has occurred net use
System Error 1314
Persistent:Yes ->To restore the current connections at each logon, regardless of future changes
Disconnect mapped drives: Type Command prompt>: NET USE * /DELETE [Deletes all the mapped drives from the computer] http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/system-error-85-has-occurred-the-local-device-name/d8bfc6c1-2476-4055-920d-89813fd6494d NET USE [drive] /delete -> deletes the mapping to the particular drive. Common Errors: - System error 85 has occurred. The local device name is already in use->This means that you already have something mapped at that name. It happens a lot when you use logon script to map drives https://blogs.msdn.microsoft.com/rajakedar_ganta/2011/08/19/system-error-85-has-occurred-the-local-device-name-is-already-in-use-net-use/ or whennet use /persistent:yes is generally used to map those network drives. Resolution:1. Use net use /persistent:no in the logon script. 2. Add "net use * /d" command line in the top of the logon script so that the script will clean the all old mapping first. 3. Restart the machine (if that is an option) How to do the above Via UI: Start > Select Computer Right Click Tags map drive using dos System error 85 has occurred. The local device name is already in use Comments (3) Cancel reply Name * Email * Website Walt says: January 27, 2012 at 2:11 pm I use "IF NOT EXIST M:NUL NET USE M: ….". So, the NET USE should only execute if the M: drive doesn't already exist. It works 99% of the time, but fails 1% of the time. Why? Reply will says: August 8, 2012 at 8:32 pm Windows provide Net use command to map or disconnect network drive. Type the following command in the command prompt (Start > Run > {type} cmd {enter}) NET USE [drive] [shared path location] /persistent:no Persistent:Yes -> To restore the currhere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about http://stackoverflow.com/questions/5914282/networked-drive-in-purgatory-after-net-use-start-up-script hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Networked drive in purgatory after `net use` start-up script up vote 2 down vote favorite I have a BAT file that runs on startup via the group policy on system error an internal server. The BAT executes a nant script which then maps several external locations via net use command. Until now, all mappings have been to external computers that are part of a different domain via public IPs. net use e: \\111.111.111.111\someshare$ /persistent:yes net use f: \\111.111.111.222\someshare$ /persistent:yes net use g: \\111.111.111.333\someshare$ /persistent:yes This has been successful. Now, I added a new computer that is part of the same network and domain as the internal server. While the system error 85 old mappings continue to work, the new mapping does not. net use h: \\anothercomputer\d$\somefolder /persistent:yes I only know that this doesn't work because subsequent scripts that depend on this drive mapping are all failing, saying that the location doesn't exist. If I try to run the same connection script manually, net use says System error 85 has occurred... The local device name is already in use. Ok, so it mapped already somewhere, somehow. So I try to unmap it using net use h: /d and that fails. The network connection could not be found. So I cannot map it. I cannot unmap it. Apparently it exists in some networking purgatory. What is going on here? How can I get this new location mapped and visible to my scripts? networking command-line nant network-share share|improve this question edited May 13 '11 at 22:10 asked May 6 '11 at 16:25 Jeff 6,57453573 1 well, mapping to a $ administrative share is not so secure. is it possible for you to define the somefolder as a shared folder ? then you can use something like: net use h: \\anothercomputer\somefolder /persistent:yes and this would probalby work. –Menahem May 15 '11 at 8:26 Yes, I can set up shares. Trying it now. –Jeff May 16 '11 at 15:04 Didnt appear to change anything. I am going to get SysInternals so I can r