Connecting using the MRC Proxy

The new and improved "Connect via Proxy Host" feature in version 6.0 and above allows you to connect to multiple machines on a remote network through a "single point of contact" on the remote network.

Instructs the MRC program to attempt to connect to the destination machine, via this Proxy Host.

Proxy Host to be used, to forward the MRC connection request. **This Proxy Host machine must be running the MRC Client Agent Service, and the "Enable Proxy" setting must also be enabled .

Ordinarily when you connect to a machine via the Mini Remote Control program (without the proxy), it's basically a straight TCP connection to the remote machine using that specific TCP port (default is 6129), provided the MRC Client Agent is already installed & running on the remote machine. The Mini Remote Control program's ability to remotely install, start, stop, or remove the Mini Remote Client Agent Service uses the Operating System's installed protocols, basically File & Printer Sharing (i.e. 137-139/445). However, we do not recommend that you open these ports on your router/firewall because those are the same ports used by any remote service install and could potentially be a security issue. Also, when connecting to remote machines behind a firewall, you would be required to install the Mini Remote Client Agent Service on a different TCP port for each remote machine that you wish to remote control. You would then have to open & forward the corresponding TCP port in the remote firewall for each machine running the Mini Remote Client Agent Service on the remote network.

1. The Mini Remote Client Agent must already be installed & running on the Proxy machine, and the destination machine. It cannot be installed "on the fly" when using a Proxy connection. However, it can be upgraded on the fly, provided it’s currently running version 6.0 or above of the Agent. So you may have to piggy-back two MRC connections to initially get version 6 of the Client Agent on your destination machine.

2. The "Enable Proxy" setting must be enabled within the Client Agent Service on this machine that will be used as a proxy.

3. The connection to the Proxy machine is performed via a Straight TCP connection, just as above.

4. The proxy machine then forwards your connection request to the destination machine.

Basically, the new "Proxy" feature eliminates the requirement of having to use (and port forward) a different TCP port for access to each individual machine behind a remote firewall. You can now pick a single machine on the remote network to be the DameWare Remote Control program's central point of contact for access to the entire remote network.

By enabling the "Proxy" feature of the Client Agent Service on that machine, it allows you to forward a single inbound TCP port to the Proxy Host machine to establish connections to other machines on the remote network. The Proxy Host receives the connection request and then forwards the request on to the appropriate machine on the remote network. Once the intended remote machine has received the connection request from the Proxy Host, you will see the desktop of the destination machine in your MRC window.

•	Allows you to use a single TCP port in the remote firewall to access multiple machines on that remote network, rather than having to open a different TCP port on the remote firewall for each machine that you wish to remote control.

•	Also allows you run the Mini Remote Client Agent Service on the same TCP port for all machines on the remote network, rather than having each machine run the Client Agent Service on a different TCP port.

•

Also allows you to use the actual (private) IP-Address of the remote machine, rather than having to use the Public WAN IP-Address of the Router/Firewall. However, you must specify the Public WAN address for the machine running the "Proxy Enabled" Client Agent Service, in addition to the correct TCP port number that the Client Agent Service is listening on.