Using network captures from Wireshark and Tcpdump.After providing a brief overview of how RADIUS authentication works, I'm going to detail the following strategies: This post will detail a few strategies for troubleshooting RADIUS integrations with Horizon. This can cause things to get dicey in the context of a RADIUS integration, particularly because VDI admins don't necessarily have access to the RADIUS server or its logs. Sometimes all that's received from the RADIUS server is a terse Access-Reject packet, with no specifics on why the rejection occurred. When a Horizon Connection server, acting as a RADIUS client, has a RADIUS request rejected it's not necessarily entitled to any explanation from the RADIUS server why the request was rejected. Making matters worse, while further info can be gleaned from the debug logs on your Horizon server, there are still blind spots from the perspective of a VDI admin.
But for someone in the midst of troubleshooting an integration it's vague and can lead to confusion. For day to day usage with a RADIUS solution that's validated and working, this message is specific enough to get by.
0 kommentar(er)
