Nice Samba hints and setup page

 Still looking for solution to a problem mounting from some servers onto an Ubuntu 22, and getting a 115 error.  apparently an improperly rejected connect attempt, but no solution yet.

https://linuxconfig.org/how-to-configure-samba-server-share-on-ubuntu-22-04-jammy-jellyfish-linux

set up a samba share on Ubuntu 20-04

 

https://www.techrepublic.com/article/how-to-create-a-samba-share-on-ubuntu-server-20-04/

--30--

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--

Workaround for when windows shares have bad credentials

Not sure if this is the correct way to remove badly credentialed shares, but a start

When you have a device on a network share and get the login incorrect, there seems to be no way to remove the bad "guess" or login so you can retry or correctly enter a password.  This is via the GUI access to shares.

This may be a way to force the credential to go away, by using a command line net command to remove it.  Untried thus far, but may work.

Execute "net use" in windows cmd box.
It will display all the links.
Run following command to remove your PI's link:

net use /D \\192.168.0.165\share

Then retry the access.
30
 

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