Cannot Update NOD32 v2

I have a single license for NOD32 v2, but am unable to update using XP Pro SP2.
I have the automatic Update service disabled and am using a user account to update. I have tried updating while using admin account with same results. Does it require that I have Automatic Updates enabled, and then would it require me to use an admin priviledged account to successfully update NOD32 V2?

I have updated several times in the past with the trial version, then only once after I installed the paid version. The connection rotates through all listed servers then fails the update.
I need a hand here.

TIA

 

What error message is seen in you Event Log?

Control Centre> Logs> Event Logs

Cheers

 

I'd check the following:

1, make sure you are able to ping Eset's update servers

2, proxy settings in the NOD32 update setup. If no proxy is used, it MUST REMAIN DISABLED

3, if a firewall is used, make sure the NOD32 kernel service has access to the Internet allowed.

 

I get all of the following:

Time Module Event User
10/20/2005 2:41:00 AM Update Function: gethostbyname, parameters: , return value: 11001

10/20/2005 2:39:50 AM Update Error connecting to server 82.165.250.33.

Time Module Event User
10/20/2005 2:14:39 AM Update Function: gethostbyname, parameters: , return value: 11001

Time Module Event User
10/20/2005 2:14:39 AM Update Update attempt failed (Server connection failure.)

 

I'll make sure to check the settings. I'm guessing it's always slow connections to the server.

 

Actually, there are many error messages in the log. I'm not sure which are best for posting here, but they all seem to say that

"error connecting to server"
"UPDATE ATTEMPT FAILED" or
"function: gethostbyname, parameters: , return value: 11001"

 

See if this thread helps in regards to Winsock.

Failing this and not seeing any issues with what Marcos has pointed out, I would uninstall, removed the Eset folder from C Drive> Program Files and reinstall a fresh copy of Nod32 from Esets website. Make a "typical" installation as per instructions found HERE

Hope this helps...

Let us know how you go.

Cheers

 

Thanks to both you and Marcos,

I have successfully updated. Yes, Marcos' suggestion concerning the firewall allowing nod32krnl was a bullseye.

You were both very helpful.

 

Good to see and thanks for letting us know.

Cheers