Internal and ExernalURL dont have anything with OWA working internally or externally. This information is picked up by clients in different scenarios to send the client to correct URL when needed. Private and Public option on OWA logon page has to do with what feature and functions are enabled for the end user when loged on. the URL for Exchange 2007 and Exchange 2010 OWA is https://......./owa not /Exchange as it was previously versions. Is the mailbox you are testing with located on Exchange 2003 or 2007 server? Have you created a redirect on your IIS website? if this is done incorrect all kinds of strange will happen with OWA and the other webservices in Exchange. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Your right indeed Sukh828, after randomly checking from a friends computer somewhere else I noticed it WAS WORKING FROM HIS HOME!!!!! So I started thinking, why is it not working from my external network computer? Its quite simple, I forgot a simple rule of testing: always test from a fresh environment!!!! What happened was, and the answer could be found with the info I gave in the first post, is that my external network computer, two of them actually, were using the certificated I had installed with the exchange 2003 server from before, hence the 2 certs prompt when I tried to log in and the failed web page afterwards. Thanks for your help, everybody contributed and it help me understand that I did set it up right and something else was wrong.

Internal and ExernalURL dont have anything with OWA working internally or externally. This information is picked up by clients in different scenarios to send the client to correct URL when needed. Private and Public option on OWA logon page has to do with what feature and functions are enabled for the end user when loged on. the URL for Exchange 2007 and Exchange 2010 OWA is https://......./owa not /Exchange as it was previously versions. Is the mailbox you are testing with located on Exchange 2003 or 2007 server? Have you created a redirect on your IIS website? if this is done incorrect all kinds of strange will happen with OWA and the other webservices in Exchange. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com For the /owa commnent, yes, I did notice the change from 2003 to 2007. I have a single 2007 exchange working, so its very basic setup, so to answer the question, yes, the mailbox is located ona 2007 exchange server. "Have you created a redirect on your IIS website? if this is done incorrect all kinds of strange will happen with OWA and the other webservices in Exchange." Could you give me more info on what you mean by that? In IIS, I have the owa virtual directory pointing to a directory located on this folder, is that what your talking about?

"Why you will get two certificate warning? It is abnormal." In exchange 2003, you'd get one warning, internally, you get one only, but external, I got 2, then loging page, then http error 400. "Is webmail.mydomain.com pointed to exchange server 2007?" Yes, the hostname is redirected to my router, which is behind nat, then port forwarded to the correct server.

Here is my situation, I had an exchange 2003 server with owa working from the outside, I am now trying exchange 2007 with owa, it is working from inside but not the outside. Port 443 and 80 are forwarded to the server, here is what is happening. From inside, http://webmail.mydomain.com/exchange, I get the warning that I need ssl, so I put in https. Now, I get the certification warning, I click the middle option (Continue to this website) , internet explorer proceeds and I get prompt for my logging. I then get another certificate warning, and then see the owa page for the loging with the "this is a public" or "this is a private" options. From the outside, I get to the first certificate, put in the user name and password, then I get the Internet explorer cannot display the webpage... So my question is this, whats different with 2007 that makes it not work when it was working fine with 2003? Made some progress, used url https://webmail.mydomain.com/owa and I see the owa page, but when I log in, I get a "the web page cannot be found"...

Hi, Please check if there is any redirect settings in default web site and OWA. If yes, please remove them. For test if the 443 port traffic forwarding is correct, you can create a home page file such as Default.htm file for this default web site in exchange 2007 server. Then try to access https://webmail.mydomain.com and check if you can open the default page. If the default page can be opened without problem. The issue should be in the OWA virtual directory. Please try to recreate it: remove-owavirtualdirecotry new-owavirtualdirectory

Hello Verify your settings for OWA; via the EMS: Server Configuration --> Client Access, right-click OWA --> Properites. There will be both Internal URL and External URL on this page. Then make sure those settings match the IIS configuration on your server.If you can get to the internal link/url but not the external then you should look at your firewall settings. Check also http://technet.microsoft.com/en-us/library/aa997682.aspx Test-OwaConnectivity -URL:https://mail.contoso.com/owa -MailboxCredential:(get-credential contoso\kweku)Thanks Mhussain

Whats wrong with your certificates? have they expired or are they not trusted by clients? symptoms indicate that you have certificate on your FW that gives you the first cert warning and when client click continue they get another cert warning because of the cert located in IIS on Exchange server. Is This correct? I suggest you start by having proper certificates.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Hi, Why you will get two certificate warning? It is abnormal. Is webmail.mydomain.com pointed to exchange server 2007? What's the url of your OWA? Please sent it to v-genli#microsoft.com with a test account. I will help you to check it. In exchange 2007 or exchange 2010, we should use https://webmail.mydomain.com/owa instead of http://webmail.mydomain.com/exchange. The OWA is the new name for Outlook Web Access. As Lasse said, make sure that the test mailbox is located in exchange 2007 mailbox server. Gen Lin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

As mentioned you seem to have some serious issue with your certs, they dont seem right. Have you got a 3rd part cert for OWA? Did you buy one? Have you setup your external namespace correctly? Have you configured Exch 2007 to use a 3rd party cert and enabled it for IIS? Sukh