RDP to Virtualbox

    • OMV 3.x
    • RDP to Virtualbox

      Hello,

      i got a problem connection to VMs via RDP. I already googled a lot for a solution, tried different network-configuraitons (nat, bridged, etc...) but i dont get a connection.

      In the little preview-window i can see the vm running, in the console-tab i only get a grey window...

      Thanks for your help!

      Greetings,
      Alexander
      Images
      • 2016-12-13 17_36_07-Program Manager.png

        81.38 kB, 1,357×594, viewed 1,008 times
      • 2016-12-13 17_36_36-phpVirtualBox - VirtualBox Web Console.png

        38.7 kB, 1,346×617, viewed 635 times
      • 2016-12-13 17_37_20-phpVirtualBox - VirtualBox Web Console.png

        113.48 kB, 1,352×624, viewed 708 times
    • I have had issues with console RDP myself
      but with normal windows rdp client you do not need to use port, just put an IP in the address bar
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • e36Alex wrote:

      or is that the mistake?


      it is, well not a mistake but misunderstanding.
      when you RDP you need to use the IP of the target VM not the host.
      if you are using the host IP it will try to RDP into host not VM.
      the port in VB is given for when you need to setup a clinent used for RDPing and the port is different from the standard defined for remote connect
      i.e. Standard port for RDP protocol is "3389" if you use windows RDP client or any other that complies with standard this is the port it will use. some client let you change the port if needed and this is where you would use the port. not user but you can use the IP:port notation in standard windows client but I am not 100% sure.

      in your case you simply using wrong IP on the client.

      now, I had some issue with VB built in console client as well. and the issue is security.
      if I remember how I fixed it last time I will let you know
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • if it is new I do not think you can RDP into it.
      you have to use the console in VB webpage to set all up.
      hold on a minute I will try to fire up the test setup I have to see if it works
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • ok, I just test the setup

      I could not connect using RDP, even though you are right for new VM you need the host IP and the port
      but it is only work with VNC.

      you need to setup remote display in VM settings/display tab.
      not 100% sure but you do need VNC password. I usually set it to the same user password as the server.

      than using VNC client you can get a nice console and setup VM

      does not work with RDP though.
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • Well I can not explain in details, but essentially they use different protocol and standards to establish connection. It is not about clients per see, it us about underlying technology.
      Rdp is predominately windows standard, in fact it was developed for Windows by Microsoft, and is rarely used in Linux, vnc is multiplatform and can be used on almost all OS.

      Sent from my SM-N910T using Tapatalk
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • Vnc works. I have tried several clients no issues. You need a third party client like tightvnc

      Sent from my SM-N910T using Tapatalk
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • Hello all,

      You can manually configure phpVirtualBox with NGINX or apache2
      On my OMV3 I've installed whole VBOX and phpVBOX by hand, using NGINX for phpVBOX.
      I didn't do it via plugin coz it needs backports kernel if I remember good.

      Please look here for www files:
      sourceforge.net/projects/phpvirtualbox/
      Debian 8.6 Jessie + OMV 3.0.latest Kernel: Linux 4.8.0-0.bpo.2-amd64
      Processor: Intel Core 2 Duo E8400@3GHz
      Memory: 4GB RAM
      OS-HDD: Samsung SSD 120 GB +LVM

      Full media and download center configured.

      BIG and special thanks for OMV-Extras team for great plug-ins (especially: TeamSpeak, VirtualBox, Sonarr, Radarr, and rest I use :))

      ------------------------------

      Wise guy don't know everything, he can search or ask!
      Don't ask me via PM!
    • kawu2 wrote:

      I didn't do it via plugin coz it needs backports kernel if I remember good.
      It needs the backports repo but not the backports kernel. And the backports repo is enabled by default now. Although, I don't have any problems with the backports kernel and all of my systems use it.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I don't know what extra plugin you had to install from linux mint.
      are you talking about Linux RDP service for Mint?
      than it has nothing to do with OMV or VB, Linux dose not support RDP by default, even for VNC you need to install and start a service.
      omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
      SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
      PSU: Silencer 760 Watt ATX Power Supply
      IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
      OS on 2×120 SSD in RAID-1 |
      DATA: 3x3T| 4x2T | 2x1T
    • You can enable a Virtualbox rdp server that allows to connect to the guest just like you were setting in front of the machine. This rdp server is disabled by default but can be enabled with (run commands on the host as root):

      su - vbox -c 'VBoxManage modifyvm "VM name" --vrde on'

      The following command will list the VMs on the host:

      su - vbox -c 'VBoxManage list vms'


      Then you remote desktop to the host:port. Each VM will have a different port. Generally the ports start at 9000.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!

      The post was edited 2 times, last by ryecoaaron ().