Guest jawdoc Posted April 1, 2008 Posted April 1, 2008 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.
Guest jawdoc Posted April 3, 2008 Posted April 3, 2008 Re: A domain controller for the domain.... On Apr 1, 5:34 pm, jawdoc <drbro...@msoms.com> 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!
Guest Meinolf Weber Posted April 3, 2008 Posted April 3, 2008 Re: A domain controller for the domain.... 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...@msoms.com> 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!
Guest jawdoc Posted April 5, 2008 Posted April 5, 2008 Re: A domain controller for the domain.... On Apr 3, 4:12 pm, Meinolf Weber <meiweb(nospam)@gmx.de> wrote: > 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...@msoms.com> 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!- Hide quoted text - > > - Show quoted text - Thanks Meinolf for the response. After I read that I am a little confused if the registry edit is to the workstation, server or both? Have you had this work for you? If so, which machine did you do the registry edit on? Thanks
Recommended Posts