DC Cannot be reached, no logon

[fitfixer]

I have a small (70+) lan with 3 DC's on Server 2003, an Exchange 2003 box and clients on XP Pro,
Last week the primary DC failed, I was able to seize the FSMO roles and continue working with the other two, everything was fine for a few days then clients started reporting logon failures, not printing, no e-mail and generally no connectivity, there are lots of Jrnl_wrap_errors in the event log
now I cant even logon, I tried running DCPROMO on the rebuilt server and it reports that the domain cannot be contacted, If I try joining a workstation it reports a similar error "does not exist in DNS"
DNS seems to be OK and I can resolve a hostname using nslookup
Short of building a new domain how do I start resolving this?,
I would be grateful for and suggestions on how to start

FrankF
A+,Network+,MCSA

 

[ntinlin]

Are your secondary DC's Global Catalog's?

Neill

 

[fitfixer]

Thanks for the reply,
yes, both are GC's

This is what we get when we try joining a workstation;

DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain codubvec.local:

The query was for the SRV record for _ldap._tcp.dc._msdcs.codubvec.local

The following domain controllers were identified by the query:

cdvec2.codubvec.local
dr01.codubvec.local

Common causes of this error include:

- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or are not running.

For information about correcting this problem, click Help.
**********

both DC's are correctly identified here but cannot be contacted!!

I am looking at replication between the 2 DC's the sysvol folder seems to be overwritten at each replication,

Regards


FrankF
A+,Network+,MCSA

 

[acl03]

Have you tried, when adding a machine to the domain, fully qualifying the domain name with all dns suffixes?



Thanks,
Andrew