My ISP finally got on the ball......

sean2002

Golden Member
Apr 9, 2001
1,538
0
0
My isp (Cox Express) has finally setup filters to block traffic to TCP/UDP port 137-139 and UDP port 135. I was getting thousands oh hits to 137 everyday, it's about time they did something right
 

Yomicron

Golden Member
Mar 5, 2002
1,735
1
81
hmmm... Cox is my ISP and in my area (Tucson, Arizona) they started blocking those ports at least a month or two ago.
 

Heisenberg

Lifer
Dec 21, 2001
10,621
1
0
I still can't believe people have broadband without some sort of hardware/dedicated firewall. That's just asking for trouble.
 

Mucman

Diamond Member
Oct 10, 1999
7,246
1
0
That sucks... I would prefer an ISP that doesn't block anything and lets me handle it the way I want to.

Losing freedom sucks.
 

dmcowen674

No Lifer
Oct 13, 1999
54,889
47
91
www.alienbabeltech.com
Originally posted by: Mucman
That sucks... I would prefer an ISP that doesn't block anything and lets me handle it the way I want to.

Losing freedom sucks.

True.

You are paying for full Internet access. The ISP should not turn off anything. Bellsouth turned off E-mail port 25 today so you can only use their SMTP Mail server and no one else's, that's not right. There is more and more of that's not right happening everyday. :|
 

Mucman

Diamond Member
Oct 10, 1999
7,246
1
0
Originally posted by: sean2002
Originally posted by: Ameesh
you could have just blocked these ports your self.

I did, but they still fillled up my firewall log on a daily basis

Ooooh those h4x0rs got you good :). j/k

Logs files are there to tell you it's working :) What's more inconvenient? Getting your machine hacked, or large log files?