I can confirm that I am having the same issues. I work for the ITI Data
Networks group here at Purdue University. We too use 802.1x/RADIUS
authentication utilizing PEAP/MSCHAP. I have tried setting up Vista just
like I would in XP.

Wireless Profile:
Connection
Connect Automatically when this network is in range (checked)
Connect even if the network is not broadcasting (checked)
Security
Security Type: WPA-Enterprise
Encryption Type: TKIP
Network Authentication Method: Protected EAP (PEAP)
Settings
Validate Server Certificate (checked)
Trusted Root Certification Authorities: Thawte Premium
Server CA
Authentication Method: Secured Password (EAP-MSCHAP v2)
Configure
Automatically use my windows login name and password
(UNCHECKED)
Enable Fast Reconnect (checked)
Cache user information for subsequent connections (checked)

The result is that you receive a bubble asking for "Addition information is
required to connect to PAL2.0"
Clicking it prompts you for your credentials. I enter the username and
password and click OK. Within 30 seconds "Addition information is required
to connect to PAL2.0" bubble appears again. This loop will continue to
happen. Enter in a username and password, wait, bubble back again, repeat.

Is this a known problem with Vista?

--Peter


"Techster" wrote in message
news
Our school is using a similar network with radius/802.1x credential based
authentication that only requires a username and password. I followed the
instructions and have zipped the entire folder and made them available at
http://www.utdallas.edu/~jmg019010/wireless_trace.zip. I ran similar
commands on a successful XP client that is almost exactly the same and
made
it available at http://www.utdallas.edu/~jmg019010/XP_trace.zip. Today
was
my first attempt at this, and i will be taking the system home to try on
my
home network to make sure it can connect to open, wep, wpa networks as
well.

I look forward to future updates,
Jeff Gibson

"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" wrote in message
...
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" wrote in message
...
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?

***The trace is located on a webserver due MS article size permissions***

I am attaching the 802.1x trace that I did during the authentication
attempts.
This was done by running "netsh wlan set tra yes" before I entered my
credentials and then "netsh wlan set tra no" after performing several
iterations of entering my credentials.

See referenced text file
10-2-2006wirelesstrace.txt (98K)
http://web.ics.purdue.edu/~psloan/wi...elesstrace.txt



Thanks

"Petely (Peter Sloan)" wrote in message
...
I can confirm that I am having the same issues. I work for the ITI Data
Networks group here at Purdue University. We too use 802.1x/RADIUS
authentication utilizing PEAP/MSCHAP. I have tried setting up Vista just
like I would in XP.

Wireless Profile:
Connection
Connect Automatically when this network is in range (checked)
Connect even if the network is not broadcasting (checked)
Security
Security Type: WPA-Enterprise
Encryption Type: TKIP
Network Authentication Method: Protected EAP (PEAP)
Settings
Validate Server Certificate (checked)
Trusted Root Certification Authorities: Thawte Premium
Server CA
Authentication Method: Secured Password (EAP-MSCHAP v2)
Configure
Automatically use my windows login name and
password
(UNCHECKED)
Enable Fast Reconnect (checked)
Cache user information for subsequent connections (checked)

The result is that you receive a bubble asking for "Addition information
is
required to connect to PAL2.0"
Clicking it prompts you for your credentials. I enter the username and
password and click OK. Within 30 seconds "Addition information is
required
to connect to PAL2.0" bubble appears again. This loop will continue to
happen. Enter in a username and password, wait, bubble back again,
repeat.

Is this a known problem with Vista?

--Peter


"Techster" wrote in message
news
Our school is using a similar network with radius/802.1x credential based
authentication that only requires a username and password. I followed
the
instructions and have zipped the entire folder and made them available at
http://www.utdallas.edu/~jmg019010/wireless_trace.zip. I ran similar
commands on a successful XP client that is almost exactly the same and
made
it available at http://www.utdallas.edu/~jmg019010/XP_trace.zip. Today
was
my first attempt at this, and i will be taking the system home to try on
my
home network to make sure it can connect to open, wep, wpa networks as
well.

I look forward to future updates,
Jeff Gibson

"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" wrote in message
...
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" wrote in message
...
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?

Several persons reported a similar problem here. Here in Portugal, colleges
have a joint 802.1x/WEP network called "e-U", which allows students from one
college to use wireless network at any other college. Worked fine in Windows
XP SP2, but doesn't work with the same exact settings in Vista RC1. It just
keeps trying to authenticate and asking for credentials. I've talked to
admins, and they don't have a clue of what's going on.
I hope someone at Microsoft will talk about what changed in 802.1x
implementation so we can unravel what's happening.

Best regards.

"Petely (Peter Sloan)" wrote:

***The trace is located on a webserver due MS article size permissions***

I am attaching the 802.1x trace that I did during the authentication
attempts.
This was done by running "netsh wlan set tra yes" before I entered my
credentials and then "netsh wlan set tra no" after performing several
iterations of entering my credentials.

See referenced text file
10-2-2006wirelesstrace.txt (98K)
http://web.ics.purdue.edu/~psloan/wi...elesstrace.txt



Thanks

"Petely (Peter Sloan)" wrote in message
...
I can confirm that I am having the same issues. I work for the ITI Data
Networks group here at Purdue University. We too use 802.1x/RADIUS
authentication utilizing PEAP/MSCHAP. I have tried setting up Vista just
like I would in XP.

Wireless Profile:
Connection
Connect Automatically when this network is in range (checked)
Connect even if the network is not broadcasting (checked)
Security
Security Type: WPA-Enterprise
Encryption Type: TKIP
Network Authentication Method: Protected EAP (PEAP)
Settings
Validate Server Certificate (checked)
Trusted Root Certification Authorities: Thawte Premium
Server CA
Authentication Method: Secured Password (EAP-MSCHAP v2)
Configure
Automatically use my windows login name and
password
(UNCHECKED)
Enable Fast Reconnect (checked)
Cache user information for subsequent connections (checked)

The result is that you receive a bubble asking for "Addition information
is
required to connect to PAL2.0"
Clicking it prompts you for your credentials. I enter the username and
password and click OK. Within 30 seconds "Addition information is
required
to connect to PAL2.0" bubble appears again. This loop will continue to
happen. Enter in a username and password, wait, bubble back again,
repeat.

Is this a known problem with Vista?

--Peter


"Techster" wrote in message
news
Our school is using a similar network with radius/802.1x credential based
authentication that only requires a username and password. I followed
the
instructions and have zipped the entire folder and made them available at
http://www.utdallas.edu/~jmg019010/wireless_trace.zip. I ran similar
commands on a successful XP client that is almost exactly the same and
made
it available at http://www.utdallas.edu/~jmg019010/XP_trace.zip. Today
was
my first attempt at this, and i will be taking the system home to try on
my
home network to make sure it can connect to open, wep, wpa networks as
well.

I look forward to future updates,
Jeff Gibson

"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" wrote in message
...
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" wrote in message
...
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?