Recent Posts


« | Main | »

SAMBA – mount error 113 = No route to host

By Dale Reagan | August 24, 2008

8/2010 – update – Chances are that the system(s) that display this error are either older versions of Linux or older versions of the Samba suite – I have not seen this problem in months (running FC13 and latest version of Samba using Windows XP, Vista and Windows 7…)  Of course, your mileage may vary… :)

I had a working network setup with 3 machines (2 Linux boxes & a WinXP box) sharing files just fine.  The power went out (during a file transfer of course!)  When I cranked back up the machine that I was copying from could no long ‘see’ the source machine.   Using the tool  ‘smbtree’ I only see the shares from two machines, instead of from three.  Also, any attempt to mount a previously working share no longer worked.  The error that I was getting when using SAMBA I was:

mount error 113 = No route to host

Hmm, searching via the Internet did not yield any direct solutions.  The message clearly indicates that the machine that I am working from can’t ‘see’ my target machine.  Ok, time for ‘testparm’ (SAMBA tool) that provides configuration as well as ‘tree’ information.

$> testparm
Load smb config files from /etc/samba/smb.conf
Processing section “[homes]”
Processing section “[printers]”
Processing section “[pix]”
Loaded services file OK.
Server role: ROLE_STANDALONE  [[ press ENTER to continue ]]

Skipping the additional information, the last line above was the clue – the system was acting as a ‘Master Browser’; to disable this I changed  /etc/samba/smb.conf  (set ‘local master = no’), restarted the ndb and smb daemons and voila!  I can now ‘see’ and connect to the ‘missing’ system…

/etc/rc.d/init.d/smb restart
/etc/rc.d/init.d/nmb restart

Note – it is quite possible that this messages (error 113) can have other causes – look for network access related items if this does not fix your connection issue.   Seems that the Netbios network options Linux – Linux work ok; add a Windows box and you may have to switch to TCP.

Well, part two of the fix to mount a SAMBA share from a WinXP machine – when a ‘name’ won’t work, use the IP address in the mount command, i.e. something like (note the ‘\‘ means to append the next line to the command – this can be quite long…):

mount_command   #1-below    #2-below   #3-below

  1. PC_Name-IP/Share name
  2. location on server to mount the share (i.e. /mnt/pc_tmp)
  3. authentication options (username=whatever,password=whatever,other_options)


mount // \

/mnt/pc_tmp -t cifs -o username=USER_NAME,password=USER_PW


mount // \

/mnt/pc_tmp -t cifs -o username=USER_NAME,password=USER_PW, \


Topics: Web Problem Solving | Comments Off

Comments are closed.

YOUR GeoIP Data | Ip:
Continent: NA | Country Code: US | Country Name: United States
Region: WA | State/Region Name: Washington | City: Seattle
(US only) Area Code: 206 | Postal code/Zip: 98109
Latitude: 47.634399 | Longitude: -122.342201
Note - if using a mobile device your physical location may NOT be accurate...

Georgia-USA.Com - Web Hosting for Business