Bugzilla – Bug 9604
Receiver / Squeezebox do not reconnect to SqueezeCenter after PC Reboot
Last modified: 2008-12-15 12:40:54 UTC
After my PC is rebooted, the receiver has a blue light, the squeezebox has a black screen, and the duet has a menu reduced to 4 entries (even though the light is white - but it cannot connect to Receiver neither Squeezebox) and is not usable in that state Workaround: restart the router and everything works again (until I restart my PC...) This is 100% reproductible My analysis of the problem: Receiver background process is unable to reconnect to the SqueezeCenter when the connection to it has been broken but while Receiver was still connected to the network. However when Receiver get disconnected from the network, after the network is reconnected, the receiver process is able to restore the connection to both network and Squeezecenter. Information on my setup: ------------------------ router: NETGEAR WGT624 - Hardware version = V2 -Firmware version = V4.2.11_1.0.1 Wireless encryption = WEP 10 digits (64 bit encryption) I Use DHCP with IP address reservation for each device Standard Wireless setup: Everything connected Wireless My SqueezeCenter: 7.2 - 22900 @ Tue Aug 26 11:27:23 PDT 2008 - Windows XP - FR - cp1252 My Receiver Firmware version: 47 My Squeezebox Firmware version: V3 - 112 My Controller Firmware version: 7.2 r2907
ross does this sound like it's covered by some of the issues you're looking at?
I wonder if this is bug 9425. Interesting that you are one of the few with r2907. I'm trying a few tests today with r2907 but so far I'm unable to reproduce this. Can you reproduce this with r2873?
(In reply to comment #2) > I wonder if this is bug 9425. Interesting that you are one of the few with > r2907. I'm trying a few tests today with r2907 but so far I'm unable to > reproduce this. > > Can you reproduce this with r2873? > No I don't think it is bug 9425. I have checked that my contoller get the correct IP address and is actually connected to the internet (since I can see pictures from flickr). Its is only a blue light not a red one. Same thing for the squeezebox. It has a black screen (nothing displayed), but If I use the remote I can switch to the SqueezeNetwork, but not to the squeezeCenter. What is particular to my installation is that I use reserved IP address (I went early to that setup to prevent any problem of devices having each time a different address). I wonder if it could be the cause of the bug I really don't know what has done that I have a beta firmware since I have never downloaded so far any beta version of the squeezeCenter. Also I don't think it will make any change since my squeezebox has the same problem than the controller (can connect to network but not to squeezecenter). It has to be noted that when resetting the router, both squeezebox and duet recover and connector the squeezeCenter.
One thing I found on one particular router (a Netgear WGR614v7) with reserved ip addresses is that sometimes the router gives out the reserved ip address to a device (as it should) but sometimes it would just give out any ip address from the address pool. And by device I mean anything not in particular a SB, but for instance an iBook or an iPhone. So I am wondering if something similar happens with your router which could then either end in two devices having the same ip address or because one device got an ip address which actually would have been reserved for another device, the other device doesn't get an ip address at all. Just some thoughts, might or might not be the actual issue here.
Can you change the DHCP lease time on your router? Could you try setting it to 5 minutes and see if this issue occurs more frequently than once per day? r2907 was released briefly, it shouldn't be a problem. I've been testing with r2907 and am still unable to reproduce.
To answer to Felix, I checked on the Router interfaces, all the devices are attached to the network with their respective IP address. I can even ping each of the devices from the computer. SqueezeBox can connect to SqueezeNetwork (Internet) but fails to connect to SqueezeCenter in that state. Could it be a question of port number that could change and may be used by the communication between device and SqueezeCenter?? Because everything looks normal from IP address perspective. To answer to Ross, It does not seem that I can set the router lease time, I can't see such parameter in the router administration interface. BTW: I found another way to reproduce the problem: Instead of rebooting the PC where SqueezeCenter runs, it is enough to disconnect the PC from the Network and connect it again, then the devices WON'T reconnect to the SqueezeCenter. All the other devices remain connected to the network in that operation, only the PC get disconnected from network a few seconds. But If I try another scenario like simply stop the SqueezeCenter service and then restart it while the PC remains connected to Network all the time, then all devices WILL reconnect to the SqueezeCenter after the service has restarted.
Maybe the PC comes up with an new ip address and the backup would be to try to connect via the PC name. Maybe that fails too if the PC name contains some special characters? What is the name of your PC? QA: Could you try with a SC running on a PC with a name with some special characters and also make sure the PC gets a new IP address. Thanks
(In reply to comment #7) > QA: Could you try with a SC running on a PC with a name with some special > characters and also make sure the PC gets a new IP address. Sure thing, however XP doesn't allow non-standard characters.
The name of my PC is PC-HOME. IP address is always the same: The PC is also using a IP address that is reserved by the router: 192.168.0.8. For your information, Squeezebox is using 192.168.0.2, Receiver is using 192.168.0.3 and Controller is using 192.168.0.4.
Thanks for the feedback. I guess, I got carried away yesterday at the bug meeting. If the PC in question always gets the same IP address then the name of the PC doesn't even matter. Must be something else then.
I think I solved the problem. Being inspired by some posts in the forum, I decided to invest in a new router (NETGEAR WNR834B(v2)), and in a new WIFI PCI card for the PC (NETGEAR WN311B which is recommended by NETGEAR to use with this router), both previous materials were 4 years old (still already WIFI 802.11G, the new ones I bought are WIFI 802.11N draft) ...And everything seems to work well now! Let me some days to confirm that, but I don't reproduce the behavior that I describe in this bug report. I have to notice that changing only the router was not enough since I experienced that the "old" WIFI card that I had on my PC did not talk well with the new router (and while I was still able to connect and surf on the internet, the connection was not enough good for playing music with squeezebox/duet). It worths mentioning since in the forums a lot of attention is put on the router, but not on the WIFI card used on the PC that hosts the SqueezeCenter. I have verified that having an optimal combination between PC and router (in my case based on WIFI 802.11N draft) does really matter for the Squeezebox/Duet. So it looks that Squeezebox/Duet are very demanding regarding the Wireless network, but if this one is up to date then it works fine.
I confirm: with new material, this is working fine now.
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.