Clients Not Communicating

[hackenbow]

I'm having problems with a bunch of XP clients not reporting back to the server.  In the install wizard, they have green icons.  The service is running.  The files are present under program files.  The upload.log file contains the following lines:

Routine : client_send_file C:\Program Files\systemhound\logs\upload.dat
         File C:\Program Files\systemhound\logs\upload.dat is not accessible!

On the server, the collector.log had a message that I think said "client failed."  (I rebooted the server, and the file has been wiped.)

The network and routers are fine, these machines are all connected via a T-1, and use Outlook, IE, Citrix, telnet, and other applications that are hosted here.

I'm running 3.1T.

I'm desperate for assistance.  We're doing a company-wide audit, and our director is after me every couple of hours, as he has an intern dedicated to the audit.

These machines were cloned with Ghost, but I've uninstalled systemhound and re-installed, or just re-installed it multiple times.  I read something in another thread about the registry settings for machine_id and machine_id2, but I can't find the thread anymore.

Please HELP!

[hackenbow]

More Information:

In reviewing HKLM\software\systemhound, I find that 3 machines have identical values for machine_id and also have identical values for machine_id2.

As I said, I can't find the thread referencing those values, but possibly this information will help.

[hackenbow]

I now have data (it's the next day) from the collector.log on the server:

Session failed!
Session failed!

[Nish]

Hi Hackenbow,

thanks for the info on machine_id and _id2

This indicates you've got at least three machines which, to systemhound, are identical. So what is happening is that they keep overwriting each other on the reports.

First thing you need to do is get unique id's on those machines. Go to two of the three machines and delete the two id's from the registry. Now re-install the clients using the install tool and you'll find they have now been assigned unique id's. They should also report back to the server, so check the reports shortly after re-installation.

Check all your machines that have apparently not been reporting - if they have duplicate id's, carry out the above procedure and you should find you're back to normal. About collector.log - not sure what the session failed messages are indicating, but try the above first.