cannot remove a domain

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We insert a new w2k server into our LAN with Active directory installed on it.
The name for this new server was SERVITESA2, and the new domain name (child domain) was servicio.itesa.com.
This was made for experimental puposses only.
We decided to remove it from our LAN after we noticed that a WXP Pro workstation tried to be the master browser and get an event log MRxSMB in our main server.
Now that we allready remove SERVITESA2 from LAN, we still have that event log from time to time.
After making a "cleanup" of DNS and Netbios with ipconfig /flushdns and nbtstat -RR, the alarmas seem to go away, but after rebooting the main server, they come again.
We decided to review the register and clean all keys with "SERVITESA2" and "servicio.itesa.com" involved, reboot the server and the alarms become warnings with source MRxSMB.
In "Active directory sites and services" we still have the name of the removed server "SERVITESA2" with its NTDS settings.
and in the "Active directory users and computers" right clicking node itesa.com and "connect to domain", browse, we get the child domain "servicio.itesa.com".
If we try to delete SERVITESA2 from "Active directory sites and services we just get the answer "The DSA object cannot be deleted".
We allready try with Ntdsutil without success.
We dont know what else to do.
Can somebody help me ?
 
ntdsutil is the correct tool to use. You will need to follow these two KB's

http://support.microsoft.com/?id=216498
http://support.microsoft.com/?id=230306

itesagsc said:
We insert a new w2k server into our LAN with Active directory installed on it.
The name for this new server was SERVITESA2, and the new domain name
(child domain) was servicio.itesa.com.
This was made for experimental puposses only.
We decided to remove it from our LAN after we noticed that a WXP Pro
workstation tried to be the master browser and get an event log MRxSMB in
our main server.
Now that we allready remove SERVITESA2 from LAN, we still have that event log from time to time.
After making a "cleanup" of DNS and Netbios with ipconfig /flushdns and
nbtstat -RR, the alarmas seem to go away, but after rebooting the main
server, they come again.
We decided to review the register and clean all keys with "SERVITESA2" and
"servicio.itesa.com" involved, reboot the server and the alarms become
warnings with source MRxSMB.
In "Active directory sites and services" we still have the name of the
removed server "SERVITESA2" with its NTDS settings.
and in the "Active directory users and computers" right clicking node
itesa.com and "connect to domain", browse, we get the child domain
"servicio.itesa.com".
If we try to delete SERVITESA2 from "Active directory sites and services
we just get the answer "The DSA object cannot be deleted".
 
use ADSIEDIT
-----Original Message-----
We insert a new w2k server into our LAN with Active directory installed on it.
The name for this new server was SERVITESA2, and the new
domain name (child domain) was servicio.itesa.com.
This was made for experimental puposses only.
We decided to remove it from our LAN after we noticed
that a WXP Pro workstation tried to be the master browser
and get an event log MRxSMB in our main server.
Now that we allready remove SERVITESA2 from LAN, we still
have that event log from time to time.
After making a "cleanup" of DNS and Netbios with
ipconfig /flushdns and nbtstat -RR, the alarmas seem to go
away, but after rebooting the main server, they come again.
We decided to review the register and clean all keys
with "SERVITESA2" and "servicio.itesa.com" involved,
reboot the server and the alarms become warnings with
source MRxSMB.
In "Active directory sites and services" we still have
the name of the removed server "SERVITESA2" with its NTDS
settings.
and in the "Active directory users and computers" right
clicking node itesa.com and "connect to domain", browse,
we get the child domain "servicio.itesa.com".
If we try to delete SERVITESA2 from "Active directory
sites and services we just get the answer "The DSA object
cannot be deleted".
 
Back
Top