Ubuntu clients can't connect to FreeNAS via SMB + AD

[Luke Jaeger]

I have a FreeNAS box serving student home directories via Samba. Users can log into the FreeNAS from any Mac or Windows machine on campus and mount their home directory via smb://someuser@my.server.edu (Mac) or //my.server.edu/ (Windows). The FreeNAS is bound to our campus AD system which handles authentication. That all works fine, whether or not the Mac or PC is bound to AD. (Some are, some aren't -- login works either way).

We are rolling out a bunch of laptops running Ubuntu Desktop 18.04 and I cannot get these to connect to the FreeNAS no matter what I try. I get a password error (even though I typed it right) or "File does not exist".

Network connectivity, DNS, etc are working properly on the Ubuntu laptops. I can SSH into the FreeNAS from one of the laptops, but need to get it so that students can mount their home directory as a Samba share.

Any guidance appreciated!

 

[anodos]

I have a FreeNAS box serving student home directories via Samba. Users can log into the FreeNAS from any Mac or Windows machine on campus and mount their home directory via smb://someuser@my.server.edu (Mac) or //my.server.edu/ (Windows). The FreeNAS is bound to our campus AD system which handles authentication. That all works fine, whether or not the Mac or PC is bound to AD. (Some are, some aren't -- login works either way).

We are rolling out a bunch of laptops running Ubuntu Desktop 18.04 and I cannot get these to connect to the FreeNAS no matter what I try. I get a password error (even though I typed it right) or "File does not exist".

Network connectivity, DNS, etc are working properly on the Ubuntu laptops. I can SSH into the FreeNAS from one of the laptops, but need to get it so that students can mount their home directory as a Samba share.

Any guidance appreciated!

Start by uploading the output of testparm -s and tcpdump -w /tmp/smb.pcap -s 0 -p -i <your interface> host <ip of the ubuntu client> and port 445.

If this is a test environment, increase logging on samba for that pid smbcontrol <pid> debug 10, reproduce issue, drop logging down again smbcontrol <pid> debug 1 and post /var/log/samba4/log.smbd.

 

[Luke Jaeger]

testparm -s output


Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: The "syslog" option is deprecated
Processing section "[printers]"
Processing section "[print$]"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
dns proxy = No
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 1000
obey pam restrictions = Yes
pam password change = Yes
panic action = /usr/share/samba/panic-action %d
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
passwd program = /usr/bin/passwd %u
server role = standalone server
server string = %h server (Samba, Ubuntu)
syslog = 0
unix password sync = Yes
usershare allow guests = Yes
idmap config * : backend = tdb


[printers]
browseable = No
comment = All Printers
create mask = 0700
path = /var/spool/samba
printable = Yes


[print$]
comment = Printer Drivers
path = /var/lib/samba/printers

 

[Luke Jaeger]

The tcpdump command results in a file full of unreadable junk:

 

[anodos]

The tcpdump command results in a file full of unreadable junk:

You have to read the pcap through wireshark or tcpdump.

 

[Luke Jaeger]

You have to read the pcap through wireshark or tcpdump.

in your message box ..

 

[anodos]

Code:

32   15   138.110.243.165   138.110.92.8   SMB2   196   Tree Connect Request Tree: \\<redacted server name>\~
33   15   138.110.92.8   138.110.243.165   SMB2   143   Tree Connect Response, Error: STATUS_BAD_NETWORK_NAME

Your Ubuntu client is requesting an SMB connection to a non-existent share "~".

 

[Luke Jaeger]

Code:

32   15   138.110.243.165   138.110.92.8   SMB2   196   Tree Connect Request Tree: \\<redacted server name>\~
33   15   138.110.92.8   138.110.243.165   SMB2   143   Tree Connect Response, Error: STATUS_BAD_NETWORK_NAME

Your Ubuntu client is requesting an SMB connection to a non-existent share "~".

OK, I feel like a moron now .... user error! thanks ...