similar to: Authentication in remote domail

Dear all, I have a problem with adduser script in smb.conf. I traing to log in WinXP as a user from trusted domain. But it writes me alwais this fail: useradd: unable to lock password file [2004/10/21 14:00:53, 3] auth/auth_util.c:smb_create_user(53) smb_create_user: Running the command `/usr/sbin/useradd -m veronika' gave 1 My add user script in smb.conf: add user script =

Hi, can I establish interdomain trust between two domains across NAT. If yes, please how??? Thank you, Sopik Bronislav

I have a problem with Samba: I want to make trust between two Samba domains. I have setup the trust on the DOMAINB server then on the Samba DOMAINA server "net rpc trustdom establish DOMAINB" I then get the following: Password: [entered password] Could not connect to server SERVERB [this is the PDC for the DOMAINB domain] Trust to domain DOMAINB established When I then try

I have a problem with Samba: I want to make trust between two Samba domains. I have setup the trust on the DOMAINB server then on the Samba DOMAINA server "net rpc trustdom establish DOMAINB" I then get the following: Password: [entered password] Could not connect to server SERVERB [this is the PDC for the DOMAINB domain] Trust to domain DOMAINB established When I then try

Hi, I have two servers, servera (DOMAINA) and serverb (DOMAINB). I have made a trust between this domain. But I try logon computer from domaina as user for domainb, the log in serverb wrotes me that a authentication was succeded: [2004/10/12 17:19:19, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(620) SAM Logon (Network). Domain:[DOMAINB]. User:[bronasek@\\XP1] Requested Domain:[DOMAINB]

> > I love diving : ) > Ok mathias, Can you explain this. This i dont get.... Why is this output so different, and i dont mean the difference with NTDOMAIN\.. See the groups differences... between a ADDC and a member server.. Samba 4.4.3 ADDC id someusername uid=10002(NTDOMAIN\someusername) gid=10000(NTDOMAIN\domain users) groups=10000(NTDOMAIN\domain

And dont forget : https://wiki.samba.org/index.php/Idmap_config_ad I also noticed and incorrect mapping, which "looks" like rights issues like in the thead here. ( it is imo not a right issue.. ) read on.. NTDOMAIN\enterprise read-only domain controllers:x:3000202: NTDOMAIN\domain admins:x:10001:NTDOMAIN\administrator NTDOMAIN\domain users:x:10000: NTDOMAIN\domain guests:x:10002:

Config: Samba 3 trusts a win2003 domain. XP workstations joined to Samba PDC domain. When a user in the 2003 domain tries to login using an XP workstation and choosing the 2003 domain in the "log onto" box this fails unless the user also has a Linux user account. Is there a way around this? Is this just the way it works? Thanks Lee Baker

On 22/06/16 13:44, lingpanda101 at gmail.com wrote: > On 6/22/2016 8:19 AM, L.P.H. van Belle wrote: >> And dont forget : >> https://wiki.samba.org/index.php/Idmap_config_ad >> >> I also noticed and incorrect mapping, which "looks" like rights >> issues like in the thead here. ( it is imo not a right issue.. ) read >> on.. >> >>

It appears that you cannot include groups from trusted domains in the 'valid users =' directive on a share. Here is the scenario as I experienced it (names have been changed to protect the innocent): Configuration: - Samba 3.0.21b as a member server in a real NT4 domain (security = domain) called 'NTDOMAIN' - NTDOMAIN has a two-way trust with Windows 2003 Active Directory

can you try : smbclient //SERVER.DOMAIN.TLD/netlogon -k bet that works.. Louis >-----Oorspronkelijk bericht----- >Van: heinz.hoelzl at gvcc.net >[mailto:samba-bounces at lists.samba.org] Namens Heinz H?lzl >Verzonden: dinsdag 14 april 2015 10:55 >Aan: samba at lists.samba.org >CC: pug at felsing.net; schnaggy at schnaggy.de >Onderwerp: Re: [Samba] samba 4.2 RDP

Hi Heinz, Baris wrote me the following: > i'm using samba4 and RDP running.... > my configuration: > > smb.conf > > .. > auth methods = sam, winbind, ntdomain, ntdomain:winbind > server services = s3fs, winbind, rpc, nbt, wrepl, cldap, ldap, kdc, drepl, ntp_signd, kcc, dnsupdate > dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon,

hi, now i did some tests with the "auth methods" option. "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest" -> RDP works -> smbclient -k does not work "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest, samba4" -> RDP hangs an the welcome-scrren -> smbclient -k works fine

I have a Samba server here with 4 users and 4 XP systems. Kind of small, but it does the job. It is running as a PDC with roaming profiles. I should note that I left professionally supporting Windows networking around the time XP came out, so I have maintained an NTDomain through a number of incarnations (NT, Win2000, Samba2/3) and use of someone elses packaging. This time I want to use

Hi, I have deployed a new file server (Samba version 4.6.2, CentOS 7) which is running as a member of an AD domain (The DCs are both Windows server 2012, forest and domain level is 2012 as well). I'm using the AD backend to store SID/UID mappings. So everything is working fine except for one specific user on one specific workstation (Windows 10) who can only access the file server with

Ok. I've done the following, any samba dev, please read below. Looks to me some bug in librpc/ndr/ndr.c But im not a coder.. so please have a look.     Environment. Debian Jessie, samba 4.2.10 (debian)   I remove my proxy2 server from the domain, cleared up the AD. Removed all content from /var/(lib/cache)/samba Removed all other unnneeded services for this test. Removed all

I am having an issue with winbind/samba and my groups. when I type the following: $ groups ntdomain\\jfountain I get the following nothing. When i type this (logged in as jfountain) $ groups I get the following: $ 50000 I am assuming this means domain admins. when i type $./wbinfo -r jfountain I get the following: 50016 50017 50018 50019 50020 50021 50010 50022 50023 50000 I

Thanks for responding On 12/09/2014 05:59 AM, Gaiseric Vandal wrote: > On 12/09/14 00:11, Robert Moskowitz wrote: >> I have a Samba server here with 4 users and 4 XP systems. Kind of >> small, but it does the job. It is running as a PDC with roaming >> profiles. I should note that I left professionally supporting >> Windows networking around the time XP came out,

On Samba AD DC most of these enpoint server are already running -- dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver, mapiproxy Use samba-tool testparm -v first before adding them to the smb.conf I say this because I could not "join" Windows clients to Samba with these running

I'm building 3.0.14a on Mandrake 10.2, trying to use the same config as my other servers (3.0.11), but ACLs are not working. In checking the outout of smbd -b, I see this line is missing: System Headers: HAVE_SYS_ACL_H .... But I am specifying ./configure --with-acl-support ... Adding an acl using 'setfacl -m 'NTDOMAIN+NTUSER' file does successfully add an ACL for the NT