Packet responder... Make it a listener on the public interface... Unless it is a server needing to actually SERVE packets you should turn off ANY response. Unfortuneately it is a Registry entry that doesn't exist till you want to create it.

Just get the MicroSoft Baseline Security Analyzer... For all the Bad things said about it... it DOES have some good uses. Just ignore it saying you don;t have patches applied that you know you do. Just be careful, it will make your machine unreachable. But it will still be able to reach others. That bit me in the Butt with the New WebJetAdmin piece of Crap HP is jamming down our throats, no loopback response either... EWWWWW. It's an all or nothing thing.

Just be fore-warned you will not be able to SERVE anything from it. That means no FTP service, no IIS service, NO Sharing.. No Ping response, No anything except being a client.

Not for the faint of heart... Anyways it takes about 12 registry settings to completely lock the packet responder up.

Take a look [link|http://www.fwbuilder.org|HERE].

I know this is Linux based but I know the product works and makes it easy to get things to function the way you want.

You just gotta understand firewall rule progression... or order of processing or rememebr first rules that fits wins.

Only real requirement... Linux with the 2.4x kernel and IPTABLES v1.2.4 or later for debugging and logging to work properly.

Good Luck. Ask advice is free, err... well at least dirty looks are still free.