Unable to connect to exchange server

I have two CAS and two Mailbox servers for my exchange 2013 running on windows 2008 R2. I am not able to connect to exchange server using outlook 2010 and 2013 when I config the outlook account. I am getting the error "exchange server is unavailable". I have attached the error. I have use Windows NLB for load balancing the two CAS servers.
excheror.jpg
jobby1Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sajid Shaik MSr. System AdminCommented:
check  the DNS ...  

internal and external name resolution...

if not resolve the DNS internal name the issue appears... like this..
0
Krishna PatilCommented:
you need to try  Virtual CAS server's name in Server name field.
0
Simon Butler (Sembee)ConsultantCommented:
On Exchange 2013 Autodiscover MUST work, because the server name is actually a unique end point. Entering a real or virtual server is not going to work.

Your use of WNLB is the first point of concern - was it working before you implemented that junk? You need to bypass it as it is the cause of a lot of problems.
Then you need to check if Autodiscover is working correctly and returning the correct information.

Simon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

jobby1Author Commented:
I am getting this error when test using the

https://testconnectivity.microsoft.com

Attempting to ping RPC proxy xx.abc.com.
       RPC Proxy can't be pinged.
       
      Additional Details
       
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Headers received:
request-id: b07eef05-edee-4f95-87f8-f761cf3e44c9
X-CasErrorCode: EndpointNotFound
Persistent-Auth: true
X-FEServer: srvcas01
Content-Length: 0
Cache-Control: private
Date: Thu, 27 Feb 2014 16:10:24 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 2276 ms.
0
Simon Butler (Sembee)ConsultantCommented:
That is pretty obvious - the directory isn't there.
Either you haven't installed the prerequisites correctly for Exchange 2013 or your web service is messed up, perhaps the bindings are wrong.

Install Exchange 2013 SP1. That effectively reinstalls the product and will resolve a lot of issues.

Simon.
0
jobby1Author Commented:
Simon Butler (Sembee):

Which directory is missing.?

If I install the prerequisites will it solve the issue or it will mess up or should I apply the sp1 better.? Do I need to apply sp1 in all four servers or just  CAS servers.
0
Simon Butler (Sembee)ConsultantCommented:
If you reinstall the pre-requisites using the command line on TechNet, then anything missing will be installed correctly.

Exchange 2013 SP1 has to be installed across all of your server, but those with the CAS role have to be done first. Be aware that there is currently a bug with third party transport agents like Exclaimer, CodeTwo and AV products which stops them from working when SP1 is installed.

The comments in the blog posting announcing the release have more information.
http://blogs.technet.com/b/exchange/archive/2014/02/25/exchange-server-2013-service-pack-1-available.aspx

Simon.
0
jobby1Author Commented:
Simon Butler (Sembee):

My exchange server is  Release to Manufacturing version of Exchange 2013
December 3, 2012 15.00.0516.032

So can I directly run the exch sp1 setup in all the serves starting with CAS or should I install the CUs first.
0
Simon Butler (Sembee)ConsultantCommented:
You can go straight to SP1 - there is no need to deploy the cumulative updates first.
Do the CAS role holders first, reboot at the end then do the mailbox servers.

Simon.
0
jobby1Author Commented:
I will apply the sp1 and update.
0
jobby1Author Commented:
After applying sp1 it is ok now
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jobby1Author Commented:
After applying sp1 it is ok now.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.