PDA

View Full Version : Having problems connectiong to server.


lvg65
07-02-2008, 08:04 AM
New to jabber...


but i installed... Openfire 3.5.2

when server runs this is what i get... i had set it up Admin console is up and running... but when i try to use the client i tipe the IM in and it says cannot find server... what am i doing wrong?

Jehan
07-02-2008, 10:34 AM
The question is to know whether your server is well running as a first point, if it is accessible as a second, and if it is well configured as the third.

1/ For the first point, a basic test is to get a bare connection with it, the simpler method being telnet. And to be even more sure you are not mixing software issues with network, do this locally on the server (through ssh most likely):
telnet localhost 5222
Here I am supposing you kept the default port value, so 5222. If the connection holds, something is listening. And to be sure this is well the Jabber server, type anything, then entry. You will receive an error xml element, then the connection will close. Something similar to this:
<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='none' from='your server domain' version='1.0'><stream:error><xml-not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error></stream:stream>Connection closed by foreign host.

2/ For the second point, do the same test, but remotely from an outside computer and using the address you would like to use as your jabber domain:
telnet myjabberdomain 5222
If it doesn't work, then the issue is about network. If the "server" is in its material meaning in the sentence "cannot find server", you will be most likely in point 1/ or 2/.

3/ Finally for the last test if all of this worked, then the missing server is probably the "logical" meaning of a server. I think the reason would be that your server is up and accessible, but simply badly configured and does not consider your wanted domain as its own domain (even though it is it!). For this, simply use a Jabber client with an xml console and activate this latter before connecting. Then spy on the exchanged xml elements. You should see probably the error at the beginning. Your client will send something like this (example.com being replaced by your own domain):

<stream:stream
xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams'
to='example.com'
version='1.0'>

And your server is probably answering a failure element directly. Tell us the exact error and check your server's configuration.