Hi,

Please help.

Thanks

Enable sylink debugging, let it run thru a few heartbeats, post the log here:

How to enable Sylink debugging for the Symantec Endpoint Protection 11.x and 12.1 client in the Windows Registry

Hello William from the screen shot its evident that it was able to connect to SEPM using port 8014 ---> Status was successful.

Next its trying to connect on  Port 80 and its not able to connect. May be you have used incorrect Sylink file

From a healthy client try to replace Sylink file first..

How to change the sylink.xml file in Symantec Endpoint Protection (SEP) 12.1

http://www.symantec.com/business/support/index?page=content&id=TECH157585

Try it

Back up registry
1. Click Start, and then click Run.
2. In the Open box, type regedt32, and then click OK.
3. Locate HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections.
4. Right Click on Connections from the menu, click Export.
5. In the Save inbox, select a location in which to save the .reg file, type a file name in the File name box, and then click Save.

Remove DefaultConnectionSettings & SavedLegacySettings
1. Delete the following registry keys:
HKEY_USER\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings
HKEY_USER\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\SavedLegacySettings
2. Reboot the system.

Hi Brian,

It's been ok after smc -stop then smc -start

Thanks

I think Rafeeq has the right path here.

It sounds like either the Management Server List (MSL), or sylink.xml communciations file assigned-to/installed-on this client has two entries for your SEPM.  One of these entries correctly lists the port 8014, while the other lists the incorrect port of 80.

A quick smc stop and start has resolved the issue in the short term, as would just leaving the client to do its own thing (as it will cycle through the list of SEPMs until it manages to find one).

The long term solution would be to update the MSL assigned to this client (via the group's "communications settings") to remove the erroneous SEPM listing on port 80 (and maybe update the local sylink file too if you want).  Doing this means the client will no longer try port 80, and should consistently use port 8014 going forward and connect first time every time.