RE: OT: (ish) Web publishing question

[Pedro de Oliveira <p.oliveira@xxxxxxx>]

Could you not use:

http://paulgordon.homeip.net:80
http://paulgordon.homeip.net:81
http://paulgordon.homeip.net:82

as hyperlinks on the default machines default page or have I missed the
point?

Pedro

-----Original Message-----
From: Paul Gordon [mailto:paul_gordon@xxxxxxx]
Sent: 04 March 2002 23:32
To: ukha_d@xxxxxxx
Subject: [ukha_d] OT: (ish) Web publishing question

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



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/