<div dir="ltr"><font face="courier new, monospace">Initially after configuring the setup I rebooted once and I was thinking</font><div><span style="font-family:'courier new',monospace">that it worked before the reboot but </span><span style="font-family:'courier new',monospace">unfortunately it didn't work the first time itself.</span><div>
<div><br></div><div><font face="courier new, monospace">Still failing after running the commands.</font></div><div><font face="courier new, monospace"><br></font></div><div><div><font face="courier new, monospace">[root@ipaserver ~]# net conf setparm global "client min protocol" smb2_02</font></div>
<div><font face="courier new, monospace">[root@ipaserver ~]# net conf setparm global "client max protocol" smb2_02</font></div><div><font face="courier new, monospace">[root@ipaserver ~]# service winbind restart</font></div>
<div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">Shutting down Winbind services: [ OK ]</font></div><div><font face="courier new, monospace">Starting Winbind services: [ OK ]</font></div>
<div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">[root@ipaserver ~]# wbinfo -n 'ADDOMAIN\Domain Admins'</font></div><div><font face="courier new, monospace">failed to call wbcLookupName: WBC_ERR_DOMAIN_NOT_FOUND</font></div>
<div><font face="courier new, monospace">Could not lookup name ADDOMAIN\Domain Admins</font></div><div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">[root@ipaserver ~]# wbinfo -u</font></div>
<div><font face="courier new, monospace">[root@ipaserver ~]# </font></div></div><div><font face="courier new, monospace"><br></font></div><div class="gmail_extra"><font face="courier new, monospace">The issue is reproducible every time if anyone follows the steps as I have done.</font></div>
<div class="gmail_extra"><font face="courier new, monospace"><br><br></font><div class="gmail_quote"><font face="courier new, monospace">On Mon, May 19, 2014 at 4:45 PM, Sumit Bose <span dir="ltr"><<a href="mailto:sbose@redhat.com" target="_blank">sbose@redhat.com</a>></span> wrote:<br>
</font><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><font face="courier new, monospace">On Mon, May 19, 2014 at 04:29:24PM +0530, Supratik Goswami wrote:<br>
> Hi<br>
><br>
> Let me start from the beginning once again. Let me explain you what steps I<br>
> followed during the setup.<br>
><br>
> I am setting up the environment in Amazon AWS, both Windows AD server and<br>
> Linux IPA configured in EC2.<br>
> For configuring Windows 2008 I selected<br>
> Windows_Server-2008-R2_SP1-English-64Bit-Base-2014.04.09 (ami-df8e93b6)<br>
> and for configuring IPA server I selected CentOS 6.5 (x86_64) - Release<br>
> Media (ami-8997afe0).<br>
><br>
> I followed the steps from<br>
> <a href="http://www.freeipa.org/page/Howto/IPAv3_AD_trust_setup" target="_blank">http://www.freeipa.org/page/Howto/IPAv3_AD_trust_setup</a> and also kept the<br>
> domain names<br>
> similar as in the example.<br>
><br>
> IPA server hostname: ipaserver<br>
> IPA domain: <a href="http://ipadomain.example.com" target="_blank">ipadomain.example.com</a><br>
> IPA NetBIOS: IPADOMAIN<br>
><br>
> AD DC hostname: adserver<br>
> AD domain: <a href="http://addomain.example.com" target="_blank">addomain.example.com</a><br>
> AD NetBIOS: ADDOMAIN<br>
><br>
><br>
> 1. Updated the system and install the packages.<br>
><br>
> # yum update -y<br>
> # yum install -y "*ipa-server" "*ipa-server-trust-ad"<br>
> samba4-winbind-clients samba4-winbind samba4-client bind bind-dyndb-ldap<br>
><br>
> List of important packages installed during the update are as follows.<br>
><br>
> bind x86_64 32:9.8.2-0.23.rc1.el6_5.1<br>
> bind-dyndb-ldap x86_64 2.3-5.el6<br>
><br>
> ipa-server x86_64 3.0.0-37.el6<br>
> ipa-server-trust-ad x86_64 3.0.0-37.el6<br>
> ipa-admintools x86_64 3.0.0-37.el6<br>
> ipa-client x86_64 3.0.0-37.el6<br>
> ipa-pki-ca-theme noarch 9.0.3-7.el6<br>
> ipa-pki-common-theme noarch 9.0.3-7.el6<br>
> ipa-python x86_64 3.0.0-37.el6<br>
> ipa-server-selinux x86_64 3.0.0-37.el6<br>
><br>
> samba4-client x86_64 4.0.0-61.el6_5.rc4<br>
> samba4-winbind x86_64 4.0.0-61.el6_5.rc4<br>
> samba4-winbind-clients x86_64 4.0.0-61.el6_5.rc4<br>
> samba4 x86_64 4.0.0-61.el6_5.rc4<br>
> samba4-common x86_64 4.0.0-61.el6_5.rc4<br>
> samba4-libs x86_64 4.0.0-61.el6_5.rc4<br>
> samba4-python x86_64 4.0.0-61.el6_5.rc4<br>
<br>
</font></div></div><font face="courier new, monospace">ah, sorry, I this might be a known issue, but I got on a wrong track<br>
because I thought it was working initially and only failed after reboot.<br>
<br>
Please try to set "client min protocol" and "client max protocol" in the<br>
samba configuration:<br>
<br>
net conf setparm global "client min protocol" smb2_02<br>
net conf setparm global "client max protocol" smb2_02<br>
<br>
restart winbind and try again.<br>
<br>
HTH<br>
<br>
bye,<br>
Sumit<br>
</font><div class="HOEnZb"><div class="h5"><font face="courier new, monospace"><br>
><br>
> 389-ds-base x86_64 1.2.11.15-32.el6_5<br>
> 389-ds-base-libs x86_64 1.2.11.15-32.el6_5<br>
><br>
> certmonger x86_64 0.61-3.el6<br>
><br>
> krb5-server x86_64 1.10.3-15.el6_5.1<br>
> krb5-workstation x86_64 1.10.3-15.el6_5.1<br>
><br>
> sssd x86_64 1.9.2-129.el6_5.4<br>
> sssd-client x86_64 1.9.2-129.el6_5.4<br>
><br>
><br>
><br>
</font></div></div></blockquote></div><font face="courier new, monospace"><br><br clear="all"></font><div><font face="courier new, monospace"><br></font></div><font face="courier new, monospace">-- <br>Warm Regards<br><br>
Supratik
</font></div></div></div></div>