When using DFS windows explorer shows owner sids instead of friendly names

All 2003 R2 DC's, when using DFS namespaces when the option to show the
owner column is used in windows explorer the sids show instead of the
friendly user names.

If I go in via a standard unc \\server\share the friendly name resolves
fine or if on the server, only appears to happen via dfs namespaces.

Any ideas ?

I have this issue as well....has anyone found a fix for this yet?

This is only an issue when using a dfs namespace path. When going back to
using the unc directly to the share, the owner column is populated properly.



"m0rk" wrote:

> All 2003 R2 DC's, when using DFS namespaces when the option to show the
> owner column is used in windows explorer the sids show instead of the
> friendly user names.
>
> If I go in via a standard unc \\server\share the friendly name resolves
> fine or if on the server, only appears to happen via dfs namespaces.
>
> Any ideas ?
>

In article <A2EB9B87-37E2-41DC-9FC4->,
says...
> I have this issue as well....has anyone found a fix for this yet?
>
> This is only an issue when using a dfs namespace path. When going back to
> using the unc directly to the share, the owner column is populated properly.
>
>
>
> "m0rk" wrote:
>
> > All 2003 R2 DC's, when using DFS namespaces when the option to show the
> > owner column is used in windows explorer the sids show instead of the
> > friendly user names.
> >
> > If I go in via a standard unc \\server\share the friendly name resolves
> > fine or if on the server, only appears to happen via dfs namespaces.
> >
> > Any ideas ?
> >
>

Our logon script was mapping to the dfs share with \\domain\share rather
than the full dns \\domain.local\share - once changed this it worked
correctly.

So what you are saying is that the DFS must be published in Active Directory,
and to use the Fully Qualified Domain Name name vs NT Domain Name?

Ie. "FQDN\dfs share name\dfs link" seems to work

Why does this work instead of "NT Domain Name\dfs share name\dfs link"

???

"jas0n" wrote:

> In article <A2EB9B87-37E2-41DC-9FC4->,
> says...
> > I have this issue as well....has anyone found a fix for this yet?
> >
> > This is only an issue when using a dfs namespace path. When going back to
> > using the unc directly to the share, the owner column is populated properly.
> >
> >
> >
> > "m0rk" wrote:
> >
> > > All 2003 R2 DC's, when using DFS namespaces when the option to show the
> > > owner column is used in windows explorer the sids show instead of the
> > > friendly user names.
> > >
> > > If I go in via a standard unc \\server\share the friendly name resolves
> > > fine or if on the server, only appears to happen via dfs namespaces.
> > >
> > > Any ideas ?
> > >
> >
>
> Our logon script was mapping to the dfs share with \\domain\share rather
> than the full dns \\domain.local\share - once changed this it worked
> correctly.
>

On Mon, 12 Jan 2009 14:45:01 -0800, confuzzled
<> wrote:

>So what you are saying is that the DFS must be published in Active Directory,
>and to use the Fully Qualified Domain Name name vs NT Domain Name?
>
>Ie. "FQDN\dfs share name\dfs link" seems to work
>
>Why does this work instead of "NT Domain Name\dfs share name\dfs link"

I believe the answer is in "How DFS works" but it is while since I read it. At
least there is a discussion on DNS v Netbios/Wins names.


>
>???
>
>"jas0n" wrote:
>
>> In article <A2EB9B87-37E2-41DC-9FC4->,
>> says...
>> > I have this issue as well....has anyone found a fix for this yet?
>> >
>> > This is only an issue when using a dfs namespace path. When going back to
>> > using the unc directly to the share, the owner column is populated properly.
>> >
>> >
>> >
>> > "m0rk" wrote:
>> >
>> > > All 2003 R2 DC's, when using DFS namespaces when the option to show the
>> > > owner column is used in windows explorer the sids show instead of the
>> > > friendly user names.
>> > >
>> > > If I go in via a standard unc \\server\share the friendly name resolves
>> > > fine or if on the server, only appears to happen via dfs namespaces.
>> > >
>> > > Any ideas ?
>> > >
>> >
>>
>> Our logon script was mapping to the dfs share with \\domain\share rather
>> than the full dns \\domain.local\share - once changed this it worked
>> correctly.
>>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

Fixing the DNS Suffix search order also appears to correct this issue.

"DaveMills" wrote:

> On Mon, 12 Jan 2009 14:45:01 -0800, confuzzled
> <> wrote:
>
> >So what you are saying is that the DFS must be published in Active Directory,
> >and to use the Fully Qualified Domain Name name vs NT Domain Name?
> >
> >Ie. "FQDN\dfs share name\dfs link" seems to work
> >
> >Why does this work instead of "NT Domain Name\dfs share name\dfs link"
>
> I believe the answer is in "How DFS works" but it is while since I read it. At
> least there is a discussion on DNS v Netbios/Wins names.
>
>
> >
> >???
> >
> >"jas0n" wrote:
> >
> >> In article <A2EB9B87-37E2-41DC-9FC4->,
> >> says...
> >> > I have this issue as well....has anyone found a fix for this yet?
> >> >
> >> > This is only an issue when using a dfs namespace path. When going back to
> >> > using the unc directly to the share, the owner column is populated properly.
> >> >
> >> >
> >> >
> >> > "m0rk" wrote:
> >> >
> >> > > All 2003 R2 DC's, when using DFS namespaces when the option to show the
> >> > > owner column is used in windows explorer the sids show instead of the
> >> > > friendly user names.
> >> > >
> >> > > If I go in via a standard unc \\server\share the friendly name resolves
> >> > > fine or if on the server, only appears to happen via dfs namespaces.
> >> > >
> >> > > Any ideas ?
> >> > >
> >> >
> >>
> >> Our logon script was mapping to the dfs share with \\domain\share rather
> >> than the full dns \\domain.local\share - once changed this it worked
> >> correctly.
> >>
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that don't.
>