About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A user opens a namespace path such as \\contoso.com\Public and gets:
Windows cannot access \\<Domain Name>\<DFS Namespace>
or "The network path was not found."
It is tempting to go straight to the file server and check the share permissions. But a DFS path is not a share. It is a name that the client has to turn into a real server and share by asking for a referral. Microsoft's page on this error says it typically occurs because the DFS namespace client cannot complete the connection to a DFS namespace path (Microsoft Learn, Troubleshoot DFS Namespace access failures). The checks below find which part of that chain broke.
What you see
- "Windows cannot access \\<domain>\<namespace>" or "The network path was not found" on the namespace path.
- Older Windows versions showed a longer message ending "Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied."
Why it happens
How the path works, from Microsoft's DFS Namespaces overview: a domain-based namespace such as \\Contoso\Public begins with the domain name, and its settings are stored in Active Directory. When a user opens a folder with folder targets, the client receives a referral that redirects it to one of the targets, for example \\LDN-SVR-01\Tools or \\NYC-SVR-01\Tools, depending on the user's site (Microsoft Learn, DFS Namespaces overview).
So there are three places it can fail. Microsoft lists them as:
- The client cannot reach a domain controller to get the namespace referral.
- The client cannot reach a namespace server.
- The namespace server does not provide a folder referral.
Underneath those, Microsoft's page names network connectivity, name resolution, and DFS service and site configuration.
How to prove the cause
Microsoft's access-failures page uses dfsutil with the parameters shown below. The dfsutil reference page says client cache functions sit under dfsutil cache and can only be done with dfsutil, not PowerShell; run dfsutil cache /? on your server to see the exact syntax for your version (Microsoft Learn, dfsutil). dfsutil comes with the DFS Management Tools.
1. Did the client find a domain controller? On the client:
dfsutil /spcinfo
This shows the domain cache: the domains and domain controllers the client has found. Microsoft explains that entries marked + are the domain controllers the client is using now. Then test a plain connection to that domain controller by IP address:
net view \\<DC IP address>
A successful connection lists the domain controller's shares.
2. Did the client get a referral, and is any target active? Open the DFS path once, then:
dfsutil /pktinfo
This shows the referral cache. Microsoft's example for \contoso.com\dfsroot lists two root targets, one marked ( ACTIVE ), and a link entry with its own target.
- No entry for the namespace: the domain controller did not return a referral. Go to step 4.
- An entry, but no target marked ACTIVE: the client reached a domain controller but none of the namespace targets. Go to step 3.
3. Can the client reach each namespace server? Test each server by IP address only:
net view \\<namespace server IP address>
Microsoft says to use the IP address only and not add the namespace share (\\<IP>\dfsroot), because you may otherwise be referred to another DFS root server and get misleading results.
4. Do the names resolve correctly? Every server name in the /spcinfo and /pktinfo output must resolve to the right address.
net view \\<server NetBIOS name>and check the shares listed belong to that server.nbtstat -cshows the NetBIOS name cache.ipconfig /displaydnsshows the DNS names the client has resolved.
Microsoft notes that by default DFS namespaces store NetBIOS names for root servers. A network without WINS can be set up to use DNS names (fully qualified domain names) in referrals instead.
5. Is the DFS configuration right?
The DFS Namespace service is started on every domain controller and namespace server, and no DFS errors appear in their System event logs.
Active Directory replication is healthy. Microsoft explains that changes to a domain-based namespace are made on the PDC emulator, and that domain controllers and root servers poll it for configuration. Check the last inbound replication on each domain controller:
repadmin /showrepl * DN_of_domain(for example
dc=contoso,dc=com).Site settings. Microsoft describes a common case: a client in a site that has no namespace or folder targets, with the namespace set to give referrals only in the client's site (the insite option). Check it with:
dfsutil /path:\\contoso.com\dfs /insite /displayA namespace server works out the client's site from the client's source IP address. Check what site it sees, on the domain controller or root server:
dfsutil /sitename:<client IP address> dfsutil /sitename:<root target name>
6. Still unclear: capture the traffic. Microsoft's troubleshooting checklist says to look at SMB traffic on port 445 for the DFS referral, which capture tools label DFSC. Is a referral request sent? Does it reach the namespace server? Does a referral response come back? Then does the client resolve and connect to the file server? (Microsoft Learn, DFS Namespace troubleshooting guidance). Before capturing, flush the client's caches so the names and referrals are requested again over the network. Microsoft gives this order:
nbtstat -RR
ipconfig /flushdns
dfsutil /pktflush
dfsutil /spcflush
The fix
Fix the layer the checks pointed to:
- No domain controller reached (step 1 failed): a network or domain controller fault. Fix that first; it is the first failure point on Microsoft's list.
- No referral returned (step 2, no entry): check the DFS Namespace service on the domain controllers, Active Directory replication, and the PDC emulator (step 5).
- Referral but no active target (step 2, no ACTIVE): fix the connection to the namespace servers (step 3), or the name resolution that points the client at them (step 4).
- Names resolve to the wrong address: correct the DNS or WINS records. In a network without WINS, Microsoft's page points to its guidance on configuring DFS to use fully qualified domain names in referrals.
- Client in a site with no targets and insite set: this follows from Microsoft's description of the insite option: the namespace needs a target in the client's site, the client needs to be mapped to the right site in Active Directory, or the insite setting needs to change. The site lookup in step 5 shows which applies.
- Referral request blocked (step 6): Microsoft says to check that Windows Firewall or another security product is not blocking it, and that Active Directory is working on the namespace server.
- Referral fine, file server fails: the problem is now the file server connection, which Microsoft says is ordinary SMB troubleshooting.
After a fix, flush the client caches (the four commands above) so the client asks again instead of using an old referral.
How to confirm the fix
dfsutil /pktinfoshows the namespace with a target markedACTIVE.- The DFS path opens from the client, and from a client in each office site.
repadmin /showreplshows no inbound replication failures.
What to watch afterwards
- Active Directory replication. Namespace changes depend on it, according to Microsoft's page.
- New offices or subnets. Microsoft's page says namespace servers work out the client's site from its IP address. It follows that a subnet missing from Active Directory Sites and Services can stop insite referrals.
- DFS errors in the System event log on the namespace servers.
Read next
Related articles you may want next.
- Backup & RecoveryRecovering a DFS namespace: what to back up, and where the configuration actually livesLocate DFS namespace configuration across Active Directory, server registry and shares, and plan recovery with system state and namespace exports.Read article
- Backup & RecoveryRestoring files into a DFS Replication folder without surprisesPlan DFS Replication file recovery around conflicts, replicated deletions, preserved files and supported member recovery methods.Read article
- TroubleshootingSystem error 53 "The network path was not found": name, port 445 or the Server serviceSystem error 53 means the client could not reach the share. Check the server's name, TCP port 445, the Server service and the firewall at the other end, and the client's own TCP/IP NetBIOS Helper service. Prove each one in turn.Read article
Risks and limits
- Flushing the referral and name caches makes the client request names and referrals again over the network, as Microsoft notes. The flush commands are run on the client.
- Microsoft's access-failures page dates from Windows Server 2003 (originally KB 975440). It is still listed for supported Windows Server versions, but its
dfsutilexamples use the older parameter style. Checkdfsutil cache /?on your own server. - If the DFS path was lost entirely, for example after a namespace server was removed, that is a recovery job, not an access fault, with its own steps.
Sources
- Microsoft Learn, "Troubleshoot Distributed File System Namespace access failures in Windows", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/dfsn-access-failures
- Microsoft Learn, "DFS Namespace troubleshooting guidance", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-dfs-namespace-guidance
- Microsoft Learn, "DFS Namespaces overview", last updated 21 May 2025: https://learn.microsoft.com/en-us/windows-server/storage/dfs-namespaces/dfs-overview
- Microsoft Learn, "dfsutil", last updated 1 November 2024: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/dfsutil
Next step
A DFS path that won't open is usually a referral problem, and the referral cache shows where it stopped. NetLeverage has looked after business servers since 2002. If your namespace still won't open, talk to us through managed support with the dfsutil /pktinfo and /spcinfo output from an affected computer.
This article was originally published on .