I am experiencing some strange issues with deployment of my Kace Agents. Sometimes I will do an advanced provision by IP address to a set of machines (anything from 2-60) and some will because the agent says it cannot connect on a certain port (either 139 or 445), even though those ports are open. I will then try to do that same machine on its own as a single machine provision, and it will work fine. This seems to happen on both XP and Windows 7, yet other machines with similar configurations work just fine.


I did notice one other thing which may or may not be related-the network speed is (for reasons I cannot say) set for 10Mb half-duplex. Could that be affecting our deployments?


we are using Kace agent version 



Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer



I wouldn't think the 10mb half duplex would be an issue, but I've never tested it.

This is written for a 5.1 agent, but most of the troubleshooting is valid: http://www.kace.com/support/resources/kb/article/troubleshooting-agent-provisioning-kbox-client-deployment

Windows 7: http://www.kace.com/support/resources/kb/article/Troubleshooting-K1000-Agent-Provisioning-for-Windows-7

General settings: http://trn-kickoff.kace.com/help/doc/Administration/wwhelp/wwhimpl/common/html/wwhelp.htm#href=kace_agent_provisioning.05.07.html&single=true

Answered 09/12/2012 by: jknox
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity



We had a similar issue and it was that the kbox was timing out on the connection, not that the ports were closed. Swapped out the old switch for a shiny new cisco and they worked like a charm!

Answered 09/12/2012 by: kwhatcher
Senior Yellow Belt

Please log in to comment

we switched to 1GB duplex and that has seemed to have fixed the issue mostly-now the only machines that appear to fail are ones that are simply off


thanks all

Answered 09/13/2012 by: dkurz8814
Fourth Degree Green Belt

Please log in to comment