Quantcast
Viewing all articles
Browse latest Browse all 19214

Changing the wrong CAS Server for clients

Hi,

I am dealing with an exchange organization not built by me from scratch so maybe i do not know some details about it but here is the problem i have now !

there are 3 CAS servers !

One is set to serve external clients so the external dns is set to redirect autodiscover and OWA clients to this server (some nat is done which i think is not important here)

so all external clients connect to CAS-3

the other CAS servers (in fact HUBCAS servers) are making a NLB (and so CAS array) together and as i saw, rpc client access is pointing to the array ! the array works ok and when one is out, the other one comes in.

but the main problem is here : I think so many clients in domain are connecting to the CAS-3 which was meant to serve outside clients !!

this is because when i go to outlook and hm.. Account Information menu i think it says that you can use owa with address https://CAS-3/owa and also the traffic flow can prove this ! (and i think test-email auto configuration also shows this .. anyway .. ) and this is very bad !

so first of all why this has happened ?

and here is what i intend to do :

1- no internal client outlook should go to this server and use it as its CAS from now on !

2- and all clients currently using that should change to the CAS array

i want to be sure that nothing happens if i completely block this server for clients !

Thanks


Viewing all articles
Browse latest Browse all 19214

Trending Articles