If you are having problems connecting to a Fernhill SCADA Server, follow these steps to find the cause of the problem:
On Windows, the Fernhill SCADA Server runs as a Windows Service. To check the Fernhill SCADA Server is running:
Note: If Status is not showing Started, open the service Properties and try to start the service. For more information, see Managing the SCADA Server.
On Linux, the Fernhill SCADA Server runs as a systemd service. To check the Fernhill SCADA Server is running:
systemctl status fernhill-scada
The output should be similar to:
โ fernhill-scada.service - Fernhill SCADA Server for Unix Loaded: loaded (/lib/systemd/system/fernhill-scada.service; enabled; vendor preset: ... Active: active (running) since Tue 2018-08-28 14:48:15 BST; 2min 43s ago Process: 363 ExecStart=/usr/bin/fernhill-scada --pidfile /var/run/fernhill-scada.pid ... Main PID: 404 (fernhill-scada) Tasks: 10 (limit: 4915) CGroup: /system.slice/fernhill-scada.service โโ404 /usr/bin/fernhill-scada --pidfile /var/run/fernhill-scada.pid --daemon
Note: If the Active: does not show running, try and start the service. For more information, see Managing the SCADA Server.
By default, the Fernhill SCADA Server accepts connections on TCP port 20295. Note: The TCP Port used by Fernhill SCADA can be changed using Server Parameters.
To check the Fernhill SCADA Server is listening on the correct ports on a Windows Computer:
netstat -naob -p TCP
Note: If another program is listening on either of the ports there is a port conflict. Try to change the configuration the other program to remove the port conflict.
To check the Fernhill SCADA Server is listening on the correct ports on a Linux computer:
sudo lsof -i -P -n | grep LISTEN
su root
lsof -i -P -n | grep LISTEN
fernhill- 404 root 24u IPv4 13757 0t0 TCP *:20295 (LISTEN) fernhill- 404 root 25u IPv6 13758 0t0 TCP *:20295 (LISTEN)
Note: If another program is listening on either of the ports there is a port conflict. Try to change the configuration the other program to remove the port conflict.
The Fernhill SCADA setup program automatically adds rules to the Windows Firewall to grant network access to the Fernhill SCADA Server. It is possible another user or program has modified, or removed, these rules which prevents programs connecting to the Fernhill SCADA Server.
To check the Windows Firewall Rules:
Note: If firewall rules are missing try to rerun the setup program in repair mode to reinstate the firewall rules.
It is possible another firewall product is blocking access. For example:
Configure any additional firewalls to accept connections on TCP Port 20295.
Run the operator interface on the computer running the Fernhill SCADA Server. This will the whether local connections are possible:
Submit a bug report if you still cannot connect locally and all of the following are true:
Submit a bug report to support@fernhillsoftware.com. Try and include the server log file for the connection attempt.
You can run a ping test to check the network connection between two computers. A successful ping test will show you have a working network connection between two computers. A failed ping tests does not mean the network connection is not working. A ping test can fail because firewall rules are blocking ICMP Echo requests.
To run a ping test
ping Address
Where Address is the IP address of the computer running the Fernhill SCADA Server.
If the ping test succeeds you will see output like:
Pinging 192.168.1.218 with 32 bytes of data: Reply from 192.168.1.218: bytes=32 time<1ms TTL=128 Reply from 192.168.1.218: bytes=32 time<1ms TTL=128 Reply from 192.168.1.218: bytes=32 time<1ms TTL=128 Reply from 192.168.1.218: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.1.218: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
If the ping test fails you will see output like:
Pinging 192.168.1.218 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.1.218: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
If the ping test fails check the Windows Firewall on the computer running the Fernhill SCADA Server allows ICMP Echo Requests. The Microsoft Technet article Nobody Can Ping My Computer provides details how to do this.
To more information about the Operator Interface.
To learn about the Fernhill SCADA Server.
For the meaning of terms used in Fernhill SCADA.