Relationship between IIS and the windows firewall

OK, I'm new to this. So I set up Server 2003 and I configured it as
an application server in order to get familiar with IIS. Once running
I went ahead to another system on the LAN and attempted to connect to
it with a browser on a client, and could not. I then shut off the
firewall on the server and it worked. I finally added port 80 to the
firewall exceptions and it was fine.

I guess my question is why was this not opened up by default once I
set it up as a web server. Seems odd that I would have to do this
manually or did I miss something?

Thanks,
-Jim

Re: Relationship between IIS and the windows firewall

No, you didn't miss anything. Its been a response by Microsoft who did a 180
responding to a context which only had one or two choices available by
default:

* enable and open all ports by default where as the "admin" must take
responsibility to close what is not secure or unwanted.

* close ports by default where as the admin must take responsibility to open
what is wanted doing what may be possible to ensure security thereafter.

Due to the overwhelming number of incompetents, idiots, and morons using
Microsoft's software in a global population which includes evil doers
attempting to exploit the ignorants, idiots and morons it Microsoft
eventually decided to implement the latter rather than the former to ensure
a more secure platform OOTB thereby putting the onus of responsibility on an
informed and competent admin where it belongs.

Quite frankly it was just as ignorant, idiotic, and moronic for Microsoft to
support the former by default in the first place proving stupidity is not
unique to their customers.



"jtpryan" wrote in message
news:f28db617-a62c-4d95-b3e5-67a480cd27e4@k2g2000hse.googleg roups.com...
> OK, I'm new to this. So I set up Server 2003 and I configured it as
> an application server in order to get familiar with IIS. Once running
> I went ahead to another system on the LAN and attempted to connect to
> it with a browser on a client, and could not. I then shut off the
> firewall on the server and it worked. I finally added port 80 to the
> firewall exceptions and it was fine.
>
> I guess my question is why was this not opened up by default once I
> set it up as a web server. Seems odd that I would have to do this
> manually or did I miss something?
>
> Thanks,
> -Jim