are your clients connection to port 5269? This is the server-2-server port and should not be used by clients. Are there any other errors or could you retry connecting to port 5222 or 5223 ?
Thank you for your reply. All clients are attempting to connect through port 5222. I found this in the warn log;
2006.02.06 12:37:39 Closing session due to incorrect hostname in stream header. Connection: org.jivesoftware.wildfire.net.SocketConnection@1c8b884 socket: Socket[addr=/192.168.0.122,port=56642,localport=5269] session: null
I just disabled the ‘‘server to server’’ component and user accounts were added through the Admin console on port 9090. Also had the client app try to connect to the secure port, which gave an error that the certificate was invalid (client is, therefor, talking to server) although afterwards the client never connected to the server. Very odd.
“incorrect hostname” let’'s my think of “_” in DNS names. Or the “to” attribute is missing in the XMPP stream. Are you able to trace the XMPP packets which are exchanged?
Your suggestion put this in the right direction. Isn’'t this a client2server issue rather than a server2server one? Both subnets are 255.255.255.0. The server name was modified several times although the client was connecting to the IP address and not the name.
I added the server’'s name to my local hosts file and changed the client to use username@hostname and it now connects to the server. Thank you very much!
This was not an issue with previous versions of Jive. Is there a way I can fix this, server side, as I do not wish to modify host files for every client. The Admin page would not save the Server name as an IP address.
I added the server’'s name to my local hosts file and
changed the client to use username@hostname and it
now connects to the server. Thank you very much!
This was not an issue with previous versions of Jive.
Is there a way I can fix this, server side, as I do
not wish to modify host files for every client. The
Admin page would not save the Server name as an IP
address.
Yes, there were some changes made for more strict handling of servername. But i thought it’'s only affecting s2s. Then using s2s you must use username@servername form then adding contacts. But for a local use IP should still work.
Well, i’'m with Wildfire 2.4.4, it has static IP - 192.168.12.41 and “jiveserver” name in server rc.conf and a line in hosts:
127.0.0.1 localdomain jiveserver
In Admin Console it’'s named jiveserver also.
When connecting new users i use username@jiveserver (and host: 192.168.12.41) in Exodus. But a lot of users are still logging as username@192.168.12.41 and it works. s2s is disabled. Maybe i’'m mising something about your problem?
P.S. BTW there were no mentions about that change in servername handling in changelog? I cant find anything about that, nor cant find a thread where we were discussing it with Gato.