Originally posted by: Dravic
And as for the comment earlier by someone that the ISP?s are filtering out this content.. That is also not true, and I hope it wasn?t the ISP that told you that. They may block in bound connection from personal servers being set up on common ports (mail 25, web 80) but there is entirely too much valid traffic on those ports to block outright.]
You can find the list of inbound ports blocked by Cox Cable (a major ISP)
on this page (do a Search Support for the term "ports blocked") Note that they block inbound TCP Port 445, which is used by Sasser. Except for Port 25 and 80, Cox blocks these same ports for Business HSI, also.
Ports blocked by Cox Home (and, mostly blocked by Cox Business, too)
25 TCP SMTP Both* SMTP Relays
80 TCP HTTP Inbound Web servers, worms
135 UDP NetBios Both Net Send Spam/Pop-ups, Worms
136-139 UDP, TCP NetBios Both Worms, Network Neighborhood
445 TCP MS-DS/ NetBios Both Worms, Network Neighhood
1433 TCP MS-SQL Inbound Worms, Trojans
1434 UDP MS-SQL Inbound Worms, SQLslammer
1900 UDP MS-DS/ NetBios Both Worms, Network Neighborhood
TCP Subseven Both SubSeven Trojan
Here's a list of ports blocked by Adelphia, another major ISP. The list includes TCP 445.
80/tcp filtered http
135/tcp filtered msrpc
136/tcp filtered profile
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
1720/tcp filtered H.323/Q.931
4444/tcp filtered krb524
5554/tcp filtered unknown
9996/tcp filtered unknown
27374/tcp filtered subseven
This recent UseNet post claims that Comcast is blocking inbound TCP Ports 135-139 and 445, at a minimum.
Another reference says that Comcast blocks:
67, 68, 135, 137, 138, 139, 445, 512, 520, and 1080
And, no, I wouldn't rely on ISP port blocking to protect my network.