PDA

View Full Version : No music... almost no connection



Khuli
2005-06-21, 09:23
My new wireless SqueezeBox turned up today - got it set up and finding the SlimServer within minutes, and even browsed some albums (albeit very slowly) - hurrah!

However, I can't get the thing to play - it 'says' it's playing, as does the SlimServer, but the network isn't transmitting, and the elapsed time on the SB is firmly on 0.00
Almost every time you move between menus it says 'Connecting to SlimServer..' for several seconds.

So what's happening? (or not happening) SlimServer is on a Win2k pc connected to a router, as is a wireless access point... it just seems that the data transfer rate is so pathetically low it can't play an mp3! The PC can see the network just fine and the signal strength on the SB is 100%.

Any ideas? Thanks.

mherger
2005-06-21, 09:53
> However, I can't get the thing to play - it 'says' it's playing, as
> does the SlimServer, but the network isn't transmitting, and the
> elapsed time on the SB is firmly on 0.00
> Almost every time you move between menus it says 'Connecting to
> SlimServer..' for several seconds.

Do you have your firewall configured to accept ports 9000 and 3843?
(http://www.slimdevices.com/pi_faq.html#networking-firewall)

I had similar symptoms when port 9000 was blocked.

--

Michael

-----------------------------------------------------------
Help translate SlimServer by using the
StringEditor Plugin (http://www.herger.net/slim/)

Khuli
2005-06-22, 06:36
No firewall running on Win2k... if it's all connected via ethernet it does work ok. The WAP is fine, as other PCs and laptops can get files from the network - it just seems to be the Squeezebox...

mherger
2005-06-22, 06:48
> No firewall running on Win2k... if it's all connected via ethernet it
> does work ok. The WAP is fine, as other PCs and laptops can get files
> from the network - it just seems to be the Squeezebox...

Can these wireless PCs connect to the slimserver? Can they open
http://yourserver:9000? Connect to stream
http://yourserver:9000/stream.mp3 (using WinAmp or similar)?

--

Michael

-----------------------------------------------------------
Help translate SlimServer by using the
StringEditor Plugin (http://www.herger.net/slim/)

Khuli
2005-06-22, 08:32
Can these wireless PCs connect to the slimserver? Can they open
http://yourserver:9000? Connect to stream
http://yourserver:9000/stream.mp3 (using WinAmp or similar)?


They can reach http://yourserver:9000 just fine

http://yourserver:9000/stream.mp3 opens Media Player but nothing gets loaded. The ethernet-networked PCs also get this (even when SqueezeBox is playing via ethernet) - is stream.mp3 whatever is currently playing, or did you mean the path to a mp3 file?

Interestingly, the Squeezebox works (when connected via ethernet) and SlimServer is on a PC connected via wireless, but not vice versa.

mherger
2005-06-22, 09:05
> http://yourserver:9000/stream.mp3 opens Media Player but nothing gets
> loaded. The ethernet-networked PCs also get this (even when SqueezeBox
> is playing via ethernet) - is stream.mp3 whatever is currently playing,
> or did you mean the path to a mp3 file?

stream.mp3 will connect the software player of your choice to the
slimserver. You can then select your songs from the web interface.

> Interestingly, the Squeezebox works (when connected via ethernet) and
> SlimServer is on a PC connected via wireless, but not vice versa.

Are you sure your wireless AP isn't filtering ports?

What's your PC's and your SB's IP configuration?

--

Michael

-----------------------------------------------------------
Help translate SlimServer by using the
StringEditor Plugin (http://www.herger.net/slim/)

Khuli
2005-06-23, 05:43
Are you sure your wireless AP isn't filtering ports?


Not postive, although there are no options for setting ports, or doing any kind of filtering, on the setup menu.

Connecting to stream.mp3 from a networked PC doesn't produce any sound either (via ethernet, no wireless involved). Even media player on the same PC as SlimServer won't connect :(

Maditude
2005-06-23, 08:20
Are you sure your wireless AP isn't filtering ports?


Not postive, although there are no options for setting ports, or doing any kind of filtering, on the setup menu.

Connecting to stream.mp3 from a networked PC doesn't produce any sound either (via ethernet, no wireless involved). Even media player on the same PC as SlimServer won't connect :(
Is the server actively playing anything? point your web-browser at your server's port 9000, and select some music to play, then you'll get something going on that stream url...

Khuli
2005-06-23, 10:20
Is the server actively playing anything? point your web-browser at your server's port 9000, and select some music to play, then you'll get something going on that stream url...

The Server is playing.. I can get the SB to work via ethernet.

Connecting to http://192.168.1.108:9000 brings up the SlimServer panel, but http://192.168.1.108:9000/stream.mp3 opens Media Player, but it doesn't play anything.

kevin
2005-06-23, 12:24
Khuli,

Could you try this with SoftSqueeze and see if it helps? You can install and launch it by clicking the SoftSqueeze link on the bottom left of SlimServer's main page.

Khuli
2005-06-23, 18:22
SoftSqueeze does work - installed on my PC it does browse and play the files on the PC with SlimServer installed.

Of course, this is all via ethernet, which works fine with the SqueezeBox too, but a least it works!

.... as an update, I installed Softsqueeze on a (wireless) laptop, and it works perfectly, which leads me to believe that there's nothing wrong with my network, the problem is with the SqueezeBox...

tiny_home
2005-06-24, 03:20
My Squeezebox has been working fine for a month or so. However at the weekend it decided to stop playing.
Everything seems to load without problem. I can add and remove songs, fast forward through them etc and it shows up on the actual squeezebox without problem. However despite the fact it says it's playing, the counter jumps to 3 seconds into the song and just sits there.
Strangely, before this happened, the squeezebox started to display the song in front of what it was actually playing which was a bit weird. Coincidently I did change the display format the day before this started happening so maybe this is an unrelated bug ?
The server software is on a W2K machine and the squeezebox is connected wirelessly. My plans are to uninstall the server softwware and reinstall to see if that fixes it.
Also will try and plug the squeezebox directly into my hub to see if it's a wireless issue. Wireless connectivity is 75% though and it has been working without problem up until now.
I have no firewall running on the PC (have disabled it to see if it was a problem).
Could it be an issue with the streaming software on W2k ?

Simon

kevinyoung
2005-06-27, 09:41
I just bought a Squeezebox a few weeks ago with the intention of using the wired connection, but i bought the wifi'd option anyway just in case.

Its been working fine straight out of the box on the wired link, but after reading the above postings, I thought i'd try out the wi-fi link. Seems I'm experiencing similar problems. It finds the access point, collects an IP addr and then usually simply gives up and shuts down (display goes off).

I'm using 802.11g, 64-bit shared key. One other device is usually sharing the airwaves (laptop).

I'll be happy to checkout any suggestions

Kevin

Khuli
2005-07-01, 03:09
Further to the help provided to Andy in http://forums.slimdevices.com/showthread.php?t=14804 here is what I have on my system.

NB: The SB2 has an IP address of 192.198.1.100 and the PC with SlimServer installed (music-server) is 192.168.1.108
jon-desktop is my other PC.

Running on Win2K, no firewall or anti-virus, and Softsqueeze works fine on a wireless laptop, and on the music-server.
Below is all the other info I currently have:


SlimServer Version: 6.1b1 - 3582 - Windows 2000 - EN - cp1252



Ping test from the music-server:


Pinging 192.168.1.100 with 32 bytes of data:

Reply from 192.168.1.100: bytes=32 time=6ms TTL=64
Reply from 192.168.1.100: bytes=32 time=10ms TTL=64
Reply from 192.168.1.100: bytes=32 time=4ms TTL=64
Reply from 192.168.1.100: bytes=32 time=11ms TTL=64

Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 11ms, Average = 7ms



Result of netstat -a


Active Connections

Proto Local Address Foreign Address State
TCP music-server:epmap music-server:0 LISTENING
TCP music-server:microsoft-ds music-server:0 LISTENING
TCP music-server:1025 music-server:0 LISTENING
TCP music-server:1027 music-server:0 LISTENING
TCP music-server:1029 music-server:0 LISTENING
TCP music-server:3149 music-server:0 LISTENING
TCP music-server:3150 music-server:0 LISTENING
TCP music-server:3483 music-server:0 LISTENING
TCP music-server:9000 music-server:0 LISTENING
TCP music-server:9090 music-server:0 LISTENING
TCP music-server:3149 music-server:9000 ESTABLISHED
TCP music-server:3150 music-server:9000 ESTABLISHED
TCP music-server:9000 music-server:3137 TIME_WAIT
TCP music-server:9000 music-server:3141 TIME_WAIT
TCP music-server:9000 music-server:3143 TIME_WAIT
TCP music-server:9000 music-server:3144 TIME_WAIT
TCP music-server:9000 music-server:3149 ESTABLISHED
TCP music-server:9000 music-server:3150 ESTABLISHED
TCP music-server:netbios-ssn music-server:0 LISTENING
TCP music-server:3146 JON-DESKTOP:netbios-ssn TIME_WAIT
TCP music-server:3483 192.168.1.103:25103 ESTABLISHED
UDP music-server:microsoft-ds *:*
UDP music-server:3483 *:*
UDP music-server:2028 *:*
UDP music-server:2059 *:*
UDP music-server:3088 *:*
UDP music-server:netbios-ns *:*
UDP music-server:netbios-dgm *:*
UDP music-server:isakmp *:*



Result of netstat -n


Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:3154 127.0.0.1:445 TIME_WAIT
TCP 127.0.0.1:9000 127.0.0.1:3143 TIME_WAIT
TCP 127.0.0.1:9000 127.0.0.1:3144 TIME_WAIT
TCP 127.0.0.1:9000 127.0.0.1:3149 TIME_WAIT
TCP 127.0.0.1:9000 127.0.0.1:3150 TIME_WAIT
TCP 192.168.1.108:3483 192.168.1.103:25103 ESTABLISHED



With SlimServer off, and SB2 off, netstat -a


Active Connections

Proto Local Address Foreign Address State
TCP music-server:epmap music-server:0 LISTENING
TCP music-server:microsoft-ds music-server:0 LISTENING
TCP music-server:1025 music-server:0 LISTENING
TCP music-server:1027 music-server:0 LISTENING
TCP music-server:1029 music-server:0 LISTENING
TCP music-server:3164 music-server:0 LISTENING
TCP music-server:microsoft-ds music-server:3164 ESTABLISHED
TCP music-server:3164 music-server:microsoft-ds ESTABLISHED
TCP music-server:netbios-ssn music-server:0 LISTENING
TCP music-server:3163 JON-DESKTOP:netbios-ssn TIME_WAIT
UDP music-server:microsoft-ds *:*
UDP music-server:2059 *:*
UDP music-server:3088 *:*
UDP music-server:netbios-ns *:*
UDP music-server:netbios-dgm *:*
UDP music-server:isakmp *:*



Connecting from music-server: telnet localhost 9000 gives blank screen. Typing GET / gives several screens of HTML, and I get the same when connecting from my desktop.


However, the SB2 still doesn't want to connect wirelessly. If anyone has more ideas I'd welcome them! I tried emailing support@slimdevices.com but apart from one brief reply several days ago, they then never replied to my answering email :(

Jon

tiny_home
2005-07-01, 05:40
Just to update on my issue. Unfortunately I didn't do things in a controlled way so can't give exact ideas about what fixed things.

Following the SB2 stopping playing music, I did the following:

1. I set the display mode back to the default setting which is Tracknum, Artist - Title (third option down on the Slimserver choices)

2. I reloaded the music library again from the slimserver software from server settings/performance/wipe cache. (Note: Server settings/rescan doesn't seem to reload things).

3. I physically unplugged and moved the SB2 down to sit right next to the netgear wireless router.

I then turned the SB2 back on, pushed play and it started working again. I then unplugged it, moved it back to it's previous position and powered it on. It worked fine again and has continued to do so (Wireless signal strength is 66%).

It also now shows the correct song again when it's playing.

So I wonder if mine was caused by either a bug with changing display information on the SB2 or a possible corruption with the music database stopping it streaming. Who knows but it's something else for you to check to see if that cures your problems.

Khuli
2005-07-01, 08:11
Thanks - I tried those (just in case), but no luck...

Triode
2005-07-01, 09:51
Could you turn on d_http debugging on the server and try to play something. Post what it says.

Khuli
2005-07-02, 02:27
Log file attached.

Selected d_http then clicked play, waited a few secs, clicked stop, then unselected d_http.

Triode
2005-07-02, 02:48
This seems to suggest a client does connect to slimserver and start to stream.

If you stop the server and restart from a cmd window, you will be able to avoid seeing web traffic and this may help focus on the streaming messages.

1) Stop the server
2) open a cmd window and change directory to the location of slim.exe
3) run: "slim --d_http"
4) nativate via player menu and pres play - leave for several seconds
5) Cut and paste the output from the cmd window and look for what happens.

Khuli
2005-07-02, 04:33
The executable in the new version of Slimserver is Slimtray.exe so should this be "slimtray --d_http"?

If I stop slimserver, and run the above command, nothing happens at all (no errors either), and slimserver is not restarted.

Triode
2005-07-02, 05:11
I think there is still a slim.exe executable for the compiled server C:\Program Files\SlimServer\server\slim.exe Please use this.

Khuli
2005-07-02, 16:32
ah yes, that worked. File attached.

Thanks for your time on this!

Scooter
2005-07-03, 03:51
I just bought a Squeezebox a few weeks ago with the intention of using the wired connection, but i bought the wifi'd option anyway just in case.

Its been working fine straight out of the box on the wired link, but after reading the above postings, I thought i'd try out the wi-fi link. Seems I'm experiencing similar problems. It finds the access point, collects an IP addr and then usually simply gives up and shuts down (display goes off).

I'm using 802.11g, 64-bit shared key. One other device is usually sharing the airwaves (laptop).

I'll be happy to checkout any suggestions

Kevin

Kevin - these symptoms usually indicate a poor wireless connection. You can confirm this by moving the Squeezebox into the same room as the access point and powering it up. If it now behaves, then it's a simple signal issue.

I had no problems with the Linksys 11b kit I was using in ad-hoc mode, but when I updated it all to 11g (using more Linksys kit, inc an access point now) wireless performance went down the toilet. I think the claimed ranges for these things are for "on the moon, outside the lander, with no land features between the 2 devices". On Earth, in my house, with it's troublesome air and walls, the range is about 50 foot. Also look for things that may be a source of interfrence such as large electric motors, microwave ovens and transformers for things like low voltage lighting.

I got around to fixing it last night by relocating the wireless bridge on my problem player.

Hope this helps.

Cheers,
Scoot.