Bugzilla – Bug 2728
Unable to connect to 3com 3CRWE754G72-A
Last modified: 2009-09-08 09:29:28 UTC
I've just bought two squeezebox3's to upgrade my squeezebox1's, but they squeezebox3 will not connect to my wireless network. They can see the wireless SSID, but it wont connect. The Router is a 3com 3CRWE754G72-A wireless ADSL modem router. I've tried it with all types of encription and even none. I've turned off all the security features (Firewall, DMZ, Mac filtering) but still it wont connect. I've upgraded the firmware on my router to 3coms latest, but still it wont connect. These new squeezeboxes are currently useless to me Please help. Keith
I've been reading the forums and have tried the following as well now. Entering the SSID manaully Turned off all long-range & Nitro features on the router upgraded to beta release 6.5.b1 I live in the UK so are using the Europe setting. I've tried all the other just in-case.
Have now tried a full factory reset of both my router and SB3. Making sure that all security features were of. Still no change.
Keith, please get in touch with our support team to help diagnose this issue. We'll keep the bug open to update after they help you out.
Keith, have you tried MANUALLY typing your SSID? When you choose to connect you are offered the SSID. Press the down button on your remote and choose to enter one manually. You'll then see your "offered" SSID already keyed in. Press right-arrow past all the SSID letters and then try. This seems to work for me on my NetGear WG602 V2 router (bizarre as though it sounds...) Jim
Jim, Yes I've tried entering the SSID manually, and many other ways too. Keith
Well at first glance it looked like slimdevices were interested in fixing this bug, but on refelction, they cant give a toss. they said they couldn't find the asme router as me so I found a few on the web and pointed them in the right direction. They didn't really update me, and I had to chase them every month. (I work in technical support and not updating customers who have problems is extremely bad). They said they were waiting for new driver and evntually said it was in rev6.2.2, but that was one that I had already tried and there was no difference. I downloaded it again, but still no change. They have now offered me a refund, but considering that it will cost me as much as new router to send it back to the US that the offer is a joke. I think they know there is a problem, and just hope that people will get fed up and sort out other options like getting new routers, going wired or switching to other manufacturers. I dont expect to hear anything anymore, so thanks for keeping an eye on this one. It wouldn't surprise me if this update dissappears very quickly after I've submitted it.
chris, can you reproduce this?
I have exactly the same problem and have sent an e-mail to support. Tried the following: * b only * g only * Network Stumbler to make sure no networks on the same channel * Putting the SB next to the wireless router * Flashing router with 1.31 firmware and resetting to factory defaults * Installing Slimserver 6.2.2 beta and updating SB firmware * Changing SSID. * Enabling /disabling WEP * Removed MAC address filtering. * Removed all security. (In reply to comment #6) > Well at first glance it looked like slimdevices were interested in fixing this > bug, but on refelction, they cant give a toss. > they said they couldn't find the asme router as me so I found a few on the web > and pointed them in the right direction. > They didn't really update me, and I had to chase them every month. (I work in > technical support and not updating customers who have problems is extremely > bad). > > They said they were waiting for new driver and evntually said it was in > rev6.2.2, but that was one that I had already tried and there was no > difference. I downloaded it again, but still no change. > > They have now offered me a refund, but considering that it will cost me as much > as new router to send it back to the US that the offer is a joke. > > I think they know there is a problem, and just hope that people will get fed up > and sort out other options like getting new routers, going wired or switching > to other manufacturers. > > I dont expect to hear anything anymore, so thanks for keeping an eye on this > one. > It wouldn't surprise me if this update dissappears very quickly after I've > submitted it. >
Hi, just did a forced firmware update on the squeezebox and I'm now running the server over the wireless router. Woooo hoooo!
This is fixed in firmware v36. The Squeezebox 2/3 will now connect to this router with no encryption and WEP. Some WPA issues remain, so I am leaving this bug open for the time being.
I have a fix that should appear in firmware 37. Will update this bug when it's available for download. I can confirm following the upgrade the router works with both WEP and WPA encryption.
Please try the latest nightly build with Firmware 37 and reopen if you have issues. Also, please note details of your configuration if you have not already.