Wi-Fi takes a long time to connect

Archived from groups: microsoft.public.pocketpc (More info?)

I have a WLan with a shared WEP key. It takes about 45 seconds to connect
my SX66. I had it going faster last week (about 7 seconds), but don't know
what has changed since. I had removed the settings for my network, then
added them again. Prior to that it was very slow to connect. I tried doing
that again, but it makes no difference. Anyone have a suggestion?

I do not have "Automatically connect to non-preferred networks checked".
However, my WLAN is listed (and is the only one) in Settings | Connections |
Network Cards | Configure Wireless Networks.

Thanks,

Bill

Archived from groups: microsoft.public.pocketpc (More info?)

Hi Martin,

I gave it a try- on three other channels, and it takes as long (or in one
case much longer) as before. I'd love to know what's behind this. How long
should it take? (My network uses a shared key- not open and no SSID
broadcast).

Thanks again,

Bill


"Martin" <martin@scotland.org> wrote in message
news:42c903f8$0$2054$ed2e19e4@ptn-nntp-reader04.plus.net...
> Bill wrote:
>> I have a WLan with a shared WEP key. It takes about 45 seconds to
>> connect my SX66. I had it going faster last week (about 7 seconds),
>> but don't know what has changed since. I had removed the settings
>> for my network, then added them again. Prior to that it was very
>> slow to connect. I tried doing that again, but it makes no
>> difference. Anyone have a suggestion?
>> I do not have "Automatically connect to non-preferred networks
>> checked". However, my WLAN is listed (and is the only one) in
>> Settings | Connections | Network Cards | Configure Wireless Networks.
>>
>> Thanks,
>>
>> Bill
>
> Hi Bill,
>
> I had similar symptoms. What cured it for me was moving to a different
> channel on the wireless access point. Worth a try as it's trivial to do,
> and easy to change back!
> Mine had been connecting very quickly, but I can only presume a neighbour
> has set up on the same channel as I was. I changed from channel 11 to 10,
> but someone pointed out that these overlap, so you may want to try 1 or 6.
> In any case channel 10 is working fine for me.
>
> HTH
>
> Martin
>