Fix ERROR_NO_BROWSER_SERVERS_FOUND (0X000017E6) Fast

Cause #1: The Computer Browser Service Is Stopped or Disabled

Nine times out of ten, this is the fix. The Computer Browser service (and its dependencies) just isn't running. This happens after a reboot, a Windows update, or some well-meaning admin disabled it.

Check the service immediately. On your Windows Server 2016, 2019, or 2022 box, open services.msc. Look for these three services:

• Computer Browser
• Server
• Workstation

All three need to be running. Computer Browser is the one that actually generates the browse list — the list of servers in your workgroup or domain. If it's stopped, you get error 0X000017E6.

# Quick PowerShell check
Get-Service -Name "Browser", "LanmanServer", "LanmanWorkstation" | Format-Table Name, Status

If Computer Browser is stopped, set it to Automatic and start it:

Set-Service -Name Browser -StartupType Automatic
Start-Service -Name Browser

Don't bother checking the registry or messing with HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters unless you're dealing with old XP-era boxes. Modern Windows Server handles this fine on its own.

After starting the service, give it a minute. Then test with net view from another machine in the same workgroup. If the list pops up, you're done. If not, move to cause #2.

Cause #2: NetBIOS over TCP/IP Is Disabled

I've seen this one trip up a lot of people. The browser service relies on NetBIOS to announce itself and find other servers. If you've disabled NetBIOS over TCP/IP on the network adapter — maybe as part of a security hardening checklist — the browse list won't populate.

Check your network adapter settings. Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your main NIC, select Properties, then select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Click the Advanced button, then the WINS tab. Make sure Enable NetBIOS over TCP/IP is selected.

Alternatively, you can check via the registry:

Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\Tcpip_*" -Name NetbiosOptions

If NetbiosOptions is 2, it's disabled. Set it to 0 (enable) or 1 (default).

This fix needs a reboot or at least a restart of the netbt service. I've seen plenty of servers where NetBIOS was disabled as a "best practice" — but if you're still using a workgroup or older NetBIOS-dependent apps, you need it.

After you enable NetBIOS, restart the Computer Browser service and test again. This fix alone resolves about 30% of the remaining cases.

Cause #3: Master Browser Election Conflicts

This one's trickier. The browser service uses an election process to pick the master browser — the machine that maintains the browse list. If you have multiple servers configured as "Preferred Master" browsers, or if a machine with a higher OS version keeps winning the election and then dropping off the network, the list never stabilizes.

The fix is to stop the Computer Browser service on all machines except one designated server. This isn't a cluster — just pick one reliable server to be the browser. On the other machines, set the service to Disabled.

# On non-browser servers:
Set-Service -Name Browser -StartupType Disabled
Stop-Service -Name Browser

Alternatively, you can force a specific server to be the master browser by adding a registry key. But I don't recommend that — it's brittle and can cause issues if that server goes down. Just let one server handle it.

If you're on a domain, consider using DFS Namespaces instead. It's way more reliable than the old browser system. But if you're stuck on a workgroup, this is the best you can do.

Quick-Reference Summary Table