Because I just want sync from AD to 389ds.
Thanks in advance!
Sincerely,
--
DaV
On Fri, Aug 23, 2019, at 08:18, DaV wrote:
> Hi William,
> Thanks for your reply.
>
> Sorry for incorrect message yesterday.
> My windows sync agreement exactly is:
>
> agreement1:
> >
This is t the first time I submit a bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744879
Sincerely,
--
DaV
On Fri, Aug 23, 2019, at 13:09, DaV wrote:
> William,
> YES. The most simple way is adding cname ds.example.com to
> tc-389ds-1.example.com on DNS Server.
>
> Sincer
William,
YES. The most simple way is adding cname ds.example.com to
tc-389ds-1.example.com on DNS Server.
Sincerely,
--
DaV
On Fri, Aug 23, 2019, at 13:05, William Brown wrote:
> Great, the issue is certainly in SSSD truncating the ldap URI then. I'd
> report the issue on the Red H
cols: files
rpc:files
services: files sss
netgroup: files sss
publickey: nisplus
automount: files sss
aliases:files nisplus
Sincerely,
--
DaV
On Fri, Aug 23, 2019, at 13:01, William Brown wrote:
> Indeed - for one last detail can you please show me your /etc/nsswitch.conf?
&
You can see the prefix 389 is gone. When I want to go to /home/ithelpdesk,
client log shows
Unable to bind to the LDAP server, error can't contact LDAP server.
Because the client try to connect to ds.example.com, not 389ds.example.com
Sincerely,
--
DaV
On Fri, Aug 23, 2019, at 10:08,
