Freerdp: Protocol Security Negotiation Failure

[ghsatpute]

I cloned the latest repository and built the source locally as mentioned here

I have done that successfully. Now I'm trying to connect to Hyper-V VM

My command is

xfreerdp -nego -sec-nla /u:<domain>\<user> /p:<pass> /v:10.44.96.117 /vmconnect:b510551d-1aed-4946-8f7b-9a5e0bcbc9be

Output I get is

[14:29:42:194] [16478:16479] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[14:29:42:194] [16478:16479] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x2000C]
[14:29:42:194] [16478:16479] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
[14:29:42:194] [16478:16479] [ERROR][com.freerdp.client.x11] - Authentication only, exit status 1

I'm sure username and password are correct.

[jojonewnew]

Use +nego, -nego will disable protocol security negotiation

[ganeshsatpute]

@jojonewnew Sadly that doesn't work :(. Any else guess.

I have this another VM on which I have played a lot with installation on that it is working. On newly created VM it doesn't work. Any way I can find out the culprit.

[jojonewnew]

From your output it looks like protocol security negotiation failed.
You can try with the following command:
xfreerdp +nego +sec-rdp +sec-tls +sec-nla /u: /p: /v:10.44.96.117 /vmconnect:b510551d-1aed-4946-8f7b-9a5e0bcbc9be
or
xfreerdp +nego +sec-rdp +sec-tls +sec-nla /d: /u: /p: /v:10.44.96.117 /vmconnect:b510551d-1aed-4946-8f7b-9a5e0bcbc9be

[ganeshsatpute]

@jojonewnew Nah. Doesn't work that way either

[hardening]

what about with just +sec-tls, I think we have some problems with VM access and NLA (not sure of that)

[ganeshsatpute]

@hardening Believe me, in lack of any idea what is going wrong I have tried all possible combination.

Another thing is same command runs perfectly on another machine.

[avnermiz]

@hardening I'm fairly new to ubuntu (not a programmer), so bear with me if I am describing things incorrectly. I'm accessing a Windows MultiPoint Server via xfreerdp from Ubuntu 14.04. For it to work, I need to put in ignore-certificate.

xfreerdp --ignore-certificate -u UserN -f IpAddress -p

That works fine, but the clipboard doesn't work, so I can't copy and paste between my rdp session and my Ubuntu desktop.

When I try

xfreerdp --ignore-certificate +clipboard -u UserN -f IpAddress -p

I get the Protocol Security Negotiation Failure. Any idea? Thanks a ton!

[hardening]

@avnermiz I guess you're using the xfreerdp that is shipped with Ubuntu 14.04, which is really old. You should give a try with the latest master (compilation instructions are easily found on the FreeRDP wiki).

[bmiklautz]

@avnermiz for testing you can try our nightly package to see if this fixes you problem. Have a look to https://github.com/FreeRDP/FreeRDP/wiki/PreBuilds

[avnermiz]

@hardening @bmiklautz - you guys are amazing. I got it to work! Thank you so much.

Some thoughts: I had no idea how to do this:

Now create /etc/ld.so.conf.d/freerdp.conf and add the following line to it:

I'm not even sure I did it right, but it does seem to have worked. I just created those directories with the "mkdir" command and than created the filename with the "touch" command.

Also, this command no longer worked:

xfreerdp --ignore-certificate +clipboard -u UserN -f IpAddress -p

It just pulled up instructions, but from them I figured out that I had to do the below, which worked! (and now I no longer need the --ignore-certificate parameter)

xfreerdp /u:UserN /v:IpAddress +clipboard /f

Thanks all!!

[bmiklautz]

@ghsatpute you still have problems with the latest master?

[ghsatpute]

@bmiklautz with new problems seems to be solved. Thanks :+1:

[rbellamy]

I just installed the Arch package freerdp-git which pulls directly from master before building, and I am having this symptom. I've tried with all the security switches turned on and adding an entry in /etc/ld.so.conf.d/freerdp.conf pointing to /usr/lib/freerdp (which really shouldn't be necessary since it's in the normal load path), as well as ignoring the cert - still no worky with a Windows 8.1 VM guest.

[bwmarrin]

I'm suddenly having this exact same problem. Two weeks ago though this wasn't an issue I've been using this for a few months without any problems. Went on vacation and came back and now I'm getting this error :(

# ./xfreerdp  /version
This is FreeRDP version 2.0.0-dev (git c3ce0c3)

[07:56:52:153] [3354:3355] [INFO][com.freerdp.client.common.cmdline] - loading channel cliprdr
[07:57:12:178] [3354:3355] [ERROR][com.freerdp.core] - failed to connect to host.domain.com
[07:57:12:178] [3354:3355] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[07:57:12:178] [3354:3355] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x2000C]
[07:57:12:178] [3354:3355] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
[07:57:12:178] [3354:3355] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1

[akallabeth]

@bwmarrin Could you retry with /log-level:TRACE? It may give additional hints on what is wrong.

[bwmarrin]

Sure, I also just did a git pull and had the same error with

/opt/remmina_devel/freerdp/bin/xfreerdp /version
This is FreeRDP version 2.0.0-dev (git 4d85ade)

[bwmarrin]

Here you go,

[08:15:23:953] [7198:7199] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.client.x11] - Pointer device: 8
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[08:15:23:954] [7198:7199] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[08:15:43:976] [7198:7199] [ERROR][com.freerdp.core] - failed to connect to host.domain.com
[08:15:43:976] [7198:7199] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[08:15:43:976] [7198:7199] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x2000C]
[08:15:43:976] [7198:7199] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
[08:15:43:976] [7198:7199] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1

[akallabeth]

Hmm, looks like there is some lookup issue involved. I get the same error, if I use a invalid hostname.
Just to be sure, could you connect to the IP of your server directly to rule out hostname lookup issues?

[bwmarrin]

Well, now don't I feel silly. That's exactly the problem. Apparently the DNS server has the wrong IP for this host. With that error looking like something else and finding this issue here... I didn't even think to verify the DNS.

Sorry to waste your time but I do appreciate the help :)

[akallabeth]

@bwmarrin No problem, the error is a bit imprecise.

[yokartiklebron]

I also get this error when I try to log in with a user in my domain and the password expires.
The first password change screen does not appear on Windows.

[frispete]

To get around this issue in my case for WIN10, it was necessary to activate the RemoteDesktop rule in the incoming firewall rules (although the remote desktop service and certain users were enabled in the system settings before, which would imply the former setting applied implicitly from my humble POV...)

[dagostinelli]

It seems this message can come up for many reasons that have nothing to do with +nego or tls.

In my case, I had a fresh Win10 machine and one of the first things I did was attempt to connect to it via xfreerdp from Linux (Fedora in my case)

• Make sure Firewall allows RDP through
• Make sure that default user (called User) has a password set
• Make sure that your command line says /v:ip-address (don't omit the /v:) (I did that because another similar command, rdesktop, doesn't use /v:)

I suspect there are lots more reasons for this message. I wish it were less generic and more specific.

[RonaldoPA]

I know this is an old post, but I am having the same issue after I upgraded my remmina & Freerdp version. when I had the original versions that came with ubuntu, I was able to connect to my server, but share folders did not work. So I upgraded both and now I am receiving the "Protocol Security Negotiation Failure" error. I tried a lot of things but none of it work...
Here is the log:trace from my attempt to connect.
~$ xfreerdp /log-level:TRACE /u:domainuser /p:xxxxxx /v:10.10.15.234
[12:48:28:607] [15722:15726] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntryEx
[12:48:28:607] [15722:15726] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[12:48:28:608] [15722:15726] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device
[12:48:28:608] [15722:15726] [DEBUG][com.freerdp.client.x11] - Pointer device: 10
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[12:48:28:610] [15722:15726] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[12:48:43:040] [15722:15726] [ERROR][com.freerdp.core] - failed to connect to 10.10.15.234
[12:48:43:040] [15722:15726] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[12:48:43:040] [15722:15726] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[12:48:43:040] [15722:15726] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

Any help is appreciated.

[frispete]

First you missed to tell us to what system you attempt to connect, and which version of xfreerdp you use now, which is pretty important in an equation with two variables...

Have you tried the -sec-xxx group of options as well as /sec:xxx?

[RonaldoPA]

Sorry for that, I am trying to access a Windows Server 2008 R2. I had try to access with all kinds of parameters and always the same kind of trace is shown. I can paste it here if needed, but it is pretty much the same, only the "Enabling XXX Security:" changes from True to false

[masip85]

Ok.

Same problem to connect to windows server 2012 R2: nla doesn't works here.With remmina either.

You have to force rdp. But command flags order is quite important. /sec-rdp doesn't work either. So I can using this order:

xfreerdp +clipboard /log-level:TRACE /sec:rdp /v:xxxx /d:Ixxxx /u:xxxxx /p:xxxxx

user and password should escape special characters.

Screen options are affected by order too:
xfreerdp +clipboard /log-level:TRACE /sec:rdp /v:xxxx /d:Ixxxx /u:xxxxx /p:xxxxx /f doesn't work.
but:
xfreerdp +clipboard /f /log-level:TRACE /sec:rdp /v:xxxx /d:Ixxxx /u:xxxxx /p:xxxxx works perfectly.

[lszyba1]

Can this ticket be re-opened? or is there a different one:

The connection says: ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED
Which is incorrect.
a) my passwords works just fine with when logging into windows.
b) logging in as domain administrator still the same problem, and that password never expires.

I'm unable to login into the server, it looks like after recent reboot after MS updates.

Can anybody tell me what the issue might be? (This is also affecting remmina)

aptitude show remmina
Package: remmina
Version: 1.2.0-rcgit.27+dfsg-3~bpo9+1

xfreerdp /u:"myuser" /v:"server1" /d:"mydomain"
Password: 


[14:11:52:552] [17987:17988] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F]
[14:11:52:552] [17987:17988] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
[14:11:52:552] [17987:17988] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1


zzzz@e7470:~$ xfreerdp /u:"zzz" /v:"zzzz" /d:"zzzz" /log-level:TRACE

[14:13:01:549] [18003:18004] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device
[14:13:01:549] [18003:18004] [DEBUG][com.freerdp.client.x11] - Pointer device: 11
[14:13:01:549] [18003:18004] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[14:13:01:549] [18003:18004] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[14:13:01:549] [18003:18004] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[14:13:01:549] [18003:18004] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[14:13:01:549] [18003:18004] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[14:13:01:550] [18003:18004] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[14:13:01:550] [18003:18004] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[14:13:01:550] [18003:18004] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[14:13:01:551] [18003:18004] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[14:13:01:553] [18003:18004] [DEBUG][com.freerdp.core.nego] - RDP_NEG_RSP
[14:13:01:553] [18003:18004] [DEBUG][com.freerdp.core.nego] - selected_protocol: 2
[14:13:01:553] [18003:18004] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_FINAL
[14:13:01:553] [18003:18004] [DEBUG][com.freerdp.core.nego] - Negotiated NLA security
[14:13:01:553] [18003:18004] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA
[14:13:01:558] [18003:18004] [DEBUG][com.winpr.utils] - Could not open SAM file!
Password: 
[14:13:09:773] [18003:18004] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[14:13:09:773] [18003:18004] [TRACE][com.freerdp.core.nla] -  InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[14:13:09:773] [18003:18004] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
[14:13:09:775] [18003:18004] [TRACE][com.freerdp.core.nla] - InitializeSecurityContext  
........
SEC_I_COMPLETE_NEEDED [0x00090313]
[14:13:09:775] [18003:18004] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token
......
......
[14:13:09:777] [18003:18004] [ERROR][com.freerdp.core] - **freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F]**
[14:13:09:777] [18003:18004] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
[14:13:09:777] [18003:18004] [DEBUG][com.freerdp.core.transport] - transport_check_fds: transport_read_pdu() - -1
[14:13:09:777] [18003:18004] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1
[14:13:09:777] [18003:18004] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1

[nerijus]

I have the same problem as @lszyba1. Adding /sec:rdp to the beginning of the command line helped.

[Samerious]

Using:
This is FreeRDP version 2.0.0-dev3 (9de311f)
On
:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
I had this same issues. Forcing rdp worked as @masip85 pointed out.
I was attempting to connect to a Windows 2008 Server R2 where TLS 1.0 was just recently removed.
Do we know why this works like that?

[akallabeth]

This is #4449 and NLA has been fixed with 2.0.0-rc2.
Please be aware you need a up to date version of OpenSSL (needs algorithms implemented that the server is expecting, depends on server configuration)
@Samerious You did try our nightly builds https://github.com/FreeRDP/FreeRDP/wiki/PreBuilds? (note: installs in /opt) If you compiled yourself that is a good reference to avoid issues introduced by broken compile flags / dependencies.
Please create a new issue if you still have issues, commenting to closed ones might not be noticed.

[nerijus]

I can confirm the latest Fedora xfreerdp works without /sec:rdp.

[jo3rg]

Having a similar issue :(

me@home ~ % xfreerdp /v:$clientip /g:$gatewaydomain /gu:$gatewayuser /gd:$gatewaydomain /log-level:TRACE /sec:rdp /u:$clientuser :(
[19:20:30:054] [3242:3243] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntryEx
[19:20:30:058] [3242:3243] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[19:20:30:059] [3242:3243] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device
[19:20:30:059] [3242:3243] [DEBUG][com.freerdp.client.x11] - Pointer device: 10
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: FALSE
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: FALSE
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_RDP
[19:20:30:062] [3242:3243] [DEBUG][com.freerdp.core.nego] - Attempting RDP security
[19:20:30:075] [3242:3243] [DEBUG][com.freerdp.core] - connecting to peer $gatewayip
GatewayPassword:
[19:20:36:932] [3242:3243] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA
[19:20:36:932] [3242:3243] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[19:20:36:958] [3242:3243] [TRACE][com.freerdp.core.gateway.ntlm] - InitializeSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
[19:20:36:985] [3242:3243] [DEBUG][com.freerdp.core.gateway.rdg] - RDG_OUT_DATA authorization result: 500
[19:20:36:985] [3242:3243] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[19:20:36:985] [3242:3243] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[19:20:36:985] [3242:3243] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

Any ideas - using:

me@home ~ % xfreerdp /version
This is FreeRDP version 2.0.0-rc3 (n/a)
me@home ~ % uname -a
Linux T430 4.18.10-arch1-1-ARCH #1 SMP PREEMPT Wed Sep 26 09:48:22 UTC 2018 x86_64 GNU/Linux

[akallabeth]

@jo3rg http status code 500, looks like your gateway config is a bit off. If related to some invalid request data this should be fixed with 2.0.0-rc4, otherwise review your gateway configuration.

[skewty]

Please re-open the bug

Still broken in:

freerdp-nightly_2.0.0+0~20190305024829.637~1.gbp435872_amd64.deb

$ xfreerdp --version
This is FreeRDP version 2.0.0-dev5 (n/a)

$ xfreerdp /u:sfhr\spalmer2 /p:topsecret /v:pc06306
[15:18:40:601] [17035:17036] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[15:18:40:601] [17035:17036] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[15:18:40:601] [17035:17036] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[15:18:43:664] [17035:17036] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[15:18:43:664] [17035:17036] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[15:18:43:664] [17035:17036] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[15:18:43:664] [17035:17036] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

[akallabeth]

Could you please check if the setup actually works first?
As in RDP is running and the user is allowed to connect?
If that is the case please add server versions and configuration settings

[akallabeth]

@skewty sorry, missed the thread you´re posting in. You mixed up things, this was gateway related, you´re not using one.

[cg-david]

Hi. I have the same problem. I use

xfreerdp /v:<IP-Address> /u:<user> /log-level:TRACE

and get

[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.client.x11] - Pointer device: 13
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[18:54:19:263] [3673:3674] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[18:54:19:264] [3673:3674] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[18:54:19:264] [3673:3674] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[18:54:19:264] [3673:3674] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[18:54:19:264] [3673:3674] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[18:54:19:264] [3673:3674] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

I can easily access the machine via ssh or in Remmina with anything else than RDP. I also tried to install a version from github and some other things mentioned in this tread. I still don't get a positive result. Any suggestions?

[ricardocupello]

Hi, how are you??? I'm reading your logs and I think that you should force
or deactivate NLA security for that you need to use the following command
-sec-nla

>