<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Putting the list back on CC (again).<div><br></div><div><div><div><div>On 16 May 2013, at 12:24, Balachandar R.A. wrote:</div><blockquote type="cite"><p>Yes, all these are correct. I shall try wireshark and see</p>
</blockquote><div>Thanks.</div><br><blockquote type="cite"><div class="gmail_quote">On 16 May 2013 16:18, "Tim Watson" <<a href="mailto:tim@rabbitmq.com">tim@rabbitmq.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div style="word-wrap:break-word"><div>Right. So, just to be clear then...</div><div><br></div><div>* you are running the broker on 40.221.94.235</div><div>* you have not altered the permissions on this broker at all</div>
<div>* you are running a client, attempting to connect to that broker, from some other host B</div><div>* you can telnet from host B to 40.221.94.235 on port 5672</div><div>* when your code (running on host B) calls ConnectionFactory#newConnection(), you get the com.rabbitmq.client.PossibleAuthenticationFailureException</div>
<div><br></div><div>Is that all correct? If so, please run a packet sniffer (such as wireshark) on both the broker and client host machines, to ensure that the network is transmitting information between the two hosts correctly. This is a very odd problem and not something that we've seen before.</div>
<div><br></div><div>Cheers,</div><div>Tim</div></div></blockquote></div></blockquote></div><br></div></div></body></html>