Quote Originally Posted by garym View Post
Great news. I hope your connection problems are over too. Do keep in mind that fixed IP addresses don't magically make wifi network interference disappear or solve every LAN issue. However, some of the SB players do have sorta flaky interactions with DHCP servers, so it certainly can't hurt (and may help) to have fixed IP addresses on all the things that don't leave your network.
Gary, you are so right. After working flawlessly for the last couple of weeks, disaster on Sunday. While I was away at grocery, my wife couldn't get the Duet to play and decided she need to turn the Duet on by holding down the button on the front. I actually don't know if this started the problem I had to deal with, or if the problem had already occurred and that's what caused her to push the button. By the time I got home, she had the Duet unplugged from AC. When I plugged it back in, it would go from red light to yellow light, then shut off. To get by this, I held down the button on the front until I got fast red flashing, then I set it up again. At that point, however; 1) it would get to blue (waiting to connect to LMS) and hold, and 2) the controller was saying it couldn't find "Mymusic" on the computer. When I checked my network map, the controller was not connected. After trying various things--like rebooting the computer, rebooting the Duet, etc., I finally decided to do a factory reset on the controller. This made things worse--or maybe marginally better. After that, trying to connect to Mymusic I would get a message saying something like "unable to resolve DNS for mysqueezebox.com." No amount of futzing around would solve it.

Long story short: one or some combination of these steps solved the problem. 1) Turned off anti-virus; 2) Turned off LMS; 3) rebooted router; 4) Turned LMS back on. Success! Then I went ahead and turned the AV (AVG Free) back on. Maybe there was an easier route to solving the problem, but that did the trick. I did this after Googling the error message and finding somebody else (in a non-Logitech forum) suggesting to reboot the router, so I hope the post here helps somebody else.