virtualbox.org

Hi

I got the following issue. Today i installed a new vm with win10 2009 added the guest additions and installed the virtualbox extensions too.

The Problem is that i can't connect to the headless vm via RDP. Win10 is configured to accept rdp connections on it's standard port 3389 and vrde is running on port 3390. The ethernet adapter of the guest ist configuerd in bridgemode with a fixed ip and it can connect to the web and i can ping it after i activated the rules for file and printersharing in the firewall app settings.

For testing i opened all incoming ports of the windows 10 host for virtualboxmanage.exe and virtualboxheadles.exe in its firewall. Doesn't help.

Maybe someone has a hint what the problem could be?

Gerne auch auf deutsch.

I regularly use RDP to communicate with a headless Win10 VM running in bridged network mode, so IMO there is nothing systemic in VirtualBox which prevents it. I did not have to whitelist any VirtualBox applications.

Why did you give the VM a static IP address? That is the only important change from how I normally do it - choosing a static address means that the address isn't necessarily known to other devices on the host physical network. In my case I let the VM be assigned an IP by the host DHCP server, and I connect to it using the "network host name" of the VM (my LAN has a PiHole DNS, so it can turn local names into LAN addresses). However if I wanted to assign a static address I'd configure that at the host network DHCP.

i don't have access to the dhcp in the network to manually set the ip to fixed or at least change the leastime for the ip to endless.

It has to be fixed because there is or should be a firebird db running on port 3050 to which different useres connect. A fixed ip of the server helps to prevent connection issues if the dhcp would cast a new ip to the vm.

edit. i assigned a ip by dhcp but sadly it did not help.

AFAIU, you didn't clearly state which IP address belongs to which system, so just in case you did it wrong:

You can either connect to the VirtualBox VRDP server running on the host with "<host IP>:3390", or to a Windows RDP server running in the guest with "<guest IP>:3389".

thank you for proofing that i am an idiot

tried to connect to [guest]:3390 all the time. never thought about [host].

TY!

Hmm. It might also have helped if you had mentioned in post #1 that you were talking about the VRDP function in VirtualBox, and not the RDP feature of Windows, despite referring to RDP throughout.

In the VirtualBox User Manual, the terms VRDP and VRDE are both used to describe different aspects of the VirtualBox VRDP Support, and the OP used the term VRDE in the heading and in the text. In addition to that, the OP was talking about both the VirtualBox VRDP and the Windows RDP services.