Link to home
Create AccountLog in
Windows OS

Windows OS

--

Questions

--

Followers

Top Experts

Avatar of Mike Caldwell
Mike Caldwell🇺🇸

Cannot connect to Terastation NAS from Windows 10
I have had a Terastation NAS working for nearly ten years.  I used it daily for backup of the D: drive data files and True Image weekly images.  The drive is currently 40% full.  LAN lights blink on the unit and on the switch it is connected to.  My PC is connected to a rounter, then to an access point downstairs, then through a switch to the NAS.   It has always been listed under Windows 10 network locations, now Windows says it cannot connect, suggesting the name is wrong and other useless suggestions.  However my IP mapper finds it (10.0.0.20), I can ping it, and I can log into the Buffalo GUI using the IP address.  But windows does not find it and my daily data backup system does not either; it appears it has been this way since February.  I have restarted the NAS, the switch, the access point, and the router; no change.

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


ASKER CERTIFIED SOLUTION
Avatar of QlemoQlemo🇩🇪

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

What I am seeing is lots of ways to disable SMBv1, not enable it.  Maybe point to a more specific place in the link for me to follow.  I want to recover this data, so if I can get connectivity restored, I'll get a spanking new NAS and move the data over, then say goodby to the Terastation.  But first I gotta get access so I can move the history out.

SOLUTION
Avatar of McKnifeMcKnife🇩🇪

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.

Avatar of QlemoQlemo🇩🇪

The screenshots are showing the GUI way to check and change whether SMBv1 is active. Or use elevated PowerShell: Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol to switch the feature on.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

What is 1709?  Your suggestions are beyond my technical expertise.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of JohnJohn🇨🇦

Follow this Microsoft Article for a discussion on SMBv1

https://support.microsoft.com/en-ca/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709

That points to this Microsoft Article that shows how to enable SMBv1

https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

The article I posted above for completeness is exactly the same article as Qlemo posted.

You asked for a pointer to the correct section in the article and it is here.

Enable: Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol

Along with others, I do not recommend you enable SMBv1

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Please comment on a Plan B:  get a WD MyCLoud NAS and transfer my files from the Terastation to the new unit via USB.

Avatar of JohnJohn🇨🇦

Do you have an older machine you can connect the NAS to?

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of McKnifeMcKnife🇩🇪

Plan B should wait.
Mike, you would know if you reinstalled windows, lately? Because if you have not, then there is no reason to believe it has anything to do with the presence of SMBv1. If in doubt, just click on start, type powershell, right click the result and select "run as administrator". Then run Qlemo's command "Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol" and see if that changes anything. If not, proceed with my suggestion and test whether the port is open or not, To do that, use the smae powershell and launch telnet. it might not be installed, so install it, first.: on the start menu, type appwiz.cpL and start it. Turn to "add or remove windows features". Then select "telnet client" and now launch
telnet IPAddressofNAS 445

What is the result?

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Did as instructed, but got this error message:

PS C:\WINDOWS\system32> Enable- WindowsOPtionalFeature -Online -FeatureName SMB1Protocol
Enable- : The term 'Enable-' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

So tried without the dash; no different.  So then took off the Enable- altogether and ran the rest, with this result:
PS C:\WINDOWS\system32> WindowsOPtionalFeature -Online -FeatureName SMB1Protocol


FeatureName      : SMB1Protocol
DisplayName      : SMB 1.0/CIFS File Sharing Support
Description      : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.
RestartRequired  : Possible
State            : Disabled
CustomProperties :
                   ServerComponent\Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer
                   Browser protocol.
                   ServerComponent\DisplayName : SMB 1.0/CIFS File Sharing Support
                   ServerComponent\Id : 487
                   ServerComponent\Type : Feature
                   ServerComponent\UniqueName : FS-SMB1
                   ServerComponent\Deploys\Update\Name : SMB1Protocol

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

BTW: I do have another machine on the LAN that I am not using but could.  It runs Ubuntu 16.04.  I assume I could transfer the files from the NAS to this machine, then back to a new NAS when I get it.  But my son set it up, I know almost nothing about Linux but I can type what I am told!  Sounds like a quick fix if I could get some hand holding for that.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of QlemoQlemo🇩🇪

The correct line has been posted twice, McKnife added a blank into it which doesn't belong there ;-)
Enable-WindowsOPtionalFeature -Online -FeatureName SMB1Protocol

Open in new window

From what you posted, the feature is disabled, and enabling (maybe requiring reboot) will help.

Using Linux is only working if you know what to do. I cannot recommend that, it intoduces more issues for you. Unless you leave it to your son to copy over ...

Avatar of McKnifeMcKnife🇩🇪

I added a blank? Sorry, for copy pasting your code, Qlemo. There is no blank there, not in yours nor in mine.

Avatar of QlemoQlemo🇩🇪

Correct, McKnife, it just looks that way, because of line wrapping in the browser - see what Mike used ...

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Here is what came back:

PS C:\WINDOWS\system32> Enable-WindowsOPtionalFeature -Online -FeatureName SMB1Protocol
Do you want to restart the computer to complete this operation now?
[Y] Yes  [N] No  [?] Help (default is "Y"):

What does this tell me?  However, I used another machine on the LAN, which runs Ubuntu 16.04, and it could see the folders, etc, so copied them all over.  Two big ones are still running, but clearly this is working.  Now I'll get a new NAS and copy them back.  But would like to know if the Terastation could be fixed so that I don't have to junk it.  I have never updated the firmware, so maybe I should try that first.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Oh; Ubuntu has a GUI, so I didn't have to type any Linux stuff.

Avatar of JohnJohn🇨🇦

It is most likely the SMBv1 issue causing the situation on the Windows machines.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of QlemoQlemo🇩🇪

Very very likely SMBv1 is the issue, and there will not be any other way to allow accessing from W10 as to enable the feature.
The prompt you got above told you that the feature has been enabled successfully, but you need to reboot your W10 machine to apply the change for real. After that, you should be able to use the (insecure) SMBv1 protocol to access your Terastation without any more issues.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Thanks to all.

Avatar of McKnifeMcKnife🇩🇪

Please indicate if it worked after rebooting.

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Oh; yes.  When I first looked in the Windows Features the "Automatice removal" was checked.   Unchecked it; fail.  So checked them all and restarted and works fine now.

I asked Buffalo for firmware that provides SMBv2.  They said that at 12 years old they no longer provided support.  I said all I wanted was the firmware and the sent me to a link.  There is only one firmware update, it is a few years old so do not know if it will make a difference or not.  But now that I have the data on the Ubuntu machine I'll working on getting it into the HOMEGROUP so I can just use it as my backup machine.  It is nearly new with 20TB of storage; the Terastation is 2TB of RAID5 and 12 years old, so want to just go to the new machine.  What I am storing is my daily backup of WIndows applications data.  It is set to never delete if I delete on the source machine.  But if that drive failed it would not be a tragedy; I would still have the source.  Plus I constantly put a third copy on Carbonite.  My business is patent law so goosey about ever losing something forever.

Avatar of McKnifeMcKnife🇩🇪

Ok, great, then please close the question now.

Avatar of QlemoQlemo🇩🇪

Remember to switch off the feature again as soon as you do not need access to the NAS anymore.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Thought I did close it.

Avatar of McKnifeMcKnife🇩🇪

Mike select helpful comments as answers - that's how you close it.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Answers seemed to stop, and there was no real solution.  I was able to get a shared folder defined, but cannot put anything into it from either the client Windows machine or directly on the Ubuntu machine.  Like an empty read only device that cannot be written to.  I appreciate the efforts, but they went nowhere.  Would be great to get to a conclusion, but nothing useful here.  Did I just quit too soon?

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of McKnifeMcKnife🇩🇪

You did not indicate where you wanted things to go. Your last comment did not show what you still wanted to solve - it's not that answering stopped. if you want to come back to this, feel free and define your goals. I will not be able to help you with linux stuff, though.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

I want to be able to use my Ubuntu 16.04 based machine as a Plex Media Server, including downloading media, and also access it from my Windows 10 PC to use it as a NAS to save my daily Windows 10 data files.  "Use" would include accessing the machine using Real VNC or Team Viewer to operate it without having to go to the garage.  Right now it cannot be used in any way; I have defined a shared volume, but I cannot put anything into it, either from my Windows machine remotely nor standing in front of the Ubuntu machine with a mouse and keyboard.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Anything?

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of McKnifeMcKnife🇩🇪

Mike, your initial question was solved as you confirmed that you have access after enabling smbv1. Your follow up question should be re-asked in a separate question, I suggest. This one should be closed by you, finally.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Maybe I did not state the issue correctly.  Yes I created a shared volume, or at least I have an icon for it, but cannot access the machine in any way.  My goal was to be able to use RealVNC or any similar remote program to operate the machine in the garage remotely.  Getting the icon did not get me there.

Avatar of QlemoQlemo🇩🇪

We have solved the original problem with your Buffalo NAS.
Now you switched over to asking for Ubuntu instructions. There is no relation technically. Please ask as a new question with proper topics so the appropriate experts can find it.

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

Just reviewed, and agree the question morphed when the notion of SMBv1 was introduced.  I'll award points for information about the original question.  I have moved from CA to NC and now have a completely different setup physically and electronically; I'll see if I still have an issue doing remote into the Ubuntu machine.

Avatar of Mike CaldwellMike Caldwell🇺🇸

ASKER

I don't use EE often enough to know how to navigate.  I hope I have awarded points; if not please contact me and hold my hand!
Windows OS

Windows OS

--

Questions

--

Followers

Top Experts

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.