When attempting to connect to GSX Monitor via the Remote User Interface (UI), a connection is constantly pending, informing you that the interface will restart. This is commonly caused by a misconfiguration of the TCP ports utilized for connecting.
Follow this article to verify Remote User Interface configuration settings and test TCP connectivity for a successful connection.
- This program has to be launched by another executable and will close.
- GSX Monitor's interface will restart in: xx seconds.
How to Solve the Issue
Verify that the default ports 33333 and 33340 are bidirectionally available on both the monitoring station and the GSX Monitor Remote UI station.
A bidirectional port means that the port is open to send and receive information.
Verify that the version of GSX Monitor and GSX Monitor Remote User Interface matches:
- From GSX Monitor, select Help > About GSX Monitor.
- Notate the Build number.
- For the GSX Monitor Remote UI, right-click the executable link.
- Select Open file location.
- Right-click the highlighted GSXMonitorRemote.exe file.
- Select Properties > Details.
- Locate Product version and verify this matches the GSX Monitor Build number.
- If they do not match, update either GSX Monitor or the Remote UI.
Verify that the default port 3333 is set in GSX Monitor:
- Launch GSX Monitor.
- Select Preferences > Globals > Advanced.
- In the Connection section, verify 33333 is set.
Verify that the default settings are correct in GSX Monitor Remote UI:
- Launch GSX Monitor Remote UI.
- Verify the IP address or hostname is correct for the GSX Monitor address.
- Verify 33333 is set in GSX Monitor port.
- Verify 33340 is set in GSX Remote UI port.
Verify TCP port connectivity succeeds:
Run the following PowerShell command to test TCP port connectivity on the Remote UI and monitoring stations providing diagnostic connection information:
- Test-NetConnection -ComputerName MonitoringComputerName -Port 33333
- Test-NetConnection -ComputerName RemoteUIComputerName -Port 33340