PDA

View Full Version : Squeezebox and Slimserver can't find each other.



wcattey
2007-03-24, 10:42
Lately my Squeezebox and Slimserver have had trouble making contact.

I hit the power button on the remote and see the mesage:

waking up slimserver...

and then the screen goes blank.

I start the web interface into Slimserver, and it says that my device is not found.

I stopped and re-started Slimserver. No change.
I power cycled the Squeezebox. No change.

The first time I tried to debug this, I started Softsqueeze 3.3, on the same host as my server, and it COULD reach the server, but no sound came out when I told it to continue the internet radio stream that it said was what I'd left off "now playing".

I quit Softsqueeze 3.3, and started Softsqueeze 2.8. That one made contact, but had trouble doing anythng. Finally from the web interface, I told it to play "random mix" onto my Softsqueeze.

A little while after that I was able to make contact from the Squeezebox to the server, and play music.

A couple days go by, and all seems well.

But today, again Squeezebox and the Slim Server can't find each other.

This time Softsqueeze 3.3 works fine, but no difference with Squeezebox.

Seeing in other threads, that sometimes there's a wi-fi issue, I've plugged my Squeezebox into one of the hard wired ports of my Wi-Fi router and power cycled the Squeezebox.

Now the Squeezebox seems to be able to reach the server.

But I don't know if that's because I've gone hard-wired, or if I managed to do the same shaking loose of the problem that I did last time.

Additional information:

My players are generally configured to be synchronized, and I wonder if this is creating additional complexity, even though the Softsqueeze is generally not running.

I listen to internet radio via Radio paradise, which sometimes has problems with streams hanging up.

My Squeezebox is literally five feet away from my wireless router, whereas my server is in the next room.

I expect nobody is going to be able to help on this one. I'll run for a while hard wired to the Squeezebox and reply to the thread if the hardwared connection manifests the problem same as the wi-fi.

bpa
2007-03-24, 13:34
If there is doubt about whether the packets from the Squeezebox reach and are processed by Slimserver - then you can do

1. run Ethereal all the time logging to a ring of files so that you will always have a log of what's has been happening on the network on the previous hours. When the problem shows - stop ethereal and see if Squeezebox packets are being logged and received by server.

2. Enable d_proto on slimserver - this will indicate if packets (including the very first discovery packets) are being received and processed by Slimserver.

If packets are not being logged by Ethereal - check wifi and network hardware (NICs, Routers and cables).

If packets are logged by Ethereal and not being processed by Slimserver then I'd investigate "security" s/w - firewall, anti spyware, IM protection etc.

If Packets are being processed by Slimservers but replies not seen by Squeezebox - check security s/w.

wcattey
2007-04-23, 08:06
I switched my Squeezebox from wireless to wired operation, because I read in other threads, that many people had worked around flakiness with Squeezebox finding Slim Server by doing that.

Alas, today, the first time I tried to use m Squeezebox after taking the latest Apple Security update, the Slim Server and the Squeezebox had trouble finding each other.

This time around, I did NOT restart Slim Server.
I DID get repeated, "Waking up Slim Server; Contacting Slim Server; <blank screen>
I DID run Softsqueeze 3.3, and have no trouble at all connecting to the server.
I DID power cycle the Squeezebox.

None of those activities seemed to affect whether I could make contact between the Squeezebox and the Slim Server.

What worked this time? While it said, "Waking up Slim Server" I hit the left arrow key, and saw the message, that it was trying to connect to my server. (I confirmed that the IP address was right.)

I hit the left and right arrows a few times.

Suddenely the dim clock face indicative of Slim Server and Squeeze box finally finding each other manifested.

Why didn't it remember that I'd ALREADY hit the On switch, and that the Squeezebox should NOT be in standby?

At that point I hit the On switch, and all behaved as if all was well.

I guess I'll have to enable debugging and fetch, install and run ethereal to try and watch what's happening.

I have a reasonably simple network here, and my Replay TV and my desktop have no problem finding each other and transferring gigabyte-sized TV programs. I think somehow, when the Apple server reboots when Squeezebox is not expecting it, a problem ensues that the initial Aloha does not seem to reconcile, and which power cycling the Squeezebox also does not rememdy.

I will continue to watch.
Any further suggestions how to watch are most welcome.

danco
2007-04-23, 08:19
Interesting, that you have the problem with a wired connection. I had always assumed it was a wireless issue.

I get the issue at times when my computer wakes from sleep, so it isn't actually a matter of rebooting.

I solve the problem by pressing and holding the power button. This does one of two things (I'm not sure why it doesn't consistently just do one thing).

It either

immediately gives the message connecting to network and after a while provides the clock face that shows it connects or

gives the Welcome to Squeezebox message followed by the "to begin setup press Right" message. At that point I press Up and then Right and it goes through the connection process ending with the clock.

If you can work out exactly what is happening it would be a great service. It's only a small bug (since there is the easy work-around), but it is still annoying and it would be good to have it eliminated.

wcattey
2007-04-23, 08:42
I'll definitely continue monitoring the situation.
Maybe if I get time, I'll beat on it -- sleeping and waking the computer a bunch
to see if I can identify the specific fault.

Next time it happens, I'll try your "hold down the power button" work-around.

Thanks!

agentsmith
2007-04-23, 23:16
I have been having the exact same problem with SB3.

Happened to both the SB3 and the SlimServer connected either wired or wireless.

Slimserver version 6.51 on Windows XP

It started happening about 3 weeks ago. Not much has been changed then. Before the problem, the clock on SB3 would show after slimserver is started. Nowadays, I have to trick the Sb3 into turning on by:

1. Pressing the on button a few times until it shows connecting to server....

2. Press left arrow and select sevrer to connect

3. Press right arrow to connect

4. repeat 2 and 3 until it connects

5. Once connected, it defaults back to the clock. I have to then press the powe button again to turn iton

By the way, Slim server shows "Your Player is not found" before SB3 is connected.

Also, when I connect to the server web page from another machine using http://servername:9000, the web page shows "player not found" even though the player is connected to the server happily player a song.



I switched my Squeezebox from wireless to wired operation, because I read in other threads, that many people had worked around flakiness with Squeezebox finding Slim Server by doing that.

Alas, today, the first time I tried to use m Squeezebox after taking the latest Apple Security update, the Slim Server and the Squeezebox had trouble finding each other.

This time around, I did NOT restart Slim Server.
I DID get repeated, "Waking up Slim Server; Contacting Slim Server; <blank screen>
I DID run Softsqueeze 3.3, and have no trouble at all connecting to the server.
I DID power cycle the Squeezebox.

None of those activities seemed to affect whether I could make contact between the Squeezebox and the Slim Server.

What worked this time? While it said, "Waking up Slim Server" I hit the left arrow key, and saw the message, that it was trying to connect to my server. (I confirmed that the IP address was right.)

I hit the left and right arrows a few times.

Suddenely the dim clock face indicative of Slim Server and Squeeze box finally finding each other manifested.

Why didn't it remember that I'd ALREADY hit the On switch, and that the Squeezebox should NOT be in standby?

At that point I hit the On switch, and all behaved as if all was well.

I guess I'll have to enable debugging and fetch, install and run ethereal to try and watch what's happening.

I have a reasonably simple network here, and my Replay TV and my desktop have no problem finding each other and transferring gigabyte-sized TV programs. I think somehow, when the Apple server reboots when Squeezebox is not expecting it, a problem ensues that the initial Aloha does not seem to reconcile, and which power cycling the Squeezebox also does not rememdy.

I will continue to watch.
Any further suggestions how to watch are most welcome.

wcattey
2007-04-24, 06:40
The additional symptoms you mention are also present with my system.