IE doesn't treat local website as part of Intranet Zone

Discussion in 'Windows Server' started by RW, Apr 4, 2006.

  1. RW

    RW Guest

    I've come across a problem with how Internet Explorer determines which
    websites are in the Local Intranet zone.

    We've got a website on our internal network. People access this site using
    http://<machinename>. IE sees it's a website in the local intranet zone.
    But when we access the website with a FQDN, http://machinename.domain.com IE
    doesn't think it's part of the local intranet zone. It thinks it's in the
    Internet zone. This results in more security settings for this site, and for
    that reason Intgrated Authentication no longer works (people have to log
    on).

    Why would IE handle these two sites as different when in fact they are the
    same ? Only the URL is different. The settings for the Zone Intranet are
    default (Include all site in local intranet).
    Manually addding the FQDN site in the zone solves the problem, but every
    user will have to do this.

    Is this a bug or am I missing the point ?

    Greetz
     
    RW, Apr 4, 2006
    #1
    1. Advertisements

  2. RW

    Gary Mount Guest

    If you go to your Internet Options : Security, and select the Local
    Intranet, then click the Sites... button, you might be able to change the
    ..com site so it is in the Local Intranet site instead of the Trusted sites.
    I just did that for my site, and it now says "Local intranet" when I am on
    my web site when it had "Trusted sites" before.
    However that wasn't my .com site. So I just now tried it on my .com site,
    and I was able to add that to "Local intranet" as well.
     
    Gary Mount, Apr 4, 2006
    #2
    1. Advertisements

  3. RW

    RW Guest

    I didn't have to put the http://<machinename> site in my Local Intranet zone
    manually. So why doesn't IE put the other one in automatically ? They're the
    same, even down to the IP address.
    I know this method is a workaround, but telling 500 users they need to
    change this is somewhat of problem (even using a policy to change it, it too
    much work if you ask me)

    Still sounds like a bug to me.
     
    RW, Apr 4, 2006
    #3
  4. The former cannot be on the Internet whereas the .com version could be. I
    could have an alias in my hosts file so that http://google resolves to
    127.0.0.1 - that does not mean it should also regard www.google.com as
    127.0.0.1.

    Does that make sense?

    Andrew
     
    Andrew Morton, Apr 4, 2006
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.