SOLVED Can't access CIFS shares from Windows 10

[erikiiofph7]

Ever since I reinstalled my Windows installation (changed windows version from 8 to 10) my CIFS shares haven't worked from windows any more. I have a dual boot setup with windows&linux, my linux installation can access the CIFS shares perfectly fine.

In /var/log/samba4/log.smbd I notice these error messages after I've tried with Win10 to access \\nasse or \\nasse\slask, what do they mean?

Code:

[2016/04/15 19:43:27.132388,  3] ../source3/auth/auth.c:178(auth_check_ntlm_password)
  check_ntlm_password:  Checking password for unmapped user [brum]\[Erik]@[BRUM] with the new password interface
[2016/04/15 19:43:27.132481,  3] ../source3/auth/auth.c:181(auth_check_ntlm_password)
  check_ntlm_password:  mapped user is: [NASSE]\[Erik]@[BRUM]
[2016/04/15 19:43:27.133261,  3] ../source3/passdb/lookup_sid.c:1645(get_primary_group_sid)
  Forcing Primary Group to 'Domain Users' for erik
[2016/04/15 19:43:27.133794,  1] ../source3/auth/check_samsec.c:187(sam_account_ok)
  sam_account_ok: Account for user 'erik' was disabled.
[2016/04/15 19:43:27.133918,  2] ../source3/auth/auth.c:315(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [Erik] -> [Erik] FAILED with error NT_STATUS_ACCOUNT_DISABLED
[2016/04/15 19:43:27.134037,  2] ../auth/gensec/spnego.c:693(gensec_spnego_server_negTokenTarg)
  SPNEGO login failed: NT_STATUS_ACCOUNT_DISABLED

My samba shares should be publically browseable and the share "slask" should be accessible without logging in. Both parts work from linux but not from Win10.

 

[anodos]

Ever since I reinstalled my Windows installation (changed windows version from 8 to 10) my CIFS shares haven't worked from windows any more. I have a dual boot setup with windows&linux, my linux installation can access the CIFS shares perfectly fine.

In /var/log/samba4/log.smbd I notice these error messages after I've tried with Win10 to access \\nasse or \\nasse\slask, what do they mean?

Code:

[2016/04/15 19:43:27.132388,  3] ../source3/auth/auth.c:178(auth_check_ntlm_password)
  check_ntlm_password:  Checking password for unmapped user [brum]\[Erik]@[BRUM] with the new password interface
[2016/04/15 19:43:27.132481,  3] ../source3/auth/auth.c:181(auth_check_ntlm_password)
  check_ntlm_password:  mapped user is: [NASSE]\[Erik]@[BRUM]
[2016/04/15 19:43:27.133261,  3] ../source3/passdb/lookup_sid.c:1645(get_primary_group_sid)
  Forcing Primary Group to 'Domain Users' for erik
[2016/04/15 19:43:27.133794,  1] ../source3/auth/check_samsec.c:187(sam_account_ok)
  sam_account_ok: Account for user 'erik' was disabled.
[2016/04/15 19:43:27.133918,  2] ../source3/auth/auth.c:315(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [Erik] -> [Erik] FAILED with error NT_STATUS_ACCOUNT_DISABLED
[2016/04/15 19:43:27.134037,  2] ../auth/gensec/spnego.c:693(gensec_spnego_server_negTokenTarg)
  SPNEGO login failed: NT_STATUS_ACCOUNT_DISABLED

My samba shares should be publically browseable and the share "slask" should be accessible without logging in. Both parts work from linux but not from Win10.

Best guess: the error message typically means that you've disabled the password for your user. Try resetting your user's password from the FreeNAS gui.

 

[erikiiofph7]

Good guess, password was disabled. Now it works. Thanks!

For future reference:
Why I needed a password set for the user was a mystery to me as the share has guest access, but I found this page explaining that Microsoft has disabled guest access without authentication in Windows 10.

For guests I added a guest account with a password on the FreeNAS. On the guest windows 10 machine you then need to:
Go to Control Panel > System and Security > User Accounts
Click "Manage Windows Credentials".
Click "Add a Windows credential".
After filling in the info the windows guest should also have access without the need of setting up a separate account on the FreeNAS for each and every guest who's visiting.

 

[anodos]

Good guess, password was disabled. Now it works. Thanks!

For future reference:
Why I needed a password set for the user was a mystery to me as the share has guest access, but I found this page explaining that Microsoft has disabled guest access without authentication in Windows 10.

For guests I added a guest account with a password on the FreeNAS. On the guest windows 10 machine you then need to:
Go to Control Panel > System and Security > User Accounts
Click "Manage Windows Credentials".
Click "Add a Windows credential".
After filling in the info the windows guest should also have access without the need of setting up a separate account on the FreeNAS for each and every guest who's visiting.

If you wish to only have unauthenticated access to the share, you can check the 'guest only' and 'allow guest access' boxes for the share in your webgui. This will actually obviate the need for passwords for the share.

 

[erikiiofph7]

If you wish to only have unauthenticated access to the share, you can check the 'guest only' and 'allow guest access' boxes for the share in your webgui. This will actually obviate the need for passwords for the share.

That wasn't enough, I've had them both checked the whole time.

 

[anodos]

That wasn't enough, I've had them both checked the whole time.

The dataset also has to be owned by the user you designate in your CIFS config. Additionally, a password should be set for the guest user to ensure a passdb.tdb and smbusers entries are properly generated for it.

 

[erikiiofph7]

The dataset also has to be owned by the user you designate in your CIFS config. Additionally, a password should be set for the guest user to ensure a passdb.tdb and smbusers entries are properly generated for it.

Ok, then it was the lack of password that was stopping me before.