|
Peter, in my experience, there are no pitfalls with remote desktop, you're essentially on the desktop of the machine you're remotely connected to. I use RD every day for work, we have RD set up from the outside world via the net and port mapping, using alternate ports to the standard (which is 3389) and with user accounts that lockout after 3 incorrect login attempts. I use this when I'm on holidays for support purposes.
Works a treat for everything we do, every app works including some that use an outgoing ISDN modem to dial in to PABX's.
BTW grid dishes are overkill for the distance you're using (grids will work at distances over 10Km) and may even give problems as they're prone to picking up interference from the rear.
If you get interference problems a better option are the 12db panels which, although directional, don't pick up from behind. You can even print remotely if you have the same driver on both the remote and host machine. Given that you're using wireless make sure you have encryption set up and it wouldn't be a bad idea to change the default RD port (I use something in the 32000 and upwards range, a simple registry hack, just google for it) and set up some login restrictions just in case someone does manage to hack your network.
To put an account login restriction (you need to have first applied a password to the host machine user account) go to Control Panel, Admin Tools,Local Security Policy, Account policies, Account lockout policy. You'll find settings for the number of login attempts, a time period for those attempts and a lockout period if you number of unsuccesful attempts has been reached.
|