Bug 10100 - SqueezePlay fails to connect to SqueezeCenter
: SqueezePlay fails to connect to SqueezeCenter
Status: CLOSED FIXED
Product: SB Desktop
Classification: Unclassified
Component: Settings
: unspecified
: PC All
: -- normal (vote)
: 7.4.0
Assigned To: Wadzinski Tom
http://forums.slimdevices.com/showpos...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-21 07:11 UTC by Mike Richichi
Modified: 2009-10-05 14:36 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Richichi 2008-11-21 07:11:16 UTC
Nightly builds of SqueezePlay after November 15th fail to connect to SqueezeCenter.  The connection continues to attempt to be established, but fails and keeps retrying.  Older builds of SqueezePlay work fine with later builds of SqueezeCenter so it doesn't seem to be a SqueezeCenter issue.

The above link has an excerpt from the error log showing the issue.  I can get a network trace if that would be beneficial.
Comment 1 Paul Molodowitch 2008-12-08 09:22:21 UTC
Just wanted to add that I'm experiencing the same problem, using 2008-12-08 nightly, SqueezeCenter 7.2.1, Windows XP x64.
Comment 2 James Richardson 2008-12-19 08:04:05 UTC
Changing target to next release
Comment 3 Wadzinski Tom 2009-06-09 13:36:23 UTC
This is a bit stale now and is likely fixed, since it is not being seen now.
Comment 4 James Richardson 2009-10-05 14:36:45 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.