Bugzilla – Bug 9176
Duet fails to connect to a Music Source
Last modified: 2009-09-08 09:28:56 UTC
See bug 8984, Right Now ticket 080812-000979. Dan Evans to provide networking specifics and more ticket numbers. Symptoms: Duet connects fine to 7.01, 7.1 or 7.2 Controller fails to connect to music source but does connect to wireless network.
Okay, here's what I've been able to gather from everyone in Support at this time... copied comment from bug 8984: 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. Breakdown: 3 x Failure #1 (ticket examples: none) 5 x Failure #2 (ticket examples: 080812-000979)
Support team, please include specific network details. Router including version number, firmware of router, as well as an additional network topological details that may help QA to reproduce.
Ross please continue to communicate with support on this bug, trying to get information and attempt to reproduce when new info comes in.
Dan, anything new?
Ross, Nothing. Querying customer today with some direct questions.
Ping Dan.
I just had another one of these customers. 080912-001745 SMC router. Model SMCWBR14-g firmware version v1.00.024 2004.1215 latest firmware customer could find on the website.
Customer above: Controller: 7.2 r2873 Customer was able to connect to SN perfectly fine. No matter what mode we tried to connect in....Bridged, hybrid, or wireless we could not connect to PC. Receiver would go white and Controller would get stuck on Connecting to Receiver.
Sorry...Left out a little more information. Customer uninstalled Zone Alarm firewall. Turned off Windows Firewall. Turned of SMC firewall in router. Customer is able to see his computer as a Music Source.
(In reply to comment #9) > Customer is able to see his computer as a Music Source. We discussed this briefly and I had a question for you. You mentioned that Receiver appears to connect (white) and Controller fails with try again/skip this step message, please check SqueezeCenter and confirm that Receiver is connected, and confirm the IP and firmware version please. Dan, any input from the original customer here?
Created attachment 4120 [details] SC setting screen Confirmed Receiver was connected. I was able to play song of my choice via SC. Screenshot attached with HW and FW info.
(In reply to comment #11) > Created an attachment (id=4120) [details] > SC setting screen > > Confirmed Receiver was connected. I was able to play song of my choice via SC. > Screenshot attached with HW and FW info. > Awesome! Thanks for getting involved, I really appreciate your input. I'm having a tough time reproducing this. I'm wondering if you could give me some insight about your PC or your network that might help me to reproduce this. Is there anything out of the ordinary that you think might cause the disconnect? I was under the impression this wasn't an issue with latest Controller firmware, which you have.
(In reply to comment #12) ..........I'm wondering if you could give me > some insight about your PC or your network that might help me to reproduce > this. Is there anything out of the ordinary that you think might cause the > disconnect? I was under the impression this wasn't an issue with latest > Controller firmware, which you have. > My ticket 080912-001745 has the 4 PC and 5 configurations I tried. Right now I'm using the Thinkpad X31 with Windows firewall with the UDP and TCP ports opened. Also, tried without any firewall on PC and router. I don't broadcast network SSID. SB and PC connected to router via ethernet. 802.11g router. WEP128bit encryption. MAC filters activated with access allowed for all HW MAC IDs in question. Nothing out of the ordinary with the network. The FW and SC versions are the only version I've used as I am a new Duet owner. On rare occasion where the PC is connected as music source, the connection seems to fail when my playlist grows. Song count is about 70 in the play list. If I play one song at a time, it seems to stay connected.
Thank you Stephen for the details. I'm curious if you've tried any networking diagnostics, specifically have you tried disabling encryption and MAC address filtering? In this case, does Duet connect properly? Also what about enabling SSID broadcast? Or perhaps WPA encryption? So you can reproduce this on 4 different PCs? All without firewalls?
Ross-- original customer has gone silent. I emailed him on 9/2 and 9/17. No response.
(In reply to comment #14) Tried w/o software firewall on the X31, Quadcore and PIII 700MHz running Windows. Don't know if I firewall was running when using Ubuntu. I tried broadcasting SSID. Tried disabling MAC filter. Did not tried w/o encryption. Hardware not capable of WPA. I have spent much time testing with the X31 and PIII 700MHz, not much with Ubuntu and Quadcore Vista. I will be sending the SB out on RMA within a day or two. If you have some test suggestions, I can run some tests with the XP31. But no time for other PCs for now. Will test w/o encryption this evening.
While it's possible this is a hardware specific issue, I'm doubtful. I believe this to be a software issue, possibly network but that's unlikely too. You're of course welcome to RMA if you'd like, Anoop will gladly help you get a replacement Controller. I'm only concerned the issue will be the same with a new Controller, and I would hate to have you wait just to be disappointed again. Did your testing show any success? I take it you've got an older adapter that doesn't support WPA, now I understand why you're using WEP. Please let us know how it goes with SSID broadcast enabled and mac address filtering disabled. Ubuntu does not have a firewall. Ubuntu would be a great test bed, are you certain SqueezeCenter is running on your Ubuntu machine? You can see the web interface etc?
(In reply to comment #17) Some of my old hardware on the network do not support WPA. So I have to let them access the network with WEP. Broadcasting SSID and disabling MAC address were previously tested and did not help. Just tested with wireless encryption disabled. Controller still cannot connect to receiver but SC was connected to receiver. Already tested with Ubuntu previously. Console said SC was starting. I gave it long time to start and then tried to confirm with the web interface and the browser always timed out after a long wait. No SC screen appeared. Anoop suggested RMA so he could have the hardware to diagnose. I can hold off on that. You can call me tomorrow to run some more tests and confirm various settings. I'm off tomorrow. Anoop has my number.
SC isn't running on your Ubuntu machine. That's is a separate issue, lets stay focused on your connection problem. Do you have any PCs that SC runs on and definitely do not have any firewall?
(In reply to comment #19) > SC isn't running on your Ubuntu machine. That's is a separate issue, lets stay > focused on your connection problem. I only mentioned how SC runs on Ubuntu because you asked. I only want SB to work on my XP PC for now. > > Do you have any PCs that SC runs on and definitely do not have any firewall? > NO. The XP PC has built-in firewall. It was tested with firewall disabled already (see earlier reply). I cannot remove XP's firewall if that's what you mean. All my other Windows PCs have OS firewall also.
(In reply to comment #20) > NO. The XP PC has built-in firewall. It was tested with firewall disabled > already (see earlier reply). I cannot remove XP's firewall if that's what you > mean. All my other Windows PCs have OS firewall also. One last test. Disable the XP firewall, double check that SqueezeCenter is running. SSID broadcast enabled, MAC address filtering disabled, encryption disabled. Factory reset both Controller and Receiver, and try to connect. If this fails, please follow through with the RMA and we will get you a replacement Controller quickly, and I'd like to see this Controller.
(In reply to comment #21) > One last test. Disable the XP firewall, double check that SqueezeCenter is > running. SSID broadcast enabled, MAC address filtering disabled, encryption > disabled. Factory reset both Controller and Receiver, and try to connect. If > this fails, please follow through with the RMA and we will get you a > replacement Controller quickly, and I'd like to see this Controller. > Disabled Windows firewall.Disabled wireless router's firewall. Broadcasted SSID. Disabled MAC address filter. Disabled wireless encryption. Then factory reset the controller and receiver. The controller was still unable to connect to SC. SC can connect to the receiver with or without all the setting changes. I was able to select music in SC to play with the receiver. Internet Radio is still working. Will RMA the Duet set as Anoop described.
Trying couple of things before ship out for RMA. 1. Tried two other routers with no encryption. Controller could connect only once in 30+ resets. 2. Move the music files from Buffalo LS Live 500GB (Linkstation Live, FW v.2.1) to PC where SC is running. Controller was able to connect quite consistently. I was also able to create lengthy playlists with controller that previously always caused controller to disconnect from SC. All network and PC settings are the same as when controller failed to connect (see previous postings for detail). Please advise.
(In reply to comment #23) > 2. Move the music files from Buffalo LS Live 500GB (Linkstation Live, FW v.2.1) > to PC where SC is running. Controller was able to connect quite consistently. I > was also able to create lengthy playlists with controller that previously > always caused controller to disconnect from SC. All network and PC settings are > the same as when controller failed to connect (see previous postings for > detail). Please advise. This sounds like bug 9004. I remember having strange issues with a LinkStation years ago, unrelated to SqueezeCenter. Have you had any other issues with the LinkStation? Is it v.2.1 the latest?
(In reply to comment #24) > This sounds like bug 9004. I remember having strange issues with a LinkStation > years ago, unrelated to SqueezeCenter. Have you had any other issues with the > LinkStation? Is it v.2.1 the latest? > The LS FW 2.1 is the latest. LS has been able to serve all my songs to multiple computers and players on my network without issues. It can also server 1080i videos with multi-channels sound with little problem. The LS has a gigabit port. The router has a 100mb port. Tested the same with music on any USB external HD and SB works fine. Stress tested the said setup by adding many artists to the playlist successively without pause. The controller connection was lost at one point with a red antenna icon on the controlerl (white on receiver) but got reconnected after < 10 seconds. Do you still want to my SB via RMA?
*** Bug 8415 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 9004 ***
Update SC to 2.7.1. No help. Updated controller FW to 7.2 r3191. build #111. So far, it has been 4 days and I am still connected even with music files on NAS.
(In reply to comment #28) > Update SC to 2.7.1. No help. Updated controller FW to 7.2 r3191. build #111. So > far, it has been 4 days and I am still connected even with music files on NAS. > I find this confusing, could you please clarify? 4 days it's been working, but that is no help?
(In reply to comment #29) > (In reply to comment #28) > > Update SC to 2.7.1. No help. Updated controller FW to 7.2 r3191. build #111. So > > far, it has been 4 days and I am still connected even with music files on NAS. > > > > I find this confusing, could you please clarify? 4 days it's been working, but > that is no help? > I downloaded and installed SC 2.7.1 on PC. Did not run SW update on the controller. No improvement. Then I ran SW update on the controller. Then Duet works like a charm. All settings on PC and network are the same as when I had the connection problem. Only changes are SC 2.7.1 and subsequent SW update on the controller.
This is not correlated with slow servers. Support states this is their #1 issue. Do not resolve this bug as a duplicate or close it due to difficulty reproducing.
Ross, please work with Dan to gather information about these cases including OS, server speed, and network/router info.
If this is the #1 support issue, it sure isn't reflected in the A8 google document. Can we get some more data points please?
We may have our wires crossed. A8 was identified as #1 top issue. On the other hand, in Comment #1 there are multiple failures described. Failure #1 as described in Comment #1 correlates to A13. Failure #2 correlates to A8. We should split this bug in two, yes? Or start over with two new bugs?
Split it. It's easy with the 'clone bug' feature (although by default it marks one bug as depending on the other, which is not always true.
Split to two new bugs, see bug 11183 and bug 11184. This bug (9176) is too general and starting to get confusing. *** This bug has been marked as a duplicate of bug 11184 ***