I do use teamviewer. I'm finding Remote desktop connection to be significantly faster. Team viewer is giving me a framerate of around 5-10fps. Remote desktop connection is getting me 55fps. Not that the framerate is all that important, but the reality is why not work with what is giving me the best performance? When I'm dragging windows around on teamviewer they 'teleport'. The cursor stutters as well. Remote desktop connection is as flawless as if I were sitting right there at that computer. When fullscreen I literally can't tell a difference between it, and my own desktop.

Rdp is very unsecure and should not be running it direct. There is too much risk involved with it. To secure it properly you need to run a vpn connection. I would not directly open that port on any network.

Also rdping on the the local lan is different than on the internet. Local you have between 100 and 1000Mb/s. The internet you have between 1 and 50, it is only as fast as your upload or the remote sites download. Which ever had the slowest speed.

How are you using TV -- are you connecting local? How are you using RDP - local? As sc302 mentions there is a huge difference between doing these technologies on the local lan vs interent. Don't you have a 150mbps connection, what is your upload speed?

Where are are you at and what is that speed for internet?

I use both TV from work and RDP through a openvpn connection to my home network. Both work just fine - I normally just rdp in because I normally have the vpn connection open. But if something goes wrong with the vpn I TV in, etc. I will do some testing to see which one works better today from some sort of fps? How are you measuring this? I don't recall RDP showing any sort of FPS number? But maybe I never looked.

Also if you want to use rdp from remote, you also need to know what your public IP is or us some form of dynamic dns to get your public IP.

Unsecure how? If by a user having a weak-password, then this isn't RDP's fault. You could always change the listening port in the registry and make it something non-standard, that will cut down on most of the 3389 attempts right there since most drive-by attackers won't bother scanning and just go straight for the single port, if it's closed, most will move on.

I am not currently aware of some open RDP vulnerability that Microsoft hasn't patches in their currently supported OS's...

I err to the side of caution. Microsoft is constantly under the gun...constantly. While the RDP protocol itself is secure the insecurity comes from users. There are no requirements for passwords, that in itself is an issue and what can makes it unsecure.