Re: [fw-wiz] Blocking Kazaa
From: Bruce Smith (bruce_the_loon_at_worldonline.co.za)
To: "Dante Fressone" <FressoneD@officenet.com> Date: Thu, 26 Jun 2003 21:27:07 +0200
I would add my voice to Paul's, setting a proxy up would solve your problem.
We found that we successfully blocked new installations of Kazaa by blocking
TCP and UDP packets going to port 1214 and also, oddly enough, sourcing from
1214 on the inside of our network. That coupled with a blanket port 80 block
has prevented new Kazaa instances from connecting. We've been purging the
existing installations by using the PS Tools package to remotely search and
destroy the Kazaa folder.
----- Original Message -----
From: "Paul Armstrong" <firstname.lastname@example.org>
To: "Dante Fressone" <FressoneD@officenet.com>
Sent: Thursday, June 26, 2003 7:04 AM
Subject: Re: [fw-wiz] Blocking Kazaa
> On Wed, Jun 25, 2003 at 03:20:54PM -0300, Dante Fressone wrote:
> > Hi, I want to block kazaa from my pix fw blocking port 1214 TCP, but it
> > seems like it's using port 80 now,,,,and I can't drop that port because
> > wont work.....
> > Any ideas?
> Use a HTTP proxy such as Squid and only allow traffic to port 80 from the
> This has other advantages such as faster response time for cached objects,
> general filtering (e.g. if your policy says people aren't allowed to
> anything with a .vbs extension) and will save you money if you pay by the
> (or if you pay for pipe size and the traffic reduction means you don't
> such a large pipe).
> firewall-wizards mailing list
firewall-wizards mailing list