Re: samba password changes after potato upgrade
Thanks for the clarification. Doug Martin Bialasinski wrote: Doug == Doug Thistlethwaite [EMAIL PROTECTED] wrote: Doug password file (I don't even remember if it was an option at that Doug time). I think the latest version set the system up to use Doug passwords, but the file didn't have the users or passwords Doug available. And it can't. SMB uses a different algorithm than crypt which is used for /etc/shadow. So you can't just copy the crypted password into the samba password file. Ciao, Martin -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: samba password changes after potato upgrade
Doug == Doug Thistlethwaite [EMAIL PROTECTED] wrote: Doug One more thing about Samba. Does anyone know why the Doug distribution does not have all of the tools that are described Doug on the samba site. Because the package has been broken up. Doug There is a file that describes a set of steps to debug problems Doug like I am having. The third step call for the use of smbclient Doug which is not in any of the deb files as far as I can tell. Package smbclient. You could also install smaba-doc package which also has the diagnosis file you were reading. If you are looking for a package that has some specific file, look at packages.debian.org, which has a search engine. Ciao, Martin
Re: samba password changes after potato upgrade
Thanks for the information! The smbclient is in its own package. I fixed my samba installation by re-creating the password file for samba. I think that the problem was that when I first installed samba, I did not use a separate password file (I don't even remember if it was an option at that time). I think the latest version set the system up to use passwords, but the file didn't have the users or passwords available. I re-created the password file, and entered the users and passwords by hand. After this, samba works fine! Thanks to all who helped on this issue! Doug Martin Bialasinski wrote: Doug == Doug Thistlethwaite [EMAIL PROTECTED] wrote: Doug One more thing about Samba. Does anyone know why the Doug distribution does not have all of the tools that are described Doug on the samba site. Because the package has been broken up. Doug There is a file that describes a set of steps to debug problems Doug like I am having. The third step call for the use of smbclient Doug which is not in any of the deb files as far as I can tell. Package smbclient. You could also install smaba-doc package which also has the diagnosis file you were reading. If you are looking for a package that has some specific file, look at packages.debian.org, which has a search engine. Ciao, Martin -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: samba password changes after potato upgrade
Thanks for the information James, My first instalation was using plain text passwords. The latest version didn't transfer that setting from my old config. Craig, I found this out before I read your message, but you are completely correct. I recreated the users and passwords and everything worked great! Thanks again, Doug Daniels, Craig wrote: I had the same problem when I upgraded to potato with samba 2.04. There's probably a better way to do this, but I fixed it using smbpasswd with the username for each of my users and entered a default password. After that, it seems to work fine. Craig -- From: Doug Thistlethwaite Sent: Monday, July 19, 1999 2:12 AM To: Lewis, James M.; debian-user@lists.debian.org Cc: Doug Work Subject: Re: samba password changes after potato upgrade Ok, I upgraded to 2.2.10 kernel but my Samba still does not recognise my passwords from my win 95 system. My old samba configuration used plain text passwords if my memory serves me right. I think there was a problem with encription of passwords when I first installed it. If this is the case, how do I go about setting up my system to accept passwords? Any help pointing me in the correct direction would be greatly appriciated! Doug Lewis, James M. wrote: After upgrading my system to potato, my samba services no longer work. I get an error message saying that the password supplied is not valid. Everything worked fine under slink. If I remember correctly, part of the instructions on the old setup was to remove password encryption so windows 95 could connect (Its been so long, I'm not sure exactly what I did to set it up). The latest version of samba has encryption enabled for windows 95/98. Where should I look to modify my configuration files? Are there any docs on conversion issues from the version that was stable with slink? If all you did was upgrade samba, then the problem might be with the kernel version. I had a similar problem with 2.0.36 kernel. I upgraded to 2.2.10 and things worked right. The problem was that samba could not become the connected user. Thanks, Doug -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null jim -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: samba password changes after potato upgrade
Doug == Doug Thistlethwaite [EMAIL PROTECTED] wrote: Doug password file (I don't even remember if it was an option at that Doug time). I think the latest version set the system up to use Doug passwords, but the file didn't have the users or passwords Doug available. And it can't. SMB uses a different algorithm than crypt which is used for /etc/shadow. So you can't just copy the crypted password into the samba password file. Ciao, Martin
RE: samba password changes after potato upgrade
Ok, I upgraded to 2.2.10 kernel but my Samba still does not recognise my passwords from my win 95 system. My old samba configuration used plain text passwords if my memory serves me right. I think there was a problem with encription of passwords when I first installed it. If this is the case, how do I go about setting up my system to accept passwords? Any help pointing me in the correct direction would be greatly appriciated! Doug My system has to deal with nt so I use encrypted passwords. I am also using one of the nt domain controllers to verify the passwords. To use encrypted passwords you need to put encrypt passwords = yes in the [global] section. Here is what I have: encrypt passwords = yes security = server password server = domaincontroller1, backupdomaincontroller, etc I'm not an expert by any means. Samba security is a little fuzzy to me. However, here is a stab at some other configs. nt4.0 clients and recent win95/98 clients, local authentication: encrypt passwords = yes security = user In this case, each user has to have an account on the samba server and an entry in the smbpasswd file. Alternately, you can map win users to samba server (linux) users with a users.map file in /etc/samba. win95 clients with passwords sent clear text: encrypt passwords = no security = user Pretty much the same as the previous example on user setup. I haven't tried this. If you need to connect nt this way, there is info about a registry entry to force clear text passwords. Info is in the samba-doc package. References: smb.conf man page, ENCRYPTION.txt.gz, security_level.txt.gz On the kernel, I have found 2.2.10 to be pretty solid. It seems faster on my tired old 486-66 cast-off that's running samba. I have heard of file system problems but haven't experienced anything like that. jim Lewis, James M. wrote: After upgrading my system to potato, my samba services no longer work. I get an error message saying that the password supplied is not valid. Everything worked fine under slink. If I remember correctly, part of the instructions on the old setup was to remove password encryption so windows 95 could connect (Its been so long, I'm not sure exactly what I did to set it up). The latest version of samba has encryption enabled for windows 95/98. Where should I look to modify my configuration files? Are there any docs on conversion issues from the version that was stable with slink? If all you did was upgrade samba, then the problem might be with the kernel version. I had a similar problem with 2.0.36 kernel. I upgraded to 2.2.10 and things worked right. The problem was that samba could not become the connected user. Thanks, Doug -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null jim -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
RE: samba password changes after potato upgrade
I had the same problem when I upgraded to potato with samba 2.04. There's probably a better way to do this, but I fixed it using smbpasswd with the username for each of my users and entered a default password. After that, it seems to work fine. Craig -- From: Doug Thistlethwaite Sent: Monday, July 19, 1999 2:12 AM To: Lewis, James M.; debian-user@lists.debian.org Cc: Doug Work Subject: Re: samba password changes after potato upgrade Ok, I upgraded to 2.2.10 kernel but my Samba still does not recognise my passwords from my win 95 system. My old samba configuration used plain text passwords if my memory serves me right. I think there was a problem with encription of passwords when I first installed it. If this is the case, how do I go about setting up my system to accept passwords? Any help pointing me in the correct direction would be greatly appriciated! Doug Lewis, James M. wrote: After upgrading my system to potato, my samba services no longer work. I get an error message saying that the password supplied is not valid. Everything worked fine under slink. If I remember correctly, part of the instructions on the old setup was to remove password encryption so windows 95 could connect (Its been so long, I'm not sure exactly what I did to set it up). The latest version of samba has encryption enabled for windows 95/98. Where should I look to modify my configuration files? Are there any docs on conversion issues from the version that was stable with slink? If all you did was upgrade samba, then the problem might be with the kernel version. I had a similar problem with 2.0.36 kernel. I upgraded to 2.2.10 and things worked right. The problem was that samba could not become the connected user. Thanks, Doug -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null jim -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: samba password changes after potato upgrade
Subject: Re: samba password changes after potato upgrade Date: Sun, Jul 18, 1999 at 11:19:16PM -0700 In reply to:Doug Thistlethwaite Quoting Doug Thistlethwaite([EMAIL PROTECTED]): One more thing about Samba. Does anyone know why the distribution does not have all of the tools that are described on the samba site. There is a file that describes a set of steps to debug problems like I am having. The third step call for the use of smbclient which is not in any of the deb files as far as I can tell. Where can I get this program? In step 4 it says to us an utility called nmblookup. Is this file available in a deb install file? Thanks for your time, Doug What version are you running? dpkg -s samba I have version 1.9.18p10-7 installed and have everything you are looking for. -- Real computer scientists don't program in assembler. They don't write in anything less portable than a number two pencil. ___ Wayne T. Topa [EMAIL PROTECTED]
Re: samba password changes after potato upgrade
Humm. I was using 2.0.36 with slink and it worked fine. I will checkout the kernel upgrade and see what is up. How stable is 2.2.10? Doug Lewis, James M. wrote: After upgrading my system to potato, my samba services no longer work. I get an error message saying that the password supplied is not valid. Everything worked fine under slink. If I remember correctly, part of the instructions on the old setup was to remove password encryption so windows 95 could connect (Its been so long, I'm not sure exactly what I did to set it up). The latest version of samba has encryption enabled for windows 95/98. Where should I look to modify my configuration files? Are there any docs on conversion issues from the version that was stable with slink? If all you did was upgrade samba, then the problem might be with the kernel version. I had a similar problem with 2.0.36 kernel. I upgraded to 2.2.10 and things worked right. The problem was that samba could not become the connected user. Thanks, Doug -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null jim
Re: samba password changes after potato upgrade
Subject: Re: samba password changes after potato upgrade Date: Sun, Jul 18, 1999 at 05:10:07PM -0700 In reply to:Doug Thistlethwaite Quoting Doug Thistlethwaite([EMAIL PROTECTED]): Humm. I was using 2.0.36 with slink and it worked fine. I will checkout the kernel upgrade and see what is up. How stable is 2.2.10? Doug Very stable. I have been using it for over a month. HTH, YMMV, HAND -- Hi, my name is Any Key. Please don't hit me! ___ Wayne T. Topa [EMAIL PROTECTED]
Re: samba password changes after potato upgrade
Ok, I upgraded to 2.2.10 kernel but my Samba still does not recognise my passwords from my win 95 system. My old samba configuration used plain text passwords if my memory serves me right. I think there was a problem with encription of passwords when I first installed it. If this is the case, how do I go about setting up my system to accept passwords? Any help pointing me in the correct direction would be greatly appriciated! Doug Lewis, James M. wrote: After upgrading my system to potato, my samba services no longer work. I get an error message saying that the password supplied is not valid. Everything worked fine under slink. If I remember correctly, part of the instructions on the old setup was to remove password encryption so windows 95 could connect (Its been so long, I'm not sure exactly what I did to set it up). The latest version of samba has encryption enabled for windows 95/98. Where should I look to modify my configuration files? Are there any docs on conversion issues from the version that was stable with slink? If all you did was upgrade samba, then the problem might be with the kernel version. I had a similar problem with 2.0.36 kernel. I upgraded to 2.2.10 and things worked right. The problem was that samba could not become the connected user. Thanks, Doug -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null jim -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: samba password changes after potato upgrade
One more thing about Samba. Does anyone know why the distribution does not have all of the tools that are described on the samba site. There is a file that describes a set of steps to debug problems like I am having. The third step call for the use of smbclient which is not in any of the deb files as far as I can tell. Where can I get this program? In step 4 it says to us an utility called nmblookup. Is this file available in a deb install file? Thanks for your time, Doug P.S: The file I was looking at is http://us1.samba.org/samba/docs/DIAGNOSIS.html
RE: samba password changes after potato upgrade
After upgrading my system to potato, my samba services no longer work. I get an error message saying that the password supplied is not valid. Everything worked fine under slink. If I remember correctly, part of the instructions on the old setup was to remove password encryption so windows 95 could connect (Its been so long, I'm not sure exactly what I did to set it up). The latest version of samba has encryption enabled for windows 95/98. Where should I look to modify my configuration files? Are there any docs on conversion issues from the version that was stable with slink? If all you did was upgrade samba, then the problem might be with the kernel version. I had a similar problem with 2.0.36 kernel. I upgraded to 2.2.10 and things worked right. The problem was that samba could not become the connected user. Thanks, Doug -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null jim
