Symantec System Center Console- threats not shown - 02/18/09 09:52 PM
Our network uses Symantec AntiVirus Corporate Edition 10.2 on all servers (2003 and 2000 SP4) and clients (XP SP3). We use the Symantec System Center Console (SSC) to manage and monitor all clients/servers. Whenever a threat is detected, the SSC is supposed to show the a warning/threat icon on the client and its parent server, which helps to know if a virus has been detected.
At some point last year (we're uncertain), the SSC stopped displaying the alert icon when a threat was detected. Because of this, we were unaware of any potential threats. Now, I have to pull a threat log of all clients/servers each day to ensure that nothing is at risk. While this isn't a huge chore, the SSC should be functioning properly. All of the updates and sheduled scans are functioning as they should and communication between the clients and servers is not a problem. TCP port 2967 has been set as an exception in the clients' firewalls to allow proper communication.
I've uninstalled and reinstalled the SSC, but to no avail. I plan on calling Symantec, but haven't had time for the minimum 3 hours that I know I'll be spending on the phone with them. Was hoping that anyone in here might have encountered this problem before, or possibly have any clues or hints that I may not have thought of or seen before.
As always, thanks in advance.
At some point last year (we're uncertain), the SSC stopped displaying the alert icon when a threat was detected. Because of this, we were unaware of any potential threats. Now, I have to pull a threat log of all clients/servers each day to ensure that nothing is at risk. While this isn't a huge chore, the SSC should be functioning properly. All of the updates and sheduled scans are functioning as they should and communication between the clients and servers is not a problem. TCP port 2967 has been set as an exception in the clients' firewalls to allow proper communication.
I've uninstalled and reinstalled the SSC, but to no avail. I plan on calling Symantec, but haven't had time for the minimum 3 hours that I know I'll be spending on the phone with them. Was hoping that anyone in here might have encountered this problem before, or possibly have any clues or hints that I may not have thought of or seen before.
As always, thanks in advance.