Headless virtual machine connection problem

[alexandrpaliy]

Hi!

I'm trying to use VirtualBox in headless mode.
My knowledge base is chapter 7 of VBox manual. Performing all of the steps, I did nit see any error, so I think there was no mistype or something like that.
The problem is, when I start headless virtual machine and try to connect, I see:
1) client side:

Code: Select all

[alex ~]$ rdesktop -a 16 -N localhost:3389
Autoselected keyboard map ru
ERROR: Connection closed

2) host side:

Code: Select all

[alex ~]$ VBoxHeadless --startvm "winxp"
Oracle VM VirtualBox Headless Interface 4.2.16_OSE
(C) 2008-2013 Oracle Corporation
All rights reserved.

31/10/2013 12:37:13 Listening for VNC connections on TCP port 3389
31/10/2013 12:37:13 Listening for VNC connections on TCP6 port 5900
VRDE server is listening on port 3389.
31/10/2013 12:37:16   other clients:
31/10/2013 12:37:16 webSocketsHandshake: invalid client header
31/10/2013 12:37:16 Client 127.0.0.1 gone
31/10/2013 12:37:16 Statistics             events    Transmit/ RawEquiv ( saved)
31/10/2013 12:37:16  TOTALS              :      0 |         0/        0 (  0.0%)
31/10/2013 12:37:16 Statistics             events    Received/ RawEquiv ( saved)
31/10/2013 12:37:16  TOTALS              :      0 |         0/        0 (  0.0%)

Googling for that error did not give my anything, so I don't know, what and where should I check and repair.

My OS is Slackware Linux 14.1 RC3 x86_64 (i.e. slackware-current) with multilib packages. VBox version is 4.2.16. I have all available packages installed:

Code: Select all

[alex ~]$ ls /var/log/packages/ | grep virtualbox
virtualbox-4.2.16-x86_64-1_SBo
virtualbox-addons-4.2.16-x86_64-1_SBo
virtualbox-extension-pack-4.2.10-x86_64-1_SBo
virtualbox-kernel-4.2.16_3.10.17-x86_64-1_SBo
virtualbox-kernel-addons-4.2.16_3.10.17-x86_64-1_SBo

Any advice or suggestion?

[Perryg]

31/10/2013 12:37:13 Listening for VNC connections on TCP port 3389
31/10/2013 12:37:13 Listening for VNC connections on TCP6 port 5900
VRDE server is listening on port 3389.

You can't have VNC and VRDE listening on the same port, it will kill the port due to conflict.
Look at the guests log file and see if it doesn't mention this.