Hello everyone!I am seeking to enable a client on the "PC1" with IP address 172.80.10.100 to have the ability to run a client application within a distributed network environment. The client should be able to access the server's HMI files, although without access to the data itself. Although the client application opens successfully on PC1, it is unable to retrieve any data. Conversely, "PC2" with IP address 172.80.10.101 (configured on the same subnet and gateway as PC1) is capable of accessing the data. Both PCs are currently connected to the same server hosting the FactoryTalk Directory, and can communicate with the server hosting the HMI files and Data server via ping requests. The main discrepancy between the two PCs lies in the fact that PC1 cannot ping the PLC directly, while PC2 can. In order to resolve this issue, should I request IT to modify the routing settings to enable PC1 to establish a connection with the PLC? Despite the assumption that PC1 should be able to access the data server given its ability to connect with the directory server and Data server, it seems that PC1 may need to be reconfigured to allow for communication with the PLC.
Rise to the Top: Elevate Your Ranking with These SEO Strategies
Before calling IT, it might be worth checking the firewall settings on PC1. It could be that the firewall is blocking communication with the PLC. If that's not the issue, inspect the network adapter settings to ensure they're set correctly. Lastly, there could be a physical issue with PC1's network connection - try swapping the Ethernet cable and checking the port. If none of these steps help, then it'd be time to get IT to investigate the routing settings.
Definitely, your thought process seems to be in the right direction. If PC1 is unable to ping the PLC directly while PC2 can, then your problem likely lies with the network configuration between PC1 and the PLC, rather than any issue with the client application or the data server. Requesting IT to examine and perhaps modify the routing settings on PC1 might indeed resolve your issue. It may be a case of a simple missing route or incorrect firewall setting between PC1 and the PLC.
Absolutely, it seems like a routing issue given the conditions you've mentioned. Direct communication with the PLC is crucial for the client application to function correctly. Having your IT team modify the routing settings to allow PC1 to ping the PLC directly could potentially resolve the problem. But before doing that, I'd also suggest a simple diagnostic step - try temporarily disabling the firewall on PC1 to make sure it's not blocking the connection. If this doesn't work, you should definitely proceed with reconfiguring the routing settings.
I'd say your hypothesis is on the right track though I'd also suggest a couple more things to verify. Start by taking a closer look into firewall settings on PC1. A strict firewall might prevent ping requests from being transmitted or received. Also, do check the Network Interface Card (NIC) settings on PC1. If the settings or the driver is misconfigured, the NIC might not function as expected. If these don't work, asking IT to revisit routing settings might indeed be necessary. Also, ensure that PC1, the data server, and the PLC are all on the same VLAN, as this could also be a likely culprit. Hope this helps!
It sounds like you've narrowed down the issue pretty well! Since PC1 can't ping the PLC while PC2 can, I'd definitely recommend having IT look at the routing settings for PC1 to ensure it's properly configured to communicate with the PLC. It might also be worth checking any firewall settings or network restrictions specific to PC1 that could be blocking that access. Once PC1 can ping the PLC, it should have the necessary connectivity to retrieve the HMI files correctly. Good luck!
✅ 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: Answer: The issue might be related to PC1's inability to ping the PLC directly, unlike PC2. This discrepancy could be causing the data retrieval problem.
Answer: Answer: The routing settings may need to be modified to enable PC1 to establish a connection with the PLC. This modification could potentially resolve the communication problem.
Answer: Answer: Requesting IT to look into reconfiguring PC1 to allow communication with the PLC might be a solution to ensure data access in the distributed network environment.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.