Ticket #10017 (closed defect: invalid)
VRDP Disconnects Upon Reception of Client Capabilities
| Reported by: | awakecoding | Owned by: | |
|---|---|---|---|
| Priority: | major | Component: | RDP |
| Version: | VirtualBox 4.1.6 | Keywords: | |
| Cc: | Guest type: | Linux | |
| Host type: | Linux |
Description (last modified by sunlover) (diff)
VRDP disconnects the FreeRDP remote desktop client right after it has sent its capabilities (demand active pdu). rdesktop can successfully connect, but sends a much smaller list of RDP capabilities. This does not seem to be a bug in FreeRDP which is written according to the Microsoft Open Specifications. This seems to be undocumented behavior of the VRDP server, since if the client sends unsupported capabilities it should not result in a disconnection.
I was willing to take a look at the issue myself in VRDP, but it turns out that it is one of the closed-source components of VirtualBox. I therefore rely on someone from the VirtualBox team to help me out with this and tell me more about the reason why VRDP disconnects FreeRDP. The capabilities that VRDP "does not like" could be just about anything.
We have a corresponding ticket in the FreeRDP bug tracker: https://github.com/FreeRDP/FreeRDP/issues/242
Attachments
-
vrdp_freerdp.txt
(10.9 KB) -
added by awakecoding 2 years ago.
- packet dump of failure case
Change History
Changed 2 years ago by awakecoding
-
attachment
vrdp_freerdp.txt
added
comment:1 Changed 2 years ago by sunlover
Please attach VBox.log of the session where you tried to connect with FreeRDP.
comment:2 Changed 2 years ago by sunlover
- Status changed from new to closed
- Resolution set to invalid
- Description modified (diff)
According to https://github.com/FreeRDP/FreeRDP/issues/242 this was a bug in FreeRDP, which has been fixed.
packet dump of failure case