similar to: how to use /etc/passwd and /etc/shadow for samba passwords?

i'm looking for an answer to the problem WIN98/samba-connection. It shows the same failure as shown by WinNT unless the change of Registry to EnablePlainPasswd. Is there an answer where the entry "EnablePlainPasswd" should be by WIN98? Enable encryoptedPasswd in smb.conf brought no solution. Thanks an many greetings Lothar M?hlbauer Lothar.Muehlbauer@iiv.de

Hi Folks, I need to use Shadow Passwords or point Samba to a password file other then /etc/passwd. Do I need to be running 1.9.17? If you could please respond to me privately, I'll post a summary of responses to the list. Thank You Pam Buffington pamc@cc.gatech.edu

I don't know if this got posted. Sorry for the double. Basically I have 4 Win AD servers I'm trying to use for password servers. I can net join others but not this one. All AD servers are identical and I have a computer account on all 4. What does this error mean? Thank u ! I'm also getting intermittent “password server not available” and users can't connect at random. I've

Does anyone Know the procedure for Windows 2000 workstation, in order to not encrypt passwords. What I needed is something similar to the transcription I make below that works for windows nt4 and 98. Thank's Emanuel Duarte (Portugal) ********************************** This should take care of the "clear text password" problemsyou've encountered: For Win 98 (To enable

I have a question about Win98 and Samba. Is there a registry fix similar to the WinNT plaintext passwd that needs to be performed? Win95, and WinNT can see Linux via Netbios, but the same machine, running Win98 cannot see the Linux box. I am running the most current version of Samba. The WinNT box can see the 98 machine fine. Does anyone have any experience with this? Please let me know if

Hello, This patch fix order of checking password in systems that contains /etc/shadow file (Linux for example). The order is exactly like in linux-shadow-password package. First is checked /etc/passwd but if password field contains "x" then password is read from /etc/shadow instead. Best regards, Krzysztof Ol?dzki -------------- next part -------------- A non-text attachment was

We've been running Samba2.2.x and relying on the underlying Solaris user authentication (/etc/passwd /etc/shadow). For historical reasons, we've allowed plaintext passwords. Now as we've upgraded to Samba 3.0.3. we would like to continue this method of authentication (at least until we can implement ldap). The docs are sketchy at best (you can use plaintext authentication, etc.), but

Fellow list members, I recently tried to add a user to a little used server that hadn't see a change in users for quite a while. When I use system-config-users I get an error alert that says - The user database cannot be read. This problem is most likely caused by a mismatch in /etc/passwd and /etc/shadow. The program will exit now. I awk'ed out the user ID's and ran diff.

Author: basabi Repository: /hg/zfs-crypto/gate Revision: a7008170624f2dc6e0cfef8b2e6f356bf5d3b141 Log message: 6253934 passwd and pwconv are crashing with wrong entry in /etc/shadow Files: update: usr/src/lib/libc/port/gen/getspent_r.c

Does the same fix for windows 95 fix windows 98? Does anyone know for sure -------------------------------------------- You can tune a piano but you can't tuna fish - REO Speedwagon

On Tue, Nov 08, 2005 at 08:04:54AM -0800, Bryan J. Smith wrote: > > > NAS offers safe concurent access (generally, there might be > > some NAS devices outthere that do not). NAS device will > > manage file system internally, and export it over NFS or > > SMB protocols to the clients. > > Such NAS' are a combined host+storage aka

Hello All, I''m new to puppet, and I''d like to know: Is there a formal best practices guide for syncing { /etc/passwd, shadow, group, hosts} across clients from the master? For instance; is it a better practice to make a hard link to these files and share the link, as opposed to just sharing the files directly via a target in fileserver.conf? Inquiring minds want to know...

Hi Jerry/Samba Team I have Samba 3.0.10 installed on Solaris8 server and Samba-client-2.2.10 installed on Linux Red Hat2.1AS servers The Linux servers use Samba to mount filesystems from Solaris8 server. My question is how to find out on the Solaris8 server which Linux servers are using Samba to mount from. Because it is hideous to go to every Linux server and see which Solaris8 server they are

Greetings- I have not found discussed / documented what to do with machine accounts when moving a Samba PDC to new hardware. I have seen that uid/gid numbers must match between the old/new system. I am thinking to use adduser to accomplish that, then make the numbers on the new server match, using a text editor. After that, can I simply enter the machine account entries by hand with a text

Hi! I'm new on the list, so please, be patient with me! I have a problem for wich I can't find the answer in the FAQ. Until recently I was running a 16 PC-s network with SCO OpenServer 5.0.4 and Samba 1.9.16p11 on the server and mixed clients (Win 3.11 to Win 95 OSR2). The users on the network have access to a PUBLIC directory on they own user directories on the server without

Greetings- I am wondering if anyone from the Samba team would happen to have interest in creating official builds for Ubuntu? To add a twist, unfortunately I would not be fishing for 7.10 packages, but rather 7.04 as we ran into too many issues with 7.10 whereas 7.04 seems rock solid stable. Or, are there packages built of Samba releases for Ubuntu external to samba.org? Thanks, -- Michael

I am somewhat confused... I understand that the preferred method to mount a Samba share with a Linux client is to use "mount -t cifs" rather than "mount -t smbfs". I get the impression that smbfs is samba.org developed code where as cifs is from elsewhere. Thus the point of confusion. Why is samba.org not developing the preferred code in this case? A sub question to that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Date: Thu, 16 Oct 2003 12:25:48 +0200 (CEST) > From: Dani Pardo <dani@enpl.es> > Subject: [Samba] Migrating /etc/shadow passwords to LDAP > To: <samba@lists.samba.org> > Message-ID: <Pine.LNX.4.33L2.0310161221220.5408-100000@minerva> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > > Hi!. Since now, I

We have bumped into a most odd problem. Server: Debian Etch and their Samba 3.0.24-2 Client: WinXP SP2, MSI v3, all hot fixes The following settings are in place on the server: #!/bin/bash # # initGrps.sh # Map Windows Domain Groups to UNIX groups net groupmap add ntgroup="Domain Admins" unixgroup=domadmin rid=512 type=d net groupmap add ntgroup="Domain Users"

Greetings- I am working through coming up with a Linux client integration to Samba PDC's. I mount several shares with this sort of syntax: /bin/mount -t cifs -o credentials=/home/userid/.smbcredentials,uid=userid,gid=userid,dmask=0777,fmask=0666 //ldslnx01/data /mnt/ldslnx01/data/ However when I create new files/dirs on the Samba share from the Linux workstation, the perms are not 0666/0777