Am Monday 29 March 2010 14:56:13 schrieb John H Terpstra: > Richi, > > Please file a detailed bug report on https://bugzilla.samba.org with > clear steps so that one of the developers can reproduce your problem. > > Is your installation new, or was is migrated from an earlier version of > Samba? > > - John T. > > On 03/29/2010 01:45 AM, Richard Lamboj wrote: > > Good morning John, > > > > here is the Output: > > server-b10:/# ls -al /lib*/libc-*so > > -rwxr-xr-x 1 root root 1375536 14. Jän 07:51 /lib64/libc-2.7.so > > -rwxr-xr-x 1 root root 1375536 14. Jän 07:51 /lib/libc-2.7.so > > server-b10:/# uname -a > > Linux server-b10.intern.bilcom.at 2.6.32-vs2.3.0.36.26 #1 SMP Thu Dec 10 > > 16:36:45 CET 2009 x86_64 GNU/Linux > > > > Some System informations: > > OS: Debian Lenny > > Arch: x86_64 > > Others: Linux VServer Guest > > > > Kind Regards > > > > Richi > > > > Am Sunday 28 March 2010 15:39:54 schrieb John H Terpstra: > >> Please will all who have this problem respond with the output of > >> executing the following: > >> > >> 1) smbd -V > >> 2) ls -al /lib*/libc-*so > >> 3) uname -a > >> > >> Thanks. > >> > >> - John T. > >> > >> On 03/28/2010 07:33 AM, Denis BUCHER wrote: > >>> Hello everyone, > >>> > >>> I have the exact same problem, but without any solution : > >>> > >>> Le 12.03.2010 08:03, Richard Lamboj a écrit : > >>>> Its definitly a signed 32 bit int: > >>>> net sam policy set "maximum password age" 4294967291 > >>>> Account policy "maximum password age" value was: -1 > >>>> Account policy "maximum password age" value is now: -5 > >>>> > >>>> Does not work: > >>>> net sam policy set "maximum password age" never > >>>> Account policy "maximum password age" value was: 2147483647 > >>>> Account policy "maximum password age" value is now: -1 > >>>> > >>>> Does also not work: > >>>> net sam policy set "maximum password age" 2147483647 > >>>> Account policy "maximum password age" value was: -5 > >>>> Account policy "maximum password age" value is now: 2147483647 > >>>> > >>>> So when i'am using "never" it will be set to -1, so it must be a > >>>> signed integer and this has a maximal value of 2147483647. > >>>> > >>>> Napalm and a new Job on the Beach could be the Solution... > >>>> > >>>> Am Friday 12 March 2010 02:14:10 schrieb Michael B. Trausch: > >>>>> On 03/11/2010 03:52 PM, Richard Lamboj wrote: > >>>>>> Hello, > >>>>>> > >>>>>> server-p:/# net sam policy set "maximum password age" 4294967294 > >>>>>> Account policy "maximum password age" value was: -2 > >>>>>> Account policy "maximum password age" value is now: -2 > >>>>>> > >>>>>> Is that Output Normal? > >>>>> > >>>>> Looks like there is some wrapping going on there. Try: > >>>>> > >>>>> # net sam policy set "maximum password age" 4294967291 > >>>>> > >>>>> That said, I don't know why there would be wrapping. An unsigned > >>>>> 32-bit integer's maximum value is 4294967295, so 4294967294 (the > >>>>> value that you used) should be something that would fit. I don't > >>>>> know what would cause that to happen that way. > >>> > >>> I tried all points and IT DOES NOT WORK, always the message "Your > >>> password expires today, please change your password yes/no" : > >>> > >>> -> My users are all "UX" (I also tried without X, it's even worse) > >>> -> I tried pdbedit > >>> -> I tried net sam > >>> -> removed "passdb backend = smbpasswd" from config > >>> > >>> # net sam policy set "maximum password age" 4294967295 > >>> Account policy "maximum password age" value was: 0 > >>> Account policy "maximum password age" value is now: -1 > >>> > >>> pdbedit -u mbucher -v > >>> gives either > >>> > >>>> Password last set: 0 > >>>> Password can change: 0 > >>>> Password must change: 0 > >>>> Last bad password : 0 > >>>> Bad password count : 0 > >>> > >>> either > >>> > >>>> Password last set: Thu, 25 Feb 2010 15:17:18 CET > >>>> Password can change: Thu, 25 Feb 2010 15:17:18 CET > >>>> Password must change: never > >>>> Last bad password : 0 > >>>> Bad password count : 0 > >>> > >>> Any help would be greatly appreciated we have 90 people here and I > >>> really becoming mad about this, I don't know where to search for ? > >>> > >>> Denis
Hello John, there is already a bug report at bugzilla. The bug number is 7066. But i can write again to this bug, with more informations? Scenario 1: =============== DOMAIN1 - 3.5.1 DOMAIN2 - 3.2.14 PC1 - Member of DOMAIN1 Login on DOMAIN1(Machine Domain): No Error Message Login on DOMAIN2(Trusted Domain): Your password expires today Scenario 2: =============== DOMAIN1 - 3.5.1 DOMAIN2 - 3.5.1 PC1 - Member of DOMAIN1 Login on DOMAIN1(Machine Domain): No Error Message Login on DOMAIN2(Trusted Domain): Your password expires today Scenario 3: =============== DOMAIN1 - 3.2.14 DOMAIN2 - 3.2.14 PC1 - Member of DOMAIN1 Login on DOMAIN1(Machine Domain): No Error Message Login on DOMAIN2(Trusted Domain): No Error Message I have upgraded from 3.2.14 to 3.5.1. Re-Joining the Trusted Domains doesn't help. It is just the Message and everything works. At the Moment the log level is 3 and there is nothing strange in de log files. I could take it higher after work. Kind Regards Richi -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
