establish 2-way trust between two physically separated AD domains

Hello,

I need to establish a two-way trust between 2 physically separated AD domains - when I run through the "create new trust" wizard and supply either side with the other side's domain name, the wizard will error out and tell me it cannot find the supplied Windows Domain.

Additional details:
there is a site to site VPN in place that enables connectivity between the two sites and hosts on either side are pingable and accessible by IP - general high level infrastructure concerns are pretty solid and there is no firewalling of the traffic between the two sites.

One domain controller on one side can ping the other by name, the other one cannot by name, but can by IP

The AD on one side has a domain functional level of 2003 / forest 2008

The AD on the other side has a domain functional level of 2000 / forest is 2003

One AD has a ".us" ending to its' internal NETBios domain name, the other has a ".com" ending to its' internal NETBios domain name :-/


What is the best way to configure DNS in this situation? Obviously I would like to avoid an internal domain re-name on the one that ends in ".com"

Will the functional levels need to be raised to support the trust?



The goal here is very simply to be able to login to computers at one site with credentials from the other site.

Thank you!
Bill WelshAsked:
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.

Mike KlineCommented:
You can use conditional forwarders for name resolution    (stub zones and secondary zones would work too) http://technet.microsoft.com/en-us/library/ee307976(v=ws.10).aspx

So you set a conditional forwarder in domain A to point to domain B and vice versa.

Also make sure your ports are open

http://support.microsoft.com/kb/179442

Thankjs

Mike
0

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
Bill WelshAuthor Commented:
The newly created conditional forwarders at both sites fixed this problem beautifully, much appreciated!
0
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
Windows Server 2003

From novice to tech pro — start learning today.

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.