New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
ghsatpute opened this issue
Sep 2, 2015
· 39 comments
Comments
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.
Use +nego, -nego will disable protocol security negotiation
@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.
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:<user> /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
what about with just +sec-tls, I think we have some problems with VM access and NLA (not sure of that)
@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.
@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!
@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).
@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!!
@ghsatpute you still have problems with the latest master?
@bmiklautz with new problems seems to be solved. Thanks 👍
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.
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
@bwmarrin Could you retry with /log-level:TRACE? It may give additional hints on what is wrong.
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)
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
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?
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 
@bwmarrin No problem, the error is a bit imprecise.
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.
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…)
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.
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.
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?
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
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.
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
I have the same problem as @lszyba1. Adding /sec:rdp to the beginning of the command line helped.
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?
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.
I can confirm the latest Fedora xfreerdp works without /sec:rdp.
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
@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.
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:sfhrspalmer2 /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
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
@skewty sorry, missed the thread you´re posting in. You mixed up things, this was gateway related, you´re not using one.
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?
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
…
Содержание
- Sometimes getting: Error: protocol security negotiation failure #457
- Comments
- Protocol Security Negotiation Failure and Memory leaks #4663
- Comments
- protocol security negotiation failure #1639
- Comments
- Footer
- Cannot connect to secure Windows 10 Workstation #6225
- Comments
Sometimes getting: Error: protocol security negotiation failure #457
Hi! Using FreeRDP 1.0.1 and FreeRDP 1.0
If I just try to connect to Windows XP machine with
xfreerdp -u user IP
Error: protocol security negotiation failure
if I run the same command again and again for about 3 times for the fourth time it would connect.
Sometimes (after couple of failures) I provide —no-tls but it works.
But when I use —no-tls initially it would show (again, sometimes): Error: protocol security negotiation failure
I am having to run the same command again and again until it works.
The text was updated successfully, but these errors were encountered:
Is this still an issue?
closing for now. (not using as intensive as before, but issue hasn’t occurred to me last times)
I still get this when connecting to some machines.
is your bug is showing as described?
It is, but I have been unable to find the machine in question (it’s been a
hectic day here) avs reproduce the issue. I’ll reply back when I have
further information.
Thanks for the quick response.
On Apr 22, 2012 1:46 PM, «Bakyt Niyazov»
wrote:
is your bug is showing as described?
Reply to this email directly or view it on GitHub:
#457 (comment)
I have the issue right now. I rebooted a Windows 7 VM and could not connect to it. I added the —no-tls option and it worked.
May be it’s firewall related? Howerver when I was facing this problem Firewalls were disabled.
In the instances where I have encountered this, firewalls have been
disabled, nla is enabled (will try with —no-nla next time), but was able
to connect from my Win 08 VM. I’m off shift for the night, but will try to
find an example tomorrow.
On Apr 22, 2012 10:41 PM, «Bakyt Niyazov»
wrote:
May be it’s firewall related? Howerver when I was facing this problem
Firewalls were disabled.
Reply to this email directly or view it on GitHub:
#457 (comment)
I would like to report that after a month of trying to reproduce this issue, the only time I have encountered it is when the credentials are incorrect (or the machine has just come back from updates and will not respond to windows machines either, obviously this is a Windows problem). Perhaps it would be possible to clarify the error message, but please don’t keep this issue open on my account.
I can confirm this is still an issue with Windows 8. Like three18ti, the machine had just rebooted on it’s own because of a system update, but now it is unavailable remotely whether —no-tls or —no-nla is used or not.
@nikmartin could you try the latest git master and see if this still happens?
I never faced this again with latest versions (git). Let’s close it for now?
I get this Error when i try to connect to Windows Server R2 2008
ternes3@TERM1
$ sudo xfreerdp -u Administrator — ec2-54-217-0-11.eu-west-1.compute.amazonaws.com
WARNING: Using deprecated command-line interface!
-u Administrator -> /u:Administrator
ec2-54-217-0-11.eu-west-1.compute.amazonaws.com -> /v:ec2-54-217-0-11.eu-west-1.compute.amazonaws.com
connected to ec2-54-217-0-11.eu-west-1.compute.amazonaws.com:3389
Password:
SSL_read: Failure in SSL library (protocol error?)
SSL_read: error:14094419:SSL routines:SSL3_READ_BYTES:tlsv1 alert access denied
credssp_recv() error: -1
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.
Error: protocol security negotiation or connection failure
are you using the latest version compiled from GIT? Anyway, I think you have to create the new issue for this. This is very old issue and I think these are different situations. Because when I had that problem it could connect after 3 or 4 attempts. In your case it seems it’s just not using SSL (may be not installed or not configured)
Источник
Protocol Security Negotiation Failure and Memory leaks #4663
I’m not sure if this behavior is due to a bug or configuration issue on client or server side.
That said i would still appreciate tipps if its not a bug.
My client runs Xenial Xerus and the connection that can’t be established is to a RDS Farm with gateway and load balancer. I got reports that it works fine with red hat.
I Compiled version 2.0.0rc2 on the 14. may on my own.
The Debug output of the connection looks fine up to this point:
I then tested the nightly build and got these additional errors at the end:
==6242==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 112 byte(s) in 1 object(s) allocated from:
SUMMARY: AddressSanitizer: 112 byte(s) leaked in 1 allocation(s).
/opt/freerdp-nightly/bin/xfreerdp —version
This is FreeRDP version 2.0.0-dev3 (1cb1401)
The text was updated successfully, but these errors were encountered:
@2f6465762f6e756c6c could you post your command line, xfreerdp /buildconfig and setup details?
from the message I see you have a gateway, so maybe try our nightlies first too, as there have been some fixes since rc2 regarding gateway.
@akallabeth
The buildconfig for the version that i compiled myself is:
This is FreeRDP version 2.0.0-dev3 (c5b84db)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_JOURNALD_H=TRUE HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=on WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DIRECTFB=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_GFX_H264=OFF WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_GSTREAMER_0_10=OFF WITH_GSTREAMER_1_0=ON WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=ON WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PCSC=OFF WITH_PROFILER=OFF WITH_PULSE=on WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SSE2=ON WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=off WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XV=ON WITH_ZLIB=ON
Build type: Debug
CFLAGS: -fPIC -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -g
Compiler: GNU, 5.4.0
Target architecture: x64
I already tested it with a nightly build too with this buildconfig:
This is FreeRDP version 2.0.0-dev3 (1cb1401)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DIRECTFB=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_GFX_H264=OFF WITH_GPROF=OFF WITH_GSM=ON WITH_GSSAPI=OFF WITH_GSTREAMER_0_10=ON WITH_GSTREAMER_1_0=ON WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PAM=ON WITH_PCSC=ON WITH_PROFILER=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=ON WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=0 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=0 WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SSE2=ON WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=0 WITH_WAYLAND=OFF WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XDAMAGE=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XTEST=ON WITH_XV=ON WITH_ZLIB=ON
Build type: RelWithDebInfo
CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -g -fsanitize=address -fno-omit-frame-pointer
Compiler: GNU, 5.3.1
Target architecture: x64
Источник
protocol security negotiation failure #1639
i just tried to connecting to my Hyper-V server with this command (From my Ubuntu and the FreeRDP version is latest one):
xfreerdp /cert-ignore –no-nego /u:administrator /p:123 /v:192.168.172.129 /port:2179 /vmconnect:8021D293-FA6F-4CB5-AFD2-2499936D0949
but i got this error message :
transport_connect: getaddrinfo (Name or service not known)
Error: protocol security negotiation failure
The text was updated successfully, but these errors were encountered:
The old-style option -no-nego might be part of the problem — it is best to only use old-style arguments or new-style, not both. I suggest that you retry with the new style -nego and see if you get different results. You might also try adding one of the /sec:foo options, where foo is rdp or tls or nla to explicitly choose the correct protocol security layer.
I have same problem. Doesn’t work.
xfreerdp /v:servername:port /u:username
xfreerdp /v:servername:port /u:username /sec:rdp
When I use remmina it works and I get in fine. So what are we missing?
@srmcatee1110 @alizafzali did you try using /v:servername as last argument?
@srmcatee1110 @alizafzali btw what does xfreerdp —version say?
I tried as the last argument. No luck.
Our version is 1.0.2
@srmcatee1110 in case of 1.0.2 the «old» command line needs to be used. That would be something like xfreerdp -u username servername:port — server name and port must be the last argument.
That worked. Thanks.
Brew still use 1.0.2 version in 2017.
xfreerdp +clipboard /size:1280×1024 /u:Administrator /p:’test’ /v:10.1.2.3
How can I write this in old style command? @bmiklautz
@adamziaja give —HEAD a try with brew.
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Cannot connect to secure Windows 10 Workstation #6225
Remote Computer: Windows 10 Enterprise LTSC Version 1809 OSBuild: 17763.1192
Host Computer: RHEL 7.8
freerdp version: xfreerdp 2.0.0-rc4 (n/a) — using the default version available from the RHEL 7.8 repo
The remote computer is secured according to the DISA STIG requirements.
Some of the remote computer RDP server settings
I am pretty sure it is setup to use NLA, FIPS, and possibly Kerebos
The two systems are on the same subnetwork with no gateways nor proxies in between.
I entered my actual domain, username, and machine name in the appropriate areas in the below commands. I attempted variants of the domain such as:
/u:DOMAINusername
/d:DOMAIN /u:username
/u:username@DOMAIN.com
Attempted unsuccessfully to connect to the remote computer from the host computer via xfreerdp and the following commands:
If I try to force NLA it selects nothing
If I try NLA extended, I get a different error:
I tried enabling FIPS via xfreerdp, but this had no effect.
This may have something to do with Kerebos. I am not exactly sure. I can ask IT for more information on how the Windows 10 workstation is setup exactly.
I can connect to the secure Windows 10 Workstation from another Windows 10 workstation using the standard Microsoft Remote Desktop Connection client. I tried saving off the desktop.rdp and having xfreerdp call it to no avail
Please let me know if there is something else I should try to help debug and/or resolve this issue or if I should try with the latest release of freeRDP.
The text was updated successfully, but these errors were encountered:
Источник
Open
Issue created Dec 15, 2021 by
Can’t establish a connection to RDP server — Checl «Security Protocol Negotation»
A remote desktop connection I’ve been using for a while suddenly stopped working, with a «check security protocol negotiations» error. I’ve tried different options on the advanced tab but nothing seems to work.
Can anyone help? Log is below
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Opening connection
(DEBUG) - (remmina_rdp_event_init) - Disable smooth scrolling is set to 0
(DEBUG) - (remmina_rdp_event_init) - Adding GDK_SMOOTH_SCROLL_MASK
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Have SSH
(DEBUG) - (remmina_rdp_main) - RDP data path is /home/xxxx/.local/share/remmina/RDP
(DEBUG) - (remmina_rdp_main) - Not using system proxy settings
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel init
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - SSH tunnel initialization…
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port (tunnel)
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - server: xxxx, port: 3389
(DEBUG) - (remmina_rdp_tunnel_init) - protocol_plugin_start_direct_tunnel() returned [xxxx]:3389
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel has been optionally initialized. Now connecting to xxxx:3389
(DEBUG) - (remmina_rdp_main) - gfx_h264_available: 1
(DEBUG) - (remmina_rdp_main) - Resolution set by the user: 1188x448
(DEBUG) - (remmina_rdp_main) - Resolution set after workarounds: 1188x480
(DEBUG) - (remmina_rdp_main) - proxy_type: (null)
(DEBUG) - (remmina_rdp_main) - proxy_username: (null)
(DEBUG) - (remmina_rdp_main) - proxy_password: (null)
(DEBUG) - (remmina_rdp_main) - proxy_hostname: (null)
(DEBUG) - (remmina_rdp_main) - proxy_port: 80
(DEBUG) - (remmina_rdp_main) - Network settings not set
(DEBUG) - (remmina_rdp_main) - rdp_keyboard_remapping_list:
(DEBUG) - (remmina_rdp_main) - Log level set to to INFO
(DEBUG) - (rco_on_disconnect) - Disconnect signal received on RemminaProtocolWidget
(DEBUG) - (remmina_file_save) - Saving profile
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_store_password) - Password “password” saved for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_password” deleted for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_store_password) - Password “gateway_password” saved for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_passphrase” deleted for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - Profile saved
(DEBUG) - (remmina_file_save) - Connection profile states saved
(DEBUG) - (remmina_network_monitor_status) - G_NETWORK_CONNECTIVITY_FULL
(DEBUG) - (rco_on_disconnect) - Could not disconnect
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Opening connection
(DEBUG) - (remmina_rdp_event_init) - Disable smooth scrolling is set to 0
(DEBUG) - (remmina_rdp_event_init) - Adding GDK_SMOOTH_SCROLL_MASK
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Have SSH
(DEBUG) - (remmina_rdp_main) - RDP data path is /home/xxxx/.local/share/remmina/RDP
(DEBUG) - (remmina_rdp_main) - Not using system proxy settings
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel init
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - SSH tunnel initialization…
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port (tunnel)
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - server: xxxx, port: 3389
(DEBUG) - (remmina_rdp_tunnel_init) - protocol_plugin_start_direct_tunnel() returned [xxxx]:3389
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel has been optionally initialized. Now connecting to xxxx:3389
(DEBUG) - (remmina_rdp_main) - gfx_h264_available: 1
(DEBUG) - (remmina_rdp_main) - Resolution set by the user: 1188x448
(DEBUG) - (remmina_rdp_main) - Resolution set after workarounds: 1188x480
(DEBUG) - (remmina_rdp_main) - proxy_type: (null)
(DEBUG) - (remmina_rdp_main) - proxy_username: (null)
(DEBUG) - (remmina_rdp_main) - proxy_password: (null)
(DEBUG) - (remmina_rdp_main) - proxy_hostname: (null)
(DEBUG) - (remmina_rdp_main) - proxy_port: 80
(DEBUG) - (remmina_rdp_main) - Network settings not set
(DEBUG) - (remmina_rdp_main) - rdp_keyboard_remapping_list:
(DEBUG) - (remmina_rdp_main) - Log level set to to INFO
(DEBUG) - (rco_on_disconnect) - Disconnect signal received on RemminaProtocolWidget
(DEBUG) - (remmina_file_save) - Saving profile
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_store_password) - Password “password” saved for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_password” deleted for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_store_password) - Password “gateway_password” saved for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_passphrase” deleted for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - Profile saved
(DEBUG) - (remmina_file_save) - Connection profile states saved
(DEBUG) - (remmina_network_monitor_status) - G_NETWORK_CONNECTIVITY_FULL
(DEBUG) - (rco_on_disconnect) - Could not disconnect
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Opening connection
(DEBUG) - (remmina_rdp_event_init) - Disable smooth scrolling is set to 0
(DEBUG) - (remmina_rdp_event_init) - Adding GDK_SMOOTH_SCROLL_MASK
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Have SSH
(DEBUG) - (remmina_rdp_main) - RDP data path is /home/xxxx/.local/share/remmina/RDP
(DEBUG) - (remmina_rdp_main) - Not using system proxy settings
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel init
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - SSH tunnel initialization…
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port (tunnel)
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - server: xxxx, port: 3389
(DEBUG) - (remmina_rdp_tunnel_init) - protocol_plugin_start_direct_tunnel() returned [xxxx]:3389
(DEBUG) - (remmina_rdp_tunnel_init) - Tunnel has been optionally initialized. Now connecting to xxxx:3389
(DEBUG) - (remmina_rdp_main) - gfx_h264_available: 1
(DEBUG) - (remmina_rdp_main) - Resolution set by the user: 1188x448
(DEBUG) - (remmina_rdp_main) - Resolution set after workarounds: 1188x480
(DEBUG) - (remmina_rdp_main) - proxy_type: (null)
(DEBUG) - (remmina_rdp_main) - proxy_username: (null)
(DEBUG) - (remmina_rdp_main) - proxy_password: (null)
(DEBUG) - (remmina_rdp_main) - proxy_hostname: (null)
(DEBUG) - (remmina_rdp_main) - proxy_port: 80
(DEBUG) - (remmina_rdp_main) - Network settings not set
(DEBUG) - (remmina_rdp_main) - rdp_keyboard_remapping_list:
(DEBUG) - (remmina_rdp_main) - Log level set to to INFO
(DEBUG) - (rco_on_disconnect) - Disconnect signal received on RemminaProtocolWidget
(DEBUG) - (remmina_file_save) - Saving profile
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_store_password) - Password “password” saved for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_password” deleted for file /home/xxxx/.local/share/remmina/group_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_store_password) - Password “gateway_password” saved for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - We have a secret and disablepasswordstoring=0
(DEBUG) - (remmina_plugin_glibsecret_delete_password) - password “ssh_tunnel_passphrase” deleted for file /home/xxxx/.local/share/remmina/group_rdp_xxxx.remmina
(DEBUG) - (remmina_file_save) - Profile saved
(DEBUG) - (remmina_file_save) - Connection profile states saved
(DEBUG) - (remmina_network_monitor_status) - G_NETWORK_CONNECTIVITY_FULL
(DEBUG) - (rco_on_disconnect) - Could not disconnect**Please select the right template in the above drop down box.**Edited Dec 17, 2021 by Antenore Gatta (tmow)
- Index
- » Networking, Server, and Protection
- » [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
Pages: 1
#1 2013-05-22 19:11:32
- toni
- Member
- Registered: 2011-10-15
- Posts: 437
[SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
I would like to connect to a WIndows 2008 server r2 remote desktop at work from home. I have configured a cisco VPN connection correctly as it is required with the necessary credentials. I can establish connection through VPN, no problem. But using a remote desktop viewer such as Remmina, I cannot access to the remote desktop. The protocol selected is RDP. However, I can do it from Windows, using a cisco client to establish the VPN connection and then using the typical remote desktop application that comes with Windows.
How to do the same from arch linux?
Last edited by toni (2013-05-25 11:30:13)
#2 2013-05-22 19:40:36
- alphaniner
- Member
- From: Ancapistan
- Registered: 2010-07-12
- Posts: 2,810
Re: [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
Since Vista/2008, Windows versions have two options for enabling remote desktop, one of which requires clients use Network Level Authentication. I’m pretty sure freerdp (the RDP backend used by Remmina) supports NLA, but you may need to enable it or something.
But whether the Constitution really be one thing, or another, this much is certain — that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
#3 2013-05-22 19:55:58
- toni
- Member
- Registered: 2011-10-15
- Posts: 437
Re: [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
alphaniner wrote:
Since Vista/2008, Windows versions have two options for enabling remote desktop, one of which requires clients use Network Level Authentication. I’m pretty sure freerdp (the RDP backend used by Remmina) supports NLA, but you may need to enable it or something.
Yes, it has the NLA option. If you edit the connection, in advanced tab, you can select security as NLA. I have changed to NLA and it says: «Connecting to NameConnection…» but nothing happens: No error messages are shown. Simply this message is shown inderterminately, well, after 5 minutes approximately it says: «Unable to connect to RDP server xxx.xxx.xxx.xxx»
Last edited by toni (2013-05-22 20:00:29)
#4 2013-05-22 20:10:36
- alphaniner
- Member
- From: Ancapistan
- Registered: 2010-07-12
- Posts: 2,810
Re: [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
Is that different behaviour than before you enabled NLA?
Anyway, I would try running freerdp directly from the command line and if necessary enable verbose/debug output. Maybe Remmina already does this and has some logs somewhere (speaking of logs, check the kernel log and journal). Or maybe it can tell you what command it’s using so you don’t have to start from scratch.
If it’s easy enough to connect from the Windows box, check the event logs on the RDP server in case the problem is on that end.
Also, I know nothing about VPN so for all I know it could be interfering somehow.
But whether the Constitution really be one thing, or another, this much is certain — that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
#5 2013-05-23 18:42:33
- toni
- Member
- Registered: 2011-10-15
- Posts: 437
Re: [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
alphaniner wrote:
Is that different behaviour than before you enabled NLA?
Anyway, I would try running freerdp directly from the command line and if necessary enable verbose/debug output. Maybe Remmina already does this and has some logs somewhere (speaking of logs, check the kernel log and journal). Or maybe it can tell you what command it’s using so you don’t have to start from scratch.
If it’s easy enough to connect from the Windows box, check the event logs on the RDP server in case the problem is on that end.
Also, I know nothing about VPN so for all I know it could be interfering somehow.
The behaviour is the same than NLA.
How does freerdp work? I have installed but when trying to execute from terminal it says not found….
#6 2013-05-23 19:27:04
- alphaniner
- Member
- From: Ancapistan
- Registered: 2010-07-12
- Posts: 2,810
Re: [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
I used it briefly a long time ago and don’t remember the details. The binary probably isn’t named ‘freerdp’. Run
pacman -Ql freerdp | grep binto help you find it.
Last edited by alphaniner (2013-05-23 19:29:03)
But whether the Constitution really be one thing, or another, this much is certain — that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
#7 2013-05-25 10:21:18
- toni
- Member
- Registered: 2011-10-15
- Posts: 437
Re: [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
alphaniner wrote:
I used it briefly a long time ago and don’t remember the details. The binary probably isn’t named ‘freerdp’. Run
pacman -Ql freerdp | grep binto help you find it.
I have tried different commands using xfreerdp without success:
$ xfreerdp -u myUser --sec rdp -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --sec nla -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --sec tls -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --sec rdp --ignore-certificate -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --sec nla --ignore-certificate -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --sec tls --ignore-certificate -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --secure-checksum -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --secure-checksum --ignore-certificate -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failure
$ xfreerdp -u myUser --sec rdp --secure-checksum -p myPass xxx.xxx.xxx.xxx:3389
unable to connect to xxx.xxx.xxx.xxx:3389
Error: protocol security negotiation failureI think my cisco based VPN Is set correctly as I can connect correctly to server at work through it.
Any ideas?
#8 2013-05-25 11:29:23
- toni
- Member
- Registered: 2011-10-15
- Posts: 437
Re: [SOLVED]HOWTO:Connect Windows 2008 server R2 remote desktop from arch
Hi!
I have already solved this issue. The problem was the cisco vpn connection that was wrong. I created using gnome-network by selecting CISCO compatible and importing my *.pcf profile but for some reason it does not work if I do in this way.
So I have installed cisco-vpnclient as commented in another post that I have posted (see https://bbs.archlinux.org/viewtopic.php … #p1277733).
Then once I execute from terminal:
$vpnclient connect myProfilethe connection is established correctly. Then I can use any remote desktop client to connect to the server at work, such as, xfreerdp or remmina by simply using:
$ xfreerdp -u myUser -p myPassword xxx.xxx.xxx.xxx <--- not necesary specify the port as by default is 3389 using rdp security protocolor using remmina, by leave options as:
-Security: leave as negotiate (not necessary specify rdp, nla, tls…)
Thanks all!
Hi,
We are encountering an issue connecting to a Server 2012 R2 RDS Server using a HP T530 Thin Client…
We are able to connect to other servers with the same OS — so believe it is something to do with this particular server, more so a particular setting that is preventing connection ..
I have compared working and non working server settings (Security Layer, NLA, Encryption level etc) and these are identical .. One thing noticed on the non working server was : Network Security: LAN Manager authentication level had been amended, but have now since removed the reg key and this is now showing as undefined (Same as working server) but still not connecting ..
On the thin client we are prompted for credentials but upon entering these it returns an credential error — the credentials are 100% correct ! Connecting from a windows machine connects no problem, so this is looks like a setting mismatch between the thin client and the RDS Server …
Now being unsure of what other settings may or may not have been amended on the RDS Server from a vanilla build — where is the best place to start to see the changes — if at all possible ?
Lastly, see below the logs from the thin client when trying to connect;
Connection starting
2019-08-05T19:12:10 connection start, id {5c9d71cc-c2d6-444b-8429-1fb86ee7d217}
wrapper script logs —————————————————-
=======================================================
RDP Keyboard: 0x00000809 United Kingdom
Bandwidth limiter: [(none)]
rdp logs —————————————————————
Mon 05 Aug 2019 07:12:14 PM BST: check_host_and_port: getaddrinfo(********,****,0xa2)
Mon 05 Aug 2019 07:12:14 PM BST: = 0 (errno=0)
Mon 05 Aug 2019 07:12:14 PM BST: attempt_connect max 1000ms took 24ms
Mon 05 Aug 2019 07:12:14 PM BST: Starting xfreerdp to
********,****
—————————————————————-
Mon Aug 5 19:12:14 2019: RDP session opened
freerdp package ‘1.1.1-hp16.3’ branch ‘/Jenkins-Workspace/ThinPro-710_Tagged_Build/Sources/Proprietary/freerdp-1.1’ build ‘19790:48058’ arch ‘amd64’
Logging levels:
(default): NOTICE
Server [********] Port [****]
Gateway Enabled [No] Hostname [(none)] Port [443]
GDI Mode [Hardware]
Bitmap Cache [On]
Offscreen Cache [On]
Load Balance Info [(none)]
RDP Debug Packet Spooling:
none
desktop final state 1024×768+0+0
Mon 05 Aug 2019 07:12:14 PM BST: connected to ********:****
tcp_get_mac_address: MAC **********
nego_recv: selected_protocol: 2
Connecting with security layer NLA
TLS Version requested [1.2] actual [TLSv1.2]
Server certificate CN: *********.local
Encryption Cipher: E***************, 256/256 bits
Sending Authentication Token
CredSSP protocol support 6, peer supports 6
read errorCode [0X80090302] from TSRequest
Sending Authentication Token
tls_print_error: SSL_read default: Failure in SSL library (protocol error?)
tls_errors: SSL_read default: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
nla_client_authenticate failure
Failed to connect with NLA security
Initial RDP connection failure.
Conventional exit code 0x83=131
Mon 05 Aug 2019 07:12:16 PM BST: Closing RDP connection with exit code 131
Mon 05 Aug 2019 07:12:16 PM BST: xfreerdp exit: pid=5855, sig=0 (none), status=0x83
stdout / stderr ———————————————————
loading channel rdpdr
loading channel rdpsnd
loading channel drdynvc
Warning xf_GetWindowProperty (332): Property 300 does not exist
Warning xf_GetWindowProperty (332): Property 300 does not exist
Warning xf_GetWindowProperty (332): Property 300 does not exist
Verify result: unable to get local issuer certificate
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.
Error: protocol security negotiation or connection failure
tls_print_error: SSL_read default: Failure in SSL library (protocol error?)
tls_errors: SSL_read default: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
Mon 05 Aug 2019 07:12:14 PM BST: check_host_and_port: getaddrinfo(********,****,0xa2)
Mon 05 Aug 2019 07:12:14 PM BST: = 0 (errno=0)
Mon 05 Aug 2019 07:12:14 PM BST: attempt_connect max 1000ms took 24ms
Mon 05 Aug 2019 07:12:14 PM BST: Starting xfreerdp to ********:****
Mon 05 Aug 2019 07:12:16 PM BST: xfreerdp exit: pid=5855, sig=0 (none), status=0x83
Connection stopped
2019-08-05T19:12:28 connection stop
======================================================================
From what I can gather, it is failing to connect using NLA so failing back to SSL ? This leads me to believe there is some more settings on the offending RDS Server which is causing this problem !
Heres the logs from a working server on the same thin client for comparison ..
======================================================================
2019-08-05T19:18:59 connection start, id *****************
wrapper script logs —————————————————-
=======================================================
RDP Keyboard: 0x00000809 United Kingdom
Bandwidth limiter: [(none)]
rdp logs —————————————————————
Mon 05 Aug 2019 07:19:03 PM BST: check_host_and_port: getaddrinfo(*********,****,0xa2)
Mon 05 Aug 2019 07:19:03 PM BST: = 0 (errno=0)
Mon 05 Aug 2019 07:19:03 PM BST: attempt_connect max 1000ms took 32ms
Mon 05 Aug 2019 07:19:03 PM BST: Starting xfreerdp to *********:****
—————————————————————-
Mon Aug 5 19:19:03 2019: RDP session opened
freerdp package ‘1.1.1-hp16.3’ branch ‘/Jenkins-Workspace/ThinPro-710_Tagged_Build/Sources/Proprietary/freerdp-1.1’ build ‘19790:48058’ arch ‘amd64’
Logging levels:
(default): NOTICE
Server [*********] Port [****]
Gateway Enabled [No] Hostname [(none)] Port [443]
GDI Mode [Hardware]
Bitmap Cache [On]
Offscreen Cache [On]
Load Balance Info [(none)]
RDP Debug Packet Spooling:
none
desktop final state 1024×768+0+0
Mon 05 Aug 2019 07:19:03 PM BST: connected to **********:****
tcp_get_mac_address: MAC ***********
nego_recv: selected_protocol: 2
Connecting with security layer NLA
TLS Version requested [1.2] actual [TLSv1.2]
Server certificate CN: *******.local
Encryption Cipher: ***********, 256/256 bits
Sending Authentication Token
CredSSP protocol support 6, peer supports 6
RDP Server Build: 9600 (WS2012R2/Win8.1)
Sending Authentication Token
Local time zone ‘Europe/London’
Found time zone match for ‘Europe/London’ — ‘GMT Standard Time’.
mac address read from sysfs
mac address: ************
Using hashed mac address for hardware ID:
Number of bytes: 0X10=16
0000: 8A7B 6B77 F5BE 8769 63D2 CBF7 D12A 0B6B .{kw…ic….*.k
License Hardware Id:
Number of bytes: 0X14=20
0000: 0000 0104 8A7B 6B77 F5BE 8769 63D2 CBF7 …..{kw…ic…
0010: D12A 0B6B .*.k
No RDP license in cache, requesting license.
RDP Licensing complete
Mon 05 Aug 2019 07:19:09 PM BST: Server status code 0x401: The destination computer is being located.
Mon 05 Aug 2019 07:19:09 PM BST: Server status code 0x402: The destination computer is being prepared for use.
Mon 05 Aug 2019 07:19:09 PM BST: Server status code 0x404: The client is being redirected to the destination computer.
Mon 05 Aug 2019 07:19:09 PM BST: Server status code 0x403: The destination computer is being prepared to accept a remote connection.
Peer supports codec ‘CODEC_GUID_NSCODEC’
Peer supports codec ‘CODEC_GUID_REMOTEFX’
Peer supports codec ‘CODEC_GUID_IGNORE’
Peer supports codec ‘CODEC_GUID_IMAGE_REMOTEFX’
The server supports the RDP8 Graphics Pipeline Extension (EGFX).
Initial desktop size: 1024×768
dvcman_get_plugin_by_name(0x7f701c0008c0,echo) failed
dvcman_get_plugin_by_name(0x7f701c0008c0,egfx) failed
dvcman_get_plugin_by_name(0x7f701c0008c0,audin) failed
dvcman_get_plugin_by_name(0x7f701c0008c0,tsmf) failed
The RDP Server requests a dynamic channel for Graphics Pipeline Extension [RDPEGFX], Id=6
This is an RDP8 server.
The RDP Server requests a dynamic channel for Video Control [RDPEVOR], Id=8
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,Microsoft::Windows::RDS::Video::Control::v08.01) failed
dvcman_connect_channel(0x7f701c0008c0,8,Microsoft::Windows::RDS::Video::Control::v08.01) plugin not found.
The RDP Server requests a dynamic channel for Video Optimized Remoting [RDPEVOR], Id=9
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,Microsoft::Windows::RDS::Video::Data::v08.01) failed
dvcman_connect_channel(0x7f701c0008c0,9,Microsoft::Windows::RDS::Video::Data::v08.01) plugin not found.
The RDP Server requests a dynamic channel for Geometry Tracking for Video [RDPEGT], Id=10
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,Microsoft::Windows::RDS::Geometry::v08.01) failed
dvcman_connect_channel(0x7f701c0008c0,10,Microsoft::Windows::RDS::Geometry::v08.01) plugin not found.
The RDP Server requests a dynamic channel for TCP Reliable Audio, Id=13
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,AUDIO_PLAYBACK_DVC) failed
dvcman_connect_channel(0x7f701c0008c0,13,AUDIO_PLAYBACK_DVC) plugin not found.
The RDP Server requests a dynamic channel for TCP Reliable Audio, Id=13
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,AUDIO_PLAYBACK_DVC) failed
dvcman_connect_channel(0x7f701c0008c0,13,AUDIO_PLAYBACK_DVC) plugin not found.
00000.000: xf_sentinel_connect
00000.000: Auto-Recon S::Input) plugin not found.
The RDP Server requests a dynamic channel for Geometry Tracking for Video [RDPEGT], Id=13
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,Microsoft::Windows::RDS::Geometry::v08.01) failed
dvcman_connect_channel(0x7f701c0008c0,13,Microsoft::Windows::RDS::Geometry::v08.01) plugin not found.
The RDP Server requests a dynamic channel for Geometry Tracking for Video [RDPEGT], Id=13
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,Microsoft::Windows::RDS::Geometry::v08.01) failed
dvcman_connect_channel(0x7f701c0008c0,13,Microsoft::Windows::RDS::Geometry::v08.01) plugin not found.
The RDP Server requests a dynamic channel for TCP Reliable Audio, Id=15
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,AUDIO_PLAYBACK_DVC) failed
dvcman_connect_channel(0x7f701c0008c0,15,AUDIO_PLAYBACK_DVC) plugin not found.
The RDP Server requests a dynamic channel for Dynamic Display Reconfiguration [RDPEDISP], Id=13
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,Microsoft::Windows::RDS::DisplayControl) failed
dvcman_connect_channel(0x7f701c0008c0,13,Microsoft::Windows::RDS::DisplayControl) plugin not found.
The RDP Server requests a dynamic channel for TCP Reliable Audio, Id=15
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,AUDIO_PLAYBACK_DVC) failed
dvcman_connect_channel(0x7f701c0008c0,15,AUDIO_PLAYBACK_DVC) plugin not found.
The RDP Server requests a dynamic channel for Plug and Play Devices [RDPEPNP], Id=13
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,PNPDR) failed
dvcman_connect_channel(0x7f701c0008c0,13,PNPDR) plugin not found.
The RDP Server requests a dynamic channel for General USB Redirection [RDPEUSB], Id=13
dvcman_connect_channel(0x7f701c0008c0,13,URBDRC) no Connected call.
Telling sentinel USBR is ready.
Mon 05 Aug 2019 07:19:13 PM BST: Connection monitoring is active, timeouts=6000,30000,2147483647ms.
Mon 05 Aug 2019 07:19:13 PM BST: ==== hptc-freerdp-device —verbosity=2 —attach-all —uuid={5c9d71cc-c2d6-444b-8429-1fb86ee7d217} ====
The RDP Server requests a dynamic channel for Geometry Tracking for Video [RDPEGT], Id=15
dvcman_get_plugin_by_channel_name(0x7f701c0008c0,Microsoft::Windows::RDS::Geometry::v08.01) failed
dvcman_connect_channel(0x7f701c0008c0,15,Microsoft::Windows::RDS::Geometry::v08.01) plugin not found.
RDP client exit code 12 (0xc): The disconnection was initiated by the user logging off his or her session on the server.
The RDP server requested a disconnect (DisconnectProviderUltimatum), reason code 0x80=»Provider-initiated disconnect»
00008.190: Session Metrics:
> Warning: frames and pixel per second measurements are only valid
> if the content, server, and network is driving the thin client
> to the maximum. Otherwise, the limiter is elsewhere.
RemoteFX Frame Index: 0
EGFX Frame Id: 61
Codec Uncompressed: 0 blocks; 0 pixels (0%/0%)
Codec CAVideo: 0 blocks; 0 pixels (0%/0%)
Codec ClearCodec: 90 blocks; 730,494 pixels (21%/7%)
Codec Planar: 0 blocks; 0 pixels (0%/0%)
Codec AVC420: 0 blocks; 0 pixels (0%/0%)
Codec AVC444: 0 blocks; 0 pixels (0%/0%)
Codec Alpha: 0 blocks; 0 pixels (0%/0%)
Codec Progressive-Simple: 0 blocks; 0 pixels (0%/0%)
Codec Progressive-First: 240 blocks; 983,040 pixels (29%/10%)
Codec Progressive-Upgrade: 404 blocks; 1,654,784 pixels (49%/16%)
Codec SolidFill: 6 blocks; 14,080 pixels (0%)
Codec SurfaceToSurface: 0 blocks; 0 pixels (0%)
Codec SurfaceToCache: 256 blocks; 1,048,576 pixels (10%)
Codec CacheToSurface: 1,306 blocks; 5,349,376 pixels (54%)
Fallthrough exit code 0xc=12
Mon 05 Aug 2019 07:19:18 PM BST: Closing RDP connection with exit code 12
Mon 05 Aug 2019 07:19:18 PM BST: xfreerdp exit: pid=22133, sig=0 (none), status=0xc
stdout / stderr ———————————————————
loading channel rdpdr
loading channel rdpsnd
loading channel drdynvc
Warning xf_GetWindowProperty (332): Property 300 does not exist
Warning xf_GetWindowProperty (332): Property 300 does not exist
Warning xf_GetWindowProperty (332): Property 300 does not exist
Warning xf_GetWindowProperty (332): Property 300 does not exist
Verify result: unable to get local issuer certificate
Loading device service smartcard (static)
Loading Dynamic Virtual Channel echo
Loading Dynamic Virtual Channel egfx
Loading Dynamic Virtual Channel rdpeusb
Loading Dynamic Virtual Channel audin
Loading Dynamic Virtual Channel tsmf
registered device #1: SCARD (type=32 id=1)
registered device #1: SCARD (type=32 id=1)
registered device #1: SCARD (type=32 id=1)
ERRINFO_LOGOFF_BY_USER (0x0000000C):
The disconnection was initiated by the user logging off his or her session on the server.
=========================================================================
Any help or advice appreciated
Thanks.