Answered by:
TLS handshake Failed:192.168.2.50:5061 Error Code 0x80096004

Question
-
Hi , I am getting this error while trying to verify Edge server configuration. This is my configurations
Windows 2008 x64 Enterprise Ed.
IP Address : 192.168.2.50
Installed Applications: AD, DNS, Certification Authority & OCS Front End Server2007 R2 (Standard Edition)
This server works perfectly fine for users inside domain and autoconfig works fine too. Now I am trying to deployed Edge Server for external users. The setup installed just fine. I have assigned certificates for edge server using on line certificate authority which is my OCS Server certificate wizard.
Edge Server is installed on top of Server 2008 Ent. x64
Internal IP : 192.168.2.22
External IP : 88.96.xxx.xxx
But verification failed with error : TLS handshake Failed:192.168.2.50:5061 Error Code 0x80096004 outgoing TLS negotiation failed; HRESULT--2146869244
Can anyone help please.
As this is a test environment , I am not using any firewall to protect it.
Thanks
Wednesday, November 4, 2009 11:41 AM
Answers
-
Hi Guyz,
Thanks for all you help. I manage to sort it out. there are a problem with edge server port i assigned for port signaling that was creating problems. I change to port from 443 to 5061 and voillla it works.- Marked as answer by MuhammadBajwa Wednesday, November 25, 2009 12:40 PM
Wednesday, November 25, 2009 12:40 PM
All replies
-
Make sure that you have imported the Root/Issuing CA certs from your internal Enterprise CA into the Edge servers Computer Store. That error could indicate that the internal certificate issued to the Internal Edge interface (and the certificate on the internal Front-End server) is not trusted by the Edge Server.
See this blog article for more details: http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=72
Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCSWednesday, November 4, 2009 12:17 PMModerator -
Hi Jeff,
Thanks for coming back to me on this. I have followed the process but its didn't sort out the issue i was having. I am really freaked out as i have be working on this test environment for couple of days and could seem to figure this out :(
This is the exact error I am getting.
TLS handshake failed: 192.168.2.50:5061 Error Code: 0x80096004 outgoing TLS negotiation failed; HRESULT=-2146869244
Failure
[0xC3FC200D] One or more errors were detectedWednesday, November 4, 2009 1:47 PM -
Hi
Per your description, and i have do some research about it.
I agree with Jeff, the issue usually caused by the CERT problem, you should you must configure the certficate on the edge server internal interface correctly, you can refer to below link:
http://technet.microsoft.com/en-us/library/dd441270(office.13).aspx
Check the port of the edge server internal interface confiured correctly.
And please ensure that the CERT you issued configured properly.
Some related thread you can refer to.
http://social.microsoft.com/forums/en-US/communicationsserversetup/thread/9ef6bbdd-e6ba-4369-8401-c36667f726db/
http://social.microsoft.com/Forums/en-US/communicationsserversetup/thread/6ddfc69e-0bd7-4204-acbc-a4de91475025/
http://social.microsoft.com/Forums/en-US/communicationsserversetup/thread/e4bba44a-f9e2-4a0b-a38e-471b4f02c882/
http://social.microsoft.com/forums/en-US/communicationsserveredgeservers/thread/a3afca7a-c274-4061-8f0b-3b3fafce8099/
Hope those help.
Best Regards!Monday, November 9, 2009 9:31 AMModerator -
Hi, I have done some troubleshooting and in my event viewer the error is : Log Name: System Source: Schannel Date: 11/11/2009 12:54:42 Event ID: 36876 Task Category: None Level: Error Keywords: Classic User: N/A Computer: edge Description: The certificate received from the remote server has not validated correctly. The error code is 0x80096004. The SSL connection request has failed. The attached data contains the server certificate. Can you please help?Wednesday, November 11, 2009 1:53 PM
-
Hi Guyz,
Thanks for all you help. I manage to sort it out. there are a problem with edge server port i assigned for port signaling that was creating problems. I change to port from 443 to 5061 and voillla it works.- Marked as answer by MuhammadBajwa Wednesday, November 25, 2009 12:40 PM
Wednesday, November 25, 2009 12:40 PM