Re: A domain controller for the domain....

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

Hello jawdoc,

Single label domains should be avoided:
http://support.microsoft.com/kb/300684

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

On Apr 1, 5:34 pm, jawdoc <drbro...@xxxxxxxxx> wrote:

Hello
I have an issue I need help with. Adding a new XP pro workstation to
an existing domain "local" with one DC Windows 2000 server.
New workstation is named "consult3"
I get an error "A domain controller for the domain local could not be
contacted..."
I can ping the workstation by ip and name from server and I can ping
the server by both from the workstation.
I added the computer name manually to the AD as well as add the DNS
host manually to the DNS on the server.
IP address is set statically with DNS IP as the server.
Error details as follows: (where does this name come
rom>>_ldap._tcp.dc._msdcs.local) ?

The domain name local might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then
the following information can help you troubleshoot your DNS
configuration.

The following error occurred when DNS was queried for the service
location (SRV) resource record used to locate a domain controller for
domain local:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.local

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its
child zone:

local
. (the root zone)
For information about correcting this problem, click Help.

I have a little more info and really need help on this one.
I logged into the server and looked in AD for the full domain name.
Instead of the typical FQDN "something.local" the only thing that is
listed is "local" no period in front nor is there a second level name.
I assume this is the top level of the domain name and the second level
was never named. Is that possible? And if so what do I put in the
domain name for the workstation. ".local"?
So I am trying to figure out how this domain was named?
Any help is really appreciated!


.

Relevant Pages

  • Re: AD Newbie Questions
    ... Remember that though DNS and AD are ... You can copy the profile over, either doing a straight copy (get the ... > I've reviewed a few books on Server2K3, but before I> promote my server to a Domain Controller, there are still a few specifics> where I'd appreciate some guidance. ... I would install Studio.NET on the XP Pro workstation. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Basic Active Directory Questions
    ... Primary DC DNS service was disabled. ... Seondary DNS server has problem address with this DC ... Point your Member server and workstation to '10.81.20.19' as their prefered ...
    (microsoft.public.windows.server.active_directory)
  • Re: XP Client Connection Problem
    ... I'm not the most knowledgable about DNS but I ... > now consists of a single server and single workstation. ... > The server is Windows 2003 and is set up for DNS, ... This first client is also an XP ...
    (microsoft.public.windows.server.dns)
  • Re: Need help please, Having trouble finding/adding users for purpose of granting permissions or add
    ... the XP Pro computer to see if it reports any errors such as dns, dclist, ... server in the preferred dns server list of tcp/ip properties an shown via ... I also setup a simulation in my lab of an XP Pro ... > workstation and a single W2K Server running as the Domain controller. ...
    (microsoft.public.win2000.security)
  • Re: Event ID 5719: No Windows NT or Windows 2000 Domain Controller is available for domain .
    ... The workstation gets its networking information from DHCP that, in turn, ... the DNS has Enable Forwarders and the ... I don't believe the problem to be at the server end though. ... security settings) I messed with and that policy has since been removed. ...
    (microsoft.public.win2000.security)