Environment
Novell ZENworks Asset Management 3.3 - ZAM3.3
Novell ZENworks Asset Management 7 - ZAM7
Situation
The symptom
will be that the machine is not getting scanned. If you put
the collection client in diagnostic mode you may see somthing
similar to this message within the client trace
window:
07/31/06
11:17:40 - message channel failure
07/31/06 11:42:10 - OnTimer, entry: timer:30, retry count:0
07/31/06 11:42:11 - OnTimer init state: ConnState:2, Retrying:1, Lost:0
07/31/06 11:42:15 - ConnectForScanMode to unknown_collection_server (0.0.0.0)
07/31/06 11:42:15 - 29xID: LAN addr: 003065B91A22
07/31/06 11:42:15 - Could not ConnectForScanMode to unknown_collection_server (0.0.0.0)
07/31/06 11:42:10 - OnTimer, entry: timer:30, retry count:0
07/31/06 11:42:11 - OnTimer init state: ConnState:2, Retrying:1, Lost:0
07/31/06 11:42:15 - ConnectForScanMode to unknown_collection_server (0.0.0.0)
07/31/06 11:42:15 - 29xID: LAN addr: 003065B91A22
07/31/06 11:42:15 - Could not ConnectForScanMode to unknown_collection_server (0.0.0.0)
Resolution
This means that whatever the hostname is in the the hostname registry key for a windows machine ( HKEY_LOCAL_MACHINE\SOFTWARE\Tally Systems Corp.\TSCensus\CollectionClient) or in the OSX mac conf file cannot be resolved to the machine name of the collection server.
1. Resolve the DNS name
2. Use the ip of the collection server if the ip is static to the collection server.