search for: wkdom

..._DLZ. All has gone well until I run: root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. _ldap._tcp.[domain].work has no SRV record Then I run: root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp SRV '[dchost].[domain].work 8080 0 100' -Uadministrator Password for [WKDOM\administrator]: Record _added successfully_ And I am still getting: root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. _ldap._tcp.[domain].work has no SRV record If I run the "add" again, I get: root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp SRV '[dchos...

Yes, sorry, forgot to include in the last email. > root at lws4:~# getent passwd tuser16 > tuser16:*:10016:10000:User 16. Test:/home/WKDOM/tuser16:/bin/sh > On Sat, Sep 26, 2020 at 9:02 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 26/09/2020 14:52, Robert Wooden wrote: > > First, my use of IP addresses is a force of habit. User at shorthostname > > does work but, as I do not normally ssh...

Okay, now so I don't get confused. Yes, /home/WKDOM/tuser16 does exist on the client/workstation. root at lws4:~# getent group > root:x:0: > *..snipped for brevity..* > winbindd_priv:x:129: > sshgroup:x:998:adminlinux > postfix:x:130: > ..snipped for brevity.. > There is no servers-ssh group on the C/W. (I have a server-ssh gr...

...-t SRV _ldap._tcp.[domain].work. >> _ldap._tcp.[domain].work has no SRV record >> >> Then I run: >> >> root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp >> SRV '[dchost].[domain].work 8080 0 100' -Uadministrator >> Password for [WKDOM\administrator]: >> Record _added successfully_ >> >> And I am still getting: >> >> root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. >> _ldap._tcp.[domain].work has no SRV record >> >> If I run the "add" again, I get: >> >>...

...ith you because, I think your correct (you usually are). I manually added the "Domain Users" group id (10000) with samba-tool (samba-tool group addunixattrs "Domain Users" 10000, I think without looking thru my notes) some time ago. The member smb.conf has "idmap config WKDOM : range = 10000-999999" and gid started with 10000, should uid start at (for example) 10001 (for first user to be mapped) and increase sequence (+1 as in 10002) for subsequent users? (Adding uid & gid manually, I am aware that I will need to keep a record of these.) Guide lines you c...

On 8/17/2020 7:59 AM, Rowland penny via samba wrote: > Could it be that 'username' doesn't have a uidNumber ? > > Well, when I run "id [username]" on the DC, I get a "uid=3000013(SUBDOM\[username])" and"gid=10000", etc. When I run "id [username]" on the member server (mbr04) I get "id: 'SUBDOM\[username]': no such

...ect (you usually > are). > > I manually added the "Domain Users" group id (10000) with samba-tool > (samba-tool group addunixattrs "Domain Users" 10000, I think without > looking thru my notes) some time ago. > > The member smb.conf has "idmap config WKDOM : range = 10000-999999" > and gid started with 10000, should uid start at (for example) 10001 > (for first user to be mapped) and increase sequence (+1 as in 10002) > for subsequent users? > > (Adding uid & gid manually, I am aware that I will need to keep a > record...

...what users get > what group on > what domain computer? > > On Sat, Sep 26, 2020 at 10:34 AM Rowland penny > <rpenny at samba.org> wrote: > > > On 26/09/2020 16:23, Robert Wooden wrote: > > > Okay, now so I don't get confused. > > > Yes, /home/WKDOM/tuser16 does exist on the client/workstation. > > > > > > root at lws4:~# getent group > > > root:x:0: > > > /..snipped for brevity../ > > > > > > winbindd_priv:x:129: > > > sshgroup:x:998:adminlinux > > >...

First, my use of IP addresses is a force of habit. User at shorthostname does work but, as I do not normally ssh with hostname. > adminlinux at lws2:~$ ssh tuser16 at lws4 > The authenticity of host 'lws4 (192.168.16.220)' can't be established. > ECDSA key fingerprint is > SHA256:iOPtH7sjCWWoWR/92nVv/fWIp0ogRtlHxeRTrC5EePI. > Are you sure you want to continue connecting

...n? Perhaps you see now why I may have confused what users get what group on what domain computer? On Sat, Sep 26, 2020 at 10:34 AM Rowland penny <rpenny at samba.org> wrote: > On 26/09/2020 16:23, Robert Wooden wrote: > > Okay, now so I don't get confused. > > Yes, /home/WKDOM/tuser16 does exist on the client/workstation. > > > > root at lws4:~# getent group > > root:x:0: > > /..snipped for brevity../ > > > > winbindd_priv:x:129: > > sshgroup:x:998:adminlinux > > postfix:x:130: > > > >...

...o.ca = UTORONTO.CA root at dc01:~# cat /etc/samba/smb.conf # Global parameters [global] netbios name = DC01 realm = EXAMPLE.COM server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate workgroup = WKDOM idmap_ldb:use rfc2307 = yes [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No [netlogon] path = /usr/local/samba/var/locks/sysvol/example.com/scripts read only = No root at dc01:~# cat /etc/bind/named.conf // This is the primary configuration file for the BIND DNS server nam...

...what users get > what group on > what domain computer? > > On Sat, Sep 26, 2020 at 10:34 AM Rowland penny > <rpenny at samba.org> wrote: > > > On 26/09/2020 16:23, Robert Wooden wrote: > > > Okay, now so I don't get confused. > > > Yes, /home/WKDOM/tuser16 does exist on the client/workstation. > > > > > >? ? ?root at lws4:~# getent group > > >? ? ?root:x:0: > > >? ? ?/..snipped for brevity../ > > > > > >? ? ?winbindd_priv:x:129: > > >? ? ?sshgroup:x:998:adminlinux > > >?...

On 11/06/2020 12:16, Bob Wooden via samba wrote: > When I "nslookup". I get: > > root@[dchost]:~# nslookup [dchost].[domain].work > Server:??? ??? 192.168.116.50 > Address:??? 192.168.116.50#53 > > Non-authoritative answer: > Name:??? [dchost].[domain].work > Address: xx.198.245.139 > > This local active directory is the first I have ever setup with a