KB: Domain either does not exist or could not be contacted

ISSUE

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.

CAUSE

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.

VERSIONS AFFECTED

AD cmdlets version 1.0.6.

RESOLUTION

Upgrade to a later version or install a patch from http://www.powergui.org/thread.jspa?messageID=15755.

ACKNOWLEDGEMENTS

Thanks to everyone who reported the issue at the AD PowerShell discussion forums and helped troubleshoot and narrow down the issue.

Tags: , , , , , ,

0 Responses to “KB: Domain either does not exist or could not be contacted”



  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




My Recent Tweets

Legal

The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

January 2008
M T W T F S S
« Dec   Feb »
 123456
78910111213
14151617181920
21222324252627
28293031  

%d bloggers like this: