blotto99
asked on
DNS error -- server not resolving its own name?
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.
Type: Error
Source: NTDS Replication
Category: DS RPC Client
Event ID: 1960
User: NT AUTHORITY\ANONYMOUS USER
Computer: SERVER1
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:
Error Value
The RPC Server is unavailable (1722)
Domain Controller
cd90a204-44eb-99b0-aba6-b0
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).
Domain Controller
SERVER1
Additional Data
Internal ID
2f4e888
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.
Type: Error
Source: NTDS Replication
Category: DS RPC Client
Event ID: 1960
User: NT AUTHORITY\ANONYMOUS USER
Computer: SERVER1
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:
Error Value
The RPC Server is unavailable (1722)
Domain Controller
cd90a204-44eb-99b0-aba6-b0
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).
Domain Controller
SERVER1
Additional Data
Internal ID
2f4e888
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You said you moved DNS? Did you change the DNS search order so the DC can find the new DNS server?
ASKER
The errors went away and have not returned after no changes.