Problem with filtering logs?

Help for v3
#1

I may have found a filtering problem with the firewall logs…

I’m using CFP 3.0.14.276 on a Dell laptop running XP with SP2. I haven’t updated the December patches for XP yet, but those should be the only ones I’m behind on.

When I tried to filter the firewall log for a destination port of 1024 I got back a bunch of hits, but they were for a “Code(4)” not port 1024. I attached a screen shot of what I saw.

Also, I got a popup saying “cfplogvw.exe wasn’t a recognized application”. I set it as a Trusted application, and told it to remember my setting, but shouldn’t the CPF log file viewer already be on the safe list?

[attachment deleted by admin]

#2

I’m

using CFP 3.0.14.276 on a Dell laptop running XP with SP2.

I’m using CFP 3.0.14.276 on a Dell Desktop running XP with SP2.

Strange, filter works fine on my system - shows all logs for chosen port or IP.

Also, I got a popup saying "cfplogvw.exe wasn't a recognized application". I set it as a Trusted application, and told it to remember my setting, but shouldn't the CPF log file viewer already be on the safe list?

Already on safe list by default on my CFP - no popups here.

[attachment deleted by admin]

#3

I receive same result. Most likely log entries on your screenshot are related to ICMP protocol. And for this protocol we have type(x) and code(x) instead of port numbers.
Don’t know how to interpret this, though.

#4

For a list of the ICMP type and code parameters see Internet Control Message Protocol (ICMP) Parameters .

#5

No comments from the developers yet? ???