Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Thu, 30 Aug 2007, Jerry Feldman wrote: > On Thu, 30 Aug 2007 14:33:09 -0400 (EDT) > Scott Ehrlich <scott-DPNOqEs/LNQ at public.gmane.org> wrote: > >> I normally try not to ask questions until I have done as much research as >> possible, and again, this is the case... >> >> Just after I thought I had my RH5 samba/nis server working fine, I come >> across the inability to update nis passwords. >> >>> From the server as root: >> >> passwd guest1 >> Changing password for user guest1. >> New UNIX password: >> Retype new UNIX password: >> NIS password could not be changed. >> passwd: all authentication tokens updated successfully >> >> >> For the heck of it: >> >> yppasswd guest1 >> Changing NIS acount information for guest1 on server. >> Please enter root password: >> Changing NIS password for guest1 on server. >> Please enter new password: >> Please retype new password: >> Error while changing the NIS password. >> The NIS password has not been changed on the server. >> >> The server was rebooted, but that didn't help. >> >> What am I missing? > > cd /var/yp > make > I've tried this several times. > This will take care of it, but there is an easier way, use the > yppasswd(1) rather than passwd(1). I've tried both. I've now discovered that ypcat passwd on the server returns new test accounts, but a client machine that is able to log into an existing yp account, does not reflect the new accounts... Would using pdbedit this morning for samba security lockdowns have any impact? > > > > -- > Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> > Boston Linux and Unix user group > http://www.blu.org PGP key id:C5061EA9 > PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |