Quote:
Are there any hoops for the remote user to jump through in order for me to gain remote access?
For terminal services (remote desktop) access, it needs:
- To be enabled in the SYSDM.CPL screen as I described above.
- Not blocked in the firewall. (In theory, enabling it as above should automatically unblock it through the firewall, unless you are using a thirdparty firewall.)
- The desired login user needs to be added to the group of users for terminal services acces. This can all be done from that same screen, IIRC. Note that members of the local machine's "administrators" group (this includes domain admins if the machine is domain-joined) are already enabled for this.
- You need to be able to get to that machine's IP address. For instance, if there's NAT in the way, you might have trouble.
For remote assistance, the requirements are similar, but you don't need to spec a user, it goes by straight password authentication.
The difference between terminal services and remote assistance, is that remote assistance is like a "chat" with both of you seeing the same screen at the same time, and you showing him how to get things done. Terminal services, their screen goes blank and they can't see what you're doing.
Previous Topic
Index
