How can I troubleshoot errors relating to the Notification Server, Server name resolution?
If errors appear in the logs relating to failures resolving the server name, try the following steps.
We can try resolving the server name from a command prompt.
Go to Start > Run, type command, and click OK.
Type Ping <servername> and press Enter.
Try the same command with your Fully Qualified Domain Name (FQDN).
If neither Ping can resolve, you must fix your DNS or WINS issue. The clients need the ability to reach the server, and if the name cannot be resolved, this will inhibit the Altiris Agent's ability to communicate with the server.
We can try reaching the default website for the server where Notification Server is installed.
We should receive a custom page (if configured) or an under construction message. If you cannot access this page, IIS may not be configured to allow communication.
On the Notification Server, open up IIS Manager.
Right-click on the Default Website and choose Properties.
Select the tab “Directory Security”
Click Edit under Authentication and access control.
Check both "Enable anonymous access" and "Integrated Windows authentication"
How is the name of the server shown in the Altiris Agent client window? Try changing from FQDN to NetBIOS (or the other way around if NetBIOS is listed). Use the AeXAgentUtil.exe /server:<servername> utlitiy to make the change. (Note: Must put the server name in as shown in the NS client interface or the registry).
Imported Document ID: TECH14343
Subscribing will provide email updates when this Article is updated. Login is required.