forti tunnel NPS

[mateusz1]

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

[AEK]

• Check just with diag sniffer if FG is exchanging some RADIUS data with the NPS
• You can also use wireshark on NPS side to see if RADIUS queries are arriving from FG and if there is any reply
• You may also check if NPS server's firewall allows RADIUS queries from FG

[hbac]

Hi @mateusz1,

Please refer to the following articles: 

https://community.fortinet.com/t5/FortiGate/Technical-Tip-RADIUS-user-credential-verification-via-GU...

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Radius-authentication-troubleshooting/ta-p...

Regards, 

[Toshi_Esumi]

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