Every now and then some users will not receive the correct dhcp address when connecting to a wpa2 enterprise ssid. This ssid is bridged with another vlan for physical ports under end users desks. DHCP is handed out by the fortigate, so no relay server. Users will have a dhcp lease assigned in the fortigate but when checking WiFi clients it shows them with a 169.254 ip address and doesn’t allow them to connect via WiFi. Logs show discover and offer but no ack. The next day these users will be able to connect just fine but then this problem randomly happens again. Not sure what would be causing this issue. Any suggestions would be greatly appreciated. Thank you!
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.
As first troubleshooting step, when a host is in this situation, you may check on the WLC if the host has been placed in the right VLAN.
You may also try to set a static IP to that client and ping its default gateway to make sure it is (or is not) in the right VLAN.
Hi,
you can troubleshoot by following this article: https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-DHCP-relay-issue/ta-p/215535
Regards
Rajan
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 |
---|---|
1669 | |
1082 | |
752 | |
446 | |
225 |
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.