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

Exchange 2010 CAS Failover Problem

I am currently implenting Exchange 2010 with 2 CAS servers using WLNB. I believe everything is setup correctly as far as autodiscover goes. The internal DNS of mail.domain.com is pointing to the VIP. The FQDN of the CAS array is outlook.corp.domain.com so that part is different although they're point to the sam VIP.

The problem is when I do a reboot of one of the CAS servers. Basically whichever is active. I did get an authentication box the first time I noticed it, but when I disabled the NICs on CAS1 server, nothing happened, although I did see a Reconnect so it seemed goo. I re-enabled the NICs on CAS1 server and then disabled the NICs on CAS2 server. Outlok then disconnected entirely and wouldn't come back up. Meanwhile ping the VIP of the WLNB never lost a beat.

I haven't messed with the permissions or authentication on IIS, but I haven't started migrating users over yet so I'd be willing to change some of this stuff if anybody has suggestions.

Thanks.
0
nnbit
Asked:
nnbit
  • 3
  • 2
1 Solution
 
Praveen BalanSolution ArchitectCommented:
If your databases are created before the CAS Array implementation, please set the rpcclientaccessserver property to match with the new cas array URL.

Set-MailboxDatabase "DB Name" -RpcClientAccessServer "outlook.corp.domain.com"

Verify it again with Get-MailboxDatabase "DB Name" |fl Rpc*

-Praveen
0
 
Praveen BalanSolution ArchitectCommented:
the below ms exchange team article gives quick steps about cas array configuration ..
http://blogs.technet.com/b/ucedsg/archive/2009/12/06/how-to-setup-an-exchange-2010-cas-array-to-load-balance-mapi.aspx
0
 
nnbitAuthor Commented:
I created the array before even installing the MB role.
0
 
nnbitAuthor Commented:
There were soem issues with the NICs on one of the VMs. I deleted and added a pair of NICs and all is working as expected. Thanks for the help.
0
 
nnbitAuthor Commented:
The solution was found, but was not a common solution and wouldn't expect anyone to be able to point it to a NIC problem.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

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