Discussion Locked

AD Domain to NT Domain over P2P

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running Win2K with Active Directory on a domain. I want to connect, over a P2P connection to an NT Domain at our corporate office. Are there problems with AD to NT communication? How should I go about this? Thanks for any input you may have.

5 replies

by kimyves

I have got the same problem with a BDC located in remote site. But first, make a wins static mapping record of your Windows 2000 Domain Server into NT domain server. Go to AD domain and Trust, perform a one way trust relationship with your NT doamin, do the same on NT server by eanbling trust relationship through policy (user manager menu) and test the trust from W2k domain server, and try to see if you can open users from W2k server under user manager of NT domain server , by choosing "selectdomain" under User function.
Thanks

by bobby gillette

To answer your question, no. There aren't any problems with AD-NT communication. You simply need to determine what level of functionality you want to provide.

You can either create static mappings in WINS for the domains, or you can use the #PRE#DOM method in LMHOSTS for your secure channel (this needs to be in place prior to setting up your trust relationships.

If you are going to administer the remote NT domain, you'll want to set your AD up as a trusted domain on the NT side, set your NT domain up as a trusting domain in AD. Vice versa if its the other way around.

If you're wanting to use pass-through authentication, you'll have to implement two-way trust relationships on both domains. Its a little tricky, when I get back I'll post some links detailing the process.

This discussion is closed to new replies.