Procedure to check if ports are open on IT network for GTXL

[Pages:2]Procedure to check if ports are open on IT network for GTXL In the event that you run your Gaugetools XL software and the automatic network discovery does not find your gauges automatically you have the option of using remote devices to set-up a direct IP address connection from GTXL to the gauge. However typically the cause for this not working is that the UDP broadcasts are blocked by the routers and so you need to connect via IP address When this happens the most likely cause is IT restrictions on the network. For security reasons many IT setups restrict which IP ports are opened. For NDC's GaugeToolsXL software to connect to the gauges we need to be able to access port 25011 You can fairly simply test to check this. Open a web browser on the PC running GaugeToolsXL and then in the URL type in the IP address of one of the gauges you can ping e.g. in Chrome something like this

This will attempt to connect to the web server on port 80.

Typically these ports are left open so do not normally have the same IT restrictions applied. If the web page loads and you see the measurements page from the gauge but are not discovering the devices through GTXL, then the issue must be a port issue. To verify this you can go through the below procedure. Open PowerShell on the computer running GaugeToolsXL - You can search for PowerShell using the magnifying glass on the Windows bar as shown below

NDC Technologies Ltd. Bates Road, Maldon, Essex, CM9 5FA, United Kingdom

T: +44 1621 852 244 F: +44 1621 856 180 helpdesk@

Intelligence that transforms the world.

- Unrestricted Information -

Registered in England and Wales, No 00630998



Addressee September 17, 2021 Page 2

For the example here we are testing the gauge which has IP address 10.32.15.169

Then type in the following commands to test 10.32.15.169 Test-NetConnection 10.32.15.169 Test-NetConnection 10.32.15.169 -Port 25011

If port 25011 is not open you will get a good response for the first command and a bad response for the second.

Below is what you see when you test this where the port 25011 is open.

There is a 3rd command as well Test-NetConnection 10.32.15.169 -Port 19999 where we know this is not a valid port and you can see the response that comes back as a failure. If on your PC port 25011 is not open you would expect to see this response

Ports can be opened on PC's through firewall defender ? typically this would be done from IT and should be discussed with your IT administrator

- Unrestricted Information -



 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download