Translations by sputnik

File Sharing in <phrase>Kubuntu</phrase>

Credits and License

This document is maintained by the Ubuntu documentation team (https://wiki.ubuntu.com/DocumentationTeam). For a list of contributors, see the <ulink url="help:/kubuntu/contributors.html">contributors page</ulink>

This document is made available under the Creative Commons ShareAlike 2.5 License (CC-BY-SA).

You are free to modify, extend, and improve the Ubuntu documentation source code under the terms of this license. All derivative works must be released under this license.

This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE AS DESCRIBED IN THE DISCLAIMER.

A copy of the license is available here: <ulink url="help:/kubuntu/copyright.html">Creative Commons ShareAlike License</ulink>.

2009

Ubuntu Documentation Project

The Ubuntu Documentation Project

This document explains how to share files between <phrase>Kubuntu</phrase> and Windows.

Introduction

Computer networks are often comprised of diverse systems. While operating a network made up entirely of <phrase>Kubuntu</phrase> desktop and server computers would certainly be fun, some network environments will consist of <phrase>Kubuntu</phrase> and <trademark class="registered">Microsoft</trademark><trademark class="registered">Windows</trademark> systems working together. This section of the <phrase>Kubuntu</phrase> Server Guide introduces principles and tools used for configuring <phrase>Kubuntu</phrase> servers to share network resources with Windows computers.

It is now possible to read, write, and execute files in the shared directory as normal, and the <application>smbd</application> binary will have access to only the configured files and directories. Be sure to add entries for each directory that Samba is configured to share. Any errors will be logged to <filename>/var/log/syslog</filename>.

For in depth Samba configurations, see the <ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/">Samba HOWTO Collection</ulink>

For more information on Samba and ACLs, see the <ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/AccessControls.html#id397568">Samba ACLs page </ulink>.

When configuring Samba as a BDC, there must be a way to sync account information with the PDC. There are multiple ways of accomplishing this, such as <application>scp</application>, <application>rsync</application>, or by using <application>LDAP</application> as the <emphasis>passdb backend</emphasis>.

Using LDAP is the most robust way to sync account information, because both domain controllers can use the same information in real time. However, setting up a LDAP server may be overly complicated for a small number of user and computer accounts. See Samba<ulink url="http://wiki.samba.org/index.php/Samba_&amp;_LDAP"> LDAP</ulink> page for details.

First, install <application>samba</application> and <application>libpam-smbpass</application>. From a terminal enter:

Replace <emphasis>username</emphasis> with a valid username and <emphasis>pdc</emphasis> with the hostname or IP Address of the actual PDC.

Test that the Backup Domain controller is working by stopping the Samba daemon on the PDC, then trying to login to a Windows client joined to the domain.

If the <emphasis>logon home</emphasis> option has been configured as a directory on the PDC, and the PDC becomes unavailable, access to the user's <emphasis>Home</emphasis> drive will also be unavailable. For this reason, it is best to configure the <emphasis>logon home</emphasis> to reside on a separate file server from the PDC and BDC.

<ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/samba-pdc.html"> Chapter 4</ulink> of the Samba HOWTO Collection explains setting up a Primary Domain Controller.

<ulink url="http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/samba-bdc.html"> Chapter 5</ulink> of the Samba HOWTO Collection explains setting up a Backup Domain Controller.

Another use for Samba is to integrate into an existing Windows network. Once part of an Active Directory (AD) domain, Samba can provide file and print services to AD users.

The simplest way to join an AD domain is to use <application>Likewise-open</application>. For detailed instructions, see <xref linkend="likewise-open"/>.

Since the <application>likewise-open</application> and <application>samba</application> packages use separate <filename>secrets.tdb</filename> files, a symlink must be created in <filename role="directory">/var/lib/samba</filename>:

It should now be possible to access any <application>Samba</application> shares from a Windows client. However, be sure to give the appropriate AD users or groups access to the share directory. See <xref linkend="samba-fileprint-security"/> for more details.

Accessing a Windows Share

Now that the Samba server is part of the Active Directory domain, any Windows server shares can be accessed:

To mount a Windows file share, enter the following in a terminal prompt:

It is also possible to access shares on computers not part of an AD domain, but a username and password must be provided.

To mount the share during boot, place an entry in <filename>/etc/fstab</filename>, for example:

Likewise Open

<application>Likewise Open</application> simplifies the necessary configuration needed to authenticate a Linux machine to an Active Directory domain. Based on <application>winbind</application>, the <application>likewise-open</application> package takes the pain out of integrating <phrase>Kubuntu</phrase> authentication into an existing Windows network.

sudo apt-get install likewise-open

Installing likewise-open5 over an existing likewise-open (4.1) installation will replace it. The domain will have to be rejoined after install.