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

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 Neth

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

2010-12-25 Thread Fastream Technologies
astream.com> > To: "ICS support mailing" > 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 a

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

2010-12-25 Thread Francois PIETTE
M 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 machi