Raspberry pi Samba sources

Kaladin · 06-15-2018, 08:09 PM

What do I need to feed apt-get install to get the correct Samba sources to match my Raspberry Pi?

Short summary: I have a COTS NAS running Linux exporting Public/foo. I have a raspberry pi where I'm trying to mount //NAS/Public/foo to /media/foo. Mount gives "Invalid argument". smbclient //NAS/Public/foo /media/foo gives NT_STATUS_BAD_NETWORK_NAME. Wireshark (running on the pi) doesn't show anything going from the pi to the NAS. None of the log files on the NAS change when I try the mount. I've used smbcontrol pid debug 10, everything looks good until NT_STATUS_BAD_NETWORK_NAME suddenly shows up. I can use foo on my Windows boxes.

I'm an experienced Linux user, the problem is not directory permissions, nor a firewall. I've spent a good 30 hours on this and I'm at the end of my rope.

I want to run gdb on samba itself, which means I need to build it with the -g option. After apt-get update and apt-get upgrade I have the following installed:

samba/stable,now 2:4.5.12+dfsg-2+deb9u2 armhf [installed]
samba-common/stable,now 2:4.5.12+dfsg-2+deb9u2 all [installed,automatic]
samba-common-bin/stable,now 2:4.5.12+dfsg-2+deb9u2 armhf [installed,automatic]
samba-dsdb-modules/stable,now 2:4.5.12+dfsg-2+deb9u2 armhf [installed,automatic]
samba-libs/stable,now 2:4.5.12+dfsg-2+deb9u2 armhf [installed,automatic]
samba-vfs-modules/stable,now 2:4.5.12+dfsg-2+deb9u2 armhf [installed,automatic]
libsmbclient/stable,now 2:4.5.12+dfsg-2+deb9u2 armhf [installed,automatic]
smbclient/stable,now 2:4.5.12+dfsg-2+deb9u2 armhf [installed]

smbclient says I have Samba 3.6.5 installed. Samba.org says the latest is 4.8.2. Not seeing sources to 3.6.5.

What do I need to feed apt-get install to get the correct Samba sources to match my Raspberry Pi? Yeah, I know whatever I build will now be "my current samba". I want sources that are known to work on the pi, namely the source to the binaries already installed.

ps. Just realized the binaries already installed are not known to work, they're just known to run

But you know what I mean.

jlinkels · 06-16-2018, 06:48 AM

My apologies if I give an asnwer to something you don't ask.

You say:

Code:

smbclient //NAS/Public/foo /media/foo

gives an error. But this command is not the command to mount an SMB share on /media/foo. Smbclient only takes ONE parameter, the first one. And it drops you in an smb shell.

It is correct wireshark does not show anything. The smbclient never executes beyond the syntax check.

Too mount (what you intend) you use:

Code:

mount -t cifs -o username=samba-user //NAS/Public/foo /media/foo

I think your error message is because you use /media/foo which is not an SMB file system. Beware I did not test the posted mount command.But at least your error should be different. And if you get an error, double-check my proposed syntax.

jlinkels

AwesomeMachine · 06-16-2018, 09:34 AM

Put a line in /etc/apt/sources.list that begins with 'deb-src'. Then do

Code:

$ apt-get source <package>

That will download and unpack the source package in the current directory.

Kaladin · 06-16-2018, 02:20 PM

You are correct, I wasted hours due to faulty instructions. Thanks Google!

Still can't mount that stupid share though

jlinkels · 06-16-2018, 03:21 PM

I must admit that I cannot connect to a Windows share from my Raspi either.

Code:

jlinkels@raspberrypi:~$ smbclient -U jlinkels //w7/Users/
WARNING: The "syslog" option is deprecated
Enter jlinkels's password: 
Connection to w7 failed (Error NT_STATUS_IO_TIMEOUT)
jlinkels@raspberrypi:~$

SMBClient is version 4.5.12-Debian

While connecting from my desktop machine running Jessie it is no problem.
SMBClient is version 4.1.17-Debian

jlinkels

Rickkkk · 06-18-2018, 03:36 PM

Hi to all on this thread,

Just in case this may be part of the issue, especially since we're talking connecting linux and Windows through samba : check the version of the smb protocol being used. I ran into similar issues not long ago when updated versions of samba on linux changed the default version of smb it used and it wasn't compatible with what the Windows OS was expecting.

There is a mount option (both for command line and fstab mounting) that specifies the version of the smb protocol to use - that solved my problem.

jlinkels · 06-18-2018, 04:43 PM

That is very useful post, thank you.

However, it doesn't make any difference. SMBClient still does not work, and I miss the option to specify a version anyway.

However, the mount command simply works.

Code:

jlinkels@raspberrypi:~$ sudo mount -t cifs -o user=jlinkels //192.168.110.104/Users/ /mnt/w7/
Password for jlinkels@//192.168.110.104/Users/:  ***********

Even without the type and version:

Code:

jlinkels@raspberrypi:~$ sudo mount  -o user=jlinkels //192.168.110.104/Users/ /mnt/w7/
Password for jlinkels@//192.168.110.104/Users/:  ***********

I don't understand why I stopped testing at the SMBClient and did not try the mount command.

BTW, I double-checked and this is Stretch. Kernel 4.14.34-v7+.

jlinkels

Rickkkk · 06-19-2018, 06:58 AM

Quote:

Originally Posted by jlinkels

That is very useful post, thank you.

However, it doesn't make any difference. SMBClient still does not work, and I miss the option to specify a version anyway.

However, the mount command simply works.

I don't understand why I stopped testing at the SMBClient and did not try the mount command.

BTW, I double-checked and this is Stretch. Kernel 4.14.34-v7+.

jlinkels

Hi jlinkels,

I admit to actually *never* having used the smbclient option. I always just mount the shares - mostly through fstab and at the command line as needed.

Cheers :-)