Environment
Novell ZENworks 10 Configuration Management Authentication
Novell ZENworks 10 Configuration Management Bundles
Novell ZENworks 10 Configuration Management Content
Novell ZENworks 11 Configuration Management Authentication
Novell ZENworks 11 Configuration Management Bundles
Novell ZENworks 11 Configuration Management Content
Microsoft Windows Server 2008
Microsoft Windows Server 2008 R2
Novell ZENworks 10 Configuration Management Bundles
Novell ZENworks 10 Configuration Management Content
Novell ZENworks 11 Configuration Management Authentication
Novell ZENworks 11 Configuration Management Bundles
Novell ZENworks 11 Configuration Management Content
Microsoft Windows Server 2008
Microsoft Windows Server 2008 R2
Situation
ZCM server slows down.
ZCM server may go into high utilization.
ZCM agents experience slow login.
ZCM agents have issues with downloading content.
Workstations resolve the server name without problems. When looking at the server itself, the server resolves it's own name with an IPV6 address when pinging localhost and the ServerShortName.
Examples of replies to ping command from server command prompt:
C:\Users\Administrator>ping localhost
Pinging ServerShortName.fully.qualified.name [::1] with 32 bytes of data:
Reply from ::1: time<1ms
C:\Users\Administrator>ping ServerShortName
Pinging ServerShortName.fully.qualified.name [fe80::5efe:10.10.0.224%11] with 32 by
Reply from fe80::5efe:10.10.0.224%11: time<1ms
ZCM server may go into high utilization.
ZCM agents experience slow login.
ZCM agents have issues with downloading content.
Workstations resolve the server name without problems. When looking at the server itself, the server resolves it's own name with an IPV6 address when pinging localhost and the ServerShortName.
Examples of replies to ping command from server command prompt:
C:\Users\Administrator>ping localhost
Pinging ServerShortName.fully.qualified.name [::1] with 32 bytes of data:
Reply from ::1: time<1ms
C:\Users\Administrator>ping ServerShortName
Pinging ServerShortName.fully.qualified.name [fe80::5efe:10.10.0.224%11] with 32 by
Reply from fe80::5efe:10.10.0.224%11: time<1ms
Resolution
Workaround:
1. Add a hosts entry for localhost that points to 127.0.0.1 and for the server short name and FQDN that points to the local IPv4 address.
Example:
127.0.0.1 localhost
10.0.0.224 ServerName.fully.qualified.name
10.0.0.224 ServerName
2. Reboot the server. *Note a restart of the services does not help, a reboot is required for this to work.