Renewed - but NOD won't update

Hey'a

This might be just a problem with the servers being busy, or i have missed a step in my renewal of my NOD32 license?

my yearly license expired 24-Mar-03....i just purchased the 1-yr renewal for my XP-Home and received both comfirmation emails...one with my new UserName and Password. In the email it said if this was just a renewal that i didn't have to re-download the software again, and that i could just put the new UserName and Password in the Control Centre, which i did.

i also rebooted just in case. But when i clicked on the update to bring NOD up to the most recent v.1.387 (2003032, the li'l pop-up that says my NOD is up-to-date came up. my NOD is not up-to-date though. It is still at v.1.385 (20030324). 4 days behind.

Is there something i have missed or is there maybe a waiting period for the new UserName and Password to work? Just to let you know, i have not had any troubles updating NOD before this. That is why i am wondering now.

Thank you for any help, is greatly appreciated.

snap

 

You did everything right! It could be a server glitch. Try again later!


Technodrome

 

works ok here

Ruben

 

Hi!

I also seem to have trouble updating. Nod32 website states that the latest update is 1. 387 (2003032 and my latest update is 1.386. I've tried both www.nod32.com and www.eset.sk servers. The first one claims that I have the current update, the latter gives me "file not found" warning.

Is there a way to manually update the file, an ftp-server perhaps?

Cheers,

Earldor

 

Thanks Technodrome, i am hoping it's just a server glitch too because i don't want to uninstall and reinstall unless i really have to.

Earldor, i justed tried again (both servers) and i get the same messages as you do.

NOD32 system information
Version:         1.385 (20030324)
Installed on:      03/24/2003
Virus database build:   2890
Environment version:   1.047
Last Update attempt:   03/30/03 08:06:42

i looked also for a way to manually update the database, but i couldn't find anything on it either.

Hopefully one of the NOD32 Mods will be in soon?

regards,

snap

 

I cannot update to the 1.387 either ??

NOD32 system information
Version:         1.386 (20030326)
Installed on:      03/26/2003
Virus database build:   2891
Environment version:   1.047
Last Update attempt:   03/30/03 17:18:13

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Common controls version: 5.82.2800
RAM:   383 MB

Diagnostics information
Base module build:   2876

Michael

 

Try removing your username and password, un-checking the "Remember" box, shutting down NOD, re-starting it and then re-inputting the username/password again.

Make especially sure of the case input (upper or lower) of the password when inputting it.

Don't know if it'll help or not, but it's worth a shot if you haven't already tried it. Pete

 

Same problem here. Here is my system info.

NOD32 system information
Version:         1.383 (20030321)
Installed on:      03/21/2003
Virus database build:   2885
Environment version:   1.047
Last Update attempt:   03/30/03 12:03:32

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Common controls version: 5.82.2800
RAM:   511 MB

Diagnostics information
Base module build:   2876

Here is my log:

<03/30/03 12:03:10> Control Center: NOD32 Control Center executed as NT service
<03/30/03 12:03:31> Control Center: Search for new version triggered manually
<03/30/03 12:03:33> Control Center: NOD32 current version installed.

Thanks for any help.

 

Hello again!

I got a reply from the Scandinavian support:

"The current beta-version updates to that version without any problems, but the release version doesn't. I do not know the cause of this, and have contacted the developers regarding this probable problem."

So, no solution yet, but at least the Nod32 crew know about the glitch. Maybe the release of the _new_ Nod32 is nearing, and the servers are being updated.... No? Ok, maybe not.



Cheers,

Earldor

 

Hi,

we are sorry about that. Our provider for www.nod32.com has temporary problems - they will solve it
asap.

You can use our mirror server www.esetsoftware.com where possible - e.g. for updating ( the hint is ment fo all levels of users ):

How to update the NOD32 current version from the www.esetsoftware.com server:

- click on the NOD32 Control Center icon on the Taskbar (small diskette icon with "CC" on it)
- go to "Update" tab
- click on the "Servers" button
- enter "http://www.esetsoftware.com/upd_info" to the "New server:" field
- click "Add server"
- click "Close"
- click on the "Server:" combo beside the "Servers" button
- choose "www.esetsoftware.com"
- Click "Update now"

Updating the NOD32 Beta from the www.esetsoftware.com server:

- click the NOD32 Control Center Icon on the Taskbar (half-white, half-green icon)
- go to Update>Update>Setup
- click on the "Server:" combo beside the "Servers" button
- choose "www.esetsoftware.com"
- click OK
- click "Update now"

We will improve this situation.

Thanks,

jan

 

Hi jan, and thank you!

It took a wee while but i wasn't going to close the update box....and it worked great!

NOD32 system information
Version:      1.389 (20030331)
Installed on:      03/31/2003
Virus database build:   2902
Environment version:   1.047
Last Update attempt:   03/31/03 11:29:45

Thank you very much for your help!

snap

 

Jan
Thak you for this service..
Worked fine and gave me 1.389

Michael

 

OK, thanks for workaround. But, it will be nice to put this solution to your Web.

Also, it will be very helpful that ControlCenter can try multiple servers, when default server is unreachable.

 

Thanks!

I only just noticed that my last update was v.1.386, but changing the update server to http://www.esetsoftware.com/ fixed it for me as well!

 

Hi Gule and all,

as you've probably already discovered - there should be no problems with updating from these servers:

www.nod32.com and

www.esetsoftware.com

for a longer time.

We'd recommend to use www.nod32.com first.

>Also, it will be very helpful that ControlCenter can try multiple servers, when default server is unreachable.

Yes, this will be added - this is a good point and we realized it too.

Thanks,

jan