The default communication profiles that are enabled on the Host are LAN (TCP) and TCP/IP (UDP).  To connect to a Remote Control Host that is behind a router or hardware firewall, using one of these communication profiles, you will need to configure the router or firewall to include a port forwarding rule.

Create a port forwarding rule for TCP on port 6502 to the private IP address of the Host.  You may also optionally create a port forwarding rule for UDP on port 6502 to the private IP address of the Host.

When your Guest is trying to reach this Host across the Internet, I recommend that you use the communication profile called Internet (TCP) on the the Guest and enter the public IP address of the Firewall or Router in to the address field of the Guest and select the Connect button.  The Internet (TCP) communication profile is compatible with the LAN (TCP) profile.  If you added a rule for UPD, you may also have the option to use the TCP/IP communication profile in the Guest.

If this does not work, you should verify that the Host is running and then check the activity log on the Router or Firewall to verify that the TCP or UDP from the Guest is reaching that device.

In some environments, it may be necessary to configure the Host computer to use a static private IP address so that it will not change later.  Go to the Command Prompt and enter the ipconfig command to obtain the current values.  Then in Windows go to the properties of the TCP/IP protocol and manually configure it to always use the values you obtained from the ipconfig command.  (On Windows XP go to Start > Control Panel > Network and Internet Connections > Network Connections.  Then select the active connection. In some cases this may be "Local Area Connection"  Go to Properties and then highlight Internet Protocol (TCP/IP).  Select the Properties button.  Now you can manually configure the IP address.)

Idea NOTE: If you are using Netop’s WebConnect service for communication between Guest and Host, it may not be necessary to configure your firewall because this communication profile is designed to be firewall friendly.  For more information about Netop WebConnect please review the following article.  WebConnect overview including prerequisites and recommendations