Re: mount error 113 = No route to host

rbw Thu, 03 May 2007 15:51:16 -0700

James G. Sack (jim) wrote:

rbw wrote:

I'm running into a problem that has me scratching my head...


This works to the server I want to get to:
ftp cca-csis.[workdomain].com

and this too :
ssh -l rbrwill cca-csis.[workdomain].com
ssh -l rbrwill 192.168.17.25


And this works to another server on the LAN:
sudo mount -t cifs //gondor.[workdomain].com/konica
~/smb4k/gondor.[workdomain].com/konica/ -o rw,user=rwilliams

And this works to that same server by IP number:
sudo mount -t cifs //192.168.17.4/konica
~/smb4k/gondor.[workdomain].com/konica/ -o rw,user=rwilliams


But neither of the following 2 work to the server that I need to get to
on the LAN via cifs mount:

sudo mount -t cifs //192.168.17.25/rbrwill/
~/smb4k/gondor.[workdomain].com/rbrwill/ -o rw,user=rbrwill
Password:
mount error 113 = No route to host
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

sudo mount -t cifs //cca-csis.[workdomain].com/rbrwill/
~/smb4k/cca-csis.[workdomain].com/rbrwill/ -o rw,user=rbrwill
Password:
mount error 113 = No route to host
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)


I have a CentOS server at home in the same condition as the one at work
and "cifs" mount does work there. I think I am a little thrown by the
idea that I can ftp and ssh to the box by IP and by hostname, and
therefore routing is good, but I get a "no route to host" when I try to
"cifs" mount that same CentOS box at work.

Googling this gets me nowhere...
What am I missing?


I might want to try

 smbclient -NL 192.168.17.25
 smbclient -NL cca-csis.[workdomain].com

then try

 smbclient -Urbwill -L 192.168.17.25
 smbclient -Urbwill -L cca-csis.[workdomain].com

just to see if there's any extra clues.

You might also want to add -d3 (or -d9, or ?) to get client debug messages.

If it's really an auth problem (although it seems to be lower level),
then you might get some clues from wbinfo and/or net from the
samba-common package (in RH systems, at least))

Are the servers Windows or samba?
If samba, then you can use debugging at that end via the smbcontrol
command.  I don't remember the syntax -- it is a bit fussy.

Regards,
..jim

Thanks Jim...

I got this:

$ smbclient -NL 192.168.17.25

params.c:Parameter() - Ignoring badly formed line in configuration file:*passwd:*all*authentication*tokens*updated*successfully*params.c:Parameter() - Ignoring badly formed line in configuration file:*passwd:*all*authentication*tokens*updated*successfully*

Error connecting to 192.168.17.25 (No route to host)
Connection to 192.168.17.25 failed

$ smbclient -Urbwill -L 192.168.17.25

Error connecting to 192.168.17.25 (No route to host)
Connection to 192.168.17.25 failed

I also got this with the debug:
$ smbclient -d3 -Urbwill -L 192.168.17.25
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"

added interface ip=192.168.17.34 bcast=192.168.17.255 nmask=255.255.255.0
sys_gethostbyname: Unknown host. ath0
can't determine netmask for ath0
added interface ip=172.16.48.1 bcast=172.16.48.255 nmask=255.255.255.0
added interface ip=172.16.168.1 bcast=172.16.168.255 nmask=255.255.255.0
sys_gethostbyname: Unknown host. wifi0
can't determine netmask for wifi0
Client started (version 3.0.24-3.fc6).
Connecting to 192.168.17.25 at port 445
error connecting to 192.168.17.25:445 (No route to host)
Connecting to 192.168.17.25 at port 139
error connecting to 192.168.17.25:139 (No route to host)
Error connecting to 192.168.17.25 (No route to host)
Connection to 192.168.17.25 failed

Looks like I need to look at how the smb.conf file varies on the twodifferent servers to eliminate this auth error... But it still lookslike some sort of layer 3 networking issue... (btw those are othervirtual IF's on my laptop... ;^)


rbw



--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Re: mount error 113 = No route to host

Reply via email to