> 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
>
>
