Actually, RDP (Microsoft Remote Desktop Services) may be the fastest on the market. Not surprisingly, because it comes from the folks who develop the operating system itself.
That said, it only makes sense to compare apples to apples. Namely,
1. If you compare RU's Full Control mode against RDP, you need to use the same connection type. In this case direct connection. It doesn't make sense to compare Full Control over Internet ID with RDP over direct connection.
2. Color depth settings should be the same in both cases.
3. RDP can automatically optimize performance. Currently, RU doesn't adjust performance according to connection speed whereas RDP does.
Still, I'm not saying that RDP isn't faster than Full Control, perhaps it is (due to program architecture and some clever code). I'm only saying that the difference may not be that big if you take into consideration the factors above. Soon we'll implement auto-adjustment too.
All in all, Remote Utilities allows you to get the best of both worlds. So you can work with RDP in RU too, and use RU's powerful address book capabilities to manage your RDP connections. We need to fix that drop issue soon though.
I closed the port-forward off, and installed RU on his work PC and home, and it seemed to work fine. Only problem is, anytime there is little to no activity on the RDP session it will drop and "reconnect". This can happen multiple times over a 10 minute span.
This is a known problem when RDP-over-ID is used. This is not about Remote Utilities, more about RDP. But we will see how we can fix or eliminate this problem on our end.
That said, there are a couple questions:
1. If you still want to connect directly using RDP, you could change the RDP port or mask it (using different source and target ports in the port forwarding rule).
2. Why not using Remote Utilities own Full Control connection mode instead of RDP?