SSL protocol issue on https connection on Windows Server 2003 .NET 4.0

i run web service (https://www.gloebit.com) , have developed plugin opensimulator virtual world platform.  this works customers running opensimulator on linux servers.  opensimulator , our plugin both written in c#.  the opensimulator thread crashes when opensimulator server attempts make https call our web server (exception stack trace below).  as said, works fine when opensimulator run via mono on linux server.  i crash customer running windows server 2012 (https://social.technet.microsoft.com/forums/windowsserver/en-us/15e7f5bd-c8ad-4a3c-9a53-0f3a8c632690/valid-certificate-fails-validation-procedure-but-works-from-ie-on-server?forum=winserver8gen#15e7f5bd-c8ad-4a3c-9a53-0f3a8c632690), may more generic windows server issue.  i've used ssl checker (https://www.sslshopper.com/ssl-checker.html#hostname=www.gloebit.com) verify our certificate , chain valid.  i've pulled ssl report (https://www.ssllabs.com/ssltest/analyze.html?d=www.gloebit.com&hideresults=on&latest) looks properl.  our server set use tls 1.2, tls 1.1 or tls 1.0.  from read, tls 1.0 should defaults on windows server 2003 , .net 4.0 our customer running on server.  the specific endpoint user attempting access our service is https://www.gloebit.com/oauth2/access-token/

i did research, , appeared exception caused ssl security protocol issue.  the suggested resolutions force system use tls, tls 1.0 should in protocols , since plugin within larger platform, can't modify security protocols suit our service.

how can our customer fix this?  is bug in windows server?

stack trace:

opensim.framework.servers.httpserver.basehttpserver [base http server]: handlerequest() threw exception 

system.net.webexception: underlying connection closed: unexpected error occurred on send. ---> system.io.ioexception: received unexpected eof or 0 bytes transport stream.

   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.forceauthentication(boolean receivefirst, byte[] buffer, asyncprotocolrequest asyncrequest)

   at system.net.security.sslstate.processauthentication(lazyasyncresult lazyresult)

   at system.net.tlsstream.callprocessauthentication(object state)

   at system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state, boolean ignoresyncctx)

   at system.threading.executioncontext.run(executioncontext executioncontext, contextcallback callback, object state)

   at system.net.tlsstream.processauthentication(lazyasyncresult result)

   at system.net.tlsstream.write(byte[] buffer, int32 offset, int32 size)

   at system.net.pooledstream.write(byte[] buffer, int32 offset, int32 size)

   at system.net.connectstream.writeheaders(boolean async)

   --- end of inner exception stack trace ---

   at system.net.httpwebrequest.getrequeststream(transportcontext& context)

   at system.net.httpwebrequest.getrequeststream()

   at gloebit.gloebitmoneymodule.gloebitapi.buildgloebitrequest(string relativeurl, string method, user user, string contenttype, osdmap parammap)

   at gloebit.gloebitmoneymodule.gloebitapi.exchangeaccesstoken(user user, string auth_code, uri baseuri)

   at gloebit.gloebitmoneymodule.gloebitmoneymodule.authcomplete_func(hashtable requestdata)

   at opensim.framework.servers.httpserver.basehttpserver.handlecontentverbs(oshttprequest request, oshttpresponse response)

   at opensim.framework.servers.httpserver.basehttpserver.handlehttprequest(oshttprequest request, oshttpresponse response)

   at opensim.framework.servers.httpserver.basehttpserver.handlerequest(oshttprequest request, oshttpresponse response)

hi,

microsoft ending support windows server 2003 operating system on july 14, 2015.if still running windows server 2003 in datacenter, need take steps plan , execute migration strategy protect infrastructure. migrating windows server 2016, microsoft azure or office 365, can achieve concrete benefits, including improved performance, reduced maintenance requirements, , increased agility , speed of response business.

---

best regards
cartman
please remember mark replies answers if help. if have feedback technet subscriber support, contact tnmff@microsoft.com

Windows Server  >  Windows Server General Forum