troubleshoot s2s connection problem howto

Our ejabberd server is working fine for local users (with accounts on our server) and it works properly when I log in to a test account at jabber.org. I can see my jabber.org presence and exchange messages.

However, a company we work with has their own jabber server and we can't communicate with them any more. We used to be able to, but something has gotten broken/stuck and now we don't see each other's presence and can't exchange messages.

I have tried to telnet to their server on both port 5222 and 5269 and I seem to get legitimate responses, or at least XML error messages from them. So the communication link seems to work.

We have both stopped/restarted our servers with no change.

We run ejabberd and they run a standard jabber 1.4.2 server.

Any advice about how to trouble shoot this problem?

We run ejabberd and they run

We run ejabberd and they run a standard jabber 1.4.2 server.

It can be a problem in jabberd 1.4.2. AFAIR there is a bug in older jabberd versions that result in random s2s breakdown. But a more important reason for the other company to upgrade their jabberd installation is that there is a remotely exploitable vulnerability in their server.

--
sander

Syndicate content