I am the administrator of approximately 50 mac systems that connect to a wireless network and authenticate via TLS using certificates generated by a radius server. Everything worked without issue on Mavericks, however I had a few users upgrade to Yosemite without my knowledge, resulting in those users not being able to connect to that network. Out of four Cisco AP's, two of them will allow Yosemite users to connect, with the other two allowing users to connect to the network but not to the internet. Information from network preferences shows that the users are connected using a self assigned IP outside of our address range, or with no IP at all. When I manually set all of the parameters (IP, DNS info etc) the systems will still not connect. Last week, (out of nowhere) one of the two AP's began rejecting Yosemite users, now leaving me with one AP out of four that will allow connections from Yosemite systems. I was originally under the impression that this issue was the result of mDNSResponder being replaced in Yosemite, however, now these users are all on 10.4/5 and experiencing the same problem. I have a test system with a fresh installation that will connect and authenticate without issue, and I have had a users' system connect and work since upgrading to 10.4 (however they can no longer connect since the last round of AP rejections)
Would anyone be able to shed some light on what the issue may be? I have been trying to figure this out for months and I am all out of ideas.
Would anyone be able to shed some light on what the issue may be? I have been trying to figure this out for months and I am all out of ideas.