Still Can't Block 135 with Symantec Firewall 2.01.
From: Ron (rconners_at_earthlink.net)
Date: 07/30/03
- Next message: Don Kelloway: "Re: Sonicwall TELE3 TZX & DMZ"
- Previous message: Chris Carey: "Re: iptables - syn not new"
- Next in thread: Larry: "Re: Still Can't Block 135 with Symantec Firewall 2.01."
- Reply: Larry: "Re: Still Can't Block 135 with Symantec Firewall 2.01."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 29 Jul 2003 22:09:44 -0700
I'm running Symantec Desktop Firewall 2.01 and when I run Sheilds-Up
and Symantec Security Checks they tell me that my RPC Port 135
is open and it SHOULD NOT be visible to the Internet. I added a new
TCP & UDP Block (Inbound & OutBound)for port (Single Service) 135 but
when I run the security checks it still says Port 135 is Open. I
raised the new block to the TOP of the list and even rebooted but
still
the same problem. I've also ran Live Update but that didn't help. I
have also run all the latest Windows 2000 Updates. Do you have any
ideas?
- Next message: Don Kelloway: "Re: Sonicwall TELE3 TZX & DMZ"
- Previous message: Chris Carey: "Re: iptables - syn not new"
- Next in thread: Larry: "Re: Still Can't Block 135 with Symantec Firewall 2.01."
- Reply: Larry: "Re: Still Can't Block 135 with Symantec Firewall 2.01."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]