Shared folder not being recognised

[willum08]

Hello,
I have just bought a Buffalo Link Station Model LS-CH1.OTL
I am having a problem trying to set it up on my home network  and would really appreciate some help...
The link Station is directly connected to my Router via a  short CAT5 cable.
I'm using Windows 10 Pro.
I Open NAS Navigator2.
Shows LS-CHL66B  on WORKGROUP

I Click on LS-CHL66B Icon and then Menu
Select Map Share
Result : Could Not map the Share. Create a folder named "Share" before mapping the Drive...

I followed the instructions "Launching NAS Navigator 2...
which state.......
Windows
1. Double-click the NAS Navigator2 icon (  ) created on the desktop to start NAS Navigator2.
If you have already launched NAS Navigator2, the icon will appear on the notification area. Right-click the icon and select Open NAS Navigator2.
2.The process is complete once the NAS Navigator2 window is displayed.

3. In the  NAS Navigator window, I click on Menu >Properties> Open Settings> and Log in using Username and Password..
4. In the FolderSetup window there is a folder called "info" I then create a folder called "share"
5. The "share" folder has attributes Read and Write, Recycle Bin and Support -Windows and Volume as Disk1
6. So I close the Folder Setup Window and go back to the NAS Navigator2 screen, and click on Menu > Map Share...
7. Result : Could Not map the Share. Create a folder named "Share" before mapping the Drive... but I have done so.....
8. What can I do Now ??
Thank you for any help......

[davo]

The LS-CH1.OTL is from 2008, so 17 years old. Why anyone would buy a 17 year old device and expect it to work on modern hardware is beyond me.
Basically, Windows 10 requires SMB2 at a minimum to operate, this NAS only has SMB1, there are work arounds but it's a major security risk.

Just buy a newer NAS.

[LesG]

Windows 10 requires SMB2 at a minimum to operate, this NAS only has SMB1

That's the nub of it.Your options on the NAS end are involved (opening it up to SSH and modding the samba config program to allow SMB2) OR you could allow SMB1 on Win10 - that's the "security risk" bit referred to above. Windows deliberately disabled SMB1, with good reason.

I don't know Windows well enough to advise on how to do it but there is probably 'how to' info just a web search away.