UDP Ports, closing Win2K Server (No IIS)
From: Craig Gillette (craig_at_accessorystore.com)
Date: 08/21/03
- Next message: Ken Schaefer: "Re: Internet Explorer"
- Previous message: Satisfied: "w00t ! fixed the SSL"
- Next in thread: Ken Schaefer: "Re: UDP Ports, closing Win2K Server (No IIS)"
- Reply: Ken Schaefer: "Re: UDP Ports, closing Win2K Server (No IIS)"
- Reply: Karl Levinson [x y] mvp: "Re: UDP Ports, closing Win2K Server (No IIS)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
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?
- Next message: Ken Schaefer: "Re: Internet Explorer"
- Previous message: Satisfied: "w00t ! fixed the SSL"
- Next in thread: Ken Schaefer: "Re: UDP Ports, closing Win2K Server (No IIS)"
- Reply: Ken Schaefer: "Re: UDP Ports, closing Win2K Server (No IIS)"
- Reply: Karl Levinson [x y] mvp: "Re: UDP Ports, closing Win2K Server (No IIS)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
