For some reason I was unable to view the websites that I previously published on this server, and access to the back end IIS server was not working.Let me show you how my lab environment is configured: My domain “uilson.net” contains the following servers: The labiis server hosts a non-claims application which receives pre-authentication from labadfs using my AD DS account to log in.
After some research, I decided to do exactly what AD FS Event ID 276 says to do: Run the Install-Web Application Proxy cmdlet on the WAP server to re-establish trust between AD FS and WAP: The command above re-installs the correct certificate on the WAP Server.
Note that I’m using the correct certificate thumbprint (starting with 22121…): You need to provide your credentials in order to execute the cmdlet.
After running this cmdlet, the WAP server came back online and the configuration could be successfully retrieved from AD FS.
If you’re running newer versions of Windows like Windows 10, Windows 8, or Windows 7, then everything will work fine.
It’s only with older versions of Windows like Windows XP, Windows 2000, Windows 98, etc.
Previously, I wrote an article about what would happen if you had two computers with the same IP address on the same network: an IP address conflict.