I have a website that has been working flawlessly for years until just the other day. The has worked in the past is that if you are inside the network, your domain credentials automatically pass to the site to grant you access, if you have it in IE as a trusted site. If you are outside the network, you must authenticate. Below are the Virtual Directory Authentication Methods.
Authentication Methods:
- Basic Authentication
- Digest authentication for Windows domain servers
- Integrated Windows authentication
The only way it will work now is if you remove it as a trusted site in IE, then it prompts both internal and external users all the time.
The other way it works if you leave it as a trusted site, and for external users they have to literally type in the public IP of the site. For internal users, it operates normal.
At first I thought this was a DNS issues but after flushing dns cache locally and trying it on several different networks, I was able to resolve the host name fine (externally) using nslookup. I even went as far as adding an entry into the host file on my local machine.
Have anyone else experienced this?
Authentication Methods:
- Basic Authentication
- Digest authentication for Windows domain servers
- Integrated Windows authentication
The only way it will work now is if you remove it as a trusted site in IE, then it prompts both internal and external users all the time.
The other way it works if you leave it as a trusted site, and for external users they have to literally type in the public IP of the site. For internal users, it operates normal.
At first I thought this was a DNS issues but after flushing dns cache locally and trying it on several different networks, I was able to resolve the host name fine (externally) using nslookup. I even went as far as adding an entry into the host file on my local machine.
Have anyone else experienced this?