home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
[Updated 14 Jul!] MPExtended WebMediaPortal 0.5.4
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="tomfrogger" data-source="post: 1030772" data-attributes="member: 20976"><p>This was the issue. I was seeing the problem while also being connected to my vpn on the server. I changed the bind order to ensure the local adapter was 1st in the list within windows itself and now I no longer have a problem. I followed this guide from a msdn blog (It was for a similar issue with sql server..):</p><p></p><p><em>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.</em></p><p><em></em></p><p><em>To find out to which network adapter Local Area Connection *8 correspond to run the following command to list the NIC configuration:</em></p><p><em></em></p><p><em>"<strong>wmic nicconfig get description, SettingID > C:\nicconfig.txt</strong>"</em></p><p><em></em></p><p><em>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</em></p><p><em></em></p><p><em><Nicconfig.txt></em></p><p><em>HP NC380T PCIe DP Multifunc Gig Server Adapter {52AEDCB0-9E8E-4243-9D5D-ED86E602DF23} </em></p><p><em>HP NC380T PCIe DP Multifunc Gig Server Adapter #2 {5AC63784-8088-40F7-93C8-37F9CD03D445} </em></p><p><em>WAN Miniport (IP) {7F583D1B-4203-4AD0-A6A0-4BD007D21735} </em></p><p><em>HP Network Team #1 {0BF4D354-E6E9-480C-91CF-DC598282C4C1} </em></p><p><em>Microsoft Failover Cluster Virtual Adapter {4DB91193-72F1-4713-A938-EB73F27CFEC8} </em></p><p><em>RAS Async Adapter {7C264673-3322-4312-AE60-D09B4E71E368} </em></p><p><em>HP NC373i Multifunction Gigabit Server Adapter {C6CEC36A-3D03-4C32-ACD0-2DB2851A841D} </em></p><p><em>HP NC373i Multifunction Gigabit Server Adapter {5C3D2BA3-B15C-4FBB-A093-B42C80C39B81} </em></p><p><em></Nicconfig.txt></em></p><p><em></em></p><p><em>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 :</em></p><p><em></em></p><p><em>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Linkage\<Bind></em></p><p><em></em></p><p><em>So we can check the Bind order in registry as shown</em></p><p><em></em></p><p><em><Bind></em></p><p><em>\Device\{4DB91193-72F1-4713-A938-EB73F27CFEC8} : Microsoft Failover Cluster Virtual Adapter </em></p><p><em>\Device\{0BF4D354-E6E9-480C-91CF-DC598282C4C1} : HP Network Team #1 </em></p><p><em>\Device\{5AC63784-8088-40F7-93C8-37F9CD03D445} : HP NC380T PCIe DP Multifunc Gig Server Adapter #2 </em></p><p><em>\Device\{52AEDCB0-9E8E-4243-9D5D-ED86E602DF23} : HP NC380T PCIe DP Multifunc Gig Server Adapter #2 </em></p><p><em></Bind></em></p><p><em></em></p><p><em>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 </em></p><p><em>NetworkBindingFacet: Network: 'Production Team' Device: '\Device\{0BF4D354-E6E9-480C-91CF-DC598282C4C1}' Domain: 'contoso.com' Adapter Id: '{0BF4D354-E6E9-480C-91CF-DC598282C4C1}'</em></p><p><em></em></p><p><em>Once the binding order is changed we need to run the installation and the warning will not be reported.</em></p></blockquote><p></p>
[QUOTE="tomfrogger, post: 1030772, member: 20976"] This was the issue. I was seeing the problem while also being connected to my vpn on the server. I changed the bind order to ensure the local adapter was 1st in the list within windows itself and now I no longer have a problem. I followed this guide from a msdn blog (It was for a similar issue with sql server..): [I]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: "[B]wmic nicconfig get description, SettingID > C:\nicconfig.txt[/B]" 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.[/I] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
[Updated 14 Jul!] MPExtended WebMediaPortal 0.5.4
Contact us
RSS
Top
Bottom