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
Last Comment
ASKER
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.
NAT'ed IP on the non teamed nic for the SSL site.
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.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
we moved the site to an new VM and issues fixed
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
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.