authentication using 802.1x but the device cannot authenticate and there is nothing visible in the eventlogs on the NPS server. MTU on Forti devices is 1500.
we have a similar configuration between forti F100 in the headquarters and forti F100 in DataCenter and here the replacement or switching to the second radius works correctly, plus we have all the logs.
we performed the test by uploading our Forti F40 to the local network together with the switches and the authentication was successful, so we assume that it is a problem with the tunnel or settings on the Fortigat
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Must be the source IP or NAS IP mismatching with what the Win NPS RADIUS proxy is expecting or you configured to expect. For NAS IP (doesn't have to be routable), you must be specifying it already. But for source IP, if you don't have a routable IP set on the tunnel interface, in which case it would pick either the lowest or highest (I just don't remember which) available IP on the FGT, you need to set a routable IP in the RADIUS config so that the server can reply back.
config user radius
edit "radius_name"
set nas-ip x.x.x.x
set source-ip y.y.y.y
next
end
Toshi
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.