Setting up a Buffalo LS210D NAS

Wed Jul 19 22:46:49 UTC 2023

On 7/19/23 17:02, Jay Ridgley wrote:
> On 7/19/23 14:24, Little Girl wrote:
>> Hey there,
>>
>> I don't know Samba, so take anything I write here with a huge grain
>> of salt. I took a look at the links. I ran away screaming from the
>> Tech Republic page, because it seemed to be how to set up a Samba
>> server. The Buffalo already has Samba set up on it, from what you
>> wrote, so what you need is client instructions. The Ask Ubuntu page
>> had what looked like some good suggestions.
>>
>> Are you able to access Buffalo's dashboard like the OP on the Ask
>> Ubuntu page did? If so, which version of SMB does the Buffalo use?
> 
> NO That is most of the problem, I think. I get the following response:
> 
> sudo smbclient -L //192.168.1.23
> do_connect: Connection to 192.168.1.23 failed (Error 
> NT_STATUS_CONNECTION_REFUSED)
> 
>> You might need to know that for your mount command.
>>
>> My approach to this kind of problem is to throw spaghetti at the wall
>> until it sticks, so I cobbled together some possible mount commands
>> from that page to try in a terminal window on the client. Two of them
>> use topsecret for the password, so you'll need to edit that, and two
>> of them use version 2.0, so you might need to change that to 1.0.
>>
>> The username and password are surely set by the Buffalo, so if you
>> don't have those, they'll be the next thing you'd need to figure
>> out.
> I entered each of the commands you suggested below, no messages were 
> ever recorded in /var/log/dmesg (I had this command running in another 
> terminal tail -f /var/log/dmesg)
> 
>>
>> sudo mount -t cifs //192.168.1.23/D210 /big_archive
> 
> sudo mount -t cifs //192.168.1.23/D210 /big_archive
> [sudo] password for jay:
> Password for root@//192.168.1.23/D210: **I do not know this ***
> mount error(111): could not connect to 192.168.1.23Unable to find 
> suitable address.
> 
>>
>> sudo mount -t xfs //192.168.1.23/D210 /big_archive
> jay at polar:~$ sudo mount -t xfs //192.168.1.23/D210 /big_archive
> mount: /big_archive: special device //192.168.1.23/D210 does not exist.
> 
>>
>> sudo mount -t cifs -o username=jay //192.168.1.23/D210 /big_archive
> 
> jay at polar:~$ sudo mount -t cifs -o username=jay //192.168.1.23/D210 
> /big_archive
> Password for jay@//192.168.1.23/D210:**********
> mount error(111): could not connect to 192.168.1.23Unable to find 
> suitable address.
>>
>> sudo mount -t xfs -o username=jay //192.168.1.23/D210 /big_archive
> 
> jay at polar:~$ sudo mount -t xfs -o username=jay //192.168.1.23/D210 
> /big_archive
> mount: /big_archive: wrong fs type, bad option, bad superblock on 
> //192.168.1.23/D210, missing codepage or helper program, or other error.
>>
>> sudo mount -t cifs -o
>> uid=jay,username=jay,password=topsecret,nounix,vers=2.0
>> //192.168.1.23/D210 /big_archive
> jay at polar:~$ sudo mount -t cifs -o 
> uid=jay,userid=jay,password=**********,nounix,vers=2.0 
> //192.138.1.23/D210 /big_archive
> mount error(22): Invalid argument
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel 
> log messages (dmesg)
> 
>>
>> sudo mount -t xfs -o
>> uid=jay,username=jay,password=topsecret,nounix,vers=2.0
>> //192.168.1.23/D210 /big_archive
>>
> jay at polar:~$ sudo mount -t xfs -o uid=jay, password=*************, 
> nounix,vers=2.0 //192.168.1.23/D210 /big_archive
> mount: bad usage
> Try 'mount --help' for more information.
> 
>> Once you can get connected manually, an /etc/fstab line can be
>> created. It looks like Steve Grim has a working one that you could
>> edit:
>>
>> https://lists.ubuntu.com/archives/ubuntu-users/2023-July/310796.html
>>
>> All I can do is make guesses, but either way, good luck. It will be
>> very exciting when it finally connects.
>>
> I bhad tried Mr. Grim's example previously to no avail.
> 
> As I said at the start i think the key here is getting the smbclient 
> command to work is the key.
> 
> Thanks,
> Jay
I may be way out of line here, but samba/cifs lost all interest here, 
when Andy took on a helper 15+ years ago and it started growing all 
sorts of windows related stuff tha broke it for my use model.
.
Fist, I have no windows stuff on my local net so the windows 
compatibility is not a concern of mine. But I needed the ability to sit 
in a comfy chair and work on my other machines.  So I messed with 
limited success with nfs for a year or so, but every update session 
broke it at 2 week intervals which got old rapidly.

Then I discovered ssh to login to the other machines, and shortly after 
that, sshfs, so mc can copy any file to any machine and has been doing 
it with no excitement for going on well into the 2nd decade here.  Now 
I've had access to all my network, quite transparently for well over 15 
years.

I don't have any winders machines but I expect there is a windows equ. 
So unless Redmond has broke it, it might even work.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>