One static IP - 2 port 80 apps, 2 servers

Over Clocker

Over Clocker

Over Clocker

Man of Honour
Joined
17 Oct 2002
Posts
9,712
Location
Retired Don
Hi guys.

Quick question -

We've got 1 static IP applied to our site, and we are running 2 port 80 applications on 2 different servers. (Outlook Web Access and Sharepoint).

I don't want the Sharepoint port for internal usage reasons.

Is there a way to set up a redirection in IIS7 so that when we externally browse to sharepoint.blahblah.co.uk:8080 is redirects to the internal sharepoint port 80 on that server? We can setup a port forward for 8080 to that IP on our firewall so that's all fine.

Cheers,

Mal
 
you can nat it, incoming traffic on port 8080 can be natted internally to port 80.

i.e.

externalip:8080 > Router > internalip:80

What do you use as your internet router?

i though owa was over https anyways - could be wrong ive not worked with owa much?
 
Wouldn't that do something odd with the outgoing traffic though? Presumably you'd need to setup some kind of rules for that too?
 
depends what you meant:

the connection tracking table would cover the returning traffic, as it does all established connections.

normal outgoing traffic initiated from the LAN wouldnt be affected as the NAT rule wont effect it as the destination would be set to the public ip address on the firewall, the only time it would affect would be if you typed into the browser from the LAN externalip:8080, you would then be forwarded through to the server locally on port 80 - but its easier to type localip:80
 
Last edited:
your other options are:

specify different source addresses to differentiate the traffic (i dont think this is possible in this scenario)

get a new public ip address / subnet

set up home user vpns so that employees wanted to access their email can dial in and access it as though they were local to the server.
 
You could stick an apache box as the first hit on port 80 then use reverse proxy and name based vhosts to serve through that - i've done this so that i can serve a site through HTTPS (the service runs its own built in insecure server) which was bound to localhost:9080
 
You must log in or register to reply here.
Back
Top Bottom