Update does not complete and starts again

[Johnoz]

I noticed unusual modem over the last few days. I eventually tracked it to NOD32 2.7 trying to update.

NOD32 was trying to update engine1.nup. It will download to the point of 1722kB of the file size 1733kB (99%) and then stall.

It then waits nearly a minute and does exactly the same again. Then another minute and tries again. (I hate to think what has happened to my download limit)

Any assistance would be appreciated
thanks
John

Win XP SP2

[Johnoz]

Further to the above problem I followed Blackspear's advice to Nameless.
http://www.wilderssecurity.com/showthread.php?t=186682

I now have an absolutely identical problem to Nameless - that is I now get to 76% of the 7.7mB download of engine0.nup and the download stalls, waits then goes to another server - and repeats the download to the 76% point - over and over.

Nameless was unsure how he solved the problem.

Can anyone assist.

thanks

John

[webyourbusiness]

did you try repairing winsock?

http://support.microsoft.com/kb/811259

[Johnoz]

-{ Quote: "did you try repairing winsock?

http://support.microsoft.com/kb/811259" }-

Thank you WebYourBusiness,

I followed the "Guided Help to determine and recover from Winsock2 corruption" on this KB and found no problems.

Further thoughts would be appreciated.

with thanks

[Blackspear]

Hi there, this error occurs where there is Windows corruption, please complete the following:

Download and SAVE WinsockXPfix from here: http://www.spychecker.com/download/download_winsockxpfix.html

For Windows XP:

Click on Start
Click on Run
Type in cmd
Click on OK
Type in netsh winsock reset
(Please note there are spaces between the netsh and winsock and reset)

Press ENTER
Restart your computer.

If the above does not work due to an issue with Windows, run WinsockXPfix that you downloaded above and follow the prompts.


For Windows VISTA

1. Click Start. In the Start Search dialog box, type: cmd, and right-click cmd.
2. Click Run as administrator.
3. Type: netsh winsock reset (and then press the ENTER key).
4. Type: Exit and press ENTER.
5. Restart the computer

AFTER the above please go to the NOD32 Control Centre

Click on IMON

Click on Start and restart IMON.

Then reboot your PC.



Please also check for missing or damaged files within Windows:

1. From the Start menu, select Run.
2. In the Open field, type sfc /scannow (Note: There is a space between sfc and /scannow)
3. Select the OK button.
4. Follow the prompts throughout the System File Checker process.
5. Reboot the computer when System File Checker completes.

Cheers ;D

[Johnoz]

Thank you Blackspear

I have tried these to no avail -

netsh winsock reset
then
sfc /scannow
then, as I was a little wary of the behaviour of WinsockXPfix I did a full NOD32 reinstall.
this did not work so bit the bullet and ran WinsockXPfix
still no good - downloads 69% of 8401Kb, stops and then retries.

And I re ran "Guided Help to determine and recover from Winsock2 corruption" from http://support.microsoft.com/kb/811259 telling it that Winsock was corrupted. It was rebuilt - but did not help.

One strange bit of behaviour. I run 512kb broadband. The speed shown during the download is around the usual 50k. But each time when the download passes about 50% the download speed shown by NOD32 drops to low levels (moving around in the range of about 1k to 10k) - but my eye says the rate of download has not altered right up to the 69%.



Anyway, still not out of the woods.

cheers

[Blackspear]

Please also check for missing or damaged files within Windows:

1. From the Start menu, select Run.
2. In the Open field, type sfc /scannow (Note: There is a space between sfc and /scannow)
3. Select the OK button.
4. Follow the prompts throughout the System File Checker process.
5. Reboot the computer when System File Checker completes.

Cheers ;D

[Johnoz]

Thanks again Blackspear - have already done that.

This is getting tricky!

[Blackspear]

You are hurting my head :blink: :blink: :blink:

Please check the Registry Permissions:

Click on Start
Click on Run
Type in regedit
Click on OK
Right Click on HKEY_LOCAL_MACHINE
Click on Permissions
Click on Advanced
On the “Permissions” tab and make sure at the bottom of this window the following lines are ticked:

• Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here.

• Replace permission entries on all child objects with entries shown here that apply to child objects.

After the above, please try reinstalling a FRESH copy of NOD32.

Cheers ;D

[Johnoz]

Hello Blackspear

I appreciate your help.

The following is done.

• Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here.
was ticked

• Replace permission entries on all child objects with entries shown here that apply to child objects.
was not ticked - done

then
restarted
downloaded fresh NOD32
removed installed NOD 32 through add/remove programs and also the ESET directory in Program Files
installed the new NOD32 - no problems

still no joy......
and my head hurts too

[Blackspear]

Have you cleaned out your temp folders?

Cheers ;D

[Johnoz]

-{ Quote: "Have you cleaned out your temp folders?

Cheers ;D" }-

Yes,
Disk cleanup followed by defrag.

Desperately clutching at straws here, but the problem has approximately coincided with a speed change from 256k to 512K with my ISP two or so days ago.

cheers

[webyourbusiness]

do you have "<Choose Automatically>" selected in the list of update servers, or are you using one in particular?

[sangam]

just a thought, i had a problem on a client machine not updating, each time, it did, it failed, & then restarted the updation. i could finally resolve the issue after i corrected the proxy setting, or the dial up account... i really do not remember clearly, it was several months ago :-\ .

[Johnoz]

-{ Quote: "do you have "<Choose Automatically>" selected in the list of update servers, or are you using one in particular?" }-
Thanks,
Yes, I do. I can see the server name change at each attempted download.

Thanks Sangam,
I will play around with the proxy server settings, but I am pretty certain we don't use one. On the latest install I let NOD32 decide based on what IE used.

thanks for the help

[NOD32 user]

-{ Quote: "... I am pretty certain we don't use one ...." }-Hi Johnoz,

Please visit the following URL for detailed information on any transparent proxy your ISP may have installed http://www.lagado.com/proxy-test

If it shows none then please confirm by using http://www.lagado.com/tools/cache-test and following the instructions there.

Cheers :)

[Johnoz]

-{ Quote: "Hi Johnoz,

Please visit the following URL for detailed information on any transparent proxy your ISP may have installed http://www.lagado.com/proxy-test

If it shows none then please confirm by using http://www.lagado.com/tools/cache-test and following the instructions there.

Cheers :)" }-

Thank you NOD32 user.
Both tests indicate there is no proxy.

[ronjor]

Seems to be a connection problem of some sort. Pick random servers from the list of servers in the program, run tracert, and see where the connection goes bad.

[NOD32 user]

-{ Quote: "Thank you NOD32 user.
Both tests indicate there is no proxy." }-OK Johnoz, please continue with Blackspear - he is very experienced with NOD32 and has several methods of direct communication with ESET to that end.

Cheers :)

[sangam]

is it that there are two internet accounts configured, one that works for the network, another only for your pc ? if so, try using the local PC internet account. does that help ?

[Johnoz]

-{ Quote: "Seems to be a connection problem of some sort. Pick random servers from the list of servers in the program, run tracert, and see where the connection goes bad." }-
Thanks Ronjor,
I can Ping u32.eset.com (and many other sites) but Tracert will not get beyond my modem IP address 192.168.1.1. In fact cannot Tracert to any site. (including with the Firewall off)
Just to add -
I can download all other files normally except the update (including NOD32 from ESET)

Hi Sangam,
I have a stand alone PC connected to an ADSL modem.

Again thanks to all for the advice.

[ronjor]

Bypass your router, making sure you have a firewall in place, Windows firewall is handy, and see if you can tracert to the servers.

It sounds like your modem (does it include a firewall?) may have something to do with your problem.

[Blackspear]

-{ Quote: "...please continue with Blackspear - he is very experienced with NOD32 and has several methods of direct communication with ESET to that end." }-I'm still asking around, as I have run out of ideas.

Cheers ;D

[Johnoz]

-{ Quote: "I'm still asking around, as I have run out of ideas.

Cheers ;D" }-
Thanks Blackspear and NOD32,
The only thing I can firm up on a bit is the peculiar event associated with download speed.
Independent of server in use and quite repeatably, download proceeds at max speed for 512k and then at exactly 50% it stops momentarily and then continues until 69%. Ive done it enough times........
This may of course be normal.

thanks again

[Marcos]

You might want to try installing ESS/EAV which uses very small updates. It should help if you experience problems downloading larger files (the updater requires a continual data flow, otherwise the update may not complete).

[Johnoz]

-{ Quote: "You might want to try installing ESS/EAV which uses very small updates..... " }-
Thanks Marcos,
Could you help me find ESS/EAV. I can't see it on the Eset site.

thanks

[Blackspear]

-{ Quote: "...Could you help me find ESS/EAV...." }-Remember this is BETA Software, even though it may be very stable:

http://www.wilderssecurity.com/showthread.php?t=186164

Cheers ;D

[Johnoz]

-{ Quote: "Remember this is BETA Software, even though it may be very stable:

Cheers ;D" }-
Thanks Blackspear,
I see this is V3.0 beta.
I assume that I download "ESET NOD32 Antivirus RC1" from the page you pointed me at then remove V2.7 and install V3.0
thanks again

[Blackspear]

-{ Quote: "I assume that I download "ESET NOD32 Antivirus RC1" from the page you pointed me at then remove V2.7 and install V3.0" }-Correct.

AGAIN, the Warning that this is BETA Software.

Cheers ;D

[Johnoz]

OK - done

Version 3 beta 3.0.414.0 loaded and working. Updated in a flash to version 2565 20071002 which looks current.

Ran a full scan over the drives - no problems. So far so good.

Thank you to the Moderators and Forum Members for their help and support through my trials.

I wonder if we will ever have the luxury of knowing what was going on.

cheers

[Philippe_FR22]

Johnoz,
Please can you be more explicit regarding your configuration ?
1) Do you use a personal firewall ?
If yes : could you deactivate temporarly and then try again to update ?
please could you check configuration

2) Can you check windows XP firewall and do the same ?

3) Can you check your ADSL gateway (firewall rules ?)

Regards

[Johnoz]

-{ Quote: "Johnoz,
Please can you be more explicit regarding your configuration ?
1) Do you use a personal firewall ?
If yes : could you deactivate temporarly and then try again to update ?
please could you check configuration

2) Can you check windows XP firewall and do the same ?

3) Can you check your ADSL gateway (firewall rules ?)

Regards" }-
Hi Phillipe,
I have now changed to Ver 3 beta and this seems to be working. Started this morning and updated no problems.

For the record, I use

Win XP SP2
ZoneAlarm firewall - free version
Netcomm NB3 ADSL modem - a simple single port modem.

I tried disabling ZoneAlarm ( but not removing) - no change
I did not try any changes with XP firewall.
I have made no changes to the modem's setup since installation and will need to get out the book to check out it's firewall rules.

Thank you for the help.

[Ideafix]

Ok, it seems that there's more going on, since I experienced exactly the same problem today.
Download of updates goes fine at a steady 100-120 KB/s till it hits 50%. Then it goes down to 2-10 KB/s till it reaches 69%, a point at which it stops, switches server and does it all over again. This has happened some 20 times in a row.

Manual updating does exactly the same.
I followed every step here and I still get stuck at 69%.

Only similar situation I can figure out between my system and that of Johnoz is that my ISP won't allow traces to my machine. I use an Anydata CDMA Radiolink modem (Wireless Radio ISP) and I have noticed that trace sites such as Visualware or Dslreports can't trace back to my machine, not even to my ISP. In fact the trace ends unexpectedy some 3-4 hops away from my ISP. I assume some manner of firewalling is in place or that the wireless nature of my ISP may have something to do with it...

BTW, I'm running Vista ultimate and no other security software other than windows firewall and windows defender.

[Blackspear]

-{ Quote: "Ok, it seems that there's more going on, since I experienced exactly the same problem today." }-Please try the following:

Check that the below files exist:

C Drive> Windows> Temp

C Drive> Documents and Settings> (User Name) XXXXXX> Local Settings> Temp

Do the "Temp and TMP" folders exist in "Environmental Variables" when you right click on My Computer as per the screenshots found in this link? http://www.wilderssecurity.com/showthread.php?p=764434#post764434

When you then navigate to the folders mentioned in "Environmental Variables" are they actually there?

Sometimes the only method is to delete and reinstall the Temp folders.

You can also try running this file http://www.nod32.it/getfile.php?tool=settmp it will set both the user and system TEMP/TMP variables to c:\windows\temp. Just make sure the folder exists.

With Vista, you can also try turning off UAC in the Vista Control Panel.



If after the above the issue remains, can you also try the BETA:

Remember this is BETA Software, even though it may be very stable:

http://www.wilderssecurity.com/showthread.php?t=186164

If this resolves it for you as well, then it points to an issue with v2.7

Cheers ;D

[Ideafix]

Yes, I ried all that to no avail, but I managed to narrow down the probabilities. It defenitely has something to do with my ISP. Since I'm on a laptop, I tried updating from friend's houses and public access Internet places.
The conclusion I came to was that this very same laptop, has no problems whatsoever updating from "standard" ADSL ISPs, but fails to do so at 69% whenever my ISP is used. I tried this at 4 different friend's houses who use the same CDMA ISP as me and NOD failed at 69% at each of their houses.
However, on standard "per cable" ADSL ISPs, it had no problem updating.
I can't say that the problem could be related to the need of NOD update to have "a continuous flow of data", as an ESET person here stated, since I get a very continuous and fast data stream rated with a 96% QOS by Visualware.
The only strange thing about my ISP is (as I stated) that you can't do traces to our machines, so my wild guess would be that NOD 2.70.39 has difficulty updating on machines that can't be traced.
This may be an issue, but I don't complain too much, since I can manage to update at work or McDonalds... hehe