I have a site which if accessed by our company domain name with a sub domain prefix it passes across our firewall to an internal server and requests basic authentication. Fine so far.
Internally if I access the site by its server name I get windows authentication and the site comes up without a challenge.
But if I access the site internally using our domain with the sub domain prefix it challenges for basic authentication.
I have added a DNS rule so using the domain internally does now go to the server without going out of the company (or at least I think it isn't, tracert'ing the name internally reveals a direct hop to the server i.p)
So I am guessing there is another step I need to complete to allow my IIS server to be happy that the user connecting is internal?
Hopefully that's clear enough , if I'm missing something please advise.