I'm encountering strange behaviour on installed web package
(outlooksoft) for IIS 5.
When entering the address for the application in the browser the
attempt succedes when using the ip-address and fails when using the
DNS alias.
ex: http://45.216.48.249/osoft/ is successful,
http://ap0210.bgc.net/osoft/ fails.
Directory secutrity settings: Basic Authentication & Integrated
windows authentication are active. (these settings are set by default
when installing the product)
When putting anonymous access active and removing the basic
authentication all works fine.
Can someone help why IP-address is OK and DNS alias fails.

[ Post a follow-up to this message ]

On 18 Feb 2004 04:35:12 -0800, olivier.lammens@belgacom.be (Olivier)
wrote:

>I'm encountering strange behaviour on installed web package
>(outlooksoft) for IIS 5.
>When entering the address for the application in the browser the
>attempt succedes when using the ip-address and fails when using the
>DNS alias.
>ex: http://45.216.48.249/osoft/ is successful,
>http://ap0210.bgc.net/osoft/ fails.
>Directory secutrity settings: Basic Authentication & Integrated
>windows authentication are active. (these settings are set by default
>when installing the product)
>When putting anonymous access active and removing the basic
>authentication all works fine.
>Can someone help why IP-address is OK and DNS alias fails.

Define "fails."

Jeff

[ Post a follow-up to this message ]

jcochran.nospam@naplesgov.com (Jeff Cochran) wrote in message news:<40366b46.579817914@m
snews.microsoft.com>...
> On 18 Feb 2004 04:35:12 -0800, olivier.lammens@belgacom.be (Olivier)
> wrote:
> 
>
> Define "fails."
>
> Jeff

Fails means: This page can not be displayed

[ Post a follow-up to this message ]

On 18 Feb 2004 23:09:00 -0800, olivier.lammens@belgacom.be (Olivier)
wrote:

>jcochran.nospam@naplesgov.com (Jeff Cochran) wrote in message news:<40366b4
6.579817914@msnews.microsoft.com>... 
>
>Fails means: This page can not be displayed

Many possibilities, the only IIS one is that you use host headers and
have an incorrect header or missing header for the domain name.  The
other possibilities are your DNS is wrong, you have a host file that
is incorrect, your DNS points to an internal address that IIS doesn't
use, etc.

Tracing this is normal network name resolution stuff, NSLOOKUP, Ping,
etc.

Jeff

[ Post a follow-up to this message ]

I might also check the browser securing and zone settings.  Some combination
of settings can intentionally forbid nt integrated authentication to sites
that are on the internet or that you did not tell your browser is part of
your internal network.  The solution is either to add the DNS or domain name
to another zone such as Intranet zone, or change the checkbox that forbids
integrated authentication in that zone.


"Jeff Cochran" <jcochran.nospam@naplesgov.com> wrote in message
news:403cd499.672317491@msnews.microsoft.com...
> On 18 Feb 2004 23:09:00 -0800, olivier.lammens@belgacom.be (Olivier)
> wrote:
 
>
> Many possibilities, the only IIS one is that you use host headers and
> have an incorrect header or missing header for the domain name.  The
> other possibilities are your DNS is wrong, you have a host file that
> is incorrect, your DNS points to an internal address that IIS doesn't
> use, etc.
>
> Tracing this is normal network name resolution stuff, NSLOOKUP, Ping,
> etc.

[ Post a follow-up to this message ]