Root-cause diagnosis of a Wi-Fi extender's NAT mode silently splitting a home network into two subnets, breaking Windows file sharing. Fixed by converting the extender to access-point mode - no Windows changes needed.
- ✓8-step elimination: services → permissions → firewall → ipconfig → ping → DHCP trace → extender UI
- ✓Caught by evidence: laptop gateway 192.168.2.1 vs desktop 192.168.1.1 - a second DHCP server
- ✓Root cause: extender in Router/NAT mode with DHCP pool 192.168.2.100–199
- ✓Fix: AP/bridge mode, extender DHCP off → single 192.168.1.0/24, sharing restored instantly
TCP/IPSubnettingSMBDHCPNATWireshark-style analysis
192.168.1.105 /24
gw 192.168.1.1 · DHCP 192.168.1.1
EXTENDER
NAT MODE
⇅ double NAT
NAT MODE
⇅ double NAT
192.168.2.58 /24
gw 192.168.2.1 · DHCP 192.168.2.1
✗ "Windows cannot access \\computername\share" - NetBIOS/LLMNR broadcasts never cross the NAT boundary.
Desktop .105 ━ Router .1 ━ Extender .200 (AP bridge) ━ Laptop .106
One DHCP server · one gateway (192.168.1.1) · broadcasts forwarded
✓ \\PC\share opens instantly - Network Neighborhood populates. No Windows changes were needed.
- 1. Services + permissions + firewall ruled out first (all healthy)
- 2. ipconfig exposed two subnets + two DHCP servers
- 3. Rogue DHCP traced to the extender in Router/NAT mode (pool .100–199)
- 4. Extender → Access Point mode, DHCP off, reboot
- 5. Both hosts on 192.168.1.x, gateway .1 - SMB verified
How it works
- SymptomsShares refused to open; Network Neighborhood empty; \\IP\share failed; ping-by-name failed but ping-by-IP worked.
- Rule out WindowsDiscovery services running, Everyone permissions set, firewall disabled temporarily - no change.
- ipconfig revealsDesktop 192.168.1.105/24 via 192.168.1.1; laptop 192.168.2.58/24 via 192.168.2.1. Two subnets, two DHCP servers.
- Trace the rogue DHCP192.168.2.1 was the extender - running Router/NAT mode, its own pool and gateway.
- Fix + verifyAP mode, DHCP off, reboot, renew - both on 192.168.1.x, same gateway, SMB works.
SMOKING GUN - IPCONFIG /ALL
| Interface | Address |
|---|---|
| Desktop (wired) | 192.168.1.105 · mask /24 · gw 192.168.1.1 · DHCP 192.168.1.1 |
| Laptop (Wi-Fi) | 192.168.2.58 · mask /24 · gw 192.168.2.1 · DHCP 192.168.2.1 |
BEFORE VS AFTER
| Aspect | Before → After |
|---|---|
| Topology | Extender NAT, two subnets → AP bridge, one flat network |
| Addresses | Desktop .1.x + laptop .2.x → both 192.168.1.x |
| DHCP | Router + extender → router only |
| Broadcast domain | Two → one (NetBIOS/LLMNR discovery restored) |
| File sharing | Inaccessible → fully functional |
DIAGNOSIS COMMANDS
cmd
ipconfig /all ping 192.168.1.105 \\192.168.1.105\share
—Reproduce: extender in Router/NAT mode → clients land on 192.168.2.x
—Gather: ipconfig on both machines, compare gateway + DHCP server
—Fix: extender admin → Access Point mode → DHCP off → reboot
—Verify: both on 192.168.1.x/24, gateway 192.168.1.1, SMB opens