• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 890
  • Last Modified:

ADFS not behaving as expected through load balancer

We are experiencing a very strange problem with our ADFS Environment.

When we connect to our ADFS Landing Page at https://adfs.mydomain.com and click the “Sign In” Button, something happens to make our workstations query DNS for a server other than adfs.mydomain.com.

This is shown in Fiddler in the highlighted portion at the lower right (shown below) where I see <h2> Object moved to <a href=’https://server-119.mydomain.com/adfs.ls/?SAMLRequest=…

See the fiddler analysis below.

Fiddler Screenshot
How all of our 100+ websites behave


User enters the URL https://mywebsite.mydomain.com into their web browser to access the one of our websites.


User successfully arrives at the website using that URL.


User signs into the website, or clicks some links to go to other parts of the website.


The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename1.htm


User clicks more links on the website.


The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename2.htm


User clicks more links on the website and performs some complex tasks on the website.


The code on the websites uses relative paths and the user continues to access the website at http://mywebsite.mydomain.com/pagename3.htm      
How all 100+ of our websites work
How our ADFS Website Behaves - which is totally different than all our other websites


User enters the URL https://adfs.mydomain.com/adfs/ls/IdpInitiatedSignOn.aspx into their web browser to access the ADFS Landing Page.


User successfully arrives at the ADFS Landing page via that URL.


User clicks the "Click Continue to Sign In Button" on the ADFS Landing Page.


Something, most likely code on that landing page or somewhere else inside the ADFS Server, sends back information to the web browser with the name http://server-119.mydomain.com.


The User's computer then queries DNS for http://server-119.mydomain.com 


The User's web browser then access http://server-119.mydomain.com directly and no longer goes through the load balancer.
How the ADFS Website Does Not Behave Like all the others.
This is my problem.

I have a feeling that ADFS has done something to IIS that is making IIS behave differently when ADFS sits inside of it, when compared to every other IIS website we have.

That’s what I need to get to the bottom of .
1 Solution

In IIS have your check your site binding and redirect settings?

Do you have any external DNS Cname records points to there other server name?
ACECORPAuthor Commented:
I had to rip the environment down and rebuild it. I had to make a lot of changes, to many to list here, but I solved it :)

Thanks for your efforts.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now