Again, try WPA as opposed to WPA2.
GrahameP wrote:
> Hi,
>
> More info: -
>
> Using WEP128 each end & DHCP - all connects OK
>
> Using WPA2 Personal - AES on router, WPA2 Personal
on SB2 & DHCP -
> connects to network but gets a 169. address (should
be 192.168.) and
> fails to connect to slimserver.
>
> Using WPA2 Personal - AES on router, WPA2 Personal
on SB2 & fixed
> (192.168.) address - connects to network and fails
to connect to
> slimserver.
>
> Using WPA2 Personal - TKIP+AES on router, WPA2
Personal on SB2 & fixed
> (192.168.) address - fails to connect to network.
>
> Hope this is useful.
>
> Cheers,
> Grahame.
>
>
> GrahameP Wrote:
>
>>I tried both TKIP and AES, but got the same response
from the SB2 with
>>both of them. I am using a mainly Windows network
(XP SP2,
>>PocketPC2003 & 2003 SBS), so the authentication
solution needs to work
>>in this environment (the server is not on the
wireless side of the
>>network, so I suppose it doesn't count).
>>
>>Cheers,
>>Grahame.
>
>
>
--
___________________________________
Mark Lanctot
___________________________________
__________________________________________________________
Find your next car at http://autos.yahoo.ca
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
