Net Use Error 53 Computer Name
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet
System Error 53 Has Occurred Net Use
Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet system error 53 net view Magazine TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter
System Error 53 Has Occurred Mapping Network Drive
Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2016 System Center 2016 Windows 10 Enterprise SQL Server 2016 See all net use system error 5 trials » 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 SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows system error 53 windows 10 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 & 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
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website
System Error 53 Has Occurred Windows 8
Security SSL Certificates Complete Website Security Code Signing Certificates system error 53 has occurred windows 10 Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services
System Error 53 Has Occurred Windows 2012
Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries https://technet.microsoft.com/en-us/library/cc940100.aspx Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools https://support.symantec.com/en_US/article.HOWTO1125.html Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Error 53: The computer name specified in the network path could not be located HOWTO1125 April 8th, 2008 http://www.symantec.com/docs/HOWTO1125 Support / Error 53: The computer name specified in the network path could not be located Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Description Problem In a DOS envi
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 http://superuser.com/questions/643239/lan-connection-dos-to-windows-7 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 error 5 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 system error 5 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 softw