Problems using DFS accross a Forest Trust

I have two Windows 2003 AD domains with a forest-level trust established between them. DNS forwarding has been configured properly and resource access (\\\share works properly between the two forests.

I want to have users in Forest1 access a DFS (domain root) that is located in forest2. The actual shares are located within forest2. When users browse to \\\shared (DFS root) they recieve the following error:

"Configuration information could not be read from the domain controller, either because machine is unavailable, or access has been denied."

If the same user attempts to access the actual share via \\\shared they are able to access the files correctly, just not through the DFS root.Rights are assigned in forest2 via DLG (Domain Local Group) which includes members from forest1.

Any help would be greatly appreciated
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

maddenjcAuthor Commented:
I figured out what was causing this issue. I was receiving this error due to a name resolution issue. The default funtionality for DFS is to use NetBIOS names in the response to clients. The clients in the other name does not use WINS, only DNS. Since the DFS servers were only issuing \\servername instead of \\ the resolution would fail giving me the error above.

There are a couple of solutions to this type of problem, but we ended up pushing a GPO to all workstaions in forest1 to configure DNS Suffix Search orders and everything has been working well. I will note that there is a registry key that can be put on the DFS servers to configure it to use DNS FQDN's; however, for domain-based DFS roots it requres you to export all links and recreate your roots  and then import your links with modified FQDN addresses...  We choose the DNS suffix route instead for now...   :)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.