This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 64%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
We have ADFS farm with WAP servers, suddenly the operation status under Remote Management console of proxy servers shows - Either the server is not working properly, or credentials are not available to manage and monitor it.
From WAP1 under Remote Management console, the status of WAP2 shows "Either the server is not working properly, or credentials are not available to manage and monitor it" and vice versa when I check from WAP2
When we try to enter a valid credentials nothing happens. We are not sure if this is an expected behavior, if not what action we need to take to fix it.
We already tried restarting each WAP server and also successfully ran the Install-WebApplicationProxy –CertificateThumbprint <> -FederationServiceName <ADFS FQDN>, but nothing worked.
Need help to fix this issue. 
Federated identity management using Active Directory Federation Services
Are the servers domain joined or in workgroup? Is there any Windows NLB in the mix?
WAP don't really need to talk to each other. So, I wouldn't worry about the message as long as both servers are working.
These servers are hosted in Azure and externally load balanced using Azure External Load Balancer.
I want to believe what you are saying, but looking at the WAP monitoring status it is concerning as I have seen in another environment with same setup it shows green for both.