Getting bad smb2 signature for message after upgrade

[danpoleary]

After I upgraded from 9.2.0 to 9.2.1, I get a

Feb 9 13:44:47 freenas smbd[7120]: [2014/02/09 13:44:47.938864, 0] ../libcli/smb/smb2_signing.c:170(smb2_signing_check_pdu)
Feb 9 13:44:47 freenas smbd[7120]: Bad SMB2 signature for message
Feb 9 13:44:47 freenas smbd[7120]: [2014/02/09 13:44:47.938889, 0] ../lib/util/util.c:556(dump_data)
Feb 9 13:44:47 freenas smbd[7120]: [0000] F5 50 31 C4 3E 5F 8A 79 F4 B0 B5 04 97 E7 65 9E .P1.>_.y ......e.
Feb 9 13:44:47 freenas smbd[7120]: [2014/02/09 13:44:47.938908, 0] ../lib/util/util.c:556(dump_data)
Feb 9 13:44:47 freenas smbd[7120]: [0000] 5D 3F 13 48 07 B7 D1 13 FD DF 58 68 B7 F9 11 B4 ]?.H.... ..Xh....
Feb 9 13:44:47 freenas smbd[7120]: [2014/02/09 13:44:47.941482, 0] ../libcli/smb/smb2_signing.c:170(smb2_signing_check_pdu)
Feb 9 13:44:47 freenas smbd[7120]: Bad SMB2 signature for message

I cannot get rid of these. What is causing this?
thanks,

Dan

 

[Logan]

Same issue here. Brand new install. Can't map a drive from Win8 but can from Win7. Neither are domain machines and the FreeNAS install is default with a single user/no AD integration.

 

[redinsight]

I am also getting the same thing and mine is part of a domain. I just used the backup that I made and booted off of the F2 option so that I could get back working.

Upgrade 9.2.0 to 9.2.1.

 

[Franklin7777]

Same here. Not on domain, upgraded from 9.2.0 to 9.2.1. Can't connect from my Win8.1 machine, can connect from a Win7 machine. My console is spitting out all sorts of errors. This is a pretty gnarly bug to make it into a release... I'm going to have to downgrade to 9.2.0. Any bug filed on this issue yet?

 

[Mathias Johansson]

Tip if you cant connect from win 8..

I notice that if I tried to connect to \\freenas\ then I could not connect IF i connect to \\freenas.local\ then it work. Try to add .local to your server name

//mathias

 

[SweetAndLow]

I'm using windows 8.1, freenas 9.2.1.3 and just local user auth. I hit this bug also, i tried the .local fix that the previous post suggested and that did work but something with auth was still broken. I disabled smb3 and am using smb2 on the server and that seems to have been a decent work around. Either way this is pretty bad that they would ship with a bug like this in smb3.

 

[John Hixson]

Can those of you having this issue try setting the cifs max protocol to SMB2 ?

 

[DDH]

Just upgraded 9.2.0 to 9.2.1.3 got the error. As suggested set the max protocol to SMB2, problem gone (thanks John).

Any other fault finding I can help with? Clearly would like to get back to SMB3 at some point.

 

[Gavin]

Upgraded to FreeNAS-9.2.1.4.1-RELEASE-x64 (fec915c). Forgot which version I was using before... maybe 9.2.0. setting CIFS max protocol to SMB2 fixed the issue. Is SMB3 supposed to be better?

 

[darkryoushii]

Tip if you cant connect from win 8..

I notice that if I tried to connect to \\freenas\ then I could not connect IF i connect to \\freenas.local\ then it work. Try to add .local to your server name

//mathias

This fixed my issue, blitzcrank.home.lan just like I set it in the hostname setting.

 

[Gavin]

I'm pretty sure it's because of this issue, I noticed both my Android phones cannot sync with FolderSync using SMB/CIFS. It tries to upload to my FreeNAS box, but gets Access Denied errors.

 

[DDH]

So I finally got around to trying it, and the ".local" on the end of my NAS name also fixed the SMB3 issue. Mine was from Server 2012 R2, which really behaves the same as Win8.

 

[Gavin]

I just tried it. Works on Windows 8.1, but my Android still can't sync to CIFS. I guess I'm going to have to install ownCloud.