Update servers config/problems?

Hi.

The computer/internet is on 24/7 and working fine. I have a legal, 2 year license for NOD, not cracked or anything.

In my event log, I have quit a few of these:

Time Module Event User
09/01/2006 13:44:19 Update Error connecting to server 82.165.250.33.
09/01/2006 13:13:31 Update Error connecting to server 82.165.237.14.

My update server settings are on choose automatically, and the following servers are in the list:

http://img324.imageshack.us/my.php?image=untitled5jq.jpg

Why do a couple of them (the ones I can't connect to) show up as IP's where as the others are uxx.eset.com

Why can't I connect to them?

Are there any other servers I can add, I'm sure I read somewhere that there were 12 update servers, which I would assume to be in the format of:

u1.eset.com
u2.eset.com
...
u12.eset.com

ETC, if so, how do I go about adding them. Also is it possible for me to remove the servers that aren't working (and is this recommended?). When NOD tries to look for an update, I assume it randomlly chooses a server, if it chooses either 82.165.237.14 or 82.165.250.33, and fails - does it give up, or will it try the others?

I never used to get any of these errors, I've also restored the computer back so theres nothing wrong with the computer/internet connection. I do have the latest version (1.1357 at the time of writing this) but I just don't see why I'm getting these errors now.

I do reformat/restore from an image quite frequently, which means that NOD will have to update from the installer sig's each time. This wouldn't make the servers think I've shared my username password would it?

Thanks in advance.

 

the ip addresses are are just there in-case of DNS failure. Over the weekend at least, u6 (the ip ending in 14) has been having issues - but you don't need to worry about it too much, I'm sure Eset is on it...

hth

Greg

 

Don't worry I have the same problem, but just leave it to Eset to get them server up and running again.