Dos Error 53
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 Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual dos extended error 53 Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins error 53 the computer name specified Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1 Enterprise See all trials dos error 5 » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses
Dos Error 64
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 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 & dos error 4 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 particular computer name. Error 53 can also occur when there is a problem establishing a NetBIOS session. To distinguish betweenthese two cases, use the following procedure: To determine the cause of an Error 53 message From the Start menu, open a command prompt. At the command prompt, type: net view \\< hostname > where < hostname > is a network resource you know is active. If
360 games PC games dos error level Windows games Windows phone games Entertainment All Entertainment
Dos Error Code 1
Movies & TV Music Business & Education Business Students & educators
Dos Error 2
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://technet.microsoft.com/en-us/library/cc940100.aspx Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/108479 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
services company. Wi-Fi Network Expansion - Lake Street Deploy access points to a remote site that functions as a DR site and also is a power generating facility https://community.spiceworks.com/topic/211980-ms-dos-ver6-2-error-53 with Jet Turbine engines. New Domain Controllers - 2012R2 Current DC's are 2008R2 and http://superuser.com/questions/643239/lan-connection-dos-to-windows-7 2003 -- needed new one in our main HQ, and one to replace the old 2003 VM. TECHNOLOGY IN THIS DISCUSSION Microsoft Windows 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 DOS expert out dos error 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 it does see six other computers running XP. When dos error 5 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 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
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 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 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 a connection using a drive letter, the shared network path - and the specified userdate, name and password. That just worked. That so configured shared directory was visible and usable when running the machines control software - that's the goal of all this. Current situation Trying to build up the c