OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Ondrej Gug (ondrej.duchonDEBIS.CZ)
Date: Fri Apr 06 2001 - 00:40:22 CDT

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

    I did the same thing try to open port 42 tcp

    Ondrej

    -----Original Message-----
    From: Rich Wilson [mailto:wk633YAHOO.COM]
    Sent: Thursday, April 05, 2001 2:18 AM
    To: FOCUS-MSSECURITYFOCUS.COM
    Subject: Win2K port filtering, DNS

    I'm trying to add Win2K port filtering (not via IPSec) to a Win2K IIS
    Server,
    and it breaks dns as a client. I've allowed both 53 UDP and TCP.

    Based on Philip Cox's 'Hardening Windows 2000' paper
    (http://www.systemexperts.com/tutors/HardenW2K101.pdf) I don't think I
    should
    even have to explicitly open port 53 to use dns as a client. In any case,
    with
    port filtering on, and 53 (tcp and udp) open, dns times out. With port
    filtering off, dns works fine.

    It is a dual homed box, with the dns server on the 'outside', and the port
    filtering applied only to the 'external' interface.

    Any ideas?

    =====
    : __o
    : -\<,
    : 0/ 0

    __________________________________________________
    Do You Yahoo!?
    Get email at your own domain with Yahoo! Mail.
    http://personal.mail.yahoo.com/