OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Networking => Topic started by: Paul Smedley on September 15, 2018, 10:22:45 am

Title: Samba 4.9.0 based client
Post by: Paul Smedley 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
Title: Re: Samba 4.9.0 based client
Post by: David McKenna 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...
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley 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...
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley 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
Title: Re: Samba 4.9.0 based client
Post by: Dariusz Piatkowski 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
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley 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
Title: Re: Samba 4.9.0 based client
Post by: David McKenna 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,
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley 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
Title: Re: Samba 4.9.0 based client
Post by: Dariusz Piatkowski 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
Title: Re: Samba 4.9.0 based client
Post by: mauro 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-
Title: Re: Samba 4.9.0 based client
Post by: ivan 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.
Title: Re: Samba 4.9.0 based client
Post by: mauro 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.
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley 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
Title: Re: Samba 4.9.0 based client
Post by: Dariusz Piatkowski 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?)



Title: Re: Samba 4.9.0 based client
Post by: ivan 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?
Title: Re: Samba 4.9.0 based client
Post by: mauro on May 30, 2019, 08:43:22 pm
Hi,
............……………………………….
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

Hi Paul, I've created  ndpsmb.dbg in C:\ , rebooted, started Netdrive and filled the smbfs parametres field with same parametres as x Samba resource working in the OS2 window, pressed on DONE : error alert.   And no ndpsmb.log found anywhere.
All I can show in the following image of how I filled the smbfs configuration page end the other image of the system error message.
the software in use is
-Samba client 4.9.4-4 i686 (rpm package from Arcaos Subscription repository)
-Heimdal 7.5.0-3 i686 (rpm package linked to samba package)
-Heimdal lib 7.5.0-3 i686 (rpm package linked to samba package)
-Netdrive  3.1.6.876 (executable package)
-smbfs plugin 2.1.5 GA (wpi package)
thank you

Title: Re: Samba 4.9.0 based client
Post by: mauro on May 30, 2019, 08:46:01 pm
mauro:
Can you post the specific versions of the installed components you have?


Hi Dariusz, here are the installed components:

-Samba client 4.9.4-4 i686 (rpm package from Arcaos Subscription repository)
-Heimdal 7.5.0-3 i686 (rpm package linked to samba package)
-Heimdal lib 7.5.0-3 i686 (rpm package linked to samba package)
-Netdrive  3.1.6.876 (executable package)
-smbfs plugin 2.1.5 GA (wpi package)
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley on May 31, 2019, 04:46:15 am
Hi Mauro,

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


Hi Dariusz, here are the installed components:

-Samba client 4.9.4-4 i686 (rpm package from Arcaos Subscription repository)
-Heimdal 7.5.0-3 i686 (rpm package linked to samba package)
-Heimdal lib 7.5.0-3 i686 (rpm package linked to samba package)
-Netdrive  3.1.6.876 (executable package)
-smbfs plugin 2.1.5 GA (wpi package)

If you really have 'smbfs plugin 2.1.5 GA (wpi package)' installed, this is your issue with Windows 10. the 2.1.5 package uses Samba 3.x which only understands the SMB1 protocol.

For security reasons, Windows 10 (by default) only talks SMB2+

There should be a rpm package for a ndpsmb that talks to -Samba client 4.9.4-4 i686 (rpm package from Arcaos Subscription repository)

Cheer,s

Paul.
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley on May 31, 2019, 04:48:14 am
Also.... your parameters to configure the plugin are wrong....

you have \\192.168.56.1\Users as the share

This needs to be:

Server: 192.168.56.1
Share:  Users

Title: Re: Samba 4.9.0 based client
Post by: mauro on May 31, 2019, 09:23:53 pm
well thank you, something has changed.
I've taken a ndsmb.dll 3.5.0 version from a zip archive (not rpm found in the repositories) , and used it to replace the old 2.1.5 GA version in c:\ndfs\ndplugs.

The result (see images) is no more error alerts when, after having filled the configuration fields as you indicated, I press DONE.
Good.
But then I do not see anything in NetDrive mounted resource panel, it remains empty.
The new mounted drive letter appears in WPS volumes, but empty.

Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley on May 31, 2019, 11:43:44 pm
Server entry is still wrong...

needs to be Server: 192.168.56.1 NOT \\192.168.56.1\
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 01, 2019, 02:06:24 pm
Server entry is still wrong...

needs to be Server: 192.168.56.1 NOT \\192.168.56.1\

I went for this entry after having tested the different combinations of "\" symbol (only \\ before, only \ after, completely without), and with my choice was the only one without error messages yesterday.
But today the message is  : "The smbfs resource was not mounted to Mount point L:\   Error code: 58"

While the way you suggest gives this error message after pressing DONE: 
"The smbfs resource was not mounted to Mount point L:\   Error code: 65"

Title: Re: Samba 4.9.0 based client
Post by: ivan on June 01, 2019, 08:11:55 pm
Can you ping 192.168.56.1  In other words is that a valid IP address?
Title: Re: Samba 4.9.0 based client
Post by: Wim Brul on June 01, 2019, 09:17:45 pm
Quote
I went for this entry after having tested the different combinations of "\" symbol (only \\ before, only \ after, completely without), and with my choice was the only one without error messages yesterday.
But today the message is  : "The smbfs resource was not mounted to Mount point L:\   Error code: 58"
Code: [Select]
[H:\]help sys58
SYS0058: The specified server cannot perform the requested operation.

EXPLANATION: You are attempting an operation that cannot be performed
by the specified server.

ACTION: Make sure that you have specified the correct computer name
and command, then retry the command.  If you continue to have problems,
contact your network administrator.
Quote
While the way you suggest gives this error message after pressing DONE:
"The smbfs resource was not mounted to Mount point L:\   Error code: 65"
Code: [Select]
[H:\]help sys65
SYS0065: Network access is denied.

EXPLANATION: You attempted to access a resource that is not available
to you.  It is possible that:
o  You do not have a valid account on the server sharing the resource.
o  Your account on this server has not been granted the permissions
   necessary to access the resource.

ACTION: Make sure that you specify the correct name of the resource
that you want to use and retry the command.  If you are still denied
access, contact your network administrator.
Seems to me that 192.168.56.1 as said by Paul Smedley is correct.

Wim
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 02, 2019, 09:07:12 am
Seems to me that 192.168.56.1 as said by Paul Smedley is correct.

Wim

Hi Wim, as said, the thing is that the resource is available at a "smb:>" prompt in an OS2 command window, and (also said), if it is available there must be available in NetDrive. The issue could also be -just guessing- the password request that I skip just by hitting RETURN :

smbclient \\192.168.56.1\Users


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

here I hit RETURN and I get this :

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

then I command
smb: \> dir

and the requested resource's folders are 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: \>
Title: Re: Samba 4.9.0 based client
Post by: Wim Brul on June 02, 2019, 10:32:20 am
Seems to me that 192.168.56.1 as said by Paul Smedley is correct.

Wim

Hi Wim, as said, the thing is that the resource is available at a "smb:>" prompt in an OS2 command window, and (also said), if it is available there must be available in NetDrive.
Hi Mauro, unfortunately for you I have no experience with smb nor NetDrive at all, so I cannot help you further. Sorry.
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 02, 2019, 11:16:31 am
Seems to me that 192.168.56.1 as said by Paul Smedley is correct.

Wim

Hi Wim, as said, the thing is that the resource is available at a "smb:>" prompt in an OS2 command window, and (also said), if it is available there must be available in NetDrive.
Hi Mauro, unfortunately for you I have no experience with smb nor NetDrive at all, so I cannot help you further. Sorry.

ok, thank you anyway for answering.  Samba implementation was tricky but at the end with good suggestions and attempts I succeeded to make it work at least by OS2 command line, while NetDrive is really a mistery. I believe it might be a version issue of application itself or ndsmb plugin version not matching with Samba version (although already tried to change them) or else some implementation is only good for ARCA OS but not for OS2 Warp 4.52.
Title: Re: Samba 4.9.0 based client
Post by: Sean Casey on June 02, 2019, 06:31:23 pm

or ndsmb plugin version not matching with Samba version (although already tried to change them) or else some implementation is only good for ARCA OS but not for OS2 Warp 4.52.

i have installed NetDrive on vanilla Warp 4.52 using the plugin "ndpsmb-2.2.0-Beta4-20140226.wpi".  You can find this on http://trac.netlabs.org/samba
(http://smb1.jpg)

To map a drive within NetDrive, I use the settings per the attached.
(http://smb2.jpg)
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley on June 03, 2019, 10:49:41 am
Server entry is still wrong...

needs to be Server: 192.168.56.1 NOT \\192.168.56.1\

I went for this entry after having tested the different combinations of "\" symbol (only \\ before, only \ after, completely without), and with my choice was the only one without error messages yesterday.
But today the message is  : "The smbfs resource was not mounted to Mount point L:\   Error code: 58"

While the way you suggest gives this error message after pressing DONE: 
"The smbfs resource was not mounted to Mount point L:\   Error code: 65"

Do you have a ndpsmb.log at all?
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 03, 2019, 09:01:39 pm
Server entry is still wrong...

needs to be Server: 192.168.56.1 NOT \\192.168.56.1\

I went for this entry after having tested the different combinations of "\" symbol (only \\ before, only \ after, completely without), and with my choice was the only one without error messages yesterday.
But today the message is  : "The smbfs resource was not mounted to Mount point L:\   Error code: 58"

While the way you suggest gives this error message after pressing DONE: 
"The smbfs resource was not mounted to Mount point L:\   Error code: 65"

Do you have a ndpsmb.log at all?

LOOK BELOW !!!!!

still cannot believe, please don't wake me up!

I kept trying every variation of settings in smbfs parametres, and now I've found it needed the "workgroup" specification in the Workgroup field, and nousers/nopassword in the login table.

This is it, thank you a lot Paul, Sean, Dave, David, Dariusz, Ivan, Wim, everyone who supported me here, hope this thread will be an additional reference for those ones encountering issues in configuring Samba and NetDrive in OS2 Warp 4.52.

Title: Re: Samba 4.9.0 based client
Post by: Dariusz Piatkowski on June 05, 2019, 04:52:49 am
...
LOOK BELOW !!!!!

still cannot believe, please don't wake me up!

I kept trying every variation of settings in smbfs parametres, and now I've found it needed the "workgroup" specification in the Workgroup field, and nousers/nopassword in the login table.
..

Ahh....this is so easy to overlook...sorry I did not catch this earlier. On my network I have mapped all the static IP addresses for each machine to a hostname. The same HOSTS file has been deployed on all the networked PCs, so when I want to access my NAS box I simply point to "NAS" everywhere. This way at least I have a single source of the name to IP address mapping and if things ever change I do not have to chase around all different places to update the stuff.

In parallel to this I re-named my workgroup to "HOME".

Well, congrats...glad to hear you are up and running now!
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 05, 2019, 10:02:01 pm
....what about linux (Ubuntu) host? I have same cloned Vbox Warp 4.52 machine, in an Ubuntu 18.04 system fully working in an usb pendrive.
When this USB is plugged in same laptop with Win10 hard disk, Ubuntu can browse every Win 10 directory, but from Warp 4.52 virtual machine the resource call
[C:\]smbclient  \\192.168.56.1\Users

gives this answer:

gethostname failed
gethostname failed
Connection to 192.168.56.1 failed (Error NT_STATUS_IO_TIMEOUT)

also, found the Ubuntu machine static ip address 192.168.1.84 (by ifconfig command),
 if I give
[C:\]smbclient  \\192.168.1.84\

obtain:
gethostname failed
gethostname failed

I presume not getting the correct resource call for Ubuntu (or I'm missing an important part as usual), do you have your own experience to get me on the right path here as well?
 :D
Thank you




Title: Re: Samba 4.9.0 based client
Post by: ivan on June 05, 2019, 10:34:53 pm
How did you setup networking for the Linux vbox host? 

If you want it to see anything on your network you have to set it as a 'bridged adapter', at least that is how I have vbox setup in a real Linux Mint machine and I can see everything on my network.
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 06, 2019, 10:51:25 pm
How did you setup networking for the Linux vbox host? 

If you want it to see anything on your network you have to set it as a 'bridged adapter', at least that is how I have vbox setup in a real Linux Mint machine and I can see everything on my network.

Have also changed the Vbox network setting in "Bridge adapter" as you said but getting same

[C:\]smbclient \\192.168.1.84\home
gethostname failed
gethostname failed
Connection to 192.168.1.84 failed (Error NT_STATUS_CONNECTION_REFUSED)

it is like the Linux resource is not ready for some setting reasons (permissions? name? wrong mounted/unmounted status? .....
Not even appears a password prompt like it was in Windows host, which I would expect as a Linux standard
Title: Re: Samba 4.9.0 based client
Post by: ivan on June 07, 2019, 01:07:23 am
OK, first check what the network settings are for your Linux install Find under 'Preferences' -- 'Network', it should open showing the basic network connection information (connection speed, IPv4 address, IPv6 address,hardware address, default route, DNS) if you don't have an IPv4 address in the range supplied by the DHCP server of your router you have problems which need to be fixed first.

The 'gear' symbol, bottom right, opens a page that allows you to edit settings except for the 'Details' page.

Once you are satisfied the network settings are correct you can close the network window.

Now open either the 'Computer'  or 'Home' 'File Browser' window and click on 'Network' down arrow, then click on what is displayed, this should open a window showing all items it can read (it generally shows SMB/CIFS items as 'Windows Network', double clicking on that should show all your running SMB/CIFS servers (remember you will not see your win 10 box because it is not running while you are booted into your live linux USB stick).

I hope this helps bur remember I am using a full Linux Mint install on a real computer whereas you are using a live linux from a bootable USB.
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 07, 2019, 06:55:49 am
(remember you will not see your win 10 box because it is not running while you are booted into your live linux USB stick).

I hope this helps bur remember I am using a full Linux Mint install on a real computer whereas you are using a live linux from a bootable USB.

I'm using a full Ubuntu 18.04 install, it is on an USB stick but fully installed like it was on a pc.

Not a live usb
Title: Re: Samba 4.9.0 based client
Post by: ivan on June 07, 2019, 04:21:44 pm
OK, that still requires that you get the Linux networking setup correctly.

The problem will still be viewing anything on the disks of your win 10 machine. Ubuntu should be able to read the win10 drive partitions (you can do that with a live linux usb/dvd so a full install makes it easy) the problem comes from just how vbox running on linux on usb will see the SMB/CIFS server that only works when win10 is running (since Ubuntu is the operating system when running from your USB, win does not start the SMB/CIFS server therefore any samba drives will not be visible).
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 07, 2019, 05:23:03 pm
OK, that still requires that you get the Linux networking setup correctly.

The problem will still be viewing anything on the disks of your win 10 machine. Ubuntu should be able to read the win10 drive partitions (you can do that with a live linux usb/dvd so a full install makes it easy) the problem comes from just how vbox running on linux on usb will see the SMB/CIFS server that only works when win10 is running (since Ubuntu is the operating system when running from your USB, win does not start the SMB/CIFS server therefore any samba drives will not be visible).

ok, I' have had this idea yesterday and have also installed the smb client on Ubuntu, but then responding same "Connection to 192.168.1.84 failed (Error NT_STATUS_CONNECTION_REFUSED)"  as in OS2 when give the "smbclient \\192.168.1.84\home" command in linux terminal.  It could also be the client activation not correctly performed or running.....
Title: Re: Samba 4.9.0 based client
Post by: ivan on June 07, 2019, 06:29:52 pm
First question, is 192.168.1.84 the IP address of a different separate machine running a SMB/CIFS server?

Second question, what shows up in file manager when you click on 'network'?

Third thing, if you don't have a samba server running no matter what you are doing you are not going to find anything.  For example, on my network I have 3 NAS boxes that each run a SMB/CIFS server, I am also running samba servers on 3 of my computers.  All of those are visible to any samba client on the network.
Title: Re: Samba 4.9.0 based client
Post by: Gregg Young on June 08, 2019, 10:46:24 pm
Hi Paul

smbspool.exe is broken in 4.9.4 and higher (tried 4.9.5 & 4.10.1). I am using the SMB printer port which works with version 4.4 and 4.7.7. These are the only versions I have tried.

I get "Error 1 during spooling to smb://USERNAME:****@CATMASTER/PIPPIN/Printer" Error 1 is NT_STATUS_ACCESS_VIOLATION. See ticket 2528 on the AN mantis site for more details. Thanks

Gregg
Title: Re: Samba 4.9.0 based client
Post by: Paul Smedley on June 09, 2019, 07:10:33 am
Hi Gregg,

smbspool.exe is broken in 4.9.4 and higher (tried 4.9.5 & 4.10.1). I am using the SMB printer port which works with version 4.4 and 4.7.7. These are the only versions I have tried.

I get "Error 1 during spooling to smb://USERNAME:****@CATMASTER/PIPPIN/Printer" Error 1 is NT_STATUS_ACCESS_VIOLATION. See ticket 2528 on the AN mantis site for more details. Thanks

See updates in ticket 2528 at the AN site, but smbspool is working fine here - this is some kind of authentication issue with your Samba 3.x server - most likely due to increased security in newer Samba releases.

Cheers,

Paul
Title: Re: Samba 4.9.0 based client
Post by: mauro on June 09, 2019, 12:40:24 pm
First question, is 192.168.1.84 the IP address of a different separate machine running a SMB/CIFS server?

Second question, what shows up in file manager when you click on 'network'?

Third thing, if you don't have a samba server running no matter what you are doing you are not going to find anything.  For example, on my network I have 3 NAS boxes that each run a SMB/CIFS server, I am also running samba servers on 3 of my computers.  All of those are visible to any samba client on the network.

ok, finally I made it work for Ubuntu host as well !!!


Almost everything was correct, the missing part was that Samba client in Linux must also be configured after installing, in order to set a specific folder for the samba resource and for which user, otherwise it won't be available.

This tutorial was my lighthouse:
https://www.computerbeginnersguides.com/blog/2018/04/27/install-and-configure-samba-in-ubuntu-18-04-bionic-beaver/ (https://www.computerbeginnersguides.com/blog/2018/04/27/install-and-configure-samba-in-ubuntu-18-04-bionic-beaver/)0

and you the navigator  :D
thanks


Title: Re: Samba 4.9.0 based client
Post by: ivan on June 09, 2019, 03:52:41 pm
Sorry I missed out mentioning that.  I've had everything working here for the last 30 years that I didn't even think about it.