Non Existent Machine showing up in Landesk Resident Agent.log file
Posted on 2004-04-09
We run Landesk Version 8.01 for network/system management and remote control and I have a machine name that keeps popping up on the client machines in the ResidentAgent.Log file......
here is an excerpt of the file:
Fri, 09 Apr 2004 08:03:24 Windows Platform 2, version 5.2
Fri, 09 Apr 2004 08:03:39 Could not start ctrl dispatcher
Fri, 09 Apr 2004 08:06:51 Entering ServiceHostThreadProc, thread id 2160
Fri, 09 Apr 2004 08:06:51 Handling request from clyw2k3.hnmc.hnm.tenethealth.com:1082
Fri, 09 Apr 2004 08:06:51 Started process 2112 to handle request
Fri, 09 Apr 2004 08:07:01 Socket error 0 was classified as non recoverable
Fri, 09 Apr 2004 08:07:01 Socket 368 closed gracefully
Fri, 09 Apr 2004 08:07:01 Socket closed, client has disconnected
Fri, 09 Apr 2004 08:07:01 Request handling complete
Fri, 09 Apr 2004 08:07:01 Exiting ServiceHostThreadProc, previous sem count: 4
The machinename above does not exist. It was renamed to something different almost 2 months ago. It was a windows 2003 server machine that we used to test landesk.....But the actual rollout was done on a clean server with nothing on it except landesk and sql server. However, most if not all our clients have a reference to this old non existent machine in the ResidentAgent.Log file. I believe this is the reason we are having so many remote control issues like:
CANNOT FIND AGENT or CANNOT CREATE SECURE SESSION WITH CLIENT etc...
We have about 950 clients, of which all but 144 have the correct certificate file installed. All have CBA, Remote and Inventory.
We have checked both of our DNS servers for the machine name...and did not find it, and we also checked WINS for good measure. It ain't there. Also we do not use Hosts or LMHosts files for anything. What could be causing this.