Hi, in my solaris , smb.conf i have enabled the encrypt password option. Windows 95 PCs do not send encrypted passwords. How do i get around that?. Like it is now, users at windows 95 PCs can not share the solaris dir. S _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
> Hi, > in my solaris , smb.conf i have enabled the encrypt password option. > Windows 95 PCs do not send encrypted passwords. How do i get around that?. > Like it is now, users at windows 95 PCs can not share the solaris dir.If the client does not send encrypted passwords, samba takes the plaintext password and checks it again /etc/passwd, /etc/shadow, nis, pam or what ever is used on your system. With out any special setup wie do not have any problems with a mixture of plaintext and encrypted passwords. Are your solaris user accounts disabled in /etc/passwd? Christian> S > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >___________________________________________________________________ Unix *is* userfrendly, its only selectiv about its users, ... freak@aixd2[tran_var] cat ?210?0/m2t*.log | grep "stelle(26),fx" | \ awk 'BEGIN {FS=","}; {print $4}' | sed 's/-//' | \ ssh -l barth fbk.mv.uni-kl.de "cat - | unix2dos > fx26.txt"
> you mean in [gloabl] add: > include = /usr/local/samba/lib/security.Win95 ?? > security.Win95 already exist or does it have to be created > and modified?.include parameters let you insert text into your smb.conf just as if they had been typed in. So, don't put [global] into your include file! You must make the file security.Win95> excuse my stupid question but what you mean by %m > or %I?.%m is the netbios name of the client, %I is the ip of the client. %a returns the OS of the calling client. Samba generates a lot of information about itself and the client whenever a client connects. These can be accessed by your smb.conf In the book that comes with the SWAT GUI, see sections 4.3 and 4.1.2. (Actually, I would read the whole thing, if I had time.) I posted a smb.conf entry and a script to allow users to see all these variables several days ago. If you can, check old posts from 13 Sep. It was called: Script for capturing variables Joel