OS/2, eCS & ArcaOS - Technical > Networking
ArcaMapper and Network Protocols
Mark Szkolnicki:
Hi Alex!
Long time no talk!
--- Quote from: Alex Taylor on January 18, 2024, 12:34:36 am ---In the New Connection dialog, select the "Options" button and try the following connection settings:
* Enable encryption: turn OFF
* Enable NTLMv1: turn ON
--- End quote ---
Tried you suggestion, Sir ................. AND IT WORKED!
I should say though it worked ......... but only partially.
I now can access at Least one of the Windows machines, a portable running Windows 7 - the ReadyNAS is still not accessible for mounting and logon.
I've attached a picture showing the Network Browser, when I display the resources available on MEMORY ALPHA - I don't know where ArcaMapper gets the information but it shows it as a UNIX based system in the bottom left of the window. As it is circa 2010, but still functions perfectly, I assume that the problem may be one of two things:
1) the credentials are still not being recognized
2) something may be different related to the network protocols it recognizes
Any idea, anyone, as to what those protocols may have been?
Best!
Mark
roberto:
--- Quote from: Mark Szkolnicki on January 18, 2024, 04:59:11 pm ---I now can access at Least one of the Windows machines, a portable running Windows 7 - the ReadyNAS is still not accessible for mounting and logon
Mark
--- End quote ---
Is ReadyNAS in WORKGROUP?
In all cases you can put the ip of your ReadyNAS without Workgroup, similar //IP/folder
Saludos
Paul Smedley:
--- Quote from: Mark Szkolnicki on January 18, 2024, 04:59:11 pm ---I should say though it worked ......... but only partially.
I now can access at Least one of the Windows machines, a portable running Windows 7 - the ReadyNAS is still not accessible for mounting and logon.
--- End quote ---
You mention the NAS is circa 2010? It will be running an ancient version of Samba, and probably using an authentication mechanism that has been deprecated in Samba 4.x
It may be worth trying adding some or all of the following to smb.conf - and either rebooting, or killing and restarting ndctl.exe before re-trying:
--- Code: ---client lanman auth = no
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = no
--- End code ---
Note that it's worth reading https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html to understand that the impact of these switches is, in terms of network security.'
If all this fails, I'd be suggesting we work through enabling debug logging for the Netdrive plugin which should show the issue - I'm pretty confident though, that it's a mismatch in authentication protocols due to increased security in the Samba client included in AOS.
At some point (probably Samba 5.0) all the code for support of SMB1 will be removed, as opposed to being deprecated.
Mark Szkolnicki:
Saludos to you as well Roberto
--- Quote from: roberto on January 18, 2024, 07:01:24 pm ---
--- Quote from: Mark Szkolnicki on January 18, 2024, 04:59:11 pm ---I now can access at Least one of the Windows machines, a portable running Windows 7 - the ReadyNAS is still not accessible for mounting and logon
Mark
--- End quote ---
Is ReadyNAS in WORKGROUP?
In all cases you can put the ip of your ReadyNAS without Workgroup, similar //IP/folder
Saludos
--- End quote ---
The ReadyNAS is the system listed as MEMORY ALPHA under PALNET which is the name of my Network workgroup as seen in the graphic I provided, I have it as a storage location for archiving files from all of my systems, as backup.
M
ivan:
Both of my NAS boxes (DNS-323 and DNS-320) are accessible from all my computers on the local network including OS/2, ArcaOS and Linux mint using the code Paul supplied on the Linux boxes.
For those that might be concerned that I am leaving the network open to the world I have it behind a TP-Link R600VPN v4 unit.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version