Re: IIS web proxy
From: BP (jobseeker04_at_iwon.com)
Date: 02/04/05
- Next message: mrxether: "IIS 6, Bandwidth throttling, and BITS uploads"
- Previous message: Ben: "IIS 5.1 500 Internal Server Error"
- In reply to: Imran Aziz: "Re: IIS web proxy"
- Next in thread: Imran Aziz: "Re: IIS web proxy"
- Reply: Imran Aziz: "Re: IIS web proxy"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Feb 2005 12:07:05 -0500
Is this a multihomed server, 2 Nics?
If so is the local nic IP addresss not assigned in iis root web? I ask this because U
mention
external interface to router on SBS this would lead one to believe more than one exists.
If
that is the case why not assign both address to iis even though you have to bind another
in
advanced properties of nic as a work around to ISA being at same port 80 then disable
socket pooling on iis5.0 allowing it to share port 80 at another local address.
I have done the same to allow Netshow unicast service to bind on port 80
and iis5.0 port 80 without error. Add the entry into DNS for the new address
and publish web via name entered into dns like ww1.myweb.com. Don't believe it
will interfere with ISA as it uses the first local bound address and iis5.0
will use the other new local bound address. IIs assumes it owns port 80 and
is unwilling to give it up without disabling socket pooling as I have learned.
To disable socket pooling for an IIS 5.0 Web site
1.. At the command prompt, type cd SystemDrive\inetpub\adminscripts.
2.. At the SystemDrive\Inetpub\AdminScripts command prompt, type
cscript adsutil.vbs set w3svc/disablesocketpooling true.
The command prompt will reply:
disablesocketpooling : (BOOLEAN) TRUE
"Imran Aziz" <imran@bindweb.com> wrote in message
news:OeMKXosCFHA.1604@TK2MSFTNGP10.phx.gbl...
> Hello Jeff,
> Thanks a lot for your response, Sorry I missed out one thing. There is a
> website already published from SBS2K, so all the firewall and Router rules
> are setup fine for that, and I do understand them, the issue is now with
> this development machine, how can I publish IIS sites from another server
> using the SBS2K, since all traffic goes through SBS, and Dev Server is on
> the internal network, and is not connected to the external interface facing
> the router, so how do request route from the router to the Dev Server, since
> they will have to go through SBS to do so.
> You mentioned this can be done using ISA, any leads as to how to get
> that done, since after more then a year of working with ISA it still is a
> black box to me :)
>
> Imran.
>
> "Jeff Cochran" <jeff.nospam@zina.com> wrote in message
> news:420b751d.259721639@msnews.microsoft.com...
> > On Fri, 4 Feb 2005 10:42:02 -0000, "Imran Aziz" <imran@bindweb.com>
> > wrote:
> >
> >> I want to publish my website from behind a firewall, how can I do
> >> that?
> >
> > Open the proper ports in the firewall, provide network address
> > translation if needed.
> >
> >>Here is my setup.
> >>I have a small intranet which is configured as follows
> >>
> >>Router facing the internet configured with NAT so port redirect has been
> >>configured.
> >>
> >>IIS is installed on a SBS2K server behind the Router, there is an ISA
> >>firewall running on the SBS2K server.
> >>
> >>port 80 and 8080 is being used by ISA web proxy, so IIS sites are running
> >>on
> >>port 801.
> >>
> >>Now I redirect port 801 from router to the IIS to service one website on
> >>the
> >>SBS2K, works fine.
> >>
> >>Now I also have a separate development server on our intranet from which I
> >>want to publish a website.
> >>
> >>Since router can only publish websites from the IIS installed on the
> >>SBS2K,
> >>the only way I can think of publishing a website from the dev server is to
> >>use a web proxy somehow, like one provided in Apache webserver. i.e
> >>request
> >>comes to IIS of SBS2K which does a proxy for the IIS on the Dev Server and
> >>services the website.
> >>
> >>Is there a way to do that with IIS?
> >
> > No.
> >
> >>if not is there an alternate solution
> >>without compromising the security of the network?
> >
> > SBS has ISA, which should do this.
> >
> >>I do not want to create a
> >>DMZ, and I do not want to put the dev server directly behind the router.
> >
> > Then you've eliminated one option that would have worked as well.
> >
> > Jeff
>
>
- Next message: mrxether: "IIS 6, Bandwidth throttling, and BITS uploads"
- Previous message: Ben: "IIS 5.1 500 Internal Server Error"
- In reply to: Imran Aziz: "Re: IIS web proxy"
- Next in thread: Imran Aziz: "Re: IIS web proxy"
- Reply: Imran Aziz: "Re: IIS web proxy"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
