Error: SSL: No authority could be contacted for authentication. The domain name of the authenticating party could be wrong, the domain could be unreachable, or there might have been a trust relationship failure.
Possible Cause: The VM lost connectivity with the Domain Controller.
Possible Solution: Ensure the VM is joined to the domain and able to communicate with the Domain Controller. An Admin can log in to the VM by using Local Administrator accounts and validate connectivity with the following command.
Get-WmiObject -Class Win32_ComputerSystem | Select-Object Domain
Test-ComputerSecureChannel
Please ensure the VM can communicate with the Domain Controllers.
Possible Cause: An end user changed the network settings of the Virtual machine, for example DNS Server, as a result VM lost connectivity with the Domain Controller.
Possible Solution:
For Azure VM, run the following command from the Azure Run Command in the Azure console to reset the DNS server on all network adapters.
Get-NetAdapter | Set-DnsClientServerAddress -ResetServerAddresses
For GCP VM, use the startup script from the VM instance page, in the Metadata section, add a startup script.
Netsh interface ip set dns "Ethernet" dhcp
Possible Cause: VM was in the paused or stopped state for more than 30 days, as a result Computer account password expired on the Active Directory.
Possible Solution:
Log in to the VM with a Local Admin credential and try below:
Test-ComputerSecureChannel -Repair -Credential (Get-Credential)
Unjoin the VM from the domain, then restart and rejoin the VM to the Domain from the UI or using the below command from elevated PowerShell:
Remove-Computer -UnjoinDomainCredential (Get-Credential)
Add-Computer -DomainName "<DomainName>" -Credential (Get-Credential) -Force
Restart-Computer
Possible Cause: Hostname Exceeding Maximum(15) Character Limit of Active Directory. The pool was configured to allow single-digit suffixes, but no restriction was placed on the number of digits used. As a result, the naming sequence continued beyond "ABCD-EFG-HIJK-9," leading to unintended behaviour in the Workspot Pool configuration. Although the customer initially selected a single-digit suffix (altogether 15 characters), the system permitted the creation of VM names exceeding the intended character limit, ultimately causing conflicts with Active Directory's 15-character hostname restriction.
Possible Solution:
Create a new pool with the correct naming convention, limiting the hostname character to 15 digits (plan ahead of the number of VMs needed in the pool)
Log in to the VM with a local admin account and change the FQDN of the VM.