Port 135

[hotrod55]

How can I create a rule in version 2.04 that will block any traffic through port 135, the one that was exploited by the Blaster worm.

[Phant0m]

Though it’s irreverent to your Question, you using Look ‘n’ Stop v2.04 or v2.04p2?

In EnhancedRulesSet.rls you’ll see “TCP : Block WinNuke” rule, just export that and import it back in-to the rule-set and place it below “TCP : Block incoming connections” rule and make modification to the rule-name, description and the source port (139), just change it to 135….

Though if you using EnhancedRulesSet.rls (one of Look ‘n’ Stop’s Default rule-sets) and you have TCP SPI Activated, then you shouldn’t need that additional rule. “TCP : Block incoming connections” rule should block the Connection attempts onto ALL your TCP ports (0-65534), unless you added additional inefficient rule or rules to the rule-set… ;)

[hotrod55]

I think I'm using 2.04, not the p2 version, whatever that is.

[Phant0m]

-{ Quote: " quoting: hotrod55 link=board=13;threadid=12451;start=0#msg80017 date=1060876013]
I think I'm using 2.04, not the p2 version, whatever that is.
" }-

Hey hotrod55

Visit http://www.wilderssecurity.info/pg.shtml :D

[FireDancer]

What the HE** is the little guy with the sign and the ip address??? rofl

FireDancer

[Pieter_Arntz]

-{ Quote: " quoting: FireDancer link=board=13;threadid=12451;start=0#msg80629 date=1061100915]
What the HE** is the little guy with the sign and the ip address??? rofl

FireDancer
" }-

http://www.wilderssecurity.com/showthread.php?t=12527;start=0#msg80547

[FireDancer]

I want one of those :) hehehehe