www.gsx.com | log in | register

Last update: . Author: Cyril LEROY .

Lync Front-end Service Error: "User Authentication: 403, Forbidden"

When scanning a Lync Front-end service, it may fail to run a User Authentication test. This can be due to bad credentials being used for the Test account configured.

This article describes how to validate user credentials outside of GSX Monitor using PowerShell commands or cmdlets. 

GSX Monitor 10.9+ | Lync 2013 | Powershell

Symptoms

  • Front-end service is down: User Authentication test failed.
  • User Authentication: 403, Forbidden

How to Troubleshoot the Issue

The probable cause of this error is that the password used in the configuration contains a typing error. Once you have entered the passwords again to ensure they are correct, you can use PowerShell to get a more detailed error message.

The user credentials configured in Lync server Connectivity tab  can be validated outside GSX Monitor by issuing the following commands from the server running GSX Monitor:

  1. Open the session to Lync Remote PowerShell Endpoint using a Lync admin account:

    $admincred = Get-Credential domainname\adminuser

    $sessionoption = New-PSSessionOption -SkipCACheck -SkipCNCheck –SkipRevocationCheck

    $session= New-PSSession -ConnectionUri https://yourlyncFQDN/OcsPowershell -Credential $admincred -SessionOption $sessionoption

    Enter-PSSession $session

  2. Issue the test-authentication command using the account configured as Test User 1:

    $usercred = Get-Credential domainname\testuser

    Test-CsClientAuthentication -TargetFqdn lyncfrontendfqdn -UserSipAddress "sip:testusersipaddress" -UserCredential $usercred

Command should pass successfully.

Once you have credentials that can run the above commands with no errors, transfer this information into the relevant part of GSX Monitor where domain\testuser is the Test User 1.

Microsoft Related articles



Not finding what you are looking for?

Have more questions? Submit a request


Was this article helpful?

0 out of 0 found this helpful