Vista - Still can't connect to WPA Enterprise

The problem that stopped me using Beta 2, is still there with RC1 for me.

Trying to connect to WPA Enterprise, TKIP PEAP with certificate validation
off, and just using a username/password combination, no domain name. This
worked fine in XP.

I get asked for my username and password, provide the ones which have worked
for a long time in XP, and after 10-20 seconds I just get a baloon I saying I
need to provide additional credentials. I put them in again, and after a
similar length of time I am told I can not connect.

Anyone have this problem or any ideas on a solution?

You're not alone.

Same setup, same problem. No idea how to solve this tough. Somehow my radius
server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed to it.

"Costanza" wrote:

> The problem that stopped me using Beta 2, is still there with RC1 for me.
>
> Trying to connect to WPA Enterprise, TKIP PEAP with certificate validation
> off, and just using a username/password combination, no domain name. This
> worked fine in XP.
>
> I get asked for my username and password, provide the ones which have worked
> for a long time in XP, and after 10-20 seconds I just get a baloon I saying I
> need to provide additional credentials. I put them in again, and after a
> similar length of time I am told I can not connect.
>
> Anyone have this problem or any ideas on a solution?

I thought it would be something like that. I just don't really want to annoy
our sys admins about it too much as it is my personal laptop I have decided
to run Vista on, trying to connect to work wireless network.

"drahnier" wrote:

> You're not alone.
>
> Same setup, same problem. No idea how to solve this tough. Somehow my radius
> server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed to it.
>
> "Costanza" wrote:
>
> > The problem that stopped me using Beta 2, is still there with RC1 for me.
> >
> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate validation
> > off, and just using a username/password combination, no domain name. This
> > worked fine in XP.
> >
> > I get asked for my username and password, provide the ones which have worked
> > for a long time in XP, and after 10-20 seconds I just get a baloon I saying I
> > need to provide additional credentials. I put them in again, and after a
> > similar length of time I am told I can not connect.
> >
> > Anyone have this problem or any ideas on a solution?

Are you on a domain or workgroup? Are you using certificate based
authentication?

Assuming that you are connecting to a network that requires a certificate,
you are probably hitting the following:

In vista the default authentication was changed from certificate based auth
to PEAP/MSCHAPv2. This means when using discovery to connect to a network
for which requires an EAP type, this is the new default. To connect to a
network which uses another eap type you need to create a wireless profile
for that network in advance. This can be done through group policy or by
creating a profile from the "Get connected Wizard."

To do this, just click "set up a connection or network" on the "connect to a
network" page (then chose "Manually connect to a wireless network"). After
typing the SSID (case sensitive) and setting the initial security settings,
click next. The next page will have a button which says "Change connection
settings." Click it. Here you can change the auth type back to "Smart card
or other certificate" on the "security" tab. Set any other relavent settings
while here. After pressing OK, you should be connected to your network
(assuming that automatic connections were allowed earlier in the process).

The design of the wireless "discovery" (using the UI) phase is not
necessarily designed to connect to networks which require management and
there are a range of options to create/distribute wireless profiles in
advance from netsh scripting to group policy.

Creating a wireless profile (steps above) is the more powerful method of
connecting to any type of network manually.

--
J.P.
_____________________________________
This posting is provided "AS IS" with
no warranties, and confers no rights.


"Costanza" <Costanza@discussions.microsoft.com> wrote in message
news:807F895E-6D07-419C-A990-B6F416F774C4@microsoft.com...
>I thought it would be something like that. I just don't really want to
>annoy
> our sys admins about it too much as it is my personal laptop I have
> decided
> to run Vista on, trying to connect to work wireless network.
>
> "drahnier" wrote:
>
>> You're not alone.
>>
>> Same setup, same problem. No idea how to solve this tough. Somehow my
>> radius
>> server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed to
>> it.
>>
>> "Costanza" wrote:
>>
>> > The problem that stopped me using Beta 2, is still there with RC1 for
>> > me.
>> >
>> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate
>> > validation
>> > off, and just using a username/password combination, no domain name.
>> > This
>> > worked fine in XP.
>> >
>> > I get asked for my username and password, provide the ones which have
>> > worked
>> > for a long time in XP, and after 10-20 seconds I just get a baloon I
>> > saying I
>> > need to provide additional credentials. I put them in again, and after
>> > a
>> > similar length of time I am told I can not connect.
>> >
>> > Anyone have this problem or any ideas on a solution?

I the same problem, manualy configuration is correctly but after try connect
to wireless network - Vista not asked userneme and password.

In XP this working correctly and after 10-20 seconds I just get a baloon I
saying I need to provide additional credentials.

Ladislav

"J.P. Stewart [MSFT]" wrote:

> Are you on a domain or workgroup? Are you using certificate based
> authentication?
>
> Assuming that you are connecting to a network that requires a certificate,
> you are probably hitting the following:
>
> In vista the default authentication was changed from certificate based auth
> to PEAP/MSCHAPv2. This means when using discovery to connect to a network
> for which requires an EAP type, this is the new default. To connect to a
> network which uses another eap type you need to create a wireless profile
> for that network in advance. This can be done through group policy or by
> creating a profile from the "Get connected Wizard."
>
> To do this, just click "set up a connection or network" on the "connect to a
> network" page (then chose "Manually connect to a wireless network"). After
> typing the SSID (case sensitive) and setting the initial security settings,
> click next. The next page will have a button which says "Change connection
> settings." Click it. Here you can change the auth type back to "Smart card
> or other certificate" on the "security" tab. Set any other relavent settings
> while here. After pressing OK, you should be connected to your network
> (assuming that automatic connections were allowed earlier in the process).
>
> The design of the wireless "discovery" (using the UI) phase is not
> necessarily designed to connect to networks which require management and
> there are a range of options to create/distribute wireless profiles in
> advance from netsh scripting to group policy.
>
> Creating a wireless profile (steps above) is the more powerful method of
> connecting to any type of network manually.
>
> --
> J.P.
> _____________________________________
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
>
> "Costanza" <Costanza@discussions.microsoft.com> wrote in message
> news:807F895E-6D07-419C-A990-B6F416F774C4@microsoft.com...
> >I thought it would be something like that. I just don't really want to
> >annoy
> > our sys admins about it too much as it is my personal laptop I have
> > decided
> > to run Vista on, trying to connect to work wireless network.
> >
> > "drahnier" wrote:
> >
> >> You're not alone.
> >>
> >> Same setup, same problem. No idea how to solve this tough. Somehow my
> >> radius
> >> server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed to
> >> it.
> >>
> >> "Costanza" wrote:
> >>
> >> > The problem that stopped me using Beta 2, is still there with RC1 for
> >> > me.
> >> >
> >> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate
> >> > validation
> >> > off, and just using a username/password combination, no domain name.
> >> > This
> >> > worked fine in XP.
> >> >
> >> > I get asked for my username and password, provide the ones which have
> >> > worked
> >> > for a long time in XP, and after 10-20 seconds I just get a baloon I
> >> > saying I
> >> > need to provide additional credentials. I put them in again, and after
> >> > a
> >> > similar length of time I am told I can not connect.
> >> >
> >> > Anyone have this problem or any ideas on a solution?
>
>

Also note that in vista to get a balloon for entering credentials, you must
uncheck the box which says "Use my windows credentials" in the MSCHAPv2
advanced settings. OR just use discovery to connect to a 1x/WPA network
while logged on as a non-domain user. Either of these methods will cause a
balloon to appear to enter alternate credentials.

If you are still seeing a failure, the following steps will log what is
going wrong:

1. Launch an elevated command prompt
2. netsh wlan set tra yes
3. Reproduce the problem
4. netsh wlan set tra no (make sure this is still in an elevated command
prompt, and wait for the command to complete)
5. Tracing results will be in %windir%\tracing\wireless (try report.html or
just attach a zip file of the dir)

--
J.P.
_____________________________________
This posting is provided "AS IS" with
no warranties, and confers no rights.


"Ladislav" <Ladislav@discussions.microsoft.com> wrote in message
news:9DBA4107-F720-4195-8E38-E7DB86B50068@microsoft.com...
>I the same problem, manualy configuration is correctly but after try
>connect
> to wireless network - Vista not asked userneme and password.
>
> In XP this working correctly and after 10-20 seconds I just get a baloon I
> saying I need to provide additional credentials.
>
> Ladislav
>
> "J.P. Stewart [MSFT]" wrote:
>
>> Are you on a domain or workgroup? Are you using certificate based
>> authentication?
>>
>> Assuming that you are connecting to a network that requires a
>> certificate,
>> you are probably hitting the following:
>>
>> In vista the default authentication was changed from certificate based
>> auth
>> to PEAP/MSCHAPv2. This means when using discovery to connect to a network
>> for which requires an EAP type, this is the new default. To connect to a
>> network which uses another eap type you need to create a wireless profile
>> for that network in advance. This can be done through group policy or by
>> creating a profile from the "Get connected Wizard."
>>
>> To do this, just click "set up a connection or network" on the "connect
>> to a
>> network" page (then chose "Manually connect to a wireless network").
>> After
>> typing the SSID (case sensitive) and setting the initial security
>> settings,
>> click next. The next page will have a button which says "Change
>> connection
>> settings." Click it. Here you can change the auth type back to "Smart
>> card
>> or other certificate" on the "security" tab. Set any other relavent
>> settings
>> while here. After pressing OK, you should be connected to your network
>> (assuming that automatic connections were allowed earlier in the
>> process).
>>
>> The design of the wireless "discovery" (using the UI) phase is not
>> necessarily designed to connect to networks which require management and
>> there are a range of options to create/distribute wireless profiles in
>> advance from netsh scripting to group policy.
>>
>> Creating a wireless profile (steps above) is the more powerful method of
>> connecting to any type of network manually.
>>
>> --
>> J.P.
>> _____________________________________
>> This posting is provided "AS IS" with
>> no warranties, and confers no rights.
>>
>>
>> "Costanza" <Costanza@discussions.microsoft.com> wrote in message
>> news:807F895E-6D07-419C-A990-B6F416F774C4@microsoft.com...
>> >I thought it would be something like that. I just don't really want to
>> >annoy
>> > our sys admins about it too much as it is my personal laptop I have
>> > decided
>> > to run Vista on, trying to connect to work wireless network.
>> >
>> > "drahnier" wrote:
>> >
>> >> You're not alone.
>> >>
>> >> Same setup, same problem. No idea how to solve this tough. Somehow my
>> >> radius
>> >> server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed
>> >> to
>> >> it.
>> >>
>> >> "Costanza" wrote:
>> >>
>> >> > The problem that stopped me using Beta 2, is still there with RC1
>> >> > for
>> >> > me.
>> >> >
>> >> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate
>> >> > validation
>> >> > off, and just using a username/password combination, no domain name.
>> >> > This
>> >> > worked fine in XP.
>> >> >
>> >> > I get asked for my username and password, provide the ones which
>> >> > have
>> >> > worked
>> >> > for a long time in XP, and after 10-20 seconds I just get a baloon I
>> >> > saying I
>> >> > need to provide additional credentials. I put them in again, and
>> >> > after
>> >> > a
>> >> > similar length of time I am told I can not connect.
>> >> >
>> >> > Anyone have this problem or any ideas on a solution?
>>
>>

"J.P. Stewart [MSFT]" wrote:

> Are you on a domain or workgroup? Are you using certificate based
> authentication?
>
> Assuming that you are connecting to a network that requires a certificate,
> you are probably hitting the following:
>
> In vista the default authentication was changed from certificate based auth
> to PEAP/MSCHAPv2. This means when using discovery to connect to a network
> for which requires an EAP type, this is the new default. To connect to a
> network which uses another eap type you need to create a wireless profile
> for that network in advance. This can be done through group policy or by
> creating a profile from the "Get connected Wizard."
>
> To do this, just click "set up a connection or network" on the "connect to a
> network" page (then chose "Manually connect to a wireless network"). After
> typing the SSID (case sensitive) and setting the initial security settings,
> click next. The next page will have a button which says "Change connection
> settings." Click it. Here you can change the auth type back to "Smart card
> or other certificate" on the "security" tab. Set any other relavent settings
> while here. After pressing OK, you should be connected to your network
> (assuming that automatic connections were allowed earlier in the process).
>
> The design of the wireless "discovery" (using the UI) phase is not
> necessarily designed to connect to networks which require management and
> there are a range of options to create/distribute wireless profiles in
> advance from netsh scripting to group policy.
>
> Creating a wireless profile (steps above) is the more powerful method of
> connecting to any type of network manually.
>
> --
> J.P.
> _____________________________________
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
>
> "Costanza" <Costanza@discussions.microsoft.com> wrote in message
> news:807F895E-6D07-419C-A990-B6F416F774C4@microsoft.com...
> >I thought it would be something like that. I just don't really want to
> >annoy
> > our sys admins about it too much as it is my personal laptop I have
> > decided
> > to run Vista on, trying to connect to work wireless network.
> >
> > "drahnier" wrote:
> >
> >> You're not alone.
> >>
> >> Same setup, same problem. No idea how to solve this tough. Somehow my
> >> radius
> >> server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed to
> >> it.
> >>
> >> "Costanza" wrote:
> >>
> >> > The problem that stopped me using Beta 2, is still there with RC1 for
> >> > me.
> >> >
> >> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate
> >> > validation
> >> > off, and just using a username/password combination, no domain name.
> >> > This
> >> > worked fine in XP.
> >> >
> >> > I get asked for my username and password, provide the ones which have
> >> > worked
> >> > for a long time in XP, and after 10-20 seconds I just get a baloon I
> >> > saying I
> >> > need to provide additional credentials. I put them in again, and after
> >> > a
> >> > similar length of time I am told I can not connect.
> >> >
> >> > Anyone have this problem or any ideas on a solution?
>
>

No, that seems to be the opposite of my problem.

I am not on a domain.
I am not using certificate based, and I turned off 'validate certificate'
I also turned off 'use my windows login and password by default'
I am set to use PEAP/MSCHAPv2 and provide the correct credentials when
asked, with no success.

I will attempt to log as per your next response.

"J.P. Stewart [MSFT]" wrote:

> Are you on a domain or workgroup? Are you using certificate based
> authentication?
>
> Assuming that you are connecting to a network that requires a certificate,
> you are probably hitting the following:
>
> In vista the default authentication was changed from certificate based auth
> to PEAP/MSCHAPv2. This means when using discovery to connect to a network
> for which requires an EAP type, this is the new default. To connect to a
> network which uses another eap type you need to create a wireless profile
> for that network in advance. This can be done through group policy or by
> creating a profile from the "Get connected Wizard."
>
> To do this, just click "set up a connection or network" on the "connect to a
> network" page (then chose "Manually connect to a wireless network"). After
> typing the SSID (case sensitive) and setting the initial security settings,
> click next. The next page will have a button which says "Change connection
> settings." Click it. Here you can change the auth type back to "Smart card
> or other certificate" on the "security" tab. Set any other relavent settings
> while here. After pressing OK, you should be connected to your network
> (assuming that automatic connections were allowed earlier in the process).
>
> The design of the wireless "discovery" (using the UI) phase is not
> necessarily designed to connect to networks which require management and
> there are a range of options to create/distribute wireless profiles in
> advance from netsh scripting to group policy.
>
> Creating a wireless profile (steps above) is the more powerful method of
> connecting to any type of network manually.
>
> --
> J.P.
> _____________________________________
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
>
> "Costanza" <Costanza@discussions.microsoft.com> wrote in message
> news:807F895E-6D07-419C-A990-B6F416F774C4@microsoft.com...
> >I thought it would be something like that. I just don't really want to
> >annoy
> > our sys admins about it too much as it is my personal laptop I have
> > decided
> > to run Vista on, trying to connect to work wireless network.
> >
> > "drahnier" wrote:
> >
> >> You're not alone.
> >>
> >> Same setup, same problem. No idea how to solve this tough. Somehow my
> >> radius
> >> server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed to
> >> it.
> >>
> >> "Costanza" wrote:
> >>
> >> > The problem that stopped me using Beta 2, is still there with RC1 for
> >> > me.
> >> >
> >> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate
> >> > validation
> >> > off, and just using a username/password combination, no domain name.
> >> > This
> >> > worked fine in XP.
> >> >
> >> > I get asked for my username and password, provide the ones which have
> >> > worked
> >> > for a long time in XP, and after 10-20 seconds I just get a baloon I
> >> > saying I
> >> > need to provide additional credentials. I put them in again, and after
> >> > a
> >> > similar length of time I am told I can not connect.
> >> >
> >> > Anyone have this problem or any ideas on a solution?
>
>

I try
> 1. Launch an elevated command prompt
> 2. netsh wlan set tra yes
> 3. Reproduce the problem
> 4. netsh wlan set tra no (make sure this is still in an elevated command
> prompt, and wait for the command to complete)
> 5. Tracing results will be in %windir%\tracing\wireless (try report.html or
> just attach a zip file of the dir)

but %windir%\tracing is empty !!

Result - this is bug in RC1 (wireles networking not funct. properly).

Ladislav

"J.P. Stewart [MSFT]" wrote:

> Also note that in vista to get a balloon for entering credentials, you must
> uncheck the box which says "Use my windows credentials" in the MSCHAPv2
> advanced settings. OR just use discovery to connect to a 1x/WPA network
> while logged on as a non-domain user. Either of these methods will cause a
> balloon to appear to enter alternate credentials.
>
> If you are still seeing a failure, the following steps will log what is
> going wrong:
>
> 1. Launch an elevated command prompt
> 2. netsh wlan set tra yes
> 3. Reproduce the problem
> 4. netsh wlan set tra no (make sure this is still in an elevated command
> prompt, and wait for the command to complete)
> 5. Tracing results will be in %windir%\tracing\wireless (try report.html or
> just attach a zip file of the dir)
>
> --
> J.P.
> _____________________________________
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
>
> "Ladislav" <Ladislav@discussions.microsoft.com> wrote in message
> news:9DBA4107-F720-4195-8E38-E7DB86B50068@microsoft.com...
> >I the same problem, manualy configuration is correctly but after try
> >connect
> > to wireless network - Vista not asked userneme and password.
> >
> > In XP this working correctly and after 10-20 seconds I just get a baloon I
> > saying I need to provide additional credentials.
> >
> > Ladislav
> >
> > "J.P. Stewart [MSFT]" wrote:
> >
> >> Are you on a domain or workgroup? Are you using certificate based
> >> authentication?
> >>
> >> Assuming that you are connecting to a network that requires a
> >> certificate,
> >> you are probably hitting the following:
> >>
> >> In vista the default authentication was changed from certificate based
> >> auth
> >> to PEAP/MSCHAPv2. This means when using discovery to connect to a network
> >> for which requires an EAP type, this is the new default. To connect to a
> >> network which uses another eap type you need to create a wireless profile
> >> for that network in advance. This can be done through group policy or by
> >> creating a profile from the "Get connected Wizard."
> >>
> >> To do this, just click "set up a connection or network" on the "connect
> >> to a
> >> network" page (then chose "Manually connect to a wireless network").
> >> After
> >> typing the SSID (case sensitive) and setting the initial security
> >> settings,
> >> click next. The next page will have a button which says "Change
> >> connection
> >> settings." Click it. Here you can change the auth type back to "Smart
> >> card
> >> or other certificate" on the "security" tab. Set any other relavent
> >> settings
> >> while here. After pressing OK, you should be connected to your network
> >> (assuming that automatic connections were allowed earlier in the
> >> process).
> >>
> >> The design of the wireless "discovery" (using the UI) phase is not
> >> necessarily designed to connect to networks which require management and
> >> there are a range of options to create/distribute wireless profiles in
> >> advance from netsh scripting to group policy.
> >>
> >> Creating a wireless profile (steps above) is the more powerful method of
> >> connecting to any type of network manually.
> >>
> >> --
> >> J.P.
> >> _____________________________________
> >> This posting is provided "AS IS" with
> >> no warranties, and confers no rights.
> >>
> >>
> >> "Costanza" <Costanza@discussions.microsoft.com> wrote in message
> >> news:807F895E-6D07-419C-A990-B6F416F774C4@microsoft.com...
> >> >I thought it would be something like that. I just don't really want to
> >> >annoy
> >> > our sys admins about it too much as it is my personal laptop I have
> >> > decided
> >> > to run Vista on, trying to connect to work wireless network.
> >> >
> >> > "drahnier" wrote:
> >> >
> >> >> You're not alone.
> >> >>
> >> >> Same setup, same problem. No idea how to solve this tough. Somehow my
> >> >> radius
> >> >> server (ZyXEL Vantage Radius 50) doesn't seem to like what is passed
> >> >> to
> >> >> it.
> >> >>
> >> >> "Costanza" wrote:
> >> >>
> >> >> > The problem that stopped me using Beta 2, is still there with RC1
> >> >> > for
> >> >> > me.
> >> >> >
> >> >> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate
> >> >> > validation
> >> >> > off, and just using a username/password combination, no domain name.
> >> >> > This
> >> >> > worked fine in XP.
> >> >> >
> >> >> > I get asked for my username and password, provide the ones which
> >> >> > have
> >> >> > worked
> >> >> > for a long time in XP, and after 10-20 seconds I just get a baloon I
> >> >> > saying I
> >> >> > need to provide additional credentials. I put them in again, and
> >> >> > after
> >> >> > a
> >> >> > similar length of time I am told I can not connect.
> >> >> >
> >> >> > Anyone have this problem or any ideas on a solution?
> >>
> >>
>
>

Are there any errors when attempting the instructions below? Are you sure
the command prompt is elevated?

Many others have reported results with these same instructions.

--
J.P.
_____________________________________
This posting is provided "AS IS" with
no warranties, and confers no rights.


"Ladislav" <Ladislav@discussions.microsoft.com> wrote in message
news:C6299035-9B17-4C34-9375-0704126EF8AD@microsoft.com...
>I try
>> 1. Launch an elevated command prompt
>> 2. netsh wlan set tra yes
>> 3. Reproduce the problem
>> 4. netsh wlan set tra no (make sure this is still in an elevated command
>> prompt, and wait for the command to complete)
>> 5. Tracing results will be in %windir%\tracing\wireless (try report.html
>> or
>> just attach a zip file of the dir)
>
> but %windir%\tracing is empty !!
>
> Result - this is bug in RC1 (wireles networking not funct. properly).
>
> Ladislav
>
> "J.P. Stewart [MSFT]" wrote:
>
>> Also note that in vista to get a balloon for entering credentials, you
>> must
>> uncheck the box which says "Use my windows credentials" in the MSCHAPv2
>> advanced settings. OR just use discovery to connect to a 1x/WPA network
>> while logged on as a non-domain user. Either of these methods will cause
>> a
>> balloon to appear to enter alternate credentials.
>>
>> If you are still seeing a failure, the following steps will log what is
>> going wrong:
>>
>> 1. Launch an elevated command prompt
>> 2. netsh wlan set tra yes
>> 3. Reproduce the problem
>> 4. netsh wlan set tra no (make sure this is still in an elevated command
>> prompt, and wait for the command to complete)
>> 5. Tracing results will be in %windir%\tracing\wireless (try report.html
>> or
>> just attach a zip file of the dir)
>>
>> --
>> J.P.
>> _____________________________________
>> This posting is provided "AS IS" with
>> no warranties, and confers no rights.
>>
>>
>> "Ladislav" <Ladislav@discussions.microsoft.com> wrote in message
>> news:9DBA4107-F720-4195-8E38-E7DB86B50068@microsoft.com...
>> >I the same problem, manualy configuration is correctly but after try
>> >connect
>> > to wireless network - Vista not asked userneme and password.
>> >
>> > In XP this working correctly and after 10-20 seconds I just get a
>> > baloon I
>> > saying I need to provide additional credentials.
>> >
>> > Ladislav
>> >
>> > "J.P. Stewart [MSFT]" wrote:
>> >
>> >> Are you on a domain or workgroup? Are you using certificate based
>> >> authentication?
>> >>
>> >> Assuming that you are connecting to a network that requires a
>> >> certificate,
>> >> you are probably hitting the following:
>> >>
>> >> In vista the default authentication was changed from certificate based
>> >> auth
>> >> to PEAP/MSCHAPv2. This means when using discovery to connect to a
>> >> network
>> >> for which requires an EAP type, this is the new default. To connect to
>> >> a
>> >> network which uses another eap type you need to create a wireless
>> >> profile
>> >> for that network in advance. This can be done through group policy or
>> >> by
>> >> creating a profile from the "Get connected Wizard."
>> >>
>> >> To do this, just click "set up a connection or network" on the
>> >> "connect
>> >> to a
>> >> network" page (then chose "Manually connect to a wireless network").
>> >> After
>> >> typing the SSID (case sensitive) and setting the initial security
>> >> settings,
>> >> click next. The next page will have a button which says "Change
>> >> connection
>> >> settings." Click it. Here you can change the auth type back to "Smart
>> >> card
>> >> or other certificate" on the "security" tab. Set any other relavent
>> >> settings
>> >> while here. After pressing OK, you should be connected to your network
>> >> (assuming that automatic connections were allowed earlier in the
>> >> process).
>> >>
>> >> The design of the wireless "discovery" (using the UI) phase is not
>> >> necessarily designed to connect to networks which require management
>> >> and
>> >> there are a range of options to create/distribute wireless profiles in
>> >> advance from netsh scripting to group policy.
>> >>
>> >> Creating a wireless profile (steps above) is the more powerful method
>> >> of
>> >> connecting to any type of network manually.
>> >>
>> >> --
>> >> J.P.
>> >> _____________________________________
>> >> This posting is provided "AS IS" with
>> >> no warranties, and confers no rights.
>> >>
>> >>
>> >> "Costanza" <Costanza@discussions.microsoft.com> wrote in message
>> >> news:807F895E-6D07-419C-A990-B6F416F774C4@microsoft.com...
>> >> >I thought it would be something like that. I just don't really want
>> >> >to
>> >> >annoy
>> >> > our sys admins about it too much as it is my personal laptop I have
>> >> > decided
>> >> > to run Vista on, trying to connect to work wireless network.
>> >> >
>> >> > "drahnier" wrote:
>> >> >
>> >> >> You're not alone.
>> >> >>
>> >> >> Same setup, same problem. No idea how to solve this tough. Somehow
>> >> >> my
>> >> >> radius
>> >> >> server (ZyXEL Vantage Radius 50) doesn't seem to like what is
>> >> >> passed
>> >> >> to
>> >> >> it.
>> >> >>
>> >> >> "Costanza" wrote:
>> >> >>
>> >> >> > The problem that stopped me using Beta 2, is still there with RC1
>> >> >> > for
>> >> >> > me.
>> >> >> >
>> >> >> > Trying to connect to WPA Enterprise, TKIP PEAP with certificate
>> >> >> > validation
>> >> >> > off, and just using a username/password combination, no domain
>> >> >> > name.
>> >> >> > This
>> >> >> > worked fine in XP.
>> >> >> >
>> >> >> > I get asked for my username and password, provide the ones which
>> >> >> > have
>> >> >> > worked
>> >> >> > for a long time in XP, and after 10-20 seconds I just get a
>> >> >> > baloon I
>> >> >> > saying I
>> >> >> > need to provide additional credentials. I put them in again, and
>> >> >> > after
>> >> >> > a
>> >> >> > similar length of time I am told I can not connect.
>> >> >> >
>> >> >> > Anyone have this problem or any ideas on a solution?
>> >>
>> >>
>>
>>