ejabberd Installer issues
 

Perhaps it isn't the installer at fault here. I've installed ejabberd in /opt/ejabberd-1.1.1/ I've started it using the scripts that the installer placed on my desktop. Is there some sort of configuration on the command line before I can get to the web based administration? The connection is being refused everytime. Firewall on this machine is completely disabled. ps -A reveals one process that I hadn't seen before, a program called Beam after running the start scripts. I assume this is the framework that ejabberd uses to do it's job.

So if it is started successfully (which is reported by the html page when I launch the start script) why is the connection refused? No log file is present either after the "successful" startup.

I am assuming that ejabberd is using the default config file, unless I had to specify which I never did.

The computer is running Cent OS 4.

The server has an AMD 64. I'm not sure if this is actually running Cent OS in 64bit mode, and if it is maybe that's the issue? Is there a way to check this out?

I'm sorry that I didn't direct this question directly to the ejabberd site, but I've been getting frustrated wading through the info only to see lots and lots of configuration options, with little or no "beginner" type tutorials or howtos. Also google seems to reveal mostly irrelevant info, at least to me cause most of the results of my searches lead to non-english sites, or sites with little information on my specific issue.

Thank you in advance for any help you can give!
Nathan

I meant to research this last weekend but had other obligations to attend to. I've found a page with info regarding setup of a small jabberd implementation. Hopefully this will enable me to get the service up and running. Here's the link if anyone needs some help on the issue.

http://www.vanemery.com/Linux/Jabber/jabberd.html

I've found that documentation is sparse for most of these servers. I've never seen so many 404 errors in my life on one topic. :P I hope the availability of these pages isn't a result of crappy security in the protocol. Cause that would be scary.

Anyone know of some alternate protocols (preferabley GPL'd) for enterprise chat solutions?

[rant]
Perhaps my issue lies in the fact that I'm unaware of the current DNS setup within the company. My place of employment hired a third party to setup this network, and as a result everyone is in the dark about how and what is setup. I may have to contact our ISP, but if we do not have a FQDN for our server I may have to look into an alternative solution.
[/rant]

I believe my problem may have been that I was installing the Jabber server on my PDC (Samba) and if I remember correctly the PDC isn't actually a member of the domain<?>. If that is true then it explains why I couldn't connect to the server, Jabber servers IPs must reverse resolve in order for the server to work and being outside of the domain would make it very hard for it to do that. ;)

I've installed Wildfire on my terminal server and have now got an entire office setup and waiting to recieve their user accounts. Everyone here is so excited that this is actually working!

Three more offices to go!
Ah the satisfaction!

Setup
Server: Wildfire Homepage
Client: Coccinella Homepage