/build/static/layout/Breadcrumb_cap_w.png

Agent wont connect to Server, except when it is forced

We have one server where the agent wont talk to K1000. I have tried re-installing the agent to no avail. The server will connect when I run a runkbot 4 0 command. However, this connection doesnt seem to last more that a few seconds. I cannot run any scripts through or even force inventory through K1000 to the server in question. Has anyone run into this issue before? out of 200+ machines this is the only one that is having issues staying connected to our K1000 appliance. Thanks for any direction.

4 Comments   [ + ] Show comments
  • we are using 8.1.52-x86 with server 2012 and connecting through the internet not the VPN.
    One of our Servers was not connecting even after we received the inventory.xml ... we left it did connect after a long time yet has been strong after that.
    How long are you giving it? - CEIadmin 6 years ago
  • Specify agent and server version. - Channeler 6 years ago
  • If Agent version is below 7 and server version is above 7, it will not connect, What versions are you running? - Keltonfoss 6 years ago
  • When you uninstalled KACE from the server, did you delete the following folders before reinstalling? I would also recommend deleting it from the K1000 (Inventory and Assets) to get a full clean reload.

    C:\ProgramData\Quest\KACE
    C:\ProgramData\Dell\Kace
    C:\Program Files (x86)\Quest\KACE
    C:\Program Files (x86)\Dell\KACE - DaveMT 6 years ago

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ