R
robr
We have an application hosted on Server 2003 running on port 8090.
Problem is when the sales guys go to demo this, many companies can't
access it, so we changed it to run on port 80 instead.
Then I get a call from another sales guy who says he's passed out the
8090 URL to many potential clients and also wants 8090 to work for the
app... essentially the application will respond on two different
ports. This box is not behind a firewall, there is no NAT and I
cannot set up any rules at the router level.
On a Linux box, I can just tell the OS if a request comes in on 8090,
forward it to port 80. I have no idea if this is possible on a
Windows box but that's what I need to be able to do. Any pointers?
Google searches on forwarding ports just turns up a zillion hits about
NAT port forwarding.
Problem is when the sales guys go to demo this, many companies can't
access it, so we changed it to run on port 80 instead.
Then I get a call from another sales guy who says he's passed out the
8090 URL to many potential clients and also wants 8090 to work for the
app... essentially the application will respond on two different
ports. This box is not behind a firewall, there is no NAT and I
cannot set up any rules at the router level.
On a Linux box, I can just tell the OS if a request comes in on 8090,
forward it to port 80. I have no idea if this is possible on a
Windows box but that's what I need to be able to do. Any pointers?
Google searches on forwarding ports just turns up a zillion hits about
NAT port forwarding.