XigmaNAS

SMB2 worked fine before the upgrade to 9.3.0.2.1190 and continues to work fine after the upgrade. This 9.3.0.2.1190 also has an option for SMB3 that the previous version of NAS4Free did not have, and NAS4Free UI recommended it for Windows 8 networks. I have Windows 8.1 clients so selected SMB3 in NAS4Free, but it did not work. The Windows machines immediately were not able to see the NAS4Free shares and the Diagnostic log in NAS4Free has errors:

Dec 17 02:00:45 nas4free smbd[11931]: [0000] 60 5D 3D C4 8F 2E 6F B1 7A B2 66 60 5E 0C 8A 7E `]=...o. z.f`^..~
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.674160, 0] ../lib/util/util.c:556(dump_data)
Dec 17 02:00:45 nas4free smbd[11931]: [0000] 25 45 38 F1 5A 53 B0 2E 04 9F C4 3C C9 1A B6 67 %E8.ZS.. ...<...g
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.674137, 0] ../lib/util/util.c:556(dump_data)
Dec 17 02:00:45 nas4free smbd[11931]: Bad SMB2 signature for message
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.674106, 0] ../libcli/smb/smb2_signing.c:170(smb2_signing_check_pdu)
Dec 17 02:00:45 nas4free smbd[11931]: [0000] 14 59 EA C7 39 A4 2A 28 70 F2 AA 3A 6D BC B6 16 .Y..9.*( p..:m...
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.673110, 0] ../lib/util/util.c:556(dump_data)
Dec 17 02:00:45 nas4free smbd[11931]: [0000] 6E C4 96 BD 71 FB AB AA 54 15 EF EC 5B 92 2B 7A n...q... T...[.+z
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.673090, 0] ../lib/util/util.c:556(dump_data)
Dec 17 02:00:45 nas4free smbd[11931]: Bad SMB2 signature for message
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.673074, 0] ../libcli/smb/smb2_signing.c:170(smb2_signing_check_pdu)
Dec 17 02:00:45 nas4free smbd[11931]: [0000] AE 78 3B D0 2C 85 8D 63 C9 07 96 C6 12 C1 F6 35 .x;.,..c .......5
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.672105, 0] ../lib/util/util.c:556(dump_data)
Dec 17 02:00:45 nas4free smbd[11931]: [0000] 09 40 7C 40 A1 E5 44 40 B0 D9 39 0D 27 A8 35 6C .@|@..D@ ..9.'.5l
Dec 17 02:00:45 nas4free smbd[11931]: [2014/12/17 02:00:45.672086, 0] ../lib/util/util.c:556(dump_data)
Dec 17 02:00:45 nas4free smbd[11931]: Bad SMB2 signature for message
(etc etc)

What other configuration changes do I need to make on the NAS4Free server and/or the Windows clients in order to convert my home network from SMB2 to SMB3?

Thank you for your help!!! I am sure your answer could help others that upgrade as well.

I tested SMB3 and it worked to a certain extent but proved to be unusable because of very large delays or errors often, when navigating or when opening files.
Using SMB2 all seems to work fine.
Maybe SMB3 will be fixed in a later Samba release.

Thank you, id2test! I am fine sticking with SMB2 then. But for the record, I can not get as far as you did. I can not connect my Windows 8.1 clients to the NAS4Free at all - they do not see the NAS4Free server in Windows Explorer when it is running SMB3, but connect fine and can transfer files with no issues when the NAS4Free is running SMB2.

I am wondering if you get NAS4Free errors similar to those that I had posted above. At this point, it is only a curiosity item for me as SMB2 works perfectly fine.

Thanks again for your response and help !

I'm not getting those exact errors. But I only have Windows 8, not 8.1; not sure if that is related.
Samba 4.1.14 (currently the latest version) is to be included in a new nas4free release (not sure when it will be available).
We can test again then.

I do not have such errors SMB3 on rev.1190 and rev.1201.
Tested Win7, Win8.1.
The logs only: Works great !
PS: Install from scratch, do not upgrade (many changes in version 9.3.0.2). Try! The problem may be that not all files are replaced when upgrading from samba3 on samba4! Some files from samba3 (not used in the upgrade on samba4) remains and therefore does not work properly!

The Install from scratch was an interesting idea. I tried it and my Windows 8.1 clients can not see the shares. NAS4Free gives me the following errors:

Dec 17 22:51:31 nas4free smbd[4196]: [0000] 2F 94 A0 01 21 A6 D1 9F 65 B3 33 91 AA E2 87 B4 /...!... e.3.....
Dec 17 22:51:31 nas4free smbd[4196]: [2014/12/17 22:51:31.953296, 0] ../lib/util/util.c:556(dump_data)
Dec 17 22:51:31 nas4free smbd[4196]: [0000] 5C 7A CD 3D 3E ED A3 B3 00 F5 EE 74 75 1E 07 BE \z.=>... ...tu...
Dec 17 22:51:31 nas4free smbd[4196]: [2014/12/17 22:51:31.953274, 0] ../lib/util/util.c:556(dump_data)
Dec 17 22:51:31 nas4free smbd[4196]: Bad SMB2 signature for message
Dec 17 22:51:31 nas4free smbd[4196]: [2014/12/17 22:51:31.953248, 0] ../libcli/smb/smb2_signing.c:170(smb2_signing_check_pdu)

Yikes!

After doing the clean install and switching back to SMB2 from my SMB3 test results above, I now get many SMB2 errors and don't know how to fix them. They were not there after the clean upgrade, before I did the clean install to test. (Lesson learned, if it ain't broke, don't fix it. )

Dec 17 23:27:03 nas4free smbd[2390]: refusing to dump core
Dec 17 23:27:03 nas4free smbd[2390]: unable to change to %N.core
Dec 17 23:27:03 nas4free smbd[2390]: [2014/12/17 23:27:03.341829, 0] ../source3/lib/dumpcore.c:312(dump_core)
Dec 17 23:27:03 nas4free smbd[2390]: #4 0x804505236 <pthread_sigmask+918> at /lib/libthr.so.3
Dec 17 23:27:03 nas4free smbd[2390]: #3 0x8014698f3 <fault_setup_disable+435> at /usr/local/lib/libsamba-util.so.0
Dec 17 23:27:03 nas4free smbd[2390]: #2 0x8014698d7 <fault_setup_disable+407> at /usr/local/lib/libsamba-util.so.0
Dec 17 23:27:03 nas4free smbd[2390]: #1 0x801469bc5 <smb_panic+37> at /usr/local/lib/libsamba-util.so.0
Dec 17 23:27:03 nas4free smbd[2390]: #0 0x802ca509c <smb_panic_s3+108> at /usr/local/lib/libsmbconf.so.0
Dec 17 23:27:03 nas4free smbd[2390]: BACKTRACE: 5 stack frames:
Dec 17 23:27:03 nas4free smbd[2390]: [2014/12/17 23:27:03.341716, 0] ../source3/lib/util.c:896(log_stack_trace)
Dec 17 23:27:03 nas4free smbd[2390]: PANIC (pid 2390): internal error
Dec 17 23:27:03 nas4free smbd[2390]: [2014/12/17 23:27:03.341610, 0] ../source3/lib/util.c:785(smb_panic_s3)
Dec 17 23:27:03 nas4free smbd[2390]: ===============================================================
Dec 17 23:27:03 nas4free smbd[2390]: [2014/12/17 23:27:03.341599, 0] ../lib/util/fault.c:75(fault_report)
Dec 17 23:27:03 nas4free smbd[2390]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 17 23:27:03 nas4free smbd[2390]: INTERNAL ERROR: Signal 11 in pid 2390 (4.1.13)
Dec 17 23:27:03 nas4free smbd[2390]: [2014/12/17 23:27:03.341583, 0] ../lib/util/fault.c:73(fault_report)
Dec 17 23:27:03 nas4free smbd[2390]: ===============================================================
Dec 17 23:27:03 nas4free smbd[2390]: [2014/12/17 23:27:03.341539, 0] ../lib/util/fault.c:72(fault_report)

The problem I have is not related to upgrading or files from the previous Samba version. I also did a fresh install and a fresh setup, so no import of an old config file, and ran into the same issue; with SMB3 I get hangs.
So I did some more checking.
When I disable option: 'Enable use Sendfile' all works OK, also in my upgraded system.

On SMB2, changing option: 'Enable use Sendfile' does not have any effect, because the samba config file is NOT updated; 'use sendfile = yes' is NOT added when this options is enabled and the configuration saved.
This is a bug, at least in the interface.

I have the "Enable use Sendfile" disabled for both my SMB3 and SMB2 attempts. SMB2 works with these errors:

Dec 18 06:03:01 nas4free smbd[8962]: refusing to dump core
Dec 18 06:03:01 nas4free smbd[8962]: unable to change to %N.core
Dec 18 06:03:01 nas4free smbd[8962]: [2014/12/18 06:03:01.008082, 0] ../source3/lib/dumpcore.c:312(dump_core)
Dec 18 06:03:01 nas4free smbd[8962]: #4 0x804505236 <pthread_sigmask+918> at /lib/libthr.so.3
Dec 18 06:03:01 nas4free smbd[8962]: #3 0x8014698f3 <fault_setup_disable+435> at /usr/local/lib/libsamba-util.so.0
Dec 18 06:03:01 nas4free smbd[8962]: #2 0x8014698d7 <fault_setup_disable+407> at /usr/local/lib/libsamba-util.so.0
Dec 18 06:03:01 nas4free smbd[8962]: #1 0x801469bc5 <smb_panic+37> at /usr/local/lib/libsamba-util.so.0
Dec 18 06:03:01 nas4free smbd[8962]: #0 0x802ca509c <smb_panic_s3+108> at /usr/local/lib/libsmbconf.so.0
Dec 18 06:03:01 nas4free smbd[8962]: BACKTRACE: 5 stack frames:
Dec 18 06:03:01 nas4free smbd[8962]: [2014/12/18 06:03:01.007963, 0] ../source3/lib/util.c:896(log_stack_trace)
Dec 18 06:03:01 nas4free smbd[8962]: PANIC (pid 8962): internal error
Dec 18 06:03:01 nas4free smbd[8962]: [2014/12/18 06:03:01.007863, 0] ../source3/lib/util.c:785(smb_panic_s3)
Dec 18 06:03:01 nas4free smbd[8962]: ===============================================================
Dec 18 06:03:01 nas4free smbd[8962]: [2014/12/18 06:03:01.007851, 0] ../lib/util/fault.c:75(fault_report)
Dec 18 06:03:01 nas4free smbd[8962]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 18 06:03:01 nas4free smbd[8962]: INTERNAL ERROR: Signal 11 in pid 8962 (4.1.13)
Dec 18 06:03:01 nas4free smbd[8962]: [2014/12/18 06:03:01.007835, 0] ../lib/util/fault.c:73(fault_report)
Dec 18 06:03:01 nas4free smbd[8962]: ===============================================================
Dec 18 06:03:01 nas4free smbd[8962]: [2014/12/18 06:03:01.007794, 0] ../lib/util/fault.c:72(fault_report)

When I switch the the SMB3 option on NAS4Free, the Windows 8.1 client machines can no longer see the server and the server gives these errors instead:

Dec 18 06:05:48 nas4free smbd[9479]: [0000] 2D D9 BD D4 A5 59 70 8F 93 78 12 22 E3 B9 CE 2C -....Yp. .x."...,
Dec 18 06:05:48 nas4free smbd[9479]: [2014/12/18 06:05:48.411537, 0] ../lib/util/util.c:556(dump_data)
Dec 18 06:05:48 nas4free smbd[9479]: [0000] 91 14 07 4F 64 71 3E 36 B8 FD 71 D8 24 84 24 5A ...Odq>6 ..q.$.$Z
Dec 18 06:05:48 nas4free smbd[9479]: [2014/12/18 06:05:48.411516, 0] ../lib/util/util.c:556(dump_data)
Dec 18 06:05:48 nas4free smbd[9479]: Bad SMB2 signature for message
Dec 18 06:05:48 nas4free smbd[9479]: [2014/12/18 06:05:48.411489, 0] ../libcli/smb/smb2_signing.c:170(smb2_signing_check_pdu)

Try the following on a windows 8.1 client machine (at your own risk of course) :
- start a Command Prompt box; run it as Administrator using right-mouse-click
- run command (as one single command/line) :
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force

This should disable the SMB3 signing requirement.

And/or on nas4fee for the cifs/samba service add the following in the Auxiliary parameters field :
client signing = disabled

I hope this helps. If any combination works please provide details here for others.

Very important, you cannot switch SMB protocol while the client is connected.
So if you switch SMB2/SMB3, you must restart all windows client connected to NAS4Free.
It should be noted on the WebGUI....

If you use win8.1, try Get-SmbConnection from Windows PowerShell.

id2test - I tried your idea of restarting the service on the NAS4Free server with the option you suggested and it had no effect.

daoyama - I tried your idea of rebooting the Windows 8.1 clients AND IT WORKED. EVERYTHING WORKS FINE NOW- NO ERRORS. This didn't make sense to me since rebooting the service on the NAS4Free would cause the connection to break, or so I thought. But with a reboot everything went fine.

id2test and daoyama - After the reboot and everything working fine, I removed the option that id2test had suggested and rebooted again and everything worked fine as well.

Thanks for all your help. I hope my documentation here helps someone else.

oops - I spoke a little too soon. The SMB3 does seem to be working fine, but I notice these errors:


Dec 18 16:47:30 nas4free smbd[16387]: STATUS=daemon 'smbd' finished starting up and ready to serve connections../source3/librpc/crypto/gse_krb5.c:619: Error! Unable to set mem keytab - -1765328254
Dec 18 16:46:51 nas4free smbd[16385]: STATUS=daemon 'smbd' finished starting up and ready to serve connections../source3/librpc/crypto/gse_krb5.c:619: Error! Unable to set mem keytab - -1765328254
Dec 18 16:46:30 nas4free smbd[16371]: STATUS=daemon 'smbd' finished starting up and ready to serve connections../source3/librpc/crypto/gse_krb5.c:619: Error! Unable to set mem keytab - -1765328254
Dec 18 16:45:50 nas4free smbd[16359]: STATUS=daemon 'smbd' finished starting up and ready to serve connections../source3/librpc/crypto/gse_krb5.c:619: Error! Unable to set mem keytab - -1765328254