Error 53 Map Drive
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 04:40:20 GMT by s_wx1131 (squid/3.5.20)
United States Australia United Kingdom Japan Newsletters Forums Resource Library Tech Pro Free Trial Membership Membership My Profile People Subscriptions My stuff Preferences sql server error 53 Send a message Log Out TechRepublic Search GO Topics: CXO Cloud Big
Error 53 Markiplier
Data Security Innovation Software Data Centers Networking Startups Tech & Work All Topics Sections: Photos Videos All error 53 solution Writers Newsletters Forums Resource Library Tech Pro Free Trial Editions: US United States Australia United Kingdom Japan Membership Membership My Profile People Subscriptions My stuff Preferences Send a http://answers.microsoft.com/en-us/windows/forum/windows_vista-networking/system-error-53-has-occurred-the-network-path-was/9511bbd8-ca11-4c1e-8d85-f7e8ce7e0fb9 message Log Out TechRepublic | Forums | Networks Networks Register Now or Log In to post Welcome back, My Profile Log Out Recent Activity FAQs Guidelines Question 0 Votes Locked system error 53 with net use By etienneh8y · 10 years ago This might be a simple problem, but I am trying to map a drive in a http://www.techrepublic.com/forums/discussions/system-error-53-with-net-use/ .bat file using net use.When I do net use \\serverA\folderI get error 53 and "The network path was not found.However, I can map the drive in explorer and can browse the server just fine in i.e. using the same path.Any thoughts? Share Flag This conversation is currently closed to new comments. 8 total posts (Page 1 of 1) + Follow this Discussion · | Thread display: Collapse - | Expand + All Answers Collapse - Where's the drive letter? by jpenrose · 10 years ago In reply to system error 53 with net ... http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/net_use.mspx?mfr=true -J- 0Votes Share Flag Collapse - Any drive letter by etienneh8y · 10 years ago In reply to Where's the drive letter? Typo in the post, woops. I tried a variety of different drive letters, including ones that I successfully mapped to other servers (I unmapped them before trying with this one).Sorry for the confusion. 0Votes Share Flag Collapse - Does the folder exists? by sbx14 · 10 years ago In reply to sy
for 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 a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today https://www.experts-exchange.com/questions/21611903/System-error-53-has-occured-during-attempt-to-map-network-drive-via-command-prompt.html Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > "System error 53 has occured" during attempt to map network drive via command prompt Want to Advertise Here? Solved "System error 53 https://sites.google.com/site/synologysupport/english/mapping-issues/q1--how-i-solve-error-53-when-creating-a-mapped-drive has occured" during attempt to map network drive via command prompt Posted on 2005-10-28 Windows Networking 1 Verified Solution 6 Comments 4,094 Views Last Modified: 2010-07-27 I am trying to create a simple logon script to map certain network dirves error 53 for each user group. For some reason I can not map to one share on a certain server using the command promt; however, I can map to it using the GUI wizard. I can map to qll other shares on the same server using the command promt. The server is a Win 2003 server, and the client is Win XP pro. Here is a copy of the script. net time \\main-fs /set /yes net use m: \\main-fs\all users net use error 53 map F: \\main-fs\Fiserv net use L: \\exchange\easylndr net use t: \\main-fs\tele5 net use g: \\main-fs\gl \\main-fs\all users is the share that I am having trouble with. 0 Question by:kellytroym Facebook Twitter LinkedIn Google LVL 82 Active today Best Solution byoBdA That's simply because the "net use" command you're using is looking for the share "\\main-fs\all". Make that net use m: "\\main-fs\all users" (note the quotes) and you're good to go. Go to Solution 6 Comments LVL 2 Overall: Level 2 Windows Networking 1 Message Expert Comment by:ChicagoMikeW2005-10-28 53 error man you are screwed. ;) just kidding. here is a MS artical about it http://support.microsoft.com/?kbid=227283 also try using \\IP_ADDRESS\share name 0 Message Author Comment by:kellytroym2005-10-28 The article didn't help, it is telling me to map it through the GUI. I know I can do that, but I want to run scripts to map the drives. When I try mapping with \\IP_Address\share name I get the following: Logon failure: unknown user name or bad password 0 LVL 82 Overall: Level 82 Windows Networking 23 Message Active today Accepted Solution by:oBdA2005-10-28 That's simply because the "net use" command you're using is looking for the share "\\main-fs\all". Make that net use m: "\\main-fs\all users" (note the quotes) and you're good to go. 0 Message Author Comment by:kellytroym2005-10-29 oBda, Thank you very much you just releive a major headache of mine. As you can tell I have no formal
does not work, then use the MSconfig signature below (and attachment): First please ensure the Let's try this1. Go to Start>>Run, and type: msconfig2. Once the window pops up, see the "MSConfig 1" picture in the attachment. Under the "General" tab, do the same as in "MSConfig 1".3. Then go to the "Services" tab.4. First click on "Hide All Microsoft Services", then press "Disable All" (see the "MSConfig 2" picture).5. The remaining applications should be non-Windows applications. Mentally divide the remaining applications into 2 groups (groups A and B), and the disable one of the groups (let's assume we disabled group A).6. Try using the desired Synology application to see if it works.Works:a. If step 6 from above works, then that means the non-Windows application that is causing this disruption is one or more of the applications in group A.b. Using group A, repeat steps 5 and 6. Narrow down the applications until you find the one that is causing the disruption.Does Not Work:a. If step 6 does NOT work, then that means the non-Windows application that is causing this disruption is one or more of the applications in group B.b. Using group B, repeat steps 5 and 6. Narrow down the applications until your find the one that is causing the disruption. ČUpdating... ċErrorCode53.rar (520k)Synology Online Support, Dec 10, 2008, 7:40 PMv.1ď ċMSConfig.rar (114k)Synology Online Support, Dec 10, 2008, 7:40 PMv.1ď Comments Sign in|Recent Site Activity|Report Abuse|Print Page|Powered By Google Sites