Windows 2000 Domain with New 2003 DC hangs

Discussion in 'DNS Server' started by James, Jan 29, 2010.

  1. James

    James Guest

    Hey,

    I have a domain with 2 windows 2000 DC, running in Windows 2000 native mode.

    I recently ran forest prep and domain prep from CD2 of Windows 2k3 R2

    I then created a new w2k3 server, installed all updates and DNS.
    I ran dcpromo on it without error
    I have set its DNS to point to its own static IP

    Now when I reboot it, it hangs at Preparing network connections and logs
    events: 2088 & 5781


    If I change its DNS to point at a W2k DC with DNS, and put the alternative
    DNS to its own IP, it boots up much quicker and only logs event ID 4015

    Any suggestions?
     
    James, Jan 29, 2010
    #1
    1. Advertisements

  2. Is your DNS set as AD integrated?


    hth
    DDS
     
    Danny Sanders, Jan 29, 2010
    #2
    1. Advertisements

  3. James

    James Guest

    yes it is


     
    James, Jan 29, 2010
    #3
  4. James

    James Guest

    I should also add, the Windows 2000 Domain controllers/DNS servers boot up
    with out issue. Its only the new Windows 2003 DC/DNS server that has issues
     
    James, Jan 29, 2010
    #4
  5. Is the DNS zone replicated to the new DC?
    Are the SRV records of the new DC listed in the DNS zone?


    hth
    DDS
     
    Danny Sanders, Jan 29, 2010
    #5
  6. Meinolf Weber [MVP-DS], Jan 29, 2010
    #6
  7. James

    James Guest

    New server
    Windows IP Configuration

    Host Name . . . . . . . . . . . . : 2003DC
    Primary Dns Suffix . . . . . . . : domain.com
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : domain.com

    Ethernet adapter Local Area Connection 2:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network
    A
    pter
    Physical Address. . . . . . . . . : 00-15-5D-0A-72-10
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.50.19
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.50.30
    DNS Servers . . . . . . . . . . . : 192.168.50.7
    192.168.50.19

    Old Server

    Windows 2000 IP Configuration

    Host Name . . . . . . . . . . . . : 2000DC
    Primary DNS Suffix . . . . . . . : domain.com
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : domain.com

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel 21140 Based PCI Fast
    Ethernet
    Adapter
    Physical Address. . . . . . . . . : 00-B0-D0-AB-1B-47
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.50.7
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.50.30
    DNS Servers . . . . . . . . . . . : 192.168.50.7
     
    James, Jan 29, 2010
    #7
  8. Hello james,

    The second 2000 DC isn't DNS server also?

    If you have more then one server you should always use the other as secondary
    DNS and not only using itself.

    As Danny already asked, does the 2003 server show the forward/reverse lookup
    zone in the DNS management console? Also when promoting a new DC/DNS you
    should always configure it only to the existing DC/DNS until the complete
    replciation of AD and DNS is done, then reconfigure it to itself as preferred
    and the other DNS as secondary.

    For Windows server 2000 see also this article about pointing to other 2000
    DNS server as there is an existing problem:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;275278&id=kb;en-us;275278

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Jan 29, 2010
    #8
  9. James

    James Guest

    Hey

    Yes the second 2000 DC is a DNS server

    And yes, the 2003 server does show the zones ok in DNS
     
    James, Jan 29, 2010
    #9
  10. James

    James Guest

    Yes on the new server, there are SOA, NS, and A records for the new domain
    controller
     
    James, Jan 29, 2010
    #10
  11. Hello james,

    The slower startup belongs to the problem that the DNS server pointing to
    itself has to wait for AD to be started, as when using AD integrated zones,
    BUT as AD only can start when DNS is started you are here in a kind of circle.
    No AD, no DNS but no DNS also no AD and after a while it comes up.

    So choosing the way to point to a running DNS server is always quicker because
    it can resolve all names already.

    For 2088 from dns see also:
    http://technet.microsoft.com/en-us/library/cc787713(WS.10).aspx

    5781 from netlogon
    http://www.eventid.net/display.asp?eventid=5781&eventno=167&source=NETLOGON&phase=1

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Jan 29, 2010
    #11
  12. James

    James Guest

    makes sense
    I added another windows 2003 DC/DNS and now all errors are gone...
     
    James, Jan 29, 2010
    #12
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.