Hi Hamid, What happens if you try to connect using Internet Explorer on your Windows machine? Using the following in the address bar:
https://amqserver.rest.com:10170 where "amqpserver.rest.com" is the name of the server as it appears in the certificate. Usually if I have a certificate related problem, I try to make IE happy first. Even though you don't get an interesting web page (obviously), if you get anything at all, without an intervening error mesage about the certificate, you are past initial hurdles. You need this to work first. However, I note several things. If I have a certificate problem my error message resembles: 2012-01-30 18:47:36 notice SSL negotiation failed to test1.foo.bar:6789: The certificate chain was issued by an authority that is not trusted. In particular "test1.foo.bar" is not an ip address as in your case. The fact that you see an ip address is suspicious (hence Gordon's initial query). Also a web search of your particular error message "The target principal name is incorrect" seems associated with kerberos authentication or other complex domain setups that are probably beyond anything Qpid developers have tried yet. Are you able to bypass DNS altogether and put the server's name in your host file? If none of the above helps you out, are you able to post the server's certificate? Cliff On Mon, Jan 30, 2012 at 10:28 AM, Jakub Scholz <ja...@scholz.cz> wrote: > Hi Hamid, > > Are you actually using a "Third-Party Root Certification Authority" > certificate - e.g. Verisign? Or do you have only a public key of a > signed or self-signed certificate? Couldn't that be the problem? > > I also agree with Gordon that you should not use the IP address to > connect to, but the hostname as mentioned in the certificate used by > the broker. You may need to change your hosts file to get the hostname > routed to the IP address ... > > Regards > Jakub > > On Fri, Jan 27, 2012 at 16:36, Hamid.Shahid <hamid2...@hotmail.com> wrote: >> Hi, >> >> >> 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 <server-ip>:10170: The >> target 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. >> >> Thank you. >> >> regards, >> Hamid. >> >> -- >> View this message in context: >> http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp7229984p7229984.html >> Sent from the Apache Qpid users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:users-subscr...@qpid.apache.org >> > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscr...@qpid.apache.org > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
