Re: basic firewall with TCP IP filtering
- From: "Roger Abell [MVP]" <mvpNoSpam@xxxxxxx>
- Date: Mon, 19 Mar 2007 22:24:02 -0700
The Tcp/Ip filtering you are using is very old. It probably has
not been changed since NT 3.51.
The issue you have is due to fact that you are attempting to go
to Tcp 80 (or 443) but from a port not in your list, so the return
is to a port not allowed.
Most people today would be using the Windows firewall, or
IPsec in a purely filtering mode (and to meet your IE usage,
then define that traffic FROM tcp 80 and 443 is allowed)
Actually, as a standard practice people do not browse from
their servers, so while most people use other means they are
likely not defining such that browsing can happen.
"user" <some@xxxxxxxxxxxxx> wrote in message
news:GcFLh.38385$zU1.35304@xxxxxxxxxxxx
Hello,
On my webserver I set "enable tcp ip filtering" to permit only TCP ports
21,21,25,53,80,110,443,1433,3389 and 8086
UDP ports permit only 53 and IP protocols set to permit all.
Problem now is I can access the webserver on this machine from a remote
location (as expected), however, I now cannot access the internet using
internet explorer from this machine (unexpected)
What do I need to change in order for IE to access the internet from this
server? (It has also affected the ability to download NAV updates)
.
- References:
- basic firewall with TCP IP filtering
- From: user
- basic firewall with TCP IP filtering
- Prev by Date: basic firewall with TCP IP filtering
- Next by Date: Re: Can I have multiple password policies?
- Previous by thread: basic firewall with TCP IP filtering
- Next by thread: Re: basic firewall with TCP IP filtering
- Index(es):
Relevant Pages
|
|
