OS/2, eCS & ArcaOS - Technical > Networking
ArcaMapper and Network Protocols
Mark Szkolnicki:
--- Quote from: Paul Smedley on January 20, 2024, 01:45:45 am ---
--- Quote from: Neil Waldhauer on January 17, 2024, 03:25:07 pm ---Both of Mark's servers are old. The new client demands more security, and perhaps the servers aren't offering it. You can reduce the client demand for security by adding this line to smb.conf
client min protocol = NT1
--- End quote ---
NB: This only impacts the version of the protocol protocol - some of the authentication methods (eg lanman) are also deprecated and need to be forced on.
--- End quote ---
Hi Paul!
Was a busy 5 days guest entertaining and interacting - but its now Monday and back to tech troubleshooting ............
Modified smb.conf with the following (cut and pasted the statements you provided):
# 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 = 0
client lanman auth = no
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = no
(I retained the format that was present in the original version of SMB.conf below, as I expected syntax may be sensitive to how it was formatted - cutting and pasting this seems to have dropped some space(s) in front of the statements
The original SMB.conf only contained the following:
# 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 = 0
client min protocol = NT1
After making those modifications, rebooted and attempted to mount one of the shares on the Ready NAS Pro6, and received the same access denied message.
This was done in concert with Alex's suggestion about OPTIONS, but also did not work with the original default logon OPTIONS settings.
Its been quite a while since I accessed the ReadyNAS through the software admin package included with it called "RAIDar", but did that on the weekend to see how I set things up (in 2010 I knew little about RAID systems, so it was interesting seeing what I had done then)
The ReadyNAS could be set up for all or just a limited set of standard file sharing protocols of the time, including CIFS, NFS, AFP, FTP, HTTP and HTTPS. I saw that I chose CIFS for all (or perhaps that was a default added by the system), and AFP and HTTPS as well for a couple of the shares.
The shares I am most interested in mounting are all associated with CIFS on the ReadyNAS, if that helps a little more to isolate the access problem. I did try three separate User / Password sets that I created to log on to the ReadyNAS for those shares, and all of the accesses were denied.
I am curious about two things related to Samba and credentials, if anyone can enlighten me -
1) Two of the three User Names have more than ten letters in them and a strong level of password with more than ten characters in them. These are recognized no problem logging into the ReadyNAS through Windows, but is there a limit in User Name or Password as to number of characters that may be used in ArcaMapper?
2) One of the three User Names (paladin) is the same as I use to log into the workgroup (named PALNET) but with a different password - in that case originally playing with ArcaMapper, I did receive an error message saying "paladin is already logged on" if I used the different User / Password combination. In Windows I log on the "paladin" user name to access the system, and then access the ReadyNAS using "paladin" and the different password, so not sure if ArcaMapper handles that differently.
Anyway that summarizes my latest efforts - if anyone has any other ideas to try, I'm all ears.
Best of the Rest of the Week!
Mark
Alex Taylor:
Perhaps you could see if the following combination of options gets you anywhere:
--- Code: --- client lanman auth = yes
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = yes
--- End code ---
Mark Szkolnicki:
Heh Alex!
--- Quote from: Alex Taylor on January 23, 2024, 05:06:11 am ---Perhaps you could see if the following combination of options gets you anywhere:
--- Code: --- client lanman auth = yes
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = yes
--- End code ---
--- End quote ---
Thanks! Will try it.
Paul gave me a link to a site explaining the implications of some of the statements, but had no time yesterday to follow up. I was thinking along the same lines, as I was assuming from some of Paul's explanation that certain services may need to be present and enabled explicitly in SMB.conf, not disabled - we will see if that is indeed the case
Mark Szkolnicki:
Heh Alex!
--- Quote from: Alex Taylor on January 23, 2024, 05:06:11 am ---Perhaps you could see if the following combination of options gets you anywhere:
--- Code: --- client lanman auth = yes
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = yes
--- End code ---
--- End quote ---
Tried a number of things today - again no joy.
I think they were really good suggestions, Alex but still get the "no access" error message, regarding the credentials - if the ReadyNAS Pro 6 is seen clearly by ArcaMapper seen as a resource, there must be something I'm missing - tried a number of permutations of statements in SMB.conf (after reading the information in the link Paul provided) as well as your suggestions in OPTIONS, and using various User_Name/ Password combinations, including one new one within the 8.3 character limit, with a simple password (8 character), which I created - again nothing.
But as always, we soldier on - and learn from every success and failure.
Banging your head against a wall is painful ........... but if you learn something in the end, always somewhat rewarding ..............
M
Paul Smedley:
Client logs might help us understand more.
Add to smb.conf:
log level = 8
Create a file in the root of the OS drive - ndpsmb.dbg
Reboot or restart ndctl.exe
try to connect
zip/share x:\var\log\log.ndpsmb & x:\var\log\log.smbc
Once logs are captured - you can reset log level and remove x:\ndpsmb.dbg
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version