Jerry dubuke 2006-08-03 07:57:16
Good morning all,
I have an E2K3 server with an internal IP address, and do port forwarding
from a firewall/router to it from the outside world.
From outside the company, I can hit http://mail.xxxx.com/exchange (my A
record public address) and get into OWA after entering name/password.
When I am inside the company, if I try the same exercise, I cannot get past
the login prompt! It keeps popping up and never lets me into the OWA. I
have also tried entering
mail.x**.com is resolving to the external address (verified by a ping).
If I try from within the LAN to use the internal address
(exchserver/exchange), I get right into OWA and my mailbox without a logon.
I would like a user to be able to go to a connected computer, and using IE
get to their mail during the day.
Can anyone shed some light on this phenomenon?
Ben winzenz ex 2006-08-03 07:57:45
Try adding mail.x**.com to your internal DNS as an alias or another A record
for your Exchange server. If you add another A record, use the internal IP,
otherwise an alias (CNAME) should work fine. I’m betting you’re getting the
external IP and trying to hit that from inside the LAN, which doesn’t
You could confirm this by pinging mail.xxxx.com – when you do that do you
get the external IP?
Lanwench mvp - 2006-08-03 08:00:22
You could show users how to use http://servername/exchange when inside –
Jerry dubuke 2006-08-03 08:07:00
The problem with the http://servername/exchange is that it directly goes to
the inbox of the user that is logged in – no prompt for a userid/password.
That is not what I am looking for. want to be able to go up to the pc and
type it in and be prompted for which user to go to – not go directly to the
“logged in” user as it is currently doing.
How can I get the OWA to prompt for a password when on the internal LAN?
“Lanwench [MVP – Exchange]”
Jerry dubuke 2006-08-03 08:07:15
when I ping the mail.xxxx.com from within the LAN, it resolves to the public
(outside) addy. So, I dont think I need to add anything to my internal DNS
at this point. As I mentioned in the initial post, it prompts me for
login/password, but I cannot get any verification to work from inside the
Peretz stern 2006-08-03 08:07:23
You can get a prompt from OWA if you go to http:\\server\exchange\username.
At that point it WILL ask you for u/p.
Ben winzenz ex 2006-08-03 08:09:03
Think about that for a second.
Internal clients are attempting to connect to the external IP of your
firewall, which is publishing that IP to the internal server. Because they
are connecting to the external IP, the information will then attempt to be
forwarded through the firewall, back in and to the client. I don’t think it
is going to work.
It *really* would be much easier to add an A record to your internal DNS
that says mail.xxxx.com goes to Internal IP of Exchange. You really don’t
want internal clients attempting to resolve internal systems using the