-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Hal White
Sent: Friday, September 29, 2000 11:55 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Napster Question
Blocking these IP addresses will only block users from accessing the =
main
napster servers
D]
On Tue, 3 Oct 2000, Jeff Kell wrote:
Date: Tue, 03 Oct 2000 22:23:10 -0400
From: Jeff Kell [EMAIL PROTECTED]
To: Tom Pruneau [EMAIL PROTECTED]
Cc: "Dorroh, Hunter" [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Napster Question
Tom Pruneau wrote:
How about just
[mailto:[EMAIL PROTECTED]]
Sent: Friday, September 29, 2000 3:49 PM
To: Hal White; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Napster Question
The list went through this several times already.
Blocking ports , , , is useless.. since Beta6, Napster has
been able to work on ANY
I think the key is to allow outbound packets to the Napster servers and
other PCs on the Internet, but not allowing external PCs to establish a
connection to your users' PCs. Find out the ports that a PC running Napster
is listening on, and then block those at the FW. A PIX should do this by
ge-
From: Dorroh, Hunter [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 03, 2000 12:17 AM
To: [EMAIL PROTECTED]
Subject: RE: Napster Question
Hello everyone,
I searched through the archives and found lots of good information on
blocking but I did not see anything on the possibili
int FW-1) so I cannot tell you the
syntax, but the logic is the same for every FW. Checkpoint call it Content
Security.
Good luck.
-Original Message-
From: Dorroh, Hunter [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 03, 2000 12:17 AM
To: [EMAIL PROTECTED]
Subject: RE: Napster Question
me Napster!)
Wait, no... that's what I wish we could do. Really we just block the
napster.com Ip's.
Good luck
[EMAIL PROTECTED]
Original Message Follows
From: "Dorroh, Hunter" [EMAIL PROTECTED]
To: 'Ejay Hire' [EMAIL PROTECTED]
Subject: RE: Napster Question
Date: Tue, 3 Oct
Tom Pruneau wrote:
How about just permitting established connections. That should do
it, only allowing responses to you requests
You're missing the point. Napster can work around much of this. Scour
certainly can (it has "push" capability, using an established
connection), and Scour fully
Tom Pruneau wrote:
How about just permitting established connections. That should do
it, only allowing responses to you requests
You're missing the point. Napster can work around much of this. Scour
certainly can (it has "push" capability, using an established
connection), and Scour fully
yelling.
- Original Message -
From: Jeff Kell [EMAIL PROTECTED]
To: Tom Pruneau [EMAIL PROTECTED]
Cc: Dorroh, Hunter [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, October 03, 2000 7:20 PM
Subject: Re: Napster Question
Tom Pruneau wrote:
How about just permitting established
e
napster.
From: "Fowler, Joey" [EMAIL PROTECTED]
Reply-To: "Fowler, Joey" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: Napster Question
Date: Fri, 29 Sep 2000 13:15:19 -0400
If you search the archives it has some info on this, but I just implemented
it this mornin
? I was thinking
this might limit a company's legal exposure.
Thanks,
Hunter
-Original Message-
From: Trevor Corness, CCNA [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 29, 2000 3:49 PM
To: Hal White; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Napster Question
The list went
Title: RE: Napster Question
If you search the archives it has some info on this, but I just implemented it this morning and it seems to working here. If you are using PIX firewall (or any other) create an access list using the outbound and apply commands to block the following addresses
I found my documentation and of course my memory had failed me. The ports
for napster are ,6699,,9009. I think blocking these will disable
napster.
From: "Fowler, Joey" [EMAIL PROTECTED]
Reply-To: "Fowler, Joey" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject:
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Hal White
Sent: Friday, September 29, 2000 11:55 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Napster Question
Blocking these IP addresses will only block users from accessing the main
napster servers
"Trevor Corness, CCNA" wrote:
The list went through this several times already.
Blocking ports , , , is useless.. since Beta6, Napster has
been able to work on ANY port, INCLUDING 80.. so to kill Napster, you would
have to kill all access to http/tcp80.. NOT good.
16 matches
Mail list logo