Yet Another Samba Share Mounter
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonjour,
I was running an old version of Puppy today (4.3.1) and accidentally (or by chance!) noticed that, using yassm 2.4, I could access to an usb key plugged on my Internet box, what I couldn't do with later versions 2.6 and 2.7! I thought it was my box or any misconfigured permission/password which was the cause of the problem but it is finally not the case.
Have you any idea of what's wrong?
Cordialement.
I was running an old version of Puppy today (4.3.1) and accidentally (or by chance!) noticed that, using yassm 2.4, I could access to an usb key plugged on my Internet box, what I couldn't do with later versions 2.6 and 2.7! I thought it was my box or any misconfigured permission/password which was the cause of the problem but it is finally not the case.
Have you any idea of what's wrong?
Cordialement.
YASSM v2.7 uses a new scanning method based on a tool called pnscan. Earlier versions used mpscan, but the 4.x Puppies may have contained a different version of mpscan.
Pnethood used a different tool called nbtscan!
Based on a variety of tests, it appears that v2.7 works better than the older versions of YASSM. But that may not be true in your case.
With v2.7, did you try using Wake or Rescan?
[Edit] In v2.7, was the share detected by YASSM-search? This may be a situation where new Puppies need to use the "sec=ntlm" option in YASSM-login.
Pnethood used a different tool called nbtscan!
Based on a variety of tests, it appears that v2.7 works better than the older versions of YASSM. But that may not be true in your case.
With v2.7, did you try using Wake or Rescan?
[Edit] In v2.7, was the share detected by YASSM-search? This may be a situation where new Puppies need to use the "sec=ntlm" option in YASSM-login.
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonsoir,
Thanks for your quick reply!
Thanks.
Cordialement.
Thanks for your quick reply!
Pnethood doesn't "see" my usb key, contrary to yassm.Pnethood used a different tool called nbtscan!
Not needed. I just couldn't mount it...did you try using Wake or Rescan?
... and with the option "sec=ntlm", all works fine.In v2.7, was the share detected by YASSM-search? This may be a situation where new Puppies need to use the "sec=ntlm" option in YASSM-login.
Thanks.
Cordialement.
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonjour,
Please see this thread.
Cordialement.
For those who are interested in, the French team did it!rcrsn51 wrote:Do you want the share to be automatically unmounted if it has not been used for a while? I think that would be too difficult to implement.
Please see this thread.
Cordialement.
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonjour,
A Puppy user sent this message to me (Google translation), using yassm to access to a machine running Windows 10 (I cannot reproduce this...)
Cordialement.
A Puppy user sent this message to me (Google translation), using yassm to access to a machine running Windows 10 (I cannot reproduce this...)
What could I suggest to him to solve this problem?I tried the option sec=ntlm, but unsuccessfully.
My other machines under Linux have not this access problem.
A smbclient -L ip-pc-windows gives me a NET_STATUS_ACCES_DENIED
The firewall is deactivated.
Cordialement.
Every version of Windows makes sharing more complicated. The only way I could get it to work in Win10 was by turning password protected sharing OFF.
Right-click on the shared folder > Properties > Sharing
At the bottom, click on Network and Sharing Center.
Select All Networks.
Select Turn off password protected sharing.
I thought that I once has this working with password protected sharing ON, but I couldn't get it to work this time.
Right-click on the shared folder > Properties > Sharing
At the bottom, click on Network and Sharing Center.
Select All Networks.
Select Turn off password protected sharing.
I thought that I once has this working with password protected sharing ON, but I couldn't get it to work this time.
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonjour,
Cordialement.
Here is the answer of this Puppy/yassm user:rcrsn51 wrote:I thought that I once has this working with password protected sharing ON, but I couldn't get it to work this time.
Is there really nothing to do, because if it is a handicap for now, it should be more severe for the future... especially for maintainers who bet everything on yassm?Thank you for the information.
However it is not the nature of the problem because I had already set the sharing under Windows without password.
I always try empirically from time to time to find a solution.
The distributions based on Ubuntu reach it with no problem at all. Mageia, based on RedHat also.
My technical knowledge under Linux is insufficient to understand what makes that some distributions reach it with no problem at all while others not.
Cordialement.
@Argolance: What Puppy version is causing the problem? I am seeing the same problem with a Win10 share in some Puppies like Precise. This command fails
For some reason, Slacko Puppies work, even though they use the same version of smbclient!
Here is what fixed it for me in Precise.
1. Go here and get the samba4_basic_tahrpup-4.1.9.pet.
2. Get the patch file for your particular Puppy.
3. Get the samba4_client-4.1.9.pet.
You need to install the Samba server package in Step 1 because it has dependencies for the Samba client tools.
I have not checked to see if Precise also has a problem with Win7 shares. I would assume that someone has already done so. [Edit] I did a quick test of Precise 571 with a Win7 share and it worked correctly OOTB, including password-protection.
I tried many ways to get the Win10 share working with password-protected sharing turned ON, but they all failed. I wonder if this works in other Linuxes?
Code: Select all
smbclient -NL aaa.bbb.cc.dd
Here is what fixed it for me in Precise.
1. Go here and get the samba4_basic_tahrpup-4.1.9.pet.
2. Get the patch file for your particular Puppy.
3. Get the samba4_client-4.1.9.pet.
You need to install the Samba server package in Step 1 because it has dependencies for the Samba client tools.
I have not checked to see if Precise also has a problem with Win7 shares. I would assume that someone has already done so. [Edit] I did a quick test of Precise 571 with a Win7 share and it worked correctly OOTB, including password-protection.
I tried many ways to get the Win10 share working with password-protected sharing turned ON, but they all failed. I wonder if this works in other Linuxes?
Last edited by rcrsn51 on Fri 04 Dec 2015, 20:37, edited 1 time in total.
Samba-TNG is self-contained in /usr/local/samba. Its start/stop scripts are in /usr/local/bin. Samba4 Basic does not use any of these, so you can safely delete them.
I was curious about how the mainstream Linuxes work with Windows 10 shares, so I booted Ubuntu 14. It had the same problem - it could only mount the share if password-protection was OFF.
I was curious about how the mainstream Linuxes work with Windows 10 shares, so I booted Ubuntu 14. It had the same problem - it could only mount the share if password-protection was OFF.
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonjour,
--------------------------------------------
Something else concerning yassm:
When I copy any file to my usb drive plugged to my Box, it works well though I get this message every time:
Please, what does this mean?
Thank you.
Cordialement.
Sorry but I want to be sure I well understood: is it to say the whole /usr/local/samba directory can be safely deleted?Samba-TNG is self-contained in /usr/local/samba. Its start/stop scripts are in /usr/local/bin. Samba4 Basic does not use any of these, so you can safely delete them.
Good... and bad news!I was curious about how the mainstream Linuxes work with Windows 10 shares, so I booted Ubuntu 14. It had the same problem - it could only mount the share if password-protection was OFF.
--------------------------------------------
Something else concerning yassm:
When I copy any file to my usb drive plugged to my Box, it works well though I get this message every time:
Code: Select all
Copie de /mnt/sdb2/my-pictures/argolance.gif vers /root/YASSM/USB1@192.168.1.1/argolance.gif
cp: preserving permissions for `/root/YASSM/USB1@192.168.1.1/argolance.gif': Permission denied
Impossible de copier '/mnt/sdb2/my-pictures/argolance.gif'
Terminé
Il y a eu une erreur.
Thank you.
Cordialement.
- Attachments
-
- 151206_112022_495x254_easyshot.jpg
- (21.83 KiB) Downloaded 1095 times
1. Yes, you can delete the folder /usr/local/samba.
2. Regarding the error message when copying:
a. I have seen some versions of ROX throw this error message, even though it copied the file correctly.
b. What Puppy version are you using on the client machine?
c. How are the two drives formatted - the local drive sdb2 on the client and the shared drive USB1 on the server. FAT32 or NTFS?
d. I set up some test machines with Samba4 Basic and YASSM using FAT32 drives, but I could not make the error message happen.
2. Regarding the error message when copying:
a. I have seen some versions of ROX throw this error message, even though it copied the file correctly.
b. What Puppy version are you using on the client machine?
c. How are the two drives formatted - the local drive sdb2 on the client and the shared drive USB1 on the server. FAT32 or NTFS?
d. I set up some test machines with Samba4 Basic and YASSM using FAT32 drives, but I could not make the error message happen.
- Argolance
- Posts: 3767
- Joined: Sun 06 Jan 2008, 22:57
- Location: PORT-BRILLET (Mayenne - France)
- Contact:
Bonsoir,
USB1: FAT32
Cordialement.
OK, thanks!rcrsn51 wrote:1. Yes, you can delete the folder /usr/local/samba.
USB drive is directly plugged to my Internet Box.b. What Puppy version are you using on the client machine?
sdb2: ext2c. How are the two drives formatted - the local drive sdb2 on the client and the shared drive USB1 on the server. FAT32 or NTFS?
USB1: FAT32
Cordialement.
So your Internet box is acting as the Samba server? When I set up a Samba4 server on a Puppy machine with the same drive configurations, ROX doesn't throw any errors.Argolance wrote:USB drive is directly plugged to my Internet Box.
Here is something to try. In the yassm-login Options box, enter "nounix". Or maybe "noperms".