DFS link to a network attached HDD enclosure

Discussion in 'File Systems' started by Chris, Feb 8, 2009.

  1. Chris

    Chris Guest

    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
    Chris, Feb 8, 2009
    #1
    1. Advertising

  2. Chris

    HAL07 Guest

    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
    HAL07, Feb 9, 2009
    #2
    1. Advertising

  3. Chris

    DaveMills Guest

    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/library/cc782417.aspx#w2k3tr_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.
    DaveMills, Feb 9, 2009
    #3
  4. Chris

    Chris Guest

    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/library/cc782417.aspx#w2k3tr_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.
    >
    Chris, Feb 10, 2009
    #4
  5. Chris

    DaveMills Guest

    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/library/cc782417.aspx#w2k3tr_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, Feb 10, 2009
    #5
  6. Chris

    HAL07 Guest

    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/library/cc782417.aspx#w2k3tr_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
    HAL07, Feb 10, 2009
    #6
  7. Chris

    Chris Guest

    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/library/cc782417.aspx#w2k3tr_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.
    >
    Chris, Feb 10, 2009
    #7
  8. Chris

    Hans Liss Guest

    In article <>,
    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/library/cc782417.aspx#w2k3tr_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.
    >>
    Hans Liss, Feb 11, 2009
    #8
  9. Chris

    DaveMills Guest

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

    >In article <>,
    >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/library/cc782417.aspx#w2k3tr_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.
    DaveMills, Feb 11, 2009
    #9
  10. Chris

    Hans Liss Guest

    In article <>,
    DaveMills <> wrote:
    >On Wed, 11 Feb 2009 05:58:29 +0000 (UTC), (Hans Liss) wrote:
    >
    >>In article <>,
    >>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/library/cc782417.aspx#w2k3tr_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.
    Hans Liss, Feb 12, 2009
    #10
  11. Chris

    DaveMills Guest

    On Thu, 12 Feb 2009 08:21:54 +0000 (UTC), (Hans Liss) wrote:

    >In article <>,
    >DaveMills <> wrote:
    >>On Wed, 11 Feb 2009 05:58:29 +0000 (UTC), (Hans Liss) wrote:
    >>
    >>>In article <>,
    >>>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.


    You are correct I misread Chris' 2 post. Upon re-reading it look like Chris is
    saying he can create the link but not open it. I took it that he meant he could
    not open the link target but that is not exactly what he said.

    So to test this out Chris, can you open \\D-Link IP\Share and use it normally in
    Explorer. If so the issue is not with the D-Link but with DFS.
    The DFS Root contains folders (physical ones). So if your DFS root on the DFS
    Server is "C:\DFSRoot" then when you add a link and target a link folder is
    created and changed to a reparse point that redirects to the target UNC. Say
    this is a folder/reparse point called "Data", you will see on the DFS server
    C:\DFSRoot\Data. You cannot open "Data" using the local path "C:\DFSRoot\Data"
    as it is not a folder but a reparse point. When you access the DFS path as
    "\\Domain\DFSRoot\Data" the reparse point redirects to \\D-Link\Target.

    Now looking at permissions, There are 3 sets of permissions involved for "Data"
    1) the Share permissions on "\\D-Link IP\Target"
    2) the NTFS permissions on the folder that is shared as "\\D-Link IP\Target"
    3) The NTFS permissions on the reparse point "C:\DFSRoot\Data"

    Since you can use "\\D-Link\Target" without issue 1) and 2) must be OK. However
    the NTFS permissions on 3) may be "Administrator=F/C" but "Users=NoAccess" (or
    any other permissions). For the DFS path to work these permission, on the
    reparse point, must allow the user to actually read the reparse point in order
    to determine where the link target is. This is also true of the whole tree of
    folders and reparse points in "C:\DFSRoot". On the DFS server chock the local
    NTFS permission on the whole DFSRoot folder.

    I have on one occasion seen this set up with two DFS servers where serverA had
    permission on "C:\DFSRoot" as Everyone=F/C and on the other replica DFS Server
    the permissions were something like "Admin=F/S" + "Users=Read". The effect was
    that the actual permissions changed for the path \\Domain\DFSRoot" depending
    upon which DFS server was used to resolve the "\\Domain\DFSRoot\Data" path.


    >
    >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/library/cc782417.aspx#w2k3tr_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.

    >

    --
    Dave Mills
    There are 10 types of people, those that understand binary and those that don't.
    DaveMills, Feb 13, 2009
    #11
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Tony97103

    external HDD enclosure probs

    Tony97103, Mar 2, 2008, in forum: Windows Vista Hardware
    Replies:
    14
    Views:
    357
  2. Eric_Twilly

    Windows explorer crashes when i access my usb attached hdd

    Eric_Twilly, Sep 26, 2007, in forum: Windows Vista General Discussion
    Replies:
    6
    Views:
    165
    MICHAEL
    Sep 28, 2007
  3. txt3rob

    PC stays on with usb hdd attached

    txt3rob, Mar 27, 2009, in forum: Windows Vista Hardware
    Replies:
    0
    Views:
    199
    txt3rob
    Mar 27, 2009
  4. don treat

    external hdd enclosure problem

    don treat, Oct 11, 2009, in forum: Windows Vista Hardware
    Replies:
    7
    Views:
    609
    treatddt
    Oct 11, 2009
  5. Adam Sudol
    Replies:
    4
    Views:
    1,972
    Dan Lovinger [MSFT]
    Jul 6, 2004
Loading...

Share This Page