Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I would like to have a setup where I can tell any of two servers to be the "main"-server on a specific IP (for redundancy reasons). Both servers should be accessible at any given time but only one should respond to public IP.

IP-restriction is because of infrastructure dependencies beyond my control.

share|improve this question

Sounds like a job for windows Network Load Balancing service. Which doesn't necessarily do load balancing, you can specify a primary node and just use the secondary node for failover.

NLB is fairly straight forward to configure, you need 3 IP address in total (one per server and a virtual IP for the web service).

share|improve this answer
I'll look into it! – Toft Apr 1 '11 at 9:02

I believe I found a rather simple solution that will work for us:

Excerpt: Modules: ARR, URL rewriter

“For a very simple reverse proxy, all you have to do is:

  1. Select the server node on inetmgr.

  2. Double click on Application Request Routing icon.

  3. Select/check “Enable proxy”.

  4. Select/check “Use URL Rewrite to inspect incoming requests.

  5. Enter the server of where you want to route the request to in “Reverse proxy” – ie. (

Our setup would be: www1, www2 - internal names for servers, these are referenced by separate IIS7 instance (responding to public IP and domain) which reverse proxies www1 or www2 as we please. ARR can be scripted too which would enable us to implement event-driven scenarios.

share|improve this answer
You'll need to use some form of LB with that to ensure redundancy of the r-proxy host too. – TristanK Apr 2 '11 at 1:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.