Hello! I was wondering if anyone out there has been able to get the command: NET PASSWORD \\sambaserver to work from within Windows95 talking to a Samba server? We're running Samba 1.9.17p2 and Linux (RedHat 4.1 2.0.27 kernel). The Samba server is handling domain logons and roaming user profiles. We need a nice easy way for idiot users to change their passwords when needed ... we're trying to avoid having them login to the Linux server if at all possible.>From reading the docs for Samba, it states that this "may or may not work,depending on your installation". We have compiled in the option to allow this, but never seem to be able to get the silly thing to work, always returning a network error. Otherwise, all else is fine and dandy. As a side note, just a few days ago I got a call from our users that no-one was able to log in to their workstations, that their login was not validated. Rebooting the samba server fixed the problem, but I am unaware as to what exactly happened. It sounds similar to what others have experienced with "hung" logins from Win95. Thanks for the great support (and info) this group has. Always makes for interesting reading between code compiles... --Mike Huttinger ______________________________________________________ Michael Huttinger huttinger@ipact.com Engineer Phone:(219) 464-7212 IPACT, Inc. FAX: (219) 462-5387 260 S. Campbell Valparaiso, IN 46383
On Fri, 10 Oct 1997 02:48:16 +1000, you wrote:> >Hello! > >I was wondering if anyone out there has been able to get the command: > > NET PASSWORD \\sambaserver > >to work from within Windows95 talking to a Samba server? > >We're running Samba 1.9.17p2 and Linux (RedHat 4.1 2.0.27 kernel). The >Samba server is handling domain logons and roaming user profiles. We need >a nice easy way for idiot users to change their passwords when needed ... >we're trying to avoid having them login to the Linux server if at all >possible. > >>From reading the docs for Samba, it states that this "may or may not work, >depending on your installation". We have compiled in the option to allow >this, but never seem to be able to get the silly thing to work, always >returning a network error. Otherwise, all else is fine and dandy. >Doesn't sound like you have actually done any playing around with the smb.conf file, you might want to start by looking at the following 2 sections in man smb.conf, iirc the: passwd chat passwd program
On Thursday, October 09, 1997 4:31 PM, Simon Hyde [SMTP:shyde@poboxes.com] wrote:> On Fri, 10 Oct 1997 02:48:16 +1000, you wrote: > >I was wondering if anyone out there has been able to get the command: > > > > NET PASSWORD \\sambaserver > > > >to work from within Windows95 talking to a Samba server? > > >From reading the docs for Samba, it states that this "may or may notwork,> >depending on your installation". We have compiled in the option toallow> >this, but never seem to be able to get the silly thing to work, always > >returning a network error. Otherwise, all else is fine and dandy. > > > Doesn't sound like you have actually done any playing around with the > smb.conf file, you might want to start by looking at the following 2 > sections in man smb.conf, iirc the: > passwd chat > passwd programBeen there, done that about a zillion times, and I never seemed to get the right settings. For program, we're using the standard Linux passwd, and for chat (hmm, trying to remember as I don't have the box here to look at) something _similiar_ to the default, but not exactly. I tried to match it up to what the passwd program does for any normal user, but no matter what happens the command always fails. Perhaps I'll bump up the debug output and see if anything significant is in the log files. What I'd like to know is if anyone has gotten this to run on a Linux machine (RedHat 4.1, kernel 2.0.27, and Samba 1.9.17p2) If so, what configuration did you use? Is using passwd the problem? Thanks for any help you may have... --Mike Huttinger ______________________________________________________ Michael Huttinger huttinger@ipact.com Engineer Phone:(219) 464-7212 IPACT, Inc. FAX: (219) 462-5387 260 S. Campbell Valparaiso, IN 46383
> > On Fri, 10 Oct 1997 02:48:16 +1000, you wrote: > > >I was wondering if anyone out there has been able to get the command: > > > > > > NET PASSWORD \\sambaserver > > > > > >to work from within Windows95 talking to a Samba server? > > > Been there, done that about a zillion times, and I never seemed to get the > right settings. For program, we're using the standard Linux passwd, and > for chat (hmm, trying to remember as I don't have the box here to look at) > something _similiar_ to the default, but not exactly. I tried to match it > up to what the passwd program does for any normal user, but no matter what > happens the command always fails. Perhaps I'll bump up the debug output > and see if anything significant is in the log files. >[Someone please correct if I am wrong...] I don't think this will work with Windows 95 clients because the password is sent across the wire in UPPER case letters. Therefore the original password will most likely never match. I am asuming that you UNIX passwords are not all UPPER case in the first place. I was interested in the original post so I played around with it on the client side and verified this ( the upper case password that is ). Of course I could be wrong if the password level parameter in smb.conf applies here as well but I don't see how it could be applied to the new password. Any ideas? j- ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 ) ________________________________________________________________________
> On Thursday, October 09, 1997 4:31 PM, Simon Hyde [SMTP:shyde@poboxes.com] > wrote: > > On Fri, 10 Oct 1997 02:48:16 +1000, you wrote: > > >I was wondering if anyone out there has been able to get the command: > > > > > > NET PASSWORD \\sambaserver > > > > > >to work from within Windows95 talking to a Samba server? > > > > >From reading the docs for Samba, it states that this "may or may not > work, > > >depending on your installation". We have compiled in the option to > allow > > >this, but never seem to be able to get the silly thing to work, always > > >returning a network error. Otherwise, all else is fine and dandy. > > > > > Doesn't sound like you have actually done any playing around with the > > smb.conf file, you might want to start by looking at the following 2 > > sections in man smb.conf, iirc the: > > passwd chat > > passwd program > > Been there, done that about a zillion times, and I never seemed to get the > right settings. For program, we're using the standard Linux passwd, and > for chat (hmm, trying to remember as I don't have the box here to look at) > something _similiar_ to the default, but not exactly. I tried to match it > up to what the passwd program does for any normal user, but no matter what > happens the command always fails. Perhaps I'll bump up the debug output > and see if anything significant is in the log files. > > What I'd like to know is if anyone has gotten this to run on a Linux > machine (RedHat 4.1, kernel 2.0.27, and Samba 1.9.17p2) If so, what > configuration did you use? Is using passwd the problem? > > Thanks for any help you may have... > > --Mike HuttingerI was experimenting with remote password changes from DOS MS Client (the same "net password" command) and after several hacks to samba code I finally got it to work (if I remember - some setuid/seteuid kludge was needed. System is RedHat 4.2 based with nearly complete authorization utilities replace). Unfortunately although Samba is compiled with DES and DOS client is using crypted passwords during login, the password change process is insecure - clear text passwords (both old and new) are sent over NetBIOS. I also made patches to std. passwd command to automatically call smbpasswd and have added new option to smbpasswd to accept new password also from stdin (and workaround that ugly ptyp/ttyp pair shuffling for getpass()). Unfortunately this is not 'professional' so /etc/smbpasswd is not coherent over useradd/userdel and I have now no time to fix it. If someone wants to kick it to some distributable state, give me a mail... Looking forward for 1.9.18alpha1, Jan "Lace" Kratochvil
Michael Huttinger writes:> >On Thursday, October 09, 1997 4:31 PM, Simon Hyde [SMTP:shyde@poboxes.com] >wrote: >> On Fri, 10 Oct 1997 02:48:16 +1000, you wrote: >> >I was wondering if anyone out there has been able to get the command: >> > >> > NET PASSWORD \\sambaserver >> > >> >to work from within Windows95 talking to a Samba server? >> > [ ... snip ... ] > >Been there, done that about a zillion times, and I never seemed to get the >right settings. For program, we're using the standard Linux passwd, and >for chat (hmm, trying to remember as I don't have the box here to look at) >something _similiar_ to the default, but not exactly. I tried to match it >up to what the passwd program does for any normal user, but no matter what >happens the command always fails. Perhaps I'll bump up the debug output >and see if anything significant is in the log files. > >What I'd like to know is if anyone has gotten this to run on a Linux >machine (RedHat 4.1, kernel 2.0.27, and Samba 1.9.17p2) If so, what >configuration did you use? Is using passwd the problem? >I actually tried it on almost that exact configuration (using 2.0.30 instead) two weeks ago. I also had absolutely no luck ... I don't think it's the passwd program, though, because I tried to write a noop shell script that would log (using logger(1)) each step of the process -- I never really got anything in the logs. I didn't have time to deal with the issue, so I ended up hacking together a perl script that changes both the UNIX password and the smbpasswd file simultaneously, and have the users telnet into an account that has said shell as its login shell .. kludgy but I had to get something working immediately. Could someone who is successfully using the 'NET PASSWORD ..' support provide any insight about what might be wrong? -Joshua -------- Joshua Heling jrh@securepipe.com