This is, unfortunately, not an openssl problem. If you can use 'openssl s_client -connect host:port' to figure out what the connection is doing, it might help you track down what's going on -- but since it's not an openssl problem, we really can't help you.
-Kyle H On Wed, Jul 23, 2008 at 12:09 PM, Foreacre, Craig A. CTR <[EMAIL PROTECTED]> wrote: > Hi, > > > > I hope that you can help me with this. > > > > I have an application that uses ssl. I ran some MS updates and now ssl > doesn't work anymore. I have reinstalled IIS, ran windows repair got a later > version of SSLeay32 and libeay32, but to no avail. I used httpwatch and I > get this error > > > > ERROR_INTERNET_SECURITY_CHANNEL_ERROR > > > > I have other servers running IIS with SSL and they work fine. This server > got hosed somehow. > > > > If I try to reregister the dlls the entry point cannot be found. > > > > I have googled this to death and cant come up with anything. > > > > Please HELP! > > > > Thanks in advance, > > > > Craig Foreacre > > Application Developer/Knowledge Content System Manager > > 2090 Child St > > Naval Hospital Jacksonville > > Jacksonville, FL 32214 > > 904.542.9100 > > > > This electronic mail and any attachments may contain information that is > subject to the Privacy Act of 1974 and the Health Insurance Portability and > Accountability Act (HIPAA) of 1996. Use and disclosure of protected health > information is for OFFICIAL USE ONLY, and must be in compliance with these > statutes. If you have inadvertently received this e-mail, please notify the > sender and delete the data without forwarding it or making any copies > > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
