08-17-2016 09:36 AM - edited 03-18-2019 06:16 AM
I've recently deployed a new VM Acano Server running v1.93 and having trouble connecting S4B/Lync 2013 clients, getting a "handshake error 104 on incoming connection X" I've completed the in and outbound dialing peers in Acano that support the calls as well as setting the static route from Lync to Acano. My company did deploy a new CA/PKI server so the server that provided the cert for Lync is different than the one on my new VM but not certain that that is causing the problem. On the DNS entry I did not specifically request an A record if that matters at all. I am seeing the calls hit the Acano bridge. Any help or guidance is greatly appreciated.
Solved! Go to Solution.
08-17-2016 05:48 PM
I'd make sure that the Acano and S4B servers can trust and validate each other's certificates? Handshaking errors are usually due to certificate issues, since S4B relies on TLS.
08-17-2016 05:48 PM
I'd make sure that the Acano and S4B servers can trust and validate each other's certificates? Handshaking errors are usually due to certificate issues, since S4B relies on TLS.
08-18-2016 09:42 AM
That was the issue Patrick. The Acano cert path didn't match the Lync static route so I issued another one and installed it and even though the certs are from different CA servers it's connecting now. Thank you!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide