DFS link to a network attached HDD enclosure

This is my first experience with DFS and am working with a Windows 2003 domain.

I am trying to create a DFS link to a network attached HDD enclosure (D-Link
DNS323). The DNS323 is attached to the network switch.

I got so far as to create the root and link.

When I created the link to the enclosure and the wizard requests the UNC
path to the target, the enclosure does not appear through the 'browse'
button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
appears in the DFS console and when clicked, opens the proper target folder.

I can browse with Windows Explorer to the folder that is created when the
root is created (is this the namespace?), but when I try to open that folder
I get a 'Not accessible' error.

I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
Does the target share have to be physically attached to the server, as mine
is not?

The only way to give the DNS323 a drive letter is to map to it. Mapped
drives cannot be used to create DFS links, correct?

Can someone please tell me why this link is not working.
andwhichvitalinformationIleftout

Thank you,
Chris

As far as I know, you cannot setup a DFS between devices and a Windows Server.
You need to have Windows server in BOTH ENDS.

Thus You need to connect the device to a Windows Server and then sync that server to another Server.

You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
replication.

Chris wrote:
> This is my first experience with DFS and am working with a Windows 2003 domain.
>
> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
> DNS323). The DNS323 is attached to the network switch.
>
> I got so far as to create the root and link.
>
> When I created the link to the enclosure and the wizard requests the UNC
> path to the target, the enclosure does not appear through the 'browse'
> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
> appears in the DFS console and when clicked, opens the proper target folder.
>
> I can browse with Windows Explorer to the folder that is created when the
> root is created (is this the namespace?), but when I try to open that folder
> I get a 'Not accessible' error.
>
> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
> Does the target share have to be physically attached to the server, as mine
> is not?
>
> The only way to give the DNS323 a drive letter is to map to it. Mapped
> drives cannot be used to create DFS links, correct?
>
> Can someone please tell me why this link is not working.
> andwhichvitalinformationIleftout
>
> Thank you,
> Chris


--
-- HAL07, Engineering Services, Norway
-- Info: social.technet.microsoft.com/Forums/ replaces a lot of the newsgroups

On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:

>As far as I know, you cannot setup a DFS between devices and a Windows Server.
>You need to have Windows server in BOTH ENDS.
>
Not true:

From
http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
(who creates these URLs?)
Link targets can be shared folders served by other protocols, such as NetWare
Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
client computers must have the appropriate redirector installed to access those
link targets.


>Thus You need to connect the device to a Windows Server and then sync that server to another Server.
>
>You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
>replication.
>
>Chris wrote:
>> This is my first experience with DFS and am working with a Windows 2003 domain.
>>
>> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
>> DNS323). The DNS323 is attached to the network switch.
>>
>> I got so far as to create the root and link.
>>
>> When I created the link to the enclosure and the wizard requests the UNC
>> path to the target, the enclosure does not appear through the 'browse'
>> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
>> appears in the DFS console and when clicked, opens the proper target folder.
>>
>> I can browse with Windows Explorer to the folder that is created when the
>> root is created (is this the namespace?), but when I try to open that folder
>> I get a 'Not accessible' error.
>>
>> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
>> Does the target share have to be physically attached to the server, as mine
>> is not?
In essence if the client can access \\server\share then it should be able to
access \\dfs\root\linkname --> \\server\share provided it supports DFS
namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
actual UNC of the target. Then the client uses its redirector to access the
resolved target just as if the target UNC had been entered in the first place.
>>
>> The only way to give the DNS323 a drive letter is to map to it. Mapped
>> drives cannot be used to create DFS links, correct?
Yes

>>
>> Can someone please tell me why this link is not working.
>> andwhichvitalinformationIleftout
Nope but start by using the UNC to the share. If that will not work then DFS
will not work. Think of DFS names as an alias for the real UNC name.
>>
>> Thank you,
>> Chris
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

Hal & Dave, I appreciate your replies!

I think my issue is that I don’t have a proper UNC for the share. Because
the D-Link hangs off the network it is not a server share. I have tried
\\server\DLink_IP\share but it is not valid, only \\DLink_IP\share works
(works = creates the folder for the link, but that folder cannot be accessed)
..

Would this hardware configuration prevent a valid UNC?

Cheers,
Chris


"DaveMills" wrote:

> On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:
>
> >As far as I know, you cannot setup a DFS between devices and a Windows Server.
> >You need to have Windows server in BOTH ENDS.
> >
> Not true:
>
> From
> http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
> (who creates these URLs?)
> Link targets can be shared folders served by other protocols, such as NetWare
> Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
> client computers must have the appropriate redirector installed to access those
> link targets.
>
>
> >Thus You need to connect the device to a Windows Server and then sync that server to another Server.
> >
> >You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
> >replication.
> >
> >Chris wrote:
> >> This is my first experience with DFS and am working with a Windows 2003 domain.
> >>
> >> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
> >> DNS323). The DNS323 is attached to the network switch.
> >>
> >> I got so far as to create the root and link.
> >>
> >> When I created the link to the enclosure and the wizard requests the UNC
> >> path to the target, the enclosure does not appear through the 'browse'
> >> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
> >> appears in the DFS console and when clicked, opens the proper target folder.
> >>
> >> I can browse with Windows Explorer to the folder that is created when the
> >> root is created (is this the namespace?), but when I try to open that folder
> >> I get a 'Not accessible' error.
> >>
> >> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
> >> Does the target share have to be physically attached to the server, as mine
> >> is not?
> In essence if the client can access \\server\share then it should be able to
> access \\dfs\root\linkname --> \\server\share provided it supports DFS
> namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
> actual UNC of the target. Then the client uses its redirector to access the
> resolved target just as if the target UNC had been entered in the first place.
> >>
> >> The only way to give the DNS323 a drive letter is to map to it. Mapped
> >> drives cannot be used to create DFS links, correct?
> Yes
>
> >>
> >> Can someone please tell me why this link is not working.
> >> andwhichvitalinformationIleftout
> Nope but start by using the UNC to the share. If that will not work then DFS
> will not work. Think of DFS names as an alias for the real UNC name.
> >>
> >> Thank you,
> >> Chris
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that don't.
>

I have no idea. This groups is focused on DFS and your issue is not DFS at all.
It is the ability to create and then use a share on the D-Link device.


On Mon, 9 Feb 2009 20:03:01 -0800, Chris <>
wrote:

>Hal & Dave, I appreciate your replies!
>
>I think my issue is that I don’t have a proper UNC for the share. Because
>the D-Link hangs off the network it is not a server share. I have tried
>\\server\DLink_IP\share but it is not valid, only \\DLink_IP\share works
>(works = creates the folder for the link, but that folder cannot be accessed)
>.
>
>Would this hardware configuration prevent a valid UNC?
>
>Cheers,
>Chris
>
>
>"DaveMills" wrote:
>
>> On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:
>>
>> >As far as I know, you cannot setup a DFS between devices and a Windows Server.
>> >You need to have Windows server in BOTH ENDS.
>> >
>> Not true:
>>
>> From
>> http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
>> (who creates these URLs?)
>> Link targets can be shared folders served by other protocols, such as NetWare
>> Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
>> client computers must have the appropriate redirector installed to access those
>> link targets.
>>
>>
>> >Thus You need to connect the device to a Windows Server and then sync that server to another Server.
>> >
>> >You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
>> >replication.
>> >
>> >Chris wrote:
>> >> This is my first experience with DFS and am working with a Windows 2003 domain.
>> >>
>> >> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
>> >> DNS323). The DNS323 is attached to the network switch.
>> >>
>> >> I got so far as to create the root and link.
>> >>
>> >> When I created the link to the enclosure and the wizard requests the UNC
>> >> path to the target, the enclosure does not appear through the 'browse'
>> >> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
>> >> appears in the DFS console and when clicked, opens the proper target folder.
>> >>
>> >> I can browse with Windows Explorer to the folder that is created when the
>> >> root is created (is this the namespace?), but when I try to open that folder
>> >> I get a 'Not accessible' error.
>> >>
>> >> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
>> >> Does the target share have to be physically attached to the server, as mine
>> >> is not?
>> In essence if the client can access \\server\share then it should be able to
>> access \\dfs\root\linkname --> \\server\share provided it supports DFS
>> namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
>> actual UNC of the target. Then the client uses its redirector to access the
>> resolved target just as if the target UNC had been entered in the first place.
>> >>
>> >> The only way to give the DNS323 a drive letter is to map to it. Mapped
>> >> drives cannot be used to create DFS links, correct?
>> Yes
>>
>> >>
>> >> Can someone please tell me why this link is not working.
>> >> andwhichvitalinformationIleftout
>> Nope but start by using the UNC to the share. If that will not work then DFS
>> will not work. Think of DFS names as an alias for the real UNC name.
>> >>
>> >> Thank you,
>> >> Chris
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that don't.
>>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

DaveMills wrote:
> On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:
>
>> As far as I know, you cannot setup a DFS between devices and a Windows Server.
>> You need to have Windows server in BOTH ENDS.
>>
> Not true:
>
> From
> http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
> (who creates these URLs?)
> Link targets can be shared folders served by other protocols, such as NetWare
> Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
> client computers must have the appropriate redirector installed to access those
> link targets.
>
>
>> Thus You need to connect the device to a Windows Server and then sync that server to another Server.
>>
>> You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
>> replication.
>>
>> Chris wrote:
>>> This is my first experience with DFS and am working with a Windows 2003 domain.
>>>
>>> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
>>> DNS323). The DNS323 is attached to the network switch.
>>>
>>> I got so far as to create the root and link.
>>>
>>> When I created the link to the enclosure and the wizard requests the UNC
>>> path to the target, the enclosure does not appear through the 'browse'
>>> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
>>> appears in the DFS console and when clicked, opens the proper target folder.
>>>
>>> I can browse with Windows Explorer to the folder that is created when the
>>> root is created (is this the namespace?), but when I try to open that folder
>>> I get a 'Not accessible' error.
>>>
>>> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
>>> Does the target share have to be physically attached to the server, as mine
>>> is not?
> In essence if the client can access \\server\share then it should be able to
> access \\dfs\root\linkname --> \\server\share provided it supports DFS
> namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
> actual UNC of the target. Then the client uses its redirector to access the
> resolved target just as if the target UNC had been entered in the first place.
>>> The only way to give the DNS323 a drive letter is to map to it. Mapped
>>> drives cannot be used to create DFS links, correct?
> Yes
>
>>> Can someone please tell me why this link is not working.
>>> andwhichvitalinformationIleftout
> Nope but start by using the UNC to the share. If that will not work then DFS
> will not work. Think of DFS names as an alias for the real UNC name.
>>> Thank you,
>>> Chris

I apologize.

Well well. you learn every day

--
-- HAL07, Engineering Services, Norway
-- Info: social.technet.microsoft.com/Forums/ replaces a lot of the newsgroups

Thank you for your time Dave.

"DaveMills" wrote:

> I have no idea. This groups is focused on DFS and your issue is not DFS at all.
> It is the ability to create and then use a share on the D-Link device.


I have wondered about this myself.

The folder we are trying to share is not on a Windows OS therefore has not
been set up as a share would be in Windows. The D-Link is designed to be very
sharing but I can't tell how the share would perform in a DFS environment.

Also, because the folder we wish to share does not belong to the server, it
will not have the permission to share it out. This seems more probably,
especially considering the error we get is "Share is not accessible, the
network location cannot be reached".

I may peruse in the correct forum.

Chris







> On Mon, 9 Feb 2009 20:03:01 -0800, Chris <>
> wrote:
>
> >Hal & Dave, I appreciate your replies!
> >
> >I think my issue is that I don’t have a proper UNC for the share. Because
> >the D-Link hangs off the network it is not a server share. I have tried
> >\\server\DLink_IP\share but it is not valid, only \\DLink_IP\share works
> >(works = creates the folder for the link, but that folder cannot be accessed)
> >.
> >
> >Would this hardware configuration prevent a valid UNC?
> >
> >Cheers,
> >Chris
> >
> >
> >"DaveMills" wrote:
> >
> >> On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:
> >>
> >> >As far as I know, you cannot setup a DFS between devices and a Windows Server.
> >> >You need to have Windows server in BOTH ENDS.
> >> >
> >> Not true:
> >>
> >> From
> >> http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
> >> (who creates these URLs?)
> >> Link targets can be shared folders served by other protocols, such as NetWare
> >> Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
> >> client computers must have the appropriate redirector installed to access those
> >> link targets.
> >>
> >>
> >> >Thus You need to connect the device to a Windows Server and then sync that server to another Server.
> >> >
> >> >You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
> >> >replication.
> >> >
> >> >Chris wrote:
> >> >> This is my first experience with DFS and am working with a Windows 2003 domain.
> >> >>
> >> >> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
> >> >> DNS323). The DNS323 is attached to the network switch.
> >> >>
> >> >> I got so far as to create the root and link.
> >> >>
> >> >> When I created the link to the enclosure and the wizard requests the UNC
> >> >> path to the target, the enclosure does not appear through the 'browse'
> >> >> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
> >> >> appears in the DFS console and when clicked, opens the proper target folder.
> >> >>
> >> >> I can browse with Windows Explorer to the folder that is created when the
> >> >> root is created (is this the namespace?), but when I try to open that folder
> >> >> I get a 'Not accessible' error.
> >> >>
> >> >> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
> >> >> Does the target share have to be physically attached to the server, as mine
> >> >> is not?
> >> In essence if the client can access \\server\share then it should be able to
> >> access \\dfs\root\linkname --> \\server\share provided it supports DFS
> >> namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
> >> actual UNC of the target. Then the client uses its redirector to access the
> >> resolved target just as if the target UNC had been entered in the first place.
> >> >>
> >> >> The only way to give the DNS323 a drive letter is to map to it. Mapped
> >> >> drives cannot be used to create DFS links, correct?
> >> Yes
> >>
> >> >>
> >> >> Can someone please tell me why this link is not working.
> >> >> andwhichvitalinformationIleftout
> >> Nope but start by using the UNC to the share. If that will not work then DFS
> >> will not work. Think of DFS names as an alias for the real UNC name.
> >> >>
> >> >> Thank you,
> >> >> Chris
> >> --
> >> Dave Mills
> >> There are 10 types of people, those that understand binary and those that don't.
> >>
> --
> Dave Mills
> There are 10 types of people, those that understand binary and those that don't.
>

In article <C23ED915-29E9-41C6-B3CB->,
Chris <> wrote:
>Thank you for your time Dave.
>
>"DaveMills" wrote:
>
>> I have no idea. This groups is focused on DFS and your issue is not DFS at all.
>> It is the ability to create and then use a share on the D-Link device.
>
>
>I have wondered about this myself.
>
>The folder we are trying to share is not on a Windows OS therefore has not
>been set up as a share would be in Windows. The D-Link is designed to be very
>sharing but I can't tell how the share would perform in a DFS environment.
>
>Also, because the folder we wish to share does not belong to the server, it
>will not have the permission to share it out. This seems more probably,
>especially considering the error we get is "Share is not accessible, the
>network location cannot be reached".
>
>I may peruse in the correct forum.
>
>Chris

I got the impression from one of your earlier post that you could indeed
reach the D-Link share using an UNC path built using the IP address of the
box ("\\10.254.254.41\Volume_1").i

If you can indeed do that but still not use it as a DFS target, then you
are in the right group.

Anyway, why don't you try setting up correct DNS and WINS entries for the
D-Link so you can reach it without using the IP address? Maybe the DFS referral
needs a *name* to work? If nothing else, it will make your UNC paths look less
messy. And with a WINS entry, you should even be able to browse to the share.

/Hans


>> On Mon, 9 Feb 2009 20:03:01 -0800, Chris <>
>> wrote:
>>
>> >Hal & Dave, I appreciate your replies!
>> >
>> >I think my issue is that I don’t have a proper UNC for the share. Because
>> >the D-Link hangs off the network it is not a server share. I have tried
>> >\\server\DLink_IP\share but it is not valid, only \\DLink_IP\share works
>> >(works = creates the folder for the link, but that folder cannot be accessed)
>> >.
>> >
>> >Would this hardware configuration prevent a valid UNC?
>> >
>> >Cheers,
>> >Chris
>> >
>> >
>> >"DaveMills" wrote:
>> >
>> >> On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:
>> >>
>> >> >As far as I know, you cannot setup a DFS between devices and a Windows Server.
>> >> >You need to have Windows server in BOTH ENDS.
>> >> >
>> >> Not true:
>> >>
>> >> From
>> >> http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
>> >> (who creates these URLs?)
>> >> Link targets can be shared folders served by other protocols, such as NetWare
>> >> Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
>> >> client computers must have the appropriate redirector installed to access those
>> >> link targets.
>> >>
>> >>
>> >> >Thus You need to connect the device to a Windows Server and then sync that server to another Server.
>> >> >
>> >> >You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
>> >> >replication.
>> >> >
>> >> >Chris wrote:
>> >> >> This is my first experience with DFS and am working with a Windows 2003 domain.
>> >> >>
>> >> >> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
>> >> >> DNS323). The DNS323 is attached to the network switch.
>> >> >>
>> >> >> I got so far as to create the root and link.
>> >> >>
>> >> >> When I created the link to the enclosure and the wizard requests the UNC
>> >> >> path to the target, the enclosure does not appear through the 'browse'
>> >> >> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
>> >> >> appears in the DFS console and when clicked, opens the proper target folder.
>> >> >>
>> >> >> I can browse with Windows Explorer to the folder that is created when the
>> >> >> root is created (is this the namespace?), but when I try to open that folder
>> >> >> I get a 'Not accessible' error.
>> >> >>
>> >> >> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
>> >> >> Does the target share have to be physically attached to the server, as mine
>> >> >> is not?
>> >> In essence if the client can access \\server\share then it should be able to
>> >> access \\dfs\root\linkname --> \\server\share provided it supports DFS
>> >> namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
>> >> actual UNC of the target. Then the client uses its redirector to access the
>> >> resolved target just as if the target UNC had been entered in the first place.
>> >> >>
>> >> >> The only way to give the DNS323 a drive letter is to map to it. Mapped
>> >> >> drives cannot be used to create DFS links, correct?
>> >> Yes
>> >>
>> >> >>
>> >> >> Can someone please tell me why this link is not working.
>> >> >> andwhichvitalinformationIleftout
>> >> Nope but start by using the UNC to the share. If that will not work then DFS
>> >> will not work. Think of DFS names as an alias for the real UNC name.
>> >> >>
>> >> >> Thank you,
>> >> >> Chris
>> >> --
>> >> Dave Mills
>> >> There are 10 types of people, those that understand binary and those that don't.
>> >>
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that don't.
>>

On Wed, 11 Feb 2009 05:58:29 +0000 (UTC), (Hans Liss) wrote:

>In article <C23ED915-29E9-41C6-B3CB->,
>Chris <> wrote:
>>Thank you for your time Dave.
>>
>>"DaveMills" wrote:
>>
>>> I have no idea. This groups is focused on DFS and your issue is not DFS at all.
>>> It is the ability to create and then use a share on the D-Link device.
>>
>>
>>I have wondered about this myself.
>>
>>The folder we are trying to share is not on a Windows OS therefore has not
>>been set up as a share would be in Windows. The D-Link is designed to be very
>>sharing but I can't tell how the share would perform in a DFS environment.
>>
>>Also, because the folder we wish to share does not belong to the server, it
>>will not have the permission to share it out. This seems more probably,
>>especially considering the error we get is "Share is not accessible, the
>>network location cannot be reached".
>>
>>I may peruse in the correct forum.
>>
>>Chris
>
>I got the impression from one of your earlier post that you could indeed
>reach the D-Link share using an UNC path built using the IP address of the
>box ("\\10.254.254.41\Volume_1").i
>
>If you can indeed do that but still not use it as a DFS target, then you
>are in the right group.
>
>Anyway, why don't you try setting up correct DNS and WINS entries for the
>D-Link so you can reach it without using the IP address? Maybe the DFS referral
>needs a *name* to work? If nothing else, it will make your UNC paths look less
>messy. And with a WINS entry, you should even be able to browse to the share.
>

All good things to do but the issue is that Chris can access the DFS paths and
create and delete files but not update them. I would be very surprised if this
was a DFS issue so back off of DFS and use the UNC names. Once that works go
flat out for the DFS links to the UNC names.

>/Hans
>
>
>>> On Mon, 9 Feb 2009 20:03:01 -0800, Chris <>
>>> wrote:
>>>
>>> >Hal & Dave, I appreciate your replies!
>>> >
>>> >I think my issue is that I don’t have a proper UNC for the share. Because
>>> >the D-Link hangs off the network it is not a server share. I have tried
>>> >\\server\DLink_IP\share but it is not valid, only \\DLink_IP\share works
>>> >(works = creates the folder for the link, but that folder cannot be accessed)
>>> >.
>>> >
>>> >Would this hardware configuration prevent a valid UNC?
>>> >
>>> >Cheers,
>>> >Chris
>>> >
>>> >
>>> >"DaveMills" wrote:
>>> >
>>> >> On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:
>>> >>
>>> >> >As far as I know, you cannot setup a DFS between devices and a Windows Server.
>>> >> >You need to have Windows server in BOTH ENDS.
>>> >> >
>>> >> Not true:
>>> >>
>>> >> From
>>> >> http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
>>> >> (who creates these URLs?)
>>> >> Link targets can be shared folders served by other protocols, such as NetWare
>>> >> Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
>>> >> client computers must have the appropriate redirector installed to access those
>>> >> link targets.
>>> >>
>>> >>
>>> >> >Thus You need to connect the device to a Windows Server and then sync that server to another Server.
>>> >> >
>>> >> >You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
>>> >> >replication.
>>> >> >
>>> >> >Chris wrote:
>>> >> >> This is my first experience with DFS and am working with a Windows 2003 domain.
>>> >> >>
>>> >> >> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
>>> >> >> DNS323). The DNS323 is attached to the network switch.
>>> >> >>
>>> >> >> I got so far as to create the root and link.
>>> >> >>
>>> >> >> When I created the link to the enclosure and the wizard requests the UNC
>>> >> >> path to the target, the enclosure does not appear through the 'browse'
>>> >> >> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
>>> >> >> appears in the DFS console and when clicked, opens the proper target folder.
>>> >> >>
>>> >> >> I can browse with Windows Explorer to the folder that is created when the
>>> >> >> root is created (is this the namespace?), but when I try to open that folder
>>> >> >> I get a 'Not accessible' error.
>>> >> >>
>>> >> >> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
>>> >> >> Does the target share have to be physically attached to the server, as mine
>>> >> >> is not?
>>> >> In essence if the client can access \\server\share then it should be able to
>>> >> access \\dfs\root\linkname --> \\server\share provided it supports DFS
>>> >> namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
>>> >> actual UNC of the target. Then the client uses its redirector to access the
>>> >> resolved target just as if the target UNC had been entered in the first place.
>>> >> >>
>>> >> >> The only way to give the DNS323 a drive letter is to map to it. Mapped
>>> >> >> drives cannot be used to create DFS links, correct?
>>> >> Yes
>>> >>
>>> >> >>
>>> >> >> Can someone please tell me why this link is not working.
>>> >> >> andwhichvitalinformationIleftout
>>> >> Nope but start by using the UNC to the share. If that will not work then DFS
>>> >> will not work. Think of DFS names as an alias for the real UNC name.
>>> >> >>
>>> >> >> Thank you,
>>> >> >> Chris
>>> >> --
>>> >> Dave Mills
>>> >> There are 10 types of people, those that understand binary and those that don't.
>>> >>
>>> --
>>> Dave Mills
>>> There are 10 types of people, those that understand binary and those that don't.
>>>
>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

In article <>,
DaveMills <> wrote:
>On Wed, 11 Feb 2009 05:58:29 +0000 (UTC), (Hans Liss) wrote:
>
>>In article <C23ED915-29E9-41C6-B3CB->,
>>Chris <> wrote:
>>>Thank you for your time Dave.
>>>
>>>"DaveMills" wrote:
>>>
>>>> I have no idea. This groups is focused on DFS and your issue is not DFS at all.
>>>> It is the ability to create and then use a share on the D-Link device.
>>>
>>>
>>>I have wondered about this myself.
>>>
>>>The folder we are trying to share is not on a Windows OS therefore has not
>>>been set up as a share would be in Windows. The D-Link is designed to be very
>>>sharing but I can't tell how the share would perform in a DFS environment.
>>>
>>>Also, because the folder we wish to share does not belong to the server, it
>>>will not have the permission to share it out. This seems more probably,
>>>especially considering the error we get is "Share is not accessible, the
>>>network location cannot be reached".
>>>
>>>I may peruse in the correct forum.
>>>
>>>Chris
>>
>>I got the impression from one of your earlier post that you could indeed
>>reach the D-Link share using an UNC path built using the IP address of the
>>box ("\\10.254.254.41\Volume_1").i
>>
>>If you can indeed do that but still not use it as a DFS target, then you
>>are in the right group.
>>
>>Anyway, why don't you try setting up correct DNS and WINS entries for the
>>D-Link so you can reach it without using the IP address? Maybe the DFS referral
>>needs a *name* to work? If nothing else, it will make your UNC paths look less
>>messy. And with a WINS entry, you should even be able to browse to the share.
>>
>
>All good things to do but the issue is that Chris can access the DFS paths and
>create and delete files but not update them. I would be very surprised if this
>was a DFS issue so back off of DFS and use the UNC names. Once that works go
>flat out for the DFS links to the UNC names.

The OP never said that he could "access the DFS paths and create and delete
files but not update them". At least not within this thread. Since these NAS
devices are primarily used to share volumes via SMB/CIFS, I didn't expect that
to be an issue.

That said, I just made an empirical test, creating DFS folders pointing to eight
different UNC paths (using eight different kinds of server references) to a
non-Windows NAS device (from Netgear), and they all worked fine. Here is what I
tried (for DNS names I used only the host part unless otherwise stated):
1) IP address - same format as the OP used
2) DNS "A" name in non-AD domain (FQDN)
3) DNS CNAME in non-AD domain (FQDN)
4) DNS "A" name in AD domain
5) DNS "A" name in AD domain + WINS
6) DNS CNAME in AD domain
7) DNS CNAME in AD domain + WINS
8) WINS only

The only weird one was the eighth one, which the DFS Management console protested
could not be reached (and for which the "Site" column specifies "<Unknown>"),
but all eight DFS folders worked fine when accessing them from the address bar in
XP or Vista. The DFS root is on a W2k3 server.

/Hans

>
>>/Hans
>>
>>
>>>> On Mon, 9 Feb 2009 20:03:01 -0800, Chris <>
>>>> wrote:
>>>>
>>>> >Hal & Dave, I appreciate your replies!
>>>> >
>>>> >I think my issue is that I don’t have a proper UNC for the share. Because
>>>> >the D-Link hangs off the network it is not a server share. I have tried
>>>> >\\server\DLink_IP\share but it is not valid, only \\DLink_IP\share works
>>>> >(works = creates the folder for the link, but that folder cannot be accessed)
>>>> >.
>>>> >
>>>> >Would this hardware configuration prevent a valid UNC?
>>>> >
>>>> >Cheers,
>>>> >Chris
>>>> >
>>>> >
>>>> >"DaveMills" wrote:
>>>> >
>>>> >> On Mon, 09 Feb 2009 10:52:47 +0100, HAL07 <> wrote:
>>>> >>
>>>> >> >As far as I know, you cannot setup a DFS between devices and a Windows Server.
>>>> >> >You need to have Windows server in BOTH ENDS.
>>>> >> >
>>>> >> Not true:
>>>> >>
>>>> >> From
>>>> >> http://technet.microsoft.com/en-us/l...r_dfs_how_sdzq
>>>> >> (who creates these URLs?)
>>>> >> Link targets can be shared folders served by other protocols, such as NetWare
>>>> >> Core Protocol (NCP) for NetWare and Network File System (NFS) for UNIX, but
>>>> >> client computers must have the appropriate redirector installed to access those
>>>> >> link targets.
>>>> >>
>>>> >>
>>>> >> >Thus You need to connect the device to a Windows Server and then sync that server to another Server.
>>>> >> >
>>>> >> >You see, the device you try to sync with does not have the DFS service running. It only has SMB which is not sufficient for a DFS
>>>> >> >replication.
>>>> >> >
>>>> >> >Chris wrote:
>>>> >> >> This is my first experience with DFS and am working with a Windows 2003 domain.
>>>> >> >>
>>>> >> >> I am trying to create a DFS link to a network attached HDD enclosure (D-Link
>>>> >> >> DNS323). The DNS323 is attached to the network switch.
>>>> >> >>
>>>> >> >> I got so far as to create the root and link.
>>>> >> >>
>>>> >> >> When I created the link to the enclosure and the wizard requests the UNC
>>>> >> >> path to the target, the enclosure does not appear through the 'browse'
>>>> >> >> button. Instead I entered its IP address, \\10.254.254.41\Volume_1. The link
>>>> >> >> appears in the DFS console and when clicked, opens the proper target folder.
>>>> >> >>
>>>> >> >> I can browse with Windows Explorer to the folder that is created when the
>>>> >> >> root is created (is this the namespace?), but when I try to open that folder
>>>> >> >> I get a 'Not accessible' error.
>>>> >> >>
>>>> >> >> I am unsure if the \\10.254.254.41\Volume_1 path is valid as a DFS target.
>>>> >> >> Does the target share have to be physically attached to the server, as mine
>>>> >> >> is not?
>>>> >> In essence if the client can access \\server\share then it should be able to
>>>> >> access \\dfs\root\linkname --> \\server\share provided it supports DFS
>>>> >> namespaces. i.e. the DFS client is responsible for resolving the DFS name to the
>>>> >> actual UNC of the target. Then the client uses its redirector to access the
>>>> >> resolved target just as if the target UNC had been entered in the first place.
>>>> >> >>
>>>> >> >> The only way to give the DNS323 a drive letter is to map to it. Mapped
>>>> >> >> drives cannot be used to create DFS links, correct?
>>>> >> Yes
>>>> >>
>>>> >> >>
>>>> >> >> Can someone please tell me why this link is not working.
>>>> >> >> andwhichvitalinformationIleftout
>>>> >> Nope but start by using the UNC to the share. If that will not work then DFS
>>>> >> will not work. Think of DFS names as an alias for the real UNC name.
>>>> >> >>
>>>> >> >> Thank you,
>>>> >> >> Chris
>>>> >> --
>>>> >> Dave Mills
>>>> >> There are 10 types of people, those that understand binary and those that don't.
>>>> >>
>>>> --
>>>> Dave Mills
>>>> There are 10 types of people, those that understand binary and those that don't.
>>>>
>>
>--
>Dave Mills
>There are 10 types of people, those that understand binary and those that don't.