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 - David McKenna

Pages: [1] 2 3 ... 50
Networking / Re: Updated Samba Client
« on: February 25, 2024, 03:42:20 pm »
Thanks Paul!

  This 4.19.5 server seems to perform about the same as the 4.19.4 version, except WINBINDD will not start - log ends with this message:

[2024/02/25 09:07:58.200000,  5] ../../librpc/rpc/dcesrv_core.c:430(dcesrv_interface_register_b)
  dcesrv_interface_register_b: Interface 'winbind' registered on endpoint 'ncalrpc:' (single process required)
[2024/02/25 09:07:58.200000,  1] ../../source3/winbindd/winbindd.c:1038(winbindd_setup_listeners)
  lp_winbindd_socket_directory() = \socket\winbindd, WINBINDD_SOCKET_NAME = pipe
[2024/02/25 09:07:58.200000,  0] ../../lib/util/util.c:225(directory_create_or_exist)
  directory_create_or_exist: mkdir failed on directory \socket\winbindd: No such file or directory
[2024/02/25 09:07:58.200000,  0] ../../lib/util/become_daemon.c:123(exit_daemon)
  exit_daemon: daemon failed to start: Winbindd failed to setup listeners, error code 32

 Didn't we see something like this before?


EDIT: added net rpc user log for comparison...

Networking / Re: Updated Samba Client
« on: February 22, 2024, 11:17:00 pm »
Hey Paul,

 Curious how your theory panned out...


Applications / Re: Test build of dooble with qt5
« on: February 22, 2024, 11:12:57 pm »

  Thanks for the updates... seem to be working well here. No more db file in the root... Haven't seen that in the QT6 versions, but the latest hasn't been ported yet.


Comments, Suggestions & Questions / Re: Hobbes (Files) Reoganization
« on: February 16, 2024, 11:33:35 pm »
 Thanks Martin and Nathan for keeping Hobbes alive! Very important resource for OS/2 users on the web.


EDIT: I notice on the main page mirror 'OS/2 Site Australia' is shown to be in the USA? I doubt it...

 Also was not able to register an account - got a generic 'something went wrong' error...

Applications / Re: Test build of dooble with qt5
« on: February 13, 2024, 01:48:47 am »

 Well, it kinda works here (I think) only if the jar file is on my unixroot drive. But all it does is display the contents - if I click on any file displayed nothing happens. What exactly is it supposed to do?

 One weird thing: I get a new 'dooble_settings.db' file in the root of my boot drive with this version. Never had that before...


Applications / Re: Test build of dooble with qt5
« on: February 12, 2024, 10:39:35 pm »
 Thanks - got it. So far it works fine. Also got the zip file and there is a 'Data' folder in there with a couple of jar files that are not in the rpm. What are they?


Applications / Re: Test build of dooble with qt5
« on: February 12, 2024, 10:26:15 pm »
 Thanks Dave! Tried to get the rpm, but it wants a password to login. Can you give the password?


Networking / Re: Updated Samba Client
« on: February 08, 2024, 11:16:46 pm »
 Hey Paul,

 Spent the last couple of evenings pondering the forgotten lore of Netlabs SAMBA apps code to try to figure out the SMBTREE command that causes the trap in server 4.19 and it seems to be something like this:

SMBTREE -S -N -d 2 2>smberror.txt 1>smbtree.txt

 I'll attach the results. They show a trap, and I tried with both 'null passwords = Yes' and 'No' in smb.conf, but no difference.

 So also tried SMBTREE -S -U DaveM%password -d 2 2>smberror2.txt 1>smbtree2.txt

 and don't get a trap, but it still doesn't seem to work quite right - I'll attach them too. The SMBMon app probably needs to be updated to work properly with server 4.19 in any case...

 Comparing the logs for 'net rpc user' from the 4.15 and 4.19 server, it seems the 4.19 server doesn't even use the 'rpc' part - it is completely missing from the log...


Networking / Re: Updated Samba Client
« on: February 05, 2024, 10:24:22 pm »
 Thanks Dave! I forgot about that...

 Attached are the full results for the 4.15 and 4.19 servers...


Networking / Re: Updated Samba Client
« on: February 05, 2024, 12:19:00 pm »

 I see the same as you with server 4.19 with 'net rpc user -d 10' at the end:

gensec_update_send: spnego[20049570]: subreq: 2004b1a0
gensec_update_done: spnego[20049570]: NT_STATUS_OK tevent_req[2004b1a0/../../aut
h/gensec/spnego.c:1631]: state[2] error[0 (0x0)]  state[struct gensec_spnego_upd
ate_state (2004b2a0)] timer[0] finish[../../auth/gensec/spnego.c:2116]
 session setup ok
signed SMB2 message (sign_algo_id=2)
 tconx ok
     NetQueryDisplayInformation: struct NetQueryDisplayInformation
        out: struct NetQueryDisplayInformation
            entries_read             : *
                entries_read             : 0x00000000 (0)
            result                   : UNKNOWN_ENUM_VALUE (2152)
return code = 2152
Freeing parametrics:

 and server 4.15 shows at the end:

[0000] 00 00 00 00 00 00 00 00   00 00 00 00 00 00 00 00   ........ ........
[0010] 00 00 00 00 00 00 00 00                             ........
Got pdu len 48, data_len 24
rpc_api_pipe: got frag len of 48 at offset 0: NT_STATUS_OK
rpc_api_pipe: host localhost returned 24 bytes.
     samr_Close: struct samr_Close
        out: struct samr_Close
            handle                   : *
                handle: struct policy_handle
                    handle_type              : 0x00000000 (0)
                    uuid                     : 00000000-0000-0000-0000-000000000
            result                   : NT_STATUS_OK
Freeing parametrics:

 Couldn't figure out how to capture the whole thing - is there a way?

 I'll look at the Rexx code of the SAMBA Status Monitor (on the Netlabs Trac site) and see if I can figure out the actual SMBTREE command used there after work...


Networking / Re: Updated Samba Client
« 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.


Networking / Re: Updated Samba Client
« on: February 03, 2024, 10:04:43 pm »

  Client 20240127 seems to work fine...


Networking / Re: Updated Samba Client
« on: February 03, 2024, 09:31:38 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...   


Networking / Re: Updated Samba Client
« 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.


Networking / Re: Updated Samba Client
« 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?


Pages: [1] 2 3 ... 50