[Samba] win 10 login - Not enough storage is available to process this command

[lejeczek]

hi everyone

I've had a Win 10 Pro client to a non-AD samba fine for a 
long time.
Suddenly I could not logon new user(which had not logged in 
on that Win box before). I was lazy, I remember that 
quickest thing that worked once in the past was remove & 
re-add client, you know, in Windows itself, to the domain.
Now I cannot login any user at all at that Win box(even 
though the box was re-added to domain ok), but my suspicion 
is that a big update that I let Windows applied just before, 
and from them a "restart" was pending, did something bad.
If I login to a local Win account(which has the same 
username & passwd as in domain) I can get to DC's shares 
right away, no problems.

When I at login attempt get error as in subject and the try 
again the same then the next message will be: "We can't sign 
you in with this credential because your domain isn't 
available...."

Samba's logs:
in log.172.24.154.142
..
[2018/02/06 12:11:51.005832,  5] 
../source3/auth/auth_util.c:123(make_user_info_map)
   Mapping user []\[] from workstation [20160217]
[2018/02/06 12:11:51.005880,  5] 
../source3/auth/auth_util.c:144(make_user_info_map)
   Mapped domain from [] to [_BIOTEC] for user [] from 
workstation [20160217]
[2018/02/06 12:11:51.005905,  5] 
../source3/auth/user_info.c:62(make_user_info)
   attempting to make a user_info for  ()
[2018/02/06 12:11:51.005929,  5] 
../source3/auth/user_info.c:70(make_user_info)
   making strings for 's user_info struct
[2018/02/06 12:11:51.005950,  5] 
../source3/auth/user_info.c:108(make_user_info)
   making blobs for 's user_info struct
[2018/02/06 12:11:51.005971,  3] 
../source3/auth/auth.c:178(auth_check_ntlm_password)
   check_ntlm_password:  Checking password for unmapped user 
[]\[]@[20160217] with the new password int
erface
[2018/02/06 12:11:51.005996,  3] 
../source3/auth/auth.c:181(auth_check_ntlm_password)
   check_ntlm_password:  mapped user is: 
[_BIOTEC]\[]@[20160217]
[2018/02/06 12:11:51.006041,  3] 
../source3/auth/auth.c:249(auth_check_ntlm_password)
   check_ntlm_password: guest authentication for user [] 
succeeded
[2018/02/06 12:11:51.006067,  5] 
../source3/auth/auth.c:305(auth_check_ntlm_password)
   check_ntlm_password:  guest authentication for user [] -> 
[] -> [nobody] succeeded

in log.20160217:

[2018/02/06 12:00:59.825349,  1] 
../source3/smbd/process.c:554(receive_smb_talloc)
   receive_smb_raw_talloc failed for client 
ipv4:172.24.154.142:49680 read error = NT_STATUS_CONNECTION_RES
ET.
[2018/02/06 12:02:34.623861,  1] 
../source3/smbd/process.c:554(receive_smb_talloc)
   receive_smb_raw_talloc failed for client 
ipv4:172.24.154.142:49681 read error = NT_STATUS_CONNECTION_RES
ET.
[2018/02/06 12:03:42.310069,  1] 
../source3/smbd/process.c:554(receive_smb_talloc)
   receive_smb_raw_talloc failed for client 
ipv4:172.24.154.142:49723 read error = NT_STATUS_CONNECTION_RES
ET.
[2018/02/06 12:12:01.798485,  1] 
../source3/smbd/process.c:554(receive_smb_talloc)
   receive_smb_raw_talloc failed for client 
ipv4:172.24.154.142:49731 read error = NT_STATUS_CONNECTION_RES
ET.

I did that IRPStackSize resolution you can find on the web, 
but it did no help(unless devil in the value of this entry?)
At the same time I have a number of Win7 & Win10, which 
Win10 have not gotten this new, latest update and these 
login okey.

Would you guys know what might a problem & how to 
troubleshoot it?
many thanks, L.