NOD32 having trouble "connecting to server"

Hi,

I have NOD32 as my antivirus, no firewall running, and Spy Sweeper as an anti spyware program. I've done a full system scan with both and I've also done it on both when the computer is in safe mode... my OS is Windows XP Home Edition and I am on a Cable Internet connection. My ISP is Comcast.

The problem I am seeing in the Event log is that there is several attempts for NOD32 to try and connect to a server to see if theres any new updates I assume and its having frequent trouble because it keeps saying for the "Event", Error connecting to so and so server... and theres a variety of servers its tried to connect to.

Could anyone help me figure out the problem or anything I can do?

Thanks everyone... appreciate it always.

Gracie

 

Is there any pattern to it? For example, do the error messages come when you first turn the computer on, when you come out of sleep mode, when you first establish or reestablish and internet connection, etc.?

 

Hi, seems like when the computers on... through out the day, that it is on.

 

Can you please post a copy of your logs.

Do you have the update servers as "choose automatically"?

Cheers

 

Hi Blackspear,

Yes, I have it set to Choose automatically... in fact, I have it set up the way your guide shows .

Here is a copy of the Event log:

Time Module Event User
11/10/2005 20:09:23 PM Kernel Statistical information has been sent to Eset.
11/10/2005 20:09:22 PM Kernel Statistical information has been sent to Eset.
11/10/2005 20:09:18 PM Kernel The virus signature database has been successfully updated to version 1.1283 (20051110).
11/10/2005 19:08:39 PM Update Function: gethostbyname, parameters: , return value: 11001
11/10/2005 19:08:39 PM Update Update attempt failed (Server connection failure.)
11/10/2005 19:08:37 PM Update Error connecting to server www.nod32.com.
11/10/2005 19:08:35 PM Update Error connecting to server u4.eset.com.
11/10/2005 19:08:33 PM Update Error connecting to server u3.eset.com.
11/10/2005 19:08:31 PM Update Error connecting to server 82.165.250.33.
11/10/2005 19:08:29 PM Update Error connecting to server u1a.eset.com.
11/10/2005 19:08:28 PM Update Error connecting to server 82.165.237.14.
11/10/2005 12:47:37 PM Kernel Statistical information has been sent to Eset.
11/10/2005 12:47:37 PM Kernel Statistical information has been sent to Eset.
11/10/2005 12:47:36 PM Kernel Statistical information has been sent to Eset.
11/10/2005 11:47:38 AM Update Function: gethostbyname, parameters: , return value: 11001
11/10/2005 11:47:38 AM Update Update attempt failed (Server connection failure.)
11/10/2005 11:47:36 AM Update Error connecting to server www.nod32.com.
11/10/2005 11:47:34 AM Update Error connecting to server u4.eset.com.
11/10/2005 11:47:32 AM Update Error connecting to server u3.eset.com.
11/10/2005 11:47:30 AM Update Error connecting to server u1a.eset.com.
11/10/2005 11:47:27 AM Update Error connecting to server 82.165.250.33.
11/10/2005 11:47:26 AM Update Error connecting to server 82.165.237.14.

Hope this is helpful

 

All the errors occur in two groups, and each group lasts a little over 10 seconds. It looks like there is no internet connection present at 11:47 AM and at 7:08 PM.

However, there is a big gap in the times between 12:47 PM and 7:08 PM. Did you turn off your computer sometime before 1:47 PM, and then turn it back on around 7:08 PM?

 

That is correct. I do turn off my PC at different times when I am done using it and start it back up whenever I want to use it again. Could this be the reason for the problem NOD32 is saying about it not being able to connect to servers.....?

Probably so... yes.

 

It sounds like your TCP/IP networking is slow to start up when you boot your computer. Since TCP/IP is slow to start, NOD32 cannot contact the servers. Chances are, nothing else can access the internet during this period, either.

There can be several reasons for his. On my computer, it is because of my router. My router is set to drop the internet connection (DSL for me) on purpose if it has been idle for a certain amount of time. When I do try to access the internet, there can be a lag time of several seconds for the connection to be reestablished. This is expected for me, so I do not worry about it.

If TCP/IP takes too long to start for no good reason, it could be because of some program (or remnants) interfering with the TCP/IP startup. There are several ways of fixing this. Basically, they involve resetting the Windows TCP/IP configuration. Unfortunately, this may break antivirus/firewall/spyware programs in the process, so you may have to reinstall those programs.

One way to "repair" TCP/IP is the method used by "pcgamingman" in this link: https://www.wilderssecurity.com/showthread.php?t=102416 .

Uninstall NOD32 (and any similar programs).
Reboot.
Go to the Command Prompt and enter the following commands:
netsh int ip reset
netsh winsock reset
Reboot.
Reinstall programs.

Note that this method works only for WinXP SP2 and newer.

Or... you may decide that these messags are something you can live with. It is up to you.

 

Hi alglove,

That actually makes a lot of sense. I have a Linksys USB card that connects me to the Internet and I have a Linksys software program that connects me to the Internet instead of the default Windows program to connect to the Internet.

During this time, it has to connect a few times and sometimes it loses signal strength to the router.. the Linksys program shows this.

So this might be why sometimes I am getting those error messages.

Thanks everyone though for all your help ,

Gracie

 

Yup, that sounds like the reason right there. Your computer is just a little slow to connect to the internet, and the NOD32 update tries to start before it has finished connecting. Nothing to worry about, unless you absolutely cannot wait an hour for the first update.