OS/2, eCS & ArcaOS - Technical > Networking

[fixed] NetDrive can't load module smbcln47??

(1/2) > >>

Mathias:
Hello together,

worked until yesterday or so.. and now I try to mount a samba share, and it tells me about a network error. :o
Okay.. so I went and tried net use on the prompt... which also says something about error 50.

In the end I went and had a look at netdrive.. which works. I can attach and detach.
But: ndctl says:

--- Code: ---NetDrive for OS/2(R) Control Program version 3.1.5.865 Apr 06 2017

NDFSDIR environment variable found: C:\Programs\NDFS
NetDrive working directory is C:\Programs\NDFS
File system driver name is NDFS32.
NetDrive configuration file 'C:\Programs\NDFS\ndctl.cfg' has been processed.

Exclusive Samba Use

[   local] internal plugin has been initialized.
NDF0033: The system can't load the module: SMBCLN47
NDF0029: [  ndpsmb] plugin has not been loaded.
NDF0007: The system error is SYS0002
Initialization completed. The control program is running.
NDF0016: Can't connect to file system driver.
NDF0015: NetDrive Control Program is already running.
--- End code ---

The last two lines appear to be normal. On a second ArcaOS machine I did the same things, compared the output .. and it worked out there.

So.. I have two questions now:
1) what is SMBCLN47?
2) How to get that thing working again?

Config.sys wise...
- C:\PROGRAMS\NDFS is in LIBPATH
- C:\PROGRAMS\NDFS is in PATH
- IFS=C:\Programs\NDFS\NDFS32.IFS is set in config.sys and DOES exist on the file system (no error at OS boot, Net Drive message displays properly)
- SET NDFSDIR=C:\Programs\NDFS is set

Didn't change a thing, that I am aware of. Well.. I installed an update today via ArcaNoae Packet Manager: poppler (which should imo only have to do with PDF stuff)

Any ideas? @_@

ivan:
Did you check that ndfs32.ifs is still in the 'programs\NDFS\ directory?  If not it should be and you need to find it and put it back there.

As an aside, I am very careful with using rpm/yum because it can mess up things. I learned that way back when I was using SUSE Linux and it was the reason I moved over to Linux mint and its 'deb' packages.

BTW,
SYS0002: The system cannot find the file specified.

EXPLANATION: The file named in the command does not exist in the
current directory or search path specified or the file name was
entered incorrectly.

ACTION: Retry the command using the correct file name.

Mathias:
Yes, indeed. The ndfs32.ifs is still in that path.

Also it loads fine when the machine starts up. Displaying as normal at boot:

--- Code: ---NDFS32 NetDrive for OS/2 File System Driver (Large Files), V3.028
--- End code ---

roberto:
You could try changing these files, this is part of a previous ticket. Comment if it works for you or not.

In the C:\usr\lib\ these two dlls appeared

smbcln47.dll │ 9910862│28/04/18│10:19a
smbnetap.dll │ 267180│28/04/18│10:45a

Copy these four files, to c: \ usr \ lib Overwriting those of the same name and everything seems fine.
smbcln49.dll │ 9963156│09/06/19│10:00a
smbcln49.map │ 881613│09/06/19│10:00a
smbnetap.dll │ 264069│24/03/19│ 1:33a
smbnetap.map │ 83288│24/03/19│ 1:33a

Dariusz Piatkowski:
Hi Mathias,


--- Quote from: Mathias on February 06, 2020, 02:18:48 pm ---...

--- Code: ---[   local] internal plugin has been initialized.
NDF0033: The system can't load the module: SMBCLN47
NDF0029: [  ndpsmb] plugin has not been loaded.
NDF0007: The system error is SYS0002
Initialization completed. The control program is running.
NDF0016: Can't connect to file system driver.
NDF0015: NetDrive Control Program is already running.
--- End code ---

...

So.. I have two questions now:
1) what is SMBCLN47?
2) How to get that thing working again?

--- End quote ---

Does 'smbclient --version' at CLI return anything?

This will tell you what verison of Samba client you have installed.

The DLL you show is part of the Samba client install, on my machine it is part of a working 4.10.10 release.

Now, not sure if this is your issue but I've been consistently seeing the following with my NetDrive: all of a sudden my Samba connections just go 'dead'. As in, no WPS/Drive objects anywhere (which normally bring up NAS or other LAN boxes storage devices) show-up.

To fix I have to kill NDCTL, re-start NDCTL and all seems to be good. No trap anywhere, it's almost like something about the Samba client (or NDCTL) just dies.

Navigation

[0] Message Index

[#] Next page

Go to full version