Re: HTTP!!!! Does it use any UDP ports?
From: karl [x y] (jamescagney90210@excite.com)
Date: 08/08/02
- Next message: S. Pidgorny [MVP]: "Re: Certificate Authority How-to Question"
- Previous message: Mike: "Firewall for Windows 2000 Server / .Net Server"
- In reply to: Keith W. McCammon: "Re: HTTP!!!! Does it use any UDP ports?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "karl [x y]" <jamescagney90210@excite.com> Date: Thu, 8 Aug 2002 08:15:41 -0400
"Keith W. McCammon" <km@km.com> wrote in message
news:elhZVskPCHA.1996@tkmsftngp12...
> Q: How does it do that?
> A: DNS.
>
> Q: What ports does DNS require?
> A: Destination port 53/UDP.
... and TCP 53 if the DNS request cannot be answered in a single UDP packet.
If you're using a firewall to do this blocking, you always want to check the
firewall log immediately after a failed access, to see what port, if any, is
being blocked, and to see what rule you need to add or modify to open things
up. This logging is also essential IMHO since you'll never know if a hacker
is trying to get into your system or has gotten into your system, or who the
hacker is, without logging. If you're using a low end NAT router such as
Linksys or Netgear for this, you may need to set up Syslog and download a
syslog client such as the free one from www.kiwi-enterprises.com to capture
the logging.
The packet filtering that comes with Windows 2000 IPsec has no such logging,
which is why I would always recommend forgetting IPsec and using a third
party packet filtering tool such as the Sygate firewall [free for
non-commercial use] instead.
- Next message: S. Pidgorny [MVP]: "Re: Certificate Authority How-to Question"
- Previous message: Mike: "Firewall for Windows 2000 Server / .Net Server"
- In reply to: Keith W. McCammon: "Re: HTTP!!!! Does it use any UDP ports?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
