1
Vote

Websocket error.. connects in 3rd attempt

description

We are using websocket4net (v 0.14.1) in our application. This issue of websocket error unexpectedly is happening on Windows 7 machine only and not with windows 8 or 10.

On windows 7 machine we get following websocket exception..

Web socket error: System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The message received was unexpected or badly formatted^M
--- End of inner exception stack trace ---^M
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)^M
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)^M
at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult)^M
at SuperSocket.ClientEngine.SslStreamTcpSession.OnAuthenticated(IAsyncResult result)^M


i have seen the wireshark traces but nothing has helped yet. Wireshark traces are attached with server ip address = 123.255.13.242 and client IP address = 10.221.12.50 and clients tries websocket connection at port 36008. Our application tries for a websocket connection to the server and get this exception always in first 2 attempt, then the websocket connection is established in 3rd attempt

The websocket connection connects to server port 36008 using TLS v1.2 for the connection with the server.

file attachments

comments

abhirajgandhi wrote Oct 19, 2016 at 9:55 AM

Please provide your comments !

Thanks,
Abhiraj