Video Screencast Help

Altiris communication from agent and server

Created: 18 Dec 2013 • Updated: 18 Dec 2013 | 7 comments
This issue has been solved. See solution.

Hi All

I'm installing Altiris client management suite and server management

Could all please help me to clear some concern?

- As I understanded, currently client will communicate with server after agent installed on client. Client alway establish request to server as schedule

So in some case, Server need to establish connection to client. How can it work, which port need to open between both?

Thanks and Best Regards

Operating Systems:

Comments 7 CommentsJump to latest comment

pete_4u2002's picture

check this link

Ports and Protocols for Symantec IT Management Suite 7.1

Article:HOWTO83503  |  Created: 2013-02-07  |  Updated: 2013-03-21  |  Article URL

Summary of Ports Used by Altiris Solutions

Article:HOWTO3401  |  Created: 2006-05-03  |  Updated: 2013-04-30  |  Article URL
telecomvn's picture

HI Pete

Thanks for your respone. I read this link

So it doesn't clarify how can server communicate with client after agent install. I mean how can Altiris work with client, if client isn't communicate with server for along time. How can server know, and how can it initial connection client


andykn101's picture

To get the server to trigger tasks on the client the system uses the Task Agent and Task Server, ports can be configured under Settings > Notification Server > Site Server Settings > Task Service > Settings > Task Service Settings. 50120-24 inclusive by default.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

telecomvn's picture

Hi Andy

You mean this this case, NS server will send request to client. This mean we have to open port 50120-24 from server to client if we have firewall


James007's picture

Notification Server uses standard MS ports to connect to the workstation from the Notification Server to copy over the bootstrap and then HTTP from the workstation to the Notification Server to download the agent.

Initial connection Notification Server to client

  • UDP 138 (NETLOGON)
  • TCP 445 (MS DS/CIFS/SMB)

Initial connection Client to Notification Server (after Service Starts)

  • TCP 80 (HTTP) client download
  • ICMP Type 8 (PING) package server speed check

See this post

pete_4u2002's picture
HTTP Client / Server communications, such as policy updates and posting events:

The Agent establishes a connection to server port TCP 80 for HTTP and server port TCP 443 for SSL. This port is configurable by the user, however, and can be set to any free port.