OS/2, eCS & ArcaOS - Technical > Networking

Samba 4.9.0 based client

<< < (3/9) > >>

ivan:
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:

--- Quote from: 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.

--- End quote ---

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:
Hi,


--- Quote from: mauro on May 28, 2019, 03:17:09 pm ---
--- Quote from: 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.

--- End quote ---

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.

--- End quote ---

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:

--- Quote from: Paul Smedley on May 29, 2019, 11:33:50 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).
...
--- End quote ---

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: ---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]

--- End code ---

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:
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?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version