Re: basic firewall with TCP IP filtering




"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




.



Relevant Pages

  • basic firewall with TCP IP filtering
    ... On my webserver I set "enable tcp ip filtering" to permit only TCP ports ... UDP ports permit only 53 and IP protocols set to permit all. ...
    (microsoft.public.windows.server.security)
  • TCP IP filtering
    ... On my webserver I set "enable tcp ip filtering" to permit only TCP ports ... UDP ports permit only 53 adn IP protocols set to permit all. ...
    (microsoft.public.inetserver.iis.security)
  • Re: basic firewall with TCP IP filtering
    ... On my webserver I set "enable tcp ip filtering" to permit only TCP ports ... UDP ports permit only 53 and IP protocols set to permit all. ...
    (microsoft.public.windows.server.security)
  • Re: keeping only ports 21 and 80 open
    ... depending on how your configuration is in XPE... ... configuration, under TCP/IP, and setup TCP/IP filtering, to permit all, ... permit only on TCP/UDP, and IP ports. ... The only real ports I see a potentail problem with is 13 this is ...
    (microsoft.public.windowsxp.embedded)
  • RE: Blocking NetBios
    ... ports 139 and 445 will not respond to a port scan. ... Control Panel - Network - Internet Protocol Properties ... Use: Permit Only specific protocols. ... tcp 139 will not respond to port scans ...
    (Security-Basics)