Cannot connect to some windows PCs on Lan

Intermittent connectivity to specific Windows PCs on a LAN usually stems from misconfigured network discovery settings, outdated network adapters, or firewall restrictions rather than physical cabling failures. By verifying that the Network Discovery service is active, ensuring all devices reside on the same subnet, and updating driver software, you can restore stable file sharing and remote access between your machines.

Verify Network Profile and Subnet Configuration

The most common cause for being unable to see certain computers in your local area network is that Windows has classified the connection as "Public" instead of "Private." A public network profile aggressively blocks incoming connections for security reasons, effectively hiding your machine from others while still allowing internet access. To correct this, open the Settings app and navigate to Network & Internet. Select Wi-Fi or Ethernet depending on your connection type, then click on Properties for the active network. Change the network profile setting from Public to Private. This action tells Windows to trust the local network environment, enabling file and printer sharing features. It is also critical to ensure that all participating devices are on the same IP subnet. If one PC is connected via Ethernet with an IP address like 192.168.1.10 and another is on a guest Wi-Fi network with 192.168.0.x, they cannot communicate directly without routing. Open Command Prompt and run ipconfig to check the IPv4 address and default gateway. All devices must share the first three octets of their IP addresses (e.g., 192.168.1.x) and have matching subnet masks, typically 255.255.255.0. If devices are on different subnets, you may need to adjust router DHCP settings or reconnect devices to the correct VLAN. For more details on resolving broader LAN issues, see Troubleshooting LAN Connection Issues on a Brand New Windows 11 Machine.

Enable Network Discovery and File Sharing Services

Even with a private network profile, core services required for discovery might be disabled. Windows uses the Function Discovery Resource Publication service to broadcast its presence to other devices. Press Win + R, type services.msc, and hit Enter. Locate "Function Discovery Provider Host" and "Function Discovery Resource Publication." Ensure both are set to Automatic startup type and are currently Running. If they are stopped, right-click and select Start. Restarting these services often forces the computer to re-advertise itself on the network immediately. Additionally, verify that network discovery is enabled through the Control Panel. Navigate to Control Panel > Network and Sharing Center > Advanced sharing settings. Under the Private section, ensure that "Turn on network discovery" and "Turn on file and printer sharing" are selected. It is also wise to enable password protected sharing if you want to restrict access to authorized users only; otherwise, leave it off for easier guest access within a trusted home environment. These settings apply per-profile, so double-check that you are editing the Private profile settings and not the Guest or Public ones.

Update Network Adapters and Drivers

Outdated or corrupted network interface card (NIC) drivers frequently cause intermittent connectivity drops or failure to establish sessions with specific peers. Device Manager is the primary tool for diagnosing this. Right-click the Start button and select Device Manager, then expand Network adapters. Look for any entries with a yellow warning icon, which indicates a driver conflict or failure. Even without warnings, it is prudent to update the driver. Right-click your primary adapter (Ethernet or Wi-Fi) and select Update driver, choosing Search automatically for updated driver software. If automatic updates fail to resolve the issue, visit the manufacturer’s website for your motherboard or laptop model to download the latest LAN driver manually. Generic Microsoft drivers provided by Windows Update are sometimes insufficient for optimal performance with specific hardware. After installing the new driver, restart the computer to ensure the changes take effect. In cases where the NIC shows "No Connection" despite physical links being intact, consider rolling back to a previous version if the update introduced instability. You can find more insights on handling persistent connection errors in NIC shows "No Connection" in Windows 11 - works in Linux.

Check Firewall and Antivirus Restrictions

Third-party antivirus suites and Windows Defender Firewall can block SMB ports (445 and 139) used for file sharing and network discovery. If you recently installed new security software, it may have created strict rules that isolate your PC from the LAN. Temporarily disable third-party firewalls to test if connectivity returns. If it does, configure the firewall to allow inbound traffic for File and Printer Sharing. For Windows Defender, go to Windows Security > Firewall & network protection. Ensure that the rule for "File and Printer Sharing" is allowed on Private networks. Sometimes, custom rules added by enterprise policies or manual configurations can inadvertently block peer-to-peer communication. Check the advanced settings for inbound rules to ensure no deny rules are overriding the standard allow rules. Additionally, ensure that the "Network Connectivity Status Indicator" service is running, as it helps Windows determine if the network is usable for sharing resources.

Reset Network Stack

When configuration changes do not yield results, resetting the entire network stack can clear corrupt DNS caches, socket bindings, and TCP/IP configurations. Open Command Prompt as Administrator. Execute the following commands in order, pressing Enter after each: netsh winsock reset, netsh int ip reset, and ipconfig /release followed by ipconfig /renew. Finally, restart the computer. This process forces Windows to rebuild its network configuration files from scratch. It is particularly effective when dealing with obscure issues where some PCs connect and others do not, suggesting a localized protocol error.

Frequently Asked Questions

Why can I ping the IP address but not see the computer name?

This indicates that basic IP connectivity is working, but Name Resolution (DNS or NetBIOS) is failing. Ensure that the Function Discovery services are running on both machines. You can try accessing the shared folder using the IP address directly (e.g., \\192.168.1.10) to bypass name resolution issues temporarily.

Does disabling Fast Startup help with LAN connectivity?

Yes, Fast Startup can sometimes prevent network adapters from fully initializing during boot, leading to delayed or failed network discovery. Disabling Fast Startup in Power Options ensures a full cold boot, which often stabilizes network connections on the first login attempt.

What should I do if the problem persists after updating drivers?

If driver updates fail, try uninstalling the network adapter in Device Manager and restarting the PC to force a clean reinstall of the default driver. You can also check for BIOS/UEFI updates from your hardware manufacturer, as these can contain fixes for underlying chipset networking issues.

Can a VPN interfere with LAN connections?

Absolutely. Many VPN clients route all traffic through the tunnel, including local LAN broadcasts, which prevents discovery protocols from reaching your local network. Configure your VPN client to split-tunnel traffic or disconnect it entirely when accessing local resources.

How do I check if SMB 1.0 is causing issues?

SMB 1.0 is deprecated and insecure, but some older devices rely on it. While modern Windows disables it by default, ensure that SMB 2.0 and 3.0 are enabled in Server Manager > Features. Avoid enabling SMB 1.0 unless absolutely necessary for legacy hardware, as it poses significant security risks.