Video Screencast Help

symantec management agent communicating issue

Created: 19 Sep 2013 | 4 comments
Nagaraj Kukke's picture

Dear Support,

i have installed altiris notification server with client management features, i have some issue related to communication between NS to SMA, NS is installed in VM server for testing purpose i have installed SMA in some of the vm systems and physical systems but my issue is all vm systems are communicating to server after agent installation but physical systems are not communicating what might be the thing i have missed related to configuration side is there any change for VM and physical systems please let me know.

Operating Systems:

Comments 4 CommentsJump to latest comment

Sachin Sawant's picture

check ports are open or not.

Communication ports:

Port No:

Protocol

Use

Use for

401–402

UDP

Deployment Solution

Is used to tickle the A client

67, 68, 69, 4011

UDP

PXE

DHCP

402

TCP

DS Client

To talk with Altiris Server Service

2070-2073, 1758-1759

UDP

PXE

For TFPT and MTFTP transfer of PXE image

1010

TCP

PXE Management

PXE Config to talk with PXE configuration service

401

UDP

RapiDeploy

Imaging engine

4949, 3829

TCP

PCT Real Time

To communicate between PCTWiz and RtdestAgent

4950, 4951

TCP

PCT Real Time

Used to search for the RtdestAgent

4952

TCP

DS Communication

Used for managing the connection drops

8080

TCP

Data Manager

DS Web Console

138

UDP

Net Logon

NS client installation

445

UDP

MS DS/CIFS/SMB

non-HTTP communications (e.g. client package download via UNC)

80

TCP

HTTP

NS Client communication

ICMP

-

Ping

Package Server speed check

80, 443

TCP

NS Client

Altiris Agent once installed

135, 137, 139

UDP

NetBIOS

non-HTTP communications (e.g. client package download via UNC)

52028, 52029

TCP

NS Client

Multicast

80, 135, 150, 2500, 53, 137, 139, 1433

TCP

Altiris Console

Console using a Remote Computer

1680-1701

TCP/UDP

Carbon Copy

Remote control (not DS)

161

TCP

SNMP

For Network discovery and management

1011

TCP

Monitor Solution

43190

UDP

Recovery Solution

43189

TCP

Recovery Solution

50120 – 50124

TCP

Task Server

Nagaraj Kukke's picture

windows firewall is disabled and all ports are able to telnet to the server but agent is not communicating the same configuration systems in VM are communicating properly what migh be the issue

Thanks & Regards,

Nagaraj Kukke

Brandon Morrow's picture

I would check the agent logs for any errors or warnings. Below is a link to a document to help find the agent logs and also a tool to help view the logs.

Where can I find logs? - http://www.symantec.com/docs/HOWTO4922

Symantec SSE tools for ITMS - http://www.symantec.com/docs/HOWTO60787

Saeed's picture

There are lot of thing you will need to see.

1] Have you deployed the client to PHY machine via server ? If yes then the out bond communication is working fine. If not then try doing it you will come to know if your VM configration needs any tweeks.

2] VM client are taking to the server this mean all the basic port that are needed for communication are open hence you do need to work on opening any port on the NS server.

3] You can also try copying some files for your PHy clinet to the NS check if that is working.Also try opening the NS via web on the PHY machine.

I stongly think that there a problem with the cofigration with your VM. We used to set the VM on brigde mode for it to communicate with the PHy machine. You can try this as well.

If a forum post solves your problem, please flag it as a solution. If you like an article, blog post or download vote it up.