Is this possible?

[sduffey]

I have an incoming TCP port mapping on port 80. I have web servers at two different IP's internally. I have remote users that all come from the same IP address. I want them to be able to enter one username and password to be routed to one of the internal web servers and a different username and password to get routed to another internal web server.

If I set up a default mapping I can route to whichever server I put in there without problem, but just that single one. If I use the mappings option, I can route to two different internal servers based on the user (assumed by ip address)

However I can't make it play nice together since all the users will be coming from the same ip.

I have been racking my brains trying to figure out if I can do this somehow in Wingate. Any ideas would be more than welcomed.

[MattP]

Hi,

If you're using the latest version of WinGate then you can make use of the REVERSE PROXY that we've added and redirect to different webservers based on the HOST tag.

In the WWW proxy choose Web Server
Add a new site and select Action: REVERSE PROXY
Enter the server IP address and port
Select the HOSTS tab and add a HOST header

Any incoming request that matches that host header will be redirected to the web server that you defined above.

So you can have test1.domain.com and test2.domain.com being redirected to two different servers on your network.

Is that what you're after?

[sduffey]

I am not quite sure that will work. Will the Wingate server simply forward the connection from the internet to the internal server and then drop it or will it act as the go between for all communications from the outside internet user and the internal web server (on the private lan)

Plus the way we would be differentiating the requests would be like this:

A request to 70.88.33.14/sites/intra goes to one server, a request to 70.88.33.14/mv/mv.asp goes to another server.

I did download the new version yesterday and will be playing with it.

[ChrisH]

However I can't make it play nice together since all the users will be coming from the same ip.

If you have them authenticated already don't assume by IP. Utilise the authenticated username instead. That way you can use the alternative mapping option as it is based on username.

[sduffey]

Actually I got it working as Matt described. I set up some hostnames like abc123.company.com in the dns space for our domain, had wingate redirect based on that header and it works like a champ!

[ChrisH]

Yes that is a nice feature that Qbik added. It no doubt was the solution best suited for you.