Home › Forum › WTOS/ThinOS › 802.1X authentication failed after ugrade to ThinOS 2303 (9.4.1141)
- This topic has 7 replies, 3 voices, and was last updated 2 months, 1 week ago by
vinz.
-
AuthorPosts
-
April 12, 2023 at 5:44 am #108166
Hi,
Since upgrading to ThinOS 2303 (9.4.1141), users can’t connect to our Wifi network with 802.1x authentication.
The events log says :
WLAN : EAP PEAP selected
WLAN : Disconnected with bssid=xx:xx:xx:xx:xx:xx reason=7
WLAN : Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID=”my_domain” freq=5180 MHz)
WLAN : Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID=”my_domain” freq=2437 MHz)
WLAN : Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID=”my_domain” freq=2412 MHz)
EAP : authentication failed
WLAN : Disconnected with bssid=xx:xx:xx:xx:xx:xx reason=1
Then user is prompted for a user/password/domain
Sometimes the reason also =23
Our WMS conf (sorry, in French !)
That conf works perfectly with all my mobile Thin Client (Wyse 5470 and Latitude 3420) but stop working when they are upgraded to ThinOS 2303
I downgraded a 5470 to ThinOS 2211, and it’s working again !
Anyone with the same issue ? Any idea why this ?
Thank you
April 12, 2023 at 8:10 am #108169For information, according to the Deauthentication Reason Code Table :
Reason 1 = “unspecified reason”
Reason 7 = “Class 3 frame received from nonassociated STA”
Reason 23 = “IEEE 802.1X authentication failed”
July 7, 2023 at 4:57 am #108230Hello!
Issue still there with ThinOS 2306, so my mobile devices will have to stay with ThinOS 2211…
Nobody’s got this authentication problem ?
July 11, 2023 at 8:25 pm #108326Have you opened support ticket? if so, I can help escalate it.
July 13, 2023 at 8:45 am #108339Hi !
No I didn’t open a ticket yet. I was waiting for testing the latest ThinOS.
But I think I will do it soon, as I still can’t make it working again.
July 17, 2023 at 10:17 am #108343OK I didn’t know but I can’t open a ticket regarding software issue, as I don’t have a pro licence, just a standard (on premise).
I will try on the DELL Community webpage instead…
July 17, 2023 at 10:17 pm #108344The device you are using, say 5070 or 3000 TC, does it have a valid warranty? If so, use that service tag.
July 26, 2023 at 8:59 am #108357Hi,
Finally my problem is solved, thanks to zzomp from the DELL Community.
The authentication failed because of my NPS server which is still under Windows Server 2012R2, that uses TLS 1.0 and 1.1 but not 1.2
The ThinOS 2303+ documentation reveals that point :
To further improve the security of ThinOS devices, TLS 1.0 and 1.1 have been removed in ThinOS 2303. If your network or
VDI environments still require TLS 1.0 or 1.1, use ThinOS 2211 or earlier versions until you have updated your environment.So I had to activate TLS 1.2 by simply adding a registry key to the NPS server :
https://community.spiceworks.com/topic/2195158-enable-tls1-2-in-windows-server-nps
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\PPP\EAP\13]
“TlsVersion”=dword:00000c00Then restart the EAP service, and that’s it ! authentication passed !
-
AuthorPosts
- You must be logged in to reply to this topic.