Basic Install of Samba Server 1.3 on ArcaOS

The install and configuration of Samba Server 1.3 is a bit confusing. I am simply thankful that BWW took the time to port Samba and hope they continue to maintain the port.

This assumes ArcaOS 5.x and Samba Server 1.3 from Netlabs. This version of Samba branch is older... 3.6 the GA Samba at the time of writing this is 4.6.

How to Install
Samba Server can be selected to install during the original install of ArcaOS or later after the initial install. The selection during install is simply a check box on the Configure Networking / Install network services screen.



If you install later you can download the latest version from:

http://trac.netlabs.org/samba

The download is a Warpin install. It is fairly simple click through to install. After Samba is installed the configuration is “bare bones”. There are no admin or user accounts created, and there are no shares created

kLIBC User Management
The users are: root, guest, nobody, and a real user such as yourself. The users are created with a tool named: kLIBC User Management. It will appear after Samba is installed in the Programs group. Look in the Programs and you will see: bitwiseworks Apps and Ports
 * Before we go into Samba we need to create some users to make Samba work.



It can be started from a OS/2 command prompt. Open a OS/2 command prompt and enter: klusrmgr.exe
 * If for some reason you don't find kLIBC User Management program:

Open bitwiseworks Apps and Ports and you will see another folder to open:



Now you will see kLIBC User Management:



Start kLIBC User Management and you will see the defaults that were set from the initial install of ArcaOS. If you have not used this program before there will be some odd things. Only three users and some defaults that say “Missing message 193!”. Don’t worry this is normal. We will correct these omissions.



Let’s start with the user root. That is the system administrator login. Select root and then click Edit user. Correct the Full Name and add a password into the two fields Note: this password is something you need to remember and store in your password vault. I recommend something like KeePassX



Correct the guest account with name and password. Then add a user named:    nobody And have at least one user name for yourself. When finished the dialog should look something like this:



Then click Save and Exit

OS/2 Command prompt
Now we need to assign password for those users in Samba. There is a command line program to do this initial setup. There is a GUI for this process but it does not function until Samba is running, and we have not configured Samba yet. Open up a command prompt and enter:  cd \Programs\Samba then:   smbpasswd –a root You will get prompted to enter the password and verify. Do this for root, guest, and your username:



Simple Samba Configuration Center
Now we can start to use the Samba configuration program. To start the configuration open the Simple Samba Configuration Center:



The first time you open the Configuration Center you get a dialog to install libraries using YUM. It is a good idea to use this option to get ArcaOS updated for Samba. Click Continue button. It takes a minute depending on your internet connection speed.



Now you should see the configuration main dialog:



Click on Global You will see the defaults entered. Edit as needed Take note of the NetBIOS name. That is the server name we will use to connect. The Workgroup name can be set here. Workgroup is not too important to connect. It is sometimes helpful when browsing for servers.




 * A sharp eyed reader will note we did not fill in the Log file location.
 * You can enter a log file location or leave it blank.
 * The default will send logs to: \mptn\etc\samba\log

Then click Save button and Yes button



I will not go into the Shared printers, as it is easier to use CUPS to share printers Right click on Shared directories

You will get a dialog to allow which directory for Samba to share. In this example I decided to share D:\tmp



The configuration program will default and use the directory name as the share name, edit as needed. Then click OK



You will see a dialog to remind you to restart Samba. Don’t restart at this point. Simply click OK and the box will go away:



Now you should see the share appear in the window:



Click on the Save button.
 * But we are not ready to start.



Start Samba Server
Click on the Close button. Since this is our first time starting Samba we need to see any errors that may appear. For this the command prompt is better than that Start button on the Configuration Center. Open a command prompt. Enter:   cd \programs\samba then enter:  smb start This is a screen of a normal startup of Samba:



A close look at that start up does show some benign errors. I am using DHCP on the the first network card. A fixed ip address is best for a server. Also, LAN1 error. LAN1 is not even configured or hooked up to the network.

At this point Samba Server should be online and sharing our d:\tmp You should be able to go to another machine and do a network connection. For example a Window 10 client. A quick check from a command line will verify the Samba server: Note this assumes you are logged on to the Win10 machine with the same username and password that we created for ourselves with kLIBc tool and the smbpasswd command line.

Open a command prompt from Win10 Enter:  net view  \\netbiosname



To actually make the Win10 map a disk drive letter to the Samba, one method is to use open File Explorer: Right click on This PC Click on Map network drive



You can also use the ip address of the Samba Server if the server name is not working.



This is just the bare bones
Samba has many options and features. This was just to get online.