OK
I want to setup a servermachine with
2003 exchange with Webmail(Virtualized)
and
Apache portal website (Virtualized)
Both are webservers and should run on one PC, so that i have webmailaccess via IIS (wildcard) and the portal website on linux.
I know... but i hope it could anyway functional
HTTPS in OWA is supported by default, it only takes a certificate and 2min config in IIS... and offers better security !
Yes it'd work. Effectively the two web server will be running on their own servers with their own IP's, even though they are on the same physical box. Your only problem, which is the same as if they were actual physical machines, is if your using NAT routing from the internet to these machines. Port 80 can only point to one of the servers, the other would have to use another port number.
External IP - 81.10.9.42
Internal IP - IIS - 192.168.11.11, Apache - 192.168.11.12
To access either server internally just punch it's Internal IP into your favourite Web browser, so http://192.168.11.11 for IIS.
If port 80 is forwarded to Apache on your router then http://81.10.9.52 would point to http://192.168.11.12
To access the IIS in this config then you would need to forward another port to it, say http://81.10.9.42:1080 -> http://192.168.11.11
Thanks for the solution
Right the problem is port 80.
I know that apache has the vhosts function like
horde.domain.com
joomla.domain.com
owa.domain.com
so i could fix this problem easy with only Apache but for Outlook Web Access i have to use IIS, actually there is no solution to host this on apache
That's the reason because i get this idea.
So at last i want to share both servers for webaccess over port 80
OWA via wildcard -> mail.portal.com
and
Apache -> portal.com
maybe there is any way that IIS gives no answer for a portal request, but the only solution which reminds me are 2 external ips
Message was edited by:
could this work?
to set the port on the iis maindirectory to 12345 and sets up a new virtual host
freebee
frebee, you can run owa over https which uses port 443, leaving port 80 for your apache
with this solution you can use a single public IP and two NAT port forwarding rules as you will be running two boxes
you can use a self signed certificate generated by either windows built in certificate server...
would this answer your needs ?
I've never used Outlook web Access. If you can't move it away from port 80 then ther may be another solution, depending on your router.
You should be able to port forward port 80 to say port 8080 on the apache box. Then the vhost can host a redirect page to yourip:1080 with your router port forwarding to the IIS on port 80.
So a request from the outside world may go something like this:
owa.domain.com -> 81.12.45.123:80 (your ip) -> apache (owa.domain.com) port 8080-> redirect page -> 81.12.45.123:1080 -> IIS port 80
HTTPS in OWA is supported by default, it only takes a certificate and 2min config in IIS... and offers better security !