Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Can't connect

  1. #1

    Can't connect

    So, I'm probably doing something silly here. I installed 7.4.1 on ubuntu 9.04 on a new mediabox (zotac atom n330 based) I built.

    Version: 7.4.1 - r28947 @ Tue Oct 20 07:58:02 PDT 2009
    Hostname: mbox
    Server IP Address: 127.0.0.1
    Server HTTP Port Number: 9000
    Operating system: Debian - EN - utf8
    Platform Architecture: i686-linux
    Perl Version: 5.10.0 - i486-linux-gnu-thread-multi
    MySQL Version: 5.0.75-0ubuntu10.2
    Total Players Recognized: 0

    I can connect to the squeezecenter over http port 9000 locally. No players are recognized and I can't browse the squeezecenter interface.

    The port 9000 appears open when I scan with nmap from my other ubuntu box.

    I see this error in the log:

    09-11-01 09:15:14.7996] Slim::Utils::IPDetect::_init (113) Warning: Couldn't call connect() - falling back to 127.0.0.1


    This makes me wonder whether it's not the case that squeezecenter is somehow only accessible through 127.0.0.1 (as though it were "bound" to the lo rather than to wlan0 or eth0).

    The other thought is that perhaps I messed around with samba. I can connect to the mediabox with my other ubuntu box. Both have samba running and I'm wondering if I somehow am limiting access to WORKGROUP. The players and my laptop (xp) aren't in that WORKGROUP.

    I add this possibility because I can now stream to the ubuntu box and get to the web interface from it, but not from the laptop or from the players.

    Weird, weird.
    I've disabled ufw (and created rules to allow access on the home network to port 9000 for the relevant ip range).

    When I'm logged into the mediabox, I can stream to mplayer at both localhost and 192.168.1.103 (router assigns this statically). Also I can ssh to another box and stream to that machine. Yet no player will connect to the server and I can't get the web-page from the other box.

    edit--rebooting the xp laptop gets me the web interface and streaming to laptop. Still nothing from the players. Reset to factory defaults does nothing. Boom firmware was up to date 50, but squeezebox2 was 127. No difference in behavior in any variation.

    I'm at a loss. It has to be something really silly that I'm missing here.
    Last edited by Clnanderson; 2009-11-01 at 08:20.

  2. #2
    Junior Member
    Join Date
    Feb 2007
    Posts
    28

    Similar problem...and possible workaround

    I see the same problem with the following exceptions. I can get to my installation from a windows pc by hitting http://8250-ubuntu:9000 but cannot get there from my linux pc.

    As a workaround I can get to it using http://192.168.0.189:9000/ but since I am using DHCP I realize this will ultimately change.

    This workaround might help some of the experts around here diagnose both of our problems.

  3. #3
    From my server.prefs file.


    allowedHosts: 192.168.1.110
    artfolder: ''
    audiodir: /home/music
    authorize: 0
    bandInArtists: 0
    bindAddress: 127.0.0.1

    I deleted the entry for allowedhosts and bindaddress. They are both blank now.

    Version: 7.4.1 - r28947 @ Tue Oct 20 07:58:02 PDT 2009
    Hostname: mbox
    Server IP Address: 192.168.1.103
    Server HTTP Port Number: 9000
    Operating system: Debian - EN - utf8
    Platform Architecture: i686-linux
    Perl Version: 5.10.0 - i486-linux-gnu-thread-multi
    MySQL Version: 5.0.75-0ubuntu10.2
    Total Players Recognized: 0

    Still no players connecting.

    For kicks I deleted the server.prefs file and restarted and it generated the file with 192.168.1.103 as allowed hosts and 127.0.0.1 as the value for bindaddress. Not sure what these mean I guess.
    Last edited by Clnanderson; 2009-11-01 at 09:54.

  4. #4
    Rebooting seemed to work. The players show up in squeezeboxcenter. I even managed to play a song on one of them. But then something happens and they are dropped and are unable to connect anymore.

    This is getting even stranger.

    Could zeroconf have something to do with this? I publish a localnet ftp service off the mediabox, so that I can load files onto it.

    I've stopped samba, ufw, and zeroconf, and am at a loss.
    Last edited by Clnanderson; 2009-11-01 at 11:27.

  5. #5
    Senior Member Diana's Avatar
    Join Date
    Sep 2006
    Location
    UK
    Posts
    295
    Quote Originally Posted by Bokenrosie View Post
    ...As a workaround I can get to it using http://192.168.0.189:9000/ but since I am using DHCP I realize this will ultimately change...
    There may be a way to fix the DHCP issue. Have a look at your router's set up screens: you may be able to bind the IP address to the specific computer (actually the MAC of its network card). The router's DHCP will then assign the same IP address to your computer every time you boot it. (I do this with my SqueezeCentre server and it works perfectly.)

    HTH

  6. #6
    Member
    Join Date
    Mar 2008
    Posts
    54
    I am having a connection issue after reinstalling the os (ubuntu 8.04 server). I have a static ip set up on the server and can reach the web front end from it. The software was "upgraded" to 7.4.1 as I selected from the stable repository.

    The receiver light stays yellow even if I run an ethernet cable to it.

    I can reach the server and stream music remotely (have dynamic ip set up on dyndns.org).

    I'm looking for advice on how to troubleshoot this...

  7. #7
    Quote Originally Posted by Clnanderson View Post
    Rebooting seemed to work. The players show up in squeezeboxcenter. I even managed to play a song on one of them. But then something happens and they are dropped and are unable to connect anymore.
    Check with "lsof -i -n | grep squeeze" if SB Server is listening.

    Quote Originally Posted by Clnanderson View Post
    I've stopped samba, ufw, and zeroconf, and am at a loss.
    Maybe ufw is not disabled correctly. Check with "iptables -L -n".

    But your problem with a dropped connection after it was working sounds a bit strange. Maybe an ethernet issue? You mentioned wlan0 and eth0. Having both connected to the same network may cause trouble.

  8. #8
    Quote Originally Posted by Bokenrosie View Post
    I see the same problem with the following exceptions. I can get to my installation from a windows pc by hitting http://8250-ubuntu:9000 but cannot get there from my linux pc.

    As a workaround I can get to it using http://192.168.0.189:9000/ but since I am using DHCP I realize this will ultimately change.
    That's a problem with name resolution. It has nothing to do with Clnandersons problem.

  9. #9
    Member
    Join Date
    Mar 2008
    Posts
    54
    my problem was in getting a factory reset. I tried a few different ways to no avail. It worked when I did the "hold left arrow for five seconds", which brought up the settings menu, from which I could do a factory reset. After that I was able to connect to the network.

  10. #10
    Thanks for the suggestions!

    No output from lsof -i -n | grep squeeze

    With lsof -i

    The only listening file is listening on 5900 (vnc server), though ssh and vsftp and squeezeboxserver are all running processes.

    Netstat gives me a bunch of connections to 9000 from the localhost/mediabox.

    When I ssh in from desktop I see the connection both in Netstat and as an established connection in lsof -i.

    But neither SBS nor SSH show as "listening" like vnc does.

    On ufw, it looks disabled. Iptables gives no rules when it is disabled and if I enable it, I see all of my rules limiting access to the localnet. But it makes no difference in players connecting.

    Nmap scan of mediabox gives me

    PORT STATE SERVICE
    21/tcp open ftp
    22/tcp open ssh
    5900/tcp open vnc
    9000/tcp open cslistener
    9090/tcp open zeus-admin

    I can stream from desktop (ubuntu 9.10) with mplayer and it works and shows up in netstat. But doing that doesn't change the output of lsof (though ssh-ing did).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •