Tuesday, December 7, 2010

Failure testing OCS 2007 R2 Edge server with https://www.testocsconnectivity.com/ with the message: “Connectivity Test Failed” and “Testing SSLCertificate for validity.”

Ran into an interesting failure while testing a newly deployed OCS 2007 R2 Edge server on a Windows Server 2008 R2 64-bit server that I thought was worth a blog post because what ended up fixing it seemingly had nothing to do with the error message. First off, I actually made the mistakes of selected 5061 as the port instead of 443 which was what I intended to do. The reason why I made this mistakes was:

  1. I did not select the auto discovery option because the ISP managed to incorrectly create the public SRV records 3 times.
  2. I didn’t pay attention while manually entering the settings.

Though I had selected the wrong port, I did learn something out of this and it was one of the many reasons that could possibly cause https://www.testocsconnectivity.com/ to throw the error message:

“Testing SSLCertificate for validity.”

Problem

You use https://www.testocsconnectivity.com/ to test your newly deployed OCS 2007 R2 Edge server but run into the following results:

clip_image001

Connectivity Test Failed

Test Details

Copy to Clipboard

Expand/Collapse

clip_image002

Testing the Remote Connectivity of user tluk@domain.com.

Specified Remote Connectivity test(s) failed. Please examine below details of specific reason for failure.

clip_image003

Test Steps

clip_image004

Attempting to Resolve the host name sip.domain.com in DNS.

Host successfully Resolved

clip_image005

Additional Details

IP(s) returned: 99.333.181.44

clip_image004[1]

Testing TCP Port 5061 on host sip.domain.com to ensure it is listening/open.

The port was opened successfully.

clip_image002[1]

Testing SSLCertificate for validity.

The SSLCertificate failed one or more certificate

clip_image006

Tell me more about this issue and how to resolve it

clip_image003[1]

Additional Details

A network connection error occured while communicating with the remote host: Exception Details: Message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Type: System.IO.IOException Stack Trace: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost, X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation) at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost) at TestOCSConnectivity.Tests.SSLCertificateTest.PerformTestReally() Exception Details: Message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Type: System.IO.IOException Stack Trace: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost, X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation) at System.Net.Security.SslStream.AuthenticateAsClient(String targetHost) at TestOCSConnectivity.Tests.SSLCertificateTest.PerformTestReally()

image

As I noted above, this can be caused by other reasons and the following is only one of the reasons.

Solution

What I found was that the edge servers weren’t defined in the Edge Servers tab in the Office Communications Server Global properties.

image

Once I filled in the servers, this error from https://www.testocsconnectivity.com/ (Microsoft Office Communications Server Remote Connectivity Analyzer) went away.

image

I found this extremely strange because the error referenced the SSL certificate yet this didn’t seem like something that would cause such an error.

image

1 comment:

cheaprsgoldforever said...

What Selections To Pick On Sash Windows In this day and age, you are able to discover a lot of choices in relation to picking an ideal window for the location of abode office 2010 key. Various types and styles of windows are readily available. Certainly one of one of the most common forms used in several properties nowadays will be the sash wooden windows. These windows are generally discovered in most homes that happen to be Victorian inspired. While their usage is prevalent throughout the Victorian era, their timeless beauty and elegance is nonetheless windows 7 upgrade key verified valuable up to now.

A lot of men and women that are into house making or dwelling improvement as of late prefer to utilize the sash sort of windows. This can be in view of the fact that there are many advantages that you could derive from working with them. They not just make your house appealing but they may be also terrific for power efficiency. They're a great addition into your house considering that they're able to match any style of household interiors too as exteriors. So if you would like a great windows key improvement within the appearance of one's household, you might want to settle on windows with superb excellent. The sashes are proven timeless and exceptional by means of the years.