Problem with WNLB with virtualised CAS Servers

Dear Experts,

I have following environment:

2 x CAS EXchange 2010 Servers
2 x MB Exchange 2010 Servers

MB Servers are configured with DAG and working fine, now i am trying to configure WNLB on CAS Servers, The operating System i have is Windows Server 2008 R2 SP1, All Servers are in same VLAN.

Issue:
I created NLB Cluster on CAS01 and all went ok, as soon as i added CAS02 in that cluster. CAS01 cannot ping to MB 02 and CAS02 cannot ping to MB 01 and vice versa.

whereas cas 01 can communicate with MB01 and CAS 02 can communicate with MB02.

Please advise asap. i am stuck with this strange issue.

Windows Server 2008ExchangeNetwork Operations

Last Comment

Akhater

8/22/2022 - Mon

ASKER CERTIFIED SOLUTION

M A

10/1/2016

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

GET A PERSONALIZED SOLUTION

Ask your own question & get feedback from real experts

Find out why thousands trust the EE community with their toughest problems.

Peter Hutchison

10/1/2016

In the WNLB console, you need to fine tune the ports to determine which ports should be load balanced and which ports are server specific. See Port Rules.
Load balanced ports: 80, 443, 25, 110, 143 etc
Server ports: ICMP for pings, File and Print sharing (SMB) etc

https://technet.microsoft.com/en-us/library/bb633031.aspx

Akhater

10/3/2016

Yous issue is due the the Hyper-Visor, you have to enable Enable MAC Address Spoofing on the NICs from inside hyperV for that to work as shown in this picture

https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/telligent.evolution.components.attachments/13/7308/00/00/03/27/24/60/MAC%20address%20spoofing.png

All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat

William Peck