nicketynick wrote:
> LOL - thanks Mark, I've been kind of figuring I was
pushing my luck.
> I just don't see why it should be so flaky - IIRC
SMC uses the same
> chipsets as Linksys, so why so different?
SMC doesn't know how to write firmware?
This isn't as flippant as it sounds. Certain
firmware versions broke some pretty basic
functionality on my SMC2804WBRP-G, and this would
have been discovered by the most basic testing,
i.e. actually running the firmware in a production
unit!
So they put out 20 different firmware versions.
Some worked worked for wireless networking, some
worked for wired networking, some made the USB
print server work, etc. etc. It was like playing
whack-a-mole.
> Here's the latest info: the SB3 does reconnect to
the router every 20
> seconds or so after a failure, but somehow still
doesn't reconnect to
> the server (this is with static ip, so shouldn't
it?) If I leave it
> alone, it will eventually reconnect, but it
sometimes takes quite a
> while. (BTW, slimserver never comes up and says it
can't find the
> player - shouldn't it?)
Perhaps communication is very, very slow - i.e. it
connects and sends enough packets to think it's
connected to SlimServer, but not enough packets to
actually do anything.
> So I'm stumped - maybe the Slim Devices tech guys
have some ideas?
>
That sounds reasonable. I wouldn't hold my breath
if I were you though, the device works perfectly
with a Linksys WRT54G running all firmware
versions under the sun, so there's nothing
inherently wrong with the Squeezebox's wireless
module IMHO, i.e. there's nothing they can do
differently.
--
___________________________________
Mark Lanctot
___________________________________
__________________________________________________________
Find your next car at http://autos.yahoo.ca
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
