Does RDP work with W10?

I can't get my local RDP to work my VM W10. I am using the IP address of my VM and not the UnRAID server. The error msg says that it can't connect. I can't ping it either.

I think you need W10 Pro for RDP server

Ok...I have the W10 Pro installed. Should you be able to ping your VM from your local PC?

Have you enabled a network bridge and configured the VM to use it?  You need to have done this to have the VM visible on the LAN.

As an aside, if you need help with something, the more information you can post the better, screenshots, XML etc....

 

Otherwise it's kind of like sending an email to a doctor saying "I'm not well" and hoping they'll be able to tell you what's wrong. 

The VM Network Bridge was initially set up as virbr0. Also, the VM w10 Pro seems to show a valid Network Connection as Red Hat VirtIO Ethernet Adapter which shows as Ethernet Connected. I would've thought that I could ping it from my local PC on the same network as the UnRAID server.

Here is my XML.......

 

<domain type='kvm'>

  <name>VMWindows10</name>

  <uuid>92f35f71-5522-72df-7bce-84276250db16</uuid>

  <description>This is a test!</description>

  <metadata>

    <vmtemplate name="Custom" icon="windows.png" os="windows"/>

  </metadata>

  <memory unit='KiB'>8388608</memory>

  <currentMemory unit='KiB'>8388608</currentMemory>

  <memoryBacking>

    <nosharepages/>

    <locked/>

  </memoryBacking>

  <vcpu placement='static'>8</vcpu>

  <cputune>

    <vcpupin vcpu='0' cpuset='0'/>

    <vcpupin vcpu='1' cpuset='1'/>

    <vcpupin vcpu='2' cpuset='2'/>

    <vcpupin vcpu='3' cpuset='3'/>

    <vcpupin vcpu='4' cpuset='4'/>

    <vcpupin vcpu='5' cpuset='5'/>

    <vcpupin vcpu='6' cpuset='6'/>

    <vcpupin vcpu='7' cpuset='7'/>

  </cputune>

  <os>

    <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>

  </os>

  <features>

    <acpi/>

    <apic/>

    <hyperv>

      <relaxed state='on'/>

      <vapic state='on'/>

      <spinlocks state='on' retries='8191'/>

    </hyperv>

  </features>

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='8' threads='1'/>

  </cpu>

  <clock offset='localtime'>

    <timer name='hypervclock' present='yes'/>

    <timer name='hpet' present='no'/>

  </clock>

  <on_poweroff>destroy</on_poweroff>

  <on_reboot>restart</on_reboot>

  <on_crash>restart</on_crash>

  <devices>

    <emulator>/usr/bin/qemu-system-x86_64</emulator>

    <disk type='file' device='disk'>

      <driver name='qemu' type='raw' cache='writeback'/>

      <source file='/mnt/cache/VMWindows8/vdisk1.img'/>

      <target dev='hdc' bus='virtio'/>

      <boot order='1'/>

      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>

    </disk>

    <disk type='file' device='cdrom'>

      <driver name='qemu' type='raw'/>

      <source file='/mnt/user/BeallStorage1/Software/Windows 10 ISO image.iso'/>

      <target dev='hda' bus='sata'/>

      <readonly/>

      <boot order='2'/>

      <address type='drive' controller='0' bus='0' target='0' unit='0'/>

    </disk>

    <disk type='file' device='cdrom'>

      <driver name='qemu' type='raw'/>

      <source file='/mnt/user/VMStorage/virtio-win-0.1.112.iso'/>

      <target dev='hdb' bus='sata'/>

      <readonly/>

      <address type='drive' controller='0' bus='0' target='0' unit='1'/>

    </disk>

    <controller type='usb' index='0' model='ich9-ehci1'>

      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/>

    </controller>

    <controller type='usb' index='0' model='ich9-uhci1'>

      <master startport='0'/>

      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/>

    </controller>

    <controller type='sata' index='0'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>

    </controller>

    <controller type='pci' index='0' model='pcie-root'/>

    <controller type='pci' index='1' model='dmi-to-pci-bridge'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>

    </controller>

    <controller type='pci' index='2' model='pci-bridge'>

      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>

    </controller>

    <controller type='virtio-serial' index='0'>

      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>

    </controller>

    <interface type='bridge'>

      <mac address='52:54:00:2b:93:f6'/>

      <source bridge='virbr0'/>

      <model type='virtio'/>

      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>

    </interface>

    <serial type='pty'>

      <target port='0'/>

    </serial>

    <console type='pty'>

      <target type='serial' port='0'/>

    </console>

    <channel type='unix'>

      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/VMWindows10.org.qemu.guest_agent.0'/>

      <target type='virtio' name='org.qemu.guest_agent.0'/>

      <address type='virtio-serial' controller='0' bus='0' port='1'/>

    </channel>

    <input type='tablet' bus='usb'/>

    <input type='mouse' bus='ps2'/>

    <input type='keyboard' bus='ps2'/>

    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>

      <listen type='address' address='0.0.0.0'/>

    </graphics>

    <video>

      <model type='vmvga' vram='16384' heads='1'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>

    </video>

    <hostdev mode='subsystem' type='pci' managed='yes'>

      <driver name='vfio'/>

      <source>

        <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/>

      </source>

      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>

    </hostdev>

    <memballoon model='virtio'>

      <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/>

    </memballoon>

  </devices>

</domain>

 

 

UPDATE: I think this is my issue................excerpt from WiKi..............

 

Configure a Network Bridge

 

There are two methods by which your virtual machines can get access to host-based networking: through a private NAT bridge managed by libvirt or through a public bridge managed by unRAID directly. The private bridge (virbr0) is automatically configured when libvirt starts. The public bridge can be created through the Network Settings page on the unRAID webGui.

 

The private bridge generates an internal DHCP server/address pool to create IPs for VMs automatically, but the VMs will be on a subnet that cannot be accessed by other devices or even other services on unRAID. This type of bridge is ideal if you want your VM to be completely isolated from all other network services except internet access and the host's network file sharing protocols. VM management can be performed through a VNC session provided by the browser.

 

The public bridge provides VMs with an IP address from your router, but internally bridges communications between VMs and each other, as well the host. This type of bridge is ideal if you want your VMs to act just like another device on your network, where you manage it's network access at the LAN-router instead of inside the VM. We persist MAC address settings for the virtual interfaces you create, ensuring the VMs should get the same IP address each time they connect, as long as your router-managed DHCP pool doesn't run out of addresses. So if you want to connect to your VM from another PC, laptop, tablet, or other type of device, you should use the public bridge.

 

Whichever bridge you prefer can be defined as the Default Network Bridge on the VM Settings page.

****************************************************************************************************************************************

 

Ok...so, I can now ping the VM W10 Pro from my local PC but, when I try to RDP I get an error msg "The remote computer requires Network Level Authentication, which your computer does not support." I cannot tell if its talking about the VM W10 Pro or my local PC running WXP. I think I will try to RDP from my IPad and see what happens.

 

 

 

 

 

Give splashtop desktop a try. Better performance than rdc

Go into RDP on the VM and change the setting...

Go into RDP on the VM and change the setting...

I took another look at the Remote Desktop settings on my VM w10 Pro. As I thought, I had the "Allow remote connections to this computer" button selected and had the checkbox below "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)" also checked. I decided to uncheck the bottom checkbox and voila....... SUCCESS!!

 

However, my screen background is black and the Background Settings say "Your background is currently turned off by Remote Desktop Connection".

UPDATE: I think I have a black background because my local PC is running wXP.