Troubleshoot issues with Publisher connections

Typically, issues with connections between components are due to configurations where a required port or route is blocked. You should first check settings for any firewalls and proxies in use and ensure that connections to ports and IP addresses required by AVEVA Insight applications are allowed.

Configuration issues are often found between the Control network to the DMZ and the DMZ to the corporate proxy. Another possible cause could be that a component on the network is using an older version of the AVEVA Insight Publisher which defaults to insufficient encryption. More information can be found in Tech Note TA419.

To isolate a network issue, you can perform network tests using Powershell. The tests outlined in this section address different layers of network communication using the following commands:

• Ping – Tests basic IP routing and name resolution.

• Test-NetConnection – Tests TCP on a specific port.

• Invoke-WebRequest – Tests HTTP to a specific destination and can also be used to test proxy settings.

The following examples reference the network architecture from earlier in this section and detail how to use the above commands to troubleshoot network connectivity.

To test a request to a specific IP address

Use the ping command from the machine hosting AVEVA Insight Publisher to ensure that requests to the upstream machines on the network can be resolved. The following example tests a request to the DMZ Secure Link:

Ping 192.168.2.15

To test a TCP request on a specific port

The Powershell command Test-Netconnection can be used to test whether a specified route and port are accessible. In the following example, this command is executed from the DMZ Secure Link system to test a connection to the corporate proxy:

Test-Netconnection 10.1.1.20 -Port 8888 -InformationLevel "Detailed"

And in this example, the command is executed from the Publisher system to test a connection to the DMZ Secure Link:

Test-Netconnection 192.168.2.15 -Port 8080 -InformationLevel "Detailed"

To test an HTTP request with proxy

The Powershell command Invoke-WebRequest can be used to test HTTP requests and proxy settings.

The following command, executed from the business network or DMZ computer, attempts a connection to http://online.wonderware.com using the corporate proxy:

Invoke-WebRequest -Uri http://online.wonderware.com -Proxy http://10.1.1.20:8888

And in this command executed from the DMZ computer or the control network, a connection to http://online.wonderware.com is attempted using the DMZ Secure Link as the proxy:

Invoke-WebRequest -Uri http://online.wonderware.com -Proxy http:// 192.168.2.15:8080

The above tests can be repeated for HTTPS connections by updating the target URL with HTTPS, as seen in the following example:

Invoke-WebRequest -Uri https://online.wonderware.com -Proxy http://10.1.1.20:8888

Another test can be performed with Invoke-WebRequest to test a connection using the default proxy settings configured under Internet Options in Windows, as seen in the following example:

Invoke-WebRequest -Uri https://online.wonderware.com

To test DMZ Secure Link Website Access

Finally, you can use Invoke-WebRequest to verify whether DMZ Secure Link is blocking access to sites, as seen in the following example:

Invoke-WebRequest -Uri http://online.wonderware.com -Proxy http://10.1.1.20:8888