I installed ejabberd-1.0.0.exe (1,505 KB) & Erlang 5.4.12 on an intranet Windows 2003 server
When I run 'All Programs'--->'Ejabberd'--->'Start Ejabberd' I get...
Erlang (BEAM) emulator version 5.4.12 [threads:0]
Eshell V5.4.12 (abort with ^G)
(ejabberd@servernamehere)1>
When I attempt to register a new account using Psi from a client in the same subnet Erlang shows...
=INFO REPORT==== 3-Feb-2006::20:39:31 ===
I(<0.231.0>:ejabberd_listener:90): (#Port<0.305>) Accepted connection {{"clientip"},2456} -> {{"serverip"},5222}
Yet the PSI client reports the following error...
There was an error communicating with the Jabber server.
Details: Stream Negotiation Error: Host unknown
The PSI client is configured to connect on port 5222 to the value returned from "hostname" on the server which matches the entry under the "hosts" section of ejabberd.cfg
C:\Program Files\Ejabberd>hostname
servernamehere
% Host name(s):
{hosts, ["servernamehere"]}.
----
I am able to telnet from this client to the serverip on port 5222 but it just sits there.
When I attempt to type something I get the following error...
< ? xml version='1.0'? >< stream:stream xmlns='jabber:client' xmlns:stream='http://
etherx.jabber.org/streams' id='none' from='servernamehere' version='1.0' >< stream:error ><
xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/ >< /stream:error >
< /stream:stream >
(I added the extra spaces so that it would display properly)
----
Also - I am unable to access the web administrator page @ &
(The page cannot be found...)
----
I would greatly appreciate some assistance with this problem.
Please let me know if I can provide any additional information.
Thank you!
-T
I was able to resolve this
I was able to resolve this issue on a development box.
This is not related…but anyone viewing this should know that I left out some details in my post. If you do not understand JID please read the following…
Jabber ID
A Jabber ID or JID is the username or account name used to access a Jabber account. It usually take the form user@domain/resource, similar way to email addresses. The resource component enables a user to contact a particular access point logged into each account, e.g. user@domain.com/work and user@domain.com/home. The resource component is not necessary in order to contact a Jabber user.
Transports, agents, and other automated parts of the Jabber network may not have a user part to the JID. A common example would be the AIM transport, where the transport itself has a JID along the lines of aim.domain.com, and contacts on AIM would appear as .
In a similar way to Sendmail, accessing other protocols is possible with Jabber transports. Users can then contact from a client such as MSN Messenger using the JID form user%msn.com@msn.jabberserver.com.
Jabber ID's may not contain certain characters, such as @, : (a colon), or " (a double quote).