I was connected to SqueezeNetwork, playing one of the natural sounds. I paused the playback.
A few seconds later my SB2 crashed (can't remember precisely whether it crashed whilst paused - I may have unpaused the playback and that caused it to crash). I didn't think too much of it. However, following the restart, I couldn't reconnect to my normal wireless network. The SB detected my SSID, and even reported a signal strength, but it refused to connect. I tried rebooting my router and restarting slimserver. I tried to restore my SB to factory defaults, and powered off the unit for good measure. Again, the SB could see the network, but upon entering my WPA2 passphrase, I got the countdown whilst it tried to connect to the network, which failed. I noticed a very quiet ticking coming through my passive speakers (connected to the headphone jack) - I'd say about 2Hz. I noticed that my router listed the players MAC address in the list of connected wireless clients. In the end, I turned off wireless security, MAC address filtering, etc, and did another factory reset of the SB2. Eventually it reconnected. I tried returning to my usual WPA2-Mixed (TKIP+AES) security mode, and changed the SB2 to use WPA2 and it failed to connect again. I now find that it works if I select WPA (not WPA-2) from the SB2, even though the wireless router is set to WPA2-Mixed. I'm sure this wasn't what I had set up before. I had to actively change my security settings to reconnect - so what has SqueezeNetwork done to the firmware to cause this? LinkSys WAG54GX2 WinXP Pro. 6.2.2 Firmware 33 Phil _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
