• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 901
  • Last Modified:



we are setting exchange 2010 with exchange 2003,till now we managed to make the owa accesed from outside, but from inside it cannot.

we have created casarray virtual ip for 2 cas servers its ip:
the nlb casarray seems to work fine.
but when we ping it, it does not respond

any suggestion.
  • 2
1 Solution
That sounds suspiciously certificate related but why dont you get through this doc or something  like it and see if you can provide more detailed information.


Do you have mail boxes on the 2003? if you move them to 2010 does the situation change? what are the errors? try testexchangeconnectivity.com and https://testexchangeconnectivity.com/ and let us know the results of that testing.

thanks L
yaser_981Author Commented:
the answer did not give me new information, it suggest me to read another thread.
The link  was provided to show you the types of things to provide. There are several things needed to answer this question properly. 1. Ure you using outlook anywhere whe you say internal? Does your UC SAN have the internal URl on it ? Does the Connection point have the proper internal url setting? I need to know more about the goal before I can give you an A answer. Here is another example


Can you provide the method you are using to coneect internally, along with certificates information? even the results ot ttp://testexchangeconnectivity.com would give me something to go on.

Thank you,

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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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