Symantec Management Platform (Notification Server)

 View Only
Expand all | Collapse all

Task Servers, The Client Task Agent and The DMZ

  • 1.  Task Servers, The Client Task Agent and The DMZ

    Posted Oct 27, 2010 11:06 AM

    I have a problem configuring an NS in the DMZ. 

    I've set-up a child NS in the DMZ to service remote internet clients. I've specified the Alternate URL in the Agent settings and the test client is connecting to the DMZ NS server.

    The server name I'm using is contactable using the same DNS name either via the internal network or via the internet.

    ie. server.domain.com is resolved internally and externally

    The issue I'm having is the Task Server status component. The log files show that the client is trying to connect to the internal name which is based on the actual server host name ie. server10.local

    The client log file details are:

     

    <![CDATA[Attempting to register using "http://server10.local:80/Altiris/ClientTaskServer/Register.aspx?resourceGuid=c8e4afe8-b4ae-417a-972c-d0a30c8a6a4d&lastResort=true"]]></event>
    <event date='Oct 27 14:50:37' severity='4' hostName='host-a1' source='ConfigServer' module='aexnsagent.exe' process='aexnsagent.exe' pid='1172' thread='648' tickCount='304296' >
      <![CDATA[Basic inventory update has been sent]]>
    </event>
    <event date='Oct 27 14:50:37' severity='4' hostName='host-a1' source='ServerSettings' module='aexnsagent.exe' process='aexnsagent.exe' pid='1172' thread='648' tickCount='304296' >
      <![CDATA[Next basic inventory update will be sent to server server.domain.com at 2010-10-27 16:50:37, in 120 minutes]]>
    </event>
    <event date='Oct 27 14:50:39' severity='2' hostName='host-a1' source='AeXNetworkTransport' module='AeXNetComms.dll' process='aexnsagent.exe' pid='1172' thread='3928' tickCount='306515' >
      <![CDATA[Post to 'http://server10.local:80/Altiris/ClientTaskServer/Register.aspx?resourceGuid=c8e4afe8-b4ae-417a-972c-d0a30c8a6a4d&lastResort=true' failed: HTTP Request Failed: No connection could be made because the target machine actively refused it. (-2147014835)]]>
    </event>
     
    So i seem to have a mix of internal and external addresses, and i know the external connections can't connect to server10.local. Does anyone have any suggestions for a resolution so all connections are via server.domain.com instead?
     
    Does the server in the DMZ need to be renamed for example?
     
    Thanks.


  • 2.  RE: Task Servers, The Client Task Agent and The DMZ

    Posted Oct 28, 2010 02:50 PM

    http://www.symantec.com/docs/HOWTO2789