I am encountering a unique issue with my FT Batch software where my data server is unable to connect to my PLC across a network. After consulting with Rockwell, it appears that the problem may stem from my computer running the batch server on a different subnet than the PLC. Currently, the PLC is being accessed by tunneling through one CLX chassis via EN2T to another EN2T in that chassis on a different subnet. The computer running the data server can ping the 192.97 subnet but cannot reach the 192.168 subnet. It seems that FT Batch may not support tunneling across a network via Linx like other PLC applications do. Rockwell's suggestion was to move the PLC to the same subnet as the computer hosting the batch server, but this would require moving it to the main plant network, which I would like to avoid due to limited IPs. I am open to further questions or recommendations.
Consider utilizing a router, such as the Hirschmann Eagle, to effectively connect two subnets. This router features two ports, each specifically addressing the separate subnets. By configuring a 1:1 NAT setup, seamless connectivity can be established. Alternatively, you can opt to incorporate a second NIC into your server to position it within the 192.168.x.x subnet. This method offers flexibility and enhanced network performance.
The user imtiredboss suggested using a router like the Hirschmann Eagle to connect two subnets. This router has 2 ports, each assigned to a different subnet, allowing for configuration of 1:1 NAT for connection. Another option is to add a second NIC to the server and place it on the 192.168.x.x subnet. However, this may still require tunneling across racks or moving the PLC to the 192.97 subnet, which the user is hoping to avoid if possible.
In a conversation, MichaelQSI mentioned the need to connect devices on different subnets without tunneling or moving equipment. One possible solution is to add a second NIC card to the computer, allowing it to communicate with the PLC on a different subnet. While there may be other alternatives available, this is a cost-effective approach to achieving connectivity between devices on separate subnets.
imtiredboss suggested that using a second NIC card on the computer in a different subnet is the most convenient and cost-effective way to enable communication with the PLC. While there may be other options available, this method is recommended if bringing all devices onto the same subnet is not feasible. No need for tunneling through the rack. Another potential solution could be using a router with 1:1 NAT, although this might not be suitable for a virtual machine being accessed remotely. Thank you for the suggestion.
One alternative is to install an additional ethernet module in the rack and configure it to be on the same subnet as the server attempting to communicate with it. This option may be pricey unless you already have a spare module on hand.
Interesting issue you're experiencing. I do agree with Rockwell's suggestion - problems like yours often arise due to devices being on different subnets. However, I understand your constraints too. As a workaround, have you considered using a VPN? This could trick your software into believing that the PLC and the data server are on the same network. Alternatively, setting up a NAT (Network Address Translation) should allow your computer to reach the 192.168 subnet. This could resolve the issue without needing to move your PLC to the main plant network. It might take a bit of tinkering, but it's certainly worth exploring.
It sounds like a tricky situation you're in. I also had a similar issue with FT Batch and what I found helpful was adding a static route to my batch server. This allowed it to access the other subnet and communicate with the PLC. It's worth mentioning you might need to involve your IT department, though, because static routes can affect network security. This way you could avoid moving your PLC to the main plant network, and not worry about the limited IPs. Just a thought.
This does sound like a complex networking issue. Sometimes Rockwell's solutions may not be the best fit in certain situations, especially in your case where shifting to the main plant network isn't ideal. I've encountered similar networking roadblocks with Rockwell's automation software before. You might want to consider setting up a NAT (Network Address Translation) configuration on your router, it can create a gateway for your server to access the other subnet while maintaining separate networks. This can be a solution provided your IT architecture supports it. Always be aware of potential security implications when making such changes. Worst case scenario, if no other options are feasible, you may have to take Rockwell's advice or look into expanding your IP address range to accommodate the PLC on the main plant network.
That's an interesting dilemma you've got there. Typically, as Rockwell suggested, having both the PLC and the host computer on the same subnet is the most straightforward path. However, understanding your concerns about shifting to the main plant network, you may look into using a router to connect the subnets or possibly get a dedicated IP for PLC from your IT department. An additional thought - have you considered setting up a VLAN? It might help segregating your network traffic while keeping your PLC and host computer within the same logical network. It might be another avenue to investigate. A networking expert should be able to guide you better on this.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: The issue may arise from the computer running the batch server being on a different subnet than the PLC. FactoryTalk Batch may not support tunneling across networks via Linx like some other PLC applications do.
Answer: Rockwell recommended moving the PLC to the same subnet as the computer hosting the batch server to establish a successful connection.
Answer: This limitation could be due to network configuration issues that prevent communication between different subnets.
Answer: Moving the PLC to the main plant network may resolve the connectivity issue but could lead to limited IP address availability concerns.
Answer: Exploring alternative networking configurations or solutions that enable communication between different subnets without moving the PLC may be viable options to consider.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.