search for: make_user_info_for_repli

Hi there, I have looked for a solution to my problem on the Internet (and in particular this mailing list), but couldn't find one, probably due to searching for the wrong thing :-) I have an RPI running Samba version 4.9.5-Debian. "pdbedit -L" shows that the user "smbuser" exists. I used "smbpassword" to set the password of "smbuser". I also have

We have been running Samba 2.2.x for some time without problems. Servers are Solaris 2.7 and RH Linux. Clients are a mix of WinNTsp4 and Win2K. Server setting is for plaintext (un-encryted passwords). On upgrading the Samba server to 3.0.0, (smb.conf file unchanged): All WinNt clients fail to authenticare. Win2k clients authenticate correctly. On reverting back to Samba 2.2.x, all cleints

NT4.0 SP4 gives me this error when trying to access a Samba 3.0.23c server. \\Omega300\files is not accessable The specific network password is not correct. omega300 is the samba server, running samaba 3.0.23.c on SCO Openserver 5.0.7. omg180 is a Windows NT4 SP4 box. omega is a Windows 98 box. Passwords are not encrypted. We are also using VisionFS (SCO's smb product, which they no longer

At a number of sites we are using Windows 2000 Server SP4 (APPSERVER) as a Terminal Server and a PDC. All user areas are stored on a NetBSD 1.6.2 server with Samba 3.0.7 using security = domain and a named password server. We've joined the domain from the Samba box (domain DOMAINNAME). In general everything works fine, but when a number of clients log on at around the same time (say 25 users

Hello, After an almost 19 year gap, I need to ask this list for help again :-) I have somewhat specific circumstances, where I think I can tolerate plaintext passwords on the wire as long as I get samba to authenticate against the system /etc/shadow (using PAM) in exchange. 0) I'm using Debian 8.4 (jessie), samba packages 2:4.2.10+dfsg-0+deb8u3. 1) I have created user smbtest with password