RDP to a PC running RDM closes after a few seconds
I have a PC in the office I often RDP into from home, using RDM free. If RDM (licensed) is running on that PC, the session closes after a few seconds. If it is not, the connection works first time, every time. It doesn't appear to matter what else is or isn't running; RDM running, can't stay connected. RDM not running, connection normal. It also doesn't appear to matter if RDM is connected to anything, or what it's connected to. I have a network ping testing tool running on that PC also, and it's often unable to access the network briefly at the same time (lost packets are red, but the time shows up as grey, which is something like "network not available"). Is there something, like maybe a forwarding feature, that might explain how an incoming RDP session is interacting so badly with a running RDM?
EDIT: After the connection is stable, I can run RDM normally without disconnection.
All Comments (3)
Hello,
If you RDP to this PC with mstsc do you get the same issue ?
If not, do you get the issue when running the RDP session as "External" instead of "Embedded" ?
What version number of RDM is installed on both PCs ?
Best regards,
Don't worry about this. I did a big round of maintenance on the PC, uninstalling a few things, upgrading the video drivers and in particular removed the nVidia desktop manager. This morning, for the first time in about a month, I was able to log into the PC to discover I'd left RDM running. So, it's not the problem, but there's a chance it interacts poorly with other utilities when the screen topology changes, or that it's sensitive to video drivers getting a little out of date when hardware-accelerated RDP is being used. Make of that what you will.
Hello,
Thank you for updating us regarding this as well as informing us of the possible cause of this issue.
I'm glad to read that this is now working.
Best regards,