Debian 64 VRDP stuck on configuring remote session

[Karol159]

I have created virtual machine with Debian_64. I'm trying to use it as remote headless machine.
Unfortunately I can't connect to it via VRDP.
OS is not even installed.
I have configured VM with nat networking and redirected custom port to VRDP.

I'm trying to connect from Windows 7 machine. Connection stuck at "configuring remote session" and after a while timeout occurs.
I have been trying to connect from Raspberry PI with Raspbian, also no luck.

Any ideas what I have done wrong?

My config:
VirtualBox 5.0.16 with extension pack, the same version
Host runs on Debian 8.3 with 8GB of ram. On VM I'm trying to install the same Debian 8.3 but with 512MB of ram.
Log in attachment.

[Perryg]

Have you followed the manual? http://www.virtualbox.org/manual/ch07.html http://www.virtualbox.org/manual/ch07.h ... 7704257984

I also see a problem with the type selected and the install media.

Code: Select all

00:00:00.189727 Guest OS type: 'Debian_64'
00:00:00.201582 File system of '/home/username/Software/debian-8.3.0-amd64-i386-netinst.iso' (DVD) is ext4

You either need to select Debian ( without the 64-bit ) or download the 64-bit ISO.

[Karol159]

Yes, I have created my VM exactly from this manual.

That iso contains installer of 32 and 64-bits Debian, but I have downloaded 64-bit iso as suggested. Nothing changed.

VM seems to be booting properly from that iso. I assume this by taking a screenshot of working VM(in attachement).

[Perryg]

Ok so the vRDP is working or you would not see the install screen. Post a new log file with 65-bit install.

[Karol159]

Yes, vRDP seems to be working, but it can't somehow configure connection.

New log in attachment

[Perryg]

Can you use the arrow keys to move up and down in the install screen?

From the hosts terminal type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

[Karol159]

That screenshot was captured by command:

Code: Select all

VBoxManage controlvm "vm_name" screenshotpng ss.png

Not by vRDP, so I can't perform any input.

Strange thing happened. I have created another VM, with the same settings but on root user and different vRDP port and I have connected successfully.
So I have tried creating another one with root user, but now I can't connect neither to old nor new. I have tried removing them and creating again, but no luck.

vm info in attachment

[Perryg]

You really don't want to run as root. Ever. How was the VirtualBox install preformed? Was it an elevated user or did you actually log in as root?

[Karol159]

I know, It was just a try.

VirtualBox was installed in host system by root. VMs are created and executed by regular user with no special permissions.

[Perryg]

This is very important. Did you use su or did you log off and back on as root to install VirtualBox?

[Karol159]

I have logged in by ssh with regular user, then logged in to root by 'su' command and performed installation.

[Perryg]

That would be the proper way.
You say you log in to a shell then run the install on the guest. Is the host a headless server and you are actually doing all of this from a remote location? If so then you very well may have a port conflict. Hard to diagnose this from afar I am afraid.

[Karol159]

Host is headless, really remote location server.

but, I think I have found the problem.
I'm forwarding vRDP port like this

Code: Select all

VBoxManage modifyvm "VM name" --natpf1 "rdpname,tcp,,5012,,5012"

I understand that, connecting to host at 5012 port will forward connection to 5012 on my vm. This is not working in my case.

When I changed vm port like this

Code: Select all

VBoxManage modifyvm "VM name" --natpf1 "rdpname,tcp,,5011,,5012"

I can connect to vRDP on vm on port 5012.

Isn't it strange?

[Perryg]

Not if you think about it. You use 5012 to connect to the host and then you try to port it to the guest and there is your conflict.