Re: OT: (ish) Web publishing question

[<lee@xxxxxxx>]

Forgot to add - Argh! Don't use IIS !!  Use Apache much more secure and
won't get clobbered by worm/tojans/etc as badly as IIS.
If you must use IIS get the LockDown tool from MS and run that to fully
secure it.

Lee.




> Sorry for the mildly off-topic post, but I know the answer is in here
> somewhere... and it does involve my HA server....
>
> Can anyone familiar with IIS 4.0 give me some advice on configuring it
> to  publish websites on other machines on my internal network...
>
> I have several machines on my home LAN that have webservers on them,
> one of  which is IIS, the others being either PWS or Homeseer's
> built-in etc...
>
> I can currently access any or all of them by configuring port
> redirections  on my router, so the request URL at the browser has to
> include a
> non-standard port number, - 80 for one machine, 81 for another and so
> on...  (the actual ports on the webservers themselves don't have to
> change, the  router does the port mapping back to 80 once the request
> is received). This  is OK, but sometimes I forget which port number to
> use for which machine!!
>
> So, what I want to do is to be able to redirect to the appropriate
> internal  server by using a friendly URL instead, like
> http://paulgordon.homeip.net/server1
and
> http://paulgordon.homeip.net/server2
and so on....
> and have *all* of these requests sent to one machine which then
proxies
> them  to the appropriate internal server.
>
> I've tried to do this on the IIS server,  I set up a virtual directory
> under  my default website, and configured it to redirect to another
> URL, the URL  specified being the internal IP address of another
server
> on my LAN. This is  all fine & dandy when browsing on my internal
LAN
> (I can access the IP of  the target server), but obviously *wont* work
> from outside my LAN, as the  server doesn't actually prody the
request,
> it just sends the redirect URL  back to the browser, which quite
> obviously can't resolve it.
>
> So my question is: Is it actually possible to get IIS to publish
> websites  hosted on other machines on my internal network in the way I
> want? One of  the machines in question is my Homeseer webserver, so
> would it work if I  redirect to a directory instead of a URL and point
> it to the program  files\homeseer\html directory instead? - my initial
> efforts seem to suggest  that it isn't - there is no obvious htm or
asp
> file in any of the Homeseer  directories that can be displayed.
>
> If IIS can't do this, is there anything I can bung in that can?
>
> Thanks for listening chaps...
>
> Paul G.
>
>
>
>
> _________________________________________________________________
> Send and receive Hotmail on your mobile device: http://mobile.msn.com
>
>
> ------------------------ Yahoo! Groups Sponsor
> ---------------------~--> Buy Stock for $4.
> No Minimums.
> FREE Money 2002.
> http://us.click.yahoo.com/BgmYkB/VovDAA/ySSFAA/IBOolB/TM
>
---------------------------------------------------------------------~->
>
> For more information: http://www.automatedhome.co.uk
> Post message: ukha_d@xxxxxxx
> Subscribe:  ukha_d-subscribe@xxxxxxx
> Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
> List owner:  ukha_d-owner@xxxxxxx
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/