Author Topic: Samba 4.9.0 based client  (Read 3866 times)

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 53
  • Posts: 446
    • View Profile
Samba 4.9.0 based client
« on: September 15, 2018, 10:22:45 am »
Hi All,

Updated Samba client build for testing - seems OK here - both smbclient.exe and ndpsmb.dll have been tested.

Netdrive plugin (depends on smbcln49.dll for samba libraries support) - http://smedley.id.au/tmp/ndpsmb-3.5-samba49-20180915.zip

Samba client libraries and associated utilities:http://smedley.id.au/tmp/smbcln49-4.9.0-20180915.zip

As per previous builds, these also need an ldap.dll from openldap (openldap-2.4.46-os2-20180428.zip) and the heimdall DLL's (heimdal-7.5.0-os2-20180225.zip)

Feedback appreciated!

Paul

David McKenna

  • Full Member
  • ***
  • Thank You
  • -Given: 8
  • -Receive: 9
  • Posts: 207
    • View Profile
Re: Samba 4.9.0 based client
« Reply #1 on: September 16, 2018, 05:38:20 am »
 Thanks, Paul! Got it installed and so far seems to work well with my OS/2 SAMBA server. I'll try some Windows shares next...

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 53
  • Posts: 446
    • View Profile
Re: Samba 4.9.0 based client
« Reply #2 on: September 16, 2018, 11:49:48 am »
Thanks, Paul! Got it installed and so far seems to work well with my OS/2 SAMBA server. I'll try some Windows shares next...

Great, seems to be working fine here connecting to a linux Samba 4.8.x server...

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 53
  • Posts: 446
    • View Profile
Re: Samba 4.9.0 based client
« Reply #3 on: March 24, 2019, 02:56:27 am »
Updated client libs to Samba 4.9.5 at http://smedley.id.au/tmp/smbcln49-4.9.5-20190324.zip

I also built 4.10.0
Client libs: http://smedley.id.au/tmp/smbcl410-4.10.0-20190324.zip
Netdrive plugin: http://smedley.id.au/tmp/ndpsmb-3.6-samba410-20190324.zip

I've had smbd.exe and nmbd.exe compiling for some time - I hadn't previously commented on this, as I hadn't considered it announcement worthy as they don't work, but given others think announcing they have code for an obsolete version of samba server compiling but not working is worthwhile, I thought I'd mention it.

Cheers,

Paul

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 560
    • View Profile
Re: Samba 4.9.0 based client
« Reply #4 on: March 24, 2019, 02:51:44 pm »
Paul,

Thanks for the always great work, but I've got to ask this question (well, a couple of them anyways):

1) How do your releases compare to the official RPM packages (because I was originally using your ZIP stuff, then moved over to RPM, which I was under the impression you were doing, or at least helping out with???) I have samba-client.i686 (4.9.4-4.oc00) currently installed.

2) In this last post you show the 4.9.5 and 4.10.0, is there a particular version we should pursue?

3) NetDrive plug-in, is this to be used ONLY with the 4.10.0 client judging by the fact that you have lumped with the 4.10.0 release?

-Dariusz
« Last Edit: March 24, 2019, 02:58:21 pm by Dariusz Piatkowski »

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 53
  • Posts: 446
    • View Profile
Re: Samba 4.9.0 based client
« Reply #5 on: March 24, 2019, 10:03:31 pm »
Hi Dariusz,

Thanks for the always great work, but I've got to ask this question (well, a couple of them anyways):

1) How do your releases compare to the official RPM packages (because I was originally using your ZIP stuff, then moved over to RPM, which I was under the impression you were doing, or at least helping out with???) I have samba-client.i686 (4.9.4-4.oc00) currently installed.

2) In this last post you show the 4.9.5 and 4.10.0, is there a particular version we should pursue?

3) NetDrive plug-in, is this to be used ONLY with the 4.10.0 client judging by the fact that you have lumped with the 4.10.0 release?

1) For ArcaOS - Lewis will end up packaging 4.9.5 as a rpm. I mainly provided these links for non-ArcaOS users, who people who like to live on the cutting edge :P

2) 4.9.5 is a bug fix for the 4.9.x series, 4.10.0 is the next feature update for Samba. I'd consider 4.9.x more mature, but would welcome feedback on 4.10.x

3) Currently, ndpsmb.dll releases are paired with a specific samba support DLL, so it's important to use them as a matched pair.

Hope this helps,

Paul

David McKenna

  • Full Member
  • ***
  • Thank You
  • -Given: 8
  • -Receive: 9
  • Posts: 207
    • View Profile
Re: Samba 4.9.0 based client
« Reply #6 on: March 25, 2019, 01:32:42 am »
 Hi Paul!

 I installed your 4.10 versions and they seem to work just fine so far in light testing. I'll post if any problems show up.... thanks again for your Olympian support of OS/2!  ;D

Regards,

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 53
  • Posts: 446
    • View Profile
Re: Samba 4.9.0 based client
« Reply #7 on: March 25, 2019, 02:59:08 am »
Hey David,

I installed your 4.10 versions and they seem to work just fine so far in light testing. I'll post if any problems show up.... thanks again for your Olympian support of OS/2!  ;D

Thanks mate, I've been really slack updating the public facing website (https://os2ports.smedley.id.au) over the last couple of years, I really must spend a few hours updating it with stuff that has accumulated in http://smedley.id.au/tmp/* :)

Cheers,

Paul

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 560
    • View Profile
Re: Samba 4.9.0 based client
« Reply #8 on: March 25, 2019, 11:10:07 pm »
Hi Paul,

Hi Dariusz,

Thanks for the always great work, but I've got to ask this question (well, a couple of them anyways):

1) How do your releases compare to the official RPM packages (because I was originally using your ZIP stuff, then moved over to RPM, which I was under the impression you were doing, or at least helping out with???) I have samba-client.i686 (4.9.4-4.oc00) currently installed.

2) In this last post you show the 4.9.5 and 4.10.0, is there a particular version we should pursue?

3) NetDrive plug-in, is this to be used ONLY with the 4.10.0 client judging by the fact that you have lumped with the 4.10.0 release?

1) For ArcaOS - Lewis will end up packaging 4.9.5 as a rpm. I mainly provided these links for non-ArcaOS users, who people who like to live on the cutting edge :P

2) 4.9.5 is a bug fix for the 4.9.x series, 4.10.0 is the next feature update for Samba. I'd consider 4.9.x more mature, but would welcome feedback on 4.10.x

3) Currently, ndpsmb.dll releases are paired with a specific samba support DLL, so it's important to use them as a matched pair.

Hope this helps,

Paul

I installed the stuff Lewis released, so far so good, no hiccups. Will do a bit more of file/folder creation testing later on and will report back.

Once I have this stable I will take a stab at the 4.10.0 stuff...

Thanks, as always!
-Dariusz

mauro

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 2
  • Posts: 160
    • View Profile
Re: Samba 4.9.0 based client
« Reply #9 on: May 28, 2019, 12:23:53 pm »
Hi Dariusz,

.....................

1) For ArcaOS - Lewis will end up packaging 4.9.5 as a rpm. I mainly provided these links for non-ArcaOS users, who people who like to live on the cutting edge :P

2) 4.9.5 is a bug fix for the 4.9.x series, 4.10.0 is the next feature update for Samba. I'd consider 4.9.x more mature, but would welcome feedback on 4.10.x

3) Currently, ndpsmb.dll releases are paired with a specific samba support DLL, so it's important to use them as a matched pair.

Hope this helps,

Paul

Hi Paul, if still ontime I'd like to enquiry the following which maybe -hopefully- could unlock my situation in having NetDrive with samba plugin working .
I had opened a thread before here https://www.os2world.com/forum/index.php/topic,2064.15.html#lastPost and have been brilliantly supported by Sean Casey, who brought me to a good point, but at the last step had discontinued to respond, maybe for no more suggestion available.

Have intalled Samba 4-9-5 rpm from Arca subscription repository on my OS2 Warp 4.52, installation went appearently well, so if I give the following command in an OS2 window

smbclient \\xxx.xxx.xxx.xxx\yyyyy  (it is my Windows 10 Users resource, Windows 10 is the hosting OS of my guest OS2 Warp 4.52 on Virtualbox)

I obtain the following :

gethostname failed
gethostname failed
Enter WORKGROUP\GUEST's password:

give enter again (no password to input) and I get this :

Try "help" to get a list of possible commands.
smb: \>

then I command
smb: \> dir

and the requested resource make its directories available

  .                                  DR        0  Sat Jul  7 13:06:16 2018
  ..                                 DR        0  Sat Jul  7 13:06:16 2018
  Default                           DHR        0  Wed Sep 26 20:29:58 2018
  Default.migrated                    D        0  Sun Sep  4 19:20:29 2016
  desktop.ini                       AHS      174  Sat Jun 16 17:26:53 2018
  Public                             DR        0  Wed Sep 26 20:28:39 2018
  user                                D        0  Sun Jul 31 08:38:03 2016

                239907945 blocks of size 4096. 178492899 blocks available
smb: \>


this seems indicating Samba client working.

But I'm unable then to make NetDrive and its Samba plugin get working on same resource, after having mounted a resource drive letter and filled the smbfs plugin configuration fields in the table with same parametres of the OS2 Samba client command, it just gives back an error alert, this is also displayed in the other mentioned thread.

If there is no other clear reason for this issue (I mainly believe I'm doing something wrong, being not much experienced in this kind of application), can it be due to the fact that Samba 4.9.5 is not working specifically for OS2 Warp 4.52 ?  Or maybe I'm using a samba plugin version (2.1.5 GA) for NetDrive which someway conflicts with this Samba client version?
Thank you -at least for having read till now-
« Last Edit: May 28, 2019, 12:34:25 pm by mauro »

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 34
  • Posts: 978
    • View Profile
Re: Samba 4.9.0 based client
« Reply #10 on: May 28, 2019, 01:47:39 pm »
It sounds as if your win 10 is the problem.  For supposed security reasons win 10 CIFS/SMB defaults to version 2 and I think that our CIFS/SMB is version 1.  We have been seeing a lot of problems on the D-Link NAS forums where people with win 10 find they are unable to connect to the NAS CIFS/SMB because the NAS uses the 'old' v1 and win uses the 'new' v2.  There should be a setting in win10 that allows you to set CIFS/SMB back to v1.

mauro

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 2
  • Posts: 160
    • View Profile
Re: Samba 4.9.0 based client
« Reply #11 on: May 28, 2019, 03:17:09 pm »
It sounds as if your win 10 is the problem.  For supposed security reasons win 10 CIFS/SMB defaults to version 2 and I think that our CIFS/SMB is version 1.  We have been seeing a lot of problems on the D-Link NAS forums where people with win 10 find they are unable to connect to the NAS CIFS/SMB because the NAS uses the 'old' v1 and win uses the 'new' v2.  There should be a setting in win10 that allows you to set CIFS/SMB back to v1.

Hi, it seems I've succeeded to make the proper adjustment under Windows 10 after having applied Sean Casey suggestion; while before I could not obtain any smb> prompt in an OS2 window, now the command line get the correct output from the called Win 10 resource, which should indicate it is working and I could manage everything from there if I were smart enough whith OS2 commands, unfortunately I'm not that good.

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 53
  • Posts: 446
    • View Profile
Re: Samba 4.9.0 based client
« Reply #12 on: May 29, 2019, 11:33:50 am »
Hi,

It sounds as if your win 10 is the problem.  For supposed security reasons win 10 CIFS/SMB defaults to version 2 and I think that our CIFS/SMB is version 1.  We have been seeing a lot of problems on the D-Link NAS forums where people with win 10 find they are unable to connect to the NAS CIFS/SMB because the NAS uses the 'old' v1 and win uses the 'new' v2.  There should be a setting in win10 that allows you to set CIFS/SMB back to v1.

Hi, it seems I've succeeded to make the proper adjustment under Windows 10 after having applied Sean Casey suggestion; while before I could not obtain any smb> prompt in an OS2 window, now the command line get the correct output from the called Win 10 resource, which should indicate it is working and I could manage everything from there if I were smart enough whith OS2 commands, unfortunately I'm not that good.

Agree that if smbclient can view the windows 10 share, then ndpsmb should be able to as well.

Logs will help us understand what's happening.

Create a file ndpsmb.dbg in the root directory of the drive where netdrive is installed. Restart ndctl (or reboot).

try and access your windows 10 share - and after, send me a copy of ndpsmb.log (not sure where this will get created on a Warp 4 install).

Cheers,

Paul

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 560
    • View Profile
Re: Samba 4.9.0 based client
« Reply #13 on: May 30, 2019, 03:45:05 am »
...
Logs will help us understand what's happening.

Create a file ndpsmb.dbg in the root directory of the drive where netdrive is installed. Restart ndctl (or reboot).

try and access your windows 10 share - and after, send me a copy of ndpsmb.log (not sure where this will get created on a Warp 4 install).
...

On my machine (Warp 4.52 install) this goes where "SET LOGFILES=" in my CONFIG.SYS points to.

mauro:
Can you post the specific versions of the installed components you have?

I have been almost exclusively using NetDrive to access all of my LAN shares, that's across Linux based NAS box, Win7 and Win10 machines. It is working fine for the most part, there is an annoying problem with the shares just "going away", a NDCTL re-start usually fixes that though...never been able to pin-point what causes that issue though.

Anyways, happy to give you a rundown of what I have here:

Code: [Select]
Samba Client Versions:
File system NDFS32 Version 3.028
Plugin file G:\UTIL\NDFS\NDPLUGS\NDPSMB.DLL]
Plugin Vendor netlabs
Plugin Revision 3.05.0
Plugin Date/Time 3 Jan 2019 15:59:04
Plugin Build Machine ARCAOS-D0C2
Plugin Language Code en
Plugin File Version 3.5
Plugin Description NDPSMB - SMBFS NetDrive External Plugin Build 20180916
Commandline utilities Version 3.0.37-eCS 1.0.6-565
EVFSGUIVersion 2.5.RC7-[2014-11-14]

I picked up this handy dump from the EVFSGUI utility. The NetDrive itself is version 3.1.6.876.

The support packages I have deployed (to specifically give NetDrive the Samba plugin functionality) are:
1) samba-client.i686 - 4.9.5-1.oc00
2) heimdal.i686 - 7.6.0-0.oc00
3) heimdal-libs.i686 - 7.6.0-0.oc00
4) ndpsmb-3_5_0-GA-20190103.wpi (which was a AN test build, maybe a GA by now?)




ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 34
  • Posts: 978
    • View Profile
Re: Samba 4.9.0 based client
« Reply #14 on: May 30, 2019, 02:04:46 pm »
Hi Dariusz,

You have me scratching my head with your list of support packages. 

What is heimdal and what does it do? 

I checked my ArcaOS test bed and while it has a directory of that name said dir is empty so no help there.  Do I need it since my CIFS/SMB access to all my NAS boxes is good?