NOD32 connections

Whilst perusing TCPView (as I often do) I noticed that NOD32 has two seemingly permanent connections. They have only appeared since upgrading to the 2.51.20 version.

I can understand NOD32 connecting for updates and sending statistical data but do these two connections need to be constantly open?

http://tinypic.com/m9y737.jpg

 

Would Marcos or Happy Bytes care to comment on this?

 

I'm assuming the lack of response means there's nothing to worry about? A little clarification would be highly appreciated

 

I have asked for someone from Eset to respond to this thread.

Cheers

 

Here it closes connections properly.
If it didn't, you would hear some bashing

 

Thanks Blackspear

 

No connections left open on my machine either (version 2.51.20 installed). Obvious question: have you re-started your machine?

Bandicoot.

 

Yes, several times since I started this thread.

The connections seem to be a hit and miss affair; sometimes they're there, sometimes they're not. Currently there's none open. I'll keep an eye out from time to time and see if they decide to show up again.

Before I end, please be aware that I in no way think these are surreptitious activities, I was asking out of pure curiosity (as this has never happened with earlier versions).

 

Funny should you ask actually because I did think it strange that it wasn't contained in my server list.

My servers are as shown below.

http://i1.tinypic.com/miozno.jpg

I thought the 82.165.237.14 may in fact be u6.eset.com. I assumed this because of the servers before and after it (2,3,4 etc).

 

You are correct.
u5.eset.com = 82.165.250.33
u6.eset.com = 82.165.237.14

 

I've just found another connection only to an address not on my update server list. The whois information can be seen here.

I'd really, really like some information about this.

http://i1.tinypic.com/mmano3.jpg

 

I get that address for u1a.eset.com.

 

hi! dont worry - the conx are not established any more... the conx state CLOSE_WAIT indicates a passive close. the server just received the first FIN from a client - waiting for an ACK... sorry for my poor english...feel free to correct me...

 

Thanks a lot for your posts FirePost and gnervt; it's nice to have some responses.