Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 4 of 4
  1. #1
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    247

    Controller can't find any networks

    Hi

    I was doing a rebuild of my wireless system (had to recreate router config) and then I found that the controller couldn't connect to my SBS music library. The controller Diags showed that it had connected to my wireless net OK but had not obtained an ip address. After a reboot made no difference, I removed the battery and rebooted (ISTR this was one of the recommended actions a while back) - still no change. Then I tried to reconfigure Networking but this time the controller showed that it couldn't see any networks (Found Networks = 0) and there are quite a few!

    Eventually I found the Factory Reset menu option and after that the controller could view all the networks again and it connected fine. However is this kind of network config degradation thing normal? It seems quite drastic to have to do a complete reconfig from scratch.

    Controller firmware = 7.4.1 r7915
    SBS 7.4.2
    Router = Netgear WPN824v2 (WPA2) in wireless bridge mode

  2. #2
    It seems like once a week or so I have to do a full
    factory reset on the controller. It is somewhat annoying, but
    only takes a few minutes.

  3. #3
    I was having a similar issue after a recent SBS7.4.1/FW updates.

    I have a Duet and a pair of Booms and I found the SBC in particular would lose its connection (blue network icon). I also noticed the Booms taking longer to acquire an IP address via DHCP (sometimes they would even time out).

    I reconfigured my router and setup all SB components on Static IP's and I've not experienced the problems since. FWIW, all components are on an 802.11g wireless connection.

  4. #4
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    247
    Ick - I really don't want to have to use static ips. Plus I'm sure >99% of the Duet customers won't be wanting to do this either.

    Is flaky DHCP the smoking gun? Is there a controller error log? Are there bugs filed on this?

Posting Permissions

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