Re: Trying to understand this behavior, Ports in IIS

From: Marlon Brown (nospamarlon_at_hotmail.com)
Date: 06/26/05

  • Next message: Bernard Cheah [MVP]: "Re: Resetting IUSR user token" 
    Date: Sat, 25 Jun 2005 17:07:08 -0700

    Correct. It should work over 443, but then the connection from client to
    server was successful only upon opening port 8080 in the firewall. This is
    the part I can't understand.
    "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
    news:OK$olWdeFHA.1384@TK2MSFTNGP09.phx.gbl...
    > I'm not certain what your question is about. Can you clarify?
    >
    >
    > Your requests are over https:// , which default to port 443. This means
    > that
    > for those requests, you should NOT see traffic over HTTP/8080 -- which is
    > exactly what you are seeing. So, I'm confused at what behavior you are
    > trying to understand because it all looks by-design to me right now.
    >
    > --
    > //David
    > IIS
    > http://blogs.msdn.com/David.Wang
    > This posting is provided "AS IS" with no warranties, and confers no
    > rights.
    > //
    > "Marlon" <marlon-nospam@hotmail.com> wrote in message
    > news:eNNYszMeFHA.2520@TK2MSFTNGP09.phx.gbl...
    > Win2003, IIS6.
    > Under "Internet Information Services/Web Sites" snap-in, I've created a
    >
    > "Mysite" site.
    >
    > If I click "Properties", "Web Site" tab, I see the following information:
    > TCP Port=8080 SSL=443
    >
    > I published this site via ISA 2004. In ISA I setup a web listener to
    > "listen
    > on port 8080" and "SSL=443".
    >
    > Then when I browse
    > https://mysite.mycompany.com
    >
    > I take traces and I see no indication of port 8080 being in use. Netmon
    > doesn't show that packets use port 8080 at all neither on the client or
    > the
    > server during the request to https://mysite.mycompany.com (all the
    > communications are happening over SSL).
    >
    > The strange part is this:
    > Prior to 'open' port 8080 in our main edge Checkpoint firewall, the site
    > was
    > unreachable from the "Internet".
    > Perhaps even more strange, after opening the port in the edge firewall and
    > make the whole thing work, I go back to the edge firewall and I see *no*
    > hits in the access-list related to port 8080.
    >
    > What would this port 8080 be used for this in this situation ? I am
    > curious.
    >
    >
    >

  • Next message: Bernard Cheah [MVP]: "Re: Resetting IUSR user token"

    Relevant Pages

    • Re: Remote Admin Tools source code for Delphi 4,5,6 & 7
      ... this way I guess the traffic is outbound form the client to ... be remoted and opens up a channel on the firewall. ... the actual client you are going to remotely control. ... all using the same configuration and one Port on your machine. ...
      (borland.public.delphi.thirdpartytools.general)
    • Re: open a certain port
      ... My firewall client is enabled. ... set the option to bypass proxy for internal addresses ... ISA 2004 by default allows only SSL through port 443. ...
      (microsoft.public.isa.configuration)
    • Re: two way communication using NAT and port forwarding
      ... >> How does instant messengers like ICQ work from behind the firewall. ... >> seems to be done using NAT or port forwarding. ... A central server maintained by the creators of the messenger ... >> When the client messenger initiates a request from private IP like ...
      (comp.security.firewalls)
    • RE: RWW and New Firewall Problem
      ... firewall, the network configuration was also changed. ... Once the connection is established on port ... client at port 3389. ... What you cannot visit in RWW, is the computer Terminal Server or just ...
      (microsoft.public.windows.server.sbs)
    • Re: thin client com ports
      ... I'm glad that you got at least one more client working! ... MCSE, CCEA, Microsoft MVP - Terminal Server ... the COM port settings? ... I am testing several thin clients. ...
      (microsoft.public.windows.terminal_services)