On the local primary hub:
1. Check if the local firewall is blocking the connection:
Depending on OS:
- Windows firewall
- iptables is disabled
- SELinux is disabled
2. Use nslookup from the primary hub to determine the IP address of the support site/archive site,
(Do an nslookup on support.nimsoft.com and archive.nimsoft.com)
Check if both support.nimsoft.com and archive.nimsoft.com resolve to their IP addresses using reverse lookup.
- support.nimsoft.com: 126.96.36.199
- archive.nimsoft.com: 188.8.131.52
3. Try to telnet to the support site over port 80:
telnet archive.nimsoft.com 80
telnet support.nimsoft.com 80
To check for a successful connection.
4. Verify login to http://support.nimsoft.com with your credentials.
5. Verify you have the credentials configured in the IM under Tools->Options.
6. If all else fails you can check the connection from the IM session to the Internet Archive using Wireshark. It may also be advisable to have your your network team check at the firewall/router level, proxy's, etc. Also check things like antivirus, local security (zone alarm etc), which may be getting in the way.
7. If nothing seems to be working, uninstall the Infrastructure Manager client and/or local Nimsoft Infrastructure (hub) installation (if this is just a desktop/laptop accessing the primary hub via IM), then reinstall the appropriate version of Infrastructure Manager (IM) for your NMS version and reboot.
When you install IM, the SOAP-runtime-TK3 program is also installed. To FULLY uninstall IM, BOTH programs must be uninstalled from the IM server:
From Control Panel->Programs and Features, UNINSTALL the following 2 programs on the IM client:
1. Nimsoft Infrastructure Manager
Make sure that you delete ALL the files when uninstalling Nimsoft IM. After both are uninstalled, make sure that the C:\Program Files (x86)\Common Files\MSSoap directory and its contents are also removed. If not, then manually remove them.
Then reinstall Nimsoft Infrastructure Manager.
The IM connection issue to the Nimsoft Online Archive should then be resolved and probes can be downloaded from the local archive on the hub via rt-click->download.