Re: [Samba] Samba 3.0.1 - 3.0.2 upgrade problem
Gerald (Jerry) Carter schrieb: Is the last change time on the password set to 0 by chance? Please provide more details. This little question made my day. :-) I updated all our servers from 2.2.8a+LDAP to 3.0.2 this evening and had the problem that most users couldn't log in any more while my own account was still working. I remembered this little post from you, checked my LDAP-entries and found that the broken accounts all had 'sambaPwdLastSet' set to '0'. I changed them to a reasonable value and all worked fine. Thank you. :-) cu, Uwe -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.1 - 3.0.2 upgrade problem
Uwe Laverenz wrote: Gerald (Jerry) Carter schrieb: Is the last change time on the password set to 0 by chance? Please provide more details. This little question made my day. :-) I updated all our servers from 2.2.8a+LDAP to 3.0.2 this evening and had the problem that most users couldn't log in any more while my own account was still working. I remembered this little post from you, checked my LDAP-entries and found that the broken accounts all had 'sambaPwdLastSet' set to '0'. I changed them to a reasonable value and all worked fine. Thank you. :-) cu, Uwe We have hundreds of ldap entries, and about half of them have this set, but I swear, that even the ones that didn't couldn't get on... We can be up for another test run this weekend... -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.1 - 3.0.2 upgrade problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 amrito wrote: | Basic effect: | when attaching a network drive, the system asked for a password and | afterwards rejected the service with a message like | 'invalid user or password' Is the last change time on the password set to 0 by chance? Please provide more details. cheers, jerry - -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc If we're adding to the noise, turn off this song --Switchfoot (2003) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAKkwEIR7qMdg1EfYRAjdBAKCDBXBa0aIF839EAaTB/mAQD05eZwCcDB2e Qs4MbSKAPM7CU6WjVlFnvY8= =1U0K -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.1 - 3.0.2 upgrade problem
same thing here... amrito wrote: Michal Sladek wrote: This morning I tried to upgrade Samba from 3.0.1 to 3.0.2 final I had only few minutes to test it from Windows XP clients (we use Windows 98 and XP clients in our company) because we have hundreds of users connected and I had to go back to 3.0.1 immediately before the get angry:-) Exactly the same happend with me. After compiling 3.0.2 (which worked absolutely fine) and installing it, the telephone started to ring, and I had to revert immediately. Basic effect: when attaching a network drive, the system asked for a password and afterwards rejected the service with a message like 'invalid user or password' I haven't got time to install 3.0.2 on a spare server to check what went wrong without the threat of being thrown out of the window, but if in between someone got some hints what might have gone wrong and (even more interesting) how to fix it, I would greatly appreciate to get the info, too. Thanks Regards john -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba 3.0.1 - 3.0.2 upgrade problem
org] On Behalf Of Barry Smoke Sent: Thursday, 12 February 2004 02:47 Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Samba 3.0.1 - 3.0.2 upgrade problem same thing here... I had a similar experience, where NT4, 9X DOS clients dropped off. This was caused by a hung process or locked file in my case, where smbd failed shutdown cleanly. Rather than attempting to trace the rogue file/process, I simply restarted the machine and all came up roses. amrito wrote: Michal Sladek wrote: This morning I tried to upgrade Samba from 3.0.1 to 3.0.2 final I had only few minutes to test it from Windows XP clients (we use Windows 98 and XP clients in our company) because we have hundreds of users connected and I had to go back to 3.0.1 immediately before the get angry:-) Exactly the same happend with me. After compiling 3.0.2 (which worked absolutely fine) and installing it, the telephone started to ring, and I had to revert immediately. Basic effect: when attaching a network drive, the system asked for a password and afterwards rejected the service with a message like 'invalid user or password' I haven't got time to install 3.0.2 on a spare server to check what went wrong without the threat of being thrown out of the window, but if in between someone got some hints what might have gone wrong and (even more interesting) how to fix it, I would greatly appreciate to get the info, too. Thanks Regards john Might be better to set-up a test machine test your upgrades before rolling them out eh! Cheers, Lewis -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
