I thought Turbo-G modes needed every device on the wlan to be by the same manufacturer and have the same 3rd party extensions to the standard. I therefore wouldn't have expected it to work with the Squeezebox. Is this not the case?
Max KitKat Wrote: > I received my SB3s today (one wired, one wireless) and am having almost > this exact same problem, except that mine is not fixed by rebooting the > router. There have been quite a few posts to this forum describing > essentially the same problem with new SB2s (search "wireless DHCP"), > and based on my experience today, I think the problem originates in the > Sqeezebox. I had previously assumed that many of the people reporting > problems with their SB2s had only themselves to blame (using incorrect > passwords, leaving MAC filtering on, etc.) but after today I have a > different perspective. > > I'm running SlimServer 6.2 on a dedicated 2.4 ghz box running Windows > XP professional, with plenty of RAM and available disk space, wired to > a D-link DI-624 router (firmware version 2.7). I previously had a > wireless SB1 (w/ graphics) and then (until yesterday) a wireless SB2 in > the same location, and I never had a problem with either. I'm not sure > of the original firmware on the SB2, but it had been running the most > recent firmware release (26) without incident since I installed > SlimServer 6.2 a week or so ago. When originally installed, both the > SB1 and the SB2 successfully connected to my wireless network (SSID > broadcast OFF, WEP encryption ON) on the first run through the > configuration menu, and neither experienced any significant problems > thereafter. (BTW, yes, I am aware that this configuration provides a > level of security that many would consider inadequate). > > Prior to installing the SB3s today, I turned MAC address filtering OFF > on the router. I then connected the wired SB3, which obtained an IP > address in my local subnet (192.168.0.XXX) via DHCP and connected to > the SlimServer without any problems. > > I then powered up the wireless SB3 and began configuration. I input > the SSID and encryption key (which I triple-checked) of my network when > prompted, and the SB3 connected to the network. I then selected "Get IP > address automatically". The SB3 obtained an IP address beginning with > 169, i.e., automatic private network. I used the left arrow button to > back up, rebooted my laptop to make sure that the router's DHCP server > was working (it was) and tried again, with the same result. I then > chose "Static IP", entered a local IP address, and specified the IP > address of the router for gateway and dns (the router has dns > forwarding) and the IP address of the SlimServer box. Result: > "Problem: can't find SlimServer"... etc. At each stage of this process > at which connecting to SqueezeNetwork was offered as an option, I > attempted to do so, with no success. > > I then restored factory default settings on both the router and the > SB3. Even with the router wide open, the SB3 could not obtain an IP > address, and although it claimed to have connected to the wireless > network, it could not see the SlimServer box and could not access > SqueezeNetwork. I then tried to connect using the Ethernet port; the > SB3 obtained a local IP address via DHCP and connected to SlimServer > immediately. I went back to the wireless connection, but could not get > the SB3 to connect. The several times I checked the current > configuration settings through the SB3 menu, I noticed that the > wireless signal strength was reported as 0%, then would jump to 100%, > then slowly cycle down, then abruptly drop to zero, then repeat the > cycle. While this was going on, my desktop computer, which is one room > farther away from the router than the SB3, and also uses a wireless > connection, consistently reported signal strength as "good" or "very > good"; I then confirmed that the signal was not experiencing any > unusual fluctuation or degradation using Network Stumbler. I also sat > the SB3 unit a foot away from the router and tried the configuration > menu again, with no better luck than before. > > I sold my wireless SB2 on eBay and shipped it out yesterday, and I > therefore could not test its performance against the SB3 with the same > settings. I still have a wireless SB1 around, though (firmware > version: 40) (I already sold it on eBay but haven't yet shipped it out) > and so I restored it to factory default settings, disabled encryption on > the router, and went through the configuration menu. The SB1 connected > to the SlimServer with NO PROBLEM WHATSOEVER. Although the SB1 > reports weaker signal strength (hovering around 30%) than my computer, > it is not showing the 100% to 0% pattern that the SB3 reports. I found > this result so unbelievable that reset both the SB1 and SB3 to factory > defaults again, and went through the configuration menu with the two > units side by side. The SB1 connected without difficulty, the SB3 > obtained an automatic private network address, and would not connect > even when a static IP was entered. > > Being somewhat obsessive-compulsive, I was not prepared to accept the > possibility that my new SB3 suffered from an ailment that was beyond > my ability to fix. Suffice it to say that I ultimately determined that > the SB3 does not like D-Link's "Turbo G" mode, which is used on the > DI-624 (as well as on the wireless cards my laptop and desktop use to > access the router). Turbo-G is supposed to be fully backward > compatible/degradable, and neither the SB1 nor (based on my experience) > the SB2 had any difficulty in obtaining an IP address with Turbo-G > enabled. My SB3 finally obtained an IP address and completed > configuration correctly after I disabled Turbo-G on the router and set > the channel to 11 (SB3 also seems not to like the router's > "automatically select channel" option, but I didn't fully investigate > that problem). > > Although I'm happy that my SB3 is finally connected, I'm annoyed at the > time it's taken to get it working, and that my Turbo-G enabled devices > are now throttled from 108 mbps to 54 mbps. I hope this can help > someone else fix this problem should they encounter it. -- max.spicer The wild things roared their terrible roars and gnashed their terrible teeth and rolled their terrible eyes and showed their terrible claws but Max stepped into his private boat and waved good-bye ------------------------------------------------------------------------ max.spicer's Profile: http://forums.slimdevices.com/member.php?userid=23 View this thread: http://forums.slimdevices.com/showthread.php?t=16648 _______________________________________________ Discuss mailing list Discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
