Windows Network Load Balancing - Virtual MAC Address

Hi All,
I have environment that running 2 Exchange 2010 server with CASHT and join windows network load balancing as a node.
My question is,
If NLB service is restart, is it virtual MAC Address for NLB will change to new virtual MAC Address?
Thanks for response,
Best Regards,
Henry Stefanus

Hi Henry Stefanus,
The NLB work mechanism will not change whether what higher application we used and I am not very familiar with Exchange NLB architecture, may the following KB and article
may help you.
When you use the unicast method, all cluster hosts share an identical unicast MAC address. Network Load Balancing overwrites the original MAC address of the cluster adapter
with the unicast MAC address that is assigned to all the cluster hosts.
When you use the multicast method, each cluster host retains the original MAC address of the adapter. In addition to the original MAC address of the adapter, the adapter is
assigned a multicast MAC address, which is shared by all cluster hosts. The incoming client requests are sent to all cluster hosts by using the multicast MAC address.
Selecting the Unicast or Multicast Method of Distributing Incoming Requests
http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
The related third party article:
Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
http://blog.morecoffeeany1.com/2010/03/19/building-nlb-exchange-2010-rtm-cas-ht-servers-hyper-v-%E2%80%93-part-1/
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Host Unreachable intermittently within a Windows Network Load Balancing Cluster

Hi,
We have 2 Windows 2008 R2 servers running multiple IIS web sites and load balanced across Windows Network Load Balancer in unicast mode. Although there are two interfaces in each server, only 1 interface in each server participates in load balancing and
other interface is used for a different backup LAN. The problem I am going to mention was not seen within the NLB for almost 1 year.
I have noticed intermittent "host unreachable" detected from NLB in each host from time to time since 3 weeks ago. After servers are rebooted, both hosts can be reached and can be detected from NLB manager. However it becomes unreachable in both
servers within minutes and then becomes reachable again after several minutes. This behavior is noticed in the load balancer and pings do not work between the two hosts when the issue occurs. I did a packet capture to see what was going on with ARP message
when the issue occurs. ARP entry goes missing in each server when the problem occurs and no ARP replies are returned from each server. But ARP requests are dispatched from both servers when the issue occurs. ARP replies come back after sometime after which
hosts become reachable again.
I tried to create a permanent static ARP entry (By copying the MAC address from ARP table when the two hosts are reachable) in each host but that hasn't solved the issue either. It seems like the individual MAC address generated by each host is a virtual
one and it doesn't seem to respond when the problem occurs.
However load balancing and web sites are fully functional without any issues even while "host unreachability" issue is detected.
Appreciate if someone could help me to dig the real problem out.
Thank you.

Hi,
Did you do some change of your network or the NLB firewall settings recently?
If you are using the NLB cluster in Hyper-V guest vm you need to enable the spoofing of MAC address.
The related article:
Cannot access the virtual or dedicated IP address of an NLB node (Guest) running in Unicast Mode on Windows Server 2008 R2 Hyper-V
http://blogs.technet.com/b/networking/archive/2010/02/12/cannot-access-the-virtual-or-dedicated-ip-address-of-an-nlb-node-guest-running-in-unicast-mode-on-windows-server-2008-r2-hyper-v.aspx
More information:
Selecting the Unicast or Multicast Method of Distributing Incoming Requests
http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
Single network adapter
http://technet.microsoft.com/en-us/library/cc776178(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Server 2012 R2 - ADFS/Windows Network Load Balancing Converging Issue

Hello,
My name is Brandon. We have started upgrading our servers to Windows Server 2012 R2. We have some powerful servers for running ESXI 5.5 as the OS with the Guest Operating Systems as Windows Server 2012 R2. As far of our migrations/upgrades we have configured
ADFS 2012 R2 into a Server Farm with Windows Network Load Balancing to add redundancy in the event a server goes down.
I have been having issues with a Node with the Cluster getting stuck in the Status of Converging. The only way I have been able to get it back up is to restart the virtual server completely and it is temporary. When I first configure the Cluster the two
virtual servers get added to the Node with no problems and fully converge. However, after some time a node will end up in Converging and this takes Authentication for ADFS down as the nodes can not be contacted over Port 443.
Error: Host: server.domain.com Unable to connect to "server name"
System
Provider
[ Name]
Microsoft-Windows-NLB
[ Guid]
{F22AF71F-C4C3-425D-9653-B2F47B85DD30}
EventID
21
I have tried using 1 & 2 Virtual NICs on the machines and still end up with communication issues. Could someone assist me with why I am having this issue? This is not an issue with a firewall. If it was a firewall it would never communicate the first
time. Has anyone had experience with a similar configuration and how were you able to make it work?
Below is my configuration.
Static ARP Entry for Cluster IP Address has been added to our Layer 3 switch.
Physical Server 1:
ESXI 5.5 HOST
1 NIC CONNECTED (shared with virtual guest)
IP ADDRESS: 192.168.0.5
SUBNET: 255.255.255.0
DGW: 192.168.0.1
Virtual Server 1 (Guest OS)
Physical Server 2:
ESXI 5.5 HOST
1 NIC CONNECTED (shared with virtual guest)
IP ADDRESS: 192.168.0.6
SUBNET: 255.255.255.0
DGW: 192.168.0.1
Virtual Server 2 (Guest OS)
Virtual Servers
Virtual Server 1
MS SERVER 2012 R2 (VIRTUAL)
NLB NODE 2
VIRTUAL NETWORK ADAPTERS
VNIC1 IP ADDRESS 192.168.0.10
SUBNET: 255.255.255.0
DGW: 192.168.0.1
VNIC 2 (NLB)
IP ADDRESS: 192.168.0.11
SUBNET: 255.255.255.0
Virtual Server 2
MS SERVER 2012 R2 (VIRTUAL)
NLB NODE 2
VIRTUAL NETWORK ADAPTERS
VNIC1
IP ADDRESS 192.168.0.20
SUBNET: 255.255.255.0
DGW: 192.168.0.1
VNIC 2 (NLB)
IP ADDRESS: 192.168.0.21
SUBNET: 255.255.255.0
Cluster Configuration/Properties
CLUSTER PROPERTIES CLUSTER IP: 192.168.0.30
CLUSTER SUBNET: 255.255.255.0
FULL INTERNET NAME: FS.DOMAIN.COM
CLUSTER OPERATION MODE: MULTICAST
PORT RULES:
CLUSTER IP ADDRESS
START
END
PROTOCAL
MODE
PRIORITY
LOAD
AFFINITY
ALL
80
80
BOTH
MULTIPLE
EQUAL
NONE
ALL
443
443
BOTH
MULTIPLE
EQUAL
NONE
CLUSTER NODES:
1.) SERVER1.DOMAIN.COM
a. IP: 192.168.0.11
2.) SERVER2.DOMAIN.COM
a. IP: 192.168.0.21

Hi,
According to your description, my understanding is that：2 ESXI 5.5 physical devices (192.168.0.5 and 192.168.0.6), each of them has a virtual WS 2012 R2(192.168.0.10 and 192.168.0.20). Cluster the 2 virtual servers successfully, but they corrupt with event
ID 21, and a restart of virtual device will resolve this problem temporarily.
Event ID 21 means that NLB failed to converge due to inconsistencies in the port rules between this host and cluster host. This will occur if the number of port rules or the type of port rules are different between hosts.
Ensure that all NLB hosts have identical port rules. Detailed steps you may reference:
Event ID 21 — NLB Port Rules Configuration
https://technet.microsoft.com/en-us/library/dd364034%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Windows Server 2012 R2 - Windows Network Load Balancing Converging Issue

Hello,
My name is Brandon. We have started upgrading our servers to Windows Server 2012 R2. We have some powerful servers for running ESXI 5.5 as the OS with the Guest Operating Systems as Windows Server 2012 R2. As far of our migrations/upgrades we have configured
ADFS 2012 R2 into a Server Farm with Windows Network Load Balancing to add redundancy in the event a server goes down.
I have been having issues with a Node with the Cluster getting stuck in the Status of Converging. The only way I have been able to get it back up is to restart the virtual server completely and it is temporary. When I first configure the Cluster the two
virtual servers get added to the Node with no problems and fully converge. However, after some time a node will end up in Converging and this takes Authentication for ADFS down as the nodes can not be contacted over Port 443.
Error: Host: server.domain.com Unable to connect to "server name"
System
Provider
Name]
Microsoft-Windows-NLB
Guid]
{F22AF71F-C4C3-425D-9653-B2F47B85DD30}
EventID
21
I have tried using 1 & 2 Virtual NICs on the machines and still receive this error even if only 1 VNIC is assigned to the virtual machine. Could someone assist me with why I am having this issue? Has anyone had experience with a similar configuration
and how were you able to make it work?
Below is my configuration.
Static ARP Entry for Cluster IP Address has been added to our Layer 3 switch.
Physical Server 1:
ESXI 5.5 HOST
1 NIC CONNECTED (shared with virtual guest)
IP ADDRESS: 192.168.0.5
SUBNET: 255.255.255.0
DGW: 192.168.0.1
Virtual Server 1
Physical Server 2:
ESXI 5.5 HOST
1 NIC CONNECTED (shared with virtual guest)
IP ADDRESS: 192.168.0.6
SUBNET: 255.255.255.0
DGW: 192.168.0.1
Virtual Server 2
Virtual Servers
Virtual Server 1
MS SERVER 2012 R2 (VIRTUAL)
NLB NODE
2 – VIRTUAL NETWORK ADAPTERS
VNIC1
IP ADDRESS 192.168.0.10
SUBNET: 255.255.255.0
DGW: 192.168.0.1
VNIC 2 (NLB)
IP ADDRESS: 192.168.0.11
SUBNET: 255.255.255.0
Virtual Server 2
MS SERVER 2012 R2 (VIRTUAL)
NLB NODE
2 – VIRTUAL NETWORK ADAPTERS
VNIC1
IP ADDRESS 192.168.0.20
SUBNET: 255.255.255.0
DGW: 192.168.0.1
VNIC 2 (NLB)
IP ADDRESS: 192.168.0.21
SUBNET: 255.255.255.0
Cluster Configuration/Properties
CLUSTER PROPERTIES
CLUSTER IP: 192.168.0.30
CLUSTER SUBNET: 255.255.255.0
FULL INTERNET NAME: FS.DOMAIN.COM
CLUSTER OPERATION MODE: MULTICAST
PORT RULES:
CLUSTER IP ADDRESS  START END PROTOCAL MODE   PRIORITY LOAD  AFFINITY
ALL    80 80 BOTH  MULTIPLE  ..  EQUAL  NONE
ALL    443 443 BOTH  MULTIPLE  ..  EQUAL  NONE
CLUSTER NODES:
1.) SERVER1.DOMAIN.COM
a. IP: 192.168.0.11
2.) SERVER2.DOMAIN.COM
a. IP: 192.168.0.21

Thank you for your response. It took me a while to figure it out, but the whole issue was related to the type of Virtual Network Adapter I was selecting.
I changed the network adapter from E1000 to VMXNET 3 and have not had a single error in the event logs or Windows NLB.
I read somewhere that VMXNET 3 is preferred for Windows Server 2012 R2.
https://communities.vmware.com/thread/433792
Leyuka       May 23, 2013 6:14 AM
"Just a help for everyone with this problem :
After 10 days of research for our virtual datacenter behind a vcloud as iias , i found a solution .
I only run windows 2012 server .
Install vmware tools , remove e1000 network card after a vm stop, add a card same vswitch etc BUT with a vmxnet3 TYPE . DONT USE DEFAULT CARD
Start and enjoy this solution . E1000 and E1000e are just unstable in windows8 / windows 2012 , the network card reset randomly with or without heavy IO. No log in windows , and as a vcloud user i don"t have esxi logs (damn i don't like cloud) and provider
don"t know why ..."

Windows Network Load Balancing (WNLB) in Azure VM

Is WLNB supported in Azure VM? If you have to use DHCP, how would you assign an IP (VIP) through the WNLB manager?

Apology.
Here is my take.
1) I am assuming you will be running Azure VM in this case since you are bound to use Windows NLB. Then probably you want to set up Virtual Network. - This will ensure that the IP addresses that is assigned to each VM doesn't change.
2) It really depends on what is your usage is for to use Windows NLB, but the price compared to using Traffic Manager in Azure is way lower than running a VM that is hosting Windows NLB.
Just my 2 cents and I would love to hear your feedback.
Cheers.
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Milton Goh
MCSE, MCSA, MCITP, MOF, ITIL, AIIM SharePoint Specialist
Blog |
Twitter

Windows Network Load Balancing not working

OS: Windows Server 2008 R2
Tested in our environment both are able to talk to each other. One will be converged as DEFAULT and another will be just converged.
When deployed at Customer site, Server1 is converged as Default as seen in Server1.
Server 2 is converged as Default as seen in Server 2.
Server1 and 2 are in the same subnet and have no firewalls in between. (They seem unable to detect each other)
NLB Configurations is using multicast.
Would like to know how to resolve this issue.

Hi,
First, please try to ping each other with FQDN on the servers.
Also, please make sure that the servers are connected to a layer2 switch or hub.
To verify if this issue is caused by the misconfigure of the network device, pleae try to connect these servers to a hub for the test.
Besides, is there any warning or error related to this issue in the event viewer of these servers?
Here is a troubshooting guide for NLB, it may be helpful,
http://technet.microsoft.com/en-us/library/cc732592.aspx#BKMK_N
Best Regards.
Steven Lee
TechNet Community Support

Network Load Balance in BizTalk

Hi All,
following is my senario, we have two biztalk nodes on same BizTalk Group, Group was configured on SQL-Cluster(Active-Pasive).
In my DNS, network administrator configured hardware NLB, and configured my BizTalk nodes IPs on NLB provided us load balancer IP.
my question is "Do I need to install and configure the windows network load balance on BizTalk both nodes with load balancer IP?". or simple create hosts and hostinstances for separete nodes?
I have to maintain load balance for following Adapters.
HTTP(WCFBasicHTTP),SOAP, File, WCF-SQL.
Please help me.
Thanks in Advance,
Teegala.
Teegala

Since you have an external hardware NLB you DO NOT need to install Windows NLBS.
To get your HTTP/SOAP/WCF Receive Endpoints to get Load Balanced, you'd need to ensure that your IIS on BOTH the nodes is identically configured. On the BizTalk You need to have the same Receive Host Instances on BOTH the nodes. The external NLB would do
the rest.
Refer http://msdn.microsoft.com/en-us/library/aa577415.aspx
Regards.

Network Load Balancing for AFP Sharing

Dear all,
Anyone can kindly teach me how can I configure network load balancing with 2 xserve?
Currently I success to bond 6 ethernet port with a virtual IP in a single machine and I have a link aggregation setup in my switch. It works fine.
How to configure 2 xserve with 6 ethernet port per each to have a single virtual IP?
my switch do not support link aggregation with a virtual IP to do the load balancing so I just can consider to do it in software level.
Anyone know whether OS Leopard/Snow Leopard can do it? Or any suggestion for 3rd party software can perform this?
Thanks expert!
Karl

It sounds like you need a load balancer. There's nothing built-in to Mac OS X Server that's going to support one virtual IP address shared across multiple physical servers.
Your problem, though, is likely to be one of throughput - I don't know any cheap load balancers that will sustain that kind of throughput, so you may be looking at some serious $$$$s.
There are some software-based load balancers that might be able to handle the load balancing side of things but many of them are designed around HTTP so might not work so well for other protocols.
In addition, the software load balancer is going to suffer the same bottleneck as your AFP server, but doubly so - two servers with 6 x 1gbps links each you have a theoretical limit of 12gbps.
To run that through a load balancer, the load balancer will need double that - 12gbps for the client-side, plus 12gbps for the server side. In reality you're probably looking at needing 10gbps interfaces and switches if you're really pulling that much bandwidth.

Network Load Balancing - Multicast IPv6

I have a two servers with network load balancing. They are configured to use IGMP Multicast which works well with IPv4. The switch correctly detects the group and sends the traffic to only the ports connected to the servers.
However i can't get IPv6 working outside of the servers subnet. You can access the loadbalanced IPv6 address from within the servers subnet but machines outside the subnet cannot access it.
Does load balancing properly support IPv6? Should it not support Multicast Listerner Discovery (MLD) to work properly with IPv6?
Thanks

Thanks for your reply.
Yes - you are correct. We are using an IPv6 address as the cluster IP address for incoming connections but it can't be access outside of the subnet. The cluster has both a link-local and global address - both are only accessible from within the subnet.
The two servers that are part of load balancing cluster both have IPv6 address assigned to their network adapters - these are accesible outside the subnet. Infact 80% of all our network traffic is IPv6 - routing is working fine between all servers, workstations
and devices on our various subnets. The problem is purley affecting the load balancing IPv6 address.
The IP config and route tables are below. Thanks for your help.
Regards, Daniel
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
M:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : indium
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :
Ethernet adapter Public:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
pter
Physical Address. . . . . . . . . : 00-15-5D-CA-6C-04
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::42(Preferred)
IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::40(Preferred)
Link-local IPv6 Address . . . . . : fe80::4c7b:41a3:be85:e6c4%10(Preferred)
Link-local IPv6 Address . . . . . : fe80::95f6:2da7:dcdb:1fc1%10(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.42(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IPv4 Address. . . . . . . . . . . : 10.0.0.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 2001:630:34:1010::1
10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 234886493
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-D0-9F-CD-00-15-5D-01-14-35
DNS Servers . . . . . . . . . . . : 2001:630:34:1010::10
2001:630:34:1010::8
10.0.0.10
10.0.0.8
NetBIOS over Tcpip. . . . . . . . : Disabled
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
M:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : aluminium
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :
Ethernet adapter Public:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
pter
Physical Address. . . . . . . . . : 00-15-5D-01-37-04
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::43(Preferred)
IPv6 Address. . . . . . . . . . . : 2001:630:34:1010::40(Preferred)
Link-local IPv6 Address . . . . . : fe80::95f6:2da7:dcdb:1fc1%10(Preferred)
Link-local IPv6 Address . . . . . : fe80::fcab:aeb9:175d:9994%10(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.43(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IPv4 Address. . . . . . . . . . . : 10.0.0.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 2001:630:34:1010::1
10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 234886493
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-BF-55-42-00-15-5D-01-13-45
DNS Servers . . . . . . . . . . . : 2001:630:34:1010::10
2001:630:34:1010::8
10.0.0.10
10.0.0.8
NetBIOS over Tcpip. . . . . . . . : Disabled
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
M:\>route print
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
10 261 ::/0 2001:630:34:1010::1
1 306 ::1/128 On-link
10 261 2001:630:34:1010::/64 On-link
10 261 2001:630:34:1010::40/128 On-link
10 261 2001:630:34:1010::42/128 On-link
10 261 fe80::/64 On-link
10 261 fe80::4c7b:41a3:be85:e6c4/128
On-link
10 261 fe80::95f6:2da7:dcdb:1fc1/128
On-link
1 306 ff00::/8 On-link
10 261 ff00::/8 On-link
===========================================================================
Persistent Routes:
If Metric Network Destination Gateway
0 4294967295 ::/0 2001:630:34:1010::1
===========================================================================

Hyper-V 2012 R2 & NLB (Network Load Balancing) with Unicast on VMs

Hi,
We set up a 2012 R2 Hyper-V Cluster. On this Cluster we would like to run 2 VM's which are using NLB (Network load Balancing) in Unicast mode.
We have created a External Virtual Switch wich is connected trough a 3x10GB LACP Team to a Cisco Nexux Switch.
We have tried to set the NLB up in the way we did with 2008 R2 but we were not be able to get this working. Is there any Change in 2012 R2 we did not think about?
Each time we form the Cluster one Node becomes unavailable.
Timo

Check the virtual network adapter properties - you must enable MAC address spoofing. We had the same issues.
Note that this will absolutely pollute your host machine's system log with tons of spam and make it pretty much worthless. I'm trying to find a way around this as we speak, actually.

Bug with Network Load Balancing Services and SkipAsSource always reverting to true

Steps to reproduce:
Add an IP address to the cluster (2 nodes running Windows Server 2012) using the Network Load Balancing Manager
Using PowerShell set the SkipAsSource flag on the IP Address to true (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $true). The flag is correctly set.
Try to reverse the setting (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $false). Flag stays as true.
It appears as though Network Load Balancing Services is remembering the setting from someone.
Things I've tried all without success (in no particular order):
Removing the IP address from the cluster and adding it back in
Using PowerShell to remove the IP address and add it back in manually (on each host).Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
Using netsh to remove the IP address and add it back in manually (on each host). Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
Deleting each host from the cluster (one at a time), removing the registry keys CurrentControlSet\Services\WLBS and
Removing both hosts from the cluster
Restarting the hosts
Using processmon (sysinternals) to try and find a registry entry that might be set when SkipAsSource is set
Does anyone know:
How to resolve this issue? I'm guessing resetting the TCP/IP stack would work but that's a last resort as it requires an on sight visit to the datacentre.
Where the SkipAsSource flag it stored?
How to reset the master/global cluster config?
Thank in advance,
Antony

Hi Antony,
I am trying to involve someone familiar with this topic to further look at this issue.
There might be some time delay. Appreciate your patience.
Best Regards.
Steven Lee
TechNet Community Support

Set up Network Load Balancing on an Azure VM

i have an VM on Azure, on which I have two AD LDS instances. I want to set up Network Load Balancing to have fault tolerance between the two AD LDS instances. when i start to create a new cluster, it shows me a message that DHCP will be turned off. i ignored
that one time, and what conspired was that i was unable to access the VM only. i had to set up my AD LDS instance on a different VM again.
is there any way which will enable me to set up the AD LDS instance properly on the VM?

Hi,
Firstly, if I understand correctly, you set up a cluster with only one VM? Based on my experience, you need to use two Azure VMs running AD LDS to configure Failover cluster.
In addition, did you mean that you cannot RDP into the VM after you created the cluster? If yes, which kind of error message you have received? Please check the Quick Glance of that VM on the
Azure management portal to make sure that all the parameters for that VM are displaying, especially for the internal IP address.
Furthermore, it seems that the question is related to Azure Virtual Machines, I recommend you to ask in Azure Virtual Machine forum below for further assistance:
https://social.msdn.microsoft.com/Forums/en-US/home?forum=WAVirtualMachinesforWindows
Best regards,
Susie

Network Load Balancing - "access denied" when loading configuration information from host2

We have 2 Windows 2012 R2 servers, both are running on workgroup.
We set up NLB cluster. When we open NLB Manager on the server2, then message shows "loading configuration information. Access denied. Error connecting to server1".
There is no issue doing this on server1, NLB Manager is able to connect to both servers. We login using default administrator account, both account name and password are the same for 2 servers.
When we check security event log on server1, there is this strange Audit Failure log using account "test_nlb" from server2 which related to "Access denied" error. Please let us know how to resolve this. Thanks in advance.
      Event ID: 4776
      The computer attempted to validate the credentials for an account.
      Authentication Package:
MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
      Logon Account:
test_nlb
      Source Workstation:
WPAAP2
      Error Code:
0xc0000064
      An account failed to log on.
Event ID: 4625
Subject:
    Security ID:
S-1-0-0
    Account Name:
    Account Domain:
    Logon ID:
0x0
Logon Type:
3
Account For Which Logon Failed:
    Security ID:
S-1-0-0
    Account Name:
test_nlb
   Account Domain:
WPAAP2
Failure Information:
    Failure Reason:
Unknown user name or bad password.
    Status:
0xc000006d
    Sub Status:
0xc0000064
Process Information:
    Caller Process ID:
0x0
    Caller Process Name:
Network Information:
    Workstation Name:
WPAAP2
    Source Network Address:
192.168.70.45
    Source Port:
55136
Detailed Authentication Information:
    Logon Process:
NtLmSsp
    Authentication Package:
NTLM
    Transited Services:
    Package Name (NTLM only):
    Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Hi Zhong Gang,
When you are using Network Load Balancing (NLB) Manager, you must be a member of the Administrators group on the host that you are configuring, or you must have been delegated
the appropriate authority. If you are configuring a cluster or host by running NLB Manager from a computer that is not part of the cluster, you do not have to be a member of the Administrators group on that computer. Please disable your nodes firewall and
try again.
The related KB:
Add a Host to the Network Load Balancing Cluster
http://technet.microsoft.com/en-us/library/cc753744.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Network Load Balancing not failing over properly

I have 2 MS 2012 servers setup in a NLB unicast configuration, with 2 NICs each on the same subnet. When I take down the second server (and only the second server) the FQDN goes offline. Below are the ipconfigs for each server. Any help
would be greatly appreciated!
Ethernet adapter Data NIC 192.168.220.172:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) I350 Gigabit Network
#4
   Physical Address. . . . . . . . . : 6C-3B-E5-B2-48-60
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.220.172(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.220.1
   DNS Servers . . . . . . . . . . . : 192.168.220.100
                                       192.168.200.10
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster NIC:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Broadcom BCM57810 NetXtreme II
DIS VBD Client) #67
   Physical Address. . . . . . . . . : 02-BF-C0-A8-DC-AA
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.220.171(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 192.168.220.170(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.220.1
   DNS Servers . . . . . . . . . . . : 192.168.220.100
                                       192.168.200.10
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Data NIC 192.168.220.174:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : HP FlexFabric 10Gb 2-port 533FLR-
r #54
   Physical Address. . . . . . . . . : A0-D3-C1-F6-96-08
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.220.174(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.220.1
   DNS Servers . . . . . . . . . . . : 192.168.220.100
                                       192.168.200.10
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Cluster NIC:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : HP NC523SFP 10Gb 2-port Server Ad
   Physical Address. . . . . . . . . : 02-BF-C0-A8-DC-AA
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.220.173(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 192.168.220.170(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.220.1
   DNS Servers . . . . . . . . . . . : 192.168.220.100
                                       192.168.200.10
   NetBIOS over Tcpip. . . . . . . . : Enabled

Hi MS DEF,
A second network adapter is required to provide peer-to-peer communication between cluster hosts. Please isolate your heartbeat network. With unicast when cluster is connected
to a switch, incoming packets are sent to all the ports on the switch, which can cause switch flooding, please confirm you have setup your switch correct, you can refer the following Cisco Switch related unicast configuration.
The Cisco switch unicast related information:
How to configure Microsoft Network Load Balancing on two switches
https://supportforums.cisco.com/discussion/11918276/how-configure-microsoft-network-load-balancing-two-switches
More information:
Selecting the Unicast or Multicast Method of Distributing Incoming Requests
http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
An Optimal Network Load Balancing (NLB) Configuration
http://blogs.technet.com/b/clint_huffman/archive/2007/10/08/an-optimal-network-load-balancing-nlb-configuration.aspx
Selecting the Unicast or Multicast Method of Distributing Incoming Requests
http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Network Load balancing for Server 2003 and Server 2012

Our environment currently has 2 web servers running Windows Server 2003 with Network Load Balancing. We are looking to update the servers to Windows Server 2012. Is it possible to add Windows Server 2012 into the Windows Server 2003 Network Load
balancing cluster? This way we could bring up 2 new servers add them into the network load balancing and then take out the 2003 servers without disrupting our production.
Any thoughts or suggestions on how to make this work properly?

Hi,
You can upgrade an existing Network Load Balancing (NLB) cluster to Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 by taking the entire cluster offline
and upgrading all the hosts, or you can leave the NLB cluster online and perform a rolling upgrade. A rolling upgrade entails taking individual cluster hosts offline one at a time, upgrading each host, and returning the host to the cluster. You continue upgrading
individual cluster hosts until the entire cluster is upgraded. A rolling upgrade allows the cluster to continue running during the upgrade.
The related KB:
Upgrading an Existing Network Load Balancing Cluster
http://technet.microsoft.com/en-us/library/cc731691(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Network Load Balancing - Virtual MAC Address

Similar Messages

Maybe you are looking for