Post reply

Topic Summary

Posted by: LiQuIdRoOm

« on: April 06, 2007, 05:21:58 pm »

Insert Quote

Thanks for replay Ghost; sice today and as I could see, bdnews.exe didn't try anymore. The day bitdefender connected to the blocklist, I started Winmx and repaired the av installation, so it (BD) maybe checked a connection recognized as new, even if bdnews should only be a "new threats advisor" for BD users...or maybe just this could be the reason.

Good sharing ladies and gentlemen

Posted by: GhostShip

« on: April 03, 2007, 11:52:47 pm »

Insert Quote

Cant think myself why anything would be trying to access the blocklist addy except winmx using the patch and if thats the case have no worries.

I,m glad you found out about PG being a pain, we are still wondering why anyone uses it anymore when the list is so bad they are blocking P2P networks, the entire list last time I looked covered 904, million IP's, rather more than the RIAA/MPAA can afford I,m sure.

Posted by: LiQuIdRoOm

« on: April 03, 2007, 04:31:32 pm »

Insert Quote

Hi Guys,

today, looking into the "program alert log" page of zonealarm, I noticed something strange: in some records of the mentioned log was written that the bdnews.exe application tried to connect to internet, this file is the Bitdefender News Application and now the "mistery":
in the fw log I also read that destination IPs were 69.3.33.208 and 64.248.57.132, both on port 53; these IPs have the same DNS name: flooders.block-list.winmxgroup.com.
The log shown 3 connection attempt, the first at 21.04, the second at 22.04, the third at 23.04, all on april 2nd (yesterday); after that, there aren't any others.
Why should Bitdefender try to connect to a DNS that seems related to Winmx ? It's all ok, or should I have to be concerned about ?
Thank a lot in advance.

Good sharing ladies and gentlemen

ps: some months ago I enabled pg2 to use ONLY your allow and block list. Today I completely uninstalled pg2. Now Winmx works fine, and really really better.....