On Wed, 16 Jul 2008 12:55:49 -0700, linearred <nospam@nospam.nospam> wrote:

> Well, on second look, getting the drive format may not matter. I mapped
> a
> drive letter to a Samba file share UNC address on a Solaris box.
> DriveInfo.DriveFormat on the mapped letter returned "NTFS", but it
> appears
> that the volume still does not support alternate data streams. (In
> theory,
> is an NTFS volume actually required to support ADS streams, or is that an
> optional feature... or is this a Samba bug?)

Frankly, I think you're asking in the wrong newsgroup. I understand that
you're using .NET, but the expertise here is probably not focused on these
kinds of issues. You'll probably have better luck asking a .NET-neutral
question that's specifically about accessing the ADS on an NTFS volume
over a network connection on a forum that is more specifically about file
systems and/or Windows networking.

You might even trying the Samba community over at http://www.samba.org/.
They've got a mailing list, with archives, and an IRC channel there. Of
course, Samba is open-source, so if all else fails, you could always look
at the source code to see if there's anything in there that should be
supported ADS.

My own guess is that you can't depend on a networked volume supporting
NTFS-specific features over that connection, and in fact it may be that
it's simply something that's completely unsupported on Windows networking,
never mind Samba. I'm not even sure that using native Windows-to-Windows
SMB networking, it would be supported (but then again, I'm not the expert
you're looking for, so... :) ).

Pete