[62573] in North American Network Operators' Group
Providers removing blocks on port 135?
daemon@ATHENA.MIT.EDU (Adam Hall)
Fri Sep 19 10:19:57 2003
From: Adam Hall <Adam.Hall@networktelephone.net>
To: "'nanog@nanog.org'" <nanog@nanog.org>
Date: Fri, 19 Sep 2003 09:08:35 -0500
Errors-To: owner-nanog-outgoing@merit.edu
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C37EB7.83B52E70
Content-Type: text/plain
Anyone know anything about prorviders removing ACLs from their routers to
allow ports 135/445/4444 back into their network? Curious only because
customers are calling in saying that Verizon, Cox, Bellsouth, and DSL.net
are doing so and seem to have a big problem with the fact that we're
hesitent follow their lead.
Adam
------_=_NextPart_001_01C37EB7.83B52E70
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Providers removing blocks on port 135?</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Anyone know anything about prorviders removing ACLs =
from their routers to allow ports 135/445/4444 back into their =
network? Curious only because customers are calling in saying =
that Verizon, Cox, Bellsouth, and DSL.net are doing so and seem to have =
a big problem with the fact that we're hesitent follow their =
lead.</FONT></P>
<P><FONT SIZE=3D2>Adam</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C37EB7.83B52E70--
