#2963 closed defect (fixed)
RDP stops working correctly. Client can connect, but screen is black. -> Fixed in 2.1.2 — at Version 5
Reported by: | tale | Owned by: | |
---|---|---|---|
Component: | RDP | Version: | VirtualBox 2.1.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description (last modified by )
I've had this occur several times in the past few days. I have a headless setup running on Ubuntu with Windows XP running as a guest. If the network connection drops or I kill the rdp client that is connected, then it will occasionally show a black screen when I reconnect. I've tried reconnecting multiple times with different clients (Windows RDC and rdesktop-vrdp) and the screen is always black.
The only way that I can fix the rdp connection is to shutdown the windows xp guest. Restarting Windows XP doesn't fix the issue.
After a complete shutdown, I can restart the guest and then the rdp connection is fine again.
Change History (5)
comment:1 by , 15 years ago
Component: | other → RDP |
---|
comment:2 by , 15 years ago
comment:3 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Summary: | RDP stops working correctly. Client can connect, but screen is black. → RDP stops working correctly. Client can connect, but screen is black. -> Fixed in 2.1.2 |
Should be fixed in 2.1.2. Please reopen if the problem persists.
comment:4 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Same problem here: Headless Ubuntu Server 10.10 host and Windows 7 64-bit guest. VirtualBox version 3.2.12
The network drops connection from time to time (bad CPL connection it seems) and when it gets back, I get a black screen. The only way to fix it is to halt the virtual machine and restore it back.
This might be linked to the following ticket where I attached the log: http://www.virtualbox.org/ticket/4655
comment:5 by , 11 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
Please reopen if still relevant with VBox 4.2.14.
Please attach VBox.log with this problem.