Unable to update Nod32 v2.12.3

I have not been able to update Nod32 today.
Here is the log:
Time Module Event User
5/1/2005 3:46:23 AM Update Error connecting to server u3.eset.com.
4/30/2005 19:46:03 PM Kernel The virus signature database has been updated successfully to version 1.1085 (20050501).
4/30/2005 11:45:38 AM Kernel The virus signature database has been updated successfully to version 1.1084 (20050430).
4/28/2005 20:45:51 PM Kernel The virus signature database has been updated successfully to version 1.1083 (20050429).
4/28/2005 12:45:43 PM Kernel The virus signature database has been updated successfully to version 1.1082 (2005042.
4/28/2005 5:03:13 AM Kernel The virus signature database has been updated successfully to version 1.1081 (2005042.
4/27/2005 22:03:25 PM Update Error connecting to server u7.eset.com.
4/27/2005 19:03:10 PM Kernel The virus signature database has been updated successfully to version 1.1080 (2005042.
4/26/2005 18:04:06 PM Kernel The virus signature database has been updated successfully to version 1.1079 (20050426).
4/25/2005 18:34:39 PM Kernel The virus signature database has been updated successfully to version 1.1078 (20050425).
4/24/2005 15:39:42 PM Kernel The virus signature database has been updated successfully to version 1.1076 (20050424).
4/24/2005 10:40:22 AM Update Error connecting to server u3.eset.com.
4/24/2005 10:40:10 AM Update Error connecting to server u5.eset.com.
4/24/2005 10:39:53 AM Update Error connecting to server u1a.eset.com.

I cannot even access www.nod32.com.

Any suggestions.

Thank You,
Shahtech

 

According to the website, and my own copy of NOD32, you have the most recent definitions.

Blue

 

Looking at that log, you do not really have anything to worry about. Eset has several update servers available. If you cannot connect to one, it will try the others. By default, NOD32 looks for updates every hour.

Keep in mind that the Event Log shows successful updates, and it also shows failure to connect. However, if there is a successful connection but with no update (as when Eset has not put out any new virus definitions), this is NOT logged. This is what is happening to you. Nothing to worry about.

As for why you cannot connect to http://www.nod32.com , I do not know. Probably just a temporary thing.