How to Disable MMC.EXE acting as a server? (Microsoft Mana..

Archived from groups: microsoft.public.windowsxp.configuration_manage,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.setup_deployment (More info?)

I've managed to close all the listening ports using online guides, and the
utilities at GRC.COM.

However, if I click Start -> Run -> type DCOMCNFG and hit OK. When the
Microsoft Management Console opens, I click on "Components" but then Zone
Alarm prompts asking if I want to allow Microsoft Management Console to act
as a server program. Whether I deny or allow access, TCP ports 135 and 1030
are opened regardless.

The IP address it's trying to connect to is 0.0.0.0 which, as I understand
it, is Loopback(?) in other words it's trying to connect to itself, and not
a remote system?

What confuses me even more is that Steve Gibson says on his Website
(GRC.COM) that *ONLY* Task Scheduler, MSDTC or DCOM will cause TCP 135 to
open. I know for certain I have DCOM and Task Scheduler disabled, but MSDTC
no longer appears in the Services window so I cannot be 100% sure.

This occurs both before AND after I've freshly re-installed WindowsXP Pro,
applied SP1 and installed Zone Alarm (free). Network card disabled in BIOS,
no Internet connection set up.

Why does MMC need to act as a server? How can I disable it from even trying?