Managed Clients NO COMMUNICATION!

[MyEyesAreBurning]

We have a NAV server on the network... The Big boss got a virus, and of course the clients are locked and managed from the SCS... Problem is that the big bosses computer is not managable. I get a error that states that the computer is either off line of there is no communication between the server and the client. Im getting this error while I'm TermServered(RDC) in to the server from the client which leaves me shaking my head...
Ive also checked the services and poked around in SCS but cant get the server to update virus defs of do a manual scan...HERES the kicker!!! I can on some of the other machines!!!!! what is going on here!!!!??? please help...
Thanks in advance,
MEAB

 

[Auger282]

if it was me.. I would run housecall over the web to get a clean scan... then maybe a reinstall of navce

http://housecall.trendmicro.com

 

[LawnBoy]

The virus has disable Symantec services on that machine. That's why it won't comm or get updates. Not that unusual.
You can run an online scanner as Auger282 suggests, you can also map to that machine and scan it from your machine.

 

[TweakMYbox]

I would Download the latest defs manually from Symantec's web site, boot into safe-mode, install the drivers, and run a full-system scan.

Mike Fegan, MCSE

Read about the best FREE IT tools available, and check out the 'Babe of the Week' at

http://tweakmybox.com

 

[MyEyesAreBurning]

Thanks for the input gentlemen I will look into the solution... I just got back from tinkering with the machine and doing some reading and it seems that the problem was the windows firewall. I turned it off and it worked like a charm. Although I would not recommend just opening all the ports up. I found a good artical from Indiana University so Im assuming that its correct...but basically it stats that you should allow a exception and open port 2967 for NAV to communicate with remote agents... heres the artical.

http://kb.iu.edu/data/aowt.html

check it out let me know what you think.

MEAB

 

[CCESAV]

You should make sure the parent server group root certificate is still present on the client and that it is the same one as the root certificate of the client's parent server

From Symantec Knowledgebase:

Confirm the presence of the server group root certificate
Communication fails if the server group root certificate is not present on Symantec AntiVirus 10.x servers, managed clients, and the computer that runs Symantec System Center. Legacy clients and servers do not need a copy of the root certificate.

To confirm the presence of the certificate on parent servers and computers that run Symantec System Center

1. Start Windows Explorer.
2. Open the Symantec AntiVirus program folder.
The default location on a Symantec AntiVirus Corporate Edition server is the following:
<OS drive>:\Program Files\SAV
The default location on a Symantec Client Security server is the following:
<OS drive>:\Program Files\SAV\Symantec AntiVirus
3. Open the pki\roots folder and find the xxx.x.servergroupca.cer file.
4. If the xxx.x.servergroupca.cer file is not present, do one of the following:
* Copy the file from another parent server and restart the Symantec AntiVirus service.