Client Management Suite

 View Only
Back to discussions
Expand all | Collapse all

Clients no longer using Task Server alias, using FQDN instead

  • 1.  Clients no longer using Task Server alias, using FQDN instead

    Posted Sep 24, 2012 11:04 AM

    We have created an alias for our task server to use in place of its FQDN. It has been working for quite some time until, recently, Task Server agents  switched from using the alias to the FQDN.

     

    The fallout of this is that our remote clients are no longer able to reach a Task Server. The a.logs show the errors below (with FQDN entered where the FQDN has replaced the alias).

    • <event date='Sep 23 23:03:05' severity='2' hostName='HOSTNAME' source='AeXNetworkTransport' module='AeXNetComms.dll' process='AeXNSAgent.exe' pid='4936' thread='1620' tickCount='200663118' > <![CDATA[Post to 'http://FQDN/Altiris/ClientTaskServer/Register.aspx?resourceGuid=0b58104e-97b5-417e-a3d7-133ed0f2f7a4&lastResort=true' failed: HTTP Request Failed: No such host is known. (-2147013895)]]></event>

    We have noticed, on the Task Server, that both the alias and the FQDN have entries in the HKLM\Software\Altiris\Communications\Trusted Servers\Communications\Server Profiles\Servers key. We're not sure if that is the culprit.

    Does anyone have any ideas about how we can force our clients back to using the Task Server alias rather than the FQDN?

    Thanks!