virtualbox.org

Hello,

I currently have a windows 2012 server running on virtualbox, with RDP enabled on it.
but my problem is, wen i connect to the server with the IP:PORT it boots me straight to the desktop, with out asking for any login credentials.

I did already try, using NAT with port forward and Bridged Adapter, but both don't work as intended.

RDP is enabled on the server, with the option: "Allow Connections only from computers running remote desktop with network level authentication" and i have the users selected.
Also on the local group policy editor i do have "always prompt for password upon connection" Enabled, still after all that no authentication shows up.

Thanks to any one that can help me with this issue.

Sounds like you are connecting with vRDP and what you need to use is RDP. Set the guest to bridged and use that address instead of the host address + port.

Perryg wrote:Sounds like you are connecting with vRDP and what you need to use is RDP. Set the guest to bridged and use that address instead of the host address + port.

But then if i use Bridged the vm does not have internet connection.

I assume then that you do not have a router?

If not then use host-only for the host to be able to reach the guest and a second adapter set to NAT for the guest to be able to get to the Internet.

See chapter 6 in your VBox users manual

Thanks for the help so far guys, its appreciated.

What i am trying to achieve is to use virtualbox for container management for windows 2012 and centos. and then use a rdp / ssh protocol directly into the servers. The problem we seem to be having is that, we were using vrdp which is why windows doesn't prompt for login every time. so we are having to instead, i believe create a 2012 server and then enable rdp services with network management involved on the server to allow rdp.
The master server has failover ip's on the server available and a primary ip. so my problem is how do i get rdp to work properly with virtual box so that it prompts login every time.

You simply do not use the host IP and port as this will usurp the login on the guest. How you achieve direct communications to the guest is the issue you face. Simple network 101. Look at the guests as another PC on the LAN and not an app to the host. How would you do this on metal?

trying to get my head around creating a new vm on VB and to get to rdp into that server. the actions i need to take ?
is there a way of connecting to the particular vm by ip ... is port required ?

If you use the guests RDP the port is defined there and if you left it set to default it would be 3389 but you should not need the port entered in the client.

The only way you can use the guests RDP is Bridged or Host-Only as NAT is not a LAN protocol as such, it is a one-way Internet connection.

You would leave the remote unchecked in the guests settings as you will not be using the VBox vRDP server.

Then is just a simple IP address of the guest in the client.

As Perry said, this is networking 101, not rocket science.

I think your major problem is that you have not learned to look at the virtual machine as a machine in its own right, not as a part of the host. If you run the vm using bridged networking, VirtualBox allows the guest to have joint use of the physical network adapter. That is really the end of the story. From that point on, the vm behaves just like any other LAN machine from a networking point of view. It will get its network config from the LAN DHCP and behave just as you would expect a physical LAN machine to behave. LAN machines contact it directly by name or address.