full-disclosure - PacBell Internet blocked port 135

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BAY1-DAV65C7JSF90kG00003172@hotmail.com>
From: SecuresDotComs at hotmail.com (SecuresDotComs)
Subject: PacBell Internet blocked port 135

Confirmed. I am no longer able to use Outlook to my Exchange Server.

SDC

----- Original Message ----- 
From: "Jim Race" <caferace@...l.com>
To: <full-disclosure@...ts.netsys.com>
Sent: Tuesday, August 12, 2003 7:48 PM
Subject: [Full-Disclosure] PacBell Internet blocked port 135


> After a pretty relentless pounding, PacBell Internet services looks like 
> they started blocking port 135 right around 10:20 PST this morning.
> 
> I haven't had a single port 135 hit on the firewall since then. Plenty 
> of 137's and 445's, but not a single 135.
> 
> Dunno if the rest of Southwest Bell services did the same. Bueller?
> 
> -jim
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>