vangipe
asked on
Windows 2003 NLB not routed
Hi there,
I recently installed a new NLB cluster on Windows 2003 R2 SP2 x64. The config:
server 1:
- Public LAN: 172.30.200.17, SM 255.255.255.0, DG 172.30.200.1, DNS 172.30.200.11
- NLB LAN: 172.30.200.19, SM 255.255.255.0, no DG/DNS/WINS
server 2:
- Public LAN: 172.30.200.18, SM 255.255.255.0, DG 172.30.200.1, DNS 172.30.200.11
- NLB LAN: 172.30.200.20, SM 255.255.255.0, no DG/DNS/WINS
NLB cluster: IP 172.30.200.21, SM 255.255.255.0, Unicast
Server 1 has priority 1, Server 2 has priority 2.
All NICs are connected to the same segment.
Both servers have Public LAN on top in Network Bindings.
Now when I test NLB all seems to be working ok. A ping -t keeps on running when disabling the NLB LAN interfaces on either of the servers.
The problem is that the shared IP address (172.30.200.21) is not routed. From another subnet I can ping or telnet to 172.30.200.17 and .18 but not to .21. During the NLB setup I never entered a default gateway for NLB itself.
What I found is that the NLB cluster should respond over its Public NICs, is that correct?
If so, how do I configure this? If not, what else could be wrong?
Thanks in advance.
I recently installed a new NLB cluster on Windows 2003 R2 SP2 x64. The config:
server 1:
- Public LAN: 172.30.200.17, SM 255.255.255.0, DG 172.30.200.1, DNS 172.30.200.11
- NLB LAN: 172.30.200.19, SM 255.255.255.0, no DG/DNS/WINS
server 2:
- Public LAN: 172.30.200.18, SM 255.255.255.0, DG 172.30.200.1, DNS 172.30.200.11
- NLB LAN: 172.30.200.20, SM 255.255.255.0, no DG/DNS/WINS
NLB cluster: IP 172.30.200.21, SM 255.255.255.0, Unicast
Server 1 has priority 1, Server 2 has priority 2.
All NICs are connected to the same segment.
Both servers have Public LAN on top in Network Bindings.
Now when I test NLB all seems to be working ok. A ping -t keeps on running when disabling the NLB LAN interfaces on either of the servers.
The problem is that the shared IP address (172.30.200.21) is not routed. From another subnet I can ping or telnet to 172.30.200.17 and .18 but not to .21. During the NLB setup I never entered a default gateway for NLB itself.
What I found is that the NLB cluster should respond over its Public NICs, is that correct?
If so, how do I configure this? If not, what else could be wrong?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad you have solved it.
SP
SP
I have suggested the same solution (Layer 3). NLB doesn't work with Layer 3 switch.
Closed, 500 points refunded.
ForestDenizen
Community Support Moderator
ForestDenizen
Community Support Moderator
Hello there,
Can you tell me why did you accept the above solution???
Can you tell me why did you accept the above solution???
ASKER
With all due respect, you didn't suggest that solution, you asked whether there was a L3 device in between. Furthermore the problem was solved by our network engineer, not by information I received here. So thank you for your suggestions, but since they didn't contribute to the solution I won't award any points.
If I have asked you whether you are using a Layer 3 Switch or not to connect NLB Cluster then there must be something wrong with NLB when connecting to Layer 3 Switch and you also should think why I have asked you about Layer 3 Switch.
Moreover, its not about points here. We are always here to help you :)
Thanks
SP
Moreover, its not about points here. We are always here to help you :)
Thanks
SP
>>>From another subnet I can ping or telnet to 172.30.200.17 and .18 but not to .21. During the NLB setup I never entered a default gateway for NLB itself.
What do you mean by "from another subnet"? Can you please be bit more specific here? Are you using any router or layer 3 switch between subnets? Is statis ARP enabled for Cluster MAC address in router?
Let us know.