Topic: Virtual domain "forwarding"

[Xander]

I'm looking for the best way (if possible) to have one of my virtual domains set up under E-Smith, forwarded to another server on the network running Windows. I need this for one website running on ASP + SQL Server.

Any ideas as to the best/easiest way to accomplish this? I would like E-Smith to do this forwarding, rather than the modem/router.

ps. E-Smith connected to Net via ADSL and modem/router.

[Tim Litwiller]

You mean for just the website of the virtual domain to be on another server?  Or the other server behind the e-smith?

We need a bit more info on what you are actually trying to do.

[Xander]

Thanks, hope this explains it better:

1. I have e-smith server set up with 2 ethernet cards (one goes to the adsl modem/router and the other to the internal network). E-Smith is set up as a Server and Gateway.
2. I've set up 3 virtual domains (a.com, b.com and c.com on e-smith, each pointing to its own i-bay. This works fine.
3. I now want to redirect c.com to go to a Windows web server running on the internal network. In other words, a.com and b.com will be served by e-smith and c.com served by an IIS-based windows webserver.
4. I'd like e-smith to do the redirection if possible since all my internal machines are behind the e-smith server/gateway.
5. I've mapped port 80 on my modem/router to point the e-smith server.

Is this possible? I could set up e-smith as only a server and use the adsl router to redirect to either the e-smith or the windows server, but this would be based on port number - not really suitable.

Thanks in advance...

[Darrell May]

If you want website a.com and b.com to remain on your e-smith-server and to host your c.com on your IIS server, you will need two external IP addresses.

Darrell

[Gordon Rowell]

Darrell May wrote:
>
> If you want website a.com and b.com to remain on your
> e-smith-server and to host your c.com on your IIS server, you
> will need two external IP addresses.

Actually, this should be possible with the apache Proxy or ReverseProxy
directives (I can't remember the exact details of the two).

We don't support such a configuration, but careful reading of the
Apache documentation  and customisation of the Apache configuration
should make it possible to forward a HTTP single virtual domain using
a single external IP address.

The appropriate place to discuss this is the developer list.

Gordon