EROE Web Server is Not Reachable Over WAN Network – SCADAPack 474i Routing Table configuration

Symptoms seen: Can't connect to EROE webserver from outside local RTU subnet.

EROE Web server not connecting:

Example Network Topology:

Local Connection:

Even though the EROE Web Server PC and the remote device could communicate locally, see Local Connection, remote access failed because the SCADAPack 474i routing table was not configured to return traffic back to the PC network (10.10.10.0/24) as seen in the Example Network Topology.

This caused one‑way communication, which is why:

• The EROE Web Server PC (10.10.10.224) could send packets toward the remote network (192.168.1.x).
• But the SCADAPack 474i or End Device had no route telling it how to return packets back to the 10.10.10.x network.
• As a result, the web server appeared reachable locally but never responded to network clients, making the web interface inaccessible from the remote side.

Resolution

• Add a NETWORK route in the SCADAPack 474i routing table.
• In RemoteConnect, Configuration → IP Communication → Routing Table
• Add IP Route.

After adding this route, the SCADAPack will know how to return traffic to the PC, and the EROE Web Server will be fully accessible across the network.

For additional information, you can connect to the SCADAPack 474i RTU using Telnet and run the command route print to review the routing configuration on the device. Verify the Edge routing entries to confirm that the required networks and gateway paths are correctly defined.

/user>route print

Interface List:

10: ETHERNET 1 IP Address: 192.168.1.110/27

11: ETHERNET 2 IP Address: 172.16.1.200/24

EDGE(ETH3) IP Address: 172.16.1.201/24

EDGE(ETH4) IP Address: 0.0.0.0

13: USB        IP Address: 10.2.3.4/29

RTU Routes:

Type     Destination-IP   Net-mask          Gateway-IP       Interface   Metric

DFLT-GW  0.0.0.0          0.0.0.0           192.168.1.97     10          0

NETWORK  10.2.3.0         255.255.255.248   10.2.3.4         13          0

HOST     10.2.3.4         255.255.255.255   10.2.3.4         13          0

GATEWAY  10.10.10.0       255.255.255.0     172.20.30.97     10          1

HOST     127.0.0.1        255.255.255.255   127.0.0.1         0          0

NETWORK  169.254.254.248  255.255.255.248   169.254.254.249  11          0

HOST     169.254.254.249  255.255.255.255   169.254.254.249  11          0

NETWORK  172.16.1.0       255.255.255.0     172.16.1.200     11          0

HOST     172.16.1.200     255.255.255.255   172.16.1.200     11          0

NETWORK  192.168.1.96     255.255.255.224   192.168.1.110    10          0

HOST     192.168.1.110    255.255.255.255   192.168.1.110    10          0

Route Priority: HOST NETWORK GATEWAY DEFAULT-GW

Edge Routes:

Type     Destination-IP   Net-mask          Gateway-IP       Interface

DFLT-GW  0.0.0.0          0.0.0.0           172.16.1.1       ETH3

NETWORK  10.2.3.0         255.255.255.248   169.254.254.249  EDGE

NETWORK  192.168.1.96     255.255.255.224   169.254.254.249  EDGE

NETWORK  10.10.10.0       255.255.255.0     169.254.254.249  EDGE

RTU NAT Redirections:

Destination-IP   Port   Redirect-IP      Port  Protocol

10.2.3.4         22     169.254.254.250  22    tcp

10.2.3.4         443    169.254.254.250  443   tcp

10.2.3.4         4323   169.254.254.250  4323  tcp

192.168.1.110    22     169.254.254.250  22    tcp

192.168.1.110    443    169.254.254.250  443   tcp

192.168.1.110    4323   169.254.254.250  4323  tcp

172.16.1.200     22     169.254.254.250  22    tcp

172.16.1.200     443    169.254.254.250  443   tcp

172.16.1.200     4323   169.254.254.250  4323  tcp

Publié pour: Schneider Electric Belgium