Bug 16539 - Erroneous error message "Cannot communicate with Server"
: Erroneous error message "Cannot communicate with Server"
Status: UNCONFIRMED
Product: SB Controller
Classification: Unclassified
Component: SB Server
: unspecified
: All Windows Vista
: -- normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-09-13 15:27 UTC by Darren
Modified: 2011-02-22 01:30 UTC (History)
4 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darren 2010-09-13 15:27:11 UTC
I have SB Radio, SB Boom and a number of receivers all connected and usually work fine.

I discovered that if i am using my SB Controller to control the SB Radio and then turn the SB Radio off, the SB Controller is still thinks its controlling the SB Radio and says cannot connect to server when you browse for music.

Of course I have found that the solution is to keep clicking back and out of controlling the SB radio and then select a (current) powered on device to browse music.

Summary - the error "Cant connect to server" is incorrect - it should recognise that the SB Radio has been powered off and say "The device you are controling is powered off please select a different device and then browse your music".

This took me ages to realise - and anyway the SB Radio still exists in the list of selectable deviced EVEN when its powered off.  All powered off devices should not be listed...
Comment 1 Martin 2011-02-22 01:30:35 UTC
I have the same problem running sbs 7.5.4 on ubuntu 10.10 and sb classic on 132 over a wireless network. Also I am using the Richard Harris server power control plugin. Since the last firmware update (132)the sb keeps producing connect messages in power off mode while the server is sleeping (can't connect to server). 

This gets worse when I switch off the wireless network at night. sb gets stuck in reconnect mode even though it's supposed to be 'off'. Remote commands don't respond at all and the display keeps displaying reconnect error messages. 

I guess there should be a timeout during network setup to stop retries and switch to 'off' mode completely.