search for: tuser16

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 shorthostn...

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 (yes/no)? yes > Warning: Permanently added 'lws4' (ECDS...

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 some...

Without trying your suggestions, I know that a domain user cannot login via ssh. Neither of these work: > [bob at dn-pc ~]$ ssh tuser16 at 192.168.16.220 > tuser16 at 192.168.16.220's password: > Permission denied, please try again. > tuser16 at 192.168.16.220's password: > Permission denied, please try again. > tuser16 at 192.168.16.220's password: > tuser16 at 192.168.16.220: Permission denied > (...

...efstype=" to "cifs" and failure remained the same (so, changed it back to "fuse".) This leads me to think sign in permissions issues? The auth.log shows: > root at lws4:~# tail -f /var/log/auth.log > Sep 26 06:22:29 lws4 sshd[2296]: Failed password for invalid user tuser16 > from 192.168.24.30 port 33008 ssh2 > Sep 26 06:22:50 lws4 sshd[2296]: pam_winbind(sshd:auth): getting password > (0x00000388) > Sep 26 06:22:50 lws4 sshd[2296]: pam_winbind(sshd:auth): pam_get_item > returned a password > Sep 26 06:22:51 lws4 sshd[2296]: pam_winbind(sshd:auth):...

...hgroup: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 one. > >...

...> > > > 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, > &...

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 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 (yes/no)? yes > Warning: Permanently added...

...> > > > 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, > &...

yes 'FS_PRUEBA_3' is the share name El vie., 25 sept. 2020 a las 14:03, Rowland penny via samba (< samba at lists.samba.org>) escribi?: > On 25/09/2020 17:50, jmpatagonia via samba wrote: > > Is still not working > > > > <volume fstype="cifs" > > server="domain-server2.policia2.rionegro.gov.ar" > >