Application Delivery Management
Application Modernization & Connectivity
CyberRes by OpenText
IT Operations Management
You can install Samba during the installation or after the installation of OES 2. Either way the process is pretty much the same. I will walk you through installing Samba after the installation of OES 2 since there are a few more steps.
Important: The LUM configuration is not required. If your users are not
already LUM enabled when you Samba enable the user, they will be
automatically LUM enabled with the default Samba group. If you want the
users to have a different group for rights management then make sure you
LUM enable them to the desired group before they are Samba enabled.
One thing to keep in mind with Samba on OES 2 is that it is not the same exact Samba that comes with SLES 10 SP1. The Samba on OES 2 includes components for eDirectory integration and therefore is configured using iManager rather than Yast. Samba on OES 2 also requires LUM (Linux User Management) and UP (Universal Password) to be configured for each user.
You can either create your own password policy or use the default password policy that has been created for Samba. Since there is already a default Samba password policy, I will use that one.
Now that all of the prerequisites are out of the way, we are ready to configure Samba. This again is configured through iManager for OES 2. Do not configure this using Yast. Remember that OES 2 is an add on product to SLES 10 SP1 and has separate configurations for the components that shipped with the product. That doesn't mean that you can't use the Samba configuration with SLES 10 SP1, but rather that it will not have the OES components (like eDirectory authentication) if you use the SLES configuration.
You need to make sure that the user(s) you are assigning access to your share have eDirectory rights to that volume or folder. You can do this using the Novell Client, ConsoleOne, or iManager. Since I am already in iManager I will use it to assign the rights. If you are sure that the user(s) already has eDirectory rights then you can skip to the Testing Samba Access section.
Testing Samba from Linux
Testing Samba from Windows