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 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
