Why I can't connect to 'www.eset.com' ?

Since yesterday I can't connect to eset homepage.. tried two different connections... just to be sure it was not a DNS problem...

Anybody else?

 

working here....check your host files.

 

No problems here.

 

I don't know about NOD32.com - but the nameserver (singular) for eset.com domain I think... a mistake in nameserver records has knocked the domain out of cache for major networks, cox, at&t, internap to name just THREE major ones.

If you mess up a nameserver record - it can have knock on effects for 72 hours while the rest of the net catches up to you.

Meanwhile, the nameserver HAS been corrected, but being there is only one:

NS.NOD.SK

My guess (I haven't checked) is that this is the SOA for nod32.com and eset.com.

This is also affecting people attempting to download trials and full versions from u3 and u4. It may also have update implications.

 

it's a bit strange here, too!

Using my usual dsl provider connection I can't reach eset.com, even trying to ping leads to "unknown host". When I try another provider (in this case a dial up connection) I can reach eset.com and also ping it - IP then is 195.12.128.61. Now the strange thing: putting this IP in adressbar while using my usual dsl connection I am lead to "http://home.euroweb.sk/".

regards,
qs

 

@ webyourbusiness

thx for the explanantion.

qs

 

This is not Anormal, que sera, a lot of web sites can be hosted in the same ip address.
and if you use the ip adress, the server regarding this adress, which have the website you are looking for, can answer with the default web site, depending of the server configuration. Web sites are not referred only by the ip address, but also with their name.

 

Doesn't work for me either.

 

Thanks for the many of you that replied and for the explanations of possible cause....

Now it seems back....however the info on signature updates is very old.... weird...

Fax

 

Now there is even better thing. NOD32 CANNOT update AT ALL for me

 

@ zashita

as you see, I don't know much about this. So far I thought, an IP address associated to a big company server wouldn't change frequently. I would have expected to be lead to at least some kind of eset related page. Euroweb.sk doesn't seem to belong to eset (?) but I couldn't tell for sure - my slovak is a bit rosty and I don't know of a translation page for slovak.

As always Wilders is a great place to learn.

thx
qs

 

No problem on www.eset.com and NOD32 updates...

 

This don't mean that Eset website change its IP, but the host server associated with this IP have not only eset website on it. And the other website can be the default site of the server if we try to access to a website with this ip address. This depends of the server configuration.

We all learn a lot each day here

 

Euroweb is a hosting company I think - like us...

Most of our clients sites run on shared servers, some on VPS and some on dedicated machines. Even those clients with dedicated machines have multiple IP addresses - we put AT LEAST two IPs on the machine. Whenever APACHE (I can't speak for other web server applications), is addressed using an IP address, it serves the FIRST site in the list for those sites it has under that IP. Using names, you can have thousands of sites sharing an IP, but referencing a resource by IP, the site returned the default, or first site configured under that IP address.

If - and this is a BIG if ... if anyone gets problems receiving updates, they could TEMPORARILY add the IP addresses of an update server or two - such as:

u3.eset.com = 82.208.27.3
u4.eset.com = 62.168.97.99
u5.eset.com = 82.165.250.33
u7.eset.com = 213.215.116.226

These machines are geographically diverse - all over the place it seems - but it would NOT be recommended to keep IP addresses in place beyond any DNS update, as there is nothing to say that any one or all of these servers needs to stay on those IPs for any length of time!

regards

Greg

 

I tried the 'fix' and the 'fix' is NOT working.

I added these addresses to the server list and none of them have the updates. I just purchased 3 licenses yesterday, and now I'm wondering if my licenses are recognized as valid or not... in addition to this...

(at least, I have a backup: AVG free antivirus)

here's the error message log:
Time Module Event User
6/29/2005 14:39:48 PM Update Update attempt failed (File not found.)
6/29/2005 14:39:13 PM Update Update attempt failed (File not found.)
6/29/2005 14:38:50 PM Update Update attempt failed (File not found.)
6/29/2005 14:38:46 PM Update Update attempt failed (File not found.)
6/29/2005 13:07:39 PM Update Function: gethostbyname, parameters: , return value: 11001
6/29/2005 13:07:39 PM Update Update attempt failed (Server connection failure.)
6/29/2005 13:07:37 PM Update Error connecting to server www.nod32.com.
6/29/2005 13:07:36 PM Update Error connecting to server u3.eset.com.
6/29/2005 13:07:34 PM Update Error connecting to server u7.eset.com.
6/29/2005 13:07:32 PM Update Error connecting to server 82.165.250.33.
6/29/2005 13:07:31 PM Update Error connecting to server u1a.eset.com.
6/29/2005 13:07:31 PM Update Error connecting to server u4.eset.com.
6/29/2005 12:21:22 PM Update Function: gethostbyname, parameters: , return value: 11001
6/29/2005 12:21:22 PM Update Update attempt failed (Server connection failure.)
6/29/2005 12:21:21 PM Update Error connecting to server www.nod32.com.
Time Module Event User
6/29/2005 12:21:21 PM Update Error connecting to server www.nod32.com.
6/29/2005 12:21:19 PM Update Error connecting to server u3.eset.com.
6/29/2005 12:21:17 PM Update Error connecting to server u4.eset.com.
6/29/2005 12:21:15 PM Update Error connecting to server u7.eset.com.
6/29/2005 12:21:13 PM Update Error connecting to server u1a.eset.com.
6/29/2005 12:21:12 PM Update Error connecting to server 82.165.250.33.
6/29/2005 12:07:27 PM Update Function: gethostbyname, parameters: , return value: 11001
6/29/2005 12:07:27 PM Update Update attempt failed (Server connection failure.)

 

Just now succeded to update nod

 

hmmm.... now I can connect and it updated successfully

okay, so I removed all of the above mentioned servers and tried again!
it worked this time...
(now to try the other two computers and see if NOD32 recognizes my licenses!)
Time Module Event User
6/29/2005 14:52:36 PM Kernel The virus signature database has been successfully updated to version 1.1158 (20050629).

thanks!

 

I have been having that problem all day.

Time Module Event User
6/29/2005 14:51:56 PM Update Error connecting to server u3.eset.com.
6/29/2005 14:51:52 PM Update Error connecting to server u1a.eset.com.
6/29/2005 14:51:48 PM Update Error connecting to server u4.eset.com.
6/29/2005 14:51:46 PM Update Error connecting to server u7.eset.com.
6/29/2005 14:04:26 PM Update Error connecting to server u7.eset.com.
6/29/2005 13:04:28 PM Update Error connecting to server u3.eset.com.
6/29/2005 13:04:26 PM Update Error connecting to server u1a.eset.com.
6/29/2005 12:04:26 PM Update Error connecting to server u3.eset.com.
6/29/2005 11:04:28 AM Update Error connecting to server u7.eset.com.
6/29/2005 11:04:26 AM Update Error connecting to server u3.eset.com.
6/29/2005 10:35:01 AM Update Error connecting to server u4.eset.com.
6/29/2005 10:28:28 AM Update Error connecting to server u7.eset.com.
6/29/2005 10:27:40 AM Update Function: gethostbyname, parameters: , return value: 11001
6/29/2005 10:27:40 AM Update Update attempt failed (Server connection failure.)
6/29/2005 10:27:25 AM Update Function: gethostbyname, parameters: , return value: 11001
6/29/2005 10:27:25 AM Update Update attempt failed (Server connection failure.)
6/29/2005 10:27:08 AM Update Function: gethostbyname, parameters: , return value: 11001
6/29/2005 10:27:08 AM Update Update attempt failed (Server connection failure.)
6/29/2005 10:26:52 AM Update Function: gethostbyname, parameters: , return value: 11001
6/29/2005 10:26:52 AM Update Update attempt failed (Server connection failure.)
6/29/2005 10:25:42 AM Update Error connecting to server u7.eset.com.
6/29/2005 10:25:40 AM Update Error connecting to server u4.eset.com.
6/29/2005 8:04:28 AM Update Error connecting to server u1a.eset.com.
6/29/2005 8:04:26 AM Update Error connecting to server u7.eset.com.
6/29/2005 7:04:26 AM Update Error connecting to server u1a.eset.com.

Until about 2 minutes ago, it finally updated correctly.

 

Now a least server 5 is working (because it has only IP).

 

here is how I "fixed" the problem on my update mirror, which was experiencing TONS of failures...

Enter Control Center - click the update options, then setup...
Look in the server drop-down to see if you have one of the Eset servers listed by IP address - see the list above - if you do - select it temporarily instead of:

<Choose Automatically>

... now... click the Ok button and click the "Update Now" button in the control-center... you should see your connection get made, and if you don't already have 1.158, it will download!

hth

Greg

 

NOD just updated for me as well, and no problem getting to there page.

The only thing that I have noticed is they seemed to have taken off the virus signatures from there website.

 

it's kind of odd - on my fileserver running my mirror version, I have an IP only server, which appears to be the u5 ip address, yet on my desktop running the admin version (used to grab CD update files for remote machine cleanup), I don't see that server (it updates from our mirror, so it's not that important) - my guess is that some installers provided it, while others may not have it.

If the IP address version of u5.eset.com is there, selecting it instead of "Choose automatically" will get you through this DNS problem - it's IP is:

82.165.250.33

However, it would be nice if everyone could use a random IP, just so it's sort of balanced a little - for Eset's sanity, and so that everyone can get updates:

See me post above for 4 different IPs of servers that can be used.

regards

Greg

 

Update:

the http://IP.AD.DRE.SS method does NOT work...

So - check your update servers - if you ALREADY have the server listed:

82.165.250.33

Select this one, and you can get updates. It seems the internal servers don't respond on port 80 - if someone knows how to get IPs of regular servers into the settings, perhaps they can publish the information here.

regards

Greg

 

I have noticed that NOD is now defaulting to 82.165.250.33 whenever I attempt to update. I have the update servers set to "choose automatically". Maybe its because of the others not functioning too well?