Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals
Key Takeaways
- Wireless problems often involve RF conditions, authentication, roaming, DHCP, DNS, or captive portal behavior.
- Interference and channel overlap reduce usable airtime even when signal bars appear acceptable.
- RSSI describes received signal strength, while SNR compares signal to background noise.
- Roaming problems can come from poor AP placement, sticky clients, mismatched SSID settings, or weak fast-roaming support.
- Wrong security settings and captive portal failures can allow association but block network access.
Wireless Troubleshooting
Wireless adds a shared radio environment to normal network troubleshooting. A client may associate to an access point but still fail DHCP. It may authenticate but be placed into the wrong VLAN. It may have strong RSSI but poor throughput because noise, channel overlap, or congestion consumes airtime.
RF and Channel Issues
| Issue | Symptom | Troubleshooting direction |
|---|---|---|
| Interference | Retries, drops, low throughput, unstable voice/video | Identify non-Wi-Fi and Wi-Fi sources, check spectrum and airtime |
| Channel overlap | Nearby APs contend or interfere | Plan non-overlapping channels and power levels |
| Co-channel contention | Many APs or clients share one channel | Reduce channel reuse pressure and tune power/channel width |
| Excessive channel width | Higher throughput in theory, more interference in practice | Use width appropriate for density and band |
| Poor AP placement | Dead zones, sticky roaming, uneven load | Survey coverage and adjust placement or power |
In 2.4 GHz, there are fewer non-overlapping channels, so channel planning is especially important. The 5 GHz and 6 GHz bands provide more channel options, but client support, regulatory rules, and deployment density still matter.
RSSI and SNR
RSSI is received signal strength. SNR is signal-to-noise ratio. Strong signal is not enough if the noise floor is also high. A client beside a microwave, industrial device, or crowded RF area may show an acceptable signal level while real throughput suffers because frames must be retransmitted.
| Metric | What it tells you |
|---|---|
| RSSI | How strongly the client hears the AP |
| Noise floor | Background RF energy |
| SNR | How clearly the signal stands above noise |
| Retries | How often frames must be sent again |
| Airtime utilization | How busy the channel is |
For voice and video, jitter and packet loss may be more noticeable than raw throughput. Stable RF and low retries matter.
Roaming Problems
Roaming is client-driven in many deployments. The network can assist with standards and tuning, but the client decides when to move. A sticky client may remain connected to a distant AP even when a closer AP is available.
| Roaming clue | Likely cause |
|---|---|
| Calls drop while walking | Coverage gap, roaming delay, or weak fast-roaming support |
| Client stays on distant AP | Sticky client, AP power too high, or poor placement |
| Device roams but loses access | VLAN, security, or policy mismatch between APs |
| Only one device type has trouble | Client driver, band support, or roaming behavior |
Wrong Security and Captive Portals
Wireless security settings must match. WPA2-Personal, WPA3-Personal, WPA2/WPA3-Enterprise, 802.1X method, certificate trust, username format, and RADIUS reachability all matter. A client may see the SSID but fail to authenticate because it does not support the configured mode or does not trust the certificate chain.
Captive portals add another layer. A guest may associate and receive an IP address but fail Internet access until the portal opens and authorization completes. Portal problems can involve DNS interception, HTTPS behavior, expired certificates, blocked portal addresses, browser privacy features, or a controller outage.
| Symptom | Likely direction |
|---|---|
| Cannot join SSID | Security mode, password, certificate, RADIUS, or client support |
| Joins but no IP address | DHCP scope, relay, VLAN, or controller tunnel |
| Gets IP but no Internet on guest Wi-Fi | Captive portal, DNS, firewall, NAT, or policy |
| Works near one AP but not another | VLAN, trunk, AP config, channel, or power difference |
Exam Focus
For N10-009, wireless troubleshooting is not only "move closer." Use the clue. Interference, channel overlap, and low SNR are RF issues. Wrong security points to authentication and encryption settings. Roaming points to coverage, power, AP settings, or client behavior. Captive portal issues often appear after association and IP addressing succeed.
A wireless client shows strong signal strength but has poor throughput and many retransmissions. A spectrum check shows a high noise floor. Which metric best explains the issue?
Guest users connect to the SSID and receive IP addresses but cannot browse the Internet until a login page appears. What feature is most likely involved?
Match each wireless clue to the likely troubleshooting area.
Match each item on the left with the correct item on the right