• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 743
  • Last Modified:

Non Existent Machine showing up in Landesk Resident Agent.log file

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:


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.


  • 2
1 Solution
I had a similar problem with a workstation some time ago. I honestly can't remember the specifics, but I think we were getting strange errors in the event log on some of our servers referring to a machine that didn't exist. We eventually found the machine (a Win2K laptop) that had a different host name, but was using the offending name for certain operations on the network. We disjoined the machine from the domain, renamed it again and then rejoined it to the domain and I don't believe we've had a problem since. If I remember correctly, the machine in question was improperly imaged or something like that because I think the "other name" it was using was our image name.

Now I'll admit I'm not remotely famailar with Landesk, but if you're getting "Handling request from clyw2k3.hnmc.hnm.tenethealth.com:1082", that would indicate to me that there is a machine on your network that is currently operating with the name of "clyw2k3". My first step would be to try pinging that name which probably won't return anything since you've already checked DNS. Maybe check the DNS (ipconfig /displaydns) on a client machine with the above log entry and if it has an entry, then flush the DNS on that machine. We use a 802.1q VLAN management application and I think that is how we found our offending machine. Either way, in my opinion there is a machine on your network using that name somehow and your first step is to find it. If you get these events in your log at specific times each day then that is the best time to search for the machine. Good luck.

dspentAuthor Commented:
There is NO machine using that name.  The reason I am 100% sure of this is because the machine was named that way previously because it was MY machine.  cly (my initials) w2k3 (windows 2003).......We have a strict naming scheme in our company and there are no exceptions to it....Except in the case of myself, our servers and the 4 other admins all machines are named according to the asset tag they receive when we roll them out.

So finding the machine that was using clyw2k3 is easy.  I am typing on it right now.  What I can't figure is why this machine's OLD computername is showing up in logs on other client machines when they don't have to connect or communicate with this machine in order to authenticate with the landesk server which is a totally different machine.

At any rate, I'm going to give you the points and close the question because you gave me an idea that I didn't even think of.....disjoining and renaming then rejoining the machine back to the domain.  The name clyw2k3.hnmc.hnm.tenethealth.com is the FQDN used when this machine was attached to the active directory domain.... It now uses Jones2K3 and is attached to a Windows NT4 domain...   This may actually fix the problem I think.
What you describe is the exact problem we encountered. The machine was named according to our naming convention (a combination of building and username), but was showing up in event logs under the name used during imaging (using Ghost For Unix). So the same machine was using 2 different names at the same time. We were able to verify both names were the same machine using Atlas VLAN Manager. Renaming & then rejoining the domain solved our problem, but we were never able to determine the cause. The verify this (if you want proof before trying to fix the problem) unplug your machine and see if the event is still recorded in the logs with your PC off the network.

Either way, good luck.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now