[JDEV] Server problems 1.2 & 1.4
tim.ferguson at cw.com
Fri Feb 2 13:22:17 CST 2001
I saw the same problems trying to get 1.4pre2 to work on Tru64. I had to
comment out the mod_auth_digest and mod_auth_0k jsm modules leaving the
mod_auth_plain one. This is OK with me as I have a module that does LDAP
authentication now, but it seemed to me that the hash's did not jive
Cable & Wireless
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
Sent: Friday, February 02, 2001 12:00 PM
To: 'jdev at jabber.org'
Subject: [JDEV] Server problems 1.2 & 1.4
I'm obviously doing something wrong or there is something wrong with my
configuration. I just brought up 1.4RC, and it is behaving the same way
that 1.2 behaved for me. I can use a client to connect with a new user, but
when that user quits and then tries to come back in, the user can't connect.
Right now WinJab can't even make that initial connection. Both WinJab and
JabberIM show a 10061 socket error (MyJabber says that the user is
unauthorized on the server). On the server side, I basically just see login
fail messages. On the 1.2 server I was seeing access problems to the spool
directory. It would claim no such file or directory when it (and the xml
files) did exist and the jabber user had full access. It seems to read the
xml file now, but denies access.
I am sitting on an Intranet behind a firewall. However, the clients and
server are are on the same ethernet segment. I compiled both jabber servers
with gcc. I am running them on a two processor Alpha under Redhat 7.0. The
clients I am using are all windows based; I've tried WinJab, JabberIM, and
MyJabber. Any idea as to what I might be doing wrong? I think I've read
all of the relevant documentation, but I haven't seen anything like this.
Thanks for any help.
al.gaspar at lrn.va.gov
jdev mailing list
jdev at jabber.org
More information about the JDev