What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Why are my VMware sensors not working after upgrading to VCSA 6.5 U1?



Your Vote:



Since upgrading to VCSA version 6.5 Update 1, my VMware sensors are in a Down status due to invalid credentials. How can I fix this?

prtg vmware vmwaresensor

Created on Feb 28, 2018 2:45:19 PM by  Brandy Greger [Paessler Support]

Last change on May 22, 2019 10:04:17 AM by  Maike Guba [Paessler Support]

1 Reply

Accepted Answer



Your Vote:



This article applies to PRTG Network Monitor version 19 or later

AD authentication not working with VCSA 6.5 Update 1

If you have issues with VMware sensors in a Down status because of invalid credentials since updating to VCSA 6.5 Update 1, this may be because VMware modified the Identity Source settings.

As of this version, Active Directory (Integrated Windows Authentication) is now set by default. With this setting, the sensors can no longer authenticate themselves with the vCenter Server using the AD credentials by default and are therefore in a Down status. Because the sensors are using username and password for authentication, you have to explicitly enable LDAP integration for the identity source, as this authenticates based on the given credentials.

Configure a new identity source with LDAP integration in vCenter

  1. Log in to the vSphere Web Client interface as Single Sign-On administrator. For example, as [email protected].
  2. Go to Administration | Single Sign-On | Configuration.
  3. On the Identity Sources tab, click the + button to add a new identity source.
  4. Make sure to select Active Directory as an LDAP Server.
    Active Directory as an LDAP Server Setting
    Click to enlarge.
  5. Configure the identity source as usual using your AD information.
  6. Click OK to save the new identity source.
  7. Click Test Connection to check the connection to the new identity source.

Your VMware sensors can now successfully authenticate themselves and will return to an Up status.

Note: Alternatively, you can configure a local user in your vSphere environment. Then you do not have to change the LDAP settings manually.


For more detailed information, see the VMware documentation.

Created on Feb 28, 2018 4:44:33 PM by  Brandy Greger [Paessler Support]

Last change on Dec 10, 2020 3:18:41 PM by  Brandy Greger [Paessler Support]

Please log in or register to enter your reply.

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.