Skip to Content.

cat-users - Re: [[cat-users]] Windows 10 1703

cat-users AT lists.geant.org

Subject: The mailing list for users of the eduroam Configuration Assistant Tool (CAT)

List archive


Re: [[cat-users]] Windows 10 1703


Chronological Thread 
  • From: Tomasz Wolniewicz <twoln AT umk.pl>
  • To: Stefan Winter <stefan.winter AT restena.lu>, Stefano Manfredda <stefano AT unica.it>, cat-users AT lists.geant.org
  • Subject: Re: [[cat-users]] Windows 10 1703
  • Date: Mon, 15 May 2017 23:07:47 +0200

One addition,

the problem seems to be TTLS specific, setting PEAP with an XML
profile works fine.

Tomasz



W dniu 15.05.2017 o 23:00, Tomasz Wolniewicz pisze:
> So,
>
> I have run some more tests and things look really strange.
>
> If I delete the connection properties altogether and manually connect to
> the network, I will be prompted the username/password and then, after I
> confirm I wan to connect, I do get connected.
>
> Having an active connection, using the Network Center, I can enter the
> network properties window and checking security properites on the
> connection I see:
>
> 1. TTLS/PAP is set (this is different from previous default of
> TTLS/MSCHAPv2)
>
> 2. Annonymous id is set to "anonymous" without any realm
>
> 3. No root CA is selected as trusted (this is different from the
> previous behavious, when the CA which issued the certificate of the
> server we connected to was automatically selected).
>
> Now, not having changes anything I click OK and try to connect again.
> This time a differently looking credentials prompt is displayed and the
> connection fails.
>
> If, instead, after the first successful connection I export the profile
> with netsh, I see the the root CA fingerprint *is* set. After
> "forgetting" the network I load the xml profile with netsh, but the
> connection fails. I have tried deleting parts of security settings and
> the anonymous support, but nothing helps.
>
> This really looks completely hopeless.
>
> Tomasz
>
>
>
> W dniu 15.05.2017 o 20:37, Tomasz Wolniewicz pisze:
>> Hello,
>>
>> I am in the process of testing things but it appears that the recent
>> Windows update has completely broken EAP-TTLS. This seem to have nothing
>> to do with CAT, I cannot connect using manual configuration.
>>
>> Your situation seems to be different as in your case Windows does
>> connect when no profile is installed.
>>
>> I will send an update when I know more.
>>
>> Tomasz
>>
>>
>>
>> W dniu 15.05.2017 o 16:26, Stefan Winter pisze:
>>> Hello,
>>>
>>> I have read user reports about Win 10 1703 breakage in relation to Wi-Fi.
>>>
>>> This is sometimes due to a Wi-Fi driver which isn't up-to-date.
>>>
>>> A possible theory is that the updated machine got a fix to the driver
>>> prior to the update - and continues to work after the upgrade - while a
>>> fresh install from (stale) media doesn't have the newest driver yet and
>>> then fails.
>>>
>>> Does that make any sense?
>>>
>>> Stefan
>>>
>>> Am 15.05.2017 um 15:50 schrieb Stefano Manfredda:
>>>> Hello all,
>>>>
>>>> we had problems with Windows 10 1703: it seems that it isn't able to
>>>> connect to eduRoam after a clean installation.
>>>>
>>>> We're testing eduroam installers before deploying them; we
>>>> tested them on Linux, Android, OSX, IOS, Windows 7 (clean install),
>>>> Windows 8.1 (clean install), Windows 10 (Pro) 1511 (clean install),
>>>> Windows 10 (Pro) 10.0 build 10240 (clean install), Windows 10 (Pro)
>>>> 1607 (clean install) and Windows 10 (Pro) 1703 migrated from 1607
>>>> without getting any issue.
>>>>
>>>> Testing eduroam-W10-UdSdC after a Windows 10 1703 clean
>>>> install, we weren't able to connect or better, we haven't been able to
>>>> connect via eduroam-W10-UdSdC: as soon as installation ends, tryig to
>>>> connect gives a "impossible to connect to this network" message; if we
>>>> remove CAT and delete eduroam from known networks list, then Windows
>>>> automatically connects in TTLS/PAP.
>>>> Maybe is a xml-related problem? We can't understand this
>>>> behavior while is quite simple (just do a clean 1703 installation) to
>>>> reproduce it.
>>>>
>>>> Best regards,
>>>>
>> To unsubscribe, send this message:
>> mailto:sympa AT lists.geant.org?subject=unsubscribe%20cat-users
>> Or use the following link:
>> https://lists.geant.org/sympa/sigrequest/cat-users
> To unsubscribe, send this message:
> mailto:sympa AT lists.geant.org?subject=unsubscribe%20cat-users
> Or use the following link:
> https://lists.geant.org/sympa/sigrequest/cat-users




Archive powered by MHonArc 2.6.19.

Top of Page