Looking for Players ... forever
Beantwortet
I was having zero issues on the previous version of BlueOS Controller on my Windows 10 laptop... then I got a brilliant idea and upgraded to the latest controller... now when I open the controller, it just spins and spins forever trying to find my NAD M17 player. How beautiful. Previous version worked... new version does not.
How can I fix this... or at least go back to a working version?
Ruined my plans for listening to MQA's tonight.
-
Offizieller Kommentar
Hi Sonnie
As with all network troubleshooting issues, close the BluOS App. Please restart your router. Wait 5 minutes then power off your NAD M17 using the back panel switch. Wait 30 seconds and then power up the M17. Wait 30 seconds then launch the App.
If the problem persists after that, please e-mail the BluOS Support Crew at support@bluos.net and they will be in touch.
-
Hi Sonnie
I know this is a very old question, but I had the same issue, with the BluOS Controller looking for players infinitely.
As my MacBook and my Android device could see my players instantly, I knew it must be a problem with my Wintendo.
From my many years being an infrastructure specialist, I recalled something called nic-enumeration (the order of which network interface cards are seen in the OS). So first, I tried to disable unnecessary nics in Windows (being WSL and VMware nics). And then, my BluOS players showed up instantly.
The permant solution to this (for me), was to launch PowerShell and run the cmdlet "Get-NetIPInterface". Find my WiFi nic and ensure this nic has a metric, that is lower than all the other nics on my system. My WiFi nic has index 17 and the lowest metric was 15 (for my WSL nic), so i ran "Set-NetIPInterface -InterfaceIndex 17 -InterfaceMetric 10" and everything worked as a charm - instantly.
Hope this can help others, with the same issue.
2 -
I'm glad you were able to sort this issue out but I like many others I'm sure have absolutely no idea how to apply your solution for ourselves. Might as well be in Greek. Is there a simpler elucidation?
0 -
Hello Brian
I know my description might have been a bit "techy". So I'll try to do a step-by-step guide:
1. Start a command prompt (cmd), and locate the name of your network adapter in use, using the ipconfig command. The adapter we need to locate, is the one with an IP address you recognize.
2. Start an elevated PowerShell prompt (Run as Administrator). Run the command
Get-NetIPInterface -AddressFamily IPv4 and note the ifIndex number of the adapter with the name located in step 1.
3. If InterfaceMetric for your adapter does not have a value lower than all other adapters, run the command
Set-NetIPInterface -InterfaceIndex 9 -InterfaceMetric 20
Important: Be sure to replace the InterfaceIndex number with the number you noted in step 2.4. Repeat the Get-NetIPInterface command from step 2 and verify the result.
Hope this will do some magic, and help your BluOS Controller to find your players.
P.S. I don't recall, if this change requires a reboot to be activated. So please reboot to be sure. ;)
2 -
Unplug the player for a few minutes, plug it back, give it a minute to restart and reconnect.
This just worked for me.
-1 -
I had the same stubborn problem on a new Windows laptop. Changing NIC precedence helped! Thanks a lot erpomik!
0 -
This is happening in my setup, twice in the last few days. I have a node 2i and a b100s.
Unplugging the players is not a solution.
@erpomic solution from 2 years ago is also not a solution but it is a workaround. WSL has a lower index by default and I guess this is not uncommon. The app needs to be changed to work, without having us play home sysadmin.
0 -
Please see my original official comment - This does work.
-1 -
It works, it is not a solution.
The solution is to fix the code.
1 -
Hi Tony W.
I'm not saying, that cheap routers might eventually stop forwarding mDNS packets between VLANs and that restarting the router might help for some people.
But you cannot ignore the fact, that on systems with multiple NICs, the BluOS Controller only listens for mDNS packets on the NIC with the highest priority (lowest interface metric) and that this ought to be fixed in the software.
This is the exact same problem we were fighting 30 years ago, when we had to change LANA number on the NIC drivers, to get NetBIOS working.
2 -
FYI: A follow-up support ticket 293018 for my original ticket 196580 has just been filed.
1 -
Regrettably, erpomik's solution of changing the InterfaceMetric somehow only provided a temporary solution. The InterfaceMetric of the network interface that I use still is the lowest, but the BluOS controller is back to looking for players forever. By the way, this only happens on one of my computers.
0 -
Hi Frans
Akkam's Razor suggests there is something blocking traffic on your one PC that is being affected. If you cannot locate it or are unsure what might be blocking it, our Support Crew will be happy to assist you by e-mailing them at support@bluesound.com as per my official answer.
0 -
I have just found out that the connection problem was resolved by following the advice of Emanuel B in this thread: https://support1.bluesound.com/hc/en-us/community/posts/9447722845719-BluOS-controller-stuck-in-looking-for-players-after-update-on-Windows-10-
I changed the Windows Defender firewall rules for both instances of the BluOS Controller I encountered (it should probably be only one). One was allowed on private networks, the other only on public networks. They are now both allowed only on private network, and the controller works well now.
1
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
14 Kommentare