cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3164
Views
4
Helpful
6
Replies

Windows 10 and ISE 2.1.0.474

__Beth__
Beginner
Beginner

Hello,

I was wondering if anyone has seen issues with Windows 10 and ISE 2.1.0.474.  We just upgraded ISE Tuesday night and are starting to roll out Windows 10 and am finding those devices cannot connect to wireless.  The error is:

12309 PEAP handshake failed

I found an article that indicates Windows 10 and an older version of ISE had issues:

https://support.microsoft.com/en-us/kb/3121002

If any more information is needed, please let me know. 

Any comments or advice would be appreciated. 

Thanks,

Beth

1 Accepted Solution

Accepted Solutions

hslai
Cisco Employee
Cisco Employee

Please engage TAC on this. Why would Windows 10 attempt SSL3_GET_CLIENT_HELLO? Is registry modified on the Windows 10 to enforce older SSL/TLS protocols? Is this not Windows 10 version 1511?

Note that our product and support teams do not support any pre-release or insider builds but I am not aware of any issue in PEAP auth with ISE 2.1.

View solution in original post

6 Replies 6

__Beth__
Beginner
Beginner

More info:

OpenSSLErrorMessage  SSL alert: code=0x228=552 ; source=local ; type=fatal ; message="handshake failure" 

OpenSSLErrorStack  139992965986048:error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher:s3_srvr.c:1443:

hslai
Cisco Employee
Cisco Employee

Please engage TAC on this. Why would Windows 10 attempt SSL3_GET_CLIENT_HELLO? Is registry modified on the Windows 10 to enforce older SSL/TLS protocols? Is this not Windows 10 version 1511?

Note that our product and support teams do not support any pre-release or insider builds but I am not aware of any issue in PEAP auth with ISE 2.1.

Thank you.  It is build 1511.  I have opened a ticket with TAC.  I will try to update this with the solution. 

__Beth__
Beginner
Beginner

It looks like the patch for this problem regressed in 2.1.  The engineer I am working with is contacting the developers.  In the meantime, this link provides a work around.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuw88770

Thanks for the link and workaround.

Is there any update on your TAC or has this issue been solved by a new release?

We had so many issues with this release, we ended up rolling back.  I need to revisit this at some point...

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers