Receive a warning about the network binding order on the Setup Support Rules page when install SQL Server 2008 in a failover cluster

Receive a warning about the network binding order on the Setup Support Rules page when install SQL Server 2008 in a failover cluster

Rate This
  • Comments 4

While installing sql server 2008 setup we might face following warning in the installation window

 Receive a warning about the network binding order on the Setup Support Rules page when  install SQL Server 2008 in a failover cluster

 The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced    configuration to change the binding order

Cause

We might see the above warning due to following reason

1)  The domain network is not the first bound network.

2) This issue may also occur when you have a disabled network adapter or a ghosted network adapter on the computer.

Note A network adapter that is enumerated in the Windows registry but that is hidden in Device Manager is called a ghosted network adapter. This issue may occur when you change a network connection's TCP/IP configuration from DHCP to a static IP. This issue may also occur when you have added and removed network adapters multiple times.

 

Resolution

SOLUTION I

=======================================================

For Disabled network adapter or ghosted network adapter we need to follow the below KB article:

 http://support.microsoft.com//kb/955963

 SOLUTION II
=======================================================

Here is the description to verify whether domain network is not the first bound network:

We get a warning message on Network Binding Order Setup Support rule:
The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced configuration to change the binding order
 

<Detail .txt >
Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet
NetworkBindingFacet: Looking up network binding order.
NetworkBindingFacet:   Network: 'Local Area Connection* 8' Device: '\Device\{4DB91193-72F1-4713-A938-EB73F27CFEC8}' Domain: '' Adapter Id: '{4DB91193-72F1-4713-A938-EB73F27CFEC8}'
NetworkBindingFacet:   Network: 'Production Team' Device: '\Device\{0BF4D354-E6E9-480C-91CF-DC598282C4C1}' Domain: 'UPHS.PENNHEALTH.PRV' Adapter Id: '{0BF4D354-E6E9-480C-91CF-DC598282C4C1}'
NetworkBindingFacet:   Network: 'Heart Beat' Device: '\Device\{5AC63784-8088-40F7-93C8-37F9CD03D445}' Domain: '' Adapter Id: '{5AC63784-8088-40F7-93C8-37F9CD03D445}'
NetworkBindingFacet:   Network: 'BackUp Network' Device: '\Device\{52AEDCB0-9E8E-4243-9D5D-ED86E602DF23}' Domain: '' Adapter Id: '{52AEDCB0-9E8E-4243-9D5D-ED86E602DF23}'
IsDomainInCorrectBindOrder: The top network interface 'Local Area Connection* 8' is bound to domain '' and the current domain is 'contoso.com'.
Evaluating rule        : IsDomainNetworkTopOfBindings
Rule running on machine: TESTLAB12
Rule evaluation done   : Warning
Rule evaluation message: The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced    configuration to change the binding order.
Send result to channel: RulesEngineNotificationChannel
</Detail.txt>

 Local Area Connection*8 has a GUID value of {4DB91193-72F1-4713-A938-EB73F27CFEC8} but we are not sure to which network adapter it corresponds to.

 To find out to which network adapter Local Area Connection *8 correspond to run the following command to list the NIC configuration:

"wmic nicconfig get description, SettingID > C:\nicconfig.txt"

 From the NIC configuration it shows that GUID value {4DB91193-72F1-4713-A938-EB73F27CFEC8} which is for Local Area Connection*8 from detail.txt corresponds to Microsoft Failover Cluster Virtual Adapter

<Nicconfig.txt>
HP NC380T PCIe DP Multifunc Gig Server Adapter                                      {52AEDCB0-9E8E-4243-9D5D-ED86E602DF23} 
HP NC380T PCIe DP Multifunc Gig Server Adapter #2                                 {5AC63784-8088-40F7-93C8-37F9CD03D445} 
WAN Miniport (IP)                                                                                      {7F583D1B-4203-4AD0-A6A0-4BD007D21735} 
HP Network Team #1                                                                                 {0BF4D354-E6E9-480C-91CF-DC598282C4C1} 
Microsoft Failover Cluster Virtual Adapter                                                    {4DB91193-72F1-4713-A938-EB73F27CFEC8} 
RAS Async Adapter                                                                                     {7C264673-3322-4312-AE60-D09B4E71E368} 
HP NC373i Multifunction Gigabit Server Adapter                                         {C6CEC36A-3D03-4C32-ACD0-2DB2851A841D} 
HP NC373i Multifunction Gigabit Server Adapter                                         {5C3D2BA3-B15C-4FBB-A093-B42C80C39B81} 
</Nicconfig.txt>

When "IsDomainNetworkTopOfBindings" rule is run by the sql server 2008 setup, it queries registry using WMI and gets the results from the following registry key :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Linkage\<Bind>

So we can check the Bind order in registry as shown

<Bind>
\Device\{4DB91193-72F1-4713-A938-EB73F27CFEC8}                                : Microsoft Failover Cluster Virtual Adapter        
\Device\{0BF4D354-E6E9-480C-91CF-DC598282C4C1}                               : HP Network Team #1                                
\Device\{5AC63784-8088-40F7-93C8-37F9CD03D445}                               : HP NC380T PCIe DP Multifunc Gig Server Adapter #2 
\Device\{52AEDCB0-9E8E-4243-9D5D-ED86E602DF23}                               : HP NC380T PCIe DP Multifunc Gig Server Adapter #2 
</Bind>

To avoid the above warning message we need to change the Bind Order and reorganize it in a way that domain bound network is top in the list. Domain bound network can be found from detail.txt
 NetworkBindingFacet:   Network: 'Production Team' Device: '\Device\{0BF4D354-E6E9-480C-91CF-DC598282C4C1}' Domain: 'contoso.com' Adapter Id: '{0BF4D354-E6E9-480C-91CF-DC598282C4C1}'

Once the binding order is changed we need to run the installation and the warning will not be reported.

Meera R Sinhasane
SE, Microsoft Sql Server

Reviewed By

Amit Banerjee
Technical Lead, Microsoft Sql Server

Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post
  • This worked well for me, just to note that I had the bindings correct in Network Connections, and I changed them in the registry.

    Is it necessary to do this also on the passive node?

  • Yes, you need to make changes on both the nodes.This was the same scenario that i ran into.

  • Thank you very much

  • “Microsoft Failover Cluster Virtual Adapter” is the first connection listed in the binding order. This is the default on Windows Server 2008. On Windows Server 2012, it is the last connection listed in the binding order.

    SQL Server 2008/2012 clustered setup is expecting the domain network to be first and hence raising the “Warning” message.

    Resolution:

    Ignore the warning message and continue with the SQL Server Setup.

    OR

    Use a public utility called ‘nvspbind from MSDN and move the “Microsoft Failover Cluster Virtual Adapter” down in the binding order and then run the SQL Server Setup. You will not be gaining anything by doing this except that you will not see the “warning” message.

    It is not recommended to modify the registry entry manually.

Page 1 of 1 (4 items)