Re: DC Promo / DNS

From: msnews.microsoft.com (chrissaia_at_hotmail.com)
Date: 03/15/04 

Date: Mon, 15 Mar 2004 10:44:49 -0800

Thank you for the help! Answers to your questions below.

> Thanks for posting that info up front. I have a few questions...
>
>
> 1. Is sammys.lajolla your Active Directory domain name or should it have
> been sammys.lajolla.com ?

AD name is Sammys.lajolla (I'm wondering if this counts as a single word AD)

> 2. What is the spelling of the zone name in DNS?

lrgfs1.sammys.lajolla (this is on the DC)
lrgfs2.sammys.lajolla (on the memberserver i want to promote)

> 3. What is your primary DNS suffix on this machine?

Sammys.lajolla

> 4. Is Dynamic Updates set to at least "YES" in the zone properties?

Yes

> 5. Also what do you mean by this statement below?
> > 2 Dynamic forwarding is enabled

Sorry about the wording, I meant "Allow Dynamic updates" is set to "yes"

> 6. Can we also see an ipconfig /all?

Windows 2000 IP Configuration

 Host Name . . . . . . . . . . . . : lrgfs1
 Primary DNS Suffix . . . . . . . : sammys.lajolla
 Node Type . . . . . . . . . . . . : Hybrid

 IP Routing Enabled. . . . . . . . : No

 WINS Proxy Enabled. . . . . . . . : No

 DNS Suffix Search List. . . . . . : sammys.lajolla

Ethernet adapter Local Area Connection:

 Connection-specific DNS Suffix . : sammys.lajolla
 Description . . . . . . . . . . . : HP NC3163 Fast Ethernet NIC
 Physical Address. . . . . . . . . : 00-50-8B-F3-75-E1

 DHCP Enabled. . . . . . . . . . . : No

 IP Address. . . . . . . . . . . . : 10.0.0.41

 Subnet Mask . . . . . . . . . . . : 255.255.255.0

 Default Gateway . . . . . . . . . : 10.0.0.1

 DNS Servers . . . . . . . . . . . : 10.0.0.41
 Primary WINS Server . . . . . . . : 10.0.0.41

"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:u%237%23LcoCEHA.2800@tk2msftngp13.phx.gbl...
> In news:ugnazhnCEHA.1228@TK2MSFTNGP11.phx.gbl,
> Chris Saia <christophersaia@yahoo.com> posted their thoughts, then I
offered
> mine
> > I may have posted this message twice by accident. I'm just getting
> > setup on the newsgroups. My problem:
> >
> > I have two Win2K servers. One is the DC and DNS server. The other is
> > simply a member server. I want to promote the memberserver to
> > become a DC. My DNS setup is completely internal with fowarding to
> > our DSL's providers DNS. There is full comminication between the DC
> > and the member server. However when I try to run DC promo on the
> > member server I get the error message below.
> >
> > Other notes:
> >
> > 1.AD integrated zones setup on DC
> > 2 Dynamic forwarding is enabled
> > 3. The DNS on the member server is pointing to the IP of the DC.
> > 4. On the DC, I'm missing the four subzones from my foward zone
> > setup. I've tried "ipconfig /registerdns" to get those four subs
> > created but it didn't work
> > 5. I've restarted the net logon service several times.
> > 6. The Sysvol share exists.
> >
> > Error:
> >
> > "The wizard cannot gain access to the list of domains in the forest.
> > This condition may be caused by a DNS lookup problem. For information
> > about troubleshooting common DNS lookup problems, please see the
> > following Microsoft Web site:
> >
> > http://go.microsoft.com/fwlink/?LinkId=5171. The error is:
> >
> > The specified domain either does not exist or could not be contacted."
> >
> >
>
____________________________________________________________________________
> > I ran netdiag fix on the DC and below is the output.
> >
> >
> > ........................................
> >
> > Computer Name: LRGFS1
> > DNS Host Name: lrgfs1.sammys.lajolla
> > System info : Windows 2000 Server (Build 2195)
> > Processor : x86 Family 6 Model 8 Stepping 3, GenuineIntel
> > List of installed hotfixes :
> > KB823182
> > KB823559
> > KB824105
> > KB824141
> > KB824146
> > KB825119
> > KB826232
> > KB828028
> > KB828035
> > KB828749
> > KB830352
> > Q147222
> >
> >
> > Netcard queries test . . . . . . . : Passed
> >
> >
> >
> > Per interface results:
> >
> > Adapter : Local Area Connection
> >
> > Netcard queries test . . . : Passed
> >
> > Host Name. . . . . . . . . : lrgfs1.sammys.lajolla
> > IP Address . . . . . . . . : 10.0.0.41
> > Subnet Mask. . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . : 10.0.0.1
> > Primary WINS Server. . . . : 10.0.0.41
> > Dns Servers. . . . . . . . : 10.0.0.41
> >
> >
> > AutoConfiguration results. . . . . . : Passed
> >
> > Default gateway test . . . : Failed
> > No gateway reachable for this adapter. ( Gateway on DC is
> > IP of firewall (checkpoint) computer. Firewall cpu has two nics,one
> > nic has the IP which is the gateway on all machines in the network)
> > NetBT name test. . . . . . : Passed
> >
> > WINS service test. . . . . : Passed
> >
> >
> > Global results:
> >
> >
> > Domain membership test . . . . . . : Passed
> >
> >
> > NetBT transports test. . . . . . . : Passed
> > List of NetBt transports currently configured:
> > NetBT_Tcpip_{2DE3A1AE-9FCB-49C8-B49B-D7F1345DD029}
> > 1 NetBt transport currently configured.
> >
> >
> > Autonet address test . . . . . . . : Passed
> >
> >
> > IP loopback ping test. . . . . . . : Passed
> >
> >
> > Default gateway test . . . . . . . : Failed
> >
> > [FATAL] NO GATEWAYS ARE REACHABLE.
> > You have no connectivity to other network segments.
> > If you configured the IP protocol manually then
> > you need to add at least one valid gateway.
> >
> >
> > NetBT name test. . . . . . . . . . : Passed
> >
> >
> > Winsock test . . . . . . . . . . . : Passed
> >
> >
> > DNS test . . . . . . . . . . . . . : Failed
> > [FATAL] Failed to fix: DC DNS entry sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry _ldap._tcp.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _ldap._tcp.Default-First-Site-Name._sites.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _ldap._tcp.pdc._msdcs.sammys.lajolla. re-registeration on DNS server
> > '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _ldap._tcp.gc._msdcs.sammys.lajolla. re-registeration on DNS server
> > '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> >
>
_ldap._tcp.b5183208-4ee2-4bc1-9e79-f7c999b983ce.domains._msdcs.sammys.lajoll
> a.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry gc._msdcs.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > 226b9309-2184-455e-826e-05202de3ca9c._msdcs.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _kerberos._tcp.dc._msdcs.sammys.lajolla. re-registeration on DNS
> > server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _ldap._tcp.dc._msdcs.sammys.lajolla. re-registeration on DNS server
> > '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _kerberos._tcp.Default-First-Site-Name._sites.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry _gc._tcp.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > _gc._tcp.Default-First-Site-Name._sites.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry _kerberos._udp.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry _kpasswd._udp.sammys.lajolla.
> > re-registeration on DNS server '10.0.0.41' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Fix Failed: netdiag failed to re-register missing DNS
> > entries for this DC on DNS server '10.0.0.41'.
> > [FATAL] No DNS servers have the DNS records for this DC
> > registered.
> >
> >
> > Redir and Browser test . . . . . . : Passed
> > List of NetBt transports currently bound to the Redir
> > NetBT_Tcpip_{2DE3A1AE-9FCB-49C8-B49B-D7F1345DD029}
> > The redir is bound to 1 NetBt transport.
> >
> > List of NetBt transports currently bound to the browser
> > NetBT_Tcpip_{2DE3A1AE-9FCB-49C8-B49B-D7F1345DD029}
> > 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 . . . . . . . . . : Passed
> > IPSec policy service is active, but no policy is assigned.
> >
> >
> > The command completed successfully
> >
> > Thank You!
>
>
> Thanks for posting that info up front. I have a few questions...
>
>
> 1. Is sammys.lajolla your Active Directory domain name or should it have
> been sammys.lajolla.com ?
>
> 2. What is the spelling of the zone name in DNS?
>
> 3. What is your primary DNS suffix on this machine?
>
> 4. Is Dynamic Updates set to at least "YES" in the zone properties?
>
> 5. Also what do you mean by this statement below?
> > 2 Dynamic forwarding is enabled
>
> 6. Can we also see an ipconfig /all?
>
> Thanks!
>
>
> --
> Regards,
> Ace
>
> Please direct all replies to the newsgroup so all can benefit.
> This posting is provided "AS-IS" with no warranties and confers no
> rights.
>
> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
> Microsoft Windows MVP - Active Directory
> --
> =================================
>
>

Relevant Pages

  • Re: W2K3 DC not playing with member W2K3 Server
    ... to log on to the DC and intermittently loses connection to the DC. ... AD client MUST point to the DNS server set up for the AD domain ONLY. ... this member server is NOT pointing to the DNS server set up for the AD ...
    (microsoft.public.windows.server.setup)
  • Re: DC Promo / DNS
    ... Is sammys.lajolla your Active Directory domain name or should it have ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ... >> simply a member server. ...
    (microsoft.public.win2000.active_directory)
  • Re: Internet Connection issue out of the blue!
    ... Ethernet adapter Server Local Area Connection: ... Connection-specific DNS Suffix. ... >>information obtained from Active Directory for this zone and is unable to ...
    (microsoft.public.windows.server.sbs)
  • Re: Internet Connection issue out of the blue!
    ... You have a foreign DNS suffix in the search list that shouldn't be there. ... > Ethernet adapter Server Local Area Connection: ... >>>information obtained from Active Directory for this zone and is unable ... >>>The DNS server has encountered a critical error from the Active ...
    (microsoft.public.windows.server.sbs)
  • RE: Add domain user to local group, but where is the domain?
    ... no problem with the connection ... Then I noticed that my computer was not in DNS. ... Thanks for letting me think in a different order. ... My computer is Win2003 server as a member server. ...
    (microsoft.public.windows.server.active_directory)