0200274D means ECONNREFUSED. There's most likely nothing listening on port 700
on your local machine. The reason(1869) is gibberish and a known issue with
Winsock, so don't pay any attention to that.
The suggested solution would firstly be to ensure that something is listening
on port 700. Fur
On Thu, Jul 24, 2014 at 2:57 AM, Sharath B wrote:
> Admin,
>
> We are getting following error while connecting to server.
>
> 4992:error:0200274D:system
> library:connect:reason(1869):.\crypto\bio\bss_conn.c:269:host=localhost:700
> 4992:error:20073067:BIO routines:CONN_STATE:connect
> error:.\cry
Admin,
We are getting following error while connecting to server.
4992:error:0200274D:system
library:connect:reason(1869):.\crypto\bio\bss_conn.c:269:host=localhost:700
4992:error:20073067:BIO routines:CONN_STATE:connect
error:.\crypto\bio\bss_conn.c:273:
Please suggest the solution.
Regards,
S
Admin,
I have recently upgraded to openssl version 0.9.8za on windows server 2008,
the client connections are failing at BIO_do_connect. Please suggest what
need to be done.
Regards,
Sharath B
CJ Holmes <[EMAIL PROTECTED]> writes:
> on 9/17/01 10:50 AM, Eric Rescorla at [EMAIL PROTECTED] wrote:
>
> >> I get the same error connecting from other client machines using Netscape
> >> 4.7, but not if I use 4.7.5. There's clearly a bug in Netscape 4.7 and
> >> earlier versions, but why is i
on 9/17/01 10:50 AM, Eric Rescorla at [EMAIL PROTECTED] wrote:
>> I get the same error connecting from other client machines using Netscape
>> 4.7, but not if I use 4.7.5. There's clearly a bug in Netscape 4.7 and
>> earlier versions, but why is it just affecting our implementation of
>> OpenSSL
CJ Holmes <[EMAIL PROTECTED]> writes:
> I get the same error connecting from other client machines using Netscape
> 4.7, but not if I use 4.7.5. There's clearly a bug in Netscape 4.7 and
> earlier versions, but why is it just affecting our implementation of
> OpenSSL?
That's a good question.
> I
on 9/14/01 7:14 PM, Eric Rescorla at [EMAIL PROTECTED] wrote:
> Just because the client sends a bogus CSS message, why would this
> cause the server to do so? I'm wondering if you have a networking
> problem. Did you collect these traces with a sniffer or via your
> program? If you did so via you
