• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 460
  • Last Modified:

Exchange 2003 OWA only authenticates IP Address Users

When users outside the WAN type in dns adress and attempt to log in to the OWA server, the server does nothing and displays the login page again.  If a user uses the public IP address, they can then log in.

Users within the WAN can specify the server name and login, they don't need to use an IP address.

Any ideas?
Thanks!

***UPDATE***
The OWA accessed by the DNS name works in both Chrome and Safari.  It seems not to work in Internet Explorer.
0
jlgerber
Asked:
jlgerber
  • 3
  • 2
1 Solution
 
mlongohCommented:
At first glance it sounds like a public DNS lookup failure.  I would be using NSLOOKUP to confirm what the OWA's public FQDN resolves and verify if it is the public IP.

However, in our update, you indicate that it works for Chrome and Safari users, but not IE users?  Is this still limited to just public internet connected users?
0
 
jlgerberAuthor Commented:
Our local DNS server had a bad forwarder.  I removed it, and all is fine.
Thanks! :)
0
 
jlgerberAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for jlgerber's comment #a38788949

for the following reason:

Since the page actually loaded, hadn't thought to check DNS.  Good Call!!!!
0
 
jlgerberAuthor Commented:
Since the page actually loaded, I hadn't thought to check DNS.  Good Call!
0
 
mlongohCommented:
Thanks for the points.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now