Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 759
  • Last Modified:

Unable to create trust relationship btwn 2 windows 2000 advanced server

HELP!

I am trying to get my trust relationship to work btwn my existing domain to a newly created one.

While on my current domain controller when i add the trust relationship of the new domain i get the following error:

The newdomainname cannot be contacted.  If this domain is a windows domain, the trust cannot be setup unitl the domain is contacted.  Click canecl and try again later.  If this is an interoperable non-windows Kerberos realm and you want to set up this side of the trust click ok.  

what's wierd is i dont get this msg on the newly created domain.  it just says something about cannnot verify or validate at this time.  another thing, while on the newdc, i can access my currentdc by typing  \\currentdc machine.  accessable only one way - kinda.

i'm checking out article #Q312003 and just added WINS but still nothing.
note1: when trying to ping the newdcname, it returns back w/a different ip than on the actual newdc.
note2:testing the newdc on a virtual server running vmware.

Thanks for any other pointers you may have.

ST
0
ststst
Asked:
ststst
  • 5
  • 3
1 Solution
 
_treySterCommented:
Windows 2000 relies on DNS heavily.  Check your DNS setup on BOTH servers and make sure there are entreis for both host names.
0
 
PakaCommented:
The problem could be in many places.  As treySter pointed out DNS is the main name resolution system for W2K.  Check and double check DNS to make sure there are no problems.  Your wrong IP could be a manually created A record in your zone.  After that, make sure you don't have any entries in your HOSTS and LMHOSTS files.  Finally, check your WINS to see what it has for registrations.  (Bring up WINS, search for records like the NetBIOS name of your servers (real and VMWare).
0
 
stststAuthor Commented:
Treyster

i tried adding the host to the currentdc's DNS and it defaults to newdc.currentdc.com.  is that the way its supposed to be?  Same issue on newdc.

ST
0
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

 
stststAuthor Commented:
Paka,

WIns on my currentdc shows the newdc w/the wrong ip address.  how can i clear/change the wins ip info?

ST
0
 
stststAuthor Commented:
Paka,
one other note, when i look in wins on the newdc, the currentdc does not show.

ST
0
 
_treySterCommented:
If they are two different domains then you need an additional forward lookup zone for the newdc on the currentdc's DNS.
0
 
stststAuthor Commented:
I'm assuming i would need to do on both domain/DNS? and also which option to choose, Active dir-integrated, standard primary, or std 2ndary?

thanks.

ST
0
 
stststAuthor Commented:
HEY HEY HEY!!  
Just added forward zone to both using AD integ and it got validated.

thanks so much for your help!!

ST
0
 
_treySterCommented:
Glad you got it! -_treySter
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now