Server 2003 PDC failed - but got a BDC

ramar said:
run some dcdiag tests and see what errors it throws up. dcdiag /test:dns
Click to expand...

Here's the results :

Code: 
Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Default-First-Site-Name\server03
      Starting test: Connectivity
         ......................... server03 passed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\server03

DNS Tests are running and not hung. Please wait a few minutes...
   
   Running partition tests on : Schema
   
   Running partition tests on : Configuration
   
   Running partition tests on : tollink
   
   Running enterprise tests on : tollink.co.za
      Starting test: DNS
         Test results for domain controllers:
            
            DC: tolsrv03.tollink.co.za
            Domain: tollink.co.za

                  
               TEST: Forwarders/Root hints (Forw)
                  Error: Forwarders list has invalid forwarder: 8.8.4.4 (<name unavailable>)
                  Error: Forwarders list has invalid forwarder: 8.8.8.8 (<name unavailable>)
                  Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4)
                  Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201)
                  Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12)
                  Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90)
                  Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10)
                  Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241)
                  Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53)
                  Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17)
                  Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30)
                  Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129)
                  Error: Root hints list has invalid root hint server: l.root-servers.net. (199.7.83.42)
                  Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33)
                  
               TEST: Dynamic update (Dyn)
                  Warning: Dynamic update is enabled on the zone but not secure ookfart.co.za.
         
         Summary of test results for DNS servers used by the above domain controllers:

            DNS server: 128.63.2.53 (h.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53
               
            DNS server: 128.8.10.90 (d.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90
               
            DNS server: 192.203.230.10 (e.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10
               
            DNS server: 192.228.79.201 (b.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.228.79.201
               
            DNS server: 192.33.4.12 (c.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12
               
            DNS server: 192.36.148.17 (i.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17
               
            DNS server: 192.5.5.241 (f.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241
               
            DNS server: 192.58.128.30 (j.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.58.128.30
               
            DNS server: 193.0.14.129 (k.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129
               
            DNS server: 198.41.0.4 (a.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4
               
            DNS server: 199.7.83.42 (l.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 199.7.83.42
               
            DNS server: 202.12.27.33 (m.root-servers.net.)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33
               
            DNS server: 8.8.4.4 (<name unavailable>)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 8.8.4.4
               
            DNS server: 8.8.8.8 (<name unavailable>)
               1 test failure on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 8.8.8.8
               
         Summary of DNS test results:
         
                                            Auth Basc Forw Del  Dyn  RReg Ext  
               ________________________________________________________________
            Domain: ookfart.co.za
               server03                     PASS PASS FAIL PASS WARN PASS n/a  
         
         ......................... ookfart.co.za failed test DNS

I must be missing something somewhere, but don't know where... :(

Time for a break and find a rogue DHCP server, and give its owner a good talking to :mad:
 
I got gautvol. But I succeeded :cool:

Here is what I did.

1. PDC had a systemstate backup, but it was 3 months old :o
Created a domain with the exact same name etc on a new server (fresh 2003 install).
I tried to do a system restore using this, but it showed me a .!.. when I wanted to log in after the restore. Probably out of tombstone.

2. Luckily I did a systemstate backup on the BDC before I did any promoting etc.
Reinstalled server2003 on the new server. Restored this systemstate from the BDC.
Then I followed the steps outlined in this :

http://usefulglyphs.wordpress.com/2009/11/13/how-to-backuprestore-a-windows-2003-domain-controller/

All seems well. DNS had a glitch initially, but now dcdiag /test:dns passes all tests. It do give a warning that dynamic update is enabled on the zone but not secure ookfart.co.za

Will leave it for an hour or so, then start looking at recovering Exchange :sick:



Lessons learnt so far :

1. Do start a regular systemstate backup.
2. Do have a BDC (if you're running server2003).
3. Make sure you can get a spare server post haste if things go south.
4. Be prepared to deal with :mad: Bosses
 
Last edited:
By the by, we're getting new server hardware soon.

I'm planning to virtualize most of the stuff wherever possible. We'll be using Server2008.

Also, we're looking at moving mail services to the cloud.
 
Electron1 said:
How is the recovery going?
Have you been successful?
Click to expand...

:mad:

Let's not even go there.

BDC to PDC conversion was not without its hiccups. Got that sorted in the end.

IT guys over the weekend got Exchange server (the original PDC) up and running. Exchange DB is borked totally. Have to start with a new Exchange Database. :(

But something in Exchange is corrupted, workstations can't connect/send/receive emails, even with POP3. OWA works, but can't connect. :rolleyes:

So now we'll have to get a new server, install 2k3, promote it to a BDC, install Exchange and see if it will work (as we can't get Exchange to install on the PDC). Something is not lekker on that machine.

In the meantime we'll have to host our emails via another company for 5 days or so... will switch over to gmail totally and get rid of the Exchange baggage.

Lovely IT tjol... :mad:
 
Damn sad I missed this thread,i've made miracles happen with recoveries like this

Had so many tips and tricks and suggestions to use but now a bit late :P

Have you got the exchange MDB files? Can you get teamviewer on the server box and a client? Wouldn't mind prodding at it

Technically speaking no such thing as a PDC/BDC since 2003,only AD servers and FSMO role master holders

Nothing wrong with exchange,just need your active directory forest covered
 
Exchange db and streaming file is out of sync.

We're up and running. This time the mail server's hosted outside the company, so we should continue to get mails if eishkom happens @ office.
 
This is probably every network administrator's nightmare, when AD and Exchange get tangled and go down. I learnt it's best not to have Exchange on the same box as a DC, too many things can go toast if the box collapses. Plus it really slows shut down/restart speed of the box.

I have a second DC running in a VM, just to make sure that Active Directory is replicated, so that even if the main DC goes down, the entire AD schema is safe. This includes the extensions Exchange made when it was installed.

Good luck, I hope things are on the road to full recovery now!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X