Network binding order

Question

Post reply

Network binding order

sudhakara

SSCrazy Eights

Points: 9425
More actions
July 29, 2009 at 5:47 am

#203256

Hi..
I Am getting the following waring message while installing the sql server 2008 cluster x64 in windows x64 2008 server .
"Rule "Network binding order" generated a warning. 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 configurations to change the binding order."
i have two netwrok adapater . once is for public network and another one for privat (heartbeat ) and alos i have changed the network order in the network connection management public and privat.
How resolve this issue ?
Thnks in advance .

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply

sudhakara SSCrazy Eights Points: 9425 More actions · Answer 1

i have got solution for this issue ....

HKLM\System\CurrentControlSet\Services\TCPIP\Linkage

change your network adapter binding in above reigistry path and you can verify the network adapter order by ipconfig command....

Scott Ohar Hall of Fame Points: 3607 More actions · Answer 2

Windows Server 2008, just go into your network adapter > properties > you will get an Up / down arrow move them that way, alot easier then messing with registry values.

sudhakara SSCrazy Eights Points: 9425 More actions · Answer 3

you can change the network binding of the physical network adapter but you can not change binding order of the virtual network adapter order ...

Scott Ohar Hall of Fame Points: 3607 More actions · Answer 4

Hmm, thats odd. I've had no issues, just stating how to address that issue which a clustering engineer from microsoft recommened to do.

sudhakara SSCrazy Eights Points: 9425 More actions · Answer 5

MM.. this is the only way to change the network binding order of virtual work order ... 🙂 ...

Scott Ohar Hall of Fame Points: 3607 More actions · Answer 6

This is getting pointless. my last post for this thread.

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

http://blogs.technet.com/brad_rutkowski/archive/2007/01/31/how-to-change-the-network-binding-order-in-vista.aspx

Here is one with pictures.

http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/deploying-exchange-2007-sp1-ccr-cluster-windows-server-2008-failover-cluster-part1.html

NULLgarity SSCommitted Points: 1572 More actions · Answer 7

I've run into an issue with this warning. According to my detail.txt, none of my network interfaces are reporting back as bound to our domain. When I look at Network Connections, I see them in the correct order. Hoping it's just a case where things are correct, but the way that setup verifies it is not working so I cannot get around the warning. Don't know how to set the network interface to report as being bound to the domain.

2010-03-15 14:30:40 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet

2010-03-15 14:30:40 Slp: NetworkBindingFacet: Looking up network binding order.

2010-03-15 14:30:40 Slp: NetworkBindingFacet: Network: 'Local Area Connection' Device: '\Device\{64D56DB1-1661-40D6-A413-D45C88172F65}' Domain: '' Adapter Id: '{64D56DB1-1661-40D6-A413-D45C88172F65}'

2010-03-15 14:30:40 Slp: NetworkBindingFacet: Network: 'Local Area Connection 2' Device: '\Device\{24CC2631-3CED-43B5-9393-E60C2BC9EEF3}' Domain: '' Adapter Id: '{24CC2631-3CED-43B5-9393-E60C2BC9EEF3}'

2010-03-15 14:30:40 Slp: NetworkBindingFacet: Network: 'Local Area Connection* 9' Device: '\Device\{19280E30-8A2F-45BC-B358-3E9F063DE3D8}' Domain: '' Adapter Id: '{19280E30-8A2F-45BC-B358-3E9F063DE3D8}'

2010-03-15 14:30:40 Slp: IsDomainInCorrectBindOrder: The top network interface 'Local Area Connection' is bound to domain '' and the current domain is 'mydomainhere.COM'.

2010-03-15 14:30:40 Slp: Evaluating rule : IsDomainNetworkTopOfBindings

Twitter | LinkedIn

Corbett Enders Valued Member Points: 67 More actions · Answer 8

If you are still having trouble sorting this one out, and the official MS link doesn't mention hidden virtual adapters, then look for this tool:

NVSPBind (http://code.msdn.microsoft.com/nvspbind)

Using it, you can view your adapters

NVSPBIND.exe /o ms_tcpip

then the same tool to adjust their order

NVSPBIND.exe /++ "Local Area Connection" ms_tcpip

Enjoy.

Perry Whittle SSC Guru Points: 234013 More actions · Answer 9

Scott Ohar (8/11/2009)
Hmm, thats odd. I've had no issues, just stating how to address that issue which a clustering engineer from microsoft recommened to do.

I have only seen this when using more than 1 network adapter, the only way to correct the bindings is via the registry.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Kevin Callahan SSC Rookie Points: 45 More actions · Answer 10

Thanks Corbett! this solved the issue with my cluster.

asadeen SSC Rookie Points: 30 More actions · Answer 11

Changing the binding order in the adapter settings did not work Editing the registry worked for me.

asadeen SSC Rookie Points: 30 More actions · Answer 12

I would recommend compare registry HKLM\system\currentcontrolset\services\TCPIP\linkage\ -> bind value with the one listed indetail.txt. and then correct the registry as per the SQL server installation detail reports.

Thanks

Shaik Maricar

matthew.lass Grasshopper Points: 11 More actions · Answer 13

sudhakara (8/1/2009)
i have got solution for this issue ....
HKLM\System\CurrentControlSet\Services\TCPIP\Linkage
change your network adapter binding in above reigistry path and you can verify the network adapter order by ipconfig command....

This is what helped me. As stated, ipconfig /all will show binding order. The registry key mentioned can re-order the interface binding.

I tried just doing normal re-ordering, but the problem for me was that the MS failover cluster virual adapter was first, but does not show up in the network management control panel (ncpa.cpl)