so first here is the architecture i'm planning :
The question is simple : Is that is possible and how manage routing in HyperV to route the 443 port on both VM or better on the right vm ?
migrated from stackoverflow.com Apr 30 '11 at 6:02
This question came from our site for professional and enthusiast programmers.
Lets say public ip is 18.104.22.168, private ip of the hyper-v host is 22.214.171.124, vm1 126.96.36.199, vm2 188.8.131.52.
If you want to route 184.108.40.206:443 to just 220.127.116.11, then your firewall rules would do nat/port redirection to get it there. If you want to route 18.104.22.168:443 to 22.214.171.124, again it is firewall rules.
Hyper-v does allow vlan tagging so you can bind the public IP straight into a VM even if the Hyper-V host is on a private IP (assuming your network infrastructure allows)
If you are trying to direct 126.96.36.199:443 to 188.8.131.52:443 if it sharepoint requests, or 184.108.40.206:443 if it is an Apache request, well that isn't something Hyper-V (or any VM platform) can do. You can probably get it working using Squid to intercept the traffic and direct the request based on the incoming domain, but that requires another host in front of your two webservers.