Can not manage remote DNS with dnsmgmt MMC

When trying to manage domain controller A's DNS with the dnsmgmt MMC on domain controller B I get the following:

     The server is unavailable. Would you like to add it anyway?

I can add it anyway and not be able to do anything. The DHCP MMC can manage a remote DC ok, but fails with the dnsmgmt.

Does anyone know what could cause this behavior?
Who is Participating?
dfxdeimosConnect With a Mentor Commented:
Ok, a value of 0x4 (4) restricts the DNS RPC interface to local procedure calls only. This allows for local management only.

Change it to 0x1 (1) and reboot the server.
Does it matter if you try to connect using the server name, the FQDN (server.domain.local), or the IP address?

Can you verify the value of the "RpcProtocol" key located in the following registry hive:

sounds like a firewall or port blocking issue
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

mike_lfcuAuthor Commented:
IP or FQDN returns:
    The server you tried to contact is not a Windows 2000 or Windows 2003 family DNS server...

RpcProtocol" key  value is    "4"
mike_lfcuAuthor Commented:
No firewall is configured.
mike_lfcuAuthor Commented:
Ahhhhhh! Thank you dfxdeimos! That is it.

I was now able to find  "How to disable remote administration of the DNS Server service in Windows Server 2003 and in Windows 2000 Server"

You get da points!
Cool, glad that worked for you.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.