Error accessing OWA 2007

Check the firewall logs, make sure https port is open to your new exchange server's IP address for your firewall's incoming rules.

Thank you.
Will do in the morning.
Now I have 7:37 p.m. (19:37)

After checking that, try a different address: https://webmail.company.com/owa  If you are using Exchange 2007, the exchange folder is no more. You can change that behavior, but for purposes of your post here (to just be able to access OWA), try that different URL to see if  you can access it.

Regards.
~coolsport00

https://webmail.company.com/owa gives me the same error righ away.
 
Thank you.
 

Did you verify paragonsubro's solution? Is your firewall configured correctly? Also, it looks like you're using 2 different URLs for internal/external? Are you using the self-created cert or purchased a 3rd party? Have you correctly imported then enabled it using the Shell cmdlets?

Not yet.
I guess I have to fix the certificate issues first as I never cared about it and users always went through ignoring the message.
Although, internally I connected to OWA with the certifcate warning.
 
Thank you.

Not to take you off track but I have had the certificate prompts in outlook 2007 even with OWA and exchange working. The only other thing I can think of from my experience is IIS misconfiguration on the exchange server but since you are able to access the logon page AND logon successfully from the internal network, you should have no problems (permissions usually) with IIS. If IIS is broke, usually loging on locally fails and there is a cmdlet to restore IIS that MS support gave me once.


The only time IIS fails is when your exchange 2007 users who's mailboxes have already move to exch07 can logon but the mailboxes on the ex03 server can't use the new IIS address, sounds like this is not the issue you are experiencing.
 

Since you still have your exch03 OWA working outside/inside but your exchange 03 server is working only from inside it tells me that either a firewall or some kind of name resolution problem is existant.


Also remember you have to call network solutions or whoever your dns provides for your domain is and have them not only add an MX record for your new mail server but also an A record ie "mail2.company.com". Obviously a new static IP address seperate for your new exch07 server is necessary. (common migration scenario).


I have a lot of experience in ex03 to ex07 migration so feel free to use the steps above and come back with details of where it fails.

The certificate warning prompts in Outlook with Exchg 2K7 aren't IIS related. It is due to autodiscover within Exchg and the discrepancy between the defined Internal/External URLs in separate services and the name on the certificate. As mentioned above, you can look at the KB article I posted to resolve that. But first, let's get u accessing OWA. Please verify your firewall config per paragonsubro's orig. post. From there, we can narrow things down a bit.

Hello,
Sorry I wasn't here in the morning. A few meetings and long overdue expense report took my time.
The fire wall port settings are changed. To do that I have to ask a CISCO certified consultant as I am not touching it.
HTTPS is now pointing to the new Exchange2007 server. External IP to internal new Exch2007.
Although I was maintaining Exch2003 I am doing it for the first time, the transition I mean by myself. So, please be a bit patient.
 
This is what is now.
2007 user
internally - can log in to OWA Exchange2007:
externally - gets same error number, but a bit different description:
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
2003 user
internally - can log in to OWA to Exchange2003;
externally they get log in screen but 401 error after second connection attempt:
401 - Unauthorized: Access is denied due to invalid credentials.
You do not have permission to view this directory or page using the credentials that you supplied.
Both users, 2003 and 2007 get the certificate warning internally and externally.
 
Thank you for your dedication.

There is one thing I am not sure about, how this change on the fire wall would and whether it did affect the network, but we get excessive collisions on the internal port of the CISCO router / firewall.
 
I am thinking however of moving everyone to Exchange 2007 and working out OWA having one server in place only.
In the meantime users will have connection to Terminal Server where they can check e-mail if needed. So my next step after moving everyone would be decommissioning Exchange 2003.
 
This topic is going to be still a valid issue.
I am going to reward your points now, thank you, and re-post the question after.