Solved

exchange 2010 owa external access

Posted on 2013-11-05
5
477 Views
Last Modified: 2013-11-10
I cannot access OWA from outside my network
(extensive google search took me nowhere)

so...
OWA is accessible from local network
https://localhost/OWA

Firewall
Port forwarding 80 & 443 to exchange

what is also weird:
http://mail.mydomain.com/owa
Returns a 403, the 403 is located inside my network. (so it is kind of working!)
I have updated the 403 error & can see that it is definitely going through

https://http://mail.mydomain.com/owa
Page cannot be displayed

I am lost now, dont know what I can try

Thanks
0
Comment
Question by:defrey
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 15

Expert Comment

by:Skyler Kincaid
ID: 39626303
You are getting the 403 error message when trying to use http because it is setup to force https.

What if you try going to https://mail.company.com/owa

What do you get then?
0
 
LVL 1

Author Comment

by:defrey
ID: 39626336
https://mail.mydomain.com/owa
Page cannot be displayed
0
 

Expert Comment

by:saratoga172
ID: 39626348
Have you setup the external OWA address within Exchange itself? Also double check your DNS records to ensure everything is pointing.

Then you'll want to make sure your web address is exact.

Since you are receiving the page cannot be displayed, check to verify all of your Exchange services and IIS services are running. You may also try an IISreset from the command line to restart the IIS services.

Can you check the Event Viewer on the Exchange server and post up any related errors?
0
 
LVL 1

Accepted Solution

by:
defrey earned 0 total points
ID: 39626517
Right..Out of all the posts I have read the last 2 days, I just figured out what it wasn't working.
I also understand that many things can go wrong, so thank you for your answers.

My solution:
I said that everything was working ok internally
I could also telnet my ip on port 443 OK

After moving away from looking the EMC & IIS, I turned out to my router.

The router management (allow management from the internet) was on & using https on port 443

I turned it off & freed port 443 for exchange & now everything working
0
 
LVL 1

Author Closing Comment

by:defrey
ID: 39636741
I found the exact solution to my issue
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question