AD cmdlets are issuing the following error message: “
The specified domain either does not exist or could not be contacted“.
The message is displayed even though native tools, such as Active Directory Users and Computers, can connect to the domain with no issues.
Explicitly specifying credentials or domain/DC name (in a cmdlet or Connect-QADService) does not help and leads to the same error message.
AD cmdlets version 1.0.6 have a software issue which leads to this error message in the following circumstances:
- Netbios domain name and Name attribute of the domainDNS object do not match.
- Global Catalog is not available.
AD cmdlets version 1.0.6.
Upgrade to a later version or install a patch from
Thanks to everyone who reported the issue at the AD PowerShell discussion forums and helped troubleshoot and narrow down the issue.