OS/2, eCS & ArcaOS - Technical > Networking
ArcaMapper and Network Protocols
Mark Szkolnicki:
Good Morning, Paul
(my time)
--- Quote from: Paul Smedley on January 26, 2024, 04:14:12 am ---Hey Mark - glad we're making progress - if you re-enable log level in smb.conf, and recreate ndpsmb.dbg and capture a log - the full log may tell us what the authentication problem is and guide how to fix it.
--- End quote ---
I was thinking the same thing - I actually hadn't disabled ndpsmb.dbg at all, so planning to run a number of new tests today. I'm also wondering after reading up on the link you provided, whether it may be useful to create a (Home) resource section in smb.conf specifically related to the ReadyNAS.
Will get back here soon and Best, Sir!
M
Mark Szkolnicki:
Heh Paul!
--- Quote from: Paul Smedley on January 26, 2024, 04:14:12 am ---Hey Mark - glad we're making progress - if you re-enable log level in smb.conf, and recreate ndpsmb.dbg and capture a log - the full log may tell us what the authentication problem is and guide how to fix it.
--- End quote ---
So this is where we seem to have advanced to, Sir:
Entering the IP as the UserName and the password for user "Paladin" the error message this time in log.ndpsmb is:
2024/01/26 11:52:44.42: 4 2: MEMORY-ALPHA2024/01/26 11:52:44.43: 4 2: session setup ok. Sending tconx <archive> <********>
2024/01/26 11:52:44.43: 4 2: tree connect failed: NT_STATUS_ACCESS_DENIED
So login has occurred successfully and the session is set up, but if I'm reading this correctly it can't see the organizational structure of the resource.
That would make sense, as a blank mount was created - i.e. the ArcaMapper drive shows nothing in it (window empty when opened).
Attached that log and the latest log.smbc (both in .txt format)
That was with smb.conf:
# Samba Configuration file for Clients
# Required place for this file %ETC%\samba\smb.conf
# Change the value of WORKGROUP according to your needs
[global]
workgroup = PALNET
loglevel = 8
client lanman auth = yes
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = yes
Was also wondering, Paul, if you had ever used or seen used the "Interface" parameter, in smb.conf? As mentioned previously, I was wondering if setting up a [home] section for the ReadyNAS in smb.conf, with Interface and potentially other parameters would potentially be a solution for this?
As the Windows systems seem to connect fine to ArcaMapper, perhaps also moving client lanman auth and client plaintext auth, if needed, would also be appropriate specifically for the ReadyNAS resource under a [Home] section?
Just lateral thinking again,
M
Paul Smedley:
Given we're now seeing a connection (which we weren't previously), and that Windows can connect without modification, I would remove the following from smb.conf:
--- Code: --- client lanman auth = yes
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = yes
--- End code ---
and try with the defaults. Is that the full log.smbc? It seems shorter than I would expect...
Mark Szkolnicki:
--- Quote from: Paul Smedley on January 26, 2024, 09:56:51 pm ---Given we're now seeing a connection (which we weren't previously), and that Windows can connect without modification, I would remove the following from smb.conf:
--- Code: --- client lanman auth = yes
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = yes
--- End code ---
and try with the defaults. Is that the full log.smbc? It seems shorter than I would expect...
--- End quote ---
As to log.smbc I noted that too - I was expecting it to show an error at the bottom, but it was like it just ended abruptly - thought I'd let you see it as is first - will run it again and see what happens
M
Mark Szkolnicki:
Hi Paul!
--- Quote from: Paul Smedley on January 26, 2024, 09:56:51 pm ---Given we're now seeing a connection (which we weren't previously), and that Windows can connect without modification, I would remove the following from smb.conf:
--- Code: --- client lanman auth = yes
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = yes
--- End code ---
and try with the defaults. Is that the full log.smbc? It seems shorter than I would expect...
--- End quote ---
Ran the logon three times with the paladin credentials, Paul - log.smbc ended each time at the statements you saw in the one I sent.
As to removing the smb.conf statements - taking all of them out and I couldn't see the resources in the Network Browser - I suspect I have to retain the client min protocol = NT1, but no time tonight to test.
M
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version