Hello, recently I have added 2 CAS Servers and setup NLB however I am just noticng that when trying to connect to owa usig the server internal hostname the 2 new CAS servers are not working and gives Page Cannot Be Displayed. Only the old CAS server loads OWA fine. What could cause this pls ? Exchange 2010

A CAS array has nothing to do with OWA. Do ensure that you haven't mixed things up. Have you changed the URL configuration on the CAS servers at all? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

yes in fact I set up a CAS server array to provide redundancy for the same CAS. No the internal url of the OWA for each CAS Server is different and is like this: https://casserver1.domain.local/owa https://casserver2 etc... Basically when I set CAS array I did not change any URL as regards to OWA

Hi Run those commands on both servers and paste the result in here Get-OwaVirtualDirectory | fl *url*Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

I would start by removing the NLB and any other changes that you made and verify that the CAS does work correctly without it. Did you test them before adding the NLB functionality? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hello, I had installed the 2 Client access servers and implimented CAS array immediately, however now I have removed the network load balancing and they are standalone CAS servers, I can see that in IIS there are the directories however when specifying by hostname I cannot get OWA working and I think actually nothing is working on both of them. Please correct me here, if I add CAS servers they work immediately after installing them or you need to associate them with mailbox server ?

Nothing else has to be done to a CAS for it to work. Therefore as long as it is at the same or higher patch level as the mailbox server with the mailbox on it, you should be able to load OWA and get connected. As you can't, that would tend to indicate one of three things is wrong: 1. The patch level isn't correct. 2. The self signed SSL certificate is corrupt - or the import didn't work, so the SSL session can't establish 3. It is a bad installation. It would be very surprising for two installations to be bad. Therefore I wouldn't expect the last one. If you can't see anything obvious wrong, then remove Exchange from the machines, remove IIS and reinstall. Do ensure that you have all of the prerequisites in place before installing Exchange again. Test the functionality before you do any advanced configuration like CAS Array, NLB etc. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

I am suspecting that it is a certificate issue, so for each CAS I add I have to manually add a certificate ( request it to the CA and import it )? Or can I use a certificate that it is already installed on another CAS server ?

Hello, recently I have added 2 CAS Servers and setup NLB however I am just noticng that when trying to connect to owa usig the server internal hostname the 2 new CAS servers are not working and gives Page Cannot Be Displayed. Only the old CAS server loads OWA fine. What could cause this pls ? Exchange 2010 Are you able to connect through the ip address instead of using the internal hostname?Pano Boschung, PageUp AG

I am suspecting that it is a certificate issue, so for each CAS I add I have to manually add a certificate ( request it to the CA and import it )? Or can I use a certificate that it is already installed on another CAS server ? Usually with multiple CAS servers you have a single certificate with all of the names in it, then export/import to the other servers. This is because most SSL providers will not allow multiple certificates with the same name in them - and you really need autodiscover.example.com in the certificate. Now the added complication is that you want to use NLB. A certificate you have on another server is unlikely to work, simply because it doesn't have the relevant names. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi acmsoft, I would do some troubleshooting as below: 1. confirm the exchange services work well 2. run exbpa on the exchange server to confirm some useful information 3. use get-owavirtualdirectory, and then post them here 4. use get-exchangecertificate and post them here 5. use test-owaconnectivity on the exchange server and post the result here About how to issue the certificate, please refer to below: http://technet.microsoft.com/en-us/library/bb851505(EXCHG.80).aspx http://technet.microsoft.com/en-us/library/dd351044.aspx Some related issue: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/144eecf0-1963-4768-a08a-7c06eb2a79f1 Regards! GavinPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.