This link to Ubuntu forums might be a help with Samba issues: https://ubuntuforums.org/showthread.php?t=2432909
After upgrading my server from Xubuntu 18.04 to 20.04 I could no longer connect to shares from my Seagate GoFlex TV media player. This only supports SMBv1, as do many older, working NAS devices such as my old Buffalo Linkstation. The firmware of these will never be updated so you have to make SMBv1 work somehow. The suggestion in the final post on that link sorted things out for me.
Last edit: MrB 2020-06-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are coming across this discussion forum topic and need help connecting to an SMB/CIFS server, MrB is completely correct that many older SMB servers only support SMBv1. The SMB client available on more recent versions of Ubuntu attempts use SMBv3.1.1 by default, which causes issues when trying to connect to older samba servers. For users affected by this particular issue, I recommend trying to connect using a different SMB version, for example by entering "1.0" in the Version field.
Q: I am having trouble connecting to a network shared folder using SMB/CIFS?
A: First make sure the fields have the correct UNC path (eg "\\fileserver\johnsmith") and username/password. Some network shares may not support the default SMB 3.1.1 protocol, so you may need to enter '2.1' or even '1.0' in the version field.
It has been reported that to connect to an anonymous/unauthenticated shared folder the username field needs to be filled with a single asterisk character (*), despite the field being marked as optional. This will be improved in the next version.
Rescuezilla v2.0 had an issue where the version field didn't work correctly, but this has been resolved on Rescuezilla v2.1 and newer.
(Edit Feb 2021: Updated the quoted Frequently Asked Question to the most recent revision)
Last edit: Rescuezilla 2021-02-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-02-08
Are you considering adding other network protocols alongside smb? For example SSH. Being one who likes to exist in a Linux world I found adding smbd to my Linux server quite messy. As you know Clonzilla offers SSH it as one of its options. BTW I started using Rescuezilla because Clonezilla refused to back up my new box that has UEFI citing partition table errors . It had worked fine with earlier computers. No problem with Rescuezilla so far in that respect. Thanks for your good work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I hope to finally add support for more network protocols in Rescuezilla v2.2, which scheduled for release in May 2021. Sorry it has taken so long, I was focused on getting other functionality out to users like Image Explorer (beta), so additional network protocols had been lower priority until now. Here are the 3 tasks captured on GitHub if anybody is interested:
It's interesting that you've had trouble making a backup with Clonezilla but not with Rescuezilla. Both programs work very similarly internally, so potentially the issue you describe has been fixed in more recent versions of Clonezilla.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-02-25
i am a windows 7 user and have tried for quite some time to get a network backup done on a non-passworded, open system. The mount always fails, although i enter all the correct information. i have found the solution and thought it may help someone. this is finally what worked for me...
\\100.100.100.100\backupsusername:*ver:2.1
i used the ip address of the receiving computer and directory, populated the name field with an * asterisk and used 2.1 as version. it works like a charm. it seems the name and password fields that are labeled optional actually have to be populated. my system does not require a password but the name field must have an asterisk to work. hope this helps someone.
(Edit by Rescuezilla: Enclosed the IP, username and version as a codeblock so that all characters are displayed)
Last edit: Rescuezilla 2021-02-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It has been reported that to connect to an anonymous/unauthenticated shared folder the username field needs to be filled with a single asterisk character (*), despite the field being marked as optional. This will be improved in the next version.
I have just created GitHub task #190 to capture the exact details behind this poor-usability issue. It looks like the difficulty connecting to anonymous/unauthenticated shared folders likely affects Rescuezilla v2.1.3 and all prior versions. I will improve things for Rescuezilla v2.2, which is scheduled for release in May 2021. Until then your asterisk character workaround looks great! Thanks for letting me know!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-07-22
@rescuezilla, I am not OP. Please consider these UX on SMB share: browser a server's shares from gui. currently I do smbclient -U ham -W spam -L eggs and it lists the shares. I cannot recommend this to GUI users. Next problem is critical data on same share by many groups. Ideally gui SMB browse would work read-only. After selecting the backup destination from a large directory tree hierarchy on the share, rescuezillapy would rw mount that to /mnt/backup . For me the biggest UX problems with clonezilla is network card initialization and SMB share browsing. Rescuezilla worked well for network card, but SMB browse is the same old thing in my version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-07-22
browser a server's shares
I meant browse a server's shares
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes and more, GUI to list SMB shares, and it would be good to chdir into the share and select a possibly nested subdirectory which I would like as /mnt/backup
the ability to mount shares as read-only on restore/verify/explore operations?
no. although that would also be good. but what I meant was for the above. during selecting the SMB share in the imagined GUI, I imagine to go into a subfolder. During doing this I want to prevent dragging around directories or deletion and for this reason it would be best if the data of the GUI would come from a read-only access to the list of shares and the subfolders of a selected share. what you said is entirely different however that also makes sense in that context so I also would support that.
New suggestion 2:
could you please install gvfs-backends , because although "Nautilus" / Gnome Files / Files exist in your rescuezilla ubuntu image, IT is NOT possible to use smb://[user@]host[:port][/share] because the gvfs-backends has the /usr/lib/gvfs/gvfsd-smb/ and that is what handles the smb uri scheme.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-10-24
New suggestion 3:
when going Back and Next in the GUI, the settings are forgotten.
This is not surprising for bash scripts of clonezilla, but is it really necessary for a GUI like rescuezilla to forget the settings the user painfully entered already, only because Back and Next is pressed? For example the user realizes a different partition is needed, too late in the process, goes back to unselect the bad partition, and going Next from there, the user enters the settings for the second time.
New suggestion 4:
I should also suggest this to clonezilla , but it would be really helpful if the settings could be filled up partially from a config file, that could be selected from gui, or preselected from boot loader. I imagine multiple config files I want to customize my image with. Then according to the case, the good configuration is selected. The user would still be able to set up more settings by hand, however, instead of defaults hardcoded into rescuezilla, now some of the settings could be customized with simple config files to provide a more appropriate default.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-11-10
If there are any questions I can help with about the above... I think gvfs-backens would be the most valuable compared to cost because it easily enables smb share navigation in nautilus gnome files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-10-24
Hey, just wanted to mention, thank you for the latest work on your release, I am very happy the development is ongoing!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This link to Ubuntu forums might be a help with Samba issues: https://ubuntuforums.org/showthread.php?t=2432909
After upgrading my server from Xubuntu 18.04 to 20.04 I could no longer connect to shares from my Seagate GoFlex TV media player. This only supports SMBv1, as do many older, working NAS devices such as my old Buffalo Linkstation. The firmware of these will never be updated so you have to make SMBv1 work somehow. The suggestion in the final post on that link sorted things out for me.
Last edit: MrB 2020-06-26
Hi MrB,
Thanks for the workaround/suggestion for Rescuezilla (a fork of the Redo Backup and Recovery project by a new developer). You are referencing an issue where Rescuezilla v1.0.6.1 cannot connect to a samba server hosted on Ubuntu 20.04 (task #84). I have responded to your suggestion on that GitHub issue.
If you are coming across this discussion forum topic and need help connecting to an SMB/CIFS server, MrB is completely correct that many older SMB servers only support SMBv1. The SMB client available on more recent versions of Ubuntu attempts use SMBv3.1.1 by default, which causes issues when trying to connect to older samba servers. For users affected by this particular issue, I recommend trying to connect using a different SMB version, for example by entering "1.0" in the Version field.
As noted in the Frequently Asked Questions:
(Edit Feb 2021: Updated the quoted Frequently Asked Question to the most recent revision)
Last edit: Rescuezilla 2021-02-26
Are you considering adding other network protocols alongside smb? For example SSH. Being one who likes to exist in a Linux world I found adding smbd to my Linux server quite messy. As you know Clonzilla offers SSH it as one of its options. BTW I started using Rescuezilla because Clonezilla refused to back up my new box that has UEFI citing partition table errors . It had worked fine with earlier computers. No problem with Rescuezilla so far in that respect. Thanks for your good work.
Hi Anonymous,
I hope to finally add support for more network protocols in Rescuezilla v2.2, which scheduled for release in May 2021. Sorry it has taken so long, I was focused on getting other functionality out to users like Image Explorer (beta), so additional network protocols had been lower priority until now. Here are the 3 tasks captured on GitHub if anybody is interested:
It's interesting that you've had trouble making a backup with Clonezilla but not with Rescuezilla. Both programs work very similarly internally, so potentially the issue you describe has been fixed in more recent versions of Clonezilla.
Don't forget to give a "like" on AlternativeTo so that more people can discover Rescuezilla! :-)
i am a windows 7 user and have tried for quite some time to get a network backup done on a non-passworded, open system. The mount always fails, although i enter all the correct information. i have found the solution and thought it may help someone. this is finally what worked for me...
i used the ip address of the receiving computer and directory, populated the name field with an * asterisk and used 2.1 as version. it works like a charm. it seems the name and password fields that are labeled optional actually have to be populated. my system does not require a password but the name field must have an asterisk to work. hope this helps someone.
(Edit by Rescuezilla: Enclosed the IP, username and version as a codeblock so that all characters are displayed)
Last edit: Rescuezilla 2021-02-26
Oh, very nice find! I have just updated the frequently asked questions:
I have just created GitHub task #190 to capture the exact details behind this poor-usability issue. It looks like the difficulty connecting to anonymous/unauthenticated shared folders likely affects Rescuezilla v2.1.3 and all prior versions. I will improve things for Rescuezilla v2.2, which is scheduled for release in May 2021. Until then your asterisk character workaround looks great! Thanks for letting me know!
@rescuezilla, I am not OP. Please consider these UX on SMB share: browser a server's shares from gui. currently I do smbclient -U ham -W spam -L eggs and it lists the shares. I cannot recommend this to GUI users. Next problem is critical data on same share by many groups. Ideally gui SMB browse would work read-only. After selecting the backup destination from a large directory tree hierarchy on the share, rescuezillapy would rw mount that to /mnt/backup . For me the biggest UX problems with clonezilla is network card initialization and SMB share browsing. Rescuezilla worked well for network card, but SMB browse is the same old thing in my version.
I meant browse a server's shares
If I understand, you want:
Is that correct?
Last edit: Rescuezilla 2022-07-22
Hello @rescuezilla , I am from https://sourceforge.net/p/rescuezilla/discussion/discussion/thread/a484b22dd2/?limit=25#e4bb
yes and more, GUI to list SMB shares, and it would be good to chdir into the share and select a possibly nested subdirectory which I would like as /mnt/backup
no. although that would also be good. but what I meant was for the above. during selecting the SMB share in the imagined GUI, I imagine to go into a subfolder. During doing this I want to prevent dragging around directories or deletion and for this reason it would be best if the data of the GUI would come from a read-only access to the list of shares and the subfolders of a selected share. what you said is entirely different however that also makes sense in that context so I also would support that.
New suggestion:
may I recommend you install krb5-user because the preferred authentication in an active directory domain is kerberos according to https://learn.microsoft.com/en-us/windows-server/security/windows-authentication/security-support-provider-interface-architecture#BKMK_KerbSSP
also could you please install
New suggestion 2:
could you please install gvfs-backends , because although "Nautilus" / Gnome Files / Files exist in your rescuezilla ubuntu image, IT is NOT possible to use
smb://[user@]host[:port][/share]because the gvfs-backends has the /usr/lib/gvfs/gvfsd-smb/ and that is what handles the smb uri scheme.The scheme format I found in https://wiki.gnome.org/Projects/gvfs/schemes (even if now gio replaced gvfs), which should be noted because for example CUPS uses a completely different scheme format. There is also the official third format, which is https://www.iana.org/assignments/uri-schemes/prov/smb and I have no idea if gnome supports it or not.
New suggestion 3:
when going Back and Next in the GUI, the settings are forgotten.
This is not surprising for bash scripts of clonezilla, but is it really necessary for a GUI like rescuezilla to forget the settings the user painfully entered already, only because Back and Next is pressed? For example the user realizes a different partition is needed, too late in the process, goes back to unselect the bad partition, and going Next from there, the user enters the settings for the second time.
New suggestion 4:
I should also suggest this to clonezilla , but it would be really helpful if the settings could be filled up partially from a config file, that could be selected from gui, or preselected from boot loader. I imagine multiple config files I want to customize my image with. Then according to the case, the good configuration is selected. The user would still be able to set up more settings by hand, however, instead of defaults hardcoded into rescuezilla, now some of the settings could be customized with simple config files to provide a more appropriate default.
If there are any questions I can help with about the above... I think gvfs-backens would be the most valuable compared to cost because it easily enables smb share navigation in nautilus gnome files.
Hey, just wanted to mention, thank you for the latest work on your release, I am very happy the development is ongoing!