The reason being for this behavior resides in the IE security configuration.
I was using Local Intranet when I should use Trusted Site
What IE does internally ?
When is given a URL to load, IE performs the following checks to determine which security zone should be used
- If IE has been told (via policy or by the user) which zone to apply, use the setting
- FYI: this is the only way that restricted sites are used
- If the address is not fully qualified (does not have a . in its name, such as .com)... meaning that it is ONLY accessible via the local network (not internet rout able), IE defaults to the INTRANET ZONE
- If the address is fully qualified, meaning it MAY be publicly routable, it is thrown into the internet zone
Next, IE will attempt to load the page anonymously, if the site accepts anonymous access, no problems, but if the site requires authentication, it asks IE to authenticate.
This is one area that zones come into play, and is often why zones get misused.
- In the intranet zone, your windows security token can be shared with the site to attempt automatic/integrated login... since the intranet is often used for sites which are not publicly routable, providing the token (which does not in any way contain your password) is considered safe, and often provides a good user experience
- The trusted zone is meant to allow sharing of SAVED PASSWORDS
additionally, the intranet site is generally configured to be less restrictive than trusted sites, since intranet sites are managed and trusted by a company.