To provide the troubleshooting process when vCenter login failure issues are reported by the on-premise VCDR connectors. This error can be seen in both the VCDR UI as well as in connector ssh sessions.
Symptoms:
The following error can be seen in the VCDR UI:
"Connector <connector name> in protected site <site name> is unabe to reach vCenter <IP address>. Cannot complete login due to an incorrect username or password on port 443."
The following message is seen when running the cli command 'drc network test --scope all' on the VCDR connector. Typically you would expect to see the local, on-premise, ESXi hosts listed in this output as well.
The expected output of the cli command 'drc network test --scope local' on the VCDR connector should also include both the vCenter information and on-premise ESXi host information. When running the 'drc network test --scope local' cli command only the on-premise vCenter information was shown along with the login error message.
Check the on-premise vCenter NTP settings and on-premise EXSi host NTP settings to verify that the settings match. There are several ways to view and configure this information. Helpful articles are posted below:
After verifying or correcting the NTP settings, the next step is to re-register the vCenter. There are two ways to re-register the vCenter: