How to fix Buffalo Linkstation LIVE NAS SMB File Sharing in Windows (Could not map share)

[@stickyvicar]

In 2023 this still worked a treat from a Windows 11 laptop. I had to install Java for the ACP Commander to work. Once done I had to remove Access Restrictions off my folders via the User Interface which is still slow as I couldn't get the laptop past the authentication popup. That could be a domain or workgroup issue. This is a fantastic fix, not sure how secure it is but it allows me to access my files. Thanks Simon.

[@fredsmith9380]

I used this patch several years ago on my LS-XLF83 with good results. Recently Buffalo released updated firmware (1.75) to fix a bug. You would think they would add this patch too, but I guess they are more interested in selling new drives than supporting their product. Anyway, I reapplied the patch and everything is good.

[@danielbeecher]

What a great solution - thank you for sharing - you deserve a medal - device saved! Not so much to Buffalo. SMB1 has been defunct for at least 5 years now, it's incredible that Buffalo haven't included this fix in their firmware releases for their LS series LinkStations. As recently as December 2020 Buffalo released a new firmware update (version 1.75). It claims to be compatible with Windows 10, but the firmware STILL does not enable SMB2! It's an insult to injury to now see how easy it would have been for them to include SMB2 to make their device usable. I'll NEVER EVER again buy anything from Buffalo.

[@pr0d1gyvisions74]

Yea, glad I ran into this very quickly so I can return this crappy device. Never again am I wasting money on this Buffalo crap.

[@CRSolarice]

Absolute excellence. I wasn't even planning on attacking this job today or any time in the near future and now its wiped out. I haven't been this impressed since I put DOS on my Altair 8800; You deserve a Nobel Prize for this.

[@unholyarmyofone]

Thank you Simon, this was a very easy to follow video that has solved my NAS problem. The disappointing news from 2021 is that the latest firmware update 1.75 still does not solve the issue, presumably because Buffalo want you to buy their latest box.

[@malcolmelliott1876]

Wonderful.... 3 days of trying to find why one PC would not see the NAS when others could... also learned a lot of other bits as well THANK YOU!

[@mikeb8605]

Hi Simon, stumbled upon this tutorial by accident. After some checking, I still had SMB v1 running, so disabled that and followed your excellent guidance. NAS fully accessible, but hopefully in a slightly more secure fashion. Many thanks.

[@TaiihoKIM]

My machine is Buffalo LinkStation Pro Duo (LS-WVL/E-AP) NAS firmware 1.74 Thank you so much. It's very easy to follow and Doesn't need to learn vi.

[@ronnyakarob]

You sir are a legend! We've had so many issues with Buffalo NAS drives supplied to people over the last few years. Some newer NAS's have the enable SMB2 option, but your video helped me find it! and the older ones work following this :D

[@nigelcarey]

Thank you very much for this tutorial. I was ready to bin an old LinkStation but this patch has given it a new lease of life.

[@dariodmaster]

just update to 4.50 firmware from Buffalo. all works on my linkstation now

[@olivermoritz8906]

OMG Simon I am completely IT illiterate but was able to follow your instructions and get Windows access to my NAS folders {I did have to change the port number to 22 on the WinSCP login page}. Thank you.

[@rayfielding4340]

Outstanding, picked up a Buffalo with no experience of NAS really so was a dipping toe in water, followed your tutorial to the letter and problem solved with an insight into the NAS. Thank You

[@melissacolthurst3598]

Thanks very much for simple and easy to use instructions. I upgraded the firmware from 1.74 to 1.75 and it lost the patch so would not work with Windows 10. This is much easier than using putty and vi. Much appreciated.

[@geoffwhite1920]

Absolute legend. I've just done this and gained access to my NAS. FYI Buffalo have basically said that due to SMB1 be withdrawn by MS all of the old NAS drives that use this are now obsolete so buy a new one. This is why this video is so important.

[@CRSolarice]

I've really left some scorching remarks on Buffalo's website, ever since the very beginning! Now I'm starting to realize that it isn't because of my bitchy personality set, either. They have it coming. Buffalo, Inc. is chock full of a55h0les. You can bet I've stored this video and added every step to my notes (I thought this would be a dillemma to fix and this fellow pulls it through in seconds, like it was in his DNA at birth. Another demonstration of Britains finest minds (even as rare as they are becoming). Zoiks! And away!!!!

[@davidfletcher682]

Thanks for this just what I needed. Enabled smb 1. Copied my files and removed smb 1. Will try methods 2 later.

[@mauriziosaccani4938]

Great video Simon! Thanks to You I was able to solve the problem. Just a note: ACP Commander refused to connect to my Buffalo LinkStation on Windows 10 (IP address case was greyed out). I had to install a Windows 7 VM and from there everything worked liked a charm. Kudos to You and nothing for Buffalo that doesn't offer support anymore. I will rethink buying their products in the future.

[@thebeerg0d]

I join the other people in the comments . Excellent tutorial ! I stumble upon on your video looking by chance. I was looking for how to rip open my now useless buffalo ls-xl NAS, to use the drive elesewhere. This simple software hack gave a second life to my device . Big thanks for this :)

[@JudexDirus]

Absolutely Brilliant! I was already on the web looking for a new NAS..... You just saved me $300 ...... Well Done !!!

[@simonbenney5845]

SMB1 fix worked perfectly. Extracted the files I needed from an old linkstation then turned SMB1 off again. THANKS 👍

[@reynaldogonzaga6084]

great vid as always. After following your video on how to install a new drive, stumbled into this issue. Thanks for the very clear instructions.

[@weskeener1725]

This was super helpful. I SSH'd via WSL into the Linkstation. I was able to edit the smb.sh file using vi, which was scary, but educational. I'm a lazy nano user. Again, thanks for the walk-through.

[@pbelieve]

Brilliant, thank you very much for this, I actually have a terastation (same interface and firmware) but could not enable ssh so I had to use telnet in case anyone has the same issues: Java -jar acp_commander.jar -t NAS_IP -pw Youradminpassword -o (the -o enables telnet and blanks the root password) then i could telnet to NAS_IP using root and no pass vi /etc/init.d/smb.sh add ""/bin/sed -i '3i\\ max protocol = SMB2\\' /etc/samba/smb.conf" to the correct place as per Simons instruction save/write the file reboot terastation all working thanks very much again, great info

[@midiman5045]

Great tip. I just got it working on my LS-WVL/E. Thanks so much. The model is for others who might want to know if it will work on that one.

[@tylerdoop]

THANK YOU!!! All I had to do was go into advanced settings, click on the little grey square looking icon on the right and then turn on SMB2. SO EASY YET SO DIFFICULT

[@vwmullen]

Thanks this worked for me too, and no kidding they really buried that setting! Click the little grey square icon, click "edit", then enable SMB2. Buffalo LS220DE

[@simontickell8005]

You my friend are a star - just updated the drive after doing this previously and it dumped the share - back up and running again!

[@eckhardtmeise4885]

Thank you very much! My Linkstation works again under WIN 10 with SMB2!!!! Very helpfull tutorial!

[@alessiolorenzocasini4041]

Thanks for the video also by me. Now my NAS LinkStation LS-WXL909 works perfectly with my new computer MS Windows 10. Thank You very much.

[@iancooper530]

I originally used the SMB 1.0 work around after watching several other KZbin videos but glad I found your tutorial. Another professional job. Cheers Ian

[@MrExdeo]

Fix just applied to my LS-XHL (Firmware 1.74), a huge thank you for detailing such thoroughly this process.

[@P4DKK]

Thank you Simon, worked first time on my Buffalo Pro due to changing to Windows10 from Windows7

[@stefansommerhofer4314]

You are a legend! Thank You so much for the easy to understand tutorial, the access to the NAS is working again now!

[@andytoth]

Thanks Simon, I got a new computer and thank god your tutorial is still here! (I don't want to update my NAS unless necessary obviously!)

[@andytoth]

(Lol my smb config file was good I was just not in the Workgroup that I specified Ten years ago, but this helped bring back memories!) Thanks again!

[@andytoth]

(Lol my smb config file was good I was just not in the Workgroup that I specified Ten years ago, but this helped bring back memories!) Thanks again!

[@westcountryninja]

Simon sir, you are a king among men. I salute you and thank-you for this excellent solution. Maximum Kudos!

[@keithpellowe]

Brilliant. Thanks for that. I was almost giving up on my nas and you have helped me out. Thanks again.

[@carstenw.6023]

thank you so much for sharing your workflow with us. it worked perfectly!

[@rolandsnel5960]

Hero! Thanks for a simple tutorial getting my LS-QVL working again!

[@tyshewmake67]

Fantastic. My buffalo was 2 minutes from the trash can. You saved it.

[@iberntz]

This worked perfectly on my LS-WVL/E. Many thanks!

[@scottloeppky4517]

You are a legend, as if this still is necessary but yet still works! Thank you! Now able to record from my tv box :)

[@courtneywalsh5486]

Very impressive! Thorough directions and successful fix for Buffalo. Thank you!

[@802106139]

Thank you so much, just worked for me on an old Terastation and i'm using windows 11 23H2

[@oliverreidy8864]

Absolutely a medal - a Gold one ! I have a bunch of these nas systems and was considering dumping them due to that issue with windows. Might get some more life out of them yet!

[@jacquelinepinckers6622]

Hi Simon, again marvelous tutorial! I'm now able to acces the share with my Ipad with iOS 13. Many thanks!

[@thomsenbodo1920]

Hi Simon worked perfect with my LS-WXL. Great video, all steps are well described. thanks

[@pbh]

Worked brilliantly - many thanks!! (LS-WVL, version 1.75)

[@Mac-UK]

Old school never fails! Thanks :)

[@antoniocoppolabove2744]

Great tutorial! Finally I could solve a problem since long time annoying me! Thanks a lot!

[@dinospatoulas7592]

Any idea where to get the ACP commander GUI exe? the link does not work and can't seem to find it anywhere?

[@elfenixnight]

didn't need the complicated fix but did have to enable smb 2 so thank you for the suggestion!

[@BrainHurricanes]

For some of you wondering where the link to ACP commander is in the desription: gry.ch/Java/styled/ Correct me if I'm wrong Simon. Thanks for your tutorial! Edit: worked like a charm! Only thing I wonder is how you get the NAS to show up in windows explorer (network) ? I can only access the NAS by using NAS navigator2 and then browse. Thanks.

[@MsSexpanther123]

that link is dead

[@MsSexpanther123]

advanxer.com/blog/2013/02/buffalo-linkstation-acp-commander-gui/ The link on this page is also dead, but the direct download for the exe on the bottom of the page worked for me

[@michaelmansfield6804]

Thanks for the video, this solution fixed the issue on an 10 year old Buffalo Linkstation RX.

[@time4thetruth305]

You ARE DA Man! Many thanks Indeed for this info. 🙂

[@anandchandrasekar]

Excellent. Thanks for sharing this. this made it so much easier for me.

[@hansklug2240]

Thanks for sharing - this helped me perfectly to solve a long standing problem!

[@KimboG77]

Worked great! Thanks for your easy to understand and follow tutorial

[@droosens]

Superb tutorial, worked like a charm. Thank you Simon.

[@elliej2b654]

Thanks so much! Works a treat.

[@Beercules48]

Thank you so much - worked perfectly! Great work, much appreciated! 🙌🙌

[@iancooper530]

Unfortunately I had to roll back the Samba upgrade as it wasn't stable. Whilst it worked initially I was constantly losing connectivity with my Buffalo NAS drives. I have Windows 10pro. Interestingly though my new WD NAS drive, which runs SMB v3, works absolutely fine and never gets disconnected.

[@ordu01]

Definitive Lifesaver with my issue. You're champ. Thanks!

[@PeterLunn1of1]

Thanks, just got hold of a TeraStation TS-XL and this worked great

[@marcusl.gronemann5295]

Thanks simon you just saved my old Buffalo NAS

[@juldominjon]

c'est super !! "formidable" even a "frog" can succeed, little trick type "root" instead of user name in SCP, unless no file seen :) Simon you saved my LS-WVL "merci" !!

[@kevinsmith4776]

Hi Simon Thank you very much; I have a 12Tb NAS that I thought was only fit for the BIN. Buffalo are not going to fix this issue and want you to buy a new drive. “Most older Buffalo NAS devices do not support SMB version 2 or above. Currently there is no plan to update these older NAS devices to add support for newer SMB versions” If it just a line of code in the config file surely it can be included in a firmware update? Next time I need a NAS, I will be looking at other manufactures. Thanks again worked a treat.

[@SimonHayter]

You will find that all NAS manufacturers have END-OF-LINE support for their products. So it doesn't matter if its Netgear, Cisco, Buffalo or G-Tech, you will face the same problems at somewhere down the line. My advice is to make your own NAS using PC with ITX mobo and Linux using a Raid 1 (Mirror). Doing so will allow you to update the software and the hardware without losing data. So while I'm happy it worked for you! just know some point you will need to replace that NAS, and chances are it'll have less sell value, so I always say better sooner than later.

[@klenzgaming]

worked like a champ. thanks for putting this video out Simon.. much appreciated!

[@DEvilParsnip]

YOU ARE A LEGEND .... thank you very much, didn't know what was going on !!!

[@mariodinis5820]

Excellent mate! thank you for this tutorial!

[@RonDollete]

I don't know why but my LinkStation LS220D had problems doing any sort of SSH/SCP related file transfer. I ended up using the acp-commander's -o option which opened telnet.

[@kwame6683]

Thanks a lot dude. You saved my pictures and files.

[@martinlowe1457]

Hi Simon - I can't see the settings when logging into the NAS using WinSCP at the 4:55 mark

[@vinylimpressions]

When I try to login using Winscp, it just says 403 Forbidden.

[@philipfrkovic1486]

awesome tip, worked first time on my Buffalo Terastation

[@ich07071986]

Thanks a lot for this guide through! Worked perfectly.

[@okdokd3385]

Hello Simon, first off, thank you very much. Will the change of SMB v1 to SMB v2 take place on the NAS or Windows features? will I be required to switch on SMB 1 in windows feature when I need to use NAS?

[@gezabela]

this unfortunately is not working on my LS-CHL-V2 ... after restart i see that the config file is properly modified by the init.d script, bu still it haven't enable smb2. I am not a linux guy, how can i figure out whether the distro on the box is supporting smb2 or not?

[@gezabela]

i take it back! it works in certain win10 machines... but smb1 were definitly not enabled on them, so it must kick-in the smb2

[@davidlemap810]

This looks like it could fix my Linkstation Win10 access problem, but I cannot make out all the details of where to find the smb.sh file. I am using WinSCP to look at the NAS. There is no etc folder. So does it exist, and is only visible under some other OS, or does this device hide the root folders? Solved. First, I hadn't set the Root Password using ACP Commander. For simplicity I used the NAS admin password. Second, I had not logged into WinSCP as root. Having done that, all seems good.

[@edumaker-alexgibson]

Hi, great tutorial but I have run into an issue: I can't get root access. Can someone help please? Linkstation Mini - LS-WSGL/R1 ACP commander seems to work - it enabled SSH which did not work before, and gives a positive confirmation message if I set the root password. But in WinSCP if I try to SSH in using username root, I get asked for the password, enter it, get Access denied. I have repeated the ACP commander root password update with no joy. Using user 'admin' and password I can SSH in perfectly OK, I can find and edit the files. but I can't save them to make the change :( Help!

[@davewatler9788]

Worked a treat on my old linkstation LS-WXL

[@ddstitt]

Do I need amp commander where do I get or is win’s picking ok. Having trouble getting logged on to the nas with win’s phone or app-commander

[@guzzy92fs]

Brilliant! can anyone explain what the command does exactly? It simply indicates the NAS that the protocol is SMB2?

[@topc5826]

that's what I want to know too. no mention of whether it just spoofs the SMB 1 to replace SMB 2 or actually uses SMB_2 What about it Simon, you still around here after all these years since this vid posting?

[@wakeeee749]

Thanks! mutch needed for a second hand linkstation LS-WXL !

[@68Vitesse]

Firstly, thanks for posting this video, it's all I could find to ressurect my NAS drive. I had high hopes as everything went smoothly - my LS-CHL738 rebooted (took it's time), showed up on NAS Navigator2 and on the Web console but it won't show up in File Explorer - if I type the \\IP address of the NAS into File Explorer it fails with "Windows cannot access" the IP address, (if I type in //IP Address then it pops up the browser console). I've gone back to WinSCP and tried to check the config amendment and it's there. ACP Commander finds the NAS straight away on the IP address I'm using (as does the web console). So now I'm a bit stumped - any ideas please?

[@rlmack35]

Thank you!! It worked great for my LS-QVL!

[@davidwhiteside7044]

Thank you very much for this tutorial Simon!

[@dariodmaster]

I was using LS520D: LinkStation™ 520, and firmware 4.40 released in mid 2018. In January 2020 Buffalo "woke up" and released firmware 4.50 for Linkstation, after update , and disabling SMB1.0 in my win10 I still can access all my shares. In Widows Powershell on my win10: EnableSMB1Protocol: False EnableSMB2Protocol: True Linkstation works fine.

[@Kanne1466]

Hi, I've got a TeraStationPRO which is only working with SMB1 activated within W10. According to this manual I was able to get acp_commander running but there seems to be a Problem: acp_commander telling me that changing root was succesfull, but SFTP is only working with the admin-account (read-only with SFTP) and is not working with the root-account / pw set by acp_commander. Any hints ?

[@gideonfpv1026]

Did you get it to work? Same issue here.

[@TophFu]

Same Issue

[@jackiehung7258]

Than you so much. Easy to follow and now my LS has smbv2. I can access my nas from all my win 10 machines. But somehow chromebook still cannot see the nas with smb file share. I read somewhere that chromebook now use smb3. Any idea if smb3 can be added to old LS?

[@Alcahest]

After using this method SSH is still enabled on a reboot. This is dangerous for multiple reasons, one of which is the extremely weak root password used to make this procedure work. How can SSH be disabled after all this is done ? Or can acp_commander only open pandora's box but cannot properly close if afterwards ?

[@legz7676]

Thank you so much. Crazy that Buffalo is not putting out a patch.

[@andy25104741]

They've always been lazy with this kind of thing in the hope that someone will find a work round to save them from bothering

[@jeffprest4588]

Not working for me. Buffalo firmware is 3.xxx . ACP Commander says it changed my root password but Win SCP wont allow me to save amended text line. Keeps saying root password is incorrect. Any ideas? I really want to keep using this NAS.

[@gurhanbayr5080]

I have downloaded the java files and the gui to do the ssh login. I have put the jar file and the gui exe in to the same directory. I started the gui and was not been able to connect to nas. the ip adress section is dimmed and can not enter anything. The after reading some more material i tried to run the jar file from command line but was not been able to find the proper command line command with the switches to run. Can anyone be kind to explain to me how i use the acp_commander and the gui section in detail so i can go to scp part to modify the file.

[@rockugotcha]

what should I do if I can't save smb file by permission denying?

[@arasu3]

Brilliant, works perfectly...

[@WaveOne11]

When using the WinSCP I'm getting access denied with my LS220D. Please help.

[@olijomusic2481]

Same here! I need help with the same issue

[@JasonSmart]

Big thanks. This worked like a charm. Video liked :)

[@chrisallen5018]

Hi Simon - I followed your instructions using ACP Commander and got confirmation that that SSH was enabled and the root password set to the new value I had assigned it. However, when I then tried to logon via WinSCP or putty using the root credentials I was refused access - "access denied". Any thoughts on what has gone wrong or what I need to do to get the root password effectively changed and SSH enabled successfully? My Linkstation is an LS-WTGL/R1-V3 series. Thanks - Chris

[@ronca1234]

you have the same version as me. I managed to update the file and can see the line min protocol = SMB2 in the SMB.Conf file after reboot. Still get the windows error.... Hopefully you have more luck. Please let me know how you get on?

[@gxambook]

It worked for me. Thanks Simon

[@saipower5081]

I was able to update the smb to v2, however could not map share. Create a folder share. I already have the share folder, but am still getting this error. I have windows 10 Pro version, please help. Thanks

[@boriswessely1854]

Simon - all the steps worked but while I can log into the Linkstation and see everything, I can't see it in the NasNavigator or Explorer

[@johnewing3892]

i lost access to my shared folder on all devices. At first i thought it was just windows but it turned out it was all devices. Managed to update the firmware and also update the DTCP-IP and got the DLNA server working again on my iphone and TV however still cant access shares from my laptop. Followed your instructions and everything seemed to work correctly but it still will not let me access shares. Even checked in etc/samba/smb.conf and it as changed to SMB2 so looks like it worked correctly. I just can access shares form the laptop. Either using \\NAS_Drive\ or \\192.168.1.1XX. any ideas