file server for storage

install cifs
install samba
install nfs-server

use blkid
add strorage to fstab for boot time mount

setup smb.conf
setup /exports
install dropbox
re-assign location of dropbox

https://www.dropbox.com/install-linux

https://help.dropbox.com/installs-integrations/desktop/linux-commands

https://linux.dropbox.com/packages/

64-bit:

cd ~ && wget -O - "https://www.dropbox.com/download?plat=lnx.x86_64" | tar xzf -

Next, run the Dropbox daemon from the newly created .dropbox-dist folder.

~/.dropbox-dist/dropboxd

*******

https://www.techrepublic.com/article/how-to-install-and-run-dropbox-from-a-headless-linux-server/

--30--

Error 53, or not available error on Windows 10

Microsoft in their infinite wisdom have horribly broken SMB1 functionality on Windows 10.  No simple way to turn it back on, nor any explanation of why it is broken.

When you try to connect to a share via the protocol \\192.168.1.1\share you get an error not available, or an error 53.

The page below is an extended explanation of the justification, FWIW.  If there was a comprehensible error or change there would be less sarcasm and criticism here,  but just removing an insecure and broken protocol that they invented which was wrong and not putting in a way to recover when a release upgrade is made is just nuts.

When you upgrade to the 1709 creator release, or so, you will see this happen with your shares that have SMB1 and no SMB2 version support.  FWIW, I believe the latest and approved SMB is 4. 

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

Knowledge base workaround to re-enable it or get it back

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

seems to be in the same spot you enable and install the Ubuntu shell support

Windows server





Windows 8 and 10



-30-

how to mount drives on Windows 10 Ubuntu shell

From link below, can get to drives or other servers

https://superuser.com/questions/1114341/windows-10-ubuntu-bash-shell-how-do-i-mount-other-windows-drives

Good news, it is now possible to mount USB media (including formatted as FAT) and network shares with drvfs on Windows 10:
Mount removable media: (e.g. D:)

$ sudo mkdir /mnt/d
$ sudo mount -t drvfs D: /mnt/d

To safely unmount

$ sudo umount /mnt/d

You can also mount network shares without smbfs:

$ sudo mount -t drvfs '\\server\share' /mnt/share

Readynas Radiator 4.1 firmware problem with SMB CIFS shares

The changes made to SMB protocol from version 1 to version 3, seems to have killed the share mode of access on readynas older systems.

Switching to user share mode and creating a user is a pain as well.

But the share name is entered as a user id in passwd, but not put up as a user in the gui, which is a huge hole when you switch from share to user.

the only method of fixing it is to install EnableSSHAccess and log in as root.  One can then set an SMB passwd on the shares that exist, and each will be accessible with that passwd on system thru so far and including windows 10.

Also other secured user access is then possible once the sharing is turned on if desired.  The users cannot access others storage w/o using group access features.

Of course this has a possibility of voiding any service you have with Netgear (warranty for 4.x devices is long gone).  But if you have any service agreements, don't do this w/o checking since it may impact your agreements for unauthorized user mods to devices.

To install ssh access for 4.x radiator do the following

Download EnableRootSSHAccess for your architecture from here

EnableRootSSHAccess

Original NV+ and 1100 systems are Sparc.  Pro and Ultra systems on 4.x will be Intel.  I'm not sure if Arm has a 4.x version.  All the ones I've seen with Arm are 6.0

then:

1. Get the SSH bin file from the ReadyNAS web site. Click the Add-ons for RAIDiator 4.1.3+ link and scroll to the EnableRootSSH link. Download the bin file and store it on your local computer.


2. Log in as admin on your ReadyNAS using a browser


3. Update your ReadyNAS firmware (optional). This is under System > Update. Just click the Check for Updates button.


4. Click the Local tab and click Choose File to find the EnableRootSSH.bin file that you previously downloaded. Upload this and follow the prompts.

 A restart of the Readynas system is required, if you have other users on the device.  (since some windows systems may work).  I doubt if any samba stacks such as one would have with shares on MacOS would work, but they may be impacted.

Install instructions from here;

http://blog.epdoc.com/2009/11/ssh-on-readynas-nv.html

CIFS mount problem on Linux, Error 12, can't allocate memory error

There is a workaround for this which is in the link below.

What worked however is this:

reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters /v Size /t REG_DWORD /d 3 /f
sc stop  LanmanServer
sc start LanmanServer

Will have to research and update link with whatever is being done, but this worked for mounting my Google driver server windows 7 system.

Windows Xp so far has not shown the problem.  Other options have been necessary too, this is just the latest.

Occured on a Cubox debian Wheezy system on 3/27/2017 for me.

mount-cifs-mount-error12-cannot-allocate-memory

possible workaround to readynas windows 10 share problem. (relevant to developer win 10 installs)

Note on removing credential (If I understand it), as a workaround fix for broken Windows 10 fix. 

Windows 10 upgrades to the developer releases seem to be invalidating stored credentials with each update with some regularity.  if you have a drive share mount with stored credentials, or on another front though not with the readynas nas, stored logins for say remote desktop, you have to reinput them.

That was working up to the latest 9/14 or 9/16 set of updates.  now it seems to retain the credential and not let you easily reinput the login, or share.

And it was not accepting any password on other shares, even valid ones.

A fellow on the Readynas forum (where this became a topic) suggested a workaround worth documenting.

Thanks to Readynas forum user nayadn for this.

nayadn (Aspirant) posted a new reply in R6000 Series AC WiFi Routers on 2016-09-17 07:32 AM :

---

Re: Can no longer access ReadyShare drives on Windows 10

i googled again the error and i came up with a sideway solution
go into user account in control panel
if you're in windows 10 select manage your credentials this will open 2 options
web credentials and windows credentials
head to windows credentials and add a new windows credential
enter the location of the drive \\readyshare on the first line
your windows user name in the second line
your windows password in the third line
and you're done, you should see the drive under network and be able to access it as before
good luck

cubox setup notes

with the debian jesse of 3/9/2015, I had to set up the network manually.

copy the contents of /etc/network/intefaces.d/eth0 to the new image.

apt-get -y install cifs-utils  (still work in progress)

apt-get -y install nfs-common nfs-server to get nfs stuff set up

cifs mounts are not running, but smbd is running fine.  Still to gen up further testing as of 4/12/15

cifs / smbfs mount notes

http://www.thatsquality.com/articles/mounting-windows-smb-file-shares-using-cifs

Note:  from above articles writing to present, package install has changed form

apt-get -y install smbfs

to

apt-get -y install cifs-utils

Now, if it worked, you should see your mount right on the desktop. Browse through it, play music from it, watch movies from it (network speed permitting). Here are some common errors:

• mount error: can not change directory into mount target... - either you didn't create your /media/my_share directory or specified it wrong in your mount command.
• mount error 13 = Permission denied - your username and password are being rejected. Try some other combinations
• mount error 6 = No such device or address - the share_name that you specified in your mount command is not being found on the host computer. Browse the network, find that computer, and check to make sure you see the exact share name.