[6.7.0-rc4] SMB Active Directory - Access Denied

I also have this issue. 

 

A domain un-join and re-join after reboot doesn't rectify this either.

 

This is with rc7

 

Final lines in syslog, with additional SMB logs enabled are

 

Mar 3 10:20:21 unraid smbd[7310]: check_ntlm_password: authentication for user [userid] -> [userid] -> [DOMAIN\userid] succeeded
Mar 3 10:20:21 unraid smbd[7310]: [2019/03/03 10:20:21.011860, 2] ../source3/auth/token_util.c:713(finalize_local_nt_token)
Mar 3 10:20:21 unraid smbd[7310]: WARNING: Failed to create BUILTIN\Administrators group! Can Winbind allocate gids?
Mar 3 10:20:21 unraid smbd[7310]: [2019/03/03 10:20:21.012217, 2] ../source3/auth/token_util.c:732(finalize_local_nt_token)
Mar 3 10:20:21 unraid smbd[7310]: WARNING: Failed to create BUILTIN\Users group! Can Winbind allocate gids?
Mar 3 10:20:21 unraid smbd[7310]: [2019/03/03 10:20:21.012569, 2] ../source3/auth/token_util.c:774(finalize_local_nt_token)
Mar 3 10:20:21 unraid smbd[7310]: Failed to create BUILTIN\Guests group NT_STATUS_ACCESS_DENIED! Can Winbind allocate gids?

 

So looks like some winbind problem.

 

Note behaviour is identical from Windows and Mac hosts, so this isn't a recent Windows update.

 

Happened when moving to 6.7.0-rc releases.

 

I will probably revert to 6.6

unraid-diagnostics-20190303-0957.zip

Reverting to 6.6 and all my shares are accessible again, so there is an issue with 6.7.0-rc7

38 minutes ago, dsmith44 said:

so there is an issue with 6.7.0-rc7

I suppose you mean version 6.7.0-rc5

Yes, sorry, 6.7.0-rc5.

 

Not sure where the rc7 came from. 

 

Any updates on this thread. I am also experiencing this issue.

 

I request to make this thread change from Minor to Urgent. Due to not being able to access the NAS via SMB it is a showstopper in my humble opinion 

Edited March 7, 2019 by Ravinmiist

This is a critical issue for me, a NAS that can't act as a NAS is somewhat pointless.

 

Seems to be a Samba 4.9 issue which 6.7 introduces.

 

https://bugzilla.samba.org/show_bug.cgi?id=13697

 

As suggested in multiple places (https://lists.samba.org/archive/samba/2018-September/218485.html)

running

net -s /dev/null groupmap add sid=S-1-5-32-546 unixgroup=nobody type=builtin

fixes the problem.

 

I've added this to my /boot/config/go script.

 

However I am not 100% comfortable with this as not clear if this is going to cause other issues and the mapping created doesn't actually match the errors, but will run rc5 like this for now and see if anything crops up.

 

Edited March 17, 2019 by dsmith44

5 hours ago, dsmith44 said:

This is a critical issue for me, a NAS that can't act as a NAS is somewhat pointless.

 

Seems to be a Samba 4.9 issue which 6.7 introduces.

 

https://bugzilla.samba.org/show_bug.cgi?id=13697

 

As suggested in multiple places (https://lists.samba.org/archive/samba/2018-September/218485.html)

running

net -s /dev/null groupmap add sid=S-1-5-32-546 unixgroup=nobody type=builtin

fixes the problem.

 

I've added this to my /boot/config/go script.

 

However I am not 100% comfortable with this as not clear if this is going to cause other issues and the mapping created doesn't actually match the errors, but will run rc5 like this for now and see if anything crops up.

 

They just need to push Samba 4.9.5 before 6.7 final.

 

It fixes this bug.

 

https://www.samba.org/samba/history/samba-4.9.5.html

 

@limetech

Edited March 17, 2019 by Dazog

RC6 has samba 4.9.5

 

Problem should be solved.

I just updated to RC6 - I can confirm that I can now join AD. Thanks so much!