Slave Connection over the Internet

Top  Previous  Next

A Client Slave can also connect over a fast internet connection.  For this to work effectively you first need to obtain a fixed IP address from your ISP for the Client Master PC.  We cannot guarantee that this will work as it is extremely dependant on the speed of upload and download of both the server and slave PC.


For example, if you have the Client Master PC connected to the internet via a router at your work site, then you will need to obtain a fixed IP address for the work site.  Once you've done this, you will need to set the router at the work site to forward all data requests on port 19001 to the Client Master.  This is ordinarily called port forwarding and a google search should find instructions on how to set this up on your particular router.


Now you need to tell Onyx's database server that it is to accept secure connections from the internet on port 19001.  This can be done by starting the Database Server Admin Control Panel on the CLIENT MASTER PC and enabling 'Secure TCP' and setting a SECURE keyprase  (both topics covered here).


Once the Database Server has been set to accept incoming connections, you can test that it is working by going to and entering 19001 in the 'Port' field and then pressing 'Check Port'.  If you see anything other than 'Success' then you need to review your port forwarding settings in your router, or your firewall settings to ensure that 'OGDBServer.exe' is not blocked and that port 19001 is not blocked.


Once you see 'Success' on then you can now add the relevant settings into the Client Slave.  You do this by selecting the last option as shown below (this will be shown when you first start Onyx but can be accessed via Maintenance->Select Server):




Press 'Next' and you will see:




You should now enter the static IP address provided by your ISP, then enter the Connection Password (the Secure Keyphrase set in the server control panel) and then press 'Test Connection'


Compression should be started at 5 and adjusted to give the best performance (higher compression creates more work for the server but goes some way to compensate for slow internet connections).  The other setting (shown as 512), is the size in kb that a data request has to exceed before compression is applied.