SLow outlook connection to exchange in an NLB and CAS array
Posted on 2012-09-06
Here is our configuration:
2 x Exchange 2010 servers running CAS & HT roles configured as a cas array
2 x Exchange 2010 servers running Mailbox roles only
Active directory domain domain.com (split scope)
Windows NLB configured using unicast
We have the cas array name and NLB configured both as cas.domain.com so pinging cas.domain.com resolved to the VIP of the NLB internally.
Outlook Anywhere and OWA clients connect to mail.domain.com so not the same name as cas array name
We have been seeing slow connections to outlook on the LAN whereby outlook is opened and it takes about a minute to connect to exchange - it will just sit there with connecting to exchange server. It does however get there in the end.
My worry is that the cas name is configured to use a name that is externally resolveable even though we have no external dns record for it and the external users connect to mail.domain.com I have been reading that this is not recommened practice?
Is someone able to verfy our configuration or suggest any troubleshooting metholds