johnny181
asked on
workstation joining the domain issues
We have run into this a number of times and I am not sure where to locate the issue. We have an image of our laptops done by Acronis software. After we put the image back onto the laptop, we leave it unplugged, change the name, restart and then join the domain. This is where we have issues. It keeps giving us an error message;
~~~~~~~~~~~~~~
The domain name "INTERNALDOMAIN" 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 an Active Directory Domain Controller (AD DC) for domain " INTERNALDOMAIN ":
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. INTERNALDOMAIN
Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
10.1.1.15
10.1.1.17
- One or more of the following zones do not include delegation to its child zone:
INTERNALDOMAIN
. (the root zone)
~~~~~~~~~~~~~~~~
To resolve this, I statically set the current IP address, mask and gateway and then I am able to attach the machine to the domain. Once I do that, I restart it, log into the domain, remove the static IP info and everything works fine after that. 15 and 17 are our DNS servers.
So what is our problem and how do I fix it?
~~~~~~~~~~~~~~
The domain name "INTERNALDOMAIN" 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 an Active Directory Domain Controller (AD DC) for domain " INTERNALDOMAIN ":
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. INTERNALDOMAIN
Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
10.1.1.15
10.1.1.17
- One or more of the following zones do not include delegation to its child zone:
INTERNALDOMAIN
. (the root zone)
~~~~~~~~~~~~~~~~
To resolve this, I statically set the current IP address, mask and gateway and then I am able to attach the machine to the domain. Once I do that, I restart it, log into the domain, remove the static IP info and everything works fine after that. 15 and 17 are our DNS servers.
So what is our problem and how do I fix it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
- doe Acronis software run sysprep or changes SID after deploying image? this might not be relevant to your issue but I thought it's worth to ask.
- After you put the image back onto the laptop, what is the IP address configurations of that image or laptop, is it static or configured to get IP from DHCP? does your dhcp provide correct IP configurations to these newly deployed images?
- we leave it unplugged, change the name, restart and then join the domain.
this does not seems to be a standard way of deploying images, most of these tasks are taken care by sysprep, you might want to review your deployment process.
overall, this seems to be the issue related to your P/Network configurations once image is deployed.