DNS Management issues seeing other DNS servers

Hello,
I currently have 4 DNS servers in my office. I'm having an issue where I can see some, but not all , of the other DNS server from the DNS Manager console from each machine. But there is no logical pattern.

This table attempts to illustrate what I'm talking about. The table shows, from each server (vertical letters) what other server can be seen from the DNS Management console of that machine in a Yes / No fashion.

All machines are Windows 2003 Domain Controller machines with at least SP1. Server B and D are SP2. Dashes means the computer itself for which each can obviously see.

Server A B C D
A - N Y Y
B N - Y Y
C N N - Y
D N N N -

To summarize in case the table doesn't come across clearly formatted:
Server A can successfully only add servers C & D to its DNS Manager window.
Server B can successfully only add servers C & D to its DNS Manager window.
Server C can successfully only add server D to its DNS Manager window.
Server D can NOT successfully add any servers to its DNS Manager window.

When I write that the machine can not see the remote machine, I mean that if, inside the DNS management window, if I right click on the DNS text and click on Connect to DNS server, select connect to this server, it will come back as "The Server Is Unavailable". If I add it anyway, it will list the server with a red X. If I then click on the server with the red X it expands to show the event log and I can see the event log of the server it says it cannot connect to. The event logs are very clean with no errors or warnings.

From each DNS Server machine, I can open a nslookup session and query each
of the servers that the DNS management tool says it can't connect to without error. Each machine can ping each other machine. I can telnet from each machine to each other machine.

Everything seems fine but the DNS manager just can't see any/all of the other machines - just some.

Any ideas of what could be wrong?

Thanks
Jim


.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)