Windows XP pro Packet Filtering, want to block kazaa

[FSAA]

Hi all,

I have a small LAN and I have WinXP Pro acting as a router/gateway to the
WAN.
One of my user is downloading from Kazaa like mad and I wanted to ban kazaa
traffic to his IP address.
I have made some IPSec settings but that doesn't help, because IPSec only
blocks a certain port, but kazaa can just use any random port to download,
even port 80.
I want a packet filtering software that sniff the incomming packets and
check in their headers to see if they belong to kazaa and drop them.

Is there any good (may be free??) tools to do it, I spent hours on google
researching this but most are expensive, or just plain packet sniffers but
can't drop packets.

Thanks

 

[Carey Frisch [MVP]]

Doug's Windows XP Security Console
http://www.dougknox.com/xp/utils/xp_securityconsole.htm

[Courtesy of MS-MVP Doug Knox]

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

----------------------------------------------------------------------------------------------


| Hi all,
|
| I have a small LAN and I have WinXP Pro acting as a router/gateway to the
| WAN.
| One of my user is downloading from Kazaa like mad and I wanted to ban kazaa
| traffic to his IP address.
| I have made some IPSec settings but that doesn't help, because IPSec only
| blocks a certain port, but kazaa can just use any random port to download,
| even port 80.
| I want a packet filtering software that sniff the incomming packets and
| check in their headers to see if they belong to kazaa and drop them.
|
| Is there any good (may be free??) tools to do it, I spent hours on google
| researching this but most are expensive, or just plain packet sniffers but
| can't drop packets.
|
| Thanks

 

[jaimin]

Actually, you can use Browse Control to block KazaA.

You can download this from: www.browsecontrol.com

As you say KazAa can port hop and so no use just blocking any ports,
Browse Control will actually stop Kazaa from being launched at the
client end...even if the user renames it to something else, Browse
Control looks at the internal name of the application so he cannot get
around this!

Regards
Divyesh