opc.tcp://192.168.1.200:4850, while Factory I/O failed with error 10013. The confirmed cause in this case was the Windows firewall blocking the Factory I/O socket connection.
Identify the Failure Boundary
| Evidence | Engineering conclusion |
|---|---|
| UaExpert connects to the same endpoint | PLCSIM Advanced is serving OPC UA and the endpoint is reachable from at least one client context. |
Factory I/O returns 10013
|
Investigate Windows socket access, firewall rules, and antivirus controls before changing the simulated PLC. |
| Both applications run as administrator | Administrative rights do not prove that firewall policy permits the connection. |
Check OPC UA Security Assumptions
Confirm that the client configuration matches the server's enabled secure-channel policy. The available evidence does not establish whether “No security” was the only configured server policy, so verify the project rather than assuming the policy list from the reported description.
Resolve Windows Socket Error 10013
- Confirm that Factory I/O uses the endpoint
opc.tcp://192.168.1.200:4850. - Check the firewall and antivirus controls on the machine running Factory I/O and TIA Portal. Ensure they allow the required outbound TCP socket connection.
- Retest after applying or enabling the applicable firewall allowance. In the reported case, correcting the firewall state restored the connection.
Do not treat temporarily running the applications as administrator as a firewall test. The incident persisted with both Factory I/O and PLCSIM Advanced running with administrative rights.
Verify the Repair
Connect Factory I/O to the same endpoint that UaExpert successfully used. The repair is verified when Factory I/O establishes the OPC UA session without error 10013. If UaExpert still connects but Factory I/O does not, keep the investigation focused on client-specific socket permissions, firewall handling, antivirus controls, and matching OPC UA security configuration.
FAQ
What causes OPC UA error 10013 with PLCSIM Advanced?
In this incident, error 10013 was caused by the Windows firewall denying the Factory I/O socket connection. Correcting the firewall state restored communication.
Why does UaExpert connect when Factory I/O cannot?
UaExpert 1.5.1 successfully reached opc.tcp://192.168.1.200:4850, showing that the simulated OPC UA server was available to that client. A firewall or antivirus rule can still handle Factory I/O differently.
Does running Factory I/O as administrator bypass error 10013?
No. Both Factory I/O and PLCSIM Advanced were already running as administrator, but the connection remained blocked until the firewall issue was corrected.