OK, just to confirm I am indeed thick... So, let see if this is correct:

1. YASSM is a client, for connecting to ('mounting') samba AND samba-tng shares on OTHER PCs ...
2. And samba-tng-rcrsn-0.5-rc1 is purely for setting up a server, creating a 'share' that others can 'mount'...

I just installed Puppy Precise 5.4. I can access my shares from the other computers on my LAN but how do I create a share so that I can see it on my other machines. Do I use YASSM or do I have to download Samba Full or do I use Yassm instead?

I know how to set up a share in Puppy Linux 5.2.8 but am not sure how to do it in Precise. Thanks!!

I just installed Puppy Precise 5.4. I can access my shares from the other computers on my LAN but how do I create a share so that I can see it on my other machines. Do I use YASSM or do I have to download Samba Full?

YASSM is not a Samba server. It is a client app, like Pnethood. It does not create shares. It accesses the shares on other machines.

Quote:

I know how to set up a share in Puppy Linux 5.2.8 but am not sure how to do it in Precise. Thanks!!

I have been trying your YASSM in the latest Pups as pnethood is now mostly missing.

With YASSM, I found I could not mount the shares on my quite old XP computer (called 'DAD2' - from when my children were around - now it's grandchildren pushing buttons & keys!).

I/YASSM could see each share, listed by the drop-down button (e.g. MyDocuments@DAD2) but could not connect.

Reading your advice in some threads, I tried replacing "DAD2" as the Server option with the computer's network address (192.168.2.105 - it was manually set so should be a fixed address) and I could now access the shares.

What is your advice to make this accessing easier in future - rename the old desktop (e.g. is a lowercase name needed? Why is DAD2 a problem - pnethood worked as is) or can I set up a default to use the network address in some way in place of the DAD2 name?

This is a bit of a mystery. YASSM uses a different technique than Pnethood for resolving the server name DAD2 into its IP address 192.168.2.105. But since the nmblookup command above worked for you, I can't see why YASSM would fail.

Try this version

Code:

nmblookup DAD2 | tail -n 1 | cut -f 1 -d " "

Does it also return 192.168.2.105?

In any case, you can continue to use YASSM by using Samba-Select and building a list of your shares on DAD2. Just use the IP address in the list.

As a test, I named an XP machine as DAD2 and created a share named MyDocuments. I then accessed it from Slacko 5.5. Everything worked correctly.

and got "192.168.2.101" - which is the network address for this computer's wireless connection with XP.
It has wireless (101) and wired (105) connections.

Could this (2 addresses/2 adaptors) be the cause of the odd behaviour with YASSM on this old desktop? I could try turning one off (e.g. the wireless which can be a little erratic with XP - and I did not get YASSM to work using 192.168.2.101 in place of DAD2, whereas 192.168.2.105 did work)?

I only found the wired 192.168.2.105 connection yesterday with the nmblookup.
But trying again this morning, it did report both addresses (101 & 105). I suspect the wireless was temporarily off yesterday on the XP machine and I did not notice.

As I seem to be successfully learning about networking my now less-used Windows computers ( , thanks), I have a mainly dust-gathering Windows7 laptop.

When I try YASSM (& pnethood - I'm running a Upup Precise), the lap-top is found/reported but as "hidden@DAVIDLAPTOP-PC". It is connecting via its wireless adaptor at 192.168.2.8 - I had unplugged its wired connection quite a while ago.

In case you are a Windows7 expert, how do I unhide the Shares on this lap-top? I think I have tried everything in its Control Panel to make folders shared and public, but "who knows?"
I'm trying a few passwords and user names but with no luck nor skill (as suggested in your guide earlier (page1) in this thread).

Or should I re-establish the wired connection (if that was an issue with the XP computer difficulty)? Just need to find a cable to test this out.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum