Re: Wireless router

"Somebody." <somebody.@spamout.russdoucet.com> wrote in message
news:LUEjf.4362$43.19@nnrp.ca.mci.com!nnrp1.uunet.ca...
|
| "maybenot" <isomon@here.invalid> wrote in message
| news:8ewjf.1643$s96.596@trndny01...
| >
| > "Somebody." <somebody.@spamout.russdoucet.com> wrote in message
| > news:q4rjf.4332$43.3781@nnrp.ca.mci.com!nnrp1.uunet.ca...
| > |
| > | "maybenot" <isomon@here.invalid> wrote in message
| > | news:Ynpjf.1293$s96.48@trndny01...
| > | >
| > | > "Somebody." <somebody.@spamout.russdoucet.com> wrote in
message
| > | > news:tSgjf.4302$43.2011@nnrp.ca.mci.com!nnrp1.uunet.ca...
| > | > | WPA implementation on clients is horrible though, and it's
often
| > | > unstable to
| > | > | the point of unusability. WEP is easy to set up and use on
just
| > | > about any
| > | > | device.
| > | >
| > | > I disagree, you'll have problem with WPA if you are using a
non
| > | > standard hardware/drivers. As we all know WPA standard has
been
| > | > approved and ratified awhile ago. But there were hardwares
that
| > were
| > | > pre-built before the standard was approved, in this scenario
| > | > incompatible hardware/driver might arise. Newer firmwares
and
| > | > matured drivers should be available by now. For older
| > | > hardwares/drivers it's a must that you upgrade to the latest
| > | > firmware/drivers to prevent inconsistensy. For XPSP2 users MS
| > updated
| > | > their wireless clients(zero config) also, it is more choosy to
| > what AP
| > | > it connects to.
| > | > The Wi-Fi Protected Access 2 (WPA2)/Wireless Provisioning
Services
| > can
| > | > be downloaded here.
| > | > http://support.microsoft.com/default.aspx?scid=kb;en-us;893357
| > |
| > | I have a competent engineer who can't get WPA to be stable on
very
| > recent
| > | Dell Axiom, I couldn't get it to connect on a very recent Dell
| > Inpsiron, and
| > | I have a Toshiba that just refuses to communicate. And that's
just
| > some of
| > | our in-house devices. After patching my Dell 8500 it works fine
for
| > me, but
| > | WEP works for everybody in the door on their first crack,
including
| > guests
| > | in the boardroom.
| >
| > Do you have Intel pro/wireless 2200 BG on those problematic pc's?
If
| > yes, they are known to be unstable but the latest intel drivers
have
| > corrected that.
| >
| > | Many Access points need just the right firmware to be stable, ie
not
| > always
| > | the most recent one, but the one that actually works based on
real
| > world
| > | experience. WEP, any old firmware will do.
| >
| > I agree but if you have not tried the latest firmware you will not
| > know. Dell firmwares/drivers most of the time are two versions
| > behind. Have you tried the manufacturer's chipset firmware?
|
| We have done firmware/driver updates with some success and some
failure.
| But this is my point, it's very hard to get it to work. If WPA has
been out
| for 2 years, why am I still dicking with drivers and firmwares on a
4 month
| old PC? I'm not saying it's impossible, just far harder than it
should be.
| And if you get a less common device like a PDA, you may well just be
flat
| out of luck.

I have to agree, at this time there are still few manufacturer that
are a bit slow in applying the standard. They don't care as long as
their hardwares works with theirs. Fortunately, so far, I have not
encountered problems with mixed client/AP, I have mix clients
chipsets(broadcom, atheros, intel) that works with my BG AP. Since
all my clients are capable of g, I don't allow b access to my AP, that
probably makes a difference.
Received on Sat Dec 3 04:19:04 2005