Page 3 of 10
Posted: Tue 04 Jan 2011, 13:36
by drblock2
This is a wonderful little pet. It works perfectly on my Windows XP LAN.
Can anyone tell me if it is possible to use Samba to share files between machines running puppy? I use ftp for this now, but this is much more limited than actually mounting the remote drive.
Posted: Tue 04 Jan 2011, 13:46
by rcrsn51
drblock2 wrote:Can anyone tell me if it is possible to use Samba to share files between machines running puppy? I use ftp for this now, but this is much more limited than actually mounting the remote drive.
You need to install a Samba server package on one of your Puppies. My favourite is
Samba-TNG.
Out of curiosity, does your Windows LAN use simple file sharing with open shares or the more complicated version with password security?
Posted: Tue 04 Jan 2011, 16:36
by drblock2
My Windows LAN uses simple file sharing with open shares.
One interesting observation. If I mount via samba share select, the path to the mounted file system goes via /root/samba. If I mount with pnethood, the path is direct, e.g., /mnt/network/host/share, whereas the samba share select mount has the path /root/Samba/share. This is somewhat inconvenient as the user has to keep this "small detour" in mind when accessing the share with the command line or a file manager.
This should, perhaps, be mentioned in the instructions.
Thanks for the link to Samba-TNG. I will experiment with this asap. This is, I think, very important. It is one thing to maintain compatibility with Windows because we have to deal with Windows computers and quite another to have to rely on ftp because there is no other way for puppy computers to talk to one another.
Posted: Tue 04 Jan 2011, 16:50
by rcrsn51
One interesting observation. If I mount via samba share select, the path to the mounted file system goes via /root/samba. If I mount with pnethood, the path is direct, e.g., /mnt/network/host/share, whereas the samba share select mount has the path /root/Samba/share. This is somewhat inconvenient as the user has to keep this "small detour" in mind when accessing the share with the command line or a file manager.
This should, perhaps, be mentioned in the instructions.
It is:
Samba-login uses the folder /root/Samba to hold the mount points.
This was a matter of personal preference on my part. If, when using pnethood, I close the share window, I then have to drill all the way down into /mnt/network to open it again. It seemed much simpler to put the mount points in /root. Most applications start their File>Open dialog there.
yassm
Posted: Sat 12 Feb 2011, 14:41
by kennardly
Is there a way to auto mount the shares at boot ?
Thanks for any response.
Love puppy linux!
Posted: Thu 15 Sep 2011, 18:00
by rcrsn51
Deleted.
Re: Yet Another Samba Share Mounter
Posted: Fri 17 Feb 2012, 20:50
by keith_moon
I can't download the pet. Is the download link still valid?
Posted: Fri 17 Feb 2012, 21:32
by Makoto
It's hosted locally on the forum, so, yes, the link should still be valid. However, there's currently an issue or two with the forum (you may have noticed 'garbage' appearing at the top of a page or two, for example), that appears to be interfering with things like the post attachment above. Hopefully, it'll all be sorted, soon.
Posted: Sun 19 Feb 2012, 17:42
by sebus
It also works fine on Fatdog64, thanks
sebus
Posted: Tue 10 Jul 2012, 01:58
by rcrsn51
YASSM v2.2 is posted on Page 1.
Posted: Tue 10 Jul 2012, 03:36
by Geoffrey
YASSM v2.2 don't run in Saluki, I tried YASSM v2.1 and it works fine, I get this message with v2.2
Posted: Tue 10 Jul 2012, 10:45
by rcrsn51
Please type the command "iproute" and report the results.
Posted: Tue 10 Jul 2012, 13:58
by Geoffrey
rcrsn51 wrote:Please type the command "iproute" and report the results.
Code: Select all
# iproute
default via 10.1.1.1 dev eth0 metric 202
10.0.0.0/8 dev eth0 src 10.1.1.11 metric 202
127.0.0.0/8 dev lo
Posted: Tue 10 Jul 2012, 14:32
by rcrsn51
Thanks. What is the IP address of the server you are looking for?
Now try:
Does this find the server? (You may have to kill this command.) If not, use
or
Posted: Tue 10 Jul 2012, 15:09
by Geoffrey
rcrsn51 wrote:Thanks. What is the IP address of the server you are looking for?
I have 3 nas units ip 10.1.1.2, 10.1.1.3, 10.1.1.7
only the 10.1.1.3 is running to test with
Code: Select all
# nbtscan -q 10.0.0.0/8
# nbtscan -q 10.0.0.0/16
# nbtscan -q 10.1.1.0-254
10.1.1.3 REPOTEC <server> REPOTEC 00-00-00-00-00-00
using fping
Code: Select all
LAN IPs found:
10.1.1.1
10.1.1.3
10.1.1.8
Local IP: 10.1.1.11
Posted: Tue 10 Jul 2012, 15:36
by rcrsn51
Posted: Tue 10 Jul 2012, 16:13
by Geoffrey
rcrsn51 wrote:Thanks. One more:
That gave no result
Posted: Tue 10 Jul 2012, 16:36
by rcrsn51
Thanks. If you run Pnethood from another Puppy (Saluki doesn't have it) can it find your NAS boxes?
Posted: Wed 11 Jul 2012, 03:27
by Geoffrey
rcrsn51 wrote:Thanks. If you run Pnethood from another Puppy (Saluki doesn't have it) can it find your NAS boxes?
With Pnethood I've never had a problem with other puppy's using a network scan of 3 seconds, Saluki has pnethood but I need to adjust the network scan to 6 seconds then it finds the servers.
I have had this problem with lameSMBxplorer, I was never was able to get it to function correctly, it also had issues with ip's in the 10.1.1.0 range and netmask 255.0.0.0, this was discussed here
http://murga-linux.com/puppy/viewtopic. ... 033#440033.
Don't pull your hair out over it, your version 2.1 works fine and it's easier for me to set the shares manually, the only time it's a pain is if someone arrives with a device that I wish to access, but a quick fping scan will find any new ip's.
Posted: Wed 11 Jul 2012, 04:46
by rcrsn51
Thank you for this testing - it has been extremely valuable. I had made some incorrect assumptions about how people set up home networks.
I was surprised that "nbtscan -q 10.1.0.0/16" did not find your NAS boxes, because I believe that's how Pnethood does it. But maybe "nbtscan -q -t 3000 10.1.0.0/16" would work.
It's interesting that "nbtscan -q 10.1.1.0-254" did work with the default 1 second time interval.
I will be releasing a YASSM v2.3 shortly.
Bill