DFS Namespace not functioning in Parent/Child Domain

I set up a DFS namespace for file servers (both server 2008) in a network that I manage.  We will call it Child for ease at the moment.  We have a parent domain on top of that, we will call Parent.  Anyone in Child can access the namespace with no issues whatsoever.  We have a Remote Access Server (server 2003) at the Parent domain level that people can log into from the Child level.  They cannot, however, access the Child DFS namespace.

Little bit more background, there are also 3 other child domains under the 1 parent set up for different networks, so simply changing the network of the remote server is not a valid option.  I will eventually be creating DFS spaces at each of the other 3 domains as well, and they will all need to be accessible from the remote server but the other 3 respective child domains.

Error message that I receive is that it is not accessible.  Might not have permission to use the network resource.  Configuration information could not be read from the domain controller, either because the machine is unaavailable, or access has been denied.  

The account that I am using to test is an Enterprise Admin account at the Parent level (that can access it when I log into a Child computer with the same account), though the same message appears when I attempt to log into it with a Child user that has access on her Child level computer.

I have verified DNS connectivity.  I can access the domain through explorer and see all the shares, but I cannot open the folder that contains the DFS namespace shares.

I appreciate any assistance that you can provide.
LVL 1
Crossroads305Asked:
Who is Participating?
 
Crossroads305Connect With a Mentor Author Commented:
I was finally able to solve this myself.  I went into the Local Area Connection the server users, went to the TCP/IP v4 settings, and went to avanced.  Under the DNS section, I changed the DNS suffixes from parent domain to the list I created.  When I added the Child domain to the suffix list, DFS worked immediately.
0
 
Rob StoneCommented:
There are some steps to follow in this KB article.

http://support.microsoft.com/kb/975440/EN-US?wa=wsignin1.0
0
 
Crossroads305Author Commented:
I have gone through all of the steps in that article.  I can see the domain controller in Child, I can get to it by FQDN, and I can connect to the servers via the "start" command.  I mapped to the domain itself via FQDN (child.parent.org), and I can map by domain.  I attempt to access the space that way, and it gives me the same message.  I have set both the NTFS permissions and Sharing permissions to allow everyone (simply for testing purposes), and it is still not functioning.

Any assistance would be greatly appreciated.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Crossroads305Author Commented:
Another piece of this puzzle: I do have the individual locations configured in different sites in AD.  I have a virtual machine that is part of the Child domain in the physical location of the Parent domain: slightly more plain, the same physical site as the remote access server.  I can log in on the virtual machine and access the DFS space.
0
 
Crossroads305Author Commented:
A point of clarification as well, the virtual machine uses the same DNS servers as the remote access server.
0
 
Crossroads305Author Commented:
I was able to solve this myself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.