Trouble Upgrading PDC / BDC to Windows Server 2003

[Will.Spencer]

Originally Posted by aamir

Hi.. This is Aamir From Karachi, Pakistan. I,m having a problem with my PDC, It was all working fine. Windows 2000 Server was installed on my PDC and BDC. First i upgraded PDC to Windows Server 2003 and then BDC to Windows Server 2003. But now the problem is that my PDC can ping other computer and other computer can't ping the PDC even BDC can't. What should i do.

Originally Posted by aamir

one of the error came in Directory Service Event is.

vent Type: Error
Event Source: NTDS Replication
Event Category: (22)
Event ID: 2087
Date: 11/23/2006
Time: 1:01:13 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: AQUATECH
Description:
Active Directory could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.

Source domain controller:
aquatech-bak
Failing DNS host name:
2ecad2eb-3c44-4e98-90fa-283c810e66a4._msdcs.aquatec.com

NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1:

Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagno stics\22 DS RPC Client

User Action:

1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.

2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".

3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns

dcdiag /test:dns

4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:

dcdiag /test:dns

5) For further analysis of DNS error failures see KB 824449:
http://support.microsoft.com/?kbid=824449

Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type was found.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Can you ping the PDC by it's IP address?

Are your PDC and your BDC also your DNS servers?

What error messages do you see if you use the `nslookup` command?