Re: basic firewall with TCP IP filtering
- From: "Roger Abell [MVP]" <mvpNoSpam@xxxxxxx>
- Date: Tue, 20 Mar 2007 19:57:30 -0700
"Dana" <raff242@xxxxxxxxx> wrote in message
news:8e14f$46007f73$944e306e$1004@xxxxxxxxxxxxxxx
"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)
need to allow port 80
The feature poster is using only allow defining receiving ports.
Poster lack definition to allow from tcp 80/443 to any tcp port at local IP.
So, need you mention cannot be done with feature in use.
.
- Follow-Ups:
- Re: basic firewall with TCP IP filtering
- From: ghaaaaaaz
- Re: basic firewall with TCP IP filtering
- References:
- basic firewall with TCP IP filtering
- From: user
- Re: basic firewall with TCP IP filtering
- From: Dana
- basic firewall with TCP IP filtering
- Prev by Date: Cannot Manage Certificate Services error message
- Next by Date: Re: Can I have multiple password policies?
- Previous by thread: Re: basic firewall with TCP IP filtering
- Next by thread: Re: basic firewall with TCP IP filtering
- Index(es):
Relevant Pages
|
