[SOLVED] Connecting to Windows share in version 10.0

[gmc]

Greetings,

I have a problem in TC 10.0 connecting to a Windows network share.  With version 4.7.7 I use the following commands to connect to the share (as root):

mkdir /mnt/d
mount -t cifs //192.168.2.102/d /mnt/d -o guest

This works without any issues, and has for years.

Now with version 10.0, using the same commands, I get a "Mount error (112), the Host is down.

it is not down.  I can still connect from other machines, including TC 4.7.7.

Started with clean boot of V10.0 and installed cifs-utils.  Is there something I am missing?

Thanks for any suggestions...

[Juanito]

do you need to add "vers=2.0" or similar at the end of your command?

[gmc]

OK, vers=2.0 is new to me.  Let me guess, would that have anything to do with the SMB version?

In any case, I can't get the mount command to accept it and I don't find it listed as an option.  Maybe an example?  I am connecting to an XP system and I believe that would be SMB version 1, yes?

[gmc]

Update:

I tried a clean boot of TC v9.0, installed cifs-utils: same mount command, same result (failed).

I next tried going back to v4.7.7, the last version I have that works.  Booted from a clean, unmodified ISO.  Installed cifs-utils.  Ran the mount -t cifs //192.168.2.102/d /mnt/d -o guest  command (as root) and it worked.

Apparently something changed between 4.7.7 and 9.0/10.0 that I don't know about.  Something else needs to be installed or configured or whatever.

Does anyone have any ideas?

Thanks.

[mocore]

probably something in one of the deps

http://tinycorelinux.net/10.x/x86/tcz/cifs-utils.tcz.dep

possibly something in  filesystems-KERNEL.tcz  or samba3-libs.tcz ??

http://tinycorelinux.net/4.x/x86/tcz/samba3-libs.tcz.info
http://tinycorelinux.net/10.x/x86/tcz/samba3-libs.tcz.info

...

a search for error string

Mount error (112), the Host is down.

dug up this
raspberrypi.org/forums/viewtopic.php?t=210311#p1299205 - Re: [SOLVED] “mount error(112): Host is down”

that indicates changes to the "-o ect"  option arguments .

[Rich]

Hi gmc
See what the following commands return:

Code: [Select]

ldd /usr/local/bin/cifscreds
ldd /usr/local/sbin/cifs.upcall
ldd /usr/local/sbin/mount.cifs

[gmc]

OK, here it is:

tc@box:~$ ldd /usr/local/bin/cifscreds
        linux-gate.so.1 (0xb7ee8000)
        libkeyutils.so.1 => /usr/local/lib/libkeyutils.so.1 (0xb7ed7000)
        librt.so.1 => /lib/librt.so.1 (0xb7ece000)
        libc.so.6 => /lib/libc.so.6 (0xb7da1000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7d88000)
        /lib/ld-linux.so.2 (0xb7ee9000)

tc@box:~$ ldd /usr/local/sbin/cifs.upcall
        linux-gate.so.1 (0xb7f7a000)
        libtalloc.so.2 => /usr/local/lib/libtalloc.so.2 (0xb7f5a000)
        libkeyutils.so.1 => /usr/local/lib/libkeyutils.so.1 (0xb7f57000)
        libkrb5.so.3 => /usr/local/lib/libkrb5.so.3 (0xb7eaa000)
        librt.so.1 => /lib/librt.so.1 (0xb7ea1000)
        libc.so.6 => /lib/libc.so.6 (0xb7d74000)
        libk5crypto.so.3 => /usr/local/lib/libk5crypto.so.3 (0xb7d44000)
        libcom_err.so.3 => /usr/local/lib/libcom_err.so.3 (0xb7d40000)
        libkrb5support.so.0 => /usr/local/lib/libkrb5support.so.0 (0xb7d35000)
        libresolv.so.2 => /lib/libresolv.so.2 (0xb7d22000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7d09000)
        /lib/ld-linux.so.2 (0xb7f7b000)
        libdl.so.2 => /lib/libdl.so.2 (0xb7d04000)
       
tc@box:~$ ldd /usr/local/sbin/mount.cifs
        linux-gate.so.1 (0xb7f76000)
        librt.so.1 => /lib/librt.so.1 (0xb7f5f000)
        libc.so.6 => /lib/libc.so.6 (0xb7e32000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7e19000)
        /lib/ld-linux.so.2 (0xb7f77000)

[Juanito]

Here's what I got:

Code: [Select]

$ tce-load -i cifs-utils
mtd-4.19.10-tinycore64.tcz: OK
filesystems-4.19.10-tinycore64.tcz: OK
samba-libs.tcz: OK
cifs-utils.tcz: OK
$ sudo mount -t cifs //192.168.1.160/Public /mnt/public-n4800 -o user=blah,pass=blah
mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
$ dmesg | tail -3
CIFS VFS: Dialect not supported by server. Consider specifying vers=1.0 or vers=2.0 on mount for accessing older servers
No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.

..and this worked:

Code: [Select]

$ sudo mount -t cifs //192.168.1.160/Public /mnt/public-n4800 -o user=blah,pass=blah,vers=1.0

[gmc]

OK, thanks guys, you gave me what I needed.  It was the "guest" option that was causing the problem.  It would appear that the kernal portion of cifs has changed  and no longer allows the guest option, even though the manual hasn't caught up yet.  I can use the user/password option with any password and the Windows share will allow guest access if there is no matching user/password account (if the Windows share is set ulp to allow that option).

So, to sumerize: don't use the -o guest opton.  Use -o user=anyname,pass=anything,vers=x.x

And I now understand vers=x.x.  It is the protocol version, and yes, for XP I would use vers=1.0.

I don't know why sometimes I got the host down error (112) and other times I got 'Invalid argument' for the same command.  But I am glad that it is working now.  Syntax is everything!

Again, thanks to all who responed.  Your help was great.  And I can now access my Windows shares.

[gmc]

How do I modify the original topic heading?  I would like to add [Solved] to it.

Thanks.

[Rich]

Hi gmc

How do I modify the original topic heading? ...

Easy, you ask me to do it.

... I would like to add [Solved] to it.

Done.

[gmc]

Thanks!