Bugzilla – Bug 8984
Controller fails to connect to Microsoft router
Last modified: 2009-09-08 09:16:06 UTC
Support has a report of trouble with a SB Controller (Duet) connecting to a Microsoft MN-700 after upgrading the firmware. (ticket 080801-001079) Note: even Bridged mode failed with r2722. He upgrade to 7.1 and his Controller upgrade to firmware r2722. After that he could no longer connect to his wireless network. I had him downgrade to 7.0.1 and copy r2448 to an SD card to downgrade his Controller. After that, everything is working again.
Dan was going to see if we could get this unit back from the customer since this is the only person reporting so far.
Bumping to 7.3
Dan notes support now has many reports of this. Ross, please have a look at this ASAP. We did at one time have an MS router. If it's not around, send email to everyone@slimdevices.com asking about it and try and find one to buy.
Okay, here's what I've been able to gather from everyone in Support at this time... We have 9 specific cases (including the one above) where upgrading to 7.1 caused a SB Duet to stop functioning correctly. Failure #1: Duet is successfully talking to SC 7.0.1 and customer upgrades to 7.1. We've confirmed the Jive firmware is up to r2722. Post-upgrade Jive will no longer connect to the server. It succeeds in connecting to the WiFi, it succeeds in "seeing" Music Sources, but when selecting a Music Source it fails with an error along the lines of "Problem Connecting". In this case, Ray's LED went WHITE. Failure #2: Duet is successfully talking to SC 7.0.1 and customer upgrades to 7.1. We've confirmed the Jive firmware is up to r2722. Post-upgrade Jive will no longer even offer to connect to a Music Source. (Jive connects to WiFi, Select Ray for setup, Ray connects to WiFi, then "Problem Connecting".) Ray's LED gets stuck on BLUE. Failure #3: Post-upgrade Jive will not even connect to WiFi. This is detailed in Comment #0 above. Breakdown: 3 x Failure #1 (ticket examples: none) 5 x Failure #2 (ticket examples: 080812-000979) 1 x Failure #3 (ticket examples: 080801-001079)
With 2448 Duet connects and works fine, it upgrades to latest firmware and connects just fine. However with later firmware 2826 or 2722, Duet fails to connect on first attempt. Controller shows Address Problem, try again, self assign, or use static. Self assign works for me, try again fails every time. Holding left arrow and then selecting choose player, I'm able to select a player (SB3) already connected to SC7.2 and it works fine, however I don't see Receiver from this menu.
Richard: Any idea what's going on here?
Factory reset, hold left to exit setup, disable power management and select wireless network, this setup also fails in the exact same manor. Self-assign still works. Dan, are your technicians suggesting to self-assign? The workaround seems to work well for me.
Changing this to a Microsoft router specific bug. The work around for now is solid, self-assigned IP (after DHCP failure) works for me 100%. I've tried no encryption, WEP64 and WPA, they all work. This will not work for choosing SqueezeNetwork as a source, so the customer will need to install SqueezeCenter, and music services will work. See bug 9176.
Disabled sending Controller hostname to dhcp server in 7.2 r2859. As far as I can tell this is the only dhcp related change in the 7.1 release, so this is likely to be causing the problem. Ross could you please if this fixes the problem. If so then this will need more investigation at a later time.
If this works, go ahead and mark it closed, Ross?
We actually need the bug open if the latest build works. I had to regress a (not important) feature, and this will need more investigation. Please retarget to 7.3 if it works.
Works with 7.2 r2859.
(In reply to comment #12) > Works with 7.2 r2859. > Support folks, this is working. Please let your customer(s) know that if they can update to 7.2 with bridged mode or another access point, this will work. Richard to improve this fix for 7.3.
Moving to 7.3.1
Changing target to next release
*** Bug 10445 has been marked as a duplicate of this bug. ***
We are now planning to make a 7.3.3 release. Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future. Thanks!
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out. If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it. Thanks.
Still reproducible with MN-700, thanks James for finding this router for me! Richard and I to investigate further.
Waiting on fix back port from Richard.
Fixed in 7.3 r5376.
(In reply to comment #21) > Fixed in 7.3 r5376. Indeed this is fixed, works great! r5398. Thank you Richard!
This bug has been fixed in the 7.3.3 release version of SqueezeCenter! If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.