OS/2, eCS & ArcaOS - Technical > Networking
Samba client error sys0050 The network request is not supported.
Paul Smedley:
Hey Ivan,
--- Quote from: ivan on August 04, 2019, 12:51:02 pm ---All I know is that I used the 'update' option of the ArcaOS 5.0.4 DVD on one of my test machines and now I can't connect to my NAS boxes from that machine (always get a SYS0050 error message). I also know a number of friends also lost connection to their NAS boxes when MS updated win 10 to default to SMB v2 and the workround was to reset SMB back to v1.
I suppose I could copy over a working Samba from another of my computers but that doesn't solve the problem (all the other un-updated computers have no problem connecting to the NAS boxes).
Something has changed but the question is what!
--- End quote ---
There was a change to authentication around Samba 4.7 or 4.8 timeframe if I recall correctly (I'll try remember what it was).
IIRC the version of the Samba client in used changed from v4.4.x to v4.9.x in 5.0.4....
Meanwhile, logs would be useful....
Cheers,
Paul.
Paul Smedley:
--- Quote from: Paul Smedley on August 05, 2019, 05:16:05 am ---Hey Ivan,
--- Quote from: ivan on August 04, 2019, 12:51:02 pm ---All I know is that I used the 'update' option of the ArcaOS 5.0.4 DVD on one of my test machines and now I can't connect to my NAS boxes from that machine (always get a SYS0050 error message). I also know a number of friends also lost connection to their NAS boxes when MS updated win 10 to default to SMB v2 and the workround was to reset SMB back to v1.
I suppose I could copy over a working Samba from another of my computers but that doesn't solve the problem (all the other un-updated computers have no problem connecting to the NAS boxes).
Something has changed but the question is what!
--- End quote ---
There was a change to authentication around Samba 4.7 or 4.8 timeframe if I recall correctly (I'll try remember what it was).
IIRC the version of the Samba client in used changed from v4.4.x to v4.9.x in 5.0.4....
Meanwhile, logs would be useful....
--- End quote ---
I suspect this change could be the reason for Ivan's issue (from Samba 4.7 changelog)
--- Code: ---The 'ntlm auth' option default is renamed to 'ntlmv2-only', reflecting
the previous behaviour. Two new values have been provided,
'mschapv2-and-ntlmv2-only' (allowing MSCHAPv2 while denying NTLMv1)
and 'disabled', totally disabling NTLM authentication and password
changes.
@Ivan do you know what Samba version your NAS is running? Connecting to it with smbclient should show it.
Cheers,
Paul
--- End code ---
ivan:
Hi Paul,
All the small D-Link NAS boxes are using SMB v1 with no possibility of wver changing that to anything higher. There were a lot of problems on the the various NAS forums when MS changed the default to SMB v2 in win 10 hence my asking how to do that in ArcaOS v5.0.4
Paul Smedley:
Hi Ivan,
--- Quote from: ivan on August 06, 2019, 09:05:53 am ---All the small D-Link NAS boxes are using SMB v1 with no possibility of wver changing that to anything higher. There were a lot of problems on the the various NAS forums when MS changed the default to SMB v2 in win 10 hence my asking how to do that in ArcaOS v5.0.4
--- End quote ---
Samba still defaults to allowing SMB1. Can you enable debug logging for the Netdrive plugin (create a file NDPSMB.DBG in the root directory of your boot drive), restart ndctl using Arcamapper, try to connect to the D-Link NAS then send me the resulting ndpsmb.log ?
Cheers,
Paul
ivan:
Hi Paul,
I did as you asked and all I get is an empty file even after rebooting the computer.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version