<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im"><br>
    <br>
    <blockquote type="cite">
      <div dir="ltr">has anyone worked it out. Secondly cifs-utils has
        dependency on samba3 packages and ipa-ad-trust needs samba4 but
        samba3 and samba4 don't like each other , so this is the story
        of my experience with ipa. Any suggestions ?<br>
      </div>
    </blockquote>
    <br></div>
    Why do you need cifs-utils on the same server?<br>
    cifs-utils to make a system a client to MSFT file server, AFAIU you
    cant make IPA server to be a cifs client.<br>
    <br></div></blockquote><div><br></div><div><a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/trust-diff-dns-domains.html">https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/trust-diff-dns-domains.html</a></div>
<div><br></div><div>Step 3 mentions that cifs-utils is required, but:</div><div><br></div><div><div>yum install cifs-utils</div><div>Loaded plugins: product-id, security, subscription-manager</div><div>This system is receiving updates from Red Hat Subscription Management.</div>
<div>rhel-6-server-cf-tools-1-rpms                                 | 2.8 kB     00:00     </div><div>rhel-6-server-rhev-agent-rpms                                 | 3.1 kB     00:00     </div><div>rhel-6-server-rpms                                            | 3.7 kB     00:00     </div>
<div>Setting up Install Process</div><div>Resolving Dependencies</div><div>--> Running transaction check</div><div>---> Package cifs-utils.x86_64 0:4.8.1-19.el6 will be installed</div><div>--> Processing Dependency: libwbclient.so.0()(64bit) for package: cifs-utils-4.8.1-19.el6.x86_64</div>
<div>--> Running transaction check</div><div>---> Package samba-winbind-clients.x86_64 0:3.6.9-167.el6_5 will be installed</div><div>--> Processing Dependency: samba-winbind = 3.6.9-167.el6_5 for package: samba-winbind-clients-3.6.9-167.el6_5.x86_64</div>
<div>--> Running transaction check</div><div>---> Package samba-winbind.x86_64 0:3.6.9-167.el6_5 will be installed</div><div>--> Processing Dependency: samba-common = 3.6.9-167.el6_5 for package: samba-winbind-3.6.9-167.el6_5.x86_64</div>
<div>--> Running transaction check</div><div>---> Package samba-common.x86_64 0:3.6.9-167.el6_5 will be installed</div><div>--> Processing Conflict: samba4-common-4.0.0-60.el6_5.rc4.x86_64 conflicts samba-common < 3.9.9</div>
<div>--> Processing Conflict: samba4-winbind-4.0.0-60.el6_5.rc4.x86_64 conflicts samba-winbind < 3.9.9</div><div>--> Processing Conflict: samba4-winbind-clients-4.0.0-60.el6_5.rc4.x86_64 conflicts samba-winbind-clients < 3.9.9</div>
<div>--> Finished Dependency Resolution</div><div>Error: samba4-common conflicts with samba-common-3.6.9-167.el6_5.x86_64</div><div>Error: samba4-winbind-clients conflicts with samba-winbind-clients-3.6.9-167.el6_5.x86_64</div>
<div>Error: samba4-winbind conflicts with samba-winbind-3.6.9-167.el6_5.x86_64</div><div> You could try using --skip-broken to work around the problem</div><div> You could try running: rpm -Va --nofiles --nodigest</div></div>
<div><br></div><div><br></div><div>Is this no longer a requirement? Can this documentation be updated?</div><div><br></div><div>Steve</div><div> </div></div><br></div></div>