Hi Faisal.
Thanks for your reply.
"is it that they open their outlook client and it
dosent connect???" Exactly, that's the problem.
I'll describe better the situation:
- We have two CAS servers, load balanced as Windows NLB
- The idea is to use F5 LTM as load balancing technology.
- I've set all Exchange services: OWA, Autodiscover, RPC, etc..
following the deployment guide:
http://www.f5.com/pdf/deployment-guides/microsoft-exchange2010-ia
pp-dg.pdf.
- Everything seems to work fine, except that some clients using Outlook 2010 can not connect to exchange server.
- The strange thing is that it always fails from the same computerd.
From computers on the same VLAN, some fail and others do not.
- We have logged the connections. When using the Outlook 2010 client, always begins with an RPC connection to port 135.
- In the good and correct situation, there are connections to RPC ports 7575 and everything works fine.
- In the bad situation, there are only attempts of RPC connections
to port 135 and a message appears on the client, something like "Outlook
can not connect to the Exchange server."
We have seen the following message captured with Network Monitor
"DCERPC174Bind_ack: call_id: 2 Fragment: Single Unknown result (3),
reason: Local limit exceeded"
Can you help us? Have you had any similar cases?
Our suspicion is that the problem may be related to any further
modification to be carried out in the CAS server configuration,
something related to authentication and FQDN.
When you ask me about certificate, do you mean certifacates installed in F5 or in CAS servers?
Thank you
Nimbostratus