Re: Unknown+User and Unknown+Group when using ls via ssh

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 2688 bytes --]

On Feb 18 17:17, James Whitwell wrote:
> Hi,
> 
> We’re having some trouble when logged in via ssh that we don’t have
> when we log in directly (in our case RDP to the server, then start
> bash from the Windows desktop).  Our environment is Windows Server
> 2008 R2 64-bit joined to a Samba domain, running Cygwin 2.4.1 64-bit.
> 
> The problem we’re having seems to be with usernames and groups.  When
> we’re logged in directly, it works perfectly e.g.
> 
> WORKFLOW3:jams:~:$ cd /cygdrive/e
> WORKFLOW3:jams:/cygdrive/e:$ ls -l
> total 12
> dr-xr-x---+ 1 jams         Domain Users  0 Feb 18 10:36 $RECYCLE.BIN/
> drwxrwx---+ 1 wfcron       Domain Users  0 Sep 23 14:13 PDF/
> drwxr-x---  1 Unknown+User Unknown+Group 0 Mar  7  2015 System Volume Information/
> drwxrwx---+ 1 wfcron       Domain Users  0 Sep  7 10:30 Vault/
> WORKFLOW3:jams:/cygdrive/e:$ cd PDF
> WORKFLOW3:jams:/cygdrive/e/PDF:$ ls -l
> total 29696
> -rwxrwx---+ 1 wfcron Domain Users 0 Feb 18 17:09 from-cron*
> drwxrwx---+ 1 wfcron Domain Users 0 Feb 18 11:15 pdf/
> WORKFLOW3:jams:/cygdrive/e/PDF:$
> 
> But when I ssh to the machine and try the same commands, I get
> “Unknown+User” and “Unknown+Group” from “ls”, and can’t “cd PDF” e.g.
> 
> WORKFLOW3:jams:~:$ cd /cygdrive/e
> WORKFLOW3:jams:/cygdrive/e:$ ls -l
> total 4
> dr-xr-x---+ 1 jams         Domain Users  0 Feb 18 10:36 $RECYCLE.BIN/
> drwxr-x---  1 Unknown+User Unknown+Group 0 Sep 23 14:13 PDF/
> drwxr-x---  1 Unknown+User Unknown+Group 0 Mar  7  2015 System Volume Information/
> drwxr-x---  1 Unknown+User Unknown+Group 0 Sep  7 10:30 Vault/
> WORKFLOW3:jams:/cygdrive/e:$ cd PDF
> -bash: cd: PDF: Permission denied
> WORKFLOW3:jams:/cygdrive/e:$
> 
> I’ve tried strace on the ls via ssh (attached) but can’t see anything
> obvious failing in it.

I tried this myself and can't reproduce it in my (granted: very tiny)
AD environment.  But there's an obvious problem in the strace:

  13138   42223 [ldap_init] ls 6764 cyg_ldap::connect_non_ssl: ldap_bind((null)) 0x51

So ldap_bind returns with error code 0x51 which is LDAP_SERVER_DOWN.
Assuming the server is not really down, the error code means the caller
cannot connect to the LDAP server for one reason or the other.  This
reason is not visible from the strace and it might be necessary to hunt
this down locally.  Note that error 0x51 really means contacting the
server fails.  It's not an authentication problem or something like that.


HTH,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]