On a computer that is running Windows XP or Window Server 2003, when you try to access to a Domain-based Distributed File System Namespace (DFSN), you receive the following error message:
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.
The connection may fail because of any of the following reasons:
- Failure to connect to a domain controller to obtain a DFSN namespace referral
- Failure to connect to a DFSN server
- Failure of the DFSN server to provide a folder referral
ConnectivityIn this article, "connectivity" refers to the client's ability to contact a domain controller or a DFSN server. If a client cannot complete a network connection to a domain controller or to a DFSN server, the DFSN request fails.
You can use the following tests to verify connectivity.
Determine whether the client was able to connect to a domain controller for domain information by using the DFSUtil.exe /spcinfo command. The output of this command describes the trusted domains and their domain controllers that are discovered by the client through DFSN referral queries. This is known as the "Domain Cache."
In the following example, both the DNS domain name "contoso.com" and the NetBIOS domain name "CONTOSO" are discovered by the client. Two domain controllers were identified for the domain name "CONTOSO": 2003server2 and 2003server1. If the client accesses the DNS name "contoso.com" in a request, the entries are displayed under the "contoso.com" entry.
- start \\192.168.1.11
- net view \\192.168.1.11
If the connection is successful, determine whether a valid DFSN referral is returned to the client after it accesses the namespace. You can do this by viewing the referral cache (also known as the PKT cache) by using the DFSUtil.exe /pktinfo command.
The following output details the expected entries within the client's referral cache after the client accesses the DFSN path "\\contoso.com\dfsroot\link." The root has two targets ("rootserver1" and "rootserver2"). The link has a single target ("fileserver").
Expires in 300 seconds
UseCount: 0 Type:0x81 ( REFERRAL_SVC DFS )
0:[\ROOTSERVER1\dfsshare] State:0x119 ( ACTIVE )
1:[\ROOTSERVER2\dfsshare] State:0x09 ( )
Expires in 1800 seconds
UseCount: 0 Type:0x1 ( DFS )
0:[\fileserver\data] State:0x131 ( ACTIVE )
If you see an entry for the namespace (that is, "\contoso.com\dfsroot"), the entry proves that the client was able to contact a domain controller, but then did not reach any DFSN namespace targets. If not any of the namespace targets that are listed are designated as "ACTIVE," that indicates that all targets were unreachable.
Try to access to each namespace server by using IP addresses. For this test, you must specify only the IP address of the server, and you must not include the namespace share (that is, "net view \\192.168.1.11" but not "net view \\192.168.1.11\dfsroot"). Otherwise, you may unknowingly be referred to another DFS root server. If this occurs, you will receive misleading results. Note any error messages that are reported during these actions.
You must investigate and resolve any failures of a domain controller or of DFS namespace server communications. For more information about TCP/IP networking details and about troubleshooting utilities, visit the following Microsoft Web site:
Name ResolutionClients must resolve the name of the DFS namespace and of any servers that are hosting the namespace. Review the output that was previously generated by the dfsutil /pktinfo and dfsutil /spcinfo commands. The server names that are listed must be resolved by the client to IP addresses.
You can use the following methods to verify proper name resolution functionality.
- WINS and NetBIOS names
NetBIOS name resolution failures may occur because name records are missing or because you received the wrong IP address for the name. To test this, try to access the domain controller by using only its NetBIOS computer name (that is, by using the command net view \\2003server1). Then, verify that the shares that are listed are those that are expected to be hosted by the server. As an administrator, you can view the client's NetBIOS name cache by using the nbtstat -c command to review all resolved names and their IP addresses. Consider the following example.Review the following documents to troubleshoot WINS failures:
NetBIOS Remote Cache Name Table
Name Type Host Address Life [sec]
2003server1 <00> UNIQUE 192.168.1.11 462Troubleshooting WINS servers
Troubleshooting WINS clients
- DNS Names
By default, DFSN stores NetBIOS names for root servers. DFSN can also be configured to use DNS names for environments without WINS servers. For more information, click the following article number to view the article in the Microsoft Knowledge Base:244380 How to configure DFS to use fully qualified domain names in referralsYou can view the client's DNS resolver cache to verify resolved DNS names. To do this, open a command prompt, and type the following command:ipconfig /displaydnsConsider the following example.Review the following documents to troubleshoot DNS failures:
Windows IP Configuration
Record Name . . . . . : 2003server1.contoso.com
Record Type . . . . . : 1
Time To Live . . . . : 882
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 192.168.1.11Troubleshooting DNS clients
Troubleshooting DNS servers
- Network capture
A network capture may help you diagnose a name resolution failure. Before you perform a capture, flush cached naming information on the client. If you do this, you will not expose any problems that may exist in the capture because cached referral data or names will not be requested again over the network. To flush the name caches, run the following commands in this order:
933741 Information about Network Monitor 3For more information about the network traffic that is observed between a client and a domain-based DFS environment, visit the following Microsoft Web site:
- nbtstat -RR
- ipconfig /flushdns
- dfsutil /pktflush
- dfsutil /spcflush
DFS and System ConfigurationEven when connectivity and name resolution are functioning correctly, DFS configuration problems may cause the error to occur on a client. DFS relies on up-to-date DFS configuration data, correctly configured service settings, and Active Directory site configuration.
First, verify that the DFS service is started on all domain controllers and on DFS namespace/root servers. If the service is started in all locations, make sure that no DFS-related errors are reported in the system event logs of the servers.
When an administrator makes a change to the domain-based namespace, the change is made on the Primary Domain Controller (PDC) emulator master. Domain controllers and DFS root servers periodically poll PDC for configuration information. If the PDC is unavailable, or if "Root Scalability Mode" is enabled, Active Directory replication latencies and failures may prevent servers from issuing correct referrals. For more information about "Root Scalability Mode," visit the following Microsoft Web site:repadmin.exe command. The required syntax for this command is as follows:
Review the status and time of the last successful replication to make sure that DFSN configuration changes have reached all domain controllers. You should investigate any failures that are reported for inbound replication to a DC.
DFSN configuration problems may also prevent access to the namespace. One common scenario in which this occurs is a client that belongs to a site that contains no namespace or folder targets. If the namespace is configured to issue referral targets only within the client's site (the "insite" option), DFSN will not provide a referral. To evaluate whether the "insite" option is configured on a namespace, opena a command prompt, and then type the following command:
- dfsutil /sitename:root_target_name
- dfsutil /sitename:client_ip_address
Distributed File System: Frequently Asked Questions
Updated namespace terminology:
ID do Artigo: 975440 - Última Revisão: 12/03/2010 - Revisão: 1