Hello. Anyone else experiencing Problems with this update ? We do have W2k AD. And Samba Member-Server. This is done via Winbind without using Kerberos. After installing the Update to our AD-Servers. It seems that winbind lost its connectivity. wbinfo -t worked. wbinfo -u showed errors. After removing the update from all our servers, winbind works again. Should I move our configuration to kerberos ? Thanks. Oktay Akbal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oktay Akbal wrote:> Hello. > > Anyone else experiencing Problems with this update ? > > We do have W2k AD. And Samba Member-Server. This is done > via Winbind without using Kerberos. > > After installing the Update to our AD-Servers. It seems > that winbind lost > its connectivity. > wbinfo -t worked. > wbinfo -u showed errors. > > After removing the update from all our servers, winbind > works again. Should I move our configuration to kerberos ?Can you send me a download link to the update rollup? I've a hunch this might be introducing similar behavior that we saw with Windows 2003 sp1. cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCyXH1IR7qMdg1EfYRAnvmAJ95R2HQkyEBlatBrwGEFTs0uAtkiwCgnLjr 41eHQ5of5VbdBxT5by6IW4M=Stxs -----END PGP SIGNATURE-----
The Information is at: http://support.microsoft.com/?scid=kb%3Ben-us%3B891861 The Download: http://www.microsoft.com/downloads/details.aspx?amp;amp;displaylang=en&familyid=c0a2ca36-1179-431c-80e6-60a494d3823d&displaylang=en or via windowsupdate. Thanks. Oktay
On Fri, 01 Jul 2005 09:07:00 +0200, Oktay Akbal wrote:> Hello. > > Anyone else experiencing Problems with this update ? > > We do have W2k AD. And Samba Member-Server. This is done via Winbind > without using Kerberos. > > After installing the Update to our AD-Servers. It seems that winbind lost > its connectivity. > wbinfo -t worked. > wbinfo -u showed errors. > > After removing the update from all our servers, winbind works again. > > Should I move our configuration to kerberos ? > Thanks. > > Oktay AkbalSeveral of our W2K workstations here would not boot up after this rollup. It turned out there was a conflict with our antivirus software. Uninstalling or disabling the antivirus made things work again. I think they rolled out an fix patch a couple days ago. Not sure if that's any help :/ -- http://www.0x09.com
On 7/1/05, Oktay Akbal <oktay.akbal@s-tec.de> wrote:> Hello. > > Anyone else experiencing Problems with this update ? > > We do have W2k AD. And Samba Member-Server. This is done via Winbind > without using Kerberos. > > After installing the Update to our AD-Servers. It seems that winbind lost > its connectivity. > wbinfo -t worked. > wbinfo -u showed errors.I can confirm this - it does however seam somewhat samba related because winbind does not work with samba 3.0.8 but it does work in 3.14a - note that it first works in 3.14a after adding the following to /etc/nsswitch.conf passwd: files winbind group: files winbind hosts: files winbind dns Regards. Lars Roland
I forgot to mention. Our Version is 3.0.14a and worked before the Rollup. Oktay On Thu, 14 Jul 2005, Lars Roland wrote:> On 7/1/05, Oktay Akbal <oktay.akbal@s-tec.de> wrote: > > Hello. > > > > Anyone else experiencing Problems with this update ? > > > > We do have W2k AD. And Samba Member-Server. This is done via Winbind > > without using Kerberos. > > > > After installing the Update to our AD-Servers. It seems that winbind lost > > its connectivity. > > wbinfo -t worked. > > wbinfo -u showed errors. > > I can confirm this - it does however seam somewhat samba related > because winbind does not work with samba 3.0.8 but it does work in > 3.14a - note that it first works in 3.14a after adding the following > to /etc/nsswitch.conf > > passwd: files winbind > group: files winbind > hosts: files winbind dns > > > Regards. > > Lars Roland > >
On 7/15/05, Oktay Akbal <oktay.akbal@s-tec.de> wrote:> > I forgot to mention. Our Version is 3.0.14a and worked before the Rollup. > > Oktay >have you updated /etc/nsswitch.conf -- Lars Roland
Our nsswitch is correct and btw. it does not have anything todo with the wbinfo -u command that is not working. Oktay Am Fr 15.07.2005 09:34 schrieb Lars Roland <lroland@gmail.com>:> On 7/15/05, Oktay Akbal <oktay.akbal@s-tec.de> wrote: > > > > I forgot to mention. Our Version is 3.0.14a and worked before the > > Rollup. > > > > Oktay > > > > have you updated /etc/nsswitch.conf > > > -- > Lars Roland >
On 7/15/05, Oktay Akbal <Oktay.Akbal@s-tec.de> wrote:> Our nsswitch is correct and btw. it does not have anything todo with > the wbinfo -u command that is not working. > > OktayWell it did in my case, but that may be other stuff - anyhow "wbinfo -u" works with this smb.conf on samba 3.14a in a AD controlled by a win2k with the rollup applied: ------------------------ [global] security = ads password server = win2000 encrypt passwords = yes workgroup = testdomain realm = TESTDOMAIN.LOCAL netbios name = testserver idmap uid = 10000-20000 idmap gid = 10000-20000 winbind enum users = yes winbind enum groups = yes winbind use default domain = Yes ------------------------ Samba is build with: ------------------------ ./configure \ --prefix=/usr \ --localstatedir=/var \ --with-configdir=/etc/samba \ --with-privatedir=/etc/samba \ --with-fhs \ --with-quotas \ --with-msdfs \ --with-smbmount \ --with-automount \ --with-ads \ --with-syslog \ --with-utmp \ --with-sambabook=/usr/share/swat/using_samba \ --with-swatdir=/usr/share/swat \ --with-libsmbclient \ --with-winbind \ --with-winbind-auth-challenge \ --with-manpages-langs=en \ --with-idmap \ --with-acl-support \ --with-ldap \ ------------------------ Regards. Lars Roland
There may the the point, that you are using Kerberos. We do not. We migrated a 2.2.x-Samba to 3.0 that was running without before. Oktay On Fri, 15 Jul 2005, Lars Roland wrote:> On 7/15/05, Oktay Akbal <Oktay.Akbal@s-tec.de> wrote: > > Our nsswitch is correct and btw. it does not have anything todo with > > the wbinfo -u command that is not working. > > > > Oktay > > Well it did in my case, but that may be other stuff - anyhow "wbinfo > -u" works with this smb.conf on samba 3.14a in a AD controlled by a > win2k with the rollup applied: > > ------------------------ > [global] > security = ads > password server = win2000 > encrypt passwords = yes > workgroup = testdomain > realm = TESTDOMAIN.LOCAL > netbios name = testserver > idmap uid = 10000-20000 > idmap gid = 10000-20000 > winbind enum users = yes > winbind enum groups = yes > winbind use default domain = Yes > ------------------------ > > Samba is build with: > > ------------------------ > ./configure \ > --prefix=/usr \ > --localstatedir=/var \ > --with-configdir=/etc/samba \ > --with-privatedir=/etc/samba \ > --with-fhs \ > --with-quotas \ > --with-msdfs \ > --with-smbmount \ > --with-automount \ > --with-ads \ > --with-syslog \ > --with-utmp \ > --with-sambabook=/usr/share/swat/using_samba \ > --with-swatdir=/usr/share/swat \ > --with-libsmbclient \ > --with-winbind \ > --with-winbind-auth-challenge \ > --with-manpages-langs=en \ > --with-idmap \ > --with-acl-support \ > --with-ldap \ > ------------------------ > > > Regards. > > Lars Roland > >
On 7/15/05, Oktay Akbal <oktay.akbal@s-tec.de> wrote:> There may the the point, that you are using Kerberos. > We do not. We migrated a 2.2.x-Samba to 3.0 that was running without > before. > > Oktay >Yes it does indeed seam like they have updated RPC extensively, if I try to connect to the PDC emulator in my Windows 2000 domain then "wbinfo -u" does not work even with 3.14a - if I use kerberos then it is all fine with 3.14a when the rollup is applied, but not with 3.08. So it looks like there is a real conflict here at least when you are using samba to connect to the PDC emulator (the same thing seams to be the case with Windows 2003 with all the latest hotfixes but I am still investigating that). -- Lars Roland