Looking for ejabberd docs?

To access the most up-to-date ejabberd documentation, please visit docs.ejabberd.im »

connecting problem other than localhost

Submitted by catav on Mon, 2008-03-24 20:41

Hello,
I installed ejabberd on debian etch from process-one.net. It works on local machine. I can connect on local as user or admin. But i can't connect to server from my LAN. Server machine accessible from LAN, there where no firewall rules to block connection requests.
How can i acces to ejabberd, how can i use it accross LAN.
Thanks in advance.

Zeki Çatav M.D.

There are several

Submitted by mfoss on Tue, 2008-03-25 00:17.

There are several solutions.

For example, if the machine that runs the server is accesible by other machines in your LAN with the name 'machineserver', for example, then you can call your Jabber server with that name. For that, edit ejabberd.cfg:

{hosts, ["machineserver"]}.

In the other machines, tell in the Jabber client to connect to the Jabber server 'machineserver'.

There are several solutions

Submitted by catav on Tue, 2008-03-25 06:44.

Hello,
My server named in LAN as kvc and full name is kvc.tyih.gov.tr
Other machines find it without any problem with this name. ejabberd.cfg file contains following line;
{hosts, ["kvc.tyih.gov.tr"]}
But i can't connect to server.

Thanks.

Maybe a firewall blocks port 5222

Submitted by mfoss on Tue, 2008-04-01 11:15.

catav wrote:

My server named in LAN as kvc and full name is kvc.tyih.gov.tr
Other machines find it without any problem with this name. ejabberd.cfg file contains following line;
{hosts, ["kvc.tyih.gov.tr"]}
But i can't connect to server.

So, the other machines can reach the server, but Jabber client can't login in the ejabberd server.

Maybe there is a firewall blocking the connection to port 5222 TCP. You can ensure that the other machines can access the port 5222 with telnet.

In this example I verify that my machine can connect to a Jabber server, port 5222:

$ telnet jabberes.org 5222
Trying 83.149.104.137...
Connected to jabberes.org.
Escape character is '^]'.
asdasd
<?xml version='1.0'?>...
Connection closed by foreign host.

You can also take a look at the log files ejabberd.log and sasl.log. Check what appears in the files when you login with a Jabber client in the server machine; and in other machines.

problem solved

Submitted by catav on Tue, 2008-04-01 20:28.

Hello,
I found the problem. When other machines try to connect ejabberd server NAT use a real ip and old port 5223 (195.xxx.xxx.xxx:5223) for client connection.
Network doesn't respond ejabberd traffic like other request. In the same stuaiton web request to port 80 doesn't fails. Request to apache works fine but ejabberd requests fail.
Net admin abolishes NAT and clients connect now to ejabberd.
Thanks for your suggestions.