Hi,
I'm preparing to install SQL 2008 to a 2008 cluster and have a few questions. Any help is appreciated.
The Setup Support Rules check fails on the binding rule where the top network interface 'Public' is bound to domain '' and the current domain is 'ourdomainname'. When I look in Network and Sharing Center, the NIC appears with the ourdomainname (Domain Network). I looked at customize, I don't seem to have another option. How do I resolve this?
For the private network, the customize options are "private" network and "public" network. It is now set as public. Should it be private?
What about network discovery? Is off okay?
I also noticed that the two nodes are set to get the IP and DNS address automatically. Is this an issue?
Here is the detail for the binding issue.
2009-11-09 17:47:54 Slp: Initializing rule : Network binding order
2009-11-09 17:47:54 Slp: Rule applied features : ALL
2009-11-09 17:47:54 Slp: Rule is will be executed : True
2009-11-09 17:47:54 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Looking up network binding order.
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Public' Device: '\Device\{43DA14CC-DD68-4932-A312-6F175D1BABCB}' Domain: '' Adapter Id: '{43DA14CC-DD68-4932-A312-6F175D1BABCB}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Local Area Connection* 8' Device: '\Device\{649DB2BE-9AC3-4FF9-9062-24B97B01FC2C}' Domain: '' Adapter Id: '{649DB2BE-9AC3-4FF9-9062-24B97B01FC2C}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Private' Device: '\Device\{EDD1C661-763A-4D43-9A52-90D809211CF6}' Domain: '' Adapter Id: '{EDD1C661-763A-4D43-9A52-90D809211CF6}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Local Area Connection 3' Device: '\Device\{7020CF2E-1FE4-4E86-B5D5-1D35CCF98A62}' Domain: '' Adapter Id: '{7020CF2E-1FE4-4E86-B5D5-1D35CCF98A62}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Local Area Connection 4' Device: '\Device\{88DA3161-160A-46E4-AAB3-0F2BD97D02B8}' Domain: '' Adapter Id: '{88DA3161-160A-46E4-AAB3-0F2BD97D02B8}'
2009-11-09 17:47:54 Slp: IsDomainInCorrectBindOrder: The top network interface 'Public' is bound to domain '' and the current domain is 'ourdomainname'.
2009-11-09 17:47:54 Slp: Evaluating rule : IsDomainNetworkTopOfBindings
2009-11-09 17:47:54 Slp: Rule running on machine: OURNODEA
2009-11-09 17:47:54 Slp: Rule evaluation done : Warning
2009-11-09 17:47:54 Slp: 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.
2009-11-09 17:47:54 Slp: Send result to channel : RulesEngineNotificationChannel
Thanks,
Randy
I'm preparing to install SQL 2008 to a 2008 cluster and have a few questions. Any help is appreciated.
The Setup Support Rules check fails on the binding rule where the top network interface 'Public' is bound to domain '' and the current domain is 'ourdomainname'. When I look in Network and Sharing Center, the NIC appears with the ourdomainname (Domain Network). I looked at customize, I don't seem to have another option. How do I resolve this?
For the private network, the customize options are "private" network and "public" network. It is now set as public. Should it be private?
What about network discovery? Is off okay?
I also noticed that the two nodes are set to get the IP and DNS address automatically. Is this an issue?
Here is the detail for the binding issue.
2009-11-09 17:47:54 Slp: Initializing rule : Network binding order
2009-11-09 17:47:54 Slp: Rule applied features : ALL
2009-11-09 17:47:54 Slp: Rule is will be executed : True
2009-11-09 17:47:54 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Looking up network binding order.
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Public' Device: '\Device\{43DA14CC-DD68-4932-A312-6F175D1BABCB}' Domain: '' Adapter Id: '{43DA14CC-DD68-4932-A312-6F175D1BABCB}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Local Area Connection* 8' Device: '\Device\{649DB2BE-9AC3-4FF9-9062-24B97B01FC2C}' Domain: '' Adapter Id: '{649DB2BE-9AC3-4FF9-9062-24B97B01FC2C}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Private' Device: '\Device\{EDD1C661-763A-4D43-9A52-90D809211CF6}' Domain: '' Adapter Id: '{EDD1C661-763A-4D43-9A52-90D809211CF6}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Local Area Connection 3' Device: '\Device\{7020CF2E-1FE4-4E86-B5D5-1D35CCF98A62}' Domain: '' Adapter Id: '{7020CF2E-1FE4-4E86-B5D5-1D35CCF98A62}'
2009-11-09 17:47:54 Slp: NetworkBindingFacet: Network: 'Local Area Connection 4' Device: '\Device\{88DA3161-160A-46E4-AAB3-0F2BD97D02B8}' Domain: '' Adapter Id: '{88DA3161-160A-46E4-AAB3-0F2BD97D02B8}'
2009-11-09 17:47:54 Slp: IsDomainInCorrectBindOrder: The top network interface 'Public' is bound to domain '' and the current domain is 'ourdomainname'.
2009-11-09 17:47:54 Slp: Evaluating rule : IsDomainNetworkTopOfBindings
2009-11-09 17:47:54 Slp: Rule running on machine: OURNODEA
2009-11-09 17:47:54 Slp: Rule evaluation done : Warning
2009-11-09 17:47:54 Slp: 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.
2009-11-09 17:47:54 Slp: Send result to channel : RulesEngineNotificationChannel
Thanks,
Randy