[RESOLVED] AIS FW - 'Unknown' connections

[lukor]

Hi Mag,
how I see it this seems to be a problem with AIS FW cleaning (deleting) its records about active connections. What you see there are actually connection records that should have been already deleted from the active connections list. I am trying to find some bug in the code and come up with the fix. It does not reproduce here, so it must be depended on the specific situation it is happening in - e.g. all the services and their list of UDP ports they have opened. I have asked the QA team to come up with some configuration setups to reproduce that. Thanks for you analyses.

Lukas.

[MAG]

Thanks Lukas.

I'll try to keep an eye on which applications give rise to this.

As noted above, one is Secunia PSI v1.5.0.2.

[lukor]

Hi mag, I hope I have found a bug causing this improper cleanup of Firewall connections. It should be fixed in the next release. Thanks for pointing that out.

Lukas.

[MAG]

Thanks Lukas.

[avast@@dvantage77.com]

The avast! BSOD is very rare. I am providing avast! tech support to over 4000 organizations world wide. I earned avast! Rising Star 2010. Here is what I have learned on this subject:

I have cured avast! BSODs by using CCleaner registry tool.  CCleaner should be run multiple times until it comes up clean.  This may also be the last step, so keep reading.

A/V software is the most invasive application you will ever have on your computer.  Many times there are leftover pieces of A/V software that cause conflicts (including avast!) I get very aggressive here by scouring the system for these.  Look in Program Files for any directories of previous A/V programs.  Get their removal tools and use them.  Do the same for avast! (if avast!, run the removal tool for every version of avast! that has ever been installed)

Last statement is:  removal tools still leave registry entries.  So I use CCleaner, or manual registry hacks when needed.

Hopes this helps!

J.R. Guthrie
President at Advantage Micro Corporation
Failure Analysis Engineer