05-21-2012 06:02 PM
I have two Squeezebox radios that will not reconnect to my wireless network. Both have been functioning well for quite awhile. My network went down yesterday for a few minutes and when it came back up neither Squeezebox would reconnect. Actually that's not entirely true as they both appear to connect when configuring. Network Health diagnostics check out fine on both units. They both will show all the wireless configuration data correctly and information about the network (IP addresses, etc.) They both see the network. They just don't reconnect. I factory reset one of them and it still doesn't work. It's odd that both devices are behaving exactly the same. I know it's something on my end but I'm not sure what. The wireless network works fine with all other devices (laptops, kindles, iPad, Roku, etc.) I've not cabled one them to the router yet to test a direct connection. I'll get a cable tomorrown and try that. Any ideas what to look at in the router (Linksys WRT54G)? Thanks, Tim
05-21-2012 06:32 PM
Just tried with an Ethernet cable connected to the router and it doesn't work.
I also disconnected my ISP's Ethernet cable from the router and put it directly into the Squeezebox and it doesn't work either so it's not the router.
05-21-2012 09:53 PM
If you can connect your network, but you can't connect to the internet, then you can fix the problem by entering a static dns but unfortunately, it seems to be impossible to do that on a Squeezebox device. I've seen this bug before. In short, you'll see a DNS server listed as 192.168.1.1 or something else. In reality, the DNS server being used is based on your internet provider (comcast, 184.108.40.206 abd 220.127.116.11). A good one to know is Google's public dns (18.104.22.168 and 22.214.171.124.) Devices usually handle this fine. In other words, my iPhone and iPad list the DNS as something related to the ip address which might be 192.168.1.4, and the DNS will say 192.168.1.1 which is probably the same as your gateway, but the dns server is really the 126.96.36.199 address. However, I've seen this before where a device can't resolve the DNS correctly so it connects to your netork, but not the internet. Sorry for the long-winded reply. I'm just frustrated that it is not a simple task or even possible) to assign static addresses to the Squeezebox.
05-22-2012 02:03 AM
Tim I was having the same problem. I took blueice007's advice and actually changed the DNS settings in my router to my ISP's static Primary and Seconday DNS instead of using the "get automatically from the ISP" option. I have comcast and used 188.8.131.52 for primary and 184.108.40.206 for secondary and all of a sudden everything was back to normal with my squeezebox radio. Not sure what caused the problem initially as mine seemed to occur on the same day yours did and i have seen some other posts about the same issue.
05-25-2012 04:38 PM
Thanks for the replies. I haven't had time to mess with them but now, magically, they are both connected and working fine. I know there is no magic so it sure would be nice to know what changed. I'll keep the suggested fix in mind in case (when?) it happens again. Thanks, Tim