Setting up a server to run on the same local network the instrument is in is relatively easy. In addition to the steps above, one should make sure of the following:
| • | If the server is contacted by its IP address, the IP address of the PC working as a server must be fixed. To that end, the router that the PC is connected to must be set to use “Static DHCP” for that PC. This way the IP address will not change over time. |
| • | The PC working as a server must be always on, and must be running the Instrument_Listener. Otherwise the connection can’t be established when the instrument tries to connect. |
Setting up a server to work in a Wide Area Network (in a different city for instance) is a little more complicated. One option is to use a corporate server running the Instrument_Listener. In that case it usually makes sense to use a domain name to represent the server’s address.
When the server is a simple PC in an office, the following configuration may be used:
| • | The router that the PC is connected to is configured for “Port Forwarding”. Port Forwarding must be enabled on port 50 000, for TCP/IP, to the local IP address of the PC. |
| • | Static DHCP must be configured on that PC, so its local IP address will not change. |
| • | Ideally the router must be setup to use a DDNS service, such as noip.com. This way the instrument can use a domain name registered through the DDNS service in order to contact the server. Alternately the instrument’s server setup can use the WAN IP address of the router that the server is connected to. That is a less optimal solution because that WAN IP address is often subject to change by the internet provider, and when it changes the instrument won’t be able to connect to the server anymore. |
