(old)Puppy Linux Discussion Forum

Still all good here running v4.1 with a single retry, I switched the samba server over to X-Slacko 4.3 from the LxPupSc 17.08.23 I tested with first, doing a fresh frugal install as the X-Slacko savefile was getting pretty shopworn. In short and overnight tests v4.1 found and connected every time. The process is indeed faster than the full search in Yassm-search by a couple of seconds on this network and setup.

Thanks,

Marv wrote:... with a single retry...

Please explain. Are you using the unmodified version of 4.1?

Was your original report of "Server not found" a fluke?

I have posted a new v4.1 that sets RETRIES=4 on line 6.

rcrsn51 wrote:

Marv wrote:... with a single retry...

Please explain. Are you using the unmodified version of 4.1?

Was your original report of "Server not found" a fluke?

I have posted a new v4.1 that sets RETRIES=4 on line 6.

I am using the unmodified 4.1. I have never had a "Server not found" with it. What I said a few posts up was that I would look for that failure. It never has occurred with the unmodified 4.1. I have tested with samba under X-Slacko and LxPupSc so far. Since I haven't had any failures I haven't yet updated to the multiple retry version.

OK. I misunderstood this statement:

Both the PcManFm in the LxPups and the Thunar in the X- series can connect to the shares but after a period of non-use even though the server box doesn't hibernate or sleep they sometimes fail to connect. Yassm-search always has

Were you referring to the built-in Samba client tools in PcManFm?

IIRC, there were reports by LxPup users that they needed additional wake-up procedures to make previous YASSMs work. But this may be a non-issue with v4.1, especially with the increased RETRIES value.

Bill

rcrsn51 wrote:Were you referring to the built-in Samba client tools in PcManFm?

IIRC, there were reports by LxPup users that they needed additional wake-up procedures to make previous YASSMs work. But this may be a non-issue with v4.1, especially with the increased RETRIES value.

Bill

Yes, it was the built-in client tools. Since I have been using Yassm-search exclusively for quite a while I really don't know if they have changed/improved over time.

Both Yassm-search and now Yassm v4.1 have worked extremely reliably over many LxPups for me on a fairly wide variety of hardware. IIRC also there were some wakeup problems with Yassm not using the -search option. I'll update to the current 4.1 and continue to use it later today.

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