Created attachment 9343 [details]
level 10 debug log

I upgraded a 3.6 machine to 4.1.0. Everything seems to work fine. But whenever I execute a program on a share with a "valid users" option, I receive several of the following error in the log (we run only at log level = 1):

[2013/10/30 11:09:20.618755,  1, pid=122095, effective(0, 0), real(0, 0)] ../source3/smbd/service.c:550(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED


When I increase the log level (find the level 10 debug log attached), then it looks like the message is caused by the machine account:

[2013/10/30 11:09:20.618684, 10, pid=122095, effective(0, 0), real(0, 0)] ../source3/smbd/share_access.c:215(user_ok_token)
  User MUC\it-01$ not in 'valid users'
[2013/10/30 11:09:20.618735,  2, pid=122095, effective(0, 0), real(0, 0)] ../source3/smbd/service.c:418(create_connection_session_info)
  user 'MUC\it-01$' (from session setup) not permitted to access this share (packages)
[2013/10/30 11:09:20.618755,  1, pid=122095, effective(0, 0), real(0, 0)] ../source3/smbd/service.c:550(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED


If I remove the "valid users" statement, then the error doesn't appear when I execute programs on the share.


Currently we can't configure the share permissions through windows, that's why we continue using "valid users". And as this parameter is still available it should be still supported, I guess.


Is it a bug or just logged at a to low level?