Test-OWAConnectivity Failing

[Seth P]

My Exchange monitoring is going well, one of my last sticking points is on my
Client Access servers. The test-owaconnectivity cmdlet always fails when it
runs on both the external & internal tests, with error "The test was unable
to establish a connection to Outlook Web Access". The only time it will run
properly is if I use the -url parameter and use the server's actual FQDN,
such as https://server1.ourdomain.com. The problem with this is that I have
to manually authenticate the test, so using it in a SCOM rule is an issue.
Also, I can run the test from any other Exchange box and it will run fine,
but the SCOM agent runs it locally, so that solution isn't viable. I think
the problem might be with our certificates, but I don't know where to begin
troubleshooting this, as I'm not a cert expert, and I can't just go mucking
with our certs while the server is in production. Our servers are patched
with Rollup 8. Any suggestions would be welcome.

Thanks,
Seth

[Steven Halsey [MSFT]]

For starters check the internal and external URL that are set on each of
your client Access Servers (get-owavirtualdirectory in Exchange powershell).
Make sure these are set to the same URLs as certificates are on the server.
For instance you said you use the url https://server1.ourdomain.com , but
the default will be set to https://server1.ourdomain.com/owa.

Check to be sure the Client Access Servers can access the correct DNS
records for the URLs you can set by using a DNS tool like nslookup.exe.
Often the problem lies in the Client Access server being unable to resolve
the URL because the URL lives on a DNS inaccessible by the Client Access
Servers.

If you are using Load Balancing or a fire wall check to be sure each Client
Access can either access the owa virtual directory on other servers, or only
ever tests itself. Due to duplex settings. Check out
http://technet.microsoft.com/en-us/library/cc732592.aspx#BKMK_C, especially
There is no response when using ping to access a host's dedicated IP
addresses from another cluster host.
--
Steven Halsey [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Seth P
My Exchange monitoring is going well, one of my last sticking points is on my
Client Access servers. The test-owaconnectivity cmdlet always fails when it
runs on both the external & internal tests, with error "The test was unable
to establish a connection to Outlook Web Access". The only time it will run
properly is if I use the -url parameter and use the server's actual FQDN,
such as https://server1.ourdomain.com. The problem with this is that I have
to manually authenticate the test, so using it in a SCOM rule is an issue.
Also, I can run the test from any other Exchange box and it will run fine,
but the SCOM agent runs it locally, so that solution isn't viable. I think
the problem might be with our certificates, but I don't know where to begin
troubleshooting this, as I'm not a cert expert, and I can't just go mucking
with our certs while the server is in production. Our servers are patched
with Rollup 8. Any suggestions would be welcome.
Thanks,
Seth