Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

GUP active connection

Created: 27 Feb 2014 • Updated: 01 Mar 2014 | 5 comments
This issue has been solved. See solution.

Hello,

My network team has seen unusual activity on the GUP side.

They have complaint about too many active connection from GUP to the SEPM Manager.

We tried to do some basic troubleshooting and it seems it's not related to our end issue.

Did uninstall and resinstall of GUP machine.

Formatted OS.

Scan with the Symantec Power Erasers but still showing active connection.

Operating Systems:

Comments 5 CommentsJump to latest comment

Chetan Savade's picture

Hi,

Thank you for posting in Symantec community.

It seems again you have been affected by a known issue.

Too many active connections from the Group Update Provider (GUP) to Symantec Endpoint Protection Manager
Fix ID: 3110944
Symptom: The Group Update Provider (GUP) computer keeps more than 200 connections open to Symantec Endpoint Protection Manager.
Solution: Fixed a callback function that was not properly called before closing
 
Reference: New fixes and features in Symantec Endpoint Protection 12.1.4
 
 
I would recommend to upgrade to the latest version of SEPM i.e. 12.1 RU4a.
 
 

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

SOLUTION
Rafeeq's picture

is the connection on port 2967? or 8014? Whats the port number?

GUP  - SEPM will be port 8014

Clients to GUP - 2097.

Clients to SEPM - 8014.

 

JS@support's picture

Port: 2967, we are using default port.

It seems to resolve both the problems I need to upgrade.sad

Chetan Savade's picture

Yes, upgrade can be a solution.

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

JS@support's picture

Yesterday midnight we performed an upgrade and issues are no longer exist now.