I got a network binding order warning when I try to install sql 2008 cluster.
I have change the binding order through the network connection, advanced
settings. But that did not work. Any ideas what is going on?
Thanks in advance for your help!
--
Yuhong

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote

http://msdn.microsoft.com/en-us/library/ms189910.aspx

Here is the relevant section of the page:

• Failover cluster Setup operations include a rule that checks network
binding order. Although binding orders might seem correct, you might have
disabled or "ghosted" NIC configurations on the system. "Ghosted" NIC
configurations can affect the binding order and cause the binding order rule
to issue a warning. To avoid this situation, use the following steps to
identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be
in the list. If you have a disabled network adapter, Setup will report a
failure for the network binding order rule. Control Panel/Network
Connections will also show that adapter was disabled. Confirm that Network
Settings in Control Panel shows the same list of enabled physical adaptors
that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and
disable any network adapters that are not currently in use.



--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Yuhong" <Yuhong (AT) discussions (DOT) microsoft.com> wrote