RE: OT: (ish) Web publishing question

[<lee@xxxxxxx>]

Oops, sorry, I missed the bit about multiple servers - I run all my stuff
on a single server at home. Ideally I'd like all the webservers using port
80 because the firewall at work does a sterling job of blocking anything
out of the ordinary - say, running http over a telnet port, which
effectively blocks out a lot of stuff running on the server.

In your situation the stuff below should work quite nicely :)

Lee.

> I'm not sure what you mean by IIS has to serve them, - when creating
> the new  default directory it has to be pointed initially to a real
> directory, which  can be either a local one, or a network share, but
> the choice is irrelevant,  because as soon as the wizard has finished
> and the new virtual directory is  created, I change the properties so
> that the content selection changes from  "A directory located on
this
> computer" to "A redirection to a URL" then  specify
> "www.paulgordon.homeip.net:82" as the URL to redirect to.
>
> NO content has to be served to the browser from the IIS machine the
new
> URL  gets passed back to the client which then requests it as normal.
> Then,  because it is a *NEW* request on a different port number, my
> router's  redirection sends it to the requisite server on my LAN, on
> THAT machines  standard http port 80.
>
> so I _can_ publish multiple internal webservers all on port 80 - but I
> _do_  need the client request to come in on the alternate port number
> eventually,  so that the router knows which server the request is
> for...
>
> Paul G.