Asked by bpl5000
at 2024-08-13 18:48:20
Point:500 Replies:10 POST_ID:828745USER_ID:11655
Topic:
Microsoft IIS Web Server;;
We have a web server running IIS7 and we have a few websites on that server. My problem is that we have very few public IPs, yet we have several other web servers in our organization (Apache server, appliances, etc.). I thought maybe I could use my web server running IIS7 to redirect to the appropriate web servers. For example:
1. web1 is my server running IIS
2. I have web2.mydomain.com NAT to web1.mydomain.com
3. web1.mydomain.com has a site in IIS7 with web2.mydomain.com as the host file
This part works great, I go to web2.mydomain.com, and it goes to the web2 site I created on web1. I then want to redirect it to the web2 server, which is inside the firewall in the same vlan as web1. If I redirect it to web2.mydomain.com, inside the firewall it might work, but outside it's just going to send it right back to web1, which will send it to web2... infinite loop!
How can I go about doing this? I'm thinking I could redirect it to a port. I could have web1 redirect the site web2.mydomain.com to something like web3.mydomain.com:8000. Would this work? Is there a better way?
1. web1 is my server running IIS
2. I have web2.mydomain.com NAT to web1.mydomain.com
3. web1.mydomain.com has a site in IIS7 with web2.mydomain.com as the host file
This part works great, I go to web2.mydomain.com, and it goes to the web2 site I created on web1. I then want to redirect it to the web2 server, which is inside the firewall in the same vlan as web1. If I redirect it to web2.mydomain.com, inside the firewall it might work, but outside it's just going to send it right back to web1, which will send it to web2... infinite loop!
How can I go about doing this? I'm thinking I could redirect it to a port. I could have web1 redirect the site web2.mydomain.com to something like web3.mydomain.com:8000. Would this work? Is there a better way?