Filtering ADS requests on a network file system

Quick question,
I’m finishing up work on a network redirector (not using mini-rdr)
that interacts with linux/unix machines and I’d like a way to filter
out windows explorer CREATE requests on alternate data streams, which
explorer seems to do a LOT of just browsing around. These requests add
a good bit of overhead that I’d like to remove - since my create needs
to verify that the file exists, and does so by passing the request
across the wire. The file servers I am connecting to support both :
and $ in the filename, thus doing a simple expression test within the
IFS on the file name coming in from explorer might not be the best.
Any suggestions on how I can remove the overhead of passing all these
ADS create requests across the wire?
Thanks.
-Jeff

I wonder, does the redirector tell us all that alternative data streams are
supported, as in ZwQueryVolumeInformation FileFsAttributeInformation would
return with FILE_NAMED_STREAMS set in FILE_FS_ATTRIBUTE_INFORMATION
FileSystemAttributes or does explorer just go ahead and try to open the
named streams, irrespective of the FileSystemAttributes?

“Jeff Mancuso” wrote in message news:xxxxx@ntfsd…
> Quick question,
> I’m finishing up work on a network redirector (not using mini-rdr)
> that interacts with linux/unix machines and I’d like a way to filter
> out windows explorer CREATE requests on alternate data streams, which
> explorer seems to do a LOT of just browsing around. These requests add
> a good bit of overhead that I’d like to remove - since my create needs
> to verify that the file exists, and does so by passing the request
> across the wire. The file servers I am connecting to support both :
> and $ in the filename, thus doing a simple expression test within the
> IFS on the file name coming in from explorer might not be the best.
> Any suggestions on how I can remove the overhead of passing all these
> ADS create requests across the wire?
> Thanks.
> -Jeff
>
>

As far as I can tell, explorer doesn’t respect that.
I certainly never set that in my code, and it doesn’t matter if I use
the device type of network_filesystem or disk_filesystem, it still
makes the request. I can remove support for files given the ADS naming
convention, but I’d like to find a better solution.
-Jeff

On Sun, 17 Oct 2004 00:20:00 +0100, Lyndon J Clarke
wrote:
> I wonder, does the redirector tell us all that alternative data streams are
> supported, as in ZwQueryVolumeInformation FileFsAttributeInformation would
> return with FILE_NAMED_STREAMS set in FILE_FS_ATTRIBUTE_INFORMATION
> FileSystemAttributes or does explorer just go ahead and try to open the
> named streams, irrespective of the FileSystemAttributes?
>
> “Jeff Mancuso” wrote in message news:xxxxx@ntfsd…
>
>
> > Quick question,
> > I’m finishing up work on a network redirector (not using mini-rdr)
> > that interacts with linux/unix machines and I’d like a way to filter
> > out windows explorer CREATE requests on alternate data streams, which
> > explorer seems to do a LOT of just browsing around. These requests add
> > a good bit of overhead that I’d like to remove - since my create needs
> > to verify that the file exists, and does so by passing the request
> > across the wire. The file servers I am connecting to support both :
> > and $ in the filename, thus doing a simple expression test within the
> > IFS on the file name coming in from explorer might not be the best.
> > Any suggestions on how I can remove the overhead of passing all these
> > ADS create requests across the wire?
> > Thanks.
> > -Jeff
> >
> >
>
>
> —
> Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

Anyone else have anny suggestions here?
-Jeff

On Sun, 17 Oct 2004 02:06:01 -0400, Jeff Mancuso wrote:
> As far as I can tell, explorer doesn’t respect that.
> I certainly never set that in my code, and it doesn’t matter if I use
> the device type of network_filesystem or disk_filesystem, it still
> makes the request. I can remove support for files given the ADS naming
> convention, but I’d like to find a better solution.
> -Jeff
>
>
>
>
> On Sun, 17 Oct 2004 00:20:00 +0100, Lyndon J Clarke
> wrote:
> > I wonder, does the redirector tell us all that alternative data streams are
> > supported, as in ZwQueryVolumeInformation FileFsAttributeInformation would
> > return with FILE_NAMED_STREAMS set in FILE_FS_ATTRIBUTE_INFORMATION
> > FileSystemAttributes or does explorer just go ahead and try to open the
> > named streams, irrespective of the FileSystemAttributes?
> >
> > “Jeff Mancuso” wrote in message news:xxxxx@ntfsd…
> >
> >
> > > Quick question,
> > > I’m finishing up work on a network redirector (not using mini-rdr)
> > > that interacts with linux/unix machines and I’d like a way to filter
> > > out windows explorer CREATE requests on alternate data streams, which
> > > explorer seems to do a LOT of just browsing around. These requests add
> > > a good bit of overhead that I’d like to remove - since my create needs
> > > to verify that the file exists, and does so by passing the request
> > > across the wire. The file servers I am connecting to support both :
> > > and $ in the filename, thus doing a simple expression test within the
> > > IFS on the file name coming in from explorer might not be the best.
> > > Any suggestions on how I can remove the overhead of passing all these
> > > ADS create requests across the wire?
> > > Thanks.
> > > -Jeff
> > >
> > >
> >
> >
> > —
> > Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
> >
> > You are currently subscribed to ntfsd as: xxxxx@gmail.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
>