SOLVED Accessing Multiple FNs CIFS

[aloisio mello]

Build FreeNAS-9.3-STABLE-201602031011
Platform Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz
Memory 32432MB
System Time Sat Feb 27 07:36:47 EST 2016
Uptime 7:36AM up 1:32, 0 users
Load Average 0.02, 0.06, 0.07

Running into an interesting issue here.

My home n/w:
- pfSense as router
- Three FNs boxes
- One Synology test box
- One CentOS box for VM
- One kubuntu as desktop
- Windows 10 users desktop/laptops

Samba is running on 2 of the FNs, the Synology, and the kubuntu;

From any desktop I can browse the network and open the servers, see the shares, open the ones I have access to, but one of the FN servers will show in the network, but I won't be able to open it to see the cifs. It times out.

If I use smb:\\ip or smb:\\name from my centos I can mount the cifs no problem, but I can't "click" on it's icon in Files.

With Windows same issue: Can open the box from the command prompt with name or ip (\\ip or \\name). From explorer I can see the box, but it won't open to show the cifs.

Checked both FN CIFS configuration and the only difference was that the one I could access had a max protocol of SMB2 (maybe my son changed as I haven't set to that when installed his FN). Changed mine to the same max and still no go (disabled CIFS, reboot, etc, etc).

As for history and timing, the one I can access is running on an old Dell desktop and was installed two months ago with the latest build:

Build FreeNAS-9.3-STABLE-201602031011
Platform Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
Memory 12143MB
System Time Sat Feb 27 07:52:41 EST 2016
Uptime 7:52AM up 15 days, 10:22, 0 users
Load Average 0.01, 0.03, 0.00

The one I can't access was build on a Asus MB one year ago and moved to a ASRock MB as I added more disks to it (now 10 4TB WD Red).

By the way, just created a CIF on my 3rd NAS, also running on an ASRock used to rsync all the data from the other two, and it is behaving the same: It shows in the network, but can't access from explorer, only from the command prompt.

Any ideas on how to continue troubleshooting this issue and try to resolve it would be appreciated.

Thanks!

 

[aloisio mello]

No ideas, no research has paid off.
I'm mounting my cifs on my fstab no problem, but Dolphin, smb4, and all other applications tested can't see them. The server shows up, but won't browse to open the cifs.
Next step, unless I see any ideas from the forum is to erase everything, install my new M1015 as was planning to do sometime, reinstall from scratch and test again.

I really can't understand why the new FN doesn't have a problem and only the one year old one does. Maybe the original installation had a bug and/or as it was installed on another MB - Asus - and moved to the ASRock Extreme 6 later, it has caused some disconnection ... we will see.

 

[BigDave]

Your setting may not be the same as mine, but I have my share set up as Windows(CIFS).
This is a suggestion to change ONE setting as shown below.
Please make sure to save a copy of your configuration BEFORE making ANY changes (see the manual for directions)
From the FreeNAS GUI go to:
Sharing > Windows(CIFS) > Edit
In this window go to:
Advanced tab.
Make sure the share is browsable by network clients (checkmark in box) then click OK.
See screenies of my GUI below

 

[BigDave]

Checked both FN CIFS configuration and the only difference was that the one I could access had a max protocol of SMB2 (maybe my son changed as I haven't set to that when installed his FN). Changed mine to the same max and still no go (disabled CIFS, reboot, etc, etc).

Max of SMB2 is default for FreeNAS and should not be changed.

 

[aloisio mello]

Thanks BigDave.

My CIF configuration was already with the option browsable by network on. Saw your comment about SMB2, so changed, created a new cif, restarted the service and same: can't browse the shares.

 

[BigDave]

Some times when making these changes, your machine, edit *(server and/or client)*
needs a reboot to make it stick.
There are also some excellent guides in this forum for setting up and config of shares.
I'm absolutly worthless when it comes to sharing configuration, sorry!

 

[aloisio mello]

Thanks BigDave. Vnc to the box and rebooted. Will test when back home.

 

[BigDave]

Hope that does it, let us know...

 

[aloisio mello]

Still not browsable. It is working for the newerly installed box, as below, but for the two old ones I can only mount from windows command prompt (IP or name). From ubuntu only on fstab - Dolphin won't browse, CentOS files only via connect to a server - won't browse to it on the network.

 

[BigDave]

FreeNAS-9.3-STABLE-201602031011

Are all three of your FreeNAS boxes on the same STABLE build as stated above?

 

[aloisio mello]

Can't browse:


mellonas: FreeNAS-9.3-STABLE-201602031011
homenas: FreeNAS-9.3-STABLE-201602031011

Can browse:

bennas: FreeNAS-9.3-STABLE-201602031011

--------------------------------SMB Conf from FN that is not working: -----------------------------------------------

[global]
server max protocol = SMB2
encrypt passwords = yes
dns proxy = no
strict locking = no
oplocks = yes
deadtime = 15
max log size = 51200
max open files = 934040
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
getwd cache = yes
guest account = nobody
map to guest = Bad User
obey pam restrictions = no
directory name cache size = 0
kernel change notify = no
panic action = /usr/local/libexec/samba/samba-backtrace
nsupdate command = /usr/local/bin/samba-nsupdate -g
server string = MELLONAS Server
ea support = yes
store dos attributes = yes
lm announce = yes
unix extensions = no
time server = yes
acl allow execute always = false
acl check permissions = true
dos filemode = yes
multicast dns register = no
domain logons = no
local master = yes
idmap config *: backend = tdb
idmap config *: range = 90000001-100000000
server role = standalone
netbios name = MELLONAS
workgroup = WORKGROUP
security = user
pid directory = /var/run/samba
create mask = 0666
directory mask = 0777
client ntlmv2 auth = yes
dos charset = CP437
unix charset = UTF-8
log level = 2
ea support = no
store dos attributes = no
map archive = no
map hidden = no
map readonly = no
map system = no


[ATTLaptop]
path = /mnt/raid/cifs/ATTLaptop
printable = no
veto files = /.snapshot/.windows/.mac/.zfs/
writeable = yes
browseable = yes
vfs objects = zfs_space zfsacl aio_pthread streams_xattr
hide dot files = yes
guest ok = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = true
zfsacl:acesort = dontcare


[GoogleDriveBackup]
path = /mnt/raid/cifs/GoogleDriveBackup
printable = no
veto files = /.snapshot/.windows/.mac/.zfs/
writeable = yes
browseable = yes
vfs objects = zfs_space zfsacl aio_pthread streams_xattr
hide dot files = yes
guest ok = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = true
zfsacl:acesort = dontcare


[cloud]
path = /mnt/raid/cifs/mycloud
printable = no
veto files = /.snapshot/.windows/.mac/.zfs/
writeable = yes
browseable = yes
vfs objects = zfs_space zfsacl aio_pthread streams_xattr
hide dot files = yes
guest ok = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = true
zfsacl:acesort = dontcare


---------------------------------------------- SMB conf for the FN that's working ---------------------------------------

[global]
server max protocol = SMB2
encrypt passwords = yes
dns proxy = no
strict locking = no
oplocks = yes
deadtime = 15
max log size = 51200
max open files = 349715
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
getwd cache = yes
guest account = nobody
map to guest = Bad User
obey pam restrictions = yes
directory name cache size = 0
kernel change notify = no
panic action = /usr/local/libexec/samba/samba-backtrace
nsupdate command = /usr/local/bin/samba-nsupdate -g
server string = FreeNAS Server
ea support = yes
store dos attributes = yes
lm announce = yes
hostname lookups = yes
time server = yes
acl allow execute always = true
acl check permissions = true
dos filemode = yes
multicast dns register = yes
domain logons = no
local master = yes
idmap config *: backend = tdb
idmap config *: range = 90000001-100000000
server role = standalone
netbios name = BENNAS
workgroup = WORKGROUP
security = user
pid directory = /var/run/samba
create mask = 0666
directory mask = 0777
client ntlmv2 auth = yes
dos charset = CP437
unix charset = UTF-8
log level = 1


[Applications]
path = /mnt/raid/cifs/Applications
printable = no
veto files = /.snapshot/.windows/.mac/.zfs/
writeable = yes
browseable = yes
shadow:snapdir = .zfs/snapshot
shadow:sort = desc
shadow:localtime = yes
shadow:format = auto-%Y%m%d.%H%M-2w
shadow:snapdirseverywhere = yes
vfs objects = shadow_copy2 zfs_space zfsacl aio_pthread streams_xattr
hide dot files = yes
guest ok = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = true
zfsacl:acesort = dontcare

------------------------------- Differences --------------------------------------

max open file: 934040 (not working); 349715 (on working)
obey pam restriction: no (not working); yes (on working)
unix extensions: no (not working); yes (on working)
acl allow execute always: false (not working); true (on working)
multicast DNS register: no (not working); yes (on working)

--------------------------- Next steps -------------------------------------------

After saving my configs and backup, will start changing to see if any of the above differences are/is causing the problem.

Regards!

 

[BigDave]

After saving my configs and backup, will start changing to see if any of the above differences are/is causing the problem.

You're on the right track, there has to be something missing or different...
After a quick look, I noticed no entry in the non-working lists for:
Hostname lookups = yes

Could it be that simple?

 

[aloisio mello]

Nope :) Nothing with me is simple.

Changed the above on my main FN and same; replaced smb4.conf on my backup FN with the one from the FM that's working, created a share ... same.

Going to wipe the backup FN and reinstall with 201602031011 from scratch ;)

 

[aloisio mello]

Fresh install fixed.

A pain as I only had a BD available, but worked. The wizard found the old raid and imported without my intervention (Good job guys!).

Now will re-rsync all and do the main FN. If the SMB gurus want to look at the confs above and post any thing to try I'm game, as it will take sometime to sync ~12TB.

Will keep this open for a little while to report any news and/or fixes.

Regards!

 

[SweetAndLow]

Just another data point but I can't use the 'network' option under a file explorer to access my shares either. I have to use fstab or connect using ip/hostname in windows.

 

[aloisio mello]

Interesting ... we need to play with those smb options to find out what causes that. My fresh install fixed whatever I broke and the cifs are accessible from the network icon in win10 explorer, dolphin in my kubuntu, and files in my CentOS 7.

 

[aloisio mello]

Maybe is deeper than I though... See smb start on the fresh install and on the old install:

--------------------- fresh ------------------------------

Feb 28 22:53:45 freenas notifier: Starting nmbd.
Feb 28 22:53:45 freenas notifier: Starting smbd.
Feb 28 22:53:45 freenas nmbd[25188]: [2016/02/28 22:53:45.816515, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Feb 28 22:53:45 freenas notifier: Starting winbindd.
Feb 28 22:53:45 freenas winbindd[25196]: [2016/02/28 22:53:45.877313, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Feb 28 22:53:45 freenas winbindd[25196]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Feb 28 22:53:45 freenas winbindd[25196]: [2016/02/28 22:53:45.881841, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Feb 28 22:53:45 freenas smbd[25192]: [2016/02/28 22:53:45.931574, 0] ../lib/util/become_daemon.c:136(daemon_ready)

---------------------- old --------------------------------

Feb 28 22:52:10 mellonas notifier: Performing sanity check on Samba configuration: OK
Feb 28 22:52:10 mellonas notifier: Starting nmbd.
Feb 28 22:52:10 mellonas notifier: Starting smbd.
Feb 28 22:52:10 mellonas nmbd[24193]: [2016/02/28 22:52:10.666087, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Feb 28 22:52:10 mellonas notifier: Starting winbindd.
Feb 28 22:52:10 mellonas winbindd[24201]: [2016/02/28 22:52:10.712479, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Feb 28 22:52:10 mellonas winbindd[24201]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Feb 28 22:52:10 mellonas winbindd[24201]: [2016/02/28 22:52:10.714706, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Feb 28 22:52:10 mellonas winbindd[24203]: STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsNo builtin backend found, trying to load plugin
Feb 28 22:52:10 mellonas winbindd[24220]: STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsNo builtin backend found, trying to load plugin
Feb 28 22:52:10 mellonas winbindd[24221]: STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsNo builtin backend found, trying to load plugin
Feb 28 22:52:10 mellonas smbd[24197]: [2016/02/28 22:52:10.778056, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Feb 28 22:52:10 mellonas smbd[24197]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionswaiting for connections
Feb 28 22:52:12 mellonas smbd[24225]: [2016/02/28 22:52:12.056229, 0] ../source3/lib/util_sock.c:941(matchname)
Feb 28 22:52:12 mellonas smbd[24225]: matchname: host name/name mismatch: 10.10.10.40 != (NULL)
Feb 28 22:52:12 mellonas smbd[24225]: [2016/02/28 22:52:12.056313, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 28 22:52:12 mellonas smbd[24225]: matchname failed on 10.10.10.40
Feb 28 22:52:12 mellonas smbd[24223]: [2016/02/28 22:52:12.094583, 0] ../source3/lib/util_sock.c:941(matchname)
Feb 28 22:52:12 mellonas smbd[24223]: matchname: host name/name mismatch: 10.10.10.2 != (NULL)
Feb 28 22:52:12 mellonas smbd[24223]: [2016/02/28 22:52:12.094659, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 28 22:52:12 mellonas smbd[24223]: matchname failed on 10.10.10.2

... and the list goes on

 

[aloisio mello]

Ok ... closing this here and moving to N/W troubleshooting as I don't see this as a SMB issue.

 

[aloisio mello]

CIF share name > 12 characters was getting things out of balance.

 

[Mirfster]

CIF share name > 12 characters was getting things out of balance.

Interesting. If this truly is the issue and can easily be re-created; then I would think that a bug should be filed for the devs to look at.