| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 116120 | 2011-02-17 19:36:00 | RDP vs TightVNC | GR8Metal (14133) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1179284 | 2011-02-17 19:36:00 | Hi Team, Would there there be any performance difference between using Windows RDP or TightVNC? PC will be on standard 100mb LAN. Cheers :cool: |
GR8Metal (14133) | ||
| 1179285 | 2011-02-17 19:59:00 | Yes, there is a difference (RDP is generally better), but on a 100m connection you're not likely to notice it; you'll only really see a difference on a slow link. | Erayd (23) | ||
| 1179286 | 2011-02-17 20:03:00 | TightVNC will use the session of the currently logged in user, they can still use it. RDP will lock the screen, so they can't see what's going on. There's other limitations also... We have both installed here at work. Using TightVNC, you can also password protect the admin interface. Well worth doing. Remove access to the registry through regedit also in case they get clever ;) |
Chilling_Silence (9) | ||
| 1179287 | 2011-02-17 20:14:00 | RDP will lock the screen, so they can't see what's going on.Depends how you use it - it's quite possible to share a session; that's what remote assistance does. There's other limitations also...Any chance you could expand on what those are? Using TightVNC, you can also password protect the admin interface.As does RDP by default; it's handled via standard Windows permissions. Don't get me wrong though, they're both great tools, and on a 100m network the OP should be choosing on features rather than performance, as at that speed there's not much difference between them performance-wise. |
Erayd (23) | ||
| 1179288 | 2011-02-17 20:29:00 | If you're using Windows XP as the client, then you've only got 1 active session. Term serv is different. |
Chilling_Silence (9) | ||
| 1179289 | 2011-02-17 20:47:00 | If you're using Windows XP as the client, then you've only got 1 active session. Term serv is different.I'm not talking about terminal server - even on XP, it's quite possible to share a session - I do this all the time at work. This is what Microsoft calls 'remote assistance' - it's just RDP that connects to an already-running local session and allows shared viewing / control with the existing logged-on user. |
Erayd (23) | ||
| 1179290 | 2011-02-18 02:09:00 | I use RDP exclusively at work, and sometimes when jumping between multiple machines I need to send ctrl alt del and cant, while you can in VNC. | nedkelly (9059) | ||
| 1179291 | 2011-02-18 06:08:00 | I generally use UltraVNC. It does file transfer as well (others probably do too). Their SC binary server is tiny, requires no installation and is a no-brainer for remote support behind a router. I find it faster over slow links than RDP and it's easy to poke through an SSH tunnel. |
fred_fish (15241) | ||
| 1179292 | 2011-02-18 07:59:00 | I use RDP exclusively at work, and sometimes when jumping between multiple machines I need to send ctrl alt del and cant, while you can in VNC. You can use CTRL+ALT+END in RDP. |
CYaBro (73) | ||
| 1179293 | 2011-02-18 22:21:00 | You should make your decision based on what you want to do. If you want to connect to the machine and do work yourself then use RDP since it's way easier and the client comes with every version on Windows. Keeping in mind that you'll need XP Pro or W7 Business+ to be able to connect to the machine. If you want to help someone do something by shadowing their screen then use VNC. Remote Assistance is a bit flaky :) RDP is faster, VNC is known for it's slowness. |
WarNox (8772) | ||
| 1 2 | |||||