No VNC or RDP connection when GPU is active

[sEEbE]

Hi All,

I'm running a TS-1277 with NVIDIA Quattro P4000 GPU. On the VM I'm running Windows Server 2016.
On my first setup (without GPU pass through) VNC and RDP working fine.
After I add GPU VNC and RDP connection got refused. With a direct connected monitor, mouse and keyboard all is working.
NVIDIA drivers and tools from guest CD was installed.
When I remove GPU pass through VNC and RDP working again.

Any idea how to make RDP working with GPU pass through?

Thanks
Frank

[Trexx]

VNC you would need to install a VNC Server within the VM to enable access to that with GPU. For RDP, just enable remote desktop support within Windows 2016.

[sEEbE]

Hi Paul,

thanks for your answer but VNC and RDP are working fine as long as I not use GPU pass through.
I only stop the VM, add GPU and restart. Now VNC and RDP connections are not possible.

Cheers
Frank

[Trexx]

Hi Paul,

thanks for your answer but VNC and RDP are working fine as long as I not use GPU pass through.
I only stop the VM, add GPU and restart. Now VNC and RDP connections are not possible.

Cheers
Frank

I understand... and I gave you the solution. I have an x77 and have used GPU VM's in VS as well. RDP works just fine on my win10 VM w/GPU.

GPU Passthrough breaks the "built-in" VS vnc that was leveraging the SW based Graphics cards. WIth the GPU, you have to install VNC server (which is bundled as an option on the Guest Tools btw).

RDP works fine for me (I think I did have to enable it in WIn10 though initially).

[sEEbE]

Hi Paul,
again thank you for the fast response.
After GPU was enabled I connected a local display, mouse and keyboard. I installed the tools from the guest cd and disabled and enabled RDP.
But unfortunately I was not able to connect with vnc or rdp to the vm. Only local logins was possible.
After I removed the gpu I was able to connect again as before.
Cheers
Frank

[Trexx]

The VNC Server isn't part of the tools, but a separate option you have to select. I don't recall if you have to select custom install to be able to choose the option or not.

As for RDP, I would do some googling on that. Also make sure you are pointing at the WIndows 2016 IP address for your RDP connection and NOT the NAS IP address.

[sEEbE]

Thanks for your help Paul.
I'll do some more tests after my business trip and come back with more information

[sEEbE]

Hi Paul, hi all,

after more tests I saw the core reason of the issue.
In my VM where the IP address was hard coded in the setup the add of the GPU changes the whole network setup and I got a different IP address.
After I set a new fix IP address all works fine.
Again for all: VM with GPU and the same VM without GPU have different network setup.

@Paul: thanks for your effort on this and sorry that I saw the network change so late.

Cheers Frank

[Trexx]

Hi Paul, hi all,

after more tests I saw the core reason of the issue.
In my VM where the IP address was hard coded in the setup the add of the GPU changes the whole network setup and I got a different IP address.
After I set a new fix IP address all works fine.
Again for all: VM with GPU and the same VM without GPU have different network setup.

@Paul: thanks for your effort on this and sorry that I saw the network change so late.

Cheers Frank

No worries Frank. Glad you are up and running.

[zsolt_bezdan]

Very similar situation ("VNC or RDP connection when GPU is active") but in case with Linux VM
TVS-1282T3 (4.3.5.xxx), VM-CentOS7.3, GPU (1050ti/P2000).
CentOS 7.3 distro -Blackmagicdesign with Nvidia drivers.
1) If GPU switched on- connected monitor (via GPU's HDMI) + wired mouse and keyboard is fine. Davinci Resolve 15 rendering excellent. But no access via Virtualization Station, VNC, RDP.
2) If GPU switched off - No Davinci Resolve, but I have access via VS3, VNC etc.