SOLVED Can't mount SMB share: "Unable to find suitable address." How to diagnose?

LimeCrusher

Explorer
Joined
Nov 25, 2018
Messages
87
I have successfully created and accessed SMB shares previously. I am no longer able to mount them neither on my wife's Windows laptop nor on my Linux laptop. On my Linux Laptop, I get the following message:
Code:
limecrusher@MyLinuxLaptop:~⟫ sudo mount -a
[sudo] Password for limecrusher :
Password for limecrusher@//freenas.local/media:  *******
Unable to find suitable address.

Strangely, freenas.local responds to ping and I can ssh into it. My network has not changed, in the FreeNAS Gui, nothing has changed, shares are still there, the SMB service is still on and the following seems to say that everything is running as intended:
Code:
root@freenas[/etc/rc.d]# service samba_server status
nmbd is running as pid 2620.
smbd is running as pid 2624.
winbindd is running as pid 2629.

I have restarted the SMB service and the whole server, the problem is still there. Any idea how I can diagnose what's going wrong here?
 
Last edited:

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,545
I have successfully created and accessed SMB shares previously. I am no longer able to mount them neither on my wife's Windows laptop nor on my Linux laptop. On my Linux Laptop, I get the following message:
Code:
limecrusher@MyLinuxLaptop:~⟫ sudo mount -a
[sudo] Password for limecrusher :
Password for limecrusher@//freenas.local/media:  *******
Unable to find suitable address.

Strangely, freenas.local responds to ping and I can ssh into it. My network has not changed, in the FreeNAS Gui, nothing has changed, shares are still there, the SMB service is still on and the following seems to say that everything is running as intended:
Code:
root@freenas[/etc/rc.d]# service samba_server status
nmbd is running as pid 2620.
smbd is running as pid 2624.
winbindd is running as pid 2629.

I have restarted the SMB service and the whole server, the problem is still there. Any idea how I can diagnose what's going wrong here?
Are you able to mount by IP address?
 

LimeCrusher

Explorer
Joined
Nov 25, 2018
Messages
87
Are you able to mount by IP address?
Unfortunately not:
Code:
limecrusher@MyLinuxLaptop:~⟫ sudo mount -t cifs //$(freenasIP)/media /mnt/Media/     
[sudo] password for limecrusher :
Password for root@//$(freenasIP)/media:  *******
Unable to find suitable address.
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,545
Unfortunately not:
Code:
limecrusher@MyLinuxLaptop:~⟫ sudo mount -t cifs //$(freenasIP)/media /mnt/Media/    
[sudo] password for limecrusher :
Password for root@//$(freenasIP)/media:  *******
Unable to find suitable address.
Do you have `smbclient` on the linux box? If so, what's the output of smbclient //(ip of server)/media -U <your user>
 

LimeCrusher

Explorer
Joined
Nov 25, 2018
Messages
87
Do you have `smbclient` on the linux box? If so, what's the output of smbclient //(IP of server)/media -U <your user>
I do, here is what I get, same behavior with the IP or freenas.local:
Code:
limecrusher@MyLinuxLaptop:~⟫ smbclient //(IP of FreeNAS box)/media -U limecrusher
WARNING: The "syslog" option is deprecated
Enter limecrusher's password:
Connection to (IP of freenas box) failed (Error NT_STATUS_CONNECTION_REFUSED)
limecrusher@MyLinuxLaptop:~⟫ smbclient //freenas.local/media -U limecrusher
WARNING: The "syslog" option is deprecated
Enter limecrusher's password:
Connection to freenas.local failed (Error NT_STATUS_CONNECTION_REFUSED)
limecrusher@MyLinuxLaptop:~⟫ smbclient //freenas.local/media -U root
WARNING: The "syslog" option is deprecated
Enter root's password:
Connection to freenas.local failed (Error NT_STATUS_CONNECTION_REFUSED)

I remind you that my wife's Windows laptop can't access the share no more either. Browsing \\freenas.local\media from the Windows Explorer does not return anything.

Also try local smbclient smbclient -NL //127.0.0.1 to list your shares (verify that at least something is working).
My laptop has no samba shares, so I all I get is the following (why is this error still there though!?):
Code:
limecrusher@MyLinuxLaptop:~⟫ smbclient -NL //127.0.0.1
WARNING: The "syslog" option is deprecated
Connection to 127.0.0.1 failed (Error NT_STATUS_CONNECTION_REFUSED)

I thought I should rather try this on FreeNAS as well. Here it is:
Code:
root@freenas[~]# smbclient -NL //127.0.0.1
Anonymous login successful

        Sharename       Type      Comment
        ---------       ----      -------
        media           Disk     
        misc            Disk     
        IPC$            IPC       IPC Service (FreeNAS Server)
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Failed to connect with SMB1 -- no workgroup available

I am puzzled by the mention of SMB1 here but anyway, it's not supposed to be the client. For information, on my Linux laptop I force SMB v3.0 and the /etc/fstab file contains this line:
Code:
//freenas.local/media /mnt/Media cifs username=limecrusher,vers=3.0,uid=limecrusher,gid=limecrusher,forceuid,forcegid 0 0


I am starting to suspect my router is doing something weird so I restarted it, but it didn't change anything. I should probably review its DHCP settings :-/

EDIT : Router check, the FreeNAS box has been given an IP within the dynamic range of the DHCP server. Everything seems fine there.
 
Last edited:

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,545
I do, here is what I get, same behavior with the IP or freenas.local:
Code:
limecrusher@MyLinuxLaptop:~⟫ smbclient //(IP of FreeNAS box)/media -U limecrusher
WARNING: The "syslog" option is deprecated
Enter limecrusher's password:
Connection to (IP of freenas box) failed (Error NT_STATUS_CONNECTION_REFUSED)
limecrusher@MyLinuxLaptop:~⟫ smbclient //freenas.local/media -U limecrusher
WARNING: The "syslog" option is deprecated
Enter limecrusher's password:
Connection to freenas.local failed (Error NT_STATUS_CONNECTION_REFUSED)
limecrusher@MyLinuxLaptop:~⟫ smbclient //freenas.local/media -U root
WARNING: The "syslog" option is deprecated
Enter root's password:
Connection to freenas.local failed (Error NT_STATUS_CONNECTION_REFUSED)

I remind you that my wife's Windows laptop can't access the share no more either. Browsing \\freenas.local\media from the Windows Explorer does not return anything.


My laptop has no samba shares, so I all I get is the following (why is this error still there though!?):
Code:
limecrusher@MyLinuxLaptop:~⟫ smbclient -NL //127.0.0.1
WARNING: The "syslog" option is deprecated
Connection to 127.0.0.1 failed (Error NT_STATUS_CONNECTION_REFUSED)

I thought I should rather try this on FreeNAS as well. Here it is:
Code:
root@freenas[~]# smbclient -NL //127.0.0.1
Anonymous login successful

        Sharename       Type      Comment
        ---------       ----      -------
        media           Disk    
        misc            Disk    
        IPC$            IPC       IPC Service (FreeNAS Server)
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Failed to connect with SMB1 -- no workgroup available

I am puzzled by the mention of SMB1 here but anyway, it's not supposed to be the client. For information, on my Linux laptop I force SMB v3.0 and the /etc/fstab file contains this line:
Code:
//freenas.local/media /mnt/Media cifs username=limecrusher,vers=3.0,uid=limecrusher,gid=limecrusher,forceuid,forcegid 0 0


I am starting to suspect my router is doing something weird so I restarted it, but it didn't change anything. I should probably review its DHCP settings :-/

EDIT : Router check, the FreeNAS box has been given an IP within the dynamic range of the DHCP server. Everything seems fine there.
What's the output of 'testparm -s'
 

LimeCrusher

Explorer
Joined
Nov 25, 2018
Messages
87
What's the output of 'testparm -s'

There it is. I am surprised by interfaces = 127.0.0.1 192.168.0.29 because the current IP of the FreeNAS machine is 192.168.0.13 according to ifconfig and not 192.168.0.29.

Code:
root@freenas[~]# testparm -s
Load smb config files from /usr/local/etc/smb4.conf
Processing section "[homes]"
Processing section "[media]"
Processing section "[misc]"
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
        bind interfaces only = Yes
        deadtime = 15
        disable spoolss = Yes
        dns proxy = No
        dos charset = CP437
        hostname lookups = Yes
        interfaces = 127.0.0.1 192.168.0.29
        kernel change notify = No
        lm announce = Yes
        load printers = No
        logging = file
        map to guest = Bad User
        max log size = 51200
        max open files = 233957
        nsupdate command = /usr/local/bin/samba-nsupdate -g
        obey pam restrictions = Yes
        panic action = /usr/local/libexec/samba/samba-backtrace
        printcap name = /dev/null
        security = USER
        server min protocol = SMB2_02
        server role = standalone server
        server string = FreeNAS Server
        time server = Yes
        idmap config *: range = 90000001-100000000
        idmap config * : backend = tdb
        acl allow execute always = Yes
        create mask = 0666
        directory mask = 0777
        directory name cache size = 0
        dos filemode = Yes
        ea support = Yes
        store dos attributes = Yes
        strict locking = No


[homes]
        browseable = No
        comment = Home Directories
        path = "/mnt/poolochon/home/%U"
        read only = No
        valid users = %U
        veto files = /.snapshot/.windows/.mac/.zfs/
        vfs objects = zfs_space zfsacl streams_xattr
        zfsacl:acesort = dontcare
        nfs4:chown = true
        nfs4:acedup = merge
        nfs4:mode = special


[media]
        path = "/mnt/poolochon/media"
        read only = No
        veto files = /.snapshot/.windows/.mac/.zfs/
        vfs objects = zfs_space zfsacl streams_xattr
        zfsacl:acesort = dontcare
        nfs4:chown = true
        nfs4:acedup = merge
        nfs4:mode = special


[misc]
        path = "/mnt/poolochon/misc"
        read only = No
        veto files = /.snapshot/.windows/.mac/.zfs/
        vfs objects = zfs_space zfsacl streams_xattr
        zfsacl:acesort = dontcare
        nfs4:chown = true
        nfs4:acedup = merge
        nfs4:mode = special
 

LimeCrusher

Explorer
Joined
Nov 25, 2018
Messages
87
There are some checkboxes under Services->SMB to select which interface to listen on (Bind IP Addresses). Uncheck all of them.
None are checked. If I click in the "Bind IP Addresses" field, the GUI offers me to check 192.168.0.13 which is the current IP of the server.
 

LimeCrusher

Explorer
Joined
Nov 25, 2018
Messages
87
It worked. Checking the current IP and saving the form solved the problem. I can still mount them after I unchecked the IP in the form and saved it.
I am using DHCP for the server that's on bare metal and static IP addresses for jails and plugins. I should probably change that though and put the server on a static IP as well but I don't really care thanks to that good freenas.local (that's muticastDNS right?).

A big thank to you for your time, dedication and expertise. Any way I can help squash that nasty bug by reproducing it? Any log I could provide?
 
Last edited:
Top