FREERDP MULTIMON MAC

test connecting to the shadow server using Microsoft's Android, Mac OSX, iOS, Windows CE/RT/XP/Vista/7/8 clients.xfreerdp /v:realipaddress /cert-ignore & done (don't use localhost or 127.0.0.1) on your real desktop (not inside the Xephyr window) cd client/X11 and try if you can open 10 concurrent xfreerdp sessions to the shadow server: for i in `seq 1 10` do.

Xephyr -screen 1024x768x32 -query localhost :99.

use the virtual X11 server Xephyr to open a connection to your local display manager:.

enable xdmcp on your linux server's display manager.

test connection to the sample server remotely using windows 7/8/rt mstsc and xfreerdp clients.

test connection to the unix socket using xfreerdp /rfx /v:/tmp/tfreerdp-server.0.

note the listening unix domain socket (output Listening on socket /tmp/tfreerdp-server.0 ).

FREERDP MULTIMON CODE

In FreeRDP source code directory: cd server/Sample.

test automatic reconnection under the network failure scenarios of test.

now try the same test but terminate the socket on the client side: run sudo tcpkill port 3389 wait some seconds until xfreerdp tries to reconnect and then ctrl-c the tcpkill command.

ideally you should not even notice the disconnect/reconnect inside the xfreerdp session.

by comparing the remote port or the packet counter)

in TCPView verify that the you really got a new tcp connection (e.g.

verify that xfreerdp prints the message 'Network disconnect', 'Attempting reconnect (1 of 20)'.

in the session open Sysinternal's TCPView, right-click the corrct connection and select 'Close Connection'.

connect using the command xfreerdp /v:servername +auto-reconnect.

Do the same tests again but instead of pulling the network cable set a firewall rule: iptables -A INPUT -p tcp -source-port 3389 -j DROP iptables -A OUTPUT -p tcp -destination-port 3389 -j DROP (you can clear the tables again using iptables -D INPUT x iptables -D OUTPUT y x, y are the rule numbers, see iptables -line-numbers -L).

Note: depending on the kernel version the following test might not succeed.

restart this test but this time continue clicking inside the xfreerdp window immediately after pulling the network cable (freerdp should try to send data to the server).xfreerdp should terminate with the message 'Network disconnect' within a few seconds.pull the network cable on the client machine and wait.make sure that the xfreerdp window is not focused and the mouse pointer is outside the window (freerdp should not generate any input that is sent to the server).connect to a remote server in windowed mode: xfreerdp /v:servername /size:640x480.on the server, immediately after the connection, use tcpview or netstat to verify that the amount of established tcp connections on 3389 equals the amount of connected rdp clients.verify that xfreerdp prints out messages confirming that nego was retried.connect using the command xfreerdp /v:servername and don't specify any other options, especially not the /sec:xxx option.Depending on the OS this can be done via Group Policy, Remote Desktop Session Host configuration or by editing the registry. Prepare a server that enforces RDP-security by setting Security Layer to 'RDP', not 'Negotiate' and not 'SSL(TLS1.0)'.Verify that freerdp closes sockets from nego attempts

Freerdp multimon