DFS Paths

NTFSD
1

I am seeing some DFS paths in my mini-filter that do not look right to me. Here is the scenario, can someone please tell me if this is normal or if I have done something wrong?

If this is normal, how can I get a proper path?

Physical Path: “\Machine\Folder\Folder2\File.txt”
DFS Path: “\domain.com\Folder\Folder2\File.txt”

Data->TargetFileObject->FileName (in all relavent callbacks, e.g. PreCleanup) contains:

“\Machine\Folder\domain.com\Folder\Folder2\File.txt”

Any ideas?

2

This is a normal DFS pattern, although it is very configuration specific
(I seem to recall that this requires the DFS server be exporting
something from itself AND that it is not in a domain, but the details
are a bit fuzzy.) You get a doubled prefix, complete with the logical
name of the server (so it can differ in exactly the format that you
mentioned.)

You are responsible for figuring this out.

Tony
OSR

3

Thanks Tony.

Is there any documentation out there on this or does everyone just re-invent the wheel?

4

It shouldn’t look configuration specific.

The doubled path form will always be seen on access to a DFS root share. If you don’t see it, an interesting bug has occurred because it’s a direct indication the DFS state machine is not processing the request.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Wednesday, August 20, 2008 7:16 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] DFS Paths

This is a normal DFS pattern, although it is very configuration specific
(I seem to recall that this requires the DFS server be exporting
something from itself AND that it is not in a domain, but the details
are a bit fuzzy.) You get a doubled prefix, complete with the logical
name of the server (so it can differ in exactly the format that you
mentioned.)

You are responsible for figuring this out.

Tony
OSR

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

Well, what we are seeing is:

If the physical folder is on the DC, I get a path that looks like:

\dc_name\path\domain.com\path

If the physical folder is NOT on the DC (i.e. some other file server), the path looks like this:

\file_server\path

In yet another configuration on a customer’s machine (I don’t know what it is), we see the DFS link itself in the FO instead.

This is pretty inconsistent behavior. If the doubled path is normal, what is the algorithm to parse it?