Hello, I am trying to use OWA on an exchange 2003 server. It works fine on 
the LAN, but I can't get anything when I'm outside of the network. I even 
checked the logs on the firewall and see that HTTPS traffic is being allowed 
in and is directling to my exchange server. From the outside I am trying 
"mail.company.com/exchange." Is there anything I'm doing wrong? Is there 
something I need to set up in DNS? Any help would be greatly appreciated.

"Starfish"  wrote in message 
news:4E68D7E9-E859-47E2-84E2-B0F45C1B47C8@microsoft.com...
> Hello, I am trying to use OWA on an exchange 2003 server. It works fine on
> the LAN, but I can't get anything when I'm outside of the network. I even
> checked the logs on the firewall and see that HTTPS traffic is being 
> allowed
> in and is directling to my exchange server. From the outside I am trying
> "mail.company.com/exchange." Is there anything I'm doing wrong? Is there
> something I need to set up in DNS? Any help would be greatly appreciated.

Check your OWA server's IIS log files to make sure that the external 
requests are reaching the server.

Lee.

-- 
______________________________________

Outlook Web Access For PDA , OWA For WAP
www.leederbyshire.com
email a@t leederbyshire d.0.t c.0.m
______________________________________

Yes, it appears that there is traffic hitting the server. It almost looks 
like somoene logged in last night. It may be possible that we are using the 
wrong address on the outside. Is there an easy way to tell what the OWA url 
is on the outside?

"Lee Derbyshire [MVP]" wrote:

> "Starfish"  wrote in message 
> news:4E68D7E9-E859-47E2-84E2-B0F45C1B47C8@microsoft.com...
> > Hello, I am trying to use OWA on an exchange 2003 server. It works fine on
> > the LAN, but I can't get anything when I'm outside of the network. I even
> > checked the logs on the firewall and see that HTTPS traffic is being 
> > allowed
> > in and is directling to my exchange server. From the outside I am trying
> > "mail.company.com/exchange." Is there anything I'm doing wrong? Is there
> > something I need to set up in DNS? Any help would be greatly appreciated.
> 
> Check your OWA server's IIS log files to make sure that the external 
> requests are reaching the server.
> 
> Lee.
> 
> -- 
> ______________________________________
> 
> Outlook Web Access For PDA , OWA For WAP
> www.leederbyshire.com
> email a@t leederbyshire d.0.t c.0.m
> ______________________________________ 
> 
> 
>

If the external traffic reaches the server, then you are using a correct 
address.  As long as it resolves to the correct IP address, IIS doesn't 
care.  Unless you configured the Default Web Site with a Host Header name.

"Starfish"  wrote in message 
news:31C69962-A0EC-4161-ACB1-37F6C51B3340@microsoft.com...
> Yes, it appears that there is traffic hitting the server. It almost looks
> like somoene logged in last night. It may be possible that we are using 
> the
> wrong address on the outside. Is there an easy way to tell what the OWA 
> url
> is on the outside?
>
> "Lee Derbyshire [MVP]" wrote:
>
>> "Starfish"  wrote in message
>> news:4E68D7E9-E859-47E2-84E2-B0F45C1B47C8@microsoft.com...
>> > Hello, I am trying to use OWA on an exchange 2003 server. It works fine 
>> > on
>> > the LAN, but I can't get anything when I'm outside of the network. I 
>> > even
>> > checked the logs on the firewall and see that HTTPS traffic is being
>> > allowed
>> > in and is directling to my exchange server. From the outside I am 
>> > trying
>> > "mail.company.com/exchange." Is there anything I'm doing wrong? Is 
>> > there
>> > something I need to set up in DNS? Any help would be greatly 
>> > appreciated.
>>
>> Check your OWA server's IIS log files to make sure that the external
>> requests are reaching the server.
>>
>> Lee.
>>
>> -- 
>> ______________________________________
>>
>> Outlook Web Access For PDA , OWA For WAP
>> www.leederbyshire.com
>> email a@t leederbyshire d.0.t c.0.m
>> ______________________________________
>>
>>
>>

Did you create an external record for your owa access (maybe
owa.whatever.com)?  I know mail.whatever.com will hit your smtp
gateway.  You use a frontend server as your mail gateway or do you
have a standalone server running SMTP/Antispam?

We just have an external DNS record (and cert for SSL) that will point
to our internal frontend server.  From the frontend, it just redirects
to the correct backend server where the user's mailbox resides.

Well, it looks like there is a record for "mail.company.com". I can ping it 
and it does resolve. We just migrated SBS to a new exchange server and that 
is where it stopped working. We also implemented a new firewall but I've 
verified that 80 and 443 traffic can come in. We have an exchange server 
behind our firewall. That is it. All there any records in our internal dns 
server that I need to set up? As I mentioned, OWA works fine inside of the 
lan, just not from the internet. 

"Jamer1" wrote:

> Did you create an external record for your owa access (maybe
> owa.whatever.com)?  I know mail.whatever.com will hit your smtp
> gateway.  You use a frontend server as your mail gateway or do you
> have a standalone server running SMTP/Antispam?
> 
> We just have an external DNS record (and cert for SSL) that will point
> to our internal frontend server.  From the frontend, it just redirects
> to the correct backend server where the user's mailbox resides.
>

Did you re-map your firewall NAT to your new SBS exchange server after
the migration? When you try to access it externally what HTTP error
are you getting?



James Chong (MVP)
MCITP | EMA; MCSE | M, S,
Security, Project, ITIL
msexchangetips.blogspot.com


On Jun 17, 10:41 am, Starfish 
wrote:
> Well, it looks like there is a record for "mail.company.com". I can ping it
> and it does resolve. We just migrated SBS to a new exchange server and that
> is where it stopped working. We also implemented a new firewall but I've
> verified that 80 and 443 traffic can come in. We have an exchange server
> behind our firewall. That is it. All there any records in our internal dns> server that I need to set up? As I mentioned, OWA works fine inside of the> lan, just not from the internet.
>
>
>
> "Jamer1" wrote:
> > Did you create an external record for your owa access (maybe
> > owa.whatever.com)?  I know mail.whatever.com will hit your smtp
> > gateway.  You use a frontend server as your mail gateway or do you
> > have a standalone server running SMTP/Antispam?
>
> > We just have an external DNS record (and cert for SSL) that will point
> > to our internal frontend server.  From the frontend, it just redirects> > to the correct backend server where the user's mailbox resides.- Hide quoted text -
>
> - Show quoted text -

Yes, all HTTPS and HTTP traffic is set to map to the IP of the new server. 
When I try https://mail.company.com/exchange, I get a "page cannot be 
displayed. Cannot find server or dns error." If I try 
https://company.com/exchange, I get "The page cannot be found. HTTP Error 
404. File or directory not found."

"Jamestechman" wrote:

> Did you re-map your firewall NAT to your new SBS exchange server after
> the migration? When you try to access it externally what HTTP error
> are you getting?
> 
> 
> 
> James Chong (MVP)
> MCITP | EMA; MCSE | M+, S+,
> Security+, Project+, ITIL
> msexchangetips.blogspot.com
> 
> 
> On Jun 17, 10:41 am, Starfish 
> wrote:
> > Well, it looks like there is a record for "mail.company.com". I can ping it
> > and it does resolve. We just migrated SBS to a new exchange server and that
> > is where it stopped working. We also implemented a new firewall but I've
> > verified that 80 and 443 traffic can come in. We have an exchange server
> > behind our firewall. That is it. All there any records in our internal dns
> > server that I need to set up? As I mentioned, OWA works fine inside of the
> > lan, just not from the internet.
> >
> >
> >
> > "Jamer1" wrote:
> > > Did you create an external record for your owa access (maybe
> > > owa.whatever.com)?  I know mail.whatever.com will hit your smtp
> > > gateway.  You use a frontend server as your mail gateway or do you
> > > have a standalone server running SMTP/Antispam?
> >
> > > We just have an external DNS record (and cert for SSL) that will point
> > > to our internal frontend server.  From the frontend, it just redirects
> > > to the correct backend server where the user's mailbox resides.- Hide quoted text -
> >
> > - Show quoted text -
> 
>

I'd just hit http://mail.company.com and see if it puts up the dialog
box for authentication.  You'll have to try this from an outside
connection though as your internal resolution is working okay.  Being
that your mail is coming via port 25, port 80 or 443 should be open
for OWA connectivity.

If I try mail.company.com I get "Page cannot be displayed. Cannot find server 
or DNS error."

"Jamer1" wrote:

> I'd just hit http://mail.company.com and see if it puts up the dialog
> box for authentication.  You'll have to try this from an outside
> connection though as your internal resolution is working okay.  Being
> that your mail is coming via port 25, port 80 or 443 should be open
> for OWA connectivity.
>

what about mail.company.com/exchange

Al

"Starfish"  wrote in message 
news:C1263652-3C91-4F73-A089-02F0EA9F4363@microsoft.com...
> If I try mail.company.com I get "Page cannot be displayed. Cannot find 
> server
> or DNS error."
>
> "Jamer1" wrote:
>
>> I'd just hit http://mail.company.com and see if it puts up the dialog
>> box for authentication.  You'll have to try this from an outside
>> connection though as your internal resolution is working okay.  Being
>> that your mail is coming via port 25, port 80 or 443 should be open
>> for OWA connectivity.
>>

Wait a sec...what IP is IIS set to use for default website or the
exchange ones?  If it's only set to use a private address, no public
referrals would work correctly.  However I'd imagine your router is
set to NAT public IP to the internal one of your mail server already.
Hmmm.....