Re: Port 135
From: \ (dvader@deathstar.mil)Date: 03/19/02
- Next message: Paul Reutas: "Re: Connection limit reached in WinRoute"
- Previous message: Larry W4CSC: "Re: responding to a hacker"
- In reply to: Tore Lund: "Re: Port 135"
- Next in thread: Tore Lund: "Re: Port 135"
- Reply: Tore Lund: "Re: Port 135"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "\"Crash\" Dummy" <dvader@deathstar.mil> Date: Tue, 19 Mar 2002 09:44:28 -0500
>Strange, my ports are closed or blocked.
Do you have your PWS running? Those were the only ports that showed up as
open. Port 135 isn't tested with the "Stealth scan," but I suspect any port
that is in use will show up.
>(Still, Sygate tells me that
>"You are not fully protected", without giving a good reason why.)
"Not fully protected" can just mean closed but not stealth.
>Hope you find out and tell us.
I had to add specific rules to block HTTP Server ports. I had an "All TCP"
rule to block anything not defined in another rule, but that wasn't enough.
So for example, I have:
HTTP Client
Source: My IP
Destination: Any IP
From: Any port
To: Port 80
Permit
HTTP Server
Source: My IP
Destination: Any IP
From: Port 80
To: Any port
Block
Both are "mirrored." I figured out that that was necessary for two way
communication, like sending web pages.
-- Dave "Crash" Dummy Certified Dilettante Dave@gpick.com http://lists.gpick.com
- Next message: Paul Reutas: "Re: Connection limit reached in WinRoute"
- Previous message: Larry W4CSC: "Re: responding to a hacker"
- In reply to: Tore Lund: "Re: Port 135"
- Next in thread: Tore Lund: "Re: Port 135"
- Reply: Tore Lund: "Re: Port 135"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|