Background info: MPLS connection Static IP assigned Extra nic disabled (I have not installed the teaming app at this point) DNS pointing to main office for primary DNS I can ping DC's at all locations After entering single label domain and account credentials...... I get this message. The domain name <DOMAIN> 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.DNS was successfully queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain <DOMAIN>: The query was for the SRV record for _ldap._tcp.dc._msdcs.<domain> The following AD DCs were identified by the query: dc1.boc dc2.boc dc3.boc dc4.boc dc5.boc dc6.boc dc7.boc dc8.boc dc9.boc dc10.boc Common causes of this error include: - Host (A) records that map the name of the AD DCs to its IP addresses are missing or contain incorrect addresses. - Active Directory Domain Controllers registered in DNS are not connected to the network or are not running. For information about correcting this problem, click Help. Suggestions?

Hi, A workstation that is logging on to an active Directory domain queries DNS for SRV records in the general form. _Service._protocol.DnsDomainName _ldap._tcp.DnsDomainName When a client logs on or joins the network, the client must be able to locate a domain controller. The client sends a DNS lookup query to DNS to find domain controller,preferably in the client's own subnet. Therefore, clients find a domain controller by querying DNS for a record of the form: _LDAP._TCP.dc._msdcs.domainname After the client locates a domain controller, the client establishes communtication by using LDAP to gain access to active directory. Use the nltest /dsgetdc:domainname command to verify that a domain controller can be located for a specific domain. Use the nslookup tool to verify that DNS enteries are correctly registered in DNS. for example: nslookup ServerName.child_of_root_domain.root_domain.com nslookup guid._msdcs.root_domain.com if either of the commands does not succeed, use one of the following methods to register records with DNS. 1)To force host record registration "ipconfig /registerdns" 2)To force DC SRV records registration, stop and start the NetLogon Service. Sometimes IPv6 may also be producing issues. Kindly try disabling IPV6. Try running Netdiag /fix after disabling the IPv6. Regards, Rafic If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!

Hi, A workstation that is logging on to an active Directory domain queries DNS for SRV records in the general form. _Service._protocol.DnsDomainName _ldap._tcp.DnsDomainName When a client logs on or joins the network, the client must be able to locate a domain controller. The client sends a DNS lookup query to DNS to find domain controller,preferably in the client's own subnet. Therefore, clients find a domain controller by querying DNS for a record of the form: _LDAP._TCP.dc._msdcs.domainname After the client locates a domain controller, the client establishes communtication by using LDAP to gain access to active directory. Use the nltest /dsgetdc:domainname command to verify that a domain controller can be located for a specific domain. Use the nslookup tool to verify that DNS enteries are correctly registered in DNS. for example: nslookup ServerName.child_of_root_domain.root_domain.com nslookup guid._msdcs.root_domain.com if either of the commands does not succeed, use one of the following methods to register records with DNS. 1)To force host record registration "ipconfig /registerdns" 2)To force DC SRV records registration, stop and start the NetLogon Service. Sometimes IPv6 may also be producing issues. Kindly try disabling IPV6. Try running Netdiag /fix after disabling the IPv6. Regards, Rafic If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!

Thanks! I found simular info on Petri but I couldn't join the domain from the branch office. I had to take the server back to the main office and DCPROMO the box there and place the box in the correct container. Then cleanup old dns entries after returning to the branch. Thanks again!

Thanks! I found simular info on Petri but I couldn't join the domain from the branch office. I had to take the server back to the main office and DCPROMO the box there and place the box in the correct container. Then cleanup old dns entries after returning to the branch. Thanks again!