Steven
Sat Aug 16 12:57:59 CDT 2003
Ip filtering is basically meant as another line of defense for
dedicated servers. Ip filtering for tcp blocks non initiated inbound traffic
only, so if you are trying to access a website from your computer, then you
are sending port 80 outbound traffic. A firewall would be a much better
option. A good one [even a free personal one] can controll traffic both
inbound and outbound, show connected ports, and log traffic/intrusions. If
you absolutely do not want to install a firewall, then ipsec filtering
starting with a default block all ip traffic rule would be much better.
However if you misconfigure the rules, you could leave your computer
vulnerable while thinking it is safe. Whatever you do, be sure to go to one
of the online firewall testing sites to check your final configuration. ---
Steve
http://scan.sygatetech.com/
"Gus" <first_chicago@nospam.hotmail.com.nospam> wrote in message
news:05e701c363a5$6058c590$a401280a@phx.gbl...
> I'm looking to lockdown a server that has two nics on it.
> One NIC is a direct connection to the internet, and the
> other has full internal access. I turn filtering on and
> only allowed the following ports:
>
> TCP:
> 20
> 21
> 25
> 80
> 110
> 443
>
> UDP:
> 53
>
> When I filter the direct internet connection to these
> only, I am unable to resolve DNS names through the name
> server. Am I missing something? I tried this on Windows
> 2000 Advanced and Windows 2003 Advance and have had no
> luck with both. Thanks.
>
> Gus