:)
Hola amigos aqui molestandoles de nuevo..

Estoy intentando unificar servicios con LDAP en red hat server 4

ESta corriendo muy bien mi servido OpenLdap autentificando correo e internet..pero ahora me toca con jabberd2 (chat).. Siguiendo manuales y guis logre configurar sin que me de error al iniciar...pero cuando alguien quiere entrar a utilizar jabberd con un cliente jabberd no puede comunicarse con el servidor LDAP...

Eesto es un extracto de log..

Sep 25 19:17:03 dominio jabberd/router[2924]: process id is 2924, written to /var/run/jabberd/router.pid
Sep 25 19:17:03 dominio jabberd/router[2924]: loaded user table (1 users)
Sep 25 19:17:03 dominio jabberd/router[2924]: [0.0.0.0, port=5347] listening for incoming connections
Sep 25 19:17:03 dominio jabberd/resolver[2925]: starting up
Sep 25 19:17:03 dominio jabberd/resolver[2925]: process id is 2925, written to /var/run/jabberd/resolver.pid
Sep 25 19:17:03 dominio jabberd/resolver[2925]: attempting connection to router at 127.0.0.1, port=5347
Sep 25 19:17:03 dominio jabberd/router[2924]: [127.0.0.1, port=32888] connect
Sep 25 19:17:03 dominio jabberd/router[2924]: [127.0.0.1, port=32888] authenticated as jabberd
Sep 25 19:17:03 dominio jabberd/resolver[2925]: connection to router established
Sep 25 19:17:03 dominio jabberd/router[2924]: [resolver] online (bound to 127.0.0.1, port 32888)
Sep 25 19:17:03 dominio jabberd/resolver[2925]: ready to resolve
Sep 25 19:17:04 dominio jabberd/sm[2926]: starting up
Sep 25 19:17:04 dominio jabberd/sm[2926]: id: mail.ruat.net
Sep 25 19:17:04 dominio jabberd/sm[2926]: process id is 2926, written to /var/run/jabberd/sm.pid
Sep 25 19:17:04 dominio jabberd/sm[2926]: initialised storage driver 'mysql'
Sep 25 19:17:04 dominio jabberd/sm[2926]: version: jabberd sm 2.0s10
Sep 25 19:17:04 dominio jabberd/c2s[2927]: starting up
Sep 25 19:17:04 dominio jabberd/c2s[2927]: process id is 2927, written to /var/run/jabberd/c2s.pid
Sep 25 19:17:04 dominio jabberd/c2s[2927]: ldap: configured 1 realms
Sep 25 19:17:04 dominio jabberd/c2s[2927]: initialised auth module 'ldap'
Sep 25 19:17:04 dominio jabberd/c2s[2927]: [mail.ruat.net] configured; realm=(null)
Sep 25 19:17:04 dominio jabberd/c2s[2927]: attempting connection to router at 127.0.0.1, port=5347
Sep 25 19:17:04 dominio jabberd/router[2924]: [127.0.0.1, port=32889] connect
Sep 25 19:17:04 dominio jabberd/sm[2926]: attempting connection to router at 127.0.0.1, port=5347
Sep 25 19:17:04 dominio jabberd/router[2924]: [127.0.0.1, port=32890] connect
Sep 25 19:17:04 dominio jabberd/router[2924]: [127.0.0.1, port=32890] authenticated as jabberd
Sep 25 19:17:04 dominio jabberd/sm[2926]: connection to router established
Sep 25 19:17:04 dominio jabberd/router[2924]: [mail.ruat.net] online (bound to 127.0.0.1, port 32890)
Sep 25 19:17:04 dominio jabberd/sm[2926]: ready for sessions
Sep 25 19:17:04 dominio jabberd/s2s[2929]: starting up (interval=0, queue=0, keepalive=0, idle=86400)
Sep 25 19:17:04 dominio jabberd/s2s[2929]: process id is 2929, written to /var/run/jabberd/s2s.pid
Sep 25 19:17:04 dominio jabberd/s2s[2929]: attempting connection to router at 127.0.0.1, port=5347
Sep 25 19:17:04 dominio jabberd/router[2924]: [127.0.0.1, port=32891] connect
Sep 25 19:17:04 dominio jabberd/router[2924]: [127.0.0.1, port=32891] authenticated as jabberd
Sep 25 19:17:04 dominio jabberd/s2s[2929]: connection to router established
Sep 25 19:17:04 dominio jabberd/router[2924]: [s2s] set as default route
Sep 25 19:17:04 dominio jabberd/router[2924]: [s2s] online (bound to 127.0.0.1, port 32891)
Sep 25 19:17:04 dominio jabberd/router[2924]: [127.0.0.1, port=32889] authenticated as jabberd
Sep 25 19:17:04 dominio jabberd/c2s[2927]: connection to router established
Sep 25 19:17:04 dominio jabberd/router[2924]: [c2s] online (bound to 127.0.0.1, port 32889)
Sep 25 19:17:04 dominio jabberd/s2s[2929]: [0.0.0.0, port=5269] listening for connections
Sep 25 19:17:04 dominio jabberd/s2s[2929]: ready for connections
Sep 25 19:17:04 dominio jabberd/c2s[2927]: [0.0.0.0, port=5222] listening for connections
Sep 25 19:17:04 dominio jabberd/c2s[2927]: ready for connections
Sep 25 19:17:27 dominio jabberd/c2s[2927]: [6] [172.21.45.41, port=1336] connect
Sep 25 19:17:27 dominio jabberd/c2s[2927]: [6] [172.21.45.41, port=1336] disconnect
Sep 25 19:17:38 dominio jabberd/c2s[2927]: [6] [172.21.45.41, port=1337] connect
Sep 25 19:17:38 dominio jabberd/c2s[2927]: ldap: bind failed: Can't contact LDAP server
Sep 25 19:17:38 dominio jabberd/c2s[2927]: ldap: bind failed: Can't contact LDAP server
Sep 25 19:17:38 dominio jabberd/c2s[2927]: [6] [172.21.45.41, port=1337] disconnect

Como ven sube el servicio pero cuendo alguien deseautlizar el servio no se conecta...
Presento la configuracion cd c2s.xml..

ldap.ruat.net
389

-->

instead of this. -->

-->

cn=manager,dc=abc,dc=net
secret

uid

section above,
by using the realm attribute. -->

dc=abc,dc=net

y la configuracion del slapd es:

#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema

include /etc/openldap/schema/misc.schema
#include /etc/openldap/schema/sendmail.schema

# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2

# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org

pidfile /var/run/slapd.pid
argsfile /var/run/slapd.args

# Load dynamic backend modules:
# modulepath /usr/sbin/openldap
# moduleload back_bdb.la
# moduleload back_ldap.la
# moduleload back_ldbm.la
# moduleload back_passwd.la
# moduleload back_shell.la

# The next three lines allow use of TLS for encrypting connections using a
# dummy test certificate which you can generate by changing to
# /usr/share/ssl/certs, running "make slapd.pem", and fixing permissions on
# slapd.pem so that the ldap user or group can read it. Your client software
# may balk at self-signed certificates, however.
# TLSCACertificateFile /usr/share/ssl/certs/ca-bundle.crt
# TLSCertificateFile /usr/share/ssl/certs/slapd.pem
# TLSCertificateKeyFile /usr/share/ssl/certs/slapd.pem

# Sample security restrictions
# Require integrity protection (prevent hijacking)
# Require 112-bit (3DES or better) encryption for updates
# Require 63-bit encryption for simple bind
# security ssf=1 update_ssf=112 simple_bind=64

# Sample access control policy:
# Root DSE: allow anyone to read it
# Subschema (sub)entry DSE: allow anyone to read it
# Other DSEs:
# Allow self write access
# Allow authenticated users read access
# Allow anonymous users to authenticate
# Directives needed to implement policy:
access to dn.base="" by * read
access to dn.base="cn=Subschema" by * read
access to *
by self write
by users read
by anonymous auth

#
# if no access controls are present, the default policy
# allows anyone and everyone to read anything but restricts
# updates to rootdn. (e.g., "access to * by * read")
#
# rootdn can always read and write EVERYTHING!

#######################################################################
# ldbm and/or bdb database definitions
#######################################################################

database bdb
suffix "dc=abc,dc=net"
rootdn "cn=manager,dc=abc,dc=net"
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
#rootpw secret
# rootpw {crypt}ijFYNcSNctBYg
rootpw {MD5}Xr4ilOzQ4PCOq3aQ0qbuaQ==

# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /var/lib/ldap

#-----
#access to attr=userPassword
# by dn="cn=manager,dc=abc,dc=net" write
# by self write
# by * auth
#access to attr=mail
# by dn="cn=manager,dc=abc,dc=net" write
# by self write
# by * read
#access to DN=".*,ou=People,dc=abc,dc=net"
# by DN="cn=manager,dc=abc,dc=net" write
# by * read
access to *
by dn="cn=manager,dc=abc,dc=net" write
by * read
#-----

# Indices to maintain for this database
index objectClass eq,pres
index ou,cn,mail,surname,givenname eq,pres,sub
index uidNumber,gidNumber,loginShell eq,pres
index uid,memberUid eq,pres,sub
index nisMapName,nisMapEntry eq,pres,sub

# Replicas of this database
#replogfile /var/lib/ldap/openldap-master-replog
#replica host=ldap-1.example.com:389 starttls=critical
# bindmethod=sasl saslmech=GSSAPI
# authcId=host/ldap-master.example.com@EXAMPLE.COM

Favor les pido ayuda...estoy seguro a alguien ya le paso y lo pudieron solucionar...no se si es la configuracion del ajbberd del openlapd o algo que no estoyb considerando...

Les agradezco de antemano su ayudda...

diego