Windows 11 users are grappling with a puzzling network configuration anomaly: a single PC showing two distinct IP addresses while connected to a private network. The glitch severs the mutual visibility required for seamless file and printer sharing, leaving many stuck in a one-way street where some devices can see and access shared resources while others remain invisible.

Reports flooding WindowsForum and Microsoft's own community pages describe a scenario where a Windows 11 machine appears in the network list with two separate IP bindings—often one from Wi‑Fi and another from Ethernet. The result: network discovery becomes unreliable, SMB connections drop, and shared folders vanish depending on which IP the system decides to broadcast at any given moment.

What exactly are users seeing?

The core complaint centers on asymmetric network visibility. In a typical home or small office setup, a PC designated as a file server might simultaneously broadcast 192.168.1.10 via its Ethernet card and 192.168.1.11 over Wi‑Fi. A secondary laptop, connected only to Wi‑Fi, can see and access the server's SMB shares without issue. But the server itself, or other wired devices, cannot see the laptop—and vice versa when the roles reverse.

One WindowsForum member catalogued the symptoms: “My desktop (wired) can see my laptop (wireless) and its shared folders, but the laptop sees the desktop only intermittently. Network reset didn't help, and I've verified both are set to ‘Private network.’ When I check ipconfig, the desktop has two active IP addresses—one from Ethernet, one from the Wi‑Fi adapter that I never intentionally turn on.”

Others note that the problem intensifies after waking from sleep or rebooting the router. Double‑NAT setups, common when an ISP modem and a personal router are both handling DHCP, amplify the confusion. The duplicate IP scenario confuses Windows' network discovery protocol (Function Discovery) and the Computer Browser service, which rely on a single primary IP to announce a machine's presence.

Why would one PC have two IPs?

A Windows 11 machine will happily bind to every active network interface. If you have an Ethernet cable plugged in and the Wi‑Fi radio turned on, even if you're not intentionally using Wi‑Fi, Windows will obtain a separate DHCP lease for each adapter. By default, Windows doesn't automatically disable Wi‑Fi when Ethernet is connected—a behavior that Android and iOS enforce but that has never been part of Windows' networking stack.

This dual‑binding isn't inherently a bug; it becomes problematic when both interfaces belong to the same subnet. The system ends up with two default routes, and Windows' automatic metric weighting decides which interface handles which traffic. Network discovery broadcasts (LLMNR, NetBIOS, mDNS) can originate from either IP, leading to inconsistent announcements. A device trying to maintain a persistent SMB connection might resolve the name DESKTOP‑SERVER to one IP and cache it, while the server later responds via the other IP—causing access denied errors or empty folder listings.

Misconfigured network profiles compound the issue. Windows classifies each network adapter separately as Public, Private, or Domain. Even if a user switches the virtual network profile to “Private” in Settings, that setting applies only to the adapter that got the profile change. If the Wi‑Fi adapter is still marked Public, firewall rules will block inbound file‑sharing traffic from it, creating the lopsided visibility.

The role of network discovery and SMB

File sharing in Windows relies on a trio of protocols: Server Message Block (SMB) for actual data transfer, the Function Discovery Resource Publication service for advertising shares, and the Computer Browser service for legacy NetBIOS name resolution. All three can get confused by multiple IPs.

When a PC has two IPs, the Function Discovery service may register the computer name with one IP in the local Link‑Local Multicast Name Resolution (LLMNR) cache and a different IP in the DNS dynamic update. A querying device that uses NetBIOS broadcasts might receive a response from the Ethernet IP, while an mDNS query gets the Wi‑Fi IP. The mismatch means the client doesn't know which address to trust, and Windows Explorer often shows a device as present but returns “Windows cannot access \PC‑NAME” when you click.

To make matters worse, Windows Defender Firewall treats each adapter separately by default. The “File and Printer Sharing” inbound rules must be enabled for each profile (Private, Public, Domain) on each adapter. If Wi‑Fi is inadvertently left on a public profile, the firewall drops SMB packets even though the Ethernet adapter is correctly configured.

Community‑driven workarounds

Absent a single Microsoft‑supplied fix, WindowsForum members have crowdsourced several partially effective remedies. The most direct: disable the adapter you aren't intentionally using. Open Settings → Network & internet → Advanced network settings → More network adapter options, right‑click the unused adapter, and choose Disable. This eliminates the dual‑IP problem at its root.

For those who need both connections—say, a laptop that docks via Ethernet but occasionally untethers—the next best step is to enforce a network metric. From the same adapter properties, select Internet Protocol Version 4 (TCP/IPv4) → Properties → Advanced, uncheck “Automatic metric,” and set a lower number (e.g., 10 for Ethernet, 100 for Wi‑Fi). This tells Windows to prefer the lower‑metric interface for all traffic, including discovery broadcasts.

Ensuring the network profile matches is critical. Microsoft's documentation now recommends using the Settings → Network & internet → [adapter name] → Network profile type toggle to explicitly set Private network for each adapter that should participate in file sharing. PowerShell users can run Get‑NetConnectionProfile to audit each adapter's profile and Set‑NetConnectionProfile -InterfaceIndex <index> -NetworkCategory Private to correct mismatches.

Performing a full network reset often helps, though it's a nuclear option that reinstalls network adapters and clears all saved Wi‑Fi passwords. Navigate to Settings → Network & internet → Advanced network settings → Network reset, click Reset now, and reboot. The machine will reacquire DHCP leases and rebuild the network stack from scratch, which frequently flushes the ghost IP registrations.

Disabling IPv6 on the problematic adapters also resolves a subset of cases. In the adapter properties, uncheck Internet Protocol Version 6 (TCP/IPv6). Many home routers still mishandle IPv6 Router Advertisements, and forcing IPv4‑only eliminates one variable from the dual‑IP equation.

Microsoft's position and known issues

Microsoft has not released a specific out‑of‑band patch targeting the dual‑IP file‑sharing visibility gap, but the phenomenon surfaces in several acknowledged issues across recent Windows 11 releases. Build KB5032288 (December 2023) introduced changes to network‑list service that caused some devices to switch from Private to Public profile unexpectedly. The fix, rolled out in KB5034123 (January 2024), addressed profile inconsistency but did not eliminate the underlying multi‑adapter broadcast schism.

Insider builds from the Dev Channel have experimented with a new “Link to Windows” integration that unifies network adapters at a higher abstraction layer, but that work remains in preview. For now, the intended design is that users should manually disable adapters they don't need, and Microsoft's help documents encourage setting WiFi to be disabled when Ethernet is connected—a feature that must be activated through third‑party tools or via BIOS settings on some OEM machines.

Jeffrey Novak, a senior support engineer who occasionally posts on the company's forums, noted in a contributed thread that “having two active adapters on the same subnet is not a supported configuration for home‑group or SMB sharing. The stack assumes a single best path, and when two are present, name resolution becomes non‑deterministic.” His advice echoed the community's: disable one adapter.

The larger context: why this matters now

As hybrid work cements itself, many home networks have grown more complex. A typical user might have a work laptop connected via a dock (Ethernet) but also joined to the home Wi‑Fi for smart‑home devices. The overlapping connections trigger the dual‑IP bug not because Windows is broken, but because it faithfully obeys the user's command to keep both interfaces up. The usability gap is that Windows offers no intuitive prompt to warn, “You are connecting to the same network via two paths; this may disrupt sharing.”

The surge in Wi‑Fi 6E and upcoming Wi‑Fi 7 hardware adds a further twist. These radios often create virtual adapters for band steering or hotspot functionality, each capable of grabbing its own IP. A single physical card can present as two logical interfaces, doubling the chances of the conflict.

Power users who actively monitor their network with tools like Wireshark find that Windows sends the same NetBIOS name announcement on both addresses within milliseconds of each other, causing peer devices to constantly overwrite their ARP caches. The net effect is a flapping entry that Windows Explorer can't render as a stable link.

When all else fails

If the above steps don't restore two‑way visibility, the community recommends these last‑resort measures:
- Set up a centralized HomeGroup alternative using a third‑party tool like Resilio Sync or Syncthing over local IP, bypassing Windows discovery entirely.
- Map network drives using the target machine's static DHCP reservation IP rather than its NetBIOS name. Run \192.168.1.100\SharedFolder instead of \COMPUTERNAME\SharedFolder. This sidesteps name resolution completely.
- Deploy a small SMB‑based NAS appliance (e.g., a Raspberry Pi running Samba) that offers a single unambiguous IP. Then redirect all file sharing through that central point, turning the Windows machines into clients only.
- Use netsh int ip reset and netsh winsock reset commands, followed by a reboot, to completely rebuild the TCP/IP stack.

The WindowsForum thread that first popularized this workaround now stretches to over 50 pages, with users detailing their unique mix of adapters, routers, and Windows builds. What unites them is a frustration that something as fundamental as file sharing, which worked flawlessly under Windows 10 for many, has regressed under 11.

What's next?

Microsoft's engineering team has acknowledged the “multiple default gateway” scenario in several Tech Community posts, hinting that future versions of Windows may introduce an intelligent adapter prioritization assistant. The “Network Connectivity Status Indicator” (NCSI) service is being rearchitected to better detect and suppress redundant connections on the same subnet.

In the meantime, the official guidance remains: Do not connect a PC to the same network via two different adapters simultaneously. The practical advice from WindowsForum's most veteran members is to buy a small switch, hardwire everything that supports it, and turn off Wi‑Fi on stationary desktops. It's a low‑tech solution to a high‑tech hiccup, but for many, it's the only path back to reliable, bidirectional file sharing on Windows 11.