(old)Puppy Linux Discussion Forum

Excellent. I'm hoping that RETRIES=4 should be enough to wake up a sleepy server.

There were old reports that you had to hit the server with a ping before YASSM would see it.

I just can't get it to work. Seems like to many steps to find shares. I can connect other ways with less input and me having to know a lot of ip's or shares. Want to press a button let it search out then I select. This v4.1 I just can not get working. Most programs I get to work.

What I am I doing here wrong to make it so complicated?

rockedge wrote:What I am I doing here wrong to make it so complicated?

YASSM v4.1 is based on this idea: once you have found something, why keep searching for it? This is the same principle you apply when you make a bookmark in your web browser.

But there is a learning curve to making these YASSM "bookmarks". Have you read the new instructions on Page 1? If they are confusing, I will try to make them less so.

Have you checked if root user and password woofwoof is still used in your new install.

From my own experience, the common problem is

So I go to the machine running the server software and run but then samba needs to be restarted to recognize a new user.
______________________________________________

don570 wrote:Have you checked if root user and password woofwoof is still used in your new install.

YASSM is Samba CLIENT software - it doesn't create users.

Smbpasswd is a command that you would use on a machine running a Samba SERVER.

I have YASSM (2.9 and 4.1 checked) now running with post 4.13 kernels (It was a mount.cifs issue discussed in the LxPupSc thread). With post 4.13 kernels, mount.cifs requires an explicit SMB version option to run. A command line example is: It can be passed as an option in YASSM, png attached below. I'm running samba 4.4.14 in LxPupSc 17.09.24 as the server currently and SMB2.1 is the maximum protocol level I have gotten to run. 2.1 works reliably. So far the client side (YASSM and CLI mounts) just tested in LxPupSc 17.11.1 with kernels 4.13.10 and 4.13.11 but seems solid. Glad to have YASSM back in the pups with post 4.13 kernels. I'll test in XFCE-XenialPup64 r4 tomorrow.

Thanks for solving this problem. I will make a note in the main post.

Two additional tests run. YASSM (and mount.cifs) work correctly in XFCE-XenialPup64 r4 with kernel 4.13.3.
The vers=2.1 option and the samba server referenced above were used.

I also switched the pup running the samba server to the latest LxPupSc (17.11.1 1T with the 4.13.11 kernel and the same 4.4.14 samba software). vers=3.0 is now supported as well as vers=2.1.

Note the discussion here where p310don also needed the option with an older Windows share.

At the moment, are the only choices 1.0, 2.1 or 3.0?

Running the latest LxPupSc (17.11.1 1T with the 4.13.11 kernel and 4.4.14 samba software), 3.1 or 3.2 were not supported so yes, I'm pretty sure at this time 1.0, 2.1, and 3.0 are the only valid options. Someone running and versed in the newest 64 bit pups and samba setup would have to double check that but the 4.13.11 kernel in that LxpupSc is 64b and that seems to be the determining factor so I would be surprised if anything higher than 3.0 was supported in the 64b pups either.

Dear @rcrsn51

Your latest YASSM-4.1 failed to load smb shares for the synology's shares (newest OS based on Linux) on Tahrpuppy i386 while version 2.7 could do this without any.. trouble.. just 20 minutes ago )

Then I got another issue while uninstalling YASSM-4.1. It's funny, but I couldn't do it until repaired a bug in ppm's (Puppy Package Manager) script called removemodes.sh.. LOL!

It happened (ppm just got hung) 'cause your pet file is named only with UPPERcase characters that leads to the fault like "couldn't devide by zero" in ppm script, line 141. So I've changed [a-z] onto [A-Z,a-z] for the $TOTAL in the line 132 to make ppm delete the package.

Funny bug but nevertheless! BTW who is responsible for PPM to point on the bug.

thx

@takenp, I use an older YASSM version and I can mount Sinology shares. If it's a new DSM version you're using, you might need to add "vers=1.0" to the YASSM Options field. I didn't find it necessary to set the other configuration options that rcrsn51 listed in the first post of this thread.

Hell0 rcrsn51
Yassm in Stretch 7.5 connect problem.

I have two networks as follows:
wired network on 192.168.254.x
wireless network on 192.168.1.x

My file server is on the wired network on static address: 192.168.254.7
My laptop is on the wireless network at 192.168.1.106. Here are my test results:

laptop>precise 5.7.1>192.168.1.106>yassm=connect
laptop>slacko 6 .3.0>192.168.1.106>yassm=connect
laptop>stretch 7.5>192.168.1.106>pnethood=connect
laptop>stretch 7.5>192.168.1.106>yassm=server not found
laptop>stretch 7.5>192.168.254.106>yassm=connect

I have tried using options "vers=" with values of 1.0, 2.1 & 3.0 but still
no connect

Note the last test when the laptop is moved to the same network as the server, Stretch 7.5 yassm does connect even with no options given.

Try v4.2 attached on the main post.

When you click Set, you will get the message "MAC address not found" because the server is on the other subnet.

But you should be able to mount the share.

success, version 4.2 connects.

thanks
Gary

Excellent.

Here is the situation: Samba client apps use a variety of search tools - nbtscan, mpscan, nmblookup. YASSM v4.x replaces them with a single tool - arp-scan.

Unfortunately, arp-scan only works on the local subnet. It is not routable across to another subnet like in your situation.

So I replaced some of the arp-scan calls with pings, which are routable.

I don't think that there is any penalty for doing this, but it needs more testing and feedback.

Thanks for the explanation, makes me smarter

Gary

Dear @rcrsn51

Bionicpup_64/Tahrpup_32 with Samba Simple Management and YASSM:


YASSM 2.7 and 2.9

search works (it is convenient!)
mount works


YASSM 4.1

no search (have to type in all fields manually)
mount does not work!

It says: "Server 192.168.88.35 not found!"

I checked with bash and it works:
So I rolled back to 2.9 and ask a question: where I am wrong?

thx!

takenp wrote:Dear @rcrsn51

Bionicpup_64/Tahrpup_32 with Samba Simple Management and YASSM:

Just as bit of a BTW:
I have made my own samba share mounter script.
It is not really ready for prime time but something I did may be useful.
I discovered that on a dodgy network, sometimes machines are not seen by any method. Basically any machine may come and go at any time. But on the average it is there more than 50% of the time. Sometimes it appears that network traffic made the machine start paying attention again.

I "solved" the problem with the following things:

1) I always scan the network twice
2) In /tmp I save the results
3) If the previous results in /tmp don't match this time I try a bit more
4) I have a "server not seen" option in the server selection list

The network I was using when I did this had some Win10 machines that were not working right along with some things doing UDP and WiFi connections that were getting jammed. In other words a complete "pigs breakfast" of a network. My mounter still worked on this mess.