Bug 5079 - Rhapsody "Connection Timed Out" errors
: Rhapsody "Connection Timed Out" errors
Status: RESOLVED WONTFIX
Product: Logitech Media Server
Classification: Unclassified
Component: Rhapsody UPnP
: 6.5.2
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-22 08:12 UTC by Matt Richards
Modified: 2007-12-10 09:37 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Richards 2007-05-22 08:12:03 UTC
I have a lot of clunkiness with Rhapsody in 6.5.2 - 12069.  I have only just come back to 6.5 today.  The clunkiness is similar to what I have seen in the past.  Putting on the new SlimServer seems to require a reboot to get SlimServer to "see" Rhapsody.  (I note a bug that says you should just wait a while to see if Rhapsody comes up, so perhaps I will start doing that.)  After doing that, frequently when I try to play music, it will not play.  I get "Connection Timed Out" errors.  The fix for this seems to be to play a non-Rhapsody track, then go back to Rhapsody.

It's very hard to report these bugs because there is just a generalized failure of SlimServer, Rhapsody, and the Squeezebox to link up and do what they are supposed to do.  Weird problems, like "Connection Timed Out" happen, and it is not always clear what fixes them.  But the linkage is pretty weak.  6.3 did not seem to have nearly the amount of difficulty with Rhapsody that 6.5.2 has.  I can only assume that you guys are not seeing these bugs because they would be as blatantly obvious and annoying to you as they are to me.

There isn't anything unusual about my system.  The SlimServer system is Windows XP SP2 and is pretty much dedicated to SlimServer and Rhapsody.  I get on it using VNC from my other computer.

So . . . call this whining, but it is really very frustrating when the software does not simply link up and work properly, and there is no clear path to either describing or fixing the problems.
Comment 1 Ross Levine 2007-05-22 11:36:38 UTC
Could this be a duplicate of bug 4836
Comment 2 Matt Richards 2007-05-22 12:16:30 UTC
I don't think it's the same thing, but the next time I have the problem I will see if I am seeing "Server Status: Stopped".  Right now it says it's running.  I am running Rhapsody 4.0, like the person in the other bug, so that is one similarity.
Comment 3 Blackketter Dean 2007-10-26 12:14:09 UTC
Matt: Can you upgrade to 7.0 and use the new Rhapsody direct service?  It's much more reliable.
Comment 4 Matt Richards 2007-10-26 13:05:48 UTC
Funny you would ask.  I was considering doing that, but I found that dealing with the previous pre-release version of SlimServer was unpleasant, and didn't want to put myself through that again.  But I suppose I could . . . <sigh>, especially since you've asked so nicely.  I also couldn't find anything on the forums etc. that told me whether Rhapsody Direct required setup, and if so how to do it, or if it would "just work".

I'll try . . .
Comment 5 Chris Owens 2007-11-01 10:10:29 UTC
Dean directs that we turn off support for rhapsody UPNP.  The workaround is to use Rhapsody Direct.