IIS port redirection

[Gregoire Gentil]

Hello,

I am looking for a product that will be installed on my win2k IIS5 server
and that will do port redirection. I mean all requests to http://xxx.yyy.com
will be redirected internally to http://www.yyy.com/redirect/:8080 while
http://www.yyy.com is working normally.

Any idea which product can do that? I am also ready to develop it if
required (but I am pretty sure that it already exists).

Many thanks by advance,

Gregoire

[Tom Kaminski [MVP]]

Post by Gregoire Gentil
Hello,
I am looking for a product that will be installed on my win2k IIS5 server
and that will do port redirection. I mean all requests to

http://xxx.yyy.com

Post by Gregoire Gentil
will be redirected internally to http://www.yyy.com/redirect/:8080 while
http://www.yyy.com is working normally.
Any idea which product can do that? I am also ready to develop it if
required (but I am pretty sure that it already exists).

Just setup a new web site (virtual server) using xxx.yyy.com in the host
headers that has its root set to \inetpub\wwwroot\redirect (or whatever the
path is, the one you provide does not make sense.)

[Jeff Cochran]

Post by Gregoire Gentil
I am looking for a product that will be installed on my win2k IIS5 server
and that will do port redirection. I mean all requests to http://xxx.yyy.com
will be redirected internally to http://www.yyy.com/redirect/:8080 while
http://www.yyy.com is working normally.

Why? That's exactly what host headers are for.

See:

Running mutiple web sites on a single IP address:
http://www.iisanswers.com/Top10FAQ/t10-hostheaders.htm
http://www.iisanswers.com/articles/dns_for_iis.htm

Jeff

[Leythos]

In article <***@TK2MSFTNGP10.phx.gbl>, ***@a.com
says...

Post by Gregoire Gentil
Hello,
I am looking for a product that will be installed on my win2k IIS5 server
and that will do port redirection. I mean all requests to http://xxx.yyy.com
will be redirected internally to http://www.yyy.com/redirect/:8080 while
http://www.yyy.com is working normally.
Any idea which product can do that? I am also ready to develop it if
required (but I am pretty sure that it already exists).

IIS can do this already - why buy something extra to install on the
server?

In fact, you can have different virtual directories under the root site
forward to many different hosts/ports, I do it all the time.

[Gregoire Gentil]

Probably my question was not clear:

- I have win2k and IIS5
- I have one IP address on the machine ppp.ppp.ppp.ppp
- I have a website http://www.xxx.com set up in IIS
- I have an application that is using the port 8080. I reach this
application at http://ppp.ppp.ppp.ppp:8080

I want people to reach this application using http://yyy.xxx.com on port 80.

The port redirection should occur on the server when the request reaches the
server not before. (my end user uses computers with a firewall that restrict
them from using a port different from 80).

Any idea how to achieve this?

Gregoire

Post by Leythos
says...

Post by Gregoire Gentil
Hello,
I am looking for a product that will be installed on my win2k IIS5 server
and that will do port redirection. I mean all requests to

http://xxx.yyy.com

Post by Leythos

Post by Gregoire Gentil
will be redirected internally to http://www.yyy.com/redirect/:8080 while
http://www.yyy.com is working normally.
Any idea which product can do that? I am also ready to develop it if
required (but I am pretty sure that it already exists).

IIS can do this already - why buy something extra to install on the
server?
In fact, you can have different virtual directories under the root site
forward to many different hosts/ports, I do it all the time.
--
--
(Remove 999 to reply to me)

[Gregoire Gentil]

I did not say that they can't use port 80. They CAN!!! But they can't use
port 880.

"my end user uses computers with a firewall that restrict
them from using a port different from 80"
======

I want the end user to connect using a request on port 80. Once this request
hits my server, the first thing to do is to forward this request to port
8080. Then the application responding to port 8080 will handle the answer.


Gregoire

Post by Leythos
says...

Post by Gregoire Gentil
- I have win2k and IIS5
- I have one IP address on the machine ppp.ppp.ppp.ppp
- I have a website http://www.xxx.com set up in IIS
- I have an application that is using the port 8080. I reach this
application at http://ppp.ppp.ppp.ppp:8080
I want people to reach this application using http://yyy.xxx.com on port 80.
The port redirection should occur on the server when the request reaches the
server not before. (my end user uses computers with a firewall that restrict
them from using a port different from 80).
Any idea how to achieve this?

You can't - you said it yourself: The end users are blocked from using
port 80 by their firewall. That means that when they try and connect to
www or http it's going to fail at the firewall unless you tell them to
use 8080.
What makes you think that 8080 is open? Any firewall admin is only going
to allow outbound on selected ports, and all ports are blocked by
default in a good firewall. The firewall admin would have had to
specifically open 8080 for outbound.
Mark
--
--
(Remove 999 to reply to me)

[Leythos]

In article <***@TK2MSFTNGP10.phx.gbl>, ***@a.com
says...

Post by Gregoire Gentil
I did not say that they can't use port 80. They CAN!!! But they can't use
port 880.
"my end user uses computers with a firewall that restrict
them from using a port different from 80"
======
I want the end user to connect using a request on port 80. Once this request
hits my server, the first thing to do is to forward this request to port
8080. Then the application responding to port 8080 will handle the answer.

Ok, while I got the line wrong you said it again - they can not access
port 8080 due to their firewall. No amount of redirection will allow
them to access port 8080 (or other non port 80 ports).

Please bottom post, top posting is not acceptable in usenet.

[Kristofer Gafvert]

What i think he wants to do is this:

One public IP
Two domain names, www.mycompany.com and pc1.mycompany.com

When a user goes to www.mycompany.com:80, everything should work as usually
When a user goes to pc1.mycompany.com:80, the user should not hit the
webserver running on that IP (which is www.mycompany.com), but instead the
server should forward the request to an internal machine. Just like a
firewall forwards IPs to machines inside the firewall, but this time, we
also have to find out what DNS-name was used, and not only the IP.

And what's wrong with top posting? Most news reader nowadays have the
messages threaded, which means that you start with the first message, and
then read all other messages in the thread. If you do this, it is only
annoying if you bottom post, because you have to scroll for _every_ post. If
you top post, no scrolling is needed.

So use whatever you feel like, it's acceptable to top post or bottom post.
--
Regards,
Kristofer Gafvert
http://www.ilopia.com - My personal Web Site, with information about things
i find interesting, for example Windows Server 2003.
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.

Post by Leythos
says...

Post by Gregoire Gentil
I did not say that they can't use port 80. They CAN!!! But they can't use
port 880.
"my end user uses computers with a firewall that restrict
them from using a port different from 80"
======
I want the end user to connect using a request on port 80. Once this request
hits my server, the first thing to do is to forward this request to port
8080. Then the application responding to port 8080 will handle the answer.

Ok, while I got the line wrong you said it again - they can not access
port 8080 due to their firewall. No amount of redirection will allow
them to access port 8080 (or other non port 80 ports).
Please bottom post, top posting is not acceptable in usenet.
--
--
(Remove 999 to reply to me)