Bugzilla – Bug 4385
Radio streaming not working
Last modified: 2008-12-15 13:07:42 UTC
Environment: Windows 2000 Gateway PC - DSL connection and Internet Connection Sharing activated, running SlimServer Versions affected: from SlimServer 6.5 to all subsequent releases till last 7.0 beta Premise: After reading some bug posts, I understood that from release 6.5, the connection to a streaming radio is handled directly from the Squeezebox while before it was handled from SlimServer software. My Squeezebox is perfectly configured with a static IP address, DNS, Gateway and SlimServer (all pointing to the same IP, see Environment) and is regularly connected to SlimServer through wireless lan. Problem: Apparently all the functions that require the SqueezeBox to connect to an Internet source (radio streming, or simply browsing SlimDevices Picks) don't work anymore (all was ok with release 6.3.1). The problem shows up only when the SqueezeBox is connected to SlimServer. If the SqueezeBox is connected to SqueezeNetwork, all works well. Workaround: I installed an HTTP proxy on my W2K Gateway and I configured SlimServer to use it. Now all is working again. Idea: I suspect that the new connection method implemented from release 6.5 has some problem in my environment, perhaps the problem is general to Microsoft Internet Connection Sharing feature? Or it can be related to the fact that in my setup DNS, GW and SlimServer are all one the same machine?? Le me know how can I debug better. Luca
Luca, are you still seeing this in the most recent 6.5.1 build? I can't reproduce your symptoms. If you are still seeing this problem, please let me know an example radio station that displays the problem. (I know you said all, but just give me one). Thanks for any info!
I installed latest build and the problem is still here. It seems a DNS lookup problem (see the error below): "There was an error loading the remote feed for radioio.com - no boundaries.: (Failed to connect to http://www.radioio.com/opml/channelsLOGIN.php?device=Squeezebox&speed=high&membername=*******&pw=******* (Couldn't resolve IP address for: www.radioio.com) )" If I configure the proxy in the SlimServer all works well. If I do not, all dns-lookups starting from SqueezeBox fail, so no radio streaming works. The "DNS server" setting of the SqueezeBox is correctly set up to point to my W2K gateway with Internet Connection Sharing and SlimServer installed. It's pointless to notice that dns works perfectly and any other PC on my lan, including my gateway, succesfully connects to that URL (and that the problem did not exist in version 6.3.x and below). Could you give me some instructions on how to debug this network problem? Some debug mode to activate so I can send you the log? Luca
Ross, you probably have more experience than me working with proxy servers. Could you try to help Luca?
Luca, When you specify a static IP address for the Squeezebox, you must also specify the DNS servers. Are you already doing this? Curious: is DHCP not possible?
Subject: Re: Radio streaming not working Slim Devices Bugzilla ha scritto: >https://bugs-archive.lyrion.org/show_bug.cgi?id=4385 > > > > > >------- Comment #4 from ross@slimdevices.com 2006-11-03 16:34 ------- >Luca, > >When you specify a static IP address for the Squeezebox, you must also specify >the DNS servers. Are you already doing this? > >Curious: is DHCP not possible? > > > > >------- You are receiving this mail because: ------- >You are on the CC list for the bug, or are watching someone who is. >You reported the bug, or are watching the reporter. > > DHCP is not possible. I set up correcly the static IP, DNS and Gateway on the SqueezeBox. If I connect the Squeezebox to the SqueezeNetwork radio straming WORKS... with a LOT of stuttering (it seems the device stops responding to the remote sometimes). So my network settings are OK, otherwise I would not be able to connect successfully to SqueezeNetwork. Luca
Luca are you still seeing this? This sounds like a network throughput issue with the stuttering. Shall I have our support staff give you a call?
Hi Ross, just installed 6.5.4 and the problem is gone, thanx. Luca
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.