Hello,
I would also recommend you tcp 25 as outgoing destination port. If not, you
won't be able to send any e-mail. And I would also recommend you enable
packets going to 53 (dns queries).
This is at least what is needed to keep your network working and your users
slightly happy....
If this is not enough, I would recommend you have a look on the firewall
rejections and see what is the port involved... Or have a small lab with a
Linux to tcpdump and a workstation with a Sharing File Client/server
isolated...
Best regards,
Juan
-----Original Message-----
From: dewt [mailto:[EMAIL PROTECTED]]
Sent: 09 March 2002 23:41
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Stopping File Sharing Programs...
On Friday 08 March 2002 10:45 am, [EMAIL PROTECTED] wrote:
> Hello Everyone,
>
> Our connection to the Internet these days is getting bogged down as
> quite a few users are using P2P progs to share/download files. Initially
> the problem was just one: Kazaa. We were able to stop user access to
> Kazaa by blocking the port 1214. Users currently use a whole set of
> filesharing programs.. Morpheus, Kazaa, Gnutella, Bearshare etc. etc.
> Yes, it is possible to keep track of the programs being used, block each
> one individually etc.
>
> Would there be some kind of a generic way to block such P2P progs?
>
> Regards
> Dhar
You could just go ahead and block everything outgoing but port 80,21 and a
few others, it would kill most, if not all of the filesharing mechanisms,
along with just about every other service but the web and ftp =P, depending
on what this is for it may or may not be a workable solution.
