Advertisement

Realtek LAN adapter cannot find shared computers: fixes

If a Realtek wired adapter can reach the internet but not shared PCs, the problem is often Windows discovery, subnet, or sharing settings. Start with the safest checks first, then narrow down whether the adapter, router, or the other computer is blocking visibility.

Networking 9 min read
A Windows desktop PC is connected to the network with an Ethernet cable on a desk.

A Realtek wired adapter that can reach the internet but cannot find shared computers is usually a Windows discovery or network-segmentation problem, not a dead Ethernet port. Start with the network profile, subnet, and sharing settings. Then test whether the computer name fails while the direct IP still works. Only after that should you suspect the Realtek adapter itself.

What this problem usually means

If web browsing works but shared PCs and folders do not appear in File Explorer, the network link is probably up while Windows discovery is not. In practice, that usually points to the network profile, discovery services, SMB sharing settings, or an isolated router or switch path.

Internet access only proves the adapter can send traffic out to the network. Seeing shared computers depends on three things: your PC must be on the same local segment, Windows must be allowed to discover peers, and the other machines must advertise themselves correctly.

If only one PC has the problem, the fault is usually local to that machine. If every PC on one wired LAN loses visibility at the same time, look harder at the router, switch, VLAN, guest network, or port isolation before changing drivers.

Before you start

Use the safe checks first. They show whether this is a Windows setting problem, a local network layout problem, or a real adapter fault, and you can reverse them later.

  • You should be signed in with an account that can change the network profile and sharing settings.
  • Have one other PC available for comparison if you can.
  • If you plan to check services, be ready to restart the PC only after you’ve confirmed the service state.
  • If the machine also drops the Ethernet link, changes subnet unexpectedly, or keeps switching network profile, treat the adapter or cable path as a stronger suspect.
  1. Check the network profile on the Ethernet connection.
Settings path
Settings > Network & internet > Ethernet > Network profile

Set the connection to Private on a home or small-office LAN. Public mode often blocks discovery and file sharing by design. If it is already Private, leave it there and move on.

  1. Compare your subnet with a PC that can see the shares.

Open the adapter details on both PCs and compare the IPv4 address, subnet mask, and default gateway. On a typical home LAN, the addresses should be in the same local range and use the same gateway. If one PC is on a different subnet, VLAN, guest network, or isolated port, it can still get internet access while local discovery fails.

  1. Check the cable, switch port, and wall jack.

Make sure the cable is fully seated and the link light is on. If the PC goes through a switch, try another port. If you can, test with a known-good cable and a different port on the router or switch. A bad port or a marginal cable can leave internet access looking normal while local discovery acts strangely.

  1. Stop here if every PC on one wired LAN has the same symptom.

That points away from the Realtek adapter and toward the network device or topology. At that point, changing Windows drivers on one PC usually wastes time.

Check the Windows sharing and discovery settings

Windows can have a healthy network adapter and still hide shared computers if discovery or file sharing is turned off.

  1. Turn on Network Discovery for the Private profile.

Make sure discovery is enabled for the current Private network profile. If Windows has separate sharing options for the current profile and for all networks, fix the current profile first. That setting usually decides whether nearby PCs show up at all.

  1. Turn on File and Printer Sharing.

If this is off, Windows may not advertise the PC properly for SMB sharing, and browsing nearby machines often fails even though the network link is fine.

  1. Leave unrelated sharing settings alone unless you know why you need them.

You do not need to change every advanced sharing option to fix this. The safer move is to correct the current profile, test again, and only then touch anything else.

  1. If the PC recently changed from Private to Public, switch it back before doing anything else.

That one change is enough to hide discovery on a local LAN, especially after a driver update, a router change, or a network reset.

Check the discovery services Windows needs

If the sharing switches are correct and the PC still cannot see shared computers, check the services that publish and find devices on the network.

  1. Open Services and look for the discovery-related entries.

Check Function Discovery Provider Host and Function Discovery Resource Publication. These help Windows announce the PC and find other devices on the local network.

  1. Make sure those services are running.

If one is stopped, start it. If it keeps stopping, that suggests a deeper Windows problem rather than a Realtek-only problem. At that point, changing the adapter driver is usually not the first fix.

  1. Restart the PC only if the service change does not take effect immediately.

A reboot can make the symptoms look better without telling you what caused them, so I’d only use it after you’ve checked the service state.

  1. If you still rely on older SMB browsing behavior, check whether NetBIOS over TCP/IP was disabled.

Some mixed home and small-office networks still depend on older name-browsing behavior for older devices or NAS units. If that setting was changed recently, put it back only if your network actually needs it.

Test name-based discovery against direct IP access

This is the quickest way to separate discovery problems from file-sharing problems.

  1. Try opening the shared computer by name.

Enter \\ComputerName in File Explorer or the Run box.

If the name works but the PC never appears under Network, the share itself is probably fine and the problem is discovery or browsing. If the name does not work, keep going.

  1. Try the same share by IP address.

Enter \\192.168.x.x\SharedFolder with the other PC’s actual local IP address.

If the IP works but the name does not, the issue is name resolution or browsing, not the share itself. If neither the name nor the IP works, the problem is broader: the other PC may not be sharing correctly, Windows may be blocking access, or the network may be isolating devices.

  1. Compare one invisible PC with one visible PC.

If one machine can see shares and this one cannot, the problem is local to this PC. If none of the machines can see each other, stop looking at the Realtek adapter and inspect the router, switch, guest network, VLAN, or isolation settings instead.

Look for router, switch, cable, or isolation settings that hide shared computers

A wired adapter can be perfectly healthy and still be cut off from local discovery by the network gear.

  1. Check for guest network or client isolation.

If the PC is on a guest network, a separated VLAN, or a port with isolation enabled, it may get internet access but be prevented from seeing local machines. That is common on some routers and managed switches.

  1. Check the switch and router path.

If the PC is plugged into a different switch, a second router, or a wall jack that lands on another segment, it may not be on the same LAN as the shared computers. That kind of layout can be easy to miss because the web still works.

  1. Move the PC to a normal LAN port if you have one.

Do not test from a guest port, uplink port, or any port labeled for isolation. If moving to a plain LAN port fixes discovery, the adapter was not the problem.

  1. Stop blaming the Realtek adapter if multiple devices on one segment fail together.

When the symptom shows up across several PCs, the router or switch settings are the more likely cause.

When the Realtek adapter is the likely cause

The adapter moves up the list only after you’ve ruled out profile, sharing, services, subnet, and isolation problems.

  1. Treat the adapter as a stronger suspect if the link itself is unstable.

If the PC keeps dropping the Ethernet connection, keeps changing network profile, or fails on multiple known-good cables and ports, the adapter or its driver deserves attention.

  1. Treat Windows discovery as the more likely cause if internet access still works cleanly.

If the PC stays online but only discovery is broken, that usually points to Windows settings or services rather than the Realtek hardware.

  1. Roll back the last change if things got worse after a tweak.

If changing sharing settings, services, or the network profile makes access worse, undo the last change first. That is safer than jumping straight to a driver reinstall or a BIOS change.

Verify the fix worked

  1. Open Network in File Explorer and confirm that the other computers appear.
  1. Try \\ComputerName for one shared PC and \\192.168.x.x\SharedFolder for the same PC.
  1. Open one shared folder from File Explorer without getting a permission or path error.

If the machine appears under Network and both the name and the direct IP open the share, the fix worked. If the name still fails but the IP works, you still have a discovery or name-resolution problem rather than a file-sharing problem. If both fail, the issue is still on the network path, the other PC, or the sharing setup.

Conclusion

If the PC can get internet but cannot see shared computers, keep the problem framed as discovery first and adapter second. Check the profile, subnet, sharing settings, services, and network isolation in that order, then move on to the Realtek driver only if the link itself looks unstable.

Frequently Asked Questions

Should I reinstall the Realtek driver first?

Usually not. If internet access still works, start with the Windows network profile, discovery settings, services, and subnet checks. Those are more likely to block shared computers than the Realtek driver itself.

Why can I browse the internet but not see shared PCs?

Because internet access and local network discovery are different jobs. The adapter can pass web traffic while Windows browsing, SMB visibility, or name resolution is blocked by profile settings, services, or network isolation.

How do I know if the router or switch is the problem?

If several PCs on one wired LAN all fail to see each other, suspect the router, switch, VLAN, guest network, or port isolation. If only one PC is affected, the fault is usually local to that machine.