Contents
- What are the different ports used by Updater during its operations?
- What's the exhaustive list of Updater error displayed in the finder?
- Why NEXThink Updater didn't connect to the Engine?
- What's the frequency of the NEXThink Updater requests ?
- How to configure the Updater in HTTP mode (instead of HTTPs)
- Why the NEXThink Updater connect to the internet?
1. What are the different ports used by Updater during its operations?
NEXThink Updater uses different TCP ports to exchange data with Engine in order to maintain the installed Collectors updated. The following design describes in greater details the TCP ports used by Updater, together with the UDP port used by Collector.
2. What's the exhaustive list of Updater error displayed in the finder?
Here's the list of error with solution provided:
Error Message |
Description |
Solution |
Failed to download MSI |
NEXThink Updater didn't succeeed to download the MSI |
Please check if this computer can access to the file https://<Engine_DNS>:99/downloads/1/collector/x86/signed/NEXThink_Collector.msi or if the firewall port 99 is open. |
Invalid MSI Signature |
NEXThink Updater check the data integrity of the MSI file provided. |
Please check if you can access to the file https://<Engine_DNS>:99/downloads/1/collector/x86/signed/NEXThink_Collector.msi and also if the parameter "Engine DNS" is set (Engine/Parameters) using webconsole. |
MSI error (<number>): <msi_error_description> |
Problem to install the latest version of the MSI. |
Please create a ticket into our support website (http://www.nexthink.com/customer_support.html) with the log. |
Checksum error |
NEXThink Updater verify the checksum of the file. |
Please create a ticket into our support website (http://www.nexthink.com/customer_support.html) with the log. |
3. Why NEXThink Updater didn't connect to the Engine?
Please make sure that the parameter "Engine/Engine DNS name" in the webconsole is set accordingly.
4. What's the frequency of the NEXThink Updater requests ?
The delay between updater requests is 300 minutes by default. This delay can be modified by editing the configuration file of the engine :
<retry_period>300</retry_period>
5. How to configure the Updater in HTTP mode (instead of HTTPs)
Please find the link here.
6. Why the NEXThink Updater connect to the internet?
In HTTPS mode, NEXThink Updater client connect to the internet to check the certificate (using Windows Update).
It is impossible to abort the SSL handshake and forces “insecure” connection.
The only workaround will be to use NEXThink Updater in HTTP mode.