Duet won't connect to Library under 7.7.1

[Arch Hokie 06]

My duet won't connect to my library under v7.7.1 - r33735. The duet is running 7.7.1 r9557. Logitech Media Server is running on a MacBook running OSX 10.6.8. The duet is completely unusable. Is anyone else having these issues? Is this bug going to be fixed in a future version?

I'm getting frustrated with the Squeezebox equipment. When I bought this device at launch everything would typically work, but under the last few versions of the software it just seems like there are crippling bugs that destroy my experience. I feel like buying a touch would help, but based on my experience with this device I don't think I trust Logitech to keep their products working. Furthermore, I shouldn't have to tinker with this device every few hours just to keep it working.

[toby10]

Tried rebooting (unplugging) the Receiver? Tried rebooting (stop then start) LMS server?
Will it connect to MySB.com if you select an item within Internet Radio?

[Arch Hokie 06]

List of things I have tried:
1. Reboot receiver (unplug)
2. Reboot computer running LMS.
3. Doing a "Stop Server" then "Start Server" from the LMS settings.
4. Reinstall LMS.
5. Factory reset of Receiver.
6. Factory reset of Controller.
7. Factory reset of both receiver and controller at the same time.
8. Installing an older version of LMS (Tried 7.5.3 on the MacBook, the controller would not downgrade and only offered 7.7.1 as a software upgrade, the Duet would not find my music files and said to upgrade to the latest version of LMS to get it to work).

I'm running through a Wireless G/N network with the Receiver connected directly through ethernet. I've tried using two different routers to see if it was on the Router's side. A few other items that may be of help:

1. The Duet appears to connect directly to MySB.com and play Internet Radio. I only tried this this AM since I rarely listen to Internet Radio. After 15 minutes it is still working.
2. Every now and then it will connect to my server for a brief period of time. This morning I woke up and the light was white instead of blue. I tested it out by using Triode's Spotify app. 3/4 of the way through the first song, it stopped playing music. I then went and played a song from my Library that is located on the MacBook. It played for 30 seconds, then stopped and the Receiver changed back to a blue light. It's back to not finding my library when I tell it to with the Controller.

Thanks for the response Toby.

[Arch Hokie 06]

Also of note, I have a Radio running on wirelessly that cannot connect to my LMS server either. It appears to not want to connect to the official Spotify app either, but I haven't used the Radio enough lately to really give an accure description of any issues with it.

[toby10]

White is good, blue is bad. White means it is connected to your network AND to a server (MySB.com or LMS). Blue means it cannot connect to one or the other.

Seems to stream fine with MySB.com so it is unlikely a general network issue. Common cause for issues connecting too and staying connected too LMS is anti virus and/or firewalls.
Can you launch the LMS Control Panel (not the web UI) and go to Diagnostics? If yes, what is reported for ALL pings, ports, IP's?

[chrisspangler99]

I can't connect outbound on slimproto 3483 and http 9000 (status = fail) to mysqueezebox.com.
Otherwise all others are OK.

I'm also running 7.7.1 r9557 and can't connect to "My Music" for about the last week or whenever I updated to 7.7.1 running on Windows7.

I've only rebooted hardware and reinstalled the LMS software on my Win7 desktop, which I really never ever have to think about regarding upgrades. Typically they work, but I'm interested to see if there is a bug that won't let me connect to "My Music", which is most frustrating.

I have had no trouble listening to any Internet Radio or XM stations thankfully.

Appreciate any updates.

[anjenaire]

I finally updated my Duet yesterday. By taking the battery out I was finally able to download the update.I found out by trying to do a manual update via SC Card which necessitated taking out the battery that that was required.

I too had issues with the controller finding my media server. Tried the usual start/stop of server, rebooting PC, etc. I even tried to make sure I was on the same network. I attempted to add the network connection "Manually". That hosed up my controller big time and "repair network" left it in a constant spinning circle of nothingness. Another battery pull required.

Steps I took included deleting the old DHCP listing on the router matching the MAC address of the controller (thought perhaps it was conflicting with the controller trying to connect to the network after the update). Since I hosed up the network trying to manually adding the controller, I went the "Factory Reset" route to start all over (after pulling the battery to stop the "Repair Network" effort).

After this, it found the media server PC, the receiver (although following the screen instructions proved to be problematic; it didn't immediately find my receiver and instructed me to push the front button which resulted in a solid red light on the front of the receiver and no change on the controller. A re-power of the receiver and pulling the network cable out and reinserting it caused the light to go from red to white/blue on the front of the receiver. After that it found the receiver with its original name, and also my media server.

So far so good, seems to be working. I'll report back in a few days to see how long it stays connected etc. I had issues a few days ago after a power outage but reboots, router resets seemed to take care of it. This latest, after the update to 7.7.1 on the controller, seemed to require a factory reset to get everything lined up.

Hope that helps someone.

[Simon_loves_music]

I've had a Duet installed for several years, has been pretty stable once I realised it was foolish to take software updates too often! Once it is working, leave it, seems to be the best policy.

But recently I updated to 7.7.1 and now 7.7.2 r33893 (doh!) and I now cannot get the player to connect to the library, I just have the persistent blue light.

I also have a Squeezebox Radio, which is working fine and can connect to the library no problem. The Duet controller can also "see" both the squeezebox player and squeezebox radio from the "Choose Player" menu, and can act as a remote control for the radio no problem, but not the duet player.

I have tried the following:
factory reset of controller
factory reset of player
updated firmware on controller to latest
rebooting everything multiple times
tried connecting both over wireless, and ethernet

I can't seem to connect to sb.com either. Very frustrating. Has been broken like this for several weeks, not had the time to try and fix it.

Anyone have a suggestion ?

Thanks.

P.S. I will try to delete the DHCP reservation on my router and start again as suggested above by anjenaire; does it need to go to a new IP address to kick start it into life again?

[Simon_loves_music]

...so I tried deleting DHCP reservation, followed by factory reset on both parts of the DUET, still not working.

But then I just tried a battery pull on the controller, and wow, it now works with internet Radio at least! So finally I know the device is still alive at least, just can't make it connect to the server.... will now try a full reboot cycle, see if that works.

[w3wilkes]

Really had to jump through some hoops to connect this time!

One of my Duets gets transported between two locations. Brought it to the summer home, did the normal factory reset on the receiver and controller and when I went to configure it the receiver refused to connect to my LMS server. It would go as far as getting a IP on my network (blue light) but when I'd try to connect to my Squeezebox server it would fail and go back to the Try Again / Switch Library step on the controller.

After 2 days of mucking with it I did finally come up with a method to get the receiver connected to my Squeezebox server. First step was doing a factory reset on the receiver (hold button until fast red blink) while ethernet connected. Used UDAP to set the Squeezebox server IP which is static on my network along with some of the wireless network settings;

>discover
>conf 1
>set interface=0 lan_ip_mode=0 lan_gateway=192.168.0.1 lan_subnet_mask=255.255.255.0 primary_dns=192.168.0.1 wireless_SSID=MyNetName wireless_mode=0 wireless_region_id=14 wireless_channel=11 wireless_wpa_mode=2 wireless_wpa_cipher=3 wireless_wpa_psk=MyNetPass squeezecenter_address=192.168.0.16
>save_data
>reset

(MyNetName and MyNetPass are not my real SSID and PSK)

Then I pressed the receiver button just long enough to get into network setup (released as soon as it turned red) and used the controller to let DHCP connect the receiver to my wireless WPA2 AES(PSK) network. With what I'd set using UDAP it connected to my Squeezebox server immediately.