"Unjoin a domain NT4"

  • Thread starter Thread starter Jörgen
  • Start date Start date
J

Jörgen

(Sorry for posting this in a Win2K ng but i have a small emergency)

Hi!

I have an OLD windows NT 4 machine in my domain that I've "forgotten" about
so I deleted the trust to that domain and removed the PDC for that domain.
When I try to remove the server that was in the old domain it says: "Unable
to connect to the domain controller for this domain. Have your administrator
check your computer account." How do I change the domain for this server
without the OLD PDC. The new domain is a Win 2K AD doamin in native mode.

Thanx

/Jörgen
Sweden
 
yes it is. And if I try to demote it it says "Cannot find a domain
controller for this doamin". Is there a way to make a "brutal" demote???

My NT knowledge is obviously to weak in this matter. Thank good for w2k! : )

Tack på förhand!

Jörgen
 
NT4.0 was before my time.

How ever I suppose you have to promote your particular BDC to become PDC and
then demote the domain and ujoin the particular server as any Domain
Controller to make it a standalone server. I think this can be done in the
tool Server Manager.

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1
 
NT4.0 was before my time.

How ever I suppose you have to promote your particular BDC to become PDC and
then demote the domain and ujoin the particular server as any Domain
Controller to make it a standalone server. I think this can be done in the
tool Server Manager.
Click to expand...
Chris, you can't demote an NT4 server. I would promote it to PDC, as
you suggest then set up trusts between its Domain and the Win2K
Domain. Then transfer any services to the Win2K domain. If this is the
only NT server in its Domain, it can then just be removed, and rebuilt
into the Win2K Domain if it is still required.

Cheers,

Cliff

(MVP)
 
I removed the entire server/Domain and replaced it with a DC for the new
domain instead. Easier than troubleshooting a WinNT problem. Thanks for all
your help...
 
Back
Top