Hello.

There is some profound misunderstanding about what our Launcher application does. It has nothing to do with doing the actual OPC communications. It is, in fact, a replacement for faulty Windows Start menu. It only exists to allow users to easily navigate to various part of the product, while developing or building. It has zero role in/for runtime

You should remove the OPC Studio Launcher from your block diagram. Then you get an architecture that can work.

As to the rules on Firewall O2:
- If you are using OPC UA, you need to allow outgoing communication to the address/port of the OPC UA server. Default port is TCP 4840, but that is most commonly used by embedded devices (PLCs). PC-based servers frequently use different ports.
- If you are using OPC Classic, then, frankly, your are (almost) doomed. You will need to open wide range of ports, both incoming and outgoing. This is because OPC Classic is based on DCOM which is then based on RPC. Let me know if this is your case and I can then give some more info.

Best regards

Hello, Support Team.

I am developing an application in python that will write and read OPC tags values. This same application will have interface with the corporate network, and for that reason, I need this VM to run in a DMZ Layer, where all communications with the corporate network will respect a Firewall 01 rule.

Other point is that I can not install OPC Labs Launcher at the same server as my OPC, so I am planning to dedicate a VM only to run the OPC Labs software. This VM will be located at the same network level as the OPC Server, this way I think I won't have problems to map my OPC Server in the OPC Lab Launcher.

Architecture drawing is attached.

My doubt is, Is it possible to write and read data from my python application with the OPC Labs running in another VM? If yes, what protocol and ports should I allow in my firewall 02?

Thanks in advance!