Re: [Samba] xfreerdp and SPNEGO failed
- Date: Tue, 27 Feb 2018 12:52:07 +0000
- From: lejeczek via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] xfreerdp and SPNEGO failed
On 23/02/18 11:12, Jonathan Hunter via samba wrote:
On 22 February 2018 at 15:00, lejeczek via samba <samba@xxxxxxxxxxxxxxx>
I try xfreerdp to connect to a Win10 which is a member of NT-style domain
and it fails this way:
[14:55:33:905] [8048:8055] [ERROR][com.freerdp.core.nla] - SPNEGO failed
with NTSTATUS: 0xC0000017
[14:55:33:905] [8048:8055] [ERROR][com.freerdp.core] -
freerdp_set_last_error ERRCONNECT_AUTHENTICATION_FAILED [0x00020009]
[14:55:33:905] [8048:8055] [ERROR][com.freerdp.core.rdp] -
rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[14:55:33:905] [8048:8055] [ERROR][com.freerdp.core.transport] -
transport_check_fds: transport->ReceiveCallback() - -1
Does it successfully connect to any other Win10 machines in the same
domain? i.e. is it just this one machine, or something more generic?
It indeed seem to be problem of this one win-box, I have
three more, one metal + two virtual and those work ok.
This one after a cumulative update went haywire, I email of
that with another tread: "win 10 login - Not enough storage
is available to process this command".
Now after some more(latest) update that problem has gone but...
Maybe I should make this box a clean slate... (?)
I wonder if it might be due to the NLA authentication mechanism (or I might
be clutching at straws here, just from the NLA strings above).
A thread here has some more discussion.. it's not the same problem you are
having, but contains some pointers to other resources on the subject, if
that is indeed where the problem lies:
Hope that helps, or at least gives some pointers..
To unsubscribe from this list go to the following URL and read the