DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 509FJ88j1188057
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 30DA13858D1E
MIME-Version: 1.0
References: <CAKAoaQnkqcZZiOUMfVctAxT_yKbmKqOizZpXfwXd3BWDc6ga-A AT mail DOT gmail DOT com>
In-Reply-To: <CAKAoaQnkqcZZiOUMfVctAxT_yKbmKqOizZpXfwXd3BWDc6ga-A@mail.gmail.com>
Date: Thu, 9 Jan 2025 16:18:10 +0100
Message-ID: <CAKAoaQm0uCqPUw3HB-OxNNqSc1vS50buOTmQJBk9NdMap+g-qA@mail.gmail.com>
Subject: Re: Using forwarded filesystems with Windows Remote Client (e.g.
 accessing //TSCLIENT/L via mstsc.exe) ?
To: cygwin AT cygwin DOT com
From: Roland Mainz via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Roland Mainz <roland DOT mainz AT nrubsig DOT org>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

On Wed, Jan 8, 2025 at 5:33 PM Roland Mainz <roland DOT mainz AT nrubsig DOT org> wrote:
>
> Hi!
>
> ----
>
> Does Cygwin 3.6 support filesystems which have been forwarded by the
> Windows Remote Client (mstsc.exe) ?
>
> I tried to access such a forwarded dir, but $ ls -l # returned this:
> ---- snip ----
> $ bash -c 'cd //TSCLIENT/L && ls -l'
> ls: cannot read symbolic link 'newtestmachine_dir2': Invalid argument
> ls: cannot read symbolic link 'winserver2019_admindir2': Invalid argument
> total 665207504417527
> ?--xr--r-x     0 Unix_User+2       Unix_Group+1252
> 8589934592 Jan  1  1970  builds
> ?--xr--r-x 65535 Unix_User+0       Unix_Group+6539296
> 8589934592 Jan  1  1970  download
> ?--xr--r-x 65535 Unix_User+0       Unix_Group+6539296
> 8589934592 Jan  1  1970  gitbundles
> ?--xr--r-x 65535 Unix_User+0       Unix_Group+6539296
> 8589934592 Jan  1  1970  newtestmachine1
> l-----xr-x    13 Unix_User+6539088 Unix_Group+6539672
> 4294967295 Jan  1  1970  newtestmachine_dir2
> ?-ws-wS--t 65535 Unix_User+0       Unix_Group+6539296
> 4294967296000 Jan  1  1970  newtestmachine_dir3
> ?--xr--r-x 65535 Unix_User+0       Unix_Group+6539296
> 8589934592 Jan  1  1970  rde
> ?--xr--r-x 65535 Unix_User+0       Unix_Group+6539296
> 8589934592 Jan  1  1970  rde.zip
> ?-ws-wS--t 65535 Unix_User+0       Unix_Group+6539296
> 4294967296000 Mar 17  1970  te_install
> l-----x-wx    11 Unix_User+6539088 Unix_Group+6539672
> 4294967295 Jan  1  1970  winserver2019_admindir2
> ---- snip ----
>
> Any idea what is going wrong in this case ?

Short update:
On the machine which got the forwarded filesystems I get this:
---- snip ----
$ nfs_ea '\??\UNC\TSCLIENT\T\test1' getnfs3attr
Querying extended attribute 'NfsV3Attributes' on file
'\??\UNC\TSCLIENT\T\test1':
ZwQueryEaFile('"') failed with 0xc0000002
---- snip ----

0xC0000002 == STATUS_NOT_IMPLEMENTED

The Windows NFSv3 and NFSv4.1/NFSv.2 drivers implement support for
"NfsV3Attributes", so it seems filesystem forwarding in RDP does not
support EAs (=extended attributes).
Powershell itself can handle files&&cd etc., it seems only
applications which rely on "NfsV3Attributes" are affected...

... maybe in Cygwin there are places where the return code for
|nfs_fetch_fattr3()| isn't checked ?


----

Bye,
Roland
-- 
  __ .  . __
 (o.\ \/ /.o) roland DOT mainz AT nrubsig DOT org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple