Check the AP output power is 100% or not. We suggest the AP power is
50% or less than 50%, it is because the client’s output power is less than
AP, so it will caused the AP can be sent the packet for client but the
packet cannot be reached by AP.
Check the security mode of configuration which was setup with TKIP or
AES.
Check the AP which has setup the RSSI threshold or not. If the client
reaches the RSSI threshold, the client can’t connect the AP
successfully.
2 Environment Verification
Make sure the wireless site survey performance is exceptionally.
Check the client which was connected with far AP or near one. If the
station is a laptop, use the CMD command “netsh wlan show interface”
to check the laptop which connects with nearby client AP or not.
Client can ping to the gateway, Internet or not? Using the CMD
command “ping” and ping to the Gateway and Internet on the same
time to verify the high latency which was bottleneck on Internet or AP.
Check the client which was connected with far AP or near one. Using
the CMD command “tracert” to show you the path your traffic takes
when you are attempting to connect to another machine.
Check the distance of AP which the transmit AP to the receive station.
Check the security of APs’ configuration. The security mode is setup
with TKIP mode, and it will cause the client cannot reach 802.11n type.
3 Information collection and report the issue to the HQ.
Collect the basic information on AP.
Capture the Ethernet packets between DHCP server and AP, if the
client cannot get IP address.
Collect the AP and NXC controller log via diagnostics.
Provide the station devices detail information.
6 Captive Portal
The process of captive portal redirect on controller
1. User tries to access Internet and open browser.
2. Captive Portal intercepts and sends Login Page.
3. Username / Password entered are sent to authentication server.
To Next Page
Loading...
