SMBv1 and Windows 10 (network attached storage)

Page 1 of 4 123 ... LastLast

  1. Posts : 72
    Windows 10
       #1

    SMBv1 and Windows 10 (network attached storage)


    I have a couple Drobo 5N's attached to a switch and then to my network.
    I can't see them in Network but I can see them in Drobo Dashboard.

    I know you can enable SMBv1 in Windows 10. It's only when it's enabled in Windows 10 is when I can see and use them.

    SMBv1 is disabled in all of the Drobo's.

    Is there a setting in the switch (Netgear GS108Ev3) or the modem/router (Netgear C6230) that I'm missing?

    Windows 10 Version 21H1 (OS Build 19043.844)
    Attached Thumbnails Attached Thumbnails SMBv1 and Windows 10 (network attached storage)-drobo.png  
      My Computer


  2. Posts : 16,932
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #2

    Harry,

    You say that SMB1 is disabled in your Drobos and you show the dialog in which you disabled it. Surely you could simply just enable it.

    Denis
      My Computer


  3. Posts : 72
    Windows 10
    Thread Starter
       #3

    Try3 said:
    Harry,

    You say that SMB1 is disabled in your Drobos and you show the dialog in which you disabled it. Surely you could simply just enable it.

    Denis
    If I enable it in Drobo dashboard it still doesn't show in Windows. The latest firmware for the Drobo's (which I have) gives you the option to disable it because of security concerns.
      My Computer


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

    There are no settings that will change this behavior. The problem is within Network Discovery. Devices like the Drobo use NetBIOS as a discovery method. NetBIOS relies on SMB1 and that is the problem.

    My advice is to create a Network Location for your Drobo's in Windows File Explorer. You will find the ability to do that by selecting This PC then click on the Computer tab. The Add network location will create a shortcut to your devices and place them under This PC in Explorer giving you access. I have found this to be the only successful way to have solid access to Linux based devices. If SAMBA which is used by Linux ever gets beyond NetBIOS discovery this problem will end. Until then adding a network location for these devices is the best workaround.
      My Computer


  5. Posts : 16,932
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #5

    HarryD said:
    If I enable it in Drobo dashboard it still doesn't show in Windows. The latest firmware for the Drobo's (which I have) gives you the option to disable it because of security concerns.
    Harry,

    But I thought you said that you could see them if you enabled SMB1 in Windows.

    Denis
      My Computer


  6. Posts : 72
    Windows 10
    Thread Starter
       #6

    Try3 said:
    Harry,

    But I thought you said that you could see them if you enabled SMB1 in Windows.

    Denis
    Only if SMBv1 in enabled in Windows, not the Drobo.
    Railtech seems to be on to something. I'll play around with Network location.

    - - - Updated - - -

    Railtech said:
    There are no settings that will change this behavior. The problem is within Network Discovery. Devices like the Drobo use NetBIOS as a discovery method. NetBIOS relies on SMB1 and that is the problem.

    My advice is to create a Network Location for your Drobo's in Windows File Explorer. You will find the ability to do that by selecting This PC then click on the Computer tab. The Add network location will create a shortcut to your devices and place them under This PC in Explorer giving you access. I have found this to be the only successful way to have solid access to Linux based devices. If SAMBA which is used by Linux ever gets beyond NetBIOS discovery this problem will end. Until then adding a network location for these devices is the best workaround.
    Thank you.
    Will I need to set a static IP in each of the Drobo's?
      My Computer


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

    No, static IP is not necessary, I use DHCP.

    You can use either device name or IP address when setting the path to your devices.

    Examples:

    \\DeviceName\Sharename

    or

    \\IPaddress\Sharename

    Note that the slashes are back slashes not forward. Getting these confused is the most common mistake made by users in setting this up.
      My Computer


  8. Posts : 72
    Windows 10
    Thread Starter
       #8

    Railtech said:
    No, static IP is not necessary, I use DHCP.

    You can use either device name or IP address when setting the path to your devices.

    Examples:

    \\DeviceName\Sharename

    or

    \\IPaddress\Sharename

    Note that the slashes are back slashes not forward. Getting these confused is the most common mistake made by users in setting this up.
    so like this:
    \\D1\Movies
      My Computer


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

    That is the concept yes. You can find the device name in the dashboard under network settings, probably something like Drobo5N for example.
      My Computer


  10. Posts : 72
    Windows 10
    Thread Starter
       #10

    Railtech said:
    That is the concept yes. You can find the device name in the dashboard under network settings, probably something like Drobo5N for example.
    I renamed the Drobo's some time ago when I had them setup in Windows 7.
      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 11:07.
Find Us




Windows 10 Forums