Why Wi-Fi Doesn't Work on My Phone but Connects on My Computer: A Deep Dive

It's understandable that a laptop or desktop computer maintains a reliable connection, while a smartphone stubbornly displays "Connected, no internet access" or refuses to connect at all. Users immediately blame the phone itself, although in the vast majority of cases, the problem lies in incompatible settings between the router and the mobile network module. Computers, especially those with external adapters, often have more flexible settings and better antennas, allowing them to ignore minor configuration errors that can be fatal for mobile devices.

The main difficulty with diagnostics is that the network is visually visible, the signal may be full, but no data exchange occurs. This indicates that the physical connection layer (radio signal) is working, but the logical layer (encryption protocols, address assignment) is failing. Unlike a PC, where you can easily view event logs or run complex diagnostics via the command line, mobile operating systems Android And iOS hide the details of the connection process from the user, displaying only general error messages.

In this article, we'll take a detailed look at the technical reasons for this behavior, from frequency ranges to MAC address conflicts. You'll learn how to properly configure your router for compatibility with all devices in your home and why resetting your phone's network settings is often more effective than rebooting the router itself. Understanding these processes will help you not only solve the current problem but also optimize your home network for stable smart home and streaming.

Conflict between the 2.4 GHz and 5 GHz frequency bands

The most common reason why a laptop sees the network and works, but a phone doesn't, is the difference in supported frequency bands. Modern routers often operate in two bands: 2.4 GHz And 5 GHzOlder or budget smartphone models may only support the 2.4 GHz band. If the router is configured to operate exclusively in 5 GHz mode (or the network name for this band is hidden), the phone will simply be physically unable to "see" the access point, while a newer laptop with a dual-band module will connect without issue.

However, the opposite situation also occurs: the phone tries to connect to the 5 GHz band, but the signal there is too weak due to the poor penetration of high frequencies through walls. A laptop, being closer to the router or having a more powerful antenna, maintains this signal, but the phone, being in another room, loses the connection or fails to complete the initial handshake. A function is often implemented in the router settings. Smart Connect, which combines both ranges under one name, which sometimes leads to client routing errors.

⚠️ Note: If your router is broadcasting two networks with the same name (SSID) for different frequencies, try temporarily separating them by adding "_5G" to the name. This will help you understand which band your phone is trying (or failing) to connect to.

To resolve this issue, you need to log into your router's control panel and check your wireless settings. Make sure the standard is 802.11 b/g/n active for the 2.4 GHz band. If your phone is older, it may not support new standards. ax or ac, which may be enabled on the router by default. Switching the wireless network operating mode to mixed (Mixed) often solves the compatibility problem.

Problems with DHCP and IP address assignment

When a device connects to a network, it requests an IP address from a DHCP server, which is usually built into the router. If the network is working on the computer, the server is functioning. However, mobile devices sometimes get stuck in the "Obtaining IP Address" state or receive an address already taken by another device on the network (IP conflict). In the router logs, this may appear as successful authorization, but the phone will remain stuck with the "Obtaining IP Address" status indefinitely.

Often, the problem stems from an overflowing DHCP lease table. The router has a limit on the number of simultaneous connections, and if you have many smart home devices, a camera, TV, and laptops, the DHCP memory can become full. A computer that has connected previously and has a saved lease can simply renew its old address, while a phone attempting to connect for the first time or after a reset no longer receives an address.

To diagnose and resolve this issue, you can try manually entering a static IP address in your phone's Wi-Fi settings. This will eliminate the possibility of a DHCP server error. You'll need to know the gateway (usually the router's address, such as 192.168.0.1) and subnet mask.

• 📱 Go to Wi-Fi settings on your phone and select your network.
• 🔧 Find the "IP Settings" item and switch from DHCP to "Static".
• 🌐 Enter an IP address that is different from those already in use (for example, if the router is 192.168.1.1, enter 192.168.1.150).
• 💾 Save your settings and try connecting again.

It's also worth checking the Lease Time in your router settings. If it's set too long (for example, 1 week) and the network is active, there may be no free addresses left. Reducing this time to 2-4 hours releases addresses faster, allowing new devices to connect successfully.

Encryption and network security type errors

Wireless network security is ensured by encryption protocols such as WPA2 and the newest WPA3Computers with modern network cards and up-to-date drivers easily adapt to new security standards. Mobile devices, especially those released more than 3-4 years ago, may lack hardware or software support for the WPA3 protocol. If the router is set to "WPA3 Only" mode, a phone simply won't be able to authenticate, although a laptop will connect without issue.

Another nuance is compatibility mode. Some routers use transitional mode when enabling WPA3. WPA2/WPA3 TransitionalIn theory, this should allow older devices to connect, but in practice, the implementation of this mode in firmware from different manufacturers (for example, Asus, TP-Link, Keenetic) may not work correctly. The phone may "see" the network, but when entering the password, access is denied.

Why is WPA3 mode dangerous for older devices?

WPA3 mode requires support for the SAE (Simultaneous Authentication of Equals) protocol. Older Wi-Fi drivers in phones only support the PSK (Pre-Shared Key) method. If the router forces SAE, the handshake simply won't take place, and the connection will be terminated during the password verification phase, even if the password is entered correctly.

It is recommended to check the security settings in the router control panel. For maximum compatibility, it is best to use a combination WPA2-PSK (AES)Avoid using outdated encryption. TKIP or mixed modes WPA/WPA2, as they can reduce speed and create security holes, although they provide backward compatibility with very ancient gadgets.

DNS cache overflow and routing errors

Sometimes, a phone is technically connected to the router (an IP address has been obtained and there's a connection), but the internet isn't working. However, websites can still open on the computer. This is a classic sign of DNS (Domain Name System) issues. The phone may have cached old or incorrect DNS addresses, while the computer is using up-to-date ones. It's also possible that the ISP has blocked DNS access for certain devices or ports, and the computer is bypassing this restriction using other methods (for example, IPv6, if configured).

Router settings often default to the provider's DNS servers, which can be unstable. A computer may ignore them and use its own (for example, Google or Yandex) if they're configured in the network adapter, while a phone blindly follows the router's instructions. As a result, everything works fine on the PC, while pages don't load on the smartphone.

To fix this, manually configure trusted DNS servers in your phone's Wi-Fi settings. This often works wonders and speeds up webpage loading.

After changing the DNS on your phone, be sure to turn off Wi-Fi and then turn it back on to clear the cache. If the problem was due to incorrect domain name records, the internet should work immediately. It's also worth checking whether parental controls or MAC address filtering are enabled on your router, which could have accidentally blocked your phone.

Driver failures and Wi-Fi module power saving

Mobile operating systems aggressively optimize energy consumption. Function Wi-Fi Power Save may not function correctly, especially after updating the phone's firmware. The system may "put the Wi-Fi module to sleep" at inopportune moments or prevent it from waking up for authentication. Computers running on AC power or with large batteries are less prone to such abrupt radio module shutdowns at critical moments.

Additionally, software junk may have accumulated in the phone's network settings. The connection profile may have become corrupted. Unlike Windows, where you can easily remove the device in Device Manager, on Android or iOS you need to reset the network settings, which deletes all saved passwords and Bluetooth configurations.

If you have Wi-Fi booster or traffic manager apps installed on your phone, they may conflict with system drivers. Such programs often require deep permissions and can block the standard connection process. Removing such software is the first step in troubleshooting.

MAC address filtering and router restrictions

One of the hidden reasons why your PC works but your phone doesn't is MAC address filtering enabled on your router. If the network administrator (perhaps you or the previous owner) has configured an "Allow List," access is restricted to specific devices. Your computer is on this list, but your phone isn't. As a result, your phone sees the network and may even request a password, but after entering the correct information, the connection fails.

There is also a problem with Randomized MAC Address (Random MAC address). Modern versions of iOS (starting with 14) and Android (starting with 10) use a random MAC address for each new connection by default for privacy reasons. If your router has strict IP-to-MAC binding rules or device restrictions, the router may treat a phone with a randomized address as a new, unauthorized device and block it.

To eliminate this factor, go to your phone's Wi-Fi settings, tap the network information icon (or the gear icon), and find "Privacy" or "MAC Address Type." Switch the setting from "Random" to "Device MAC Address" (use device MAC address). This will cause your phone to use its real, permanent physical address, which is easier to control and whitelist in the router.

⚠️ Note: Changing your MAC address may require you to re-enter your network password. Make sure you remember the current security key for your Wi-Fi network.

Frequently Asked Questions (FAQ)

Why does the phone say "Saved" but won't connect?

This means the password is correct and authentication was successful, but the router didn't assign an IP address or didn't allow the device onto the network. Check your DHCP settings, MAC address filter, and whether the phone is blacklisted in the router settings.

Will resetting the router help if the PC has internet access?

Resetting your router to factory settings will help if the problem is due to accumulated firmware errors or incorrect channel settings. However, this will require reconfiguring your internet connection (PPPoE, ISP login/password). Start by rebooting the router through the web interface without resetting the settings.

Can an antivirus on a computer block Wi-Fi on a phone?

Antivirus software doesn't directly affect your PC, as they're separate devices. However, if your antivirus software is built into your router (as a feature) or configured as a gateway, it may block unknown devices. Check the security logs on your router itself.

What should I do if my phone sees the 5 GHz network but doesn't connect?

Most likely, your phone is too far from the router for this range, or the channel is occupied by neighbors. Try changing the channel in your router settings to 36, 40, 44, or 48 (these are often less crowded) or force your phone to switch to 2.4 GHz.

Does the date and time on my phone affect my Wi-Fi connection?

Yes, very much so. If the date on your phone is off (for example, set to 2015), security certificates (SSL/TLS) will not be verified, and many networks (especially public or corporate ones, and sometimes home networks with complex authentication) may reject connections. Check if "Automatic date and time" is enabled.