[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1026
  • Last Modified:

Cannot connect to a win2k3 dns server through MMC

I was having some replication issues relating to dns so i ran "netdiag /fix".  I let it run for about 30 hours and then ended the task.  we have about 50 dns entries total most of which get propagated through dhcp so it really should not have taken that long.

I can now replicate between dc's just fine, but i cannot connect to the dns server through the dns MMC.

DNS starts and restarts just fine without throwing any flags or indicators that something is wrong.  
The log files dont suggest any issues.  
the server resolves to its name just fine when i ping it.
netdiag /fix runs now in a matter of seconds and does not report any issues.
the dns server is AD integrated

thanks for the help
NETDIAG /FIX -- Results
....................................
 
    Computer Name: Jarver3
    DNS Host Name: Jarver3.local.Jarver3J.org
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 2 Stepping 5, GenuineIntel
    List of installed hotfixes : 
        KB911564
        KB915800-v9
        KB921503
        KB925398_WMP64
        KB925876
        KB925902
        KB926122
        KB927891
        KB929123
        KB930178
        KB931768
        KB931784
        KB931836
        KB932168
        KB933360
        KB933566
        KB933729
        KB933854
        KB935839
        KB935840
        KB935966
        KB936021
        KB936357
        KB936782
        KB937143
        KB938127
        KB938127-IE7
        KB938464
        KB938759-v4
        KB939653
        KB941202
        KB941568
        KB941569
        KB941644
        KB941672
        KB941693
        KB942615
        KB942615-IE7
        KB942763
        KB942830
        KB942831
        KB942840
        KB943055
        KB943460
        KB943484
        KB943485
        KB943729
        KB944275
        KB944533-IE7
        KB944653
        KB945553
        KB946026
        KB947864-IE7
        KB948496
        KB948590
        KB948745
        KB948881
        KB949014
        KB950759-IE7
        KB950760
        KB950762
        KB950974
        KB951066
        KB951072-v2
        KB951698
        KB951746
        KB951748
        KB952068
        KB952069
        KB952954
        KB953155
        KB953838-IE7
        KB953839
        KB954211
        KB954600
        KB955069
        KB955839
        KB956390-IE7
        KB956391
        KB956802
        KB956803
        KB956841
        KB957095
        KB957097
        KB958215-IE7
        KB958644
        KB958687
        KB960714-IE7
        Q147222
 
 
Netcard queries test . . . . . . . : Passed
 
 
 
Per interface results:
 
    Adapter : Local Area Connection 10
 
        Netcard queries test . . . : Passed
 
        Host Name. . . . . . . . . : Jarver3
        IP Address . . . . . . . . : 10.1.1.44
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.1.1.30
        Dns Servers. . . . . . . . : 10.1.1.54
                                     216.136.95.2
                                     64.132.94.250
                                     10.1.1.54
 
 
        AutoConfiguration results. . . . . . : Passed
 
        Default gateway test . . . : Passed
 
        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
 
        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.
 
 
Global results:
 
 
Domain membership test . . . . . . : Passed
 
 
NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{69505E45-E3F1-41A5-BA19-CD9DC589467B}
    1 NetBt transport currently configured.
 
 
Autonet address test . . . . . . . : Passed
 
 
IP loopback ping test. . . . . . . : Passed
 
 
Default gateway test . . . . . . . : Passed
 
 
NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.
 
 
Winsock test . . . . . . . . . . . : Passed
 
 
DNS test . . . . . . . . . . . . . : Passed
    PASS - All the DNS entries for DC are registered on DNS server '10.1.1.54' and other DCs also have some of the names registered.
 
 
Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{69505E45-E3F1-41A5-BA19-CD9DC589467B}
    The redir is bound to 1 NetBt transport.
 
    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{69505E45-E3F1-41A5-BA19-CD9DC589467B}
    The browser is bound to 1 NetBt transport.
 
 
DC discovery test. . . . . . . . . : Passed
 
 
DC list test . . . . . . . . . . . : Passed
 
 
Trust relationship test. . . . . . : Skipped
 
 
Kerberos test. . . . . . . . . . . : Passed
 
 
LDAP test. . . . . . . . . . . . . : Passed
 
 
Bindings test. . . . . . . . . . . : Passed
 
 
WAN configuration test . . . . . . : Skipped
    No active remote access connections.
 
 
Modem diagnostics test . . . . . . : Passed
 
IP Security test . . . . . . . . . : Skipped
 
    Note: run "netsh ipsec dynamic show /?" for more detailed information
 
 
The command completed successfully

Open in new window

mmcdns.jpg
0
koffea
Asked:
koffea
  • 2
1 Solution
 
koffeaAuthor Commented:
forgot to mention this:

when i use NSLOOKUP - everything appears to resolve just fine

its like the dns server is running just fine in every possilbe way - i just cant connect to it via the MMC.
0
 
koffeaAuthor Commented:
fixed the issue - uggh been dealing with this for 5 days now.

some how the registry setting:
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
Value name: RpcProtocol

got set to 0  which = disable

here is a link to the technotes
http://technet.microsoft.com/en-us/library/cc740223.aspx


0
 
aces4all2008Commented:
Glad to see you worked out the problem with mmc.  Looking at the netdiag output I can see where some of the issues you were having with replication may have been coming from.

It looks like the network interface for JARVER3 is set to use both internal and outside DNS servers for name resolution.  If your DCs are on a private network you network adapters should be configured to use only internal DNS servers.  See http://support.microsoft.com/kb/300202 for how to set up dns correctly.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now