Error Updating since 20th April 2007

Thanks for responding DDCchik. This issue needs to be fixed ASAP!

What I don't understand is I've used Nod32 for just over a year (I bought a 2 year licence in April 06) and in that time, I could count on 1 hand the amount of times I've had an issue updating the definitions.

Since my original post on the 22nd of April, I've had major issues updating.

When I reviewed the event log recently, I saw update error messages galore & discovered my definitions were 4 days behind.

I can ping the Eset servers until I die from boredom & without any error but I can't update

FWIW, now I can't even download the paid for software from:

http://download1.eset.com/download/win/v2st/ndntenst.exe

All I get in firefox is loading on the tab & a message in the lower left of the screen stating waiting for download1.eset.com.

Not even the request for username & password pops up

I'm at a total loss as to what is going on.

 

I don't know what's going on either. I have the network version of Nod32 on 3 of my Windows machines on my home network. I can't update any of them - 2 XP and 1 Vista.

I've searched the Whirlpool Internode forum and see if there's an Internode issue. I can't find any instance where someone has posted there about it. They have quite a few Nod32 users.

http://www.whirlpool.net.au

Internode staff routinely respond in the forums so I might post and see if there is an issue with Internode.

 

Hey,

I too thought about a thread in Whirlpool within the Internode threads...why not

Like you, I also submitted a search on Nod & Nod32 (both give same results - no issues with updating).

Either people aren't noticing or we are the unlucky few with issues

 

I've posted - so we'll see if there are any known issues. Otherwise I'll email Nod32. I usually get really quick responses from them.

 

Hi,

I haven't had any more issues updating. I am constantly on 121.45.yyy.zzz though, so perhaps this issues is affecting 121.44 only.

 

I'm on a 121.45 IP too.

I really don't want to uninstall/reinstall on 3 machines just to end up with the same issue. I'm really only interested in finding out what the issue is, then I can work on sorting out my end if necessary.

 

Hello,

I'm still having issues updating...as of this morning I've re-booted my router 3 times in an attempt to download the latest definitions.

Still no response from anyone from Eset

Does the silence mean you are treating this as a "not your fault" situation?

Looks like I'll be trying out another AV that will update without fuss until this issue is resolved.

I'm not going to restart my router 50 times just to download a 132kb file beacuse IP ranges are blocked.

 

When this is an issue at the ISP level, and specifically Internodes issue, why would you want to change antivirus programs, that simply doesn't make sense.

Have you actually contacted Internode and talked them them about it, that the issue has returned, and whatever they did last time, to please fix it again permanently this time?

Blackspear.

 

I emailed Eset Australia and they weren't able to help. I think the Whirlpool bogon response is probably close to right answer. Companies that deal in Security related products have to be careful about their own security

I left my modem off for about 30 mins. I know from past experience that I sometimes get the same IP or one very similar if I only leave it off for a short time.

 

Hi DDCchik, have you also contacted Internode, unless they are hearing from their customers that there is a problem and they are the cause, they will never know.

Cheers

 

Hi,

I have emailed Internode helpdesk asking for advice regarding the situation, will post whatever Internode's response is so that other people can use the info too.

I also emailed Nod32 Australia this morning, they feel it's an Internode issue.

DDCchik glad you've got the issue half sorted like myself.

If we are encountering a Bogon Filter issue, then this isn't an Internode issue. It is an issue of website owners using outdated lists that cause access to be blocked.

 

Issue is happening again. My IP has not changed since yesterday, which I must correct something as yesterday I said all was okay.

Yesterday I hit update and it said no new version was necessary. I forgot that the part where it checks for update.ver file is not the problem. Hence, it was okay yesterday as I wasn't connecting to the update server.

I've contacted Internode support as i think the issue might be the transparent proxy. As I can contact download1.eset.com via ssh but not http, I think that's why.

If bogon filtering affected access, we would not be able to contact the server at all (or ping either).

 

I've raised a helpdesk call as well...can we combine them?

Send me a PM if you like and I'll send you the ticket number.

 

I've been having the same issue since April 30th. Internode, Adelaide, 150.101 IP address. I agree with the intercepting proxy theory; if you guys PM me your ticket numbers I'll log another support ticket tomorrow.

 

Has Eset contacted Internode, because this will ultimately affect their business? I am here in the UK, and I am having a separate issue with licence renewal. Are Eset falling apart at the seams?

 

I'd hope not Graphic EQ, as Eset make a damn good AV (best I've ever used).

Our problem can be sourced back to a specific location - South Australia, nearly all of us are using the same ISP; Internode & we all have the same update issue.

At first, bogon filtering was suggested, now it may be a transparent proxy issue.

No one is 120% certain of the cause, could be Internode or it may be Eset.

The only thing we can be certain on is the issue did start around the 20th of April and that its a pain in the butt

 

We'll take this into a thread of it's own and see what issue you are having and what we can do to sort it out for you.

Cheers

 

I agree. NOD32 is the best AV. However, if you're the best and you're not owned by Microsoft, then prepare to be poached or for trouble. The IP address is not just limited to a certain range. On another thread here at https://www.wilderssecurity.com/showthread.php?t=173606 someone else had problems with their IP address. I am not sure if they were in Australia or not.

I am in the UK and am having problems updating (or renewing) my licence. Sure, the 30 day trial runs OK, but every time I go through the renewal procedure, and await the email with instructions, the email never arrives. This is getting beyond a joke now - it is as if they do not want new business!

 

Bogon issues on the 150.101 range are pretty much unheard of; that block's been allocated since 1993. I'm almost certain it's to do with Node's intercepting proxy in SA/NT, and it just needs to be bypassed for the NOD32 update servers.

Updates are working for me this morning so there's no point me logging a ticket now, but next time it happens I'll send them the list of update servers. I've got TJP's ticket number (thanks) to show that it's not just me having an issue.

 

Since I had a ticket already open I just sent a list of the update server IPs so that they can add them to an exception list.

Updates are working today though. So hopefully for us Adelaidians we won't see the problem again.

 

Hi,

Here is the email response I received from Internode about an hour ago:

"We have had another report from a customer who is experiencing issues with NOD32 and the HTTP updates.

We believe it may *possibly* be an issue with our transparent proxy and the fact that NOD32 performs updates through HTTP.

At this point, we have requested that our other client obtains the IP addresses that NOD32 use for the HTTP updates so that we can put in a bypass.

We will contact you once this has been done so that you can perform further testing"

With helpdesk tickets raised by several people, Internode are now fully aware of the situation & hopefully things can go back to normal ASAP

Thanks to Denno, SirLagalot & everyone else who has contributed to fix the issue

 

No problem.. first time i've ever had this problem and I've used NOD32 on Internode for approximately 18 months.

I wish the problem was still apparent so that we could see for certain when they implement the bypass. Oh well!

I would have loved to have known what changed either end to cause the issue. I hate mysteries!

 

Hi,

Internode helpdesk have sent out an email regarding bypassing of their transparent proxy for Nod32. This will be active from 6pm today, 08.05.07.

Internode ask that we test the bypass (not sure how...) and report back any errors to the helpdesk.

FWIW, Nod32 has been updating perfectly for the last 3 days, lets hope the bypass will end the intermittent issues we've had since the 20th of April.

Again thanks to everyone for raising the issue with Internode

Cheers,
Travis

 

Thanks for your persistence with this, and good to see what could be a positive result.

Cheers