RDP Issue

[travismailsa]

Hi, i have managed to get it working on my pc. No problems with windows 2004 update. On another pc, running Version 10.0.18363 Build 18363 - version exists in ini file - when i rdp in, the rdp session displays over the local session. So the actual local machine sees or displays the remote session. When signing out, it returns to the normal desktop. Why is this?

[robbak]

So, you have a running session, open and logged in on the local computer. Then when you log in from another computer with a different user account, you get a new session for the remote computer, but that remote session is also displayed on the local monitor - is that right? Can you both operate the computer at the same time, or can only the remote user control the mouse and keyboard?

And then, when you log out of the remote session, it disappears from the screen and the old local session returns?

Weird. The important thing might be the hardware. Some graphics drivers don't play nice with RDP. Could you reply with your graphics setup and graphics driver versions?

[travismailsa]

Thanks for the reply. (So, you have a running session, open and logged in on the local computer. Then when you log in from another computer with a different user account, you get a new session for the remote computer, but that remote session is also displayed on the local monitor - is that right?) - That is correct, unfortunately i am not sure if the local pc can control the remote session as i am setting this up remotely via teamviewer - there is no user on site at the moment. You are also correct in the understanding of once you signout/disconnect the remote session, the local desktop returns , still signed in and active.

Currently this is being setup on a Microsoft Surface Pro 7, running hybrid display with Intel and Nvidia - I will try get the driver information of both, but last time i worked on the pc - a week ago, i updated both drivers too the latest version. Should i try force the laptop to use only the Intel driver as a test?

[robbak]

Ok - one thing I do know - Teamviewer and rdp do NOT work well together. Teamviewer has to guess which session you really want - and it is probably making the wrong decision.

Wait until there is someone on site before going further - it could be working just fine. Teamviewer is just selecting the new rdp session to connect you to, instead of sticking to the local session as you expected.

On Mon, 20 Jul 2020 at 20:45, travismailsa notifications@github.com wrote:

Thanks for the reply. (So, you have a running session, open and logged in on the local computer. Then when you log in from another computer with a different user account, you get a new session for the remote computer, but that remote session is also displayed on the local monitor - is that right?) - That is correct, unfortunately i am not sure if the local pc can control the remote session as i am setting this up remotely via teamviewer - there is no user on site at the moment. You are also correct in the understanding of once you signout/disconnect the remote session, the local desktop returns , still signed in and active.

Currently this is being setup on a Microsoft Surface Pro 7, running hybrid display with Intel and Nvidia - I will try get the driver information of both, but last time i worked on the pc - a week ago, i updated both drivers too the latest version. Should i try force the laptop to use only the Intel driver as a test?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/stascorp/rdpwrap/issues/1125#issuecomment-660951828, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMCGIRNW6BWTD3A6ON5OX3R4QN4HANCNFSM4PCAZESQ .

[travismailsa]

That makes sense, thanks it did cross my mind, but not sure if it would affect mstsc and 127.0.0.1. Will see if i can get someone to assist later and will give feedback.

Thanks so much