Newbie to NOD32 2.5 AV

[cutehomoboi]

Hi all,

I started using NOD32 last night. I have been following the guide HERE (http://www.wilderssecurity.com/showthread.php?t=37509), so have happily configured the settings.

But I have got a little question to ask.

I have been looking in the 'event log' of my NOD32, and have noticed a few things that is concerning me. I can see the following messages in the 'event log:'

{QUOTE-> Time Module Event User
12/12/2005 08:07:04 Update Error connecting to server 213.215.116.226.
Time Module Event User
12/12/2005 07:06:17 Update Function: gethostbyname, parameters: , return value: 11001
Time Module Event User
12/12/2005 07:06:14 Update Error connecting to server www.nod32.com.
12/12/2005 07:06:12 Update Error connecting to server 213.215.116.226.
12/12/2005 07:06:05 Update Error connecting to server u3.eset.com.
12/12/2005 07:06:03 Update Error connecting to server u4.eset.com.
12/12/2005 07:06:02 Update Error connecting to server u2.eset.com.
11/12/2005 23:02:21 Update Function: gethostbyname, parameters: , return value: 11001
Time Module Event User
11/12/2005 21:01:49 Update Error connecting to server www.nod32.com.
11/12/2005 21:01:47 Update Error connecting to server 213.215.116.226.
11/12/2005 21:01:45 Update Error connecting to server u4.eset.com.
11/12/2005 21:01:43 Update Error connecting to server u1a.eset.com.
11/12/2005 21:01:42 Update Error connecting to server u3.eset.com. <-QUOTE}

Not really sure why I am getting these messages, as NOD32 seems to be running fine. I have checked the virus signature, and can see it was last updated yesterday (1.1318 ). I have clicked on the update button, and I am told that my version of NOD32 is upto date.

So I am don't know why there are so many error messages in my event log. Can anyone assist?

Thanks in advance.

[cupez80]

that msg appears if nod32 cant connect to update server. its normal cause sometimes server traffic is full.

[cutehomoboi]

{QUOTE-> that msg appears if nod32 cant connect to update server. its normal cause sometimes server traffic is full. <-QUOTE}

So it's nothing to really worry about then?

[Blackspear]

{QUOTE-> So it's nothing to really worry about then? <-QUOTE}Do you by chance have a Wireless Connection?

Cheers ;D

[cutehomoboi]

{QUOTE-> Do you by chance have a Wireless Connection?

Cheers ;D <-QUOTE}

No I don't.

I have got a 1 Meg connection, via a Speed Touch ASDL USD Modem.

Will this cause problems? :-\

[Marcos]

Ain't your modem connected via USB? This would explain it as you first need to dial up a connection when you want to access the Internet.

[cutehomoboi]

{QUOTE-> Ain't your modem connected via USB? This would explain it as you first need to dial up a connection when you want to access the Internet. <-QUOTE}

Yes the modem is connected via a USB port.

[Blackspear]

Are you showing successful updates in your logs?

Cheers ;D

[cutehomoboi]

{QUOTE-> Are you showing successful updates in your logs?

Cheers ;D <-QUOTE}

Here is a copy of my full log:

{QUOTE-> Time Module Event User
12/12/2005 08:07:04 Update Error connecting to server 213.215.116.226.
12/12/2005 07:46:47 Kernel Statistical information has been sent to Eset.
12/12/2005 07:06:17 Update Function: gethostbyname, parameters: , return value: 11001
12/12/2005 07:06:17 Update Update attempt failed (Server connection failure.)
12/12/2005 07:06:14 Update Error connecting to server www.nod32.com.
12/12/2005 07:06:12 Update Error connecting to server 213.215.116.226.
12/12/2005 07:06:05 Update Error connecting to server u3.eset.com.
12/12/2005 07:06:03 Update Error connecting to server u4.eset.com.
12/12/2005 07:06:02 Update Error connecting to server u2.eset.com.
11/12/2005 23:02:21 Update Function: gethostbyname, parameters: , return value: 11001
11/12/2005 23:02:21 Update Update attempt failed (Server connection failure.)
11/12/2005 23:02:20 Update Error connecting to server www.nod32.com.
11/12/2005 23:02:18 Update Error connecting to server u3.eset.com.
11/12/2005 23:02:16 Update Error connecting to server 213.215.116.226.
11/12/2005 23:02:15 Update Error connecting to server u2.eset.com.
11/12/2005 23:02:14 Update Error connecting to server u4.eset.com.
11/12/2005 21:32:04 Update Error connecting to server 213.215.116.226.
11/12/2005 21:03:49 Kernel The virus signature database has been successfully updated to version 1.1318 (20051211).
11/12/2005 21:01:52 Update Function: gethostbyname, parameters: , return value: 11001
11/12/2005 21:01:52 Update Update attempt failed (Server connection failure.)
11/12/2005 21:01:49 Update Error connecting to server www.nod32.com.
11/12/2005 21:01:47 Update Error connecting to server 213.215.116.226.
11/12/2005 21:01:45 Update Error connecting to server u4.eset.com.
11/12/2005 21:01:43 Update Error connecting to server u1a.eset.com.
11/12/2005 21:01:42 Update Error connecting to server u3.eset.com <-QUOTE}

My current virus signature is: 1.1318 (20051211) - is this the most upto date signature?

:P

[cupez80]

as your connection use dialup then nod32 unable to connect server before you internet connection available. you can change nod32 update setting to dial-up.

[Blackspear]

{QUOTE-> My current virus signature is: 1.1318 (20051211) - is this the most upto date signature? <-QUOTE}Indeed it is, you have nothing to worry about.

Cheers ;D

[cutehomoboi]

{QUOTE-> as your connection use dialup then nod32 unable to connect server before you internet connection available. you can change nod32 update setting to dial-up. <-QUOTE}

Ok, I have done this:

Clicked update > Setup > Advanced > Within the Internet Connection section > Changed from LAN/fixed line to Dial-up > Clicked ok > Clicked ok again...

Should this stop these errors in the event log?

[Blackspear]

{QUOTE-> Should this stop these errors in the event log? <-QUOTE}Probably ??? ;) ;D

So long as you are receiving updates I wouldn't be concerned...

Cheers ;D

[cutehomoboi]

{QUOTE-> Probably ??? ;) ;D

So long as you are receiving updates I wouldn't be concerned...

Cheers ;D <-QUOTE}

Excellent stuff... ;)

[noduser]

I had a lot of connection to server errors when I was using the trial version. Since I purchased NOD32 a couple of weeks ago I have only had 3 connection failures with the paid version (set to check for updates every hour). For some reason there must be a difference in the servers used for the paid vs. trial version.

[Blackspear]

{QUOTE-> For some reason there must be a difference in the servers used for the paid vs. trial version. <-QUOTE}Paying clients take precedence over Trial version customers when updates are large... This has been discussed somewhere on the forum a while back.

Cheers ;D