Many users are familiar with the situation where a smartphone or laptop finds your home network but displays the status "Saved" or "Connected, no internet access" instead of full internet access. This message means that the device successfully saved the security settings (password, encryption type), but was unable to complete the connection to the router. Most often, the problem lies not in hardware failure, but in a software conflict with IP addresses or a DHCP protocol failure.
Unlike a complete loss of signal, here the radio module works properly. Data exchange protocol is blocked at the address acquisition stage. In the operating system Android it looks like an endless "Obtaining IP address" which then changes to "Saved" status. In the environment Windows A yellow triangle may be illuminated. Understanding what exactly is interrupting the handshake between the gadget and the router allows you to solve 90% of such problems in a couple of minutes.
There are many factors that can affect this process, from a full router memory to an incorrectly set time on your phone. In this guide, we'll walk you through step-by-step procedures to help restore your connection. Don't rush to take your device to a service center—most likely, all that's needed is a proper reconfiguration of your network settings.
DHCP failure and IP address conflicts
The most common reason for the "Saved" status to appear is the device's inability to obtain a dynamic IP address from the router. Protocol DHCP (Dynamic Host Configuration Protocol) is responsible for automatically distributing addresses to all connected devices. If the router's DHCP server is frozen or the address pool is exhausted, your device will be unable to identify itself on the network, and the connection will remain in the configuration saving phase.
Sometimes static address conflicts occur. If you or someone in your household previously assigned a hardcoded IP address to your phone in the router settings and then changed the router hardware or address range, this will cause desynchronization. Router simply rejects the connection request because the addressing doesn't match the current network rules. In this case, automatic address acquisition (DHCP) is the only correct solution.
To resolve the issue, you need to force a reset of the network settings on the client device. This will force the smartphone or laptop to re-query the address from the router, ignoring old, possibly erroneous, cached data. Often, even simply switching to airplane mode, which restarts the operating system's network stack, helps.
If automatic configuration doesn't help, you can try entering the address manually, but this requires understanding your subnet structure. Typically, the gateway (router) has an address of 192.168.0.1 or 192.168.1.1. When entering a static IP, make sure it's in the same range as, but not the same as, the gateway address.
Problems with encryption type and password
The "Saved" status often masks an authentication error. If the security type has been changed in the router settings (for example, from WPA2 on WPA3 If the phone still has old data (or mixed mode), the device will attempt to connect with invalid handshake parameters. As a result, the router sees the login attempt but rejects it due to an encryption protocol mismatch.
This is especially common during router firmware updates, when old security standards are forcibly disabled for increased protection. Your device "remembers" the network, but the access keys or encryption algorithm no longer work. The system believes the network is saved because the SSID (name) matches, but no actual connection is established.
- 🔐 Forget the network in the Wi-Fi settings and reconnect by entering the password manually.
- 📡 Check if filtering by is enabled MAC addresses in the router settings.
- ⚙️ Make sure your router doesn't have a limit on the number of devices that can be connected.
It's also worth paying attention to special characters in your password. Some older devices or specific firmware may incorrectly process complex passwords with emoji, spaces, or rare international characters. If your password was recently changed, try simplifying it to only Latin letters and numbers to eliminate the risk of human error.
☑️ Password and encryption diagnostics
Date and time settings
Few people realize that an incorrect date and time on a device can block a Wi-Fi connection. Security protocols such as WPA2-Enterprise Or even regular home networks with up-to-date certificates, they check timestamps. If the time on your phone deviates significantly from the actual time (for example, it shows 2020), the security certificates are considered invalid.
In this case, the router or ISP's security system blocks the connection, considering it potentially dangerous. The device, however, simply reports the status "Saved" to the user, without going into the technical details of the certificate error. This is a common issue with devices that have been left without a battery for a long time or have been reset to factory settings without being connected to the network.
To fix this, simply go to your date and time settings and enable automatic synchronization via the internet (using a 4G/5G mobile network). Once the time is synchronized with the server, security protocols will begin to function correctly, and the "Saved" status will change to "Connected."
Why is time so important for Wi-Fi?
Encryption protocols use timestamps to prevent replay attacks on old data packets. If the timestamp is incorrect, the security cannot guarantee the integrity of the connection, and access is blocked at the driver level.
Router and provider malfunctions
Don't rule out problems with your provider's equipment or the router itself. If the router is overloaded with tasks (for example, actively downloading torrents or updating the system), it may stop responding to new connection requests. In the router logs, this may appear as if the settings are being saved successfully, but no actual data is being transferred.
It's also possible that the ISP is performing maintenance or there's a line outage. In this case, the router is working and Wi-Fi is available, but there's no access to the global network. Some operating systems, seeing the internet connection down, may mark the network as "Saved" or "Limited" to prevent the user from accessing it.
Checking the status of the WAN port on your router (usually the indicator with a globe or the letter "W" is lit or flashing) can help quickly diagnose the problem. If the indicator is off or red/orange, the problem is definitely not with your phone, but with the incoming signal.
| Indicator | Meaning | Action |
|---|---|---|
| Power | Meals included | If it doesn't light up, check the cable. |
| WAN / Internet | Contacting your provider | If there is a blinking/no signal, call your provider. |
| Wi-Fi / WLAN | Wireless module operation | Should blink when data is being transmitted. |
| LAN (1-4) | Cable connection | Lights up if the PC is connected via cable. |
Frequency and channel conflicts (2.4 GHz and 5 GHz)
Modern routers often operate in two ranges: 2.4 GHz And 5 GHzIf these networks are grouped under a single name in the router settings (using the Smart Connect or Band Steering feature), the device may "jump" between them. Sometimes the phone will try to connect to the 5 GHz band, but the signal is too weak due to walls, and the connection is lost, remaining in the "Saved" status.
Furthermore, the 2.4 GHz band often experiences high levels of noise from neighboring routers, microwave ovens, and Bluetooth headsets. If the channel your network is on is heavily loaded, data packets are lost, and a full connection cannot be established. The router may be working properly, but the radio spectrum is clogged.
It's recommended to separate the networks by giving them different names (for example, Home_2.4 and Home_5) and try connecting to each separately. This will help you determine which band is causing the problem. For devices located far from the router, the 2.4 GHz band is usually more stable, despite the slower speed.
Resetting the device's network settings
If none of the previous methods help, there's a radical but effective option: a complete reset of the device's network settings. This will delete all saved Wi-Fi passwords, Bluetooth pairing settings, and mobile network (APN) settings. However, it's guaranteed to clear any software errors that have accumulated in the network module.
On Android This function is located in the System or General Settings -> Reset -> Reset Network Settings section. iPhone The path looks like this: "General" -> "Move or reset iPhone" -> "Reset" -> "Reset network settings." After the reboot, the device will be cleared in terms of network connections.
⚠️ Attention: After resetting your network settings, you'll need to re-enter passwords for all Wi-Fi networks and re-pair your Bluetooth headphones or watch. Make sure you remember your home network password.
This method is especially useful when the problem is intermittent: Wi-Fi works one day, but not the next, and reboots don't help. A reset returns drivers and configuration files to their factory defaults, eliminating the influence of third-party apps or system glitches.
Frequently Asked Questions (FAQ)
Why does it say "Saved" if the password is definitely correct?
The "Saved" status means the device has remembered the network but is unable to authenticate or obtain an IP address. Even with the correct password, this could be due to router settings (MAC filtering, client limitation) or a DHCP protocol failure.
Will deleting the Wi-Fi app help?
On Android, deleting updates or data from the Wi-Fi system app (via app settings) may help if the problem is with the system module itself. However, a full network settings reset (as described above) is a more reliable and secure method.
Can antivirus block the connection?
Yes, some aggressive firewall settings in antivirus or VPN applications can block the connection. Try temporarily disabling your VPN or antivirus and checking the connection status.
What if the status is "Saved" only on one device?
If other devices work fine, the problem is localized to a specific device. It likely lacks access rights (MAC filtering) or has corrupted network settings. Perform a network reset on that specific device.