Hi Paul,
...Sorry - I'm confused - how exactly did you resolve your issues? Backlevelling ndpsmb.dll and matching smbclnxx.dll? I'd rather fix the issue in current builds if it still exists...
Well, I simply reverted back to the smbclut-1_3_0-1054.zip package and made no other changes to the NetDrive samba plugin, I left that as it was, with the bldlevel info I showed in my last update.
Some months ago you made some changes to the NetDrive plugin based on the issues I was experiencing. I deployed that setup, the last set of filenames I deployed were:
1) ndpsmb-3.2-samba46-20170317.zip
2) ndpsmb-fix1.zip
...with #2 being the last test release you made, which addressed the issues I was seeing on my system. I left things that way, probably expecting that eventually you (or bitwise works?) would release the final version. Not sure if that ever happened, maybe it did and I missed it?
More importantly, I am confused as to which is the proper set of CLUs to use:
1) smbclut-1_3_0-1054.zip
OR
2) smbcln46-4.6.0-20170312.zip
I am NOT running an OS/2 Samba server, only client, so given the description at the Samba wiki (
http://trac.netlabs.org/samba/wiki), I ended up using smbclut-1_3_0-1054.zip.
In your previous post you listed two files, which I downloaded and will test out. However, I am still confused whether smbcln47-4.7.7-20180428.zip or smbclut-1_3_0-1054.zip should be used for a client-only install?
As best as I can tell it all comes down to which version of Samba client the particular CLU implements, right now, given the latest releases discussed here, these are:
1) smbclut-1_3_0-1054.zip (Version 3.6.25-OS/2 and OS/2-based systems v1.3.0-1054)
2) SMBCLN47-4.7.7-20180428 (Version 4.7.7)
Now, maybe if you are running an OS/2 server that matters a lot, which is perhaps why the wiki says they officially ONLY support the 3.6.25 release. But if all you want is the Samba client, does that open things up to running something like your latest test relase above, which is 4.7.7?
I will test this out and report back.