The WiFi password is correct, but why can’t the camera connect?
The reason was to help my cousin with home decoration and monitoring. There are four cameras, and the instructions say to scan the QR code to configure the network, and the first three cameras are all stuck spinning in circles at the last step. She copied the WiFi password on paper and handed it to me. I checked it letter by letter, and it was correct. The fourth one plugs in the network cable and it's done once. This is strange: If the password is the same and the network cable is working but the WiFi is not, then the problem is probably not the password. That afternoon I passed through the six in my own order and rescued them all. Write down the sequence in this article. Next time you encounter "the password is obviously correct, but the device just can't be connected", follow the steps.
First, distinguish between the two types of "failure to connect". The directions of investigation are completely different.
Before taking action, check where the device is stuck. The first type: Your name cannot be found in the WiFi list at all . There is no such item in the list at all, and it has nothing to do with the password. It is a matter of signal or hiding the SSID. Check whether the router broadcasts the name and how many walls there are. Check these two things first. The second type is the home field of this article: Searched, clicked in, entered password, circled, failed . Reaching the step of entering the password means that there is no problem with the signal and name. The problem is the "association" layer - the router rejected the device at the last moment, or the device itself gave up halfway.
The three units at my cousin's house are all of the second type. The error report in the camera app is also very misleading. It only shows "Connection failed, please check password" but does not tell you the real reason. I will record the processing of the three channels in the following sections. I will first explain how to eliminate the six sources in the fastest order.
The first suspect: The device only recognizes 2.4G, you connected it to 5G
This is the one with the highest hit rate among the six, accounting for half of my own failure records. Many cameras, sweepers, old TV boxes, smart sockets, and wireless modules only use the 2.4G band to save money. When you search for WiFi on your mobile phone, you can see both frequency bands, but not on the device side - it doesn't even have the name 5G in its eyes.
The trouble lies in the "dual frequency integration". Now the router combines 2.4G and 5G into one WiFi name by default, and the mobile phone automatically selects the frequency band when connected, which is very smart. However, some network distribution processes will package the 5G information currently connected to the mobile phone and send it to the camera. The camera will use this information to shout on 2.4G. The call cannot be made, will circle, time out, and report "wrong password". This is the place where my cousin lives.: Her mobile phone is connected to 5G, and the first three cameras are all stuck. ; I switched my phone to 2.4G and matched the name, and the first one was connected on the spot. How to dismantle dual-band, and what to do after disassembly, I am here The article about dual frequency in one The complete operation is written here. The complete trampling of the sweeper, in The sweeper only recognizes 2.4G Here, the mechanism is exactly the same.
quick judgment method: In the list of networks that the device can search, if there are two names (one with the 5G suffix and one without), your device will most likely only be able to connect to the one without it. If there is only one name in the list, first use your mobile phone to connect to 2.4G and then go through the network distribution process to try it out, which will take two minutes.
Second suspect: The encryption method is wrong, and the old device does not recognize WPA3
The second camera at my cousin's house is stuck on this. Hers is an old model from 2018. The router is a WiFi6 machine that I replaced for her the year before last. The encryption is WPA3-SAE by default. The new phone connects very quickly, but the old camera gets blurry as soon as I use it.: If the handshake agreement does not match, it will be rejected directly. The behavior is exactly the same as a wrong password - spinning in circles, failure, "please check password".
Verification is quick: The router changes the encryption to WPA2/WPA3 mixed mode in the background (some firmwares call it "transition mode"), saves it, and the device tries again. That's it. Which device from a year ago is easy to be infected? Which menu in the backend of which company has the hybrid mode? I am in WPA3 old equipment cannot connect to that article There is a list here, just follow it and look for it. By the way, don’t drop your whole family’s encryption back to WPA2 single mode just because it’s an old device. That’s what mixed mode is for, and the old and new go their separate ways.
The third suspect: The "input layer" pitfall of the password itself
Channel 3 is the most annoying. After checking for a long time, I found that there was a capital letter in the password. The camera's network configuration interface uses a mobile phone app to pass the password. However, my cousin's old man's phone was manually connected once before, and the input method could not cut off the capital letters, so the input was all lowercase. This kind of mistake is the hardest to catch, because "looking at the password on the paper" is always correct, and the wrong one is the one you type into the device.
I have stepped on the pitfalls of the input layer several times, and I can summarize them into three points:: One is Special characters in password , I can’t find that symbol in the input method of old devices and remote controls. This pitfall and countermeasures are in The special character password article As written in, the conclusion is don’t use it. 12-digit pure alphanumeric characters are more practical than fancy symbols. ; The second is Chinese name , the WiFi name contains Chinese characters, and the wireless modules of some devices cannot be parsed. The search list directly displays garbled characters or simply cannot be found. The actual measurement records of the five types of devices are in The Chinese name of WiFi inside ; The third is If you enter incorrectly too many times, you will be temporarily locked by the router. , some firmwares will block the same device for several minutes if it fails to authenticate continuously. At this time, even if the password is changed correctly, the connection cannot be made. You have to wait. The mechanism is in Wrong entry locks the article It has been dismantled. The investigation method is very crude: Change the phone and manually connect to the same WiFi once. If it can be connected, it means that there is no problem with the password itself. The problem lies in the input on the other side of the device.
The fourth suspect: The whitelist is on and new devices will be blocked.
If the device is tampering with someone else's network, or if your own router has "Only allow whitelisted devices to connect", then the new device will not be able to get in even if you enter the correct password - it is not on the list at all. This kind of rejection is the most unfair, because the router will not give you any prompts, and the device will only show that the connection failed.
I've stepped on it since I was a kid: He tried to be safe and opened a whitelist. Later, he bought a new TV, but couldn't connect to it and almost returned it. The way to determine is to go into the backend of the router and look for menus such as "Wireless Access Control" and "MAC Filtering" to see if the mode is "Whitelist/Only allow devices in the list". If yes, add the MAC of the new device to the list, or temporarily turn off this function and try to connect again. In Tenda's interface, the whitelist and blacklist are hidden closely and are easy to reverse. It is a complete trap. Tenda whitelist article inside. Using a whitelist to prevent network fraud is the right idea, but the price is that every new device must be manually released. If you have many smart devices at home, it will be more worry-free to use "new device connection notification". Here is how to do it The anti-robbing website article inside.
The fifth suspect: The number of devices has reached its maximum
There is an upper limit on the number of routers you can carry, and the actual upper limit is much lower than the number printed on the packaging. A machine with a nominal number of 128 may start to have problems when it reaches sixty or seventy.: The old device is disconnected and the association of the new device is rejected. The performance is still "the password is correct but cannot be connected" because the router has no number to send and can only reject you at the association layer.
The characteristic of this source is that "more than one device cannot be connected" - the newly purchased camera, the guest's mobile phone, and the new tablet all cannot be connected one after another, but all the old equipment at home are normal. Go into the backend and count the number of currently online devices. If there are more than 50 or 60 devices, you should be suspicious. Which devices occupy accounts, how to lose weight, and the true scale of the upper limit, I am here The article about measuring with a machine Tested in practice. Another reminder: The optical modem layer also has its own limit on the number of devices. If the optical modem WiFi is exposed, you have to check the optical modem. The solution is The article about limiting the number of devices in optical modem Here, the three levels range from free to root-free.
The sixth suspect: The signal is so weak that the handshake cannot be completed
The last one is the easiest to mix with others. When the signal is too weak, the device can search for the name and initiate a connection, but the handshake data packets are lost halfway, and after several rounds of back and forth, the data cannot be collected, and finally it times out and fails. The error message on the device side is still "Please check password" - it doesn't know it's a signal.
Determine the signal strength: Stand the mobile phone at the same location as the device and look at the signal grid number or dBm number in the WiFi details. A dBm of more than 60 dBm is considered healthy, and a dBm below 75 dBm should be used with caution. The solution is to move the equipment or the router. If you cannot believe the scale, use dBm to judge. The scale is in The article about devices with weak signals slowing down the entire network mentioned in. By the way, a related pitfall: A device with a weak signal will not only be unable to connect by itself, but even if it barely connects, it will also slow down the whole family's WiFi because it will occupy the air interface for a longer period of time. This account is also mentioned in the same article. Also pay attention to the protocol compatibility of old equipment: When a WiFi6 router encounters a very old WiFi4 device, some firmware just can’t get along with it. For that one, use the “WiFi5 compatibility mode” to help. The article about old devices not being able to connect to WiFi6 inside.
List of six origins and my investigation sequence
That day at my cousin's house, my actual order of checking was the table below, from the ones with the highest hit rate to the lowest. Each step could be completed in two or three minutes.:
| order | origin | Two-minute test | Corresponding solution |
|---|---|---|---|
| 1 | Only recognizes 2.4G | Connect the mobile phone to 2.4G first and then configure the network | Remove the dual-band or change the mobile phone distribution network |
| 2 | Encryption incompatible | Cut WPA2/WPA3 mix and try again | Mixed mode long term retention |
| 3 | Error in input layer | Change the mobile phone and lose once | Password changed to 12 digits purely alphanumeric |
| 4 | Whitelist blocking | Check wireless access control mode in the background | Add MAC or change notification mode |
| 5 | The machine is full | Count online devices | Clear idle or separate IoT networks |
| 6 | signal too weak | See dBm at the same position | Move equipment or router |
Give it a try: Of these six sources, one and two can cover 70 to 80% of the cases I handle. So if you encounter "the password is correct but cannot connect", first spend two minutes each to check 2.4G and encryption, and most of the time it will be solved on the spot. The remaining four are long tail, and it is not difficult to follow the table. Finally tell the truth: Don't really believe it when the device reports "Incorrect password". That prompt is a snake oil. It doesn't know why it can't connect. The password is the only word it can say.
