OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Networking => Topic started by: roberto on August 03, 2019, 12:03:57 pm
-
After a hardware problem, I buy a new computer, I restore the system. The first pc with intel E1000B the new pc with realtek 8111 ...
On the first boot I change with naps.exe the adapter all apparently fine.
I restore the net.acc
Ibm peer to peer is ok.
The tcp-ip is ok, it goes online ok.
The connection to NAS units with the browser is ok, both.
But the samba client gives me the error of the message title, and fails. Any suggestions?
-
Hi roberto
Sorry, no answers only questions...
Which driver did you select for the 8111?
What are you trying to connect to using the samba client?
Could it be a samba configuration or authorization problem due to change of nic/driver?
Regards
Pete
-
Which driver did you select for the 8111?
Realtek 8139C+/8169.... On this equipment, install another maintenance unit, only with tcp, to restore the data. And the connection was with that driver, and using the samba client without problems.
What are you trying to connect to using the samba client?
2 NAS disks
Could it be a samba configuration or authorization problem due to change of nic/driver?
Autorization NO,
Configuration ???
Regards
PD
With this system we don't get bored, it's really entertaining.
-
Hi roberto,
Is this a new install using ArcaOS 5.0.4? If it is you have hit the SMB update problem since most small NAS boxes are setup to use SMB v1and the AOS 5.0.4 is now set to use some other version the two won't communicate hence the error message.
There has to be a way of setting SMB back to using v1 but I haven't found it yet.
-
Hi All,
Is this a new install using ArcaOS 5.0.4? If it is you have hit the SMB update problem since most small NAS boxes are setup to use SMB v1and the AOS 5.0.4 is now set to use some other version the two won't communicate hence the error message.
There has to be a way of setting SMB back to using v1 but I haven't found it yet.
I really doubt the Samba client has been set to use SMB2+ only in AOS 5.0.4. There's nothing in my code to do this. If they have done this, the only place it could be is in %ETC%\samba\smb.conf
Look for something like:
min protocol = SMB2
Cheers,
Paul
-
Hi Paul,
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!
-
Ivan:
For clarity, the new computer will restore it with a backup made with RAR.
The rarlog showed 4 files not copied from the \ lock \ folder.
In C: and D: restore the files from one of the NAS drives. On E: the arca504 is installed and works perfectly with the two NAS drives.
The problem is when starting C: after restore arca503.
Paul:
Modifying the smb.conf with your suggestion I see no difference.
I attach the error log, I have only modified the password
From what I can see the problem is not in the samba,
but in the change of the network driver, but this is only a guess.
Thanks all
-
Hi roberto
It may be worth trying the alternative 8111 driver, MMRE.OS2, to see if that makes a difference.
Regards
Pete
-
No difference, what works in one works with the other and what fails in one fault in another.
The pci104vk program shows me how RTL8136, attached the detail.
-
A couple of thing to check:
First what protocol are you using to run Peer. If it is Netbios over TCP/IP this will prevent Samba from working, Remove netbios over TCP/IP and replace with Netbios.
Next how is the NAS accessed by name or by IP address. If it is by name you need to add this to your hosts file
(NAS 192.168.0.2 to X:\MPTN\ETC\hosts). Obviously use the correct values here.
You need to reboot after either of these changes
-
Hey Ivan,
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!
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.
-
Hey Ivan,
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!
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....
I suspect this change could be the reason for Ivan's issue (from Samba 4.7 changelog)
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
-
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
-
Hi Ivan,
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
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
-
Hi Paul,
I did as you asked and all I get is an empty file even after rebooting the computer.
-
Hi Paul,
I did as you asked and all I get is an empty file even after rebooting the computer.
Did you check in X:\var\log\ndpsmb.log ?
-
Hello Paul,
Just for trying to clarify
Some comments about arca504 and samba client.
The smb.conf file is in two places in
C:\MPTN\ETC\samba\smb.conf
C:\var\temp\smb.conf
The debug file is rooted in the system,C:\ndpsmb.dbg, but does not show anything or in my case a single line:
NDPSMB debug flag file
Marking the log, and debug option, in the arcamap shows a window that allows copy paste, which I know is the only way to get a log-file.
-
The smb.conf file is in two places in
C:\MPTN\ETC\samba\smb.conf
C:\var\temp\smb.conf
The file C:\var\temp\smb.conf Is a work file, in a temporary location. It is used by the program to fill out the defaulted (not defined) settings. Ignore it, although it can tell you what actual settings are being used. C:\MPTN\ETC\samba\smb.conf is the file that you would want to edit, to change default settings.
Note that C:\sys\apps\smbclnt contains the code used by the SAMBA client. It was updated with ArcaOS 5.0.4, and you will see a SYS0050 if that didn't get updated, or if your system has another copy somewhere, that isn't updated, or if your CONFIG.SYS points somewhere else (or...). The contents are:
[C:\SYS\APPS\SMBCLNT]dir
The volume label in drive C is ARCAOS.
The Volume Serial Number is DFDA:75BB.
Directory of C:\SYS\APPS\SMBCLNT
8-26-18 12:34p <DIR> 0 ---- .
8-26-18 12:38p <DIR> 0 a--- ..
8-26-18 12:34p <DIR> 0 ---- codepages
7-09-17 12:39a 4,128,772 0 a--- net.exe
7-09-17 12:39a 765,956 0 a--- nmblookup.exe
7-09-17 12:39a 3,739,652 0 a--- rpcclient.exe
7-09-17 12:39a 199 0 a--- smb.conf.sample
7-09-17 12:39a 3,567,620 0 a--- smbclient.exe
7-09-17 12:39a 1,867,780 0 a--- smbspool.exe
7-09-17 12:39a 3,481,604 0 a--- smbtree.exe
7-09-17 12:39a 716,804 0 a--- testparm.exe
11 file(s) 18,268,387 bytes used
2,651,516 K bytes free
Note that some of these file names are used in the SAMBA server too, but they are not, necessarily, the same files.
-
Hello Paul,
Just for trying to clarify
Some comments about arca504 and samba client.
The smb.conf file is in two places in
C:\MPTN\ETC\samba\smb.conf
C:\var\temp\smb.conf
The debug file is rooted in the system,C:\ndpsmb.dbg, but does not show anything or in my case a single line:
NDPSMB debug flag file
Marking the log, and debug option, in the arcamap shows a window that allows copy paste, which I know is the only way to get a log-file.
I have no idea why there's a smb.conf in c:\var\temp\smb.conf - the Samba code will only look in %ETC%\samba\smb.conf
If C:\ndpsmb.dbg exists - and ndctl.exe is restarted (this can be done in Arcamapper - the menu option is something like restart control daemon) then logs should be put into %LOGFILES%\ndpsmb.log - IIRC (I don't have an ArcaOS nearby) by default this is c:\var\log\ndpsmb.log
Hope this helps,
Paul.
-
The smb.conf file is in two places in
C:\MPTN\ETC\samba\smb.conf
C:\var\temp\smb.conf
The file C:\var\temp\smb.conf Is a work file, in a temporary location. It is used by the program to fill out the defaulted (not defined) settings. Ignore it, although it can tell you what actual settings are being used. C:\MPTN\ETC\samba\smb.conf is the file that you would want to edit, to change default settings.
Note that C:\sys\apps\smbclnt contains the code used by the SAMBA client. It was updated with ArcaOS 5.0.4, and you will see a SYS0050 if that didn't get updated, or if your system has another copy somewhere, that isn't updated, or if your CONFIG.SYS points somewhere else (or...). The contents are:
[C:\SYS\APPS\SMBCLNT]dir
The volume label in drive C is ARCAOS.
The Volume Serial Number is DFDA:75BB.
Directory of C:\SYS\APPS\SMBCLNT
8-26-18 12:34p <DIR> 0 ---- .
8-26-18 12:38p <DIR> 0 a--- ..
8-26-18 12:34p <DIR> 0 ---- codepages
7-09-17 12:39a 4,128,772 0 a--- net.exe
7-09-17 12:39a 765,956 0 a--- nmblookup.exe
7-09-17 12:39a 3,739,652 0 a--- rpcclient.exe
7-09-17 12:39a 199 0 a--- smb.conf.sample
7-09-17 12:39a 3,567,620 0 a--- smbclient.exe
7-09-17 12:39a 1,867,780 0 a--- smbspool.exe
7-09-17 12:39a 3,481,604 0 a--- smbtree.exe
7-09-17 12:39a 716,804 0 a--- testparm.exe
11 file(s) 18,268,387 bytes used
2,651,516 K bytes free
Note that some of these file names are used in the SAMBA server too, but they are not, necessarily, the same files.
Correction. The files in C:\sys\apps\smbclnt are NOT used by Netdrive or the Samba plugin. They are used for other ArcaOS components, like arcamapper and for printing support.
The only system files used by Netdrive and the Samba plugin are ndpsmb.dll and smbcln49.dll (and things like libc, et al).
Cheers,
Paul.
-
The only system files used by Netdrive and the Samba plugin are ndpsmb.dll and smbcln49.dll (and things like libc, et al).
Thanks Paul, I went looking in the NDFS directory and found NDCTL.LOG which gave:
NetDrive for OS/2(R) Control Program version 3.1.5.865 Apr 06 2017
NDFSDIR environment variable found: E:\Programs\NDFS
NetDrive working directory is E:\Programs\NDFS
File system driver name is NDFS32.
NetDrive configuration file 'E:\Programs\NDFS\ndctl.cfg' has been processed.
Exclusive Samba Use
[ local] internal plugin has been initialized.
NDF0033: The system can't load the module: SMBCLN49
NDF0029: [ ndpsmb] plugin has not been loaded.
NDF0007: The system error is SYS0002
Initialization completed. The control program is running.
So it appears that SMBCLN49.DLL is missing. Searching for it brings up a blank, I can only assume that the ArcaOS 5.0.4 didn't install it when it updated the ndplugs directory unless it is supposed to be somewhere else.
-
Hi Ivan, was this a full install or an upgrade?
Here (I don't use Samba so haven't tested), I only find it on a partition where I did a full install of the last beta, not where I did an update :( Possibly you need to install from the ISO RPM repository samba-client-4.9.5-2.oc00.i686.rpm. This should be brought to Arca Noae's attention in the form of a ticket as it is supposed to be part of ArcaOS 5.04.
-
Hi Dave, it was an update using the 'update' function of the ArcaOS 5.0.4 DVD.
Will look for the RPM you mentioned when I start the test computer again.
-
Couldn't find the RP so I went to Paul's site and downloaded the zip from there, extracted the SMBCLN49.DLL put it in the programs\ndfs\ndplugs directory, rebooted and all is well, I have connection back to my NAS boxes.
-
The only system files used by Netdrive and the Samba plugin are ndpsmb.dll and smbcln49.dll (and things like libc, et al).
Thanks Paul, I went looking in the NDFS directory and found NDCTL.LOG which gave:
NetDrive for OS/2(R) Control Program version 3.1.5.865 Apr 06 2017
NDFSDIR environment variable found: E:\Programs\NDFS
NetDrive working directory is E:\Programs\NDFS
File system driver name is NDFS32.
NetDrive configuration file 'E:\Programs\NDFS\ndctl.cfg' has been processed.
Exclusive Samba Use
[ local] internal plugin has been initialized.
NDF0033: The system can't load the module: SMBCLN49
NDF0029: [ ndpsmb] plugin has not been loaded.
NDF0007: The system error is SYS0002
Initialization completed. The control program is running.
So it appears that SMBCLN49.DLL is missing. Searching for it brings up a blank, I can only assume that the ArcaOS 5.0.4 didn't install it when it updated the ndplugs directory unless it is supposed to be somewhere else.
Well that would explain the lack of log file, and the error connecting. smbcln49.dll should be in the same directory as ndpsmb.dll
-
Hi Ivan,
Couldn't find the RP so I went to Paul's site and downloaded the zip from there, extracted the SMBCLN49.DLL put it in the programs\ndfs\ndplugs directory, rebooted and all is well, I have connection back to my NAS boxes.
I'd still be interested in a copy of the ndpsmb.log file to see what version of Samba your NAS is running.
Cheers,
Paul
-
Hi Paul,
See attachment
-
Found missing smbcln49.dll in : \sys\dll on install-dvd, copied to \usr\lib. Reboot and now the error message sys0050 is gone. Arcamap can connect with my NAS.
Gunnar Engell
-
Hey Ivan,
See attachment
Thanks... that must be a pretty old NAS:
"Server supports NT1 protocol"
Cheers,
Paul
-
I didn't see any bug reports for this in the Arca Noae bug tracker, so I raised https://mantis.arcanoae.com/view.php?id=2592
-
Hi Paul,
Yes, they are old but they just keep on working. I have 4 of them, 2 D-Link DNS-323 and 2 D-Link DNS-320, they are all on 24/7/365 and have been since late 2009. Two are on the network and the other 2 are remote and backup the network pair overnight using rsync.
Since the system has been working without problems why change?
-
Hi Ivan,
Yes, they are old but they just keep on working. I have 4 of them, 2 D-Link DNS-323 and 2 D-Link DNS-320, they are all on 24/7/365 and have been since late 2009. Two are on the network and the other 2 are remote and backup the network pair overnight using rsync.
Since the system has been working without problems why change?
No reason to change what isn't broken, but security does become a concern. Presumably your two remote NAS are connected via VPN which will help mitigate any security issues from an old Samba release...
-
Hi Paul,The original remote setup was the testbed for some clients but it has evolved over the years and I now use a TP-Link TL-R600VPN dedicated VPN and Firewall unit which does make it more secure as well as easier to manage.
Thanks for your help. if you hadn't mentioned the two DLLs I would have been reverting back to the much older version.
-
Ivan, you really should log into https://mantis.arcanoae.com/view.php?id=2592 (https://mantis.arcanoae.com/view.php?id=2592) using your Arca Noae creds with the part after @ in your user name and supply the upgrade logs so this problem can be fixed in the future. Complaining here or down leveling when things go wrong does not lead to fixes.
-
Hello Ivan
It's lucky to arrive for a few days on vacation and find the solution to the problem.
My case was a little different, but the solution has been the same.
After restoring the system, the ndfs program log said that the smbcli49.dll was missing, when I had the smbcli47.dll
Thank you all
-
Hello Ivan
It's lucky to arrive for a few days on vacation and find the solution to the problem.
My case was a little different, but the solution has been the same.
After restoring the system, the ndfs program log said that the smbcli49.dll was missing, when I had the smbcli47.dll
Thank you all
Question to those that had the issue after upgrading to 5.0.4. Had you installed any of my test builds of the Samba plugin, or were you running the version that came with ArcaOS?
If you can add your feedback to https://mantis.arcanoae.com/view.php?id=2592 it would help fix this for others.
Cheers,
Paul