search for: tuser17

....... > sshgroup:x:998:adminlinux > ..................... > But, on my member server that acts as a fileserver for domain users (redirected) files there is no "sshgroup" at this time. The AD has server-ssh group: > root at dc1:~# samba-tool group listmembers server-ssh > tuser17 > tuser16 > I went back and found Louis' email where he explained these two groups. Here is part of that email: > Created "server-ssh" group in AD and gave it a GID. > Add the needed windows users that are allowed to ssh in the server, > only windows users in this on...

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 group somewhere per Louis' instructions,

..................... > > > > But, on my member server that acts as a fileserver for domain users > (redirected) files there is no "sshgroup" at this time. > > The AD has server-ssh group: > > > root at dc1:~# samba-tool group listmembers server-ssh > > tuser17 > > tuser16 > > > > I went back and found Louis' email where he explained these > two groups. > Here is part of that email: > > > Created "server-ssh" group in AD and gave it a GID. > > Add the needed windows users that are allowed to ssh in...

..................... > > > > But, on my member server that acts as a fileserver for domain users > (redirected) files there is no "sshgroup" at this time. > > The AD has server-ssh group: > > > root at dc1:~# samba-tool group listmembers server-ssh > > tuser17 > > tuser16 > > > >? I went back and found Louis' email where he explained these > two groups. > Here is part of that email: > > > Created "server-ssh" group in AD and gave it a GID. > > Add the needed windows users that are allowed to ssh in...