Troubleshooting Systemhound Client Connectivity
From systemhoundwiki
The following steps will guide you through some steps to identify some of the more common issues relating to the systemhound client not being listed at all within the reporting website.
On the client machine (that is not reporting)...
- Confirm that 'systemhound client' is installed by checking for either an entry within 'add remove programs' or the presence of the folder c:\program files\systemhound
- Confirm that the systemhound service is running - check that the windows service 'systemhound scheduler' is installed and running via control panel->services
- Using regedit confirm the name of the systemhound central server that the client is attempting to connect to. The server name is held under [HKEY_LOCAL_MACHINE\SOFTWARE\systemhound] within the database_server field
- From a DOS Prompt attempt to ping the central server name located within the registry. If this doesn't work investigate whether you have the correct server name and the network/firewall
- Confirm that port 4004 is not blocked between the client machine and the central server - systemhound uses this TCP/IP port to transfer data. Telnet to the server on port 4004 to confirm the network port is not blocked.
- If that works try running shrefresh from a DOS prompt - everything should work as expected
- Confirm that there are files present within c:\program files\systemhound\plugins if you have more than 5 files with recent time stamps the machine has contact the server ok and should appear within the database shortly.
