What ports use Nod to update and to send ...

What port/ports and protocols use Nod to update and which to send statistical information to Eset?

 

TCP protocol, and HTTP (80) port

 

For both? Update and send?
I'm asking because Outpost give permision to NOD32KRN.EXE for Tcp outbond TCP protocol and remote port 80-83.

Are there any specifical rule to Outpost 3.51.759.6511 for Nod32?

 

Set Outpost to allow all the activity nodkrn.exe will do

 

Ok. Thank you

 

You are welcome !

 

Thank you again
I have some errors and don't know why.
It's possible because the specific server is down?
And if this are the reason, can I edit the server list to delete u8.eset.com or is not neccesary?

Time Module Event User
24/08/2006 13:09:46 Update Error connecting to server u8.eset.com.
24/08/2006 09:42:02 Update Error connecting to server 82.165.250.33.
24/08/2006 09:40:02 Update Error connecting to server u8.eset.com.
24/08/2006 06:38:10 Kernel The virus signature database has been successfully updated to version 1.1723 (20060824).
23/08/2006 23:37:25 Kernel Statistical information has been sent to Eset.
23/08/2006 16:37:50 Update Error connecting to server u8.eset.com.
23/08/2006 15:37:50 Update Error connecting to server u8.eset.com.

 

Well looking again the event log can see news errors.
Is it normal?

Can I delete HKLM/software/eset/nodcurrent version/modules/update/settings
and delete default server 3 and 5 or edit them with some settings or better, replace for other servers?


Time Module Event User
24/08/2006 17:12:43 Update Error connecting to server 82.165.250.33.
24/08/2006 17:10:43 Update Error connecting to server u8.eset.com.
24/08/2006 14:09:06 Kernel The virus signature database has been successfully updated to version 1.1724 (20060824).
24/08/2006 13:09:46 Update Error connecting to server u8.eset.com.
24/08/2006 09:42:02 Update Error connecting to server 82.165.250.33.
24/08/2006 09:40:02 Update Error connecting to server u8.eset.com.
24/08/2006 06:38:10 Kernel The virus signature database has been successfully updated to version 1.1723 (20060824).
23/08/2006 23:37:25 Kernel Statistical information has been sent to Eset.
23/08/2006 16:37:50 Update Error connecting to server u8.eset.com.
23/08/2006 15:37:50 Update Error connecting to server u8.eset.com.

 

You have successful updates. Don't worry about the logs, all you are seeing is NOD32 rolling through servers trying to find an update, which it does.

Cheers

 

OK Thank you Blackspear

 

You can set Outpost rule for NOD32KRN.EXE:

Where the protocol is: TCP
and where Direction is: Outgoing
and where Remote port is: 80
Allow it

If you have your Outpost set as 'Block Most" - this rule will be enough.

 

Ok, it's the same as default just only 80 instead 80-83.
Thank you.

 

My pleasure.

Cheers