Discussion in 'NOD32 version 2 Forum' started by jayt, Oct 31, 2005.
Who needs it? Things are running smoothly without it, leave it unplugged.
It was taken off because it need fixing. If they get it working you can't have too many servers, but you can have too few.
It was taken out of the checks - but I noticed a problem with the server status check (or perhaps just the way it's worded)...
It says "responded to our ping requests" - well just because the server is UP - doesn't mean it's responding to requests on the port used for nod32 updates... just be a little wary until Brian_N confirms they're checking that the NOD32 update service is running - not just a network ping...
It's actually a socket connection on port 80 which I'm sure NOD is using too when it checks the update.ver file.
I thought the word 'ping' would make it more understandable, guess I'll have to change that
Thanks for the clarification Brian_N - I figured you would have that handled, but the use of the word ping wasn't 100% indicative of that...
Point taken, I need to improve my english language skills
They just put it back online a few updates ago it seems (u7). Bye bye.
and u1a.eset.com went bye-bye...
But got replaced by u2
I noticed u2 online a while back - but today I've seen some outages on u6...
I'm also wondering why it connects to u12 sometimes.. It's not even on the serverlist.. hmm
u12 is a ThreatSense server for collecting samples detected by AH
Well that pretty much explains it Thanks.
Hmm.. So whats up with 188.8.131.52 refusing connections?
Usually NOD will display a connection error after 10-20 seconds, but now it does it immediately because it's refused.
Just wondering why, thats all
As far as I remember, u6 is mostly for trial users and cracked version users update from it as well. If it's overloaded, paying users will get updates from other servers.
It's still refusing any connection BTW.
I see u6 as down from here too...
u6? hmmm ...
Your not checking that from the standard version are you?
I'm using a mirror locally - but I'd need to check - last time I looked, u6.eset.com (184.108.40.206) was listed in the servers on our admin version which runs the mirror - it's also listed in the servers YOU check on your website, and we also check it using ours:
I just checked the list of servers in my machine here, and 220.127.116.11 is not listed, but I *KNOW* I saw it on ONE of my desktop machines at work yesterday.
Damn, there's like 20 people already [make that 120'ish] checked the server and it's just refusing each and every one - Even in NOD itself.
Cool, finally made your own
yep - same script as: http://status.webyourbusiness.com/ - different config file... I found an ancient php script and hacked it into something useful...
hehe, I know all about that
18.104.22.168 is still messed up..
Separate names with a comma.