We have 2 Exchange 2010 client access servers in a CAS array, this works fine. Outlook clients and systems point to the CAS array address. Both are also Hub Transport servers
We have 1 other CAS on the same network that is solely used for OWA. This only has the Client Access role.
Occasionally outlook clients will try to connect to this 3rd CAS rather than the proper CAS array.
How can I stop clients connecting to this 3rd CAS? I dont want clients to ever use this instead of the array.
I was thinking of using the windows firewall on the server itself to reject the outlook clients having access to it. These outlook clients are all within a contiguous range of IP addresses so I would just block that range.
But is there a better way to stop it advertising itself and taking requests away from the CAS array?