Right they totally are I have done NLB a bunch of times on 2003 but this is my first 2008. My config looks like this:
NIC1: 192.168.200.7/24/192.168.200.1 NIC2: 10.10.10.10/24/no gw NIC1:192.168.200.9/24/192.168.200.1 NIC2:10.10.10.11/24/no gw When I go in and enable NLB the IP's show 0.0.0.0 however if you do an ipconfig the ip's are there. Now, when I goto setup the cluster if I select the 10.10.10.10 or 10.10.10.11 it shows me both NICs of each server. If I bind to the 10.x IP's and then add the IP's 192.168.200.20-.30 the NLB works internally but wont traverse the firewall. If I bind the NLB to the 192.168.200.7 and .9 and then add the IP's it works internally and externally. I was always under the impression you put the heartbeat on a separate nic/subnet and that bonds the two for that IP set. That's how I always do it in 2003 but its definitely not working in 2008 this way for whatever reason. The technet walk through was basically the same thing, create a second subnet, run in unicast mode, and bind them. So not sure what Im doing wrong/differently then Ive always done in the past. From: Michael B. Smith [mailto:[email protected]] Sent: Thursday, September 24, 2009 8:38 AM To: NT System Admin Issues Subject: RE: NLB w/ 2008 i don't know what you mean by this statement: "I see on the 2008 NICS they all have 0.0.0.0 in them but apparently this is ok". you should have a default gateway on the NLB network and NO default getway on the heartbeat network. your public and private networks must be different networks. _____ From: Benjamin Zachary - Lists [[email protected]] Sent: Wednesday, September 23, 2009 10:44 PM To: NT System Admin Issues Subject: NLB w/ 2008 I have two webservers w/ 2008 standard with dual nics. The nics have two different ips in different subnets (192.168.200.x and 10.10.10.x). I created an NLB and added ip's 192.168.200.20-30 into the cluster. Im using the 10.10.10.x network for the dedicated heartbeat. Internally this works just fine and I can hit the website by its IP on http/https (Im listening to 80/443 in the cluster). >From the firewall this works as well, however from the outside this does *NOT* work. The traffic passes the firewall successfully and is nat'ed to the right IP set but there is no response. I see on the 2008 NICS they all have 0.0.0.0 in them but apparently this is ok? The only thing I can think of is somewhere there is an issue with the NLB seeing the gateway. I only have 1 gateway and each server in the cluster can see the internet. I thought maybe the cluster wasn't setup right so I tried redoing it and just putting 1 server in and had the same result. Anyone seen this? I can't think of what to even look for. I was thinking maybe the different subnet ip's are the problem but I have this working just fine in a 2003 setup just fine with basically the exact same settings. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
