exchange for external access.

sina2011sina2011 Member Posts: 239 ■□□□□□□□□□
hey guys so I just finished learning exchange after 3 months now I have abit of a problem.

I'm Trying to setup OWA for external access but it wont work the things I have done in my configuration are:

1.Opened Ports 80,443,25,110,
2.Created Send Connectors,Recieve Connectors
3.Enabled Outlook Anywhere
4.Bought a Static IP from my ISP
5.created The MX and A Records on my External DNS
6.Obviously bought a domain name

when i go to

I get the error message:

The connection has timed out

The server at is taking too long to respond.

The site could be temporarily unavailable or too busy. Try again in a few
If you are unable to load any pages, check your computer's network
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

does anybody know where im going wrong any push in the right direction will be appreciated.



  • Chivalry1Chivalry1 Member Posts: 569
    First....For security reason I would leave the actual url anonymous.

    Second....log onto the server hosting the OWA and try accessing the servers OWA locally by going to http://localhost/owa. If that is successful then that means the server is operational.

    Third....Check your firewall settings and your NAT address table.
    "The recipe for perpetual ignorance is: be satisfied with your opinions and
    content with your knowledge. " Elbert Hubbard (1856 - 1915)
  • sina2011sina2011 Member Posts: 239 ■□□□□□□□□□
    hey chivalry thanks for your response

    I have checked it locally and it works but not externally.

  • ClaymooreClaymoore Member Posts: 1,637
    You need to set the external url for the OWA site, it is blank by default.

    Server Configuration > Client Access > Outlook Web Access > General Tab (RTM): Exchange 2007 Help

    Be sure you know how to do it from the command line as well:
    Set-OwaVirtualDirectory: Exchange 2010 SP1 Help

    Set-OwaVirtualDirectory -Identity "Contoso\owa (default Web site)" -ExternalUrl
  • sina2011sina2011 Member Posts: 239 ■□□□□□□□□□
    hey claymoore thanks for the reply

    Yeah I have already done that.
  • jibbajabbajibbajabba Member Posts: 4,317 ■■■■■■■■□□
    Chivalry1 wrote: »
    First....For security reason I would leave the actual url anonymous..

    Globalmatics is the Trainsignal domain they are using in their videos :)

    Have you tried to telnet to your server using port 443, making sure it is properly configured ?
    Using http://<server&gt; without /owa (or SSL) should show the default page of IIS - does this work ?
    My own knowledge base made public: :p
  • sina2011sina2011 Member Posts: 239 ■□□□□□□□□□
    yeah I know that theres is mine is

    how do I telnet to my server?

    Thanks for your reply.
  • sina2011sina2011 Member Posts: 239 ■□□□□□□□□□
    hey guys I was just thinking and having a look as well on the net do I need to create a Internal MX record on my internal DNS?

    I know its a stupid question its the first time I'm doing this.
  • undomielundomiel Member Posts: 2,818
    Sina, sorry to keep being a pain, but it still seems like you're trying to fly before you can walk. I would highly recommend going over some of the Network+ material, I believe it will do you a lot of good. You seem to have a pretty big weakness on the networking side of things. Get DNS and NAT understanding down good then jump back into learning Exchange. You'll get a lot more benefit from your studies then.

    Anyhow, the problem at hand. In your router is 80 and 443 both pointed at your Exchange server's internal ip address? Also if is your real address and not a faked one you do not have your A record setup correctly on GoDaddy. Judging from the registration it does look like your realy domain. This is what I see from an nslookup of

    Non-authoritative answer:

    Get your correct static ip address in there.
    Now your MX records:

    Non-authoritative answer: MX preference = 0, mail exchanger = MX preference = 0, mail exchanger = MX preference = 10, mail exchanger = MX preference = 10, mail exchanger =

    You will have some definitely mail flow problems with those, you need to flush everything out and only have

    When you say you opened up those ports did you do that on your router? Is their a NAT/PAT pointing back to your Exchange server? Do you understand how NAT works and where to use it?

    As for telnet, what you would do is open up a prompt and do "telnet 443" for instance to telnet into port 443. You need to do this external to your connection, it is meaningless from the inside. If it gives you a connect failed or connection refused you know you need to look at your router and firewalls. You will definitely want to learn how to telnet into the smtp port and send e-mails via telnet as it is an invaluable troubleshooting tool.
    Jumping on the IT blogging band wagon --
  • sina2011sina2011 Member Posts: 239 ■□□□□□□□□□
    Hi undomiel

    answers to your question:
    1.Yeah I understand NAT and how it all works I just didnt think about it at that time.
    2.I Do have those ports associated with my internal IP.

    For the second section of your questions that you asked:

    These are the records that I created on my external DNS (Godaddy):


    A (

    A (

    A (

    When you asked this Question: When you say you opened up those ports did you do that on your router? Is their a NAT/PAT pointing back to your Exchange server? Do you understand how NAT works and where to use it?

    The only thing I have on my Router that has any NAT configuration information is the following:

    Port Restricted Cone NAT & Full Cone NAT

    I appreciate what your saying and pointing out my mistakes as i would rather do my mistakes here then in the real world.

  • KenCKenC Member Posts: 131
    Any luck getting this resolved?
    It does seem to be a port forward issue on your router at first glance, not sure if this is what you mean when you say you have "associated" the ports with internal IP.
    Have you tried external access using an IP address instead?
  • jibbajabbajibbajabba Member Posts: 4,317 ■■■■■■■■□□
    sina, to telnet, open a command prompt and type

    telnet 443

    If it turns into a blank / black screen, then you know you get through to the server via https and if OWA still doesn't work then it is a configuration issue.

    If you get an error that the server doesn't response / can't connect, then it is a port forwarding issue.

    If you are on Windows 7 / 2008 then you will need to install the telnet client first (add / remove windows features > telnet client).
    My own knowledge base made public: :p
  • pespi_manpespi_man Member Posts: 56 ■■□□□□□□□□
    Sina, i had issues with my OWA when I was building my home lab.

    For me it was the Go Daddy settings...

    My settings can be found here -

    godaddy | Flickr - Photo Sharing!

    (Let me know if this doesnt work, havent used Flickr before)

    Also is a easy way to see if the correct ports are open.
Sign In or Register to comment.