[SOLVED] Can't connect to windows share, mount error 113 = No route to host

jmpetre · 06-22-2009, 06:26 PM

I've followed the man page and online guides, I type:

Code:

 mount -t smbfs -o username=jesse,password=**** //192.168.1.108/D-drive /mnt/win

I get back:

Code:

mount error 113 = No route to host
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

I can ping the IP fine. I also tried:

Code:

smbclient -L server -U jesse

(server is the actual hostname, smbclient will resolve it, but mount and ping won't)
and I get back the following

Code:

Password: 
Domain=[SERVER] OS=[Windows Server (R) 2008 Standard 6001 Service Pack 1] Server=[Windows Server (R) 2008 Standard 6.0]

	Sharename       Type      Comment
	---------       ----      -------
	ADMIN$          Disk      Remote Admin
	Brother HL-5140 Printer   Brother HL-5140
	C$              Disk      Default share
	D$              Disk      Default share
	D-drive         Disk      
	IPC$            IPC       Remote IPC
	print$          Disk      Printer Drivers
Domain=[SERVER] OS=[Windows Server (R) 2008 Standard 6001 Service Pack 1] Server=[Windows Server (R) 2008 Standard 6.0]

	Server               Comment
	---------            -------

	Workgroup            Master
	---------            -------

What am I doing wrong?

I've also configured the shared printer and can successfully print to it, so it seems weird that I can open the file share...?

This is on a stock xubuntu 8.04

Tinkster · 06-22-2009, 06:40 PM

try

Code:

mount.smbfs  //192.168.1.108/D-drive /mnt/win -o username=jesse,password=****

jmpetre · 06-22-2009, 07:54 PM

I get the same error:

Code:

mount error 113 = No route to host
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

jmpetre · 06-23-2009, 05:04 PM

Bump. Any ideas what I can try next?

Tinkster · 06-23-2009, 05:23 PM

Hmmm ... my only other idea is that maybe one of the characters in that
string "//192.168.1.108/D-drive " is weird, maybe some unicode thing
rather than a period. Really no idea, though.

You could have a look at the process execution under control of strace,
like so:

Code:

strace -o ugly_smbfs -vFf mount.smbfs  //192.168.1.108/D-drive /mnt/win -o username=jesse,password=****

and then check the ugly_smbfs file after failure.

Cheers,
Tink

jmpetre · 06-23-2009, 05:42 PM

Erg, it was my fault. The lease on the IP expired, and my router gave it a new one, .107
My crappy linksys router doesn't let me assign static IPs....very annoying.

Thanks anyway for your help!

Tinkster · 06-23-2009, 05:43 PM

Oh lol ;D

Can't you just assign them fixed IPs and have the router
handle "other" devices via DHCP?

Cheers,
Tink