1 Reply Latest reply on May 13, 2010 3:37 AM by phoffmann

    LDMS 9 gives "cannot find agent" error when device is on

    Rookie

      I am trying to push a Distribution Package to a machine, and LDMS 9 keeps telling me the status is Off and it can not find the agent.

       

      The PC is on

      I can ping it

      LDMS discovered it in Devices and shows that is can communicate with it

      I can remote control the box

      The Name and the IP are correct in the scheduled task

      All the LANDesk services are running

       

      Anyone have some suggestions?

        • 1. Re: LDMS 9 gives "cannot find agent" error when device is on
          phoffmann SupportEmployee

          Try this.

           

          1 - create a scheduled task with JUST this device.

           

          2 - Make sure that there's nothing else going on, ideally.

           

          3 - Start the task.

           

          4 - On the Core, go to (default directory):

          ""

          C:\Program Files\LANDesk\ManagementSuite\log\

          ""

           

          5 - open up the RAXFER.LOG

           

          ==> Looking at the timestamp, look which IP-address is being targeted. The line should look something like this:

          Wed, 12 May 2010 10:20:46 4612 4676 Performing remote execute, target 192.168.0.21:9594, hash 91543e62

           

          I marked the relevant part in BOLD RED. Is that IP correct (doesn't matter what the console says) - for this is the IP that we're sending the command to.

           

          ===============

          ===============

           

          6 - If the IP is correct, connect to the client's C$ share, and look here:

          ""

          C:\Program Files\LANDesk\Shared Files\

          ""

           

          and open up the SERVICEHOST.LOG -- that's essentially the "communication by the Core to me, and what I've been told to do" log file.

           

          Is there anything in there? If no, then the Core hasn't reached the client, and you will want to start network traces about where these things disappear off to.

           

          Anything from a DNS-problem, to a router being stubborn to a firewall could block communication here.

           

          =================

          =================

           

          7 - If the IP is wrong, I'm guessing you're targeting agents via DNS (which is principally a good thing) - but if the DNS resolves to the wrong IP (you can check that easily enough via a "PING CLIENTHOSTNAME" command in a CMD-window too), then you need to fix that DNS issue.

           

          I know you said "you can ping it", but I'm hesitant to assume that you're talking of the IP-address, or whether the hostname resolves to the correct IP.

           

          ================

           

          That tends to cover most such issues.

           

          - Paul Hoffmann

          LANDesk EMEA Technical Lead

          1 of 1 people found this helpful