locked
Windows 10 Mobile 1607 and WPA2 Enterprise RRS feed

  • Question

  • Hi,

    since the Upgrade to Windows 10 Mobile 1607 it is no longer possible to connect to the WPA2-Enterpise Network at my University.

    After entering my account data, the Phone shows the general "could not connect" Message.

    The Connection is working fine on a PC with Win 10 1607 and on the Phone with Win 10 1511 or lower.

    The WLAN Profile is imported via Provisioning Package created by ICD with the WiFi Profile exported from Windows 10 1607 Desktop.

    The Provisioning Package is working fine on PC.

    The Network uses WPA2-Enterprise TTLS with FreeRadius 2.1.12, we also tested with FreeRadius 3.0.10.

    I would be grateful for any tips to identify the problem.

    Thanks

    Friday, September 9, 2016 2:30 PM

Answers

  • Hi,

    I have tested the connection with latest Insider Build (10.0.14977.1000) it is working fine, again.

    Note:

    You have to install a provisioning package defining the WiFi settings and you have to use the NEW WIFI settings.

    • Marked as answer by tichachm Monday, January 9, 2017 8:56 AM
    Monday, January 9, 2017 8:56 AM
  • Hi,

    you can try this:

    1. Setup the network on a PC

    2. Export the network settings als XML with: netsh wlan export profile %SSIDName% folder=c:\

    3. Now use Imaging And Configuration Designer (Part of ADK) to create the Provisionig Package.

    4. Under Runtime-Settings -> ConnectivityProfiles -> Profiles you can add the XML-File from above.

    5. After creating the package, copy it on to the device over USB and approve the installation on the device.

    6. Connect to the network and enter your login data

    Please note:

    You have to use Windows 10 Mobile Version 1511 to use this. It is not working with Version 1607!

    Thanks


    • Marked as answer by tichachm Thursday, April 13, 2017 6:05 PM
    • Edited by tichachm Wednesday, April 19, 2017 6:59 AM
    Thursday, April 13, 2017 6:05 PM

All replies

  • Hi,

    Did you fix your problem? I have the same issue with my new Lumia 950. It was working fine with my Lumia 640.

    Thank you

    Patrick

    Wednesday, November 30, 2016 4:35 PM
  • No news, I think nobody interested in this issue.

    I hope it will work with the next release again. (it is NOT working with the latest Insider Build but they are updating the WiFi Settings)

    The only thing you can do right now, is to go back to Version 1511.

    You can also upvote this:

    https://social.technet.microsoft.com/Forums/windows/en-US/d9e49e03-1e19-475b-8402-95aadf51182a/8021x-eapttlspap-universitywifi-eduroam-not-working-anymore-since-last-windows-10-for-mobile?forum=win10itpromobile#64d0828d-2fcd-4bb2-9a55-d3cf5e75e9d3

    and

    http://aka.ms/Vpp5uw

    Wednesday, November 30, 2016 6:42 PM
  • Hi,

    I have tested the connection with latest Insider Build (10.0.14977.1000) it is working fine, again.

    Note:

    You have to install a provisioning package defining the WiFi settings and you have to use the NEW WIFI settings.

    • Marked as answer by tichachm Monday, January 9, 2017 8:56 AM
    Monday, January 9, 2017 8:56 AM
  • How do you create a provision package with WPA2-Enterprise settings? I have attempted to follow the directions on TechNet for creating provision packages with WCD, however the Windows Configuration Designer only allows for WPA2 Personal.

    I am trying to get an HP Elite x3 with the latest build of Windows 10 Mobile to connect to a WPA2 Enterprise network with PEAP and MSCHAPv2.  On laptops and other devices we have to tweak some settings to get it working, but I can't find any way to configure these settings on the phone.  Any suggestions would be appreciated.

    Thursday, April 13, 2017 5:12 PM
  • Hi,

    you can try this:

    1. Setup the network on a PC

    2. Export the network settings als XML with: netsh wlan export profile %SSIDName% folder=c:\

    3. Now use Imaging And Configuration Designer (Part of ADK) to create the Provisionig Package.

    4. Under Runtime-Settings -> ConnectivityProfiles -> Profiles you can add the XML-File from above.

    5. After creating the package, copy it on to the device over USB and approve the installation on the device.

    6. Connect to the network and enter your login data

    Please note:

    You have to use Windows 10 Mobile Version 1511 to use this. It is not working with Version 1607!

    Thanks


    • Marked as answer by tichachm Thursday, April 13, 2017 6:05 PM
    • Edited by tichachm Wednesday, April 19, 2017 6:59 AM
    Thursday, April 13, 2017 6:05 PM
  • Thank you.  We're currently on 1607 (of course).  I'll try this out as soon as I can, though.  It's one of the few leads I've gotten so far.
    Tuesday, April 18, 2017 2:20 PM
  • I found a machine with 1511 on it.  I was able to export the profile and create a provisioning package as per your instructions.  I'm just now waiting to get a hold of the phone and try it out.  I'll post here when I do.  Thanks again, it was very informative regardless.
    Tuesday, April 18, 2017 5:47 PM
  • Hello Spekk10,

    just to clarify, you need to have Windows 10 Mobile 1511 on the Phone. The PC you build the provisioning package can run any version.

    I am currently testing the final version of Windows 10 Mobile 1703, there seems to be an bug, too. I will post an update if I have more information.

    -------Update:

    It is not working with 1703 at the moment!

    • Edited by tichachm Monday, April 24, 2017 9:02 AM
    Wednesday, April 19, 2017 6:59 AM
  • Hello Tichachm,

    I can confirm, Windows Phone 10 1703 update (Lumia 650) doesn't work as well. Previous old Lumia 630 on latest Windows 8.1 worked well even on automatic settings, not specifying exactly WPA2.

    Looks only the only option is waiting for the next update which is quite frustrating :(

    Friday, May 12, 2017 10:30 AM
  • Hi DualitySoul,

    yes I also found a (the same) problem on Win 10 1703 on PC.

    You can vote here, if you have this issue, too: https://aka.ms/J4bt3d

    I will report as soon as there is a Update/Fix.

    Thanks

    Monday, May 15, 2017 7:09 AM