Author Topic: Updated Samba Client  (Read 81044 times)

David McKenna

  • Hero Member
  • *****
  • Posts: 766
  • Karma: +25/-0
    • View Profile
Re: Updated Samba Client
« Reply #165 on: February 03, 2024, 12:52:53 am »
Paul,

  I'm having trouble with this one - get a trap in WINBINDD.EXE at start. Logs attached. Went back to previous and all is well...

Regards,
« Last Edit: February 03, 2024, 02:17:51 pm by David McKenna »

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2115
  • Karma: +164/-0
    • View Profile
Re: Updated Samba Client
« Reply #166 on: February 03, 2024, 04:41:10 am »
  I'm having trouble with this one - get a trap in WINBINDD.EXE at start. Logs attached. Went back to previous and all is well...
Interesting. There were no *intentional* changes for winbindd  - I'll have to figure out how to use it. You backlevelled just winbindd.exe?

Edit:  I can reproduce this... investigating now.

Edit2: This is due to my  uncommitted changes to https://github.com/psmedley/samba-os2/blob/samba-os2-4.19.x/lib/messaging/messages_dgm.c (to fix all the leftover files in msg.lock) Will investigate...

Edit3:  https://smedley.id.au/tmp/samba-4.19.4-os2-20240203.zip contains a change that seems to fix startup of winbindd but may cause message files in msg.lock to not be removed -  needs testing...
« Last Edit: February 03, 2024, 08:45:20 am by Paul Smedley »

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2115
  • Karma: +164/-0
    • View Profile
Re: Updated Samba Client
« Reply #167 on: February 03, 2024, 08:57:50 am »
Network browsing is still not working, same as before.

Clarifying - is this with Arcamapper from 5.0 or 5.1? They use quite different approaches...

David McKenna

  • Hero Member
  • *****
  • Posts: 766
  • Karma: +25/-0
    • View Profile
Re: Updated Samba Client
« Reply #168 on: February 03, 2024, 02:17:20 pm »
 Hey Paul,

 Thanks for that update - WINBINDD is now fine again and the lock files are deleted when the server is stopped just like before.

 One weird thing I just noticed - when I copy a file to the server (from an OS/2 client - both 4.19) the file name is truncated to 8.3 format. Do you see that? I tried both EA's on and off, but still the same. I know this didn't used to happen, but not sure when it crept in (first noticed in the 20240202 drop).

EDIT: I backlevelled the ndpsmb.dll on the client to the 20240110 version, and now files are copied with the full name. So it's not the server, it's the 20240131 client plugin causing this.

  Like Neil, I also don't see shares with the ArcaMapper browser (AN 5.1). Is there something that can be added to smb.conf to allow displaying shares? SMBTREE works fine (once the password is added).

 One question - the 4.11 version of smbcl411 came with some binaries of things like net.exe and smbtree.exe etc. that were considerably smaller than the ones that come with the server. Is it OK to replace the old ones on the client with the new ones from the server package?

Regards,
« Last Edit: February 03, 2024, 03:28:54 pm by David McKenna »

Alex Taylor

  • Sr. Member
  • ****
  • Posts: 393
  • Karma: +5/-0
    • View Profile
Re: Updated Samba Client
« Reply #169 on: February 03, 2024, 02:34:06 pm »
  Like Neil, I also don't see shares with the ArcaMapper browser (AN 5.1). Is there something that can be added to smb.conf to allow displaying shares? SMBTREE works fine (once the password is added).

I assume you see the actual servers and just not the shares on them?

This is most likely due to using the wrong user credentials for browsing. The bottom right of the status bar shows the user that's currently being used. If that user doesn't have permission to see shares on each server, you won't see them. 

You can change the browsing credentials from the Network->Authenticate menu item.

David McKenna

  • Hero Member
  • *****
  • Posts: 766
  • Karma: +25/-0
    • View Profile
Re: Updated Samba Client
« Reply #170 on: February 03, 2024, 02:43:09 pm »
Hi Alex,

  Yes, the workgroup and server show up in the left pane, just not any shares in the right. I am running Paul's 4.19 client and server, using the same credentials used to log on to the shares, and also used when running SMBTREE. The same credentials are shown as being 'active'. I have also tried 'root' and 'guest' but nothing seems to work. Is there a way to get logs for the ArcaMapper to figure this out?

EDIT: one thing I didn't mention that might be a clue - even though I am already logged on to a share with the credentials, the first time after booting when I open the browser, it asks for the password. Is that working as designed? Subsequent attempts to open the browser do not ask for the password.

Regards,
« Last Edit: February 03, 2024, 03:39:53 pm by David McKenna »

Neil Waldhauer

  • Hero Member
  • *****
  • Posts: 1044
  • Karma: +25/-0
    • View Profile
    • Blonde Guy
Re: Updated Samba Client
« Reply #171 on: February 03, 2024, 03:26:45 pm »
Network browsing is still not working, same as before.

Clarifying - is this with Arcamapper from 5.0 or 5.1? They use quite different approaches...

This is with ArcaOS 5.1. I didn't think to try the old ArcaMapper. I'll set one up and try it...

The old ArcaMapper is much like the new. Browsing fails with this message "Connecting to Magnesium failed (Error NT_STATUS_UNSUCCESSFUL)

I see the workgroup and computers, but not the shares. How do you enable browsing for a user?
« Last Edit: February 03, 2024, 04:33:04 pm by Neil Waldhauer »
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2115
  • Karma: +164/-0
    • View Profile
Re: Updated Samba Client
« Reply #172 on: February 03, 2024, 09:13:20 pm »
Hey Paul,

 Thanks for that update - WINBINDD is now fine again and the lock files are deleted when the server is stopped just like before.

 One weird thing I just noticed - when I copy a file to the server (from an OS/2 client - both 4.19) the file name is truncated to 8.3 format. Do you see that? I tried both EA's on and off, but still the same. I know this didn't used to happen, but not sure when it crept in (first noticed in the 20240202 drop).

EDIT: I backlevelled the ndpsmb.dll on the client to the 20240110 version, and now files are copied with the full name. So it's not the server, it's the 20240131 client plugin causing this.

  Like Neil, I also don't see shares with the ArcaMapper browser (AN 5.1). Is there something that can be added to smb.conf to allow displaying shares? SMBTREE works fine (once the password is added).

 One question - the 4.11 version of smbcl411 came with some binaries of things like net.exe and smbtree.exe etc. that were considerably smaller than the ones that come with the server. Is it OK to replace the old ones on the client with the new ones from the server package?

I'll  try take these in order:
1) truncation of files names - I'm not seeing this with:
31/01/24  17:50          50,526    124  ndpsmb.dll
md5sum: fbdf044abee62c4fa6020f04a041695b *ndpsmb.dll
Tested against linux and OS/2  servers - and copying from command line and via WPS.

2) the older client had net.exe and others built using smbcl4xx.dll  (hence they were smaller) - there's no harm  dropping in the larger ones

3) I need to do some testing with arcamapper against OS/2 and unix hosts. My test machines are still AOS 5.0 though, will need to spin up  a 5.1 VM.

David McKenna

  • Hero Member
  • *****
  • Posts: 766
  • Karma: +25/-0
    • View Profile
Re: Updated Samba Client
« Reply #173 on: February 03, 2024, 09:31:38 pm »
Paul,

 Just tried again with the 20240131 client version you list (also checked md5sum), and when I drag and drop from a local drive to the shared drive, the copied file has a truncated 8.3 style name on the share - does it every time. Hadn't tried before, but when doing it from a command line it works correctly.  Strange it doesn't happen for you...   

Regards,   
« Last Edit: February 03, 2024, 09:42:35 pm by David McKenna »

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2115
  • Karma: +164/-0
    • View Profile
Re: Updated Samba Client
« Reply #174 on: February 03, 2024, 09:48:48 pm »
Just tried again with the 20240131 client version you list (also checked md5sum), and when I drag and drop from a local drive to the shared drive, the copied file has a truncated 8.3 style name on the share - does it every time. Hadn't tried before, but when doing it from a command line it works correctly.  Strange it doesn't happen for you...   
I used WPS Move command  -  drag/drop is too hard in Virtualbox.  For interest, can you try with ndpsmb-20240127.zip ? the only difference is the return code of the check for A.+,;=[].B
ie https://github.com/psmedley/ndpsmb/commit/0fb2bbc232ea9d5d0e360fc24fb265462e55d956

David McKenna

  • Hero Member
  • *****
  • Posts: 766
  • Karma: +25/-0
    • View Profile
Re: Updated Samba Client
« Reply #175 on: February 03, 2024, 10:04:43 pm »
Paul,

  Client 20240127 seems to work fine...

Regards,

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2115
  • Karma: +164/-0
    • View Profile
Re: Updated Samba Client
« Reply #176 on: February 03, 2024, 10:09:34 pm »
Thanks - I'll revert the last commit

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1335
  • Karma: +26/-0
    • View Profile
Re: Updated Samba Client
« Reply #177 on: February 04, 2024, 12:09:53 am »
Client 20240127 seems to work fine...

...re-tried here and still getting a TRAP-D.

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2115
  • Karma: +164/-0
    • View Profile
Re: Updated Samba Client
« Reply #178 on: February 04, 2024, 03:24:06 am »
Client 20240127 seems to work fine...

...re-tried here and still getting a TRAP-D.
Unfortunately I have no real  clue why this is happening.

David McKenna

  • Hero Member
  • *****
  • Posts: 766
  • Karma: +25/-0
    • View Profile
Re: Updated Samba Client
« Reply #179 on: February 04, 2024, 05:45:43 pm »
Hey Paul,

 I have been using the Netlabs 3.6 SAMBA WPI to install SAMBA on my machine, then use the 'SAMBA Simple Configuration Center' app to update it with your binaries. This has worked well enough, except now the 'SAMBA Users and Groups' app gives an error when run after updating to your current 4.19.4 binaries. From what I have been able to determine, 'SAMBA Users and Groups' uses 'net rpc xxxx' commands to manipulate the users and groups in SAMBA databases. Did some testing to see if I could figure out why it doesn't work...

 After installing the 3.6 wpi, I am able to issue say -  'net rpc user' - on a command line and after entering a password it lists all users set up for SAMBA. Other 'net rpc xxx' commands also work.

 After upgrading to 4.19.4, when I enter 'net rpc user', after entering a password I get nothing (no error, it just returns to the prompt). So that explains the error I get when trying to run 'SAMBA Users and Groups'. Is this a bug?

EDIT: I went thru and tried each of your SAMBA builds starting with 4.11. SAMBA Users and Groups worked with 4.11, 4.13 and 4.15, but not 4.18 and 4.19.

 The 'SAMBA Status Monitor' 'Nethood' tab also gives an error (other tabs work fine), and I get an exceptq log in SMBTREE - I'll attach.

EDIT: 4.11 was the last build 'Nethood' worked with.

Regards,
« Last Edit: February 04, 2024, 11:29:54 pm by David McKenna »