I just upgraded all of my DC's from 2000-SP4 to 2003-SP1. In the process of the upgrade, I moved all of the FSMO roles (all except infrastructure) and authoritative DNS to a new server. Everything appears to be working properly, but I'm seeing the following DNS error repeat on this new DC. It appears to be having issues resolving its own machine name.
Source: NTDS Replication
Category: DS RPC Client
Event ID: 1960
User: NT AUTHORITY\ANONYMOUS USER
Internal Event: The following domain controller received an exception from a remote procedure call (RPC) connection. The operation may have failed.
Process ID 764
Reported error information:
The RPC Server is unavailable (1722)
Extended error information
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond (10060).
Any ideas? The RPC service is running on the server. Replication is running without error to the other DC's. Name resolution is working properly. BUT, since it is having issues with its own name, I don't want to ignore it.