Net Use Dos Error 53
Contents |
as a domain controller, web server, and active directory services. Migrate PC Hardware I needed to migrate PC hardware from one case to
System Error 53 Has Occurred Windows 10
another and then install new hardware in the primary case. Google Apps For system error 53 has occurred windows 8 Business Switch from Microsoft Office and Microsoft Exchange Server to Google Apps For Business TECHNOLOGY IN THIS DISCUSSION Microsoft Windows
System Error 53 Has Occurred Windows 2012
Server 2003 Microsoft Windows Server Microsoft Windows 2003 Join the Community! Creating your account only takes a few minutes. Join Now Hello all, I am hoping there is a http://www.symantec.com/connect/forums/error-53-computer-name-specified-network-path-cannot-be-located DOS expert out here that can help. We have a very old machine that runs MS-DOS ver6.2. It is for scientific equipment that does scientific stuff. Basically according to the guy that is requesting assistance is that it USED to be able to connect to his Server 2003 machine via 'NET USE'. I have been unable to get it to see that 2003 machine. But https://community.spiceworks.com/topic/211980-ms-dos-ver6-2-error-53 it does see six other computers running XP. When I type in 'net use * \\\\domain\\computer\\d' I get the error 53. Same goes with trying to assign a letter or adjusting the path to something like \\\\\\\\domain\\\\computer. What is in place that somewhat automates it is an old blue screen menu system that you can get to by just typing in 'net'. It auto logs in with the user and you can see those XP machines when you tab over to browse. But the Server 2003 machine is not there. Any ideas? Reply Subscribe RELATED TOPICS: MS DOS ver 5.0 MS Dos Mobile MS-DOS goes mobile   1 2 Next ► 25 Replies Datil OP Gandalf50 Mar 29, 2012 at 5:49 UTC try typing net use drive letter: \\servername\\share seems to be doubling the backslashes . 0 Sonora OP Chuck77 Mar 29, 2012 at 5:54 UTC Well, the backslashes seems to be multiplying. But I assure you, I am typing them correctly and I know what everyone will mean when they put in 15 slashes before the domain name...heh. 0 Cayenne OP Ma
here 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 http://superuser.com/questions/643239/lan-connection-dos-to-windows-7 about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for https://engineering.purdue.edu/ECN/Support/KB/Docs/WinMapNetDrive computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to error 5 the top LAN connection - DOS to Windows 7 up vote 8 down vote favorite 1 Hello community, This is my problem: I'm trying to connect a DOS-machine to a Windows 7 computer, using a LAN-crossover-cable - and it won't work. I want to access a shared directory on the Windows-PC from the DOS-machine. Best solution would be to assign a drive-letter to the shared directory and make that persistent. system error 5 I've done this before we got new hardware, establishing that connection from the DOS-machine to a Windows XP computer worked just fine. Using Windows 7 now, it won't. Details The Windows-PC Running Windows 7 (Ultimate - or Professional, not sure right now) 64bit. There are two network cards in it, one for the logon via authentication server, internet and so on - and the second one only to build a connection to the DOS-Machine. There is a separate local user specified, with name and password. There is also a shared directory in C:\ with full acces rights to exactly that user. (That's exactly what i did when using XP) The DOS-machine It's exactly that - a machine. Not a PC. It's a CNC machine with a special control software and so on. This control software is running on DOS and the network connections are built up via DOS, too. I can't tell you which version of DOS - but scanning through the directorys i tend to say that this isn't some kind of "normal" DOS-version. Seems to be something "special" or "minimal", just to get the machine software running and providing basic things. Using the mentioned XP-computer a while ago, i could use the NET commands to establish
Network Maps Contact Us Our People Staff Directory Organizational Groups Site Specialists Student Staff Services Overview E-Mail Backups Software Computer Labs Online Tools Special Projects Web Hosting FTP Account Hosting Database Hosting SharePoint Services Campus Services Support Getting Support Trouble Report Knowledge Base Short Courses Campus Support Schools College of Engineering Aeronautics and Astronautics Agricultural and Biological Engineering Biomedical Engineering Chemical Engineering Civil Engineering Construction Engineering and Management Electrical and Computer Engineering Engineering Education Engineering Professional Education Environmental and Ecological Engineering Industrial Engineering Materials Engineering Mechanical Engineering Nuclear Engineering Programs College of Engineering Honors Program First-Year Engineering Program Office of Future Engineers Engineering Leadership @ Purdue EPICS (Engineering Projects In Community Service) Global Engineering Program Indiana Space Grant Consortium Minority Engineering Program Professional Practice (Co-Op) Program Women in Engineering Program Intranet Intranet Home Committees Schools Programs Faculty Hiring Purdue > Engineering > ECN > Support > Knowledge Base > Docs > Map Network Drive or NET USE results in System Error 53 Support Getting Support Trouble Report Knowledge Base Short Courses Campus Support Information For... New ECN Users Polytechnic Users ECN Staff (restricted) Print-Friendly: E-mail this Page: Shortcut URL: Map Network Drive or NET USE results in System Error 53 Map Network Drive or NET USE results in System Error 53 (The network path was not found) By Joshua T. Hogle For instructions on how to map a network drive, please see Mapping ECN Drive using Windows XP. Applies To Windows 2000 Professional Windows 2000 Server Windows 2000 Advanced Server Windows XP Professional Summary When a user attempts to connect to a network share via the Map Network Drive option or the DOS net use command, the system returns with an error code of 53 (The network path was not found). This problem occurs when no DNS to NetBIOS name resolution was performed. It typically occurs w