If a RDP client is overrun with viruses and trojans is there any risk to the Terminal server? Printers are the only local resource that is shared. Connection to the server is through a Gateway. User authentication is assured (Through something like phonefactor).
3 Answers
My concern would be that on an infected client someone would use a keyboard logger or something and collect the credentials and server information that was used to establish the RDP session. If a system has malware, then having a keylogger installed is a real possibility.
![](../../users/profiles/984.webp)
- 128,755
- 40
- 271
- 413
-
+1 that's a good point. – squillman Feb 23 '10 at 01:00
-
Good point and all too easily overlooked. – John Gardeniers Feb 23 '10 at 01:10
If you have File Sharing turned on, yes it's possible for virus to upload themselves to the terminal service
![](../../users/profiles/25622.webp)
- 1,482
- 9
- 10
You should be good, if you're connecting strictly via RDP. The only thing that might get you is if something weird was configured to run when the connection is established. For example, if you are using the built-in Windows RDP client then you can set a program to run when the connection is made. In the off-chance that you have something detrimental to the server set up there then something bad could happen I suppose. That's somewhat of a longshot, though, I'd think.
You might also get something funky if you set the clipboard to share with local resources. And for sure don't bring local drives to the party (following Stephen Thompson's answer on file-sharing).
![](../../users/profiles/1054.webp)
- 37,618
- 10
- 90
- 145