SOLVED Network causing Samba errors?

[aloisio mello]

The network

• pfSense
• 3 FreeNAS: FN1, FN2, and FN3:

FN1


Build FreeNAS-9.3-STABLE-201602031011
Platform Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz
Memory 32432MB

FN2

Build FreeNAS-9.3-STABLE-201602031011
Platform Intel(R) Pentium(R) CPU G3258 @ 3.20GHz
Memory 32432MB

FN3


Build FreeNAS-9.3-STABLE-201602031011
Platform Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
Memory 12143MB

• 2 CentOS 7 server
• 2 kubuntu workstations
• 1 windows 10 workstations
• Several family windows 10 workstations

2 of the FNs are not reporting errors and can be browsed from any of the workstations and open/map cifs with right permissions

1 of the FN display the error below when samba is started and shows in the network but we can't browse the shares – it times out.

Mar 1 08:31:05 mellonas smbd[18773]: [2016/03/01 08:31:05.101260, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Mar 1 08:31:05 mellonas smbd[18773]: matchname failed on htlinux.local

All servers are configured with DNS and pfSense is allocating SIPs to them; All SIPs are mapped with DNS resolver and host.domain are accessible;

FN1 and FN2 were installed 6 months ago and moved from their original boxes to new boxes with ASRock Extreame 6 with 32 GB RAM, 10 4TB WD Red.

FN3 was built with latest build last month on a Dell 880 with 12 GB RAM, 4 2TB WD Red.

Initially all cifs on FN3 were working fine and all cifs on FN1 and FN2 were not. The only way to access them was mounting from the command prompt or adding to fstab.

Started troubleshooting the samba side and. After comparing the smb4.conf between FN3 and FN2 found some differences. Backed up smb4.conf on FN2, and created a new SMB4.conf with FN3 configuration; created a new cif and the same issue continued heppening.

Reinstall FN2 from scratch and the error is gone, all cifs are browseble and accessible.

FN1 continues with original configuration and I'll be willing to play with it as I just finished backing up all data, so up to any test ;)

As I've done all reconfigurations as above, I do think is not smb, so going now to the n/w path. Please correct me if I'm wrong.

What suggestions the forum would have for me to test?

Regards!

 

[aloisio mello]

hmmm ... why fresh installation doesn't create an interface under network?? I did noticed that when 1st installed and created one myself ... maybe that's the problem or not as I remove it and still the same.

 

[aloisio mello]

Just noticed the same "error" on the working FN, so that might be part of the working in progress I read about it:


Mar 1 17:57:56 bennas smbd[52874]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: htlinux.local != (NULL)
Mar 1 17:57:56 bennas smbd[52874]: [2016/03/01 17:57:56.294991, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Mar 1 17:57:56 bennas smbd[52874]: matchname failed on htlinux.local

Bug #4780

 

[aloisio mello]

Fixed. Thanks for all help.

Share name with more than 12 characters caused the issue, so not network after all.