What should I do if the Guest WiFi connection fails on Reyee AP ?

You can do troubleshooting for Guest WiFi connection fails on Reyee AP as follows:

1. Cannot find Guest WiFi

You can check whether enable Hide SSID function



2. The Guest WiFi can be searched but can not be connected

1）Ensure that the wireless network name you are trying to connect to is the same as the Guest WiFi set on the AP

2）Check whether the strength of the wireless signal is sufficient. If the signal is weak (for example, less than two bars of signal), it is recommended to adjust the AP position or try a close connection

3) Check whether the Guest WiFi is encrypted. If a password is set, check whether the password is consistent with the encryption setting of the Guest WiFi

4)Switch to another terminal test or create a Guest WiFi test

5)After trying the above methods, if the connection still fails, please restore the AP to factory Settings and reset the Guest WiFi（After the system is restored to factory defaults, all configurations are lost, and will lose the wireless network, so please do it when network is free and you are beside the devices.）

3. The terminal can not obtain the address

1)Check the AP network



2）The terminal is configured with a static IP to check whether the channel with the DHCP server is working. If not, check the configurations (VLAN, port security, and MAC address filtering) and MAC address entries of the intermediate device

3) If the IP address can not be obtained, check whether DHCP snooping is enabled on the intermediate device. If yes, check whether trusted interfaces are configured

4) Check whether the address pool of the DHCP server is exhausted

5)If the ACL is invoked on the gateway interface, you need to check that an entry is added at the end to allow all passes

6)Check the DHCP process of the CPU. If the number of ARP packets is too high, check whether the logs contain a large number of ARP packets. You can enable anti-attack measures.

4. Unable to access the Internet after obtaining the address

1)Check whether the terminal can communicate with the DNS address. If not, tracert checks the destination hop

2)If the device is stuck to the egress device, check whether the egress device can access the Internet and whether NAT is enabled on the egress device. You can view the NAT flow table to check whether address translation is generated in the data and check the NAT policy

3)Check whether the Internet access blacklist and behavior policy are configured on the uplink device

4)Check whether policy-based routing is configured on the device to forward Intranet data to the interface that can not access the Internet

5)If DNS addresses are communicating properly and the domain name can not be accessed, check the DNS configuration or check whether the DNS port on the uplink device is blocked (53)