How to Resolve Copilot ‘NetBIOS Name Resolution Failed’ on Hybrid AD

When you run Copilot in a hybrid Active Directory environment, you may see the error ‘NetBIOS Name Resolution Failed.’ This error stops Copilot from connecting to on-premises resources like file shares or domain controllers. The root cause is a mismatch between how Copilot resolves NetBIOS names and how your network handles name resolution. This article explains why the error occurs and provides step-by-step fixes to restore Copilot connectivity.

Why Copilot Fails to Resolve NetBIOS Names in Hybrid AD

Copilot in Microsoft 365 uses several mechanisms to discover and connect to on-premises resources. In a hybrid Active Directory setup, where some domain controllers are on-premises and others are in Azure AD, name resolution can break. The error ‘NetBIOS Name Resolution Failed’ specifically means that Copilot sent a NetBIOS name query but received no reply from the network.

NetBIOS name resolution relies on broadcast messages or the LMHOSTS file. In hybrid environments, broadcasts often do not cross subnet boundaries. If the target server is on a different subnet, the broadcast fails. Additionally, if DNS is not configured to resolve NetBIOS names, Copilot cannot fall back to DNS-based resolution. The typical scenario is a user on a workstation joined to Azure AD trying to access a file share on an on-premises server that only responds to its NetBIOS name.

How Copilot Uses Name Resolution

Copilot checks the following order when resolving a name: NetBIOS cache, WINS server if configured, broadcast on the local subnet, LMHOSTS file, then DNS. If none of these succeed, Copilot returns the error. In hybrid AD, WINS is often absent. Broadcasts are blocked by routers. DNS may not have the NetBIOS name registered. This failure cascade produces the error.

Steps to Resolve NetBIOS Name Resolution Failure for Copilot

The fix depends on your network architecture. Choose the method that matches your environment. Apply changes on the machine where Copilot runs.

Method 1: Configure DNS Suffix Search Order

1. Open Network Adapter Properties
   Press Windows key + R, type ncpa.cpl, and press Enter. Right-click your active network adapter and select Properties.
2. Select Internet Protocol Version 4
   Double-click Internet Protocol Version 4 TCP/IPv4. Click the Advanced button at the bottom.
3. Add Domain Suffix to DNS Search List
   In the DNS tab, under DNS suffix for this connection, select Append these DNS suffixes. Click Add and type your on-premises domain name, for example contoso.local. Click Add again and type the parent domain if needed. Click OK on all dialogs.
4. Test Name Resolution
   Open Command Prompt as administrator. Type nslookup server-name replacing server-name with the NetBIOS name of the target resource. If it resolves, Copilot will use DNS to find the resource.

Method 2: Enable NetBIOS over TCP/IP

1. Open Network Adapter Properties
   Press Windows key + R, type ncpa.cpl, and press Enter. Right-click your active network adapter and select Properties.
2. Select Internet Protocol Version 4
   Double-click Internet Protocol Version 4 TCP/IPv4. Click the Advanced button.
3. Enable NetBIOS
   Go to the WINS tab. Under NetBIOS setting, select Enable NetBIOS over TCP/IP. Click OK on all dialogs.
4. Restart the Network Adapter
   In Network Connections, right-click the adapter and select Disable. Wait 5 seconds, then right-click and select Enable. This applies the new setting.

Method 3: Add Entries to the LMHOSTS File

1. Open LMHOSTS File
   Press Windows key + R, type notepad C:\Windows\System32\drivers\etc\lmhosts.sam, and press Enter. If prompted, click Yes to create a new file.
2. Add NetBIOS Name and IP Mapping
   At the end of the file, add a line with the IP address, a space, and the NetBIOS name. For example: 192.168.1.50 fileserver. Save the file as lmhosts without any extension in the same folder. The system already has a file named LMHOSTS without extension. If not, save as type All Files and name it LMHOSTS.
3. Flush DNS and NetBIOS Cache
   Open Command Prompt as administrator. Run ipconfig /flushdns then nbtstat -R. The -R flag reloads the LMHOSTS file into the NetBIOS name cache.
4. Verify Resolution
   Run nbtstat -a fileserver replacing fileserver with the NetBIOS name. If the command returns the IP address, Copilot can now resolve the name.

If Copilot Still Has Issues After the Main Fix

Copilot Returns the Same Error After DNS Configuration

If you configured the DNS suffix search order but the error persists, the target server may not have a DNS A record. Check the DNS zone on your on-premises domain controller. Open DNS Manager and verify that the server name appears under the forward lookup zone. If missing, create a host A record manually. Copilot will then resolve the name via DNS.

Copilot Works on Some Machines but Not Others

This usually indicates that the machines that fail are not joined to the on-premises domain or do not have the correct DNS suffix. Verify that each machine has the DNS suffix search order configured as described in Method 1. For Azure AD-joined machines, add the on-premises domain suffix to the connection-specific DNS suffix list.

Copilot Still Cannot Reach the Resource After NetBIOS Enablement

If NetBIOS over TCP/IP is enabled but the error remains, the target server may have NetBIOS disabled. On the server, open Network Adapter Properties, select TCP/IPv4, click Advanced, go to the WINS tab, and ensure Enable NetBIOS over TCP/IP is selected. Restart the server after the change.

Copilot NetBIOS Name Resolution Methods: Comparison

Item	DNS Suffix Search	NetBIOS over TCP/IP	LMHOSTS File
Requires Domain Join	No, works on any machine	No, works on any machine	No, works on any machine
Network Overhead	Low, uses existing DNS	Medium, broadcasts can increase traffic	None, static file
Administrative Effort	Medium, per-machine or Group Policy	Low, per-machine setting	High, must update file for each resource
Works Across Subnets	Yes	No, broadcasts are local	Yes, IP-based
Best For	Hybrid AD with working DNS	Small flat networks	Few static servers

Copilot in hybrid AD environments requires reliable name resolution to access on-premises resources. The error ‘NetBIOS Name Resolution Failed’ occurs when broadcasts fail and DNS is not configured to resolve NetBIOS names. By configuring the DNS suffix search order, enabling NetBIOS over TCP/IP, or using the LMHOSTS file, you can restore Copilot connectivity. For persistent issues, verify that both the client and target server have NetBIOS enabled and that DNS records exist. After applying the fix, test with nbtstat -a to confirm resolution before using Copilot.