UDP Ports, closing Win2K Server (No IIS)

From: Craig Gillette (craig_at_accessorystore.com)
Date: 08/21/03 

Date: Wed, 20 Aug 2003 19:10:02 -0700

I am managing a Win2K Server, no IIS. I want to start
closing ports to help prevent worm attacks.
How do I do this? Do I need IIS?
I was thinking of using IPSec? Is this correct?
I wanted to block inbound traffic on port 995, for
example, and I was going to use this syntax:

ipsecpol -w REG -p "Block UDP 995 Filter" -r "Block
Inbound UDP 995 Rule" -f *=0:995:UDP -n BLOCK -x

Does this look correct? Is there another or a better way?

Relevant Pages

  • Re: exploited win2k box, not quite sure how:
    ... > Win2k server, SP2 ... the patch level on the OS was SP2. ... As for anonymous writeable ftp, ... IIS had three definitions to ...
    (Incidents)
  • RE: directory configuration issue w/2K pro
    ... Kristofer Gafvert - IIS MVP ... "Jeff B." ... > this works perfectly on the server, which is a win2k server machine. ...
    (microsoft.public.inetserver.iis)
  • IIS Logon
    ... I have configured 2 ftp sites on iis (win2k server version) ... (as well as the ftproot directory) ... documentation for configuring iis? ...
    (microsoft.public.win2000.general)
  • IIS Login
    ... I have configured 2 ftp sites on iis (win2k server version) ... (as well as the ftproot directory) ... documentation for configuring iis? ...
    (microsoft.public.win2000.security)
  • IIS Logon
    ... I have configured 2 ftp sites on iis (win2k server version) ... directory (as well as the ftproot directory) ... documentation for configuring iis? ...
    (microsoft.public.inetserver.iis)