Hi  @Tiagofalcao 

If the SSID can't be connected, it's not a portal issue, we need to troubleshoot this first:

1. Verify Network Settings

• Ensure that the DHCP server is running and providing IP addresses to the devices.

• Check if the DNS settings are correctly configured. Incorrect DNS settings can prevent devices from accessing the captive portal.

2. Check for Network Connectivity

• Ensure that the EAP is connected to the PoE switch correctly and that there are no issues with the network cables.

• Verify that the switch is providing power and data to the EAP.

3. Test with Other Devices

• Try connecting with a different mobile device to see if the issue is specific to the Samsung A52 or if it’s a general problem.

• If other devices can connect and access the captive portal, the issue might be with the Samsung A52’s Wi-Fi settings or firmware.

4. Check for Firmware Updates

• Ensure that your Omada OC200 and EAP units are running the latest firmware. Sometimes, firmware updates can resolve connectivity issues.

• You can check for updates in the Omada Controller interface.

5. Reset Network Settings on the Device

• On the Samsung A52, go to Settings > Network & Internet > Wi-Fi > Advanced > Reset Wi-Fi settings. This can sometimes resolve connectivity issues.

6. Check for Interference

• Ensure that there are no other Wi-Fi networks or devices interfering with your network.

• Try changing the Wi-Fi channel to a less congested one.

How to optimize wireless performance of EAP products