xfreerdp的用法

Posted 2020-10-03 梁汉立

[[email protected] ~]# xfreerdp 192.168.1.107 -u username  --sec nla
connected to 192.168.1.107:3389
Password:
SSL_read: Failure in SSL library (protocol error?)
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.

[[email protected] ~]# xfreerdp 192.168.1.107 -u username -p 123 -sec-nla
connected to 192.168.1.107:3389
Password:
SSL_read: Failure in SSL library (protocol error?)
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.

[[email protected] ~]# xfreerdp 192.168.1.107 -u username  /cert-ignore
connected to 192.168.1.107:3389
Password:
SSL_read: Failure in SSL library (protocol error?)
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.
[[email protected] ~]# xfreerdp 192.168.1.107 -u username  --no-tls
connected to 192.168.1.107:3389
Password:
SSL_read: Failure in SSL library (protocol error?)
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.
[[email protected] ~]# xfreerdp 192.168.1.107 -u username  --no-nla
connected to 192.168.1.107:3389
Password:
SSL_read: Failure in SSL library (protocol error?)
Authentication failure, check credentials.

If credentials are valid, the NTLMSSP implementation may be to blame.
[[email protected] ~]# xfreerdp -u username  --no-nla 192.168.1.107
connected to 192.168.1.107:3389

username是远程主机192.168.1.107的用户名，从以上过程可以看出来，最后一次尝试成功了。具体原因下面这个帖子回答了：

https://github.com/FreeRDP/FreeRDP/issues/2128

julianjm commented on May 31, 2016 ? edited
I had the same problem. It turns out that the order of the arguments is important:

Works: xfreerdp -u username -d domain rd.example.com

Doesn‘t work: xfreerdp rd.example.com -u username -d domain

Edited: better late than never. I obviously meant xfreerdp insted of rdesktop :(

dkwami commented on Aug 10, 2016
I thought the same thing, but changing the order of my arguments actually helped.
I‘ve had the same problem going from ubuntu to windows server 2012 for a couple
of weeks. What finally worked for me was:
xfreerdp --sec nla --ignore-certificate -u username -d domain serverName
Thanks @julianjm!