In theory, this allows the Cisco device to populate its mac-address-table. That second problem stems from the fact that some vendors (like Cisco) don't accept mapping 元 unicast IP addresses to L2 multicast MAC addresses (this happens when NLB cluster operates in multicast mode - 元 unicast IP address is the NLB cluster IP address and L2 mac address is the multicast MAC address that is chose by NLB) so you have to create a static mapping on the router to avoid such a problem. KB960916 is already included in Windows 2008 SP2 Problem 2: When NLB cluster on Windows 2003 or Windows 2008 operates in multicast mode, remote subnets cannot access NLB cluster IP address. You can find more information at the two most common scenarios below: Problem 1: When NLB cluster on Windows 2008/SP2 operates in multicast mode, due to a problem with NLB implementation on 2008 remote subnets cannot access NLB cluster IP address Solution 1: - This problem was stemming from NLB implementation - This has been fixed by Microsoft with the hotfix KB960916. When Microsoft NLB cluster operates in multicast mode, in certain scenarios you may not be able to access the NLB cluster IP address from remote subnets whereas suame subnet access keeps working fine. Hi there, In today's blog, I would like to talk about NLB cluster access problems that our customers experience most of the time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |