Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mauro

Pages: 1 ... 17 18 [19] 20 21 ... 28
271
Networking / Re: Samba 4.9.0 based client
« 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"


272
Networking / Re: Samba 4.9.0 based client
« 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.


273
Networking / Re: Samba 4.9.0 based client
« 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)

274
Networking / Re: Samba 4.9.0 based client
« 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


275
Applications / Re: Samba client on OS2 Warp 4.52
« 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

276
Networking / Re: Samba 4.9.0 based client
« 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.

277
Networking / Re: Samba 4.9.0 based client
« 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-

278
Applications / Re: Samba client on OS2 Warp 4.52
« 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

279
Applications / Re: Samba client on OS2 Warp 4.52
« 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

280
Applications / Re: Samba client on OS2 Warp 4.52
« 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

281
Applications / Re: Samba client on OS2 Warp 4.52
« 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:\]

282
Applications / Re: Samba client on OS2 Warp 4.52
« 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

283
Applications / Re: Samba client on OS2 Warp 4.52
« 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 ?


284
Applications / Re: Samba client on OS2 Warp 4.52
« 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)"

285
Applications / Re: Samba client on OS2 Warp 4.52
« 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

Pages: 1 ... 17 18 [19] 20 21 ... 28