The underlying issue seems to stem from changes that Microsoft made in the way Windows server 2025 responds to UDP based network protocols. such as Radius/NPS, and DHCP. The Chromebooks on chrome OS v138 are not tolerant of the changes that are creating variable response times that are now in Windows server 2025. We had to downgrade the Chromebook radius authentication process used for the wifi connection to a Windows 2019 Radius/NPS server to get the chromebooks back to reliably connecting to wifi.
We tried multiple network card setting changes on the Window 2025 NPS server, and changed to a different model network card. None of the changes that we tried on the Windows 2025 server, resolved the issue for the Chromebooks. The Windows laptops are working fine on the Windows 2025 Radius/NPS server.
We are monitoring Microsoft patches as they come out over the next several months to see if they release a fix for the Windows 2025 server to allow the Chromebooks to work. There is also a possibility that Google adds a fix to the Chrome LTS v144, or v150 as they are release over the next six months.
For now we are running with the Chromebook wifi Radius/NPS authentication process running through a Windows 2019 server.