WPA2-AES, but notification area bubble says "(unsecured)"

I have a wireless network setup using WPA2 with AES. I recently noticed that
the notification area bubble sometimes shows the wireless connection as
"(unsecured)" even though the computer and access points are configured for
WPA2 and AES.

I would like to know if there is a known issue in Windows XP with service
pack 2?

My knowledge base searches haven't found anything yet.

Thank you for your time,

Michel

Michel Thebeau wrote:
> I have a wireless network setup using WPA2 with AES. I recently noticed that
> the notification area bubble sometimes shows the wireless connection as
> "(unsecured)" even though the computer and access points are configured for
> WPA2 and AES.
>
> I would like to know if there is a known issue in Windows XP with service
> pack 2?
>
> My knowledge base searches haven't found anything yet.
>
> Thank you for your time,
>
> Michel
>
I get the same issue. I put my laptop to standby when I'm not using
it, and then wake it up to see it try to acquire. Then I see the
(unsecured) connection. I changed settings once to unsecured and then
back. It wasn't until then that I noticed this. So its kinda like
its finding the router info but the bubble is bringing up the wrong
title from an old history? Got me, but I see it too. And oddly enough
I have WPA2 AES.

Big_Al wrote:
> Michel Thebeau wrote:
>> I have a wireless network setup using WPA2 with AES. I recently
>> noticed that the notification area bubble sometimes shows the wireless
>> connection as "(unsecured)" even though the computer and access points
>> are configured for WPA2 and AES.
>>
>> I would like to know if there is a known issue in Windows XP with
>> service pack 2?
>>
>> My knowledge base searches haven't found anything yet.
>>
>> Thank you for your time,
>>
>> Michel
>>
> I get the same issue. I put my laptop to standby when I'm not using
> it, and then wake it up to see it try to acquire. Then I see the
> (unsecured) connection. I changed settings once to unsecured and then
> back. It wasn't until then that I noticed this. So its kinda like
> its finding the router info but the bubble is bringing up the wrong
> title from an old history? Got me, but I see it too. And oddly enough
> I have WPA2 AES.

Of course, XP2 has known issues - otherwise there won't be SP3.
A wi-fi sniffer can solve these doubts...

--PA

Hi
When this happens check if you are connecting to another Wireless source.
Configuring your Wireless source to WPA-AES and the computer's Wireless as
related to your SSID, does not preclude None Secure connection to other
sources.
Jack (MS, MVP-Networking)

"Michel Thebeau" <Michel (E-Mail Removed)> wrote in message
news:9BCF8F73-6597-4A1A-BC28-(E-Mail Removed)...
>I have a wireless network setup using WPA2 with AES. I recently noticed
>that
> the notification area bubble sometimes shows the wireless connection as
> "(unsecured)" even though the computer and access points are configured
> for
> WPA2 and AES.
>
> I would like to know if there is a known issue in Windows XP with service
> pack 2?
>
> My knowledge base searches haven't found anything yet.
>
> Thank you for your time,
>
> Michel
>

Thank you.

Yeah, we've 15000 laptops to update. It sometimes helps to raise the
priority of getting things upgraded if we can lay a little fire under the
table. I was hoping there was a tech note somewhere that said the
notification area bubble was being silly or that there's actually a flaw.

I do appreciate the info in your replies.

The access points we use detect rogues networks, so I'm confident that there
are no other networks involved...

Cheers,

Michel

> When this happens check if you are connecting to another Wireless source.
> Configuring your Wireless source to WPA-AES and the computer's Wireless as
> related to your SSID, does not preclude None Secure connection to other
> sources.

Thanks Jack,

Could you clarify that statement in context if I said that we use peap and
ms-chap v2 for authentication? I'm not sure what you meant really. Even
with wpa2-psk I would not expect "does not preclude [non-secure] connection
to other sources"

I'm thinking that you might have intended that I should double-check which
SSID I was connected to.

Hi
Your OP does not indicate any thing beyond simple statement about your
Wireless concern.
Assuming that this is a regular End-User situation I meant to check if
indeed the computer is connected to the secure SSID and not to some other
signal that it picks.
Jack (MS, MVP-Networking)

"Michel Thebeau" <(E-Mail Removed)> wrote in message
news:0C2B35A4-6504-462F-89F8-(E-Mail Removed)...
>> When this happens check if you are connecting to another Wireless source.
>> Configuring your Wireless source to WPA-AES and the computer's Wireless
>> as
>> related to your SSID, does not preclude None Secure connection to other
>> sources.
>
> Thanks Jack,
>
> Could you clarify that statement in context if I said that we use peap and
> ms-chap v2 for authentication? I'm not sure what you meant really. Even
> with wpa2-psk I would not expect "does not preclude [non-secure]
> connection
> to other sources"
>
> I'm thinking that you might have intended that I should double-check which
> SSID I was connected to.

Excellent, thanks Jack. Yup, my original post was pretty general without a
lot of details. When I replied I wanted to clarify that you didn't mean that
my computer might successfully connect to the same SSID but from an un-secure
source. Thanks for clarifying.