Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

The server isnt a Client Access Server

$
0
0

We recently moved over to a 2013 cas server and we are in coexistence with 2010. 2010 clients are working right now, however 2013 users do not work. If you tryand setup the user manually and hit check name, this pops us:

---------------------------
Microsoft Outlook
---------------------------
Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name.  The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
---------------------------
OK   
---------------------------

All the DNS, the urls are fine, OA is setup correctly but the "Find Name" and logging in at all fails. When I run the following command though:

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Test-OutlookWebServices -ClientAccessServer mailhub2.domain.org

I get the following

The specified server, MAILHUB2, isn't a Client Access server.
    + CategoryInfo          : InvalidArgument: (:) [Test-OutlookWebServices], TestWebServicesTaskException
    + FullyQualifiedErrorId : [Server=MBOXMPR1,RequestId=abc688a3-a89c-40c2-855b-7d36bb33f5c6,TimeStamp=1/22/2015 11:0
   6:51 PM] [FailureCategory=Cmdlet-TestWebServicesTaskException] 1D179E80,Microsoft.Exchange.Monitoring.TestOutlookW
  ebServicesTask
    + PSComputerName        : mailhub2.willowcreek.org

Is this the issue or is this simply not a 2013 feature? 



Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>