|
|
|||
Unable to push a task to a client (Connection refused)
VERSION 1
Created on: Aug 29, 2008 2:40 PM by Tracy Hammond - Last Modified: Aug 29, 2008 3:14 PM by Tracy Hammond
When starting any task from the ManagementSuite Console the following error is returned:
Failed, The remote system refused the network connection
This is usually a certificate problem, but in this case the problem occurs when the SSL libraries are loaded and doesn't even make it to the certificate check.
You will see the following log entries:
ResidentAgent.log
Fri, 29 Aug 2008 14:52:43 1276: Entering ServiceHostThreadProc, thread id 1052
Fri, 29 Aug 2008 14:52:43 1276: Handling request from 192.168.5.10
Fri, 29 Aug 2008 14:52:43 1276: Service host (process) 1048 handlings request from socket 504
Fri, 29 Aug 2008 14:52:43 1276: Failed to read from serivce host pipe, service host has finished
Fri, 29 Aug 2008 14:52:43 1276: Request handling complete
Fri, 29 Aug 2008 14:52:43 1276: Exiting ServiceHostThreadProc
ServiceHost.log
Fri, 29 Aug 2008 14:52:43 1048: Service Host Started, Host TH-WIN2K.134451,:9594, Peer 192.168.5.10, IP Address 192.168.5.134
Fri, 29 Aug 2008 14:52:43 1048: Public key path C:\Program Files\LANDesk\Shared Files\cbaroot\certs
Fri, 29 Aug 2008 14:52:43 1048: Cached certificate EXPIRED cached(0) now(128645167634653750)
Fri, 29 Aug 2008 14:52:43 1048: Failed to initialize SSL context
Fri, 29 Aug 2008 14:52:43 1048: Service host has finished
This problem (in this scenario) is that the Primary DNS Suffix is incorrect. Anything in this field that does not resolve, will cause the SSL failure. I have seen this caused by blank, gibberish, and multiple domains separated by commas type entries.
|
|||||
I have an issue with my new machines, I believe due to using the wrong Sysprep for SP3 at some point during a rebuild of my image. I have checked the items above and cannot find the reason for the connection refused. When I look at the ServiceHost.log file, it has no entries from today when I attempted to push software out to a machine. I've tried running sysprep for SP3 once I realized that I used SP2 Sysprep and it still refuses the connection. I have 40 machines this way, is there an easy fix?