Bugzilla – Bug 14995
Radio won't connect to Squeezebox Server
Last modified: 2010-02-08 09:57:00 UTC
My Radio, after working ok, suddenly decided it won't connect to my Squeezebox Server (diagnostics error message "Can't Ping"). This has happened twice. Nothing I can do brings it back, except booting from an old backup, which is highly inconvenient, but did once. My SB2 works fine. The Radio connects to mysqueezebox.com without trouble (occasionally it fails, but recovers later). Computer is wired in to the router, Radio I have tried both wired and wireless with the same issue, the Radio connects to the network ok but not to the SBS. After a long call to support, trying various things I had previously tried but with no success, the support person finally stated that the Radio was incompatible with my router, a Netgear DG834G. He promised to send me a link to a discussion of compatibility of routers, but has not done so. Is this true? If so, can I have the link (it might be good to have this publicly available) so I can consider whether to buy a new router? Is this something you expect to be able to deal with in the future by new firmware? (I think this sort of thing happened with the old Squeezeboxes)
This could be a duplicate of bug 14851, assigning to Tom for evaluation. Dan Evans: Please see the comments below regarding technical support Daniel Cohen: the link can be found here; http://wiki.slimdevices.com/index.php/RouterStatus
It *may* be an issue on my computer, but if so I have no idea what. I just tried reinstalling from a backup (which is, of course, a major hassle) and it is currently working ok. The question is whether it will continue working after several days switching it on and off. It seems the tech support guy overstated the case, in that he claimed that the router was not compatible, while the wiki page just indicates that it has not been tested. I can report, by the way, that it works fine with my SB2, and seems fine with the Radio when connected to mysqueezebox.com. It is only connection to the local server that has been a problem.
To be clear, concluding the cause was an "unsupported router" was far too big a leap. It's likely something more mundane than that. I'm curious: when this failure occurs, if you simply unplug the Radio and plug it back in, allow it to go through its startup routine and reconnect to your WiFi... what happens? * Does it connect to your WiFi? * Does it connect to SBS? * Can you play internet radio?
(In reply to comment #3) > To be clear, concluding the cause was an "unsupported router" was far too big a > leap. It's likely something more mundane than that. > > I'm curious: when this failure occurs, if you simply unplug the Radio and plug > it back in, allow it to go through its startup routine and reconnect to your > WiFi... what happens? > > * Does it connect to your WiFi? > * Does it connect to SBS? > * Can you play internet radio? I'm not sure if I tried that, though I tried most things (including turning the Radio fully off, without disconnecting from the power supply. It's working ok at present, and I hope I won't have the issue again. I'll try unplugging from power if it happens. This is what happened in the past. 1. Never any trouble connecting to wi-fi or to an ethernet connection. 2. Almost never any trouble connecting to mysqueezebox.com and playing internet radio. A couple of occasions when ping and TCP to mysqueezebox.com were fine but internet radio was not present. That cleared up in an hour or so, and I suspect was a server issue at mysqueezebox.com. 3. Connected to SBS fine for a couple of days, then failed and I could not get it back. As noted in my first post, I got the error message "Can't ping", and also no TCP connection. Again, as reported,reverting to a backup of a few days ago has cured the problem at present, which suggests some software oddity on my machine. Any suggestions as to what the cause could be?
If it was a PC I would guess a virus scanner issue. Puzzling on a mac.
> Again, as reported,reverting to a backup of a few days ago has cured the > problem at present, which suggests some software oddity on my machine. Any > suggestions as to what the cause could be? That is great news, even if we lack a full understanding of what caused or cured the issue. Historically, the kinds of things that can cause this sort of behavior are the various forms of security software available on the market. That you have a Mac though makes that list much, much shorter. My second guess would be some snafu with the Mac's internal firewall protection. My third guess would be some sort of file permissions issue. Notice though that these are truly guesses. If this issue reappears, please contact me offline or contact support and we'll try and work the problem again.
(In reply to comment #6) > > Again, as reported,reverting to a backup of a few days ago has cured the > > problem at present, which suggests some software oddity on my machine. Any > > suggestions as to what the cause could be? > > That is great news, even if we lack a full understanding of what caused or > cured the issue. Historically, the kinds of things that can cause this sort of > behavior are the various forms of security software available on the market. > That you have a Mac though makes that list much, much shorter. > > My second guess would be some snafu with the Mac's internal firewall > protection. My third guess would be some sort of file permissions issue. > Notice though that these are truly guesses. > > If this issue reappears, please contact me offline or contact support and we'll > try and work the problem again. I do have Little Snitch and Intego NetBarrier, as well as the internal firewall. But I checked them both, and confirmed that they were both set to allow all local connections. I wondered if an incompatible plugin could causthe problem? By the way, the Logitech FAQ on firewalls cover Tiger and Leopard, but not Snow Leopard which is slightly different again.
These are all bugs that have been marked 'fixed' or 'closed' but still have the bug_meeting keyword. They were not showing up in James's bug meeting search. Please let me know (chris_owens@logitech.com) if these need to be brought up at the next bug meeting. In the meantime I will fix the search.