Before heading down the wrong path, I want to gather input from others on a project I'm working on. The individual who previously handled these setups has retired, and I lack expertise in networking. Any suggestions or ideas would be greatly appreciated. Thank you, Dave.
1. Optimal practice dictates that PLCs should be kept separate from the corporate network to ensure security. 2. Engage with the IT department. Connecting multiple PLCs to the corporate network without proper authorization can lead to issues. 3. PLCs are not compatible with the high communication demands of a corporate LAN. 4. Connecting PLCs to a corporate network is not recommended. If you need secure routing for remote devices within the OT segment, specialized hardware and knowledge are essential.
The described scenario aligns perfectly with the purpose of NAT appliances. Investing in a NAT appliance priced between $700 - $1000 per network, complete with a 24V power supply and DIN rail mounting, is a reasonable choice. For those with limited funds but networking skills, utilizing a $40 travel router with OpenWRT can achieve similar NAT functionality. Alternatively, opting for a more professional solution involves purchasing a case of Ubiquiti Edgerouter X units and deploying one at each location. For those looking to minimize remote user networking headaches, enabling routing in the Windows 10 Registry Editor and opening TCP Port 44818 in the firewall while teaching users to create static routes via the command line may be a suitable approach. Alternatively, for a more adventurous option, consider installing software NAT on Windows PCs.
The sounds of frustrated SecOps professionals grinding their teeth can be heard echoing in the office.
In my office, I have a dedicated "PLC lab" equipped with a variety of controllers, HMIs, servos, and computers. To ensure seamless connectivity to both local network resources and internet services, I utilize an old mini server computer running OpenWRT, a Linux-based routing software. Despite being designed for WiFi access, this server effectively functions as a wired two-port router and firewall in my setup. This setup allows me to isolate my automation devices and traffic from the corporate LAN. When my IT department detected unauthorized traffic (specifically from DropBox), they struggled to identify my router on the corporate network. Due to its unresponsiveness to PING requests, non-standard TCP ports usage, and randomized MAC address, it appeared suspicious and raised security concerns. However, they eventually located its IP address and secured it, avoiding the need for a thorough physical inspection of the premises. To avoid involving IT in such matters in the future, I prefer using a user-friendly device for self-administration. Devices like A-B, Moxa, Phoenix Contact, and Red Lion routers are suitable options, along with Ubiquiti EdgeRouters and OpenWRT boxes. For instance, the EdgeRouter X, priced at sixty dollars, offers a cost-effective solution with minimal risks of preinstalled malware.
TheWaterboy recommended keeping Programmable Logic Controllers (PLCs) off the corporate network to adhere to best practices. It is crucial to involve IT in the process to prevent any issues that may arise from connecting PLCs to a corporate network. PLCs are not designed to function efficiently on a busy corporate LAN, so it is advisable to keep them isolated within the Operational Technology (OT) segment. For secure routing to remote devices, specialized hardware and expertise are required. Instead of the IT network, the appropriate term would be the SCADA network, which must be completely isolated from the main office IT. Additionally, implementing VLAN separations can further enhance network security.
Hi Dave, absolutely agree it's critical to gather input before making big decisions. As far as networking goes, I'd suggest starting with some basic online tutorials or courses. Websites like Coursera and Udemy offer affordable courses that cover the basics of networking. Once you have a good foundation, you can move onto advanced topics. Also, don't hesitate to reach out to professionals in your network or on LinkedIn for advice. There's always someone willing to help. Best of luck with your project!
Hey Dave, it's great that you're seeking input before diving into your project! One idea might be to start with a simple network diagram to map out what you need, which can clarify any potential issues. Also, consider reaching out to online communities or local meetups focused on networking—there are plenty of knowledgeable folks who might be willing to share their experiences. Good luck, and don’t hesitate to ask specific questions as you progress!
Hey Dave! It sounds like you’re in a bit of a tricky spot, but there’s definitely a way forward. Have you considered reaching out to online networking communities or forums? They can be a treasure trove of information and insights, especially if you outline what you’re trying to achieve. Additionally, if you can connect with a local networking group or even a few tech-savvy friends, they might provide valuable hands-on support. Good luck with your project!
✅ 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: 1. How can I connect Allen Bradley PLCs to a corporate network without using RS-Linx Gateway? - One way to achieve this is by using a device such as a Stratix switch or an industrial router to establish the connection. It is important to ensure that the necessary network configurations and security measures are in place.
Answer: - Other options include using OPC (OLE for Process Control) servers, industrial VPN solutions, or implementing a secure tunneling protocol like MQTT (Message Queuing Telemetry Transport) to facilitate communication between the PLCs and the corporate network.
Answer: - To enhance security, it is recommended to implement measures such as network segmentation, firewall rules, VPN encryption, strong authentication mechanisms, regular software updates, and monitoring for any unusual network activities.
Answer: - Factors to consider include network compatibility, data transmission requirements, network latency, potential cybersecurity threats, compliance with industry regulations, and the scalability of the solution for future expansion or upgrades.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.