Re: Publishing A web Server
From: Jim Harrison [MSFT] (jmharr_at_online.microsoft.com)
Date: 05/27/04
- Next message: Frederico: "Problem with telnet to a outside machine"
- Previous message: A Klimkin: "Re: packet filters just dont apply?"
- In reply to: Tony Su: "Re: Publishing A web Server"
- Next in thread: Tony Su: "Re: Publishing A web Server"
- Reply: Tony Su: "Re: Publishing A web Server"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 May 2004 23:39:44 -0700
Actually, what you responded with and what I referenced are two separate actions.
Specifying individual IPs in the http.sys configuration is NOT the same as binding "per IP" in the web site properties.
-- Jim Harrison [ISASE] Read the help, books and articles! This posting is provided "AS IS" with no warranties, and confers no rights. "Tony Su" <anonymous@discussions.microsoft.com> wrote in message news:1319701c443ab$604a09b0$a601280a@phx.gbl... Hello Jim, I would have quoted exactly the same article and believe it actually supports what I have said. This is the important passage (for IIS6)... HTTP.sys uses an IP inclusion list. By default, this list is blank and IIS listens on all IP addresses. You can specify the IP addresses IIS will listen on by adding them to the IP inclusion list. So, if the list is blank (no IP address configured), then Socket Pooling is enabled. And if a single IP address is configured, that act automatically not only configures listening on that one address, it effectively disables listening on all other addresses. There is an additional important comment in the beginning that the DisableSocketPooling metabase setting doesn't have any effect (unlike IIS5.x) Tony Su >-----Original Message----- >Sorry Tony, that's not true. >Windows 2003 still requires that you disable socket pooling; it's just that the process is different. >IIS5: http://support.microsoft.com/default.aspx? scid=kb;EN-US;238131 >IIS6 http://support.microsoft.com/default.aspx?scid=kb;EN- US;813368 > >-- > Jim Harrison [ISASE] > Read the help, books and articles! > > This posting is provided "AS IS" with no warranties, and confers no rights. > > >"Tony Su" <anonymous@discussions.microsoft.com> wrote in message news:ed5901c43d24$111c7090$a601280a@phx.gbl... >On Win2K3, if you have specified exact IP addresses for >your website, you have already automatically disabled web >socket pooling. > >Fredrik is partially right that the path is not described >correctly, but what he suggests may or may not be what is >needed. The path is a "relative path" as described in IIS >for the website, and ordinarily should not include >inetpub/wwwroot. A relative path is virtual and relative >to the root of the website as seen in the ISM... and may >or may not be described as /* > >Tony Su > > > > > > >>-----Original Message----- >>Whoa, first of all, publishing a service or a website >hosteb by the ISA 2000 >>itself it's always nasty... >> >>I think that, in order to publish the web site, you >should first disable the >>socket pooling (ISA and IIS listening on the same port, >TCP 80) and then >>create the web publishing rule (I'm not sure about it). >You can find >>something about the socket pooling on the MSFT sites. >> >>The destination set should be set with the name of the >web site >>www.yourdomain.com and the path should be /* , not the >local path of the >>folder containing your webiste on IIS. The web pub rule >seems to be ok. >> >>Begin to look around for a good ISA Server tutorial ;). >> >>Byez >> >>"MIcrosoft" <mjones04@tampabay.rr.com> ha scritto nel >messaggio >>news:uGIwETRPEHA.3052@TK2MSFTNGP12.phx.gbl... >>> Greetings All >>> >>> I may be being very dumb here but that is nothing new. >>> >>> Here is the problem >>> >>> I am trying to publish a web server on the sam server >as the ISA server. >>> >>> Here are specs >>> >>> Windows 2003 >>> ISA 2000 SP1 ISA 2000 Updates FP1 >>> Rules as follows >>> >>> Destination set Wedding cam 192.168.1.2 >path /inetpub/wwwroot >>> Rule >>> Wedding Cam name >>> Destination Wedding cam Included >192.168.1.2 /inetpub/wwwroot >>> Action >>> Redirect to 192.168.1.2 >>> Send Original Header >>> Bridging >>> HTTP >>> SSL to HTTP >>> Applies to Any request >>> >>> Can see the Server from Inside at 192.168.1.2 >>> cannot see server from outside >>> >>> Can any one tell me what an idiot i am and what i am >doing wrong >>> >>> Thanks >>> >>> Michael C. Jones >>> Email Michael.Jones@cpuoftampa.com >>> >>> >> >> >>. >> > > >. >
- Next message: Frederico: "Problem with telnet to a outside machine"
- Previous message: A Klimkin: "Re: packet filters just dont apply?"
- In reply to: Tony Su: "Re: Publishing A web Server"
- Next in thread: Tony Su: "Re: Publishing A web Server"
- Reply: Tony Su: "Re: Publishing A web Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
