What's new

BACKUPMON BACKUPMON installation instructions / tutorial

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I created and changed destination folder to Backup2 to be sure the folder's properties on the NAS were not causing the issue.
Have you been able to get to this folder from another device on your network?
 
In my German version of Win 10 I can't find anything similar to "manage advanced sharing settings". But I will probably figure that one out tomorrow.
Perhaps "Erweiterte Freigabe-Einstellungen verwalten" ?

In English, according to the Googles, in Windows 10 you go to Start > Settings > Network & Internet > Advanced network settings > Network and Sharing Center > Change advanced sharing settings.
 
Have you been able to get to this folder from another device on your network?
Yes no problem. Can see files, move files, copy files to folder specified for destination secondary backup on NAS.
 
Yes no problem. Can see files, move files, copy files to folder specified for destination secondary backup on NAS.
Do you have to manually specify which version(s) of SMB that this share can utilize? I know you said it could handle 2.0 - was that the maximum? Have you tried setting it all the way down to SMB v1.0?
 
Do you have to manually specify which version(s) of SMB that this share can utilize? I know you said it could handle 2.0 - was that the maximum? Have you tried setting it all the way down to SMB v1.0?
I do have the option on the NAS but when I set it 1.0-2.0 the NAS warned about security issues and recommended not to do it. I will set it at 1.0 and give it a try and see if it makes any difference.
 
I do have the option on the NAS but when I set it 1.0-2.0 the NAS warned about security issues and recommended not to do it. I will set it at 1.0 and give it a try and see if it makes any difference.
Yeah, it would just be to test... Any firmware updates available that would perhaps be able to raise the SMB version?
 
@Viktor Jaep

Let me know if the instructions require any updates:

See if these instructions help... this is on a local Windows 11 laptop.

1.) In the search bar, type "sharing", and run the "manage advanced sharing settings"
2.) Expand private networks, ensure that network discovery and file & printer sharing are both "on".
3.) Using file explorer, create a top-level folder somewhere on your drive... call it "backups"
4.) Right-click on "backups", and click on properties -> sharing
5.) Click on the "share" button, hit the drop-down, and select "everyone" -> add -> permission level "read/write" -> and hit the "share" button.
6.) Go back to your properties page, click on "advanced sharing" and just double check under "permissions" that you see "everyone", and they have "read/write/full control" permissions.
7.) At this point, you have a basic share that gives anyone access to this folder on your local network. You can get more granular by creating a local user/pwd, and assigning this user account to this folder... but let's just keep it easy for now.

You can now test access to your folder... copy this script into a test.sh file in your /jffs/scripts... make sure you change the IP to your laptop's IP address... and make sure the share is called "backups" or whatever you called it.

I think I probably need to add 1 more modification to this... I had to do this on Windows Server, so I'm thinking the later versions of Windows 10/Windows 11 may need this step as well.

1.) In the search bar, type "sharing", and run the "manage advanced sharing settings"
2.) Expand private networks, ensure that network discovery and file & printer sharing are both "on".
3.) Using file explorer, create a top-level folder somewhere on your drive... call it "backups"
4.) Right-click on "backups", and click on properties -> sharing
5.) Click on the "share" button, hit the drop-down, and select "everyone" -> add -> permission level "read/write" -> and hit the "share" button.
6.) Go back to your properties page, click on "advanced sharing" and just double check under "permissions" that you see "everyone", and they have "read/write/full control" permissions.
7.) (NEW) You may need to take this additional step before you have access to this folder. Go back to your properties page, click on "Security" and look for your "Everyone" account in this list (or the user you specified). If you do not see this user listed you will need to specifically grant them permissions to interact with the folder itself -- click on the "edit" button, click "add", find the "Everyone" user (or the one you specified), hit "OK" to add them, then make sure that this user is assigned the "Full Control" rights (or as you see fit). Hit "OK" to save these config settings.
8.) At this point, you have a basic share that gives anyone access to this folder on your local network. You can get more granular by creating a local user/pwd, and assigning this user account to this folder... but let's just keep it easy for now.
 
Yeah, it would just be to test... Any firmware updates available that would perhaps be able to raise the SMB version?
It didn't make any difference. Still can't mount the drive. Many tries both Network and NTSF and it can't mount the drive.

Just as an experiment even tried to write to the same folder on the NAS where I backup my PC every evening.

I will reach out to Synology and see if they have any suggestions.

I will let you know if I find out anything.

Thanks.
 
Thanks but still no joy.

Running first command returns: Module md4 not found modules.dep

Second command after making necessary changes returns

mounting \\192.168.216.25\ on tmp/mnt/backup2 failed

I created and changed destination folder to Backup2 to be sure the folder's properties on the NAS were not causing the issue.

Hey @CaptainSTX ... just looking at this again pulling my hair out... ;) make sure your mount statement includes a \\\\server\\path... it seems that was cut off based on that output above? Also had noticed you had several nested subfolders in your target path. Perhaps try making it simpler like \\\\NASIP\\Backup ? Last thing... pay attention to upper/lower case of everything... sometimes it matters.

Code:
mount -t cifs \\\\192.168.11.13\\Backup /tmp/mnt/backup2 -o "vers=2.0,username=myname,password=mypass"

I will reach out to Synology and see if they have any suggestions.

I will let you know if I find out anything.
There's a bunch of folks with Synology NAS's on this forum... Perhaps see if you can get someone to respond with the make/model/version you're running and see if you can compare notes?
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top