similar to: Problem with duplicated groups?

I suspect there's something wrong in wbinfo on a freshly installed Samba AD Domain Controller on Ubuntu 18.04 server. wbinfo does not resolve Windows SID to usernames: # wbinfo -S S-1-5-21-299502267-616249376-1417001333-14107 3000103 I should see "SAMDOM\username" instead of "3000103", right? getfacls has the same behavior: # getfacl /var/lib/samba/sysvol # file:

Hi We have a few Linux samba servers that authenticate against our Active Directory domain (Small Business Server 2000). I've added a couple of disks to a FreeBSD 6.1 server in our office and I'm trying to achieve the same but not having much luck. I'm new to all this... I'm not our network admin, but he is BSD-phobic so I thought it was safer to do it myself.

Hi there, I have another problem on WinXP SP2 with samba.3.0.20a. Somehow, in a random situation, once user logged onto the workstations, they were prompted with the winlogon.exe Fatal error + blue screen to death then self-reboot. When I checked out the log from windows, it said there's problem on msgina.dll from WinXP SP2. However, another user can successfully logon to the same workstation

Am 27.02.2015 um 15:17 schrieb Rowland Penny <rowlandpenny at googlemail.com> : > On 27/02/15 14:04, Markert, Martin wrote: >> Hi, >> I've successfully configure idmap_rid to read id mappings from our AD servers: >> >> winbind enum users = Yes >> winbind enum groups = Yes >> winbind use default domain = Yes >>

Am 27.02.2015 um 15:48 schrieb Rowland Penny <rowlandpenny at googlemail.com> : > On 27/02/15 14:28, Markert, Martin wrote: >> Am 27.02.2015 um 15:17 schrieb Rowland Penny <rowlandpenny at googlemail.com> >> : >> >>> On 27/02/15 14:04, Markert, Martin wrote: >>>> Hi, >>>> I've successfully configure idmap_rid to read id

Hi, I'm currently trying the 3.2 version of winbindd (pam + nss + winbindd). I would like to loging with the userPrincipalName on ? Win 2k3 but I can't. Winbindd retrun NT_STATUS_INVALID_PARAMETER_MIX (PAM: 4) Any idea winbindd --version output : Version 3.2.0pre2-GIT--e 85eec1d-test My smb.conf file : [global] security = ads realm =

Am 27.02.2015 um 16:06 schrieb Rowland Penny <rowlandpenny at googlemail.com>: > On 27/02/15 14:59, Markert, Martin wrote: >> Am 27.02.2015 um 15:48 schrieb Rowland Penny <rowlandpenny at googlemail.com> >> : >> >>> On 27/02/15 14:28, Markert, Martin wrote: >>>> Am 27.02.2015 um 15:17 schrieb Rowland Penny <rowlandpenny at

Hi, I'm running samba-3.0.22, linux-kernel-2.6.16 and I'm having troubles with trusted domains. How can I find the suitable DC for each domain? Could be a resolution issue? Bellow my smb.conf and some tests. [global] workgroup = DOM1 netbios name = localhost server string = LOCALHOST Server security = ads realm = MYDOMAINCONTROLLERREALM

We have Samba 3.2.4 on two SLES 10 (one is SP1, the other SP2 64bit) machines. Both are member servers in our ADS, which was over the past month given some additional DCs, new IPs for all DCs, and upgraded to Windows 2008 (from win2003). The krb5.conf and nsswitch.conf files on the two machines are identical; the smb.conf files are *nearly* identical in their common section; the filewall rules

Hello, I've been working on converting our OmniOS home directory member servers from Samba 3.6.25 to 4.3.8. For the first few hours after startup, everything is accessible and works as expected. Eventually, winbindd stops responding and smbd starts logging this error: domain_client_validate: Domain password server not available. At this point, authentications no longer work.

SAMBA 3.0.21c (domain is LINBOXTEXT) Windows 2000 SP4 (domain is ADTEST) Hello, I've established an interdomain trust relationship between SAMBA and Windows. Samba domain users can log into the Windows domain, but Windows domain users can't log to the SAMBA server. For example, if I try to log as "ADTEST/dupond" from Windows to SAMBA, SAMBA log says: [2006/11/15 20:17:05,

Hi list, I'd like to update you on the issue, as I did some more tests. First, I've added some directives to smb.conf (in italic): [global] netbios name = testserver security = ADS workgroup = EXAMPLE realm = EXAMPLE.COM log file = /var/log/samba/%m.log log level = 10 dedicated keytab file = /etc/krb5.keytab kerberos method

Hi All, can anyone make any sense of the error below, please advise if I need to log this as a bug but I'm not sure how to further diagnose what is happening. This is from my winbindd log file, thanks Andy. [2003/11/07 17:47:59, 1] nsswitch/winbindd.c:main(832) winbindd version 3.0.0 started. Copyright The Samba Team 2000-2003 [2003/11/07 17:48:00, 1]

On 27/02/15 14:28, Markert, Martin wrote: > Am 27.02.2015 um 15:17 schrieb Rowland Penny <rowlandpenny at googlemail.com> > : > >> On 27/02/15 14:04, Markert, Martin wrote: >>> Hi, >>> I've successfully configure idmap_rid to read id mappings from our AD servers: >>> >>> winbind enum users = Yes >>> winbind

On 27/02/15 14:59, Markert, Martin wrote: > Am 27.02.2015 um 15:48 schrieb Rowland Penny <rowlandpenny at googlemail.com> > : > >> On 27/02/15 14:28, Markert, Martin wrote: >>> Am 27.02.2015 um 15:17 schrieb Rowland Penny <rowlandpenny at googlemail.com> >>> : >>> >>>> On 27/02/15 14:04, Markert, Martin wrote: >>>>>

I can mount Win 2003 shares on my Macs fine. However, the shares disappear after a while. This behavior is unlike on XP where the mounts stay attached forever. The session timeout on 2003 doesn't matter. It works that way out of the box, and after reconfiguring samba on the MAC to join the windows domain. I think it happens when the MAC goes to sleep and after waking up tries to

Hello all, I've successfully added a samba 3.0.20 server to an Active Directory domain. My only problem seems to be a fairly common one: there are 10 trusted domains with close to 20,000 users in our AD "network", and if I do a "wbinfo -u", wbinfo appears to time out before winbind has finished contacting all 10 domains. I've set the "allow trusted domains"

server: ms 2003 with ads client: debian 3.1/samba 3.0.14 smb.conf: .. [global] workgroup = SP-GRUPPE password server = 10.85.117.150 realm = SP-GRUPPE.DE encrypt passwords = no server string = %h server (Samba %v) obey pam restrictions = yes passdb backend = tdbsam, guest passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .

Hello list, I'm runnung samba 2.2.4 on solaris 2.6 using winbind for account management. The samba server is a member server in a w2k domain. I've tested winbind in two different w2k domain (test and productive) with the same settings and analogue entries in the smb.conf. In the one w2k domain all run properly, in the other one I can join the domain (wbinfo -t tells secret is good), but

I'm setting up Samba in an environment with 2 Active Directory domains setup with a one way trust (DOMAINA -> DOMAINB). Samba is in DOMAINA. From looking at the logs (see below) it appears that winbind is having troubles getting the credentials for the domain controller in DOMAINB. I can get tickets, using kinit, for accounts in both domains. I can join DOMAINA just fine. Running