Forumite Members › General Topics › Tech › PC Talk › Buffalo Nas not detected.
- This topic has 11 replies, 5 voices, and was last updated 7 years, 2 months ago by
Ed P.
-
AuthorPosts
-
January 4, 2019 at 4:30 pm #29653
A up lads, decided to bring my nas up to date, firmware 1.74 w10. Buffalo sl chl rebooted and said all was good but windows cannot detect nas drive.
looks like? all adresses to detection have been wiped?
I’m a bit lost here!
January 4, 2019 at 6:07 pm #29654There is a Windows update that’s been knackering network access, it’s fixed by upgrading to the latest version of W10 – 1809.
You can probably still access it via it’s IP address \\ipaddress\sharename
January 4, 2019 at 6:21 pm #29656You might find that it’s because of SMB1 being removed from Windows 10. I’ve got a Buffalo LinkStation that won’t connect to Windows anymore because of it. Ubuntu 18.04 connects to it with no problem though.
I can understand why MS removed it, but the sudden lack of access to my backup device with no explanation really wasn’t helpful.
January 4, 2019 at 6:59 pm #29658The withdrawal of the SMB1 function has been heralded for so long even the wide boys thought it should just go, I disabled it months ago, could even be more than a year ago. I agree with Dave 1809 did greatly improve finding devices on my network allowing the server, several print servers and the PVRs to be seen and usually used from my PC. An old Buffalo device is hung off of the USB port on one of my repurposed old routers that now acts as an AP and that Buffalo can be seen and accessed very easily.
January 4, 2019 at 8:39 pm #296671.74 was actually released in Feb 18 and it fixes Samba ver 3+ vulnerabilities, so I don’t think it’s an SM1 issue. The previous update was July 17, again Samba vulnerabilities. You have to go back to 2013 for any o/s bug fixes.
January 4, 2019 at 9:51 pm #29668TY for replies.
OK It is done. I used Fing io to find the linkstation which gave me the IP address. I then went into it and set to share. Whooooo! Now watching Ice Cold In Alex and I’m Having A Beer 2 🙂
January 5, 2019 at 4:05 am #29674The withdrawal of the SMB1 function has been heralded for so long even the wide boys thought it should just go, I disabled it months ago, could even be more than a year ago.
That’s one of the reasons it threw me. I remember the fuss, and the updates that supposedly turned it all off, and my NAS worked afterwards. Like most people, I had no clue what the Buffalo box was running, just that it was up to date according to the web interface. A few weeks ago I tried to double check a backup before I went away, and I couldn’t access it through Windows.
God knows why, but Windows let me access it up until recently.
January 5, 2019 at 8:24 am #29676It’s the Windows update before the big 1809. I’ll try and find the KB number.
January 5, 2019 at 12:46 pm #29681Thanks Dave, but don’t worry. I’m not going to risk rolling it back, especially if Ubuntu can access the drive. I’ve got it running in VirtualBox, so I can get the files off if I need to. It doesn’t look like Buffalo are going to release an update to help out either, so I’ll just retire the boxes.
January 5, 2019 at 1:53 pm #29686When your W10 boxes upgrade to 1809 (you can force it with Update Assistant) they’ll be back again.
January 5, 2019 at 11:32 pm #29697I’ll have to check tomorrow but I’m pretty sure that they’re on 1809.
I think Windows just doesn’t like me 😀
January 7, 2019 at 12:28 pm #29725Have you fixed it yet – you could try a hack to add smb2 (of course the usual backup important files applies!) — link
“Meantime for use my linkstation now i have modified /etc/init.d/smb.sh
after this line –> /usr/local/sbin/nas_configgen -c samba
add this line –> sed -i ‘2 i\ max protocol = SMB2’ /etc/samba/smb.confafter restart linkstation, my window pc with SMBv1 disabled, can work with the NAS.”
For the usual reasons I would not advise hacking Windows to allow smb1
-
AuthorPosts
- You must be logged in to reply to this topic.
