OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Bronek Kozicki (brokrubikon.pl)
Date: Fri Apr 05 2002 - 14:53:43 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    > I'm trying to use Internet Services Manager snap-in on a web server
    > located in our internal network. The web server is running Win2k and
    > IIS 5.0. At first, I was connecting fine. I've added TCP/IP filtering
    > to the remote machine, and now I can't connect. What ports does ISM use
    > anyway?
    >
    > I'm allowing UDP and TCP connection to port 137-139 and just TCP to port
    > 80. All other filtering is taken care off in the outside firewall.

    MMC is using RPC (aka DCE) protocol. You will need to open port 135 (UDP and
    TCP), this will allow to negotiate "real" connection. Unfortunatelly, this
    usually means some random TCP port above 1024. I do not think that there is
    any way to force negotiating some fixed port for this particular tools, but
    maybe someone knows some hack ?

    B.