Re: Closing ports using Sygate
- From: Casey Klc <casey@xxxxxxxxxxxxxxxx>
- Date: Sat, 28 Jan 2006 18:35:26 GMT
snip...
> He needs to find out what program/service has the port open and then do
> as you mentioned above, remove the act as server check. That should fix
> the problem. If not, then he can indeed create an advances rule to
> block that port if he's sure it's always 1025 that's open. I believe
> the free version of Sygate allows you 20 advanced rules, so that should
> be more than enough. You can block by port and address, etc.
>
>
To find out what application/services is running and holding
local port 1025 open, just look on Sygate main page at the
Running Applications window.
(Connection Details must be enabled under view menu)
This will show application/service, protocol, connect/listen,
ports(local/remote, and IP.
Casey
.
- Follow-Ups:
- Re: Closing ports using Sygate
- From: ohaya
- Re: Closing ports using Sygate
- References:
- Closing ports using Sygate
- From: tenplay
- Re: Closing ports using Sygate
- From: ohaya
- Re: Closing ports using Sygate
- From: Kerodo
- Closing ports using Sygate
- Prev by Date: The Dreaded Personal Firewall
- Next by Date: Re: The Dreaded Personal Firewall
- Previous by thread: Re: Closing ports using Sygate
- Next by thread: Re: Closing ports using Sygate
- Index(es):
Relevant Pages
|