Dos Error 53 Network
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet
Dos Error 2
Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs dos error handling Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server
Dos Error Number 5 Occurred While Trying To Create Directory
2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet http://www.symantec.com/connect/forums/error-53-computer-name-specified-network-path-cannot-be-located Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find https://technet.microsoft.com/en-us/library/cc940100.aspx technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Library Wiki Learn Gallery Downloads Support Forums Blogs We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Windows 2000 TCP/IP TCP/IP Troubleshooting Unable to Reach a Host or NetBIOS Name Unable to Reach a Host or NetBIOS Name Error 53 Error 53 Error 53 Error 53 Cannot Connect to Remote Systems Using Host Name TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Error 53 The most common symptom of a problem in NetBIOS name resolution is when the Ping utility returns an Error 53 message. The Error 53 message is generally returned when name resolution fails for a par
Windows 2003 Join the Community! Creating your account only takes a few minutes. Join Now Hello all, I am hoping there is a 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 https://community.spiceworks.com/topic/211980-ms-dos-ver6-2-error-53 scientific stuff. Basically according to the guy that is requesting assistance is that it USED to be http://superuser.com/questions/643239/lan-connection-dos-to-windows-7 able to connect to his Server 2003 machine via 'NET USE'. I have been unable to get it to see that 2003 machine. But 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 dos error 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 dos error 5 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 Mark1950 Mar 29, 2012 at 5:57 UTC netbios issue? or WINS? 0 Datil OP Gandalf50 Mar 29, 2012 at 5:58 UTC hehe check here http://www.myitforum.com/articles/5/view.asp?id=960
0 Datil OP Jono Mar 29, 2012 at 7:23 UTC You should be able to see what sharename it is trying to connect to in the batch file it is use eg Net USE G: \\\\\\\\COMPNAME\\\\SHARENAME and then check on the 2003 box that it is sharing that out. EG NET SHARE To see what is running on the PC at the dos prompt type Edlin Autoexec.bat Type L to list the lines of text Type Q to exit 0 Serrano OP OceanV Mar 29, 2012 at 8:16 UTC Error 53 is a 'network name not found' error. Like they indicated above, find out what share it's trying to open here's a list of dos errors http://www.computerhope.com/xdoseror.htm if you can get to the share, maybe try assigning a drive letter to it and see if it will work that way also another way is on the server side, assign the drive letter, then from the dhere 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 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 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 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. 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 s