OWA/IIS Authentication Issue

OWA/IIS Authentication Issue

Post by Keith Crosb » Thu, 02 Aug 2001 01:50:56



Posted this a while ago, got some responses, but nothing has changed.
Please Help!

For the less computer literate around here, I want to be have one address
for them to go to, whether internal or external.  Also I would like to
secure
it using an SSL certificate, but would have to get 2 certificates (one for
each name used) or train them to ignore the warnings - and that's never a
good idea.  Here is my situation:

I am currently running OWA & E2k on an internal member server.    OWA is
open to the internet using server publishing in ISA at
"host1.domain.com/exchange".  E2k is SP1 and Win2k is SP2 on both ISA and
E2k server.  Externally, everything runs fine and I prompted for my
credentials appropriately.

Internally everything works fine.  If I point my browser to
"e2kservername/exchange", I am let in using my Win2k credentials
automatically.

I have created an in-house DNS entry that points "host1" to the OWA/E2k
server.  If I point my browser (internally) to "host1/exchange" everything
works the same as if I point to "e2kservername/exchange".

Now here's the problem:

If I point my internal browser to "host1.domain.com/exchange" I get sent to
the correct internal IP address, but this time I am prompted for my
credentials.  I enter them, and am immediately prompted for them again, and
again, and again, and again, etc.

Any help is greatly appreciated,
Keith

 
 
 

1. OWA/IIS Authentication Issue

Posted this a while ago, got some responses, but nothing has changed.
Please Help!

For the less computer literate around here, I want to be have one address
for them to go to, whether internal or external.  Also I would like to
secure
it using an SSL certificate, but would have to get 2 certificates (one for
each name used) or train them to ignore the warnings - and that's never a
good idea.  Here is my situation:

I am currently running OWA & E2k on an internal member server.    OWA is
open to the internet using server publishing in ISA at
"host1.domain.com/exchange".  E2k is SP1 and Win2k is SP2 on both ISA and
E2k server.  Externally, everything runs fine and I prompted for my
credentials appropriately.

Internally everything works fine.  If I point my browser to
"e2kservername/exchange", I am let in using my Win2k credentials
automatically.

I have created an in-house DNS entry that points "host1" to the OWA/E2k
server.  If I point my browser (internally) to "host1/exchange" everything
works the same as if I point to "e2kservername/exchange".

Now here's the problem:

If I point my internal browser to "host1.domain.com/exchange" I get sent to
the correct internal IP address, but this time I am prompted for my
credentials.  I enter them, and am immediately prompted for them again, and
again, and again, and again, etc.

Any help is greatly appreciated,
Keith

2. create newsgroup and publish it on an intranet

3. IIS Webcast Series: In's and Out's of Authentication in IIS (OWA)

4. Exchange5.5 and SMTP

5. E2k/IIS authentication issues

6. Recovering Deleted Public Folder

7. IIS Authentication & OWA

8. Adding a disclaimer to ALL emails

9. Using IIS authentication for OWA.

10. OWA/IIS authentication problem

11. IIS/Owa authentication

12. OWA/IIS Authentication problem

13. IIS/OWA Authentication