Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3
Long zenlogin times when agent is updated to 10.3 but the CASA and CASA auth token client is at a previous version. This problem occurs especially when the ZENserver does not use default port 443 but another service listens on 443.
Note: This problem is specific to agents at 10.3 or later.
ERROR (from CasaAuthToken.log):
[134-1EC] [17:37:32] CASA_AuthToken -ObtainAuthTokenFromServer- port = 443
[134-1EC] [17:37:48] CASA_AuthToken -InternalRpc- Unsuccessful send http request, error = 12007
[134-1EC] [17:38:33] CASA_AuthToken -ObtainAuthTokenFromServer- End, retStatus = C7FF0025
Note in the log above that 443 port is being used and that this port is not the ZENworks server port.
Ensure that the CASA and Novell Auth Token programs are up to date on the managed device.
In 10.3 and later, the CASA login should try the standard ZENworks port first. If 443 is tried first this may cause long login times or certificate errors if the standard https port is in use by a non-ZENworks service.
In 10.3 and later, CASA dynamically determines the default ZENworks port. For example, the zmd-messages.log should show:
[DEBUG] [07/14/2010 05:54:34.171]  [ZenworksWindowsService]   [CommonCasa]  [SetATSHostList will be called with ]  
[DEBUG] [07/14/2010 05:54:34.171]  [ZenworksWindowsService]   [CommonCasa]  [hostname is: linux-64.mry.com:444]  
[DEBUG] [07/14/2010 05:54:34.171]  [ZenworksWindowsService]   [CommonCasa]  [hostname is: linux-64.mry.com:2645]  
Where the first port is the standard port used by ZEN services (confirmed with zac zc -l)
If the system update failed to update to the current versions:
1.7.1614 or later authtokenclient
1.7.1613 or later CASA
Correct the problem with system update files and compare to download files on server.
For agents with older versions, uninstall and reinstall both from the newer MSIs.