Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Using checkADConfig to detect connectivity and DNS issues between vCenter Server and Active Directory (79323)

Last Updated: 4/20/2022Categories: How toTotal Views: 8075Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Slow or failed authentication with Active Directory credentials.

Purpose

This article shows how to use the checkADConfig.sh script. This script is meant to collect data regarding connectivity/port connectivity to all the Domain Controllers within the specified domain based on krb5-affinity.conf file and lookups of SRV records for the specified domain with the functionality to check site specific SRV records.  It can also be used to query a specified DNS server to get the response for lookups of Domain Controllers.

Resolution

Using the checkADConfig.sh script

This tool should be run from a PSC or embedded vCenter Server.

Download the checkADConfig.sh script attached to this article.

From an SSH session to the vCenter Appliance, create a new directory for the tool

mkdir -p /root/debugging
cd /root/debugging

Move the checkADConfig.sh file to the /root/debugging directory

Make the file executable

chmod +x /root/debugging/checkADConfig.sh

Run the script with the options applicable for your environment

Usage:
./checkADConfig.sh --domain=domain1 --hostType=<esx/vc> --site=site1 --nameserver=dns1 > checkADConfig_res.txt

Required: --domain=<single or comma-separated AD domain list>

Required: --hostType=<esx/vc>

Optional: --site=<single or comma-separated sites list>

Optional: --site=<dns server ip>

Example:
./checkADConfig.sh --domain=likewisetest.com,likewise-ad2016.com --hostType=vc --site=Default-First-Site-Name > checkADConfig_res.txt

It will generate output into a file like this: checkADConfig_res.txt
An example of this file has also been attached to this article for comparison.

Related Information

For information on using the lw_measure tool to detect latency between vCenter Server and Active Directory domain controllers, see https://kb.vmware.com/s/article/79317

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

checkADConfig

checkADConfig_res

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
[解決済み] AMST-27056：Windows 10 バージョン 2004 リリースで Workspace ONE UEM への加入が失敗する (79333)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Workspace ONE Access/vIDM バックアップ/リストアのプロシージャ： OVF エクスポート問題への対処方法 (79131)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

Take Our Survey

Support Assistant