This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
Just replaced EAP660HD APs on our Branch agains EAP670.
With the 660 WPA Enterprise was working fine - with the EAP670 a connection can not be established.
Multiple VLANs are used for the SSIDs, all other without WPA Enterprise Authentication are working fine.
Hello @MEINL,
Could you provide more details info containing your Network Layout, SSID-related settings?
What is the firmware version of your controller?
May I know the specific behavior of those clients who try to connect to the WPA Enterprise SSID? Can they get a valid IP address?
Hello @Hank21 ,
thanks for your reply
we have 5 ssids which send the clients to 4 vlans, (vlan ids simplified below)
management network of controller and accesspoints is on vlan 1
ssid1 WPA2-PSK/WPA3-SAE / AES - vlan 2 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid2 "guest network" with no security - vlan 3 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid3 "guest network" with hidden ssid with no security - vlan 4 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid4 hidden test network WPA2-PSK/WPA3-SAE / AES - vlan 2 - all working perfect, client are sent to correct vlan and get ip via dhcp from firewall
ssid5 WPA3-Enterprise / AES - vlan 5 - radius (windows nps) log shows same result as connecting to a eap660hd, eap225, but with eap670 and eap650outdoor - the client gets no ip from our windows dhcp server, the client connected to the "old" ap's work fine as always - after roaming from an old to a eap670 the clients remain the dhcp ip and work as well - so the associated vlan should be also correct
controller firmware is 5.9.31 (virtual on ubuntu - vmware)
ap firmwares
EAP660 HD(EU) v1.0 1.1.1
EAP610-Outdoor(EU) v1.0 1.1.3
EAP225-Outdoor(EU) v1.0 5.1.0
EAP650-Outdoor(EU) v1.0 1.0.2
EAP670(EU) v1.0 1.0.6
Hello @MEINL，
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230711117, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
Helpful: 0
Views: 402
Replies: 3
No one has voted for it yet.
We use cookies and browser activity to improve your experience, personalize content and ads, and analyze how our sites are used. For more details, please read our Privacy Policy.
