Problems after installation of exchange 2010
I can access OWA internally but not externally
so far I only move one user (myself)
when I go to http://mail.mydomain.com/exchange
and log in as any user it takes me to exchange 2003
but when I log in (I've been move to 2010) to the same address it takes me to
http://new-exchange-server.domain.local/exchange with this error msg
Server Error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
Now internally in the network I can access OWA this way
https://new-exchange-server.domain.local/owa
and it will allow me to log in to the new exchange and OWA 2010
so far I only move one user (myself)
when I go to http://mail.mydomain.com/exchange
and log in as any user it takes me to exchange 2003
but when I log in (I've been move to 2010) to the same address it takes me to
http://new-exchange-server.domain.local/exchange with this error msg
Server Error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
Now internally in the network I can access OWA this way
https://new-exchange-server.domain.local/owa
and it will allow me to log in to the new exchange and OWA 2010
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Hi,
It is redirected to a .local addres this will never be available from external.
Read here http://technet.microsoft.com/en-us/library/ee332348.aspx what steps you should do for moving client access from echange 2003 to exchange 2010.
It is redirected to a .local addres this will never be available from external.
Read here http://technet.microsoft.com/en-us/library/ee332348.aspx what steps you should do for moving client access from echange 2003 to exchange 2010.
As you have seen, Exchange changed the location from 2003 to 2010 as OWA for the virtual directory. You also will have this as an issue trying to access your internal email from within your office subnet. Unless you have a static dns entry within your office dns, for remote.yourdomain.com that resolves to the internal Ip address, I have found it problematic to get it to resolve and behave correctly. The best way to test is to have a machine on a different subnet, using a cel carrier access card or taking over a machine at home remotely. Then use remote.yourdomain.com/owa and see what you get.
I also STRONGLY advise you get a third party certificate for authentication as it will greatly simplify your life connecting mobile phones and accessing from outside. (under$200)
I bet if you try it from outside the office, it will work properly. (also make sure you have enabled Outlook Web Access for your account in Exchange Features on Active Directory.
Good luck!
I also STRONGLY advise you get a third party certificate for authentication as it will greatly simplify your life connecting mobile phones and accessing from outside. (under$200)
I bet if you try it from outside the office, it will work properly. (also make sure you have enabled Outlook Web Access for your account in Exchange Features on Active Directory.
Good luck!
Premium Content
You need an Expert Office subscription to comment.Start Free Trial