Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 498
  • Last Modified:

Exchange server 2010 external url can not access 404 error

We have current exchange 2003 and we have migrated it with exchange server 2010.


We have paid ssl certificate for the exchange server 2003 and now we want to by a new certificate for the exchange server 2010

old server : exchange.abc.com
url : https://exchange.abc.com/owa

new server: mail.abc.com
URL: https://mail.abc.com/owa

we can access mails with https://mail.abc.com/owa internal url and its working internally fine. But we can not able to access this from the outside network.

when we try to access https://mail.abc.com/owa externally we got the error of certificate mismatch and we got error of 404.

when we click on certificate then the certificate is of exchange.abc.com

kindly suggest...
0
rigelnet
Asked:
rigelnet
2 Solutions
 
MAS (MVE)Technical Department HeadCommented:
Did you point your external IP to your new exchange 2010server?

Did you install certificate in exchange2010 server and enabled IIS services on the installed certificate ?
0
 
rigelnetAuthor Commented:
Yes,we have point mx record to the new exchange server 2010 and mail flow is working fine.
We have generated request for the SSL certificate and we are waiting for the certificate from SSL certificate provider.
0
 
Arjun VyavahareTechnical ConsultantCommented:
You need to point your Public IP address to  https://mail.abc.com/owa and in your firewall you need to configure NAT rule i.e. SSL request will deliver to your mail.abc.com server, then only your user can access OWA from WAN, refer below scenario:


 https://mail.abc.com/owa =======> Your Firewall ==================> Exchange Server.
                                                    Public IP Ex: 121.443.221.223
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
MAS (MVE)Technical Department HeadCommented:
Did you NAT port 80/443 to the public IP?

Install the certificate and check
0
 
Md. MojahidCommented:
are you able to access from IP instead of name. if yes then you have to check it out DNS.
0
 
rigelnetAuthor Commented:
thankyou
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now