jobby1
asked on
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
excheror.jpg
you need to try Virtual CAS server's name in Server name field.
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.
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.
ASKER
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-f7
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.
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-f7
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.
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.
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.
ASKER
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.
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.
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.
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.
ASKER
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will apply the sp1 and update.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
After applying sp1 it is ok now.
internal and external name resolution...
if not resolve the DNS internal name the issue appears... like this..