Re: DCOM Listening Ports
From: alan (me_at_privacy.net)
Date: 12/25/03
- Next message: David: "Re: Security through wide system use?"
- Previous message: JHLee: "PGP alternatives ?"
- In reply to: Anonymous: "DCOM Listening Ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 25 Dec 2003 14:15:32 -0000
"Anonymous" <monster5001@hotmail.com> wrote in message
news:1d6d478d.0312242143.3b37fad@posting.google.com...
| I do a netstat -an and I have several ports related to DCOM
which are listening. Ports 1025 and 1027 particularly.
| Here is an example exactly as shown in Netstat
|
| TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
The link below explains that some ports will continue to be
shown as 'listening' in netstat despite tightening up your
security. This does not necessarily mean you are at risk.
To quote the article "The netstat command does not exactly
report TCP and UDP ports states".
http://www.hsc.fr/ressources/breves/min_srv_res_win.en.html
You will find that disabling the service Task Scheduler will
eventually be needed (after following the other advice) to
ensure the netstat display is free of these entries.
If you disable Task Scheduler of course you will lose some
other functionality - for example Windows Prefetch will no
longer work and I am not prepared to lose this useful
feature of XP.
The article has been translated from the original French so it is
a little uneven but I managed to implement all the
recommended changes (apart from disabling Task Schedule).
Hope it helps
Alan
- Next message: David: "Re: Security through wide system use?"
- Previous message: JHLee: "PGP alternatives ?"
- In reply to: Anonymous: "DCOM Listening Ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|