Wireless Access

Hello every one, 

i am facing issue with Aruba WC 7030, where mobiles are able to connect but Windows 10 not(Cant connect to this network), it has 2 SSID's: 

first SSID has password is fine but the issue is with the second SSID which requred auth over RADIUS. 

my question is :

how can i trace the issue, or if there is any way to let the controller not ask for certification during the Auth?

thanks 

Did you check the radius server log to see why it was rejected?

yes, its a bit weird, when connect from mobile it accept, but when try to connect from Window 10 it cant connect, here is the log:

Network Policy Server denied access to a user.

Contact the Network Policy Server administrator for more information.

User:
Security ID: HI*****
Account Name: fr*****
Account Domain: HI*****
Fully Qualified Account Name: HI*****

Client Machine:
Security ID: NULL SID
Account Name: -
Fully Qualified Account Name: -
Called Station Identifier: 204C0306A580
Calling Station Identifier: 3CA9F4BD56DC

NAS:
NAS IPv4 Address: 10.16.7.**
NAS IPv6 Address: -
NAS Identifier: 10.16.7.**
NAS Port-Type: Wireless - IEEE 802.11
NAS Port: 0

RADIUS Client:
Client Friendly Name: RCS-Aruba-Master-Controller
Client IP Address: 10.16.7.**

Authentication Details:
Connection Request Policy Name: RCS Secure Wireless Connections
Network Policy Name: RCS Secure Wireless Connections
Authentication Provider: Windows
Authentication Server: *****ics.net
Authentication Type: PEAP
EAP Type: -
Account Session Identifier: -
Logging Results: Accounting information was written to the local log file.
Reason Code: 16
Reason: Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.

Does your Windows computer already have the server certificate or the CA that issued the certificate in the trust list?

Also, Windows does not guess correctly when you just click on an SSID.  In most cases,  have to  setup the SSID manually.  Typical domain computers are setup via group policy to avoid this.

Mobile clients will properly guess the EAP type and ask you for what is needed or just ask you to accept.  Windows doesn't....