3
I often RDP to my Windows 7 Enterprise (32-bit) work desktop from home through an IPSec VPN; I also connect to from work from other Windows 7 and Windows XP computers.
While I am at work, I have no issues with RDP... specifically, the connectivity would be:
- Windows7 (data center terminal) -> Windows7 (work desktop)
- WindowsXP (lab terminal) -> Windows7 (work desktop)
However when I'm at home, I use my Vista Home Premium (64-bit) machine to connect to my same Windows 7 Enterprise (32-bit) work desktop and experience the following symptoms:
- Parts of application window tiles "stick" when I minimize the window through the RDP session, until I move the mouse across the stuck RDP desktop tile or highlight it by dragging across the desktop
- Scrolling with the mouse scroll wheel looks jittery and the screen doesn't paint smoothly via RDP
- Within RDP to my work desktop, using
vim
insideputty
orsuperputty
is almost impossible, since I have to manually shift theputty
window for keystrokes to show up. This is my biggest gripe, since I usevim
as an IDE and all my development is on a linux machine I ssh to viaputty
. - Oddly, the issues are not as bad when I type directly into a router or linux ssh session (without firing up vim inside the putty ssh window). However, my green putty cursor sometimes "sticks" a ghost cursor on the line if I arrow key back to fix an error on that line
I should note that none of those symptoms exist when I RDP from a machine at work; these problems only exist when I RDP from my home MS Vista system.
CPU utilization of my Vista system at home is almost nothing... I routinely run ping plotters from my Vista PC to my Windows 7 work desktop when I VPN from home, but I don't see packet loss or jitter going to the system...
My Question: How can I stop the issues listed above when I RDP to my Windows 7 desktop from my home MS Vista system?
MS Vista System Specs
- OS: Vista Home Premium (64-bit), SP2 [latest patches]
- CPU: Core2 E8400 @ 3.00Ghz
- Memory: 4GB
- Graphics: NVidia GeForce GT 520
(Driver 9.18.13.697)(Driver 9.18.13.1090) - RDPv7 (via KB969084, with persistent bitmap caching turned off)
I tried applying these GeForce settings specifically to C:\Windows\System32\mstsc.exe
, but it did not help...
- Anisotropic filtering: Off
- Antialiasing - FXAA: Off
- Antialiasing - Gamma correction: Off
- Antialiasing - Mode: Override any application setting
- Texture Filtering - Anisotropic sample optimization: Off
- Texture filtering - Negative LOD bias: Allow
- Texture filtering - Quality: High quality
- Texture filtering - Trilinear optimization: Off
- Threaded optimization: Off
- Texture filtering - Anisotropic filter optimization: Off
- Vertical sync: Off
Teamviewer has been increasingly hostile towards defining "fair use/commercial use" to push license sales. Try AnyDesk. If the established connection is a "direct connection" (any static IP server will likely qualify) , you should be able to connect 1 user for several hours with no problem. No install method works best on servers IMO
– Jon Grah – 2019-09-22T14:00:10.923Actually, RDP doesn’t quite transfer graphic data. It works on a higher level, making it more responsive. – kinokijuf – 2013-02-01T11:55:26.593
Yes, I know almost anything about internal work of RDP. But I think this specific details will not help solve the problem of this question. So I gave a simple and easy example in my answer. However RDP transfers graphic data (I don't say that raw pixels is only one type of "graphics data"). Do you think some kind of additional information can improve my answer? – Dmitry Zorin – 2013-02-01T16:06:03.720
I must use RDP, it is the corporate standard... I have always used a 64 bit RDP client connecting to my 32 bit windows desktop... the problems just appeared a couple of months ago – Mike Pennington – 2013-02-02T10:38:53.693