1

HI all,

Recenlty i ran into a issue i use ERA to monitor all of our clients antivirus status.

Now most of the users cannot update their virus signature database. same goes for the Remote Admin console.

Is there anything in particular that is causing this to happen???

4 Spice ups
2

Check to make sure your user/pass for NOD32 is current. Make sure the clients having the issue are on a fresh login. Then go to your ESET Console and send update to the selected clients.

edit: I believe the cause is a token ring /permissions [bug] issue that started happening about a year ago with the ESET console. We had the same issue here and though the ESET kept us completely virus free for 3 years, my boss opted to go to Sophos because of that very issue (and a few other console problems).

3

Are your client computers showing up in the clients tab on the ERA? what policy is being applied to the clients? check update settings of said policy to make sure that clients are connecting to the proper location for updates. i would also check to make sure your server can connect to the update site.

4

Yes they are showing up in my ERA but it does not seem they are connected.

If i choose update automatically i can connect and update on clients side, in my ERA if i try to update is just Fails to connect.

About :the cause is a token ring /permissions [bug] issue what was the fix for this issue??

What should i change or update…etc on the server side( i don’t work alot on the server)

Thanks guys

5

We had to update the console and do a .net repair to fix the bug.

6

Can ERA update itself? Verify that ERA has downloaded the latest update (6460 as of this writing).

Go to Tools>Server Options.

Click Updates tab.

7

  1. I have seen a minor bug in the occasional Definitions update that won’t let the machine update - but it clears itself when the client machine is Restarted.

  2. I once got myself in a tangled mess by getting the NOD32 and RA Console ports reversed, and made it worse when trying to figure it out by accidentally blocking the RA port and forgetting to open it again. So I got all the clients fixed but I had no Console until I realized that the problem was…me!

8

Will try the .NET framework fix/update.

I also restarted server but still persists, might be proxy settings??

What ports need to be opened??

Thanks guys

9

Ports open on ERA console

Console- 2223

Client - 2222

Replication - 2846

Remote Installer Agent - 2224

10

Thank you All

11

port 2221 (default) for updates if you are running a mirror setup on your ERA Server