OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Martin Iturbide on December 08, 2016, 05:57:27 pm
-
Hi
I noticed the new samba news and I'm installing to try it out.
It says to install "REXX libraries 1.1.1" as a requirement. (rxlib4smb.wpi) (12/07/2012)
I found two DLLs that are different in size from the ones I got.
- VROBJ.DLL
- PR1UTIL.DLL
I want to validate which is the latest version of these DLL's and correct size.
Regards
-
For VX-REXX VROBJ.DLL the internal version number must be 2.1d. It really dates from 1995, when VX-REXX development was stopped by Watcom.
The one that you got is likely not lxlited and definitely has a false date stamp.
For PR1Util.DLL I cannot rule out that I overlooked a version, I will check that.
-
Hi
I checked the one on Paul R's website (http://home.clara.net/orac/os2.htm#pr1util) and it is this one:
08-19-2010 7:06p 37,685 181 a--- pr1util.dll
The readme says it is version V1.65, while rxlib4smb.wpi installer says it will install version 1.64.
If it does not produce problems with Samba, I think that "pr1util.dll" should be updated on "rxlib4smb.wpi".
Regards
-
Martin,
I will be interested in if you get this server running. So far, I have not been able to, but I need to spend more time on it. Keep getting a 'could not find a valid language file' error when I try starting the Samba Status Monitor and NMBD always craps out at startup with this error:
[2016/12/08 17:07:43.529000, 0] lib/util_sock.c:667(open_socket_in)
bind failed on port 137 socket_addr = 192.168.0.255.
Error = Can't assign requested address
[2016/12/08 17:07:43.529000, 0] nmbd/nmbd_subnetdb.c:127(make_subnet)
nmbd_subnetdb:make_subnet()
Failed to open nmb bcast socket on interface 192.168.0.255 for port 137. Error was Can't assign requested address
[2016/12/08 17:07:43.529000, 0] nmbd/nmbd.c:989(main)
ERROR: Failed when creating subnet lists. Exiting.
It never shows a running server in the 'Find SMB Machines' app either...
I was running version 3.6.24 with no trouble previously (which was deleted before install of new version 3.6.25).
-
Hi Herwig,
Using your WPIVIEW (thanks for that) I see that the rxlib4smb.wpi is set to put everything into subdirectories of ecs which is OK for those running eCS but what does it do for those of us that are running OS/2 v4.52 (CP2) and don't have an ecs directory?
I'm asking this before running the wpi in case it messes up our test system.
Another point the vrobj.dll we have is 900,545 dated 27/08/96 but shows itself as v2.14 of 01/09/95. Can I assume it is the correct one?
-
Got a little farther... for some reason SAMBA was trying to change the IP of my computer from the static 192.168.0.2 to 192.168.0.100 handed out by the local DHCP server (on my router). I found that if I replaced b4smb.cmd with the one from the SAMBA 1.2.0 package, this did not happen and I can see the server running in the 'Find SMB Machines' app. 'Network Neighborhood' on the server shows everything including shares too. No idea if this is wise, but it avoids the attempted IP change.
On my clients, now the server shows up, but none of the shares do and so I can't mount any of them. Have to keep digging...
-
Regarding the rx4smblib directories on OS/2 (and later ArcaOS)
- Rather sooner than later this will be available as a rpm/yum package and therefore end up in %unixroot%\usr\lib, however we do not endores to put stuff manually there.
- I suggest to put them in \os2\apps\dll or \os2\dll on "pure" OS/2 4.52 systems for now.
As for the version number of vrobj.dll: Watcom couldn't really decide which version number scheme to use - 2.14 = 2.1d (d being 4th in a b c d). Both schemes are found within the product. The 900k version is not lxlited, but otherwise correct.
-
Dave,
what you see are genuine TCP/IP problems, not Samba.
Please note:
1.) http://searchitchannel.techtarget.com/tip/Assigning-an-IP-address-ending-in-0-or-255
2.) the nmbd stuff (which is responsible for browsing and "seeing" stuff is cached in various buffers in various machines - changing the IP of a running server ist asking for troubles - I know that from my own (test) setups. I may take some time until an IP change has spread to every machine on a network.
-
Herwig,
I agree there is a TCPIP problem.... but it only happens when I try to start the SAMBA server 1.3.0. Version 1.2.0 worked fine. My IP address is 192.168.0.2. For some reason starting the 1.3.0 server causes the IP address to change to whatever the DHCP server gives it. Replacing b4smb.cmd with the version from 1.2.0 stops that, so there must be something in b4smb.cmd that is requesting an IP address from the DHCP server. I haven't yet scrutinized b4smb.cmd to try to figure it out....
Regards,
-
Hello,
I confirm the problem reported by David and find the same logfile entries. The previous Samba versions worked just fine.
Best regards, Harald
-
b4smb.cmd is just a "plugin" - a script just run before Samba. No change intended there AFAIR.
-
Maybe the dhcpstrt has something to do with it. I don't think that is what you want on a fixed IP server, at least we don't.
if DHCPWait then do /* Make sure we got network interfaces up and running */
address cmd' dhcpstrt'
end
-
dhcpstrt is not related to the problem, afaics. Commenting it out doesn't change the situation, at least on my system. I don't understand why nmbd tries to bind on the socket address 192.168.178.255 instead of 192.168.178.21:
[2016/12/09 19:01:28.402000, 0] lib/util_sock.c:667(open_socket_in)
bind failed on port 137 socket_addr = 192.168.178.255.
Error = Can't assign requested address
Where is this configured? Or is it even hardcoded?
-
Well, I seem to have gotten it working. Opened b4smb.cmd in a text editor and near the top of the file there is a line:
DHCPWait = 1 /*Wait until an address was obtained by the DHCP server*/
Set '1' to '0' and the IP address change craziness is gone. Server seems to start OK.
I installed the server using defaults, but when I run 'smb test' I get 2 errors for deprecated settings that were automatically set. So I turned OFF 'Null Passwords' (using SSCC) under 'Global' and turned ON 'Share Modes' under 'Netlogon'. Errors are now gone.
Also all my drives were setup and shared by default, but they are setup as, for example, 'C:\', but this is wrong, it should be 'C:'. This can be changed just by browsing for the drive by clicking on the folder to the right.
Now I can connect to shares on my clients and browse the directories. I'll try sharing and connecting to a printer next....
Thanks Herwig and everyone at Netlabs for making SAMBA on OS/2 possible!
-
I have put up a (final) updated WPI for rx4smb.wpi ftp://ftp.netlabs.org/pub/samba/server/rxlib4smb.wpi
- updated pr1util from 1.64 to Paul Ratcliffes last 1.65
- added Alex Taylor VROBJEX.DLL as it is used by all the Samba GUI Tools
Just a sidenote: All efforts to provide the updated Samba Server package were done by bitwise works.
-
The updated rxlib4smb.wpi still contains pr1util.dll version 1.64.
-
Hi Herwig,
Thanks for the update, and please forgive my Netlabs/BitwiseWorks confusion. One thing I just noticed is that there is no winbindd.exe file in the 1.3.0 wpi. Is that intentional? I have a previous 3.6.24 archive that includes one...
Regards,
-
Dave,
no excuse needed ;-) Netlabs host many projects and Adrian still provides access rights. However the work behind most of the stuff is doen by bitwisers.
Regarding winbindd.exe - we did not put it in as it is completely untested. The same applies to its companion wbinfo.exe.
We have built both files, so I can but them into a separate package.
Cheers,
Herwig
-
Thanks, Herwig. Be glad to try out winbindd if you like.
Regards,
-
Keep getting a 'could not find a valid language file' error when I try starting the Samba Status Monitor ...
David did you fix this error? I'm getting the same here.
-
Greggory,
No... but so far it seems harmless. I never got it before... should look at the last version of the status monitor, maybe there is something obviously missing that could be inserted in the new one...
-
It turns out that there are *.hlp files missing from the server 1.3.0 wpi. Went to ftp://ftp.netlabs.org/pub/samba/server/guitools and got the most recent smbmon*.zip. Copied the *.hlp files from that to my SAMBA directory and now that error is gone...
-
In case anyone is interested... was able to get SWAT running, but had to make minor changes to the file /Samba/swat/index.html to get it to display. Added a '/' in front of both instances of 'cgi' and removed 'swat/' from in front of 'images' so now the contents of index.html' are:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<meta http-equiv="refresh" content="2; URL=/cgi-bin/samba/swat.exe/"></head>
<body><h1><img style="width: 230px; height: 106px;" alt="Samba" src="images/samba.gif"><br></h1><br><a href="/cgi-bin/samba/swat.exe/">Samba Web Adminstration Tool
(SWAT)</a></body></html>
-
Hi David,
Did you manage to get SMB printing to work? So far it does not do anything for me yet I can use samba printing from a win XP VM without any problems.
-
Ivan,
I have not... the print job gets to the SAMBA spooler, but then just sits there. I suspect there may be an issue with the 'command' lines in smb.conf, but I can't seem to find a log file for the printing attempt (if any). Need to read more about it...
-
@David McKenna: Looks like you are missing the smbprint.exe utility. It wasn't included, sscc however assumes, it is there. Sorry, here it is: ftp://ftp.netlabs.org/pub/samba/server/guitools/smbprint-030-20161213.zip
Rx4Smb.WPI has been updated once more yesterday (really updated outdated pr2utill.dll)
ftp://ftp.netlabs.org/pub/samba/server/rxlib4smb.wpi
We accidentally disabled winbind building some time ago.
Here is the winbind package ftp://ftp.netlabs.org/pub/samba/server/winbind-1.3.0.1-982.zip
-
Thanks Herwig! Everything seems to work now with your new packages. Printing works to my OMNI Deskjet (thanks for the instructions in the readme), but I can't figure out how to use CUPS. I assume I will need Printing = CUPS in smb.conf, but what goes in the section for the printer? Do I use the CUPS queue name, or the printers' name on the desktop? What driver do I use in CUPS (saw something on the web about using a RAW driver)? Any advice for CUPS with SAMBA would be greatly appreciated...
Regards,
-
I had that running in a test env some time in the past - however that is long gone (tdb stuff made everything other stall for a long time :-( ).
While some Samba/CUPS info ist definitely on my todo-list, it simply does not exist yet.
As soon as I start this will be my starting point https://wiki.samba.org/index.php/Setup_a_Samba_print_server
-
...
On my clients, now the server shows up, but none of the shares do and so I can't mount any of them. Have to keep digging...
Hi David,
I have the same issue of not seeing any shares on my server from my client machine, any luck ?
1) I deleted Samba 3.6.24 with settings and installed 3.6.25 on my media server. Install samba on a test machine and still a no go on seeing the media server shares.
2) Also on a new install of Samba, I specified a different WORKGROUP name but that wasn't added to the 'smb.conf' file or the NETBIOS of the computer either.
3) No problem accessing Samba 1.3 from Win 10 or an OS/2 machine without Samba 1.3 installed (even tired with Samba 4 client).
4) With the Samba 4 client installed I get the message when trying to access the servers:
(Error NT_STATUS_IO_TIMEOUT)
Is anyone else having these problems ?
Thank you to the developers for all the work on Samba everyone
-
A few thoughts:
Seeing a server but not its shares: This may be a result of disabling the guest account and/or denieing browsing rights to it.
EVFSGUI shows in which user context the browsing is done. Usually it tries both, context of the logged in user and guest. In case there is no login, the context will be guest only.
The guest account is mandatory.
-
A few thoughts:
Seeing a server but not its shares: This may be a result of disabling the guest account and/or denieing browsing rights to it.
....
I think I found the issue when I use the command: yum install libc libcx libgcc1 cups-libs popt-libs gettext-libs zlib readline
I overwrote Paul version of libcx, my fault.
Samba 1.3 and Paul's Samba client installed and working great (with Win 10 too) !
Thanks
Greggory