Re: Trying to understand this behavior, Ports in IIS
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 06/26/05
- Previous message: Bernard Cheah [MVP]: "Re: Is MBSchExt.xml a legitimate schema file ?"
- In reply to: Marlon Brown: "Re: Trying to understand this behavior, Ports in IIS"
- Next in thread: Marlon Brown: "Re: Trying to understand this behavior, Ports in IIS"
- Reply: Marlon Brown: "Re: Trying to understand this behavior, Ports in IIS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 26 Jun 2005 03:03:36 -0700
Well, the issue could be with your:
1. Checkpoint firewall
2. network devices between the firewall and ISA Server
3. ISA Server
4. network devices between ISA Server and IIS
5. IIS server
Can you please describe the steps you took to determine that issues #1
through #4 were not happening, thus it must be #5 that is causing the
strange behavior?
Given your current information, the issue seems to be with the Checkpoint
firewall.
-- //David IIS http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights. // "Marlon Brown" <nospamarlon@hotmail.com> wrote in message news:%23nuE0LeeFHA.688@TK2MSFTNGP14.phx.gbl... 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. > > >
- Previous message: Bernard Cheah [MVP]: "Re: Is MBSchExt.xml a legitimate schema file ?"
- In reply to: Marlon Brown: "Re: Trying to understand this behavior, Ports in IIS"
- Next in thread: Marlon Brown: "Re: Trying to understand this behavior, Ports in IIS"
- Reply: Marlon Brown: "Re: Trying to understand this behavior, Ports in IIS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
Loading