Hi guys
I'm currently messing around with certain VM's on my Proxmox.
One of those is a Linux-Mint as desktop version.
To setup the RDP, I followed this guide:
https://medium.com/@piyushkashyap04...an-ubuntu-machine-a-simple-guide-1e229214aa36
Everything seems to work properly...seems....
Once running the RDP on my Windows10, for a few seconds, it looks like connection builds up (have a black screen and the common bar in the upper middle with the IP of the target PC).
But suddenly the connection closes without any error.
While connecting via RDP, I'm also connected with to the system via noVNC, where I can see on the target system's desktop for 1-2 seconds an icon named "thinclient_drivers" poping up and then disappearing again.
Anybody some idea why I cannot connect with RDP to the machine?
Also tried connecting via RDP when noVNC isn't active - but same result.
What I noted now, that the VM summary says under "IPs": No Guest Agent configured.
Could this be the reason for the issue? But I don't get an error under my Windows when trying to connect to the VM IP that I got from "ip a"
I'm currently messing around with certain VM's on my Proxmox.
One of those is a Linux-Mint as desktop version.
To setup the RDP, I followed this guide:
https://medium.com/@piyushkashyap04...an-ubuntu-machine-a-simple-guide-1e229214aa36
Everything seems to work properly...seems....
Once running the RDP on my Windows10, for a few seconds, it looks like connection builds up (have a black screen and the common bar in the upper middle with the IP of the target PC).
But suddenly the connection closes without any error.
While connecting via RDP, I'm also connected with to the system via noVNC, where I can see on the target system's desktop for 1-2 seconds an icon named "thinclient_drivers" poping up and then disappearing again.
Anybody some idea why I cannot connect with RDP to the machine?
Also tried connecting via RDP when noVNC isn't active - but same result.
What I noted now, that the VM summary says under "IPs": No Guest Agent configured.
Could this be the reason for the issue? But I don't get an error under my Windows when trying to connect to the VM IP that I got from "ip a"