Re: [twsocket] 10053 error occurring only on Win2008 (SP2) and not onWin7

2010-12-25 Thread Francois PIETTE 

Error 10053 is WSAECONNABORTED.
Software caused connection abort.
An established connection was aborted by the software in your host computer, 
possibly due to a data transmission time-out or protocol error.

http://msdn.microsoft.com/en-us/library/ms740668(v=vs.85).aspx

--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be


- Original Message - 
From: Fastream Technologies ga...@fastream.com

To: ICS support mailing twsocket@elists.org
Sent: Saturday, December 25, 2010 8:24 AM
Subject: [twsocket] 10053 error occurring only on Win2008 (SP2) and not 
onWin7




Hello,

With the HttpCli, I get 10053 when lots of consecutive POSTs are made with
SSL. I first thought it is related to the 4096 bit self-signed cert we 
used

but it does not happen on Win2008. The test machine is remote (in the
Netherlands) and when I run the GUI (web client) from here on my Win7, it
works as expected. It also works if I run it against the same ICS web 
server

on localhost. But when I run the client on Win2008 remotely on RDP, it
crashes! Since all but all customers use Win2008, I need some help with
this!

Happy holidays to all of you!

SZ
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be 


--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Re: [twsocket] 10053 error occurring only on Win2008 (SP2) and not onWin7

2010-12-25 Thread Arno Garrels 
Fastream Technologies wrote:
 Hello,
 
 With the HttpCli, I get 10053 when lots of consecutive POSTs are made
 with SSL. I first thought it is related to the 4096 bit self-signed
 cert we used but it does not happen on Win2008.

So it works on 2008?

 The test machine is
 remote (in the Netherlands) and when I run the GUI (web client) from
 here on my Win7, it works as expected. It also works if I run it
 against the same ICS web server on localhost. But when I run the
 client on Win2008 remotely on RDP, it crashes! 

So it crashes on 2008? 
Any error message, stack trace etc.?

Isn't server 2008 SP2 64-bits only?

-- 
Arno Garrels



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Re: [twsocket] 10053 error occurring only on Win2008 (SP2) and not onWin7

2010-12-25 Thread Fastream Technologies 
Dear Arno,

It does work on Win7 but does NOT work on Win2008 and Win2008R2. It works
perfectly with NO SSL on all Windows. The HTTP client does not raise any
exception--just 10053 and StatusCode=0 issues. I have uploaded the cert/pkey
at,

http://www.fastream.com/ics/certpkey.zip

It is a 4096-bit self-signed cert for testing. It works for 8-10 POSTs then
this error occurs. We use ICS-based web server for testing with the
following properties:

adminHTTPSSLServer = new TSslHttpServer(NULL);
adminHTTPSSLServer-OnGetDocument = HTTPServerGetDocument;
 adminHTTPSSLServer-OnHeadDocument = HTTPServerHeadDocument;
adminHTTPSSLServer-OnPostDocument = HTTPServerPostDocument;
 adminHTTPSSLServer-OnPostedData = HTTPServerPostedData;
adminHTTPSSLServer-OnClientDisconnect = HTTPServerClientDisconnected;
 adminHTTPSSLServer-OnHttpRequestDone = HTTPServerClientRequestDone;
adminHTTPSSLServer-MaxClients = 200;
 adminHTTPSSLServer-ListenBacklog = 200;

adminHTTPSSLContext = new TSslContext(NULL);
 adminHTTPSSLContext-SslVerifyPeer = false;
adminHTTPSSLContext-SslOptions  sslOpt_MICROSOFT_SESS_ID_BUG 
sslOpt_NETSCAPE_CHALLENGE_BUG  sslOpt_NETSCAPE_REUSE_CIPHER_CHANGE_BUG 
sslOpt_SSLREF2_REUSE_CERT_TYPE_BUG  sslOpt_MICROSOFT_BIG_SSLV3_BUFFER 
sslOpt_SSLEAY_080_CLIENT_DH_BUG  sslOpt_TLS_D5_BUG 
sslOpt_TLS_BLOCK_PADDING_BUG, sslOpt_TLS_ROLLBACK_BUG  sslOpt_NO_SSLv2 
sslOpt_NETSCAPE_CA_DN_BUG  sslOpt_NO_SESSION_RESUMPTION_ON_RENEGOTIATION
 sslOpt_NETSCAPE_DEMO_CIPHER_CHANGE_BUG;
 adminHTTPSSLContext-SslVerifyPeerModes  SslVerifyMode_PEER;
adminHTTPSSLContext-SslSessionCacheModes  sslSESS_CACHE_NO_INTERNAL_STORE
 sslSESS_CACHE_NO_INTERNAL_STORE;
 adminHTTPSSLContext-SslCipherList = ALL:!ADH:!DES:RC4+RSA:@STRENGTH;
adminHTTPSSLContext-SslVersionMethod = sslV23_SERVER;
 adminHTTPSSLContext-SslSessionTimeout = 300;
adminHTTPSSLContext-SslSessionCacheSize = 20480;
 adminHTTPSSLContext-SslDefaultSessionIDContext = ADMIN_SERVER;

HTH,

SZ

On Sat, Dec 25, 2010 at 12:43 PM, Arno Garrels arno.garr...@gmx.de wrote:

 Fastream Technologies wrote:
  Hello,
 
  With the HttpCli, I get 10053 when lots of consecutive POSTs are made
  with SSL. I first thought it is related to the 4096 bit self-signed
  cert we used but it does not happen on Win2008.

 So it works on 2008?

  The test machine is
  remote (in the Netherlands) and when I run the GUI (web client) from
  here on my Win7, it works as expected. It also works if I run it
  against the same ICS web server on localhost. But when I run the
  client on Win2008 remotely on RDP, it crashes!

 So it crashes on 2008?
 Any error message, stack trace etc.?

 Isn't server 2008 SP2 64-bits only?

 --
 Arno Garrels




--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be