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
