- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SSID authentication via Radius Server on FortiOS 7.2.10 / FortiGate 80F
Hello all,
is there any Documentation or Best-Practice on how to set-up a Wifi SSID with AD-Authentication via Windows NPS Server from scratch?
At the moment our company uses MAC Filter based via WPA2-Personal, but i want to change it into Authentication through AD via Radius Server. Best would be WPA3 Enterprise i guess. I set up the NPS Server, applied the Network policy and Connection Request Policies, set up the AD groups, added them into the Network policy, created Radius Client on the Forti (and NPS Server ofc), connection between Forti and Radius is successfull and also my user credentials are working, but when i set up the SSID and add it to my Network Interface, the Client says connection is not possible.
I mainly used this technical tip: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Configuring-FortiGate-and-Microsoft-NPS-Ra...
and also this
https://docs.fortinet.com/document/fortiap/7.4.4/fortiwifi-and-fortiap-configuration-guide/961597/co...
But i think in some config im doing somethin wrong.
The Network Interface on my FortiGate 80F is a software switch with IP/Netmask from 192.168.5.254/23 and i want the clients to get an IP from this range. This works perfectly fine with our main Wifi atm.
Has anyone any helpful links or even idea what could possible be wrong?
This i atm mainly a test to see if everything works to rollout via FortiManager afterwards.
thank you in advance :)
- Labels:
-
FortiGate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I suppose you are trying to implement EAP-PEAP. Firstly make sure that the supplicant in the end host is configured correctly. Doing the configuration from Control Panel it will show all the available options, certificates and credentials (this example is for EAP-TLS but the options are similar).
A packet capture of RADIUS traffic while trying to login from the end host will give more details for the request/response, Network> Diagnostics> Filters [Port: 1812].
You can also refer to this article for troubleshooting the authentication part from the FGT side.
If you have found a solution, please like and accept it to make it easily accessible for others.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes EAP-PEAP correct. Okay i will look into it. If i solved the issue or i'll have any problems ill come back. Thank you!
