Exchange 2010 Cas Array, Problems with Outlook
-
יום חמישי 26 אפריל 2012 17:07
Hi,
I am having some troubles with our Exchange servers. A CAS array was created and I set up all the RPC ports correctly in the registry. I also put the CAS Array on RPCClientAccess in my database. However whenever I use Outlook, It says, as per as the print screen shown below, that my server is not online.
What does “=SMTP:” before my email address mean?
I tested that solution using my loadbalancer or directly connected to my server (modifying my DNS setting), OWA works correctly. RPC only gets to work, Outlook Anywhere not being activated.
I am on the middle of migrating Exchange 2003 to 2010, everything is working apart from the CAS Array issue.
Have you got any idea what could be the issue?
Thanks,
Julien
כל התגובות
-
יום חמישי 26 אפריל 2012 17:24
What settings in the registry did you add ? and what servers did you do this on? Is the CASarray name pointed to a vip on the load balancer? what ports did you condfigure on the load balaner? they should be the same ports you created in the registry on the CAS Servers. please run the below commands and reply with the values
#1 get-clientaccessarray
#2 get-mailboxdatabase |select *rpc*
Bulls on Parade
-
יום חמישי 26 אפריל 2012 17:41
Hi,
I have add for RPC : 60000 and for AdressBook : 60001 i have the same in my loadbalancer. But if my dns is directly on the server this is the same issue.
[PS] C:\Windows\system32>get-clientaccessarray
Name Site Fqdn Members
---- ---- ---- -------
Cas Array Boetie cmc01.xxxxxxxxx.re.lan {SINF-CMC01, SINF-CMC03}
[PS] C:\Windows\system32>get-mailboxdatabase |select *rpc*
RpcClientAccessServer
---------------------
cmc01.xxxxxxxxxxxx.re.lanI have other database but i haven't configure RPCClientAccess because that doesn't works..
Julien
- נערך על-ידי J.OHAYON יום חמישי 26 אפריל 2012 17:41
-
יום חמישי 26 אפריל 2012 18:05
on the load balancer have you added port 135? you need to. If this port is not present please add it, then point your DNS back to vip on the load balancer and try again. On the client machine with outlook open run a netstat -an the output of the netstat command will show you if your outlook client is able to make a connection to the configured ports on the CAS server
Bulls on Parade
-
יום חמישי 26 אפריל 2012 18:52
Too many changes to really know the issue.
I would start by bypassing the load balancer. Change the DNS entry of the CAS array to point directly to one of the CAS role servers. Test it again.
The SMTP bit is usually a sign that the name resolution isn't working correctly, which would point the finger at the load balancer not being configured correctly.
Confirm the RPC CAS array works correctly natively before trying to add anything else to mix. You may have to reverse the registry changes and restart the Exchange services to be sure.
Simon.
Simon Butler, Exchange MVP
Blog | Exchange Resources | In the UK? Hire Me.- הוצע כתשובה על-ידי Simon_WuMicrosoft Contingent Staff, Moderator שבת 28 אפריל 2012 19:48
- הצעה כתשובה בוטלה על-ידי J.OHAYON שבת 28 אפריל 2012 20:06
-
יום חמישי 26 אפריל 2012 19:13
Too many changes to really know the issue.
I would start by bypassing the load balancer. Change the DNS entry of the CAS array to point directly to one of the CAS role servers. Test it again.
The SMTP bit is usually a sign that the name resolution isn't working correctly, which would point the finger at the load balancer not being configured correctly.
Confirm the RPC CAS array works correctly natively before trying to add anything else to mix. You may have to reverse the registry changes and restart the Exchange services to be sure.
Simon.
Simon Butler, Exchange MVP
Blog | Exchange Resources | In the UK? Hire Me.
Good list to work through.
And if you have the Windows firewall running on the CAS servers, did you create exceptions for these two custom ports?
You also want to validate using netstat -ano OR netstat -anob that the RCA and AB ports are actually picking up the changes that you made and are listening on the correct ports. I have seen too many cases of people swapping the DWORD and STRING values around, and calling the wrong one parametersSystem :)
Just saying....
Cheers, Rhoderick NOTICE: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
-
יום חמישי 26 אפריל 2012 20:15
Hello,
I already tried by change DNS entry by the Exchange Server but this is the same issue.
When i look with netstat -anob i have my parameters :
TCP 0.0.0.0:60000 0.0.0.0:0 LISTENING 12352
[Microsoft.Exchange.RpcClientAccess.Service.exe]
TCP 0.0.0.0:60001 0.0.0.0:0 LISTENING 1356
[Microsoft.Exchange.AddressBook.Service.exe]I doesn't have Firewall in the server
Really, i don't know why this is not work...
-
יום חמישי 26 אפריל 2012 22:16
Undo everything - including the registry changes. You still have too many modifications from the defaults to know where the problem is.
Simon.
Simon Butler, Exchange MVP
Blog | Exchange Resources | In the UK? Hire Me. -
יום חמישי 26 אפריל 2012 23:18
yea, you need to revert, but before you do that you might want to try from a client that is on the same network segment as the CAS servers, to rule out any network issues
Bulls on Parade
-
יום שישי 27 אפריל 2012 08:42
I have found something today, in fact this only with users who have created before the installation of Exchange 2010.
When a user is created now in Exchange 2003 and migrate in the 2010 everything is OK but not before...
Someone have an idea ?
- הוצע כתשובה על-ידי Simon_WuMicrosoft Contingent Staff, Moderator שבת 28 אפריל 2012 19:48
- הצעה כתשובה בוטלה על-ידי J.OHAYON שבת 28 אפריל 2012 20:06
-
יום רביעי 02 מאי 2012 02:08מנחה דיוןAre you able to restart the 2003 information store service? I have seen issues where it doesn't get updated and this happens.
Mike Crowley | MVP
My Blog -- Planet Technologies
-
יום רביעי 02 מאי 2012 08:16
Are you able to restart the 2003 information store service? I have seen issues where it doesn't get updated and this happens.
Mike Crowley | MVP
My Blog -- Planet TechnologiesReally, restart a service from the 2003 for a problem in 2010 ???
But i have already restart the server after installing exchange 2010. But i can try that tonight
-
יום רביעי 02 מאי 2012 13:25מנחה דיוןI meant if the profiles aren't updating. you said this is only affecting old users, right? Does it work when you create a brand new outlook profile for the same set of old users?
Mike Crowley | MVP
My Blog -- Planet Technologies- נערך על-ידי Mike CrowleyMVP, Moderator יום רביעי 02 מאי 2012 13:27
-
יום רביעי 02 מאי 2012 14:24
I meant if the profiles aren't updating. you said this is only affecting old users, right? Does it work when you create a brand new outlook profile for the same set of old users?
Mike Crowley | MVP
My Blog -- Planet Technologies
The problem is on person was created on Exchange 2003 before the installation of Exchange 2010 and migrate to the exchange 2010 -
יום חמישי 03 מאי 2012 01:46מנחה דיון
Hello,
You may need to compare the attributes between a good user and a problematic user.
[Dump the attribute of the new created user and a problematic user]
===============================================
Pease export the following information on both of a good user and a problematic user so that I can compare with them.
On the DC\GC server, open Command Prompt, type the commands, compress and send the output files to me.
ldifde -f c:\<Name of User>.txt -d "distinguishedName of User"
Here is the detailed steps for getting the distinguishedName of a user:
a. Run the Adsiedit.msc from a command prompt.
b. Expand “Domain”->”DC=domainName,DC=com”->”CN=Users”
c. Right click on ”CN=the problematic user name”, click “Properties”.
d. Find the attribute “distinguishedName” attribute. Double click copy the value of it.
Thanks,
Simon
-
יום חמישי 03 מאי 2012 16:50
Hello,
You may need to compare the attributes between a good user and a problematic user.
[Dump the attribute of the new created user and a problematic user]
===============================================
Pease export the following information on both of a good user and a problematic user so that I can compare with them.
On the DC\GC server, open Command Prompt, type the commands, compress and send the output files to me.
ldifde -f c:\<Name of User>.txt -d "distinguishedName of User"
Here is the detailed steps for getting the distinguishedName of a user:
a. Run the Adsiedit.msc from a command prompt.
b. Expand “Domain”->”DC=domainName,DC=com”->”CN=Users”
c. Right click on ”CN=the problematic user name”, click “Properties”.
d. Find the attribute “distinguishedName” attribute. Double click copy the value of it.
Thanks,
Simon
Can i have your mail address because they have some many information...
Julien
-
יום שני 07 מאי 2012 16:22
Hi !
The problem is resolve ! Thanks everyone but an support engineer for critical issue has found the problem !
In fact, Kerberos has not configure on all Exchange server but we force Kerberos on Outlook :
http://technet.microsoft.com/en-us/library/ff808312.aspx
Julien
Thanks again everyone !
- סומן כתשובה על-ידי J.OHAYON יום שני 07 מאי 2012 16:22
.png)
