Net Use Samba Error 53
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet system error 53 has occurred mapping network drive Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions
System Error 53 Net View
TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads system error 53 has occurred net use Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2016 System Center 2016 Windows 10 Enterprise SQL Server 2016 See all trials » Related Sites
System Error 53 Windows 10
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 Server Certification (MCSE) Private Cloud Certification (MCSE) system error 53 has occurred windows 8 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 and is not being maintained. This documentation is archived and is not being mainta
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 02:27:44 GMT by s_wx1206 (squid/3.5.20)
client. It works ok from the Fedora server...I.e. I can access the SAMBA shares from the server. I can ALSO access http://forums.fedoraforum.org/archive/index.php/t-54405.html to XP shares from the server (here-in called gene-photo). when I do net http://serverfault.com/questions/541625/unable-to-browse-to-samba-shares use:-------------------------------------------------------- C:\>net use x: \\192.168.1.220\gene Enter the user name for '192.168.1.220': gene Enter the password for 192.168.1.220: System error 53 has occurred. The network path was not found. ----------------------------------------------------------------------------- Same thing when I use gene-photo instead of the IP gene-photo's IP is 192.168.1.220 lmhosts and hosts files are at the bottom error 5 of this post in the trascript. What do I need to change to make this work? Any reasonable help would be appericated. :) :) Gene The transcript below is from a XP Laptop with wireless call SOXPL2501 (ip is 192.1658.1.208) -----------------------slightly edited for readability---------------------- C:\>ping 192.168.1.220 Pinging 192.168.1.220 with 32 bytes of data: Reply from 192.168.1.220: bytes=32 time=2ms TTL=64 . . . Ping statistics for system error 5 192.168.1.220: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 2ms, Average = 2ms C:\>ping gene-photo Pinging GENE-PHOTO [192.168.1.220] with 32 bytes of data: Reply from 192.168.1.220: bytes=32 time=2ms TTL=64 . . . Ping statistics for 192.168.1.220: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 2ms, Average = 2ms C:\>nbtstat -A 192.168.1.220 Wireless Network Connection 2: Node IpAddress: [192.168.1.210] Scope Id: [] Host not found. Local Area Connection: Node IpAddress: [0.0.0.0] Scope Id: [] Host not found. C:\>route print 192.168.1.220 ===================== Interface List 0x1 ........................... MS TCP Loopback interface 0x2 ...00 0c f1 24 69 2b ...... Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter - Packet Schedule r Miniport 0x3 ...00 0d 60 af 26 c4 ...... Intel(R) PRO/1000 MT Mobile Connection - Packet Scheduler Miniport ====================== ====================== Active Routes: Default Gateway: 192.168.1.1 None Persistent Routes: None C:\>nbtstat -nSs Wireless Network Connection 2: Node IpAddress: [192.168.1.210] Scope Id: [] NetBIOS Connection Table Local Name State In/Out Remote Host Input Output --------
Start 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 Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. 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 Unable to browse to SAMBA shares up vote 0 down vote favorite In my enviroment I have CentOS 5 installed with CUPS and SAMBA. I am unable to browse any SAMBA shares from any machine. From Windows 8 and Windows Server 2008, I have tried the commands below net view \\veculx1 net view \\172.19.50.30 However I receive the same error on both commands: System error 53 has occurred. The network path was not found. From another CentOS server I tried running SMBCLEINT -L \\172.19.50.30 Error connecting to 172.19.50.30 (No route to host) Connection to 172.19.50.30 failed (Error NT_STATUS_HOST_UNREACHABLE) Pinging the server resolves and replies. I can also telnet and SSH into the server without issue. Running testparm smb.conf shows no errors in my setup. Below is the contents of smb.conf # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # For a step to step guide on installing, configuring and using samba, # read the Samba-HOWTO-Collection. This may be obtained from: # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf # # Many working examples of smb.conf files can be found in the # Samba-Guide which is generated daily and can be downloaded from: # http://www.samba.org/samba/docs/Samba-Guide.pdf # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may