ISP/Exchange Question

2003-08-14 Thread Steck, Herb
Has anyone heard of the Dept. of Homeland security putting out an anouncement to ISP's to block TCP/UDP ports 135, 137, 445? "The information transmitted is intended only for the person or entity to which it is addressed and may contain proprietary, confidential and/or legally privileged mater

Re: ISP/Exchange Question

2003-08-14 Thread bscott
On Wed, 13 Aug 2003, at 10:19am, [EMAIL PROTECTED] wrote: >> You do not own your ISP's network, your ISP does. > > And that makes any arbitrary decision they choose to implement acceptable? Acceptable? Perhaps not. You can always switch to another ISP. Of course, if all ISPs are doing the sa

Re: ISP/Exchange Question

2003-08-14 Thread Chris Scharff
> You do not own your ISP's network, your ISP does. And that makes any arbitrary decision they choose to implement acceptable? Please sign up here for the Patriot Service Plan comrade. _ List posting FAQ: http://www.swinc.com/

RE: ISP/Exchange Question

2003-08-14 Thread bscott
On Wed, 13 Aug 2003, at 8:37am, [EMAIL PROTECTED] wrote: > I also think that most good network citizens should be egress blocking > those ports anyway - there are precious few reasons a corporate network > should be allowing egrees traffic on those ports, or for that matter on > most ports. Yah.

RE: ISP/Exchange Question

2003-08-14 Thread Galloway, Dave
notification, no change to the Homeland Security Advisory System (HSAS) is anticipated; the current HSAS level is YELLOW. -Original Message- From: Erik Sojka [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 4:05 PM To: Exchange Discussions Subject: RE: ISP/Exchange Question I

RE: ISP/Exchange Question

2003-08-14 Thread Ed Crowley
Sent: Thursday, August 14, 2003 7:23 AM To: Exchange Discussions Subject: RE: ISP/Exchange Question On Wed, 13 Aug 2003, at 9:24am, [EMAIL PROTECTED] wrote: > Except that your ISP holds you hostage because it "owns" your DNS > entries until you can get them moved somewhere else.

Re: ISP/Exchange Question

2003-08-14 Thread bscott
On Tue, 12 Aug 2003, at 5:44pm, [EMAIL PROTECTED] wrote: > Inbound, Inbound Inbound INBOUND INBOUND CONNECTIONS! > > Fscking Road Runner SSMs decided that "inbound" meant _all_. One man's outbound is somebody else's inbound. Many ISPs are concerned with stopping existing compromises from spre

Re: ISP/Exchange Question

2003-08-14 Thread Chris Scharff
> On Tue, 12 Aug 2003, at 5:44pm, [EMAIL PROTECTED] wrote: >> Inbound, Inbound Inbound INBOUND INBOUND CONNECTIONS! >> >> Fscking Road Runner SSMs decided that "inbound" meant _all_. > > One man's outbound is somebody else's inbound. Right, which is why all firewalls come with default rules set

RE: ISP/Exchange Question

2003-08-14 Thread bscott
On Wed, 13 Aug 2003, at 9:24am, [EMAIL PROTECTED] wrote: > Except that your ISP holds you hostage because it "owns" your DNS entries > until you can get them moved somewhere else. Well, first off, my original point was that Internet access is not the inalienable right that some people seem to th

RE: ISP/Exchange Question

2003-08-14 Thread Martin Blackstone
Over dialup? -Original Message- From: Ed Crowley [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2003 9:58 AM To: Exchange Discussions Subject: RE: ISP/Exchange Question You're going to try that tired argument in every thread until it sticks? Ed Crowley MCSE+Interne

Re: ISP/Exchange Question

2003-08-14 Thread bscott
On Wed, 13 Aug 2003, at 9:41am, [EMAIL PROTECTED] wrote: >> One man's outbound is somebody else's inbound. > > Right, which is why all firewalls come with default rules set to block all > inbound and all outbound traffic. By default, most products on the market are hideously insecure, and shoul

RE: ISP/Exchange Question

2003-08-14 Thread Erik Sojka
iminated a while ago... > -Original Message- > From: Steck, Herb [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 12, 2003 5:53 PM > To: Exchange Discussions > Subject: ISP/Exchange Question > > > Has anyone heard of the Dept. of Homeland security putting > out

RE: ISP/Exchange Question

2003-08-14 Thread Roger Seielstad
. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 12, 2003 7:32 PM > To: Exchange Discussions > Subject: Re: ISP/Exchange Question > > > On Tue

Re: ISP/Exchange Question

2003-08-14 Thread bscott
On Tue, 12 Aug 2003, at 4:52pm, [EMAIL PROTECTED] wrote: > Has anyone heard of the Dept. of Homeland security putting out an > anouncement to ISP's to block TCP/UDP ports 135, 137, 445? The DHS advisory doesn't target ISPs in particular. Many ISPs block 135, 137, 138, 139, and 445. More have

RE: ISP/Exchange Question

2003-08-14 Thread Ed Crowley
m PSTs and Bricked Backups!T -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 8:59 AM To: Exchange Discussions Subject: Re: ISP/Exchange Question On Wed, 13 Aug 2003, at 10:19am, [EMAIL PROTECTED] wrote: >

Re: ISP/Exchange Question

2003-08-14 Thread Chris Scharff
Inbound, Inbound Inbound INBOUND INBOUND CONNECTIONS! Fscking Road Runner SSMs decided that "inbound" meant _all_. It's really unfortunate for the Austin RR group that I live within stal^H^H^H^Hwalking distance. > RECOMMENDATION > Due to the seriousness of the RPC vulnerability, DHS and Microsoft