DNS2Go and RemotelyAnywhere (v3.5)

1. If you haven't done so already, please download RemotelyAnywhere.
2. Install RemotelyAnywhere following each step carefully.
3. At the 'Software Options' page, note the HTTP port RA will operate on (default: 2000).
4. Once RA has been installed successfully, you can reach your computer through one of the following methods:

   Locally - on the same machine RA resides

   • http://127.0.0.1:2000
   • http://localhost:2000

   Local Area Network - same subnet

   • http://192.168.1.110:2000 (statically assigned private IP)
   • http://RAcomputer:2000 (NetBIOS name)

   Remotely - detached from LAN; physically separate location

   • http://ISP_assigned_IP:2000 (could change dynamically)
   • http://uniquename.dns2go.com:2000 (static name for any IP)

   For this example, let's assume you are at a separate location.

   Note: To make a successful connection, ensure that the RA computer has an active Internet connection, and the DNS2Go client is connected. If you have DNS2Go online with your broadband connection, this should not be an issue. If you use DNS2Go with a dial-up analog modem, scheduling can be established to allow access at specified times throughout the day.

    

5. Logon to your RA site by opening any standard Internet browser, and entering your DNS2Go domain followed by the HTTP port specified when you installed RA.
6. DNS2Go resolves your IP address, and connects you directly to the RA login screen.
7. Enter the User Name/Password established at installation, and select 'Login' to enter the RA interface. From here, you can access all the great functions RA provides.
8. If you need to modify your HTTP port assignment (possibly due to port conflicts), select 'Configuration' from the left pane and then the 'Connections' option.
9. Change your HTTP port assignment in the appropriate location, and restart RA for these changes to take effect.

   For more information, or support on the RemotelyAnywhere product, please refer to the product Website.

   * If RA is installed on a machine behind a firewall router/proxy server, you must establish port mappings to allow access from outside your network. Please refer to your firewall router/proxy server documentation for more information.