virtualbox.org

I am using virtualbox v 5.0.24 on unbuntu server 16.0.1.
I imported a vm from ubuntu 12.x with vb 4.x . When I connect with uvnc to the server vnc asks for a password.
vboxmanage showvminfo firewall1 gives:
VRDE: enabled (Address 0.0.0.0, Ports 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
Video redirection: disabled
VRDE property: TCP/Ports = "3389"
VRDE property: TCP/Address = <not set>
What is the password? And where can I find it?
I also created a new vm but that also asks for a password and I tried tightvnc and there the password question is also asked.
I'm a bit out of options, and as the server is command-line only I cannot access the console.

Edit:
I include the messages I get on the server:

root@hmgrwk:~# vboxheadless --startvm firewall
Oracle VM VirtualBox Headless Interface 5.0.24_Ubuntu
(C) 2008-2016 Oracle Corporation
All rights reserved.

09/10/2016 18:04:50 Listening for VNC connections on TCP port 3391
09/10/2016 18:04:50 Listening for VNC connections on TCP6 port 5900
VRDE server is listening on port 3391.
09/10/2016 18:05:02 other clients:
09/10/2016 18:05:02 Normal socket connection
09/10/2016 18:05:02 Client Protocol Version 3.8
09/10/2016 18:05:02 Protocol version sent 3.8, using 3.8
09/10/2016 18:05:02 rfbProcessClientSecurityType: executing handler for type 2
09/10/2016 18:05:09 authProcessClientMessage: authentication failed from 192.168.17.149
09/10/2016 18:05:09 rfbAuthProcessClientMessage: password check failed
09/10/2016 18:05:09 rfbClientSendString("password check failed!")
09/10/2016 18:05:09 Client 192.168.17.149 gone
09/10/2016 18:05:09 Statistics events Transmit/ RawEquiv ( saved)
09/10/2016 18:05:09 TOTALS : 0 | 0/ 0 ( 0.0%)
09/10/2016 18:05:09 Statistics events Received/ RawEquiv ( saved)
09/10/2016 18:05:09 TOTALS : 0 | 0/ 0 ( 0.0%)

jpflathead wrote:What is the password? And where can I find it?

Please read Chapter 7.1.5. RDP authentication for more information.

Also keep in mind that RDP and VNC are totally different. If you are really using VNC you would normally set the password in the *.vbox file ( use the manual for how )
Using RDP VBox does not set a default password, the user does.

socratis wrote:

jpflathead wrote:What is the password? And where can I find it?

Please read Chapter 7.1.5. RDP authentication for more information.

I configured vb to use VBoxAuthSimple but still at first I get this screen I attached.

Oh and by the way rdp (MS remote desktop) doesn't work either

You seem to be misunderstanding one thing; VNC it not RDP. Did you read Perry's reply?

socratis wrote:You seem to be misunderstanding one thing; VNC it not RDP. Did you read Perry's reply?

Yes, I read it and the line
VBoxManage modifyvm "VM name" --vrdeproperty VNCPassword=secret
solved my problem.
Thanks

Leaving this here for the next weary Googler looking for answers. I have found that virtualbox, or at least the open-source package that's available through Ubuntu 16.04's package repositories, ships with an extension titled simply, 'VNC'. This extension is (and all respect for the community that developed it) a new, half-baked, community-sourced replacement for VRDP that's delivered in the normal "Oracle VM VirtualBox Extension Pack". The 'VNC' extension listens somewhat to the 'Display' configuration screen you get to using the GUI virtual machine settings window, and somewhat to settings supplied on the command line (see previous post in this thread for an example of one of those commands) - in particular it listens to the 'port' setting and the setting that enables it. I believe the port has been set to '3389' by default in the past (and possibly even now) by virtualbox when creating VMs, because the normal extension pack uses RDP, not VNC. Long story short, the VNC plugin conflicts with the VRDP portion of the normal extension pack. This conflict can cause you to not be able to use VRDP or VNC to remotely access your VMs. It was actually causing my VM to crash unexpectedly also. If you want to use VNC to do this, and you see that the VNC plugin is installed, then you will need to use VNC, not RDP (even though the port may very well be set to 3389). I'd also suggest that if you want to use VNC, you do not install the normal extension pack. If you want to use RDP, as you did in the past, remove the 'VNC' extension, and RDP will begin working as before (that's what I did to take advantage of the other features of the normal extension pack).

heltoupee wrote:virtualbox, or at least the open-source package that's available through Ubuntu 16.04's package repositories

Two different animals. Not saying that the glitch you reported isn't in official Virtualbox, but if all you're using is the Ubuntu repository of Virtualbox, you need to try your glitch by uninstalling Ubuntu's version and installing from the Virtualbox website. Linux distros may change and have changed Virtualbox in ways not known to the developers. Until the weary Googlers see that you have confirmed the glitch in official Virtualbox, they should consider that official Virtualbox may not have that issue.

FWIW, the guest's RDP port can be changed in the guest Display settings to be something else besides the MS RDP default 3389 port number.