IIS behind firewall

I'm hosting a web site for a school. Internally the
website works fine, but externally the web site returns an
error "The page cannot be displayed" this has only
happened after the firewall was set to block ports 1024-
6535.

I knew that IIS listened on port 80 but I heard that it
negotiates with the web browser for a port to return the
http requests.

I am a novice to IIS.

Thanks

 >-----Original Message-----
 >Um, what exactly are you trying to connect to that "isn't
working"?
 >
 >The websites typically listen on port 80 (HTTP), or port
443 (HTTPS), so a
 >block on ports > 1024 shouldn't have any effect.
 >
 >If you're trying to connect via the IIS MMC Snapin, then
you may have
 >problems, since that requires access (by default) to one
of the dynamic
 >high-order ports
 >
 >Cheers
 >Ken
 >
 >"David McKenzie" <mckenzie.david.m.DeleteThis@edumail.vic.gov.au>
wrote in message
 >news:0b1d01c36d24$1d193f70$a101280a@phx.gbl...
 >: I run an IIS web server that recently stop working once
a
 >: firewall was placed upstream. the firewall blocks ports
 >: 1024 - 6535. My question is which ports should I request
 >: to be opened or how do I change IIS to operate on the
 >: lower ports?
 >:
 >: Thanks
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS behind firewall 

If you are using Internet Explorer (as the error message indicates), in IE
go to Tools / Internet Options / Advanced tab / uncheck "Show friendly HTTP
error messages". That will give you the true error message, post it here and
we'll see what we can do...

hth
--
Best regards,
Anders Janson
Microsoft Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
<a style='text-decoration: underline;' href="http://www.microsoft.com/info/cpyright.htm." target="_blank">http://www.microsoft.com/info/cpyright.htm.</a>


"David McKenzie" <mckenzie.david.m.TakeThisOut@edumail.vic.gov.au> wrote in message
news:0ba001c36d2d$bdae0480$a101280a@phx.gbl...
 > I'm hosting a web site for a school. Internally the
 > website works fine, but externally the web site returns an
 > error "The page cannot be displayed" this has only
 > happened after the firewall was set to block ports 1024-
 > 6535.
 >
 > I knew that IIS listened on port 80 but I heard that it
 > negotiates with the web browser for a port to return the
 > http requests.
 >
 > I am a novice to IIS.
 >
 > Thanks
 >
  > >-----Original Message-----
  > >Um, what exactly are you trying to connect to that "isn't
 > working"?
  > >
  > >The websites typically listen on port 80 (HTTP), or port
 > 443 (HTTPS), so a
  > >block on ports > 1024 shouldn't have any effect.
  > >
  > >If you're trying to connect via the IIS MMC Snapin, then
 > you may have
  > >problems, since that requires access (by default) to one
 > of the dynamic
  > >high-order ports
  > >
  > >Cheers
  > >Ken
  > >
  > >"David McKenzie" <mckenzie.david.m.TakeThisOut@edumail.vic.gov.au>
 > wrote in message
  > >news:0b1d01c36d24$1d193f70$a101280a@phx.gbl...
  > >: I run an IIS web server that recently stop working once
 > a
  > >: firewall was placed upstream. the firewall blocks ports
  > >: 1024 - 6535. My question is which ports should I request
  > >: to be opened or how do I change IIS to operate on the
  > >: lower ports?
  > >:
  > >: Thanks
  > >
  > >
  > >.
  > ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS behind firewall 

It doesn't negotiate with the clients about a port to return the request.

When your browser needs to open a connection to the webserver to request a
webpage, the browser is assigned a port (or two) by the operating system.
These are usually > 1024. Your browser connects to port 80 on the webserver,
and the webserver sends back the data to your browser's port. There is no
negotiation.

Secondly "the page can not be displayed" is just a generic error. There
shoudl be some more infomation further down the page. If a connection to the
server can not be made at all, then you should see "Can not find server, or
DNS error" (assuming you are using Internet Explorer). If the server can be
reached, but is generating an error you might see somethng like "404 File
Not Found" or "500 Internal Server Error"

Cheers
Ken

"David McKenzie" <mckenzie.david.m.TakeThisOut@edumail.vic.gov.au> wrote in message
news:0ba001c36d2d$bdae0480$a101280a@phx.gbl...
: I'm hosting a web site for a school. Internally the
: website works fine, but externally the web site returns an
: error "The page cannot be displayed" this has only
: happened after the firewall was set to block ports 1024-
: 6535.
:
: I knew that IIS listened on port 80 but I heard that it
: negotiates with the web browser for a port to return the
: http requests.
:
: I am a novice to IIS.
:
: Thanks
:
: >-----Original Message-----
: >Um, what exactly are you trying to connect to that "isn't
: working"?
: >
: >The websites typically listen on port 80 (HTTP), or port
: 443 (HTTPS), so a
: >block on ports > 1024 shouldn't have any effect.
: >
: >If you're trying to connect via the IIS MMC Snapin, then
: you may have
: >problems, since that requires access (by default) to one
: of the dynamic
: >high-order ports
: >
: >Cheers
: >Ken
: >
: >"David McKenzie" <mckenzie.david.m.TakeThisOut@edumail.vic.gov.au>
: wrote in message
: >news:0b1d01c36d24$1d193f70$a101280a@phx.gbl...
: >: I run an IIS web server that recently stop working once
: a
: >: firewall was placed upstream. the firewall blocks ports
: >: 1024 - 6535. My question is which ports should I request
: >: to be opened or how do I change IIS to operate on the
: >: lower ports?
: >:
: >: Thanks
: >
: >
: >.
: >
 >> Stay informed about: IIS behind firewall