I'm trying to mount one of my FreeNAS SMB shares from a small board computer running Linux, using the following:
Which gives the following output,
Using //FREENAS in that command gives the same result, and both generate "Unable to determine destination address." via
However, using the numeric IP of the FreeNAS machine works just fine. Note that my router has local hostname resolution enabled and I can ping freenas.lan from the command line of the Linux board. On top of that, my Windows machine can mount the share using both \\freenas.lan and \\FREENAS. So the problem seems to be with the way Samba on the Linux board is resolving hostnames.
This seems to be a relatively common problem, and based on a couple of older threads on the forums, I've tried manually setting "name resolve order" in smb.conf and specifying "vers=3.0" (and 2.0) in the mount command, but neither has worked. For further diagnostic info I ran the following on the Linux board:
and on the FreeNAS box:
Could the "workgroup" stuff be relevant there? In all my googling about this I did find something about all machines needing to be part of the same workgroup, but I'm very out of my depth on how that works.
Granted I could just mount the numeric IP and move on with my life, but I like to use the hostname if possible so I don't have to worry about going around updating configs on various devices when IPs inevitably change at some point down the line.
Code:
mount -t cifs //freenas.lan/share /local/path -o username=USER,password=PASS
Which gives the following output,
Code:
mount: wrong fs type, bad option, bad superblock on //freenas.lan/share, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program) In some cases useful info is found in syslog - try dmesg | tail or so.
Using //FREENAS in that command gives the same result, and both generate "Unable to determine destination address." via
dmesg
.However, using the numeric IP of the FreeNAS machine works just fine. Note that my router has local hostname resolution enabled and I can ping freenas.lan from the command line of the Linux board. On top of that, my Windows machine can mount the share using both \\freenas.lan and \\FREENAS. So the problem seems to be with the way Samba on the Linux board is resolving hostnames.
This seems to be a relatively common problem, and based on a couple of older threads on the forums, I've tried manually setting "name resolve order" in smb.conf and specifying "vers=3.0" (and 2.0) in the mount command, but neither has worked. For further diagnostic info I ran the following on the Linux board:
Code:
# smbclient //10.0.1.144/share -U user Enter user's password: protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE # smbclient //freenas.lan/Media -U user Enter user's password: protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
and on the FreeNAS box:
Code:
root@freenas[~]# smbclient -L //127.0.0.1 -U user Enter WORKGROUP\user's password: Sharename Type Comment --------- ---- ------- One Disk Two Disk Three Disk Four Disk IPC$ IPC IPC Service (FreeNAS Server) Reconnecting with SMB1 for workgroup listing. smbXcli_negprot_smb1_done: No compatible protocol selected by server. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Unable to connect with SMB1 -- no workgroup available
Could the "workgroup" stuff be relevant there? In all my googling about this I did find something about all machines needing to be part of the same workgroup, but I'm very out of my depth on how that works.
Granted I could just mount the numeric IP and move on with my life, but I like to use the hostname if possible so I don't have to worry about going around updating configs on various devices when IPs inevitably change at some point down the line.