OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: mauro on April 23, 2019, 10:19:42 am

Title: Samba client on OS2 Warp 4.52
Post by: mauro on April 23, 2019, 10:19:42 am
Hi all, I've seen that a few packages have been introducted on Arcanoae subscription repository, and Samba Client Utility among them.
I do not have a strong knowledge on what it could be useful for, I just presume that it could be good to implement the browsing of the volumes belonging to my  host pc HD (being OS2 running on VirtualBox), or else other pc connected in my domestic lan.
Could someone help me in understanding more?
Thank you
Title: Re: Samba client on OS2 Warp 4.52
Post by: Martin Iturbide on April 23, 2019, 02:39:48 pm
Hi Mauro.

I use the Samba client to copy files from:
-  a Windows 10 machine on my network to the ArcaOS Box (and viceversa)
- a Windows 10 machine on my network to my ArcaOS VM  (and viceversa) (Even if Windows 10 is the host).
- a Network hard drive.

I'm not a Samba power user, I don't know how to use the commands, I just mount the drive with Arca Mapper.

Regards
Title: Re: Samba client on OS2 Warp 4.52
Post by: Dariusz Piatkowski on April 23, 2019, 11:59:29 pm
Hi mauro,

Martin provided a pretty good explanation.

I have been using NetDrive for some years now. You can access various types of storage through plug-ins, in the case of Samba the NetDrive has a Samba plug-in, which in turn requires that a Samba client is present on your local machine.

In my case that allows various disks mounted across my various computers on the LAN to be visible on my local OS/2 machine, as if they were local drives. In particular though I am heavily using this functionality to access our NAS, which is really where I am pushing everyone in my household to start storing their documents.

Of course you do not neet NetDrive to use Samba client, you can do it from CLI as well, just a little more troublesome, that's all.
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on April 24, 2019, 08:20:47 am
Ok, thank you Martin and Dariusz, I understood would be easier having NetDrive to handle with Samba Client installed.
I just saw that is a shareware, it costs 29$ to to use it,  but also read this point (below) in terms & conditions which would state a free utilization if limited to Samba plugin only, that would apply to my case, am I right?

Using NetDrive for OS/2 exclusively with the Samba plugin removes the
restrictions imposed by the Shareware License but does not convert
NetDrive for OS/2 to the registered version. Specifically, using NetDrive
for OS/2 exclusively with the Samba plugin under this Exclusive Samba Use
License does not entitle the user to the Developer support provided for
the registered version of NetDrive for OS/2 under the Shareware License.
Title: Re: Samba client on OS2 Warp 4.52
Post by: Dariusz Piatkowski on April 24, 2019, 05:25:58 pm
Hi mauro,

...I just saw that is a shareware, it costs 29$ to to use it,  but also read this point (below) in terms & conditions which would state a free utilization if limited to Samba plugin only, that would apply to my case, am I right?...

I was not aware of this, but that's a pretty awesome way to let folks try things out. I have used it for other access such as mapping into a ISO file, to FTP or NFS shares. So given that I was going to use it across numerous applications I just went ahead and purchased the license. For the sort of functionality it delivers I thought it was a very reasonable cost.

Try it out first and go from there!
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on April 25, 2019, 07:48:42 pm
ok installed Samba client and NetDrive, started NetDrive I have a blank panel…..can you lead me on the right way to get a shared resource (i.e my other volume on the system), or maybe I have to separately add the proper plugin?
Thanks

Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on April 26, 2019, 03:55:02 am
Hi,

You will also need to install the smb NetDrive plugin.   You can find it here: http://trac.netlabs.org/samba

Once installed, use the NetDrive Volume menu and select "Attach New Volume" menu option.  You will then elect a drive letter to assign your mount point.

With your mount point highlighted within NetDrive, select the Resource menu and the "Mount Resource" menu option. You will be presented with a screen where you should see the option of "smbfs" which is your samba plugin you installed.   

Clicking the "Properties" button will present a screen where you identify your smb workgroup, server, share name, and login credentials.  Once you complete these entries and click the Done button, you will then have your mount point defined and it should be mounted and ready for use.

To save these settings for future use, select the NetDrive menu and the Volume Configuration Save option. 

If you ever lose your mount point due to network issues, you can restart NetDrive by selecting the NetDrive menu, and Control Program Start option.

Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on April 26, 2019, 03:30:19 pm
thank you Sean, the netlabs url linking to the Samba Netdrive plugin (both 3.3.16  and  3.5.21 beta4) point to 404 message pages, but now found this file by Paul Smedley at

https://ecsoft2.org/client-samba-plugin-netdrive-o-evfsgui

so I got the zip file
http://smedley.id.au/downloads/ndpsmb-3.6-samba410-20190324.zip

containing only ndpsmb.dll and ndpsmb.map, no readme for installation instruction. 

the quick manual inst reference on the EcSoft/2 page says "unzip the downloaded plugin archive to an empty directory and run instpl.cmd" but there is no such file in the zip archive
Am I supposed to just place those two files in the OS2/DLL directory ?
Title: Re: Samba client on OS2 Warp 4.52
Post by: Andreas Schnellbacher on April 26, 2019, 03:54:30 pm
thank you Sean, the netlabs url linking to the Samba Netdrive plugin (both 3.3.16  and  3.5.21 beta4) point to 404 message pages
This link from http://trac.netlabs.org/samba (http://trac.netlabs.org/samba) works for me:
ftp://ftp.netlabs.org/pub/samba/client/ndpsmb-2_1_5-GA-20131003.wpi (http://ftp://ftp.netlabs.org/pub/samba/client/ndpsmb-2_1_5-GA-20131003.wpi)
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on April 26, 2019, 04:02:35 pm

This link from http://trac.netlabs.org/samba (http://trac.netlabs.org/samba) works for me:
ftp://ftp.netlabs.org/pub/samba/client/ndpsmb-2_1_5-GA-20131003.wpi (http://ftp://ftp.netlabs.org/pub/samba/client/ndpsmb-2_1_5-GA-20131003.wpi)

I believe there is a wrong URL prefix address handling on my browser, since it anyway begins in the address field as "http://ftp://ftp..............."
Title: Re: Samba client on OS2 Warp 4.52
Post by: Andreas Schnellbacher on April 26, 2019, 04:14:47 pm
I believe there is a wrong URL prefix address handling on my browser, since it anyway begins in the address field as "http://ftp://ftp..............."
You're right. I remember that some links here in this forum don't work. Likely ftp:// links are affected. Try the links on the trac web page. That's the one I've just tried. Or transfer it via copy and paste to the address bar of your browser.
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on April 27, 2019, 07:14:50 pm
Hi,

You will also need to install the smb NetDrive plugin.   You can find it here: http://trac.netlabs.org/samba

Once installed, use the NetDrive Volume menu and select "Attach New Volume" menu option.  You will then elect a drive letter to assign your mount point.

With your mount point highlighted within NetDrive, select the Resource menu and the "Mount Resource" menu option. You will be presented with a screen where you should see the option of "smbfs" which is your samba plugin you installed.   

Clicking the "Properties" button will present a screen where you identify your smb workgroup, server, share name, and login credentials.  Once you complete these entries and click the Done button, you will then have your mount point defined and it should be mounted and ready for use.

To save these settings for future use, select the NetDrive menu and the Volume Configuration Save option. 

If you ever lose your mount point due to network issues, you can restart NetDrive by selecting the NetDrive menu, and Control Program Start option.

Sean, sorry for getting back to you, I have installed the samba plugin and proceeded as per your instruction.
Once selected a drive letter to mount (K) , then I go in Resource menu, select the Mount Resource item, choose smbfs and click on Properties (img smbfs1.jpg).

Here (img smbfs2.JPG) is not so clear what/where to set as parameter, and I've also read the HELP section. My main need is to discover/browse my HD volumes other than C:\ which is the root OS2 system in VirtualBox, and secondly (possibly) my home lan connected volumes.

Whatever I try to write -without knowing what it might mean- , I obtain the system error warnings (img smbfs3.JPG and img smbfs4.JPG).

Of course I would need to be more aware or at least more intuitive

Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on April 28, 2019, 06:10:30 pm
Hi Mauro,

It would be helpful to confirm the shares you made available on your network.   At an OS/2 command line, type the following, replacing "xxx" with the IP or host name (if defined in your \mptn\etc\hosts file) of the host having the shares:

            smbclient -L xxx.xxx.xxx.xxx

If your are unable to enumarate your shares with the above command, you will need to verify your host machine has available shares. 

If the above returns a list of available shares, connect to one of the shares using the following OS/2 command, replacing "zzz" with your share name.  If you have user security established on your share, you will be prompted for a password.  If you need to identify a different user when connecting, add "-U username" to the following command to identify the user.

           smbclient \\xxx.xxx.xxx.xxx\zzz

If you successfully connect to the share, you will be at an smb command prompt "smb: \>".  You can then issue a "dir" command to list the files in your share.

Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on April 28, 2019, 07:33:56 pm
Hi Mauro,

It would be helpful to confirm the shares you made available on your network.   At an OS/2 command line, type the following, replacing "xxx" with the IP or host name (if defined in your \mptn\etc\hosts file) of the host having the shares:

            smbclient -L xxx.xxx.xxx.xxx
Hi Sean, I hoped it could be easier sharing local resources with NetDrive and Samba:

[C:\]smbclient -L 127.0.0.1
*here I do not know what else could I write instead 127.0.0.1 and how to discover it, I have just read this address in
C:\MPTN\ETC\hosts.  In other words I ignore the IP address of my resources

the terminal answer is:
gethostname failed
Unable to initialize messaging context
gethostname failed
smbclient: Can't load C:\MPTN\ETC/samba/smb.conf - run testparm to debug it

Quote
If your are unable to enumarate your shares with the above command, you will need to verify your host machine has available shares. 

in my Windows10 resources I have the C volume and the network shared resources accessible just by opening the explorer window, don't know how to translate it in a local resource address to indicate to Samba, which I thought is there to do this.
In the other OS that I'm working with, like Linux Ubuntu or Project Trident (Unix) , you have a resource browser utility that just discover the resource and make them available to you, I believed NetDrive + Samba in OS2 worked with the same premises.

Quote

If the above returns a list of available shares, connect to one of the shares using the following OS/2 command, replacing "zzz" with your share name.  If you have user security established on your share, you will be prompted for a password.  If you need to identify a different user when connecting, add "-U username" to the following command to identify the user.

           smbclient \\xxx.xxx.xxx.xxx\zzz

If you successfully connect to the share, you will be at an smb command prompt "smb: \>".  You can then issue a "dir" command to list the files in your share.

I then need to clear out on how to solve the above explained difficulty, otherwise I won't go far.
Thank you anyway
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on April 29, 2019, 03:32:49 am
I am assuming you are using Windows as your host machine and you are running OS/2 as a virtualized guest and would like your OS/2 guest to access your Windows file system using a Windows share. 

Use the smbclient -L command with your Windows IP address.  The 127.0.0.1 address you had used is your OS/2 "local" address, also called your loopback address.  To find your Windows IP address and your Windows workgroup, get to a command line on your Windows machine and type "nbtstat -n".  This is the address you should use when typing smbclient -L xxx.xxx.xxx.xxx at an OS/2 command prompt.  You will also see your workgroup name (identified as TYPE GROUP).

Before you try to access your Windows share from OS/2, you can test accessing your Windows share from within Windows itself.  Get to a Windows command line and type "net share" to identify the share you have created.  You will see hidden system shares with a dollar sign "$", but you should see the share you created without the dollar sign. 

Once you confirm you have created a Windows share and can see it with the Windows "net share" command, from the Windows command line,  create a mount point to your share to see that you can access the share from Windows.   You would do this by typing the following at a Windows command prompt:

"net use z: \\xxx.xxx.xxx.xxx\sharename persistent:yes"       

Replace "z:" with any unused drive letter you want to use as a mount point.  Replace "xxx.xxx.xxx.xxx" with your Windows machine's IP address obtained from the "nbtstat -n" command.   Replace "sharename" with the name of the share you created and confirmed existed with the "net share" command. 

If your share exists and you have permission to access the share, you should be able to change to the mount point (z:) and issue a "dir" command to see the contents of your share.

If this all works, then go back to OS/2 and use the command smbclient \\xxx.xxx.xxx.xxx\sharename using your Windows host IP address and Windows sharename.  You hopefully will connect to the share and have an smb command prompt "smb: \>".  You can then issue a "dir" command to list the files in your share as you had  done on your Windows machine.

While doing the above might seem like a PITA, it's helpful to diagnose where you might be having a problem.  If the above works, then you should be able to get NetDrive configured and working with the above IP address, workgroup and sharename.
Title: Re: Samba client on OS2 Warp 4.52
Post by: Tom on April 29, 2019, 07:17:08 pm
Sean, don't you mean using 'netstat'  instead of 'nbtstat' ?
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on April 29, 2019, 08:40:41 pm
Hi Tom,

Windows should provide the netbios over TCP/IP output needed to obtain the hostname, IP address and workgroup as follows:

C:\Users\SVC>nbtstat -n
Local Area Connection:
Node IpAddress: [199.50.132.203] Scope Id: []

                NetBIOS Local Name Table
       Name               Type         Status
    ---------------------------------------------
    SATELLITE      <00>  UNIQUE      Registered
    SATELLITE      <20>  UNIQUE      Registered
    UNIVERSE       <00>  GROUP       Registered
    UNIVERSE       <1E>  GROUP       Registered
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 01, 2019, 11:03:33 am
I am assuming you are using Windows as your host machine and you are running OS/2 as a virtualized guest and would like your OS/2 guest to access your Windows file system using a Windows share. 

correct

Quote

Use the smbclient -L command with your Windows IP address.  The 127.0.0.1 address you had used is your OS/2 "local" address, also called your loopback address.  To find your Windows IP address and your Windows workgroup, get to a command line on your Windows machine and type "nbtstat -n".  This is the address you should use when typing smbclient -L xxx.xxx.xxx.xxx at an OS/2 command prompt.  You will also see your workgroup name (identified as TYPE GROUP).


done (img 01)

Quote

Before you try to access your Windows share from OS/2, you can test accessing your Windows share from within Windows itself.  Get to a Windows command line and type "net share" to identify the share you have created.  You will see hidden system shares with a dollar sign "$", but you should see the share you created without the dollar sign. 


done (img 02)

Quote
Once you confirm you have created a Windows share and can see it with the Windows "net share" command, from the Windows command line,  create a mount point to your share to see that you can access the share from Windows.   You would do this by typing the following at a Windows command prompt:

"net use z: \\xxx.xxx.xxx.xxx\sharename persistent:yes"       

Replace "z:" with any unused drive letter you want to use as a mount point.  Replace "xxx.xxx.xxx.xxx" with your Windows machine's IP address obtained from the "nbtstat -n" command.   Replace "sharename" with the name of the share you created and confirmed existed with the "net share" command. 

done (img 03)

Quote

If your share exists and you have permission to access the share, you should be able to change to the mount point (z:) and issue a "dir" command to see the contents of your share.


done (img 04) , since don't know how to change to k because I'm able to get back until C:\ by the cd .. command , then I just found this new resource in explorer, and I can browse the directories in it, assuming with this that everything is ok.

Quote


If this all works, then go back to OS/2 and use the command smbclient \\xxx.xxx.xxx.xxx\sharename using your Windows host IP address and Windows sharename.  You hopefully will connect to the share and have an smb command prompt "smb: \>".  You can then issue a "dir" command to list the files in your share as you had  done on your Windows machine.


ok, here comes the issue  (img 05):
[C:\]smbclient \\192.168.56.1\Users
gethostname failed
Unable to initialize messaging context
gethostname failed
smbclient: Can't load C:\MPTN\ETC/samba/smb.conf - run testparm to debug it .

If it can be of any help, img 06 shows what I actually have in C:\MPTN\ETC  (my OS2 volume directory)

Quote
While doing the above might seem like a PITA, it's helpful to diagnose where you might be having a problem.  If the above works, then you should be able to get NetDrive configured and working with the above IP address, workgroup and sharename.

infact, the above seems something missing in the C:\MPTN\ETC and/or in Samba client 4.9.4-4, which I have installed by ANPM on the Arcanoae Subscription repository.

Thank you
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on May 02, 2019, 12:13:57 am
From your OS/2 machine are you able to ping 192.168.56.1?
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 02, 2019, 07:01:21 am
From your OS/2 machine are you able to ping 192.168.56.1?

yes, it returns an ininterrupted lines sequence of answer:
"64 bytes from  192.168.56.1 icmp_seq=… (sequence number)  time=0. ms  (once sometimes 10. ms)"
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on May 02, 2019, 06:37:46 pm
Networking looks good and that last error you posted points to an issue with your Samba client installation - your smb.conf file couldn't be found, which is needed by the client utilities.   

Per the following readme client installation guidance (smbclut-1_3_0-1054), see if your client is appropriately configured:

Manual installation for older systems:
======================================
The following 3 files should be placed into \lib directory below the
directory you created in step 1. Their purpose is to help with character
translation in certain utilities. Run smbtree.exe -N in order to find out
whether these table files are actually found or not.
   lib\lowcase.dat
   lib\upcase.dat
   lib\valid.dat
Put the enclosed smb.conf in %ETC%\samba. It's purpose is more or less to make
the utilities happy when they check for its presence. It is however recommended
to set the workgroup properly.
======================================

Unrelated to this smbclient issue, I'm not sure what direction to go for the NetDrive error you received.  See if you missed something in Arca Noae's NetDrive installation, checking against their manual installation instructions (https://www.arcanoae.com/shop/netdrive-for-os2/).

Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 05, 2019, 08:13:25 pm
thank you Sean, I have tried to manage with smbclut-1_3_0-1054 and its readme but the only thing I could take for sure was that smb.conf had to be placed in the exsisting C:\etc\samba directory. Doing only this did not change anything.
The other instructions on where to place the other files  are not clear to me.

"The following 3 files should be placed into \lib directory below the
directory you created in step 1." I did not create any directory, I need to know exactly if it's intended to be C:\usr\lib or what else.  Also, I do not catch exactly where to place the other files that are included in sys\apps\smbclnt of the zip archive.

If it tells anything, when I try to set the Netdrive smbfs resource configuration and it gives the system error, the detailed error message is the one in the image below. Could it mean anything wrong with the current system version of LBC066.DLL ?

Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on May 08, 2019, 02:08:09 am
Hi,

I was fortunate to have had the Samba client preinstalled for me on ArcaOS.  My smb.conf is located at \mptn\etc\samba\smb.conf.   I suspect the location can vary based on how your installation was configured, but it's safe to assume smb.conf should be located in your samba directory as it always is in the *nix world.

By running smbtree -N you will validate if your client and server are translating correctly, otherwise your network map might show strange output/characters.   My codepage files are located under the smbclnt subdirectory \sys\apps\smbclnt\codepage\.

I have installed NetDrive on a Warp 4 client without needing to install the samba client, so you might want to put the client install on hold and see if you can get your NetDrive working.
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 09, 2019, 08:33:43 pm
ok, putting SAMBA folder (containing smb.conf) in C:/MPTN/ETC has produced something different as command line answer

[C:\]smbclient //192.168.56.1/User
gethostname failed
gethostname failed
Enter WORKGROUP\GUEST's password:

needless to say that I have no valid password to input there (never wanted a password for my home lan), and the result is:

session setup failed: NT_STATUS_ACCESS_DENIED

also, I've copied the 3 codepage files in C:/USR/LIB folder  ,  C:/USR/LIBEXEC folder ,  C:/LANGUAGE/CODEPAGE folder ,  being those directories the nearest ones I could find sharing the string "LIB" and "CODEPAGE" in their name.
As you see I'm trying hard before surrending


I feel this is a step forward but still no target in view
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on May 10, 2019, 02:01:22 am
What do you see when typing the following at an OS/2 command prompt:  smbtree -N
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 10, 2019, 07:16:06 pm
What do you see when typing the following at an OS/2 command prompt:  smbtree -N

[C:\]smbtree -N
gethostname failed
gethostname failed

[C:\]
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on May 15, 2019, 04:26:36 am
Hi Mauro,

Your networking and authentication look fine.  Your issue appears to involve how smbclient was installed as it is not able to see your network.  I can't think of anything else other than going back over your installation of smbclient.

Your NetDrive installation doesn't have much in the way of software dependencies other than meeting minimum patch levels for your OS.  The NetDrive installation (and smb plugin) for my newly installed vanilla Warp 4 client didn't require any manual configuration for the software's installation, and the set up of those few configuration screens.  There are manual installation instructions you might want to review to help verify your installation.   I would focus first on getting your NetDrive working before moving back to getting the smbclient package installed.

It's not uncommon for me to spend hours and sometimes days to resolve my OS/2 related issues. Keep at it and I'm confident you will eventually get it working.   I'm happy to share any information on my smbclient and NetDrive installation configurations if you need a working reference point.
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 18, 2019, 09:01:47 pm
hi Sean, just to make it clear: while I attempt to connect, is that Windows volume resource supposed to remain mounted or not?
Consider that while OS2 guest system si running, Windows and its resources are running too
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on May 19, 2019, 07:05:26 am
No, it's not to remain mounted.  That was to check to see if you could access your Windows share using your Windows machine's loopback adapter. 

I primarily use Linux and rarely boot Windows.  The latest version of Windows I have is v.7 and I understand you are using v.10.   Assuming you have your OS/2 software configured correctly, it's possible you might also run into security negotiation issues with Windows.   

The following settings are to make your Windows security less restrictive and are applicable to Windows v.7 but could very well apply to your Windows 10 host.  This will weaken your Windows security, but will allow older clients, such as OS/2, access.    I have tested this using a Warp 4 client and NetDrive connecting to a Windows 7 share.

=============

1) Type secpol.msc at the Windows command prompt

Browse to "Local Policies" - "Security Options".  Look for "Network Security: LAN Manager authentication level" and open it.  Click on the menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated".  Apply the setting.

2) In the Advanced sharing settings page of Network and sharing center, you need to have it set as Work/Home profile.

-Enable network discovery
-Turn on file and print sharing
-Turn off password protected sharing
-Use user accounts and passwords to connect to other computers

3) Enter "gpedit.msc" at the Windows command prompt. Open "Computer Configuration"/Windows Settings/Security Settings/Local Policies/Security Settings.  In the right pane, enable the following policies:

-Enable network discovery
-Turn on  file and print sharing
-Turn off password protected sharing
-Use user accounts and passwords to connect to other computers



Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 19, 2019, 02:53:05 pm
No, it's not to remain mounted.  That was to check to see if you could access your Windows share using your Windows machine's loopback adapter. 

I primarily use Linux and rarely boot Windows.  The latest version of Windows I have is v.7 and I understand you are using v.10.   Assuming you have your OS/2 software configured correctly, it's possible you might also run into security negotiation issues with Windows.   

The following settings are to make your Windows security less restrictive and are applicable to Windows v.7 but could very well apply to your Windows 10 host.  This will weaken your Windows security, but will allow older clients, such as OS/2, access.    I have tested this using a Warp 4 client and NetDrive connecting to a Windows 7 share.

=============

1) Type secpol.msc at the Windows command prompt

Browse to "Local Policies" - "Security Options".  Look for "Network Security: LAN Manager authentication level" and open it.  Click on the menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated".  Apply the setting.

2) In the Advanced sharing settings page of Network and sharing center, you need to have it set as Work/Home profile.

-Enable network discovery
-Turn on file and print sharing
-Turn off password protected sharing
-Use user accounts and passwords to connect to other computers

3) Enter "gpedit.msc" at the Windows command prompt. Open "Computer Configuration"/Windows Settings/Security Settings/Local Policies/Security Settings.  In the right pane, enable the following policies:

-Enable network discovery
-Turn on  file and print sharing
-Turn off password protected sharing
-Use user accounts and passwords to connect to other computers

Hi Sean, something good has finally happened after having applied your last suggestions : Samba seems alive ! Here is the command responses in the OS2 command window (at password request I've just hitted [send]:

[C:\]smbclient \\192.168.56.1\Users
gethostname failed
gethostname failed
Enter WORKGROUP\GUEST's password:

Try "help" to get a list of possible commands.
smb: \> dir
  .                                  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: \>

now, this is working in the OS2 command window but still cannot get it work in the Net Drive panel -Mount resource configuration (smbfs plugin) where I keep having an error alert when at the end I hit DONE, sure 100% that I'm doing mistakes in filling the fields values.
Another small step to the goal   :D
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 21, 2019, 08:42:45 pm

If this all works, then go back to OS/2 and use the command smbclient \\xxx.xxx.xxx.xxx\sharename using your Windows host IP address and Windows sharename.  You hopefully will connect to the share and have an smb command prompt "smb: \>".  You can then issue a "dir" command to list the files in your share as you had  done on your Windows machine.

While doing the above might seem like a PITA, it's helpful to diagnose where you might be having a problem.  If the above works, then you should be able to get NetDrive configured and working with the above IP address, workgroup and sharename.

I'm there: the above works. But getting same error alert after having filled the configuration of smbfs plugin values.
Repeat, maybe I'm missing the correct way to input values in the fields or else the smbfs plugin version 2.1.5 does not match the 4.9.4-4 samba client version installed by yum-rpm, but it looks like I've almost done it, just need the final push.
Thank you
Title: Re: Samba client on OS2 Warp 4.52
Post by: Sean Casey on May 29, 2019, 06:30:08 pm
Hi,

I didn't have any further suggestions regarding your NetDrive issue.  I see Paul has offered his assistance so hopefully you will have this resolved shortly.
Title: Re: Samba client on OS2 Warp 4.52
Post by: mauro on May 29, 2019, 07:56:38 pm
Hi,

I didn't have any further suggestions regarding your NetDrive issue.  I see Paul has offered his assistance so hopefully you will have this resolved shortly.

Ok no problem, thank you for all the indications given till now, which let me a better knowledge than before on this argument