Domain controller 2003 and 2008

I have a SBS 20003 server (my main server), and HAD a Win 2008 RC1 server.  The win 2008 server recently died and I cannot restore that server due to corrupt backup.

When both were running, I had run dcpromo on the server 2008 machine.  I had really only installed the server 2008 on that machine to allow simultaneous logins to a piece of software.  But I thought that as long as I had a second server, I might as well also make that server a domain controller, so in case my main server went down, I'd still be running ok (more or less).

Well the server 2008 died and I can;t restore it.  On the same day there were some power outages and the battery backup on the main server failed and it cut out a few times.  Later in the evening, I restarted the server properly and checked for bad sectors on HD.  There were none.

However, now my main sbs 2003 server when it boots up give the following error:  Windows cannot obtain the domain controller name for your computer network (the specified name either does not exist or could not be contacted.)

Does running DCPROMO on a second server demote the first one?  I did not think that was the case and can;t see why that would happen.

How do i see what server the sbs2003 machine is looking for the domain controller?

I have good backups off the SBS2003 from before the incident.  I suppose I can go into directory restore mode and restore from an old backup.  Do you think this is the best course of action?  Or do you recommend checking something else first?
colin911Asked:
Who is Participating?
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
i have solved the problem to colin remotely using Teamviewer session by deleting the additional died domain from active directory site and services , also remove the server from domain computers and usrers ->pointing to domain controller -> delete it , doing some clean up of metadata and seize active directory partitions using NTDSUTIL .. here is other way to remove additional domain using NTDSUTIL

http://www.petri.co.il/delete_failed_dcs_from_ad.htm

also remove the additional old domain from DNS entries its very important , and troubleshooting some issues in group policy.
0
 
NivleshCommented:
Does your SBS 2003 server finally start? If not then try to unplug all network cables and do a restart and see if that allows it to start.

Also, see if you can do a last known good config repair using the F8 key.

Once you are logged in, check to see what is the DNS settings on the server. Ensure that it is pointing to itself.
0
 
kcoectCommented:
Make sure your SBS server is looking at itself as its DNS server (127.0.0.1), once it's up, verify the FSMO roles are held by the SBS server (they should be as SBS will complain if the roles are transferred off it), and check to see if the SBS server is still a Global Catalog server.  

If the server is configured to use the 2008 (now down) server as it's DNS server, then it will never find any of the service records for Active Directory.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
Please refer below KB articles...

Event ID 1054 is logged in the Application log in Windows Server 2003 or in Windows XP Professional

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

Cannot connect to domain controller and cannot apply Group Policy with Gigabit Ethernet devices

http://support.microsoft.com/kb/326152
0
 
colin911Author Commented:
Thank you all for your responses.

Nivlesh.  The server starts and runs fine.  DNS points to itself.  

kcoect:  Not 127.0.0.1, but 192.168.0.2 which is it's statis IP address on the lan.  This has always been the case, even since before the 2008 server

Jordanmet:  I had seen those articles and they don;t seem to provide a solution for me.


If I run dcpromo on the 2003 server I get a message that the server is already the domain controller and so it can only provide steps to remove it.  How can it both be the domain controller and not know of the domain controller.
0
 
colin911Author Commented:
how do I check the FSMO roles and to see that it is still a global catalog server?
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
i think you need to use directory restore  :

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

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

to repair the problems is AD.
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
0
 
colin911Author Commented:
jordannet, none of those support articles refer to my problems though...

Are you thinking that if I follow kb263532 and start going trough the steps taht one of these may fix this problem for me?
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
your problem confuse me , how many server died? you said 2003 & 2008 , so what is main ? and how is death level? can simplify what you want to do?
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
i read it again , and i understood that you have only backup on NTBackup , i think you need to restore using directroy restore mode . .. here is very useful article :

http://technet.microsoft.com/en-us/library/bb727062.aspx

but am still thinking about worst case if the previous procedures doesn't work , how to restore system state.
0
 
colin911Author Commented:
sorry.

2008 is dead and unrecoverable.  SBS 2003 is booting fine.

When I boot 2003 though, my clients's network drives cannot connect unless I reconnect them manually.   I find the following error in event viewer of the 2003 server:  Windows cannot obtain the domain controller name for your computer network (the specified name either does not exist or could not be contacted.)

That leads me to believe that the 2008 server's death (which i had promoted to a domain controller) was the source of the problem.  However, I had never demoted the 2003 server.  So I don;t see how the lack off the 2008 server should break the directory.  yet every time I boot the 2003 server I get the same message.

Does this help?
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
not necessary its possible that DNS problem , anyway lets start work around :
1- open Domain Computers and Users then right click on the root and connect to the domain , determine the 2008 server by name first if its not work by IP .
2- if its shown that its not working , then you can announce that its died , here is also very simple you need to use NTDSUTIL to clean up metadata orphan domain or dead domain  :

http://technet.microsoft.com/en-us/library/cc736378(WS.10).aspx

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

for users who have disconnected Network drive , after cleaning up you can set auto connect using group policy , but lets work step-by-step.
0
 
colin911Author Commented:
i connect to the domain fine.

In the connect to domain window, my domain name domain.local is already in the window.  If I click ok, I get taken back to the active directory users and computers console
0
 
colin911Author Commented:
tried to do a screen capture but it made my server blue screen of death!  So rebooting now.
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
this because its additional domain , so you need to check replica , on domain controller go to start -> administrative tools -> active directory site and services -> browse sites -> Inter-Site Transports -> Servers -> your server name -> right click on NTDS settings -> all tasks -> check replication topology.

also i want to check on windows 2008 if netlogon service is running , sometimes its stopping for unknow reasons , if its started also restart it. i wish that you can get server 2008 back to work.
0
 
colin911Author Commented:
ok, while I am waiting for the server to reboot am I looking for anything in particular when I do this?  
this because its additional domain , so you need to check replica , on domain controller go to start -> administrative tools -> active directory site and services -> browse sites -> Inter-Site Transports -> Servers -> your server name -> right click on NTDS settings -> all tasks -> check replication topology.

I wish I could get the 2008 server running too!
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
i never heard that server reboot on Capture screen , i wish that is rebooting get the server back for work again  like arabic proverb say "the problems of some peoples are benefits to other people" , i mean capture screen problem possible to let your server back :-p , i hope so
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
your problem simple believe me , but as i told you check the 2008 service winlogon if its running or not?
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
you need to check the previous comment :
 administrative tools -> active directory site and services -> browse sites -> Inter-Site Transports -> Servers -> your server name -> right click on NTDS settings -> all tasks -> check replication topology.

on windows 2008 also
0
 
colin911Author Commented:
yeah, i was a bit surprised myself but it happened exactly as I was uploading.  Hoping that is not part of a bigger problem...

following your descriptions after check topology I get the message:

AD on domain controller server.domain.local has checked the replication topology. you will need to refresh the sires container to see any new or deleted container.
0
 
colin911Author Commented:
BTW, in your description, i had to go to the correction below:

administrative tools -> active directory site and services -> browse sites -> DEFAULT FIRST SITE NAME (not inter-site transposrts) -> Servers -> your server name -> right click on NTDS settings -> all tasks -> check replication topology.
0
 
colin911Author Commented:
also, the 2008 server is listed there in the server list.  should I be deleting it?
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
its normal message .. don't worry , if you can access your windows 2008 server using remote desktop , do the following to test connectivity , go to active directory users and computers on the domain (2003 server) , then create any temp user like "maen" , my name :p , and see if its found on the active directory computers and users on 2008 server and let me know
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
no don't delete anything , you must be careful. listen if you see that problem will not be solved , i can open remote session with you using teamviewer just go to my profile and there is my email exist , send me email or add me to messenger i will help you for free :-p , don't worry the top of my aim in the life is helping people only
0
 
colin911Author Commented:
your problem simple believe me , but as i told you check the 2008 service winlogon if its running or not?
not sure how to do this since the server is unrecoverable.

you need to check the previous comment :
 administrative tools -> active directory site and services -> browse sites -> Inter-Site Transports -> Servers -> your server name -> right click on NTDS settings -> all tasks -> check replication topology.

on windows 2008 also

Cheked replica on 2008 server and got the following message:  the following error occured during the attempt to contact the domain controller:  The RPC server is unavailable.
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
can you run this command on domain :

repadmin /showreps

and on windows 2008 check if netlogin service is running or not ...its very important , also on windows 2008 stop windows firewall and try
0
 
colin911Author Commented:
the 2008 server is completely broken and offline.  2008 no longer exists.  Can't do ANYTHING on that server.
0
 
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
you can not access it with Remote desktop???
0
 
colin911Author Commented:
no, the problem from the beginning is that the 2008 server is down and not recoverable.  sbs 2003 is up and running but seems to be confused as to who the domain controller is.
0
 
NivleshCommented:
Hi
Can you check if the dns server is running on your sbs 2003 server?

Also run dcdiag and report what errors it shows. Dcdiag is part of the windows 2003 resource kit. If you do not have the server cds then you might be able to download from microsoft. Do a google for dcdiag download
0
 
great_gentle_manCommented:
hey colin911

may i suggest that before you make nay changes to sbs 2003, if possible make a virtual machine of it, so may a have working sbs instance in-case you you run into a dead end.

and what happened to 2008 server, hardware failure or OS corruption, if your hdd is safe, with os working we might be in business.
0
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.

All Courses

From novice to tech pro — start learning today.