Difference between revisions of "CentOS 7.x remote desktop or freerdp"

From Notes_Wiki
m
m
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
<yambe:breadcrumb>CentOS 7.x Desktop tools or applications</yambe:breadcrumb>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 7.x]] > [[CentOS 7.x Desktop tools or applications|Desktop tools or applications]] > [[CentOS 7.x remote desktop or freerdp]]
=CentOS 7.x remote desktop or freerdp=


Till CentOS 6.x rdesktop command was available to connect to Windows machines.  For CentOS 7.x use:
Till CentOS 6.x rdesktop command was available to connect to Windows machines.  For CentOS 7.x use:
Line 9: Line 8:
Refer:
Refer:
*http://unix.stackexchange.com/questions/259180/centos-7-how-to-install-rdesktop
*http://unix.stackexchange.com/questions/259180/centos-7-how-to-install-rdesktop
==xfreerdp fullscreen==
Use 'Ctrl+Alt+Enter' to shift from fullscreen mode to normal and then back to fullscreen.  This might work better if initial connection is made using '-f' fullscreen option.
==xfreerdp connection issue due to argument order==
xfreerdp might fail connection with error:
<pre>
  SSL_read: Failure in SSL library (protocol error?)
  Authentication failure, check credentials.
  If credentials are valid, the NTLMSSP implementation may be to blame. 
</pre>
even when username, password, domain, etc. are correct.  You can validate the username, password, etc. from a windows machine to be extra sure.  If all other details are correct then problem might be with order of arguments as shown below:
<pre>
  [saurabh@barjatiyarklp ~]$ xfreerdp windows-server -d domain1 -u saurabh
  connected to windows-server: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.
  [saurabh@barjatiyarklp ~]$ xfreerdp  -d domain1 -u saurabh windows-server
  connected to windows-server:3389
  Password:   
</pre>
'''Please note that in the working version, hostname 'windows-server' was given after all other parameters.'''
==Connecting to Windows 10+ or Server 2016+==
Latest xfreerdp might use options in below manner:
<pre>
xfreerdp /u:RND /v:172.31.1.13 /dynamic-resolution /size:1366x768
</pre>
Here dynamic-resolution and /size help in getting good remote desktop resolution (perhaps same as local client machine).
Refer:
* https://github.com/FreeRDP/FreeRDP/issues/733
==Connecting to older Windows XP machines==
Since /dynamic-resolution does not seems to work with XP machines use following to specify a specific resolution:
<pre>
xfreerdp /v:192.168.122.248 /u:administrator /p:<secret> /w:1600 /h:900
</pre>
In this case there is no scaling of display.  We cant resize.  Even "Clt+Alt+Ent" to go to fullscreen does not resizes.
==Forward audio from Windows machine to local machine==
To forward audio while using xfreerdp use:
<pre>
/audio-mode:0
</pre>
To leave it on the remote machine (Eg while using some sound recording / meeting) on remote machine use:
<pre>
/audio-mode:1
</pre>
Refer:
* https://unix.stackexchange.com/questions/285716/enable-audio-on-remote-windows-computer-through-xfreerdp
* https://unix.stackexchange.com/questions/285716/enable-audio-on-remote-windows-computer-through-xfreerdp/532384#532384
* https://github.com/FreeRDP/FreeRDP/issues/3869
* https://unix.stackexchange.com/questions/372995/xfreerdp-microphone-forwarding-but-windows-says-no-audio-devices-are-installed
=xfreerdp Troubleshooting=
==xfreerdp connection issue due to Wrong authentication==
If authentication information (username, password, domain, etc.) is wrong then error message similar to:
<pre>
[13:31:48:606] [23565:23566] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_LOGON_FAILURE [0x00020014]
[13:31:48:606] [23565:23566] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[13:31:48:606] [23565:23566] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
</pre>
might be shown.  Best is to validate all three from a Windows machine to by logging into destination machine.
==xfreerdp remote connection fails on Windows 10 if user is not already logged in==
xfreerdp remote connection fails to a Windows 10 user if user is not already logged in on the system from KVM (or web UI in case of VMs):
<pre>
[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
</pre>
If user logs in the above problem is solved automatically.
[[Main Page|Home]] > [[CentOS]] > [[CentOS 7.x]] > [[CentOS 7.x Desktop tools or applications|Desktop tools or applications]] > [[CentOS 7.x remote desktop or freerdp]]

Latest revision as of 05:53, 11 June 2023

Home > CentOS > CentOS 7.x > Desktop tools or applications > CentOS 7.x remote desktop or freerdp

Till CentOS 6.x rdesktop command was available to connect to Windows machines. For CentOS 7.x use:

  1. yum -y install freerdp
  2. xfreerdp <server-ip-or-fqdn>


Refer:


xfreerdp fullscreen

Use 'Ctrl+Alt+Enter' to shift from fullscreen mode to normal and then back to fullscreen. This might work better if initial connection is made using '-f' fullscreen option.


xfreerdp connection issue due to argument order

xfreerdp might fail connection with error: 

   SSL_read: Failure in SSL library (protocol error?)
   Authentication failure, check credentials.
   If credentials are valid, the NTLMSSP implementation may be to blame.

even when username, password, domain, etc. are correct. You can validate the username, password, etc. from a windows machine to be extra sure. If all other details are correct then problem might be with order of arguments as shown below: 

   [saurabh@barjatiyarklp ~]$ xfreerdp windows-server -d domain1 -u saurabh
   connected to windows-server: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.
   [saurabh@barjatiyarklp ~]$ xfreerdp  -d domain1 -u saurabh windows-server
   connected to windows-server:3389
   Password:

Please note that in the working version, hostname 'windows-server' was given after all other parameters.


Connecting to Windows 10+ or Server 2016+

Latest xfreerdp might use options in below manner: 

xfreerdp /u:RND /v:172.31.1.13 /dynamic-resolution /size:1366x768

Here dynamic-resolution and /size help in getting good remote desktop resolution (perhaps same as local client machine).

Refer:


Connecting to older Windows XP machines

Since /dynamic-resolution does not seems to work with XP machines use following to specify a specific resolution: 

xfreerdp /v:192.168.122.248 /u:administrator /p:<secret> /w:1600 /h:900

In this case there is no scaling of display. We cant resize. Even "Clt+Alt+Ent" to go to fullscreen does not resizes.


Forward audio from Windows machine to local machine

To forward audio while using xfreerdp use: 

/audio-mode:0

To leave it on the remote machine (Eg while using some sound recording / meeting) on remote machine use: 

/audio-mode:1

Refer:


xfreerdp Troubleshooting

xfreerdp connection issue due to Wrong authentication

If authentication information (username, password, domain, etc.) is wrong then error message similar to: 

[13:31:48:606] [23565:23566] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_LOGON_FAILURE [0x00020014]
[13:31:48:606] [23565:23566] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[13:31:48:606] [23565:23566] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1

might be shown. Best is to validate all three from a Windows machine to by logging into destination machine.


xfreerdp remote connection fails on Windows 10 if user is not already logged in

xfreerdp remote connection fails to a Windows 10 user if user is not already logged in on the system from KVM (or web UI in case of VMs): 

[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[13:14:52:567] [11702:11703] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

If user logs in the above problem is solved automatically.


Home > CentOS > CentOS 7.x > Desktop tools or applications > CentOS 7.x remote desktop or freerdp

Retrieved from "http://www.sbarjatiya.com/notes_wiki/index.php?title=CentOS_7.x_remote_desktop_or_freerdp&oldid=7932"