DC Problems

[Guest]

I have a windows 2000 server (Exchange2k3). It is the domain controller for
the network and it is also running Exchange 2003. Two days ago my users could
no longer login to the network or Exchange. There used to be another Windows
2000 server running on the network as a domain controller (optserver), but it
was removed from the network about a week ago. The server was never demoted
or removed from Active Directory. It was just shutdown and disconnected.

Since my users were unable to login to the domain, I plugged the old domain
controller back into the network. At that point the users were able to login
to the domain. However, There is a problem with replication between the two
servers.

The currnet server (exchange2k3) will not act as a domain controller and
since it is the holder of all of the FSMO roles, there are still lots of
problems with Exchange and policies and logons etc...

I also discovered that there was no sysvol share. I tried to reshare the
sysvol, but it didnt seem to help much.

At this point, I am lost. I'm not really sure what cased this problem or how
to resolve it. I did run a dc diag and found some dns errors. I looked at DNS
and all of the settings look ok to me.

Here is the DCDiag logfile of just the errors ( I figured pasting the whole
log would be too big to post here.
____________________________________________________________________
Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine exchange2k3, is a DC.
* Connecting to directory service on server exchange2k3.
* Collecting site info.
* Identifying all servers.
* Found 2 DC(s). Testing 2 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\EXCHANGE2K3
Starting test: Connectivity
* Active Directory LDAP Services Check
7b3db329-3a52-46e1-8734-de354095c091._msdcs.optinc.local's server
GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(7b3db329-3a52-46e1-8734-de354095c091._msdcs.optinc.local) couldn't
be

resolved, the server name (exchange2k3.optinc.local) resolved to the

IP address (10.0.0.6) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... EXCHANGE2K3 failed test Connectivity

Testing server: Default-First-Site-Name\OPTSERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
2dc6ddd4-191b-499e-a587-f7a3f43758d8._msdcs.optinc.local's server
GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(2dc6ddd4-191b-499e-a587-f7a3f43758d8._msdcs.optinc.local) couldn't
be

resolved, the server name (optserver.optinc.local) resolved to the IP

address (10.0.0.8) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... OPTSERVER failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\EXCHANGE2K3
Skipping all tests, because server EXCHANGE2K3 is
not responding to directory service requests

Testing server: Default-First-Site-Name\OPTSERVER
Skipping all tests, because server OPTSERVER is
not responding to directory service requests

Running enterprise tests on : optinc.local
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope

provided by the command line arguments provided.
......................... optinc.local passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
PDC Name: \\exchange2k3.optinc.local
Locator Flags: 0xe00001fd
Time Server Name: \\optserver.optinc.local
Locator Flags: 0xe00001fc
Preferred Time Server Name: \\optserver.optinc.local
Locator Flags: 0xe00001fc
KDC Name: \\optserver.optinc.local
Locator Flags: 0xe00001fc
......................... optinc.local failed test FsmoCheck
____________________________________________________________________

Hopefully someone can help me with this problem.
Thanks,
Doug

 

[Jmnts]

Hi
It seems that you're haing some problems with DNS records.
First check your dns configurations.
Run Netdiag /fix on pdc emulator.
Restart Netlogon service.

Be carefull if you're running Exchange on a GC.

 

[Guest]

I checked all of the DNS settings and they all look good. I also ran netdiag
/fix and I am still having the same problem. I am now thinking about deleting
the entire DNS zone file on this server and copy the zone file from the other
server. Will this work?

 

[Jmnts]

Do you have DNS AD integrated?
Did you check the pdc folder srv record on the _msdcs,PDC,tcp, check the
_ldap record.
Did you check _kerberos records, _ldap and _kpasswd srv records, are they
pointing to the right direction?


when you type netdom query fsmo (or pdc), what do you get?