Have not been able to update pro

Problems updating for the past half hour. Is it just me? I know it's just temporary, but am I the only one? Need to know if its my PC or is it the servers i've selected.

 

No problems here.
Let NOD32 choose server automatically.

 

Time Module Event User
3/27/2006 21:53:02 PM Update Error connecting to server 82.165.237.14.
Time Module Event User
3/24/2006 18:40:41 PM Update Error connecting to server u8a.eset.com.
Time Module Event User
3/24/2006 18:40:01 PM Update Error connecting to server u3.eset.com.
Time Module Event User
3/23/2006 14:18:39 PM Update Function: gethostbyname, parameters: , return value: 11001
Time Module Event User
3/23/2006 14:18:38 PM Update Error connecting to server www.nod32.com.
Time Module Event User
3/23/2006 14:18:33 PM Update Error connecting to server u8a.eset.com.

I have it set to Automatic.

 

If there is an error connecting to one server the error will be logged, and NOD32 automatically switch to another server to check if there is an update available.
If there is no update available at that moment, NOD32 does not log something like "Connected succesfully to another server, but no update available".

 

There haven't been any problems with www.nod32.com recently so I assume the problem was with your Internet connectivity.

 

None, I clicked the update now button and this is the entry in the Events log Time Module Event User
3/28/2006 0:31:51 AM Update Error connecting to server u8a.eset.com.
3/27/2006 21:53:02 PM Update Error connecting to server 82.165.237.14.

 

I have the same errors once in a while, namely with 82.165.237.14, but updating always takes place through another server, so....don't worry about it, except if it doesn't update at all!

 

When the update first comes out (I see it in the security updates forum) I can't update straight away. I just leave it and it updates itself within the hour.

 

I am seeing some update errors relating to the IP address servers listed as update servers on our office mirror - these are not due to internet connectivity issues our end.

 

82.165.237.14 is overloaded quite often, but this shouldn't concern you as far as you have the update server set to automatic selection.

 

I posted the same question when I first purchased NOD. What I have found is that you will see some errors from time to time, but I have never been denied an update due to them.

Most other AVs that I've used never logged server errors just the actual "Update Successful" message. I think NOD's additional information may make some new users feel uneasy, but in reality there really isn't anything to worry about unless you are overdue for an update that's already been published.