Re: warning Connect failed

2012-02-02 Thread Hamid.Shahid
message in context: http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp7229984p7247024.html Sent from the Apache Qpid users mailing list archive at Nabble.com. - Apache Qpid - AMQP Messaging Implementation Project: http

Re: warning Connect failed

2012-02-01 Thread Cliff Jansen
- Hamid > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp7229984p7243260.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > - >

Re: warning Connect failed

2012-02-01 Thread Hamid.Shahid
P.S. I have also tried it with the host name and get the following error; 2012-01-25 18:08:09 notice SSL negotiation failed to :10170: The target principal name is incorrect. Best Regards, - Hamid -- View this message in context: http://qpid.2158936.n2.nabble.com/warning-Connect-failed

Re: warning Connect failed

2012-02-01 Thread Hamid.Shahid
he certificate support for the client side. Many thanks. -Hamid. -- View this message in context: http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp7229984p7242637.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --

Re: warning Connect failed

2012-01-31 Thread Cliff Jansen
Hi Hamid, I am confused. It was explained to you in November that client side certificates were not yet implemented in the Windows implementation. Yet here it looks like your server will not negotiate the ssl connection without a client certificate. Am I misunderstanding what you are trying to d

Re: warning Connect failed

2012-01-31 Thread Jakub Scholz
Hi Hamid, The error you get in Chrome is caused by your certificate being loaded only as a trusted peer on the broker. This is an issue we had with Java applications - when you use signed certificates, the broker gives you a list of supported certification authorities and the application selects a

Re: warning Connect failed

2012-01-31 Thread Hamid.Shahid
both in .pem format) and connects to the same server and I was able to establish the connection with the server which shows the certificates are fine with SSL. But when it comes to the QPID and SChannel then I am getting these errors. -Hamid. -- View this message in context: http://qpid.21589

Re: warning Connect failed

2012-01-31 Thread Cliff Jansen
gt;> I am getting the following error when I try to connect via my client code. >> After placing all the certificates in the "Third-Party Root Certification >> Authorities" >> >> 2012-01-25 18:08:09 notice SSL negotiation failed to :10170: The >> target

Re: warning Connect failed

2012-01-30 Thread Jakub Scholz
ry to connect via my client code. > After placing all the certificates in the "Third-Party Root Certification > Authorities" > > 2012-01-25 18:08:09 notice SSL negotiation failed to :10170: The > target principal name is incorrect. >  2012-01-25 18:08:09 warning C

Re: warning Connect failed

2012-01-30 Thread Hamid.Shahid
NULL, &sendBuffDesc, &ctxtAttrs, NULL); regards, Hamid. -- View this message in context: http://qpid.2158936

Re: warning Connect failed

2012-01-27 Thread Gordon Sim
principal name is incorrect. 2012-01-25 18:08:09 warning Connect failed: The target principal name is incorrect. (..\..\..\..\..\..\..\..\qpidc-0.12\src\qpid\client\windows\SslConnector.cpp:111) Please let me know, what does it mean and how can it be rectified. Are you using the correct hostna

warning Connect failed

2012-01-27 Thread Hamid.Shahid
5 18:08:09 warning Connect failed: The target principal name is incorrect. (..\..\..\..\..\..\..\..\qpidc-0.12\src\qpid\client\windows\SslConnector.cpp:111) Please let me know, what does it mean and how can it be rectified. Thank you. regards, Hamid. -- View this message in context: http://qpid.