This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Wifi Enterprise (EAP/PEAP) not working with Android 13

ck-r over 1 year ago

Hello,

we use Wifi Enterprise with Security type EAP/PEAP.

The configuration is working in the past but now the Wifi not connect after the enrollment of the device.

This error only occurs on Android 13 devices for about 3 weeks.

Has anything changed there?

Here is my configuration:

SSID = [SSID Wifi]

Security type = EAP/PEAP

Phase 2 authorization = MSCHAPv2

Identity = [user whos known on the RADIUS-Server]

Anonymous identity = %_USERNAME_%

Password = [Password from the Identity User]

Identity certificate = None

Trusted certificate = [Root certificate]

I can't see any Information for a connection request on the RADIUS-Server, when the Device is rolled out.

> The phone doesn't even try to connect with the Wifi.

Can anyone help me here?

This thread was automatically locked due to age.

Top Replies

Gladys over 1 year ago in reply to ck-r +1

Hi ck-r , Thanks for getting back to me. It does appear to be the same issue. Our Development Team is currently looking into this. I will follow up on this thread as soon as we have an update.

Parents

0 Gladys over 1 year ago

Hi ck-r ,

Thank you for reaching out to the Sophos Community Forum.

This might be related to the issue previously raised to our Development Team, wherein customers can't set up Wi-Fi configurations for new Android 13 phones with the latest Android patch installed.

Can you please check and let me know if it works when you manually enter the configuration?

Gladys Reyes

Global Community Support Engineer
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the "Verify Answer" button.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 ck-r over 1 year ago in reply to Gladys

Hi,

Thank you for your answer.

I've tried to add the Wi-Fi configuration manually. It works.

Before that, I had to install the Root-CA certificate to use for Wi-Fi manually in Android.

After I entered all the other settings manually, the connection was established.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 ck-r over 1 year ago in reply to Gladys

Hi,

Thank you for your answer.

I've tried to add the Wi-Fi configuration manually. It works.

Before that, I had to install the Root-CA certificate to use for Wi-Fi manually in Android.

After I entered all the other settings manually, the connection was established.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Gladys over 1 year ago in reply to ck-r

Hi ck-r ,

Thanks for getting back to me. It does appear to be the same issue. Our Development Team is currently looking into this. I will follow up on this thread as soon as we have an update.

Gladys Reyes

Global Community Support Engineer
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the "Verify Answer" button.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up +1 Vote Down

Cancel
0 Jan-Philipp Lechner over 1 year ago in reply to Gladys

Hi Gladys ,

is there an update?

The Oktober 1st, 2023 Update is installed, but the Problem is still.
Cancel
Vote Up 0 Vote Down

Cancel
0 Qoosh over 1 year ago in reply to Jan-Philipp Lechner

This issue is resolved in version 9.7.102XXX and later of the SMC app. Allow me some time to inquire internally about the expected release date for this version and I will update you here.

Update: The new SMC client will roll out to customers on Monday, November 6th.

Kushal Lakhan

Team Lead, Global Community Support
Connect with Sophos Support, get alerted, and be informed.
If a post solves your question, please use the "Verify Answer" button.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 Jan-Philipp Lechner over 1 year ago in reply to Qoosh

Hi,

now we have the Version 9.7.10218, but the problem still exists.

We do have TLS, but it should be the same?
Cancel
Vote Up 0 Vote Down

Cancel
0 Qoosh over 1 year ago in reply to Jan-Philipp Lechner

If you are continuing to experience this issue, I'd suggest opening a support case with our team from the Sophos Support Portal.

You can also get immediate assistance by calling your regional support phone number listed on the following page.
- Contact us

Kushal Lakhan

Team Lead, Global Community Support
Connect with Sophos Support, get alerted, and be informed.
If a post solves your question, please use the "Verify Answer" button.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 ck-r over 1 year ago in reply to Jan-Philipp Lechner

Hi,

the problem still exists in our company with Version 9.7.10218, too.
Cancel
Vote Up 0 Vote Down

Cancel
+1 Jan-Philipp Lechner 11 months ago in reply to ck-r

Hi ck-r ,

it was the combination of the version 9.7.10218 and the domain suffix match of the certificate, by us.

We have TLS, but the android requirements are changed. At least I found something there. https://www.androidenterprise.community/t5/community-feedback/recent-android-change-regarding-wifi-configuration/td-p/359

Sophos support also pointed out the domain suffix name again. https://doc.sophos.com/central/Mobile/help/en-us/AdminHelp/Policies/AndroidEnterpriseDevice/WiFi/index.html

We had to fill the domain suffix match in the SCEP- and Wifi-Profile and with the version 9.7.10218 works all again.
Cancel
Vote Up +1 Vote Down

Cancel
0 ck-r 11 months ago in reply to Jan-Philipp Lechner

Hi,

thanks for your answer.

It works too after insert the Domain suffix match.
Cancel
Vote Up 0 Vote Down

Cancel