Hi
When using regular End-User Wireless hardware it is better to leave the
Wireless setting left at the default.
Playing with some of the variable just because they have "exotic" names
usually impede the signal rather than making it faster.
The None default setting are suitable for special networks that use more
sophisticated enterprise level equipment.
Jack (MS, MVP-Networking)

"poster" <poster.3ivcva@DoNotSpam.com> wrote in message
newsoster.3ivcva@DoNotSpam.com...

>
> this problem is not related to security options, this happen to me when
> i have activated the "Xpress technologie" on my router ( actualy is not
> mine
>
> so, i think, its about some frame compression/bursting that is not
> supported by the station adapter
>
> the Xpress technologie (maybe is the same technologie of the Atheros
> SuperG) is supposed to accelerate (some how) the packets in
> transmission, and when the STA is not receiving correctly those packet
> its like his not receving any response from "authentification request"
> he sended. so it result an "Authentification timeout"
>
> i have spend a lot of time to resolve this problem but i cant do
> anything with my Atheros 5005G
>
>
> --
> poster
> ------------------------------------------------------------------------
> poster's Profile: http://forums.techarena.in/members/poster.htm
> View this thread:
> http://forums.techarena.in/windows-v...ork/816806.htm
>
> http://forums.techarena.in
>

I have had an HP laptop since December 07 with Vista Home Premium, usin
a Belkin router. I have connected WPA-TKIP with no problems. My daughte
just bought a laptop with latest version of VISTA Home Premium. Sh
could not connect. After lots of tech calls, she could set up if profil
was WPA2-AES but then I could not connect. I updated the router drive
(had 2 files to download then updated using Belkin site). I also update
the Network Adapter driver using the VISTA find feature under Networ
Adapter properties - it automatically searched online, found the correc
file, updated. My daughter and I are both now connected (I use WPA-TKI
and she uses WPA2-AES). No other solutions listed in other posts helpe
but this worked for us. I realize Microsoft is able to point the finge
and say it is not VISTA - but the conflict occurs because of VISTA
Unfortunately, it seems that VISTA creates different conflicts fo
different routers, drivers, laptop manufacturers and the conflict is no
universal. However, it does not negate the fact that the conflict doe
not occur in non-VISTA systems - XP and Macs connected to my networ
with no problems

--
byates3789