Comparing tcpdump traces of xfreerdp and rdesktop shows, I think, based on the TCP flags, the same failure:
09:37:58.222556 IP client.54938 >
host.ms-wbt-server: Flags [P.], seq 1:46, ack 1, win 502,
options [nop,nop,TS val 2653789238 ecr 2608962080], length 45
09:37:58.222713 IP host.ms-wbt-server > client.54938:
Flags [.], ack 46, win 509, options [nop,nop,TS val 2608962080
ecr 2653789238], length 0
09:37:58.222822 IP host.ms-wbt-server > client.54938:
Flags [F.], seq 1, ack 46, win 509, options [nop,nop,TS
val 2608962080 ecr 2653789238], length 0
09:37:58.222841 IP host.ms-wbt-server > client.54938:
Flags [R.], seq 2, ack 46, win 509, options [nop,nop,TS
val 2608962080 ecr 2653789238], length 0
That would be PSH, FIN, RST?
The port on the host only appears when I enable the remote console on the vm in VirtualBox.
The authentication is External:
VRDE: enabled (Address 0.0.0.0, Ports 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: external)
VRDE port: 3389
So, I guess this isn't an xfreerdp issue...
So, now that I've emerged xfreerdb, is there a reason it's better than rdesktop?