Re: Unable to create an additional DC using dcpromo at remote site

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Dmitry Korolyov [MVP] (d__k_at_removethispart.mail.ru)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 18:05:03 +0400

You are using single-label domain name for your root domain. W2k3 and W2k
SP4 + need additional configuration for working with single-label domain
names. Check KB300684 for more information. 

-- 
Dmitry Korolyov [d__k@removethispart.mail.ru]
MVP: Windows Server - Active Directory
  <Ray> wrote in message news:eVMqjtRTEHA.3140@tk2msftngp13.phx.gbl...
  We have one domain and 3 sites, all of which have been setup and defined
in
  sites and services.
  we are attempting to setup an additinal dc at the 3rd remote (the other 2
  sites work fine).
  The proposed Dc at the remote site is currently in the W2k3 domain.
  a 2mb vpn link is the connection between both sites
  We can ping the root dc, dns, wins servers at the central site from the
  remote site by netbios name and ipaddress. i can only ping the root dc by
  FQDN is i add its entry in the host file, but when we run dcpromo we
receive
  the following error:
  The following error occurred when DNS was queried for the service location
  (SRV) resource record used to locate a domain controller for domain
health1:
  The error was: "This operation returned because the timeout period
expired."
  (error code 0x000005B4 ERROR_TIMEOUT)
  The query was for the SRV record for _ldap._tcp.dc._msdcs.health1
  The DNS servers used by this computer for name resolution are not
  responding. This computer is configured to use DNS servers with the
  following IP addresses:
  10.1.20.1
  Verify that this computer is connected to the network, that these are the
  correct DNS server IP addresses, and that at least one of the DNS servers
is
  running.
  For more information on how to correct this problem, click Help.
  Any ideas would be well appreciated
  Ray

Relevant Pages

  • Re: DHCP Problem causing ip to be 169.X.X.X and not 192.168.X.X
    ... > their configuration to limit the number of clients they will serve DHCP to. ... My linksys router is set to 50. ... Did that and my virus checker, still no ip address from DHCP on the linksys. ... and use what it is using for DNS servers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Question re: DNS forwarding best practices
    ... > Lets say you have a company with a root AD domain, ... > in all domains are DNS servers, ... while the child domains have DC's spread across ... Correct it won't work for the Win2k boxes ...
    (microsoft.public.windows.server.dns)
  • Re: strange dns client errors
    ... Client IP configuration: ... There are no forwarders configured on both DNS Servers ... There are three correctly configured reverse lookup zones for the networks ... - ICS was never configured on the network ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP Problem causing ip to be 169.X.X.X and not 192.168.X.X
    ... their configuration to limit the number of clients they will serve DHCP to. ... If your router was set up by your ISP, they may have set this to just the ... and use what it is using for DNS servers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Actiontec GT704 and DNS
    ... I have found that if I set up the router in DHCP configuration, ... IP address and the local ISP DNS server IP address rather than the IP ... DNS servers that are not associated with your ISP. ... open up a command prompt and issue the command "IPCONFIG /renew" ...
    (comp.dcom.xdsl)