Any Port in a Storm?...
mk42 said:
I can't speak for RSLinx specifically...
I can...
Bullzi said:
I figured it wasn't the most secure system but that is what they use.
How to set up my RSLinx so I can communicate with my PLC that is on that network?
Hi,
"If" I'm reading "that" network's setup correctly...
RSLinx Classic specifically requires port 2222 TCP and port 44818 UDP Port Forwarding to be configured to the Private IP address of the controller. This would need to be configured through all routing appliances on the network. If there is only a single destination modem/router path to the controller then it would just need Port Forwarding configured for the above ports.
The controller's Gateway address should be set to the Private IP address of the router appliance that the controller is directly connected to. Again, a modem/router could simply be the next hop back for the controller. In this case, the Private IP address of the modem/router is used as the controller's Gateway address.
You then need to know how to remotely connect to their "modem" appliance. They should have configured this already.
Example: Using Web Browser, type in address: 74.22.168.14:2850
Then login credentials, and you are now connected to the modem appliance. This should give you access through the modem/router, or several routers, to reach the nodes on the network.
Once connected, you can try to PING the Private IP address of the controller. This will confirm that the routing is configured correctly and the controller is now reachable.
In RSLinx Classic, the "EtherNet/IP Driver" will usually not work as most network switches/routers will be configured to block "Broadcast" and/or "Multicast" traffic. Instead, you can try the "Ethernet Devices" driver, as it uses Unicast and Explicit IP targeting. For the driver, set the Private IP address of the controller and then attempt to browse the driver for the controller. "If" there was NAT being used (Network Address Translation), it is possible the Private IP address of the controller has been translated to a Public IP address. "If" this were the case, then you would use this Public IP address for the "Ethernet devices" driver.
Alternatively, in RSLinx Classic there is also the "Remote Devices via Linx Gateway" TCP driver. Using this driver you would configure the "Server's IP address or hostname" as the Public IP address of the router before the controller. Then browse this driver and the controller may respond active.
That's "loosely" the norm. We'd really need to know the full architecture of the network and the path to the particular controller you would like to reach. The architecture of the controller might also be useful to know - Logix 500/5000? For instance, you could be remotely connecting to their network via ADSL and then routed to a wireless modem appliance which then polls the radios modems wirelessly at each controller. Here you are not remoting in directly to a "modem" and instead it would be the ADSL router's Public IP address you would use to configure the "Ethernet devices" driver, and so on.
I would also agree that a VPN is a must really when opening up your IACS to the Wretched Wild Web.
Regards,
George