Problem with Signature Updates in ESS RC1

[ba1u]

Hi,
Im behind a college proxy . Though I gave the proxy credentials to ESS it always
showing ' failed to update '
http://www.picpeek.com/uploads/a795ed2a23.jpg
This is a fresh install . I havent tried any betas before. the old nod32 av 2.7 was uninstalled via ccleaner??? ???

[ronjor]

Hello ba1u,

Have you restarted your computer lately? Same message?

[ba1u]

-{ Quote: "Hello ba1u,

Have you restarted your computer lately? Same message?" }-
yes restarted still showing the same:(

Is it possible to choose some servers here
http://www.picpeek.com/uploads/c53073e93f.jpg

:'(

[ronjor]

-{ Quote: "Is it possible to choose some servers here" }-No. I don't know how that will look in the future.

It looks like the proxy might be the problem.

You could try an uninstall/reinstall of the beta. http://www.wilderssecurity.com/showpost.php?p=1065245&postcount=2

[ba1u]

-{ Quote: "No. I don't know how that will look in the future.

It looks like the proxy might be the problem.

You could try an uninstall/reinstall of the beta. http://www.wilderssecurity.com/showpost.php?p=1065245&postcount=2" }-


already tried. this is the 4th reinstallation:wacko:

[ronjor]

I would say you have a proxy problem.

Not sure how your college proxy is set up but you might want to check with them. ;)

[ba1u]

-{ Quote: "I would say you have a proxy problem.

Not sure how your college proxy is set up but you might want to check with them. ;)" }-
But the same proxy worked for nod32 2.7 & other softwares.

[ronjor]

Set the firewall to automatic and see if that helps.

[ba1u]

no even now it doesnt work
http://www.picpeek.com/uploads/7fd79de2fb.jpg
I even changed file sharing enabling in advanced firewall settings

[ronjor]

Do you need the firewall under your circumstances? Have you the tried the stand alone version of NOD32 Version 3, RC1?

NOD 2.7 doesn't have a firewall and it worked.

[ba1u]

-{ Quote: "Do you need the firewall under your circumstances? Have you the tried the stand alone version of NOD32 Version 3, RC1?

NOD 2.7 doesn't have a firewall and it worked." }-Didnt try the standalone.
anyways I will wait for few days

[ronjor]

If you discover the cause of your problem, let us know. :)

[Bubba]

-{ Quote: "anyways I will wait for few days" }-I normally do not see any failures in my event log but after noticing a few threads about update problems....I took a look. The failures recorded were more than likely associated with what Blackspear posted about yesterday here (http://www.wilderssecurity.com/showthread.php?p=1085822#post1085822).

-{ Quote: "A large update is being load balanced at the moment, so Trial version users may be pushed back until licensed clients receive their updates." }-A day or 2 wait will probably prove successful.

Bubba

[smith2006]

-{ Quote: "Didnt try the standalone.
anyways I will wait for few days" }-

I am using ESET NOD32 Antivirus V3.0 RC 1 & have problem in updating (it was okay when I used NOD32 V2.70 & ESET NOD32 Antivirus V3.0 Beta 2).

[smith2006]

-{ Quote: "I normally do not see any failures in my event log but after noticing a few threads about update problems....I took a look. The failures recorded were more than likely associated with what Blackspear posted about yesterday here (http://www.wilderssecurity.com/showthread.php?p=1085822#post1085822).

A day or 2 wait will probably prove successful.

Bubba" }-

But I am a licensed client. ::)

Anyway, the technical support is looking into my problem. ;D

[Bubba]

-{ Quote: "But I am a licensed client." }-I am also ::)

-{ Quote: "Anyway, the technical support is looking into my problem." }-The crux of the matter IMHO had to do with the "large update" so missing a few connections is not that big a deal. YMMV ::)

[ba1u]

Hi ,
Thanks for the help. As Bubba said , its a problem with the traffic of upload server. Im a trial version user.ust now it updated to the latest signatures, the update speed was very slow , took 2 hours with a lot of disconnections in between.:)

[Marcos]

There is no trial version of ESS/EAV so the large update wouldn't affect the beta users. What's more, ESS/EAV don't download such large updates.

[hotdogandchips]

I too am still having issues with updating through my transparent proxy, all the logs show is this:

30/09/2007 12:01:28 p.m. Update Bad link to update server. NT AUTHORITY\SYSTEM

The only way I found to get it to update correctly is add an ESET update server to my squid proxy's cache exclusion list and update solely from that server. It's a really strange problem as according to the squid logs, it correctly notes a "cache miss" (ie. the requested file isn't in the proxy cache) and passes the traffic along accordingly.

I should also note that I do no sort of filtering on access to the internet, so there's no chance in my mind of it being a squid malfunction (or unintended function); as everything else works through it something isn't quite right with this latest version's updater (I have NOD32 2.7 on other computers that update just fine on the same network/subnet).

Edit: Cancel all that - it's working perfectly now... you've just gotta make sure that "Choose Automatically" is selected in the "Update" prompt instead of the blank. (Hah! :ouch:)