|
Posted by louise on September 6, 2005, 10:14 pm
If you were Registered and logged in, you could reply and use other advanced thread options
I just started using Nod32 in August.
The event logs say Update - trouble reaching server and they say
this every hour or two on most days.
Eventually, after several entries like this, with many different
servers tried, I get a a kernal update and everything is fine....
Here is an example of the logs:
Time Module Event User
9/6/2005 14:49:18 PM Kernel The virus signature database has
been successfully updated to version 1.1210 (20050906).
9/5/2005 16:39:07 PM Kernel The virus signature database has
been successfully updated to version 1.1209 (20050905).
9/2/2005 16:01:48 PM Kernel The virus signature database has
been successfully updated to version 1.1208 (20050902).
9/1/2005 14:01:37 PM Update Function: gethostbyname,
parameters: , return value: 11001
9/1/2005 14:01:37 PM Update Update attempt failed (Server
connection failure.)
9/1/2005 14:01:35 PM Update Error connecting to server
www.nod32.com.
9/1/2005 14:01:16 PM Update Error connecting to server
u1a.eset.com.
9/1/2005 14:00:57 PM Update Error connecting to server
u4.eset.com.
9/1/2005 14:00:38 PM Update Error connecting to server
u3.eset.com.
9/1/2005 14:00:20 PM Update Error connecting to server
82.165.250.33.
9/1/2005 13:59:57 PM Update Error connecting to server
82.165.237.14.
9/1/2005 13:59:36 PM Update Error connecting to server
u7.eset.com.
9/1/2005 12:58:33 PM Update Function: gethostbyname,
parameters: , return value: 11004
9/1/2005 12:58:33 PM Update Update attempt failed (Server
connection failure.)
9/1/2005 12:58:32 PM Update Error connecting to server
www.nod32.com.
9/1/2005 12:58:30 PM Update Error connecting to server
u4.eset.com.
9/1/2005 12:58:28 PM Update Error connecting to server
82.165.237.14.
9/1/2005 12:58:27 PM Update Error connecting to server
u3.eset.com.
9/1/2005 12:58:25 PM Update Error connecting to server
u1a.eset.com.
9/1/2005 12:58:23 PM Update Error connecting to server
u7.eset.com.
9/1/2005 12:58:23 PM Update Error connecting to server
82.165.250.33.
9/1/2005 11:58:33 AM Update Function: gethostbyname,
parameters: , return value: 11004
9/1/2005 11:58:33 AM Update Update attempt failed (Server
connection failure.)
9/1/2005 11:58:31 AM Update Error connecting to server
www.nod32.com.
9/1/2005 11:58:30 AM Update Error connecting to server
u4.eset.com.
9/1/2005 11:58:28 AM Update Error connecting to server
u3.eset.com.
9/1/2005 11:58:26 AM Update Error connecting to server
82.165.237.14.
9/1/2005 11:58:25 AM Update Error connecting to server
82.165.250.33.
9/1/2005 11:58:23 AM Update Error connecting to server
u1a.eset.com.
9/1/2005 11:58:23 AM Update Error connecting to server
u7.eset.com.
9/1/2005 10:58:33 AM Update Function: gethostbyname,
parameters: , return value: 11004
9/1/2005 10:58:33 AM Update Update attempt failed (Server
connection failure.)
9/1/2005 10:58:31 AM Update Error connecting to server
www.nod32.com.
9/1/2005 10:58:29 AM Update Error connecting to server
u1a.eset.com.
9/1/2005 10:58:28 AM Update Error connecting to server
u4.eset.com.
9/1/2005 10:58:26 AM Update Error connecting to server
u3.eset.com.
9/1/2005 10:58:25 AM Update Error connecting to server
u7.eset.com.
9/1/2005 10:58:23 AM Update Error connecting to server
82.165.250.33.
9/1/2005 10:58:23 AM Update Error connecting to server
82.165.237.14.
8/31/2005 23:38:42 PM Update Function: gethostbyname,
parameters: , return value: 11001
8/31/2005 23:38:42 PM Update Update attempt failed (Server
connection failure.)
8/31/2005 23:38:40 PM Update Error connecting to server
www.nod32.com.
8/31/2005 23:38:36 PM Update Error connecting to server
u4.eset.com.
8/31/2005 23:38:32 PM Update Error connecting to server
u1a.eset.com.
8/31/2005 23:38:28 PM Update Error connecting to server
u3.eset.com.
8/31/2005 23:38:25 PM Update Error connecting to server
82.165.250.33.
8/31/2005 23:38:23 PM Update Error connecting to server
u7.eset.com.
8/31/2005 23:38:21 PM Update Error connecting to server
82.165.237.14.
8/31/2005 14:37:51 PM Kernel The virus signature database has
been successfully updated to version 1.1207 (20050831).
8/31/2005 10:37:51 AM Kernel The virus signature database has
been successfully updated to version 1.1206 (20050831).
8/30/2005 15:56:24 PM Kernel The virus signature database has
been successfully updated to version 1.1205 (20050830).
8/26/2005 21:55:57 PM Update Error connecting to server
u4.eset.com.
8/25/2005 10:30:11 AM Update Function: gethostbyname,
parameters: , return value: 11001
8/25/2005 10:30:11 AM Update Update attempt failed (Server
connection failure.)
8/25/2005 10:30:09 AM Update Error connecting to server
www.nod32.com.
8/25/2005 10:29:50 AM Update Error connecting to server
u3.eset.com.
Eset tech support has not been helpful. They say I shouldn't run a
Linksys NAT router and Sygate - in other words, only one
firewall...
But more importantly, they suggest it's a firewall setting problem
router and they don't support anything but their own software -
regardless of whether it plays well with others or not.
I've checked and Sygate is definitely letting the nod kernal
through and is set accordingly.
Help?
Louise
|
|
Posted by Duane Arnold on September 6, 2005, 10:30 pm
If you were Registered and logged in, you could reply and use other advanced thread options
server.nyc.rr.com:
> I just started using Nod32 in August.
>
> The event logs say Update - trouble reaching server and they say
> this every hour or two on most days.
>
> Eventually, after several entries like this, with many different
> servers tried, I get a a kernal update and everything is fine....
>
So? The machine is getting through and getting the update is it not?
Duane :)
|
|
Posted by louise on September 6, 2005, 10:48 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> server.nyc.rr.com:
>
> > I just started using Nod32 in August.
> >
> > The event logs say Update - trouble reaching server and they say
> > this every hour or two on most days.
> >
> > Eventually, after several entries like this, with many different
> > servers tried, I get a a kernal update and everything is fine....
> >
>
> So? The machine is getting through and getting the update is it not?
>
> Duane :)
>
Yes - but I thought this shouldn't happen and maybe something isn't
working right.
Eset tech did not indicate it was "normal" although they've been
unable to pinpoint the problem. If it's not a problem....then I
wont worry about it, but I'd like to be sure.
Louise
|
|
Posted by Duane Arnold on September 6, 2005, 11:48 pm
If you were Registered and logged in, you could reply and use other advanced thread options
> notme@notme.com says...
>>
>> > I just started using Nod32 in August.
>> >
>> > The event logs say Update - trouble reaching server and they say
>> > this every hour or two on most days.
>> >
>> > Eventually, after several entries like this, with many different
>> > servers tried, I get a a kernal update and everything is fine....
>> >
>>
>> So? The machine is getting through and getting the update is it not?
>>
>> Duane :)
>>
> Yes - but I thought this shouldn't happen and maybe something isn't
> working right.
>
> Eset tech did not indicate it was "normal" although they've been
> unable to pinpoint the problem. If it's not a problem....then I
> wont worry about it, but I'd like to be sure.
>
> Louise
>
There can be connection problems to a site for updates. I have seen it at
times with Eset and other sites that do updates. As long as it connects at
some point to the server and does it, it's OK.
Duane :)
|
|
Posted by someone on September 8, 2005, 12:44 am
If you were Registered and logged in, you could reply and use other advanced thread options
>
> > notme@notme.com says...
> >>
> >> > I just started using Nod32 in August.
> >> >
> >> > The event logs say Update - trouble reaching server and they say
> >> > this every hour or two on most days.
> >> >
> >> > Eventually, after several entries like this, with many different
> >> > servers tried, I get a a kernal update and everything is fine....
> >> >
> >>
> >> So? The machine is getting through and getting the update is it not?
> >>
> >> Duane :)
> >>
> > Yes - but I thought this shouldn't happen and maybe something isn't
> > working right.
> >
> > Eset tech did not indicate it was "normal" although they've been
> > unable to pinpoint the problem. If it's not a problem....then I
> > wont worry about it, but I'd like to be sure.
> >
> > Louise
> >
>
> There can be connection problems to a site for updates. I have seen it at
> times with Eset and other sites that do updates. As long as it connects at
> some point to the server and does it, it's OK.
>
> Duane :)
I've been using NOD for about five years with dialup, never had a problem.
Two nights ago there was an unexpected NOD program component upgrade of
about 1.2 Mb, not just the small virus sig updates, maybe that could be what
could have caused the clag, if everybody was uploading that.
I understand that if you run two AV progs simultaneously you could get a
clash, maybe it's the same with a firewall and an AV prog.
s.
|
| Similar Threads | Posted | | Zone Alarm anti virus scheduler not showing if ran | June 30, 2005, 4:51 am |
| 'Sitehound': Anyone else having trouble getting to use it? | November 1, 2005, 4:07 pm |
| AVG installation trouble | December 6, 2006, 2:56 pm |
| Trouble with Trojans | July 14, 2007, 2:16 pm |
| Trouble with online scans | February 12, 2006, 10:39 am |
| Logs in Mcafee v10? | October 14, 2005, 6:26 pm |
| Kaspersky logs | February 9, 2006, 6:53 pm |
| Trouble with Comodo Anti Virus | June 4, 2006, 7:47 pm |
| trouble downloading Trend db on Multi_AV | July 5, 2008, 8:59 am |
| Best place for hijackthis logs? | June 3, 2005, 5:48 pm |
|
XML site map