2071
Networking / Re: Samba 4.9.0 based client
« on: May 29, 2019, 11:33:50 am »
Hi,
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
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