SMBv1 and Windows 10 (network attached storage)

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 494
    Win 10 Pro x64 versions
       #11

    I see that now looking back, sorry. So yes, \\D1\Movies should map the Movies folder as a shortcut for you in Explorer.

    I do have one device that refuses to work using the DeviceName so in that case I use the device IP address.
      My Computer


  2. Posts : 72
    Windows 10
    Thread Starter
       #12

    Railtech said:
    I see that now looking back, sorry. So yes, \\D1\Movies should map the Movies folder as a shortcut for you in Explorer.

    I do have one device that refuses to work using the DeviceName so in that case I use the device IP address.
    What if I have multiple folders stored to the Drobo? The first Drobo is for all my misc files and folders. The second Drobo is for my movies and the third is for my PC games. The second and third are currently empty.
      My Computer


  3. Posts : 494
    Win 10 Pro x64 versions
       #13

    You would simply setup a location to each Drobo. On the device create folder such as Data then nest other folders below Data to hold your misc. files and folders. You then map \\D1\Data. You then get access to all the data in the Data folder. Repeat for all devices.
      My Computer


  4. Posts : 72
    Windows 10
    Thread Starter
       #14

    Railtech said:
    You would simply setup a location to each Drobo. On the device create folder such as Data then nest other folders below Data to hold your misc. files and folders. You then map \\D1\Data. You then get access to all the data in the Data folder. Repeat for all devices.
    Thanks again Railtech.
      My Computer


  5. Posts : 494
    Win 10 Pro x64 versions
       #15

    You bet, happy sharing!
      My Computer


  6. Posts : 72
    Windows 10
    Thread Starter
       #16

    Railtech said:
    You bet, happy sharing!
    I was looking at the apps I have installed to the Drobo. Right now there are Drobo Access, MyDrobo, Apache, Locale, MySQL and Python 2.
    Do you think there is an app that I can install to get around the NetBIOS issue?
      My Computer

  7.   My Computers


  8. Posts : 494
    Win 10 Pro x64 versions
       #18

    HarryD,

    I would not use the suggested fix by James Gravert as that fix enables SMB1 on a Windows 10 machine via Group policy which is not recommended as you know due to security concerns.

    I will do some looking about a possible app although I have my doubts.
      My Computer


  9. Posts : 72
    Windows 10
    Thread Starter
       #19

    Railtech said:
    HarryD,

    I would not use the suggested fix by James Gravert as that fix enables SMB1 on a Windows 10 machine via Group policy which is not recommended as you know due to security concerns.

    I will do some looking about a possible app although I have my doubts.
    I've read through his fix and realized that all it does is enable SMBv1. I can do that quite easily but I'm looking for another solution. If the Drobo's rely on SMB but version 1 is disabled on the Drobo, the problem has to lie within Windows.

    - - - Updated - - -

    Maybe I'd be better off looking for a new NAS?

    Synology 4 Bay NAS DiskStation DS418 (Diskless) - Newegg.com
      My Computer


  10. Posts : 494
    Win 10 Pro x64 versions
       #20

    The issue is and always will be how SAMBA (the Linux equivalent of SMB) handles network discovery. Almost all of the NAS devices on the market use a Linux based OS (which uses SAMBA). Manufacturers of these devices simply use whatever version of SAMBA that works with their OS with little concern about how the user interacts with the device.

    For the most part it is expected that users will map drive letters to these NAS devices to have access. Doing that is very similar to using a mapped location. So my question to you is, what about that do you not like?

    Switching to a different NAS brand is no guarantee that your situation will change, in fact, it is likely nothing will change as far as access to the device goes. Reality is that just because you cannot see these devices in Explorer does not mean that they do not or will not function, it only means that the user needs to adapt to a new way of working with the devices. As I said before, the most effective way I have found is the mapped location method. I do not use mapped drive letters as I find them to be unreliable for my purposes. I run multiple machines on my LAN that require access to my NAS devices so having access via mapped location allows for that where a mapped drive letter does not.

    You can force an NAS device to appear in the traditional way, showing under Network in the Navigation column of Explorer by selecting Network and then typing the path in the address field in Explorer. Example below:

    SMBv1 and Windows 10 (network attached storage)-network-path.png

    The above example should work for your Drobo the same way. The Synology device you link to would also be the same way.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:25.
Find Us




Windows 10 Forums