I'm a little confused here; what is the purpose of the passsync service
(I've successfully created a replication agreement over ssl via fds and
ad). Thanks again.
Aaron
-----Original Message-----
From: fedora-directory-users-bounces(a)redhat.com
[mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Nathan
Kinder
Sent: Tuesday, October 31, 2006 11:57 AM
To: General discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] Trouble getting windows to talk to
fds
Bliss, Aaron wrote:
I must apologize for all of the questions, however this (getting
windows
to talk to fds) is very new to me; I believe that I have the ssl
piece
as far as the service is concerned configured properly; passync
service
is installed to the ad box, however after rebooting I checked the
logfile and noticed some errors;
failed to load entries from file,
ldap bind error,
no such object
Can not connect to ldap server in syncpasswords
It sounds like I have not configured the service properly to bind to
the
fds database; on the fds side of the house, I've configured an
account
called dn=psync,cn=config in the config ou (simular to setting up an
account used for setting up a supplier/consumer setup, such that the
account itself will not be replicated); I then installed the passsync
service on the ad box usning the following values:
Host name: hostname of fds suppler server
Port: 636
Username: uid=psync,cn=config
Password: same as user setup in database on fds box
Cert token: password to local passync database
Search base: dc=mydomain,dc=org
Couple of questions; does it appear that I've set things up properly
on
both the fds side of the house and the ad side of the house? What
is
the best way to further troubleshoot this? Thanks again.
The best thing to do when setting up Windows Sync is to go one step at a
time. First get your user & group sync working. It will work just fine
without setting up the PassSync service. Do you have this part working
already?
If PassSync is having trouble binding to FDS, you should start
troubleshooting by looking at the FDS access logs when PassSync attempts
to connect. It sounds like the bind DN may be incorrect.
-NGK
Aaron
Confidentiality Notice:
The information contained in this electronic message is intended for the exclusive use of
the individual or entity named above and may contain privileged or confidential
information. If the reader of this message is not the intended recipient or the employee
or agent responsible to deliver it to the intended recipient, you are hereby notified that
dissemination, distribution or copying of this information is prohibited. If you have
received this communication in error, please notify the sender immediately by telephone
and destroy the copies you received.