microsoft.public.windowsxp.security_admin

From: "Marbles"

| Is port 135 flapping in the wind ?
|
| Possibly being a security risk if your firewall is not blocking this port.
| Even if your firewall is blocking this port. Just the thought of this port
| being left open by the Microsoft operating system annoys you and you would
| like that port 135 closed once and for all
|
| Check to see what ports are currently open. This is best done when you first
| boot in to windows and have not connected to the net
|

< snip >

I use a Linksys BEFSR81 Cable/DSL Router which uses NAT Translation and I specifically block
TCP/UDP ports 135 ~ 139 and 445 on the Router. Most, if not all, Cable/DSL Routers have
simplistic FireWall constructs. Therefore I have no problems and I need no modifications on
my LAN side nodes. :-)


--
Dave
http://www.claymania.com/removal-trojan-adware.html
Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp