CCUITAdmin
asked on
Can't join computers to domain using the short name
We have a single domain forest and have always been able to add computers with either the full domain name "contoso.priv" or the short name (pre-Windows 2000 name) "CTS". Today, I attempted to add a computer using the short name and it did not work.
Info that might be relevant:
We recently demoted/retired our last server 2003 DC
Domain Functional level is still 2003
While the demotion went very smooth for the most part, we had to clean up a lot entries in the dns module for our old DC.
I'm happy to provide more info if anyone needs it Any help would be greatly appreciated.
Info that might be relevant:
We recently demoted/retired our last server 2003 DC
Domain Functional level is still 2003
While the demotion went very smooth for the most part, we had to clean up a lot entries in the dns module for our old DC.
I'm happy to provide more info if anyone needs it Any help would be greatly appreciated.
ASKER
McKnife
Thanks for the input. I was able to join a different machine. I examined the firewall which I currently have disabled and it seems fine. I can ping the dc and access it over all ports. I got an error message this time.
Could you look it over and point me toward a next step? (I updated this for Contoso :-)
-----
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.tx
The domain name "SFS" 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 "SFS":
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.SFS
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.10.20.22
10.10.20.138
- One or more of the following zones do not include delegation to its child zone:
CTS
. (the root zone)
Thanks for the input. I was able to join a different machine. I examined the firewall which I currently have disabled and it seems fine. I can ping the dc and access it over all ports. I got an error message this time.
Could you look it over and point me toward a next step? (I updated this for Contoso :-)
-----
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.tx
The domain name "SFS" 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 "SFS":
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.SFS
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.10.20.22
10.10.20.138
- One or more of the following zones do not include delegation to its child zone:
CTS
. (the root zone)
Is that computer that could be joined successfully on the same subnet? If not, put the comp. in question on that subnet and verify the gateway entry in ipconfig.
ASKER
We'll, this is weird. I did what you said and it work which great! I guess the thing I don't understand is that I just deployed three of these vms from the same template. Two worked,one didn't. I'm gonna close this out a a fluke and cite your answers as the solution. But this doesn't make a lot of sense.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
First, make sure it's not just this one pc. For example, it could be a client side problem - even the windows firewall kept me from using the netbios name, once.