TCP/IP Filtering Problem

From: George Jewell (gjewell_at_usdatalink.com)
Date: 09/07/04


Date: Tue, 07 Sep 2004 18:11:24 GMT

Hello,

I'm trying to lock down a Win2K server (Svc. Pak 4) for use as a web server
and want to be as thorough as possible. I'd like to use TCP/IP Filtering,
but have run into a snag. I have it set so that the following TCP ports are
permitted: 21, 25, 53, and 80; and also UDP port 53. The problem is that it
seems name resolution is not working. I can ping sites by IP address but not
DNS names. Also, sending mail with the SMTP server does not work, and adds
this entry to the system log: "message delivery to the remote domain
<domain> failed for the following reason: destination server does not
exist."

When I allow all UDP ports, everything works fine. Obviously there are a few
other UDP ports I must allow - does anyone have any suggestions as to which
ports to open? Thanks.



Relevant Pages

  • TCP/IP Filtering Problem
    ... but have run into a snag. ... Also, sending mail with the SMTP server does not work, and adds ... this entry to the system log: "message delivery to the remote domain ... When I allow all UDP ports, ...
    (microsoft.public.inetserver.iis.security)
  • TCP/IP Filtering Problem
    ... but have run into a snag. ... Also, sending mail with the SMTP server does not work, and adds ... this entry to the system log: "message delivery to the remote domain ... When I allow all UDP ports, ...
    (microsoft.public.win2000.networking)
  • Re: TCP/IP Filtering Problem
    ... security than fooling around with the TCP/IP Protocol. ... Also, sending mail with the SMTP server does not work, and adds ... > this entry to the system log: "message delivery to the remote domain ... > When I allow all UDP ports, ...
    (microsoft.public.win2000.networking)