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

Wed Feb 7 11:31:55 UTC 2018

On 06/02/18 18:33, Luke Barone via samba wrote:
> Is this one computer causing issues, or more than one?
> When logged in to the computer, what do you see in the Event Viewer
> (eventvwr.msc) relating to the time of your login?
> Are you using Samba in NT mode or AD mode?
> Can you run a command as an AD user (for example, click on Start, press
> Shift as you right-click on an application and choose "Run as other
> user...", and enter a domain username/password)?
>
> On Tue, Feb 6, 2018 at 7:39 AM, lejeczek via samba <samba at lists.samba.org>
> wrote:
>
>> 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:12
>> 3(make_user_info_map)
>>    Mapping user []\[] from workstation [20160217]
>> [2018/02/06 12:11:51.005880,  5] ../source3/auth/auth_util.c:14
>> 4(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:10
>> 8(make_user_info)
>>    making blobs for 's user_info struct
>> [2018/02/06 12:11:51.005971,  3] ../source3/auth/auth.c:178(aut
>> h_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(aut
>> h_check_ntlm_password)
>>    check_ntlm_password:  mapped user is: [_BIOTEC]\[]@[20160217]
>> [2018/02/06 12:11:51.006041,  3] ../source3/auth/auth.c:249(aut
>> h_check_ntlm_password)
>>    check_ntlm_password: guest authentication for user [] succeeded
>> [2018/02/06 12:11:51.006067,  5] ../source3/auth/auth.c:305(aut
>> h_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.
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>

(I generally advocate, and I dare to do it here on samba 
list, replies should go below always so other people when 
read the thread can get what it is about right away, without 
scrolling all the way)

Like I said earlier, non-AD samba. In Windows gui I see only 
"run as Admin..".
 From within CMD consoler when I execute "runas 
/user:mydom\myuser cmd" I get the same error about "not 
enough storage is available..."
In the event viewer I see similar:
"This computer was not able to set up a secure session with 
a domain controller in domain MYDOM due to the following:
Not enough storage is available to process this command.
This may lead to authentication problems. Make sure this 
computer is connected to the network. If the problem 
persists, please contact your administrator.
"
Above is in "System" section with NETLOGON source, but in 
"Application" section I see, yet judging by the time this 
happens when computer/OS starts/boots(not when I exec "runas")
"
SCEP Certificate enrollment for _BIOTEC\CCNR20160217$ via 
https://IFX-KeyId-97e5d1cd8b0497c04b4655a869c8f30efa89388d.microsoftaik.azure.net/templates/Aik/scep 
failed:

SubmitDone
GetCACertChain: OK
HTTP/1.1 200 OK
Cache-Control: no-cache
Date: Wed, 07 Feb 2018 11:04:29 GMT
Pragma: no-cache
Content-Length: 5185
Content-Type: application/x-x509-ca-ra-cert
Expires: -1
Server: Microsoft-IIS/8.5
x-ms-request-id: 56f4240a-7b6b-4d82-a43f-7a49cace562c
Strict-Transport-Security: max-age=31536000;includeSubDomains
X-Content-Type-Options: nosniff
X-Powered-By: ASP.NET

Method: POST(3016ms)
Stage: SubmitDone
Bad request (400). 0x80190190 (-2145844848 
HTTP_E_STATUS_BAD_REQUEST)
"

I've no idea if above is related(?)
My worry is that maybe M$ have us(those with NT style at 
least) in for a surprise with its latest "cumulative" 
update, I hope I'm wrong. I'm in a process of updating to 
the latest another Win10 Pro, hopefully that would help 
answer if it's the problem indeed. Otherwise... well, big 
question.