ejabberd 1.1.2 on win2003 can't connect

Hi all,

I've downloaded the ejabberd 1.1.2 win32 installer and installed it on a win2003 server so we can have IM inside our company. I'm able to start the server and access the webadmin without any problems. I'm also able to create users from within the webadmin without a problem, but I cannot seem to connect from a client. I've tried with PSI, Miranda and Gaim, but to no avail. It can't seem to make a connection. If I try to connect telnet (telnet {hostname} 5222) i get a blank telnet screen, then it bumps right back to the prompt.

I haven't got a clue as to what I'm doing wrong. Can anybody help?

Not sure this helps.

Used the windows installer. Admin works. Now from behind the firewall, i used webjabber (webjabber.net/live test/use browser. login id @ and the password (and then login, did not even have to enter server name or address) you used when you set jabber up (or one of the user logins you made). I was able to login and instant message with users setup through the admin screen (you can open multiple sessions of webjabber). I was also able to do it with a pandion (a jabber client application). You should also check in a web browser that you get a response to http://:5222.

I do have another problem though: I am unable to communicate with users outside of my domain (for example gmail). I get response on port 5222 and port 5269 (even from outside my firewall). Any suggestions?

No dice

Thanks for your reply, but it didn't work I'm afraid. I got a message that said 'failure' (not a particularly nice thing to say ;)
Any other ideas?

did you download the installer over the last couple of days?

I saw that they fixed a problem a couple of days ago. Did you open the right ports on your router?

Works!

Hi thegallier, thanks for helping out. I got it working! The problem was a proces (jabadns.exe) from our previous server (jabberD) that was still running, effectively blocking ejabberd from running as expected. Hope this helps someone.

Thanks again!

Check log files

Maybe the log files include interesting information: ejabberd may not be able to start the 5222 listeners, or it shows an error when you try to connect.

Syndicate content