UaGateway  1.3.4.261
 All Pages
Windows Firewall Configuration

The setup procedure is modifying security settings on your computer. After a successful setup the UaGateway will be included in the exception list of the Firewall. To use computer’s name instead of the IP address for connecting to UaGateway, the Network Discovery must be enabled in the Firewall.

The setup adds following entries in the exception list of your Firewall:

  • DCOM-Port: Port 135 for TCP
  • UaGateway-Port: 4850 for TCP
  • OPC Enum: %SYSTEM%\opcenum.exe
  • UaGateway: %PROGRAMFILES%\UnifiedAutomation\uagateway\bin\uagateway.exe

Windows Security Alert

Problem:

When starting the UaGateway the first time the Firewall may ask you to unblock the application.

Solution:

Press the “Unblock” button to add the UaGateway application to the Windows Firewall and to enable it's entry in the exception list.

BadHostUnknown

Problem:

When connecting with a remote UA Client (e.g. UaExpert) and getting error BadHostUnknown (0x81060000), the server’s machine name could not be resolved.

Solution:

Include the “Network Discovery” in the exception list of the Windows Firewall on the Server machine.

BadTimeout

Problem:

When connecting with a remote UA Client (e.g. UaExpert) and getting error BadTimeout (0x800A0000) the server could not be reached because the Firewall blocks the incoming call.

Solution:

Include “UaGateway.exe” in the exception list of the Windows Firewall on the Server machine.