similar to: Could not fetch trust account password for domain ...

I've installed the latest/greatest from Samba (3.0.alpha...). I've been following the directions from this site (http://samba.linuxbe.org/en/samba/learn/swat.html) on how to set up SWAT for configuring Samba. The problem I'm running into is logging into SWAT. I've tried every user imaginable and still no luck. I've enabled the SWAT service using xinetd, and it actually

I'm a bit confused on several points of the security infrastructure of Samba. First, and simplest, why (and is it necessary) do we need to keep a smbpasswd file when the Linux/Unix passwd file could be suffice? I like the idea of mapping particular users to a given UNIX account via the username map option, but I see no reason in specifying a separate password file for these same UNIX users.

Good morning all, I am new to this list. I have been running FreeBSD 5.1 with dovecot successfully for about a year. Just recently, I built a new machine with 5.2.1-p5 on the Intel platform with dovecot-0.99.10.4_2. When I use the same configuration options on the new machine, I get Apr 24 10:53:59 standrew pop3-login: Login: tabthorpe [172.16.1.100] Apr 24 10:53:59 standrew pop3(tabthorpe): We

I created a centos 7 docker container in which I want to mount a NFS share in. Said share is owned by user virtual with uid 1200. So I do some exporting (docker container is in 172.17.0.0/16): spindizzy> cat /etc/exports /export 10.0.0.0/24(ro,fsid=0,no_subtree_check,sync) 172.17.0.0/16(ro,fsid=0,no_subtree_check,sync) [...] /export/mail 172.17.0.0/16(rw,root_squash,no_subtree_check,sync)

Hello, I wondered how folks monitored slaves. In my case, I am using Nagios and the check_ups plugin. It seems to work fine but being new to nut, I'm seeking confirmation that this is a sane approach. The goal: confirm the slaves have contact with the master. The environment: * FreeBSD 12.1 * nut-2.7.4 installed from package Background: I am replacing an APC 2200 UPS (still in use) with

Hi All, Does anyone know if there has been any developments in asterisk to use LineJacks to dial out (connect to the PSTN)? The card works perfectly with virtually anything else but asterisk. Maybe the CVS versions have some work on it? Cheers, -Z -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com

Hi, New to the list. Just wanted to know if someone managed to get LineJack to make outgoing calls to the PSTN line in Asterisk. Any dev on this? Cheers, -P -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup

I do not have any ideas on this. Where should I start. [root at 192.168.1.80 security]# date && time ssh -v 192.168.1.21 date Fri May 23 11:43:53 EDT 2008 OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /root/.ssh/config debug1: Applying options for 192.168.1.21 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1:

Hi all I have system with Redhat Enterprise Server 4.0 with SAMBA 3 . i want to configure samba 3 with LDAP, to integrate LDAP with PAM , it's not working, ie i am unable to join clients to the samba server and when i type the following command it's does not show any thing getent passwd | grep Administrators My windows clients, cannot join to the SAMBA PDC, ie when i give the domain,

seems to mess up the pam for swat. [root at host67 security]# rpm -qf /etc/pam.d/samba samba-3.0.25b-1.el4_6.4 [root at host67 security]# cat /etc/pam.d/samba #auth required /lib/security/pam_stack.so service=system-auth #account required /lib/security/pam_stack.so service=system-auth auth required pam_stack.so service=system-auth account required

Hello, I'm trying to get Winbind to authenticate users that don't have local accounts on a SAMBA BDC. I have (3) BDCs (1) PDC running OpenLDAP 2.1.23 pass backend and Samba 3.0. These are on RedHat 8.0 systems. 3 BDC are also slave LDAP and 1 master directory server on the PDC. I went through the Samba documentation CH21 and made modifications to the BDCs and PDC as follows:

I read the docs and did the following: smbd, nmbd, winbind all running, also able to get domain user/group info. with "wbinfo". However still can't su, telnet to the linux box with my active directory user account on w2k. Am I missing something? In /lib ------ /lib/libnss_winbind.so /lib/libnss_winbind.so.2 /etc/nsswitch.conf ------------------ passwd: files winbind shadow:

Hi All, I've got winbind happening and can telnet into the box using my NT account (have manually made home directory) and it works a treat. When I try to ssh in I get access denied. As you can see from the log winbind is granting access but it seems that sshd is blocking access before winbind can get to it? That's a guess of course. Any ideas? Matthew

I'm struggling just as much as the next person on this setup. Although; I do have it working under Mandrake 9.2 with Samba3.0.pre1. Perhaps we can work together and figure out what is different between setups. smb.conf: > #======================= Global Settings ===================================== > [global] > > # 1. Server Naming Options: > workgroup = LABOR >

I am following the instruction in Samba by Example chapter 6 on a RHEL4 server. Everything seems OK until I get to 6.3.5.7, which says to do the following:- root# getent passwd | grep Adminstrator which returns nothing, indicating that the nsswitch (nss_ldap libary) is not working. I cannot find anything in any of the log files to give my a clue nor any hints on how to debug this. Any

----- Original Message ----- From: David Hoang To: samba-bugs@samba.org Sent: Friday, September 20, 2002 4:20 PM Subject: Winbind-bug I am using winbind and I notice it's not letting me logon to my unix box unless i have created a unix-style account with entries in /etc/passwd & shadow. I thought winbind was suppose to allow me to logon using my active directory (w2k) box. I please

Samba setup as a Member Server in native AD domain with winbind authenticating AD users for access to shares. My understanding is that with pam and winbind, domain users can log into the samba server via ssh, even if they do not have a local user account? Logs shows access granted but user unknown, so I must be missing something and need some help. /var/log/messages during an ssh login: Nov

Hi, I have setup linux as a member server (fedora 1), it authenticates against a w2k AD server and runs winbind. I modified the login pam file so can login to the linux box with my windows account. After login I see my windows "home" directory that is mounted from a windows w2k fileserver. All described above works fine the only problem I have that I don't see the owner/group of

What is the trick for having home directories on a samba share be accessible from a windows machine?? I am using winbind with NT to authenticate -- it works fine. I have users with accounts on the samba machine, they have the same usernames and passwords on the NT machine. All users on the samba machine have accounts in /home Is there some sort of trick with the template homedir command, and

Hello, I currently have samba configured with winbind so that I can login using NT authentication with my domain controller. Winbind is working perfectly with the domain, I have /etc/pam.d/login configured perfectly and I can login through the console.etc.. However, when I try to use passwd, it doesn't prompt for a new password, it does this: bash-2.05b$ passwd Changing password for