The Samba service actually consists of two different network services (netbios-ssn and netbios-ns) which allow your Freedom server to interact with Microsoft® Networking components. Using Samba, you can:
Map your server’s entire filesystem as a Network Drive on your Microsoft® Windows™ workstation. This allows you to access or save files on your Freedom server as easily as saving them to your local disk drive, because your server’s filesystem is assigned a drive letter just like a local disk.
Create a secure, shared Internet drive on your server that your employees or friends can save their data files to for collaboration and storage.
Using the smbclient command, you can access a Microsoft Windows network or another Samba server from your server’s command line
The server applications that power the Samba services are called smbd and nmbd. Both services are spawned through the xinetd application when needed, and are enabled by default. Samba can be disabled if desired through the inetctl command, which is described in the section of this manual which discusses the xinetd application.
The provided Samba configuration provides two different “shares” – set’s of files that users can access through Samba. The first share is named “root”, and it contains the entire filesystem of your Freedom server. Samba-enabled users can connect to the “root” share and access any of the files that they have permissions to access. The second share is named “homes”, and provides access to a user’s own home directory. Additional shares and a host of other options can be configured through Samba’s configuration file, which is only accessible to the superuser, and therefore available only on the Freedom 400x and above.