I am fairly new to IIS and I have been tasked with setting up a 2 node IIS loadbalanced site. This will be for internal domain use (single Domain). Here is what I want to be able to do. We will have 2 nodes in the NLB cluster. Node 1 will be at Site
A (10.10.x.x, 10.1.x.x 10.40.x.x subnets). Node 2 will be at Site B (10.20.x.x, 10.23.x.x, 10.28.x.x subnets). I want to configure a preferred server to use based on the clients source IP address. And if either server fails all requests will go to either
node1 or node2. Can this be done?
I'm not sure that NLB is your solution here. Assuming that we are talking about internal users then perhaps Active Dirctory Sites will allow you to 'prefer' one server depending on the client location. I'm not an Active Directory specialist so this needs
some investigation to figure this way out.
What you are describing is Policy based routing and is not supported by Windows networking. It is in the later versions of Linux - Vyatta has a community edition Linux based product [http://www.vyatta.com/downloads/index.php] and you may be able to try
some networking scenarios out in your lab cheaply.
DNS round robin doesn't know if a server has failed so it isn't resilient, only load balancing. It doesn't address the 'find the local server' requirement either.
My take on the requirement is the need for reduced WAN traffic and increased availability. This address neither.
If my understanding of the requirements is wrong then my solution suggested may not be right.
sjkeith77
1 Post
IIS Load Balancing based on source IP
Nov 03, 2009 03:06 PM|LINK
Hello,
I am fairly new to IIS and I have been tasked with setting up a 2 node IIS loadbalanced site. This will be for internal domain use (single Domain). Here is what I want to be able to do. We will have 2 nodes in the NLB cluster. Node 1 will be at Site A (10.10.x.x, 10.1.x.x 10.40.x.x subnets). Node 2 will be at Site B (10.20.x.x, 10.23.x.x, 10.28.x.x subnets). I want to configure a preferred server to use based on the clients source IP address. And if either server fails all requests will go to either node1 or node2. Can this be done?
jeff@zina.co...
3379 Posts
MVP
Moderator
Re: IIS Load Balancing based on source IP
Nov 03, 2009 03:31 PM|LINK
Might want to start by looking at:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/0baca8b1-73b9-4cd2-ab9c-654d88d05b4f.mspx?mfr=true
Jeff
j_easter
3 Posts
Re: IIS Load Balancing based on source IP
Feb 12, 2010 10:17 AM|LINK
I'm not sure that NLB is your solution here. Assuming that we are talking about internal users then perhaps Active Dirctory Sites will allow you to 'prefer' one server depending on the client location. I'm not an Active Directory specialist so this needs some investigation to figure this way out.
What you are describing is Policy based routing and is not supported by Windows networking. It is in the later versions of Linux - Vyatta has a community edition Linux based product [http://www.vyatta.com/downloads/index.php] and you may be able to try some networking scenarios out in your lab cheaply.
lexusplus
6 Posts
Re: IIS Load Balancing based on source IP
Mar 29, 2010 09:25 PM|LINK
can't we use DNS based balancing ? DNS round robin or similar ?
premature ejaculation treatmentj_easter
3 Posts
Re: IIS Load Balancing based on source IP
Apr 03, 2010 10:58 AM|LINK
DNS round robin doesn't know if a server has failed so it isn't resilient, only load balancing. It doesn't address the 'find the local server' requirement either.
My take on the requirement is the need for reduced WAN traffic and increased availability. This address neither.
If my understanding of the requirements is wrong then my solution suggested may not be right.