Yet Another Samba Share Mounter
Yet Another Samba Share Mounter
-----------------------------
Important Updates:
For Puppies with very new (k4.13.x) kernels, read here about a new YASSM option. It appears that you must now explicitly state the SMB version of the target server.
For example, "vers=1.0" or "vers=2.1". Read here for more info about Windows servers.
Accessing some ancient Samba servers, Android tablets, etc. may require the YASSM option sec=ntlm. However, this old security setting has been finally dropped from recent Samba client versions.
----------------------------
YASSM is a tool for accessing shares located on remote servers. These could be shared folders on a Windows machine, an NAS box or a Linux Samba server.
Look for it in the Network/Internet menu as "YASSM Samba share mounter".
Note: If you have any existing setup files in /root/.yassm belonging to very old YASSM versions, you must delete them first.
---------------------------
Before starting YASSM, you need to know the IP addresses of the Samba server machines on your network. You can find them by running PeasyPort and scanning for ports 139 or 445. You should also know the names of the shares on those servers, but you can look them up if necessary.
Run YASSM. Click the New button.
On the next screen fill in the details for a target Samba share.
If you are logging into a basic Windows XP share, leave the Username, Password and Options fields empty. A Win7 or newer share may require authentication with a password. A share on a Linux Samba server may require authentication, depending on its configuration.
The server MUST be identified by its IP address.
If you need to identify the shares on the server, click Shares.
Click Test to verify the connection. Your file manager will open with a window/tab for the share. The mount points are in your home directory in the folder YASSM.
Click Save. Give the share a one-word nickname that uniquely identifies it on the network, like "Freds-Music". This creates a setup file for the share in the hidden folder /root/.yassm.
Click Quit and Restart. Select your new share. Click Mount.
Repeat the procedure for other shares on your network.
-------------------------
Use the Options field for arguments like sec=ntlm or iocharset=utf8. Multiple options must be separated by commas. To make the geany text editor work with files in a Windows share, you will need the option noserverino.
----------------------
For your convenience, you can drag a shortcut to /root/YASSM folder onto your desktop. If necessary, press the ROX Rescan button (the blue Recycle symbol) to update the mounted shares. To disconnect a share, use the ROX Unmount command. Or you can use YASSM's Unmount button to disconnect all the mounted shares at once.
-------------------
YASSM works primarily with IP addresses under the assumption that your network's Samba servers have static addresses. But V4.6 offers an alternative. The .set config files can now have the extra field "NETBIOS=xxx". If you insert a server's NETBIOS name in this field, YASSM will search the network for the server's current IP address and use it to mount the share instead of the address in the SERVER field. Be aware that this lookup procedure may be unreliable.
------------------
Note to firewall users: YASSM may have trouble mounting shares if the client machine is running the Puppy firewall. Read here.
--------------------------------
Important Updates:
For Puppies with very new (k4.13.x) kernels, read here about a new YASSM option. It appears that you must now explicitly state the SMB version of the target server.
For example, "vers=1.0" or "vers=2.1". Read here for more info about Windows servers.
Accessing some ancient Samba servers, Android tablets, etc. may require the YASSM option sec=ntlm. However, this old security setting has been finally dropped from recent Samba client versions.
----------------------------
YASSM is a tool for accessing shares located on remote servers. These could be shared folders on a Windows machine, an NAS box or a Linux Samba server.
Look for it in the Network/Internet menu as "YASSM Samba share mounter".
Note: If you have any existing setup files in /root/.yassm belonging to very old YASSM versions, you must delete them first.
---------------------------
Before starting YASSM, you need to know the IP addresses of the Samba server machines on your network. You can find them by running PeasyPort and scanning for ports 139 or 445. You should also know the names of the shares on those servers, but you can look them up if necessary.
Run YASSM. Click the New button.
On the next screen fill in the details for a target Samba share.
If you are logging into a basic Windows XP share, leave the Username, Password and Options fields empty. A Win7 or newer share may require authentication with a password. A share on a Linux Samba server may require authentication, depending on its configuration.
The server MUST be identified by its IP address.
If you need to identify the shares on the server, click Shares.
Click Test to verify the connection. Your file manager will open with a window/tab for the share. The mount points are in your home directory in the folder YASSM.
Click Save. Give the share a one-word nickname that uniquely identifies it on the network, like "Freds-Music". This creates a setup file for the share in the hidden folder /root/.yassm.
Click Quit and Restart. Select your new share. Click Mount.
Repeat the procedure for other shares on your network.
-------------------------
Use the Options field for arguments like sec=ntlm or iocharset=utf8. Multiple options must be separated by commas. To make the geany text editor work with files in a Windows share, you will need the option noserverino.
----------------------
For your convenience, you can drag a shortcut to /root/YASSM folder onto your desktop. If necessary, press the ROX Rescan button (the blue Recycle symbol) to update the mounted shares. To disconnect a share, use the ROX Unmount command. Or you can use YASSM's Unmount button to disconnect all the mounted shares at once.
-------------------
YASSM works primarily with IP addresses under the assumption that your network's Samba servers have static addresses. But V4.6 offers an alternative. The .set config files can now have the extra field "NETBIOS=xxx". If you insert a server's NETBIOS name in this field, YASSM will search the network for the server's current IP address and use it to mount the share instead of the address in the SERVER field. Be aware that this lookup procedure may be unreliable.
------------------
Note to firewall users: YASSM may have trouble mounting shares if the client machine is running the Puppy firewall. Read here.
--------------------------------
- Attachments
-
- out.png
- (16.49 KiB) Downloaded 483 times
Last edited by rcrsn51 on Sun 26 Apr 2020, 14:12, edited 203 times in total.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Need help on this
Thanks for this pet.
However, when I tried Samba share selector, the response was
"No connection to ShelSources!"
Info in the .dat is
ShelSources,,,sources,192,168.1.100,workgroup
lameSMBqmount was able to mount and explore it
Of course I'd prefer your way.
Can you help me make it work?
I'm still not skilled, so please excuse.
Thanks,
Sheldon
However, when I tried Samba share selector, the response was
"No connection to ShelSources!"
Info in the .dat is
ShelSources,,,sources,192,168.1.100,workgroup
lameSMBqmount was able to mount and explore it
Of course I'd prefer your way.
Can you help me make it work?
I'm still not skilled, so please excuse.
Thanks,
Sheldon
Can samba-login find the share?
Instead of the IP address, you should have the server name.
Code: Select all
ShelSources,,,sources,192,168.1.100,workgroup
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
No luck so far, rcrscn51; and thank you very much for such a fast response.rcrsn51 wrote:Can samba-login find the share?Instead of the IP address, you should have the server name.Code: Select all
ShelSources,,,sources,192,168.1.100,workgroup
I have tried various things with samba-login ;
at the moment, it's like this:
Code: Select all
Username is blank
Password is blank
Share is H-BCP
Server is SHELDON
Workgroup is WORKGROUP
Thanks again
Sheldon
What names does lameSMBxplorer have for the server and the share? In your example above, you have the share name as "sources".
Also, what Puppy version are you using?
Also, what Puppy version are you using?
Last edited by rcrsn51 on Sun 19 Dec 2010, 18:26, edited 1 time in total.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
lameSMBxplorer says that IP Address is 192.169.1.1 , Server is SHELDON,rcrsn51 wrote:What names does lameSMBxplorer have for the server and the share? In your example above, you have the share name as "sources".
Also, what Puppy version are you using? This package does not work in 2.14.
Share Name is SOURCES and H-BCP
I have also been trying clarf's Pnethood 0.66, no success yet.
Some problem with name servers?
I seem to recall that these things worked under Puppy 4.31?
Currently working with 5.11
Thanks,
Sheldon
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Thanks, rcrsn51.rcrsn51 wrote:What kind of machine is SHELDON?
What does this command return?Code: Select all
nmblookup sheldon
SHELDON (or sheldon?) is an ASUS P5A (motherboard, from approx 1999) which usually boots MS-Windows 98SE from a 160GB HDD connected to a Promise controller (to let the computer see all of the "large" HDD)
The other computer (frugal Puppys 4.31 and 5.11, as well as MS-Windows XP) is an Acer Aspire One, with an Ethernet cable to the Linksys router as well as a wireless adapter.
Since the last messages, I did some stuff, including copying (via /etc/rc.d/rc.local) the following (stored in a file) to /etc/resolv.conf :
Code: Select all
nameserver 192.168.1.1
nameserver 71.242.0.12
nameserver 71.250.0.12
Pnethood 0.66 now seems to work, but samba-login still saysquerying sheldon on 192.168.1.255
192.168.1.100 sheldon<00>
I got the same response from samba-shares and selecting ShelSourcesNo connection to H-BCP!
So nmblookup is correctly finding sheldon's IP address. So let's try to mount the share manually. First make a mount point
Then mount the share with
Are there any error messages? If not, have a look in /root/mnt.
Code: Select all
mkdir /root/mnt
Code: Select all
mount-FULL -t cifs //192.168.1.100/H-BCP /root/mnt -o guest
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Thank you.rcrsn51 wrote:So nmblookup is correctly finding sheldon's IP address. So let's try to mount the share manually. First make a mount pointThen mount the share withCode: Select all
mkdir /root/mnt
Are there any error messages? If not, have a look in /root/mnt.Code: Select all
mount-FULL -t cifs //192.168.1.100/H-BCP /root/mnt -o guest
The result was:
I'll reboot later this evening into Puppy 4.31 , and re-try that test .mount error 112 = Host is down
Refer to the mount.cifs manual page (e.g. man mount.cifs)
Repeat the above command, but use "smbfs" instead of "cifs".
Code: Select all
mount-FULL -t smbfs //192.168.1.100/H-BCP /root/mnt -o guest
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
win98 shares from puppy
In the interim, I'd booted 4.31, and got the same results.rcrsn51 wrote:Repeat the above command, but use "smbfs" instead of "cifs".Code: Select all
mount-FULL -t smbfs //192.168.1.100/H-BCP /root/mnt -o guest
The following was done under 5.11, like the previous attempt with cifs.
# ls -lt /root/mnt/
total 0
# mount-FULL -t smbfs //192.168.1.100/SOURCES /root/mnt -o guest
mount: wrong fs type, bad option, bad superblock on //192.168.1.100/SOURCES,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[EDIT] I think that this has something to do with the Win98 server. Try:
(all one line)
Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,username=xxx,password=
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Thanks for trying help; I appreciate it.rcrsn51 wrote:[EDIT] I think that this has something to do with the Win98 server. Try:(all one line)Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,username=xxx,password=
Oops! It works!?!?mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,username=xxx,password=
mount error 13 = Permission denied
Refer to the mount.cifs manual page (e.g.man mount.cifs)
Wonder what happened - maybe changed the sharing on the Win98 computer? rebooting?
Will have to try all this again tomorrow.
# mount.cifs //192.168.1.100/SOURCES /root/mnt -o servernetbiosname=SHELDON,username=xxx,password=# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 516040 32008 484032 7% /
/dev/sda5 12630768 5027344 7603424 40% /initrd/mnt/dev_save
/dev/loop1 516040 32008 484032 7% /initrd/pup_rw
tmpfs 129584 128716 868 100% /initrd/mnt/tmpfs
/dev/loop0 128640 128640 0 100% /initrd/pup_ro2
/dev/loop4 17792 17792 0 100% /initrd/pup_ro4
unionfs 516040 32008 484032 7% /
tmpfs 255768 88 255680 1% /tmp
shmfs 185472 0 185472 0% /dev/shm
//192.168.1.100/SOURCES
19862528 6597120 13265408 34% /root/mnt
# mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,username=xxx,password=
# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 516040 32008 484032 7% /
/dev/sda5 12630768 5027344 7603424 40% /initrd/mnt/dev_save
/dev/loop1 516040 32008 484032 7% /initrd/pup_rw
tmpfs 129584 128716 868 100% /initrd/mnt/tmpfs
/dev/loop0 128640 128640 0 100% /initrd/pup_ro2
/dev/loop4 17792 17792 0 100% /initrd/pup_ro4
unionfs 516040 32008 484032 7% /
tmpfs 255768 88 255680 1% /tmp
shmfs 185472 0 185472 0% /dev/shm
//192.168.1.100/SOURCES
6982528 3528320 3454208 51% /root/mnt
//192.168.1.100/H-BCP
6982528 3528320 3454208 51% /root/mnt
#
Last edited by sheldonisaac on Mon 20 Dec 2010, 01:17, edited 2 times in total.
Try:
or
or
Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,username=xxx,password=xxx
Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON
Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,guest
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
OK, rcrsn51. You said I should try these 3; here's what happened-
First I did this:
It asked for a Password, I pressed Enter and it mounted.
I'll unmount and try the other two.
This worked, didn't ask for a password.
This also worked, didn't ask for a password.
And so did this work, didn't ask for a password.
First I did this:
Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON
I'll unmount and try the other two.
Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,username=xxx,password=xxx
Code: Select all
mount.cifs //192.168.1.100/H-BCP /root/mnt -o servernetbiosname=SHELDON,guest
And so did this work, didn't ask for a password.
Code: Select all
mount.cifs //SHELDON/H-BCP /root/mnt -o servernetbiosname=SHELDON,guest
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Thanks.rcrsn51 wrote:I have posted the new version samba-share-mount-1.3.pet at the start of the thread. Please give it a test and report back. Leave the Options field blank.
I hope more people can test and report.
The version 1.1 worked fine for me, and I was going to say I will take some time to do other things, for a while.
Version 1.3 gave the "No connection to xxx-share!"