Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Blocking port 135?

  • From: Sean Donelan
  • Date: Sat Aug 02 14:58:30 2003

On Sat, 2 Aug 2003, Jack Bates wrote:
> Many AUP/TOS aggreements have interesting no-server clauses. Blocking
> 135 inbound to those systems would not breach "Internet access" as the
> customer shouldn't have a server running on that port. The lack of <1024
> filtering on such AUP/TOS services is courtesy really. If it's not a
> problem to the network, the ISP generally doesn't care.

The Slammer worm was > 1024.

As someone else pointed out, if you want the ISP to provide you with a
completely "safe" network you will end up with something like Minitel.
ISPs do not control what Microsoft puts in its operating systems, bugs,
features or other things.  ISPs also did not control the introduction
of NCSA Mosaic, Real Streaming, IRC Chat or most of the other things.

Services which require the ISP to "update" their network are always
at a disadvantage, such as Multicast or IPv6.





Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.