Avatar of elv1s
elv1sFlag for United States of America asked on

Dual homed web server sites going down

We have the need to run multiple websites off of our server. The issues arose when we were ubnable to get a NAT address for the latest web site and were given a public address 162.129.235.xx. So we have 2 sites runnig off of 2 nic's teamed together 10.16.198.xxx on one subnet and a third nic on a disparate subnet 162.129.235.xx running another website. After random amounts of time the sites go down. When they are down i can not ping the IP's from another computer but can from the server itself. Would the addition of a static route in the servers routing table fix this?  Basically being thown to wolves at this moment. No worries though AHHH
Windows Server 2003Microsoft IIS Web ServerInternet Protocols

Avatar of undefined
Last Comment
elv1s

8/22/2022 - Mon
kevinhsieh

You can't do it. You need all IP addresses on your website to be on the same subnet, or you won't be able to route properly. If you aren't using SSL, you can host multiple web sites on the same IP address.

I don't understand what you mean by you couldn't get a NAT address. You say that you currently are using 10.16.198.xxx on your interfaces. What do those NAT to, and can you get another public IP address in that same range? If you can't, than the 162.129.235.xx should get assigned to your NAT device, and you need to NAT it to 10.16.198.xxx. But again, best thing to do is host on the existing IP address and use host headers to distinguish between the sites, as long as you are not using SSL.
ASKER
elv1s

My organization is large and the group that issued the NAT address years ago no longer issues NAT ip address's. We wanted the new site to have SSL so we requested a public ip 162.129.235.xx. The NAT'ed  10.16.198.xxx traslates to 162.129.252.xxx. I will look into why we can not move the existing sites to one IP via host headers and use an existing
NAT'ed IP on the non teamed nic for the SSL site.
kevinhsieh

I don't understand large organizations. It should be harder to get a public IP than a public IP. Public IPs should never be assigned directly to a computer unless there is a transparent firewall somewhere protecting the resource. The NAT device normally provides that function.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
ASKER CERTIFIED SOLUTION
elv1s

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
elv1s

we moved the site to an new VM and issues fixed