WallWatcher - AVP conflict

  • Thread starter Thread starter goofy
  • Start date Start date
G

goofy

not possible to send a report to (e-mail address removed) I have to try to
get an answer in a newsgroup.
Hopes that this is the wright newsgroup.


Using WallWatcher v2.2.1701 for a while I got recently serious problems with
my virusscanner.
After downloading the latest virusdefinitions AVP wants to kill the running
WallWatcher because it has a backdoor named :
Heuristic/Backdoor.Win32.VB5.
Both programms ( AVP and WW ) are startup programms on my PC and the AVP
programm don't allow WallWatcher to startup. If I say continue with the
startup of WW the AVP programm refuses that. I had to disable one of the two
conflicting programms to get my PC up and running. I had to deactivate WW
because working without a virusscanner is not really recommended :-).

I'm using the virusscanner from http://www.antivir.de/de/ version :

AntiVir®/9x Personal Edition v6.25.00.03 vom 11.05.2004
VDF-Datei v6.25.0.70 (0) vom 19.05.2004

but also the earlier VDF version 6.25.0.69 don't like WW to startup.

Downloaded and installed WW v2.2.18 but that doesn't change anything.

The AVP programm find nothing wrong with a sleeping WW (the programm in a
directory) but if I want to start WW the AVP programm makes that impossible.
 
1) You may send reports to me at "(e-mail address removed)", and I
normally reply; but perhaps you literally "can't" send one, in which
case, we'll just have to communicate through this forum.

2) most firewalls block certain aspects of WallWatcher's activities,
as they should. However, all the ones I've used or heard about have
provision for letting you tell them to allow specific programs to use
the Internet. Often, there's a "configuration" section for this
purpose. In the case of WallWatcher, if you are not using the "email
alerts" feature, WW only receives messages from the Router, but never
sends anything. So, it's sufficient to tell the firewall that the
Router's address is allowed to send messages to WallWatcher on port
162 or 514, depending on which kind of router you are using. You
don't have to tell it to allow WallWatcher to reply (because it
doesn't).

-Dan Tseng (WallWatcher author)

* * * * *
 
Back
Top