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
elv1sAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kevinhsiehCommented:
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.
0
elv1sAuthor Commented:
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.
0
kevinhsiehCommented:
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.
0
elv1sAuthor Commented:
we moved the site to an new VM and issues fixed
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
elv1sAuthor Commented:
we moved the site to an new VM and issues fixed
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.