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)

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.

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.

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?

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.

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

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

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.