Server 2012 Domain Trusts

Hey All,

Currently, I have everything configured for domain trusts between three domains inside of my operational scope.

Domain A -> Domain B <- Domain C

Inside of Domain B, I have a terminal server that I want to allow access to from Domain A and C. I've managed to get this configured properly for Domain A... by adding a RDP Group from Domain A into the Remote Desktop "Select Users..." screen on the terminal server.
I'm able to see every user and object in Domain A from this point.

The same isn't true for Domain C. The weird thing is, if I go onto the Domain Controller for B, I can query and connect to C without issues.

I can also add users in C to the "Select Users..." portion of the domain controller.

The only section where this seems to fail is on the terminal server, and I'm not sure where to head next with this issue. Inside of the "Select Users..." Interface, I can change the location from Domain B to Domain C (so it knows it's there) but any user or group that should exist inside of Domain C will not populate and returns "Name Not Found".
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Sounds like a DNS. Please explain how DNS is configured for each domain.

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
troycslAuthor Commented:
I thought I had the DNS configured correctly because of the Trust on the DC, but the static mappings had public DNS mapped for the terminal server. I removed the public DNS, and flushed the cache, and we're back in business.
Good to hear!
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.