+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="net2000users">
- <title>A Distributed 2000-User Network</title>
-
-<para>
-There is something indeed mystical about things that are
-big. Large networks exhibit a certain magnetism and exude a sense of
-importance that obscures reality. You and I know that it is no more
-difficult to secure a large network than it is a small one. We all
-know that over and above a particular number of network clients, the
-rules no longer change; the only real dynamic is the size of the domain
-(much like a kingdom) over which the network ruler (oops, administrator)
-has control. The real dynamic then transforms from the technical to the
-political. Then again, that point is often reached well before the
-kingdom (or queendom) grows large.
-</para>
-
-<para>
-If you have systematically worked your way to this chapter, hopefully you
-have found some gems and techniques that are applicable in your
-world. The network designs you have worked with in this book have their
-strong points as well as weak ones. That is to be expected given that
-they are based on real business environments, the specifics of which are
-molded to serve the purposes of this book.
-</para>
-
-<para>
-This chapter is intent on wrapping up issues that are central to
-implementation and design of progressively larger networks. Are you ready
-for this chapter? Good, it is time to move on.
-</para>
-
-<para>
-In previous chapters, you made the assumption that your network
-administration staff need detailed instruction right down to the
-nuts and bolts of implementing the solution. That is still the case,
-but they have graduated now. You decide to document only those issues,
-methods, and techniques that are new or complex. Routine tasks such as
-implementing a DNS or a DHCP server are under control. Even the basics of
-Samba are largely under control. So in this section you focus on the
-specifics of implementing LDAP changes, Samba changes, and approach and
-design of the solution and its deployment.
-</para>
-
-<sect1>
-<title>Introduction</title>
-
-<para>
-Abmas is a miracle company. Most businesses would have collapsed under
-the weight of rapid expansion that this company has experienced. Samba
-is flexible, so there is no need to reinstall the whole operating
-system just because you need to implement a new network design. In fact,
-you can keep an old server running right up to the moment of cutover
-and then do a near-live conversion. There is no need to reinstall a
-Samba server just to change the way your network should function.
-</para>
-
-<para>
-<indexterm><primary>LDAP</primary></indexterm>
-Network growth is common to all organizations. In this exercise,
-your preoccupation is with the mechanics of implementing Samba and
-LDAP so that network users on each network segment can work
-without impediment.
-</para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- Starting with the configuration files for the server called
- <constant>MASSIVE</constant> in <link linkend="happy"/>, you now deal with the
- issues that are particular to large distributed networks. Your task
- is simple &smbmdash; identify the challenges, consider the
- alternatives, and then design and implement a solution.
- </para>
-
- <para>
- <indexterm><primary>VPN</primary></indexterm>
- Remember, you have users based in London (UK), Los Angeles,
- Washington. DC, and, three buildings in New York. A significant portion
- of your workforce have notebook computers and roam all over the
- world. Some dial into the office, others use VPN connections over the
- Internet, and others just move between buildings.i
- </para>
-
- <para>
- What do you say to an employee who normally uses a desktop
- system but must spend six weeks on the road with a notebook computer?
- She is concerned about email access and how to keep coworkers current
- with changing documents.
- </para>
-
- <para>
- To top it all off, you have one network support person and one
- help desk person based in London, a single person dedicated to all
- network operations in Los Angeles, five staff for user administration
- and help desk in New York, plus one <emphasis>floater</emphasis> for
- Washington.
- </para>
-
- <para>
- You have outsourced all desktop deployment and management to
- DirectPointe. Your concern is server maintenance and third-level
- support. Build a plan and show what must be done.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
-<title>Dissection and Discussion</title>
-
-<para>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-In <link linkend="happy"/>, you implemented an LDAP server that provided the
-<parameter>passdb backend</parameter> for the Samba servers. You
-explored ways to accelerate Windows desktop profile handling and you
-took control of network performance.
-</para>
-
-<para>
-<indexterm><primary>ldapsam</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>replicated</primary></indexterm>
-The implementation of an LDAP-based passdb backend (known as
-<emphasis>ldapsam</emphasis> in Samba parlance), or some form of database
-that can be distributed, is essential to permit the deployment of Samba
-Primary and Backup Domain Controllers (PDC/BDCs). You see, the problem
-is that the <emphasis>tdbsam</emphasis>-style passdb backend does not
-lend itself to being replicated. The older plain-text-based
-<emphasis>smbpasswd</emphasis>-style passdb backend can be replicated
-using a tool such as <command>rsync</command>, but
-<emphasis>smbpasswd</emphasis> suffers the drawback that it does not
-support the range of account facilities demanded by modern network
-managers.
-</para>
-
-<para>
-<indexterm><primary>XML</primary></indexterm>
-<indexterm><primary>SQL</primary></indexterm>
-The new <emphasis>tdbsam</emphasis> facility supports functionality
-that is similar to an <emphasis>ldapsam</emphasis>, but the lack of
-distributed infrastructure sorely limits the scope for its
-deployment. This raises the following questions: Why can't I just use
-an XML-based backend, or for that matter, why not use an SQL-based
-backend? Is support for these tools broken? Answers to these
-questions require a bit of background.</para>
-
-<para>
-<indexterm><primary>directory</primary></indexterm>
-<indexterm><primary>database</primary></indexterm>
-<indexterm><primary>transaction processing</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<emphasis>What is a directory?</emphasis> A directory is a
-collection of information regarding objects that can be accessed to
-rapidly find information that is relevant in a particular and
-consistent manner. A directory differs from a database in that it is
-generally more often searched (read) than updated. As a consequence, the
-information is organized to facilitate read access rather than to
-support transaction processing.</para>
-
-<para>
-<indexterm><primary>Lightweight Directory Access Protocol</primary><see>LDAP</see></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>master</primary></indexterm>
-<indexterm><primary>slave</primary></indexterm>
-The Lightweight Directory Access Protocol (LDAP) differs
-considerably from a traditional database. It has a simple search
-facility that uniquely makes a highly preferred mechanism for managing
-user identities. LDAP provides a scalable mechanism for distributing
-the data repository and for keeping all copies (slaves) in sync with
-the master repository.</para>
-
-<para>
-<indexterm><primary>identity management</primary></indexterm>
-<indexterm><primary>Active Directory</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-Samba is a flexible and powerful file and print sharing
-technology. It can use many external authentication sources and can be
-part of a total authentication and identity management
-infrastructure. The two most important external sources for large sites
-are Microsoft Active Directory and LDAP. Sites that specifically wish to
-avoid the proprietary implications of Microsoft Active Directory
-naturally gravitate toward OpenLDAP.</para>
-
-<para>
-<indexterm><primary>network</primary><secondary>routed</secondary></indexterm>
-In <link linkend="happy"/>, you had to deal with a locally routed
-network. All deployment concerns focused around making users happy,
-and that simply means taking control over all network practices and
-usage so that no one user is disadvantaged by any other. The real
-lesson is one of understanding that no matter how much network
-bandwidth you provide, bandwidth remains a precious resource.</para>
-
-<para>In this chapter, you must now consider how the overall network must
-function. In particular, you must be concerned with users who move
-between offices. You must take into account the way users need to
-access information globally. And you must make the network robust
-enough so that it can sustain partial breakdown without causing loss of
-productivity.</para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- There are at least three areas that need to be addressed as you
- approach the challenge of designing a network solution for the newly
- expanded business:
- </para>
-
- <itemizedlist>
- <listitem><para><indexterm><primary>mobility</primary></indexterm>
- User needs such as mobility and data access</para></listitem>
-
- <listitem><para>The nature of Windows networking protocols</para></listitem>
-
- <listitem><para>Identity management infrastructure needs</para></listitem>
- </itemizedlist>
-
- <para>Let's look at each in turn.</para>
-
- <sect3>
- <title>User Needs</title>
-
- <para>
- The new company has three divisions. Staff for each division are spread across
- the company. Some staff are office-bound and some are mobile users. Mobile
- users travel globally. Some spend considerable periods working in other offices.
- Everyone wants to be able to work without constraint of productivity.
- </para>
-
- <para>
- The challenge is not insignificant. In some parts of the world, even dial-up
- connectivity is poor, while in other regions political encumbrances severely
- curtail user needs. Parts of the global Internet infrastructure remain shielded
- off for reasons outside the scope of this discussion.
- </para>
-
- <para>
- <indexterm><primary>synchronize</primary></indexterm>
- Decisions must be made regarding where data is to be stored, how it will be
- replicated (if at all), and what the network bandwidth implications are. For
- example, one decision that can be made is to give each office its own master
- file storage area that can be synchronized to a central repository in New
- York. This would permit global data to be backed up from a single location.
- The synchronization tool could be <command>rsync,</command> run via a cron
- job. Mobile users may use off-line file storage under Windows XP Professional.
- This way, they can synchronize all files that have changed since each logon
- to the network.
- </para>
-
- <para>
- <indexterm><primary>bandwidth</primary><secondary>requirements</secondary></indexterm>
- <indexterm><primary>roaming profile</primary></indexterm>
- No matter which way you look at this, the bandwidth requirements
- for acceptable performance are substantial even if only 10 percent of
- staff are global data users. A company with 3,500 employees,
- 280 of whom are mobile users who use a similarly distributed
- network, found they needed at least 2 Mb/sec connectivity
- between the UK and US offices. Even over 2 Mb/sec bandwidth, this
- company abandoned any attempt to run roaming profile usage for
- mobile users. At that time, the average roaming profile took 480
- KB, while today the minimum Windows XP Professional roaming
- profile involves a transfer of over 750 KB from the profile
- server to and from the client.
- </para>
-
- <para>
- <indexterm><primary>wide-area</primary></indexterm>
- Obviously then, user needs and wide-area practicalities dictate the economic and
- technical aspects of your network design as well as for standard operating procedures.
- </para>
-
- </sect3>
-
- <sect3>
- <title>The Nature of Windows Networking Protocols</title>
-
- <para>
- <indexterm><primary>profile</primary><secondary>mandatory</secondary></indexterm>
- Network logons that include roaming profile handling requires from 140 KB to 2 MB.
- The inclusion of support for a minimal set of common desktop applications can push
- the size of a complete profile to over 15 MB. This has substantial implications
- for location of user profiles. Additionally, it is a significant factor in
- determining the nature and style of mandatory profiles that may be enforced as
- part of a total service-level assurance program that might be implemented.
- </para>
-
- <para>
- <indexterm><primary>logon traffic</primary></indexterm>
- <indexterm><primary>redirected folders</primary></indexterm>
- One way to reduce the network bandwidth impact of user logon
- traffic is through folder redirection. In <link linkend="happy"/>, you
- implemented this in the new Windows XP Professional standard
- desktop configuration. When desktop folders such as <guimenu>My
- Documents</guimenu> are redirected to a network drive, they should
- also be excluded from synchronization to and from the server on
- logon or logout. Redirected folders are analogous to network drive
- connections.
- </para>
-
- <para><indexterm><primary>application servers</primary></indexterm>
- Of course, network applications should only be run off
- local application servers. As a general rule, even with 2 Mb/sec
- network bandwidth, it would not make sense at all for someone who
- is working out of the London office to run applications off a
- server that is located in New York.
- </para>
-
- <para>
- <indexterm><primary>affordability</primary></indexterm>
- When network bandwidth becomes a precious commodity (that is most
- of the time), there is a significant demand to understand network
- processes and to mold the limits of acceptability around the
- constraints of affordability.
- </para>
-
- <para>
- When a Windows NT4/200x/XP Professional client user logs onto
- the network, several important things must happen.
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>DHCP</primary></indexterm>
- The client obtains an IP address via DHCP. (DHCP is
- necessary so that users can roam between offices.)
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- The client must register itself with the WINS and/or DNS server.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Domain Controller</primary><secondary>closest</secondary></indexterm>
- The client must locate the closest domain controller.
- </para></listitem>
-
- <listitem><para>
- The client must log onto a domain controller and obtain as part of
- that process the location of the user's profile, load it, connect to
- redirected folders, and establish all network drive and printer connections.
- </para></listitem>
-
- <listitem><para>
- The domain controller must be able to resolve the user's
- credentials before the logon process is fully implemented.
- </para></listitem>
- </itemizedlist>
-
- <para>
- Given that this book is about Samba and that it implements the Windows
- NT4-style domain semantics, it makes little sense to compare Samba with
- Microsoft Active Directory insofar as the logon protocols and principles
- of operation are concerned. The following information pertains exclusively
- to the interaction between a Windows XP Professional workstation and a
- Samba-3.0.20 server. In the discussion that follows, use is made of DHCP and WINS.
- </para>
-
- <para>
- As soon as the Windows workstation starts up, it obtains an
- IP address. This is immediately followed by registration of its
- name both by broadcast and Unicast registration that is directed
- at the WINS server.
- </para>
-
- <para>
- <indexterm><primary>Unicast</primary></indexterm>
- <indexterm><primary>broadcast</primary><secondary>directed</secondary>
- </indexterm><indexterm><primary>NetBIOS</primary></indexterm>
- Given that the client is already a domain member, it then sends
- a directed (Unicast) request to the WINS server seeking the list of
- IP addresses for domain controllers (NetBIOS name type 0x1C). The
- WINS server replies with the information requested.</para>
-
- <para>
- <indexterm><primary>broadcast</primary><secondary>mailslot</secondary></indexterm>
- <indexterm><primary>Unicast</primary></indexterm>
- <indexterm><primary>WINS</primary></indexterm>
- The client sends two netlogon mailslot broadcast requests
- to the local network and to each of the IP addresses returned by
- the WINS server. Whichever answers this request first appears to
- be the machine that the Windows XP client attempts to use to
- process the network logon. The mailslot messages use UDP broadcast
- to the local network and UDP Unicast directed at each machine that
- was listed in the WINS server response to a request for the list of
- domain controllers.
- </para>
-
- <para>
- <indexterm><primary>protocol</primary><secondary>negotiation</secondary></indexterm>
- <indexterm><primary>logon server</primary></indexterm>
- <indexterm><primary>fail</primary></indexterm>
- The logon process begins with negotiation of the SMB/CIFS
- protocols that are to be used; this is followed by an exchange of
- information that ultimately includes the client sending the
- credentials with which the user is attempting to logon. The logon
- server must now approve the further establishment of the
- connection, but that is a good point to halt for now. The priority
- here must center around identification of network infrastructure
- needs. A secondary fact we need to know is, what happens when
- local domain controllers fail or break?
- </para>
-
- <para>
- <indexterm><primary>Domain Controller</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>netlogon</primary></indexterm>
- Under most circumstances, the nearest domain controller
- responds to the netlogon mailslot broadcast. The exception to this
- norm occurs when the nearest domain controller is too busy or is out
- of service. Herein lies an important fact. This means it is
- important that every network segment should have at least two
- domain controllers. Since there can be only one PDC, all additional
- domain controllers are by definition BDCs.
- </para>
-
- <para>
- <indexterm><primary>authentication</primary></indexterm>
- <indexterm><primary>Identity Management</primary></indexterm>
- The provision of sufficient servers that are BDCs is an
- important design factor. The second important design factor
- involves how each of the BDCs obtains user authentication
- data. That is the subject of the next section, which involves key
- decisions regarding Identity Management facilities.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Identity Management Needs</title>
-
- <para>
- <indexterm><primary>privacy</primary></indexterm>
- <indexterm><primary>user credentials</primary></indexterm>
- <indexterm><primary>validated</primary></indexterm>
- <indexterm><primary>privileges</primary></indexterm>
- Network managers recognize that in large organizations users
- generally need to be given resource access based on needs, while
- being excluded from other resources for reasons of privacy. It is
- therefore essential that all users identify themselves at the
- point of network access. The network logon is the principal means
- by which user credentials are validated and filtered and appropriate
- rights and privileges are allocated.
- </para>
-
- <para>
- <indexterm><primary>Identity Management</primary></indexterm>
- <indexterm><primary>Yellow Pages</primary></indexterm>
- <indexterm><primary>NIS</primary></indexterm>
- Unfortunately, network resources tend to have their own Identity
- Management facilities, the quality and manageability of which varies
- from quite poor to exceptionally good. Corporations that use a mixture
- of systems soon discover that until recently, few systems were
- designed to interoperate. For example, UNIX systems each have an
- independent user database. Sun Microsystems developed a facility that
- was originally called <constant>Yellow Pages</constant>, and was renamed
- when a telephone company objected to the use of its trademark.
- What was once called <constant>Yellow Pages</constant> is today known
- as <constant>Network Information System</constant> (NIS).
- </para>
-
- <para>
- <indexterm><primary>NIS+</primary></indexterm>
- NIS gained a strong following throughout the UNIX/VMS space in a short
- period of time and retained that appeal and use for over a decade.
- Security concerns and inherent limitations have caused it to enter its
- twilight. NIS did not gain widespread appeal outside of the UNIX world
- and was not universally adopted. Sun updated this to a more secure
- implementation called NIS+, but even it has fallen victim to changing
- demands as the demand for directory services that can be coupled with
- other information systems is catching on.
- </para>
-
-
- <para>
- <indexterm><primary>NIS</primary></indexterm>
- <indexterm><primary>government</primary></indexterm>
- <indexterm><primary>education</primary></indexterm>
- Nevertheless, both NIS and NIS+ continue to hold ground in
- business areas where UNIX still has major sway. Examples of
- organizations that remain firmly attached to the use of NIS and
- NIS+ include large government departments, education institutions,
- and large corporations that have a scientific or engineering
- focus.
- </para>
-
- <para>
- <indexterm><primary>scalable</primary></indexterm>
- <indexterm><primary>distributed</primary></indexterm>
- Today's networking world needs a scalable, distributed Identity
- Management infrastructure, commonly called a directory. The most
- popular technologies today are Microsoft Active Directory service
- and a number of LDAP implementations.
- </para>
-
- <para>
- <indexterm><primary>multiple directories</primary></indexterm>
- The problem of managing multiple directories has become a focal
- point over the past decade, creating a large market for
- metadirectory products and services that allow organizations that
- have multiple directories and multiple management and control
- centers to provision information from one directory into
- another. The attendant benefit to end users is the promise of
- having to remember and deal with fewer login identities and
- passwords.</para>
-
- <para>
- <indexterm><primary>network</primary><secondary>bandwidth</secondary></indexterm>
- The challenge of every large network is to find the optimum
- balance of internal systems and facilities for Identity
- Management resources. How well the solution is chosen and
- implemented has potentially significant impact on network bandwidth
- and systems response needs.</para>
-
- <para>
- <indexterm><primary>LDAP server</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>master</secondary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>slave</secondary></indexterm>
- In <link linkend="happy"/>, you implemented a single LDAP server for the
- entire network. This may work for smaller networks, but almost
- certainly fails to meet the needs of large and complex networks. The
- following section documents how you may implement a single
- master LDAP server with multiple slave servers.</para>
-
- <para>
- What is the best method for implementing master/slave LDAP
- servers within the context of a distributed 2,000-user network is a
- question that remains to be answered.</para>
-
- <para>
- <indexterm><primary>distributed domain</primary></indexterm>
- <indexterm><primary>wide-area</primary></indexterm>
- One possibility that has great appeal is to create a single,
- large distributed domain. The practical implications of this
- design (see <link linkend="chap7net"/>) demands the placement of
- sufficient BDCs in each location. Additionally, network
- administrators must make sure that profiles are not transferred
- over the wide-area links, except as a totally unavoidable
- measure. Network design must balance the risk of loss of user
- productivity against the cost of network management and
- maintenance.
- </para>
-
- <para>
- <indexterm><primary>domain name space</primary></indexterm>
- The network design in <link linkend="chap7net2"/> takes the approach
- that management of networks that are too remote to be managed
- effectively from New York ought to be given a certain degree of
- autonomy. With this rationale, the Los Angeles and London networks,
- though fully integrated with those on the East Coast, each have their
- own domain name space and can be independently managed and controlled.
- One of the key drawbacks of this design is that it flies in the face of
- the ability for network users to roam globally without some compromise
- in how they may access global resources.
- </para>
-
- <para>
- <indexterm><primary>interdomain trusts</primary></indexterm>
- Desk-bound users need not be negatively affected by this design, since
- the use of interdomain trusts can be used to satisfy the need for global
- data sharing.
- </para>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>backend</secondary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- When Samba is configured to use an LDAP backend, it stores the domain
- account information in a directory entry. This account entry contains the
- domain SID. An unintended but exploitable side effect is that this makes it
- possible to operate with more than one PDC on a distributed network.
- </para>
-
- <para>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>wins.dat</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- How might this peculiar feature be exploited? The answer is simple. It is
- imperative that each network segment have its own WINS server. Major
- servers on remote network segments can be given a static WINS entry in
- the <filename>wins.dat</filename> file on each WINS server. This allows
- all essential data to be visible from all locations. Each location would,
- however, function as if it is an independent domain, while all sharing the
- same domain SID. Since all domain account information can be stored in a
- single LDAP backend, users have unfettered ability to roam.
- </para>
-
- <para>
- <indexterm><primary>NetBIOS name</primary><secondary>aliases</secondary></indexterm>
- <indexterm><primary>fail-over</primary></indexterm>
- This concept has not been exhaustively validated, though we can see no reason
- why this should not work. The important facets are the following: The name of
- the domain must be identical in all locations. Each network segment must have
- its own WINS server. The name of the PDC must be the same in all locations; this
- necessitates the use of NetBIOS name aliases for each PDC so that they can be
- accessed globally using the alias and not the PDC's primary name. A single master
- LDAP server can be based in New York, with multiple LDAP slave servers located
- on every network segment. Finally, the BDCs should each use failover LDAP servers
- that are in fact slave LDAP servers on the local segments.
- </para>
-
- <para>
- <indexterm><primary>LDAP</primary><secondary>updates</secondary></indexterm>
- <indexterm><primary>domain tree</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>database</secondary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>directory</secondary></indexterm>
- With a single master LDAP server, all network updates are effected on a single
- server. In the event that this should become excessively fragile or network
- bandwidth limiting, one could implement a delegated LDAP domain. This is also
- known as a partitioned (or multiple partition) LDAP database and as a distributed
- LDAP directory.
- </para>
-
- <para>
- As the LDAP directory grows, it becomes increasingly important
- that its structure is implemented in a manner that mirrors
- organizational needs, so as to limit network update and
- referential traffic. It should be noted that all directory
- administrators must of necessity follow the same standard
- procedures for managing the directory, because retroactive correction of
- inconsistent directory information can be exceedingly difficult.
- </para>
-
- </sect3>
-
- </sect2>
-
-
- <sect2>
- <title>Political Issues</title>
-
- <para>
- As organizations grow, the number of points of control increases
- also. In a large distributed organization, it is important that the
- Identity Management system be capable of being updated from
- many locations, and it is equally important that changes made should
- become usable in a reasonable period, typically
- minutes rather than days (the old limitation of highly manual
- systems).
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>GID</primary></indexterm>
- Samba has the ability to use multiple password (authentication and
- identity resolution) backends. The diagram in <link linkend="chap7idres"/>
- demonstrates how Samba uses winbind, LDAP, and NIS, the traditional system
- password database. The diagram only documents the mechanisms for
- authentication and identity resolution (obtaining a UNIX UID/GID)
- using the specific systems shown.
- </para>
-
- <figure id="chap7idres">
- <title>Samba and Authentication Backend Search Pathways</title>
- <imagefile scale="55">chap7-idresol</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>xmlsam</primary></indexterm>
- <indexterm><primary>SMB passwords</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>mysqlsam</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>distributed</primary></indexterm>
- Samba is capable of using the <constant>smbpasswd</constant> and
- <constant>tdbsam</constant>. The SMB
- passwords can, of course, also be stored in an LDAP ldapsam
- backend. LDAP is the preferred passdb backend for distributed network
- operations.
- </para>
-
- <para>
- <indexterm><primary>passdb backend</primary></indexterm>
- You can specify a failover LDAP backend. The syntax for specifying a
- single LDAP backend in &smb.conf; is:
-<screen>
-...
-passdb backend = ldapsam:ldap://master.abmas.biz
-...
-</screen>
- This configuration tells Samba to use a single LDAP server, as shown in <link linkend="ch7singleLDAP"/>.
- <figure id="ch7singleLDAP">
- <title>Samba Configuration to Use a Single LDAP Server</title>
- <imagefile scale="65">ch7-singleLDAP</imagefile>
- </figure>
- <indexterm><primary>LDAP</primary><secondary>fail-over</secondary></indexterm>
- <indexterm><primary>fail-over</primary></indexterm>
- The addition of a failover LDAP server can simply be done by adding a
- second entry for the failover server to the single <parameter>ldapsam</parameter>
- entry, as shown here (note the particular use of the double quotes):
-<screen>
-...
-passdb backend = ldapsam:"ldap://master.abmas.biz \
- ldap://slave.abmas.biz"
-...
-</screen>
- This configuration tells Samba to use a master LDAP server, with failover to a slave server if necessary,
- as shown in <link linkend="ch7dualLDAP"/>.
- <figure id="ch7dualLDAP">
- <title>Samba Configuration to Use a Dual (Fail-over) LDAP Server</title>
- <imagefile scale="65">ch7-fail-overLDAP</imagefile>
- </figure>
- </para>
-
- <para>
- It is assumed that the network you are working with follows in a
- pattern similar to what was covered in <link linkend="happy"/>. The following steps
- permit the operation of a master/slave OpenLDAP arrangement.
- </para>
-
- <procedure>
- <title>Implementation Steps for an LDAP Slave Server</title>
-
- <step><para>
- <indexterm><primary>SUSE Linux</primary></indexterm>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- Log onto the master LDAP server as <constant>root</constant>.
- You are about to change the configuration of the LDAP server, so it
- makes sense to temporarily halt it. Stop OpenLDAP from running on
- SUSE Linux by executing:
-<screen>
-&rootprompt; rcldap stop
-</screen>
- On Red Hat Linux, you can do this by executing:
-<screen>
-&rootprompt; service ldap stop
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
- Edit the <filename>/etc/openldap/slapd.conf</filename> file so it
- matches the content of <link linkend="ch7-LDAP-master"/>.
- </para></step>
-
- <step><para>
- Create a file called <filename>admin-accts.ldif</filename> with the following contents:
-<screen>
-dn: cn=updateuser,dc=abmas,dc=biz
-objectClass: person
-cn: updateuser
-sn: updateuser
-userPassword: not24get
-
-dn: cn=sambaadmin,dc=abmas,dc=biz
-objectClass: person
-cn: sambaadmin
-sn: sambaadmin
-userPassword: buttercup
-</screen>
- </para></step>
-
- <step><para>
- Add an account called <quote>updateuser</quote> to the master LDAP server as shown here:
-<screen>
-&rootprompt; slapadd -v -l admin-accts.ldif
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>LDIF</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>preload</secondary></indexterm>
- Change directory to a suitable place to dump the contents of the
- LDAP server. The dump file (and LDIF file) is used to preload
- the slave LDAP server database. You can dump the database by executing:
-<screen>
-&rootprompt; slapcat -v -l LDAP-transfer-LDIF.txt
-</screen>
- Each record is written to the file.
- </para></step>
-
- <step><para>
- <indexterm><primary>LDAP-transfer-LDIF.txt</primary></indexterm>
- Copy the file <filename>LDAP-transfer-LDIF.txt</filename> to the intended
- slave LDAP server. A good location could be in the directory
- <filename>/etc/openldap/preload</filename>.
- </para></step>
-
- <step><para>
- Log onto the slave LDAP server as <constant>root</constant>. You can
- now configure this server so the <filename>/etc/openldap/slapd.conf</filename>
- file matches the content of <link linkend="ch7-LDAP-slave"/>.
- </para></step>
-
- <step><para>
- Change directory to the location in which you stored the
- <filename>LDAP-transfer-LDIF.txt</filename> file (<filename>/etc/openldap/preload</filename>).
- While in this directory, execute:
-<screen>
-&rootprompt; slapadd -v -l LDAP-transfer-LDIF.txt
-</screen>
- If all goes well, the following output confirms that the data is being loaded
- as intended:
-<screen>
-added: "dc=abmas,dc=biz" (00000001)
-added: "cn=sambaadmin,dc=abmas,dc=biz" (00000002)
-added: "cn=updateuser,dc=abmas,dc=biz" (00000003)
-added: "ou=People,dc=abmas,dc=biz" (00000004)
-added: "ou=Groups,dc=abmas,dc=biz" (00000005)
-added: "ou=Computers,dc=abmas,dc=biz" (00000006)
-added: "uid=Administrator,ou=People,dc=abmas,dc=biz" (00000007)
-added: "uid=nobody,ou=People,dc=abmas,dc=biz" (00000008)
-added: "cn=Domain Admins,ou=Groups,dc=abmas,dc=biz" (00000009)
-added: "cn=Domain Users,ou=Groups,dc=abmas,dc=biz" (0000000a)
-added: "cn=Domain Guests,ou=Groups,dc=abmas,dc=biz" (0000000b)
-added: "uid=bobj,ou=People,dc=abmas,dc=biz" (0000000c)
-added: "sambaDomainName=MEGANET2,dc=abmas,dc=biz" (0000000d)
-added: "uid=stans,ou=People,dc=abmas,dc=biz" (0000000e)
-added: "uid=chrisr,ou=People,dc=abmas,dc=biz" (0000000f)
-added: "uid=maryv,ou=People,dc=abmas,dc=biz" (00000010)
-added: "cn=Accounts,ou=Groups,dc=abmas,dc=biz" (00000011)
-added: "cn=Finances,ou=Groups,dc=abmas,dc=biz" (00000012)
-added: "cn=PIOps,ou=Groups,dc=abmas,dc=biz" (00000013)
-</screen>
- </para></step>
-
- <step><para>
- Now start the LDAP server and set it to run automatically on system reboot by executing:
-<screen>
-&rootprompt; rcldap start
-&rootprompt; chkconfig ldap on
-</screen>
- On Red Hat Linux, execute the following:
-<screen>
-&rootprompt; service ldap start
-&rootprompt; chkconfig ldap on
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>chkconfig</primary></indexterm>
- <indexterm><primary>service</primary></indexterm>
- <indexterm><primary>rcldap</primary></indexterm>
- Go back to the master LDAP server. Execute the following to start LDAP as well
- as <command>slurpd</command>, the synchronization daemon, as shown here:
-<screen>
-&rootprompt; rcldap start
-&rootprompt; chkconfig ldap on
-&rootprompt; rcslurpd start
-&rootprompt; chkconfig slurpd on
-</screen>
- <indexterm><primary>slurpd</primary></indexterm>
- On Red Hat Linux, check the equivalent command to start <command>slurpd</command>.
- </para></step>
-
- <step><para>
- <indexterm><primary>smbldap-useradd</primary></indexterm>
- On the master LDAP server you may now add an account to validate that replication
- is working. Assuming the configuration shown in <link linkend="happy"/>, execute:
-<screen>
-&rootprompt; /var/lib/samba/sbin/smbldap-useradd -a fruitloop
-</screen>
- </para></step>
-
- <step><para>
- On the slave LDAP server, change to the directory <filename>/var/lib/ldap</filename>.
- There should now be a file called <filename>replogfile</filename>. If replication worked
- as expected, the content of this file should be:
-<screen>
-time: 1072486403
-dn: uid=fruitloop,ou=People,dc=abmas,dc=biz
-changetype: modify
-replace: sambaProfilePath
-sambaProfilePath: \\MASSIVE\profiles\fruitloop
--
-replace: sambaHomePath
-sambaHomePath: \\MASSIVE\homes
--
-replace: entryCSN
-entryCSN: 2003122700:43:38Z#0x0005#0#0000
--
-replace: modifiersName
-modifiersName: cn=Manager,dc=abmas,dc=biz
--
-replace: modifyTimestamp
-modifyTimestamp: 20031227004338Z
--
-</screen>
- </para></step>
-
- <step><para>
- Given that this first slave LDAP server is now working correctly, you may now
- implement additional slave LDAP servers as required.
- </para></step>
-
- <step><para>
- On each machine (PDC and BDCs) after the respective &smb.conf; files have been created as shown in
- <link linkend="ch7-massmbconfA">Primary Domain Controller &smb.conf; File &smbmdash; Part A + B + C</link> and
- on BDCs the <link linkend="ch7-slvsmbocnfA">Backup Domain Controller &smb.conf; File &smbmdash; Part A
- + B + C</link> execute the following:
-<screen>
-&rootprompt; smbpasswd -w buttercup
-</screen>
- This will install in the <filename>secrets.tdb</filename> file the password that Samba will need to
- manage (write to) the LDAP Master server to perform account updates.
- </para></step>
-
- </procedure>
-
-<example id="ch7-LDAP-master">
-<title>LDAP Master Server Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename></title>
-<screen>
-include /etc/openldap/schema/core.schema
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/nis.schema
-include /etc/openldap/schema/samba.schema
-
-pidfile /var/run/slapd/slapd.pid
-argsfile /var/run/slapd/slapd.args
-
-database bdb
-suffix "dc=abmas,dc=biz"
-rootdn "cn=Manager,dc=abmas,dc=biz"
-
-# rootpw = not24get
-rootpw {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
-
-replica host=lapdc.abmas.biz:389
- suffix="dc=abmas,dc=biz"
- binddn="cn=updateuser,dc=abmas,dc=biz"
- bindmethod=simple credentials=not24get
-
-access to attrs=sambaLMPassword,sambaNTPassword
- by dn="cn=sambaadmin,dc=abmas,dc=biz" write
- by * none
-
-replogfile /var/lib/ldap/replogfile
-
-directory /var/lib/ldap
-
-# Indices to maintain
-index objectClass eq
-index cn pres,sub,eq
-index sn pres,sub,eq
-index uid pres,sub,eq
-index displayName pres,sub,eq
-index uidNumber eq
-index gidNumber eq
-index memberUID eq
-index sambaSID eq
-index sambaPrimaryGroupSID eq
-index sambaDomainName eq
-index default sub
-</screen>
-</example>
-
-<example id="ch7-LDAP-slave">
-<title>LDAP Slave Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename></title>
-<screen>
-include /etc/openldap/schema/core.schema
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/nis.schema
-include /etc/openldap/schema/samba.schema
-
-pidfile /var/run/slapd/slapd.pid
-argsfile /var/run/slapd/slapd.args
-
-database bdb
-suffix "dc=abmas,dc=biz"
-rootdn "cn=Manager,dc=abmas,dc=biz"
-
-# rootpw = not24get
-rootpw {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
-
-access to *
- by dn=cn=updateuser,dc=abmas,dc=biz write
- by * read
-
-updatedn cn=updateuser,dc=abmas,dc=biz
-updateref ldap://massive.abmas.biz
-
-directory /var/lib/ldap
-
-# Indices to maintain
-index objectClass eq
-index cn pres,sub,eq
-index sn pres,sub,eq
-index uid pres,sub,eq
-index displayName pres,sub,eq
-index uidNumber eq
-index gidNumber eq
-index memberUID eq
-index sambaSID eq
-index sambaPrimaryGroupSID eq
-index sambaDomainName eq
-index default sub
-</screen>
-</example>
-
-<example id="ch7-massmbconfA">
-<title>Primary Domain Controller &smb.conf; File &smbmdash; Part A</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="unix charset">LOCALE</smbconfoption>
-<smbconfoption name="workgroup">MEGANET2</smbconfoption>
-<smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">0</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="time server">Yes</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m '%u'</smbconfoption>
-<smbconfoption name="delete user script">/opt/IDEALX/sbin/smbldap-userdel '%u'</smbconfoption>
-<smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p '%g'</smbconfoption>
-<smbconfoption name="delete group script">/opt/IDEALX/sbin/smbldap-groupdel '%g'</smbconfoption>
-<smbconfoption name="add user to group script">/opt/IDEALX/sbin/smbldap-groupmod -m '%g' '%u'</smbconfoption>
-<smbconfoption name="delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x '%g' '%u'</smbconfoption>
-<smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</smbconfoption>
-<smbconfoption name="add machine script">/opt/IDEALX/sbin/smbldap-useradd -w '%u'</smbconfoption>
-<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
-<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
-<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
-<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">X:</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="domain master">Yes</smbconfoption>
-<smbconfoption name="wins support">Yes</smbconfoption>
-<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=sambaadmin,dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="idmap backend">ldap://massive.abmas.biz</smbconfoption>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch7-massmbconfB">
-<title>Primary Domain Controller &smb.conf; File &smbmdash; Part B</title>
-<smbconfblock>
-<smbconfsection name="[IPC$]"/>
-<smbconfoption name="path">/tmp</smbconfoption>
-
-<smbconfsection name="[accounts]"/>
-<smbconfoption name="comment">Accounting Files</smbconfoption>
-<smbconfoption name="path">/data/accounts</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[service]"/>
-<smbconfoption name="comment">Financial Services Files</smbconfoption>
-<smbconfoption name="path">/data/service</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[pidata]"/>
-<smbconfoption name="comment">Property Insurance Files</smbconfoption>
-<smbconfoption name="path">/data/pidata</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch7-massmbconfC">
-<title>Primary Domain Controller &smb.conf; File &smbmdash; Part C</title>
-<smbconfblock>
-<smbconfsection name="[apps]"/>
-<smbconfoption name="comment">Application Files</smbconfoption>
-<smbconfoption name="path">/apps</smbconfoption>
-<smbconfoption name="admin users">bjones</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network Logon Service</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="admin users">root, Administrator</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="locking">No</smbconfoption>
-
-<smbconfsection name="[profiles]"/>
-<smbconfoption name="comment">Profile Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[profdata]"/>
-<smbconfoption name="comment">Profile Data Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
-<smbconfoption name="write list">root</smbconfoption>
-<smbconfoption name="admin users">root, Administrator</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch7-slvsmbocnfA">
-<title>Backup Domain Controller &smb.conf; File &smbmdash; Part A</title>
-<smbconfblock>
-<smbconfcomment># Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="unix charset">LOCALE</smbconfoption>
-<smbconfoption name="workgroup">MEGANET2</smbconfoption>
-<smbconfoption name="netbios name">BLDG1</smbconfoption>
-<smbconfoption name="passdb backend">ldapsam:ldap://lapdc.abmas.biz</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">50</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
-<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">X:</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="os level">63</smbconfoption>
-<smbconfoption name="domain master">No</smbconfoption>
-<smbconfoption name="wins server">192.168.2.1</smbconfoption>
-<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=sambaadmin,dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="utmp">Yes</smbconfoption>
-<smbconfoption name="idmap backend">ldap://massive.abmas.biz</smbconfoption>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[accounts]"/>
-<smbconfoption name="comment">Accounting Files</smbconfoption>
-<smbconfoption name="path">/data/accounts</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[service]"/>
-<smbconfoption name="comment">Financial Services Files</smbconfoption>
-<smbconfoption name="path">/data/service</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch7-slvsmbocnfB">
-<title>Backup Domain Controller &smb.conf; File &smbmdash; Part B</title>
-<smbconfblock>
-<smbconfsection name="[pidata]"/>
-<smbconfoption name="comment">Property Insurance Files</smbconfoption>
-<smbconfoption name="path">/data/pidata</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[apps]"/>
-<smbconfoption name="comment">Application Files</smbconfoption>
-<smbconfoption name="path">/apps</smbconfoption>
-<smbconfoption name="admin users">bjones</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network Logon Service</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="locking">No</smbconfoption>
-
-<smbconfsection name="[profiles]"/>
-<smbconfoption name="comment">Profile Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[profdata]"/>
-<smbconfoption name="comment">Profile Data Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <sect2>
- <title>Key Points Learned</title>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>LDAP</primary></indexterm><indexterm><primary>BDC</primary></indexterm>
- Where Samba is used as a domain controller, the use of LDAP is an
- essential component to permit the use of BDCs.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>wide-area</primary></indexterm>
- Replication of the LDAP master server to create a network of BDCs
- is an important mechanism for limiting WAN traffic.
- </para></listitem>
-
- <listitem><para>
- Network administration presents many complex challenges, most of which
- can be satisfied by good design but that also require sound communication
- and unification of management practices. This can be highly challenging in
- a large, globally distributed network.
- </para></listitem>
-
- <listitem><para>
- Roaming profiles must be contained to the local network segment. Any
- departure from this may clog wide-area arteries and slow legitimate network
- traffic to a crawl.
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
- <figure id="chap7net">
- <title>Network Topology &smbmdash; 2000 User Complex Design A</title>
- <imagefile scale="80">chap7-net-Ar</imagefile>
- </figure>
-
- <figure id="chap7net2">
- <title>Network Topology &smbmdash; 2000 User Complex Design B</title>
- <imagefile scale="80">chap7-net2-Br</imagefile>
- </figure>
-
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- There is much rumor and misinformation regarding the use of MS Windows networking protocols.
- These questions are just a few of those frequently asked.
- </para>
-
- <qandaset defaultlabel="chap07qa" type="number">
- <qandaentry>
- <question>
-
- <para>
- <indexterm><primary>DHCP</primary></indexterm>
- <indexterm><primary>network</primary><secondary>bandwidth</secondary></indexterm>
- Is it true that DHCP uses lots of WAN bandwidth?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>DHCP</primary><secondary>Relay Agent</secondary></indexterm>
- <indexterm><primary>routers</primary></indexterm>
- <indexterm><primary>DHCP</primary><secondary>servers</secondary></indexterm>
- It is a smart practice to localize DHCP servers on each network segment. As a
- rule, there should be two DHCP servers per network segment. This means that if
- one server fails, there is always another to service user needs. DHCP requests use
- only UDP broadcast protocols. It is possible to run a DHCP Relay Agent on network
- routers. This makes it possible to run fewer DHCP servers.
- </para>
-
- <para>
- <indexterm><primary>DHCP</primary><secondary>request</secondary></indexterm>
- <indexterm><primary>DHCP</primary><secondary>traffic</secondary></indexterm>
- A DHCP network address request and confirmation usually results in about six UDP packets.
- The packets are from 60 to 568 bytes in length. Let us consider a site that has 300 DHCP
- clients and that uses a 24-hour IP address lease. This means that all clients renew
- their IP address lease every 24 hours. If we assume an average packet length equal to the
- maximum (just to be on the safe side), and we have a 128 Kb/sec wide-area connection,
- how significant would the DHCP traffic be if all of it were to use DHCP Relay?
- </para>
-
- <para>
- I must stress that this is a bad design, but here is the calculation:
-<screen>
-Daily Network Capacity: 128,000 (Kbits/s) / 8 (bits/byte)
- x 3600 (sec/hr) x 24 (hrs/day)= 2288 Mbytes/day.
-
-DHCP traffic: 300 (clients) x 6 (packets)
- x 512 (bytes/packet) = 0.9 Mbytes/day.
-</screen>
- From this can be seen that the traffic impact would be minimal.
- </para>
-
- <para>
- <indexterm><primary>DNS</primary><secondary>Dynamic</secondary></indexterm>
- <indexterm><primary>DHCP</primary></indexterm>
- Even when DHCP is configured to do DNS update (dynamic DNS) over a wide-area link,
- the impact of the update is no more than the DHCP IP address renewal traffic and thus
- still insignificant for most practical purposes.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- <indexterm><primary>background communication</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>master/slave</secondary><tertiary>background communication</tertiary></indexterm>
- How much background communication takes place between a master LDAP server and its slave LDAP servers?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>slurpd</primary></indexterm>
- The process that controls the replication of data from the master LDAP server to the slave LDAP
- servers is called <command>slurpd</command>. The <command>slurpd</command> remains nascent (quiet)
- until an update must be propagated. The propagation traffic per LDAP slave to update (add/modify/delete)
- two user accounts requires less than 10KB traffic.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- LDAP has a database. Is LDAP not just a fancy database front end?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>database</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>database</secondary></indexterm>
- <indexterm><primary>SQL</primary></indexterm>
- <indexterm><primary>transactional</primary></indexterm>
- LDAP does store its data in a database of sorts. In fact, the LDAP backend is an application-specific
- data storage system. This type of database is indexed so that records can be rapidly located, but the
- database is not generic and can be used only in particular pre-programmed ways. General external
- applications do not gain access to the data. This type of database is used also by SQL servers. Both
- an SQL server and an LDAP server provide ways to access the data. An SQL server has a transactional
- orientation and typically allows external programs to perform ad hoc queries, even across data tables.
- An LDAP front end is a purpose-built tool that has a search orientation that is designed around specific
- simple queries. The term <constant>database</constant> is heavily overloaded and thus much misunderstood.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- <indexterm><primary>OpenLDAP</primary></indexterm>
- Can Active Directory obtain account information from an OpenLDAP server?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>meta-directory</primary></indexterm>
- No, at least not directly. It is possible to provision Active Directory from and/or to an OpenLDAP
- database through use of a metadirectory server. Microsoft MMS (now called MIIS) can interface
- to OpenLDAP using standard LDAP queries and updates.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What are the parts of a roaming profile? How large is each part?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>roaming profile</primary>
- </indexterm>
- A roaming profile consists of
- </para>
-
- <itemizedlist>
- <listitem><para>
- Desktop folders such as <constant>Desktop</constant>, <constant>My Documents</constant>,
- <constant>My Pictures</constant>, <constant>My Music</constant>, <constant>Internet Files</constant>,
- <constant>Cookies</constant>, <constant>Application Data</constant>,
- <constant>Local Settings,</constant> and more. See <link linkend="happy"/>, <link linkend="XP-screen001"/>.
- </para>
-
- <para>
- <indexterm><primary>folder redirection</primary></indexterm>
- Each of these can be anywhere from a few bytes to gigabytes in capacity. Fortunately, all
- such folders can be redirected to network drive resources. See <link linkend="redirfold"/>
- for more information regarding folder redirection.
- </para></listitem>
-
- <listitem><para>
- A static or rewritable portion that is typically only a few files (2-5 KB of information).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>NTUSER.DAT</primary></indexterm>
- <indexterm><primary>HKEY_LOCAL_USER</primary></indexterm>
- The registry load file that modifies the <constant>HKEY_LOCAL_USER</constant> hive. This is
- the <filename>NTUSER.DAT</filename> file. It can be from 0.4 to 1.5 MB.
- </para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>Microsoft Outlook</primary><secondary>PST files</secondary></indexterm>
- Microsoft Outlook PST files may be stored in the <constant>Local Settings\Application Data</constant>
- folder. It can be up to 2 GB in size per PST file.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Can the <constant>My Documents</constant> folder be stored on a network drive?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>UNC name</primary></indexterm>
- <indexterm><primary>Universal Naming Convention</primary><see>UNC name</see></indexterm>
- Yes. More correctly, such folders can be redirected to network shares. No specific network drive
- connection is required. Registry settings permit this to be redirected directly to a UNC (Universal
- Naming Convention) resource, though it is possible to specify a network drive letter instead of a
- UNC name. See <link linkend="redirfold"/>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- <indexterm><primary>wide-area</primary></indexterm>
- <indexterm><primary>network</primary><secondary>bandwidth</secondary></indexterm>
- <indexterm><primary>WINS</primary></indexterm>
- How much WAN bandwidth does WINS consume?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>NetBIOS</primary><secondary>name cache</secondary></indexterm>
- <indexterm><primary>WINS server</primary></indexterm>
- <indexterm><primary>domain replication</primary></indexterm>
- MS Windows clients cache information obtained from WINS lookups in a local NetBIOS name cache.
- This keeps WINS lookups to a minimum. On a network with 3500 MS Windows clients and a central WINS
- server, the total bandwidth demand measured at the WINS server, averaged over an 8-hour working day,
- was less than 30 KB/sec. Analysis of network traffic over a 6-week period showed that the total
- of all background traffic consumed about 11 percent of available bandwidth over 64 Kb/sec links.
- Background traffic consisted of domain replication, WINS queries, DNS lookups, and authentication
- traffic. Each of 11 branch offices had a 64 Kb/sec wide-area link, with a 1.5 Mb/sec main connection
- that aggregated the branch office connections plus an Internet connection.
- </para>
-
- <para>
- In conclusion, the total load afforded through WINS traffic is again marginal to total operational
- usage &smbmdash; as it should be.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- How many BDCs should I have? What is the right number of Windows clients per server?
- </para>
-
- </question>
- <answer>
-
- <para>
- It is recommended to have at least one BDC per network segment, including the segment served
- by the PDC. Actual requirements vary depending on the working load on each of the BDCs and the
- load demand pattern of client usage. I have seen sites that function without problem with 200
- clients served by one BDC, and yet other sites that had one BDC per 20 clients. In one particular
- company, there was a drafting office that had 30 CAD/CAM operators served by one server, a print
- server; and an application server. While all three were BDCs, typically only the print server would
- service network logon requests after the first 10 users had started to use the network. This was
- a reflection of the service load placed on both the application server and the data server.
- </para>
-
- <para>
- As unsatisfactory as the answer might sound, it all depends on network and server load
- characteristics.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- <indexterm><primary>NIS server</primary></indexterm><indexterm><primary>LDAP</primary></indexterm>
- I've heard that you can store NIS accounts in LDAP. Is LDAP not just a smarter way to
- run an NIS server?
- </para>
-
- </question>
- <answer>
-
- <para>
- The correct answer to both questions is yes. But do understand that an LDAP server has
- a configurable schema that can store far more information for many more purposes than
- just NIS.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Can I use NIS in place of LDAP?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>NIS</primary></indexterm>
- <indexterm><primary>NIS schema</primary></indexterm>
- No. The NIS database does not have provision to store Microsoft encrypted passwords and does not deal
- with the types of data necessary for interoperability with Microsoft Windows networking. The use
- of LDAP with Samba requires the use of a number of schemas, one of which is the NIS schema, but also
- a Samba-specific schema extension.
- </para>
-
-</answer>
- </qandaentry>
-
- </qandaset>
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="Big500users">
- <title>The 500-User Office</title>
-
- <para>
- The Samba networking you explored in <link linkend="secure"/> covers the finer points of
- configuration of peripheral services such as DHCP and DNS, and WINS. You experienced
- implementation of a simple configuration of the services that are important adjuncts
- to successful deployment of Samba.
- </para>
-
- <para>
- An analysis of the history of postings to the Samba mailing list easily demonstrates
- that the two most prevalent Samba problem areas are
- </para>
-
- <itemizedlist>
- <listitem><para>
- Defective resolution of a NetBIOS name to its IP address
- </para></listitem>
-
- <listitem><para>
- Printing problems
- </para></listitem>
-
- </itemizedlist>
-
- <para>
- The exercises
- so far in this book have focused on implementation of the simplest printing processes
- involving no print job processing intelligence. In this chapter, you maintain
- that same approach to printing, but <link linkend="happy"/> presents an opportunity
- to make printing more complex for the administrator while making it easier for the user.
- </para>
-
- <para>
- <indexterm><primary>WINS server</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- <link linkend="secure"/> demonstrates operation of a DHCP server and a DNS server
- as well as a central WINS server. You validated the operation of these services and
- saw an effective implementation of a Samba domain controller using the
- <parameter>tdbsam</parameter> passdb backend.
- </para>
-
- <para>
- The objective of this chapter is to introduce more complex techniques that can be used to
- improve manageability of Samba as networking needs grow. In this chapter, you implement
- a distributed DHCP server environment, a distributed DNS server arrangement, a centralized
- WINS server, and a centralized Samba domain controller.
- </para>
-
- <para>
- A note of caution is important regarding the Samba configuration that is used in this
- chapter. The use of a single domain controller on a routed, multisegment network is
- a poor design choice that leads to potential network user complaints.
- This chapter demonstrates some successful
- techniques in deployment and configuration management. This should be viewed as a
- foundation chapter for complex Samba deployments.
- </para>
-
- <para>
- As you master the techniques presented here, you may find much better methods to
- improve network management and control while reducing human resource overheads.
- You should take the opportunity to innovate and expand on the methods presented
- here and explore them to the fullest.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- Business continues to go well for Abmas. Mr. Meany is driving your success and the
- network continues to grow thanks to the hard work Christine has done. You recently
- hired Stanley Soroka as manager of information systems. Christine recommended Stan
- to the role. She told you Stan is so good at handling Samba that he can make a cast
- iron rocking horse that is embedded in concrete kick like a horse at a rodeo. You
- need skills like his. Christine and Stan get along just fine. Let's see what
- you can get out of this pair as they plot the next-generation networks.
- </para>
-
- <para>
- Ten months ago Abmas closed an acquisition of a property insurance business. The
- founder lost interest in the business and decided to sell it to Mr. Meany. Because
- they were former university classmates, the purchase was concluded with mutual assent.
- The acquired business is located at the other end of town in much larger facilities.
- The old Abmas building has become too small. Located on the same campus as the newly
- acquired business are two empty buildings that are ideal to provide Abmas with
- opportunity for growth.
- </para>
-
- <para>
- Abmas has now completed the purchase of the two empty buildings, and you are
- to install a new network and relocate staff in nicely furnished new facilities.
- The new network is to be used to fully integrate company operations. You have
- decided to locate the new network operations control center in the larger building
- in which the insurance group is located to take advantage of an ideal floor space
- and to allow Stan and Christine to fully stage the new network and test it before
- it is rolled out. Your strategy is to complete the new network so that it
- is ready for operation when the old office moves into the new premises.
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- The acquired business had 280 network users. The old Abmas building housed
- 220 network users in unbelievably cramped conditions. The network that
- initially served 130 users now handles 220 users quite well.
- </para>
-
- <para>
- The two businesses will be fully merged to create a single campus company.
- The Property Insurance Group (PIG) houses 300 employees, the new Accounting
- Services Group (ASG) will be in a small building (BLDG1) that houses 50
- employees, and the Financial Services Group (FSG) will be housed in a large
- building that has capacity for growth (BLDG2). Building 2 houses 150 network
- users.
- </para>
-
- <para>
- You have decided to connect the building using fiber optic links between new
- routers. As a backup, the buildings are interconnected using line-of-sight
- high-speed infrared facilities. The infrared connection provides a
- secondary route to be used during periods of high demand for network
- bandwidth.
- </para>
-
- <para>
- The Internet gateway is upgraded to 15 Mb/sec service. Your ISP
- provides on your premises a fully managed Cisco PIX firewall. You no longer need
- to worry about firewall facilities on your network.
- </para>
-
- <para>
- Stanley and Christine have purchased new server hardware. Christine wants to
- roll out a network that has whistles and bells. Stan wants to start off with
- a simple to manage, not-too-complex network. He believes that network
- users need to be gradually introduced to new features and capabilities and not
- rushed into an environment that may cause disorientation and loss of productivity.
- </para>
-
- <para>
- Your intrepid network team has decided to implement a network configuration
- that closely mirrors the successful system you installed in the old Abmas building.
- The new network infrastructure is owned by Abmas, but all desktop systems
- are being procured through a new out-source services and leasing company. Under
- the terms of a deal with Mr. M. Proper (CEO), DirectPointe, Inc., provides
- all desktop systems and includes full level-one help desk support for
- a flat per-machine monthly fee. The deal allows you to add workstations on demand.
- This frees Stan and Christine to deal with deeper issues as they emerge and
- permits Stan to work on creating new future value-added services.
- </para>
-
- <para>
- DirectPointe Inc. receives from you a new standard desktop configuration
- every four months. They automatically roll that out to each desktop system.
- You must keep DirectPointe informed of all changes.
- </para>
-
- <para><indexterm>
- <primary>PDC</primary>
- </indexterm>
- The new network has a single Samba Primary Domain Controller (PDC) located in the
- Network Operation Center (NOC). Buildings 1 and 2 each have a local server
- for local application servicing. It is a domain member. The new system
- uses the <parameter>tdbsam</parameter> passdb backend.
- </para>
-
- <para>
- Printing is based on raw pass-through facilities just as it has been used so far.
- All printer drivers are installed on the desktop and notebook computers.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>network load factors</primary></indexterm>
- The example you are building in this chapter is of a network design that works, but this
- does not make it a design that is recommended. As a general rule, there should be at least
- one Backup Domain Controller (BDC) per 150 Windows network clients. The principle behind
- this recommendation is that correct operation of MS Windows clients requires rapid
- network response to all SMB/CIFS requests. The same rule says that if there are more than
- 50 clients per domain controller, they are too busy to service requests. Let's put such
- rules aside and recognize that network load affects the integrity of domain controller
- responsiveness. This network will have 500 clients serviced by one central domain
- controller. This is not a good omen for user satisfaction. You, of course, address this
- very soon (see <link linkend="happy"/>).
- </para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- Stan has talked you into a horrible compromise, but it is addressed. Just make
- certain that the performance of this network is well validated before going live.
- </para>
-
- <para>
- Design decisions made in this design include the following:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>identity management</primary></indexterm>
- A single PDC is being implemented. This limitation is based on the choice not to
- use LDAP. Many network administrators fear using LDAP because of the perceived
- complexity of implementation and management of an LDAP-based backend for all user
- identity management as well as to store network access credentials.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>machine secret password</primary></indexterm>
- Because of the refusal to use an LDAP (ldapsam) passdb backend at this time, the
- only choice that makes sense with 500 users is to use the tdbsam passwd backend.
- This type of backend is not receptive to replication to BDCs. If the tdbsam
- <filename>passdb.tdb</filename> file is replicated to BDCs using
- <command>rsync</command>, there are two potential problems: (1) data that is in
- memory but not yet written to disk will not be replicated, and (2) domain member
- machines periodically change the secret machine password. When this happens, there
- is no mechanism to return the changed password to the PDC.
- </para></listitem>
-
- <listitem><para>
- All domain user, group, and machine accounts are managed on the PDC. This makes
- for a simple mode of operation but has to be balanced with network performance and
- integrity of operations considerations.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>WINS</primary></indexterm>
- A single central WINS server is being used. The PDC is also the WINS server.
- Any attempt to operate a routed network without a WINS server while using NetBIOS
- over TCP/IP protocols does not work unless on each client the name resolution
- entries for the PDC are added to the <filename>LMHOSTS</filename>. This file is
- normally located on the Windows XP Professional client in the
- <filename>C:\WINDOWS\SYSTEM32\ETC\DRIVERS</filename> directory.
- </para></listitem>
-
- <listitem><para>
- At this time the Samba WINS database cannot be replicated. That is
- why a single WINS server is being implemented. This should work without a problem.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>winbindd</primary></indexterm>
- BDCs make use of <command>winbindd</command> to provide
- access to domain security credentials for file system access and object storage.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>DHCP</primary><secondary>relay</secondary></indexterm>
- <indexterm><primary>DHCP</primary><secondary>requests</secondary></indexterm>
- Configuration of Windows XP Professional clients is achieved using DHCP. Each
- subnet has its own DHCP server. Backup DHCP serving is provided by one
- alternate DHCP server. This necessitates enabling of the DHCP Relay agent on
- all routers. The DHCP Relay agent must be programmed to pass DHCP Requests from the
- network directed at the backup DHCP server.
- </para></listitem>
-
- <listitem><para>
- All network users are granted the ability to print to any printer that is
- network-attached. All printers are available from each server. Print jobs that
- are spooled to a printer that is not on the local network segment are automatically
- routed to the print spooler that is in control of that printer. The specific details
- of how this might be done are demonstrated for one example only.
- </para></listitem>
-
- <listitem><para>
- The network address and subnetmask chosen provide 1022 usable IP addresses in
- each subnet. If in the future more addresses are required, it would make sense
- to add further subnets rather than change addressing.
- </para></listitem>
-
- </itemizedlist>
-
- </sect2>
-
-
- <sect2>
- <title>Political Issues</title>
-
- <para>
- This case gets close to the real world. You and I know the right way to implement
- domain control. Politically, we have to navigate a minefield. In this case, the need is to
- get the PDC rolled out in compliance with expectations and also to be ready to save the day
- by having the real solution ready before it is needed. That real solution is presented in
- <link linkend="happy"/>.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- The following configuration process begins following installation of Red Hat Fedora Core2 on the
- three servers shown in the network topology diagram in <link linkend="chap05net"/>. You have
- selected hardware that is appropriate to the task.
- </para>
-
- <figure id="chap05net">
- <title>Network Topology &smbmdash; 500 User Network Using tdbsam passdb backend.</title>
- <imagefile scale="50">chap5-net</imagefile>
- </figure>
-
- <sect2 id="ch5-dnshcp-setup">
- <title>Installation of DHCP, DNS, and Samba Control Files</title>
-
- <para>
- Carefully install the configuration files into the correct locations as shown in
- <link linkend="ch5-filelocations"/>. You should validate that the full file path is
- correct as shown.
- </para>
-
- <para>
- The abbreviation shown in this table as <constant>{VLN}</constant> refers to
- the directory location beginning with <filename>/var/lib/named</filename>.
- </para>
-
-
- <table id="ch5-filelocations"><title>Domain: <constant>MEGANET</constant>, File Locations for Servers</title>
- <tgroup cols="5">
- <colspec colname='c1' align="left"/>
- <colspec colname='c2' align="left"/>
- <colspec colname='c3' align="center"/>
- <colspec colname='c4' align="center"/>
- <colspec colname='c5' align="center"/>
- <thead>
- <row>
- <entry align="center" namest='c1' nameend='c2'>File Information</entry>
- <entry align="center" namest="c3" nameend="c5">Server Name</entry>
- </row>
- <row>
- <entry align="center">Source</entry>
- <entry align="center">Target Location</entry>
- <entry align="center">MASSIVE</entry>
- <entry align="center">BLDG1</entry>
- <entry align="center">BLDG2</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><link linkend="ch5-massivesmb"/></entry>
- <entry><filename>/etc/samba/smb.conf</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="ch5-dc-common"/></entry>
- <entry><filename>/etc/samba/dc-common.conf</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="ch5-commonsmb"/></entry>
- <entry><filename>/etc/samba/common.conf</filename></entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="ch5-bldg1-smb"/></entry>
- <entry><filename>/etc/samba/smb.conf</filename></entry>
- <entry>No</entry>
- <entry>Yes</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="ch5-bldg2-smb"/></entry>
- <entry><filename>/etc/samba/smb.conf</filename></entry>
- <entry>No</entry>
- <entry>No</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="ch5-dommem-smb"/></entry>
- <entry><filename>/etc/samba/dommem.conf</filename></entry>
- <entry>No</entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="massive-dhcp"/></entry>
- <entry><filename>/etc/dhcpd.conf</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="bldg1dhcp"/></entry>
- <entry><filename>/etc/dhcpd.conf</filename></entry>
- <entry>No</entry>
- <entry>Yes</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="bldg2dhcp"/></entry>
- <entry><filename>/etc/dhcpd.conf</filename></entry>
- <entry>No</entry>
- <entry>No</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="massive-nameda"/></entry>
- <entry><filename>/etc/named.conf (part A)</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="massive-namedb"/></entry>
- <entry><filename>/etc/named.conf (part B)</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="massive-namedc"/></entry>
- <entry><filename>/etc/named.conf (part C)</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="abmasbizdns"/></entry>
- <entry><filename>{VLN}/master/abmas.biz.hosts</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="abmasusdns"/></entry>
- <entry><filename>{VLN}/master/abmas.us.hosts</filename></entry>
- <entry>Yes</entry>
- <entry>No</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry><link linkend="bldg12nameda"/></entry>
- <entry><filename>/etc/named.conf (part A)</filename></entry>
- <entry>No</entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="bldg12namedb"/></entry>
- <entry><filename>/etc/named.conf (part B)</filename></entry>
- <entry>No</entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="loopback"/></entry>
- <entry><filename>{VLN}/localhost.zone</filename></entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="dnsloopy"/></entry>
- <entry><filename>{VLN}/127.0.0.zone</filename></entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry><link linkend="roothint"/></entry>
- <entry><filename>{VLN}/root.hint</filename></entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- <entry>Yes</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- </sect2>
-
- <sect2>
- <title>Server Preparation: All Servers</title>
-
- <para>
- The following steps apply to all servers. Follow each step carefully.
- </para>
-
- <procedure>
- <title>Server Preparation Steps</title>
-
- <step><para>
- Using the UNIX/Linux system tools, set the name of the server as shown in the network
- topology diagram in <link linkend="chap05net"/>. For SUSE Linux products, the tool
- that permits this is called <command>yast2</command>; for Red Hat Linux products,
- you can use the <command>netcfg</command> tool.
- Verify that your hostname is correctly set by running:
-<screen>
-&rootprompt; uname -n
-</screen>
- An alternate method to verify the hostname is:
-<screen>
-&rootprompt; hostname -f
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- <indexterm><primary>named</primary></indexterm>
- Edit your <filename>/etc/hosts</filename> file to include the primary names and addresses
- of all network interfaces that are on the host server. This is necessary so that during
- startup the system is able to resolve all its own names to the IP address prior to
- startup of the DNS server. You should check the startup order of your system. If the
- CUPS print server is started before the DNS server (<command>named</command>), you
- should also include an entry for the printers in the <filename>/etc/hosts</filename> file.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/resolv.conf</primary></indexterm>
- All DNS name resolution should be handled locally. To ensure that the server is configured
- correctly to handle this, edit <filename>/etc/resolv.conf</filename> so it has the following
- content:
-<screen>
-search abmas.us abmas.biz
-nameserver 127.0.0.1
-</screen>
- This instructs the name resolver function (when configured correctly) to ask the DNS server
- that is running locally to resolve names to addresses.
- </para></step>
-
-
- <step><para>
- <indexterm><primary>administrator</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- Add the <constant>root</constant> user to the password backend:
-<screen>
-&rootprompt; smbpasswd -a root
-New SMB password: XXXXXXXX
-Retype new SMB password: XXXXXXXX
-&rootprompt;
-</screen>
- The <constant>root</constant> account is the UNIX equivalent of the Windows domain administrator.
- This account is essential in the regular maintenance of your Samba server. It must never be
- deleted. If for any reason the account is deleted, you may not be able to recreate this account
- without considerable trouble.
- </para></step>
-
- <step><para>
- <indexterm><primary>username map</primary></indexterm>
- <indexterm><primary>/etc/samba/smbusers</primary></indexterm>
- Create the username map file to permit the <constant>root</constant> account to be called
- <constant>Administrator</constant> from the Windows network environment. To do this, create
- the file <filename>/etc/samba/smbusers</filename> with the following contents:
-<screen>
-####
-# User mapping file
-####
-# File Format
-# -----------
-# Unix_ID = Windows_ID
-#
-# Examples:
-# root = Administrator
-# janes = "Jane Smith"
-# jimbo = Jim Bones
-#
-# Note: If the name contains a space it must be double quoted.
-# In the example above the name 'jimbo' will be mapped to Windows
-# user names 'Jim' and 'Bones' because the space was not quoted.
-#######################################################################
-root = Administrator
-####
-# End of File
-####
-</screen>
- </para></step>
-
- <step><para>
- Configure all network-attached printers to have a fixed IP address.
- </para></step>
-
- <step><para>
- Create an entry in the DNS database on the server <constant>MASSIVE</constant>
- in both the forward lookup database for the zone <constant>abmas.biz.hosts</constant>
- and in the reverse lookup database for the network segment that the printer is
- located in. Example configuration files for similar zones were presented in <link linkend="secure"/>,
- <link linkend="abmasbiz"/> and <link linkend="eth2zone"/>.
- </para></step>
-
- <step><para>
- Follow the instructions in the printer manufacturer's manuals to permit printing
- to port 9100. Use any other port the manufacturer specifies for direct mode,
- raw printing. This allows the CUPS spooler to print using raw mode protocols.
- <indexterm><primary>CUPS</primary></indexterm>
- <indexterm><primary>raw printing</primary></indexterm>
- </para></step>
-
- <step><para>
- <indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm>
- Only on the server to which the printer is attached configure the CUPS Print
- Queues as follows:
-<screen>
-&rootprompt; lpadmin -p <parameter>printque</parameter> -v socket://<parameter>printer-name</parameter>.abmas.biz:9100 -E
-</screen>
- <indexterm><primary>print filter</primary></indexterm>
- This step creates the necessary print queue to use no assigned print filter. This
- is ideal for raw printing, that is, printing without use of filters.
- The name <parameter>printque</parameter> is the name you have assigned for
- the particular printer.
- </para></step>
-
- <step><para>
- Print queues may not be enabled at creation. Make certain that the queues
- you have just created are enabled by executing the following:
-<screen>
-&rootprompt; /usr/bin/enable <parameter>printque</parameter>
-</screen>
- </para></step>
-
- <step><para>
- Even though your print queue may be enabled, it is still possible that it
- does not accept print jobs. A print queue services incoming printing
- requests only when configured to do so. Ensure that your print queue is
- set to accept incoming jobs by executing the following command:
-<screen>
-&rootprompt; /usr/bin/accept <parameter>printque</parameter>
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>mime type</primary></indexterm>
- <indexterm><primary>/etc/mime.convs</primary></indexterm>
- <indexterm><primary>application/octet-stream</primary></indexterm>
- This step, as well as the next one, may be omitted where CUPS version 1.1.18
- or later is in use. Although it does no harm to follow it anyway, and may
- help to avoid time spent later trying to figure out why print jobs may be
- disappearing without a trace. Look at these two steps as <emphasis>insurance</emphasis>
- against lost time. Edit file <filename>/etc/cups/mime.convs</filename> to
- uncomment the line:
-<screen>
-application/octet-stream application/vnd.cups-raw 0 -
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/mime.types</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
-<screen>
-application/octet-stream
-</screen>
- </para></step>
-
- <step><para>
- Refer to the CUPS printing manual for instructions regarding how to configure
- CUPS so that print queues that reside on CUPS servers on remote networks
- route print jobs to the print server that owns that queue. The default setting
- on your CUPS server may automatically discover remotely installed printers and
- may permit this functionality without requiring specific configuration.
- </para></step>
-
- <step><para>
- As part of the roll-out program, you need to configure the application's
- server shares. This can be done once on the central server and may then be
- replicated using a tool such as <command>rsync</command>. Refer to the man
- page for <command>rsync</command> for details regarding use. The notes in
- <link linkend="ch4appscfg"/> may help in your decisions to use an application
- server facility.
- </para></step>
-
- </procedure>
-
- <note><para>
- Logon scripts that are run from a domain controller (PDC or BDC) are capable of using semi-intelligent
- processes to automap Windows client drives to an application server that is nearest to the client. This
- is considerably more difficult when a single PDC is used on a routed network. It can be done, but not
- as elegantly as you see in the next chapter.
- </para></note>
-
- </sect2>
-
- <sect2>
- <title>Server-Specific Preparation</title>
-
- <para>
- There are some steps that apply to particular server functionality only. Each step is critical
- to correct server operation. The following step-by-step installation guidance will assist you
- in working through the process of configuring the PDC and then both BDC's.
- </para>
-
- <sect3>
- <title>Configuration for Server: <constant>MASSIVE</constant></title>
-
- <para>
- The steps presented here attempt to implement Samba installation in a generic manner. While
- some steps are clearly specific to Linux, it should not be too difficult to apply them to
- your platform of choice.
- </para>
-
- <procedure>
- <title>Primary Domain Controller Preparation</title>
-
- <step><para>
- <indexterm><primary>/etc/rc.d/boot.local</primary></indexterm>
- <indexterm><primary>IP forwarding</primary></indexterm>
- The host server acts as a router between the two internal network segments as well
- as for all Internet access. This necessitates that IP forwarding be enabled. This can be
- achieved by adding to the <filename>/etc/rc.d/boot.local</filename> an entry as follows:
-<screen>
-echo 1 > /proc/sys/net/ipv4/ip_forward
-</screen>
- To ensure that your kernel is capable of IP forwarding during configuration, you may wish to execute
- that command manually also. This setting permits the Linux system to act as a router.
- </para></step>
-
- <step><para>
- This server is dual hosted (i.e., has two network interfaces) &smbmdash; one goes to the Internet
- and the other to a local network that has a router that is the gateway to the remote networks.
- You must therefore configure the server with route table entries so that it can find machines
- on the remote networks. You can do this using the appropriate system tools for your Linux
- server or using static entries that you place in one of the system startup files. It is best
- to always use the tools that the operating system vendor provided. In the case of SUSE Linux, the
- best tool to do this is YaST (refer to SUSE Administration Manual); in the case of Red Hat,
- this is best done using the graphical system configuration tools (see the Red Hat documentation).
- An example of how this may be done manually is as follows:
-<screen>
-&rootprompt; route add net 172.16.4.0 netmask 255.255.252.0 gw 172.16.0.128
-&rootprompt; route add net 172.16.8.0 netmask 255.255.252.0 gw 172.16.0.128
-</screen>
- If you just execute these commands manually, the route table entries you have created are
- not persistent across system reboots. You may add these commands directly to the local
- startup files as follows: (SUSE) <filename>/etc/rc.d/boot.local</filename>, (Red Hat)
- <filename>/etc/rc.d/init.d/rc.local</filename>.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The final step that must be completed is to edit the <filename>/etc/nsswitch.conf</filename> file.
- This file controls the operation of the various resolver libraries that are part of the Linux
- Glibc libraries. Edit this file so that it contains the following entries:
-<screen>
-hosts: files dns wins
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>initGrps.sh</primary></indexterm>
- Create and map Windows domain groups to UNIX groups. A sample script is provided in
- <link linkend="ch5-initgrps"/>. Create a file containing this script. You called yours
- <filename>/etc/samba/initGrps.sh</filename>. Set this file so it can be executed
- and then execute the script. An example of the execution of this script as well as its
- validation are shown in Section 4.3.2, Step 5.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>password</primary><secondary>backend</secondary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- For each user who needs to be given a Windows domain account, make an entry in the
- <filename>/etc/passwd</filename> file as well as in the Samba password backend.
- Use the system tool of your choice to create the UNIX system account, and use the Samba
- <command>smbpasswd</command> to create a domain user account.
- </para>
-
- <para>
- <indexterm><primary>useradd</primary></indexterm>
- <indexterm><primary>adduser</primary></indexterm>
- <indexterm><primary>user</primary><secondary>management</secondary></indexterm>
- There are a number of tools for user management under UNIX, such as
- <command>useradd</command>, <command>adduser</command>, as well as a plethora of custom
- tools. With the tool of your choice, create a home directory for each user.
- </para></step>
-
- <step><para>
- Using the preferred tool for your UNIX system, add each user to the UNIX groups created
- previously as necessary. File system access control is based on UNIX group membership.
- </para></step>
-
- <step><para>
- Create the directory mount point for the disk subsystem that is to be mounted to provide
- data storage for company files, in this case, the mount point indicated in the &smb.conf;
- file is <filename>/data</filename>. Format the file system as required and mount the formatted
- file system partition using appropriate system tools.
- </para></step>
-
- <step><para>
- <indexterm><primary>file system</primary>
- <secondary>permissions</secondary></indexterm>
- Create the top-level file storage directories for data and applications as follows:
-<screen>
-&rootprompt; mkdir -p /data/{accounts,finsvcs,pidata}
-&rootprompt; mkdir -p /apps
-&rootprompt; chown -R root:root /data
-&rootprompt; chown -R root:root /apps
-&rootprompt; chown -R bjordan:accounts /data/accounts
-&rootprompt; chown -R bjordan:finsvcs /data/finsvcs
-&rootprompt; chown -R bjordan:finsvcs /data/pidata
-&rootprompt; chmod -R ug+rwxs,o-rwx /data
-&rootprompt; chmod -R ug+rwx,o+rx-w /apps
-</screen>
- Each department is responsible for creating its own directory structure within the departmental
- share. The directory root of the <command>accounts</command> share is <filename>/data/accounts</filename>.
- The directory root of the <command>finsvcs</command> share is <filename>/data/finsvcs</filename>.
- The <filename>/apps</filename> directory is the root of the <constant>apps</constant> share
- that provides the application server infrastructure.
- </para></step>
-
- <step><para>
- The &smb.conf; file specifies an infrastructure to support roaming profiles and network
- logon services. You can now create the file system infrastructure to provide the
- locations on disk that these services require. Adequate planning is essential
- because desktop profiles can grow to be quite large. For planning purposes, a minimum of
- 200 MB of storage should be allowed per user for profile storage. The following
- commands create the directory infrastructure needed:
-<screen>
-&rootprompt; mkdir -p /var/spool/samba
-&rootprompt; mkdir -p /var/lib/samba/{netlogon/scripts,profiles}
-&rootprompt; chown -R root:root /var/spool/samba
-&rootprompt; chown -R root:root /var/lib/samba
-&rootprompt; chmod a+rwxt /var/spool/samba
-</screen>
- For each user account that is created on the system, the following commands should be
- executed:
-<screen>
-&rootprompt; mkdir /var/lib/samba/profiles/'username'
-&rootprompt; chown 'username':users /var/lib/samba/profiles/'username'
-&rootprompt; chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>unix2dos</primary></indexterm>
- <indexterm><primary>dos2unix</primary></indexterm>
- Create a logon script. It is important that each line is correctly terminated with
- a carriage return and line-feed combination (i.e., DOS encoding). The following procedure
- works if the right tools (<constant>unxi2dos</constant> and <constant>dos2unix</constant>) are installed.
- First, create a file called <filename>/var/lib/samba/netlogon/scripts/logon.bat.unix</filename>
- with the following contents:
-<screen>
-net time \\massive /set /yes
-net use h: /home
-</screen>
- Convert the UNIX file to a DOS file:
-<screen>
-&rootprompt; dos2unix < /var/lib/samba/netlogon/scripts/logon.bat.unix \
- > /var/lib/samba/netlogon/scripts/logon.bat
-</screen>
- </para></step>
-
- <step><para>
- There is one preparatory step without which you cannot have a working Samba network
- environment. You must add an account for each network user. You can do this by executing
- the following steps for each user:
-<screen>
-&rootprompt; useradd -m <parameter>username</parameter>
-&rootprompt; passwd <parameter>username</parameter>
-Changing password for <parameter>username</parameter>.
-New password: XXXXXXXX
-Re-enter new password: XXXXXXXX
-Password changed
-&rootprompt; smbpasswd -a <parameter>username</parameter>
-New SMB password: XXXXXXXX
-Retype new SMB password: XXXXXXXX
-Added user <parameter>username</parameter>.
-</screen>
- You do, of course, use a valid user login ID in place of <parameter>username</parameter>.
- </para></step>
-
- <step><para>
- Follow the processes shown in <link linkend="ch5-procstart"/> to start all services.
- </para></step>
-
- <step><para>
- Your server is ready for validation testing. Do not proceed with the steps in
- <link linkend="ch5-domsvrspec"/> until after the operation of the server has been
- validated following the same methods as outlined in <link linkend="secure"/>, <link linkend="ch4valid"/>.
- </para></step>
-
- </procedure>
-
- </sect3>
-
- <sect3 id="ch5-domsvrspec">
- <title>Configuration Specific to Domain Member Servers: <constant>BLDG1, BLDG2</constant></title>
-
- <para>
- The following steps will guide you through the nuances of implementing BDCs for the broadcast
- isolated network segments. Remember that if the target installation platform is not Linux, it may
- be necessary to adapt some commands to the equivalent on the target platform.
- </para>
-
- <procedure>
- <title>Backup Domain Controller Configuration Steps</title>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The final step that must be completed is to edit the <filename>/etc/nsswitch.conf</filename> file.
- This file controls the operation of the various resolver libraries that are part of the Linux
- Glibc libraries. Edit this file so that it contains the following entries:
-<screen>
-passwd: files winbind
-group: files winbind
-hosts: files dns wins
-</screen>
- </para></step>
-
- <step><para>
- Follow the steps outlined in <link linkend="ch5-procstart"/> to start all services. Do not
- start Samba at this time. Samba is controlled by the process called <command>smb</command>.
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
- You must now attempt to join the domain member servers to the domain. The following
- instructions should be executed to effect this:
-<screen>
-&rootprompt; net rpc join
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>service</primary><secondary>smb</secondary><tertiary>start</tertiary></indexterm>
- You now start the Samba services by executing:
-<screen>
-&rootprompt; service smb start
-</screen>
- </para></step>
-
- <step><para>
- Your server is ready for validation testing. Do not proceed with the steps in
- <link linkend="ch5-domsvrspec"/> until after the operation of the server has been
- validated following the same methods as outlined in <link linkend="ch4valid"/>.
- </para></step>
-
- </procedure>
-
- </sect3>
-
- </sect2>
-
-<!-- One -->
-<example id="ch5-massivesmb">
-<title>Server: MASSIVE (PDC), File: <filename>/etc/samba/smb.conf</filename></title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MEGANET</smbconfoption>
-<smbconfoption name="netbios name">MASSIVE</smbconfoption>
-<smbconfoption name="interfaces">eth1, lo</smbconfoption>
-<smbconfoption name="bind interfaces only">Yes</smbconfoption>
-<smbconfoption name="passdb backend">tdbsam</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
-<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
-<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
-<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
-<smbconfoption name="add user to group script">/usr/sbin/usermod -G '%g' '%u'</smbconfoption>
-<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="wins support">Yes</smbconfoption>
-<smbconfoption name="include">/etc/samba/dc-common.conf</smbconfoption>
-
-<smbconfsection name="[accounts]"/>
-<smbconfoption name="comment">Accounting Files</smbconfoption>
-<smbconfoption name="path">/data/accounts</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[service]"/>
-<smbconfoption name="comment">Financial Services Files</smbconfoption>
-<smbconfoption name="path">/data/service</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[pidata]"/>
-<smbconfoption name="comment">Property Insurance Files</smbconfoption>
-<smbconfoption name="path">/data/pidata</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<!-- Two -->
-<example id="ch5-dc-common">
-<title>Server: MASSIVE (PDC), File: <filename>/etc/samba/dc-common.conf</filename></title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
-<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
-<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
-<smbconfoption name="logon path">\%L\profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">X:</smbconfoption>
-<smbconfoption name="logon home">\%L\%U</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="include">/etc/samba/common.conf</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network Logon Service</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="locking">No</smbconfoption>
-
-<smbconfsection name="[profiles]"/>
-<smbconfoption name="comment">Profile Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<!-- Three -->
-<example id="ch5-commonsmb">
-<title>Common Samba Configuration File: <filename>/etc/samba/common.conf</filename></title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">50</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="time server">Yes</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
-<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
-<smbconfoption name="utmp">Yes</smbconfoption>
-<smbconfoption name="map acl inherit">Yes</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-<smbconfoption name="veto files">/*.eml/*.nws/*.{*}/</smbconfoption>
-<smbconfoption name="veto oplock files">/*.doc/*.xls/*.mdb/</smbconfoption>
-<smbconfoption name="include"> </smbconfoption>
-
-<smbconfcomment>Share and Service Definitions are common to all servers</smbconfcomment>
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="default devmode">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[apps]"/>
-<smbconfoption name="comment">Application Files</smbconfoption>
-<smbconfoption name="path">/apps</smbconfoption>
-<smbconfoption name="admin users">bjordan</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<!-- Four -->
-<example id="ch5-bldg1-smb">
-<title>Server: BLDG1 (Member), File: smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MEGANET</smbconfoption>
-<smbconfoption name="netbios name">BLDG1</smbconfoption>
-<smbconfoption name="include">/etc/samba/dom-mem.conf</smbconfoption>
-</smbconfblock>
-</example>
-
-<!-- Five -->
-<example id="ch5-bldg2-smb">
-<title>Server: BLDG2 (Member), File: smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MEGANET</smbconfoption>
-<smbconfoption name="netbios name">BLDG2</smbconfoption>
-<smbconfoption name="include">/etc/samba/dom-mem.conf</smbconfoption>
-</smbconfblock>
-</example>
-
-<!-- Six -->
-<example id="ch5-dommem-smb">
-<title>Common Domain Member Include File: dom-mem.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
-<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="wins server">172.16.0.1</smbconfoption>
-<smbconfoption name="idmap uid">15000-20000</smbconfoption>
-<smbconfoption name="idmap gid">15000-20000</smbconfoption>
-<smbconfoption name="include">/etc/samba/common.conf</smbconfoption>
-</smbconfblock>
-</example>
-
-<!-- Seven -->
-<example id="massive-dhcp">
-<title>Server: MASSIVE, File: dhcpd.conf</title>
-<screen>
-# Abmas Accounting Inc.
-
-default-lease-time 86400;
-max-lease-time 172800;
-default-lease-time 86400;
-ddns-updates on;
-ddns-update-style interim;
-
-option ntp-servers 172.16.0.1;
-option domain-name "abmas.biz";
-option domain-name-servers 172.16.0.1, 172.16.4.1;
-option netbios-name-servers 172.16.0.1;
-option netbios-node-type 8;
-
-subnet 172.16.1.0 netmask 255.255.252.0 {
- range dynamic-bootp 172.16.1.0 172.16.2.255;
- option subnet-mask 255.255.252.0;
- option routers 172.16.0.1, 172.16.0.128;
- allow unknown-clients;
- }
-subnet 172.16.4.0 netmask 255.255.252.0 {
- range dynamic-bootp 172.16.7.0 172.16.7.254;
- option subnet-mask 255.255.252.0;
- option routers 172.16.4.128;
- allow unknown-clients;
- }
-subnet 172.16.8.0 netmask 255.255.252.0 {
- range dynamic-bootp 172.16.11.0 172.16.11.254;
- option subnet-mask 255.255.252.0;
- option routers 172.16.4.128;
- allow unknown-clients;
- }
-subnet 127.0.0.0 netmask 255.0.0.0 {
- }
-subnet 123.45.67.64 netmask 255.255.255.252 {
- }
-</screen>
-</example>
-
-<!-- Eight -->
-<example id="bldg1dhcp">
-<title>Server: BLDG1, File: dhcpd.conf</title>
-<screen>
-# Abmas Accounting Inc.
-
-default-lease-time 86400;
-max-lease-time 172800;
-default-lease-time 86400;
-ddns-updates on;
-ddns-update-style ad-hoc;
-
-option ntp-servers 172.16.0.1;
-option domain-name "abmas.biz";
-option domain-name-servers 172.16.0.1, 172.16.4.1;
-option netbios-name-servers 172.16.0.1;
-option netbios-node-type 8;
-
-subnet 172.16.1.0 netmask 255.255.252.0 {
- range dynamic-bootp 172.16.3.0 172.16.3.255;
- option subnet-mask 255.255.252.0;
- option routers 172.16.0.1, 172.16.0.128;
- allow unknown-clients;
- }
-subnet 172.16.4.0 netmask 255.255.252.0 {
- range dynamic-bootp 172.16.5.0 172.16.6.255;
- option subnet-mask 255.255.252.0;
- option routers 172.16.4.128;
- allow unknown-clients;
- }
-subnet 127.0.0.0 netmask 255.0.0.0 {
- }
-</screen>
-</example>
-
-<!-- Nine -->
-<example id="bldg2dhcp">
-<title>Server: BLDG2, File: dhcpd.conf</title>
-<screen>
-# Abmas Accounting Inc.
-
-default-lease-time 86400;
-max-lease-time 172800;
-default-lease-time 86400;
-ddns-updates on;
-ddns-update-style interim;
-
-option ntp-servers 172.16.0.1;
-option domain-name "abmas.biz";
-option domain-name-servers 172.16.0.1, 172.16.4.1;
-option netbios-name-servers 172.16.0.1;
-option netbios-node-type 8;
-
-subnet 172.16.8.0 netmask 255.255.252.0 {
- range dynamic-bootp 172.16.9.0 172.16.10.255;
- option subnet-mask 255.255.252.0;
- option routers 172.16.8.128;
- allow unknown-clients;
- }
-subnet 127.0.0.0 netmask 255.0.0.0 {
- }
-</screen>
-</example>
-
-<!-- Ten -->
-<example id="massive-nameda">
-<title>Server: MASSIVE, File: named.conf, Part: A</title>
-<screen>
-###
-# Abmas Biz DNS Control File
-###
-# Date: November 15, 2003
-###
-options {
- directory "/var/lib/named";
- forwarders {
- 123.45.12.23;
- 123.45.54.32;
- };
- forward first;
- listen-on {
- mynet;
- };
- auth-nxdomain yes;
- multiple-cnames yes;
- notify no;
-};
-
-zone "." in {
- type hint;
- file "root.hint";
-};
-
-zone "localhost" in {
- type master;
- file "localhost.zone";
-};
-
-zone "0.0.127.in-addr.arpa" in {
- type master;
- file "127.0.0.zone";
-};
-
-acl mynet {
- 172.16.0.0/24;
- 172.16.4.0/24;
- 172.16.8.0/24;
- 127.0.0.1;
-};
-
-acl seconddns {
- 123.45.54.32;
-};
-</screen>
-</example>
-
-<!-- Eleven -->
-<example id="massive-namedb">
-<title>Server: MASSIVE, File: named.conf, Part: B</title>
-<screen>
-zone "abmas.biz" {
- type master;
- file "/var/lib/named/master/abmas.biz.hosts";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-
-zone "abmas.us" {
- type master;
- file "/var/lib/named/master/abmas.us.hosts";
- allow-query {
- all;
- };
- allow-transfer {
- seconddns;
- };
-};
-</screen>
-</example>
-
-<!-- Twelve -->
-<example id="massive-namedc">
-<title>Server: MASSIVE, File: named.conf, Part: C</title>
-<screen>
-zone "0.16.172.in-addr.arpa" {
- type master;
- file "/var/lib/named/master/172.16.0.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-
-zone "4.16.172.in-addr.arpa" {
- type master;
- file "/var/lib/named/master/172.16.4.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-
-zone "8.16.172.in-addr.arpa" {
- type master;
- file "/var/lib/named/master/172.16.8.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-</screen>
-</example>
-
-<!-- Thirteen -->
-<example id="abmasbizdns">
-<title>Forward Zone File: abmas.biz.hosts</title>
-<screen>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-abmas.biz IN SOA massive.abmas.biz. root.abmas.biz. (
- 2003021833 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS massive.abmas.biz.
- NS bldg1.abmas.biz.
- NS bldg2.abmas.biz.
- MX 10 massive.abmas.biz.
-$ORIGIN abmas.biz.
-massive A 172.16.0.1
-router0 A 172.16.0.128
-bldg1 A 172.16.4.1
-router4 A 172.16.4.128
-bldg2 A 172.16.8.1
-router8 A 172.16.8.128
-</screen>
-</example>
-
-<!-- Forteen -->
-<example id="abmasusdns">
-<title>Forward Zone File: abmas.biz.hosts</title>
-<screen>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-abmas.us IN SOA server.abmas.us. root.abmas.us. (
- 2003021833 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS dns.abmas.us.
- NS dns2.abmas.us.
- MX 10 mail.abmas.us.
-$ORIGIN abmas.us.
-server A 123.45.67.66
-dns2 A 123.45.54.32
-gw A 123.45.67.65
-www CNAME server
-mail CNAME server
-dns CNAME server
-</screen>
-</example>
-
-<!-- Fifteen -->
-<example id="bldg12nameda">
-<title>Servers: BLDG1/BLDG2, File: named.conf, Part: A</title>
-<screen>
-###
-# Abmas Biz DNS Control File
-###
-# Date: November 15, 2003
-###
-options {
- directory "/var/lib/named";
- forwarders {
- 172.16.0.1;
- };
- forward first;
- listen-on {
- mynet;
- };
- auth-nxdomain yes;
- multiple-cnames yes;
- notify no;
-};
-
-zone "." in {
- type hint;
- file "root.hint";
-};
-
-zone "localhost" in {
- type master;
- file "localhost.zone";
-};
-
-zone "0.0.127.in-addr.arpa" in {
- type master;
- file "127.0.0.zone";
-};
-
-acl mynet {
- 172.16.0.0/24;
- 172.16.4.0/24;
- 172.16.8.0/24;
- 127.0.0.1;
-};
-
-acl seconddns {
- 123.45.54.32;
-};
-</screen>
-</example>
-
-<!-- Sixteen -->
-<example id="bldg12namedb">
-<title>Servers: BLDG1/BLDG2, File: named.conf, Part: B</title>
-<screen>
-zone "abmas.biz" {
- type slave;
- file "/var/lib/named/slave/abmas.biz.hosts";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
-};
-
-zone "0.16.172.in-addr.arpa" {
- type slave;
- file "/var/lib/slave/master/172.16.0.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
-};
-
-zone "4.16.172.in-addr.arpa" {
- type slave;
- file "/var/lib/named/slave/172.16.4.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
-};
-
-zone "8.16.172.in-addr.arpa" {
- type slave;
- file "/var/lib/named/slave/172.16.8.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
-};
-</screen>
-</example>
-
-
-<!-- Seventeen -->
-<example id="ch5-initgrps">
-<title>Initialize Groups Script, File: /etc/samba/initGrps.sh</title>
-<screen>
-#!/bin/bash
-
-# Create UNIX groups
-groupadd acctsdep
-groupadd finsrvcs
-groupadd piops
-
-# Map Windows Domain Groups to UNIX groups
-net groupmap add ntgroup="Domain Admins" unixgroup=root type=d
-net groupmap add ntgroup="Domain Users" unixgroup=users type=d
-net groupmap add ntgroup="Domain Guests" unixgroup=nobody type=d
-
-# Add Functional Domain Groups
-net groupmap add ntgroup="Accounts Dept" unixgroup=acctsdep type=d
-net groupmap add ntgroup="Financial Services" unixgroup=finsrvcs type=d
-net groupmap add ntgroup="Insurance Group" unixgroup=piops type=d
-</screen>
-</example>
-
-<!-- End of Examples -->
-
- <sect2 id="ch5-procstart">
- <title>Process Startup Configuration</title>
-
- <para>
- <indexterm><primary>chkconfig</primary></indexterm>
- <indexterm><primary>daemon control</primary></indexterm>
- There are two essential steps to process startup configuration. A process
- must be configured so that it is automatically restarted each time the server
- is rebooted. This step involves use of the <command>chkconfig</command> tool that
- created appropriate symbolic links from the master daemon control file that is
- located in the <filename>/etc/rc.d</filename> directory to the <filename>/etc/rc'x'.d</filename>
- directories. Links are created so that when the system run-level is changed, the
- necessary start or kill script is run.
- </para>
-
- <para>
- <indexterm><primary>/etc/xinetd.d</primary></indexterm>
- In the event that a service is provided not as a daemon but via the internetworking
- super daemon (<command>inetd</command> or <command>xinetd</command>), then the <command>chkconfig</command>
- tool makes the necessary entries in the <filename>/etc/xinetd.d</filename> directory
- and sends a hang-up (HUP) signal to the super daemon, thus forcing it to
- re-read its control files.
- </para>
-
- <para>
- Last, each service must be started to permit system validation to proceed. The following steps
- are for a Red Hat Linux system, please adapt them to suit the target OS platform on which you
- are installing Samba.
- </para>
-
- <procedure>
- <title>Process Startup Configuration Steps</title>
-
- <step><para>
- Use the standard system tool to configure each service to restart
- automatically at every system reboot. For example,
- <indexterm><primary>chkconfig</primary></indexterm>
-<screen>
-&rootprompt; chkconfig dhpc on
-&rootprompt; chkconfig named on
-&rootprompt; chkconfig cups on
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig swat on
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>starting dhcpd</primary></indexterm>
- <indexterm><primary>starting samba</primary></indexterm>
- <indexterm><primary>starting CUPS</primary></indexterm>
- Now start each service to permit the system to be validated.
- Execute each of the following in the sequence shown:
-
-<screen>
-&rootprompt; service dhcp restart
-&rootprompt; service named restart
-&rootprompt; service cups restart
-&rootprompt; service smb restart
-&rootprompt; service swat restart
-</screen>
- </para></step>
- </procedure>
-
- </sect2>
-
- <sect2 id="ch5wincfg">
- <title>Windows Client Configuration</title>
-
- <para>
- The procedure for desktop client configuration for the network in this chapter is similar to
- that used for the previous one. There are a few subtle changes that should be noted.
- </para>
-
- <procedure>
- <title>Windows Client Configuration Steps</title>
-
- <step><para>
- Install MS Windows XP Professional. During installation, configure the client to use DHCP for
- TCP/IP protocol configuration.
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>DHCP</primary></indexterm>
- DHCP configures all Windows clients to use the WINS Server address that has been defined
- for the local subnet.
- </para></step>
-
- <step><para>
- Join the Windows domain <constant>MEGANET</constant>. Use the domain administrator
- username <constant>root</constant> and the SMB password you assigned to this account.
- A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to
- a Windows domain is given in <link linkend="appendix"/>, <link linkend="domjoin"/>.
- Reboot the machine as prompted and then log on using the domain administrator account
- (<constant>root</constant>).
- </para></step>
-
- <step><para>
- Verify that the server called <constant>MEGANET</constant> is visible in <guimenu>My Network Places</guimenu>,
- that it is possible to connect to it and see the shares <guimenuitem>accounts</guimenuitem>,
- <guimenuitem>apps</guimenuitem>, and <guimenuitem>finsvcs</guimenuitem>,
- and that it is possible to open each share to reveal its contents.
- </para></step>
-
- <step><para>
- Create a drive mapping to the <constant>apps</constant> share on a server. At this time, it does
- not particularly matter which application server is used. It is necessary to manually
- set a persistent drive mapping to the local applications server on each workstation at the time of
- installation. This step is avoided by the improvements to the design of the network configuration
- in the next chapter.
- </para></step>
-
- <step><para>
- Perform an administrative installation of each application to be used. Select the options
- that you wish to use. Of course, you choose to run applications over the network, correct?
- </para></step>
-
- <step><para>
- Now install all applications to be installed locally. Typical tools include Adobe Acrobat,
- NTP-based time synchronization software, drivers for specific local devices such as fingerprint
- scanners, and the like. Probably the most significant application to be locally installed
- is antivirus software.
- </para></step>
-
- <step><para>
- Now install all four printers onto the staging system. The printers you install
- include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers, and you
- also configure use of the identical printers that are located in the financial services department.
- Install printers on each machine using the following steps:
- </para>
-
- <procedure>
- <title>Steps to Install Printer Drivers on Windows Clients</title>
-
- <step><para>
- Click <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Settings</guimenuitem>
- <guimenuitem>Printers</guimenuitem>
- <guiicon>Add Printer</guiicon>
- <guibutton>Next</guibutton>
- </menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
- Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
- </para></step>
-
- <step><para>
- Click <guibutton>Next</guibutton>. In the
- <guimenuitem>Manufacturer:</guimenuitem> panel, select <constant>HP</constant>.
- In the <guimenuitem>Printers:</guimenuitem> panel, select the printer called
- <constant>HP LaserJet 6</constant>. Click <guibutton>Next</guibutton>.
- </para></step>
-
- <step><para>
- In the <guimenuitem>Available ports:</guimenuitem> panel, select
- <constant>FILE:</constant>. Accept the default printer name by clicking
- <guibutton>Next</guibutton>. When asked, <quote>Would you like to print a
- test page?</quote>, click <guimenuitem>No</guimenuitem>. Click
- <guibutton>Finish</guibutton>.
- </para></step>
-
- <step><para>
- You may be prompted for the name of a file to print to. If so, close the
- dialog panel. Right-click <menuchoice>
- <guiicon>HP LaserJet 6</guiicon>
- <guimenuitem>Properties</guimenuitem>
- <guisubmenu>Details (Tab)</guisubmenu>
- <guibutton>Add Port</guibutton>
- </menuchoice>.
- </para></step>
-
- <step><para>
- In the <guimenuitem>Network</guimenuitem> panel, enter the name of
- the print queue on the Samba server as follows: <constant>\\BLDG1\hplj6a</constant>.
- Click <menuchoice>
- <guibutton>OK</guibutton>
- <guibutton>OK</guibutton>
- </menuchoice> to complete the installation.
- </para></step>
-
- <step><para>
- Repeat the printer installation steps above for both HP LaserJet 6 printers
- as well as for both QMS Magicolor laser printers. Remember to install all
- printers but to set the destination port for each to the server on the
- local network. For example, a workstation in the accounting group should
- have all printers directed at the server <constant>BLDG1</constant>.
- You may elect to point all desktop workstation configurations at the
- server called <constant>MASSIVE</constant> and then in your deployment
- procedures, it would be wise to document the need to redirect the printer
- configuration (as well as the applications server drive mapping) to the
- server on the network segment on which the workstation is to be located.
- </para></step>
- </procedure>
- </step>
-
- <step><para>
- When you are satisfied that the staging systems are complete, use the appropriate procedure to
- remove the client from the domain. Reboot the system, and then log on as the local administrator
- and clean out all temporary files stored on the system. Before shutting down, use the disk
- defragmentation tool so that the file system is in optimal condition before replication.
- </para></step>
-
- <step><para>
- Boot the workstation using the Norton (Symantec) Ghosting disk (or CD-ROM) and image the
- machine to a network share on the server.
- </para></step>
-
- <step><para>
- You may now replicate the image using the appropriate Norton Ghost procedure to the target
- machines. Make sure to use the procedure that ensures each machine has a unique
- Windows security identifier (SID). When the installation of the disk image is complete, boot the PC.
- </para></step>
-
- <step><para>
- Log onto the machine as the local Administrator (the only option), and join the machine to
- the domain following the procedure set out in <link linkend="appendix"/>, <link linkend="domjoin"/>. You must now set the
- persistent drive mapping to the applications server that the user is to use. The system is now
- ready for the user to log on, provided you have created a network logon account for that
- user, of course.
- </para></step>
-
- <step><para>
- Instruct all users to log onto the workstation using their assigned username and password.
- </para></step>
- </procedure>
-
- </sect2>
-
- <sect2>
- <title>Key Points Learned</title>
-
- <para>
- The network you have just deployed has been a valuable exercise in forced constraint.
- You have deployed a network that works well, although you may soon start to see
- performance problems, at which time the modifications demonstrated in <link linkend="happy"/>
- bring the network to life. The following key learning points were experienced:
- </para>
-
- <itemizedlist>
- <listitem><para>
- The power of using &smb.conf; include files
- </para></listitem>
-
- <listitem><para>
- Use of a single PDC over a routed network
- </para></listitem>
-
- <listitem><para>
- Joining a Samba domain member server to a Samba-3 domain
- </para></listitem>
-
- <listitem><para>
- Configuration of winbind to use domain users and groups for Samba access
- to resources on the domain member servers
- </para></listitem>
-
- <listitem><para>
- The introduction of roaming profiles
- </para></listitem>
-
- </itemizedlist>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- </para>
-
- <qandaset defaultlabel="chap01qa" type="number">
- <qandaentry>
- <question>
-
- <para>
- The example &smb.conf; files in this chapter make use of the <parameter>include</parameter> facility.
- How may I get to see what the actual working &smb.conf; settings are?
- </para>
-
- </question>
- <answer>
-
- <para>
- You may readily see the net compound effect of the included files by running:
-<screen>
-&rootprompt; testparm -s | less
-</screen>
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why does the include file <filename>common.conf</filename> have an empty include statement?
- </para>
-
- </question>
- <answer>
-
- <para>
- The use of the empty include statement nullifies further includes. For example, let's say you
- desire to have just an smb.conf file that is built from the array of include files of which the
- master control file is called <filename>master.conf</filename>. The following command
- produces a compound &smb.conf; file.
-<screen>
-&rootprompt; testparm -s /etc/samba/master.conf > /etc/samba/smb.conf
-</screen>
- If the include parameter was not in the common.conf file, the final &smb.conf; file leaves
- the include in place, even though the file it points to has already been included. This is a bug
- that will be fixed at a future date.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- I accept that the simplest configuration necessary to do the job is the best. The use of <parameter>tdbsam</parameter>
- passdb backend is much simpler than having to manage an LDAP-based <parameter>ldapsam</parameter> passdb backend.
- I tried using <command>rsync</command> to replicate the <filename>passdb.tdb</filename>, and it seems to work fine!
- So what is the problem?
- </para>
-
- </question>
- <answer>
-
- <para>
- Replication of the <parameter>tdbsam</parameter> database file can result in loss of currency in its
- contents between the PDC and BDCs. The most notable symptom is that workstations may not be able
- to log onto the network following a reboot and may have to rejoin the domain to recover network
- access capability.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- You are using DHCP Relay enabled on the routers as well as a local DHCP server. Will this cause a clash?
- </para>
-
- </question>
- <answer>
-
- <para>
- No. It is possible to have as many DHCP servers on a network segment as makes sense. A DHCP server
- offers an IP address lease, but it is the client that determines which offer is accepted, no matter how many
- offers are made. Under normal operation, the client accepts the first offer it receives.
- </para>
-
- <para>
- The only exception to this rule is when the client makes a directed request from a specific DHCP server
- for renewal of the lease it has. This means that under normal circumstances there is no risk of a clash.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- How does the Windows client find the PDC?
- </para>
-
- </question>
- <answer>
-
- <para>
- The Windows client obtains the WINS server address from the DHCP lease information. It also
- obtains from the DHCP lease information the parameter that causes it to use directed UDP (UDP Unicast)
- to register itself with the WINS server and to obtain enumeration of vital network information to
- enable it to operate successfully.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why did you enable IP forwarding (routing) only on the server called <constant>MASSIVE</constant>?
- </para>
-
- </question>
- <answer>
-
- <para>
- The server called <constant>MASSIVE</constant> is acting as a router to the Internet. No other server
- (BLDG1 or BLDG2) has any need for IP forwarding because they are attached only to their own network.
- Route table entries are needed to direct MASSIVE to send all traffic intended for the remote network
- segments to the router that is its gateway to them.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- You did nothing special to implement roaming profiles. Why?
- </para>
-
- </question>
- <answer>
-
- <para>
- Unless configured to do otherwise, the default behavior with Samba and Windows XP Professional
- clients is to use roaming profiles.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- On the domain member computers, you configured winbind in the <filename>/etc/nsswitch.conf</filename> file.
- You did not configure any PAM settings. Is this an omission?
- </para>
-
- </question>
- <answer>
-
- <para>
- PAM is needed only for authentication. When Samba is using Microsoft encrypted passwords, it makes only
- marginal use of PAM. PAM configuration handles only authentication. If you want to log onto the domain
- member servers using Windows networking usernames and passwords, it is necessary to configure PAM
- to enable the use of winbind. Samba makes use only of the identity resolution facilities of the name
- service switch (NSS).
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- You are starting SWAT up on this example but have not discussed that anywhere. Why did you do this?
- </para>
-
- </question>
- <answer>
-
- <para>
- Oh, I did not think you would notice that. It is there so that it can be used. This is more fully discussed
- in <emphasis>TOSHARG2</emphasis>, which has a full chapter dedicated to the subject. While we are on the
- subject, it should be noted that you should definitely not use SWAT on any system that makes use
- of &smb.conf; <parameter>include</parameter> files because SWAT optimizes them out into an aggregated
- file but leaves in place a broken reference to the top-layer include file. SWAT was not designed to
- handle this functionality gracefully.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- The domain controller has an auto-shutdown script. Isn't that dangerous?
- </para>
-
- </question>
- <answer>
-
- <para>
- Well done, you spotted that! I guess it is dangerous. It is good to know that you can do this, though.
- </para>
-
- </answer>
- </qandaentry>
-
- </qandaset>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="unixclients">
- <title>Adding Domain Member Servers and Clients</title>
-
- <para><indexterm>
- <primary>Open Magazine</primary>
- </indexterm><indexterm>
- <primary>survey</primary>
- </indexterm>
- The most frequently discussed Samba subjects over the past 2 years have focused around domain control and printing.
- It is well known that Samba is a file and print server. A recent survey conducted by <emphasis>Open Magazine</emphasis> found
- that of all respondents, 97 percent use Samba for file and print services, and 68 percent use Samba for Domain Control. See the
- <ulink url="http://www.open-mag.com/cgi-bin/opencgi/surveys/survey.cgi?survey_name=samba">Open-Mag</ulink>
- Web site for current information. The survey results as found on January 14, 2004, are shown in
- <link linkend="ch09openmag"/>.
- </para>
-
- <figure id="ch09openmag">
- <title>Open Magazine Samba Survey</title>
- <imagefile scale="60">openmag</imagefile>
- </figure>
-
- <para>
- While domain control is an exciting subject, basic file and print sharing remains the staple bread-and-butter
- function that Samba provides. Yet this book may give the appearance of having focused too much on more
- exciting aspects of Samba deployment. This chapter directs your attention to provide important information on
- the addition of Samba servers into your present Windows network &smbmdash; whatever the controlling technology
- may be. So let's get back to our good friends at Abmas.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para><indexterm>
- <primary>Linux desktop</primary>
- </indexterm><indexterm>
- <primary>Domain Member</primary>
- <secondary>server</secondary>
- </indexterm>
- Looking back over the achievements of the past year or two, daily events at Abmas are rather straightforward
- with not too many distractions or problems. Your team is doing well, but a number of employees
- are asking for Linux desktop systems. Your network has grown and demands additional domain member servers. Let's
- get on with this; Christine and Stan are ready to go.
- </para>
-
- <para><indexterm>
- <primary>Domain Member</primary>
- <secondary>desktop</secondary>
- </indexterm>
- Stan is firmly in control of the department of the future, while Christine is enjoying a stable and
- predictable network environment. It is time to add more servers and to add Linux desktops. It is
- time to meet the demands of future growth and endure trial by fire.
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para><indexterm>
- <primary>Active Directory</primary>
- </indexterm>
- You must now add UNIX/Linux domain member servers to your network. You have a friend who has a Windows 2003
- Active Directory domain network who wants to add a Samba/Linux server and has asked Christine to help him
- out. Your real objective is to help Christine to see more of the way the Microsoft world lives and use
- her help to get validation that Samba really does live up to expectations.
- </para>
-
- <para>
- Over the past 6 months, you have hired several new staff who want Linux on their desktops. You must integrate
- these systems to make sure that Abmas is not building islands of technology. You ask Christine to
- do likewise at Swodniw Biz NL (your friend's company) to help them to evaluate a Linux desktop. You want to make
- the right decision, don't you?
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>winbind</primary></indexterm>
- Recent Samba mailing-list activity is witness to how many sites are using winbind. Some have no trouble
- at all with it, yet to others the problems seem insurmountable. Periodically there are complaints concerning
- an inability to achieve identical user and group IDs between Windows and UNIX environments.
- </para>
-
- <para>
- You provide step-by-step implementations of the various tools that can be used for identity
- resolution. You also provide working examples of solutions for integrated authentication for
- both UNIX/Linux and Windows environments.
- </para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- One of the great challenges we face when people ask us, <quote>What is the best way to solve
- this problem?</quote> is to get beyond the facts so we not only can clearly comprehend
- the immediate technical problem, but also can understand how needs may change.
- </para>
-
- <para>
- <indexterm><primary>integrate</primary></indexterm>
- There are a few facts we should note when dealing with the question of how best to
- integrate UNIX/Linux clients and servers into a Windows networking environment:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>Domain Controller</primary></indexterm>
- <indexterm><primary>authoritative</primary></indexterm>
- <indexterm><primary>accounts</primary><secondary>authoritative</secondary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- A domain controller (PDC or BDC) is always authoritative for all accounts in its domain.
- This means that a BDC must (of necessity) be able to resolve all account UIDs and GIDs
- to the same values that the PDC resolved them to.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>local accounts</primary></indexterm>
- <indexterm><primary>Domain Member</primary><secondary>authoritative</secondary><tertiary>local accounts</tertiary></indexterm>
- <indexterm><primary>Domain accounts</primary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- A domain member can be authoritative for local accounts, but is never authoritative for
- domain accounts. If a user is accessing a domain member server and that user's account
- is not known locally, the domain member server must resolve the identity of that user
- from the domain in which that user's account resides. It must then map that ID to a
- UID/GID pair that it can use locally. This is handled by <command>winbindd</command>.
- </para></listitem>
-
- <listitem><para>
- Samba, when running on a domain member server, can resolve user identities from a
- number of sources:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>getpwnam</primary></indexterm>
- <indexterm><primary>getgrnam</primary></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>NIS</primary></indexterm>
- By executing a system <command>getpwnam()</command> or <command>getgrnam()</command> call.
- On systems that support it, this utilizes the name service switch (NSS) facility to
- resolve names according to the configuration of the <filename>/etc/nsswitch.conf</filename>
- file. NSS can be configured to use LDAP, winbind, NIS, or local files.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>PADL</primary></indexterm>
- <indexterm><primary>nss_ldap</primary></indexterm>
- Performing, via NSS, a direct LDAP search (where an LDAP passdb backend has been configured).
- This requires the use of the PADL nss_ldap tool (or equivalent).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>winbindd_idmap.tdb</primary></indexterm>
- <indexterm><primary>winbindd_cache.tdb</primary></indexterm>
- Directly by querying <command>winbindd</command>. The <command>winbindd</command>
- contacts a domain controller to attempt to resolve the identity of the user or group. It
- receives the Windows networking security identifier (SID) for that appropriate
- account and then allocates a local UID or GID from the range of available IDs and
- creates an entry in its <filename>winbindd_idmap.tdb</filename> and
- <filename>winbindd_cache.tdb</filename> files.
- </para>
-
- <para>
- <indexterm><primary>idmap backend</primary></indexterm>
- <indexterm><primary>mapping</primary></indexterm>
- If the parameter <smbconfoption name="idmap backend">ldap:ldap://myserver.domain</smbconfoption>
- was specified and the LDAP server has been configured with a container in which it may
- store the IDMAP entries, all domain members may share a common mapping.
- </para></listitem>
- </itemizedlist>
-
- <para>
- Irrespective of how &smb.conf; is configured, winbind creates and caches a local copy of
- the ID mapping database. It uses the <filename>winbindd_idmap.tdb</filename> and
- <filename>winbindd_cache.tdb</filename> files to do this.
- </para>
-
- <para>
- Which of the resolver methods is chosen is determined by the way that Samba is configured
- in the &smb.conf; file. Some of the configuration options are rather less than obvious to the
- casual user.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>winbind trusted domains only</primary></indexterm>
- <indexterm><primary>domain member</primary><secondary>servers</secondary></indexterm>
- <indexterm><primary>domain controllers</primary></indexterm>
- If you wish to make use of accounts (users and/or groups) that are local to (i.e., capable
- of being resolved using) the NSS facility, it is possible to use the
- <smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
- in the &smb.conf; file. This parameter specifically applies to domain controllers,
- and to domain member servers.
- </para></listitem>
-
- </itemizedlist>
-
- <para>
- <indexterm><primary>Posix accounts</primary></indexterm>
- <indexterm><primary>Samba accounts</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- For many administrators, it should be plain that the use of an LDAP-based repository for all network
- accounts (both for POSIX accounts and for Samba accounts) provides the most elegant and
- controllable facility. You eventually appreciate the decision to use LDAP.
- </para>
-
- <para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- <indexterm><primary>identifiers</primary></indexterm>
- <indexterm><primary>resolve</primary></indexterm>
- If your network account information resides in an LDAP repository, you should use it ahead of any
- alternative method. This means that if it is humanly possible to use the <command>nss_ldap</command>
- tools to resolve UNIX account UIDs/GIDs via LDAP, this is the preferred solution, because it provides
- a more readily controllable method for asserting the exact same user and group identifiers
- throughout the network.
- </para>
-
- <para>
- <indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
- <indexterm><primary>winbind trusted domains only</primary></indexterm>
- <indexterm><primary>getpwnam</primary></indexterm>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>Trusted Domains</primary></indexterm>
- <indexterm><primary>External Domains</primary></indexterm>
- In the situation where UNIX accounts are held on the domain member server itself, the only effective
- way to use them involves the &smb.conf; entry
- <smbconfoption name="winbind trusted domains only">Yes</smbconfoption>. This forces
- Samba (<command>smbd</command>) to perform a <command>getpwnam()</command> system call that can
- then be controlled via <filename>/etc/nsswitch.conf</filename> file settings. The use of this parameter
- disables the use of Samba with trusted domains (i.e., external domains).
- </para>
-
- <para>
- <indexterm><primary>appliance mode</primary></indexterm>
- <indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>automatically allocate</primary></indexterm>
- Winbind can be used to create an appliance mode domain member server. In this capacity, <command>winbindd</command>
- is configured to automatically allocate UIDs/GIDs from numeric ranges set in the &smb.conf; file. The allocation
- is made for all accounts that connect to that domain member server, whether within its own domain or from
- trusted domains. If not stored in an LDAP backend, each domain member maintains its own unique mapping database.
- This means that it is almost certain that a given user who accesses two domain member servers does not have the
- same UID/GID on both servers &smbmdash; however, this is transparent to the Windows network user. This data
- is stored in the <filename>winbindd_idmap.tdb</filename> and <filename>winbindd_cache.tdb</filename> files.
- </para>
-
- <para>
- <indexterm><primary>mapping</primary></indexterm>
- The use of an LDAP backend for the Winbind IDMAP facility permits Windows domain SIDs
- mappings to UIDs/GIDs to be stored centrally. The result is a consistent mapping across all domain member
- servers so configured. This solves one of the major headaches for network administrators who need to copy
- files between or across network file servers.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Political Issues</title>
-
- <para>
- <indexterm><primary>OpenLDAP</primary></indexterm>
- <indexterm><primary>NIS</primary></indexterm>
- <indexterm><primary>yellow pages</primary><see>NIS</see></indexterm>
- <indexterm><primary>identity management</primary></indexterm>
- One of the most fierce conflicts recently being waged is resistance to the adoption of LDAP, in
- particular OpenLDAP, as a replacement for UNIX NIS (previously called Yellow Pages). Let's face it, LDAP
- is different and requires a new approach to the need for a better identity management solution. The more
- you work with LDAP, the more its power and flexibility emerges from its dark, cavernous chasm.
- </para>
-
- <para>
- LDAP is a most suitable solution for heterogenous environments. If you need crypto, add Kerberos.
- The reason these are preferable is because they are heterogenous. Windows solutions of this sort are <emphasis>not</emphasis>
- heterogenous by design. This is fundamental &smbmdash; it isn't religious or political. This also doesn't say that
- you can't use Windows Active Directory in a heterogenous environment &smbmdash; it can be done, it just requires
- commercial integration products. But it's not what Active Directory was designed for.
- </para>
-
- <para>
- <indexterm><primary>directory</primary></indexterm>
- <indexterm><primary>management</primary></indexterm>
- A number of long-term UNIX devotees have recently commented in various communications that the Samba Team
- is the first application group to almost force network administrators to use LDAP. It should be pointed
- out that we resisted this for as long as we could. It is not out of laziness or malice that LDAP has
- finally emerged as the preferred identity management backend for Samba. We recommend LDAP for your total
- organizational directory needs.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- <indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
- <indexterm><primary>Domain Member</primary><secondary>client</secondary></indexterm>
- <indexterm><primary>Domain Controller</primary></indexterm>
- The domain member server and the domain member client are at the center of focus in this chapter.
- Configuration of Samba domain controller is covered in earlier chapters, so if your
- interest is in domain controller configuration, you will not find that here. You will find good
- oil that helps you to add domain member servers and clients.
- </para>
-
- <para>
- <indexterm><primary>Domain Member</primary><secondary>workstations</secondary></indexterm>
- In practice, domain member servers and domain member workstations are very different entities, but in
- terms of technology they share similar core infrastructure. A technologist would argue that servers
- and workstations are identical. Many users would argue otherwise, given that in a well-disciplined
- environment a workstation (client) is a device from which a user creates documents and files that
- are located on servers. A workstation is frequently viewed as a disposable (easy to replace) item,
- but a server is viewed as a core component of the business.
- </para>
-
- <para>
- <indexterm><primary>workstation</primary></indexterm>
- We can look at this another way. If a workstation breaks down, one user is affected, but if a
- server breaks down, hundreds of users may not be able to work. The services that a workstation
- must provide are document- and file-production oriented; a server provides information storage
- and is distribution oriented.
- </para>
-
- <para>
- <indexterm><primary>authentication process</primary></indexterm>
- <indexterm><primary>logon process</primary></indexterm>
- <indexterm><primary>user identities</primary></indexterm>
- <emphasis>Why is this important?</emphasis> For starters, we must identify what
- components of the operating system and its environment must be configured. Also, it is necessary
- to recognize where the interdependencies between the various services to be used are.
- In particular, it is important to understand the operation of each critical part of the
- authentication process, the logon process, and how user identities get resolved and applied
- within the operating system and applications (like Samba) that depend on this and may
- actually contribute to it.
- </para>
-
- <para>
- So, in this chapter we demonstrate how to implement the technology. It is done within a context of
- what type of service need must be fulfilled.
- </para>
-
- <sect2 id="sdcsdmldap">
- <title>Samba Domain with Samba Domain Member Server &smbmdash; Using NSS LDAP</title>
-
- <para>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>ldapsam backend</primary></indexterm>
- <indexterm><primary>IDMAP</primary></indexterm>
- <indexterm><primary>mapping</primary><secondary>consistent</secondary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>foreign SID</primary></indexterm>
- In this example, it is assumed that you have Samba PDC/BDC servers. This means you are using
- an LDAP ldapsam backend. We are adding to the LDAP backend database (directory)
- containers for use by the IDMAP facility. This makes it possible to have globally consistent
- mapping of SIDs to and from UIDs and GIDs. This means that it is necessary to run
- <command>winbindd</command> as part of your configuration. The primary purpose of running
- <command>winbindd</command> (within this operational context) is to permit mapping of foreign
- SIDs (those not originating from the the local Samba server). Foreign SIDs can come from any
- domain member client or server, or from Windows clients that do not belong to a domain. Another
- way to explain the necessity to run <command>winbindd</command> is that Samba can locally
- resolve only accounts that belong to the security context of its own machine SID. Winbind
- handles all non-local SIDs and maps them to a local UID/GID value. The UID and GID are allocated
- from the parameter values set in the &smb.conf; file for the <parameter>idmap uid</parameter> and
- <parameter>idmap gid</parameter> ranges. Where LDAP is used, the mappings can be stored in LDAP
- so that all domain member servers can use a consistent mapping.
- </para>
-
- <para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>getpwnam</primary></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- If your installation is accessed only from clients that are members of your own domain, and all
- user accounts are present in a local passdb backend then it is not necessary to run
- <command>winbindd</command>. The local passdb backend can be in smbpasswd, tdbsam, or in ldapsam.
- </para>
-
- <para>
- It is possible to use a local passdb backend with any convenient means of resolving the POSIX
- user and group account information. The POSIX information is usually obtained using the
- <command>getpwnam()</command> system call. On NSS-enabled systems, the actual POSIX account
- source can be provided from
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>/etc/group</primary></indexterm>
- Accounts in <filename>/etc/passwd</filename> or in <filename>/etc/group</filename>.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>compat</primary></indexterm>
- <indexterm><primary>ldap</primary></indexterm>
- <indexterm><primary>nis</primary></indexterm>
- <indexterm><primary>nisplus</primary></indexterm>
- <indexterm><primary>hesiod</primary></indexterm>
- <indexterm><primary>ldap</primary></indexterm>
- <indexterm><primary>nss_ldap</primary></indexterm>
- <indexterm><primary>PADL Software</primary></indexterm>
- Resolution via NSS. On NSS-enabled systems, there is usually a facility to resolve IDs
- via multiple methods. The methods typically include <command>files</command>,
- <command>compat</command>, <command>db</command>, <command>ldap</command>,
- <command>nis</command>, <command>nisplus</command>, <command>hesiod.</command> When
- correctly installed, Samba adds to this list the <command>winbindd</command> facility.
- The ldap facility is frequently the nss_ldap tool provided by PADL Software.
- </para></listitem>
- </itemizedlist>
-
- <note><para>
- To advoid confusion the use of the term <literal>local passdb backend</literal> means that
- the user account backend is not shared by any other Samba server &smbmdash; instead, it is
- used only locally on the Samba domain member server under discussion.
- </para></note>
-
- <para>
- <indexterm><primary>Identity resolution</primary></indexterm>
- The diagram in <link linkend="ch9-sambadc"/> demonstrates the relationship of Samba and system
- components that are involved in the identity resolution process where Samba is used as a domain
- member server within a Samba domain control network.
- </para>
-
-<figure id="ch9-sambadc">
- <title>Samba Domain: Samba Member Server</title>
- <imagefile scale="60">chap9-SambaDC</imagefile>
-</figure>
-
- <para>
- <indexterm><primary>IDMAP</primary></indexterm>
- <indexterm><primary>foreign</primary></indexterm>
- In this example configuration, Samba will directly search the LDAP-based passwd backend ldapsam
- to obtain authentication and user identity information. The IDMAP information is stored in the LDAP
- backend so that it can be shared by all domain member servers so that every user will have a
- consistent UID and GID across all of them. The IDMAP facility will be used for all foreign
- (i.e., not having the same SID as the domain it is a member of) domains. The configuration of
- NSS will ensure that all UNIX processes will obtain a consistent UID/GID.
- </para>
-
- <para>
- The instructions given here apply to the Samba environment shown in <link linkend="happy"/> and <link linkend="net2000users"/>.
- If the network does not have an LDAP slave server (i.e., <link linkend="happy"/> configuration),
- change the target LDAP server from <constant>lapdc</constant> to <constant>massive.</constant>
- </para>
-
- <procedure>
- <title>Configuration of NSS_LDAP-Based Identity Resolution</title>
-
- <step><para>
- Create the &smb.conf; file as shown in <link linkend="ch9-sdmsdc"/>. Locate
- this file in the directory <filename>/etc/samba</filename>.
- </para></step>
-
- <step><para>
- <indexterm><primary>ldap.conf</primary></indexterm>
- Configure the file that will be used by <constant>nss_ldap</constant> to
- locate and communicate with the LDAP server. This file is called <filename>ldap.conf</filename>.
- If your implementation of <constant>nss_ldap</constant> is consistent with
- the defaults suggested by PADL (the authors), it will be located in the
- <filename>/etc</filename> directory. On some systems, the default location is
- the <filename>/etc/openldap</filename> directory, however this file is intended
- for use by the OpenLDAP utilities and should not really be used by the nss_ldap
- utility since its content and structure serves the specific purpose of enabling
- the resolution of user and group IDs via NSS.
- </para>
-
- <para>
- Change the parameters inside the file that is located on your OS so it matches
- <link linkend="ch9-sdmlcnf"/>. To find the correct location of this file, you
- can obtain this from the library that will be used by executing the following:
-<screen>
-&rootprompt; strings /lib/libnss_ldap* | grep ldap.conf
-/etc/ldap.conf
-</screen>
- </para></step>
-
- <step><para>
- Configure the NSS control file so it matches the one shown in
- <link linkend="ch9-sdmnss"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>Identity resolution</primary></indexterm>
- <indexterm><primary>getent</primary></indexterm>
- Before proceeding to configure Samba, validate the operation of the NSS identity
- resolution via LDAP by executing:
-<screen>
-&rootprompt; getent passwd
-...
-root:x:0:512:Netbios Domain Administrator:/root:/bin/false
-nobody:x:999:514:nobody:/dev/null:/bin/false
-bobj:x:1000:513:Robert Jordan:/home/bobj:/bin/bash
-stans:x:1001:513:Stanley Soroka:/home/stans:/bin/bash
-chrisr:x:1002:513:Christine Roberson:/home/chrisr:/bin/bash
-maryv:x:1003:513:Mary Vortexis:/home/maryv:/bin/bash
-jht:x:1004:513:John H Terpstra:/home/jht:/bin/bash
-bldg1$:x:1006:553:bldg1$:/dev/null:/bin/false
-temptation$:x:1009:553:temptation$:/dev/null:/bin/false
-vaioboss$:x:1005:553:vaioboss$:/dev/null:/bin/false
-fran$:x:1008:553:fran$:/dev/null:/bin/false
-josephj:x:1007:513:Joseph James:/home/josephj:/bin/bash
-</screen>
- You should notice the location of the users' home directories. First, make certain that
- the home directories exist on the domain member server; otherwise, the home directory
- share is not available. The home directories could be mounted off a domain controller
- using NFS or by any other suitable means. Second, the absence of the domain name in the
- home directory path is indicative that identity resolution is not being done via winbind.
-<screen>
-&rootprompt; getent group
-...
-Domain Admins:x:512:root,jht
-Domain Users:x:513:bobj,stans,chrisr,maryv,jht,josephj
-Domain Guests:x:514:
-Accounts:x:1000:
-Finances:x:1001:
-PIOps:x:1002:
-sammy:x:4321:
-</screen>
- <indexterm><primary>secondary group</primary></indexterm>
- <indexterm><primary>primary group</primary></indexterm>
- <indexterm><primary>group membership</primary></indexterm>
- This shows that all is working as it should be. Notice that in the LDAP database
- the users' primary and secondary group memberships are identical. It is not
- necessary to add secondary group memberships (in the group database) if the
- user is already a member via primary group membership in the password database.
- When using winbind, it is in fact undesirable to do this because it results in
- doubling up of group memberships and may cause problems with winbind under certain
- conditions. It is intended that these limitations with winbind will be resolved soon
- after Samba-3.0.20 has been released.
- </para></step>
-
- <step><para>
- <indexterm><primary>slapcat</primary></indexterm>
- The LDAP directory must have a container object for IDMAP data. There are several ways you can
- check that your LDAP database is able to receive IDMAP information. One of the simplest is to
- execute:
-<screen>
-&rootprompt; slapcat | grep -i idmap
-dn: ou=Idmap,dc=abmas,dc=biz
-ou: idmap
-</screen>
- <indexterm><primary>ldapadd</primary></indexterm>
- If the execution of this command does not return IDMAP entries, you need to create an LDIF
- template file (see <link linkend="ch9-ldifadd"/>). You can add the required entries using
- the following command:
-<screen>
-&rootprompt; ldapadd -x -D "cn=Manager,dc=abmas,dc=biz" \
- -w not24get < /etc/openldap/idmap.LDIF
-</screen>
- </para></step>
-
- <step><para>
- Samba automatically populates the LDAP directory container when it needs to. To permit Samba
- write access to the LDAP directory it is necessary to set the LDAP administrative password
- in the <filename>secrets.tdb</filename> file as shown here:
-<screen>
-&rootprompt; smbpasswd -w not24get
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
- <indexterm><primary>Domain join</primary></indexterm>
- The system is ready to join the domain. Execute the following:
-<screen>
-&rootprompt; net rpc join -U root%not24get
-Joined domain MEGANET2.
-</screen>
- This indicates that the domain join succeeded.
- </para>
-
- <para>
- Failure to join the domain could be caused by any number of variables. The most common
- causes of failure to join are:
- </para>
-
- <para>
- <itemizedlist>
- <listitem><para>Broken resolution of NetBIOS names to the respective IP address.</para></listitem>
- <listitem><para>Incorrect username and password credentials.</para></listitem>
- <listitem><para>The NT4 <parameter>restrict anonymous</parameter> is set to exclude anonymous
- connections.</para></listitem>
- </itemizedlist>
- </para>
-
- <para>
- The connection setup can be diagnosed by executing:
-<screen>
-&rootprompt; net rpc join -S 'pdc-name' -U administrator%password -d 5
-</screen>
- <indexterm><primary>failed</primary></indexterm>
- <indexterm><primary>failed join</primary></indexterm>
- <indexterm><primary>rejected</primary></indexterm>
- <indexterm><primary>restrict anonymous</primary></indexterm>
- Note: Use "root" for UNIX/Linux and Samba, use "Administrator" for Windows NT4/200X. If the cause of
- the failure appears to be related to a rejected or failed NT_SESSION_SETUP* or an error message that
- says NT_STATUS_ACCESS_DENIED immediately check the Windows registry setting that controls the
- <constant>restrict anonymous</constant> setting. Set this to the value 0 so that an anonymous connection
- can be sustained, then try again.
- </para>
-
- <para>
- It is possible (perhaps even recommended) to use the following to validate the ability to connect
- to an NT4 PDC/BDC:
-<screen>
-&rootprompt; net rpc info -S 'pdc-name' -U Administrator%not24get
-Domain Name: MEGANET2
-Domain SID: S-1-5-21-422319763-4138913805-7168186429
-Sequence number: 1519909596
-Num users: 7003
-Num domain groups: 821
-Num local groups: 8
-
-&rootprompt; net rpc testjoin -S 'pdc-name' -U Administrator%not24get
-Join to 'MEGANET2' is OK
-</screen>
- If for any reason the following response is obtained to the last command above,it is time to
- call in the Networking Super-Snooper task force (i.e., start debugging):
-<screen>
-NT_STATUS_ACCESS_DENIED
-Join to 'MEGANET2' failed.
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>wbinfo</primary></indexterm>
- Just joining the domain is not quite enough; you must now provide a privileged set
- of credentials through which <command>winbindd</command> can interact with the
- domain servers. Execute the following to implant the necessary credentials:
-<screen>
-&rootprompt; wbinfo --set-auth-user=Administrator%not24get
-</screen>
- The configuration is now ready to obtain the Samba domain user and group information.
- </para></step>
-
- <step><para>
- You may now start Samba in the usual manner, and your Samba domain member server
- is ready for use. Just add shares as required.
- </para></step>
-
- </procedure>
-
-<example id="ch9-sdmsdc">
-<title>Samba Domain Member in Samba Domain Using LDAP &smbmdash; &smb.conf; File</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="unix charset">LOCALE</smbconfoption>
-<smbconfoption name="workgroup">MEGANET2</smbconfoption>
-<smbconfoption name="security">DOMAIN</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">10</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">50</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="wins server">192.168.2.1</smbconfoption>
-<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="idmap backend">ldap:ldap://lapdc.abmas.biz</smbconfoption>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
-<smbconfoption name="admin users">root, Administrator</smbconfoption>
-<smbconfoption name="write list">root</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch9-ldifadd">
-<title>LDIF IDMAP Add-On Load File &smbmdash; File: /etc/openldap/idmap.LDIF</title>
-<screen>
-dn: ou=Idmap,dc=abmas,dc=biz
-objectClass: organizationalUnit
-ou: idmap
-structuralObjectClass: organizationalUnit
-</screen>
-</example>
-
-<example id="ch9-sdmlcnf">
-<title>Configuration File for NSS LDAP Support &smbmdash; <filename>/etc/ldap.conf</filename></title>
-<screen>
-URI ldap://massive.abmas.biz ldap://massive.abmas.biz:636
-host 192.168.2.1
-base dc=abmas,dc=biz
-binddn cn=Manager,dc=abmas,dc=biz
-bindpw not24get
-
-pam_password exop
-
-nss_base_passwd ou=People,dc=abmas,dc=biz?one
-nss_base_shadow ou=People,dc=abmas,dc=biz?one
-nss_base_group ou=Groups,dc=abmas,dc=biz?one
-ssl no
-</screen>
-</example>
-
-<example id="ch9-sdmnss">
-<title>NSS using LDAP for Identity Resolution &smbmdash; File: <filename>/etc/nsswitch.conf</filename></title>
-<screen>
-passwd: files ldap
-shadow: files ldap
-group: files ldap
-
-hosts: files dns wins
-networks: files dns
-
-services: files
-protocols: files
-rpc: files
-ethers: files
-netmasks: files
-netgroup: files
-publickey: files
-
-bootparams: files
-automount: files
-aliases: files
-</screen>
-</example>
-
- </sect2>
-
- <sect2 id="wdcsdm">
- <title>NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind</title>
-
- <para>
- You need to use this method for creating a Samba domain member server if any of the following conditions
- prevail:
- </para>
-
- <itemizedlist>
- <listitem><para>
- LDAP support (client) is not installed on the system.
- </para></listitem>
-
- <listitem><para>
- There are mitigating circumstances forcing a decision not to use LDAP.
- </para></listitem>
-
- <listitem><para>
- The Samba domain member server must be part of a Windows NT4 Domain, or a Samba Domain.
- </para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>Windows ADS Domain</primary></indexterm>
- <indexterm><primary>Samba Domain</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- Later in the chapter, you can see how to configure a Samba domain member server for a Windows ADS domain.
- Right now your objective is to configure a Samba server that can be a member of a Windows NT4-style
- domain and/or does not use LDAP.
- </para>
-
- <note><para>
- <indexterm><primary>duplicate accounts</primary></indexterm>
- If you use <command>winbind</command> for identity resolution, make sure that there are no
- duplicate accounts.
- </para>
-
- <para>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- For example, do not have more than one account that has UID=0 in the password database. If there
- is an account called <constant>root</constant> in the <filename>/etc/passwd</filename> database,
- it is okay to have an account called <constant>root</constant> in the LDAP ldapsam or in the
- tdbsam. But if there are two accounts in the passdb backend that have the same UID, winbind will
- break. This means that the <constant>Administrator</constant> account must be called
- <constant>root</constant>.
- </para>
-
- <para>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- Winbind will break if there is an account in <filename>/etc/passwd</filename> that has
- the same UID as an account that is in LDAP ldapsam (or in tdbsam) but that differs in name only.
- </para></note>
-
- <para>
- <indexterm><primary>credentials</primary></indexterm>
- <indexterm><primary>traverse</primary></indexterm>
- <indexterm><primary>wide-area</primary></indexterm>
- <indexterm><primary>network</primary><secondary>wide-area</secondary></indexterm>
- <indexterm><primary>tdbdump</primary></indexterm>
- The following configuration uses CIFS/SMB protocols alone to obtain user and group credentials.
- The winbind information is locally cached in the <filename>winbindd_cache.tdb winbindd_idmap.tdb</filename>
- files. This provides considerable performance benefits compared with the LDAP solution, particularly
- where the LDAP lookups must traverse WAN links. You may examine the contents of these
- files using the tool <command>tdbdump</command>, though you may have to build this from the Samba
- source code if it has not been supplied as part of a binary package distribution that you may be using.
- </para>
-
- <procedure>
- <title>Configuration of Winbind-Based Identity Resolution</title>
-
- <step><para>
- Using your favorite text editor, create the &smb.conf; file so it has the contents
- shown in <link linkend="ch0-NT4DSDM"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- Edit the <filename>/etc/nsswitch.conf</filename> so it has the entries shown in
- <link linkend="ch9-sdmnss"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
- The system is ready to join the domain. Execute the following:
-<screen>
-net rpc join -U root%not2g4et
-Joined domain MEGANET2.
-</screen>
- This indicates that the domain join succeed.
-
- </para></step>
-
- <step><para>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>wbinfo</primary></indexterm>
- Validate operation of <command>winbind</command> using the <command>wbinfo</command>
- tool as follows:
-<screen>
-&rootprompt; wbinfo -u
-MEGANET2+root
-MEGANET2+nobody
-MEGANET2+jht
-MEGANET2+maryv
-MEGANET2+billr
-MEGANET2+jelliott
-MEGANET2+dbrady
-MEGANET2+joeg
-MEGANET2+balap
-</screen>
- This shows that domain users have been listed correctly.
-<screen>
-&rootprompt; wbinfo -g
-MEGANET2+Domain Admins
-MEGANET2+Domain Users
-MEGANET2+Domain Guests
-MEGANET2+Accounts
-MEGANET2+Finances
-MEGANET2+PIOps
-</screen>
- This shows that domain groups have been correctly obtained also.
- </para></step>
-
- <step><para>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>getent</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- The next step verifies that NSS is able to obtain this information
- correctly from <command>winbind</command> also.
-<screen>
-&rootprompt; getent passwd
-...
-MEGANET2+root:x:10000:10001:NetBIOS Domain Admin:
- /home/MEGANET2/root:/bin/bash
-MEGANET2+nobody:x:10001:10001:nobody:
- /home/MEGANET2/nobody:/bin/bash
-MEGANET2+jht:x:10002:10001:John H Terpstra:
- /home/MEGANET2/jht:/bin/bash
-MEGANET2+maryv:x:10003:10001:Mary Vortexis:
- /home/MEGANET2/maryv:/bin/bash
-MEGANET2+billr:x:10004:10001:William Randalph:
- /home/MEGANET2/billr:/bin/bash
-MEGANET2+jelliott:x:10005:10001:John G Elliott:
- /home/MEGANET2/jelliott:/bin/bash
-MEGANET2+dbrady:x:10006:10001:Darren Brady:
- /home/MEGANET2/dbrady:/bin/bash
-MEGANET2+joeg:x:10007:10001:Joe Green:
- /home/MEGANET2/joeg:/bin/bash
-MEGANET2+balap:x:10008:10001:Bala Pillay:
- /home/MEGANET2/balap:/bin/bash
-</screen>
- The user account information has been correctly obtained. This information has
- been merged with the winbind template information configured in the &smb.conf; file.
-<screen>
-&rootprompt;# getent group
-...
-MEGANET2+Domain Admins:x:10000:MEGANET2+root,MEGANET2+jht
-MEGANET2+Domain Users:x:10001:MEGANET2+jht,MEGANET2+maryv,\
- MEGANET2+billr,MEGANET2+jelliott,MEGANET2+dbrady,\
- MEGANET2+joeg,MEGANET2+balap
-MEGANET2+Domain Guests:x:10002:MEGANET2+nobody
-MEGANET2+Accounts:x:10003:
-MEGANET2+Finances:x:10004:
-MEGANET2+PIOps:x:10005:
-</screen>
- </para></step>
-
- <step><para>
- The Samba member server of a Windows NT4 domain is ready for use.
- </para></step>
-
- </procedure>
-
-<example id="ch0-NT4DSDM">
-<title>Samba Domain Member Server Using Winbind &smb.conf; File for NT4 Domain</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="unix charset">LOCALE</smbconfoption>
-<smbconfoption name="workgroup">MEGANET2</smbconfoption>
-<smbconfoption name="security">DOMAIN</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">0</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="wins server">192.168.2.1</smbconfoption>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfoption name="template primary group">"Domain Users"</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind separator">+</smbconfoption>
-<smbconfoption name="hosts allow">192.168.2., 192.168.3., 127.</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
-<smbconfoption name="admin users">root, Administrator</smbconfoption>
-<smbconfoption name="write list">root</smbconfoption>
-</smbconfblock>
-</example>
-
- </sect2>
-
- <sect2 id="dcwonss">
- <title>NT4/Samba Domain with Samba Domain Member Server without NSS Support</title>
-
- <para>
- No matter how many UNIX/Linux administrators there may be who believe that a UNIX operating
- system that does not have NSS and PAM support to be outdated, the fact is there
- are still many such systems in use today. Samba can be used without NSS support, but this
- does limit it to the use of local user and group accounts only.
- </para>
-
- <para>
- The following steps may be followed to implement Samba with support for local accounts.
- In this configuration Samba is made a domain member server. All incoming connections
- to the Samba server will cause the look-up of the incoming username. If the account
- is found, it is used. If the account is not found, one will be automatically created
- on the local machine so that it can then be used for all access controls.
- </para>
-
- <procedure>
- <title>Configuration Using Local Accounts Only</title>
-
- <step><para>
- Using your favorite text editor, create the &smb.conf; file so it has the contents
- shown in <link linkend="ch0-NT4DSCM"/>.
- </para></step>
-
- <step>
- <para><indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
- The system is ready to join the domain. Execute the following:
-<screen>
-net rpc join -U root%not24get
-Joined domain MEGANET2.
-</screen>
- This indicates that the domain join succeed.
- </para></step>
-
- <step><para>
- Be sure to run all three Samba daemons: <command>smbd</command>, <command>nmbd</command>, <command>winbindd</command>.
- </para></step>
-
- <step><para>
- The Samba member server of a Windows NT4 domain is ready for use.
- </para></step>
- </procedure>
-
-<example id="ch0-NT4DSCM">
-<title>Samba Domain Member Server Using Local Accounts &smb.conf; File for NT4 Domain</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="unix charset">LOCALE</smbconfoption>
-<smbconfoption name="workgroup">MEGANET3</smbconfoption>
-<smbconfoption name="netbios name">BSDBOX</smbconfoption>
-<smbconfoption name="security">DOMAIN</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
-<smbconfoption name="add machine script">/usr/sbin/useradd -M '%u'</smbconfoption>
-<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">0</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="wins server">192.168.2.1</smbconfoption>
-<smbconfoption name="hosts allow">192.168.2., 192.168.3., 127.</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
-<smbconfoption name="admin users">root, Administrator</smbconfoption>
-<smbconfoption name="write list">root</smbconfoption>
-</smbconfblock>
-</example>
- </sect2>
-
- <sect2 id="adssdm">
- <title>Active Directory Domain with Samba Domain Member Server</title>
-
- <para>
- <indexterm><primary>Active Directory</primary><secondary>join</secondary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- <indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
- One of the much-sought-after features new to Samba is the ability to join an Active Directory
- domain using Kerberos protocols. This makes it possible to operate an entire Windows network
- without the need to run NetBIOS over TCP/IP and permits more secure networking in general. An
- exhaustively complete discussion of the protocols is not possible in this book; perhaps a
- later book may explore the intricacies of the NetBIOS-less operation that Samba can participate
- in. For now, we simply focus on how a Samba server can be made a domain member server.
- </para>
-
- <para>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>Identity resolution</primary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- The diagram in <link linkend="ch9-adsdc"/> demonstrates how Samba interfaces with
- Microsoft Active Directory components. It should be noted that if Microsoft Windows Services
- for UNIX (SFU) has been installed and correctly configured, it is possible to use client LDAP
- for identity resolution just as can be done with Samba when using an LDAP passdb backend.
- The UNIX tool that you need for this, as in the case of LDAP on UNIX/Linux, is the PADL
- Software nss_ldap tool-set. Compared with use of winbind and Kerberos, the use of
- LDAP-based identity resolution is a little less secure. In view of the fact that this solution
- requires additional software to be installed on the Windows 200x ADS domain controllers,
- and that means more management overhead, it is likely that most Samba ADS client sites
- may elect to use winbind.
- </para>
-
- <para>
- Do not attempt to use this procedure if you are not 100 percent certain that the build of Samba
- you are using has been compiled and linked with all the tools necessary for this to work.
- Given the importance of this step, you must first validate that the Samba message block
- daemon (<command>smbd</command>) has the necessary features.
- </para>
-
- <para>
- The hypothetical domain you are using in this example assumes that the Abmas London office
- decided to take its own lead (some would say this is a typical behavior in a global
- corporate world; besides, a little divergence and conflict makes for an interesting life).
- The Windows Server 2003 ADS domain is called <constant>london.abmas.biz</constant> and the
- name of the server is <constant>W2K3S</constant>. In ADS realm terms, the domain controller
- is known as <constant>w2k3s.london.abmas.biz</constant>. In NetBIOS nomenclature, the
- domain name is <constant>LONDON</constant> and the server name is <constant>W2K3S</constant>.
- </para>
-
- <figure id="ch9-adsdc">
- <title>Active Directory Domain: Samba Member Server</title>
- <imagefile scale="60">chap9-ADSDC</imagefile>
- </figure>
-
- <procedure>
- <title>Joining a Samba Server as an ADS Domain Member</title>
-
- <step><para>
- <indexterm><primary>smbd</primary></indexterm>
- Before you try to use Samba, you want to know for certain that your executables have
- support for Kerberos and for LDAP. Execute the following to identify whether or
- not this build is perhaps suitable for use:
-<screen>
-&rootprompt; cd /usr/sbin
-&rootprompt; smbd -b | grep KRB
- HAVE_KRB5_H
- HAVE_ADDR_TYPE_IN_KRB5_ADDRESS
- HAVE_KRB5
- HAVE_KRB5_AUTH_CON_SETKEY
- HAVE_KRB5_GET_DEFAULT_IN_TKT_ETYPES
- HAVE_KRB5_GET_PW_SALT
- HAVE_KRB5_KEYBLOCK_KEYVALUE
- HAVE_KRB5_KEYTAB_ENTRY_KEYBLOCK
- HAVE_KRB5_MK_REQ_EXTENDED
- HAVE_KRB5_PRINCIPAL_GET_COMP_STRING
- HAVE_KRB5_SET_DEFAULT_IN_TKT_ETYPES
- HAVE_KRB5_STRING_TO_KEY
- HAVE_KRB5_STRING_TO_KEY_SALT
- HAVE_LIBKRB5
-</screen>
- This output was obtained on a SUSE Linux system and shows the output for
- Samba that has been compiled and linked with the Heimdal Kerberos libraries.
- The following is a typical output that will be found on a Red Hat Linux system that
- has been linked with the MIT Kerberos libraries:
-<screen>
-&rootprompt; cd /usr/sbin
-&rootprompt; smbd -b | grep KRB
- HAVE_KRB5_H
- HAVE_ADDRTYPE_IN_KRB5_ADDRESS
- HAVE_KRB5
- HAVE_KRB5_AUTH_CON_SETUSERUSERKEY
- HAVE_KRB5_ENCRYPT_DATA
- HAVE_KRB5_FREE_DATA_CONTENTS
- HAVE_KRB5_FREE_KTYPES
- HAVE_KRB5_GET_PERMITTED_ENCTYPES
- HAVE_KRB5_KEYTAB_ENTRY_KEY
- HAVE_KRB5_LOCATE_KDC
- HAVE_KRB5_MK_REQ_EXTENDED
- HAVE_KRB5_PRINCIPAL2SALT
- HAVE_KRB5_PRINC_COMPONENT
- HAVE_KRB5_SET_DEFAULT_TGS_KTYPES
- HAVE_KRB5_SET_REAL_TIME
- HAVE_KRB5_STRING_TO_KEY
- HAVE_KRB5_TKT_ENC_PART2
- HAVE_KRB5_USE_ENCTYPE
- HAVE_LIBGSSAPI_KRB5
- HAVE_LIBKRB5
-</screen>
- You can validate that Samba has been compiled and linked with LDAP support
- by executing:
-<screen>
-&rootprompt; smbd -b | grep LDAP
-massive:/usr/sbin # smbd -b | grep LDAP
- HAVE_LDAP_H
- HAVE_LDAP
- HAVE_LDAP_DOMAIN2HOSTLIST
- HAVE_LDAP_INIT
- HAVE_LDAP_INITIALIZE
- HAVE_LDAP_SET_REBIND_PROC
- HAVE_LIBLDAP
- LDAP_SET_REBIND_PROC_ARGS
-</screen>
- This does look promising; <command>smbd</command> has been built with Kerberos and LDAP
- support. You are relieved to know that it is safe to progress.
- </para></step>
-
- <step><para>
- <indexterm><primary>Kerberos</primary><secondary>libraries</secondary></indexterm>
- <indexterm><primary>MIT Kerberos</primary></indexterm>
- <indexterm><primary>Heimdal Kerberos</primary></indexterm>
- <indexterm><primary>Kerberos</primary><secondary>MIT</secondary></indexterm>
- <indexterm><primary>Kerberos</primary><secondary>Heimdal</secondary></indexterm>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- <indexterm><primary>SUSE Linux</primary></indexterm>
- <indexterm><primary>SerNet</primary></indexterm>
- <indexterm><primary>validated</primary></indexterm>
- The next step is to identify which version of the Kerberos libraries have been used.
- In order to permit Samba to interoperate with Windows 2003 Active Directory, it is
- essential that it has been linked with either MIT Kerberos version 1.3.1 or later,
- or that it has been linked with Heimdal Kerberos 0.6 plus specific patches. You may
- identify what version of the MIT Kerberos libraries are installed on your system by
- executing (on Red Hat Linux):
-<screen>
-&rootprompt; rpm -q krb5
-</screen>
- Or on SUSE Linux, execute:
-<screen>
-&rootprompt; rpm -q heimdal
-</screen>
- Please note that the RPMs provided by the Samba-Team are known to be working and have
- been validated. Red Hat Linux RPMs may be obtained from the Samba FTP sites. SUSE
- Linux RPMs may be obtained from <ulink url="ftp://ftp.sernet.de">Sernet</ulink> in
- Germany.
- </para>
-
- <para>
- From this point on, you are certain that the Samba build you are using has the
- necessary capabilities. You can now configure Samba and the NSS.
- </para></step>
-
- <step><para>
- Using you favorite editor, configure the &smb.conf; file that is located in the
- <filename>/etc/samba</filename> directory so that it has the contents shown
- in <link linkend="ch9-adssdm"/>.
- </para></step>
-
- <step><para>
- Edit or create the NSS control file so it has the contents shown in <link linkend="ch9-sdmnss"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/samba/secrets.tdb</primary></indexterm>
- Delete the file <filename>/etc/samba/secrets.tdb</filename> if it exists. Of course, you
- do keep a backup, don't you?
- </para></step>
-
- <step><para>
- Delete the tdb files that cache Samba information. You keep a backup of the old
- files, of course. You also remove all files to ensure that nothing can pollute your
- nice, new configuration. Execute the following (example is for SUSE Linux):
-<screen>
-&rootprompt; rm /var/lib/samba/*tdb
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>testparm</primary></indexterm>
- Validate your &smb.conf; file using <command>testparm</command> (as you have
- done previously). Correct all errors reported before proceeding. The command you
- execute is:
-<screen>
-&rootprompt; testparm -s | less
-</screen>
- Now that you are satisfied that your Samba server is ready to join the Windows
- ADS domain, let's move on.
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- This is a good time to double-check everything and then execute the following
- command when everything you have done has checked out okay:
-<screen>
-&rootprompt; net ads join -UAdministrator%not24get
-Using short domain name -- LONDON
-Joined 'FRAN' to realm 'LONDON.ABMAS.BIZ'
-</screen>
- You have successfully made your Samba server a member of the ADS domain
- using Kerberos protocols.
- </para>
-
- <para>
- <indexterm><primary>silent return</primary></indexterm>
- <indexterm><primary>failed join</primary></indexterm>
- In the event that you receive no output messages, a silent return means that the
- domain join failed. You should use <command>ethereal</command> to identify what
- may be failing. Common causes of a failed join include:
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>name resolution</primary><secondary>Defective</secondary></indexterm>
- Defective or misconfigured DNS name resolution.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Restrictive security</primary></indexterm>
- Restrictive security settings on the Windows 200x ADS domain controller
- preventing needed communications protocols. You can check this by searching
- the Windows Server 200x Event Viewer.
- </para></listitem>
-
- <listitem><para>
- Incorrectly configured &smb.conf; file settings.
- </para></listitem>
-
- <listitem><para>
- Lack of support of necessary Kerberos protocols because the version of MIT
- Kerberos (or Heimdal) in use is not up to date enough to support the necessary
- functionality.
- </para></listitem>
- </itemizedlist>
-
- <indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
- <indexterm><primary>RPC</primary></indexterm>
- <indexterm><primary>mixed mode</primary></indexterm>
- In any case, never execute the <command>net rpc join</command> command in an attempt
- to join the Samba server to the domain, unless you wish not to use the Kerberos
- security protocols. Use of the older RPC-based domain join facility requires that
- Windows Server 200x ADS has been configured appropriately for mixed mode operation.
- </para></step>
-
- <step><para>
- <indexterm><primary>tdbdump</primary></indexterm>
- <indexterm><primary>/etc/samba/secrets.tdb</primary></indexterm>
- If the <command>tdbdump</command> is installed on your system (not essential),
- you can look inside the <filename>/etc/samba/secrets.tdb</filename> file. If
- you wish to do this, execute:
-<screen>
-&rootprompt; tdbdump secrets.tdb
-{
-key = "SECRETS/SID/LONDON"
-data = "\01\04\00\00\00\00\00\05\15\00\00\00\EBw\86\F1\ED\BD\
- F6{\5C6\E5W\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
- 00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
- 00\00\00\00\00\00\00\00"
-}
-{
-key = "SECRETS/MACHINE_PASSWORD/LONDON"
-data = "le3Q5FPnN5.ueC\00"
-}
-{
-key = "SECRETS/MACHINE_SEC_CHANNEL_TYPE/LONDON"
-data = "\02\00\00\00"
-}
-{
-key = "SECRETS/MACHINE_LAST_CHANGE_TIME/LONDON"
-data = "E\89\F6?"
-}
-</screen>
- This is given to demonstrate to the skeptics that this process truly does work.
- </para></step>
-
- <step><para>
- It is now time to start Samba in the usual way (as has been done many time before
- in this book).
- </para></step>
-
- <step><para>
- <indexterm><primary>wbinfo</primary></indexterm>
- This is a good time to verify that everything is working. First, check that
- winbind is able to obtain the list of users and groups from the ADS domain controller.
- Execute the following:
-<screen>
-&rootprompt; wbinfo -u
-LONDON+Administrator
-LONDON+Guest
-LONDON+SUPPORT_388945a0
-LONDON+krbtgt
-LONDON+jht
-</screen>
- Good, the list of users was obtained. Now do likewise for group accounts:
-<screen>
-&rootprompt; wbinfo -g
-LONDON+Domain Computers
-LONDON+Domain Controllers
-LONDON+Schema Admins
-LONDON+Enterprise Admins
-LONDON+Domain Admins
-LONDON+Domain Users
-LONDON+Domain Guests
-LONDON+Group Policy Creator Owners
-LONDON+DnsUpdateProxy
-</screen>
- Excellent. That worked also, as expected.
- </para></step>
-
- <step><para><indexterm>
- <primary>getent</primary>
- </indexterm>
- Now repeat this via NSS to validate that full identity resolution is
- functional as required. Execute:
-<screen>
-&rootprompt; getent passwd
-...
-LONDON+Administrator:x:10000:10000:Administrator:
- /home/LONDON/administrator:/bin/bash
-LONDON+Guest:x:10001:10001:Guest:
- /home/LONDON/guest:/bin/bash
-LONDON+SUPPORT_388945a0:x:10002:10000:SUPPORT_388945a0:
- /home/LONDON/support_388945a0:/bin/bash
-LONDON+krbtgt:x:10003:10000:krbtgt:
- /home/LONDON/krbtgt:/bin/bash
-LONDON+jht:x:10004:10000:John H. Terpstra:
- /home/LONDON/jht:/bin/bash
-</screen>
- Okay, ADS user accounts are being resolved. Now you try group resolution:
-<screen>
-&rootprompt; getent group
-...
-LONDON+Domain Computers:x:10002:
-LONDON+Domain Controllers:x:10003:
-LONDON+Schema Admins:x:10004:LONDON+Administrator
-LONDON+Enterprise Admins:x:10005:LONDON+Administrator
-LONDON+Domain Admins:x:10006:LONDON+jht,LONDON+Administrator
-LONDON+Domain Users:x:10000:
-LONDON+Domain Guests:x:10001:
-LONDON+Group Policy Creator Owners:x:10007:LONDON+Administrator
-LONDON+DnsUpdateProxy:x:10008:
-</screen>
- This is very pleasing. Everything works as expected.
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>ads</secondary><tertiary>info</tertiary></indexterm>
- <indexterm><primary>Active Directory</primary><secondary>server</secondary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- You may now perform final verification that communications between Samba winbind and
- the Active Directory server is using Kerberos protocols. Execute the following:
-<screen>
-&rootprompt; net ads info
-LDAP server: 192.168.2.123
-LDAP server name: w2k3s
-Realm: LONDON.ABMAS.BIZ
-Bind Path: dc=LONDON,dc=ABMAS,dc=BIZ
-LDAP port: 389
-Server time: Sat, 03 Jan 2004 02:44:44 GMT
-KDC server: 192.168.2.123
-Server time offset: 2
-</screen>
- It should be noted that Kerberos protocols are time-clock critical. You should
- keep all server time clocks synchronized using the network time protocol (NTP).
- In any case, the output we obtained confirms that all systems are operational.
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>ads</secondary><tertiary>status</tertiary></indexterm>
- There is one more action you elect to take, just because you are paranoid and disbelieving,
- so you execute the following command:
-<programlisting>
-&rootprompt; net ads status -UAdministrator%not24get
-objectClass: top
-objectClass: person
-objectClass: organizationalPerson
-objectClass: user
-objectClass: computer
-cn: fran
-distinguishedName: CN=fran,CN=Computers,DC=london,DC=abmas,DC=biz
-instanceType: 4
-whenCreated: 20040103092006.0Z
-whenChanged: 20040103092006.0Z
-uSNCreated: 28713
-uSNChanged: 28717
-name: fran
-objectGUID: 58f89519-c467-49b9-acb0-f099d73696e
-userAccountControl: 69632
-badPwdCount: 0
-codePage: 0
-countryCode: 0
-badPasswordTime: 0
-lastLogoff: 0
-lastLogon: 127175965783327936
-localPolicyFlags: 0
-pwdLastSet: 127175952062598496
-primaryGroupID: 515
-objectSid: S-1-5-21-4052121579-2079768045-1474639452-1109
-accountExpires: 9223372036854775807
-logonCount: 13
-sAMAccountName: fran$
-sAMAccountType: 805306369
-operatingSystem: Samba
-operatingSystemVersion: 3.0.20-SUSE
-dNSHostName: fran
-userPrincipalName: HOST/fran@LONDON.ABMAS.BIZ
-servicePrincipalName: CIFS/fran.london.abmas.biz
-servicePrincipalName: CIFS/fran
-servicePrincipalName: HOST/fran.london.abmas.biz
-servicePrincipalName: HOST/fran
-objectCategory: CN=Computer,CN=Schema,CN=Configuration,
- DC=london,DC=abmas,DC=biz
-isCriticalSystemObject: FALSE
--------------- Security Descriptor (revision: 1, type: 0x8c14)
-owner SID: S-1-5-21-4052121579-2079768045-1474639452-512
-group SID: S-1-5-21-4052121579-2079768045-1474639452-513
-------- (system) ACL (revision: 4, size: 120, number of ACEs: 2)
-------- ACE (type: 0x07, flags: 0x5a, size: 0x38,
- mask: 0x20, object flags: 0x3)
-access SID: S-1-1-0
-access type: AUDIT OBJECT
-Permissions:
- [Write All Properties]
-------- ACE (type: 0x07, flags: 0x5a, size: 0x38,
- mask: 0x20, object flags: 0x3)
-access SID: S-1-1-0
-access type: AUDIT OBJECT
-Permissions:
- [Write All Properties]
-------- (user) ACL (revision: 4, size: 1944, number of ACEs: 40)
-------- ACE (type: 0x00, flags: 0x00, size: 0x24, mask: 0xf01ff)
-access SID: S-1-5-21-4052121579-2079768045-1474639452-512
-access type: ALLOWED
-Permissions: [Full Control]
-------- ACE (type: 0x00, flags: 0x00, size: 0x18, mask: 0xf01ff)
-access SID: S-1-5-32-548
-...
-------- ACE (type: 0x05, flags: 0x12, size: 0x38,
- mask: 0x10, object flags: 0x3)
-access SID: S-1-5-9
-access type: ALLOWED OBJECT
-Permissions:
- [Read All Properties]
--------------- End Of Security Descriptor
-</programlisting>
- And now you have conclusive proof that your Samba ADS domain member server
- called <constant>FRAN</constant> is able to communicate fully with the ADS
- domain controllers.
- </para></step>
-
- </procedure>
-
-
- <para>
- Your Samba ADS domain member server is ready for use. During training sessions,
- you may be asked what is inside the <filename>winbindd_cache.tdb and winbindd_idmap.tdb</filename>
- files. Since curiosity just took hold of you, execute the following:
-<programlisting>
-&rootprompt; tdbdump /var/lib/samba/winbindd_idmap.tdb
-{
-key = "S-1-5-21-4052121579-2079768045-1474639452-501\00"
-data = "UID 10001\00"
-}
-{
-key = "UID 10005\00"
-data = "S-1-5-21-4052121579-2079768045-1474639452-1111\00"
-}
-{
-key = "GID 10004\00"
-data = "S-1-5-21-4052121579-2079768045-1474639452-518\00"
-}
-{
-key = "S-1-5-21-4052121579-2079768045-1474639452-502\00"
-data = "UID 10003\00"
-}
-...
-
-&rootprompt; tdbdump /var/lib/samba/winbindd_cache.tdb
-{
-key = "UL/LONDON"
-data = "\00\00\00\00bp\00\00\06\00\00\00\0DAdministrator\0D
- Administrator-S-1-5-21-4052121579-2079768045-1474639452-500-
- S-1-5-21-4052121579-2079768045-1474639452-513\05Guest\05
- Guest-S-1-5-21-4052121579-2079768045-1474639452-501-
- S-1-5-21-4052121579-2079768045-1474639452-514\10
- SUPPORT_388945a0\10SUPPORT_388945a0.
- S-1-5-21-4052121579-2079768045-1474639452-1001-
- S-1-5-21-4052121579-2079768045-1474639452-513\06krbtgt\06
- krbtgt-S-1-5-21-4052121579-2079768045-1474639452-502-
- S-1-5-21-4052121579-2079768045-1474639452-513\03jht\10
- John H. Terpstra.S-1-5-21-4052121579-2079768045-1474639452-1110-
- S-1-5-21-4052121579-2079768045-1474639452-513"
-}
-{
-key = "GM/S-1-5-21-4052121579-2079768045-1474639452-512"
-data = "\00\00\00\00bp\00\00\02\00\00\00.
- S-1-5-21-4052121579-2079768045-1474639452-1110\03
- jht\01\00\00\00-S-1-5-21-4052121579-2079768045-1474639452-500\0D
- Administrator\01\00\00\00"
-}
-{
-key = "SN/S-1-5-21-4052121579-2079768045-1474639452-513"
-data = "\00\00\00\00xp\00\00\02\00\00\00\0CDomain Users"
-}
-{
-key = "GM/S-1-5-21-4052121579-2079768045-1474639452-518"
-data = "\00\00\00\00bp\00\00\01\00\00\00-
- S-1-5-21-4052121579-2079768045-1474639452-500\0D
- Administrator\01\00\00\00"
-}
-{
-key = "SEQNUM/LONDON\00"
-data = "xp\00\00C\92\F6?"
-}
-{
-key = "U/S-1-5-21-4052121579-2079768045-1474639452-1110"
-data = "\00\00\00\00xp\00\00\03jht\10John H. Terpstra.
- S-1-5-21-4052121579-2079768045-1474639452-1110-
- S-1-5-21-4052121579-2079768045-1474639452-513"
-}
-{
-key = "NS/S-1-5-21-4052121579-2079768045-1474639452-502"
-data = "\00\00\00\00bp\00\00-
- S-1-5-21-4052121579-2079768045-1474639452-502"
-}
-{
-key = "SN/S-1-5-21-4052121579-2079768045-1474639452-1001"
-data = "\00\00\00\00bp\00\00\01\00\00\00\10SUPPORT_388945a0"
-}
-{
-key = "SN/S-1-5-21-4052121579-2079768045-1474639452-500"
-data = "\00\00\00\00bp\00\00\01\00\00\00\0DAdministrator"
-}
-{
-key = "U/S-1-5-21-4052121579-2079768045-1474639452-502"
-data = "\00\00\00\00bp\00\00\06krbtgt\06krbtgt-
- S-1-5-21-4052121579-2079768045-1474639452-502-
- S-1-5-21-4052121579-2079768045-1474639452-513"
-}
-....
-</programlisting>
- Now all is revealed. Your curiosity, as well as that of your team, has been put at ease.
- May this server serve well all who happen upon it.
- </para>
-
-<example id="ch9-adssdm">
-<title>Samba Domain Member &smb.conf; File for Active Directory Membership</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="unix charset">LOCALE</smbconfoption>
-<smbconfoption name="workgroup">LONDON</smbconfoption>
-<smbconfoption name="realm">LONDON.ABMAS.BIZ</smbconfoption>
-<smbconfoption name="server string">Samba 3.0.20</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">50</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="ldap ssl">no</smbconfoption>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfoption name="template primary group">"Domain Users"</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind separator">+</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
-<smbconfoption name="admin users">root, Administrator</smbconfoption>
-<smbconfoption name="write list">root</smbconfoption>
-</smbconfblock>
-</example>
-
- <sect3>
- <title>IDMAP_RID with Winbind</title>
-
- <para>
- <indexterm><primary>idmap_rid</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>RID</primary></indexterm>
- <indexterm><primary>IDMAP</primary></indexterm>
- The <command>idmap_rid</command> facility is a new tool that, unlike native winbind, creates a
- predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method
- of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data
- in a central place. The downside is that it can be used only within a single ADS domain and
- is not compatible with trusted domain implementations.
- </para>
-
- <para>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>allow trusted domains</primary></indexterm>
- <indexterm><primary>idmap uid</primary></indexterm>
- <indexterm><primary>idmap gid</primary></indexterm>
- This alternate method of SID to UID/GID mapping can be achieved with the idmap_rid
- plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the
- RID to a base value specified. This utility requires that the parameter
- <quote>allow trusted domains = No</quote> must be specified, as it is not compatible
- with multiple domain environments. The <parameter>idmap uid</parameter> and
- <parameter>idmap gid</parameter> ranges must be specified.
- </para>
-
- <para>
- <indexterm><primary>idmap_rid</primary></indexterm>
- <indexterm><primary>realm</primary></indexterm>
- The idmap_rid facility can be used both for NT4/Samba-style domains as well as with Active Directory.
- To use this with an NT4 domain, the <parameter>realm</parameter> is not used. Additionally the
- method used to join the domain uses the <constant>net rpc join</constant> process.
- </para>
-
- <para>
- An example &smb.conf; file for an ADS domain environment is shown in <link linkend="sbe-idmapridex"/>.
- </para>
-
-<example id="sbe-idmapridex">
-<title>Example &smb.conf; File Using <constant>idmap_rid</constant></title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">KPAK</smbconfoption>
-<smbconfoption name="netbios name">BIGJOE</smbconfoption>
-<smbconfoption name="realm">CORP.KPAK.COM</smbconfoption>
-<smbconfoption name="server string">Office Server</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="allow trusted domains">No</smbconfoption>
-<smbconfoption name="idmap backend">idmap_rid:KPAK=500-100000000</smbconfoption>
-<smbconfoption name="idmap uid">500-100000000</smbconfoption>
-<smbconfoption name="idmap gid">500-100000000</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-<smbconfoption name="winbind enum users">No</smbconfoption>
-<smbconfoption name="winbind enum groups">No</smbconfoption>
-<smbconfoption name="winbind nested groups">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>large domain</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>response</primary></indexterm>
- <indexterm><primary>getent</primary></indexterm>
- In a large domain with many users, it is imperative to disable enumeration of users and groups.
- For example, at a site that has 22,000 users in Active Directory the winbind-based user and
- group resolution is unavailable for nearly 12 minutes following first start-up of
- <command>winbind</command>. Disabling of such enumeration results in instantaneous response.
- The disabling of user and group enumeration means that it will not be possible to list users
- or groups using the <command>getent passwd</command> and <command>getent group</command>
- commands. It will be possible to perform the lookup for individual users, as shown in the procedure
- below.
- </para>
-
- <para>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The use of this tool requires configuration of NSS as per the native use of winbind. Edit the
- <filename>/etc/nsswitch.conf</filename> so it has the following parameters:
-<screen>
-...
-passwd: files winbind
-shadow: files winbind
-group: files winbind
-...
-hosts: files wins
-...
-</screen>
- </para>
-
- <para>
- The following procedure can be used to utilize the idmap_rid facility:
- </para>
-
- <procedure>
- <step><para>
- Create or install and &smb.conf; file with the above configuration.
- </para></step>
-
- <step><para>
- Edit the <filename>/etc/nsswitch.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Execute:
-<screen>
-&rootprompt; net ads join -UAdministrator%password
-Using short domain name -- KPAK
-Joined 'BIGJOE' to realm 'CORP.KPAK.COM'
-</screen>
- </para>
-
- <para>
- <indexterm><primary>failed join</primary></indexterm>
- An invalid or failed join can be detected by executing:
-<screen>
-&rootprompt; net ads testjoin
-BIGJOE$@'s password:
-[2004/11/05 16:53:03, 0] utils/net_ads.c:ads_startup(186)
- ads_connect: No results returned
-Join to domain is not valid
-</screen>
- The specific error message may differ from the above because it depends on the type of failure that
- may have occurred. Increase the <parameter>log level</parameter> to 10, repeat the above test,
- and then examine the log files produced to identify the nature of the failure.
- </para></step>
-
- <step><para>
- Start the <command>nmbd</command>, <command>winbind,</command> and <command>smbd</command> daemons in the order shown.
- </para></step>
-
- <step><para>
- Validate the operation of this configuration by executing:
- <indexterm><primary></primary></indexterm>
-<screen>
-&rootprompt; getent passwd administrator
-administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
-</screen>
- </para></step>
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>IDMAP Storage in LDAP using Winbind</title>
-
- <para>
- <indexterm><primary>ADAM</primary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- The storage of IDMAP information in LDAP can be used with both NT4/Samba-style domains as well as
- with ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any standards-compliant
- LDAP server can be used. It is therefore possible to deploy this IDMAP configuration using
- the Sun iPlanet LDAP server, Novell eDirectory, Microsoft ADS plus ADAM, and so on.
- </para>
-
- <para>
- The example in <link linkend="sbeunxa"/> is for an ADS-style domain.
- </para>
-
-<example id="sbeunxa">
-<title>Typical ADS Style Domain &smb.conf; File</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">SNOWSHOW</smbconfoption>
-<smbconfoption name="netbios name">GOODELF</smbconfoption>
-<smbconfoption name="realm">SNOWSHOW.COM</smbconfoption>
-<smbconfoption name="server string">Samba Server</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="log level">1 ads:10 auth:10 sam:10 rpc:10</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager,dc=SNOWSHOW,dc=COM</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-<smbconfoption name="ldap suffix">dc=SNOWSHOW,dc=COM</smbconfoption>
-<smbconfoption name="idmap backend">ldap:ldap://ldap.snowshow.com</smbconfoption>
-<smbconfoption name="idmap uid">150000-550000</smbconfoption>
-<smbconfoption name="idmap gid">150000-550000</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>realm</primary></indexterm>
- In the case of an NT4 or Samba-style domain the <parameter>realm</parameter> is not used, and the
- command used to join the domain is <command>net rpc join</command>. The above example also demonstrates
- advanced error reporting techniques that are documented in the chapter called "Reporting Bugs" in
- <quote>The Official Samba HOWTO and Reference Guide, Second Edition</quote> (TOSHARG2).
- </para>
-
- <para>
- <indexterm><primary>MIT kerberos</primary></indexterm>
- <indexterm><primary>Heimdal kerberos</primary></indexterm>
- <indexterm><primary>/etc/krb5.conf</primary></indexterm>
- Where MIT kerberos is installed (version 1.3.4 or later), edit the <filename>/etc/krb5.conf</filename>
- file so it has the following contents:
-<screen>
-[logging]
- default = FILE:/var/log/krb5libs.log
- kdc = FILE:/var/log/krb5kdc.log
- admin_server = FILE:/var/log/kadmind.log
-
-[libdefaults]
- default_realm = SNOWSHOW.COM
- dns_lookup_realm = false
- dns_lookup_kdc = true
-
-[appdefaults]
- pam = {
- debug = false
- ticket_lifetime = 36000
- renew_lifetime = 36000
- forwardable = true
- krb4_convert = false
- }
-</screen>
- </para>
-
- <para>
- Where Heimdal kerberos is installed, edit the <filename>/etc/krb5.conf</filename>
- file so it is either empty (i.e., no contents) or it has the following contents:
-<screen>
-[libdefaults]
- default_realm = SNOWSHOW.COM
- clockskew = 300
-
-[realms]
- SNOWSHOW.COM = {
- kdc = ADSDC.SHOWSHOW.COM
- }
-
-[domain_realm]
- .snowshow.com = SNOWSHOW.COM
-</screen>
- </para>
-
- <note><para>
- Samba cannot use the Heimdal libraries if there is no <filename>/etc/krb5.conf</filename> file.
- So long as there is an empty file, the Heimdal kerberos libraries will be usable. There is no
- need to specify any settings because Samba, using the Heimdal libraries, can figure this out automatically.
- </para></note>
- <para>
- Edit the NSS control file <filename>/etc/nsswitch.conf</filename> so it has the following entries:
-<screen>
-...
-passwd: files ldap
-shadow: files ldap
-group: files ldap
-...
-hosts: files wins
-...
-</screen>
- </para>
-
- <para>
- <indexterm><primary>PADL</primary></indexterm>
- <indexterm><primary>/etc/ldap.conf</primary></indexterm>
- You will need the <ulink url="http://www.padl.com">PADL</ulink> <command>nss_ldap</command>
- tool set for this solution. Configure the <filename>/etc/ldap.conf</filename> file so it has
- the information needed. The following is an example of a working file:
-<screen>
-host 192.168.2.1
-base dc=snowshow,dc=com
-binddn cn=Manager,dc=snowshow,dc=com
-bindpw not24get
-
-pam_password exop
-
-nss_base_passwd ou=People,dc=snowshow,dc=com?one
-nss_base_shadow ou=People,dc=snowshow,dc=com?one
-nss_base_group ou=Groups,dc=snowshow,dc=com?one
-ssl no
-</screen>
- </para>
-
- <para>
- The following procedure may be followed to affect a working configuration:
- </para>
- <procedure>
- <step><para>
- Configure the &smb.conf; file as shown above.
- </para></step>
-
- <step><para>
- Create the <filename>/etc/krb5.conf</filename> file following the indications above.
- </para></step>
-
- <step><para>
- Configure the <filename>/etc/nsswitch.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Download, build, and install the PADL nss_ldap tool set. Configure the
- <filename>/etc/ldap.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Configure an LDAP server and initialize the directory with the top-level entries needed by IDMAP
- as shown in the following LDIF file:
-<screen>
-dn: dc=snowshow,dc=com
-objectClass: dcObject
-objectClass: organization
-dc: snowshow
-o: The Greatest Snow Show in Singapore.
-description: Posix and Samba LDAP Identity Database
-
-dn: cn=Manager,dc=snowshow,dc=com
-objectClass: organizationalRole
-cn: Manager
-description: Directory Manager
-
-dn: ou=Idmap,dc=snowshow,dc=com
-objectClass: organizationalUnit
-ou: idmap
-</screen>
- </para></step>
-
- <step><para>
- Execute the command to join the Samba domain member server to the ADS domain as shown here:
-<screen>
-&rootprompt; net ads testjoin
-Using short domain name -- SNOWSHOW
-Joined 'GOODELF' to realm 'SNOWSHOW.COM'
-</screen>
- </para></step>
-
- <step><para>
- Store the LDAP server access password in the Samba <filename>secrets.tdb</filename> file as follows:
-<screen>
-&rootprompt; smbpasswd -w not24get
-</screen>
- </para></step>
-
- <step><para>
- Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
- </para></step>
- </procedure>
-
-
- <para>
- <indexterm><primary>diagnostic</primary></indexterm>
- Follow the diagnostic procedures shown earlier in this chapter to identify success or failure of the join.
- In many cases a failure is indicated by a silent return to the command prompt with no indication of the
- reason for failure.
- </para>
-
- </sect3>
-
- <sect3>
- <title>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</title>
-
- <para>
- <indexterm><primary>rfc2307bis</primary></indexterm>
- <indexterm><primary>schema</primary></indexterm>
- The use of this method is messy. The information provided in this section is for guidance only
- and is very definitely not complete. This method does work; it is used in a number of large sites
- and has an acceptable level of performance.
- </para>
-
- <para>
- An example &smb.conf; file is shown in <link linkend="sbewinbindex"/>.
- </para>
-
-<example id="sbewinbindex">
-<title>ADS Membership Using RFC2307bis Identity Resolution &smb.conf; File</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">BUBBAH</smbconfoption>
-<smbconfoption name="netbios name">MADMAX</smbconfoption>
-<smbconfoption name="realm">BUBBAH.COM</smbconfoption>
-<smbconfoption name="server string">Samba Server</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="idmap uid">150000-550000</smbconfoption>
-<smbconfoption name="idmap gid">150000-550000</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
-<smbconfoption name="winbind nested groups">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary
- to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the
- following:
-<screen>
-./configure --enable-rfc2307bis --enable-schema-mapping
-make install
-</screen>
- </para>
-
- <para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The following <filename>/etc/nsswitch.conf</filename> file contents are required:
-<screen>
-...
-passwd: files ldap
-shadow: files ldap
-group: files ldap
-...
-hosts: files wins
-...
-</screen>
- </para>
-
- <para>
- <indexterm><primary>/etc/ldap.conf</primary></indexterm>
- <indexterm><primary>nss_ldap</primary></indexterm>
- The <filename>/etc/ldap.conf</filename> file must be configured also. Refer to the PADL documentation
- and source code for nss_ldap instructions.
- </para>
-
- <para>
- The next step involves preparation on the ADS schema. This is briefly discussed in the remaining
- part of this chapter.
- </para>
-
- <sect4>
- <title>IDMAP, Active Directory, and MS Services for UNIX 3.5</title>
-
- <para>
- <indexterm><primary>SFU</primary></indexterm>
- The Microsoft Windows Service for UNIX version 3.5 is available for free
- <ulink url="http://www.microsoft.com/windows/sfu/">download</ulink>
- from the Microsoft Web site. You will need to download this tool and install it following
- Microsoft instructions.
- </para>
-
- </sect4>
-
- <sect4>
- <title>IDMAP, Active Directory, and AD4UNIX</title>
-
- <para>
- Instructions for obtaining and installing the AD4UNIX tool set can be found from the
- <ulink url="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?LDAP01/An_Alternative_Approach">
- Geekcomix</ulink> Web site.
- </para>
-
- </sect4>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>UNIX/Linux Client Domain Member</title>
-
- <para><indexterm>
- <primary>user credentials</primary>
- </indexterm>
- So far this chapter has been mainly concerned with the provision of file and print
- services for domain member servers. However, an increasing number of UNIX/Linux
- workstations are being installed that do not act as file or print servers to anyone
- other than a single desktop user. The key demand for desktop systems is to be able
- to log onto any UNIX/Linux or Windows desktop using the same network user credentials.
- </para>
-
- <para><indexterm>
- <primary>Single Sign-On</primary>
- <see>SSO</see>
- </indexterm>
- The ability to use a common set of user credential across a variety of network systems
- is generally regarded as a single sign-on (SSO) solution. SSO systems are sold by a
- large number of vendors and include a range of technologies such as:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Proxy sign-on
- </para></listitem>
-
- <listitem><para>
- Federated directory provisioning
- </para></listitem>
-
- <listitem><para>
- Metadirectory server solutions
- </para></listitem>
-
- <listitem><para>
- Replacement authentication systems
- </para></listitem>
- </itemizedlist>
-
- <para><indexterm>
- <primary>Identity management</primary>
- </indexterm>
- There are really four solutions that provide integrated authentication and
- user identity management facilities:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Samba winbind (free). Samba-3.0.20 introduced a complete replacement for Winbind that now
- provides a greater level of scalability in large ADS environments.
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.padl.com">PADL</ulink> PAM and LDAP tools (free).
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.vintela.com">Vintela</ulink> Authentication Services (commercial).
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.centrify.com">Centrify</ulink> DirectControl (commercial).
- Centrify's commercial product allows UNIX and Linux systems to use Active Directory
- security, directory and policy services. Enhancements include a centralized ID mapping that
- allows Samba, DirectControl and Active Directory to seamlessly work together.
- </para></listitem>
- </itemizedlist>
-
- <para>
- The following guidelines are pertinent to the deployment of winbind-based authentication
- and identity resolution with the express purpose of allowing users to log on to UNIX/Linux desktops
- using Windows network domain user credentials (username and password).
- </para>
-
- <para>
- You should note that it is possible to use LDAP-based PAM and NSS tools to permit distributed
- systems logons (SSO), providing user and group accounts are stored in an LDAP directory. This
- provides logon services for UNIX/Linux users, while Windows users obtain their sign-on
- support via Samba.
- </para>
-
- <para>
- <indexterm><primary>Windows Services for UNIX</primary><see>SUS</see></indexterm>
- On the other hand, if the authentication and identity resolution backend must be provided by
- a Windows NT4-style domain or from an Active Directory Domain that does not have the Microsoft
- Windows Services for UNIX installed, winbind is your best friend. Specific guidance for these
- situations now follows.
- </para>
-
- <para>
- <indexterm><primary>PAM</primary></indexterm>
- <indexterm><primary>Identity resolution</primary></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- To permit users to log on to a Linux system using Windows network credentials, you need to
- configure identity resolution (NSS) and PAM. This means that the basic steps include those
- outlined above with the addition of PAM configuration. Given that most workstations (desktop/client)
- usually do not need to provide file and print services to a group of users, the configuration
- of shares and printers is generally less important. Often this allows the share specifications
- to be entirely removed from the &smb.conf; file. That is obviously an administrator decision.
- </para>
-
- <sect3>
- <title>NT4 Domain Member</title>
-
- <para>
- The following steps provide a Linux system that users can log onto using
- Windows NT4 (or Samba) domain network credentials:
- </para>
-
- <procedure>
- <step><para>
- Follow the steps outlined in <link linkend="wdcsdm"/> and ensure that
- all validation tests function as shown.
- </para></step>
-
- <step><para>
- Identify what services users must log on to. On Red Hat Linux, if it is
- intended that the user shall be given access to all services, it may be
- most expeditious to simply configure the file
- <filename>/etc/pam.d/system-auth</filename>.
- </para></step>
-
- <step><para>
- Carefully make a backup copy of all PAM configuration files before you
- begin making changes. If you break the PAM configuration, please note
- that you may need to use an emergency boot process to recover your Linux
- system. It is possible to break the ability to log into the system if
- PAM files are incorrectly configured. The entire directory
- <filename>/etc/pam.d</filename> should be backed up to a safe location.
- </para></step>
-
- <step><para>
- If you require only console login support, edit the <filename>/etc/pam.d/login</filename>
- so it matches <link linkend="ch9-pamwnbdlogin"/>.
- </para></step>
-
- <step><para>
- To provide the ability to log onto the graphical desktop interface, you must edit
- the files <filename>gdm</filename> and <filename>xdm</filename> in the
- <filename>/etc/pam.d</filename> directory.
- </para></step>
-
- <step><para>
- Edit only one file at a time. Carefully validate its operation before attempting
- to reboot the machine.
- </para></step>
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>ADS Domain Member</title>
-
- <para>
- This procedure should be followed to permit a Linux network client (workstation/desktop)
- to permit users to log on using Microsoft Active Directory-based user credentials.
- </para>
-
- <procedure>
- <step><para>
- Follow the steps outlined in <link linkend="adssdm"/> and ensure that
- all validation tests function as shown.
- </para></step>
-
- <step><para>
- Identify what services users must log on to. On Red Hat Linux, if it is
- intended that the user shall be given access to all services, it may be
- most expeditious to simply configure the file
- <filename>/etc/pam.d/system-auth</filename> as shown in <link linkend="ch9-rhsysauth"/>.
- </para></step>
-
- <step><para>
- Carefully make a backup copy of all PAM configuration files before you
- begin making changes. If you break the PAM configuration, please note
- that you may need to use an emergency boot process to recover your Linux
- system. It is possible to break the ability to log into the system if
- PAM files are incorrectly configured. The entire directory
- <filename>/etc/pam.d</filename> should be backed up to a safe location.
- </para></step>
-
- <step><para>
- If you require only console login support, edit the <filename>/etc/pam.d/login</filename>
- so it matches <link linkend="ch9-pamwnbdlogin"/>.
- </para></step>
-
- <step><para>
- To provide the ability to log onto the graphical desktop interface, you must edit
- the files <filename>gdm</filename> and <filename>xdm</filename> in the
- <filename>/etc/pam.d</filename> directory.
- </para></step>
-
- <step><para>
- Edit only one file at a time. Carefully validate its operation before attempting
- to reboot the machine.
- </para></step>
- </procedure>
-
- </sect3>
-
-<example id="ch9-pamwnbdlogin">
-<title>SUSE: PAM <filename>login</filename> Module Using Winbind</title>
-<screen>
-# /etc/pam.d/login
-
-#%PAM-1.0
-auth sufficient pam_unix2.so nullok
-auth sufficient pam_winbind.so use_first_pass use_authtok
-auth required pam_securetty.so
-auth required pam_nologin.so
-auth required pam_env.so
-auth required pam_mail.so
-account sufficient pam_unix2.so
-account sufficient pam_winbind.so user_first_pass use_authtok
-password required pam_pwcheck.so nullok
-password sufficient pam_unix2.so nullok use_first_pass use_authtok
-password sufficient pam_winbind.so use_first_pass use_authtok
-session sufficient pam_unix2.so none
-session sufficient pam_winbind.so use_first_pass use_authtok
-session required pam_limits.so
-</screen>
-</example>
-
-<example id="ch9-pamwbndxdm">
-<title>SUSE: PAM <filename>xdm</filename> Module Using Winbind</title>
-<screen>
-# /etc/pam.d/gdm (/etc/pam.d/xdm)
-
-#%PAM-1.0
-auth sufficient pam_unix2.so nullok
-auth sufficient pam_winbind.so use_first_pass use_authtok
-account sufficient pam_unix2.so
-account sufficient pam_winbind.so use_first_pass use_authtok
-password sufficient pam_unix2.so
-password sufficient pam_winbind.so use_first_pass use_authtok
-session sufficient pam_unix2.so
-session sufficient pam_winbind.so use_first_pass use_authtok
-session required pam_dev perm.so
-session required pam_resmgr.so
-</screen>
-</example>
-
-<example id="ch9-rhsysauth">
-<title>Red Hat 9: PAM System Authentication File: <filename>/etc/pam.d/system-auth</filename> Module Using Winbind</title>
-<screen>
-#%PAM-1.0
-auth required /lib/security/$ISA/pam_env.so
-auth sufficient /lib/security/$ISA/pam_unix.so likeauth nullok
-auth sufficient /lib/security/$ISA/pam_winbind.so use_first_pass
-auth required /lib/security/$ISA/pam_deny.so
-
-account required /lib/security/$ISA/pam_unix.so
-account sufficient /lib/security/$ISA/pam_winbind.so use_first_pass
-
-password required /lib/security/$ISA/pam_cracklib.so retry=3 type=
-# Note: The above line is complete. There is nothing following the '='
-password sufficient /lib/security/$ISA/pam_unix.so \
- nullok use_authtok md5 shadow
-password sufficient /lib/security/$ISA/pam_winbind.so use_first_pass
-password required /lib/security/$ISA/pam_deny.so
-
-session required /lib/security/$ISA/pam_limits.so
-session sufficient /lib/security/$ISA/pam_unix.so
-session sufficient /lib/security/$ISA/pam_winbind.so use_first_pass
-</screen>
-</example>
-
- </sect2>
-
- <sect2>
- <title>Key Points Learned</title>
-
- <para>
- The addition of UNIX/Linux Samba servers and clients is a common requirement. In this chapter, you
- learned how to integrate such servers so that the UID/GID mappings they use can be consistent
- across all domain member servers. You also discovered how to implement the ability to use Samba
- or Windows domain account credentials to log on to a UNIX/Linux client.
- </para>
-
- <para>
- The following are key points made in this chapter:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Domain controllers are always authoritative for the domain.
- </para></listitem>
-
- <listitem><para>
- Domain members may have local accounts and must be able to resolve the identity of
- domain user accounts. Domain user account identity must map to a local UID/GID. That
- local UID/GID can be stored in LDAP. This way, it is possible to share the IDMAP data
- across all domain member machines.
- </para></listitem>
-
- <listitem><para>
- Resolution of user and group identities on domain member machines may be implemented
- using direct LDAP services or using winbind.
- </para></listitem>
-
- <listitem><para>
- On NSS/PAM enabled UNIX/Linux systems, NSS is responsible for identity management
- and PAM is responsible for authentication of logon credentials (username and password).
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- The following questions were obtained from the mailing list and also from private discussions
- with Windows network administrators.
- </para>
-
- <qandaset defaultlabel="chap09qa" type="number">
- <qandaentry>
- <question>
-
- <para>
- We use NIS for all UNIX accounts. Why do we need winbind?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>NIS</primary></indexterm>
- <indexterm><primary>encrypted passwords</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>Winbind</primary></indexterm>
- You can use NIS for your UNIX accounts. NIS does not store the Windows encrypted
- passwords that need to be stored in one of the acceptable passdb backends.
- Your choice of backend is limited to <parameter>smbpasswd</parameter> or
- <parameter>tdbsam</parameter>. Winbind is needed to handle the resolution of
- SIDs from trusted domains to local UID/GID values.
- </para>
-
- <para>
- <indexterm><primary>winbind trusted domains only</primary></indexterm>
- <indexterm><primary>getpwnam()</primary></indexterm>
- On a domain member server, you effectively map Windows domain users to local users
- that are in your NIS database by specifying the <parameter>winbind trusted domains
- only</parameter>. This causes user and group account lookups to be routed via
- the <command>getpwnam()</command> family of systems calls. On an NIS-enabled client,
- this pushes the resolution of users and groups out through NIS.
- </para>
-
- <para>
- As a general rule, it is always a good idea to run winbind on all Samba servers.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Our IT management people do not like LDAP but are looking at Microsoft Active Directory.
- Which is better?<indexterm>
- <primary>Active Directory</primary>
- </indexterm>
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>LDAP</primary>
- <secondary>server</secondary>
- </indexterm><indexterm>
- <primary>Kerberos</primary>
- </indexterm><indexterm>
- <primary>schema</primary>
- </indexterm>
- Microsoft Active Directory is an LDAP server that is intricately tied to a Kerberos
- infrastructure. Most IT managers who object to LDAP do so because
- an LDAP server is most often supplied as a raw tool that needs to be configured and
- for which the administrator must create the schema, create the administration tools, and
- devise the backup and recovery facilities in a site-dependent manner. LDAP servers
- in general are seen as a high-energy, high-risk facility.
- </para>
-
- <para><indexterm>
- <primary>management</primary>
- </indexterm>
- Microsoft Active Directory by comparison is easy to install and configure and
- is supplied with all tools necessary to implement and manage the directory. For sites
- that lack a lot of technical competence, Active Directory is a good choice. For sites
- that have the technical competence to handle Active Directory well, LDAP is a good
- alternative. The real issue is, What type of solution does
- the site want? If management wants a choice to use an alternative, they may want to
- consider the options. On the other hand, if management just wants a solution that works,
- Microsoft Active Directory is a good solution.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- We want to implement a Samba PDC, four Samba BDCs, and 10 Samba servers. Is it possible
- to use NIS in place of LDAP?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>NIS</primary>
- </indexterm><indexterm>
- <primary>LDAP</primary>
- </indexterm><indexterm>
- <primary>encrypted passwords</primary>
- </indexterm><indexterm>
- <primary>synchronized</primary>
- </indexterm><indexterm>
- <primary>secure account password</primary>
- </indexterm><indexterm>
- <primary>PDC</primary>
- </indexterm><indexterm>
- <primary>BDC</primary>
- </indexterm>
- Yes, it is possible to use NIS in place of LDAP, but there may be problems with keeping
- the Windows (SMB) encrypted passwords database correctly synchronized across the entire
- network. Workstations (Windows client machines) periodically change their domain
- membership secure account password. How can you keep changes that are on remote BDCs
- synchronized on the PDC?
- </para>
-
- <para><indexterm>
- <primary>centralized storage</primary>
- </indexterm><indexterm>
- <primary>management</primary>
- </indexterm><indexterm>
- <primary>network Identities</primary>
- </indexterm>
- LDAP is a more elegant solution because it permits centralized storage and management
- of all network identities (user, group, and machine accounts) together with all information
- Samba needs to provide to network clients and their users.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Are you suggesting that users should not log on to a domain member server? If so, why?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>security</primary>
- </indexterm><indexterm>
- <primary>data</primary>
- <secondary>integrity</secondary>
- </indexterm><indexterm>
- <primary>mapped drives</primary>
- </indexterm>
- Many UNIX administrators mock the model that the personal computer industry has adopted
- as normative since the early days of Novell NetWare. The old
- perception of the necessity to keep users off file and print servers was a result of
- fears concerning the security and integrity of data. It was a simple and generally
- effective measure to keep users away from servers, except through mapped drives.
- </para>
-
- <para><indexterm>
- <primary>user logins</primary>
- </indexterm><indexterm>
- <primary>risk</primary>
- </indexterm><indexterm>
- <primary>user errors</primary>
- </indexterm><indexterm>
- <primary>strategy</primary>
- </indexterm><indexterm>
- <primary>policy</primary>
- </indexterm>
- UNIX administrators are fully correct in asserting that UNIX servers and workstations
- are identical in terms of the software that is installed. They correctly assert that
- in a well-secured environment it is safe to store files on a system that has hundreds
- of users. But all network administrators must factor into the decision to allow or
- reject general user logins to a UNIX system that is principally a file and print
- server the risk to operations through simple user errors.
- Only then can one begin to appraise the best strategy and adopt a site-specific
- policy that best protects the needs of users and of the organization alike.
- </para>
-
- <para><indexterm>
- <primary>system level logins</primary>
- </indexterm>
- From experience, it is my recommendation to keep general system-level logins to a
- practical minimum and to eliminate them if possible. This should not be taken as a
- hard rule, though. The better question is, what works best for the site?
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>trusted domains</primary>
- </indexterm><indexterm>
- <primary>domain</primary>
- <secondary>trusted</secondary>
- </indexterm><indexterm>
- <primary>winbind trusted domains only</primary>
- </indexterm><indexterm>
- <primary>domain members</primary>
- </indexterm>
- We want to ensure that only users from our own domain plus from trusted domains can use our
- Samba servers. In the &smb.conf; file on all servers, we have enabled the <parameter>winbind
- trusted domains only</parameter> parameter. We now find that users from trusted domains
- cannot access our servers, and users from Windows clients that are not domain members
- can also access our servers. Is this a Samba bug?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>distributed</primary>
- </indexterm><indexterm>
- <primary>NIS</primary>
- </indexterm><indexterm>
- <primary>rsync</primary>
- </indexterm><indexterm>
- <primary>LDAP</primary>
- </indexterm><indexterm>
- <primary>winbindd</primary>
- </indexterm><indexterm>
- <primary>/etc/passwd</primary>
- </indexterm>
- The manual page for this <parameter>winbind trusted domains only</parameter> parameter says,
- <quote>This parameter is designed to allow Samba servers that are members of a Samba-controlled
- domain to use UNIX accounts distributed vi NIS, rsync, or LDAP as the UIDs for winbindd users
- in the hosts primary domain. Therefore, the user <constant>SAMBA\user1</constant> would be
- mapped to the account <constant>user1</constant> in <filename>/etc/passwd</filename> instead
- of allocating a new UID for him or her.</quote> This clearly suggests that you are trying
- to use this parameter inappropriately.
- </para>
-
- <para><indexterm>
- <primary>valid users</primary>
- </indexterm>
- A far better solution is to use the <parameter>valid users</parameter> by specifying
- precisely the domain users and groups that should be permitted access to the shares. You could,
- for example, set the following parameters:
-<screen>
-[demoshare]
- path = /export/demodata
- valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"
-</screen>
- </para>
-
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What are the benefits of using LDAP for my domain member servers?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>LDAP</primary>
- </indexterm><indexterm>
- <primary>benefit</primary>
- </indexterm><indexterm>
- <primary>UID</primary>
- </indexterm><indexterm>
- <primary>GID</primary>
- </indexterm><indexterm>
- <primary>Domain Controllers</primary>
- </indexterm><indexterm>
- <primary>Domain Member servers</primary>
- </indexterm><indexterm>
- <primary>copy</primary>
- </indexterm><indexterm>
- <primary>replicate</primary>
- </indexterm><indexterm>
- <primary>identity</primary>
- </indexterm>
- The key benefit of using LDAP is that the UID of all users and the GID of all groups
- are globally consistent on domain controllers as well as on domain member servers.
- This means that it is possible to copy/replicate files across servers without
- loss of identity.
- </para>
-
- <para><indexterm>
- <primary>Identity resolution</primary>
- </indexterm><indexterm>
- <primary>winbind</primary>
- </indexterm><indexterm>
- <primary>IDMAP backend</primary>
- </indexterm><indexterm>
- <primary>LDAP</primary>
- </indexterm><indexterm>
- <primary>Domain Controllers</primary>
- </indexterm><indexterm>
- <primary>Domain Member</primary>
- <secondary>servers</secondary>
- </indexterm><indexterm>
- <primary>Posix</primary>
- </indexterm><indexterm>
- <primary>account information</primary>
- </indexterm>
- When use is made of account identity resolution via winbind, even when an IDMAP backend
- is stored in LDAP, the UID/GID on domain member servers is consistent, but differs
- from the ID that the user/group has on domain controllers. The winbind allocated UID/GID
- that is stored in LDAP (or locally) will be in the numeric range specified in the <parameter>
- idmap uid/gid</parameter> in the &smb.conf; file. On domain controllers, the UID/GID is
- that of the POSIX value assigned in the LDAP directory as part of the POSIX account information.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Is proper DNS operation necessary for Samba plus LDAP? If so, what must I put into
- my DNS configuration?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>DNS</primary>
- <secondary>configuration</secondary>
- </indexterm><indexterm>
- <primary>DNS</primary>
- <secondary>lookup</secondary>
- </indexterm><indexterm>
- <primary>hosts</primary>
- </indexterm><indexterm>
- <primary>/etc/nsswitch.conf</primary>
- </indexterm><indexterm>
- <primary>NSS</primary>
- </indexterm><indexterm>
- <primary>/etc/hosts</primary>
- </indexterm><indexterm>
- <primary>WINS</primary>
- <secondary>lookup</secondary>
- </indexterm>
- Samba depends on correctly functioning resolution of hostnames to their IP address. Samba
- makes no direct DNS lookup calls, but rather redirects all name-to-address calls via the
- <command>getXXXbyXXX()</command> function calls. The configuration of the <constant>hosts</constant>
- entry in the NSS <filename>/etc/nsswitch.conf</filename> file determines how the underlying
- resolution process is implemented. If the <constant>hosts</constant> entry in your NSS
- control file says:
-<screen>
-hosts: files dns wins
-</screen>
- this means that a hostname lookup first tries the <filename>/etc/hosts</filename>.
- If this fails to resolve, it attempts a DNS lookup, and if that fails, it tries a
- WINS lookup.
- </para>
-
- <para><indexterm>
- <primary>NetBIOS</primary>
- </indexterm><indexterm>
- <primary>TCP/IP</primary>
- </indexterm><indexterm>
- <primary>name resolution</primary>
- </indexterm>
- The addition of the WINS-based name lookup makes sense only if NetBIOS over TCP/IP has
- been enabled on all Windows clients. Where NetBIOS over TCP/IP has been disabled, DNS
- is the preferred name resolution technology. This usually makes most sense when Samba
- is a client of an Active Directory domain, where NetBIOS use has been disabled. In this
- case, the Windows 200x autoregisters all locator records it needs with its own DNS
- server or servers.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Our Windows 2003 Server Active Directory domain runs with NetBIOS disabled. Can we
- use Samba with that configuration?
- </para>
-
- </question>
- <answer>
-
- <para>
- Yes.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>net</primary>
- <secondary>ads</secondary>
- <tertiary>join</tertiary>
- </indexterm><indexterm>
- <primary>net</primary>
- <secondary>rpc</secondary>
- <tertiary>join</tertiary>
- </indexterm>
- When I tried to execute net ads join, I got no output. It did not work, so
- I think that it failed. I then executed net rpc join and that worked fine.
- That is okay, isn't it?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>Kerberos</primary>
- </indexterm><indexterm>
- <primary>authentication</primary>
- </indexterm>
- No. This is not okay. It means that your Samba client has joined the ADS domain as
- a Windows NT4 client, and Samba will not be using Kerberos-based authentication.
- </para>
-
- </answer>
- </qandaentry>
-
- </qandaset>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE appendix PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<chapter id="appendix">
- <title>A Collection of Useful Tidbits</title>
-
- <para>
- <indexterm><primary>material</primary></indexterm>
- <indexterm><primary>domain</primary><secondary>joining</secondary></indexterm>
- Information presented here is considered to be either basic or well-known material that is informative
- yet helpful. Over the years, I have observed an interesting behavior. There is an expectation that
- the process for joining a Windows client to a Samba-controlled Windows domain may somehow involve steps
- different from doing so with Windows NT4 or a Windows ADS domain. Be assured that the steps are identical,
- as shown in the example given below.
- </para>
-
-<sect1 id="domjoin">
-<title>Joining a Domain: Windows 200x/XP Professional</title>
-
- <para>
- <indexterm><primary>joining a domain</primary></indexterm>
- Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security.
- This section steps through the process for making a Windows 200x/XP Professional machine a
- member of a Domain Security environment. It should be noted that this process is identical
- when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
- </para>
-
- <procedure>
- <title>Steps to Join a Domain</title>
-
- <step><para>
- Click <guimenu>Start</guimenu>.
- </para></step>
-
- <step><para>
- Right-click <guimenu>My Computer</guimenu>, and then select <guimenuitem>Properties</guimenuitem>.
- </para></step>
-
- <step><para>
- The opening panel is the same one that can be reached by clicking <guimenu>System</guimenu> on the Control Panel.
- See <link linkend="swxpp001"></link>.
- <figure id="swxpp001"><title>The General Panel.</title><imagefile>wxpp001</imagefile></figure>
- </para></step>
-
- <step><para>
- Click the <guimenu>Computer Name</guimenu> tab.
- This panel shows the <guimenuitem>Computer Description</guimenuitem>, the <guimenuitem>Full computer name</guimenuitem>,
- and the <guimenuitem>Workgroup</guimenuitem> or <guimenuitem>Domain name</guimenuitem>.
- </para>
-
- <para>
- Clicking the <guimenu>Network ID</guimenu> button launches the configuration wizard. Do not use this with
- Samba. If you wish to change the computer name, or join or leave the domain, click the <guimenu>Change</guimenu> button.
- See <link linkend="swxpp004"></link>.
- <figure id="swxpp004"><title>The Computer Name Panel.</title><imagefile>wxpp004</imagefile></figure>
- </para></step>
-
- <step><para>
- Click on <guimenu>Change</guimenu>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
- We join the domain called MIDEARTH. See <link linkend="swxpp006"></link>.
- <figure id="swxpp006"><title>The Computer Name Changes Panel</title><imagefile>wxpp006</imagefile></figure>
- </para></step>
-
- <step><para>
- Enter the name <guimenu>MIDEARTH</guimenu> in the field below the Domain radio button.
- </para>
-
- <para>
- This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <link linkend="swxpp007"></link>.
- <figure id="swxpp007"><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH</title><imagefile>wxpp007</imagefile></figure>
- </para></step>
-
- <step><para>
- Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the credentials (username and password)
- of a domain administrative account that has the rights to add machines to the domain.
- </para>
-
- <para>
- Enter the name <quote>root</quote> and the root password from your Samba server. See <link linkend="swxpp008"></link>.
- <figure id="swxpp008"><title>Computer Name Changes &smbmdash; User name and Password Panel</title><imagefile>wxpp008</imagefile></figure>
- </para></step>
-
- <step><para>
- Click <guimenu>OK</guimenu>.
- </para>
-
- <para>
- The <quote>Welcome to the MIDEARTH domain</quote> dialog box should appear. At this point, the machine must be rebooted.
- Joining the domain is now complete.
- </para></step>
-
- </procedure>
-
- <para>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- The screen capture shown in <link linkend="swxpp007"/> has a button labeled <guimenu>More...</guimenu>. This button opens a
- panel in which you can set (or change) the Primary DNS suffix of the computer. This is a parameter that mainly affects members
- of Microsoft Active Directory. Active Directory is heavily oriented around the DNS namespace.
- </para>
-
- <para>
- <indexterm><primary>Netlogon</primary></indexterm>
- <indexterm><primary>DNS</primary><secondary>dynamic</secondary></indexterm>
- Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers
- register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server
- to find the services (like which machines are domain controllers or which machines have the Netlogon service running).
- </para>
-
- <para>
- <indexterm><primary>DNS</primary><secondary>suffix</secondary></indexterm>
- The default setting of the Primary DNS suffix is the Active Directory domain name. When you change the Primary DNS suffix,
- this does not affect domain membership, but it can break network browsing and the ability to resolve your computer name to
- a valid IP address.
- </para>
-
- <para>
- The Primary DNS suffix parameter principally affects MS Windows clients that are members of an Active Directory domain.
- Where the client is a member of a Samba domain, it is preferable to leave this field blank.
- </para>
-
- <para>
- <indexterm><primary>Group Policy</primary></indexterm>
- According to Microsoft documentation, <quote>If this computer belongs to a group with <constant>Group Policy</constant>
- enabled on <command>Primary DNS suffice of this computer</command>, the string specified in the Group Policy is used
- as the primary DNS suffix and you might need to restart your computer to view the correct setting. The local setting is
- used only if Group Policy is disabled or unspecified.</quote>
- </para>
-
-</sect1>
-
-<sect1>
- <title>Samba System File Location</title>
-
- <para><indexterm>
- <primary>default installation</primary>
- </indexterm><indexterm>
- <primary>/usr/local/samba</primary>
- </indexterm><indexterm>
- <primary>/usr/local</primary>
- </indexterm>
- One of the frustrations expressed by subscribers to the Samba mailing lists revolves around the choice of where the default Samba Team
- build and installation process locates its Samba files. The location, chosen in the early 1990s, for the default installation is
- in the <filename>/usr/local/samba</filename> directory. This is a perfectly reasonable location, particularly given all the other
- Open Source software that installs into the <filename>/usr/local</filename> subdirectories.
- </para>
-
- <para>
- Several UNIX vendors, and Linux vendors in particular, elected to locate the Samba files in a location other than the Samba Team
- default.
- </para>
-
- <para><indexterm>
- <primary>Free Standards Group</primary>
- <see>FSG</see>
- </indexterm><indexterm>
- <primary>FSG</primary>
- </indexterm><indexterm>
- <primary>Linux Standards Base</primary>
- <see>LSB</see>
- </indexterm><indexterm>
- <primary>LSB</primary>
- </indexterm><indexterm>
- <primary>File Hierarchy System</primary>
- <see>FHS</see>
- </indexterm><indexterm>
- <primary>FHS</primary>
- </indexterm><indexterm>
- <primary>file locations</primary>
- </indexterm><indexterm>
- <primary>/etc/samba</primary>
- </indexterm><indexterm>
- <primary>/usr/sbin</primary>
- </indexterm><indexterm>
- <primary>/usr/bin</primary>
- </indexterm><indexterm>
- <primary>/usr/share</primary>
- </indexterm><indexterm>
- <primary>/usr/share/swat</primary>
- </indexterm><indexterm>
- <primary>/usr/lib/samba</primary>
- </indexterm><indexterm>
- <primary>/usr/share/samba/swat</primary>
- </indexterm><indexterm>
- <primary>SWAT</primary>
- </indexterm><indexterm>
- <primary>VFS modules</primary>
- </indexterm>
- Linux vendors, working in conjunction with the Free Standards Group (FSG), Linux Standards Base (LSB), and File Hierarchy
- System (FHS), have elected to locate the configuration files under the <filename>/etc/samba</filename> directory, common binary
- files (those used by users) in the <filename>/usr/bin</filename> directory, and the administrative files (daemons) in the
- <filename>/usr/sbin</filename> directory. Support files for the Samba Web Admin Tool (SWAT) are located under the
- <filename>/usr/share</filename> directory, either in <filename>/usr/share/samba/swat</filename> or in
- <filename>/usr/share/swat</filename>. There are additional support files for <command>smbd</command> in the
- <filename>/usr/lib/samba</filename> directory tree. The files located there include the dynamically loadable modules for the
- passdb backend as well as for the VFS modules.
- </para>
-
- <para><indexterm>
- <primary>/var/lib/samba</primary>
- </indexterm><indexterm>
- <primary>/var/log/samba</primary>
- </indexterm><indexterm>
- <primary>run-time control files</primary>
- </indexterm>
- Samba creates runtime control files and generates log files. The runtime control files (tdb and dat files) are stored in
- the <filename>/var/lib/samba</filename> directory. Log files are created in <filename>/var/log/samba.</filename>
- </para>
-
- <para>
- When Samba is built and installed using the default Samba Team process, all files are located under the
- <filename>/usr/local/samba</filename> directory tree. This makes it simple to find the files that Samba owns.
- </para>
-
- <para><indexterm>
- <primary>smbd</primary>
- <secondary>location of files</secondary>
- </indexterm>
- One way to find the Samba files that are installed on your UNIX/Linux system is to search for the location
- of all files called <command>smbd</command>. Here is an example:
-<screen>
-&rootprompt; find / -name smbd -print
-</screen>
- You can find the location of the configuration files by running:
-<screen>
-&rootprompt; /path-to-binary-file/smbd -b | more
-...
-Paths:
- SBINDIR: /usr/sbin
- BINDIR: /usr/bin
- SWATDIR: /usr/share/samba/swat
- CONFIGFILE: /etc/samba/smb.conf
- LOGFILEBASE: /var/log/samba
- LMHOSTSFILE: /etc/samba/lmhosts
- LIBDIR: /usr/lib/samba
- SHLIBEXT: so
- LOCKDIR: /var/lib/samba
- PIDDIR: /var/run/samba
- SMB_PASSWD_FILE: /etc/samba/smbpasswd
- PRIVATE_DIR: /etc/samba
-...
-</screen>
- If you wish to locate the Samba version, just run:
-<screen>
-&rootprompt; /path-to-binary-file/smbd -V
-Version 3.0.20-SUSE
-</screen>
- </para>
-
- <para>
- Many people have been caught by installation of Samba using the default Samba Team process when it was already installed
- by the platform vendor's method. If your platform uses RPM format packages, you can check to see if Samba is installed by
- executing:<indexterm>
- <primary>rpm</primary>
- </indexterm>
-<screen>
-&rootprompt; rpm -qa | grep samba
-samba3-pdb-3.0.20-1
-samba3-vscan-0.3.6-0
-samba3-winbind-3.0.20-1
-samba3-3.0.20-1
-samba3-python-3.0.20-1
-samba3-utils-3.0.20-1
-samba3-doc-3.0.20-1
-samba3-client-3.0.20-1
-samba3-cifsmount-3.0.20-1
- </screen><indexterm>
- <primary>package names</primary>
- </indexterm>
- The package names, of course, vary according to how the vendor, or the binary package builder, prepared them.
- </para>
-
-</sect1>
-
-<sect1>
- <title>Starting Samba</title>
-
- <para><indexterm>
- <primary>daemon</primary>
- </indexterm>
- Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services.
- An example of a service is the Apache Web server for which the daemon is called <command>httpd</command>. In the case of Samba, there
- are three daemons, two of which are needed as a minimum.
- </para>
-
- <para>
- The Samba server is made up of the following daemons:
- </para>
-
-<example id="ch12SL">
-<title>A Useful Samba Control Script for SUSE Linux</title>
-<screen>
-#!/bin/bash
-#
-# Script to start/stop samba
-# Locate this in /sbin as a file called 'samba'
-
-RCD=/etc/rc.d
-
-if [ z$1 == 'z' ]; then
- echo $0 - No arguments given; must be start or stop.
- exit
-fi
-
-if [ $1 == 'start' ]; then
- ${RCD}/nmb start
- ${RCD}/smb start
- ${RCD}/winbind start
-
-fi
-if [ $1 == 'stop' ]; then
- ${RCD}/smb stop
- ${RCD}/winbind stop
- ${RCD}/nmb stop
-fi
-if [ $1 == 'restart' ]; then
- ${RCD}/smb stop
- ${RCD}/winbind stop
- ${RCD}/nmb stop
- sleep 5
- ${RCD}/nmb start
- ${RCD}/smb start
- ${RCD}/winbind start
-fi
-exit 0
-</screen>
-</example>
-
- <variablelist>
- <varlistentry><term>nmbd</term>
- <listitem><para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
- This daemon handles all name registration and resolution requests. It is the primary vehicle involved
- in network browsing. It handles all UDP-based protocols. The <command>nmbd</command> daemon should
- be the first command started as part of the Samba startup process.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>smbd</term>
- <listitem><para>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
- This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
- manages local authentication. It should be started immediately following the startup of <command>nmbd</command>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>winbindd</term>
- <listitem><para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
- This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
- Samba has trust relationships with another domain. The <command>winbindd</command> daemon will check the
- &smb.conf; file for the presence of the <parameter>idmap uid</parameter> and <parameter>idmap gid</parameter>
- parameters. If they are not found, <command>winbindd</command> bails out and refuses to start.
- </para></listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its
- integration into the platform as a whole. Please refer to your operating system platform administration manuals for
- specific information pertaining to correct management of Samba startup.
- </para>
-
-<example id="ch12RHscript">
-<title>A Sample Samba Control Script for Red Hat Linux</title>
-<screen>
-#!/bin/sh
-#
-# chkconfig: 345 81 35
-# description: Starts and stops the Samba smbd and nmbd daemons \
-# used to provide SMB network services.
-
-# Source function library.
-. /etc/rc.d/init.d/functions
-# Source networking configuration.
-. /etc/sysconfig/network
-# Check that networking is up.
-[ ${NETWORKING} = "no" ] && exit 0
-CONFIG=/etc/samba/smb.conf
-# Check that smb.conf exists.
-[ -f $CONFIG ] || exit 0
-
-# See how we were called.
-case "$1" in
- start)
- echo -n "Starting SMB services: "
- daemon smbd -D; daemon nmbd -D; echo;
- touch /var/lock/subsys/smb
- ;;
- stop)
- echo -n "Shutting down SMB services: "
- smbdpids=`ps guax | grep smbd | grep -v grep | awk '{print $2}'`
- for pid in $smbdpids; do
- kill -TERM $pid
- done
- killproc nmbd -TERM; rm -f /var/lock/subsys/smb
- echo ""
- ;;
- status)
- status smbd; status nmbd;
- ;;
- restart)
- echo -n "Restarting SMB services: "
- $0 stop; $0 start;
- echo "done."
- ;;
- *)
- echo "Usage: smb {start|stop|restart|status}"
- exit 1
-esac
-</screen>
-</example>
-
- <para><indexterm>
- <primary>samba control script</primary>
- </indexterm>
- SUSE Linux implements individual control over each Samba daemon. A Samba control script that can be conveniently
- executed from the command line is shown in <link linkend="ch12SL"/>. This can be located in the directory
- <filename>/sbin</filename> in a file called <filename>samba</filename>. This type of control script should be
- owned by user root and group root, and set so that only root can execute it.
- </para>
-
- <para><indexterm>
- <primary>startup script</primary>
- </indexterm>
- A sample startup script for a Red Hat Linux system is shown in <link linkend="ch12RHscript"/>.
- This file could be located in the directory <filename>/etc/rc.d</filename> and can be called
- <filename>samba</filename>. A similar startup script is required to control <command>winbind</command>.
- If you want to find more information regarding startup scripts please refer to the packaging section of
- the Samba source code distribution tarball. The packaging files for each platform include a
- startup control file.
- </para>
-
-</sect1>
-
-<sect1>
- <title>DNS Configuration Files</title>
-
- <para>
- The following files are common to all DNS server configurations. Rather than repeat them multiple times, they
- are presented here for general reference.
- </para>
-
- <sect2>
- <title>The Forward Zone File for the Loopback Adaptor</title>
-
- <para>
- The forward zone file for the loopback address never changes. An example file is shown
- in <link linkend="loopback"/>. All traffic destined for an IP address that is hosted on a
- physical interface on the machine itself is routed to the loopback adaptor. This is
- a fundamental design feature of the TCP/IP protocol implementation. The loopback adaptor
- is called <constant>localhost</constant>.
- </para>
-
-<example id="loopback">
-<title>DNS Localhost Forward Zone File: <filename>/var/lib/named/localhost.zone</filename></title>
-<screen>
-$TTL 1W
-@ IN SOA @ root (
- 42 ; serial
- 2D ; refresh
- 4H ; retry
- 6W ; expiry
- 1W ) ; minimum
-
- IN NS @
- IN A 127.0.0.1
-</screen>
-</example>
-
- </sect2>
-
- <sect2>
- <title>The Reverse Zone File for the Loopback Adaptor</title>
-
- <para>
- The reverse zone file for the loopback address as shown in <link linkend="dnsloopy"/>
- is necessary so that references to the address <constant>127.0.0.1</constant> can be
- resolved to the correct name of the interface.
- </para>
-
-<example id="dnsloopy">
-<title>DNS Localhost Reverse Zone File: <filename>/var/lib/named/127.0.0.zone</filename></title>
-<screen>
-$TTL 1W
-@ IN SOA localhost. root.localhost. (
- 42 ; serial
- 2D ; refresh
- 4H ; retry
- 6W ; expiry
- 1W ) ; minimum
-
- IN NS localhost.
-1 IN PTR localhost.
-</screen>
-</example>
-
-<example id="roothint">
-<title>DNS Root Name Server Hint File: <filename>/var/lib/named/root.hint</filename></title>
-<screen>
-; This file is made available by InterNIC under anonymous FTP as
-; file /domain/named.root
-; on server FTP.INTERNIC.NET
-; last update: Nov 5, 2002. Related version of root zone: 2002110501
-; formerly NS.INTERNIC.NET
-. 3600000 IN NS A.ROOT-SERVERS.NET.
-A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
-; formerly NS1.ISI.EDU
-. 3600000 NS B.ROOT-SERVERS.NET.
-B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
-; formerly C.PSI.NET
-. 3600000 NS C.ROOT-SERVERS.NET.
-C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
-; formerly TERP.UMD.EDU
-. 3600000 NS D.ROOT-SERVERS.NET.
-D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
-; formerly NS.NASA.GOV
-. 3600000 NS E.ROOT-SERVERS.NET.
-E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
-; formerly NS.ISC.ORG
-. 3600000 NS F.ROOT-SERVERS.NET.
-F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
-; formerly NS.NIC.DDN.MIL
-. 3600000 NS G.ROOT-SERVERS.NET.
-G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
-; formerly AOS.ARL.ARMY.MIL
-. 3600000 NS H.ROOT-SERVERS.NET.
-H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
-; formerly NIC.NORDU.NET
-. 3600000 NS I.ROOT-SERVERS.NET.
-I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
-; operated by VeriSign, Inc.
-. 3600000 NS J.ROOT-SERVERS.NET.
-J.ROOT-SERVERS.NET. 3600000 A 192.58.128.30
-; housed in LINX, operated by RIPE NCC
-. 3600000 NS K.ROOT-SERVERS.NET.
-K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
-; operated by IANA
-. 3600000 NS L.ROOT-SERVERS.NET.
-L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12
-; housed in Japan, operated by WIDE
-. 3600000 NS M.ROOT-SERVERS.NET.
-M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
-; End of File
-</screen>
-</example>
- </sect2>
-
- <sect2>
- <title>DNS Root Server Hint File</title>
-
- <para>
- The content of the root hints file as shown in <link linkend="roothint"/> changes slowly over time.
- Periodically this file should be updated from the source shown. Because
- of its size, this file is located at the end of this chapter.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1 id="altldapcfg">
- <title>Alternative LDAP Database Initialization</title>
-
- <para><indexterm>
- <primary>LDAP</primary>
- <secondary>database</secondary>
- </indexterm><indexterm>
- <primary>LDAP</primary>
- <secondary>initial configuration</secondary>
- </indexterm>
- The following procedure may be used as an alternative means of configuring
- the initial LDAP database. Many administrators prefer to have greater control
- over how system files get configured.
- </para>
-
- <sect2>
- <title>Initialization of the LDAP Database</title>
-
- <para><indexterm>
- <primary>LDIF</primary>
- </indexterm><indexterm>
- <primary>Domain Groups</primary>
- <secondary>well-known</secondary>
- </indexterm><indexterm>
- <primary>SID</primary>
- </indexterm>
- The first step to get the LDAP server ready for action is to create the LDIF file from
- which the LDAP database will be preloaded. This is necessary to create the containers
- into which the user, group, and other accounts are written. It is also necessary to
- preload the well-known Windows NT Domain Groups, as they must have the correct SID so
- that they can be recognized as special NT Groups by the MS Windows clients.
- </para>
-
- <procedure id="ldapinit">
- <title>LDAP Directory Pre-Load Steps</title>
-
- <step><para>
- Create a directory in which to store the files you use to generate
- the LDAP LDIF file for your system. Execute the following:
-<screen>
-&rootprompt; mkdir /etc/openldap/SambaInit
-&rootprompt; chown root:root /etc/openldap/SambaInit
-&rootprompt; chmod 700 /etc/openldap/SambaInit
-</screen>
- </para></step>
-
- <step><para>
- Install the files shown in <link linkend="sbehap-ldapreconfa"/>, <link linkend="sbehap-ldapreconfb"/>,
- and <link linkend="sbehap-ldapreconfc"/> into the directory
- <filename>/etc/openldap/SambaInit/SMBLDAP-ldif-preconfig.sh.</filename> These three files are,
- respectively, parts A, B, and C of the <filename>SMBLDAP-ldif-preconfig.sh</filename> file.
- </para></step>
-
- <step><para>
- Install the files shown in <link linkend="sbehap-ldifpata"/> and <link linkend="sbehap-ldifpatb"/> into the directory
- <filename>/etc/openldap/SambaInit/.</filename> These two files are
- parts A and B, respectively, of the <filename>init-ldif.pat</filename> file.
- </para></step>
-
- <step><para>
- Change to the <filename>/etc/openldap/SambaInit</filename> directory. Execute the following:
-<screen>
-&rootprompt; sh SMBLDAP-ldif-preconfig.sh
-
-How do you wish to refer to your organization?
-Suggestions:
- Black Tire Company, Inc.
- Cat With Hat Ltd.
-How would you like your organization name to appear?
-Your organization name is: My Organization
-Enter a new name is this is not what you want, press Enter to Continue.
-Name [My Organization]: Abmas Inc.
-
-Samba Config File Location [/etc/samba/smb.conf]:
-Enter a new full path or press Enter to continue.
-Samba Config File Location [/etc/samba/smb.conf]:
-Domain Name: MEGANET2
-Domain SID: S-1-5-21-3504140859-1010554828-2431957765
-
-The name of your Internet domain is now needed in a special format
-as follows, if your domain name is mydomain.org, what we need is
-the information in the form of:
- Domain ID: mydomain
- Top level: org
-If your fully qualified hostname is: snoopy.bazaar.garagesale.net
-where "snoopy" is the name of the machine,
-Then the information needed is:
- Domain ID: garagesale
- Top Level: net
-
-Found the following domain name: abmas.biz
-I think the bit we are looking for might be: abmas
-Enter the domain name or press Enter to continue:
-
-The top level organization name I will use is: biz
-Enter the top level org name or press Enter to continue:
-&rootprompt;
-</screen>
- This creates a file called <filename>MEGANET2.ldif</filename>.
- </para></step>
-
- <step><para>
- It is now time to preload the LDAP database with the following
- command:
-<screen>
-&rootprompt; slapadd -v -l MEGANET2.ldif
-added: "dc=abmas,dc=biz" (00000001)
-added: "cn=Manager,dc=abmas,dc=biz" (00000002)
-added: "ou=People,dc=abmas,dc=biz" (00000003)
-added: "ou=Computers,dc=abmas,dc=biz" (00000004)
-added: "ou=Groups,dc=abmas,dc=biz" (00000005)
-added: "ou=Domains,dc=abmas,dc=biz" (00000006)
-added: "sambaDomainName=MEGANET2,ou=Domains,dc=abmas,dc=biz" (00000007)
-added: "cn=domadmins,ou=Groups,dc=abmas,dc=biz" (00000008)
-added: "cn=domguests,ou=Groups,dc=abmas,dc=biz" (00000009)
-added: "cn=domusers,ou=Groups,dc=abmas,dc=biz" (0000000a)
-</screen>
- You should verify that the account information was correctly loaded by executing:
-<screen>
-&rootprompt; slapcat
-dn: dc=abmas,dc=biz
-objectClass: dcObject
-objectClass: organization
-dc: abmas
-o: Abmas Inc.
-description: Posix and Samba LDAP Identity Database
-structuralObjectClass: organization
-entryUUID: af552f8e-c4a1-1027-9002-9421e01bf474
-creatorsName: cn=manager,dc=abmas,dc=biz
-modifiersName: cn=manager,dc=abmas,dc=biz
-createTimestamp: 20031217055747Z
-modifyTimestamp: 20031217055747Z
-entryCSN: 2003121705:57:47Z#0x0001#0#0000
-...
-
-dn: cn=domusers,ou=Groups,dc=abmas,dc=biz
-objectClass: posixGroup
-objectClass: sambaGroupMapping
-gidNumber: 513
-cn: domusers
-sambaSID: S-1-5-21-3504140859-1010554828-2431957765-513
-sambaGroupType: 2
-displayName: Domain Users
-description: Domain Users
-structuralObjectClass: posixGroup
-entryUUID: af7e98ba-c4a1-1027-900b-9421e01bf474
-creatorsName: cn=manager,dc=abmas,dc=biz
-modifiersName: cn=manager,dc=abmas,dc=biz
-createTimestamp: 20031217055747Z
-modifyTimestamp: 20031217055747Z
-entryCSN: 2003121705:57:47Z#0x000a#0#0000
-</screen>
- </para></step>
-
- <step><para>
- Your LDAP database is ready for testing. You can now start the LDAP server
- using the system tool for your Linux operating system. For SUSE Linux, you can
- do this as follows:
-<screen>
-&rootprompt; rcldap start
-</screen>
- </para></step>
-
- <step><para>
- It is now a good idea to validate that the LDAP server is running correctly.
- Execute the following:
-<screen>
-&rootprompt; ldapsearch -x -b "dc=abmas,dc=biz" "(ObjectClass=*)"
-# extended LDIF
-#
-# LDAPv3
-# base <dc=abmas,dc=biz> with scope sub
-# filter: (ObjectClass=*)
-# requesting: ALL
-#
-
-# abmas.biz
-dn: dc=abmas,dc=biz
-objectClass: dcObject
-objectClass: organization
-dc: abmas
-o: Abmas Inc.
-description: Posix and Samba LDAP Identity Database
-...
-# domusers, Groups, abmas.biz
-dn: cn=domusers,ou=Groups,dc=abmas,dc=biz
-objectClass: posixGroup
-objectClass: sambaGroupMapping
-gidNumber: 513
-cn: domusers
-sambaSID: S-1-5-21-3504140859-1010554828-2431957765-513
-sambaGroupType: 2
-displayName: Domain Users
-description: Domain Users
-
-# search result
-search: 2
-result: 0 Success
-
-# numResponses: 11
-# numEntries: 10
-</screen>
- Your LDAP server is ready for creation of additional accounts.
- </para></step>
- </procedure>
-
- </sect2>
-
-<example id="sbehap-ldapreconfa">
-<title>LDAP Pre-configuration Script: <filename>SMBLDAP-ldif-preconfig.sh</filename> &smbmdash; Part A</title>
-<screen>
-#!/bin/bash
-#
-# This script prepares the ldif LDAP load file only
-#
-
-# Pattern File Name
-file=init-ldif.pat
-
-# The name of my organization
-ORGNAME="My Organization"
-
-# My Internet domain. ie: if my domain is: buckets.org, INETDOMAIN="buckets"
-INETDOMAIN="my-domain"
-
-# In the above case, md domain is: buckets.org, TLDORG="org"
-TLDORG="org"
-
-# This is the Samba Domain/Workgroup Name
-DOMNAME="MYWORKGROUP"
-
-#
-# Here We Go ...
-#
-
-cat <<EOF
-
-How do you wish to refer to your organization?
-
-Suggestions:
- Black Tire Company, Inc.
- Cat With Hat Ltd.
-
-How would you like your organization name to appear?
-
-EOF
-
-echo "Your organization name is: $ORGNAME"
-echo
-echo "Enter a new name or, press Enter to Continue."
-echo
-</screen>
-</example>
-
-<example id="sbehap-ldapreconfb">
-<title>LDAP Pre-configuration Script: <filename>SMBLDAP-ldif-preconfig.sh</filename> &smbmdash; Part B</title>
-<screen>
-echo -e -n "Name [$ORGNAME]: "
- read name
-
-if [ ! -z "$name" ]; then
- ORGNAME=${name}
-fi
-echo
-sed "s/ORGNAME/${ORGNAME}/g" < $file > $file.tmp1
-
-# Try to find smb.conf
-
-if [ -e /usr/local/samba/lib/smb.conf ]; then
- CONF=/usr/local/samba/lib/smb.conf
-elif [ -e /etc/samba/smb.conf ]; then
- CONF=/etc/samba/smb.conf
-fi
-
-echo "Samba Config File Location [$CONF]: "
-echo
-echo "Enter a new full path or press Enter to continue."
-echo
-echo -n "Samba Config File Location [$CONF]: "
- read name
-if [ ! -z "$name" ]; then
- CONF=$name
-fi
-echo
-
-# Find the name of our Domain/Workgroup
-DOMNAME=`grep -i workgroup ${CONF} | sed "s/ //g" | cut -f2 -d=`
-echo Domain Name: $DOMNAME
-echo
-
-sed "s/DOMNAME/${DOMNAME}/g" < $file.tmp1 > $file.tmp2
-
-DOMSID=`net getlocalsid ${DOMNAME} | cut -f2 -d: | sed "s/ //g"`
-echo Domain SID: $DOMSID
-
-sed "s/DOMSID/${DOMSID}/g" < $file.tmp2 > $file.tmp1
-</screen>
-</example>
-
-<example id="sbehap-ldapreconfc">
-<title>LDAP Pre-configuration Script: <filename>SMBLDAP-ldif-preconfig.sh</filename> &smbmdash; Part C</title>
-<screen>
-cat <<EOL
-The name of your Internet domain is now needed in a special format
-as follows, if your domain name is mydomain.org, what we need is
-the information in the form of:
- Domain ID: mydomain
- Top level: org
-
-If your fully qualified hostname is: snoopy.bazaar.garagesale.net
-where "snoopy" is the name of the machine,
-Then the information needed is:
- Domain ID: garagesale
- Top Level: net
-
-EOL
-INETDOMAIN=`hostname -d | cut -f1 -d.`
-echo Found the following domain name: `hostname -d`
-echo "I think the bit we are looking for might be: $INETDOMAIN"
-echo
-echo -n "Enter the domain name or press Enter to continue: "
- read domnam
-if [ ! -z $domnam ]; then
- INETDOMAIN=$domnam
-fi
-echo
-sed "s/INETDOMAIN/${INETDOMAIN}/g" < $file.tmp1 > $file.tmp2
-TLDORG=`hostname -d | sed "s/${INETDOMAIN}.//g"`
-echo "The top level organization name I will use is: ${TLDORG}"
-echo
-echo -n "Enter the top level org name or press Enter to continue: "
- read domnam
-if [ ! -z $domnam ]; then
- TLDORG=$domnam
-fi
-sed "s/TLDORG/${TLDORG}/g" < $file.tmp2 > $DOMNAME.ldif
-rm $file.tmp*
-exit 0
-</screen>
-</example>
-
-<example id="sbehap-ldifpata">
-<title>LDIF Pattern File Used to Pre-configure LDAP &smbmdash; Part A</title>
-<screen>
-dn: dc=INETDOMAIN,dc=TLDORG
-objectClass: dcObject
-objectClass: organization
-dc: INETDOMAIN
-o: ORGNAME
-description: Posix and Samba LDAP Identity Database
-
-dn: cn=Manager,dc=INETDOMAIN,dc=TLDORG
-objectClass: organizationalRole
-cn: Manager
-description: Directory Manager
-
-dn: ou=People,dc=INETDOMAIN,dc=TLDORG
-objectClass: top
-objectClass: organizationalUnit
-ou: People
-
-dn: ou=Computers,dc=INETDOMAIN,dc=TLDORG
-objectClass: top
-objectClass: organizationalUnit
-ou: Computers
-
-dn: ou=Groups,dc=INETDOMAIN,dc=TLDORG
-objectClass: top
-objectClass: organizationalUnit
-ou: Groups
-
-dn: ou=Idmap,dc=INETDOMAIN,dc=TLDORG
-objectClass: top
-objectClass: organizationalUnit
-ou: Idmap
-
-dn: ou=Domains,dc=INETDOMAIN,dc=TLDORG
-objectClass: top
-objectClass: organizationalUnit
-ou: Domains
-
-dn: sambaDomainName=DOMNAME,ou=Domains,dc=INETDOMAIN,dc=TLDORG
-objectClass: sambaDomain
-sambaDomainName: DOMNAME
-sambaSID: DOMSID
-sambaAlgorithmicRidBase: 1000
-structuralObjectClass: sambaDomain
-</screen>
-</example>
-
-<example id="sbehap-ldifpatb">
-<title>LDIF Pattern File Used to Pre-configure LDAP &smbmdash; Part B</title>
-<screen>
-dn: cn=domadmins,ou=Groups,dc=INETDOMAIN,dc=TLDORG
-objectClass: posixGroup
-objectClass: sambaGroupMapping
-gidNumber: 512
-cn: domadmins
-sambaSID: DOMSID-512
-sambaGroupType: 2
-displayName: Domain Admins
-description: Domain Administrators
-
-dn: cn=domguests,ou=Groups,dc=INETDOMAIN,dc=TLDORG
-objectClass: posixGroup
-objectClass: sambaGroupMapping
-gidNumber: 514
-cn: domguests
-sambaSID: DOMSID-514
-sambaGroupType: 2
-displayName: Domain Guests
-description: Domain Guests Users
-
-dn: cn=domusers,ou=Groups,dc=INETDOMAIN,dc=TLDORG
-objectClass: posixGroup
-objectClass: sambaGroupMapping
-gidNumber: 513
-cn: domusers
-sambaSID: DOMSID-513
-sambaGroupType: 2
-displayName: Domain Users
-description: Domain Users
-</screen>
-</example>
-
-</sect1>
-
-<sect1>
-<title>The LDAP Account Manager</title>
-
-<para>
-<indexterm><primary>LAM</primary></indexterm>
-<indexterm><primary>LDAP Account Manager</primary><see>LAM</see></indexterm>
-<indexterm><primary>PHP</primary></indexterm>
-<indexterm><primary>unencrypted</primary></indexterm>
-<indexterm><primary>SSL</primary></indexterm>
-<indexterm><primary>Posix</primary></indexterm>
-<indexterm><primary>accounts</primary><secondary>manage</secondary></indexterm>
-The LDAP Account Manager (LAM) is an application suite that has been written in PHP.
-LAM can be used with any Web server that has PHP4 support. It connects to the LDAP
-server either using unencrypted connections or via SSL/TLS. LAM can be used to manage
-Posix accounts as well as SambaSAMAccounts for users, groups, and Windows machines
-(hosts).
-</para>
-
-<para>
-LAM is available from the <ulink url="http://sourceforge.net/projects/lam/">LAM</ulink>
-home page and from its mirror sites. LAM has been released under the GNU GPL version 2.
-The current version of LAM is 0.4.9. Release of version 0.5 is expected in the third quarter
-of 2005.
-</para>
-
-<para>
-<indexterm><primary>PHP4</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>Perl</primary></indexterm>
-Requirements:
-</para>
-
-<itemizedlist>
- <listitem><para>A web server that will work with PHP4.</para></listitem>
- <listitem><para>PHP4 (available from the <ulink url="http://www.php.net/">PHP</ulink> home page.)</para></listitem>
- <listitem><para>OpenLDAP 2.0 or later.</para></listitem>
- <listitem><para>A Web browser that supports CSS.</para></listitem>
- <listitem><para>Perl.</para></listitem>
- <listitem><para>The gettext package.</para></listitem>
- <listitem><para>mcrypt + mhash (optional).</para></listitem>
- <listitem><para>It is also a good idea to install SSL support.</para></listitem>
-</itemizedlist>
-
-<para>
-LAM is a useful tool that provides a simple Web-based device that can be used to
-manage the contents of the LDAP directory to:
-<indexterm><primary>organizational units</primary></indexterm>
-<indexterm><primary>operating profiles</primary></indexterm>
-<indexterm><primary>account policies</primary></indexterm>
-</para>
-
-<itemizedlist>
- <listitem><para>Display user/group/host and Domain entries.</para></listitem>
- <listitem><para>Manage entries (Add/Delete/Edit).</para></listitem>
- <listitem><para>Filter and sort entries.</para></listitem>
- <listitem><para>Store and use multiple operating profiles.</para></listitem>
- <listitem><para>Edit organizational units (OUs).</para></listitem>
- <listitem><para>Upload accounts from a file.</para></listitem>
- <listitem><para>Is compatible with Samba-2.2.x and Samba-3.</para></listitem>
-</itemizedlist>
-
-<para>
-When correctly configured, LAM allows convenient management of UNIX (Posix) and Samba
-user, group, and windows domain member machine accounts.
-</para>
-
-<para>
-<indexterm><primary>default password</primary></indexterm>
-<indexterm><primary>secure connections</primary></indexterm>
-<indexterm><primary>LAM</primary></indexterm>
-<indexterm><primary>SSL</primary></indexterm>
-The default password is <quote>lam.</quote> It is highly recommended that you use only
-an SSL connection to your Web server for all remote operations involving LAM. If you
-want secure connections, you must configure your Apache Web server to permit connections
-to LAM using only SSL.
-</para>
-
-<procedure id="sbehap-laminst">
-<title>Apache Configuration Steps for LAM</title>
-
- <step><para>
- Extract the LAM package by untarring it as shown here:
-<screen>
-&rootprompt; tar xzf ldap-account-manager_0.4.9.tar.gz
-</screen>
- Alternatively, install the LAM DEB for your system using the following command:
-<screen>
-&rootprompt; dpkg -i ldap-account-manager_0.4.9.all.deb
-</screen>
- </para></step>
-
- <step><para>
- Copy the extracted files to the document root directory of your Web server.
- For example, on SUSE Linux Enterprise Server 9, copy to the
- <filename>/srv/www/htdocs</filename> directory.
- </para></step>
-
- <step><para>
- <indexterm><primary>file permissions</primary></indexterm>
- Set file permissions using the following commands:
-<screen>
-&rootprompt; chown -R wwwrun:www /srv/www/htdocs/lam
-&rootprompt; chmod 755 /srv/www/htdocs/lam/sess
-&rootprompt; chmod 755 /srv/www/htdocs/lam/tmp
-&rootprompt; chmod 755 /srv/www/htdocs/lam/config
-&rootprompt; chmod 755 /srv/www/htdocs/lam/lib/*pl
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>LAM</primary><secondary>configuration file</secondary></indexterm>
- Using your favorite editor create the following <filename>config.cfg</filename>
- LAM configuration file:
-<screen>
-&rootprompt; cd /srv/www/htdocs/lam/config
-&rootprompt; cp config.cfg_sample config.cfg
-&rootprompt; vi config.cfg
-</screen>
- <indexterm><primary>LAM</primary><secondary>profile</secondary></indexterm>
- <indexterm><primary>LAM</primary><secondary>wizard</secondary></indexterm>
- An example file is shown in <link linkend="lamcfg"/>.
- This is the minimum configuration that must be completed. The LAM profile
- file can be created using a convenient wizard that is part of the LAM
- configuration suite.
- </para></step>
-
- <step><para>
- Start your Web server then, using your Web browser, connect to
- <ulink url="http://localhost/lam">LAM</ulink> URL. Click on the
- the <parameter>Configuration Login</parameter> link then click on the
- Configuration Wizard link to begin creation of the default profile so that
- LAM can connect to your LDAP server. Alternately, copy the
- <filename>lam.conf_sample</filename> file to a file called
- <filename>lam.conf</filename> then, using your favorite editor,
- change the settings to match local site needs.
- </para></step>
-</procedure>
-
- <para>
- <indexterm><primary>pitfalls</primary></indexterm>
- An example of a working file is shown here in <link linkend="lamconf"/>.
- This file has been stripped of comments to keep the size small. The comments
- and help information provided in the profile file that the wizard creates
- is very useful and will help many administrators to avoid pitfalls.
- Your configuration file obviously reflects the configuration options that
- are preferred at your site.
- </para>
-
- <para>
- <indexterm><primary>LAM</primary><secondary>login screen</secondary></indexterm>
- It is important that your LDAP server is running at the time that LAM is
- being configured. This permits you to validate correct operation.
- An example of the LAM login screen is provided in <link linkend="lam-login"/>.
- </para>
-
- <figure id="lam-login">
- <title>The LDAP Account Manager Login Screen</title>
- <imagefile scale="50">lam-login</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>LAM</primary><secondary>configuration editor</secondary></indexterm>
- The LAM configuration editor has a number of options that must be managed correctly.
- An example of use of the LAM configuration editor is shown in <link linkend="lam-config"/>.
- It is important that you correctly set the minimum and maximum UID/GID values that are
- permitted for use at your site. The default values may not be compatible with a need to
- modify initial default account values for well-known Windows network users and groups.
- The best work-around is to temporarily set the minimum values to zero (0) to permit
- the initial settings to be made. Do not forget to reset these to sensible values before
- using LAM to add additional users and groups.
- </para>
-
- <figure id="lam-config">
- <title>The LDAP Account Manager Configuration Screen</title>
- <imagefile scale="50">lam-config</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>PDF</primary></indexterm>
- LAM has some nice, but unusual features. For example, one unexpected feature in most application
- screens permits the generation of a PDF file that lists configuration information. This is a well
- thought out facility. This option has been edited out of the following screen shots to conserve
- space.
- </para>
-
- <para>
- <indexterm><primary>LAM</primary><secondary>opening screen</secondary></indexterm>
- When you log onto LAM the opening screen drops you right into the user manager as shown in
- <link linkend="lam-user"/>. This is a logical action as it permits the most-needed facility
- to be used immediately. The editing of an existing user, as with the addition of a new user,
- is easy to follow and very clear in both layout and intent. It is a simple matter to edit
- generic settings, UNIX specific parameters, and then Samba account requirements. Each step
- involves clicking a button that intuitively drives you through the process. When you have
- finished editing simply press the <guimenu>Final</guimenu> button.
- </para>
-
- <figure id="lam-user">
- <title>The LDAP Account Manager User Edit Screen</title>
- <imagefile scale="50">lam-users</imagefile>
- </figure>
-
- <para>
- The edit screen for groups is shown in <link linkend="lam-group"/>. As with the edit screen
- for user accounts, group accounts may be rapidly dealt with. <link linkend="lam-group-mem"/>
- shows a sub-screen from the group editor that permits users to be assigned secondary group
- memberships.
- </para>
-
- <figure id="lam-group">
- <title>The LDAP Account Manager Group Edit Screen</title>
- <imagefile scale="50">lam-groups</imagefile>
- </figure>
-
- <figure id="lam-group-mem">
- <title>The LDAP Account Manager Group Membership Edit Screen</title>
- <imagefile scale="50">lam-group-members</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>smbldap-tools</primary></indexterm><indexterm><primary>scripts</primary></indexterm>
- The final screen presented here is one that you should not normally need to use. Host accounts will
- be automatically managed using the smbldap-tools scripts. This means that the screen <link linkend="lam-host"/>
- will, in most cases, not be used.
- </para>
-
- <figure id="lam-host">
- <title>The LDAP Account Manager Host Edit Screen</title>
- <imagefile scale="50">lam-hosts</imagefile>
- </figure>
-
- <para>
- One aspect of LAM that may annoy some users is the way it forces certain conventions on
- the administrator. For example, LAM does not permit the creation of Windows user and group
- accounts that contain spaces even though the underlying UNIX/Linux
- operating system may exhibit no problems with them. Given the propensity for using upper-case
- characters and spaces (particularly in the default Windows account names) this may cause
- some annoyance. For the rest, LAM is a very useful administrative tool.
- </para>
-
- <para>
- The next major release, LAM 0.5, will have fewer restrictions and support the latest Samba features
- (e.g., logon hours). The new plugin-based architecture also allows management of much more different
- account types like plain UNIX accounts. The upload can now handle groups and hosts, too. Another
- important point is the tree view which allows browsing and editing LDAP objects directly.
- </para>
-
-<example id="lamcfg">
-<title>Example LAM Configuration File &smbmdash; <filename>config.cfg</filename></title>
-<screen>
-# password to add/delete/rename configuration profiles
-password: not24get
-
-# default profile, without ".conf"
-default: lam
-</screen>
-</example>
-
-<example id="lamconf">
-<title>LAM Profile Control File &smbmdash; <filename>lam.conf</filename></title>
-<screen>
-ServerURL: ldap://massive.abmas.org:389
-Admins: cn=Manager,dc=abmas,dc=biz
-Passwd: not24get
-usersuffix: ou=People,dc=abmas,dc=biz
-groupsuffix: ou=Groups,dc=abmas,dc=biz
-hostsuffix: ou=Computers,dc=abmas,dc=biz
-domainsuffix: ou=Domains,dc=abmas,dc=biz
-MinUID: 0
-MaxUID: 65535
-MinGID: 0
-MaxGID: 65535
-MinMachine: 20000
-MaxMachine: 25000
-userlistAttributes: #uid;#givenName;#sn;#uidNumber;#gidNumber
-grouplistAttributes: #cn;#gidNumber;#memberUID;#description
-hostlistAttributes: #cn;#description;#uidNumber;#gidNumber
-maxlistentries: 30
-defaultLanguage: en_GB:ISO-8859-1:English (Great Britain)
-scriptPath:
-scriptServer:
-samba3: yes
-cachetimeout: 5
-pwdhash: SSHA
-</screen>
-</example>
-
-</sect1>
-
-<sect1>
- <title>IDEALX Management Console</title>
-
- <para>
- IMC (the IDEALX Mamagement Console) is a tool that can be used as the basis for a comprehensive
- web-based management interface for UNIX and Linux systems.
- </para>
-
- <para>
- The Samba toolset is the first console developped for IMC. It offers a simple and ergonomic
- interface for managing a Samba domain controler. The goal is to give Linux administrators who
- need to manage production Samba servers an effective, intuitive and consistent management
- experience. An IMC screenshot of the user management tool is shown in <link linkend="imcidealx"/>.
- </para>
-
- <figure id="imcidealx">
- <title>The IMC Samba User Account Screen</title>
- <imagefile scale="40">imc-usermanager2</imagefile>
- </figure>
-
- <para>
- IMC is built on a set of Perl modules. Most modules are standard CPAN modules. Some are bundled with IMC,
- but will soon to be hosted on the CPAN independently, like Struts4P, a port of Struts to the Perl language.
- </para>
-
- <para>
- For further information regarding IMC refer to the web <ulink url="http://imc.sourceforge.net/">site.</ulink>
- Prebuilt RPM packages are also <ulink url="http://imc.sourceforge.net/download.html">available.</ulink>
- </para>
-
-</sect1>
-
-<sect1 id="ch12-SUIDSGID">
- <title>Effect of Setting File and Directory SUID/SGID Permissions Explained</title>
-
- <indexterm><primary>SUID</primary></indexterm>
- <indexterm><primary>SGID</primary></indexterm>
- <para>
- The setting of the SUID/SGID bits on the file or directory permissions flag has particular
- consequences. If the file is executable and the SUID bit is set, it executes with the privilege
- of (with the UID of) the owner of the file. For example, if you are logged onto a system as
- a normal user (let's say as the user <constant>bobj</constant>), and you execute a file that is owned
- by the user <constant>root</constant> (uid = 0), and the file has the SUID bit set, then the file is
- executed as if you had logged in as the user <constant>root</constant> and then executed the file.
- The SUID bit effectively gives you (as <constant>bobj</constant>) administrative privilege for the
- use of that executable file.
- </para>
-
- <para>
- The setting of the SGID bit does precisely the same as the effect of the SUID bit, except that it
- applies the privilege to the UNIX group setting. In other words, the file executes with the force
- of capability of the group.
- </para>
-
- <para>
- When the SUID/SGID permissions are set on a directory, all files that are created within that directory
- are automatically given the ownership of the SUID user and the SGID group, as per the ownership
- of the directory in which the file is created. This means that the system level <command>create()</command>
- function executes with the SUID user and/or SGID group of the directory in which the file is
- created.
- </para>
-
- <para>
- If you want to obtain the SUID behavior, simply execute the following command:
-<screen>
-&rootprompt; chmod u+s file-or-directory
-</screen>
- To set the SGID properties on a file or a directory, execute this command:
-<screen>
-&rootprompt; chmod g+s file-or-directory
-</screen>
- And to set both SUID and SGID properties, execute the following:
-<screen>
-&rootprompt; chmod ug+s file-or-directory
-</screen>
- </para>
-
- <para>
- Let's consider the example of a directory <filename>/data/accounts</filename>. The permissions on this
- directory before setting both SUID and SGID on this directory are:
-<screen>
-&rootprompt; ls -al /data/accounts
-total 1
-drwxr-xr-x 10 root root 232 Dec 18 17:08 .
-drwxr-xr-x 21 root root 600 Dec 17 23:15 ..
-drwxrwxrwx 2 bobj Domain Users 48 Dec 18 17:08 accounts/
-drwx------ 2 root root 48 Jan 26 2002 lost+found
-</screen>
- In this example, if the user <constant>maryv</constant> creates a file, it is owned by her.
- If <constant>maryv</constant> has the primary group of <constant>Accounts</constant>, the file is
- owned by the group <constant>Accounts</constant>, as shown in this listing:
-<screen>
-&rootprompt; ls -al /data/accounts/maryvfile.txt
-drw-rw-r-- 2 maryv Accounts 12346 Dec 18 17:53
-</screen>
- </para>
-
- <para>
- Now you set the SUID and SGID and check the result as follows:
-<screen>
-&rootprompt; chmod ug+s /data/accounts
-&rootprompt; ls -al /data/accounts
-total 1
-drwxr-xr-x 10 root root 232 Dec 18 17:08 .
-drwxr-xr-x 21 root root 600 Dec 17 23:15 ..
-drwsrwsr-x 2 bobj Domain Users 48 Dec 18 17:08 accounts
-drwx------ 2 root root 48 Jan 26 2002 lost+found
-</screen>
- If <constant>maryv</constant> creates a file in this directory after this change has been made, the
- file is owned by the user <constant>bobj</constant>, and the group is set to the group
- <constant>Domain Users</constant>, as shown here:
-<screen>
-&rootprompt; chmod ug+s /data/accounts
-&rootprompt; ls -al /data/accounts/maryvfile.txt
-total 1
-drw-rw-r-- 2 bobj Domain Users 12346 Dec 18 18:11 maryvfile.txt
-</screen>
- </para>
-
-</sect1>
-
-<sect1 id="ch12dblck">
- <title>Shared Data Integrity</title>
-
- <para><indexterm>
- <primary>data integrity</primary>
- </indexterm><indexterm>
- <primary>multi-user</primary>
- <secondary>data access</secondary>
- </indexterm>
- The integrity of shared data is often viewed as a particularly emotional issue, especially where
- there are concurrent problems with multiuser data access. Contrary to the assertions of some who have
- experienced problems in either area, the cause has nothing to do with the phases of the moons of Jupiter.
- </para>
-
- <para>
- The solution to concurrent multiuser data access problems must consider three separate areas
- from which the problem may stem:<indexterm>
- <primary>locking</primary>
- <secondary>Application level</secondary>
- </indexterm><indexterm>
- <primary>locking</primary>
- <secondary>Client side</secondary>
- </indexterm><indexterm>
- <primary>locking</primary>
- <secondary>Server side</secondary>
- </indexterm>
- </para>
-
- <itemizedlist>
- <listitem><para>application-level locking controls</para></listitem>
- <listitem><para>client-side locking controls</para></listitem>
- <listitem><para>server-side locking controls</para></listitem>
- </itemizedlist>
-
- <para><indexterm>
- <primary>database applications</primary>
- </indexterm><indexterm>
- <primary>Microsoft Access</primary>
- </indexterm>
- Many database applications use some form of application-level access control. An example of one
- well-known application that uses application-level locking is Microsoft Access. Detailed guidance
- is provided here because this is the most common application for which problems have been reported.
- </para>
-
- <para><indexterm>
- <primary>Microsoft Excel</primary>
- </indexterm><indexterm>
- <primary>Act!</primary>
- </indexterm>
- Common applications that are affected by client- and server-side locking controls include MS
- Excel and Act!. Important locking guidance is provided here.
- </para>
-
-
- <sect2>
- <title>Microsoft Access</title>
-
- <para>
- The best advice that can be given is to carefully read the Microsoft knowledgebase articles that
- cover this area. Examples of relevant documents include:
- </para>
-
- <itemizedlist>
- <listitem><para>http://support.microsoft.com/default.aspx?scid=kb;en-us;208778</para></listitem>
- <listitem><para>http://support.microsoft.com/default.aspx?scid=kb;en-us;299373</para></listitem>
- </itemizedlist>
-
-
- <para><indexterm>
- <primary>multi-user</primary>
- <secondary>access</secondary>
- </indexterm><indexterm>
- <primary>exclusive open</primary>
- </indexterm>
- Make sure that your MS Access database file is configured for multiuser access (not set for
- exclusive open). Open MS Access on each client workstation, then set the following: <menuchoice>
- <guimenu>(Menu bar) Tools</guimenu><guimenu>Options</guimenu><guimenu>[tab] General</guimenu>
- </menuchoice>. Set network path to Default database folder: <filename>\\server\share\folder</filename>.
- </para>
-
- <para>
- You can configure MS Access file sharing behavior as follows: click <guimenu>[tab] Advanced</guimenu>.
- Set:<indexterm>
- <primary>record locking</primary>
- </indexterm>
- </para>
-
- <itemizedlist>
- <listitem><para>Default open mode: Shared</para></listitem>
- <listitem><para>Default Record Locking: Edited Record</para></listitem>
- <listitem><para>Open databases using record_level locking</para></listitem>
- </itemizedlist>
-
- <para><indexterm>
- <primary>MS Access</primary>
- <secondary>validate</secondary>
- </indexterm>
- You must now commit the changes so that they will take effect. To do so, click
- <guimenu>Apply</guimenu><guimenu>Ok</guimenu>. At this point, you should exit MS Access, restart
- it, and then validate that these settings have not changed.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Act! Database Sharing</title>
-
- <para><indexterm>
- <primary>ACT! database</primary>
- </indexterm><indexterm>
- <primary>data corruption</primary>
- </indexterm>
- Where the server sharing the ACT! database(s) is running Samba,or Windows NT, 200x, or XP, you
- must disable opportunistic locking on the server and all workstations. Failure to do so
- results in data corruption. This information is available from the Act! Web site
- knowledgebase articles
- <ulink url="http://itdomino.saleslogix.com/act.nsf/docid/1998223162925">1998223162925</ulink>
- as well as from article
- <ulink url="http://itdomino.saleslogix.com/act.nsf/docid/200110485036">200110485036</ulink>.
- </para>
-
- <para><indexterm>
- <primary>opportunistic locking</primary>
- </indexterm><indexterm>
- <primary>Act!Diag</primary>
- </indexterm>
- These documents clearly state that opportunistic locking must be disabled on both
- the server (Samba in the case we are interested in here), as well as on every workstation
- from which the centrally shared Act! database will be accessed. Act! provides
- a tool called <command>Act!Diag</command> that may be used to disable all workstation
- registry settings that may otherwise interfere with the operation of Act!
- Registered Act! users may download this utility from the Act! Web
- <ulink url="http://www.act.com/support/updates/index.cfm">site.</ulink>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Opportunistic Locking Controls</title>
-
- <para><indexterm>
- <primary>file caching</primary>
- </indexterm>
- Third-party Windows applications may not be compatible with the use of opportunistic file
- and record locking. For applications that are known not to be compatible,<footnote><para>Refer to
- the application manufacturer's installation guidelines and knowledge base for specific
- information regarding compatibility. It is often safe to assume that if the software
- manufacturer does not specifically mention incompatibilities with opportunistic file
- and record locking, or with Windows client file caching, the application is probably
- compatible with Windows (as well as Samba) default settings.</para></footnote> oplock
- support may need to be disabled both on the Samba server and on the Windows workstations.
- </para>
-
- <para><indexterm>
- <primary>cache</primary>
- </indexterm><indexterm>
- <primary>write lock</primary>
- </indexterm><indexterm>
- <primary>flush</primary>
- <secondary>cache memory</secondary>
- </indexterm>
- Oplocks enable a Windows client to cache parts of a file that are being
- edited. Another windows client may then request to open the file with the
- ability to write to it. The server will then ask the original workstation
- that had the file open with a write lock to release its lock. Before
- doing so, that workstation must flush the file from cache memory to the
- disk or network drive.
- </para>
-
- <para><indexterm>
- <primary>Oplocks</primary>
- <secondary>disabled</secondary>
- </indexterm>
- Disabling of Oplocks usage may require server and client changes.
- Oplocks may be disabled by file, by file pattern, on the share, or on the
- Samba server.
- </para>
-
- <para>
- The following are examples showing how Oplock support may be managed using
- Samba &smb.conf; file settings:
-<screen>
-By file: veto oplock files = myfile.mdb
-
-By Pattern: veto oplock files = /*.mdb/
-
-On the Share: oplocks = No
- level2 oplocks = No
-
-On the server:
-(in [global]) oplocks = No
- level2 oplocks = No
-</screen>
- </para>
-
- <para>
- The following registry entries on Microsoft Windows XP Professional, 2000 Professional, and Windows NT4
- workstation clients must be configured as shown here:
-<screen>
-REGEDIT4
-
-[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
- Services\LanmanServer\Parameters]
- "EnableOplocks"=dword:00000000
-
-[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
- Services\LanmanWorkstation\Parameters]
- "UseOpportunisticLocking"=dword:00000000
-</screen>
- </para>
-
- <para>
- Comprehensive coverage of file and record-locking controls is provided in TOSHARG2, Chapter 13.
- The information in that chapter was obtained from a wide variety of sources.
- </para>
-
- </sect2>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="primer">
- <title>Networking Primer</title>
-
- <para>
- You are about to use the equivalent of a microscope to look at the information
- that runs through the veins of a Windows network. We do more to observe the information than
- to interrogate it. When you are done with this primer, you should have a good understanding
- of the types of information that flow over the network. Do not worry, this is not
- a biology lesson. We won't lose you in unnecessary detail. Think to yourself, <quote>This
- is easy,</quote> then tackle each exercise without fear.
- </para>
-
- <para>
- Samba can be configured with a minimum of complexity. Simplicity should be mastered
- before you get too deeply into complexities. Let's get moving: we have work to do.
- </para>
-
-<sect1>
- <title>Requirements and Notes</title>
- <para>
- Successful completion of this primer requires two Microsoft Windows 9x/Me Workstations
- as well as two Microsoft Windows XP Professional Workstations, each equipped with an Ethernet
- card connected using a hub. Also required is one additional server (either Windows
- NT4 Server, Windows 2000 Server, or a Samba on UNIX/Linux server) running a network
- sniffer and analysis application (Wireshark is a good choice). All work should be undertaken
- on a quiet network where there is no other traffic. It is best to use a dedicated hub
- with only the machines under test connected at the time of the exercises.
- </para>
-
- <para><indexterm>
- <primary>Wireshark</primary>
- </indexterm>
- Wireshark (formerly Ethereal) has become the network protocol analyzer of choice for many network administrators.
- You may find more information regarding this tool from the
- <ulink url="http://www.wireshark.org">Wireshark</ulink> Web site. Wireshark installation
- files for Windows may be obtained from the Wireshark Web site. Wireshark is provided with
- SUSE and Red Hat Linux distributions, as well as with many other Linux distributions. It may
- not be installed on your system by default. If it is not installed, you may also need
- to install the <command>libpcap</command> software before you can install or use Wireshark.
- Please refer to the instructions for your operating system or to the Wireshark Web site
- for information regarding the installation and operation of Wireshark.
- </para>
-
- <para>
- To obtain <command>Wireshark</command> for your system, please visit the Wireshark
- <ulink url="http://www.wireshark.org/download.html">download site</ulink>.
- </para>
-
- <note><para>
- The successful completion of this chapter requires that you capture network traffic
- using <command>Wireshark</command>. It is recommended that you use a hub, not an
- Ethernet switch. It is necessary for the device used to act as a repeater, not as a
- filter. Ethernet switches may filter out traffic that is not directed at the machine
- that is used to monitor traffic; this would not allow you to complete the projects.
- </para></note>
-
- <para>
- <indexterm><primary>network</primary><secondary>captures</secondary></indexterm>
- Do not worry too much if you do not have access to all this equipment; network captures
- from the exercises are provided on the enclosed CD-ROM. This makes it possible to dive directly
- into the analytical part of the exercises if you so desire.
- </para>
-
- <para><indexterm>
- <primary>network</primary>
- <secondary>sniffer</secondary>
- </indexterm><indexterm>
- <primary>protocol analysis</primary>
- </indexterm>
- Please do not be alarmed at the use of a high-powered analysis tool (Wireshark) in this
- primer. We expose you only to a minimum of detail necessary to complete
- the exercises. If you choose to use any other network sniffer and protocol
- analysis tool, be advised that it may not allow you to examine the contents of
- recently added security protocols used by Windows 200x/XP.
- </para>
-
- <para>
- You could just skim through the exercises and try to absorb the key points made.
- The exercises provide all the information necessary to convince the die-hard network
- engineer. You possibly do not require so much convincing and may just want to move on,
- in which case you should at least read <link linkend="chap01conc"/>.
- </para>
-
- <para>
- <link linkend="chap01qa"/> also provides useful information
- that may help you to avoid significantly time-consuming networking problems.
- </para>
-</sect1>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- The purpose of this chapter is to create familiarity with key aspects of Microsoft Windows
- network computing. If you want a solid technical grounding, do not gloss over these exercises.
- The points covered are recurrent issues on the Samba mailing lists.
- </para>
-
- <para><indexterm>
- <primary>network</primary>
- <secondary>broadcast</secondary>
- </indexterm>
- You can see from these exercises that Windows networking involves quite a lot of network
- broadcast traffic. You can look into the contents of some packets, but only to see
- some particular information that the Windows client sends to a server in the course of
- establishing a network connection.
- </para>
-
- <para>
- To many people, browsing is everything that happens when one uses Microsoft Internet Explorer.
- It is only when you start looking at network traffic and noting the protocols
- and types of information that are used that you can begin to appreciate the complexities of
- Windows networking and, more importantly, what needs to be configured so that it can work.
- Detailed information regarding browsing is provided in the recommended
- preparatory reading.
- </para>
-
- <para>
- Recommended preparatory reading: <emphasis>The Official Samba HOWTO and Reference Guide, Second
- Edition</emphasis> (TOSHARG2) Chapter 9, <quote>Network Browsing,</quote> and Chapter 3,
- <quote>Server Types and Security Modes.</quote>
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para><indexterm>
- <primary>browsing</primary>
- </indexterm>
- You are about to witness how Microsoft Windows computer networking functions. The
- exercises step through identification of how a client machine establishes a
- connection to a remote Windows server. You observe how Windows machines find
- each other (i.e., how browsing works) and how the two key types of user identification
- (share mode security and user mode security) are affected.
- </para>
-
- <para><indexterm>
- <primary>network</primary>
- <secondary>analyzer</secondary>
- </indexterm>
- The networking protocols used by MS Windows networking when working with Samba
- use TCP/IP as the transport protocol. The protocols that are specific to Windows
- networking are encapsulated in TCP/IP. The network analyzer we use (Wireshark)
- is able to show you the contents of the TCP/IP packets (or messages).
- </para>
-
- <procedure id="chap01tasks">
- <title>Diagnostic Tasks</title>
-
- <step><para><indexterm>
- <primary>network</primary>
- <secondary>trace</secondary>
- </indexterm><indexterm>
- <primary>host announcement</primary>
- </indexterm><indexterm>
- <primary>name resolution</primary>
- </indexterm>
- Examine network traces to witness SMB broadcasts, host announcements,
- and name resolution processes.
- </para></step>
-
- <step><para>
- Examine network traces to witness how share mode security functions.
- </para></step>
-
- <step><para>
- Examine network traces to witness the use of user mode security.
- </para></step>
-
- <step><para>
- Review traces of network logons for a Windows 9x/Me client as well as
- a domain logon for a Windows XP Professional client.
- </para></step>
- </procedure>
-
- </sect2>
-</sect1>
-
-<sect1>
- <title>Exercises</title>
-
- <para>
- <indexterm><primary>wireshark</primary></indexterm>
- You are embarking on a course of discovery. The first part of the exercise requires
- two MS Windows 9x/Me systems. We called one machine <constant>WINEPRESSME</constant> and the
- other <constant>MILGATE98</constant>. Each needs an IP address; we used <literal>10.1.1.10</literal>
- and <literal>10.1.1.11</literal>. The test machines need to be networked via a <emphasis>hub</emphasis>. A UNIX/Linux
- machine is required to run <command>Wireshark</command> to enable the network activity to be captured.
- It is important that the machine from which network activity is captured must not interfere with
- the operation of the Windows workstations. It is helpful for this machine to be passive (does not
- send broadcast information) to the network.
- </para>
-
- <para>
- For these exercises, our test environment consisted of a SUSE 9.2 Professional Linux Workstation running
- VMWare 4.5. The following VMWare images were prepared:
- </para>
-
- <itemizedlist>
- <listitem><para>Windows 98 &smbmdash; name: MILGATE98</para></listitem>
- <listitem><para>Windows Me &smbmdash; name: WINEPRESSME</para></listitem>
- <listitem><para>Windows XP Professional &smbmdash; name: LightrayXP</para></listitem>
- <listitem><para>Samba-3.0.20 running on a SUSE Enterprise Linux 9</para></listitem>
- </itemizedlist>
-
- <para>
- Choose a workgroup name (MIDEARTH) for each exercise.
- </para>
-
- <para>
- <indexterm><primary>ethereal</primary></indexterm>
- The network captures provided on the CD-ROM included with this book were captured using <constant>Ethereal</constant>
- version <literal>0.10.6</literal>. A later version suffices without problems (i.e. you should be using Wireshark), but an earlier version may not
- expose all the information needed. Each capture file has been decoded and listed as a trace file. A summary of all
- packets has also been included. This makes it possible for you to do all the studying you like without the need to
- perform the time-consuming equipment configuration and test work. This is a good time to point out that the value
- that can be derived from this book really does warrant your taking sufficient time to practice each exercise with
- care and attention to detail.
- </para>
-
- <sect2>
- <title>Single-Machine Broadcast Activity</title>
-
- <para>
- In this section, we start a single Windows 9x/Me machine, then monitor network activity for 30 minutes.
- </para>
-
- <procedure>
- <title>Monitoring Windows 9x Steps</title>
-
- <step><para>
- Start the machine from which network activity will be monitored (using <command>Wireshark</command>).
- Launch <command>Wireshark</command>, click
- <menuchoice>
- <guimenu>Capture</guimenu>
- <guimenuitem>Start</guimenuitem>
- </menuchoice>.
- </para>
-
- <para>
- Click the following:
- <orderedlist>
- <listitem><para>Update list of packets in real time</para></listitem>
- <listitem><para>Automatic scrolling in live capture</para></listitem>
- <listitem><para>Enable MAC name resolution</para></listitem>
- <listitem><para>Enable network name resolution</para></listitem>
- <listitem><para>Enable transport name resolution</para></listitem>
- </orderedlist>
- Click <guibutton>OK</guibutton>.
- </para></step>
-
- <step><para>
- Start the Windows 9x/Me machine to be monitored. Let it run for a full 30 minutes. While monitoring,
- do not press any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes.
- </para></step>
-
- <step><para>
- At the conclusion of 30 minutes, stop the capture. Save the capture to a file so you can go back to it later.
- Leave this machine running in preparation for the task in <link linkend="secondmachine"/>.
- </para></step>
-
- <step><para>
- Analyze the capture. Identify each discrete message type that was captured. Note what transport protocol
- was used. Identify the timing between messages of identical types.
- </para></step>
-
- </procedure>
-
- <sect3>
- <title>Findings</title>
-
- <para>
- The summary of the first 10 minutes of the packet capture should look like <link linkend="pktcap01"/>.
- A screenshot of a later stage of the same capture is shown in <link linkend="pktcap02"/>.
- </para>
-
- <figure id="pktcap01">
- <title>Windows Me &smbmdash; Broadcasts &smbmdash; The First 10 Minutes</title>
- <imagefile scale="40">WINREPRESSME-Capture</imagefile>
- </figure>
-
- <figure id="pktcap02">
- <title>Windows Me &smbmdash; Later Broadcast Sample</title>
- <imagefile scale="42">WINREPRESSME-Capture2</imagefile>
- </figure>
-
- <para><indexterm>
- <primary>Local Master Browser</primary>
- <see>LMB</see>
- </indexterm><indexterm>
- <primary>LMB</primary>
- </indexterm>
- Broadcast messages observed are shown in <link linkend="capsstats01"/>.
- Actual observations vary a little, but not by much.
- Early in the startup process, the Windows Me machine broadcasts its name for two reasons:
- first to ensure that its name would not result in a name clash, and second to establish its
- presence with the Local Master Browser (LMB).
- </para>
-
- <table id="capsstats01">
- <title>Windows Me &smbmdash; Startup Broadcast Capture Statistics</title>
- <tgroup cols="4">
- <colspec align="left" colwidth="3*"/>
- <colspec align="center"/>
- <colspec align="center"/>
- <colspec align="left" colwidth="3*"/>
- <thead>
- <row>
- <entry>Message</entry>
- <entry>Type</entry>
- <entry>Num</entry>
- <entry>Notes</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>WINEPRESSME<00></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.6 sec apart</entry>
- </row>
- <row>
- <entry>WINEPRESSME<03></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.6 sec apart</entry>
- </row>
- <row>
- <entry>WINEPRESSME<20></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<00></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<1d></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<1e></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<1b></entry>
- <entry>Qry</entry>
- <entry>84</entry>
- <entry>300 sec apart at stable operation</entry>
- </row>
- <row>
- <entry>__MSBROWSE__</entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>Registered after winning election to Browse Master</entry>
- </row>
- <row>
- <entry>JHT<03></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 x 2. This is the name of the user that logged onto Windows</entry>
- </row>
- <row>
- <entry>Host Announcement WINEPRESSME</entry>
- <entry>Ann</entry>
- <entry>2</entry>
- <entry>Observed at 10 sec</entry>
- </row>
- <row>
- <entry>Domain/Workgroup Announcement MIDEARTH</entry>
- <entry>Ann</entry>
- <entry>18</entry>
- <entry>300 sec apart at stable operation</entry>
- </row>
- <row>
- <entry>Local Master Announcement WINEPRESSME</entry>
- <entry>Ann</entry>
- <entry>18</entry>
- <entry>300 sec apart at stable operation</entry>
- </row>
- <row>
- <entry>Get Backup List Request</entry>
- <entry>Qry</entry>
- <entry>12</entry>
- <entry>6 x 2 early in startup, 0.5 sec apart</entry>
- </row>
- <row>
- <entry>Browser Election Request</entry>
- <entry>Ann</entry>
- <entry>10</entry>
- <entry>5 x 2 early in startup</entry>
- </row>
- <row>
- <entry>Request Announcement WINEPRESSME</entry>
- <entry>Ann</entry>
- <entry>4</entry>
- <entry>Early in startup</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para><indexterm>
- <primary>election</primary>
- </indexterm><indexterm>
- <primary>browse master</primary>
- </indexterm>
- From the packet trace, it should be noted that no messages were propagated over TCP/IP;
- all messages employed UDP/IP. When steady-state operation has been achieved, there is a cycle
- of various announcements, re-election of a browse master, and name queries. These create
- the symphony of announcements by which network browsing is made possible.
- </para>
-
- <para><indexterm>
- <primary>CIFS</primary>
- </indexterm>
- For detailed information regarding the precise behavior of the CIFS/SMB protocols,
- refer to the book <quote>Implementing CIFS: The Common Internet File System,</quote>
- by Christopher Hertel, (Prentice Hall PTR, ISBN: 013047116X).
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2 id="secondmachine">
- <title>Second Machine Startup Broadcast Interaction</title>
-
- <para>
- At this time, the machine you used to capture the single-system startup trace should still be running.
- The objective of this task is to identify the interaction of two machines in respect to broadcast activity.
- </para>
-
- <procedure>
- <title>Monitoring of Second Machine Activity</title>
-
- <step><para>
- On the machine from which network activity will be monitored (using <command>Wireshark</command>),
- launch <command>Wireshark</command> and click
- <menuchoice>
- <guimenu>Capture</guimenu>
- <guimenuitem>Start</guimenuitem>
- </menuchoice>.
- </para>
-
- <para>
- Click:
- <orderedlist>
- <listitem><para>Update list of packets in real time</para></listitem>
- <listitem><para>Automatic scrolling in live capture</para></listitem>
- <listitem><para>Enable MAC name resolution</para></listitem>
- <listitem><para>Enable network name resolution</para></listitem>
- <listitem><para>Enable transport name resolution</para></listitem>
- </orderedlist>
- Click <guibutton>OK</guibutton>.
- </para></step>
-
- <step><para>
- Start the second Windows 9x/Me machine. Let it run for 15 to 20 minutes. While monitoring, do not press
- any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes.
- </para></step>
-
- <step><para>
- At the conclusion of the capture time, stop the capture. Be sure to save the captured data so you
- can examine the network data capture again at a later date should that be necessary.
- </para></step>
-
- <step><para>
- Analyze the capture trace, taking note of the transport protocols used, the types of messages observed,
- and what interaction took place between the two machines. Leave both machines running for the next task.
- </para></step>
- </procedure>
-
- <sect3>
- <title>Findings</title>
-
- <para>
- <link linkend="capsstats02"/> summarizes capture statistics observed. As in the previous case,
- all announcements used UDP/IP broadcasts. Also, as was observed with the last example, the second
- Windows 9x/Me machine broadcasts its name on startup to ensure that there exists no name clash
- (i.e., the name is already registered by another machine) on the network segment. Those wishing
- to explore the inner details of the precise mechanism of how this functions should refer to
- <quote>Implementing CIFS: The Common Internet File System.</quote>
- </para>
-
- <table id="capsstats02">
- <title>Second Machine (Windows 98) &smbmdash; Capture Statistics</title>
- <tgroup cols="4">
- <colspec align="left" colwidth="3*"/>
- <colspec align="center"/>
- <colspec align="center"/>
- <colspec align="left" colwidth="3*"/>
- <thead>
- <row>
- <entry>Message</entry>
- <entry>Type</entry>
- <entry>Num</entry>
- <entry>Notes</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>MILGATE98<00></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.6 sec apart</entry>
- </row>
- <row>
- <entry>MILGATE98<03></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.6 sec apart</entry>
- </row>
- <row>
- <entry>MILGATE98<20></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<00></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<1d></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<1e></entry>
- <entry>Reg</entry>
- <entry>8</entry>
- <entry>4 lots of 2, 0.75 sec apart</entry>
- </row>
- <row>
- <entry>MIDEARTH<1b></entry>
- <entry>Qry</entry>
- <entry>18</entry>
- <entry>900 sec apart at stable operation</entry>
- </row>
- <row>
- <entry>JHT<03></entry>
- <entry>Reg</entry>
- <entry>2</entry>
- <entry>This is the name of the user that logged onto Windows</entry>
- </row>
- <row>
- <entry>Host Announcement MILGATE98</entry>
- <entry>Ann</entry>
- <entry>14</entry>
- <entry>Every 120 sec</entry>
- </row>
- <row>
- <entry>Domain/Workgroup Announcement MIDEARTH</entry>
- <entry>Ann</entry>
- <entry>6</entry>
- <entry>900 sec apart at stable operation</entry>
- </row>
- <row>
- <entry>Local Master Announcement WINEPRESSME</entry>
- <entry>Ann</entry>
- <entry>6</entry>
- <entry>Insufficient detail to determine frequency</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- <indexterm><primary>host announcement</primary></indexterm>
- <indexterm><primary>Local Master Announcement</primary></indexterm>
- <indexterm><primary>Workgroup Announcement</primary></indexterm>
- Observation of the contents of Host Announcements, Domain/Workgroup Announcements,
- and Local Master Announcements is instructive. These messages convey a significant
- level of detail regarding the nature of each machine that is on the network. An example
- dissection of a Host Announcement is given in <link linkend="hostannounce"/>.
- </para>
-
-
- <figure id="hostannounce">
- <title>Typical Windows 9x/Me Host Announcement</title>
- <imagefile scale="41">HostAnnouncment</imagefile>
- </figure>
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Simple Windows Client Connection Characteristics</title>
-
- <para>
- The purpose of this exercise is to discover how Microsoft Windows clients create (establish)
- connections with remote servers. The methodology involves analysis of a key aspect of how
- Windows clients access remote servers: the session setup protocol.
- </para>
-
- <procedure>
- <title>Client Connection Exploration Steps</title>
-
- <step><para>
- Configure a Windows 9x/Me machine (MILGATE98) with a share called <constant>Stuff</constant>.
- Create a <parameter>Full Access</parameter> control password on this share.
- </para></step>
-
- <step><para>
- Configure another Windows 9x/Me machine (WINEPRESSME) as a client. Make sure that it exports
- no shared resources.
- </para></step>
-
- <step><para>
- Start both Windows 9x/Me machines and allow them to stabilize for 10 minutes. Log on to both
- machines using a user name (JHT) of your choice. Wait approximately 2 minutes before proceeding.
- </para></step>
-
- <step><para>
- Start Wireshark (or the network sniffer of your choice).
- </para></step>
-
- <step><para>
- From the WINEPRESSME machine, right-click <guimenu>Network Neighborhood</guimenu>, select
- <guimenuitem>Explore</guimenuitem>, select
- <menuchoice>
- <guimenuitem>My Network Places</guimenuitem>
- <guimenuitem>Entire Network</guimenuitem>
- <guimenuitem>MIDEARTH</guimenuitem>
- <guimenuitem>MILGATE98</guimenuitem>
- <guimenuitem>Stuff</guimenuitem>
- </menuchoice>.
- Enter the password you set for the <constant>Full Control</constant> mode for the
- <constant>Stuff</constant> share.
- </para></step>
-
- <step><para>
- When the share called <constant>Stuff</constant> is being displayed, stop the capture.
- Save the captured data in case it is needed for later analysis.
- </para></step>
-
- <step><para>
- <indexterm><primary>session setup</primary></indexterm>
- From the top of the packets captured, scan down to locate the first packet that has
- interpreted as <constant>Session Setup AndX, User: anonymous; Tree Connect AndX,
- Path: \\MILGATE98\IPC$</constant>.
- </para></step>
-
- <step><para><indexterm>
- <primary>Session Setup</primary>
- </indexterm><indexterm>
- <primary>Tree Connect</primary>
- </indexterm>
- In the dissection (analysis) panel, expand the <constant>SMB, Session Setup AndX Request,
- and Tree Connect AndX Request</constant>. Examine both operations. Identify the name of
- the user Account and what password was used. The Account name should be empty.
- This is a <constant>NULL</constant> session setup packet.
- </para></step>
-
- <step><para>
- Return to the packet capture sequence. There will be a number of packets that have been
- decoded of the type <constant>Session Setup AndX</constant>. Locate the last such packet
- that was targeted at the <constant>\\MILGATE98\IPC$</constant> service.
- </para></step>
-
- <step><para>
- <indexterm><primary>password length</primary></indexterm>
- <indexterm><primary>User Mode</primary></indexterm>
- Dissect this packet as per the previous one. This packet should have a password length
- of 24 (characters) and should have a password field, the contents of which is a
- long hexadecimal number. Observe the name in the Account field. This is a User Mode
- session setup packet.
- </para></step>
- </procedure>
-
- <sect3>
- <title>Findings and Comments</title>
-
- <para>
- <indexterm><primary>IPC$</primary></indexterm>
- The <constant>IPC$</constant> share serves a vital purpose<footnote><para>TOSHARG2, Sect 4.5.1</para></footnote>
- in SMB/CIFS-based networking. A Windows client connects to this resource to obtain the list of
- resources that are available on the server. The server responds with the shares and print queues that
- are available. In most but not all cases, the connection is made with a <constant>NULL</constant>
- username and a <constant>NULL</constant> password.
- </para>
-
- <para>
- <indexterm><primary>account credentials</primary></indexterm>
- The two packets examined are material evidence of how Windows clients may
- interoperate with Samba. Samba requires every connection setup to be authenticated using
- valid UNIX account credentials (UID/GID). This means that even a <constant>NULL</constant>
- session setup can be established only by automatically mapping it to a valid UNIX
- account.
- </para>
-
- <para>
- <indexterm><primary>NULL session</primary></indexterm><indexterm>
- <primary>guest account</primary>
- </indexterm>
- <indexterm><primary>nobody</primary></indexterm>
- Samba has a special name for the <constant>NULL</constant>, or empty, user account:
- it calls it the <smbconfoption name="guest account"/>. The
- default value of this parameter is <constant>nobody</constant>; however, this can be
- changed to map the function of the guest account to any other UNIX identity. Some
- UNIX administrators prefer to map this account to the system default anonymous
- FTP account. A sample NULL Session Setup AndX packet dissection is shown in
- <link linkend="nullconnect"/>.
- </para>
-
- <figure id="nullconnect">
- <title>Typical Windows 9x/Me NULL SessionSetUp AndX Request</title>
-
- <imagefile scale="41">NullConnect</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>nobody</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>guest account</primary></indexterm>
- When a UNIX/Linux system does not have a <constant>nobody</constant> user account
- (<filename>/etc/passwd</filename>), the operation of the <constant>NULL</constant>
- account cannot validate and thus connections that utilize the guest account
- fail. This breaks all ability to browse the Samba server and is a common
- problem reported on the Samba mailing list. A sample User Mode session setup AndX
- is shown in <link linkend="userconnect"/>.
- </para>
-
- <figure id="userconnect">
- <title>Typical Windows 9x/Me User SessionSetUp AndX Request</title>
- <imagefile scale="41">UserConnect</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>encrypted</primary></indexterm>
- The User Mode connection packet contains the account name and the domain name.
- The password is provided in Microsoft encrypted form, and its length is shown
- as 24 characters. This is the length of Microsoft encrypted passwords.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Windows 200x/XP Client Interaction with Samba</title>
-
- <para>
- By now you may be asking, <quote>Why did you choose to work with Windows 9x/Me?</quote>
- </para>
-
- <para>
- First, we want to demonstrate the simple case. This book is not intended to be a detailed treatise
- on the Windows networking protocols, but rather to provide prescriptive guidance for deployment of Samba.
- Second, by starting out with the simple protocol, it can be demonstrated that the more complex case mostly
- follows the same principles.
- </para>
-
- <para>
- The following exercise demonstrates the case that even MS Windows XP Professional with up-to-date service
- updates also uses the <constant>NULL</constant> account, as well as user accounts. Simply follow the procedure
- to complete this exercise.
- </para>
-
- <para>
- To complete this exercise, you need a Windows XP Professional client that has been configured as
- a domain member of either a Samba-controlled domain or a Windows NT4 or 200x Active Directory domain.
- Here we do not provide details for how to configure this, as full coverage is provided earlier in this book.
- </para>
-
- <procedure>
- <title>Steps to Explore Windows XP Pro Connection Set-up</title>
-
- <step><para>
- Start your domain controller. Also, start the Wireshark monitoring machine, launch Wireshark,
- and then wait for the next step to complete.
- </para></step>
-
- <step><para>
- Start the Windows XP Client and wait 5 minutes before proceeding.
- </para></step>
-
- <step><para>
- On the machine from which network activity will be monitored (using <command>Wireshark</command>),
- launch <command>Wireshark</command> and click
- <menuchoice>
- <guimenu>Capture</guimenu>
- <guimenuitem>Start</guimenuitem>
- </menuchoice>.
- </para>
-
- <para>
- Click:
- <orderedlist>
- <listitem><para>Update list of packets in real time</para></listitem>
- <listitem><para>Automatic scrolling in live capture</para></listitem>
- <listitem><para>Enable MAC name resolution</para></listitem>
- <listitem><para>Enable network name resolution</para></listitem>
- <listitem><para>Enable transport name resolution</para></listitem>
- </orderedlist>
- Click <guibutton>OK</guibutton>.
- </para></step>
-
- <step><para>
- On the Windows XP Professional client, press <guimenu>Ctrl-Alt-Delete</guimenu> to bring
- up the domain logon screen. Log in using valid credentials for a domain user account.
- </para></step>
-
- <step><para>
- Now proceed to connect to the domain controller as follows:
- <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>(right-click) My Network Places</guimenuitem>
- <guimenuitem>Explore</guimenuitem>
- <guimenuitem>{Left Panel} [+] Entire Network</guimenuitem>
- <guimenuitem>{Left Panel} [+] Microsoft Windows Network</guimenuitem>
- <guimenuitem>{Left Panel} [+] Midearth</guimenuitem>
- <guimenuitem>{Left Panel} [+] Frodo</guimenuitem>
- <guimenuitem>{Left Panel} [+] data</guimenuitem>
- </menuchoice>. Close the explorer window.
- </para>
-
- <para>
- In this step, our domain name is <constant>Midearth</constant>, the domain controller is called
- <constant>Frodo</constant>, and we have connected to a share called <constant>data</constant>.
- </para></step>
-
- <step><para>
- Stop the capture on the <command>Wireshark</command> monitoring machine. Be sure to save the captured data
- to a file so that you can refer to it again later.
- </para></step>
-
- <step><para>
- If desired, the Windows XP Professional client and the domain controller are no longer needed for exercises
- in this chapter.
- </para></step>
-
- <step><para>
- <indexterm><primary>NTLMSSP_AUTH</primary></indexterm>
- <indexterm><primary>session setup</primary></indexterm>
- From the top of the packets captured, scan down to locate the first packet that has
- interpreted as <constant>Session Setup AndX Request, NTLMSSP_AUTH</constant>.
- </para></step>
-
- <step><para>
- <indexterm><primary>GSS-API</primary></indexterm>
- <indexterm><primary>SPNEGO</primary></indexterm>
- <indexterm><primary>NTLMSSP</primary></indexterm>
- In the dissection (analysis) panel, expand the <constant>SMB, Session Setup AndX Request</constant>.
- Expand the packet decode information, beginning at the <constant>Security Blob:</constant>
- entry. Expand the <constant>GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</constant>
- keys. This should reveal that this is a <constant>NULL</constant> session setup packet.
- The <constant>User name: NULL</constant> so indicates. An example decode is shown in
- <link linkend="XPCap01"/>.
- </para></step>
-
- <step><para>
- Return to the packet capture sequence. There will be a number of packets that have been
- decoded of the type <constant>Session Setup AndX Request</constant>. Click the last such packet that
- has been decoded as <constant>Session Setup AndX Request, NTLMSSP_AUTH</constant>.
- </para></step>
-
- <step><para>
- <indexterm><primary>encrypted password</primary></indexterm>
- In the dissection (analysis) panel, expand the <constant>SMB, Session Setup AndX Request</constant>.
- Expand the packet decode information, beginning at the <constant>Security Blob:</constant>
- entry. Expand the <constant>GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</constant>
- keys. This should reveal that this is a <constant>User Mode</constant> session setup packet.
- The <constant>User name: jht</constant> so indicates. An example decode is shown in
- <link linkend="XPCap02"/>. In this case the user name was <constant>jht</constant>. This packet
- decode includes the <constant>Lan Manager Response:</constant> and the <constant>NTLM Response:</constant>.
- The values of these two parameters are the Microsoft encrypted password hashes: respectively, the LanMan
- password and then the NT (case-preserving) password hash.
- </para></step>
-
- <step><para>
- <indexterm><primary>password length</primary></indexterm>
- <indexterm><primary>User Mode</primary></indexterm>
- The passwords are 24-character hexadecimal numbers. This packet confirms that this is a User Mode
- session setup packet.
- </para></step>
-
- </procedure>
-
- <figure id="XPCap01">
- <title>Typical Windows XP NULL Session Setup AndX Request</title>
- <imagefile scale="50">WindowsXP-NullConnection</imagefile>
- </figure>
-
- <figure id="XPCap02">
- <title>Typical Windows XP User Session Setup AndX Request</title>
- <imagefile scale="50">WindowsXP-UserConnection</imagefile>
- </figure>
-
- <sect3>
- <title>Discussion</title>
-
- <para><indexterm>
- <primary>NULL-Session</primary>
- </indexterm>
- This exercise demonstrates that, while the specific protocol for the Session Setup AndX is handled
- in a more sophisticated manner by recent MS Windows clients, the underlying rules or principles
- remain the same. Thus it is demonstrated that MS Windows XP Professional clients still use a
- <constant>NULL-Session</constant> connection to query and locate resources on an advanced network
- technology server (one using Windows NT4/200x or Samba). It also demonstrates that an authenticated
- connection must be made before resources can be used.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Conclusions to Exercises</title>
-
- <para>
- In summary, the following points have been established in this chapter:
- </para>
-
- <itemizedlist>
- <listitem><para>
- When NetBIOS over TCP/IP protocols are enabled, MS Windows networking employs broadcast-oriented messaging protocols to provide knowledge of network services.
- </para></listitem>
-
- <listitem><para>
- Network browsing protocols query information stored on browse masters that manage
- information provided by NetBIOS Name Registrations and by way of ongoing host
- announcements and workgroup announcements.
- </para></listitem>
-
- <listitem><para>
- All Samba servers must be configured with a mechanism for mapping the <constant>NULL-Session</constant>
- to a valid but nonprivileged UNIX system account.
- </para></listitem>
-
- <listitem><para>
- The use of Microsoft encrypted passwords is built right into the fabric of Windows
- networking operations. Such passwords cannot be provided from the UNIX <filename>/etc/passwd</filename>
- database and thus must be stored elsewhere on the UNIX system in a manner that Samba can
- use. Samba-2.x permitted such encrypted passwords to be stored in the <constant>smbpasswd</constant>
- file or in an LDAP database. Samba permits use of multiple <parameter>passdb backend</parameter>
- databases in concurrent deployment. Refer to <emphasis>TOSHARG2</emphasis>, Chapter 10, <quote>Account Information Databases.</quote>
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
-</sect1>
-
-<sect1 id="chap01conc">
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>guest account</primary></indexterm>
- The exercises demonstrate the use of the <constant>guest</constant> account, the way that
- MS Windows clients and servers resolve computer names to a TCP/IP address, and how connections
- between a client and a server are established.
- </para>
-
- <para>
- Those wishing background information regarding NetBIOS name types should refer to
- the Microsoft knowledgebase article
- <ulink url="http://support.microsoft.com/support/kb/articles/Q102/78/8.asp">Q102878.</ulink>
- </para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- <indexterm><primary>guest account</primary></indexterm>
- Network browsing involves SMB broadcast announcements, SMB enumeration requests,
- connections to the <constant>IPC$</constant> share, share enumerations, and SMB connection
- setup processes. The use of anonymous connections to a Samba server involve the use of
- the <parameter>guest account</parameter> that must map to a valid UNIX UID.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1 id="chap01qa">
- <title>Questions and Answers</title>
-
- <para>
- The questions and answers given in this section are designed to highlight important aspects of Microsoft
- Windows networking.
- </para>
-
- <qandaset defaultlabel="chap01qa" type="number">
- <qandaentry>
- <question>
-
- <para>
- What is the significance of the MIDEARTH<1b> type query?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>Domain Master Browser</primary><see>DMB</see></indexterm>
- <indexterm><primary>DMB</primary></indexterm>
- This is a broadcast announcement by which the Windows machine is attempting to
- locate a Domain Master Browser (DMB) in the event that it might exist on the network.
- Refer to <emphasis>TOSHARG2,</emphasis> Chapter 9, Section 9.7, <quote>Technical Overview of Browsing,</quote>
- for details regarding the function of the DMB and its role in network browsing.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What is the significance of the MIDEARTH<1d> type name registration?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>Local Master Browser</primary><see>LMB</see></indexterm>
- <indexterm><primary>LMB</primary></indexterm>
- This name registration records the machine IP addresses of the LMBs.
- Network clients can query this name type to obtain a list of browser servers from the
- master browser.
- </para>
-
- <para>
- The LMB is responsible for monitoring all host announcements on the local network and for
- collating the information contained within them. Using this information, it can provide answers to other Windows
- network clients that request information such as:
- </para>
-
- <itemizedlist>
- <listitem><para>
- The list of machines known to the LMB (i.e., the browse list)
- </para></listitem>
-
- <listitem><para>
- The IP addresses of all domain controllers known for the domain
- </para></listitem>
-
- <listitem><para>
- The IP addresses of LMBs
- </para></listitem>
-
- <listitem><para>
- The IP address of the DMB (if one exists)
- </para></listitem>
-
- <listitem><para>
- The IP address of the LMB on the local segment
- </para></listitem>
- </itemizedlist>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What is the role and significance of the <01><02>__MSBROWSE__<02><01>
- name registration?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>Browse Master</primary></indexterm>
- This name is registered by the browse master to broadcast and receive domain announcements.
- Its scope is limited to the local network segment, or subnet. By querying this name type,
- master browsers on networks that have multiple domains can find the names of master browsers
- for each domain.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What is the significance of the MIDEARTH<1e> type name registration?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>Browser Election Service</primary></indexterm>
- This name is registered by all browse masters in a domain or workgroup. The registration
- name type is known as the Browser Election Service. Master browsers register themselves
- with this name type so that DMBs can locate them to perform cross-subnet
- browse list updates. This name type is also used to initiate elections for Master Browsers.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- <indexterm><primary>guest account</primary></indexterm>
- What is the significance of the <parameter>guest account</parameter> in smb.conf?
- </para>
-
- </question>
- <answer>
-
- <para>
- This parameter specifies the default UNIX account to which MS Windows networking
- NULL session connections are mapped. The default name for the UNIX account used for
- this mapping is called <constant>nobody</constant>. If the UNIX/Linux system that
- is hosting Samba does not have a <constant>nobody</constant> account and an alternate
- mapping has not been specified, network browsing will not work at all.
- </para>
-
- <para>
- It should be noted that the <parameter>guest account</parameter> is essential to
- Samba operation. Either the operating system must have an account called <constant>nobody</constant>
- or there must be an entry in the &smb.conf; file with a valid UNIX account, such as
- <smbconfoption name="guest account">ftp</smbconfoption>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Is it possible to reduce network broadcast activity with Samba?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>NetBIOS</primary></indexterm>
- Yes, there are two ways to do this. The first involves use of WINS (See <emphasis>TOSHARG2</emphasis>, Chapter 9,
- Section 9.5, <quote>WINS &smbmdash; The Windows Inter-networking Name Server</quote>); the
- alternate method involves disabling the use of NetBIOS over TCP/IP. This second method requires
- a correctly configured DNS server (see <emphasis>TOSHARG2</emphasis>, Chapter 9, Section 9.3, <quote>Discussion</quote>).
- </para>
-
- <para>
- <indexterm><primary>broadcast</primary></indexterm>
- <indexterm><primary>NetBIOS</primary><secondary>Node Type</secondary></indexterm>
- <indexterm><primary>Hybrid</primary></indexterm>
- The use of WINS reduces network broadcast traffic. The reduction is greatest when all network
- clients are configured to operate in <parameter>Hybrid Mode</parameter>. This can be effected through
- use of DHCP to set the NetBIOS node type to type 8 for all network clients. Additionally, it is
- beneficial to configure Samba to use <smbconfoption name="name resolve order">wins host cast</smbconfoption>.
- </para>
-
- <note><para>
- Use of SMB without NetBIOS is possible only on Windows 200x/XP Professional clients and servers, as
- well as with Samba.
- </para></note>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Can I just use plain-text passwords with Samba?
- </para>
-
- </question>
- <answer>
-
- <para>
- Yes, you can configure Samba to use plain-text passwords, though this does create a few problems.
- </para>
-
- <para>
- First, the use of <filename>/etc/passwd</filename>-based plain-text passwords requires that registry
- modifications be made on all MS Windows client machines to enable plain-text passwords support. This
- significantly diminishes the security of MS Windows client operation. Many network administrators
- are bitterly opposed to doing this.
- </para>
-
- <para>
- Second, Microsoft has not maintained plain-text password support since the default setting was made
- disabling this. When network connections are dropped by the client, it is not possible to re-establish
- the connection automatically. Users need to log off and then log on again. Plain-text password support
- may interfere with recent enhancements that are part of the Microsoft move toward a more secure computing
- environment.
- </para>
-
- <para>
- Samba supports Microsoft encrypted passwords. Be advised not to reintroduce plain-text password handling.
- Just create user accounts by running <command>smbpasswd -a 'username'</command>
- </para>
-
- <para>
- It is not possible to add a user to the <parameter>passdb backend</parameter> database unless there is
- a UNIX system account for that user. On systems that run <command>winbindd</command> to access the Samba
- PDC/BDC to provide Windows user and group accounts, the <parameter>idmap uid, idmap gid</parameter> ranges
- set in the &smb.conf; file provide the local UID/GIDs needed for local identity management purposes.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What parameter in the &smb.conf; file is used to enable the use of encrypted passwords?
- </para>
-
- </question>
- <answer>
-
- <para>
- The parameter in the &smb.conf; file that controls this behavior is known as <parameter>encrypt
- passwords</parameter>. The default setting for this in Samba is <constant>Yes (Enabled)</constant>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Is it necessary to specify <smbconfoption name="encrypt passwords">Yes</smbconfoption>
- when Samba is configured as a domain member?
- </para>
-
- </question>
- <answer>
-
- <para>
- No. This is the default behavior.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Is it necessary to specify a <parameter>guest account</parameter> when Samba is configured
- as a domain member server?
- </para>
-
- </question>
- <answer>
-
- <para>
- Yes. This is a local function on the server. The default setting is to use the UNIX account
- <constant>nobody</constant>. If this account does not exist on the UNIX server, then it is
- necessary to provide a <smbconfoption name="guest account">an_account</smbconfoption>,
- where <constant>an_account</constant> is a valid local UNIX user account.
- </para>
-
- </answer>
- </qandaentry>
- </qandaset>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<chapter id="DomApps">
-<title>Integrating Additional Services</title>
-
- <para>
- <indexterm><primary>authentication</primary></indexterm>
- <indexterm><primary>backends</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- You've come a long way now. You have pretty much mastered Samba for
- most uses it can be put to. Up until now, you have cast Samba in the leading
- role, and where authentication was required, you have used one or another of
- Samba's many authentication backends (from flat text files with smbpasswd
- to LDAP directory integration with ldapsam). Now you can design a
- solution for a new Abmas business. This business is running Windows Server
- 2003 and Active Directory, and these are to stay. It's time to master
- implementing Samba and Samba-supported services in a domain controlled by
- the latest Windows authentication technologies. Let's get started &smbmdash; this is
- leading edge.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- Abmas has continued its miraculous growth; indeed, nothing seems to be able
- to stop its diversification into multiple (and seemingly unrelated) fields.
- Its latest acquisition is Abmas Snack Foods, a big player in the snack-food
- business.
- </para>
-
- <para>
- With this acquisition comes new challenges for you and your team. Abmas Snack
- Foods is a well-developed business with a huge and heterogeneous network. It
- already has Windows, NetWare, and Proprietary UNIX, but as yet no Samba or Linux.
- The network is mature and well-established, and there is no question of its chosen
- user authentication scheme being changed for now. You need to take a wise new
- approach.
- </para>
-
- <para>
- You have decided to set the ball rolling by introducing Samba into the network
- gradually, taking over key services and easing the way to a full migration and,
- therefore, integration into Abmas's existing business later.
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- <indexterm><primary>web</primary><secondary>proxying</secondary></indexterm>
- <indexterm><primary>web</primary><secondary>caching</secondary></indexterm>
- You've promised the skeptical Abmas Snack Foods management team
- that you can show them how Samba can ease itself and other Open Source
- technologies into their existing infrastructure and deliver sound business
- advantages. Cost cutting is high on their agenda (a major promise of the
- acquisition). You have chosen Web proxying and caching as your proving ground.
- </para>
-
- <para>
- <indexterm><primary>bandwidth</primary></indexterm>
- <indexterm><primary>Microsoft ISA</primary></indexterm>
- Abmas Snack Foods has several thousand users housed at its head office
- and multiple regional offices, plants, and warehouses. A high proportion of
- the business's work is done online, so Internet access for most of these
- users is essential. All Internet access, including for all regional offices,
- is funneled through the head office and is the job of the (now your) networking
- team. The bandwidth requirements were horrific (comparable to a small ISP), and
- the team soon discovered proxying and caching. In fact, they became one of
- the earliest commercial users of Microsoft ISA.
- </para>
-
- <para>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>authenticated</primary></indexterm>
- <indexterm><primary>proxy</primary></indexterm>
- The team is not happy with ISA. Because it never lived up to its marketing promises,
- it underperformed and had reliability problems. You have pounced on the opportunity
- to show what Open Source can do. The one thing they do like, however, is ISA's
- integration with Active Directory. They like that their users, once logged on,
- are automatically authenticated against the proxy. If your alternative to ISA
- can operate completely seamlessly in their Active Directory domain, it will be
- approved.
- </para>
-
- <para>
- This is a hands-on exercise. You build software applications so
- that you obtain the functionality Abmas needs.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
-<title>Dissection and Discussion</title>
-
- <para>
- The key requirements in this business example are straightforward. You are not required
- to do anything new, just to replicate an existing system, not lose any existing features,
- and improve performance. The key points are:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Internet access for most employees
- </para></listitem>
- <listitem><para>
- Distributed system to accommodate load and geographical distribution of users
- </para></listitem>
- <listitem><para>
- Seamless and transparent interoperability with the existing Active Directory domain
- </para></listitem>
- </itemizedlist>
-
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- <indexterm><primary>browsing</primary></indexterm>
- <indexterm><primary>Squid proxy</primary></indexterm>
- <indexterm><primary>proxy</primary></indexterm>
- <indexterm><primary>authentication</primary></indexterm>
- <indexterm><primary>Internet Explorer</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>NTLM</primary></indexterm>
- <indexterm><primary>NTLM authentication daemon</primary></indexterm>
- <indexterm><primary>authentication</primary></indexterm>
- <indexterm><primary>daemon</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>domain</primary><secondary>Active Directory</secondary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm><indexterm><primary>token</primary></indexterm>
- Functionally, the user's Internet Explorer requests a browsing session with the
- Squid proxy, for which it offers its AD authentication token. Squid hands off
- the authentication request to the Samba authentication helper application
- called <command>ntlm_auth</command>. This helper is a hook into winbind, the
- Samba NTLM authentication daemon. Winbind enables UNIX services to authenticate
- against Microsoft Windows domains, including Active Directory domains. As Active
- Directory authentication is a modified Kerberos authentication, winbind is assisted
- in this by local Kerberos 5 libraries configured to check passwords with the Active
- Directory server. Once the token has been checked, a browsing session is established.
- This process is entirely transparent and seamless to the user.
- </para>
-
- <para>
- Enabling this consists of:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Preparing the necessary environment using preconfigured packages
- </para></listitem>
-
- <listitem><para>
- Setting up raw Kerberos authentication against the Active Directory domain
- </para></listitem>
-
- <listitem><para>
- Configuring, compiling, and then installing the supporting Samba components
- </para></listitem>
-
- <listitem><para>
- Tying it all together
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
-
- <sect2>
- <title>Political Issues</title>
-
- <para>
- You are a stranger in a strange land, and all eyes are upon you. Some would even like to see
- you fail. For you to gain the trust of your newly acquired IT people, it is essential that your
- solution does everything the old one did, but does it better in every way. Only then
- will the entrenched positions consider taking up your new way of doing things on a
- wider scale.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- <indexterm><primary>Squid</primary></indexterm>
- First, your system needs to be prepared and in a known good state to proceed. This consists
- of making sure that everything the system depends on is present and that everything that could
- interfere or conflict with the system is removed. You will be configuring the Squid and Samba
- packages and updating them if necessary. If conflicting packages of these programs are installed,
- they must be removed.
- </para>
-
- <para>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- The following packages should be available on your Red Hat Linux system:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>krb5</primary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- krb5-libs
- </para></listitem>
-
- <listitem><para>
- krb5-devel
- </para></listitem>
-
- <listitem><para>
- krb5-workstation
- </para></listitem>
-
- <listitem><para>
- krb5-server
- </para></listitem>
-
- <listitem><para>
- pam_krb5
- </para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>SUSE Linux</primary></indexterm>
- In the case of SUSE Linux, these packages are called:
- </para>
-
- <itemizedlist>
- <listitem><para>
- heimdal-lib
- </para></listitem>
-
- <listitem><para>
- heimdal-devel
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Heimdal</primary></indexterm>
- heimdal
- </para></listitem>
-
- <listitem><para>
- pam_krb5
- </para></listitem>
- </itemizedlist>
-
- <para>
- If the required packages are not present on your system, you must install
- them from the vendor's installation media. Follow the administrative guide
- for your Linux system to ensure that the packages are correctly updated.
- </para>
-
- <note><para>
- <indexterm><primary>MS Windows Server 2003</primary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- <indexterm><primary>MIT</primary></indexterm>
- If the requirement is for interoperation with MS Windows Server 2003, it
- will be necessary to ensure that you are using MIT Kerberos version 1.3.1
- or later. Red Hat Linux 9 ships with MIT Kerberos 1.2.7 and thus requires
- updating.
- </para>
-
- <para>
- <indexterm><primary>Heimdal</primary></indexterm>
- <indexterm><primary>SUSE Enterprise Linux Server</primary></indexterm>
- Heimdal 0.6 or later is required in the case of SUSE Linux. SUSE Enterprise
- Linux Server 8 ships with Heimdal 0.4. SUSE 9 ships with the necessary version.
- </para></note>
-
- <sect2 id="ch10-one">
- <title>Removal of Pre-Existing Conflicting RPMs</title>
-
- <para>
- <indexterm><primary>Squid</primary></indexterm>
- If Samba and/or Squid RPMs are installed, they should be updated. You can
- build both from source.
- </para>
-
- <para>
- <indexterm><primary>rpm</primary></indexterm>
- <indexterm><primary>samba</primary></indexterm>
- <indexterm><primary>squid</primary></indexterm>
- Locating the packages to be un-installed can be achieved by running:
-<screen>
-&rootprompt; rpm -qa | grep -i samba
-&rootprompt; rpm -qa | grep -i squid
-</screen>
- The identified packages may be removed using:
-<screen>
-&rootprompt; rpm -e samba-common
-</screen>
- </para>
-
- <sect2>
- <title>Kerberos Configuration</title>
-
- <para>
- <indexterm><primary>Kerberos</primary></indexterm>
- <indexterm><primary>Active Directory</primary><secondary>server</secondary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- <indexterm><primary>KDC</primary></indexterm>
- The systems Kerberos installation must be configured to communicate with
- your primary Active Directory server (ADS KDC).
- </para>
-
- <para>
- Strictly speaking, MIT Kerberos version 1.3.4 currently gives the best results,
- although the current default Red Hat MIT version 1.2.7 gives acceptable results
- unless you are using Windows 2003 servers.
- </para>
-
- <para>
- <indexterm><primary>MIT</primary></indexterm>
- <indexterm><primary>Heimdal</primary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- <indexterm><primary>/etc/krb5.conf</primary></indexterm>
- <indexterm><primary>DNS</primary><secondary>SRV records</secondary></indexterm>
- <indexterm><primary>KDC</primary></indexterm>
- <indexterm><primary>DNS</primary><secondary>lookup</secondary></indexterm>
- Officially, neither MIT (1.3.4) nor Heimdal (0.63) Kerberos needs an <filename>/etc/krb5.conf</filename>
- file in order to work correctly. All ADS domains automatically create SRV records in the
- DNS zone <constant>Kerberos.REALM.NAME</constant> for each KDC in the realm. Since both
- MIT and Heimdal, KRB5 libraries default to checking for these records, so they
- automatically find the KDCs. In addition, <filename>krb5.conf</filename> allows
- specifying only a single KDC, even if there is more than one. Using the DNS lookup
- allows the KRB5 libraries to use whichever KDCs are available.
- </para>
-
- <procedure>
- <title>Kerberos Configuration Steps</title>
-
- <step><para>
- <indexterm><primary>krb5.conf</primary></indexterm>
- If you find the need to manually configure the <filename>krb5.conf</filename>, you should edit it
- to have the contents shown in <link linkend="ch10-krb5conf"/>. The final fully qualified path for this file
- should be <filename>/etc/krb5.conf</filename>.
- </para></step>
-
- <step><para>
- <indexterm><primary>Kerberos</primary></indexterm>
- <indexterm><primary>realm</primary></indexterm>
- <indexterm><primary>case-sensitive</primary></indexterm>
- <indexterm><primary>KDC</primary></indexterm>
- <indexterm><primary>synchronization</primary></indexterm>
- <indexterm><primary>initial credentials</primary></indexterm>
- <indexterm><primary>Clock skew</primary></indexterm>
- <indexterm><primary>NTP</primary></indexterm>
- <indexterm><primary>DNS</primary><secondary>lookup</secondary></indexterm>
- <indexterm><primary>reverse DNS</primary></indexterm>
- <indexterm><primary>NetBIOS name </primary></indexterm>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- <indexterm><primary>mapping</primary></indexterm>
- The following gotchas often catch people out. Kerberos is case sensitive. Your realm must
- be in UPPERCASE, or you will get an error: <quote>Cannot find KDC for requested realm while getting
- initial credentials</quote>. Kerberos is picky about time synchronization. The time
- according to your participating servers must be within 5 minutes or you get an error:
- <quote>kinit(v5): Clock skew too great while getting initial credentials</quote>.
- Clock skew limits are, in fact, configurable in the Kerberos protocols (the default is
- 5 minutes). A better solution is to implement NTP throughout your server network.
- Kerberos needs to be able to do a reverse DNS lookup on the IP address of your KDC.
- Also, the name that this reverse lookup maps to must either be the NetBIOS name of
- the KDC (i.e., the hostname with no domain attached) or the
- NetBIOS name followed by the realm. If all else fails, you can add a
- <filename>/etc/hosts</filename> entry mapping the IP address of your KDC to its
- NetBIOS name. If Kerberos cannot do this reverse lookup, you will get a local error
- when you try to join the realm.
- </para></step>
-
- <step><para>
- <indexterm><primary>kinit</primary></indexterm>
- You are now ready to test your installation by issuing the command:
-<screen>
-&rootprompt; kinit [USERNAME@REALM]
-</screen>
- You are asked for your password, which you should enter. The following
- is a typical console sequence:
-<screen>
-&rootprompt; kinit ADMINISTRATOR@LONDON.ABMAS.BIZ
-Password for ADMINISTRATOR@LONDON.ABMAS.BIZ:
-</screen>
- Make sure that your password is accepted by the Active Directory KDC.
- </para></step>
- </procedure>
-
-<example id="ch10-krb5conf">
-<title>Kerberos Configuration &smbmdash; File: <filename>/etc/krb5.conf</filename></title>
-<screen>
-[libdefaults]
- default_realm = LONDON.ABMAS.BIZ
-
-[realms]
- LONDON.ABMAS.BIZ = {
- kdc = w2k3s.london.abmas.biz
- }
-</screen>
-</example>
-
- <para><indexterm>
- <primary>klist</primary>
- </indexterm>
- The command
-<screen>
-&rootprompt; klist -e
-</screen>
- shows the Kerberos tickets cached by the system.
- </para>
-
- <sect3>
- <title>Samba Configuration</title>
-
- <para>
- <indexterm><primary>Active Directory</primary></indexterm>
- Samba must be configured to correctly use Active Directory. Samba must be used, since it
- has the necessary components to interface with Active Directory.
- </para>
-
- <procedure>
- <title>Securing Samba With ADS Support Steps</title>
-
- <step><para>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- <indexterm><primary>Samba Tea</primary></indexterm>
- <indexterm><primary>Red Hat Fedora Linux</primary></indexterm>
- <indexterm><primary>MIT KRB5</primary></indexterm>
- <indexterm><primary>ntlm_auth</primary></indexterm>
- Download the latest stable Samba for Red Hat Linux from the official Samba Team
- <ulink url="http://ftp.samba.org">FTP site.</ulink> The official Samba Team
- RPMs for Red Hat Fedora Linux contain the <command>ntlm_auth</command> tool
- needed, and are linked against MIT KRB5 version 1.3.1 and therefore are ready for use.
- </para>
-
- <para>
- <indexterm><primary>SerNet</primary></indexterm>
- <indexterm><primary>RPMs</primary></indexterm>
- The necessary, validated RPM packages for SUSE Linux may be obtained from
- the <ulink url="ftp://ftp.sernet.de/pub/samba">SerNet</ulink> FTP site that
- is located in Germany. All SerNet RPMs are validated, have the necessary
- <command>ntlm_auth</command> tool, and are statically linked
- against suitably patched Heimdal 0.6 libraries.
- </para></step>
-
- <step><para>
- Using your favorite editor, change the <filename>/etc/samba/smb.conf</filename>
- file so it has contents similar to the example shown in <link linkend="ch10-smbconf"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>computer account</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>i
- <indexterm><primary>Kerberos ticket</primary></indexterm>
- <indexterm><primary>ticket</primary></indexterm>
- Next you need to create a computer account in the Active Directory.
- This sets up the trust relationship needed for other clients to
- authenticate to the Samba server with an Active Directory Kerberos ticket.
- This is done with the <quote>net ads join -U [Administrator%Password]</quote>
- command, as follows:
-<screen>
-&rootprompt; net ads join -U administrator%vulcon
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>Samba</primary></indexterm>
- Your new Samba binaries must be started in the standard manner as is applicable
- to the platform you are running on. Alternatively, start your Active Directory-enabled Samba with the following commands:
-<screen>
-&rootprompt; smbd -D
-&rootprompt; nmbd -D
-&rootprompt; winbindd -D
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>Active Directory</primary><secondary>domain</secondary></indexterm>
- <indexterm><primary>wbinfo</primary></indexterm>
- <indexterm><primary>enumerating</primary></indexterm>
- <indexterm><primary>Active Directory</primary><secondary>tree</secondary></indexterm>
- We now need to test that Samba is communicating with the Active
- Directory domain; most specifically, we want to see whether winbind
- is enumerating users and groups. Issue the following commands:
-<screen>
-&rootprompt; wbinfo -t
-checking the trust secret via RPC calls succeeded
-</screen>
- This tests whether we are authenticating against Active Directory:
-<screen>
-&rootprompt; wbinfo -u
-LONDON+Administrator
-LONDON+Guest
-LONDON+SUPPORT_388945a0
-LONDON+krbtgt
-LONDON+jht
-LONDON+xjht
-</screen>
- This enumerates all the users in your Active Directory tree:
-<screen>
-&rootprompt; wbinfo -g
-LONDON+Domain Computers
-LONDON+Domain Controllers
-LONDON+Schema Admins
-LONDON+Enterprise Admins
-LONDON+Domain Admins
-LONDON+Domain Users
-LONDON+Domain Guests
-LONDON+Group Policy Creator Owners
-LONDON+DnsUpdateProxy
-</screen>
- This enumerates all the groups in your Active Directory tree.
- </para></step>
-
- <step><para>
- <indexterm><primary>Squid</primary></indexterm>
- <indexterm><primary>ntlm_auth</primary></indexterm>
- Squid uses the <command>ntlm_auth</command> helper build with Samba.
- You may test <command>ntlm_auth</command> with the command:
-<screen>
-&rootprompt; /usr/bin/ntlm_auth --username=jht
-password: XXXXXXXX
-</screen>
- You are asked for your password, which you should enter. You are rewarded with:
-<screen>
-&rootprompt; NT_STATUS_OK: Success (0x0)
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>ntlm_auth</primary></indexterm>
- <indexterm><primary>authenticate</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>privileged pipe</primary></indexterm>
- <indexterm><primary>squid</primary></indexterm>
- <indexterm><primary>chgrp</primary></indexterm>
- <indexterm><primary>chmod</primary></indexterm>
- <indexterm><primary>failure</primary></indexterm>
- The <command>ntlm_auth</command> helper, when run from a command line as the user
- <quote>root</quote>, authenticates against your Active Directory domain (with
- the aid of winbind). It manages this by reading from the winbind privileged pipe.
- Squid is running with the permissions of user <quote>squid</quote> and group
- <quote>squid</quote> and is not able to do this unless we make a vital change.
- Squid cannot read from the winbind privilege pipe unless you change the
- permissions of its directory. This is the single biggest cause of failure in the
- whole process. Remember to issue the following command (for Red Hat Linux):
-<screen>
-&rootprompt; chgrp squid /var/cache/samba/winbindd_privileged
-&rootprompt; chmod 750 /var/cache/samba/winbindd_privileged
-</screen>
- For SUSE Linux 9, execute the following:
-<screen>
-&rootprompt; chgrp squid /var/lib/samba/winbindd_privileged
-&rootprompt; chmod 750 /var/lib/samba/winbindd_privileged
-</screen>
- </para></step>
-
- </procedure>
- </sect3>
-
- <sect3>
- <title>NSS Configuration</title>
-
- <para>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>authentication</primary></indexterm>
- For Squid to benefit from Samba, NSS must be updated to allow winbind as a valid route to user authentication.
- </para>
-
- <para>
- Edit your <filename>/etc/nsswitch.conf</filename> file so it has the parameters shown
- in <link linkend="ch10-etcnsscfg"/>.
- </para>
-
-<example id="ch10-smbconf">
-<title>Samba Configuration &smbmdash; File: <filename>/etc/samba/smb.conf</filename></title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">LONDON</smbconfoption>
-<smbconfoption name="netbios name">W2K3S</smbconfoption>
-<smbconfoption name="realm">LONDON.ABMAS.BIZ</smbconfoption>
-<smbconfoption name="security">ads</smbconfoption>
-<smbconfoption name="encrypt passwords">yes</smbconfoption>
-<smbconfoption name="password server">w2k3s.london.abmas.biz</smbconfoption>
-
-<smbconfcomment>separate domain and username with '/', like DOMAIN/username</smbconfcomment>
-<smbconfoption name="winbind separator">/</smbconfoption>
-
-<smbconfcomment>use UIDs from 10000 to 20000 for domain users</smbconfcomment>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfcomment>use GIDs from 10000 to 20000 for domain groups</smbconfcomment>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-
-<smbconfcomment>allow enumeration of winbind users and groups</smbconfcomment>
-<smbconfoption name="winbind enum users">yes</smbconfoption>
-<smbconfoption name="winbind enum groups">yes</smbconfoption>
-<smbconfoption name="winbind user default domain">yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch10-etcnsscfg">
-<title>NSS Configuration File Extract &smbmdash; File: <filename>/etc/nsswitch.conf</filename></title>
-<screen>
-passwd: files winbind
-shadow: files
-group: files winbind
-</screen>
-</example>
-
- </sect3>
-
- <sect3>
- <title>Squid Configuration</title>
-
- <para>
- <indexterm><primary>Squid</primary></indexterm>
- <indexterm><primary>Active Directory</primary><secondary>authentication</secondary></indexterm>
- Squid must be configured correctly to interact with the Samba
- components that handle Active Directory authentication.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Configuration</title></sect2>
-
- <procedure>
- <title>Squid Configuration Steps</title>
-
- <step><para>
- <indexterm><primary>SUSE Linux</primary></indexterm>
- <indexterm><primary>Squid</primary> </indexterm>
- <indexterm><primary>helper agent</primary></indexterm>
- If your Linux distribution is SUSE Linux 9, the version of Squid
- supplied is already enabled to use the winbind helper agent. You
- can therefore omit the steps that would build the Squid binary
- programs.
- </para></step>
-
- <step><para>
- <indexterm><primary>nobody</primary></indexterm>
- <indexterm><primary>squid</primary></indexterm>
- <indexterm><primary>rpms</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>/etc/group</primary></indexterm>
- Squid, by default, runs as the user <constant>nobody</constant>. You need to
- add a system user <constant>squid</constant> and a system group
- <constant>squid</constant> if they are not set up already (if the default
- Red Hat squid rpms were installed, they will be). Set up a
- <constant>squid</constant> user in <filename>/etc/passwd</filename>
- and a <constant>squid</constant> group in <filename>/etc/group</filename> if these aren't there already.
- </para></step>
-
- <step><para>
- <indexterm><primary>permissions</primary></indexterm>
- <indexterm><primary>chown</primary></indexterm>
- You now need to change the permissions on Squid's <constant>var</constant>
- directory. Enter the following command:
-<screen>
-&rootprompt; chown -R squid /var/cache/squid
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>logging</primary></indexterm>
- <indexterm><primary>Squid</primary></indexterm>
- Squid must also have control over its logging. Enter the following commands:
-<screen>
-&rootprompt; chown -R chown squid:squid /var/log/squid
-&rootprompt; chmod 770 /var/log/squid
-</screen>
- </para></step>
-
- <step><para>
- Finally, Squid must be able to write to its disk cache!
- Enter the following commands:
-<screen>
-&rootprompt; chown -R chown squid:squid /var/cache/squid
-&rootprompt; chmod 770 /var/cache/squid
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/squid/squid.conf</primary></indexterm>
- The <filename>/etc/squid/squid.conf</filename> file must be edited to include the lines from
- <link linkend="etcsquidcfg"/> and <link linkend="etcsquid2"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>cache directories</primary></indexterm>
- You must create Squid's cache directories before it may be run. Enter the following command:
-<screen>
-&rootprompt; squid -z
-</screen>
- </para></step>
-
- <step><para>
- Finally, start Squid and enjoy transparent Active Directory authentication.
- Enter the following command:
-<screen>
-&rootprompt; squid
-</screen>
- </para></step>
- </procedure>
-
-<example id="etcsquidcfg">
-<title>Squid Configuration File Extract &smbmdash; <filename>/etc/squid.conf</filename> [ADMINISTRATIVE PARAMETERS Section]</title>
-<screen>
- cache_effective_user squid
- cache_effective_group squid
-</screen>
-</example>
-
-<example id="etcsquid2">
-<title>Squid Configuration File extract &smbmdash; File: <filename>/etc/squid.conf</filename> [AUTHENTICATION PARAMETERS Section]</title>
-<screen>
- auth_param ntlm program /usr/bin/ntlm_auth \
- --helper-protocol=squid-2.5-ntlmssp
- auth_param ntlm children 5
- auth_param ntlm max_challenge_reuses 0
- auth_param ntlm max_challenge_lifetime 2 minutes
- auth_param basic program /usr/bin/ntlm_auth \
- --helper-protocol=squid-2.5-basic
- auth_param basic children 5
- auth_param basic realm Squid proxy-caching web server
- auth_param basic credentialsttl 2 hours
- acl AuthorizedUsers proxy_auth REQUIRED
- http_access allow all AuthorizedUsers
-</screen>
-</example>
-
- </sect2>
-
- <sect2>
- <title>Key Points Learned</title>
-
- <para>
- <indexterm><primary>Web browsers</primary></indexterm>
- <indexterm><primary>services</primary></indexterm>
- <indexterm><primary>authentication protocols</primary></indexterm>
- <indexterm><primary>Web</primary><secondary>proxy</secondary><tertiary>access</tertiary></indexterm>
- <indexterm><primary>NTLMSSP</primary></indexterm>
- Microsoft Windows networking protocols permeate the spectrum of technologies that Microsoft
- Windows clients use, even when accessing traditional services such as Web browsers. Depending
- on whom you discuss this with, this is either good or bad. No matter how you might evaluate this,
- the use of NTLMSSP as the authentication protocol for Web proxy access has some advantages over
- the cookie-based authentication regime used by all competing browsers. It is Samba's implementation
- of NTLMSSP that makes it attractive to implement the solution that has been demonstrated in this chapter.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- <indexterm><primary>ntlm_auth</primary></indexterm>
- <indexterm><primary>SambaXP conference</primary></indexterm>
- <indexterm><primary>Goettingen</primary></indexterm>
- <indexterm><primary>Italian</primary></indexterm>
- The development of the <command>ntlm_auth</command> module was first discussed in many Open Source circles
- in 2002. At the SambaXP conference in Goettingen, Germany, Mr. Francesco Chemolli demonstrated the use of
- <command>ntlm_auth</command> during one of the late developer meetings that took place. Since that time, the
- adoption of <command>ntlm_auth</command> has spread considerably.
- </para>
-
- <para>
- The largest report from a site that uses Squid with <command>ntlm_auth</command>-based authentication
- support uses a dual processor server that has 2 GB of memory. It provides Web and FTP proxy services for 10,000
- users. Approximately 2,000 of these users make heavy use of the proxy services. According to the source, who
- wishes to remain anonymous, the sustained transaction load on this server hovers around 140 hits/sec. The following
- comments were made with respect to questions regarding the performance of this installation:
- </para>
-
- <blockquote><para>
- [In our] EXTREMELY optimized environment . . . [the] performance impact is almost [nothing]. The <quote>almost</quote>
- part is due to the brain damage of the ntlm-over-http protocol definition. Suffice to say that its worst-case
- scenario triples the number of hits needed to perform the same transactions versus basic or digest auth[entication].
- </para></blockquote>
-
- <para>
- You would be well-advised to recognize that all cache-intensive proxying solutions demand a lot of memory.
- Make certain that your Squid proxy server is equipped with sufficient memory to permit all proxy operations to run
- out of memory without invoking the overheads involved in the use of memory that has to be swapped to disk.
- </para>
-
- <qandaset defaultlabel="chap10bqa" type="number">
- <qandaentry>
- <question>
-
- <para>
- What does Samba have to do with Web proxy serving?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><secondary>transparent inter-operability</secondary></indexterm>
- <indexterm><primary>Windows clients</primary></indexterm>
- <indexterm><primary>network</primary><secondary>services</secondary></indexterm>
- <indexterm><primary>authentication</primary></indexterm>
- <indexterm><primary>wrapper</primary></indexterm>
- To provide transparent interoperability between Windows clients and the network services
- that are used from them, Samba had to develop tools and facilities that deliver that feature. The benefit
- of Open Source software is that it can readily be reused. The current <command>ntlm_auth</command>
- module is basically a wrapper around authentication code from the core of the Samba project.
- </para>
-
- <para>
- <indexterm><primary>plain-text</primary></indexterm>
- <indexterm><primary>authentication</primary><secondary>plain-text</secondary></indexterm>
- <indexterm><primary>Web</primary><secondary>proxy</secondary></indexterm>
- <indexterm><primary>FTP</primary><secondary>proxy</secondary></indexterm>
- <indexterm><primary>NTLMSSP</primary></indexterm>
- <indexterm><primary>logon credentials</primary></indexterm>
- <indexterm><primary>Windows explorer</primary></indexterm>
- <indexterm><primary>Internet Information Server</primary></indexterm>
- <indexterm><primary>Apache Web server</primary></indexterm>
- The <command>ntlm_auth</command> module supports basic plain-text authentication and NTLMSSP
- protocols. This module makes it possible for Web and FTP proxy requests to be authenticated without
- the user being interrupted via his or her Windows logon credentials. This facility is available with
- MS Windows Explorer and is one of the key benefits claimed for Microsoft Internet Information Server.
- There are a few open source initiatives to provide support for these protocols in the Apache Web server
- also.
- </para>
-
- <para>
- <indexterm><primary>wrapper</primary></indexterm>
- The short answer is that by adding a wrapper around key authentication components of Samba, other
- projects (like Squid) can benefit from the labors expended in meeting user interoperability needs.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What other services does Samba provide?
- </para>
-
- </question>
- <answer>
-
- <para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>Identity resolver</primary></indexterm>
- <indexterm><primary>daemon</primary></indexterm>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>file and print server</primary></indexterm>
- Samba is a file and print server. The core components that provide this functionality are <command>smbd</command>,
- <command>nmbd</command>, and the identity resolver daemon, <command>winbindd</command>.
- </para>
-
- <para>
- <indexterm><primary>SMB/CIFS</primary></indexterm>
- <indexterm><primary>smbclient</primary></indexterm>
- Samba is an SMB/CIFS client. The core component that provides this is called <command>smbclient</command>.
- </para>
-
- <para>
- <indexterm><primary>modules</primary></indexterm>
- <indexterm><primary>utilities</primary></indexterm>
- <indexterm><primary>validation</primary></indexterm>
- <indexterm><primary>inter-operability</primary></indexterm>
- <indexterm><primary>authentication</primary></indexterm>
- Samba includes a number of helper tools, plug-in modules, utilities, and test and validation facilities.
- Samba includes glue modules that help provide interoperability between MS Windows clients and UNIX/Linux
- servers and clients. It includes Winbind agents that make it possible to authenticate UNIX/Linux access attempts
- as well as logins to an SMB/CIFS authentication server backend. Samba includes name service switch (NSS) modules
- to permit identity resolution via SMB/CIFS servers (Windows NT4/200x, Samba, and a host of other commercial
- server products).
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Does use of Samba (<command>ntlm_auth</command>) improve the performance of Squid?
- </para>
-
- </question>
- <answer>
-
- <para>
- Not really. Samba's <command>ntlm_auth</command> module handles only authentication. It requires that
- Squid make an external call to <command>ntlm_auth</command> and therefore actually incurs a
- little more overhead. Compared with the benefit obtained, that overhead is well worth enduring. Since
- Squid is a proxy server, and proxy servers tend to require lots of memory, it is good advice to provide
- sufficient memory when using Squid. Just add a little more to accommodate <command>ntlm_auth</command>.
- </para>
-
- </answer>
- </qandaentry>
- </qandaset>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<chapter id="HA">
-<title>Performance, Reliability, and Availability</title>
-
- <para>
- <indexterm><primary>performance</primary></indexterm>
- <indexterm><primary>reliability</primary></indexterm>
- <indexterm><primary>availability</primary></indexterm>
- Well, you have reached one of the last chapters of this book. It is customary to attempt
- to wrap up the theme and contents of a book in what is generally regarded as the
- chapter that should draw conclusions. This book is a suspense thriller, and since
- the plot of the stories told mostly lead you to bigger, better Samba networking
- solutions, it is perhaps appropriate to close this book with a few pertinent comments
- regarding some of the things everyone can do to deliver a reliable Samba network.
- </para>
-
- <blockquote><attribution>Anonymous</attribution><para>
- In a world so full of noise, how can the sparrow be heard?
- </para></blockquote>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- <indexterm><primary>clustering</primary></indexterm>
- The sparrow is a small bird whose sounds are drowned out by the noise of the busy
- world it lives in. Likewise, the simple steps that can be taken to improve the
- reliability and availability of a Samba network are often drowned out by the volume
- of discussions about grandiose Samba clustering designs. This is not intended to
- suggest that clustering is not important, because clearly it is. This chapter does not devote
- itself to discussion of clustering because each clustering methodology uses its own
- custom tools and methods. Only passing comments are offered concerning these methods.
- </para>
-
- <para>
- <indexterm><primary>cluster</primary></indexterm>
- <indexterm><primary>samba cluster</primary></indexterm>
- <indexterm><primary>scalability</primary></indexterm>
-<ulink url="http://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=samba+cluster&btnG=Google+Search">A search</ulink>
- for <quote>samba cluster</quote> produced 71,600 hits. And a search for <quote>highly available samba</quote>
- and <quote>highly available windows</quote> produced an amazing number of references.
- It is clear from the resources on the Internet that Windows file and print services
- availability, reliability, and scalability are of vital interest to corporate network users.
- </para>
-
- <para>
- <indexterm><primary>performance</primary></indexterm>
- So without further background, you can review a checklist of simple steps that
- can be taken to ensure acceptable network performance while keeping costs of ownership
- well under control.
- </para>
-
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>simple</primary></indexterm>
- <indexterm><primary>complexities</primary></indexterm>
- If it is your purpose to get the best mileage out of your Samba servers, there is one rule that
- must be obeyed. If you want the best, keep your implementation as simple as possible. You may
- well be forced to introduce some complexities, but you should do so only as a last resort.
- </para>
-
- <para>
- Simple solutions are likely to be easier to get right than are complex ones. They certainly
- make life easier for your successor. Simple implementations can be more readily audited than can
- complex ones.
- </para>
-
- <para>
- <indexterm><primary>broken behavior</primary></indexterm>
- <indexterm><primary>poor performance</primary></indexterm>
- Problems reported by users fall into three categories: configurations that do not work, those
- that have broken behavior, and poor performance. The term <emphasis>broken behavior</emphasis>
- means that the function of a particular Samba component appears to work sometimes, but not at
- others. The resulting intermittent operation is clearly unacceptable. An example of
- <emphasis>broken behavior</emphasis> known to many Windows networking users occurs when the
- list of Windows machines in MS Explorer changes, sometimes listing machines that are running
- and at other times not listing them even though the machines are in use on the network.
- </para>
-
- <para>
- <indexterm><primary>smbfs</primary></indexterm>
- <indexterm><primary>smbmnt</primary></indexterm>
- <indexterm><primary>smbmount</primary></indexterm>
- <indexterm><primary>smbumnt</primary></indexterm>
- <indexterm><primary>smbumount</primary></indexterm>
- <indexterm><primary>front-end</primary></indexterm>
- A significant number of reports concern problems with the <command>smbfs</command> file system
- driver that is part of the Linux kernel, not part of Samba. Users continue to interpret that
- <command>smbfs</command> is part of Samba, simply because Samba includes the front-end tools
- that are used to manage <command>smbfs</command>-based file service connections. So, just
- for the record, the tools <command>smbmnt</command>, <command>smbmount</command>,
- <command>smbumount</command>, and <command>smbumnt</command> are front-end
- facilities to core drivers that are supplied as part of the Linux kernel. These tools share a
- common infrastructure with some Samba components, but they are not maintained as part of
- Samba and are really foreign to it.
- </para>
-
- <para>
- <indexterm><primary>cifsfs</primary></indexterm>
- The new project, <command>cifsfs</command>, is destined to replace <command>smbfs</command>.
- It, too, is not part of Samba, even though one of the Samba Team members is a prime mover in
- this project.
- </para>
-
- <para>
- Table 13.1 lists typical causes of:
- </para>
-
- <itemizedlist>
- <listitem><para>Not Working (NW)</para></listitem>
- <listitem><para>Broken Behavior (BB)</para></listitem>
- <listitem><para>Poor Performance (PP)</para></listitem>
- </itemizedlist>
-
-
- <table id="ProbList">
- <title>Effect of Common Problems</title>
- <tgroup cols="4">
- <colspec align="left"/>
- <colspec align="center"/>
- <colspec align="center"/>
- <colspec align="center"/>
- <thead>
- <row>
- <entry><para>Problem</para></entry>
- <entry><para>NW</para></entry>
- <entry><para>BB</para></entry>
- <entry><para>PP</para></entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><para>File locking</para></entry>
- <entry><para>-</para></entry>
- <entry><para>X</para></entry>
- <entry><para>-</para></entry>
- </row>
- <row>
- <entry><para>Hardware problems</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- </row>
- <row>
- <entry><para>Incorrect authentication</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- <entry><para>-</para></entry>
- </row>
- <row>
- <entry><para>Incorrect configuration</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- </row>
- <row>
- <entry><para>LDAP problems</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- <entry><para>-</para></entry>
- </row>
- <row>
- <entry><para>Name resolution</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- </row>
- <row>
- <entry><para>Printing problems</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- <entry><para>-</para></entry>
- </row>
- <row>
- <entry><para>Slow file transfer</para></entry>
- <entry><para>-</para></entry>
- <entry><para>-</para></entry>
- <entry><para>X</para></entry>
- </row>
- <row>
- <entry><para>Winbind problems</para></entry>
- <entry><para>X</para></entry>
- <entry><para>X</para></entry>
- <entry><para>-</para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- <indexterm><primary>network hygiene</primary></indexterm>
- It is obvious to all that the first requirement (as a matter of network hygiene) is to eliminate
- problems that affect basic network operation. This book has provided sufficient working examples
- to help you to avoid all these problems.
- </para>
-
-</sect1>
-
-<sect1>
- <title>Guidelines for Reliable Samba Operation</title>
-
- <para>
- <indexterm><primary>resilient</primary></indexterm>
- <indexterm><primary>extreme demand</primary></indexterm>
- Your objective is to provide a network that works correctly, can grow at all times, is resilient
- at times of extreme demand, and can scale to meet future needs. The following subject areas provide
- pointers that can help you today.
- </para>
-
- <sect2>
- <title>Name Resolution</title>
-
- <para>
- There are three basic current problem areas: bad hostnames, routed networks, and network collisions.
- These are covered in the following discussion.
- </para>
-
- <sect3>
- <title>Bad Hostnames</title>
-
- <para>
- <indexterm><primary>DHCP</primary><secondary>client</secondary></indexterm>
- <indexterm><primary>netbios name</primary></indexterm>
- <indexterm><primary>localhost</primary></indexterm>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- <indexterm><primary>NetBIOS</primary></indexterm>
- When configured as a DHCP client, a number of Linux distributions set the system hostname
- to <constant>localhost</constant>. If the parameter <parameter>netbios name</parameter> is not
- specified to something other than <constant>localhost</constant>, the Samba server appears
- in the Windows Explorer as <constant>LOCALHOST</constant>. Moreover, the entry in the <filename>/etc/hosts</filename>
- on the Linux server points to IP address <constant>127.0.0.1</constant>. This means that
- when the Windows client obtains the IP address of the Samba server called <constant>LOCALHOST</constant>,
- it obtains the IP address <constant>127.0.0.1</constant> and then proceeds to attempt to
- set up a NetBIOS over TCP/IP connection to it. This cannot work, because that IP address is
- the local Windows machine itself. Hostnames must be valid for Windows networking to function
- correctly.
- </para>
-
- <para>
- <indexterm><primary>digits</primary></indexterm>
- A few sites have tried to name Windows clients and Samba servers with a name that begins
- with the digits 1-9. This does not work either because it may result in the client or
- server attempting to use that name as an IP address.
- </para>
-
- <para>
- <indexterm><primary>DNS</primary><secondary>name lookup</secondary></indexterm>
- <indexterm><primary>resolve</primary></indexterm>
- A Samba server called <constant>FRED</constant> in a NetBIOS domain called <constant>COLLISION</constant>
- in a network environment that is part of the fully-qualified Internet domain namespace known
- as <constant>parrots.com</constant>, results in DNS name lookups for <constant>fred.parrots.com</constant>
- and <constant>collision.parrots.com</constant>. It is therefore a mistake to name the domain
- (workgroup) <constant>collision.parrots.com</constant>, since this results in DNS lookup
- attempts to resolve <constant>fred.parrots.com.parrots.com</constant>, which most likely
- fails given that you probably do not have this in your DNS namespace.
- </para>
-
- <note><para>
- <indexterm><primary>Active Directory</primary><secondary>realm</secondary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- An Active Directory realm called <constant>collision.parrots.com</constant> is perfectly okay,
- although it too must be capable of being resolved via DNS, something that functions correctly
- if Windows 200x ADS has been properly installed and configured.
- </para></note>
-
- </sect3>
-
- <sect3>
- <title>Routed Networks</title>
-
- <para>
- <indexterm><primary>NetBIOS</primary></indexterm>
- <indexterm><primary>UDP</primary><secondary>broadcast</secondary></indexterm>
- <indexterm><primary>broadcast</primary></indexterm>
- NetBIOS networks (Windows networking with NetBIOS over TCP/IP enabled) makes extensive use
- of UDP-based broadcast traffic, as you saw during the exercises in <link linkend="primer"/>.
- </para>
-
- <para>
- <indexterm><primary>routers</primary></indexterm>
- <indexterm><primary>forwarded</primary></indexterm>
- <indexterm><primary>multi-subnet</primary></indexterm>
- UDP broadcast traffic is not forwarded by routers. This means that NetBIOS broadcast-based
- networking cannot function across routed networks (i.e., multi-subnet networks) unless
- special provisions are made:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>LMHOSTS</primary></indexterm>
- <indexterm><primary>remote announce</primary></indexterm>
- <indexterm><primary>remote browse sync</primary></indexterm>
- Either install on every Windows client an LMHOSTS file (located in the directory
- <filename>C:\windows\system32\drivers\etc</filename>). It is also necessary to
- add to the Samba server &smb.conf; file the parameters <parameter>remote announce</parameter>
- and <parameter>remote browse sync</parameter>. For more information, refer to the online
- manual page for the &smb.conf; file.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>WINS</primary><secondary>server</secondary></indexterm>
- Or configure Samba as a WINS server, and configure all network clients to use that
- WINS server in their TCP/IP configuration.
- </para></listitem>
- </itemizedlist>
-
- <note><para>
- <indexterm><primary>WINS</primary><secondary>name resolution</secondary></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- The use of DNS is not an acceptable substitute for WINS. DNS does not store specific
- information regarding NetBIOS networking particulars that get stored in the WINS
- name resolution database and that Windows clients require and depend on.
- </para></note>
-
- </sect3>
-
- <sect3>
- <title>Network Collisions</title>
-
- <para>
- <indexterm><primary>network</primary><secondary>collisions</secondary></indexterm>
- <indexterm><primary>network</primary><secondary>timeouts</secondary></indexterm>
- <indexterm><primary>collision rates</primary></indexterm>
- <indexterm><primary>network</primary><secondary>load</secondary></indexterm>
- Excessive network activity causes NetBIOS network timeouts. Timeouts may result in
- blue screen of death (BSOD) experiences. High collision rates may be caused by excessive
- UDP broadcast activity, by defective networking hardware, or through excessive network
- loads (another way of saying that the network is poorly designed).
- </para>
-
- <para>
- The use of WINS is highly recommended to reduce network broadcast traffic, as outlined
- in <link linkend="primer"/>.
- </para>
-
- <para>
- <indexterm><primary>netbios forwarding</primary></indexterm>
- <indexterm><primary>broadcast storms</primary></indexterm>
- <indexterm><primary>performance</primary></indexterm>
- Under no circumstances should the facility be supported by many routers, known as <constant>NetBIOS
- forwarding</constant>, unless you know exactly what you are doing. Inappropriate use of this
- facility can result in UDP broadcast storms. In one case in 1999, a university network became
- unusable due to NetBIOS forwarding being enabled on all routers. The problem was discovered during performance
- testing of a Samba server. The maximum throughput on a 100-Base-T (100 MB/sec) network was
- less than 15 KB/sec. After the NetBIOS forwarding was turned off, file transfer performance
- immediately returned to 11 MB/sec.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Samba Configuration</title>
-
- <para>
- As a general rule, the contents of the &smb.conf; file should be kept as simple as possible.
- No parameter should be specified unless you know it is essential to operation.
- </para>
-
- <para>
- <indexterm><primary>document the settings</primary></indexterm>
- <indexterm><primary>documented</primary></indexterm>
- <indexterm><primary>optimized</primary></indexterm>
- Many UNIX administrators like to fully document the settings in the &smb.conf; file. This is a
- bad idea because it adds content to the file. The &smb.conf; file is re-read by every <command>smbd</command>
- process every time the file timestamp changes (or, on systems where this does not work, every 20 seconds or so).
- </para>
-
- <para>
- As the size of the &smb.conf; file grows, the risk of introducing parsing errors also increases.
- It is recommended to keep a fully documented &smb.conf; file on hand, and then to operate Samba only
- with an optimized file.
- </para>
-
- <para><indexterm>
- <primary>testparm</primary>
- </indexterm>
- The preferred way to maintain a documented file is to call it something like <filename>smb.conf.master</filename>.
- You can generate the optimized file by executing:
-<screen>
-&rootprompt; testparm -s smb.conf.master > smb.conf
-</screen>
- You should carefully observe all warnings issued. It is also a good practice to execute the following
- command to confirm correct interpretation of the &smb.conf; file contents:
-<screen>
-&rootprompt; testparm
-Load smb config files from /etc/samba/smb.conf
-Can't find include file /etc/samba/machine.
-Processing section "[homes]"
-Processing section "[print$]"
-Processing section "[netlogon]"
-Processing section "[Profiles]"
-Processing section "[printers]"
-Processing section "[media]"
-Processing section "[data]"
-Processing section "[cdr]"
-Processing section "[apps]"
-Loaded services file OK.
-'winbind separator = +' might cause problems with group membership.
-Server role: ROLE_DOMAIN_PDC
-Press enter to see a dump of your service definitions
-</screen>
- <indexterm><primary>fatal problem</primary></indexterm>
- You now, of course, press the enter key to complete the command, or else abort it by pressing Ctrl-C.
- The important thing to note is the noted Server role, as well as warning messages. Noted configuration
- conflicts must be remedied before proceeding. For example, the following error message represents a
- common fatal problem:
-<screen>
-ERROR: both 'wins support = true' and 'wins server = <server list>'
-cannot be set in the smb.conf file. nmbd will abort with this setting.
-</screen>
- </para>
-
- <para>
- <indexterm><primary>performance degradation</primary></indexterm>
- <indexterm><primary>socket options</primary></indexterm>
- <indexterm><primary>socket address</primary></indexterm>
- There are two parameters that can cause severe network performance degradation: <parameter>socket options</parameter>
- and <parameter>socket address</parameter>. The <parameter>socket options</parameter> parameter was often necessary
- when Samba was used with the Linux 2.2.x kernels. Later kernels are largely self-tuning and seldom benefit from
- this parameter being set. Do not use either parameter unless it has been proven necessary to use them.
- </para>
-
- <para>
- <indexterm><primary>strict sync</primary></indexterm>
- <indexterm><primary>sync always</primary></indexterm>
- <indexterm><primary>severely degrade</primary></indexterm>
- <indexterm><primary>network</primary><secondary>performance</secondary></indexterm>
- Another &smb.conf; parameter that may cause severe network performance degradation is the
- <parameter>strict sync</parameter> parameter. Do not use this at all. There is no good reason
- to use this with any modern Windows client. The <parameter>strict sync</parameter> is often
- used with the <parameter>sync always</parameter> parameter. This, too, can severely
- degrade network performance, so do not set it; if you must, do so with caution.
- </para>
-
- <para>
- <indexterm><primary>opportunistic locking</primary></indexterm>
- <indexterm><primary>file caching</primary></indexterm>
- <indexterm><primary>caching</primary></indexterm>
- <indexterm><primary>oplocks</primary></indexterm>
- Finally, many network administrators deliberately disable opportunistic locking support. While this
- does not degrade Samba performance, it significantly degrades Windows client performance because
- this disables local file caching on Windows clients and forces every file read and written to
- invoke a network read or write call. If for any reason you must disable oplocks (opportunistic locking)
- support, do so only on the share on which it is required. That way, all other shares can provide
- oplock support for operations that are tolerant of it. See <link linkend="ch12dblck"/> for more
- information.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Use and Location of BDCs</title>
-
- <para>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>routed network</primary></indexterm>
- <indexterm><primary>wide-area network</primary></indexterm>
- <indexterm><primary>network segment</primary></indexterm>
- On a network segment where there is a PDC and a BDC, the BDC carries the bulk of the network logon
- processing. If the BDC is a heavily loaded server, the PDC carries a greater proportion of
- authentication and logon processing. When a sole BDC on a routed network segment gets heavily
- loaded, it is possible that network logon requests and authentication requests may be directed
- to a BDC on a distant network segment. This significantly hinders WAN operations
- and is undesirable.
- </para>
-
- <para>
- <indexterm><primary>Domain Member</primary></indexterm>
- <indexterm><primary>Domain Controller</primary></indexterm>
- As a general guide, instead of adding domain member servers to a network, you would be better advised
- to add BDCs until there are fewer than 30 Windows clients per BDC. Beyond that ratio, you should add
- domain member servers. This practice ensures that there are always sufficient domain controllers
- to handle logon requests and authentication traffic.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Use One Consistent Version of MS Windows Client</title>
-
- <para>
- Every network client has its own peculiarities. From a management perspective, it is easier to deal
- with one version of MS Windows that is maintained to a consistent update level than it is to deal
- with a mixture of clients.
- </para>
-
- <para>
- On a number of occasions, particular Microsoft service pack updates of a Windows server or client
- have necessitated special handling from the Samba server end. If you want to remain sane, keep you
- client workstation configurations consistent.
- </para>
-
- </sect2>
-
- <sect2>
- <title>For Scalability, Use SAN-Based Storage on Samba Servers</title>
-
- <para>
- <indexterm><primary>SAN</primary></indexterm>
- <indexterm><primary>synchronization</primary></indexterm>
- Many SAN-based storage systems permit more than one server to share a common data store.
- Use of a shared SAN data store means that you do not need to use time- and resource-hungry data
- synchronization techniques.
- </para>
-
- <para>
- <indexterm><primary>load distribution</primary></indexterm>
- <indexterm><primary>clustering</primary></indexterm>
- The use of a collection of relatively low-cost front-end Samba servers that are coupled to
- a shared backend SAN data store permits load distribution while containing costs below that
- of installing and managing a complex clustering facility.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Distribute Network Load with MSDFS</title>
-
- <para>
- <indexterm><primary>MSDFS</primary></indexterm>
- <indexterm><primary>distributed</primary></indexterm>
- Microsoft DFS (distributed file system) technology has been implemented in Samba. MSDFS permits
- data to be accessed from a single share and yet to actually be distributed across multiple actual
- servers. Refer to <emphasis>TOSHARG2</emphasis>, Chapter 19, for information regarding
- implementation of an MSDFS installation.
- </para>
-
- <para>
- <indexterm><primary>front-end</primary><secondary>server</secondary></indexterm>
- <indexterm><primary>MSDFS</primary></indexterm>
- The combination of multiple backend servers together with a front-end server and use of MSDFS
- can achieve almost the same as you would obtain with a clustered Samba server.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</title>
-
- <para>
- <indexterm><primary>replicate</primary></indexterm>
- <indexterm><primary>rsync</primary></indexterm>
- <indexterm><primary>wide-area network</primary></indexterm>
- Consider using <command>rsync</command> to replicate data across the WAN during times
- of low utilization. Users can then access the replicated data store rather than needing to do so
- across the WAN. This works best for read-only data, but with careful planning can be
- implemented so that modified files get replicated back to the point of origin. Be careful with your
- implementation if you choose to permit modification and return replication of the modified file;
- otherwise, you may inadvertently overwrite important data.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Hardware Problems</title>
-
- <para>
- <indexterm><primary>hardware prices</primary></indexterm>
- <indexterm><primary>hardware problems</primary></indexterm>
- <indexterm><primary>NICs</primary></indexterm>
- <indexterm><primary>defective</primary><secondary>HUBs</secondary></indexterm>
- <indexterm><primary>defective</primary><secondary>switches</secondary></indexterm>
- <indexterm><primary>defective</primary><secondary>cables</secondary></indexterm>
- Networking hardware prices have fallen sharply over the past 5 years. A surprising number
- of Samba networking problems over this time have been traced to defective network interface
- cards (NICs) or defective HUBs, switches, and cables.
- </para>
-
- <para>
- <indexterm><primary>corrective action</primary></indexterm>
- Not surprising is the fact that network administrators do not like to be shown to have made
- a bad decision. Money saved in buying low-cost hardware may result in high costs incurred
- in corrective action.
- </para>
-
- <para>
- <indexterm><primary>intermittent</primary></indexterm>
- <indexterm><primary>data corruption</primary></indexterm>
- <indexterm><primary>slow network</primary></indexterm>
- <indexterm><primary>low performance</primary></indexterm>
- <indexterm><primary>data integrity</primary></indexterm>
- Defective NICs, HUBs, and switches may appear as intermittent network access problems, intermittent
- or persistent data corruption, slow network throughput, low performance, or even as BSOD
- problems with MS Windows clients. In one case, a company updated several workstations with newer, faster
- Windows client machines that triggered problems during logon as well as data integrity problems on
- an older PC that was unaffected so long as the new machines were kept shut down.
- </para>
-
- <para>
- Defective hardware problems may take patience and persistence before the real cause can be discovered.
- </para>
-
- <para>
- <indexterm><primary>RAID controllers</primary></indexterm>
- Networking hardware defects can significantly impact perceived Samba performance, but defective
- RAID controllers as well as SCSI and IDE hard disk controllers have also been known to impair Samba server
- operations. One business came to this realization only after replacing a Samba installation with MS
- Windows Server 2000 running on the same hardware. The root of the problem completely eluded the network
- administrator until the entire server was replaced. While you may well think that this would never
- happen to you, experience shows that given the right (unfortunate) circumstances, this can happen to anyone.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Large Directories</title>
-
- <para>
- There exist applications that create or manage directories containing many thousands of files. Such
- applications typically generate many small files (less than 100 KB). At the best of times, under UNIX,
- listing of the files in a directory that contains many files is slow. By default, Windows NT, 200x,
- and XP Pro cause network file system directory lookups on a Samba server to be performed for both
- the case preserving file name as well as for the mangled (8.3) file name. This incurs a huge overhead
- on the Samba server that may slow down the system dramatically.
- </para>
-
- <para>
- In an extreme case, the performance impact was dramatic. File transfer from the Samba server to a Windows
- XP Professional workstation over 1 Gigabit Ethernet for 250-500 KB files was measured at approximately
- 30 MB/sec. But when tranferring a directory containing 120,000 files, all from 50KB to 60KB in size, the
- transfer rate to the same workstation was measured at approximately 1.5 KB/sec. The net transfer was
- on the order of a factor of 20-fold slower.
- </para>
-
- <para>
- The symptoms that will be observed on the Samba server when a large directory is accessed will be that
- aggregate I/O (typically blocks read) will be relatively low, yet the wait I/O times will be incredibly
- long while at the same time the read queue is large. Close observation will show that the hard drive
- that the file system is on will be thrashing wildly.
- </para>
-
- <para>
- Samba-3.0.12 and later, includes new code that radically improves Samba performance. The secret to this is
- really in the <smbconfoption name="case sensitive">True</smbconfoption> line. This tells smbd never to scan
- for case-insensitive versions of names. So if an application asks for a file called <filename>FOO</filename>,
- and it can not be found by a simple stat call, then smbd will return "file not found" immediately without
- scanning the containing directory for a version of a different case.
- </para>
-
- <para>
- Canonicalize all the files in the directory to have one case, upper or lower - either will do. Then set up
- a new custom share for the application as follows:
- <screen>
- [bigshare]
- path = /data/xrayfiles/neurosurgeons/
- read only = no
- case sensitive = True
- default case = upper
- preserve case = no
- short preserve case = no
- </screen>
- </para>
-
- <para>
- All files and directories under the <parameter>path</parameter> directory must be in the same case
- as specified in the &smb.conf; stanza. This means that smbd will not be able to find lower case
- filenames with these settings. Note, this is done on a per-share basis.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Key Points Learned</title>
-
- <para>
- This chapter has touched in broad sweeps on a number of simple steps that can be taken
- to ensure that your Samba network is resilient, scalable, and reliable, and that it
- performs well.
- </para>
-
- <para>
- Always keep in mind that someone is responsible to maintain and manage your design.
- In the long term, that may not be you. Spare a thought for your successor and give him or
- her an even break.
- </para>
-
- <para>
- <indexterm><primary>assumptions</primary></indexterm>
- Last, but not least, you should not only keep the network design simple, but also be sure it is
- well documented. This book may serve as your pattern for documenting every
- aspect of your design, its implementation, and particularly the objects and assumptions
- that underlie it.
- </para>
-
-</sect1>
-
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="happy">
- <title>Making Happy Users</title>
-
- <para>
- It is said that <quote>a day that is without troubles is not fulfilling. Rather, give
- me a day of troubles well handled so that I can be content with my achievements.</quote>
- </para>
-
- <para>
- In the world of computer networks, problems are as varied as the people who create them
- or experience them. The design of the network implemented in <link linkend="Big500users"/>
- may create problems for some network users. The following lists some of the problems that
- may occur:
- </para>
-
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>network bandwidth</primary><secondary>utilization</secondary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>user account</primary></indexterm>
- <indexterm><primary>PDC/BDC ratio</primary></indexterm>
-<caution><para>
-A significant number of network administrators have responded to the guidance given
-here. It should be noted that there are sites that have a single PDC for many hundreds of
-concurrent network clients. Network bandwidth, network bandwidth utilization, and server load
-are among the factors that determine the maximum number of Windows clients that
-can be served by a single domain controller (PDC or BDC) on a network segment. It is possible
-to operate with only a single PDC over a routed network. What is possible is not necessarily
-<emphasis>best practice</emphasis>. When Windows client network logons begin to fail with
-the message that the domain controller cannot be found or that the user account cannot
-be found (when you know it exists), that may be an indication that the domain controller is
-overloaded or network bandwidth is overloaded. The guidance given for PDC/BDC ratio to Windows
-clients is conservative and if followed will minimize problems &smbmdash; but it is not absolute.
-</para></caution>
-
- <variablelist>
- <varlistentry>
- <term>Users experiencing difficulty logging onto the network</term>
- <listitem><para>
- <indexterm><primary>network</primary><secondary>logon</secondary></indexterm>
- <indexterm><primary>multiple domain controllers</primary></indexterm>
- When a Windows client logs onto the network, many data packets are exchanged
- between the client and the server that is providing the network logon services.
- Each request between the client and the server must complete within a specific
- time limit. This is one of the primary factors that govern the installation of
- multiple domain controllers (usually called secondary or backup controllers).
- As a rough rule, there should be one such backup controller for every
- 30 to 150 clients. The actual limits are determined by network operational
- characteristics.
- </para>
-
- <para>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>clients per DC</primary></indexterm>
- If the domain controller provides only network logon services
- and all file and print activity is handled by domain member servers, one domain
- controller per 150 clients on a single network segment may suffice. In any
- case, it is highly recommended to have a minimum of one domain controller (PDC or BDC)
- per network segment. It is better to have at least one BDC on the network
- segment that has a PDC. If the domain controller is also used as a file and
- print server, the number of clients it can service reliably is reduced,
- and generally for low powered hardware should not exceed 30 machines (Windows
- workstations plus domain member servers) per domain controller. Many sites are
- able to operate with more clients per domain controller, the number of clients
- that can be supported is limited by the CPU speed, memory and the workload on
- the Samba server as well as network bandwidth utilization.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Slow logons and log-offs</term>
- <listitem><para>
- <indexterm><primary>slow logon</primary></indexterm>
- Slow logons and log-offs may be caused by many factors that include:
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>NetBIOS</primary><secondary>name resolution</secondary><tertiary>delays</tertiary></indexterm>
- <indexterm><primary>WINS</primary><secondary>server</secondary></indexterm>
- Excessive delays in the resolution of a NetBIOS name to its IP
- address. This may be observed when an overloaded domain controller
- is also the WINS server. Another cause may be the failure to use
- a WINS server (this assumes that there is a single network segment).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>traffic collisions</primary></indexterm>
- <indexterm><primary>HUB</primary></indexterm>
- <indexterm><primary>ethernet switch</primary></indexterm>
- Network traffic collisions due to overloading of the network
- segment. One short-term workaround to this may be to replace
- network HUBs with Ethernet switches.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>networking hardware</primary><secondary>defective</secondary></indexterm>
- Defective networking hardware. Over the past few years, we have seen
- on the Samba mailing list a significant increase in the number of
- problems that were traced to a defective network interface controller,
- a defective HUB or Ethernet switch, or defective cabling. In most cases,
- it was the erratic nature of the problem that ultimately pointed to
- the cause of the problem.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>profile</primary><secondary>roaming</secondary></indexterm>
- <indexterm><primary>MS Outlook</primary><secondary>PST file</secondary></indexterm>
- Excessively large roaming profiles. This type of problem is typically
- the result of poor user education as well as poor network management.
- It can be avoided by users not storing huge quantities of email in
- MS Outlook PST files as well as by not storing files on the desktop.
- These are old bad habits that require much discipline and vigilance
- on the part of network management.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>WebClient</primary></indexterm>
- You should verify that the Windows XP WebClient service is not running.
- The use of the WebClient service has been implicated in many Windows
- networking-related problems.
- </para></listitem>
- </itemizedlist>
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Loss of access to network drives and printer resources</term>
- <listitem><para>
- Loss of access to network resources during client operation may be caused by a number
- of factors, including:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>network</primary><secondary>overload</secondary></indexterm>
- Network overload (typically indicated by a high network collision rate)
- </para></listitem>
-
- <listitem><para>
- Server overload
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>network</primary><secondary>timeout</secondary></indexterm>
- Timeout causing the client to close a connection that is in use but has
- been latent (no traffic) for some time (5 minutes or more)
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>network hardware</primary><secondary>defective</secondary></indexterm>
- Defective networking hardware
- </para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>data</primary><secondary>corruption</secondary></indexterm>
- No matter what the cause, a sudden loss of access to network resources can
- result in BSOD (blue screen of death) situations that necessitate rebooting of the client
- workstation. In the case of a mild problem, retrying to access the network drive of the printer
- may restore operations, but in any case this is a serious problem that may lead to the next
- problem, data corruption.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Potential data corruption</term>
- <listitem><para>
- <indexterm><primary>data</primary><secondary>corruption</secondary></indexterm>
- Data corruption is one of the most serious problems. It leads to uncertainty, anger, and
- frustration, and generally precipitates immediate corrective demands. Management response
- to this type of problem may be rational, as well as highly irrational. There have been
- cases where management has fired network staff for permitting this situation to occur without
- immediate correction. There have been situations where perfectly functional hardware was thrown
- out and replaced, only to find the problem caused by a low-cost network hardware item. There
- have been cases where server operating systems were replaced, or where Samba was updated,
- only to later isolate the problem due to defective client software.
- </para></listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- In this chapter, you can work through a number of measures that significantly arm you to
- anticipate and combat network performance issues. You can work through complex and thorny
- methods to improve the reliability of your network environment, but be warned that all such steps
- demand the price of complexity.
- </para>
-
-<sect1>
-<title>Regarding LDAP Directories and Windows Computer Accounts</title>
-
- <para>
- <indexterm><primary>LDAP</primary><secondary>directory</secondary></indexterm>
- Computer (machine) accounts can be placed wherever you like in an LDAP directory subject to some
- constraints that are described in this section.
- </para>
-
- <para>
- <indexterm><primary>POSIX</primary></indexterm>
- <indexterm><primary>SambaSAMAccount</primary></indexterm>
- <indexterm><primary>machine account</primary></indexterm>
- <indexterm><primary>trust account</primary></indexterm>
- The POSIX and SambaSAMAccount components of computer (machine) accounts are both used by Samba.
- That is, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
- them. A user account and a machine account are indistinguishable from each other, except that
- the machine account ends in a $ character, as do trust accounts.
- </para>
-
- <para>
- <indexterm><primary>account</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- The need for Windows user, group, machine, trust, and other such accounts to be tied to a valid UNIX UID
- is a design decision that was made a long way back in the history of Samba development. It is
- unlikely that this decision will be reversed or changed during the remaining life of the
- Samba-3.x series.
- </para>
-
- <para>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
- must refer back to the host operating system on which Samba is running. The name service
- switch (NSS) is the preferred mechanism that shields applications (like Samba) from the
- need to know everything about every host OS it runs on.
- </para>
-
- <para>
- Samba asks the host OS to provide a UID via the <quote>passwd</quote>, <quote>shadow</quote>
- and <quote>group</quote> facilities in the NSS control (configuration) file. The best tool
- for achieving this is left up to the UNIX administrator to determine. It is not imposed by
- Samba. Samba provides winbindd together with its support libraries as one method. It is
- possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
- all account entities can be located in an LDAP directory.
- </para>
-
- <para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
- be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
- is fundamentally an LDAP design question. The information provided on the Samba list and
- in the documentation is directed at providing working examples only. The design
- of an LDAP directory is a complex subject that is beyond the scope of this documentation.
- </para>
-
-</sect1>
-
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- You just opened an email from Christine that reads:
- </para>
-
- <para>
- Good morning,
- <blockquote><attribution>Christine</attribution><para>
- A few months ago we sat down to design the network. We discussed the challenges ahead and we all
- agreed to compromise our design to keep it simple. We knew there would be problems, but anticipated
- that we would have some time to resolve any issues that might be encountered.
- </para>
-
- <para>
- As you now know, we started off on the wrong foot. We have a lot of unhappy users. One of them
- resigned yesterday afternoon because she was under duress to complete some critical projects. She
- suffered a blue screen of death situation just as she was finishing four hours of intensive work, all
- of which was lost. She has a unique requirement that involves storing large files on her desktop.
- Mary's desktop profile is nearly 1 GB in size. As a result of her desktop configuration, it
- takes her nearly 15 minutes just to log onto her workstation. But that is not enough. Because all
- network logon traffic passes over the network links between our buildings, logging on may take
- three or four attempts due to blue screen problems associated with network timeouts.
- </para>
-
- <para>
- A few of us worked to help her out of trouble. We convinced her to stay and promised to fully
- resolve the difficulties she is facing. We have no choice. We must implement LDAP and set hard
- limits on what our users can do with their desktops. Otherwise, we face staff losses
- that can surely do harm to our growth as well as to staff morale. I am sure we can better deal
- with the consequences of what we know we must do than we can with the unrest we have now.
- </para>
-
- <para>
- Stan and I have discussed the current situation. We are resolved to help our users and protect
- the well being of Abmas. Please acknowledge this advice with consent to proceed as required to
- regain control of our vital IT operations.
- </para></blockquote>
- </para>
-
- <para>
- <indexterm><primary>compromise</primary></indexterm>
- <indexterm><primary>network</primary><secondary>multi-segment</secondary></indexterm>
- Every compromise has consequences. Having a large routed (i.e., multisegment) network with only a
- single domain controller is a poor design that has obvious operational effects that may
- frustrate users. Here is your reply:
- </para>
-
- <blockquote><attribution>Bob</attribution><para>
- Christine, Your diligence and attention to detail are much valued. Stan and I fully support your
- proposals to resolve the issues. I am confident that your plans fully realized will significantly
- boost staff morale. Please go ahead with your plans. If you have any problems, please let me know.
- Please let Stan know what the estimated cost will be so I can approve the expense. Do not wait
- for approval; I appreciate the urgency.
- </para></blockquote>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- The priority of assigned tasks in this chapter is:
- </para>
-
- <orderedlist>
- <listitem><para>
- <indexterm><primary>Backup Domain Controller</primary><see>BDC</see></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm><indexterm><primary>migration</primary></indexterm>
- Implement Backup Domain Controllers (BDCs) in each building. This involves
- a change from a <emphasis>tdbsam</emphasis> backend that was used in the previous
- chapter to an LDAP-based backend.
- </para>
-
- <para>
- You can implement a single central LDAP server for this purpose.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>logon time</primary></indexterm>
- <indexterm><primary>network share</primary></indexterm>
- <indexterm><primary>default profile</primary></indexterm>
- <indexterm><primary>profile</primary><secondary>default</secondary></indexterm>
- Rectify the problem of excessive logon times. This involves redirection of
- folders to network shares as well as modification of all user desktops to
- exclude the redirected folders from being loaded at login time. You can also
- create a new default profile that can be used for all new users.
- </para></listitem>
- </orderedlist>
-
- <para>
- <indexterm><primary>disk image</primary></indexterm>
- You configure a new MS Windows XP Professional workstation disk image that you roll out
- to all desktop users. The instructions you have created are followed on a staging machine
- from which all changes can be carefully tested before inflicting them on your network users.
- </para>
-
- <para>
- <indexterm><primary>CUPS</primary></indexterm>
- This is the last network example in which specific mention of printing is made. The example
- again makes use of the CUPS printing system.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>OpenLDAP</primary></indexterm>
- The implementation of Samba BDCs necessitates the installation and configuration of LDAP.
- For this site, you use OpenLDAP, the open source software LDAP server platform. Commercial
- LDAP servers in current use with Samba include:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>eDirectory</primary></indexterm>
- Novell <ulink url="http://www.novell.com/products/edirectory/">eDirectory</ulink>
- is being successfully used by some sites. Information on how to use eDirectory can be
- obtained from the Samba mailing lists or from Novell.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Tivoli Directory Server</primary></indexterm>
- IBM <ulink url="http://www-306.ibm.com/software/tivoli/products/directory-server/">Tivoli
- Directory Server</ulink> can be used to provide the Samba LDAP backend. Example schema
- files are provided in the Samba source code tarball under the directory
- <filename>~samba/example/LDAP.</filename>
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Sun ONE Identity Server</primary></indexterm>
- Sun <ulink url="http://www.sun.com/software/software/products/identity_srvr/home_identity.xml">ONE Identity
- Server product suite</ulink> provides an LDAP server that can be used for Samba.
- Example schema files are provided in the Samba source code tarball under the directory
- <filename>~samba/example/LDAP.</filename>
- </para></listitem>
- </itemizedlist>
-
- <para>
- A word of caution is fully in order. OpenLDAP is purely an LDAP server, and unlike commercial
- offerings, it requires that you manually edit the server configuration files and manually
- initialize the LDAP directory database. OpenLDAP itself has only command-line tools to
- help you to get OpenLDAP and Samba running as required, albeit with some learning curve challenges.
- </para>
-
- <para>
- <indexterm><primary>Active Directory</primary></indexterm>
- For most sites, the deployment of Microsoft Active Directory from the shrink-wrapped installation is quite
- adequate. If you are migrating from Microsoft Active Directory, be warned that OpenLDAP does not include
- GUI-based directory management tools. Even a simple task such as adding users to the OpenLDAP database
- requires an understanding of what you are doing, why you are doing it, and the tools that you must use.
- </para>
-
- <para>
- <indexterm><primary>Identity Management</primary></indexterm>
- <indexterm><primary>high availability</primary></indexterm>
- <indexterm><primary>directory</primary><secondary>replication</secondary></indexterm>
- <indexterm><primary>directory</primary><secondary>synchronization</secondary></indexterm>
- <indexterm><primary>performance</primary></indexterm>
- <indexterm><primary>directory</primary><secondary>management</secondary></indexterm>
- <indexterm><primary>directory</primary><secondary>schema</secondary></indexterm>
- When installed and configured, an OpenLDAP Identity Management backend for Samba functions well.
- High availability operation may be obtained through directory replication/synchronization and
- master/slave server configurations. OpenLDAP is a mature platform to host the organizational
- directory infrastructure that can include all UNIX accounts, directories for electronic mail, and much more.
- The price paid through learning how to design an LDAP directory schema in implementation and configuration
- of management tools is well rewarded by performance and flexibility and the freedom to manage directory
- contents with greater ability to back up, restore, and modify the directory than is generally possible
- with Microsoft Active Directory.
- </para>
-
- <para>
- <indexterm><primary>comparison</primary><secondary>Active Directory & OpenLDAP</secondary></indexterm>
- <indexterm><primary>ADAM</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>OpenLDAP</primary></indexterm>
- A comparison of OpenLDAP with Microsoft Active Directory does not do justice to either. OpenLDAP is an LDAP directory
- tool-set. Microsoft Active Directory Server is an implementation of an LDAP server that is largely preconfigured
- for a specific task orientation. It comes with a set of administrative tools that is entirely customized
- for the purpose of running MS Windows applications that include file and print services, Microsoft Exchange
- server, Microsoft SQL server, and more. The complexity of OpenLDAP is highly valued by the UNIX administrator
- who wants to build a custom directory solution. Microsoft provides an application called
- <ulink url="http://www.microsoft.com/windowsserver2003/adam/default.mspx">
- MS ADAM</ulink> that provides more generic LDAP services, yet it does not have the vanilla-like services
- of OpenLDAP.
- </para>
-
- <para>
- <indexterm><primary>directory</primary><secondary>schema</secondary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- You may wish to consider outsourcing the development of your OpenLDAP directory to an expert, particularly
- if you find the challenge of learning about LDAP directories, schemas, configuration, and management
- tools and the creation of shell and Perl scripts a bit
- challenging. OpenLDAP can be easily customized, though it includes
- many ready-to-use schemas. Samba provides an OpenLDAP schema file
- that is required for use as a passdb backend.
- </para>
-
- <para>
- <indexterm><primary>interoperability</primary></indexterm>
- For those who are willing to brave the process of installing and configuring LDAP and Samba interoperability,
- there are a few nice Web-based tools that may help you to manage your users and groups more effectively.
- The Web-based tools you might like to consider include the
- <ulink url="http://lam.sourceforge.net/">LDAP Account Manager</ulink> (LAM) and the Webmin-based
- <ulink url="http://www.webmin.com">Webmin</ulink> Idealx
- <ulink url="http://webmin.idealx.org/index.en.html">CGI tools</ulink>.
- </para>
-
- <para>
- Some additional LDAP tools should be mentioned. Every so often a Samba user reports using one of
- these, so it may be useful to them:
- <ulink url="http://biot.com/gq">GQ</ulink>, a GTK-based LDAP browser;
- LDAP <ulink url="http://www.iit.edu/~gawojar/ldap/">Browser/Editor</ulink>
- <ulink url="http://www.jxplorer.org/">; JXplorer</ulink> (by Computer Associates);
- and <ulink url="http://phpldapadmin.sourceforge.net/">phpLDAPadmin</ulink>.
- </para>
-
- <note><para>
- The following prescriptive guidance is not an LDAP tutorial. The LDAP implementation expressly uses minimal
- security controls. No form of secure LDAP communications is attempted. The LDAP configuration information provided
- is considered to consist of the barest essentials only. You are strongly encouraged to learn more about
- LDAP before attempting to deploy it in a business-critical environment.
- </para></note>
-
- <para>
- Information to help you get started with OpenLDAP is available from the
- <ulink url="http://www.openldap.org/pub/">OpenLDAP web site</ulink>. Many people have found the book
- <ulink url="http://www.oreilly.com/catalog/ldapsa/index.html"><emphasis>LDAP System Administration</emphasis>,</ulink>
- by Jerry Carter quite useful.
- </para>
-
- <para>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>network</primary><secondary>segment</secondary></indexterm>
- <indexterm><primary>performance</primary></indexterm>
- <indexterm><primary>network</primary><secondary>wide-area</secondary></indexterm>
- Mary's problems are due to two factors. First, the absence of a domain controller on the local network is the
- main cause of the errors that result in blue screen crashes. Second, Mary has a large profile that must
- be loaded over the WAN connection. The addition of BDCs on each network segment significantly
- improves overall network performance for most users, but it is not enough. You must gain control over
- user desktops, and this must be done in a way that wins their support and does not cause further loss of
- staff morale. The following procedures solve this problem.
- </para>
-
- <para>
- <indexterm><primary>smart printing</primary></indexterm>
- There is also an opportunity to implement smart printing features. You add this to the Samba configuration
- so that future printer changes can be managed without need to change desktop configurations.
- </para>
-
- <para>
- You add the ability to automatically download new printer drivers, even if they are not installed
- in the default desktop profile. Only one example of printing configuration is given. It is assumed that
- you can extrapolate the principles and use them to install all printers that may be needed.
- </para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- <indexterm><primary>identity</primary><secondary>management</secondary></indexterm>
- <indexterm><primary>directory</primary><secondary>server</secondary></indexterm>
- <indexterm><primary>Posix</primary></indexterm>
- The solution provided is a minimal approach to getting OpenLDAP running as an identity management directory
- server for UNIX system accounts as well as for Samba. From the OpenLDAP perspective, UNIX system
- accounts are stored POSIX schema extensions. Samba provides its own schema to permit storage of account
- attributes Samba needs. Samba can use the LDAP backend to store:
- </para>
-
- <itemizedlist>
- <listitem><para>Windows Networking User Accounts</para></listitem>
- <listitem><para>Windows NT Group Accounts</para></listitem>
- <listitem><para>Mapping Information between UNIX Groups and Windows NT Groups</para></listitem>
- <listitem><para>ID Mappings for SIDs to UIDs (also for foreign Domain SIDs)</para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>UNIX accounts</primary></indexterm>
- <indexterm><primary>Windows accounts</primary></indexterm>
- <indexterm><primary>PADL LDAP tools</primary></indexterm>
- <indexterm><primary>/etc/group</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>name service switch</primary><see>NSS</see></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>nss_ldap</primary></indexterm>
- The use of LDAP with Samba makes it necessary to store UNIX accounts as well as Windows Networking
- accounts in the LDAP backend. This implies the need to use the
- <ulink url="http://www.padl.com/Contents/OpenSourceSoftware.html">PADL LDAP tools</ulink>. The resolution
- of the UNIX group name to its GID must be enabled from either the <filename>/etc/group</filename>
- or from the LDAP backend. This requires the use of the PADL <filename>nss_ldap</filename> tool-set
- that integrates with the NSS. The same requirements exist for resolution
- of the UNIX username to the UID. The relationships are demonstrated in <link linkend="sbehap-LDAPdiag"/>.
- </para>
-
- <figure id="sbehap-LDAPdiag">
- <title>The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts</title>
- <imagefile scale="50">UNIX-Samba-and-LDAP</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>security</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>secure</secondary></indexterm>
- You configure OpenLDAP so that it is operational. Before deploying the OpenLDAP, you really
- ought to learn how to configure secure communications over LDAP so that site security is not
- at risk. This is not covered in the following guidance.
- </para>
-
- <para>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>LDAP Interchange Format</primary><see>LDIF</see></indexterm>
- <indexterm><primary>LDIF</primary></indexterm>
- <indexterm><primary>secrets.tdb</primary></indexterm>
- When OpenLDAP has been made operative, you configure the PDC called <constant>MASSIVE</constant>.
- You initialize the Samba <filename>secrets.tdb<subscript></subscript></filename> file. Then you
- create the LDAP Interchange Format (LDIF) file from which the LDAP database can be initialized.
- You need to decide how best to create user and group accounts. A few hints are, of course, provided.
- You can also find on the enclosed CD-ROM, in the <filename>Chap06</filename> directory, a few tools
- that help to manage user and group configuration.
- </para>
-
- <para>
- <indexterm><primary>folder redirection</primary></indexterm>
- <indexterm><primary>default profile</primary></indexterm>
- <indexterm><primary>roaming profile</primary></indexterm>
- In order to effect folder redirection and to add robustness to the implementation,
- create a network default profile. All network users workstations are configured to use
- the new profile. Roaming profiles will automatically be deleted from the workstation
- when the user logs off.
- </para>
-
- <para>
- <indexterm><primary>mandatory profile</primary></indexterm>
- The profile is configured so that users cannot change the appearance
- of their desktop. This is known as a mandatory profile. You make certain that users
- are able to use their computers efficiently.
- </para>
-
- <para>
- <indexterm><primary>logon script</primary></indexterm>
- A network logon script is used to deliver flexible but consistent network drive
- connections.
- </para>
-
- <sect3 id="sbehap-ppc">
- <title>Addition of Machines to the Domain</title>
-
- <para>
- <indexterm><primary></primary></indexterm>
- <indexterm><primary></primary></indexterm>
- <indexterm><primary></primary></indexterm>
- <indexterm><primary></primary></indexterm>
- Samba versions prior to 3.0.11 necessitated the use of a domain administrator account
- that maps to the UNIX UID=0. The UNIX operating system permits only the <constant>root</constant>
- user to add user and group accounts. Samba 3.0.11 introduced a new facility known as
- <constant>Privileges</constant>, which provides five new privileges that
- can be assigned to users and/or groups; see Table 5.1.
- </para>
-
-
- <table id="sbehap-privs">
- <title>Current Privilege Capabilities</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry align="left">Privilege</entry>
- <entry align="left">Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><para>SeMachineAccountPrivilege</para></entry>
- <entry><para>Add machines to domain</para></entry>
- </row>
- <row>
- <entry><para>SePrintOperatorPrivilege</para></entry>
- <entry><para>Manage printers</para></entry>
- </row>
- <row>
- <entry><para>SeAddUsersPrivilege</para></entry>
- <entry><para>Add users and groups to the domain</para></entry>
- </row>
- <row>
- <entry><para>SeRemoteShutdownPrivilege</para></entry>
- <entry><para>Force shutdown from a remote system</para></entry>
- </row>
- <row>
- <entry><para>SeDiskOperatorPrivilege</para></entry>
- <entry><para>Manage disk share</para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- In this network example use is made of one of the supported privileges purely to demonstrate
- how any user can now be given the ability to add machines to the domain using a normal user account
- that has been given the appropriate privileges.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Roaming Profile Background</title>
-
- <para>
- As XP roaming profiles grow, so does the amount of time it takes to log in and out.
- </para>
-
- <para>
- <indexterm><primary>roaming profile</primary></indexterm>
- <indexterm><primary>HKEY_CURRENT_USER</primary></indexterm>
- <indexterm><primary>NTUSER.DAT</primary></indexterm>
- <indexterm><primary>%USERNAME%</primary></indexterm>
- An XP roaming profile consists of the <constant>HKEY_CURRENT_USER</constant> hive file
- <filename>NTUSER.DAT</filename> and a number of folders (My Documents, Application Data,
- Desktop, Start Menu, Templates, NetHood, Favorites, and so on). When a user logs onto the
- network with the default configuration of MS Windows NT/200x/XPP, all this data is
- copied to the local machine under the <filename>C:\Documents and Settings\%USERNAME%</filename>
- directory. While the user is logged in, any changes made to any of these folders or to the
- <constant>HKEY_CURRENT_USER</constant> branch of the registry are made to the local copy
- of the profile. At logout the profile data is copied back to the server. This behavior
- can be changed through appropriate registry changes and/or through changes to the default
- user profile. In the latter case, it updates the registry with the values that are set in the
- profile <filename>NTUSER.DAT</filename>
- file.
- </para>
-
- <para>
- The first challenge is to reduce the amount of data that must be transferred to and
- from the profile server as roaming profiles are processed. This includes removing
- all the shortcuts in the Recent directory, making sure the cache used by the Web browser
- is not being dumped into the <filename>Application Data</filename> folder, removing the
- Java plug-ins cache (the .jpi_cache directory in the profile), as well as training the
- user to not place large files on the desktop and to use his or her mapped home directory
- instead of the <filename>My Documents</filename> folder for saving documents.
- </para>
-
- <para>
- <indexterm><primary>My Documents</primary></indexterm>
- Using a folder other than <filename>My Documents</filename> is a nuisance for
- some users, since many applications use it by default.
- </para>
-
- <para>
- <indexterm><primary>roaming profiles</primary></indexterm>
- <indexterm><primary>Local Group Policy</primary></indexterm>
- <indexterm><primary>NTUSER.DAT</primary></indexterm>
- The secret to rapid loading of roaming profiles is to prevent unnecessary data from
- being copied back and forth, without losing any functionality. This is not difficult;
- it can be done by making changes to the Local Group Policy on each client as well
- as changing some paths in each user's <filename>NTUSER.DAT</filename> hive.
- </para>
-
- <para>
- <indexterm><primary>Network Default Profile</primary></indexterm>
- <indexterm><primary>redirected folders</primary></indexterm>
- Every user profile has its own <filename>NTUSER.DAT</filename> file. This means
- you need to edit every user's profile, unless a better method can be
- followed. Fortunately, with the right preparations, this is not difficult.
- It is possible to remove the <filename>NTUSER.DAT</filename> file from each
- user's profile. Then just create a Network Default Profile. Of course, it is
- necessary to copy all files from redirected folders to the network share to which
- they are redirected.
- </para>
-
- </sect3>
-
- <sect3 id="sbehap-locgrppol">
- <title>The Local Group Policy</title>
-
- <para>
- <indexterm><primary>Group Policy Objects</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>Group Policy editor</primary></indexterm>
- Without an Active Directory PDC, you cannot take full advantage of Group Policy
- Objects. However, you can still make changes to the Local Group Policy by using
- the Group Policy editor (<command>gpedit.msc</command>).
- </para>
-
- <para>
- The <emphasis>Exclude directories in roaming profile</emphasis> settings can
- be found under
- <menuchoice>
- <guimenu>User Configuration</guimenu>
- <guimenuitem>Administrative Templates</guimenuitem>
- <guimenuitem>System</guimenuitem>
- <guimenuitem>User Profiles</guimenuitem>
- </menuchoice>.
- By default this setting contains
- <quote>Local Settings; Temporary Internet Files; History; Temp</quote>.
- </para>
-
- <para>
- Simply add the folders you do not wish to be copied back and forth to this
- semicolon-separated list. Note that this change must be made on all clients
- that are using roaming profiles.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Profile Changes</title>
-
- <para>
- <indexterm><primary>NTUSER.DAT</primary></indexterm>
- <indexterm><primary>%USERNAME%</primary></indexterm>
- There are two changes that should be done to each user's profile. Move each of
- the directories that you have excluded from being copied back and forth out of
- the usual profile path. Modify each user's <filename>NTUSER.DAT</filename> file
- to point to the new paths that are shared over the network instead of to the default
- path (<filename>C:\Documents and Settings\%USERNAME%</filename>).
- </para>
-
- <para>
- <indexterm><primary>Default User</primary></indexterm>
- <indexterm><primary>regedt32</primary></indexterm>
- The above modifies existing user profiles. So that newly created profiles have
- these settings, you need to modify the <filename>NTUSER.DAT</filename> in
- the <filename>C:\Documents and Settings\Default User</filename> folder on each
- client machine, changing the same registry keys. You could do this by copying
- <filename>NTUSER.DAT</filename> to a Linux box and using <command>regedt32</command>.
- The basic method is described under <link linkend="redirfold"/>.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Using a Network Default User Profile</title>
-
- <para>
- <indexterm><primary>NETLOGON</primary></indexterm>
- <indexterm><primary>NTUSER.DAT</primary></indexterm>
- If you are using Samba as your PDC, you should create a file share called
- <constant>NETLOGON</constant> and within that create a directory called
- <filename>Default User</filename>, which is a copy of the desired default user
- configuration (including a copy of <filename>NTUSER.DAT</filename>).
- If this share exists and the <filename>Default User</filename> folder exists,
- the first login from a new account pulls its configuration from it.
- See also <ulink url="http://isg.ee.ethz.ch/tools/realmen/det/skel.en.html">
- the Real Men Don't Click</ulink> Web site.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Installation of Printer Driver Auto-Download</title>
-
- <para>
- <indexterm><primary>printing</primary><secondary>dumb</secondary></indexterm>
- <indexterm><primary>dumb printing</primary></indexterm>
- <indexterm><primary>Raw Print Through</primary></indexterm>
- The subject of printing is quite topical. Printing problems run second place to name
- resolution issues today. So far in this book, you have experienced only what is generally
- known as <quote>dumb</quote> printing. Dumb printing is the arrangement by which all drivers
- are manually installed on each client and the printing subsystems perform no filtering
- or intelligent processing. Dumb printing is easily understood. It usually works without
- many problems, but it has its limitations also. Dumb printing is better known as
- <command>Raw-Print-Through</command> printing.
- </para>
-
- <para>
- <indexterm><primary>printing</primary><secondary>drag-and-drop</secondary></indexterm>
- <indexterm><primary>printing</primary><secondary>point-n-click</secondary></indexterm>
- Samba permits the configuration of <command>smart</command> printing using the Microsoft
- Windows point-and-click (also called drag-and-drop) printing. What this provides is
- essentially the ability to print to any printer. If the local client does not yet have a
- driver installed, the driver is automatically downloaded from the Samba server and
- installed on the client. Drag-and-drop printing is neat; it means the user never needs
- to fuss with driver installation, and that is a <trademark>Good Thing,</trademark>
- isn't it?
- </para>
-
- <para>
- There is a further layer of print job processing that is known as <command>intelligent</command>
- printing that automatically senses the file format of data submitted for printing and
- then invokes a suitable print filter to convert the incoming data stream into a format
- suited to the printer to which the job is dispatched.
- </para>
-
- <para>
- <indexterm><primary>CUPS</primary></indexterm>
- <indexterm><primary>Easy Software Products</primary></indexterm>
- <indexterm><primary>Postscript</primary></indexterm>
- The CUPS printing subsystem is capable of intelligent printing. It has the capacity to
- detect the data format and apply a print filter. This means that it is feasible to install
- on all Windows clients a single printer driver for use with all printers that are routed
- through CUPS. The most sensible driver to use is one for a PostScript printer. Fortunately,
- <ulink url="http://www.easysw.com">Easy Software Products</ulink>, the authors of CUPS, have
- released a PostScript printing driver for Windows. It can be installed into the Samba
- printing backend so that it automatically downloads to the client when needed.
- </para>
-
- <para>
- This means that so long as there is a CUPS driver for the printer, all printing from Windows
- software can use PostScript, no matter what the actual printer language for the physical
- device is. It also means that the administrator can swap out a printer with a totally
- different type of device without ever needing to change a client workstation driver.
- </para>
-
- <para>
- This book is about Samba, so you can confine the printing style to just the smart
- style of installation. Those interested in further information regarding intelligent
- printing should review documentation on the Easy Software Products Web site.
- </para>
-
- </sect3>
-
- <sect3 id="sbeavoid">
- <title>Avoiding Failures: Solving Problems Before They Happen</title>
-
- <para>
- It has often been said that there are three types of people in the world: those who
- have sharp minds and those who forget things. Please do not ask what the third group
- is like! Well, it seems that many of us have company in the second group. There must
- be a good explanation why so many network administrators fail to solve apparently
- simple problems efficiently and effectively.
- </para>
-
- <para>
- Here are some diagnostic guidelines that can be referred to when things go wrong:
- </para>
-
- <sect4>
- <title>Preliminary Advice: Dangers Can Be Avoided</title>
-
- <para>
- The best advice regarding how to mend a broken leg is <quote>Never break a leg!</quote>
- </para>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- Newcomers to Samba and LDAP seem to struggle a great deal at first. If you want advice
- regarding the best way to remedy LDAP and Samba problems: <quote>Avoid them like the plague!</quote>
- </para>
-
- <para>
- If you are now asking yourself how problems can be avoided, the best advice is to start
- out your learning experience with a <emphasis>known-good configuration.</emphasis> After
- you have seen a fully working solution, a good way to learn is to make slow and progressive
- changes that cause things to break, then observe carefully how and why things ceased to work.
- </para>
-
- <para>
- The examples in this chapter (also in the book as a whole) are known to work. That means
- that they could serve as the kick-off point for your journey through fields of knowledge.
- Use this resource carefully; we hope it serves you well.
- </para>
-
- <warning><para>
- Do not be lulled into thinking that you can easily adopt the examples in this
- book and adapt them without first working through the examples provided. A little
- thing overlooked can cause untold pain and may permanently tarnish your experience.
- </para></warning>
-
- </sect4>
-
- <sect4>
- <title>The Name Service Caching Daemon</title>
-
- <para>
- The name service caching daemon (nscd) is a primary cause of difficulties with name
- resolution, particularly where <command>winbind</command> is used. Winbind does its
- own caching, thus nscd causes double caching which can lead to peculiar problems during
- debugging. As a rule, it is a good idea to turn off the name service caching daemon.
- </para>
-
- <para>
- Operation of the name service caching daemon is controlled by the
- <filename>/etc/nscd.conf</filename> file. Typical contents of this file are as follows:
-<screen>
-# /etc/nscd.conf
-# An example Name Service Cache config file. This file is needed by nscd.
-# Legal entries are:
-# logfile <file>
-# debug-level <level>
-# threads <threads to use>
-# server-user <user to run server as instead of root>
-# server-user is ignored if nscd is started with -S parameters
-# stat-user <user who is allowed to request statistics>
-# reload-count unlimited|<number>
-#
-# enable-cache <service> <yes|no>
-# positive-time-to-live <service> <time in seconds>
-# negative-time-to-live <service> <time in seconds>
-# suggested-size <service> <prime number>
-# check-files <service> <yes|no>
-# persistent <service> <yes|no>
-# shared <service> <yes|no>
-# Currently supported cache names (services): passwd, group, hosts
-# logfile /var/log/nscd.log
-# threads 6
-# server-user nobody
-# stat-user somebody
- debug-level 0
-# reload-count 5
- enable-cache passwd yes
- positive-time-to-live passwd 600
- negative-time-to-live passwd 20
- suggested-size passwd 211
- check-files passwd yes
- persistent passwd yes
- shared passwd yes
- enable-cache group yes
- positive-time-to-live group 3600
- negative-time-to-live group 60
- suggested-size group 211
- check-files group yes
- persistent group yes
- shared group yes
-# !!!!!WARNING!!!!! Host cache is insecure!!! The mechanism in nscd to
-# cache hosts will cause your local system to not be able to trust
-# forward/reverse lookup checks. DO NOT USE THIS if your system relies on
-# this sort of security mechanism. Use a caching DNS server instead.
- enable-cache hosts no
- positive-time-to-live hosts 3600
- negative-time-to-live hosts 20
- suggested-size hosts 211
- check-files hosts yes
- persistent hosts yes
- shared hosts yes
-</screen>
- It is feasible to comment out the <constant>passwd</constant> and <constant>group</constant>
- entries so they will not be cached. Alternatively, it is often simpler to just disable the
- <command>nscd</command> service by executing (on Novell SUSE Linux):
-<screen>
-&rootprompt; chkconfig nscd off
-&rootprompt; rcnscd off
-</screen>
- </para>
-
- </sect4>
-
- <sect4>
- <title>Debugging LDAP</title>
-
- <para>
- <indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
- <indexterm><primary>loglevel</primary></indexterm>
- <indexterm><primary>slapd</primary></indexterm>
- In the example <filename>/etc/openldap/slapd.conf</filename> control file
- (see <link linkend="sbehap-dbconf"/>) there is an entry for <constant>loglevel 256</constant>.
- To enable logging via the syslog infrastructure, it is necessary to uncomment this parameter
- and restart <command>slapd</command>.
- </para>
-
- <para>
- <indexterm><primary>/etc/syslog.conf</primary></indexterm>
- <indexterm><primary>/var/log/ldaplogs</primary></indexterm>
- LDAP log information can be directed into a file that is separate from the normal system
- log files by changing the <filename>/etc/syslog.conf</filename> file so it has the following
- contents:
-<screen>
-# Some foreign boot scripts require local7
-#
-local0,local1.* -/var/log/localmessages
-local2,local3.* -/var/log/localmessages
-local5.* -/var/log/localmessages
-local6,local7.* -/var/log/localmessages
-local4.* -/var/log/ldaplogs
-</screen>
- In this case, all LDAP-related logs will be directed to the file
- <filename>/var/log/ldaplogs</filename>. This makes it easy to track LDAP errors.
- The snippet provides a simple example of usage that can be modified to suit
- local site needs. The configuration used later in this chapter reflects such
- customization with the intent that LDAP log files will be stored at a location
- that meets local site needs and wishes more fully.
- </para>
-
- </sect4>
-
- <sect4>
- <title>Debugging NSS_LDAP</title>
-
- <para>
- The basic mechanism for diagnosing problems with the nss_ldap utility involves adding to the
- <filename>/etc/ldap.conf</filename> file the following parameters:
-<screen>
-debug 256
-logdir /data/logs
-</screen>
- Create the log directory as follows:
-<screen>
-&rootprompt; mkdir /data/logs
-</screen>
- </para>
-
-<?latex \newpage ?>
-
- <para>
- The diagnostic process should follow these steps:
- </para>
-
- <procedure>
- <title>NSS_LDAP Diagnostic Steps</title>
-
- <step><para>
- Verify the <constant>nss_base_passwd, nss_base_shadow, nss_base_group</constant> entries
- in the <filename>/etc/ldap.conf</filename> file and compare them closely with the directory
- tree location that was chosen when the directory was first created.
- </para>
-
- <para>
- One way this can be done is by executing:
-<screen>
-&rootprompt; slapcat | grep Group | grep dn
-dn: ou=Groups,dc=abmas,dc=biz
-dn: cn=Domain Admins,ou=Groups,dc=abmas,dc=biz
-dn: cn=Domain Users,ou=Groups,dc=abmas,dc=biz
-dn: cn=Domain Guests,ou=Groups,dc=abmas,dc=biz
-dn: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
-dn: cn=Administrators,ou=Groups,dc=abmas,dc=biz
-dn: cn=Print Operators,ou=Groups,dc=abmas,dc=biz
-dn: cn=Backup Operators,ou=Groups,dc=abmas,dc=biz
-dn: cn=Replicators,ou=Groups,dc=abmas,dc=biz
-</screen>
- The first line is the DIT entry point for the container for POSIX groups. The correct entry
- for the <filename>/etc/ldap.conf</filename> for the <constant>nss_base_group</constant>
- parameter therefore is the distinguished name (dn) as applied here:
-<screen>
-nss_base_group ou=Groups,dc=abmas,dc=biz?one
-</screen>
- The same process may be followed to determine the appropriate dn for user accounts.
- If the container for computer accounts is not the same as that for users (see the &smb.conf;
- file entry for <constant>ldap machine suffix</constant>), it may be necessary to set the
- following DIT dn in the <filename>/etc/ldap.conf</filename> file:
-<screen>
-nss_base_passwd dc=abmas,dc=biz?sub
-</screen>
- This instructs LDAP to search for machine as well as user entries from the top of the DIT
- down. This is inefficient, but at least should work. Note: It is possible to specify multiple
- <constant>nss_base_passwd</constant> entries in the <filename>/etc/ldap.conf</filename> file; they
- will be evaluated sequentially. Let us consider an example of use where the following DIT
- has been implemented:
- </para>
-
- <para>
- <itemizedlist>
- <listitem><para>User accounts are stored under the DIT: ou=Users, dc=abmas, dc=biz</para></listitem>
- <listitem><para>User login accounts are under the DIT: ou=People, ou-Users, dc=abmas, dc=biz</para></listitem>
- <listitem><para>Computer accounts are under the DIT: ou=Computers, ou=Users, dc=abmas, dc=biz</para></listitem>
- </itemizedlist>
- </para>
-
- <para>
- The appropriate multiple entry for the <constant>nss_base_passwd</constant> directive
- in the <filename>/etc/ldap.conf</filename> file may be:
-<screen>
-nss_base_passwd ou=People,ou=Users,dc=abmas,dc=org?one
-nss_base_passwd ou=Computers,ou=Users,dc=abmas,dc=org?one
-</screen>
- </para></step>
-
- <step><para>
- Perform lookups such as:
-<screen>
-&rootprompt; getent passwd
-</screen>
- Each such lookup will create an entry in the <filename>/data/log</filename> directory
- for each such process executed. The contents of each file created in this directory
- may provide a hint as to the cause of the a problem that is under investigation.
- </para></step>
-
- <step><para>
- For additional diagnostic information, check the contents of the <filename>/var/log/messages</filename>
- to see what error messages are being generated as a result of the LDAP lookups. Here is an example of
- a successful lookup:
-<screen>
-slapd[12164]: conn=0 fd=10 ACCEPT from IP=127.0.0.1:33539
-(IP=0.0.0.0:389)
-slapd[12164]: conn=0 op=0 BIND dn="" method=128
-slapd[12164]: conn=0 op=0 RESULT tag=97 err=0 text=
-slapd[12164]: conn=0 op=1 SRCH base="" scope=0 deref=0
-filter="(objectClass=*)"
-slapd[12164]: conn=0 op=1 SEARCH RESULT tag=101 err=0
-nentries=1 text=
-slapd[12164]: conn=0 op=2 UNBIND
-slapd[12164]: conn=0 fd=10 closed
-slapd[12164]: conn=1 fd=10 ACCEPT from
-IP=127.0.0.1:33540 (IP=0.0.0.0:389)
-slapd[12164]: conn=1 op=0 BIND
-dn="cn=Manager,dc=abmas,dc=biz" method=128
-slapd[12164]: conn=1 op=0 BIND
-dn="cn=Manager,dc=abmas,dc=biz" mech=SIMPLE ssf=0
-slapd[12164]: conn=1 op=0 RESULT tag=97 err=0 text=
-slapd[12164]: conn=1 op=1 SRCH
-base="ou=People,dc=abmas,dc=biz" scope=1 deref=0
-filter="(objectClass=posixAccount)"
-slapd[12164]: conn=1 op=1 SRCH attr=uid userPassword
-uidNumber gidNumber cn
-homeDirectory loginShell gecos description objectClass
-slapd[12164]: conn=1 op=1 SEARCH RESULT tag=101 err=0
-nentries=2 text=
-slapd[12164]: conn=1 fd=10 closed
-
-</screen>
- </para></step>
-
- <step><para>
- Check that the bindpw entry in the <filename>/etc/ldap.conf</filename> or in the
- <filename>/etc/ldap.secrets</filename> file is correct, as specified in the
- <filename>/etc/openldap/slapd.conf</filename> file.
- </para></step>
-
- </procedure>
-
- </sect4>
-
- <sect4>
- <title>Debugging Samba</title>
-
- <para>
- The following parameters in the &smb.conf; file can be useful in tracking down Samba-related problems:
-<screen>
-[global]
- ...
- log level = 5
- log file = /var/log/samba/%m.log
- max log size = 0
- ...
-</screen>
- This will result in the creation of a separate log file for every client from which connections
- are made. The log file will be quite verbose and will grow continually. Do not forget to
- change these lines to the following when debugging has been completed:
-<screen>
-[global]
- ...
- log level = 1
- log file = /var/log/samba/%m.log
- max log size = 50
- ...
-</screen>
- </para>
-
- <para>
- The log file can be analyzed by executing:
-<screen>
-&rootprompt; cd /var/log/samba
-&rootprompt; grep -v "^\[200" machine_name.log
-</screen>
- </para>
-
- <para>
- Search for hints of what may have failed by looking for the words <emphasis>fail</emphasis>
- and <emphasis>error</emphasis>.
- </para>
-
- </sect4>
-
- <sect4>
- <title>Debugging on the Windows Client</title>
-
- <para>
- MS Windows 2000 Professional and Windows XP Professional clients can be configured
- to create a netlogon.log file that can be very helpful in diagnosing network logon problems. Search
- the Microsoft knowledge base for detailed instructions. The techniques vary a little with each
- version of MS Windows.
- </para>
-
- </sect4>
-
- </sect3>
-
- </sect2>
-
-
- <sect2>
- <title>Political Issues</title>
-
- <para>
- MS Windows network users are generally very sensitive to limits that may be imposed when
- confronted with locked-down workstation configurations. The challenge you face must
- be promoted as a choice between reliable, fast network operation and a constant flux
- of problems that result in user irritation.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Installation Checklist</title>
-
- <para>
- You are starting a complex project. Even though you went through the installation of a complex
- network in <link linkend="Big500users"/>, this network is a bigger challenge because of the
- large number of complex applications that must be configured before the first few steps
- can be validated. Take stock of what you are about to undertake, prepare yourself, and
- frequently review the steps ahead while making at least a mental note of what has already
- been completed. The following task list may help you to keep track of the task items
- that are covered:
- </para>
-
-
- <itemizedlist>
- <listitem><para>Samba PDC Server Configuration</para>
- <orderedlist>
- <listitem><para>DHCP and DNS servers</para></listitem>
- <listitem><para>OpenLDAP server</para></listitem>
- <listitem><para>PAM and NSS client tools</para></listitem>
- <listitem><para>Samba PDC</para></listitem>
- <listitem><para>Idealx smbldap scripts</para></listitem>
- <listitem><para>LDAP initialization</para></listitem>
- <listitem><para>Create user and group accounts</para></listitem>
- <listitem><para>Printers</para></listitem>
- <listitem><para>Share point directory roots</para></listitem>
- <listitem><para>Profile directories</para></listitem>
- <listitem><para>Logon scripts</para></listitem>
- <listitem><para>Configuration of user rights and privileges</para></listitem>
- </orderedlist>
- </listitem>
- <listitem><para>Samba BDC Server Configuration</para>
- <orderedlist>
- <listitem><para>DHCP and DNS servers</para></listitem>
- <listitem><para>PAM and NSS client tools</para></listitem>
- <listitem><para>Printers</para></listitem>
- <listitem><para>Share point directory roots</para></listitem>
- <listitem><para>Profiles directories</para></listitem>
- </orderedlist>
- </listitem>
- <listitem><para>Windows XP Client Configuration</para>
- <orderedlist>
- <listitem><para>Default profile folder redirection</para></listitem>
- <listitem><para>MS Outlook PST file relocation</para></listitem>
- <listitem><para>Delete roaming profile on logout</para></listitem>
- <listitem><para>Upload printer drivers to Samba servers</para></listitem>
- <listitem><para>Install software</para></listitem>
- <listitem><para>Creation of roll-out images</para></listitem>
- </orderedlist>
- </listitem>
- </itemizedlist>
-
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Samba Server Implementation</title>
-
- <para>
- <indexterm><primary>file servers</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- The network design shown in <link linkend="chap6net"/> is not comprehensive. It is assumed
- that you will install additional file servers and possibly additional BDCs.
- </para>
-
- <figure id="chap6net">
- <title>Network Topology &smbmdash; 500 User Network Using ldapsam passdb backend</title>
- <imagefile scale="50">chap6-net</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>SUSE Linux</primary></indexterm>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- All configuration files and locations are shown for SUSE Linux 9.2 and are equally valid for SUSE
- Linux Enterprise Server 9. The file locations for Red Hat Linux are similar. You may need to
- adjust the locations for your particular Linux system distribution/implementation.
- </para>
-
-<note><para>
-The following information applies to Samba-3.0.20 when used with the Idealx smbldap-tools
-scripts version 0.9.1. If using a different version of Samba or of the smbldap-tools tarball,
-please verify that the versions you are about to use are matching. The smbldap-tools package
-uses counter-entries in the LDAP directory to avoid duplication of the UIDs and GIDs that are
-issued for POSIX accounts. The LDAP rdn under which this information is stored are called
-<constant>uidNumber</constant> and <constant>gidNumber</constant> respectively. These may be
-located in any convenient part of the directory information tree (DIT). In the examples that
-follow they have been located under <constant>dn=sambaDomainName=MEGANET2,dc=abmas,dc=org</constant>.
-They could just as well be located under the rdn <constant>cn=NextFreeUnixId</constant>.
-</para></note>
-
- <para>
- The steps in the process involve changes from the network configuration shown in
- <link linkend="Big500users"/>. Before implementing the following steps, you must
- have completed the network implementation shown in that chapter. If you are starting
- with newly installed Linux servers, you must complete the steps shown in
- <link linkend="ch5-dnshcp-setup"/> before commencing at <link linkend="ldapsetup"/>.
- </para>
-
- <sect2 id="ldapsetup">
- <title>OpenLDAP Server Configuration</title>
-
- <para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- <indexterm><primary>pam_ldap</primary></indexterm>
- <indexterm><primary>openldap</primary></indexterm>
- Confirm that the packages shown in <link linkend="oldapreq"/> are installed on your system.
- </para>
-
- <table id="oldapreq">
- <title>Required OpenLDAP Linux Packages</title>
- <tgroup cols="3">
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry align="center">SUSE Linux 8.x</entry>
- <entry align="center">SUSE Linux 9.x</entry>
- <entry align="center">Red Hat Linux</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>nss_ldap</entry>
- <entry>nss_ldap</entry>
- <entry>nss_ldap</entry>
- </row>
- <row>
- <entry>pam_ldap</entry>
- <entry>pam_ldap</entry>
- <entry>pam_ldap</entry>
- </row>
- <row>
- <entry>openldap2</entry>
- <entry>openldap2</entry>
- <entry>openldap</entry>
- </row>
- <row>
- <entry>openldap2-client</entry>
- <entry>openldap2-client</entry>
- <entry></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- Samba and OpenLDAP will have a degree of interdependence that is unavoidable. The method
- for bootstrapping the LDAP and Samba configuration is relatively straightforward. If you
- follow these guidelines, the resulting system should work fine.
- </para>
-
- <procedure>
- <title>OpenLDAP Server Configuration Steps</title>
-
- <step><para>
- <indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
- Install the file shown in <link linkend="sbehap-slapdconf"/> in the directory
- <filename>/etc/openldap</filename>.
- </para></step>
-
- <step><para>
- <indexterm><primary>/data/ldap</primary></indexterm>
- <indexterm><primary>group account</primary></indexterm>
- <indexterm><primary>user account</primary></indexterm>
- Remove all files from the directory <filename>/data/ldap</filename>, making certain that
- the directory exists with permissions:
-<screen>
-&rootprompt; ls -al /data | grep ldap
-drwx------ 2 ldap ldap 48 Dec 15 22:11 ldap
-</screen>
- This may require you to add a user and a group account for LDAP if they do not exist.
- </para></step>
-
- <step><para>
- <indexterm><primary>DB_CONFIG</primary></indexterm>
- Install the file shown in <link linkend="sbehap-dbconf"/> in the directory
- <filename>/data/ldap</filename>. In the event that this file is added after <constant>ldap</constant>
- has been started, it is possible to cause the new settings to take effect by shutting down
- the <constant>LDAP</constant> server, executing the <command>db_recover</command> command inside the
- <filename>/data/ldap</filename> directory, and then restarting the <constant>LDAP</constant> server.
- </para></step>
-
- <step><para>
- <indexterm><primary>syslog</primary></indexterm>
- Performance logging can be enabled and should preferably be sent to a file on
- a file system that is large enough to handle significantly sized logs. To enable
- the logging at a verbose level to permit detailed analysis, uncomment the entry in
- the <filename>/etc/openldap/slapd.conf</filename> shown as <quote>loglevel 256</quote>.
- </para>
-
- <para>
- Edit the <filename>/etc/syslog.conf</filename> file to add the following at the end
- of the file:
-<screen>
-local4.* -/data/ldap/log/openldap.log
-</screen>
- Note: The path <filename>/data/ldap/log</filename> should be set at a location
- that is convenient and that can store a large volume of data.
- </para></step>
-
- </procedure>
-
-<example id="sbehap-dbconf">
-<title>LDAP DB_CONFIG File</title>
-<screen>
-set_cachesize 0 150000000 1
-set_lg_regionmax 262144
-set_lg_bsize 2097152
-#set_lg_dir /var/log/bdb
-set_flags DB_LOG_AUTOREMOVE
-</screen>
-</example>
-
-<example id="sbehap-slapdconf">
-<title>LDAP Master Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename> Part A</title>
-<screen>
-include /etc/openldap/schema/core.schema
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/nis.schema
-include /etc/openldap/schema/samba3.schema
-
-pidfile /var/run/slapd/slapd.pid
-argsfile /var/run/slapd/slapd.args
-
-access to dn.base=""
- by self write
- by * auth
-
-access to attr=userPassword
- by self write
- by * auth
-
-access to attr=shadowLastChange
- by self write
- by * read
-
-access to *
- by * read
- by anonymous auth
-
-#loglevel 256
-
-schemacheck on
-idletimeout 30
-backend bdb
-database bdb
-checkpoint 1024 5
-cachesize 10000
-
-suffix "dc=abmas,dc=biz"
-rootdn "cn=Manager,dc=abmas,dc=biz"
-
-# rootpw = not24get
-rootpw {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
-
-directory /data/ldap
-</screen>
-</example>
-
-<example id="sbehap-slapdconf2">
-<title>LDAP Master Configuration File &smbmdash; <filename>/etc/openldap/slapd.conf</filename> Part B</title>
-<screen>
-# Indices to maintain
-index objectClass eq
-index cn pres,sub,eq
-index sn pres,sub,eq
-index uid pres,sub,eq
-index displayName pres,sub,eq
-index uidNumber eq
-index gidNumber eq
-index memberUID eq
-index sambaSID eq
-index sambaPrimaryGroupSID eq
-index sambaDomainName eq
-index default sub
-</screen>
-</example>
-
- </sect2>
-
- <sect2 id="sbehap-PAM-NSS">
- <title>PAM and NSS Client Configuration</title>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>PAM</primary></indexterm>
- The steps that follow involve configuration of LDAP, NSS LDAP-based resolution of users and
- groups. Also, so that LDAP-based accounts can log onto the system, the steps ahead configure
- the Pluggable Authentication Modules (PAM) to permit LDAP-based authentication.
- </para>
-
- <para>
- <indexterm><primary>Pluggable Authentication Modules</primary><see>PAM</see></indexterm>
- <indexterm><primary>pam_unix2.so</primary></indexterm>
- Since you have chosen to put UNIX user and group accounts into the LDAP database, it is likely
- that you may want to use them for UNIX system (Linux) local machine logons. This necessitates
- correct configuration of PAM. The <command>pam_ldap</command> open source package provides the
- PAM modules that most people would use. On SUSE Linux systems, the <command>pam_unix2.so</command>
- module also has the ability to redirect authentication requests through LDAP.
- </para>
-
- <para>
- <indexterm><primary>YaST</primary></indexterm>
- <indexterm><primary>SUSE Linux</primary></indexterm>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- <indexterm><primary>authconfig</primary></indexterm>
- You have chosen to configure these services by directly editing the system files, but of course, you
- know that this configuration can be done using system tools provided by the Linux system vendor.
- SUSE Linux has a facility in YaST (the system admin tool) through <menuchoice><guimenu>yast</guimenu>
- <guimenuitem>system</guimenuitem><guimenuitem>ldap-client</guimenuitem></menuchoice> that permits
- configuration of SUSE Linux as an LDAP client. Red Hat Linux provides the <command>authconfig</command>
- tool for this.
- </para>
-
- <procedure>
- <title>PAM and NSS Client Configuration Steps</title>
-
- <step><para>
- <indexterm><primary>/lib/libnss_ldap.so.2</primary></indexterm>
- <indexterm><primary>/etc/ldap.conf</primary></indexterm>
- <indexterm><primary>nss_ldap</primary></indexterm>
- Execute the following command to find where the <filename>nss_ldap</filename> module
- expects to find its control file:
-<screen>
-&rootprompt; strings /lib/libnss_ldap.so.2 | grep conf
-</screen>
- The preferred and usual location is <filename>/etc/ldap.conf</filename>.
- </para></step>
-
- <step><para>
- On the server <constant>MASSIVE</constant>, install the file shown in
- <link linkend="sbehap-nss01"/> into the path that was obtained from the step above.
- On the servers called <constant>BLDG1</constant> and <constant>BLDG2</constant>, install the file shown in
- <link linkend="sbehap-nss02"/> into the path that was obtained from the step above.
- </para></step>
-
-<example id="sbehap-nss01">
-<title>Configuration File for NSS LDAP Support &smbmdash; <filename>/etc/ldap.conf</filename></title>
-<screen>
-host 127.0.0.1
-
-base dc=abmas,dc=biz
-
-binddn cn=Manager,dc=abmas,dc=biz
-bindpw not24get
-
-timelimit 50
-bind_timelimit 50
-bind_policy hard
-
-idle_timelimit 3600
-
-pam_password exop
-
-nss_base_passwd ou=People,dc=abmas,dc=biz?one
-nss_base_shadow ou=People,dc=abmas,dc=biz?one
-nss_base_group ou=Groups,dc=abmas,dc=biz?one
-
-ssl off
-</screen>
-</example>
-
-<example id="sbehap-nss02">
-<title>Configuration File for NSS LDAP Clients Support &smbmdash; <filename>/etc/ldap.conf</filename></title>
-<screen>
-host 172.16.0.1
-
-base dc=abmas,dc=biz
-
-binddn cn=Manager,dc=abmas,dc=biz
-bindpw not24get
-
-timelimit 50
-bind_timelimit 50
-bind_policy hard
-
-idle_timelimit 3600
-
-pam_password exop
-
-nss_base_passwd ou=People,dc=abmas,dc=biz?one
-nss_base_shadow ou=People,dc=abmas,dc=biz?one
-nss_base_group ou=Groups,dc=abmas,dc=biz?one
-
-ssl off
-</screen>
-</example>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- Edit the NSS control file (<filename>/etc/nsswitch.conf</filename>) so that the lines that
- control user and group resolution will obtain information from the normal system files as
- well as from <command>ldap</command>:
-<screen>
-passwd: files ldap
-shadow: files ldap
-group: files ldap
-hosts: files dns wins
-</screen>
- Later, when the LDAP database has been initialized and user and group accounts have been
- added, you can validate resolution of the LDAP resolver process. The inclusion of
- WINS-based hostname resolution is deliberate so that all MS Windows client hostnames can be
- resolved to their IP addresses, whether or not they are DHCP clients.
- </para>
-
- <note><para>
- Some Linux systems (Novell SUSE Linux in particular) add entries to the <filename>nsswitch.conf</filename>
- file that may cause operational problems with the configuration methods adopted in this book. It is
- advisable to comment out the entries <constant>passwd_compat</constant> and <constant>group_compat</constant>
- where they are found in this file.
- </para></note>
-
- <para>
- Even at the risk of overstating the issue, incorrect and inappropriate configuration of the
- <filename>nsswitch.conf</filename> file is a significant cause of operational problems with LDAP.
- </para></step>
-
- <step><para>
- <indexterm><primary>pam_unix2.so</primary><secondary>use_ldap</secondary></indexterm>
- For PAM LDAP configuration on this SUSE Linux 9.0 system, the simplest solution is to edit the following
- files in the <filename>/etc/pam.d</filename> directory: <command>login</command>, <command>password</command>,
- <command>samba</command>, <command>sshd</command>. In each file, locate every entry that has the
- <command>pam_unix2.so</command> entry and add to the line the entry <command>use_ldap</command> as shown
- for the <command>login</command> module in this example:
-<screen>
-#%PAM-1.0
-auth requisite pam_unix2.so nullok use_ldap #set_secrpc
-auth required pam_securetty.so
-auth required pam_nologin.so
-#auth required pam_homecheck.so
-auth required pam_env.so
-auth required pam_mail.so
-account required pam_unix2.so use_ldap
-password required pam_pwcheck.s nullok
-password required pam_unix2.so nullok use_first_pass \
- use_authtok use_ldap
-session required pam_unix2.so none use_ldap # debug or trace
-session required pam_limits.so
-</screen>
- </para>
-
- <para>
- <indexterm><primary>pam_ldap.so</primary></indexterm>
- On other Linux systems that do not have an LDAP-enabled <command>pam_unix2.so</command> module,
- you must edit these files by adding the <command>pam_ldap.so</command> modules as shown here:
-<screen>
-#%PAM-1.0
-auth required pam_securetty.so
-auth required pam_nologin.so
-auth sufficient pam_ldap.so
-auth required pam_unix2.so nullok try_first_pass #set_secrpc
-account sufficient pam_ldap.so
-account required pam_unix2.so
-password required pam_pwcheck.so nullok
-password required pam_ldap.so use_first_pass use_authtok
-password required pam_unix2.so nullok use_first_pass use_authtok
-session required pam_unix2.so none # debug or trace
-session required pam_limits.so
-session required pam_env.so
-session optional pam_mail.so
-</screen>
- This example does have the LDAP-enabled <command>pam_unix2.so</command>, but simply
- demonstrates the use of the <command>pam_ldap.so</command> module. You can use either
- implementation, but if the <command>pam_unix2.so</command> on your system supports
- LDAP, you probably want to use it rather than add an additional module.
- </para></step>
-
- </procedure>
-
- </sect2>
-
- <sect2 id="sbehap-massive">
- <title>Samba-3 PDC Configuration</title>
-
- <para>
- <indexterm><primary>Samba RPM Packages</primary></indexterm>
- Verify that the Samba-3.0.20 (or later) packages are installed on each SUSE Linux server
- before following the steps below. If Samba-3.0.20 (or later) is not installed, you have the
- choice to either build your own or obtain the packages from a dependable source.
- Packages for SUSE Linux 8.x, 9.x, and SUSE Linux Enterprise Server 9, as well as for
- Red Hat Fedora Core and Red Hat Enterprise Linux Server 3 and 4, are included on the CD-ROM that
- is included with this book.
- </para>
-
- <procedure>
- <title>Configuration of PDC Called <constant>MASSIVE</constant></title>
-
- <step><para>
- Install the files in <link linkend="sbehap-massive-smbconfa"/>,
- <link linkend="sbehap-massive-smbconfb"/>, <link linkend="sbehap-shareconfa"/>,
- and <link linkend="sbehap-shareconfb"/> into the <filename>/etc/samba/</filename>
- directory. The three files should be added together to form the &smb.conf;
- master file. It is a good practice to call this file something like
- <filename>smb.conf.master</filename> and then to perform all file edits
- on the master file. The operational &smb.conf; is then generated as shown in
- the next step.
- </para></step>
-
- <step><para>
- <indexterm><primary>testparm</primary></indexterm>
- Create and verify the contents of the &smb.conf; file that is generated by:
-<screen>
-&rootprompt; testparm -s smb.conf.master > smb.conf
-</screen>
- Immediately follow this with the following:
-<screen>
-&rootprompt; testparm
-</screen>
- The output that is created should be free from errors, as shown here:
-
-<screen>
-Load smb config files from /etc/samba/smb.conf
-Processing section "[accounts]"
-Processing section "[service]"
-Processing section "[pidata]"
-Processing section "[homes]"
-Processing section "[printers]"
-Processing section "[apps]"
-Processing section "[netlogon]"
-Processing section "[profiles]"
-Processing section "[profdata]"
-Processing section "[print$]"
-Loaded services file OK.
-Server role: ROLE_DOMAIN_PDC
-Press enter to see a dump of your service definitions
-</screen>
- </para></step>
-
- <step><para>
- Delete all runtime files from prior Samba operation by executing (for SUSE
- Linux):
-<screen>
-&rootprompt; rm /etc/samba/*tdb
-&rootprompt; rm /var/lib/samba/*tdb
-&rootprompt; rm /var/lib/samba/*dat
-&rootprompt; rm /var/log/samba/*
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>secrets.tdb</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- Samba communicates with the LDAP server. The password that it uses to
- authenticate to the LDAP server must be stored in the <filename>secrets.tdb</filename>
- file. Execute the following to create the new <filename>secrets.tdb</filename> files
- and store the password for the LDAP Manager:
-<screen>
-&rootprompt; smbpasswd -w not24get
-</screen>
- The expected output from this command is:
-<screen>
-Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
- Samba generates a Windows Security Identifier (SID) only when <command>smbd</command>
- has been started. For this reason, you start Samba. After a few seconds delay,
- execute:
-<screen>
-&rootprompt; smbclient -L localhost -U%
-&rootprompt; net getlocalsid
-</screen>
- A report such as the following means that the domain SID has not yet
- been written to the <filename>secrets.tdb</filename> or to the LDAP backend:
-<screen>
-[2005/03/03 23:19:34, 0] lib/smbldap.c:smbldap_connect_system(852)
- failed to bind to server ldap://massive.abmas.biz
-with dn="cn=Manager,dc=abmas,dc=biz" Error: Can't contact LDAP server
- (unknown)
-[2005/03/03 23:19:48, 0] lib/smbldap.c:smbldap_search_suffix(1169)
- smbldap_search_suffix: Problem during the LDAP search:
- (unknown) (Timed out)
-</screen>
- The attempt to read the SID will cause and attempted bind to the LDAP server. Because the LDAP server
- is not running, this operation will fail by way of a timeout, as shown previously. This is
- normal output; do not worry about this error message. When the domain has been created and
- written to the <filename>secrets.tdb</filename> file, the output should look like this:
-<screen>
-SID for domain MASSIVE is: S-1-5-21-3504140859-1010554828-2431957765
-</screen>
- If, after a short delay (a few seconds), the domain SID has still not been written to
- the <filename>secrets.tdb</filename> file, it is necessary to investigate what
- may be misconfigured. In this case, carefully check the &smb.conf; file for typographical
- errors (the most common problem). The use of the <command>testparm</command> is highly
- recommended to validate the contents of this file.
- </para></step>
-
- <step><para>
- When a positive domain SID has been reported, stop Samba.
- </para></step>
-
- <step><para>
- <indexterm><primary>NFS server</primary></indexterm>
- <indexterm><primary>/etc/exports</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>rsync</primary></indexterm>
- Configure the NFS server for your Linux system. So you can complete the steps that
- follow, enter into the <filename>/etc/exports</filename> the following entry:
-<screen>
-/home *(rw,root_squash,sync)
-</screen>
- This permits the user home directories to be used on the BDC servers for testing
- purposes. You, of course, decide what is the best way for your site to distribute
- data drives, and you create suitable backup and restore procedures for Abmas
- I'd strongly recommend that for normal operation the BDC is completely independent
- of the PDC. rsync is a useful tool here, as it resembles the NT replication service quite
- closely. If you do use NFS, do not forget to start the NFS server as follows:
-<screen>
-&rootprompt; rcnfsserver start
-</screen>
- </para></step>
- </procedure>
-
- <para>
- Your Samba PDC is now ready to communicate with the LDAP password backend. Let's get on with
- configuration of the LDAP server.
- </para>
-
-<example id="sbehap-massive-smbconfa">
-<title>LDAP Based &smb.conf; File, Server: MASSIVE &smbmdash; global Section: Part A</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
- <smbconfoption name="unix charset">LOCALE</smbconfoption>
- <smbconfoption name="workgroup">MEGANET2</smbconfoption>
- <smbconfoption name="netbios name">MASSIVE</smbconfoption>
- <smbconfoption name="interfaces">eth1, lo</smbconfoption>
- <smbconfoption name="bind interfaces only">Yes</smbconfoption>
- <smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
- <smbconfoption name="enable privileges">Yes</smbconfoption>
- <smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
- <smbconfoption name="log level">1</smbconfoption>
- <smbconfoption name="syslog">0</smbconfoption>
- <smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
- <smbconfoption name="max log size">50</smbconfoption>
- <smbconfoption name="smb ports">139</smbconfoption>
- <smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
- <smbconfoption name="time server">Yes</smbconfoption>
- <smbconfoption name="printcap name">CUPS</smbconfoption>
- <smbconfoption name="show add printer wizard">No</smbconfoption>
- <smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m "%u"</smbconfoption>
- <smbconfoption name="delete user script">/opt/IDEALX/sbin/smbldap-userdel "%u"</smbconfoption>
- <smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p "%g"</smbconfoption>
- <smbconfoption name="delete group script">/opt/IDEALX/sbin/smbldap-groupdel "%g"</smbconfoption>
- <smbconfoption name="add user to group script">/opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</smbconfoption>
- <smbconfoption name="delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</smbconfoption>
- <smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</smbconfoption>
- <smbconfoption name="add machine script">/opt/IDEALX/sbin/smbldap-useradd -w "%u"</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="sbehap-massive-smbconfb">
-<title>LDAP Based &smb.conf; File, Server: MASSIVE &smbmdash; global Section: Part B</title>
-<smbconfblock>
- <smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
- <smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
- <smbconfoption name="logon drive">X:</smbconfoption>
- <smbconfoption name="domain logons">Yes</smbconfoption>
- <smbconfoption name="preferred master">Yes</smbconfoption>
- <smbconfoption name="wins support">Yes</smbconfoption>
- <smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
- <smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
- <smbconfoption name="ldap user suffix">ou=People</smbconfoption>
- <smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
- <smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
- <smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
- <smbconfoption name="idmap backend">ldap:ldap://massive.abmas.biz</smbconfoption>
- <smbconfoption name="idmap uid">10000-20000</smbconfoption>
- <smbconfoption name="idmap gid">10000-20000</smbconfoption>
- <smbconfoption name="map acl inherit">Yes</smbconfoption>
- <smbconfoption name="printing">cups</smbconfoption>
- <smbconfoption name="printer admin">root, chrisr</smbconfoption>
-</smbconfblock>
-</example>
-
- </sect2>
-
-
- <sect2 id="sbeidealx">
- <title>Install and Configure Idealx smbldap-tools Scripts</title>
-
- <para>
- <indexterm><primary>Idealx</primary><secondary>smbldap-tools</secondary></indexterm>
- The Idealx scripts, or equivalent, are necessary to permit Samba to manage accounts
- on the LDAP server. You have chosen the Idealx scripts because they are the best-known
- LDAP configuration scripts. The use of these scripts will help avoid the necessity
- to create custom scripts. It is easy to download them from the Idealx
- <ulink url="http://samba.idealx.org/index.en.html">Web site</ulink>. The tarball may
- be directly <ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.1.tgz">downloaded</ulink>
- from this site also. Alternatively, you may obtain the
- <ulink url="http://samba.idealx.org/dist/smbldap-tools-0.9.1-1.src.rpm">smbldap-tools-0.9.1-1.src.rpm</ulink>
- file that may be used to build an installable RPM package for your Linux system.
- </para>
-
-<note><para>
-The smbldap-tools scripts can be installed in any convenient directory of your choice, in which case you must
-change the path to them in your &smb.conf; file on the PDC (<constant>MASSIVE</constant>).
-</para></note>
-
- <para>
- The smbldap-tools are located in <filename>/opt/IDEALX/sbin</filename>.
- The scripts are not needed on BDC machines because all LDAP updates are handled by
- the PDC alone.
- </para>
-
- <sect3>
- <title>Installation of smbldap-tools from the Tarball</title>
-
- <para>
- To perform a manual installation of the smbldap-tools scripts, the following procedure may be used:
- </para>
-
- <procedure id="idealxscript">
- <title>Unpacking and Installation Steps for the <constant>smbldap-tools</constant> Tarball</title>
-
- <step><para>
- Create the <filename>/opt/IDEALX/sbin</filename> directory, and set its permissions
- and ownership as shown here:
-<screen>
-&rootprompt; mkdir -p /opt/IDEALX/sbin
-&rootprompt; chown root:root /opt/IDEALX/sbin
-&rootprompt; chmod 755 /opt/IDEALX/sbin
-&rootprompt; mkdir -p /etc/smbldap-tools
-&rootprompt; chown root:root /etc/smbldap-tools
-&rootprompt; chmod 755 /etc/smbldap-tools
-</screen>
- </para></step>
-
- <step><para>
- If you wish to use the downloaded tarball, unpack the smbldap-tools in a suitable temporary location.
- Change into either the directory extracted from the tarball or the smbldap-tools
- directory in your <filename>/usr/share/doc/packages</filename> directory tree.
- </para></step>
-
- <step><para>
- Copy all the <filename>smbldap-*</filename> and the <filename>configure.pl</filename> files into the
- <filename>/opt/IDEALX/sbin</filename> directory, as shown here:
-<screen>
-&rootprompt; cd smbldap-tools-0.9.1/
-&rootprompt; cp smbldap-* configure.pl *pm /opt/IDEALX/sbin/
-&rootprompt; cp smbldap*conf /etc/smbldap-tools/
-&rootprompt; chmod 750 /opt/IDEALX/sbin/smbldap-*
-&rootprompt; chmod 750 /opt/IDEALX/sbin/configure.pl
-&rootprompt; chmod 640 /etc/smbldap-tools/smbldap.conf
-&rootprompt; chmod 600 /etc/smbldap-tools/smbldap_bind.conf
-</screen>
- </para></step>
-
- <step><para>
- The smbldap-tools scripts master control file must now be configured.
- Change to the <filename>/opt/IDEALX/sbin</filename> directory, then edit the
- <filename>smbldap_tools.pm</filename> to affect the changes
- shown here:
-<screen>
-...
-# ugly funcs using global variables and spawning openldap clients
-
-my $smbldap_conf="/etc/smbldap-tools/smbldap.conf";
-my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf";
-...
-</screen>
- </para></step>
-
- <step><para>
- To complete the configuration of the smbldap-tools, set the permissions and ownership
- by executing the following commands:
-<screen>
-&rootprompt; chown root:root /opt/IDEALX/sbin/*
-&rootprompt; chmod 755 /opt/IDEALX/sbin/smbldap-*
-&rootprompt; chmod 640 /opt/IDEALX/sbin/smb*pm
-</screen>
- The smbldap-tools scripts are now ready for the configuration step outlined in
- <link linkend="smbldap-init"/>.
- </para></step>
-
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>Installing smbldap-tools from the RPM Package</title>
-
- <para>
- In the event that you have elected to use the RPM package provided by Idealx, download the
- source RPM <filename>smbldap-tools-0.9.1-1.src.rpm</filename>, then follow this procedure:
- </para>
-
- <procedure>
- <title>Installation Steps for <constant>smbldap-tools</constant> RPM's</title>
-
- <step><para>
- Install the source RPM that has been downloaded as follows:
-<screen>
-&rootprompt; rpm -i smbldap-tools-0.9.1-1.src.rpm
-</screen>
- </para></step>
-
- <step><para>
- Change into the directory in which the SPEC files are located. On SUSE Linux:
-<screen>
-&rootprompt; cd /usr/src/packages/SPECS
-</screen>
- On Red Hat Linux systems:
-<screen>
-&rootprompt; cd /usr/src/redhat/SPECS
-</screen>
- </para></step>
-
- <step><para>
- Edit the <filename>smbldap-tools.spec</filename> file to change the value of the
- <constant>_sysconfig</constant> macro as shown here:
-<screen>
-%define _prefix /opt/IDEALX
-%define _sysconfdir /etc
-</screen>
- Note: Any suitable directory can be specified.
- </para></step>
-
- <step><para>
- Build the package by executing:
-<screen>
-&rootprompt; rpmbuild -ba -v smbldap-tools.spec
-</screen>
- A build process that has completed without error will place the installable binary
- files in the directory <filename>../RPMS/noarch</filename>.
- </para></step>
-
- <step><para>
- Install the binary package by executing:
-<screen>
-&rootprompt; rpm -Uvh ../RPMS/noarch/smbldap-tools-0.9.1-1.noarch.rpm
-</screen>
- </para></step>
-
- </procedure>
-
- <para>
- The Idealx scripts should now be ready for configuration using the steps outlined in
- <link linkend="smbldap-init">Configuration of smbldap-tools</link>.
- </para>
-
- </sect3>
-
- <sect3 id="smbldap-init">
- <title>Configuration of smbldap-tools</title>
-
- <para>
- Prior to use, the smbldap-tools must be configured to match the settings in the &smb.conf; file
- and to match the settings in the <filename>/etc/openldap/slapd.conf</filename> file. The assumption
- is made that the &smb.conf; file has correct contents. The following procedure ensures that
- this is completed correctly:
- </para>
-
- <para>
- The smbldap-tools require that the NetBIOS name (machine name) of the Samba server be included
- in the &smb.conf; file.
- </para>
-
- <procedure>
- <title>Configuration Steps for <constant>smbldap-tools</constant> to Enable Use</title>
-
- <step><para>
- Change into the directory that contains the <filename>configure.pl</filename> script.
-<screen>
-&rootprompt; cd /opt/IDEALX/sbin
-</screen>
- </para></step>
-
- <step><para>
- Execute the <filename>configure.pl</filename> script as follows:
-<screen>
-&rootprompt; ./configure.pl
-</screen>
- The interactive use of this script for the PDC is demonstrated here:
-<screen>
-&rootprompt; /opt/IDEALX/sbin/configure.pl
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- smbldap-tools script configuration
- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Before starting, check
- . if your samba controller is up and running.
- . if the domain SID is defined (you can get it with the
- 'net getlocalsid')
-
- . you can leave the configuration using the Crtl-c key combination
- . empty value can be set with the "." character
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Looking for configuration files...
-
-Samba Config File Location [/etc/samba/smb.conf] >
-smbldap-tools configuration file Location (global parameters)
- [/etc/opt/IDEALX/smbldap-tools/smbldap.conf] >
-smbldap Config file Location (bind parameters)
- [/etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf] >
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Let's start configuring the smbldap-tools scripts ...
-
-. workgroup name: name of the domain Samba act as a PDC
- workgroup name [MEGANET2] >
-. netbios name: netbios name of the samba controler
- netbios name [MASSIVE] >
-. logon drive: local path to which the home directory
- will be connected (for NT Workstations). Ex: 'H:'
- logon drive [H:] >
-. logon home: home directory location (for Win95/98 or NT Workstation)
- (use %U as username) Ex:'\\MASSIVE\%U'
- logon home (press the "." character if you don't want homeDirectory)
- [\\MASSIVE\%U] >
-. logon path: directory where roaming profiles are stored.
- Ex:'\\MASSIVE\profiles\%U'
- logon path (press the "." character
- if you don't want roaming profile) [\\%L\profiles\%U] >
-. home directory prefix (use %U as username)
- [/home/%U] > /data/users/%U
-. default users' homeDirectory mode [700] >
-. default user netlogon script (use %U as username)
- [scripts\logon.bat] >
- default password validation time (time in days) [45] > 900
-. ldap suffix [dc=abmas,dc=biz] >
-. ldap group suffix [ou=Groups] >
-. ldap user suffix [ou=People,ou=Users] >
-. ldap machine suffix [ou=Computers,ou=Users] >
-. Idmap suffix [ou=Idmap] >
-. sambaUnixIdPooldn: object where you want to store the next uidNumber
- and gidNumber available for new users and groups
- sambaUnixIdPooldn object (relative to ${suffix})
- [sambaDomainName=MEGANET2] >
-. ldap master server: IP adress or DNS name of the master
- (writable) ldap server
- ldap master server [massive.abmas.biz] >
-. ldap master port [389] >
-. ldap master bind dn [cn=Manager,dc=abmas,dc=biz] >
-. ldap master bind password [] >
-. ldap slave server: IP adress or DNS name of the slave ldap server:
- can also be the master one
- ldap slave server [massive.abmas.biz] >
-. ldap slave port [389] >
-. ldap slave bind dn [cn=Manager,dc=abmas,dc=biz] >
-. ldap slave bind password [] >
-. ldap tls support (1/0) [0] >
-. SID for domain MEGANET2: SID of the domain
- (can be obtained with 'net getlocalsid MASSIVE')
- SID for domain MEGANET2
- [S-1-5-21-3504140859-1010554828-2431957765]] >
-. unix password encryption: encryption used for unix passwords
- unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA) [SSHA] > MD5
-. default user gidNumber [513] >
-. default computer gidNumber [515] >
-. default login shell [/bin/bash] >
-. default skeleton directory [/etc/skel] >
-. default domain name to append to mail adress [] > abmas.biz
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-backup old configuration files:
- /etc/opt/IDEALX/smbldap-tools/smbldap.conf->
- /etc/opt/IDEALX/smbldap-tools/smbldap.conf.old
- /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf->
- /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf.old
-writing new configuration file:
- /etc/opt/IDEALX/smbldap-tools/smbldap.conf done.
- /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf done.
-</screen>
- Since a slave LDAP server has not been configured, it is necessary to specify the IP
- address of the master LDAP server for both the master and the slave configuration
- prompts.
- </para></step>
-
- <step><para>
- Change to the directory that contains the <filename>smbldap.conf</filename> file,
- then verify its contents.
- </para></step>
-
- </procedure>
-
- <para>
- The smbldap-tools are now ready for use.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>LDAP Initialization and Creation of User and Group Accounts</title>
-
- <para>
- The LDAP database must be populated with well-known Windows domain user accounts and domain group
- accounts before Samba can be used. The following procedures step you through the process.
- </para>
-
- <para>
- At this time, Samba requires that on a PDC all UNIX (POSIX) group accounts that are
- mapped (linked) to Windows domain group accounts must be in the LDAP database. It does not
- hurt to have UNIX user and group accounts in both the system files as well as in the LDAP
- database. From a UNIX system perspective, the NSS resolver checks system files before
- referring to LDAP. If the UNIX system can resolve (find) an account in the system file, it
- does not need to ask LDAP.
- </para>
-
- <para>
- Addition of an account to the LDAP backend can be done in two ways:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>NIS</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>Posix accounts</primary></indexterm>
- <indexterm><primary>pdbedit</primary></indexterm>
- <indexterm><primary>SambaSamAccount</primary></indexterm>
- <indexterm><primary>PosixAccount</primary></indexterm>
- If you always have a user account in the <filename>/etc/passwd</filename> on every
- server or in a NIS(+) backend, it is not necessary to add POSIX accounts for them in
- LDAP. In this case, you can add Windows domain user accounts using the
- <command>pdbedit</command> utility. Use of this tool from the command line adds the
- SambaSamAccount entry for the user, but does not add the PosixAccount entry for the user.
- </para>
-
- <para>
- This is the least desirable method because when LDAP is used as the passwd backend Samba
- expects the POSIX account to be in LDAP also. It is possible to use the PADL account
- migration tool to migrate all system accounts from either the <filename>/etc/passwd</filename>
- files, or from NIS, to LDAP.
- </para></listitem>
-
- <listitem><para>
- If you decide that it is probably a good idea to add both the PosixAccount attributes
- as well as the SambaSamAccount attributes for each user, then a suitable script is needed.
- In the example system you are installing in this exercise, you are making use of the
- Idealx smbldap-tools scripts. A copy of these tools, preconfigured for this system,
- is included on the enclosed CD-ROM under <filename>Chap06/Tools.</filename>
- </para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>Idealx</primary><secondary>smbldap-tools</secondary></indexterm>
- If you wish to have more control over how the LDAP database is initialized or
- if you don't want to use the Idealx smbldap-tools, you should refer to
- <link linkend="appendix"/>, <link linkend="altldapcfg"/>.
- </para>
-
- <para>
- <indexterm><primary>smbldap-populate</primary></indexterm>
- The following steps initialize the LDAP database, and then you can add user and group
- accounts that Samba can use. You use the <command>smbldap-populate</command> to
- seed the LDAP database. You then manually add the accounts shown in <link linkend="sbehap-bigacct"/>.
- The list of users does not cover all 500 network users; it provides examples only.
- </para>
-
- <note><para>
- <indexterm><primary>LDAP</primary><secondary>database</secondary></indexterm>
- <indexterm><primary>directory</primary><secondary>People container</secondary></indexterm>
- <indexterm><primary>directory</primary><secondary>Computers container</secondary></indexterm>
- In the following examples, as the LDAP database is initialized, we do create a container
- for Computer (machine) accounts. In the Samba &smb.conf; files, specific use is made
- of the People container, not the Computers container, for domain member accounts. This is not a
- mistake; it is a deliberate action that is necessitated by the fact that the resolution of
- a machine (computer) account to a UID is done via NSS. The only way this can be handled is
- using the NSS (<filename>/etc/nsswitch.conf</filename>) entry for <constant>passwd</constant>,
- which is resolved using the <filename>nss_ldap</filename> library. The configuration file for
- the <filename>nss_ldap</filename> library is the file <filename>/etc/ldap.conf</filename> that
- provides only one possible LDAP search command that is specified by the entry called
- <constant>nss_base_passwd</constant>. This means that the search path must take into account
- the directory structure so that the LDAP search will commence at a level that is above
- both the Computers container and the Users (or People) container. If this is done, it is
- necessary to use a search that will descend the directory tree so that the machine account
- can be found. Alternatively, by placing all machine accounts in the People container, we
- are able to sidestep this limitation. This is the simpler solution that has been adopted
- in this chapter.
- </para></note>
-
-
- <table id="sbehap-bigacct">
- <title>Abmas Network Users and Groups</title>
- <tgroup cols="4">
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry align="center">Account Name</entry>
- <entry align="center">Type</entry>
- <entry align="center">ID</entry>
- <entry align="center">Password</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Robert Jordan</entry>
- <entry>User</entry>
- <entry>bobj</entry>
- <entry>n3v3r2l8</entry>
- </row>
- <row>
- <entry>Stanley Soroka</entry>
- <entry>User</entry>
- <entry>stans</entry>
- <entry>impl13dst4r</entry>
- </row>
- <row>
- <entry>Christine Roberson</entry>
- <entry>User</entry>
- <entry>chrisr</entry>
- <entry>S9n0nw4ll</entry>
- </row>
- <row>
- <entry>Mary Vortexis</entry>
- <entry>User</entry>
- <entry>maryv</entry>
- <entry>kw13t0n3</entry>
- </row>
- <row>
- <entry>Accounts</entry>
- <entry>Group</entry>
- <entry>Accounts</entry>
- <entry></entry>
- </row>
- <row>
- <entry>Finances</entry>
- <entry>Group</entry>
- <entry>Finances</entry>
- <entry></entry>
- </row>
- <row>
- <entry>Insurance</entry>
- <entry>Group</entry>
- <entry>PIOps</entry>
- <entry></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <procedure id="creatacc">
- <title>LDAP Directory Initialization Steps</title>
-
- <step><para>
- Start the LDAP server by executing:
-<screen>
-&rootprompt; rcldap start
-Starting ldap-server done
-</screen>
- </para></step>
-
- <step><para>
- Change to the <filename>/opt/IDEALX/sbin</filename> directory.
- </para></step>
-
- <step><para>
- Execute the script that will populate the LDAP database as shown here:
-<screen>
-&rootprompt; ./smbldap-populate -a root -k 0 -m 0
-</screen>
- The expected output from this is:
-<screen>
-Using workgroup name from smb.conf: sambaDomainName=MEGANET2
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=> Warning: you must update smbldap.conf configuration file to :
-=> sambaUnixIdPooldn parameter must be set
- to "sambaDomainName=MEGANET2,dc=abmas,dc=biz"
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Using builtin directory structure
-adding new entry: dc=abmas,dc=biz
-adding new entry: ou=People,dc=abmas,dc=biz
-adding new entry: ou=Groups,dc=abmas,dc=biz
-entry ou=People,dc=abmas,dc=biz already exist.
-adding new entry: ou=Idmap,dc=abmas,dc=biz
-adding new entry: sambaDomainName=MEGANET2,dc=abmas,dc=biz
-adding new entry: uid=root,ou=People,dc=abmas,dc=biz
-adding new entry: uid=nobody,ou=People,dc=abmas,dc=biz
-adding new entry: cn=Domain Admins,ou=Groups,dc=abmas,dc=biz
-adding new entry: cn=Domain Users,ou=Groups,dc=abmas,dc=biz
-adding new entry: cn=Domain Guests,ou=Groups,dc=abmas,dc=biz
-adding new entry: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
-adding new entry: cn=Administrators,ou=Groups,dc=abmas,dc=biz
-adding new entry: cn=Print Operators,ou=Groups,dc=abmas,dc=biz
-adding new entry: cn=Backup Operators,ou=Groups,dc=abmas,dc=biz
-adding new entry: cn=Replicators,ou=Groups,dc=abmas,dc=biz
-</screen>
- </para></step>
-
- <step><para>
- Edit the <filename>/etc/smbldap-tools/smbldap.conf</filename> file so that the following
- information is changed from:
-<screen>
-# Where to store next uidNumber and gidNumber available
-sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}"
-</screen>
- to read, after modification:
-<screen>
-# Where to store next uidNumber and gidNumber available
-#sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}"
-sambaUnixIdPooldn="sambaDomainName=MEGANET2,dc=abmas,dc=biz"
-</screen>
- </para></step>
-
- <step><para>
- It is necessary to restart the LDAP server as shown here:
-<screen>
-&rootprompt; rcldap restart
-Shutting down ldap-server done
-Starting ldap-server done
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>slapcat</primary></indexterm>
- So that we can use a global IDMAP repository, the LDAP directory must have a container object for IDMAP data.
- There are several ways you can check that your LDAP database is able to receive IDMAP information. One of
- the simplest is to execute:
-<screen>
-&rootprompt; slapcat | grep -i idmap
-dn: ou=Idmap,dc=abmas,dc=biz
-ou: idmap
-</screen>
- <indexterm> <primary>ldapadd</primary></indexterm>
- If the execution of this command does not return IDMAP entries, you need to create an LDIF
- template file (see <link linkend="sbehap-ldifadd"/>). You can add the required entries using
- the following command:
-<screen>
-&rootprompt; ldapadd -x -D "cn=Manager,dc=abmas,dc=biz" \
- -w not24get < /etc/openldap/idmap.LDIF
-</screen>
- Samba automatically populates this LDAP directory container when it needs to.
- </para></step>
-
- <step><para>
- <indexterm><primary>slapcat</primary></indexterm>
- It looks like all has gone well, as expected. Let's confirm that this is the case
- by running a few tests. First we check the contents of the database directly
- by running <command>slapcat</command> as follows (the output has been cut down):
-<screen>
-&rootprompt; slapcat
-dn: dc=abmas,dc=biz
-objectClass: dcObject
-objectClass: organization
-dc: abmas
-o: abmas
-structuralObjectClass: organization
-entryUUID: 5ab02bf6-c536-1027-9d29-b1f32350fb43
-creatorsName: cn=Manager,dc=abmas,dc=biz
-createTimestamp: 20031217234200Z
-entryCSN: 2003121723:42:00Z#0x0001#0#0000
-modifiersName: cn=Manager,dc=abmas,dc=biz
-modifyTimestamp: 20031217234200Z
-...
-dn: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
-objectClass: posixGroup
-objectClass: sambaGroupMapping
-gidNumber: 553
-cn: Domain Computers
-description: Netbios Domain Computers accounts
-sambaSID: S-1-5-21-3504140859-1010554828-2431957765-553
-sambaGroupType: 2
-displayName: Domain Computers
-structuralObjectClass: posixGroup
-entryUUID: 5e0a41d8-c536-1027-9d3b-b1f32350fb43
-creatorsName: cn=Manager,dc=abmas,dc=biz
-createTimestamp: 20031217234206Z
-entryCSN: 2003121723:42:06Z#0x0002#0#0000
-modifiersName: cn=Manager,dc=abmas,dc=biz
-modifyTimestamp: 20031217234206Z
-</screen>
- This looks good so far.
- </para></step>
-
- <step><para>
- <indexterm><primary>ldapsearch</primary></indexterm>
- The next step is to prove that the LDAP server is running and responds to a
- search request. Execute the following as shown (output has been cut to save space):
-<screen>
-&rootprompt; ldapsearch -x -b "dc=abmas,dc=biz" "(ObjectClass=*)"
-# extended LDIF
-#
-# LDAPv3
-# base <dc=abmas,dc=biz> with scope sub
-# filter: (ObjectClass=*)
-# requesting: ALL
-#
-
-# abmas.biz
-dn: dc=abmas,dc=biz
-objectClass: dcObject
-objectClass: organization
-dc: abmas
-o: abmas
-
-# People, abmas.biz
-dn: ou=People,dc=abmas,dc=biz
-objectClass: organizationalUnit
-ou: People
-...
-# Domain Computers, Groups, abmas.biz
-dn: cn=Domain Computers,ou=Groups,dc=abmas,dc=biz
-objectClass: posixGroup
-objectClass: sambaGroupMapping
-gidNumber: 553
-cn: Domain Computers
-description: Netbios Domain Computers accounts
-sambaSID: S-1-5-21-3504140859-1010554828-2431957765-553
-sambaGroupType: 2
-displayName: Domain Computers
-
-# search result
-search: 2
-result: 0 Success
-
-# numResponses: 20
-# numEntries: 19
-</screen>
- Good. It is all working just fine.
- </para></step>
-
- <step><para>
- <indexterm><primary>getent</primary></indexterm>
- You must now make certain that the NSS resolver can interrogate LDAP also.
- Execute the following commands:
-<screen>
-&rootprompt; getent passwd | grep root
-root:x:998:512:Netbios Domain Administrator:/home:/bin/false
-
-&rootprompt; getent group | grep Domain
-Domain Admins:x:512:root
-Domain Users:x:513:
-Domain Guests:x:514:
-Domain Computers:x:553:
-</screen>
- <indexterm><primary>nss_ldap</primary></indexterm>
- This demonstrates that the <command>nss_ldap</command> library is functioning
- as it should. If these two steps fail to produce this information, refer to
- <link linkend="sbeavoid"/> for diagnostic procedures that can be followed to
- isolate the cause of the problem. Proceed to the next step only when the previous steps
- have been successfully completed.
- </para></step>
-
- <step><para>
- <indexterm><primary>smbldap-useradd</primary></indexterm>
- <indexterm><primary>smbldap-passwd</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- Our database is now ready for the addition of network users. For each user for
- whom an account must be created, execute the following:
-<screen>
-&rootprompt; ./smbldap-useradd -m -a <constant>username</constant>
-&rootprompt; ./smbldap-passwd <constant>username</constant>
-Changing password for <constant>username</constant>
-New password : XXXXXXXX
-Retype new password : XXXXXXXX
-
-&rootprompt; smbpasswd <constant>username</constant>
-New SMB password: XXXXXXXX
-Retype new SMB password: XXXXXXXX
-</screen>
- where <constant>username</constant> is the login ID for each user.
- </para></step>
-
- <step><para>
- <indexterm><primary>getent</primary></indexterm>
- Now verify that the UNIX (POSIX) accounts can be resolved via NSS by executing the
- following:
-<screen>
-&rootprompt; getent passwd
-root:x:0:0:root:/root:/bin/bash
-bin:x:1:1:bin:/bin:/bin/bash
-...
-root:x:0:512:Netbios Domain Administrator:/home:/bin/false
-nobody:x:999:514:nobody:/dev/null:/bin/false
-bobj:x:1000:513:System User:/home/bobj:/bin/bash
-stans:x:1001:513:System User:/home/stans:/bin/bash
-chrisr:x:1002:513:System User:/home/chrisr:/bin/bash
-maryv:x:1003:513:System User:/home/maryv:/bin/bash
-</screen>
- This demonstrates that user account resolution via LDAP is working.
- </para></step>
-
- <step><para>
- This step will determine whether or not identity resolution is working correctly.
- Do not procede is this step fails, rather find the cause of the failure. The
- <command>id</command> command may be used to validate your configuration so far,
- as shown here:
-<screen>
-&rootprompt; id chrisr
-uid=1002(chrisr) gid=513(Domain Users) groups=513(Domain Users)
-</screen>
- This confirms that the UNIX (POSIX) user account information can be resolved from LDAP
- by system tools that make a getentpw() system call.
- </para></step>
-
- <step><para>
- <indexterm><primary>smbldap-usermod</primary></indexterm>
- The root account must have UID=0; if not, this means that operations conducted from
- a Windows client using tools such as the Domain User Manager fails under UNIX because
- the management of user and group accounts requires that the UID=0. Additionally, it is
- a good idea to make certain that no matter how root account credentials are resolved,
- the home directory and shell are valid. You decide to effect this immediately
- as demonstrated here:
-<screen>
-&rootprompt; cd /opt/IDEALX/sbin
-&rootprompt; ./smbldap-usermod -u 0 -d /root -s /bin/bash root
-</screen>
- </para></step>
-
- <step><para>
- Verify that the changes just made to the <constant>root</constant> account were
- accepted by executing:
-<screen>
-&rootprompt; getent passwd | grep root
-root:x:0:0:root:/root:/bin/bash
-root:x:0:512:Netbios Domain Administrator:/root:/bin/bash
-</screen>
- This demonstrates that the changes were accepted.
- </para></step>
-
- <step><para>
- Make certain that a home directory has been created for every user by listing the
- directories in <filename>/home</filename> as follows:
-<screen>
-&rootprompt; ls -al /home
-drwxr-xr-x 8 root root 176 Dec 17 18:50 ./
-drwxr-xr-x 21 root root 560 Dec 15 22:19 ../
-drwx------ 7 bobj Domain Users 568 Dec 17 01:16 bobj/
-drwx------ 7 chrisr Domain Users 568 Dec 17 01:19 chrisr/
-drwx------ 7 maryv Domain Users 568 Dec 17 01:27 maryv/
-drwx------ 7 stans Domain Users 568 Dec 17 01:43 stans/
-</screen>
- This is precisely what we want to see.
- </para></step>
-
- <step><para>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>pdbedit</primary></indexterm>
- The final validation step involves making certain that Samba can obtain the user
- accounts from the LDAP ldapsam passwd backend. Execute the following command as shown:
-<screen>
-&rootprompt; pdbedit -Lv chrisr
-Unix username: chrisr
-NT username: chrisr
-Account Flags: [U ]
-User SID: S-1-5-21-3504140859-1010554828-2431957765-3004
-Primary Group SID: S-1-5-21-3504140859-1010554828-2431957765-513
-Full Name: System User
-Home Directory: \\MASSIVE\homes
-HomeDir Drive: H:
-Logon Script: scripts\login.cmd
-Profile Path: \\MASSIVE\profiles\chrisr
-Domain: MEGANET2
-Account desc: System User
-Workstations:
-Munged dial:
-Logon time: 0
-Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Password last set: Wed, 17 Dec 2003 17:17:40 GMT
-Password can change: Wed, 17 Dec 2003 17:17:40 GMT
-Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-Last bad password : 0
-Bad password count : 0
-Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
-</screen>
- This looks good. Of course, you fully expected that it would all work, didn't you?
- </para></step>
-
- <step><para>
- <indexterm><primary>smbldap-groupadd</primary></indexterm>
- Now you add the group accounts that are used on the Abmas network. Execute
- the following exactly as shown:
-<screen>
-&rootprompt; ./smbldap-groupadd -a Accounts
-&rootprompt; ./smbldap-groupadd -a Finances
-&rootprompt; ./smbldap-groupadd -a PIOps
-</screen>
- The addition of groups does not involve keyboard interaction, so the lack of console
- output is of no concern.
- </para></step>
-
- <step><para>
- <indexterm><primary>getent</primary></indexterm>
- You really do want to confirm that UNIX group resolution from LDAP is functioning
- as it should. Let's do this as shown here:
-<screen>
-&rootprompt; getent group
-...
-Domain Admins:x:512:root
-Domain Users:x:513:bobj,stans,chrisr,maryv
-Domain Guests:x:514:
-...
-Accounts:x:1000:
-Finances:x:1001:
-PIOps:x:1002:
-</screen>
- The well-known special accounts (Domain Admins, Domain Users, Domain Guests), as well
- as our own site-specific group accounts, are correctly listed. This is looking good.
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
- The final step we need to validate is that Samba can see all the Windows domain groups
- and that they are correctly mapped to the respective UNIX group account. To do this,
- just execute the following command:
-<screen>
-&rootprompt; net groupmap list
-Domain Admins (S-1-5-21-3504140859-...-2431957765-512) -> Domain Admins
-Domain Users (S-1-5-21-3504140859-...-2431957765-513) -> Domain Users
-Domain Guests (S-1-5-21-3504140859-...-2431957765-514) -> Domain Guests
-...
-Accounts (S-1-5-21-3504140859-1010554828-2431957765-3001) -> Accounts
-Finances (S-1-5-21-3504140859-1010554828-2431957765-3003) -> Finances
-PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps
-</screen>
- This is looking good. Congratulations &smbmdash; it works! Note that in the above output
- the lines were shortened by replacing the middle value (1010554828) of the SID with the
- ellipsis (...).
- </para></step>
-
- <step><para>
- The server you have so carefully built is now ready for another important step. You
- start the Samba server and validate its operation. Execute the following to render all
- the processes needed fully operative so that, on system reboot, they are automatically
- started:
-<screen>
-&rootprompt; chkconfig named on
-&rootprompt; chkconfig dhcpd on
-&rootprompt; chkconfig ldap on
-&rootprompt; chkconfig nmb on
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig winbind on
-&rootprompt; rcnmb start
-&rootprompt; rcsmb start
-&rootprompt; rcwinbind start
-</screen>
- </para></step>
-
- <step><para>
- The next step might seem a little odd at this point, but take note that you are about to
- start <command>winbindd</command>, which must be able to authenticate to the PDC via the
- localhost interface with the <command>smbd</command> process. This account can be
- easily created by joining the PDC to the domain by executing the following command:
-<screen>
-&rootprompt; net rpc join -S MASSIVE -U root%not24get
-</screen>
- Note: Before executing this command on the PDC, both <command>nmbd</command> and
- <command>smbd</command> must be started so that the <command>net</command> command
- can communicate with <command>smbd</command>. The expected output is as follows:
-<screen>
-Joined domain MEGANET2.
-</screen>
- This indicates that the domain security account for the PDC has been correctly created.
- </para></step>
-
- <step><para>
- At this time it is necessary to restart <command>winbindd</command> so that it can
- correctly authenticate to the PDC. The following command achieves that:
-<screen>
-&rootprompt; rcwinbind restart
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>smbclient</primary></indexterm>
- You may now check Samba operation as follows:
-<screen>
-&rootprompt; smbclient -L massive -U%
-
- Sharename Type Comment
- --------- ---- -------
- IPC$ IPC IPC Service (Samba 3.0.20)
- accounts Disk Accounting Files
- service Disk Financial Services Files
- pidata Disk Property Insurance Files
- apps Disk Application Files
- netlogon Disk Network Logon Service
- profiles Disk Profile Share
- profdata Disk Profile Data Share
- ADMIN$ IPC IPC Service (Samba 3.0.20)
-
- Server Comment
- --------- -------
- MASSIVE Samba 3.0.20
-
- Workgroup Master
- --------- -------
- MEGANET2 MASSIVE
-</screen>
- This shows that an anonymous connection is working.
- </para></step>
-
- <step><para>
- For your finale, let's try an authenticated connection:
-<screen>
-&rootprompt; smbclient //massive/bobj -Ubobj%n3v3r2l8
-smb: \> dir
- . D 0 Wed Dec 17 01:16:19 2003
- .. D 0 Wed Dec 17 19:04:42 2003
- bin D 0 Tue Sep 2 04:00:57 2003
- Documents D 0 Sun Nov 30 07:28:20 2003
- public_html D 0 Sun Nov 30 07:28:20 2003
- .urlview H 311 Fri Jul 7 06:55:35 2000
- .dvipsrc H 208 Fri Nov 17 11:22:02 1995
-
- 57681 blocks of size 524288. 57128 blocks available
-smb: \> q
-</screen>
- Well done. All is working fine.
- </para></step>
- </procedure>
-
- <para>
- The server <constant>MASSIVE</constant> is now configured, and it is time to move onto the next task.
- </para>
-
- </sect2>
-
- <sect2 id="sbehap-ptrcfg">
- <title>Printer Configuration</title>
-
- <para>
- <indexterm><primary>CUPS</primary></indexterm>
- The configuration for Samba to enable CUPS raw-print-through printing has already been
- taken care of in the &smb.conf; file. The only preparation needed for <constant>smart</constant>
- printing to be possible involves creation of the directories in which Samba stores
- Windows printing driver files.
- </para>
-
- <procedure>
- <title>Printer Configuration Steps</title>
-
- <step><para>
- Configure all network-attached printers to have a fixed IP address.
- </para></step>
-
- <step><para>
- Create an entry in the DNS database on the server <constant>MASSIVE</constant>
- in both the forward lookup database for the zone <constant>abmas.biz.hosts</constant>
- and in the reverse lookup database for the network segment that the printer is to
- be located in. Example configuration files for similar zones were presented in <link linkend="secure"/>,
- <link linkend="abmasbiz"/> and in <link linkend="eth2zone"/>.
- </para></step>
-
- <step><para>
- Follow the instructions in the printer manufacturers' manuals to permit printing
- to port 9100. Use any other port the manufacturer specifies for direct mode,
- raw printing. This allows the CUPS spooler to print using raw mode protocols.
- <indexterm><primary>CUPS</primary></indexterm>
- <indexterm><primary>raw printing</primary></indexterm>
- </para></step>
-
- <step><para>
- <indexterm><primary>lpadmin</primary></indexterm>
- <indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm>
- Only on the server to which the printer is attached, configure the CUPS Print
- Queues as follows:
-<screen>
-&rootprompt; lpadmin -p <parameter>printque</parameter>
- -v socket://<parameter>printer-name</parameter>.abmas.biz:9100 -E
-</screen>
- <indexterm><primary>print filter</primary></indexterm>
- This step creates the necessary print queue to use no assigned print filter. This
- is ideal for raw printing, that is, printing without use of filters.
- The name <parameter>printque</parameter> is the name you have assigned for
- the particular printer.
- </para></step>
-
- <step><para>
- Print queues may not be enabled at creation. Make certain that the queues
- you have just created are enabled by executing the following:
-<screen>
-&rootprompt; /usr/bin/enable <parameter>printque</parameter>
-</screen>
- </para></step>
-
- <step><para>
- Even though your print queue may be enabled, it is still possible that it
- may not accept print jobs. A print queue will service incoming printing
- requests only when configured to do so. Ensure that your print queue is
- set to accept incoming jobs by executing the following commands:
-<screen>
-&rootprompt; /usr/bin/accept <parameter>printque</parameter>
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>mime type</primary></indexterm>
- <indexterm><primary>/etc/mime.convs</primary></indexterm>
- <indexterm><primary>application/octet-stream</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
-<screen>
-application/octet-stream application/vnd.cups-raw 0 -
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/mime.types</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
-<screen>
-application/octet-stream
-</screen>
- </para></step>
-
- <step><para>
- Refer to the CUPS printing manual for instructions regarding how to configure
- CUPS so that print queues that reside on CUPS servers on remote networks
- route print jobs to the print server that owns that queue. The default setting
- on your CUPS server may automatically discover remotely installed printers and
- may permit this functionality without requiring specific configuration.
- </para></step>
-
- <step><para>
- The following action creates the necessary directory subsystem. Follow these
- steps to printing heaven:
-<screen>
-&rootprompt; mkdir -p /var/lib/samba/drivers/{W32ALPHA,W32MIPS,W32X86,WIN40}
-&rootprompt; chown -R root:root /var/lib/samba/drivers
-&rootprompt; chmod -R ug=rwx,o=rx /var/lib/samba/drivers
-</screen>
- </para></step>
-
- </procedure>
-
- </sect2>
-
-</sect1>
-
-<sect1 id="sbehap-bldg1">
- <title>Samba BDC Configuration</title>
-
- <procedure>
- <title>Configuration of BDC Called: <constant>BLDG1</constant></title>
-
- <step><para>
- Install the files in <link linkend="sbehap-bldg1-smbconf"/>,
- <link linkend="sbehap-shareconfa"/>, and <link linkend="sbehap-shareconfb"/>
- into the <filename>/etc/samba/</filename> directory. The three files
- should be added together to form the &smb.conf; file.
- </para></step>
-
- <step><para>
- Verify the &smb.conf; file as in step 2 of <link
- linkend="sbehap-massive"/>.
- </para></step>
-
- <step><para>
- Carefully follow the steps outlined in <link linkend="sbehap-PAM-NSS"/>, taking
- particular note to install the correct <filename>ldap.conf</filename>.
- </para></step>
-
- <step><para>
- Verify that the NSS resolver is working. You may need to cycle the run level
- to 1 and back to 5 before the NSS LDAP resolver functions. Follow these
- commands:
-<screen>
-&rootprompt; init 1
-</screen>
- After the run level has been achieved, you are prompted to provide the
- <constant>root</constant> password. Log on, and then execute:
-<screen>
-&rootprompt; init 5
-</screen>
- When the normal logon prompt appears, log into the system as <constant>root</constant>
- and then execute these commands:
-<screen>
-&rootprompt; getent passwd
-root:x:0:0:root:/root:/bin/bash
-bin:x:1:1:bin:/bin:/bin/bash
-daemon:x:2:2:Daemon:/sbin:/bin/bash
-lp:x:4:7:Printing daemon:/var/spool/lpd:/bin/bash
-mail:x:8:12:Mailer daemon:/var/spool/clientmqueue:/bin/false
-...
-root:x:0:512:Netbios Domain Administrator:/root:/bin/bash
-nobody:x:999:514:nobody:/dev/null:/bin/false
-bobj:x:1000:513:System User:/home/bobj:/bin/bash
-stans:x:1001:513:System User:/home/stans:/bin/bash
-chrisr:x:1002:513:System User:/home/chrisr:/bin/bash
-maryv:x:1003:513:System User:/home/maryv:/bin/bash
-vaioboss$:x:1005:553:vaioboss$:/dev/null:/bin/false
-bldg1$:x:1006:553:bldg1$:/dev/null:/bin/false
-</screen>
- This is the correct output. If the accounts that have UIDs above 512 are not shown, there is a problem.
- </para></step>
-
- <step><para>
- <indexterm><primary>getent</primary></indexterm>
- The next step in the verification process involves testing the operation of UNIX group
- resolution via the NSS LDAP resolver. Execute these commands:
-<screen>
-&rootprompt; getent group
-root:x:0:
-bin:x:1:daemon
-daemon:x:2:
-sys:x:3:
-...
-Domain Admins:x:512:root
-Domain Users:x:513:bobj,stans,chrisr,maryv,jht
-Domain Guests:x:514:
-Administrators:x:544:
-Users:x:545:
-Guests:x:546:nobody
-Power Users:x:547:
-Account Operators:x:548:
-Server Operators:x:549:
-Print Operators:x:550:
-Backup Operators:x:551:
-Replicator:x:552:
-Domain Computers:x:553:
-Accounts:x:1000:
-Finances:x:1001:
-PIOps:x:1002:
-</screen>
- This is also the correct and desired output, because it demonstrates that the LDAP client
- is able to communicate correctly with the LDAP server (<constant>MASSIVE</constant>).
- </para></step>
-
- <step><para>
- <indexterm><primary>smbpasswd</primary></indexterm>
- You must now set the LDAP administrative password into the Samba <filename>secrets.tdb</filename>
- file by executing this command:
-<screen>
-&rootprompt; smbpasswd -w not24get
-Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb
-</screen>
- </para></step>
-
- <step><para>
- Now you must obtain the domain SID from the PDC and store it into the
- <filename>secrets.tdb</filename> file also. This step is not necessary with an LDAP
- passdb backend because Samba obtains the domain SID from the
- sambaDomain object it automatically stores in the LDAP backend. It does not hurt to
- add the SID to the <filename>secrets.tdb</filename>, and if you wish to do so, this
- command can achieve that:
-<screen>
-&rootprompt; net rpc getsid MEGANET2
-Storing SID S-1-5-21-3504140859-1010554828-2431957765 \
- for Domain MEGANET2 in secrets.tdb
-</screen>
- When configuring a Samba BDC that has an LDAP backend, there is no need to take
- any special action to join it to the domain. However, winbind communicates with the
- domain controller that is running on the localhost and must be able to authenticate,
- thus requiring that the BDC should be joined to the domain. The process of joining
- the domain creates the necessary authentication accounts.
- </para></step>
-
- <step><para>
- To join the Samba BDC to the domain, execute the following:
-<screen>
-&rootprompt; net rpc join -U root%not24get
-Joined domain MEGANET2.
-</screen>
- This indicates that the domain security account for the BDC has been correctly created.
- </para></step>
-
- <step><para>
- <indexterm>
- <primary>pdbedit</primary>
- </indexterm>
- Verify that user and group account resolution works via Samba tools as follows:
-<screen>
-&rootprompt; pdbedit -L
-root:0:root
-nobody:65534:nobody
-bobj:1000:System User
-stans:1001:System User
-chrisr:1002:System User
-maryv:1003:System User
-bldg1$:1006:bldg1$
-
-&rootprompt; net groupmap list
-Domain Admins (S-1-5-21-3504140859-...-2431957765-512) ->
- Domain Admins
-Domain Users (S-1-5-21-3504140859-...-2431957765-513) -> Domain Users
-Domain Guests (S-1-5-21-3504140859-...-2431957765-514) ->
- Domain Guests
-Administrators (S-1-5-21-3504140859-...-2431957765-544) ->
- Administrators
-...
-Accounts (S-1-5-21-3504140859-1010554828-2431957765-3001) -> Accounts
-Finances (S-1-5-21-3504140859-1010554828-2431957765-3003) -> Finances
-PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps
-</screen>
- These results show that all things are in order.
- </para></step>
-
- <step><para>
- The server you have so carefully built is now ready for another important step. Now
- start the Samba server and validate its operation. Execute the following to render all
- the processes needed fully operative so that, upon system reboot, they are automatically
- started:
-<screen>
-&rootprompt; chkconfig named on
-&rootprompt; chkconfig dhcpd on
-&rootprompt; chkconfig nmb on
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig winbind on
-&rootprompt; rcnmb start
-&rootprompt; rcsmb start
-&rootprompt; rcwinbind start
-</screen>
- Samba should now be running and is ready for a quick test. But not quite yet!
- </para></step>
-
- <step><para>
- Your new <constant>BLDG1, BLDG2</constant> servers do not have home directories for users.
- To rectify this using the SUSE yast2 utility or by manually editing the <filename>/etc/fstab</filename>
- file, add a mount entry to mount the <constant>home</constant> directory that has been exported
- from the <constant>MASSIVE</constant> server. Mount this resource before proceeding. An alternate
- approach could be to create local home directories for users who are to use these machines.
- This is a choice that you, as system administrator, must make. The following entry in the
- <filename>/etc/fstab</filename> file suffices for now:
-<screen>
-massive.abmas.biz:/home /home nfs rw 0 0
-</screen>
- To mount this resource, execute:
-<screen>
-&rootprompt; mount -a
-</screen>
- Verify that the home directory has been mounted as follows:
-<screen>
-&rootprompt; df | grep home
-massive:/home 29532988 283388 29249600 1% /home
-</screen>
- </para></step>
-
- <step><para>
- Implement a quick check using one of the users that is in the LDAP database. Here you go:
-<screen>
-&rootprompt; smbclient //bldg1/bobj -Ubobj%n3v3r2l8
-smb: \> dir
- . D 0 Wed Dec 17 01:16:19 2003
- .. D 0 Wed Dec 17 19:04:42 2003
- bin D 0 Tue Sep 2 04:00:57 2003
- Documents D 0 Sun Nov 30 07:28:20 2003
- public_html D 0 Sun Nov 30 07:28:20 2003
- .urlview H 311 Fri Jul 7 06:55:35 2000
- .dvipsrc H 208 Fri Nov 17 11:22:02 1995
-
- 57681 blocks of size 524288. 57128 blocks available
-smb: \> q
-</screen>
- </para></step>
-
- </procedure>
-
- <para>
- Now that the first BDC (<constant>BDLG1</constant>) has been configured it is time to build
- and configure the second BDC server (<constant>BLDG2</constant>) as follows:
- </para>
-
- <procedure id="sbehap-bldg2">
- <title>Configuration of BDC Called <constant>BLDG2</constant></title>
-
- <step><para>
- Install the files in <link linkend="sbehap-bldg2-smbconf"/>,
- <link linkend="sbehap-shareconfa"/>, and <link linkend="sbehap-shareconfb"/>
- into the <filename>/etc/samba/</filename> directory. The three files
- should be added together to form the &smb.conf; file.
- </para></step>
-
- <step><para>
- Follow carefully the steps shown in <link linkend="sbehap-bldg1"/>, starting at step 2.
- </para></step>
-
- </procedure>
-
-<example id="sbehap-bldg1-smbconf">
-<title>LDAP Based &smb.conf; File, Server: BLDG1</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
- <smbconfoption name="unix charset">LOCALE</smbconfoption>
- <smbconfoption name="workgroup">MEGANET2</smbconfoption>
- <smbconfoption name="netbios name">BLDG1</smbconfoption>
- <smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
- <smbconfoption name="enable privileges">Yes</smbconfoption>
- <smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
- <smbconfoption name="log level">1</smbconfoption>
- <smbconfoption name="syslog">0</smbconfoption>
- <smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
- <smbconfoption name="max log size">50</smbconfoption>
- <smbconfoption name="smb ports">139</smbconfoption>
- <smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
- <smbconfoption name="printcap name">CUPS</smbconfoption>
- <smbconfoption name="show add printer wizard">No</smbconfoption>
- <smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
- <smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
- <smbconfoption name="logon drive">X:</smbconfoption>
- <smbconfoption name="domain logons">Yes</smbconfoption>
- <smbconfoption name="domain master">No</smbconfoption>
- <smbconfoption name="wins server">172.16.0.1</smbconfoption>
- <smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
- <smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
- <smbconfoption name="ldap user suffix">ou=People</smbconfoption>
- <smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
- <smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
- <smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
- <smbconfoption name="idmap backend">ldap:ldap://massive.abmas.biz</smbconfoption>
- <smbconfoption name="idmap uid">10000-20000</smbconfoption>
- <smbconfoption name="idmap gid">10000-20000</smbconfoption>
- <smbconfoption name="printing">cups</smbconfoption>
- <smbconfoption name="printer admin">root, chrisr</smbconfoption>
-</smbconfblock>
-</example>
-
-
-<example id="sbehap-bldg2-smbconf">
-<title>LDAP Based &smb.conf; File, Server: BLDG2</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
- <smbconfoption name="unix charset">LOCALE</smbconfoption>
- <smbconfoption name="workgroup">MEGANET2</smbconfoption>
- <smbconfoption name="netbios name">BLDG2</smbconfoption>
- <smbconfoption name="passdb backend">ldapsam:ldap://massive.abmas.biz</smbconfoption>
- <smbconfoption name="enable privileges">Yes</smbconfoption>
- <smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
- <smbconfoption name="log level">1</smbconfoption>
- <smbconfoption name="syslog">0</smbconfoption>
- <smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
- <smbconfoption name="max log size">50</smbconfoption>
- <smbconfoption name="smb ports">139</smbconfoption>
- <smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
- <smbconfoption name="printcap name">CUPS</smbconfoption>
- <smbconfoption name="show add printer wizard">No</smbconfoption>
- <smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
- <smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
- <smbconfoption name="logon drive">X:</smbconfoption>
- <smbconfoption name="domain logons">Yes</smbconfoption>
- <smbconfoption name="domain master">No</smbconfoption>
- <smbconfoption name="wins server">172.16.0.1</smbconfoption>
- <smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
- <smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
- <smbconfoption name="ldap user suffix">ou=People</smbconfoption>
- <smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
- <smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
- <smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
- <smbconfoption name="idmap backend">ldap:ldap://massive.abmas.biz</smbconfoption>
- <smbconfoption name="idmap uid">10000-20000</smbconfoption>
- <smbconfoption name="idmap gid">10000-20000</smbconfoption>
- <smbconfoption name="printing">cups</smbconfoption>
- <smbconfoption name="printer admin">root, chrisr</smbconfoption>
-</smbconfblock>
-</example>
-
-
-<example id="sbehap-shareconfa">
-<title>LDAP Based &smb.conf; File, Shares Section &smbmdash; Part A</title>
-<smbconfblock>
-<smbconfsection name="[accounts]"/>
- <smbconfoption name="comment">Accounting Files</smbconfoption>
- <smbconfoption name="path">/data/accounts</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[service]"/>
- <smbconfoption name="comment">Financial Services Files</smbconfoption>
- <smbconfoption name="path">/data/service</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[pidata]"/>
- <smbconfoption name="comment">Property Insurance Files</smbconfoption>
- <smbconfoption name="path">/data/pidata</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[homes]"/>
- <smbconfoption name="comment">Home Directories</smbconfoption>
- <smbconfoption name="valid users">%S</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
- <smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
- <smbconfoption name="comment">SMB Print Spool</smbconfoption>
- <smbconfoption name="path">/var/spool/samba</smbconfoption>
- <smbconfoption name="guest ok">Yes</smbconfoption>
- <smbconfoption name="printable">Yes</smbconfoption>
- <smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="sbehap-shareconfb">
-<title>LDAP Based &smb.conf; File, Shares Section &smbmdash; Part B</title>
-<smbconfblock>
-<smbconfsection name="[apps]"/>
- <smbconfoption name="comment">Application Files</smbconfoption>
- <smbconfoption name="path">/apps</smbconfoption>
- <smbconfoption name="admin users">bjordan</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
- <smbconfoption name="comment">Network Logon Service</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
- <smbconfoption name="guest ok">Yes</smbconfoption>
- <smbconfoption name="locking">No</smbconfoption>
-
-<smbconfsection name="[profiles]"/>
- <smbconfoption name="comment">Profile Share</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
- <smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[profdata]"/>
- <smbconfoption name="comment">Profile Data Share</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
- <smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[print$]"/>
- <smbconfoption name="comment">Printer Drivers</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
- <smbconfoption name="browseable">yes</smbconfoption>
- <smbconfoption name="guest ok">no</smbconfoption>
- <smbconfoption name="read only">yes</smbconfoption>
- <smbconfoption name="write list">root, chrisr</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="sbehap-ldifadd">
-<title>LDIF IDMAP Add-On Load File &smbmdash; File: /etc/openldap/idmap.LDIF</title>
-<screen>
-dn: ou=Idmap,dc=abmas,dc=biz
-objectClass: organizationalUnit
-ou: idmap
-structuralObjectClass: organizationalUnit
-</screen>
-</example>
-
-</sect1>
-
-<sect1>
- <title>Miscellaneous Server Preparation Tasks</title>
-
- <para>
- My father would say, <quote>Dinner is not over until the dishes have been done.</quote>
- The makings of a great network environment take a lot of effort and attention to detail.
- So far, you have completed most of the complex (and to many administrators, the interesting
- part of server configuration) steps, but remember to tie it all together. Here are
- a few more steps that must be completed so that your network runs like a well-rehearsed
- orchestra.
- </para>
-
- <sect2>
- <title>Configuring Directory Share Point Roots</title>
-
- <para>
- In your &smb.conf; file, you have specified Windows shares. Each has a <parameter>path</parameter>
- parameter. Even though it is obvious to all, one of the common Samba networking problems is
- caused by forgetting to verify that every such share root directory actually exists and that it
- has the necessary permissions and ownership.
- </para>
-
- <para>
- Here is an example, but remember to create the directory needed for every share:
-<screen>
-&rootprompt; mkdir -p /data/{accounts,finsvcs,piops}
-&rootprompt; mkdir -p /apps
-&rootprompt; chown -R root:root /data
-&rootprompt; chown -R root:root /apps
-&rootprompt; chown -R bobj:Accounts /data/accounts
-&rootprompt; chown -R bobj:Finances /data/finsvcs
-&rootprompt; chown -R bobj:PIOps /data/piops
-&rootprompt; chmod -R ug+rwxs,o-rwx /data
-&rootprompt; chmod -R ug+rwx,o+rx-w /apps
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Configuring Profile Directories</title>
-
- <para>
- You made a conscious decision to do everything it would take to improve network client
- performance. One of your decisions was to implement folder redirection. This means that Windows
- user desktop profiles are now made up of two components: a dynamically loaded part and a set of file
- network folders.
- </para>
-
- <para>
- For this arrangement to work, every user needs a directory structure for the network folder
- portion of his or her profile as shown here:
-<screen>
-&rootprompt; mkdir -p /var/lib/samba/profdata
-&rootprompt; chown root:root /var/lib/samba/profdata
-&rootprompt; chmod 755 /var/lib/samba/profdata
-
-# Per user structure
-&rootprompt; cd /var/lib/samba/profdata
-&rootprompt; mkdir -p <emphasis>username</emphasis>
-&rootprompt; for i in InternetFiles Cookies History AppData \
- LocalSettings MyPictures MyDocuments Recent
-&rootprompt; do
-&rootprompt; mkdir <emphasis>username</emphasis>/$i
-&rootprompt; done
-&rootprompt; chown -R <emphasis>username</emphasis>:Domain\ Users <emphasis>username</emphasis>
-&rootprompt; chmod -R 750 <emphasis>username</emphasis>
-</screen>
- </para>
-
- <para>
- <indexterm><primary>roaming profile</primary></indexterm>
- <indexterm><primary>mandatory profile</primary></indexterm>
- You have three options insofar as the dynamically loaded portion of the roaming profile
- is concerned:
- </para>
-
- <itemizedlist>
- <listitem><para>You may permit the user to obtain a default profile.</para></listitem>
- <listitem><para>You can create a mandatory profile.</para></listitem>
- <listitem><para>You can create a group profile (which is almost always a mandatory profile).</para></listitem>
- </itemizedlist>
-
- <para>
- Mandatory profiles cannot be overwritten by a user. The change from a user profile to a mandatory
- profile is effected by renaming the <filename>NTUSER.DAT</filename> to <filename>NTUSER.MAN</filename>,
- that is, just by changing the filename extension.
- </para>
-
- <para>
- <indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
- <indexterm><primary>Domain User Manager</primary></indexterm>
- The location of the profile that a user can obtain is set in the user's account in the LDAP passdb backend.
- You can manage this using the Idealx smbldap-tools or using the
- <ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">Windows NT4 Domain User Manager</ulink>.
- </para>
-
- <para>
- It may not be obvious that you must ensure that the root directory for the user's profile exists
- and has the needed permissions. Use the following commands to create this directory:
-<screen>
-&rootprompt; mkdir -p /var/lib/samba/profiles/<emphasis>username</emphasis>
-&rootprompt; chown <emphasis>username</emphasis>:Domain\ Users
- /var/lib/samba/profiles/<emphasis>username</emphasis>
-&rootprompt; chmod 700 /var/lib/samba/profiles/<emphasis>username</emphasis>
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Preparation of Logon Scripts</title>
-
- <para>
- <indexterm><primary>logon script</primary></indexterm>
- The use of a logon script with Windows XP Professional is an option that every site should consider.
- Unless you have locked down the desktop so the user cannot change anything, there is risk that
- a vital network drive setting may be broken or that printer connections may be lost. Logon scripts
- can help to restore persistent network folder (drive) and printer connections in a predictable
- manner. One situation in which such breakage may occur in particular is when a mobile PC (notebook)
- user attaches to another company's network that forces environment changes that are alien to your
- network.
- </para>
-
- <para>
- If you decide to use network logon scripts, by reference to the &smb.conf; files for the domain
- controllers, you see that the path to the share point for the <constant>NETLOGON</constant>
- share defined is <filename>/var/lib/samba/netlogon</filename>. The path defined for the logon
- script inside that share is <filename>scripts\logon.bat</filename>. This means that as a Windows
- NT/200x/XP client logs onto the network, it tries to obtain the file <filename>logon.bat</filename>
- from the fully qualified path <filename>/var/lib/samba/netlogon/scripts</filename>. This fully
- qualified path should therefore exist whether you install the <filename>logon.bat</filename>.
- </para>
-
- <para>
- You can, of course, create the fully qualified path by executing:
-<screen>
-&rootprompt; mkdir -p /var/lib/samba/netlogon/scripts
-</screen>
- </para>
-
- <para>
- You should research the options for logon script implementation by referring to <emphasis>TOSHARG2</emphasis>, Chapter 24,
- Section 24.4. A quick Web search will bring up a host of options. One of the most popular logon
- facilities in use today is called <ulink url="http://www.kixtart.org">KiXtart</ulink>.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Assigning User Rights and Privileges</title>
-
- <para>
- The ability to perform tasks such as joining Windows clients to the domain can be assigned to
- normal user accounts. By default, only the domain administrator account (<constant>root</constant> on UNIX
- systems because it has UID=0) can add accounts. New to Samba 3.0.11 is the ability to grant
- this privilege in a very limited fashion to particular accounts.
- </para>
-
- <para>
- By default, even Samba-3.0.11 does not grant any rights even to the <constant>Domain Admins</constant>
- group. Here we grant this group all privileges.
- </para>
-
- <para>
- Samba limits privileges on a per-server basis. This is a deliberate limitation so that users who
- are granted rights can be restricted to particular machines. It is left to the network administrator
- to determine which rights should be provided and to whom.
- </para>
-
- <procedure>
- <title>Steps for Assignment of User Rights and Privileges</title>
-
- <step><para>
- Log onto the PDC as the <constant>root</constant> account.
- </para></step>
-
- <step><para>
- Execute the following command to grant the <constant>Domain Admins</constant> group all
- rights and privileges:
-<screen>
-&rootprompt; net -S MASSIVE -U root%not24get rpc rights grant \
- "MEGANET2\Domain Admins" SeMachineAccountPrivilege \
- SePrintOperatorPrivilege SeAddUsersPrivilege \
- SeDiskOperatorPrivilege SeRemoteShutdownPrivilege
-Successfully granted rights.
-</screen>
- Repeat this step on each domain controller, in each case substituting the name of the server
- (e.g., BLDG1, BLDG2) in place of the PDC called MASSIVE.
- </para></step>
-
- <step><para>
- In this step the privilege will be granted to Bob Jordan (bobj) to add Windows workstations
- to the domain. Execute the following only on the PDC. It is not necessary to do this on
- BDCs or on DMS machines because machine accounts are only ever added by the PDC:
-<screen>
-&rootprompt; net -S MASSIVE -U root%not24get rpc rights grant \
- "MEGANET2\bobj" SeMachineAccountPrivilege
-Successfully granted rights.
-</screen>
- </para></step>
-
- <step><para>
- Verify that privilege assignments have been correctly applied by executing:
-<screen>
-net rpc rights list accounts -Uroot%not24get
-MEGANET2\bobj
-SeMachineAccountPrivilege
-
-S-0-0
-No privileges assigned
-
-BUILTIN\Print Operators
-No privileges assigned
-
-BUILTIN\Account Operators
-No privileges assigned
-
-BUILTIN\Backup Operators
-No privileges assigned
-
-BUILTIN\Server Operators
-No privileges assigned
-
-BUILTIN\Administrators
-No privileges assigned
-
-Everyone
-No privileges assigned
-
-MEGANET2\Domain Admins
-SeMachineAccountPrivilege
-SePrintOperatorPrivilege
-SeAddUsersPrivilege
-SeRemoteShutdownPrivilege
-SeDiskOperatorPrivilege
-</screen>
- </para></step>
-
- </procedure>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Windows Client Configuration</title>
-
- <para>
- <indexterm><primary>NETLOGON</primary></indexterm>
- In the next few sections, you can configure a new Windows XP Professional disk image on a staging
- machine. You will configure all software, printer settings, profile and policy handling, and desktop
- default profile settings on this system. When it is complete, you copy the contents of the
- <filename>C:\Documents and Settings\Default User</filename> directory to a directory with the same
- name in the <constant>NETLOGON</constant> share on the domain controllers.
- </para>
-
- <para>
- Much can be learned from the Microsoft Support site regarding how best to set up shared profiles.
- One knowledge-base article in particular stands out:
- "<ulink url="http://support.microsoft.com/default.aspx?scid=kb;EN-US;168475">How to Create a
- Base Profile for All Users."</ulink>
-
- </para>
-
- <sect2 id="redirfold">
- <title>Configuration of Default Profile with Folder Redirection</title>
-
- <para>
- <indexterm><primary>folder redirection</primary></indexterm>
- Log onto the Windows XP Professional workstation as the local <constant>Administrator</constant>.
- It is necessary to expose folders that are generally hidden to provide access to the
- <constant>Default User</constant> folder.
- </para>
-
- <procedure>
- <title>Expose Hidden Folders</title>
-
- <step><para>
- Launch the Windows Explorer by clicking
- <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>My Computer</guimenuitem>
- <guimenuitem>Tools</guimenuitem>
- <guimenuitem>Folder Options</guimenuitem>
- <guimenuitem>View Tab</guimenuitem>
- </menuchoice>.
- Select <guilabel>Show hidden files and folders</guilabel>,
- and click <guibutton>OK</guibutton>. Exit Windows Explorer.
- </para></step>
-
- <step><para>
- <indexterm><primary>regedt32</primary></indexterm>
- Launch the Registry Editor. Click
- <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Run</guimenuitem>
- </menuchoice>. Key in <command>regedt32</command>, and click
- <guibutton>OK</guibutton>.
- </para></step>
-
- </procedure>
-
- <para>
- </para>
-
- <procedure id="sbehap-rdrfldr">
- <title>Redirect Folders in Default System User Profile</title>
-
- <step><para>
- <indexterm><primary>HKEY_LOCAL_MACHINE</primary></indexterm>
- <indexterm><primary>Default User</primary></indexterm>
- Give focus to <constant>HKEY_LOCAL_MACHINE</constant> hive entry in the left panel.
- Click <menuchoice>
- <guimenu>File</guimenu>
- <guimenuitem>Load Hive...</guimenuitem>
- <guimenuitem>Documents and Settings</guimenuitem>
- <guimenuitem>Default User</guimenuitem>
- <guimenuitem>NTUSER</guimenuitem>
- <guimenuitem>Open</guimenuitem>
- </menuchoice>. In the dialog box that opens, enter the key name
- <constant>Default</constant> and click <guibutton>OK</guibutton>.
- </para></step>
-
- <step><para>
- Browse inside the newly loaded Default folder to:
-<screen>
-HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
- CurrentVersion\Explorer\User Shell Folders\
-</screen>
- The right panel reveals the contents as shown in <link linkend="XP-screen001"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>%USERPROFILE%</primary></indexterm>
- <indexterm><primary>%LOGONSERVER%</primary></indexterm>
- You edit hive keys. Acceptable values to replace the
- <constant>%USERPROFILE%</constant> variable includes:
-
- <itemizedlist>
- <listitem><para>A drive letter such as <constant>U:</constant></para></listitem>
- <listitem><para>A direct network path such as
- <constant>\\MASSIVE\profdata</constant></para></listitem>
- <listitem><para>A network redirection (UNC name) that contains a macro such as </para>
- <para><constant>%LOGONSERVER%\profdata\</constant></para></listitem>
- </itemizedlist>
- </para></step>
-
- <step><para>
- <indexterm><primary>registry keys</primary></indexterm>
- Set the registry keys as shown in <link linkend="proffold"/>. Your implementation makes the assumption
- that users have statically located machines. Notebook computers (mobile users) need to be
- accommodated using local profiles. This is not an uncommon assumption.
- </para></step>
-
- <step><para>
- Click back to the root of the loaded hive <constant>Default</constant>.
- Click <menuchoice><guimenu>File</guimenu><guimenuitem>Unload Hive...</guimenuitem>
- <guimenuitem>Yes</guimenuitem></menuchoice>.
- </para></step>
-
- <step><para>
- <indexterm><primary>Registry Editor</primary></indexterm>
- Click <menuchoice><guimenu>File</guimenu><guimenuitem>Exit</guimenuitem></menuchoice>. This exits the
- Registry Editor.
- </para></step>
-
- <step><para>
- Now follow the procedure given in <link linkend="sbehap-locgrppol"/>. Make sure that each folder you
- have redirected is in the exclusion list.
- </para></step>
-
- <step><para>
- You are now ready to copy<footnote><para>
- There is an alternate method by which a default user profile can be added to the
- <constant>NETLOGON</constant> share. This facility in the Windows System tool
- permits profiles to be exported. The export target may be a particular user or
- group profile share point or else the <constant>NETLOGON</constant> share.
- In this case, the profile directory must be named <constant>Default User</constant>.
- </para></footnote>
- the Default User profile to the Samba domain controllers. Launch Microsoft Windows Explorer,
- and use it to copy the full contents of the directory <filename>Default User</filename> that
- is in the <filename>C:\Documents and Settings</filename> to the root directory of the
- <constant>NETLOGON</constant> share. If the <constant>NETLOGON</constant> share has the defined
- UNIX path of <filename>/var/lib/samba/netlogon</filename>, when the copy is complete there must
- be a directory in there called <filename>Default User</filename>.
- </para></step>
-
- </procedure>
-
- <para>
- Before punching out new desktop images for the client workstations, it is perhaps a good idea that
- desktop behavior should be returned to the original Microsoft settings. The following steps achieve
- that ojective:
- </para>
-
- <procedure>
- <title>Reset Folder Display to Original Behavior</title>
-
- <step><para>
- To launch the Windows Explorer, click
- <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>My Computer</guimenuitem>
- <guimenuitem>Tools</guimenuitem>
- <guimenuitem>Folder Options</guimenuitem>
- <guimenuitem>View Tab</guimenuitem>
- </menuchoice>.
- Deselect <guilabel>Show hidden files and folders</guilabel>, and click <guibutton>OK</guibutton>.
- Exit Windows Explorer.
- </para></step>
-
- </procedure>
-
- <figure id="XP-screen001">
- <title>Windows XP Professional &smbmdash; User Shared Folders</title>
- <imagefile scale="65">XP-screen001</imagefile>
- </figure>
-
-<table id="proffold">
- <title>Default Profile Redirections</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry>Registry Key</entry>
- <entry>Redirected Value</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Cache</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\InternetFiles</entry>
- </row>
- <row>
- <entry>Cookies</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\Cookies</entry>
- </row>
- <row>
- <entry>History</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\History</entry>
- </row>
- <row>
- <entry>Local AppData</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\AppData</entry>
- </row>
- <row>
- <entry>Local Settings</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\LocalSettings</entry>
- </row>
- <row>
- <entry>My Pictures</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\MyPictures</entry>
- </row>
- <row>
- <entry>Personal</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\MyDocuments</entry>
- </row>
- <row>
- <entry>Recent</entry>
- <entry>%LOGONSERVER%\profdata\%USERNAME%\Recent</entry>
- </row>
- </tbody>
- </tgroup>
-</table>
-
- </sect2>
-
- <sect2>
- <title>Configuration of MS Outlook to Relocate PST File</title>
-
- <para>
- <indexterm><primary>Outlook</primary><secondary>PST</secondary></indexterm>
- <indexterm><primary>MS Outlook</primary><secondary>PST</secondary></indexterm>
- Microsoft Outlook can store a Personal Storage file, generally known as a PST file.
- It is the nature of email storage that this file grows, at times quite rapidly.
- So that users' email is available to them at every workstation they may log onto,
- it is common practice in well-controlled sites to redirect the PST folder to the
- users' home directory. Follow these steps for each user who wishes to do this.
- </para>
-
- <para>
- To redirect the Outlook PST file in Outlook 2003 (older versions of Outlook behave
- slightly differently), follow these steps:
- </para>
-
- <procedure>
- <title>Outlook PST File Relocation</title>
-
- <step><para>
- Close Outlook if it is open.
- </para></step>
-
- <step><para>
- From the <guimenu>Control Panel</guimenu>, launch the Mail icon.
- </para></step>
-
- <step><para>
- Click <guimenu>Email Accounts.</guimenu>
- </para></step>
-
- <step><para>
- Make a note of the location of the PST file(s). From this location, move
- the files to the desired new target location. The most desired new target location
- may well be the users' home directory.
- </para></step>
-
- <step><para>
- Add a new data file, selecting the PST file in the new desired target location.
- Give this entry (not the filename) a new name such as <quote>Personal Mail Folders.</quote>
- </para>
-
- <para>
- Note: If MS Outlook has been configured to use an IMAP account configuration there may be problems
- following these instructions. Feedback from users suggests that where IMAP is used the PST
- file is used to store rules and filters. When the PST store is relocated it appears to break
- MS Outlook's Send/Receive button. If anyone has successfully relocated PST files where IMAP is
- used please email <literal>jht@samba.org</literal> with useful tips and suggestions so that
- this warning can be removed or modified.
- </para></step>
-
- <step><para>
- Close the <guimenu>Date Files</guimenu> windows, then click <guimenu>Email Accounts</guimenu>.
- </para></step>
-
- <step><para>
- Select <guimenu>View of Change</guimenu> exiting email accounts, click <guibutton>Next.</guibutton>
- </para></step>
-
- <step><para>
- Change the <guimenu>Mail Delivery Location</guimenu> so as to use the data file in the new
- target location.
- </para></step>
-
- <step><para>
- Go back to the <guimenu>Data Files</guimenu> window, then delete the old data file entry.
- </para></step>
-
- </procedure>
-
- <note><para>
- <indexterm><primary>Outlook Address Book</primary></indexterm>
- You may have to remove and reinstall the Outlook Address Book (Contacts) entries, otherwise
- the user may be not be able to retrieve contacts when addressing a new email message.
- </para></note>
-
- <note><para>
- <indexterm><primary>Outlook Express</primary></indexterm>
- Outlook Express is not at all like MS OutLook. It stores file very differently also. Outlook
- Express storage files can not be redirected to network shares. The options panel will not permit
- this, but they can be moved to folders outside of the user's profile. They can also be excluded
- from folder synchronization as part of the roaming profile.
- </para>
-
- <para>
- While it is possible to redirect the data stores for Outlook Express data stores by editing the
- registry, experience has shown that data corruption and loss of email messages will result.
- </para>
-
- <para>
- <indexterm><primary>Outlook Express</primary></indexterm>
- <indexterm><primary>MS Outlook</primary></indexterm>
- In the same vane as MS Outlook, Outlook Express data stores can become very large. When used with
- roaming profiles this can result in excruciatingly long login and logout behavior will files are
- synchronized. For this reason, it is highly recommended not to use Outlook Express where roaming
- profiles are used.
- </para></note>
-
- <para>
- <indexterm><primary>PST file</primary></indexterm>
- Microsoft does not support storing PST files on network shares, although the practice does appear
- to be rather popular. Anyone who does relocation the PST file to a network resource should refer
- the Microsoft <ulink url="http://support.microsoft.com/kb/297019/">reference</ulink> to better
- understand the issues.
- </para>
-
- <para>
- <indexterm><primary>PST file</primary></indexterm>
- Apart from manually moving PST files to a network share, it is possible to set the default PST
- location for new accounts by following the instructions at the WindowsITPro <ulink
- url="http://www.windowsitpro.com/Windows/Article/ArticleID/48228/48228.html">web</ulink> site.
- </para>
-
- <para>
- <indexterm><primary>PST file</primary></indexterm>
- User feedback suggests that disabling of oplocks on PST files will significantly improve
- network performance by reducing locking overheads. One way this can be done is to add to the
- &smb.conf; file stanza for the share the PST file the following:
-<screen>
-veto oplock files = /*.pdf/*.PST/
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Configure Delete Cached Profiles on Logout</title>
-
- <para>
- Configure the Windows XP Professional client to auto-delete roaming profiles on logout:
- </para>
-
- <para>
- <indexterm><primary>MMC</primary></indexterm>
- Click
- <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Run</guimenuitem>
- </menuchoice>. In the dialog box, enter <command>MMC</command> and click <guibutton>OK</guibutton>.
- </para>
-
- <para>
- Follow these steps to set the default behavior of the staging machine so that all roaming
- profiles are deleted as network users log out of the system. Click
- <menuchoice>
- <guimenu>File</guimenu>
- <guimenuitem>Add/Remove Snap-in</guimenuitem>
- <guimenuitem>Add</guimenuitem>
- <guimenuitem>Group Policy</guimenuitem>
- <guimenuitem>Add</guimenuitem>
- <guimenuitem>Finish</guimenuitem>
- <guimenuitem>Close</guimenuitem>
- <guimenuitem>OK</guimenuitem>
- </menuchoice>.
- </para>
-
- <para>
- <indexterm><primary>Microsoft Management Console</primary><see>MMC</see></indexterm>
- The Microsoft Management Console now shows the <guimenu>Group Policy</guimenu>
- utility that enables you to set the policies needed. In the left panel, click
- <menuchoice>
- <guimenuitem>Local Computer Policy</guimenuitem>
- <guimenuitem>Administrative Templates</guimenuitem>
- <guimenuitem>System</guimenuitem>
- <guimenuitem>User Profiles</guimenuitem>
- </menuchoice>. In the right panel, set the properties shown here by double-clicking on each
- item as shown:
- </para>
-
- <itemizedlist>
- <listitem><para>Do not check for user ownership of Roaming Profile Folders = Enabled</para></listitem>
- <listitem><para>Delete cached copies of roaming profiles = Enabled</para></listitem>
- </itemizedlist>
-
- <para>
- Close the Microsoft Management Console. The settings take immediate effect and persist onto all image copies
- made of this system to deploy the new standard desktop system.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Uploading Printer Drivers to Samba Servers</title>
-
- <para>
- <indexterm><primary>printing</primary><secondary>drag-and-drop</secondary></indexterm>
- Users want to be able to use network printers. You have a vested interest in making
- it easy for them to print. You have chosen to install the printer drivers onto the Samba
- servers and to enable point-and-click (drag-and-drop) printing. This process results in
- Samba being able to automatically provide the Windows client with the driver necessary to
- print to the printer chosen. The following procedure must be followed for every network
- printer:
- </para>
-
- <procedure>
- <title>Steps to Install Printer Drivers on the Samba Servers</title>
-
- <step><para>
- Join your Windows XP Professional workstation (the staging machine) to the
- <constant>MEGANET2</constant> domain. If you are not sure of the procedure,
- follow the guidance given in <link linkend="appendix"/>, <link linkend="domjoin"/>.
- </para></step>
-
- <step><para>
- After the machine has rebooted, log onto the workstation as the domain
- <constant>root</constant> (this is the Administrator account for the
- operating system that is the host platform for this implementation of Samba.
- </para></step>
-
- <step><para>
- Launch MS Windows Explorer. Navigate in the left panel. Click
- <menuchoice>
- <guimenu>My Network Places</guimenu>
- <guimenuitem>Entire Network</guimenuitem>
- <guimenuitem>Microsoft Windows Network</guimenuitem>
- <guimenuitem>Meganet2</guimenuitem>
- <guimenuitem>Massive</guimenuitem>
- </menuchoice>. Click on <guimenu>Massive</guimenu>
- <guimenu>Printers and Faxes</guimenu>.
- </para></step>
-
- <step><para>
- Identify a printer that is shown in the right panel. Let us assume the printer is called
- <constant>ps01-color</constant>. Right-click on the <guimenu>ps01-color</guimenu> icon
- and select the <guimenu>Properties</guimenu> entry. This opens a dialog box that indicates
- that <quote>The printer driver is not installed on this computer. Some printer properties
- will not be accessible unless you install the printer driver. Do you want to install the
- driver now?</quote> It is important at this point you answer <guimenu>No</guimenu>.
- </para></step>
-
- <step><para>
- The printer properties panel for the <guimenu>ps01-color</guimenu> printer on the server
- <constant>MASSIVE</constant> is displayed. Click the <guimenu>Advanced</guimenu> tab.
- Note that the box labeled <guimenu>Driver</guimenu> is empty. Click the <guimenu>New Driver</guimenu>
- button that is next to the <guimenu>Driver</guimenu> box. This launches the <quote>Add Printer Wizard</quote>.
- </para></step>
-
- <step><para>
- <indexterm><primary>Add Printer Wizard</primary><secondary>APW</secondary></indexterm>
- <indexterm><primary>APW</primary></indexterm>
- The <quote>Add Printer Driver Wizard on <constant>MASSIVE</constant></quote> panel
- is now presented. Click <guimenu>Next</guimenu> to continue. From the left panel, select the
- printer manufacturer. In your case, you are adding a driver for a printer manufactured by
- Lexmark. In the right panel, select the printer (Lexmark Optra Color 40 PS). Click
- <guimenu>Next</guimenu>, and then <guimenu>Finish</guimenu> to commence driver upload. A
- progress bar appears and instructs you as each file is being uploaded and that it is being
- directed at the network server <constant>\\massive\ps01-color</constant>.
- </para></step>
-
- <step><para>
- <indexterm><primary>printers</primary><secondary>Advanced</secondary></indexterm>
- <indexterm><primary>printers</primary><secondary>Properties</secondary></indexterm>
- <indexterm><primary>printers</primary><secondary>Sharing</secondary></indexterm>
- <indexterm><primary>printers</primary><secondary>General</secondary></indexterm>
- <indexterm><primary>printers</primary><secondary>Security</secondary></indexterm>
- <indexterm><primary>AD printer publishing</primary></indexterm>
- The driver upload completes in anywhere from a few seconds to a few minutes. When it completes,
- you are returned to the <guimenu>Advanced</guimenu> tab in the <guimenu>Properties</guimenu> panel.
- You can set the Location (under the <guimenu>General</guimenu> tab) and Security settings (under
- the <guimenu>Security</guimenu> tab). Under the <guimenu>Sharing</guimenu> tab it is possible to
- load additional printer drivers; there is also a check-box in this tab called <quote>List in the
- directory</quote>. When this box is checked, the printer will be published in Active Directory
- (Applicable to Active Directory use only.)
- </para></step>
-
- <step><para>
- <indexterm><primary>printers</primary><secondary>Default Settings</secondary></indexterm>
- Click <guimenu>OK</guimenu>. It will take a minute or so to upload the settings to the server.
- You are now returned to the <guimenu>Printers and Faxes on Massive</guimenu> monitor.
- Right-click on the printer, click <menuchoice><guimenu>Properties</guimenu>
- <guimenuitem>Device Settings</guimenuitem> </menuchoice>. Now change the settings to suit
- your requirements. BE CERTAIN TO CHANGE AT LEAST ONE SETTING and apply the changes even if
- you need to reverse the changes back to their original settings.
- </para></step>
-
- <step><para>
- This is necessary so that the printer settings are initialized in the Samba printers
- database. Click <guimenu>Apply</guimenu> to commit your settings. Revert any settings you changed
- just to initialize the Samba printers database entry for this printer. If you need to revert a setting,
- click <guimenu>Apply</guimenu> again.
- </para></step>
-
- <step><para>
- <indexterm><primary>Print Test Page</primary></indexterm>
- Verify that all printer settings are at the desired configuration. When you are satisfied that they are,
- click the <guimenu>General</guimenu> tab. Now click the <guimenu>Print Test Page</guimenu> button.
- A test page should print. Verify that it has printed correctly. Then click <guimenu>OK</guimenu>
- in the panel that is newly presented. Click <guimenu>OK</guimenu> on the <guimenu>ps01-color on
- massive Properties</guimenu> panel.
- </para></step>
-
- <step><para>
- You must repeat this process for all network printers (i.e., for every printer on each server).
- When you have finished uploading drivers to all printers, close all applications. The next task
- is to install software your users require to do their work.
- </para></step>
-
- </procedure>
-
- </sect2>
-
- <sect2>
- <title>Software Installation</title>
-
- <para>
- Your network has both fixed desktop workstations as well as notebook computers. As a general rule, it is
- a good idea to not tamper with the operating system that is provided by the notebook computer manufacturer.
- Notebooks require special handling that is beyond the scope of this chapter.
- </para>
-
- <para>
- For desktop systems, the installation of software onto administratively centralized application servers
- make a lot of sense. This means that you can manage software maintenance from a central
- perspective and that only minimal application stubware needs to be installed onto the desktop
- systems. You should proceed with software installation and default configuration as far as is humanly
- possible and so long as it makes sense to do so. Make certain to thoroughly test and validate every aspect
- of software operations and configuration.
- </para>
-
- <para>
- When you believe that the overall configuration is complete, be sure to create a shared group profile
- and migrate that to the Samba server for later reuse when creating custom mandatory profiles, just in
- case a user may have specific needs you had not anticipated.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Roll-out Image Creation</title>
-
- <para>
- The final steps before preparing the distribution Norton Ghost image file you might follow are:
- </para>
-
- <blockquote><para>
- Unjoin the domain &smbmdash; Each workstation requires a unique name and must be independently
- joined into domain membership.
- </para></blockquote>
-
- <blockquote><para>
- Defragment the hard disk &smbmdash; While not obvious to the uninitiated, defragmentation results
- in better performance and often significantly reduces the size of the compressed disk image. That
- also means it will take less time to deploy the image onto 500 workstations.
- </para></blockquote>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Key Points Learned</title>
-
- <para>
- This chapter introduced many new concepts. Is it a sad fact that the example presented deliberately
- avoided any consideration of security. Security does not just happen; you must design it into your total
- network. Security begins with a systems design and implementation that anticipates hostile behavior from
- users both inside and outside the organization. Hostile and malicious intruders do not respect barriers;
- they accept them as challenges. For that reason, if not simply from a desire to establish safe networking
- practices, you must not deploy the design presented in this book in an environment where there is risk
- of compromise.
- </para>
-
- <para>
- <indexterm><primary>Access Control Lists</primary><see>ACLs</see></indexterm>
- <indexterm><primary>ACLs</primary></indexterm>
- As a minimum, the LDAP server must be protected by way of Access Control Lists (ACLs), and it must be
- configured to use secure protocols for all communications over the network. Of course, secure networking
- does not result just from systems design and implementation but involves constant user education
- training and, above all, disciplined attention to detail and constant searching for signs of unfriendly
- or alien activities. Security is itself a topic for a whole book. Please do consult appropriate sources.
- Jerry Carter's book <ulink url="http://www.booksense.com/product/info.jsp&isbn=1565924916">
- <emphasis>LDAP System Administration</emphasis></ulink> is a good place to start reading about OpenLDAP
- as well as security considerations.
- </para>
-
- <para>
- The substance of this chapter that has been deserving of particular attention includes:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Implementation of an OpenLDAP-based passwd backend, necessary to support distributed
- domain control.
- </para></listitem>
-
- <listitem><para>
- Implementation of Samba primary and secondary domain controllers with a common LDAP backend
- for user and group accounts that is shared with the UNIX system through the PADL nss_ldap and
- pam_ldap tool-sets.
- </para></listitem>
-
- <listitem><para>
- Use of the Idealx smbldap-tools scripts for UNIX (POSIX) account management as well as
- to manage Samba Windows user and group accounts.
- </para></listitem>
-
- <listitem><para>
- The basics of implementation of Group Policy controls for Windows network clients.
- </para></listitem>
-
- <listitem><para>
- Control over roaming profiles, with particular focus on folder redirection to network drives.
- </para></listitem>
-
- <listitem><para>
- Use of the CUPS printing system together with Samba-based printer driver auto-download.
- </para></listitem>
- </itemizedlist>
-
-</sect1>
-
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- Well, here we are at the end of this chapter and we have only ten questions to help you to
- remember so much. There are bound to be some sticky issues here.
- </para>
-
- <qandaset defaultlabel="chap06qa" type="number">
- <qandaentry>
- <question>
-
- <para>
- Why did you not cover secure practices? Isn't it rather irresponsible to instruct
- network administrators to implement insecure solutions?
- </para>
-
- </question>
- <answer>
-
- <para>
- Let's get this right. This is a book about Samba, not about OpenLDAP and secure
- communication protocols for subjects other than Samba. Earlier on, you note,
- that the dynamic DNS and DHCP solutions also used no protective secure communications
- protocols. The reason for this is simple: There are so many ways of implementing
- secure protocols that this book would have been even larger and more complex.
- </para>
-
- <para>
- The solutions presented here all work (at least they did for me). Network administrators
- have the interest and the need to be better trained and instructed in secure networking
- practices and ought to implement safe systems. I made the decision, right or wrong,
- to keep this material as simple as possible. The intent of this book is to demonstrate
- a working solution and not to discuss too many peripheral issues.
- </para>
-
- <para>
- This book makes little mention of backup techniques. Does that mean that I am recommending
- that you should implement a network without provision for data recovery and for disaster
- management? Back to our focus: The deployment of Samba has been clearly demonstrated.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- You have focused much on SUSE Linux and little on the market leader, Red Hat. Do
- you have a problem with Red Hat Linux? Doesn't that make your guidance irrelevant
- to the Linux I might be using?
- </para>
-
- </question>
- <answer>
-
- <para>
- Both Red Hat Linux and SUSE Linux comply with the Linux Standards Base specifications
- for a standard Linux distribution. The differences are marginal. Surely you know
- your Linux platform, and you do have access to administration manuals for it. This
- book is not a Linux tutorial; it is a Samba tutorial. Let's keep the focus on
- the Samba part of the book; all the other bits are peripheral (but important) to
- creation of a total network solution.
- </para>
-
- <para>
- What I find interesting is the attention reviewers give to Linux installation and to
- the look and feel of the desktop, but does that make for a great server? In this book,
- I have paid particular attention to the details of creating a whole solution framework.
- I have not tightened every nut and bolt, but I have touched on all the issues you
- need to be familiar with. Over the years many people have approached me wanting to
- know the details of exactly how to implement a DHCP and dynamic DNS server with Samba
- and WINS. In this chapter, it is plain to see what needs to be configured to provide
- transparent interoperability. Likewise for CUPS and Samba interoperation. These are
- key stumbling areas for many people.
- </para>
-
- <para>
- At every critical junction, I have provided comparative guidance for both SUSE and
- Red Hat Linux. Both manufacturers have done a great job in furthering the cause
- of open source software. I favor neither and respect both. I like particular
- features of both products (companies also). No bias in presentation is intended.
- Oh, before I forget, I particularly like Debian Linux; that is my favorite playground.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- You did not use SWAT to configure Samba. Is there something wrong with it?
- </para>
-
- </question>
- <answer>
-
- <para>
- That is a good question. As it is, the &smb.conf; file configurations are presented
- in as direct a format as possible. Adding SWAT into the equation would have complicated
- matters. I sought simplicity of implementation. The fact is that I did use SWAT to
- create the files in the first place.
- </para>
-
- <para>
- There are people in the Linux and open source community who feel that SWAT is dangerous
- and insecure. Many will not touch it with a barge-pole. By not introducing SWAT, I
- hope to have brought their interests on board. SWAT is well covered is <emphasis>TOSHARG2</emphasis>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- You have exposed a well-used password <emphasis>not24get</emphasis>. Is that
- not irresponsible?
- </para>
-
- </question>
- <answer>
-
- <para>
- Well, I had to use a password of some sort. At least this one has been consistently
- used throughout. I guess you can figure out that in a real deployment it would make
- sense to use a more secure and original password.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- The Idealx smbldap-tools create many domain group accounts that are not used. Is that
- a good thing?
- </para>
-
- </question>
- <answer>
-
- <para>
- I took this up with Idealx and found them most willing to change that in the next version.
- Let's give Idealx some credit for the contribution they have made. I appreciate their work
- and, besides, it does no harm to create accounts that are not now used &smbmdash; at some time
- Samba may well use them.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Can I use LDAP just for Samba accounts and not for UNIX system accounts?
- </para>
-
- </question>
- <answer>
-
- <para>
- Yes, you can do that for user accounts only. Samba requires there to be a POSIX (UNIX)
- group account for every Windows domain group account. But if you put your users into
- the system password account, how do you plan to keep all domain controller system
- password files in sync? I think that having everything in LDAP makes a lot of sense
- for the UNIX administrator who is still learning the craft and is migrating from MS Windows.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why are the Windows domain RID portions not the same as the UNIX UID?
- </para>
-
- </question>
- <answer>
-
- <para>
- Samba uses a well-known public algorithm for assigning RIDs from UIDs and GIDs.
- This algorithm ought to ensure that there will be no clashes with well-known RIDs.
- Well-known RIDs have special significance to MS Windows clients. The automatic
- assignment used the calculation: RID = UID x 2 + 1000. Of course, Samba does
- permit you to override that to some extent. See the &smb.conf; man page entry
- for <parameter>algorithmic rid base</parameter>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Printer configuration examples all show printing to the HP port 9100. Does this
- mean that I must have HP printers for these solutions to work?
- </para>
-
- </question>
- <answer>
-
- <para>
- No. You can use any type of printer and must use the interfacing protocol supported
- by the printer. Many networks use LPR/LPD print servers to which are attached
- PCL printers, inkjet printers, plotters, and so on. At home I use a USB-attached
- inkjet printer. Use the appropriate device URI (Universal Resource Interface)
- argument to the <constant>lpadmin -v</constant> option that is right for your
- printer.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Is folder redirection dangerous? I've heard that you can lose your data that way.
- </para>
-
- </question>
- <answer>
-
- <para>
- The only loss of data I know of that involved folder redirection was caused by
- manual misuse of the redirection tool. The administrator redirected a folder to
- a network drive and said he wanted to migrate (move) the data over. Then he
- changed his mind, so he moved the folder back to the roaming profile. This time,
- he declined to move the data because he thought it was still in the local profile
- folder. That was not the case, so by declining to move the data back, he wiped out
- the data. You cannot hold the tool responsible for that. Caveat emptor still applies.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Is it really necessary to set a local Group Policy to exclude the redirected
- folders from the roaming profile?
- </para>
-
- </question>
- <answer>
-
- <para>
- Yes. If you do not do this, the data will still be copied from the network folder
- (share) to the local cached copy of the profile.
- </para>
-
- </answer>
- </qandaentry>
-
- </qandaset>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="ntmigration">
- <title>Migrating NT4 Domain to Samba</title>
-
- <para>
- Ever since Microsoft announced that it was discontinuing support for Windows
- NT4, Samba users started to ask for detailed instructions on how to migrate
- from NT4 to Samba. This chapter provides background information that should
- meet these needs.
- </para>
-
- <para>
- One wonders how many NT4 systems will be left in service by the time you read this
- book though.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para><indexterm>
- <primary>migration</primary>
- </indexterm>
- Network administrators who want to migrate off a Windows NT4 environment know
- one thing with certainty. They feel that NT4 has been abandoned, and they want
- to update. The desire to get off NT4 and to not adopt Windows 200x and Active
- Directory is driven by a mixture of concerns over complexity, cost, fear of
- failure, and much more.
- </para>
-
- <para>
- <indexterm><primary>group policies</primary></indexterm>
- <indexterm><primary>accounts</primary><secondary>user</secondary></indexterm>
- <indexterm><primary>accounts</primary><secondary>group</secondary></indexterm>
- <indexterm><primary>accounts</primary><secondary>machine</secondary></indexterm>
- The migration from NT4 to Samba can involve a number of factors, including
- migration of data to another server, migration of network environment controls
- such as group policies, and migration of the users, groups, and machine
- accounts.
- </para>
-
- <para>
- <indexterm><primary>accounts</primary><secondary>Domain</secondary></indexterm>
- It should be pointed out now that it is possible to migrate some systems from
- a Windows NT4 domain environment to a Samba domain environment. This is certainly
- not possible in every case. It is possible to just migrate the domain accounts
- to Samba and then to switch machines, but as a hands-off transition, this is more
- the exception than the rule. Most systems require some tweaking after
- migration before an environment that is acceptable for immediate use
- is obtained.
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- You are about to migrate an MS Windows NT4 domain accounts database to
- a Samba server. The Samba-3 server is using a
- <parameter>passdb backend</parameter> based on LDAP. The
- <constant>ldapsam</constant> is ideal because an LDAP backend can be distributed
- for use with BDCs &smbmdash; generally essential for larger networks.
- </para>
-
- <para>
- Your objective is to document the process of migrating user and group accounts
- from several NT4 domains into a single Samba LDAP backend database.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>snap-shot</primary></indexterm>
- <indexterm><primary>NT4 registry</primary></indexterm>
- <indexterm><primary>registry</primary><secondary>keys</secondary><tertiary>SAM</tertiary></indexterm>
- <indexterm><primary>registry</primary><secondary>keys</secondary><tertiary>SECURITY</tertiary></indexterm>
- <indexterm><primary>SAM</primary></indexterm>
- <indexterm><primary>Security Account Manager</primary><see>SAM</see></indexterm>
- The migration process takes a snapshot of information that is stored in the
- Windows NT4 registry-based accounts database. That information resides in
- the Security Account Manager (SAM) portion of the NT4 registry under keys called
- <constant>SAM</constant> and <constant>SECURITY</constant>.
- </para>
-
- <warning><para>
- <indexterm><primary>crippled</primary></indexterm>
- <indexterm><primary>inoperative</primary></indexterm>
- The Windows NT4 registry keys called <constant>SAM</constant> and <constant>SECURITY</constant>
- are protected so that you cannot view the contents. If you change the security setting
- to reveal the contents under these hive keys, your Windows NT4 domain is crippled. Do not
- do this unless you are willing to render your domain controller inoperative.
- </para></warning>
-
- <para>
- <indexterm><primary>migration</primary><secondary>objectives</secondary></indexterm>
- <indexterm><primary>disruptive</primary></indexterm>
- Before commencing an NT4 to Samba migration, you should consider what your objectives are.
- While in some cases it is possible simply to migrate an NT4 domain to a single Samba server,
- that may not be a good idea from an administration perspective. Since the process involves going
- through a certain amount of disruptive activity anyhow, why not take this opportunity to
- review the structure of the network, how Windows clients are controlled and how they
- interact with the network environment.
- </para>
-
- <para>
- <indexterm><primary>network</primary><secondary>logon scripts</secondary></indexterm>
- <indexterm><primary>profiles share</primary></indexterm>
- <indexterm><primary>security descriptors</primary></indexterm>
- MS Windows NT4 was introduced some time around 1996. Many environments in which NT4 was deployed
- have done little to keep the NT4 server environment up to date with more recent Windows releases,
- particularly Windows XP Professional. The migration provides opportunity to revise and update
- roaming profile deployment as well as folder redirection. Given that you must port the
- greater network configuration of this from the old NT4 server to the new Samba server.
- Do not forget to validate the security descriptors in the profiles share as well as network logon
- scripts. Feedback from sites that are migrating to Samba suggests that many are using this
- as a good time to update desktop systems also. In all, the extra effort should constitute no
- real disruption to users, but rather, with due diligence and care, should make their network experience
- a much happier one.
- </para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- <indexterm><primary>strategic</primary></indexterm>
- <indexterm><primary>active directory</primary></indexterm>
- Migration of an NT4 domain user and group database to Samba involves a certain strategic
- element. Many sites have asked for instructions regarding merging of multiple NT4
- domains into one Samba LDAP database. It seems that this is viewed as a significant
- added value compared with the alternative of migration to Windows Server 200x and Active
- Directory. The diagram in <link linkend="ch8-migration"/> illustrates the effect of migration
- from a Windows NT4 domain to a Samba domain.
- </para>
-
- <figure id="ch8-migration">
- <title>Schematic Explaining the <command>net rpc vampire</command> Process</title>
- <imagefile scale="55">ch8-migration</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>merge</primary></indexterm>
- <indexterm><primary>passdb.tdb</primary></indexterm>
- If you want to merge multiple NT4 domain account databases into one Samba domain,
- you must now dump the contents of the first migration and edit it as appropriate. Now clean
- out (remove) the tdbsam backend file (<filename>passdb.tdb</filename>) or the LDAP database
- files. You must start each migration with a new database into which you merge your NT4
- domains.
- </para>
-
- <para><indexterm>
- <primary>dump</primary>
- </indexterm>
- At this point, you are ready to perform the second migration, following the same steps as
- for the first. In other words, dump the database, edit it, and then you may merge the
- dump for the first and second migrations.
- </para>
-
- <para><indexterm>
- <primary>LDAP</primary>
- </indexterm><indexterm>
- <primary>migrate</primary>
- </indexterm><indexterm>
- <primary>Domain SID</primary>
- </indexterm>
- You must be careful. If you choose to migrate to an LDAP backend, your dump file
- now contains the full account information, including the domain SID. The domain SID for each
- of the two NT4 domains will be different. You must choose one and change the domain
- portion of the account SIDs so that all are the same.
- </para>
-
- <para>
- <indexterm><primary>passdb.tdb</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>merged</primary></indexterm>
- <indexterm><primary>logon script</primary></indexterm>
- <indexterm><primary>logon hours</primary></indexterm>
- <indexterm><primary>logon machines</primary></indexterm>
- <indexterm><primary>profile path</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>LDAP backend</primary></indexterm>
- <indexterm><primary>export</primary></indexterm>
- <indexterm><primary>import</primary></indexterm>
- If you choose to use a tdbsam (<filename>passdb.tdb</filename>) backend file, your best choice
- is to use <command>pdbedit</command> to export the contents of the tdbsam file into an
- smbpasswd data file. This automatically strips out all domain-specific information,
- such as logon hours, logon machines, logon script, profile path, as well as the domain SID.
- The resulting file can be easily merged with other migration attempts (each of which must start
- with a clean file). It should also be noted that all users who end up in the merged smbpasswd
- file must have an account in <filename>/etc/passwd</filename>. The resulting smbpasswd file
- may be exported or imported into either a tdbsam (<filename>passdb.tdb</filename>) or
- an LDAP backend.
- </para>
-
- <figure id="NT4DUM">
- <title>View of Accounts in NT4 Domain User Manager</title>
- <imagefile scale="50">UserMgrNT4</imagefile>
- </figure>
-
-</sect2>
-
-
-<sect2>
- <title>Political Issues</title>
-
- <para>
- The merging of multiple Windows NT4-style domains into a single LDAP-backend-based Samba
- domain may be seen by those who had power over them as a loss of prestige or a loss of
- power. The imposition of a single domain may even be seen as a threat. So in migrating and
- merging account databases, be consciously aware of the political fall-out in which you
- may find yourself entangled when key staff feel a loss of prestige.
- </para>
-
- <para>
- The best advice that can be given to those who set out to merge NT4 domains into a single
- Samba domain is to promote (sell) the action as one that reduces costs and delivers
- greater network interoperability and manageability.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- From feedback on the Samba mailing lists, it seems that most Windows NT4 migrations
- to Samba are being performed using a new server or a new installation of a Linux or UNIX
- server. If you contemplate doing this, please note that the steps that follow in this
- chapter assume familiarity with the information that has been previously covered in this
- book. You are particularly encouraged to be familiar with <link linkend="secure"/>,
- <link linkend="Big500users"/> and <link linkend="happy"/>.
- </para>
-
- <para>
- We present here the steps and example output for two NT4 to Samba domain migrations. The
- first uses an LDAP-based backend, and the second uses a tdbsam backend. In each case the
- scripts you specify in the &smb.conf; file for the <parameter>add user script</parameter>
- collection of parameters are used to effect the addition of accounts into the passdb backend.
- </para>
-
- <para>
- Before proceeding to NT4 migration using either a tdbsam or ldapsam, it is most strongly recommended to
- review <link linkend="ch5-dnshcp-setup"/> for DNS and DHCP configuration. The importance of correctly
- functioning name resolution must be recognized. This applies equally for both hostname and NetBIOS names
- (machine names, computer names, domain names, workgroup names &smbmdash; ALL names!).
- </para>
-
- <para>
- The migration process involves the following steps:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Prepare the target Samba server. This involves configuring Samba-3 for
- migration to either a tdbsam or an ldapsam backend.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>uppercase</primary></indexterm>
- <indexterm><primary>Posix</primary></indexterm>
- <indexterm><primary>lower-case</primary></indexterm>
- Clean up the source NT4 PDC. Delete all accounts that need not be migrated.
- Delete all files that should not be migrated. Where possible, change NT group
- names so there are no spaces or uppercase characters. This is important if
- the target UNIX host insists on POSIX-compliant all lowercase user and group
- names.
- </para></listitem>
-
- <listitem><para>
- Step through the migration process.
- </para></listitem>
-
- <listitem><para><indexterm><primary>PDC</primary></indexterm>
- Remove the NT4 PDC from the network.
- </para></listitem>
-
- <listitem><para>
- Upgrade the Samba server from a BDC to a PDC, and validate all account
- information.
- </para></listitem>
- </itemizedlist>
-
- <para>
- It may help to use the above outline as a pre-migration checklist.
- </para>
-
- <sect2>
- <title>NT4 Migration Using LDAP Backend</title>
-
- <para>
- In this example, the migration is of an NT4 PDC to a Samba PDC with an LDAP backend. The accounts about
- to be migrated are shown in <link linkend="NT4DUM"/>. In this example use is made of the
- smbldap-tools scripts to add the accounts that are migrated into the ldapsam passdb backend.
- Four scripts are essential to the migration process. Other scripts will be required
- for daily management, but these are not critical to migration. The critical scripts are dependant
- on which passdb backend is being used. Refer to <link linkend="ch8-vampire"/> to see which scripts
- must be provided so that the migration process can complete.
- </para>
-
- <para>
- Verify that you have correctly specified in the &smb.conf; file the scripts and arguments
- that should be passed to them before attempting to perform the account migration. Note also
- that the deletion scripts must be commented out during migration. These should be uncommented
- following successful migration of the NT4 Domain accounts.
- </para>
-
- <warning><para>
- Under absolutely no circumstances should the Samba daemons be started until instructed to do so.
- Delete the <filename>/etc/samba/secrets.tdb</filename> file and all Samba control tdb files
- before commencing the following configuration steps.
- </para></warning>
-
- <table id="ch8-vampire">
- <title>Samba &smb.conf; Scripts Essential to Samba Operation</title>
- <tgroup cols="3">
- <colspec align="left"/>
- <colspec align="center"/>
- <colspec align="center"/>
- <thead>
- <row>
- <entry>Entity</entry>
- <entry>ldapsam Script</entry>
- <entry>tdbsam Script</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Add User Accounts</entry>
- <entry>smbldap-useradd</entry>
- <entry>useradd</entry>
- </row>
- <row>
- <entry>Delete User Accounts</entry>
- <entry>smbldap-userdel</entry>
- <entry>userdel</entry>
- </row>
- <row>
- <entry>Add Group Accounts</entry>
- <entry>smbldap-groupadd</entry>
- <entry>groupadd</entry>
- </row>
- <row>
- <entry>Delete Group Accounts</entry>
- <entry>smbldap-groupdel</entry>
- <entry>groupdel</entry>
- </row>
- <row>
- <entry>Add User to Group</entry>
- <entry>smbldap-groupmod</entry>
- <entry>usermod (See Note)</entry>
- </row>
- <row>
- <entry>Add Machine Accounts</entry>
- <entry>smbldap-useradd</entry>
- <entry>useradd</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <note><para>
- <indexterm><primary>usermod</primary></indexterm>
- <indexterm><primary>groupmem</primary></indexterm>
- <indexterm><primary>smbldap-tools</primary></indexterm>
- The UNIX/Linux <command>usermod</command> utility does not permit simple user addition to (or deletion
- of users from) groups. This is a feature provided by the smbldap-tools scripts. If you want this
- capability, you must create your own tool to do this. Alternately, you can search the Web
- to locate a utility called <command>groupmem</command> (by George Kraft) that provides this functionality.
- The <command>groupmem</command> utility was contributed to the shadow package but has not surfaced
- in the formal commands provided by Linux distributions (March 2004).
- </para></note>
-
- <note><para>
- <indexterm><primary>tdbdump</primary></indexterm>
- The <command>tdbdump</command> utility is a utility that you can build from the Samba source-code tree. Not all Linux binary distributions include this tool. If it is missing from your
- Linux distribution, you will need to build this yourself or else forgo its use.
- </para></note>
-
- <para>
- <indexterm><primary>User Manager</primary></indexterm>
- Before starting the migration, all dead accounts were removed from the NT4 domain using the User Manager for Domains.
- </para>
-
- <procedure>
- <title>User Migration Steps</title>
-
- <step><para>
- Configure the Samba &smb.conf; file to create a BDC. An example configuration is
- given in <link linkend="sbent4smb"/>.
- The delete scripts are commented out so that during the process of migration
- no account information can be deleted.
- </para></step>
-
-<example id="sbent4smb">
-<title>NT4 Migration Samba Server <filename>smb.conf</filename> &smbmdash; Part: A</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
- <smbconfoption name="workgroup">DAMNATION</smbconfoption>
- <smbconfoption name="netbios name">MERLIN</smbconfoption>
- <smbconfoption name="passdb backend">ldapsam:ldap://localhost</smbconfoption>
- <smbconfoption name="log level">1</smbconfoption>
- <smbconfoption name="syslog">0</smbconfoption>
- <smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
- <smbconfoption name="max log size">0</smbconfoption>
- <smbconfoption name="smb ports">139 445</smbconfoption>
- <smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
- <smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m '%u'</smbconfoption>
- <smbconfoption name="#delete user script">/opt/IDEALX/sbin/smbldap-userdel '%u'</smbconfoption>
- <smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd '%g'</smbconfoption>
- <smbconfoption name="#delete group script">/opt/IDEALX/sbin/smbldap-groupdel '%g'</smbconfoption>
- <smbconfoption name="add user to group script">/opt/IDEALX/sbin/ smbldap-groupmod -m '%u' '%g'</smbconfoption>
- <smbconfoption name="#delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x '%u' '%g'</smbconfoption>
- <smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'</smbconfoption>
- <smbconfoption name="add machine script">/opt/IDEALX/sbin/smbldap-useradd -w '%u'</smbconfoption>
- <smbconfoption name="logon script">scripts\logon.cmd</smbconfoption>
- <smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
- <smbconfoption name="logon home">\\%L\%U</smbconfoption>
- <smbconfoption name="logon drive">X:</smbconfoption>
- <smbconfoption name="domain logons">Yes</smbconfoption>
- <smbconfoption name="domain master">No</smbconfoption>
- <smbconfoption name="#wins support">Yes</smbconfoption>
- <smbconfoption name="wins server">192.168.123.124</smbconfoption>
- <smbconfoption name="ldap admin dn">cn=Manager,dc=terpstra-world,dc=org</smbconfoption>
- <smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
- <smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
- <smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
- <smbconfoption name="ldap passwd sync">Yes</smbconfoption>
- <smbconfoption name="ldap suffix">dc=terpstra-world,dc=org</smbconfoption>
- <smbconfoption name="ldap ssl">no</smbconfoption>
- <smbconfoption name="ldap timeout">20</smbconfoption>
- <smbconfoption name="ldap user suffix">ou=People</smbconfoption>
- <smbconfoption name="idmap backend">ldap:ldap://localhost</smbconfoption>
- <smbconfoption name="idmap uid">15000-20000</smbconfoption>
- <smbconfoption name="idmap gid">15000-20000</smbconfoption>
- <smbconfoption name="winbind nested groups">Yes</smbconfoption>
- <smbconfoption name="ea support">Yes</smbconfoption>
- <smbconfoption name="map acl inherit">Yes</smbconfoption>
- </smbconfblock>
-</example>
-
-<example id="sbent4smb2">
-<title>NT4 Migration Samba Server <filename>smb.conf</filename> &smbmdash; Part: B</title>
-<smbconfblock>
-<smbconfsection name="[apps]"/>
- <smbconfoption name="comment">Application Data</smbconfoption>
- <smbconfoption name="path">/data/home/apps</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[homes]"/>
- <smbconfoption name="comment">Home Directories</smbconfoption>
- <smbconfoption name="path">/home/users/%U/Documents</smbconfoption>
- <smbconfoption name="valid users">%S</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
- <smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
- <smbconfoption name="comment">SMB Print Spool</smbconfoption>
- <smbconfoption name="path">/var/spool/samba</smbconfoption>
- <smbconfoption name="guest ok">Yes</smbconfoption>
- <smbconfoption name="printable">Yes</smbconfoption>
- <smbconfoption name="use client driver">No</smbconfoption>
- <smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
- <smbconfoption name="comment">Network Logon Service</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
- <smbconfoption name="guest ok">Yes</smbconfoption>
- <smbconfoption name="locking">No</smbconfoption>
-
-<smbconfsection name="[profiles]"/>
- <smbconfoption name="comment">Profile Share</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
- <smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[profdata]"/>
- <smbconfoption name="comment">Profile Data Share</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/profdata</smbconfoption>
- <smbconfoption name="read only">No</smbconfoption>
- <smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[print$]"/>
- <smbconfoption name="comment">Printer Drivers</smbconfoption>
- <smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
- </smbconfblock>
-</example>
-
- <step><para>
- <indexterm><primary>slapd.conf</primary></indexterm>
- Configure OpenLDAP in preparation for the migration. An example
- <filename>sladp.conf</filename> file is shown in <link linkend="sbentslapd"/>.
- The <constant>rootpw</constant> value is an encrypted password string that can
- be obtained by executing the <command>slappasswd</command> command.
- </para></step>
-
-<example id="sbentslapd">
-<title>NT4 Migration LDAP Server Configuration File: <filename>/etc/openldap/slapd.conf</filename> &smbmdash; Part A</title>
-<screen>
-include /etc/openldap/schema/core.schema
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/nis.schema
-include /etc/openldap/schema/samba3.schema
-
-pidfile /var/run/slapd/slapd.pid
-argsfile /var/run/slapd/slapd.args
-
-access to dn.base=""
- by self write
- by * auth
-
-access to attr=userPassword
- by self write
- by * auth
-
-access to attr=shadowLastChange
- by self write
- by * read
-
-access to *
- by * read
- by anonymous auth
-</screen>
-</example>
-
-<example id="sbentslapd2">
-<title>NT4 Migration LDAP Server Configuration File: <filename>/etc/openldap/slapd.conf</filename> &smbmdash; Part B</title>
-<screen>
-#loglevel 256
-
-#schemacheck on
-idletimeout 30
-#backend bdb
-database bdb
-checkpoint 1024 5
-cachesize 10000
-
-suffix "dc=terpstra-world,dc=org"
-rootdn "cn=Manager,dc=terpstra-world,dc=org"
-
-# rootpw = not24get
-rootpw {SSHA}86kTavd9Dw3FAz6qzWTrCOKX/c0Qe+UV
-
-directory /var/lib/ldap
-
-# Indices to maintain
-index objectClass eq
-index cn pres,sub,eq
-index sn pres,sub,eq
-index uid pres,sub,eq
-index displayName pres,sub,eq
-index uidNumber eq
-index gidNumber eq
-index memberUID eq
-index sambaSID eq
-index sambaPrimaryGroupSID eq
-index sambaDomainName eq
-index default sub
-</screen>
-</example>
-
- <step><para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- <indexterm><primary>/etc/ldap.conf</primary></indexterm>
- Install the PADL <command>nss_ldap</command> tool set, then configure the <filename>/etc/ldap.conf</filename>
- as shown in <link linkend="sbrntldapconf"/>.
- </para></step>
-
-<example id="sbrntldapconf">
-<title>NT4 Migration NSS LDAP File: <filename>/etc/ldap.conf</filename></title>
-<screen>
-host 127.0.0.1
-
-base dc=terpstra-world,dc=org
-
-ldap_version 3
-
-binddn cn=Manager,dc=terpstra-world,dc=org
-bindpw not24get
-
-pam_password exop
-
-nss_base_passwd ou=People,dc=terpstra-world,dc=org?one
-nss_base_shadow ou=People,dc=terpstra-world,dc=org?one
-nss_base_group ou=Groups,dc=terpstra-world,dc=org?one
-
-ssl off
-</screen>
-</example>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- Edit the <filename>/etc/nsswitch.conf</filename> file so it has the entries shown
- in <link linkend="sbentnss"/>. Note that the LDAP entries have been commented out.
- This is deliberate. If these entries are active (not commented out), and the
- <filename>/etc/ldap.conf</filename> file has been configured, when the LDAP server
- is started, the process of starting the LDAP server will cause LDAP lookups. This
- causes the LDAP server <command>slapd</command> to hang because it finds port 389
- open and therefore cannot gain exclusive control of it. By commenting these entries
- out, it is possible to avoid this gridlock situation and thus the overall
- installation and configuration will progress more smoothly.
- </para></step>
-
-<example id="sbentnss">
-<title>NT4 Migration NSS Control File: <filename>/etc/nsswitch.conf</filename> (Stage:1)</title>
-<screen>
-passwd: files #ldap
-shadow: files #ldap
-group: files #ldap
-
-hosts: files dns wins
-networks: files dns
-
-services: files
-protocols: files
-rpc: files
-ethers: files
-netmasks: files
-netgroup: files
-publickey: files
-
-bootparams: files
-automount: files nis
-aliases: files
-#passwd_compat: ldap #Not needed.
-#group_compat: ldap #Not needed.
-</screen>
-</example>
-
- <step><para>
- Validate the the target NT4 PDC name is being correctly resolved to its IP address by
- executing the following:
-<screen>
-&rootprompt; ping transgression
-PING transgression.terpstra-world.org (192.168.1.5) 56(84) bytes of data.
-64 bytes from (192.168.1.5): icmp_seq=1 ttl=128 time=0.159 ms
-64 bytes from (192.168.1.5): icmp_seq=2 ttl=128 time=0.192 ms
-64 bytes from (192.168.1.5): icmp_seq=3 ttl=128 time=0.141 ms
-
---- transgression.terpstra-world.org ping statistics ---
-3 packets transmitted, 3 received, 0% packet loss, time 2000ms
-rtt min/avg/max/mdev = 0.141/0.164/0.192/0.021 ms
-</screen>
- Do not proceed to the next step if this step fails. It is imperative that the name of the PDC
- can be resolved to its IP address. If this is broken, fix it.
- </para></step>
-
- <step><para>
- Pull the domain SID from the NT4 domain that is being migrated as follows:
-<screen>
-&rootprompt; net rpc getsid -S TRANGRESSION -U Administrator%not24get
-Storing SID S-1-5-21-1385457007-882775198-1210191635 \
- for Domain DAMNATION in secrets.tdb
-</screen>
- </para>
-
- <para>
- Another way to obtain the domain SID from the target NT4 domain that is being
- migrated to Samba is by executing the following:
-<screen>
-&rootprompt; net rpc info -S TRANSGRESSION
-</screen>
- If this method is used, do not forget to store the SID obtained into the
- <filename>secrets.tdb</filename> file. This can be done by executing:
-<screen>
-&rootprompt; net setlocalsid S-1-5-21-1385457007-882775198-1210191635
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>Idealx</primary></indexterm>
- <indexterm><primary>configure.pl</primary></indexterm>
- <indexterm><primary>/opt/IDEALX/sbin</primary></indexterm>
- <indexterm><primary>smbldap-tools</primary></indexterm>
- Install the Idealx <command>smbldap-tools</command> software package, following
- the instructions given in <link linkend="sbeidealx"/>. The resulting perl scripts
- should be located in the <filename>/opt/IDEALX/sbin</filename> directory.
- Change into that location, or wherever the scripts have been installed. Execute the
- <filename>configure.pl</filename> script to configure the Idealx package for use.
- Note: Use the domain SID obtained from the step above. The following is
- an example configuration session:
-<screen>
-&rootprompt; ./configure.pl
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- smbldap-tools script configuration
- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Before starting, check
- . if your samba controller is up and running.
- . if the domain SID is defined
- (you can get it with the 'net getlocalsid')
-
- . you can leave the configuration using the Crtl-c key combination
- . empty value can be set with the "." character
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Looking for configuration files...
-
-Samba Config File Location [/etc/samba/smb.conf] >
-smbldap Config file Location (global parameters)
- [/etc/smbldap-tools/smbldap.conf] >
-smbldap Config file Location (bind parameters)
- [/etc/smbldap-tools/smbldap_bind.conf] >
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-Let's start configuring the smbldap-tools scripts ...
-
-. workgroup name: name of the domain Samba act as a PDC
- workgroup name [DAMNATION] >
-. netbios name: netbios name of the samba controller
- netbios name [MERLIN] >
-. logon drive: local path to which the home directory
- will be connected (for NT Workstations). Ex: 'H:'
- logon drive [X:] > H:
-. logon home: home directory location (for Win95/98 or NT Workstation)
- (use %U as username) Ex:'\\MERLIN\home\%U'
- logon home (leave blank if you don't want homeDirectory)
- [\\MERLIN\home\%U] > \\%L\%U
-. logon path: directory where roaming profiles are stored.
- Ex:'\\MERLIN\profiles\%U'
- logon path (leave blank if you don't want roaming profile)
- [\\MERLIN\profiles\%U] > \\%L\profiles\%U
-. home directory prefix (use %U as username) [/home/%U] >
- /home/users/%U
-. default user netlogon script (use %U as username)
- [%U.cmd] > scripts\logon.cmd
- default password validation time (time in days) [45] > 180
-. ldap suffix [dc=terpstra-world,dc=org] >
-. ldap group suffix [ou=Groups] >
-. ldap user suffix [ou=People] >
-. ldap machine suffix [ou=People] >
-. Idmap suffix [ou=Idmap] >
-. sambaUnixIdPooldn: object where you want to store the next uidNumber
- and gidNumber available for new users and groups
- sambaUnixIdPooldn object (relative to ${suffix})
- [sambaDomainName=DAMNATION] >
-. ldap master server:
- IP address or DNS name of the master (writable) ldap server
- ldap master server [] > 127.0.0.1
-. ldap master port [389] >
-. ldap master bind dn [cn=Manager,dc=terpstra-world,dc=org] >
-. ldap master bind password [] >
-. ldap slave server: IP address or DNS name of the slave ldap server:
- can also be the master one
- ldap slave server [] > 127.0.0.1
-. ldap slave port [389] >
-. ldap slave bind dn [cn=Manager,dc=terpstra-world,dc=org] >
-. ldap slave bind password [] >
-. ldap tls support (1/0) [0] >
-. SID for domain DAMNATION: SID of the domain
- (can be obtained with 'net getlocalsid MERLIN')
- SID for domain DAMNATION []
- > S-1-5-21-1385457007-882775198-1210191635
-. unix password encryption: encryption used for unix passwords
-unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA) [SSHA] > MD5
-. default user gidNumber [513] >
-. default computer gidNumber [515] >
-. default login shell [/bin/bash] >
-. default domain name to append to mail address [] >
- terpstra-world.org
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-backup old configuration files:
- /etc/smbldap-tools/smbldap.conf->
- /etc/smbldap-tools/smbldap.conf.old
- /etc/smbldap-tools/smbldap_bind.conf->
- /etc/smbldap-tools/smbldap_bind.conf.old
-writing new configuration file:
- /etc/smbldap-tools/smbldap.conf done.
- /etc/smbldap-tools/smbldap_bind.conf done.
-</screen>
- <indexterm><primary>sambaDomainName</primary></indexterm>
- <indexterm><primary>NextFreeUnixId</primary></indexterm>
- <indexterm><primary>updating smbldap-tools</primary></indexterm>
- <indexterm><primary>smbldap-tools updating</primary></indexterm>
- Note that the NT4 domain SID that was previously obtained was entered above. Also,
- the sambaUnixIdPooldn object was specified as sambaDomainName=DAMNATION. This is
- the location into which the Idealx smbldap-tools store the next available UID/GID
- information. It is also where Samba stores domain specific information such as the
- next RID, the SID, and so on. In older version of the smbldap-tools this information
- was stored in the sambaUnixIdPooldn DIT location cn=NextFreeUnixId. Where smbldap-tools
- are being upgraded to version 0.9.1 it is appropriate to update this to the new location
- only if the directory information is also relocated.
- </para></step>
-
- <step><para>
- Start the LDAP server using the system interface script. On Novell SLES9
- this is done as shown here:
-<screen>
-&rootprompt; rcldap start
-</screen>
- </para></step>
-
- <step><para>
- Edit the <filename>/etc/nsswitch.conf</filename> file so it has the entries shown in
- <link linkend="sbentnss2"/>. Note that the LDAP entries have now been uncommented.
- </para></step>
-
-<example id="sbentnss2">
-<title>NT4 Migration NSS Control File: <filename>/etc/nsswitch.conf</filename> (Stage:2)</title>
-<screen>
-passwd: files ldap
-shadow: files ldap
-group: files ldap
-
-hosts: files dns wins
-networks: files dns
-
-services: files
-protocols: files
-rpc: files
-ethers: files
-netmasks: files
-netgroup: files
-publickey: files
-
-bootparams: files
-automount: files nis
-aliases: files
-#passwd_compat: ldap #Not needed.
-#group_compat: ldap #Not needed.
-</screen>
-</example>
-
- <step><para>
- The LDAP management password must be installed into the <filename>secrets.tdb</filename>
- file as follows:
-<screen>
-&rootprompt; smbpasswd -w not24get
-Setting stored password for
- "cn=Manager,dc=terpstra-world,dc=org" in secrets.tdb
-</screen>
- </para></step>
-
- <step><para>
- Populate the LDAP directory as shown here:
-<screen>
-&rootprompt; /opt/IDEALX/sbin/smbldap-populate -a root -k 0 -m 0
-Using workgroup name from sambaUnixIdPooldn (smbldap.conf):
- sambaDomainName=DAMNATION
-Using builtin directory structure
-adding new entry: dc=terpstra-world,dc=org
-adding new entry: ou=People,dc=terpstra-world,dc=org
-adding new entry: ou=Groups,dc=terpstra-world,dc=org
-entry ou=People,dc=terpstra-world,dc=org already exist.
-adding new entry: ou=Idmap,dc=terpstra-world,dc=org
-adding new entry: sambaDomainName=DAMNATION,dc=terpstra-world,dc=org
-adding new entry: uid=root,ou=People,dc=terpstra-world,dc=org
-adding new entry: uid=nobody,ou=People,dc=terpstra-world,dc=org
-adding new entry: cn=Domain Admins,ou=Groups,dc=terpstra-world,dc=org
-adding new entry: cn=Domain Users,ou=Groups,dc=terpstra-world,dc=org
-adding new entry: cn=Domain Guests,ou=Groups,dc=terpstra-world,dc=org
-adding new entry: cn=Domain Computers,ou=Groups,dc=terpstra-world,dc=org
-adding new entry: cn=Administrators,ou=Groups,dc=terpstra-world,dc=org
-adding new entry: cn=Print Operators,ou=Groups,dc=terpstra-world,dc=org
-adding new entry: cn=Backup Operators,ou=Groups,dc=terpstra-world,dc=org
-adding new entry: cn=Replicators,ou=Groups,dc=terpstra-world,dc=org
-</screen>
- The script tries to add the ou=People container twice, hence the error message.
- This is expected behavior.
- </para></step>
-
- <step><para>
- <indexterm><primary>Novell SUSE SLES 9</primary></indexterm>
- Restart the LDAP server following initialization of the LDAP directory. Execute the
- system control script provided on your system. The following steps can be used on
- Novell SUSE SLES 9:
-<screen>
-&rootprompt; rcldap restart
-&rootprompt; chkconfig ldap on
-</screen>
- </para></step>
-
- <step><para>
- Verify that the new user accounts that have been added to the LDAP directory can be
- resolved as follows:
-<screen>
-&rootprompt; getent passwd
-...
-nobody:x:65534:65533:nobody:/var/lib/nobody:/bin/bash
-man:x:13:62:Manual pages viewer:/var/cache/man:/bin/bash
-news:x:9:13:News system:/etc/news:/bin/bash
-uucp:x:10:14:Unix-to-Unix CoPy system:/etc/uucp:/bin/bash
-+::0:0:::
-root:x:0:0:Netbios Domain Administrator:/home/users/root:/bin/false
-nobody:x:999:514:nobody:/dev/null:/bin/false
-</screen>
- Now repeat this for the group accounts as shown here:
-<screen>
-&rootprompt; getent group
-...
-nobody:x:65533:
-nogroup:x:65534:nobody
-users:x:100:
-+::0:
-Domain Admins:x:512:root
-Domain Users:x:513:
-Domain Guests:x:514:
-Domain Computers:x:515:
-Administrators:x:544:
-Print Operators:x:550:
-Backup Operators:x:551:
-Replicators:x:552:
-</screen>
- In both cases the LDAP accounts follow the <quote>+::0:</quote> entry.
- </para></step>
-
- <step><para>
- Now it is time to join the Samba BDC to the target NT4 domain that is being
- migrated to Samba by executing the following:
-<screen>
-&rootprompt; net rpc join -S TRANSGRESSION -U Administrator%not24get
-merlin:/opt/IDEALX/sbin # net rpc join -S TRANSGRESSION \
- -U Administrator%not24get
-Joined domain DAMNATION.
-</screen>
- </para></step>
-
- <step><para>
- Set the new domain administrator (root) password for both UNIX and Windows as shown here:
-<screen>
-&rootprompt; /opt/IDEALX/sbin/smbldap-passwd root
-Changing password for root
-New password : ********
-Retype new password : ********
-</screen>
- Note: During account migration, the Windows Administrator account will not be migrated
- to the Samba server.
- </para></step>
-
- <step><para>
- Now validate that these accounts can be resolved using Samba's tools as
- shown here for user accounts:
-<screen>
-&rootprompt; pdbedit -Lw
-root:0:84B0D8E14D158FF8417EAF50CFAC29C3:
- AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[U ]:LCT-425F6467:
-nobody:65534:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:
- NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:[NU ]:LCT-00000000:
-</screen>
- Now complete the following step to validate that group account mappings have
- been correctly set:
-<screen>
-&rootprompt; net groupmap list
-Domain Admins (S-1-5-21-1385457007-882775198-1210191635-512)
- -> Domain Admins
-Domain Users (S-1-5-21-1385457007-882775198-1210191635-513)
- -> Domain Users
-Domain Guests (S-1-5-21-1385457007-882775198-1210191635-514)
- -> Domain Guests
-Domain Computers (S-1-5-21-1385457007-882775198-1210191635-515)
- -> Domain Computers
-Administrators (S-1-5-32-544) -> Administrators
-Print Operators (S-1-5-32-550) -> Print Operators
-Backup Operators (S-1-5-32-551) -> Backup Operators
-Replicators (S-1-5-32-552) -> Replicators
-</screen>
- These are the expected results for a correctly configured system.
- </para></step>
-
- <step><para>
- Commence migration as shown here:
-<screen>
-&rootprompt; net rpc vampire -S TRANSGRESSION \
- -U Administrator%not24get > /tmp/vampire.log 2>1
-</screen>
- Check the vampire log to confirm that only expected errors have been
- reported. See <link linkend="sbevam1"/>.
- </para></step>
-
- <step><para>
- The migration of user accounts can be quickly validated as follows:
-<screen>
-&rootprompt; pdbedit -Lw
-root:0:84B0D8E14D158FF8417EAF50CFAC29C3:...
-nobody:65534:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:...
-Administrator:0:84B0D8E14D158FF8417EAF50CFAC29C3:...
-Guest:1:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:...
-TRANSGRESSION$:2:CC044B748CEE294CE76B6B0D1B86C1A8:...
-IUSR_TRANSGRESSION:3:64046AC81B056C375F9537FC409085F8:...
-MIDEARTH$:4:E93186E5819706D2AAD3B435B51404EE:...
-atrickhoffer:5:DC08CFE0C12B2867352502E32A407F23:...
-barryf:6:B829BCDE01FF24376E45D5F10408CFBD:...
-fsellerby:7:6A97CBEBE8F9826B417EAF50CFAC29C3:...
-gdaison:8:48F6A8C8A900024351DA8C2061C5F1D3:...
-hrambotham:9:7330D9EA0964465EAAD3B435B51404EE:...
-jrhapsody:10:ACBA7D207E2BA35D9BD41A26B01626BD:...
-maryk:11:293B5A4CA41F6CA1A7D80430B8342B73:...
-jacko:12:8E8982D86BD037C364BBD09A598E07AD:...
-bridge:13:0D2CA7D2BE67FE2193BE3A377C968336:...
-sharpec:14:8841A75CAC19D2855D8B73B1F4D430F8:...
-jimbo:15:6E8BDC904FD9EC5C17306D272A9441BB:...
-dhenwick:16:D1694A03C33584BDAAD3B435B51404EE:...
-dork:17:69E2D19E69A593D5AAD3B435B51404EE:...
-blue:18:E355EBF9559979FEAAD3B435B51404EE:...
-billw:19:EE35C3481CF7F7DB484448BC86A641A5:...
-rfreshmill:20:7EC033B58661B60CAAD3B435B51404EE:...
-MAGGOT$:21:A3B9334765AD30F7AAD3B435B51404EE:...
-TRENTWARE$:22:1D92C8DD5E7F0DDF93BE3A377C968336:...
-MORTON$:23:89342E69DCA9D3F8AAD3B435B51404EE:...
-NARM$:24:2B93E2D1D25448BDAAD3B435B51404EE:...
-LAPDOG$:25:14AA535885120943AAD3B435B51404EE:...
-SCAVENGER$:26:B6288EB6D147B56F8963805A19B0ED49:...
-merlin$:27:820C50523F368C54AB9D85AE603AD09D:...
-</screen>
- </para></step>
-
- <step><para>
- The mapping of UNIX and Windows groups can be validated as show here:
-<screen>
-&rootprompt; net groupmap list
-Domain Admins (S-1-5-21-1385457007-882775198-1210191635-512)
- -> Domain Admins
-Domain Users (S-1-5-21-1385457007-882775198-1210191635-513)
- -> Domain Users
-Domain Guests (S-1-5-21-1385457007-882775198-1210191635-514)
- -> Domain Guests
-Domain Computers (S-1-5-21-1385457007-882775198-1210191635-515)
- -> Domain Computers
-Administrators (S-1-5-32-544) -> Administrators
-Print Operators (S-1-5-32-550) -> Print Operators
-Backup Operators (S-1-5-32-551) -> Backup Operators
-Replicator (S-1-5-32-552) -> Replicators
-Engineers (S-1-5-21-1385457007-882775198-1210191635-1020) -> Engineers
-Marketoids (S-1-5-21-1385457007-882775198-1210191635-1022) -> Marketoids
-Gnomes (S-1-5-21-1385457007-882775198-1210191635-1023) -> Gnomes
-Catalyst (S-1-5-21-1385457007-882775198-1210191635-1024) -> Catalyst
-Recieving (S-1-5-21-1385457007-882775198-1210191635-1025) -> Recieving
-Rubberboot (S-1-5-21-1385457007-882775198-1210191635-1026) -> Rubberboot
-Sales (S-1-5-21-1385457007-882775198-1210191635-1027) -> Sales
-Accounting (S-1-5-21-1385457007-882775198-1210191635-1028) -> Accounting
-Shipping (S-1-5-21-1385457007-882775198-1210191635-1029) -> Shipping
-Account Operators (S-1-5-32-548) -> Account Operators
-Guests (S-1-5-32-546) -> Guests
-Server Operators (S-1-5-32-549) -> Server Operators
-Users (S-1-5-32-545) -> Users
-</screen>
- It is of vital importance that the domain SID portions of all group
- accounts are identical.
- </para></step>
-
- <step><para>
- The final responsibility in the migration process is to create identical
- shares and printing resources on the new Samba server, copy all data
- across, set up privileges, and set share and file/directory access controls.
- </para></step>
-
- <step><para>
- <indexterm><primary>domain master</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- Edit the &smb.conf; file to reset the parameter
- <smbconfoption name="domain master">Yes</smbconfoption> so that
- the Samba server functions as a PDC for the purpose of migration.
- Also, uncomment the deletion scripts so they will now be fully functional,
- enable the <parameter>wins support = yes</parameter> parameter and
- comment out the <parameter>wins server</parameter>. Validate the configuration
- with the <command>testparm</command> utility as shown here:
-<screen>
-&rootprompt; testparm
-Load smb config files from /etc/samba/smb.conf
-Processing section "[apps]"
-Processing section "[media]"
-Processing section "[homes]"
-Processing section "[printers]"
-Processing section "[netlogon]"
-Processing section "[profiles]"
-Processing section "[profdata]"
-Processing section "[print$]"
-Loaded services file OK.
-Server role: ROLE_DOMAIN_PDC
-Press enter to see a dump of your service definitions
-</screen>
- </para></step>
-
- <step><para>
- Now shut down the old NT4 PDC. Only when the old NT4 PDC and all
- NT4 BDCs have been shut down can the Samba PDC be started.
- </para></step>
-
- <step><para>
- All workstations should function as they did with the old NT4 PDC. All
- interdomain trust accounts should remain in place and fully functional.
- All machine accounts and user logon accounts should also function correctly.
- </para></step>
-
- <step><para>
- The configuration of Samba BDC servers can be accomplished now or at any
- convenient time in the future. Please refer to the carefully detailed process
- for doing so is outlined in <link linkend="sbehap-bldg1"/>.
- </para></step>
-
- </procedure>
-
- <sect3 id="sbevam1">
- <title>Migration Log Validation</title>
-
- <para>
- The following <filename>vampire.log</filename> file is typical of a valid migration.
-<screen>
-adding user Administrator to group Domain Admins
-adding user atrickhoffer to group Engineers
-adding user dhenwick to group Engineers
-adding user dork to group Engineers
-adding user rfreshmill to group Marketoids
-adding user jacko to group Gnomes
-adding user jimbo to group Gnomes
-adding user maryk to group Gnomes
-adding user gdaison to group Gnomes
-adding user dhenwick to group Catalyst
-adding user jacko to group Catalyst
-adding user jacko to group Recieving
-adding user blue to group Recieving
-adding user hrambotham to group Rubberboot
-adding user billw to group Sales
-adding user bridge to group Sales
-adding user jrhapsody to group Sales
-adding user maryk to group Sales
-adding user rfreshmill to group Sales
-adding user fsellerby to group Sales
-adding user sharpec to group Sales
-adding user jimbo to group Accounting
-adding user gdaison to group Accounting
-adding user jacko to group Shipping
-adding user blue to group Shipping
-Fetching DOMAIN database
-Creating unix group: 'Engineers'
-Creating unix group: 'Marketoids'
-Creating unix group: 'Gnomes'
-Creating unix group: 'Catalyst'
-Creating unix group: 'Recieving'
-Creating unix group: 'Rubberboot'
-Creating unix group: 'Sales'
-Creating unix group: 'Accounting'
-Creating unix group: 'Shipping'
-Creating account: Administrator
-Creating account: Guest
-Creating account: TRANSGRESSION$
-Creating account: IUSR_TRANSGRESSION
-Creating account: MIDEARTH$
-Creating account: atrickhoffer
-Creating account: barryf
-Creating account: fsellerby
-Creating account: gdaison
-Creating account: hrambotham
-Creating account: jrhapsody
-Creating account: maryk
-Creating account: jacko
-Creating account: bridge
-Creating account: sharpec
-Creating account: jimbo
-Creating account: dhenwick
-Creating account: dork
-Creating account: blue
-Creating account: billw
-Creating account: rfreshmill
-Creating account: MAGGOT$
-Creating account: TRENTWARE$
-Creating account: MORTON$
-Creating account: NARM$
-Creating account: LAPDOG$
-Creating account: SCAVENGER$
-Creating account: merlin$
-Group members of Domain Admins: Administrator,
-Group members of Domain Users: Administrator(primary),
-TRANSGRESSION$(primary),IUSR_TRANSGRESSION(primary),
-MIDEARTH$(primary),atrickhoffer(primary),barryf(primary),
-fsellerby(primary),gdaison(primary),hrambotham(primary),
-jrhapsody(primary),maryk(primary),jacko(primary),bridge(primary),
-sharpec(primary),jimbo(primary),dhenwick(primary),dork(primary),
-blue(primary),billw(primary),rfreshmill(primary),MAGGOT$(primary),
-TRENTWARE$(primary),MORTON$(primary),NARM$(primary),
-LAPDOG$(primary),SCAVENGER$(primary),merlin$(primary),
-Group members of Domain Guests: Guest(primary),
-Group members of Engineers: atrickhoffer,dhenwick,dork,
-Group members of Marketoids: rfreshmill,
-Group members of Gnomes: jacko,jimbo,maryk,gdaison,
-Group members of Catalyst: dhenwick,jacko,
-Group members of Recieving: jacko,blue,
-Group members of Rubberboot: hrambotham,
-Group members of Sales: billw,bridge,jrhapsody,maryk,
-rfreshmill,fsellerby,sharpec,
-Group members of Accounting: jimbo,gdaison,
-Group members of Shipping: jacko,blue,
-Fetching BUILTIN database
-skipping SAM_DOMAIN_INFO delta for 'Builtin' (is not my domain)
-Creating unix group: 'Account Operators'
-Creating unix group: 'Guests'
-Creating unix group: 'Server Operators'
-Creating unix group: 'Users'
-</screen>
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>NT4 Migration Using tdbsam Backend</title>
-
- <para>
- In this example, we change the domain name of the NT4 server from
- <constant>DRUGPREP</constant> to <constant>MEGANET</constant> prior to the use
- of the vampire (migration) tool. This migration process makes use of Linux system tools
- (like <command>useradd</command>) to add the accounts that are migrated into the
- UNIX/Linux <filename>/etc/passwd</filename> and <filename>/etc/group</filename>
- databases. These entries must therefore be present, and correct options specified,
- in your &smb.conf; file, or else the migration does not work as it should.
- </para>
-
- <procedure>
- <title>Migration Steps Using tdbsam</title>
-
- <step><para>
- Prepare a Samba server precisely per the instructions shown in <link linkend="Big500users"/>.
- Set the workgroup name to <constant>MEGANET</constant>.
- </para></step>
-
- <step><para><indexterm>
- <primary>domain master</primary>
- </indexterm><indexterm>
- <primary>BDC</primary>
- </indexterm>
- Edit the &smb.conf; file to temporarily change the parameter
- <smbconfoption name="domain master">No</smbconfoption> so
- the Samba server functions as a BDC for the purpose of migration.
- </para></step>
-
- <step><para>
- Start Samba as you have done previously.
- </para></step>
-
- <step><para><indexterm>
- <primary>net</primary>
- <secondary>rpc</secondary>
- <tertiary>join</tertiary>
- </indexterm>
- Join the NT4 Domain as a BDC, as shown here:
-<screen>
-&rootprompt; net rpc join -S oldnt4pdc -W MEGANET -UAdministrator%not24get
-Joined domain MEGANET.
-</screen>
- </para></step>
-
- <step><para><indexterm>
- <primary>net</primary>
- <secondary>rpc</secondary>
- <tertiary>vampire</tertiary>
- </indexterm>
- You may vampire the accounts from the NT4 PDC by executing the command, as shown here:
-<screen>
-&rootprompt; net rpc vampire -S oldnt4pdc -U Administrator%not24get
-Fetching DOMAIN database
-SAM_DELTA_DOMAIN_INFO not handled
-Creating unix group: 'Domain Admins'
-Creating unix group: 'Domain Users'
-Creating unix group: 'Domain Guests'
-Creating unix group: 'Engineers'
-Creating unix group: 'Marketoids'
-Creating unix group: 'Account Operators'
-Creating unix group: 'Administrators'
-Creating unix group: 'Backup Operators'
-Creating unix group: 'Guests'
-Creating unix group: 'Print Operators'
-Creating unix group: 'Replicator'
-Creating unix group: 'Server Operators'
-Creating unix group: 'Users'
-Creating account: Administrator
-Creating account: Guest
-Creating account: oldnt4pdc$
-Creating account: jacko
-Creating account: maryk
-Creating account: bridge
-Creating account: sharpec
-Creating account: jimbo
-Creating account: dhenwick
-Creating account: dork
-Creating account: blue
-Creating account: billw
-Creating account: massive$
-Group members of Engineers: Administrator,
- sharpec(primary),bridge,billw(primary),dhenwick
-Group members of Marketoids: Administrator,jacko(primary),
- maryk(primary),jimbo,blue(primary),dork(primary)
-Creating unix group: 'Gnomes'
-Fetching BUILTIN database
-SAM_DELTA_DOMAIN_INFO not handled
-</screen>
- </para></step>
-
- <step><para><indexterm>
- <primary>pdbedit</primary>
- </indexterm>
- At this point, we can validate our migration. Let's look at the accounts
- in the form in which they are seen in a smbpasswd file. This achieves that:
-<screen>
-&rootprompt; pdbedit -Lw
-Administrator:505:84B0D8E14D158FF8417EAF50CFAC29C3:
- AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[UX ]:LCT-3DF7AA9F:
-jimbo:512:6E9A2A51F64A1BD5C187B8085FE1D9DF:
- CDF7E305E639966E489A0CEFB95EE5E0:[UX ]:LCT-3E9362BC:
-sharpec:511:E4301A7CD8FDD1EC6BBF9BC19CDF8151:
- 7000255938831D5B948C95C1931534C5:[UX ]:LCT-3E8B42C4:
-dhenwick:513:DCD8886141E3F892AAD3B435B51404EE:
- 2DB36465949CB938DD98C312EFDC2639:[UX ]:LCT-3E939F41:
-bridge:510:3FE6873A43101B46417EAF50CFAC29C3:
- 891741F481AF111B4CAA09A94016BD01:[UX ]:LCT-3E8B4291:
-blue:515:256D41D2559BB3D2AAD3B435B51404EE:
- 9CCADDA4F7D281DD0FAD321478C6F971:[UX ]:LCT-3E939FDC:
-diamond$:517:6C8E7B64EDCDBC4218B6345447A4454B:
- 3323AC63C666CFAACB60C13F65D54E9A:[S ]:LCT-00000000:
-oldnt4pdc$:507:3E39430CDCABB5B09ED320D0448AE568:
- 95DBAF885854A919C7C7E671060478B9:[S ]:LCT-3DF7AA9F:
-Guest:506:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[DUX ]:LCT-3E93A008:
-billw:516:85380CA7C21B6EBE168C8150662AF11B:
- 5D7478508293709937E55FB5FBA14C17:[UX ]:LCT-3FED7CA1:
-dork:514:78C70DDEC35A35B5AAD3B435B51404EE:
- 0AD886E015AC595EC0AF40E6C9689E1A:[UX ]:LCT-3E939F9A:
-jacko:508:BC472F3BF9A0A5F63832C92FC614B7D1:
- 0C6822AAF85E86600A40DC73E40D06D5:[UX ]:LCT-3E8B4242:
-maryk:509:3636AB7E12EBE79AB79AE2610DD89D4C:
- CF271B744F7A55AFDA277FF88D80C527:[UX ]:LCT-3E8B4270:
-</screen>
- </para></step>
-
- <step><para><indexterm>
- <primary>pdbedit</primary>
- </indexterm>
- An expanded view of a user account entry shows more of what was
- obtained from the NT4 PDC:
-<screen>
-sleeth:~ # pdbedit -Lv maryk
-Unix username: maryk
-NT username: maryk
-Account Flags: [UX ]
-User SID: S-1-5-21-1988699175-926296742-1295600288-1003
-Primary Group SID: S-1-5-21-1988699175-926296742-1295600288-1007
-Full Name: Mary Kathleen
-Home Directory: \\diamond\maryk
-HomeDir Drive: X:
-Logon Script: scripts\logon.bat
-Profile Path: \\diamond\profiles\maryk
-Domain: MEGANET
-Account desc: Peace Maker
-Workstations:
-Munged dial:
-Logon time: 0
-Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Password last set: Wed, 02 Apr 2003 13:05:04 GMT
-Password can change: 0
-Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-</screen>
- </para></step>
-
- <step><para><indexterm>
- <primary>net</primary>
- <secondary>group</secondary>
- </indexterm>
- The following command lists the long names of the groups that have been
- imported (vampired) from the NT4 PDC:
-<screen>
-&rootprompt; net group -l -Uroot%not24get -Smassive
-
-Group name Comment
------------------------------
-Engineers Snake Oil Engineers
-Marketoids Untrustworthy Hype Vendors
-Gnomes Plain Vanilla Garden Gnomes
-Replicator Supports file replication in a domain
-Guests Users granted guest access to the computer/domain
-Administrators Members can fully administer the computer/domain
-Users Ordinary users
-</screen>
- Everything looks well and in order.
- </para></step>
-
- <step><para><indexterm>
- <primary>domain master</primary>
- </indexterm><indexterm>
- <primary>PDC</primary>
- </indexterm>
- Edit the &smb.conf; file to reset the parameter
- <smbconfoption name="domain master">Yes</smbconfoption> so
- the Samba server functions as a PDC for the purpose of migration.
- </para></step>
- </procedure>
- </sect2>
-
- <sect2>
- <title>Key Points Learned</title>
-
- <para>
- Migration of an NT4 PDC database to a Samba PDC is possible.
- </para>
-
- <itemizedlist>
- <listitem><para>
- An LDAP backend is a suitable vehicle for NT4 migrations.
- </para></listitem>
-
- <listitem><para>
- A tdbsam backend can be used to perform a migration.
- </para></listitem>
-
- <listitem><para>
- Multiple NT4 domains can be merged into a single Samba
- domain.
- </para></listitem>
-
- <listitem><para>
- The net Samba domain most likely requires some
- administration and updating before going live.
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- </para>
-
- <qandaset defaultlabel="chap08qa" type="number">
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>clean database</primary>
- </indexterm>
- Why must I start each migration with a clean database?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>merge</primary>
- </indexterm>
- This is a recommendation that permits the data from each NT4 domain to
- be kept separate until you are ready to merge them. Also, if you do not start with a clean database,
- you may find errors due to users or groups from multiple domains having the
- same name but different SIDs. It is better to permit each migration to complete
- without undue errors and then to handle the merging of vampired data under
- proper supervision.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>Domain SID</primary>
- </indexterm>
- Is it possible to set my domain SID to anything I like?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>auto-generated SID</primary>
- </indexterm><indexterm>
- <primary>SID</primary>
- </indexterm><indexterm>
- <primary>Domain SID</primary>
- </indexterm>
- Yes, so long as the SID you create has the same structure as an autogenerated SID.
- The typical SID looks like this: S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX, where
- the XXXXXXXXXX can be any number with from 6 to 10 digits. On the other hand, why
- would you really want to create your own SID? I cannot think of a good reason.
- You may want to set the SID to one that is already in use somewhere on your network,
- but that is a little different from straight out creating your own domain SID.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>/etc/passwd</primary>
- </indexterm><indexterm>
- <primary>/etc/group</primary>
- </indexterm><indexterm>
- <primary>tdbsam</primary>
- </indexterm><indexterm>
- <primary>passdb backend</primary>
- </indexterm><indexterm>
- <primary>accounts</primary>
- <secondary>user</secondary>
- </indexterm><indexterm>
- <primary>accounts</primary>
- <secondary>group</secondary>
- </indexterm><indexterm>
- <primary>accounts</primary>
- <secondary>Domain</secondary>
- </indexterm>
- When using a tdbsam passdb backend, why must I have all domain user and group accounts
- in <filename>/etc/passwd</filename> and <filename>/etc/group</filename>?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>UID</primary>
- </indexterm><indexterm>
- <primary>GID</primary>
- </indexterm><indexterm>
- <primary>smbpasswd</primary>
- </indexterm><indexterm>
- <primary>/etc/passwd</primary>
- </indexterm><indexterm>
- <primary>Posix</primary>
- </indexterm><indexterm>
- <primary>LDAP database</primary>
- </indexterm>
- Samba must be able to tie all user and group account SIDs to a UNIX UID or GID. Samba
- does not fabricate the UNIX IDs from thin air, but rather requires them to be located
- in a suitable place.
- </para>
-
- <para>
- When migrating a <filename>smbpasswd</filename> file to an LDAP backend, the
- UID of each account is taken together with the account information in the
- <filename>/etc/passwd</filename>, and both sets of data are used to create the account
- entry in the LDAP database.
- </para>
-
- <para>
- If you elect to create the POSIX account also, the entire UNIX account is copied to the
- LDAP backend. The same occurs with NT groups and UNIX groups. At the conclusion of
- migration to the LDAP database, the accounts may be removed from the UNIX database files.
- In short then, all UNIX and Windows networking accounts, both in tdbsam as well as in
- LDAP, require UIDs/GIDs.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>validate</primary>
- </indexterm><indexterm>
- <primary>connectivity</primary>
- </indexterm><indexterm>
- <primary>migration</primary>
- </indexterm>
- Why did you validate connectivity before attempting migration?
- </para>
-
- </question>
- <answer>
-
- <para>
- Access validation before attempting to migrate NT4 domain accounts helps to pinpoint
- potential problems that may otherwise affect or impede account migration. I am always
- mindful of the 4 P's of migration: Planning Prevents Poor Performance.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- How would you merge 10 tdbsam-based domains into an LDAP database?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>risk</primary>
- </indexterm><indexterm>
- <primary>dump</primary>
- </indexterm><indexterm>
- <primary>tdbsam</primary>
- </indexterm><indexterm>
- <primary>Samba Domain</primary>
- </indexterm><indexterm>
- <primary>UID</primary>
- </indexterm><indexterm>
- <primary>GID</primary>
- </indexterm><indexterm>
- <primary>pdbedit</primary>
- </indexterm><indexterm>
- <primary>transfer</primary>
- </indexterm><indexterm>
- <primary>smbpasswd</primary>
- </indexterm><indexterm>
- <primary>LDAP</primary>
- </indexterm><indexterm>
- <primary>tool</primary>
- </indexterm>
- If you have 10 tdbsam Samba domains, there is considerable risk that there are a number of
- accounts that have the same UNIX identifier (UID/GID). This means that you almost
- certainly have to edit a lot of data. It would be easiest to dump each database in smbpasswd
- file format and then manually edit all records to ensure that each has a unique UID. Each
- file can then be imported a number of ways. You can use the <command>pdbedit</command> tool
- to affect a transfer from the smbpasswd file to LDAP, or you can migrate them en masse to
- tdbsam and then to LDAP. The final choice is yours. Just remember to verify all accounts that
- you have migrated before handing over access to a user. After all, too many users with a bad
- migration experience may threaten your career.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>machine accounts</primary>
- </indexterm><indexterm>
- <primary>accounts</primary>
- <secondary>machine</secondary>
- </indexterm>
- I want to change my domain name after I migrate all accounts from an NT4 domain to a
- Samba domain. Does it make any sense to migrate the machine accounts in that case?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>registry</primary>
- </indexterm><indexterm>
- <primary>un-join</primary>
- </indexterm><indexterm>
- <primary>rejoin</primary>
- </indexterm><indexterm>
- <primary>tattooing</primary>
- </indexterm>
- I would recommend not to migrate the machine account. The machine accounts should still work, but there are registry entries
- on each Windows NT4 and upward client that have a tattoo of the old domain name. If you
- unjoin the domain and then rejoin the newly renamed Samba domain, you can be certain to avoid
- this tattooing effect.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>multiple group mappings</primary>
- </indexterm>
- After merging multiple NT4 domains into a Samba domain, I lost all multiple group mappings. Why?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>/etc/passwd</primary>
- </indexterm><indexterm>
- <primary>/etc/group</primary>
- </indexterm>
- Samba currently does not implement multiple group membership internally. If you use the Windows
- NT4 Domain User Manager to manage accounts and you have an LDAP backend, the multiple group
- membership is stored in the POSIX groups area. If you use either tdbsam or smbpasswd backend,
- then multiple group membership is handled through the UNIX groups file. When you dump the user
- accounts, no group account information is provided. When you edit (change) UIDs and GIDs in each
- file to which you migrated the NT4 Domain data, do not forget to edit the UNIX <filename>/etc/passwd</filename>
- and <filename>/etc/group</filename> information also. That is where the multiple group information
- is most closely at your fingertips.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- How can I reset group membership after loading the account information into the LDAP database?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>SRVTOOLS.EXE</primary>
- </indexterm>
- You can use the NT4 Domain User Manager that can be downloaded from the Microsoft Web site. The
- installation file is called <filename>SRVTOOLS.EXE</filename>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>group names</primary>
- </indexterm>
- What are the limits or constraints that apply to group names?
- </para>
-
- </question>
- <answer>
-
- <para><indexterm>
- <primary>limit</primary>
- </indexterm><indexterm>
- <primary>shadow-utils</primary>
- </indexterm><indexterm>
- <primary>groupadd</primary>
- </indexterm><indexterm>
- <primary>groupdel</primary>
- </indexterm><indexterm>
- <primary>groupmod</primary>
- </indexterm><indexterm>
- <primary>account names</primary>
- </indexterm>
- A Windows 200x group name can be up to 254 characters long, while in Windows NT4 the group
- name is limited to 20 characters. Most UNIX systems limit this to 32 characters. Windows
- groups can contain upper- and lowercase characters, as well as spaces.
- Many UNIX system do not permit the use of uppercase characters, and some do not permit the
- space character either. A number of systems (i.e., Linux) work fine with both uppercase
- and space characters in group names, but the shadow-utils package that provides the group
- control functions (<command>groupadd</command>, <command>groupmod</command>, <command>groupdel</command>, and so on) do not permit them.
- Also, a number of UNIX systems management tools enforce their own particular interpretation
- of the POSIX standards and likewise do not permit uppercase or space characters in group
- or user account names. You have to experiment with your system to find what its
- peculiarities are.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para><indexterm>
- <primary>vampire</primary>
- </indexterm>
- My Windows NT4 PDC has 323,000 user accounts. How long will it take to migrate them to a Samba
- LDAP backend system using the vampire process?
- </para>
-
- </question>
- <answer>
-
- <para>
- UNIX UIDs and GIDs on most UNIX systems use an unsigned short or an unsigned integer. Recent Linux
- kernels support at least a much larger number. On systems that have a 16-bit constraint on UID/GIDs,
- you would not be able to migrate 323,000 accounts because this number cannot fit into a 16-bit unsigned
- integer. UNIX/Linux systems that have a 32-bit UID/GID can easily handle this number of accounts.
- Please check this carefully before you attempt to effect a migration using the vampire process.
- </para>
-
- <para><indexterm>
- <primary>Migration speed</primary>
- </indexterm>
- Migration speed depends much on the processor speed, the network speed, disk I/O capability, and
- LDAP update overheads. On a dual processor AMD MP1600+ with 1 GB memory that was mirroring LDAP
- to a second identical system over 1 Gb Ethernet, I was able to migrate around 180 user accounts
- per minute. Migration would obviously go much faster if LDAP mirroring were turned off during the migration.
- </para>
-
- </answer>
- </qandaentry>
-
- </qandaset>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="nw4migration">
- <title>Migrating NetWare Server to Samba</title>
-
- <para>
- <indexterm><primary>Novell</primary></indexterm>
- <indexterm><primary>SUSE</primary></indexterm>
- Novell is a company any seasoned IT manager has to admire. It has become increasingly
- Linux-friendly and is emerging out of a deep regression that almost saw the company
- disappear into obscurity. Novell's SUSE Linux hosts the NetWare server and it is the
- platform of choice to which many older NetWare servers are being migrated.
- It will be interesting to see what becomes of NetWare over time.
- Meanwhile, there can be no denying that Novell is a Linux company.
- </para>
-
- <para>
- <indexterm><primary>Red Hat</primary></indexterm>
- <indexterm><primary>Debian</primary></indexterm>
- <indexterm><primary>Gentoo</primary></indexterm>
- <indexterm><primary>Mandrake</primary></indexterm>
- Whatever flavor of Linux is preferred in your environment, whether Red Hat, Debian,
- Gentoo, Mandrake, or SUSE (Novell), the information in this chapter should be read with
- the knowledge that file locations may vary a little; even so, the information
- in this chapter should provide something of value.
- </para>
-
- <para>
- <indexterm><primary>migration</primary></indexterm>
- Contributions to this chapter were made by Misty Stanley-Jones, a UNIX administrator of many
- years who surfaced on the Samba mailing list with a barrage of questions and who
- regularly helps other administrators to solve thorny Samba migration questions.
- </para>
-
- <para>
- <indexterm><primary>NetWare</primary></indexterm>
- <indexterm><primary>NLM</primary></indexterm>
- <indexterm><primary>NetWare</primary></indexterm>
- <indexterm><primary>Mars_NWE</primary></indexterm>
- One wonders how many NetWare servers remain in active service. Many are being migrated
- to Samba on Linux. Red Hat Linux, SUSE Linux 9.x, and SUSE Linux Enterprise Server 9 are
- ideal target platforms to which a NetWare server may be migrated. The migration method
- of choice is much dependent on the tools that the administrator finds most natural to use.
- The old-hand NetWare guru will likely want to use tools like the NetWare NLM for
- <command>rsync</command> to migrate files from the NetWare server to the Samba server.
- The UNIX administrator might prefer tools that are part of the Mars_NWE (Martin Stovers' NetWare
- Emulator) open source package. The MS Windows network administrator will likely make use of the
- NWConv utility that is a part of Windows NT4 Server. Whatever your tool of choice,
- migration will be filled with joyous and challenging moments &smbmdash; though probably not
- concurrently.
- </para>
-
- <para>
- The priority that Misty faced was one of migration of the data files off the NetWare 4.11
- server and onto a Samba-based Windows file and print server. This chapter does not pretend
- to document all the different methods that could be used to migrate user and group accounts
- off a NetWare server. Its focus is on migration of data files.
- </para>
-
- <para>
- This chapter tells its own story, so ride along. Maybe the information presented here
- will help to smooth over a similar migration challenge in your favorite networking environment.
- </para>
-
- <para>
- File paths have been modified to permit use of RPM packages provided by Novell. In the
- original documentation contributed by Misty, the Courier-IMAP package had been built
- directly from the original source tarball.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- <indexterm><primary>Novell</primary></indexterm>
- Misty Stanley-Jones was recruited by Abmas to administer a network that had
- not received much attention for some years and was much in need of a makeover.
- As a brand-new sysadmin to this company, she inherited a very old Novell file server
- and came with a determination to change things for the better.
- </para>
-
- <para>
- A site survey turned up the following details for the old NetWare server:
- </para>
-
- <simplelist>
- <member>200 MHz MMX processor</member>
- <member>512K RAM</member>
- <member>24 GB disk space in RAID1</member>
- <member>Novell 4.11 patched to service pack 7</member>
- <member>60+ users</member>
- <member>7 network-attached printers</member>
- </simplelist>
-
- <para>
- The company had outgrown this server several years before and was dealing with
- severe growing pains. Some of the problems experienced were:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>Very slow performance</para>
- </listitem>
- <listitem>
- <para>Available storage hovering around the 5% range</para>
- <itemizedlist>
- <listitem>
- <para>Extremely slow print spooling.</para>
- </listitem>
- <listitem>
- <para>
- Users storing information on their local hard
- drives, causing backup integrity problems
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>payroll</primary></indexterm>
- At one point disk space had filled up to 100 percent, causing the payroll database
- to become corrupt. This caused the accounting department to be down for over
- a week and necessitated deployment of another file server. The replacement
- server was created with very poor security and design considerations from
- a discarded desktop PC.
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- Misty has provided this summary of her migration experience in the hope
- that it will help someone to avoid the challenges she faced. Perhaps her
- configuration files and background will accelerate your learning as you
- grapple with a similar migration challenge. Let there be no confusion,
- the information presented in this chapter is provided to demonstrate
- how Misty dealt with a particular NetWare migration requirement, and
- it provides an overall approach to the implementation of a Samba
- environment that is significantly divergent from that presented in
- <link linkend="happy"/>.
- </para>
-
- <para>
- The complete removal of all site-specific information in order to produce
- a generic migration solution would rob this chapter of its character.
- It should be recognized, therefore, that the examples given require
- significant adaptation to suit local needs and thus
- there are some gaps in the example files. That is not Misty's fault;it
- is the result of treatment given to her files in an attempt to make
- the overall information more useful to you.
- </para>
-
- <para>
- <indexterm><primary>cost-benefit</primary></indexterm>
- After management reviewed a cost-benefit report as well as an estimated
- time-to-completion, approval was given proceed with the solution proposed.
- The server was built from purchased components. The total project cost
- was $3,000. A brief description of the configuration follows:
- </para>
-
- <simplelist>
- <member>
- 3.0 GHz P4 Processor
- </member>
- <member>
- 1 GB RAM
- </member>
- <member>
- 120 GB SATA operating system drive
- </member>
- <member>
- 4 x 80 GB SATA data drives (RAID5 240 GB capacity)
- </member>
- <member>
- 2 x 80 GB SATA removable drives for online backup
- </member>
- <member>
- A DLT drive for asynchronous offline backup
- </member>
- <member>
- SUSE Linux Professional 9.1
- </member>
- </simplelist>
-
- <para>
- The new system has operated for 6 months without problems. Over the past months
- much attention has been focused on cleaning up desktops and user profiles.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>e-Directory</primary></indexterm>
- <indexterm><primary>authentication</primary></indexterm>
- <indexterm><primary>identity management</primary></indexterm>
- A decision to use LDAP was made even though I knew nothing about LDAP except that
- I had been reading the book <quote>LDAP System Administration,</quote> by Gerald Carter.
- LDAP seemed to provide some of the functionality of Novell's e-Directory Services
- and would provide centralized authentication and identity management.
- </para>
-
- <para>
- <indexterm><primary>database</primary></indexterm>
- <indexterm><primary>RPM</primary></indexterm>
- <indexterm><primary>tree</primary></indexterm>
- Building the LDAP database took a while and a lot of trial and error. Following
- the guidance I obtained from <quote>LDAP System
- Administration,</quote> I installed OpenLDAP (from RPM; later I compiled
- a more current version from source) and built my initial LDAP tree.
- </para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- <indexterm><primary>white-pages</primary></indexterm>
- <indexterm><primary>inetOrgPerson</primary></indexterm>
- <indexterm><primary>OpenLDAP</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>/etc/shadow</primary></indexterm>
- <indexterm><primary>LDIF</primary></indexterm>
- <indexterm><primary>IMAP</primary></indexterm>
- <indexterm><primary>POP3</primary></indexterm>
- <indexterm><primary>SMTP</primary></indexterm>
- The first challenge was to create a company white pages, followed by manually
- entering everything from the printed company directory. This used only the inetOrgPerson
- object class from the OpenLDAP schemas. The next step was to write a shell script that
- would look at the <filename>/etc/passwd</filename> and <filename>/etc/shadow</filename>
- files on our mail server and create an LDIF file from which the information could be
- imported into LDAP. This would allow use of LDAP for Linux authentication, IMAP, POP3,
- and SMTP.
- </para>
-
- <para>
- Because a decision was made to use Courier-IMAP the schema <quote>authldap.schema</quote>
- from the Courier-IMAP source, tarball is necessary to resolve Courier-specific LDAP directory
- needs. Where the Courier-IMAP file provided by SUSE is used, this file is named
- <filename>courier.schema</filename>.
- </para>
-
- <para>
- Looking back, it would have been much easier to populate the LDAP directory using a convenient
- tool such as <command>phpLDAPAdmin</command> from the outset. An excessive amount of time was
- spent trying to generate LDIF files that could be parsed using the <command>ldapmodify</command>
- so that necessary changes could be written to the directory. This was a learning experience!
- </para>
-
- <para>
- An attempt was made to use the PADL POSIX account migration scripts, but I gave up trying to
- make them work. Instead, even though it is most inelegant, I wrote a simple script that did
- what I needed. It is enclosed as a simple example to demonstrate that you do not need to be
- a guru to make light of otherwise painful repetition. This file is listed in <link linkend="sbeamg"/>.
- </para>
-
-<example id="sbeamg">
-<title>A Rough Tool to Create an LDIF File from the System Account Files</title>
-<screen>
-#!/bin/bash
-
-cat /etc/passwd | while read l; do
- uid=`echo $l | cut -d : -f 1`
- uidNumber=`echo $l | cut -d : -f 3`
- gidNumber=`echo $1 | cut -d : -f 4`
- gecos=`echo $l | cut -d : -f 5`
- homeDirectory=`echo $l | cut -d : -f 6`
- loginShell=`echo $l | cut -d : -f 6`
- userPassword=`cat /etc/shadow | grep $uid | cut -d : -f 2`
-
- echo "dn: cn=$gecos,ou=people,dc=mycompany,dc=com"
- echo "objectClass: account"
- echo "objectClass: posixAccount"
- echo "cn: $gecos"
- echo "uid: $uid"
- echo "uidNumber: $uidNumber"
- echo "gidNumber: $gidNumber"
- echo "homeDirectory: $homeDirectory"
- echo "loginShell: $loginShell"
- echo "userPassword: $userPassword"
-done
-</screen>
-</example>
-
- <note><para>
-
- The PADL MigrationTools are recommended for migration of the UNIX account information into
- the LDAP directory. The tools consist of a set of Perl scripts for migration of users, groups,
- aliases, hosts, netgroups, networks, protocols, PRCs, and services from the existing ASCII text
- files (or from a name service such as NIS). This too set can be obtained from the <ulink url=
- "http://www.padl.com">PADL Web site</ulink>.
- </para></note>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- </para>
-
- <sect2>
- <title>NetWare Migration Using LDAP Backend</title>
-
- <para>
- The following software must be installed on the SUSE Linux Enterprise Server to perform
- this migration:
- </para>
-
- <simplelist>
- <member>courier-imap</member>
- <member>courier-imap-ldap</member>
- <member>nss_ldap</member>
- <member>openldap2-client</member>
- <member>openldap2-devel (only for Samba compilation)</member>
- <member>openldap2</member>
- <member>pam_ldap</member>
- <member>samba-3.0.20 or later</member>
- <member>samba-client-3.0.20 or later</member>
- <member>samba-winbind-3.0.20 or later</member>
- <member>smbldap-tools Version 0.9.1</member>
- </simplelist>
-
- <para>
- Each software application must be carefully configured in preparation for migration.
- The configuration files used at Abmas are provided as a guide and should be modified
- to meet needs at your site.
- </para>
-
- <sect3>
- <title>LDAP Server Configuration</title>
-
- <para>
- The <filename>/etc/openldap/slapd.conf</filename> file Misty used is shown here:
-<programlisting>
-#/etc/openldap/slapd.conf
-#
-# See slapd.conf(5) for details on configuration options.
-# This file should NOT be world readable.
-#
-include /etc/openldap/schema/core.schema
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/nis.schema
-include /etc/openldap/schema/samba3.schema
-include /etc/openldap/schema/dhcp.schema
-include /etc/openldap/schema/misc.schema
-include /etc/openldap/schema/idpool.schema
-include /etc/openldap/schema/eduperson.schema
-include /etc/openldap/schema/commURI.schema
-include /etc/openldap/schema/local.schema
-include /etc/openldap/schema/courier.schema
-
-pidfile /var/run/slapd/run/slapd.pid
-argsfile /var/run/slapd/run/slapd.args
-
-replogfile /data/ldap/log/slapd.replog
-
-# Load dynamic backend modules:
-modulepath /usr/lib/openldap/modules
-
-#######################################################################
-# Logging parameters
-#######################################################################
-loglevel 256
-
-#######################################################################
-# SASL and TLS options
-#######################################################################
-sasl-host ldap.corp.abmas.org
-sasl-realm DIGEST-MD5
-sasl-secprops none
-TLSCipherSuite HIGH:MEDIUM:+SSLV2
-TLSCertificateFile /etc/ssl/certs/private/abmas-cert.pem
-TLSCertificateKeyFile /etc/ssl/certs/private/abmas-key.pem
-password-hash {SSHA}
-defaultsearchbase "dc=abmas,dc=biz"
-
-#######################################################################
-# bdb database definitions
-#######################################################################
-database bdb
-suffix "dc=abmas,dc=biz"
-rootdn "cn=manager,dc=abmas,dc=biz"
-rootpw {SSHA}gdo/dUvoT4ZJmULz3rUt6A3H/hBEduJ5
-directory /data/ldap
-mode 0600
-# The following is for BDB to make it flush its data to disk every
-# 500 seconds or 5kb of data
-checkpoint 500 5
-
-## For running slapindex
-#readonly on
-
-## Indexes for often-requested attributes
-index objectClass eq
-index cn eq,sub
-index sn eq,sub
-index uid eq,sub
-index uidNumber eq
-index gidNumber eq
-index sambaSID eq
-index sambaPrimaryGroupSID eq
-index sambaDomainName eq
-index default sub
-cachesize 2000
-
-replica host=baa.corp.abmas.org:389
- suffix="dc=abmas,dc=biz"
- binddn="cn=replica,dc=abmas,dc=biz"
- credentials=verysecret
- bindmethod=simple
- tls=yes
-replica host=ns.abmas.org:389
- suffix="dc=abmas,dc=biz"
- binddn="cn=replica,dc=abmas,dc=biz"
- credentials=verysecret
- bindmethod=simple
- tls=yes
-
-#######################################################################
-# ACL section
-#######################################################################
-## MOST RESTRICTIVE RULES MUST GO FIRST!
-# Admins get access to everything. This way I do not have to rename.
-access to *
- by group/groupOfUniqueNames/uniqueMember="cn=LDAP
-Administrators,ou=groups,dc=abmas,dc=biz" write
- by * break
-
-## Users can change their own passwords.
-access to
-attrs=userPassword,sambaNTPassword,sambaLMPassword,sambaPwdLastSet,
-sambaPwdMustChange,sambaPwdCanChange
- by self write
- by * auth
-
-## Home contact info restricted to the logged-in user and the HR dept
-access to attrs=hometelephoneNumber,homePostalAddress,
-mobileTelephoneNumber,pagerTelephoneNumber
- by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
-ou=groups,dc=abmas,dc=biz"
-write
- by self write
- by * none
-
-## Everyone can read email aliases
-access to dn.sub="ou=Email Aliases,dc=abmas,dc=biz"
- by * read
-
-## Only admins can manage email aliases
-## If someone is the role occupant of an alias they can change it -- this
-## is accomplished by the "organizationalRole" objectclass and is
-## pretty cool -- like a groupOfUniqueNames but for individual
-## users.
-access to dn.children="ou=Email Aliases,dc=abmas,dc=biz"
- by dnattr=roleOccupant write
- by * read
-
-## Admins and HR can add and delete users
-access to dn.sub="ou=people,dc=abmas,dc=biz"
- by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
-ou=groups,dc=abmas,dc=biz"
-write
- by * read
-
-## Admins and HR can add and delete bizputers
-access to dn.sub="ou=bizputers,dc=abmas,dc=biz"
- by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
-ou=groups,dc=abmas,dc=biz"
-write
- by * read
-
-## Admins and HR can add and delete groups
-access to dn.sub="ou=groups,dc=abmas,dc=biz"
- by group/groupOfUniqueNames/uniqueMember="cn=hr_admin,
-ou=groups,dc=abmas,dc=biz"
-write
- by * read
-
-## This is used to quickly deactivate any LDAP object only
-## Admins have access.
-access to dn.sub="ou=inactive,dc=abmas,dc=biz"
- by * none
-
-## This is for programs like Windows Address Book that can
-## detect the default search base.
-access to attrs=namingcontexts,supportedControl
- by anonymous =cs
- by * read
-
-## Default to read-only access
-access to *
- by dn.base="cn=replica,ou=people,dc=abmas,dc=biz" write
- by * read
-</programlisting>
-</para>
-
- <para>
- <indexterm><primary>/etc/ldap.conf</primary></indexterm>
- The <filename>/etc/ldap.conf</filename> file used is listed in <link linkend="ch8ldap"/>.
- </para>
-
-<example id="ch8ldap">
-<title>NSS LDAP Control File &smbmdash; /etc/ldap.conf</title>
-<screen>
-# /etc/ldap.conf
-# This file is present on every *NIX client that authenticates to LDAP.
-# For me, most of the defaults are fine. There is an amazing amount of
-# customization that can be done see the man page for info.
-
-# Your LDAP server. Must be resolvable without using LDAP. The following
-# is for the LDAP server all others use the FQDN of the server
-URI ldap://127.0.0.1
-
-# The distinguished name of the search base.
-base ou=corp,dc=abmas,dc=biz
-
-# The LDAP version to use (defaults to 3 if supported by client library)
-ldap_version 3
-
-# The distinguished name to bind to the server with if the effective
-# user ID is root. Password is stored in /etc/ldap.secret (mode 600)
-rootbinddn cn=Manager,dc=abmas,dc=biz
-
-# Filter to AND with uid=%s
-pam_filter objectclass=posixAccount
-
-# The user ID attribute (defaults to uid)
-pam_login_attribute uid
-
-# Group member attribute
-pam_member_attribute memberUID
-
-# Use the OpenLDAP password change
-# extended operation to update the password.
-pam_password exop
-
-# OpenLDAP SSL mechanism
-# start_tls mechanism uses the normal LDAP port, LDAPS typically 636
-ssl start_tls
-
-tls_cacertfile /etc/ssl/certs/private/abmas-cert.pem
-...
-</screen>
-</example>
-
- <para>
- The NSS control file <filename>/etc/nsswitch.conf</filename> has the following contents:
-<screen>
-# /etc/nsswitch.conf
-# This file controls the resolve order for system databases.
-
-# the following two lines obviate the "+" entry in /etc/passwd and /etc/group.
-passwd: compat ldap
-group: compat ldap
-# The above are all that I store in LDAP at this point. There are
-# possibilities to store hosts, services, ethers, and lots of other things.
-</screen>
- </para>
-
- <para>
- <indexterm><primary>PAM</primary></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- In my setup, users authenticate via PAM and NSS using LDAP-based accounts.
- The configuration file that controls the behavior of the PAM <command>pam_unix2</command>
- module is shown in <link linkend="sbepu2"/> file.
- This works out of the box with the configuration files in this chapter. It
- enables you to have no local accounts for users (it is highly advisable
- to have a local account for the root user). Traps for the unwary include the following:
- </para>
-
-<example id="sbepu2">
-<title>The PAM Control File <filename>/etc/security/pam_unix2.conf</filename></title>
-<screen>
-# pam_unix2 config file
-#
-# This file contains options for the pam_unix2.so module.
-# It contains a list of options for every type of management group,
-# which will be used for authentication, account management and
-# password management. Not all options will be used from all types of
-# management groups.
-#
-# At first, pam_unix2 will read this file and then uses the local
-# options. Not all options can be set her global.
-#
-# Allowed options are:
-#
-# debug (account, auth, password, session)
-# nullok (auth)
-# md5 (password / overwrites /etc/default/passwd)
-# bigcrypt (password / overwrites /etc/default/passwd)
-# blowfish (password / overwrites /etc/default/passwd)
-# crypt_rounds=XX
-# none (session)
-# trace (session)
-# call_modules=x,y,z (account, auth, password)
-#
-# Example:
-# auth: nullok
-# account:
-# password: nullok blowfish crypt_rounds=8
-# session: none
-#
-auth: use_ldap
-account: use_ldap
-password: use_ldap
-session: none
-</screen>
-</example>
-
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>authenticate</primary></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- <itemizedlist>
- <listitem>
- <para>
- If your LDAP database goes down, nobody can authenticate except for root.
- </para>
- </listitem>
-
- <listitem>
- <para>
- If failover is configured incorrectly, weird behavior can occur. For example,
- DNS can fail to resolve.
- </para>
- </listitem>
- </itemizedlist>
-
- <para>
- I do have two LDAP slave servers configured. That subject is beyond the scope
- of this document, and steps for implementing it are well documented.
- </para>
-
- <para>
- The following services authenticate using LDAP:
- </para>
- <indexterm><primary>UNIX</primary></indexterm>
- <indexterm><primary>Postfix</primary></indexterm>
- <indexterm><primary>Courier-IMAP</primary></indexterm>
- <simplelist>
- <member>UNIX login/ssh</member>
- <member>Postfix (SMTP)</member>
- <member>Courier-IMAP/IMAPS/POP3/POP3S</member>
- </simplelist>
-
- <para>
- <indexterm><primary>white-pages</primary></indexterm>
- <indexterm><primary>Windows Address Book</primary></indexterm>
- Companywide white pages can be searched using an LDAP client
- such as the one in the Windows Address Book.
- </para>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>smbldap-tools</primary></indexterm>
- Having gained a solid understanding of LDAP and a relatively workable LDAP tree
- thus far, it was time to configure Samba. I compiled the latest stable Samba and
- also installed the latest <command>smbldap-tools</command> from
- <ulink url="http://idealx.com">Idealx</ulink>.
- </para>
-
- <para>
- The Samba &smb.conf; file was configured as shown in <link linkend="ch8smbconf"/>.
- </para>
-
-<example id="ch8smbconf">
-<title>Samba Configuration File &smbmdash; smb.conf Part A</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MEGANET2</smbconfoption>
-<smbconfoption name="netbios name">MASSIVE</smbconfoption>
-<smbconfoption name="server string">Corp File Server</smbconfoption>
-<smbconfoption name="passdb backend">ldapsam:ldap://localhost</smbconfoption>
-<smbconfoption name="pam password change">Yes</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="log file">/data/samba/log/%m.log</smbconfoption>
-<smbconfoption name="name resolve order">wins host bcast</smbconfoption>
-<smbconfoption name="time server">Yes</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="cups options">Raw</smbconfoption>
-<smbconfoption name="add user script">/opt/IDEALX/sbin/smbldap-useradd -m "%u"</smbconfoption>
-<smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p "%g"</smbconfoption>
-<smbconfoption name="add user to group script">/opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"</smbconfoption>
-<smbconfoption name="delete user from group script">/opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"</smbconfoption>
-<smbconfoption name="set primary group script">/opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"</smbconfoption>
-<smbconfoption name="add machine script">/usr/local/sbin/smbldap-useradd -w "%m"</smbconfoption>
-<smbconfoption name="logon script">logon.bat</smbconfoption>
-<smbconfoption name="logon path">\\%L\profiles\%U\%a</smbconfoption>
-<smbconfoption name="logon drive">H:</smbconfoption>
-<smbconfoption name="logon home">\\%L\%U</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="wins support">Yes</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager,dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
-<smbconfoption name="ldap suffix">ou=MEGANET2,dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="ldap ssl">no</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
-<smbconfoption name="admin users">root, "@Domain Admins"</smbconfoption>
-<smbconfoption name="printer admin">"@Domain Admins"</smbconfoption>
-<smbconfoption name="force printername">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch8smbconf2">
-<title>Samba Configuration File &smbmdash; smb.conf Part B</title>
-<smbconfblock>
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network logon service</smbconfoption>
-<smbconfoption name="path">/data/samba/netlogon</smbconfoption>
-<smbconfoption name="write list">"@Domain Admins"</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-
-<smbconfsection name="[profiles]"/>
-<smbconfoption name="comment">Roaming Profile Share</smbconfoption>
-<smbconfoption name="path">/data/samba/profiles/</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-<smbconfoption name="veto files">desktop.ini</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="create mask">0770</smbconfoption>
-<smbconfoption name="veto files">desktop.ini</smbconfoption>
-<smbconfoption name="hide files">desktop.ini</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[software]"/>
-<smbconfoption name="comment">Software for %a computers</smbconfoption>
-<smbconfoption name="path">/data/samba/shares/software/%a</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-
-<smbconfsection name="[public]"/>
-<smbconfoption name="comment">Public Files</smbconfoption>
-<smbconfoption name="path">/data/samba/shares/public</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-
-<smbconfsection name="[PDF]"/>
-<smbconfoption name="comment">Location of documents printed to PDFCreator printer</smbconfoption>
-<smbconfoption name="path">/data/samba/shares/pdf</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch8smbconf3">
-<title>Samba Configuration File &smbmdash; smb.conf Part C</title>
-<smbconfblock>
-<smbconfsection name="[EVERYTHING]"/>
-<smbconfoption name="comment">All shares</smbconfoption>
-<smbconfoption name="path">/data/samba</smbconfoption>
-<smbconfoption name="valid users">"@Domain Admins"</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[CDROM]"/>
-<smbconfoption name="comment">CD-ROM on MASSIVE</smbconfoption>
-<smbconfoption name="path">/mnt</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers Share</smbconfoption>
-<smbconfoption name="path">/data/samba/drivers</smbconfoption>
-<smbconfoption name="write list">root</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/data/samba/spool</smbconfoption>
-<smbconfoption name="create mask">0644</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[acct_hp8500]"/>
-<smbconfoption name="comment">"Accounting Color Laser Printer"</smbconfoption>
-<smbconfoption name="path">/data/samba/spool/private</smbconfoption>
-<smbconfoption name="valid users">@acct, @acct_admin, @hr, "@Domain Admins",@Receptionist, dwayne, terri, danae, jerry</smbconfoption>
-<smbconfoption name="create mask">0644</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="copy">printers</smbconfoption>
-
-<smbconfsection name="[plotter]"/>
-<smbconfoption name="comment">Engineering Plotter</smbconfoption>
-<smbconfoption name="path">/data/samba/spool</smbconfoption>
-<smbconfoption name="create mask">0644</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="copy">printers</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch8smbconf4">
-<title>Samba Configuration File &smbmdash; smb.conf Part D</title>
-<smbconfblock>
-<smbconfsection name="[APPS]"/>
-<smbconfoption name="path">/data/samba/shares/Apps</smbconfoption>
-<smbconfoption name="force group">"Domain Users"</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[ACCT]"/>
-<smbconfoption name="path">/data/samba/shares/Accounting</smbconfoption>
-<smbconfoption name="valid users">@acct, "@Domain Admins"</smbconfoption>
-<smbconfoption name="force group">acct</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="create mask">0660</smbconfoption>
-<smbconfoption name="directory mask">0770</smbconfoption>
-
-<smbconfsection name="[ACCT_ADMIN]"/>
-<smbconfoption name="path">/data/samba/shares/Acct_Admin</smbconfoption>
-<smbconfoption name="valid users">@"acct_admin"</smbconfoption>
-<smbconfoption name="force group">acct_admin</smbconfoption>
-
-<smbconfsection name="[HR_PR]"/>
-<smbconfoption name="path">/data/samba/shares/HR_PR</smbconfoption>
-<smbconfoption name="valid users">@hr, @acct_admin</smbconfoption>
-<smbconfoption name="force group">hr</smbconfoption>
-
-<smbconfsection name="[ENGR]"/>
-<smbconfoption name="path">/data/samba/shares/Engr</smbconfoption>
-<smbconfoption name="valid users">@engr, @receptionist, @truss, "@Domain Admins", cheri</smbconfoption>
-<smbconfoption name="force group">engr</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="create mask">0770</smbconfoption>
-
-<smbconfsection name="[DATA]"/>
-<smbconfoption name="path">/data/samba/shares/DATA</smbconfoption>
-<smbconfoption name="valid users">@engr, @receptionist, @truss, "@Domain Admins", cheri</smbconfoption>
-<smbconfoption name="force group">engr</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="create mask">0770</smbconfoption>
-<smbconfoption name="copy">engr</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="ch8smbconf5">
-<title>Samba Configuration File &smbmdash; smb.conf Part E</title>
-<smbconfblock>
-<smbconfsection name="[X]"/>
-<smbconfoption name="path">/data/samba/shares/X</smbconfoption>
-<smbconfoption name="valid users">@engr, @acct</smbconfoption>
-<smbconfoption name="force group">engr</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="create mask">0770</smbconfoption>
-<smbconfoption name="copy">engr</smbconfoption>
-
-<smbconfsection name="[NETWORK]"/>
-<smbconfoption name="path">/data/samba/shares/network</smbconfoption>
-<smbconfoption name="valid users">"@Domain Users"</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="create mask">0770</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-
-<smbconfsection name="[UTILS]"/>
-<smbconfoption name="path">/data/samba/shares/Utils</smbconfoption>
-<smbconfoption name="write list">"@Domain Admins"</smbconfoption>
-
-<smbconfsection name="[SYS]"/>
-<smbconfoption name="path">/data/samba/shares/SYS</smbconfoption>
-<smbconfoption name="valid users">chad</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>Qbasic</primary></indexterm>
- <indexterm><primary>Rbase</primary></indexterm>
- <indexterm><primary>drive letters</primary></indexterm>
- Most of these shares are only used by one company group, but they are required
- because of some ancient Qbasic and Rbase applications were that written expecting
- their own drive letters.
- </para>
-
- <para>
- <indexterm><primary>rsync</primary></indexterm>
- <indexterm><primary>rsyncd.conf</primary></indexterm>
- <indexterm><primary>synchronize</primary></indexterm>
- Note: During the process of building the new server, I kept data files
- up to date with the Novell server via use of <command>rsync</command>.
- On a separate system (my workstation in fact), which could be rebooted
- whenever necessary, I set up a mount point to the Novell server via
- <command>ncpmount</command>. I then created a
- <filename>rsyncd.conf</filename> to share that mount point out to my
- new server, and synchronized once an hour. The script I used to synchronize
- is shown in <link linkend="sbersync"/>. The files exclusion list I used
- is shown in <link linkend="sbexcld"/>. The reason I had to have the
- <command>rsync</command> daemon running on a system that could be
- rebooted frequently is because <constant>ncpfs</constant>
- (part of the MARS NetWare Emulation package) has a nasty habit of creating stale
- mount points that cannot be recovered without a reboot. The reason for hourly
- synchronization is because some part of the chain was very slow and
- performance-heavy (whether <command>rsync</command> itself, the network,
- or the Novell server, I am not sure, but it was probably the Novell server).
- </para>
-
-<example id="sbersync">
-<title>Rsync Script</title>
-<screen>
-#!/bin/bash
-# Part 1 - rsync the Novell directories to the new server
-echo "#############################################"
-echo "New sync operation starting at `date`"
-if ! pgrep -fl '^rsync\> ; then
- echo "Good, no rsync is running!"
- echo "Synchronizing oink to BHPRO"
- rsync -av --exclude-from=/root/excludes.txt
-baa.corp:/BHPRO/SYS1/ /data/samba/shares/SYS1
- retval=$?
- [ ${retval} = 0 ] && echo "Sync operation completed at `date`"
- echo "Fixing permissions"
- # I had a whole lot more permission-fixing stuff here. It got
- # pared down as groups got moved over. The problem
- # was that the way I was mounting the directory, everything
- # was owned by the Novell administrator which translated to
- # Root. This is also why I could only do one-way sync because
- # I could not fix the ACLs on the Novell side.
- find /data/samba/shares/Engr/ -perm +770 -exec chmod 770 {} \;
- find /data/samba/shares/Engr/ ! -group engr -exec chgrp engr {} \;
-else
- # This rsync took ages and ages -- I had it set to run every hour but
- # I needed a way to prevent it running into itself.
- echo "Oh no, rsync is already running!"
-echo "#############################################"
-fi
-</screen>
-</example>
-
-<example id="sbexcld">
-<title>Rsync Files Exclusion List &smbmdash; <filename>/root/excludes.txt</filename></title>
-<screen>
-/Acct/
-/Apps/
-/DATA/
-/Engr/*.pc3
-/Engr/plotter
-/Engr/APPOLO/
-/Engr/LIBRARY/
-/Home/Accounting/
-/Home/Angie/
-/Home/AngieY/
-/Home/Brandon/
-/Home/Carl/
-</screen>
-</example>
-
- <para>
- After Samba was configured, I initialized the LDAP database. The first
- thing I had to do was store the LDAP password in the Samba configuration by
- issuing the command (as root):
-<screen>
-&rootprompt; smbpasswd -w verysecret
-</screen>
- where <quote>verysecret</quote> is replaced by the LDAP bind password.
- </para>
-
-<note><para>
-The Idealx smbldap-tools package can be configured using a script called
-<command>configure.pl</command> that is provided as part of the tool. See <link linkend="happy"/>
-for an example of its use. Many administrators, like Misty, choose to do this manually
-so as to maintain greater awareness of how the tool-chain works and possibly to avoid
-undesirable actions from occurring unnoticed.
-</para></note>
-
- <para>
- Now Samba was ready for use and it was time to configure the smbldap-tools. There are two
- relevant files, which are usually put into the directory
- <filename>/etc/smbldap-tools</filename>. The main file,
- <filename>smbldap.conf</filename> is shown in <link linkend="ch8ideal"/>.
- </para>
-
-<example id="ch8ideal">
-<title>Idealx smbldap-tools Control File &smbmdash; Part A</title>
-<screen>
-#########
-#
-# located in /etc/smbldap-tools/smbldap.conf
-#
-######################################################################
-#
-# General Configuration
-#
-######################################################################
-
-# Put your own SID
-# to obtain this number do: net getlocalsid
-SID="S-1-5-21-725326080-1709766072-2910717368"
-
-######################################################################
-#
-# LDAP Configuration
-#
-######################################################################
-
-# Notes: to use to dual ldap servers backend for Samba, you must patch
-# Samba with the dual-head patch from IDEALX. If not using this patch
-# just use the same server for slaveLDAP and masterLDAP.
-# Those two servers declarations can also be used when you have
-# . one master LDAP server where all writing operations must be done
-# . one slave LDAP server where all reading operations must be done
-# (typically a replication directory)
-
-# Ex: slaveLDAP=127.0.0.1
-slaveLDAP="127.0.0.1"
-slavePort="389"
-
-# Master LDAP : needed for write operations
-# Ex: masterLDAP=127.0.0.1
-masterLDAP="127.0.0.1"
-masterPort="389"
-
-# Use TLS for LDAP
-# If set to 1, this option will use start_tls for connection
-# (you should also used the port 389)
-ldapTLS="0"
-
-# How to verify the server's certificate (none, optional or require)
-# see "man Net::LDAP" in start_tls section for more details
-verify=""
-</screen>
-</example>
-
-<example id="ch8ideal2">
-<title>Idealx smbldap-tools Control File &smbmdash; Part B</title>
-<screen>
-# CA certificate
-# see "man Net::LDAP" in start_tls section for more details
-cafile=""
- certificate to use to connect to the ldap server
-# see "man Net::LDAP" in start_tls section for more details
-clientcert=""
-
-# key certificate to use to connect to the ldap server
-# see "man Net::LDAP" in start_tls section for more details
-clientkey=""
-
-# LDAP Suffix
-# Ex: suffix=dc=IDEALX,dc=ORG
-suffix="ou=MEGANET2,dc=abmas,dc=biz"
-
-# Where are stored Users
-# Ex: usersdn="ou=Users,dc=IDEALX,dc=ORG"
-usersdn="ou=People,${suffix}"
-
-# Where are stored Computers
-# Ex: computersdn="ou=Computers,dc=IDEALX,dc=ORG"
-computersdn="ou=People,${suffix}"
-
-# Where are stored Groups
-# Ex groupsdn="ou=Groups,dc=IDEALX,dc=ORG"
-groupsdn="ou=Groups,${suffix}"
-
-# Where are stored Idmap entries
-# (used if samba is a domain member server)
-# Ex groupsdn="ou=Idmap,dc=IDEALX,dc=ORG"
-idmapdn="ou=Idmap,${suffix}"
-
-# Where to store next uidNumber and gidNumber available
-sambaUnixIdPooldn="sambaDomainName=MEGANET2,${suffix}"
-
-# Default scope Used
-scope="sub"
-</screen>
-</example>
-
-<example id="ch8ideal3">
-<title>Idealx smbldap-tools Control File &smbmdash; Part C</title>
-<screen>
-# Unix password encryption (CRYPT, MD5, SMD5, SSHA, SHA)
-hash_encrypt="MD5"
-
-# if hash_encrypt is set to CRYPT, you may set a salt format.
-# default is "%s", but many systems will generate MD5 hashed
-# passwords if you use "$1$%.8s". This parameter is optional!
-crypt_salt_format="%s"
-
-######################################################################
-#
-# Unix Accounts Configuration
-#
-######################################################################
-
-# Login defs
-# Default Login Shell
-# Ex: userLoginShell="/bin/bash"
-userLoginShell="/bin/false"
-
-# Home directory
-# Ex: userHome="/home/%U"
-userHome="/home/%U"
-
-# Gecos
-userGecos="Samba User"
-
-# Default User (POSIX and Samba) GID
-defaultUserGid="513"
-
-# Default Computer (Samba) GID
-defaultComputerGid="515"
-
-# Skel dir
-skeletonDir="/etc/skel"
-
-# Default password validation time (time in days) Comment the next
-# line if you don't want password to be enable for
-# defaultMaxPasswordAge days (be careful to the sambaPwdMustChange
-# attribute's value)
-defaultMaxPasswordAge="45"
-</screen>
-</example>
-
-<example id="ch8ideal4">
-<title>Idealx smbldap-tools Control File &smbmdash; Part D</title>
-<screen>
-######################################################################
-#
-# SAMBA Configuration
-#
-######################################################################
-
-# The UNC path to home drives location (%U username substitution)
-# Ex: \\My-PDC-netbios-name\homes\%U
-# Just set it to a null string if you want to use the smb.conf
-# 'logon home' directive and/or disable roaming profiles
-userSmbHome=""
-
-# The UNC path to profiles locations (%U username substitution)
-# Ex: \\My-PDC-netbios-name\profiles\%U
-# Just set it to a null string if you want to use the smb.conf
-# 'logon path' directive and/or disable roaming profiles
-userProfile=""
-
-# The default Home Drive Letter mapping
-# (will be automatically mapped at logon time if home directory exist)
-# Ex: H: for H:
-userHomeDrive=""
-
-# The default user netlogon script name (%U username substitution)
-# if not used, will be automatically username.cmd
-# make sure script file is edited under DOS
-# Ex: %U.cmd
-# userScript="startup.cmd" # make sure script file is edited under DOS
-userScript=""
-
-# Domain appended to the users "mail"-attribute
-# when smbldap-useradd -M is used
-mailDomain="abmas.org"
-
-######################################################################
-#
-# SMBLDAP-TOOLS Configuration (default are ok for a RedHat)
-#
-######################################################################
-# Allows not to use smbpasswd
-# (if with_smbpasswd == 0 in smbldap_conf.pm) but
-# prefer Crypt::SmbHash library
-with_smbpasswd="0"
-smbpasswd="/usr/bin/smbpasswd"
-</screen>
-</example>
-
- <para>
- <indexterm><primary>TLS</primary></indexterm>
- Note: I chose not to take advantage of the TLS capability of this.
- Eventually I may go back and tweak it. Also, I chose not to take advantage
- of the master/slave configuration as I heard horror stories that it was
- unstable. My slave servers are replicas only.
- </para>
-
- <para>
- The <filename>/etc/smbldap-tools/smbldap_bind.conf</filename> file is shown here:
-<screen>
-# smbldap_bind.conf
-#
-# This file simply tells smbldap-tools how to bind to your LDAP server.
-# It has to be a DN with full write access to the Samba portion of
-# the database.
-
-############################
-# Credential Configuration #
-############################
-# Notes: you can specify two different configurations if you use a
-# master ldap for writing access and a slave ldap server for reading access
-# By default, we will use the same DN (so it will work for standard Samba
-# release)
-slaveDN="cn=Manager,dc=abmas,dc=biz"
-slavePw="verysecret"
-masterDN="cn=Manager,dc=abmas,dc=biz"
-masterPw="verysecret"
-</screen>
- </para>
-
- <para>
- The next step was to run the <command>smbldap-populate</command> command, which populates
- the LDAP tree with the appropriate default users, groups, and UID and GID pools.
- It creates a user called Administrator with UID=0 and GID=0 matching the
- Domain Admins group. This is fine because you can still log on as root to a Windows system,
- but it will break cached credentials if you need to log on as the administrator
- to a system that is not on the network.
- </para>
-
- <para>
- After the LDAP database has been preloaded, it is prudent to validate that the
- information needed is in the LDAP directory. This can be done done by restarting
- the LDAP server, then performing an LDAP search by executing:
-<screen>
-&rootprompt; ldapsearch -W -x -b "dc=abmas,dc=biz"\
- -D "cn=Manager,dc=abmas,dc=biz" \
- "(Objectclass=*)"
-Enter LDAP Password:
-# extended LDIF
-#
-# LDAPv3
-# base <dc=abmas,dc=biz> with scope sub
-# filter: (ObjectClass=*)
-# requesting: ALL
-#
-
-# abmas.biz
-dn: dc=abmas,dc=biz
-objectClass: dcObject
-objectClass: organization
-o: abmas
-dc: abmas
-
-# People, abmas.biz
-dn: ou=People,dc=abmas,dc=biz
-objectClass: organizationalUnit
-ou: People
-
-# Groups, abmas.biz
-dn: ou=Groups,dc=abmas,dc=biz
-objectClass: organizationalUnit
-ou: Groups
-
-# Idmap, abmas.biz
-dn: ou=Idmap,dc=abmas,dc=biz
-objectClass: organizationalUnit
-ou: Idmap
-...
-</screen>
- </para>
-
- <para>
- <indexterm><primary>Windows</primary></indexterm>
- <indexterm><primary>POSIX</primary></indexterm>
- <indexterm><primary>smbldap-groupadd</primary></indexterm>
- <indexterm><primary>RID</primary></indexterm>
- <indexterm><primary>sambaGroupMapping</primary></indexterm>
- With the LDAP directory now initialized, it was time to create the Windows and POSIX
- (UNIX) group accounts as well as the mappings from Windows groups to UNIX groups.
- The easiest way to do this was to use <command>smbldap-groupadd</command> command.
- It creates the group with the posixGroup and sambaGroupMapping attributes, a
- unique GID, and an automatically determined RID. I learned the hard way not to
- try to do this by hand.
- </para>
-
- <para>
- <indexterm><primary>group mapping</primary></indexterm>
- <indexterm><primary>smbldap-groupmod</primary></indexterm>
- <indexterm><primary>memberUID</primary></indexterm>
- After I had my group mappings in place, I added users to the groups (the users
- don't really have to exist yet). I used the <command>smbldap-groupmod</command>
- command to accomplish this. It can also be done manually by adding memberUID
- attributes to the group entries in LDAP.
- </para>
-
- <para>
- <indexterm><primary>sambaSamAccount</primary></indexterm>
- <indexterm><primary>posixAccount</primary></indexterm>
- <indexterm><primary>smbldap-usermod</primary></indexterm>
- The most monumental task of all was adding the sambaSamAccount information to each
- already existent posixAccount entry. I did it one at a time as I moved people onto
- the new server, by issuing the command:
-<screen>
-&rootprompt; smbldap-usermod -a -P username
-</screen>
- <indexterm><primary>NetWare</primary></indexterm>
- <indexterm><primary>LDIF</primary></indexterm>
- <indexterm><primary>slapcat</primary></indexterm>
- I completed that step for every user after asking the person what his or her current
- NetWare password was. The wiser way to have done it would probably have been to dump the
- entire database to an LDIF file. This can be done by executing:
-<screen>
-&rootprompt; slapcat > somefile.ldif
-</screen>
- <indexterm><primary>Perl</primary></indexterm>
- <indexterm><primary>objectClass</primary></indexterm>
- Then update the LDIF file created by using a Perl script to parse and add the
- appropriate attributes and objectClasses to each entry, followed by re-importing
- the entire database into the LDAP directory.
- </para>
-
- <para>
- Rebuilding of the LDAP directory can be done as follows:
-<screen>
-&rootprompt; rcldap stop
-&rootprompt; cd /data/ldap
-&rootprompt; rm *bdb _* log*
-&rootprompt; su - ldap -c "slapadd -l somefile.ldif"
-&rootprompt; rcldap start
-</screen>
- This can be done at any time and for any reason, with no harm to the database.
- </para>
-
- <para>
- I first added a test user, of course. The LDIF for this test user looks like
- this, to give you an idea:
-<screen>
-# Entry 1: cn=Test User,ou=people,ou=corp,dc=abmas,dc=biz
-dn:cn=Test User,ou=people,ou=corp,dc=abmas,dc=biz
-cn: Test User
-gecos: Test User
-gidNumber: 513
-givenName: Test
-homeDirectory: /home/test.user
-homePhone: 555
-l: Somewhere
-l: ST
-mail: test.user
-o: Corp
-objectClass: top
-objectClass: inetOrgPerson
-objectClass: posixAccount
-objectClass: sambaSamAccount
-postalCode: 12345
-sn: User
-street: 10 Some St.
-uid: test.user
-uidNumber: 1074
-sambaLogonTime: 0
-sambaLogoffTime: 2147483647
-sambaKickoffTime: 2147483647
-sambaPwdCanChange: 0
-displayName: Samba User
-sambaSID: S-1-5-21-725326080-1709766072-2910717368-3148
-sambaLMPassword: 9D29C287C58448F9AAD3B435B51404EE
-sambaAcctFlags: [U]
-sambaNTPassword: D062088E99C95E37D7702287BB35E770
-sambaPwdLastSet: 1102537694
-sambaPwdMustChange: 1106425694
-userPassword: {SSHA}UzFZ2VxRGdwUueLnTGtsTBtnsvMO1oj8
-loginShell: /bin/false
-</screen>
- </para>
-
- <para>
- Then I went over to a spare Windows NT machine and joined it to the MEGANET2 domain.
- It worked, and the machine's account entry under ou=Computers looks like this:
-<screen>
-dn:uid=w2kengrspare$,ou=Computers,ou=MEGANET2,dc=abmas,dc=biz
-objectClass: top
-objectClass: inetOrgPerson
-objectClass: posixAccount
-objectClass: sambaSamAccount
-cn: w2kengrspare$
-sn: w2kengrspare$
-uid: w2kengrspare$
-uidNumber: 1104
-gidNumber: 515
-homeDirectory: /dev/null
-loginShell: /bin/false
-description: Computer
-gecos: Computer
-sambaSID: S-1-5-21-725326080-1709766072-2910717368-3208
-sambaPrimaryGroupSID: S-1-5-21-725326080-1709766072-2910717368-2031
-displayName: W2KENGRSPARE$
-sambaPwdCanChange: 1103149236
-sambaPwdMustChange: 2147483647
-sambaNTPassword: CA199C45CB6737035DB6D9D9F6CD1834
-sambaPwdLastSet: 1103149236
-sambaAcctFlags: [W ]
-</screen>
- </para>
-
- <para>
- <indexterm><primary>netlogon</primary></indexterm>
- So now I could log on with a test user from the machine w2kengrspare. It was all well and
- good, but that user was in no groups yet and so had pretty boring access. I fixed that
- by writing the login script! To write the login script, I used
- <ulink url="http://www.kixtart.org">Kixtart</ulink> because it will work
- with every architecture of Windows, has an active and helpful user base, and was both
- easier to learn and more powerful than the standard netlogon scripts I have seen.
- I also did not have to do a logon script per user or per group.
- </para>
-
- <para>
- <indexterm><primary>Kixtart</primary></indexterm>
- I downloaded Kixtart and put the following files in my netlogon share:
-<screen>
-KIX32.EXE
-KX32.dll
-KX95.dll <-- Not needed unless you are running Win9x clients.
-kx16.dll <-- Probably not needed unless you are running DOS clients.
-kxrpc.exe <-- Probably useless as it has to run on the server and can
- only be run on NT. It's for Windows 95 to become group-aware.
- We can get around the need.
-</screen>
- </para>
-
- <para>
- <indexterm><primary>logon.kix</primary></indexterm>
- I then wrote the <filename>logon.kix</filename> file that is shown in
- <link linkend="ch8kix"/>. I chose to keep it all in one file, but it
- can be split up and linked via include directives.
- </para>
-
-<example id="ch8kix">
-<title>Kixtart Control File &smbmdash; File: logon.kix</title>
-<screen>
-; This script just calls the other scripts.
-
-; First we want to get things done for everyone.
-
-; Second, we do first-time login stuff.
-
-; Third, we go through the group-oriented scripts one at a time.
-
-
-; We want to check for group membership here to avoid the overhead of running
-; scripts which don't apply.
-call "\\massive\netlogon\scripts\main.kix"
-call "\\massive\netlogon\scripts\setup.kix"
-IF INGROUP("MEGANET2\ACCT")
- call "scripts\acct.kix"
-ENDIF
-IF INGROUP("MEGANET2\ENGR","MEGANET2\RECEPTIONIST")
-call "\\massive\netlogon\scripts\engr.kix"
-ENDIF
-IF INGROUP("MEGANET2\FURN")
- call "\\massive\netlogon\scripts\furn.kix"
-ENDIF
-IF INGROUP("MEGANET2\TRUSS")
- call "\\massive\netlogon\scripts\truss.kix"
-ENDIF
-</screen>
-</example>
-
-<example id="ch8kix2">
-<title>Kixtart Control File &smbmdash; File: main.kix</title>
-<screen>
-break on
-
-; Choose whether to hide the login window or not
-IF INGROUP("MEGANET2\Domain Admins")
- USE Z: \\massive\everything
- SETCONSOLE("show")
-ELSE
- ; Nobody cares about seeing the login script except admins
- SETCONSOLE("hide")
-ENDIF
-
-; Delete all previously connected shares
-USE * /delete
-
-SETTITLE("Logging on @USERID to @LDOMAIN at @TIME")
-
-; Set the time on the workstation
-$Timeserver = "\\massive"
-Settime $TimeServer
-
-; Map the home directory
-USE H: @HOMESHR ; connect to user's home share
-IF @ERROR = 0
-
- H:
- CD @HOMEDIR ; change directory to user's home directory
-ENDIF
-
-; Everyone gets the N drive
-USE N: \\massive\network
-</screen>
-</example>
-
-<example id="ch8kix3">
-<title>Kixtart Control File &smbmdash; File: setup.kix, Part A</title>
-<screen>
-; My setup.kix is where all of the redirection stuff happens. Note that with
-; the use of registry keys, this only happens the first time they log in ,or if
-; I delete the pertinent registry keys which triggers it to happen again:
-
-; Check to see if we have written the abmas sub-key before
-$RETURNCODE = EXISTKEY("HKEY_CURRENT_USER\abmas")
-IF NOT $RETURNCODE = 0
-; Add key for abmas-specific things on the first login
- ADDKEY("HKEY_CURRENT_USER\abmas")
- ; The following key gets deleted at the end of the first login
- ADDKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
-ENDIF
-
-; People with laptops need My Documents to be in their profile. People with
-; desktops can have My Documents redirected to their home directory to avoid
-; long delays with logging out and out-of-sync files.
-
-; Check to see if this is the first login -- doesn't make sense to do this
-; at the very first login
-
-$RETURNCODE = EXISTKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
-IF NOT $RETURNCODE = 0
-
-; We don't want to do this stuff for people with laptops or people in the FURN
-; group. (They store their profiles in a different server)
-
- IF NOT INGROUP("MASSIVE\Laptop","MASSIVE\FURN")
- $RETURNCODE=EXISTKEY("HKEY_CURRENT_USER\abmas\profile_copied")
-
-; A crude way to tell what OS our profile is for and copy the "My Documents"
-; to the redirected folder on the server. It works because the profiles
-; are stored as \\server\profiles\user\architecture
- IF NOT $RETURNCODE = 0
- IF EXIST("\\massive\profiles\@userID\WinXP")
- copy "\\massive\profiles\@userID\WinXP\My Documents\*"
-"\\massive\@userID\"
- ENDIF
- IF EXIST("\\massive\profiles\@userID\Win2K")
- copy "\\massive\profiles\@userID\Win2K\My Documents\*"
-"\\massive\@userID\"
- ENDIF
- IF EXIST("\\massive\profiles\@userID\WinNT")
- copy "\\massive\profiles\@userID\WinNT\My Documents\*"
-"\\massive\@userID\"
- ENDIF
-</screen>
-</example>
-
-<example id="ch8kix3b">
-<title>Kixtart Control File &smbmdash; File: setup.kix, Part B</title>
-<screen>
-; Now we will write the registry values to redirect the locations of "My
-Documents"
-; and other folders.
- ADDKEY("HKEY_CURRENT_USER\abmas\profile_copied")
- WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
-Windows\CurrentVersion\Explorer\User
-Shell Folders", "Personal","\\massive\@userID","REG_SZ")
- WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
-Windows\CurrentVersion\Explorer\User
-Shell Folders", "My Pictures", "\\massive\@userID\My Pictures", "REG_SZ")
- IF @PRODUCTTYPE="Windows 2000 Professional" or @PRODUCTTYPE="Windows XP
-Professional"
- WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
-Windows\CurrentVersion\Explorer\User
-Shell Folders", "My Videos", "\\massive\@userID\My Videos", "REG_SZ")
- WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
-Windows\CurrentVersion\Explorer\User
-Shell Folders", "My Music", "\\massive\@userID\My Music", "REG_SZ")
- WRITEVALUE("HKEY_CURRENT_USER\Software\Microsoft\
-Windows\CurrentVersion\Explorer\User
-Shell Folders", "My eBooks", "\\massive\@userID\My eBooks", "REG_SZ")
- ENDIF
- ENDIF
- ENDIF
-
-; Now we will delete the FIRST_LOGIN sub-key that we made before.
-; Note - to run this script again you will want to delete the HKCU\abmas
-; sub-key, log out, and log back in.
-$RETURNVALUE = EXISTKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
-IF $RETURNVALUE = 0
- DELKEY("HKEY_CURRENT_USER\abmas\FIRST_LOGIN")
-ENDIF
-</screen>
-</example>
-
-<example id="ch8kix4">
-<title>Kixtart Control File &smbmdash; File: acct.kix</title>
-<screen>
-; And here is one group-oriented script to show what can be
-; done that way: acct.kix:
-
-IF INGROUP("MASSIVE\Acct_Admin","MASSIVE\HR")
- USE I: \\MEGANET2\HR_PR
-ENDIF
-
-; Set up printer
-$RETURNVALUE = existkey("HKEY_CURRENT_USER\Printers\,,massive,acct_hp8500")
-IF NOT $RETURNVALUE = 0
- ADDPRINTERCONNECTION("\\massive\acct_hp8500")
- SETDEFAULTPRINTER("\\massive\acct_hp8500")
-ENDIF
-; Set up drive mappings
- USE M: \\massive\ACCT
- IF INGROUP("MEGANET2\ABRA")
- USE T: \\trussrv\abra
- ENDIF
-</screen>
-</example>
-
- <para>
- As you can see in the script, I redirected the My Documents to the user's home
- share if he or she were not in the Laptop group. I also added printers on a
- group-by-group basis, and if applicable I set the group printer. For this to
- be effective, the print drivers must be installed on the Samba server in the
- <filename>[print$]</filename> share. Ample documentation exists about how to
- do that, so it is not covered here.
- </para>
-
- <para>
- I call this script via the logon.bat script in the [netlogon] directory:
-<screen>
-\\corpsrv\netlogon\kix32 \\corpsrv\netlogon\logon.kix /f
-</screen>
- I only had to fully qualify the paths for Windows 9x, as Windows NT and
- greater automatically add [NETLOGON] to the path.
- </para>
-
- <para>
- Also of note for Win9x is that the drive mappings and printer setup will not
- work because they rely on RPC. You merely have to put the appropriate settings
- into the <filename>c:\autoexec.bat</filename> file or map the drives manually.
- One option is to check the OS as part of the Kixtart script, and if it
- is Win9x and is the first login, copy a premade
- <filename>autoexec.bat</filename> to the <filename>C:</filename> drive. I
- have only three such machines, and one is going away in the very near future,
- so it was easier to do it by hand.
- </para>
-
- <para>
- <indexterm><primary>upgrade</primary></indexterm>
- At this point I was able to add the users. This is the part that really falls
- into upgrade. I moved the users over one group at a time, starting with the
- people who used the least amount of resources on the network. With each group
- that I moved, I first logged on as a standard user in that group and took
- careful note of the environment, mainly the printers he or she used, the PATH,
- and what network resources he or she had access to (most importantly, which ones
- the user actually needed access to).
- </para>
-
- <para>
- I then added the user's SambaSamAccount information as mentioned earlier,
- and join the computer to the domain. The very first thing I had to do was to
- copy the user's profile to the new server. This was very important, and I really
- struggled with the most effective way to do it. Here is the method that worked
- for every one of my users on Windows NT, 2000, and XP:
- </para>
-
- <procedure>
- <step><para>
- Log in as the user on the domain. This creates the local copy
- of the user's profile and copies it to the server as he or she logs out.
- </para></step>
-
- <step><para>
- Reboot the computer and log in as the local machine administrator.
- </para></step>
-
- <step><para>
- Right-click My Computer, click Properties, and navigate to the
- user profiles tab (varies per version of Windows).
- </para></step>
-
- <step><para>
- Select the user's local profile <constant>(COMPUTERNAME\username)</constant>,
- and click the <command>Copy To</command> button.
- </para></step>
-
- <step><para>
- In the next dialog, copy it directly to the profiles share on the
- Samba server (in my case \\PDCname\profiles\user\<architecture>.
- You will have had to make a connection to the share as that
- user (e.g., Windows Explorer type \\PDCname\profiles\username).
- </para></step>
-
- <step><para>
- When the copy is complete (it can take a while) log out, and log back in
- as the user. All of his or her settings and all contents of My Documents,
- Favorites, and the registry should have been copied successfully.
- </para></step>
-
- <step><para>
- If it doesn't look right (the dead giveaway is the desktop background),
- shut down the computer without logging out (power cycle) and try logging
- in as the user again. If it still doesn't work, repeat the steps above.
- I only had to ever repeat it once.
- </para></step>
-
- </procedure>
-
- <para>
- Words to the Wise:
- </para>
-
- <itemizedlist>
- <listitem><para>
- If the user was anything other than a standard user on his or her system
- before, you will save yourself some headaches by giving him or her identical
- permissions (on the local machine) as his or her domain account <emphasis>before</emphasis>
- copying the profile over. Do this through the User Administrator
- in the Control Panel, after joining the computer to the domain and
- before logging on as that user for the first time. Otherwise the user will
- have trouble with permissions on his or her registry keys.
- </para></listitem>
-
- <listitem><para>
- If any application was installed for the user only, rather than for
- the entire system, it will probably not work without being reinstalled.
- </para></listitem>
- </itemizedlist>
-
- <para>
- After all these steps are accomplished, only cleanup details are left. Make sure user's
- shortcuts and Network Places point to the appropriate place on the new server, check
- the important applications to be sure they work as expected and troubleshoot any problems
- that might arise, and check to be sure the user's printers are present and working. By the
- way, if there are any network printers installed as system printers (the Novell way),
- you will need to log in as a local administrator and delete them.
- </para>
-
- <para>
- For my non-laptop systems, I would then log in and out a couple times as the user
- to be sure that his or her registry settings were modified, and then I was finished.
- </para>
-
- <para>
- Some compatibility issues that cropped up included the following:
- </para>
-
- <para>
- Blackberry client: It did not like having its registry settings moved around
- and so had to be reinstalled. Also, it needed write permissions to a portion of
- the hard drive, and I had to give it those manually on the one system where
- this was an issue.
- </para>
-
- <para>
- CAMedia: Digital camera software for Canon cameras caused all kinds of trouble
- with the registry. I had to use the Run as service to open the registry of
- the local user while logged in as the domain user, and give the domain user
- the appropriate permissions to some registry keys, then export that portion
- of the registry to a file. Then, as the domain user, I had to import that file
- into the registry.
- </para>
-
- <para>
- Crystal Reports version 7: More registry problems that were solved by recopying
- the user's profile.
- </para>
-
- <para>
- Printing from legacy applications: I found out that Novell sends its jobs to
- the printer in a raw format. CUPS sends them in PostScript by default. I had
- to make a second printer definition for one printer and tell CUPS specifically
- to send raw data to the printer, then assign this printer to the LPT port with
- Kixtart's version of the net use command.
- </para>
-
- <para>
- These were all eventually solved by elbow grease, queries to the Samba mailing
- list and others, and diligence. The complete migration took about 5 weeks.
- My userbase is relatively small but includes multiple versions of Windows,
- multiple Linux member servers, a mechanized saw, a pen plotter, and legacy
- applications written in Qbasic and R:Base, just to name a few. I actually
- ended up making some of these applications work better (or work again, as
- some of them had stopped functioning on the old server) because as part of
- the process I had to find out how things were supposed to work.
- </para>
-
- <para>
- The one thing I have not been able to get working is a very old database that
- we had around for reference purposes; it uses Novell's Btrieve engine.
- </para>
-
- <para>
- As the resources compare, I went from 95 percent disk usage to just around 10 percent.
- I went from a very high load on the server to an average load of between one
- and two runnable processes on the server. I have improved the security and
- robustness of the system. I have also implemented
- <ulink url="http://www.clamav.net">ClamAV</ulink> antivirus software,
- which scans the entire Samba server for viruses every 2 hours and
- quarantines them. I have found it much less problematic than our ancient
- version of Norton Antivirus Corporate Edition, and much more up-to-date.
- </para>
-
- <para>
- In short, my users are much happier now that the new server is running, and that
- is what is important to me.
- </para>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="secure">
- <title>Secure Office Networking</title>
-
- <para>
- Congratulations, your Samba networking skills are developing nicely. You started out
- with three simple networks in <link linkend="simple"/>, and then in <link linkend="small"/>
- you designed and built a network that provides a high degree of flexibility, integrity,
- and dependability. It was enough for the basic needs each was designed to fulfill. In
- this chapter you address a more complex set of needs. The solution you explore
- introduces you to basic features that are specific to Samba.
- </para>
-
- <para>
- You should note that a working and secure solution could be implemented using Samba-2.2.x.
- In the exercises presented here, you are gradually using more Samba-specific features,
- so caution is advised for anyone who tries to use Samba-2.2.x with the guidance here given.
- To avoid confusion, this book is all about Samba. Let's get the exercises in this
- chapter underway.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- You have made Mr. Meany a very happy man. Recently he paid you a fat bonus for work
- well done. It is one year since the last network upgrade. You have been quite busy.
- Two months ago Mr. Meany gave approval to hire Christine Roberson, who has taken over
- general network management. Soon she will provide primary user support. You have
- demonstrated that you can delegate responsibility and can plan and execute according
- to that plan. Above all, you have shown Mr. Meany that you are a responsible person.
- Today is a big day. Mr. Meany called you to his office at 9 a.m. for news you never
- expected: You are going to take charge of business operations. Mr. Meany
- is retiring and has entrusted the business to your capable hands.
- </para>
-
- <para>
- Mr. Meany may be retiring from this company, but not from work. He is taking the
- opportunity to develop Abmas Accounting into a larger and more substantial company.
- He says that it took him many years to learn that there is no future in just running
- a business. He now realizes there is great personal satisfaction in the creation of
- career opportunities for people in the local community. He wants to do more for others,
- as he is doing for you. Today he spent a lot of time talking about his grand plan
- for growth, which you will deal with in the chapters ahead.
- </para>
-
- <para>
- Over the past year, the growth projections were exceeded. The network has grown to
- meet the needs of 130 users. Along with growth, the demand for improved services
- and better functionality has also developed. You are about to make an interim
- improvement and then hand over all Help desk and network maintenance to Christine.
- Christine has professional certifications in Microsoft Windows as well as in Linux;
- she is a hard worker and quite likable. Christine does not want to manage the department
- (although she manages well). She gains job satisfaction when left to sort things out.
- Occasionally she wants to work with you on a challenging problem. When you told her
- about your move, she almost resigned, although she was reassured that a new manager would
- be hired to run Information Technology, and she would be responsible only for operations.
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- You promised the staff Internet services including Web browsing, electronic mail, virus
- protection, and a company Web site. Christine is eager to help turn the vision into
- reality. Let's see how close you can get to the promises made.
- </para>
-
- <para>
- The network you are about to deliver will service 130 users today. Within a year,
- Abmas will aquire another company. Mr. Meany claims that within 2 years there will be
- well over 500 users on the network. You have bought into the big picture, so prepare
- for growth. You have purchased a new server and will implement a new network infrastructure.
- </para>
-
- <para>
- You have decided to not recycle old network components. The only items that will be
- carried forward are notebook computers. You offered staff new notebooks, but not
- one person wanted the disruption for what was perceived as a marginal update.
- You decided to give everyone, even the notebook user, a new desktop computer.
- </para>
-
- <para>
- You procured a DSL Internet connection that provides 1.5 Mb/sec (bidirectional)
- and a 10 Mb/sec ethernet port. You registered the domain
- <constant>abmas.us</constant>, and the Internet Service Provider (ISP) is supplying
- secondary DNS. Information furnished by your ISP is shown in <link linkend="chap4netid"/>.
- </para>
-
- <para>
- It is of paramount priority that under no circumstances will Samba offer
- service access from an Internet connection. You are paying an ISP to
- give, as part of its value-added services, full firewall protection for your
- connection to the outside world. The only services allowed in from
- the Internet side are the following destination ports: <constant>http/https (ports
- 80 and 443), email (port 25), DNS (port 53)</constant>. All Internet traffic
- will be allowed out after network address translation (NAT). No internal IP addresses
- are permitted through the NAT filter because complete privacy of internal network
- operations must be assured.
- </para>
-
- <table id="chap4netid">
- <title>Abmas.US ISP Information</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="center"/>
- <thead>
- <row>
- <entry>Parameter</entry>
- <entry>Value</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Server IP Address</entry>
- <entry>123.45.67.66</entry>
- </row>
- <row>
- <entry>DSL Device IP Address</entry>
- <entry>123.45.67.65</entry>
- </row>
- <row>
- <entry>Network Address</entry>
- <entry>123.45.67.64/30</entry>
- </row>
- <row>
- <entry>Gateway Address</entry>
- <entry>123.45.54.65</entry>
- </row>
- <row>
- <entry>Primary DNS Server</entry>
- <entry>123.45.54.65</entry>
- </row>
- <row>
- <entry>Secondary DNS Server</entry>
- <entry>123.45.54.32</entry>
- </row>
- <row>
- <entry>Forwarding DNS Server</entry>
- <entry>123.45.12.23</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <figure id="ch04net">
- <title>Abmas Network Topology &smbmdash; 130 Users</title>
- <imagefile scale="65">chap4-net</imagefile>
- </figure>
-
- <para>
- Christine recommended that desktop systems should be installed from a single cloned
- master system that has a minimum of locally installed software and loads all software
- off a central application server. The benefit of having the central application server
- is that it allows single-point maintenance of all business applications, a more
- efficient way to manage software. She further recommended installation of antivirus
- software on workstations as well as on the Samba server. Christine knows the dangers
- of potential virus infection and insists on a comprehensive approach to detective
- as well as corrective action to protect network operations.
- </para>
-
- <para>
- A significant concern is the problem of managing company growth. Recently, a number
- of users had to share a PC while waiting for new machines to arrive. This presented
- some problems with desktop computers and software installation into the new users'
- desktop profiles.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- Many of the conclusions you draw here are obvious. Some requirements are not very clear
- or may simply be your means of drawing the most out of Samba. Much can be done more simply
- than you will demonstrate here, but keep in mind that the network must scale to at least 500
- users. This means that some functionality will be overdesigned for the current 130-user
- environment.
- </para>
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- In this exercise we use a 24-bit subnet mask for the two local networks. This,
- of course, limits our network to a maximum of 253 usable IP addresses. The network
- address range chosen is one assigned by RFC1918 for private networks.
- When the number of users on the network begins to approach the limit of usable
- addresses, it is a good idea to switch to a network address specified in RFC1918
- in the 172.16.0.0/16 range. This is done in subsequent chapters.
- </para>
-
- <para>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- The high growth rates projected are a good reason to use the <constant>tdbsam</constant>
- passdb backend. The use of <constant>smbpasswd</constant> for the backend may result in
- performance problems. The <constant>tdbsam</constant> passdb backend offers features that
- are not available with the older, flat ASCII-based <constant>smbpasswd</constant> database.
- </para>
-
- <para>
- <indexterm><primary>risk</primary></indexterm>
- The proposed network design uses a single server to act as an Internet services host for
- electronic mail, Web serving, remote administrative access via SSH,
- Samba-based file and print services. This design is often chosen by sites that feel
- they cannot afford or justify the cost or overhead of having separate servers. It must
- be realized that if security of this type of server should ever be violated (compromised),
- the whole network and all data is at risk. Many sites continue to choose this type
- of solution; therefore, this chapter provides detailed coverage of key implementation
- aspects.
- </para>
-
- <para>
- Samba will be configured to specifically not operate on the Ethernet interface that is
- directly connected to the Internet.
- </para>
-
- <para>
- <indexterm><primary>iptables</primary></indexterm>
- <indexterm><primary>NAT</primary></indexterm>
- <indexterm><primary>Network Address Translation</primary><see>NAT</see></indexterm>
- <indexterm><primary>firewall</primary></indexterm>
- You know that your ISP is providing full firewall services, but you cannot rely on that.
- Always assume that human error will occur, so be prepared by using Linux firewall facilities
- based on <command>iptables</command> to effect NAT. Block all
- incoming traffic except to permitted well-known ports. You must also allow incoming packets
- to establish outgoing connections. You will permit all internal outgoing requests.
- </para>
-
- <para>
- The configuration of Web serving, Web proxy services, electronic mail, and the details of
- generic antivirus handling are beyond the scope of this book and therefore are not
- covered except insofar as this affects Samba.
- </para>
-
- <para>
- <indexterm><primary>login</primary></indexterm>
- Notebook computers are configured to use a network login when in the office and a
- local account to log in while away from the office. Users store all work done in
- transit (away from the office) by using a local share for work files. Standard procedures
- dictate that on completion of the work that necessitates mobile file access, all
- work files are moved back to secure storage on the office server. Staff is instructed
- to not carry on any company notebook computer any files that are not absolutely required.
- This is a preventative measure to protect client information as well as private business
- records.
- </para>
-
- <para>
- <indexterm><primary>application server</primary></indexterm>
- All applications are served from the central server from a share called <constant>apps</constant>.
- Microsoft Office XP Professional and OpenOffice 1.1.0 will be installed using a network
- (or administrative) installation. Accounting and financial management software can also
- be run only from the central application server. Notebook users are provided with
- locally installed applications on a need-to-have basis only.
- </para>
-
- <para>
- <indexterm><primary>roaming profiles</primary></indexterm>
- The introduction of roaming profiles support means that users can move between
- desktop computer systems without constraint while retaining full access to their data.
- The desktop travels with them as they move.
- </para>
-
- <para>
- <indexterm><primary>DNS</primary></indexterm>
- The DNS server implementation must now address both internal and external
- needs. You forward DNS lookups to your ISP-provided server as well as the
- <constant>abmas.us</constant> external secondary DNS server.
- </para>
-
- <para>
- <indexterm><primary>dynamic DNS</primary></indexterm>
- <indexterm><primary>DDNS</primary><see>dynamic DNS</see></indexterm>
- <indexterm><primary>DHCP server</primary></indexterm>
- Compared with the DHCP server configuration in <link linkend="small"/>, <link linkend="dhcp01"/>, the
- configuration used in this example has to deal with the presence of an Internet connection.
- The scope set for it ensures that no DHCP services will be offered on the external
- connection. All printers are configured as DHCP clients so that the DHCP server assigns
- the printer a fixed IP address by way of the Ethernet interface (MAC) address. One additional
- feature of this DHCP server configuration file is the inclusion of parameters to allow dynamic
- DNS (DDNS) operation.
- </para>
-
- <para>
- This is the first implementation that depends on a correctly functioning DNS server.
- Comprehensive steps are included to provide for a fully functioning DNS server that also
- is enabled for DDNS operation. This means that DHCP clients can be autoregistered
- with the DNS server.
- </para>
-
- <para>
- You are taking the opportunity to manually set the netbios name of the Samba server to
- a name other than what will be automatically resolved. You are doing this to ensure that
- the machine has the same NetBIOS name on both network segments.
- </para>
-
- <para>
- As in the previous network configuration, printing in this network configuration uses
- direct raw printing (i.e., no smart printing and no print driver autodownload to Windows
- clients). Printer drivers are installed on the Windows client manually. This is not
- a problem because Christine is to install and configure one single workstation and
- then clone that configuration, using Norton Ghost, to all workstations. Each machine is
- identical, so this should pose no problem.
- </para>
-
- <sect3>
- <title>Hardware Requirements</title>
-
- <para>
- <indexterm><primary>memory requirements</primary></indexterm>
- This server runs a considerable number of services. From similarly configured Linux
- installations, the approximate calculated memory requirements are as shown in
- <link linkend="ch4memoryest"/>.
-
-<example id="ch4memoryest">
-<title>Estimation of Memory Requirements</title>
-<screen>
-Application Memory per User 130 Users 500 Users
- Name (MBytes) Total MBytes Total MBytes
------------ --------------- ------------ ------------
-DHCP 2.5 3 3
-DNS 16.0 16 16
-Samba (nmbd) 16.0 16 16
-Samba (winbind) 16.0 16 16
-Samba (smbd) 4.0 520 2000
-Apache 10.0 (20 User) 200 200
-CUPS 3.5 16 32
-Basic OS 256.0 256 256
- -------------- --------------
- Total: 1043 MBytes 2539 MBytes
- -------------- --------------
-</screen>
-</example>
- You should add a safety margin of at least 50% to these estimates. The minimum
- system memory recommended for initial startup 1 GB, but to permit the system
- to scale to 500 users, it makes sense to provision the machine with 4 GB memory.
- An initial configuration with only 1 GB memory would lead to early performance complaints
- as the system load builds up. Given the low cost of memory, it does not make sense to
- compromise in this area.
- </para>
-
- <para>
- <indexterm><primary>bandwidth calculations</primary></indexterm>
- Aggregate input/output loads should be considered for sizing network configuration as
- well as disk subsystems. For network bandwidth calculations, one would typically use an
- estimate of 0.1 MB/sec per user. This suggests that 100-Base-T (approx. 10 MB/sec)
- would deliver below acceptable capacity for the initial user load. It is therefore a good
- idea to begin with 1 Gb Ethernet cards for the two internal networks, each attached
- to a 1 Gb Ethernet switch that provides connectivity to an expandable array of 100-Base-T
- switched ports.
- </para>
-
- <para>
- <indexterm><primary>network segments</primary></indexterm>
- <indexterm><primary>RAID</primary></indexterm>
- Considering the choice of 1 Gb Ethernet interfaces for the two local network segments,
- the aggregate network I/O capacity will be 2100 Mb/sec (about 230 MB/sec), an I/O
- demand that would require a fast disk storage I/O capability. Peak disk throughput is
- limited by the disk subsystem chosen. It is desirable to provide the maximum
- I/O bandwidth affordable. If a low-cost solution must be chosen,
- 3Ware IDE RAID Controllers are a good choice. These controllers can be fitted into a
- 64-bit, 66 MHz PCI-X slot. They appear to the operating system as a high-speed SCSI
- controller that can operate at the peak of the PCI-X bandwidth (approximately 450 MB/sec).
- Alternative SCSI-based hardware RAID controllers should also be considered. Alternately,
- it makes sense to purchase well-known, branded hardware that has appropriate performance
- specifications. As a minimum, one should attempt to provide a disk subsystem that can
- deliver I/O rates of at least 100 MB/sec.
- </para>
-
- <para>
- Disk storage requirements may be calculated as shown in <link linkend="ch4diskest"/>.
-
-<example id="ch4diskest">
-<title>Estimation of Disk Storage Requirements</title>
-<screen>
-Corporate Data: 100 MBytes/user per year
-Email Storage: 500 MBytes/user per year
-Applications: 5000 MBytes
-Safety Buffer: At least 50%
-
-Given 500 Users and 2 years:
------------------------------
- Corporate Data: 2 x 100 x 500 = 100000 MBytes = 100 GBytes
- Email Storage: 2 x 500 x 500 = 500000 MBytes = 500 GBytes
- Applications: 5000 MBytes = 5 GBytes
- ----------------------------
- Total: 605 GBytes
- Add 50% buffer 303 GBytes
- Recommended Storage: 908 GBytes
-</screen>
-</example>
- <indexterm><primary>storage capacity</primary></indexterm>
- The preferred storage capacity should be approximately 1 Terabyte. Use of RAID level 5
- with two hot spare drives would require an 8-drive by 200 GB capacity per drive array.
- </para>
-
- </sect3>
-
- </sect2>
-
-
- <sect2>
- <title>Political Issues</title>
-
- <para>
- Your industry is coming under increasing accountability pressures. Increased paranoia
- is necessary so you can demonstrate that you have acted with due diligence. You must
- not trust your Internet connection.
- </para>
-
- <para>
- Apart from permitting more efficient management of business applications through use of
- an application server, your primary reason for the decision to implement this is that it
- gives you greater control over software licensing.
- </para>
-
- <para>
- <indexterm><primary>Outlook Express</primary></indexterm>
- You are well aware that the current configuration results in some performance issues
- as the size of the desktop profile grows. Given that users use Microsoft Outlook
- Express, you know that the storage implications of the <constant>.PST</constant> file
- is something that needs to be addressed later.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- <link linkend="ch04net"/> demonstrates the overall design of the network that you will implement.
- </para>
-
- <para>
- The information presented here assumes that you are already familiar with many basic steps.
- As this stands, the details provided already extend well beyond just the necessities of
- Samba configuration. This decision is deliberate to ensure that key determinants
- of a successful installation are not overlooked. This is the last case that documents
- the finite minutiae of DHCP and DNS server configuration. Beyond the information provided
- here, there are many other good reference books on these subjects.
- </para>
-
- <para>
- The &smb.conf; file has the following noteworthy features:
- </para>
-
- <itemizedlist>
- <listitem><para>
- The NetBIOS name of the Samba server is set to <constant>DIAMOND</constant>.
- </para></listitem>
-
- <listitem><para>
- The Domain name is set to <constant>PROMISES</constant>.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>broadcast messages</primary></indexterm>
- <indexterm><primary>interfaces</primary></indexterm>
- <indexterm><primary>bind interfaces only</primary></indexterm>
- Ethernet interface <constant>eth0</constant> is attached to the Internet connection
- and is externally exposed. This interface is explicitly not available for Samba to use.
- Samba listens on this interface for broadcast messages but does not broadcast any
- information on <constant>eth0</constant>, nor does it accept any connections from it.
- This is achieved by way of the <parameter>interfaces</parameter> parameter and the
- <parameter>bind interfaces only</parameter> entry.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>binary database</primary></indexterm>
- The <parameter>passdb backend</parameter> parameter specifies the creation and use
- of the <constant>tdbsam</constant> password backend. This is a binary database that
- has excellent scalability for a large number of user account entries.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>WINS serving</primary></indexterm>
- <indexterm><primary>wins support</primary></indexterm>
- <indexterm><primary>name resolve order</primary></indexterm>
- WINS serving is enabled by the <smbconfoption name="wins support">Yes</smbconfoption>,
- and name resolution is set to use it by means of the
- <smbconfoption name="name resolve order">wins bcast hosts</smbconfoption> entry.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>time server</primary></indexterm>
- The Samba server is configured for use by Windows clients as a time server.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>CUPS</primary></indexterm>
- <indexterm><primary>printing</primary></indexterm>
- <indexterm><primary>printcap name</primary></indexterm>
- Samba is configured to directly interface with CUPS via the direct internal interface
- that is provided by CUPS libraries. This is achieved with the
- <smbconfoption name="printing">CUPS</smbconfoption> as well as the
- <smbconfoption name="printcap name">CUPS</smbconfoption> entries.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>user management</primary></indexterm>
- <indexterm><primary>group management</primary></indexterm>
- <indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
- External interface scripts are provided to enable Samba to interface smoothly to
- essential operating system functions for user and group management. This is important
- to enable workstations to join the Domain and is also important so that you can use
- the Windows NT4 Domain User Manager as well as the Domain Server Manager. These tools
- are provided as part of the <filename>SRVTOOLS.EXE</filename> toolkit that can be
- downloaded from the Microsoft FTP
- <ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">site</ulink>.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>User Mode</primary></indexterm>
- The &smb.conf; file specifies that the Samba server will operate in (default) <parameter>
- security = user</parameter> mode<footnote><para>See <emphasis>TOSHARG2</emphasis>, Chapter 3.
- This is necessary so that Samba can act as a Domain Controller (PDC); see
- <emphasis>TOSHARG2</emphasis>, Chapter 4, for additional information.</para></footnote>
- (User Mode).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>logon services</primary></indexterm>
- <indexterm><primary>logon script</primary></indexterm>
- Domain logon services as well as a Domain logon script are specified. The logon script
- will be used to add robustness to the overall network configuration.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>roaming profiles</primary></indexterm>
- <indexterm><primary>logon path</primary></indexterm>
- <indexterm><primary>profile share</primary></indexterm>
- Roaming profiles are enabled through the specification of the parameter,
- <smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>. The value of this parameter translates the
- <constant>%L</constant> to the name by which the Samba server is called by the client (for this
- configuration, it translates to the name <constant>DIAMOND</constant>), and the <constant>%U</constant>
- will translate to the name of the user within the context of the connection made to the profile share.
- It is the administrator's responsibility to ensure there is a directory in the root of the
- profile share for each user. This directory must be owned by the user also. An exception to this
- requirement is when a profile is created for group use.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>virus</primary></indexterm>
- <indexterm><primary>opportunistic locking</primary></indexterm>
- Precautionary veto is effected for particular Windows file names that have been targeted by
- virus-related activity. Additionally, Microsoft Office files are vetoed from opportunistic locking
- controls. This should help to prevent lock contention-related file access problems.
- </para></listitem>
-
- <listitem><para>
- Every user has a private home directory on the UNIX/Linux host. This is mapped to
- a network drive that is the same for all users.
- </para></listitem>
-
- </itemizedlist>
-
- <para>
- The configuration of the server is the most complex so far. The following steps are used:
- </para>
-
- <orderedlist numeration="arabic">
- <listitem><para>
- Basic System Configuration
- </para></listitem>
-
- <listitem><para>
- Samba Configuration
- </para></listitem>
-
- <listitem><para>
- DHCP and DNS Server Configuration
- </para></listitem>
-
- <listitem><para>
- Printer Configuration
- </para></listitem>
-
- <listitem><para>
- Process Start-up Configuration
- </para></listitem>
-
- <listitem><para>
- Validation
- </para></listitem>
-
- <listitem><para>
- Application Share Configuration
- </para></listitem>
-
- <listitem><para>
- Windows Client Configuration
- </para></listitem>
- </orderedlist>
-
- <para>
- The following sections cover each step in logical and defined detail.
- </para>
-
- <sect2 id="ch4bsc">
- <title>Basic System Configuration</title>
-
- <para>
- <indexterm><primary>SUSE Enterprise Linux Server</primary></indexterm>
- The preparation in this section assumes that your SUSE Enterprise Linux Server 8.0 system has been
- freshly installed. It prepares basic files so that the system is ready for comprehensive
- operation in line with the network diagram shown in <link linkend="ch04net"/>.
- </para>
-
- <procedure>
- <title>Server Configuration Steps</title>
-
- <step><para>
- <indexterm><primary>hostname</primary></indexterm>
- Using the UNIX/Linux system tools, name the server <constant>server.abmas.us</constant>.
- Verify that your hostname is correctly set by running:
-<screen>
-&rootprompt; uname -n
-server
-</screen>
- An alternate method to verify the hostname is:
-<screen>
-&rootprompt; hostname -f
-server.abmas.us
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- <indexterm><primary>localhost</primary></indexterm>
- Edit your <filename>/etc/hosts</filename> file to include the primary names and addresses
- of all network interfaces that are on the host server. This is necessary so that during
- startup the system can resolve all its own names to the IP address prior to
- startup of the DNS server. An example of entries that should be in the
- <filename>/etc/hosts</filename> file is:
-<screen>
-127.0.0.1 localhost
-192.168.1.1 sleeth1.abmas.biz sleeth1 diamond
-192.168.2.1 sleeth2.abmas.biz sleeth2
-123.45.67.66 server.abmas.us server
-</screen>
- You should check the startup order of your system. If the CUPS print server is started before
- the DNS server (<command>named</command>), you should also include an entry for the printers
- in the <filename>/etc/hosts</filename> file, as follows:
-<screen>
-192.168.1.20 qmsa.abmas.biz qmsa
-192.168.1.30 hplj6a.abmas.biz hplj6a
-192.168.2.20 qmsf.abmas.biz qmsf
-192.168.2.30 hplj6f.abmas.biz hplj6f
-</screen>
- <indexterm><primary>named</primary></indexterm>
- <indexterm><primary>cupsd</primary></indexterm>
- <indexterm><primary>daemon</primary></indexterm>
- The printer entries are not necessary if <command>named</command> is started prior to
- startup of <command>cupsd</command>, the CUPS daemon.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/rc.d/boot.local</primary></indexterm>
- <indexterm><primary>IP forwarding</primary></indexterm>
- <indexterm><primary>/proc/sys/net/ipv4/ip_forward</primary></indexterm>
- The host server is acting as a router between the two internal network segments as well
- as for all Internet access. This necessitates that IP forwarding be enabled. This can be
- achieved by adding to the <filename>/etc/rc.d/boot.local</filename> an entry as follows:
-<screen>
-echo 1 > /proc/sys/net/ipv4/ip_forward
-</screen>
- To ensure that your kernel is capable of IP forwarding during configuration, you may
- wish to execute that command manually also. This setting permits the Linux system to
- act as a router.<footnote><para>You may want to do the echo command last and include
- "0" in the init scripts, since it opens up your network for a short time.</para></footnote>
- </para></step>
-
- <step><para>
- <indexterm><primary>firewall</primary></indexterm>
- <indexterm><primary>abmas-netfw.sh</primary></indexterm>
- Installation of a basic firewall and NAT facility is necessary.
- The following script can be installed in the <filename>/usr/local/sbin</filename>
- directory. It is executed from the <filename>/etc/rc.d/boot.local</filename> startup
- script. In your case, this script is called <filename>abmas-netfw.sh</filename>. The
- script contents are shown in <link linkend="ch4natfw"/>.
-
-<example id="ch4natfw">
-<title>NAT Firewall Configuration Script</title>
-<screen>
-#!/bin/sh
-echo -e "\n\nLoading NAT firewall.\n"
-IPTABLES=/usr/sbin/iptables
-EXTIF="eth0"
-INTIFA="eth1"
-INTIFB="eth2"
-
-/sbin/depmod -a
-/sbin/modprobe ip_tables
-/sbin/modprobe ip_conntrack
-/sbin/modprobe ip_conntrack_ftp
-/sbin/modprobe iptable_nat
-/sbin/modprobe ip_nat_ftp
-$IPTABLES -P INPUT DROP
-$IPTABLES -F INPUT
-$IPTABLES -P OUTPUT ACCEPT
-$IPTABLES -F OUTPUT
-$IPTABLES -P FORWARD DROP
-$IPTABLES -F FORWARD
-
-$IPTABLES -A INPUT -i lo -j ACCEPT
-$IPTABLES -A INPUT -i $INTIFA -j ACCEPT
-$IPTABLES -A INPUT -i $INTIFB -j ACCEPT
-$IPTABLES -A INPUT -i $EXTIF -m state --state ESTABLISHED,RELATED -j ACCEPT
-# Enable incoming traffic for: SSH, SMTP, DNS(tcp), HTTP, HTTPS
-for i in 22 25 53 80 443
-do
- $IPTABLES -A INPUT -i $EXTIF -p tcp --dport $i -j ACCEPT
-done
-# Allow DNS(udp)
-$IPTABLES -A INPUT -i $EXTIF -p udp -dport 53 -j ACCEPT
-echo "Allow all connections OUT and only existing and specified ones IN"
-$IPTABLES -A FORWARD -i $EXTIF -o $INTIFA -m state \
- --state ESTABLISHED,RELATED -j ACCEPT
-$IPTABLES -A FORWARD -i $EXTIF -o $INTIFB -m state \
- --state ESTABLISHED,RELATED -j ACCEPT
-$IPTABLES -A FORWARD -i $INTIFA -o $EXTIF -j ACCEPT
-$IPTABLES -A FORWARD -i $INTIFB -o $EXTIF -j ACCEPT
-$IPTABLES -A FORWARD -j LOG
-echo " Enabling SNAT (MASQUERADE) functionality on $EXTIF"
-$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
-echo "1" > /proc/sys/net/ipv4/ip_forward
-echo -e "\nNAT firewall done.\n"
-</screen>
-</example>
- </para></step>
-
- <step><para>
- Execute the following to make the script executable:
-<screen>
-&rootprompt; chmod 755 /usr/local/sbin/abmas-natfw.sh
-</screen>
- You must now edit <filename>/etc/rc.d/boot.local</filename> to add an entry
- that runs your <command>abmas-natfw.sh</command> script. The following
- entry works for you:
-<screen>
-#! /bin/sh
-#
-# Copyright (c) 2002 SUSE Linux AG Nuernberg, Germany.
-# All rights reserved.
-#
-# Author: Werner Fink, 1996
-# Burchard Steinbild, 1996
-#
-# /etc/init.d/boot.local
-#
-# script with local commands to be executed from init on system startup
-#
-# Here you should add things that should happen directly after booting
-# before we're going to the first run level.
-#
-/usr/local/sbin/abmas-natfw.sh
-</screen>
- </para></step>
- </procedure>
-
- <para>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- The server is now ready for Samba configuration. During the validation step, you remove
- the entry for the Samba server <constant>diamond</constant> from the <filename>/etc/hosts</filename>
- file. This is done after you are satisfied that DNS-based name resolution is functioning correctly.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Samba Configuration</title>
-
- <para>
- When you have completed this section, the Samba server is ready for testing and validation;
- however, testing and validation have to wait until DHCP, DNS, and printing (CUPS) services have
- been configured.
- </para>
-
- <procedure>
- <title>Samba Configuration Steps</title>
-
- <step><para>
- Install the Samba binary RPM from the Samba-Team FTP site. Assuming that the binary
- RPM file is called <filename>samba-3.0.20-1.i386.rpm</filename>, one way to install this
- file is as follows:
-<screen>
-&rootprompt; rpm -Uvh samba-3.0.20-1.i386.rpm
-</screen>
- This operation must be performed while logged in as the <command>root</command> user.
- Successful operation is clearly indicated. If this installation should fail for any reason,
- refer to the operating system manufacturer's documentation for guidance.
- </para></step>
-
- <step><para>
- Install the &smb.conf; file shown in <link linkend="promisnet"/>, <link linkend="promisnetsvca"/>,
- and <link linkend="promisnetsvcb"/>. Concatenate (join) all three files to make a single &smb.conf;
- file. The final, fully qualified path for this file should be <filename>/etc/samba/smb.conf</filename>.
-
-<example id="promisnet">
-<title>130 User Network with <emphasis>tdbsam</emphasis> &smbmdash; [globals] Section</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">PROMISES</smbconfoption>
-<smbconfoption name="netbios name">DIAMOND</smbconfoption>
-<smbconfoption name="interfaces">eth1, eth2, lo</smbconfoption>
-<smbconfoption name="bind interfaces only">Yes</smbconfoption>
-<smbconfoption name="passdb backend">tdbsam</smbconfoption>
-<smbconfoption name="pam password change">Yes</smbconfoption>
-<smbconfoption name="passwd program">/usr/bin/passwd %u</smbconfoption>
-<smbconfoption name="passwd chat">*New*Password* %n\n *Re-enter*new*password*%n\n *Password*changed*</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="unix password sync">Yes</smbconfoption>
-<smbconfoption name="log level">1</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%m</smbconfoption>
-<smbconfoption name="max log size">50</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="time server">Yes</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
-<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
-<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
-<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
-<smbconfoption name="add user to group script">/usr/sbin/usermod -G '%g' '%u'</smbconfoption>
-<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /tmp '%u'</smbconfoption>
-<smbconfoption name="shutdown script">/var/lib/samba/scripts/shutdown.sh</smbconfoption>
-<smbconfoption name="abort shutdown script">/sbin/shutdown -c</smbconfoption>
-<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
-<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">X:</smbconfoption>
-<smbconfoption name="logon home">\\%L\%U</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="wins support">Yes</smbconfoption>
-<smbconfoption name="utmp">Yes</smbconfoption>
-<smbconfoption name="map acl inherit">Yes</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-<smbconfoption name="cups options">Raw</smbconfoption>
-<smbconfoption name="veto files">/*.eml/*.nws/*.{*}/</smbconfoption>
-<smbconfoption name="veto oplock files">/*.doc/*.xls/*.mdb/</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="promisnetsvca">
-<title>130 User Network with <emphasis>tdbsam</emphasis> &smbmdash; Services Section Part A</title>
-<smbconfblock>
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="default devmode">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network Logon Service</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="locking">No</smbconfoption>
-
-<smbconfsection name="[profiles]"/>
-<smbconfoption name="comment">Profile Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfsection name="[accounts]"/>
-<smbconfoption name="comment">Accounting Files</smbconfoption>
-<smbconfoption name="path">/data/accounts</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="promisnetsvcb">
-<title>130 User Network with <emphasis>tdbsam</emphasis> &smbmdash; Services Section Part B</title>
-<smbconfblock>
-<smbconfsection name="[service]"/>
-<smbconfoption name="comment">Financial Services Files</smbconfoption>
-<smbconfoption name="path">/data/service</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[pidata]"/>
-<smbconfoption name="comment">Property Insurance Files</smbconfoption>
-<smbconfoption name="path">/data/pidata</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[apps]"/>
-<smbconfoption name="comment">Application Files</smbconfoption>
-<smbconfoption name="path">/apps</smbconfoption>
-<smbconfoption name="read only">Yes</smbconfoption>
-<smbconfoption name="admin users">bjordan</smbconfoption>
-</smbconfblock>
-</example>
- </para></step>
-
- <step><para>
- <indexterm><primary>administrator</primary></indexterm><indexterm>
- <primary>smbpasswd</primary>
- </indexterm>
- Add the <constant>root</constant> user to the password backend as follows:
-<screen>
-&rootprompt; smbpasswd -a root
-New SMB password: XXXXXXXX
-Retype new SMB password: XXXXXXXX
-&rootprompt;
-</screen>
- The <constant>root</constant> account is the UNIX equivalent of the Windows Domain Administrator.
- This account is essential in the regular maintenance of your Samba server. It must never be
- deleted. If for any reason the account is deleted, you may not be able to recreate this account
- without considerable trouble.
- </para></step>
-
- <step><para>
- <indexterm><primary>username map</primary></indexterm>
- Create the username map file to permit the <constant>root</constant> account to be called
- <constant>Administrator</constant> from the Windows network environment. To do this, create
- the file <filename>/etc/samba/smbusers</filename> with the following contents:
-<screen>
-####
-# User mapping file
-####
-# File Format
-# -----------
-# Unix_ID = Windows_ID
-#
-# Examples:
-# root = Administrator
-# janes = "Jane Smith"
-# jimbo = Jim Bones
-#
-# Note: If the name contains a space it must be double quoted.
-# In the example above the name 'jimbo' will be mapped to Windows
-# user names 'Jim' and 'Bones' because the space was not quoted.
-#######################################################################
-root = Administrator
-####
-# End of File
-####
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>initGrps.sh</primary></indexterm>
- <indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>add</tertiary></indexterm>
- <indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>modify</tertiary></indexterm>
- <indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
- Create and map Windows Domain Groups to UNIX groups. A sample script is provided in <link linkend="small"/>,
- <link linkend="initGrps"/>. Create a file containing this script. We called ours
- <filename>/etc/samba/initGrps.sh</filename>. Set this file so it can be executed,
- and then execute the script. Sample output should be as follows:
-
-<example id="ch4initGrps">
-<title>Script to Map Windows NT Groups to UNIX Groups</title>
-<indexterm><primary>initGrps.sh</primary></indexterm>
-<screen>
-#!/bin/bash
-#
-# initGrps.sh
-#
-
-# Create UNIX groups
-groupadd acctsdep
-groupadd finsrvcs
-
-# Map Windows Domain Groups to UNIX groups
-net groupmap add ntgroup="Domain Admins" unixgroup=root type=d
-net groupmap add ntgroup="Domain Users" unixgroup=users type=d
-net groupmap add ntgroup="Domain Guests" unixgroup=nobody type=d
-
-# Add Functional Domain Groups
-net groupmap add ntgroup="Accounts Dept" unixgroup=acctsdep type=d
-net groupmap add ntgroup="Financial Services" unixgroup=finsrvcs type=d
-net groupmap add ntgroup="Insurance Group" unixgroup=piops type=d
-
-# Map Windows NT machine local groups to local UNIX groups
-# Mapping of local groups is not necessary and not functional
-# for this installation.
-</screen>
-</example>
-
-<screen>
-&rootprompt; chmod 755 initGrps.sh
-&rootprompt; /etc/samba # ./initGrps.sh
-Updated mapping entry for Domain Admins
-Updated mapping entry for Domain Users
-Updated mapping entry for Domain Guests
-No rid or sid specified, choosing algorithmic mapping
-Successfully added group Accounts Dept to the mapping db
-No rid or sid specified, choosing algorithmic mapping
-Successfully added group Domain Guests to the mapping db
-
-&rootprompt; /etc/samba # net groupmap list | sort
-Account Operators (S-1-5-32-548) -> -1
-Accounts Dept (S-1-5-21-179504-2437109-488451-2003) -> acctsdep
-Administrators (S-1-5-32-544) -> -1
-Backup Operators (S-1-5-32-551) -> -1
-Domain Admins (S-1-5-21-179504-2437109-488451-512) -> root
-Domain Guests (S-1-5-21-179504-2437109-488451-514) -> nobody
-Domain Users (S-1-5-21-179504-2437109-488451-513) -> users
-Financial Services (S-1-5-21-179504-2437109-488451-2005) -> finsrvcs
-Guests (S-1-5-32-546) -> -1
-Power Users (S-1-5-32-547) -> -1
-Print Operators (S-1-5-32-550) -> -1
-Replicators (S-1-5-32-552) -> -1
-System Operators (S-1-5-32-549) -> -1
-Users (S-1-5-32-545) -> -1
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>useradd</primary></indexterm>
- <indexterm><primary>adduser</primary></indexterm>
- <indexterm><primary>passwd</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>password</primary><secondary>backend</secondary></indexterm>
- <indexterm><primary>user</primary><secondary>management</secondary></indexterm>
- There is one preparatory step without which you will not have a working Samba
- network environment. You must add an account for each network user.
- For each user who needs to be given a Windows Domain account, make an entry in the
- <filename>/etc/passwd</filename> file as well as in the Samba password backend.
- Use the system tool of your choice to create the UNIX system account, and use the Samba
- <command>smbpasswd</command> to create a Domain user account.
- There are a number of tools for user management under UNIX, such as
- <command>useradd</command>, and <command>adduser</command>, as well as a plethora of custom
- tools. You also want to create a home directory for each user.
- You can do this by executing the following steps for each user:
-<screen>
-&rootprompt; useradd -m <parameter>username</parameter>
-&rootprompt; passwd <parameter>username</parameter>
-Changing password for <parameter>username</parameter>.
-New password: XXXXXXXX
-Re-enter new password: XXXXXXXX
-Password changed
-&rootprompt; smbpasswd -a <parameter>username</parameter>
-New SMB password: XXXXXXXX
-Retype new SMB password: XXXXXXXX
-Added user <parameter>username</parameter>.
-</screen>
- You do of course use a valid user login ID in place of <parameter>username</parameter>.
- </para></step>
-
- <step><para>
- <indexterm><primary>file system</primary><secondary>access control</secondary></indexterm>
- <indexterm><primary>file system</primary><secondary>permissions</secondary></indexterm>
- <indexterm><primary>group membership</primary></indexterm>
- Using the preferred tool for your UNIX system, add each user to the UNIX groups created
- previously as necessary. File system access control will be based on UNIX group membership.
- </para></step>
-
- <step><para>
- Create the directory mount point for the disk subsystem that can be mounted to provide
- data storage for company files. In this case the mount point is indicated in the &smb.conf;
- file is <filename>/data</filename>. Format the file system as required, and mount the formatted
- file system partition using appropriate system tools.
- </para></step>
-
- <step><para>
- <indexterm><primary>file system</primary><secondary>permissions</secondary></indexterm>
- Create the top-level file storage directories for data and applications as follows:
-<screen>
-&rootprompt; mkdir -p /data/{accounts,finsrvcs}
-&rootprompt; mkdir -p /apps
-&rootprompt; chown -R root:root /data
-&rootprompt; chown -R root:root /apps
-&rootprompt; chown -R bjordan:acctsdep /data/accounts
-&rootprompt; chown -R bjordan:finsrvcs /data/finsrvcs
-&rootprompt; chmod -R ug+rwxs,o-rwx /data
-&rootprompt; chmod -R ug+rwx,o+rx-w /apps
-</screen>
- Each department is responsible for creating its own directory structure within the departmental
- share. The directory root of the <command>accounts</command> share is <filename>/data/accounts</filename>.
- The directory root of the <command>finsvcs</command> share is <filename>/data/finsvcs</filename>.
- The <filename>/apps</filename> directory is the root of the <constant>apps</constant> share
- that provides the application server infrastructure.
- </para></step>
-
- <step><para>
- The &smb.conf; file specifies an infrastructure to support roaming profiles and network
- logon services. You can now create the file system infrastructure to provide the
- locations on disk that these services require. Adequate planning is essential,
- since desktop profiles can grow to be quite large. For planning purposes, a minimum of
- 200 MB of storage should be allowed per user for profile storage. The following
- commands create the directory infrastructure needed:
-<screen>
-&rootprompt; mkdir -p /var/spool/samba
-&rootprompt; mkdir -p /var/lib/samba/{netlogon/scripts,profiles}
-&rootprompt; chown -R root:root /var/spool/samba
-&rootprompt; chown -R root:root /var/lib/samba
-&rootprompt; chmod a+rwxt /var/spool/samba
-&rootprompt; chmod 2775 /var/lib/samba/profiles
-&rootprompt; chgrp users /var/lib/samba/profiles
-</screen>
- For each user account that is created on the system, the following commands should be
- executed:
-<screen>
-&rootprompt; mkdir /var/lib/samba/profiles/'username'
-&rootprompt; chown 'username':users /var/lib/samba/profiles/'username'
-&rootprompt; chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>logon scrip</primary></indexterm>
- <indexterm><primary>unix2dos</primary></indexterm>
- <indexterm><primary>dos2unix</primary></indexterm>
- Create a logon script. It is important that each line is correctly terminated with
- a carriage return and line-feed combination (i.e., DOS encoding). The following procedure
- works if the right tools (<constant>unix2dos</constant> and <constant>dos2unix</constant>) are installed.
- First, create a file called <filename>/var/lib/samba/netlogon/scripts/logon.bat.unix</filename>
- with the following contents:
-<screen>
-net time \\diamond /set /yes
-net use h: /home
-net use p: \\diamond\apps
-</screen>
- Convert the UNIX file to a DOS file using the <command>unix2dos</command> as shown here:
-<screen>
-&rootprompt; unix2dos < /var/lib/samba/netlogon/scripts/logon.bat.unix \
- > /var/lib/samba/netlogon/scripts/logon.bat
-</screen>
- </para></step>
- </procedure>
-
- </sect2>
-
- <sect2 id="ch4dhcpdns">
- <title>Configuration of DHCP and DNS Servers</title>
-
- <para>
- DHCP services are a basic component of the entire network client installation. DNS operation is
- foundational to Internet access as well as to trouble-free operation of local networking. When
- you have completed this section, the server should be ready for solid duty operation.
- </para>
-
- <procedure>
- <title>DHCP and DNS Server Configuration Steps</title>
-
- <step><para>
- <indexterm><primary>/etc/dhcpd.conf</primary></indexterm>
- Create a file called <filename>/etc/dhcpd.conf</filename> with the contents as
- shown in <link linkend="prom-dhcp"/>.
-
-<example id="prom-dhcp">
-<title>DHCP Server Configuration File &smbmdash; <filename>/etc/dhcpd.conf</filename></title>
-<screen>
-# Abmas Accounting Inc.
-default-lease-time 86400;
-max-lease-time 172800;
-default-lease-time 86400;
-option ntp-servers 192.168.1.1;
-option domain-name "abmas.biz";
-option domain-name-servers 192.168.1.1, 192.168.2.1;
-option netbios-name-servers 192.168.1.1, 192.168.2.1;
-option netbios-node-type 8; ### Node type = Hybrid ###
-ddns-updates on; ### Dynamic DNS enabled ###
-ddns-update-style interim;
-
-subnet 192.168.1.0 netmask 255.255.255.0 {
- range dynamic-bootp 192.168.1.128 192.168.1.254;
- option subnet-mask 255.255.255.0;
- option routers 192.168.1.1;
- allow unknown-clients;
- host qmsa {
- hardware ethernet 08:00:46:7a:35:e4;
- fixed-address 192.168.1.20;
- }
- host hplj6a {
- hardware ethernet 00:03:47:cb:81:e0;
- fixed-address 192.168.1.30;
- }
- }
-subnet 192.168.2.0 netmask 255.255.255.0 {
- range dynamic-bootp 192.168.2.128 192.168.2.254;
- option subnet-mask 255.255.255.0;
- option routers 192.168.2.1;
- allow unknown-clients;
- host qmsf {
- hardware ethernet 01:04:31:db:e1:c0;
- fixed-address 192.168.1.20;
- }
- host hplj6f {
- hardware ethernet 00:03:47:cf:83:e2;
- fixed-address 192.168.2.30;
- }
- }
-subnet 127.0.0.0 netmask 255.0.0.0 {
- }
-subnet 123.45.67.64 netmask 255.255.255.252 {
- }
-</screen>
-</example>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/named.conf</primary></indexterm>
- Create a file called <filename>/etc/named.conf</filename> that has the combined contents
- of the <link linkend="ch4namedcfg"/>, <link linkend="ch4namedvarfwd"/>, and
- <link linkend="ch4namedvarrev"/> files that are concatenated (merged) in this
- specific order.
- </para></step>
-
- <step><para>
- Create the files shown in their respective directories as shown in <link linkend="namedrscfiles">DNS
- (named) Resource Files</link>.
-
- <table id="namedrscfiles">
- <title>DNS (named) Resource Files</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry>Reference</entry>
- <entry>File Location</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><link linkend="loopback"/></entry>
- <entry>/var/lib/named/localhost.zone</entry>
- </row>
- <row>
- <entry><link linkend="dnsloopy"/></entry>
- <entry>/var/lib/named/127.0.0.zone</entry>
- </row>
- <row>
- <entry><link linkend="roothint"/></entry>
- <entry>/var/lib/named/root.hint</entry>
- </row>
- <row>
- <entry><link linkend="abmasbiz"/></entry>
- <entry>/var/lib/named/master/abmas.biz.hosts</entry>
- </row>
- <row>
- <entry><link linkend="abmasus"/></entry>
- <entry>/var/lib/named/abmas.us.hosts</entry>
- </row>
- <row>
- <entry><link linkend="eth1zone"/></entry>
- <entry>/var/lib/named/192.168.1.0.rev</entry>
- </row>
- <row>
- <entry><link linkend="eth2zone"/></entry>
- <entry>/var/lib/named/192.168.2.0.rev</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
-<example id="ch4namedcfg">
-<title>DNS Master Configuration File &smbmdash; <filename>/etc/named.conf</filename> Master Section</title>
-<indexterm><primary>/etc/named.conf</primary></indexterm>
-<screen>
-###
-# Abmas Biz DNS Control File
-###
-# Date: November 15, 2003
-###
-options {
- directory "/var/lib/named";
- forwarders {
- 123.45.12.23;
- };
- forward first;
- listen-on {
- mynet;
- };
- auth-nxdomain yes;
- multiple-cnames yes;
- notify no;
-};
-
-zone "." in {
- type hint;
- file "root.hint";
-};
-
-zone "localhost" in {
- type master;
- file "localhost.zone";
-};
-
-zone "0.0.127.in-addr.arpa" in {
- type master;
- file "127.0.0.zone";
-};
-
-acl mynet {
- 192.168.1.0/24;
- 192.168.2.0/24;
- 127.0.0.1;
-};
-
-acl seconddns {
- 123.45.54.32;
-};
-
-</screen>
-</example>
-
-<example id="ch4namedvarfwd">
-<title>DNS Master Configuration File &smbmdash; <filename>/etc/named.conf</filename> Forward Lookup Definition Section</title>
-<screen>
-zone "abmas.biz" {
- type master;
- file "/var/lib/named/master/abmas.biz.hosts";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-
-zone "abmas.us" {
- type master;
- file "/var/lib/named/master/abmas.us.hosts";
- allow-query {
- any;
- };
- allow-transfer {
- seconddns;
- };
-};
-</screen>
-</example>
-
-<example id="ch4namedvarrev">
-<title>DNS Master Configuration File &smbmdash; <filename>/etc/named.conf</filename> Reverse Lookup Definition Section</title>
-<screen>
-zone "1.168.192.in-addr.arpa" {
- type master;
- file "/var/lib/named/master/192.168.1.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-
-zone "2.168.192.in-addr.arpa" {
- type master;
- file "/var/lib/named/master/192.168.2.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-</screen>
-</example>
-
-<example id="eth1zone">
-<title>DNS 192.168.1 Reverse Zone File</title>
-<screen>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-1.168.192.in-addr.arpa IN SOA sleeth.abmas.biz. root.abmas.biz. (
- 2003021825 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS sleeth1.abmas.biz.
-$ORIGIN 1.168.192.in-addr.arpa.
-1 PTR sleeth1.abmas.biz.
-20 PTR qmsa.abmas.biz.
-30 PTR hplj6a.abmas.biz.
-</screen>
-</example>
-
-<example id="eth2zone">
-<title>DNS 192.168.2 Reverse Zone File</title>
-<screen>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-2.168.192.in-addr.arpa IN SOA sleeth.abmas.biz. root.abmas.biz. (
- 2003021825 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS sleeth2.abmas.biz.
-$ORIGIN 2.168.192.in-addr.arpa.
-1 PTR sleeth2.abmas.biz.
-20 PTR qmsf.abmas.biz.
-30 PTR hplj6f.abmas.biz.
-</screen>
-</example>
-
-<example id="abmasbiz">
-<title>DNS Abmas.biz Forward Zone File</title>
-<screen>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-abmas.biz IN SOA sleeth1.abmas.biz. root.abmas.biz. (
- 2003021833 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS dns.abmas.biz.
- MX 10 mail.abmas.biz.
-$ORIGIN abmas.biz.
-sleeth1 A 192.168.1.1
-sleeth2 A 192.168.2.1
-qmsa A 192.168.1.20
-hplj6a A 192.168.1.30
-qmsf A 192.168.2.20
-hplj6f A 192.168.2.30
-dns CNAME sleeth1
-diamond CNAME sleeth1
-mail CNAME sleeth1
-</screen>
-</example>
-
-<example id="abmasus">
-<title>DNS Abmas.us Forward Zone File</title>
-<screen>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-abmas.us IN SOA server.abmas.us. root.abmas.us. (
- 2003021833 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS dns.abmas.us.
- NS dns2.abmas.us.
- MX 10 mail.abmas.us.
-$ORIGIN abmas.us.
-server A 123.45.67.66
-dns2 A 123.45.54.32
-gw A 123.45.67.65
-www CNAME server
-mail CNAME server
-dns CNAME server
-</screen>
-</example>
-
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/resolv.conf</primary></indexterm><indexterm>
- <primary>name resolution</primary>
- </indexterm>
- All DNS name resolution should be handled locally. To ensure that the server is configured
- correctly to handle this, edit <filename>/etc/resolv.conf</filename> to have the following
- content:
-<screen>
-search abmas.us abmas.biz
-nameserver 127.0.0.1
-nameserver 123.45.54.23
-</screen>
- <indexterm>
- <primary>DNS server</primary>
- </indexterm>
- This instructs the name resolver function (when configured correctly) to ask the DNS server
- that is running locally to resolve names to addresses. In the event that the local name server
- is not available, ask the name server provided by the ISP. The latter, of course, does not resolve
- purely local names to IP addresses.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The final step is to edit the <filename>/etc/nsswitch.conf</filename> file.
- This file controls the operation of the various resolver libraries that are part of the Linux
- Glibc libraries. Edit this file so that it contains the following entries:
-<screen>
-hosts: files dns wins
-</screen>
- </para></step>
- </procedure>
-
- <para>
- The basic DHCP and DNS services are now ready for validation testing. Before you can proceed,
- there are a few more steps along the road. First, configure the print spooling and print
- processing system. Then you can configure the server so that all services
- start automatically on reboot. You must also manually start all services prior to validation testing.
- </para>
-
- </sect2>
-
- <sect2 id="ch4ptrcfg">
- <title>Printer Configuration</title>
-
- <para>
- Network administrators who are new to CUPS based-printing typically experience some difficulty mastering
- its powerful features. The steps outlined in this section are designed to navigate around the distractions
- of learning CUPS. Instead of implementing smart features and capabilities, our approach is to use it as a
- transparent print queue that performs no filtering, and only minimal handling of each print job that is
- submitted to it. In other words, our configuration turns CUPS into a raw-mode print queue. This means that
- the correct printer driver must be installed on all clients.
- </para>
-
- <procedure>
- <title>Printer Configuration Steps</title>
-
- <step><para>
- Configure each printer to be a DHCP client, carefully following the manufacturer's guidelines.
- </para></step>
-
- <step><para>
- Follow the instructions in the printer manufacturer's manuals to permit printing to port 9100.
- Use any other port the manufacturer specifies for direct-mode raw printing, and adjust the
- port as necessary in the following example commands.
- This allows the CUPS spooler to print using raw mode protocols.
- <indexterm><primary>CUPS</primary></indexterm>
- <indexterm><primary>raw printing</primary></indexterm>
- </para></step>
-
- <step><para>
- <indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm><indexterm>
- <primary>lpadmin</primary>
- </indexterm>
- Configure the CUPS Print Queues as follows:
-<screen>
-&rootprompt; lpadmin -p qmsa -v socket://qmsa.abmas.biz:9100 -E
-&rootprompt; lpadmin -p hplj6a -v socket://hplj6a.abmas.biz:9100 -E
-&rootprompt; lpadmin -p qmsf -v socket://qmsf.abmas.biz:9100 -E
-&rootprompt; lpadmin -p hplj6f -v socket://hplj6f.abmas.biz:9100 -E
-</screen>
- <indexterm><primary>print filter</primary></indexterm>
- This creates the necessary print queues with no assigned print filter.
- </para></step>
-
- <step><para><indexterm>
- <primary>enable</primary>
- </indexterm>
- Print queues may not be enabled at creation. Use <command>lpc stat</command> to check
- the status of the print queues and, if necessary, make certain that the queues you have
- just created are enabled by executing the following:
-<screen>
-&rootprompt; /usr/bin/enable qmsa
-&rootprompt; /usr/bin/enable hplj6a
-&rootprompt; /usr/bin/enable qmsf
-&rootprompt; /usr/bin/enable hplj6f
-</screen>
- </para></step>
-
- <step><para><indexterm>
- <primary>accept</primary>
- </indexterm>
- Even though your print queues may be enabled, it is still possible that they
- are not accepting print jobs. A print queue services incoming printing
- requests only when configured to do so. Ensure that your print queues are
- set to accept incoming jobs by executing the following commands:
-<screen>
-&rootprompt; /usr/sbin/accept qmsa
-&rootprompt; /usr/sbin/accept hplj6a
-&rootprompt; /usr/sbin/accept qmsf
-&rootprompt; /usr/sbin/accept hplj6f
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>mime type</primary></indexterm>
- <indexterm><primary>/etc/mime.convs</primary></indexterm>
- <indexterm><primary>application/octet-stream</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
-<screen>
-application/octet-stream application/vnd.cups-raw 0 -
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/mime.types</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
-<screen>
-application/octet-stream
-</screen>
- </para></step>
-
- <step><para>
- Printing drivers are installed on each network client workstation.
- </para></step>
- </procedure>
-
- <para>
- Note: If the parameter <parameter>cups options = Raw</parameter> is specified in the &smb.conf; file,
- the last two steps can be omitted with CUPS version 1.1.18, or later.
- </para>
-
- <para>
- The UNIX system print queues have been configured and are ready for validation testing.
- </para>
-
- </sect2>
-
- <sect2 id="procstart">
- <title>Process Startup Configuration</title>
-
- <para>
- <indexterm><primary>chkconfig</primary></indexterm>
- There are two essential steps to process startup configuration. First, the process
- must be configured so that it automatically restarts each time the server
- is rebooted. This step involves use of the <command>chkconfig</command> tool that
- creates the appropriate symbolic links from the master daemon control file that is
- located in the <filename>/etc/rc.d</filename> directory, to the <filename>/etc/rc'x'.d</filename>
- directories. Links are created so that when the system run level is changed, the
- necessary start or kill script is run.
- </para>
-
- <para>
- <indexterm><primary>/etc/xinetd.d</primary></indexterm>
- <indexterm><primary>inetd</primary></indexterm>
- <indexterm><primary>xinetd</primary></indexterm>
- <indexterm><primary>chkconfig</primary></indexterm>
- <indexterm><primary>super daemon</primary></indexterm>
- In the event that a service is not run as a daemon, but via the internetworking
- super daemon (<command>inetd</command> or <command>xinetd</command>), then the <command>chkconfig</command>
- tool makes the necessary entries in the <filename>/etc/xinetd.d</filename> directory
- and sends a hang-up (HUP) signal to the the super daemon, thus forcing it to
- re-read its control files.
- </para>
-
- <para>
- Last, each service must be started to permit system validation to proceed.
- </para>
-
- <procedure>
- <step><para>
- Use the standard system tool to configure each service to restart
- automatically at every system reboot. For example,
- <indexterm><primary>chkconfig</primary></indexterm>
-<screen>
-&rootprompt; chkconfig dhpcd on
-&rootprompt; chkconfig named on
-&rootprompt; chkconfig cups on
-&rootprompt; chkconfig smb on
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>starting dhcpd</primary></indexterm>
- <indexterm><primary>starting samba</primary></indexterm>
- <indexterm><primary>starting CUPS</primary></indexterm>
- Now start each service to permit the system to be validated.
- Execute each of the following in the sequence shown:
-
-<screen>
-&rootprompt; /etc/rc.d/init.d/dhcpd restart
-&rootprompt; /etc/rc.d/init.d/named restart
-&rootprompt; /etc/rc.d/init.d/cups restart
-&rootprompt; /etc/rc.d/init.d/smb restart
-</screen>
- </para></step>
- </procedure>
-
- </sect2>
-
- <sect2 id="ch4valid">
- <title>Validation</title>
-
- <para>
- <indexterm><primary>validation</primary></indexterm>
- Complex networking problems are most often caused by simple things that are poorly or incorrectly
- configured. The validation process adopted here should be followed carefully; it is the result of the
- experience gained from years of making and correcting the most common mistakes. Shortcuts often lead to basic errors. You should
- refrain from taking shortcuts, from making basic assumptions, and from not exercising due process
- and diligence in network validation. By thoroughly testing and validating every step in the process
- of network installation and configuration, you can save yourself from sleepless nights and restless
- days. A well debugged network is a foundation for happy network users and network administrators.
- Later in this book you learn how to make users happier. For now, it is enough to learn to
- validate. Let's get on with it.
- </para>
-
- <procedure>
- <title>Server Validation Steps</title>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- One of the most important facets of Samba configuration is to ensure that
- name resolution functions correctly. You can check name resolution
- with a few simple tests. The most basic name resolution is provided from the
- <filename>/etc/hosts</filename> file. To test its operation, make a
- temporary edit to the <filename>/etc/nsswitch.conf</filename> file. Using
- your favorite editor, change the entry for <constant>hosts</constant> to read:
-<screen>
-hosts: files
-</screen>
- When you have saved this file, execute the following command:
-<screen>
-&rootprompt; ping diamond
-PING sleeth1.abmas.biz (192.168.1.1) 56(84) bytes of data.
-64 bytes from sleeth1 (192.168.1.1): icmp_seq=1 ttl=64 time=0.131 ms
-64 bytes from sleeth1 (192.168.1.1): icmp_seq=2 ttl=64 time=0.179 ms
-64 bytes from sleeth1 (192.168.1.1): icmp_seq=3 ttl=64 time=0.192 ms
-64 bytes from sleeth1 (192.168.1.1): icmp_seq=4 ttl=64 time=0.191 ms
-
---- sleeth1.abmas.biz ping statistics ---
-4 packets transmitted, 4 received, 0% packet loss, time 3016ms
-rtt min/avg/max/mdev = 0.131/0.173/0.192/0.026 ms
-</screen>
- This proves that name resolution via the <filename>/etc/hosts</filename> file
- is working.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- So far, your installation is going particularly well. In this step we validate
- DNS server and name resolution operation. Using your favorite UNIX system editor,
- change the <filename>/etc/nsswitch.conf</filename> file so that the
- <constant>hosts</constant> entry reads:
-<screen>
-hosts: dns
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>named</primary></indexterm>
- Before you test DNS operation, it is a good idea to verify that the DNS server
- is running by executing the following:
-<screen>
-&rootprompt; ps ax | grep named
- 437 ? S 0:00 /sbin/syslogd -a /var/lib/named/dev/log
- 524 ? S 0:00 /usr/sbin/named -t /var/lib/named -u named
- 525 ? S 0:00 /usr/sbin/named -t /var/lib/named -u named
- 526 ? S 0:00 /usr/sbin/named -t /var/lib/named -u named
- 529 ? S 0:00 /usr/sbin/named -t /var/lib/named -u named
- 540 ? S 0:00 /usr/sbin/named -t /var/lib/named -u named
- 2552 pts/2 S 0:00 grep named
-</screen>
- This means that we are ready to check DNS operation. Do so by executing:
- <indexterm><primary>ping</primary></indexterm>
-<screen>
-&rootprompt; ping diamond
-PING sleeth1.abmas.biz (192.168.1.1) 56(84) bytes of data.
-64 bytes from sleeth1 (192.168.1.1): icmp_seq=1 ttl=64 time=0.156 ms
-64 bytes from sleeth1 (192.168.1.1): icmp_seq=2 ttl=64 time=0.183 ms
-
---- sleeth1.abmas.biz ping statistics ---
-2 packets transmitted, 2 received, 0% packet loss, time 999ms
-rtt min/avg/max/mdev = 0.156/0.169/0.183/0.018 ms
-</screen>
- You should take a few more steps to validate DNS server operation, as follows:
-<screen>
-&rootprompt; host -f diamond.abmas.biz
-sleeth1.abmas.biz has address 192.168.1.1
-</screen>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- You may now remove the entry called <constant>diamond</constant> from the
- <filename>/etc/hosts</filename> file. It does not hurt to leave it there,
- but its removal reduces the number of administrative steps for this name.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- WINS is a great way to resolve NetBIOS names to their IP address. You can test
- the operation of WINS by starting <command>nmbd</command> (manually or by way
- of the Samba startup method shown in <link linkend="procstart"/>). You must edit
- the <filename>/etc/nsswitch.conf</filename> file so that the <constant>hosts</constant>
- entry is as follows:
-<screen>
-hosts: wins
-</screen>
- The next step is to make certain that Samba is running using <command>ps ax | grep mbd</command>.
- The <command>nmbd</command> daemon will provide the WINS name resolution service when the
- &smb.conf; file <smbconfsection name="global"/> parameter <smbconfoption name="wins
- support">Yes</smbconfoption> has been specified. Having validated that Samba is operational,
- excute the following:
-<screen>
-&rootprompt; ping diamond
-PING diamond (192.168.1.1) 56(84) bytes of data.
-64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.094 ms
-64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.479 ms
-</screen>
- <indexterm><primary>ping</primary></indexterm>
- Now that you can relax with the knowledge that all three major forms of name
- resolution to IP address resolution are working, edit the <filename>/etc/nsswitch.conf</filename>
- again. This time you add all three forms of name resolution to this file.
- Your edited entry for <constant>hosts</constant> should now look like this:
-<screen>
-hosts: files dns wins
-</screen>
- The system is looking good. Let's move on.
- </para></step>
-
- <step><para>
- It would give you peace of mind to know that the DHCP server is running
- and available for service. You can validate DHCP services by running:
-
-<screen>
-&rootprompt; ps ax | grep dhcp
- 2618 ? S 0:00 /usr/sbin/dhcpd ...
- 8180 pts/2 S 0:00 grep dhcp
-</screen>
- This shows that the server is running. The proof of whether or not it is working
- comes when you try to add the first DHCP client to the network.
- </para></step>
-
- <step><para>
- <indexterm><primary>testparm</primary></indexterm>
- This is a good point at which to start validating Samba operation. You are
- content that name resolution is working for basic TCP/IP needs. Let's move on.
- If your &smb.conf; file has bogus options or parameters, this may cause Samba
- to refuse to start. The first step should always be to validate the contents
- of this file by running:
-<screen>
-&rootprompt; testparm -s
-Load smb config files from smb.conf
-Processing section "[homes]"
-Processing section "[printers]"
-Processing section "[netlogon]"
-Processing section "[profiles]"
-Processing section "[accounts]"
-Processing section "[service]"
-Processing section "[apps]"
-Loaded services file OK.
-# Global parameters
-[global]
- workgroup = PROMISES
- netbios name = DIAMOND
- interfaces = eth1, eth2, lo
- bind interfaces only = Yes
- passdb backend = tdbsam
- pam password change = Yes
- passwd program = /usr/bin/passwd '%u'
- passwd chat = *New*Password* %n\n \
- *Re-enter*new*password* %n\n *Password*changed*
- username map = /etc/samba/smbusers
- unix password sync = Yes
- log level = 1
- syslog = 0
- log file = /var/log/samba/%m
- max log size = 50
- smb ports = 139
- name resolve order = wins bcast hosts
- time server = Yes
- printcap name = CUPS
- show add printer wizard = No
- add user script = /usr/sbin/useradd -m '%u'
- delete user script = /usr/sbin/userdel -r '%u'
- add group script = /usr/sbin/groupadd '%g'
- delete group script = /usr/sbin/groupdel '%g'
- add user to group script = /usr/sbin/usermod -G '%g' '%u'
- add machine script = /usr/sbin/useradd \
- -s /bin/false -d /dev/null '%u'
- shutdown script = /var/lib/samba/scripts/shutdown.sh
- abort shutdown script = /sbin/shutdown -c
- logon script = scripts\logon.bat
- logon path = \\%L\profiles\%U
- logon drive = X:
- logon home = \\%L\%U
- domain logons = Yes
- preferred master = Yes
- wins support = Yes
- utmp = Yes
- winbind use default domain = Yes
- map acl inherit = Yes
- cups options = Raw
- veto files = /*.eml/*.nws/*.{*}/
- veto oplock files = /*.doc/*.xls/*.mdb/
-
-[homes]
- comment = Home Directories
- valid users = %S
- read only = No
- browseable = No
-...
-### Remainder cut to save space ###
-</screen>
- Clear away all errors before proceeding.
- </para></step>
-
- <step><para>
- <indexterm><primary>check samba daemons</primary></indexterm>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- Check that the Samba server is running:
-<screen>
-&rootprompt; ps ax | grep mbd
-14244 ? S 0:00 /usr/sbin/nmbd -D
-14245 ? S 0:00 /usr/sbin/nmbd -D
-14290 ? S 0:00 /usr/sbin/smbd -D
-
-$rootprompt; ps ax | grep winbind
-14293 ? S 0:00 /usr/sbin/winbindd -D
-14295 ? S 0:00 /usr/sbin/winbindd -D
-</screen>
- The <command>winbindd</command> daemon is running in split mode (normal), so there are also
- two instances<footnote><para>For more information regarding winbindd, see <emphasis>TOSHARG2</emphasis>,
- Chapter 23, Section 23.3. The single instance of <command>smbd</command> is normal. One additional
- <command>smbd</command> slave process is spawned for each SMB/CIFS client
- connection.</para></footnote> of it.
- </para></step>
-
- <step><para>
- <indexterm><primary>anonymous
- connection</primary></indexterm>
- <indexterm>
- <primary>smbclient</primary>
- </indexterm>
- Check that an anonymous connection can be made to the Samba server:
-<screen>
-&rootprompt; smbclient -L localhost -U%
-
- Sharename Type Comment
- --------- ---- -------
- IPC$ IPC IPC Service (Samba 3.0.20)
- netlogon Disk Network Logon Service
- profiles Disk Profile Share
- accounts Disk Accounting Files
- service Disk Financial Services Files
- apps Disk Application Files
- ADMIN$ IPC IPC Service (Samba 3.0.20)
- hplj6a Printer hplj6a
- hplj6f Printer hplj6f
- qmsa Printer qmsa
- qmsf Printer qmsf
-
- Server Comment
- --------- -------
- DIAMOND Samba 3.0.20
-
- Workgroup Master
- --------- -------
- PROMISES DIAMOND
-</screen>
- This demonstrates that an anonymous listing of shares can be obtained. This is the equivalent
- of browsing the server from a Windows client to obtain a list of shares on the server.
- The <constant>-U%</constant> argument means to send a <constant>NULL</constant> username and
- a <constant>NULL</constant> password.
- </para></step>
-
- <step><para>
- <indexterm><primary>dhcp client validation</primary></indexterm>
- <indexterm><primary>printer validation</primary></indexterm>
- <indexterm><primary>arp</primary></indexterm>
- Verify that each printer has the IP address assigned in the DHCP server configuration file.
- The easiest way to do this is to ping the printer name. Immediately after the ping response
- has been received, execute <command>arp -a</command> to find the MAC address of the printer
- that has responded. Now you can compare the IP address and the MAC address of the printer
- with the configuration information in the <filename>/etc/dhcpd.conf</filename> file. They
- should, of course, match. For example,
-<screen>
-&rootprompt; ping hplj6
-PING hplj6a (192.168.1.30) 56(84) bytes of data.
-64 bytes from hplj6a (192.168.1.30): icmp_seq=1 ttl=64 time=0.113 ms
-
-&rootprompt; arp -a
-hplj6a (192.168.1.30) at 00:03:47:CB:81:E0 [ether] on eth0
-</screen>
- <indexterm>
- <primary>/etc/dhcpd.conf</primary>
- </indexterm>
- The MAC address <constant>00:03:47:CB:81:E0</constant> matches that specified for the
- IP address from which the printer has responded and with the entry for it in the
- <filename>/etc/dhcpd.conf</filename> file. Repeat this for each printer configured.
- </para></step>
-
- <step><para>
- <indexterm><primary>authenticated connection</primary></indexterm>
- Make an authenticated connection to the server using the <command>smbclient</command> tool:
-<screen>
-&rootprompt; smbclient //diamond/accounts -U gholmes
-Password: XXXXXXX
-smb: \> dir
- . D 0 Thu Nov 27 15:07:09 2003
- .. D 0 Sat Nov 15 17:40:50 2003
- zakadmin.exe 161424 Thu Nov 27 15:06:52 2003
- zak.exe 6066384 Thu Nov 27 15:06:52 2003
- dhcpd.conf 1256 Thu Nov 27 15:06:52 2003
- smb.conf 2131 Thu Nov 27 15:06:52 2003
- initGrps.sh A 1089 Thu Nov 27 15:06:52 2003
- POLICY.EXE 86542 Thu Nov 27 15:06:52 2003
-
- 55974 blocks of size 65536. 33968 blocks available
-smb: \> q
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>nmap</primary></indexterm>
- Your new server is connected to an Internet-accessible connection. Before you start
- your firewall, you should run a port scanner against your system. You should repeat that
- after the firewall has been started. This helps you understand to what extent the
- server may be vulnerable to external attack. One way you can do this is by using an
- external service, such as the <ulink url="http://www.dslreports.com/scan">DSL Reports</ulink>
- tools. Alternately, if you can gain root-level access to a remote
- UNIX/Linux system that has the <command>nmap</command> tool, you can run the following:
-<screen>
-&rootprompt; nmap -v -sT server.abmas.us
-
-Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
-Host server.abmas.us (123.45.67.66) appears to be up ... good.
-Initiating Connect() Scan against server.abmas.us (123.45.67.66)
-Adding open port 6000/tcp
-Adding open port 873/tcp
-Adding open port 445/tcp
-Adding open port 10000/tcp
-Adding open port 901/tcp
-Adding open port 631/tcp
-Adding open port 25/tcp
-Adding open port 111/tcp
-Adding open port 32770/tcp
-Adding open port 3128/tcp
-Adding open port 53/tcp
-Adding open port 80/tcp
-Adding open port 443/tcp
-Adding open port 139/tcp
-Adding open port 22/tcp
-The Connect() Scan took 0 seconds to scan 1601 ports.
-Interesting ports on server.abmas.us (123.45.67.66):
-(The 1587 ports scanned but not shown below are in state: closed)
-Port State Service
-22/tcp open ssh
-25/tcp open smtp
-53/tcp open domain
-80/tcp open http
-111/tcp open sunrpc
-139/tcp open netbios-ssn
-443/tcp open https
-445/tcp open microsoft-ds
-631/tcp open ipp
-873/tcp open rsync
-901/tcp open samba-swat
-3128/tcp open squid-http
-6000/tcp open X11
-10000/tcp open snet-sensor-mgmt
-32770/tcp open sometimes-rpc3
-
-Nmap run completed -- 1 IP address (1 host up) scanned in 1 second
-</screen>
- The above scan was run before the external interface was locked down with the NAT-firewall
- script you created above. The following results are obtained after the firewall rules
- have been put into place:
-<screen>
-&rootprompt; nmap -v -sT server.abmas.us
-
-Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
-Host server.abmas.us (123.45.67.66) appears to be up ... good.
-Initiating Connect() Scan against server.abmas.us (123.45.67.66)
-Adding open port 53/tcp
-Adding open port 22/tcp
-The Connect() Scan took 168 seconds to scan 1601 ports.
-Interesting ports on server.abmas.us (123.45.67.66):
-(The 1593 ports scanned but not shown below are in state: filtered)
-Port State Service
-22/tcp open ssh
-25/tcp closed smtp
-53/tcp open domain
-80/tcp closed http
-443/tcp closed https
-
-Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds
-</screen>
- </para></step>
-
- </procedure>
-
- </sect2>
-
- <sect2 id="ch4appscfg">
- <title>Application Share Configuration</title>
-
- <para>
- <indexterm><primary>application server</primary></indexterm>
- <indexterm><primary>administrative installation</primary></indexterm>
- The use of an application server is a key mechanism by which desktop administration overheads
- can be reduced. Check the application manual for your software to identify how best to
- create an administrative installation.
- </para>
-
- <para>
- Some Windows software will only run locally on the desktop computer. Such software
- is typically not suited for administrative installation. Administratively installed software
- permits one or more of the following installation choices:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Install software fully onto a workstation, storing data files on the same workstation.
- </para></listitem>
-
- <listitem><para>
- Install software fully onto a workstation with central network data file storage.
- </para></listitem>
-
- <listitem><para>
- Install software to run off a central application server with data files stored
- on the local workstation. This is often called a minimum installation, or a
- network client installation.
- </para></listitem>
-
- <listitem><para>
- Install software to run off a central application server with data files stored
- on a central network share. This type of installation often prevents storage
- of work files on the local workstation.
- </para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary></primary></indexterm>
- A common application deployed in this environment is an office suite.
- Enterprise editions of Microsoft Office XP Professional can be administratively installed
- by launching the installation from a command shell. The command that achieves this is
- <command>setup /a</command>. It results in a set of prompts through which various
- installation choices can be made. Refer to the Microsoft Office Resource SDK and Resource
- Kit for more information regarding this mode of installation of MS Office XP Professional.
- The full administrative installation of MS Office XP Professional requires approximately
- 650 MB of disk space.
- </para>
-
- <para>
- When the MS Office XP Professional product has been installed to the administrative network
- share, the product can be installed onto a workstation by executing the normal setup program.
- The installation process now provides a choice to either perform a minimum installation
- or a full local installation. A full local installation takes over 100 MB of disk space.
- A network workstation (minimum) installation requires typically 10 MB to 15 MB of
- local disk space. In the latter case, when the applications are used, they load over the network.
- </para>
-
- <para>
- <indexterm><primary>Service Packs</primary></indexterm>
- <indexterm><primary>Microsoft Office</primary></indexterm>
- Microsoft Office Service Packs can be unpacked to update an administrative share. This makes
- it possible to update MS Office XP Professional for all users from a single installation
- of the service pack and generally circumvents the need to run updates on each network
- Windows client.
- </para>
-
- <para>
- The default location for MS Office XP Professional data files can be set through registry
- editing or by way of configuration options inside each Office XP Professional application.
- </para>
-
- <para>
- <indexterm><primary>OpenOffice</primary></indexterm>
- OpenOffice.Org OpenOffice Version 1.1.0 can be installed locally. It can also
- be installed to run off a network share. The latter is a most desirable solution for office-bound
- network users and for administrative staff alike. It permits quick and easy updates
- to be rolled out to all users with a minimum of disruption and with maximum flexibility.
- </para>
-
- <para>
- The process for installation of administrative shared OpenOffice involves download of the
- distribution ZIP file, followed by extraction of the ZIP file into a temporary disk area.
- When fully extracted using the unzipping tool of your choosing, change into the Windows
- installation files directory then execute <command>setup -net</command>. You are
- prompted on screen for the target installation location. This is the administrative
- share point. The full administrative OpenOffice share takes approximately 150 MB of disk
- space.
- </para>
-
- <sect3>
- <title>Comments Regarding Software Terms of Use</title>
- <para>
- Many single-user products can be installed into an administrative share, but
- personal versions of products such as Microsoft Office XP Professional do not permit this.
- Many people do not like terms of use typical with commercial products, so a few comments
- regarding software licensing seem important.
- </para>
-
- <para>
- Please do not use an administrative installation of proprietary and commercially licensed
- software products to violate the copyright holders' property. All software is licensed,
- particularly software that is licensed for use free of charge. All software is the property
- of the copyright holder unless the author and/or copyright holder has explicitly disavowed
- ownership and has placed the software into the public domain.
- </para>
-
- <para>
- Software that is under the GNU General Public License, like proprietary software, is
- licensed in a way that restricts use. For example, if you modify GPL software and then
- distribute the binary version of your modifications, you must offer to provide the source
- code as well. This restriction is designed to maintain the momentum
- of the diffusion of technology and to protect against the withholding of innovations.
- </para>
-
- <para>
- Commercial and proprietary software generally restrict use to those who have paid the
- license fees and who comply with the licensee's terms of use. Software that is released
- under the GNU General Public License is restricted to particular terms and conditions
- also. Whatever the licensing terms may be, if you do not approve of the terms of use,
- please do not use the software.
- </para>
-
- <para>
- <indexterm><primary>GPL</primary></indexterm>
- Samba is provided under the terms of the GNU
- GPL Version 3, a copy of which is provided
- with the source code.
- </para>
- </sect3>
-
- </sect2>
-
- <sect2 id="ch4wincfg">
- <title>Windows Client Configuration</title>
-
- <para>
- Christine needs to roll out 130 new desktop systems. There is no doubt that she also needs
- to reinstall many of the notebook computers that will be recycled for use with the new network
- configuration. The smartest way to handle the challenge of the roll-out program is to build
- a staged system for each type of target machine, and then use an image replication tool such as Norton
- Ghost (enterprise edition) to replicate the staged machine to its target desktops. The same can
- be done with notebook computers as long as they are identical or sufficiently similar.
- </para>
-
- <procedure id="sbewinclntprep">
- <title>Windows Client Configuration Procedure</title>
-
- <step><para>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>DHCP</primary></indexterm>
- Install MS Windows XP Professional. During installation, configure the client to use DHCP for
- TCP/IP protocol configuration. DHCP configures all Windows clients to use the WINS Server
- address that has been defined for the local subnet.
- </para></step>
-
- <step><para>
- Join the Windows Domain <constant>PROMISES</constant>. Use the Domain Administrator
- username <constant>root</constant> and the SMB password you assigned to this account.
- A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to
- a Windows Domain is given in <link linkend="appendix"/>, <link linkend="domjoin"/>.
- Reboot the machine as prompted and then log on using the Domain Administrator account
- (<constant>root</constant>).
- </para></step>
-
- <step><para>
- Verify <constant>DIAMOND</constant> is visible in <guimenu>My Network Places</guimenu>,
- that it is possible to connect to it and see the shares <guimenuitem>accounts</guimenuitem>,
- <guimenuitem>apps</guimenuitem>, and <guimenuitem>finsvcs</guimenuitem>, and that it is
- possible to open each share to reveal its contents.
- </para></step>
-
- <step><para>
- Create a drive mapping to the <constant>apps</constant> share on the server <constant>DIAMOND</constant>.
- </para></step>
-
- <step><para>
- Perform an administrative installation of each application to be used. Select the options
- that you wish to use. Of course, you can choose to run applications over the network, correct?
- </para></step>
-
- <step><para>
- Now install all applications to be installed locally. Typical tools include Adobe Acrobat,
- NTP-based time synchronization software, drivers for specific local devices such as fingerprint
- scanners, and the like. Probably the most significant application for local installation
- is antivirus software.
- </para></step>
-
- <step><para>
- Now install all four printers onto the staging system. The printers you install
- include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers. You will
- also configure identical printers that are located in the financial services department.
- Install printers on each machine following the steps shown in the Windows client printer
- preparation procedure below.
- </para></step>
-
- <step><para>
- <indexterm><primary>defragmentation</primary></indexterm>
- When you are satisfied that the staging systems are complete, use the appropriate procedure to
- remove the client from the domain. Reboot the system and then log on as the local administrator
- and clean out all temporary files stored on the system. Before shutting down, use the disk
- defragmentation tool so that the file system is in optimal condition before replication.
- </para></step>
-
- <step><para>
- Boot the workstation using the Norton (Symantec) Ghosting diskette (or CD-ROM) and image the
- machine to a network share on the server.
- </para></step>
-
- <step><para>
- <indexterm><primary>Windows security identifier</primary><see>SID</see></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- You may now replicate the image to the target machines using the appropriate Norton Ghost
- procedure. Make sure to use the procedure that ensures each machine has a unique
- Windows security identifier (SID). When the installation of the disk image has completed, boot the PC.
- </para></step>
-
- <step><para>
- Log on to the machine as the local Administrator (the only option), and join the machine to
- the Domain, following the procedure set out in <link linkend="appendix"/>, <link linkend="domjoin"/>. The system is now
- ready for the user to log on, provided you have created a network logon account for that
- user, of course.
- </para></step>
-
- <step><para>
- Instruct all users to log on to the workstation using their assigned username and password.
- </para></step>
- </procedure>
-
- <procedure id="sbewinclntptrprep">
- <title>Windows Client Printer Preparation Procedure</title>
-
- <step><para>
- Click <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Settings</guimenuitem>
- <guimenuitem>Printers</guimenuitem>
- <guiicon>Add Printer</guiicon>
- <guibutton>Next</guibutton>
- </menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
- Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
- </para></step>
-
- <step><para>
- Click <guibutton>Next</guibutton>. In the
- <guimenuitem>Manufacturer:</guimenuitem> panel, select <constant>HP</constant>.
- In the <guimenuitem>Printers:</guimenuitem> panel, select the printer called
- <constant>HP LaserJet 6</constant>. Click <guibutton>Next</guibutton>.
- </para></step>
-
- <step><para>
- In the <guimenuitem>Available ports:</guimenuitem> panel, select
- <constant>FILE:</constant>. Accept the default printer name by clicking
- <guibutton>Next</guibutton>. When asked, <quote>Would you like to print a
- test page?,</quote> click <guimenuitem>No</guimenuitem>. Click
- <guibutton>Finish</guibutton>.
- </para></step>
-
- <step><para>
- You may be prompted for the name of a file to print to. If so, close the
- dialog panel. Right-click <menuchoice>
- <guiicon>HP LaserJet 6</guiicon>
- <guimenuitem>Properties</guimenuitem>
- <guisubmenu>Details (Tab)</guisubmenu>
- <guimenuitem>Add Port</guimenuitem>
- </menuchoice>.
- </para></step>
-
- <step><para>
- In the <guimenuitem>Network</guimenuitem> panel, enter the name of
- the print queue on the Samba server as follows: <constant>\\DIAMOND\hplj6a</constant>.
- Click <menuchoice>
- <guibutton>OK</guibutton>
- <guibutton>OK</guibutton>
- </menuchoice> to complete the installation.
- </para></step>
-
- <step><para>
- Repeat the printer installation steps above for both HP LaserJet 6 printers
- as well as for both QMS Magicolor laser printers.
- </para></step>
- </procedure>
-
- </sect2>
-
- <sect2>
- <title>Key Points Learned</title>
-
- <para>
- How do you feel? You have built a capable network, a truly ambitious project.
- Future network updates can be handled by
- your staff. You must be a satisfied manager. Let's review the achievements.
- </para>
-
- <itemizedlist>
- <listitem><para>
- A simple firewall has been configured to protect the server in the event that
- the ISP firewall service should fail.
- </para></listitem>
-
- <listitem><para>
- The Samba configuration uses measures to ensure that only local network users
- can connect to SMB/CIFS services.
- </para></listitem>
-
- <listitem><para>
- Samba uses the new <constant>tdbsam</constant> passdb backend facility.
- Considerable complexity was added to Samba functionality.
- </para></listitem>
-
- <listitem><para>
- A DHCP server was configured to implement dynamic DNS (DDNS) updates to the DNS
- server.
- </para></listitem>
-
- <listitem><para>
- The DNS server was configured to permit DDNS only for local network clients. This
- server also provides primary DNS services for the company Internet presence.
- </para></listitem>
-
- <listitem><para>
- You introduced an application server as well as the concept of cloning a Windows
- client in order to effect improved standardization of desktops and to reduce
- the costs of network management.
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- </para>
-
- <qandaset defaultlable="missed01" type="number">
- <qandaentry>
- <question>
-
- <para>
- What is the maximum number of account entries that the <parameter>tdbsam</parameter>
- passdb backend can handle?
- </para>
-
- </question>
- <answer>
-
- <para>
- The tdb data structure and support system can handle more entries than the number of
- accounts that are possible on most UNIX systems. A practical limit would come into
- play long before a performance boundary would be anticipated. That practical limit
- is controlled by the nature of Windows networking. There are few Windows file and
- print servers that can handle more than a few hundred concurrent client connections.
- The key limiting factors that predicate offloading of services to additional servers
- are memory capacity, the number of CPUs, network bandwidth, and disk I/O limitations.
- All of these are readily exhausted by just a few hundred concurrent active users.
- Such bottlenecks can best be removed by segmentation of the network (distributing
- network load across multiple networks).
- </para>
-
- <para>
- As the network grows, it becomes necessary to provide additional authentication
- servers (domain controllers). The tdbsam is limited to a single machine and cannot
- be reliably replicated. This means that practical limits on network design dictate
- the point at which a distributed passdb backend is required; at this time, there is
- no real alternative other than ldapsam (LDAP).
- </para>
-
- <para>
- The guideline provided in <emphasis>TOSHARG2</emphasis>, Chapter 10, Section 10.1.2,
- is to limit the number of accounts in the tdbsam backend to 250. This is the point
- at which most networks tend to want backup domain controllers (BDCs). Samba does
- not provide a mechanism for replicating tdbsam data so it can be used by a BDC. The
- limitation of 250 users per tdbsam is predicated only on the need for replication,
- not on the limits<footnote><para>Bench tests have shown that tdbsam is a very
- effective database technology. There is surprisingly little performance loss even
- with over 4000 users.</para></footnote> of the tdbsam backend itself.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Would Samba operate any better if the OS level is set to a value higher than 35?
- </para>
-
- </question>
- <answer>
-
- <para>
- No. MS Windows workstations and servers do not use a value higher than 33. Setting this to a value
- of 35 already assures Samba of precedence over MS Windows products in browser elections. There is
- no gain to be had from setting this higher.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why in this example have you provided UNIX group to Windows Group mappings for only Domain Groups?
- </para>
-
- </question>
- <answer>
-
- <para>
- At this time, Samba has the capacity to use only Domain Groups mappings. It is possible that at
- a later date Samba may make use of Windows Local Groups, as well as of the Active Directory special
- Groups. Proper operation requires Domain Groups to be mapped to valid UNIX groups.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why has a path been specified in the <parameter>IPC$</parameter> share?
- </para>
-
- </question>
- <answer>
-
- <para>
- This is done so that in the event that a software bug may permit a client connection to the IPC$ share to
- obtain access to the file system, it does so at a location that presents least risk. Under normal operation
- this type of paranoid step should not be necessary. The use of this parameter should not be necessary.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why does the &smb.conf; file in this exercise include an entry for <smbconfoption name="smb ports"/>?
- </para>
-
- </question>
- <answer>
-
- <para>
- The default order by which Samba attempts to communicate with MS Windows clients is via port 445 (the TCP port
- used by Windows clients when NetBIOS-less SMB over TCP/IP is in use). TCP port 139 is the primary port used for NetBIOS
- over TCP/IP. In this configuration Windows network operations are predicated around NetBIOS over TCP/IP. By
- specifying the use of only port 139, the intent is to reduce unsuccessful service connection attempts.
- The result of this is improved network performance. Where Samba is installed as an Active Directory Domain
- member, the default behavior is highly beneficial and should not be changed.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What is the difference between a print queue and a printer?
- </para>
-
- </question>
- <answer>
-
- <para>
- A printer is a physical device that is connected either directly to the network or to a computer
- via a serial, parallel, or USB connection so that print jobs can be submitted to it to create a
- hard copy printout. Network-attached printers that use TCP/IP-based printing generally accept a
- single print data stream and block all secondary attempts to dispatch jobs concurrently to the
- same device. If many clients were to concurrently print directly via TCP/IP to the same printer,
- it would result in a huge amount of network traffic through continually failing connection attempts.
- </para>
-
- <para>
- A print server (like CUPS or LPR/LPD) accepts multiple concurrent input streams or
- print requests. When the data stream has been fully received, the input stream is closed,
- and the job is then submitted to a sequential print queue where the job is stored until
- the printer is ready to receive the job.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Can all MS Windows application software be installed onto an application server share?
- </para>
-
- </question>
- <answer>
-
- <para>
- Much older Windows software is not compatible with installation to and execution from
- an application server. Enterprise versions of Microsoft Office XP Professional can
- be installed to an application server. Retail consumer versions of Microsoft Office XP
- Professional do not permit installation to an application server share and can be installed
- and used only to/from a local workstation hard disk.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why use dynamic DNS (DDNS)?
- </para>
-
- </question>
- <answer>
-
- <para>
- When DDNS records are updated directly from the DHCP server, it is possible for
- network clients that are not NetBIOS-enabled, and thus cannot use WINS, to locate
- Windows clients via DNS.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why would you use WINS as well as DNS-based name resolution?
- </para>
-
- </question>
- <answer>
-
- <para>
- WINS is to NetBIOS names as DNS is to fully qualified domain names (FQDN). The FQDN is
- a name like <quote>myhost.mydomain.tld</quote> where <parameter>tld</parameter>
- means <constant>top-level domain</constant>. A FQDN is a longhand but easy-to-remember
- expression that may be up to 1024 characters in length and that represents an IP address.
- A NetBIOS name is always 16 characters long. The 16<superscript>th</superscript> character
- is a name type indicator. A specific name type is registered<footnote><para>
- See <emphasis>TOSHARG2</emphasis>, Chapter 9, for more information.</para></footnote> for each
- type of service that is provided by the Windows server or client and that may be registered
- where a WINS server is in use.
- </para>
-
- <para>
- WINS is a mechanism by which a client may locate the IP Address that corresponds to a
- NetBIOS name. The WINS server may be queried to obtain the IP Address for a NetBIOS name
- that includes a particular registered NetBIOS name type. DNS does not provide a mechanism
- that permits handling of the NetBIOS name type information.
- </para>
-
- <para>
- DNS provides a mechanism by which TCP/IP clients may locate the IP address of a particular
- hostname or service name that has been registered in the DNS database for a particular domain.
- A DNS server has limited scope of control and is said to be authoritative for the zone over
- which it has control.
- </para>
-
- <para>
- Windows 200x Active Directory requires the registration in the DNS zone for the domain it
- controls of service locator<footnote><para>See TOSHARG2, Chapter 9, Section 9.3.3.</para></footnote> records
- that Windows clients and servers will use to locate Kerberos and LDAP services. ADS also
- requires the registration of special records that are called global catalog (GC) entries
- and site entries by which domain controllers and other essential ADS servers may be located.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What are the major benefits of using an application server?
- </para>
-
- </question>
- <answer>
-
- <para>
- The use of an application server can significantly reduce application update maintenance.
- By providing a centralized application share, software updates need be applied to only
- one location for all major applications used. This results in faster update roll-outs and
- significantly better application usage control.
- </para>
-
- </answer>
- </qandaentry>
-
- </qandaset>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="simple">
- <title>No-Frills Samba Servers</title>
-
- <para>
- This is the start of the real journey toward the successful deployment of Samba. For some this chapter
- is the end of the road because their needs will have been adequately met. For others, this chapter is
- the beginning of a journey that will take them well past the contents of this book. This book provides
- example configurations of, for the greater part, complete networking solutions. The intent of this book
- is to help you to get your Samba installation working with the least amount of pain and aggravation.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- This chapter lays the groundwork for understanding the basics of Samba operation.
- Instead of a bland technical discussion, each principle is demonstrated by way of a
- real-world scenario for which a working solution<footnote><para>The examples given mirror those documented
- in The Official Samba HOWTO and Reference Guide, Second Edition (TOSHARG2) Chapter 2, Section 2.3.1. You may gain additional
- insight from the standalone server configurations covered in TOSHARG2, sections 2.3.1.2 through 2.3.1.4.
- </para></footnote> is fully described.
- </para>
-
- <para>
- The practical exercises take you on a journey through a drafting office, a charity administration
- office, and an accounting office. You may choose to apply any or all of these exercises to your own environment.
- </para>
-
- <para>
- Every assignment case can be implemented far more creatively, but remember that the solutions you
- create are designed to demonstrate a particular solution possibility. With experience, you should
- find much improved solutions compared with those presented here. By the time you complete this book,
- you should aim to be a Samba expert, so do attempt to find better solutions and try them as you work your
- way through the examples.
- </para>
-
-</sect1>
-<sect1>
- <title>Assignment Tasks</title>
-
- <para>
- Each case presented highlights different aspects of Windows networking for which a simple
- Samba-based solution can be provided. Each has subtly different requirements taken from real-world cases.
- The cases are briefly reviewed to cover important points. Instructions are based
- on the assumption that the official Samba Team RPM package has been installed.
- </para>
-
- <para>
- This chapter has three assignments built around fictitious companies:
- </para>
-
- <para>
- <itemizedlist>
- <listitem><para>A drafting office</para></listitem>
- <listitem><para>A charity administration office</para></listitem>
- <listitem><para>An accounting office</para></listitem>
- </itemizedlist>
- </para>
-
- <para>
- Let's get started.
- </para>
-
- <sect2>
- <title>Drafting Office</title>
-
- <para>
- Our fictitious company is called <emphasis>Abmas Design, Inc.</emphasis> This is a three-person
- computer-aided design (CAD) business that often has more work than can be handled. The
- business owner hires contract draftspeople from wherever he can. They bring their own
- notebook computers into the office. There are four permanent drafting machines. Abmas has a
- collection of over 10 years of plans that must be available for all draftsmen to reference.
- Abmas hires the services of an experienced network engineer to update the
- plans that are stored on a central server one day per month. She knows how to upload
- plans from each machine. The files available from the server must remain read-only.
- Anyone should be able to access the plans at any time and without barriers or difficulty.
- </para>
-
- <para><indexterm><primary>Red Hat</primary></indexterm>
- <indexterm><primary>Fedora</primary></indexterm>
- Mr. Bob Jordan has asked you to install the new server as economically as possible. The central
- server has a Pentium-IV 1.6GHz CPU, 768MB RAM, a 20GB IDE boot drive, a 160GB IDE second disk
- to store plans, and a 100-base-T Ethernet card. You have already installed Red Hat Fedora CoreX and
- have upgraded Samba to version 3.0.20 using the RPM package that is provided from the Samba
- <ulink url="http://www.samba.org">FTP</ulink> sites. (Note: Fedora CoreX indicates your favorite
- version.)
- </para>
-
- <para><indexterm>
- <primary>consultant</primary>
- </indexterm>
- The four permanent drafting machines (Microsoft Windows workstations) have attached printers
- and plotters that are shared on a peer-to-peer basis by any and all network users. The intent
- is to continue to share printers in this manner. The three permanent staff work together with
- all contractors to store all new work on one PC. A daily copy is made of the work storage
- area to another PC for safekeeping. When the network consultant arrives, the weekly work
- area is copied to the central server and the files are removed from the main weekly storage
- machine. The office works best with this arrangement and does not want to change anything.
- Old habits are too ingrained.
- </para>
-
- <sect3>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>file server</primary><secondary>read-only</secondary></indexterm>
- The requirements for this server installation demand simplicity. An anonymous read-only
- file server adequately meets all needs. The network consultant determines how
- to upload all files from the weekly storage area to the server. This installation should
- focus only on critical aspects of the installation.
- </para>
-
- <para>
- It is not necessary to have specific users on the server. The site has a method for storing
- all design files (plans). Each plan is stored in a directory that is named YYYYWW,<footnote><para>
- This information is given purely as an example of how data may be stored in such a way that it
- will be easy to locate records at a later date. The example is not meant to imply any instructions
- that may be construed as essential to the design of the solution; this is something you will almost
- certainly want to determine for yourself.</para></footnote> where
- YYYY is the year, and WW is the week of the year. This arrangement allows work to be stored
- by week of year to preserve the filing technique the site is familiar with.
- There is also a customer directory that is alphabetically listed. At the top level are 26
- directories (A-Z), in each is a second-level of directory for the first plus second letters of the name
- (A-Z); inside each is a directory by the customers' name. Inside each directory is a symbolic
- link to each design drawing or plan. This way of storing customer data files permits all
- plans to be located both by customer name and by the date the work was performed, without
- demanding the disk space that would be needed if a duplicate file copy were to be stored.
- The share containing the plans is called <emphasis>Plans</emphasis>.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Implementation</title>
-
- <para>
- It is assumed that the server is fully installed and ready for installation and
- configuration of Samba 3.0.20 and any support files needed. All TCP/IP addresses
- have been hard-coded. In our case the IP address of the Samba server is
- <constant>192.168.1.1</constant> and the netmask is <constant>255.255.255.0</constant>.
- The hostname of the server used is <constant>server</constant>.
- </para>
-
- <procedure>
- <title>Samba Server Configuration</title>
-
- <step><para>
- Download the Samba RPM packages for Red Hat Fedora Core2 from the Samba
- <ulink url="http://www.samba.org">FTP servers.</ulink>
- </para></step>
-
- <step><para>
- <indexterm><primary>RPM</primary><secondary>install</secondary></indexterm>
- <indexterm><primary>package</primary></indexterm>
- Install the RPM package using either the Red Hat Linux preferred GUI
- tool or the <command>rpm</command>:
-<screen>
-&rootprompt; rpm -Uvh samba-3.0.20-1.i386.rpm
-</screen>
- </para></step>
-
- <step><para>
- Create a mount point for the file system that will be used to store all data files.
- You can create a directory called <filename>/plans</filename>:
-<screen>
-&rootprompt; mkdir /plans
-&rootprompt; chmod 755 /plans
-</screen>
- The 755 permissions on this directory (mount point) permit the owner to read, write,
- and execute, and the group and everyone else to read and execute only.
- </para>
-
- <para>
- <indexterm><primary>file system</primary><secondary>Ext3</secondary></indexterm>
- Use Red Hat Linux system tools (refer to Red Hat instructions)
- to format the 160GB hard drive with a suitable file system. An Ext3 file system
- is suitable. Configure this drive to automatically mount using the <filename>/plans</filename>
- directory as the mount point.
- </para></step>
-
- <step><para>
- Install the &smb.conf; file shown in <link linkend="draft-smbconf"/> in the
- <filename>/etc/samba</filename> directory.
-
-<example id="draft-smbconf">
-<title>Drafting Office &smb.conf; File</title>
-<smbconfblock>
-<smbconfcomment>Global Parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="security">SHARE</smbconfoption>
-
-<smbconfsection name="[Plans]"/>
-<smbconfoption name="path">/plans</smbconfoption>
-<smbconfoption name="read only">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-</smbconfblock>
-</example>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- Verify that the <filename>/etc/hosts</filename> file contains the following entry:
-<screen>
-192.168.1.1 server
-</screen>
-
- </para></step>
-
- <step><para>
- <indexterm><primary>samba</primary><secondary>starting samba</secondary></indexterm>
- <indexterm><primary>chkconfig</primary></indexterm>
- <indexterm><primary>starting samba</primary></indexterm>
- Use the standard system tool to start Samba and to configure it to restart
- automatically at every system reboot. For example,
-<screen>
-&rootprompt; chkconfig smb on
-&rootprompt; /etc/rc.d/init.d/smb restart
-</screen>
- </para></step>
-
- </procedure>
-
- <procedure>
- <title>Windows Client Configuration</title>
-
- <step><para>
- Make certain that all clients are set to the same network address range as
- used for the Samba server. For example, one client might have an IP
- address 192.168.1.10.
- </para></step>
-
- <step><para>
- <indexterm><primary>netmask</primary></indexterm>
- Ensure that the netmask used on the Windows clients matches that used
- for the Samba server. All clients must have the same netmask, such as
- 255.255.255.0.
- </para></step>
-
- <step><para>
- <indexterm><primary>workgroup</primary></indexterm>
- Set the workgroup name on all clients to <constant>MIDEARTH</constant>.
- </para></step>
-
- <step><para>
- Verify on each client that the machine called <constant>SERVER</constant>
- is visible in the <guimenu>Network Neighborhood</guimenu>, that it is
- possible to connect to it and see the share <guimenuitem>Plans</guimenuitem>,
- and that it is possible to open that share to reveal its contents.
- </para></step>
-
- </procedure>
-
- </sect3>
-
- <sect3 id="validate1">
- <title>Validation</title>
-
- <para>
- <indexterm><primary>validation</primary></indexterm>
- The first priority in validating the new Samba configuration should be to check
- that Samba answers on the loop-back interface. Then it is time to check that Samba
- answers its own name correctly. Last, check that a client can connect to the Samba
- server.
- </para>
-
- <procedure>
- <step><para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>daemon</primary></indexterm>
- <indexterm><primary>smbclient</primary></indexterm>
- To check the ability to access the <command>smbd</command> daemon
- services, execute the following:
-<screen>
-&rootprompt; smbclient -L localhost -U%
- Sharename Type Comment
- --------- ---- -------
- Plans Disk
- IPC$ IPC IPC Service (Samba 3.0.20)
- ADMIN$ IPC IPC Service (Samba 3.0.20)
-
- Server Comment
- --------- -------
- SERVER Samba 3.0.20
-
- Workgroup Master
- --------- --------
- MIDEARTH SERVER
-</screen>
- <indexterm><primary>loopback</primary></indexterm>
- <indexterm><primary>NULL connection</primary></indexterm>
- This indicates that Samba is able to respond on the loopback interface to
- a NULL connection. The <parameter>-U%</parameter> means send an empty
- username and an empty password. This command should be repeated after
- Samba has been running for 15 minutes.
- </para></step>
-
- <step><para>
- Now verify that Samba correctly handles being passed a username
- and password, and that it answers its own name. Execute the following:
-<screen>
-&rootprompt; smbclient -L server -Uroot%password
-</screen>
- The output should be identical to the previous response. Samba has been
- configured to ignore all usernames given; instead it uses the
- <parameter>guest account</parameter> for all connections.
- </para></step>
-
- <step><para>
- <indexterm><primary>Windows Explorer</primary></indexterm>
- <indexterm><primary>Network Neighborhood</primary></indexterm>
- From the Windows 9x/Me client, launch Windows Explorer:
- <menuchoice>
- <guiicon>[Desktop: right-click] Network Neighborhood</guiicon>
- <guimenu>Explore</guimenu>
- <guimenuitem>[Left Panel] [+] Entire Network</guimenuitem>
- <guimenuitem>[Left Panel] [+] Server</guimenuitem>
- <guimenuitem>[Left Panel] [+] Plans</guimenuitem>
- </menuchoice>. In the right panel you should see the files and directories
- (folders) that are in the <guiicon>Plans</guiicon> share.
- </para></step>
- </procedure>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Charity Administration Office</title>
-
- <para>
- The fictitious charity organization is called <emphasis>Abmas Vision NL</emphasis>. This office
- has five networked computers. Staff are all volunteers, staff changes are frequent.
- Ms. Amy May, the director of operations, wants a no-hassle network. Anyone should be able to
- use any PC. Only two Windows applications are used: a custom funds tracking and management package
- that stores all files on the central server and Microsoft Word. The office prepares mail-out
- letters, invitations, and thank-you notes. All files must be stored in perpetuity.
- The custom funds tracking and management (FTM) software is configured to use a server named
- <constant>SERVER</constant>, a share named <constant>FTMFILES</constant>, and a printer queue
- named <constant>PRINTQ</constant> that uses preprinted stationery, thus demanding a
- dedicated printer. This printer does not need to be mapped to a local printer on the workstations.
- </para>
-
- <para>
- The FTM software has been in use since the days of Windows 3.11. The software was configured
- by the vendor who has since gone out of business. The identities of the file
- server and the printer are hard-coded in a configuration file that was created using a
- setup tool that the vendor did not provide to Abmas Vision NL or to its predecessors. The
- company that produced the software is no longer in business. In order to avoid risk of
- any incompatibilities, the share name and the name of the target print queue must be set
- precisely as the application expects. In fact, share names and print queue names
- should be treated as case insensitive (i.e., case does not matter), but Abmas Vision advises
- that if the share name is not in lowercase, the application claims it cannot find the
- file share.
- </para>
-
- <para>
- <indexterm><primary>print queue</primary></indexterm>
- <indexterm><primary>print spooler</primary></indexterm>
- Printer handling in Samba results in a significant level of confusion. Samba presents to the
- MS Windows client only a print queue. The Samba <command>smbd</command> process passes a
- print job sent to it from the Windows client to the native UNIX printing system. The native
- UNIX printing system (spooler) places the job in a print queue from which it is
- delivered to the printer. In this book, network diagrams refer to a printer by the name
- of the print queue that services that printer. It does not matter what the fully qualified
- name (or the hostname) of a network-attached printer is. The UNIX print spooler is configured
- to correctly deliver all jobs to the printer.
- </para>
-
- <para>
- This organization has a policy forbidding use of privately owned computers on site as a measure
- to prevent leakage of confidential information. Only the five PCs owned by Abmas Vision NL are
- used on this network.
- </para>
-
- <para>
- <indexterm><primary>SUSE Enterprise Linux Server</primary></indexterm>
- The central server was donated by a local computer store. It is a dual processor Pentium-III
- server, has 1GB RAM, a 3-Ware IDE RAID Controller that has four 200GB IDE hard drives, and a
- 100-base-T network card. The office has 100-base-T permanent network connections that go to
- a central hub, and all equipment is new. The five network computers all are equipped with Microsoft
- Windows Me. Funding is limited, so the server has no operating system on it. You have approval
- to install Samba on Linux, provided it works without problems. There are two HP LaserJet
- 5 PS printers that are network connected. The second printer is to be used for general
- office and letter printing. Your recommendation to allow only the Linux server to print directly
- to the printers was accepted. You have supplied SUSE Enterprise Linux Server 9 and
- have upgraded Samba to version 3.0.20.
- </para>
-
- <sect3>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>force user</primary></indexterm>
- <indexterm><primary>nt acl support</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>Posix</primary></indexterm>
- This installation demands simplicity. Frequent turnover of volunteer staff indicates that
- a network environment that requires users to logon might be problematic. It is suggested that the
- best solution for this office would be one where the user can log onto any PC with any username
- and password. Samba can accommodate an office like this by using the <parameter>force user</parameter>
- parameter in share and printer definitions. Using the <parameter>force user</parameter>
- parameter ensures that all files are owned by same user identifier (UID) and thus that there
- will never be a problem with file access due to file access permissions. Additionally, you elect
- to use the <parameter>nt acl support = No</parameter> option to ensure that
- access control lists (Posix type) cannot be written to any file or directory. This prevents
- an inadvertent ACL from overriding actual file permissions.
- </para>
-
- <para>
- <indexterm><primary>SUID</primary></indexterm>
- <indexterm><primary>SGID</primary></indexterm>
- <indexterm><primary>security</primary><secondary>share mode</secondary></indexterm>
- This organization is a prime candidate for Share Mode security. The <parameter>force user</parameter>
- allows all files to be owned by the same user and group. In addition, it would not hurt to
- set SUID and set SGID shared directories. This means that all new files that are created, no matter
- who creates it, are owned by the owner or group of the directory in which they are created.
- For further information regarding the significance of the SUID/SGID settings, see <link
- linkend="appendix"/>, <link linkend="ch12-SUIDSGID"/>.
- </para>
-
- <para>
- <indexterm><primary>CUPS</primary></indexterm>
- <indexterm><primary>printing</primary><secondary>raw</secondary></indexterm>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- <indexterm><primary>SUSE Linux</primary></indexterm>
- All client workstations print to a print queue on the server. This ensures that print jobs
- continue to print in the event that a user shuts down the workstation immediately after
- sending a job to the printer. Today, both Red Hat Linux and SUSE Linux use CUPS-based printing.
- Older Linux systems offered a choice between the LPRng printing system or CUPS. It appears, however,
- that CUPS has become the leading UNIX printing technology.
- </para>
-
- <para>
- <indexterm><primary>print queue</primary></indexterm>
- The print queues are set up as <constant>Raw</constant> devices, which means that CUPS will
- not do intelligent print processing, and vendor-supplied drivers must be installed locally on the
- Windows clients.
- </para>
-
- <para>
- The hypothetical software, FTM, is representative of
- custom-built software that directly uses a NetBIOS interface. Most such software originated in
- the days of MS/PC DOS. NetBIOS names are uppercase (and functionally are case insensitive),
- so some old software applications would permit only uppercase names to be entered.
- Some such applications were later ported to MS Windows but retain the uppercase network
- resource naming conventions because customers are familiar with that. We made the decision
- to name shares and print queues for this application in uppercase for the same reason.
- Nothing would break if we were to use lowercase names, but that decision might create a need
- to retrain staff &smbmdash; something well avoided at this time.
- </para>
-
- <para>
- NetBIOS networking does not print directly to a printer. Instead, all printing is done to a
- print queue. The print spooling system is responsible for communicating with the physical
- printer. In this example, therefore, the resource called <constant>PRINTQ</constant>
- really is just a print queue. The name of the print queue is representative of
- the device to which the print spooler delivers print jobs.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Implementation</title>
-
- <para>
- It is assumed that the server is fully installed and ready for configuration of
- Samba 3.0.20 and for necessary support files. All TCP/IP addresses should be hard-coded.
- In our case, the IP address of the Samba server is 192.168.1.1 and the netmask is
- 255.255.255.0. The hostname of the server used is <constant>server</constant>.
- The office network is built as shown in <link linkend="charitynet"/>.
- </para>
-
- <figure id="charitynet">
- <title>Charity Administration Office Network</title>
- <imagefile scale="80">Charity-Network</imagefile>
- </figure>
-
- <procedure>
- <title>Samba Server Configuration</title>
-
- <step><para>
- <indexterm><primary>groupadd</primary></indexterm>
- Create a group account for office file storage:
-<screen>
-&rootprompt; groupadd office
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>useradd</primary></indexterm>
- <indexterm><primary>passwd</primary></indexterm>
- Create a user account for office file storage:
-<screen>
-&rootprompt; useradd -m abmas
-&rootprompt; passwd abmas
-Changing password for abmas.
-New password: XXXXXXXX
-Re-enter new password: XXXXXXXX
-Password changed
-</screen>
- where XXXXXXXX is a secret password.
- </para></step>
-
- <step><para>
- Use the 3-Ware IDE RAID Controller firmware utilities to configure the four 200GB
- drives as a single RAID level 5 drive, with one drive set aside as the hot spare.
- (Refer to the 3-Ware RAID Controller Manual for the manufacturer's preferred procedure.)
- The resulting drive has a capacity of approximately 500GB of usable space.
- </para></step>
-
- <step><para>
- <indexterm><primary>permissions</primary></indexterm>
- Create a mount point for the file system that can be used to store all data files.
- Create a directory called <filename>/data</filename>:
-<screen>
-&rootprompt; mkdir /data
-&rootprompt; chmod 755 /data
-</screen>
- The 755 permissions on this directory (mount point) permit the owner to read, write, and execute,
- and the group and everyone else to read and execute only.
- </para></step>
-
- <step><para>
- Use SUSE Linux system tools (refer to the SUSE Administrators Guide for correct
- procedures) to format the partition with a suitable file system. The reiserfs file system
- is suitable. Configure this drive to automount using the <filename>/data</filename>
- directory as the mount point. It must be mounted before proceeding.
- </para></step>
-
- <step><para>
- Under the directory called <filename>/data</filename>, create two directories
- named <filename>ftmfiles</filename> and <filename>officefiles</filename>, and set
- ownership and permissions:
-<screen>
-&rootprompt; mkdir -p /data/{ftmfiles,officefiles/{letters,invitations,misc}}
-&rootprompt; chown -R abmas:office /data
-&rootprompt; chmod -R ug+rwxs,o-w,o+rx /data
-</screen>
- These demonstrate compound operations. The <command>mkdir</command> command
- creates in one step these directories:
-<programlisting>
-/data/fmtfiles
-/data/officefiles
-/data/officefiles/letters
-/data/officefiles/invitations
-/data/officefiles/misc
-</programlisting>
- <indexterm><primary>TOSHARG2</primary></indexterm>
- The <command>chown</command> operation sets the owner to the user <constant>abmas</constant>
- and the group to <constant>office</constant> on all directories just created. It recursively
- sets the permissions so that the owner and group have SUID/SGID with read, write, and execute
- permission, and everyone else has read and execute permission. This means that all files and
- directories are created with the same owner and group as the directory in which they are
- created. Any new directories created still have the same owner, group, and permissions as the
- directory they are in. This should eliminate all permissions-based file access problems. For
- more information on this subject, refer to TOSHARG2<footnote><para>The Official Samba HOWTO and
- Reference Guide, Chapter 15, File, Directory and Share Access Controls.</para></footnote> or refer
- to the UNIX man page for the <command>chmod</command> and the <command>chown</command> commands.
- </para></step>
-
- <step><para>
- Install the &smb.conf; file shown in <link linkend="charity-smbconfnew"/> in the
- <filename>/etc/samba</filename> directory. This newer &smb.conf; file uses user-mode security
- and is more suited to the mode of operation of Samba than the older share-mode security
- configuration that was shown in the first edition of this book.
- </para>
-
- <para>
- Note: If you want to use the older-style configuration that uses share-mode security, you
- can install the file shown in <link linkend="charity-smbconf"/> in the
- <filename>/etc/samba</filename> directory.
- </para></step>
-
- <step><para>
- <indexterm><primary>smbd</primary></indexterm>
- We must ensure that the <command>smbd</command> can resolve the name of the Samba
- server to its IP address. Verify that the <filename>/etc/hosts</filename> file
- contains the following entry:
-<screen>
-192.168.1.1 server
-</screen>
- </para></step>
-
- <step><para>
- Configure the printers with the IP address as shown in <link linkend="charitynet"/>.
- Follow the instructions in the manufacturer's manual to permit printing to port 9100
- so that the CUPS spooler can print using raw mode protocols.
- </para></step>
-
- <step><para>
- <indexterm><primary>lpadmin</primary></indexterm>
- Configure the CUPS Print Queues:
-<screen>
-&rootprompt; lpadmin -p PRINTQ -v socket://192.168.1.20:9100 -E
-&rootprompt; lpadmin -p hplj5 -v socket://192.168.1.30:9100 -E
-</screen>
- This creates the necessary print queues with no assigned print filter.
- </para></step>
-
- <step><para>
- <indexterm><primary>mime type</primary></indexterm>
- <indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
- <indexterm><primary>application/octet-stream</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
-<screen>
-application/octet-stream application/vnd.cups-raw 0 -
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/cups/mime.types</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
-<screen>
-application/octet-stream
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>starting samba</primary></indexterm>
- Use the standard system tool to start Samba and CUPS to configure them to restart
- automatically at every system reboot. For example,
- </para>
-
- <para>
- <indexterm><primary>starting samba</primary></indexterm>
- <indexterm><primary>starting CUPS</primary></indexterm>
- <indexterm><primary>chkconfig</primary></indexterm>
-<screen>
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig cups on
-&rootprompt; /etc/rc.d/init.d/smb restart
-&rootprompt; /etc/rc.d/init.d/cups restart
-</screen>
- </para></step>
-
- </procedure>
-
-<example id="charity-smbconfnew">
-<title>Charity Administration Office &smb.conf; New-style File</title>
-<smbconfblock>
-<smbconfcomment>Global Parameters - Newer Configuration</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="printing">CUPS</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="map to guest">Bad User</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="wins support">yes</smbconfoption>
-
-<smbconfsection name="[FTMFILES]"/>
-<smbconfoption name="comment">Funds Tracking & Management Files</smbconfoption>
-<smbconfoption name="path">/data/ftmfiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="force user">abmas</smbconfoption>
-<smbconfoption name="force group">office</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="nt acl support">No</smbconfoption>
-
-<smbconfsection name="[office]"/>
-<smbconfoption name="comment">General Office Files</smbconfoption>
-<smbconfoption name="path">/data/officefiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="force user">abmas</smbconfoption>
-<smbconfoption name="force group">office</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="nt acl support">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="charity-smbconf">
-<title>Charity Administration Office &smb.conf; Old-style File</title>
-<smbconfblock>
-<smbconfcomment>Global Parameters - Older Style Configuration</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="security">SHARE</smbconfoption>
-<smbconfoption name="printing">CUPS</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="disable spoolss">Yes</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="wins support">yes</smbconfoption>
-
-<smbconfsection name="[FTMFILES]"/>
-<smbconfoption name="comment">Funds Tracking & Management Files</smbconfoption>
-<smbconfoption name="path">/data/ftmfiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="force user">abmas</smbconfoption>
-<smbconfoption name="force group">office</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="nt acl support">No</smbconfoption>
-
-<smbconfsection name="[office]"/>
-<smbconfoption name="comment">General Office Files</smbconfoption>
-<smbconfoption name="path">/data/officefiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="force user">abmas</smbconfoption>
-<smbconfoption name="force group">office</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="nt acl support">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
- <procedure>
- <title>Windows Client Configuration</title>
-
- <step><para>
- Configure clients to the network settings shown in <link linkend="charitynet"/>.
- </para></step>
-
- <step><para>
- Ensure that the netmask used on the Windows clients matches that used
- for the Samba server. All clients must have the same netmask, such as
- <constant>255.255.255.0</constant>.
- </para></step>
-
- <step><para>
- <indexterm><primary>WINS</primary></indexterm>
- On all Windows clients, set the WINS Server address to <constant>192.168.1.1</constant>,
- the IP address of the server.
- </para></step>
-
- <step><para>
- Set the workgroup name on all clients to <constant>MIDEARTH</constant>.
- </para></step>
-
- <step><para>
- <indexterm><secondary>logon</secondary></indexterm>
- Install the <quote>Client for Microsoft Networks.</quote> Ensure that the only option
- enabled in its properties is the option <quote>Logon and restore network connections.</quote>
- </para></step>
-
- <step><para>
- Click <guibutton>OK</guibutton> when you are prompted to reboot the system. Reboot the
- system, then log on using any username and password you choose.
- </para></step>
-
- <step><para>
- <indexterm><primary>My Network Places</primary></indexterm>
- Verify on each client that the machine called <constant>SERVER</constant>
- is visible in <guimenu>My Network Places</guimenu>, that it is
- possible to connect to it and see the share <guimenuitem>office</guimenuitem>,
- and that it is possible to open that share to reveal its contents.
- </para></step>
-
- <step><para>
- <indexterm><primary>password caching</primary></indexterm>
- <indexterm><primary>regedit</primary></indexterm>
- Disable password caching on all Windows 9x/Me machines using the registry change file
- shown in <link linkend="MEreg"/>. Be sure to remove all files that have the
- <filename>PWL</filename> extension that are in the <filename>C:\WINDOWS</filename>
- directory.
-<example id="MEreg">
-<title>Windows Me &smbmdash; Registry Edit File: Disable Password Caching</title>
-<screen>
-REGEDIT4
-
-[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
- Windows\CurrentVersion\Policies\Network]
- "DisablePwdCaching"=dword:00000001
-</screen>
-</example>
- The best way to apply this change is to save the patch in a file called
- <filename>ME-dpwc.reg</filename> and then execute:
-<screen>
-C:\WINDOWS: regedit ME-dpwc.reg
-</screen>
- </para></step>
-
- <step><para>
- Instruct all users to log onto the workstation using a name and password of their own
- choosing. The Samba server has been
- configured to ignore the username and password given.
- </para></step>
-
- <step><para>
- On each Windows Me workstation, configure a network drive mapping to drive <filename>G:</filename>
- that redirects to the uniform naming convention (UNC) resource
- <filename>\\server\office</filename>. Make this a permanent drive connection:
- </para>
- <procedure>
- <step><para>
- Right-click <menuchoice><guimenu>My Network</guimenu>
- <guimenuitem>Map Network Drive...</guimenuitem></menuchoice>
- </para></step>
-
- <step><para>
- In the box labeled <quote>Drive:</quote>, type G.
- </para></step>
-
- <step><para>
- In the box labeled <quote>Path:</quote>, enter
- <filename>\\server\officefiles</filename>.
- </para></step>
-
- <step><para>
- Click <guimenuitem>Reconnect at logon</guimenuitem>.
- Click <guibutton>OK</guibutton>.
- </para></step>
-
- </procedure>
- </step>
-
- <step><para>
- On each workstation, install the FTM software following the
- manufacturer's instructions.
- </para>
- <procedure>
- <step><para>
- During installation, you are prompted for the name of the Windows 98
- server. Enter the name <constant>SERVER</constant>.
- </para></step>
- <step><para>
- You are prompted for the name of the data share.
- The prompt defaults to <constant>FTMFILES</constant>. Press enter to accept the default value.
- </para></step>
- <step><para>
- You are now prompted for the print queue name. The default prompt is the name of
- the server you entered (<constant>SERVER</constant> as follows:
- <constant>\\SERVER\PRINTQ</constant>). Simply accept the default and press enter to
- continue. The software now completes the installation.
- </para></step>
- </procedure>
- </step>
-
- <step><para>
- Install an office automation software package of the customer's choice. Either Microsoft
- Office 2003 Standard or OpenOffice 1.1.0 suffices for any functions the office may
- need to perform. Repeat this on each workstation.
- </para></step>
-
- <step><para>
- Install a printer on each workstation using the following steps:
- </para>
-
- <procedure>
- <step><para>
- Click <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Settings</guimenuitem>
- <guimenuitem>Printers</guimenuitem>
- <guiicon>Add Printer</guiicon>
- <guibutton>Next</guibutton>
- </menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
- Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
- </para></step>
-
- <step><para>
- Click <guibutton>Next</guibutton>. In the Manufacturer: panel, select
- <constant>HP</constant>. In the Printers: panel, select the printer called
- <constant>HP LaserJet 5/5M Postscript</constant>. Click <guibutton>Next</guibutton>.
- </para></step>
-
- <step><para>
- In the Available ports: panel, select <constant>FILE:</constant>. Accept the
- default printer name by clicking <guibutton>Next</guibutton>. When asked,
- <quote>Would you like to print a test page?</quote>, click
- <guimenuitem>No</guimenuitem>. Click <guibutton>Finish</guibutton>.
- </para></step>
-
- <step><para>
- You may be prompted for the name of a file to print to. If so, close the
- dialog panel. Right-click <menuchoice>
- <guiicon>HP LaserJet 5/5M Postscript</guiicon>
- <guimenuitem>Properties</guimenuitem>
- <guisubmenu>Details (Tab)</guisubmenu>
- <guimenuitem>Add Port</guimenuitem>
- </menuchoice>.
- </para></step>
-
- <step><para>
- In the Network panel, enter the name of
- the print queue on the Samba server as follows: <constant>\\SERVER\hplj5</constant>.
- Click <menuchoice>
- <guibutton>OK</guibutton>
- <guibutton>OK</guibutton>
- </menuchoice> to complete the installation.
- </para></step>
-
- <step><para>
- It is a good idea to test the functionality of the complete installation before
- handing the newly configured network over to the Charity Administration Office
- for production use.
- </para></step>
-
- </procedure>
-
- </step>
-
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>Validation</title>
-
- <para>
- Use the same validation process as was followed in <link linkend="validate1"/>.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2 id="AccountingOffice">
- <title>Accounting Office</title>
-
- <para>
- Abmas Accounting is a 40-year-old family-run business. There are nine permanent
- computer users. The network clients were upgraded two years ago. All computers run Windows 2000
- Professional. This year the server will be upgraded from an old Windows NT4 server (actually
- running Windows NT4 Workstation, which worked fine for fewer than 10 users) that has
- run in workgroup (standalone) mode, to a new Linux server running Samba.
- </para>
-
- <para>
- The office does not want a Domain Server. Mr. Alan Meany wants to keep the Windows 2000 Professional
- clients running as workgroup machines so that any staff member can take a machine home and keep
- working. It has worked well so far, and your task is to replace the old server. All users have
- their own workstation logon (you configured it that way when the machines were installed).
- Mr. Meany wants the new system to operate the same way as the old Windows NT4 server &smbmdash; users
- cannot access each others' files, but he can access everyone's files. Each person's work files are
- in a separate share on the server. Users log on to their Windows workstation with their username
- and enter an assigned password; they do not need to enter a password when accessing their files
- on the server.
- </para>
-
- <para>
- <indexterm><primary>Red Hat Linux</primary></indexterm>
- The new server will run Red Hat Fedora Core2. You should install Samba-3.0.20 and
- copy all files from the old system to the new one. The existing Windows NT4 server has a parallel
- port HP LaserJet 4 printer that is shared by all. The printer driver is installed on each
- workstation. You must not change anything on the workstations. Mr. Meany gave instructions to
- replace the server, <quote>but leave everything else alone to avoid staff unrest.</quote>
- </para>
-
- <para>
- You have tried to educate Mr. Meany and found that he has no desire to understand networking.
- He believes that Windows for Workgroups 3.11 was <quote>the best server Microsoft ever sold
- </quote> and that Windows NT and 2000 are <quote>too fang-dangled complex!</quote>
- </para>
-
- <sect3>
- <title>Dissection and Discussion</title>
-
- <para>
- <indexterm><primary>security</primary><secondary>user mode</secondary></indexterm>
- The requirements of this network installation are not unusual. The staff are not interested in the
- details of networking. Passwords are never changed. In this example solution, we demonstrate the use
- of User Mode security in a simple context. Directories should be set SGID to ensure that members
- of a common group can access the contents. Each user has his or her own share to which only they
- can connect. Mr. Meany's share will be a top-level directory above the share point for each employee.
- Mr. Meany is a member of the same group as his staff and can access their work files.
- The well-used HP LaserJet 4 is available as a service called <constant>hplj</constant>.
- </para>
-
- <para>
- You have finished configuring the new hardware and have just completed installation of Red Hat
- Fedora Core2. Roll up your sleeves and let's get to work.
- </para>
-
- </sect3>
-
- <sect3 id="AcctgNet">
- <title>Implementation</title>
-
- <para>
- The workstations have fixed IP addresses. The old server runs Windows NT4 Workstation, so it
- cannot be running as a WINS server. It is best that the new configuration preserves the same
- configuration. The office does not use Internet access, so security really is not an issue.
- </para>
-
- <para>
- The core information regarding the users, their passwords, the directory share point, and the
- share name is given in <link linkend="acctingnet"/>. The overall network topology is shown in
- <link linkend="acctingnet2"/>. All machines have been configured as indicated prior to the
- start of Samba configuration. The following prescriptive steps may now commence.
- </para>
-
- <figure id="acctingnet2">
- <title>Accounting Office Network Topology</title>
- <imagefile scale="85">AccountingNetwork</imagefile>
- </figure>
-
- <table id="acctingnet">
- <title>Accounting Office Network Information</title>
- <tgroup cols="6">
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry>User</entry>
- <entry>Login-ID</entry>
- <entry>Password</entry>
- <entry>Share Name</entry>
- <entry>Directory</entry>
- <entry>Wkst</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Alan Meany</entry>
- <entry>alan</entry>
- <entry>alm1961</entry>
- <entry>alan</entry>
- <entry>/data</entry>
- <entry>PC1</entry>
- </row>
- <row>
- <entry>James Meany</entry>
- <entry>james</entry>
- <entry>jimm1962</entry>
- <entry>james</entry>
- <entry>/data/james</entry>
- <entry>PC2</entry>
- </row>
- <row>
- <entry>Jeannie Meany</entry>
- <entry>jeannie</entry>
- <entry>jema1965</entry>
- <entry>jeannie</entry>
- <entry>/data/jeannie</entry>
- <entry>PC3</entry>
- </row>
- <row>
- <entry>Suzy Millicent</entry>
- <entry>suzy</entry>
- <entry>suzy1967</entry>
- <entry>suzy</entry>
- <entry>/data/suzy</entry>
- <entry>PC4</entry>
- </row>
- <row>
- <entry>Ursula Jenning</entry>
- <entry>ujen</entry>
- <entry>ujen1974</entry>
- <entry>ursula</entry>
- <entry>/data/ursula</entry>
- <entry>PC5</entry>
- </row>
- <row>
- <entry>Peter Pan</entry>
- <entry>peter</entry>
- <entry>pete1984</entry>
- <entry>peter</entry>
- <entry>/data/peter</entry>
- <entry>PC6</entry>
- </row>
- <row>
- <entry>Dale Roland</entry>
- <entry>dale</entry>
- <entry>dale1986</entry>
- <entry>dale</entry>
- <entry>/data/dale</entry>
- <entry>PC7</entry>
- </row>
- <row>
- <entry>Bertrand E Paoletti</entry>
- <entry>eric</entry>
- <entry>eric1993</entry>
- <entry>eric</entry>
- <entry>/data/eric</entry>
- <entry>PC8</entry>
- </row>
- <row>
- <entry>Russell Lewis</entry>
- <entry>russ</entry>
- <entry>russ2001</entry>
- <entry>russell</entry>
- <entry>/data/russell</entry>
- <entry>PC9</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <procedure>
- <title>Migration from Windows NT4 Workstation System to Samba</title>
-
- <step><para><indexterm>
- <primary>migration</primary>
- </indexterm>
- Rename the old server from <constant>CASHPOOL</constant> to <constant>STABLE</constant>
- by logging onto the console as the <constant>Administrator</constant>. Restart the machine
- following system prompts.
- </para></step>
-
- <step><para>
- Name the new server <constant>CASHPOOL</constant> using the standard configuration method.
- Restart the machine following system prompts.
- </para></step>
-
- <step><para>
- Install the latest Samba binary Red Hat Linux RPM that is available from the
- Samba FTP site.
- </para></step>
-
- <step><para>
- <indexterm><primary>group account</primary></indexterm>
- <indexterm><primary>groupadd</primary></indexterm>
- Add a group account for the office to use. Execute the following:
-<screen>
-&rootprompt; groupadd accts
-</screen>
- </para></step>
-
- <step><para>
- Install the &smb.conf; file shown<footnote><para>This example uses the
- <parameter>smbpasswd</parameter> file in an obtuse way, since the use of
- the <parameter>passdb backend</parameter> has not been specified in the &smb.conf;
- file. This means that you are depending on correct default behavior.</para></footnote>
- in <link linkend="acctconf"/>.
- </para></step>
-
- <step><para>
- <indexterm><primary>useradd</primary></indexterm>
- <indexterm><primary>passwd</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- For each user who uses this system (see <link linkend="acctingnet"/>),
- execute the following:
-<screen>
-&rootprompt; useradd -m -G accts -c "Name of User" "LoginID"
-&rootprompt; passwd "LoginID"
-Changing password for user "LoginID"
-New Password: XXXXXXXXX <-- the password from the table
-Retype new password: XXXXXXXXX
-&rootprompt; smbpasswd -a "LoginID"
-New SMB password: XXXXXXXXX <-- the password from the table
-Retype new SMB password: XXXXXXXXX
-Added user "LoginID"
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>data storage</primary></indexterm>
- Create the directory structure for the file shares by executing the following:
-<screen>
-&rootprompt; mkdir -p /data
-&rootprompt; chown alan /data
-&rootprompt; for i in james suzy ujen peter dale eric jeannie russ
-> do
-> mkdir -p /data/$i
-> chown $i /data/$i
-> done
-&rootprompt; chgrp -R accts /data
-&rootprompt; chmod -R ug+rwxs,o-r+x /data
-</screen>
- The data storage structure is now prepared for use.
- </para></step>
-
- <step><para>
- <indexterm><primary>lpadmin</primary></indexterm>
- Configure the CUPS Print Queues:
-<screen>
-&rootprompt; lpadmin -p hplj -v parallel:/dev/lp0 -E
-</screen>
- This creates the necessary print queues with no assigned print filter.
- </para></step>
-
- <step><para>
- <indexterm><primary>mime types</primary></indexterm>
- <indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
-<screen>
-application/octet-stream application/vnd.cups-raw 0 -
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/cups/mime.types</primary></indexterm>
- <indexterm><primary>application/octet-stream</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
-<screen>
-application/octet-stream
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>starting samba</primary></indexterm>
- Use the standard system tool to start Samba and CUPS to configure them to restart
- automatically at every system reboot. For example,
- </para>
-
- <para>
- <indexterm><primary>starting samba</primary></indexterm>
- <indexterm><primary>startingCUPS</primary></indexterm>
- <indexterm><primary>chkconfig</primary></indexterm>
-<screen>
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig cups on
-&rootprompt; /etc/rc.d/init.d/smb restart
-&rootprompt; /etc/rc.d/init.d/cups restart
-</screen>
- </para></step>
-
- <step><para>
- On Alan's workstation, use Windows Explorer to migrate the files from the old server
- to the new server. The new server should appear in the <guimenu>Network Neighborhood</guimenu>
- with the name of the old server (<constant>CASHPOOL</constant>).
- </para>
-
- <procedure>
-
- <step><para>
- Log on to Alan's workstation as the user <constant>alan</constant>.
- </para></step>
-
- <step><para>
- Launch a second instance of Windows Explorer and navigate to the share called
- <guiicon>files</guiicon> on the server called <guimenu>STABLE</guimenu>.
- </para></step>
-
- <step><para>
- Click in the right panel, and press <guimenu>Ctrl-A</guimenu> to select all files and
- directories. Press <guimenu>Ctrl-C</guimenu> to instruct Windows that you wish to
- copy all selected items.
- </para></step>
-
- <step><para>
- Launch the Windows Explorer, and navigate to the share called <guiicon>files</guiicon>
- on the server called <guimenu>CASHPOOL</guimenu>. Click in the right panel, and then press
- <guimenu>Ctrl-V</guimenu> to commence the copying process.
- </para></step>
-
- </procedure>
- </step>
-
- <step><para>
- Verify that the files are being copied correctly from the Windows NT4 machine to the Samba server.
- This is best done on the Samba server. Check the contents of the directory tree under
- <filename>/data</filename> by executing the following command:
-<screen>
-&rootprompt; ls -aR /data
-</screen>
- Make certain to check the ownership and permissions on all files. If in doubt, execute the following:
-<screen>
-&rootprompt; chown alan /data
-&rootprompt; for i in james suzy ujen peter dale eric jeannie russ
-> do
-> chown $i /data/$i
-> done
-&rootprompt; chgrp -R accts /data
-&rootprompt; chmod -R ug+rwxs,o-r+x /data
-</screen>
- </para></step>
-
- <step><para>
- The migration of all data should now be complete. It is time to validate the installation.
- For this, you should make sure all applications, including printing, work before asking the
- customer to test drive the new network.
- </para></step>
-
- </procedure>
-
-<example id="acctconf">
-<title>Accounting Office Network &smb.conf; Old Style Configuration File</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">BILLMORE</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="disable spoolss">Yes</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[files]"/>
-<smbconfoption name="comment">Work area files</smbconfoption>
-<smbconfoption name="path">/data/%U</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[master]"/>
-<smbconfoption name="comment">Master work area files</smbconfoption>
-<smbconfoption name="path">/data</smbconfoption>
-<smbconfoption name="valid users">alan</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">Print Temporary Spool Configuration</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
- </sect3>
- </sect2>
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- The following questions and answers draw from the examples in this chapter.
- Many design decisions are impacted by the configurations chosen. The intent
- is to expose some of the hidden implications.
- </para>
-
- <qandaset defaultlabel="chap02qa" type="number">
- <qandaentry>
- <question>
-
- <para>
- What makes an anonymous Samba server more simple than a non-anonymous Samba server?
- </para>
-
- </question>
- <answer>
-
- <para>
- In the anonymous server, the only account used is the <constant>guest</constant> account.
- In a non-anonymous configuration, it is necessary to add real user accounts to both the
- UNIX system and to the Samba configuration. Non-anonymous servers require additional
- administration.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- How is the operation of the parameter <parameter>force user</parameter> different from
- setting the root directory of the share SUID?
- </para>
-
- </question>
- <answer>
-
- <para>
- The parameter <parameter>force user</parameter> causes all operations on the share to assume the UID
- of the forced user. The new default GID that applies is the primary GID of the forced user.
- This gives all users of this resource the actual privilege of the forced user.
- </para>
-
- <para>
- When a directory is set SUID, the operating system forces files that are written within it
- to be owned by the owner of the directory. While this happens, the user who is using the share
- has only the level of privilege he or she is assigned within the operating system context.
- </para>
-
- <para>
- The parameter <parameter>force user</parameter> has potential security implications that go
- beyond the actual share root directory. Be careful and wary of using this parameter.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- When would you both use the per share parameter <parameter>force user</parameter> and set
- the share root directory SUID?
- </para>
-
- </question>
- <answer>
-
- <para>
- You would use both parameters when it is necessary to guarantee that all share handling operations
- are conducted as the forced user, while all file and directory creation are done as the SUID
- directory owner.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What is better about CUPS printing than LPRng printing?
- </para>
-
- </question>
- <answer>
-
- <para>
- CUPS is a print spooling system that has integrated remote management facilities, provides completely
- automated print processing/preprocessing, and can be configured to automatically
- apply print preprocessing filters to ensure that a print job submitted is correctly rendered for the
- target printer. CUPS includes an image file RIP that supports printing of image files to
- non-PostScript printers. CUPS has lots of bells and whistles and is more like a supercharged MS Windows
- NT/200x print monitor and processor. Its complexity can be eliminated or turbocharged to suit
- any fancy.
- </para>
-
- <para>
- The LPRng software is an enhanced, extended, and portable implementation of the Berkeley LPR print
- spooler functionality. It provides the same interface and meets RFC1179 requirements. LPRng can be
- configured to act like CUPS, but it is in principle a replacement for the old Berkeley lpr/lpd
- spooler. LPRng is generally preferred by those who are familiar with Berkeley lpr/lpd.
- </para>
-
- <para>
- Which spooling system is better is a matter of personal taste. It depends on what you want to do and how you want to
- do it and manage it. Most modern Linux systems ship with CUPS as the default print management system.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- When should Windows client IP addresses be hard-coded?
- </para>
-
- </question>
- <answer>
-
- <para>
- When there are few MS Windows clients, little client change, no mobile users, and users are not
- inclined to tamper with network settings, it is a safe and convenient matter to hard-code Windows
- client TCP/IP settings. Given that it is possible to lock down the Windows desktop and remove
- user ability to access network configuration controls, fixed configuration eliminates the need
- for a DHCP server. This reduces maintenance overheads and eliminates a possible point of network
- failure.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Under what circumstances is it best to use a DHCP server?
- </para>
-
- </question>
- <answer>
-
- <para>
- In network configurations where there are mobile users, or where Windows client PCs move around
- (particularly between offices or between subnets), it makes complete sense to control all Windows
- client configurations using a DHCP server. Additionally, when users do tamper with the network
- settings, DHCP can be used to normalize all client settings.
- </para>
-
- <para>
- One underappreciated benefit of using a DHCP server to assign all network client
- device TCP/IP settings is that it makes it a pain-free process to change network TCP/IP
- settings, change network addressing, or enhance the ability of client devices to
- benefit from new network services.
- </para>
-
- <para>
- Another benefit of modern DHCP servers is their ability to register dynamically
- assigned IP addresses with the DNS server. The benefits of Dynamic DNS (DDNS) are considerable in
- a large Windows network environment.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What is the purpose of setting the parameter <parameter>guest ok</parameter> on a share?
- </para>
-
- </question>
- <answer>
-
- <para>
- If this parameter is set to yes for a service, then no password is required to connect to the service.
- Privileges are those of the guest account.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- When would you set the global parameter <parameter>disable spoolss</parameter>?
- </para>
-
- </question>
- <answer>
-
- <para>
- Setting this parameter to <constant>Yes</constant> disables Samba's support for the SPOOLSS set of
- MS-RPCs and yields behavior identical to Samba 2.0.x. Windows NT/2000 clients can downgrade to
- using LanMan style printing commands. Windows 9x/Me are unaffected by the parameter. However, this
- disables the ability to upload printer drivers to a Samba server via the Windows NT/200x Add Printer
- Wizard or by using the NT printer properties dialog window. It also disables the capability of
- Windows NT/200x clients to download print drivers from the Samba host on demand. Be extremely careful about
- setting this parameter.
- </para>
-
- <para>
- The alternate parameter <parameter>use client driver</parameter> applies only to Windows NT/200x clients. It has no
- effect on Windows 95/98/Me clients. When serving a printer to Windows NT/200x clients without first installing a valid
- printer driver on the Samba host, the client is required to install a local printer driver. From this point on,
- the client treats the printer as a local printer and not a network printer connection. This is much the same behavior
- that occurs when <parameter>disable spoolss = yes</parameter>.
- </para>
-
- <para>
- Under normal circumstances, the NT/200x client attempts to open the network printer using MS-RPC. Because the client
- considers the printer to be local, it attempts to issue the <parameter>OpenPrinterEx()</parameter> call requesting
- access rights associated with the logged on user. If the user possesses local administrator rights but not root
- privilege on the Samba host (often the case), the <parameter>OpenPrinterEx()</parameter> call fails. The result is
- that the client now displays an <quote>Access Denied; Unable to connect</quote> message in the printer queue window
- (even though jobs may be printed successfully). This parameter MUST not be enabled on a print share that has a valid
- print driver installed on the Samba server.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why would you disable password caching on Windows 9x/Me clients?
- </para>
-
- </question>
- <answer>
-
- <para>
- Windows 9x/Me workstations that are set at default (password caching enabled) store the username and
- password in files located in the Windows master directory. Such files can be scavenged (read off a client
- machine) and decrypted, thus revealing the user's access credentials for all systems the user may have accessed.
- It is most insecure to allow any Windows 9x/Me client to operate with password caching enabled.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- The example of Abmas Accounting uses User Mode security. How does this provide anonymous access?
- </para>
-
- </question>
- <answer>
-
- <para>
- The example used does not provide anonymous access. Since the clients are all Windows 2000 Professional,
- and given that users are logging onto their machines, by default the client attempts to connect to
- a remote server using currently logged in user credentials. By ensuring that the user's login ID and
- password are the same as those set on the Samba server, access is transparent and does not require
- separate user authentication.
- </para>
-
- </answer>
- </qandaentry>
-
- </qandaset>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<chapter lang="en-US">
-<title>Samba Support</title>
-
-<para>
-<indexterm><primary>support</primary></indexterm>
-One of the most difficult to answer questions in the information technology industry is, <quote>What is
-support?</quote>. That question irritates some folks, as much as common answers may annoy others.
-</para>
-
-<para>
-<indexterm><primary>customers</primary></indexterm>
-The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to
-an Internet service provider who, instead of listening to the problem to find a solution, blandly replies:
-<quote>Oh, Linux? We do not support Linux!</quote>. It has happened to me, and similar situations happen
-through-out the IT industry. Answers like that are designed to inform us that there are some customers
-that a business just does not want to deal with, and well may we feel the anguish of the rejection that
-is dished out.
-</para>
-
-<para>
-One way to consider support is to view it as consisting of the right answer, in the right place,
-at the right time, no matter the situation. Support is all that it takes to take away pain, disruption,
-inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.
-</para>
-
-<para>
-<indexterm><primary>provided services</primary></indexterm>
-<indexterm><primary>services provided</primary></indexterm>
-<indexterm><primary>customer expected</primary></indexterm>
-One of the forces that has become a driving force for the adoption of open source software is the fact that
-many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or
-that have been found wanting for other reasons.
-</para>
-
-<para>
-<indexterm><primary>consumer expects</primary></indexterm>
-<indexterm><primary>problem resolution</primary></indexterm>
-In recognition of the need for needs satisfaction as the primary experience an information technology user or
-consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience
-in respect of problem resolution.
-</para>
-
-<para>
-<indexterm><primary>free support</primary></indexterm>
-<indexterm><primary>paid-for support</primary></indexterm>
-<indexterm><primary>commercial support</primary></indexterm>
-In the open source software arena there are two support options: free support and paid-for (commercial)
-support.
-</para>
-
- <sect1>
- <title>Free Support</title>
-
- <para>
-<indexterm><primary>user groups</primary></indexterm>
-<indexterm><primary>mailing lists</primary></indexterm>
-<indexterm><primary>interactive help</primary></indexterm>
-<indexterm><primary>help</primary></indexterm>
-<indexterm><primary>mutual assistance</primary></indexterm>
-<indexterm><primary>assistance</primary></indexterm>
- Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help
- facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user
- supported mutual assistance.
- </para>
-
- <para>
-<indexterm><primary>mailing list</primary></indexterm>
-<indexterm><primary>deployment</primary></indexterm>
-<indexterm><primary>subscription</primary></indexterm>
-<indexterm><primary>IRC</primary></indexterm>
-<indexterm><primary>project</primary></indexterm>
- The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments.
- Information regarding subscription to the Samba mailing list can be found on the Samba <ulink
- url="https://lists.samba.org/mailman/">web</ulink> site. The public mailing list that can be used to obtain
- free, user contributed, support is called the <literal>samba</literal> list. The email address for this list
- is at <literal>mail:samba@lists.samba.org</literal>. Information regarding the Samba IRC channels may be found on
- the Samba <ulink url="http://www.samba.org/samba.irc.html">IRC</ulink> web page.
- </para>
-
- <para>
-<indexterm><primary>free support</primary></indexterm>
-<indexterm><primary>qualified problem</primary></indexterm>
-<indexterm><primary>requesting payment</primary></indexterm>
-<indexterm><primary>professional support</primary></indexterm>
- As a general rule, it is considered poor net behavior to contact a Samba Team member directly
- for free support. Most active members of the Samba Team work exceptionally long hours to assist
- users who have demonstrated a qualified problem. Some team members may respond to direct email
- or telephone contact, with requests for assistance, by requesting payment. A few of the Samba
- Team members actually provide professional paid-for Samba support and it is therefore wise
- to show appropriate discretion and reservation in all direct contact.
- </para>
-
- <para>
-<indexterm><primary>bug report</primary></indexterm>
-<indexterm><primary>problem report</primary></indexterm>
-<indexterm><primary>code maintainer</primary></indexterm>
- When you stumble across a Samba bug, often the quickest way to get it resolved is by posting
- a bug <ulink url="https://bugzilla.samba.org/">report</ulink>. All such reports are mailed to
- the responsible code maintainer for action. The better the report, and the more serious it is,
- the sooner it will be dealt with. On the other hand, if the responsible person can not duplicate
- the reported bug it is likely to be rejected. It is up to you to provide sufficient information
- that will permit the problem to be reproduced.
- </para>
-
- <para>
-<indexterm><primary>purchase support</primary></indexterm>
- We all recognize that sometimes free support does not provide the answer that is sought within
- the time-frame required. At other times the problem is elusive and you may lack the experience
- necessary to isolate the problem and thus to resolve it. This is a situation where is may be
- prudent to purchase paid-for support.
- </para>
-
- </sect1>
-
- <sect1>
- <title>Commercial Support</title>
-
- <para>
- There are six basic support oriented services that are most commonly sought by Samba sites:
- </para>
-
- <itemizedlist>
- <listitem><para>Assistance with network design</para></listitem>
- <listitem><para>Staff Training</para></listitem>
- <listitem><para>Assistance with Samba network deployment and installation</para></listitem>
- <listitem><para>Priority telephone or email Samba configuration assistance</para></listitem>
- <listitem><para>Trouble-shooting and diagnostic assistance</para></listitem>
- <listitem><para>Provision of quality assured ready-to-install Samba binary packages</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>commercial support</primary></indexterm>
-<indexterm><primary>country of origin</primary></indexterm>
- Information regarding companies that provide professional Samba support can be obtained by performing a Google
- search, as well as by reference to the Samba <ulink
- url="http://www.samba.org/samba/support.html">Support</ulink> web page. Companies who notify the Samba Team
- that they provide commercial support are given a free listing that is sorted by the country of origin.
- Multiple listings are permitted, however no guarantee is offered. It is left to you to qualify a support
- provider and to satisfy yourself that both the company and its staff are able to deliver what is required of
- them.
- </para>
-
- <para>
-<indexterm><primary>commercial support</primary></indexterm>
- The policy within the Samba Team is to treat all commercial support providers equally and to show no
- preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else.
- You are encouraged to obtain the services needed from a company in your local area. The open source movement
- is pro-community; so do what you can to help a local business to prosper.
- </para>
-
- <para>
-<indexterm><primary>unsupported software</primary></indexterm>
- Open source software support can be found in any quality, at any price and in any place you can
- to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for
- suffering in the mistaken belief that Samba is unsupported software &smbmdash; it is supported.
- </para>
-
- </sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="small">
- <title>Small Office Networking</title>
-
- <para>
- <link linkend="simple"/> focused on the basics of simple yet effective
- network solutions. Network administrators who take pride in their work
- (that's most of us, right?) take care to deliver what our users want,
- but not too much more. If we make things too complex, we confound our users
- and increase costs of network ownership. A professional network manager
- avoids the temptation to put too much pizazz into the way that the network
- operates. Some creativity is helpful, but keep it under control &smbmdash;
- good advice that the following two scenarios illustrate.
- </para>
-
- <para>
- <indexterm><primary>Netware</primary></indexterm>
- In one case the network administrator of a mid-sized company spent three
- months building a new network to replace an old Netware server. What he
- delivered had all the bells and whistles he could muster. There were a
- few teething problems during the changeover, nothing serious but a little
- disruptive all the same. Users were exposed to many changes at once. The
- network administrator was asked to resign two months after implementing
- the new system because so many staff complained they had lost time and
- were not happy with the new network. Everything was automated, and he
- delivered more features than any advanced user could think of. He was
- just too smart for his own good.
- </para>
-
- <para>
- In the case of the other company, a new network manager was appointed
- to oversee the replacement of a LanTastic network with an MS Windows
- NT 4.0 network. He had the replacement installed and operational within
- two weeks. Before installation and changeover, he called a meeting to
- explain to all users what was going to happen, how it would affect them,
- and that he would be available 24 hours a day to help them transition.
- One week after conversion, he held another meeting asking for cooperation
- in the introduction of a few new features that would help to make life
- easier. Network users were thrilled with the help he provided. The network
- he implemented was nowhere near as complex as in the first example, had fewer
- features, and yet he had happy users. Months later he was still adding
- new innovations. He always asked the users if a
- particular feature was what they wanted. He asked his boss for a raise
- and got it. He often told me, <quote>Always keep a few new tricks up your
- sleeves for when you need them.</quote> Was he smart? You decide. Let's
- get on with our next exercise.
- </para>
-
-<sect1>
- <title>Introduction</title>
-
- <para>
- Abmas Accounting has grown. Mr. Meany likes you and says he knew you
- were the right person for the job. That's why he asked you to install the
- new server. The past few months have been hard work. You advised Mr. Meany
- that it is time for a change. Abmas now has 52 users, having acquired an
- investment consulting business recently. The new users were added to the
- network without any problems.
- </para>
-
- <para>
- Some of the Windows clients are nearly past their use-by date. You found damaged and unusable software on
- some of the workstations that came with the acquired business and found some machines in need of both
- hardware and software maintenance.
- </para>
-
- <sect2>
- <title>Assignment Tasks</title>
-
- <para>
- <indexterm><primary>Windows XP</primary></indexterm>
- Mr. Meany is retiring in 12 months. Before he goes, he wants you to help ensure
- that the business is running efficiently. Many of the new staff want notebook
- computers. They visit customer business premises and need to use local network
- facilities; these users are technically competent. The company uses a
- business application that requires Windows XP Professional. In short, a complete
- client upgrade is about to happen. Mr. Meany told you that he is working
- on another business acquisition and that by the time he retires there will be
- 80 to 100 users.
- </para>
-
- <para>
- Mr. Meany is not concerned about security. He wants to make it easier for
- staff to do their work. He has hired you to help him appoint a full-time
- network manager before he retires. Above all, he says he is investing in
- the ability to grow. He is determined to live his lifelong dream and
- hand the business over to a bright and capable executive who can make
- things happen. This means your network design must cope well with
- growth.
- </para>
-
- <para>
- In a few months, Abmas will require an Internet connection for email and so
- that staff can easily obtain software updates. Mr. Meany is warming up to
- the installation of antivirus software but is not yet ready to approve
- this expense. He told you to spend the money a virus scanner costs
- on better quality notebook computers for mobile users.
- </para>
-
- <para>
- One of Mr. Meany's golfing partners convinced him to buy new laser
- printers, one black only, the other a color laser printer. Staff support
- the need for a color printer so they can present more attractive proposals
- and reports.
- </para>
-
- <para>
- Mr. Meany also asked if it would be possible for one of the staff to manage
- user accounts from the Windows desktop. That person will be responsible for
- basic operations.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
- <title>Dissection and Discussion</title>
-
- <para>
- What are the key requirements in this business example? A quick review indicates
- a need for
- </para>
-
- <itemizedlist>
- <listitem><para>
- Scalability, from 52 to over 100 users in 12 months
- </para></listitem>
-
- <listitem><para>
- Mobile computing capability
- <indexterm><primary>mobile computing</primary></indexterm>
- </para></listitem>
-
- <listitem><para>
- Improved reliability and usability
- </para></listitem>
-
- <listitem><para>
- Easier administration
- </para></listitem>
- </itemizedlist>
-
- <para>
- In this instance the installed Linux system is assumed to be a Red Hat Linux Fedora Core2 server
- (as in <link linkend="AccountingOffice"/>).
-
- </para>
-
-
- <sect2>
- <title>Technical Issues</title>
-
- <para>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>DHCP</primary></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>Domain</primary></indexterm>
- It is time to implement a domain security environment. You will use the <constant>
- smbpasswd</constant> (default) backend. You should implement a DHCP server. There is no need to
- run DNS at this time, but the system will use WINS. The domain name will be <constant>
- BILLMORE</constant>. This time, the name of the server will be <constant>SLEETH</constant>.
- </para>
-
- <para>
- All printers will be configured as DHCP clients. The DHCP server will assign
- the printer a fixed IP address by way of its Ethernet interface (MAC) address.
- See <link linkend="dhcp01"/>.
- </para>
-
- <note><para>
- The &smb.conf; file you are creating in this exercise can be used with equal effectiveness
- with Samba-2.2.x series releases. This is deliberate so that in the next chapter it is
- possible to start with the installation that you have created here, migrate it
- to a Samba configuration, and then secure the system further. Configurations following
- this one utilize features that may not be supported in Samba-2.2.x releases.
- However, you should note that the examples in each chapter start with the assumption
- that a fresh new installation is being effected.
- </para></note>
-
- <para>
- Later on, when the Internet connection is implemented, you will add DNS as well as
- other enhancements. It is important that you plan accordingly.
- </para>
-
- <para>
- <indexterm><primary>Ethernet switch</primary></indexterm>
- You have split the network into two separate areas. Each has its own Ethernet switch.
- There are 20 users on the accounting network and 32 users on the financial services
- network. The server has two network interfaces, one serving each network. The
- network printers will be located in a central area. You plan to install the new
- printers and keep the old printer in use also.
- </para>
-
- <para>
- You will provide separate file storage areas for each business entity. The old system
- will go away, accounting files will be handled under a single directory, and files will
- be stored under customer name, not under a personal work area. Staff will be made
- responsible for file location, so the old share point must be maintained.
- </para>
-
- <para>
- Given that DNS will not be used, you will configure WINS name resolution for UNIX
- hostname name resolution.
- </para>
-
- <para>
- <indexterm><primary>Domain</primary><secondary>groups</secondary></indexterm>
- <indexterm><primary>UNIX</primary><secondary>groups</secondary></indexterm>
- It is necessary to map Windows Domain Groups to UNIX groups. It is
- advisable to also map Windows Local Groups to UNIX groups. Additionally, the two
- key staff groups in the firm are accounting staff and financial services staff.
- For these, it is necessary to create UNIX groups as well as Windows Domain Groups.
- </para>
-
- <para>
- In the sample &smb.conf; file, you have configured Samba to call the UNIX
- <command>groupadd</command> to add group entries. This utility does not permit
- the addition of group names that contain uppercase characters or spaces. This
- is considered a bug. The <command>groupadd</command> is part of the
- <command>shadow-utils</command> open source software package. A later release
- of this package may have been patched to resolve this bug. If your operating
- platform has this bug, it means that attempts to add a Windows Domain Group that
- has either a space or uppercase characters in it will fail. See
- <emphasis>TOSHARG2</emphasis>, Chapter 11, Section 11.3.1, Example 11.1, for
- more information.
- </para>
-
- <para>
- <indexterm><primary>CUPS</primary></indexterm>
- Vendor-supplied printer drivers will be installed on each client. The CUPS print
- spooler on the UNIX host will be operated in <constant>raw</constant> mode.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Political Issues</title>
-
- <para>
- Mr. Meany is an old-school manager. He sets the rules and wants to see compliance.
- He is willing to spend money on things he believes are of value. You need more
- time to convince him of real priorities.
- </para>
-
- <para>
- Go ahead, buy better notebooks. Wouldn't it be neat if they happened to be
- supplied with antivirus software? Above all, demonstrate good purchase value and remember
- to make your users happy.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Implementation</title>
-
- <para>
- <indexterm><primary>migration</primary></indexterm>
- In this example, the assumption is made that this server is being configured from a clean start.
- The alternate approach could be to demonstrate the migration of the system that is documented
- in <link linkend="AcctgNet"/> to meet the new requirements. The decision to treat this case, as with
- future examples, as a new installation is based on the premise that you can determine
- the migration steps from the information provided in <link linkend="ntmigration"/>.
- Additionally, a fresh installation makes the example easier to follow.
- </para>
-
- <para>
- <indexterm><primary>group membership</primary></indexterm>
- Each user will be given a home directory on the UNIX system, which will be available as a private
- share. Two additional shares will be created, one for the accounting department and the other for
- the financial services department. Network users will be given access to these shares by way
- of group membership.
- </para>
-
- <para>
- <indexterm><primary>UNIX</primary><secondary>groups</secondary></indexterm>
- UNIX group membership is the primary mechanism by which Windows Domain users will be granted
- rights and privileges within the Windows environment.
- </para>
-
- <para>
- <indexterm><primary>sticky bit</primary></indexterm>
- The user <command>alanm</command> will be made the owner of all files. This will be preserved
- by setting the sticky bit (set UID/GID) on the top-level directories.
- </para>
-
- <para>
- <figure id="acct2net">
- <title>Abmas Accounting &smbmdash; 52-User Network Topology</title>
- <imagefile scale="100">acct2net</imagefile>
- </figure>
-</para>
-
- <procedure>
- <title>Server Installation Steps</title>
-
- <step><para>
- Using UNIX/Linux system tools, name the server <constant>sleeth</constant>.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/hosts</primary></indexterm>
- Place an entry for the machine <constant>sleeth</constant> in the <filename>/etc/hosts</filename>.
- The printers are network attached, so there should be entries for the
- network printers also. An example <filename>/etc/hosts</filename> file is shown here:
-<screen>
-192.168.1.1 sleeth sleeth1
-192.168.2.1 sleeth2
-192.168.1.10 hplj6
-192.168.1.11 hplj4
-192.168.2.10 qms
-</screen>
- </para></step>
-
- <step><para>
- Install the Samba binary RPM from the Samba-Team FTP site.
- </para></step>
-
- <step><para>
- Install the ISC DHCP server using the UNIX/Linux system tools available to you.
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/rc.d/rc.local</primary></indexterm>
- <indexterm><primary>IP forwarding</primary></indexterm>
- <indexterm><primary>router</primary></indexterm>
- <indexterm><primary>/proc/sys/net/ipv4/ip_forward</primary></indexterm>
- Because Samba will be operating over two network interfaces and clients on each side
- may want to be able to reach clients on the other side, it is imperative that IP forwarding
- is enabled. Use the system tool of your choice to enable IP forwarding. In the
- absence of such a tool on the Linux system, add to the <filename>/etc/rc.d/rc.local</filename>
- file an entry as follows:
-<screen>
-echo 1 > /proc/sys/net/ipv4/ip_forward
-</screen>
- This causes the Linux kernel to forward IP packets so that it acts as a router.
- </para></step>
-
- <step><para>
- Install the &smb.conf; file as shown in <link linkend="acct2conf"/> and
- <link linkend="acct3conf"/>. Combine these two examples to form a single
- <filename>/etc/samba/smb.conf</filename> file.
- </para></step>
-
- <step><para>
- <indexterm><primary>smbpasswd</primary></indexterm>
- Add the user <command>root</command> to the Samba password backend:
-<screen>
-&rootprompt; smbpasswd -a root
-New SMB password: XXXXXXX
-Retype new SMB password: XXXXXXX
-&rootprompt;
-</screen>
- <indexterm><primary>administrator</primary></indexterm>
- This is the Windows Domain Administrator password. Never delete this account from
- the password backend after Windows Domain Groups have been initialized. If you delete
- this account, your system is crippled. You cannot restore this account,
- and your Samba server can no longer be administered.
- </para></step>
-
- <step><para>
- <indexterm><primary>username map</primary></indexterm>
- Create the username map file to permit the <constant>root</constant> account to be called
- <constant>Administrator</constant> from the Windows network environment. To do this, create
- the file <filename>/etc/samba/smbusers</filename> with the following contents:
-<screen>
-####
-# User mapping file
-####
-# File Format
-# -----------
-# Unix_ID = Windows_ID
-#
-# Examples:
-# root = Administrator
-# janes = "Jane Smith"
-# jimbo = Jim Bones
-#
-# Note: If the name contains a space it must be double quoted.
-# In the example above the name 'jimbo' will be mapped to Windows
-# user names 'Jim' and 'Bones' because the space was not quoted.
-#######################################################################
-root = Administrator
-####
-# End of File
-####
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>initGrps.sh</primary></indexterm>
- Create and map Windows Domain Groups to UNIX groups. A sample script is provided in
- <link linkend="initGrps"/>. Create a file containing this script. We called ours
- <filename>/etc/samba/initGrps.sh</filename>. Set this file so it can be executed,
- and then execute the script. Sample output should be as follows:
-
-<example id="initGrps">
-<title>Script to Map Windows NT Groups to UNIX Groups</title>
-<indexterm><primary>initGrps.sh</primary></indexterm>
-<screen>
-#!/bin/bash
-#
-# initGrps.sh
-#
-
-# Create UNIX groups
-groupadd acctsdep
-groupadd finsrvcs
-
-# Map Windows Domain Groups to UNIX groups
-net groupmap add ntgroup="Domain Admins" unixgroup=root type=d
-net groupmap add ntgroup="Domain Users" unixgroup=users type=d
-net groupmap add ntgroup="Domain Guests" unixgroup=nobody type=d
-
-# Add Functional Domain Groups
-net groupmap add ntgroup="Accounts Dept" unixgroup=acctsdep type=d
-net groupmap add ntgroup="Financial Services" unixgroup=finsrvcs type=d
-</screen>
-</example>
-
-<screen>
-&rootprompt; chmod 755 initGrps.sh
-&rootprompt; cd /etc/samba
-&rootprompt; ./initGrps.sh
-Updated mapping entry for Domain Admins
-Updated mapping entry for Domain Users
-Updated mapping entry for Domain Guests
-No rid or sid specified, choosing algorithmic mapping
-Successfully added group Accounts Dept to the mapping db
-No rid or sid specified, choosing algorithmic mapping
-Successfully added group Domain Guests to the mapping db
-
-&rootprompt; cd /etc/samba
-&rootprompt; net groupmap list | sort
-Account Operators (S-1-5-32-548) -> -1
-Accounts Dept (S-1-5-21-194350-25496802-3394589-2003) -> acctsdep
-Administrators (S-1-5-32-544) -> -1
-Backup Operators (S-1-5-32-551) -> -1
-Domain Admins (S-1-5-21-194350-25496802-3394589-512) -> root
-Domain Guests (S-1-5-21-194350-25496802-3394589-514) -> nobody
-Domain Users (S-1-5-21-194350-25496802-3394589-513) -> users
-Financial Services (S-1-5-21-194350-25496802-3394589-2005) -> finsrvcs
-Guests (S-1-5-32-546) -> -1
-Power Users (S-1-5-32-547) -> -1
-Print Operators (S-1-5-32-550) -> -1
-Replicators (S-1-5-32-552) -> -1
-System Operators (S-1-5-32-549) -> -1
-Users (S-1-5-32-545) -> -1
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>password</primary><secondary>backend</secondary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- For each user who needs to be given a Windows Domain account, make an entry in the
- <filename>/etc/passwd</filename> file as well as in the Samba password backend.
- Use the system tool of your choice to create the UNIX system accounts, and use the Samba
- <command>smbpasswd</command> program to create the Domain user accounts.
- </para>
-
- <para>
- <indexterm><primary>useradd</primary></indexterm>
- <indexterm><primary>adduser</primary></indexterm>
- <indexterm><primary>user</primary><secondary>management</secondary></indexterm>
- There are a number of tools for user management under UNIX, such as
- <command>useradd</command> and <command>adduser</command>, as well as a plethora of custom
- tools. With the tool of your choice, create a home directory for each user.
- </para></step>
-
- <step><para>
- Using the preferred tool for your UNIX system, add each user to the UNIX groups created
- previously, as necessary. File system access control will be based on UNIX group membership.
- </para></step>
-
- <step><para>
- Create the directory mount point for the disk subsystem that is mounted to provide
- data storage for company files. In this case the mount point is indicated in the &smb.conf;
- file is <filename>/data</filename>. Format the file system as required, mount the formatted
- file system partition using <command>mount</command>,
- and make the appropriate changes in <filename>/etc/fstab</filename>.
- </para></step>
-
- <step><para>
- Create the top-level file storage directories are follows:
-<screen>
-&rootprompt; mkdir -p /data/{accounts,finsvcs}
-&rootprompt; chown -R root:root /data
-&rootprompt; chown -R alanm:acctsdep /data/accounts
-&rootprompt; chown -R alanm:finsrvcs /data/finsrvcs
-&rootprompt; chmod -R ug+rwx,o+rx-w /data
-</screen>
- Each department is responsible for creating its own directory structure within its
- share. The directory root of the <command>accounts</command> share is <filename>/data/accounts</filename>.
- The directory root of the <command>finsvcs</command> share is <filename>/data/finsvcs</filename>.
- </para></step>
-
- <step><para>
- Configure the printers with the IP addresses as shown in <link linkend="acct2net"/>.
- Follow the instructions in the manufacturers' manuals to permit printing to port 9100.
- This allows the CUPS spooler to print using raw mode protocols.
- <indexterm><primary>CUPS</primary></indexterm>
- <indexterm><primary>raw printing</primary></indexterm>
- </para></step>
-
- <step><para>
- <indexterm><primary>CUPS</primary><secondary>queue</secondary></indexterm>
- <indexterm><primary>lpadmin</primary></indexterm>
- Configure the CUPS Print Queues as follows:
-<screen>
-&rootprompt; lpadmin -p hplj4 -v socket://192.168.1.11:9100 -E
-&rootprompt; lpadmin -p hplj6 -v socket://192.168.1.10:9100 -E
-&rootprompt; lpadmin -p qms -v socket://192.168.2.10:9100 -E
-</screen>
- <indexterm><primary>print filter</primary></indexterm>
- This creates the necessary print queues with no assigned print filter.
- </para></step>
-
- <step><para>
- <indexterm><primary>mime type</primary></indexterm>
- <indexterm><primary>/etc/mime.convs</primary></indexterm>
- <indexterm><primary>application/octet-stream</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.convs</filename> to uncomment the line:
-<screen>
-application/octet-stream application/vnd.cups-raw 0 -
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>/etc/mime.types</primary></indexterm>
- Edit the file <filename>/etc/cups/mime.types</filename> to uncomment the line:
-<screen>
-application/octet-stream
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>DHCP Server</primary></indexterm>
- Using your favorite system editor, create an <filename>/etc/dhcpd.conf</filename> with the
- contents as shown in <link linkend="dhcp01"/>.
-<example id="dhcp01">
-<title>Abmas Accounting DHCP Server Configuration File &smbmdash; <filename>/etc/dhcpd.conf</filename></title>
-<indexterm><primary>/etc/dhcpd.conf</primary></indexterm>
-<screen>
-default-lease-time 86400;
-max-lease-time 172800;
-default-lease-time 86400;
-
-option ntp-servers 192.168.1.1;
-option domain-name "abmas.biz";
-option domain-name-servers 192.168.1.1, 192.168.2.1;
-option netbios-name-servers 192.168.1.1, 192.168.2.1;
-option netbios-node-type 8;
-### NOTE ###
-# netbios-node-type=8 means set clients to Hybrid Mode
-# so they will use Unicast communication with the WINS
-# server and thus reduce the level of UDP broadcast
-# traffic by up to 90%.
-############
-
-subnet 192.168.1.0 netmask 255.255.255.0 {
- range dynamic-bootp 192.168.1.128 192.168.1.254;
- option subnet-mask 255.255.255.0;
- option routers 192.168.1.1;
- allow unknown-clients;
- host hplj4 {
- hardware ethernet 08:00:46:7a:35:e4;
- fixed-address 192.168.1.10;
- }
- host hplj6 {
- hardware ethernet 00:03:47:cb:81:e0;
- fixed-address 192.168.1.11;
- }
- }
-subnet 192.168.2.0 netmask 255.255.255.0 {
- range dynamic-bootp 192.168.2.128 192.168.2.254;
- option subnet-mask 255.255.255.0;
- option routers 192.168.2.1;
- allow unknown-clients;
- host qms {
- hardware ethernet 01:04:31:db:e1:c0;
- fixed-address 192.168.1.10;
- }
- }
-subnet 127.0.0.0 netmask 255.0.0.0 {
- }
-</screen>
-</example>
- </para></step>
-
-
- <step><para>
- Use the standard system tool to start Samba and CUPS and configure them to start
- automatically at every system reboot. For example,
- </para>
-
- <para>
- <indexterm><primary>chkconfig</primary></indexterm>
- <indexterm><primary>starting dhcpd</primary></indexterm>
- <indexterm><primary>starting samba</primary></indexterm>
- <indexterm><primary>starting CUPS</primary></indexterm>
- <indexterm><primary>chkconfig</primary></indexterm>
-<screen>
-&rootprompt; chkconfig dhcp on
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig cups on
-&rootprompt; /etc/rc.d/init.d/dhcp restart
-&rootprompt; /etc/rc.d/init.d/smb restart
-&rootprompt; /etc/rc.d/init.d/cups restart
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>name service switch</primary></indexterm>
- <indexterm><primary>NSS</primary><see>same service switch</see></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- <indexterm><primary>DNS server</primary></indexterm>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- Configure the name service switch (NSS) to handle WINS-based name resolution.
- Since this system does not use a DNS server, it is safe to remove this option from
- the NSS configuration. Edit the <filename>/etc/nsswitch.conf</filename> file so that
- the <constant>hosts:</constant> entry looks like this:
-<screen>
-hosts: files wins
-</screen>
- </para></step>
-
- </procedure>
-
-<example id="acct2conf">
-<title>Accounting Office Network &smb.conf; File &smbmdash; [globals] Section</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">BILLMORE</smbconfoption>
-<smbconfoption name="passwd chat">*New*Password* %n\n*Re-enter*new*password* %n\n *Password*changed*</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="name resolve order">wins bcast hosts</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="add user script">/usr/sbin/useradd -m -G users '%u'</smbconfoption>
-<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
-<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
-<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
-<smbconfoption name="add user to group script">/usr/sbin/usermod -A '%g' '%u'</smbconfoption>
-<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</smbconfoption>
-<smbconfoption name="logon script">scripts\login.bat</smbconfoption>
-<smbconfoption name="logon path"> </smbconfoption>
-<smbconfoption name="logon drive">X:</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="wins support">Yes</smbconfoption>
-<smbconfoption name="printing">CUPS</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="acct3conf">
-<title>Accounting Office Network &smb.conf; File &smbmdash; Services and Shares Section</title>
-<smbconfblock>
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">SMB Print Spool</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network Logon Service</smbconfoption>
-<smbconfoption name="path">/data/%U</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[accounts]"/>
-<smbconfoption name="comment">Accounting Files</smbconfoption>
-<smbconfoption name="path">/data/accounts</smbconfoption>
-<smbconfoption name="valid users">%G</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[finsrvcs]"/>
-<smbconfoption name="comment">Financial Service Files</smbconfoption>
-<smbconfoption name="path">/data/finsrvcs</smbconfoption>
-<smbconfoption name="valid users">%G</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-</smbconfblock>
-</example>
-
- <sect2>
- <title>Validation</title>
-
- <para>
- Does everything function as it ought? That is the key question at this point.
- Here are some simple steps to validate your Samba server configuration.
- </para>
-
- <procedure>
- <title>Validation Steps</title>
-
- <step><para>
- <indexterm><primary>testparm</primary></indexterm>
- If your &smb.conf; file has bogus options or parameters, this may cause Samba
- to refuse to start. The first step should always be to validate the contents
- of this file by running:
-<screen>
-&rootprompt; testparm -s
-Load smb config files from smb.conf
-Processing section "[homes]"
-Processing section "[printers]"
-Processing section "[netlogon]"
-Processing section "[accounts]"
-Processing section "[service]"
-Loaded services file OK.
-# Global parameters
-[global]
- workgroup = BILLMORE
- passwd chat = *New*Password* \
- %n\n *Re-enter*new*password* %n\n *Password*changed*
- username map = /etc/samba/smbusers
- syslog = 0
- name resolve order = wins bcast hosts
- printcap name = CUPS
- show add printer wizard = No
- add user script = /usr/sbin/useradd -m -G users '%u'
- delete user script = /usr/sbin/userdel -r '%u'
- add group script = /usr/sbin/groupadd '%g'
- delete group script = /usr/sbin/groupdel '%g'
- add user to group script = /usr/sbin/usermod -A '%g' '%u'
- add machine script = /usr/sbin/useradd
- -s /bin/false -d /var/lib/nobody '%u'
- logon script = scripts\logon.bat
- logon path =
- logon drive = X:
- domain logons = Yes
- preferred master = Yes
- wins support = Yes
-...
-### Remainder cut to save space ###
-</screen>
- The inclusion of an invalid parameter (say one called dogbert) would generate an
- error as follows:
-<screen>
-Unknown parameter encountered: "dogbert"
-Ignoring unknown parameter "dogbert"
-</screen>
- Clear away all errors before proceeding, and start or restart samba as necessary.
- </para></step>
-
- <step><para>
- <indexterm><primary>check samba daemons</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- Check that the Samba server is running:
-<screen>
-&rootprompt; ps ax | grep mbd
-14244 ? S 0:00 /usr/sbin/nmbd -D
-14245 ? S 0:00 /usr/sbin/nmbd -D
-14290 ? S 0:00 /usr/sbin/smbd -D
-
-$rootprompt; ps ax | grep winbind
-14293 ? S 0:00 /usr/sbin/winbindd -D
-14295 ? S 0:00 /usr/sbin/winbindd -D
-</screen>
- The <command>winbindd</command> daemon is running in split mode (normal), so there are also
- two instances of it. For more information regarding <command>winbindd</command>, see
- <emphasis>TOSHARG2</emphasis>, Chapter 23, Section 23.3. The single instance of
- <command>smbd</command> is normal.
- </para></step>
-
- <step><para>
- <indexterm><primary>anonymous connection</primary></indexterm>
- Check that an anonymous connection can be made to the Samba server:
-<screen>
-&rootprompt; smbclient -L localhost -U%
-
- Sharename Type Comment
- --------- ---- -------
- netlogon Disk Network Logon Service
- accounts Disk Accounting Files
- finsvcs Disk Financial Service Files
- IPC$ IPC IPC Service (Samba3)
- ADMIN$ IPC IPC Service (Samba3)
- hplj4 Printer Hewlett-Packard LaserJet 4
- hplj6 Printer Hewlett-Packard LaserJet 6
- qms Printer QMS Magicolor Laser Printer XXXX
-
- Server Comment
- --------- -------
- SLEETH Samba 3.0.20
-
- Workgroup Master
- --------- -------
- BILLMORE SLEETH
-</screen>
- This demonstrates that an anonymous listing of shares can be obtained. This is the equivalent
- of browsing the server from a Windows client to obtain a list of shares on the server.
- The <constant>-U%</constant> argument means to send a <constant>NULL</constant> username and
- a <constant>NULL</constant> password.
- </para></step>
-
- <step><para>
- <indexterm><primary>dhcp client validation</primary></indexterm>
- <indexterm><primary>printer validation</primary></indexterm>
- <indexterm><primary>/etc/dhcpd.conf</primary></indexterm>
- Verify that the printers have the IP addresses assigned in the DHCP server configuration file.
- The easiest way to do this is to ping the printer name. Immediately after the ping response
- has been received, execute <command>arp -a</command> to find the MAC address of the printer
- that has responded. Now you can compare the IP address and the MAC address of the printer
- with the configuration information in the <filename>/etc/dhcpd.conf</filename> file. They
- should, of course, match. For example,
-<screen>
-&rootprompt; ping hplj4
-PING hplj4 (192.168.1.11) 56(84) bytes of data.
-64 bytes from hplj4 (192.168.1.11): icmp_seq=1 ttl=64 time=0.113 ms
-
-&rootprompt; arp -a
-hplj4 (192.168.1.11) at 08:00:46:7A:35:E4 [ether] on eth0
-</screen>
- The MAC address <constant>08:00:46:7A:35:E4</constant> matches that specified for the
- IP address from which the printer has responded and the entry for it in the
- <filename>/etc/dhcpd.conf</filename> file.
- </para></step>
-
- <step><para>
- <indexterm><primary>authenticated connection</primary></indexterm>
- Make an authenticated connection to the server using the <command>smbclient</command> tool:
-<screen>
-&rootprompt; smbclient //sleeth/accounts -U alanm
-Password: XXXXXXX
-smb: \> dir
- . D 0 Sun Nov 9 01:28:34 2003
- .. D 0 Sat Aug 16 17:24:26 2003
- .mc DH 0 Sat Nov 8 21:57:38 2003
- .qt DH 0 Fri Sep 5 00:48:25 2003
- SMB D 0 Sun Oct 19 23:04:30 2003
- Documents D 0 Sat Nov 1 00:31:51 2003
- xpsp1a_en_x86.exe 131170400 Sun Nov 2 01:25:44 2003
-
- 65387 blocks of size 65536. 28590 blocks available
-smb: \> q
-</screen>
- </para></step>
-
- </procedure>
-
- </sect2>
-
-
- <procedure>
- <title>Windows XP Professional Client Configuration</title>
-
- <step><para>
- Configure clients to the network settings shown in <link linkend="acct2net"/>.
- All clients use DHCP for TCP/IP protocol stack configuration.
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>DHCP</primary></indexterm>
- DHCP configures all Windows clients to use the WINS Server address <constant>192.168.1.1</constant>.
- </para></step>
-
- <step><para>
- Join the Windows Domain called <constant>BILLMORE</constant>. Use the Domain Administrator
- username <constant>root</constant> and the SMB password you assigned to this account.
- A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to
- a Windows Domain is given in <link linkend="appendix"/>, <link linkend="domjoin"/>.
- Reboot the machine as prompted and then log on using a Domain User account.
- </para></step>
-
- <step><para>
- Verify on each client that the machine called <constant>SLEETH</constant>
- is visible in <guimenu>My Network Places</guimenu>, that it is
- possible to connect to it and see the shares <guimenuitem>accounts</guimenuitem>
- and <guimenuitem>finsvcs</guimenuitem>,
- and that it is possible to open that share to reveal its contents.
- </para></step>
-
- <step><para>
- Instruct all users to log onto the workstation using their assigned username and password.
- </para></step>
-
- <step><para>
- Install a printer on each using the following steps:
- </para>
-
- <procedure>
- <step><para>
- Click <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Settings</guimenuitem>
- <guimenuitem>Printers</guimenuitem>
- <guiicon>Add Printer</guiicon>
- <guibutton>Next</guibutton>
- </menuchoice>. Do not click <guimenuitem>Network printer</guimenuitem>.
- Ensure that <guimenuitem>Local printer</guimenuitem> is selected.
- </para></step>
-
- <step><para>
- Click <guibutton>Next</guibutton>. In the
- <guimenuitem>Manufacturer:</guimenuitem> panel, select <constant>HP</constant>.
- In the <guimenuitem>Printers:</guimenuitem> panel, select the printer called
- <constant>HP LaserJet 4</constant>. Click <guibutton>Next</guibutton>.
- </para></step>
-
- <step><para>
- In the <guimenuitem>Available ports:</guimenuitem> panel, select
- <constant>FILE:</constant>. Accept the default printer name by clicking
- <guibutton>Next</guibutton>. When asked, <quote>Would you like to print a
- test page?</quote>, click <guimenuitem>No</guimenuitem>. Click
- <guibutton>Finish</guibutton>.
- </para></step>
-
- <step><para>
- You may be prompted for the name of a file to print to. If so, close the
- dialog panel. Right-click <menuchoice>
- <guiicon>HP LaserJet 4</guiicon>
- <guimenuitem>Properties</guimenuitem>
- <guisubmenu>Details (Tab)</guisubmenu>
- <guimenuitem>Add Port</guimenuitem>
- </menuchoice>.
- </para></step>
-
- <step><para>
- In the <guimenuitem>Network</guimenuitem> panel, enter the name of
- the print queue on the Samba server as follows: <constant>\\SERVER\hplj4</constant>.
- Click <menuchoice>
- <guibutton>OK</guibutton>
- <guibutton>OK</guibutton>
- </menuchoice> to complete the installation.
- </para></step>
-
- <step><para>
- Repeat the printer installation steps above for the HP LaserJet 6 printer
- as well as for the QMS Magicolor XXXX laser printer.
- </para></step>
- </procedure>
- </step>
- </procedure>
-
- <sect2>
- <title>Notebook Computers: A Special Case</title>
-
- <para>
- As a network administrator, you already know how to create local machine accounts for Windows 200x/XP
- Professional systems. This is the preferred solution to provide continuity of work for notebook users
- so that absence from the office network environment does not become a barrier to productivity.
- </para>
-
- <para>
- By creating a local machine account that has the same username and password as you create for that
- user in the Windows Domain environment, the user can log onto the machine locally and still
- transparently access network resources as if logged onto the domain itself. There are some trade-offs
- that mean that as the network is more tightly secured, it becomes necessary to modify Windows client
- configuration somewhat.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Key Points Learned</title>
-
- <para>
- In this network design and implementation exercise, you created a Windows NT4-style Domain
- Controller using Samba-3.0.20. Following these guidelines, you experienced
- and implemented several important aspects of Windows networking. In the next chapter,
- you build on the experience. These are the highlights from this chapter:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>DHCP</primary></indexterm>
- You implemented a DHCP server, and Microsoft Windows clients were able to obtain all necessary
- network configuration settings from this server.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Domain Controller</primary></indexterm>
- You created a Windows Domain Controller. You were able to use the network logon service
- and successfully joined Windows 200x/XP Professional clients to the Domain.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>CUPS</primary></indexterm>
- You created raw print queues in the CUPS printing system. You maintained a simple
- printing system so that all users can share centrally managed printers. You installed
- native printer drivers on the Windows clients.
- </para></listitem>
-
- <listitem><para>
- You experienced the benefits of centrally managed user accounts on the server.
- </para></listitem>
-
- <listitem><para>
- You offered Mobile notebook users a solution that allows them to continue to work
- while away from the office and not connected to the corporate network.
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Questions and Answers</title>
-
- <para>
- Your new Domain Controller is ready to serve you. What does it mean? Here are some questions and answers that
- may help.
- </para>
-
- <qandaset>
- <qandaentry>
- <question>
-
- <para>
- What is the key benefit of using DHCP to configure Windows client TCP/IP stacks?
- </para>
-
- </question>
- <answer>
-
- <para>
- First and foremost, portability. It means that notebook users can move between
- the Abmas office and client offices (so long as they, too, use DHCP) without having to manually
- reconfigure their machines. It also means that when they work from their home environments
- either using DHCP assigned addressing or when using dial-up networking, settings such as
- default routes and DNS server addresses that apply only to the Abmas office environment do
- not interfere with remote operations. This is an extremely important feature of DHCP.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Are there any DHCP server configuration parameters in the <filename>/etc/dhcpd.conf</filename>
- that should be noted in particular?
- </para>
-
- </question>
- <answer>
-
- <para>
- Yes. The configuration you created automatically provides each client with the IP address
- of your WINS server. It also configures the client to preferentially register NetBIOS names
- with the WINS server, and then instructs the client to first query the WINS server when a
- NetBIOS machine name needs to be resolved to an IP Address. This configuration
- results in far lower UDP broadcast traffic than would be the case if WINS was not used.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Is it possible to create a Windows Domain account that is specifically called <constant>Administrator</constant>?
- </para>
-
- </question>
- <answer>
-
- <para>
- You can surely create a Windows Domain account called <constant>Administrator</constant>. It is also
- possible to map that account so that it has the effective UNIX UID of 0. This way it isn't
- necessary to use the <parameter>username map</parameter> facility to map this account to the UNIX
- account called <constant>root</constant>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why is it necessary to give the Windows Domain <constant>Administrator</constant> a UNIX UID of 0?
- </para>
-
- </question>
- <answer>
-
- <para>
- The Windows Domain <constant>Administrator</constant> account is the most privileged account that
- exists on the Windows platform. This user can change any setting, add, delete, or modify user
- accounts, and completely reconfigure the system. The equivalent to this account in the UNIX
- environment is the <constant>root</constant> account. If you want to permit the Windows Domain
- Administrator to manage accounts as well as permissions, privileges, and security
- settings within the Domain and on the Samba server, equivalent rights must be assigned. This is
- achieved with the <constant>root</constant> UID equal to 0.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him
- <constant>root</constant> access. How can we do this?
- </para>
-
- </question>
- <answer>
-
- <para>
- Users who are members of the <constant>Domain Admins</constant> group can add machines to the
- Domain. This group is mapped to the UNIX group account called <constant>root</constant>
- (or the equivalent <constant>wheel</constant> on some UNIX systems) that has a GID of 0.
- This must be the primary GID of the account of the user who is a member of the Windows <constant>
- Domain Admins</constant> account.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- Why must I map Windows Domain Groups to UNIX groups?
- </para>
-
- </question>
- <answer>
-
- <para>
- Samba does not permit a Domain Group to become visible to Domain network clients unless the account
- has a UNIX group account equivalent. The Domain groups that should be given UNIX equivalents are
- <guimenu>Domain Guests</guimenu>, <guimenu>Domain Users</guimenu>, and <guimenu>Domain Admins</guimenu>.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- I deleted my <constant>root</constant> account and now I cannot add it back! What can I do?
- </para>
-
- </question>
- <answer>
-
- <para>
- This is a nasty problem. Fortunately, there is a solution.
- </para>
-
- <procedure>
- <step><para>
- Back up your existing configuration files in case you need to restore them.
- </para></step>
-
- <step><para>
- Rename the <filename>group_mapping.tdb</filename> file.
- </para></step>
-
- <step><para>
- Use the <command>smbpasswd</command> to add the root account.
- </para></step>
-
- <step><para>
- Restore the <filename>group_mapping.tdb</filename> file.
- </para></step>
- </procedure>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- When I run <command>net groupmap list</command>, it reports a group called <guimenu>Administrators</guimenu>
- as well as <guimenu>Domain Admins</guimenu>. What is the difference between them?
- </para>
-
- </question>
- <answer>
-
- <para>
- The group called <guimenu>Administrators</guimenu> is representative of the same account that would be
- present as the Local Group account on a Domain Member server or workstation. Samba uses only Domain
- Groups at this time. A Workstation or Server Local Group has no meaning in a Samba context. This
- may change at some later date. These accounts are provided only so that security objects are correctly shown.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- What is the effect of changing the name of a Samba server or of changing the Domain name?
- </para>
-
- </question>
- <answer>
-
- <para>
- If you elect to change the name of the Samba server, on restarting <command>smbd</command>,
- Windows security identifiers are changed. In the case of a standalone server or a Domain Member server,
- the machine SID is changed. This may break Domain membership. In the case of a change of the Domain name
- (Workgroup name), the Domain SID is changed. This affects all Domain memberships.
- </para>
-
- <para>
- If it becomes necessary to change either the server name or the Domain name, be sure to back up the respective
- SID before the change is made. You can back up the SID using the <command>net getlocalsid</command> (Samba)
- or the <command>smbpasswd</command> (Samba-2.2.x). To change the SID, you use the same tool. Be sure
- to check the man page for this command for detailed instructions regarding the steps involved.
- </para>
-
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
-
- <para>
- How can I manage user accounts from my Windows XP Professional workstation?
- </para>
-
- </question>
- <answer>
-
- <para>
- Samba implements a Windows NT4-style security domain architecture. This type of Domain cannot
- be managed using tools present on a Windows XP Professional installation. You may download from the
- Microsoft Web site the SRVTOOLS.EXE package. Extract it into the directory from which you wish to use
- it. This package extracts the tools: <command>User Manager for Domains</command>, <command>Server Manager</command>, and <command>Event
- Viewer</command>. You may use the <guimenu>User Manager for Domains</guimenu> to manage your Samba
- Domain user and group accounts. Of course, you do need to be logged on as the <constant>Administrator</constant>
- for the Samba Domain. It may help to log on as the <constant>root</constant> account.
- </para>
-
- </answer>
- </qandaentry>
-
- </qandaset>
-
-</sect1>
-
-</chapter>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="upgrades">
-<title>Updating Samba</title>
-
-<para>
-<indexterm><primary>migrate</primary></indexterm>
-<indexterm><primary>install</primary></indexterm>
-It was a little difficult to select an appropriate title for this chapter.
-From email messages on the Samba mailing lists it is clear that many people
-consider the updating and upgrading of Samba to be a migration matter. Others
-talk about migrating Samba servers when in fact the issue at hand is one of
-installing a new Samba server to replace an older existing Samba server.
-</para>
-
-<para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
-There has also been much talk about migration of Samba from an smbpasswd
-passdb backend to the use of the tdbsam or ldapsam facilities that are new
-to Samba.
-</para>
-
-<para>
-Clearly, there is not a great deal of clarity in the terminology that various
-people apply to these modes by which Samba servers are updated. This is further
-highlighted by an email posting that included the following neat remark:
-</para>
-
-<blockquote><para>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
-I like the <quote>net rpc vampire</quote> on NT4, but that to my surprise does
-not seem to work against a Samba PDC and, if addressed in the Samba to Samba
-context in either book, I could not find it.
-</para></blockquote>
-
-<para>
-<indexterm><primary>contributions</primary></indexterm>
-So in response to the significant request for these situations to be better
-documented, this chapter has now been added. User contributions and documentation
-of real-world experiences are a most welcome addition to this chapter.
-</para>
-
-<sect1>
-<title>Introduction</title>
-
-<para>
-<indexterm><primary>update</primary></indexterm>
-<indexterm><primary>upgrade</primary></indexterm>
-<indexterm><primary>frustration</primary></indexterm>
-A Windows network administrator explained in an email what changes he was
-planning to make and followed with the question: <quote>Anyone done this
-before?</quote> Many of us have upgraded and updated Samba without incident.
-Others have experienced much pain and user frustration. So it is to be hoped
-that the notes in this chapter will make a positive difference by assuring
-that someone will be saved a lot of discomfort.
-</para>
-
-<para>
-Before anyone commences an upgrade or an update of Samba, the one cardinal
-rule that must be observed is: Backup all Samba configuration files in
-case it is necessary to revert to the old version. Even if you do not like
-this precautionary step, users will punish an administrator who
-fails to take adequate steps to avoid situations that may inflict lost
-productivity on them.
-</para>
-
-<warning><para>
-<indexterm><primary>configuration files</primary></indexterm>
-<indexterm><primary>down-grade</primary></indexterm>
-Samba makes it possible to upgrade and update configuration files, but it
-is not possible to downgrade the configuration files. Please ensure that
-all configuration and control files are backed up to permit a down-grade
-in the rare event that this may be necessary.
-</para></warning>
-
-
-<para>
-<indexterm><primary>adequate precautions</primary></indexterm>
-<indexterm><primary>precaution</primary></indexterm>
-It is prudent also to backup all data files on the server before attempting
-to perform a major upgrade. Many administrators have experienced the consequences
-of failure to take adequate precautions. So what is adequate? That is simple!
-If data is lost during an upgrade or update and it can not be restored,
-the precautions taken were inadequate. If a backup was not needed, but was available,
-caution was on the side of the victor.
-</para>
-
- <sect2>
- <title>Cautions and Notes</title>
-
- <para>
- Someone once said, <quote>It is good to be sorry, but better never to need to be!</quote>
- These are wise words of advice to those contemplating a Samba upgrade or update.
- </para>
-
- <para>
- <indexterm><primary>update</primary></indexterm>
- <indexterm><primary>upgrade</primary></indexterm>
- <indexterm><primary>generation</primary></indexterm>
- This is as good a time as any to define the terms <constant>upgrade</constant> and
- <constant>update</constant>. The term <constant>upgrade</constant> refers to
- the installation of a version of Samba that is a whole generation or more ahead of
- that which is installed. Generations are indicated by the first digit of the version
- number. So far Samba has been released in generations 1.x, 2.x, 3.x, and currently 4.0
- is in development.
- </para>
-
- <para>
- <indexterm><primary>generation</primary></indexterm>
- The term <constant>update</constant> refers to a minor version number installation
- in place of one of the same generation. For example, updating from Samba 3.0.10 to 3.0.14
- is an update. The move from Samba 2.0.7 to 3.0.14 is an upgrade.
- </para>
-
- <para>
- <indexterm><primary>functional differences</primary></indexterm>
- While the use of these terms is an exercise in semantics, what needs to be realized
- is that there are major functional differences between a Samba 2.x release and a Samba
- 3.0.x release. Such differences may require a significantly different approach to
- solving the same networking challenge and generally require careful review of the
- latest documentation to identify precisely how the new installation may need to be
- modified to preserve prior functionality.
- </para>
-
- <para>
- There is an old axiom that says, <quote>The greater the volume of the documentation,
- the greater the risk that noone will read it, but where there is no documentation,
- noone can read it!</quote> While true, some documentation is an evil necessity.
- It is hoped that this update to the documentation will avoid both extremes.
- </para>
-
- <sect3>
- <title>Security Identifiers (SIDs)</title>
-
- <para>
- <indexterm><primary>Windows</primary><secondary>NT</secondary></indexterm>
- <indexterm><primary>OS/2</primary></indexterm>
- <indexterm><primary>DOS</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>networking</primary><secondary>client</secondary></indexterm>
- <indexterm><primary>security</primary><secondary>identifier</secondary></indexterm>
- Before the days of Windows NT and OS/2, every Windows and DOS networking client
- that used the SMB protocols was an entirely autonomous entity. There was no concept
- of a security identifier for a machine or a user outside of the username, the
- machine name, and the workgroup name. In actual fact, these were not security identifiers
- in the same context as the way that the SID is used since the development of
- Windows NT 3.10.
- </para>
-
- <para>
- <indexterm><primary>SessionSetUpAndX</primary></indexterm>
- <indexterm><primary>SMB</primary></indexterm>
- <indexterm><primary>CIFS</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>username</primary></indexterm>
- <indexterm><primary>Windows</primary><secondary>client</secondary></indexterm>
- Versions of Samba prior to 1.9 did not make use of a SID. Instead they make exclusive use
- of the username that is embedded in the SessionSetUpAndX component of the connection
- setup process between a Windows client and an SMB/CIFS server.
- </para>
-
- <para>
- <indexterm><primary>MACHINE.SID</primary></indexterm>
- <indexterm><primary>rpc</primary></indexterm>
- <indexterm><primary>security</primary></indexterm>
- Around November 1997 support was added to Samba-1.9 to handle the Windows security
- RPC-based protocols that implemented support for Samba to store a machine SID. This
- information was stored in a file called <filename>MACHINE.SID.</filename>
- </para>
-
- <para>
- <indexterm><primary>machine</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>secrets.tdb</primary></indexterm>
- Within the lifetime of the early Samba 2.x series, the machine SID information was
- relocated into a tdb file called <filename>secrets.tdb</filename>, which is where
- it is still located in Samba 3.0.x along with other information that pertains to the
- local machine and its role within a domain security context.
- </para>
-
- <para>
- <indexterm><primary>server</primary><secondary>stand-alone</secondary></indexterm>
- <indexterm><primary>server</primary><secondary>domain member</secondary></indexterm>
- <indexterm><primary>DMS</primary></indexterm>
- <indexterm><primary>SAS</primary></indexterm>
- There are two types of SID, those pertaining to the machine itself and the domain to
- which it may belong, and those pertaining to users and groups within the security
- context of the local machine, in the case of standalone servers (SAS) and domain member
- servers (DMS).
- </para>
-
- <para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>workgroup</primary></indexterm>
- <indexterm><primary>hostname</primary></indexterm>
- <indexterm><primary>daemon</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>secrets.tdb</primary></indexterm>
- When the Samba <command>smbd</command> daemon is first started, if the <filename>secrets.tdb</filename>
- file does not exist, it is created at the first client connection attempt. If this file does
- exist, <command>smbd</command> checks that there is a machine SID (if it is a domain controller,
- it searches for the domain SID). If <command>smbd</command> does not find one for the current
- name of the machine or for the current name of the workgroup, a new SID will be generated and
- then written to the <filename>secrets.tdb</filename> file. The SID is generated in a nondeterminative
- manner. This means that each time it is generated for a particular combination of machine name
- (hostname) and domain name (workgroup), it will be different.
- </para>
-
- <para>
- <indexterm><primary>ACL</primary></indexterm>
- The SID is the key used by MS Windows networking for all networking operations. This means
- that when the machine or domain SID changes, all security-encoded objects such as profiles
- and ACLs may become unusable.
- </para>
-
- <note><para>
- It is of paramount importance that the machine and domain SID be backed up so that in
- the event of a change of hostname (machine name) or domain name (workgroup) the SID can
- be restored to its previous value.
- </para></note>
-
- <para>
- <indexterm><primary>domain controller</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>domain SID</primary></indexterm>
- <indexterm><primary>hostname</primary></indexterm>
- <indexterm><primary>computer name</primary></indexterm>
- <indexterm><primary>netbios name</primary></indexterm>
- <indexterm><primary>stand-alone server</primary></indexterm>
- <indexterm><primary>SAS</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- In Samba on a domain controller (PDC or BDC), the domain name controls the domain
- SID. On all prior versions the hostname (computer name, or NetBIOS name) controlled
- the SID. On a standalone server the hostname still controls the SID.
- </para>
-
- <para>
- <indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
- <indexterm><primary>net</primary><secondary>setlocalsid</secondary></indexterm>
- The local machine SID can be backed up using this procedure (Samba):
-<screen>
-&rootprompt; net getlocalsid > /etc/samba/my-local-SID
-</screen>
- The contents of the file <filename>/etc/samba/my-local-SID</filename> will be:
-<screen>
-SID for domain FRODO is: S-1-5-21-726309263-4128913605-1168186429
-</screen>
- This SID can be restored by executing:
-<screen>
-&rootprompt; net setlocalsid S-1-5-21-726309263-4128913605-1168186429
-</screen>
- </para>
-
- <para>
- Samba 1.9.x stored the machine SID in the the file <filename>/etc/MACHINE.SID</filename>
- from which it could be recovered and stored into the <filename>secrets.tdb</filename> file
- using the procedure shown above.
- </para>
-
- <para>
- Where the <filename>secrets.tdb</filename> file exists and a version of Samba 2.x or later
- has been used, there is no specific need to go through this update process. Samba has the
- ability to read the older tdb file and to perform an in-situ update to the latest tdb format.
- This is not a reversible process &smbmdash; it is a one-way upgrade.
- </para>
-
- <para>
- <indexterm><primary>smbpasswd</primary></indexterm>
- In the course of the Samba 2.0.x series the <command>smbpasswd</command> was modified to
- permit the domain SID to be captured to the <filename>secrets.tdb</filename> file by executing:
-<screen>
-&rootprompt; smbpasswd -S PDC -Uadministrator%password
-</screen>
- </para>
-
- <para>
- The release of the Samba 2.2.x series permitted the SID to be obtained by executing:
-<screen>
-&rootprompt; smbpasswd -S PDC -Uadministrator%password
-</screen>
- from which the SID could be copied to a file and then written to the Samba-2.2.x
- <filename>secrets.tdb</filename> file by executing:
-<screen>
-&rootprompt; smbpasswd -W S-1-5-21-726309263-4128913605-1168186429
-</screen>
- </para>
-
- <para>
- <indexterm><primary>rpcclient</primary></indexterm>
- <indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>info</tertiary></indexterm>
- Domain security information, which includes the domain SID, can be obtained from Samba-2.2.x
- systems by executing:
-<screen>
-&rootprompt; rpcclient hostname lsaquery -Uroot%password
-</screen>
- This can also be done with Samba by executing:
-<screen>
-&rootprompt; net rpc info -Uroot%password
-Domain Name: MIDEARTH
-Domain SID: S-1-5-21-726309263-4128913605-1168186429
-Sequence number: 1113415916
-Num users: 4237
-Num domain groups: 86
-Num local groups: 0
-</screen>
- It is a very good practice to store this SID information in a safely kept file, just in
- case it is ever needed at a later date.
- </para>
-
- <para>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- Take note that the domain SID is used extensively in Samba. Where LDAP is used for the
- <parameter>passdb backend</parameter>, all user, group, and trust accounts are encoded
- with the domain SID. This means that if the domain SID changes for any reason, the entire
- Samba environment can become broken and require extensive corrective action if the
- original SID cannot be restored. Fortunately, it can be recovered from a dump of the
- LDAP database. A dump of the LDAP directory database can be obtained by executing:
-<screen>
-&rootprompt; slapcat -v -l filename.ldif
-</screen>
- </para>
-
- <para>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>profiles</primary></indexterm>
- <indexterm><primary>RPM</primary></indexterm>
- When the domain SID has changed, roaming profiles cease to be functional. The recovery
- of roaming profiles necessitates resetting of the domain portion of the user SID
- that owns the profile. This is encoded in the <filename>NTUser.DAT</filename> and can be
- updated using the Samba <command>profiles</command> utility. Please be aware that not all
- Linux distributions of the Samba RPMs include this essential utility. Please do not
- complain to the Samba Team if this utility is missing; that issue that must be
- addressed to the creator of the RPM package. The Samba Team do their best to make
- available all the tools needed to manage a Samba-based Windows networking environment.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Change of hostname</title>
-
- <para>
- <indexterm><primary>netbios</primary><secondary>machine name</secondary></indexterm>
- <indexterm><primary>netbios name</primary></indexterm>
- Samba uses two methods by which the primary NetBIOS machine name (also known as a computer
- name or the hostname) may be determined: If the &smb.conf; file contains a
- <parameter>netbios name</parameter> entry, its value will be used directly. In the absence
- of such an entry, the UNIX system hostname will be used.
- </para>
-
- <para>
- Many sites have become victims of lost Samba functionality because the UNIX system
- hostname was changed for one reason or another. Such a change will cause a new machine
- SID to be generated. If this happens on a domain controller, it will also change the
- domain SID. These SIDs can be updated (restored) using the procedure outlined previously.
- </para>
-
- <note><para>
- Do NOT change the hostname or the <parameter>netbios name</parameter>. If this
- is changed, be sure to reset the machine SID to the original setting. Otherwise
- there may be serious interoperability and/or operational problems.
- </para></note>
-
- </sect3>
-
- <sect3>
- <title>Change of Workgroup (Domain) Name</title>
-
- <para>
- <indexterm><primary>workgroup</primary></indexterm>
- The domain name of a Samba server is identical to the workgroup name and is
- set in the &smb.conf; file using the <parameter>workgroup</parameter> parameter.
- This has been consistent throughout the history of Samba and across all versions.
- </para>
-
- <para>
- <indexterm><primary>SID</primary></indexterm>
- Be aware that when the workgroup name is changed, a new SID will be generated.
- The old domain SID can be reset using the procedure outlined earlier in this chapter.
- </para>
-
- </sect3>
-
- <sect3 id="sbeug1">
- <title>Location of config files</title>
-
- <para>
- The Samba-Team has maintained a constant default location for all Samba control files
- throughout the life of the project. People who have produced binary packages of Samba
- have varied the location of the Samba control files. This has led to some confusion
- for network administrators.
- </para>
-
- <para>
- <indexterm><primary>directory</primary></indexterm>
- The Samba 1.9.x &smb.conf; file may be found either in the <filename>/etc</filename>
- directory or in <filename>/usr/local/samba/lib</filename>.
- </para>
-
- <para>
- During the life of the Samba 2.x release, the &smb.conf; file was relocated
- on Linux systems to the <filename>/etc/samba</filename> directory where it
- remains located also for Samba 3.0.x installations.
- </para>
-
- <para>
- <indexterm><primary>secrets.tdb</primary></indexterm>
- Samba 2.x introduced the <filename>secrets.tdb</filename> file that is also stored in the
- <filename>/etc/samba</filename> directory, or in the <filename>/usr/local/samba/lib</filename>
- directory subsystem.
- </para>
-
- <para>
- <indexterm><primary>smbd</primary></indexterm>
- The location at which <command>smbd</command> expects to find all configuration and control
- files is determined at the time of compilation of Samba. For versions of Samba prior to
- 3.0, one way to find the expected location of these files is to execute:
-<screen>
-&rootprompt; strings /usr/sbin/smbd | grep conf
-&rootprompt; strings /usr/sbin/smbd | grep secret
-&rootprompt; strings /usr/sbin/smbd | grep smbpasswd
-</screen>
- Note: The <command>smbd</command> executable may be located in the path
- <filename>/usr/local/samba/sbin</filename>.
- </para>
-
- <para>
- <indexterm><primary>compile-time</primary></indexterm>
- Samba provides a neat new way to track the location of all control files as well as to
- find the compile-time options used as the Samba package was built. Here is how the dark
- secrets of the internals of the location of control files within Samba executables can
- be uncovered:
-<screen>
-&rootprompt; smbd -b | less
-Build environment:
- Built by: root@frodo
- Built on: Mon Apr 11 20:23:27 MDT 2005
- Built using: gcc
- Build host: Linux frodo 2.6...
- SRCDIR: /usr/src/packages/BUILD/samba-3.0.20/source
- BUILDDIR: /usr/src/packages/BUILD/samba-3.0.20/source
-
-Paths:
- SBINDIR: /usr/sbin
- BINDIR: /usr/bin
- SWATDIR: /usr/share/samba/swat
- CONFIGFILE: /etc/samba/smb.conf
- LOGFILEBASE: /var/log/samba
- LMHOSTSFILE: /etc/samba/lmhosts
- LIBDIR: /usr/lib/samba
- SHLIBEXT: so
- LOCKDIR: /var/lib/samba
- PIDDIR: /var/run/samba
- SMB_PASSWD_FILE: /etc/samba/smbpasswd
- PRIVATE_DIR: /etc/samba
- ...
-</screen>
- </para>
-
- <para>
- <indexterm><primary></primary></indexterm>
- It is important that both the &smb.conf; file and the <filename>secrets.tdb</filename>
- be backed up before attempting any upgrade. The <filename>secrets.tdb</filename> file
- is version-encoded, and therefore a newer version may not work with an older version
- of Samba. A backup means that it is always possible to revert a failed or problematic
- upgrade.
- </para>
-
- </sect3>
-
- <sect3>
- <title>International Language Support</title>
-
- <para>
- <indexterm><primary>unicode</primary></indexterm>
- <indexterm><primary>character set</primary></indexterm>
- <indexterm><primary>codepage</primary></indexterm>
- <indexterm><primary>internationalization</primary></indexterm>
- Samba-2.x had no support for Unicode; instead, all national language character-set support in file names
- was done using particular locale codepage mapping techniques. Samba supports Unicode in file names, thus
- providing true internationalization support.
- </para>
-
- <para>
- <indexterm><primary>8-bit</primary></indexterm>
- Non-English users whose national language character set has special characters and who upgrade naively will
- find that many files that have the special characters in the file name will see them garbled and jumbled up.
- This typically happens with umlauts and accents because these characters were particular to the codepage
- that was in use with Samba-2.x using an 8-bit encoding scheme.
- </para>
-
- <para>
- <indexterm><primary>UTF-8</primary></indexterm>
- Files that are created with Samba will use UTF-8 encoding. Should the file system ever end up with a
- mix of codepage (unix charset)-encoded file names and UTF-8-encoded file names, the mess will take some
- effort to set straight.
- </para>
-
- <para>
- <indexterm><primary>convmv</primary></indexterm>
- A very helpful tool is available from Bjorn Jacke's <ulink url="http://j3e.de/linux/convmv/">convmv</ulink>
- work. Convmv is a tool that can be used to convert file and directory names from one encoding method to
- another. The most common use for this tool is to convert locale-encoded files to UTF-8 Unicode encoding.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Updates and Changes in Idealx smbldap-tools</title>
-
- <para>
- The smbldap-tools have been maturing rapidly over the past year. With maturation comes change.
- The location of the <filename>smbldap.conf</filename> and the <filename>smbldap_bind.conf</filename>
- configuration files have been moved from the directory <filename>/etc/smbldap-tools</filename> to
- the new location of <filename>/etc/opt/IDEALX/smblda-tools</filename> directory.
- </para>
-
- <para>
- The smbldap-tools maintains an entry in the LDAP directory in which it stores the next
- values that should be used for UID and GID allocation for POSIX accounts that are created
- using this tool. The DIT location of these values has changed recently. The original
- <constant>sambaUnixIdPooldn object</constant> entity was stored in a directory entry (DIT object)
- called <constant>NextFreeUnixId</constant>, this has been changed to the DIT object
- <constant>sambaDomainName</constant>. Anyone who updates from an older version to the
- current release should note that the information stored under <constant>NextFreeUnixId</constant>
- must now be relocated to the DIT object <constant>sambaDomainName</constant>.
- </para>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Upgrading from Samba 1.x and 2.x to Samba-3</title>
-
-<para>
-Sites that are being upgraded from Samba-2 (or earlier versions) to Samba-3
-may experience little difficulty or may require a lot of effort, depending
-on the complexity of the configuration. Samba-1.9.x upgrades to Samba-3 will
-generally be simple and straightforward, although no upgrade should be
-attempted without proper planning and preparation.
-</para>
-
-<para>
-There are two basic modes of use of Samba versions prior to Samba-3. The first
-does not use LDAP, the other does. Samba-1.9.x did not provide LDAP support.
-Samba-2.x could be compiled with LDAP support.
-</para>
-
- <sect2 id="sbeug2">
- <title>Samba 1.9.x and 2.x Versions Without LDAP</title>
-
- <para>
- Where it is necessary to upgrade an old Samba installation to Samba-3,
- the following procedure can be followed:
- </para>
-
- <procedure>
- <title>Upgrading from a Pre-Samba-3 Version</title>
-
- <step><para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- Stop Samba. This can be done using the appropriate system tool
- that is particular for each operating system or by executing the
- <command>kill</command> command on <command>smbd</command>,
- <command>nmbd</command>, and <command>winbindd</command>.
- </para></step>
-
- <step><para>
- Find the location of the Samba &smb.conf; file and back it up to a
- safe location.
- </para></step>
-
- <step><para>
- Find the location of the <filename>smbpasswd</filename> file and
- back it up to a safe location.
- </para></step>
-
- <step><para>
- Find the location of the <filename>secrets.tdb</filename> file and
- back it up to a safe location.
- </para></step>
-
- <step><para>
- <indexterm><primary>lock directory</primary></indexterm>
- <indexterm><primary>/usr/local/samba/var/locks</primary></indexterm>
- <indexterm><primary>/var/cache/samba</primary></indexterm>
- <indexterm><primary>/var/lib/samba</primary></indexterm>
- Find the location of the lock directory. This is the directory
- in which Samba stores all its tdb control files. The default
- location used by the Samba Team is in
- <filename>/usr/local/samba/var/locks</filename> directory,
- but on Linux systems the old location was under the
- <filename>/var/cache/samba</filename> directory. However, the
- Linux Standards Base specified location is now under the
- <filename>/var/lib/samba</filename> directory. Copy all the
- tdb files to a safe location.
- </para></step>
-
- <step><para>
- <indexterm><primary>RPM</primary></indexterm>
- It is now safe to upgrade the Samba installation. On Linux systems
- it is not necessary to remove the Samba RPMs because a simple
- upgrade installation will automatically remove the old files.
- </para>
-
- <para>
- On systems that do not support a reliable package management system
- it is advisable either to delete the Samba old installation or to
- move it out of the way by renaming the directories that contain the
- Samba binary files.
- </para></step>
-
- <step><para>
- When the Samba upgrade has been installed, the first step that should
- be completed is to identify the new target locations for the control
- files. Follow the steps shown in <link linkend="sbeug1"/> to locate
- the correct directories to which each control file must be moved.
- </para></step>
-
- <step><para>
- Do not change the hostname.
- </para></step>
-
- <step><para>
- Do not change the workgroup name.
- </para></step>
-
- <step><para>
- <indexterm><primary>testparm</primary></indexterm>
- Execute the <command>testparm</command> to validate the &smb.conf; file.
- This process will flag any parameters that are no longer supported.
- It will also flag configuration settings that may be in conflict.
- </para>
-
- <para>
- One solution that may be used to clean up and to update the &smb.conf;
- file involves renaming it to <filename>smb.conf.master</filename> and
- then executing the following:
-<screen>
-&rootprompt; cd /etc/samba
-&rootprompt; testparm -s smb.conf.master > smb.conf
-</screen>
- <indexterm><primary>stripped</primary></indexterm>
- The resulting &smb.conf; file will be stripped of all comments
- and of all nonconforming configuration settings.
- </para></step>
-
- <step><para>
- <indexterm><primary>winbindd</primary></indexterm>
- It is now safe to start Samba using the appropriate system tool.
- Alternately, it is possible to just execute <command>nmbd</command>,
- <command>smbd</command>, and <command>winbindd</command> for the command
- line while logged in as the root user.
- </para></step>
-
- </procedure>
-
- </sect2>
-
- <sect2>
- <title>Applicable to All Samba 2.x to Samba-3 Upgrades</title>
-
- <para>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>domain controller</primary></indexterm>
- <indexterm><primary>inter-domain</primary></indexterm>
- Samba 2.x servers that were running as a domain controller (PDC)
- require changes to the configuration of the scripting interface
- tools that Samba uses to perform OS updates for
- users, groups, and trust accounts (machines and interdomain).
- </para>
-
- <para>
- <indexterm><primary>parameters</primary></indexterm>
- The following parameters are new to Samba and should be correctly configured.
- Please refer to <link linkend="secure"/> through <link linkend="net2000users"/>
- in this book for examples of use of the new parameters shown here:
- <indexterm><primary>add group script</primary></indexterm>
- <indexterm><primary>add machine script</primary></indexterm>
- <indexterm><primary>add user to group script</primary></indexterm>
- <indexterm><primary>delete group script</primary></indexterm>
- <indexterm><primary>delete user from group script</primary></indexterm>
- <indexterm><primary>set primary group script</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- </para>
-
- <para>
- <simplelist>
- <member>add group script</member>
- <member>add machine script</member>
- <member>add user to group script</member>
- <member>delete group script</member>
- <member>delete user from group script</member>
- <member>passdb backend</member>
- <member>set primary group script</member>
- </simplelist>
- </para>
-
- <para>
- <indexterm><primary>add machine script</primary></indexterm>
- <indexterm><primary>add user script</primary></indexterm>
- The <parameter>add machine script</parameter> functionality was previously
- handled by the <parameter>add user script</parameter>, which in Samba is
- used exclusively to add user accounts.
- </para>
-
- <para>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>useradd</primary></indexterm>
- <indexterm><primary>usermod</primary></indexterm>
- <indexterm><primary>userdel</primary></indexterm>
- <indexterm><primary>groupadd</primary></indexterm>
- <indexterm><primary>groupmod</primary></indexterm>
- <indexterm><primary>groupdel</primary></indexterm>
- Where the <parameter>passdb backend</parameter> used is either <constant>smbpasswd</constant>
- (the default) or the new <constant>tdbsam</constant>, the system interface scripts
- are typically used. These involve use of OS tools such as <command>useradd</command>,
- <command>usermod</command>, <command>userdel</command>, <command>groupadd</command>,
- <command>groupmod</command>, <command>groupdel</command>, and so on.
- </para>
-
- <para>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>Idealx</primary></indexterm>
- Where the <parameter>passdb backend</parameter> makes use of an LDAP directory,
- it is necessary either to use the <constant>smbldap-tools</constant> provided
- by Idealx or to use an alternate toolset provided by a third
- party or else home-crafted to manage the LDAP directory accounts.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Samba-2.x with LDAP Support</title>
-
- <para>
- Samba version 2.x could be compiled for use either with or without LDAP.
- The LDAP control settings in the &smb.conf; file in this old version are
- completely different (and less complete) than they are with Samba. This
- means that after migrating the control files, it is necessary to reconfigure
- the LDAP settings entirely.
- </para>
-
- <para>
- Follow the procedure outlined in <link linkend="sbeug2"/> to affect a migration
- of all files to the correct locations.
- </para>
-
- <para>
- <indexterm><primary>schema</primary></indexterm>
- <indexterm><primary>WHATSNEW.txt</primary></indexterm>
- The Samba SAM schema required for Samba-3 is significantly different from that
- used with Samba 2.x. This means that the LDAP directory must be updated
- using the procedure outlined in the Samba WHATSNEW.txt file that accompanies
- all releases of Samba-3. This information is repeated here directly from this
- file:
-<screen>
-This is an extract from the Samba-3.0.x WHATSNEW.txt file:
-==========================================================
-Changes in Behavior
--------------------
-
-The following issues are known changes in behavior between Samba 2.2 and
-Samba 3.0 that may affect certain installations of Samba.
-
- 1) When operating as a member of a Windows domain, Samba 2.2 would
- map any users authenticated by the remote DC to the 'guest account'
- if a uid could not be obtained via the getpwnam() call. Samba 3.0
- rejects the connection as NT_STATUS_LOGON_FAILURE. There is no
- current work around to re-establish the 2.2 behavior.
-
- 2) When adding machines to a Samba 2.2 controlled domain, the
- 'add user script' was used to create the UNIX identity of the
- machine trust account. Samba 3.0 introduces a new 'add machine
- script' that must be specified for this purpose. Samba 3.0 will
- not fall back to using the 'add user script' in the absence of
- an 'add machine script'
-
-######################################################################
-Passdb Backends and Authentication
-##################################
-
-There have been a few new changes that Samba administrators should be
-aware of when moving to Samba 3.0.
-
- 1) encrypted passwords have been enabled by default in order to
- inter-operate better with out-of-the-box Windows client
- installations. This does mean that either (a) a samba account
- must be created for each user, or (b) 'encrypt passwords = no'
- must be explicitly defined in smb.conf.
-
- 2) Inclusion of new 'security = ads' option for integration
- with an Active Directory domain using the native Windows
- Kerberos 5 and LDAP protocols.
-
- MIT kerberos 1.3.1 supports the ARCFOUR-HMAC-MD5 encryption
- type which is necessary for servers on which the
- administrator password has not been changed, or kerberos-enabled
- SMB connections to servers that require Kerberos SMB signing.
- Besides this one difference, either MIT or Heimdal Kerberos
- distributions are usable by Samba 3.0.
-
-
-Samba 3.0 also includes the possibility of setting up chains
-of authentication methods (auth methods) and account storage
-backends (passdb backend). Please refer to the smb.conf(5)
-man page for details. While both parameters assume sane default
-values, it is likely that you will need to understand what the
-values actually mean in order to ensure Samba operates correctly.
-
-The recommended passdb backends at this time are
-
- * smbpasswd - 2.2 compatible flat file format
- * tdbsam - attribute rich database intended as an smbpasswd
- replacement for stand alone servers
- * ldapsam - attribute rich account storage and retrieval
- backend utilizing an LDAP directory.
-
-Certain functions of the smbpasswd(8) tool have been split between the
-new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8)
-utility. See the respective man pages for details.
-
-New Suffix for Searching
-------------------------
-
-The following new smb.conf parameters have been added to aid in directing
-certain LDAP queries when 'passdb backend = ldapsam://...' has been
-specified.
-
- * ldap suffix - used to search for user and computer accounts
- * ldap user suffix - used to store user accounts
- * ldap machine suffix - used to store machine trust accounts
- * ldap group suffix - location of posixGroup/sambaGroupMapping entries
- * ldap idmap suffix - location of sambaIdmapEntry objects
-
-If an 'ldap suffix' is defined, it will be appended to all of the
-remaining sub-suffix parameters. In this case, the order of the suffix
-listings in smb.conf is important. Always place the 'ldap suffix' first
-in the list.
-
-Due to a limitation in Samba's smb.conf parsing, you should not surround
-the DN's with quotation marks.
-</screen>
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Updating a Samba-3 Installation</title>
-
-<para>
-The key concern in this section is to deal with the changes that have been
-affected in Samba-3 between the Samba-3.0.0 release and the current update.
-Network administrators have expressed concerns over the steps that should be
-taken to update Samba-3 versions.
-</para>
-
-<para>
-<indexterm><primary>control files</primary></indexterm>
-The information in <link linkend="sbeug1"/> would not be necessary if every
-person who has ever produced Samba executable (binary) files could agree on
-the preferred location of the &smb.conf; file and other Samba control files.
-Clearly, such agreement is further away than a pipedream.
-</para>
-
-<para>
-<indexterm><primary>vendors</primary></indexterm>
-Vendors and packagers who produce Samba binary installable packages do not,
-as a rule, use the default paths used by the Samba-Team for the location of
-the binary files, the &smb.conf; file, and the Samba control files (tdb's
-as well as files such as <filename>secrets.tdb</filename>). This means that
-the network or UNIX administrator who sets out to build the Samba executable
-files from the Samba tarball must take particular care. Failure to take care
-will result in both the original vendor's version of Samba remaining installed
-and the new version being installed in the default location used
-by the Samba-Team. This can lead to confusion and to much lost time as the
-uninformed administrator deals with apparent failure of the update to take
-effect.
-</para>
-
-<para>
-<indexterm><primary>packages</primary></indexterm>
-The best advice for those lacking in code compilation experience is to use
-only vendor (or Samba-Team) provided binary packages. The Samba packages
-that are provided by the Samba-Team are generally built to use file paths
-that are compatible with the original OS vendor's practices.
-</para>
-
-<para>
-<indexterm><primary>binary package</primary></indexterm>
-<indexterm><primary>binary files</primary></indexterm>
-If you are not sure whether a binary package complies with the OS
-vendor's practices, it is better to ask the package maintainer via
-email than to waste much time dealing with the nuances.
-Alternately, just diagnose the paths specified by the binary files following
-the procedure outlined above.
-</para>
-
- <sect2>
- <title>Samba to Samba-3 Updates on the Same Server</title>
-
- <para>
- The guidance in this section deals with updates to an existing
- Samba server installation.
- </para>
-
- <sect3>
- <title>Updating from Samba Versions Earlier than 3.0.5</title>
-
- <para>
- With the provision that the binary Samba package has been built
- with the same path and feature settings as the existing Samba
- package that is being updated, an update of Samba versions 3.0.0
- through 3.0.4 can be updated to 3.0.5 without loss of functionality
- and without need to change either the &smb.conf; file or, where
- used, the LDAP schema.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Updating from Samba Versions between 3.0.6 and 3.0.10</title>
-
- <para>
- <indexterm><primary>schema</primary></indexterm>
- <indexterm><primary>LDAP</primary><secondary>schema</secondary></indexterm>
- When updating versions of Samba prior to 3.0.6 to 3.0.6 through 3.0.10,
- it is necessary only to update the LDAP schema (where LDAP is used).
- Always use the LDAP schema file that is shipped with the latest Samba
- update.
- </para>
-
- <para>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- Samba-3.0.6 introduced the ability to remember the last <emphasis>n</emphasis> number
- of passwords a user has used. This information will work only with
- the <constant>tdbsam</constant> and <constant>ldapsam</constant>
- <parameter>passdb backend</parameter> facilities.
- </para>
-
- <para>
- After updating the LDAP schema, do not forget to re-index the LDAP database.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Updating from Samba Versions after 3.0.6 to a Current Release</title>
-
- <para>
- <indexterm><primary>winbindd</primary></indexterm>
- Samba-3.0.8 introduced changes in how the <parameter>username map</parameter>
- behaves. It also included a change in behavior of <command>winbindd</command>.
- Please refer to the man page for &smb.conf; before implementing any update
- from versions prior to 3.0.8 to a current version.
- </para>
-
- <para>
- <indexterm><primary>privileges</primary></indexterm>
- In Samba-3.0.11 a new privileges interface was implemented. Please
- refer to <link linkend="sbehap-ppc"/> for information regarding this new
- feature. It is not necessary to implement the privileges interface, but it
- is one that has been requested for several years and thus may be of interest
- at your site.
- </para>
-
- <para>
- In Samba-3.0.11 there were some functional changes to the <parameter>ldap user
- suffix</parameter> and to the <parameter>ldap machine suffix</parameter> behaviors.
- The following information has been extracted from the WHATSNEW.txt file from this
- release:
-<screen>
-============
-LDAP Changes
-============
-
-If "ldap user suffix" or "ldap machine suffix" are defined in
-smb.conf, all user-accounts must reside below the user suffix,
-and all machine and inter-domain trust-accounts must be located
-below the machine suffix. Previous Samba releases would fall
-back to searching the 'ldap suffix' in some cases.
-</screen>
- </para>
-
- </sect3>
- </sect2>
-
- <sect2>
- <title>Migrating Samba to a New Server</title>
-
- <para>
- The two most likely candidates for replacement of a server are
- domain member servers and domain controllers. Each needs to be
- handled slightly differently.
- </para>
-
- <sect3>
- <title>Replacing a Domain Member Server</title>
-
- <para>
- <indexterm><primary>DMS</primary></indexterm>
- Replacement of a domain member server should be done
- using the same procedure as outlined in <link linkend="unixclients"/>.
- </para>
-
- <para>
- Usually the new server will be introduced with a temporary name. After
- the old server data has been migrated to the new server, it is customary
- that the new server be renamed to that of the old server. This will
- change its SID and will necessitate rejoining to the domain.
- </para>
-
- <para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>wins.dat</primary></indexterm>
- <indexterm><primary>browse.dat</primary></indexterm>
- <indexterm><primary>resolution</primary></indexterm>
- Following a change of hostname (NetBIOS name) it is a good idea on all servers
- to shut down the Samba <command>smbd</command>, <command>nmbd</command>, and
- <command>winbindd</command> services, delete the <filename>wins.dat</filename>
- and <filename>browse.dat</filename> files, then restart Samba. This will ensure
- that the old name and IP address information is no longer able to interfere with
- name to IP address resolution. If this is not done, there can be temporary name
- resolution problems. These problems usually clear within 45 minutes of a name
- change, but can persist for a longer period of time.
- </para>
-
- <para>
- <indexterm><primary>DMS</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>/etc/shadow</primary></indexterm>
- <indexterm><primary>/etc/group</primary></indexterm>
- If the old domain member server had local accounts, it is necessary to create
- on the new domain member server the same accounts with the same UID and GID
- for each account. Where the <parameter>passdb backend</parameter> database
- is stored in the <constant>smbpasswd</constant> or in the
- <constant>tdbsam</constant> format, the user and group account information
- for UNIX accounts that match the Samba accounts will reside in the system
- <filename>/etc/passwd</filename>, <filename>/etc/shadow</filename>, and
- <filename>/etc/group</filename> files. In this case, be sure to copy these
- account entries to the new target server.
- </para>
-
- <para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- Where the user accounts for both UNIX and Samba are stored in LDAP, the new
- target server must be configured to use the <command>nss_ldap</command> tool set.
- This will automatically ensure that the appropriate user entities are
- available on the new server.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Replacing a Domain Controller</title>
-
- <para>
- <indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
- In the past, people who replaced a Windows NT4 domain controller typically
- installed a new server, created printers and file shares on it, then migrate across
- all data that was destined to reside on it. The same can of course be done with
- Samba.
- </para>
-
- <para>
- From recent mailing list postings it would seem that some administrators
- have the intent to just replace the old Samba server with a new one with
- the same name as the old one. In this case, simply follow the same process
- as for upgrading a Samba 2.x system and do the following:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Where UNIX (POSIX) user and group accounts are stored in the system
- <filename>/etc/passwd</filename>, <filename>/etc/shadow</filename>, and
- <filename>/etc/group</filename> files, be sure to add the same accounts
- with identical UID and GID values for each user.
- </para>
-
- <para>
- Where LDAP is used, if the new system is intended to be the LDAP server,
- migrate it across by configuring the LDAP server
- (<filename>/etc/openldap/slapd.conf</filename>). The directory can
- be populated either initially by setting this LDAP server up as a slave or
- by dumping the data from the old LDAP server using the <command>slapcat</command>
- command and then reloading the same data into the new LDAP server using the
- <command>slapadd</command> command. Do not forget to install and configure
- the <command>nss_ldap</command> tool and the <filename>/etc/nsswitch.conf</filename>
- (as shown in <link linkend="happy"/>).
- </para></listitem>
-
- <listitem><para>
- Copy the &smb.conf; file from the old server to the new server into the correct
- location as indicated previously in this chapter.
- </para></listitem>
-
- <listitem><para>
- Copy the <filename>secrets.tdb</filename> file, the <filename>smbpasswd</filename>
- file (if it is used), the <filename>/etc/samba/passdb.tdb</filename> file (only
- used by the <constant>tdbsam</constant> backend), and all the tdb control files
- from the old system to the correct location on the new system.
- </para></listitem>
-
- <listitem><para>
- Before starting the Samba daemons, verify that the hostname of the new server
- is identical to that of the old one. Note: The IP address can be different
- from that of the old server.
- </para></listitem>
-
- <listitem><para>
- Copy all files from the old server to the new server, taking precaution to
- preserve all file ownership and permissions as well as any POSIX ACLs that
- may have been created on the old server.
- </para></listitem>
- </itemizedlist>
-
- <para>
- When replacing a Samba domain controller (PDC or BDC) that uses LDAP, the new server
- need simply be configured to use the LDAP directory, and for the rest it should just
- work. The domain SID is obtained from the LDAP directory as part of the first connect
- to the LDAP directory server.
- </para>
-
- <para>
- All Samba servers, other than one that uses LDAP, depend on the tdb files, and
- particularly on the <filename>secrets.tdb</filename> file. So long as the tdb files are
- all in place, the &smb.conf; file is preserved, and either the hostname is identical
- or the <parameter>netbios name</parameter> is set to the original server name, Samba
- should correctly pick up the original SID and preserve all other settings. It is
- sound advice to validate this before turning the system over to users.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Migration of Samba Accounts to Active Directory</title>
-
- <para>
- Yes, it works. The Windows ADMT tool can be used to migrate Samba accounts
- to MS Active Directory. There are a few pitfalls to be aware of:
- </para>
-
- <procedure>
- <title>Migration to Active Directory</title>
-
- <step><para>
- Administrator password must be THE SAME on the Samba server,
- the 2003 ADS, and the local Administrator account on the workstations.
- Perhaps this goes without saying, but there needs to be an account
- called <constant>Administrator</constant> in your Samba domain, with
- full administrative (root) rights to that domain.
- </para></step>
-
- <step><para>
- In the Advanced/DNS section of the TCP/IP settings on your Windows
- workstations, make sure the <parameter>DNS suffix for this
- connection</parameter> field is blank.
- </para></step>
-
- <step><para>
- Because you are migrating from Samba, user passwords cannot be
- migrated. You'll have to reset everyone's passwords. (If you were
- migrating from NT4 to ADS, you could migrate passwords as well.)
- </para>
-
- <para>
- To date this has not been attempted with roaming profile support;
- it has been documented as working with local profiles.
- </para></step>
-
- <step><para>
- Disable the Windows Firewall on all workstations. Otherwise,
- workstations won't be migrated to the new domain.
- </para></step>
-
- <step><para>
- <indexterm><primary>ADMT</primary></indexterm>
- When migrating machines, always test first (using ADMT's test mode)
- and satisfy all errors before committing the migration. Note that the
- test will always fail, because the machine will not have been actually
- migrated. You'll need to interpret the errors to know whether the
- failure was due to a problem or simply to the fact that it was just
- a test.
- </para></step>
-
- </procedure>
-
-
- <para>
- <indexterm><primary>ADMT</primary></indexterm>
- There are some significant benefits of using the ADMT, besides just
- migrating user accounts. ADMT can be found on the Windows 2003 CD.
- </para>
-
- <itemizedlist>
- <listitem><para>
- You can migrate workstations remotely. You can specify that SIDs
- be simply added instead of replaced, giving you the option of joining a
- workstation back to the old domain if something goes awry. The
- workstations will be joined to the new domain.
- </para></listitem>
-
- <listitem><para>
- Not only are user accounts migrated from the old domain to the new
- domain, but ACLs on the workstations are migrated as well. Like SIDs,
- ACLs can be added instead of replaced.
- </para></listitem>
-
- <listitem><para>
- Locally stored user profiles on workstations are migrated as well,
- presenting almost no disruption to the user. Saved passwords will be
- lost, just as when you administratively reset the password in Windows ADS.
- </para></listitem>
-
- <listitem><para>
- The ADMT lets you test all operations before actually performing the
- migration. Accounts and workstations can be migrated individually or in
- batches. User accounts can be safely migrated all at once (since no
- changes are made on the original domain). It is recommended to migrate only one
- or two workstations as a test before committing them all.
- </para></listitem>
-
- </itemizedlist>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<preface lang="en-US">
-<title>Acknowledgments</title>
-
- <para>
- <emphasis>Samba-3 by Example</emphasis> would not have been written except
- as a result of feedback provided by reviewers and readers of the book <emphasis>The
- Official Samba-3 HOWTO and Reference Guide.</emphasis> This second edition
- was made possible by generous feedback from Samba users. I hope this book
- more than answers the challenge and needs of many more networks that are
- languishing for a better networking solution.
- </para>
-
- <para>
- I am deeply indebted to a large group of diligent people. Space prevents
- me from listing all of them, but a few stand out as worthy of mention.
- Jelmer Vernooij made the notable contribution of building the XML production
- environment and thereby made possible the typesetting of this book.
- </para>
-
- <para>
- Samba would not have come into existence if Andrew Tridgell had not taken
- the first steps. He continues to lead the project. Under the shadow of his
- mantle are some great folks who never give up and are always ready to help.
- Thank you to: Jeremy Allison, Jerry Carter, Andrew Bartlett, Jelmer Vernooij,
- Alexander Bokovoy, Volker Lendecke, and other team members who answered my
- continuous stream of questions &smbmdash; all of which resulted in improved content
- in this book.
- </para>
-
- <para>
- My heartfelt thanks go out also to a small set of reviewers (alphabetically
- listed) who gave substantial feedback and significant suggestions for improvement:
- Tony Earnshaw, William Enestvedt, Eric Hines, Roland Gruber, Gavin Henry,
- Steven Henry, Luke Howard, Tarjei Huse, Jon Johnston, Alan Munter, Mike MacIsaac,
- Scott Mann, Ed Riddle, Geoff Scott, Santos Soler, Misty Stanley-Jones, Mark Taylor,
- and Jérôme Tournier.
- </para>
-
- <para>
- My appreciation is extended to a team of more than 30 additional reviewers who
- helped me to find my way around dark corners.
- </para>
-
- <para>
- Particular mention is due to Lyndell, Amos, and Melissa who gave me the
- latitude necessary to spend nearly an entire year writing Samba documentation,
- and then gave more so this second edition could be created.
- </para>
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<preface lang="en-US">
-<title>Foreword</title>
-
-<sect1><title>By John M. Weathersby, Executive Director, OSSI</title>
-<blockquote>
-
-<para>
-The Open Source Software Institute (OSSI) is comprised of representatives from a broad spectrum of business and
-non-business organizations that share a common interest in the promotion of development and implementation
-of open source software solutions globally, and in particular within the United States of America.
-</para>
-
-<para>
-The OSSI has global affiliations with like-minded organizations. Our affiliate in the United Kingdom is the
-Open Source Consortium (OSC). Both the OSSI and the OSC share a common objective to expand the use of open source
-software in federal, state, and municipal government agencies; and in academic institutions. We represent
-businesses that provide professional support services that answer the needs of our target organizational
-information technology consumers in an effective and cost-efficient manner.
-</para>
-
-<para>
-Open source software has matured greatly over the past five years with the result that an increasing number of
-people who hold key decisionmaking positions want to know how the business model works. They
-want to understand how problems get resolved, how questions get answered, and how the development model
-is sustained. Information and communications technology directors in defense organizations, and in other
-government agencies that deal with sensitive information, want to become familiar with development road-maps
-and, in particular, seek to evaluate the track record of the mainstream open source project teams.
-</para>
-
-<para>
-Wherever the OSSI gains entrance to new opportunities we find that Microsoft Windows technologies are the
-benchmark against which open source software solutions are measured. Two open source software projects
-are key to our ability to present a structured and convincing proposition that there are alternatives
-to the incumbent proprietary means of meeting information technology needs. They are the Apache Web Server
-and Samba.
-</para>
-
-<para>
-Just as the Apache Web Server is the standard in web serving technology, Samba is the definitive standard
-for providing interoperability with UNIX systems and other non-Microsoft operating system platforms. Both
-open source applications have a truly remarkable track record that extends for more than a decade. Both have
-demonstrated the unique capacity to innovate and maintain a level of development that has not only kept
-pace with demands, but, in many areas, each project has also proven to be an industry leader.
-</para>
-
-<para>
-One of the areas in which the Samba project has demonstrated key leadership is in documentation. The OSSI
-was delighted when we saw the Samba Team, and John H. Terpstra in particular, release two amazingly
-well-written books to help Samba software users deploy, maintain, and troubleshoot Windows networking
-installations. We were concerned that, given the large volume of documentation, the challenge to maintain
-it and keep it current might prove difficult.
-</para>
-
-<para>
-This second edition of the book, <emphasis>Samba-3 by Example</emphasis>, barely one year following the release
-of the first edition, has removed all concerns and is proof that open source solutions are a compelling choice.
-The first edition was released shortly following the release of Samba version 3.0 itself, and has become
-the authoritative instrument for training and for guiding deployment.
-</para>
-
-<para>
-I am personally aware of how much effort has gone into this second edition. John Terpstra has worked with
-government bodies and with large organizations that have deployed Samba-3 since it was released. He also
-worked to ensure that this book gained community following. He asked those who have worked at the coalface
-of large and small organizations alike, to contribute their experiences. He has captured that in this book
-and has succeeded yet again. His recipe is persistence, intuition, and a high level of respect for the people
-who use Samba.
-</para>
-
-<para>
-This book is the first source you should turn to before you deploy Samba and as you are mastering its
-deployment. I am proud and excited to be associated in a small way with such a useful tool. This book has
-reached maturity that is demonstrated by reiteration that every step in deployment must be validated.
-This book makes it easy to succeed, and difficult to fail, to gain a stable network environment.
-</para>
-
-<para>
-I recommend this book for use by all IT managers and network administrators.
-</para>
-
-</blockquote>
-
-</sect1>
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<preface lang="en-US">
-<title>Front Matter</title>
-
- <para>
- Just a place holder.
- </para>
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE glossary PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<glossary>
- <title>Glossary</title>
-
- <glossentry>
- <glossterm>Access Control List</glossterm>
- <acronym>ACL</acronym>
- <glossdef><para>
- A detailed list of permissions granted to users or groups with respect to file and network
- resource access.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Active Directory Service</glossterm>
- <acronym>ADS</acronym>
- <glossdef><para>
- A service unique to Microsoft Windows 200x servers that provides a centrally managed
- directory for management of user identities and computer objects, as well as the
- permissions each user or computer may be granted to access distributed network resources.
- ADS uses Kerberos-based authentication and LDAP over Kerberos for directory access.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Common Internet File System</glossterm>
- <acronym>CIFS</acronym>
- <glossdef><para>
- The new name for SMB. Microsoft renamed the SMB protocol to CIFS during
- the Internet hype in the 1990s. At about the time that the SMB protocol was renamed
- to CIFS, an additional dialect of the SMB protocol was in development. The need for the
- deployment of the NetBIOS layer was also removed, thus paving the way for use of the SMB
- protocol natively over TCP/IP (known as NetBIOS-less SMB or <quote>naked</quote> TCP
- transport).
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Common UNIX Printing System</glossterm>
- <acronym>CUPS</acronym>
- <glossdef><para>
- A recent implementation of a high-capability printing system for UNIX developed by
- <ulink url="http://www.easysw.com/">Easy Software Inc.</ulink>. The design objective
- of CUPS was to provide a rich print processing system that has built-in intelligence
- that is capable of correctly rendering (processing) a file that is submitted for
- printing even if it was formatted for an entirely different printer.
- </para>
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Domain Master Browser</glossterm>
- <acronym>DMB</acronym>
- <glossdef><para>
- The Domain Master Browser maintains a list of all the servers that
- have announced their services within a given workgroup or NT domain.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Domain Name Service</glossterm>
- <acronym>DNS</acronym>
- <glossdef><para>
- A protocol by which computer hostnames may be resolved to the matching IP address/es.
- DNS is implemented by the Berkeley Internet Name Daemon. There exists a recent version
- of DNS that allows dynamic name registration by network clients or by a DHCP server.
- This recent protocol is known as dynamic DNS (DDNS).
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Dynamic Host Configuration Protocol</glossterm>
- <acronym>DHCP</acronym>
- <glossdef><para>
- A protocol that was based on the BOOTP protocol that may be used to dynamically assign
- an IP address, from a reserved pool of addresses, to a network client or device.
- Additionally, DHCP may assign all network configuration settings and may be used to
- register a computer name and its address with a dynamic DNS server.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Group IDentifier</glossterm>
- <acronym>GID</acronym>
- <glossdef><para>
- The UNIX system group identifier; on older systems, a 32-bit unsigned integer, and on
- newer systems, an unsigned 64-bit integer. The GID is used in UNIX-like operating systems
- for all group-level access control.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Key Distribution Center</glossterm>
- <acronym>KDC</acronym>
- <glossdef><para>
- The Kerberos authentication protocol makes use of security keys (also called a ticket)
- by which access to network resources is controlled. The issuing of Kerberos tickets
- is effected by a KDC.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Lightweight Directory Access Protocol</glossterm>
- <acronym>LDAP</acronym>
- <glossdef>
- <para>
- The Lightweight Directory Access Protocol is a technology that
- originated from the development of X.500 protocol specifications and
- implementations. LDAP was designed as a means of rapidly searching
- through X.500 information. Later LDAP was adapted as an engine that
- could drive its own directory database. LDAP is not a database per
- se; rather it is a technology that enables high-volume search and
- locate activity from clients that wish to obtain simply defined
- information about a subset of records that are stored in a
- database. LDAP does not have a particularly efficient mechanism for
- storing records in the database, and it has no concept of transaction
- processing nor of mechanisms for preserving data consistency. LDAP is
- premised around the notion that the search and read activity far
- outweigh any need to add, delete, or modify records. LDAP does
- provide a means for replication of the database to keep slave
- servers up to date with a master. It also has built-in capability to
- handle external references and deferral.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Local Master Browser</glossterm>
- <acronym>LMB</acronym>
- <glossdef><para>
- The Local Master Browser maintains a list of all servers that have announced themselves
- within a given workgroup or NT domain on a particular broadcast isolated subnet.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Media Access Control</glossterm>
- <acronym>MAC</acronym>
- <glossdef><para>
- The hard-coded address of the physical-layer device that is attached to the network.
- All network interface controllers must have a hard-coded and unique MAC address. The
- MAC address is 48 bits long.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>NetBIOS Extended User Interface</glossterm>
- <acronym>NetBEUI</acronym>
- <glossdef><para>
- Very simple network protocol invented by IBM and Microsoft. It is used to do NetBIOS
- over Ethernet with low overhead. NetBEUI is a non-routable protocol.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Network Address Translation</glossterm>
- <acronym>NAT</acronym>
- <glossdef><para>
- Network address translation is a form of IP address masquerading. It ensures that internal
- private (RFC1918) network addresses from packets inside the network are rewritten so
- that TCP/IP packets that leave the server over a public connection are seen to come only
- from the external network address.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Network Basic Input/Output System</glossterm>
- <acronym>NetBIOS</acronym>
- <glossdef><para>
- NetBIOS is a simple application programming interface (API) invented in the 1980s
- that allows programs to send data to certain network names. NetBIOS is always run over
- another network protocol such as IPX/SPX, TCP/IP, or Logical Link Control (LLC).
- NetBIOS run over LLC is best known as NetBEUI (the NetBIOS Extended User Interface
- &smbmdash; a complete misnomer!).
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>NetBT</glossterm>
- <acronym>NBT</acronym>
- <glossdef><para>
- Protocol for transporting NetBIOS frames over TCP/IP. Uses ports 137, 138, and 139.
- NetBT is a fully routable protocol.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>NT/LanManager Security Support Provider</glossterm>
- <acronym>NTLMSSP</acronym>
- <glossdef><para>
- The NTLM Security Support Provider (NTLMSSP) service in Windows NT4/200x/XP is responsible for
- handling all NTLM authentication requests. It is the front end for protocols such as SPNEGO,
- Schannel, and other technologies. The generic protocol family supported by NTLMSSP is known as
- GSSAPI, the Generic Security Service Application Program Interface specified in RFC2078.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Server Message Block</glossterm>
- <acronym>SMB</acronym>
- <glossdef><para>
- SMB was the original name of the protocol spoken by Samba. It was invented in the 1980s
- by IBM and adopted and extended further by Microsoft. Microsoft renamed the protocol to
- CIFS during the Internet hype in the 1990s.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>The Simple and Protected GSS-API Negotiation</glossterm>
- <acronym>SPNEGO</acronym>
- <glossdef><para>
- The purpose of SPNEGO is to allow a client and server to negotiate a security mechanism for
- authentication. The protocol is specified in RFC2478 and uses tokens as built via ASN.1 DER.
- DER refers to Distinguished Encoding Rules. These are a set of common rules for creating
- binary encodings in a platform-independent manner. Samba has support for SPNEGO.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>The Official Samba-3 HOWTO and Reference Guide, Second Edition</glossterm>
- <acronym>TOSHARG2</acronym>
- <glossdef><para>
- This book makes repeated reference to <quote>The Official Samba-3 HOWTO and Reference Guide, Second
- Edition</quote> by John H. Terpstra and Jelmer R. Vernooij. This publication is available from
- Amazon.com. Publisher: Prentice Hall PTR (August 2005),
- ISBN: 013122282.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>User IDentifier</glossterm>
- <acronym>UID</acronym>
- <glossdef><para>
- The UNIX system user identifier; on older systems, a 32-bit unsigned integer, and on newer systems,
- an unsigned 64-bit integer. The UID is used in UNIX-like operating systems for all user-level access
- control.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Universal Naming Convention</glossterm>
- <acronym>UNC</acronym>
- <glossdef><para>A syntax for specifying the location of network resources (such as file shares).
- The UNC syntax was developed in the early days of MS DOS 3.x and is used internally by the SMB protocol.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Wireshark</glossterm>
- <acronym>wireshark</acronym>
- <glossdef><para>
- A network analyzer, also known as a network sniffer or a protocol analyzer. Formerly known as Ethereal, Wireshark is
- freely available for UNIX/Linux and Microsoft Windows systems from
- <ulink url="http://www.wireshark.org">the Wireshark Web site</ulink>.
- </para></glossdef>
- </glossentry>
-
-</glossary>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<preface lang="en-US">
-<title>About the Cover Artwork</title>
-
- <para>
- The cover artwork of this book continues the freedom theme of the first
- edition of <quote>Samba-3 by Example</quote>. The history of civilization
- demonstrates the fragile nature of freedom. It can be lost in a moment,
- and once lost, the cost of recovering liberty can be incredible. The last
- edition cover featured Alfred the Great who liberated England from the
- constant assault of Vikings and Norsemen. Events in England that
- finally liberated the common people came about in small steps, but
- the result should not be under-estimated. Today, as always, freedom and
- liberty are seldom appreciated until they are lost. If we can not quantify
- what is the value of freedom, we shall be little motivated to protect it.
- </para>
-
- <para>
- <emphasis>Samba-3 by Example Cover Artwork:</emphasis> The British houses
- of parliament are a symbol of the Westminster system of government. This form
- of government permits the people to govern themselves at the lowest level, yet
- it provides for courts of appeal that are designed to protect freedom and to
- hold back all forces of tyranny. The clock is a pertinent symbol of the
- importance of time and place.
- </para>
-
- <para>
- The information technology industry is being challenged by the imposition of
- new laws, hostile litigation, and the imposition of significant constraint
- of practice that threatens to remove the freedom to develop and deploy open
- source software solutions. Samba is a software solution that epitomizes freedom
- of choice in network interoperability for Microsoft Windows clients.
- </para>
-
- <para>
- I hope you will take the time needed to deploy it well, and that you may realize
- the greatest benefits that may be obtained. You are free to use it in ways never
- considered, but in doing so there may be some obstacles. Every obstacle that is
- overcome adds to the freedom you can enjoy. Use Samba well, and it will serve
- you well.
- </para>
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<preface id="preface">
- <title>Preface</title>
-
- <para>
- Network administrators live busy lives. We face distractions and pressures
- that drive us to seek proven, working case scenarios that can be easily
- implemented. Often this approach lands us in trouble. There is a
- saying that, geometrically speaking, the shortest distance between two
- points is a straight line, but practically we find that the quickest
- route to a stable network solution is the long way around.
- </para>
-
- <para>
- This book is your means to the straight path. It provides step-by-step,
- proven, working examples of Samba deployments. If you want to deploy
- Samba with the least effort, or if you want to become an expert at deploying
- Samba without having to search through lots of documentation, this
- book is the ticket to your destination.
- </para>
-
- <para>
- Samba is software that can be run on a platform other than Microsoft Windows,
- for example, UNIX, Linux, IBM System 390, OpenVMS, and other operating systems.
- Samba uses the TCP/IP protocol that is installed on the host server. When
- correctly configured, it allows that host to interact with a Microsoft Windows
- client or server as if it is a Windows file and print server. This book
- will help you to implement Windows-compatible file and print services.
- </para>
-
- <para>
- The examples presented in this book are typical of various businesses and
- reflect the problems and challenges they face. Care has been taken to preserve
- attitudes, perceptions, practices, and demands from real network case studies.
- The maximum benefit may be obtained from this book by working carefully through
- each exercise. You may be in a hurry to satisfy a specific need, so feel
- free to locate the example that most closely matches your need, copy it, and
- innovate as much as you like. Above all, enjoy the process of learning the
- secrets of MS Windows networking that is truly liberated by Samba.
- </para>
-
- <para>
- The focus of attention in this book is Samba. Specific notes are made in
- respect of how Samba may be made secure. This book does not attempt to provide
- detailed information regarding secure operation and configuration of peripheral
- services and applications such as OpenLDAP, DNS and DHCP, the need for which
- can be met from other resources that are dedicated to the subject.
- </para>
-
- <sect1>
- <title>Why Is This Book Necessary?</title>
-
- <para>
- This book is the result of observations and feedback. The feedback from
- the Samba-HOWTO-Collection has been positive and complimentary. There
- have been requests for far more worked examples, a
- <quote>Samba Cookbook,</quote> and for training materials to
- help kick-start the process of mastering Samba.
- </para>
-
- <para>
- The Samba mailing lists users have asked for sample configuration files
- that work. It is natural to question one's own ability to correctly
- configure a complex tool such as Samba until a minimum necessary
- knowledge level has been attained.
- </para>
-
- <para>
- The Samba-HOWTO-Collection &smbmdash; as does <emphasis>The Official Samba-3 HOWTO and
- Reference Guide</emphasis> &smbmdash; documents Samba features and functionality in
- a topical context. This book takes a completely different approach. It
- walks through Samba network configurations that are working within particular
- environmental contexts, providing documented step-by-step implementations.
- All example case configuration files, scripts, and other tools are provided
- on the CD-ROM. This book is descriptive, provides detailed diagrams, and
- makes deployment of Samba a breeze.
- </para>
-
- <sect2>
- <title>Samba 3.0.20 Update Edition</title>
-
- <para>
- The Samba 3.0.x series has been remarkably popular. At the time this book first
- went to print samba-3.0.2 was being released. There have been significant modifications
- and enhancements between samba-3.0.2 and samba-3.0.14 (the current release) that
- necessitate this documentation update. This update has the specific intent to
- refocus this book so that its guidance can be followed for samba-3.0.20
- and beyond. Further changes are expected as Samba matures further and will
- be reflected in future updates.
- </para>
-
- <para>
- The changes shown in <link linkend="pref-new"/> are incorporated in this update.
- </para>
-
- <table id="pref-new">
- <title>Samba Changes &smbmdash; 3.0.2 to 3.0.20</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="justify"/>
- <thead>
- <row>
- <entry align="left">
- <para>
- New Feature
- </para>
- </entry>
- <entry align="left">
- <para>
- Description
- </para>
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <para>
- Winbind Case Handling
- </para>
- </entry>
- <entry>
- <para>
- User and group names returned by <command>winbindd</command> are now converted to lower case
- for better consistency. Samba implementations that depend on the case of information returned
- by winbind (such as %u and %U) must now convert the dependency to expecting lower case values.
- This affects mail spool files, home directories, valid user lines in the &smb.conf; file, etc.
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Schema Changes
- </para>
- </entry>
- <entry>
- <para>
- Addition of code to handle password aging, password uniqueness controls, bad
- password instances at logon time, have made necessary extensions to the SambaSAM
- schema. This change affects all sites that use LDAP and means that the directory
- schema must be updated.
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Username Map Handling
- </para>
- </entry>
- <entry>
- <para>
- Samba-3.0.8 redefined the behavior: Local authentication results in a username map file
- lookup before authenticating the connection. All authentication via an external domain
- controller will result in the use of the fully qualified name (i.e.: DOMAIN\username)
- after the user has been successfully authenticated.
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- UNIX Extension Handling
- </para>
- </entry>
- <entry>
- <para>
- Symbolically linked files and directories on the UNIX host to absolute paths will
- now be followed. This can be turned off using <quote>wide links = No</quote> in
- the share stanza in the &smb.conf; file. Turning off <quote>wide links</quote>
- support will degrade server performance because each path must be checked.
- </para>
- </entry>
- </row>
- <row>
- <entry>
- <para>
- Privileges Support
- </para>
- </entry>
- <entry>
- <para>
- Versions of Samba prior to samba-3.0.11 required the use of the UNIX <constant>root</constant>
- account from network Windows clients. The new <quote>enable privileges = Yes</quote> capability
- means that functions such as adding machines to the domain, managing printers, etc. can now
- be delegated to normal user accounts or to groups of users.
- </para>
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </sect2>
-
- </sect1>
-
- <sect1>
- <title>Prerequisites</title>
-
- <para>
- This book is not a tutorial on UNIX or Linux administration. UNIX and Linux
- training is best obtained from books dedicated to the subject. This book
- assumes that you have at least the basic skill necessary to use these operating
- systems, and that you can use a basic system editor to edit and configure files.
- It has been written with the assumption that you have experience with Samba,
- have read <emphasis>The Official Samba-3 HOWTO and Reference Guide</emphasis> and
- the Samba-HOWTO-Collection, or that you have familiarity with Microsoft Windows.
- </para>
-
- <para>
- If you do not have this experience, you can follow the examples in this book but may
- find yourself at times intimidated by assumptions made. In this situation, you
- may need to refer to administrative guides or manuals for your operating system
- platform to find what is the best method to achieve what the text of this book describes.
- </para>
-
- </sect1>
-
- <sect1>
- <title>Approach</title>
-
- <para>
- The first chapter deals with some rather thorny network analysis issues. Do not be
- put off by this. The information you glean, even without a detailed understanding
- of network protocol analysis, can help you understand how Windows networking functions.
- </para>
-
- <para>
- Each following chapter of this book opens with the description of a networking solution
- sought by a hypothetical site. Bob Jordan is a hypothetical decision maker
- for an imaginary company, <constant>Abmas Biz NL</constant>. We will use the
- non-existent domain name <constant>abmas.biz</constant>. All <emphasis>facts</emphasis>
- presented regarding this company are fictitious and have been drawn from a variety of real
- business scenarios over many years. Not one of these reveal the identify of the
- real-world company from which the scenario originated.
- </para>
-
- <para>
- In any case, Mr. Jordan likes to give all his staff nasty little assignments.
- Stanley Saroka is one of his proteges; Christine Roberson is the network administrator
- Bob trusts. Jordan is inclined to treat other departments well because they finance
- Abmas IT operations.
- </para>
-
- <para>
- Each chapter presents a summary of the network solution we have chosen to
- demonstrate together with a rationale to help you to understand the
- thought process that drove that solution. The chapter then documents in precise
- detail all configuration files and steps that must be taken to implement the
- example solution. Anyone wishing to gain serious value from this book will
- do well to take note of the implications of points made, so watch out for the
- <emphasis>this means that</emphasis> notations.
- </para>
-
- <para>
- Each chapter has a set of questions and answers to help you to
- to understand and digest key attributes of the solutions presented.
- </para>
-
- </sect1>
-
- <sect1>
- <title>Summary of Topics</title>
-
- <para>
- The contents of this second edition of <emphasis>Samba-3 by Example</emphasis>
- have been rearranged based on feedback from purchasers of the first edition.
- </para>
-
- <para>
- Clearly the first edition contained most of what was needed and that was missing
- from other books that cover this difficult subject. The new arrangement adds
- additional material to meet consumer requests and includes changes that originated
- as suggestions for improvement.
- </para>
-
- <para>
- Chapter 1 now dives directly into the heart of the implementation of Windows
- file and print server networks that use Samba at the heart.
- </para>
-
- <variablelist>
- <varlistentry>
- <term>Chapter 1 &smbmdash; No Frills Samba Servers.</term><listitem>
- <para>
- Here you design a solution for three different business scenarios, each for a
- company called Abmas. There are two simple networking problems and one slightly
- more complex networking challenge. In the first two cases, Abmas has a small
- simple office, and they want to replace a Windows 9x peer-to-peer network. The
- third example business uses Windows 2000 Professional. This must be simple,
- so let's see how far we can get. If successful, Abmas grows quickly and
- soon needs to replace all servers and workstations.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; This chapter demands:
- <itemizedlist>
- <listitem><para>Case 1: The simplest &smb.conf; file that may
- reasonably be used. Works with Samba-2.x also. This
- configuration uses Share Mode security. Encrypted
- passwords are not used, so there is no
- <filename>smbpasswd</filename> file.
- </para></listitem>
-
- <listitem><para>Case 2: Another simple &smb.conf; file that adds
- WINS support and printing support. This case deals with
- a special requirement that demonstrates how to deal with
- purpose-built software that has a particular requirement
- for certain share names and printing demands. This
- configuration uses Share Mode security and also works with
- Samba-2.x. Encrypted passwords are not used, so there is no
- <filename>smbpasswd</filename> file.
- </para></listitem>
-
- <listitem><para>Case 3: This &smb.conf; configuration uses User Mode
- security. The file share configuration demonstrates
- the ability to provide master access to an administrator
- while restricting all staff to their own work areas.
- Encrypted passwords are used, so there is an implicit
- <filename>smbpasswd</filename> file.
- </para></listitem>
- </itemizedlist>
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 2 &smbmdash; Small Office Networking.</term><listitem>
- <para>
- Abmas is a successful company now. They have 50 network users
- and want a little more varoom from the network. This is a typical
- small office and they want better systems to help them to grow. This is
- your chance to really give advanced users a bit more functionality and usefulness.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
- makes use of encrypted passwords, so there is an <filename>smbpasswd</filename>
- file. It also demonstrates use of the <parameter>valid users</parameter> and
- <parameter>valid groups</parameter> to restrict share access. The Windows
- clients access the server as Domain members. Mobile users log onto
- the Domain while in the office, but use a local machine account while on the
- road. The result is an environment that answers mobile computing user needs.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 3 &smbmdash; Secure Office Networking.</term><listitem>
- <para>
- Abmas is growing rapidly now. Money is a little tight, but with 130
- network users, security has become a concern. They have many new machines
- to install and the old equipment will be retired. This time they want the
- new network to scale and grow for at least two years. Start with a sufficient
- system and allow room for growth. You are now implementing an Internet
- connection and have a few reservations about user expectations.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
- makes use of encrypted passwords, and you can use a <filename>tdbsam</filename>
- password backend. Domain logons are introduced. Applications are served from the central
- server. Roaming profiles are mandated. Access to the server is tightened up
- so that only domain members can access server resources. Mobile computing
- needs still are catered to.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 4 &smbmdash; The 500 User Office.</term><listitem>
- <para>
- The two-year projections were met. Congratulations, you are a star.
- Now Abmas needs to replace the network. Into the existing user base, they
- need to merge a 280-user company they just acquired. It is time to build a serious
- network. There are now three buildings on one campus and your assignment is
- to keep everyone working while a new network is rolled out. Oh, isn't it nice
- to roll out brand new clients and servers! Money is no longer tight, you get
- to buy and install what you ask for. You will install routers and a firewall.
- This is exciting!
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
- makes use of encrypted passwords, and a <filename>tdbsam</filename>
- password backend is used. You are not ready to launch into LDAP yet, so you
- accept the limitation of having one central Domain Controller with a Domain
- Member server in two buildings on your campus. A number of clever techniques
- are used to demonstrate some of the smart options built into Samba.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 5 &smbmdash; Making Happy Users.</term><listitem>
- <para>
- Congratulations again. Abmas is happy with your services and you have been given another raise.
- Your users are becoming much more capable and are complaining about little
- things that need to be fixed. Are you up to the task? Mary says it takes her 20 minutes
- to log onto the network and it is killing her productivity. Email is a bit <emphasis>
- unreliable</emphasis> &smbmdash; have you been sleeping on the job? We do not discuss the
- technology of email but when the use of mail clients breaks because of networking
- problems, you had better get on top of it. It's time for a change.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; This &smb.conf; file
- makes use of encrypted passwords; a distributed <filename>ldapsam</filename>
- password backend is used. Roaming profiles are enabled. Desktop profile controls
- are introduced. Check out the techniques that can improve the user experience
- of network performance. As a special bonus, this chapter documents how to configure
- smart downloading of printer drivers for drag-and-drop printing support. And, yes,
- the secret of configuring CUPS is clearly documented. Go for it; this one will
- tease you, too.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 6 &smbmdash; A Distributed 2000 User Network.</term><listitem>
- <para>
- Only eight months have passed, and Abmas has acquired another company. You now need to expand
- the network further. You have to deal with a network that spans several countries.
- There are three new networks in addition to the original three buildings at the head-office
- campus. The head office is in New York and you have branch offices in Washington, Los Angeles, and
- London. Your desktop standard is Windows XP Professional. In many ways, everything has changed
- and yet it must remain the same. Your team is primed for another roll-out. You know there are
- further challenges ahead.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; Slave
- LDAP servers are introduced. This is a brief chapter; it assumes that the
- technology has been mastered and gets right down to concepts and how to deploy them.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 7 &smbmdash; Adding UNIX/Linux Servers and Clients.</term><listitem>
- <para>
- Well done, Bob, your team has achieved much. Now help Abmas integrate the entire network.
- You want central control and central support and you need to cut costs. How can you reduce administrative
- overheads and yet get better control of the network?
- </para>
-
- <para>
- This chapter has been contributed by Mark Taylor <email>mark.taylor@siriusit.co.uk</email>
- and is based on a live site. For further information regarding this example case,
- please contact Mark directly.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; It is time to consider how to add Samba servers
- and UNIX and Linux network clients. Users who convert to Linux want to be able to log on
- using Windows network accounts. You explore nss_ldap, pam_ldap, winbind, and a few neat
- techniques for taking control. Are you ready for this?
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 8 &smbmdash; Updating Samba.</term><listitem>
- <para>
- This chapter is the result of repeated requests for better documentation of the steps
- that must be followed when updating or upgrading a Samba server. It attempts to cover
- the entire subject in broad-brush but at the same time provides detailed background
- information that is not covered elsewhere in the Samba documentation.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; Samba stores a lot of essential network
- information in a large and growing collection of files. This chapter documents the
- essentials of where those files may be located and how to find them. It also provides
- an insight into inter-related matters that affect a Samba installation.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 9 &smbmdash; Migrating NT4 Domain to Samba.</term><listitem>
- <para>
- Another six months have passed. Abmas has acquired yet another company. You will find a
- way to migrate all users off the old network onto the existing network without loss
- of passwords and will effect the change-over during one weekend. May the force (and caffeine) be with
- you, may you keep your back to the wind and may the sun shine on your face.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; This chapter demonstrates the use of
- the <command>net rpc migrate</command> facility using an LDAP ldapsam backend, and also
- using a tdbsam passdb backend. Both are much-asked-for examples of NT4 Domain migration.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 10 &smbmdash; Migrating NetWare 4.11 Server to Samba.</term><listitem>
- <para>
- Misty Stanley-Jones has contributed information that summarizes her experience at migration
- from a NetWare server to Samba.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; The documentation provided demonstrates
- how one site migrated from NetWare to Samba. Some alternatives tools are mentioned. These
- could be used to provide another pathway to a successful migration.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 11 &smbmdash; Active Directory, Kerberos and Security.</term><listitem>
- <para>
- Abmas has acquired another company that has just migrated to running Windows Server 2003 and
- Active Directory. One of your staff makes offhand comments that land you in hot water.
- A network security auditor is hired by the head of the new business and files a damning
- report, and you must address the <emphasis>defects</emphasis> reported. You have hired new
- network engineers who want to replace Microsoft Active Directory with a pure Kerberos
- solution. How will you handle this?
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; This chapter is your answer. Learn about
- share access controls, proper use of UNIX/Linux file system access controls, and Windows
- 200x Access Control Lists. Follow these steps to beat the critics.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 12 &smbmdash; Integrating Additional Services.</term><listitem>
- <para>
- The battle is almost over, Samba has won the day. Your team are delighted and now you
- find yourself at yet another cross-roads. Abmas have acquired a snack food business, you
- made promises you must keep. IT costs must be reduced, you have new resistance, but you
- will win again. This time you choose to install the Squid proxy server to validate the
- fact that Samba is far more than just a file and print server. SPNEGO authentication
- support means that your Microsoft Windows clients gain transparent proxy access.
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; Samba provides the <command>ntlm_auth</command>
- module that makes it possible for MS Windows Internet Explorer to connect via the Squid Web
- and FTP proxy server. You will configure Samba as well as Squid to deliver authenticated
- access control using the Active Directory Domain user security credentials.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 13 &smbmdash; Performance, Reliability and Availability.</term><listitem>
- <para>
- Bob, are you sure the new Samba server is up to the load? Your network is serving many
- users who risk becoming unproductive. What can you do to keep ahead of demand? Can you
- keep the cost under control also? What can go wrong?
- </para>
-
- <para><emphasis>TechInfo</emphasis> &smbmdash; Hot tips that put chili into your
- network. Avoid name resolution problems, identify potential causes of network collisions,
- avoid Samba configuration options that will weigh the server down. MS distributed file
- services to make your network fly and much more. This chapter contains a good deal of
- <quote>Did I tell you about this...?</quote> type of hints to help keep your name on the top
- performers list.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 14 &smbmdash; Samba Support.</term><listitem>
- <para>
- This chapter has been added specifically to help those who are seeking professional
- paid support for Samba. The critics of Open Source Software often assert that
- there is no support for free software. Some critics argue that free software
- undermines the service that proprietary commercial software vendors depend on.
- This chapter explains what are the support options for Samba and the fact that
- a growing number of businesses make money by providing commercial paid-for
- Samba support.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 15 &smbmdash; A Collection of Useful Tid-bits.</term><listitem>
- <para>
- Sometimes it seems that there is not a good place for certain odds and ends that
- impact Samba deployment. Some readers would argue that everyone can be expected
- to know this information, or at least be able to find it easily. So to avoid
- offending a reader's sensitivities, the tid-bits have been placed in this chapter.
- Do check out the contents, you may find something of value among the loose ends.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Chapter 16 &smbmdash; Windows Networking Primer.</term><listitem>
- <para>
- Here we cover practical exercises to help us to understand how MS Windows
- network protocols function. A network protocol analyzer helps you to
- appreciate the fact that Windows networking is highly dependent on broadcast
- messaging. Additionally, you can look into network packets that a Windows
- client sends to a network server to set up a network connection. On completion,
- you should have a basic understanding of how network browsing functions and
- have seen some of the information a Windows client sends to
- a file and print server to create a connection over which file and print
- operations may take place.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
- </sect1>
-
- <!-- the conventions used in this book -->
- <xi:include href="conventions.xml" xmlns:xi="http://www.w3.org/2003/XInclude" />
-
-</preface>
-
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
- <sect1>
- <title>Conventions Used</title>
-
- <para>
- The following notation conventions are used throughout this book:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- TOSHARG2 is used as an abbreviation for the book, <quote>The Official Samba-3
- HOWTO and Reference Guide, Second Edition</quote> Editors: John H. Terpstra and Jelmer R. Vernooij,
- Publisher: Prentice Hall, ISBN: 0131882228.
- </para>
- </listitem>
-
- <listitem>
- <para>
- S3bE2 is used as an abbreviation for the book, <quote>Samba-3 by Example, Second Edition</quote>
- Editors: John H. Terpstra, Publisher: Prentice Hall, ISBN: 013188221X.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Directories and filenames appear in mono-font. For example,
- <filename>/etc/pam.conf</filename>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Executable names are bolded. For example, <command>smbd</command>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Menu items and buttons appear in bold. For example, click <guibutton>Next</guibutton>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Selecting a menu item is indicated as:
- <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Control Panel</guimenuitem>
- <guimenuitem>Administrative Tools</guimenuitem>
- <guimenuitem>Active Directory Users and Computers</guimenuitem>
- </menuchoice>
- </para>
- </listitem>
- </itemizedlist>
-
- </sect1>
-
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-<appendix>
- <title>
- <acronym>GNU</acronym> General Public License version 3
- </title>
- <para>
- Version 3, 29 June 2007
- </para>
- <para>
- Copyright © 2007 Free Software Foundation, Inc.
- <ulink url="http://fsf.org/">http://fsf.org/</ulink>
- </para>
- <para>
- Everyone is permitted to copy and distribute verbatim copies of this license
- document, but changing it is not allowed.
- </para>
- <bridgehead renderas="sect1">
- Preamble
- </bridgehead>
- <para>
- The <acronym>GNU</acronym> General Public License is a free, copyleft
- license for software and other kinds of works.
- </para>
- <para>
- The licenses for most software and other practical works are designed to
- take away your freedom to share and change the works. By contrast, the
- <acronym>GNU</acronym> General Public License is intended to guarantee your
- freedom to share and change all versions of a program—to make sure it
- remains free software for all its users. We, the Free Software Foundation,
- use the <acronym>GNU</acronym> General Public License for most of our
- software; it applies also to any other work released this way by its
- authors. You can apply it to your programs, too.
- </para>
- <para>
- When we speak of free software, we are referring to freedom, not price. Our
- General Public Licenses are designed to make sure that you have the freedom
- to distribute copies of free software (and charge for them if you wish),
- that you receive source code or can get it if you want it, that you can
- change the software or use pieces of it in new free programs, and that you
- know you can do these things.
- </para>
- <para>
- To protect your rights, we need to prevent others from denying you these
- rights or asking you to surrender the rights. Therefore, you have certain
- responsibilities if you distribute copies of the software, or if you modify
- it: responsibilities to respect the freedom of others.
- </para>
- <para>
- For example, if you distribute copies of such a program, whether gratis or
- for a fee, you must pass on to the recipients the same freedoms that you
- received. You must make sure that they, too, receive or can get the source
- code. And you must show them these terms so they know their rights.
- </para>
- <para>
- Developers that use the <acronym>GNU</acronym> <acronym>GPL</acronym>
- protect your rights with two steps: (1) assert copyright on the software,
- and (2) offer you this License giving you legal permission to copy,
- distribute and/or modify it.
- </para>
- <para>
- For the developers’ and authors’ protection, the
- <acronym>GPL</acronym> clearly explains that there is no warranty for this
- free software. For both users’ and authors’ sake, the
- <acronym>GPL</acronym> requires that modified versions be marked as changed,
- so that their problems will not be attributed erroneously to authors of
- previous versions.
- </para>
- <para>
- Some devices are designed to deny users access to install or run modified
- versions of the software inside them, although the manufacturer can do so.
- This is fundamentally incompatible with the aim of protecting users’
- freedom to change the software. The systematic pattern of such abuse occurs
- in the area of products for individuals to use, which is precisely where it
- is most unacceptable. Therefore, we have designed this version of the
- <acronym>GPL</acronym> to prohibit the practice for those products. If such
- problems arise substantially in other domains, we stand ready to extend this
- provision to those domains in future versions of the <acronym>GPL</acronym>,
- as needed to protect the freedom of users.
- </para>
- <para>
- Finally, every program is threatened constantly by software patents. States
- should not allow patents to restrict development and use of software on
- general-purpose computers, but in those that do, we wish to avoid the
- special danger that patents applied to a free program could make it
- effectively proprietary. To prevent this, the <acronym>GPL</acronym>
- assures that patents cannot be used to render the program non-free.
- </para>
- <para>
- The precise terms and conditions for copying, distribution and modification
- follow.
- </para>
- <bridgehead>
- TERMS AND CONDITIONS
- </bridgehead>
- <bridgehead renderas="sect1">
- 0. Definitions.
- </bridgehead>
- <para>
- “This License” refers to version 3 of the <acronym>GNU</acronym>
- General Public License.
- </para>
- <para>
- “Copyright” also means copyright-like laws that apply to other
- kinds of works, such as semiconductor masks.
- </para>
- <para>
- “The Program” refers to any copyrightable work licensed under
- this License. Each licensee is addressed as “you”.
- “Licensees” and “recipients” may be individuals or
- organizations.
- </para>
- <para>
- To “modify” a work means to copy from or adapt all or part of
- the work in a fashion requiring copyright permission, other than the making
- of an exact copy. The resulting work is called a “modified
- version” of the earlier work or a work “based on” the
- earlier work.
- </para>
- <para>
- A “covered work” means either the unmodified Program or a work
- based on the Program.
- </para>
- <para>
- To “propagate” a work means to do anything with it that, without
- permission, would make you directly or secondarily liable for infringement
- under applicable copyright law, except executing it on a computer or
- modifying a private copy. Propagation includes copying, distribution (with
- or without modification), making available to the public, and in some
- countries other activities as well.
- </para>
- <para>
- To “convey” a work means any kind of propagation that enables
- other parties to make or receive copies. Mere interaction with a user
- through a computer network, with no transfer of a copy, is not conveying.
- </para>
- <para>
- An interactive user interface displays “Appropriate Legal
- Notices” to the extent that it includes a convenient and prominently
- visible feature that (1) displays an appropriate copyright notice, and (2)
- tells the user that there is no warranty for the work (except to the extent
- that warranties are provided), that licensees may convey the work under this
- License, and how to view a copy of this License. If the interface presents
- a list of user commands or options, such as a menu, a prominent item in the
- list meets this criterion.
- </para>
- <bridgehead renderas="sect1">
- 1. Source Code.
- </bridgehead>
- <para>
- The “source code” for a work means the preferred form of the
- work for making modifications to it. “Object code” means any
- non-source form of a work.
- </para>
- <para>
- A “Standard Interface” means an interface that either is an
- official standard defined by a recognized standards body, or, in the case of
- interfaces specified for a particular programming language, one that is
- widely used among developers working in that language.
- </para>
- <para>
- The “System Libraries” of an executable work include anything,
- other than the work as a whole, that (a) is included in the normal form of
- packaging a Major Component, but which is not part of that Major Component,
- and (b) serves only to enable use of the work with that Major Component, or
- to implement a Standard Interface for which an implementation is available
- to the public in source code form. A “Major Component”, in this
- context, means a major essential component (kernel, window system, and so
- on) of the specific operating system (if any) on which the executable work
- runs, or a compiler used to produce the work, or an object code interpreter
- used to run it.
- </para>
- <para>
- The “Corresponding Source” for a work in object code form means
- all the source code needed to generate, install, and (for an executable
- work) run the object code and to modify the work, including scripts to
- control those activities. However, it does not include the work’s
- System Libraries, or general-purpose tools or generally available free
- programs which are used unmodified in performing those activities but which
- are not part of the work. For example, Corresponding Source includes
- interface definition files associated with source files for the work, and
- the source code for shared libraries and dynamically linked subprograms that
- the work is specifically designed to require, such as by intimate data
- communication or control flow between those subprograms and other parts of
- the work.
- </para>
- <para>
- The Corresponding Source need not include anything that users can regenerate
- automatically from other parts of the Corresponding Source.
- </para>
- <para>
- The Corresponding Source for a work in source code form is that same work.
- </para>
- <bridgehead renderas="sect1">
- 2. Basic Permissions.
- </bridgehead>
- <para>
- All rights granted under this License are granted for the term of copyright
- on the Program, and are irrevocable provided the stated conditions are met.
- This License explicitly affirms your unlimited permission to run the
- unmodified Program. The output from running a covered work is covered by
- this License only if the output, given its content, constitutes a covered
- work. This License acknowledges your rights of fair use or other
- equivalent, as provided by copyright law.
- </para>
- <para>
- You may make, run and propagate covered works that you do not convey,
- without conditions so long as your license otherwise remains in force. You
- may convey covered works to others for the sole purpose of having them make
- modifications exclusively for you, or provide you with facilities for
- running those works, provided that you comply with the terms of this License
- in conveying all material for which you do not control copyright. Those
- thus making or running the covered works for you must do so exclusively on
- your behalf, under your direction and control, on terms that prohibit them
- from making any copies of your copyrighted material outside their
- relationship with you.
- </para>
- <para>
- Conveying under any other circumstances is permitted solely under the
- conditions stated below. Sublicensing is not allowed; section 10 makes it
- unnecessary.
- </para>
- <bridgehead renderas="sect1">
- 3. Protecting Users’ Legal Rights From Anti-Circumvention Law.
- </bridgehead>
- <para>
- No covered work shall be deemed part of an effective technological measure
- under any applicable law fulfilling obligations under article 11 of the WIPO
- copyright treaty adopted on 20 December 1996, or similar laws prohibiting or
- restricting circumvention of such measures.
- </para>
- <para>
- When you convey a covered work, you waive any legal power to forbid
- circumvention of technological measures to the extent such circumvention is
- effected by exercising rights under this License with respect to the covered
- work, and you disclaim any intention to limit operation or modification of
- the work as a means of enforcing, against the work’s users, your or
- third parties’ legal rights to forbid circumvention of technological
- measures.
- </para>
- <bridgehead renderas="sect1">
- 4. Conveying Verbatim Copies.
- </bridgehead>
- <para>
- You may convey verbatim copies of the Program’s source code as you
- receive it, in any medium, provided that you conspicuously and appropriately
- publish on each copy an appropriate copyright notice; keep intact all
- notices stating that this License and any non-permissive terms added in
- accord with section 7 apply to the code; keep intact all notices of the
- absence of any warranty; and give all recipients a copy of this License
- along with the Program.
- </para>
- <para>
- You may charge any price or no price for each copy that you convey, and you
- may offer support or warranty protection for a fee.
- </para>
- <bridgehead renderas="sect1">
- 5. Conveying Modified Source Versions.
- </bridgehead>
- <para>
- You may convey a work based on the Program, or the modifications to produce
- it from the Program, in the form of source code under the terms of section
- 4, provided that you also meet all of these conditions:
- </para>
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>
- The work must carry prominent notices stating that you modified it, and
- giving a relevant date.
- </para>
- </listitem>
- <listitem>
- <para>
- The work must carry prominent notices stating that it is released under
- this License and any conditions added under section 7. This requirement
- modifies the requirement in section 4 to “keep intact all
- notices”.
- </para>
- </listitem>
- <listitem>
- <para>
- You must license the entire work, as a whole, under this License to
- anyone who comes into possession of a copy. This License will therefore
- apply, along with any applicable section 7 additional terms, to the
- whole of the work, and all its parts, regardless of how they are
- packaged. This License gives no permission to license the work in any
- other way, but it does not invalidate such permission if you have
- separately received it.
- </para>
- </listitem>
- <listitem>
- <para>
- If the work has interactive user interfaces, each must display
- Appropriate Legal Notices; however, if the Program has interactive
- interfaces that do not display Appropriate Legal Notices, your work need
- not make them do so.
- </para>
- </listitem>
- </orderedlist>
- <para>
- A compilation of a covered work with other separate and independent works,
- which are not by their nature extensions of the covered work, and which are
- not combined with it such as to form a larger program, in or on a volume of
- a storage or distribution medium, is called an “aggregate” if
- the compilation and its resulting copyright are not used to limit the access
- or legal rights of the compilation’s users beyond what the individual works
- permit. Inclusion of a covered work in an aggregate does not cause
- this License to apply to the other parts of the aggregate.
- </para>
- <bridgehead renderas="sect1">
- 6. Conveying Non-Source Forms.
- </bridgehead>
- <para>
- You may convey a covered work in object code form under the terms of
- sections 4 and 5, provided that you also convey the machine-readable
- Corresponding Source under the terms of this License, in one of these ways:
- </para>
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>
- Convey the object code in, or embodied in, a physical product (including
- a physical distribution medium), accompanied by the Corresponding Source
- fixed on a durable physical medium customarily used for software
- interchange.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey the object code in, or embodied in, a physical product (including
- a physical distribution medium), accompanied by a written offer, valid
- for at least three years and valid for as long as you offer spare parts
- or customer support for that product model, to give anyone who possesses
- the object code either (1) a copy of the Corresponding Source for all
- the software in the product that is covered by this License, on a
- durable physical medium customarily used for software interchange, for a
- price no more than your reasonable cost of physically performing this
- conveying of source, or (2) access to copy the Corresponding Source from
- a network server at no charge.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey individual copies of the object code with a copy of the written
- offer to provide the Corresponding Source. This alternative is allowed
- only occasionally and noncommercially, and only if you received the
- object code with such an offer, in accord with subsection 6b.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey the object code by offering access from a designated place
- (gratis or for a charge), and offer equivalent access to the
- Corresponding Source in the same way through the same place at no
- further charge. You need not require recipients to copy the
- Corresponding Source along with the object code. If the place to copy
- the object code is a network server, the Corresponding Source may be on
- a different server (operated by you or a third party) that supports
- equivalent copying facilities, provided you maintain clear directions
- next to the object code saying where to find the Corresponding Source.
- Regardless of what server hosts the Corresponding Source, you remain
- obligated to ensure that it is available for as long as needed to
- satisfy these requirements.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey the object code using peer-to-peer transmission, provided you
- inform other peers where the object code and Corresponding Source of the
- work are being offered to the general public at no charge under
- subsection 6d.
- </para>
- </listitem>
- </orderedlist>
- <para>
- A separable portion of the object code, whose source code is excluded from
- the Corresponding Source as a System Library, need not be included in
- conveying the object code work.
- </para>
- <para>
- A “User Product” is either (1) a “consumer product”,
- which means any tangible personal property which is normally used for
- personal, family, or household purposes, or (2) anything designed or sold
- for incorporation into a dwelling. In determining whether a product is a
- consumer product, doubtful cases shall be resolved in favor of coverage.
- For a particular product received by a particular user, “normally
- used” refers to a typical or common use of that class of product,
- regardless of the status of the particular user or of the way in which the
- particular user actually uses, or expects or is expected to use, the
- product. A product is a consumer product regardless of whether the product
- has substantial commercial, industrial or non-consumer uses, unless such
- uses represent the only significant mode of use of the product.
- </para>
- <para>
- “Installation Information” for a User Product means any methods,
- procedures, authorization keys, or other information required to install and
- execute modified versions of a covered work in that User Product from a
- modified version of its Corresponding Source. The information must suffice
- to ensure that the continued functioning of the modified object code is in
- no case prevented or interfered with solely because modification has been
- made.
- </para>
- <para>
- If you convey an object code work under this section in, or with, or
- specifically for use in, a User Product, and the conveying occurs as part of
- a transaction in which the right of possession and use of the User Product
- is transferred to the recipient in perpetuity or for a fixed term
- (regardless of how the transaction is characterized), the Corresponding
- Source conveyed under this section must be accompanied by the Installation
- Information. But this requirement does not apply if neither you nor any
- third party retains the ability to install modified object code on the User
- Product (for example, the work has been installed in
- <acronym>ROM</acronym>).
- </para>
- <para>
- The requirement to provide Installation Information does not include a
- requirement to continue to provide support service, warranty, or updates for
- a work that has been modified or installed by the recipient, or for the User
- Product in which it has been modified or installed. Access to a network may
- be denied when the modification itself materially and adversely affects the
- operation of the network or violates the rules and protocols for
- communication across the network.
- </para>
- <para>
- Corresponding Source conveyed, and Installation Information provided, in
- accord with this section must be in a format that is publicly documented
- (and with an implementation available to the public in source code form),
- and must require no special password or key for unpacking, reading or
- copying.
- </para>
- <bridgehead renderas="sect1">
- 7. Additional Terms.
- </bridgehead>
- <para>
- “Additional permissions” are terms that supplement the terms of
- this License by making exceptions from one or more of its conditions.
- Additional permissions that are applicable to the entire Program shall be
- treated as though they were included in this License, to the extent that
- they are valid under applicable law. If additional permissions apply only
- to part of the Program, that part may be used separately under those
- permissions, but the entire Program remains governed by this License
- without regard to the additional permissions.
- </para>
- <para>
- When you convey a copy of a covered work, you may at your option remove any
- additional permissions from that copy, or from any part of it. (Additional
- permissions may be written to require their own removal in certain cases
- when you modify the work.) You may place additional permissions on
- material, added by you to a covered work, for which you have or can give
- appropriate copyright permission.
- </para>
- <para>
- Notwithstanding any other provision of this License, for material you add
- to a covered work, you may (if authorized by the copyright holders of that
- material) supplement the terms of this License with terms:
- </para>
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>
- Disclaiming warranty or limiting liability differently from the terms
- of sections 15 and 16 of this License; or
- </para>
- </listitem>
- <listitem>
- <para>
- Requiring preservation of specified reasonable legal notices or author
- attributions in that material or in the Appropriate Legal Notices
- displayed by works containing it; or
- </para>
- </listitem>
- <listitem>
- <para>
- Prohibiting misrepresentation of the origin of that material, or
- requiring that modified versions of such material be marked in
- reasonable ways as different from the original version; or
- </para>
- </listitem>
- <listitem>
- <para>
- Limiting the use for publicity purposes of names of licensors or
- authors of the material; or
- </para>
- </listitem>
- <listitem>
- <para>
- Declining to grant rights under trademark law for use of some trade
- names, trademarks, or service marks; or
- </para>
- </listitem>
- <listitem>
- <para>
- Requiring indemnification of licensors and authors of that material by
- anyone who conveys the material (or modified versions of it) with
- contractual assumptions of liability to the recipient, for any
- liability that these contractual assumptions directly impose on those
- licensors and authors.
- </para>
- </listitem>
- </orderedlist>
- <para>
- All other non-permissive additional terms are considered “further
- restrictions” within the meaning of section 10. If the Program as
- you received it, or any part of it, contains a notice stating that it is
- governed by this License along with a term that is a further restriction,
- you may remove that term. If a license document contains a further
- restriction but permits relicensing or conveying under this License, you
- may add to a covered work material governed by the terms of that license
- document, provided that the further restriction does not survive such
- relicensing or conveying.
- </para>
- <para>
- If you add terms to a covered work in accord with this section, you must
- place, in the relevant source files, a statement of the additional terms
- that apply to those files, or a notice indicating where to find the
- applicable terms.
- </para>
- <para>
- Additional terms, permissive or non-permissive, may be stated in the form
- of a separately written license, or stated as exceptions; the above
- requirements apply either way.
- </para>
- <bridgehead renderas="sect1">
- 8. Termination.
- </bridgehead>
- <para>
- You may not propagate or modify a covered work except as expressly provided
- under this License. Any attempt otherwise to propagate or modify it is
- void, and will automatically terminate your rights under this License
- (including any patent licenses granted under the third paragraph of section
- 11).
- </para>
- <para>
- However, if you cease all violation of this License, then your license from
- a particular copyright holder is reinstated (a) provisionally, unless and
- until the copyright holder explicitly and finally terminates your license,
- and (b) permanently, if the copyright holder fails to notify you of the
- violation by some reasonable means prior to 60 days after the cessation.
- </para>
- <para>
- Moreover, your license from a particular copyright holder is reinstated
- permanently if the copyright holder notifies you of the violation by some
- reasonable means, this is the first time you have received notice of
- violation of this License (for any work) from that copyright holder, and
- you cure the violation prior to 30 days after your receipt of the notice.
- </para>
- <para>
- Termination of your rights under this section does not terminate the
- licenses of parties who have received copies or rights from you under this
- License. If your rights have been terminated and not permanently
- reinstated, you do not qualify to receive new licenses for the same
- material under section 10.
- </para>
- <bridgehead renderas="sect1">
- 9. Acceptance Not Required for Having Copies.
- </bridgehead>
- <para>
- You are not required to accept this License in order to receive or run a
- copy of the Program. Ancillary propagation of a covered work occurring
- solely as a consequence of using peer-to-peer transmission to receive a
- copy likewise does not require acceptance. However, nothing other than
- this License grants you permission to propagate or modify any covered work.
- These actions infringe copyright if you do not accept this License.
- Therefore, by modifying or propagating a covered work, you indicate your
- acceptance of this License to do so.
- </para>
- <bridgehead renderas="sect1">
- 10. Automatic Licensing of Downstream Recipients.
- </bridgehead>
- <para>
- Each time you convey a covered work, the recipient automatically receives a
- license from the original licensors, to run, modify and propagate that
- work, subject to this License. You are not responsible for enforcing
- compliance by third parties with this License.
- </para>
- <para>
- An “entity transaction” is a transaction transferring control
- of an organization, or substantially all assets of one, or subdividing an
- organization, or merging organizations. If propagation of a covered work
- results from an entity transaction, each party to that transaction who
- receives a copy of the work also receives whatever licenses to the work the
- party’s predecessor in interest had or could give under the previous
- paragraph, plus a right to possession of the Corresponding Source of the
- work from the predecessor in interest, if the predecessor has it or can get
- it with reasonable efforts.
- </para>
- <para>
- You may not impose any further restrictions on the exercise of the rights
- granted or affirmed under this License. For example, you may not impose a
- license fee, royalty, or other charge for exercise of rights granted under
- this License, and you may not initiate litigation (including a cross-claim
- or counterclaim in a lawsuit) alleging that any patent claim is infringed
- by making, using, selling, offering for sale, or importing the Program or
- any portion of it.
- </para>
- <bridgehead renderas="sect1">
- 11. Patents.
- </bridgehead>
- <para>
- A “contributor” is a copyright holder who authorizes use under
- this License of the Program or a work on which the Program is based. The
- work thus licensed is called the contributor’s “contributor
- version”.
- </para>
- <para>
- A contributor’s “essential patent claims” are all patent
- claims owned or controlled by the contributor, whether already acquired or
- hereafter acquired, that would be infringed by some manner, permitted by
- this License, of making, using, or selling its contributor version, but do
- not include claims that would be infringed only as a consequence of further
- modification of the contributor version. For purposes of this definition,
- “control” includes the right to grant patent sublicenses in a
- manner consistent with the requirements of this License.
- </para>
- <para>
- Each contributor grants you a non-exclusive, worldwide, royalty-free patent
- license under the contributor’s essential patent claims, to make, use,
- sell, offer for sale, import and otherwise run, modify and propagate the
- contents of its contributor version.
- </para>
- <para>
- In the following three paragraphs, a “patent license” is any
- express agreement or commitment, however denominated, not to enforce a
- patent (such as an express permission to practice a patent or covenant not
- to sue for patent infringement). To “grant” such a patent
- license to a party means to make such an agreement or commitment not to
- enforce a patent against the party.
- </para>
- <para>
- If you convey a covered work, knowingly relying on a patent license, and the
- Corresponding Source of the work is not available for anyone to copy, free
- of charge and under the terms of this License, through a publicly available
- network server or other readily accessible means, then you must either (1)
- cause the Corresponding Source to be so available, or (2) arrange to deprive
- yourself of the benefit of the patent license for this particular work, or
- (3) arrange, in a manner consistent with the requirements of this License,
- to extend the patent license to downstream recipients. “Knowingly
- relying” means you have actual knowledge that, but for the patent
- license, your conveying the covered work in a country, or your
- recipient’s use of the covered work in a country, would infringe one
- or more identifiable patents in that country that you have reason to believe
- are valid.
- </para>
- <para>
- If, pursuant to or in connection with a single transaction or arrangement,
- you convey, or propagate by procuring conveyance of, a covered work, and
- grant a patent license to some of the parties receiving the covered work
- authorizing them to use, propagate, modify or convey a specific copy of the
- covered work, then the patent license you grant is automatically extended to
- all recipients of the covered work and works based on it.
- </para>
- <para>
- A patent license is “discriminatory” if it does not include
- within the scope of its coverage, prohibits the exercise of, or is
- conditioned on the non-exercise of one or more of the rights that are
- specifically granted under this License. You may not convey a covered work
- if you are a party to an arrangement with a third party that is in the
- business of distributing software, under which you make payment to the third
- party based on the extent of your activity of conveying the work, and under
- which the third party grants, to any of the parties who would receive the
- covered work from you, a discriminatory patent license (a) in connection
- with copies of the covered work conveyed by you (or copies made from those
- copies), or (b) primarily for and in connection with specific products or
- compilations that contain the covered work, unless you entered into that
- arrangement, or that patent license was granted, prior to 28 March 2007.
- </para>
- <para>
- Nothing in this License shall be construed as excluding or limiting any
- implied license or other defenses to infringement that may otherwise be
- available to you under applicable patent law.
- </para>
- <bridgehead renderas="sect1">
- 12. No Surrender of Others’ Freedom.
- </bridgehead>
- <para>
- If conditions are imposed on you (whether by court order, agreement or
- otherwise) that contradict the conditions of this License, they do not
- excuse you from the conditions of this License. If you cannot convey a
- covered work so as to satisfy simultaneously your obligations under this
- License and any other pertinent obligations, then as a consequence you may
- not convey it at all. For example, if you agree to terms that obligate you
- to collect a royalty for further conveying from those to whom you convey the
- Program, the only way you could satisfy both those terms and this License
- would be to refrain entirely from conveying the Program.
- </para>
- <bridgehead renderas="sect1">
- 13. Use with the <acronym>GNU</acronym> Affero General Public License.
- </bridgehead>
- <para>
- Notwithstanding any other provision of this License, you have permission to
- link or combine any covered work with a work licensed under version 3 of the
- <acronym>GNU</acronym> Affero General Public License into a single combined
- work, and to convey the resulting work. The terms of this License will
- continue to apply to the part which is the covered work, but the special
- requirements of the <acronym>GNU</acronym> Affero General Public License,
- section 13, concerning interaction through a network will apply to the
- combination as such.
- </para>
- <bridgehead renderas="sect1">
- 14. Revised Versions of this License.
- </bridgehead>
- <para>
- The Free Software Foundation may publish revised and/or new versions of the
- <acronym>GNU</acronym> General Public License from time to time. Such new
- versions will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns.
- </para>
- <para>
- Each version is given a distinguishing version number. If the Program
- specifies that a certain numbered version of the <acronym>GNU</acronym>
- General Public License “or any later version” applies to it, you
- have the option of following the terms and conditions either of that
- numbered version or of any later version published by the Free Software
- Foundation. If the Program does not specify a version number of the
- <acronym>GNU</acronym> General Public License, you may choose any version
- ever published by the Free Software Foundation.
- </para>
- <para>
- If the Program specifies that a proxy can decide which future versions of
- the <acronym>GNU</acronym> General Public License can be used, that
- proxy’s public statement of acceptance of a version permanently
- authorizes you to choose that version for the Program.
- </para>
- <para>
- Later license versions may give you additional or different permissions.
- However, no additional obligations are imposed on any author or copyright
- holder as a result of your choosing to follow a later version.
- </para>
- <bridgehead renderas="sect1">
- 15. Disclaimer of Warranty.
- </bridgehead>
- <para>
- THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
- LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
- OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF
- ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
- THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
- YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
- NECESSARY SERVICING, REPAIR OR CORRECTION.
- </para>
- <bridgehead renderas="sect1">
- 16. Limitation of Liability.
- </bridgehead>
- <para>
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
- ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
- PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
- GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE
- OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA
- OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
- PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
- EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGES.
- </para>
- <bridgehead renderas="sect1">
- 17. Interpretation of Sections 15 and 16.
- </bridgehead>
- <para>
- If the disclaimer of warranty and limitation of liability provided above
- cannot be given local legal effect according to their terms, reviewing
- courts shall apply local law that most closely approximates an absolute
- waiver of all civil liability in connection with the Program, unless a
- warranty or assumption of liability accompanies a copy of the Program in
- return for a fee.
- </para>
- <bridgehead>
- END OF TERMS AND CONDITIONS
- </bridgehead>
- <bridgehead renderas="sect1">
- How to Apply These Terms to Your New Programs
- </bridgehead>
- <para>
- If you develop a new program, and you want it to be of the greatest possible
- use to the public, the best way to achieve this is to make it free software
- which everyone can redistribute and change under these terms.
- </para>
- <para>
- To do so, attach the following notices to the program. It is safest to
- attach them to the start of each source file to most effectively state the
- exclusion of warranty; and each file should have at least the
- “copyright” line and a pointer to where the full notice is
- found.
- </para>
- <screen>
-<replaceable>one line to give the program’s name and a brief idea of what it does.</replaceable>
-Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
-
-This program is free software: you can redistribute it and/or modify
-it under the terms of the <acronym>GNU</acronym> General Public License as published by
-the Free Software Foundation, either version 3 of the License, or
-(at your option) any later version.
-
-This program 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. See the
-<acronym>GNU</acronym> General Public License for more details.
-
-You should have received a copy of the <acronym>GNU</acronym> General Public License
-along with this program. If not, see <ulink url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
- </screen>
- <para>
- Also add information on how to contact you by electronic and paper mail.
- </para>
- <para>
- If the program does terminal interaction, make it output a short notice like
- this when it starts in an interactive mode:
- </para>
- <screen>
-<replaceable>program</replaceable> Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
-This program comes with ABSOLUTELY NO WARRANTY; for details type ‘<literal>show w</literal>’.
-This is free software, and you are welcome to redistribute it
-under certain conditions; type ‘<literal>show c</literal>’ for details.
- </screen>
- <para>
- The hypothetical commands ‘<literal>show w</literal>’ and
- ‘<literal>show c</literal>’ should show the appropriate parts of
- the General Public License. Of course, your program’s commands might be
- different; for a GUI interface, you would use an “about box”.
- </para>
- <para>
- You should also get your employer (if you work as a programmer) or school,
- if any, to sign a “copyright disclaimer” for the program, if
- necessary. For more information on this, and how to apply and follow the
- <acronym>GNU</acronym> <acronym>GPL</acronym>, see <ulink
- url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
- </para>
- <para>
- The <acronym>GNU</acronym> General Public License does not permit
- incorporating your program into proprietary programs. If your program is a
- subroutine library, you may consider it more useful to permit linking
- proprietary applications with the library. If this is what you want to do,
- use the <acronym>GNU</acronym> Lesser General Public License instead of this
- License. But first, please read <ulink
- url="http://www.gnu.org/philosophy/why-not-lgpl.html">http://www.gnu.org/philosophy/why-not-lgpl.html</ulink>.
- </para>
-</appendix>
+++ /dev/null
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<appendix>
- <appendixinfo>
- <title>GNU General Public License</title>
- <pubdate>Version 2, June 1991</pubdate>
- <copyright>
- <year>1989, 1991</year>
- <holder>Free Software Foundation, Inc.</holder>
- </copyright>
- <legalnotice>
- <para>
- <address>Free Software Foundation, Inc.
- <street>59 Temple Place, Suite 330</street>,
- <city>Boston</city>,
- <state>MA</state>
- <postcode>02111-1307</postcode>
- <country>USA</country>
- </address>.
- </para>
- <para> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
- </para>
- </legalnotice>
- <releaseinfo> Version 2, June 1991</releaseinfo>
- </appendixinfo>
- <title>GNU General Public License</title>
- <sect1>
- <title>Preamble</title>
- <para> The licenses for most software are designed to take away your
- freedom to share and change it. By contrast, the GNU General Public License is
- intended to guarantee your freedom to share and change
- free software - to make sure the software is free for all its users.
- This General Public License applies to most of the Free Software
- Foundation's software and to any other program whose authors commit
- to using it. (Some other Free Software Foundation software is covered
- by the GNU Library General Public License instead.) You can apply it
- to your programs, too.
- </para>
- <para> When we speak of free software, we are referring to freedom, not price.
- Our General Public Licenses are designed to make sure that you have the
- freedom to distribute copies of free software (and charge for this
- service if you wish), that you receive source code or can get it if you
- want it, that you can change the software or use pieces of it in new free
- programs; and that you know you can do these things.
- </para>
- <para> To protect your rights, we need to make restrictions that forbid anyone
- to deny you these rights or to ask you to surrender the rights. These
- restrictions translate to certain responsibilities for you if you distribute
- copies of the software, or if you modify it.
- </para>
- <para> For example, if you distribute copies of such a program, whether gratis or
- for a fee, you must give the recipients all the rights that you have. You
- must make sure that they, too, receive or can get the source code. And you
- must show them these terms so they know their rights.
- </para>
- <para> We protect your rights with two steps:
- <orderedlist>
- <listitem>
- <para> copyright the software, and
- </para>
- </listitem>
- <listitem>
- <para> offer you this license which gives you legal permission to copy,
- distribute and/or modify the software.
- </para>
- </listitem>
- </orderedlist>
- </para>
- <para> Also, for each author's protection and ours, we want to make certain that
- everyone understands that there is no warranty for this free software. If
- the software is modified by someone else and passed on, we want its
- recipients to know that what they have is not the original, so that any
- problems introduced by others will not reflect on the original authors'
- reputations.
- </para>
- <para> Finally, any free program is threatened constantly by software patents.
- We wish to avoid the danger that redistributors of a free program will
- individually obtain patent licenses, in effect making the program
- proprietary. To prevent this, we have made it clear that any patent must be
- licensed for everyone's free use or not licensed at all.
- </para>
- <para> The precise terms and conditions for copying, distribution and modification
- follow.
- </para>
- </sect1>
- <sect1>
- <title>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</title>
- <sect2>
- <title>Section 0</title>
- <para> This License applies to any program or other work which contains a notice
- placed by the copyright holder saying it may be distributed under the terms
- of this General Public License. The "Program", below, refers to any such
- program or work, and a
- <quote>work based on the Program
- </quote> means either
- the Program or any derivative work under copyright law: that is to say, a
- work containing the Program or a portion of it, either verbatim or with
- modifications and/or translated into another language. (Hereinafter, translation
- is included without limitation in the term
- <quote>modification
- </quote>.) Each licensee is addressed as <quote>you</quote>.
- </para>
- <para> Activities other than copying, distribution and modification are not covered by
- this License; they are outside its scope. The act of running the Program is not
- restricted, and the output from the Program is covered only if its contents
- constitute a work based on the Program (independent of having been made by running
- the Program). Whether that is true depends on what the Program does.
- </para>
- </sect2>
- <sect2 id="sect1">
- <title>Section 1</title>
- <para> You may copy and distribute verbatim copies of the Program's source code as you
- receive it, in any medium, provided that you conspicuously and appropriately
- publish on each copy an appropriate copyright notice and disclaimer of warranty;
- keep intact all the notices that refer to this License and to the absence of any
- warranty; and give any other recipients of the Program a copy of this License
- along with the Program.
- </para>
- <para> You may charge a fee for the physical act of transferring a copy, and you may at
- your option offer warranty protection in exchange for a fee.
- </para>
- </sect2>
- <sect2 id="sect2">
- <title>Section 2</title>
- <para> You may modify your copy or copies of the Program or any portion of it, thus
- forming a work based on the Program, and copy and distribute such modifications
- or work under the terms of
- <link linkend="sect1">Section 1
- </link> above, provided
- that you also meet all of these conditions:
- <orderedlist>
- <listitem>
- <para> You must cause the modified files to carry prominent notices stating that
- you changed the files and the date of any change.
- </para>
- </listitem>
- <listitem>
- <para> You must cause any work that you distribute or publish, that in whole or
- in part contains or is derived from the Program or any part thereof, to be
- licensed as a whole at no charge to all third parties under the terms of
- this License.
- </para>
- </listitem>
- <listitem>
- <para> If the modified program normally reads commands interactively when run, you
- must cause it, when started running for such interactive use in the most
- ordinary way, to print or display an announcement including an appropriate
- copyright notice and a notice that there is no warranty (or else, saying
- that you provide a warranty) and that users may redistribute the program
- under these conditions, and telling the user how to view a copy of this
- License.
- <note>
- <title>Exception:
- </title>
- <para> If the Program itself is interactive but does not normally print such an
- announcement, your work based on the Program is not required to print an
- announcement.)
- </para>
- </note>
- </para>
- </listitem>
- </orderedlist>
- </para>
- <para> These requirements apply to the modified work as a whole. If identifiable sections
- of that work are not derived from the Program, and can be reasonably considered
- independent and separate works in themselves, then this License, and its terms,
- do not apply to those sections when you distribute them as separate works. But when
- you distribute the same sections as part of a whole which is a work based on the
- Program, the distribution of the whole must be on the terms of this License, whose
- permissions for other licensees extend to the entire whole, and thus to each and
- every part regardless of who wrote it.
- </para>
- <para> Thus, it is not the intent of this section to claim rights or contest your rights
- to work written entirely by you; rather, the intent is to exercise the right to control
- the distribution of derivative or collective works based on the Program.
- </para>
- <para> In addition, mere aggregation of another work not based on the Program with the Program
- (or with a work based on the Program) on a volume of a storage or distribution medium
- does not bring the other work under the scope of this License.
- </para>
- </sect2>
- <sect2>
- <title>Section 3
- </title>
- <para> You may copy and distribute the Program (or a work based on it, under
- <link linkend="sect2">Section 2
- </link> in object code or executable form under the terms of
- <link linkend="sect1">Sections 1
- </link> and
- <link linkend="sect2">2
- </link> above provided that you also do one of the following:
- <orderedlist>
- <listitem>
- <para> Accompany it with the complete corresponding machine-readable source code, which
- must be distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
- </para>
- </listitem>
- <listitem>
- <para> Accompany it with a written offer, valid for at least three years, to give any
- third party, for a charge no more than your cost of physically performing source
- distribution, a complete machine-readable copy of the corresponding source code,
- to be distributed under the terms of Sections 1 and 2 above on a medium customarily
- used for software interchange; or,
- </para>
- </listitem>
- <listitem>
- <para> Accompany it with the information you received as to the offer to distribute
- corresponding source code. (This alternative is allowed only for noncommercial
- distribution and only if you received the program in object code or executable form
- with such an offer, in accord with Subsection b above.)
- </para>
- </listitem>
- </orderedlist>
- </para>
- <para> The source code for a work means the preferred form of the work for making modifications
- to it. For an executable work, complete source code means all the source code for all modules
- it contains, plus any associated interface definition files, plus the scripts used to control
- compilation and installation of the executable. However, as a special exception, the source
- code distributed need not include anything that is normally distributed (in either source or
- binary form) with the major components (compiler, kernel, and so on) of the operating system
- on which the executable runs, unless that component itself accompanies the executable.
- </para>
- <para> If distribution of executable or object code is made by offering access to copy from a
- designated place, then offering equivalent access to copy the source code from the same place
- counts as distribution of the source code, even though third parties are not compelled to
- copy the source along with the object code.
- </para>
- </sect2>
- <sect2>
- <title>Section 4
- </title>
- <para> You may not copy, modify, sublicense, or distribute the Program except as expressly provided
- under this License. Any attempt otherwise to copy, modify, sublicense or distribute the
- Program is void, and will automatically terminate your rights under this License. However,
- parties who have received copies, or rights, from you under this License will not have their
- licenses terminated so long as such parties remain in full compliance.
- </para>
- </sect2>
- <sect2>
- <title>Section 5
- </title>
- <para> You are not required to accept this License, since you have not signed it. However, nothing
- else grants you permission to modify or distribute the Program or its derivative works.
- These actions are prohibited by law if you do not accept this License. Therefore, by modifying
- or distributing the Program (or any work based on the Program), you indicate your acceptance
- of this License to do so, and all its terms and conditions for copying, distributing or
- modifying the Program or works based on it.
- </para>
- </sect2>
- <sect2>
- <title>Section 6
- </title>
- <para> Each time you redistribute the Program (or any work based on the Program), the recipient
- automatically receives a license from the original licensor to copy, distribute or modify
- the Program subject to these terms and conditions. You may not impose any further restrictions
- on the recipients' exercise of the rights granted herein. You are not responsible for enforcing
- compliance by third parties to this License.
- </para>
- </sect2>
- <sect2>
- <title>Section 7
- </title>
- <para> If, as a consequence of a court judgment or allegation of patent infringement or for any other
- reason (not limited to patent issues), conditions are imposed on you (whether by court order,
- agreement or otherwise) that contradict the conditions of this License, they do not excuse you
- from the conditions of this License. If you cannot distribute so as to satisfy simultaneously
- your obligations under this License and any other pertinent obligations, then as a consequence
- you may not distribute the Program at all. For example, if a patent license would not permit
- royalty-free redistribution of the Program by all those who receive copies directly or
- indirectly through you, then the only way you could satisfy both it and this License would be
- to refrain entirely from distribution of the Program.
- </para>
- <para> If any portion of this section is held invalid or unenforceable under any particular circumstance,
- the balance of the section is intended to apply and the section as a whole is intended to apply
- in other circumstances.
- </para>
- <para> It is not the purpose of this section to induce you to infringe any patents or other property
- right claims or to contest validity of any such claims; this section has the sole purpose of
- protecting the integrity of the free software distribution system, which is implemented by public
- license practices. Many people have made generous contributions to the wide range of software
- distributed through that system in reliance on consistent application of that system; it is up
- to the author/donor to decide if he or she is willing to distribute software through any other
- system and a licensee cannot impose that choice.
- </para>
- <para> This section is intended to make thoroughly clear what is believed to be a consequence of the
- rest of this License.
- </para>
- </sect2>
- <sect2>
- <title>Section 8
- </title>
- <para> If the distribution and/or use of the Program is restricted in certain countries either by patents
- or by copyrighted interfaces, the original copyright holder who places the Program under this License
- may add an explicit geographical distribution limitation excluding those countries, so that
- distribution is permitted only in or among countries not thus excluded. In such case, this License
- incorporates the limitation as if written in the body of this License.
- </para>
- </sect2>
- <sect2>
- <title>Section 9
- </title>
- <para> The Free Software Foundation may publish revised and/or new versions of the General Public License
- from time to time. Such new versions will be similar in spirit to the present version, but may differ
- in detail to address new problems or concerns.
- </para>
- <para> Each version is given a distinguishing version number. If the Program specifies a version number of
- this License which applies to it and "any later version", you have the option of following the terms
- and conditions either of that version or of any later version published by the Free Software
- Foundation. If the Program does not specify a version number of this License, you may choose any
- version ever published by the Free Software Foundation.
- </para>
- </sect2>
- <sect2>
- <title>Section 10
- </title>
- <para> If you wish to incorporate parts of the Program into other free programs whose distribution
- conditions are different, write to the author to ask for permission. For software which is copyrighted
- by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
- for this. Our decision will be guided by the two goals of preserving the free status of all
- derivatives of our free software and of promoting the sharing and reuse of software generally.
- </para>
- </sect2>
- <sect2>
-<title>NO WARRANTY Section 11
- </title>
- <para> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
- PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
- OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
- INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
- PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
- </para>
- </sect2>
- <sect2>
- <title>Section 12
- </title>
- <para> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR
- ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
- FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
- USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
- INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
- ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
- DAMAGES.
- </para>
- <para>END OF TERMS AND CONDITIONS
- </para>
- </sect2>
- </sect1>
- <sect1>
- <title>How to Apply These Terms to Your New Programs
- </title>
- <para>
- If you develop a new program, and you want it to be of the greatest
- possible use to the public, the best way to achieve this is to make it
- free software which everyone can redistribute and change under these terms.
- </para>
- <para>
- To do so, attach the following notices to the program. It is safest
- to attach them to the start of each source file to most effectively
- convey the exclusion of warranty; and each file should have at least
- the "copyright" line and a pointer to where the full notice is found.
- </para>
- <para>
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
- </para>
- <para>
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
- </para>
- <para>
- This program 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. See the
- GNU General Public License for more details.
- </para>
- <para>
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
- </para>
- <para>
- Also add information on how to contact you by electronic and paper mail.
- </para>
- <para>
- If the program is interactive, make it output a short notice like this
- when it starts in an interactive mode:
- </para>
- <para>
- Gnomovision version 69, Copyright (C) year name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
- </para>
- <para>
- The hypothetical commands `show w' and `show c' should show the appropriate
- parts of the General Public License. Of course, the commands you use may
- be called something other than `show w' and `show c'; they could even be
- mouse-clicks or menu items--whatever suits your program.
- </para>
- <para>
- You should also get your employer (if you work as a programmer) or your
- school, if any, to sign a "copyright disclaimer" for the program, if
- necessary. Here is a sample; alter the names:
- </para>
- <para>
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
- </para>
- <para>
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
- </para>
- <para>
- This General Public License does not permit incorporating your program into
- proprietary programs. If your program is a subroutine library, you may
- consider it more useful to permit linking proprietary applications with the
- library. If this is what you want to do, use the GNU Library General
- Public License instead of this License.
- </para>
- </sect1>
- </appendix>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="12.034cm"
- height="10.095cm"
- viewBox="1.1 0.162 13.134 10.258"
- id="svg2">
- <defs
- id="defs439" />
- <text
- x="4.2160001"
- y="1.6"
- id="text4"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Workgroup: BILLMORE</text>
- <rect
- width="1.5"
- height="3"
- x="1.15"
- y="4.6500001"
- id="rect6"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.5"
- height="3"
- x="1.15"
- y="4.6500001"
- id="rect8"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.5"
- height="3"
- x="1.15"
- y="4.6500001"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.2"
- height="1.2"
- x="1.3"
- y="4.8000002"
- id="rect12"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.2"
- height="1.2"
- x="1.3"
- y="4.8000002"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.2"
- height="1.2"
- x="1.3"
- y="4.8000002"
- id="rect16"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.5"
- y1="5.0999999"
- x2="1.3"
- y2="5.0999999"
- stroke="#000000"
- stroke-width="0.010"
- id="line18"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.3"
- y1="5.4000001"
- x2="2.5"
- y2="5.4000001"
- stroke="#000000"
- stroke-width="0.010"
- id="line20"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.5"
- y1="5.625"
- x2="1.3"
- y2="5.625"
- stroke="#000000"
- stroke-width="0.010"
- id="line22"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="1.3"
- y="6.1500001"
- id="rect24"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="1.3"
- y="6.1500001"
- id="rect26"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="1.3"
- y="6.1500001"
- id="rect28"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.15"
- y1="6.6750002"
- x2="2.6500001"
- y2="6.6750002"
- stroke="#000000"
- stroke-width="0.010"
- id="line30"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="1.825"
- y="6.8249998"
- id="rect32"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="1.825"
- y="6.8249998"
- id="rect34"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="1.825"
- y="6.8249998"
- id="rect36"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="2.125"
- y="6.8249998"
- id="rect38"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="2.125"
- y="6.8249998"
- id="rect40"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="2.125"
- y="6.8249998"
- id="rect42"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="2.425"
- y="6.8249998"
- id="rect44"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="2.425"
- y="6.8249998"
- id="rect46"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="2.425"
- y="6.8249998"
- id="rect48"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="2.3499999"
- y="6.375"
- id="rect50"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="2.3499999"
- y="6.375"
- id="rect52"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="2.3499999"
- y="6.375"
- id="rect54"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.3"
- y1="6.375"
- x2="2.125"
- y2="6.375"
- stroke="#000000"
- stroke-width="0.010"
- id="line56"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="1.3"
- y="6.75"
- id="rect58"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="1.3"
- y="6.75"
- id="rect60"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="1.3"
- y="6.75"
- id="rect62"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.05"
- height="0.075000003"
- x="1.375"
- y="5.6999998"
- id="rect64"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.05"
- height="0.075000003"
- x="1.375"
- y="5.6999998"
- id="rect66"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.05"
- height="0.075000003"
- x="1.375"
- y="5.6999998"
- id="rect68"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.375"
- y1="6.2249999"
- x2="2.05"
- y2="6.2249999"
- stroke="#000000"
- stroke-width="0.010"
- id="line70"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.05"
- y1="6.3000002"
- x2="1.975"
- y2="6.3000002"
- stroke="#000000"
- stroke-width="0.010"
- id="line72"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.375"
- y1="6.3000002"
- x2="1.45"
- y2="6.3000002"
- stroke="#000000"
- stroke-width="0.010"
- id="line74"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.375"
- height="0.075000003"
- x="1.525"
- y="6.2249999"
- id="rect76"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.375"
- height="0.075000003"
- x="1.525"
- y="6.2249999"
- id="rect78"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.375"
- height="0.075000003"
- x="1.525"
- y="6.2249999"
- id="rect80"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.375"
- y1="5.8499999"
- x2="1.45"
- y2="5.8499999"
- stroke="#000000"
- stroke-width="0.010"
- id="line82"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.525"
- y1="5.8499999"
- x2="1.6"
- y2="5.8499999"
- stroke="#000000"
- stroke-width="0.010"
- id="line84"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.2750001"
- y1="5.8499999"
- x2="2.425"
- y2="5.8499999"
- stroke="#000000"
- stroke-width="0.010"
- id="line86"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.575"
- y1="7.5749998"
- x2="1.225"
- y2="7.5749998"
- stroke="#000000"
- stroke-width="0.010"
- id="line88"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.225"
- y1="7.5"
- x2="2.575"
- y2="7.5"
- stroke="#000000"
- stroke-width="0.010"
- id="line90"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.575"
- y1="7.4250002"
- x2="1.225"
- y2="7.4250002"
- stroke="#000000"
- stroke-width="0.010"
- id="line92"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.225"
- y1="7.3499999"
- x2="2.575"
- y2="7.3499999"
- stroke="#000000"
- stroke-width="0.010"
- id="line94"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.575"
- y1="7.2750001"
- x2="1.225"
- y2="7.2750001"
- stroke="#000000"
- stroke-width="0.010"
- id="line96"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.225"
- y1="7.1999998"
- x2="2.575"
- y2="7.1999998"
- stroke="#000000"
- stroke-width="0.010"
- id="line98"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.575"
- y1="7.125"
- x2="1.225"
- y2="7.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line100"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3329999"
- height="4"
- x="3.733"
- y="3.688"
- id="rect102"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.3329999"
- height="4"
- x="3.733"
- y="3.688"
- id="rect104"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.3329999"
- height="4"
- x="3.733"
- y="3.688"
- id="rect106"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.067"
- height="1.6"
- x="3.8670001"
- y="3.8210001"
- id="rect108"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.067"
- height="1.6"
- x="3.8670001"
- y="3.8210001"
- id="rect110"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.067"
- height="1.6"
- x="3.8670001"
- y="3.8210001"
- id="rect112"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8670001"
- y1="4.0879998"
- x2="4.9330001"
- y2="4.0879998"
- stroke="#000000"
- stroke-width="0.010"
- id="line114"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.9330001"
- y1="4.3540001"
- x2="3.8670001"
- y2="4.3540001"
- stroke="#000000"
- stroke-width="0.010"
- id="line116"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8670001"
- y1="4.6209998"
- x2="4.9330001"
- y2="4.6209998"
- stroke="#000000"
- stroke-width="0.010"
- id="line118"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8670001"
- y1="4.888"
- x2="4.9330001"
- y2="4.888"
- stroke="#000000"
- stroke-width="0.010"
- id="line120"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.9330001"
- y1="5.1539998"
- x2="3.8670001"
- y2="5.1539998"
- stroke="#000000"
- stroke-width="0.010"
- id="line122"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.73299998"
- height="0.40000001"
- x="3.8670001"
- y="5.5539999"
- id="rect124"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.73299998"
- height="0.40000001"
- x="3.8670001"
- y="5.5539999"
- id="rect126"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.73299998"
- height="0.40000001"
- x="3.8670001"
- y="5.5539999"
- id="rect128"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.733"
- y1="6.2210002"
- x2="5.0669999"
- y2="6.2210002"
- stroke="#000000"
- stroke-width="0.010"
- id="line130"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.3330002"
- y="6.3540001"
- id="rect132"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.3330002"
- y="6.3540001"
- id="rect134"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.3330002"
- y="6.3540001"
- id="rect136"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.5999999"
- y="6.3540001"
- id="rect138"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.5999999"
- y="6.3540001"
- id="rect140"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.5999999"
- y="6.3540001"
- id="rect142"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.8670001"
- y="6.3540001"
- id="rect144"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.8670001"
- y="6.3540001"
- id="rect146"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.067000002"
- height="0.067000002"
- x="4.8670001"
- y="6.3540001"
- id="rect148"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.133"
- height="0.133"
- x="4.8000002"
- y="5.954"
- id="rect150"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.133"
- height="0.133"
- x="4.8000002"
- y="5.954"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.133"
- height="0.133"
- x="4.8000002"
- y="5.954"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8670001"
- y1="5.7540002"
- x2="4.5999999"
- y2="5.7540002"
- stroke="#000000"
- stroke-width="0.010"
- id="line156"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.2"
- height="0.2"
- x="3.8670001"
- y="6.2870002"
- id="rect158"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.2"
- height="0.2"
- x="3.8670001"
- y="6.2870002"
- id="rect160"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.2"
- height="0.2"
- x="3.8670001"
- y="6.2870002"
- id="rect162"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.93300003"
- height="0.067000002"
- x="3.9330001"
- y="5.2210002"
- id="rect164"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.93300003"
- height="0.067000002"
- x="3.9330001"
- y="5.2210002"
- id="rect166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.93300003"
- height="0.067000002"
- x="3.9330001"
- y="5.2210002"
- id="rect168"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.9330001"
- y1="5.6209998"
- x2="4.533"
- y2="5.6209998"
- stroke="#000000"
- stroke-width="0.010"
- id="line170"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.533"
- y1="5.6880002"
- x2="4.467"
- y2="5.6880002"
- stroke="#000000"
- stroke-width="0.010"
- id="line172"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.9330001"
- y1="5.6880002"
- x2="4"
- y2="5.6880002"
- stroke="#000000"
- stroke-width="0.010"
- id="line174"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.333"
- height="0.067000002"
- x="4.0669999"
- y="5.6209998"
- id="rect176"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.333"
- height="0.067000002"
- x="4.0669999"
- y="5.6209998"
- id="rect178"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.333"
- height="0.067000002"
- x="4.0669999"
- y="5.6209998"
- id="rect180"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.9330001"
- y1="5.3540001"
- x2="4"
- y2="5.3540001"
- stroke="#000000"
- stroke-width="0.010"
- id="line182"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.0669999"
- y1="5.3540001"
- x2="4.1329999"
- y2="5.3540001"
- stroke="#000000"
- stroke-width="0.010"
- id="line184"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.7329998"
- y1="5.3540001"
- x2="4.8670001"
- y2="5.3540001"
- stroke="#000000"
- stroke-width="0.010"
- id="line186"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8"
- y1="7.6209998"
- x2="5"
- y2="7.6209998"
- stroke="#000000"
- stroke-width="0.010"
- id="line188"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5"
- y1="7.5539999"
- x2="3.8"
- y2="7.5539999"
- stroke="#000000"
- stroke-width="0.010"
- id="line190"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8"
- y1="7.487"
- x2="5"
- y2="7.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line192"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5"
- y1="7.421"
- x2="3.8"
- y2="7.421"
- stroke="#000000"
- stroke-width="0.010"
- id="line194"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8"
- y1="7.3540001"
- x2="5"
- y2="7.3540001"
- stroke="#000000"
- stroke-width="0.010"
- id="line196"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5"
- y1="7.2870002"
- x2="3.8"
- y2="7.2870002"
- stroke="#000000"
- stroke-width="0.010"
- id="line198"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8"
- y1="7.2210002"
- x2="5"
- y2="7.2210002"
- stroke="#000000"
- stroke-width="0.010"
- id="line200"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5"
- y1="7.1539998"
- x2="3.8"
- y2="7.1539998"
- stroke="#000000"
- stroke-width="0.010"
- id="line202"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8"
- y1="7.0879998"
- x2="5"
- y2="7.0879998"
- stroke="#000000"
- stroke-width="0.010"
- id="line204"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5"
- y1="7.0209999"
- x2="3.8"
- y2="7.0209999"
- stroke="#000000"
- stroke-width="0.010"
- id="line206"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8"
- y1="6.954"
- x2="5"
- y2="6.954"
- stroke="#000000"
- stroke-width="0.010"
- id="line208"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5"
- y1="6.888"
- x2="3.8"
- y2="6.888"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8"
- y1="6.8210001"
- x2="5"
- y2="6.8210001"
- stroke="#000000"
- stroke-width="0.010"
- id="line212"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5"
- y1="6.7540002"
- x2="3.8"
- y2="6.7540002"
- stroke="#000000"
- stroke-width="0.010"
- id="line214"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="4"
- height="1.3329999"
- x="5.9749999"
- y="6.3330002"
- id="rect216"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="4"
- height="1.3329999"
- x="5.9749999"
- y="6.3330002"
- id="rect218"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="4"
- height="1.3329999"
- x="5.9749999"
- y="6.3330002"
- id="rect220"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.524"
- height="0.76200002"
- x="8.3559999"
- y="6.7140002"
- id="rect222"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.524"
- height="0.76200002"
- x="8.3559999"
- y="6.7140002"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.524"
- height="0.76200002"
- x="8.3559999"
- y="6.7140002"
- id="rect226"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.8800001"
- y1="7.0949998"
- x2="8.3559999"
- y2="7.0949998"
- stroke="#000000"
- stroke-width="0.010"
- id="line228"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="1.048"
- x="7.9749999"
- y="6.4289999"
- id="rect230"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="1.048"
- x="7.9749999"
- y="6.4289999"
- id="rect232"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="1.048"
- x="7.9749999"
- y="6.4289999"
- id="rect234"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="6.927"
- y="6.5240002"
- id="rect236"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="6.927"
- y="6.5240002"
- id="rect238"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="6.927"
- y="6.5240002"
- id="rect240"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="7.118"
- y="6.5240002"
- id="rect242"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="7.118"
- y="6.5240002"
- id="rect244"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="7.118"
- y="6.5240002"
- id="rect246"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="7.3080001"
- y="6.5240002"
- id="rect248"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="7.3080001"
- y="6.5240002"
- id="rect250"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.094999999"
- height="0.094999999"
- x="7.3080001"
- y="6.5240002"
- id="rect252"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.19"
- height="0.19"
- x="7.5939999"
- y="6.4289999"
- id="rect254"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.19"
- height="0.19"
- x="7.5939999"
- y="6.4289999"
- id="rect256"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.19"
- height="0.19"
- x="7.5939999"
- y="6.4289999"
- id="rect258"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.28600001"
- x="6.165"
- y="6.4289999"
- id="rect260"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.28600001"
- x="6.165"
- y="6.4289999"
- id="rect262"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.28600001"
- x="6.165"
- y="6.4289999"
- id="rect264"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3329999"
- height="0.094999999"
- x="8.4510002"
- y="7.1900001"
- id="rect266"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.3329999"
- height="0.094999999"
- x="8.4510002"
- y="7.1900001"
- id="rect268"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.3329999"
- height="0.094999999"
- x="8.4510002"
- y="7.1900001"
- id="rect270"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.0699997"
- y1="6.5240002"
- x2="8.0699997"
- y2="7.381"
- stroke="#000000"
- stroke-width="0.010"
- id="line272"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.094999999"
- height="0.47600001"
- x="8.0699997"
- y="6.7140002"
- id="rect274"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.094999999"
- height="0.47600001"
- x="8.0699997"
- y="6.7140002"
- id="rect276"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.094999999"
- height="0.47600001"
- x="8.0699997"
- y="6.7140002"
- id="rect278"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.5939999"
- y1="7.381"
- x2="9.7849998"
- y2="7.381"
- stroke="#000000"
- stroke-width="0.010"
- id="line280"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.0700002"
- y1="7"
- x2="7.7849998"
- y2="7"
- stroke="#000000"
- stroke-width="0.010"
- id="line282"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.7849998"
- y1="7.0949998"
- x2="6.0700002"
- y2="7.0949998"
- stroke="#000000"
- stroke-width="0.010"
- id="line284"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.0700002"
- y1="7.1900001"
- x2="7.7849998"
- y2="7.1900001"
- stroke="#000000"
- stroke-width="0.010"
- id="line286"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.7849998"
- y1="7.4759998"
- x2="6.0700002"
- y2="7.4759998"
- stroke="#000000"
- stroke-width="0.010"
- id="line288"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.0700002"
- y1="7.381"
- x2="7.7849998"
- y2="7.381"
- stroke="#000000"
- stroke-width="0.010"
- id="line290"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.7849998"
- y1="7.2859998"
- x2="6.0700002"
- y2="7.2859998"
- stroke="#000000"
- stroke-width="0.010"
- id="line292"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.4510002"
- y1="7.381"
- x2="8.5459995"
- y2="7.381"
- stroke="#000000"
- stroke-width="0.010"
- id="line294"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6420002"
- y1="7.381"
- x2="8.7370005"
- y2="7.381"
- stroke="#000000"
- stroke-width="0.010"
- id="line296"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.165"
- y1="7.381"
- x2="8.165"
- y2="7.2859998"
- stroke="#000000"
- stroke-width="0.010"
- id="line298"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.165"
- y1="6.619"
- x2="8.165"
- y2="6.5240002"
- stroke="#000000"
- stroke-width="0.010"
- id="line300"
- style="stroke:#000000;stroke-width:0.01" />
- <polygon
- points="11.127,6.517 11.039,6.554 10.775,7.214 10.775,7.544 10.907,7.654 12.843,7.654 12.975,7.544 12.975,7.214 12.711,6.554 12.623,6.517 11.127,6.517 "
- id="polygon302"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="11.127,6.517 11.039,6.554 10.775,7.214 10.775,7.544 10.907,7.654 12.843,7.654 12.975,7.544 12.975,7.214 12.711,6.554 12.623,6.517 11.127,6.517 "
- id="polygon304"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 10.819,7.104 L 10.907,7.141 L 12.843,7.141 L 12.931,7.104"
- id="path306"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 12.843,7.141 L 12.975,7.214"
- id="path308"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 10.775,7.214 L 10.907,7.141"
- id="path310"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="11.391,5.821 11.347,6.701 12.403,6.701 12.359,5.821 11.391,5.821 "
- id="polygon312"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="11.391,5.821 11.347,6.701 12.403,6.701 12.359,5.821 11.391,5.821 "
- id="polygon314"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="11.215,6.701 11.127,6.957 12.623,6.957 12.535,6.701 11.215,6.701 "
- id="polygon316"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="11.215,6.701 11.127,6.957 12.623,6.957 12.535,6.701 11.215,6.701 "
- id="polygon318"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="11.215"
- cy="7.2690001"
- rx="0.022"
- ry="0.022"
- id="ellipse320"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.215"
- cy="7.2690001"
- rx="0.022"
- ry="0.022"
- id="ellipse322"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.435"
- cy="7.2690001"
- rx="0.022"
- ry="0.022"
- id="ellipse324"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.435"
- cy="7.2690001"
- rx="0.022"
- ry="0.022"
- id="ellipse326"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.655"
- cy="7.2690001"
- rx="0.022"
- ry="0.022"
- id="ellipse328"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.655"
- cy="7.2690001"
- rx="0.022"
- ry="0.022"
- id="ellipse330"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.215"
- cy="7.3610001"
- rx="0.022"
- ry="0.022"
- id="ellipse332"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.215"
- cy="7.3610001"
- rx="0.022"
- ry="0.022"
- id="ellipse334"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.435"
- cy="7.3610001"
- rx="0.022"
- ry="0.022"
- id="ellipse336"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.435"
- cy="7.3610001"
- rx="0.022"
- ry="0.022"
- id="ellipse338"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.655"
- cy="7.3610001"
- rx="0.022"
- ry="0.022"
- id="ellipse340"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.655"
- cy="7.3610001"
- rx="0.022"
- ry="0.022"
- id="ellipse342"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.215"
- cy="7.4520001"
- rx="0.022"
- ry="0.022"
- id="ellipse344"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.215"
- cy="7.4520001"
- rx="0.022"
- ry="0.022"
- id="ellipse346"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.435"
- cy="7.4520001"
- rx="0.022"
- ry="0.022"
- id="ellipse348"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.435"
- cy="7.4520001"
- rx="0.022"
- ry="0.022"
- id="ellipse350"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.655"
- cy="7.4520001"
- rx="0.022"
- ry="0.022"
- id="ellipse352"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.655"
- cy="7.4520001"
- rx="0.022"
- ry="0.022"
- id="ellipse354"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.215"
- cy="7.5440001"
- rx="0.022"
- ry="0.022"
- id="ellipse356"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.215"
- cy="7.5440001"
- rx="0.022"
- ry="0.022"
- id="ellipse358"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.435"
- cy="7.5440001"
- rx="0.022"
- ry="0.022"
- id="ellipse360"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.435"
- cy="7.5440001"
- rx="0.022"
- ry="0.022"
- id="ellipse362"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.655"
- cy="7.5440001"
- rx="0.022"
- ry="0.022"
- id="ellipse364"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="11.655"
- cy="7.5440001"
- rx="0.022"
- ry="0.022"
- id="ellipse366"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="11.875"
- cy="7.2870002"
- rx="0.27500001"
- ry="0.088"
- id="ellipse368"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="11.875"
- cy="7.2870002"
- rx="0.27500001"
- ry="0.088"
- id="ellipse370"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="12.425"
- cy="7.2870002"
- rx="0.27500001"
- ry="0.088"
- id="ellipse372"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="12.425"
- cy="7.2870002"
- rx="0.27500001"
- ry="0.088"
- id="ellipse374"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="2"
- height="1.6670001"
- x="6.9250002"
- y="4.237"
- id="rect376"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2"
- height="1.6670001"
- x="6.9250002"
- y="4.237"
- id="rect378"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2"
- height="1.6670001"
- x="6.9250002"
- y="4.237"
- id="rect380"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.778"
- height="1.3329999"
- x="7.0359998"
- y="4.349"
- id="rect382"
- style="fill:#a1a1a1;stroke:none;stroke-width:0" />
- <rect
- width="1.778"
- height="1.3329999"
- x="7.0359998"
- y="4.349"
- id="rect384"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.778"
- height="1.3329999"
- x="7.0359998"
- y="4.349"
- id="rect386"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="7.258,5.904 8.592,5.904 8.258,6.015 7.592,6.015 7.258,5.904 "
- id="polygon388"
- style="fill:#d9d9cd;stroke:none;stroke-width:0.1" />
- <polygon
- points="7.258,5.904 8.592,5.904 8.258,6.015 7.592,6.015 7.258,5.904 "
- id="polygon390"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.258,5.904 8.592,5.904 8.258,6.015 7.592,6.015 7.258,5.904 "
- id="polygon392"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.667"
- height="0.111"
- x="7.592"
- y="6.0149999"
- id="rect394"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.667"
- height="0.111"
- x="7.592"
- y="6.0149999"
- id="rect396"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.667"
- height="0.111"
- x="7.592"
- y="6.0149999"
- id="rect398"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3329999"
- height="0.111"
- x="7.2579999"
- y="6.1259999"
- id="rect400"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.3329999"
- height="0.111"
- x="7.2579999"
- y="6.1259999"
- id="rect402"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.3329999"
- height="0.111"
- x="7.2579999"
- y="6.1259999"
- id="rect404"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="1.863,7.675 1.863,9.350 12.012,9.350 12.012,7.662 "
- id="polyline406"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="4.4000001"
- y1="7.6880002"
- x2="4.4120002"
- y2="9.3380003"
- stroke="#000000"
- stroke-width="0.100"
- id="line408"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="7.9749999"
- y1="7.6669998"
- x2="7.987"
- y2="9.3249998"
- stroke="#000000"
- stroke-width="0.100"
- id="line410"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="5.4250002"
- y="9.9750004"
- id="text412"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 192.168.1.0/24</text>
- <text
- x="2.165"
- y="8.2250004"
- id="text414"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
- <text
- x="4.6900001"
- y="8.2290001"
- id="text416"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.3</text>
- <text
- x="12.305"
- y="8.1660004"
- id="text418"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.10</text>
- <text
- x="8.5109997"
- y="8.2379999"
- id="text420"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.100+n</text>
- <text
- x="1.3200001"
- y="2.875"
- id="text422"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">stable</text>
- <text
- x="1.34"
- y="3.4749999"
- id="text424"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(NT4)</text>
- <text
- x="3.6670001"
- y="2.8469999"
- id="text426"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">cashpool</text>
- <text
- x="3.6949999"
- y="3.447"
- id="text428"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(Samba)</text>
- <text
- x="7.5609999"
- y="2.872"
- id="text430"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PCn</text>
- <text
- x="7.3260002"
- y="3.4719999"
- id="text432"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(n=1-9)</text>
- <text
- x="11.643"
- y="4.3119998"
- id="text434"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj</text>
- <text
- x="10.716"
- y="4.9120002"
- id="text436"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(HPLaserJet 4)</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="11.88cm"
- height="9.4849997cm"
- viewBox="0.827 -0.889 12.708 8.596"
- id="svg2">
- <defs
- id="defs353" />
- <rect
- width="1.077"
- height="2.5120001"
- x="1.051"
- y="0.93599999"
- id="rect4"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.077"
- height="2.5120001"
- x="1.051"
- y="0.93599999"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="0.861"
- height="0.287"
- x="1.158"
- y="1.087"
- id="rect8"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.861"
- height="0.287"
- x="1.158"
- y="1.374"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.861"
- height="0.287"
- x="1.158"
- y="1.661"
- id="rect12"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.861"
- height="0.287"
- x="1.158"
- y="1.948"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.53799999"
- height="0.17200001"
- x="1.158"
- y="2.293"
- id="rect16"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="1.966"
- cy="2.322"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse18"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="1.966"
- cy="2.322"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse20"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="1.966"
- cy="2.4360001"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse22"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="1.966"
- cy="2.4360001"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse24"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.12899999"
- height="0.115"
- x="1.751"
- y="2.3499999"
- id="rect26"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.12899999"
- height="0.115"
- x="1.751"
- y="2.3499999"
- id="rect28"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.23,2.695 L 1.23,3.323"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.41,2.695 L 1.41,3.323"
- id="path32"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.589,2.695 L 1.589,3.323"
- id="path34"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.769,2.695 L 1.769,3.323"
- id="path36"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.948,2.695 L 1.948,3.323"
- id="path38"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.127,2.695 L 2.127,3.323"
- id="path40"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="0.836,3.664 1.051,3.233 1.051,3.448 2.127,3.448 2.127,3.233 2.414,3.664 0.836,3.664 "
- id="polygon42"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="0.836,3.664 1.051,3.233 1.051,3.448 2.127,3.448 2.127,3.233 2.414,3.664 0.836,3.664 "
- id="polygon44"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.587"
- y1="4.487"
- x2="11.412"
- y2="4.4629998"
- stroke="#000000"
- stroke-width="0.100"
- id="line46"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.625"
- y1="3.664"
- x2="1.624"
- y2="4.5240002"
- stroke="#000000"
- stroke-width="0.100"
- id="line48"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.017"
- height="1.513"
- x="2.9289999"
- y="1.6210001"
- id="rect50"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="2.017"
- height="1.513"
- x="2.9289999"
- y="1.6210001"
- id="rect52"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.58"
- height="1.0420001"
- x="3.148"
- y="1.839"
- id="rect54"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="3.202,3.134 4.24,3.134 4.24,3.369 3.257,3.369 3.202,3.134 "
- id="polygon56"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="3.202,3.134 4.24,3.134 4.24,3.369 3.257,3.369 3.202,3.134 "
- id="polygon58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="4.24,3.134 4.673,3.134 4.618,3.369 4.24,3.369 4.24,3.134 "
- id="polygon60"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.24,3.134 4.673,3.134 4.618,3.369 4.24,3.369 4.24,3.134 "
- id="polygon62"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="4.3109999"
- y="3.204"
- id="rect64"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="4.3109999"
- y="3.204"
- id="rect66"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="3.736,3.369 4.139,3.369 4.139,3.487 4.341,3.487 4.341,3.604 3.534,3.604 3.534,3.487 3.736,3.487 3.736,3.369 "
- id="polygon68"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="3.736,3.369 4.139,3.369 4.139,3.487 4.341,3.487 4.341,3.604 3.534,3.604 3.534,3.487 3.736,3.487 3.736,3.369 "
- id="polygon70"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="2.017"
- height="1.513"
- x="5.5040002"
- y="1.633"
- id="rect72"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="2.017"
- height="1.513"
- x="5.5040002"
- y="1.633"
- id="rect74"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.58"
- height="1.0420001"
- x="5.723"
- y="1.852"
- id="rect76"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="5.777,3.146 6.815,3.146 6.815,3.381 5.832,3.381 5.777,3.146 "
- id="polygon78"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.777,3.146 6.815,3.146 6.815,3.381 5.832,3.381 5.777,3.146 "
- id="polygon80"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.815,3.146 7.248,3.146 7.193,3.381 6.815,3.381 6.815,3.146 "
- id="polygon82"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.815,3.146 7.248,3.146 7.193,3.381 6.815,3.381 6.815,3.146 "
- id="polygon84"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="6.8860002"
- y="3.217"
- id="rect86"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="6.8860002"
- y="3.217"
- id="rect88"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.311,3.381 6.714,3.381 6.714,3.499 6.916,3.499 6.916,3.617 6.109,3.617 6.109,3.499 6.311,3.499 6.311,3.381 "
- id="polygon90"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.311,3.381 6.714,3.381 6.714,3.499 6.916,3.499 6.916,3.617 6.109,3.617 6.109,3.499 6.311,3.499 6.311,3.381 "
- id="polygon92"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="2.017"
- height="1.513"
- x="7.9169998"
- y="1.658"
- id="rect94"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="2.017"
- height="1.513"
- x="7.9169998"
- y="1.658"
- id="rect96"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.58"
- height="1.0420001"
- x="8.1350002"
- y="1.877"
- id="rect98"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="8.19,3.171 9.228,3.171 9.228,3.406 8.244,3.406 8.19,3.171 "
- id="polygon100"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.19,3.171 9.228,3.171 9.228,3.406 8.244,3.406 8.19,3.171 "
- id="polygon102"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.228,3.171 9.66,3.171 9.606,3.406 9.228,3.406 9.228,3.171 "
- id="polygon104"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.228,3.171 9.66,3.171 9.606,3.406 9.228,3.406 9.228,3.171 "
- id="polygon106"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="9.2980003"
- y="3.2420001"
- id="rect108"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="9.2980003"
- y="3.2420001"
- id="rect110"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.723,3.406 9.127,3.406 9.127,3.524 9.328,3.524 9.328,3.642 8.522,3.642 8.522,3.524 8.723,3.524 8.723,3.406 "
- id="polygon112"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.723,3.406 9.127,3.406 9.127,3.524 9.328,3.524 9.328,3.642 8.522,3.642 8.522,3.524 8.723,3.524 8.723,3.406 "
- id="polygon114"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="2.017"
- height="1.513"
- x="10.342"
- y="1.658"
- id="rect116"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="2.017"
- height="1.513"
- x="10.342"
- y="1.658"
- id="rect118"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.58"
- height="1.0420001"
- x="10.56"
- y="1.877"
- id="rect120"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="10.615,3.171 11.653,3.171 11.653,3.406 10.669,3.406 10.615,3.171 "
- id="polygon122"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.615,3.171 11.653,3.171 11.653,3.406 10.669,3.406 10.615,3.171 "
- id="polygon124"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="11.653,3.171 12.085,3.171 12.031,3.406 11.653,3.406 11.653,3.171 "
- id="polygon126"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.653,3.171 12.085,3.171 12.031,3.406 11.653,3.406 11.653,3.171 "
- id="polygon128"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="11.723"
- y="3.2420001"
- id="rect130"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="11.723"
- y="3.2420001"
- id="rect132"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="11.148,3.406 11.552,3.406 11.552,3.524 11.753,3.524 11.753,3.642 10.947,3.642 10.947,3.524 11.148,3.524 11.148,3.406 "
- id="polygon134"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.148,3.406 11.552,3.406 11.552,3.524 11.753,3.524 11.753,3.642 10.947,3.642 10.947,3.524 11.148,3.524 11.148,3.406 "
- id="polygon136"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="3.938"
- y1="3.6040001"
- x2="3.9389999"
- y2="5.2309999"
- stroke="#000000"
- stroke-width="0.100"
- id="line138"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.513"
- y1="3.6170001"
- x2="6.513"
- y2="5.237"
- stroke="#000000"
- stroke-width="0.100"
- id="line140"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.9250002"
- y1="3.642"
- x2="8.9329996"
- y2="4.5"
- stroke="#000000"
- stroke-width="0.100"
- id="line142"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.396"
- y1="3.654"
- x2="11.4"
- y2="5.362"
- stroke="#000000"
- stroke-width="0.100"
- id="line144"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.017"
- height="1.513"
- x="10.442"
- y="5.3460002"
- id="rect146"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="2.017"
- height="1.513"
- x="10.442"
- y="5.3460002"
- id="rect148"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.58"
- height="1.0420001"
- x="10.66"
- y="5.5640001"
- id="rect150"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="10.715,6.859 11.753,6.859 11.753,7.094 10.769,7.094 10.715,6.859 "
- id="polygon152"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.715,6.859 11.753,6.859 11.753,7.094 10.769,7.094 10.715,6.859 "
- id="polygon154"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="11.753,6.859 12.185,6.859 12.131,7.094 11.753,7.094 11.753,6.859 "
- id="polygon156"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.753,6.859 12.185,6.859 12.131,7.094 11.753,7.094 11.753,6.859 "
- id="polygon158"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="11.823"
- y="6.9289999"
- id="rect160"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.093999997"
- height="0.093999997"
- x="11.823"
- y="6.9289999"
- id="rect162"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="11.248,7.094 11.652,7.094 11.652,7.212 11.853,7.212 11.853,7.329 11.047,7.329 11.047,7.212 11.248,7.212 11.248,7.094 "
- id="polygon164"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.248,7.094 11.652,7.094 11.652,7.212 11.853,7.212 11.853,7.329 11.047,7.329 11.047,7.212 11.248,7.212 11.248,7.094 "
- id="polygon166"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="3.171,5.92 3.083,5.956 2.819,6.616 2.819,6.946 2.951,7.056 4.887,7.056 5.019,6.946 5.019,6.616 4.755,5.956 4.667,5.92 3.171,5.92 "
- id="polygon168"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.171,5.92 3.083,5.956 2.819,6.616 2.819,6.946 2.951,7.056 4.887,7.056 5.019,6.946 5.019,6.616 4.755,5.956 4.667,5.92 3.171,5.92 "
- id="polygon170"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 2.863,6.506 L 2.951,6.543 L 4.887,6.543 L 4.975,6.506"
- id="path172"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.887,6.543 L 5.019,6.616"
- id="path174"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 2.819,6.616 L 2.951,6.543"
- id="path176"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.435,5.223 3.391,6.103 4.447,6.103 4.403,5.223 3.435,5.223 "
- id="polygon178"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.435,5.223 3.391,6.103 4.447,6.103 4.403,5.223 3.435,5.223 "
- id="polygon180"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.259,6.103 3.171,6.36 4.667,6.36 4.579,6.103 3.259,6.103 "
- id="polygon182"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.259,6.103 3.171,6.36 4.667,6.36 4.579,6.103 3.259,6.103 "
- id="polygon184"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="3.2590001"
- cy="6.671"
- rx="0.022"
- ry="0.022"
- id="ellipse186"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.2590001"
- cy="6.671"
- rx="0.022"
- ry="0.022"
- id="ellipse188"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.4790001"
- cy="6.671"
- rx="0.022"
- ry="0.022"
- id="ellipse190"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.4790001"
- cy="6.671"
- rx="0.022"
- ry="0.022"
- id="ellipse192"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.6989999"
- cy="6.671"
- rx="0.022"
- ry="0.022"
- id="ellipse194"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.6989999"
- cy="6.671"
- rx="0.022"
- ry="0.022"
- id="ellipse196"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.2590001"
- cy="6.763"
- rx="0.022"
- ry="0.022"
- id="ellipse198"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.2590001"
- cy="6.763"
- rx="0.022"
- ry="0.022"
- id="ellipse200"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.4790001"
- cy="6.763"
- rx="0.022"
- ry="0.022"
- id="ellipse202"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.4790001"
- cy="6.763"
- rx="0.022"
- ry="0.022"
- id="ellipse204"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.6989999"
- cy="6.763"
- rx="0.022"
- ry="0.022"
- id="ellipse206"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.6989999"
- cy="6.763"
- rx="0.022"
- ry="0.022"
- id="ellipse208"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.2590001"
- cy="6.855"
- rx="0.022"
- ry="0.022"
- id="ellipse210"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.2590001"
- cy="6.855"
- rx="0.022"
- ry="0.022"
- id="ellipse212"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.4790001"
- cy="6.855"
- rx="0.022"
- ry="0.022"
- id="ellipse214"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.4790001"
- cy="6.855"
- rx="0.022"
- ry="0.022"
- id="ellipse216"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.6989999"
- cy="6.855"
- rx="0.022"
- ry="0.022"
- id="ellipse218"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.6989999"
- cy="6.855"
- rx="0.022"
- ry="0.022"
- id="ellipse220"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.2590001"
- cy="6.9460001"
- rx="0.022"
- ry="0.022"
- id="ellipse222"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.2590001"
- cy="6.9460001"
- rx="0.022"
- ry="0.022"
- id="ellipse224"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.4790001"
- cy="6.9460001"
- rx="0.022"
- ry="0.022"
- id="ellipse226"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.4790001"
- cy="6.9460001"
- rx="0.022"
- ry="0.022"
- id="ellipse228"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.6989999"
- cy="6.9460001"
- rx="0.022"
- ry="0.022"
- id="ellipse230"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.6989999"
- cy="6.9460001"
- rx="0.022"
- ry="0.022"
- id="ellipse232"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.9189999"
- cy="6.6900001"
- rx="0.27500001"
- ry="0.088"
- id="ellipse234"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="3.9189999"
- cy="6.6900001"
- rx="0.27500001"
- ry="0.088"
- id="ellipse236"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.4689999"
- cy="6.6900001"
- rx="0.27500001"
- ry="0.088"
- id="ellipse238"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="4.4689999"
- cy="6.6900001"
- rx="0.27500001"
- ry="0.088"
- id="ellipse240"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <polygon
- points="5.807,5.902 5.719,5.939 5.455,6.599 5.455,6.929 5.587,7.039 7.523,7.039 7.655,6.929 7.655,6.599 7.391,5.939 7.303,5.902 5.807,5.902 "
- id="polygon242"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="5.807,5.902 5.719,5.939 5.455,6.599 5.455,6.929 5.587,7.039 7.523,7.039 7.655,6.929 7.655,6.599 7.391,5.939 7.303,5.902 5.807,5.902 "
- id="polygon244"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.499,6.489 L 5.587,6.525 L 7.523,6.525 L 7.611,6.489"
- id="path246"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.523,6.525 L 7.655,6.599"
- id="path248"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.455,6.599 L 5.587,6.525"
- id="path250"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.071,5.205 6.027,6.085 7.083,6.085 7.039,5.205 6.071,5.205 "
- id="polygon252"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.071,5.205 6.027,6.085 7.083,6.085 7.039,5.205 6.071,5.205 "
- id="polygon254"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.895,6.085 5.807,6.342 7.303,6.342 7.215,6.085 5.895,6.085 "
- id="polygon256"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="5.895,6.085 5.807,6.342 7.303,6.342 7.215,6.085 5.895,6.085 "
- id="polygon258"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="5.895"
- cy="6.6539998"
- rx="0.022"
- ry="0.022"
- id="ellipse260"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.895"
- cy="6.6539998"
- rx="0.022"
- ry="0.022"
- id="ellipse262"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1149998"
- cy="6.6539998"
- rx="0.022"
- ry="0.022"
- id="ellipse264"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1149998"
- cy="6.6539998"
- rx="0.022"
- ry="0.022"
- id="ellipse266"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.335"
- cy="6.6539998"
- rx="0.022"
- ry="0.022"
- id="ellipse268"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.335"
- cy="6.6539998"
- rx="0.022"
- ry="0.022"
- id="ellipse270"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.895"
- cy="6.7449999"
- rx="0.022"
- ry="0.022"
- id="ellipse272"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.895"
- cy="6.7449999"
- rx="0.022"
- ry="0.022"
- id="ellipse274"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1149998"
- cy="6.7449999"
- rx="0.022"
- ry="0.022"
- id="ellipse276"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1149998"
- cy="6.7449999"
- rx="0.022"
- ry="0.022"
- id="ellipse278"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.335"
- cy="6.7449999"
- rx="0.022"
- ry="0.022"
- id="ellipse280"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.335"
- cy="6.7449999"
- rx="0.022"
- ry="0.022"
- id="ellipse282"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.895"
- cy="6.8369999"
- rx="0.022"
- ry="0.022"
- id="ellipse284"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.895"
- cy="6.8369999"
- rx="0.022"
- ry="0.022"
- id="ellipse286"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1149998"
- cy="6.8369999"
- rx="0.022"
- ry="0.022"
- id="ellipse288"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1149998"
- cy="6.8369999"
- rx="0.022"
- ry="0.022"
- id="ellipse290"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.335"
- cy="6.8369999"
- rx="0.022"
- ry="0.022"
- id="ellipse292"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.335"
- cy="6.8369999"
- rx="0.022"
- ry="0.022"
- id="ellipse294"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.895"
- cy="6.9289999"
- rx="0.022"
- ry="0.022"
- id="ellipse296"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.895"
- cy="6.9289999"
- rx="0.022"
- ry="0.022"
- id="ellipse298"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1149998"
- cy="6.9289999"
- rx="0.022"
- ry="0.022"
- id="ellipse300"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1149998"
- cy="6.9289999"
- rx="0.022"
- ry="0.022"
- id="ellipse302"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.335"
- cy="6.9289999"
- rx="0.022"
- ry="0.022"
- id="ellipse304"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.335"
- cy="6.9289999"
- rx="0.022"
- ry="0.022"
- id="ellipse306"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5549998"
- cy="6.6719999"
- rx="0.27500001"
- ry="0.088"
- id="ellipse308"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.5549998"
- cy="6.6719999"
- rx="0.27500001"
- ry="0.088"
- id="ellipse310"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.105"
- cy="6.6719999"
- rx="0.27500001"
- ry="0.088"
- id="ellipse312"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.105"
- cy="6.6719999"
- rx="0.27500001"
- ry="0.088"
- id="ellipse314"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <text
- x="3.415"
- y="1.183"
- id="text316"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk1</text>
- <text
- x="5.9000001"
- y="1.184"
- id="text318"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk2</text>
- <text
- x="8.3559999"
- y="1.202"
- id="text320"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk3</text>
- <text
- x="10.813"
- y="1.237"
- id="text322"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk4</text>
- <text
- x="10.92"
- y="8.0609999"
- id="text324"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">desk5</text>
- <text
- x="1.138"
- y="0.44"
- id="text326"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">server</text>
- <text
- x="4.809"
- y="-0.479"
- id="text328"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Workgroup: MIDEARTH</text>
- <text
- x="3.0309999"
- y="8.0959997"
- id="text330"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PRINTQ</text>
- <text
- x="6.211"
- y="8.0249996"
- id="text332"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj5</text>
- <text
- x="1.154"
- y="4.1560001"
- id="text334"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
- <text
- x="3.0799999"
- y="4.145"
- id="text336"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.101</text>
- <text
- x="5.605"
- y="4.1430001"
- id="text338"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.102</text>
- <text
- x="8.0349998"
- y="4.1360002"
- id="text340"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.103</text>
- <text
- x="10.516"
- y="4.1459999"
- id="text342"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.104</text>
- <text
- x="10.515"
- y="5.1589999"
- id="text344"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.105</text>
- <text
- x="3.2379999"
- y="5.0170002"
- id="text346"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.20</text>
- <text
- x="5.8140001"
- y="5.007"
- id="text348"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.30</text>
- <text
- x="5.5159998"
- y="0.15899999"
- id="text350"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 192.168.1.0/24</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="22.440001cm"
- height="13.923cm"
- viewBox="2.2 5.38 24.64 19.302"
- id="svg2">
- <defs
- id="defs95" />
- <rect
- width="7.625"
- height="11.175"
- x="9.3500004"
- y="6.2750001"
- id="rect4"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.162"
- y1="6.2750001"
- x2="13.162"
- y2="17.450001"
- stroke="#000000"
- stroke-width="0.100"
- id="line6"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.3500004"
- y1="8.8500004"
- x2="16.975"
- y2="8.8500004"
- stroke="#000000"
- stroke-width="0.100"
- id="line8"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.3400002"
- y1="11.68"
- x2="16.975"
- y2="11.725"
- stroke="#000000"
- stroke-width="0.100"
- id="line10"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.3149996"
- y1="14.655"
- x2="16.950001"
- y2="14.65"
- stroke="#000000"
- stroke-width="0.100"
- id="line12"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="10.404"
- y="5.9749999"
- id="text14"
- style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Posix</text>
- <text
- x="14.161"
- y="5.9650002"
- id="text16"
- style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="10.277"
- y="7.7399998"
- id="text18"
- style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">People</text>
- <text
- x="14.52"
- y="7.375"
- id="text20"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">User</text>
- <text
- x="14.043"
- y="8.1750002"
- id="text22"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounts</text>
- <text
- x="10.328"
- y="16.25"
- id="text24"
- style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">uid/gids</text>
- <text
- x="14.086"
- y="13.125"
- id="text26"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Windows</text>
- <text
- x="14.27"
- y="13.925"
- id="text28"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Groups</text>
- <text
- x="10.306"
- y="13.334"
- id="text30"
- style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Groups</text>
- <text
- x="10.285"
- y="10.459"
- id="text32"
- style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">People</text>
- <text
- x="14.193"
- y="9.7340002"
- id="text34"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain</text>
- <text
- x="14.138"
- y="10.534"
- id="text36"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member</text>
- <text
- x="13.99"
- y="11.334"
- id="text38"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Machines</text>
- <text
- x="14.257"
- y="16.284"
- id="text40"
- style="font-size:0.89999998px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">SIDs</text>
- <rect
- width="4.3499999"
- height="1.625"
- x="2.25"
- y="9.4499998"
- id="rect42"
- style="fill:#c6c6c6;stroke:none;stroke-width:0" />
- <rect
- width="4.3499999"
- height="1.625"
- x="2.25"
- y="9.4499998"
- id="rect44"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.3500004"
- y1="6.2750001"
- x2="6.5999999"
- y2="9.4499998"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line46"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <line
- x1="6.5999999"
- y1="11.075"
- x2="9.3249998"
- y2="14.65"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line48"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <text
- x="3.313"
- y="10.5"
- id="text50"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NSS_LDAP</text>
- <rect
- width="5.0999999"
- height="1.625"
- x="2.2750001"
- y="15.225"
- id="rect52"
- style="fill:#b9b9b9;stroke:none;stroke-width:0" />
- <rect
- width="5.0999999"
- height="1.625"
- x="2.2750001"
- y="15.225"
- id="rect54"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3.415"
- y="16.247"
- id="text56"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Winbind (NSS)</text>
- <line
- x1="9.3500004"
- y1="14.725"
- x2="7.375"
- y2="15.225"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line58"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <line
- x1="7.375"
- y1="16.85"
- x2="9.3500004"
- y2="17.450001"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line60"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <rect
- width="5.25"
- height="2.2249999"
- x="19.325001"
- y="9.1499996"
- id="rect62"
- style="fill:#adadad;stroke:none;stroke-width:0" />
- <rect
- width="5.25"
- height="2.2249999"
- x="19.325001"
- y="9.1499996"
- id="rect64"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="20.535"
- y="10.522"
- id="text66"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd + winbind</text>
- <line
- x1="16.975"
- y1="6.2750001"
- x2="19.325001"
- y2="9.1499996"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line68"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <line
- x1="19.325001"
- y1="11.375"
- x2="16.975"
- y2="14.675"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line70"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <rect
- width="5.25"
- height="2.1300001"
- x="19.34"
- y="14.925"
- id="rect72"
- style="fill:#adadad;stroke:none;stroke-width:0" />
- <rect
- width="5.25"
- height="2.1300001"
- x="19.34"
- y="14.925"
- id="rect74"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="21.211"
- y="15.875"
- id="text76"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">winbind</text>
- <text
- x="21.121"
- y="16.575001"
- id="text78"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(IDMAP)</text>
- <line
- x1="19.34"
- y1="14.925"
- x2="16.975"
- y2="14.6"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line80"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <line
- x1="19.34"
- y1="17.055"
- x2="17.049999"
- y2="17.375"
- stroke="#000000"
- stroke-width="0.050"
- stroke-dasharray="0.10,0.10"
- id="line82"
- style="stroke:#000000;stroke-width:0.05;stroke-dasharray:0.1, 0.1" />
- <text
- x="3.2219999"
- y="6.375"
- id="text84"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">UNIX Interface</text>
- <text
- x="3.8310001"
- y="7.0749998"
- id="text86"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">to LDAP</text>
- <text
- x="20.378"
- y="6.3000002"
- id="text88"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba Interface</text>
- <text
- x="21.156"
- y="7"
- id="text90"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">to LDAP</text>
- <text
- x="11.024"
- y="18.74"
- id="text92"
- style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP Database</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="12.429cm"
- height="7.289cm"
- viewBox="0.025 1.145 12.454 8.434"
- id="svg2">
- <defs
- id="defs595" />
- <rect
- width="4.4790001"
- height="5.9099998"
- x="0.34999999"
- y="2.1919999"
- id="rect4"
- style="fill:#dcdcdc;stroke:none;stroke-width:0" />
- <path
- d="M 0.35,2.192 C 0.18431458,2.192 0.05,2.3263146 0.05,2.492"
- id="path6"
- style="fill:#dcdcdc;stroke:none" />
- <path
- d="M 5.129,2.492 C 5.129,2.3263146 4.9946854,2.192 4.829,2.192"
- id="path8"
- style="fill:#dcdcdc;stroke:none" />
- <rect
- width="5.079"
- height="5.3099999"
- x="0.050000001"
- y="2.4920001"
- id="rect10"
- style="fill:#dcdcdc;stroke:none;stroke-width:0" />
- <path
- d="M 0.05,7.802 C 0.05,7.9676854 0.18431458,8.102 0.35,8.102"
- id="path12"
- style="fill:#dcdcdc;stroke:none" />
- <path
- d="M 4.829,8.102 C 4.9946854,8.102 5.129,7.9676854 5.129,7.802"
- id="path14"
- style="fill:#dcdcdc;stroke:none" />
- <line
- x1="0.34999999"
- y1="2.1919999"
- x2="4.829"
- y2="2.1919999"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.34999999"
- y1="8.1020002"
- x2="4.829"
- y2="8.1020002"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.35,2.192 C 0.18431458,2.192 0.05,2.3263146 0.05,2.492"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 5.129,2.492 C 5.129,2.3263146 4.9946854,2.192 4.829,2.192"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.050000001"
- y1="2.4920001"
- x2="0.050000001"
- y2="7.802"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="5.1290002"
- y1="2.4920001"
- x2="5.1290002"
- y2="7.802"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.05,7.802 C 0.05,7.9676854 0.18431458,8.102 0.35,8.102"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 4.829,8.102 C 4.9946854,8.102 5.129,7.9676854 5.129,7.802"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="4.1500001"
- height="5.9629998"
- x="7.9790001"
- y="2.1400001"
- id="rect32"
- style="fill:#dcdcdc;stroke:none;stroke-width:0" />
- <path
- d="M 7.979,2.14 C 7.8133146,2.14 7.679,2.2743146 7.679,2.44"
- id="path34"
- style="fill:#dcdcdc;stroke:none" />
- <path
- d="M 12.429,2.44 C 12.429,2.2743146 12.294685,2.14 12.129,2.14"
- id="path36"
- style="fill:#dcdcdc;stroke:none" />
- <rect
- width="4.75"
- height="5.3629999"
- x="7.6789999"
- y="2.4400001"
- id="rect38"
- style="fill:#dcdcdc;stroke:none;stroke-width:0" />
- <path
- d="M 7.679,7.802 C 7.679,7.9676854 7.8133146,8.102 7.979,8.102"
- id="path40"
- style="fill:#dcdcdc;stroke:none" />
- <path
- d="M 12.129,8.102 C 12.294685,8.102 12.429,7.9676854 12.429,7.802"
- id="path42"
- style="fill:#dcdcdc;stroke:none" />
- <line
- x1="7.9790001"
- y1="2.1400001"
- x2="12.129"
- y2="2.1400001"
- stroke="#000000"
- stroke-width="0.050"
- id="line44"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="7.9790001"
- y1="8.1020002"
- x2="12.129"
- y2="8.1020002"
- stroke="#000000"
- stroke-width="0.050"
- id="line46"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 7.979,2.14 C 7.8133146,2.14 7.679,2.2743146 7.679,2.44"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.429,2.44 C 12.429,2.2743146 12.294685,2.14 12.129,2.14"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="7.6789999"
- y1="2.4400001"
- x2="7.6789999"
- y2="7.802"
- stroke="#000000"
- stroke-width="0.050"
- id="line52"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.429"
- y1="2.4400001"
- x2="12.429"
- y2="7.802"
- stroke="#000000"
- stroke-width="0.050"
- id="line54"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 7.679,7.802 C 7.679,7.9676854 7.8133146,8.102 7.979,8.102"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.129,8.102 C 12.294685,8.102 12.429,7.9676854 12.429,7.802"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <text
- x="5.3099999"
- y="4.9510002"
- id="text60"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
- <text
- x="1.069"
- y="6.0370002"
- id="text62"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">IP via DHCP</text>
- <text
- x="4.098"
- y="3.1889999"
- id="text64"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj4</text>
- <rect
- width="1.309"
- height="3.928"
- x="5.7750001"
- y="3.1860001"
- id="rect66"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.309"
- height="3.928"
- x="5.7750001"
- y="3.1860001"
- id="rect68"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.309"
- height="3.928"
- x="5.7750001"
- y="3.1860001"
- id="rect70"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.0470001"
- height="1.571"
- x="5.9060001"
- y="3.3169999"
- id="rect72"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.0470001"
- height="1.571"
- x="5.9060001"
- y="3.3169999"
- id="rect74"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.0470001"
- height="1.571"
- x="5.9060001"
- y="3.3169999"
- id="rect76"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.9060001"
- y1="3.579"
- x2="6.9530001"
- y2="3.579"
- stroke="#000000"
- stroke-width="0.010"
- id="line78"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.9530001"
- y1="3.8410001"
- x2="5.9060001"
- y2="3.8410001"
- stroke="#000000"
- stroke-width="0.010"
- id="line80"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.9060001"
- y1="4.1030002"
- x2="6.9530001"
- y2="4.1030002"
- stroke="#000000"
- stroke-width="0.010"
- id="line82"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.9060001"
- y1="4.3639998"
- x2="6.9530001"
- y2="4.3639998"
- stroke="#000000"
- stroke-width="0.010"
- id="line84"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.9530001"
- y1="4.6259999"
- x2="5.9060001"
- y2="4.6259999"
- stroke="#000000"
- stroke-width="0.010"
- id="line86"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.72000003"
- height="0.39300001"
- x="5.9060001"
- y="5.0190001"
- id="rect88"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.72000003"
- height="0.39300001"
- x="5.9060001"
- y="5.0190001"
- id="rect90"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.72000003"
- height="0.39300001"
- x="5.9060001"
- y="5.0190001"
- id="rect92"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.7750001"
- y1="5.6739998"
- x2="7.0840001"
- y2="5.6739998"
- stroke="#000000"
- stroke-width="0.010"
- id="line94"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.3639998"
- y="5.8049998"
- id="rect96"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.3639998"
- y="5.8049998"
- id="rect98"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.3639998"
- y="5.8049998"
- id="rect100"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.6259999"
- y="5.8049998"
- id="rect102"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.6259999"
- y="5.8049998"
- id="rect104"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.6259999"
- y="5.8049998"
- id="rect106"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.888"
- y="5.8049998"
- id="rect108"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.888"
- y="5.8049998"
- id="rect110"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.064999998"
- height="0.064999998"
- x="6.888"
- y="5.8049998"
- id="rect112"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.131"
- height="0.131"
- x="6.822"
- y="5.4120002"
- id="rect114"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.131"
- height="0.131"
- x="6.822"
- y="5.4120002"
- id="rect116"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.131"
- height="0.131"
- x="6.822"
- y="5.4120002"
- id="rect118"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.9060001"
- y1="5.2150002"
- x2="6.6259999"
- y2="5.2150002"
- stroke="#000000"
- stroke-width="0.010"
- id="line120"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.19599999"
- height="0.19599999"
- x="5.9060001"
- y="5.7389998"
- id="rect122"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.19599999"
- height="0.19599999"
- x="5.9060001"
- y="5.7389998"
- id="rect124"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.19599999"
- height="0.19599999"
- x="5.9060001"
- y="5.7389998"
- id="rect126"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.917"
- height="0.064999998"
- x="5.9710002"
- y="4.6919999"
- id="rect128"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.917"
- height="0.064999998"
- x="5.9710002"
- y="4.6919999"
- id="rect130"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.917"
- height="0.064999998"
- x="5.9710002"
- y="4.6919999"
- id="rect132"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.9710002"
- y1="5.085"
- x2="6.5609999"
- y2="5.085"
- stroke="#000000"
- stroke-width="0.010"
- id="line134"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.5609999"
- y1="5.1500001"
- x2="6.4949999"
- y2="5.1500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line136"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.9710002"
- y1="5.1500001"
- x2="6.0370002"
- y2="5.1500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line138"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.32699999"
- height="0.064999998"
- x="6.1020002"
- y="5.085"
- id="rect140"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.32699999"
- height="0.064999998"
- x="6.1020002"
- y="5.085"
- id="rect142"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.32699999"
- height="0.064999998"
- x="6.1020002"
- y="5.085"
- id="rect144"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.9710002"
- y1="4.823"
- x2="6.0370002"
- y2="4.823"
- stroke="#000000"
- stroke-width="0.010"
- id="line146"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.1020002"
- y1="4.823"
- x2="6.1680002"
- y2="4.823"
- stroke="#000000"
- stroke-width="0.010"
- id="line148"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="6.757"
- y1="4.823"
- x2="6.888"
- y2="4.823"
- stroke="#000000"
- stroke-width="0.010"
- id="line150"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.8400002"
- y1="7.0489998"
- x2="7.0190001"
- y2="7.0489998"
- stroke="#000000"
- stroke-width="0.010"
- id="line152"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0190001"
- y1="6.9829998"
- x2="5.8400002"
- y2="6.9829998"
- stroke="#000000"
- stroke-width="0.010"
- id="line154"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.8400002"
- y1="6.9180002"
- x2="7.0190001"
- y2="6.9180002"
- stroke="#000000"
- stroke-width="0.010"
- id="line156"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0190001"
- y1="6.8520002"
- x2="5.8400002"
- y2="6.8520002"
- stroke="#000000"
- stroke-width="0.010"
- id="line158"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.8400002"
- y1="6.7870002"
- x2="7.0190001"
- y2="6.7870002"
- stroke="#000000"
- stroke-width="0.010"
- id="line160"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0190001"
- y1="6.7210002"
- x2="5.8400002"
- y2="6.7210002"
- stroke="#000000"
- stroke-width="0.010"
- id="line162"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.8400002"
- y1="6.6560001"
- x2="7.0190001"
- y2="6.6560001"
- stroke="#000000"
- stroke-width="0.010"
- id="line164"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0190001"
- y1="6.5900002"
- x2="5.8400002"
- y2="6.5900002"
- stroke="#000000"
- stroke-width="0.010"
- id="line166"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.8400002"
- y1="6.5250001"
- x2="7.0190001"
- y2="6.5250001"
- stroke="#000000"
- stroke-width="0.010"
- id="line168"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0190001"
- y1="6.4590001"
- x2="5.8400002"
- y2="6.4590001"
- stroke="#000000"
- stroke-width="0.010"
- id="line170"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.8400002"
- y1="6.3940001"
- x2="7.0190001"
- y2="6.3940001"
- stroke="#000000"
- stroke-width="0.010"
- id="line172"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0190001"
- y1="6.3280001"
- x2="5.8400002"
- y2="6.3280001"
- stroke="#000000"
- stroke-width="0.010"
- id="line174"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.8400002"
- y1="6.263"
- x2="7.0190001"
- y2="6.263"
- stroke="#000000"
- stroke-width="0.010"
- id="line176"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0190001"
- y1="6.197"
- x2="5.8400002"
- y2="6.197"
- stroke="#000000"
- stroke-width="0.010"
- id="line178"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.0159998"
- y1="5.1269999"
- x2="11.562"
- y2="5.1269999"
- stroke="#000000"
- stroke-width="0.100"
- id="line180"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="7.6430001"
- y1="5.1269999"
- x2="7.6430001"
- y2="5.125"
- stroke="#000000"
- stroke-width="0.100"
- id="line182"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.5790005"
- y1="5.1269999"
- x2="8.5790005"
- y2="4.2020001"
- stroke="#000000"
- stroke-width="0.100"
- id="line184"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.5790005"
- y1="5.1269999"
- x2="8.5790005"
- y2="6.177"
- stroke="#000000"
- stroke-width="0.100"
- id="line186"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.016"
- y1="5.1269999"
- x2="10.016"
- y2="4.2150002"
- stroke="#000000"
- stroke-width="0.100"
- id="line188"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.177"
- y1="5.1269999"
- x2="10.177"
- y2="5.1399999"
- stroke="#000000"
- stroke-width="0.100"
- id="line190"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.512"
- y1="5.1269999"
- x2="11.512"
- y2="4.177"
- stroke="#000000"
- stroke-width="0.100"
- id="line192"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="0.55599999"
- y1="5.1669998"
- x2="5.7789998"
- y2="5.177"
- stroke="#000000"
- stroke-width="0.100"
- id="line194"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.244"
- y1="5.1700001"
- x2="2.244"
- y2="5.1599998"
- stroke="#000000"
- stroke-width="0.100"
- id="line196"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.738"
- y1="5.1690001"
- x2="1.74"
- y2="4.1259999"
- stroke="#000000"
- stroke-width="0.100"
- id="line198"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="4.1370001"
- y1="5.1739998"
- x2="4.1389999"
- y2="4.27"
- stroke="#000000"
- stroke-width="0.100"
- id="line200"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.7620001"
- y1="5.171"
- x2="2.7639999"
- y2="4.1240001"
- stroke="#000000"
- stroke-width="0.100"
- id="line202"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="4.1430001"
- y1="5.1739998"
- x2="4.1409998"
- y2="6.165"
- stroke="#000000"
- stroke-width="0.100"
- id="line204"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="0.60600001"
- y1="5.1669998"
- x2="0.60799998"
- y2="4.1690001"
- stroke="#000000"
- stroke-width="0.100"
- id="line206"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.713"
- height="0.53500003"
- x="8.2119999"
- y="3.5190001"
- id="rect208"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.713"
- height="0.53500003"
- x="8.2119999"
- y="3.5190001"
- id="rect210"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.55900002"
- height="0.36899999"
- x="8.2889996"
- y="3.596"
- id="rect212"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="8.308,4.054 8.675,4.054 8.675,4.137 8.328,4.137 8.308,4.054 "
- id="polygon214"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.308,4.054 8.675,4.054 8.675,4.137 8.328,4.137 8.308,4.054 "
- id="polygon216"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.675,4.054 8.828,4.054 8.809,4.137 8.675,4.137 8.675,4.054 "
- id="polygon218"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.675,4.054 8.828,4.054 8.809,4.137 8.675,4.137 8.675,4.054 "
- id="polygon220"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.033"
- height="0.033"
- x="8.6999998"
- y="4.079"
- id="rect222"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.033"
- height="0.033"
- x="8.6999998"
- y="4.079"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.497,4.137 8.64,4.137 8.64,4.179 8.711,4.179 8.711,4.22 8.426,4.22 8.426,4.179 8.497,4.179 8.497,4.137 "
- id="polygon226"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.497,4.137 8.64,4.137 8.64,4.179 8.711,4.179 8.711,4.22 8.426,4.22 8.426,4.179 8.497,4.179 8.497,4.137 "
- id="polygon228"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.67199999"
- height="0.50400001"
- x="1.404"
- y="3.4649999"
- id="rect230"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.67199999"
- height="0.50400001"
- x="1.404"
- y="3.4649999"
- id="rect232"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.52700001"
- height="0.347"
- x="1.476"
- y="3.5380001"
- id="rect234"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="1.495,3.969 1.841,3.969 1.841,4.048 1.513,4.048 1.495,3.969 "
- id="polygon236"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="1.495,3.969 1.841,3.969 1.841,4.048 1.513,4.048 1.495,3.969 "
- id="polygon238"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="1.841,3.969 1.985,3.969 1.967,4.048 1.841,4.048 1.841,3.969 "
- id="polygon240"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="1.841,3.969 1.985,3.969 1.967,4.048 1.841,4.048 1.841,3.969 "
- id="polygon242"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.030999999"
- height="0.030999999"
- x="1.864"
- y="3.993"
- id="rect244"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.030999999"
- height="0.030999999"
- x="1.864"
- y="3.993"
- id="rect246"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="1.672,4.048 1.807,4.048 1.807,4.087 1.874,4.087 1.874,4.126 1.605,4.126 1.605,4.087 1.672,4.087 1.672,4.048 "
- id="polygon248"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="1.672,4.048 1.807,4.048 1.807,4.087 1.874,4.087 1.874,4.126 1.605,4.126 1.605,4.087 1.672,4.087 1.672,4.048 "
- id="polygon250"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.64499998"
- height="0.484"
- x="2.441"
- y="3.49"
- id="rect252"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.64499998"
- height="0.484"
- x="2.441"
- y="3.49"
- id="rect254"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.505"
- height="0.333"
- x="2.5109999"
- y="3.5599999"
- id="rect256"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="2.528,3.974 2.86,3.974 2.86,4.049 2.546,4.049 2.528,3.974 "
- id="polygon258"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.528,3.974 2.86,3.974 2.86,4.049 2.546,4.049 2.528,3.974 "
- id="polygon260"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="2.86,3.974 2.999,3.974 2.981,4.049 2.86,4.049 2.86,3.974 "
- id="polygon262"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.86,3.974 2.999,3.974 2.981,4.049 2.86,4.049 2.86,3.974 "
- id="polygon264"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.029999999"
- height="0.029999999"
- x="2.8829999"
- y="3.997"
- id="rect266"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.029999999"
- height="0.029999999"
- x="2.8829999"
- y="3.997"
- id="rect268"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="2.699,4.049 2.828,4.049 2.828,4.087 2.893,4.087 2.893,4.124 2.635,4.124 2.635,4.087 2.699,4.087 2.699,4.049 "
- id="polygon270"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.699,4.049 2.828,4.049 2.828,4.087 2.893,4.087 2.893,4.124 2.635,4.124 2.635,4.087 2.699,4.087 2.699,4.049 "
- id="polygon272"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.65899998"
- height="0.495"
- x="0.27900001"
- y="3.52"
- id="rect274"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.65899998"
- height="0.495"
- x="0.27900001"
- y="3.52"
- id="rect276"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.51700002"
- height="0.34099999"
- x="0.34999999"
- y="3.592"
- id="rect278"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="0.368,4.015 0.707,4.015 0.707,4.092 0.386,4.092 0.368,4.015 "
- id="polygon280"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="0.368,4.015 0.707,4.015 0.707,4.092 0.386,4.092 0.368,4.015 "
- id="polygon282"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="0.707,4.015 0.849,4.015 0.831,4.092 0.707,4.092 0.707,4.015 "
- id="polygon284"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="0.707,4.015 0.849,4.015 0.831,4.092 0.707,4.092 0.707,4.015 "
- id="polygon286"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.030999999"
- height="0.030999999"
- x="0.73000002"
- y="4.0380001"
- id="rect288"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.030999999"
- height="0.030999999"
- x="0.73000002"
- y="4.0380001"
- id="rect290"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="0.542,4.092 0.674,4.092 0.674,4.13 0.74,4.13 0.74,4.169 0.476,4.169 0.476,4.13 0.542,4.13 0.542,4.092 "
- id="polygon292"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="0.542,4.092 0.674,4.092 0.674,4.13 0.74,4.13 0.74,4.169 0.476,4.169 0.476,4.13 0.542,4.13 0.542,4.092 "
- id="polygon294"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.65899998"
- height="0.49399999"
- x="9.6879997"
- y="3.527"
- id="rect296"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.65899998"
- height="0.49399999"
- x="9.6879997"
- y="3.527"
- id="rect298"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.51599997"
- height="0.34099999"
- x="9.7589998"
- y="3.599"
- id="rect300"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.777,4.022 10.116,4.022 10.116,4.099 9.795,4.099 9.777,4.022 "
- id="polygon302"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.777,4.022 10.116,4.022 10.116,4.099 9.795,4.099 9.777,4.022 "
- id="polygon304"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="10.116,4.022 10.258,4.022 10.24,4.099 10.116,4.099 10.116,4.022 "
- id="polygon306"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.116,4.022 10.258,4.022 10.24,4.099 10.116,4.099 10.116,4.022 "
- id="polygon308"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.030999999"
- height="0.030999999"
- x="10.139"
- y="4.0450001"
- id="rect310"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.030999999"
- height="0.030999999"
- x="10.139"
- y="4.0450001"
- id="rect312"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.952,4.099 10.083,4.099 10.083,4.137 10.149,4.137 10.149,4.176 9.886,4.176 9.886,4.137 9.952,4.137 9.952,4.099 "
- id="polygon314"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.952,4.099 10.083,4.099 10.083,4.137 10.149,4.137 10.149,4.176 9.886,4.176 9.886,4.137 9.952,4.137 9.952,4.099 "
- id="polygon316"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.62300003"
- height="0.46700001"
- x="11.2"
- y="3.5650001"
- id="rect318"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.62300003"
- height="0.46700001"
- x="11.2"
- y="3.5650001"
- id="rect320"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.48800001"
- height="0.322"
- x="11.268"
- y="3.632"
- id="rect322"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="11.285,4.032 11.605,4.032 11.605,4.105 11.302,4.105 11.285,4.032 "
- id="polygon324"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.285,4.032 11.605,4.032 11.605,4.105 11.302,4.105 11.285,4.032 "
- id="polygon326"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="11.605,4.032 11.739,4.032 11.722,4.105 11.605,4.105 11.605,4.032 "
- id="polygon328"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.605,4.032 11.739,4.032 11.722,4.105 11.605,4.105 11.605,4.032 "
- id="polygon330"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.028999999"
- height="0.028999999"
- x="11.627"
- y="4.0539999"
- id="rect332"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.028999999"
- height="0.028999999"
- x="11.627"
- y="4.0539999"
- id="rect334"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="11.449,4.105 11.574,4.105 11.574,4.141 11.636,4.141 11.636,4.177 11.387,4.177 11.387,4.141 11.449,4.141 11.449,4.105 "
- id="polygon336"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.449,4.105 11.574,4.105 11.574,4.141 11.636,4.141 11.636,4.177 11.387,4.177 11.387,4.141 11.449,4.141 11.449,4.105 "
- id="polygon338"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="3.803,3.759 3.763,3.775 3.645,4.072 3.645,4.22 3.704,4.27 4.574,4.27 4.634,4.22 4.634,4.072 4.515,3.775 4.475,3.759 3.803,3.759 "
- id="polygon340"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.803,3.759 3.763,3.775 3.645,4.072 3.645,4.22 3.704,4.27 4.574,4.27 4.634,4.22 4.634,4.072 4.515,3.775 4.475,3.759 3.803,3.759 "
- id="polygon342"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 3.665,4.023 L 3.704,4.039 L 4.574,4.039 L 4.614,4.023"
- id="path344"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.574,4.039 L 4.634,4.072"
- id="path346"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 3.645,4.072 L 3.704,4.039"
- id="path348"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.922,3.446 3.902,3.841 4.376,3.841 4.357,3.446 3.922,3.446 "
- id="polygon350"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.922,3.446 3.902,3.841 4.376,3.841 4.357,3.446 3.922,3.446 "
- id="polygon352"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.843,3.841 3.803,3.957 4.475,3.957 4.436,3.841 3.843,3.841 "
- id="polygon354"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.843,3.841 3.803,3.957 4.475,3.957 4.436,3.841 3.843,3.841 "
- id="polygon356"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="3.8429999"
- cy="4.0970001"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse358"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.8429999"
- cy="4.0970001"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse360"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.941"
- cy="4.0970001"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse362"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.941"
- cy="4.0970001"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse364"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.04"
- cy="4.0970001"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse366"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.04"
- cy="4.0970001"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse368"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.8429999"
- cy="4.138"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse370"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.8429999"
- cy="4.138"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse372"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.941"
- cy="4.138"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse374"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.941"
- cy="4.138"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse376"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.04"
- cy="4.138"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse378"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.04"
- cy="4.138"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse380"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.8429999"
- cy="4.1789999"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse382"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.8429999"
- cy="4.1789999"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse384"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.941"
- cy="4.1789999"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse386"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.941"
- cy="4.1789999"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse388"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.04"
- cy="4.1789999"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse390"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.04"
- cy="4.1789999"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse392"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.8429999"
- cy="4.2199998"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse394"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.8429999"
- cy="4.2199998"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse396"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.941"
- cy="4.2199998"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse398"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.941"
- cy="4.2199998"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse400"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.04"
- cy="4.2199998"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse402"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.04"
- cy="4.2199998"
- rx="0.0099999998"
- ry="0.0099999998"
- id="ellipse404"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.1389999"
- cy="4.105"
- rx="0.124"
- ry="0.039999999"
- id="ellipse406"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="4.1389999"
- cy="4.105"
- rx="0.124"
- ry="0.039999999"
- id="ellipse408"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.3860002"
- cy="4.105"
- rx="0.124"
- ry="0.039999999"
- id="ellipse410"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="4.3860002"
- cy="4.105"
- rx="0.124"
- ry="0.039999999"
- id="ellipse412"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <polygon
- points="3.741,6.521 3.695,6.54 3.558,6.884 3.558,7.056 3.627,7.114 4.635,7.114 4.704,7.056 4.704,6.884 4.567,6.54 4.521,6.521 3.741,6.521 "
- id="polygon414"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.741,6.521 3.695,6.54 3.558,6.884 3.558,7.056 3.627,7.114 4.635,7.114 4.704,7.056 4.704,6.884 4.567,6.54 4.521,6.521 3.741,6.521 "
- id="polygon416"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 3.581,6.827 L 3.627,6.846 L 4.635,6.846 L 4.681,6.827"
- id="path418"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.635,6.846 L 4.704,6.884"
- id="path420"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 3.558,6.884 L 3.627,6.846"
- id="path422"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.879,6.158 3.856,6.617 4.406,6.617 4.383,6.158 3.879,6.158 "
- id="polygon424"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.879,6.158 3.856,6.617 4.406,6.617 4.383,6.158 3.879,6.158 "
- id="polygon426"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.787,6.617 3.741,6.751 4.521,6.751 4.475,6.617 3.787,6.617 "
- id="polygon428"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="3.787,6.617 3.741,6.751 4.521,6.751 4.475,6.617 3.787,6.617 "
- id="polygon430"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="3.7869999"
- cy="6.9130001"
- rx="0.011"
- ry="0.011"
- id="ellipse432"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.7869999"
- cy="6.9130001"
- rx="0.011"
- ry="0.011"
- id="ellipse434"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.902"
- cy="6.9130001"
- rx="0.011"
- ry="0.011"
- id="ellipse436"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.902"
- cy="6.9130001"
- rx="0.011"
- ry="0.011"
- id="ellipse438"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.0159998"
- cy="6.9130001"
- rx="0.011"
- ry="0.011"
- id="ellipse440"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.0159998"
- cy="6.9130001"
- rx="0.011"
- ry="0.011"
- id="ellipse442"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.7869999"
- cy="6.961"
- rx="0.011"
- ry="0.011"
- id="ellipse444"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.7869999"
- cy="6.961"
- rx="0.011"
- ry="0.011"
- id="ellipse446"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.902"
- cy="6.961"
- rx="0.011"
- ry="0.011"
- id="ellipse448"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.902"
- cy="6.961"
- rx="0.011"
- ry="0.011"
- id="ellipse450"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.0159998"
- cy="6.961"
- rx="0.011"
- ry="0.011"
- id="ellipse452"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.0159998"
- cy="6.961"
- rx="0.011"
- ry="0.011"
- id="ellipse454"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.7869999"
- cy="7.0079999"
- rx="0.011"
- ry="0.011"
- id="ellipse456"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.7869999"
- cy="7.0079999"
- rx="0.011"
- ry="0.011"
- id="ellipse458"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.902"
- cy="7.0079999"
- rx="0.011"
- ry="0.011"
- id="ellipse460"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.902"
- cy="7.0079999"
- rx="0.011"
- ry="0.011"
- id="ellipse462"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.0159998"
- cy="7.0079999"
- rx="0.011"
- ry="0.011"
- id="ellipse464"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.0159998"
- cy="7.0079999"
- rx="0.011"
- ry="0.011"
- id="ellipse466"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.7869999"
- cy="7.0560002"
- rx="0.011"
- ry="0.011"
- id="ellipse468"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.7869999"
- cy="7.0560002"
- rx="0.011"
- ry="0.011"
- id="ellipse470"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="3.902"
- cy="7.0560002"
- rx="0.011"
- ry="0.011"
- id="ellipse472"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="3.902"
- cy="7.0560002"
- rx="0.011"
- ry="0.011"
- id="ellipse474"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.0159998"
- cy="7.0560002"
- rx="0.011"
- ry="0.011"
- id="ellipse476"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.0159998"
- cy="7.0560002"
- rx="0.011"
- ry="0.011"
- id="ellipse478"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.131"
- cy="6.9219999"
- rx="0.14300001"
- ry="0.046"
- id="ellipse480"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="4.131"
- cy="6.9219999"
- rx="0.14300001"
- ry="0.046"
- id="ellipse482"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.4180002"
- cy="6.9219999"
- rx="0.14300001"
- ry="0.046"
- id="ellipse484"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="4.4180002"
- cy="6.9219999"
- rx="0.14300001"
- ry="0.046"
- id="ellipse486"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <polygon
- points="8.113,6.536 8.063,6.557 7.91,6.938 7.91,7.128 7.987,7.192 9.103,7.192 9.179,7.128 9.179,6.938 9.027,6.557 8.976,6.536 8.113,6.536 "
- id="polygon488"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="8.113,6.536 8.063,6.557 7.91,6.938 7.91,7.128 7.987,7.192 9.103,7.192 9.179,7.128 9.179,6.938 9.027,6.557 8.976,6.536 8.113,6.536 "
- id="polygon490"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.936,6.874 L 7.987,6.896 L 9.103,6.896 L 9.154,6.874"
- id="path492"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 9.103,6.896 L 9.179,6.938"
- id="path494"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.91,6.938 L 7.987,6.896"
- id="path496"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="8.266,6.134 8.24,6.642 8.849,6.642 8.824,6.134 8.266,6.134 "
- id="polygon498"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="8.266,6.134 8.24,6.642 8.849,6.642 8.824,6.134 8.266,6.134 "
- id="polygon500"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="8.164,6.642 8.113,6.79 8.976,6.79 8.925,6.642 8.164,6.642 "
- id="polygon502"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="8.164,6.642 8.113,6.79 8.976,6.79 8.925,6.642 8.164,6.642 "
- id="polygon504"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="8.1639996"
- cy="6.9699998"
- rx="0.013"
- ry="0.013"
- id="ellipse506"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.1639996"
- cy="6.9699998"
- rx="0.013"
- ry="0.013"
- id="ellipse508"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.2910004"
- cy="6.9699998"
- rx="0.013"
- ry="0.013"
- id="ellipse510"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.2910004"
- cy="6.9699998"
- rx="0.013"
- ry="0.013"
- id="ellipse512"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.4180002"
- cy="6.9699998"
- rx="0.013"
- ry="0.013"
- id="ellipse514"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.4180002"
- cy="6.9699998"
- rx="0.013"
- ry="0.013"
- id="ellipse516"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.1639996"
- cy="7.0229998"
- rx="0.013"
- ry="0.013"
- id="ellipse518"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.1639996"
- cy="7.0229998"
- rx="0.013"
- ry="0.013"
- id="ellipse520"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.2910004"
- cy="7.0229998"
- rx="0.013"
- ry="0.013"
- id="ellipse522"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.2910004"
- cy="7.0229998"
- rx="0.013"
- ry="0.013"
- id="ellipse524"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.4180002"
- cy="7.0229998"
- rx="0.013"
- ry="0.013"
- id="ellipse526"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.4180002"
- cy="7.0229998"
- rx="0.013"
- ry="0.013"
- id="ellipse528"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.1639996"
- cy="7.0749998"
- rx="0.013"
- ry="0.013"
- id="ellipse530"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.1639996"
- cy="7.0749998"
- rx="0.013"
- ry="0.013"
- id="ellipse532"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.2910004"
- cy="7.0749998"
- rx="0.013"
- ry="0.013"
- id="ellipse534"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.2910004"
- cy="7.0749998"
- rx="0.013"
- ry="0.013"
- id="ellipse536"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.4180002"
- cy="7.0749998"
- rx="0.013"
- ry="0.013"
- id="ellipse538"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.4180002"
- cy="7.0749998"
- rx="0.013"
- ry="0.013"
- id="ellipse540"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.1639996"
- cy="7.1279998"
- rx="0.013"
- ry="0.013"
- id="ellipse542"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.1639996"
- cy="7.1279998"
- rx="0.013"
- ry="0.013"
- id="ellipse544"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.2910004"
- cy="7.1279998"
- rx="0.013"
- ry="0.013"
- id="ellipse546"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.2910004"
- cy="7.1279998"
- rx="0.013"
- ry="0.013"
- id="ellipse548"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.4180002"
- cy="7.1279998"
- rx="0.013"
- ry="0.013"
- id="ellipse550"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="8.4180002"
- cy="7.1279998"
- rx="0.013"
- ry="0.013"
- id="ellipse552"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.5450001"
- cy="6.98"
- rx="0.15899999"
- ry="0.050999999"
- id="ellipse554"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="8.5450001"
- cy="6.98"
- rx="0.15899999"
- ry="0.050999999"
- id="ellipse556"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="8.8620005"
- cy="6.98"
- rx="0.15899999"
- ry="0.050999999"
- id="ellipse558"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="8.8620005"
- cy="6.98"
- rx="0.15899999"
- ry="0.050999999"
- id="ellipse560"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <text
- x="3.9879999"
- y="1.613"
- id="text562"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: BILLMORE</text>
- <text
- x="1.056"
- y="5.6669998"
- id="text564"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.1.0/24</text>
- <text
- x="9.4580002"
- y="5.6199999"
- id="text566"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.2.0/24</text>
- <text
- x="4.4000001"
- y="5.6009998"
- id="text568"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.10</text>
- <text
- x="4.4390001"
- y="5.0139999"
- id="text570"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.11</text>
- <text
- x="8.0030003"
- y="5.5640001"
- id="text572"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.10</text>
- <text
- x="7.2420001"
- y="4.927"
- id="text574"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">.1</text>
- <text
- x="9.7089996"
- y="6.026"
- id="text576"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">IP via DHCP</text>
- <text
- x="3.9430001"
- y="7.6009998"
- id="text578"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj6</text>
- <text
- x="8.382"
- y="7.6389999"
- id="text580"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">qms</text>
- <text
- x="6.0440001"
- y="2.602"
- id="text582"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="5.967"
- y="3.0020001"
- id="text584"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">SLEETH</text>
- <text
- x="0.69599998"
- y="2.615"
- id="text586"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
- <text
- x="9.6929998"
- y="2.566"
- id="text588"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
- <text
- x="0.63999999"
- y="7.7909999"
- id="text590"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">20 Users</text>
- <text
- x="10.799"
- y="7.8039999"
- id="text592"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">32 Users</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="14.175cm"
- height="7.1500001cm"
- viewBox="4.175 2.15 18.35 9.3"
- id="svg2">
- <defs
- id="defs47" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="6.1750002"
- height="2.825"
- x="12.1"
- y="2.2"
- id="rect8"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="6.1750002"
- height="2.825"
- x="12.1"
- y="2.2"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="5.4169998"
- y="5.5999999"
- id="text12"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="14.296"
- y="3.0250001"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
- <text
- x="13.676"
- y="3.825"
- id="text16"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
- <text
- x="13.84"
- y="4.625"
- id="text18"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Directory A</text>
- <line
- x1="9"
- y1="5.3790002"
- x2="10.9"
- y2="5.3499999"
- stroke="#000000"
- stroke-width="0.100"
- id="line20"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="8.996,5.129 8.5,5.387 9.004,5.629 8.996,5.129 "
- id="polygon22"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="6.1750002"
- height="2.605"
- x="12.125"
- y="6.52"
- id="rect24"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="6.1750002"
- height="2.605"
- x="12.125"
- y="6.52"
- id="rect26"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="14.575"
- y="7.25"
- id="text28"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">slave</text>
- <text
- x="13.776"
- y="8.0500002"
- id="text30"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
- <text
- x="13.941"
- y="8.8500004"
- id="text32"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Directory B</text>
- <line
- x1="11.55"
- y1="3.618"
- x2="10.925"
- y2="3.625"
- stroke="#000000"
- stroke-width="0.100"
- id="line34"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.553,3.868 12.05,3.613 11.547,3.368 11.553,3.868 "
- id="polygon36"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="10.95"
- y1="3.575"
- x2="10.925"
- y2="7.8499999"
- stroke="#000000"
- stroke-width="0.100"
- id="line38"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.575"
- y1="7.8239999"
- x2="10.95"
- y2="7.8249998"
- stroke="#000000"
- stroke-width="0.100"
- id="line40"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.576,8.074 12.075,7.823 11.574,7.574 11.576,8.074 "
- id="polygon42"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="14.331"
- y="5.9749999"
- id="text44"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">additive</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="13.05cm"
- height="7.987cm"
- viewBox="4.175 2.9 17.225 10.887"
- id="svg2">
- <defs
- id="defs51" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.1750002"
- height="1.9"
- x="12"
- y="2.95"
- id="rect8"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.1750002"
- height="1.9"
- x="12"
- y="2.95"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="5.4169998"
- y="5.5500002"
- id="text12"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="13.846"
- y="3.7249999"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
- <text
- x="13.226"
- y="4.5250001"
- id="text16"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
- <line
- x1="9"
- y1="5.3790002"
- x2="10.9"
- y2="5.3499999"
- stroke="#000000"
- stroke-width="0.100"
- id="line18"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="8.996,5.129 8.5,5.387 9.004,5.629 8.996,5.129 "
- id="polygon20"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="5.1750002"
- height="1.9"
- x="11.998"
- y="5.9450002"
- id="rect22"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.1750002"
- height="1.9"
- x="11.998"
- y="5.9450002"
- id="rect24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="14.15"
- y="6.7249999"
- id="text26"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">slave</text>
- <text
- x="13.351"
- y="7.5250001"
- id="text28"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
- <line
- x1="11.45"
- y1="3.9119999"
- x2="10.9"
- y2="3.925"
- stroke="#000000"
- stroke-width="0.100"
- id="line30"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.456,4.162 11.95,3.901 11.444,3.663 11.456,4.162 "
- id="polygon32"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="10.925"
- y1="3.925"
- x2="10.95"
- y2="6.9499998"
- stroke="#000000"
- stroke-width="0.100"
- id="line34"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.448"
- y1="6.9099998"
- x2="10.9"
- y2="6.9250002"
- stroke="#000000"
- stroke-width="0.100"
- id="line36"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.455,7.16 11.948,6.896 11.441,6.66 11.455,7.16 "
- id="polygon38"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="13.659"
- y="5.5749998"
- id="text40"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">additive</text>
- <text
- x="8.6809998"
- y="8.75"
- id="text42"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">The LDAP backend consists of a</text>
- <text
- x="7.9250002"
- y="9.3500004"
- id="text44"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master and a slave for the same database.</text>
- <text
- x="8.7819996"
- y="9.9499998"
- id="text46"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">This is a broken implementation</text>
- <text
- x="9.0249996"
- y="10.55"
- id="text48"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">- accounts will be duplicated.</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="13.098cm"
- height="4.9000001cm"
- viewBox="4.175 2.9 17.273 7.8"
- id="svg2">
- <defs
- id="defs41" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.1750002"
- height="1.9"
- x="12"
- y="2.95"
- id="rect8"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.1750002"
- height="1.9"
- x="12"
- y="2.95"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="5.4169998"
- y="5.5500002"
- id="text12"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="13.846"
- y="3.7249999"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
- <text
- x="13.226"
- y="4.5250001"
- id="text16"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
- <line
- x1="8.9820004"
- y1="4.875"
- x2="11.518"
- y2="3.813"
- stroke="#000000"
- stroke-width="0.100"
- id="line18"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="8.886,4.644 8.521,5.068 9.079,5.106 8.886,4.644 "
- id="polygon20"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="11.614,4.043 11.979,3.619 11.421,3.582 11.614,4.043 "
- id="polygon22"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="5.1750002"
- height="1.9"
- x="12.047"
- y="5.7449999"
- id="rect24"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.1750002"
- height="1.9"
- x="12.047"
- y="5.7449999"
- id="rect26"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="14.1"
- y="6.5500002"
- id="text28"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">slave</text>
- <text
- x="13.301"
- y="7.3499999"
- id="text30"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
- <line
- x1="8.993"
- y1="5.8610001"
- x2="11.43"
- y2="6.7340002"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.10,0.10"
- id="line32"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <polygon
- points="9.077,5.625 8.522,5.692 8.908,6.096 9.077,5.625 "
- id="polygon34"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="11.345,6.97 11.9,6.903 11.514,6.499 11.345,6.97 "
- id="polygon36"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="10.245"
- y="6"
- id="text38"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">fail-over</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="12.75cm"
- height="2.075cm"
- viewBox="4.175 4.425 16.925 6.5"
- id="svg2">
- <defs
- id="defs25" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.2249999"
- height="1.825"
- x="4.2249999"
- y="4.4749999"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.1750002"
- height="1.9"
- x="11.7"
- y="4.4749999"
- id="rect8"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.1750002"
- height="1.9"
- x="11.7"
- y="4.4749999"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="5.4169998"
- y="5.5500002"
- id="text12"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="13.621"
- y="5.25"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">master</text>
- <text
- x="13.001"
- y="6.0500002"
- id="text16"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP server</text>
- <line
- x1="9"
- y1="5.3899999"
- x2="11.05"
- y2="5.3979998"
- stroke="#000000"
- stroke-width="0.100"
- id="line18"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="9.001,5.14 8.5,5.388 8.999,5.64 9.001,5.14 "
- id="polygon20"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="11.049,5.648 11.55,5.4 11.051,5.148 11.049,5.648 "
- id="polygon22"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="16.389cm"
- height="11.635cm"
- viewBox="3.227 3.533 19.617 15.168"
- id="svg2">
- <defs
- id="defs221" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.746,10.964 4.746,12.225 18.667,12.225 18.667,11.050 "
- id="polyline4"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.0599999"
- height="4.8070002"
- x="3.648"
- y="5.744"
- id="rect6"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="2.0599999"
- height="4.8070002"
- x="3.648"
- y="5.744"
- id="rect8"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.648"
- height="0.54900002"
- x="3.8540001"
- y="6.033"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.648"
- height="0.54900002"
- x="3.8540001"
- y="6.5819998"
- id="rect12"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.648"
- height="0.54900002"
- x="3.8540001"
- y="7.132"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.648"
- height="0.54900002"
- x="3.8540001"
- y="7.6810002"
- id="rect16"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.03"
- height="0.33000001"
- x="3.8540001"
- y="8.3400002"
- id="rect18"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="5.3990002"
- cy="8.3950005"
- rx="0.071999997"
- ry="0.071999997"
- id="ellipse20"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="5.3990002"
- cy="8.3950005"
- rx="0.071999997"
- ry="0.071999997"
- id="ellipse22"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="5.3990002"
- cy="8.6149998"
- rx="0.071999997"
- ry="0.071999997"
- id="ellipse24"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="5.3990002"
- cy="8.6149998"
- rx="0.071999997"
- ry="0.071999997"
- id="ellipse26"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.24699999"
- height="0.22"
- x="4.987"
- y="8.4499998"
- id="rect28"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.24699999"
- height="0.22"
- x="4.987"
- y="8.4499998"
- id="rect30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 3.991,9.109 L 3.991,10.311"
- id="path32"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 4.334,9.109 L 4.334,10.311"
- id="path34"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 4.678,9.109 L 4.678,10.311"
- id="path36"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 5.021,9.109 L 5.021,10.311"
- id="path38"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 5.364,9.109 L 5.364,10.311"
- id="path40"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 5.708,9.109 L 5.708,10.311"
- id="path42"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="3.236,10.964 3.648,10.14 3.648,10.552 5.708,10.552 5.708,10.14 6.257,10.964 3.236,10.964 "
- id="polygon44"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="3.236,10.964 3.648,10.14 3.648,10.552 5.708,10.552 5.708,10.14 6.257,10.964 3.236,10.964 "
- id="polygon46"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.8"
- height="5.4000001"
- x="17.767"
- y="5.6500001"
- id="rect48"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.8"
- height="5.4000001"
- x="17.767"
- y="5.6500001"
- id="rect50"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.8"
- height="5.4000001"
- x="17.767"
- y="5.6500001"
- id="rect52"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.4400001"
- height="2.1600001"
- x="17.947001"
- y="5.8299999"
- id="rect54"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.4400001"
- height="2.1600001"
- x="17.947001"
- y="5.8299999"
- id="rect56"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.4400001"
- height="2.1600001"
- x="17.947001"
- y="5.8299999"
- id="rect58"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.947001"
- y1="6.1900001"
- x2="19.386999"
- y2="6.1900001"
- stroke="#000000"
- stroke-width="0.010"
- id="line60"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.386999"
- y1="6.5500002"
- x2="17.947001"
- y2="6.5500002"
- stroke="#000000"
- stroke-width="0.010"
- id="line62"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.947001"
- y1="6.9099998"
- x2="19.386999"
- y2="6.9099998"
- stroke="#000000"
- stroke-width="0.010"
- id="line64"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.947001"
- y1="7.27"
- x2="19.386999"
- y2="7.27"
- stroke="#000000"
- stroke-width="0.010"
- id="line66"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.386999"
- y1="7.6300001"
- x2="17.947001"
- y2="7.6300001"
- stroke="#000000"
- stroke-width="0.010"
- id="line68"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.99000001"
- height="0.54000002"
- x="17.947001"
- y="8.1700001"
- id="rect70"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.99000001"
- height="0.54000002"
- x="17.947001"
- y="8.1700001"
- id="rect72"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.99000001"
- height="0.54000002"
- x="17.947001"
- y="8.1700001"
- id="rect74"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.767"
- y1="9.0699997"
- x2="19.566999"
- y2="9.0699997"
- stroke="#000000"
- stroke-width="0.010"
- id="line76"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="18.577"
- y="9.25"
- id="rect78"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="18.577"
- y="9.25"
- id="rect80"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="18.577"
- y="9.25"
- id="rect82"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="18.937"
- y="9.25"
- id="rect84"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="18.937"
- y="9.25"
- id="rect86"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="18.937"
- y="9.25"
- id="rect88"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="19.297001"
- y="9.25"
- id="rect90"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="19.297001"
- y="9.25"
- id="rect92"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.090000004"
- height="0.090000004"
- x="19.297001"
- y="9.25"
- id="rect94"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.18000001"
- height="0.18000001"
- x="19.207001"
- y="8.71"
- id="rect96"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.18000001"
- height="0.18000001"
- x="19.207001"
- y="8.71"
- id="rect98"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.18000001"
- height="0.18000001"
- x="19.207001"
- y="8.71"
- id="rect100"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.947001"
- y1="8.4399996"
- x2="18.937"
- y2="8.4399996"
- stroke="#000000"
- stroke-width="0.010"
- id="line102"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.27000001"
- height="0.27000001"
- x="17.947001"
- y="9.1599998"
- id="rect104"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.27000001"
- height="0.27000001"
- x="17.947001"
- y="9.1599998"
- id="rect106"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.27000001"
- height="0.27000001"
- x="17.947001"
- y="9.1599998"
- id="rect108"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.26"
- height="0.090000004"
- x="18.037001"
- y="7.7199998"
- id="rect110"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.26"
- height="0.090000004"
- x="18.037001"
- y="7.7199998"
- id="rect112"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.26"
- height="0.090000004"
- x="18.037001"
- y="7.7199998"
- id="rect114"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="18.037001"
- y1="8.2600002"
- x2="18.847"
- y2="8.2600002"
- stroke="#000000"
- stroke-width="0.010"
- id="line116"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="18.847"
- y1="8.3500004"
- x2="18.757"
- y2="8.3500004"
- stroke="#000000"
- stroke-width="0.010"
- id="line118"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="18.037001"
- y1="8.3500004"
- x2="18.127001"
- y2="8.3500004"
- stroke="#000000"
- stroke-width="0.010"
- id="line120"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.44999999"
- height="0.090000004"
- x="18.216999"
- y="8.2600002"
- id="rect122"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.44999999"
- height="0.090000004"
- x="18.216999"
- y="8.2600002"
- id="rect124"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.44999999"
- height="0.090000004"
- x="18.216999"
- y="8.2600002"
- id="rect126"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="18.037001"
- y1="7.9000001"
- x2="18.127001"
- y2="7.9000001"
- stroke="#000000"
- stroke-width="0.010"
- id="line128"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="18.216999"
- y1="7.9000001"
- x2="18.306999"
- y2="7.9000001"
- stroke="#000000"
- stroke-width="0.010"
- id="line130"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.117001"
- y1="7.9000001"
- x2="19.297001"
- y2="7.9000001"
- stroke="#000000"
- stroke-width="0.010"
- id="line132"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.857"
- y1="10.96"
- x2="19.476999"
- y2="10.96"
- stroke="#000000"
- stroke-width="0.010"
- id="line134"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.476999"
- y1="10.87"
- x2="17.857"
- y2="10.87"
- stroke="#000000"
- stroke-width="0.010"
- id="line136"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.857"
- y1="10.78"
- x2="19.476999"
- y2="10.78"
- stroke="#000000"
- stroke-width="0.010"
- id="line138"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.476999"
- y1="10.69"
- x2="17.857"
- y2="10.69"
- stroke="#000000"
- stroke-width="0.010"
- id="line140"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.857"
- y1="10.6"
- x2="19.476999"
- y2="10.6"
- stroke="#000000"
- stroke-width="0.010"
- id="line142"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.476999"
- y1="10.51"
- x2="17.857"
- y2="10.51"
- stroke="#000000"
- stroke-width="0.010"
- id="line144"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.857"
- y1="10.42"
- x2="19.476999"
- y2="10.42"
- stroke="#000000"
- stroke-width="0.010"
- id="line146"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.476999"
- y1="10.33"
- x2="17.857"
- y2="10.33"
- stroke="#000000"
- stroke-width="0.010"
- id="line148"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.857"
- y1="10.24"
- x2="19.476999"
- y2="10.24"
- stroke="#000000"
- stroke-width="0.010"
- id="line150"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.476999"
- y1="10.15"
- x2="17.857"
- y2="10.15"
- stroke="#000000"
- stroke-width="0.010"
- id="line152"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.857"
- y1="10.06"
- x2="19.476999"
- y2="10.06"
- stroke="#000000"
- stroke-width="0.010"
- id="line154"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.476999"
- y1="9.9700003"
- x2="17.857"
- y2="9.9700003"
- stroke="#000000"
- stroke-width="0.010"
- id="line156"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.857"
- y1="9.8800001"
- x2="19.476999"
- y2="9.8800001"
- stroke="#000000"
- stroke-width="0.010"
- id="line158"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.476999"
- y1="9.79"
- x2="17.857"
- y2="9.79"
- stroke="#000000"
- stroke-width="0.010"
- id="line160"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="2.7190001"
- height="2.3989999"
- x="6.5500002"
- y="6.1869998"
- id="rect162"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="7.9089999"
- cy="8.585"
- rx="1.359"
- ry="0.40000001"
- id="ellipse164"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="7.9089999"
- cy="6.1869998"
- rx="1.359"
- ry="0.40000001"
- id="ellipse166"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="7.9089999"
- cy="6.1869998"
- rx="1.359"
- ry="0.40000001"
- id="ellipse168"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 9.269,6.187 L 9.269,8.585 C 9.269,8.806 8.66,8.985 7.909,8.985 C 7.159,8.985 6.55,8.806 6.55,8.585 L 6.55,6.187"
- id="path170"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.7190001"
- height="2.3989999"
- x="14.112"
- y="6.1999998"
- id="rect172"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="15.472"
- cy="8.599"
- rx="1.359"
- ry="0.40000001"
- id="ellipse174"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="15.472"
- cy="6.1999998"
- rx="1.359"
- ry="0.40000001"
- id="ellipse176"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="15.472"
- cy="6.1999998"
- rx="1.359"
- ry="0.40000001"
- id="ellipse178"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 16.831,6.2 L 16.831,8.599 C 16.831,8.82 16.223,8.999 15.472,8.999 C 14.721,8.999 14.112,8.82 14.112,8.599 L 14.112,6.2"
- id="path180"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.7249999"
- y1="7.3499999"
- x2="6.5250001"
- y2="7.3499999"
- stroke="#000000"
- stroke-width="0.100"
- id="line182"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.825001"
- y1="7.4000001"
- x2="17.75"
- y2="7.375"
- stroke="#000000"
- stroke-width="0.100"
- id="line184"
- style="stroke:#000000;stroke-width:0.1" />
- <path
- d="M 8.65,9.2 C 9.0031969,10.514524 10.174957,11.443114 11.535409,11.486614 C 12.89586,11.530113 14.124549,10.678275 14.561,9.389"
- id="path186"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="14.713,9.830 14.597,9.283 14.229,9.704 "
- id="polyline188"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="7.02"
- y="4.9749999"
- id="text190"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NT4 Registry</text>
- <text
- x="7.691"
- y="5.5749998"
- id="text192"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">SAM</text>
- <text
- x="13.871"
- y="4.9250002"
- id="text194"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba SAM</text>
- <text
- x="13.221"
- y="5.5250001"
- id="text196"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(ldapsam or tdbsam)</text>
- <text
- x="4.2259998"
- y="4.0250001"
- id="text198"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NT4</text>
- <text
- x="4.1719999"
- y="4.8249998"
- id="text200"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC</text>
- <text
- x="17.992001"
- y="4"
- id="text202"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="18.407"
- y="4.8000002"
- id="text204"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DC</text>
- <text
- x="5.8540001"
- y="13.625"
- id="text206"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">net rpc vampire</text>
- <text
- x="5.5139999"
- y="14.325"
- id="text208"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Migration migrates:</text>
- <text
- x="14.664"
- y="13.375"
- id="text210"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">User Accounts</text>
- <text
- x="14.557"
- y="14.075"
- id="text212"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain Groups</text>
- <text
- x="14.311"
- y="14.775"
- id="text214"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Machine Accounts</text>
- <line
- x1="10.725"
- y1="13.8"
- x2="12.25"
- y2="13.818"
- stroke="#000000"
- stroke-width="0.100"
- id="line216"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.247,14.068 12.75,13.824 12.253,13.568 12.247,14.068 "
- id="polygon218"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="21.725cm"
- height="12.513cm"
- viewBox="-0.013 1.735 21.712 14.247"
- id="svg2">
- <defs
- id="defs719" />
- <rect
- width="7.8249998"
- height="8.085"
- x="0.31200001"
- y="3.6170001"
- id="rect4"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 0.312,3.617 C 0.14631458,3.617 0.012,3.7513146 0.012,3.917"
- id="path6"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 8.437,3.917 C 8.437,3.7513146 8.3026854,3.617 8.137,3.617"
- id="path8"
- style="fill:#ededed;stroke:none" />
- <rect
- width="8.4250002"
- height="7.4850001"
- x="0.012"
- y="3.9170001"
- id="rect10"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 0.012,11.402 C 0.012,11.567685 0.14631458,11.702 0.312,11.702"
- id="path12"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 8.137,11.702 C 8.3026854,11.702 8.437,11.567685 8.437,11.402"
- id="path14"
- style="fill:#ededed;stroke:none" />
- <line
- x1="0.31200001"
- y1="3.6170001"
- x2="8.1370001"
- y2="3.6170001"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.31200001"
- y1="11.702"
- x2="8.1370001"
- y2="11.702"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.312,3.617 C 0.14631458,3.617 0.012,3.7513146 0.012,3.917"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 8.437,3.917 C 8.437,3.7513146 8.3026854,3.617 8.137,3.617"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.012"
- y1="3.9170001"
- x2="0.012"
- y2="11.402"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="8.4370003"
- y1="3.9170001"
- x2="8.4370003"
- y2="11.402"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.012,11.402 C 0.012,11.567685 0.14631458,11.702 0.312,11.702"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 8.137,11.702 C 8.3026854,11.702 8.437,11.567685 8.437,11.402"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="8.3249998"
- height="8.1350002"
- x="13.062"
- y="3.5420001"
- id="rect32"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 13.062,3.542 C 12.896315,3.542 12.762,3.6763146 12.762,3.842"
- id="path34"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 21.688,3.842 C 21.688,3.7622615 21.656256,3.6858034 21.599779,3.6295136 C 21.543301,3.5732239 21.466738,3.5417342 21.387,3.542"
- id="path36"
- style="fill:#ededed;stroke:none" />
- <rect
- width="8.9250002"
- height="7.5349998"
- x="12.762"
- y="3.842"
- id="rect38"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 12.762,11.377 C 12.762,11.542685 12.896315,11.677 13.062,11.677"
- id="path40"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 21.387,11.677 C 21.466738,11.677266 21.543301,11.645776 21.599779,11.589486 C 21.656256,11.533197 21.688,11.456739 21.688,11.377"
- id="path42"
- style="fill:#ededed;stroke:none" />
- <line
- x1="13.062"
- y1="3.5420001"
- x2="21.386999"
- y2="3.5420001"
- stroke="#070707"
- stroke-width="0.050"
- id="line44"
- style="stroke:#070707;stroke-width:0.05" />
- <line
- x1="13.062"
- y1="11.677"
- x2="21.386999"
- y2="11.677"
- stroke="#070707"
- stroke-width="0.050"
- id="line46"
- style="stroke:#070707;stroke-width:0.05" />
- <path
- d="M 13.062,3.542 C 12.896315,3.542 12.762,3.6763146 12.762,3.842"
- id="path48"
- style="fill:none;stroke:#070707;stroke-width:0.05" />
- <path
- d="M 21.688,3.842 C 21.688,3.7622615 21.656256,3.6858034 21.599779,3.6295136 C 21.543301,3.5732239 21.466738,3.5417342 21.387,3.542"
- id="path50"
- style="fill:none;stroke:#070707;stroke-width:0.05" />
- <line
- x1="12.762"
- y1="3.842"
- x2="12.762"
- y2="11.377"
- stroke="#070707"
- stroke-width="0.050"
- id="line52"
- style="stroke:#070707;stroke-width:0.05" />
- <line
- x1="21.688"
- y1="3.842"
- x2="21.688"
- y2="11.377"
- stroke="#070707"
- stroke-width="0.050"
- id="line54"
- style="stroke:#070707;stroke-width:0.05" />
- <path
- d="M 12.762,11.377 C 12.762,11.542685 12.896315,11.677 13.062,11.677"
- id="path56"
- style="fill:none;stroke:#070707;stroke-width:0.05" />
- <path
- d="M 21.387,11.677 C 21.466738,11.677266 21.543301,11.645776 21.599779,11.589486 C 21.656256,11.533197 21.688,11.456739 21.688,11.377"
- id="path58"
- style="fill:none;stroke:#070707;stroke-width:0.05" />
- <rect
- width="1.077"
- height="2.5120001"
- x="10.001"
- y="5.0110002"
- id="rect60"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.077"
- height="2.5120001"
- x="10.001"
- y="5.0110002"
- id="rect62"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="0.861"
- height="0.287"
- x="10.108"
- y="5.1620002"
- id="rect64"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.861"
- height="0.287"
- x="10.108"
- y="5.4489999"
- id="rect66"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.861"
- height="0.287"
- x="10.108"
- y="5.7360001"
- id="rect68"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.861"
- height="0.287"
- x="10.108"
- y="6.0229998"
- id="rect70"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.53799999"
- height="0.17200001"
- x="10.108"
- y="6.368"
- id="rect72"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="10.916"
- cy="6.3969998"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse74"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="10.916"
- cy="6.3969998"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse76"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="10.916"
- cy="6.5110002"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse78"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="10.916"
- cy="6.5110002"
- rx="0.037999999"
- ry="0.037999999"
- id="ellipse80"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.12899999"
- height="0.115"
- x="10.701"
- y="6.4250002"
- id="rect82"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.12899999"
- height="0.115"
- x="10.701"
- y="6.4250002"
- id="rect84"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.18,6.77 L 10.18,7.398"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.36,6.77 L 10.36,7.398"
- id="path88"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.539,6.77 L 10.539,7.398"
- id="path90"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.719,6.77 L 10.719,7.398"
- id="path92"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.898,6.77 L 10.898,7.398"
- id="path94"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 11.077,6.77 L 11.077,7.398"
- id="path96"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="9.786,7.739 10.001,7.308 10.001,7.523 11.077,7.523 11.077,7.308 11.364,7.739 9.786,7.739 "
- id="polygon98"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="9.786,7.739 10.001,7.308 10.001,7.523 11.077,7.523 11.077,7.308 11.364,7.739 9.786,7.739 "
- id="polygon100"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.423"
- y1="7.1059999"
- x2="10.025"
- y2="7.0999999"
- stroke="#000000"
- stroke-width="0.100"
- id="line102"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.687"
- y1="7.105"
- x2="2.688"
- y2="8.1049995"
- stroke="#000000"
- stroke-width="0.100"
- id="line104"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.6919999"
- y1="7.105"
- x2="2.691"
- y2="6.0669999"
- stroke="#000000"
- stroke-width="0.100"
- id="line106"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.1170001"
- y1="7.1030002"
- x2="5.1170001"
- y2="8.1029997"
- stroke="#000000"
- stroke-width="0.100"
- id="line108"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.1300001"
- y1="7.1030002"
- x2="5.1300001"
- y2="6.119"
- stroke="#000000"
- stroke-width="0.100"
- id="line110"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="7.572"
- y1="7.1020002"
- x2="7.572"
- y2="8.0959997"
- stroke="#000000"
- stroke-width="0.100"
- id="line112"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="7.566"
- y1="7.1020002"
- x2="7.5650001"
- y2="6.2249999"
- stroke="#000000"
- stroke-width="0.100"
- id="line114"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.05"
- y1="7.0749998"
- x2="20.325001"
- y2="7.0500002"
- stroke="#000000"
- stroke-width="0.100"
- id="line116"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.747"
- y1="7.0679998"
- x2="13.75"
- y2="8.125"
- stroke="#000000"
- stroke-width="0.100"
- id="line118"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.74"
- y1="7.0679998"
- x2="13.737"
- y2="6.0840001"
- stroke="#000000"
- stroke-width="0.100"
- id="line120"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.297001"
- y1="7.0609999"
- x2="16.299999"
- y2="8.0749998"
- stroke="#000000"
- stroke-width="0.100"
- id="line122"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.306999"
- y1="7.0609999"
- x2="16.305"
- y2="6.1690001"
- stroke="#000000"
- stroke-width="0.100"
- id="line124"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.896999"
- y1="7.0539999"
- x2="18.9"
- y2="8.0249996"
- stroke="#000000"
- stroke-width="0.100"
- id="line126"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.907"
- y1="7.0539999"
- x2="18.905001"
- y2="6.0939999"
- stroke="#000000"
- stroke-width="0.100"
- id="line128"
- style="stroke:#000000;stroke-width:0.1" />
- <path
- d="M 9.39,12.232 C 8.983,12.222 8.194,12.424 8.305,12.856 C 8.416,13.288 8.946,13.384 9.168,13.259 C 9.39,13.134 8.823,13.864 9.907,14.056 C 10.992,14.247 11.547,13.94 11.386,13.72 C 11.226,13.499 12.335,14.238 12.853,13.816 C 13.371,13.393 12.323,12.99 12.545,13.048 C 12.767,13.105 13.445,13.029 13.223,12.309 C 13.001,11.589 11.004,12.145 11.226,12.04 C 11.448,11.934 10.893,11.406 10.203,11.512 C 9.513,11.618 9.464,11.809 9.39,12.231 L 9.39,12.232"
- id="path130"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <path
- d="M 9.39,12.232 C 8.983,12.222 8.194,12.424 8.305,12.856 C 8.416,13.288 8.946,13.384 9.168,13.259 C 9.39,13.134 8.823,13.864 9.907,14.056 C 10.992,14.247 11.547,13.94 11.386,13.72 C 11.226,13.499 12.335,14.238 12.853,13.816 C 13.371,13.393 12.323,12.99 12.545,13.048 C 12.767,13.105 13.445,13.029 13.223,12.309 C 13.001,11.589 11.004,12.145 11.226,12.04 C 11.448,11.934 10.893,11.406 10.203,11.512 C 9.513,11.618 9.464,11.809 9.39,12.231 L 9.39,12.232"
- id="path132"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="10.353"
- y="12.927"
- id="text134"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
- <line
- x1="10.562"
- y1="11.552"
- x2="10.575"
- y2="7.7389998"
- stroke="#000000"
- stroke-width="0.100"
- id="line136"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.085"
- height="0.81300002"
- x="2.1489999"
- y="5"
- id="rect138"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="2.1489999"
- y="5"
- id="rect140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="2.266"
- y="5.118"
- id="rect142"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="2.296,5.814 2.854,5.814 2.854,5.94 2.325,5.94 2.296,5.814 "
- id="polygon144"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.296,5.814 2.854,5.814 2.854,5.94 2.325,5.94 2.296,5.814 "
- id="polygon146"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="2.854,5.814 3.087,5.814 3.057,5.94 2.854,5.94 2.854,5.814 "
- id="polygon148"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.854,5.814 3.087,5.814 3.057,5.94 2.854,5.94 2.854,5.814 "
- id="polygon150"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="2.892"
- y="5.8520002"
- id="rect152"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="2.892"
- y="5.8520002"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="2.583,5.94 2.8,5.94 2.8,6.003 2.908,6.003 2.908,6.067 2.474,6.067 2.474,6.003 2.583,6.003 2.583,5.94 "
- id="polygon156"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.583,5.94 2.8,5.94 2.8,6.003 2.908,6.003 2.908,6.067 2.474,6.067 2.474,6.003 2.583,6.003 2.583,5.94 "
- id="polygon158"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="18.337"
- y="8.0270004"
- id="rect160"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="18.337"
- y="8.0270004"
- id="rect162"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="18.455"
- y="8.1450005"
- id="rect164"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.484,8.841 19.042,8.841 19.042,8.967 18.514,8.967 18.484,8.841 "
- id="polygon166"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.484,8.841 19.042,8.841 19.042,8.967 18.514,8.967 18.484,8.841 "
- id="polygon168"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.042,8.841 19.275,8.841 19.246,8.967 19.042,8.967 19.042,8.841 "
- id="polygon170"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.042,8.841 19.275,8.841 19.246,8.967 19.042,8.967 19.042,8.841 "
- id="polygon172"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="19.08"
- y="8.8789997"
- id="rect174"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="19.08"
- y="8.8789997"
- id="rect176"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.771,8.967 18.988,8.967 18.988,9.031 19.097,9.031 19.097,9.094 18.663,9.094 18.663,9.031 18.771,9.031 18.771,8.967 "
- id="polygon178"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.771,8.967 18.988,8.967 18.988,9.031 19.097,9.031 19.097,9.094 18.663,9.094 18.663,9.031 18.771,9.031 18.771,8.967 "
- id="polygon180"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="15.737"
- y="8.0530005"
- id="rect182"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="15.737"
- y="8.0530005"
- id="rect184"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="15.855"
- y="8.1700001"
- id="rect186"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="15.884,8.866 16.442,8.866 16.442,8.992 15.914,8.992 15.884,8.866 "
- id="polygon188"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.884,8.866 16.442,8.866 16.442,8.992 15.914,8.992 15.884,8.866 "
- id="polygon190"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.442,8.866 16.675,8.866 16.646,8.992 16.442,8.992 16.442,8.866 "
- id="polygon192"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.442,8.866 16.675,8.866 16.646,8.992 16.442,8.992 16.442,8.866 "
- id="polygon194"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="16.48"
- y="8.9040003"
- id="rect196"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="16.48"
- y="8.9040003"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.171,8.992 16.388,8.992 16.388,9.056 16.497,9.056 16.497,9.119 16.063,9.119 16.063,9.056 16.171,9.056 16.171,8.992 "
- id="polygon200"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.171,8.992 16.388,8.992 16.388,9.056 16.497,9.056 16.497,9.119 16.063,9.119 16.063,9.056 16.171,9.056 16.171,8.992 "
- id="polygon202"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="18.362"
- y="5.027"
- id="rect204"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="18.362"
- y="5.027"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="18.48"
- y="5.145"
- id="rect208"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.509,5.841 19.067,5.841 19.067,5.967 18.539,5.967 18.509,5.841 "
- id="polygon210"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.509,5.841 19.067,5.841 19.067,5.967 18.539,5.967 18.509,5.841 "
- id="polygon212"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.067,5.841 19.3,5.841 19.271,5.967 19.067,5.967 19.067,5.841 "
- id="polygon214"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.067,5.841 19.3,5.841 19.271,5.967 19.067,5.967 19.067,5.841 "
- id="polygon216"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="19.105"
- y="5.8790002"
- id="rect218"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="19.105"
- y="5.8790002"
- id="rect220"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.796,5.967 19.013,5.967 19.013,6.031 19.122,6.031 19.122,6.094 18.688,6.094 18.688,6.031 18.796,6.031 18.796,5.967 "
- id="polygon222"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.796,5.967 19.013,5.967 19.013,6.031 19.122,6.031 19.122,6.094 18.688,6.094 18.688,6.031 18.796,6.031 18.796,5.967 "
- id="polygon224"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="15.762"
- y="5.1030002"
- id="rect226"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="15.762"
- y="5.1030002"
- id="rect228"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="15.88"
- y="5.2199998"
- id="rect230"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="15.909,5.916 16.467,5.916 16.467,6.042 15.939,6.042 15.909,5.916 "
- id="polygon232"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.909,5.916 16.467,5.916 16.467,6.042 15.939,6.042 15.909,5.916 "
- id="polygon234"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.467,5.916 16.7,5.916 16.671,6.042 16.467,6.042 16.467,5.916 "
- id="polygon236"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.467,5.916 16.7,5.916 16.671,6.042 16.467,6.042 16.467,5.916 "
- id="polygon238"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="16.504999"
- y="5.954"
- id="rect240"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="16.504999"
- y="5.954"
- id="rect242"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.196,6.042 16.413,6.042 16.413,6.106 16.522,6.106 16.522,6.169 16.088,6.169 16.088,6.106 16.196,6.106 16.196,6.042 "
- id="polygon244"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.196,6.042 16.413,6.042 16.413,6.106 16.522,6.106 16.522,6.169 16.088,6.169 16.088,6.106 16.196,6.106 16.196,6.042 "
- id="polygon246"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="4.5869999"
- y="5.053"
- id="rect248"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="4.5869999"
- y="5.053"
- id="rect250"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="4.7049999"
- y="5.1700001"
- id="rect252"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="4.734,5.866 5.292,5.866 5.292,5.992 4.764,5.992 4.734,5.866 "
- id="polygon254"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.734,5.866 5.292,5.866 5.292,5.992 4.764,5.992 4.734,5.866 "
- id="polygon256"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="5.292,5.866 5.525,5.866 5.496,5.992 5.292,5.992 5.292,5.866 "
- id="polygon258"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.292,5.866 5.525,5.866 5.496,5.992 5.292,5.992 5.292,5.866 "
- id="polygon260"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="5.3299999"
- y="5.9039998"
- id="rect262"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="5.3299999"
- y="5.9039998"
- id="rect264"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="5.021,5.992 5.238,5.992 5.238,6.056 5.347,6.056 5.347,6.119 4.913,6.119 4.913,6.056 5.021,6.056 5.021,5.992 "
- id="polygon266"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.021,5.992 5.238,5.992 5.238,6.056 5.347,6.056 5.347,6.119 4.913,6.119 4.913,6.056 5.021,6.056 5.021,5.992 "
- id="polygon268"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="4.5619998"
- y="8.0530005"
- id="rect270"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="4.5619998"
- y="8.0530005"
- id="rect272"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="4.6799998"
- y="8.1700001"
- id="rect274"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="4.709,8.866 5.267,8.866 5.267,8.992 4.739,8.992 4.709,8.866 "
- id="polygon276"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.709,8.866 5.267,8.866 5.267,8.992 4.739,8.992 4.709,8.866 "
- id="polygon278"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="5.267,8.866 5.5,8.866 5.471,8.992 5.267,8.992 5.267,8.866 "
- id="polygon280"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.267,8.866 5.5,8.866 5.471,8.992 5.267,8.992 5.267,8.866 "
- id="polygon282"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="5.3049998"
- y="8.9040003"
- id="rect284"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="5.3049998"
- y="8.9040003"
- id="rect286"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="4.996,8.992 5.213,8.992 5.213,9.056 5.322,9.056 5.322,9.119 4.888,9.119 4.888,9.056 4.996,9.056 4.996,8.992 "
- id="polygon288"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.996,8.992 5.213,8.992 5.213,9.056 5.322,9.056 5.322,9.119 4.888,9.119 4.888,9.056 4.996,9.056 4.996,8.992 "
- id="polygon290"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="2.1619999"
- y="8.1020002"
- id="rect292"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="2.1619999"
- y="8.1020002"
- id="rect294"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="2.28"
- y="8.2200003"
- id="rect296"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="2.309,8.916 2.867,8.916 2.867,9.042 2.339,9.042 2.309,8.916 "
- id="polygon298"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.309,8.916 2.867,8.916 2.867,9.042 2.339,9.042 2.309,8.916 "
- id="polygon300"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="2.867,8.916 3.1,8.916 3.071,9.042 2.867,9.042 2.867,8.916 "
- id="polygon302"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.867,8.916 3.1,8.916 3.071,9.042 2.867,9.042 2.867,8.916 "
- id="polygon304"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="2.905"
- y="8.9540005"
- id="rect306"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="2.905"
- y="8.9540005"
- id="rect308"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="2.596,9.042 2.813,9.042 2.813,9.106 2.922,9.106 2.922,9.169 2.488,9.169 2.488,9.106 2.596,9.106 2.596,9.042 "
- id="polygon310"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="2.596,9.042 2.813,9.042 2.813,9.106 2.922,9.106 2.922,9.169 2.488,9.169 2.488,9.106 2.596,9.106 2.596,9.042 "
- id="polygon312"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="20.287001"
- y="6.5770001"
- id="rect314"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="20.287001"
- y="6.5770001"
- id="rect316"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="20.405001"
- y="6.6950002"
- id="rect318"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="20.434,7.391 20.992,7.391 20.992,7.517 20.464,7.517 20.434,7.391 "
- id="polygon320"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.434,7.391 20.992,7.391 20.992,7.517 20.464,7.517 20.434,7.391 "
- id="polygon322"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.992,7.391 21.225,7.391 21.196,7.517 20.992,7.517 20.992,7.391 "
- id="polygon324"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.992,7.391 21.225,7.391 21.196,7.517 20.992,7.517 20.992,7.391 "
- id="polygon326"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="21.030001"
- y="7.4289999"
- id="rect328"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="21.030001"
- y="7.4289999"
- id="rect330"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="20.721,7.517 20.938,7.517 20.938,7.581 21.047,7.581 21.047,7.644 20.613,7.644 20.613,7.581 20.721,7.581 20.721,7.517 "
- id="polygon332"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.721,7.517 20.938,7.517 20.938,7.581 21.047,7.581 21.047,7.644 20.613,7.644 20.613,7.581 20.721,7.581 20.721,7.517 "
- id="polygon334"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.085"
- height="0.81300002"
- x="0.31200001"
- y="6.6030002"
- id="rect336"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.085"
- height="0.81300002"
- x="0.31200001"
- y="6.6030002"
- id="rect338"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.85000002"
- height="0.56"
- x="0.43000001"
- y="6.7199998"
- id="rect340"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="0.459,7.416 1.017,7.416 1.017,7.542 0.489,7.542 0.459,7.416 "
- id="polygon342"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="0.459,7.416 1.017,7.416 1.017,7.542 0.489,7.542 0.459,7.416 "
- id="polygon344"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="1.017,7.416 1.25,7.416 1.221,7.542 1.017,7.542 1.017,7.416 "
- id="polygon346"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="1.017,7.416 1.25,7.416 1.221,7.542 1.017,7.542 1.017,7.416 "
- id="polygon348"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="1.0549999"
- y="7.454"
- id="rect350"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050999999"
- height="0.050999999"
- x="1.0549999"
- y="7.454"
- id="rect352"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="0.746,7.542 0.963,7.542 0.963,7.606 1.072,7.606 1.072,7.669 0.638,7.669 0.638,7.606 0.746,7.606 0.746,7.542 "
- id="polygon354"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="0.746,7.542 0.963,7.542 0.963,7.606 1.072,7.606 1.072,7.669 0.638,7.669 0.638,7.606 0.746,7.606 0.746,7.542 "
- id="polygon356"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="7.201,5.672 7.159,5.69 7.03,6.011 7.03,6.171 7.094,6.225 8.036,6.225 8.1,6.171 8.1,6.011 7.972,5.69 7.929,5.672 7.201,5.672 "
- id="polygon358"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="7.201,5.672 7.159,5.69 7.03,6.011 7.03,6.171 7.094,6.225 8.036,6.225 8.1,6.171 8.1,6.011 7.972,5.69 7.929,5.672 7.201,5.672 "
- id="polygon360"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.052,5.957 L 7.094,5.975 L 8.036,5.975 L 8.079,5.957"
- id="path362"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 8.036,5.975 L 8.1,6.011"
- id="path364"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.03,6.011 L 7.094,5.975"
- id="path366"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="7.33,5.333 7.308,5.761 7.822,5.761 7.801,5.333 7.33,5.333 "
- id="polygon368"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="7.33,5.333 7.308,5.761 7.822,5.761 7.801,5.333 7.33,5.333 "
- id="polygon370"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="7.244,5.761 7.201,5.886 7.929,5.886 7.886,5.761 7.244,5.761 "
- id="polygon372"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="7.244,5.761 7.201,5.886 7.929,5.886 7.886,5.761 7.244,5.761 "
- id="polygon374"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="7.244"
- cy="6.0380001"
- rx="0.011"
- ry="0.011"
- id="ellipse376"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.244"
- cy="6.0380001"
- rx="0.011"
- ry="0.011"
- id="ellipse378"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.3509998"
- cy="6.0380001"
- rx="0.011"
- ry="0.011"
- id="ellipse380"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.3509998"
- cy="6.0380001"
- rx="0.011"
- ry="0.011"
- id="ellipse382"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4580002"
- cy="6.0380001"
- rx="0.011"
- ry="0.011"
- id="ellipse384"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4580002"
- cy="6.0380001"
- rx="0.011"
- ry="0.011"
- id="ellipse386"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.244"
- cy="6.0819998"
- rx="0.011"
- ry="0.011"
- id="ellipse388"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.244"
- cy="6.0819998"
- rx="0.011"
- ry="0.011"
- id="ellipse390"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.3509998"
- cy="6.0819998"
- rx="0.011"
- ry="0.011"
- id="ellipse392"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.3509998"
- cy="6.0819998"
- rx="0.011"
- ry="0.011"
- id="ellipse394"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4580002"
- cy="6.0819998"
- rx="0.011"
- ry="0.011"
- id="ellipse396"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4580002"
- cy="6.0819998"
- rx="0.011"
- ry="0.011"
- id="ellipse398"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.244"
- cy="6.1269999"
- rx="0.011"
- ry="0.011"
- id="ellipse400"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.244"
- cy="6.1269999"
- rx="0.011"
- ry="0.011"
- id="ellipse402"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.3509998"
- cy="6.1269999"
- rx="0.011"
- ry="0.011"
- id="ellipse404"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.3509998"
- cy="6.1269999"
- rx="0.011"
- ry="0.011"
- id="ellipse406"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4580002"
- cy="6.1269999"
- rx="0.011"
- ry="0.011"
- id="ellipse408"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4580002"
- cy="6.1269999"
- rx="0.011"
- ry="0.011"
- id="ellipse410"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.244"
- cy="6.171"
- rx="0.011"
- ry="0.011"
- id="ellipse412"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.244"
- cy="6.171"
- rx="0.011"
- ry="0.011"
- id="ellipse414"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.3509998"
- cy="6.171"
- rx="0.011"
- ry="0.011"
- id="ellipse416"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.3509998"
- cy="6.171"
- rx="0.011"
- ry="0.011"
- id="ellipse418"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4580002"
- cy="6.171"
- rx="0.011"
- ry="0.011"
- id="ellipse420"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4580002"
- cy="6.171"
- rx="0.011"
- ry="0.011"
- id="ellipse422"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.5650001"
- cy="6.0469999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse424"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.5650001"
- cy="6.0469999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse426"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.8330002"
- cy="6.0469999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse428"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.8330002"
- cy="6.0469999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse430"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <polygon
- points="13.374,8.356 13.331,8.374 13.202,8.695 13.202,8.856 13.267,8.909 14.208,8.909 14.272,8.856 14.272,8.695 14.144,8.374 14.101,8.356 13.374,8.356 "
- id="polygon432"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="13.374,8.356 13.331,8.374 13.202,8.695 13.202,8.856 13.267,8.909 14.208,8.909 14.272,8.856 14.272,8.695 14.144,8.374 14.101,8.356 13.374,8.356 "
- id="polygon434"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 13.224,8.642 L 13.267,8.659 L 14.208,8.659 L 14.251,8.642"
- id="path436"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 14.208,8.659 L 14.272,8.695"
- id="path438"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 13.202,8.695 L 13.267,8.659"
- id="path440"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="13.502,8.018 13.481,8.445 13.994,8.445 13.973,8.018 13.502,8.018 "
- id="polygon442"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="13.502,8.018 13.481,8.445 13.994,8.445 13.973,8.018 13.502,8.018 "
- id="polygon444"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="13.416,8.445 13.374,8.57 14.101,8.57 14.058,8.445 13.416,8.445 "
- id="polygon446"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="13.416,8.445 13.374,8.57 14.101,8.57 14.058,8.445 13.416,8.445 "
- id="polygon448"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="13.416"
- cy="8.7220001"
- rx="0.011"
- ry="0.011"
- id="ellipse450"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="8.7220001"
- rx="0.011"
- ry="0.011"
- id="ellipse452"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="8.7220001"
- rx="0.011"
- ry="0.011"
- id="ellipse454"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="8.7220001"
- rx="0.011"
- ry="0.011"
- id="ellipse456"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="8.7220001"
- rx="0.011"
- ry="0.011"
- id="ellipse458"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="8.7220001"
- rx="0.011"
- ry="0.011"
- id="ellipse460"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.416"
- cy="8.7659998"
- rx="0.011"
- ry="0.011"
- id="ellipse462"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="8.7659998"
- rx="0.011"
- ry="0.011"
- id="ellipse464"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="8.7659998"
- rx="0.011"
- ry="0.011"
- id="ellipse466"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="8.7659998"
- rx="0.011"
- ry="0.011"
- id="ellipse468"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="8.7659998"
- rx="0.011"
- ry="0.011"
- id="ellipse470"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="8.7659998"
- rx="0.011"
- ry="0.011"
- id="ellipse472"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.416"
- cy="8.8109999"
- rx="0.011"
- ry="0.011"
- id="ellipse474"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="8.8109999"
- rx="0.011"
- ry="0.011"
- id="ellipse476"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="8.8109999"
- rx="0.011"
- ry="0.011"
- id="ellipse478"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="8.8109999"
- rx="0.011"
- ry="0.011"
- id="ellipse480"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="8.8109999"
- rx="0.011"
- ry="0.011"
- id="ellipse482"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="8.8109999"
- rx="0.011"
- ry="0.011"
- id="ellipse484"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.416"
- cy="8.8559999"
- rx="0.011"
- ry="0.011"
- id="ellipse486"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="8.8559999"
- rx="0.011"
- ry="0.011"
- id="ellipse488"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="8.8559999"
- rx="0.011"
- ry="0.011"
- id="ellipse490"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="8.8559999"
- rx="0.011"
- ry="0.011"
- id="ellipse492"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="8.8559999"
- rx="0.011"
- ry="0.011"
- id="ellipse494"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="8.8559999"
- rx="0.011"
- ry="0.011"
- id="ellipse496"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.737"
- cy="8.7309999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse498"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="13.737"
- cy="8.7309999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse500"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.005"
- cy="8.7309999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse502"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="14.005"
- cy="8.7309999"
- rx="0.134"
- ry="0.043000001"
- id="ellipse504"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <polygon
- points="7.174,8.381 7.131,8.399 7.002,8.72 7.002,8.881 7.067,8.934 8.008,8.934 8.072,8.881 8.072,8.72 7.944,8.399 7.901,8.381 7.174,8.381 "
- id="polygon506"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="7.174,8.381 7.131,8.399 7.002,8.72 7.002,8.881 7.067,8.934 8.008,8.934 8.072,8.881 8.072,8.72 7.944,8.399 7.901,8.381 7.174,8.381 "
- id="polygon508"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.024,8.667 L 7.067,8.684 L 8.008,8.684 L 8.051,8.667"
- id="path510"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 8.008,8.684 L 8.072,8.72"
- id="path512"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.002,8.72 L 7.067,8.684"
- id="path514"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="7.302,8.043 7.281,8.47 7.794,8.47 7.773,8.043 7.302,8.043 "
- id="polygon516"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="7.302,8.043 7.281,8.47 7.794,8.47 7.773,8.043 7.302,8.043 "
- id="polygon518"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="7.216,8.47 7.174,8.595 7.901,8.595 7.858,8.47 7.216,8.47 "
- id="polygon520"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="7.216,8.47 7.174,8.595 7.901,8.595 7.858,8.47 7.216,8.47 "
- id="polygon522"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="7.2160001"
- cy="8.7469997"
- rx="0.011"
- ry="0.011"
- id="ellipse524"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.2160001"
- cy="8.7469997"
- rx="0.011"
- ry="0.011"
- id="ellipse526"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.323"
- cy="8.7469997"
- rx="0.011"
- ry="0.011"
- id="ellipse528"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.323"
- cy="8.7469997"
- rx="0.011"
- ry="0.011"
- id="ellipse530"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4299998"
- cy="8.7469997"
- rx="0.011"
- ry="0.011"
- id="ellipse532"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4299998"
- cy="8.7469997"
- rx="0.011"
- ry="0.011"
- id="ellipse534"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.2160001"
- cy="8.7910004"
- rx="0.011"
- ry="0.011"
- id="ellipse536"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.2160001"
- cy="8.7910004"
- rx="0.011"
- ry="0.011"
- id="ellipse538"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.323"
- cy="8.7910004"
- rx="0.011"
- ry="0.011"
- id="ellipse540"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.323"
- cy="8.7910004"
- rx="0.011"
- ry="0.011"
- id="ellipse542"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4299998"
- cy="8.7910004"
- rx="0.011"
- ry="0.011"
- id="ellipse544"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4299998"
- cy="8.7910004"
- rx="0.011"
- ry="0.011"
- id="ellipse546"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.2160001"
- cy="8.8360004"
- rx="0.011"
- ry="0.011"
- id="ellipse548"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.2160001"
- cy="8.8360004"
- rx="0.011"
- ry="0.011"
- id="ellipse550"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.323"
- cy="8.8360004"
- rx="0.011"
- ry="0.011"
- id="ellipse552"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.323"
- cy="8.8360004"
- rx="0.011"
- ry="0.011"
- id="ellipse554"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4299998"
- cy="8.8360004"
- rx="0.011"
- ry="0.011"
- id="ellipse556"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4299998"
- cy="8.8360004"
- rx="0.011"
- ry="0.011"
- id="ellipse558"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.2160001"
- cy="8.8809996"
- rx="0.011"
- ry="0.011"
- id="ellipse560"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.2160001"
- cy="8.8809996"
- rx="0.011"
- ry="0.011"
- id="ellipse562"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.323"
- cy="8.8809996"
- rx="0.011"
- ry="0.011"
- id="ellipse564"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.323"
- cy="8.8809996"
- rx="0.011"
- ry="0.011"
- id="ellipse566"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.4299998"
- cy="8.8809996"
- rx="0.011"
- ry="0.011"
- id="ellipse568"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="7.4299998"
- cy="8.8809996"
- rx="0.011"
- ry="0.011"
- id="ellipse570"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.5370002"
- cy="8.7559996"
- rx="0.134"
- ry="0.043000001"
- id="ellipse572"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.5370002"
- cy="8.7559996"
- rx="0.134"
- ry="0.043000001"
- id="ellipse574"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.8049998"
- cy="8.7559996"
- rx="0.134"
- ry="0.043000001"
- id="ellipse576"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.8049998"
- cy="8.7559996"
- rx="0.134"
- ry="0.043000001"
- id="ellipse578"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <polygon
- points="13.374,5.531 13.331,5.549 13.202,5.87 13.202,6.031 13.267,6.084 14.208,6.084 14.272,6.031 14.272,5.87 14.144,5.549 14.101,5.531 13.374,5.531 "
- id="polygon580"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="13.374,5.531 13.331,5.549 13.202,5.87 13.202,6.031 13.267,6.084 14.208,6.084 14.272,6.031 14.272,5.87 14.144,5.549 14.101,5.531 13.374,5.531 "
- id="polygon582"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 13.224,5.817 L 13.267,5.834 L 14.208,5.834 L 14.251,5.817"
- id="path584"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 14.208,5.834 L 14.272,5.87"
- id="path586"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 13.202,5.87 L 13.267,5.834"
- id="path588"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="13.502,5.192 13.481,5.62 13.994,5.62 13.973,5.192 13.502,5.192 "
- id="polygon590"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="13.502,5.192 13.481,5.62 13.994,5.62 13.973,5.192 13.502,5.192 "
- id="polygon592"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="13.416,5.62 13.374,5.745 14.101,5.745 14.058,5.62 13.416,5.62 "
- id="polygon594"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="13.416,5.62 13.374,5.745 14.101,5.745 14.058,5.62 13.416,5.62 "
- id="polygon596"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="13.416"
- cy="5.8969998"
- rx="0.011"
- ry="0.011"
- id="ellipse598"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="5.8969998"
- rx="0.011"
- ry="0.011"
- id="ellipse600"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="5.8969998"
- rx="0.011"
- ry="0.011"
- id="ellipse602"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="5.8969998"
- rx="0.011"
- ry="0.011"
- id="ellipse604"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="5.8969998"
- rx="0.011"
- ry="0.011"
- id="ellipse606"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="5.8969998"
- rx="0.011"
- ry="0.011"
- id="ellipse608"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.416"
- cy="5.941"
- rx="0.011"
- ry="0.011"
- id="ellipse610"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="5.941"
- rx="0.011"
- ry="0.011"
- id="ellipse612"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="5.941"
- rx="0.011"
- ry="0.011"
- id="ellipse614"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="5.941"
- rx="0.011"
- ry="0.011"
- id="ellipse616"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="5.941"
- rx="0.011"
- ry="0.011"
- id="ellipse618"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="5.941"
- rx="0.011"
- ry="0.011"
- id="ellipse620"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.416"
- cy="5.9860001"
- rx="0.011"
- ry="0.011"
- id="ellipse622"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="5.9860001"
- rx="0.011"
- ry="0.011"
- id="ellipse624"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="5.9860001"
- rx="0.011"
- ry="0.011"
- id="ellipse626"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="5.9860001"
- rx="0.011"
- ry="0.011"
- id="ellipse628"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="5.9860001"
- rx="0.011"
- ry="0.011"
- id="ellipse630"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="5.9860001"
- rx="0.011"
- ry="0.011"
- id="ellipse632"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.416"
- cy="6.0310001"
- rx="0.011"
- ry="0.011"
- id="ellipse634"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.416"
- cy="6.0310001"
- rx="0.011"
- ry="0.011"
- id="ellipse636"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.523"
- cy="6.0310001"
- rx="0.011"
- ry="0.011"
- id="ellipse638"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.523"
- cy="6.0310001"
- rx="0.011"
- ry="0.011"
- id="ellipse640"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.63"
- cy="6.0310001"
- rx="0.011"
- ry="0.011"
- id="ellipse642"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="13.63"
- cy="6.0310001"
- rx="0.011"
- ry="0.011"
- id="ellipse644"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="13.737"
- cy="5.9060001"
- rx="0.134"
- ry="0.043000001"
- id="ellipse646"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="13.737"
- cy="5.9060001"
- rx="0.134"
- ry="0.043000001"
- id="ellipse648"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.005"
- cy="5.9060001"
- rx="0.134"
- ry="0.043000001"
- id="ellipse650"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="14.005"
- cy="5.9060001"
- rx="0.134"
- ry="0.043000001"
- id="ellipse652"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <text
- x="9.6599998"
- y="8.3249998"
- id="text654"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth0</text>
- <text
- x="11.456"
- y="6.7820001"
- id="text656"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth2</text>
- <text
- x="9.0799999"
- y="6.8319998"
- id="text658"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth1</text>
- <text
- x="7.1090002"
- y="4.9520001"
- id="text660"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj6a</text>
- <text
- x="13.463"
- y="4.9569998"
- id="text662"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">hplj6f</text>
- <text
- x="7.1820002"
- y="9.507"
- id="text664"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">qmsa</text>
- <text
- x="13.327"
- y="9.507"
- id="text666"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">qmsf</text>
- <text
- x="8.3570004"
- y="2.2019999"
- id="text668"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: PROMISES</text>
- <text
- x="9.9700003"
- y="3.55"
- id="text670"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="9.698"
- y="4.1500001"
- id="text672"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIAMOND</text>
- <text
- x="2.221"
- y="9.9250002"
- id="text674"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="1.8150001"
- y="10.525"
- id="text676"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.1.0/24</text>
- <text
- x="15.621"
- y="9.8520002"
- id="text678"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="15.185"
- y="10.452"
- id="text680"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">192.168.2.0/24</text>
- <rect
- width="0.62699997"
- height="0.55299997"
- x="8.7729998"
- y="4.4429998"
- id="rect682"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="9.0869999"
- cy="4.9959998"
- rx="0.31299999"
- ry="0.092"
- id="ellipse684"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="9.0869999"
- cy="4.4429998"
- rx="0.31299999"
- ry="0.092"
- id="ellipse686"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="9.0869999"
- cy="4.4429998"
- rx="0.31299999"
- ry="0.092"
- id="ellipse688"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 9.4,4.443 L 9.4,4.996 C 9.4,5.047 9.26,5.088 9.087,5.088 C 8.913,5.088 8.773,5.047 8.773,4.996 L 8.773,4.443"
- id="path690"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.375"
- y1="4.9000001"
- x2="10.025"
- y2="5.3000002"
- stroke="#000000"
- stroke-width="0.100"
- id="line692"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62699997"
- height="0.55299997"
- x="11.812"
- y="4.4450002"
- id="rect694"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.126"
- cy="4.9980001"
- rx="0.31299999"
- ry="0.092"
- id="ellipse696"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.126"
- cy="4.4450002"
- rx="0.31299999"
- ry="0.092"
- id="ellipse698"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.126"
- cy="4.4450002"
- rx="0.31299999"
- ry="0.092"
- id="ellipse700"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.439,4.445 L 12.439,4.998 C 12.439,5.049 12.299,5.09 12.126,5.09 C 11.953,5.09 11.812,5.049 11.812,4.998 L 11.812,4.445"
- id="path702"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.089"
- y1="5.2789998"
- x2="11.825"
- y2="4.8499999"
- stroke="#000000"
- stroke-width="0.100"
- id="line704"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="8.7399998"
- y="5.5819998"
- id="text706"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
- <text
- x="11.799"
- y="5.6069999"
- id="text708"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">data</text>
- <text
- x="6.5149999"
- y="11.352"
- id="text710"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">30 Users</text>
- <text
- x="19.365"
- y="11.267"
- id="text712"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
- <text
- x="1.018"
- y="4.3790002"
- id="text714"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
- <text
- x="16.813"
- y="4.316"
- id="text716"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="25.385cm"
- height="20.027cm"
- viewBox="-0.789 0.573 24.595 20.6"
- id="svg2">
- <defs
- id="defs1129" />
- <rect
- width="11.5"
- height="7.7259998"
- x="12.77"
- y="12.847"
- id="rect4"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.77,12.847 C 12.604315,12.847 12.47,12.981315 12.47,13.147"
- id="path6"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 24.57,13.147 C 24.57,12.981315 24.435685,12.847 24.27,12.847"
- id="path8"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="12.1"
- height="7.1259999"
- x="12.47"
- y="13.147"
- id="rect10"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.47,20.273 C 12.47,20.438685 12.604315,20.573 12.77,20.573"
- id="path12"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 24.27,20.573 C 24.435685,20.573 24.57,20.438685 24.57,20.273"
- id="path14"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="12.77"
- y1="12.847"
- x2="24.27"
- y2="12.847"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.77"
- y1="20.573"
- x2="24.27"
- y2="20.573"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.77,12.847 C 12.604315,12.847 12.47,12.981315 12.47,13.147"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 24.57,13.147 C 24.57,12.981315 24.435685,12.847 24.27,12.847"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.47"
- y1="13.147"
- x2="12.47"
- y2="20.273001"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="24.57"
- y1="13.147"
- x2="24.57"
- y2="20.273001"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.47,20.273 C 12.47,20.438685 12.604315,20.573 12.77,20.573"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 24.27,20.573 C 24.435685,20.573 24.57,20.438685 24.57,20.273"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="12.01"
- height="7.7779999"
- x="-0.46399999"
- y="12.797"
- id="rect32"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -0.464,12.797 C -0.62968542,12.797 -0.764,12.931315 -0.764,13.097"
- id="path34"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.845,13.097 C 11.845,12.931315 11.710685,12.797 11.545,12.797"
- id="path36"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="12.61"
- height="7.178"
- x="-0.764"
- y="13.097"
- id="rect38"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -0.764,20.275 C -0.764,20.440685 -0.62968542,20.575 -0.464,20.575"
- id="path40"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.545,20.575 C 11.710685,20.575 11.845,20.440685 11.845,20.275"
- id="path42"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-0.46399999"
- y1="12.797"
- x2="11.545"
- y2="12.797"
- stroke="#000000"
- stroke-width="0.050"
- id="line44"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-0.46399999"
- y1="20.575001"
- x2="11.545"
- y2="20.575001"
- stroke="#000000"
- stroke-width="0.050"
- id="line46"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -0.464,12.797 C -0.62968542,12.797 -0.764,12.931315 -0.764,13.097"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.845,13.097 C 11.845,12.931315 11.710685,12.797 11.545,12.797"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-0.764"
- y1="13.097"
- x2="-0.764"
- y2="20.275"
- stroke="#000000"
- stroke-width="0.050"
- id="line52"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.845"
- y1="13.097"
- x2="11.845"
- y2="20.275"
- stroke="#000000"
- stroke-width="0.050"
- id="line54"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -0.764,20.275 C -0.764,20.440685 -0.62968542,20.575 -0.464,20.575"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.545,20.575 C 11.710685,20.575 11.845,20.440685 11.845,20.275"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="15.975"
- height="9.7749996"
- x="5.645"
- y="2.1719999"
- id="rect60"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 5.645,2.172 C 5.4793146,2.172 5.345,2.3063146 5.345,2.472"
- id="path62"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 21.92,2.472 C 21.92,2.3063146 21.785685,2.172 21.62,2.172"
- id="path64"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="16.575001"
- height="9.1750002"
- x="5.3449998"
- y="2.4719999"
- id="rect66"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 5.345,11.647 C 5.345,11.812685 5.4793146,11.947 5.645,11.947"
- id="path68"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 21.62,11.947 C 21.785685,11.947 21.92,11.812685 21.92,11.647"
- id="path70"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="5.645"
- y1="2.1719999"
- x2="21.620001"
- y2="2.1719999"
- stroke="#000000"
- stroke-width="0.050"
- id="line72"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="5.645"
- y1="11.947"
- x2="21.620001"
- y2="11.947"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 5.645,2.172 C 5.4793146,2.172 5.345,2.3063146 5.345,2.472"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 21.92,2.472 C 21.92,2.3063146 21.785685,2.172 21.62,2.172"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="5.3449998"
- y1="2.4719999"
- x2="5.3449998"
- y2="11.647"
- stroke="#000000"
- stroke-width="0.050"
- id="line80"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="21.92"
- y1="2.4719999"
- x2="21.92"
- y2="11.647"
- stroke="#000000"
- stroke-width="0.050"
- id="line82"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 5.345,11.647 C 5.345,11.812685 5.4793146,11.947 5.645,11.947"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 21.62,11.947 C 21.785685,11.947 21.92,11.812685 21.92,11.647"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.263,3.803 C 0.857,3.793 0.068,3.995 0.179,4.427 C 0.29,4.859 0.82,4.955 1.042,4.83 C 1.263,4.705 0.696,5.435 1.781,5.627 C 2.866,5.819 3.42,5.511 3.26,5.291 C 3.1,5.07 4.209,5.809 4.727,5.387 C 5.244,4.964 4.197,4.561 4.418,4.619 C 4.64,4.676 5.318,4.6 5.096,3.88 C 4.874,3.16 2.878,3.717 3.1,3.611 C 3.322,3.505 2.767,2.978 2.077,3.083 C 1.387,3.189 1.338,3.38 1.264,3.803 L 1.263,3.803"
- id="path88"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <path
- d="M 1.263,3.803 C 0.857,3.793 0.068,3.995 0.179,4.427 C 0.29,4.859 0.82,4.955 1.042,4.83 C 1.263,4.705 0.696,5.435 1.781,5.627 C 2.866,5.819 3.42,5.511 3.26,5.291 C 3.1,5.07 4.209,5.809 4.727,5.387 C 5.244,4.964 4.197,4.561 4.418,4.619 C 4.64,4.676 5.318,4.6 5.096,3.88 C 4.874,3.16 2.878,3.717 3.1,3.611 C 3.322,3.505 2.767,2.978 2.077,3.083 C 1.387,3.189 1.338,3.38 1.264,3.803 L 1.263,3.803"
- id="path90"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="2.2260001"
- y="4.4980001"
- id="text92"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
- <rect
- width="1.054"
- height="2.1070001"
- x="5.7290001"
- y="6.2870002"
- id="rect94"
- style="fill:#ff0000;stroke:none;stroke-width:0" />
- <polygon
- points="5.729,6.287 6.783,6.287 6.915,6.156 5.861,6.156 5.729,6.287 "
- id="polygon96"
- style="fill:#ff0000;stroke:none;stroke-width:0.1" />
- <polygon
- points="6.783,6.287 6.915,6.156 6.915,8.263 6.783,8.394 6.783,6.287 "
- id="polygon98"
- style="fill:#ff0000;stroke:none;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="6.4980001"
- x2="6.783"
- y2="6.4980001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line100"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="6.3660002"
- x2="6.783"
- y2="6.4980001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line102"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="6.2870002"
- x2="6.0450001"
- y2="6.4980001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line104"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="6.2870002"
- x2="6.177"
- y2="6.1560001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line106"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="6.9190001"
- x2="6.783"
- y2="6.9190001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line108"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="6.7880001"
- x2="6.783"
- y2="6.9190001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line110"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.467"
- y1="6.4980001"
- x2="6.467"
- y2="6.9190001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line112"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="7.3410001"
- x2="6.783"
- y2="7.3410001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line114"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="7.2090001"
- x2="6.783"
- y2="7.3410001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line116"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="6.9190001"
- x2="6.0450001"
- y2="7.3410001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line118"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="7.7620001"
- x2="6.783"
- y2="7.7620001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line120"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="7.631"
- x2="6.783"
- y2="7.7620001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line122"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.467"
- y1="7.3410001"
- x2="6.467"
- y2="7.7620001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line124"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="8.184"
- x2="6.783"
- y2="8.184"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line126"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="8.052"
- x2="6.783"
- y2="8.184"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line128"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="7.7620001"
- x2="6.0450001"
- y2="8.184"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line130"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.467"
- y1="8.184"
- x2="6.467"
- y2="8.3940001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line132"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="6.2870002"
- x2="6.783"
- y2="6.2870002"
- stroke="#000000"
- stroke-width="0.050"
- id="line134"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="6.783"
- y1="8.3940001"
- x2="6.783"
- y2="6.2870002"
- stroke="#000000"
- stroke-width="0.050"
- id="line136"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="6.783"
- y1="6.2870002"
- x2="6.915"
- y2="6.1560001"
- stroke="#000000"
- stroke-width="0.050"
- id="line138"
- style="stroke:#000000;stroke-width:0.05" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.050"
- points="5.729,6.287 5.861,6.156 6.915,6.156 6.915,8.263 6.783,8.394 5.729,8.394 5.729,6.287 "
- id="polyline140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="2.0050001"
- height="6.0149999"
- x="8.4580002"
- y="4.1360002"
- id="rect142"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.0050001"
- height="6.0149999"
- x="8.4580002"
- y="4.1360002"
- id="rect144"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.0050001"
- height="6.0149999"
- x="8.4580002"
- y="4.1360002"
- id="rect146"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.604"
- height="2.4059999"
- x="8.6590004"
- y="4.3369999"
- id="rect148"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.604"
- height="2.4059999"
- x="8.6590004"
- y="4.3369999"
- id="rect150"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.604"
- height="2.4059999"
- x="8.6590004"
- y="4.3369999"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="4.7379999"
- x2="10.263"
- y2="4.7379999"
- stroke="#000000"
- stroke-width="0.010"
- id="line154"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.263"
- y1="5.1389999"
- x2="8.6590004"
- y2="5.1389999"
- stroke="#000000"
- stroke-width="0.010"
- id="line156"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="5.54"
- x2="10.263"
- y2="5.54"
- stroke="#000000"
- stroke-width="0.010"
- id="line158"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="5.941"
- x2="10.263"
- y2="5.941"
- stroke="#000000"
- stroke-width="0.010"
- id="line160"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.263"
- y1="6.342"
- x2="8.6590004"
- y2="6.342"
- stroke="#000000"
- stroke-width="0.010"
- id="line162"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.103"
- height="0.60100001"
- x="8.6590004"
- y="6.9429998"
- id="rect164"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.103"
- height="0.60100001"
- x="8.6590004"
- y="6.9429998"
- id="rect166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.103"
- height="0.60100001"
- x="8.6590004"
- y="6.9429998"
- id="rect168"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.4580002"
- y1="7.9460001"
- x2="10.463"
- y2="7.9460001"
- stroke="#000000"
- stroke-width="0.010"
- id="line170"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.1"
- height="0.1"
- x="9.3610001"
- y="8.1459999"
- id="rect172"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.1"
- height="0.1"
- x="9.3610001"
- y="8.1459999"
- id="rect174"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.1"
- height="0.1"
- x="9.3610001"
- y="8.1459999"
- id="rect176"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.1"
- height="0.1"
- x="9.7620001"
- y="8.1459999"
- id="rect178"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.1"
- height="0.1"
- x="9.7620001"
- y="8.1459999"
- id="rect180"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.1"
- height="0.1"
- x="9.7620001"
- y="8.1459999"
- id="rect182"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.1"
- height="0.1"
- x="10.163"
- y="8.1459999"
- id="rect184"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.1"
- height="0.1"
- x="10.163"
- y="8.1459999"
- id="rect186"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.1"
- height="0.1"
- x="10.163"
- y="8.1459999"
- id="rect188"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.2"
- height="0.2"
- x="10.062"
- y="7.5450001"
- id="rect190"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.2"
- height="0.2"
- x="10.062"
- y="7.5450001"
- id="rect192"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.2"
- height="0.2"
- x="10.062"
- y="7.5450001"
- id="rect194"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="7.244"
- x2="9.7620001"
- y2="7.244"
- stroke="#000000"
- stroke-width="0.010"
- id="line196"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.301"
- height="0.301"
- x="8.6590004"
- y="8.0459995"
- id="rect198"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.301"
- height="0.301"
- x="8.6590004"
- y="8.0459995"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.301"
- height="0.301"
- x="8.6590004"
- y="8.0459995"
- id="rect202"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.403"
- height="0.1"
- x="8.7589998"
- y="6.4419999"
- id="rect204"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.403"
- height="0.1"
- x="8.7589998"
- y="6.4419999"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.403"
- height="0.1"
- x="8.7589998"
- y="6.4419999"
- id="rect208"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.7589998"
- y1="7.0430002"
- x2="9.6610003"
- y2="7.0430002"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.6610003"
- y1="7.1440001"
- x2="9.5609999"
- y2="7.1440001"
- stroke="#000000"
- stroke-width="0.010"
- id="line212"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.7589998"
- y1="7.1440001"
- x2="8.8590002"
- y2="7.1440001"
- stroke="#000000"
- stroke-width="0.010"
- id="line214"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.50099999"
- height="0.1"
- x="8.96"
- y="7.0430002"
- id="rect216"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.50099999"
- height="0.1"
- x="8.96"
- y="7.0430002"
- id="rect218"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.50099999"
- height="0.1"
- x="8.96"
- y="7.0430002"
- id="rect220"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.7589998"
- y1="6.6420002"
- x2="8.8590002"
- y2="6.6420002"
- stroke="#000000"
- stroke-width="0.010"
- id="line222"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.96"
- y1="6.6420002"
- x2="9.0600004"
- y2="6.6420002"
- stroke="#000000"
- stroke-width="0.010"
- id="line224"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.9619999"
- y1="6.6420002"
- x2="10.163"
- y2="6.6420002"
- stroke="#000000"
- stroke-width="0.010"
- id="line226"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="10.051"
- x2="10.363"
- y2="10.051"
- stroke="#000000"
- stroke-width="0.010"
- id="line228"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.9510002"
- x2="8.559"
- y2="9.9510002"
- stroke="#000000"
- stroke-width="0.010"
- id="line230"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.8500004"
- x2="10.363"
- y2="9.8500004"
- stroke="#000000"
- stroke-width="0.010"
- id="line232"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.75"
- x2="8.559"
- y2="9.75"
- stroke="#000000"
- stroke-width="0.010"
- id="line234"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.6499996"
- x2="10.363"
- y2="9.6499996"
- stroke="#000000"
- stroke-width="0.010"
- id="line236"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.5500002"
- x2="8.559"
- y2="9.5500002"
- stroke="#000000"
- stroke-width="0.010"
- id="line238"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.4490004"
- x2="10.363"
- y2="9.4490004"
- stroke="#000000"
- stroke-width="0.010"
- id="line240"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.349"
- x2="8.559"
- y2="9.349"
- stroke="#000000"
- stroke-width="0.010"
- id="line242"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.2489996"
- x2="10.363"
- y2="9.2489996"
- stroke="#000000"
- stroke-width="0.010"
- id="line244"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.1490002"
- x2="8.559"
- y2="9.1490002"
- stroke="#000000"
- stroke-width="0.010"
- id="line246"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.0480003"
- x2="10.363"
- y2="9.0480003"
- stroke="#000000"
- stroke-width="0.010"
- id="line248"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="8.948"
- x2="8.559"
- y2="8.948"
- stroke="#000000"
- stroke-width="0.010"
- id="line250"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="8.8479996"
- x2="10.363"
- y2="8.8479996"
- stroke="#000000"
- stroke-width="0.010"
- id="line252"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="8.7480001"
- x2="8.559"
- y2="8.7480001"
- stroke="#000000"
- stroke-width="0.010"
- id="line254"
- style="stroke:#000000;stroke-width:0.01" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="2.424,5.688 2.424,7.250 5.700,7.250 5.700,7.300 "
- id="polyline256"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.875"
- y1="7.3000002"
- x2="8.4250002"
- y2="7.2750001"
- stroke="#000000"
- stroke-width="0.100"
- id="line258"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.477"
- height="1.303"
- x="11.597"
- y="4.0450001"
- id="rect260"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.335"
- cy="5.348"
- rx="0.73799998"
- ry="0.21699999"
- id="ellipse262"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.335"
- cy="4.0450001"
- rx="0.73799998"
- ry="0.21699999"
- id="ellipse264"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.335"
- cy="4.0450001"
- rx="0.73799998"
- ry="0.21699999"
- id="ellipse266"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.074,4.045 L 13.074,5.348 C 13.074,5.468 12.743,5.565 12.335,5.565 C 11.928,5.565 11.597,5.468 11.597,5.348 L 11.597,4.045"
- id="path268"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.377"
- height="1.215"
- x="11.622"
- y="5.96"
- id="rect270"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.311"
- cy="7.1750002"
- rx="0.68800002"
- ry="0.20200001"
- id="ellipse272"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.311"
- cy="5.96"
- rx="0.68800002"
- ry="0.20200001"
- id="ellipse274"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.311"
- cy="5.96"
- rx="0.68800002"
- ry="0.20200001"
- id="ellipse276"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.999,5.96 L 12.999,7.175 C 12.999,7.287 12.691,7.377 12.311,7.377 C 11.931,7.377 11.622,7.287 11.622,7.175 L 11.622,5.96"
- id="path278"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.475"
- y1="4.6750002"
- x2="11.55"
- y2="4.6750002"
- stroke="#000000"
- stroke-width="0.100"
- id="line280"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.45"
- y1="6.3499999"
- x2="11.625"
- y2="6.3499999"
- stroke="#000000"
- stroke-width="0.100"
- id="line282"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.45"
- y1="8.8249998"
- x2="21"
- y2="8.8249998"
- stroke="#000000"
- stroke-width="0.100"
- id="line284"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="20.950001"
- y1="8.8249998"
- x2="20.950001"
- y2="7.9749999"
- stroke="#000000"
- stroke-width="0.100"
- id="line286"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="14.928"
- y1="8.8249998"
- x2="14.928"
- y2="7.9169998"
- stroke="#000000"
- stroke-width="0.100"
- id="line288"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="14.946"
- y1="8.8249998"
- x2="14.946"
- y2="9.8249998"
- stroke="#000000"
- stroke-width="0.100"
- id="line290"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.903"
- y1="8.8249998"
- x2="17.903"
- y2="7.901"
- stroke="#000000"
- stroke-width="0.100"
- id="line292"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.910999"
- y1="8.8249998"
- x2="17.910999"
- y2="9.8249998"
- stroke="#000000"
- stroke-width="0.100"
- id="line294"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="20.950001"
- y1="8.8249998"
- x2="20.950001"
- y2="9.9250002"
- stroke="#000000"
- stroke-width="0.100"
- id="line296"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="11.825"
- y="10.625"
- id="rect298"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="1"
- height="1"
- x="11.825"
- y="10.625"
- id="rect300"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="11.825"
- y="10.625"
- id="rect302"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
- id="path304"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
- id="path306"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
- id="polygon308"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
- id="polygon310"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
- id="polygon312"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
- id="polygon314"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
- id="path316"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
- id="path318"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
- id="polygon320"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
- id="polygon322"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
- id="polygon324"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
- id="polygon326"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="12.325"
- y1="8.8249998"
- x2="12.325"
- y2="10.625"
- stroke="#000000"
- stroke-width="0.100"
- id="line328"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="14.424,10.287 14.365,10.312 14.19,10.75 14.19,10.969 14.278,11.042 15.562,11.042 15.65,10.969 15.65,10.75 15.475,10.312 15.416,10.287 14.424,10.287 "
- id="polygon330"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="14.424,10.287 14.365,10.312 14.19,10.75 14.19,10.969 14.278,11.042 15.562,11.042 15.65,10.969 15.65,10.75 15.475,10.312 15.416,10.287 14.424,10.287 "
- id="polygon332"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 14.219,10.677 L 14.278,10.701 L 15.562,10.701 L 15.621,10.677"
- id="path334"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 15.562,10.701 L 15.65,10.75"
- id="path336"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 14.19,10.75 L 14.278,10.701"
- id="path338"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="14.599,9.825 14.57,10.409 15.27,10.409 15.241,9.825 14.599,9.825 "
- id="polygon340"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="14.599,9.825 14.57,10.409 15.27,10.409 15.241,9.825 14.599,9.825 "
- id="polygon342"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="14.482,10.409 14.424,10.579 15.416,10.579 15.358,10.409 14.482,10.409 "
- id="polygon344"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="14.482,10.409 14.424,10.579 15.416,10.579 15.358,10.409 14.482,10.409 "
- id="polygon346"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="14.482"
- cy="10.786"
- rx="0.015"
- ry="0.015"
- id="ellipse348"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.482"
- cy="10.786"
- rx="0.015"
- ry="0.015"
- id="ellipse350"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.628"
- cy="10.786"
- rx="0.015"
- ry="0.015"
- id="ellipse352"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.628"
- cy="10.786"
- rx="0.015"
- ry="0.015"
- id="ellipse354"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.774"
- cy="10.786"
- rx="0.015"
- ry="0.015"
- id="ellipse356"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.774"
- cy="10.786"
- rx="0.015"
- ry="0.015"
- id="ellipse358"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.482"
- cy="10.847"
- rx="0.015"
- ry="0.015"
- id="ellipse360"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.482"
- cy="10.847"
- rx="0.015"
- ry="0.015"
- id="ellipse362"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.628"
- cy="10.847"
- rx="0.015"
- ry="0.015"
- id="ellipse364"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.628"
- cy="10.847"
- rx="0.015"
- ry="0.015"
- id="ellipse366"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.774"
- cy="10.847"
- rx="0.015"
- ry="0.015"
- id="ellipse368"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.774"
- cy="10.847"
- rx="0.015"
- ry="0.015"
- id="ellipse370"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.482"
- cy="10.908"
- rx="0.015"
- ry="0.015"
- id="ellipse372"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.482"
- cy="10.908"
- rx="0.015"
- ry="0.015"
- id="ellipse374"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.628"
- cy="10.908"
- rx="0.015"
- ry="0.015"
- id="ellipse376"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.628"
- cy="10.908"
- rx="0.015"
- ry="0.015"
- id="ellipse378"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.774"
- cy="10.908"
- rx="0.015"
- ry="0.015"
- id="ellipse380"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.774"
- cy="10.908"
- rx="0.015"
- ry="0.015"
- id="ellipse382"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.482"
- cy="10.969"
- rx="0.015"
- ry="0.015"
- id="ellipse384"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.482"
- cy="10.969"
- rx="0.015"
- ry="0.015"
- id="ellipse386"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.628"
- cy="10.969"
- rx="0.015"
- ry="0.015"
- id="ellipse388"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.628"
- cy="10.969"
- rx="0.015"
- ry="0.015"
- id="ellipse390"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.774"
- cy="10.969"
- rx="0.015"
- ry="0.015"
- id="ellipse392"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="14.774"
- cy="10.969"
- rx="0.015"
- ry="0.015"
- id="ellipse394"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="14.92"
- cy="10.798"
- rx="0.183"
- ry="0.057999998"
- id="ellipse396"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="14.92"
- cy="10.798"
- rx="0.183"
- ry="0.057999998"
- id="ellipse398"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.285"
- cy="10.798"
- rx="0.183"
- ry="0.057999998"
- id="ellipse400"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="15.285"
- cy="10.798"
- rx="0.183"
- ry="0.057999998"
- id="ellipse402"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.112"
- height="0.83399999"
- x="14.372"
- y="6.8239999"
- id="rect404"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="14.372"
- y="6.8239999"
- id="rect406"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="14.492"
- y="6.9439998"
- id="rect408"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="14.522,7.657 15.094,7.657 15.094,7.787 14.552,7.787 14.522,7.657 "
- id="polygon410"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="14.522,7.657 15.094,7.657 15.094,7.787 14.552,7.787 14.522,7.657 "
- id="polygon412"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="15.094,7.657 15.333,7.657 15.303,7.787 15.094,7.787 15.094,7.657 "
- id="polygon414"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.094,7.657 15.333,7.657 15.303,7.787 15.094,7.787 15.094,7.657 "
- id="polygon416"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.133"
- y="7.6960001"
- id="rect418"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.133"
- y="7.6960001"
- id="rect420"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="14.816,7.787 15.039,7.787 15.039,7.852 15.15,7.852 15.15,7.917 14.705,7.917 14.705,7.852 14.816,7.852 14.816,7.787 "
- id="polygon422"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="14.816,7.787 15.039,7.787 15.039,7.852 15.15,7.852 15.15,7.917 14.705,7.917 14.705,7.852 14.816,7.852 14.816,7.787 "
- id="polygon424"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.348"
- y="6.8080001"
- id="rect426"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.348"
- y="6.8080001"
- id="rect428"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="17.468"
- y="6.928"
- id="rect430"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="17.498,7.641 18.07,7.641 18.07,7.771 17.528,7.771 17.498,7.641 "
- id="polygon432"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.498,7.641 18.07,7.641 18.07,7.771 17.528,7.771 17.498,7.641 "
- id="polygon434"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.07,7.641 18.309,7.641 18.279,7.771 18.07,7.771 18.07,7.641 "
- id="polygon436"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.07,7.641 18.309,7.641 18.279,7.771 18.07,7.771 18.07,7.641 "
- id="polygon438"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.108999"
- y="7.6799998"
- id="rect440"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.108999"
- y="7.6799998"
- id="rect442"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="17.792,7.771 18.014,7.771 18.014,7.836 18.126,7.836 18.126,7.901 17.681,7.901 17.681,7.836 17.792,7.836 17.792,7.771 "
- id="polygon444"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.792,7.771 18.014,7.771 18.014,7.836 18.126,7.836 18.126,7.901 17.681,7.901 17.681,7.836 17.792,7.836 17.792,7.771 "
- id="polygon446"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="6.8319998"
- id="rect448"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="6.8319998"
- id="rect450"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="20.518"
- y="6.9530001"
- id="rect452"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
- id="polygon454"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
- id="polygon456"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
- id="polygon458"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
- id="polygon460"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="7.7049999"
- id="rect462"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="7.7049999"
- id="rect464"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
- id="polygon466"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
- id="polygon468"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.298"
- y="9.8319998"
- id="rect470"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.298"
- y="9.8319998"
- id="rect472"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="17.417999"
- y="9.9530001"
- id="rect474"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="17.448,10.666 18.02,10.666 18.02,10.796 17.478,10.796 17.448,10.666 "
- id="polygon476"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.448,10.666 18.02,10.666 18.02,10.796 17.478,10.796 17.448,10.666 "
- id="polygon478"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.02,10.666 18.259,10.666 18.229,10.796 18.02,10.796 18.02,10.666 "
- id="polygon480"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.02,10.666 18.259,10.666 18.229,10.796 18.02,10.796 18.02,10.666 "
- id="polygon482"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.059"
- y="10.705"
- id="rect484"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.059"
- y="10.705"
- id="rect486"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="17.742,10.796 17.964,10.796 17.964,10.861 18.076,10.861 18.076,10.926 17.631,10.926 17.631,10.861 17.742,10.861 17.742,10.796 "
- id="polygon488"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.742,10.796 17.964,10.796 17.964,10.861 18.076,10.861 18.076,10.926 17.631,10.926 17.631,10.861 17.742,10.861 17.742,10.796 "
- id="polygon490"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="9.9320002"
- id="rect492"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="9.9320002"
- id="rect494"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="20.518"
- y="10.053"
- id="rect496"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="20.548,10.766 21.12,10.766 21.12,10.896 20.578,10.896 20.548,10.766 "
- id="polygon498"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.548,10.766 21.12,10.766 21.12,10.896 20.578,10.896 20.548,10.766 "
- id="polygon500"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="21.12,10.766 21.359,10.766 21.329,10.896 21.12,10.896 21.12,10.766 "
- id="polygon502"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="21.12,10.766 21.359,10.766 21.329,10.896 21.12,10.896 21.12,10.766 "
- id="polygon504"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="10.805"
- id="rect506"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="10.805"
- id="rect508"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="20.842,10.896 21.064,10.896 21.064,10.961 21.176,10.961 21.176,11.026 20.731,11.026 20.731,10.961 20.842,10.961 20.842,10.896 "
- id="polygon510"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.842,10.896 21.064,10.896 21.064,10.961 21.176,10.961 21.176,11.026 20.731,11.026 20.731,10.961 20.842,10.961 20.842,10.896 "
- id="polygon512"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1"
- height="1"
- x="3.473"
- y="13.307"
- id="rect514"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="1"
- height="1"
- x="3.473"
- y="13.307"
- id="rect516"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="3.473"
- y="13.307"
- id="rect518"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 4.034,13.469 C 4.034,13.969 4.134,13.869 3.634,13.869"
- id="path520"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 4.034,13.469 C 4.034,13.969 4.134,13.869 3.634,13.869"
- id="path522"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.083,13.547 4.033,13.447 3.982,13.547 4.083,13.547 "
- id="polygon524"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.083,13.547 4.033,13.447 3.982,13.547 4.083,13.547 "
- id="polygon526"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.713,13.817 3.613,13.867 3.713,13.917 3.713,13.817 "
- id="polygon528"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.713,13.817 3.613,13.867 3.713,13.917 3.713,13.817 "
- id="polygon530"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 4.331,13.751 C 3.831,13.751 3.931,13.651 3.931,14.151"
- id="path532"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 4.331,13.751 C 3.831,13.751 3.931,13.651 3.931,14.151"
- id="path534"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.242,13.797 4.343,13.747 4.242,13.697 4.242,13.797 "
- id="polygon536"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.242,13.797 4.343,13.747 4.242,13.697 4.242,13.797 "
- id="polygon538"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.873,14.067 3.923,14.167 3.973,14.067 3.873,14.067 "
- id="polygon540"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.873,14.067 3.923,14.167 3.973,14.067 3.873,14.067 "
- id="polygon542"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="12.025,11.600 12.025,12.422 3.973,12.422 3.973,13.307 "
- id="polyline544"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="12.625,11.650 12.625,12.422 18.872,12.422 18.872,13.332 "
- id="polyline546"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="11.971"
- y="4.928"
- id="text548"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
- <text
- x="11.969"
- y="6.79"
- id="text550"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">data</text>
- <text
- x="5.848"
- y="8.9899998"
- id="text552"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">firewall</text>
- <text
- x="10.47"
- y="11.315"
- id="text554"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
- <text
- x="16.370001"
- y="6.3779998"
- id="text556"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.0.0/22</text>
- <text
- x="15.487"
- y="3.3280001"
- id="text558"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: MEGANET</text>
- <text
- x="8.2959995"
- y="2.983"
- id="text560"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC Server:</text>
- <text
- x="8.5109997"
- y="3.5829999"
- id="text562"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">MASSIVE</text>
- <text
- x="7.4990001"
- y="7.092"
- id="text564"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth0</text>
- <text
- x="10.822"
- y="8.5419998"
- id="text566"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth1</text>
- <rect
- width="1"
- height="1"
- x="18.372"
- y="13.332"
- id="rect568"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="1"
- height="1"
- x="18.372"
- y="13.332"
- id="rect570"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="18.372"
- y="13.332"
- id="rect572"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 18.934,13.494 C 18.934,13.994 19.034,13.894 18.534,13.894"
- id="path574"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 18.934,13.494 C 18.934,13.994 19.034,13.894 18.534,13.894"
- id="path576"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="18.982,13.572 18.932,13.473 18.883,13.572 18.982,13.572 "
- id="polygon578"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="18.982,13.572 18.932,13.473 18.883,13.572 18.982,13.572 "
- id="polygon580"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="18.612,13.842 18.512,13.893 18.612,13.942 18.612,13.842 "
- id="polygon582"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="18.612,13.842 18.512,13.893 18.612,13.942 18.612,13.842 "
- id="polygon584"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 19.231,13.776 C 18.731,13.776 18.831,13.676 18.831,14.176"
- id="path586"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 19.231,13.776 C 18.731,13.776 18.831,13.676 18.831,14.176"
- id="path588"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="19.142,13.822 19.242,13.772 19.142,13.723 19.142,13.822 "
- id="polygon590"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.142,13.822 19.242,13.772 19.142,13.723 19.142,13.822 "
- id="polygon592"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="18.772,14.092 18.822,14.192 18.872,14.092 18.772,14.092 "
- id="polygon594"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="18.772,14.092 18.822,14.192 18.872,14.092 18.772,14.092 "
- id="polygon596"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.275"
- y1="15.225"
- x2="20.950001"
- y2="15.225"
- stroke="#000000"
- stroke-width="0.100"
- id="line598"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="15.093"
- y1="15.225"
- x2="15.093"
- y2="16.225"
- stroke="#000000"
- stroke-width="0.100"
- id="line600"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.325"
- y1="15.225"
- x2="13.325"
- y2="16.225"
- stroke="#000000"
- stroke-width="0.100"
- id="line602"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.979"
- y1="15.225"
- x2="16.979"
- y2="16.225"
- stroke="#000000"
- stroke-width="0.100"
- id="line604"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.872"
- y1="15.225"
- x2="18.872"
- y2="14.332"
- stroke="#000000"
- stroke-width="0.100"
- id="line606"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.864"
- y1="15.225"
- x2="18.864"
- y2="16.225"
- stroke="#000000"
- stroke-width="0.100"
- id="line608"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="20.9"
- y1="15.225"
- x2="20.9"
- y2="16.200001"
- stroke="#000000"
- stroke-width="0.100"
- id="line610"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.5"
- height="3"
- x="20.15"
- y="16.200001"
- id="rect612"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.5"
- height="3"
- x="20.15"
- y="16.200001"
- id="rect614"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.5"
- height="3"
- x="20.15"
- y="16.200001"
- id="rect616"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.2"
- height="1.2"
- x="20.299999"
- y="16.35"
- id="rect618"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.2"
- height="1.2"
- x="20.299999"
- y="16.35"
- id="rect620"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.2"
- height="1.2"
- x="20.299999"
- y="16.35"
- id="rect622"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.5"
- y1="16.65"
- x2="20.299999"
- y2="16.65"
- stroke="#000000"
- stroke-width="0.010"
- id="line624"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.299999"
- y1="16.950001"
- x2="21.5"
- y2="16.950001"
- stroke="#000000"
- stroke-width="0.010"
- id="line626"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.5"
- y1="17.174999"
- x2="20.299999"
- y2="17.174999"
- stroke="#000000"
- stroke-width="0.010"
- id="line628"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="20.299999"
- y="17.700001"
- id="rect630"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="20.299999"
- y="17.700001"
- id="rect632"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="20.299999"
- y="17.700001"
- id="rect634"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.15"
- y1="18.225"
- x2="21.65"
- y2="18.225"
- stroke="#000000"
- stroke-width="0.010"
- id="line636"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="20.825001"
- y="18.375"
- id="rect638"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="20.825001"
- y="18.375"
- id="rect640"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="20.825001"
- y="18.375"
- id="rect642"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.125"
- y="18.375"
- id="rect644"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.125"
- y="18.375"
- id="rect646"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.125"
- y="18.375"
- id="rect648"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.424999"
- y="18.375"
- id="rect650"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.424999"
- y="18.375"
- id="rect652"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.424999"
- y="18.375"
- id="rect654"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="21.35"
- y="17.924999"
- id="rect656"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="21.35"
- y="17.924999"
- id="rect658"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="21.35"
- y="17.924999"
- id="rect660"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.299999"
- y1="17.924999"
- x2="21.125"
- y2="17.924999"
- stroke="#000000"
- stroke-width="0.010"
- id="line662"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="20.299999"
- y="18.299999"
- id="rect664"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="20.299999"
- y="18.299999"
- id="rect666"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="20.299999"
- y="18.299999"
- id="rect668"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.05"
- height="0.075000003"
- x="20.375"
- y="17.25"
- id="rect670"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.05"
- height="0.075000003"
- x="20.375"
- y="17.25"
- id="rect672"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.05"
- height="0.075000003"
- x="20.375"
- y="17.25"
- id="rect674"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.375"
- y1="17.775"
- x2="21.049999"
- y2="17.775"
- stroke="#000000"
- stroke-width="0.010"
- id="line676"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.049999"
- y1="17.85"
- x2="20.975"
- y2="17.85"
- stroke="#000000"
- stroke-width="0.010"
- id="line678"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.375"
- y1="17.85"
- x2="20.450001"
- y2="17.85"
- stroke="#000000"
- stroke-width="0.010"
- id="line680"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.375"
- height="0.075000003"
- x="20.525"
- y="17.775"
- id="rect682"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.375"
- height="0.075000003"
- x="20.525"
- y="17.775"
- id="rect684"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.375"
- height="0.075000003"
- x="20.525"
- y="17.775"
- id="rect686"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.375"
- y1="17.4"
- x2="20.450001"
- y2="17.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line688"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.525"
- y1="17.4"
- x2="20.6"
- y2="17.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.275"
- y1="17.4"
- x2="21.424999"
- y2="17.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.575001"
- y1="19.125"
- x2="20.225"
- y2="19.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.225"
- y1="19.049999"
- x2="21.575001"
- y2="19.049999"
- stroke="#000000"
- stroke-width="0.010"
- id="line696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.575001"
- y1="18.975"
- x2="20.225"
- y2="18.975"
- stroke="#000000"
- stroke-width="0.010"
- id="line698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.225"
- y1="18.9"
- x2="21.575001"
- y2="18.9"
- stroke="#000000"
- stroke-width="0.010"
- id="line700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.575001"
- y1="18.825001"
- x2="20.225"
- y2="18.825001"
- stroke="#000000"
- stroke-width="0.010"
- id="line702"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.225"
- y1="18.75"
- x2="21.575001"
- y2="18.75"
- stroke="#000000"
- stroke-width="0.010"
- id="line704"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.575001"
- y1="18.674999"
- x2="20.225"
- y2="18.674999"
- stroke="#000000"
- stroke-width="0.010"
- id="line706"
- style="stroke:#000000;stroke-width:0.01" />
- <polygon
- points="18.371,16.685 18.313,16.709 18.137,17.147 18.137,17.366 18.225,17.439 19.51,17.439 19.598,17.366 19.598,17.147 19.422,16.709 19.364,16.685 18.371,16.685 "
- id="polygon708"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="18.371,16.685 18.313,16.709 18.137,17.147 18.137,17.366 18.225,17.439 19.51,17.439 19.598,17.366 19.598,17.147 19.422,16.709 19.364,16.685 18.371,16.685 "
- id="polygon710"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 18.167,17.074 L 18.225,17.099 L 19.51,17.099 L 19.568,17.074"
- id="path712"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 19.51,17.099 L 19.598,17.147"
- id="path714"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 18.137,17.147 L 18.225,17.099"
- id="path716"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="18.546,16.223 18.517,16.807 19.218,16.807 19.189,16.223 18.546,16.223 "
- id="polygon718"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="18.546,16.223 18.517,16.807 19.218,16.807 19.189,16.223 18.546,16.223 "
- id="polygon720"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="18.429,16.807 18.371,16.977 19.364,16.977 19.306,16.807 18.429,16.807 "
- id="polygon722"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="18.429,16.807 18.371,16.977 19.364,16.977 19.306,16.807 18.429,16.807 "
- id="polygon724"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="18.429001"
- cy="17.184"
- rx="0.015"
- ry="0.015"
- id="ellipse726"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.429001"
- cy="17.184"
- rx="0.015"
- ry="0.015"
- id="ellipse728"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.575001"
- cy="17.184"
- rx="0.015"
- ry="0.015"
- id="ellipse730"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.575001"
- cy="17.184"
- rx="0.015"
- ry="0.015"
- id="ellipse732"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.721001"
- cy="17.184"
- rx="0.015"
- ry="0.015"
- id="ellipse734"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.721001"
- cy="17.184"
- rx="0.015"
- ry="0.015"
- id="ellipse736"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.429001"
- cy="17.245001"
- rx="0.015"
- ry="0.015"
- id="ellipse738"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.429001"
- cy="17.245001"
- rx="0.015"
- ry="0.015"
- id="ellipse740"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.575001"
- cy="17.245001"
- rx="0.015"
- ry="0.015"
- id="ellipse742"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.575001"
- cy="17.245001"
- rx="0.015"
- ry="0.015"
- id="ellipse744"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.721001"
- cy="17.245001"
- rx="0.015"
- ry="0.015"
- id="ellipse746"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.721001"
- cy="17.245001"
- rx="0.015"
- ry="0.015"
- id="ellipse748"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.429001"
- cy="17.305"
- rx="0.015"
- ry="0.015"
- id="ellipse750"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.429001"
- cy="17.305"
- rx="0.015"
- ry="0.015"
- id="ellipse752"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.575001"
- cy="17.305"
- rx="0.015"
- ry="0.015"
- id="ellipse754"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.575001"
- cy="17.305"
- rx="0.015"
- ry="0.015"
- id="ellipse756"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.721001"
- cy="17.305"
- rx="0.015"
- ry="0.015"
- id="ellipse758"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.721001"
- cy="17.305"
- rx="0.015"
- ry="0.015"
- id="ellipse760"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.429001"
- cy="17.365999"
- rx="0.015"
- ry="0.015"
- id="ellipse762"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.429001"
- cy="17.365999"
- rx="0.015"
- ry="0.015"
- id="ellipse764"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.575001"
- cy="17.365999"
- rx="0.015"
- ry="0.015"
- id="ellipse766"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.575001"
- cy="17.365999"
- rx="0.015"
- ry="0.015"
- id="ellipse768"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.721001"
- cy="17.365999"
- rx="0.015"
- ry="0.015"
- id="ellipse770"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.721001"
- cy="17.365999"
- rx="0.015"
- ry="0.015"
- id="ellipse772"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.867001"
- cy="17.195999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse774"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="18.867001"
- cy="17.195999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse776"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.233"
- cy="17.195999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse778"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="19.233"
- cy="17.195999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse780"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.112"
- height="0.83399999"
- x="16.448"
- y="16.233"
- id="rect782"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="16.448"
- y="16.233"
- id="rect784"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="16.568001"
- y="16.353001"
- id="rect786"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.598,17.066 17.17,17.066 17.17,17.196 16.628,17.196 16.598,17.066 "
- id="polygon788"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.598,17.066 17.17,17.066 17.17,17.196 16.628,17.196 16.598,17.066 "
- id="polygon790"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.17,17.066 17.409,17.066 17.379,17.196 17.17,17.196 17.17,17.066 "
- id="polygon792"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.17,17.066 17.409,17.066 17.379,17.196 17.17,17.196 17.17,17.066 "
- id="polygon794"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="17.209"
- y="17.105"
- id="rect796"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="17.209"
- y="17.105"
- id="rect798"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.892,17.196 17.114,17.196 17.114,17.261 17.226,17.261 17.226,17.326 16.781,17.326 16.781,17.261 16.892,17.261 16.892,17.196 "
- id="polygon800"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.892,17.196 17.114,17.196 17.114,17.261 17.226,17.261 17.226,17.326 16.781,17.326 16.781,17.261 16.892,17.261 16.892,17.196 "
- id="polygon802"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="14.573"
- y="16.207001"
- id="rect804"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="14.573"
- y="16.207001"
- id="rect806"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="14.693"
- y="16.327999"
- id="rect808"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="14.723,17.041 15.295,17.041 15.295,17.171 14.753,17.171 14.723,17.041 "
- id="polygon810"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="14.723,17.041 15.295,17.041 15.295,17.171 14.753,17.171 14.723,17.041 "
- id="polygon812"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="15.295,17.041 15.534,17.041 15.504,17.171 15.295,17.171 15.295,17.041 "
- id="polygon814"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.295,17.041 15.534,17.041 15.504,17.171 15.295,17.171 15.295,17.041 "
- id="polygon816"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.334"
- y="17.08"
- id="rect818"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.334"
- y="17.08"
- id="rect820"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="15.017,17.171 15.239,17.171 15.239,17.236 15.351,17.236 15.351,17.301 14.906,17.301 14.906,17.236 15.017,17.236 15.017,17.171 "
- id="polygon822"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.017,17.171 15.239,17.171 15.239,17.236 15.351,17.236 15.351,17.301 14.906,17.301 14.906,17.236 15.017,17.236 15.017,17.171 "
- id="polygon824"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="12.798"
- y="16.233"
- id="rect826"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="12.798"
- y="16.233"
- id="rect828"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="12.918"
- y="16.353001"
- id="rect830"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="12.948,17.066 13.52,17.066 13.52,17.196 12.978,17.196 12.948,17.066 "
- id="polygon832"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="12.948,17.066 13.52,17.066 13.52,17.196 12.978,17.196 12.948,17.066 "
- id="polygon834"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="13.52,17.066 13.759,17.066 13.729,17.196 13.52,17.196 13.52,17.066 "
- id="polygon836"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="13.52,17.066 13.759,17.066 13.729,17.196 13.52,17.196 13.52,17.066 "
- id="polygon838"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="13.559"
- y="17.105"
- id="rect840"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="13.559"
- y="17.105"
- id="rect842"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="13.242,17.196 13.464,17.196 13.464,17.261 13.576,17.261 13.576,17.326 13.131,17.326 13.131,17.261 13.242,17.261 13.242,17.196 "
- id="polygon844"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="13.242,17.196 13.464,17.196 13.464,17.261 13.576,17.261 13.576,17.326 13.131,17.326 13.131,17.261 13.242,17.261 13.242,17.196 "
- id="polygon846"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.531"
- height="1.351"
- x="22.747"
- y="16.533001"
- id="rect848"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="23.513"
- cy="17.884001"
- rx="0.76599997"
- ry="0.22499999"
- id="ellipse850"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="23.513"
- cy="16.533001"
- rx="0.76599997"
- ry="0.22499999"
- id="ellipse852"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="23.513"
- cy="16.533001"
- rx="0.76599997"
- ry="0.22499999"
- id="ellipse854"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 24.279,16.533 L 24.279,17.884 C 24.279,18.008 23.936,18.109 23.513,18.109 C 23.09,18.109 22.747,18.008 22.747,17.884 L 22.747,16.533"
- id="path856"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="21.598"
- y1="16.933001"
- x2="22.773001"
- y2="16.933001"
- stroke="#000000"
- stroke-width="0.100"
- id="line858"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="23.191"
- y="17.372"
- id="text860"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
- <text
- x="19.969999"
- y="13.565"
- id="text862"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
- <text
- x="14.375"
- y="14.915"
- id="text864"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.8.0/22</text>
- <text
- x="20.979"
- y="14.872"
- id="text866"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="21.68"
- y="15.472"
- id="text868"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2</text>
- <line
- x1="3.924"
- y1="15.258"
- x2="11.127"
- y2="15.25"
- stroke="#000000"
- stroke-width="0.100"
- id="line870"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="3.974"
- y1="15.257"
- x2="3.9749999"
- y2="16.25"
- stroke="#000000"
- stroke-width="0.100"
- id="line872"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="3.974"
- y1="15.257"
- x2="3.973"
- y2="13.982"
- stroke="#000000"
- stroke-width="0.100"
- id="line874"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.5970001"
- y1="15.255"
- x2="6.598"
- y2="16.221001"
- stroke="#000000"
- stroke-width="0.100"
- id="line876"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1079998"
- y1="15.253"
- x2="8.1079998"
- y2="15.268"
- stroke="#000000"
- stroke-width="0.100"
- id="line878"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.7959995"
- y1="15.253"
- x2="8.7980003"
- y2="16.292999"
- stroke="#000000"
- stroke-width="0.100"
- id="line880"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.077"
- y1="15.25"
- x2="11.079"
- y2="16.25"
- stroke="#000000"
- stroke-width="0.100"
- id="line882"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.6670001"
- height="2.5"
- x="3.142"
- y="16.25"
- id="rect884"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.6670001"
- height="2.5"
- x="3.142"
- y="16.25"
- id="rect886"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.6670001"
- height="2.5"
- x="3.142"
- y="16.25"
- id="rect888"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3329999"
- height="1"
- x="3.2249999"
- y="16.333"
- id="rect890"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.3329999"
- height="1"
- x="3.2249999"
- y="16.333"
- id="rect892"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.3329999"
- height="1"
- x="3.2249999"
- y="16.333"
- id="rect894"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.2249999"
- y1="16.667"
- x2="4.5580001"
- y2="16.667"
- stroke="#000000"
- stroke-width="0.010"
- id="line896"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.5580001"
- y1="17"
- x2="3.2249999"
- y2="17"
- stroke="#000000"
- stroke-width="0.010"
- id="line898"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.917"
- height="0.5"
- x="3.392"
- y="17.417"
- id="rect900"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.917"
- height="0.5"
- x="3.392"
- y="17.417"
- id="rect902"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.917"
- height="0.5"
- x="3.392"
- y="17.417"
- id="rect904"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.142"
- y1="18.167"
- x2="4.8080001"
- y2="18.167"
- stroke="#000000"
- stroke-width="0.010"
- id="line906"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.3080001"
- y="18"
- id="rect908"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.3080001"
- y="18"
- id="rect910"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.3080001"
- y="18"
- id="rect912"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.4749999"
- y="18"
- id="rect914"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.4749999"
- y="18"
- id="rect916"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.4749999"
- y="18"
- id="rect918"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.6420002"
- y="18"
- id="rect920"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.6420002"
- y="18"
- id="rect922"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.6420002"
- y="18"
- id="rect924"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.167"
- height="0.167"
- x="4.5580001"
- y="17.75"
- id="rect926"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.167"
- height="0.167"
- x="4.5580001"
- y="17.75"
- id="rect928"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.167"
- height="0.167"
- x="4.5580001"
- y="17.75"
- id="rect930"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.392"
- y1="17.667"
- x2="4.3080001"
- y2="17.667"
- stroke="#000000"
- stroke-width="0.010"
- id="line932"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.25"
- height="0.25"
- x="4.4749999"
- y="17.417"
- id="rect934"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.25"
- height="0.25"
- x="4.4749999"
- y="17.417"
- id="rect936"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.25"
- height="0.25"
- x="4.4749999"
- y="17.417"
- id="rect938"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.1670001"
- height="0.082999997"
- x="3.3080001"
- y="17.083"
- id="rect940"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.1670001"
- height="0.082999997"
- x="3.3080001"
- y="17.083"
- id="rect942"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1670001"
- height="0.082999997"
- x="3.3080001"
- y="17.083"
- id="rect944"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.4749999"
- y1="17.5"
- x2="4.2249999"
- y2="17.5"
- stroke="#000000"
- stroke-width="0.010"
- id="line946"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.417"
- height="0.082999997"
- x="3.642"
- y="17.5"
- id="rect948"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.417"
- height="0.082999997"
- x="3.642"
- y="17.5"
- id="rect950"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.417"
- height="0.082999997"
- x="3.642"
- y="17.5"
- id="rect952"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3080001"
- y1="17.25"
- x2="4.4749999"
- y2="17.25"
- stroke="#000000"
- stroke-width="0.010"
- id="line954"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.2249999"
- y1="18.25"
- x2="4.7249999"
- y2="18.25"
- stroke="#000000"
- stroke-width="0.010"
- id="line956"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.7249999"
- y1="18.333"
- x2="3.2249999"
- y2="18.333"
- stroke="#000000"
- stroke-width="0.010"
- id="line958"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.2249999"
- y1="18.417"
- x2="4.7249999"
- y2="18.417"
- stroke="#000000"
- stroke-width="0.010"
- id="line960"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.7249999"
- y1="18.667"
- x2="3.2249999"
- y2="18.667"
- stroke="#000000"
- stroke-width="0.010"
- id="line962"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.2249999"
- y1="18.583"
- x2="4.7249999"
- y2="18.583"
- stroke="#000000"
- stroke-width="0.010"
- id="line964"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.7249999"
- y1="18.5"
- x2="3.2249999"
- y2="18.5"
- stroke="#000000"
- stroke-width="0.010"
- id="line966"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.3080001"
- y1="17.25"
- x2="3.392"
- y2="17.25"
- stroke="#000000"
- stroke-width="0.010"
- id="line968"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.4749999"
- y1="17.25"
- x2="3.5580001"
- y2="17.25"
- stroke="#000000"
- stroke-width="0.010"
- id="line970"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.4749999"
- y1="17.583"
- x2="3.5580001"
- y2="17.583"
- stroke="#000000"
- stroke-width="0.010"
- id="line972"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.1420002"
- y1="17.583"
- x2="4.2249999"
- y2="17.583"
- stroke="#000000"
- stroke-width="0.010"
- id="line974"
- style="stroke:#000000;stroke-width:0.01" />
- <polygon
- points="6.121,16.635 6.063,16.659 5.887,17.097 5.887,17.316 5.975,17.389 7.26,17.389 7.348,17.316 7.348,17.097 7.172,16.659 7.114,16.635 6.121,16.635 "
- id="polygon976"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.121,16.635 6.063,16.659 5.887,17.097 5.887,17.316 5.975,17.389 7.26,17.389 7.348,17.316 7.348,17.097 7.172,16.659 7.114,16.635 6.121,16.635 "
- id="polygon978"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.917,17.024 L 5.975,17.049 L 7.26,17.049 L 7.318,17.024"
- id="path980"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.26,17.049 L 7.348,17.097"
- id="path982"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.887,17.097 L 5.975,17.049"
- id="path984"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.296,16.172 6.267,16.757 6.968,16.757 6.939,16.172 6.296,16.172 "
- id="polygon986"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.296,16.172 6.267,16.757 6.968,16.757 6.939,16.172 6.296,16.172 "
- id="polygon988"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.179,16.757 6.121,16.927 7.114,16.927 7.056,16.757 6.179,16.757 "
- id="polygon990"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.179,16.757 6.121,16.927 7.114,16.927 7.056,16.757 6.179,16.757 "
- id="polygon992"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="6.1789999"
- cy="17.134001"
- rx="0.015"
- ry="0.015"
- id="ellipse994"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1789999"
- cy="17.134001"
- rx="0.015"
- ry="0.015"
- id="ellipse996"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3249998"
- cy="17.134001"
- rx="0.015"
- ry="0.015"
- id="ellipse998"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3249998"
- cy="17.134001"
- rx="0.015"
- ry="0.015"
- id="ellipse1000"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="17.134001"
- rx="0.015"
- ry="0.015"
- id="ellipse1002"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="17.134001"
- rx="0.015"
- ry="0.015"
- id="ellipse1004"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1789999"
- cy="17.195"
- rx="0.015"
- ry="0.015"
- id="ellipse1006"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1789999"
- cy="17.195"
- rx="0.015"
- ry="0.015"
- id="ellipse1008"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3249998"
- cy="17.195"
- rx="0.015"
- ry="0.015"
- id="ellipse1010"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3249998"
- cy="17.195"
- rx="0.015"
- ry="0.015"
- id="ellipse1012"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="17.195"
- rx="0.015"
- ry="0.015"
- id="ellipse1014"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="17.195"
- rx="0.015"
- ry="0.015"
- id="ellipse1016"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1789999"
- cy="17.254999"
- rx="0.015"
- ry="0.015"
- id="ellipse1018"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1789999"
- cy="17.254999"
- rx="0.015"
- ry="0.015"
- id="ellipse1020"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3249998"
- cy="17.254999"
- rx="0.015"
- ry="0.015"
- id="ellipse1022"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3249998"
- cy="17.254999"
- rx="0.015"
- ry="0.015"
- id="ellipse1024"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="17.254999"
- rx="0.015"
- ry="0.015"
- id="ellipse1026"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="17.254999"
- rx="0.015"
- ry="0.015"
- id="ellipse1028"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1789999"
- cy="17.316"
- rx="0.015"
- ry="0.015"
- id="ellipse1030"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1789999"
- cy="17.316"
- rx="0.015"
- ry="0.015"
- id="ellipse1032"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3249998"
- cy="17.316"
- rx="0.015"
- ry="0.015"
- id="ellipse1034"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3249998"
- cy="17.316"
- rx="0.015"
- ry="0.015"
- id="ellipse1036"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="17.316"
- rx="0.015"
- ry="0.015"
- id="ellipse1038"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="17.316"
- rx="0.015"
- ry="0.015"
- id="ellipse1040"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.6170001"
- cy="17.146"
- rx="0.183"
- ry="0.057999998"
- id="ellipse1042"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.6170001"
- cy="17.146"
- rx="0.183"
- ry="0.057999998"
- id="ellipse1044"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.9829998"
- cy="17.146"
- rx="0.183"
- ry="0.057999998"
- id="ellipse1046"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.9829998"
- cy="17.146"
- rx="0.183"
- ry="0.057999998"
- id="ellipse1048"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.112"
- height="0.83399999"
- x="10.473"
- y="16.257999"
- id="rect1050"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="10.473"
- y="16.257999"
- id="rect1052"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="10.593"
- y="16.378"
- id="rect1054"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="10.623,17.091 11.195,17.091 11.195,17.221 10.653,17.221 10.623,17.091 "
- id="polygon1056"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.623,17.091 11.195,17.091 11.195,17.221 10.653,17.221 10.623,17.091 "
- id="polygon1058"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="11.195,17.091 11.434,17.091 11.404,17.221 11.195,17.221 11.195,17.091 "
- id="polygon1060"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="11.195,17.091 11.434,17.091 11.404,17.221 11.195,17.221 11.195,17.091 "
- id="polygon1062"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="11.234"
- y="17.129999"
- id="rect1064"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="11.234"
- y="17.129999"
- id="rect1066"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="10.917,17.221 11.139,17.221 11.139,17.286 11.251,17.286 11.251,17.351 10.806,17.351 10.806,17.286 10.917,17.286 10.917,17.221 "
- id="polygon1068"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.917,17.221 11.139,17.221 11.139,17.286 11.251,17.286 11.251,17.351 10.806,17.351 10.806,17.286 10.917,17.286 10.917,17.221 "
- id="polygon1070"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="8.2729998"
- y="16.282"
- id="rect1072"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="8.2729998"
- y="16.282"
- id="rect1074"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="8.3929996"
- y="16.403"
- id="rect1076"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="8.423,17.116 8.995,17.116 8.995,17.246 8.453,17.246 8.423,17.116 "
- id="polygon1078"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.423,17.116 8.995,17.116 8.995,17.246 8.453,17.246 8.423,17.116 "
- id="polygon1080"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.995,17.116 9.234,17.116 9.204,17.246 8.995,17.246 8.995,17.116 "
- id="polygon1082"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.995,17.116 9.234,17.116 9.204,17.246 8.995,17.246 8.995,17.116 "
- id="polygon1084"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="9.0340004"
- y="17.155001"
- id="rect1086"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="9.0340004"
- y="17.155001"
- id="rect1088"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.717,17.246 8.939,17.246 8.939,17.311 9.051,17.311 9.051,17.376 8.606,17.376 8.606,17.311 8.717,17.311 8.717,17.246 "
- id="polygon1090"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.717,17.246 8.939,17.246 8.939,17.311 9.051,17.311 9.051,17.376 8.606,17.376 8.606,17.311 8.717,17.311 8.717,17.246 "
- id="polygon1092"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.53"
- height="1.35"
- x="0.51999998"
- y="16.433001"
- id="rect1094"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="1.285"
- cy="17.783001"
- rx="0.76499999"
- ry="0.22499999"
- id="ellipse1096"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.285"
- cy="16.433001"
- rx="0.76499999"
- ry="0.22499999"
- id="ellipse1098"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.285"
- cy="16.433001"
- rx="0.76499999"
- ry="0.22499999"
- id="ellipse1100"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 2.051,16.433 L 2.051,17.783 C 2.051,17.907 1.708,18.008 1.285,18.008 C 0.863,18.008 0.52,17.907 0.52,17.783 L 0.52,16.433"
- id="path1102"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.998"
- y1="16.832001"
- x2="3.1719999"
- y2="16.832001"
- stroke="#000000"
- stroke-width="0.100"
- id="line1104"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.97399998"
- y="17.322001"
- id="text1106"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
- <text
- x="2.102"
- y="13.872"
- id="text1108"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
- <text
- x="6.6999998"
- y="14.915"
- id="text1110"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.4.0/22</text>
- <text
- x="0.42899999"
- y="15.372"
- id="text1112"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="1.13"
- y="15.972"
- id="text1114"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG1</text>
- <text
- x="9.4289999"
- y="20.072001"
- id="text1116"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
- <text
- x="22.027"
- y="20.183001"
- id="text1118"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">150 Users</text>
- <text
- x="18.612"
- y="11.758"
- id="text1120"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">300 Users</text>
- <text
- x="0.22499999"
- y="20.048"
- id="text1122"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
- <text
- x="14.062"
- y="20.108"
- id="text1124"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
- <text
- x="15.152"
- y="4.408"
- id="text1126"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Property Insurance Group</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="25.25cm"
- height="17.834999cm"
- viewBox="-0.157 2.112 25.093 19.947"
- id="svg2">
- <defs
- id="defs1143" />
- <rect
- width="16.360001"
- height="9.5100002"
- x="5.6950002"
- y="2.1370001"
- id="rect4"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 5.695,2.137 C 5.5293146,2.137 5.395,2.2713146 5.395,2.437"
- id="path6"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.355,2.437 C 22.355,2.2713146 22.220685,2.137 22.055,2.137"
- id="path8"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="16.959999"
- height="8.9099998"
- x="5.395"
- y="2.437"
- id="rect10"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 5.395,11.347 C 5.395,11.512685 5.5293146,11.647 5.695,11.647"
- id="path12"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.055,11.647 C 22.220685,11.647 22.355,11.512685 22.355,11.347"
- id="path14"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="5.6950002"
- y1="2.1370001"
- x2="22.055"
- y2="2.1370001"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="5.6950002"
- y1="11.647"
- x2="22.055"
- y2="11.647"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 5.695,2.137 C 5.5293146,2.137 5.395,2.2713146 5.395,2.437"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.355,2.437 C 22.355,2.2713146 22.220685,2.137 22.055,2.137"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="5.395"
- y1="2.437"
- x2="5.395"
- y2="11.347"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="22.355"
- y1="2.437"
- x2="22.355"
- y2="11.347"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 5.395,11.347 C 5.395,11.512685 5.5293146,11.647 5.695,11.647"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.055,11.647 C 22.220685,11.647 22.355,11.512685 22.355,11.347"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="11.6"
- height="7.875"
- x="13.168"
- y="12.047"
- id="rect32"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 13.168,12.047 C 13.002315,12.047 12.868,12.181315 12.868,12.347"
- id="path34"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 25.068,12.347 C 25.068,12.181315 24.933685,12.047 24.768,12.047"
- id="path36"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="12.2"
- height="7.2750001"
- x="12.868"
- y="12.347"
- id="rect38"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.868,19.622 C 12.868,19.787685 13.002315,19.922 13.168,19.922"
- id="path40"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 24.768,19.922 C 24.933685,19.922 25.068,19.787685 25.068,19.622"
- id="path42"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="13.168"
- y1="12.047"
- x2="24.768"
- y2="12.047"
- stroke="#000000"
- stroke-width="0.050"
- id="line44"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="13.168"
- y1="19.922001"
- x2="24.768"
- y2="19.922001"
- stroke="#000000"
- stroke-width="0.050"
- id="line46"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 13.168,12.047 C 13.002315,12.047 12.868,12.181315 12.868,12.347"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 25.068,12.347 C 25.068,12.181315 24.933685,12.047 24.768,12.047"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.868"
- y1="12.347"
- x2="12.868"
- y2="19.622"
- stroke="#000000"
- stroke-width="0.050"
- id="line52"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="25.068001"
- y1="12.347"
- x2="25.068001"
- y2="19.622"
- stroke="#000000"
- stroke-width="0.050"
- id="line54"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.868,19.622 C 12.868,19.787685 13.002315,19.922 13.168,19.922"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 24.768,19.922 C 24.933685,19.922 25.068,19.787685 25.068,19.622"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="11.225"
- height="7.8499999"
- x="0.168"
- y="12.047"
- id="rect60"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.168,12.047 C 0.0023145751,12.047 -0.132,12.181315 -0.132,12.347"
- id="path62"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.693,12.347 C 11.693,12.181315 11.558685,12.047 11.393,12.047"
- id="path64"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.825"
- height="7.25"
- x="-0.132"
- y="12.347"
- id="rect66"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -0.132,19.597 C -0.132,19.762685 0.0023145751,19.897 0.168,19.897"
- id="path68"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.393,19.897 C 11.558685,19.897 11.693,19.762685 11.693,19.597"
- id="path70"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="0.168"
- y1="12.047"
- x2="11.393"
- y2="12.047"
- stroke="#000000"
- stroke-width="0.050"
- id="line72"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.168"
- y1="19.896999"
- x2="11.393"
- y2="19.896999"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.168,12.047 C 0.0023145751,12.047 -0.132,12.181315 -0.132,12.347"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.693,12.347 C 11.693,12.181315 11.558685,12.047 11.393,12.047"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-0.132"
- y1="12.347"
- x2="-0.132"
- y2="19.597"
- stroke="#000000"
- stroke-width="0.050"
- id="line80"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.693"
- y1="12.347"
- x2="11.693"
- y2="19.597"
- stroke="#000000"
- stroke-width="0.050"
- id="line82"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -0.132,19.597 C -0.132,19.762685 0.0023145751,19.897 0.168,19.897"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.393,19.897 C 11.558685,19.897 11.693,19.762685 11.693,19.597"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.138,4.153 C 0.732,4.143 -0.057,4.345 0.054,4.777 C 0.165,5.209 0.695,5.305 0.917,5.18 C 1.138,5.055 0.571,5.785 1.656,5.977 C 2.741,6.169 3.295,5.861 3.135,5.641 C 2.975,5.42 4.084,6.159 4.602,5.737 C 5.119,5.314 4.072,4.911 4.293,4.969 C 4.515,5.026 5.193,4.95 4.971,4.23 C 4.749,3.51 2.753,4.067 2.975,3.961 C 3.197,3.855 2.642,3.328 1.952,3.433 C 1.262,3.539 1.213,3.73 1.139,4.153 L 1.138,4.153"
- id="path88"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <path
- d="M 1.138,4.153 C 0.732,4.143 -0.057,4.345 0.054,4.777 C 0.165,5.209 0.695,5.305 0.917,5.18 C 1.138,5.055 0.571,5.785 1.656,5.977 C 2.741,6.169 3.295,5.861 3.135,5.641 C 2.975,5.42 4.084,6.159 4.602,5.737 C 5.119,5.314 4.072,4.911 4.293,4.969 C 4.515,5.026 5.193,4.95 4.971,4.23 C 4.749,3.51 2.753,4.067 2.975,3.961 C 3.197,3.855 2.642,3.328 1.952,3.433 C 1.262,3.539 1.213,3.73 1.139,4.153 L 1.138,4.153"
- id="path90"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="2.1010001"
- y="4.848"
- id="text92"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
- <rect
- width="1.054"
- height="2.1070001"
- x="5.7290001"
- y="6.2870002"
- id="rect94"
- style="fill:#ff0000;stroke:none;stroke-width:0" />
- <polygon
- points="5.729,6.287 6.783,6.287 6.915,6.156 5.861,6.156 5.729,6.287 "
- id="polygon96"
- style="fill:#ff0000;stroke:none;stroke-width:0.1" />
- <polygon
- points="6.783,6.287 6.915,6.156 6.915,8.263 6.783,8.394 6.783,6.287 "
- id="polygon98"
- style="fill:#ff0000;stroke:none;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="6.4980001"
- x2="6.783"
- y2="6.4980001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line100"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="6.3660002"
- x2="6.783"
- y2="6.4980001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line102"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="6.2870002"
- x2="6.0450001"
- y2="6.4980001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line104"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="6.2870002"
- x2="6.177"
- y2="6.1560001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line106"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="6.9190001"
- x2="6.783"
- y2="6.9190001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line108"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="6.7880001"
- x2="6.783"
- y2="6.9190001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line110"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.467"
- y1="6.4980001"
- x2="6.467"
- y2="6.9190001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line112"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="7.3410001"
- x2="6.783"
- y2="7.3410001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line114"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="7.2090001"
- x2="6.783"
- y2="7.3410001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line116"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="6.9190001"
- x2="6.0450001"
- y2="7.3410001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line118"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="7.7620001"
- x2="6.783"
- y2="7.7620001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line120"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="7.631"
- x2="6.783"
- y2="7.7620001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line122"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.467"
- y1="7.3410001"
- x2="6.467"
- y2="7.7620001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line124"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="8.184"
- x2="6.783"
- y2="8.184"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line126"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.915"
- y1="8.052"
- x2="6.783"
- y2="8.184"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line128"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.0450001"
- y1="7.7620001"
- x2="6.0450001"
- y2="8.184"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line130"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="6.467"
- y1="8.184"
- x2="6.467"
- y2="8.3940001"
- stroke="#FFFFFF"
- stroke-width="0.100"
- id="line132"
- style="stroke:#ffffff;stroke-width:0.1" />
- <line
- x1="5.7290001"
- y1="6.2870002"
- x2="6.783"
- y2="6.2870002"
- stroke="#000000"
- stroke-width="0.050"
- id="line134"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="6.783"
- y1="8.3940001"
- x2="6.783"
- y2="6.2870002"
- stroke="#000000"
- stroke-width="0.050"
- id="line136"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="6.783"
- y1="6.2870002"
- x2="6.915"
- y2="6.1560001"
- stroke="#000000"
- stroke-width="0.050"
- id="line138"
- style="stroke:#000000;stroke-width:0.05" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.050"
- points="5.729,6.287 5.861,6.156 6.915,6.156 6.915,8.263 6.783,8.394 5.729,8.394 5.729,6.287 "
- id="polyline140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="2.0050001"
- height="6.0149999"
- x="8.4580002"
- y="4.1360002"
- id="rect142"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.0050001"
- height="6.0149999"
- x="8.4580002"
- y="4.1360002"
- id="rect144"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.0050001"
- height="6.0149999"
- x="8.4580002"
- y="4.1360002"
- id="rect146"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.604"
- height="2.4059999"
- x="8.6590004"
- y="4.3369999"
- id="rect148"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.604"
- height="2.4059999"
- x="8.6590004"
- y="4.3369999"
- id="rect150"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.604"
- height="2.4059999"
- x="8.6590004"
- y="4.3369999"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="4.7379999"
- x2="10.263"
- y2="4.7379999"
- stroke="#000000"
- stroke-width="0.010"
- id="line154"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.263"
- y1="5.1389999"
- x2="8.6590004"
- y2="5.1389999"
- stroke="#000000"
- stroke-width="0.010"
- id="line156"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="5.54"
- x2="10.263"
- y2="5.54"
- stroke="#000000"
- stroke-width="0.010"
- id="line158"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="5.941"
- x2="10.263"
- y2="5.941"
- stroke="#000000"
- stroke-width="0.010"
- id="line160"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.263"
- y1="6.342"
- x2="8.6590004"
- y2="6.342"
- stroke="#000000"
- stroke-width="0.010"
- id="line162"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.103"
- height="0.60100001"
- x="8.6590004"
- y="6.9429998"
- id="rect164"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.103"
- height="0.60100001"
- x="8.6590004"
- y="6.9429998"
- id="rect166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.103"
- height="0.60100001"
- x="8.6590004"
- y="6.9429998"
- id="rect168"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.4580002"
- y1="7.9460001"
- x2="10.463"
- y2="7.9460001"
- stroke="#000000"
- stroke-width="0.010"
- id="line170"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.1"
- height="0.1"
- x="9.3610001"
- y="8.1459999"
- id="rect172"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.1"
- height="0.1"
- x="9.3610001"
- y="8.1459999"
- id="rect174"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.1"
- height="0.1"
- x="9.3610001"
- y="8.1459999"
- id="rect176"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.1"
- height="0.1"
- x="9.7620001"
- y="8.1459999"
- id="rect178"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.1"
- height="0.1"
- x="9.7620001"
- y="8.1459999"
- id="rect180"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.1"
- height="0.1"
- x="9.7620001"
- y="8.1459999"
- id="rect182"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.1"
- height="0.1"
- x="10.163"
- y="8.1459999"
- id="rect184"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.1"
- height="0.1"
- x="10.163"
- y="8.1459999"
- id="rect186"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.1"
- height="0.1"
- x="10.163"
- y="8.1459999"
- id="rect188"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.2"
- height="0.2"
- x="10.062"
- y="7.5450001"
- id="rect190"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.2"
- height="0.2"
- x="10.062"
- y="7.5450001"
- id="rect192"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.2"
- height="0.2"
- x="10.062"
- y="7.5450001"
- id="rect194"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.6590004"
- y1="7.244"
- x2="9.7620001"
- y2="7.244"
- stroke="#000000"
- stroke-width="0.010"
- id="line196"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.301"
- height="0.301"
- x="8.6590004"
- y="8.0459995"
- id="rect198"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.301"
- height="0.301"
- x="8.6590004"
- y="8.0459995"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.301"
- height="0.301"
- x="8.6590004"
- y="8.0459995"
- id="rect202"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.403"
- height="0.1"
- x="8.7589998"
- y="6.4419999"
- id="rect204"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.403"
- height="0.1"
- x="8.7589998"
- y="6.4419999"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.403"
- height="0.1"
- x="8.7589998"
- y="6.4419999"
- id="rect208"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.7589998"
- y1="7.0430002"
- x2="9.6610003"
- y2="7.0430002"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.6610003"
- y1="7.1440001"
- x2="9.5609999"
- y2="7.1440001"
- stroke="#000000"
- stroke-width="0.010"
- id="line212"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.7589998"
- y1="7.1440001"
- x2="8.8590002"
- y2="7.1440001"
- stroke="#000000"
- stroke-width="0.010"
- id="line214"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.50099999"
- height="0.1"
- x="8.96"
- y="7.0430002"
- id="rect216"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.50099999"
- height="0.1"
- x="8.96"
- y="7.0430002"
- id="rect218"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.50099999"
- height="0.1"
- x="8.96"
- y="7.0430002"
- id="rect220"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.7589998"
- y1="6.6420002"
- x2="8.8590002"
- y2="6.6420002"
- stroke="#000000"
- stroke-width="0.010"
- id="line222"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.96"
- y1="6.6420002"
- x2="9.0600004"
- y2="6.6420002"
- stroke="#000000"
- stroke-width="0.010"
- id="line224"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.9619999"
- y1="6.6420002"
- x2="10.163"
- y2="6.6420002"
- stroke="#000000"
- stroke-width="0.010"
- id="line226"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="10.051"
- x2="10.363"
- y2="10.051"
- stroke="#000000"
- stroke-width="0.010"
- id="line228"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.9510002"
- x2="8.559"
- y2="9.9510002"
- stroke="#000000"
- stroke-width="0.010"
- id="line230"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.8500004"
- x2="10.363"
- y2="9.8500004"
- stroke="#000000"
- stroke-width="0.010"
- id="line232"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.75"
- x2="8.559"
- y2="9.75"
- stroke="#000000"
- stroke-width="0.010"
- id="line234"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.6499996"
- x2="10.363"
- y2="9.6499996"
- stroke="#000000"
- stroke-width="0.010"
- id="line236"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.5500002"
- x2="8.559"
- y2="9.5500002"
- stroke="#000000"
- stroke-width="0.010"
- id="line238"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.4490004"
- x2="10.363"
- y2="9.4490004"
- stroke="#000000"
- stroke-width="0.010"
- id="line240"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.349"
- x2="8.559"
- y2="9.349"
- stroke="#000000"
- stroke-width="0.010"
- id="line242"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.2489996"
- x2="10.363"
- y2="9.2489996"
- stroke="#000000"
- stroke-width="0.010"
- id="line244"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="9.1490002"
- x2="8.559"
- y2="9.1490002"
- stroke="#000000"
- stroke-width="0.010"
- id="line246"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="9.0480003"
- x2="10.363"
- y2="9.0480003"
- stroke="#000000"
- stroke-width="0.010"
- id="line248"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="8.948"
- x2="8.559"
- y2="8.948"
- stroke="#000000"
- stroke-width="0.010"
- id="line250"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.559"
- y1="8.8479996"
- x2="10.363"
- y2="8.8479996"
- stroke="#000000"
- stroke-width="0.010"
- id="line252"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.363"
- y1="8.7480001"
- x2="8.559"
- y2="8.7480001"
- stroke="#000000"
- stroke-width="0.010"
- id="line254"
- style="stroke:#000000;stroke-width:0.01" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="2.299,6.038 2.299,7.250 5.700,7.250 5.700,7.300 "
- id="polyline256"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.875"
- y1="7.3000002"
- x2="8.4250002"
- y2="7.2750001"
- stroke="#000000"
- stroke-width="0.100"
- id="line258"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.454"
- height="1.283"
- x="11.484"
- y="4.0939999"
- id="rect260"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.211"
- cy="5.3759999"
- rx="0.727"
- ry="0.214"
- id="ellipse262"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.211"
- cy="4.0939999"
- rx="0.727"
- ry="0.214"
- id="ellipse264"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.211"
- cy="4.0939999"
- rx="0.727"
- ry="0.214"
- id="ellipse266"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.938,4.094 L 12.938,5.376 C 12.938,5.494 12.613,5.59 12.211,5.59 C 11.81,5.59 11.484,5.494 11.484,5.376 L 11.484,4.094"
- id="path268"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.3329999"
- height="1.176"
- x="11.484"
- y="6.493"
- id="rect270"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.15"
- cy="7.6690001"
- rx="0.66600001"
- ry="0.19599999"
- id="ellipse272"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.15"
- cy="6.493"
- rx="0.66600001"
- ry="0.19599999"
- id="ellipse274"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.15"
- cy="6.493"
- rx="0.66600001"
- ry="0.19599999"
- id="ellipse276"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.817,6.493 L 12.817,7.669 C 12.817,7.777 12.518,7.865 12.15,7.865 C 11.782,7.865 11.484,7.777 11.484,7.669 L 11.484,6.493"
- id="path278"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.475"
- y1="4.6750002"
- x2="11.55"
- y2="4.6750002"
- stroke="#000000"
- stroke-width="0.100"
- id="line280"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.45"
- y1="7.0250001"
- x2="11.455"
- y2="6.9970002"
- stroke="#000000"
- stroke-width="0.100"
- id="line282"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.4"
- y1="8.8000002"
- x2="21.017"
- y2="8.7969999"
- stroke="#000000"
- stroke-width="0.100"
- id="line284"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="20.954"
- y1="8.7969999"
- x2="20.952999"
- y2="7.9260001"
- stroke="#000000"
- stroke-width="0.100"
- id="line286"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="15.678"
- y1="8.7980003"
- x2="15.678"
- y2="7.9169998"
- stroke="#000000"
- stroke-width="0.100"
- id="line288"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="15.68"
- y1="8.7980003"
- x2="15.68"
- y2="9.8470001"
- stroke="#000000"
- stroke-width="0.100"
- id="line290"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.254"
- y1="8.7980003"
- x2="18.253"
- y2="7.9260001"
- stroke="#000000"
- stroke-width="0.100"
- id="line292"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.243"
- y1="8.7980003"
- x2="18.243"
- y2="9.8999996"
- stroke="#000000"
- stroke-width="0.100"
- id="line294"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="20.966999"
- y1="8.7969999"
- x2="20.966999"
- y2="9.9189997"
- stroke="#000000"
- stroke-width="0.100"
- id="line296"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="11.825"
- y="10.625"
- id="rect298"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="1"
- height="1"
- x="11.825"
- y="10.625"
- id="rect300"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="11.825"
- y="10.625"
- id="rect302"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
- id="path304"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 12.387,10.787 C 12.387,11.287 12.487,11.187 11.987,11.187"
- id="path306"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
- id="polygon308"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.435,10.865 12.385,10.765 12.335,10.865 12.435,10.865 "
- id="polygon310"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
- id="polygon312"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.065,11.135 11.965,11.185 12.065,11.235 12.065,11.135 "
- id="polygon314"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
- id="path316"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 12.684,11.068 C 12.184,11.068 12.284,10.968 12.284,11.468"
- id="path318"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
- id="polygon320"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.595,11.115 12.695,11.065 12.595,11.015 12.595,11.115 "
- id="polygon322"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
- id="polygon324"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.225,11.385 12.275,11.485 12.325,11.385 12.225,11.385 "
- id="polygon326"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="12.325"
- y1="8.8249998"
- x2="12.325"
- y2="10.625"
- stroke="#000000"
- stroke-width="0.100"
- id="line328"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="15.15,10.178 15.095,10.201 14.93,10.615 14.93,10.823 15.012,10.892 16.228,10.892 16.311,10.823 16.311,10.615 16.145,10.201 16.09,10.178 15.15,10.178 "
- id="polygon330"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="15.15,10.178 15.095,10.201 14.93,10.615 14.93,10.823 15.012,10.892 16.228,10.892 16.311,10.823 16.311,10.615 16.145,10.201 16.09,10.178 15.15,10.178 "
- id="polygon332"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 14.957,10.546 L 15.012,10.569 L 16.228,10.569 L 16.283,10.546"
- id="path334"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.228,10.569 L 16.311,10.615"
- id="path336"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 14.93,10.615 L 15.012,10.569"
- id="path338"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="15.316,9.741 15.289,10.293 15.951,10.293 15.924,9.741 15.316,9.741 "
- id="polygon340"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="15.316,9.741 15.289,10.293 15.951,10.293 15.924,9.741 15.316,9.741 "
- id="polygon342"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="15.206,10.293 15.15,10.454 16.09,10.454 16.034,10.293 15.206,10.293 "
- id="polygon344"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="15.206,10.293 15.15,10.454 16.09,10.454 16.034,10.293 15.206,10.293 "
- id="polygon346"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="15.206"
- cy="10.65"
- rx="0.014"
- ry="0.014"
- id="ellipse348"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.206"
- cy="10.65"
- rx="0.014"
- ry="0.014"
- id="ellipse350"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.344"
- cy="10.65"
- rx="0.014"
- ry="0.014"
- id="ellipse352"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.344"
- cy="10.65"
- rx="0.014"
- ry="0.014"
- id="ellipse354"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.482"
- cy="10.65"
- rx="0.014"
- ry="0.014"
- id="ellipse356"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.482"
- cy="10.65"
- rx="0.014"
- ry="0.014"
- id="ellipse358"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.206"
- cy="10.708"
- rx="0.014"
- ry="0.014"
- id="ellipse360"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.206"
- cy="10.708"
- rx="0.014"
- ry="0.014"
- id="ellipse362"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.344"
- cy="10.708"
- rx="0.014"
- ry="0.014"
- id="ellipse364"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.344"
- cy="10.708"
- rx="0.014"
- ry="0.014"
- id="ellipse366"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.482"
- cy="10.708"
- rx="0.014"
- ry="0.014"
- id="ellipse368"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.482"
- cy="10.708"
- rx="0.014"
- ry="0.014"
- id="ellipse370"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.206"
- cy="10.765"
- rx="0.014"
- ry="0.014"
- id="ellipse372"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.206"
- cy="10.765"
- rx="0.014"
- ry="0.014"
- id="ellipse374"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.344"
- cy="10.765"
- rx="0.014"
- ry="0.014"
- id="ellipse376"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.344"
- cy="10.765"
- rx="0.014"
- ry="0.014"
- id="ellipse378"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.482"
- cy="10.765"
- rx="0.014"
- ry="0.014"
- id="ellipse380"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.482"
- cy="10.765"
- rx="0.014"
- ry="0.014"
- id="ellipse382"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.206"
- cy="10.823"
- rx="0.014"
- ry="0.014"
- id="ellipse384"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.206"
- cy="10.823"
- rx="0.014"
- ry="0.014"
- id="ellipse386"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.344"
- cy="10.823"
- rx="0.014"
- ry="0.014"
- id="ellipse388"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.344"
- cy="10.823"
- rx="0.014"
- ry="0.014"
- id="ellipse390"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.482"
- cy="10.823"
- rx="0.014"
- ry="0.014"
- id="ellipse392"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="15.482"
- cy="10.823"
- rx="0.014"
- ry="0.014"
- id="ellipse394"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.62"
- cy="10.661"
- rx="0.17299999"
- ry="0.055"
- id="ellipse396"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="15.62"
- cy="10.661"
- rx="0.17299999"
- ry="0.055"
- id="ellipse398"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="15.965"
- cy="10.661"
- rx="0.17299999"
- ry="0.055"
- id="ellipse400"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="15.965"
- cy="10.661"
- rx="0.17299999"
- ry="0.055"
- id="ellipse402"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.112"
- height="0.83399999"
- x="15.122"
- y="6.8239999"
- id="rect404"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="15.122"
- y="6.8239999"
- id="rect406"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="15.242"
- y="6.9439998"
- id="rect408"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="15.272,7.657 15.844,7.657 15.844,7.787 15.302,7.787 15.272,7.657 "
- id="polygon410"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.272,7.657 15.844,7.657 15.844,7.787 15.302,7.787 15.272,7.657 "
- id="polygon412"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="15.844,7.657 16.083,7.657 16.053,7.787 15.844,7.787 15.844,7.657 "
- id="polygon414"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.844,7.657 16.083,7.657 16.053,7.787 15.844,7.787 15.844,7.657 "
- id="polygon416"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.883"
- y="7.6960001"
- id="rect418"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.883"
- y="7.6960001"
- id="rect420"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="15.566,7.787 15.789,7.787 15.789,7.852 15.9,7.852 15.9,7.917 15.455,7.917 15.455,7.852 15.566,7.852 15.566,7.787 "
- id="polygon422"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.566,7.787 15.789,7.787 15.789,7.852 15.9,7.852 15.9,7.917 15.455,7.917 15.455,7.852 15.566,7.852 15.566,7.787 "
- id="polygon424"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.698"
- y="6.8319998"
- id="rect426"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.698"
- y="6.8319998"
- id="rect428"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="17.818001"
- y="6.9530001"
- id="rect430"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="17.848,7.666 18.42,7.666 18.42,7.796 17.878,7.796 17.848,7.666 "
- id="polygon432"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.848,7.666 18.42,7.666 18.42,7.796 17.878,7.796 17.848,7.666 "
- id="polygon434"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.42,7.666 18.659,7.666 18.629,7.796 18.42,7.796 18.42,7.666 "
- id="polygon436"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.42,7.666 18.659,7.666 18.629,7.796 18.42,7.796 18.42,7.666 "
- id="polygon438"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.459"
- y="7.7049999"
- id="rect440"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.459"
- y="7.7049999"
- id="rect442"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.142,7.796 18.364,7.796 18.364,7.861 18.476,7.861 18.476,7.926 18.031,7.926 18.031,7.861 18.142,7.861 18.142,7.796 "
- id="polygon444"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.142,7.796 18.364,7.796 18.364,7.861 18.476,7.861 18.476,7.926 18.031,7.926 18.031,7.861 18.142,7.861 18.142,7.796 "
- id="polygon446"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="6.8319998"
- id="rect448"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="6.8319998"
- id="rect450"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="20.518"
- y="6.9530001"
- id="rect452"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
- id="polygon454"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.548,7.666 21.12,7.666 21.12,7.796 20.578,7.796 20.548,7.666 "
- id="polygon456"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
- id="polygon458"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="21.12,7.666 21.359,7.666 21.329,7.796 21.12,7.796 21.12,7.666 "
- id="polygon460"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="7.7049999"
- id="rect462"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="7.7049999"
- id="rect464"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
- id="polygon466"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.842,7.796 21.064,7.796 21.064,7.861 21.176,7.861 21.176,7.926 20.731,7.926 20.731,7.861 20.842,7.861 20.842,7.796 "
- id="polygon468"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.673"
- y="9.9320002"
- id="rect470"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="17.673"
- y="9.9320002"
- id="rect472"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="17.792999"
- y="10.053"
- id="rect474"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="17.823,10.766 18.395,10.766 18.395,10.896 17.853,10.896 17.823,10.766 "
- id="polygon476"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.823,10.766 18.395,10.766 18.395,10.896 17.853,10.896 17.823,10.766 "
- id="polygon478"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.395,10.766 18.634,10.766 18.604,10.896 18.395,10.896 18.395,10.766 "
- id="polygon480"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.395,10.766 18.634,10.766 18.604,10.896 18.395,10.896 18.395,10.766 "
- id="polygon482"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.434"
- y="10.805"
- id="rect484"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="18.434"
- y="10.805"
- id="rect486"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.117,10.896 18.339,10.896 18.339,10.961 18.451,10.961 18.451,11.026 18.006,11.026 18.006,10.961 18.117,10.961 18.117,10.896 "
- id="polygon488"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.117,10.896 18.339,10.896 18.339,10.961 18.451,10.961 18.451,11.026 18.006,11.026 18.006,10.961 18.117,10.961 18.117,10.896 "
- id="polygon490"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="9.8830004"
- id="rect492"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="20.398001"
- y="9.8830004"
- id="rect494"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="20.518"
- y="10.003"
- id="rect496"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="20.548,10.716 21.12,10.716 21.12,10.846 20.578,10.846 20.548,10.716 "
- id="polygon498"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.548,10.716 21.12,10.716 21.12,10.846 20.578,10.846 20.548,10.716 "
- id="polygon500"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="21.12,10.716 21.359,10.716 21.329,10.846 21.12,10.846 21.12,10.716 "
- id="polygon502"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="21.12,10.716 21.359,10.716 21.329,10.846 21.12,10.846 21.12,10.716 "
- id="polygon504"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="10.755"
- id="rect506"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="21.159"
- y="10.755"
- id="rect508"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="20.842,10.846 21.064,10.846 21.064,10.911 21.176,10.911 21.176,10.976 20.731,10.976 20.731,10.911 20.842,10.911 20.842,10.846 "
- id="polygon510"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.842,10.846 21.064,10.846 21.064,10.911 21.176,10.911 21.176,10.976 20.731,10.976 20.731,10.911 20.842,10.911 20.842,10.846 "
- id="polygon512"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1"
- height="1"
- x="18.872"
- y="12.033"
- id="rect514"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="1"
- height="1"
- x="18.872"
- y="12.033"
- id="rect516"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="18.872"
- y="12.033"
- id="rect518"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 19.434,12.194 C 19.434,12.694 19.534,12.594 19.034,12.594"
- id="path520"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 19.434,12.194 C 19.434,12.694 19.534,12.594 19.034,12.594"
- id="path522"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="19.482,12.273 19.432,12.173 19.383,12.273 19.482,12.273 "
- id="polygon524"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.482,12.273 19.432,12.173 19.383,12.273 19.482,12.273 "
- id="polygon526"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.112,12.543 19.012,12.593 19.112,12.643 19.112,12.543 "
- id="polygon528"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.112,12.543 19.012,12.593 19.112,12.643 19.112,12.543 "
- id="polygon530"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 19.731,12.476 C 19.231,12.476 19.331,12.376 19.331,12.876"
- id="path532"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 19.731,12.476 C 19.231,12.476 19.331,12.376 19.331,12.876"
- id="path534"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="19.642,12.523 19.742,12.473 19.642,12.423 19.642,12.523 "
- id="polygon536"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.642,12.523 19.742,12.473 19.642,12.423 19.642,12.523 "
- id="polygon538"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.272,12.793 19.322,12.893 19.372,12.793 19.272,12.793 "
- id="polygon540"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.272,12.793 19.322,12.893 19.372,12.793 19.272,12.793 "
- id="polygon542"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="3.1470001"
- y="12.082"
- id="rect544"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="1"
- height="1"
- x="3.1470001"
- y="12.082"
- id="rect546"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1"
- height="1"
- x="3.1470001"
- y="12.082"
- id="rect548"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.709,12.244 C 3.709,12.744 3.809,12.644 3.309,12.644"
- id="path550"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 3.709,12.244 C 3.709,12.744 3.809,12.644 3.309,12.644"
- id="path552"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.757,12.322 3.708,12.223 3.657,12.322 3.757,12.322 "
- id="polygon554"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.757,12.322 3.708,12.223 3.657,12.322 3.757,12.322 "
- id="polygon556"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.388,12.592 3.288,12.643 3.388,12.692 3.388,12.592 "
- id="polygon558"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.388,12.592 3.288,12.643 3.388,12.692 3.388,12.592 "
- id="polygon560"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 4.006,12.526 C 3.506,12.526 3.606,12.426 3.606,12.926"
- id="path562"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 4.006,12.526 C 3.506,12.526 3.606,12.426 3.606,12.926"
- id="path564"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.917,12.572 4.018,12.522 3.917,12.473 3.917,12.572 "
- id="polygon566"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.917,12.572 4.018,12.522 3.917,12.473 3.917,12.572 "
- id="polygon568"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.547,12.842 3.598,12.942 3.647,12.842 3.547,12.842 "
- id="polygon570"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.547,12.842 3.598,12.942 3.647,12.842 3.547,12.842 "
- id="polygon572"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="12.025,11.650 12.025,12.525 4.147,12.525 4.147,12.582 "
- id="polyline574"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="12.625,11.600 12.625,12.525 18.872,12.525 18.872,12.533 "
- id="polyline576"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="3.599"
- y1="14.358"
- x2="10.802"
- y2="14.35"
- stroke="#000000"
- stroke-width="0.100"
- id="line578"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="3.6489999"
- y1="14.357"
- x2="3.6500001"
- y2="15.35"
- stroke="#000000"
- stroke-width="0.100"
- id="line580"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="3.6489999"
- y1="14.357"
- x2="3.6470001"
- y2="13.082"
- stroke="#000000"
- stroke-width="0.100"
- id="line582"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.2719998"
- y1="14.355"
- x2="6.2729998"
- y2="15.321"
- stroke="#000000"
- stroke-width="0.100"
- id="line584"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="7.783"
- y1="14.353"
- x2="7.783"
- y2="14.368"
- stroke="#000000"
- stroke-width="0.100"
- id="line586"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.4709997"
- y1="14.353"
- x2="8.4729996"
- y2="15.393"
- stroke="#000000"
- stroke-width="0.100"
- id="line588"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.752"
- y1="14.35"
- x2="10.754"
- y2="15.35"
- stroke="#000000"
- stroke-width="0.100"
- id="line590"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.775"
- y1="14.325"
- x2="21.35"
- y2="14.325"
- stroke="#000000"
- stroke-width="0.100"
- id="line592"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="15.593"
- y1="14.325"
- x2="15.593"
- y2="15.325"
- stroke="#000000"
- stroke-width="0.100"
- id="line594"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.825"
- y1="14.325"
- x2="13.825"
- y2="15.325"
- stroke="#000000"
- stroke-width="0.100"
- id="line596"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.479"
- y1="14.325"
- x2="17.479"
- y2="15.325"
- stroke="#000000"
- stroke-width="0.100"
- id="line598"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.372"
- y1="14.325"
- x2="19.372"
- y2="13.033"
- stroke="#000000"
- stroke-width="0.100"
- id="line600"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.379999"
- y1="14.325"
- x2="19.379999"
- y2="15.322"
- stroke="#000000"
- stroke-width="0.100"
- id="line602"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="21.299999"
- y1="14.325"
- x2="21.299999"
- y2="15.375"
- stroke="#000000"
- stroke-width="0.100"
- id="line604"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.6670001"
- height="2.5"
- x="2.8169999"
- y="15.35"
- id="rect606"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.6670001"
- height="2.5"
- x="2.8169999"
- y="15.35"
- id="rect608"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.6670001"
- height="2.5"
- x="2.8169999"
- y="15.35"
- id="rect610"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3329999"
- height="1"
- x="2.9000001"
- y="15.433"
- id="rect612"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.3329999"
- height="1"
- x="2.9000001"
- y="15.433"
- id="rect614"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.3329999"
- height="1"
- x="2.9000001"
- y="15.433"
- id="rect616"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.9000001"
- y1="15.767"
- x2="4.2329998"
- y2="15.767"
- stroke="#000000"
- stroke-width="0.010"
- id="line618"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.2329998"
- y1="16.1"
- x2="2.9000001"
- y2="16.1"
- stroke="#000000"
- stroke-width="0.010"
- id="line620"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.917"
- height="0.5"
- x="3.0669999"
- y="16.517"
- id="rect622"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.917"
- height="0.5"
- x="3.0669999"
- y="16.517"
- id="rect624"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.917"
- height="0.5"
- x="3.0669999"
- y="16.517"
- id="rect626"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.8169999"
- y1="17.267"
- x2="4.4829998"
- y2="17.267"
- stroke="#000000"
- stroke-width="0.010"
- id="line628"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="3.983"
- y="17.1"
- id="rect630"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="3.983"
- y="17.1"
- id="rect632"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="3.983"
- y="17.1"
- id="rect634"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.1500001"
- y="17.1"
- id="rect636"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.1500001"
- y="17.1"
- id="rect638"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.1500001"
- y="17.1"
- id="rect640"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.3169999"
- y="17.1"
- id="rect642"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.3169999"
- y="17.1"
- id="rect644"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="4.3169999"
- y="17.1"
- id="rect646"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.167"
- height="0.167"
- x="4.2329998"
- y="16.85"
- id="rect648"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.167"
- height="0.167"
- x="4.2329998"
- y="16.85"
- id="rect650"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.167"
- height="0.167"
- x="4.2329998"
- y="16.85"
- id="rect652"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.0669999"
- y1="16.767"
- x2="3.983"
- y2="16.767"
- stroke="#000000"
- stroke-width="0.010"
- id="line654"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.25"
- height="0.25"
- x="4.1500001"
- y="16.517"
- id="rect656"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.25"
- height="0.25"
- x="4.1500001"
- y="16.517"
- id="rect658"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.25"
- height="0.25"
- x="4.1500001"
- y="16.517"
- id="rect660"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.1670001"
- height="0.082999997"
- x="2.983"
- y="16.183001"
- id="rect662"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.1670001"
- height="0.082999997"
- x="2.983"
- y="16.183001"
- id="rect664"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1670001"
- height="0.082999997"
- x="2.983"
- y="16.183001"
- id="rect666"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.1500001"
- y1="16.6"
- x2="3.9000001"
- y2="16.6"
- stroke="#000000"
- stroke-width="0.010"
- id="line668"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.417"
- height="0.082999997"
- x="3.3169999"
- y="16.6"
- id="rect670"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.417"
- height="0.082999997"
- x="3.3169999"
- y="16.6"
- id="rect672"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.417"
- height="0.082999997"
- x="3.3169999"
- y="16.6"
- id="rect674"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.983"
- y1="16.35"
- x2="4.1500001"
- y2="16.35"
- stroke="#000000"
- stroke-width="0.010"
- id="line676"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.9000001"
- y1="17.35"
- x2="4.4000001"
- y2="17.35"
- stroke="#000000"
- stroke-width="0.010"
- id="line678"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.4000001"
- y1="17.433001"
- x2="2.9000001"
- y2="17.433001"
- stroke="#000000"
- stroke-width="0.010"
- id="line680"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.9000001"
- y1="17.517"
- x2="4.4000001"
- y2="17.517"
- stroke="#000000"
- stroke-width="0.010"
- id="line682"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.4000001"
- y1="17.767"
- x2="2.9000001"
- y2="17.767"
- stroke="#000000"
- stroke-width="0.010"
- id="line684"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.9000001"
- y1="17.683001"
- x2="4.4000001"
- y2="17.683001"
- stroke="#000000"
- stroke-width="0.010"
- id="line686"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.4000001"
- y1="17.6"
- x2="2.9000001"
- y2="17.6"
- stroke="#000000"
- stroke-width="0.010"
- id="line688"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.983"
- y1="16.35"
- x2="3.0669999"
- y2="16.35"
- stroke="#000000"
- stroke-width="0.010"
- id="line690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.1500001"
- y1="16.35"
- x2="3.233"
- y2="16.35"
- stroke="#000000"
- stroke-width="0.010"
- id="line692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.1500001"
- y1="16.683001"
- x2="3.233"
- y2="16.683001"
- stroke="#000000"
- stroke-width="0.010"
- id="line694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.8169999"
- y1="16.683001"
- x2="3.9000001"
- y2="16.683001"
- stroke="#000000"
- stroke-width="0.010"
- id="line696"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.5"
- height="3"
- x="20.549999"
- y="15.375"
- id="rect698"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.5"
- height="3"
- x="20.549999"
- y="15.375"
- id="rect700"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.5"
- height="3"
- x="20.549999"
- y="15.375"
- id="rect702"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.2"
- height="1.2"
- x="20.700001"
- y="15.525"
- id="rect704"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.2"
- height="1.2"
- x="20.700001"
- y="15.525"
- id="rect706"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.2"
- height="1.2"
- x="20.700001"
- y="15.525"
- id="rect708"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.9"
- y1="15.825"
- x2="20.700001"
- y2="15.825"
- stroke="#000000"
- stroke-width="0.010"
- id="line710"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.700001"
- y1="16.125"
- x2="21.9"
- y2="16.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line712"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.9"
- y1="16.35"
- x2="20.700001"
- y2="16.35"
- stroke="#000000"
- stroke-width="0.010"
- id="line714"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="20.700001"
- y="16.875"
- id="rect716"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="20.700001"
- y="16.875"
- id="rect718"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.82499999"
- height="0.44999999"
- x="20.700001"
- y="16.875"
- id="rect720"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.549999"
- y1="17.4"
- x2="22.049999"
- y2="17.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line722"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.225"
- y="17.549999"
- id="rect724"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.225"
- y="17.549999"
- id="rect726"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.225"
- y="17.549999"
- id="rect728"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.525"
- y="17.549999"
- id="rect730"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.525"
- y="17.549999"
- id="rect732"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.525"
- y="17.549999"
- id="rect734"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.825001"
- y="17.549999"
- id="rect736"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.825001"
- y="17.549999"
- id="rect738"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.075000003"
- height="0.075000003"
- x="21.825001"
- y="17.549999"
- id="rect740"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="21.75"
- y="17.1"
- id="rect742"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="21.75"
- y="17.1"
- id="rect744"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.15000001"
- height="0.075000003"
- x="21.75"
- y="17.1"
- id="rect746"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.700001"
- y1="17.1"
- x2="21.525"
- y2="17.1"
- stroke="#000000"
- stroke-width="0.010"
- id="line748"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="20.700001"
- y="17.475"
- id="rect750"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="20.700001"
- y="17.475"
- id="rect752"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.22499999"
- height="0.22499999"
- x="20.700001"
- y="17.475"
- id="rect754"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.05"
- height="0.075000003"
- x="20.775"
- y="16.424999"
- id="rect756"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.05"
- height="0.075000003"
- x="20.775"
- y="16.424999"
- id="rect758"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.05"
- height="0.075000003"
- x="20.775"
- y="16.424999"
- id="rect760"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.775"
- y1="16.950001"
- x2="21.450001"
- y2="16.950001"
- stroke="#000000"
- stroke-width="0.010"
- id="line762"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.450001"
- y1="17.025"
- x2="21.375"
- y2="17.025"
- stroke="#000000"
- stroke-width="0.010"
- id="line764"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.775"
- y1="17.025"
- x2="20.85"
- y2="17.025"
- stroke="#000000"
- stroke-width="0.010"
- id="line766"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.375"
- height="0.075000003"
- x="20.924999"
- y="16.950001"
- id="rect768"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.375"
- height="0.075000003"
- x="20.924999"
- y="16.950001"
- id="rect770"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.375"
- height="0.075000003"
- x="20.924999"
- y="16.950001"
- id="rect772"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.775"
- y1="16.575001"
- x2="20.85"
- y2="16.575001"
- stroke="#000000"
- stroke-width="0.010"
- id="line774"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.924999"
- y1="16.575001"
- x2="21"
- y2="16.575001"
- stroke="#000000"
- stroke-width="0.010"
- id="line776"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.674999"
- y1="16.575001"
- x2="21.825001"
- y2="16.575001"
- stroke="#000000"
- stroke-width="0.010"
- id="line778"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.975"
- y1="18.299999"
- x2="20.625"
- y2="18.299999"
- stroke="#000000"
- stroke-width="0.010"
- id="line780"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.625"
- y1="18.225"
- x2="21.975"
- y2="18.225"
- stroke="#000000"
- stroke-width="0.010"
- id="line782"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.975"
- y1="18.15"
- x2="20.625"
- y2="18.15"
- stroke="#000000"
- stroke-width="0.010"
- id="line784"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.625"
- y1="18.075001"
- x2="21.975"
- y2="18.075001"
- stroke="#000000"
- stroke-width="0.010"
- id="line786"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.975"
- y1="18"
- x2="20.625"
- y2="18"
- stroke="#000000"
- stroke-width="0.010"
- id="line788"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.625"
- y1="17.924999"
- x2="21.975"
- y2="17.924999"
- stroke="#000000"
- stroke-width="0.010"
- id="line790"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.975"
- y1="17.85"
- x2="20.625"
- y2="17.85"
- stroke="#000000"
- stroke-width="0.010"
- id="line792"
- style="stroke:#000000;stroke-width:0.01" />
- <polygon
- points="5.796,15.735 5.738,15.759 5.562,16.197 5.562,16.416 5.65,16.489 6.935,16.489 7.023,16.416 7.023,16.197 6.847,15.759 6.789,15.735 5.796,15.735 "
- id="polygon794"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="5.796,15.735 5.738,15.759 5.562,16.197 5.562,16.416 5.65,16.489 6.935,16.489 7.023,16.416 7.023,16.197 6.847,15.759 6.789,15.735 5.796,15.735 "
- id="polygon796"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.592,16.124 L 5.65,16.149 L 6.935,16.149 L 6.993,16.124"
- id="path798"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.935,16.149 L 7.023,16.197"
- id="path800"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.562,16.197 L 5.65,16.149"
- id="path802"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.971,15.273 5.942,15.857 6.643,15.857 6.614,15.273 5.971,15.273 "
- id="polygon804"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="5.971,15.273 5.942,15.857 6.643,15.857 6.614,15.273 5.971,15.273 "
- id="polygon806"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.854,15.857 5.796,16.027 6.789,16.027 6.731,15.857 5.854,15.857 "
- id="polygon808"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="5.854,15.857 5.796,16.027 6.789,16.027 6.731,15.857 5.854,15.857 "
- id="polygon810"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="5.8540001"
- cy="16.233999"
- rx="0.015"
- ry="0.015"
- id="ellipse812"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.8540001"
- cy="16.233999"
- rx="0.015"
- ry="0.015"
- id="ellipse814"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6"
- cy="16.233999"
- rx="0.015"
- ry="0.015"
- id="ellipse816"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6"
- cy="16.233999"
- rx="0.015"
- ry="0.015"
- id="ellipse818"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1459999"
- cy="16.233999"
- rx="0.015"
- ry="0.015"
- id="ellipse820"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1459999"
- cy="16.233999"
- rx="0.015"
- ry="0.015"
- id="ellipse822"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.8540001"
- cy="16.295"
- rx="0.015"
- ry="0.015"
- id="ellipse824"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.8540001"
- cy="16.295"
- rx="0.015"
- ry="0.015"
- id="ellipse826"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6"
- cy="16.295"
- rx="0.015"
- ry="0.015"
- id="ellipse828"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6"
- cy="16.295"
- rx="0.015"
- ry="0.015"
- id="ellipse830"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1459999"
- cy="16.295"
- rx="0.015"
- ry="0.015"
- id="ellipse832"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1459999"
- cy="16.295"
- rx="0.015"
- ry="0.015"
- id="ellipse834"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.8540001"
- cy="16.355"
- rx="0.015"
- ry="0.015"
- id="ellipse836"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.8540001"
- cy="16.355"
- rx="0.015"
- ry="0.015"
- id="ellipse838"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6"
- cy="16.355"
- rx="0.015"
- ry="0.015"
- id="ellipse840"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6"
- cy="16.355"
- rx="0.015"
- ry="0.015"
- id="ellipse842"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1459999"
- cy="16.355"
- rx="0.015"
- ry="0.015"
- id="ellipse844"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1459999"
- cy="16.355"
- rx="0.015"
- ry="0.015"
- id="ellipse846"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.8540001"
- cy="16.416"
- rx="0.015"
- ry="0.015"
- id="ellipse848"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.8540001"
- cy="16.416"
- rx="0.015"
- ry="0.015"
- id="ellipse850"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6"
- cy="16.416"
- rx="0.015"
- ry="0.015"
- id="ellipse852"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6"
- cy="16.416"
- rx="0.015"
- ry="0.015"
- id="ellipse854"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.1459999"
- cy="16.416"
- rx="0.015"
- ry="0.015"
- id="ellipse856"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.1459999"
- cy="16.416"
- rx="0.015"
- ry="0.015"
- id="ellipse858"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.2919998"
- cy="16.246"
- rx="0.183"
- ry="0.057999998"
- id="ellipse860"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.2919998"
- cy="16.246"
- rx="0.183"
- ry="0.057999998"
- id="ellipse862"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.658"
- cy="16.246"
- rx="0.183"
- ry="0.057999998"
- id="ellipse864"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.658"
- cy="16.246"
- rx="0.183"
- ry="0.057999998"
- id="ellipse866"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <polygon
- points="18.871,15.81 18.813,15.834 18.637,16.272 18.637,16.491 18.725,16.564 20.01,16.564 20.098,16.491 20.098,16.272 19.922,15.834 19.864,15.81 18.871,15.81 "
- id="polygon868"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="18.871,15.81 18.813,15.834 18.637,16.272 18.637,16.491 18.725,16.564 20.01,16.564 20.098,16.491 20.098,16.272 19.922,15.834 19.864,15.81 18.871,15.81 "
- id="polygon870"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 18.667,16.199 L 18.725,16.224 L 20.01,16.224 L 20.068,16.199"
- id="path872"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 20.01,16.224 L 20.098,16.272"
- id="path874"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 18.637,16.272 L 18.725,16.224"
- id="path876"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="19.046,15.348 19.017,15.932 19.718,15.932 19.689,15.348 19.046,15.348 "
- id="polygon878"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="19.046,15.348 19.017,15.932 19.718,15.932 19.689,15.348 19.046,15.348 "
- id="polygon880"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="18.929,15.932 18.871,16.102 19.864,16.102 19.806,15.932 18.929,15.932 "
- id="polygon882"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="18.929,15.932 18.871,16.102 19.864,16.102 19.806,15.932 18.929,15.932 "
- id="polygon884"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="18.929001"
- cy="16.309"
- rx="0.015"
- ry="0.015"
- id="ellipse886"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.929001"
- cy="16.309"
- rx="0.015"
- ry="0.015"
- id="ellipse888"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.075001"
- cy="16.309"
- rx="0.015"
- ry="0.015"
- id="ellipse890"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.075001"
- cy="16.309"
- rx="0.015"
- ry="0.015"
- id="ellipse892"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.221001"
- cy="16.309"
- rx="0.015"
- ry="0.015"
- id="ellipse894"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.221001"
- cy="16.309"
- rx="0.015"
- ry="0.015"
- id="ellipse896"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.929001"
- cy="16.370001"
- rx="0.015"
- ry="0.015"
- id="ellipse898"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.929001"
- cy="16.370001"
- rx="0.015"
- ry="0.015"
- id="ellipse900"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.075001"
- cy="16.370001"
- rx="0.015"
- ry="0.015"
- id="ellipse902"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.075001"
- cy="16.370001"
- rx="0.015"
- ry="0.015"
- id="ellipse904"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.221001"
- cy="16.370001"
- rx="0.015"
- ry="0.015"
- id="ellipse906"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.221001"
- cy="16.370001"
- rx="0.015"
- ry="0.015"
- id="ellipse908"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.929001"
- cy="16.43"
- rx="0.015"
- ry="0.015"
- id="ellipse910"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.929001"
- cy="16.43"
- rx="0.015"
- ry="0.015"
- id="ellipse912"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.075001"
- cy="16.43"
- rx="0.015"
- ry="0.015"
- id="ellipse914"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.075001"
- cy="16.43"
- rx="0.015"
- ry="0.015"
- id="ellipse916"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.221001"
- cy="16.43"
- rx="0.015"
- ry="0.015"
- id="ellipse918"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.221001"
- cy="16.43"
- rx="0.015"
- ry="0.015"
- id="ellipse920"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="18.929001"
- cy="16.490999"
- rx="0.015"
- ry="0.015"
- id="ellipse922"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="18.929001"
- cy="16.490999"
- rx="0.015"
- ry="0.015"
- id="ellipse924"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.075001"
- cy="16.490999"
- rx="0.015"
- ry="0.015"
- id="ellipse926"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.075001"
- cy="16.490999"
- rx="0.015"
- ry="0.015"
- id="ellipse928"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.221001"
- cy="16.490999"
- rx="0.015"
- ry="0.015"
- id="ellipse930"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="19.221001"
- cy="16.490999"
- rx="0.015"
- ry="0.015"
- id="ellipse932"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.367001"
- cy="16.320999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse934"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="19.367001"
- cy="16.320999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse936"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="19.733"
- cy="16.320999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse938"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="19.733"
- cy="16.320999"
- rx="0.183"
- ry="0.057999998"
- id="ellipse940"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.112"
- height="0.83399999"
- x="16.948"
- y="15.332"
- id="rect942"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="16.948"
- y="15.332"
- id="rect944"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="17.068001"
- y="15.453"
- id="rect946"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="17.098,16.166 17.67,16.166 17.67,16.296 17.128,16.296 17.098,16.166 "
- id="polygon948"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.098,16.166 17.67,16.166 17.67,16.296 17.128,16.296 17.098,16.166 "
- id="polygon950"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.67,16.166 17.909,16.166 17.879,16.296 17.67,16.296 17.67,16.166 "
- id="polygon952"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.67,16.166 17.909,16.166 17.879,16.296 17.67,16.296 17.67,16.166 "
- id="polygon954"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="17.709"
- y="16.205"
- id="rect956"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="17.709"
- y="16.205"
- id="rect958"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="17.392,16.296 17.614,16.296 17.614,16.361 17.726,16.361 17.726,16.426 17.281,16.426 17.281,16.361 17.392,16.361 17.392,16.296 "
- id="polygon960"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.392,16.296 17.614,16.296 17.614,16.361 17.726,16.361 17.726,16.426 17.281,16.426 17.281,16.361 17.392,16.361 17.392,16.296 "
- id="polygon962"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="15.073"
- y="15.307"
- id="rect964"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="15.073"
- y="15.307"
- id="rect966"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="15.193"
- y="15.428"
- id="rect968"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="15.223,16.141 15.795,16.141 15.795,16.271 15.253,16.271 15.223,16.141 "
- id="polygon970"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.223,16.141 15.795,16.141 15.795,16.271 15.253,16.271 15.223,16.141 "
- id="polygon972"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="15.795,16.141 16.034,16.141 16.004,16.271 15.795,16.271 15.795,16.141 "
- id="polygon974"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.795,16.141 16.034,16.141 16.004,16.271 15.795,16.271 15.795,16.141 "
- id="polygon976"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.834"
- y="16.18"
- id="rect978"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="15.834"
- y="16.18"
- id="rect980"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="15.517,16.271 15.739,16.271 15.739,16.336 15.851,16.336 15.851,16.401 15.406,16.401 15.406,16.336 15.517,16.336 15.517,16.271 "
- id="polygon982"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="15.517,16.271 15.739,16.271 15.739,16.336 15.851,16.336 15.851,16.401 15.406,16.401 15.406,16.336 15.517,16.336 15.517,16.271 "
- id="polygon984"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="13.298"
- y="15.332"
- id="rect986"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="13.298"
- y="15.332"
- id="rect988"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="13.418"
- y="15.453"
- id="rect990"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="13.448,16.166 14.02,16.166 14.02,16.296 13.478,16.296 13.448,16.166 "
- id="polygon992"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="13.448,16.166 14.02,16.166 14.02,16.296 13.478,16.296 13.448,16.166 "
- id="polygon994"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="14.02,16.166 14.259,16.166 14.229,16.296 14.02,16.296 14.02,16.166 "
- id="polygon996"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="14.02,16.166 14.259,16.166 14.229,16.296 14.02,16.296 14.02,16.166 "
- id="polygon998"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="14.059"
- y="16.205"
- id="rect1000"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="14.059"
- y="16.205"
- id="rect1002"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="13.742,16.296 13.964,16.296 13.964,16.361 14.076,16.361 14.076,16.426 13.631,16.426 13.631,16.361 13.742,16.361 13.742,16.296 "
- id="polygon1004"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="13.742,16.296 13.964,16.296 13.964,16.361 14.076,16.361 14.076,16.426 13.631,16.426 13.631,16.361 13.742,16.361 13.742,16.296 "
- id="polygon1006"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="10.148"
- y="15.357"
- id="rect1008"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="10.148"
- y="15.357"
- id="rect1010"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="10.268"
- y="15.478"
- id="rect1012"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="10.298,16.191 10.87,16.191 10.87,16.321 10.328,16.321 10.298,16.191 "
- id="polygon1014"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.298,16.191 10.87,16.191 10.87,16.321 10.328,16.321 10.298,16.191 "
- id="polygon1016"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="10.87,16.191 11.109,16.191 11.079,16.321 10.87,16.321 10.87,16.191 "
- id="polygon1018"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.87,16.191 11.109,16.191 11.079,16.321 10.87,16.321 10.87,16.191 "
- id="polygon1020"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="10.909"
- y="16.23"
- id="rect1022"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="10.909"
- y="16.23"
- id="rect1024"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="10.592,16.321 10.814,16.321 10.814,16.386 10.926,16.386 10.926,16.451 10.481,16.451 10.481,16.386 10.592,16.386 10.592,16.321 "
- id="polygon1026"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="10.592,16.321 10.814,16.321 10.814,16.386 10.926,16.386 10.926,16.451 10.481,16.451 10.481,16.386 10.592,16.386 10.592,16.321 "
- id="polygon1028"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.112"
- height="0.83399999"
- x="7.948"
- y="15.383"
- id="rect1030"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.112"
- height="0.83399999"
- x="7.948"
- y="15.383"
- id="rect1032"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.87099999"
- height="0.574"
- x="8.0679998"
- y="15.503"
- id="rect1034"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="8.098,16.216 8.67,16.216 8.67,16.346 8.128,16.346 8.098,16.216 "
- id="polygon1036"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.098,16.216 8.67,16.216 8.67,16.346 8.128,16.346 8.098,16.216 "
- id="polygon1038"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.67,16.216 8.909,16.216 8.879,16.346 8.67,16.346 8.67,16.216 "
- id="polygon1040"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.67,16.216 8.909,16.216 8.879,16.346 8.67,16.346 8.67,16.216 "
- id="polygon1042"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="8.7089996"
- y="16.254999"
- id="rect1044"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.052000001"
- height="0.052000001"
- x="8.7089996"
- y="16.254999"
- id="rect1046"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.392,16.346 8.614,16.346 8.614,16.411 8.726,16.411 8.726,16.476 8.281,16.476 8.281,16.411 8.392,16.411 8.392,16.346 "
- id="polygon1048"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.392,16.346 8.614,16.346 8.614,16.411 8.726,16.411 8.726,16.476 8.281,16.476 8.281,16.411 8.392,16.411 8.392,16.346 "
- id="polygon1050"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="1.378"
- height="1.216"
- x="0.33899999"
- y="15.46"
- id="rect1052"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="1.028"
- cy="16.676001"
- rx="0.68900001"
- ry="0.20299999"
- id="ellipse1054"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.028"
- cy="15.46"
- rx="0.68900001"
- ry="0.20299999"
- id="ellipse1056"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.028"
- cy="15.46"
- rx="0.68900001"
- ry="0.20299999"
- id="ellipse1058"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 1.717,15.46 L 1.717,16.676 C 1.717,16.788 1.408,16.878 1.028,16.878 C 0.647,16.878 0.339,16.788 0.339,16.676 L 0.339,15.46"
- id="path1060"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.673"
- y1="15.932"
- x2="2.848"
- y2="15.932"
- stroke="#000000"
- stroke-width="0.100"
- id="line1062"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.362"
- height="1.202"
- x="23.125999"
- y="15.633"
- id="rect1064"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="23.806999"
- cy="16.834"
- rx="0.68099999"
- ry="0.2"
- id="ellipse1066"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="23.806999"
- cy="15.633"
- rx="0.68099999"
- ry="0.2"
- id="ellipse1068"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="23.806999"
- cy="15.633"
- rx="0.68099999"
- ry="0.2"
- id="ellipse1070"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 24.488,15.633 L 24.488,16.834 C 24.488,16.945 24.183,17.035 23.807,17.035 C 23.431,17.035 23.126,16.945 23.126,16.834 L 23.126,15.633"
- id="path1072"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="22.098"
- y1="16.082001"
- x2="23.062"
- y2="16.047001"
- stroke="#000000"
- stroke-width="0.100"
- id="line1074"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="11.846"
- y="4.9720001"
- id="text1076"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
- <text
- x="23.485001"
- y="16.497"
- id="text1078"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
- <text
- x="0.70999998"
- y="16.322001"
- id="text1080"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">apps</text>
- <text
- x="11.844"
- y="7.3400002"
- id="text1082"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">data</text>
- <text
- x="5.848"
- y="8.9899998"
- id="text1084"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">firewall</text>
- <text
- x="1.897"
- y="12.74"
- id="text1086"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
- <text
- x="20.27"
- y="12.665"
- id="text1088"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
- <text
- x="10.52"
- y="11.465"
- id="text1090"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">router</text>
- <text
- x="17.094999"
- y="6.4029999"
- id="text1092"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.0.0/22</text>
- <text
- x="6.4499998"
- y="14.065"
- id="text1094"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.4.0/22</text>
- <text
- x="14.906"
- y="13.965"
- id="text1096"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network: 172.16.8.0/24</text>
- <text
- x="15.58"
- y="3.178"
- id="text1098"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: MEGANET2</text>
- <text
- x="8.2959995"
- y="2.983"
- id="text1100"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC Server:</text>
- <text
- x="8.0710001"
- y="3.5829999"
- id="text1102"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">MASSIVE-PDC</text>
- <text
- x="1.272"
- y="14.296"
- id="text1104"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="0.82099998"
- y="14.896"
- id="text1106"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG1-BDC</text>
- <text
- x="22.659"
- y="14.321"
- id="text1108"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="22.207001"
- y="14.921"
- id="text1110"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
- <text
- x="7.5240002"
- y="7.9169998"
- id="text1112"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth0</text>
- <text
- x="10.847"
- y="9.3170004"
- id="text1114"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">eth1</text>
- <rect
- width="1.432"
- height="1.263"
- x="13.118"
- y="5.283"
- id="rect1116"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="13.833"
- cy="6.5469999"
- rx="0.71600002"
- ry="0.211"
- id="ellipse1118"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.833"
- cy="5.283"
- rx="0.71600002"
- ry="0.211"
- id="ellipse1120"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.833"
- cy="5.283"
- rx="0.71600002"
- ry="0.211"
- id="ellipse1122"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 14.549,5.283 L 14.549,6.547 C 14.549,6.663 14.229,6.757 13.833,6.757 C 13.438,6.757 13.118,6.663 13.118,6.547 L 13.118,5.283"
- id="path1124"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.473"
- y1="5.9720001"
- x2="13.098"
- y2="5.947"
- stroke="#000000"
- stroke-width="0.100"
- id="line1126"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="13.527"
- y="6.197"
- id="text1128"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ldap</text>
- <text
- x="9.408"
- y="19.547001"
- id="text1130"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
- <text
- x="22.794001"
- y="19.542"
- id="text1132"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">150 Users</text>
- <text
- x="17.837999"
- y="5.6919999"
- id="text1134"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">300 Users</text>
- <text
- x="0.83999997"
- y="19.539"
- id="text1136"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Accounting</text>
- <text
- x="14.316"
- y="19.514"
- id="text1138"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Financial Services</text>
- <text
- x="15.63"
- y="4.5640001"
- id="text1140"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Property Insurance Group</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="17.290001cm"
- height="13.335cm"
- viewBox="23.46 19.665 40.75 33"
- id="svg2">
- <defs
- id="defs177" />
- <rect
- width="2"
- height="2"
- x="29.1"
- y="23"
- id="rect4"
- style="fill:#fff4db;stroke:none;stroke-width:0" />
- <rect
- width="2"
- height="2"
- x="29.1"
- y="23"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2"
- height="2"
- x="32.035"
- y="27.59"
- id="rect8"
- style="fill:#d8d8d8;stroke:none;stroke-width:0" />
- <rect
- width="2"
- height="2"
- x="32.035"
- y="27.59"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2"
- height="2.04"
- x="29.184999"
- y="27.549999"
- id="rect12"
- style="fill:#d0d0d0;stroke:none;stroke-width:0" />
- <rect
- width="2"
- height="2.04"
- x="29.184999"
- y="27.549999"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.8399999"
- height="1.735"
- x="23.51"
- y="23.139999"
- id="rect16"
- style="fill:#a9d8cb;stroke:none;stroke-width:0" />
- <rect
- width="2.8399999"
- height="1.735"
- x="23.51"
- y="23.139999"
- id="rect18"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.825"
- height="1.885"
- x="32.674999"
- y="20.940001"
- id="rect20"
- style="fill:#dedede;stroke:none;stroke-width:0" />
- <rect
- width="2.825"
- height="1.885"
- x="32.674999"
- y="20.940001"
- id="rect22"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.6500001"
- height="2.01"
- x="37.799999"
- y="19.715"
- id="rect24"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.6500001"
- height="2.01"
- x="37.799999"
- y="19.715"
- id="rect26"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.3"
- height="2.0150001"
- x="38.025002"
- y="22.1"
- id="rect28"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.3"
- height="2.0150001"
- x="38.025002"
- y="22.1"
- id="rect30"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.25"
- height="2.0599999"
- x="35.150002"
- y="27.565001"
- id="rect32"
- style="fill:#d8d8d8;stroke:none;stroke-width:0" />
- <rect
- width="2.25"
- height="2.0599999"
- x="35.150002"
- y="27.565001"
- id="rect34"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="24.200001"
- y="23.9"
- id="text36"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Windows</text>
- <text
- x="24.462999"
- y="24.5"
- id="text38"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Client</text>
- <text
- x="29.659"
- y="24.15"
- id="text40"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
- <text
- x="33.388"
- y="22.051001"
- id="text42"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">winbindd</text>
- <text
- x="29.76"
- y="28.676001"
- id="text44"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NSS</text>
- <text
- x="32.653999"
- y="28.775999"
- id="text46"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PAM</text>
- <text
- x="35.763"
- y="28.700001"
- id="text48"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="38.696999"
- y="23"
- id="text50"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">W2Kx</text>
- <text
- x="38.805"
- y="23.6"
- id="text52"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ADS</text>
- <text
- x="38.759998"
- y="20.6"
- id="text54"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NT4</text>
- <text
- x="38.477001"
- y="21.200001"
- id="text56"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain</text>
- <line
- x1="26.9"
- y1="24.006001"
- x2="28.549999"
- y2="24.000999"
- stroke="#000000"
- stroke-width="0.100"
- id="line58"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="26.899,23.756 26.4,24.007 26.901,24.256 26.899,23.756 "
- id="polygon60"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="28.551,24.251 29.05,24 28.549,23.752 28.551,24.251 "
- id="polygon62"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="29.52"
- y1="25.575001"
- x2="29.504999"
- y2="27"
- stroke="#000000"
- stroke-width="0.100"
- id="line64"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="29.77,25.577 29.525,25.075 29.27,25.572 29.77,25.577 "
- id="polygon66"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="29.255,26.998 29.5,27.5 29.755,27.003 29.255,26.998 "
- id="polygon68"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="31.393999"
- y1="25.190001"
- x2="32.605999"
- y2="27.110001"
- stroke="#000000"
- stroke-width="0.100"
- id="line70"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="31.605,25.057 31.127,24.767 31.182,25.324 31.605,25.057 "
- id="polygon72"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="32.395,27.243 32.873,27.533 32.818,26.976 32.395,27.243 "
- id="polygon74"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="31.481001"
- y1="23.128"
- x2="32.293999"
- y2="22.278999"
- stroke="#000000"
- stroke-width="0.100"
- id="line76"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="31.3,22.955 31.135,23.489 31.661,23.301 31.3,22.955 "
- id="polygon78"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="32.475,22.453 32.64,21.919 32.114,22.106 32.475,22.453 "
- id="polygon80"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="31.552999"
- y1="24.312"
- x2="35.821999"
- y2="27.253"
- stroke="#000000"
- stroke-width="0.100"
- id="line82"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="31.695,24.106 31.141,24.028 31.411,24.518 31.695,24.106 "
- id="polygon84"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="35.68,27.459 36.234,27.537 35.964,27.047 35.68,27.459 "
- id="polygon86"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="36.066002"
- y1="21.360001"
- x2="37.284"
- y2="20.91"
- stroke="#000000"
- stroke-width="0.100"
- id="line88"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="35.979,21.125 35.597,21.533 36.153,21.594 35.979,21.125 "
- id="polygon90"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="37.371,21.145 37.753,20.737 37.197,20.676 37.371,21.145 "
- id="polygon92"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="36.013"
- y1="22.323999"
- x2="37.512001"
- y2="22.908001"
- stroke="#000000"
- stroke-width="0.100"
- id="line94"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="36.103,22.091 35.547,22.143 35.922,22.557 36.103,22.091 "
- id="polygon96"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="37.422,23.141 37.978,23.089 37.603,22.675 37.422,23.141 "
- id="polygon98"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="2.95"
- height="2.01"
- x="37.75"
- y="24.565001"
- id="rect100"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.95"
- height="2.01"
- x="37.75"
- y="24.565001"
- id="rect102"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="38.654999"
- y="25.424999"
- id="text104"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="38.414001"
- y="26.025"
- id="text106"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC/BDC</text>
- <line
- x1="34.959"
- y1="23.228001"
- x2="37.328999"
- y2="25.216999"
- stroke="#000000"
- stroke-width="0.100"
- id="line108"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="35.12,23.037 34.576,22.907 34.798,23.42 35.12,23.037 "
- id="polygon110"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="37.168,25.408 37.712,25.538 37.489,25.025 37.168,25.408 "
- id="polygon112"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="3.915"
- height="1.76"
- x="29.01"
- y="31.190001"
- id="rect114"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="3.915"
- height="1.76"
- x="29.01"
- y="31.190001"
- id="rect116"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="30.181999"
- y1="30.139999"
- x2="30.177999"
- y2="30.65"
- stroke="#000000"
- stroke-width="0.100"
- id="line118"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="30.432,30.142 30.185,29.64 29.932,30.138 30.432,30.142 "
- id="polygon120"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="29.928,30.648 30.175,31.15 30.428,30.652 29.928,30.648 "
- id="polygon122"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="31.402"
- y1="30.853001"
- x2="32.599998"
- y2="29.927"
- stroke="#000000"
- stroke-width="0.100"
- id="line124"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="31.249,30.656 31.007,31.159 31.555,31.051 31.249,30.656 "
- id="polygon126"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="32.753,30.124 32.995,29.621 32.447,29.729 32.753,30.124 "
- id="polygon128"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="34.584999"
- y1="28.591999"
- x2="34.599998"
- y2="28.593"
- stroke="#000000"
- stroke-width="0.100"
- id="line130"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="34.586,28.342 34.085,28.59 34.584,28.842 34.586,28.342 "
- id="polygon132"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="34.599,28.843 35.1,28.595 34.601,28.343 34.599,28.843 "
- id="polygon134"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="30.027"
- y="31.975"
- id="text136"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">/etc/passwd</text>
- <text
- x="30.179001"
- y="32.575001"
- id="text138"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">/etc/group</text>
- <rect
- width="2.0650001"
- height="1.76"
- x="33.535"
- y="31.190001"
- id="rect140"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.0650001"
- height="1.76"
- x="33.535"
- y="31.190001"
- id="rect142"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="34.049"
- y="32.25"
- id="text144"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">NIS[+]</text>
- <line
- x1="34.515999"
- y1="30.754"
- x2="33.839001"
- y2="29.987"
- stroke="#000000"
- stroke-width="0.100"
- id="line146"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="34.329,30.919 34.847,31.129 34.704,30.588 34.329,30.919 "
- id="polygon148"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="34.027,29.822 33.508,29.612 33.652,30.153 34.027,29.822 "
- id="polygon150"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="33.080002"
- y1="30.879999"
- x2="31.639999"
- y2="29.9"
- stroke="#000000"
- stroke-width="0.100"
- id="line152"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="32.94,31.087 33.494,31.162 33.221,30.674 32.94,31.087 "
- id="polygon154"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="31.78,29.693 31.226,29.618 31.499,30.106 31.78,29.693 "
- id="polygon156"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 34.773,27.172 C 33.554243,26.096992 31.732941,26.07362 30.487,27.117"
- id="path158"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="30.268,26.92 30.133,27.462 30.648,27.245 30.268,26.92 "
- id="polygon160"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="34.609,27.296 35.118,27.526 34.997,26.98 34.609,27.296 "
- id="polygon162"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="33.568001"
- y1="27.028999"
- x2="34.02"
- y2="23.371"
- stroke="#000000"
- stroke-width="0.100"
- id="line164"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="33.319,26.998 33.506,27.525 33.816,27.06 33.319,26.998 "
- id="polygon166"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="34.268,23.402 34.081,22.875 33.772,23.34 34.268,23.402 "
- id="polygon168"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="31.264999"
- y1="27.030001"
- x2="33.073002"
- y2="23.292"
- stroke="#000000"
- stroke-width="0.100"
- id="line170"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="31.039,26.921 31.047,27.48 31.49,27.139 31.039,26.921 "
- id="polygon172"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="33.298,23.401 33.291,22.842 32.848,23.183 33.298,23.401 "
- id="polygon174"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="34.522999cm"
- height="23.67cm"
- viewBox="-11.471 -0.456 23.052 23.213"
- id="svg2">
- <defs
- id="defs2855" />
- <rect
- width="13.8"
- height="6.513"
- x="1.375"
- y="16.256001"
- id="rect4"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path6"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path8"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="14.4"
- height="5.9130001"
- x="1.075"
- y="16.556"
- id="rect10"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path12"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path14"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="1.375"
- y1="16.256001"
- x2="15.175"
- y2="16.256001"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.375"
- y1="22.768999"
- x2="15.175"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.075"
- y1="16.556"
- x2="1.075"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="15.475"
- y1="16.556"
- x2="15.475"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.617"
- height="6.8530002"
- x="0.495"
- y="-0.40599999"
- id="rect32"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path34"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path36"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.217"
- height="6.2529998"
- x="0.19499999"
- y="-0.106"
- id="rect38"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path40"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path42"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="0.495"
- y1="-0.40599999"
- x2="11.112"
- y2="-0.40599999"
- stroke="#000000"
- stroke-width="0.050"
- id="line44"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.495"
- y1="6.447"
- x2="11.112"
- y2="6.447"
- stroke="#000000"
- stroke-width="0.050"
- id="line46"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.19499999"
- y1="-0.106"
- x2="0.19499999"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line52"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.412"
- y1="-0.106"
- x2="11.412"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line54"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.337"
- height="6.8600001"
- x="12.35"
- y="-0.43099999"
- id="rect60"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path62"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path64"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="10.937"
- height="6.2600002"
- x="12.05"
- y="-0.131"
- id="rect66"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path68"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path70"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="12.35"
- y1="-0.43099999"
- x2="22.687"
- y2="-0.43099999"
- stroke="#000000"
- stroke-width="0.050"
- id="line72"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.35"
- y1="6.4289999"
- x2="22.687"
- y2="6.4289999"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.05"
- y1="-0.131"
- x2="12.05"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line80"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="22.987"
- y1="-0.131"
- x2="22.987"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line82"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.821"
- height="8.375"
- x="11.905"
- y="7.244"
- id="rect88"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path90"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path92"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.421"
- height="7.7750001"
- x="11.605"
- y="7.5440001"
- id="rect94"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path96"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path98"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="11.905"
- y1="7.244"
- x2="22.726999"
- y2="7.244"
- stroke="#000000"
- stroke-width="0.050"
- id="line100"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.905"
- y1="15.619"
- x2="22.726999"
- y2="15.619"
- stroke="#000000"
- stroke-width="0.050"
- id="line102"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path104"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path106"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.605"
- y1="7.5440001"
- x2="11.605"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line108"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="23.027"
- y1="7.5440001"
- x2="23.027"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line110"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path112"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path114"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="15.1"
- height="8.3719997"
- x="-11"
- y="7.1090002"
- id="rect116"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11,7.109 C -11.165685,7.109 -11.3,7.2433146 -11.3,7.409"
- id="path118"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 4.4,7.409 C 4.4,7.2433146 4.2656854,7.109 4.1,7.109"
- id="path120"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="15.7"
- height="7.7719998"
- x="-11.3"
- y="7.4089999"
- id="rect122"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.3,15.181 C -11.3,15.346685 -11.165685,15.481 -11,15.481"
- id="path124"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 4.1,15.481 C 4.2656854,15.481 4.4,15.346685 4.4,15.181"
- id="path126"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11"
- y1="7.1090002"
- x2="4.0999999"
- y2="7.1090002"
- stroke="#000000"
- stroke-width="0.050"
- id="line128"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11"
- y1="15.481"
- x2="4.0999999"
- y2="15.481"
- stroke="#000000"
- stroke-width="0.050"
- id="line130"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11,7.109 C -11.165685,7.109 -11.3,7.2433146 -11.3,7.409"
- id="path132"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 4.4,7.409 C 4.4,7.2433146 4.2656854,7.109 4.1,7.109"
- id="path134"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.3"
- y1="7.4089999"
- x2="-11.3"
- y2="15.181"
- stroke="#000000"
- stroke-width="0.050"
- id="line136"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="4.4000001"
- y1="7.4089999"
- x2="4.4000001"
- y2="15.181"
- stroke="#000000"
- stroke-width="0.050"
- id="line138"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.3,15.181 C -11.3,15.346685 -11.165685,15.481 -11,15.481"
- id="path140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 4.1,15.481 C 4.2656854,15.481 4.4,15.346685 4.4,15.181"
- id="path142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.95"
- y1="11.168"
- x2="4.8109999"
- y2="11.165"
- stroke="#000000"
- stroke-width="0.300"
- id="line144"
- style="stroke:#000000;stroke-width:0.30000001" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
- id="polyline146"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
- id="polyline148"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.787"
- x="-1.723"
- y="14.284"
- id="rect150"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.787"
- height="0.787"
- x="-1.723"
- y="14.284"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.787"
- x="-1.723"
- y="14.284"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.28,14.411 C -1.28,14.805 -1.201,14.726 -1.595,14.726"
- id="path156"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.28,14.411 C -1.28,14.805 -1.201,14.726 -1.595,14.726"
- id="path158"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.242,14.473 -1.282,14.394 -1.321,14.473 -1.242,14.473 "
- id="polygon160"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.242,14.473 -1.282,14.394 -1.321,14.473 -1.242,14.473 "
- id="polygon162"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.534,14.685 -1.612,14.725 -1.534,14.764 -1.534,14.685 "
- id="polygon164"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.534,14.685 -1.612,14.725 -1.534,14.764 -1.534,14.685 "
- id="polygon166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.047,14.633 C -1.44,14.633 -1.362,14.554 -1.362,14.948"
- id="path168"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.047,14.633 C -1.44,14.633 -1.362,14.554 -1.362,14.948"
- id="path170"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.116,14.67 -1.038,14.63 -1.116,14.591 -1.116,14.67 "
- id="polygon172"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.116,14.67 -1.038,14.63 -1.116,14.591 -1.116,14.67 "
- id="polygon174"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.408,14.882 -1.368,14.961 -1.329,14.882 -1.408,14.882 "
- id="polygon176"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.408,14.882 -1.368,14.961 -1.329,14.882 -1.408,14.882 "
- id="polygon178"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.3"
- y1="11.069"
- x2="-1.329"
- y2="14.284"
- stroke="#000000"
- stroke-width="0.100"
- id="line180"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-9.0480003"
- y="0.86699998"
- id="text182"
- style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="1.017"
- y="13.475"
- id="text184"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="0.82800001"
- y="13.975"
- id="text186"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GNY-PDC</text>
- <line
- x1="6.118"
- y1="13.16"
- x2="7.7179999"
- y2="13.135"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.10,0.10"
- id="line188"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <text
- x="8.4429998"
- y="13.325"
- id="text190"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
- id="polyline192"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-2.9530001"
- y="15.094"
- id="text194"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="4.1469998"
- y="17.031"
- id="text196"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect198"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect202"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect204"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect208"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="2.027"
- x2="3.5869999"
- y2="2.027"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.5869999"
- y1="2.2709999"
- x2="2.6140001"
- y2="2.2709999"
- stroke="#000000"
- stroke-width="0.010"
- id="line212"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect214"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect216"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect218"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.553"
- y1="3.122"
- x2="3.77"
- y2="3.122"
- stroke="#000000"
- stroke-width="0.010"
- id="line220"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect222"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect226"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect228"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect230"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect232"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect234"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect236"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect238"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect240"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect242"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect244"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7360001"
- y1="2.757"
- x2="3.405"
- y2="2.757"
- stroke="#000000"
- stroke-width="0.010"
- id="line246"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect248"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect250"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect252"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect254"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect256"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect258"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.6359999"
- x2="3.3440001"
- y2="2.6359999"
- stroke="#000000"
- stroke-width="0.010"
- id="line260"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect262"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect264"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect266"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.405"
- y1="2.4530001"
- x2="3.527"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line268"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.1830001"
- x2="3.7090001"
- y2="3.1830001"
- stroke="#000000"
- stroke-width="0.010"
- id="line270"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.244"
- x2="2.6140001"
- y2="3.244"
- stroke="#000000"
- stroke-width="0.010"
- id="line272"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.3050001"
- x2="3.7090001"
- y2="3.3050001"
- stroke="#000000"
- stroke-width="0.010"
- id="line274"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.487"
- x2="2.6140001"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line276"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.427"
- x2="3.7090001"
- y2="3.427"
- stroke="#000000"
- stroke-width="0.010"
- id="line278"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.3659999"
- x2="2.6140001"
- y2="3.3659999"
- stroke="#000000"
- stroke-width="0.010"
- id="line280"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.675"
- y1="2.4530001"
- x2="2.7360001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line282"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.4530001"
- x2="2.8570001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line284"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.697"
- x2="2.8570001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line286"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.283"
- y1="2.697"
- x2="3.3440001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line288"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.72"
- y1="2.6359999"
- x2="8.8620005"
- y2="2.6229999"
- stroke="#000000"
- stroke-width="0.100"
- id="line290"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.2069998"
- y1="2.632"
- x2="5.2090001"
- y2="3.5910001"
- stroke="#000000"
- stroke-width="0.100"
- id="line292"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.21"
- y1="2.632"
- x2="5.2080002"
- y2="1.632"
- stroke="#000000"
- stroke-width="0.100"
- id="line294"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.6500001"
- y1="2.6289999"
- x2="6.652"
- y2="3.5339999"
- stroke="#000000"
- stroke-width="0.100"
- id="line296"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.651"
- y1="2.6289999"
- x2="6.6479998"
- y2="1.6289999"
- stroke="#000000"
- stroke-width="0.100"
- id="line298"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.092"
- y1="2.625"
- x2="8.0950003"
- y2="3.552"
- stroke="#000000"
- stroke-width="0.100"
- id="line300"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.0909996"
- y1="2.625"
- x2="8.0889997"
- y2="1.625"
- stroke="#000000"
- stroke-width="0.100"
- id="line302"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect304"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect306"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.296"
- y="3.6559999"
- id="rect308"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon310"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon312"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon314"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon316"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect318"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect320"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon322"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon324"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect326"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect328"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7389998"
- y="3.645"
- id="rect330"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon332"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon334"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon336"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon338"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect340"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect342"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon344"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon346"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect348"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect350"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="4.8639998"
- y="1.22"
- id="rect352"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon354"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon356"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon358"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon360"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect362"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect364"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon366"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon368"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect370"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect372"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.3140001"
- y="1.245"
- id="rect374"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon376"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon378"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon380"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon382"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect384"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect386"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon388"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon390"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect392"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect394"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7639999"
- y="1.22"
- id="rect396"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon398"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon400"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon402"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon404"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect406"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect408"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon410"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon412"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon414"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon416"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
- id="path418"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.715,4.135 L 5.787,4.175"
- id="path420"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.587,4.175 L 4.659,4.135"
- id="path422"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon424"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon426"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon428"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon430"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse432"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse434"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse436"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse438"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse440"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse442"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse444"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse446"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse448"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse450"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse452"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse454"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse456"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse458"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse460"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse462"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse464"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse466"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse468"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse470"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse472"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse474"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse476"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse478"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse480"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse482"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse484"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse486"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect488"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect490"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect492"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect494"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect496"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect498"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="1.829"
- x2="9.0939999"
- y2="1.829"
- stroke="#000000"
- stroke-width="0.010"
- id="line500"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.0580001"
- x2="10.009"
- y2="2.0580001"
- stroke="#000000"
- stroke-width="0.010"
- id="line502"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="2.2290001"
- x2="9.0939999"
- y2="2.2290001"
- stroke="#000000"
- stroke-width="0.010"
- id="line504"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect506"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect508"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect510"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.9790001"
- y1="3.03"
- x2="10.123"
- y2="3.03"
- stroke="#000000"
- stroke-width="0.010"
- id="line512"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect514"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect516"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect518"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect520"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect522"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect524"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect526"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect528"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect530"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect532"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect534"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect536"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.8010001"
- x2="9.7229996"
- y2="2.8010001"
- stroke="#000000"
- stroke-width="0.010"
- id="line538"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect540"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect542"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect544"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect546"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect548"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect550"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.687"
- x2="9.6660004"
- y2="2.687"
- stroke="#000000"
- stroke-width="0.010"
- id="line552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.6660004"
- y1="2.744"
- x2="9.6090002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line554"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.744"
- x2="9.2080002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line556"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect558"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect560"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect562"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.401"
- x2="9.2080002"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line564"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.2650003"
- y1="2.401"
- x2="9.323"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line566"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.8369999"
- y1="2.401"
- x2="9.9519997"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line568"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.7160001"
- x2="9.0369997"
- y2="3.7160001"
- stroke="#000000"
- stroke-width="0.010"
- id="line570"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.6589999"
- x2="10.066"
- y2="3.6589999"
- stroke="#000000"
- stroke-width="0.010"
- id="line572"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.602"
- x2="9.0369997"
- y2="3.602"
- stroke="#000000"
- stroke-width="0.010"
- id="line574"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.5439999"
- x2="10.066"
- y2="3.5439999"
- stroke="#000000"
- stroke-width="0.010"
- id="line576"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.487"
- x2="9.0369997"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line578"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.4300001"
- x2="10.066"
- y2="3.4300001"
- stroke="#000000"
- stroke-width="0.010"
- id="line580"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.3729999"
- x2="9.0369997"
- y2="3.3729999"
- stroke="#000000"
- stroke-width="0.010"
- id="line582"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="6.888"
- y="5.3340001"
- id="text584"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="6.4829998"
- y="5.934"
- id="text586"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
- <text
- x="2.187"
- y="4.1690001"
- id="text588"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="2.006"
- y="4.6690001"
- id="text590"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-BDC</text>
- <text
- x="8.3649998"
- y="0.375"
- id="text592"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="8.6969995"
- y="0.875"
- id="text594"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-APPS</text>
- <rect
- width="1.291"
- height="1.1390001"
- x="0.61699998"
- y="2.0880001"
- id="rect596"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="1.263"
- cy="3.227"
- rx="0.64499998"
- ry="0.19"
- id="ellipse598"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse600"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse602"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
- id="path604"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.928"
- y1="2.523"
- x2="2.503"
- y2="2.523"
- stroke="#000000"
- stroke-width="0.100"
- id="line606"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.935"
- y="2.7219999"
- id="text608"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="0.94999999"
- y="3.122"
- id="text610"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect612"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect614"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect616"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect618"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect620"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect622"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="2.1900001"
- x2="15.431"
- y2="2.1900001"
- stroke="#000000"
- stroke-width="0.010"
- id="line624"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="2.4330001"
- x2="14.458"
- y2="2.4330001"
- stroke="#000000"
- stroke-width="0.010"
- id="line626"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect628"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect630"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect632"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="3.2850001"
- x2="15.614"
- y2="3.2850001"
- stroke="#000000"
- stroke-width="0.010"
- id="line634"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect636"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect638"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect640"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect642"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect644"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect646"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect648"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect650"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect652"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect654"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect656"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect658"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.58"
- y1="2.9200001"
- x2="15.249"
- y2="2.9200001"
- stroke="#000000"
- stroke-width="0.010"
- id="line660"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect662"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect664"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect666"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect668"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect670"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect672"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.7980001"
- x2="15.188"
- y2="2.7980001"
- stroke="#000000"
- stroke-width="0.010"
- id="line674"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect676"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect678"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect680"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.249"
- y1="2.615"
- x2="15.371"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line682"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.345"
- x2="15.553"
- y2="3.345"
- stroke="#000000"
- stroke-width="0.010"
- id="line684"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.4059999"
- x2="14.458"
- y2="3.4059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line686"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.467"
- x2="15.553"
- y2="3.467"
- stroke="#000000"
- stroke-width="0.010"
- id="line688"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.6500001"
- x2="14.458"
- y2="3.6500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.589"
- x2="15.553"
- y2="3.589"
- stroke="#000000"
- stroke-width="0.010"
- id="line692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.5280001"
- x2="14.458"
- y2="3.5280001"
- stroke="#000000"
- stroke-width="0.010"
- id="line694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="2.615"
- x2="14.58"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.615"
- x2="14.701"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.859"
- x2="14.701"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="2.859"
- x2="15.188"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line702"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.564"
- y1="2.7980001"
- x2="20.705"
- y2="2.7850001"
- stroke="#000000"
- stroke-width="0.100"
- id="line704"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.051001"
- y1="2.7939999"
- x2="17.052999"
- y2="3.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line706"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.054001"
- y1="2.7939999"
- x2="17.052"
- y2="1.794"
- stroke="#000000"
- stroke-width="0.100"
- id="line708"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.493"
- y1="2.7909999"
- x2="18.496"
- y2="3.6960001"
- stroke="#000000"
- stroke-width="0.100"
- id="line710"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.495001"
- y1="2.7909999"
- x2="18.492001"
- y2="1.791"
- stroke="#000000"
- stroke-width="0.100"
- id="line712"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.936001"
- y1="2.7869999"
- x2="19.938999"
- y2="3.714"
- stroke="#000000"
- stroke-width="0.100"
- id="line714"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.934999"
- y1="2.7869999"
- x2="19.933001"
- y2="1.7869999"
- stroke="#000000"
- stroke-width="0.100"
- id="line716"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect718"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect720"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.139999"
- y="3.8180001"
- id="rect722"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon724"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon726"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon728"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon730"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect732"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect734"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon736"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon738"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect740"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect742"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.583"
- y="3.8069999"
- id="rect744"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon746"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon748"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon750"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon752"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect754"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect756"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon758"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon760"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect762"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect764"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.708"
- y="1.382"
- id="rect766"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon768"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon770"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon772"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon774"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect776"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect778"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon780"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon782"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect784"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect786"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.158001"
- y="1.4069999"
- id="rect788"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon790"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon792"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon794"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon796"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect798"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect800"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon802"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon804"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect806"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect808"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.608"
- y="1.382"
- id="rect810"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon812"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon814"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon816"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon818"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect820"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect822"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon824"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon826"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon828"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon830"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
- id="path832"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.558,4.297 L 17.63,4.337"
- id="path834"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.43,4.337 L 16.502,4.297"
- id="path836"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon838"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon840"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon842"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon844"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse846"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse848"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse850"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse852"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse854"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse856"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse858"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse860"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse862"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse864"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse866"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse868"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse870"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse872"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse874"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse876"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse878"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse880"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse882"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse884"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse886"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse888"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse890"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse892"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse894"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse896"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse898"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse900"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect902"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect904"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect906"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect908"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect910"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect912"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="1.9910001"
- x2="20.938"
- y2="1.9910001"
- stroke="#000000"
- stroke-width="0.010"
- id="line914"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.22"
- x2="21.853001"
- y2="2.22"
- stroke="#000000"
- stroke-width="0.010"
- id="line916"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="2.391"
- x2="20.938"
- y2="2.391"
- stroke="#000000"
- stroke-width="0.010"
- id="line918"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect920"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect922"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect924"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.823"
- y1="3.1919999"
- x2="21.966999"
- y2="3.1919999"
- stroke="#000000"
- stroke-width="0.010"
- id="line926"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect928"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect930"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect932"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect934"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect936"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect938"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect940"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect942"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect944"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect946"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect948"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect950"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.9630001"
- x2="21.566999"
- y2="2.9630001"
- stroke="#000000"
- stroke-width="0.010"
- id="line952"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect954"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect956"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect958"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect960"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect962"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect964"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.849"
- x2="21.51"
- y2="2.849"
- stroke="#000000"
- stroke-width="0.010"
- id="line966"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.51"
- y1="2.9059999"
- x2="21.452"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line968"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.9059999"
- x2="21.052"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line970"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect972"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect974"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect976"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.563"
- x2="21.052"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line978"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.108999"
- y1="2.563"
- x2="21.167"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line980"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.681"
- y1="2.563"
- x2="21.796"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line982"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.878"
- x2="20.881001"
- y2="3.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line984"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.8210001"
- x2="21.91"
- y2="3.8210001"
- stroke="#000000"
- stroke-width="0.010"
- id="line986"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.7639999"
- x2="20.881001"
- y2="3.7639999"
- stroke="#000000"
- stroke-width="0.010"
- id="line988"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.707"
- x2="21.91"
- y2="3.707"
- stroke="#000000"
- stroke-width="0.010"
- id="line990"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.6489999"
- x2="20.881001"
- y2="3.6489999"
- stroke="#000000"
- stroke-width="0.010"
- id="line992"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.592"
- x2="21.91"
- y2="3.592"
- stroke="#000000"
- stroke-width="0.010"
- id="line994"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.5350001"
- x2="20.881001"
- y2="3.5350001"
- stroke="#000000"
- stroke-width="0.010"
- id="line996"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="18.931999"
- y="5.4460001"
- id="text998"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="18.525999"
- y="6.046"
- id="text1000"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
- <text
- x="14.303"
- y="4.415"
- id="text1002"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="14.238"
- y="4.915"
- id="text1004"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-BDC</text>
- <text
- x="19.816999"
- y="0.35600001"
- id="text1006"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="20.266001"
- y="0.85600001"
- id="text1008"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-APPS</text>
- <rect
- width="1.326"
- height="1.17"
- x="12.501"
- y="2.28"
- id="rect1010"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="13.164"
- cy="3.451"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1012"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.164"
- cy="2.28"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1014"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.164"
- cy="2.28"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1016"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.827,2.28 L 13.827,3.451 C 13.827,3.559 13.53,3.646 13.164,3.646 C 12.798,3.646 12.501,3.559 12.501,3.451 L 12.501,2.28"
- id="path1018"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.85"
- y1="2.7939999"
- x2="14.397"
- y2="2.7980001"
- stroke="#000000"
- stroke-width="0.100"
- id="line1020"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.809"
- y="2.9619999"
- id="text1022"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.823"
- y="3.362"
- id="text1024"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1026"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1028"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1030"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1032"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1034"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1036"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="10.744"
- x2="15.309"
- y2="10.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line1038"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.309"
- y1="10.988"
- x2="14.336"
- y2="10.988"
- stroke="#000000"
- stroke-width="0.010"
- id="line1040"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1042"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1044"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1046"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.275"
- y1="11.839"
- x2="15.492"
- y2="11.839"
- stroke="#000000"
- stroke-width="0.010"
- id="line1048"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1050"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1052"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1054"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1056"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1058"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1060"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1062"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1064"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1066"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1068"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1070"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1072"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="11.474"
- x2="15.127"
- y2="11.474"
- stroke="#000000"
- stroke-width="0.010"
- id="line1074"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1076"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1078"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1080"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1082"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1084"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1086"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.353"
- x2="15.066"
- y2="11.353"
- stroke="#000000"
- stroke-width="0.010"
- id="line1088"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1090"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1092"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1094"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="11.17"
- x2="15.249"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1096"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="11.9"
- x2="15.431"
- y2="11.9"
- stroke="#000000"
- stroke-width="0.010"
- id="line1098"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="11.961"
- x2="14.336"
- y2="11.961"
- stroke="#000000"
- stroke-width="0.010"
- id="line1100"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.022"
- x2="15.431"
- y2="12.022"
- stroke="#000000"
- stroke-width="0.010"
- id="line1102"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.204"
- x2="14.336"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1104"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.143"
- x2="15.431"
- y2="12.143"
- stroke="#000000"
- stroke-width="0.010"
- id="line1106"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.083"
- x2="14.336"
- y2="12.083"
- stroke="#000000"
- stroke-width="0.010"
- id="line1108"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="11.17"
- x2="14.458"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1110"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.17"
- x2="14.579"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1112"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.413"
- x2="14.579"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1114"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.005"
- y1="11.413"
- x2="15.066"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1116"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.442"
- y1="11.353"
- x2="20.584"
- y2="11.34"
- stroke="#000000"
- stroke-width="0.100"
- id="line1118"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.929001"
- y1="11.349"
- x2="16.931"
- y2="12.308"
- stroke="#000000"
- stroke-width="0.100"
- id="line1120"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.931999"
- y1="11.349"
- x2="16.93"
- y2="10.349"
- stroke="#000000"
- stroke-width="0.100"
- id="line1122"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372"
- y1="11.345"
- x2="18.374001"
- y2="12.251"
- stroke="#000000"
- stroke-width="0.100"
- id="line1124"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372999"
- y1="11.345"
- x2="18.370001"
- y2="10.345"
- stroke="#000000"
- stroke-width="0.100"
- id="line1126"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.815001"
- y1="11.342"
- x2="19.816999"
- y2="12.269"
- stroke="#000000"
- stroke-width="0.100"
- id="line1128"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.813"
- y1="11.342"
- x2="19.811001"
- y2="10.342"
- stroke="#000000"
- stroke-width="0.100"
- id="line1130"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1132"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1134"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.018"
- y="12.373"
- id="rect1136"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1138"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1142"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1144"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1146"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1148"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1150"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1152"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1154"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1156"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.461"
- y="12.362"
- id="rect1158"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1160"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1162"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1164"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1166"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1168"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1170"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1172"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1174"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1176"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1178"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.586"
- y="9.9370003"
- id="rect1180"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1182"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1184"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1186"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1188"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1190"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1192"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1194"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1196"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1198"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1200"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.035999"
- y="9.9619999"
- id="rect1202"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1204"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1206"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1208"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1210"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1212"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1214"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1216"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1218"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1220"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1222"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.486"
- y="9.9370003"
- id="rect1224"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1226"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1228"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1230"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1232"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1234"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1236"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1238"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1240"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1242"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1244"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
- id="path1246"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.437,12.852 L 17.509,12.892"
- id="path1248"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.309,12.892 L 16.381,12.852"
- id="path1250"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1252"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1254"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1256"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1258"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1260"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1262"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1264"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1266"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1268"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1270"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1272"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1274"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1276"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1278"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1280"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1282"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1284"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1286"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1288"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1290"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1292"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1294"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1296"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1298"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1300"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1302"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1304"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1306"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1308"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1310"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1312"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1314"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1316"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1318"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1320"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1322"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1324"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1326"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.546"
- x2="20.816"
- y2="10.546"
- stroke="#000000"
- stroke-width="0.010"
- id="line1328"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="10.774"
- x2="21.731001"
- y2="10.774"
- stroke="#000000"
- stroke-width="0.010"
- id="line1330"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.946"
- x2="20.816"
- y2="10.946"
- stroke="#000000"
- stroke-width="0.010"
- id="line1332"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1334"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1336"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1338"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.701"
- y1="11.747"
- x2="21.844999"
- y2="11.747"
- stroke="#000000"
- stroke-width="0.010"
- id="line1340"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1342"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1344"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1346"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1348"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1350"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1352"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1354"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1356"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1358"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1360"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1362"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1364"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="11.518"
- x2="21.445"
- y2="11.518"
- stroke="#000000"
- stroke-width="0.010"
- id="line1366"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1368"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1370"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1372"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1374"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1376"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1378"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.404"
- x2="21.388"
- y2="11.404"
- stroke="#000000"
- stroke-width="0.010"
- id="line1380"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.388"
- y1="11.461"
- x2="21.330999"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1382"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.461"
- x2="20.93"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1384"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1386"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1388"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1390"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.118"
- x2="20.93"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1392"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.987"
- y1="11.118"
- x2="21.045"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1394"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.559"
- y1="11.118"
- x2="21.674"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.433"
- x2="20.759001"
- y2="12.433"
- stroke="#000000"
- stroke-width="0.010"
- id="line1398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.376"
- x2="21.788"
- y2="12.376"
- stroke="#000000"
- stroke-width="0.010"
- id="line1400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.319"
- x2="20.759001"
- y2="12.319"
- stroke="#000000"
- stroke-width="0.010"
- id="line1402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.261"
- x2="21.788"
- y2="12.261"
- stroke="#000000"
- stroke-width="0.010"
- id="line1404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.204"
- x2="20.759001"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.147"
- x2="21.788"
- y2="12.147"
- stroke="#000000"
- stroke-width="0.010"
- id="line1408"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.09"
- x2="20.759001"
- y2="12.09"
- stroke="#000000"
- stroke-width="0.010"
- id="line1410"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="18.334999"
- y="14.401"
- id="text1412"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="17.900999"
- y="15.001"
- id="text1414"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
- <text
- x="13.937"
- y="12.893"
- id="text1416"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="13.608"
- y="13.393"
- id="text1418"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-BDC</text>
- <text
- x="19.917"
- y="8.9940004"
- id="text1420"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="20.101999"
- y="9.4940004"
- id="text1422"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-APPS</text>
- <rect
- width="1.314"
- height="1.159"
- x="12.051"
- y="10.933"
- id="rect1424"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.708"
- cy="12.092"
- rx="0.65700001"
- ry="0.193"
- id="ellipse1426"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.708"
- cy="10.933"
- rx="0.65700001"
- ry="0.193"
- id="ellipse1428"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.708"
- cy="10.933"
- rx="0.65700001"
- ry="0.193"
- id="ellipse1430"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.365,10.933 L 13.365,12.092 C 13.365,12.199 13.071,12.286 12.708,12.286 C 12.345,12.286 12.051,12.199 12.051,12.092 L 12.051,10.933"
- id="path1432"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="14.275"
- y1="11.353"
- x2="13.4"
- y2="11.368"
- stroke="#000000"
- stroke-width="0.100"
- id="line1434"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.412"
- y="11.567"
- id="text1436"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.427"
- y="11.967"
- id="text1438"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1440"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1442"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.7909999"
- y="11.036"
- id="text1444"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
- <path
- d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
- id="path1446"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
- id="path1448"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
- id="path1450"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1452"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1454"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1456"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1458"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1460"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1462"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.1389999"
- x2="1.8710001"
- y2="9.1389999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1464"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="9.4180002"
- x2="0.75400001"
- y2="9.4180002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1466"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.698"
- x2="1.8710001"
- y2="9.698"
- stroke="#000000"
- stroke-width="0.010"
- id="line1468"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.9770002"
- x2="1.8710001"
- y2="9.9770002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1470"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="10.256"
- x2="0.75400001"
- y2="10.256"
- stroke="#000000"
- stroke-width="0.010"
- id="line1472"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1474"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1476"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1478"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.61400002"
- y1="11.374"
- x2="2.0109999"
- y2="11.374"
- stroke="#000000"
- stroke-width="0.010"
- id="line1480"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1482"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1484"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1486"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1488"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1490"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1492"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1494"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1496"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1498"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1500"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1502"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1504"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="10.885"
- x2="1.522"
- y2="10.885"
- stroke="#000000"
- stroke-width="0.010"
- id="line1506"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1508"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1510"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1512"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1514"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1516"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1518"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.745"
- x2="1.452"
- y2="10.745"
- stroke="#000000"
- stroke-width="0.010"
- id="line1520"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.452"
- y1="10.815"
- x2="1.382"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1522"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.815"
- x2="0.89300001"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1524"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1526"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1528"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1530"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.466"
- x2="0.89300001"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1532"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.963"
- y1="10.466"
- x2="1.033"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1534"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.6619999"
- y1="10.466"
- x2="1.801"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1536"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.84"
- x2="1.941"
- y2="12.84"
- stroke="#000000"
- stroke-width="0.010"
- id="line1538"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.77"
- x2="0.68400002"
- y2="12.77"
- stroke="#000000"
- stroke-width="0.010"
- id="line1540"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.701"
- x2="1.941"
- y2="12.701"
- stroke="#000000"
- stroke-width="0.010"
- id="line1542"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.631"
- x2="0.68400002"
- y2="12.631"
- stroke="#000000"
- stroke-width="0.010"
- id="line1544"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.561"
- x2="1.941"
- y2="12.561"
- stroke="#000000"
- stroke-width="0.010"
- id="line1546"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.491"
- x2="0.68400002"
- y2="12.491"
- stroke="#000000"
- stroke-width="0.010"
- id="line1548"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.421"
- x2="1.941"
- y2="12.421"
- stroke="#000000"
- stroke-width="0.010"
- id="line1550"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.351"
- x2="0.68400002"
- y2="12.351"
- stroke="#000000"
- stroke-width="0.010"
- id="line1552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.282"
- x2="1.941"
- y2="12.282"
- stroke="#000000"
- stroke-width="0.010"
- id="line1554"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.212"
- x2="0.68400002"
- y2="12.212"
- stroke="#000000"
- stroke-width="0.010"
- id="line1556"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.142"
- x2="1.941"
- y2="12.142"
- stroke="#000000"
- stroke-width="0.010"
- id="line1558"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.072"
- x2="0.68400002"
- y2="12.072"
- stroke="#000000"
- stroke-width="0.010"
- id="line1560"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.002"
- x2="1.941"
- y2="12.002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1562"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="11.932"
- x2="0.68400002"
- y2="11.932"
- stroke="#000000"
- stroke-width="0.010"
- id="line1564"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.3340001"
- y="11.97"
- id="rect1566"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.3340001"
- y="11.97"
- id="rect1568"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.2290001"
- y="12.076"
- id="rect1570"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.202,12.699 -5.703,12.699 -5.703,12.812 -6.176,12.812 -6.202,12.699 "
- id="polygon1572"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.202,12.699 -5.703,12.699 -5.703,12.812 -6.176,12.812 -6.202,12.699 "
- id="polygon1574"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.703,12.699 -5.494,12.699 -5.521,12.812 -5.703,12.812 -5.703,12.699 "
- id="polygon1576"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.703,12.699 -5.494,12.699 -5.521,12.812 -5.703,12.812 -5.703,12.699 "
- id="polygon1578"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.6690001"
- y="12.733"
- id="rect1580"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.6690001"
- y="12.733"
- id="rect1582"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-5.945,12.812 -5.751,12.812 -5.751,12.869 -5.654,12.869 -5.654,12.925 -6.042,12.925 -6.042,12.869 -5.945,12.869 -5.945,12.812 "
- id="polygon1584"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.945,12.812 -5.751,12.812 -5.751,12.869 -5.654,12.869 -5.654,12.925 -6.042,12.925 -6.042,12.869 -5.945,12.869 -5.945,12.812 "
- id="polygon1586"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.62800002"
- y1="11.055"
- x2="-9.6000004"
- y2="11.069"
- stroke="#000000"
- stroke-width="0.100"
- id="line1588"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.312"
- y1="11.057"
- x2="-1.314"
- y2="10.12"
- stroke="#000000"
- stroke-width="0.100"
- id="line1590"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.5769999"
- y1="11.06"
- x2="-3.575"
- y2="12.069"
- stroke="#000000"
- stroke-width="0.100"
- id="line1592"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.573"
- y1="11.06"
- x2="-3.5739999"
- y2="10.399"
- stroke="#000000"
- stroke-width="0.100"
- id="line1594"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.8520002"
- y1="11.063"
- x2="-5.8499999"
- y2="12.018"
- stroke="#000000"
- stroke-width="0.100"
- id="line1596"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.8429999"
- y1="11.063"
- x2="-5.8439999"
- y2="10.338"
- stroke="#000000"
- stroke-width="0.100"
- id="line1598"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-8.0740004"
- y1="11.066"
- x2="-8.0749998"
- y2="10.168"
- stroke="#000000"
- stroke-width="0.100"
- id="line1600"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.0779999"
- height="0.80800003"
- x="-4.079"
- y="12.008"
- id="rect1602"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.0779999"
- height="0.80800003"
- x="-4.079"
- y="12.008"
- id="rect1604"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.84399998"
- height="0.55699998"
- x="-3.9619999"
- y="12.125"
- id="rect1606"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.933,12.816 -3.378,12.816 -3.378,12.942 -3.903,12.942 -3.933,12.816 "
- id="polygon1608"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.933,12.816 -3.378,12.816 -3.378,12.942 -3.903,12.942 -3.933,12.816 "
- id="polygon1610"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.378,12.816 -3.147,12.816 -3.176,12.942 -3.378,12.942 -3.378,12.816 "
- id="polygon1612"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.378,12.816 -3.147,12.816 -3.176,12.942 -3.378,12.942 -3.378,12.816 "
- id="polygon1614"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.3399999"
- y="12.854"
- id="rect1616"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.3399999"
- y="12.854"
- id="rect1618"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.647,12.942 -3.432,12.942 -3.432,13.005 -3.324,13.005 -3.324,13.068 -3.755,13.068 -3.755,13.005 -3.647,13.005 -3.647,12.942 "
- id="polygon1620"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.647,12.942 -3.432,12.942 -3.432,13.005 -3.324,13.005 -3.324,13.068 -3.755,13.068 -3.755,13.005 -3.647,13.005 -3.647,12.942 "
- id="polygon1622"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.329"
- y="9.3830004"
- id="rect1624"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.329"
- y="9.3830004"
- id="rect1626"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.224"
- y="9.4890003"
- id="rect1628"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.198,10.112 -5.698,10.112 -5.698,10.225 -6.171,10.225 -6.198,10.112 "
- id="polygon1630"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.198,10.112 -5.698,10.112 -5.698,10.225 -6.171,10.225 -6.198,10.112 "
- id="polygon1632"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.698,10.112 -5.49,10.112 -5.516,10.225 -5.698,10.225 -5.698,10.112 "
- id="polygon1634"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.698,10.112 -5.49,10.112 -5.516,10.225 -5.698,10.225 -5.698,10.112 "
- id="polygon1636"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.664"
- y="10.146"
- id="rect1638"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.664"
- y="10.146"
- id="rect1640"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-5.941,10.225 -5.746,10.225 -5.746,10.282 -5.649,10.282 -5.649,10.338 -6.038,10.338 -6.038,10.282 -5.941,10.282 -5.941,10.225 "
- id="polygon1642"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.941,10.225 -5.746,10.225 -5.746,10.282 -5.649,10.282 -5.649,10.338 -6.038,10.338 -6.038,10.282 -5.941,10.282 -5.941,10.225 "
- id="polygon1644"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.0599999"
- y="9.4449997"
- id="rect1646"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.0599999"
- y="9.4449997"
- id="rect1648"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-3.9549999"
- y="9.5500002"
- id="rect1650"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.928,10.173 -3.429,10.173 -3.429,10.286 -3.902,10.286 -3.928,10.173 "
- id="polygon1652"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.928,10.173 -3.429,10.173 -3.429,10.286 -3.902,10.286 -3.928,10.173 "
- id="polygon1654"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.429,10.173 -3.22,10.173 -3.247,10.286 -3.429,10.286 -3.429,10.173 "
- id="polygon1656"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.429,10.173 -3.22,10.173 -3.247,10.286 -3.429,10.286 -3.429,10.173 "
- id="polygon1658"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.395"
- y="10.207"
- id="rect1660"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.395"
- y="10.207"
- id="rect1662"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.671,10.286 -3.477,10.286 -3.477,10.343 -3.38,10.343 -3.38,10.399 -3.769,10.399 -3.769,10.343 -3.671,10.343 -3.671,10.286 "
- id="polygon1664"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.671,10.286 -3.477,10.286 -3.477,10.343 -3.38,10.343 -3.38,10.399 -3.769,10.399 -3.769,10.343 -3.671,10.343 -3.671,10.286 "
- id="polygon1666"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-10.578"
- y="10.617"
- id="rect1668"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-10.578"
- y="10.617"
- id="rect1670"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-10.473"
- y="10.722"
- id="rect1672"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-10.446,11.345 -9.947,11.345 -9.947,11.458 -10.42,11.458 -10.446,11.345 "
- id="polygon1674"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-10.446,11.345 -9.947,11.345 -9.947,11.458 -10.42,11.458 -10.446,11.345 "
- id="polygon1676"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-9.947,11.345 -9.738,11.345 -9.765,11.458 -9.947,11.458 -9.947,11.345 "
- id="polygon1678"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-9.947,11.345 -9.738,11.345 -9.765,11.458 -9.947,11.458 -9.947,11.345 "
- id="polygon1680"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-9.9130001"
- y="11.379"
- id="rect1682"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-9.9130001"
- y="11.379"
- id="rect1684"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-10.19,11.458 -9.995,11.458 -9.995,11.515 -9.898,11.515 -9.898,11.571 -10.287,11.571 -10.287,11.515 -10.19,11.515 -10.19,11.458 "
- id="polygon1686"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-10.19,11.458 -9.995,11.458 -9.995,11.515 -9.898,11.515 -9.898,11.571 -10.287,11.571 -10.287,11.515 -10.19,11.515 -10.19,11.458 "
- id="polygon1688"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-1.726,9.492 -1.775,9.513 -1.92,9.877 -1.92,10.059 -1.848,10.12 -0.779,10.12 -0.707,10.059 -0.707,9.877 -0.852,9.513 -0.901,9.492 -1.726,9.492 "
- id="polygon1690"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.726,9.492 -1.775,9.513 -1.92,9.877 -1.92,10.059 -1.848,10.12 -0.779,10.12 -0.707,10.059 -0.707,9.877 -0.852,9.513 -0.901,9.492 -1.726,9.492 "
- id="polygon1692"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.896,9.816 L -1.848,9.836 L -0.779,9.836 L -0.731,9.816"
- id="path1694"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -0.779,9.836 L -0.707,9.877"
- id="path1696"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.92,9.877 L -1.848,9.836"
- id="path1698"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.581,9.108 -1.605,9.593 -1.022,9.593 -1.046,9.108 -1.581,9.108 "
- id="polygon1700"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.581,9.108 -1.605,9.593 -1.022,9.593 -1.046,9.108 -1.581,9.108 "
- id="polygon1702"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.678,9.593 -1.726,9.735 -0.901,9.735 -0.949,9.593 -1.678,9.593 "
- id="polygon1704"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.678,9.593 -1.726,9.735 -0.901,9.735 -0.949,9.593 -1.678,9.593 "
- id="polygon1706"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-1.678"
- cy="9.9069996"
- rx="0.012"
- ry="0.012"
- id="ellipse1708"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.678"
- cy="9.9069996"
- rx="0.012"
- ry="0.012"
- id="ellipse1710"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.556"
- cy="9.9069996"
- rx="0.012"
- ry="0.012"
- id="ellipse1712"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.556"
- cy="9.9069996"
- rx="0.012"
- ry="0.012"
- id="ellipse1714"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.4349999"
- cy="9.9069996"
- rx="0.012"
- ry="0.012"
- id="ellipse1716"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.4349999"
- cy="9.9069996"
- rx="0.012"
- ry="0.012"
- id="ellipse1718"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.678"
- cy="9.9580002"
- rx="0.012"
- ry="0.012"
- id="ellipse1720"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.678"
- cy="9.9580002"
- rx="0.012"
- ry="0.012"
- id="ellipse1722"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.556"
- cy="9.9580002"
- rx="0.012"
- ry="0.012"
- id="ellipse1724"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.556"
- cy="9.9580002"
- rx="0.012"
- ry="0.012"
- id="ellipse1726"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.4349999"
- cy="9.9580002"
- rx="0.012"
- ry="0.012"
- id="ellipse1728"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.4349999"
- cy="9.9580002"
- rx="0.012"
- ry="0.012"
- id="ellipse1730"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.678"
- cy="10.008"
- rx="0.012"
- ry="0.012"
- id="ellipse1732"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.678"
- cy="10.008"
- rx="0.012"
- ry="0.012"
- id="ellipse1734"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.556"
- cy="10.008"
- rx="0.012"
- ry="0.012"
- id="ellipse1736"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.556"
- cy="10.008"
- rx="0.012"
- ry="0.012"
- id="ellipse1738"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.4349999"
- cy="10.008"
- rx="0.012"
- ry="0.012"
- id="ellipse1740"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.4349999"
- cy="10.008"
- rx="0.012"
- ry="0.012"
- id="ellipse1742"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.678"
- cy="10.059"
- rx="0.012"
- ry="0.012"
- id="ellipse1744"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.678"
- cy="10.059"
- rx="0.012"
- ry="0.012"
- id="ellipse1746"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.556"
- cy="10.059"
- rx="0.012"
- ry="0.012"
- id="ellipse1748"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.556"
- cy="10.059"
- rx="0.012"
- ry="0.012"
- id="ellipse1750"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.4349999"
- cy="10.059"
- rx="0.012"
- ry="0.012"
- id="ellipse1752"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.4349999"
- cy="10.059"
- rx="0.012"
- ry="0.012"
- id="ellipse1754"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.314"
- cy="9.9169998"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1756"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-1.314"
- cy="9.9169998"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1758"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.01"
- cy="9.9169998"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1760"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-1.01"
- cy="9.9169998"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1762"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.159"
- height="2.3180001"
- x="-8.6300001"
- y="8.4790001"
- id="rect1764"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.159"
- height="2.3180001"
- x="-8.6300001"
- y="8.4790001"
- id="rect1766"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.159"
- height="2.3180001"
- x="-8.6300001"
- y="8.4790001"
- id="rect1768"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.92699999"
- height="0.92699999"
- x="-8.5150003"
- y="8.5950003"
- id="rect1770"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.92699999"
- height="0.92699999"
- x="-8.5150003"
- y="8.5950003"
- id="rect1772"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.92699999"
- height="0.92699999"
- x="-8.5150003"
- y="8.5950003"
- id="rect1774"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5869999"
- y1="8.8260002"
- x2="-8.5150003"
- y2="8.8260002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1776"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5150003"
- y1="9.0579996"
- x2="-7.5869999"
- y2="9.0579996"
- stroke="#000000"
- stroke-width="0.010"
- id="line1778"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5869999"
- y1="9.2320004"
- x2="-8.5150003"
- y2="9.2320004"
- stroke="#000000"
- stroke-width="0.010"
- id="line1780"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.63800001"
- height="0.34799999"
- x="-8.5150003"
- y="9.6379995"
- id="rect1782"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.63800001"
- height="0.34799999"
- x="-8.5150003"
- y="9.6379995"
- id="rect1784"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.63800001"
- height="0.34799999"
- x="-8.5150003"
- y="9.6379995"
- id="rect1786"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6300001"
- y1="10.044"
- x2="-7.4710002"
- y2="10.044"
- stroke="#000000"
- stroke-width="0.010"
- id="line1788"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-8.1090002"
- y="10.16"
- id="rect1790"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-8.1090002"
- y="10.16"
- id="rect1792"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-8.1090002"
- y="10.16"
- id="rect1794"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.8769999"
- y="10.16"
- id="rect1796"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.8769999"
- y="10.16"
- id="rect1798"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.8769999"
- y="10.16"
- id="rect1800"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.645"
- y="10.16"
- id="rect1802"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.645"
- y="10.16"
- id="rect1804"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.645"
- y="10.16"
- id="rect1806"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.116"
- height="0.057999998"
- x="-7.7030001"
- y="9.8120003"
- id="rect1808"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.116"
- height="0.057999998"
- x="-7.7030001"
- y="9.8120003"
- id="rect1810"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.116"
- height="0.057999998"
- x="-7.7030001"
- y="9.8120003"
- id="rect1812"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5150003"
- y1="9.8120003"
- x2="-7.8769999"
- y2="9.8120003"
- stroke="#000000"
- stroke-width="0.010"
- id="line1814"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17399999"
- height="0.17399999"
- x="-8.5150003"
- y="10.102"
- id="rect1816"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17399999"
- height="0.17399999"
- x="-8.5150003"
- y="10.102"
- id="rect1818"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17399999"
- height="0.17399999"
- x="-8.5150003"
- y="10.102"
- id="rect1820"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.81099999"
- height="0.057999998"
- x="-8.4569998"
- y="9.29"
- id="rect1822"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.81099999"
- height="0.057999998"
- x="-8.4569998"
- y="9.29"
- id="rect1824"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.81099999"
- height="0.057999998"
- x="-8.4569998"
- y="9.29"
- id="rect1826"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4569998"
- y1="9.6960001"
- x2="-7.9349999"
- y2="9.6960001"
- stroke="#000000"
- stroke-width="0.010"
- id="line1828"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.9349999"
- y1="9.7539997"
- x2="-7.993"
- y2="9.7539997"
- stroke="#000000"
- stroke-width="0.010"
- id="line1830"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4569998"
- y1="9.7539997"
- x2="-8.3990002"
- y2="9.7539997"
- stroke="#000000"
- stroke-width="0.010"
- id="line1832"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28999999"
- height="0.057999998"
- x="-8.3409996"
- y="9.6960001"
- id="rect1834"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28999999"
- height="0.057999998"
- x="-8.3409996"
- y="9.6960001"
- id="rect1836"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28999999"
- height="0.057999998"
- x="-8.3409996"
- y="9.6960001"
- id="rect1838"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4569998"
- y1="9.4060001"
- x2="-8.3990002"
- y2="9.4060001"
- stroke="#000000"
- stroke-width="0.010"
- id="line1840"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.3409996"
- y1="9.4060001"
- x2="-8.283"
- y2="9.4060001"
- stroke="#000000"
- stroke-width="0.010"
- id="line1842"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.7610002"
- y1="9.4060001"
- x2="-7.645"
- y2="9.4060001"
- stroke="#000000"
- stroke-width="0.010"
- id="line1844"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5289998"
- y1="10.739"
- x2="-8.573"
- y2="10.739"
- stroke="#000000"
- stroke-width="0.010"
- id="line1846"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.573"
- y1="10.681"
- x2="-7.5289998"
- y2="10.681"
- stroke="#000000"
- stroke-width="0.010"
- id="line1848"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5289998"
- y1="10.623"
- x2="-8.573"
- y2="10.623"
- stroke="#000000"
- stroke-width="0.010"
- id="line1850"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.573"
- y1="10.565"
- x2="-7.5289998"
- y2="10.565"
- stroke="#000000"
- stroke-width="0.010"
- id="line1852"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5289998"
- y1="10.507"
- x2="-8.573"
- y2="10.507"
- stroke="#000000"
- stroke-width="0.010"
- id="line1854"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.573"
- y1="10.449"
- x2="-7.5289998"
- y2="10.449"
- stroke="#000000"
- stroke-width="0.010"
- id="line1856"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5289998"
- y1="10.391"
- x2="-8.573"
- y2="10.391"
- stroke="#000000"
- stroke-width="0.010"
- id="line1858"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="-5.5710001"
- y="13.811"
- id="text1860"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-5.9060001"
- y="14.411"
- id="text1862"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
- <text
- x="-10.233"
- y="7.7189999"
- id="text1864"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="-9.9090004"
- y="8.2189999"
- id="text1866"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GNY-APPS</text>
- <rect
- width="1.4450001"
- height="1.275"
- x="2.5510001"
- y="8.6120005"
- id="rect1868"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="3.273"
- cy="9.8870001"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1870"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1872"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1874"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
- id="path1876"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.0109999"
- y1="9.2469997"
- x2="2.586"
- y2="9.2469997"
- stroke="#000000"
- stroke-width="0.100"
- id="line1878"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="2.983"
- y="9.3260002"
- id="text1880"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.928"
- y="9.7259998"
- id="text1882"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
- id="polyline1884"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-10.458"
- y="15.156"
- id="text1886"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
- <text
- x="1.136"
- y="6.0770001"
- id="text1888"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
- <text
- x="12.943"
- y="6.0310001"
- id="text1890"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
- <text
- x="12.358"
- y="15.177"
- id="text1892"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
- <text
- x="-4.4629998"
- y="8.1560001"
- id="text1894"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - GNY</text>
- <text
- x="13.214"
- y="0.46399999"
- id="text1896"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
- <text
- x="1.1109999"
- y="0.46399999"
- id="text1898"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
- <text
- x="12.979"
- y="8.0889997"
- id="text1900"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
- <rect
- width="11.132"
- height="6.5630002"
- x="-11.146"
- y="16.205999"
- id="rect1902"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1904"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1906"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.732"
- height="5.9629998"
- x="-11.446"
- y="16.506001"
- id="rect1908"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1910"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1912"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11.146"
- y1="16.205999"
- x2="-0.014"
- y2="16.205999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1914"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.146"
- y1="22.768999"
- x2="-0.014"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1916"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1918"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1920"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.446"
- y1="16.506001"
- x2="-11.446"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1922"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.28600001"
- y1="16.506001"
- x2="0.28600001"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1924"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1926"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1928"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1930"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1932"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1934"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1936"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1938"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1940"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1942"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1944"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1946"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1948"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1950"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1952"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1954"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1956"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1958"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-5.2220001"
- y="17.145"
- id="text1960"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-5.5609999"
- y="17.745001"
- id="text1962"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
- <text
- x="-10.001"
- y="21.07"
- id="text1964"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="-10.37"
- y="21.57"
- id="text1966"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1968"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1970"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1972"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1974"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1976"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1978"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="19.087"
- x2="-7.6300001"
- y2="19.087"
- stroke="#000000"
- stroke-width="0.010"
- id="line1980"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.6300001"
- y1="19.33"
- x2="-8.6040001"
- y2="19.33"
- stroke="#000000"
- stroke-width="0.010"
- id="line1982"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1984"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1986"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1988"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.665"
- y1="20.181999"
- x2="-7.448"
- y2="20.181999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1990"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1992"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1994"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1996"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect1998"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect2000"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect2002"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2004"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2006"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2008"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2010"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2012"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2014"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4820004"
- y1="19.816999"
- x2="-7.8130002"
- y2="19.816999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2016"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2018"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2020"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2022"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2024"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2026"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2028"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.695"
- x2="-7.8740001"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.010"
- id="line2030"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2032"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2034"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2036"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.8130002"
- y1="19.511999"
- x2="-7.691"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2038"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.242001"
- x2="-7.5089998"
- y2="20.242001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2040"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.302999"
- x2="-8.6040001"
- y2="20.302999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2042"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.364"
- x2="-7.5089998"
- y2="20.364"
- stroke="#000000"
- stroke-width="0.010"
- id="line2044"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.547001"
- x2="-8.6040001"
- y2="20.547001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2046"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.486"
- x2="-7.5089998"
- y2="20.486"
- stroke="#000000"
- stroke-width="0.010"
- id="line2048"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.424999"
- x2="-8.6040001"
- y2="20.424999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2050"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5430002"
- y1="19.511999"
- x2="-8.4820004"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2052"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.511999"
- x2="-8.3599997"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2054"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.756001"
- x2="-8.3599997"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2056"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.9349999"
- y1="19.756001"
- x2="-7.8740001"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2058"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.4980001"
- y1="19.695"
- x2="-2.164"
- y2="19.679001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2060"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9559999"
- y1="19.690001"
- x2="-5.9530001"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.100"
- id="line2062"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9530001"
- y1="19.690001"
- x2="-5.9559999"
- y2="18.690001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2064"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4590001"
- y1="19.686001"
- x2="-4.4559999"
- y2="20.591"
- stroke="#000000"
- stroke-width="0.100"
- id="line2066"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4569998"
- y1="19.686001"
- x2="-4.46"
- y2="18.686001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2068"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.961"
- y1="19.681"
- x2="-2.9579999"
- y2="20.608"
- stroke="#000000"
- stroke-width="0.100"
- id="line2070"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.9619999"
- y1="19.681"
- x2="-2.9649999"
- y2="18.681"
- stroke="#000000"
- stroke-width="0.100"
- id="line2072"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2074"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2076"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8470001"
- y="20.715"
- id="rect2078"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2080"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2082"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2084"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2086"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2088"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2090"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2092"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2094"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2096"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2098"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.329"
- y="20.704"
- id="rect2100"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2102"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2104"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2106"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2108"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2110"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2112"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2114"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2116"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2118"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2120"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-6.2789998"
- y="18.278999"
- id="rect2122"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2124"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2126"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2128"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2130"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2132"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2134"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2136"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2138"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2140"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8039999"
- y="18.278999"
- id="rect2144"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2146"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2148"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2150"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2152"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2154"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2156"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2158"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2160"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2162"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2164"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.3039999"
- y="18.304001"
- id="rect2166"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2168"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2170"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2172"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2174"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2176"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2178"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2180"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2182"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2184"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2186"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
- id="path2188"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -5.503,21.194 L -5.431,21.234"
- id="path2190"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.631,21.234 L -6.559,21.194"
- id="path2192"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2194"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2196"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2198"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2200"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2202"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2204"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2206"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2208"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2210"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2212"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2214"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2216"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2218"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2220"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2222"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2224"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2226"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2228"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2230"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2232"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2234"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2236"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2238"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2240"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2242"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2244"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2246"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2248"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2250"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2252"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2254"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2256"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.2410001"
- height="1.095"
- x="-10.66"
- y="19.143"
- id="rect2258"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="-10.04"
- cy="20.238001"
- rx="0.62099999"
- ry="0.183"
- id="ellipse2260"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.04"
- cy="19.143"
- rx="0.62099999"
- ry="0.183"
- id="ellipse2262"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.04"
- cy="19.143"
- rx="0.62099999"
- ry="0.183"
- id="ellipse2264"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -9.419,19.143 L -9.419,20.238 C -9.419,20.338 -9.697,20.42 -10.04,20.42 C -10.382,20.42 -10.66,20.338 -10.66,20.238 L -10.66,19.143"
- id="path2266"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-9.3959999"
- y1="19.684"
- x2="-8.665"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.100"
- id="line2268"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-10.328"
- y="19.759001"
- id="text2270"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="-10.313"
- y="20.159"
- id="text2272"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="-0.91500002"
- y="19.843"
- id="text2274"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="-2.1919999"
- y="22.406"
- id="text2276"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
- <text
- x="-10.31"
- y="17.143"
- id="text2278"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="-9.9130001"
- y="17.944"
- id="text2280"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg2</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.525,15.094 -1.525,15.906 -1.821,15.906 -1.821,19.285 "
- id="polyline2282"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2284"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2286"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2288"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2290"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2292"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2294"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2296"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2298"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2300"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2302"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2304"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2306"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2308"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2310"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2312"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="7.5560002"
- y="17.367001"
- id="text2314"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="7.2179999"
- y="17.966999"
- id="text2316"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
- <text
- x="3.204"
- y="18.118"
- id="text2318"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="2.835"
- y="18.618"
- id="text2320"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
- <text
- x="11.592"
- y="21.718"
- id="text2322"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="11.737"
- y="22.218"
- id="text2324"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-APPS</text>
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2326"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2328"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2330"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2332"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2334"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2336"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="19.246"
- x2="5.112"
- y2="19.246"
- stroke="#000000"
- stroke-width="0.010"
- id="line2338"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.112"
- y1="19.49"
- x2="4.138"
- y2="19.49"
- stroke="#000000"
- stroke-width="0.010"
- id="line2340"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2342"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2344"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2346"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.0770001"
- y1="20.341"
- x2="5.2940001"
- y2="20.341"
- stroke="#000000"
- stroke-width="0.010"
- id="line2348"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2350"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2352"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2354"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2356"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2358"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2360"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2362"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2364"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2366"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2368"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2370"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2372"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.2600002"
- y1="19.976"
- x2="4.9289999"
- y2="19.976"
- stroke="#000000"
- stroke-width="0.010"
- id="line2374"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2376"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2378"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2380"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2382"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2384"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2386"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.855"
- x2="4.868"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.010"
- id="line2388"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2390"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2392"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2394"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.9289999"
- y1="19.672001"
- x2="5.0510001"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.402"
- x2="5.2329998"
- y2="20.402"
- stroke="#000000"
- stroke-width="0.010"
- id="line2398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.462999"
- x2="4.138"
- y2="20.462999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.524"
- x2="5.2329998"
- y2="20.524"
- stroke="#000000"
- stroke-width="0.010"
- id="line2402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.705999"
- x2="4.138"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.645"
- x2="5.2329998"
- y2="20.645"
- stroke="#000000"
- stroke-width="0.010"
- id="line2406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.584999"
- x2="4.138"
- y2="20.584999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2408"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.1989999"
- y1="19.672001"
- x2="4.2600002"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2410"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.672001"
- x2="4.382"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2412"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.915001"
- x2="4.382"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2414"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.8070002"
- y1="19.915001"
- x2="4.868"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2416"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.244"
- y1="19.855"
- x2="10.386"
- y2="19.841999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2418"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7309999"
- y1="19.851"
- x2="6.7329998"
- y2="20.809999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2420"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7350001"
- y1="19.851"
- x2="6.7319999"
- y2="18.851"
- stroke="#000000"
- stroke-width="0.100"
- id="line2422"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1739998"
- y1="19.847"
- x2="8.1759996"
- y2="20.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line2424"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1750002"
- y1="19.847"
- x2="8.1730003"
- y2="18.848"
- stroke="#000000"
- stroke-width="0.100"
- id="line2426"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6169996"
- y1="19.844"
- x2="9.6190004"
- y2="20.771"
- stroke="#000000"
- stroke-width="0.100"
- id="line2428"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6160002"
- y1="19.844"
- x2="9.6129999"
- y2="18.844"
- stroke="#000000"
- stroke-width="0.100"
- id="line2430"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2432"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2434"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8210001"
- y="20.875"
- id="rect2436"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2438"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2440"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2442"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2444"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2446"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2448"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2450"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2452"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2454"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2456"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2629995"
- y="20.864"
- id="rect2458"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2460"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2462"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2464"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2466"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2468"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2470"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2472"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2474"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2476"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2478"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.388"
- y="18.438999"
- id="rect2480"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2482"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2484"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2486"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2488"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2490"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2492"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2494"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2496"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2498"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2500"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8379998"
- y="18.464001"
- id="rect2502"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2504"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2506"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2508"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2510"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2512"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2514"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2516"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2518"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2520"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2522"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2880001"
- y="18.438999"
- id="rect2524"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2526"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2528"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2530"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2532"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2534"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2536"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2538"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2540"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2542"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2544"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
- id="path2546"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.239,21.354 L 7.311,21.394"
- id="path2548"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.111,21.394 L 6.183,21.354"
- id="path2550"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2552"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2554"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2556"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2558"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2560"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2562"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2564"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2566"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2568"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2570"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2572"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2574"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2576"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2578"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2580"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2582"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2584"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2586"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2588"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2590"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2592"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2594"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2596"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2598"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2600"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2602"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2604"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2606"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2608"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2610"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2612"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2614"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2616"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2618"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2620"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2622"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2624"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2626"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.048"
- x2="10.618"
- y2="19.048"
- stroke="#000000"
- stroke-width="0.010"
- id="line2628"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="19.275999"
- x2="11.533"
- y2="19.275999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2630"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.448"
- x2="10.618"
- y2="19.448"
- stroke="#000000"
- stroke-width="0.010"
- id="line2632"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2634"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2636"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2638"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.504"
- y1="20.249001"
- x2="11.647"
- y2="20.249001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2640"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2642"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2644"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2646"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2648"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2650"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2652"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2654"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2656"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2658"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2660"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2662"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2664"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="20.02"
- x2="11.247"
- y2="20.02"
- stroke="#000000"
- stroke-width="0.010"
- id="line2666"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2668"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2670"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2672"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2674"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2676"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2678"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.906"
- x2="11.19"
- y2="19.906"
- stroke="#000000"
- stroke-width="0.010"
- id="line2680"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.19"
- y1="19.962999"
- x2="11.133"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2682"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.962999"
- x2="10.732"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2684"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2686"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2688"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2690"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.620001"
- x2="10.732"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.79"
- y1="19.620001"
- x2="10.847"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.362"
- y1="19.620001"
- x2="11.476"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.934999"
- x2="10.561"
- y2="20.934999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.878"
- x2="11.59"
- y2="20.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line2700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.820999"
- x2="10.561"
- y2="20.820999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2702"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.763"
- x2="11.59"
- y2="20.763"
- stroke="#000000"
- stroke-width="0.010"
- id="line2704"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.705999"
- x2="10.561"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2706"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.649"
- x2="11.59"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.010"
- id="line2708"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.591999"
- x2="10.561"
- y2="20.591999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2710"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.4960001"
- y1="19.819"
- x2="4.0770001"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.100"
- id="line2712"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.183"
- height="1.044"
- x="2.302"
- y="19.268999"
- id="rect2714"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="2.8940001"
- cy="20.312"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2716"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2718"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2720"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
- id="path2722"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="2.589"
- y="19.868999"
- id="text2724"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.6040001"
- y="20.268999"
- id="text2726"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="2.0469999"
- y="22.452"
- id="text2728"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
- <text
- x="12.072"
- y="17.239"
- id="text2730"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="12.468"
- y="18.039"
- id="text2732"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg3</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
- id="polyline2734"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.1"
- y1="22.393"
- x2="15.55"
- y2="23.143"
- stroke="#F7F7F7"
- stroke-width="0.100"
- id="line2736"
- style="stroke:#f7f7f7;stroke-width:0.1" />
- <rect
- width="1.159"
- height="2.3180001"
- x="-8.6529999"
- y="11.306"
- id="rect2738"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.159"
- height="2.3180001"
- x="-8.6529999"
- y="11.306"
- id="rect2740"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.159"
- height="2.3180001"
- x="-8.6529999"
- y="11.306"
- id="rect2742"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.92699999"
- height="0.92699999"
- x="-8.5369997"
- y="11.422"
- id="rect2744"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.92699999"
- height="0.92699999"
- x="-8.5369997"
- y="11.422"
- id="rect2746"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.92699999"
- height="0.92699999"
- x="-8.5369997"
- y="11.422"
- id="rect2748"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.6100001"
- y1="11.654"
- x2="-8.5369997"
- y2="11.654"
- stroke="#000000"
- stroke-width="0.010"
- id="line2750"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5369997"
- y1="11.886"
- x2="-7.6100001"
- y2="11.886"
- stroke="#000000"
- stroke-width="0.010"
- id="line2752"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.6100001"
- y1="12.059"
- x2="-8.5369997"
- y2="12.059"
- stroke="#000000"
- stroke-width="0.010"
- id="line2754"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.63800001"
- height="0.34799999"
- x="-8.5369997"
- y="12.465"
- id="rect2756"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.63800001"
- height="0.34799999"
- x="-8.5369997"
- y="12.465"
- id="rect2758"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.63800001"
- height="0.34799999"
- x="-8.5369997"
- y="12.465"
- id="rect2760"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6529999"
- y1="12.871"
- x2="-7.494"
- y2="12.871"
- stroke="#000000"
- stroke-width="0.010"
- id="line2762"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-8.1309996"
- y="12.987"
- id="rect2764"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-8.1309996"
- y="12.987"
- id="rect2766"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-8.1309996"
- y="12.987"
- id="rect2768"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.8990002"
- y="12.987"
- id="rect2770"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.8990002"
- y="12.987"
- id="rect2772"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.8990002"
- y="12.987"
- id="rect2774"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.6680002"
- y="12.987"
- id="rect2776"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.6680002"
- y="12.987"
- id="rect2778"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057999998"
- height="0.057999998"
- x="-7.6680002"
- y="12.987"
- id="rect2780"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.116"
- height="0.057999998"
- x="-7.7259998"
- y="12.639"
- id="rect2782"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.116"
- height="0.057999998"
- x="-7.7259998"
- y="12.639"
- id="rect2784"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.116"
- height="0.057999998"
- x="-7.7259998"
- y="12.639"
- id="rect2786"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5369997"
- y1="12.639"
- x2="-7.8990002"
- y2="12.639"
- stroke="#000000"
- stroke-width="0.010"
- id="line2788"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17399999"
- height="0.17399999"
- x="-8.5369997"
- y="12.929"
- id="rect2790"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17399999"
- height="0.17399999"
- x="-8.5369997"
- y="12.929"
- id="rect2792"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17399999"
- height="0.17399999"
- x="-8.5369997"
- y="12.929"
- id="rect2794"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.81099999"
- height="0.057999998"
- x="-8.4790001"
- y="12.117"
- id="rect2796"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.81099999"
- height="0.057999998"
- x="-8.4790001"
- y="12.117"
- id="rect2798"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.81099999"
- height="0.057999998"
- x="-8.4790001"
- y="12.117"
- id="rect2800"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4790001"
- y1="12.523"
- x2="-7.9569998"
- y2="12.523"
- stroke="#000000"
- stroke-width="0.010"
- id="line2802"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.9569998"
- y1="12.581"
- x2="-8.0150003"
- y2="12.581"
- stroke="#000000"
- stroke-width="0.010"
- id="line2804"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4790001"
- y1="12.581"
- x2="-8.4209995"
- y2="12.581"
- stroke="#000000"
- stroke-width="0.010"
- id="line2806"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28999999"
- height="0.057999998"
- x="-8.3629999"
- y="12.523"
- id="rect2808"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28999999"
- height="0.057999998"
- x="-8.3629999"
- y="12.523"
- id="rect2810"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28999999"
- height="0.057999998"
- x="-8.3629999"
- y="12.523"
- id="rect2812"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4790001"
- y1="12.233"
- x2="-8.4209995"
- y2="12.233"
- stroke="#000000"
- stroke-width="0.010"
- id="line2814"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.3629999"
- y1="12.233"
- x2="-8.3050003"
- y2="12.233"
- stroke="#000000"
- stroke-width="0.010"
- id="line2816"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.7839999"
- y1="12.233"
- x2="-7.6680002"
- y2="12.233"
- stroke="#000000"
- stroke-width="0.010"
- id="line2818"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.552"
- y1="13.566"
- x2="-8.5950003"
- y2="13.566"
- stroke="#000000"
- stroke-width="0.010"
- id="line2820"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5950003"
- y1="13.508"
- x2="-7.552"
- y2="13.508"
- stroke="#000000"
- stroke-width="0.010"
- id="line2822"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.552"
- y1="13.45"
- x2="-8.5950003"
- y2="13.45"
- stroke="#000000"
- stroke-width="0.010"
- id="line2824"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5950003"
- y1="13.393"
- x2="-7.552"
- y2="13.393"
- stroke="#000000"
- stroke-width="0.010"
- id="line2826"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.552"
- y1="13.335"
- x2="-8.5950003"
- y2="13.335"
- stroke="#000000"
- stroke-width="0.010"
- id="line2828"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5950003"
- y1="13.277"
- x2="-7.552"
- y2="13.277"
- stroke="#000000"
- stroke-width="0.010"
- id="line2830"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.552"
- y1="13.219"
- x2="-8.5950003"
- y2="13.219"
- stroke="#000000"
- stroke-width="0.010"
- id="line2832"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.0749998"
- y1="11.094"
- x2="-8.1000004"
- y2="11.344"
- stroke="#000000"
- stroke-width="0.100"
- id="line2834"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-10.538"
- y="12.993"
- id="text2836"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="-10.728"
- y="13.493"
- id="text2838"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GNY-DBC</text>
- <text
- x="-11.175"
- y="2.119"
- id="text2840"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Here there is a single Windows Network|</text>
- <text
- x="-11.175"
- y="2.7190001"
- id="text2842"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain. There is an LDAP Master in GNY</text>
- <text
- x="-11.175"
- y="3.319"
- id="text2844"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">with a Slave LDAP server in each remote</text>
- <text
- x="-11.175"
- y="3.9189999"
- id="text2846"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">office. There is at least one Application</text>
- <text
- x="-11.175"
- y="4.5190001"
- id="text2848"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">server in each office and at least one BDC</text>
- <text
- x="-11.175"
- y="5.119"
- id="text2850"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">in every office.</text>
- <text
- x="-11.175"
- y="6.3189998"
- id="text2852"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">There is 1 BDC per 50 users.</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="34.602001cm"
- height="23.67cm"
- viewBox="-11.55 -0.456 23.052 23.213"
- id="svg2">
- <defs
- id="defs2739" />
- <rect
- width="13.8"
- height="6.513"
- x="1.375"
- y="16.256001"
- id="rect4"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path6"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path8"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="14.4"
- height="5.9130001"
- x="1.075"
- y="16.556"
- id="rect10"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path12"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path14"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="1.375"
- y1="16.256001"
- x2="15.175"
- y2="16.256001"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.375"
- y1="22.768999"
- x2="15.175"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.075"
- y1="16.556"
- x2="1.075"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="15.475"
- y1="16.556"
- x2="15.475"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.617"
- height="6.8530002"
- x="0.495"
- y="-0.40599999"
- id="rect32"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path34"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path36"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.217"
- height="6.2529998"
- x="0.19499999"
- y="-0.106"
- id="rect38"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path40"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path42"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="0.495"
- y1="-0.40599999"
- x2="11.112"
- y2="-0.40599999"
- stroke="#000000"
- stroke-width="0.050"
- id="line44"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.495"
- y1="6.447"
- x2="11.112"
- y2="6.447"
- stroke="#000000"
- stroke-width="0.050"
- id="line46"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.19499999"
- y1="-0.106"
- x2="0.19499999"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line52"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.412"
- y1="-0.106"
- x2="11.412"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line54"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.337"
- height="6.8600001"
- x="12.35"
- y="-0.43099999"
- id="rect60"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path62"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path64"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="10.937"
- height="6.2600002"
- x="12.05"
- y="-0.131"
- id="rect66"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path68"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path70"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="12.35"
- y1="-0.43099999"
- x2="22.687"
- y2="-0.43099999"
- stroke="#000000"
- stroke-width="0.050"
- id="line72"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.35"
- y1="6.4289999"
- x2="22.687"
- y2="6.4289999"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.05"
- y1="-0.131"
- x2="12.05"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line80"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="22.987"
- y1="-0.131"
- x2="22.987"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line82"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.821"
- height="8.375"
- x="11.905"
- y="7.244"
- id="rect88"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path90"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path92"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.421"
- height="7.7750001"
- x="11.605"
- y="7.5440001"
- id="rect94"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path96"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path98"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="11.905"
- y1="7.244"
- x2="22.726999"
- y2="7.244"
- stroke="#000000"
- stroke-width="0.050"
- id="line100"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.905"
- y1="15.619"
- x2="22.726999"
- y2="15.619"
- stroke="#000000"
- stroke-width="0.050"
- id="line102"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path104"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path106"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.605"
- y1="7.5440001"
- x2="11.605"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line108"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="23.027"
- y1="7.5440001"
- x2="23.027"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line110"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path112"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path114"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="15.1"
- height="8.3719997"
- x="-11.225"
- y="7.1339998"
- id="rect116"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
- id="path118"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
- id="path120"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="15.7"
- height="7.7719998"
- x="-11.525"
- y="7.434"
- id="rect122"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
- id="path124"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
- id="path126"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11.225"
- y1="7.1339998"
- x2="3.875"
- y2="7.1339998"
- stroke="#000000"
- stroke-width="0.050"
- id="line128"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.225"
- y1="15.506"
- x2="3.875"
- y2="15.506"
- stroke="#000000"
- stroke-width="0.050"
- id="line130"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
- id="path132"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
- id="path134"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.525"
- y1="7.434"
- x2="-11.525"
- y2="15.206"
- stroke="#000000"
- stroke-width="0.050"
- id="line136"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="4.1750002"
- y1="7.434"
- x2="4.1750002"
- y2="15.206"
- stroke="#000000"
- stroke-width="0.050"
- id="line138"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
- id="path140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
- id="path142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.95"
- y1="11.168"
- x2="4.8109999"
- y2="11.165"
- stroke="#000000"
- stroke-width="0.300"
- id="line144"
- style="stroke:#000000;stroke-width:0.30000001" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
- id="polyline146"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
- id="polyline148"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect150"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
- id="path156"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
- id="path158"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
- id="polygon160"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
- id="polygon162"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
- id="polygon164"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
- id="polygon166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
- id="path168"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
- id="path170"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
- id="polygon172"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
- id="polygon174"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
- id="polygon176"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
- id="polygon178"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.306"
- y1="11.165"
- x2="-1.3279999"
- y2="14.136"
- stroke="#000000"
- stroke-width="0.100"
- id="line180"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-9.1479998"
- y="1.442"
- id="text182"
- style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="0.71700001"
- y="7.6999998"
- id="text184"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="0.37799999"
- y="8.1999998"
- id="text186"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-PDC</text>
- <line
- x1="6.118"
- y1="13.16"
- x2="7.7179999"
- y2="13.135"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.10,0.10"
- id="line188"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <text
- x="8.4429998"
- y="13.325"
- id="text190"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
- id="polyline192"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-3.0239999"
- y="14.751"
- id="text194"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="4.1469998"
- y="17.031"
- id="text196"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect198"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect202"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect204"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect208"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="2.027"
- x2="3.5869999"
- y2="2.027"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.5869999"
- y1="2.2709999"
- x2="2.6140001"
- y2="2.2709999"
- stroke="#000000"
- stroke-width="0.010"
- id="line212"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect214"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect216"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect218"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.553"
- y1="3.122"
- x2="3.77"
- y2="3.122"
- stroke="#000000"
- stroke-width="0.010"
- id="line220"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect222"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect226"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect228"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect230"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect232"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect234"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect236"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect238"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect240"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect242"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect244"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7360001"
- y1="2.757"
- x2="3.405"
- y2="2.757"
- stroke="#000000"
- stroke-width="0.010"
- id="line246"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect248"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect250"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect252"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect254"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect256"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect258"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.6359999"
- x2="3.3440001"
- y2="2.6359999"
- stroke="#000000"
- stroke-width="0.010"
- id="line260"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect262"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect264"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect266"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.405"
- y1="2.4530001"
- x2="3.527"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line268"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.1830001"
- x2="3.7090001"
- y2="3.1830001"
- stroke="#000000"
- stroke-width="0.010"
- id="line270"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.244"
- x2="2.6140001"
- y2="3.244"
- stroke="#000000"
- stroke-width="0.010"
- id="line272"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.3050001"
- x2="3.7090001"
- y2="3.3050001"
- stroke="#000000"
- stroke-width="0.010"
- id="line274"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.487"
- x2="2.6140001"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line276"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.427"
- x2="3.7090001"
- y2="3.427"
- stroke="#000000"
- stroke-width="0.010"
- id="line278"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.3659999"
- x2="2.6140001"
- y2="3.3659999"
- stroke="#000000"
- stroke-width="0.010"
- id="line280"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.675"
- y1="2.4530001"
- x2="2.7360001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line282"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.4530001"
- x2="2.8570001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line284"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.697"
- x2="2.8570001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line286"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.283"
- y1="2.697"
- x2="3.3440001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line288"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.72"
- y1="2.6359999"
- x2="8.8620005"
- y2="2.6229999"
- stroke="#000000"
- stroke-width="0.100"
- id="line290"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.2069998"
- y1="2.632"
- x2="5.2090001"
- y2="3.5910001"
- stroke="#000000"
- stroke-width="0.100"
- id="line292"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.21"
- y1="2.632"
- x2="5.2080002"
- y2="1.632"
- stroke="#000000"
- stroke-width="0.100"
- id="line294"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.6500001"
- y1="2.6289999"
- x2="6.652"
- y2="3.5339999"
- stroke="#000000"
- stroke-width="0.100"
- id="line296"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.651"
- y1="2.6289999"
- x2="6.6479998"
- y2="1.6289999"
- stroke="#000000"
- stroke-width="0.100"
- id="line298"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.092"
- y1="2.625"
- x2="8.0950003"
- y2="3.552"
- stroke="#000000"
- stroke-width="0.100"
- id="line300"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.0909996"
- y1="2.625"
- x2="8.0889997"
- y2="1.625"
- stroke="#000000"
- stroke-width="0.100"
- id="line302"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect304"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect306"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.296"
- y="3.6559999"
- id="rect308"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon310"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon312"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon314"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon316"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect318"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect320"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon322"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon324"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect326"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect328"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7389998"
- y="3.645"
- id="rect330"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon332"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon334"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon336"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon338"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect340"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect342"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon344"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon346"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect348"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect350"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="4.8639998"
- y="1.22"
- id="rect352"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon354"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon356"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon358"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon360"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect362"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect364"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon366"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon368"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect370"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect372"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.3140001"
- y="1.245"
- id="rect374"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon376"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon378"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon380"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon382"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect384"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect386"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon388"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon390"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect392"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect394"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7639999"
- y="1.22"
- id="rect396"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon398"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon400"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon402"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon404"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect406"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect408"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon410"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon412"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon414"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon416"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
- id="path418"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.715,4.135 L 5.787,4.175"
- id="path420"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.587,4.175 L 4.659,4.135"
- id="path422"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon424"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon426"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon428"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon430"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse432"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse434"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse436"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse438"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse440"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse442"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse444"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse446"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse448"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse450"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse452"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse454"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse456"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse458"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse460"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse462"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse464"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse466"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse468"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse470"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse472"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse474"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse476"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse478"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse480"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse482"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse484"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse486"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect488"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect490"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect492"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect494"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect496"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect498"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="1.829"
- x2="9.0939999"
- y2="1.829"
- stroke="#000000"
- stroke-width="0.010"
- id="line500"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.0580001"
- x2="10.009"
- y2="2.0580001"
- stroke="#000000"
- stroke-width="0.010"
- id="line502"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="2.2290001"
- x2="9.0939999"
- y2="2.2290001"
- stroke="#000000"
- stroke-width="0.010"
- id="line504"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect506"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect508"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect510"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.9790001"
- y1="3.03"
- x2="10.123"
- y2="3.03"
- stroke="#000000"
- stroke-width="0.010"
- id="line512"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect514"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect516"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect518"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect520"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect522"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect524"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect526"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect528"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect530"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect532"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect534"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect536"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.8010001"
- x2="9.7229996"
- y2="2.8010001"
- stroke="#000000"
- stroke-width="0.010"
- id="line538"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect540"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect542"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect544"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect546"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect548"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect550"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.687"
- x2="9.6660004"
- y2="2.687"
- stroke="#000000"
- stroke-width="0.010"
- id="line552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.6660004"
- y1="2.744"
- x2="9.6090002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line554"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.744"
- x2="9.2080002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line556"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect558"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect560"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect562"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.401"
- x2="9.2080002"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line564"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.2650003"
- y1="2.401"
- x2="9.323"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line566"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.8369999"
- y1="2.401"
- x2="9.9519997"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line568"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.7160001"
- x2="9.0369997"
- y2="3.7160001"
- stroke="#000000"
- stroke-width="0.010"
- id="line570"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.6589999"
- x2="10.066"
- y2="3.6589999"
- stroke="#000000"
- stroke-width="0.010"
- id="line572"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.602"
- x2="9.0369997"
- y2="3.602"
- stroke="#000000"
- stroke-width="0.010"
- id="line574"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.5439999"
- x2="10.066"
- y2="3.5439999"
- stroke="#000000"
- stroke-width="0.010"
- id="line576"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.487"
- x2="9.0369997"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line578"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.4300001"
- x2="10.066"
- y2="3.4300001"
- stroke="#000000"
- stroke-width="0.010"
- id="line580"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.3729999"
- x2="9.0369997"
- y2="3.3729999"
- stroke="#000000"
- stroke-width="0.010"
- id="line582"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="5.9629998"
- y="5.2589998"
- id="text584"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="5.5580001"
- y="5.8590002"
- id="text586"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
- <text
- x="1.459"
- y="4.1030002"
- id="text588"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="1.239"
- y="4.6030002"
- id="text590"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVA-BDC</text>
- <text
- x="8.3649998"
- y="0.375"
- id="text592"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="8.658"
- y="0.875"
- id="text594"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVA-APPS</text>
- <rect
- width="1.291"
- height="1.1390001"
- x="0.61699998"
- y="2.0880001"
- id="rect596"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="1.263"
- cy="3.227"
- rx="0.64499998"
- ry="0.19"
- id="ellipse598"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse600"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse602"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
- id="path604"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.928"
- y1="2.523"
- x2="2.503"
- y2="2.523"
- stroke="#000000"
- stroke-width="0.100"
- id="line606"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.935"
- y="2.7219999"
- id="text608"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="0.94999999"
- y="3.122"
- id="text610"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect612"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect614"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect616"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect618"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect620"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect622"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="2.1900001"
- x2="15.431"
- y2="2.1900001"
- stroke="#000000"
- stroke-width="0.010"
- id="line624"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="2.4330001"
- x2="14.458"
- y2="2.4330001"
- stroke="#000000"
- stroke-width="0.010"
- id="line626"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect628"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect630"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect632"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="3.2850001"
- x2="15.614"
- y2="3.2850001"
- stroke="#000000"
- stroke-width="0.010"
- id="line634"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect636"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect638"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect640"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect642"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect644"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect646"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect648"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect650"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect652"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect654"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect656"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect658"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.58"
- y1="2.9200001"
- x2="15.249"
- y2="2.9200001"
- stroke="#000000"
- stroke-width="0.010"
- id="line660"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect662"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect664"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect666"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect668"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect670"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect672"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.7980001"
- x2="15.188"
- y2="2.7980001"
- stroke="#000000"
- stroke-width="0.010"
- id="line674"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect676"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect678"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect680"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.249"
- y1="2.615"
- x2="15.371"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line682"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.345"
- x2="15.553"
- y2="3.345"
- stroke="#000000"
- stroke-width="0.010"
- id="line684"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.4059999"
- x2="14.458"
- y2="3.4059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line686"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.467"
- x2="15.553"
- y2="3.467"
- stroke="#000000"
- stroke-width="0.010"
- id="line688"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.6500001"
- x2="14.458"
- y2="3.6500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.589"
- x2="15.553"
- y2="3.589"
- stroke="#000000"
- stroke-width="0.010"
- id="line692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.5280001"
- x2="14.458"
- y2="3.5280001"
- stroke="#000000"
- stroke-width="0.010"
- id="line694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="2.615"
- x2="14.58"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.615"
- x2="14.701"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.859"
- x2="14.701"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="2.859"
- x2="15.188"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line702"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.564"
- y1="2.7980001"
- x2="20.705"
- y2="2.7850001"
- stroke="#000000"
- stroke-width="0.100"
- id="line704"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.051001"
- y1="2.7939999"
- x2="17.052999"
- y2="3.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line706"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.054001"
- y1="2.7939999"
- x2="17.052"
- y2="1.794"
- stroke="#000000"
- stroke-width="0.100"
- id="line708"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.493"
- y1="2.7909999"
- x2="18.496"
- y2="3.6960001"
- stroke="#000000"
- stroke-width="0.100"
- id="line710"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.495001"
- y1="2.7909999"
- x2="18.492001"
- y2="1.791"
- stroke="#000000"
- stroke-width="0.100"
- id="line712"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.936001"
- y1="2.7869999"
- x2="19.938999"
- y2="3.714"
- stroke="#000000"
- stroke-width="0.100"
- id="line714"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.934999"
- y1="2.7869999"
- x2="19.933001"
- y2="1.7869999"
- stroke="#000000"
- stroke-width="0.100"
- id="line716"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect718"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect720"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.139999"
- y="3.8180001"
- id="rect722"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon724"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon726"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon728"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon730"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect732"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect734"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon736"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon738"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect740"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect742"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.583"
- y="3.8069999"
- id="rect744"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon746"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon748"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon750"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon752"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect754"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect756"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon758"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon760"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect762"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect764"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.708"
- y="1.382"
- id="rect766"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon768"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon770"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon772"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon774"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect776"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect778"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon780"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon782"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect784"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect786"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.158001"
- y="1.4069999"
- id="rect788"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon790"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon792"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon794"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon796"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect798"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect800"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon802"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon804"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect806"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect808"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.608"
- y="1.382"
- id="rect810"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon812"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon814"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon816"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon818"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect820"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect822"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon824"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon826"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon828"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon830"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
- id="path832"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.558,4.297 L 17.63,4.337"
- id="path834"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.43,4.337 L 16.502,4.297"
- id="path836"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon838"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon840"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon842"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon844"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse846"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse848"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse850"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse852"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse854"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse856"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse858"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse860"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse862"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse864"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse866"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse868"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse870"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse872"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse874"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse876"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse878"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse880"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse882"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse884"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse886"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse888"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse890"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse892"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse894"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse896"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse898"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse900"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect902"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect904"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect906"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect908"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect910"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect912"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="1.9910001"
- x2="20.938"
- y2="1.9910001"
- stroke="#000000"
- stroke-width="0.010"
- id="line914"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.22"
- x2="21.853001"
- y2="2.22"
- stroke="#000000"
- stroke-width="0.010"
- id="line916"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="2.391"
- x2="20.938"
- y2="2.391"
- stroke="#000000"
- stroke-width="0.010"
- id="line918"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect920"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect922"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect924"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.823"
- y1="3.1919999"
- x2="21.966999"
- y2="3.1919999"
- stroke="#000000"
- stroke-width="0.010"
- id="line926"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect928"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect930"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect932"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect934"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect936"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect938"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect940"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect942"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect944"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect946"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect948"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect950"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.9630001"
- x2="21.566999"
- y2="2.9630001"
- stroke="#000000"
- stroke-width="0.010"
- id="line952"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect954"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect956"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect958"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect960"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect962"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect964"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.849"
- x2="21.51"
- y2="2.849"
- stroke="#000000"
- stroke-width="0.010"
- id="line966"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.51"
- y1="2.9059999"
- x2="21.452"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line968"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.9059999"
- x2="21.052"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line970"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect972"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect974"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect976"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.563"
- x2="21.052"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line978"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.108999"
- y1="2.563"
- x2="21.167"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line980"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.681"
- y1="2.563"
- x2="21.796"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line982"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.878"
- x2="20.881001"
- y2="3.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line984"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.8210001"
- x2="21.91"
- y2="3.8210001"
- stroke="#000000"
- stroke-width="0.010"
- id="line986"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.7639999"
- x2="20.881001"
- y2="3.7639999"
- stroke="#000000"
- stroke-width="0.010"
- id="line988"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.707"
- x2="21.91"
- y2="3.707"
- stroke="#000000"
- stroke-width="0.010"
- id="line990"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.6489999"
- x2="20.881001"
- y2="3.6489999"
- stroke="#000000"
- stroke-width="0.010"
- id="line992"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.592"
- x2="21.91"
- y2="3.592"
- stroke="#000000"
- stroke-width="0.010"
- id="line994"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.5350001"
- x2="20.881001"
- y2="3.5350001"
- stroke="#000000"
- stroke-width="0.010"
- id="line996"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="18.056999"
- y="5.3460002"
- id="text998"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="17.650999"
- y="5.9460001"
- id="text1000"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
- <text
- x="13.478"
- y="4.3400002"
- id="text1002"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="13.248"
- y="4.8400002"
- id="text1004"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVB-BDC</text>
- <text
- x="19.816999"
- y="0.35600001"
- id="text1006"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="20.101"
- y="0.85600001"
- id="text1008"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVB-APPS</text>
- <rect
- width="1.326"
- height="1.17"
- x="12.501"
- y="2.28"
- id="rect1010"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="13.164"
- cy="3.451"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1012"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.164"
- cy="2.28"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1014"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.164"
- cy="2.28"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1016"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.827,2.28 L 13.827,3.451 C 13.827,3.559 13.53,3.646 13.164,3.646 C 12.798,3.646 12.501,3.559 12.501,3.451 L 12.501,2.28"
- id="path1018"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.822"
- y1="2.8599999"
- x2="14.397"
- y2="2.7980001"
- stroke="#000000"
- stroke-width="0.100"
- id="line1020"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.809"
- y="2.9619999"
- id="text1022"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.823"
- y="3.362"
- id="text1024"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1026"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1028"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1030"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1032"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1034"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1036"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="10.744"
- x2="15.309"
- y2="10.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line1038"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.309"
- y1="10.988"
- x2="14.336"
- y2="10.988"
- stroke="#000000"
- stroke-width="0.010"
- id="line1040"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1042"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1044"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1046"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.275"
- y1="11.839"
- x2="15.492"
- y2="11.839"
- stroke="#000000"
- stroke-width="0.010"
- id="line1048"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1050"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1052"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1054"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1056"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1058"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1060"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1062"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1064"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1066"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1068"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1070"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1072"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="11.474"
- x2="15.127"
- y2="11.474"
- stroke="#000000"
- stroke-width="0.010"
- id="line1074"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1076"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1078"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1080"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1082"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1084"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1086"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.353"
- x2="15.066"
- y2="11.353"
- stroke="#000000"
- stroke-width="0.010"
- id="line1088"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1090"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1092"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1094"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="11.17"
- x2="15.249"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1096"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="11.9"
- x2="15.431"
- y2="11.9"
- stroke="#000000"
- stroke-width="0.010"
- id="line1098"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="11.961"
- x2="14.336"
- y2="11.961"
- stroke="#000000"
- stroke-width="0.010"
- id="line1100"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.022"
- x2="15.431"
- y2="12.022"
- stroke="#000000"
- stroke-width="0.010"
- id="line1102"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.204"
- x2="14.336"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1104"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.143"
- x2="15.431"
- y2="12.143"
- stroke="#000000"
- stroke-width="0.010"
- id="line1106"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.083"
- x2="14.336"
- y2="12.083"
- stroke="#000000"
- stroke-width="0.010"
- id="line1108"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="11.17"
- x2="14.458"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1110"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.17"
- x2="14.579"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1112"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.413"
- x2="14.579"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1114"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.005"
- y1="11.413"
- x2="15.066"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1116"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.442"
- y1="11.353"
- x2="20.584"
- y2="11.34"
- stroke="#000000"
- stroke-width="0.100"
- id="line1118"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.929001"
- y1="11.349"
- x2="16.931"
- y2="12.308"
- stroke="#000000"
- stroke-width="0.100"
- id="line1120"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.931999"
- y1="11.349"
- x2="16.93"
- y2="10.349"
- stroke="#000000"
- stroke-width="0.100"
- id="line1122"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372"
- y1="11.345"
- x2="18.374001"
- y2="12.251"
- stroke="#000000"
- stroke-width="0.100"
- id="line1124"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372999"
- y1="11.345"
- x2="18.370001"
- y2="10.345"
- stroke="#000000"
- stroke-width="0.100"
- id="line1126"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.815001"
- y1="11.342"
- x2="19.816999"
- y2="12.269"
- stroke="#000000"
- stroke-width="0.100"
- id="line1128"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.813"
- y1="11.342"
- x2="19.811001"
- y2="10.342"
- stroke="#000000"
- stroke-width="0.100"
- id="line1130"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1132"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1134"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.018"
- y="12.373"
- id="rect1136"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1138"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1142"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1144"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1146"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1148"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1150"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1152"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1154"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1156"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.461"
- y="12.362"
- id="rect1158"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1160"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1162"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1164"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1166"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1168"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1170"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1172"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1174"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1176"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1178"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.586"
- y="9.9370003"
- id="rect1180"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1182"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1184"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1186"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1188"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1190"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1192"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1194"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1196"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1198"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1200"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.035999"
- y="9.9619999"
- id="rect1202"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1204"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1206"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1208"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1210"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1212"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1214"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1216"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1218"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1220"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1222"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.486"
- y="9.9370003"
- id="rect1224"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1226"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1228"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1230"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1232"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1234"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1236"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1238"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1240"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1242"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1244"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
- id="path1246"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.437,12.852 L 17.509,12.892"
- id="path1248"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.309,12.892 L 16.381,12.852"
- id="path1250"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1252"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1254"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1256"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1258"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1260"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1262"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1264"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1266"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1268"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1270"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1272"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1274"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1276"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1278"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1280"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1282"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1284"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1286"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1288"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1290"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1292"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1294"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1296"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1298"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1300"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1302"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1304"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1306"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1308"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1310"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1312"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1314"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1316"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1318"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1320"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1322"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1324"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1326"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.546"
- x2="20.816"
- y2="10.546"
- stroke="#000000"
- stroke-width="0.010"
- id="line1328"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="10.774"
- x2="21.731001"
- y2="10.774"
- stroke="#000000"
- stroke-width="0.010"
- id="line1330"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.946"
- x2="20.816"
- y2="10.946"
- stroke="#000000"
- stroke-width="0.010"
- id="line1332"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1334"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1336"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1338"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.701"
- y1="11.747"
- x2="21.844999"
- y2="11.747"
- stroke="#000000"
- stroke-width="0.010"
- id="line1340"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1342"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1344"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1346"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1348"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1350"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1352"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1354"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1356"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1358"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1360"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1362"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1364"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="11.518"
- x2="21.445"
- y2="11.518"
- stroke="#000000"
- stroke-width="0.010"
- id="line1366"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1368"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1370"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1372"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1374"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1376"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1378"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.404"
- x2="21.388"
- y2="11.404"
- stroke="#000000"
- stroke-width="0.010"
- id="line1380"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.388"
- y1="11.461"
- x2="21.330999"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1382"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.461"
- x2="20.93"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1384"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1386"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1388"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1390"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.118"
- x2="20.93"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1392"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.987"
- y1="11.118"
- x2="21.045"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1394"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.559"
- y1="11.118"
- x2="21.674"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.433"
- x2="20.759001"
- y2="12.433"
- stroke="#000000"
- stroke-width="0.010"
- id="line1398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.376"
- x2="21.788"
- y2="12.376"
- stroke="#000000"
- stroke-width="0.010"
- id="line1400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.319"
- x2="20.759001"
- y2="12.319"
- stroke="#000000"
- stroke-width="0.010"
- id="line1402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.261"
- x2="21.788"
- y2="12.261"
- stroke="#000000"
- stroke-width="0.010"
- id="line1404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.204"
- x2="20.759001"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.147"
- x2="21.788"
- y2="12.147"
- stroke="#000000"
- stroke-width="0.010"
- id="line1408"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.09"
- x2="20.759001"
- y2="12.09"
- stroke="#000000"
- stroke-width="0.010"
- id="line1410"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="18.610001"
- y="9.026"
- id="text1412"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="18.176001"
- y="9.6260004"
- id="text1414"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
- <text
- x="13.881"
- y="12.895"
- id="text1416"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="13.65"
- y="13.395"
- id="text1418"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVC-BDC</text>
- <text
- x="19.937"
- y="14.042"
- id="text1420"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="20.219"
- y="14.542"
- id="text1422"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">DIVC-APPS</text>
- <rect
- width="1.3150001"
- height="1.161"
- x="12.175"
- y="9.5089998"
- id="rect1424"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.833"
- cy="10.669"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1426"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.833"
- cy="9.5089998"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1428"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.833"
- cy="9.5089998"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1430"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.491,9.509 L 13.491,10.669 C 13.491,10.776 13.196,10.863 12.833,10.863 C 12.47,10.863 12.175,10.776 12.175,10.669 L 12.175,9.509"
- id="path1432"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="14.219"
- y1="11.042"
- x2="13.469"
- y2="10.167"
- stroke="#000000"
- stroke-width="0.100"
- id="line1434"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.537"
- y="10.142"
- id="text1436"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.552"
- y="10.542"
- id="text1438"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1440"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1442"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.7909999"
- y="11.036"
- id="text1444"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
- <path
- d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
- id="path1446"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
- id="path1448"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
- id="path1450"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1452"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1454"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1456"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1458"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1460"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1462"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.1389999"
- x2="1.8710001"
- y2="9.1389999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1464"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="9.4180002"
- x2="0.75400001"
- y2="9.4180002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1466"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.698"
- x2="1.8710001"
- y2="9.698"
- stroke="#000000"
- stroke-width="0.010"
- id="line1468"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.9770002"
- x2="1.8710001"
- y2="9.9770002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1470"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="10.256"
- x2="0.75400001"
- y2="10.256"
- stroke="#000000"
- stroke-width="0.010"
- id="line1472"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1474"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1476"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1478"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.61400002"
- y1="11.374"
- x2="2.0109999"
- y2="11.374"
- stroke="#000000"
- stroke-width="0.010"
- id="line1480"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1482"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1484"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1486"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1488"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1490"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1492"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1494"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1496"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1498"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1500"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1502"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1504"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="10.885"
- x2="1.522"
- y2="10.885"
- stroke="#000000"
- stroke-width="0.010"
- id="line1506"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1508"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1510"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1512"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1514"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1516"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1518"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.745"
- x2="1.452"
- y2="10.745"
- stroke="#000000"
- stroke-width="0.010"
- id="line1520"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.452"
- y1="10.815"
- x2="1.382"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1522"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.815"
- x2="0.89300001"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1524"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1526"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1528"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1530"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.466"
- x2="0.89300001"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1532"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.963"
- y1="10.466"
- x2="1.033"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1534"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.6619999"
- y1="10.466"
- x2="1.801"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1536"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.84"
- x2="1.941"
- y2="12.84"
- stroke="#000000"
- stroke-width="0.010"
- id="line1538"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.77"
- x2="0.68400002"
- y2="12.77"
- stroke="#000000"
- stroke-width="0.010"
- id="line1540"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.701"
- x2="1.941"
- y2="12.701"
- stroke="#000000"
- stroke-width="0.010"
- id="line1542"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.631"
- x2="0.68400002"
- y2="12.631"
- stroke="#000000"
- stroke-width="0.010"
- id="line1544"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.561"
- x2="1.941"
- y2="12.561"
- stroke="#000000"
- stroke-width="0.010"
- id="line1546"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.491"
- x2="0.68400002"
- y2="12.491"
- stroke="#000000"
- stroke-width="0.010"
- id="line1548"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.421"
- x2="1.941"
- y2="12.421"
- stroke="#000000"
- stroke-width="0.010"
- id="line1550"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.351"
- x2="0.68400002"
- y2="12.351"
- stroke="#000000"
- stroke-width="0.010"
- id="line1552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.282"
- x2="1.941"
- y2="12.282"
- stroke="#000000"
- stroke-width="0.010"
- id="line1554"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.212"
- x2="0.68400002"
- y2="12.212"
- stroke="#000000"
- stroke-width="0.010"
- id="line1556"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.142"
- x2="1.941"
- y2="12.142"
- stroke="#000000"
- stroke-width="0.010"
- id="line1558"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.072"
- x2="0.68400002"
- y2="12.072"
- stroke="#000000"
- stroke-width="0.010"
- id="line1560"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.002"
- x2="1.941"
- y2="12.002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1562"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="11.932"
- x2="0.68400002"
- y2="11.932"
- stroke="#000000"
- stroke-width="0.010"
- id="line1564"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.559"
- y="12.296"
- id="rect1566"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.559"
- y="12.296"
- id="rect1568"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.454"
- y="12.401"
- id="rect1570"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
- id="polygon1572"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
- id="polygon1574"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
- id="polygon1576"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
- id="polygon1578"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.8940001"
- y="13.058"
- id="rect1580"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.8940001"
- y="13.058"
- id="rect1582"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
- id="polygon1584"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
- id="polygon1586"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.653"
- y1="11.13"
- x2="-9.6660004"
- y2="11.13"
- stroke="#000000"
- stroke-width="0.100"
- id="line1588"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.289"
- y1="11.13"
- x2="-1.289"
- y2="10.145"
- stroke="#000000"
- stroke-width="0.100"
- id="line1590"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.766"
- y1="11.13"
- x2="-3.766"
- y2="12.295"
- stroke="#000000"
- stroke-width="0.100"
- id="line1592"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.7739999"
- y1="11.13"
- x2="-3.7739999"
- y2="10.099"
- stroke="#000000"
- stroke-width="0.100"
- id="line1594"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-6.0799999"
- y1="11.13"
- x2="-6.0799999"
- y2="12.367"
- stroke="#000000"
- stroke-width="0.100"
- id="line1596"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-6.0939999"
- y1="11.13"
- x2="-6.0939999"
- y2="10.063"
- stroke="#000000"
- stroke-width="0.100"
- id="line1598"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-8.4139996"
- y1="11.13"
- x2="-8.4139996"
- y2="9.5740004"
- stroke="#000000"
- stroke-width="0.100"
- id="line1600"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.069"
- height="0.80199999"
- x="-4.289"
- y="12.216"
- id="rect1602"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.069"
- height="0.80199999"
- x="-4.289"
- y="12.216"
- id="rect1604"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.83700001"
- height="0.55199999"
- x="-4.1729999"
- y="12.332"
- id="rect1606"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
- id="polygon1608"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
- id="polygon1610"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
- id="polygon1612"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
- id="polygon1614"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.5569999"
- y="13.055"
- id="rect1616"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.5569999"
- y="13.055"
- id="rect1618"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
- id="polygon1620"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
- id="polygon1622"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.579"
- y="9.1079998"
- id="rect1624"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.579"
- y="9.1079998"
- id="rect1626"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.474"
- y="9.2139997"
- id="rect1628"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
- id="polygon1630"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
- id="polygon1632"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
- id="polygon1634"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
- id="polygon1636"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.914"
- y="9.8710003"
- id="rect1638"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.914"
- y="9.8710003"
- id="rect1640"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
- id="polygon1642"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
- id="polygon1644"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.2600002"
- y="9.1450005"
- id="rect1646"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.2600002"
- y="9.1450005"
- id="rect1648"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-4.1550002"
- y="9.25"
- id="rect1650"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
- id="polygon1652"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
- id="polygon1654"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
- id="polygon1656"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
- id="polygon1658"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.595"
- y="9.9069996"
- id="rect1660"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.595"
- y="9.9069996"
- id="rect1662"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
- id="polygon1664"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
- id="polygon1666"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-8.9029999"
- y="9.0410004"
- id="rect1668"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-8.9029999"
- y="9.0410004"
- id="rect1670"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-8.7980003"
- y="9.1470003"
- id="rect1672"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
- id="polygon1674"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
- id="polygon1676"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
- id="polygon1678"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
- id="polygon1680"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-8.2379999"
- y="9.8039999"
- id="rect1682"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-8.2379999"
- y="9.8039999"
- id="rect1684"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
- id="polygon1686"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
- id="polygon1688"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
- id="polygon1690"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
- id="polygon1692"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.871,9.841 L -1.823,9.861 L -0.754,9.861 L -0.706,9.841"
- id="path1694"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -0.754,9.861 L -0.682,9.902"
- id="path1696"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.895,9.902 L -1.823,9.861"
- id="path1698"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
- id="polygon1700"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
- id="polygon1702"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
- id="polygon1704"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
- id="polygon1706"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-1.653"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1708"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1710"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1712"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1714"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1716"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1718"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1720"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1722"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1724"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1726"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1728"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1730"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1732"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1734"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1736"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1738"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1740"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1742"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1744"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1746"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1748"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1750"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1752"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1754"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.289"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1756"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-1.289"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1758"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-0.98500001"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1760"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-0.98500001"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1762"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1764"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1766"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1768"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1770"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1772"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1774"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8780003"
- y1="10.141"
- x2="-10.928"
- y2="10.141"
- stroke="#000000"
- stroke-width="0.010"
- id="line1776"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.928"
- y1="10.403"
- x2="-9.8780003"
- y2="10.403"
- stroke="#000000"
- stroke-width="0.010"
- id="line1778"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8780003"
- y1="10.6"
- x2="-10.928"
- y2="10.6"
- stroke="#000000"
- stroke-width="0.010"
- id="line1780"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1782"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1784"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1786"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-11.059"
- y1="11.519"
- x2="-9.7460003"
- y2="11.519"
- stroke="#000000"
- stroke-width="0.010"
- id="line1788"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1790"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1792"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1794"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1796"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1798"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1800"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1802"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1804"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1806"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1808"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1810"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1812"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.928"
- y1="11.256"
- x2="-10.206"
- y2="11.256"
- stroke="#000000"
- stroke-width="0.010"
- id="line1814"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1816"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1818"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1820"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1822"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1824"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1826"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="11.125"
- x2="-10.271"
- y2="11.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line1828"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.271"
- y1="11.191"
- x2="-10.337"
- y2="11.191"
- stroke="#000000"
- stroke-width="0.010"
- id="line1830"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="11.191"
- x2="-10.796"
- y2="11.191"
- stroke="#000000"
- stroke-width="0.010"
- id="line1832"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1834"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1836"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1838"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="10.797"
- x2="-10.796"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1840"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.731"
- y1="10.797"
- x2="-10.665"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1842"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.074"
- y1="10.797"
- x2="-9.9429998"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1844"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.306"
- x2="-10.993"
- y2="12.306"
- stroke="#000000"
- stroke-width="0.010"
- id="line1846"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="12.241"
- x2="-9.8120003"
- y2="12.241"
- stroke="#000000"
- stroke-width="0.010"
- id="line1848"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.175"
- x2="-10.993"
- y2="12.175"
- stroke="#000000"
- stroke-width="0.010"
- id="line1850"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="12.11"
- x2="-9.8120003"
- y2="12.11"
- stroke="#000000"
- stroke-width="0.010"
- id="line1852"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.044"
- x2="-10.993"
- y2="12.044"
- stroke="#000000"
- stroke-width="0.010"
- id="line1854"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="11.978"
- x2="-9.8120003"
- y2="11.978"
- stroke="#000000"
- stroke-width="0.010"
- id="line1856"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="11.913"
- x2="-10.993"
- y2="11.913"
- stroke="#000000"
- stroke-width="0.010"
- id="line1858"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="-6.5710001"
- y="8.3360004"
- id="text1860"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-6.9060001"
- y="8.9359999"
- id="text1862"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
- <text
- x="-10.628"
- y="13.181"
- id="text1864"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="-10.454"
- y="13.681"
- id="text1866"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-APPS</text>
- <rect
- width="1.4450001"
- height="1.275"
- x="2.5510001"
- y="8.6120005"
- id="rect1868"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="3.273"
- cy="9.8870001"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1870"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1872"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1874"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
- id="path1876"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.0109999"
- y1="9.2469997"
- x2="2.586"
- y2="9.2469997"
- stroke="#000000"
- stroke-width="0.100"
- id="line1878"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="2.983"
- y="9.3260002"
- id="text1880"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.928"
- y="9.7259998"
- id="text1882"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
- id="polyline1884"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="1.317"
- y="15.131"
- id="text1886"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
- <text
- x="1.136"
- y="6.0770001"
- id="text1888"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
- <text
- x="12.943"
- y="6.0310001"
- id="text1890"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
- <text
- x="12.358"
- y="15.177"
- id="text1892"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
- <text
- x="-9.9619999"
- y="15.156"
- id="text1894"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - Bldg1</text>
- <text
- x="13.214"
- y="0.46399999"
- id="text1896"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
- <text
- x="1.1109999"
- y="0.46399999"
- id="text1898"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
- <text
- x="12.979"
- y="8.0889997"
- id="text1900"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
- <rect
- width="11.132"
- height="6.5630002"
- x="-11.146"
- y="16.205999"
- id="rect1902"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1904"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1906"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.732"
- height="5.9629998"
- x="-11.446"
- y="16.506001"
- id="rect1908"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1910"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1912"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11.146"
- y1="16.205999"
- x2="-0.014"
- y2="16.205999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1914"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.146"
- y1="22.768999"
- x2="-0.014"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1916"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1918"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1920"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.446"
- y1="16.506001"
- x2="-11.446"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1922"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.28600001"
- y1="16.506001"
- x2="0.28600001"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1924"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1926"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1928"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1930"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1932"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1934"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1936"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1938"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1940"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1942"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1944"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1946"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1948"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1950"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1952"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1954"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1956"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1958"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-5.2220001"
- y="17.145"
- id="text1960"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-5.5609999"
- y="17.745001"
- id="text1962"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
- <text
- x="-10.001"
- y="21.07"
- id="text1964"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="-10.37"
- y="21.57"
- id="text1966"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1968"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1970"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1972"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1974"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1976"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1978"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="19.087"
- x2="-7.6300001"
- y2="19.087"
- stroke="#000000"
- stroke-width="0.010"
- id="line1980"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.6300001"
- y1="19.33"
- x2="-8.6040001"
- y2="19.33"
- stroke="#000000"
- stroke-width="0.010"
- id="line1982"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1984"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1986"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1988"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.665"
- y1="20.181999"
- x2="-7.448"
- y2="20.181999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1990"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1992"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1994"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1996"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect1998"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect2000"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect2002"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2004"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2006"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2008"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2010"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2012"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2014"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4820004"
- y1="19.816999"
- x2="-7.8130002"
- y2="19.816999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2016"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2018"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2020"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2022"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2024"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2026"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2028"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.695"
- x2="-7.8740001"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.010"
- id="line2030"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2032"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2034"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2036"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.8130002"
- y1="19.511999"
- x2="-7.691"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2038"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.242001"
- x2="-7.5089998"
- y2="20.242001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2040"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.302999"
- x2="-8.6040001"
- y2="20.302999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2042"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.364"
- x2="-7.5089998"
- y2="20.364"
- stroke="#000000"
- stroke-width="0.010"
- id="line2044"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.547001"
- x2="-8.6040001"
- y2="20.547001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2046"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.486"
- x2="-7.5089998"
- y2="20.486"
- stroke="#000000"
- stroke-width="0.010"
- id="line2048"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.424999"
- x2="-8.6040001"
- y2="20.424999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2050"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5430002"
- y1="19.511999"
- x2="-8.4820004"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2052"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.511999"
- x2="-8.3599997"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2054"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.756001"
- x2="-8.3599997"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2056"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.9349999"
- y1="19.756001"
- x2="-7.8740001"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2058"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.4980001"
- y1="19.695"
- x2="-2.164"
- y2="19.679001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2060"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9559999"
- y1="19.690001"
- x2="-5.9530001"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.100"
- id="line2062"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9530001"
- y1="19.690001"
- x2="-5.9559999"
- y2="18.690001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2064"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4590001"
- y1="19.686001"
- x2="-4.4559999"
- y2="20.591"
- stroke="#000000"
- stroke-width="0.100"
- id="line2066"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4569998"
- y1="19.686001"
- x2="-4.46"
- y2="18.686001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2068"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.961"
- y1="19.681"
- x2="-2.9579999"
- y2="20.608"
- stroke="#000000"
- stroke-width="0.100"
- id="line2070"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.9619999"
- y1="19.681"
- x2="-2.9649999"
- y2="18.681"
- stroke="#000000"
- stroke-width="0.100"
- id="line2072"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2074"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2076"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8470001"
- y="20.715"
- id="rect2078"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2080"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2082"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2084"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2086"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2088"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2090"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2092"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2094"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2096"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2098"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.329"
- y="20.704"
- id="rect2100"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2102"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2104"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2106"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2108"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2110"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2112"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2114"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2116"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2118"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2120"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-6.2789998"
- y="18.278999"
- id="rect2122"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2124"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2126"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2128"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2130"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2132"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2134"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2136"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2138"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2140"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8039999"
- y="18.278999"
- id="rect2144"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2146"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2148"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2150"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2152"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2154"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2156"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2158"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2160"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2162"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2164"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.3039999"
- y="18.304001"
- id="rect2166"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2168"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2170"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2172"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2174"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2176"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2178"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2180"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2182"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2184"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2186"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
- id="path2188"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -5.503,21.194 L -5.431,21.234"
- id="path2190"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.631,21.234 L -6.559,21.194"
- id="path2192"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2194"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2196"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2198"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2200"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2202"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2204"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2206"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2208"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2210"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2212"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2214"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2216"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2218"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2220"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2222"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2224"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2226"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2228"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2230"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2232"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2234"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2236"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2238"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2240"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2242"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2244"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2246"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2248"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2250"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2252"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2254"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2256"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.17"
- height="1.033"
- x="-10.59"
- y="19.132"
- id="rect2258"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="-10.004"
- cy="20.165001"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2260"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.004"
- cy="19.132"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2262"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.004"
- cy="19.132"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2264"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -9.419,19.132 L -9.419,20.165 C -9.419,20.26 -9.681,20.337 -10.004,20.337 C -10.328,20.337 -10.59,20.26 -10.59,20.165 L -10.59,19.132"
- id="path2266"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-9.3959999"
- y1="19.684"
- x2="-8.665"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.100"
- id="line2268"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-10.303"
- y="19.759001"
- id="text2270"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="-10.288"
- y="20.159"
- id="text2272"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="-0.91500002"
- y="19.843"
- id="text2274"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="-1.867"
- y="22.455999"
- id="text2276"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
- <text
- x="-10.478"
- y="17.114"
- id="text2278"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="-10.147"
- y="17.914"
- id="text2280"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 2</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.554,15.161 -1.554,15.906 -1.821,15.906 -1.821,19.285 "
- id="polyline2282"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2284"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2286"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2288"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2290"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2292"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2294"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2296"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2298"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2300"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2302"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2304"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2306"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2308"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2310"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2312"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="7.8559999"
- y="17.167"
- id="text2314"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="7.5180001"
- y="17.767"
- id="text2316"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
- <text
- x="3.204"
- y="18.118"
- id="text2318"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="2.835"
- y="18.618"
- id="text2320"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
- <text
- x="11.067"
- y="21.718"
- id="text2322"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="11.212"
- y="22.218"
- id="text2324"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-APPS</text>
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2326"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2328"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2330"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2332"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2334"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2336"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="19.246"
- x2="5.112"
- y2="19.246"
- stroke="#000000"
- stroke-width="0.010"
- id="line2338"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.112"
- y1="19.49"
- x2="4.138"
- y2="19.49"
- stroke="#000000"
- stroke-width="0.010"
- id="line2340"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2342"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2344"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2346"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.0770001"
- y1="20.341"
- x2="5.2940001"
- y2="20.341"
- stroke="#000000"
- stroke-width="0.010"
- id="line2348"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2350"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2352"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2354"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2356"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2358"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2360"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2362"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2364"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2366"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2368"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2370"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2372"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.2600002"
- y1="19.976"
- x2="4.9289999"
- y2="19.976"
- stroke="#000000"
- stroke-width="0.010"
- id="line2374"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2376"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2378"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2380"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2382"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2384"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2386"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.855"
- x2="4.868"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.010"
- id="line2388"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2390"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2392"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2394"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.9289999"
- y1="19.672001"
- x2="5.0510001"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.402"
- x2="5.2329998"
- y2="20.402"
- stroke="#000000"
- stroke-width="0.010"
- id="line2398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.462999"
- x2="4.138"
- y2="20.462999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.524"
- x2="5.2329998"
- y2="20.524"
- stroke="#000000"
- stroke-width="0.010"
- id="line2402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.705999"
- x2="4.138"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.645"
- x2="5.2329998"
- y2="20.645"
- stroke="#000000"
- stroke-width="0.010"
- id="line2406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.584999"
- x2="4.138"
- y2="20.584999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2408"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.1989999"
- y1="19.672001"
- x2="4.2600002"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2410"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.672001"
- x2="4.382"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2412"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.915001"
- x2="4.382"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2414"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.8070002"
- y1="19.915001"
- x2="4.868"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2416"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.244"
- y1="19.855"
- x2="10.386"
- y2="19.841999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2418"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7309999"
- y1="19.851"
- x2="6.7329998"
- y2="20.809999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2420"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7350001"
- y1="19.851"
- x2="6.7319999"
- y2="18.851"
- stroke="#000000"
- stroke-width="0.100"
- id="line2422"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1739998"
- y1="19.847"
- x2="8.1759996"
- y2="20.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line2424"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1750002"
- y1="19.847"
- x2="8.1730003"
- y2="18.848"
- stroke="#000000"
- stroke-width="0.100"
- id="line2426"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6169996"
- y1="19.844"
- x2="9.6190004"
- y2="20.771"
- stroke="#000000"
- stroke-width="0.100"
- id="line2428"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6160002"
- y1="19.844"
- x2="9.6129999"
- y2="18.844"
- stroke="#000000"
- stroke-width="0.100"
- id="line2430"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2432"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2434"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8210001"
- y="20.875"
- id="rect2436"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2438"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2440"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2442"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2444"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2446"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2448"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2450"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2452"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2454"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2456"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2629995"
- y="20.864"
- id="rect2458"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2460"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2462"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2464"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2466"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2468"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2470"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2472"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2474"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2476"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2478"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.388"
- y="18.438999"
- id="rect2480"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2482"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2484"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2486"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2488"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2490"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2492"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2494"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2496"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2498"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2500"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8379998"
- y="18.464001"
- id="rect2502"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2504"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2506"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2508"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2510"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2512"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2514"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2516"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2518"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2520"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2522"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2880001"
- y="18.438999"
- id="rect2524"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2526"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2528"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2530"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2532"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2534"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2536"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2538"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2540"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2542"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2544"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
- id="path2546"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.239,21.354 L 7.311,21.394"
- id="path2548"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.111,21.394 L 6.183,21.354"
- id="path2550"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2552"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2554"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2556"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2558"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2560"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2562"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2564"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2566"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2568"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2570"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2572"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2574"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2576"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2578"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2580"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2582"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2584"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2586"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2588"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2590"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2592"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2594"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2596"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2598"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2600"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2602"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2604"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2606"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2608"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2610"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2612"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2614"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2616"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2618"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2620"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2622"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2624"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2626"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.048"
- x2="10.618"
- y2="19.048"
- stroke="#000000"
- stroke-width="0.010"
- id="line2628"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="19.275999"
- x2="11.533"
- y2="19.275999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2630"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.448"
- x2="10.618"
- y2="19.448"
- stroke="#000000"
- stroke-width="0.010"
- id="line2632"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2634"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2636"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2638"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.504"
- y1="20.249001"
- x2="11.647"
- y2="20.249001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2640"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2642"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2644"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2646"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2648"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2650"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2652"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2654"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2656"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2658"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2660"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2662"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2664"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="20.02"
- x2="11.247"
- y2="20.02"
- stroke="#000000"
- stroke-width="0.010"
- id="line2666"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2668"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2670"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2672"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2674"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2676"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2678"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.906"
- x2="11.19"
- y2="19.906"
- stroke="#000000"
- stroke-width="0.010"
- id="line2680"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.19"
- y1="19.962999"
- x2="11.133"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2682"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.962999"
- x2="10.732"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2684"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2686"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2688"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2690"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.620001"
- x2="10.732"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.79"
- y1="19.620001"
- x2="10.847"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.362"
- y1="19.620001"
- x2="11.476"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.934999"
- x2="10.561"
- y2="20.934999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.878"
- x2="11.59"
- y2="20.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line2700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.820999"
- x2="10.561"
- y2="20.820999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2702"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.763"
- x2="11.59"
- y2="20.763"
- stroke="#000000"
- stroke-width="0.010"
- id="line2704"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.705999"
- x2="10.561"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2706"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.649"
- x2="11.59"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.010"
- id="line2708"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.591999"
- x2="10.561"
- y2="20.591999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2710"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.4960001"
- y1="19.819"
- x2="4.0770001"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.100"
- id="line2712"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.183"
- height="1.044"
- x="2.302"
- y="19.268999"
- id="rect2714"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="2.8940001"
- cy="20.312"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2716"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2718"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2720"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
- id="path2722"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="2.589"
- y="19.868999"
- id="text2724"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.6040001"
- y="20.268999"
- id="text2726"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="2.0469999"
- y="22.452"
- id="text2728"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
- <text
- x="12.072"
- y="17.239"
- id="text2730"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="12.402"
- y="18.039"
- id="text2732"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 3</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
- id="polyline2734"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.1"
- y1="22.393"
- x2="15.55"
- y2="23.143"
- stroke="#F7F7F7"
- stroke-width="0.100"
- id="line2736"
- style="stroke:#f7f7f7;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="34.602001cm"
- height="23.67cm"
- viewBox="-11.55 -0.456 23.052 23.213"
- id="svg2">
- <defs
- id="defs2769" />
- <rect
- width="13.8"
- height="6.513"
- x="1.375"
- y="16.256001"
- id="rect4"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path6"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path8"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="14.4"
- height="5.9130001"
- x="1.075"
- y="16.556"
- id="rect10"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path12"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path14"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="1.375"
- y1="16.256001"
- x2="15.175"
- y2="16.256001"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.375"
- y1="22.768999"
- x2="15.175"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.075"
- y1="16.556"
- x2="1.075"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="15.475"
- y1="16.556"
- x2="15.475"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.617"
- height="6.8530002"
- x="0.495"
- y="-0.40599999"
- id="rect32"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path34"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path36"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.217"
- height="6.2529998"
- x="0.19499999"
- y="-0.106"
- id="rect38"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path40"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path42"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="0.495"
- y1="-0.40599999"
- x2="11.112"
- y2="-0.40599999"
- stroke="#000000"
- stroke-width="0.050"
- id="line44"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.495"
- y1="6.447"
- x2="11.112"
- y2="6.447"
- stroke="#000000"
- stroke-width="0.050"
- id="line46"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.19499999"
- y1="-0.106"
- x2="0.19499999"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line52"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.412"
- y1="-0.106"
- x2="11.412"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line54"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.337"
- height="6.8600001"
- x="12.35"
- y="-0.43099999"
- id="rect60"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path62"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path64"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="10.937"
- height="6.2600002"
- x="12.05"
- y="-0.131"
- id="rect66"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path68"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path70"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="12.35"
- y1="-0.43099999"
- x2="22.687"
- y2="-0.43099999"
- stroke="#000000"
- stroke-width="0.050"
- id="line72"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.35"
- y1="6.4289999"
- x2="22.687"
- y2="6.4289999"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.05"
- y1="-0.131"
- x2="12.05"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line80"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="22.987"
- y1="-0.131"
- x2="22.987"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line82"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.821"
- height="8.375"
- x="11.905"
- y="7.244"
- id="rect88"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path90"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path92"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.421"
- height="7.7750001"
- x="11.605"
- y="7.5440001"
- id="rect94"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path96"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path98"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="11.905"
- y1="7.244"
- x2="22.726999"
- y2="7.244"
- stroke="#000000"
- stroke-width="0.050"
- id="line100"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.905"
- y1="15.619"
- x2="22.726999"
- y2="15.619"
- stroke="#000000"
- stroke-width="0.050"
- id="line102"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path104"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path106"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.605"
- y1="7.5440001"
- x2="11.605"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line108"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="23.027"
- y1="7.5440001"
- x2="23.027"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line110"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path112"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path114"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="15.45"
- height="8.3719997"
- x="-11.225"
- y="7.1339998"
- id="rect116"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
- id="path118"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 4.525,7.434 C 4.525,7.2683146 4.3906854,7.134 4.225,7.134"
- id="path120"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="16.049999"
- height="7.7719998"
- x="-11.525"
- y="7.434"
- id="rect122"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
- id="path124"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 4.225,15.506 C 4.3906854,15.506 4.525,15.371685 4.525,15.206"
- id="path126"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11.225"
- y1="7.1339998"
- x2="4.2249999"
- y2="7.1339998"
- stroke="#000000"
- stroke-width="0.050"
- id="line128"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.225"
- y1="15.506"
- x2="4.2249999"
- y2="15.506"
- stroke="#000000"
- stroke-width="0.050"
- id="line130"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
- id="path132"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 4.525,7.434 C 4.525,7.2683146 4.3906854,7.134 4.225,7.134"
- id="path134"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.525"
- y1="7.434"
- x2="-11.525"
- y2="15.206"
- stroke="#000000"
- stroke-width="0.050"
- id="line136"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="4.5250001"
- y1="7.434"
- x2="4.5250001"
- y2="15.206"
- stroke="#000000"
- stroke-width="0.050"
- id="line138"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
- id="path140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 4.225,15.506 C 4.3906854,15.506 4.525,15.371685 4.525,15.206"
- id="path142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.95"
- y1="11.168"
- x2="4.8109999"
- y2="11.165"
- stroke="#000000"
- stroke-width="0.300"
- id="line144"
- style="stroke:#000000;stroke-width:0.30000001" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
- id="polyline146"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
- id="polyline148"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect150"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
- id="path156"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
- id="path158"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
- id="polygon160"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
- id="polygon162"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
- id="polygon164"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
- id="polygon166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
- id="path168"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
- id="path170"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
- id="polygon172"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
- id="polygon174"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
- id="polygon176"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
- id="polygon178"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.306"
- y1="11.165"
- x2="-1.3279999"
- y2="14.136"
- stroke="#000000"
- stroke-width="0.100"
- id="line180"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.71700001"
- y="7.6999998"
- id="text182"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="0.37799999"
- y="8.1999998"
- id="text184"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-PDC</text>
- <line
- x1="6.118"
- y1="13.16"
- x2="7.7179999"
- y2="13.135"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.10,0.10"
- id="line186"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <text
- x="8.4429998"
- y="13.325"
- id="text188"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
- id="polyline190"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-3.0239999"
- y="14.751"
- id="text192"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="4.1469998"
- y="17.031"
- id="text194"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect196"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect202"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect204"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="2.027"
- x2="3.5869999"
- y2="2.027"
- stroke="#000000"
- stroke-width="0.010"
- id="line208"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.5869999"
- y1="2.2709999"
- x2="2.6140001"
- y2="2.2709999"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect212"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect214"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect216"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.553"
- y1="3.122"
- x2="3.77"
- y2="3.122"
- stroke="#000000"
- stroke-width="0.010"
- id="line218"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect220"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect222"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect226"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect228"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect230"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect232"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect234"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect236"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect238"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect240"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect242"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7360001"
- y1="2.757"
- x2="3.405"
- y2="2.757"
- stroke="#000000"
- stroke-width="0.010"
- id="line244"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect246"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect248"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect250"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect252"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect254"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect256"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.6359999"
- x2="3.3440001"
- y2="2.6359999"
- stroke="#000000"
- stroke-width="0.010"
- id="line258"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect260"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect262"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect264"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.405"
- y1="2.4530001"
- x2="3.527"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line266"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.1830001"
- x2="3.7090001"
- y2="3.1830001"
- stroke="#000000"
- stroke-width="0.010"
- id="line268"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.244"
- x2="2.6140001"
- y2="3.244"
- stroke="#000000"
- stroke-width="0.010"
- id="line270"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.3050001"
- x2="3.7090001"
- y2="3.3050001"
- stroke="#000000"
- stroke-width="0.010"
- id="line272"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.487"
- x2="2.6140001"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line274"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.427"
- x2="3.7090001"
- y2="3.427"
- stroke="#000000"
- stroke-width="0.010"
- id="line276"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.3659999"
- x2="2.6140001"
- y2="3.3659999"
- stroke="#000000"
- stroke-width="0.010"
- id="line278"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.675"
- y1="2.4530001"
- x2="2.7360001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line280"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.4530001"
- x2="2.8570001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line282"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.697"
- x2="2.8570001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line284"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.283"
- y1="2.697"
- x2="3.3440001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line286"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.72"
- y1="2.6359999"
- x2="8.8620005"
- y2="2.6229999"
- stroke="#000000"
- stroke-width="0.100"
- id="line288"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.2069998"
- y1="2.632"
- x2="5.2090001"
- y2="3.5910001"
- stroke="#000000"
- stroke-width="0.100"
- id="line290"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.21"
- y1="2.632"
- x2="5.2080002"
- y2="1.632"
- stroke="#000000"
- stroke-width="0.100"
- id="line292"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.6500001"
- y1="2.6289999"
- x2="6.652"
- y2="3.5339999"
- stroke="#000000"
- stroke-width="0.100"
- id="line294"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.651"
- y1="2.6289999"
- x2="6.6479998"
- y2="1.6289999"
- stroke="#000000"
- stroke-width="0.100"
- id="line296"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.092"
- y1="2.625"
- x2="8.0950003"
- y2="3.552"
- stroke="#000000"
- stroke-width="0.100"
- id="line298"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.0909996"
- y1="2.625"
- x2="8.0889997"
- y2="1.625"
- stroke="#000000"
- stroke-width="0.100"
- id="line300"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect302"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect304"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.296"
- y="3.6559999"
- id="rect306"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon308"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon310"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon312"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon314"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect316"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect318"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon320"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon322"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect324"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect326"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7389998"
- y="3.645"
- id="rect328"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon330"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon332"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon334"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon336"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect338"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect340"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon342"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon344"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect346"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect348"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="4.8639998"
- y="1.22"
- id="rect350"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon352"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon354"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon356"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon358"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect360"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect362"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon364"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon366"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect368"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect370"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.3140001"
- y="1.245"
- id="rect372"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon374"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon376"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon378"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon380"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect382"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect384"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon386"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon388"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect390"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect392"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7639999"
- y="1.22"
- id="rect394"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon396"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon398"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon400"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon402"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect404"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect406"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon408"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon410"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon412"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon414"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
- id="path416"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.715,4.135 L 5.787,4.175"
- id="path418"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.587,4.175 L 4.659,4.135"
- id="path420"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon422"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon424"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon426"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon428"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse430"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse432"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse434"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse436"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse438"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse440"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse442"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse444"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse446"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse448"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse450"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse452"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse454"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse456"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse458"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse460"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse462"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse464"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse466"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse468"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse470"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse472"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse474"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse476"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse478"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse480"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse482"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse484"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect486"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect488"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect490"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect492"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect494"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect496"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="1.829"
- x2="9.0939999"
- y2="1.829"
- stroke="#000000"
- stroke-width="0.010"
- id="line498"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.0580001"
- x2="10.009"
- y2="2.0580001"
- stroke="#000000"
- stroke-width="0.010"
- id="line500"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="2.2290001"
- x2="9.0939999"
- y2="2.2290001"
- stroke="#000000"
- stroke-width="0.010"
- id="line502"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect504"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect506"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect508"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.9790001"
- y1="3.03"
- x2="10.123"
- y2="3.03"
- stroke="#000000"
- stroke-width="0.010"
- id="line510"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect512"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect514"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect516"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect518"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect520"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect522"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect524"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect526"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect528"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect530"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect532"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect534"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.8010001"
- x2="9.7229996"
- y2="2.8010001"
- stroke="#000000"
- stroke-width="0.010"
- id="line536"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect538"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect540"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect542"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect544"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect546"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect548"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.687"
- x2="9.6660004"
- y2="2.687"
- stroke="#000000"
- stroke-width="0.010"
- id="line550"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.6660004"
- y1="2.744"
- x2="9.6090002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.744"
- x2="9.2080002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line554"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect556"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect558"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect560"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.401"
- x2="9.2080002"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line562"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.2650003"
- y1="2.401"
- x2="9.323"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line564"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.8369999"
- y1="2.401"
- x2="9.9519997"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line566"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.7160001"
- x2="9.0369997"
- y2="3.7160001"
- stroke="#000000"
- stroke-width="0.010"
- id="line568"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.6589999"
- x2="10.066"
- y2="3.6589999"
- stroke="#000000"
- stroke-width="0.010"
- id="line570"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.602"
- x2="9.0369997"
- y2="3.602"
- stroke="#000000"
- stroke-width="0.010"
- id="line572"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.5439999"
- x2="10.066"
- y2="3.5439999"
- stroke="#000000"
- stroke-width="0.010"
- id="line574"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.487"
- x2="9.0369997"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line576"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.4300001"
- x2="10.066"
- y2="3.4300001"
- stroke="#000000"
- stroke-width="0.010"
- id="line578"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.3729999"
- x2="9.0369997"
- y2="3.3729999"
- stroke="#000000"
- stroke-width="0.010"
- id="line580"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="5.9629998"
- y="5.2589998"
- id="text582"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="5.5580001"
- y="5.8590002"
- id="text584"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
- <text
- x="1.234"
- y="4.1529999"
- id="text586"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="1.053"
- y="4.6529999"
- id="text588"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-BDC</text>
- <text
- x="9.5100002"
- y="4.4749999"
- id="text590"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="9.3299999"
- y="4.9749999"
- id="text592"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-PDC</text>
- <rect
- width="1.291"
- height="1.1390001"
- x="0.61699998"
- y="2.0880001"
- id="rect594"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="1.263"
- cy="3.227"
- rx="0.64499998"
- ry="0.19"
- id="ellipse596"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse598"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse600"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
- id="path602"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.928"
- y1="2.523"
- x2="2.503"
- y2="2.523"
- stroke="#000000"
- stroke-width="0.100"
- id="line604"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.935"
- y="2.7219999"
- id="text606"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="0.94999999"
- y="3.122"
- id="text608"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect610"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect612"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect614"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect616"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect618"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect620"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="2.1900001"
- x2="15.431"
- y2="2.1900001"
- stroke="#000000"
- stroke-width="0.010"
- id="line622"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="2.4330001"
- x2="14.458"
- y2="2.4330001"
- stroke="#000000"
- stroke-width="0.010"
- id="line624"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect626"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect628"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect630"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="3.2850001"
- x2="15.614"
- y2="3.2850001"
- stroke="#000000"
- stroke-width="0.010"
- id="line632"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect634"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect636"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect638"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect640"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect642"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect644"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect646"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect648"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect650"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect652"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect654"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect656"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.58"
- y1="2.9200001"
- x2="15.249"
- y2="2.9200001"
- stroke="#000000"
- stroke-width="0.010"
- id="line658"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect660"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect662"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect664"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect666"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect668"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect670"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.7980001"
- x2="15.188"
- y2="2.7980001"
- stroke="#000000"
- stroke-width="0.010"
- id="line672"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect674"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect676"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect678"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.249"
- y1="2.615"
- x2="15.371"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line680"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.345"
- x2="15.553"
- y2="3.345"
- stroke="#000000"
- stroke-width="0.010"
- id="line682"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.4059999"
- x2="14.458"
- y2="3.4059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line684"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.467"
- x2="15.553"
- y2="3.467"
- stroke="#000000"
- stroke-width="0.010"
- id="line686"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.6500001"
- x2="14.458"
- y2="3.6500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line688"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.589"
- x2="15.553"
- y2="3.589"
- stroke="#000000"
- stroke-width="0.010"
- id="line690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.5280001"
- x2="14.458"
- y2="3.5280001"
- stroke="#000000"
- stroke-width="0.010"
- id="line692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="2.615"
- x2="14.58"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.615"
- x2="14.701"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.859"
- x2="14.701"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="2.859"
- x2="15.188"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.564"
- y1="2.7980001"
- x2="20.705"
- y2="2.7850001"
- stroke="#000000"
- stroke-width="0.100"
- id="line702"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.051001"
- y1="2.7939999"
- x2="17.052999"
- y2="3.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line704"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.054001"
- y1="2.7939999"
- x2="17.052"
- y2="1.794"
- stroke="#000000"
- stroke-width="0.100"
- id="line706"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.493"
- y1="2.7909999"
- x2="18.496"
- y2="3.6960001"
- stroke="#000000"
- stroke-width="0.100"
- id="line708"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.495001"
- y1="2.7909999"
- x2="18.492001"
- y2="1.791"
- stroke="#000000"
- stroke-width="0.100"
- id="line710"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.936001"
- y1="2.7869999"
- x2="19.938999"
- y2="3.714"
- stroke="#000000"
- stroke-width="0.100"
- id="line712"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.934999"
- y1="2.7869999"
- x2="19.933001"
- y2="1.7869999"
- stroke="#000000"
- stroke-width="0.100"
- id="line714"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect716"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect718"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.139999"
- y="3.8180001"
- id="rect720"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon722"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon724"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon726"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon728"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect730"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect732"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon734"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon736"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect738"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect740"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.583"
- y="3.8069999"
- id="rect742"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon744"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon746"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon748"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon750"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect752"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect754"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon756"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon758"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect760"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect762"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.708"
- y="1.382"
- id="rect764"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon766"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon768"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon770"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon772"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect774"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect776"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon778"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon780"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect782"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect784"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.158001"
- y="1.4069999"
- id="rect786"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon788"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon790"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon792"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon794"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect796"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect798"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon800"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon802"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect804"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect806"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.608"
- y="1.382"
- id="rect808"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon810"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon812"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon814"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon816"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect818"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect820"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon822"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon824"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon826"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon828"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
- id="path830"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.558,4.297 L 17.63,4.337"
- id="path832"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.43,4.337 L 16.502,4.297"
- id="path834"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon836"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon838"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon840"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon842"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse844"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse846"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse848"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse850"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse852"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse854"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse856"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse858"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse860"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse862"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse864"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse866"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse868"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse870"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse872"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse874"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse876"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse878"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse880"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse882"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse884"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse886"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse888"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse890"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse892"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse894"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse896"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse898"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect900"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect902"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect904"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect906"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect908"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect910"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="1.9910001"
- x2="20.938"
- y2="1.9910001"
- stroke="#000000"
- stroke-width="0.010"
- id="line912"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.22"
- x2="21.853001"
- y2="2.22"
- stroke="#000000"
- stroke-width="0.010"
- id="line914"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="2.391"
- x2="20.938"
- y2="2.391"
- stroke="#000000"
- stroke-width="0.010"
- id="line916"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect918"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect920"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect922"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.823"
- y1="3.1919999"
- x2="21.966999"
- y2="3.1919999"
- stroke="#000000"
- stroke-width="0.010"
- id="line924"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect926"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect928"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect930"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect932"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect934"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect936"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect938"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect940"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect942"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect944"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect946"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect948"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.9630001"
- x2="21.566999"
- y2="2.9630001"
- stroke="#000000"
- stroke-width="0.010"
- id="line950"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect952"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect954"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect956"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect958"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect960"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect962"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.849"
- x2="21.51"
- y2="2.849"
- stroke="#000000"
- stroke-width="0.010"
- id="line964"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.51"
- y1="2.9059999"
- x2="21.452"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line966"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.9059999"
- x2="21.052"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line968"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect970"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect972"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect974"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.563"
- x2="21.052"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line976"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.108999"
- y1="2.563"
- x2="21.167"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line978"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.681"
- y1="2.563"
- x2="21.796"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line980"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.878"
- x2="20.881001"
- y2="3.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line982"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.8210001"
- x2="21.91"
- y2="3.8210001"
- stroke="#000000"
- stroke-width="0.010"
- id="line984"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.7639999"
- x2="20.881001"
- y2="3.7639999"
- stroke="#000000"
- stroke-width="0.010"
- id="line986"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.707"
- x2="21.91"
- y2="3.707"
- stroke="#000000"
- stroke-width="0.010"
- id="line988"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.6489999"
- x2="20.881001"
- y2="3.6489999"
- stroke="#000000"
- stroke-width="0.010"
- id="line990"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.592"
- x2="21.91"
- y2="3.592"
- stroke="#000000"
- stroke-width="0.010"
- id="line992"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.5350001"
- x2="20.881001"
- y2="3.5350001"
- stroke="#000000"
- stroke-width="0.010"
- id="line994"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="18.056999"
- y="5.3460002"
- id="text996"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="17.650999"
- y="5.9460001"
- id="text998"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
- <text
- x="14.353"
- y="4.415"
- id="text1000"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="14.288"
- y="4.915"
- id="text1002"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-BDC</text>
- <text
- x="21.112"
- y="4.5809999"
- id="text1004"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="21.048"
- y="5.0809999"
- id="text1006"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-PDC</text>
- <rect
- width="1.326"
- height="1.17"
- x="12.426"
- y="2.155"
- id="rect1008"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="13.089"
- cy="3.326"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1010"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.089"
- cy="2.155"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1012"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.089"
- cy="2.155"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1014"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.752,2.155 L 13.752,3.326 C 13.752,3.434 13.455,3.521 13.089,3.521 C 12.723,3.521 12.426,3.434 12.426,3.326 L 12.426,2.155"
- id="path1016"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.775"
- y1="2.6440001"
- x2="14.372"
- y2="2.648"
- stroke="#000000"
- stroke-width="0.100"
- id="line1018"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.767"
- y="2.819"
- id="text1020"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.782"
- y="3.2190001"
- id="text1022"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1024"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1026"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1028"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1030"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1032"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1034"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="10.744"
- x2="15.309"
- y2="10.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line1036"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.309"
- y1="10.988"
- x2="14.336"
- y2="10.988"
- stroke="#000000"
- stroke-width="0.010"
- id="line1038"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1040"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1042"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1044"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.275"
- y1="11.839"
- x2="15.492"
- y2="11.839"
- stroke="#000000"
- stroke-width="0.010"
- id="line1046"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1048"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1050"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1052"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1054"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1056"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1058"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1060"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1062"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1064"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1066"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1068"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1070"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="11.474"
- x2="15.127"
- y2="11.474"
- stroke="#000000"
- stroke-width="0.010"
- id="line1072"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1074"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1076"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1078"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1080"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1082"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1084"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.353"
- x2="15.066"
- y2="11.353"
- stroke="#000000"
- stroke-width="0.010"
- id="line1086"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1088"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1090"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1092"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="11.17"
- x2="15.249"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1094"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="11.9"
- x2="15.431"
- y2="11.9"
- stroke="#000000"
- stroke-width="0.010"
- id="line1096"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="11.961"
- x2="14.336"
- y2="11.961"
- stroke="#000000"
- stroke-width="0.010"
- id="line1098"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.022"
- x2="15.431"
- y2="12.022"
- stroke="#000000"
- stroke-width="0.010"
- id="line1100"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.204"
- x2="14.336"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1102"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.143"
- x2="15.431"
- y2="12.143"
- stroke="#000000"
- stroke-width="0.010"
- id="line1104"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.083"
- x2="14.336"
- y2="12.083"
- stroke="#000000"
- stroke-width="0.010"
- id="line1106"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="11.17"
- x2="14.458"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1108"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.17"
- x2="14.579"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1110"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.413"
- x2="14.579"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1112"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.005"
- y1="11.413"
- x2="15.066"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1114"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.442"
- y1="11.353"
- x2="20.584"
- y2="11.34"
- stroke="#000000"
- stroke-width="0.100"
- id="line1116"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.929001"
- y1="11.349"
- x2="16.931"
- y2="12.308"
- stroke="#000000"
- stroke-width="0.100"
- id="line1118"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.931999"
- y1="11.349"
- x2="16.93"
- y2="10.349"
- stroke="#000000"
- stroke-width="0.100"
- id="line1120"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372"
- y1="11.345"
- x2="18.374001"
- y2="12.251"
- stroke="#000000"
- stroke-width="0.100"
- id="line1122"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372999"
- y1="11.345"
- x2="18.370001"
- y2="10.345"
- stroke="#000000"
- stroke-width="0.100"
- id="line1124"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.815001"
- y1="11.342"
- x2="19.816999"
- y2="12.269"
- stroke="#000000"
- stroke-width="0.100"
- id="line1126"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.813"
- y1="11.342"
- x2="19.811001"
- y2="10.342"
- stroke="#000000"
- stroke-width="0.100"
- id="line1128"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1130"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1132"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.018"
- y="12.373"
- id="rect1134"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1136"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1138"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1140"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1144"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1146"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1148"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1150"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1152"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1154"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.461"
- y="12.362"
- id="rect1156"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1158"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1160"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1162"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1164"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1166"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1168"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1170"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1172"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1174"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1176"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.586"
- y="9.9370003"
- id="rect1178"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1180"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1182"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1184"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1186"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1188"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1190"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1192"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1194"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1196"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1198"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.035999"
- y="9.9619999"
- id="rect1200"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1202"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1204"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1206"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1208"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1210"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1212"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1214"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1216"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1218"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1220"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.486"
- y="9.9370003"
- id="rect1222"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1224"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1226"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1228"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1230"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1232"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1234"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1236"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1238"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1240"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1242"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
- id="path1244"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.437,12.852 L 17.509,12.892"
- id="path1246"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.309,12.892 L 16.381,12.852"
- id="path1248"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1250"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1252"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1254"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1256"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1258"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1260"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1262"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1264"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1266"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1268"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1270"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1272"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1274"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1276"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1278"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1280"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1282"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1284"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1286"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1288"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1290"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1292"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1294"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1296"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1298"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1300"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1302"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1304"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1306"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1308"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1310"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1312"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1314"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1316"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1318"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1320"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1322"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1324"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.546"
- x2="20.816"
- y2="10.546"
- stroke="#000000"
- stroke-width="0.010"
- id="line1326"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="10.774"
- x2="21.731001"
- y2="10.774"
- stroke="#000000"
- stroke-width="0.010"
- id="line1328"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.946"
- x2="20.816"
- y2="10.946"
- stroke="#000000"
- stroke-width="0.010"
- id="line1330"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1332"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1334"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1336"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.701"
- y1="11.747"
- x2="21.844999"
- y2="11.747"
- stroke="#000000"
- stroke-width="0.010"
- id="line1338"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1340"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1342"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1344"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1346"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1348"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1350"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1352"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1354"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1356"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1358"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1360"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1362"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="11.518"
- x2="21.445"
- y2="11.518"
- stroke="#000000"
- stroke-width="0.010"
- id="line1364"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1366"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1368"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1370"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1372"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1374"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1376"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.404"
- x2="21.388"
- y2="11.404"
- stroke="#000000"
- stroke-width="0.010"
- id="line1378"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.388"
- y1="11.461"
- x2="21.330999"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1380"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.461"
- x2="20.93"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1382"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1384"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1386"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1388"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.118"
- x2="20.93"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1390"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.987"
- y1="11.118"
- x2="21.045"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1392"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.559"
- y1="11.118"
- x2="21.674"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1394"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.433"
- x2="20.759001"
- y2="12.433"
- stroke="#000000"
- stroke-width="0.010"
- id="line1396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.376"
- x2="21.788"
- y2="12.376"
- stroke="#000000"
- stroke-width="0.010"
- id="line1398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.319"
- x2="20.759001"
- y2="12.319"
- stroke="#000000"
- stroke-width="0.010"
- id="line1400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.261"
- x2="21.788"
- y2="12.261"
- stroke="#000000"
- stroke-width="0.010"
- id="line1402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.204"
- x2="20.759001"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.147"
- x2="21.788"
- y2="12.147"
- stroke="#000000"
- stroke-width="0.010"
- id="line1406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.09"
- x2="20.759001"
- y2="12.09"
- stroke="#000000"
- stroke-width="0.010"
- id="line1408"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="17.735001"
- y="9.026"
- id="text1410"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="17.301001"
- y="9.6260004"
- id="text1412"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
- <text
- x="14.206"
- y="12.995"
- id="text1414"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="13.878"
- y="13.495"
- id="text1416"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-BDC</text>
- <text
- x="20.712"
- y="13.518"
- id="text1418"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="20.302"
- y="14.018"
- id="text1420"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WADC-APPS</text>
- <rect
- width="1.3150001"
- height="1.161"
- x="12"
- y="10.659"
- id="rect1422"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.658"
- cy="11.819"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1424"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.658"
- cy="10.659"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1426"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.658"
- cy="10.659"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1428"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.316,10.659 L 13.316,11.819 C 13.316,11.926 13.021,12.013 12.658,12.013 C 12.295,12.013 12,11.926 12,11.819 L 12,10.659"
- id="path1430"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="14.275"
- y1="11.353"
- x2="13.275"
- y2="11.344"
- stroke="#000000"
- stroke-width="0.100"
- id="line1432"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.337"
- y="11.292"
- id="text1434"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.352"
- y="11.692"
- id="text1436"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1438"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1440"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.7909999"
- y="11.036"
- id="text1442"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
- <path
- d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
- id="path1444"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
- id="path1446"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
- id="path1448"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1450"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1452"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1454"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1456"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1458"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1460"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.1389999"
- x2="1.8710001"
- y2="9.1389999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1462"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="9.4180002"
- x2="0.75400001"
- y2="9.4180002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1464"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.698"
- x2="1.8710001"
- y2="9.698"
- stroke="#000000"
- stroke-width="0.010"
- id="line1466"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.9770002"
- x2="1.8710001"
- y2="9.9770002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1468"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="10.256"
- x2="0.75400001"
- y2="10.256"
- stroke="#000000"
- stroke-width="0.010"
- id="line1470"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1472"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1474"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1476"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.61400002"
- y1="11.374"
- x2="2.0109999"
- y2="11.374"
- stroke="#000000"
- stroke-width="0.010"
- id="line1478"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1480"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1482"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1484"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1486"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1488"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1490"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1492"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1494"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1496"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1498"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1500"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1502"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="10.885"
- x2="1.522"
- y2="10.885"
- stroke="#000000"
- stroke-width="0.010"
- id="line1504"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1506"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1508"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1510"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1512"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1514"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1516"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.745"
- x2="1.452"
- y2="10.745"
- stroke="#000000"
- stroke-width="0.010"
- id="line1518"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.452"
- y1="10.815"
- x2="1.382"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1520"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.815"
- x2="0.89300001"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1522"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1524"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1526"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1528"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.466"
- x2="0.89300001"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1530"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.963"
- y1="10.466"
- x2="1.033"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1532"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.6619999"
- y1="10.466"
- x2="1.801"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1534"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.84"
- x2="1.941"
- y2="12.84"
- stroke="#000000"
- stroke-width="0.010"
- id="line1536"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.77"
- x2="0.68400002"
- y2="12.77"
- stroke="#000000"
- stroke-width="0.010"
- id="line1538"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.701"
- x2="1.941"
- y2="12.701"
- stroke="#000000"
- stroke-width="0.010"
- id="line1540"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.631"
- x2="0.68400002"
- y2="12.631"
- stroke="#000000"
- stroke-width="0.010"
- id="line1542"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.561"
- x2="1.941"
- y2="12.561"
- stroke="#000000"
- stroke-width="0.010"
- id="line1544"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.491"
- x2="0.68400002"
- y2="12.491"
- stroke="#000000"
- stroke-width="0.010"
- id="line1546"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.421"
- x2="1.941"
- y2="12.421"
- stroke="#000000"
- stroke-width="0.010"
- id="line1548"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.351"
- x2="0.68400002"
- y2="12.351"
- stroke="#000000"
- stroke-width="0.010"
- id="line1550"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.282"
- x2="1.941"
- y2="12.282"
- stroke="#000000"
- stroke-width="0.010"
- id="line1552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.212"
- x2="0.68400002"
- y2="12.212"
- stroke="#000000"
- stroke-width="0.010"
- id="line1554"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.142"
- x2="1.941"
- y2="12.142"
- stroke="#000000"
- stroke-width="0.010"
- id="line1556"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.072"
- x2="0.68400002"
- y2="12.072"
- stroke="#000000"
- stroke-width="0.010"
- id="line1558"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.002"
- x2="1.941"
- y2="12.002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1560"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="11.932"
- x2="0.68400002"
- y2="11.932"
- stroke="#000000"
- stroke-width="0.010"
- id="line1562"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.6090002"
- y="11.995"
- id="rect1564"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.6090002"
- y="11.995"
- id="rect1566"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.5040002"
- y="12.101"
- id="rect1568"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.477,12.724 -5.978,12.724 -5.978,12.837 -6.451,12.837 -6.477,12.724 "
- id="polygon1570"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.477,12.724 -5.978,12.724 -5.978,12.837 -6.451,12.837 -6.477,12.724 "
- id="polygon1572"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.978,12.724 -5.769,12.724 -5.796,12.837 -5.978,12.837 -5.978,12.724 "
- id="polygon1574"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.978,12.724 -5.769,12.724 -5.796,12.837 -5.978,12.837 -5.978,12.724 "
- id="polygon1576"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.9439998"
- y="12.758"
- id="rect1578"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.9439998"
- y="12.758"
- id="rect1580"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.22,12.837 -6.026,12.837 -6.026,12.894 -5.929,12.894 -5.929,12.95 -6.317,12.95 -6.317,12.894 -6.22,12.894 -6.22,12.837 "
- id="polygon1582"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.22,12.837 -6.026,12.837 -6.026,12.894 -5.929,12.894 -5.929,12.95 -6.317,12.95 -6.317,12.894 -6.22,12.894 -6.22,12.837 "
- id="polygon1584"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.653"
- y1="11.13"
- x2="-9.6660004"
- y2="11.13"
- stroke="#000000"
- stroke-width="0.100"
- id="line1586"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.289"
- y1="11.13"
- x2="-1.289"
- y2="10.145"
- stroke="#000000"
- stroke-width="0.100"
- id="line1588"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.8"
- y1="11.13"
- x2="-3.8"
- y2="12.118"
- stroke="#000000"
- stroke-width="0.100"
- id="line1590"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.7739999"
- y1="11.13"
- x2="-3.7739999"
- y2="10.099"
- stroke="#000000"
- stroke-width="0.100"
- id="line1592"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-6.0999999"
- y1="11.13"
- x2="-6.0999999"
- y2="11.993"
- stroke="#000000"
- stroke-width="0.100"
- id="line1594"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-6.0939999"
- y1="11.13"
- x2="-6.0939999"
- y2="10.063"
- stroke="#000000"
- stroke-width="0.100"
- id="line1596"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-8.4139996"
- y1="11.13"
- x2="-8.4139996"
- y2="9.5740004"
- stroke="#000000"
- stroke-width="0.100"
- id="line1598"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.069"
- height="0.80199999"
- x="-4.3639998"
- y="11.941"
- id="rect1600"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.069"
- height="0.80199999"
- x="-4.3639998"
- y="11.941"
- id="rect1602"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.83700001"
- height="0.55199999"
- x="-4.2480001"
- y="12.057"
- id="rect1604"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.219,12.743 -3.669,12.743 -3.669,12.868 -4.19,12.868 -4.219,12.743 "
- id="polygon1606"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.219,12.743 -3.669,12.743 -3.669,12.868 -4.19,12.868 -4.219,12.743 "
- id="polygon1608"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.669,12.743 -3.44,12.743 -3.469,12.868 -3.669,12.868 -3.669,12.743 "
- id="polygon1610"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.669,12.743 -3.44,12.743 -3.469,12.868 -3.669,12.868 -3.669,12.743 "
- id="polygon1612"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.632"
- y="12.78"
- id="rect1614"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.632"
- y="12.78"
- id="rect1616"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.936,12.868 -3.723,12.868 -3.723,12.93 -3.616,12.93 -3.616,12.992 -4.043,12.992 -4.043,12.93 -3.936,12.93 -3.936,12.868 "
- id="polygon1618"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.936,12.868 -3.723,12.868 -3.723,12.93 -3.616,12.93 -3.616,12.992 -4.043,12.992 -4.043,12.93 -3.936,12.93 -3.936,12.868 "
- id="polygon1620"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.579"
- y="9.1079998"
- id="rect1622"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.579"
- y="9.1079998"
- id="rect1624"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.474"
- y="9.2139997"
- id="rect1626"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
- id="polygon1628"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
- id="polygon1630"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
- id="polygon1632"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
- id="polygon1634"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.914"
- y="9.8710003"
- id="rect1636"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.914"
- y="9.8710003"
- id="rect1638"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
- id="polygon1640"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
- id="polygon1642"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.2600002"
- y="9.1450005"
- id="rect1644"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.2600002"
- y="9.1450005"
- id="rect1646"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-4.1550002"
- y="9.25"
- id="rect1648"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
- id="polygon1650"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
- id="polygon1652"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
- id="polygon1654"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
- id="polygon1656"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.595"
- y="9.9069996"
- id="rect1658"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.595"
- y="9.9069996"
- id="rect1660"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
- id="polygon1662"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
- id="polygon1664"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-8.9029999"
- y="9.0410004"
- id="rect1666"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-8.9029999"
- y="9.0410004"
- id="rect1668"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-8.7980003"
- y="9.1470003"
- id="rect1670"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
- id="polygon1672"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
- id="polygon1674"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
- id="polygon1676"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
- id="polygon1678"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-8.2379999"
- y="9.8039999"
- id="rect1680"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-8.2379999"
- y="9.8039999"
- id="rect1682"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
- id="polygon1684"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
- id="polygon1686"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
- id="polygon1688"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
- id="polygon1690"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.871,9.841 L -1.823,9.861 L -0.754,9.861 L -0.706,9.841"
- id="path1692"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -0.754,9.861 L -0.682,9.902"
- id="path1694"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.895,9.902 L -1.823,9.861"
- id="path1696"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
- id="polygon1698"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
- id="polygon1700"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
- id="polygon1702"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
- id="polygon1704"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-1.653"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1706"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1708"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1710"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1712"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1714"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1716"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1718"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1720"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1722"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1724"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1726"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1728"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1730"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1732"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1734"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1736"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1738"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1740"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1742"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1744"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1746"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1748"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1750"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1752"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.289"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1754"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-1.289"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1756"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-0.98500001"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1758"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-0.98500001"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1760"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1762"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1764"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1766"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1768"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1770"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1772"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8780003"
- y1="10.141"
- x2="-10.928"
- y2="10.141"
- stroke="#000000"
- stroke-width="0.010"
- id="line1774"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.928"
- y1="10.403"
- x2="-9.8780003"
- y2="10.403"
- stroke="#000000"
- stroke-width="0.010"
- id="line1776"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8780003"
- y1="10.6"
- x2="-10.928"
- y2="10.6"
- stroke="#000000"
- stroke-width="0.010"
- id="line1778"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1780"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1782"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1784"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-11.059"
- y1="11.519"
- x2="-9.7460003"
- y2="11.519"
- stroke="#000000"
- stroke-width="0.010"
- id="line1786"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1788"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1790"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1792"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1794"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1796"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1798"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1800"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1802"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1804"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1806"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1808"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1810"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.928"
- y1="11.256"
- x2="-10.206"
- y2="11.256"
- stroke="#000000"
- stroke-width="0.010"
- id="line1812"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1814"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1816"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1818"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1820"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1822"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1824"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="11.125"
- x2="-10.271"
- y2="11.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line1826"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.271"
- y1="11.191"
- x2="-10.337"
- y2="11.191"
- stroke="#000000"
- stroke-width="0.010"
- id="line1828"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="11.191"
- x2="-10.796"
- y2="11.191"
- stroke="#000000"
- stroke-width="0.010"
- id="line1830"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1832"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1834"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1836"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="10.797"
- x2="-10.796"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1838"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.731"
- y1="10.797"
- x2="-10.665"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1840"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.074"
- y1="10.797"
- x2="-9.9429998"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1842"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.306"
- x2="-10.993"
- y2="12.306"
- stroke="#000000"
- stroke-width="0.010"
- id="line1844"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="12.241"
- x2="-9.8120003"
- y2="12.241"
- stroke="#000000"
- stroke-width="0.010"
- id="line1846"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.175"
- x2="-10.993"
- y2="12.175"
- stroke="#000000"
- stroke-width="0.010"
- id="line1848"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="12.11"
- x2="-9.8120003"
- y2="12.11"
- stroke="#000000"
- stroke-width="0.010"
- id="line1850"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.044"
- x2="-10.993"
- y2="12.044"
- stroke="#000000"
- stroke-width="0.010"
- id="line1852"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="11.978"
- x2="-9.8120003"
- y2="11.978"
- stroke="#000000"
- stroke-width="0.010"
- id="line1854"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="11.913"
- x2="-10.993"
- y2="11.913"
- stroke="#000000"
- stroke-width="0.010"
- id="line1856"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="-4.0289998"
- y="8.2189999"
- id="text1858"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-4.3639998"
- y="8.8190002"
- id="text1860"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
- <text
- x="-10.628"
- y="13.181"
- id="text1862"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="-10.454"
- y="13.681"
- id="text1864"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-APPS</text>
- <rect
- width="1.4450001"
- height="1.275"
- x="2.5510001"
- y="8.6120005"
- id="rect1866"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="3.273"
- cy="9.8870001"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1868"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1870"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1872"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
- id="path1874"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.0109999"
- y1="9.2469997"
- x2="2.586"
- y2="9.2469997"
- stroke="#000000"
- stroke-width="0.100"
- id="line1876"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="2.983"
- y="9.3260002"
- id="text1878"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.928"
- y="9.7259998"
- id="text1880"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
- id="polyline1882"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="1.317"
- y="15.131"
- id="text1884"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
- <text
- x="1.136"
- y="6.0770001"
- id="text1886"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
- <text
- x="12.943"
- y="6.0310001"
- id="text1888"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
- <text
- x="12.383"
- y="15.277"
- id="text1890"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
- <text
- x="-9.8629999"
- y="15.156"
- id="text1892"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - GNY</text>
- <text
- x="13.189"
- y="0.46399999"
- id="text1894"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
- <text
- x="1.086"
- y="0.53899997"
- id="text1896"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
- <text
- x="12.979"
- y="8.0889997"
- id="text1898"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
- <rect
- width="11.132"
- height="6.5630002"
- x="-11.146"
- y="16.205999"
- id="rect1900"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1902"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1904"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.732"
- height="5.9629998"
- x="-11.446"
- y="16.506001"
- id="rect1906"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1908"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1910"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11.146"
- y1="16.205999"
- x2="-0.014"
- y2="16.205999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1912"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.146"
- y1="22.768999"
- x2="-0.014"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1914"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1916"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1918"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.446"
- y1="16.506001"
- x2="-11.446"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1920"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.28600001"
- y1="16.506001"
- x2="0.28600001"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1922"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1924"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1926"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1928"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1930"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1932"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1934"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1936"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1938"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1940"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1942"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1944"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1946"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1948"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1950"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1952"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1954"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1956"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-5.2220001"
- y="17.145"
- id="text1958"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-5.5609999"
- y="17.745001"
- id="text1960"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
- <text
- x="-10.001"
- y="21.07"
- id="text1962"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="-10.37"
- y="21.57"
- id="text1964"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1966"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1968"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1970"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1972"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1974"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1976"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="19.087"
- x2="-7.6300001"
- y2="19.087"
- stroke="#000000"
- stroke-width="0.010"
- id="line1978"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.6300001"
- y1="19.33"
- x2="-8.6040001"
- y2="19.33"
- stroke="#000000"
- stroke-width="0.010"
- id="line1980"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1982"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1984"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1986"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.665"
- y1="20.181999"
- x2="-7.448"
- y2="20.181999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1988"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1990"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1992"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1994"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect1996"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect1998"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect2000"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2002"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2004"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2006"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2008"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2010"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2012"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4820004"
- y1="19.816999"
- x2="-7.8130002"
- y2="19.816999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2014"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2016"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2018"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2020"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2022"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2024"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2026"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.695"
- x2="-7.8740001"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.010"
- id="line2028"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2030"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2032"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2034"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.8130002"
- y1="19.511999"
- x2="-7.691"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2036"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.242001"
- x2="-7.5089998"
- y2="20.242001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2038"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.302999"
- x2="-8.6040001"
- y2="20.302999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2040"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.364"
- x2="-7.5089998"
- y2="20.364"
- stroke="#000000"
- stroke-width="0.010"
- id="line2042"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.547001"
- x2="-8.6040001"
- y2="20.547001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2044"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.486"
- x2="-7.5089998"
- y2="20.486"
- stroke="#000000"
- stroke-width="0.010"
- id="line2046"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.424999"
- x2="-8.6040001"
- y2="20.424999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2048"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5430002"
- y1="19.511999"
- x2="-8.4820004"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2050"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.511999"
- x2="-8.3599997"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2052"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.756001"
- x2="-8.3599997"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2054"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.9349999"
- y1="19.756001"
- x2="-7.8740001"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2056"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.4980001"
- y1="19.695"
- x2="-2.164"
- y2="19.679001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2058"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9559999"
- y1="19.690001"
- x2="-5.9530001"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.100"
- id="line2060"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9530001"
- y1="19.690001"
- x2="-5.9559999"
- y2="18.690001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2062"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4590001"
- y1="19.686001"
- x2="-4.4559999"
- y2="20.591"
- stroke="#000000"
- stroke-width="0.100"
- id="line2064"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4569998"
- y1="19.686001"
- x2="-4.46"
- y2="18.686001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2066"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.961"
- y1="19.681"
- x2="-2.9579999"
- y2="20.608"
- stroke="#000000"
- stroke-width="0.100"
- id="line2068"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.9619999"
- y1="19.681"
- x2="-2.9649999"
- y2="18.681"
- stroke="#000000"
- stroke-width="0.100"
- id="line2070"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2072"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2074"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8470001"
- y="20.715"
- id="rect2076"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2078"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2080"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2082"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2084"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2086"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2088"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2090"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2092"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2094"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2096"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.329"
- y="20.704"
- id="rect2098"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2100"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2102"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2104"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2106"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2108"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2110"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2112"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2114"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2116"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2118"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-6.2789998"
- y="18.278999"
- id="rect2120"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2122"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2124"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2126"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2128"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2130"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2132"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2134"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2136"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2138"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8039999"
- y="18.278999"
- id="rect2142"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2144"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2146"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2148"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2150"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2152"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2154"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2156"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2158"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2160"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2162"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.3039999"
- y="18.304001"
- id="rect2164"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2166"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2168"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2170"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2172"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2174"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2176"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2178"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2180"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2182"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2184"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
- id="path2186"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -5.503,21.194 L -5.431,21.234"
- id="path2188"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.631,21.234 L -6.559,21.194"
- id="path2190"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2192"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2194"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2196"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2198"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2200"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2202"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2204"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2206"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2208"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2210"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2212"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2214"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2216"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2218"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2220"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2222"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2224"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2226"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2228"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2230"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2232"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2234"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2236"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2238"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2240"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2242"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2244"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2246"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2248"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2250"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2252"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2254"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.17"
- height="1.033"
- x="-10.59"
- y="19.132"
- id="rect2256"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="-10.004"
- cy="20.165001"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2258"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.004"
- cy="19.132"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2260"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.004"
- cy="19.132"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2262"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -9.419,19.132 L -9.419,20.165 C -9.419,20.26 -9.681,20.337 -10.004,20.337 C -10.328,20.337 -10.59,20.26 -10.59,20.165 L -10.59,19.132"
- id="path2264"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-9.3959999"
- y1="19.684"
- x2="-8.665"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.100"
- id="line2266"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-10.303"
- y="19.759001"
- id="text2268"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="-10.288"
- y="20.159"
- id="text2270"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="-0.91500002"
- y="19.843"
- id="text2272"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="-1.867"
- y="22.455999"
- id="text2274"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
- <text
- x="-10.478"
- y="17.114"
- id="text2276"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="-10.081"
- y="17.914"
- id="text2278"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg2</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.554,15.161 -1.554,15.906 -1.821,15.906 -1.821,19.285 "
- id="polyline2280"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2282"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2284"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2286"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2288"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2290"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2292"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2294"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2296"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2298"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2300"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2302"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2304"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2306"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2308"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2310"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="7.8559999"
- y="17.167"
- id="text2312"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="7.5180001"
- y="17.767"
- id="text2314"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
- <text
- x="3.204"
- y="18.118"
- id="text2316"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="2.835"
- y="18.618"
- id="text2318"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
- <text
- x="12.542"
- y="19.694"
- id="text2320"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="12.687"
- y="20.194"
- id="text2322"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-APPS</text>
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2324"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2326"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2328"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2330"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2332"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2334"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="19.246"
- x2="5.112"
- y2="19.246"
- stroke="#000000"
- stroke-width="0.010"
- id="line2336"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.112"
- y1="19.49"
- x2="4.138"
- y2="19.49"
- stroke="#000000"
- stroke-width="0.010"
- id="line2338"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2340"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2342"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2344"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.0770001"
- y1="20.341"
- x2="5.2940001"
- y2="20.341"
- stroke="#000000"
- stroke-width="0.010"
- id="line2346"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2348"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2350"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2352"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2354"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2356"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2358"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2360"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2362"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2364"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2366"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2368"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2370"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.2600002"
- y1="19.976"
- x2="4.9289999"
- y2="19.976"
- stroke="#000000"
- stroke-width="0.010"
- id="line2372"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2374"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2376"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2378"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2380"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2382"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2384"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.855"
- x2="4.868"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.010"
- id="line2386"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2388"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2390"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2392"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.9289999"
- y1="19.672001"
- x2="5.0510001"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2394"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.402"
- x2="5.2329998"
- y2="20.402"
- stroke="#000000"
- stroke-width="0.010"
- id="line2396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.462999"
- x2="4.138"
- y2="20.462999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.524"
- x2="5.2329998"
- y2="20.524"
- stroke="#000000"
- stroke-width="0.010"
- id="line2400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.705999"
- x2="4.138"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.645"
- x2="5.2329998"
- y2="20.645"
- stroke="#000000"
- stroke-width="0.010"
- id="line2404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.584999"
- x2="4.138"
- y2="20.584999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.1989999"
- y1="19.672001"
- x2="4.2600002"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2408"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.672001"
- x2="4.382"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2410"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.915001"
- x2="4.382"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2412"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.8070002"
- y1="19.915001"
- x2="4.868"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2414"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.244"
- y1="19.855"
- x2="10.386"
- y2="19.841999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2416"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7309999"
- y1="19.851"
- x2="6.7329998"
- y2="20.809999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2418"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7350001"
- y1="19.851"
- x2="6.7319999"
- y2="18.851"
- stroke="#000000"
- stroke-width="0.100"
- id="line2420"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1739998"
- y1="19.847"
- x2="8.1759996"
- y2="20.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line2422"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1750002"
- y1="19.847"
- x2="8.1730003"
- y2="18.848"
- stroke="#000000"
- stroke-width="0.100"
- id="line2424"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6169996"
- y1="19.844"
- x2="9.6190004"
- y2="20.771"
- stroke="#000000"
- stroke-width="0.100"
- id="line2426"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6160002"
- y1="19.844"
- x2="9.6129999"
- y2="18.844"
- stroke="#000000"
- stroke-width="0.100"
- id="line2428"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2430"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2432"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8210001"
- y="20.875"
- id="rect2434"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2436"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2438"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2440"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2442"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2444"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2446"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2448"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2450"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2452"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2454"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2629995"
- y="20.864"
- id="rect2456"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2458"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2460"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2462"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2464"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2466"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2468"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2470"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2472"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2474"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2476"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.388"
- y="18.438999"
- id="rect2478"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2480"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2482"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2484"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2486"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2488"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2490"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2492"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2494"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2496"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2498"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8379998"
- y="18.464001"
- id="rect2500"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2502"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2504"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2506"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2508"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2510"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2512"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2514"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2516"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2518"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2520"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2880001"
- y="18.438999"
- id="rect2522"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2524"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2526"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2528"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2530"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2532"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2534"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2536"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2538"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2540"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2542"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
- id="path2544"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.239,21.354 L 7.311,21.394"
- id="path2546"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.111,21.394 L 6.183,21.354"
- id="path2548"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2550"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2552"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2554"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2556"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2558"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2560"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2562"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2564"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2566"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2568"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2570"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2572"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2574"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2576"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2578"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2580"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2582"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2584"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2586"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2588"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2590"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2592"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2594"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2596"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2598"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2600"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2602"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2604"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2606"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2608"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2610"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2612"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2614"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2616"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2618"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2620"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2622"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2624"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.048"
- x2="10.618"
- y2="19.048"
- stroke="#000000"
- stroke-width="0.010"
- id="line2626"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="19.275999"
- x2="11.533"
- y2="19.275999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2628"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.448"
- x2="10.618"
- y2="19.448"
- stroke="#000000"
- stroke-width="0.010"
- id="line2630"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2632"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2634"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2636"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.504"
- y1="20.249001"
- x2="11.647"
- y2="20.249001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2638"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2640"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2642"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2644"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2646"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2648"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2650"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2652"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2654"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2656"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2658"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2660"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2662"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="20.02"
- x2="11.247"
- y2="20.02"
- stroke="#000000"
- stroke-width="0.010"
- id="line2664"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2666"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2668"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2670"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2672"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2674"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2676"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.906"
- x2="11.19"
- y2="19.906"
- stroke="#000000"
- stroke-width="0.010"
- id="line2678"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.19"
- y1="19.962999"
- x2="11.133"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2680"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.962999"
- x2="10.732"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2682"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2684"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2686"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2688"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.620001"
- x2="10.732"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.79"
- y1="19.620001"
- x2="10.847"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.362"
- y1="19.620001"
- x2="11.476"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.934999"
- x2="10.561"
- y2="20.934999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.878"
- x2="11.59"
- y2="20.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line2698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.820999"
- x2="10.561"
- y2="20.820999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.763"
- x2="11.59"
- y2="20.763"
- stroke="#000000"
- stroke-width="0.010"
- id="line2702"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.705999"
- x2="10.561"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2704"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.649"
- x2="11.59"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.010"
- id="line2706"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.591999"
- x2="10.561"
- y2="20.591999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2708"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.4960001"
- y1="19.819"
- x2="4.0770001"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.100"
- id="line2710"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.183"
- height="1.044"
- x="2.302"
- y="19.268999"
- id="rect2712"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="2.8940001"
- cy="20.312"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2714"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2716"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2718"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
- id="path2720"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="2.589"
- y="19.868999"
- id="text2722"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.6040001"
- y="20.268999"
- id="text2724"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="12.947"
- y="22.452"
- id="text2726"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
- <text
- x="12.072"
- y="17.239"
- id="text2728"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="12.468"
- y="18.039"
- id="text2730"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg3</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
- id="polyline2732"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.1"
- y1="22.393"
- x2="15.55"
- y2="23.143"
- stroke="#F7F7F7"
- stroke-width="0.100"
- id="line2734"
- style="stroke:#f7f7f7;stroke-width:0.1" />
- <text
- x="-10.033"
- y="7.8769999"
- id="text2736"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="-10.108"
- y="22.502001"
- id="text2738"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="2.5420001"
- y="22.502001"
- id="text2740"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="7.355"
- y="0.40200001"
- id="text2742"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: UKNET</text>
- <text
- x="18.438999"
- y="0.40200001"
- id="text2744"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: WESTNET</text>
- <text
- x="18.017"
- y="15.202"
- id="text2746"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="-10.507"
- y="0.49399999"
- id="text2748"
- style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Notes:</text>
- <text
- x="-11.175"
- y="1.294"
- id="text2750"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">The decision was made to implement separate</text>
- <text
- x="-11.175"
- y="1.794"
- id="text2752"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">domains for the West Coast and for UK</text>
- <text
- x="-11.175"
- y="2.2939999"
- id="text2754"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">operations. Wide-area traffic will be reduced.</text>
- <text
- x="-11.175"
- y="3.2939999"
- id="text2756"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">This design introduces the concept of deploying</text>
- <text
- x="-11.175"
- y="3.7939999"
- id="text2758"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">interdomain trusts, thus permitting much needed</text>
- <text
- x="-11.175"
- y="4.2940001"
- id="text2760"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">network integration and interoperabilty.</text>
- <text
- x="-11.175"
- y="5.2940001"
- id="text2762"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">There is a single LDAP Master and at least one</text>
- <text
- x="-11.175"
- y="5.7940001"
- id="text2764"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave LDAP server in each remote office.</text>
- <text
- x="-11.175"
- y="6.2940001"
- id="text2766"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="34.602001cm"
- height="23.67cm"
- viewBox="-11.55 -0.456 23.052 23.213"
- id="svg2">
- <defs
- id="defs2765" />
- <rect
- width="13.8"
- height="6.513"
- x="1.375"
- y="16.256001"
- id="rect4"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path6"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path8"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="14.4"
- height="5.9130001"
- x="1.075"
- y="16.556"
- id="rect10"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path12"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path14"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="1.375"
- y1="16.256001"
- x2="15.175"
- y2="16.256001"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.375"
- y1="22.768999"
- x2="15.175"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.375,16.256 C 1.2093146,16.256 1.075,16.390315 1.075,16.556"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.475,16.556 C 15.475,16.390315 15.340685,16.256 15.175,16.256"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.075"
- y1="16.556"
- x2="1.075"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line24"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="15.475"
- y1="16.556"
- x2="15.475"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line26"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 1.075,22.469 C 1.075,22.634685 1.2093146,22.769 1.375,22.769"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 15.175,22.769 C 15.340685,22.769 15.475,22.634685 15.475,22.469"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.617"
- height="6.8530002"
- x="0.495"
- y="-0.40599999"
- id="rect32"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path34"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path36"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.217"
- height="6.2529998"
- x="0.19499999"
- y="-0.106"
- id="rect38"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path40"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path42"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="0.495"
- y1="-0.40599999"
- x2="11.112"
- y2="-0.40599999"
- stroke="#000000"
- stroke-width="0.050"
- id="line44"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.495"
- y1="6.447"
- x2="11.112"
- y2="6.447"
- stroke="#000000"
- stroke-width="0.050"
- id="line46"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.495,-0.406 C 0.32931458,-0.406 0.195,-0.27168542 0.195,-0.106"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.412,-0.106 C 11.412,-0.27168542 11.277685,-0.406 11.112,-0.406"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.19499999"
- y1="-0.106"
- x2="0.19499999"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line52"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.412"
- y1="-0.106"
- x2="11.412"
- y2="6.1469998"
- stroke="#000000"
- stroke-width="0.050"
- id="line54"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.195,6.147 C 0.195,6.3126854 0.32931458,6.447 0.495,6.447"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.112,6.447 C 11.277685,6.447 11.412,6.3126854 11.412,6.147"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.337"
- height="6.8600001"
- x="12.35"
- y="-0.43099999"
- id="rect60"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path62"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path64"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="10.937"
- height="6.2600002"
- x="12.05"
- y="-0.131"
- id="rect66"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path68"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path70"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="12.35"
- y1="-0.43099999"
- x2="22.687"
- y2="-0.43099999"
- stroke="#000000"
- stroke-width="0.050"
- id="line72"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.35"
- y1="6.4289999"
- x2="22.687"
- y2="6.4289999"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.35,-0.431 C 12.184315,-0.431 12.05,-0.29668542 12.05,-0.131"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.987,-0.131 C 22.987,-0.29668542 22.852685,-0.431 22.687,-0.431"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.05"
- y1="-0.131"
- x2="12.05"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line80"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="22.987"
- y1="-0.131"
- x2="22.987"
- y2="6.1290002"
- stroke="#000000"
- stroke-width="0.050"
- id="line82"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 12.05,6.129 C 12.05,6.2946854 12.184315,6.429 12.35,6.429"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.687,6.429 C 22.852685,6.429 22.987,6.2946854 22.987,6.129"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="10.821"
- height="8.375"
- x="11.905"
- y="7.244"
- id="rect88"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path90"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path92"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.421"
- height="7.7750001"
- x="11.605"
- y="7.5440001"
- id="rect94"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path96"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path98"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="11.905"
- y1="7.244"
- x2="22.726999"
- y2="7.244"
- stroke="#000000"
- stroke-width="0.050"
- id="line100"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.905"
- y1="15.619"
- x2="22.726999"
- y2="15.619"
- stroke="#000000"
- stroke-width="0.050"
- id="line102"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.905,7.244 C 11.739315,7.244 11.605,7.3783146 11.605,7.544"
- id="path104"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 23.027,7.544 C 23.027,7.3783146 22.892685,7.244 22.727,7.244"
- id="path106"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="11.605"
- y1="7.5440001"
- x2="11.605"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line108"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="23.027"
- y1="7.5440001"
- x2="23.027"
- y2="15.319"
- stroke="#000000"
- stroke-width="0.050"
- id="line110"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M 11.605,15.319 C 11.605,15.484685 11.739315,15.619 11.905,15.619"
- id="path112"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 22.727,15.619 C 22.892685,15.619 23.027,15.484685 23.027,15.319"
- id="path114"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="15.1"
- height="8.3719997"
- x="-11.225"
- y="7.1339998"
- id="rect116"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
- id="path118"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
- id="path120"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="15.7"
- height="7.7719998"
- x="-11.525"
- y="7.434"
- id="rect122"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
- id="path124"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
- id="path126"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11.225"
- y1="7.1339998"
- x2="3.875"
- y2="7.1339998"
- stroke="#000000"
- stroke-width="0.050"
- id="line128"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.225"
- y1="15.506"
- x2="3.875"
- y2="15.506"
- stroke="#000000"
- stroke-width="0.050"
- id="line130"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.225,7.134 C -11.390685,7.134 -11.525,7.2683146 -11.525,7.434"
- id="path132"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 4.175,7.434 C 4.175,7.2683146 4.0406854,7.134 3.875,7.134"
- id="path134"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.525"
- y1="7.434"
- x2="-11.525"
- y2="15.206"
- stroke="#000000"
- stroke-width="0.050"
- id="line136"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="4.1750002"
- y1="7.434"
- x2="4.1750002"
- y2="15.206"
- stroke="#000000"
- stroke-width="0.050"
- id="line138"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.525,15.206 C -11.525,15.371685 -11.390685,15.506 -11.225,15.506"
- id="path140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 3.875,15.506 C 4.0406854,15.506 4.175,15.371685 4.175,15.206"
- id="path142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="1.95"
- y1="11.168"
- x2="4.8109999"
- y2="11.165"
- stroke="#000000"
- stroke-width="0.300"
- id="line144"
- style="stroke:#000000;stroke-width:0.30000001" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.145,2.624 4.145,6.819 5.675,6.819 5.675,9.944 "
- id="polyline146"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="16.100,2.794 16.100,6.844 8.674,6.844 8.674,9.887 "
- id="polyline148"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect150"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.98000002"
- height="0.98000002"
- x="-1.818"
- y="14.136"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
- id="path156"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.267,14.295 C -1.267,14.785 -1.169,14.687 -1.659,14.687"
- id="path158"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
- id="polygon160"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.22,14.371 -1.269,14.273 -1.318,14.371 -1.22,14.371 "
- id="polygon162"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
- id="polygon164"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.583,14.636 -1.681,14.685 -1.583,14.734 -1.583,14.636 "
- id="polygon166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
- id="path168"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -0.976,14.571 C -1.466,14.571 -1.368,14.473 -1.368,14.963"
- id="path170"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
- id="polygon172"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.063,14.616 -0.965,14.567 -1.063,14.518 -1.063,14.616 "
- id="polygon174"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
- id="polygon176"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.426,14.881 -1.377,14.979 -1.328,14.881 -1.426,14.881 "
- id="polygon178"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.306"
- y1="11.165"
- x2="-1.3279999"
- y2="14.136"
- stroke="#000000"
- stroke-width="0.100"
- id="line180"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.71700001"
- y="7.6999998"
- id="text182"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="0.37799999"
- y="8.1999998"
- id="text184"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-PDC</text>
- <line
- x1="6.118"
- y1="13.16"
- x2="7.7179999"
- y2="13.135"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.10,0.10"
- id="line186"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <text
- x="8.4429998"
- y="13.325"
- id="text188"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">= VPN</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="10.645,11.075 10.645,9.069 16.025,9.069 16.025,11.368 "
- id="polyline190"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-3.0239999"
- y="14.751"
- id="text192"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="4.1469998"
- y="17.031"
- id="text194"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect196"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="2.553"
- y="1.723"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect202"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect204"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="2.6140001"
- y="1.784"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="2.027"
- x2="3.5869999"
- y2="2.027"
- stroke="#000000"
- stroke-width="0.010"
- id="line208"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.5869999"
- y1="2.2709999"
- x2="2.6140001"
- y2="2.2709999"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect212"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect214"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="2.7360001"
- y="2.575"
- id="rect216"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.553"
- y1="3.122"
- x2="3.77"
- y2="3.122"
- stroke="#000000"
- stroke-width="0.010"
- id="line218"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect220"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect222"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.405"
- y="3.0009999"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect226"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect228"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.527"
- y="3.0009999"
- id="rect230"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect232"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect234"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="3.648"
- y="3.0009999"
- id="rect236"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect238"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect240"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="3.5869999"
- y="2.8180001"
- id="rect242"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7360001"
- y1="2.757"
- x2="3.405"
- y2="2.757"
- stroke="#000000"
- stroke-width="0.010"
- id="line244"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect246"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect248"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="3.527"
- y="2.575"
- id="rect250"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect252"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect254"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="2.675"
- y="2.332"
- id="rect256"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.6359999"
- x2="3.3440001"
- y2="2.6359999"
- stroke="#000000"
- stroke-width="0.010"
- id="line258"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect260"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect262"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="2.918"
- y="2.6359999"
- id="rect264"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.405"
- y1="2.4530001"
- x2="3.527"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line266"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.1830001"
- x2="3.7090001"
- y2="3.1830001"
- stroke="#000000"
- stroke-width="0.010"
- id="line268"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.244"
- x2="2.6140001"
- y2="3.244"
- stroke="#000000"
- stroke-width="0.010"
- id="line270"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.3050001"
- x2="3.7090001"
- y2="3.3050001"
- stroke="#000000"
- stroke-width="0.010"
- id="line272"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.487"
- x2="2.6140001"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line274"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.6140001"
- y1="3.427"
- x2="3.7090001"
- y2="3.427"
- stroke="#000000"
- stroke-width="0.010"
- id="line276"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.7090001"
- y1="3.3659999"
- x2="2.6140001"
- y2="3.3659999"
- stroke="#000000"
- stroke-width="0.010"
- id="line278"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.675"
- y1="2.4530001"
- x2="2.7360001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line280"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.4530001"
- x2="2.8570001"
- y2="2.4530001"
- stroke="#000000"
- stroke-width="0.010"
- id="line282"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7969999"
- y1="2.697"
- x2="2.8570001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line284"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.283"
- y1="2.697"
- x2="3.3440001"
- y2="2.697"
- stroke="#000000"
- stroke-width="0.010"
- id="line286"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.72"
- y1="2.6359999"
- x2="8.8620005"
- y2="2.6229999"
- stroke="#000000"
- stroke-width="0.100"
- id="line288"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.2069998"
- y1="2.632"
- x2="5.2090001"
- y2="3.5910001"
- stroke="#000000"
- stroke-width="0.100"
- id="line290"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="5.21"
- y1="2.632"
- x2="5.2080002"
- y2="1.632"
- stroke="#000000"
- stroke-width="0.100"
- id="line292"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.6500001"
- y1="2.6289999"
- x2="6.652"
- y2="3.5339999"
- stroke="#000000"
- stroke-width="0.100"
- id="line294"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.651"
- y1="2.6289999"
- x2="6.6479998"
- y2="1.6289999"
- stroke="#000000"
- stroke-width="0.100"
- id="line296"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.092"
- y1="2.625"
- x2="8.0950003"
- y2="3.552"
- stroke="#000000"
- stroke-width="0.100"
- id="line298"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.0909996"
- y1="2.625"
- x2="8.0889997"
- y2="1.625"
- stroke="#000000"
- stroke-width="0.100"
- id="line300"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect302"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.1989999"
- y="3.559"
- id="rect304"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.296"
- y="3.6559999"
- id="rect306"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon308"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.321,4.231 6.782,4.231 6.782,4.335 6.345,4.335 6.321,4.231 "
- id="polygon310"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon312"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.782,4.231 6.974,4.231 6.949,4.335 6.782,4.335 6.782,4.231 "
- id="polygon314"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect316"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8130002"
- y="4.2620001"
- id="rect318"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon320"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.558,4.335 6.737,4.335 6.737,4.388 6.826,4.388 6.826,4.44 6.468,4.44 6.468,4.388 6.558,4.388 6.558,4.335 "
- id="polygon322"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect324"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6420002"
- y="3.5480001"
- id="rect326"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7389998"
- y="3.645"
- id="rect328"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon330"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.763,4.22 8.224,4.22 8.224,4.325 7.787,4.325 7.763,4.22 "
- id="polygon332"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon334"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.224,4.22 8.416,4.22 8.392,4.325 8.224,4.325 8.224,4.22 "
- id="polygon336"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect338"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2550001"
- y="4.2509999"
- id="rect340"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon342"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8,4.325 8.179,4.325 8.179,4.377 8.269,4.377 8.269,4.429 7.91,4.429 7.91,4.377 8,4.377 8,4.325 "
- id="polygon344"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect346"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="4.7670002"
- y="1.123"
- id="rect348"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="4.8639998"
- y="1.22"
- id="rect350"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon352"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="4.888,1.795 5.349,1.795 5.349,1.9 4.912,1.9 4.888,1.795 "
- id="polygon354"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon356"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.349,1.795 5.541,1.795 5.517,1.9 5.349,1.9 5.349,1.795 "
- id="polygon358"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect360"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="5.3800001"
- y="1.826"
- id="rect362"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon364"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="5.125,1.9 5.304,1.9 5.304,1.952 5.394,1.952 5.394,2.004 5.035,2.004 5.035,1.952 5.125,1.952 5.125,1.9 "
- id="polygon366"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect368"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.217"
- y="1.148"
- id="rect370"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.3140001"
- y="1.245"
- id="rect372"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon374"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.338,1.82 6.799,1.82 6.799,1.925 6.362,1.925 6.338,1.82 "
- id="polygon376"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon378"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.799,1.82 6.991,1.82 6.967,1.925 6.799,1.925 6.799,1.82 "
- id="polygon380"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect382"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.8299999"
- y="1.851"
- id="rect384"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon386"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.575,1.925 6.754,1.925 6.754,1.977 6.844,1.977 6.844,2.029 6.485,2.029 6.485,1.977 6.575,1.977 6.575,1.925 "
- id="polygon388"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect390"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.6669998"
- y="1.123"
- id="rect392"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.7639999"
- y="1.22"
- id="rect394"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon396"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.788,1.795 8.249,1.795 8.249,1.9 7.812,1.9 7.788,1.795 "
- id="polygon398"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon400"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.249,1.795 8.441,1.795 8.417,1.9 8.249,1.9 8.249,1.795 "
- id="polygon402"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect404"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.2799997"
- y="1.826"
- id="rect406"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon408"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.025,1.9 8.204,1.9 8.204,1.952 8.294,1.952 8.294,2.004 7.935,2.004 7.935,1.952 8.025,1.952 8.025,1.9 "
- id="polygon410"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon412"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.779,3.795 4.731,3.815 4.587,4.175 4.587,4.355 4.659,4.415 5.715,4.415 5.787,4.355 5.787,4.175 5.643,3.815 5.595,3.795 4.779,3.795 "
- id="polygon414"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.611,4.115 L 4.659,4.135 L 5.715,4.135 L 5.763,4.115"
- id="path416"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 5.715,4.135 L 5.787,4.175"
- id="path418"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 4.587,4.175 L 4.659,4.135"
- id="path420"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon422"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.923,3.415 4.899,3.895 5.475,3.895 5.451,3.415 4.923,3.415 "
- id="polygon424"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon426"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="4.827,3.895 4.779,4.035 5.595,4.035 5.547,3.895 4.827,3.895 "
- id="polygon428"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse430"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse432"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse434"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse436"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse438"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2049999"
- rx="0.012"
- ry="0.012"
- id="ellipse440"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse442"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse444"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse446"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse448"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse450"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.2550001"
- rx="0.012"
- ry="0.012"
- id="ellipse452"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse454"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse456"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse458"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse460"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse462"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.3049998"
- rx="0.012"
- ry="0.012"
- id="ellipse464"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse466"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.8270001"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse468"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse470"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="4.947"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse472"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse474"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="5.0669999"
- cy="4.355"
- rx="0.012"
- ry="0.012"
- id="ellipse476"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse478"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.1869998"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse480"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse482"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="5.487"
- cy="4.2150002"
- rx="0.15000001"
- ry="0.048"
- id="ellipse484"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect486"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect488"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="8.9790001"
- y="1.4859999"
- id="rect490"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect492"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect494"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="9.0939999"
- y="1.6"
- id="rect496"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="1.829"
- x2="9.0939999"
- y2="1.829"
- stroke="#000000"
- stroke-width="0.010"
- id="line498"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.0580001"
- x2="10.009"
- y2="2.0580001"
- stroke="#000000"
- stroke-width="0.010"
- id="line500"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.009"
- y1="2.2290001"
- x2="9.0939999"
- y2="2.2290001"
- stroke="#000000"
- stroke-width="0.010"
- id="line502"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect504"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect506"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="9.0939999"
- y="2.6289999"
- id="rect508"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.9790001"
- y1="3.03"
- x2="10.123"
- y2="3.03"
- stroke="#000000"
- stroke-width="0.010"
- id="line510"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect512"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect514"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.4940004"
- y="3.1440001"
- id="rect516"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect518"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect520"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.7229996"
- y="3.1440001"
- id="rect522"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect524"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect526"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="9.9519997"
- y="3.1440001"
- id="rect528"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect530"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect532"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="9.8950005"
- y="2.8010001"
- id="rect534"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0939999"
- y1="2.8010001"
- x2="9.7229996"
- y2="2.8010001"
- stroke="#000000"
- stroke-width="0.010"
- id="line536"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect538"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect540"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="9.0939999"
- y="3.0869999"
- id="rect542"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect544"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect546"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="9.151"
- y="2.286"
- id="rect548"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.687"
- x2="9.6660004"
- y2="2.687"
- stroke="#000000"
- stroke-width="0.010"
- id="line550"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.6660004"
- y1="2.744"
- x2="9.6090002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.744"
- x2="9.2080002"
- y2="2.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line554"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect556"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect558"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="9.2650003"
- y="2.687"
- id="rect560"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.151"
- y1="2.401"
- x2="9.2080002"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line562"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.2650003"
- y1="2.401"
- x2="9.323"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line564"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.8369999"
- y1="2.401"
- x2="9.9519997"
- y2="2.401"
- stroke="#000000"
- stroke-width="0.010"
- id="line566"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.7160001"
- x2="9.0369997"
- y2="3.7160001"
- stroke="#000000"
- stroke-width="0.010"
- id="line568"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.6589999"
- x2="10.066"
- y2="3.6589999"
- stroke="#000000"
- stroke-width="0.010"
- id="line570"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.602"
- x2="9.0369997"
- y2="3.602"
- stroke="#000000"
- stroke-width="0.010"
- id="line572"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.5439999"
- x2="10.066"
- y2="3.5439999"
- stroke="#000000"
- stroke-width="0.010"
- id="line574"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.487"
- x2="9.0369997"
- y2="3.487"
- stroke="#000000"
- stroke-width="0.010"
- id="line576"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.0369997"
- y1="3.4300001"
- x2="10.066"
- y2="3.4300001"
- stroke="#000000"
- stroke-width="0.010"
- id="line578"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.066"
- y1="3.3729999"
- x2="9.0369997"
- y2="3.3729999"
- stroke="#000000"
- stroke-width="0.010"
- id="line580"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="5.9629998"
- y="5.2589998"
- id="text582"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="5.5580001"
- y="5.8590002"
- id="text584"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.12.0/22</text>
- <text
- x="1.234"
- y="4.1529999"
- id="text586"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="1.053"
- y="4.6529999"
- id="text588"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-BDC</text>
- <text
- x="9.3100004"
- y="0.375"
- id="text590"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="9.1300001"
- y="0.875"
- id="text592"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LON-PDC</text>
- <rect
- width="1.291"
- height="1.1390001"
- x="0.61699998"
- y="2.0880001"
- id="rect594"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="1.263"
- cy="3.227"
- rx="0.64499998"
- ry="0.19"
- id="ellipse596"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse598"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="1.263"
- cy="2.0880001"
- rx="0.64499998"
- ry="0.19"
- id="ellipse600"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 1.908,2.088 L 1.908,3.227 C 1.908,3.332 1.619,3.417 1.263,3.417 C 0.906,3.417 0.617,3.332 0.617,3.227 L 0.617,2.088"
- id="path602"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="1.928"
- y1="2.523"
- x2="2.503"
- y2="2.523"
- stroke="#000000"
- stroke-width="0.100"
- id="line604"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.935"
- y="2.7219999"
- id="text606"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="0.94999999"
- y="3.122"
- id="text608"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect610"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect612"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.397"
- y="1.885"
- id="rect614"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect616"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect618"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.458"
- y="1.946"
- id="rect620"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="2.1900001"
- x2="15.431"
- y2="2.1900001"
- stroke="#000000"
- stroke-width="0.010"
- id="line622"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="2.4330001"
- x2="14.458"
- y2="2.4330001"
- stroke="#000000"
- stroke-width="0.010"
- id="line624"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect626"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect628"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.58"
- y="2.737"
- id="rect630"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="3.2850001"
- x2="15.614"
- y2="3.2850001"
- stroke="#000000"
- stroke-width="0.010"
- id="line632"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect634"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect636"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="3.1630001"
- id="rect638"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect640"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect642"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.371"
- y="3.1630001"
- id="rect644"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect646"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect648"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.492"
- y="3.1630001"
- id="rect650"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect652"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect654"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.431"
- y="2.98"
- id="rect656"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.58"
- y1="2.9200001"
- x2="15.249"
- y2="2.9200001"
- stroke="#000000"
- stroke-width="0.010"
- id="line658"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect660"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect662"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.183"
- x="15.371"
- y="2.737"
- id="rect664"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect666"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect668"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.519"
- y="2.494"
- id="rect670"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.7980001"
- x2="15.188"
- y2="2.7980001"
- stroke="#000000"
- stroke-width="0.010"
- id="line672"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect674"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect676"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.762"
- y="2.7980001"
- id="rect678"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.249"
- y1="2.615"
- x2="15.371"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line680"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.345"
- x2="15.553"
- y2="3.345"
- stroke="#000000"
- stroke-width="0.010"
- id="line682"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.4059999"
- x2="14.458"
- y2="3.4059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line684"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.467"
- x2="15.553"
- y2="3.467"
- stroke="#000000"
- stroke-width="0.010"
- id="line686"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.6500001"
- x2="14.458"
- y2="3.6500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line688"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="3.589"
- x2="15.553"
- y2="3.589"
- stroke="#000000"
- stroke-width="0.010"
- id="line690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.553"
- y1="3.5280001"
- x2="14.458"
- y2="3.5280001"
- stroke="#000000"
- stroke-width="0.010"
- id="line692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="2.615"
- x2="14.58"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.615"
- x2="14.701"
- y2="2.615"
- stroke="#000000"
- stroke-width="0.010"
- id="line696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.641"
- y1="2.859"
- x2="14.701"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="2.859"
- x2="15.188"
- y2="2.859"
- stroke="#000000"
- stroke-width="0.010"
- id="line700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.564"
- y1="2.7980001"
- x2="20.705"
- y2="2.7850001"
- stroke="#000000"
- stroke-width="0.100"
- id="line702"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.051001"
- y1="2.7939999"
- x2="17.052999"
- y2="3.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line704"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="17.054001"
- y1="2.7939999"
- x2="17.052"
- y2="1.794"
- stroke="#000000"
- stroke-width="0.100"
- id="line706"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.493"
- y1="2.7909999"
- x2="18.496"
- y2="3.6960001"
- stroke="#000000"
- stroke-width="0.100"
- id="line708"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.495001"
- y1="2.7909999"
- x2="18.492001"
- y2="1.791"
- stroke="#000000"
- stroke-width="0.100"
- id="line710"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.936001"
- y1="2.7869999"
- x2="19.938999"
- y2="3.714"
- stroke="#000000"
- stroke-width="0.100"
- id="line712"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.934999"
- y1="2.7869999"
- x2="19.933001"
- y2="1.7869999"
- stroke="#000000"
- stroke-width="0.100"
- id="line714"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect716"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.042999"
- y="3.721"
- id="rect718"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.139999"
- y="3.8180001"
- id="rect720"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon722"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.165,4.393 18.625,4.393 18.625,4.498 18.189,4.498 18.165,4.393 "
- id="polygon724"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon726"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.625,4.393 18.818,4.393 18.793,4.498 18.625,4.498 18.625,4.393 "
- id="polygon728"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect730"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.657"
- y="4.4239998"
- id="rect732"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon734"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.402,4.498 18.581,4.498 18.581,4.55 18.67,4.55 18.67,4.602 18.312,4.602 18.312,4.55 18.402,4.55 18.402,4.498 "
- id="polygon736"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect738"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.486"
- y="3.71"
- id="rect740"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.583"
- y="3.8069999"
- id="rect742"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon744"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.607,4.382 20.068,4.382 20.068,4.487 19.631,4.487 19.607,4.382 "
- id="polygon746"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon748"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.068,4.382 20.26,4.382 20.236,4.487 20.068,4.487 20.068,4.382 "
- id="polygon750"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect752"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.099001"
- y="4.414"
- id="rect754"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon756"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.844,4.487 20.023,4.487 20.023,4.539 20.113,4.539 20.113,4.591 19.754,4.591 19.754,4.539 19.844,4.539 19.844,4.487 "
- id="polygon758"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect760"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.611"
- y="1.285"
- id="rect762"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.708"
- y="1.382"
- id="rect764"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon766"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.732,1.957 17.193,1.957 17.193,2.062 16.756,2.062 16.732,1.957 "
- id="polygon768"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon770"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.193,1.957 17.385,1.957 17.361,2.062 17.193,2.062 17.193,1.957 "
- id="polygon772"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect774"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.224001"
- y="1.989"
- id="rect776"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon778"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.969,2.062 17.148,2.062 17.148,2.114 17.238,2.114 17.238,2.166 16.879,2.166 16.879,2.114 16.969,2.114 16.969,2.062 "
- id="polygon780"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect782"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="18.061001"
- y="1.3099999"
- id="rect784"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.158001"
- y="1.4069999"
- id="rect786"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon788"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.182,1.982 18.643,1.982 18.643,2.087 18.206,2.087 18.182,1.982 "
- id="polygon790"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon792"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.643,1.982 18.835,1.982 18.811,2.087 18.643,2.087 18.643,1.982 "
- id="polygon794"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect796"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.674"
- y="2.0139999"
- id="rect798"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon800"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.419,2.087 18.598,2.087 18.598,2.139 18.688,2.139 18.688,2.191 18.329,2.191 18.329,2.139 18.419,2.139 18.419,2.087 "
- id="polygon802"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect804"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.511"
- y="1.285"
- id="rect806"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.608"
- y="1.382"
- id="rect808"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon810"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.632,1.957 20.093,1.957 20.093,2.062 19.656,2.062 19.632,1.957 "
- id="polygon812"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon814"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="20.093,1.957 20.285,1.957 20.261,2.062 20.093,2.062 20.093,1.957 "
- id="polygon816"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect818"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.124001"
- y="1.989"
- id="rect820"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon822"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.869,2.062 20.048,2.062 20.048,2.114 20.138,2.114 20.138,2.166 19.779,2.166 19.779,2.114 19.869,2.114 19.869,2.062 "
- id="polygon824"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon826"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.622,3.957 16.574,3.977 16.43,4.337 16.43,4.517 16.502,4.577 17.558,4.577 17.63,4.517 17.63,4.337 17.486,3.977 17.438,3.957 16.622,3.957 "
- id="polygon828"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.454,4.277 L 16.502,4.297 L 17.558,4.297 L 17.606,4.277"
- id="path830"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.558,4.297 L 17.63,4.337"
- id="path832"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.43,4.337 L 16.502,4.297"
- id="path834"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon836"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.766,3.577 16.742,4.057 17.318,4.057 17.294,3.577 16.766,3.577 "
- id="polygon838"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon840"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.67,4.057 16.622,4.197 17.438,4.197 17.39,4.057 16.67,4.057 "
- id="polygon842"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse844"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse846"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse848"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse850"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse852"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.3670001"
- rx="0.012"
- ry="0.012"
- id="ellipse854"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse856"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse858"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse860"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse862"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse864"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.4169998"
- rx="0.012"
- ry="0.012"
- id="ellipse866"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse868"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse870"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse872"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse874"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse876"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.467"
- rx="0.012"
- ry="0.012"
- id="ellipse878"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse880"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.67"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse882"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse884"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.790001"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse886"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse888"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.91"
- cy="4.5170002"
- rx="0.012"
- ry="0.012"
- id="ellipse890"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse892"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.030001"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse894"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse896"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.33"
- cy="4.3769999"
- rx="0.15000001"
- ry="0.048"
- id="ellipse898"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect900"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect902"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="20.823"
- y="1.648"
- id="rect904"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect906"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect908"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.938"
- y="1.762"
- id="rect910"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="1.9910001"
- x2="20.938"
- y2="1.9910001"
- stroke="#000000"
- stroke-width="0.010"
- id="line912"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.22"
- x2="21.853001"
- y2="2.22"
- stroke="#000000"
- stroke-width="0.010"
- id="line914"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.853001"
- y1="2.391"
- x2="20.938"
- y2="2.391"
- stroke="#000000"
- stroke-width="0.010"
- id="line916"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect918"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect920"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.938"
- y="2.7920001"
- id="rect922"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.823"
- y1="3.1919999"
- x2="21.966999"
- y2="3.1919999"
- stroke="#000000"
- stroke-width="0.010"
- id="line924"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect926"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect928"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.337999"
- y="3.306"
- id="rect930"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect932"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect934"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.566999"
- y="3.306"
- id="rect936"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect938"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect940"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.796"
- y="3.306"
- id="rect942"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect944"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect946"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.738001"
- y="2.9630001"
- id="rect948"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.938"
- y1="2.9630001"
- x2="21.566999"
- y2="2.9630001"
- stroke="#000000"
- stroke-width="0.010"
- id="line950"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect952"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect954"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.938"
- y="3.2490001"
- id="rect956"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect958"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect960"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.995001"
- y="2.448"
- id="rect962"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.849"
- x2="21.51"
- y2="2.849"
- stroke="#000000"
- stroke-width="0.010"
- id="line964"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.51"
- y1="2.9059999"
- x2="21.452"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line966"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.9059999"
- x2="21.052"
- y2="2.9059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line968"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect970"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect972"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="21.108999"
- y="2.849"
- id="rect974"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.995001"
- y1="2.563"
- x2="21.052"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line976"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.108999"
- y1="2.563"
- x2="21.167"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line978"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.681"
- y1="2.563"
- x2="21.796"
- y2="2.563"
- stroke="#000000"
- stroke-width="0.010"
- id="line980"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.878"
- x2="20.881001"
- y2="3.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line982"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.8210001"
- x2="21.91"
- y2="3.8210001"
- stroke="#000000"
- stroke-width="0.010"
- id="line984"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.7639999"
- x2="20.881001"
- y2="3.7639999"
- stroke="#000000"
- stroke-width="0.010"
- id="line986"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.707"
- x2="21.91"
- y2="3.707"
- stroke="#000000"
- stroke-width="0.010"
- id="line988"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.6489999"
- x2="20.881001"
- y2="3.6489999"
- stroke="#000000"
- stroke-width="0.010"
- id="line990"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.881001"
- y1="3.592"
- x2="21.91"
- y2="3.592"
- stroke="#000000"
- stroke-width="0.010"
- id="line992"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.91"
- y1="3.5350001"
- x2="20.881001"
- y2="3.5350001"
- stroke="#000000"
- stroke-width="0.010"
- id="line994"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="18.056999"
- y="5.3460002"
- id="text996"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="17.650999"
- y="5.9460001"
- id="text998"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.16.0/22</text>
- <text
- x="14.353"
- y="4.415"
- id="text1000"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="14.288"
- y="4.915"
- id="text1002"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-BDC</text>
- <text
- x="21.162001"
- y="0.80599999"
- id="text1004"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="21.098"
- y="1.306"
- id="text1006"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LA-PDC</text>
- <rect
- width="1.326"
- height="1.17"
- x="12.426"
- y="2.155"
- id="rect1008"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="13.089"
- cy="3.326"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1010"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.089"
- cy="2.155"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1012"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="13.089"
- cy="2.155"
- rx="0.66299999"
- ry="0.19499999"
- id="ellipse1014"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.752,2.155 L 13.752,3.326 C 13.752,3.434 13.455,3.521 13.089,3.521 C 12.723,3.521 12.426,3.434 12.426,3.326 L 12.426,2.155"
- id="path1016"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="13.775"
- y1="2.6440001"
- x2="14.372"
- y2="2.648"
- stroke="#000000"
- stroke-width="0.100"
- id="line1018"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.734"
- y="2.8369999"
- id="text1020"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.748"
- y="3.237"
- id="text1022"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1024"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1026"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="14.275"
- y="10.44"
- id="rect1028"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1030"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1032"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="14.336"
- y="10.501"
- id="rect1034"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="10.744"
- x2="15.309"
- y2="10.744"
- stroke="#000000"
- stroke-width="0.010"
- id="line1036"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.309"
- y1="10.988"
- x2="14.336"
- y2="10.988"
- stroke="#000000"
- stroke-width="0.010"
- id="line1038"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1040"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1042"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="14.458"
- y="11.292"
- id="rect1044"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.275"
- y1="11.839"
- x2="15.492"
- y2="11.839"
- stroke="#000000"
- stroke-width="0.010"
- id="line1046"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1048"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1050"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.127"
- y="11.718"
- id="rect1052"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1054"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1056"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.249"
- y="11.718"
- id="rect1058"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1060"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1062"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="15.37"
- y="11.718"
- id="rect1064"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1066"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1068"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="15.309"
- y="11.535"
- id="rect1070"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.458"
- y1="11.474"
- x2="15.127"
- y2="11.474"
- stroke="#000000"
- stroke-width="0.010"
- id="line1072"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1074"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1076"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.183"
- height="0.182"
- x="15.249"
- y="11.292"
- id="rect1078"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1080"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1082"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="14.397"
- y="11.048"
- id="rect1084"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.353"
- x2="15.066"
- y2="11.353"
- stroke="#000000"
- stroke-width="0.010"
- id="line1086"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1088"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1090"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="14.64"
- y="11.353"
- id="rect1092"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.127"
- y1="11.17"
- x2="15.249"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1094"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="11.9"
- x2="15.431"
- y2="11.9"
- stroke="#000000"
- stroke-width="0.010"
- id="line1096"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="11.961"
- x2="14.336"
- y2="11.961"
- stroke="#000000"
- stroke-width="0.010"
- id="line1098"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.022"
- x2="15.431"
- y2="12.022"
- stroke="#000000"
- stroke-width="0.010"
- id="line1100"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.204"
- x2="14.336"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1102"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.336"
- y1="12.143"
- x2="15.431"
- y2="12.143"
- stroke="#000000"
- stroke-width="0.010"
- id="line1104"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.431"
- y1="12.083"
- x2="14.336"
- y2="12.083"
- stroke="#000000"
- stroke-width="0.010"
- id="line1106"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.397"
- y1="11.17"
- x2="14.458"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1108"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.17"
- x2="14.579"
- y2="11.17"
- stroke="#000000"
- stroke-width="0.010"
- id="line1110"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.519"
- y1="11.413"
- x2="14.579"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1112"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.005"
- y1="11.413"
- x2="15.066"
- y2="11.413"
- stroke="#000000"
- stroke-width="0.010"
- id="line1114"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.442"
- y1="11.353"
- x2="20.584"
- y2="11.34"
- stroke="#000000"
- stroke-width="0.100"
- id="line1116"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.929001"
- y1="11.349"
- x2="16.931"
- y2="12.308"
- stroke="#000000"
- stroke-width="0.100"
- id="line1118"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.931999"
- y1="11.349"
- x2="16.93"
- y2="10.349"
- stroke="#000000"
- stroke-width="0.100"
- id="line1120"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372"
- y1="11.345"
- x2="18.374001"
- y2="12.251"
- stroke="#000000"
- stroke-width="0.100"
- id="line1122"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.372999"
- y1="11.345"
- x2="18.370001"
- y2="10.345"
- stroke="#000000"
- stroke-width="0.100"
- id="line1124"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.815001"
- y1="11.342"
- x2="19.816999"
- y2="12.269"
- stroke="#000000"
- stroke-width="0.100"
- id="line1126"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="19.813"
- y1="11.342"
- x2="19.811001"
- y2="10.342"
- stroke="#000000"
- stroke-width="0.100"
- id="line1128"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1130"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.921"
- y="12.276"
- id="rect1132"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.018"
- y="12.373"
- id="rect1134"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1136"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.043,12.948 18.504,12.948 18.504,13.052 18.067,13.052 18.043,12.948 "
- id="polygon1138"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1140"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.504,12.948 18.696,12.948 18.672,13.052 18.504,13.052 18.504,12.948 "
- id="polygon1142"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1144"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.535"
- y="12.979"
- id="rect1146"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1148"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.28,13.052 18.459,13.052 18.459,13.104 18.548,13.104 18.548,13.157 18.19,13.157 18.19,13.104 18.28,13.104 18.28,13.052 "
- id="polygon1150"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1152"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.364"
- y="12.265"
- id="rect1154"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.461"
- y="12.362"
- id="rect1156"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1158"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.485,12.937 19.946,12.937 19.946,13.041 19.509,13.041 19.485,12.937 "
- id="polygon1160"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1162"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.946,12.937 20.138,12.937 20.114,13.041 19.946,13.041 19.946,12.937 "
- id="polygon1164"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1166"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="19.976999"
- y="12.968"
- id="rect1168"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1170"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.722,13.041 19.901,13.041 19.901,13.094 19.991,13.094 19.991,13.146 19.632,13.146 19.632,13.094 19.722,13.094 19.722,13.041 "
- id="polygon1172"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1174"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="16.489"
- y="9.8400002"
- id="rect1176"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="16.586"
- y="9.9370003"
- id="rect1178"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1180"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.61,10.512 17.071,10.512 17.071,10.616 16.634,10.616 16.61,10.512 "
- id="polygon1182"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1184"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="17.071,10.512 17.263,10.512 17.239,10.616 17.071,10.616 17.071,10.512 "
- id="polygon1186"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1188"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="17.101999"
- y="10.543"
- id="rect1190"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1192"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="16.847,10.616 17.026,10.616 17.026,10.669 17.116,10.669 17.116,10.721 16.757,10.721 16.757,10.669 16.847,10.669 16.847,10.616 "
- id="polygon1194"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1196"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="17.938999"
- y="9.8649998"
- id="rect1198"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="18.035999"
- y="9.9619999"
- id="rect1200"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1202"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.06,10.537 18.521,10.537 18.521,10.641 18.084,10.641 18.06,10.537 "
- id="polygon1204"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1206"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.521,10.537 18.713,10.537 18.689,10.641 18.521,10.641 18.521,10.537 "
- id="polygon1208"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1210"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="18.552"
- y="10.568"
- id="rect1212"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1214"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="18.297,10.641 18.476,10.641 18.476,10.694 18.566,10.694 18.566,10.746 18.207,10.746 18.207,10.694 18.297,10.694 18.297,10.641 "
- id="polygon1216"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1218"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="19.389"
- y="9.8400002"
- id="rect1220"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="19.486"
- y="9.9370003"
- id="rect1222"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1224"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.51,10.512 19.971,10.512 19.971,10.616 19.534,10.616 19.51,10.512 "
- id="polygon1226"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1228"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.971,10.512 20.163,10.512 20.139,10.616 19.971,10.616 19.971,10.512 "
- id="polygon1230"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1232"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="20.002001"
- y="10.543"
- id="rect1234"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1236"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="19.747,10.616 19.926,10.616 19.926,10.669 20.016,10.669 20.016,10.721 19.657,10.721 19.657,10.669 19.747,10.669 19.747,10.616 "
- id="polygon1238"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1240"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.501,12.512 16.453,12.532 16.309,12.892 16.309,13.072 16.381,13.132 17.437,13.132 17.509,13.072 17.509,12.892 17.365,12.532 17.317,12.512 16.501,12.512 "
- id="polygon1242"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.333,12.832 L 16.381,12.852 L 17.437,12.852 L 17.485,12.832"
- id="path1244"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 17.437,12.852 L 17.509,12.892"
- id="path1246"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 16.309,12.892 L 16.381,12.852"
- id="path1248"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1250"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.645,12.132 16.621,12.612 17.197,12.612 17.173,12.132 16.645,12.132 "
- id="polygon1252"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1254"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="16.549,12.612 16.501,12.752 17.317,12.752 17.269,12.612 16.549,12.612 "
- id="polygon1256"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1258"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1260"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1262"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1264"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1266"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.922"
- rx="0.012"
- ry="0.012"
- id="ellipse1268"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1270"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1272"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1274"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1276"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1278"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="12.972"
- rx="0.012"
- ry="0.012"
- id="ellipse1280"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1282"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1284"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1286"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1288"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1290"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.022"
- rx="0.012"
- ry="0.012"
- id="ellipse1292"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1294"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.549"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1296"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1298"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.669001"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1300"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1302"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="16.789"
- cy="13.072"
- rx="0.012"
- ry="0.012"
- id="ellipse1304"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1306"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="16.909"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1308"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1310"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="17.209"
- cy="12.932"
- rx="0.15000001"
- ry="0.048"
- id="ellipse1312"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1314"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1316"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2869999"
- x="20.701"
- y="10.203"
- id="rect1318"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1320"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1322"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="20.816"
- y="10.317"
- id="rect1324"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.546"
- x2="20.816"
- y2="10.546"
- stroke="#000000"
- stroke-width="0.010"
- id="line1326"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="10.774"
- x2="21.731001"
- y2="10.774"
- stroke="#000000"
- stroke-width="0.010"
- id="line1328"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.731001"
- y1="10.946"
- x2="20.816"
- y2="10.946"
- stroke="#000000"
- stroke-width="0.010"
- id="line1330"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1332"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1334"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="20.816"
- y="11.346"
- id="rect1336"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.701"
- y1="11.747"
- x2="21.844999"
- y2="11.747"
- stroke="#000000"
- stroke-width="0.010"
- id="line1338"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1340"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1342"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.216"
- y="11.861"
- id="rect1344"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1346"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1348"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.445"
- y="11.861"
- id="rect1350"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1352"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1354"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="21.674"
- y="11.861"
- id="rect1356"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1358"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1360"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="21.615999"
- y="11.518"
- id="rect1362"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.816"
- y1="11.518"
- x2="21.445"
- y2="11.518"
- stroke="#000000"
- stroke-width="0.010"
- id="line1364"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1366"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1368"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="20.816"
- y="11.804"
- id="rect1370"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1372"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1374"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="20.872999"
- y="11.003"
- id="rect1376"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.404"
- x2="21.388"
- y2="11.404"
- stroke="#000000"
- stroke-width="0.010"
- id="line1378"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.388"
- y1="11.461"
- x2="21.330999"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1380"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.461"
- x2="20.93"
- y2="11.461"
- stroke="#000000"
- stroke-width="0.010"
- id="line1382"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1384"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1386"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="20.987"
- y="11.404"
- id="rect1388"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.872999"
- y1="11.118"
- x2="20.93"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1390"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.987"
- y1="11.118"
- x2="21.045"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1392"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.559"
- y1="11.118"
- x2="21.674"
- y2="11.118"
- stroke="#000000"
- stroke-width="0.010"
- id="line1394"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.433"
- x2="20.759001"
- y2="12.433"
- stroke="#000000"
- stroke-width="0.010"
- id="line1396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.376"
- x2="21.788"
- y2="12.376"
- stroke="#000000"
- stroke-width="0.010"
- id="line1398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.319"
- x2="20.759001"
- y2="12.319"
- stroke="#000000"
- stroke-width="0.010"
- id="line1400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.261"
- x2="21.788"
- y2="12.261"
- stroke="#000000"
- stroke-width="0.010"
- id="line1402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.204"
- x2="20.759001"
- y2="12.204"
- stroke="#000000"
- stroke-width="0.010"
- id="line1404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.759001"
- y1="12.147"
- x2="21.788"
- y2="12.147"
- stroke="#000000"
- stroke-width="0.010"
- id="line1406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.788"
- y1="12.09"
- x2="20.759001"
- y2="12.09"
- stroke="#000000"
- stroke-width="0.010"
- id="line1408"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="17.735001"
- y="9.026"
- id="text1410"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="17.301001"
- y="9.6260004"
- id="text1412"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.20.0/22</text>
- <text
- x="14.206"
- y="12.995"
- id="text1414"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="13.885"
- y="13.495"
- id="text1416"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WASH-BDC</text>
- <text
- x="20.912001"
- y="13.518"
- id="text1418"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="20.51"
- y="14.018"
- id="text1420"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">WASH-APPS</text>
- <rect
- width="1.3150001"
- height="1.161"
- x="12"
- y="10.659"
- id="rect1422"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="12.658"
- cy="11.819"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1424"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.658"
- cy="10.659"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1426"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="12.658"
- cy="10.659"
- rx="0.65799999"
- ry="0.193"
- id="ellipse1428"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 13.316,10.659 L 13.316,11.819 C 13.316,11.926 13.021,12.013 12.658,12.013 C 12.295,12.013 12,11.926 12,11.819 L 12,10.659"
- id="path1430"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="14.275"
- y1="11.353"
- x2="13.275"
- y2="11.344"
- stroke="#000000"
- stroke-width="0.100"
- id="line1432"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="12.337"
- y="11.292"
- id="text1434"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="12.352"
- y="11.692"
- id="text1436"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1438"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <path
- d="M 9.35,11.667 C 9.83,11.677 10.761,11.461 10.63,10.999 C 10.499,10.536 9.874,10.433 9.612,10.567 C 9.35,10.7 10.019,9.919 8.74,9.714 C 7.46,9.508 6.805,9.837 6.994,10.073 C 7.183,10.31 5.875,9.518 5.264,9.971 C 4.653,10.423 5.889,10.855 5.627,10.793 C 5.366,10.731 4.566,10.814 4.828,11.585 C 5.089,12.356 7.445,11.759 7.183,11.872 C 6.922,11.986 7.576,12.551 8.39,12.438 C 9.205,12.325 9.263,12.12 9.35,11.667 L 9.35,11.667"
- id="path1440"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.7909999"
- y="11.036"
- id="text1442"
- style="font-size:0.69999999px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Internet</text>
- <path
- d="M 4.7,11.1 C 5.035363,11.196174 5.3953356,11.076093 5.6057965,10.797841 C 5.8162574,10.51959 5.8338243,10.140524 5.65,9.844"
- id="path1444"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 8.675,9.794 C 7.4940305,10.104758 6.3530779,10.551408 5.275,11.125"
- id="path1446"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <path
- d="M 4.7,11.15 C 6.6098972,11.931939 8.7554368,11.904871 10.645,11.075"
- id="path1448"
- style="fill:none;stroke:#000000;stroke-width:0.1;stroke-dasharray:0.1, 0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1450"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1452"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.397"
- height="4.1900001"
- x="0.61400002"
- y="8.7200003"
- id="rect1454"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1456"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1458"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.117"
- height="1.676"
- x="0.75400001"
- y="8.8590002"
- id="rect1460"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.1389999"
- x2="1.8710001"
- y2="9.1389999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1462"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="9.4180002"
- x2="0.75400001"
- y2="9.4180002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1464"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.698"
- x2="1.8710001"
- y2="9.698"
- stroke="#000000"
- stroke-width="0.010"
- id="line1466"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="9.9770002"
- x2="1.8710001"
- y2="9.9770002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1468"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.8710001"
- y1="10.256"
- x2="0.75400001"
- y2="10.256"
- stroke="#000000"
- stroke-width="0.010"
- id="line1470"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1472"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1474"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.76800001"
- height="0.419"
- x="0.75400001"
- y="10.675"
- id="rect1476"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.61400002"
- y1="11.374"
- x2="2.0109999"
- y2="11.374"
- stroke="#000000"
- stroke-width="0.010"
- id="line1478"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1480"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1482"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.243"
- y="11.513"
- id="rect1484"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1486"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1488"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.522"
- y="11.513"
- id="rect1490"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1492"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1494"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.07"
- height="0.07"
- x="1.801"
- y="11.513"
- id="rect1496"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1498"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1500"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.14"
- height="0.14"
- x="1.7309999"
- y="11.094"
- id="rect1502"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.75400001"
- y1="10.885"
- x2="1.522"
- y2="10.885"
- stroke="#000000"
- stroke-width="0.010"
- id="line1504"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1506"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1508"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.20999999"
- height="0.20999999"
- x="0.75400001"
- y="11.444"
- id="rect1510"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1512"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1514"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97799999"
- height="0.07"
- x="0.82300001"
- y="10.326"
- id="rect1516"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.745"
- x2="1.452"
- y2="10.745"
- stroke="#000000"
- stroke-width="0.010"
- id="line1518"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.452"
- y1="10.815"
- x2="1.382"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1520"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.815"
- x2="0.89300001"
- y2="10.815"
- stroke="#000000"
- stroke-width="0.010"
- id="line1522"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1524"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1526"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.34900001"
- height="0.07"
- x="0.963"
- y="10.745"
- id="rect1528"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.82300001"
- y1="10.466"
- x2="0.89300001"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1530"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.963"
- y1="10.466"
- x2="1.033"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1532"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.6619999"
- y1="10.466"
- x2="1.801"
- y2="10.466"
- stroke="#000000"
- stroke-width="0.010"
- id="line1534"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.84"
- x2="1.941"
- y2="12.84"
- stroke="#000000"
- stroke-width="0.010"
- id="line1536"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.77"
- x2="0.68400002"
- y2="12.77"
- stroke="#000000"
- stroke-width="0.010"
- id="line1538"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.701"
- x2="1.941"
- y2="12.701"
- stroke="#000000"
- stroke-width="0.010"
- id="line1540"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.631"
- x2="0.68400002"
- y2="12.631"
- stroke="#000000"
- stroke-width="0.010"
- id="line1542"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.561"
- x2="1.941"
- y2="12.561"
- stroke="#000000"
- stroke-width="0.010"
- id="line1544"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.491"
- x2="0.68400002"
- y2="12.491"
- stroke="#000000"
- stroke-width="0.010"
- id="line1546"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.421"
- x2="1.941"
- y2="12.421"
- stroke="#000000"
- stroke-width="0.010"
- id="line1548"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.351"
- x2="0.68400002"
- y2="12.351"
- stroke="#000000"
- stroke-width="0.010"
- id="line1550"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.282"
- x2="1.941"
- y2="12.282"
- stroke="#000000"
- stroke-width="0.010"
- id="line1552"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.212"
- x2="0.68400002"
- y2="12.212"
- stroke="#000000"
- stroke-width="0.010"
- id="line1554"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.142"
- x2="1.941"
- y2="12.142"
- stroke="#000000"
- stroke-width="0.010"
- id="line1556"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="12.072"
- x2="0.68400002"
- y2="12.072"
- stroke="#000000"
- stroke-width="0.010"
- id="line1558"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="0.68400002"
- y1="12.002"
- x2="1.941"
- y2="12.002"
- stroke="#000000"
- stroke-width="0.010"
- id="line1560"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.941"
- y1="11.932"
- x2="0.68400002"
- y2="11.932"
- stroke="#000000"
- stroke-width="0.010"
- id="line1562"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.559"
- y="12.296"
- id="rect1564"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.559"
- y="12.296"
- id="rect1566"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.454"
- y="12.401"
- id="rect1568"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
- id="polygon1570"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.427,13.024 -5.928,13.024 -5.928,13.137 -6.401,13.137 -6.427,13.024 "
- id="polygon1572"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
- id="polygon1574"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.928,13.024 -5.719,13.024 -5.746,13.137 -5.928,13.137 -5.928,13.024 "
- id="polygon1576"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.8940001"
- y="13.058"
- id="rect1578"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.8940001"
- y="13.058"
- id="rect1580"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
- id="polygon1582"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.17,13.137 -5.976,13.137 -5.976,13.194 -5.879,13.194 -5.879,13.25 -6.267,13.25 -6.267,13.194 -6.17,13.194 -6.17,13.137 "
- id="polygon1584"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.653"
- y1="11.13"
- x2="-9.6660004"
- y2="11.13"
- stroke="#000000"
- stroke-width="0.100"
- id="line1586"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-1.289"
- y1="11.13"
- x2="-1.289"
- y2="10.145"
- stroke="#000000"
- stroke-width="0.100"
- id="line1588"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.766"
- y1="11.13"
- x2="-3.766"
- y2="12.295"
- stroke="#000000"
- stroke-width="0.100"
- id="line1590"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-3.7739999"
- y1="11.13"
- x2="-3.7739999"
- y2="10.099"
- stroke="#000000"
- stroke-width="0.100"
- id="line1592"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-6.0799999"
- y1="11.13"
- x2="-6.0799999"
- y2="12.367"
- stroke="#000000"
- stroke-width="0.100"
- id="line1594"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-6.0939999"
- y1="11.13"
- x2="-6.0939999"
- y2="10.063"
- stroke="#000000"
- stroke-width="0.100"
- id="line1596"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-8.4139996"
- y1="11.13"
- x2="-8.4139996"
- y2="9.5740004"
- stroke="#000000"
- stroke-width="0.100"
- id="line1598"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.069"
- height="0.80199999"
- x="-4.289"
- y="12.216"
- id="rect1600"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.069"
- height="0.80199999"
- x="-4.289"
- y="12.216"
- id="rect1602"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.83700001"
- height="0.55199999"
- x="-4.1729999"
- y="12.332"
- id="rect1604"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
- id="polygon1606"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.144,13.018 -3.594,13.018 -3.594,13.143 -4.115,13.143 -4.144,13.018 "
- id="polygon1608"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
- id="polygon1610"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.594,13.018 -3.365,13.018 -3.394,13.143 -3.594,13.143 -3.594,13.018 "
- id="polygon1612"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.5569999"
- y="13.055"
- id="rect1614"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.050000001"
- height="0.050000001"
- x="-3.5569999"
- y="13.055"
- id="rect1616"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
- id="polygon1618"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.861,13.143 -3.648,13.143 -3.648,13.205 -3.541,13.205 -3.541,13.267 -3.968,13.267 -3.968,13.205 -3.861,13.205 -3.861,13.143 "
- id="polygon1620"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.579"
- y="9.1079998"
- id="rect1622"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-6.579"
- y="9.1079998"
- id="rect1624"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-6.474"
- y="9.2139997"
- id="rect1626"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
- id="polygon1628"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.448,9.837 -5.948,9.837 -5.948,9.95 -6.421,9.95 -6.448,9.837 "
- id="polygon1630"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
- id="polygon1632"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.948,9.837 -5.74,9.837 -5.766,9.95 -5.948,9.95 -5.948,9.837 "
- id="polygon1634"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.914"
- y="9.8710003"
- id="rect1636"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-5.914"
- y="9.8710003"
- id="rect1638"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
- id="polygon1640"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.191,9.95 -5.996,9.95 -5.996,10.007 -5.899,10.007 -5.899,10.063 -6.288,10.063 -6.288,10.007 -6.191,10.007 -6.191,9.95 "
- id="polygon1642"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.2600002"
- y="9.1450005"
- id="rect1644"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-4.2600002"
- y="9.1450005"
- id="rect1646"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-4.1550002"
- y="9.25"
- id="rect1648"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
- id="polygon1650"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.128,9.873 -3.629,9.873 -3.629,9.986 -4.102,9.986 -4.128,9.873 "
- id="polygon1652"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
- id="polygon1654"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.629,9.873 -3.42,9.873 -3.447,9.986 -3.629,9.986 -3.629,9.873 "
- id="polygon1656"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.595"
- y="9.9069996"
- id="rect1658"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-3.595"
- y="9.9069996"
- id="rect1660"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
- id="polygon1662"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.871,9.986 -3.677,9.986 -3.677,10.043 -3.58,10.043 -3.58,10.099 -3.969,10.099 -3.969,10.043 -3.871,10.043 -3.871,9.986 "
- id="polygon1664"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-8.9029999"
- y="9.0410004"
- id="rect1666"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.97100002"
- height="0.72799999"
- x="-8.9029999"
- y="9.0410004"
- id="rect1668"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.76099998"
- height="0.50199997"
- x="-8.7980003"
- y="9.1470003"
- id="rect1670"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
- id="polygon1672"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.771,9.77 -8.272,9.77 -8.272,9.883 -8.745,9.883 -8.771,9.77 "
- id="polygon1674"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
- id="polygon1676"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.272,9.77 -8.063,9.77 -8.09,9.883 -8.272,9.883 -8.272,9.77 "
- id="polygon1678"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-8.2379999"
- y="9.8039999"
- id="rect1680"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.045000002"
- height="0.045000002"
- x="-8.2379999"
- y="9.8039999"
- id="rect1682"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
- id="polygon1684"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-8.515,9.883 -8.32,9.883 -8.32,9.94 -8.223,9.94 -8.223,9.996 -8.612,9.996 -8.612,9.94 -8.515,9.94 -8.515,9.883 "
- id="polygon1686"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
- id="polygon1688"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.701,9.517 -1.75,9.538 -1.895,9.902 -1.895,10.084 -1.823,10.145 -0.754,10.145 -0.682,10.084 -0.682,9.902 -0.827,9.538 -0.876,9.517 -1.701,9.517 "
- id="polygon1690"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.871,9.841 L -1.823,9.861 L -0.754,9.861 L -0.706,9.841"
- id="path1692"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -0.754,9.861 L -0.682,9.902"
- id="path1694"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -1.895,9.902 L -1.823,9.861"
- id="path1696"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
- id="polygon1698"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.556,9.133 -1.58,9.618 -0.997,9.618 -1.021,9.133 -1.556,9.133 "
- id="polygon1700"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
- id="polygon1702"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-1.653,9.618 -1.701,9.76 -0.876,9.76 -0.924,9.618 -1.653,9.618 "
- id="polygon1704"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-1.653"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1706"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1708"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1710"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1712"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1714"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="9.9320002"
- rx="0.012"
- ry="0.012"
- id="ellipse1716"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1718"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1720"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1722"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1724"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1726"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="9.9829998"
- rx="0.012"
- ry="0.012"
- id="ellipse1728"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1730"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1732"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1734"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1736"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1738"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="10.033"
- rx="0.012"
- ry="0.012"
- id="ellipse1740"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.653"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1742"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.653"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1744"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.531"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1746"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.531"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1748"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.41"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1750"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-1.41"
- cy="10.084"
- rx="0.012"
- ry="0.012"
- id="ellipse1752"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-1.289"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1754"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-1.289"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1756"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-0.98500001"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1758"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-0.98500001"
- cy="9.9420004"
- rx="0.152"
- ry="0.048999999"
- id="ellipse1760"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1762"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1764"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.312"
- height="2.625"
- x="-11.059"
- y="9.7469997"
- id="rect1766"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1768"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1770"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.05"
- height="1.05"
- x="-10.928"
- y="9.8780003"
- id="rect1772"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8780003"
- y1="10.141"
- x2="-10.928"
- y2="10.141"
- stroke="#000000"
- stroke-width="0.010"
- id="line1774"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.928"
- y1="10.403"
- x2="-9.8780003"
- y2="10.403"
- stroke="#000000"
- stroke-width="0.010"
- id="line1776"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8780003"
- y1="10.6"
- x2="-10.928"
- y2="10.6"
- stroke="#000000"
- stroke-width="0.010"
- id="line1778"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1780"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1782"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.722"
- height="0.39399999"
- x="-10.928"
- y="11.06"
- id="rect1784"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-11.059"
- y1="11.519"
- x2="-9.7460003"
- y2="11.519"
- stroke="#000000"
- stroke-width="0.010"
- id="line1786"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1788"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1790"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.468"
- y="11.65"
- id="rect1792"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1794"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1796"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-10.206"
- y="11.65"
- id="rect1798"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1800"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1802"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.066"
- height="0.066"
- x="-9.9429998"
- y="11.65"
- id="rect1804"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1806"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1808"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.131"
- height="0.066"
- x="-10.009"
- y="11.256"
- id="rect1810"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.928"
- y1="11.256"
- x2="-10.206"
- y2="11.256"
- stroke="#000000"
- stroke-width="0.010"
- id="line1812"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1814"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1816"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.197"
- height="0.197"
- x="-10.928"
- y="11.585"
- id="rect1818"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1820"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1822"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91900003"
- height="0.066"
- x="-10.862"
- y="10.666"
- id="rect1824"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="11.125"
- x2="-10.271"
- y2="11.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line1826"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.271"
- y1="11.191"
- x2="-10.337"
- y2="11.191"
- stroke="#000000"
- stroke-width="0.010"
- id="line1828"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="11.191"
- x2="-10.796"
- y2="11.191"
- stroke="#000000"
- stroke-width="0.010"
- id="line1830"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1832"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1834"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.32800001"
- height="0.066"
- x="-10.731"
- y="11.125"
- id="rect1836"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.862"
- y1="10.797"
- x2="-10.796"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1838"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.731"
- y1="10.797"
- x2="-10.665"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1840"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.074"
- y1="10.797"
- x2="-9.9429998"
- y2="10.797"
- stroke="#000000"
- stroke-width="0.010"
- id="line1842"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.306"
- x2="-10.993"
- y2="12.306"
- stroke="#000000"
- stroke-width="0.010"
- id="line1844"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="12.241"
- x2="-9.8120003"
- y2="12.241"
- stroke="#000000"
- stroke-width="0.010"
- id="line1846"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.175"
- x2="-10.993"
- y2="12.175"
- stroke="#000000"
- stroke-width="0.010"
- id="line1848"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="12.11"
- x2="-9.8120003"
- y2="12.11"
- stroke="#000000"
- stroke-width="0.010"
- id="line1850"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="12.044"
- x2="-10.993"
- y2="12.044"
- stroke="#000000"
- stroke-width="0.010"
- id="line1852"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-10.993"
- y1="11.978"
- x2="-9.8120003"
- y2="11.978"
- stroke="#000000"
- stroke-width="0.010"
- id="line1854"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-9.8120003"
- y1="11.913"
- x2="-10.993"
- y2="11.913"
- stroke="#000000"
- stroke-width="0.010"
- id="line1856"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="-4.2459998"
- y="8.2609997"
- id="text1858"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-4.5809999"
- y="8.8610001"
- id="text1860"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.0.0/22</text>
- <text
- x="-10.628"
- y="13.181"
- id="text1862"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="-10.454"
- y="13.681"
- id="text1864"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">GWYN-APPS</text>
- <rect
- width="1.4450001"
- height="1.275"
- x="2.5510001"
- y="8.6120005"
- id="rect1866"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="3.273"
- cy="9.8870001"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1868"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1870"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.273"
- cy="8.6120005"
- rx="0.72299999"
- ry="0.213"
- id="ellipse1872"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.996,8.612 L 3.996,9.887 C 3.996,10.005 3.672,10.1 3.273,10.1 C 2.874,10.1 2.551,10.005 2.551,9.887 L 2.551,8.612"
- id="path1874"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.0109999"
- y1="9.2469997"
- x2="2.586"
- y2="9.2469997"
- stroke="#000000"
- stroke-width="0.100"
- id="line1876"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="2.983"
- y="9.3260002"
- id="text1878"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.928"
- y="9.7259998"
- id="text1880"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="5.725,19.819 5.725,18.237 5.732,18.237 5.732,17.325 "
- id="polyline1882"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="1.317"
- y="15.131"
- id="text1884"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">1100 Users</text>
- <text
- x="1.136"
- y="6.0770001"
- id="text1886"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">320 Users</text>
- <text
- x="12.943"
- y="6.0310001"
- id="text1888"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">180 Users</text>
- <text
- x="12.383"
- y="15.277"
- id="text1890"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">100 Users</text>
- <text
- x="-9.9619999"
- y="15.156"
- id="text1892"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York - Bldg1</text>
- <text
- x="13.214"
- y="0.46399999"
- id="text1894"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Los Angeles</text>
- <text
- x="1.1109999"
- y="0.46399999"
- id="text1896"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">London</text>
- <text
- x="12.979"
- y="8.0889997"
- id="text1898"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Washington, DC</text>
- <rect
- width="11.132"
- height="6.5630002"
- x="-11.146"
- y="16.205999"
- id="rect1900"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1902"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1904"
- style="fill:#ebebeb;stroke:none" />
- <rect
- width="11.732"
- height="5.9629998"
- x="-11.446"
- y="16.506001"
- id="rect1906"
- style="fill:#ebebeb;stroke:none;stroke-width:0" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1908"
- style="fill:#ebebeb;stroke:none" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1910"
- style="fill:#ebebeb;stroke:none" />
- <line
- x1="-11.146"
- y1="16.205999"
- x2="-0.014"
- y2="16.205999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1912"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.146"
- y1="22.768999"
- x2="-0.014"
- y2="22.768999"
- stroke="#000000"
- stroke-width="0.050"
- id="line1914"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.146,16.206 C -11.311685,16.206 -11.446,16.340315 -11.446,16.506"
- id="path1916"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M 0.286,16.506 C 0.286,16.340315 0.15168542,16.206 -0.014,16.206"
- id="path1918"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <line
- x1="-11.446"
- y1="16.506001"
- x2="-11.446"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1920"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="0.28600001"
- y1="16.506001"
- x2="0.28600001"
- y2="22.469"
- stroke="#000000"
- stroke-width="0.050"
- id="line1922"
- style="stroke:#000000;stroke-width:0.05" />
- <path
- d="M -11.446,22.469 C -11.446,22.634685 -11.311685,22.769 -11.146,22.769"
- id="path1924"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <path
- d="M -0.014,22.769 C 0.15168542,22.769 0.286,22.634685 0.286,22.469"
- id="path1926"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1928"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1930"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.78799999"
- height="0.78799999"
- x="-2.214"
- y="19.285"
- id="rect1932"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1934"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.772,19.413 C -1.772,19.806 -1.693,19.728 -2.087,19.728"
- id="path1936"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1938"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.734,19.474 -1.773,19.395 -1.813,19.474 -1.734,19.474 "
- id="polygon1940"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1942"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-2.025,19.687 -2.104,19.726 -2.025,19.765 -2.025,19.687 "
- id="polygon1944"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1946"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M -1.538,19.634 C -1.932,19.634 -1.853,19.555 -1.853,19.949"
- id="path1948"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1950"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.608,19.671 -1.529,19.632 -1.608,19.592 -1.608,19.671 "
- id="polygon1952"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1954"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="-1.899,19.884 -1.86,19.962 -1.821,19.884 -1.899,19.884 "
- id="polygon1956"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="-5.2220001"
- y="17.145"
- id="text1958"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="-5.5609999"
- y="17.745001"
- id="text1960"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.4.0/22</text>
- <text
- x="-10.001"
- y="21.07"
- id="text1962"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="-10.37"
- y="21.57"
- id="text1964"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-BDC</text>
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1966"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1968"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="-8.665"
- y="18.782"
- id="rect1970"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1972"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1974"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="-8.6040001"
- y="18.843"
- id="rect1976"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="19.087"
- x2="-7.6300001"
- y2="19.087"
- stroke="#000000"
- stroke-width="0.010"
- id="line1978"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.6300001"
- y1="19.33"
- x2="-8.6040001"
- y2="19.33"
- stroke="#000000"
- stroke-width="0.010"
- id="line1980"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1982"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1984"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="-8.4820004"
- y="19.634001"
- id="rect1986"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.665"
- y1="20.181999"
- x2="-7.448"
- y2="20.181999"
- stroke="#000000"
- stroke-width="0.010"
- id="line1988"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1990"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1992"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.8130002"
- y="20.059999"
- id="rect1994"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect1996"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect1998"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.691"
- y="20.059999"
- id="rect2000"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2002"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2004"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="-7.5700002"
- y="20.059999"
- id="rect2006"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2008"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2010"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="-7.6300001"
- y="19.877001"
- id="rect2012"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4820004"
- y1="19.816999"
- x2="-7.8130002"
- y2="19.816999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2014"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2016"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2018"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="-7.691"
- y="19.634001"
- id="rect2020"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2022"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2024"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="-8.5430002"
- y="19.391001"
- id="rect2026"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.695"
- x2="-7.8740001"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.010"
- id="line2028"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2030"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2032"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="-8.3000002"
- y="19.695"
- id="rect2034"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.8130002"
- y1="19.511999"
- x2="-7.691"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2036"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.242001"
- x2="-7.5089998"
- y2="20.242001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2038"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.302999"
- x2="-8.6040001"
- y2="20.302999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2040"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.364"
- x2="-7.5089998"
- y2="20.364"
- stroke="#000000"
- stroke-width="0.010"
- id="line2042"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.547001"
- x2="-8.6040001"
- y2="20.547001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2044"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.6040001"
- y1="20.486"
- x2="-7.5089998"
- y2="20.486"
- stroke="#000000"
- stroke-width="0.010"
- id="line2046"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.5089998"
- y1="20.424999"
- x2="-8.6040001"
- y2="20.424999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2048"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.5430002"
- y1="19.511999"
- x2="-8.4820004"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2050"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.511999"
- x2="-8.3599997"
- y2="19.511999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2052"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-8.4209995"
- y1="19.756001"
- x2="-8.3599997"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2054"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.9349999"
- y1="19.756001"
- x2="-7.8740001"
- y2="19.756001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2056"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="-7.4980001"
- y1="19.695"
- x2="-2.164"
- y2="19.679001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2058"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9559999"
- y1="19.690001"
- x2="-5.9530001"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.100"
- id="line2060"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-5.9530001"
- y1="19.690001"
- x2="-5.9559999"
- y2="18.690001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2062"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4590001"
- y1="19.686001"
- x2="-4.4559999"
- y2="20.591"
- stroke="#000000"
- stroke-width="0.100"
- id="line2064"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-4.4569998"
- y1="19.686001"
- x2="-4.46"
- y2="18.686001"
- stroke="#000000"
- stroke-width="0.100"
- id="line2066"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.961"
- y1="19.681"
- x2="-2.9579999"
- y2="20.608"
- stroke="#000000"
- stroke-width="0.100"
- id="line2068"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="-2.9619999"
- y1="19.681"
- x2="-2.9649999"
- y2="18.681"
- stroke="#000000"
- stroke-width="0.100"
- id="line2070"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2072"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.9439998"
- y="20.618"
- id="rect2074"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8470001"
- y="20.715"
- id="rect2076"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2078"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.822,21.29 -4.361,21.29 -4.361,21.395 -4.798,21.395 -4.822,21.29 "
- id="polygon2080"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2082"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.361,21.29 -4.169,21.29 -4.193,21.395 -4.361,21.395 -4.361,21.29 "
- id="polygon2084"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2086"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.3299999"
- y="21.320999"
- id="rect2088"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2090"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.585,21.395 -4.406,21.395 -4.406,21.447 -4.317,21.447 -4.317,21.499 -4.675,21.499 -4.675,21.447 -4.585,21.447 -4.585,21.395 "
- id="polygon2092"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2094"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.4260001"
- y="20.607"
- id="rect2096"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.329"
- y="20.704"
- id="rect2098"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2100"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.305,21.279 -2.844,21.279 -2.844,21.384 -3.281,21.384 -3.305,21.279 "
- id="polygon2102"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2104"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.844,21.279 -2.652,21.279 -2.676,21.384 -2.844,21.384 -2.844,21.279 "
- id="polygon2106"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2108"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.813"
- y="21.311001"
- id="rect2110"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2112"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.068,21.384 -2.889,21.384 -2.889,21.436 -2.799,21.436 -2.799,21.488 -3.158,21.488 -3.158,21.436 -3.068,21.436 -3.068,21.384 "
- id="polygon2114"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2116"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-6.3759999"
- y="18.181999"
- id="rect2118"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-6.2789998"
- y="18.278999"
- id="rect2120"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2122"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.255,18.854 -5.794,18.854 -5.794,18.959 -6.231,18.959 -6.255,18.854 "
- id="polygon2124"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2126"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-5.794,18.854 -5.602,18.854 -5.626,18.959 -5.794,18.959 -5.794,18.854 "
- id="polygon2128"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2130"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-5.763"
- y="18.886"
- id="rect2132"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2134"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-6.018,18.959 -5.839,18.959 -5.839,19.011 -5.749,19.011 -5.749,19.063 -6.108,19.063 -6.108,19.011 -6.018,19.011 -6.018,18.959 "
- id="polygon2136"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2138"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-4.901"
- y="18.181999"
- id="rect2140"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-4.8039999"
- y="18.278999"
- id="rect2142"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2144"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.78,18.854 -4.319,18.854 -4.319,18.959 -4.756,18.959 -4.78,18.854 "
- id="polygon2146"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2148"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.319,18.854 -4.127,18.854 -4.151,18.959 -4.319,18.959 -4.319,18.854 "
- id="polygon2150"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2152"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-4.2880001"
- y="18.886"
- id="rect2154"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2156"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-4.543,18.959 -4.364,18.959 -4.364,19.011 -4.274,19.011 -4.274,19.063 -4.633,19.063 -4.633,19.011 -4.543,19.011 -4.543,18.959 "
- id="polygon2158"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2160"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="-3.401"
- y="18.207001"
- id="rect2162"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="-3.3039999"
- y="18.304001"
- id="rect2164"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2166"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.28,18.879 -2.819,18.879 -2.819,18.984 -3.256,18.984 -3.28,18.879 "
- id="polygon2168"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2170"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-2.819,18.879 -2.627,18.879 -2.651,18.984 -2.819,18.984 -2.819,18.879 "
- id="polygon2172"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2174"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="-2.7880001"
- y="18.910999"
- id="rect2176"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2178"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="-3.043,18.984 -2.864,18.984 -2.864,19.036 -2.774,19.036 -2.774,19.088 -3.133,19.088 -3.133,19.036 -3.043,19.036 -3.043,18.984 "
- id="polygon2180"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2182"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.439,20.854 -6.487,20.874 -6.631,21.234 -6.631,21.414 -6.559,21.474 -5.503,21.474 -5.431,21.414 -5.431,21.234 -5.575,20.874 -5.623,20.854 -6.439,20.854 "
- id="polygon2184"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.607,21.174 L -6.559,21.194 L -5.503,21.194 L -5.455,21.174"
- id="path2186"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -5.503,21.194 L -5.431,21.234"
- id="path2188"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M -6.631,21.234 L -6.559,21.194"
- id="path2190"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2192"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.295,20.474 -6.319,20.954 -5.743,20.954 -5.767,20.474 -6.295,20.474 "
- id="polygon2194"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2196"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="-6.391,20.954 -6.439,21.094 -5.623,21.094 -5.671,20.954 -6.391,20.954 "
- id="polygon2198"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2200"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2202"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2204"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2206"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2208"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.264"
- rx="0.012"
- ry="0.012"
- id="ellipse2210"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2212"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2214"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2216"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2218"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2220"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.313999"
- rx="0.012"
- ry="0.012"
- id="ellipse2222"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2224"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2226"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2228"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2230"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2232"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.364"
- rx="0.012"
- ry="0.012"
- id="ellipse2234"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2236"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.3909998"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2238"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2240"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.2709999"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2242"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2244"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="-6.151"
- cy="21.414"
- rx="0.012"
- ry="0.012"
- id="ellipse2246"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2248"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-6.0310001"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2250"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2252"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="-5.7309999"
- cy="21.274"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2254"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.17"
- height="1.033"
- x="-10.59"
- y="19.132"
- id="rect2256"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="-10.004"
- cy="20.165001"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2258"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.004"
- cy="19.132"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2260"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="-10.004"
- cy="19.132"
- rx="0.58499998"
- ry="0.17200001"
- id="ellipse2262"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M -9.419,19.132 L -9.419,20.165 C -9.419,20.26 -9.681,20.337 -10.004,20.337 C -10.328,20.337 -10.59,20.26 -10.59,20.165 L -10.59,19.132"
- id="path2264"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="-9.3959999"
- y1="19.684"
- x2="-8.665"
- y2="19.695"
- stroke="#000000"
- stroke-width="0.100"
- id="line2266"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-10.303"
- y="19.759001"
- id="text2268"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="-10.288"
- y="20.159"
- id="text2270"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="-0.91500002"
- y="19.843"
- id="text2272"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Router</text>
- <text
- x="-1.867"
- y="22.455999"
- id="text2274"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">50 Users</text>
- <text
- x="-10.478"
- y="17.114"
- id="text2276"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="-10.147"
- y="17.914"
- id="text2278"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 2</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.554,15.161 -1.554,15.906 -1.821,15.906 -1.821,19.285 "
- id="polyline2280"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2282"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2284"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.787"
- height="0.78799999"
- x="5.3379998"
- y="16.538"
- id="rect2286"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2288"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 5.781,16.665 C 5.781,17.059 5.859,16.98 5.466,16.98"
- id="path2290"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2292"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.818,16.727 5.779,16.648 5.74,16.727 5.818,16.727 "
- id="polygon2294"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2296"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.527,16.939 5.448,16.979 5.527,17.018 5.527,16.939 "
- id="polygon2298"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2300"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 6.014,16.887 C 5.62,16.887 5.699,16.808 5.699,17.202"
- id="path2302"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2304"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.944,16.924 6.023,16.884 5.944,16.845 5.944,16.924 "
- id="polygon2306"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2308"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.653,17.136 5.692,17.215 5.732,17.136 5.653,17.136 "
- id="polygon2310"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="7.8559999"
- y="17.167"
- id="text2312"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network:</text>
- <text
- x="7.5180001"
- y="17.767"
- id="text2314"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">172.16.8.0/22</text>
- <text
- x="3.204"
- y="18.118"
- id="text2316"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Server:</text>
- <text
- x="2.835"
- y="18.618"
- id="text2318"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG3-BDC</text>
- <text
- x="12.542"
- y="19.694"
- id="text2320"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server:</text>
- <text
- x="12.687"
- y="20.194"
- id="text2322"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BLDG2-APPS</text>
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2324"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2326"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.217"
- height="1.825"
- x="4.0770001"
- y="18.941999"
- id="rect2328"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2330"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2332"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.97299999"
- height="0.73000002"
- x="4.138"
- y="19.003"
- id="rect2334"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="19.246"
- x2="5.112"
- y2="19.246"
- stroke="#000000"
- stroke-width="0.010"
- id="line2336"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.112"
- y1="19.49"
- x2="4.138"
- y2="19.49"
- stroke="#000000"
- stroke-width="0.010"
- id="line2338"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2340"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2342"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.66900003"
- height="0.36500001"
- x="4.2600002"
- y="19.794001"
- id="rect2344"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.0770001"
- y1="20.341"
- x2="5.2940001"
- y2="20.341"
- stroke="#000000"
- stroke-width="0.010"
- id="line2346"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2348"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2350"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="4.9289999"
- y="20.219999"
- id="rect2352"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2354"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2356"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.0510001"
- y="20.219999"
- id="rect2358"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2360"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2362"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.061000001"
- height="0.061000001"
- x="5.1719999"
- y="20.219999"
- id="rect2364"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2366"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2368"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.122"
- height="0.122"
- x="5.112"
- y="20.037001"
- id="rect2370"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.2600002"
- y1="19.976"
- x2="4.9289999"
- y2="19.976"
- stroke="#000000"
- stroke-width="0.010"
- id="line2372"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2374"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2376"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.182"
- height="0.183"
- x="5.0510001"
- y="19.794001"
- id="rect2378"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2380"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2382"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.852"
- height="0.061000001"
- x="4.1989999"
- y="19.549999"
- id="rect2384"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.855"
- x2="4.868"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.010"
- id="line2386"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2388"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2390"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.30399999"
- height="0.061000001"
- x="4.4419999"
- y="19.855"
- id="rect2392"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.9289999"
- y1="19.672001"
- x2="5.0510001"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2394"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.402"
- x2="5.2329998"
- y2="20.402"
- stroke="#000000"
- stroke-width="0.010"
- id="line2396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.462999"
- x2="4.138"
- y2="20.462999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.524"
- x2="5.2329998"
- y2="20.524"
- stroke="#000000"
- stroke-width="0.010"
- id="line2400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.705999"
- x2="4.138"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.138"
- y1="20.645"
- x2="5.2329998"
- y2="20.645"
- stroke="#000000"
- stroke-width="0.010"
- id="line2404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.2329998"
- y1="20.584999"
- x2="4.138"
- y2="20.584999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.1989999"
- y1="19.672001"
- x2="4.2600002"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2408"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.672001"
- x2="4.382"
- y2="19.672001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2410"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.3210001"
- y1="19.915001"
- x2="4.382"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2412"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.8070002"
- y1="19.915001"
- x2="4.868"
- y2="19.915001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2414"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="5.244"
- y1="19.855"
- x2="10.386"
- y2="19.841999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2416"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7309999"
- y1="19.851"
- x2="6.7329998"
- y2="20.809999"
- stroke="#000000"
- stroke-width="0.100"
- id="line2418"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.7350001"
- y1="19.851"
- x2="6.7319999"
- y2="18.851"
- stroke="#000000"
- stroke-width="0.100"
- id="line2420"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1739998"
- y1="19.847"
- x2="8.1759996"
- y2="20.753"
- stroke="#000000"
- stroke-width="0.100"
- id="line2422"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8.1750002"
- y1="19.847"
- x2="8.1730003"
- y2="18.848"
- stroke="#000000"
- stroke-width="0.100"
- id="line2424"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6169996"
- y1="19.844"
- x2="9.6190004"
- y2="20.771"
- stroke="#000000"
- stroke-width="0.100"
- id="line2426"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.6160002"
- y1="19.844"
- x2="9.6129999"
- y2="18.844"
- stroke="#000000"
- stroke-width="0.100"
- id="line2428"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2430"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.723"
- y="20.778"
- id="rect2432"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8210001"
- y="20.875"
- id="rect2434"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2436"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.845,21.45 8.306,21.45 8.306,21.554 7.869,21.554 7.845,21.45 "
- id="polygon2438"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2440"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.306,21.45 8.498,21.45 8.474,21.554 8.306,21.554 8.306,21.45 "
- id="polygon2442"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2444"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3369999"
- y="21.481001"
- id="rect2446"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2448"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.082,21.554 8.261,21.554 8.261,21.606 8.351,21.606 8.351,21.659 7.992,21.659 7.992,21.606 8.082,21.606 8.082,21.554 "
- id="polygon2450"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2452"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.1660004"
- y="20.767"
- id="rect2454"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2629995"
- y="20.864"
- id="rect2456"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2458"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.287,21.439 9.748,21.439 9.748,21.543 9.311,21.543 9.287,21.439 "
- id="polygon2460"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2462"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.748,21.439 9.94,21.439 9.916,21.543 9.748,21.543 9.748,21.439 "
- id="polygon2464"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2466"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.7790003"
- y="21.469999"
- id="rect2468"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2470"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.524,21.543 9.703,21.543 9.703,21.596 9.793,21.596 9.793,21.648 9.435,21.648 9.435,21.596 9.524,21.596 9.524,21.543 "
- id="polygon2472"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2474"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="6.2909999"
- y="18.341999"
- id="rect2476"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="6.388"
- y="18.438999"
- id="rect2478"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2480"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.412,19.014 6.873,19.014 6.873,19.118 6.436,19.118 6.412,19.014 "
- id="polygon2482"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2484"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.873,19.014 7.065,19.014 7.041,19.118 6.873,19.118 6.873,19.014 "
- id="polygon2486"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2488"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="6.9039998"
- y="19.045"
- id="rect2490"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2492"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="6.649,19.118 6.828,19.118 6.828,19.171 6.918,19.171 6.918,19.223 6.56,19.223 6.56,19.171 6.649,19.171 6.649,19.118 "
- id="polygon2494"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2496"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="7.7410002"
- y="18.367001"
- id="rect2498"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="7.8379998"
- y="18.464001"
- id="rect2500"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2502"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="7.862,19.039 8.323,19.039 8.323,19.143 7.886,19.143 7.862,19.039 "
- id="polygon2504"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2506"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.323,19.039 8.515,19.039 8.491,19.143 8.323,19.143 8.323,19.039 "
- id="polygon2508"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2510"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="8.3540001"
- y="19.07"
- id="rect2512"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2514"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="8.099,19.143 8.278,19.143 8.278,19.196 8.368,19.196 8.368,19.248 8.01,19.248 8.01,19.196 8.099,19.196 8.099,19.143 "
- id="polygon2516"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2518"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="0.89600003"
- height="0.67199999"
- x="9.191"
- y="18.341999"
- id="rect2520"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.70200002"
- height="0.463"
- x="9.2880001"
- y="18.438999"
- id="rect2522"
- style="fill:#000000;stroke:none;stroke-width:0" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2524"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.312,19.014 9.773,19.014 9.773,19.118 9.336,19.118 9.312,19.014 "
- id="polygon2526"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2528"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.773,19.014 9.965,19.014 9.941,19.118 9.773,19.118 9.773,19.014 "
- id="polygon2530"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2532"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.041999999"
- height="0.041999999"
- x="9.8039999"
- y="19.045"
- id="rect2534"
- style="fill:none;stroke:#000000;stroke-width:0.025" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2536"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.05" />
- <polygon
- points="9.549,19.118 9.728,19.118 9.728,19.171 9.818,19.171 9.818,19.223 9.46,19.223 9.46,19.171 9.549,19.171 9.549,19.118 "
- id="polygon2538"
- style="fill:none;stroke:#000000;stroke-width:0.05" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2540"
- style="fill:#b3b3b3;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.303,21.014 6.255,21.034 6.111,21.394 6.111,21.574 6.183,21.634 7.239,21.634 7.311,21.574 7.311,21.394 7.167,21.034 7.119,21.014 6.303,21.014 "
- id="polygon2542"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.135,21.334 L 6.183,21.354 L 7.239,21.354 L 7.287,21.334"
- id="path2544"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 7.239,21.354 L 7.311,21.394"
- id="path2546"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <path
- d="M 6.111,21.394 L 6.183,21.354"
- id="path2548"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2550"
- style="fill:#ffffff;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.447,20.634 6.423,21.114 6.999,21.114 6.975,20.634 6.447,20.634 "
- id="polygon2552"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2554"
- style="fill:#000000;stroke:none;stroke-width:0.08" />
- <polygon
- points="6.351,21.114 6.303,21.254 7.119,21.254 7.071,21.114 6.351,21.114 "
- id="polygon2556"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2558"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2560"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2562"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2564"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2566"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.424"
- rx="0.012"
- ry="0.012"
- id="ellipse2568"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2570"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2572"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2574"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2576"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2578"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.474001"
- rx="0.012"
- ry="0.012"
- id="ellipse2580"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2582"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2584"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2586"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2588"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2590"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.524"
- rx="0.012"
- ry="0.012"
- id="ellipse2592"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2594"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.3509998"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2596"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2598"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.4710002"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2600"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2602"
- style="fill:#0000ff;stroke:none" />
- <ellipse
- cx="6.5910001"
- cy="21.573999"
- rx="0.012"
- ry="0.012"
- id="ellipse2604"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2606"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="6.711"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2608"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2610"
- style="fill:#8f8f8f;stroke:none" />
- <ellipse
- cx="7.0110002"
- cy="21.434"
- rx="0.15000001"
- ry="0.048"
- id="ellipse2612"
- style="fill:none;stroke:#000000;stroke-width:0.02" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2614"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2616"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.1440001"
- height="2.2880001"
- x="10.504"
- y="18.705"
- id="rect2618"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2620"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2622"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91500002"
- height="0.91500002"
- x="10.618"
- y="18.819"
- id="rect2624"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.048"
- x2="10.618"
- y2="19.048"
- stroke="#000000"
- stroke-width="0.010"
- id="line2626"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="19.275999"
- x2="11.533"
- y2="19.275999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2628"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.533"
- y1="19.448"
- x2="10.618"
- y2="19.448"
- stroke="#000000"
- stroke-width="0.010"
- id="line2630"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2632"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2634"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.62900001"
- height="0.34299999"
- x="10.618"
- y="19.848"
- id="rect2636"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.504"
- y1="20.249001"
- x2="11.647"
- y2="20.249001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2638"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2640"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2642"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.018"
- y="20.363001"
- id="rect2644"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2646"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2648"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.247"
- y="20.363001"
- id="rect2650"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2652"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2654"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.057"
- height="0.057"
- x="11.476"
- y="20.363001"
- id="rect2656"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2658"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2660"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.114"
- height="0.057"
- x="11.419"
- y="20.02"
- id="rect2662"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.618"
- y1="20.02"
- x2="11.247"
- y2="20.02"
- stroke="#000000"
- stroke-width="0.010"
- id="line2664"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2666"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2668"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.17200001"
- height="0.17200001"
- x="10.618"
- y="20.306"
- id="rect2670"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2672"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2674"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.801"
- height="0.057"
- x="10.675"
- y="19.504999"
- id="rect2676"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.906"
- x2="11.19"
- y2="19.906"
- stroke="#000000"
- stroke-width="0.010"
- id="line2678"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.19"
- y1="19.962999"
- x2="11.133"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2680"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.962999"
- x2="10.732"
- y2="19.962999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2682"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2684"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2686"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.28600001"
- height="0.057"
- x="10.79"
- y="19.906"
- id="rect2688"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.675"
- y1="19.620001"
- x2="10.732"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2690"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.79"
- y1="19.620001"
- x2="10.847"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2692"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.362"
- y1="19.620001"
- x2="11.476"
- y2="19.620001"
- stroke="#000000"
- stroke-width="0.010"
- id="line2694"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.934999"
- x2="10.561"
- y2="20.934999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2696"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.878"
- x2="11.59"
- y2="20.878"
- stroke="#000000"
- stroke-width="0.010"
- id="line2698"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.820999"
- x2="10.561"
- y2="20.820999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2700"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.763"
- x2="11.59"
- y2="20.763"
- stroke="#000000"
- stroke-width="0.010"
- id="line2702"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.705999"
- x2="10.561"
- y2="20.705999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2704"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.561"
- y1="20.649"
- x2="11.59"
- y2="20.649"
- stroke="#000000"
- stroke-width="0.010"
- id="line2706"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="11.59"
- y1="20.591999"
- x2="10.561"
- y2="20.591999"
- stroke="#000000"
- stroke-width="0.010"
- id="line2708"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.4960001"
- y1="19.819"
- x2="4.0770001"
- y2="19.855"
- stroke="#000000"
- stroke-width="0.100"
- id="line2710"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.183"
- height="1.044"
- x="2.302"
- y="19.268999"
- id="rect2712"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="2.8940001"
- cy="20.312"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2714"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2716"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="2.8940001"
- cy="19.268999"
- rx="0.59100002"
- ry="0.17399999"
- id="ellipse2718"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.485,19.269 L 3.485,20.312 C 3.485,20.409 3.221,20.486 2.894,20.486 C 2.567,20.486 2.302,20.409 2.302,20.312 L 2.302,19.269"
- id="path2720"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="2.589"
- y="19.868999"
- id="text2722"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="2.6040001"
- y="20.268999"
- id="text2724"
- style="font-size:0.40000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <text
- x="12.722"
- y="22.476999"
- id="text2726"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">250 Users</text>
- <text
- x="12.072"
- y="17.239"
- id="text2728"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">New York</text>
- <text
- x="12.402"
- y="18.039"
- id="text2730"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Bldg 3</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="-1.129,15.125 -1.129,15.903 5.732,15.903 5.732,16.538 "
- id="polyline2732"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="16.1"
- y1="22.393"
- x2="15.55"
- y2="23.143"
- stroke="#F7F7F7"
- stroke-width="0.100"
- id="line2734"
- style="stroke:#f7f7f7;stroke-width:0.1" />
- <text
- x="-10.033"
- y="7.7020001"
- id="text2736"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="-10.108"
- y="22.502001"
- id="text2738"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="2.5420001"
- y="22.502001"
- id="text2740"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="1.905"
- y="1.027"
- id="text2742"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: UKNET</text>
- <text
- x="13.814"
- y="1.102"
- id="text2744"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: WESTNET</text>
- <text
- x="18.017"
- y="15.202"
- id="text2746"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain: GLOBALNET</text>
- <text
- x="-10.507"
- y="1.794"
- id="text2748"
- style="font-size:1px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Notes:</text>
- <text
- x="-11.075"
- y="2.5439999"
- id="text2750"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">The decision was made to implement separate</text>
- <text
- x="-11.075"
- y="3.0439999"
- id="text2752"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">domains for the West Coast and for UK</text>
- <text
- x="-11.075"
- y="3.5439999"
- id="text2754"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">operations. Wide-area traffic will be reduced.</text>
- <text
- x="-11.075"
- y="4.0440001"
- id="text2756"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">This design introduces the concept of deploying</text>
- <text
- x="-11.075"
- y="4.5440001"
- id="text2758"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">interdomain trusts, thus permitting much needed</text>
- <text
- x="-11.075"
- y="5.0440001"
- id="text2760"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">network integration and interoperabilty.</text>
- <text
- x="-11.075"
- y="5.5440001"
- id="text2762"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="19.075001cm"
- height="15.897cm"
- viewBox="1.95 0.208 21.025 16.105"
- id="svg2">
- <defs
- id="defs413" />
- <rect
- width="10.1"
- height="13.95"
- x="2.7750001"
- y="2.125"
- id="rect4"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
- id="path6"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
- id="path8"
- style="fill:#ededed;stroke:none" />
- <rect
- width="11.5"
- height="12.55"
- x="2.075"
- y="2.825"
- id="rect10"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
- id="path12"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
- id="path14"
- style="fill:#ededed;stroke:none" />
- <line
- x1="2.7750001"
- y1="2.125"
- x2="12.875"
- y2="2.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line16"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7750001"
- y1="16.075001"
- x2="12.875"
- y2="16.075001"
- stroke="#000000"
- stroke-width="0.010"
- id="line18"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.075"
- y1="2.825"
- x2="2.075"
- y2="15.375"
- stroke="#000000"
- stroke-width="0.010"
- id="line24"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.575"
- y1="2.825"
- x2="13.575"
- y2="15.375"
- stroke="#000000"
- stroke-width="0.010"
- id="line26"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="5.533"
- height="13.95"
- x="14.717"
- y="2.1500001"
- id="rect32"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
- id="path34"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
- id="path36"
- style="fill:#ededed;stroke:none" />
- <rect
- width="6.9320002"
- height="12.55"
- x="14.018"
- y="2.8499999"
- id="rect38"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
- id="path40"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
- id="path42"
- style="fill:#ededed;stroke:none" />
- <line
- x1="14.717"
- y1="2.1500001"
- x2="20.25"
- y2="2.1500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line44"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.717"
- y1="16.1"
- x2="20.25"
- y2="16.1"
- stroke="#000000"
- stroke-width="0.010"
- id="line46"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.018"
- y1="2.8499999"
- x2="14.018"
- y2="15.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line52"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.950001"
- y1="2.8499999"
- x2="20.950001"
- y2="15.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line54"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="6.125"
- height="2.75"
- x="9.9180002"
- y="12.925"
- id="rect60"
- style="fill:#c3c3c3;stroke:none;stroke-width:0" />
- <path
- d="M 9.918,12.925 C 9.6418576,12.925 9.418,13.148858 9.418,13.425"
- id="path62"
- style="fill:#c3c3c3;stroke:none" />
- <path
- d="M 16.543,13.425 C 16.543,13.148858 16.319142,12.925 16.043,12.925"
- id="path64"
- style="fill:#c3c3c3;stroke:none" />
- <rect
- width="7.125"
- height="1.75"
- x="9.4180002"
- y="13.425"
- id="rect66"
- style="fill:#c3c3c3;stroke:none;stroke-width:0" />
- <path
- d="M 9.418,15.175 C 9.418,15.451142 9.6418576,15.675 9.918,15.675"
- id="path68"
- style="fill:#c3c3c3;stroke:none" />
- <path
- d="M 16.043,15.675 C 16.319142,15.675 16.543,15.451142 16.543,15.175"
- id="path70"
- style="fill:#c3c3c3;stroke:none" />
- <line
- x1="9.9180002"
- y1="12.925"
- x2="16.042999"
- y2="12.925"
- stroke="#000000"
- stroke-width="0.001"
- id="line72"
- style="stroke:#000000;stroke-width:0.001" />
- <line
- x1="9.9180002"
- y1="15.675"
- x2="16.042999"
- y2="15.675"
- stroke="#000000"
- stroke-width="0.001"
- id="line74"
- style="stroke:#000000;stroke-width:0.001" />
- <path
- d="M 9.918,12.925 C 9.6418576,12.925 9.418,13.148858 9.418,13.425"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <path
- d="M 16.543,13.425 C 16.543,13.148858 16.319142,12.925 16.043,12.925"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <line
- x1="9.4180002"
- y1="13.425"
- x2="9.4180002"
- y2="15.175"
- stroke="#000000"
- stroke-width="0.001"
- id="line80"
- style="stroke:#000000;stroke-width:0.001" />
- <line
- x1="16.542999"
- y1="13.425"
- x2="16.542999"
- y2="15.175"
- stroke="#000000"
- stroke-width="0.001"
- id="line82"
- style="stroke:#000000;stroke-width:0.001" />
- <path
- d="M 9.418,15.175 C 9.418,15.451142 9.6418576,15.675 9.918,15.675"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <path
- d="M 16.043,15.675 C 16.319142,15.675 16.543,15.451142 16.543,15.175"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <rect
- width="6.125"
- height="2.6500001"
- x="9.75"
- y="10.05"
- id="rect88"
- style="fill:#c3c3c3;stroke:none;stroke-width:0" />
- <path
- d="M 9.75,10.05 C 9.4738576,10.05 9.25,10.273858 9.25,10.55"
- id="path90"
- style="fill:#c3c3c3;stroke:none" />
- <path
- d="M 16.375,10.55 C 16.375,10.273858 16.151142,10.05 15.875,10.05"
- id="path92"
- style="fill:#c3c3c3;stroke:none" />
- <rect
- width="7.125"
- height="1.65"
- x="9.25"
- y="10.55"
- id="rect94"
- style="fill:#c3c3c3;stroke:none;stroke-width:0" />
- <path
- d="M 9.25,12.2 C 9.25,12.476142 9.4738576,12.7 9.75,12.7"
- id="path96"
- style="fill:#c3c3c3;stroke:none" />
- <path
- d="M 15.875,12.7 C 16.151142,12.7 16.375,12.476142 16.375,12.2"
- id="path98"
- style="fill:#c3c3c3;stroke:none" />
- <line
- x1="9.75"
- y1="10.05"
- x2="15.875"
- y2="10.05"
- stroke="#000000"
- stroke-width="0.001"
- id="line100"
- style="stroke:#000000;stroke-width:0.001" />
- <line
- x1="9.75"
- y1="12.7"
- x2="15.875"
- y2="12.7"
- stroke="#000000"
- stroke-width="0.001"
- id="line102"
- style="stroke:#000000;stroke-width:0.001" />
- <path
- d="M 9.75,10.05 C 9.4738576,10.05 9.25,10.273858 9.25,10.55"
- id="path104"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <path
- d="M 16.375,10.55 C 16.375,10.273858 16.151142,10.05 15.875,10.05"
- id="path106"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <line
- x1="9.25"
- y1="10.55"
- x2="9.25"
- y2="12.2"
- stroke="#000000"
- stroke-width="0.001"
- id="line108"
- style="stroke:#000000;stroke-width:0.001" />
- <line
- x1="16.375"
- y1="10.55"
- x2="16.375"
- y2="12.2"
- stroke="#000000"
- stroke-width="0.001"
- id="line110"
- style="stroke:#000000;stroke-width:0.001" />
- <path
- d="M 9.25,12.2 C 9.25,12.476142 9.4738576,12.7 9.75,12.7"
- id="path112"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <path
- d="M 15.875,12.7 C 16.151142,12.7 16.375,12.476142 16.375,12.2"
- id="path114"
- style="fill:none;stroke:#000000;stroke-width:0.001" />
- <line
- x1="2.0250001"
- y1="1.825"
- x2="20.950001"
- y2="1.825"
- stroke="#000000"
- stroke-width="0.150"
- id="line116"
- style="stroke:#000000;stroke-width:0.15000001" />
- <rect
- width="1.391"
- height="3.2460001"
- x="8.2889996"
- y="2.836"
- id="rect118"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.391"
- height="3.2460001"
- x="8.2889996"
- y="2.836"
- id="rect120"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.113"
- height="0.37099999"
- x="8.4280005"
- y="3.0309999"
- id="rect122"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.113"
- height="0.37099999"
- x="8.4280005"
- y="3.402"
- id="rect124"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.113"
- height="0.37099999"
- x="8.4280005"
- y="3.773"
- id="rect126"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.113"
- height="0.37099999"
- x="8.4280005"
- y="4.1440001"
- id="rect128"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.69499999"
- height="0.223"
- x="8.4280005"
- y="4.5890002"
- id="rect130"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="9.4709997"
- cy="4.6259999"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse132"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="9.4709997"
- cy="4.6259999"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse134"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="9.4709997"
- cy="4.7740002"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse136"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="9.4709997"
- cy="4.7740002"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse138"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.167"
- height="0.148"
- x="9.1929998"
- y="4.6630001"
- id="rect140"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.167"
- height="0.148"
- x="9.1929998"
- y="4.6630001"
- id="rect142"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 8.521,5.108 L 8.521,5.92"
- id="path144"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 8.752,5.108 L 8.752,5.92"
- id="path146"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 8.984,5.108 L 8.984,5.92"
- id="path148"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.216,5.108 L 9.216,5.92"
- id="path150"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.448,5.108 L 9.448,5.92"
- id="path152"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.68,5.108 L 9.68,5.92"
- id="path154"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="8.011,6.36 8.289,5.804 8.289,6.082 9.68,6.082 9.68,5.804 10.051,6.36 8.011,6.36 "
- id="polygon156"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="8.011,6.36 8.289,5.804 8.289,6.082 9.68,6.082 9.68,5.804 10.051,6.36 8.011,6.36 "
- id="polygon158"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.67"
- height="5.0089998"
- x="16.247"
- y="3.0339999"
- id="rect160"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.67"
- height="5.0089998"
- x="16.247"
- y="3.0339999"
- id="rect162"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.67"
- height="5.0089998"
- x="16.247"
- y="3.0339999"
- id="rect164"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.336"
- height="2.003"
- x="16.414"
- y="3.201"
- id="rect166"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.336"
- height="2.003"
- x="16.414"
- y="3.201"
- id="rect168"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.336"
- height="2.003"
- x="16.414"
- y="3.201"
- id="rect170"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="3.5339999"
- x2="17.75"
- y2="3.5339999"
- stroke="#000000"
- stroke-width="0.010"
- id="line172"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.75"
- y1="3.868"
- x2="16.414"
- y2="3.868"
- stroke="#000000"
- stroke-width="0.010"
- id="line174"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="4.2020001"
- x2="17.75"
- y2="4.2020001"
- stroke="#000000"
- stroke-width="0.010"
- id="line176"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="4.5359998"
- x2="17.75"
- y2="4.5359998"
- stroke="#000000"
- stroke-width="0.010"
- id="line178"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.75"
- y1="4.8699999"
- x2="16.414"
- y2="4.8699999"
- stroke="#000000"
- stroke-width="0.010"
- id="line180"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91799998"
- height="0.50099999"
- x="16.414"
- y="5.3709998"
- id="rect182"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91799998"
- height="0.50099999"
- x="16.414"
- y="5.3709998"
- id="rect184"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91799998"
- height="0.50099999"
- x="16.414"
- y="5.3709998"
- id="rect186"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.247"
- y1="6.2059999"
- x2="17.917"
- y2="6.2059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line188"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="16.997999"
- y="6.3730001"
- id="rect190"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="16.997999"
- y="6.3730001"
- id="rect192"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="16.997999"
- y="6.3730001"
- id="rect194"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.332001"
- y="6.3730001"
- id="rect196"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.332001"
- y="6.3730001"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.332001"
- y="6.3730001"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.666"
- y="6.3730001"
- id="rect202"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.666"
- y="6.3730001"
- id="rect204"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.666"
- y="6.3730001"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.167"
- height="0.167"
- x="17.583"
- y="5.8720002"
- id="rect208"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.167"
- height="0.167"
- x="17.583"
- y="5.8720002"
- id="rect210"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.167"
- height="0.167"
- x="17.583"
- y="5.8720002"
- id="rect212"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="5.6209998"
- x2="17.332001"
- y2="5.6209998"
- stroke="#000000"
- stroke-width="0.010"
- id="line214"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.25"
- height="0.25"
- x="16.414"
- y="6.289"
- id="rect216"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.25"
- height="0.25"
- x="16.414"
- y="6.289"
- id="rect218"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.25"
- height="0.25"
- x="16.414"
- y="6.289"
- id="rect220"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.169"
- height="0.082999997"
- x="16.497999"
- y="4.954"
- id="rect222"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.169"
- height="0.082999997"
- x="16.497999"
- y="4.954"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.169"
- height="0.082999997"
- x="16.497999"
- y="4.954"
- id="rect226"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.497999"
- y1="5.454"
- x2="17.249001"
- y2="5.454"
- stroke="#000000"
- stroke-width="0.010"
- id="line228"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.249001"
- y1="5.5380001"
- x2="17.165001"
- y2="5.5380001"
- stroke="#000000"
- stroke-width="0.010"
- id="line230"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.497999"
- y1="5.5380001"
- x2="16.580999"
- y2="5.5380001"
- stroke="#000000"
- stroke-width="0.010"
- id="line232"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.417"
- height="0.082999997"
- x="16.664"
- y="5.454"
- id="rect234"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.417"
- height="0.082999997"
- x="16.664"
- y="5.454"
- id="rect236"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.417"
- height="0.082999997"
- x="16.664"
- y="5.454"
- id="rect238"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.497999"
- y1="5.1199999"
- x2="16.580999"
- y2="5.1199999"
- stroke="#000000"
- stroke-width="0.010"
- id="line240"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.664"
- y1="5.1199999"
- x2="16.747999"
- y2="5.1199999"
- stroke="#000000"
- stroke-width="0.010"
- id="line242"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.499001"
- y1="5.1199999"
- x2="17.666"
- y2="5.1199999"
- stroke="#000000"
- stroke-width="0.010"
- id="line244"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.9590001"
- x2="17.833"
- y2="7.9590001"
- stroke="#000000"
- stroke-width="0.010"
- id="line246"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.875"
- x2="16.330999"
- y2="7.875"
- stroke="#000000"
- stroke-width="0.010"
- id="line248"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.7919998"
- x2="17.833"
- y2="7.7919998"
- stroke="#000000"
- stroke-width="0.010"
- id="line250"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.7080002"
- x2="16.330999"
- y2="7.7080002"
- stroke="#000000"
- stroke-width="0.010"
- id="line252"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.625"
- x2="17.833"
- y2="7.625"
- stroke="#000000"
- stroke-width="0.010"
- id="line254"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.5409999"
- x2="16.330999"
- y2="7.5409999"
- stroke="#000000"
- stroke-width="0.010"
- id="line256"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.4580002"
- x2="17.833"
- y2="7.4580002"
- stroke="#000000"
- stroke-width="0.010"
- id="line258"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.3740001"
- x2="16.330999"
- y2="7.3740001"
- stroke="#000000"
- stroke-width="0.010"
- id="line260"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.2909999"
- x2="17.833"
- y2="7.2909999"
- stroke="#000000"
- stroke-width="0.010"
- id="line262"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.2069998"
- x2="16.330999"
- y2="7.2069998"
- stroke="#000000"
- stroke-width="0.010"
- id="line264"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.1240001"
- x2="17.833"
- y2="7.1240001"
- stroke="#000000"
- stroke-width="0.010"
- id="line266"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.04"
- x2="16.330999"
- y2="7.04"
- stroke="#000000"
- stroke-width="0.010"
- id="line268"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="6.9569998"
- x2="17.833"
- y2="6.9569998"
- stroke="#000000"
- stroke-width="0.010"
- id="line270"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="6.8730001"
- x2="16.330999"
- y2="6.8730001"
- stroke="#000000"
- stroke-width="0.010"
- id="line272"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.1"
- y1="1.85"
- x2="17.1"
- y2="3.05"
- stroke="#000000"
- stroke-width="0.100"
- id="line274"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.0570002"
- y1="1.823"
- x2="9.0310001"
- y2="2.836"
- stroke="#000000"
- stroke-width="0.100"
- id="line276"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.85"
- height="1.632"
- x="5.7249999"
- y="3.359"
- id="rect278"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="6.6500001"
- cy="4.9910002"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse280"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="6.6500001"
- cy="3.359"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse282"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="6.6500001"
- cy="3.359"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse284"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 7.575,3.359 L 7.575,4.991 C 7.575,5.141 7.161,5.263 6.65,5.263 C 6.139,5.263 5.725,5.141 5.725,4.991 L 5.725,3.359"
- id="path286"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="7.5999999"
- y1="4.1750002"
- x2="8.3000002"
- y2="4.1999998"
- stroke="#000000"
- stroke-width="0.100"
- id="line288"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="6.3410001"
- y="4.3000002"
- id="text290"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ADS</text>
- <text
- x="5.5120001"
- y="7.125"
- id="text292"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Windows Server 2003</text>
- <text
- x="6.5840001"
- y="7.9250002"
- id="text294"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">ADS Server</text>
- <text
- x="5.927"
- y="8.7250004"
- id="text296"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain Controller</text>
- <text
- x="15.605"
- y="0.67500001"
- id="text298"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba Domain</text>
- <text
- x="15.598"
- y="1.475"
- id="text300"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server</text>
- <line
- x1="2.075"
- y1="8.9750004"
- x2="20.9"
- y2="9"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.50,0.50"
- id="line302"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.5, 0.5" />
- <text
- x="6.5079999"
- y="9.6750002"
- id="text304"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Domain Services</text>
- <text
- x="5.7870002"
- y="1.395"
- id="text306"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network Configuration</text>
- <rect
- width="5.3499999"
- height="1.8"
- x="4.8249998"
- y="12.25"
- id="rect308"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.3499999"
- height="1.8"
- x="4.8249998"
- y="12.25"
- id="rect310"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="4.2750001"
- height="1.375"
- x="5.4250002"
- y="10.6"
- id="rect312"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.2750001"
- height="1.375"
- x="5.4250002"
- y="10.6"
- id="rect314"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.4749999"
- y="11.411"
- id="text316"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">CIFS Server</text>
- <text
- x="16.191999"
- y="9.6499996"
- id="text318"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Client Services</text>
- <rect
- width="2.575"
- height="1.125"
- x="16"
- y="12.975"
- id="rect320"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.575"
- height="1.125"
- x="16"
- y="12.975"
- id="rect322"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="16.599001"
- y="13.7"
- id="text324"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Winbind</text>
- <rect
- width="2.575"
- height="1.1"
- x="15.992"
- y="10.275"
- id="rect326"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.575"
- height="1.1"
- x="15.992"
- y="10.275"
- id="rect328"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.6070001"
- height="1.1"
- x="16.566999"
- y="11.6"
- id="rect330"
- style="fill:#c5c5c5;stroke:none;stroke-width:0" />
- <rect
- width="2.6070001"
- height="1.1"
- x="16.566999"
- y="11.6"
- id="rect332"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="16.724001"
- y="11.086"
- id="text334"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
- <text
- x="17.357"
- y="12.361"
- id="text336"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nmbd</text>
- <rect
- width="2.7179999"
- height="1.1"
- x="15.95"
- y="14.35"
- id="rect338"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.7179999"
- height="1.1"
- x="15.95"
- y="14.35"
- id="rect340"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="16.579"
- y="15.075"
- id="text342"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nss_ldap</text>
- <path
- d="M 19.015,13.314 C 19.392106,13.104482 19.629557,12.710441 19.638616,12.279135 C 19.647674,11.84783 19.426976,11.444167 19.059,11.219"
- id="path344"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.151,10.869 18.625,11.056 19.09,11.366 19.151,10.869 "
- id="polygon346"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.053,13.169 18.575,13.458 19.094,13.667 19.053,13.169 "
- id="polygon348"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 19.172,14.715 C 19.931775,14.326769 20.402308,13.537936 20.382916,12.684938 C 20.363525,11.83194 19.857632,11.065304 19.081,10.712"
- id="path350"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.154,10.406 18.617,10.559 19.062,10.897 19.154,10.406 "
- id="polygon352"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.146,14.531 18.716,14.889 19.26,15.018 19.146,14.531 "
- id="polygon354"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="15.338"
- y1="14.9"
- x2="10.912"
- y2="14.9"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.20,0.20"
- id="line356"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
- <polygon
- points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
- id="polygon358"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
- id="polygon360"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="10.912,14.65 10.412,14.9 10.912,15.15 10.912,14.65 "
- id="polygon362"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.912,14.65 10.412,14.9 10.912,15.15 10.912,14.65 "
- id="polygon364"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.787"
- y1="13.328"
- x2="15.338"
- y2="13.347"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.20,0.20"
- id="line366"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
- <polygon
- points="10.788,13.078 10.287,13.325 10.786,13.578 10.788,13.078 "
- id="polygon368"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.788,13.078 10.287,13.325 10.786,13.578 10.788,13.078 "
- id="polygon370"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="15.337,13.597 15.838,13.35 15.339,13.097 15.337,13.597 "
- id="polygon372"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="15.337,13.597 15.838,13.35 15.339,13.097 15.337,13.597 "
- id="polygon374"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="12.594"
- y="14.05"
- id="text376"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">UID/GID</text>
- <text
- x="12.425"
- y="14.65"
- id="text378"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Resolution</text>
- <rect
- width="5.4499998"
- height="1.05"
- x="4.8249998"
- y="14.375"
- id="rect380"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.4499998"
- height="1.05"
- x="4.8249998"
- y="14.375"
- id="rect382"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.2270002"
- y="13.011"
- id="text384"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Active Directory</text>
- <text
- x="6.0279999"
- y="13.611"
- id="text386"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">(Kerberos / LDAP)</text>
- <text
- x="5.9699998"
- y="15.136"
- id="text388"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Services For UNIX</text>
- <line
- x1="10.361"
- y1="10.714"
- x2="15.314"
- y2="10.524"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.20,0.20"
- id="line390"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
- <polygon
- points="10.352,10.464 9.862,10.733 10.371,10.964 10.352,10.464 "
- id="polygon392"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.352,10.464 9.862,10.733 10.371,10.964 10.352,10.464 "
- id="polygon394"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="15.323,10.773 15.813,10.504 15.304,10.274 15.323,10.773 "
- id="polygon396"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="15.323,10.773 15.813,10.504 15.304,10.274 15.323,10.773 "
- id="polygon398"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.795"
- y1="12.333"
- x2="15.355"
- y2="11.242"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.20,0.20"
- id="line400"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.2, 0.2" />
- <polygon
- points="10.737,12.09 10.309,12.449 10.853,12.576 10.737,12.09 "
- id="polygon402"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.737,12.09 10.309,12.449 10.853,12.576 10.737,12.09 "
- id="polygon404"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="15.413,11.485 15.841,11.126 15.297,10.999 15.413,11.485 "
- id="polygon406"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="15.413,11.485 15.841,11.126 15.297,10.999 15.413,11.485 "
- id="polygon408"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="11.411"
- y="11.325"
- id="text410"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Authentication</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="19.075001cm"
- height="15.897cm"
- viewBox="1.95 0.208 21.025 16.105"
- id="svg2">
- <defs
- id="defs453" />
- <rect
- width="10.1"
- height="13.95"
- x="2.7750001"
- y="2.125"
- id="rect4"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
- id="path6"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
- id="path8"
- style="fill:#ededed;stroke:none" />
- <rect
- width="11.5"
- height="12.55"
- x="2.075"
- y="2.825"
- id="rect10"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
- id="path12"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
- id="path14"
- style="fill:#ededed;stroke:none" />
- <line
- x1="2.7750001"
- y1="2.125"
- x2="12.875"
- y2="2.125"
- stroke="#000000"
- stroke-width="0.010"
- id="line16"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.7750001"
- y1="16.075001"
- x2="12.875"
- y2="16.075001"
- stroke="#000000"
- stroke-width="0.010"
- id="line18"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.775,2.125 C 2.3884007,2.125 2.075,2.4384007 2.075,2.825"
- id="path20"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 13.575,2.825 C 13.575,2.4384007 13.261599,2.125 12.875,2.125"
- id="path22"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.075"
- y1="2.825"
- x2="2.075"
- y2="15.375"
- stroke="#000000"
- stroke-width="0.010"
- id="line24"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.575"
- y1="2.825"
- x2="13.575"
- y2="15.375"
- stroke="#000000"
- stroke-width="0.010"
- id="line26"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.075,15.375 C 2.075,15.761599 2.3884007,16.075 2.775,16.075"
- id="path28"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 12.875,16.075 C 13.261599,16.075 13.575,15.761599 13.575,15.375"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="5.533"
- height="13.95"
- x="14.717"
- y="2.1500001"
- id="rect32"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
- id="path34"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
- id="path36"
- style="fill:#ededed;stroke:none" />
- <rect
- width="6.9320002"
- height="12.55"
- x="14.018"
- y="2.8499999"
- id="rect38"
- style="fill:#ededed;stroke:none;stroke-width:0" />
- <path
- d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
- id="path40"
- style="fill:#ededed;stroke:none" />
- <path
- d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
- id="path42"
- style="fill:#ededed;stroke:none" />
- <line
- x1="14.717"
- y1="2.1500001"
- x2="20.25"
- y2="2.1500001"
- stroke="#000000"
- stroke-width="0.010"
- id="line44"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.717"
- y1="16.1"
- x2="20.25"
- y2="16.1"
- stroke="#000000"
- stroke-width="0.010"
- id="line46"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.717,2.15 C 14.330791,2.1505517 14.018,2.4637909 14.018,2.85"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 20.95,2.85 C 20.95,2.4634007 20.636599,2.15 20.25,2.15"
- id="path50"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.018"
- y1="2.8499999"
- x2="14.018"
- y2="15.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line52"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.950001"
- y1="2.8499999"
- x2="20.950001"
- y2="15.4"
- stroke="#000000"
- stroke-width="0.010"
- id="line54"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.018,15.4 C 14.018,15.786209 14.330791,16.099448 14.717,16.1"
- id="path56"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 20.25,16.1 C 20.636599,16.1 20.95,15.786599 20.95,15.4"
- id="path58"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="4.9749999"
- height="4.625"
- x="10.8"
- y="10.877"
- id="rect60"
- style="fill:#b5b5b5;stroke:none;stroke-width:0" />
- <path
- d="M 10.8,10.877 C 10.523858,10.877 10.3,11.100858 10.3,11.377"
- id="path62"
- style="fill:#b5b5b5;stroke:none" />
- <path
- d="M 16.275,11.377 C 16.275,11.100858 16.051142,10.877 15.775,10.877"
- id="path64"
- style="fill:#b5b5b5;stroke:none" />
- <rect
- width="5.9749999"
- height="3.625"
- x="10.3"
- y="11.377"
- id="rect66"
- style="fill:#b5b5b5;stroke:none;stroke-width:0" />
- <path
- d="M 10.3,15.002 C 10.3,15.278142 10.523858,15.502 10.8,15.502"
- id="path68"
- style="fill:#b5b5b5;stroke:none" />
- <path
- d="M 15.775,15.502 C 16.051142,15.502 16.275,15.278142 16.275,15.002"
- id="path70"
- style="fill:#b5b5b5;stroke:none" />
- <line
- x1="10.8"
- y1="10.877"
- x2="15.775"
- y2="10.877"
- stroke="#000000"
- stroke-width="0.010"
- id="line72"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.8"
- y1="15.502"
- x2="15.775"
- y2="15.502"
- stroke="#000000"
- stroke-width="0.010"
- id="line74"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.8,10.877 C 10.523858,10.877 10.3,11.100858 10.3,11.377"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 16.275,11.377 C 16.275,11.100858 16.051142,10.877 15.775,10.877"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.3"
- y1="11.377"
- x2="10.3"
- y2="15.002"
- stroke="#000000"
- stroke-width="0.010"
- id="line80"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.275"
- y1="11.377"
- x2="16.275"
- y2="15.002"
- stroke="#000000"
- stroke-width="0.010"
- id="line82"
- style="stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.3,15.002 C 10.3,15.278142 10.523858,15.502 10.8,15.502"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.775,15.502 C 16.051142,15.502 16.275,15.278142 16.275,15.002"
- id="path86"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.0250001"
- y1="1.825"
- x2="20.950001"
- y2="1.825"
- stroke="#000000"
- stroke-width="0.150"
- id="line88"
- style="stroke:#000000;stroke-width:0.15000001" />
- <rect
- width="1.391"
- height="3.2460001"
- x="5.539"
- y="3.161"
- id="rect90"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.391"
- height="3.2460001"
- x="5.539"
- y="3.161"
- id="rect92"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.113"
- height="0.37099999"
- x="5.678"
- y="3.3559999"
- id="rect94"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.113"
- height="0.37099999"
- x="5.678"
- y="3.727"
- id="rect96"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.113"
- height="0.37099999"
- x="5.678"
- y="4.098"
- id="rect98"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.113"
- height="0.37099999"
- x="5.678"
- y="4.4689999"
- id="rect100"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.69499999"
- height="0.223"
- x="5.678"
- y="4.914"
- id="rect102"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="6.7210002"
- cy="4.9510002"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse104"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="6.7210002"
- cy="4.9510002"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse106"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="6.7210002"
- cy="5.099"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse108"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="6.7210002"
- cy="5.099"
- rx="0.048999999"
- ry="0.048999999"
- id="ellipse110"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.167"
- height="0.148"
- x="6.4429998"
- y="4.9879999"
- id="rect112"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.167"
- height="0.148"
- x="6.4429998"
- y="4.9879999"
- id="rect114"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 5.771,5.433 L 5.771,6.245"
- id="path116"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.002,5.433 L 6.002,6.245"
- id="path118"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.234,5.433 L 6.234,6.245"
- id="path120"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.466,5.433 L 6.466,6.245"
- id="path122"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.698,5.433 L 6.698,6.245"
- id="path124"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.93,5.433 L 6.93,6.245"
- id="path126"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="5.261,6.685 5.539,6.129 5.539,6.407 6.93,6.407 6.93,6.129 7.301,6.685 5.261,6.685 "
- id="polygon128"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="5.261,6.685 5.539,6.129 5.539,6.407 6.93,6.407 6.93,6.129 7.301,6.685 5.261,6.685 "
- id="polygon130"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.354"
- height="3.158"
- x="8.8369999"
- y="3.2119999"
- id="rect132"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.354"
- height="3.158"
- x="8.8369999"
- y="3.2119999"
- id="rect134"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.0829999"
- height="0.361"
- x="8.9720001"
- y="3.402"
- id="rect136"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.0829999"
- height="0.361"
- x="8.9720001"
- y="3.763"
- id="rect138"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.0829999"
- height="0.361"
- x="8.9720001"
- y="4.1240001"
- id="rect140"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.0829999"
- height="0.361"
- x="8.9720001"
- y="4.4850001"
- id="rect142"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.67699999"
- height="0.21699999"
- x="8.9720001"
- y="4.9180002"
- id="rect144"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="9.9879999"
- cy="4.954"
- rx="0.046999998"
- ry="0.046999998"
- id="ellipse146"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="9.9879999"
- cy="4.954"
- rx="0.046999998"
- ry="0.046999998"
- id="ellipse148"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="9.9879999"
- cy="5.099"
- rx="0.046999998"
- ry="0.046999998"
- id="ellipse150"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="9.9879999"
- cy="5.099"
- rx="0.046999998"
- ry="0.046999998"
- id="ellipse152"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.162"
- height="0.14399999"
- x="9.717"
- y="4.9899998"
- id="rect154"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.162"
- height="0.14399999"
- x="9.717"
- y="4.9899998"
- id="rect156"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.063,5.423 L 9.063,6.213"
- id="path158"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.288,5.423 L 9.288,6.213"
- id="path160"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.514,5.423 L 9.514,6.213"
- id="path162"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.739,5.423 L 9.739,6.213"
- id="path164"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.965,5.423 L 9.965,6.213"
- id="path166"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.191,5.423 L 10.191,6.213"
- id="path168"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="8.566,6.642 8.837,6.1 8.837,6.371 10.191,6.371 10.191,6.1 10.552,6.642 8.566,6.642 "
- id="polygon170"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="8.566,6.642 8.837,6.1 8.837,6.371 10.191,6.371 10.191,6.1 10.552,6.642 8.566,6.642 "
- id="polygon172"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.67"
- height="5.0089998"
- x="16.247"
- y="3.0339999"
- id="rect174"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.67"
- height="5.0089998"
- x="16.247"
- y="3.0339999"
- id="rect176"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.67"
- height="5.0089998"
- x="16.247"
- y="3.0339999"
- id="rect178"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.336"
- height="2.003"
- x="16.414"
- y="3.201"
- id="rect180"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.336"
- height="2.003"
- x="16.414"
- y="3.201"
- id="rect182"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.336"
- height="2.003"
- x="16.414"
- y="3.201"
- id="rect184"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="3.5339999"
- x2="17.75"
- y2="3.5339999"
- stroke="#000000"
- stroke-width="0.010"
- id="line186"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.75"
- y1="3.868"
- x2="16.414"
- y2="3.868"
- stroke="#000000"
- stroke-width="0.010"
- id="line188"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="4.2020001"
- x2="17.75"
- y2="4.2020001"
- stroke="#000000"
- stroke-width="0.010"
- id="line190"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="4.5359998"
- x2="17.75"
- y2="4.5359998"
- stroke="#000000"
- stroke-width="0.010"
- id="line192"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.75"
- y1="4.8699999"
- x2="16.414"
- y2="4.8699999"
- stroke="#000000"
- stroke-width="0.010"
- id="line194"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.91799998"
- height="0.50099999"
- x="16.414"
- y="5.3709998"
- id="rect196"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.91799998"
- height="0.50099999"
- x="16.414"
- y="5.3709998"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.91799998"
- height="0.50099999"
- x="16.414"
- y="5.3709998"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.247"
- y1="6.2059999"
- x2="17.917"
- y2="6.2059999"
- stroke="#000000"
- stroke-width="0.010"
- id="line202"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="16.997999"
- y="6.3730001"
- id="rect204"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="16.997999"
- y="6.3730001"
- id="rect206"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="16.997999"
- y="6.3730001"
- id="rect208"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.332001"
- y="6.3730001"
- id="rect210"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.332001"
- y="6.3730001"
- id="rect212"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.332001"
- y="6.3730001"
- id="rect214"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.666"
- y="6.3730001"
- id="rect216"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.666"
- y="6.3730001"
- id="rect218"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.082999997"
- height="0.082999997"
- x="17.666"
- y="6.3730001"
- id="rect220"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.167"
- height="0.167"
- x="17.583"
- y="5.8720002"
- id="rect222"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.167"
- height="0.167"
- x="17.583"
- y="5.8720002"
- id="rect224"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.167"
- height="0.167"
- x="17.583"
- y="5.8720002"
- id="rect226"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.414"
- y1="5.6209998"
- x2="17.332001"
- y2="5.6209998"
- stroke="#000000"
- stroke-width="0.010"
- id="line228"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.25"
- height="0.25"
- x="16.414"
- y="6.289"
- id="rect230"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.25"
- height="0.25"
- x="16.414"
- y="6.289"
- id="rect232"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.25"
- height="0.25"
- x="16.414"
- y="6.289"
- id="rect234"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.169"
- height="0.082999997"
- x="16.497999"
- y="4.954"
- id="rect236"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.169"
- height="0.082999997"
- x="16.497999"
- y="4.954"
- id="rect238"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.169"
- height="0.082999997"
- x="16.497999"
- y="4.954"
- id="rect240"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.497999"
- y1="5.454"
- x2="17.249001"
- y2="5.454"
- stroke="#000000"
- stroke-width="0.010"
- id="line242"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.249001"
- y1="5.5380001"
- x2="17.165001"
- y2="5.5380001"
- stroke="#000000"
- stroke-width="0.010"
- id="line244"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.497999"
- y1="5.5380001"
- x2="16.580999"
- y2="5.5380001"
- stroke="#000000"
- stroke-width="0.010"
- id="line246"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.417"
- height="0.082999997"
- x="16.664"
- y="5.454"
- id="rect248"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.417"
- height="0.082999997"
- x="16.664"
- y="5.454"
- id="rect250"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.417"
- height="0.082999997"
- x="16.664"
- y="5.454"
- id="rect252"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.497999"
- y1="5.1199999"
- x2="16.580999"
- y2="5.1199999"
- stroke="#000000"
- stroke-width="0.010"
- id="line254"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.664"
- y1="5.1199999"
- x2="16.747999"
- y2="5.1199999"
- stroke="#000000"
- stroke-width="0.010"
- id="line256"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.499001"
- y1="5.1199999"
- x2="17.666"
- y2="5.1199999"
- stroke="#000000"
- stroke-width="0.010"
- id="line258"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.9590001"
- x2="17.833"
- y2="7.9590001"
- stroke="#000000"
- stroke-width="0.010"
- id="line260"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.875"
- x2="16.330999"
- y2="7.875"
- stroke="#000000"
- stroke-width="0.010"
- id="line262"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.7919998"
- x2="17.833"
- y2="7.7919998"
- stroke="#000000"
- stroke-width="0.010"
- id="line264"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.7080002"
- x2="16.330999"
- y2="7.7080002"
- stroke="#000000"
- stroke-width="0.010"
- id="line266"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.625"
- x2="17.833"
- y2="7.625"
- stroke="#000000"
- stroke-width="0.010"
- id="line268"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.5409999"
- x2="16.330999"
- y2="7.5409999"
- stroke="#000000"
- stroke-width="0.010"
- id="line270"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.4580002"
- x2="17.833"
- y2="7.4580002"
- stroke="#000000"
- stroke-width="0.010"
- id="line272"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.3740001"
- x2="16.330999"
- y2="7.3740001"
- stroke="#000000"
- stroke-width="0.010"
- id="line274"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.2909999"
- x2="17.833"
- y2="7.2909999"
- stroke="#000000"
- stroke-width="0.010"
- id="line276"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.2069998"
- x2="16.330999"
- y2="7.2069998"
- stroke="#000000"
- stroke-width="0.010"
- id="line278"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="7.1240001"
- x2="17.833"
- y2="7.1240001"
- stroke="#000000"
- stroke-width="0.010"
- id="line280"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="7.04"
- x2="16.330999"
- y2="7.04"
- stroke="#000000"
- stroke-width="0.010"
- id="line282"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.330999"
- y1="6.9569998"
- x2="17.833"
- y2="6.9569998"
- stroke="#000000"
- stroke-width="0.010"
- id="line284"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.833"
- y1="6.8730001"
- x2="16.330999"
- y2="6.8730001"
- stroke="#000000"
- stroke-width="0.010"
- id="line286"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.1"
- y1="1.85"
- x2="17.1"
- y2="3.05"
- stroke="#000000"
- stroke-width="0.100"
- id="line288"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.2579999"
- y1="1.823"
- x2="6.2810001"
- y2="3.161"
- stroke="#000000"
- stroke-width="0.100"
- id="line290"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="9.5249996"
- y1="1.85"
- x2="9.559"
- y2="3.2119999"
- stroke="#000000"
- stroke-width="0.100"
- id="line292"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.85"
- height="1.632"
- x="2.925"
- y="3.359"
- id="rect294"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="3.8499999"
- cy="4.9910002"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse296"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.8499999"
- cy="3.359"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse298"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="3.8499999"
- cy="3.359"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse300"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 4.775,3.359 L 4.775,4.991 C 4.775,5.141 4.361,5.263 3.85,5.263 C 3.339,5.263 2.925,5.141 2.925,4.991 L 2.925,3.359"
- id="path302"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.85"
- height="1.632"
- x="11.008"
- y="3.3699999"
- id="rect304"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <ellipse
- cx="11.932"
- cy="5.0019999"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse306"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="11.932"
- cy="3.3699999"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse308"
- style="fill:#ffffff;stroke:none" />
- <ellipse
- cx="11.932"
- cy="3.3699999"
- rx="0.92500001"
- ry="0.27200001"
- id="ellipse310"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 12.857,3.37 L 12.857,5.002 C 12.857,5.152 12.443,5.274 11.932,5.274 C 11.422,5.274 11.008,5.152 11.008,5.002 L 11.008,3.37"
- id="path312"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="4.8000002"
- y1="4.1750002"
- x2="5.5"
- y2="4.1999998"
- stroke="#000000"
- stroke-width="0.100"
- id="line314"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.259"
- y1="4.1490002"
- x2="10.959"
- y2="4.1739998"
- stroke="#000000"
- stroke-width="0.100"
- id="line316"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="3.4660001"
- y="4.3000002"
- id="text318"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="3.3929999"
- y="4.8000002"
- id="text320"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Master</text>
- <text
- x="11.541"
- y="4.3000002"
- id="text322"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <text
- x="11.555"
- y="4.8000002"
- id="text324"
- style="font-size:0.5px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Slave</text>
- <path
- d="M 10.533,3.038 C 8.7210597,2.042993 6.5088646,2.1244423 4.775,3.25"
- id="path326"
- style="fill:none;stroke:#585858;stroke-width:0.1;stroke-dasharray:0.5, 0.15, 0.05, 0.15, 0.05, 0.15" />
- <polygon
- points="10.405,3.221 10.959,3.297 10.687,2.808 10.405,3.221 "
- id="polygon328"
- style="fill:#585858;stroke:none;stroke-width:0.1" />
- <text
- x="3.0420001"
- y="6.0999999"
- id="text330"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="3.2969999"
- y="6.9000001"
- id="text332"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC</text>
- <text
- x="11.317"
- y="6.0749998"
- id="text334"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba</text>
- <text
- x="11.574"
- y="6.875"
- id="text336"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">BDC</text>
- <text
- x="15.605"
- y="0.67500001"
- id="text338"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Samba Domain</text>
- <text
- x="15.598"
- y="1.475"
- id="text340"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Member Server</text>
- <line
- x1="2.075"
- y1="8.9750004"
- x2="20.9"
- y2="9"
- stroke="#000000"
- stroke-width="0.100"
- stroke-dasharray="0.50,0.50"
- id="line342"
- style="stroke:#000000;stroke-width:0.1;stroke-dasharray:0.5, 0.5" />
- <text
- x="7.7189999"
- y="9.6750002"
- id="text344"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">PDC/BDC Services</text>
- <text
- x="5.7870002"
- y="1.395"
- id="text346"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Network Configuration</text>
- <rect
- width="2.575"
- height="1.1"
- x="7.4000001"
- y="13.025"
- id="rect348"
- style="fill:#b9b9b9;stroke:none;stroke-width:0" />
- <rect
- width="2.575"
- height="1.1"
- x="7.4000001"
- y="13.025"
- id="rect350"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="8.0240002"
- y="13.775"
- id="text352"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#010101;font-family:arial">Winbind</text>
- <rect
- width="2.575"
- height="1.1"
- x="8.0679998"
- y="14.4"
- id="rect354"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.575"
- height="1.1"
- x="8.0679998"
- y="14.4"
- id="rect356"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="8.8870001"
- y="15.1"
- id="text358"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">LDAP</text>
- <rect
- width="2.575"
- height="1.1"
- x="8.0679998"
- y="10.325"
- id="rect360"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.575"
- height="1.1"
- x="8.0679998"
- y="10.325"
- id="rect362"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.6070001"
- height="1.1"
- x="7.4180002"
- y="11.675"
- id="rect364"
- style="fill:#c6c6c6;stroke:none;stroke-width:0" />
- <rect
- width="2.6070001"
- height="1.1"
- x="7.4180002"
- y="11.675"
- id="rect366"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="8.7989998"
- y="11.136"
- id="text368"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
- <text
- x="8.2069998"
- y="12.436"
- id="text370"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nmbd</text>
- <text
- x="16.143"
- y="9.6999998"
- id="text372"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Client Services</text>
- <rect
- width="2.575"
- height="1.125"
- x="16"
- y="12.975"
- id="rect374"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.575"
- height="1.125"
- x="16"
- y="12.975"
- id="rect376"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="16.599001"
- y="13.7"
- id="text378"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Winbind</text>
- <rect
- width="2.575"
- height="1.1"
- x="15.992"
- y="10.275"
- id="rect380"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.575"
- height="1.1"
- x="15.992"
- y="10.275"
- id="rect382"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.608"
- height="1.102"
- x="16.517"
- y="11.625"
- id="rect384"
- style="fill:#c5c5c5;stroke:none;stroke-width:0" />
- <rect
- width="2.608"
- height="1.102"
- x="16.517"
- y="11.625"
- id="rect386"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="16.724001"
- y="11.086"
- id="text388"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">smbd</text>
- <text
- x="17.306999"
- y="12.386"
- id="text390"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nmbd</text>
- <rect
- width="2.7179999"
- height="1.1"
- x="15.95"
- y="14.35"
- id="rect392"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.7179999"
- height="1.1"
- x="15.95"
- y="14.35"
- id="rect394"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="16.579"
- y="15.075"
- id="text396"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nss_ldap</text>
- <rect
- width="2.717"
- height="1.1"
- x="4.1680002"
- y="14.375"
- id="rect398"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="2.717"
- height="1.1"
- x="4.1680002"
- y="14.375"
- id="rect400"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="4.796"
- y="15.1"
- id="text402"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">nss_ldap</text>
- <path
- d="M 7.56,11.075 C 6.4745981,11.601642 5.7241236,12.635796 5.56,13.831"
- id="path404"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.616,11.277 8.02,10.89 7.468,10.799 7.616,11.277 "
- id="polygon406"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="5.268,13.829 5.526,14.325 5.768,13.821 5.268,13.829 "
- id="polygon408"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="7.4349999"
- y1="14.937"
- x2="7.5180001"
- y2="14.938"
- stroke="#000000"
- stroke-width="0.100"
- id="line410"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.44,14.687 6.935,14.926 7.43,15.187 7.44,14.687 "
- id="polygon412"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="7.512,15.188 8.018,14.949 7.523,14.688 7.512,15.188 "
- id="polygon414"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 19.015,13.314 C 19.392106,13.104482 19.629557,12.710441 19.638616,12.279135 C 19.647674,11.84783 19.426976,11.444167 19.059,11.219"
- id="path416"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.151,10.869 18.625,11.056 19.09,11.366 19.151,10.869 "
- id="polygon418"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.053,13.169 18.575,13.458 19.094,13.667 19.053,13.169 "
- id="polygon420"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 19.172,14.715 C 19.931775,14.326769 20.402308,13.537936 20.382916,12.684938 C 20.363525,11.83194 19.857632,11.065304 19.081,10.712"
- id="path422"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.154,10.406 18.617,10.559 19.062,10.897 19.154,10.406 "
- id="polygon424"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.146,14.531 18.716,14.889 19.26,15.018 19.146,14.531 "
- id="polygon426"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="15.338"
- y1="14.9"
- x2="11.337"
- y2="14.9"
- stroke="#000000"
- stroke-width="0.100"
- id="line428"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
- id="polygon430"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="15.338,15.15 15.838,14.9 15.338,14.65 15.338,15.15 "
- id="polygon432"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.337,14.65 10.837,14.9 11.337,15.15 11.337,14.65 "
- id="polygon434"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="11.337,14.65 10.837,14.9 11.337,15.15 11.337,14.65 "
- id="polygon436"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <line
- x1="11.321"
- y1="11.572"
- x2="15.379"
- y2="13.132"
- stroke="#000000"
- stroke-width="0.100"
- id="line438"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.411,11.338 10.854,11.392 11.231,11.805 11.411,11.338 "
- id="polygon440"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="11.411,11.338 10.854,11.392 11.231,11.805 11.411,11.338 "
- id="polygon442"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="15.289,13.366 15.846,13.312 15.469,12.899 15.289,13.366 "
- id="polygon444"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="15.289,13.366 15.846,13.312 15.469,12.899 15.289,13.366 "
- id="polygon446"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="12.719"
- y="13.45"
- id="text448"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">UID/GID</text>
- <text
- x="12.55"
- y="14.05"
- id="text450"
- style="font-size:0.60000002px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:arial">Resolution</text>
-</svg>
+++ /dev/null
-<?xml version="1.0"?>\r
-<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">\r
-\r
-<book id="S3bE"\r
- xmlns:xi="http://www.w3.org/2003/XInclude">\r
- <title>Samba-3 by Example</title>\r
- <subtitle>Practical Exercises in Successful Samba Deployment</subtitle>\r
- <bookinfo>\r
- <authorgroup>\r
- <author>&person.jht;</author>\r
- </authorgroup>\r
- <pubdate>July, 2006</pubdate>\r
- </bookinfo>\r
-\r
- <?latex \clearpage ?>\r
- <?latex \setcounter{page}{7} ?>\r
-\r
- <xi:include href="SBE-inside-cover.xml"/>\r
- <xi:include href="SBE-acknowledgements.xml"/>\r
- <?latex \cleardoublepage ?>\r
-\r
- <toc/>\r
- <?latex \cleardoublepage ?>\r
- <?latex \listofexamples ?>\r
- <?latex \cleardoublepage ?>\r
- <lot/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-foreword.xml"/>\r
- <xi:include href="SBE-preface.xml"/>\r
-<!-- Chapters -->\r
-\r
-<part id="ExNetworks">\r
-<title>Example Network Configurations</title>\r
-<partintro>\r
-<title>Example Network Configurations</title>\r
-\r
-<?latex \pagenumbering{arabic} ?>\r
-\r
-<para>\r
-This section of <emphasis>Samba-3 by Example</emphasis> provides example network\r
-configurations that can be copied, or modified as needed, and deployed as-is.\r
-The contents have been marginally updated to reflect changes made in Samba=3.0.23.\r
-</para>\r
-\r
-<para>\r
-Best use can be made of this book by finding in this section the network design and\r
-layout that best approximates your estimated needs. It is recommended that you will\r
-implement the design pattern exactly as it appears, then after the installation has\r
-been proven to work make any changes or modifications needed at your site.\r
-</para>\r
-\r
-<para>\r
-The examples have been tested with Red Hat Fedora Core 2, Novell SUSE Linux Professional\r
-9.3 and Novell SUSE Linux Enterprise Server (SLES) 9. The principals of implementation\r
-apply to all Linux and UNIX systems in general, though some system files and tools will \r
-be different and the location of some Samba file locations will be different since these \r
-are determined by the person who packages Samba for each platform.\r
-</para>\r
-\r
-<para>\r
-If you are deploying Samba is a mission-critical environment, or if you simply want\r
-to save time and get your Samba network operational with minimal fuss, there is the\r
-option to purchase commercial, professional, Samba support. Information regarding\r
-commercial support options may be obtained from the commercial\r
-<ulink url="http://www.samba.org/samba/support/">support</ulink> pages from \r
-the Samba web site.\r
-</para>\r
-\r
-</partintro>\r
-\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-SimpleOfficeServer.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-TheSmallOffice.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-SecureOfficeServer.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-500UserNetwork.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-MakingHappyUsers.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-2000UserNetwork.xml"/>\r
- <?latex \cleardoublepage ?>\r
-\r
-</part>\r
-\r
-<part id="DMSMig">\r
-<title>Domain Members, Updating Samba and Migration</title>\r
-<partintro>\r
-<title>Domain Members, Updating Samba and Migration</title>\r
-\r
-<para>\r
-This section <emphasis>Samba-3 by Example</emphasis> covers two main topics: How to add
-Samba Domain Member Servers and Samba Domain Member Clients to a Samba domain, the other
-subject is that of how to migrate from and NT4 Domain, a NetWare server, or from an earlier
-Samba version to environments that use the most recent Samba release.
-</para>
-
-<para>
-Those who are making use of the chapter on Adding UNIX clients and servers running Samba\r
-to a Samba or a Windows networking domain may also benefit by referring to the book\r
-<emphasis>The Official Samba-3 HOWTO and Reference Guide.</emphasis>\r
-</para>\r
-\r
-</partintro>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-AddingUNIXClients.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-UpgradingSamba.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-MigrateNT4Samba3.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-MigrateNW4Samba3.xml"/>\r
- <?latex \cleardoublepage ?>\r
-</part>\r
-\r
-<part id="RefSection">\r
-<title>Reference Section</title>\r
-<partintro>\r
-<title>Reference Section</title>\r
-\r
-<para>\r
-This section <emphasis>Samba-3 by Example</emphasis> provides important reference material\r
-that may help you to solve network performance issues, to answer some of the critiques\r
-published regarding Samba, or just to gain a more broad understanding of how Samba can\r
-play in a Windows networking world.\r
-</para>\r
-\r
-</partintro>
-
- <?latex \cleardoublepage ?>
- <xi:include href="SBE-DomainAppsSupport.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="SBE-HighAvailability.xml"/>
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-Support.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-Appendix1.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="SBE-Appendix2.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <xi:include href="gpl-3.0.xml"/>\r
- <?latex \cleardoublepage ?>\r
-\r
-</part>\r
-\r
- <xi:include href="SBE-glossary.xml"/>\r
- <?latex \cleardoublepage ?>\r
- <index/>\r
-\r
-</book>\r
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<chapter id="AccessControls">
-<chapterinfo>
- &author.jht;
- &author.jeremy;
- <author>&person.jelmer;<contrib>drawing</contrib></author>
- <pubdate>May 10, 2003</pubdate>
-</chapterinfo>
-<title>File, Directory, and Share Access Controls</title>
-
-<para>
-<indexterm><primary>ACLs</primary></indexterm>
-<indexterm><primary>share</primary></indexterm>
-<indexterm><primary>network access controls</primary></indexterm>
-<indexterm><primary>unauthorized access</primary></indexterm>
-Advanced MS Windows users are frequently perplexed when file, directory, and share manipulation of
-resources shared via Samba do not behave in the manner they might expect. MS Windows network
-administrators are often confused regarding network access controls and how to
-provide users with the access they need while protecting resources from unauthorized access.
-</para>
-
-<para>
-<indexterm><primary>file access permissions</primary></indexterm>
-<indexterm><primary>directory access permissions</primary></indexterm>
-Many UNIX administrators are unfamiliar with the MS Windows environment and in particular
-have difficulty in visualizing what the MS Windows user wishes to achieve in attempts to set file
-and directory access permissions.
-</para>
-
-<para>
-<indexterm><primary>bridge</primary></indexterm>
-<indexterm><primary>directory controls</primary></indexterm>
-<indexterm><primary>directory permissions</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-The problem lies in the differences in how file and directory permissions and controls work
-between the two environments. This difference is one that Samba cannot completely hide, even
-though it does try to bridge the chasm to a degree.
-</para>
-
-<para>
-<indexterm><primary>Extended Attributes</primary></indexterm>
-<indexterm><primary>ACLs</primary><secondary>POSIX</secondary></indexterm>
-<indexterm><primary>Access Control List</primary></indexterm>
-<indexterm><primary>commercial Linux products</primary></indexterm>
-POSIX Access Control List technology has been available (along with extended attributes)
-for UNIX for many years, yet there is little evidence today of any significant use. This
-explains to some extent the slow adoption of ACLs into commercial Linux products. MS Windows
-administrators are astounded at this, given that ACLs were a foundational capability of the now
-decade-old MS Windows NT operating system.
-</para>
-
-<para>
-<indexterm><primary>network administrator</primary></indexterm>
-The purpose of this chapter is to present each of the points of control that are possible with
-Samba in the hope that this will help the network administrator to find the optimum method
-for delivering the best environment for MS Windows desktop users.
-</para>
-
-<para>
-<indexterm><primary>interoperability</primary></indexterm>
-<indexterm><primary>data interchange</primary></indexterm>
-This is an opportune point to mention that Samba was created to provide a means of interoperability
-and interchange of data between differing operating environments. Samba has no intent to change
-UNIX/Linux into a platform like MS Windows. Instead the purpose was and is to provide a sufficient
-level of exchange of data between the two environments. What is available today extends well
-beyond early plans and expectations, yet the gap continues to shrink.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
- <para>
- Samba offers much flexibility in file system access management. These are the key access control
- facilities present in Samba today:
- </para>
-
- <itemizedlist>
- <title>Samba Access Control Facilities</title>
- <listitem><para>
- <indexterm><primary>permissions</primary><secondary>UNIX file and directory</secondary></indexterm>
- <emphasis>UNIX File and Directory Permissions</emphasis>
- </para>
-
- <para>
-<indexterm><primary>UNIX file system access controls</primary></indexterm>
-<indexterm><primary>access controls</primary></indexterm>
-<indexterm><primary>permissions and controls</primary></indexterm>
- Samba honors and implements UNIX file system access controls. Users
- who access a Samba server will do so as a particular MS Windows user.
- This information is passed to the Samba server as part of the logon or
- connection setup process. Samba uses this user identity to validate
- whether or not the user should be given access to file system resources
- (files and directories). This chapter provides an overview for those
- to whom the UNIX permissions and controls are a little strange or unknown.
- </para>
- </listitem>
-
- <listitem><para>
- <emphasis>Samba Share Definitions</emphasis>
- </para>
-
- <para>
-<indexterm><primary>share settings</primary></indexterm>
- In configuring share settings and controls in the &smb.conf; file,
- the network administrator can exercise overrides to native file
- system permissions and behaviors. This can be handy and convenient
- to effect behavior that is more like what MS Windows NT users expect,
- but it is seldom the <emphasis>best</emphasis> way to achieve this.
- The basic options and techniques are described herein.
- </para>
- </listitem>
-
- <listitem><para>
- <emphasis>Samba Share ACLs</emphasis>
- <indexterm><primary>ACLs</primary><secondary>share</secondary></indexterm>
- </para>
-
- <para>
-<indexterm><primary>ACLs on shares</primary></indexterm>
- Just as it is possible in MS Windows NT to set ACLs on shares
- themselves, so it is possible to do in Samba.
- Few people make use of this facility, yet it remains one of the
- easiest ways to affect access controls (restrictions) and can often
- do so with minimum invasiveness compared with other methods.
- </para>
- </listitem>
-
- <listitem><para>
- <indexterm><primary>ACLs</primary><secondary>POSIX</secondary></indexterm>
- <indexterm><primary>ACLs</primary><secondary>Windows</secondary></indexterm>
- <emphasis>MS Windows ACLs through UNIX POSIX ACLs</emphasis>
- </para>
-
- <para>
-<indexterm><primary>native ACLs</primary></indexterm>
- The use of POSIX ACLs on UNIX/Linux is possible only if the underlying
- operating system supports them. If not, then this option will not be
- available to you. Current UNIX technology platforms have native support
- for POSIX ACLs. There are patches for the Linux kernel that also provide
- this support. Sadly, few Linux platforms ship today with native ACLs and
- extended attributes enabled. This chapter has pertinent information
- for users of platforms that support them.
- </para>
- </listitem>
- </itemizedlist>
-
-</sect1>
-
-<sect1>
-<title>File System Access Controls</title>
-
-<para>
-Perhaps the most important recognition to be made is the simple fact that MS Windows NT4/200x/XP
-implement a totally divergent file system technology from what is provided in the UNIX operating system
-environment. First we consider what the most significant differences are, then we look
-at how Samba helps to bridge the differences.
-</para>
-
- <sect2>
- <title>MS Windows NTFS Comparison with UNIX File Systems</title>
-
- <para>
- <indexterm><primary>NTFS</primary></indexterm>
- <indexterm><primary>File System</primary></indexterm>
- <indexterm><primary>File System</primary><secondary>UNIX</secondary></indexterm>
- <indexterm><primary>File System</primary><secondary>Windows</secondary></indexterm>
- Samba operates on top of the UNIX file system. This means it is subject to UNIX file system conventions
- and permissions. It also means that if the MS Windows networking environment requires file system
- behavior, that differs from UNIX file system behavior then somehow Samba is responsible for emulating
- that in a transparent and consistent manner.
- </para>
-
- <para>
- It is good news that Samba does this to a large extent, and on top of that, provides a high degree
- of optional configuration to override the default behavior. We look at some of these overrides,
- but for the greater part we stay within the bounds of default behavior. Those wishing to explore
- the depths of control ability should review the &smb.conf; man page.
- </para>
-
- <para>The following compares file system features for UNIX with those of MS Windows NT/200x:
- <indexterm><primary>File System</primary><secondary>feature comparison</secondary></indexterm>
-
- </para>
-
- <variablelist>
- <varlistentry>
- <term>Name Space</term>
- <listitem>
- <para>
- MS Windows NT4/200x/XP file names may be up to 254 characters long, and UNIX file names
- may be 1023 characters long. In MS Windows, file extensions indicate particular file types;
- in UNIX this is not so rigorously observed because all names are considered arbitrary.
- </para>
- <para>
- What MS Windows calls a folder, UNIX calls a directory.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Case Sensitivity</term>
- <listitem>
- <para>
- <indexterm><primary>8.3 file names</primary></indexterm>
- <indexterm><primary>File System</primary><secondary>case sensitivity</secondary></indexterm>
- MS Windows file names are generally uppercase if made up of 8.3 (8-character file name
- and 3 character extension. File names that are longer than 8.3 are case preserving and case
- insensitive.
- </para>
-
- <para>
- UNIX file and directory names are case sensitive and case preserving. Samba implements the
- MS Windows file name behavior, but it does so as a user application. The UNIX file system
- provides no mechanism to perform case-insensitive file name lookups. MS Windows does this
- by default. This means that Samba has to carry the processing overhead to provide features
- that are not native to the UNIX operating system environment.
- </para>
-
- <para>
- Consider the following. All are unique UNIX names but one single MS Windows file name:
- <screen>
- MYFILE.TXT
- MyFile.txt
- myfile.txt
- </screen></para>
-
- <para>
- So clearly, in an MS Windows file namespace these three files cannot co-exist, but in UNIX
- they can.
- </para>
-
- <para>
- So what should Samba do if all three are present? That which is lexically first will be
- accessible to MS Windows users; the others are invisible and unaccessible &smbmdash; any
- other solution would be suicidal. The Windows client will ask for a case-insensitive file
- lookup, and that is the reason for which Samba must offer a consistent selection in the
- event that the UNIX directory contains multiple files that would match a case insensitive
- file listing.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Directory Separators</term>
- <listitem><para>
- <indexterm><primary>Directory Separators</primary></indexterm>
- MS Windows and DOS use the backslash <constant>\</constant> as a directory delimiter, and UNIX uses
- the forward-slash <constant>/</constant> as its directory delimiter. This is handled transparently by Samba.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Drive Identification</term>
- <listitem><para>
- <indexterm><primary>Drive Identification</primary></indexterm>
- MS Windows products support a notion of drive letters, like <command>C:</command>, to represent
- disk partitions. UNIX has no concept of separate identifiers for file partitions; each
- such file system is mounted to become part of the overall directory tree.
- The UNIX directory tree begins at <constant>/</constant> just as the root of a DOS drive is specified as
- <constant>C:\</constant>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>File Naming Conventions</term>
- <listitem><para>
- <indexterm><primary>File Naming Conventions</primary></indexterm>
- MS Windows generally never experiences file names that begin with a dot (<constant>.</constant>), while in UNIX these
- are commonly found in a user's home directory. Files that begin with a dot (<constant>.</constant>) are typically
- startup files for various UNIX applications, or they may be files that contain
- startup configuration data.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Links and Short-Cuts</term>
- <listitem><para>
- <indexterm><primary>Links</primary><secondary>hard</secondary></indexterm>
- <indexterm><primary>Links</primary><secondary>soft</secondary></indexterm>
- <indexterm><primary>Shortcuts</primary></indexterm>
- MS Windows make use of <emphasis>links and shortcuts</emphasis> that are actually special types of files that will
- redirect an attempt to execute the file to the real location of the file. UNIX knows of file and directory
- links, but they are entirely different from what MS Windows users are used to.
- </para>
-
- <para>
- Symbolic links are files in UNIX that contain the actual location of the data (file or directory). An
- operation (like read or write) will operate directly on the file referenced. Symbolic links are also
- referred to as <quote>soft links.</quote> A hard link is something that MS Windows is not familiar with. It allows
- one physical file to be known simultaneously by more than one file name.
- </para></listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort
- in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the
- purpose of UNIX/Linux training and education.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Managing Directories</title>
-
- <para>
-<indexterm><primary>create</primary></indexterm>
-<indexterm><primary>delete</primary></indexterm>
-<indexterm><primary>rename</primary></indexterm>
- There are three basic operations for managing directories: <command>create</command>, <command>delete</command>,
- <command>rename</command>. <link linkend="TOSH-Accesstbl">Managing Directories with UNIX and
- Windows</link> compares the commands in Windows and UNIX that implement these operations.
- </para>
-
- <table frame="all" id="TOSH-Accesstbl">
- <title>Managing Directories with UNIX and Windows</title>
- <tgroup align="center" cols="3">
- <thead>
- <row><entry>Action</entry><entry>MS Windows Command</entry><entry>UNIX Command</entry></row>
- </thead>
-
- <tbody>
- <row><entry>create</entry><entry>md folder</entry><entry>mkdir folder</entry></row>
- <row><entry>delete</entry><entry>rd folder</entry><entry>rmdir folder</entry></row>
- <row><entry>rename</entry><entry>rename oldname newname</entry><entry>mv oldname newname</entry></row>
- </tbody>
- </tgroup>
- </table>
-
- </sect2>
-
- <sect2>
- <title>File and Directory Access Control</title>
-
- <para>
- <indexterm><primary>ACLs</primary><secondary>File System</secondary></indexterm>
-<indexterm><primary>POSIX ACLs</primary></indexterm>
-<indexterm><primary>EAs</primary></indexterm>
- The network administrator is strongly advised to read basic UNIX training manuals and reference materials
- regarding file and directory permissions maintenance. Much can be achieved with the basic UNIX permissions
- without having to resort to more complex facilities like POSIX ACLs or extended attributes (EAs).
- </para>
-
- <para>
- UNIX/Linux file and directory access permissions involves setting three primary sets of data and one control set.
- A UNIX file listing looks as follows:
-<screen>
-&prompt;<userinput>ls -la</userinput>
-total 632
-drwxr-xr-x 13 maryo gnomes 816 2003-05-12 22:56 .
-drwxrwxr-x 37 maryo gnomes 3800 2003-05-12 22:29 ..
-dr-xr-xr-x 2 maryo gnomes 48 2003-05-12 22:29 muchado02
-drwxrwxrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado03
-drw-rw-rw- 2 maryo gnomes 48 2003-05-12 22:29 muchado04
-d-w--w--w- 2 maryo gnomes 48 2003-05-12 22:29 muchado05
-dr--r--r-- 2 maryo gnomes 48 2003-05-12 22:29 muchado06
-drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08
----------- 1 maryo gnomes 1242 2003-05-12 22:31 mydata00.lst
---w--w--w- 1 maryo gnomes 7754 2003-05-12 22:33 mydata02.lst
--r--r--r-- 1 maryo gnomes 21017 2003-05-12 22:32 mydata04.lst
--rw-rw-rw- 1 maryo gnomes 41105 2003-05-12 22:32 mydata06.lst
-&prompt;
-</screen>
- </para>
-
- <para>
- The columns represent (from left to right) permissions, number of hard links to file, owner, group, size
- (bytes), access date, time of last modification, and file name.
- </para>
-
- <para>
- An overview of the permissions field is shown in <link linkend="access1">Overview of UNIX permissions
- field</link>.
- </para>
-
- <figure id="access1">
- <title>Overview of UNIX permissions field.</title>
- <imagefile scale="40">access1</imagefile>
- </figure>
-
- <para>
- Any bit flag may be unset. An unset bit flag is the equivalent of "cannot" and is represented
- as a <quote>-</quote> character (see <link linkend="access2"/>)
-<indexterm><primary>read</primary></indexterm>
-<indexterm><primary>write</primary></indexterm>
-<indexterm><primary>execute</primary></indexterm>
-<indexterm><primary>user</primary></indexterm>
-<indexterm><primary>group</primary></indexterm>
-<indexterm><primary>other</primary></indexterm>
- </para>
-
-<example id="access2">
-<title>Example File</title>
-<programlisting>
--rwxr-x--- Means:
- ^^^ The owner (user) can read, write, execute
- ^^^ the group can read and execute
- ^^^ everyone else cannot do anything with it.
-</programlisting>
-</example>
-
-
- <para>
-<indexterm><primary>character device</primary></indexterm>
-<indexterm><primary>block device</primary></indexterm>
-<indexterm><primary>pipe device</primary></indexterm>
-<indexterm><primary>UNIX Domain Socket</primary></indexterm>
- Additional possibilities in the [type] field are c = character device, b = block device, p = pipe device,
- s = UNIX Domain Socket.
- </para>
-
- <para>
-<indexterm><primary>read</primary></indexterm>
-<indexterm><primary>write</primary></indexterm>
-<indexterm><primary>execute</primary></indexterm>
-<indexterm><primary>SGID</primary></indexterm>
-<indexterm><primary>SUID</primary></indexterm>
- The letters <constant>rwxXst</constant> set permissions for the user, group, and others as read (r), write (w),
- execute (or access for directories) (x), execute only if the file is a directory or already has execute
- permission for some user (X), set user (SUID) or group ID (SGID) on execution (s), sticky (t).
- </para>
-
- <para>
-<indexterm><primary>sticky bit</primary></indexterm>
-<indexterm><primary>unlinked</primary></indexterm>
-<indexterm><primary>/tmp</primary></indexterm>
-<indexterm><primary>world-writable</primary></indexterm>
- When the sticky bit is set on a directory, files in that directory may be unlinked (deleted) or renamed only by root or their owner.
- Without the sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on
- directories, such as <filename>/tmp</filename>, that are world-writable.
- </para>
-
- <para>
-<indexterm><primary>write</primary></indexterm>
-<indexterm><primary>read</primary></indexterm>
-<indexterm><primary>setting up directories</primary></indexterm>
-<indexterm><primary>set user id</primary><see>SUID</see></indexterm>
-<indexterm><primary>set group id</primary><see>SGID</see></indexterm>
- When the set user or group ID bit (s) is set on a directory, then all files created within it will be owned by the user and/or
- group whose `set user or group' bit is set. This can be helpful in setting up directories for which it is desired that
- all users who are in a group should be able to write to and read from a file, particularly when it is undesirable for that file
- to be exclusively owned by a user whose primary group is not the group that all such users belong to.
- </para>
-
- <para>
- When a directory is set <constant>d-wx--x---</constant>, the owner can read and create (write) files in it, but because
- the (r) read flags are not set, files cannot be listed (seen) in the directory by anyone. The group can read files in the
- directory but cannot create new files. If files in the directory are set to be readable and writable for the group, then
- group members will be able to write to (or delete) them.
- </para>
-
- <sect3>
- <title>Protecting Directories and Files from Deletion</title>
-
- <para>
-<indexterm><primary>protect files</primary></indexterm>
-<indexterm><primary>protect directories</primary></indexterm>
-<indexterm><primary>access controls</primary></indexterm>
-<indexterm><primary>capability to delete</primary></indexterm>
- People have asked on the Samba mailing list how is it possible to protect files or directories from deletion by users.
- For example, Windows NT/2K/XP provides the capacity to set access controls on a directory into which people can
- write files but not delete them. It is possible to set an ACL on a Windows file that permits the file to be written to
- but not deleted. Such concepts are foreign to the UNIX operating system file space. Within the UNIX file system
- anyone who has the ability to create a file can write to it. Anyone who has write permission on the
- directory that contains a file and has write permission for it has the capability to delete it.
- </para>
-
- <para>
-<indexterm><primary>directory permissions</primary></indexterm>
-<indexterm><primary>delete a file</primary></indexterm>
-<indexterm><primary>write access</primary></indexterm>
- For the record, in the UNIX environment the ability to delete a file is controlled by the permissions on
- the directory that the file is in. In other words, a user can delete a file in a directory to which that
- user has write access, even if that user does not own the file.
- </para>
-
- <para>
-<indexterm><primary>file system capabilities</primary></indexterm>
-<indexterm><primary>inheritance</primary></indexterm>
-<indexterm><primary>POSIX ACLs</primary></indexterm>
-<indexterm><primary>extended attributes</primary></indexterm>
- Of necessity, Samba is subject to the file system semantics of the host operating system. Samba is therefore
- limited in the file system capabilities that can be made available through Windows ACLs, and therefore performs
- a "best fit" translation to POSIX ACLs. Some UNIX file systems do, however support, a feature known
- as extended attributes. Only the Windows concept of <emphasis>inheritance</emphasis> is implemented by Samba through
- the appropriate extended attribute.
- </para>
-
- <para>
-<indexterm><primary>extended attributes</primary></indexterm>
-<indexterm><primary>immutable</primary></indexterm>
-<indexterm><primary>chattr</primary></indexterm>
-<indexterm><primary>CAP_LINUX_IMMUTABLE</primary></indexterm>
- The specific semantics of the extended attributes are not consistent across UNIX and UNIX-like systems such as Linux.
- For example, it is possible on some implementations of the extended attributes to set a flag that prevents the directory
- or file from being deleted. The extended attribute that may achieve this is called the <constant>immutable</constant> bit.
- Unfortunately, the implementation of the immutable flag is NOT consistent with published documentation. For example, the
- man page for the <command>chattr</command> on SUSE Linux 9.2 says:
-<screen>
-A file with the i attribute cannot be modified: it cannot be deleted
-or renamed, no link can be created to this file and no data can be
-written to the file. Only the superuser or a process possessing the
-CAP_LINUX_IMMUTABLE capability can set or clear this attribute.
-</screen>
- A simple test can be done to check if the immutable flag is supported on files in the file system of the Samba host
- server.
- </para>
-
- <procedure>
- <title>Test for File Immutibility Support</title>
-
- <step><para>
- Create a file called <filename>filename</filename>.
- </para></step>
-
- <step><para>
- Login as the <constant>root</constant> user, then set the immutibile flag on a test file as follows:
-<screen>
-&rootprompt; chattr +i `filename'
-</screen>
- </para></step>
-
- <step><para>
- Login as the user who owns the file (not root) and attempt to remove the file as follows:
-<screen>
-mystic:/home/hannibal > rm filename
-</screen>
- It will not be possible to delete the file if the immutable flag is correctly honored.
- </para></step>
- </procedure>
-
- <para>
- On operating systems and file system types that support the immutable bit, it is possible to create directories
- that cannot be deleted. Check the man page on your particular host system to determine whether or not
- immutable directories are writable. If they are not, then the entire directory and its contents will effectively
- be protected from writing (file creation also) and deletion.
- </para>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Share Definition Access Controls</title>
-
-
- <para>
- <indexterm><primary>permissions</primary><secondary>share</secondary></indexterm>
- The following parameters in the &smb.conf; file sections define a share control or affect access controls.
- Before using any of the following options, please refer to the man page for &smb.conf;.
- </para>
-
- <sect2>
- <title>User- and Group-Based Controls</title>
-
- <para>
- User- and group-based controls can prove quite useful. In some situations it is distinctly desirable to
- force all file system operations as if a single user were doing so. The use of the
- <smbconfoption name="force user"/> and <smbconfoption name="force group"/> behavior will achieve this.
- In other situations it may be necessary to use a paranoia level of control to ensure that only particular
- authorized persons will be able to access a share or its contents. Here the use of the
- <smbconfoption name="valid users"/> or the <smbconfoption name="invalid users"/> parameter may be useful.
- </para>
-
- <para>
- As always, it is highly advisable to use the easiest to maintain and the least ambiguous method for
- controlling access. Remember, when you leave the scene, someone else will need to provide assistance, and
- if he or she finds too great a mess or does not understand what you have done, there is risk of
- Samba being removed and an alternative solution being adopted.
- </para>
-
- <para>
- <link linkend="ugbc">User and Group Based Controls</link> enumerates these controls.
- </para>
-
- <table frame='all' pgwide='0' id="ugbc"><title>User- and Group-Based Controls</title>
- <tgroup cols='2'>
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <thead>
- <row>
- <entry align="center">Control Parameter</entry>
- <entry align="center">Description, Action, Notes</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><smbconfoption name="admin users"/></entry>
- <entry><para>
- List of users who will be granted administrative privileges on the share.
- They will do all file operations as the superuser (root).
- Users in this list will be able to do anything they like on the share,
- irrespective of file permissions.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="force group"/></entry>
- <entry><para>
- Specifies a UNIX group name that will be assigned as the default primary group
- for all users connecting to this service.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="force user"/></entry>
- <entry><para>
- Specifies a UNIX username that will be assigned as the default user for all users connecting to this service.
- This is useful for sharing files. Incorrect use can cause security problems.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="guest ok"/></entry>
- <entry><para>
- If this parameter is set for a service, then no password is required to connect to the service. Privileges will be
- those of the guest account.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="invalid users"/></entry>
- <entry><para>
- List of users that should not be allowed to login to this service.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="only user"/></entry>
- <entry><para>
- Controls whether connections with usernames not in the user list will be allowed.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="read list"/></entry>
- <entry><para>
- List of users that are given read-only access to a service. Users in this list
- will not be given write access, no matter what the read-only option is set to.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="username"/></entry>
- <entry><para>
- Refer to the &smb.conf; man page for more information; this is a complex and potentially misused parameter.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="valid users"/></entry>
- <entry><para>
- List of users that should be allowed to login to this service.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="write list"/></entry>
- <entry><para>
- List of users that are given read-write access to a service.
- </para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- </sect2>
-
- <sect2>
- <title>File and Directory Permissions-Based Controls</title>
-
- <para>
- Directory permission-based controls, if misused, can result in considerable difficulty in diagnosing the causes of
- misconfiguration. Use them sparingly and carefully. By gradually introducing each, one at a time, undesirable side
- effects may be detected. In the event of a problem, always comment all of them out and then gradually reintroduce
- them in a controlled way.
- </para>
-
- <para>
- Refer to <link linkend="fdpbc">File and Directory Permission Based Controls</link> for information
- regarding the parameters that may be used to set file and directory permission-based access controls.
- </para>
-
- <table frame='all' id="fdpbc"><title>File and Directory Permission-Based Controls</title>
- <tgroup cols='2'>
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <thead>
- <row>
- <entry align="center">Control Parameter</entry>
- <entry align="center">Description, Action, Notes</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><smbconfoption name="create mask"/></entry>
- <entry><para>
- Refer to the &smb.conf; man page.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="directory mask"/></entry>
- <entry><para>
- The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories.
- See also directory security mask.
- </para></entry></row>
- <row>
- <entry><smbconfoption name="dos filemode"/></entry>
- <entry><para>
- Enabling this parameter allows a user who has write access to the file to modify the permissions on it.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="force create mode"/></entry>
- <entry><para>
- This parameter specifies a set of UNIX-mode bit permissions that will always be set on a file created by Samba.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="force directory mode"/></entry>
- <entry><para>
- This parameter specifies a set of UNIX-mode bit permissions that will always be set on a directory created by Samba.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="force directory security mode"/></entry>
- <entry><para>
- Controls UNIX permission bits modified when a Windows NT client is manipulating UNIX permissions on a directory.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="force security mode"/></entry>
- <entry><para>
- Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="hide unreadable"/></entry>
- <entry><para>
- Prevents clients from seeing the existence of files that cannot be read.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="hide unwriteable files"/></entry>
- <entry><para>
- Prevents clients from seeing the existence of files that cannot be written to. Unwritable directories are shown as usual.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="nt acl support"/></entry>
- <entry><para>
- This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT ACLs.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="security mask"/></entry>
- <entry><para>
- Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file.
- </para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- </sect2>
-
- <sect2>
- <title>Miscellaneous Controls</title>
-
- <para>
- The parameters documented in <link linkend="mcoc">Other Controls</link> are often used by administrators
- in ways that create inadvertent barriers to file access. Such are the consequences of not understanding the
- full implications of &smb.conf; file settings.
- </para>
-
- <table frame='all' id="mcoc"><title>Other Controls</title>
- <tgroup cols='2'>
- <colspec align="justify" colwidth="1*"/>
- <colspec align="justify" colwidth="1*"/>
- <thead>
- <row>
- <entry align="center">Control Parameter</entry>
- <entry align="center">Description, Action, Notes</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <smbconfoption name="case sensitive"/>,
- <smbconfoption name="default case"/>,
- <smbconfoption name="short preserve case"/>
- </entry>
- <entry><para>
- This means that all file name lookup will be done in a case-sensitive manner.
- Files will be created with the precise file name Samba received from the MS Windows client.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="csc policy"/></entry>
- <entry><para>
- Client-side caching policy parallels MS Windows client-side file caching capabilities.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="dont descend"/></entry>
- <entry><para>
- Allows specifying a comma-delimited list of directories that the server should always show as empty.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="dos filetime resolution"/></entry>
- <entry><para>
- This option is mainly used as a compatibility option for Visual C++ when used against Samba shares.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="dos filetimes"/></entry>
- <entry><para>
- DOS and Windows allow users to change file timestamps if they can write to the file. POSIX semantics prevent this.
- This option allows DOS and Windows behavior.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="fake oplocks"/></entry>
- <entry><para>
- Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an
- oplock, the client is free to assume that it is the only one accessing the file, and it will aggressively cache file data.
- </para></entry>
- </row>
- <row>
- <entry>
- <smbconfoption name="hide dot files"/>,
- <smbconfoption name="hide files"/>,
- <smbconfoption name="veto files"/>
- </entry>
- <entry><para>
- Note: MS Windows Explorer allows override of files marked as hidden so they will still be visible.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="read only"/></entry>
- <entry><para>
- If this parameter is yes, then users of a service may not create or modify files in the service's directory.
- </para></entry>
- </row>
- <row>
- <entry><smbconfoption name="veto files"/></entry>
- <entry><para>
- List of files and directories that are neither visible nor accessible.
- </para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Access Controls on Shares</title>
-
-
- <para>
-<indexterm><primary>per-share access control</primary></indexterm>
-<indexterm><primary>Everyone - Full Control</primary></indexterm>
-<indexterm><primary>specific restrictions</primary></indexterm>
-<indexterm><primary>share access</primary></indexterm>
- <indexterm><primary>permissions</primary><secondary>share ACLs</secondary></indexterm>
- This section deals with how to configure Samba per-share access control restrictions.
- By default, Samba sets no restrictions on the share itself. Restrictions on the share itself
- can be set on MS Windows NT4/200x/XP shares. This can be an effective way to limit who can
- connect to a share. In the absence of specific restrictions, the default setting is to allow
- the global user <constant>Everyone - Full Control</constant> (full control, change and read).
- </para>
-
- <para>
-<indexterm><primary>access control</primary></indexterm>
-<indexterm><primary>MMC</primary></indexterm>
-<indexterm><primary>Computer Management</primary></indexterm>
- At this time Samba does not provide a tool for configuring access control settings on the share
- itself. The only way to create those settings is to use either the NT4 Server Manager or the Windows 200x
- Microsoft Management Console (MMC) for Computer Management. There are currently no plans to provide
- this capability in the Samba command-line tool set.
- </para>
-
- <para>
-<indexterm><primary>share_info.tdb</primary></indexterm>
-<indexterm><primary>/usr/local/samba/var</primary></indexterm>
-<indexterm><primary>tdbdump</primary></indexterm>
-<indexterm><primary>tdb files</primary></indexterm>
- Samba stores the per-share access control settings in a file called <filename>share_info.tdb</filename>.
- The location of this file on your system will depend on how Samba was compiled. The default location
- for Samba's tdb files is under <filename>/usr/local/samba/var</filename>. If the <filename>tdbdump</filename>
- utility has been compiled and installed on your system, then you can examine the contents of this file
- by executing <command>tdbdump share_info.tdb</command> in the directory containing the tdb files.
- </para>
-
- <sect2>
- <title>Share Permissions Management</title>
-
- <para>
- The best tool for share permissions management is platform-dependent. Choose the best tool for your environment.
- </para>
-
- <sect3>
- <title>Windows NT4 Workstation/Server</title>
- <para>
-<indexterm><primary>manage share permissions</primary></indexterm>
-<indexterm><primary>share permissions</primary></indexterm>
-<indexterm><primary>NT Server Manager</primary></indexterm>
-<indexterm><primary>Windows NT4</primary></indexterm>
- The tool you need to manage share permissions on a Samba server from a Windows NT4 Workstation or Server
- is the NT Server Manager. Server Manager is shipped with Windows NT4 Server products but not with Windows
- NT4 Workstation. You can obtain the NT Server Manager for MS Windows NT4 Workstation from the Microsoft
- web site <ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673">support</ulink> section.
- </para>
-
- <procedure>
- <title>Instructions</title>
-
- <step><para>
- Launch the <application>NT4 Server Manager</application> and click on the Samba server you want to
- administer. From the menu select <guimenu>Computer</guimenu>, then click on
- <guimenuitem>Shared Directories</guimenuitem>.
- </para></step>
-
- <step><para>
- Click on the share that you wish to manage and click the <guilabel>Properties</guilabel> tab, then click
- the <guilabel>Permissions</guilabel> tab. Now you can add or change access control settings as you wish.
- </para></step>
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>Windows 200x/XP</title>
-
- <para>
-<indexterm><primary>Windows NT4/200x/XP</primary></indexterm>
-<indexterm><primary>ACLs on share</primary></indexterm>
-<indexterm><primary>Sharing</primary></indexterm>
-<indexterm><primary>Permissions</primary></indexterm>
- On <application>MS Windows NT4/200x/XP</application> systems, ACLs on the share itself are set using
- tools like the MS Explorer. For example, in Windows 200x, right-click on the shared folder,
- then select <guimenuitem>Sharing</guimenuitem>, then click on <guilabel>Permissions</guilabel>. The default
- Windows NT4/200x permissions allow the group "Everyone" full control on the share.
- </para>
-
- <para>
-<indexterm><primary>Computer Management</primary></indexterm>
-<indexterm><primary>MMC</primary></indexterm>
-<indexterm><primary>tool</primary></indexterm>
- MS Windows 200x and later versions come with a tool called the <application>Computer Management</application>
- snap-in for the MMC. This tool can be accessed via <guimenu>Control Panel ->
- Administrative Tools -> Computer Management</guimenu>.
- </para>
-
- <procedure>
- <title>Instructions</title>
- <step><para>
- After launching the MMC with the Computer Management snap-in, click the menu item <guimenuitem>Action</guimenuitem>
- and select <guilabel>Connect to another computer</guilabel>. If you are not logged onto a domain you will be prompted
- to enter a domain login user identifier and a password. This will authenticate you to the domain.
- If you are already logged in with administrative privilege, this step is not offered.
- </para></step>
-
- <step><para>
- If the Samba server is not shown in the <guilabel>Select Computer</guilabel> box, type in the name of the target
- Samba server in the field <guilabel>Name:</guilabel>. Now click the on <guibutton>[+]</guibutton> next to
- <guilabel>System Tools</guilabel>, then on the <guibutton>[+]</guibutton> next to
- <guilabel>Shared Folders</guilabel> in the left panel.
- </para></step>
-
- <step><para>
-<indexterm><primary>Share Permissions</primary></indexterm>
- In the right panel, double-click on the share on which you wish to set access control permissions.
- Then click the tab <guilabel>Share Permissions</guilabel>. It is now possible to add access control entities
- to the shared folder. Remember to set what type of access (full control, change, read) you
- wish to assign for each entry.
- </para></step>
- </procedure>
-
- <warning>
- <para>
- Be careful. If you take away all permissions from the <constant>Everyone</constant> user without removing
- this user, effectively no user will be able to access the share. This is a result of what is known as
- ACL precedence. Everyone with <emphasis>no access</emphasis> means that <constant>MaryK</constant> who is
- part of the group <constant>Everyone</constant> will have no access even if she is given explicit full
- control access.
- </para>
- </warning>
-
- </sect3>
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>MS Windows Access Control Lists and UNIX Interoperability</title>
-
- <sect2>
- <title>Managing UNIX Permissions Using NT Security Dialogs</title>
-
-
- <para>
- <indexterm><primary>permissions</primary><secondary>file/directory ACLs</secondary></indexterm>
- Windows NT clients can use their native security settings dialog box to view and modify the
- underlying UNIX permissions.
- </para>
-
- <para>
- This ability is careful not to compromise the security of the UNIX host on which Samba is running and
- still obeys all the file permission rules that a Samba administrator can set.
- </para>
-
- <para>
- Samba does not attempt to go beyond POSIX ACLs, so the various finer-grained access control
- options provided in Windows are actually ignored.
- </para>
-
- <note>
- <para>
- All access to UNIX/Linux system files via Samba is controlled by the operating system file access controls.
- When trying to figure out file access problems, it is vitally important to find the identity of the Windows
- user as it is presented by Samba at the point of file access. This can best be determined from the
- Samba log files.
- </para>
- </note>
- </sect2>
-
- <sect2>
- <title>Viewing File Security on a Samba Share</title>
-
- <para>
- From an NT4/2000/XP client, right-click on any file or directory in a Samba-mounted drive letter
- or UNC path. When the menu pops up, click on the <guilabel>Properties</guilabel> entry at the bottom
- of the menu. This brings up the file <constant>Properties</constant> dialog box. Click on the
- <guilabel>Security</guilabel> tab and you will see three buttons: <guibutton>Permissions</guibutton>,
- <guibutton>Auditing</guibutton>, and <guibutton>Ownership</guibutton>. The <guibutton>Auditing</guibutton>
- button will cause either an error message <errorname>"A requested privilege is not held by the client"</errorname>
- to appear if the user is not the NT administrator, or a dialog intended to allow an administrator
- to add auditing requirements to a file if the user is logged on as the NT administrator. This dialog is
- nonfunctional with a Samba share at this time, because the only useful button, the <guibutton>Add</guibutton>
- button, will not currently allow a list of users to be seen.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Viewing File Ownership</title>
-
- <para>
- Clicking on the <guibutton>Ownership</guibutton> button brings up a dialog box telling you who owns
- the given file. The owner name will be displayed like this:
- <screen>
- <constant>SERVER\user (Long name)</constant>
- </screen>
- <replaceable>SERVER</replaceable> is the NetBIOS name of the Samba server, <replaceable>user</replaceable>
- is the username of the UNIX user who owns the file, and <replaceable>(Long name)</replaceable> is the
- descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).
- Click on the <guibutton>Close</guibutton> button to remove this dialog.
- </para>
-
- <para>
- If the parameter <smbconfoption name="nt acl support"/> is set to <constant>false</constant>,
- the file owner will be shown as the NT user <emphasis>Everyone</emphasis>.
- </para>
-
- <para>
-<indexterm><primary>Take Ownership</primary></indexterm>
- The <guibutton>Take Ownership</guibutton> button will not allow you to change the ownership of this file to
- yourself (clicking it will display a dialog box complaining that the user as whom you are currently logged onto
- the NT client cannot be found). The reason for this is that changing the ownership of a file is a privileged
- operation in UNIX, available only to the <emphasis>root</emphasis> user. Because clicking on this button causes
- NT to attempt to change the ownership of a file to the current user logged into the NT client, this will
- not work with Samba at this time.
- </para>
-
- <para>
-<indexterm><primary>chown</primary></indexterm>
-<indexterm><primary>ownership</primary></indexterm>
-<indexterm><primary>Seclib</primary></indexterm>
- There is an NT <command>chown</command> command that will work with Samba and allow a user with administrator
- privilege connected to a Samba server as root to change the ownership of files on both a local NTFS file system
- or remote mounted NTFS or Samba drive. This is available as part of the <application>Seclib</application> NT
- security library written by Jeremy Allison of the Samba Team and is downloadable from the main Samba FTP site.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Viewing File or Directory Permissions</title>
-
- <para>
- The third button is the <guibutton>Permissions</guibutton> button. Clicking on it brings up a dialog box
- that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed like this:
- </para>
-
- <para><command><replaceable>SERVER</replaceable>\
- <replaceable>user</replaceable>
- <replaceable>(Long name)</replaceable></command></para>
-
- <para><replaceable>SERVER</replaceable> is the NetBIOS name of the Samba server,
- <replaceable>user</replaceable> is the username of the UNIX user who owns the file, and
- <replaceable>(Long name)</replaceable> is the descriptive string identifying the user (normally found in the
- GECOS field of the UNIX password database).</para>
-
- <para>
- If the parameter <smbconfoption name="nt acl support"/> is set to <constant>false</constant>,
- the file owner will be shown as the NT user <constant>Everyone</constant>, and the permissions will be
- shown as NT <emphasis>Full Control</emphasis>.
- </para>
-
-
- <para>
- The permissions field is displayed differently for files and directories. Both are discussed next.
- </para>
-
- <sect3>
- <title>File Permissions</title>
-
- <para>
- The standard UNIX user/group/world triplet and the corresponding <constant>read, write,
- execute</constant> permissions triplets are mapped by Samba into a three-element NT ACL with the
- <quote>r</quote>, <quote>w</quote>, and <quote>x</quote> bits mapped into the corresponding NT
- permissions. The UNIX world permissions are mapped into the global NT group <constant>Everyone</constant>, followed
- by the list of permissions allowed for the UNIX world. The UNIX owner and group permissions are displayed as an NT
- <guiicon>user</guiicon> icon and an NT <guiicon>local group</guiicon> icon, respectively, followed by the list
- of permissions allowed for the UNIX user and group.
- </para>
-
- <para>
- Because many UNIX permission sets do not map into common NT names such as <constant>read</constant>,
- <constant>change</constant>, or <constant>full control</constant>, usually the permissions will be prefixed
- by the words <constant>Special Access</constant> in the NT display list.
- </para>
-
- <para>
- But what happens if the file has no permissions allowed for a particular UNIX user group or world component?
- In order to allow <emphasis>no permissions</emphasis> to be seen and modified, Samba then overloads the NT
- <constant>Take Ownership</constant> ACL attribute (which has no meaning in UNIX) and reports a component with
- no permissions as having the NT <command>O</command> bit set. This was chosen, of course, to make it look
- like a zero, meaning zero permissions. More details on the decision behind this action are given below.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Directory Permissions</title>
-
- <para>
- Directories on an NT NTFS file system have two different sets of permissions. The first set is the ACL set on the
- directory itself, which is usually displayed in the first set of parentheses in the normal <constant>RW</constant>
- NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described
- above, and is displayed in the same way.
- </para>
-
- <para>
- The second set of directory permissions has no real meaning in the UNIX permissions world and represents the <constant>
- inherited</constant> permissions that any file created within this directory would inherit.
- </para>
-
- <para>
- Samba synthesizes these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file
- created by Samba on this share would receive.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Modifying File or Directory Permissions</title>
-
- <para>
- Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box
- and clicking on <guibutton>OK</guibutton>. However, there are limitations that a user needs to be aware of,
- and also interactions with the standard Samba permission masks and mapping of DOS attributes that also need to
- be taken into account.
- </para>
-
- <para>
- If the parameter <smbconfoption name="nt acl support"/> is set to <constant>false</constant>, any attempt to
- set security permissions will fail with an <errorname>"Access Denied" </errorname> message.
- </para>
-
- <para>
- The first thing to note is that the <guibutton>Add</guibutton> button will not return a list of users in Samba
- (it will give an error message saying <errorname>"The remote procedure call failed and did not
- execute"</errorname>). This means that you can only manipulate the current user/group/world permissions listed
- in the dialog box. This actually works quite well because these are the only permissions that UNIX actually
- has.
- </para>
-
- <para>
- If a permission triplet (either user, group, or world) is removed from the list of permissions in the NT
- dialog box, then when the <guibutton>OK</guibutton> button is pressed, it will be applied as <emphasis>no
- permissions</emphasis> on the UNIX side. If you view the permissions again, the <emphasis>no
- permissions</emphasis> entry will appear as the NT <command>O</command> flag, as described above. This allows
- you to add permissions back to a file or directory once you have removed them from a triplet component.
- </para>
-
- <para>
- Because UNIX supports only the <quote>r</quote>, <quote>w</quote>, and <quote>x</quote> bits of an NT ACL, if
- other NT security attributes such as <constant>Delete Access</constant> are selected, they will be ignored
- when applied on the Samba server.
- </para>
-
- <para>
- When setting permissions on a directory, the second set of permissions (in the second set of parentheses) is
- by default applied to all files within that directory. If this is not what you want, you must uncheck the
- <guilabel>Replace permissions on existing files</guilabel> checkbox in the NT dialog before clicking on
- <guibutton>OK</guibutton>.
- </para>
-
- <para>
- If you wish to remove all permissions from a user/group/world component, you may either highlight the
- component and click on the <guibutton>Remove</guibutton> button or set the component to only have the special
- <constant>Take Ownership</constant> permission (displayed as <command>O</command>) highlighted.
- </para>
-
- </sect2>
-
-<?latex \newpage ?>
- <sect2>
- <title>Interaction with the Standard Samba <quote>create mask</quote> Parameters</title>
-
- <para>There are four parameters that control interaction with the standard Samba <parameter>create mask</parameter> parameters:
-
-
- <itemizedlist>
- <listitem><para><smbconfoption name="security mask"/></para></listitem>
- <listitem><para><smbconfoption name="force security mode"/></para></listitem>
- <listitem><para><smbconfoption name="directory security mask"/></para></listitem>
- <listitem><para><smbconfoption name="force directory security mode"/></para></listitem>
- </itemizedlist>
-
- </para>
-
- <para>
- When a user clicks on <guibutton>OK</guibutton> to apply the
- permissions, Samba maps the given permissions into a user/group/world
- r/w/x triplet set, and then checks the changed permissions for a
- file against the bits set in the
- <smbconfoption name="security mask"/> parameter. Any bits that
- were changed that are not set to <emphasis>1</emphasis> in this parameter are left alone
- in the file permissions.</para>
-
- <para>
- Essentially, zero bits in the <smbconfoption name="security mask"/>
- may be treated as a set of bits the user is <emphasis>not</emphasis>
- allowed to change, and one bits are those the user is allowed to change.
- </para>
-
- <para>
- If not explicitly set, this parameter defaults to the same value as
- the <smbconfoption name="create mask"/> parameter. To allow a user to modify all the
- user/group/world permissions on a file, set this parameter to 0777.
- </para>
-
- <para>
- Next Samba checks the changed permissions for a file against the bits set in the
- <smbconfoption name="force security mode"/> parameter. Any bits
- that were changed that correspond to bits set to <emphasis>1</emphasis> in this parameter
- are forced to be set.</para>
-
- <para>
- Essentially, bits set in the <parameter>force security mode</parameter> parameter
- may be treated as a set of bits that, when modifying security on a file, the user
- has always set to be <emphasis>on</emphasis>.</para>
-
- <para>
- If not explicitly set, this parameter defaults to the same value
- as the <smbconfoption name="force create mode"/> parameter.
- To allow a user to modify all the user/group/world permissions on a file
- with no restrictions, set this parameter to 000. The
- <smbconfoption name="security mask"/> and <parameter>force
- security mode</parameter> parameters are applied to the change
- request in that order.</para>
-
- <para>
- For a directory, Samba performs the same operations as
- described above for a file except it uses the parameter <parameter>
- directory security mask</parameter> instead of <parameter>security
- mask</parameter>, and <parameter>force directory security mode
- </parameter> parameter instead of <parameter>force security mode
- </parameter>.</para>
-
- <para>
- The <smbconfoption name="directory security mask"/> parameter
- by default is set to the same value as the <parameter>directory mask
- </parameter> parameter and the <parameter>force directory security
- mode</parameter> parameter by default is set to the same value as
- the <smbconfoption name="force directory mode"/> parameter.
- In this way Samba enforces the permission restrictions that
- an administrator can set on a Samba share, while still allowing users
- to modify the permission bits within that restriction.</para>
-
- <para>
- If you want to set up a share that allows users full control
- in modifying the permission bits on their files and directories and
- does not force any particular bits to be set <emphasis>on</emphasis>,
- then set the following parameters in the &smb.conf; file in that
- share-specific section:
- </para>
-
-<?latex \newpage ?>
- <smbconfblock>
- <smbconfoption name="security mask">0777</smbconfoption>
- <smbconfoption name="force security mode">0</smbconfoption>
- <smbconfoption name="directory security mask">0777</smbconfoption>
- <smbconfoption name="force directory security mode">0</smbconfoption>
- </smbconfblock>
-
-</sect2>
-
-<sect2>
- <title>Interaction with the Standard Samba File Attribute Mapping</title>
-
- <note>
- <para>
- Samba maps some of the DOS attribute bits (such as <quote>read-only</quote>)
- into the UNIX permissions of a file. This means there can
- be a conflict between the permission bits set via the security
- dialog and the permission bits set by the file attribute mapping.
- </para>
- </note>
-
- <para>
- If a file has no UNIX read access for the owner, it will show up
- as <quote>read-only</quote> in the standard file attributes tabbed dialog.
- Unfortunately, this dialog is the same one that contains the security information
- in another tab.
- </para>
-
- <para>
- What this can mean is that if the owner changes the permissions
- to allow himself or herself read access using the security dialog, clicks on
- <guibutton>OK</guibutton> to get back to the standard attributes tab
- dialog, and clicks on <guibutton>OK</guibutton> on that dialog, then
- NT will set the file permissions back to read-only (as that is what
- the attributes still say in the dialog). This means that after setting
- permissions and clicking on <guibutton>OK</guibutton> to get back to the
- attributes dialog, you should always press <guibutton>Cancel</guibutton>
- rather than <guibutton>OK</guibutton> to ensure that your changes
- are not overridden.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Windows NT/200X ACLs and POSIX ACLs Limitations</title>
-
- <para>
- Windows administrators are familiar with simple ACL controls, and they typically
- consider that UNIX user/group/other (ugo) permissions are inadequate and not
- sufficiently fine-grained.
- </para>
-
- <para>
- Competing SMB implementations differ in how they handle Windows ACLs. Samba handles
- Windows ACLs from the perspective of UNIX file system administration and thus adopts
- the limitations of POSIX ACLs. Therefore, where POSIX ACLs lack a capability of the
- Windows NT/200X ACLs, the POSIX semantics and limitations are imposed on the Windows
- administrator.
- </para>
-
- <para>
- POSIX ACLs present an interesting challenge to the UNIX administrator and therefore
- force a compromise to be applied to Windows ACLs administration. POSIX ACLs are not
- covered by an official standard; rather, the latest standard is a draft standard
- 1003.1e revision 17. This is the POSIX document on which the Samba implementation has
- been implemented.
- </para>
-
- <para>
- UNIX vendors differ in the manner in which POSIX ACLs are implemented. There are a
- number of Linux file systems that support ACLs. Samba has to provide a way to make
- transparent all the differences between the various implementations of POSIX ACLs.
- The pressure for ACLs support in Samba has noticeably increased the pressure to
- standardize ACLs support in the UNIX world.
- </para>
-
- <para>
- Samba has to deal with the complicated matter of handling the challenge of the Windows
- ACL that implements <emphasis>inheritance</emphasis>, a concept not anticipated by POSIX
- ACLs as implemented in UNIX file systems. Samba provides support for <emphasis>masks</emphasis>
- that permit normal ugo and ACLs functionality to be overridden. This further complicates
- the way in which Windows ACLs must be implemented.
- </para>
-
- <sect3>
- <title>UNIX POSIX ACL Overview</title>
-
- <para>
- In examining POSIX ACLs we must consider the manner in which they operate for
- both files and directories. File ACLs have the following significance:
-<screen>
-# file: testfile <- the file name
-# owner: jeremy <-- the file owner
-# group: users <-- the POSIX group owner
-user::rwx <-- perms for the file owner (user)
-user:tpot:r-x <-- perms for the additional user `tpot'
-group::r-- <-- perms for the file group owner (group)
-group:engrs:r-- <-- perms for the additonal group `engineers'
-mask:rwx <-- the mask that is `ANDed' with groups
-other::--- <-- perms applied to everyone else (other)
-</screen>
- Directory ACLs have the following signficance:
-<screen>
-# file: testdir <-- the directory name
-# owner: jeremy <-- the directory owner
-# group: jeremy <-- the POSIX group owner
-user::rwx <-- directory perms for owner (user)
-group::rwx <-- directory perms for owning group (group)
-mask::rwx <-- the mask that is `ANDed' with group perms
-other:r-x <-- perms applied to everyone else (other)
-default:user::rwx <-- inherited owner perms
-default:user:tpot:rwx <-- inherited extra perms for user `tpot'
-default:group::r-x <-- inherited group perms
-default:mask:rwx <-- inherited default mask
-default:other:--- <-- inherited permissions for everyone (other)
-</screen>
- </para>
-
- </sect3>
-
- <sect3>
- <title>Mapping of Windows File ACLs to UNIX POSIX ACLs</title>
-
- <para>
- Microsoft Windows NT4/200X ACLs must of necessity be mapped to POSIX ACLs.
- The mappings for file permissions are shown in <link linkend="fdsacls">How
- Windows File ACLs Map to UNIX POSIX File ACLs</link>.
- The # character means this flag is set only when the Windows administrator
- sets the <constant>Full Control</constant> flag on the file.
- </para>
-
- <table frame='all' pgwide='0' id="fdsacls"><title>How Windows File ACLs Map to UNIX POSIX File ACLs</title>
- <tgroup cols='2'>
- <colspec align="left"/>
- <colspec align="center"/>
- <thead>
- <row>
- <entry align="left">Windows ACE</entry>
- <entry align="center">File Attribute Flag</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><para>Full Control</para></entry>
- <entry><para>#</para></entry>
- </row>
- <row>
- <entry><para>Traverse Folder/Execute File</para></entry>
- <entry><para>x</para></entry>
- </row>
- <row>
- <entry><para>List Folder/Read Data</para></entry>
- <entry><para>r</para></entry>
- </row>
- <row>
- <entry><para>Read Attributes</para></entry>
- <entry><para>r</para></entry>
- </row>
- <row>
- <entry><para>Read Extended Attribures</para></entry>
- <entry><para>r</para></entry>
- </row>
- <row>
- <entry><para>Create Files/Write Data</para></entry>
- <entry><para>w</para></entry>
- </row>
- <row>
- <entry><para>Create Folders/Append Data</para></entry>
- <entry><para>w</para></entry>
- </row>
- <row>
- <entry><para>Write Attributes</para></entry>
- <entry><para>w</para></entry>
- </row>
- <row>
- <entry><para>Write Extended Attributes</para></entry>
- <entry><para>w</para></entry>
- </row>
- <row>
- <entry><para>Delete Subfolders and Files</para></entry>
- <entry><para>w</para></entry>
- </row>
- <row>
- <entry><para>Delete</para></entry>
- <entry><para>#</para></entry>
- </row>
- <row>
- <entry><para>Read Permissions</para></entry>
- <entry><para>all</para></entry>
- </row>
- <row>
- <entry><para>Change Permissions</para></entry>
- <entry><para>#</para></entry>
- </row>
- <row>
- <entry><para>Take Ownership</para></entry>
- <entry><para>#</para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- As can be seen from the mapping table, there is no one-to-one mapping capability, and therefore
- Samba must make a logical mapping that will permit Windows to operate more-or-less the way
- that is intended by the administrator.
- </para>
-
- <para>
- In general the mapping of UNIX POSIX user/group/other permissions will be mapped to
- Windows ACLs. This has precedence over the creation of POSIX ACLs. POSIX ACLs are necessary
- to establish access controls for users and groups other than the user and group that
- own the file or directory.
- </para>
-
- <para>
- The UNIX administrator can set any directory permission from within the UNIX environment.
- The Windows administrator is more restricted in that it is not possible from within
- Windows Explorer to remove read permission for the file owner.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Mapping of Windows Directory ACLs to UNIX POSIX ACLs</title>
-
- <para>
- Interesting things happen in the mapping of UNIX POSIX directory permissions and
- UNIX POSIX ACLs to Windows ACEs (Access Control Entries, the discrete components of
- an ACL) are mapped to Windows directory ACLs.
- </para>
-
- <para>
- Directory permissions function in much the same way as shown for file permissions, but
- there are some notable exceptions and a few peculiarities that the astute administrator
- will want to take into account in the setting up of directory permissions.
- </para>
-
- </sect3>
-
- </sect2>
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-File, directory, and share access problems are common topics on the mailing list. The following
-are examples recently taken from the mailing list.
-</para>
-
-
- <sect2>
- <title>Users Cannot Write to a Public Share</title>
-
- <para>
- The following complaint has frequently been voiced on the Samba mailing list:
- <quote>
- We are facing some troubles with file/directory permissions. I can log on the domain as admin user (root),
- and there's a public share on which everyone needs to have permission to create/modify files, but only
- root can change the file, no one else can. We need to constantly go to the server to
- <userinput>chgrp -R users *</userinput> and <userinput>chown -R nobody *</userinput> to allow
- other users to change the file.
- </quote>
- </para>
-
- <para>
- Here is one way the problem can be solved:
- </para>
-
- <procedure>
- <step>
- <para>
- Go to the top of the directory that is shared.
- </para>
- </step>
-
- <step>
- <para>
- Set the ownership to whatever public user and group you want
-<screen>
-&prompt;find `directory_name' -type d -exec chown user:group {}\;
-&prompt;find `directory_name' -type d -exec chmod 2775 {}\;
-&prompt;find `directory_name' -type f -exec chmod 0775 {}\;
-&prompt;find `directory_name' -type f -exec chown user:group {}\;
-</screen>
- </para>
-
- <note><para>
- The above will set the <constant>SGID bit</constant> on all directories. Read your
- UNIX/Linux man page on what that does. This ensures that all files and directories
- that are created in the directory tree will be owned by the current user and will
- be owned by the group that owns the directory in which it is created.
- </para></note>
- </step>
- <step>
- <para>
- Directory is <replaceable>/foodbar</replaceable>:
-<screen>
-&prompt;<userinput>chown jack:engr /foodbar</userinput>
-</screen>
- </para>
-
- <note>
- <para>This is the same as doing:</para>
-<screen>
-&prompt;<userinput>chown jack /foodbar</userinput>
-&prompt;<userinput>chgrp engr /foodbar</userinput>
-</screen>
- </note>
- </step>
- <step>
- <para>Now type:
-
-<screen>
-&prompt;<userinput>chmod 2775 /foodbar</userinput>
-&prompt;<userinput>ls -al /foodbar/..</userinput>
-</screen>
- </para>
-
- <para>You should see:
-<screen>
-drwxrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar
-</screen>
- </para>
- </step>
- <step>
-
- <para>Now type:
-<screen>
-&prompt;<userinput>su - jill</userinput>
-&prompt;<userinput>cd /foodbar</userinput>
-&prompt;<userinput>touch Afile</userinput>
-&prompt;<userinput>ls -al</userinput>
-</screen>
- </para>
-
- <para>
- You should see that the file <filename>Afile</filename> created by Jill will have ownership
- and permissions of Jack, as follows:
-<screen>
--rw-r--r-- 1 jill engr 0 2007-01-18 19:41 Afile
-</screen>
- </para>
- </step>
-
- <step>
- <para>
- If the user that must have write permission in the directory is not a member of the group
- <emphasis>engr</emphasis> set in the &smb.conf; entry for the share:
- <smbconfblock>
-<smbconfoption name="force group">engr</smbconfoption>
- </smbconfblock>
- </para>
- </step>
- </procedure>
- </sect2>
-
-
- <sect2>
- <title>File Operations Done as <emphasis>root</emphasis> with <emphasis>force user</emphasis> Set</title>
-
- <para>
- When you have a user in <smbconfoption name="admin users"/>, Samba will always do file operations for
- this user as <emphasis>root</emphasis>, even if <smbconfoption name="force user"/> has been set.
- </para>
- </sect2>
-
- <sect2>
- <title>MS Word with Samba Changes Owner of File</title>
-
- <para>
- <emphasis>Question:</emphasis> <quote>When user B saves a word document that is owned by user A,
- the updated file is now owned by user B. Why is Samba doing this? How do I fix this?</quote>
- </para>
-
- <para>
- <emphasis>Answer:</emphasis> Word does the following when you modify/change a Word document: MS Word creates a new document with
- a temporary name. Word then closes the old document and deletes it, then renames the new document to the original document name.
- There is no mechanism by which Samba can in any way know that the new document really should be owned by the owners
- of the original file. Samba has no way of knowing that the file will be renamed by MS Word. As far as Samba is able
- to tell, the file that gets created is a new file, not one that the application (Word) is updating.
- </para>
-
- <para>
- There is a workaround to solve the permissions problem. It involves understanding how you can manage file
- system behavior from within the &smb.conf; file, as well as understanding how UNIX file systems work. Set on the directory
- in which you are changing Word documents: <command>chmod g+s `directory_name'.</command> This ensures that all files will
- be created with the group that owns the directory. In &smb.conf; share declaration section set:
- </para>
-
- <para>
- <smbconfblock>
- <smbconfoption name="force create mode">0660</smbconfoption>
- <smbconfoption name="force directory mode">0770</smbconfoption>
- </smbconfblock>
- </para>
-
- <para>
- These two settings will ensure that all directories and files that get created in the share will be readable/writable by the
- owner and group set on the directory itself.
- </para>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="AdvancedNetworkManagement">
-<chapterinfo>
- &author.jht;
- <pubdate>June 15 2005</pubdate>
-</chapterinfo>
-
-<title>Advanced Network Management</title>
-
-<para>
-<indexterm><primary>access control</primary></indexterm>
-This section documents peripheral issues that are of great importance to network
-administrators who want to improve network resource access control, to automate the user
-environment, and to make their lives a little easier.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-Often the difference between a working network environment and a well-appreciated one can
-best be measured by the <emphasis>little things</emphasis> that make everything work more
-harmoniously. A key part of every network environment solution is the ability to remotely
-manage MS Windows workstations, remotely access the Samba server, provide customized
-logon scripts, as well as other housekeeping activities that help to sustain more reliable
-network operations.
-</para>
-
-<para>
-This chapter presents information on each of these areas. They are placed here, and not in
-other chapters, for ease of reference.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Remote Server Administration</title>
-
-
-<para><quote>How do I get User Manager and Server Manager?</quote></para>
-
-<para>
-<indexterm><primary>User Manager</primary></indexterm>
-<indexterm><primary>Server Manager</primary></indexterm>
-<indexterm><primary>Event Viewer</primary></indexterm>
-Since I do not need to buy an <application>NT4 server</application>, how do I get the User Manager for Domains
-and the Server Manager?
-</para>
-
-<para>
-<indexterm><primary>Nexus.exe</primary></indexterm>
-<indexterm><primary>Windows 9x/Me</primary></indexterm>
-Microsoft distributes a version of these tools called <filename>Nexus.exe</filename> for installation
-on <application>Windows 9x/Me</application> systems. The tools set includes:
-</para>
-
-<itemizedlist>
- <listitem><para>Server Manager</para></listitem>
- <listitem><para>User Manager for Domains</para></listitem>
- <listitem><para>Event Viewer</para></listitem>
-</itemizedlist>
-
-<para>
-Download the archived file at the Microsoft <ulink noescape="1"
-url="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE">Nexus</ulink> link.
-</para>
-
-<para>
-<indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
-<indexterm><primary>User Manager for Domains</primary></indexterm>
-<indexterm><primary>Server Manager</primary></indexterm>
-The <application>Windows NT 4.0</application> version of the User Manager for
-Domains and Server Manager are available from Microsoft
-<ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">via ftp</ulink>.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Remote Desktop Management</title>
-
-<para>
-<indexterm><primary>remote desktop management</primary></indexterm>
-<indexterm><primary>network environment</primary></indexterm>
-There are a number of possible remote desktop management solutions that range from free
-through costly. Do not let that put you off. Sometimes the most costly solution is the
-most cost effective. In any case, you will need to draw your own conclusions as to which
-is the best tool in your network environment.
-</para>
-
- <sect2>
- <title>Remote Management from NoMachine.Com</title>
-
- <para>
- <indexterm><primary>NoMachine.Com</primary></indexterm>
- The following information was posted to the Samba mailing list at Apr 3 23:33:50 GMT 2003.
- It is presented in slightly edited form (with author details omitted for privacy reasons).
- The entire answer is reproduced below with some comments removed.
- </para>
-
- <para><quote>
-<indexterm><primary>remote desktop capabilities</primary></indexterm>
- I have a wonderful Linux/Samba server running as PDC for a network. Now I would like to add remote
- desktop capabilities so users outside could login to the system and get their desktop up from home or
- another country.
- </quote></para>
-
- <para><quote>
-<indexterm><primary>Windows Terminal server</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>remote login</primary></indexterm>
- Is there a way to accomplish this? Do I need a Windows Terminal server? Do I need to configure it so
- it is a member of the domain or a BDC or PDC? Are there any hacks for MS Windows XP to enable remote login
- even if the computer is in a domain?
- </quote></para>
-
- <para>
- Answer provided: Check out the new offer of <quote>NX</quote> software from
- <ulink noescape="1" url="http://www.nomachine.com/">NoMachine</ulink>.
- </para>
-
- <para>
-<indexterm><primary>Remote X protocol</primary></indexterm>
-<indexterm><primary>VNC/RFB</primary></indexterm>
-<indexterm><primary>rdesktop/RDP</primary></indexterm>
- It implements an easy-to-use interface to the Remote X protocol as
- well as incorporating VNC/RFB and rdesktop/RDP into it, but at a speed
- performance much better than anything you may have ever seen.
- </para>
-
- <para>
-<indexterm><primary>modem/ISDN</primary></indexterm>
- Remote X is not new at all, but what they did achieve successfully is
- a new way of compression and caching technologies that makes the thing
- fast enough to run even over slow modem/ISDN connections.
- </para>
-
- <para>
-<indexterm><primary>KDE konqueror</primary></indexterm>
-<indexterm><primary>mouse-over</primary></indexterm>
-<indexterm><primary>rdesktop</primary></indexterm>
-<indexterm><primary></primary></indexterm>
- I test drove their (public) Red Hat machine in Italy, over a loaded
- Internet connection, with enabled thumbnail previews in KDE konqueror,
- which popped up immediately on <quote>mouse-over</quote>. From inside that (remote X)
- session I started a rdesktop session on another, a Windows XP machine.
- To test the performance, I played Pinball. I am proud to announce
- that my score was 631,750 points at first try.
- </para>
-
- <para>
-<indexterm><primary>NX</primary></indexterm>
-<indexterm><primary>TightVNC</primary></indexterm>
-<indexterm><primary>rdesktop</primary></indexterm>
-<indexterm><primary>Remote X</primary></indexterm>
- NX performs better on my local LAN than any of the other <quote>pure</quote>
- connection methods I use from time to time: TightVNC, rdesktop or
- Remote X. It is even faster than a direct crosslink connection between
- two nodes.
- </para>
-
- <para>
-<indexterm><primary>Remote X</primary></indexterm>
-<indexterm><primary>KDE session</primary></indexterm>
-<indexterm><primary>copy'n'paste</primary></indexterm>
- I even got sound playing from the Remote X app to my local boxes, and
- had a working <quote>copy'n'paste</quote> from an NX window (running a KDE session
- in Italy) to my Mozilla mailing agent. These guys are certainly doing
- something right!
- </para>
-
- <para>
- I recommend test driving NX to anybody with a only a passing interest in remote computing
- the <ulink noescape="1" url="http://www.nomachine.com/testdrive.php">NX</ulink> utility.
- </para>
-
- <para>
- Just download the free-of-charge client software (available for Red Hat,
- SuSE, Debian and Windows) and be up and running within 5 minutes (they
- need to send you your account data, though, because you are assigned
- a real UNIX account on their testdrive.nomachine.com box).
- </para>
-
- <para>
- They plan to get to the point were you can have NX application servers
- running as a cluster of nodes, and users simply start an NX session locally
- and can select applications to run transparently (apps may even run on
- another NX node, but pretend to be on the same as used for initial login,
- because it displays in the same window. You also can run it
- full-screen, and after a short time you forget that it is a remote session
- at all).
- </para>
-
- <para>
-<indexterm><primary>GPL</primary></indexterm>
- Now the best thing for last: All the core compression and caching
- technologies are released under the GPL and available as source code
- to anybody who wants to build on it! These technologies are working,
- albeit started from the command line only (and very inconvenient to
- use in order to get a fully running remote X session up and running).
- </para>
-
- <para>
- To answer your questions:
- </para>
-
- <itemizedlist>
- <listitem><para>
- You do not need to install a terminal server; XP has RDP support built in.
- </para></listitem>
-
- <listitem><para>
- NX is much cheaper than Citrix &smbmdash; and comparable in performance, probably faster.
- </para></listitem>
-
- <listitem><para>
- You do not need to hack XP &smbmdash; it just works.
- </para></listitem>
-
- <listitem><para>
- You log into the XP box from remote transparently (and I think there is no
- need to change anything to get a connection, even if authentication is against a domain).
- </para></listitem>
-
- <listitem><para>
- The NX core technologies are all Open Source and released under the GPL &smbmdash;
- you can now use a (very inconvenient) command line at no cost,
- but you can buy a comfortable (proprietary) NX GUI front end for money.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>OSS/Free Software</primary></indexterm>
-<indexterm><primary>LTSP</primary></indexterm>
-<indexterm><primary>KDE</primary></indexterm>
-<indexterm><primary>GNOME</primary></indexterm>
-<indexterm><primary>NoMachine</primary></indexterm>
- NoMachine is encouraging and offering help to OSS/Free Software implementations
- for such a front-end too, even if it means competition to them (they have written
- to this effect even to the LTSP, KDE, and GNOME developer mailing lists).
- </para></listitem>
- </itemizedlist>
-
- </sect2>
- <sect2>
- <title>Remote Management with ThinLinc</title>
- <para>
- Another alternative for remote access is <emphasis>ThinLinc</emphasis> from Cendio.
- </para>
-
- <para>
-<indexterm><primary>ThinLinc</primary></indexterm>
-<indexterm><primary>terminal server</primary></indexterm>
-<indexterm><primary>Linux</primary></indexterm>
-<indexterm><primary>Solaris</primary></indexterm>
-<indexterm><primary>TightVNC</primary></indexterm>
-<indexterm><primary>SSH</primary></indexterm>
-<indexterm><primary>NFS</primary></indexterm>
-<indexterm><primary>PulseAudio</primary></indexterm>
- ThinLinc is a terminal server solution that is available for Linux and Solaris based on standard
- protocols such as SSH, TightVNC, NFS and PulseAudio.
- </para>
-
- <para>
-<indexterm><primary>LAN</primary></indexterm>
-<indexterm><primary>thin client</primary></indexterm>
- ThinLinc can be used both in the LAN environment to implement a Thin Client strategy for an organization, and as
- secure remote access solution for people working from remote locations, even over smallband connections.
- ThinLinc is free to use for a single concurrent user.
- </para>
-
- <para>
-<indexterm><primary>Citrix</primary></indexterm>
-<indexterm><primary>Windows Terminal Server</primary></indexterm>
-<indexterm><primary>Java</primary></indexterm>
- The product can also be used as a frontend to access Windows Terminal Server or Citrix farms, or even Windows
- XP machines, securing the connection via the ssh protocol. The client is available both for Linux (supporting
- all Linux distributions as well as numerous thin terminals) and for Windows. A Java-based Web client is also
- available.
- </para>
-
- <para>
- ThinLinc may be evaluated by connecting to Cendio's demo system, see
- <ulink noescape="1" url="http://www.cendio.com">Cendio's</ulink> web site
- <ulink noescape="1" url="http://www.cendio.com/testdrive">testdrive</ulink> center.
- </para>
-
- <para>
- Cendio is a major contributor to several open source projects including
- <ulink noescape="1" url="http://www.tightvnc.com">TightVNC</ulink>,
- <ulink noescape="1" url="http://pulseaudio.org">PulseAudio</ulink> , unfsd,
- <ulink noescape="1" url="http://www.python.org">Python</ulink> and
- <ulink noescape="1" url="http://www.rdesktop.org">rdesktop</ulink>.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
-<title>Network Logon Script Magic</title>
-
-<para>
-There are several opportunities for creating a custom network startup configuration environment.
-</para>
-
-<itemizedlist>
- <listitem><para>No Logon Script.</para></listitem>
- <listitem><para>Simple universal Logon Script that applies to all users.</para></listitem>
- <listitem><para>Use of a conditional Logon Script that applies per-user or per-group attributes.</para></listitem>
- <listitem><para>Use of Samba's preexec and postexec functions on access to the NETLOGON share to create
- a custom logon script and then execute it.</para></listitem>
- <listitem><para>User of a tool such as KixStart.</para></listitem>
-</itemizedlist>
-
-<para>
-The Samba source code tree includes two logon script generation/execution tools.
-See <filename>examples</filename> directory <filename>genlogon</filename> and
-<filename>ntlogon</filename> subdirectories.
-</para>
-
-<para>
-The following listings are from the genlogon directory.
-</para>
-
-
-<para>
-<indexterm><primary>genlogon.pl</primary></indexterm>
-This is the <filename>genlogon.pl</filename> file:
-
-<programlisting>
- #!/usr/bin/perl
- #
- # genlogon.pl
- #
- # Perl script to generate user logon scripts on the fly, when users
- # connect from a Windows client. This script should be called from
- # smb.conf with the %U, %G and %L parameters. I.e:
- #
- # root preexec = genlogon.pl %U %G %L
- #
- # The script generated will perform
- # the following:
- #
- # 1. Log the user connection to /var/log/samba/netlogon.log
- # 2. Set the PC's time to the Linux server time (which is maintained
- # daily to the National Institute of Standards Atomic clock on the
- # internet.
- # 3. Connect the user's home drive to H: (H for Home).
- # 4. Connect common drives that everyone uses.
- # 5. Connect group-specific drives for certain user groups.
- # 6. Connect user-specific drives for certain users.
- # 7. Connect network printers.
-
- # Log client connection
- #($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
- ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
- open LOG, ">>/var/log/samba/netlogon.log";
- print LOG "$mon/$mday/$year $hour:$min:$sec";
- print LOG " - User $ARGV[0] logged into $ARGV[1]\n";
- close LOG;
-
- # Start generating logon script
- open LOGON, ">/shared/netlogon/$ARGV[0].bat";
- print LOGON "\@ECHO OFF\r\n";
-
- # Connect shares just use by Software Development group
- if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
- {
- print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
- }
-
- # Connect shares just use by Technical Support staff
- if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
- {
- print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
- }
-
- # Connect shares just used by Administration staff
- If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
- {
- print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
- print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
- }
-
- # Now connect Printers. We handle just two or three users a little
- # differently, because they are the exceptions that have desktop
- # printers on LPT1: - all other user's go to the LaserJet on the
- # server.
- if ($ARGV[0] eq 'jim'
- || $ARGV[0] eq 'yvonne')
- {
- print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
- print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
- }
- else
- {
- print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
- print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
- }
-
- # All done! Close the output file.
- close LOGON;
-</programlisting>
-</para>
-
-<para>
-Those wishing to use a more elaborate or capable logon processing system should check out these sites:
-</para>
-
-<itemizedlist>
- <listitem><para><ulink noescape="1" url="http://www.craigelachie.org/rhacer/ntlogon">http://www.craigelachie.org/rhacer/ntlogon</ulink></para></listitem>
- <listitem><para><ulink noescape="1" url="http://www.kixtart.org">http://www.kixtart.org</ulink></para></listitem>
-</itemizedlist>
-
-<sect2>
-<title>Adding Printers without User Intervention</title>
-
-
-<para>
-<indexterm><primary>rundll32</primary></indexterm>
-Printers may be added automatically during logon script processing through the use of:
-<screen>
-&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /?</userinput>
-</screen>
-
-See the documentation in the <ulink url="http://support.microsoft.com/default.asp?scid=kb;en-us;189105">Microsoft Knowledge Base article 189105</ulink>.
-</para>
-</sect2>
-
-<sect2>
- <title>Limiting Logon Connections</title>
-
- <para>
- Sometimes it is necessary to limit the number of concurrent connections to a
- Samba shared resource. For example, a site may wish to permit only one network
- logon per user.
- </para>
-
- <para>
- The Samba <parameter>preexec script</parameter> parameter can be used to permit only one
- connection per user. Though this method is not foolproof and may have side effects,
- the following contributed method may inspire someone to provide a better solution.
- </para>
-
- <para>
- This is not a perfect solution because Windows clients can drop idle connections
- with an auto-reconnect capability that could result in the appearance that a share
- is no longer in use, while actually it is. Even so, it demonstrates the principle
- of use of the <parameter>preexec script</parameter> parameter.
- </para>
-
- <para>
- The following share configuration demonstrates use of the script shown in <link linkend="Tpees"/>.
-<programlisting>
-[myshare]
- ...
- preexec script = /sbin/PermitSingleLogon.sh
- preexec close = Yes
- ...
-</programlisting>
- </para>
-
-<example id="Tpees">
-<title>Script to Enforce Single Resource Logon</title>
-<screen>
-#!/bin/bash
-
-IFS="-"
-RESULT=$(smbstatus -S -u $1 2> /dev/null | awk 'NF \
- > 6 {print $1}' | sort | uniq -d)
-
-if [ "X${RESULT}" == X ]; then
- exit 0
-else
- exit 1
-fi
-</screen>
-</example>
-
-</sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="samba-bdc">
-
-<chapterinfo>
- &author.jht;
- &author.vl;
- <author>&person.gd;<contrib>LDAP updates</contrib></author>
-</chapterinfo>
-
-<title>Backup Domain Control</title>
-
-<para>
-Before you continue reading this section, please make sure that you are comfortable
-with configuring a Samba domain controller as described in <link linkend="samba-pdc">Domain Control</link>.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-This is one of the most difficult chapters to summarize. It does not matter what we say here, for someone will
-still draw conclusions and/or approach the Samba Team with expectations that are either not yet capable of
-being delivered or that can be achieved far more effectively using a totally different approach. In the event
-that you should have a persistent concern that is not addressed in this book, please email <ulink
-url="mailto:jht@samba.org">John H. Terpstra</ulink> clearly setting out your requirements and/or question, and
-we will do our best to provide a solution.
-</para>
-
-<para>
-<indexterm><primary>SAM backend</primary><secondary>LDAP</secondary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>LDAP</primary><secondary>slave</secondary></indexterm>
-<indexterm><primary>scalability</primary></indexterm>
-Samba can act as a Backup Domain Controller (BDC) to another Samba Primary Domain Controller (PDC). A
-Samba PDC can operate with an LDAP account backend. The LDAP backend can be either a common master LDAP
-server or a slave server. The use of a slave LDAP server has the benefit that when the master is down, clients
-may still be able to log onto the network. This effectively gives Samba a high degree of scalability and is
-an effective solution for large organizations. If you use an LDAP slave server for a PDC, you will need to
-ensure the master's continued availability &smbmdash; if the slave finds its master down at the wrong time,
-you will have stability and operational problems.
-</para>
-
-<para>
-<indexterm><primary>two-way</primary><secondary>propagation</secondary></indexterm>
-<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
-<indexterm><primary>non-LDAP</primary><secondary>backend</secondary></indexterm>
-<indexterm><primary>propagate</primary></indexterm>
-It is not possible to run a Samba BDC with a non-LDAP backend, as that backend must allow some form of
-"two-way" propagation of changes from the BDC to the master. At this time only LDAP delivers the capability
-to propagate identity database changes from the BDC to the PDC. The BDC can use a slave LDAP server, while it
-is preferable for the PDC to use as its primary an LDAP master server.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Essential Background Information</title>
-
-<para>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>logon requests</primary></indexterm>
-<indexterm><primary>LanMan</primary></indexterm>
-<indexterm><primary>Netlogon</primary></indexterm>
-A domain controller is a machine that is able to answer logon requests from network
-workstations. Microsoft LanManager and IBM LanServer were two early products that
-provided this capability. The technology has become known as the LanMan Netlogon service.
-</para>
-
-<para>
-<indexterm><primary>network</primary><secondary>logon</secondary><tertiary>service</tertiary></indexterm>
-<indexterm><primary>Windows NT3.10</primary></indexterm>
-When MS Windows NT3.10 was first released, it supported a new style of Domain Control
-and with it a new form of the network logon service that has extended functionality.
-This service became known as the NT NetLogon Service. The nature of this service has
-changed with the evolution of MS Windows NT and today provides a complex array of
-services that are implemented over an intricate spectrum of technologies.
-</para>
-
-<sect2>
-<title>MS Windows NT4-style Domain Control</title>
-
-<para>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>authentication server</primary></indexterm>
-<indexterm><primary>username</primary></indexterm>
-<indexterm><primary>password</primary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>Security Account Manager</primary><see>SAM</see></indexterm>
-<indexterm><primary>domain control database</primary><see>SAM</see></indexterm>
-Whenever a user logs into a Windows NT4/200x/XP Professional workstation,
-the workstation connects to a domain controller (authentication server) to validate that
-the username and password the user entered are valid. If the information entered
-does not match account information that has been stored in the domain
-control database (the SAM, or Security Account Manager database), a set of error
-codes is returned to the workstation that has made the authentication request.
-</para>
-
-<para>
-<indexterm><primary>account information</primary></indexterm>
-<indexterm><primary>machine accounts database</primary></indexterm>
-<indexterm><primary>profile</primary></indexterm>
-<indexterm><primary>network access profile</primary></indexterm>
-<indexterm><primary>desktop profile</primary></indexterm>
-When the username/password pair has been validated, the domain controller
-(authentication server) will respond with full enumeration of the account information
-that has been stored regarding that user in the user and machine accounts database
-for that domain. This information contains a complete network access profile for
-the user but excludes any information that is particular to the user's desktop profile,
-or for that matter it excludes all desktop profiles for groups that the user may
-belong to. It does include password time limits, password uniqueness controls,
-network access time limits, account validity information, machine names from which the
-user may access the network, and much more. All this information was stored in the SAM
-in all versions of MS Windows NT (3.10, 3.50, 3.51, 4.0).
-</para>
-
-<para>
-<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
-<indexterm><primary>%SystemRoot%\System32\config</primary></indexterm>
-<indexterm><primary>C:\WinNT\System32\config</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
-The account information (user and machine) on domain controllers is stored in two files,
-one containing the security information and the other the SAM. These are stored in files
-by the same name in the <filename>%SystemRoot%\System32\config</filename> directory.
-This normally translates to the path <filename>C:\WinNT\System32\config</filename>. These
-are the files that are involved in replication of the SAM database where BDCs are present
-on the network.
-</para>
-
-<para>
-There are two situations in which it is desirable to install BDCs:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- On the local network that the PDC is on, if there are many
- workstations and/or where the PDC is generally very busy. In this case the BDCs
- will pick up network logon requests and help to add robustness to network services.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>network</primary><secondary>wide-area</secondary></indexterm>
- At each remote site, to reduce wide-area network traffic and to add stability to
- remote network operations. The design of the network, and the strategic placement of
- BDCs, together with an implementation that localizes as much of network to client
- interchange as possible, will help to minimize wide-area network bandwidth needs
- (and thus costs).
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>user account database</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>trigger</primary></indexterm>
-The interoperation of a PDC and its BDCs in a true Windows NT4 environment is worth
-mentioning here. The PDC contains the master copy of the SAM. In the event that an
-administrator makes a change to the user account database while physically present
-on the local network that has the PDC, the change will likely be made directly to
-the PDC instance of the master copy of the SAM. In the event that this update may
-be performed in a branch office, the change will likely be stored in a delta file
-on the local BDC. The BDC will then send a trigger to the PDC to commence the process
-of SAM synchronization. The PDC will then request the delta from the BDC and apply
-it to the master SAM. The PDC will then contact all the BDCs in the domain and
-trigger them to obtain the update and then apply that to their own copy of the SAM.
-</para>
-
-<para>
-<indexterm><primary>SAM</primary><secondary>replication</secondary></indexterm>
-<indexterm><primary>SAM</primary><secondary>delta file</secondary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-Samba cannot participate in true SAM replication and is therefore not able to
-employ precisely the same protocols used by MS Windows NT4. A Samba BDC will
-not create SAM update delta files. It will not interoperate with a PDC (NT4 or Samba)
-to synchronize the SAM from delta files that are held by BDCs.
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-Samba cannot function as a BDC to an MS Windows NT4 PDC, and Samba-3 cannot
-function correctly as a PDC to an MS Windows NT4 BDC. Both Samba and MS Windows
-NT4 can function as a BDC to its own type of PDC.
-</para>
-
-<para>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>domain security</primary></indexterm>
-The BDC is said to hold a <emphasis>read-only</emphasis> of the SAM from which
-it is able to process network logon requests and authenticate users. The BDC can
-continue to provide this service, particularly while, for example, the wide-area
-network link to the PDC is down. A BDC plays a very important role in both the
-maintenance of domain security as well as in network integrity.
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>promoted</primary></indexterm>
-<indexterm><primary>demoted</primary></indexterm>
-<indexterm><primary>reconfiguration</primary></indexterm>
-In the event that the NT4 PDC should need to be taken out of service, or if it dies, one of the NT4 BDCs can
-be promoted to a PDC. If this happens while the original NT4 PDC is online, it is automatically demoted to an
-NT4 BDC. This is an important aspect of domain controller management. The tool that is used to effect a
-promotion or a demotion is the Server Manager for Domains. It should be noted that Samba BDCs cannot be
-promoted in this manner because reconfiguration of Samba requires changes to the &smb.conf; file. It is easy
-enough to manuall change the &smb.conf; file and then restart relevant Samba network services.
-</para>
-
-<sect3>
-<title>Example PDC Configuration</title>
-
-<para>
-<indexterm><primary>domain logon</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-Beginning with Version 2.2, Samba officially supports domain logons for all current Windows clients, including
-Windows NT4, 2003, and XP Professional. For Samba to be enabled as a PDC, some parameters in the
-<smbconfsection name="[global]"/> section of the &smb.conf; have to be set. Refer to <link
-linkend="minimalPDC">the Minimal smb.conf for a PDC in Use with a BDC &smbmdash; LDAP Server on PDC
-section</link> for an example of the minimum required settings.
-</para>
-
-<example id="minimalPDC">
-<title>Minimal smb.conf for a PDC in Use with a BDC &smbmdash; LDAP Server on PDC</title>
-<smbconfblock>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-<smbconfoption name="passdb backend">ldapsam://localhost:389</smbconfoption>
-<smbconfoption name="domain master">yes</smbconfoption>
-<smbconfoption name="domain logons">yes</smbconfoption>
-<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=Users</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=Computers</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=sambadmin,dc=quenya,dc=org</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>profile path</primary></indexterm>
-<indexterm><primary>home drive</primary></indexterm>
-Several other things like a <smbconfsection name="[homes]"/> and a <smbconfsection name="[netlogon]"/> share
-also need to be set along with settings for the profile path, the user's home drive, and so on. This is not
-covered in this chapter; for more information please refer to <link linkend="samba-pdc">Domain Control</link>.
-Refer to <link linkend="samba-pdc">the Domain Control chapter</link> for specific recommendations for PDC
-configuration. Alternately, fully documented working example network configurations using OpenLDAP and Samba
-as available in the <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample">book</ulink> <quote>Samba-3
-by Example</quote> that may be obtained from local and on-line book stores.
-</para>
-
-</sect3>
-</sect2>
-
-<sect2>
-<title>LDAP Configuration Notes</title>
-
-<para>
-<indexterm><primary>LDAP</primary><secondary>master</secondary></indexterm>
-<indexterm><primary>LDAP</primary><secondary>slave</secondary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-When configuring a master and a slave LDAP server, it is advisable to use the master LDAP server
-for the PDC and slave LDAP servers for the BDCs. It is not essential to use slave LDAP servers; however,
-many administrators will want to do so in order to provide redundant services. Of course, one or more BDCs
-may use any slave LDAP server. Then again, it is entirely possible to use a single LDAP server for the
-entire network.
-</para>
-
-<para>
-<indexterm><primary>LDAP</primary><secondary>master</secondary></indexterm>
-<indexterm><primary>LDAP</primary><secondary>server</secondary></indexterm>
-<indexterm><primary>CN</primary></indexterm>
-<indexterm><primary>DN</primary></indexterm>
-<indexterm><primary>RFC2830</primary></indexterm>
-When configuring a master LDAP server that will have slave LDAP servers, do not forget to configure this in
-the <filename>/etc/openldap/slapd.conf</filename> file. It must be noted that the DN of a server certificate
-must use the CN attribute to name the server, and the CN must carry the servers' fully qualified domain name.
-Additional alias names and wildcards may be present in the subjectAltName certificate extension. More details
-on server certificate names are in RFC2830.
-</para>
-
-<para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>transport layer security</primary><see>TLS</see></indexterm>
-<indexterm><primary>/etc/ssl/certs/slapd.pem</primary></indexterm>
-<indexterm><primary>slapd.pem</primary></indexterm>
-<indexterm><primary>Red Hat Linux</primary></indexterm>
-It does not really fit within the scope of this document, but a working LDAP installation is basic to
-LDAP-enabled Samba operation. When using an OpenLDAP server with Transport Layer Security (TLS), the machine
-name in <filename>/etc/ssl/certs/slapd.pem</filename> must be the same as in
-<filename>/etc/openldap/sldap.conf</filename>. The Red Hat Linux startup script creates the
-<filename>slapd.pem</filename> file with hostname <quote>localhost.localdomain.</quote> It is impossible to
-access this LDAP server from a slave LDAP server (i.e., a Samba BDC) unless the certificate is re-created with
-a correct hostname.
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>machine account</primary></indexterm>
-<indexterm><primary>credentials</primary></indexterm>
-<indexterm><primary>replication</primary></indexterm>
-<indexterm><primary>duplicate</primary></indexterm>
-Do not install a Samba PDC so that is uses an LDAP slave server. Joining client machines to the domain
-will fail in this configuration because the change to the machine account in the LDAP tree must take place on
-the master LDAP server. This is not replicated rapidly enough to the slave server that the PDC queries. It
-therefore gives an error message on the client machine about not being able to set up account credentials. The
-machine account is created on the LDAP server, but the password fields will be empty. Unfortunately, some
-sites are unable to avoid such configurations, and these sites should review the <smbconfoption name="ldap
-replication sleep"/> parameter, intended to slow down Samba sufficiently for the replication to catch up.
-This is a kludge, and one that the administrator must manually duplicate in any scripts (such as the
-<smbconfoption name="add machine script"/>) that they use.
-</para>
-
-<para>
-Possible PDC/BDC plus LDAP configurations include:
-</para>
-
-<itemizedlist>
- <listitem><para>
- PDC+BDC -> One Central LDAP Server.
- </para></listitem>
- <listitem><para>
- PDC -> LDAP master server, BDC -> LDAP slave server.
- </para></listitem>
- <listitem><para>
- PDC -> LDAP master, with secondary slave LDAP server.
- </para><para>
- BDC -> LDAP master, with secondary slave LDAP server.
- </para></listitem>
- <listitem><para>
- PDC -> LDAP master, with secondary slave LDAP server.
- </para><para>
- BDC -> LDAP slave server, with secondary master LDAP server.
- </para></listitem>
-</itemizedlist>
-
-<para>
-In order to have a fallback configuration (secondary) LDAP server, you would specify
-the secondary LDAP server in the &smb.conf; file as shown in <link linkend="mulitldapcfg">the Multiple LDAP
-Servers in &smb.conf; example</link>.
-</para>
-
-<example id="mulitldapcfg">
-<title>Multiple LDAP Servers in &smb.conf;</title>
-<smbconfblock>
-<smbconfoption name="passdb backend">ldapsam:"ldap://master.quenya.org ldap://slave.quenya.org"</smbconfoption>
-</smbconfblock>
-</example>
-
-</sect2>
-
-<sect2>
-<title>Active Directory Domain Control</title>
-
-<para>
-<indexterm><primary>MS Windows 2000</primary></indexterm>
-<indexterm><primary>Active Directory</primary></indexterm>
-<indexterm><primary>directory</primary></indexterm>
-<indexterm><primary>replicated</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-As of the release of MS Windows 2000 and Active Directory, this information is now stored
-in a directory that can be replicated and for which partial or full administrative control
-can be delegated. Samba-4.0 is able to be a domain controller within an Active Directory
-tree, and it can be an Active Directory server. The details for how
-this can be done are documented in the <ulink
-url="https://wiki.samba.org/index.php/Samba4/HOWTO">Samba 4.0 as an
-AD DC HOWTO</ulink>
-
-</para>
-
-</sect2>
-
-<sect2>
-<title>What Qualifies a Domain Controller on the Network?</title>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-Every machine that is a domain controller for the domain MIDEARTH has to register the NetBIOS
-group name MIDEARTH<1C> with the WINS server and/or by broadcast on the local network.
-The PDC also registers the unique NetBIOS name MIDEARTH<1B> with the WINS server.
-The name type <1B> name is normally reserved for the Domain Master Browser (DMB), a role
-that has nothing to do with anything related to authentication, but the Microsoft domain
-implementation requires the DMB to be on the same machine as the PDC.
-</para>
-
-<para>
-<indexterm><primary>broadcast</primary></indexterm>
-<indexterm><primary>name registration</primary></indexterm>
-<indexterm><primary>SMB/CIFS</primary></indexterm>
-Where a WINS server is not used, broadcast name registrations alone must suffice. Refer to
-<link linkend="NetworkBrowsing">Network Browsing</link>,<link linkend="netdiscuss">Discussion</link>
-for more information regarding TCP/IP network protocols and how SMB/CIFS names are handled.
-</para>
-
-</sect2>
-
-<sect2>
-<title>How Does a Workstation find its Domain Controller?</title>
-
-<para>
-<indexterm><primary>locate domain controller</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-There are two different mechanisms to locate a domain controller: one method is used when
-NetBIOS over TCP/IP is enabled and the other when it has been disabled in the TCP/IP
-network configuration.
-</para>
-
-<para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>broadcast messaging</primary></indexterm>
-Where NetBIOS over TCP/IP is disabled, all name resolution involves the use of DNS, broadcast
-messaging over UDP, as well as Active Directory communication technologies. In this type of
-environment all machines require appropriate DNS entries. More information may be found in
-<link linkend="adsdnstech">DNS and Active Directory</link>.
-</para>
-
-<sect3>
-<title>NetBIOS Over TCP/IP Enabled</title>
-<para>
-<indexterm><primary>Windows NT4/200x/XP</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>logon requests</primary></indexterm>
-<indexterm><primary>credentials validation</primary></indexterm>
-An MS Windows NT4/200x/XP Professional workstation in the domain MIDEARTH that wants a
-local user to be authenticated has to find the domain controller for MIDEARTH. It does this
-by doing a NetBIOS name query for the group name MIDEARTH<1C>. It assumes that each
-of the machines it gets back from the queries is a domain controller and can answer logon
-requests. To not open security holes, both the workstation and the selected domain controller
-authenticate each other. After that the workstation sends the user's credentials (name and
-password) to the local domain controller for validation.
-</para>
-
-</sect3>
-
-<sect3>
-<title>NetBIOS Over TCP/IP Disabled</title>
-
-<para>
-<indexterm><primary>realm</primary></indexterm>
-<indexterm><primary>logon authentication</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>_ldap._tcp.pdc._msdcs.quenya.org</primary></indexterm>
-An MS Windows NT4/200x/XP Professional workstation in the realm <constant>quenya.org</constant>
-that has a need to affect user logon authentication will locate the domain controller by
-re-querying DNS servers for the <constant>_ldap._tcp.pdc._msdcs.quenya.org</constant> record.
-More information regarding this subject may be found in <link linkend="adsdnstech">DNS and Active Directory</link>.
-</para>
-
-</sect3>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Backup Domain Controller Configuration</title>
-
-<para>
-<indexterm><primary>BDC</primary></indexterm>
-The creation of a BDC requires some steps to prepare the Samba server before
-&smbd; is executed for the first time. These steps are as follows:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>secrets.tdb</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>LDAP administration password</primary></indexterm>
- Specification of the <smbconfoption name="ldap admin dn"/> is obligatory.
- This also requires the LDAP administration password to be set in the <filename>secrets.tdb</filename>
- using the <command>smbpasswd -w <replaceable>mysecret</replaceable></command>.
- </para></listitem>
-
- <listitem><para>
- The <smbconfoption name="ldap suffix"/> parameter and the <smbconfoption name="ldap idmap suffix"/>
- parameter must be specified in the &smb.conf; file.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
- <indexterm><primary>user database</primary></indexterm>
- <indexterm><primary>synchronized</primary></indexterm>
- <indexterm><primary>NIS</primary></indexterm>
- The UNIX user database has to be synchronized from the PDC to the
- BDC. This means that both the <filename>/etc/passwd</filename> and
- <filename>/etc/group</filename> have to be replicated from the PDC
- to the BDC. This can be done manually whenever changes are made.
- Alternately, the PDC is set up as an NIS master server and the BDC as an NIS slave
- server. To set up the BDC as a mere NIS client would not be enough,
- as the BDC would not be able to access its user database in case of
- a PDC failure. NIS is by no means the only method to synchronize
- passwords. An LDAP solution would also work.
- </para>
- </listitem>
-
- <listitem><para>
- <indexterm><primary>password database</primary></indexterm>
- <indexterm><primary>replicated</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>rsync</primary></indexterm>
- <indexterm><primary>ssh</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- The Samba password database must be replicated from the PDC to the BDC.
- The solution
- is to set up slave LDAP servers for each BDC and a master LDAP server for the PDC.
- The use of rsync is inherently flawed by the fact that the data will be replicated
- at timed intervals. There is no guarantee that the BDC will be operating at all
- times with correct and current machine and user account information. This means that
- this method runs the risk of users being inconvenienced by discontinuity of access
- to network services due to inconsistent security data. It must be born in mind that
- Windows workstations update (change) the machine trust account password at regular
- intervals &smbmdash; administrators are not normally aware that this is happening
- or when it takes place.
- </para>
-
- <para>
- <indexterm><primary>POSIX</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>SambaSAMAccount</primary></indexterm>
- <indexterm><primary>synchronize</primary></indexterm>
- The use of LDAP for both the POSIX (UNIX user and group) accounts and for the
- SambaSAMAccount data automatically ensures that all account change information
- will be written to the shared directory. This eliminates the need for any special
- action to synchronize account information because LDAP will meet that requirement.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>netlogon share</primary></indexterm>
- <indexterm><primary>replicate</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>cron</primary></indexterm>
- <indexterm><primary>rsync</primary></indexterm>
- The netlogon share has to be replicated from the PDC to the BDC. This can be done manually whenever login
- scripts are changed, or it can be done automatically using a <command>cron</command> job that will replicate
- the directory structure in this share using a tool like <command>rsync</command>. The use of
- <command>rsync</command> for replication of the netlogon data is not critical to network security and is one
- that can be manually managed given that the administrator will make all changes to the netlogon share as part
- of a conscious move.
- </para></listitem>
-
-</itemizedlist>
-
-<sect2>
-<title>Example Configuration</title>
-
-<para>
-Finally, the BDC has to be capable of being found by the workstations. This can be done by configuring the
-Samba &smb.conf; file <smbconfsection name="[global]"/> section as shown in <link linkend="minim-bdc">Minimal
-Setup for Being a BDC</link>.
-</para>
-
-<example id="minim-bdc">
-<title>Minimal Setup for Being a BDC</title>
-<smbconfblock>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-<smbconfoption name="passdb backend">ldapsam:ldap://slave-ldap.quenya.org</smbconfoption>
-<smbconfoption name="domain master">no</smbconfoption>
-<smbconfoption name="domain logons">yes</smbconfoption>
-<smbconfoption name="ldap suffix">dc=abmas,dc=biz</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=Users</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=Computers</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=sambadmin,dc=quenya,dc=org</smbconfoption>
-<smbconfoption name="idmap backend">ldap:ldap://master-ldap.quenya.org</smbconfoption>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-Fully documented working example network configurations using OpenLDAP and Samba
-as available in the <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample">book</ulink> <quote>Samba-3
-by Example</quote> that may be obtained from local and on-line book stores.
-</para>
-
-<para>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>group</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-This configuration causes the BDC to register only the name MIDEARTH<1C> with the WINS server. This is
-not a problem, as the name MIDEARTH<1C> is a NetBIOS group name that is meant to be registered by more
-than one machine. The parameter <smbconfoption name="domain master">no</smbconfoption> forces the BDC not to
-register MIDEARTH<1B>, which is a unique NetBIOS name that is reserved for the PDC.
-</para>
-
-<para>
-<indexterm><primary>idmap backend</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>redirect</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>LDAP database</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>nss_ldap</primary></indexterm>
-The <parameter>idmap backend</parameter> will redirect the <command>winbindd</command> utility to use the LDAP
-database to store all mappings for Windows SIDs to UIDs and GIDs for UNIX accounts in a repository that is
-shared. The BDC will however depend on local resolution of UIDs and GIDs via NSS and the
-<command>nss_ldap</command> utility.
-</para>
-
-<note><para>
-<indexterm><primary>Server Type</primary><secondary>Domain Member</secondary></indexterm>
-<indexterm><primary>ID mapping</primary></indexterm>
-<indexterm><primary>domain member server</primary></indexterm>
-<indexterm><primary>idmap backend</primary></indexterm>
-Samba has introduced a new ID mapping facility. One of the features of this facility is that it
-allows greater flexibility in how user and group IDs are handled in respect to NT domain user and group
-SIDs. One of the new facilities provides for explicitly ensuring that UNIX/Linux UID and GID values
-will be consistent on the PDC, all BDCs, and all domain member servers. The parameter that controls this
-is called <parameter>idmap backend</parameter>. Please refer to the man page for &smb.conf; for more information
-regarding its behavior.
-</para></note>
-
-<para>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>domain member servers</primary></indexterm>
-The use of the <smbconfoption name="idmap backend">ldap:ldap://master.quenya.org</smbconfoption>
-option on a BDC only makes sense where ldapsam is used on a PDC. The purpose of an LDAP-based idmap backend is
-also to allow a domain member (without its own passdb backend) to use winbindd to resolve Windows network users
-and groups to common UID/GIDs. In other words, this option is generally intended for use on BDCs and on domain
-member servers.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-<indexterm><primary>domain control</primary></indexterm>
-Domain control was a new area for Samba, but there are now many examples that we may refer to.
-Updated information will be published as they become available and may be found in later Samba releases or
-from the Samba Web <ulink url="https://www.samba.org">site</ulink>; refer in particular to the
-<filename>WHATSNEW.txt</filename> in the Samba release tarball. The book, <quote>Samba-3 by Example</quote>
-documents well tested and proven configuration examples. You can obtain a copy of this
-<ulink url="http://www.samba.org/samba/docs/Samba3-ByExample.pdf">book</ulink> for the Samba web site.
-</para>
-
-<sect2>
-<title>Machine Accounts Keep Expiring</title>
-
-<para>
-<indexterm><primary>Machine Trust Accounts</primary></indexterm>
-<indexterm><primary>passdb</primary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>Local Machine Trust Account</primary></indexterm>
-This problem will occur when the passdb (SAM) files are copied from a central
-server but the local BDC is acting as a PDC. This results in the application of
-Local Machine Trust Account password updates to the local SAM. Such updates
-are not copied back to the central server. The newer machine account password is then
-overwritten when the SAM is recopied from the PDC. The result is that the domain member machine
-on startup will find that its passwords do not match the one now in the database, and
-since the startup security check will now fail, this machine will not allow logon attempts
-to proceed and the account expiry error will be reported.
-</para>
-
-<para>
-The solution is to use a more robust passdb backend, such as the ldapsam backend, setting up
-a slave LDAP server for each BDC and a master LDAP server for the PDC.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Can Samba Be a Backup Domain Controller to an NT4 PDC?</title>
-
-<para>
-<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
-No. The native NT4 SAM replication protocols have not yet been fully implemented.
-</para>
-
-<para>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>logon requests</primary></indexterm>
-Can I get the benefits of a BDC with Samba? Yes, but only to a Samba
-PDC or as a <ulink
-url="https://wiki.samba.org/index.php/Samba4/HOWTO">Samba 4.0 Active
-Directory domain controller.</ulink> The
-main reason for implementing a BDC is availability. If the PDC is a Samba
-machine, a second Samba machine can be set up to service logon requests whenever
-the PDC is down.
-</para>
-
-</sect2>
-
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="Backup">
-<chapterinfo>
- &author.jht;
-</chapterinfo>
-
-<title>Backup Techniques</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>backup</primary></indexterm>
-<indexterm><primary>UNIX system files</primary></indexterm>
-<indexterm><primary>system tools</primary></indexterm>
-<indexterm><primary>Samba mailing lists</primary></indexterm>
-The Samba project is over 10 years old. During the early history
-of Samba, UNIX administrators were its key implementors. UNIX administrators
-use UNIX system tools to backup UNIX system files. Over the past
-4 years, an increasing number of Microsoft network administrators have
-taken an interest in Samba. This is reflected in the questions about backup
-in general on the Samba mailing lists.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Discussion of Backup Solutions</title>
-
-<para>
-<indexterm><primary>Meccano set</primary></indexterm>
-<indexterm><primary>training course</primary></indexterm>
-During discussions at a Microsoft Windows training course, one of
-the pro-UNIX delegates stunned the class when he pointed out that Windows
-NT4 is limiting compared with UNIX. He likened UNIX to a Meccano set
-that has an unlimited number of tools that are simple, efficient,
-and, in combination, capable of achieving any desired outcome.
-</para>
-
-<para>
-<indexterm><primary>networking advocates</primary></indexterm>
-<indexterm><primary>clear purpose preferred</primary></indexterm>
-One of the Windows networking advocates retorted that if she wanted a
-Meccano set, she would buy one. She made it clear that a complex single
-tool that does more than is needed but does it with a clear purpose and
-intent is preferred by some like her.
-</para>
-
-<para>
-<indexterm><primary>due diligence</primary></indexterm>
-<indexterm><primary>research</primary></indexterm>
-<indexterm><primary>backup solution</primary></indexterm>
-Please note that all information here is provided as is and without recommendation
-of fitness or suitability. The network administrator is strongly encouraged to
-perform due diligence research before implementing any backup solution, whether free
-software or commercial.
-</para>
-
-<para>
-A useful Web site I recently stumbled across that you might like to refer to
-is located at <ulink noescape="1" url="http://www.allmerchants.com/Software/Backup_Software/">
-www.allmerchants.com</ulink>.
-</para>
-
-<para>
-The following three free software projects might also merit consideration.
-</para>
-
- <sect2>
- <title>BackupPC</title>
-
-
- <para>
- <indexterm><primary>BackupPC</primary></indexterm>
-<indexterm><primary>rsync</primary></indexterm>
-<indexterm><primary>rsyncd</primary></indexterm>
- BackupPC version 2.0.0 has been released on <ulink url="http://backuppc.sourceforge.net">SourceForge</ulink>.
- New features include support for <command>rsync/rsyncd</command> and internationalization of the CGI interface
- (including English, French, Spanish, and German).
- </para>
-
- <para>
-<indexterm><primary>BackupPC</primary></indexterm>
-<indexterm><primary>laptops</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>smbclient</primary></indexterm>
-<indexterm><primary>tar</primary></indexterm>
-<indexterm><primary>rsh</primary></indexterm>
-<indexterm><primary>ssh</primary></indexterm>
-<indexterm><primary>rsync</primary></indexterm>
- BackupPC is a high-performance Perl-based package for backing up Linux,
- UNIX, and Windows PCs and laptops to a server's disk. BackupPC is highly
- configurable and easy to install and maintain. SMB (via smbclient),
- <command>tar</command> over <command>rsh/ssh</command>, or <command>rsync/rsyncd</command>
- are used to extract client data.
- </para>
-
- <para>
-<indexterm><primary>RAID</primary></indexterm>
-<indexterm><primary>local disk</primary></indexterm>
-<indexterm><primary>network storage</primary></indexterm>
- Given the ever-decreasing cost of disks and RAID systems, it is now
- practical and cost effective to backup a large number of machines onto
- a server's local disk or network storage. This is what BackupPC does.
- </para>
-
- <para>
- Key features are pooling of identical files (big savings in server disk
- space), compression, and a comprehensive CGI interface that allows users
- to browse backups and restore files.
- </para>
-
- <para>
-<indexterm><primary>GNU GPL</primary></indexterm>
- BackupPC is free software distributed under a GNU GPL license.
- BackupPC runs on Linux/UNIX/freenix servers and has been tested
- on Linux, UNIX, Windows 9x/Me, Windows 98, Windows 200x, Windows XP, and Mac OSX clients.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Rsync</title>
-
- <para>
-<indexterm><primary>rsync</primary></indexterm>
-<indexterm><primary>ftp</primary></indexterm>
-<indexterm><primary>http</primary></indexterm>
-<indexterm><primary>scp</primary></indexterm>
-<indexterm><primary>rcp</primary></indexterm>
-<indexterm><primary>checksum-search</primary></indexterm>
- <command>rsync</command> is a flexible program for efficiently copying files or
- directory trees.</para>
-
- <para><command>rsync</command> has many options to select which files will be copied
- and how they are to be transferred. It may be used as an
- alternative to <command>ftp, http, scp</command>, or <command>rcp</command>.</para>
-
- <para>
-<indexterm><primary>remote-update protocol</primary></indexterm>
-<indexterm><primary>transfer differences</primary></indexterm>
-<indexterm><primary>differences</primary></indexterm>
- The rsync remote-update protocol allows rsync to transfer just
- the differences between two sets of files across the network link,
- using an efficient checksum-search algorithm described in the
- technical report that accompanies the rsync package.</para>
-
- <para>Some of the additional features of rsync are:</para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Support for copying links, devices, owners, groups, and permissions.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Exclude and exclude-from options are similar to GNU tar.
- </para>
- </listitem>
-
- <listitem>
- <para>
- A CVS exclude mode for ignoring the same files that CVS would ignore.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Can use any transparent remote shell, including rsh or ssh.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Does not require root privileges.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Pipelining of file transfers to minimize latency costs.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Support for anonymous or authenticated rsync servers (ideal for
- mirroring).
- </para>
- </listitem>
- </itemizedlist>
-
- </sect2>
-
- <sect2>
- <title>Amanda</title>
-
-
- <para>
- <indexterm><primary>Amanda</primary></indexterm>
-<indexterm><primary>native dump</primary></indexterm>
-<indexterm><primary>GNU tar</primary></indexterm>
- Amanda, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that
- allows the administrator of a LAN to set up a single master backup server to back up
- multiple hosts to a single large capacity tape drive. Amanda uses native dump and/or
- GNU tar facilities and can back up a large number of workstations running multiple
- versions of UNIX. Recent versions can also use Samba to back up Microsoft Windows hosts.
- </para>
-
- <para>
- For more information regarding Amanda, please check the <ulink url="http://www.amanda.org/">
- www.amanda.org/ site</ulink>.
- </para>
-
- </sect2>
-
- <sect2>
- <title>BOBS: Browseable Online Backup System</title>
-
-
- <para>
- <indexterm><primary>BOBS</primary></indexterm>
- Browseable Online Backup System (BOBS) is a complete online backup system. Uses large
- disks for storing backups and lets users browse the files using a Web browser. Handles
- some special files like AppleDouble and icon files.
- </para>
-
- <para>
- The home page for BOBS is located at <ulink url="http://bobs.sourceforge.net/">
- bobs.sourceforge.net</ulink>.
- </para>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="bugreport">
-
-<chapterinfo>
- &author.jht;
- &author.jelmer;
- &author.tridge;
- <pubdate> 27 June 1997 </pubdate>
-</chapterinfo>
-
-<title>Reporting Bugs</title>
-
-<sect1>
-<title>Introduction</title>
-
-<para>
-<indexterm><primary>Bugzilla</primary></indexterm>
-<indexterm><primary>bug reports</primary></indexterm>
-Please report bugs using Samba's <ulink url="https://bugzilla.samba.org/">Bugzilla</ulink> facilities and take
-the time to read this file before you submit a bug report. Also, check to see if it has changed between
-releases, as we may be changing the bug reporting mechanism at some point.
-</para>
-
-<para>
-Please do as much as you can yourself to help track down the
-bug. Samba is maintained by a dedicated group of people who volunteer
-their time, skills, and efforts. We receive far more mail than
-we can possibly answer, so you have a much higher chance of a response
-and a fix if you send us a <quote>developer-friendly</quote> bug report that lets
-us fix it fast.
-</para>
-
-<para>
-<indexterm><primary>configuration problem</primary></indexterm>
-If you suspect that your
-problem is not a bug but a configuration problem, it is best to send
-it to the Samba mailing list, as there are thousands of other users on
-that list who may be able to help you.
-</para>
-
-<para>
-You may also like to look though the recent mailing list archives,
-which are conveniently accessible on the Samba Web pages
-at <ulink noescape="1" url="https://www.samba.org/samba/">https://www.samba.org/samba/</ulink>.
-</para>
-
-</sect1>
-
-<sect1>
-<title>General Information</title>
-
-<para>
-Before submitting a bug report, check your config for silly
-errors. Look in your log files for obvious messages that tell
-you've misconfigured something. Run testparm to check your config
-file for correct syntax.
-</para>
-
-<para>
-Have you looked through <link linkend="diagnosis">The Samba Checklist</link>? This is extremely important.
-</para>
-
-<para>
-If you include part of a log file with your bug report, then be sure to
-annotate it with exactly what you were doing on the client at the
-time and exactly what the results were.
-</para>
-
-</sect1>
-
-<sect1 id="dbglvl">
-<title>Debug Levels</title>
-
-<para>
-If the bug has anything to do with Samba behaving incorrectly as a
-server (like refusing to open a file), then the log files will probably
-be quite useful. Depending on the problem, a log level of between 3 and
-10 showing the problem may be appropriate. A higher level gives more
-detail but may use too much disk space.
-</para>
-
-<para>
-<indexterm><primary>debug level</primary></indexterm>
-<indexterm><primary>log level</primary></indexterm>
-To set the debug level, use the <smbconfoption name="log level"/> in your
-&smb.conf;. You may also find it useful to set the log
-level higher for just one machine and keep separate logs for each machine.
-To do this, add the following lines to your main &smb.conf; file:
-</para>
-
-<smbconfblock>
-<smbconfoption name="log level">10</smbconfoption>
-<smbconfoption name="log file">/usr/local/samba/lib/log.%m</smbconfoption>
-<smbconfoption name="include">/usr/local/samba/lib/smb.conf.%m</smbconfoption>
-</smbconfblock>
-
-<para>
-and create a file <filename>/usr/local/samba/lib/smb.conf.<replaceable>machine</replaceable></filename> where
-<replaceable>machine</replaceable> is the name of the client you wish to debug. In that file put any
-&smb.conf; commands you want; for example, <smbconfoption name="log level"/> may be useful. This also allows
-you to experiment with different security systems, protocol levels, and so on, on just one machine.
-</para>
-
-<para>
-The &smb.conf; entry <smbconfoption name="log level"/> is synonymous with the parameter <smbconfoption
-name="debuglevel"/> that has been used in older versions of Samba and is being retained for backward
-compatibility of &smb.conf; files.
-</para>
-
-<para>
-As the <smbconfoption name="log level"/> value is increased, you will record a significantly greater level of
-debugging information. For most debugging operations, you may not need a setting higher than
-<constant>3</constant>. Nearly all bugs can be tracked at a setting of <constant>10</constant>, but be
-prepared for a large volume of log data.
-</para>
-
- <sect2>
- <title>Debugging-Specific Operations</title>
-
- <para>
-<indexterm><primary>debugging</primary></indexterm>
-<indexterm><primary>logging</primary></indexterm>
-<indexterm><primary>functional components</primary></indexterm>
-<indexterm><primary>cluttering</primary></indexterm>
- Samba-3.x permits debugging (logging) of specific functional components without unnecessarily
- cluttering the log files with detailed logs for all operations. An example configuration to
- achieve this is shown in:
- </para>
-
-<para>
-<smbconfblock>
-<smbconfoption name="log level">0 tdb:3 passdb:5 auth:4 vfs:2</smbconfoption>
-<smbconfoption name="max log size">0</smbconfoption>
-<smbconfoption name="log file">/var/log/samba/%U.%m.log</smbconfoption>
-</smbconfblock>
-</para>
-
- <para>
- This will cause the level of detail to be expanded to the debug class (log level) passed to
- each functional area per the value shown above. The first value passed to the <parameter>log level</parameter>
- of <constant>0</constant> means turn off all unnecessary debugging except the debug classes set for
- the functional areas as specified. The table shown in <link linkend="dbgclass">Debuggable Functions</link>
- may be used to attain very precise analysis of each SMB operation Samba is conducting.
- </para>
-
- <table frame="all" id="dbgclass">
- <title>Debuggable Functions</title>
- <tgroup cols="2" align="center">
- <thead>
- <row><entry>Function Name</entry><entry>Function Name</entry></row>
- </thead>
- <tbody>
- <row><entry>all</entry><entry>passdb</entry></row>
- <row><entry>tdb</entry><entry>sam</entry></row>
- <row><entry>printdrivers</entry><entry>auth</entry></row>
- <row><entry>lanman</entry><entry>winbind</entry></row>
- <row><entry>smb</entry><entry>vfs</entry></row>
- <row><entry>rpc_parse</entry><entry>idmap</entry></row>
- <row><entry>rpc_srv</entry><entry>quota</entry></row>
- <row><entry>rpc_cli</entry><entry>acls</entry></row>
- </tbody>
- </tgroup>
- </table>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Internal Errors</title>
-
-<para>
-If you get the message <quote><errorname>INTERNAL ERROR</errorname></quote> in your log files,
-it means that Samba got an unexpected signal while running. It is probably a
-segmentation fault and almost certainly means a bug in Samba (unless
-you have faulty hardware or system software).
-</para>
-
-<para>
-If the message came from smbd, it will probably be accompanied by
-a message that details the last SMB message received by smbd. This
-information is often useful in tracking down the problem, so please
-include it in your bug report.
-</para>
-
-<para>
-You should also detail how to reproduce the problem, if
-possible. Please make this reasonably detailed.
-</para>
-
-
-<para>
-<indexterm><primary>core files</primary></indexterm>
-You may also find that a core file appeared in a <filename>corefiles</filename>
-subdirectory of the directory where you keep your Samba log
-files. This file is the most useful tool for tracking down the bug. To
-use it, you do this:
-<indexterm><primary>gdb</primary></indexterm>
-<indexterm><primary>debug</primary></indexterm>
-<screen>
-&prompt;<userinput>gdb smbd core</userinput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>dbx</primary></indexterm>
-<indexterm><primary>stack trace</primary></indexterm>
-adding appropriate paths to smbd and core so gdb can find them. If you
-do not have gdb, try <userinput>dbx</userinput>. Then within the debugger,
-use the command <command>where</command> to give a stack trace of where the
-problem occurred. Include this in your report.
-</para>
-
-<para>
-<indexterm><primary>disass</primary></indexterm>
-If you know any assembly language, do a <command>disass</command> of the routine
-where the problem occurred (if it's in a library routine, then
-disassemble the routine that called it) and try to work out exactly
-where the problem is by looking at the surrounding code. Even if you
-do not know assembly, including this information in the bug report can be
-useful.
-</para>
-</sect1>
-
-<sect1>
-<title>Attaching to a Running Process</title>
-
-<para>
-<indexterm><primary>PID</primary></indexterm>
-<indexterm><primary>gdb</primary></indexterm>
-<indexterm><primary>smbstatus</primary></indexterm>
-Unfortunately, some UNIXes (in particular some recent Linux kernels)
-refuse to dump a core file if the task has changed UID (which smbd
-does often). To debug with this sort of system, you could try to attach
-to the running process using
-<userinput>gdb smbd <replaceable>PID</replaceable></userinput>, where you get
-<replaceable>PID</replaceable> from <application>smbstatus</application>.
-Then use <command>c</command> to continue and try to cause the core dump
-using the client. The debugger should catch the fault and tell you
-where it occurred.
-</para>
-
-<para>
-Sometimes it is necessary to build Samba binary files that have debugging
-symbols so as to make it possible to capture enough information from a crashed
-operation to permit the Samba Team to fix the problem.
-</para>
-
-<para>
-Compile with <constant>-g</constant> to ensure you have symbols in place.
-Add the following line to the &smb.conf; file global section:
-<screen>
-panic action = "/bin/sleep 90000"
-</screen>
-to catch any panics. If <command>smbd</command> seems to be frozen, look for any sleep
-processes. If it is not, and appears to be spinning, find the PID
-of the spinning process and type:
-<screen>
-&rootprompt; gdb -p PID
-</screen>
-<indexterm><primary>spinning process</primary></indexterm>
-then type <quote>bt full</quote> to
-get a backtrace to see where the smbd is in the call path.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Patches</title>
-
-
-<para>
-<indexterm><primary>diff</primary></indexterm>
-<indexterm><primary>patch</primary></indexterm>
-The best sort of bug report is one that includes a fix! If you send us
-patches, please use <userinput>diff -u</userinput> format if your version of
-diff supports it; otherwise, use <userinput>diff -c4</userinput>. Make sure
-you do the diff against a clean version of the source and let me know
-exactly what version you used.
-</para>
-
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="CUPS-printing">
-
-<chapterinfo>
-
- <author>
- <firstname>Kurt</firstname><surname>Pfeifle</surname>
- <affiliation>
- <orgname>Danka Deutschland GmbH </orgname>
- <address><email>kpfeifle@danka.de</email></address>
- </affiliation>
- </author>
- <author>
- <firstname>Ciprian</firstname><surname>Vizitiu</surname>
- <affiliation>
- <address><email>CVizitiu@gbif.org</email></address>
- </affiliation>
- <contrib>drawings</contrib>
- </author>
-
- <author>&person.jelmer;<contrib>drawings</contrib></author>
-
- <pubdate> (27 Jan 2004) </pubdate>
-</chapterinfo>
-
-<title>CUPS Printing Support</title>
-
-<sect1>
-
- <title>Introduction</title>
-
- <sect2>
- <title>Features and Benefits</title>
-
- <para>
-<indexterm><primary>default printing</primary></indexterm>
- The Common UNIX Print System (<ulink url="http://www.cups.org/">CUPS</ulink>)
- has become quite popular. All major Linux distributions now ship it as their default printing
- system. To many, it is still a mystical tool. Mostly, it just works. People tend to regard
- it as a <quote>black box</quote> that they do not want to look into as long as it works. But once
- there is a little problem, they have trouble finding out where to start debugging it. Refer to
- <link linkend="classicalprinting">Classical Printing</link>, which contains much information
- that is also relevant to CUPS.
- </para>
-
- <para>
-<indexterm><primary>CUPS</primary></indexterm>
- CUPS sports quite a few unique and powerful features. While its basic functions may be grasped quite
- easily, they are also new. Because it is different from other, more traditional printing systems, it is best
- not to try to apply any prior knowledge about printing to this new system. Rather, try to understand CUPS from
- the beginning. This documentation will lead you to a complete understanding of CUPS. Let's start with the most
- basic things first.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Overview</title>
-
- <para>
-<indexterm><primary>print spooling system</primary></indexterm>
-<indexterm><primary>CUPS</primary></indexterm>
-<indexterm><primary>printer management system</primary></indexterm>
-<indexterm><primary>IETF</primary></indexterm>
-<indexterm><primary>Internet Printing Protocol</primary><see>IPP</see></indexterm>
-<indexterm><primary>Internet Engineering Task Force</primary><see>IETF</see></indexterm>
-<indexterm><primary>GUI</primary></indexterm>
-<indexterm><primary>KDEPrint</primary></indexterm>
- CUPS is more than just a print spooling system. It is a complete printer management system that
- complies with the new Internet Printing Protocol (IPP). IPP is an industry and Internet Engineering Task Force
- (IETF) standard for network printing. Many of its functions can be managed remotely (or locally) via a Web
- browser (giving you platform-independent access to the CUPS print server). Additionally, it has the
- traditional command line and several more modern GUI interfaces (GUI interfaces developed by third parties,
- like KDE's overwhelming <ulink url="http://printing.kde.org/">KDEPrint</ulink>).
- </para>
-
- <para>
-<indexterm><primary>raw printers</primary></indexterm>
-<indexterm><primary>smart printers</primary></indexterm>
- CUPS allows creation of <emphasis>raw</emphasis> printers (i.e., no print file format translation) as
- well as <emphasis>smart</emphasis> printers (i.e., CUPS does file format conversion as required for the
- printer). In many ways, this gives CUPS capabilities similar to the MS Windows print monitoring system. Of
- course, if you are a CUPS advocate, you would argue that CUPS is better! In any case, let us now explore how
- to configure CUPS for interfacing with MS Windows print clients via Samba.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Basic CUPS Support Configuration</title>
-
- <para>
-<indexterm><primary>CUPS</primary></indexterm>
-<indexterm><primary>cupsd.conf</primary></indexterm>
-<indexterm><primary>/etc/printcap</primary></indexterm>
-<indexterm><primary>Printcap</primary></indexterm>
-<indexterm><primary>PrintcapFormat</primary></indexterm>
-Printing with CUPS in the most basic &smb.conf; setup in Samba requires just this parameter: <smbconfoption name="printing">cups</smbconfoption>. CUPS does not need a printcap file. However, the
-<filename>cupsd.conf</filename> configuration file knows of two related directives that control how such a
-file will be automatically created and maintained by CUPS for the convenience of third-party applications
-(example: <parameter>Printcap /etc/printcap</parameter> and <parameter>PrintcapFormat BSD</parameter>).
-Legacy programs often require the existence of a printcap file containing printer names or they will refuse to
-print. Make sure CUPS is set to generate and maintain a printcap file. For details, see <command>man
-cupsd.conf</command> and other CUPS-related documentation, like the wealth of documents regarding the CUPS
-server itself available from the <ulink noescape="1"
-url="http://localhost:631/documentation.html">CUPS</ulink> web site.
- </para>
-
- <sect2>
- <title>Linking smbd with libcups.so</title>
-
- <para>
-<indexterm><primary>libcups.so</primary></indexterm>
- Samba has a special relationship to CUPS, and to use CUPS Samba must be compiled with CUPS library support.
- Most recent installations have this support enabled. By default, CUPS linking is compiled
- into smbd and other Samba binaries. The parameter
- <smbconfoption name="printing">cups</smbconfoption> will only
- be accepted if this is the case.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Simple &smb.conf; Settings for CUPS</title>
-
- <para>
- To summarize, <link linkend="cups-exam-simple">the Simplest Printing-Related
- &smb.conf; file</link> shows the simplest printing-related setup for &smb.conf; to
- enable basic CUPS support:
- </para>
-
- <example id="cups-exam-simple">
- <title>Simplest Printing-Related smb.conf</title>
- <smbconfblock>
- <smbconfsection name="[global]"/>
- <smbconfoption name="load printers">yes</smbconfoption>
- <smbconfoption name="printing">cups</smbconfoption>
-
- <smbconfsection name="[printers]"/>
- <smbconfoption name="comment">All Printers</smbconfoption>
- <smbconfoption name="path">/var/spool/samba</smbconfoption>
- <smbconfoption name="browseable">no</smbconfoption>
- <smbconfoption name="guest ok">yes</smbconfoption>
- <smbconfoption name="writable">no</smbconfoption>
- <smbconfoption name="printable">yes</smbconfoption>
- </smbconfblock>
- </example>
-
- <para>
-<indexterm><primary>PDF</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>printer driver</primary></indexterm>
- This is all you need for basic printing setup for CUPS. It will print all graphic, text, PDF, and PostScript
- files submitted from Windows clients. However, most of your Windows users would not know how to send these
- kinds of files to print without opening a GUI application. Windows clients tend to have local printer drivers
- installed, and the GUI application's print buttons start a printer driver. Your users also rarely send files
- from the command line. Unlike UNIX clients, they rarely submit graphic, text, or PDF formatted files directly
- to the spooler. They nearly exclusively print from GUI applications with a <quote>printer driver</quote>
- hooked between the application's native format and the print data stream. If the backend printer is not a
- PostScript device, the print data stream is <quote>binary,</quote> sensible only for the target printer. Read
- on to learn what problem this may cause and how to avoid it.
- </para>
-
- </sect2>
-
- <sect2>
- <title>More Complex CUPS &smb.conf; Settings</title>
-
- <para>
- <link linkend="overridesettings">The Overriding Global CUPS Settings for One Printer example</link>
- is a slightly more complex printing-related setup for &smb.conf;. It enables general CUPS printing
- support for all printers, but defines one printer share, which is set up differently.
- </para>
-
- <example id="overridesettings">
- <title>Overriding Global CUPS Settings for One Printer</title>
- <smbconfblock>
- <smbconfsection name="[global]"/>
- <smbconfoption name="printing">cups</smbconfoption>
- <smbconfoption name="load printers">yes</smbconfoption>
-
- <smbconfsection name="[printers]"/>
- <smbconfoption name="comment">All Printers</smbconfoption>
- <smbconfoption name="path">/var/spool/samba</smbconfoption>
- <smbconfoption name="guest ok">yes</smbconfoption>
- <smbconfoption name="writable">no</smbconfoption>
- <smbconfoption name="printable">yes</smbconfoption>
-
- <smbconfsection name="[special_printer]"/>
- <smbconfoption name="comment">A special printer with his own settings</smbconfoption>
- <smbconfoption name="path">/var/spool/samba-special</smbconfoption>
- <smbconfoption name="printing">sysv</smbconfoption>
- <smbconfoption name="printcap">lpstat</smbconfoption>
- <smbconfoption name="print command">echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log ; rm %f </smbconfoption>
- <smbconfoption name="guest ok">no</smbconfoption>
- <smbconfoption name="writable">no</smbconfoption>
- <smbconfoption name="printable">yes</smbconfoption>
- <smbconfoption name="hosts deny">0.0.0.0</smbconfoption>
- <smbconfoption name="hosts allow">turbo_xp, 10.160.50.23, 10.160.51.60</smbconfoption>
- </smbconfblock>
- </example>
-
- <para>
- This special share is only for testing purposes. It does not write the print job to a file. It just logs the job parameters
- known to Samba into the <filename>/tmp/smbprn.log</filename> file and deletes the job-file. Moreover, guest access is not
- allowed, the share isn't published to the Network Neighborhood (so you need to know it is there), and it
- allows access from only three hosts. To prevent CUPS from kicking in and taking over the print jobs for that share, we need to set
- <smbconfoption name="printing">sysv</smbconfoption> and <smbconfoption name="printcap">lpstat</smbconfoption>.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Advanced Configuration</title>
-
- <para>
- Before we delve into all the configuration options, let us clarify a few points. <emphasis>Network printing
- needs to be organized and set up correctly</emphasis>. This frequently doesn't happen. Legacy systems or small
- business LAN environments often lack design and good housekeeping.
- </para>
-
-
- <sect2>
- <title>Central Spooling vs. <quote>Peer-to-Peer</quote> Printing</title>
-
-
- <para>
-<indexterm><primary>spooling</primary></indexterm>
- <indexterm><primary>spooling</primary><secondary>central</secondary></indexterm>
- <indexterm><primary>spooling</primary><secondary>peer-to-peer</secondary></indexterm>
- Many small office or home networks, as well as badly organized larger environments, allow each client a direct
- access to available network printers. This is generally a bad idea. It often blocks one client's access to the
- printer when another client's job is printing. It might freeze the first client's application while it is
- waiting to get rid of the job. Also, there are frequent complaints about various jobs being printed with their
- pages mixed with each other. A better concept is the use of a print server: it routes all jobs through one
- central system, which responds immediately, takes jobs from multiple concurrent clients, and transfers them to
- the printer(s) in the correct order.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Raw Print Serving: Vendor Drivers on Windows Clients</title>
-
- <para>
- <indexterm><primary>spooling-only</primary></indexterm>
- <indexterm><primary>raw printing</primary></indexterm>
- Most traditionally configured UNIX print servers acting on behalf of
- Samba's Windows clients represented a really simple setup. Their only
- task was to manage the <quote>raw</quote> spooling of all jobs handed to them by
- Samba. This approach meant that the Windows clients were expected to
- prepare the print job file that is ready to be sent to the printing
- device. In this case, a native (vendor-supplied) Windows printer driver needs to
- be installed on each and every client for the target device.
- </para>
-
- <para>
-<indexterm><primary>render</primary></indexterm>
-<indexterm><primary>vendor-provided drivers</primary></indexterm>
- It is possible to configure CUPS, Samba, and your Windows clients in the
- same traditional and simple way. When CUPS printers are configured
- for raw print-through mode operation, it is the responsibility of the
- Samba client to fully render the print job (file). The file must be
- sent in a format that is suitable for direct delivery to the
- printer. Clients need to run the vendor-provided drivers to do
- this. In this case, CUPS will not do any print file format conversion
- work.
- </para>
-
- <para>
- The easiest printing configuration possible is raw print-through.
- This is achieved by installation of the printer as if it were physically
- attached to the Windows client. You then redirect output to a raw network
- print queue. This procedure may be followed to achieve this:
- </para>
-
- <procedure>
- <title>Configuration Steps for Raw CUPS Printing Support</title>
-
- <step><para>
-<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
- Edit <filename>/etc/cups/mime.types</filename> to uncomment the line
- near the end of the file that has:
-<screen>
-#application/octet-...
-</screen>
- </para></step>
-
- <step><para>
-<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
- Do the same for the file <filename>/etc/cups/mime.convs</filename>.
- </para></step>
-
- <step><para>
- Add a raw printer using the Web interface. Point your browser at
- <constant>http://localhost:631</constant>. Enter Administration, and add
- the printer following the prompts. Do not install any drivers for it.
- Choose Raw. Choose queue name <constant>Raw Queue</constant>.
- </para></step>
-
- <step><para>
- In the &smb.conf; file <constant>[printers]</constant> section add
- <smbconfoption name="use client driver">Yes</smbconfoption>,
- and in the <constant>[global]</constant> section add
- <smbconfoption name="printing">CUPS</smbconfoption>, plus
- <smbconfoption name="printcap">CUPS</smbconfoption>.
- </para></step>
-
- <step><para>
- Install the printer as if it is a local printer, that is, Printing to <constant>LPT1:</constant>.
- </para></step>
-
- <step><para>
- Edit the configuration under the <guimenu>Detail</guimenu> tab and create a
- <constant>local port</constant> that points to the raw printer queue that
- you have configured above. Example: <constant>\\server\raw_q</constant>.
- Here, the name <constant>raw_q</constant> is the name you gave the print
- queue in the CUPS environment.
- </para></step>
- </procedure>
-
- </sect2>
-
- <sect2>
- <title>Installation of Windows Client Drivers</title>
-
- <para>
- The printer drivers on the Windows clients may be installed
- in two functionally different ways:
- </para>
-
- <itemizedlist>
- <listitem><para>Manually install the drivers locally on each client,
- one by one; this yields the old LanMan style
- printing and uses a <filename>\\sambaserver\printershare</filename>
- type of connection.</para></listitem>
-
-
- <listitem><para>
- <indexterm><primary>point 'n' print</primary></indexterm>
- Deposit and prepare the drivers (for later download) on
- the print server (Samba); this enables the clients to use
- <quote>Point'n'Print</quote> to get drivers semi-automatically installed the
- first time they access the printer; with this method NT/200x/XP
- clients use the <emphasis>SPOOLSS/MS-RPC</emphasis>
- type printing calls.</para></listitem>
- </itemizedlist>
-
- <para>
- The second method is recommended for use over the first as it reduces the
- administrative efforts and prevents that different versions of the drivers
- are used accidentally.
- </para>
- </sect2>
-
- <sect2 id="cups-raw">
- <title>Explicitly Enable <quote>raw</quote> Printing for <emphasis>application/octet-stream</emphasis></title>
-
-
- <para>
- <indexterm><primary>application/octet-stream</primary></indexterm>
- <indexterm><primary>raw printing</primary></indexterm>
- <indexterm><primary>MIME</primary><secondary>raw</secondary></indexterm>
- If you use the first option (drivers are installed on the client
- side), there is one setting to take care of: CUPS needs to be told
- that it should allow <quote>raw</quote> printing of deliberate (binary) file
- formats. The CUPS files that need to be correctly set for raw mode
- printers to work are:
- </para>
-
- <itemizedlist>
- <listitem><para><filename>/etc/cups/mime.types</filename></para></listitem>
- <listitem><para><filename>/etc/cups/mime.convs</filename></para></listitem>
- </itemizedlist>
-
- <para>
- Both contain entries (at the end of the respective files) that must be uncommented to allow RAW mode
- operation. In <filename>/etc/cups/mime.types</filename>, make sure this line is present:
-<programlisting>
-application/octet-stream
-</programlisting>
- <indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
- <indexterm><primary>/etc/cups/mime.types</primary></indexterm>
- In <filename>/etc/cups/mime.convs</filename>, have this line:
- <indexterm><primary>application/vnd.cups-raw</primary></indexterm>
-<programlisting>
-application/octet-stream application/vnd.cups-raw 0 -
-</programlisting>
- If these two files are not set up correctly for raw Windows client
- printing, you may encounter the dreaded <computeroutput>Unable to
- convert file 0</computeroutput> in your CUPS <filename>error_log</filename> file.
- </para>
-
- <note><para>
- Editing the <filename>mime.convs</filename> and the <filename>mime.types</filename> file does
- not <emphasis>enforce</emphasis> <quote>raw</quote> printing, it only <emphasis>allows</emphasis> it.
- </para></note>
-
- <formalpara><title>Background</title>
-
- <para>
- <indexterm><primary>application/octet-stream</primary></indexterm>
-<indexterm><primary>MIME type</primary></indexterm>
- That CUPS is a more security-aware printing system than traditional ones does not by default allow a user to
- send deliberate (possibly binary) data to printing devices. This could be easily abused to launch a
- <quote>Denial of Service</quote> attack on your printer(s), causing at least the loss of a lot of paper and
- ink. <quote>Unknown</quote> data are tagged by CUPS as <parameter>MIME type: application/octet-stream</parameter>
- and not allowed to go to the printer. By default, you can only send other (known) MIME types <quote>raw.</quote>
- Sending data <quote>raw</quote> means that CUPS does not try to convert them and passes them to the printer
- untouched.
- </para>
- </formalpara>
-
- <para>
- This is all you need to know to get the CUPS/Samba combo printing
- <quote>raw</quote> files prepared by Windows clients, which have vendor drivers
- locally installed. If you are not interested in background information about
- more advanced CUPS/Samba printing, simply skip the remaining sections
- of this chapter.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Driver Upload Methods</title>
-
- <para>
- This section describes three familiar methods, plus one new one, by which
- printer drivers may be uploaded.
- </para>
-
- <para>
- <indexterm><primary>point'n'print</primary></indexterm>
- If you want to use the MS-RPC-type printing, you must upload the
- drivers onto the Samba server first (<smbconfsection name="[print$]"/>
- share). For a discussion on how to deposit printer drivers on the
- Samba host (so the Windows clients can download and use them via
- <quote>Point'n'Print</quote>), please refer to the <link linkend="classicalprinting">Classical Printing
- chapter</link> of this book. There you will find a description or reference to
- three methods of preparing the client drivers on the Samba server:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <indexterm><primary>add printer wizard</primary></indexterm>
- The GUI, <quote>Add Printer Wizard</quote> <emphasis>upload-from-a-Windows-client</emphasis> method.
- </para></listitem>
-
- <listitem><para>
- The command line, <quote>smbclient/rpcclient</quote> upload-from-a-UNIX-workstation method.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>imprints</primary></indexterm>
- The Imprints tool set method.
- </para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
- These three methods apply to CUPS all the same. The <command>cupsaddsmb</command> utility is a new and more
- convenient way to load the Windows drivers into Samba and is provided if you use CUPS.
- </para>
-
- <para>
- <command>cupsaddsmb</command> is discussed in much detail later in this chapter. But we first
- explore the CUPS filtering system and compare the Windows and UNIX printing architectures.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
- <title>Advanced Intelligent Printing with PostScript Driver Download</title>
-
- <para>
- <indexterm><primary>PostScript</primary><seealso>Ghostscript</seealso></indexterm>
- We now know how to set up a <quote>dump</quote> print server, that is, a server that spools
- print jobs <quote>raw</quote>, leaving the print data untouched.
- </para>
-
- <para>
- You might need to set up CUPS in a smarter way. The reasons could be manifold:
- </para>
-
-<indexterm><primary>print statistics</primary></indexterm>
-<indexterm><primary>average print run</primary></indexterm>
-<indexterm><primary>print quota</primary></indexterm>
- <itemizedlist>
- <listitem><para>Maybe your boss wants to get monthly statistics: Which
- printer did how many pages? What was the average data size of a job?
- What was the average print run per day? What are the typical hourly
- peaks in printing? Which department prints how much?</para></listitem>
-
- <listitem><para>Maybe you are asked to set up a print quota system:
- Users should not be able to print more jobs once they have surpassed
- a given limit per period.</para></listitem>
-
- <listitem><para>Maybe your previous network printing setup is a mess
- and must be re-organized from a clean beginning.</para></listitem>
-
- <listitem><para>Maybe you are experiencing too many <quote>blue screens</quote>
- originating from poorly debugged printer drivers running in NT <quote>kernel mode</quote>?</para></listitem>
- </itemizedlist>
-
- <para>
- These goals cannot be achieved by a raw print server. To build a
- server meeting these requirements, you'll first need to learn
- how CUPS works and how you can enable its features.
- </para>
-
- <para>
- What follows is the comparison of some fundamental concepts for
- Windows and UNIX printing, then a description of the
- CUPS filtering system, how it works, and how you can tweak it.
- </para>
-
- <sect2 id="gdipost">
- <title>GDI on Windows, PostScript on UNIX</title>
-
- <para>
- <indexterm><primary>GDI</primary></indexterm>
- <indexterm><primary>PostScript</primary></indexterm>
- Network printing is one of the most complicated and error-prone
- day-to-day tasks any user or administrator may encounter. This is
- true for all OS platforms, and there are reasons it is so.
- </para>
-
-
- <para>
- <indexterm><primary>PCL</primary></indexterm>
- <indexterm><primary>PDL</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>Adobe</primary></indexterm>
-<indexterm><primary>page description languages</primary><see>PDL</see></indexterm>
- You can't expect to throw just any file format at a printer and have it get printed. A file format conversion
- must take place. The problem is that there is no common standard for print file formats across all
- manufacturers and printer types. While PostScript (trademark held by Adobe) and, to an extent, PCL (trademark
- held by Hewlett-Packard) have developed into semi-official <quote>standards</quote> by being the most widely
- used page description languages (PDLs), there are still many manufacturers who <quote>roll their own</quote>
- (their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, and so on).
- </para>
-
- </sect2>
-
- <sect2>
- <title>Windows Drivers, GDI, and EMF</title>
-
- <para>
- <indexterm><primary>GDI</primary></indexterm>
- <indexterm><primary>EMF</primary></indexterm>
- <indexterm><primary>WYSIWYG</primary></indexterm>
-<indexterm><primary>Enhanced MetaFile</primary><see>EMF</see></indexterm>
- In Windows OS, the format conversion job is done by the printer drivers. On MS Windows OS platforms all
- application programmers have at their disposal a built-in API, the graphical device interface (GDI), as part
- and parcel of the OS itself to base themselves on. This GDI core is used as one common unified ground for all
- Windows programs to draw pictures, fonts, and documents <emphasis>on screen</emphasis> as well as <emphasis>on
- paper</emphasis> (print). Therefore, printer driver developers can standardize on a well-defined GDI output
- for their own driver input. Achieving WYSIWYG (What You See Is What You Get) is relatively easy, because the
- on-screen graphic primitives, as well as the on-paper drawn objects, come from one common source. This source,
- the GDI, often produces a file format called Enhanced MetaFile (EMF). The EMF is processed by the printer
- driver and converted to the printer-specific file format.
- </para>
-
- <note><para>
- <indexterm><primary>PDF</primary></indexterm>
-<indexterm><primary>Xprint</primary></indexterm>
-<indexterm><primary>core graphic engine</primary></indexterm>
- To the GDI foundation in MS Windows, Apple has chosen to put paper and screen output on a common foundation
- for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating <indexterm><primary>X Window
- System</primary></indexterm> <indexterm><primary>PostScript</primary></indexterm>
- <indexterm><primary>PCL</primary></indexterm> <indexterm><primary>Xprint</primary></indexterm> systems.
- Apple's <emphasis>core graphic engine</emphasis> uses a <emphasis>PDF</emphasis> derivative for all display work.
- </para></note>
-
- <para>
- The example in <link linkend="f1small">Windows Printing to a Local Printer</link> illustrates local Windows
- printing.
- </para>
-
- <figure id="f1small">
- <title>Windows Printing to a Local Printer.</title>
- <imagefile>1small</imagefile>
- </figure>
-
- </sect2>
-
- <sect2>
- <title>UNIX Printfile Conversion and GUI Basics</title>
-
- <para>
- <indexterm><primary>X Window System</primary></indexterm>
- <indexterm><primary>PostScript</primary></indexterm>
- <indexterm><primary>PCL</primary></indexterm>
- <indexterm><primary>Xprint</primary></indexterm>
- In UNIX and Linux, there is no comparable layer built into the OS kernel(s) or the X (screen display) server.
- Every application is responsible for itself to create its print output. Fortunately, most use PostScript and
- that at least gives some common ground. Unfortunately, there are many different levels of quality for this
- PostScript. And worse, there is a huge difference (and no common root) in the way the same document is
- displayed on screen and how it is presented on paper. WYSIWYG is more difficult to achieve. This goes back to
- the time, decades ago, when the predecessors of X.org, designing the UNIX foundations and protocols for
- graphical user interfaces, refused to take responsibility for <quote>paper output</quote>, as some had
- demanded at the time, and restricted itself to <quote>on-screen only.</quote> (For some years now, the
- <quote>Xprint</quote> project has been under development, attempting to build printing support into the X
- framework, including a PostScript and a PCL driver, but it is not yet ready for prime time.) You can see this
- unfavorable inheritance up to the present day by looking into the various <quote>font</quote> directories on
- your system; there are separate ones for fonts used for X display and fonts to be used on paper.
- </para>
-
- <formalpara>
- <title>Background</title>
-
- <para>
- <indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>color</primary></indexterm>
-<indexterm><primary>linewidth</primary></indexterm>
-<indexterm><primary>scale</primary></indexterm>
-<indexterm><primary>distort</primary></indexterm>
-<indexterm><primary>rotate</primary></indexterm>
-<indexterm><primary>shift</primary></indexterm>
-<indexterm><primary>raster images</primary></indexterm>
-<indexterm><primary>display PostScript</primary></indexterm>
-<indexterm><primary>graphical objects</primary></indexterm>
- The PostScript programming language is an <quote>invention</quote> by Adobe, but its specifications have been
- published extensively. Its strength lies in its powerful abilities to describe graphical objects (fonts,
- shapes, patterns, lines, curves, and dots), their attributes (color, linewidth), and the way to manipulate
- (scale, distort, rotate, shift) them. Because of its open specification, anybody with the skill can start
- writing his or her own implementation of a PostScript interpreter and use it to display PostScript files on
- screen or on paper. Most graphical output devices are based on the concept of <quote>raster images</quote> or
- <quote>pixels</quote> (one notable exception is pen plotters). Of course, you can look at a PostScript file in
- its textual form and you will be reading its PostScript code, the language instructions that need to be
- interpreted by a rasterizer. Rasterizers produce pixel images, which may be displayed on screen by a viewer
- program or on paper by a printer.
- </para>
- </formalpara>
- </sect2>
-
- <sect2 id="post-and-ghost">
- <title>PostScript and Ghostscript</title>
-
- <para>
- <indexterm><primary>PostScript</primary></indexterm>
- <indexterm><primary>GhostScript</primary><seealso>PostScript</seealso></indexterm>
- <indexterm><primary>PostScript</primary><secondary>RIP</secondary></indexterm>
-<indexterm><primary>PostScript interpreter</primary></indexterm>
-<indexterm><primary>raster image processor</primary><see>RIP</see></indexterm>
- So UNIX is lacking a common ground for printing on paper and displaying on screen. Despite this unfavorable
- legacy for UNIX, basic printing is fairly easy if you have PostScript printers at your disposal. The reason is
- that these devices have a built-in PostScript language <quote>interpreter,</quote> also called a raster image
- processor (RIP), (which makes them more expensive than other types of printers; throw PostScript toward them,
- and they will spit out your printed pages. The RIP does all the hard work of converting the PostScript drawing
- commands into a bitmap picture as you see it on paper, in a resolution as done by your printer. This is no
- different than PostScript printing a file from a Windows origin.
- </para>
-
- <note><para>
- <indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>PPD-aware</primary></indexterm>
-<indexterm><primary>PostScript Printer Description</primary><see>PPD</see></indexterm>
- Traditional UNIX programs and printing systems &smbmdash; while using PostScript &smbmdash; are largely not
- PPD-aware. PPDs are <quote>PostScript Printer Description</quote> files. They enable you to specify and
- control all options a printer supports: duplexing, stapling, and punching. Therefore, UNIX users for a long
- time couldn't choose many of the supported device and job options, unlike Windows or Apple users. But now
- there is CUPS. as illustrated in <link linkend="f2small">Printing to a PostScript Printer</link>.
- </para>
- </note>
-
- <figure id="f2small">
- <title>Printing to a PostScript Printer.</title>
- <imagefile>2small</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>PDL</primary></indexterm>
- However, there are other types of printers out there. These do not know how to print PostScript. They use
- their own PDL, often proprietary. To print to them is much more demanding. Since your UNIX applications mostly
- produce PostScript, and since these devices do not understand PostScript, you need to convert the print files
- to a format suitable for your printer on the host before you can send it away.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Ghostscript: The Software RIP for Non-PostScript Printers</title>
-
- <para>
- <indexterm><primary>GhostScript</primary></indexterm>
- Here is where Ghostscript kicks in. Ghostscript is the traditional (and quite powerful) PostScript interpreter
- used on UNIX platforms. It is a RIP in software, capable of doing a <emphasis>lot</emphasis> of file format
- conversions for a very broad spectrum of hardware devices as well as software file formats. Ghostscript
- technology and drivers are what enable PostScript printing to non-PostScript hardware. This is shown in
- <link linkend="f3small">Ghostscript as a RIP for Non-PostScript Printers</link>.
- </para>
-
- <figure id="f3small">
- <title>Ghostscript as a RIP for Non-PostScript Printers.</title>
- <imagefile>3small</imagefile>
- </figure>
-
- <tip><para>
-<indexterm><primary>PNG</primary></indexterm>
-<indexterm><primary>AFPL</primary></indexterm>
-<indexterm><primary>ESP</primary></indexterm>
- Use the <quote>gs -h</quote> command to check for all built-in <quote>devices</quote> on your Ghostscript
- version. If you specify a parameter of <parameter>-sDEVICE=png256</parameter> on your Ghostscript command
- line, you are asking Ghostscript to convert the input into a PNG file. Naming a <quote>device</quote> on the
- command line is the most important single parameter to tell Ghostscript exactly how it should render the
- input. New Ghostscript versions are released at fairly regular intervals, now by artofcode LLC. They are
- initially put under the <quote>AFPL</quote> license, but re-released under the GNU GPL as soon as the next
- AFPL version appears. GNU Ghostscript is probably the version installed on most Samba systems. But it has some
- deficiencies. <indexterm><primary>Ghostscript</primary><secondary>ESP</secondary><see>ESP
- GhostScript</see></indexterm> Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript,
- with lots of bug-fixes, additional devices, and improvements. It is jointly maintained by developers from
- CUPS, Gutenprint, MandrakeSoft, SuSE, Red Hat, and Debian. It includes the <quote>cups</quote> device
- (essential to print to non-PS printers from CUPS).
- </para></tip>
-
- </sect2>
-
- <sect2>
- <title>PostScript Printer Description (PPD) Specification</title>
-
- <para>
- <indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>PDL</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
- While PostScript in essence is a PDL to represent the page layout in a device-independent way, real-world
- print jobs are always ending up being output on hardware with device-specific features. To take care of all
- the differences in hardware and to allow for innovations, Adobe has specified a syntax and file format for
- PostScript Printer Description (PPD) files. Every PostScript printer ships with one of these files.
- </para>
-
- <para>
- PPDs contain all the information about general and special features of the
- given printer model: Which different resolutions can it handle? Does
- it have a duplexing unit? How many paper trays are there? What media
- types and sizes does it take? For each item, it also names the special
- command string to be sent to the printer (mostly inside the PostScript
- file) in order to enable it.
- </para>
-
- <para>
- Information from these PPDs is meant to be taken into account by the
- printer drivers. Therefore, installed as part of the Windows
- PostScript driver for a given printer is the printer's PPD. Where it
- makes sense, the PPD features are presented in the drivers' UI dialogs
- to display to the user a choice of print options. In the end, the
- user selections are somehow written (in the form of special
- PostScript, PJL, JCL, or vendor-dependent commands) into the PostScript
- file created by the driver.
- </para>
-
- <warning><para>
- <indexterm><primary>PDF</primary></indexterm>
-<indexterm><primary>PDF distilling</primary></indexterm>
- A PostScript file that was created to contain device-specific commands
- for achieving a certain print job output (e.g., duplexed, stapled, and
- punched) on a specific target machine may not print as expected, or
- may not be printable at all on other models; it also may not be fit
- for further processing by software (e.g., by a PDF distilling program).
- </para></warning>
- </sect2>
-
- <sect2>
- <title>Using Windows-Formatted Vendor PPDs</title>
-
- <para>
-<indexterm><primary>CUPS</primary></indexterm>
-<indexterm><primary>PPDs</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
- CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if
- a vendor does not mention our favorite OS in his or her manuals and brochures, you can safely trust this:
- <emphasis>If you get the Windows NT version of the PPD, you can use it unchanged in CUPS</emphasis> and thus
- access the full power of your printer just like a Windows NT user could!
- </para>
-
- <tip><para>
- To check the spec compliance of any PPD online, go to <ulink noescape="1"
- url="http://www.cups.org/testppd.php">http://www.cups.org/testppd.php</ulink> and upload your PPD. You will
- see the results displayed immediately. CUPS in all versions after 1.1.19 has a much stricter internal PPD
- parsing and checking code enabled; in case of printing trouble, this online resource should be one of your
- first pit stops.
- </para></tip>
-
- <warning><para>
- <indexterm><primary>foomatic</primary></indexterm>
- <indexterm><primary>cupsomatic</primary></indexterm>
- For real PostScript printers, <emphasis>do not</emphasis> use the <emphasis>Foomatic</emphasis> or
- <emphasis>cupsomatic</emphasis> PPDs from Linuxprinting.org. With these devices, the original vendor-provided
- PPDs are always the first choice.
- </para></warning>
-
- <tip><para>
-<indexterm><primary>W32X86/2</primary></indexterm>
- If you are looking for an original vendor-provided PPD of a specific device, and you know that an NT4 box (or
- any other Windows box) on your LAN has the PostScript driver installed, just use <command>smbclient
- //NT4-box/print\$ -U username</command> to access the Windows directory where all printer driver files are
- stored. First look in the <filename>W32X86/2</filename> subdirectory for the PPD you are seeking.
- </para></tip>
- </sect2>
-
- <sect2>
- <title>CUPS Also Uses PPDs for Non-PostScript Printers</title>
-
- <para>
-<indexterm><primary>non-PostScript</primary></indexterm>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>CUPS filtering</primary></indexterm>
- CUPS also uses specially crafted PPDs to handle non-PostScript printers. These PPDs are usually not available
- from the vendors (and no, you can't just take the PPD of a PostScript printer with the same model name and
- hope it works for the non-PostScript version too). To understand how these PPDs work for non-PS printers, we
- first need to dive deeply into the CUPS filtering and file format conversion architecture. Stay tuned.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>The CUPS Filtering Architecture</title>
-
-<para>
-<indexterm><primary>CUPS filtering</primary></indexterm>
-<indexterm><primary>Ghostscript</primary></indexterm>
-<indexterm><primary>MIME type</primary></indexterm>
-<indexterm><primary>MIME recognition</primary></indexterm>
-<indexterm><primary>MIME conversion rules</primary></indexterm>
-The core of the CUPS filtering system is based on Ghostscript. In addition to Ghostscript, CUPS uses some
-other filters of its own. You (or your OS vendor) may have plugged in even more filters. CUPS handles all data
-file formats under the label of various MIME types. Every incoming print file is subjected to an initial
-autotyping. The autotyping determines its given MIME type. A given MIME type implies zero or more possible
-filtering chains relevant to the selected target printer. This section discusses how MIME types recognition
-and conversion rules interact. They are used by CUPS to automatically set up a working filtering chain for any
-given input data format.
-</para>
-
-<para>
-If CUPS rasterizes a PostScript file natively to a bitmap, this is done in two stages:
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>generic raster format</primary></indexterm>
-<indexterm><primary>CUPS raster</primary></indexterm>
- The first stage uses a Ghostscript device named <quote>cups</quote>
- (this is since version 1.1.15) and produces a generic raster format
- called <quote>CUPS raster</quote>.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>raster driver</primary></indexterm>
- The second stage uses a <quote>raster driver</quote> that converts
- the generic CUPS raster to a device-specific raster.
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>Ghostscript</primary></indexterm>
-<indexterm><primary>GNU Ghostscript</primary></indexterm>
-<indexterm><primary>ESP Ghostscript</primary></indexterm>
-Make sure your Ghostscript version has the <quote>cups</quote> device compiled in (check with <command>gs -h |
-grep cups</command>). Otherwise you may encounter the dreaded <computeroutput>Unable to convert file
-0</computeroutput> in your CUPS error_log file. To have <quote>cups</quote> as a device in your Ghostscript,
-you either need to patch GNU Ghostscript and recompile or use
-<indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm><ulink
-url="http://www.cups.org/ghostscript.php">ESP Ghostscript</ulink>. The superior alternative is ESP
-Ghostscript. It supports not just CUPS, but 300 other devices (while GNU Ghostscript supports only about 180).
-Because of this broad output device support, ESP Ghostscript is the first choice for non-CUPS spoolers, too.
-It is now recommended by Linuxprinting.org for all spoolers.
-</para>
-
-<para>
-<indexterm><primary>cupsomatic</primary></indexterm>
-<indexterm><primary>foomatic</primary></indexterm>
-<indexterm><primary>foomatic-rip</primary></indexterm>
-<indexterm><primary>ESP Ghostscript</primary></indexterm>
-CUPS printers may be set up to use external rendering paths. One of the most common is provided by the
-Foomatic/cupsomatic concept from <ulink url="http://www.linuxprinting.org/">Linuxprinting.org</ulink>. This
-uses the classical Ghostscript approach, doing everything in one step. It does not use the
-<quote>cups</quote> device, but one of the many others. However, even for Foomatic/cupsomatic usage, best
-results and <indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm> broadest printer
-model support is provided by ESP Ghostscript (more about Foomatic/cupsomatic, particularly the new version
-called now <emphasis>foomatic-rip</emphasis>, follows).
-</para>
-
- <sect2>
- <title>MIME Types and CUPS Filters</title>
-
-
- <para>
- <indexterm><primary>MIME</primary><secondary>filters</secondary></indexterm>
- <indexterm><primary>MIME</primary></indexterm>
-<indexterm><primary>mime.types</primary></indexterm>
-<indexterm><primary>application/pdf</primary></indexterm>
-<indexterm><primary>autotyping</primary></indexterm>
- CUPS reads the file <filename>/etc/cups/mime.types</filename> (and all other files carrying a
- <filename>*.types</filename> suffix in the same directory) upon startup. These files contain the MIME type
- recognition rules that are applied when CUPS runs its autotyping routines. The rule syntax is explained in the
- man page for <filename>mime.types</filename> and in the comments section of the
- <filename>mime.types</filename> file itself. A simple rule reads like this:
- <indexterm><primary>application/pdf</primary></indexterm>
-<programlisting>
-application/pdf pdf string(0,%PDF)
-</programlisting>
-<indexterm><primary>%PDF</primary></indexterm>
-<indexterm><primary>.pdf</primary></indexterm>
- This means if a filename has a <filename>.pdf</filename> suffix or if the magic string
- <emphasis>%PDF</emphasis> is right at the beginning of the file itself (offset 0 from the start), then it is a
- PDF file (<parameter>application/pdf</parameter>). Another rule is this:
-<programlisting>
-application/postscript ai eps ps string(0,%!) string(0,<04>%!)
-</programlisting>
-<indexterm><primary>suffixes</primary></indexterm>
-<indexterm><primary>.ai</primary></indexterm>
-<indexterm><primary>.eps</primary></indexterm>
-<indexterm><primary>.ps</primary></indexterm>
-<indexterm><primary>generic PostScript</primary></indexterm>
-<indexterm><primary>application/postscript</primary></indexterm>
- If the filename has one of the suffixes <filename>.ai</filename>, <filename>.eps</filename>,
- <filename>.ps</filename>, or if the file itself starts with one of the strings <emphasis>%!</emphasis> or
- <emphasis><![CDATA[<04>%!]]></emphasis>, it is a generic PostScript file
- (<parameter>application/postscript</parameter>).
- </para>
-
- <warning><para>
-<indexterm><primary>/etc/cups/</primary></indexterm>
- Don't confuse the other mime.types files your system might be using
- with the one in the <filename>/etc/cups/</filename> directory.
- </para></warning>
-
- <note><para>
-<indexterm><primary>application/postscript</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>filter</primary></indexterm>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>transformation</primary></indexterm>
- There is an important difference between two similar MIME types in CUPS: one is
- <parameter>application/postscript</parameter>, the other is
- <parameter>application/vnd.cups-postscript</parameter>. While <parameter>application/postscript</parameter> is
- meant to be device-independent, job options for the file are still outside the PS file content, embedded in
- command line or environment variables by CUPS, <parameter>application/vnd.cups-postscript</parameter> may have
- the job options inserted into the PostScript data itself (where applicable). The transformation of the generic
- PostScript (<parameter>application/postscript</parameter>) to the device-specific version
- (<parameter>application/vnd.cups-postscript</parameter>) is the responsibility of the CUPS
- <parameter>pstops</parameter> filter. pstops uses information contained in the PPD to do the transformation.
- </para></note>
-
- <para>
-<indexterm><primary>ASCII</primary></indexterm>
-<indexterm><primary>HP-GL</primary></indexterm>
-<indexterm><primary>PDF</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>DVI</primary></indexterm>
-<indexterm><primary>GIF</primary></indexterm>
-<indexterm><primary>PNG</primary></indexterm>
-<indexterm><primary>TIFF</primary></indexterm>
-<indexterm><primary>JPEG</primary></indexterm>
-<indexterm><primary>Photo-CD</primary></indexterm>
-<indexterm><primary>SUN-Raster</primary></indexterm>
-<indexterm><primary>PNM</primary></indexterm>
-<indexterm><primary>PBM</primary></indexterm>
-<indexterm><primary>SGI-RGB</primary></indexterm>
-<indexterm><primary>MIME</primary></indexterm>
-<indexterm><primary>filters</primary></indexterm>
- CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI, and
- many image formats (GIF, PNG, TIFF, JPEG, Photo-CD, SUN-Raster,
- PNM, PBM, SGI-RGB, and more) and their associated MIME types
- with its filters.
- </para>
-
- </sect2>
-
- <sect2>
- <title>MIME Type Conversion Rules</title>
-
-
- <para>
- <indexterm><primary>MIME</primary></indexterm>
- <indexterm><primary>application/pdf</primary></indexterm>
-<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
-<indexterm><primary>application/pdf</primary></indexterm>
-<indexterm><primary>application/postscript</primary></indexterm>
- CUPS reads the file <filename>/etc/cups/mime.convs</filename>
- (and all other files named with a <filename>*.convs</filename>
- suffix in the same directory) upon startup. These files contain
- lines naming an input MIME type, an output MIME type, a format
- conversion filter that can produce the output from the input type,
- and virtual costs associated with this conversion. One example line
- reads like this:
-<programlisting>
-application/pdf application/postscript 33 pdftops
-</programlisting>
-<indexterm><primary>pdftops</primary></indexterm>
- This means that the <parameter>pdftops</parameter> filter will take
- <parameter>application/pdf</parameter> as input and produce
- <parameter>application/postscript</parameter> as output; the virtual
- cost of this operation is 33 CUPS-$. The next filter is more
- expensive, costing 66 CUPS-$:
- <indexterm><primary>pdf</primary></indexterm>
-<programlisting>
-application/vnd.hp-HPGL application/postscript 66 hpgltops
-</programlisting>
-<indexterm><primary>hpgltops</primary></indexterm>
- This is the <parameter>hpgltops</parameter>, which processes HP-GL
- plotter files to PostScript.
- <indexterm><primary>application/octet-stream</primary></indexterm>
-<programlisting>
-application/octet-stream
-</programlisting>
- Here are two more examples:
- <indexterm><primary>text/plain</primary></indexterm>
-<indexterm><primary>application/x-shell</primary></indexterm>
-<indexterm><primary>text/plain</primary></indexterm>
-<indexterm><primary>texttops</primary></indexterm>
-<programlisting>
-application/x-shell application/postscript 33 texttops
-text/plain application/postscript 33 texttops
-</programlisting>
-<indexterm><primary>application/x-shell</primary></indexterm>
- The last two examples name the <parameter>texttops</parameter> filter to work on
- <parameter>text/plain</parameter> as well as on <parameter>application/x-shell</parameter>. (Hint: This
- differentiation is needed for the syntax highlighting feature of <parameter>texttops</parameter>).
- </para>
- </sect2>
-
- <sect2>
- <title>Filtering Overview</title>
-
- <para>
- <indexterm><primary>MIME</primary></indexterm>
- There are many more combinations named in <filename>mime.convs</filename>. However, you are not limited to use
- the ones predefined there. You can plug in any filter you like to the CUPS framework. It must meet, or must be
- made to meet, some minimal requirements. If you find (or write) a cool conversion filter of some kind, make
- sure it complies with what CUPS needs and put in the right lines in <filename>mime.types</filename> and
- <filename>mime.convs</filename>; then it will work seamlessly inside CUPS.
- </para>
-
- <sect3>
- <title>Filter Requirements</title>
-
- <para>
- The <quote>CUPS requirements</quote> for filters are simple. Take filenames or <filename>stdin</filename> as
- input and write to <filename>stdout</filename>. They should take these arguments:
- </para>
-
- <variablelist>
- <varlistentry><term>printer</term>
- <listitem><para>
- The name of the printer queue (normally this is the name of the filter being run).
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>job</term>
- <listitem><para>
- The numeric job ID for the job being printed.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>user</term>
- <listitem><para>
- The string from the originating-user-name attribute.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>title</term>
- <listitem><para>
- The string from the job-name attribute.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>copies</term>
- <listitem><para>
- The numeric value from the number-copies attribute.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>options</term>
- <listitem><para>
- The job options.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>filename</term>
- <listitem><para>
- (optionally) The print request file (if missing, filters expect data
- fed through <filename>stdin</filename>). In most cases, it is easy to
- write a simple wrapper script around existing filters to make them work with CUPS.
- </para></listitem>
- </varlistentry>
- </variablelist>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Prefilters</title>
-
- <para>
- <indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>non-PostScript printers</primary></indexterm>
-<indexterm><primary>raster</primary></indexterm>
- As previously stated, PostScript is the central file format to any UNIX-based
- printing system. From PostScript, CUPS generates raster data to feed
- non-PostScript printers.
- </para>
-
- <para>
-<indexterm><primary>prefilters</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>ASCII text</primary></indexterm>
-<indexterm><primary>PDF</primary></indexterm>
-<indexterm><primary>DVI</primary></indexterm>
-<indexterm><primary>HP-GL.</primary></indexterm>
-<indexterm><primary>MIME type</primary></indexterm>
-<indexterm><primary>application/postscript</primary></indexterm>
-<indexterm><primary>pstops</primary></indexterm>
-<indexterm><primary>application/vnd.cups-postscript</primary></indexterm>
- But what happens if you send one of the supported non-PS formats to print? Then CUPS runs
- <quote>prefilters</quote> on these input formats to generate PostScript first. There are prefilters to create
- PostScript from ASCII text, PDF, DVI, or HP-GL. The outcome of these filters is always of MIME type
- <parameter>application/postscript</parameter> (meaning that any device-specific print options are not yet
- embedded into the PostScript by CUPS and that the next filter to be called is pstops). Another prefilter is
- running on all supported image formats, the <parameter>imagetops</parameter> filter. Its outcome is always of
- MIME type <parameter>application/vnd.cups-postscript</parameter> (not application/postscript), meaning it has
- the print options already embedded into the file. This is shown in <link linkend="f4small">Prefiltering in
- CUPS to Form PostScript</link>.
- </para>
-
- <figure id="f4small">
- <title>Prefiltering in CUPS to Form PostScript.</title>
- <imagefile scale="25">4small</imagefile>
- </figure>
-
- </sect2>
-
- <sect2>
- <title>pstops</title>
-
- <para>
-<indexterm><primary>pstops</primary></indexterm>
-<indexterm><primary>application/postscript</primary></indexterm>
-<indexterm><primary>application/vnd.cups-postscript</primary></indexterm>
-<indexterm><primary>output duplexing</primary></indexterm>
-<indexterm><primary>stapling</primary></indexterm>
-<indexterm><primary>punching</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
- <emphasis>pstops</emphasis> is a filter that is used to convert <parameter>application/postscript</parameter> to
- <parameter>application/vnd.cups-postscript</parameter>. As stated earlier, this filter inserts all
- device-specific print options (commands to the printer to ask for the duplexing of output, or stapling and
- punching it, and so on) into the PostScript file. An example is illustrated in <link
- linkend="f5small">Adding Device-Specific Print Options</link>.
- </para>
-
- <figure id="f5small">
- <title>Adding Device-Specific Print Options.</title>
- <imagefile scale="25">5small</imagefile>
- </figure>
-
- <para>
- This is not all. Other tasks performed by it are:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Selecting the range of pages to be printed (e.g., you can choose to
- print only pages <quote>3, 6, 8-11, 16, and 19-21</quote>, or only odd-numbered
- pages).
- </para></listitem>
-
- <listitem><para>
- Putting two or more logical pages on one sheet of paper (the
- so-called <quote>number-up</quote> function).
- </para></listitem>
-
- <listitem><para>Counting the pages of the job to insert the accounting
- information into the <filename>/var/log/cups/page_log</filename>.
- </para></listitem>
- </itemizedlist>
- </sect2>
-
- <sect2>
- <title>pstoraster</title>
-
- <para>
-<indexterm><primary>pstoraster</primary></indexterm>
-<indexterm><primary>rasterization</primary></indexterm>
-<indexterm><primary>raster drivers</primary></indexterm>
- <parameter>pstoraster</parameter> is at the core of the CUPS filtering system. It is responsible for the first
- stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; its output is
- application/vnd.cups-raster. This output format is not yet meant to be printable. Its aim is to serve as a
- general-purpose input format for more specialized <emphasis>raster drivers</emphasis> that are able to
- generate device-specific printer data. This is shown in <link linkend="cups-raster">the PostScript to
- Intermediate Raster Format diagram</link>.
- </para>
-
- <figure id="cups-raster">
- <title>PostScript to Intermediate Raster Format.</title>
- <imagefile scale="25">6small</imagefile>
- </figure>
-
- <para>
-<indexterm><primary>CUPS raster</primary></indexterm>
-<indexterm><primary>generic raster</primary></indexterm>
-<indexterm><primary>IANA</primary></indexterm>
-<indexterm><primary>raster drivers</primary></indexterm>
- CUPS raster is a generic raster format with powerful features. It is able to include per-page information,
- color profiles, and more, to be used by the downstream raster drivers. Its MIME type is registered with IANA
- and its specification is, of course, completely open. It is designed to make it quite easy and inexpensive for
- manufacturers to develop Linux and UNIX raster drivers for their printer models should they choose to do so.
- CUPS always takes care of the first stage of rasterization so these vendors do not need to care about
- Ghostscript complications (in fact, there are currently more than one vendor financing the development of CUPS
- raster drivers). This is illustrated in <link linkend="cups-raster2">the CUPS-Raster Production Using
- Ghostscript illustration</link>.
- </para>
-
- <figure id="cups-raster2">
- <title>CUPS-Raster Production Using Ghostscript.</title>
- <imagefile>7small</imagefile>
- </figure>
-
- <para>
-<indexterm><primary>pstoraster</primary></indexterm>
-<indexterm><primary>GNU Ghostscript</primary></indexterm>
-<indexterm><primary>AFPL Ghostscript</primary></indexterm>
-<indexterm><primary>standalone filter</primary></indexterm>
- CUPS versions before version 1.1.15 shipped a binary (or source code) standalone filter, named
- <parameter>pstoraster</parameter>. <parameter>pstoraster</parameter>, which was derived from GNU Ghostscript
- 5.50 and could be installed instead of and in addition to any GNU or AFPL Ghostscript package without
- conflicting.
- </para>
-
- <para>
- Since version 1.1.15, this feature has changed. The functions for this filter have been integrated back
- into Ghostscript (now based on GNU Ghostscript version 7.05). The <parameter>pstoraster</parameter> filter is
- now a simple shell script calling <command>gs</command> with the <command>-sDEVICE=cups</command> parameter.
- If your Ghostscript fails when this command is executed: <command>gs -h |grep cups</command>, you might not
- be able to print, update your Ghostscript.
- </para>
- </sect2>
-
- <sect2>
- <title>imagetops and imagetoraster</title>
-
- <para>
-<indexterm><primary>prefilter</primary></indexterm>
-<indexterm><primary>imagetoraster</primary></indexterm>
- In the section about prefilters, we mentioned the prefilter
- that generates PostScript from image formats. The <parameter>imagetoraster</parameter>
- filter is used to convert directly from image to raster, without the
- intermediate PostScript stage. It is used more often than the previously
- mentioned prefilters. We summarize in a flowchart the image file
- filtering in <link linkend="small8">the Image Format to CUPS-Raster Format Conversion illustration</link>.
- </para>
-
- <figure id="small8">
- <title>Image Format to CUPS-Raster Format Conversion.</title>
- <imagefile>8small</imagefile>
- </figure>
-
- </sect2>
-
- <sect2>
- <title>rasterto [printers specific]</title>
-
- <para>
-<indexterm><primary>rastertoalps</primary></indexterm>
-<indexterm><primary>rastertobj</primary></indexterm>
-<indexterm><primary>rastertoepson</primary></indexterm>
-<indexterm><primary>rastertoescp</primary></indexterm>
-<indexterm><primary>rastertopcl</primary></indexterm>
-<indexterm><primary>rastertoturboprint</primary></indexterm>
-<indexterm><primary>rastertoescp</primary></indexterm>
-<indexterm><primary>rastertohp</primary></indexterm>
-<indexterm><primary>rastertoprinter</primary></indexterm>
-<indexterm><primary>rastertoprinter</primary></indexterm>
-<indexterm><primary>Gutenprint</primary></indexterm>
- CUPS ships with quite a variety of raster drivers for processing CUPS raster. On my system, I find in
- /usr/lib/cups/filter/ the following: <parameter>rastertoalps</parameter>, <parameter>rastertobj</parameter>,
- <parameter>rastertoepson</parameter>, <parameter>rastertoescp</parameter>, <parameter>rastertopcl</parameter>,
- <parameter>rastertoturboprint</parameter>, <parameter>rastertoapdk</parameter>,
- <parameter>rastertodymo</parameter>, <parameter>rastertoescp</parameter>, <parameter>rastertohp</parameter>,
- and <parameter>rastertoprinter</parameter>. Don't worry if you have fewer drivers than this; some of these are
- installed by commercial add-ons to CUPS (like <parameter>rastertoturboprint</parameter>), and others (like
- <parameter>rastertoprinter</parameter>) by third-party driver development projects (such as Gutenprint)
- wanting to cooperate as closely as possible with CUPS. See <link linkend="small9">the Raster to
- Printer-Specific Formats illustration</link>.
- </para>
-
- <figure id="small9">
- <title>Raster to Printer-Specific Formats.</title>
- <imagefile>9small</imagefile>
- </figure>
- </sect2>
-
- <sect2>
- <title>CUPS Backends</title>
-
- <para>
-<indexterm><primary>CUPS filtering chain</primary></indexterm>
-<indexterm><primary>print queue</primary></indexterm>
- The last part of any CUPS filtering chain is a backend. Backends
- are special programs that send the print-ready file to the final
- device. There is a separate backend program for any transfer
- protocol for sending print jobs over the network, and one for every local
- interface. Every CUPS print queue needs to have a CUPS <quote>device-URI</quote>
- associated with it. The device URI is the way to encode the backend
- used to send the job to its destination. Network device-URIs use
- two slashes in their syntax, local device URIs only one, as you can
- see from the following list. Keep in mind that local interface names
- may vary greatly from my examples, if your OS is not Linux:
- </para>
-
- <variablelist>
- <varlistentry><term>usb</term>
- <listitem><para>
- This backend sends print files to USB-connected printers. An
- example for the CUPS device-URI to use is
- <filename>usb:/dev/usb/lp0</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>serial</term>
- <listitem><para>
- This backend sends print files to serially connected printers.
- An example for the CUPS device-URI to use is
- <filename>serial:/dev/ttyS0?baud=11500</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>parallel</term>
- <listitem><para>
- This backend sends print files to printers connected to the
- parallel port. An example for the CUPS device-URI to use is
- <filename>parallel:/dev/lp0</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>SCSI</term>
- <listitem><para>
- This backend sends print files to printers attached to the
- SCSI interface. An example for the CUPS device-URI to use is
- <filename>scsi:/dev/sr1</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>lpd</term>
- <listitem><para>
- This backend sends print files to LPR/LPD-connected network
- printers. An example for the CUPS device-URI to use is
- <filename>lpd://remote_host_name/remote_queue_name</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>AppSocket/HP JetDirect</term>
- <listitem><para>
- This backend sends print files to AppSocket (a.k.a., HP
- JetDirect) connected network printers. An example for the CUPS
- device-URI to use is
- <filename>socket://10.11.12.13:9100</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>ipp</term>
- <listitem><para>
- This backend sends print files to IPP-connected network
- printers (or to other CUPS servers). Examples for CUPS device-URIs
- to use are
- <filename>ipp:://192.193.194.195/ipp</filename>
- (for many HP printers) and
- <filename>ipp://remote_cups_server/printers/remote_printer_name</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>http</term>
- <listitem><para>
- This backend sends print files to HTTP-connected printers.
- (The http:// CUPS backend is only a symlink to the ipp:// backend.)
- Examples for the CUPS device-URIs to use are
- <filename>http:://192.193.194.195:631/ipp</filename>
- (for many HP printers) and
- <filename>http://remote_cups_server:631/printers/remote_printer_name</filename>.
- </para></listitem></varlistentry>
-
- <varlistentry><term>smb</term>
- <listitem><para>
- This backend sends print files to printers shared by a Windows
- host. Examples of CUPS device-URIs that may be used includes:
- </para>
-
- <para>
- <simplelist>
- <member><filename>smb://workgroup/server/printersharename</filename></member>
- <member><filename>smb://server/printersharename</filename></member>
- <member><filename>smb://username:password@workgroup/server/printersharename</filename></member>
- <member><filename>smb://username:password@server/printersharename</filename></member>
- </simplelist>
- </para>
-
- <para>
- The smb:// backend is a symlink to the Samba utility
- <parameter>smbspool</parameter> (does not ship with CUPS). If the
- symlink is not present in your CUPS backend directory, have your
- root user create it: <command>ln -s `which smbspool'
- /usr/lib/cups/backend/smb</command>.
- </para></listitem></varlistentry>
- </variablelist>
-
- <para>
- It is easy to write your own backends as shell or Perl scripts if you
- need any modification or extension to the CUPS print system. One
- reason could be that you want to create <quote>special</quote> printers that send
- the print jobs as email (through a <quote>mailto:/</quote> backend), convert them to
- PDF (through a <quote>pdfgen:/</quote> backend) or dump them to <quote>/dev/null</quote>. (In
- fact, I have the systemwide default printer set up to be connected to
- a devnull:/ backend: there are just too many people sending jobs
- without specifying a printer, and scripts and programs that do not name
- a printer. The systemwide default deletes the job and sends a polite
- email back to the $USER asking him or her to always specify the correct
- printer name.)
- </para>
-
- <para>
-<indexterm><primary>lpinfo</primary></indexterm>
-<indexterm><primary>CUPS backends</primary></indexterm>
- Not all of the mentioned backends may be present on your system or
- usable (depending on your hardware configuration). One test for all
- available CUPS backends is provided by the <emphasis>lpinfo</emphasis>
- utility. Used with the <option>-v</option> parameter, it lists
- all available backends:
- </para>
-
- <para><screen>
- &prompt;<userinput>lpinfo -v</userinput>
- </screen></para>
- </sect2>
-
- <sect2>
- <title>The Role of <parameter>cupsomatic/foomatic</parameter></title>
-
- <para>
- <indexterm><primary>cupsomatic</primary></indexterm>
- <indexterm><primary>foomatic</primary></indexterm>
-<indexterm><primary>PPDs</primary></indexterm>
-<indexterm><primary>Foomatic Printer</primary></indexterm>
-<indexterm><primary>Linuxprinting.org</primary></indexterm>
- <parameter>cupsomatic</parameter> filters may be the most widely used on CUPS
- installations. You must be clear that these were not
- developed by the CUPS people. They are a third-party add-on to
- CUPS. They utilize the traditional Ghostscript devices to render jobs
- for CUPS. When troubleshooting, you should know about the
- difference. Here the whole rendering process is done in one stage,
- inside Ghostscript, using an appropriate device for the target
- printer. <parameter>cupsomatic</parameter> uses PPDs that are generated from the Foomatic
- Printer & Driver Database at Linuxprinting.org.
- </para>
-
- <para>
- You can recognize these PPDs from the line calling the
- <parameter>cupsomatic</parameter> filter:
-<programlisting>
-*cupsFilter: "application/vnd.cups-postscript 0 cupsomatic"
-</programlisting>
- You may find this line among the first 40 or so lines of the PPD
- file. If you have such a PPD installed, the printer shows up in the
- CUPS Web interface with a <parameter>foomatic</parameter> namepart for
- the driver description. <parameter>cupsomatic</parameter> is a Perl script that runs
- Ghostscript with all the complicated command line options
- autoconstructed from the selected PPD and command line options given to
- the print job.
- </para>
-
- <para>
- <indexterm><primary>point'n'print</primary></indexterm>
-<indexterm><primary>foomatic-rip</primary></indexterm>
-<indexterm><primary>Adobe specifications</primary></indexterm>
-<indexterm><primary>hi-res photo</primary></indexterm>
-<indexterm><primary>normal color</primary></indexterm>
-<indexterm><primary>grayscale</primary></indexterm>
-<indexterm><primary>draft</primary></indexterm>
-<indexterm><primary>media type</primary></indexterm>
-<indexterm><primary>resolution</primary></indexterm>
-<indexterm><primary>inktype</primary></indexterm>
-<indexterm><primary>dithering algorithm</primary></indexterm>
- However, <parameter>cupsomatic</parameter> is now deprecated. Its PPDs (especially the first
- generation of them, still in heavy use out there) are not meeting the
- Adobe specifications. You might also suffer difficulties when you try
- to download them with <quote>Point'n'Print</quote> to Windows clients. A better
- and more powerful successor is now available: it is called <parameter>foomatic-rip</parameter>. To use
- <parameter>foomatic-rip</parameter> as a filter with CUPS, you need the new type of PPDs, which
- have a similar but different line:
-<programlisting>
-*cupsFilter: "application/vnd.cups-postscript 0 foomatic-rip"
-</programlisting>
- The PPD-generating engine at Linuxprinting.org has been revamped.
- The new PPDs comply with the Adobe spec. They also provide a
- new way to specify different quality levels (hi-res photo, normal
- color, grayscale, and draft) with a single click, whereas before you
- could have required five or more different selections (media type,
- resolution, inktype, and dithering algorithm). There is support for
- custom-size media built in. There is support to switch
- print options from page to page in the middle of a job. And the
- best thing is that the new <constant>foomatic-rip</constant> works seamlessly with all
- legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR, and so on), providing
- for them access to use PPDs for their printing.
- </para>
- </sect2>
-
- <sect2>
- <title>The Complete Picture</title>
-
- <para>
- If you want to see an overview of all the filters and how they
- relate to each other, the complete picture of the puzzle is at the end
- of this chapter.
- </para>
- </sect2>
-
- <sect2>
- <title><filename>mime.convs</filename></title>
-
- <para>
- CUPS autoconstructs all possible filtering chain paths for any given
- MIME type and every printer installed. But how does it decide in
- favor of or against a specific alternative? (There may be cases
- where there is a choice of two or more possible filtering chains for
- the same target printer.) Simple. You may have noticed the figures in
- the third column of the mime.convs file. They represent virtual costs
- assigned to this filter. Every possible filtering chain will sum up to
- a total <quote>filter cost.</quote> CUPS decides for the most <quote>inexpensive</quote> route.
- </para>
-
- <tip><para>
-<indexterm><primary>cupsd.conf</primary></indexterm>
-<indexterm><primary>FilterLimit</primary></indexterm>
- Setting <parameter>FilterLimit 1000</parameter> in
- <filename>cupsd.conf</filename> will not allow more filters to
- run concurrently than will consume a total of 1000 virtual filter
- cost. This is an efficient way to limit the load of any CUPS
- server by setting an appropriate <quote>FilterLimit</quote> value. A FilterLimit of
- 200 allows roughly one job at a time, while a FilterLimit of 1000 allows
- approximately five jobs maximum at a time.
- </para></tip>
- </sect2>
-
- <sect2>
- <title><quote>Raw</quote> Printing</title>
-
- <para>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>lpadmin</primary></indexterm>
-<indexterm><primary>rawprinter</primary></indexterm>
- You can tell CUPS to print (nearly) any file <quote>raw</quote>. <quote>Raw</quote> means it will not be
- filtered. CUPS will send the file to the printer <quote>as is</quote> without bothering if the printer is able
- to digest it. Users need to take care themselves that they send sensible data formats only. Raw printing can
- happen on any queue if the <quote><parameter>-o raw</parameter></quote> option is specified on the command
- line. You can also set up raw-only queues by simply not associating any PPD with it. This command:
-<screen>
-&prompt;<userinput>lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E</userinput>
-</screen>
- sets up a queue named <quote>rawprinter</quote>, connected via the <quote>socket</quote> protocol (a.k.a.
- <quote>HP JetDirect</quote>) to the device at IP address 11.12.1.3.14, using port 9100. (If you had added a
- PPD with <command>-P /path/to/PPD</command> to this command line, you would have installed a
- <quote>normal</quote> print queue.)
- </para>
-
- <para>
- CUPS will automatically treat each job sent to a queue as a <quote>raw</quote> one
- if it can't find a PPD associated with the queue. However, CUPS will
- only send known MIME types (as defined in its own mime.types file) and
- refuse others.
- </para>
- </sect2>
-
- <sect2>
- <title>application/octet-stream Printing</title>
-
- <para>
-<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
-<indexterm><primary>application/octet-stream</primary></indexterm>
- Any MIME type with no rule in the <filename>/etc/cups/mime.types</filename> file is regarded as unknown
- or <parameter>application/octet-stream</parameter> and will not be
- sent. Because CUPS refuses to print unknown MIME types by default,
- you will probably have experienced that print jobs originating
- from Windows clients were not printed. You may have found an error
- message in your CUPS logs like:
- </para>
-
- <para><computeroutput>
- Unable to convert file 0 to printable format for job
- </computeroutput></para>
-
- <para>
- To enable the printing of <parameter>application/octet-stream</parameter> files, edit
- these two files:
- </para>
-
- <itemizedlist>
- <listitem><para><filename>/etc/cups/mime.convs</filename></para></listitem>
-
- <listitem><para><filename>/etc/cups/mime.types</filename></para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>raw mode</primary></indexterm>
- Both contain entries (at the end of the respective files) that must be uncommented to allow raw mode
- operation for <parameter>application/octet-stream</parameter>. In <filename>/etc/cups/mime.types</filename>
- make sure this line is present:
- <indexterm><primary>application/octet-stream</primary></indexterm>
-<programlisting>
-application/octet-stream
-</programlisting>
- This line (with no specific autotyping rule set) makes all files
- not otherwise auto-typed a member of <parameter>application/octet-stream</parameter>. In
- <filename>/etc/cups/mime.convs</filename>, have this
- line:
-<programlisting>
-application/octet-stream application/vnd.cups-raw 0 -
-</programlisting>
- <indexterm><primary>MIME</primary></indexterm>
- This line tells CUPS to use the <emphasis>Null Filter</emphasis>
- (denoted as <quote>-</quote>, doing nothing at all) on
- <parameter>application/octet-stream</parameter>, and tag the result as
- <parameter>application/vnd.cups-raw</parameter>. This last one is
- always a green light to the CUPS scheduler to now hand the file over
- to the backend connecting to the printer and sending it over.
- </para>
-
- <note><para>
- Editing the <filename>mime.convs</filename> and the <filename>mime.types</filename> file does not
- <emphasis>enforce</emphasis> <quote>raw</quote> printing, it only <emphasis>allows</emphasis> it.
- </para></note>
-
- <formalpara>
- <title>Background</title>
-
- <para>
-<indexterm><primary>security-aware</primary></indexterm>
-<indexterm><primary>MIME type</primary></indexterm>
-<indexterm><primary>/etc/cups/mime.types</primary></indexterm>
-<indexterm><primary>/etc/cups/mime.convs</primary></indexterm>
- That CUPS is a more security-aware printing system than traditional ones
- does not by default allow one to send deliberate (possibly binary)
- data to printing devices. (This could be easily abused to launch a
- Denial of Service attack on your printer(s), causing at least the loss
- of a lot of paper and ink.) <quote>Unknown</quote> data are regarded by CUPS
- as <emphasis>MIME type</emphasis> <emphasis>application/octet-stream</emphasis>. While you
- <emphasis>can</emphasis> send data <quote>raw</quote>, the MIME type for these must
- be one that is known to CUPS and allowed by it. The file
- <filename>/etc/cups/mime.types</filename> defines the <quote>rules</quote> of how CUPS
- recognizes MIME types. The file <filename>/etc/cups/mime.convs</filename> decides which file
- conversion filter(s) may be applied to which MIME types.
- </para>
- </formalpara>
- </sect2>
-
- <sect2>
- <title>PostScript Printer Descriptions for Non-PostScript Printers</title>
-
- <para>
- <indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>non-PostScript</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>RIP</primary></indexterm>
-<indexterm><primary>Ghostscript</primary></indexterm>
-<indexterm><primary>device-specific commands</primary></indexterm>
- Originally PPDs were meant to be used for PostScript printers
- only. Here, they help to send device-specific commands and settings
- to the RIP, which processes the job file. CUPS has extended this
- scope for PPDs to cover non-PostScript printers too. This was not
- difficult, because it is a standardized file format. In a way
- it was logical too: CUPS handles PostScript and uses a PostScript
- RIP (Ghostscript) to process the job files. The only difference is that
- a PostScript printer has the RIP built-in, for other types of
- printers the Ghostscript RIP runs on the host computer.
- </para>
-
- <para>
- PPDs for a non-PostScript printer have a few lines that are unique to
- CUPS. The most important one looks similar to this:
- <indexterm><primary>application/vnd.cups-raster</primary></indexterm>
-<programlisting>
-*cupsFilter: application/vnd.cups-raster 66 rastertoprinter
-</programlisting>
- It is the last piece in the CUPS filtering puzzle. This line tells the
- CUPS daemon to use as a last filter <parameter>rastertoprinter</parameter>. This filter
- should be served as input an <parameter>application/vnd.cups-raster</parameter> MIME type
- file. Therefore, CUPS should autoconstruct a filtering chain, which
- delivers as its last output the specified MIME type. This is then
- taken as input to the specified <parameter>rastertoprinter</parameter> filter. After
- the last filter has done its work (<parameter>rastertoprinter</parameter> is a Gutenprint
- filter), the file should go to the backend, which sends it to the
- output device.
- </para>
-
- <para>
- CUPS by default ships only a few generic PPDs, but they are good for
- several hundred printer models. You may not be able to control
- different paper trays, or you may get larger margins than your
- specific model supports. See Table 21.1<link linkend="cups-ppds"></link> for summary information.
- </para>
-
- <table frame="all" id="cups-ppds">
- <title>PPDs Shipped with CUPS</title>
- <tgroup cols="2" align="left">
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <thead><row><entry>PPD file</entry><entry>Printer type</entry></row></thead>
- <tbody>
- <row><entry>deskjet.ppd</entry><entry>older HP inkjet printers and compatible</entry></row>
-
- <row><entry>deskjet2.ppd</entry> <entry>newer HP inkjet printers and compatible </entry> </row>
-
- <row><entry>dymo.ppd</entry> <entry>label printers </entry> </row>
-
- <row><entry>epson9.ppd</entry> <entry>Epson 24-pin impact printers and compatible </entry> </row>
-
- <row><entry>epson24.ppd</entry> <entry>Epson 24-pin impact printers and compatible </entry> </row>
-
- <row><entry>okidata9.ppd</entry> <entry>Okidata 9-pin impact printers and compatible </entry> </row>
-
- <row><entry>okidat24.ppd</entry> <entry>Okidata 24-pin impact printers and compatible </entry> </row>
-
- <row><entry>stcolor.ppd</entry> <entry>older Epson Stylus Color printers </entry> </row>
-
- <row><entry>stcolor2.ppd</entry> <entry>newer Epson Stylus Color printers </entry> </row>
-
- <row><entry>stphoto.ppd</entry> <entry>older Epson Stylus Photo printers </entry> </row>
-
- <row><entry>stphoto2.ppd</entry> <entry>newer Epson Stylus Photo printers </entry> </row>
-
- <row><entry>laserjet.ppd</entry> <entry>all PCL printers </entry> </row>
-
- </tbody>
- </tgroup>
- </table>
-
- </sect2>
-
- <sect2>
- <title><emphasis>cupsomatic/foomatic-rip</emphasis> Versus <emphasis>Native CUPS</emphasis> Printing</title>
-
- <para>
- <indexterm><primary>cupsomatic</primary></indexterm>
- <indexterm><primary>foomatic-rip</primary></indexterm>
- Native CUPS rasterization works in two steps:
- </para>
-
- <itemizedlist>
- <listitem><para>
-<indexterm><primary>pstoraster</primary></indexterm>
- First is the <parameter>pstoraster</parameter> step. It uses the special CUPS
- <indexterm><primary>ESP</primary><secondary>Ghostscript</secondary></indexterm>
- device from ESP Ghostscript 7.05.x as its tool.
- </para></listitem>
-
- <listitem><para>
- Second is the <parameter>rasterdriver</parameter> step. It uses various
- device-specific filters; there are several vendors who provide good
- quality filters for this step. Some are free software, some are
- shareware, and some are proprietary.
- </para></listitem>
- </itemizedlist>
-
- <para>
- Often this produces better quality (and has several more advantages) than other methods.
- This is shown in <link linkend="cupsomatic-dia"> the cupsomatic/foomatic Processing Versus Native CUPS
- illustration</link>.
- </para>
-
- <figure id="cupsomatic-dia">
- <title>cupsomatic/foomatic Processing Versus Native CUPS.</title>
- <imagefile>10small</imagefile>
- </figure>
-
- <para>
- One other method is the <parameter>cupsomatic/foomatic-rip</parameter>
- way. Note that <parameter>cupsomatic</parameter> is <emphasis>not</emphasis> made by the CUPS
- developers. It is an independent contribution to printing development,
- made by people from Linuxprinting.org.<footnote><para>See also <ulink
- noescape="1" url="http://www.cups.org/cups-help.html">http://www.cups.org/cups-help.html</ulink></para></footnote>
- <parameter>cupsomatic</parameter> is no longer developed, maintained, or supported. It now been
- replaced by <parameter>foomatic-rip</parameter>. <parameter>foomatic-rip</parameter> is a complete rewrite
- of the old <parameter>cupsomatic</parameter> idea, but very much improved and generalized to
- other (non-CUPS) spoolers. An upgrade to <parameter>foomatic-rip</parameter> is strongly
- advised, especially if you are upgrading to a recent version of CUPS,
- too.
- </para>
-
- <para>
- <indexterm><primary>cupsomatic</primary></indexterm>
- <indexterm><primary>foomatic</primary></indexterm>
- Like the old <parameter>cupsomatic</parameter> method, the <parameter>foomatic-rip</parameter> (new) method
- from Linuxprinting.org uses the traditional Ghostscript print file processing, doing everything in a single
- step. It therefore relies on all the other devices built into Ghostscript. The quality is as good (or bad) as
- Ghostscript rendering is in other spoolers. The advantage is that this method supports many printer models not
- supported (yet) by the more modern CUPS method.
- </para>
-
- <para>
- Of course, you can use both methods side by side on one system (and even for one printer, if you set up
- different queues) and find out which works best for you.
- </para>
-
- <para>
-<indexterm><primary>cupsomatic</primary></indexterm>
-<indexterm><primary>pstoraster</primary></indexterm>
-<indexterm><primary>rastertosomething</primary></indexterm>
-<indexterm><primary>rasterization</primary></indexterm>
-<indexterm><primary>Foomatic/cupsomatic</primary></indexterm>
-<indexterm><primary>rendering</primary></indexterm>
- <parameter>cupsomatic</parameter> kidnaps the print file after the
- <parameter>application/vnd.cups-postscript</parameter> stage and deviates it through the CUPS-external,
- systemwide Ghostscript installation. Therefore, the print file bypasses the <parameter>pstoraster</parameter>
- filter (and also bypasses the CUPS raster drivers <parameter>rastertosomething</parameter>). After Ghostscript
- finished its rasterization, <parameter>cupsomatic</parameter> hands the rendered file directly to the CUPS
- backend. <link linkend="cupsomatic-dia">cupsomatic/foomatic Processing Versus Native
- CUPS</link>, illustrates the difference between native CUPS rendering and the
- <parameter>Foomatic/cupsomatic</parameter> method.
- </para>
- </sect2>
-
- <sect2>
- <title>Examples for Filtering Chains</title>
-
- <para>
- Here are a few examples of commonly occurring filtering chains to
- illustrate the workings of CUPS.
- </para>
-
- <para>
-<indexterm><primary>HP JetDirect</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>two-up</primary></indexterm>
-<indexterm><primary>duplex</primary></indexterm>
- Assume you want to print a PDF file to an HP JetDirect-connected
- PostScript printer, but you want to print pages 3-5, 7, and 11-13
- only, and you want to print them <quote>two-up</quote> and <quote>duplex</quote>:
- </para>
-
- <itemizedlist>
- <listitem><para>Your print options (page selection as required, two-up,
- duplex) are passed to CUPS on the command line.</para></listitem>
-
- <listitem><para>The (complete) PDF file is sent to CUPS and autotyped as
- <parameter>application/pdf</parameter>.</para></listitem>
-
- <listitem><para>The file therefore must first pass the
- <parameter>pdftops</parameter> prefilter, which produces PostScript
- MIME type <parameter>application/postscript</parameter> (a preview here
- would still show all pages of the original PDF).</para></listitem>
-
- <listitem><para>The file then passes the <parameter>pstops</parameter>
- filter that applies the command line options: it selects pages
- 2-5, 7, and 11-13, creates the imposed layout <quote>two pages on one sheet</quote>, and
- inserts the correct <quote>duplex</quote> command (as defined in the printer's
- PPD) into the new PostScript file; the file is now of PostScript MIME
- type
- <parameter>application/vnd.cups-postscript</parameter>.</para></listitem>
-
- <listitem><para>The file goes to the <parameter>socket</parameter>
- backend, which transfers the job to the printers.</para></listitem>
- </itemizedlist>
-
- <para>
- The resulting filter chain, therefore, is as shown in <link linkend="pdftosocket">the PDF to socket chain
- illustration</link>.
- </para>
-
-<indexterm><primary>pdftosocket</primary></indexterm>
- <figure id="pdftosocket">
- <title>PDF to Socket Chain.</title>
- <imagefile>pdftosocket</imagefile>
- </figure>
-
- <para>
-<indexterm><primary>USB</primary></indexterm>
-<indexterm><primary>Epson Stylus</primary></indexterm>
-<indexterm><primary>stphoto2.ppd</primary></indexterm>
- Assume you want to print the same filter to an USB-connected Epson Stylus Photo Printer installed with the CUPS
- <filename>stphoto2.ppd</filename>. The first few filtering stages are nearly the same:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Your print options (page selection as required, two-up,
- duplex) are passed to CUPS on the command line.
- </para></listitem>
-
- <listitem><para>
- The (complete) PDF file is sent to CUPS and autotyped as
- <parameter>application/pdf</parameter>.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>pdftops</primary></indexterm>
-<indexterm><primary>PDF</primary></indexterm>
- The file must first pass the <parameter>pdftops</parameter> prefilter, which produces PostScript
- MIME type <parameter>application/postscript</parameter> (a preview here would still show all
- pages of the original PDF).
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>pstops</primary></indexterm>
-<indexterm><primary>duplex printing</primary></indexterm>
- The file then passes the <quote>pstops</quote> filter that applies
- the command line options: it selects the pages 2-5, 7, and 11-13,
- creates the imposed layout <quote>two pages on one sheet,</quote> and inserts the
- correct <quote>duplex</quote> command (oops &smbmdash; this printer and PPD
- do not support duplex printing at all, so this option will
- be ignored) into the new PostScript file; the file is now of PostScript
- MIME type <parameter>application/vnd.cups-postscript</parameter>.
- </para></listitem>
-
- <listitem><para>
- The file then passes the <parameter>pstoraster</parameter> stage and becomes MIME type
- <parameter>application/cups-raster</parameter>.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>rastertoepson</primary></indexterm>
- Finally, the <parameter>rastertoepson</parameter> filter
- does its work (as indicated in the printer's PPD), creating the
- printer-specific raster data and embedding any user-selected
- print options into the print data stream.
- </para></listitem>
-
- <listitem><para>
- The file goes to the <parameter>usb</parameter> backend, which transfers the job to the printers.
- </para></listitem>
- </itemizedlist>
-
- <para>
- The resulting filter chain therefore is as shown in <link linkend="pdftoepsonusb">the PDF to USB Chain
- illustration</link>.
- </para>
-
- <figure id="pdftoepsonusb">
- <title>PDF to USB Chain.</title>
- <imagefile>pdftoepsonusb</imagefile>
- </figure>
- </sect2>
-
- <sect2>
- <title>Sources of CUPS Drivers/PPDs</title>
-
- <para>
- On the Internet you can now find many thousands of CUPS-PPD files
- (with their companion filters), in many national languages
- supporting more than 1,000 non-PostScript models.
- </para>
-
- <itemizedlist>
- <indexterm><primary>ESP</primary><secondary>Print Pro</secondary></indexterm>
- <indexterm><primary>PrintPro</primary><see>ESP Print Pro</see></indexterm>
- <listitem><para>
- <ulink url="http://www.easysw.com/printpro/">ESP PrintPro</ulink>
- (commercial, non-free) is packaged with more than 3,000 PPDs, ready for
- successful use <quote>out of the box</quote> on Linux, Mac OS X, IBM-AIX,
- HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX, and
- other commercial Unices (it is written by the CUPS developers
- themselves and its sales help finance the further development of
- CUPS, as they feed their creators).
- </para></listitem>
-
- <listitem><para>
- The <ulink url="http://gimp-print.sourceforge.net/">Gutenprint Project</ulink>
- (GPL, free software) provides around 140 PPDs (supporting nearly 400 printers, many driven
- to photo quality output), to be used alongside the Gutenprint CUPS filters.
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.turboprint.de/english.html/">TurboPrint </ulink> (shareware, non-free) supports
- roughly the same number of printers in excellent quality.
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/">OMNI </ulink>
- (LPGL, free) is a package made by IBM, now containing support for more
- than 400 printers, stemming from the inheritance of IBM OS/2 know-how
- ported over to Linux (CUPS support is in a beta stage at present).
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://hpinkjet.sourceforge.net/">HPIJS </ulink> (BSD-style licenses, free)
- supports approximately 150 of HP's own printers and also provides
- excellent print quality now (currently available only via the Foomatic path).
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.linuxprinting.org/">Foomatic/cupsomatic </ulink>
- (LPGL, free) from Linuxprinting.org provide PPDs for practically every Ghostscript
- filter known to the world (including Omni, Gutenprint, and HPIJS).
- </para></listitem>
- </itemizedlist>
-
- </sect2>
-
- <sect2>
- <title>Printing with Interface Scripts</title>
-
- <para>
-<indexterm><primary>PCL</primary></indexterm>
-<indexterm><primary>lpadmin</primary></indexterm>
- CUPS also supports the use of <quote>interface scripts</quote> as known from
- System V AT&T printing systems. These are often used for PCL
- printers, from applications that generate PCL print jobs. Interface
- scripts are specific to printer models. They have a role similar to
- PPDs for PostScript printers. Interface scripts may inject the Escape
- sequences as required into the print data stream if the user, for example, selects
- a certain paper tray, or changes paper orientation, or uses A3
- paper. Interface scripts are practically unknown in the Linux
- realm. On HP-UX platforms they are more often used. You can use any
- working interface script on CUPS too. Just install the printer with
- the <command>-i</command> option:
-<screen>
-&rootprompt;<userinput>lpadmin -p pclprinter -v socket://11.12.13.14:9100 \
- -i /path/to/interface-script</userinput>
-</screen></para>
-
- <para>
- Interface scripts might be the <quote>unknown animal</quote> to many. However,
- with CUPS they provide the easiest way to plug in your own custom-written filtering
- script or program into one specific print queue (some information about the traditional
- use of interface scripts is found at
- <ulink noescape="1" url="http://playground.sun.com/printing/documentation/interface.html">
- http://playground.sun.com/printing/documentation/interface.html</ulink>).
- </para>
- </sect2>
-</sect1>
-
-<sect1>
-<title>Network Printing (Purely Windows)</title>
-
-<para>
-Network printing covers a lot of ground. To understand what exactly
-goes on with Samba when it is printing on behalf of its Windows
-clients, let's first look at a <quote>purely Windows</quote> setup: Windows clients
-with a Windows NT print server.
-</para>
-
-<sect2>
-<title>From Windows Clients to an NT Print Server</title>
-
-<para>
-Windows clients printing to an NT-based print server have two
-options. They may:
-<indexterm><primary>GDI</primary></indexterm>
-<indexterm><primary>EMF</primary></indexterm>
-</para>
-
-
-<itemizedlist>
- <listitem><para>Execute the driver locally and render the GDI output
- (EMF) into the printer-specific format on their own.
- </para></listitem>
-
- <listitem><para>Send the GDI output (EMF) to the server, where the
- driver is executed to render the printer-specific output.
- </para></listitem>
-</itemizedlist>
-
-<para>
-Both print paths are shown in the flowcharts in <link linkend="small11">
-Print Driver Execution on the Client</link>, and
-<link linkend="small12">Print Driver Execution on the Server</link>.
-</para>
-</sect2>
-
-<sect2>
-<title>Driver Execution on the Client</title>
-
-<para>
-In the first case, the print server must spool the file as raw, meaning it shouldn't touch the job file and try
-to convert it in any way. This is what a traditional UNIX-based print server can do too, and at a better
-performance and more reliably than an NT print server. This is what most Samba administrators probably are
-familiar with. One advantage of this setup is that this <quote>spooling-only</quote> print server may be used
-even if no driver(s) for UNIX is available. It is sufficient to have the Windows client drivers available and
-installed on the clients. This is illustrated in <link linkend="small11">the Print Driver Execution on the
-Client diagram</link>.
-</para>
-
-<figure id="small11">
- <title>Print Driver Execution on the Client.</title>
- <imagefile>11small</imagefile>
-</figure>
-
-</sect2>
-
-<sect2>
-<title>Driver Execution on the Server</title>
-
-
-<para>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>PCL</primary></indexterm>
-<indexterm><primary>ESC/P</primary></indexterm>
-<indexterm><primary>EMF</primary></indexterm>
-<indexterm><primary>GDI</primary></indexterm>
-The other path executes the printer driver on the server. The client transfers print files in EMF format to
-the server. The server uses the PostScript, PCL, ESC/P, or other driver to convert the EMF file into the
-printer-specific language. It is not possible for UNIX to do the same. Currently, there is no program or
-method to convert a Windows client's GDI output on a UNIX server into something a printer could understand.
-This is illustrated in <link linkend="small12">the Print Driver Execution on the Server diagram</link>.
-</para>
-
- <figure id="small12">
- <title>Print Driver Execution on the Server.</title>
- <imagefile>12small</imagefile>
- </figure>
-
-<para>
-However, something similar is possible with CUPS, so read on.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Network Printing (Windows Clients and UNIX/Samba Print
-Servers)</title>
-
-<para>
-Since UNIX print servers <emphasis>cannot</emphasis> execute the Win32
-program code on their platform, the picture is somewhat
-different. However, this does not limit your options all that
-much. On the contrary, you may have a way here to implement printing
-features that are not possible otherwise.
-</para>
-
-<sect2>
-<title>From Windows Clients to a CUPS/Samba Print Server</title>
-
-<para>
-Here is a simple recipe showing how you can take advantage of CUPS's
-powerful features for the benefit of your Windows network printing
-clients:
-</para>
-
-<itemizedlist>
- <listitem><para>Let the Windows clients send PostScript to the CUPS
- server.</para></listitem>
-
- <listitem><para>Let the CUPS server render the PostScript into device-specific raster format.</para></listitem>
-</itemizedlist>
-
-<para>
-This requires the clients to use a PostScript driver (even if the
-printer is a non-PostScript model. It also requires that you have a
-driver on the CUPS server.
-</para>
-
-<para>
-First, to enable CUPS-based printing through Samba, the following options should be set in your &smb.conf;
-file <parameter>[global]</parameter> section:
-</para>
-
-<smbconfblock>
-<smbconfoption name="printing">cups</smbconfoption>
-</smbconfblock>
-
-<para>
-When these parameters are specified, all manually set print directives (like <smbconfoption name="print
-command"/> or <smbconfoption name="lppause command"/>) in &smb.conf; (as well as in Samba itself) will be
-ignored. Instead, Samba will directly interface with CUPS through its
-application program interface (API).
-This is illustrated in <link linkend="f13small">the Printing via
-CUPS/Samba Server diagram</link>.
-</para>
-
- <figure id="f13small">
- <title>Printing via CUPS/Samba Server.</title>
- <imagefile>13small</imagefile>
- </figure>
-</sect2>
-
-<sect2>
-<title>Samba Receiving Job-Files and Passing Them to CUPS</title>
-
-<para>
-Samba <emphasis>must</emphasis> use its own spool directory (it is set by a line similar to <smbconfoption
-name="path">/var/spool/samba</smbconfoption>, in the <smbconfsection name="[printers]"/> or <smbconfsection
-name="[printername]"/> section of &smb.conf;). Samba receives the job in its own spool space and passes it
-into the spool directory of CUPS (the CUPS spool directory is set by the <parameter>RequestRoot</parameter>
-directive in a line that defaults to <parameter>RequestRoot /var/spool/cups</parameter>). CUPS checks the
-access rights of its spool directory and resets it to healthy values with every restart. We have seen quite a
-few people who used a common spooling space for Samba and CUPS, and struggled for weeks with this
-<quote>problem.</quote>
-</para>
-
-<para>
-A Windows user authenticates only to Samba (by whatever means is
-configured). If Samba runs on the same host as CUPS, you only need to
-allow <quote>localhost</quote> to print. If it runs on different machines, you
-need to make sure the Samba host gets access to printing on CUPS.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Network PostScript RIP</title>
-
-<para>
-This section discusses the use of CUPS filters on the server &smbmdash; configuration where
-clients make use of a PostScript driver with CUPS-PPDs.
-</para>
-
-
-<para>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>PCL</primary></indexterm>
-<indexterm><primary>PJL</primary></indexterm>
-PPDs can control all print device options. They are usually provided by the manufacturer &smbmdash; if you own
-a PostScript printer, that is. PPD files are always a component of PostScript printer drivers on MS Windows or
-Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate
-PostScript, PCL, or PJL commands for the target printer. Printer driver GUI dialogs translate these options
-<quote>on the fly</quote> into buttons and drop-down lists for the user to select.
-</para>
-
-<para>
-CUPS can load, without any conversions, the PPD file from any Windows (NT is recommended) PostScript driver
-and handle the options. There is a Web browser interface to the print options (select <ulink noescape="1"
-url="http://localhost:631/printers/">http://localhost:631/printers/</ulink> and click on one
-<guibutton>Configure Printer</guibutton> button to see it) or a command line interface (see <command>man
-lpoptions</command> or see if you have <command>lphelp</command> on your system). There are also some
-different GUI front-ends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant
-to be evaluated by the PostScript RIP on the real PostScript printer.
-</para>
-
-<sect2>
-<title>PPDs for Non-PS Printers on UNIX</title>
-
-
-<para>
-<indexterm><primary>PPD</primary></indexterm>
-CUPS does not limit itself to <quote>real</quote> PostScript printers in its use of PPDs. The CUPS developers
-have extended the scope of the PPD concept to also describe available device and driver options for
-non-PostScript printers through CUPS-PPDs.
-</para>
-
-<para>
-This is logical, because CUPS includes a fully featured PostScript interpreter (RIP). This RIP is based on
-Ghostscript. It can process all received PostScript (and additionally many other file formats) from clients.
-All CUPS-PPDs geared to non-PostScript printers contain an additional line, starting with the keyword
-<parameter>*cupsFilter</parameter>. This line tells the CUPS print system which printer-specific filter to use
-for the interpretation of the supplied PostScript. Thus CUPS lets all its printers appear as PostScript
-devices to its clients, because it can act as a PostScript RIP for those printers, processing the received
-PostScript code into a proper raster print format.
-</para>
-</sect2>
-
-<sect2>
-<title>PPDs for Non-PS Printers on Windows</title>
-
-<para>
-<indexterm><primary>PPD</primary></indexterm>
-CUPS-PPDs can also be used on Windows clients, on top of a <quote>core</quote> PostScript driver (now
-recommended is the CUPS PostScript Driver for Windows NT/200x/XP; you can also use the Adobe one, with
-limitations). This feature enables CUPS to do a few tricks no other spooler can do:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Act as a networked PostScript RIP handling print files from all client platforms in a uniform way.
- </para></listitem>
-
- <listitem><para>
- Act as a central accounting and billing server, since all files are passed through the pstops filter and are therefore
- logged in the CUPS <filename>page_log</filename> file. <emphasis>Note:</emphasis> this cannot happen with
- <quote>raw</quote> print jobs, which always remain unfiltered per definition.
- </para></listitem>
-
- <listitem><para>
- Enable clients to consolidate on a single PostScript driver, even for many different target printers.
- </para></listitem>
-</itemizedlist>
-
-<para>
-Using CUPS PPDs on Windows clients enables them to control all print job settings just as a UNIX client can do.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Windows Terminal Servers (WTS) as CUPS Clients</title>
-
-<para>
-This setup may be of special interest to people experiencing major problems in WTS environments. WTS often
-need a multitude of non-PostScript drivers installed to run their clients' variety of different printer
-models. This often imposes the price of much increased instability.
-</para>
-
-<sect2>
-<title>Printer Drivers Running in <quote>Kernel Mode</quote> Cause Many
-Problems</title>
-
-<para>
-Windows NT printer drivers, which run in <quote>kernel mode</quote>, introduce a high risk for the stability
-of the system if the driver is not really stable and well-tested. And there are a lot of bad drivers out
-there! Especially notorious is the example of the PCL printer driver that had an additional sound module
-running to notify users via soundcard of their finished jobs. Do I need to say that this one was also reliably
-causing <quote>blue screens of death</quote> on a regular basis?
-</para>
-
-<para>
-PostScript drivers are generally well-tested. They are not known to cause any problems, even though they also
-run in kernel mode. This might be because until now there have been only two different PostScript drivers: the
-one from Adobe and the one from Microsoft. Both are well-tested and are as stable as you can imagine on
-Windows. The CUPS driver is derived from the Microsoft one.
-</para>
-</sect2>
-
-<sect2>
-<title>Workarounds Impose Heavy Limitations</title>
-
-<para>
-In an attempt to work around problems, site administrators have resorted to restricting the
-allowed drivers installed on their WTS to one generic PCL and one PostScript driver. This, however, restricts
-the number of printer options available for clients to use. Often they can't get out more than simplex
-prints from one standard paper tray, while their devices could do much better if driven by a different driver!
-</para>
-</sect2>
-
-<sect2>
-<title>CUPS: A <quote>Magical Stone</quote>?</title>
-
-<para>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these
-shortcomings. There are, depending on the version of Windows OS you use, up to three different PostScript
-drivers now available: Adobe, Microsoft, and CUPS PostScript drivers. None of them is known to cause major
-stability problems on WTS (even if used with many different PPDs). The clients will be able to (again) choose
-paper trays, duplex printing, and other settings. However, there is a certain price for this too: a CUPS
-server acting as a PostScript RIP for its clients requires more CPU and RAM than when just acting as a
-<quote>raw spooling</quote> device. Plus, this setup is not yet widely tested, although the first feedbacks
-look very promising.
-</para>
-</sect2>
-
-<sect2>
-<title>PostScript Drivers with No Major Problems, Even in Kernel
-Mode</title>
-
-<para>
-<indexterm><primary>DDK</primary></indexterm>
-<indexterm><primary>W32X86</primary></indexterm>
-<indexterm><primary>PostScript</primary></indexterm>
-<indexterm><primary>Visual Studio</primary></indexterm>
-<indexterm><primary>Microsoft driver</primary></indexterm>
-<indexterm><primary>Adobe</primary></indexterm>
-More recent printer drivers on W200x and XP no longer run in kernel mode (unlike Windows NT). However, both
-operating systems can still use the NT drivers, running in kernel mode (you can roughly tell which is which as
-the drivers in subdirectory <quote>2</quote> of <quote>W32X86</quote> are <quote>old</quote> ones). As was
-said before, the Adobe as well as the Microsoft PostScript drivers are not known to cause any stability
-problems. The CUPS driver is derived from the Microsoft one. There is a simple reason for this: the MS DDK
-(Device Development Kit) for Windows NT (which used to be available at no cost to licensees of Visual Studio)
-includes the source code of the Microsoft driver, and licensees of Visual Studio are allowed to use and modify
-it for their own driver development efforts. This is what the CUPS people have done. The license does not
-allow them to publish the whole of the source code. However, they have released the <quote>diff</quote> under
-the GPL, and if you are the owner of an <quote>MS DDK for Windows NT,</quote> you can check the driver
-yourself.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Configuring CUPS for Driver Download</title>
-
-<para>
-As we have said before, all previously known methods to prepare client printer drivers on the Samba server for
-download and Point'n'Print convenience of Windows workstations are working with CUPS, too. These methods were
-described in <link linkend="classicalprinting">Classical Printing</link>. In reality, this is a pure Samba
-business and relates only to the Samba-Windows client relationship.
-</para>
-
-<sect2>
-<title><emphasis>cupsaddsmb</emphasis>: The Unknown Utility</title>
-
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-The <parameter>cupsaddsmb</parameter> utility (shipped with all current CUPS versions) is an alternative
-method to transfer printer drivers into the Samba <smbconfsection name="[print$]"/> share. Remember, this
-share is where clients expect drivers deposited and set up for download and installation. It makes the sharing
-of any (or all) installed CUPS printers quite easy. <command>cupsaddsmb</command> can use the Adobe PostScript
-driver as well as the newly developed CUPS PostScript driver for Windows NT/200x/XP.
-<parameter>cupsaddsmb</parameter> does <emphasis>not</emphasis> work with arbitrary vendor printer drivers,
-but only with the <emphasis>exact</emphasis> driver files that are named in its man page.
-</para>
-
-<para>
-The CUPS printer driver is available from the CUPS download site. Its package name is
-<filename>cups-samba-[version].tar.gz</filename>. It is preferred over the Adobe drivers because it has a
-number of advantages:
-</para>
-
-<itemizedlist>
- <listitem><para>It supports a much more accurate page accounting.</para></listitem>
-
- <listitem><para>It supports banner pages and page labels on all printers.</para></listitem>
-
- <listitem><para>It supports the setting of a number of job IPP attributes
- (such as job priority, page label, and job billing).</para></listitem>
-</itemizedlist>
-
-<para>
-However, currently only Windows NT, 2000, and XP are supported by the
-CUPS drivers. You will also need to get the respective part of the Adobe driver
-if you need to support Windows 95, 98, and Me clients.
-</para>
-</sect2>
-
-<sect2>
-<title>Prepare Your &smb.conf; for <command>cupsaddsmb</command></title>
-
-<para>
-Prior to running <command>cupsaddsmb</command>, you need the settings in
-&smb.conf; as shown in <link linkend="cupsadd-ex">the &smb.conf; for cupsaddsmb Usage</link>.
-</para>
-
-<example id="cupsadd-ex">
-<title>smb.conf for cupsaddsmb Usage</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="load printers">yes</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="browseable">no</smbconfoption>
-<smbconfcomment>setting depends on your requirements</smbconfcomment>
-<smbconfoption name="guest ok">yes</smbconfoption>
-<smbconfoption name="writable">no</smbconfoption>
-<smbconfoption name="printable">yes</smbconfoption>
-<smbconfoption name="printer admin">root</smbconfoption>
- <smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers</smbconfoption>
-<smbconfoption name="path">/etc/samba/drivers</smbconfoption>
-<smbconfoption name="browseable">yes</smbconfoption>
-<smbconfoption name="guest ok">no</smbconfoption>
-<smbconfoption name="read only">yes</smbconfoption>
-<smbconfoption name="write list">root, @smbprintadm</smbconfoption>
-</smbconfblock>
-</example>
-</sect2>
-
-<sect2>
-<title>CUPS <quote>PostScript Driver for Windows NT/200x/XP</quote></title>
-
-<para>
-<indexterm><primary>PostScript</primary></indexterm>
-CUPS users may get the exact same package from <ulink noescape="1"
-url="http://www.cups.org/software.html">http://www.cups.org/software.html</ulink>. It is a separate package
-from the CUPS-based software files, tagged as CUPS 1.1.x Windows NT/200x/XP Printer Driver for Samba (tar.gz,
-192k). The filename to download is <filename>cups-samba-1.1.x.tar.gz</filename>. Upon untar and unzipping, it
-will reveal these files:
-<screen>
-&rootprompt;<userinput>tar xvzf cups-samba-1.1.19.tar.gz</userinput>
-cups-samba.install
-cups-samba.license
-cups-samba.readme
-cups-samba.remove
-cups-samba.ss
-</screen></para>
-
-<para>
-<indexterm><primary>ESP</primary><secondary>meta packager</secondary></indexterm>
-<indexterm><primary>EPM</primary><see>ESP meta packager</see></indexterm>
-These have been packaged with the ESP meta-packager software EPM. The <filename>*.install</filename> and
-<filename>*.remove</filename> files are simple shell scripts, which untar the <filename>*.ss</filename> (the
-<filename>*.ss</filename> is nothing else but a tar archive, which can be untarred by <quote>tar</quote> too).
-Then it puts the content into <filename>/usr/share/cups/drivers/</filename>. This content includes three
-files:
-<screen>
-&rootprompt;<userinput>tar tv cups-samba.ss</userinput>
-cupsdrvr.dll
-cupsui.dll
-cups.hlp
-</screen></para>
-
-<para>
-The <parameter>cups-samba.install</parameter> shell scripts are easy to
-handle:
-<screen>
-&rootprompt;<userinput>./cups-samba.install</userinput>
-[....]
-Installing software...
-Updating file permissions...
-Running post-install commands...
-Installation is complete.
-</screen></para>
-
-<para>
-The script should automatically put the driver files into the
-<filename>/usr/share/cups/drivers/</filename> directory:
-<screen>
-&rootprompt;<userinput>cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/</userinput>
-</screen></para>
-
-<warning><para>
-Due to a bug, one recent CUPS release puts the <filename>cups.hlp</filename> driver file
-into<filename>/usr/share/drivers/</filename> instead of <filename>/usr/share/cups/drivers/</filename>. To work
-around this, copy/move the file (after running the <command>./cups-samba.install</command> script) manually to
-the correct place.
-</para></warning>
-
-<para>
-<indexterm><primary>DDK</primary></indexterm>
-This new CUPS PostScript driver is currently binary only, but free of charge. No complete source code is
-provided (yet). The reason is that it has been developed with the help of the Microsoft DDK and compiled with
-Microsoft Visual Studio 6. Driver developers are not allowed to distribute the whole of the source code as
-free software. However, CUPS developers released the <quote>diff</quote> in source code under the GPL, so
-anybody with a license for Visual Studio and a DDK will be able to compile for himself or herself.
-</para>
-</sect2>
-
-<sect2>
-<title>Recognizing Different Driver Files</title>
-
-<para>
-The CUPS drivers do not support the older Windows 95/98/Me, but only the Windows NT/2000/XP client.
-</para>
-
-<para>Windows NT, 2000, and XP are supported by:</para>
-
-<itemizedlist>
- <listitem><para>cups.hlp</para></listitem>
- <listitem><para>cupsdrvr.dll</para></listitem>
- <listitem><para>cupsui.dll</para></listitem>
-</itemizedlist>
-
-<para>
-Adobe drivers are available for the older Windows 95/98/Me as well as
-for Windows NT/2000/XP clients. The set of files is different from the
-different platforms.
-</para>
-
-<para>Windows 95, 98, and ME are supported by:</para>
-
-<itemizedlist>
- <listitem><para>ADFONTS.MFM</para></listitem>
- <listitem><para>ADOBEPS4.DRV</para></listitem>
- <listitem><para>ADOBEPS4.HLP</para></listitem>
- <listitem><para>DEFPRTR2.PPD</para></listitem>
- <listitem><para>ICONLIB.DLL</para></listitem>
- <listitem><para>PSMON.DLL</para></listitem>
-</itemizedlist>
-
-<para>Windows NT, 2000, and XP are supported by:</para>
-
-<itemizedlist>
- <listitem><para>ADOBEPS5.DLL</para></listitem>
- <listitem><para>ADOBEPSU.DLL</para></listitem>
- <listitem><para>ADOBEPSU.HLP</para></listitem>
-</itemizedlist>
-
-<note><para>
-<indexterm><primary>Adobe driver files</primary></indexterm>
-If both the Adobe driver files and the CUPS driver files for the support of Windows NT/200x/XP are presently
-installed on the server, the Adobe files will be ignored and the CUPS files will be used. If you prefer
-&smbmdash; for whatever reason &smbmdash; to use Adobe-only drivers, move away the three CUPS driver files.
-The Windows 9x/Me clients use the Adobe drivers in any case.
-</para></note>
-</sect2>
-
-<sect2>
-<title>Acquiring the Adobe Driver Files</title>
-
-<para>
-Acquiring the Adobe driver files seems to be unexpectedly difficult for many users. They are not available on
-the Adobe Web site as single files, and the self-extracting and/or self-installing Windows-.exe is not easy to
-locate either. You probably need to use the included native installer and run the installation process on one
-client once. This will install the drivers (and one generic PostScript printer) locally on the client. When
-they are installed, share the generic PostScript printer. After this, the client's <smbconfsection
-name="[print$]"/> share holds the Adobe files, which you can get with smbclient from the CUPS host.
-</para>
-</sect2>
-
-<sect2>
-<title>ESP Print Pro PostScript Driver for Windows NT/200x/XP</title>
-
-<para>
-<indexterm><primary>ESP</primary><secondary>Print Pro</secondary></indexterm>
-Users of the ESP Print Pro software are able to install the ESP print drivers package as an alternative to the
-Adobe PostScript drivers. To do so, retrieve the driver files from the normal download area of the ESP Print
-Pro software at <ulink noescape="1" url="http://www.easysw.com/software.html">Easy Software</ulink> web site.
-You need to locate the link labeled <quote>SAMBA</quote> among the <guilabel>Download Printer Drivers for ESP
-Print Pro 4.x</guilabel> area and download the package. Once installed, you can prepare any driver by simply
-highlighting the printer in the Printer Manager GUI and selecting <guilabel>Export Driver...</guilabel> from
-the menu. Of course, you need to have prepared Samba beforehand to handle the driver files; that is, set up
-the <smbconfsection name="[print$]"/> share, and so on. The ESP Print Pro package includes the CUPS driver
-files as well as a (licensed) set of Adobe drivers for the Windows 95/98/Me client family.
-</para>
-</sect2>
-
-<sect2>
-<title>Caveats to Be Considered</title>
-
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-<indexterm><primary>cups.hlp</primary></indexterm>
-<indexterm><primary>WIN40</primary></indexterm>
-<indexterm><primary>W32X86</primary></indexterm>
-Once you have run the install script (and possibly manually moved the <filename>cups.hlp</filename> file to
-<filename>/usr/share/cups/drivers/</filename>), the driver is ready to be put into Samba's <smbconfsection
-name="[print$]"/> share (which often maps to <filename>/etc/samba/drivers/</filename> and contains a
-subdirectory tree with <emphasis>WIN40</emphasis> and <emphasis>W32X86</emphasis> branches). You do this by
-running <command>cupsaddsmb</command> (see also <command>man cupsaddsmb</command> for CUPS since release
-1.1.16).
-</para>
-
-<tip><para>
-<indexterm><primary>Single Sign-On</primary></indexterm>
-<indexterm><primary>Domain Controller</primary></indexterm>
-You may need to put root into the smbpasswd file by running <command>smbpasswd</command>; this is especially
-important if you should run this whole procedure for the first time and are not working in an environment
-where everything is configured for <emphasis>single sign-on</emphasis> to a Windows Domain Controller.
-</para></tip>
-
-<para>
-Once the driver files are in the <smbconfsection name="[print$]"/> share and are initialized, they are ready
-to be downloaded and installed by the Windows NT/200x/XP clients.
-</para>
-
-<note><para>
-Win 9x/Me clients will not work with the CUPS PostScript driver. For these you still need to use the
-<filename>ADOBE*.*</filename> drivers, as previously stated.
-</para></note>
-
-<note>
-<para>
-It is not harmful if you still have the <filename>ADOBE*.*</filename> driver files from previous installations
-in the <filename>/usr/share/cups/drivers/</filename> directory. The new <command>cupsaddsmb</command> (from
-1.1.16) will automatically prefer its own drivers if it finds both.
-</para></note>
-
-<note><para>
-<indexterm><primary>"Printers" folder</primary></indexterm>
-<indexterm><primary>Adobe PostScript</primary></indexterm>
-Should your Windows clients have had the old <filename>ADOBE*.*</filename> files for the Adobe PostScript
-driver installed, the download and installation of the new CUPS PostScript driver for Windows NT/200x/XP will
-fail at first. You need to wipe the old driver from the clients first. It is not enough to
-<quote>delete</quote> the printer, because the driver files will still be kept by the clients and re-used if
-you try to re-install the printer. To really get rid of the Adobe driver files on the clients, open the
-<guilabel>Printers</guilabel> folder (possibly via <guilabel>Start -> Settings -> Control Panel ->
-Printers</guilabel>), right-click on the folder background, and select <guimenuitem>Server
-Properties</guimenuitem>. When the new dialog opens, select the <guilabel>Drivers</guilabel> tab. On the list
-select the driver you want to delete and click the <guilabel>Delete</guilabel> button. This will only work if
-there is not one single printer left that uses that particular driver. You need to <quote>delete</quote> all
-printers using this driver in the <guilabel>Printers</guilabel> folder first. You will need Administrator
-privileges to do this.
-</para></note>
-
-<note><para>
-<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
-<indexterm><primary>CUPS PostScript</primary></indexterm>
-Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all
-printers to this one by proceeding as described in <link linkend="classicalprinting">Classical Printing
-Support</link>. Either change a driver for an existing printer by running the <guilabel>Printer
-Properties</guilabel> dialog, or use <command>rpcclient</command> with the <command>setdriver</command>
-subcommand.
-</para></note>
-</sect2>
-
-<sect2>
-<title>Windows CUPS PostScript Driver Versus Adobe Driver</title>
-
-<para>
-Are you interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes, these
-are the most important items that weigh in favor of CUPS:
-</para>
-
-<itemizedlist>
- <listitem><para>No hassle with the Adobe EULA.</para></listitem>
-
- <listitem><para>No hassle with the question, <quote>Where do I
- get the ADOBE*.* driver files?</quote></para></listitem>
-
- <listitem><para>
- <indexterm><primary>PJL</primary></indexterm>
- The Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the
- main PostScript part of the print file. Thus, the print file starts with <parameter><1B
- >%-12345X</parameter> or <parameter><escape>%-12345X</parameter> instead of
- <parameter>%!PS</parameter>. This leads to the CUPS daemon autotyping the incoming file as a print-ready file,
- not initiating a pass through the <parameter>pstops</parameter> filter (to speak more technically, it is not
- regarded as the generic MIME-type <indexterm><primary>application/postscript</primary></indexterm>
- <parameter>application/postscript</parameter>, but as the more special MIME type
- <indexterm><primary>application/cups.vnd-postscript</primary></indexterm>
- <parameter>application/cups.vnd-postscript</parameter>), which therefore also leads to the page accounting in
- <parameter>/var/log/cups/page_log</parameter> not receiving the exact number of pages; instead the dummy page
- number of <quote>1</quote> is logged in a standard setup).
- </para></listitem>
-
- <listitem><para>The Adobe driver has more options to misconfigure the
-<indexterm><primary>Adobe driver</primary></indexterm>
- PostScript generated by it (like setting it inadvertently to
- <guilabel>Optimize for Speed</guilabel> instead of
- <guilabel>Optimize for Portability</guilabel>, which
- could lead to CUPS being unable to process it).</para></listitem>
-
- <listitem><para>The CUPS PostScript driver output sent by Windows
-<indexterm><primary>CUPS PostScript driver</primary></indexterm>
- clients to the CUPS server is guaranteed to autotype
- as the generic MIME type <parameter>application/postscript</parameter>,
- thus passing through the CUPS <parameter>pstops</parameter> filter and logging the
- correct number of pages in the <filename>page_log</filename> for
- accounting and quota purposes.</para></listitem>
-
- <listitem><para>
- <indexterm><primary>banner pages</primary></indexterm>
- The CUPS PostScript driver supports the sending of additional standard (IPP) print options by Windows
- NT/200x/XP clients. Such additional print options are naming the CUPS standard <emphasis>banner
- pages</emphasis> (or the custom ones, should they be installed at the time of driver download), using the CUPS
- page-label option, setting a job priority, and setting the scheduled time of printing (with the option to
- support additional useful IPP job attributes in the future).
- </para></listitem>
-
- <listitem><para>The CUPS PostScript driver supports the inclusion of
- the new <parameter>*cupsJobTicket</parameter> comments at the
- beginning of the PostScript file (which could be used in the future
- for all sorts of beneficial extensions on the CUPS side, but which will
- not disturb any other applications because they will regard it as a comment
- and simply ignore it).</para></listitem>
-
- <listitem><para>The CUPS PostScript driver will be the heart of the
- fully fledged CUPS IPP client for Windows NT/200x/XP to be released soon
- (probably alongside the first beta release for CUPS 1.2).</para></listitem>
-</itemizedlist>
-
-</sect2>
-
-<sect2>
-<title>Run cupsaddsmb (Quiet Mode)</title>
-
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-<indexterm><primary>point 'n' print</primary></indexterm>
-The <command>cupsaddsmb</command> command copies the needed files into your <smbconfsection name="[print$]"/>
-share. Additionally, the PPD associated with this printer is copied from <filename>/etc/cups/ppd/</filename>
-to <smbconfsection name="[print$]"/>. There the files wait for convenient Windows client installations via
-Point'n'Print. Before we can run the command successfully, we need to be sure that we can authenticate toward
-Samba. If you have a small network, you are probably using user-level security (<smbconfoption
-name="security">user</smbconfoption>).
-</para>
-
-<para>
-Here is an example of a successfully run <command>cupsaddsmb</command> command:
-<indexterm><primary>banner pages</primary></indexterm>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-<screen>
-&rootprompt;<userinput>cupsaddsmb -U root infotec_IS2027</userinput>
-Password for root required to access localhost via Samba: <userinput>['secret']</userinput>
-</screen></para>
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-To share <emphasis>all</emphasis> printers and drivers, use the
-<option>-a</option> parameter instead of a printer name. Since
-<command>cupsaddsmb</command> <quote>exports</quote> the printer drivers to Samba, it should be
-obvious that it only works for queues with a CUPS driver associated.
-</para>
-</sect2>
-
-<sect2>
-<title>Run cupsaddsmb with Verbose Output</title>
-
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-Probably you want to see what's going on. Use the
-<option>-v</option> parameter to get a more verbose output. The
-output below was edited for better readability: all <quote>\</quote> at the end of
-a line indicate that I inserted an artificial line break plus some
-indentation here:
-<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>cupsaddsmb -U root -v infotec_2105</userinput>
-Password for root required to access localhost via &example.server.samba;:
-Running command: smbclient //localhost/print\$ -N -U'root%secret' \
- -c 'mkdir W32X86; \
- put /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd; \
- put /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll; \
- put /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll; \
- put /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
-added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
-NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd
-putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll
-putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
-putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
-
-Running command: rpcclient localhost -N -U'root%secret'
- -c 'adddriver "Windows NT x86" \
- "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL: \
- RAW:NULL"'
-cmd = adddriver "Windows NT x86" \
- "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL: \
- RAW:NULL"
-Printer Driver infotec_2105 successfully installed.
-
-Running command: smbclient //localhost/print\$ -N -U'root%secret' \
--c 'mkdir WIN40; \
- put /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; \
- put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM; \
- put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV; \
- put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP; \
- put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD; \
- put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL; \
- put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
- added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
- Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
- putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD
- putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM
- putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV
- putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP
- putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD
- putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL
- putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL
-
- Running command: rpcclient localhost -N -U'root%secret' \
- -c 'adddriver "Windows 4.0" \
- "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
- PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
- ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
- cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:\
- infotec_2105.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,\
- infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,\
- ICONLIB.DLL"
- Printer Driver infotec_2105 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret' \
- -c 'setdriver infotec_2105 infotec_2105'
- cmd = setdriver infotec_2105 infotec_2105
- Successfully set infotec_2105 to driver infotec_2105.
-</screen></para>
-
-<warning><para>
-You will see the root password for the Samba account printed on screen.
-</para></warning>
-
-<para>
-If you look closely, you'll discover your root password was transferred unencrypted over the wire, so beware!
-Also, if you look further, you may discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in the output.
-This will occur when the directories WIN40 and W32X86 already existed in the <smbconfsection name="[print$]"/>
-driver download share (from a previous driver installation). These are harmless warning messages.
-</para>
-</sect2>
-
-<sect2>
-<title>Understanding cupsaddsmb</title>
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-What has happened? What did <command>cupsaddsmb</command> do? There are five stages of the procedure:
-</para>
-
-<orderedlist>
- <listitem><para>
- <indexterm><primary>IPP</primary></indexterm>
- Call the CUPS server via IPP and request the driver files and the PPD file for the named printer.</para></listitem>
-
- <listitem><para>Store the files temporarily in the local TEMPDIR (as defined in <filename>cupsd.conf</filename>).</para></listitem>
-
- <listitem><para>Connect via smbclient to the Samba server's <smbconfsection name="[print$]"/> share and put the files into the
- share's WIN40 (for Windows 9x/Me) and W32X86 (for Windows NT/200x/XP) subdirectories.</para></listitem>
-
- <listitem><para>
- <indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
- Connect via rpcclient to the Samba server and execute the <command>adddriver</command> command with the correct parameters.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
- Connect via rpcclient to the Samba server a second time and execute the <command>setdriver</command> command.</para></listitem>
-</orderedlist>
-
-<note>
-<para>
-You can run the <command>cupsaddsmb</command> utility with parameters to specify one remote host as Samba host
-and a second remote host as CUPS host. Especially if you want to get a deeper understanding, it is a good idea
-to try it and see more clearly what is going on (though in real life most people will have their CUPS and
-Samba servers run on the same host):
-<screen>
-&rootprompt;<userinput>cupsaddsmb -H sambaserver -h cupsserver -v printer</userinput>
-</screen>
-</para></note>
-
-</sect2>
-
-<sect2>
-<title>How to Recognize If cupsaddsmb Completed Successfully</title>
-
-<para>
-You <emphasis>must</emphasis> always check if the utility completed
-successfully in all fields. You need at minimum these three messages
-among the output:
-</para>
-
-<orderedlist>
- <listitem><para><emphasis>Printer Driver infotec_2105 successfully
- installed.</emphasis> # (for the W32X86 == Windows NT/200x/XP
- architecture).</para></listitem>
-
- <listitem><para><emphasis>Printer Driver infotec_2105 successfully
- installed.</emphasis> # (for the WIN40 == Windows 9x/Me
- architecture).</para></listitem>
-
- <listitem><para><emphasis>Successfully set [printerXPZ] to driver
- [printerXYZ].</emphasis></para></listitem>
-</orderedlist>
-
-<para>
-These messages are probably not easily recognized in the general
-output. If you run <command>cupsaddsmb</command> with the <option>-a</option>
-parameter (which tries to prepare <emphasis>all</emphasis> active CUPS
-printer drivers for download), you might miss if individual printer
-drivers had problems installing properly. A redirection of the
-output will help you analyze the results in retrospective.
-</para>
-
-<para>
-If you get:
-<screen>
-SetPrinter call failed!
-result was WERR_ACCESS_DENIED
-</screen>
-it means that you might have set <smbconfoption name="use client driver">yes</smbconfoption> for this printer.
-Setting it to <quote>no</quote> will solve the problem. Refer to the &smb.conf; man page for explanation of
-the <parameter>use client driver</parameter>.
-</para>
-
-<note><para>
-It is impossible to see any diagnostic output if you do not run <command>cupsaddsmb</command> in verbose mode.
-Therefore, we strongly recommend against use of the default quiet mode. It will hide any problems from you that
-might occur.
-</para></note>
-</sect2>
-
-<sect2>
-<title>cupsaddsmb with a Samba PDC</title>
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-Can't get the standard <command>cupsaddsmb</command> command to run on a Samba PDC? Are you asked for the
-password credential again and again, and the command just will not take off at all? Try one of these
-variations:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>cupsaddsmb -U &example.workgroup;\\root -v printername</userinput>
-&rootprompt;<userinput>cupsaddsmb -H &example.pdc.samba; -U &example.workgroup;\\root -v printername</userinput>
-&rootprompt;<userinput>cupsaddsmb -H &example.pdc.samba; -U &example.workgroup;\\root -h cups-server -v printername</userinput>
-</screen></para>
-
-<para>
-(Note the two backslashes: the first one is required to <quote>escape</quote> the second one).
-</para>
-</sect2>
-
-<sect2>
-<title>cupsaddsmb Flowchart</title>
-
-<para>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-<indexterm><primary>raw print</primary></indexterm>
-<link linkend="small14">The cupsaddsmb Flowchart</link> shows a chart about the procedures, command flows, and
-data flows of the <command>cupaddsmb</command> command. Note again: cupsaddsmb is
-not intended to, and does not work with, raw print queues!
-</para>
-
- <figure id="small14">
- <title>cupsaddsmb Flowchart.</title>
- <imagefile>14small</imagefile></figure>
-</sect2>
-
-<sect2>
-<title>Installing the PostScript Driver on a Client</title>
-
-<para>
-<indexterm><primary>point'n'print</primary></indexterm>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-After <command>cupsaddsmb</command> is completed, your driver is prepared for the clients to use. Here are the
-steps you must perform to download and install it via Point'n'Print. From a Windows client, browse to the
-CUPS/Samba server:
-</para>
-
-<itemizedlist>
-
- <listitem><para>
- <indexterm><primary>"Printers" folder</primary></indexterm>
- Open the <guilabel>Printers</guilabel> share of Samba in Network Neighborhood.</para></listitem>
-
- <listitem><para>Right-click on the printer in question.</para></listitem>
-
- <listitem><para>From the opening context menu select
- <guimenuitem>Install...</guimenuitem> or
- <guimenuitem>Connect...</guimenuitem> (depending on the Windows version you use).</para></listitem>
-</itemizedlist>
-
-<para>
-After a few seconds, there should be a new printer in your client's <emphasis>local</emphasis>
-<guilabel>Printers</guilabel> folder. On Windows XP it will follow a naming convention of
-<emphasis>PrinterName on SambaServer</emphasis>. (In my current case it is infotec_2105 on kde-bitshop). If
-you want to test it and send your first job from an application like Microsoft Word,
-the new printer appears in a
-<filename>\\SambaServer\PrinterName</filename> entry in the drop-down list of available printers.
-</para>
-
-<para>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>Adobe PostScript driver</primary></indexterm>
-<indexterm><primary>net use lpt1:</primary></indexterm>
-<command>cupsaddsmb</command> will only reliably work with CUPS version 1.1.15 or higher and with Samba
-version 2.2.4, or later. If it does not work, or if the automatic printer driver download to the clients does
-not succeed, you can still manually install the CUPS printer PPD on top of the Adobe PostScript driver on
-clients. Then point the client's printer queue to the Samba printer share for a UNC type of connection:
-<screen>
-&dosprompt;<userinput>net use lpt1: \\sambaserver\printershare /user:ntadmin</userinput>
-</screen>
-should you desire to use the CUPS networked PostScript RIP functions. (Note that user <quote>ntadmin</quote>
-needs to be a valid Samba user with the required privileges to access the printershare.) This sets up the
-printer connection in the traditional LanMan way (not using MS-RPC).
-</para>
-</sect2>
-
-<sect2 id="cups-avoidps1">
-<title>Avoiding Critical PostScript Driver Settings on the Client</title>
-
-<para>
-Printing works, but there are still problems. Most jobs print well, some do not print at all. Some jobs have
-problems with fonts, which do not look very good. Some jobs print fast and some are dead-slow. Many of these
-problems can be greatly reduced or even completely eliminated if you follow a few guidelines. Remember, if
-your print device is not PostScript-enabled, you are treating your Ghostscript installation on your CUPS host
-with the output your client driver settings produce. Treat it well:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Avoid the PostScript Output Option: Optimize for Speed setting. Use the Optimize for Portability instead
- (Adobe PostScript driver).</para></listitem>
-
- <listitem><para>
- Don't use the Page Independence: NO setting. Instead, use Page Independence: YES (CUPS PostScript Driver).
- </para></listitem>
-
- <listitem><para>
- Recommended is the True Type Font Downloading Option: Native True Type over Automatic and Outline;
- you should by all means avoid Bitmap (Adobe PostScript Driver).</para></listitem>
-
- <listitem><para>
- Choose True Type Font: Download as Softfont into Printer over the default Replace by Device
- Font (for exotic fonts, you may need to change it back to get a printout at all; Adobe).</para></listitem>
-
- <listitem><para>
- Sometimes you can choose PostScript Language Level: in case of problems try 2
- instead of 3 (the latest ESP Ghostscript package handles Level 3 PostScript very well; Adobe).
- </para></listitem>
-
- <listitem><para>
- Say Yes to PostScript Error Handler (Adobe).</para></listitem>
-</itemizedlist>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Installing PostScript Driver Files Manually Using rpcclient</title>
-
-<para>
-Of course, you can run all the commands that are embedded into the
-cupsaddsmb convenience utility yourself, one by one, and upload
-and prepare the driver files for future client downloads.
-</para>
-
-<orderedlist>
- <listitem><para>Prepare Samba (a CUPS print queue with the name of the
- printer should be there. We are providing the driver now).</para></listitem>
-
- <listitem><para>Copy all files to <smbconfsection name="[print$]"/>.</para></listitem>
-
- <listitem><para>
- <indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
- Run <command>rpcclient adddriver</command>
- (for each client architecture you want to support).</para></listitem>
-
- <listitem><para>
- <indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
- Run <command>rpcclient setdriver.</command></para></listitem>
-</orderedlist>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>enumports</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>enumdrivers</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
-We are going to do this now. First, read the man page on <parameter>rpcclient</parameter> to get a first idea.
-Look at all the printing-related subcommands: <command>enumprinters</command>, <command>enumdrivers</command>,
-<command>enumports</command>, <command>adddriver</command>, and <command>setdriver</command> are among the
-most interesting ones. <parameter>rpcclient</parameter> implements an important part of the MS-RPC protocol.
-You can use it to query (and command) a Windows NT (or 200x/XP) PC, too. MS-RPC is used by Windows clients,
-among other things, to benefit from the Point'n'Print features. Samba can now mimic this as well.
-</para>
-
-<sect2>
-<title>A Check of the rpcclient man Page</title>
-
-<para>
-First let's check the <parameter>rpcclient</parameter> man page. Here are two relevant passages:
-</para>
-
-<para>
-<indexterm><primary>adddriver</primary></indexterm>
-<indexterm><primary>AddPrinterDriver()</primary></indexterm>
-<indexterm><primary>getdriverdir</primary></indexterm>
-<command>adddriver <arch> <config></command> Execute an <command>AddPrinterDriver()</command> RPC
-to install the printer driver information on the server. The driver files should already exist in the
-directory returned by <command>getdriverdir</command>. Possible values for <parameter>arch</parameter> are the
-same as those for the <command>getdriverdir</command> command. The <parameter>config</parameter> parameter is
-defined as follows:
-<screen>
-Long Printer Name:\
-Driver File Name:\
-Data File Name:\
-Config File Name:\
-Help File Name:\
-Language Monitor Name:\
-Default Data Type:\
-Comma Separated list of Files
-</screen></para>
-
-<para>
-Any empty fields should be entered as the string <quote>NULL</quote>.
-</para>
-
-<para>
-Samba does not need to support the concept of print monitors, since these only apply to local printers whose
-drivers can use a bidirectional link for communication. This field should be <quote>NULL</quote>. On a remote
-NT print server, the print monitor for a driver must already be installed before adding the driver or else the
-RPC will fail.
-</para>
-
-<para>
-<indexterm><primary>setdriver</primary></indexterm>
-<indexterm><primary>SetPrinter()</primary></indexterm>
-<command>setdriver <printername> <drivername></command> Execute a <command>SetPrinter()</command>
-command to update the printer driver associated with an installed printer. The printer driver must already be
-correctly installed on the print server.
-</para>
-
-<para>
-<indexterm><primary>enumprinters</primary></indexterm>
-<indexterm><primary>enumdrivers</primary></indexterm>
-See also the <command>enumprinters</command> and <command>enumdrivers</command> commands to
-obtain a list of installed printers and drivers.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Understanding the rpcclient man Page</title>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
-The <emphasis>exact</emphasis> format isn't made too clear by the man page, since you have to deal with some
-parameters containing spaces. Here is a better description for it. We have line-broken the command and
-indicated the breaks with <quote>\</quote>. Usually you would type the command in one line without the line
-breaks:
-<screen>
-adddriver "Architecture" \
- "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
- LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
-</screen></para>
-
-<para>
-What the man pages denote as a simple <parameter><config></parameter> keyword in reality consists of
-eight colon-separated fields. The last field may take multiple (in some very insane cases, even 20 different
-additional) files. This might sound confusing at first. What the man pages call the
-<quote>LongPrinterName</quote> in reality should be called the <quote>Driver Name</quote>. You can name it
-anything you want, as long as you use this name later in the <command>rpcclient ... setdriver</command>
-command. For practical reasons, many name the driver the same as the printer.
-</para>
-
-<para>
-It isn't simple at all. I hear you asking: <quote>How do I know which files are Driver File</quote>,
-<quote>Data File</quote>, <quote>Config File</quote>, <quote>Help File</quote> and <quote>Language Monitor
-File in each case?</quote> For an answer, you may want to have a look at how a Windows NT box with a shared
-printer presents the files to us. Remember that this whole procedure has to be developed by the Samba Team by
-listening to the traffic caused by Windows computers on the wire. We may as well turn to a Windows box now and
-access it from a UNIX workstation. We will query it with <command>rpcclient</command> to see what it tells us
-and try to understand the man page more clearly.
-</para>
-</sect2>
-
-<sect2>
-<title>Producing an Example by Querying a Windows Box</title>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
-We could run <command>rpcclient</command> with a <command>getdriver</command> or a
-<command>getprinter</command> subcommand (in level 3 verbosity) against it. Just sit down at a UNIX or Linux
-workstation with the Samba utilities installed, then type the following command:
-<screen>
-&rootprompt;<userinput>rpcclient -U'user%secret' NT-SERVER -c 'getdriver printername 3'</userinput>
-</screen></para>
-
-<para>
-From the result it should become clear which is which. Here is an example from my installation:
-<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient -U'Danka%xxxx' W200xSERVER \
- -c'getdriver "DANKA InfoStream Virtual Printer" 3'</userinput>
- cmd = getdriver "DANKA InfoStream Virtual Printer" 3
-
- [Windows NT x86]
- Printer Driver Info 3:
- Version: [2]
- Driver Name: [DANKA InfoStream]
- Architecture: [Windows NT x86]
- Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.DLL]
- Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\INFOSTRM.PPD]
- Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRPTUI.DLL]
- Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.HLP]
-
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
- Dependentfiles: []
-
- Monitorname: []
- Defaultdatatype: []
-</screen></para>
-
-<para>
-Some printer drivers list additional files under the label <parameter>Dependentfiles</parameter>, and these
-would go into the last field <parameter>ListOfFiles,Comma-separated</parameter>. For the CUPS PostScript
-drivers, we do not need any (nor would we for the Adobe PostScript driver); therefore, the field will get a
-<quote>NULL</quote> entry.
-</para>
-</sect2>
-
-<sect2>
-<title>Requirements for adddriver and setdriver to Succeed</title>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
-<indexterm><primary>cupsaddsmb</primary></indexterm>
-<indexterm><primary>setdriver</primary></indexterm>
-From the man page (and from the quoted output of <command>cupsaddsmb</command> above) it becomes clear that
-you need to have certain conditions in order to make the manual uploading and initializing of the driver files
-succeed. The two <command>rpcclient</command> subcommands (<command>adddriver</command> and
-<command>setdriver</command>) need to encounter the following preconditions to complete successfully:
-</para>
-
-<itemizedlist>
- <listitem><para>You are connected as <smbconfoption name="printer admin"/> or root (this is
- <emphasis>not</emphasis> the <quote>Printer Operators</quote> group in NT, but the <emphasis>printer
- admin</emphasis> group as defined in the <smbconfsection name="[global]"/> section of &smb.conf;).
- </para></listitem>
-
- <listitem><para>Copy all required driver files to <filename>\\SAMBA\print$\w32x86</filename> and
- <filename>\\SAMBA\print$\win40</filename> as appropriate. They will end up in the <quote>0</quote> respective
- <quote>2</quote> subdirectories later. For now, <emphasis>do not</emphasis> put them there; they'll be
- automatically used by the <command>adddriver</command> subcommand. (If you use <command>smbclient</command> to
- put the driver files into the share, note that you need to escape the <quote>$</quote>: <command>smbclient
- //sambaserver/print\$ -U root.</command>)</para></listitem>
-
- <listitem><para>The user you're connecting as must be able to write to
- the <smbconfsection name="[print$]"/> share and create
- subdirectories.</para></listitem>
-
- <listitem><para>The printer you are going to set up for the Windows
- clients needs to be installed in CUPS already.</para></listitem>
-
- <listitem><para>
- <indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
- <indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
- The CUPS printer must be known to Samba; otherwise the <command>setdriver</command> subcommand fails with an
- NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by Samba, you may use the
- <command>enumprinters</command> subcommand to <command>rpcclient</command>. A long-standing bug prevented a
- proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember
- this in case you've created the CUPS printer just recently and encounter problems: try restarting Samba.
- </para></listitem>
-</itemizedlist>
-</sect2>
-
-<sect2>
-<title>Manual Driver Installation in 15 Steps</title>
-
-<para>
-We are going to install a printer driver now by manually executing all
-required commands. Because this may seem a rather complicated process at
-first, we go through the procedure step by step, explaining every
-single action item as it comes up.
-</para>
-
-<procedure>
-<title>Manual Driver Installation</title>
-
- <step>
- <title>Install the printer on CUPS.</title>
-
- <para><screen>
- &rootprompt;<userinput>lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E \
- -P canonIR85.ppd</userinput>
- </screen></para>
-
- <para>
- This installs a printer with the name <parameter>mysmbtstprn</parameter>
- to the CUPS system. The printer is accessed via a socket
- (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
- for this step.
- </para>
- </step>
-
- <step>
- <title>(Optional.) Check if the printer is recognized by Samba.</title>
-
- <para>
- <indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
- | grep -C2 mysmbtstprn</userinput>
-flags:[0x800000]
-name:[\\kde-bitshop\mysmbtstprn]
-description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
-comment:[mysmbtstprn]
-</screen>
- </para>
-
- <para>
- This should show the printer in the list. If not, stop and restart the Samba daemon (smbd) or send a HUP signal:
-<screen>
-&rootprompt;<userinput>kill -HUP `pidof smbd`</userinput>
-</screen>
- Check again. Troubleshoot and repeat until successful. Note the <quote>empty</quote> field between the two
- commas in the <quote>description</quote> line. The driver name would appear here if there was one already. You
- need to know root's Samba password (as set by the <command>smbpasswd</command> command) for this step and most
- of the following steps. Alternatively, you can authenticate as one of the users from the <quote>write
- list</quote> as defined in &smb.conf; for <smbconfsection name="[print$]"/>.
- </para>
- </step>
-
- <step>
- <title>(Optional.) Check if Samba knows a driver for the printer.</title>
-
- <para>
- <indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
- <indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2'\
- localhost | grep driver </userinput>
-
-drivername:[]
-
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' \
- localhost | grep -C4 driv</userinput>
-
-servername:[\\kde-bitshop]
-printername:[\\kde-bitshop\mysmbtstprn]
-sharename:[mysmbtstprn]
-portname:[Samba Printer Port]
-drivername:[]
-comment:[mysmbtstprn]
-location:[]
-sepfile:[]
-printprocessor:[winprint]
-
-&rootprompt;<userinput>rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost</userinput>
- result was WERR_UNKNOWN_PRINTER_DRIVER
-</screen></para>
-
-<para>
-None of the three commands shown above should show a driver.
-This step was done for the purpose of demonstrating this condition. An
-attempt to connect to the printer at this stage will prompt a
-message along the lines of, <quote>The server does not have the required printer
-driver installed.</quote>
-</para>
-</step>
-
-<step>
-<title>Put all required driver files into Samba's
-[print$].</title>
-
-<para><screen>
-&rootprompt;<userinput>smbclient //localhost/print\$ -U 'root%xxxx' \
- -c 'cd W32X86; \
- put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \
- put /usr/share/cups/drivers/cupsui.dll cupsui.dll; \
- put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
- put /usr/share/cups/drivers/cups.hlp cups.hlp'</userinput>
-</screen></para>
-
-<para>
-(This command should be entered in one long single line. Line breaks and the line ends indicated by
-<quote>\</quote> have been inserted for readability reasons.) This step is <emphasis>required</emphasis> for
-the next one to succeed. It makes the driver files physically present in the <smbconfsection name="[print$]"/>
-share. However, clients would still not be able to install them, because Samba does not yet treat them as
-driver files. A client asking for the driver would still be presented with a <quote>not installed here</quote>
-message.
-</para>
-</step>
-
-<step>
-<title>Verify where the driver files are now.</title>
-
-<para><screen>
-&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/</userinput>
-total 669
-drwxr-sr-x 2 root ntadmin 532 May 25 23:08 2
-drwxr-sr-x 2 root ntadmin 670 May 16 03:15 3
--rwxr--r-- 1 root ntadmin 14234 May 25 23:21 cups.hlp
--rwxr--r-- 1 root ntadmin 278380 May 25 23:21 cupsdrvr.dll
--rwxr--r-- 1 root ntadmin 215848 May 25 23:21 cupsui.dll
--rwxr--r-- 1 root ntadmin 169458 May 25 23:21 mysmbtstprn.PPD
-</screen></para>
-
-<para>
-The driver files now are in the W32X86 architecture <quote>root</quote> of
-<smbconfsection name="[print$]"/>.
-</para>
-</step>
-
-<step>
-<title>Tell Samba that these are driver files (<command>adddriver</command>).</title>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>adddriver</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
- "mydrivername:cupsdrvr.dll:mysmbtstprn.PPD: \
- cupsui.dll:cups.hlp:NULL:RAW:NULL"' \
- localhost</userinput>
-Printer Driver mydrivername successfully installed.
-</screen></para>
-
-<para>
-You cannot repeat this step if it fails. It could fail even as a result of a simple typo. It will most likely
-have moved a part of the driver files into the <quote>2</quote> subdirectory. If this step fails, you need to
-go back to the fourth step and repeat it before you can try this one again. In this step, you need to choose a
-name for your driver. It is normally a good idea to use the same name as is used for the printer name;
-however, in big installations you may use this driver for a number of printers that obviously have different
-names, so the name of the driver is not fixed.
-</para>
-</step>
-
-<step>
-<title>Verify where the driver files are now.</title>
-
-<para><screen>
-&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/</userinput>
-total 1
-drwxr-sr-x 2 root ntadmin 532 May 25 23:22 2
-drwxr-sr-x 2 root ntadmin 670 May 16 03:15 3
-
-&rootprompt;<userinput>ls -l /etc/samba/drivers/W32X86/2</userinput>
-total 5039
-[....]
--rwxr--r-- 1 root ntadmin 14234 May 25 23:21 cups.hlp
--rwxr--r-- 1 root ntadmin 278380 May 13 13:53 cupsdrvr.dll
--rwxr--r-- 1 root ntadmin 215848 May 13 13:53 cupsui.dll
--rwxr--r-- 1 root ntadmin 169458 May 25 23:21 mysmbtstprn.PPD
-</screen></para>
-
-<para>
-Notice how step 6 also moved the driver files to the appropriate
-subdirectory. Compare this with the situation after step 5.
-</para>
-</step>
-
-<step>
-<title>(Optional.) Verify if Samba now recognizes the driver.</title>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>enumdrivers</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumdrivers 3' \
- localhost | grep -B2 -A5 mydrivername</userinput>
-Printer Driver Info 3:
-Version: [2]
-Driver Name: [mydrivername]
-Architecture: [Windows NT x86]
-Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-</screen></para>
-
-<para>
-Remember, this command greps for the name you chose for the
-driver in step 6. This command must succeed before you can proceed.
-</para>
-</step>
-
-<step>
-<title>Tell Samba which printer should use these driver files (<command>setdriver</command>).</title>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' \
- localhost</userinput>
-Successfully set mysmbtstprn to driver mydrivername
-</screen></para>
-
-<para>
-Since you can bind any printer name (print queue) to any driver, this is a convenient way to set up many
-queues that use the same driver. You do not need to repeat all the previous steps for the setdriver command to
-succeed. The only preconditions are that <command>enumdrivers</command> must find the driver and
-<command>enumprinters</command> must find the printer.
-</para>
-</step>
-
-<step>
-<title>(Optional) Verify if Samba has recognized this association.</title>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>getdriver</secondary></indexterm>
-<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
- | grep driver</userinput>
-drivername:[mydrivername]
-
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
- | grep -C4 driv</userinput>
-servername:[\\kde-bitshop]
-printername:[\\kde-bitshop\mysmbtstprn]
-sharename:[mysmbtstprn]
-portname:[Done]
-drivername:[mydrivername]
-comment:[mysmbtstprn]
-location:[]
-sepfile:[]
-printprocessor:[winprint]
-
-&rootprompt;<userinput>rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost</userinput>
-[Windows NT x86]
-Printer Driver Info 3:
- Version: [2]
- Driver Name: [mydrivername]
- Architecture: [Windows NT x86]
- Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
- Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
- Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
- Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
- Monitorname: []
- Defaultdatatype: [RAW]
- Monitorname: []
- Defaultdatatype: [RAW]
-
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
- | grep mysmbtstprn</userinput>
- name:[\\kde-bitshop\mysmbtstprn]
- description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
- comment:[mysmbtstprn]
-
-</screen></para>
-
-<para>
-<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
-Compare these results with the ones from steps 2 and 3. Every one of these commands show the driver is installed. Even
-the <command>enumprinters</command> command now lists the driver
-on the <quote>description</quote> line.
-</para>
-</step>
-
-<step>
-<title>(Optional.) Tickle the driver into a correct
-device mode.</title>
-
-<para>
-<indexterm><primary>"Printers" folder</primary></indexterm>
-You certainly know how to install the driver on the client. In case
-you are not particularly familiar with Windows, here is a short
-recipe: Browse the Network Neighborhood, go to the Samba server, and look
-for the shares. You should see all shared Samba printers.
-Double-click on the one in question. The driver should get
-installed and the network connection set up. Another way is to
-open the <guilabel>Printers (and Faxes)</guilabel> folder, right-click on the printer in
-question, and select <guilabel>Connect</guilabel> or <guilabel>Install</guilabel>. As a result, a new printer
-should appear in your client's local <guilabel>Printers (and Faxes)</guilabel>
-folder, named something like <guilabel>printersharename on Sambahostname</guilabel>.
-</para>
-
-<para>
-It is important that you execute this step as a Samba printer admin
-(as defined in &smb.conf;). Here is another method
-to do this on Windows XP. It uses a command line, which you may type
-into the <quote>DOS box</quote> (type root's smbpassword when prompted):
-</para>
-
-<para><screen>
-&dosprompt;<userinput>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry \
- /in /n \\sambaserver\mysmbtstprn"</userinput>
-</screen></para>
-
-<para>
-Change any printer setting once (like changing <emphasis><guilabel>portrait</guilabel> to
-<guilabel>landscape</guilabel></emphasis>), click on <guibutton>Apply</guibutton>, and change the setting back.
-</para>
-</step>
-
-<step>
-<title>Install the printer on a client (Point'n'Print).</title>
-
-<para>
-<indexterm significance="preferred"><primary>point 'n' print</primary></indexterm>
-<screen>
-&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /in /n "\\sambaserver\mysmbtstprn"</userinput>
-</screen>
-If it does not work, it could be a permissions problem with the <smbconfsection name="[print$]"/> share.
-</para>
-</step>
-
-<step>
-<title>(Optional) Print a test page.</title>
-
-<indexterm><primary>rundll32</primary></indexterm>
-<para><screen>
-&dosprompt;<userinput>rundll32 printui.dll,PrintUIEntry /p /n "\\sambaserver\mysmbtstprn"</userinput>
-</screen></para>
-
-<para>
-Then hit [TAB] five times, [ENTER] twice, [TAB] once, and [ENTER] again, and march to the printer.
-</para>
-</step>
-
-<step>
-<title>(Recommended.) Study the test page.</title>
-
-<para>
-Hmmm. Just kidding! By now you know everything about printer installations and you do not need to read a word.
-Just put it in a frame and bolt it to the wall with the heading "MY FIRST RPCCLIENT-INSTALLED PRINTER"
-&smbmdash; why not just throw it away!
-</para>
-</step>
-
-<step>
-<title>(Obligatory.) Enjoy. Jump. Celebrate your success.</title>
-
-<para><screen>
-&rootprompt;<userinput>echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd</userinput>
-</screen></para>
-</step>
-</procedure>
-</sect2>
-
-<sect2>
-<title>Troubleshooting Revisited</title>
-
-<para>
-<indexterm><primary>adddriver</primary></indexterm>
-The setdriver command will fail if in Samba's mind the queue is not
-already there. A successful installation displays the promising message that the:
-<screen>
-Printer Driver ABC successfully installed.
-</screen>
-following the <command>adddriver</command> parts of the procedure. But you may also see
-a disappointing message like this one:
-<computeroutput>
-result was NT_STATUS_UNSUCCESSFUL
-</computeroutput></para>
-
-<para>
-<indexterm><primary>lpstat</primary></indexterm>
-<indexterm><primary>rpcclient</primary></indexterm>
-It is not good enough that you can see the queue in CUPS, using the <command>lpstat -p ir85wm</command>
-command. A bug in most recent versions of Samba prevents the proper update of the queue list. The recognition
-of newly installed CUPS printers fails unless you restart Samba or send a HUP to all smbd processes. To verify
-if this is the reason why Samba does not execute the <command>setdriver</command> command successfully, check
-if Samba <quote>sees</quote> the printer:
-<indexterm><primary>rpcclient</primary><secondary>enumprinters</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient transmeta -N -U'root%xxxx' -c 'enumprinters 0'|grep ir85wm</userinput>
- printername:[ir85wm]
-</screen></para>
-
-<para>
-An alternate command could be this:
-<indexterm><primary>rpcclient</primary><secondary>getprinter</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' </userinput>
- cmd = getprinter ir85wm
- flags:[0x800000]
- name:[\\transmeta\ir85wm]
- description:[\\transmeta\ir85wm,ir85wm,DPD]
- comment:[CUPS PostScript-Treiber for Windows NT/200x/XP]
-</screen></para>
-
-<para>
-By the way, you can use these commands, plus a few more, of course, to install drivers on remote Windows NT print servers too!
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>The Printing <filename>*.tdb</filename> Files</title>
-
-<para>
-<indexterm><primary>TDB</primary></indexterm>
-<indexterm><primary>connections.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>printing.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>share_info.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>ntdrivers.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>unexpected.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>brlock.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>locking.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>ntforms.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>messages.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>ntprinters.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>sessionid.tdb</primary><seealso>TDB</seealso></indexterm>
-<indexterm><primary>secrets.tdb</primary><seealso>TDB</seealso></indexterm>
-Some mystery is associated with the series of files with a tdb suffix appearing in every Samba installation.
-They are <filename>connections.tdb</filename>, <filename>printing.tdb</filename>,
-<filename>share_info.tdb</filename>, <filename>ntdrivers.tdb</filename>, <filename>unexpected.tdb</filename>,
-<filename>brlock.tdb</filename>, <filename>locking.tdb</filename>, <filename>ntforms.tdb</filename>,
-<filename>messages.tdb</filename> , <filename>ntprinters.tdb</filename>, <filename>sessionid.tdb</filename>,
-and <filename>secrets.tdb</filename>. What is their purpose?
-</para>
-
-<sect2>
-<title>Trivial Database Files</title>
-
-<para>
-<indexterm><primary>TDB</primary></indexterm>
-A Windows NT (print) server keeps track of all information needed to serve its duty toward its clients by
-storing entries in the Windows registry. Client queries are answered by reading from the registry,
-Administrator or user configuration settings that are saved by writing into the registry. Samba and UNIX
-obviously do not have such a Registry. Samba instead keeps track of all client-related information in a series
-of <filename>*.tdb</filename> files. (TDB stands for trivial data base). These are often located in
-<filename>/var/lib/samba/</filename> or <filename>/var/lock/samba/</filename>. The printing-related files are
-<filename>ntprinters.tdb</filename>, <filename>printing.tdb</filename>,<filename>ntforms.tdb</filename>, and
-<filename>ntdrivers.tdb</filename>.
-</para>
-</sect2>
-
-<sect2>
-<title>Binary Format</title>
-
-<para>
-<filename>*.tdb</filename> files are not human readable. They are written in a binary format. <quote>Why not
-ASCII?</quote>, you may ask. <quote>After all, ASCII configuration files are a good and proven tradition on
-UNIX.</quote> The reason for this design decision by the Samba Team is mainly performance. Samba needs to be
-fast; it runs a separate <command>smbd</command> process for each client connection, in some environments many
-thousands of them. Some of these <command>smbds</command> might need to write-access the same
-<filename>*.tdb</filename> file <emphasis>at the same time</emphasis>. The file format of Samba's
-<filename>*.tdb</filename> files allows for this provision. Many smbd processes may write to the same
-<filename>*.tdb</filename> file at the same time. This wouldn't be possible with pure ASCII files.
-</para>
-</sect2>
-
-<sect2>
-<title>Losing <filename>*.tdb</filename> Files</title>
-
-<para>
-It is very important that all <filename>*.tdb</filename> files remain consistent over all write and read
-accesses. However, it may happen that these files <emphasis>do</emphasis> get corrupted. (A <command>kill -9
-`pidof smbd'</command> while a write access is in progress could do the damage, as could a power interruption,
-etc.). In cases of trouble, a deletion of the old printing-related <filename>*.tdb</filename> files may be the
-only option. After that, you need to re-create all print-related setups unless you have made a backup of the
-<filename>*.tdb</filename> files in time.
-</para>
-</sect2>
-
-<sect2>
-<title>Using <command>tdbbackup</command></title>
-
-<para>
-<indexterm><primary>TDB</primary><secondary>backing up</secondary><see>tdbbackup</see></indexterm>
-<indexterm><primary>tdbbackup</primary></indexterm>
-Samba ships with a little utility that helps the root user of your system to backup your
-<filename>*.tdb</filename> files. If you run it with no argument, it prints a usage message:
-<screen>
-&rootprompt;<userinput>tdbbackup</userinput>
- Usage: tdbbackup [options] <fname...>
-
- Version:3.0a
- -h this help message
- -s suffix set the backup suffix
- -v verify mode (restore if corrupt)
-</screen></para>
-
-<para>
-Here is how I backed up my <filename>printing.tdb</filename> file:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>ls</userinput>
-. browse.dat locking.tdb ntdrivers.tdb printing.tdb
-.. share_info.tdb connections.tdb messages.tdb ntforms.tdb
-printing.tdbkp unexpected.tdb brlock.tdb gmon.out namelist.debug
-ntprinters.tdb sessionid.tdb
-
-&rootprompt;<userinput>tdbbackup -s .bak printing.tdb</userinput>
- printing.tdb : 135 records
-
-&rootprompt;<userinput>ls -l printing.tdb*</userinput>
- -rw------- 1 root root 40960 May 2 03:44 printing.tdb
- -rw------- 1 root root 40960 May 2 03:44 printing.tdb.bak
-
-</screen></para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>CUPS Print Drivers from Linuxprinting.org</title>
-
-<para>
-<indexterm><primary>Linuxprinting.org</primary></indexterm>
-CUPS ships with good support for HP LaserJet-type printers. You can install the generic driver as follows:
-<indexterm><primary>lpadmin</primary></indexterm>
-<screen>
-&rootprompt;<userinput>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd</userinput>
-</screen></para>
-
-<para>
-The <option>-m</option> switch will retrieve the <filename>laserjet.ppd</filename> from the standard
-repository for not-yet-installed PPDs, which CUPS typically stores in
-<filename>/usr/share/cups/model</filename>. Alternatively, you may use <option>-P /path/to/your.ppd</option>.
-</para>
-
-<para>
-The generic <filename>laserjet.ppd,</filename> however, does not support every special option for every
-LaserJet-compatible model. It constitutes a sort of <quote>least common denominator</quote> of all the models.
-If for some reason you must pay for the commercially available ESP Print Pro drivers, your first move should
-be to consult the database on the <ulink noescape="1"
-url="http://www.linuxprinting.org/printer_list.cgi">Linuxprinting</ulink> Web site. Linuxprinting.org has
-excellent recommendations about which driver is best used for each printer. Its database is kept current by
-the tireless work of Till Kamppeter from Mandrakesoft, who is also the principal author of the
-<command>foomatic-rip</command> utility.
-</para>
-
-<note><para>
-<indexterm><primary>foomatic-rip</primary></indexterm>
-<indexterm><primary>cupsomatic</primary></indexterm>
-<indexterm><primary>Adobe PPD</primary></indexterm>
-The former <command>cupsomatic</command> concept is now being replaced by the new successor, a much more
-powerful <command>foomatic-rip</command>. <command>cupsomatic</command> is no longer maintained. Here is the
-new URL to the <ulink noescape="1" url="http://www.linuxprinting.org/driver_list.cgi">Foomatic-3.0</ulink>
-database. If you upgrade to <command>foomatic-rip</command>, remember to also upgrade to the new-style PPDs
-for your Foomatic-driven printers. foomatic-rip will not work with PPDs generated for the old
-<command>cupsomatic</command>. The new-style PPDs are 100% compliant with the Adobe PPD specification. They
-are also intended to be used by Samba and the cupsaddsmb utility, to provide the driver files for the Windows
-clients!
-</para></note>
-
-<sect2>
-<title>foomatic-rip and Foomatic Explained</title>
-
-
-<para>
-<indexterm significance="preferred"><primary>foomatic</primary></indexterm>
-<indexterm significance="preferred"><primary>foomatic-rip</primary></indexterm>
-Nowadays, most Linux distributions rely on the utilities from the <ulink
-url="http://www.linuxprinting.org/">Linuxprinting.org</ulink> to create their printing-related software
-(which, by the way, works on all UNIXes and on Mac OS X and Darwin, too). The utilities from this sire have a
-very end-user-friendly interface that allows for an easy update of drivers and PPDs for all supported models,
-all spoolers, all operating systems, and all package formats (because there is none). Its history goes back a
-few years.
-</para>
-
-<para>
-Recently, Foomatic has achieved the astonishing milestone of <ulink
-url="http://www.linuxprinting.org/printer_list.cgi?make=Anyone">1,000 listed</ulink> printer models.
-Linuxprinting.org keeps all the important facts about printer drivers, supported models, and which options are
-available for the various driver/printer combinations in its <ulink
-url="http://www.linuxprinting.org/foomatic.html">Foomatic</ulink> database. Currently there are <ulink
-url="http://www.linuxprinting.org/driver_list.cgi">245 drivers</ulink> in the database. Many drivers support
-various models, and many models may be driven by different drivers &smbmdash; its your choice!
-</para>
-
-<sect3>
-<title>690 <quote>Perfect</quote> Printers</title>
-
-<para>
-<indexterm><primary>Windows PPD</primary></indexterm>
-At present, there are 690 devices dubbed as working perfectly: 181 are <emphasis>mostly</emphasis> perfect, 96
-are <emphasis>partially</emphasis> perfect, and 46 are paperweights. Keeping in mind that most of these are
-non-PostScript models (PostScript printers are automatically supported by CUPS to perfection by using their
-own manufacturer-provided Windows PPD), and that a multifunctional device never qualifies as working perfectly
-if it does not also scan and copy and fax under GNU/Linux &smbmdash; then this is a truly astonishing
-achievement! Three years ago the number was not more than 500, and Linux or UNIX printing at the time wasn't
-anywhere near the quality it is today.
-</para>
-</sect3>
-
-<sect3>
-<title>How the Printing HOWTO Started It All</title>
-
-<para>
-A few years ago <ulink url="http://www2.picante.com/">Grant Taylor</ulink> started it all. The
-roots of today's Linuxprinting.org are in the first <ulink
-url="http://www.linuxprinting.org/foomatic2.9/howto/">Linux Printing HOWTO</ulink> that he authored. As a
-side-project to this document, which served many Linux users and admins to guide their first steps in this
-complicated and delicate setup (to a scientist, printing is <quote>applying a structured deposition of
-distinct patterns of ink or toner particles on paper substrates</quote>), he started to build in a little
-Postgres database with information about the hardware and driver zoo that made up Linux printing of the time.
-This database became the core component of today's Foomatic collection of tools and data. In the meantime, it
-has moved to an XML representation of the data.
-</para>
-</sect3>
-
-<sect3>
-<title>Foomatic's Strange Name</title>
-
-
-<para>
-<indexterm><primary>foomatic</primary></indexterm>
-<quote>Why the funny name?</quote> you ask. When it really took off, around spring 2000, CUPS was far less
-popular than today, and most systems used LPD, LPRng, or even PDQ to print. CUPS shipped with a few generic
-drivers (good for a few hundred different printer models). These didn't support many device-specific options.
-CUPS also shipped with its own built-in rasterization filter (<parameter>pstoraster</parameter>, derived from
-Ghostscript). On the other hand, CUPS provided brilliant support for <emphasis>controlling</emphasis> all
-printer options through standardized and well-defined PPD files. Plus, CUPS was designed to be easily
-extensible.
-</para>
-
-<para>
-Taylor already had in his database a respectable compilation of facts about many more printers and the
-Ghostscript <quote>drivers</quote> they run with. His idea, to generate PPDs from the database information and
-use them to make standard Ghostscript filters work within CUPS, proved to work very well. It also killed
-several birds with one stone:
-</para>
-
-<itemizedlist>
- <listitem><para>It made all current and future Ghostscript filter
- developments available for CUPS.</para></listitem>
-
- <listitem><para>It made available a lot of additional printer models
- to CUPS users (because often the traditional Ghostscript way of
- printing was the only one available).</para></listitem>
-
- <listitem><para>It gave all the advanced CUPS options (Web interface,
- GUI driver configurations) to users wanting (or needing) to use
- Ghostscript filters.</para></listitem>
-</itemizedlist>
-</sect3>
-
-<sect3>
-<title>cupsomatic, pdqomatic, lpdomatic, directomatic</title>
-
-<para>
-<indexterm><primary>cupsomatic</primary></indexterm>
-<indexterm><primary>CUPS-PPD</primary></indexterm>
-<indexterm><primary>PPD</primary><secondary>CUPS</secondary><see>CUPS-PPD</see></indexterm>
-CUPS worked through a quickly hacked-up filter script named <ulink
-url="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&show=0">cupsomatic</ulink>. cupsomatic
-ran the printfile through Ghostscript, constructing automatically the rather complicated command line needed.
-It just needed to be copied into the CUPS system to make it work. To configure the way cupsomatic controls the
-Ghostscript rendering process, it needs a CUPS-PPD. This PPD is generated directly from the contents of the
-database. For CUPS and the respective printer/filter combo, another Perl script named CUPS-O-Matic did the PPD
-generation. After that was working, Taylor implemented within a few days a similar thing for two other
-spoolers. Names chosen for the config-generator scripts were <ulink
-url="http://www.linuxprinting.org/download.cgi?filename=lpdomatic&show=0">PDQ-O-Matic</ulink> (for PDQ)
-and <ulink url="http://www.linuxprinting.org/download.cgi?filename=lpdomatic&show=0">LPD-O-Matic</ulink>
-(for &smbmdash; you guessed it &smbmdash; LPD); the configuration here didn't use PPDs but other
-spooler-specific files.
-</para>
-
-<para>
-From late summer of that year, <ulink url="http://www.linuxprinting.org/till/">Till Kamppeter</ulink> started
-to put work into the database. Kamppeter had been newly employed by <ulink
-url="http://www.mandrakesoft.com/">Mandrakesoft</ulink> to convert its printing system over to CUPS, after
-they had seen his <ulink url="http://www.fltk.org/">FLTK</ulink>-based <ulink
-url="http://cups.sourceforge.net/xpp/">XPP</ulink> (a GUI front-end to the CUPS lp-command). He added a huge
-amount of new information and new printers. He also developed the support for other spoolers, like <ulink
-url="http://ppr.sourceforge.net/">PPR</ulink> (via ppromatic), <ulink
-url="http://sourceforge.net/projects/lpr/">GNUlpr</ulink>, and <ulink
-url="http://www.lprng.org/">LPRng</ulink> (both via an extended lpdomatic) and spooler-less printing (<ulink
-url="http://www.linuxprinting.org/download.cgi?filename=directomatic&show=0">directomatic</ulink>).
-</para>
-
-<para>
-So, to answer your question, <quote>Foomatic</quote> is the general name for all the overlapping code and data
-behind the <quote>*omatic</quote> scripts. Foomatic, up to versions 2.0.x, required (ugly) Perl data
-structures attached to Linuxprinting.org PPDs for CUPS. It had a different <quote>*omatic</quote> script for
-every spooler, as well as different printer configuration files.
-</para>
-</sect3>
-
-<sect3>
-<title>The <emphasis>Grand Unification</emphasis> Achieved</title>
-
-<para>
-<indexterm><primary>foomatic-rip</primary></indexterm>
-This has all changed in Foomatic versions 2.9 (beta) and released as <quote>stable</quote> 3.0. It has now
-achieved the convergence of all *omatic scripts and is called the <ulink
-url="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0">foomatic-rip</ulink>.
-This single script is the unification of the previously different spooler-specific *omatic scripts.
-foomatic-rip is used by all the different spoolers alike, and because it can read PPDs (both the original
-PostScript printer PPDs and the Linuxprinting.org-generated ones), all of a sudden all supported spoolers can
-have the power of PPDs at their disposal. Users only need to plug foomatic-rip into their system. For users
-there is improved media type and source support &smbmdash; paper sizes and trays are easier to configure.
-</para>
-
-<para>
-<indexterm><primary>PPDs</primary></indexterm>
-<indexterm><primary>Foomatic tutorial</primary></indexterm>
-<indexterm><primary>LinuxKongress2002</primary></indexterm>
-Also, the new generation of Linuxprinting.org PPDs no longer contains Perl data structures. If you are a
-distro maintainer and have used the previous version of Foomatic, you may want to give the new one a spin, but
-remember to generate a new-version set of PPDs via the new <ulink
-url="http://www.linuxprinting.org/download/foomatic/foomatic-db-engine-3.0.0beta1.tar.gz">foomatic-db-engine!</ulink>.
-Individual users just need to generate a single new PPD specific to their model by <ulink
-url="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/II.Foomatic-User/II.tutorial-handout-foomatic-user.html">following
-the steps</ulink> outlined in the Foomatic tutorial or in this chapter. This new development is truly amazing.
-</para>
-
-<para>
-<indexterm><primary>foomatic-rip</primary></indexterm>
-<indexterm><primary>Adobe</primary></indexterm>
-<indexterm><primary>printer drivers</primary></indexterm>
-foomatic-rip is a very clever wrapper around the need to run Ghostscript with a different syntax, options,
-device selections, and/or filters for each different printer or spooler. At the same time, it can read the PPD
-associated with a print queue and modify the print job according to the user selections. Together with this
-comes the 100% compliance of the new Foomatic PPDs with the Adobe spec. Some innovative features of the
-Foomatic concept may surprise users. It will support custom paper sizes for many printers and will support
-printing on media drawn from different paper trays within the same job (in both cases, even where there is no
-support for this from Windows-based vendor printer drivers).
-</para>
-</sect3>
-
-<sect3>
-<title>Driver Development Outside</title>
-
-<para>
-<indexterm><primary>Linuxprinting.org</primary></indexterm>
-Most driver development itself does not happen within Linuxprinting.org. Drivers are written by independent
-maintainers. Linuxprinting.org just pools all the information and stores it in its database. In addition, it
-also provides the Foomatic glue to integrate the many drivers into any modern (or legacy) printing system
-known to the world.
-</para>
-
-<para>
-Speaking of the different driver development groups, most of the work is currently done in three projects:
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>Omni</primary></indexterm>
- <ulink url="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/">Omni</ulink>
- &smbmdash; a free software project by IBM that tries to convert its printer
- driver knowledge from good-ol' OS/2 times into a modern, modular,
- universal driver architecture for Linux/UNIX (still beta). This
- currently supports 437 models.</para></listitem>
-
- <listitem><para>
-<indexterm><primary>HPIJS</primary></indexterm>
- <ulink url="http://hpinkjet.sf.net/">HPIJS</ulink> &smbmdash;
- a free software project by HP to provide the support for its own
- range of models (very mature, printing in most cases is perfect and
- provides true photo quality). This currently supports 369
- models.</para></listitem>
-
- <listitem><para>
-<indexterm><primary>Gutenprint</primary></indexterm>
- <ulink url="http://gimp-print.sourceforge.net/">Gutenprint</ulink> &smbmdash; a free software
- effort, started by Michael Sweet (also lead developer for CUPS), now
- directed by Robert Krawitz, which has achieved an amazing level of
- photo print quality (many Epson users swear that its quality is
- better than the vendor drivers provided by Epson for the Microsoft
- platforms). This currently supports 522 models.</para></listitem>
-</itemizedlist>
-</sect3>
-
-<sect3>
-<title>Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</title>
-
-<para>
-Linuxprinting.org today is the one-stop shop to download printer drivers. Look for printer information and
-<ulink url="http://www.linuxprinting.org//kpfeifle/LinuxKongress2002/Tutorial/">tutorials</ulink> or solve
-printing problems in its popular <ulink url="http://www.linuxprinting.org/newsportal/">forums</ulink>. This
-forum is not just for GNU/Linux users, but admins of <ulink url="http://www.linuxprinting.org/macosx/">
-commercial UNIX systems</ulink> are also going there, and the relatively new
-<ulink url="http://www.linuxprinting.org/newsportal/thread.php3?name=linuxprinting.macosx.general">Mac OS X
-forum</ulink> has turned out to be one of the most frequented forums after only a few weeks.
-</para>
-
-<para>
-<indexterm><primary>Mandriva</primary></indexterm>
-<indexterm><primary>Mandrake</primary></indexterm>
-<indexterm><primary>Conectiva</primary></indexterm>
-Linuxprinting.org and the Foomatic driver wrappers around Ghostscript are now a standard tool-chain for
-printing on all the important distros. Most of them also have CUPS underneath. While in recent years most
-printer data had been added by Kamppeter, many additional contributions came from engineers with SuSE, Red
-Hat, Conectiva, Debian, and others. Vendor-neutrality is an important goal of the Foomatic project. Mandrake
-and Conectiva have merged and are now called Mandriva.
-</para>
-
-<note><para>
-Till Kamppeter from Mandrakesoft is doing an excellent job in his spare time to maintain Linuxprinting.org and
-Foomatic. So if you use it often, please send him a note showing your appreciation.
-</para></note>
-</sect3>
-
-<sect3>
-<title>Foomatic Database-Generated PPDs</title>
-
-<para>
-<indexterm><primary>Foomatic database</primary></indexterm>
-<indexterm><primary>XML-based datasets</primary></indexterm>
-<indexterm><primary>kprinter</primary></indexterm>
-<indexterm><primary>gtklp</primary></indexterm>
-<indexterm><primary>xpp</primary></indexterm>
-<indexterm><primary>HP Photosmart</primary></indexterm>
-<indexterm><primary>Epson Stylus inkjet</primary></indexterm>
-<indexterm><primary>non-PostScript printers</primary></indexterm>
-<indexterm><primary>raster</primary></indexterm>
-The Foomatic database is an amazing piece of ingenuity in itself. Not only does it keep the printer and driver
-information, but it is organized in a way that it can generate PPD files on the fly from its internal
-XML-based datasets. While these PPDs are modeled to the Adobe specification of PPDs, the
-Linuxprinting.org/Foomatic-PPDs do not normally drive PostScript printers. They are used to describe all the
-bells and whistles you could ring or blow on an Epson Stylus inkjet, or an HP Photosmart, or what-have-you.
-The main trick is one little additional line, not envisaged by the PPD specification, starting with the
-<parameter>*cupsFilter</parameter> keyword. It tells the CUPS daemon how to proceed with the PostScript print
-file (old-style Foomatic-PPDs named the cupsomatic filter script, while the new-style PPDs are now call
-foomatic-rip). This filter script calls Ghostscript on the host system (the recommended variant is ESP
-Ghostscript) to do the rendering work. foomatic-rip knows which filter or internal device setting it should
-ask from Ghostscript to convert the PostScript print job into a raster format ready for the target device.
-This usage of PPDs to describe the options of non-PostScript printers was the invention of the CUPS
-developers. The rest is easy. GUI tools (like KDE's marvelous <ulink
-url="http://printing.kde.org/overview/kprinter.phtml">kprinter</ulink> or the GNOME <ulink
-url="http://gtklp.sourceforge.net/">gtklp</ulink> xpp and the CUPS Web interface) read the PPD as well and use
-this information to present the available settings to the user as an intuitive menu selection.
-</para>
-</sect3>
-</sect2>
-
-<sect2>
-<title>foomatic-rip and Foomatic PPD Download and Installation</title>
-
-<para>
-Here are the steps to install a foomatic-rip-driven LaserJet 4 Plus-compatible
-printer in CUPS (note that recent distributions of SuSE, UnitedLinux and
-Mandrake may ship with a complete package of Foomatic-PPDs plus the
-<command>foomatic-rip</command> utility. Going directly to
-Linuxprinting.org ensures that you get the latest driver/PPD files).
-</para>
-
-<itemizedlist>
- <listitem><para>Open your browser at the Linuxprinting.org printer list <ulink url="http://www.linuxprinting.org/printer_list.cgi">page.</ulink>
- </para></listitem>
-
- <listitem><para>Check the complete list of printers in the
- <ulink url="http://www.linuxprinting.org/printer_list.cgi?make=Anyone">database.</ulink>.
- </para></listitem>
-
- <listitem><para>Select your model and click on the link.
- </para></listitem>
-
- <listitem><para>You'll arrive at a page listing all drivers working with this
- model (for all printers, there will always be <emphasis>one</emphasis>
- recommended driver. Try this one first).
- </para></listitem>
-
- <listitem><para>In our case (HP LaserJet 4 Plus), we'll arrive at the default driver for the
- <ulink url="http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus">HP-LaserJet 4 Plus.</ulink>
- </para></listitem>
-
- <listitem><para>The recommended driver is ljet4.</para></listitem>
-
- <listitem><para>Several links are provided here. You should visit them all if you
- are not familiar with the Linuxprinting.org database.
- </para></listitem>
-
- <listitem><para>There is a link to the database page for the
- <ulink url="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4">ljet4</ulink>.
- On the driver's page, you'll find important and detailed information
- about how to use that driver within the various available
- spoolers.</para></listitem>
-
- <listitem><para>Another link may lead you to the home page of the
- author of the driver.</para></listitem>
-
- <listitem><para>Important links are the ones that provide hints with
- setup instructions for <ulink noescape="1" url="http://www.linuxprinting.org/cups-doc.html">CUPS</ulink>;
- <ulink url="http://www.linuxprinting.org/pdq-doc.html">PDQ</ulink>;
- <ulink url="http://www.linuxprinting.org/lpd-doc.html">LPD, LPRng, and GNUlpr</ulink>);
- as well as <ulink url="http://www.linuxprinting.org/ppr-doc.html">PPR</ulink>
- or <quote>spoolerless</quote> <ulink url="http://www.linuxprinting.org/direct-doc.html">printing</ulink>.
- </para></listitem>
-
- <listitem><para>You can view the PPD in your browser through this link:
- <ulink noescape="1" url="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1">http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1</ulink>
- </para></listitem> <listitem><para>Most importantly, you can also generate and download
- the <ulink url="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=0">PPD</ulink>.
- </para></listitem>
-
- <listitem><para>The PPD contains all the information needed to use our
- model and the driver; once installed, this works transparently
- for the user. Later you'll only need to choose resolution, paper size,
- and so on, from the Web-based menu, or from the print dialog GUI, or from
- the command line.</para></listitem>
-
- <listitem><para>If you ended up on the drivers
- <ulink url="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4">page</ulink>,
- you can choose to use the <quote>PPD-O-Matic</quote> online PPD generator
- program.</para></listitem>
-
- <listitem><para>Select the exact model and check either <guilabel>Download</guilabel> or
- <guilabel>Display PPD file</guilabel> and click <guilabel>Generate PPD file</guilabel>.</para></listitem>
-
- <listitem><para>If you save the PPD file from the browser view, please
- do not use cut and paste (since it could possibly damage line endings
- and tabs, which makes the PPD likely to fail its duty), but use <guimenuitem>Save
- as...</guimenuitem> in your browser's menu. (It is best to use the <guilabel>Download</guilabel> option
- directly from the Web page.)</para></listitem>
-
- <listitem><para>Another interesting part on each driver page is
- the <guimenuitem>Show execution details</guimenuitem> button. If you
- select your printer model and click on that button,
- a complete Ghostscript command line will be displayed, enumerating all options
- available for that combination of driver and printer model. This is a great way to
- <quote>learn Ghostscript by doing</quote>. It is also an excellent cheat sheet
- for all experienced users who need to reconstruct a good command line
- for that darned printing script, but can't remember the exact
- syntax. </para></listitem>
-
- <listitem><para>Sometime during your visit to Linuxprinting.org, save
- the PPD to a suitable place on your hard disk, say
- <filename>/path/to/my-printer.ppd</filename> (if you prefer to install
- your printers with the help of the CUPS Web interface, save the PPD to
- the <filename>/usr/share/cups/model/</filename> path and restart
- cupsd).</para></listitem>
-
- <listitem><para>Then install the printer with a suitable command line,
- like this:
- </para>
-
- <para><screen>
- &rootprompt;<userinput>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
- -P path/to/my-printer.ppd</userinput>
- </screen></para></listitem>
-
- <listitem><para>For all the new-style <quote>Foomatic-PPDs</quote>
- from Linuxprinting.org, you also need a special CUPS filter named
- foomatic-rip.
- </para></listitem>
-
- <listitem><para>The foomatic-rip Perl script itself also makes some
- interesting <ulink url="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=1">reading</ulink>
- because it is well documented by Kamppeter's in-line comments (even
- non-Perl hackers will learn quite a bit about printing by reading
- it).</para></listitem>
-
- <listitem><para>Save foomatic-rip either directly in
- <filename>/usr/lib/cups/filter/foomatic-rip</filename> or somewhere in
- your $PATH (and remember to make it world-executable). Again,
- do not save by copy and paste but use the appropriate link or the
- <guimenuitem>Save as...</guimenuitem> menu item in your browser.</para></listitem>
-
- <listitem><para>If you save foomatic-rip in your $PATH, create a symlink:
- <screen>
- &rootprompt;<userinput>cd /usr/lib/cups/filter/ ; ln -s `which foomatic-rip'</userinput>
- </screen>
- </para>
-
- <para>
- CUPS will discover this new available filter at startup after restarting
- cupsd.</para></listitem>
-</itemizedlist>
-
-<para>
-Once you print to a print queue set up with the Foomatic PPD, CUPS will insert the appropriate commands and
-comments into the resulting PostScript job file. foomatic-rip is able to read and act upon these and uses some
-specially encoded Foomatic comments embedded in the job file. These in turn are used to construct
-(transparently for you, the user) the complicated Ghostscript command line telling the printer driver exactly
-how the resulting raster data should look and which printer commands to embed into the data stream. You need:
-</para>
-
-<itemizedlist>
- <listitem><para>A <quote>foomatic+something</quote> PPD &smbmdash; but this is not enough
- to print with CUPS (it is only <emphasis>one</emphasis> important
- component).</para></listitem>
-
- <listitem><para>The <parameter>foomatic-rip</parameter> filter script (Perl) in
- <filename>/usr/lib/cups/filters/</filename>.</para></listitem>
-
- <listitem><para>Perl to make foomatic-rip run.</para></listitem>
-
- <listitem><para>Ghostscript (because it is doing the main work,
- controlled by the PPD/foomatic-rip combo) to produce the raster data
- fit for your printer model's consumption.</para></listitem>
-
- <listitem><para>Ghostscript <emphasis>must</emphasis> (depending on
- the driver/model) contain support for a certain device representing
- the selected driver for your model (as shown by <command>gs -h</command>).</para></listitem>
-
- <listitem><para>foomatic-rip needs a new version of PPDs (PPD versions
- produced for cupsomatic do not work with foomatic-rip).</para></listitem>
-</itemizedlist>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Page Accounting with CUPS</title>
-
-
-<para>
-<indexterm><primary>CUPS</primary><secondary>Page Accounting</secondary></indexterm>
-Often there are questions regarding print quotas where Samba users (that is, Windows clients) should not be
-able to print beyond a certain number of pages or data volume per day, week, or month. This feature is
-dependent on the real print subsystem you're using. Samba's part is always to receive the job files from the
-clients (filtered <emphasis>or</emphasis> unfiltered) and hand them over to this printing subsystem.
-</para>
-
-<para>
-Of course one could hack things with one's own scripts. But then there is CUPS. CUPS supports quotas that can
-be based on the size of jobs or on the number of pages or both, and can span any time period you want.
-</para>
-
-<sect2>
-<title>Setting Up Quotas</title>
-
-<para>
-<indexterm><primary>CUPS</primary><secondary>quotas</secondary></indexterm>
-This is an example command of how root would set a print quota in CUPS, assuming an existing printer named
-<quote>quotaprinter</quote>:
-<indexterm><primary>lpadmin</primary></indexterm>
-<screen>
-&rootprompt;<userinput>lpadmin -p quotaprinter -o job-quota-period=604800 \
- -o job-k-limit=1024 -o job-page-limit=100</userinput>
-</screen></para>
-
-<para>
-This would limit every single user to print no more than 100 pages or 1024 KB of
-data (whichever comes first) within the last 604,800 seconds ( = 1 week).
-</para>
-</sect2>
-
-<sect2>
-<title>Correct and Incorrect Accounting</title>
-
-<para>
-For CUPS to count correctly, the printfile needs to pass the CUPS pstops filter; otherwise it uses a dummy
-count of <quote>one</quote>. Some print files do not pass it (e.g., image files), but then those are mostly
-one-page jobs anyway. This also means that proprietary drivers for the target printer running on the client
-computers and CUPS/Samba, which then spool these files as <quote>raw</quote> (i.e., leaving them untouched,
-not filtering them), will be counted as one-pagers too!
-</para>
-
-<para>
-You need to send PostScript from the clients (i.e., run a PostScript driver there) to have the chance to get
-accounting done. If the printer is a non-PostScript model, you need to let CUPS do the job to convert the file
-to a print-ready format for the target printer. This is currently working for about a thousand different
-printer models. Linuxprinting.org has a driver <ulink url="http://www.linuxprinting.org/printer_list.cgi">list</ulink>.
-</para>
-</sect2>
-
-<sect2>
-<title>Adobe and CUPS PostScript Drivers for Windows Clients</title>
-
-<para>
-<indexterm><primary>Adobe PostScript</primary></indexterm>
-<indexterm><primary>pstops</primary></indexterm>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>pstoraster</primary></indexterm>
-<indexterm><primary>PJL-header</primary></indexterm>
-Before CUPS 1.1.16, your only option was to use the Adobe PostScript driver on the Windows clients. The output
-of this driver was not always passed through the <command>pstops</command> filter on the CUPS/Samba side, and
-therefore was not counted correctly (the reason is that it often, depending on the PPD being used, wrote a
-PJL-header in front of the real PostScript, which caused CUPS to skip <command>pstops</command> and go
-directly to the <command>pstoraster</command> stage).
-</para>
-
-<para>
-From CUPS 1.1.16 and later releases, you can use the CUPS PostScript driver for Windows NT/200x/XP
-clients (which is tagged in the download area of <filename>http://www.cups.org/</filename> as the
-<filename>cups-samba-1.1.16.tar.gz</filename> package). It does <emphasis>not</emphasis> work for Windows
-9x/Me clients, but it guarantees:
-</para>
-
-<itemizedlist>
- <listitem><para> <indexterm><primary>PJL</primary></indexterm> To not write a PJL-header.</para></listitem>
-
- <listitem><para>To still read and support all PJL-options named in the
- driver PPD with its own means.</para></listitem>
-
- <listitem><para>That the file will pass through the <command>pstops</command> filter
- on the CUPS/Samba server.</para></listitem>
-
- <listitem><para>To page-count correctly the print file.</para></listitem>
-</itemizedlist>
-
-<para>
-You can read more about the setup of this combination in the man page for <command>cupsaddsmb</command> (which
-is only present with CUPS installed, and only current from CUPS 1.1.16).
-</para>
-</sect2>
-
-<sect2>
-<title>The page_log File Syntax</title>
-
-<para>
-<indexterm><primary>page_log</primary></indexterm>
-These are the items CUPS logs in the <filename>page_log</filename> for every page of a job:
-</para>
-
-<itemizedlist>
- <listitem><para>Printer name</para></listitem>
-
- <listitem><para>User name</para></listitem>
-
- <listitem><para>Job ID</para></listitem>
-
- <listitem><para>Time of printing</para></listitem>
-
- <listitem><para>Page number</para></listitem>
-
- <listitem><para>Number of copies</para></listitem>
-
- <listitem><para>A billing information string (optional)</para></listitem>
-
- <listitem><para>The host that sent the job (included since version 1.1.19)</para></listitem>
-</itemizedlist>
-
-<para>
-Here is an extract of my CUPS server's <filename>page_log</filename> file to illustrate the
-format and included items:
-</para>
-
-<para><screen>
-tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
-tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
-tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13
-tec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13
-Dig9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33
-</screen></para>
-
-<para>
-This was job ID <parameter>401</parameter>, printed on <parameter>tec_IS2027</parameter>
-by user <parameter>kurt</parameter>, a 64-page job printed in three copies, billed to
-<parameter>#marketing</parameter>, and sent from IP address <constant>10.160.50.13.</constant>
- The next job had ID <parameter>402</parameter>, was sent by user <parameter>boss</parameter>
-from IP address <constant>10.160.51.33</constant>, printed from one page 440 copies, and
-is set to be billed to <parameter>finance-dep</parameter>.
-</para>
-</sect2>
-
-<sect2>
-<title>Possible Shortcomings</title>
-
-<para>
-What flaws or shortcomings are there with this quota system?
-</para>
-
-<itemizedlist>
- <listitem><para>The ones named above (wrongly logged job in case of
- printer hardware failure, and so on).</para></listitem>
-
- <listitem><para>In reality, CUPS counts the job pages that are being
- processed in <emphasis>software</emphasis> (that is, going through the
- RIP) rather than the physical sheets successfully leaving the
- printing device. Thus, if there is a jam while printing the fifth sheet out
- of 1,000 and the job is aborted by the printer, the page count will
- still show the figure of 1,000 for that job.</para></listitem>
-
- <listitem><para>All quotas are the same for all users (no flexibility
- to give the boss a higher quota than the clerk) and no support for
- groups.</para></listitem>
-
- <listitem><para>No means to read out the current balance or the
- <quote>used-up</quote> number of current quota.</para></listitem>
-
- <listitem><para>A user having used up 99 sheets of a 100 quota will
- still be able to send and print a 1,000 sheet job.</para></listitem>
-
- <listitem><para>A user being denied a job because of a filled-up quota
- does not get a meaningful error message from CUPS other than
- <quote>client-error-not-possible</quote>.</para></listitem>
-</itemizedlist>
-</sect2>
-
-<sect2>
-<title>Future Developments</title>
-
-<para>
-This is the best system currently available, and there are huge
-improvements under development for CUPS 1.2:
-</para>
-
-<itemizedlist>
- <listitem><para>Page counting will go into the backends (these talk
- directly to the printer and will increase the count in sync with the
- actual printing process; thus, a jam at the fifth sheet will lead to a
- stop in the counting).</para></listitem>
-
- <listitem><para>Quotas will be handled more flexibly.</para></listitem>
-
- <listitem><para>Probably there will be support for users to inquire
- about their accounts in advance.</para></listitem>
-
- <listitem><para>Probably there will be support for some other tools
- around this topic.</para></listitem>
-</itemizedlist>
-</sect2>
-
-<sect2>
-<title>Other Accounting Tools</title>
-
-<para>
-Other accounting tools that can be used includes: PrintAnalyzer, pyKota, printbill, LogReport.
-For more information regarding these tools you can try a Google search.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Additional Material</title>
-
-<para>
-A printer queue with <emphasis>no</emphasis> PPD associated to it is a
-<quote>raw</quote> printer, and all files will go directly there as received by the
-spooler. The exceptions are file types <parameter>application/octet-stream</parameter>
-that need the pass-through feature enabled. <quote>Raw</quote> queues do not do any
-filtering at all; they hand the file directly to the CUPS backend.
-This backend is responsible for sending the data to the device
-(as in the <quote>device URI</quote> notation: <filename>lpd://, socket://,
-smb://, ipp://, http://, parallel:/, serial:/, usb:/</filename>, and so on).
-</para>
-
-<para>
-cupsomatic/Foomatic are <emphasis>not</emphasis> native CUPS drivers
-and they do not ship with CUPS. They are a third-party add-on
-developed at Linuxprinting.org. As such, they are a brilliant hack to
-make all models (driven by Ghostscript drivers/filters in traditional
-spoolers) also work via CUPS, with the same (good or bad!) quality as
-in these other spoolers. <parameter>cupsomatic</parameter> is only a vehicle to execute a
-Ghostscript command line at that stage in the CUPS filtering chain
-where normally the native CUPS <parameter>pstoraster</parameter> filter would kick
-in. <parameter>cupsomatic</parameter> bypasses <parameter>pstoraster</parameter>, kidnaps the print file from CUPS,
-and redirects it to go through Ghostscript. CUPS accepts this
-because the associated cupsomatic/foomatic-PPD specifies:
-
-<programlisting>
-*cupsFilter: "application/vnd.cups-postscript 0 cupsomatic"
-</programlisting>
-
-This line persuades CUPS to hand the file to <parameter>cupsomatic</parameter> once it has
-successfully converted it to the MIME type
-<parameter>application/vnd.cups-postscript</parameter>. This conversion will not happen for
-jobs arriving from Windows that are autotyped
-<parameter>application/octet-stream</parameter>, with the according changes in
-<filename>/etc/cups/mime.types</filename> in place.
-</para>
-
-<para>
-CUPS is widely configurable and flexible, even regarding its filtering
-mechanism. Another workaround in some situations would be to have in
-<filename>/etc/cups/mime.types</filename> entries as follows:
-
-<programlisting>
-application/postscript application/vnd.cups-raw 0 -
-application/vnd.cups-postscript application/vnd.cups-raw 0 -
-</programlisting>
-
-This would prevent all PostScript files from being filtered (rather,
-they will through the virtual <emphasis>nullfilter</emphasis>
-denoted with <quote>-</quote>). This could only be useful for PostScript printers. If you
-want to print PostScript code on non-PostScript printers (provided they support ASCII
-text printing), an entry as follows could be useful:
-
-<programlisting>
-*/* application/vnd.cups-raw 0 -
-</programlisting>
-
-and would effectively send <emphasis>all</emphasis> files to the
-backend without further processing.
-</para>
-
-<para>
-You could have the following entry:
-
-<programlisting>
-application/vnd.cups-postscript application/vnd.cups-raw 0 \
- my_PJL_stripping_filter
-</programlisting>
-
-You will need to write a <parameter>my_PJL_stripping_filter</parameter>
-(which could be a shell script) that parses the PostScript and removes the
-unwanted PJL. This needs to conform to CUPS filter design
-(mainly, receive and pass the parameters printername, job-id,
-username, jobtitle, copies, print options, and possibly the
-filename). It is installed as world executable into
-<filename>/usr/lib/cups/filters/</filename> and is called by CUPS
-if it encounters a MIME type <parameter>application/vnd.cups-postscript</parameter>.
-</para>
-
-<para>
-CUPS can handle <parameter>-o job-hold-until=indefinite</parameter>.
-This keeps the job in the queue on hold. It will only be printed
-upon manual release by the printer operator. This is a requirement in
-many central reproduction departments, where a few operators manage
-the jobs of hundreds of users on some big machine, where no user is
-allowed to have direct access (such as when the operators often need
-to load the proper paper type before running the 10,000 page job
-requested by marketing for the mailing, and so on).
-</para>
-</sect1>
-
-<sect1>
-<title>Autodeletion or Preservation of CUPS Spool Files</title>
-
-<para>
-<indexterm><primary>/var/spool/samba</primary></indexterm>
-<indexterm><primary>/var/spool/cups/</primary></indexterm>
-<indexterm><primary>cupsd.conf</primary></indexterm>
-Samba print files pass through two spool directories. One is the incoming directory managed by Samba (set in
-the <smbconfoption name="path">/var/spool/samba</smbconfoption> directive in the <smbconfsection
-name="[printers]"/> section of &smb.conf;). The other is the spool directory of your UNIX print subsystem. For
-CUPS it is normally <filename>/var/spool/cups/</filename>, as set by the <filename>cupsd.conf</filename>
-directive <filename>RequestRoot /var/spool/cups</filename>.
-</para>
-
-<sect2>
-<title>CUPS Configuration Settings Explained</title>
-
-<para>
-Some important parameter settings in the CUPS configuration file
-<filename>cupsd.conf</filename> are:
-</para>
-
-<variablelist>
-
- <varlistentry><term>PreserveJobHistory Yes</term>
- <listitem><para>
- This keeps some details of jobs in cupsd's mind (well, it keeps the
- c12345, c12346, and so on, files in the CUPS spool directory, which does a
- similar job as the old-fashioned BSD-LPD control files). This is set
- to <quote>Yes</quote> as a default.
- </para></listitem></varlistentry>
-
- <varlistentry><term>PreserveJobFiles Yes</term>
- <listitem><para>
- This keeps the job files themselves in cupsd's mind
- (it keeps the d12345, d12346, etc., files in the CUPS spool
- directory). This is set to <quote>No</quote> as the CUPS
- default.
- </para></listitem></varlistentry>
-
- <varlistentry><term><quote>MaxJobs 500</quote></term>
- <listitem><para>
- This directive controls the maximum number of jobs
- that are kept in memory. Once the number of jobs reaches the limit,
- the oldest completed job is automatically purged from the system to
- make room for the new one. If all of the known jobs are still
- pending or active, then the new job will be rejected. Setting the
- maximum to 0 disables this functionality. The default setting is
- 0.
- </para></listitem></varlistentry>
-</variablelist>
-
-<para>
-(There are also additional settings for <parameter>MaxJobsPerUser</parameter> and
-<parameter>MaxJobsPerPrinter</parameter>.)
-</para>
-</sect2>
-
-<sect2>
-<title>Preconditions</title>
-
-<para>
-For everything to work as it should, you need to have three things:
-</para>
-
-<itemizedlist>
- <listitem><para>A Samba smbd that is compiled against <filename>libcups</filename> (check
- on Linux by running <userinput>ldd `which smbd'</userinput>).</para></listitem>
-
- <listitem><para>A Samba-&smb.conf; setting of
- <smbconfoption name="printing">cups</smbconfoption>.</para></listitem>
-
-</itemizedlist>
-
-<note><para>
-In this case, all other manually set printing-related commands (like
-<smbconfoption name="print command"/>,
-<smbconfoption name="lpq command"/>,
-<smbconfoption name="lprm command"/>,
-<smbconfoption name="lppause command"/>, and
-<smbconfoption name="lpresume command"/>) are ignored, and they should normally have no
-influence whatsoever on your printing.
-</para></note>
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Printing from CUPS to Windows-Attached Printers</title>
-
-<para>
-<indexterm><primary>smbspool</primary></indexterm>
-<indexterm><primary>backends</primary></indexterm>
-From time to time the question arises, how can you print <emphasis>to</emphasis> a Windows-attached printer
-<emphasis>from</emphasis> Samba? Normally the local connection from Windows host to printer would be done by
-USB or parallel cable, but this does not matter to Samba. From here only an SMB connection needs to be opened
-to the Windows host. Of course, this printer must be shared first. As you have learned by now, CUPS uses
-<emphasis>backends</emphasis> to talk to printers and other servers. To talk to Windows shared printers, you
-need to use the <filename>smb</filename> (surprise, surprise!) backend. Check if this is in the CUPS backend
-directory. This usually resides in <filename>/usr/lib/cups/backend/</filename>. You need to find an
-<filename>smb</filename> file there. It should be a symlink to <filename>smbspool</filename>, and the file
-must exist and be executable:
-<screen>
-&rootprompt;<userinput>ls -l /usr/lib/cups/backend/</userinput>
-total 253
-drwxr-xr-x 3 root root 720 Apr 30 19:04 .
-drwxr-xr-x 6 root root 125 Dec 19 17:13 ..
--rwxr-xr-x 1 root root 10692 Feb 16 21:29 canon
--rwxr-xr-x 1 root root 10692 Feb 16 21:29 epson
-lrwxrwxrwx 1 root root 3 Apr 17 22:50 http -> ipp
--rwxr-xr-x 1 root root 17316 Apr 17 22:50 ipp
--rwxr-xr-x 1 root root 15420 Apr 20 17:01 lpd
--rwxr-xr-x 1 root root 8656 Apr 20 17:01 parallel
--rwxr-xr-x 1 root root 2162 Mar 31 23:15 pdfdistiller
-lrwxrwxrwx 1 root root 25 Apr 30 19:04 ptal -> /usr/sbin/ptal-cups
--rwxr-xr-x 1 root root 6284 Apr 20 17:01 scsi
-lrwxrwxrwx 1 root root 17 Apr 2 03:11 smb -> /usr/bin/smbspool
--rwxr-xr-x 1 root root 7912 Apr 20 17:01 socket
--rwxr-xr-x 1 root root 9012 Apr 20 17:01 usb
-
-&rootprompt;<userinput>ls -l `which smbspool`</userinput>
--rwxr-xr-x 1 root root 563245 Dec 28 14:49 /usr/bin/smbspool
-</screen></para>
-
-<para>
-If this symlink does not exist, create it:
-<screen>
-&rootprompt;<userinput>ln -s `which smbspool` /usr/lib/cups/backend/smb</userinput>
-</screen></para>
-
-<para>
-<indexterm><primary>smbspool</primary></indexterm>
-<indexterm><primary>troubleshooting</primary></indexterm>
-<command>smbspool</command> was written by Mike Sweet from the CUPS folks. It is included and ships with
-Samba. It may also be used with print subsystems other than CUPS, to spool jobs to Windows printer shares. To
-set up printer <replaceable>winprinter</replaceable> on CUPS, you need to have a driver for it. Essentially
-this means to convert the print data on the CUPS/Samba host to a format that the printer can digest (the
-Windows host is unable to convert any files you may send). This also means you should be able to print to the
-printer if it were hooked directly at your Samba/CUPS host. For troubleshooting purposes, this is what you
-should do to determine if that part of the process chain is in order. Then proceed to fix the network
-connection/authentication to the Windows host, and so on.
-</para>
-
-<para>
-To install a printer with the <parameter>smb</parameter> backend on CUPS, use this command:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename \
- -P /path/to/PPD</userinput>
-</screen></para>
-
-<para>
-<indexterm><primary>PostScript printers</primary></indexterm>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>Windows NT PostScript driver</primary></indexterm>
-The PPD must be able to direct CUPS to generate the print data for the target model. For PostScript printers,
-just use the PPD that would be used with the Windows NT PostScript driver. But what can you do if the printer
-is only accessible with a password? Or if the printer's host is part of another workgroup? This is provided
-for: You can include the required parameters as part of the <filename>smb://</filename> device-URI like this:
-</para>
-
-<itemizedlist>
- <listitem><para><filename>smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename</filename></para></listitem>
- <listitem><para><filename>smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename</filename></para></listitem>
- <listitem><para><filename>smb://username:password@WINDOWSNETBIOSNAME/printersharename</filename></para></listitem>
-</itemizedlist>
-
-<para>
-Note that the device URI will be visible in the process list of the Samba server (e.g., when someone uses the
-<command>ps -aux</command> command on Linux), even if the username and passwords are sanitized before they get
-written into the log files. This is an inherently insecure option; however, it is the only one. Don't use it
-if you want to protect your passwords. Better share the printer in a way that does not require a password!
-Printing will only work if you have a working NetBIOS name resolution up and running. Note that this is a
-feature of CUPS and you do not necessarily need to have smbd running.
-
-</para>
-</sect1>
-
-<sect1>
-<title>More CUPS Filtering Chains</title>
-
-<para>
-The diagrams in <link linkend="cups1">Filtering Chain 1</link> and <link linkend="cups2">Filtering Chain with
-cupsomatic</link> show how CUPS handles print jobs.
-</para>
-
-<figure id="cups1">
- <title>Filtering Chain 1.</title>
- <imagefile>cups1</imagefile>
-</figure>
-
-<!-- JJJ -->
-<figure id="cups2">
- <title>Filtering Chain with cupsomatic</title>
- <imagefile scale="45">cups2</imagefile>
-</figure>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
- <sect2>
- <title>Windows 9x/Me Client Can't Install Driver</title>
-
- <para>For Windows 9x/Me, clients require the printer names to be eight
- characters (or <quote>8 plus 3 chars suffix</quote>) max; otherwise, the driver files
- will not get transferred when you want to download them from Samba.</para>
-
- </sect2>
-
- <sect2 id="root-ask-loop">
- <title><quote>cupsaddsmb</quote> Keeps Asking for Root Password in Never-ending Loop</title>
-
- <para>Have you set <smbconfoption name="security">user</smbconfoption>? Have
- you used <command>smbpasswd</command> to give root a Samba account?
- You can do two things: open another terminal and execute
- <command>smbpasswd -a root</command> to create the account and
- continue entering the password into the first terminal. Or, break
- out of the loop by pressing Enter twice (without trying to type a
- password).</para>
-
- <para>
- If the error is <quote>Tree connect failed: NT_STATUS_BAD_NETWORK_NAME</quote>,
- you may have forgotten to create the <filename>/etc/samba/drivers</filename> directory.
- </para>
- </sect2>
-
- <sect2>
- <title><quote>cupsaddsmb</quote> or <quote>rpcclient addriver</quote> Emit Error</title>
-
- <para>
- If <command>cupsaddsmb</command>, or <command>rpcclient addriver</command> emit the error message
- WERR_BAD_PASSWORD/WERR_INVALID_PASSWORD, refer to <link linkend="root-ask-loop">the previous common error</link>.
- </para>
-
- </sect2>
-
- <sect2>
- <title><quote>cupsaddsmb</quote> Errors</title>
-
- <para>
- The use of <quote>cupsaddsmb</quote> gives <quote>No PPD file for printer...</quote>
- message while PPD file is present. What might the problem be?
- </para>
-
- <para>
- Have you enabled printer sharing on CUPS? This means, do you have a <literal><Location
- /printers>....</Location></literal> section in CUPS server's <filename>cupsd.conf</filename> that
- does not deny access to the host you run <quote>cupsaddsmb</quote> from? It <emphasis>could</emphasis> be an
- issue if you use cupsaddsmb remotely, or if you use it with a <option>-h</option> parameter:
- <userinput>cupsaddsmb -H sambaserver -h cupsserver -v printername</userinput>.
- </para>
-
- <para>Is your <parameter>TempDir</parameter> directive in
- <filename>cupsd.conf</filename> set to a valid value, and is it writable?
- </para>
-
- </sect2>
-
- <sect2>
- <title>Client Can't Connect to Samba Printer</title>
-
- <para>Use <command>smbstatus</command> to check which user
- you are from Samba's point of view. Do you have the privileges to
- write into the <smbconfsection name="[print$]"/>
- share?</para>
-
- </sect2>
-
- <sect2>
- <title>New Account Reconnection from Windows 200x/XP Troubles</title>
-
-<para>
-Once you are connected as the wrong user (for example, as <constant>nobody</constant>, which often occurs if
-you have <smbconfoption name="map to guest">bad user</smbconfoption>), Windows Explorer will not accept an
-attempt to connect again as a different user. There will not be any bytes transferred on the wire to Samba,
-but still you'll see a stupid error message that makes you think Samba has denied access. Use
-<command>smbstatus</command> to check for active connections. Kill the PIDs. You still can't re-connect, and
-you get the dreaded <computeroutput>You can't connect with a second account from the same
-machine</computeroutput> message as soon as you try. And you do not see a single byte arriving at Samba (see
-logs; use <quote>ethereal</quote>) indicating a renewed connection attempt. Shut all Explorer Windows. This
-makes Windows forget what it has cached in its memory as established connections. Then reconnect as the right
-user. The best method is to use a DOS terminal window and <emphasis>first</emphasis> do <userinput>net use z:
-\\&example.server.samba;\print$ /user:root</userinput>. Check with <command>smbstatus</command> that you are
-connected under a different account. Now open the <guilabel>Printers</guilabel> folder (on the Samba server in
-the <guilabel>Network Neighborhood</guilabel>), right-click on the printer in question, and select
-<guibutton>Connect....</guibutton>.
-</para>
-</sect2>
-
-<sect2>
-<title>Avoid Being Connected to the Samba Server as the Wrong User</title>
-
-<para>
-<indexterm><primary>smbstatus</primary></indexterm>
-You see per <command>smbstatus</command> that you are connected as user nobody, but you want to be root or
-printer admin. This is probably due to <smbconfoption name="map to guest">bad user</smbconfoption>, which
-silently connected you under the guest account when you gave (maybe by accident) an incorrect username. Remove
-<smbconfoption name="map to guest"/> if you want to prevent this.
-</para>
-</sect2>
-
-<sect2>
-<title>Upgrading to CUPS Drivers from Adobe Drivers</title>
-
-<para>
-This information came from a mailing list posting regarding problems experienced when
-upgrading from Adobe drivers to CUPS drivers on Microsoft Windows NT/200x/XP clients.
-</para>
-
-<para>First delete all old Adobe-using printers. Then delete all old Adobe drivers. (On Windows 200x/XP, right-click in
-the background of <guilabel>Printers</guilabel> folder, select <guimenuitem>Server Properties...</guimenuitem>, select
-tab <guilabel>Drivers</guilabel>, and delete here).</para>
-</sect2>
-
-<sect2>
-<title>Can't Use <quote>cupsaddsmb</quote> on Samba Server, Which Is a PDC</title>
-
-<para>Do you use the <quote>naked</quote> root user name? Try to do it
-this way: <userinput>cupsaddsmb -U <replaceable>DOMAINNAME</replaceable>\\root -v
-<replaceable>printername</replaceable></userinput>> (note the two backslashes: the first one is
-required to <quote>escape</quote> the second one).</para>
-
-</sect2>
-
-<sect2>
-<title>Deleted Windows 200x Printer Driver Is Still Shown</title>
-
-<para>Deleting a printer on the client will not delete the
-driver too (to verify, right-click on the white background of the
-<guilabel>Printers</guilabel> folder, select <guimenuitem>Server Properties</guimenuitem> and click on the
-<guilabel>Drivers</guilabel> tab). These same old drivers will be re-used when you try to
-install a printer with the same name. If you want to update to a new
-driver, delete the old ones first. Deletion is only possible if no
-other printer uses the same driver.</para>
-</sect2>
-
-<sect2>
-<title>Windows 200x/XP Local Security Policies</title>
-
-<indexterm><primary>Local security policies</primary></indexterm>
-<indexterm><primary>unsigned drivers</primary></indexterm>
-<para>Local security policies may not allow the installation of unsigned drivers &smbmdash; <quote>local
-security policies</quote> may not allow the installation of printer drivers at all.</para>
-
-</sect2>
-
-<sect2>
-<title>Administrator Cannot Install Printers for All Local Users</title>
-
-<para>
-<indexterm><primary>SMB printers</primary></indexterm>
-<indexterm><primary>IPP client</primary></indexterm>
-Windows XP handles SMB printers on a <quote>per-user</quote> basis.
-This means every user needs to install the printer himself or herself. To have a printer available for
-everybody, you might want to use the built-in IPP client capabilities of Win XP. Add a printer with the print
-path of <parameter>http://cupsserver:631/printers/printername</parameter>. We're still looking into this one.
-Maybe a logon script could automatically install printers for all users.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Print Change, Notify Functions on NT Clients</title>
-
-<para>For print change, notify functions on NT++ clients. These need to run the <command>Server</command>
-service first (renamed to <command>File & Print Sharing for MS Networks</command> in XP).</para>
-
-</sect2>
-
-<sect2>
-<title>Windows XP SP1</title>
-
-<para>Windows XP SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to
-<quote>Administrator</quote> or <quote>Power User</quote> groups of users). In Group Policy Object Editor, go
-to <guimenu>User Configuration -> Administrative Templates -> Control Panel -> Printers</guimenu>. The policy
-is automatically set to <constant>Enabled</constant> and the <constant>Users can only Point and Print to
-machines in their Forest</constant> . You probably need to change it to <constant>Disabled</constant> or
-<constant>Users can only Point and Print to these servers</constant> to make driver downloads from Samba
-possible.
-</para>
-</sect2>
-
-<sect2>
-<title>Print Options for All Users Can't Be Set on Windows 200x/XP</title>
-
-<para>How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three
-different ways to bring you to a dialog that <emphasis>seems</emphasis> to set everything. All three dialogs
-<emphasis>look</emphasis> the same, yet only one of them does what you intend. You need to be Administrator or
-Print Administrator to do this for all users. Here is how I do it on XP:
-</para>
-
-<orderedlist numeration="upperalpha">
-
- <listitem><para>The first wrong way:
-
- <orderedlist>
- <listitem><para>Open the <guilabel>Printers</guilabel>
- folder.</para></listitem>
-
- <listitem><para>Right-click on the printer
- (<guilabel>remoteprinter on cupshost</guilabel>) and
- select in context menu <guimenuitem>Printing
- Preferences...</guimenuitem></para></listitem>.
-
- <listitem><para>Look at this dialog closely and remember what it looks like.</para></listitem>
- </orderedlist>
- </para></listitem>
-
- <listitem><para>The second wrong way:
- <orderedlist>
- <listitem><para>Open the <guilabel>Printers</guilabel> folder.</para></listitem>
-
- <listitem><para>Right-click on the printer (<guilabel>remoteprinter on
- cupshost</guilabel>) and select the context menu
- <guimenuitem>Properties</guimenuitem>.</para></listitem>
-
- <listitem><para>Click on the <guilabel>General</guilabel> tab.</para></listitem>
-
- <listitem><para>Click on the button <guibutton>Printing
- Preferences...</guibutton></para></listitem>.
-
- <listitem><para>A new dialog opens. Keep this dialog open and go back
- to the parent dialog.</para></listitem>
- </orderedlist>
- </para></listitem>
-
- <listitem><para>The third and correct way:
- <orderedlist>
- <listitem><para>Open the <guilabel>Printers</guilabel> folder.</para></listitem>
-
- <listitem><para>Right-click on the printer (<guilabel>remoteprinter on
- cupshost</guilabel>) and select the context menu
- <guimenuitem>Properties</guimenuitem>.</para></listitem>
-
- <listitem><para>Click on the <guilabel>Advanced</guilabel>
- tab. (If everything is <quote>grayed out,</quote> then you are not logged
- in as a user with enough privileges).</para></listitem>
-
- <listitem><para>Click on the <guibutton>Printing
- Defaults...</guibutton> button.</para></listitem>
-
- <listitem><para>On any of the two new tabs, click on the
- <guibutton>Advanced...</guibutton> button.</para></listitem>
-
- <listitem><para>A new dialog opens. Compare this one to the other
- identical-looking one from step <quote>B.5</quote> or A.3".</para></listitem>
- </orderedlist>
- </para></listitem>
-</orderedlist>
-
-<para>
-Do you see any difference? I don't either. However, only the last one, which you arrived at with steps
-<quote>C.1. to C.6.</quote>, will save any settings permanently and be the defaults for new users. If you want
-all clients to get the same defaults, you need to conduct these steps <emphasis>as Administrator</emphasis>
-(<smbconfoption name="printer admin"/> in &smb.conf;) <emphasis>before</emphasis> a client downloads the
-driver (the clients can later set their own <emphasis>per-user defaults</emphasis> by following the procedures
-<emphasis>A</emphasis> or <emphasis>B</emphasis>).
-</para>
-
-</sect2>
-
-<sect2>
-<title>Most Common Blunders in Driver Settings on Windows Clients</title>
-
-<para>
-Don't use <parameter>Optimize for Speed</parameter>, but use <parameter>Optimize for Portability</parameter>
-instead (Adobe PS Driver). Don't use <parameter>Page Independence: No</parameter>. Always settle with
-<parameter>Page Independence: Yes</parameter> (Microsoft PS Driver and CUPS PS Driver for Windows NT/200x/XP).
-If there are problems with fonts, use <parameter>Download as Softfont into printer</parameter> (Adobe PS
-Driver). For <guilabel>TrueType Download Options</guilabel> choose <constant>Outline</constant>. Use
-PostScript Level 2 if you are having trouble with a non-PS printer and if there is a choice.
-</para>
-
-</sect2>
-
-<sect2>
-<title><command>cupsaddsmb</command> Does Not Work with Newly Installed Printer</title>
-
-<para>
-Symptom: The last command of <command>cupsaddsmb</command> does not complete successfully. If the <command>cmd
-= setdriver printername printername</command> result was NT_STATUS_UNSUCCESSFUL, then possibly the printer was
-not yet recognized by Samba. Did it show up in Network Neighborhood? Did it show up in <command>rpcclient
-hostname -c `enumprinters'</command>? Restart smbd (or send a <command>kill -HUP</command> to all processes
-listed by <command>smbstatus</command>, and try again.
-</para></sect2>
-
-<sect2>
-<title>Permissions on <filename>/var/spool/samba/</filename> Get Reset After Each Reboot</title>
-
-<para>
-Have you ever by accident set the CUPS spool directory to the same location (<parameter>RequestRoot
-/var/spool/samba/</parameter> in <filename>cupsd.conf</filename> or the other way round:
-<filename>/var/spool/cups/</filename> is set as <smbconfoption name="path"/>> in the <smbconfsection
-name="[printers]"/> section)? These <parameter>must</parameter> be different. Set <parameter>RequestRoot
-/var/spool/cups/</parameter> in <filename>cupsd.conf</filename> and <smbconfoption name="path">
-/var/spool/samba</smbconfoption> in the <smbconfsection name="[printers]"/> section of &smb.conf;. Otherwise,
-cupsd will sanitize permissions to its spool directory with each restart and printing will not work reliably.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Print Queue Called <quote>lp</quote> Mishandles Print Jobs</title>
-
-<para>
-In this case a print queue called <quote>lp</quote> intermittently swallows jobs and
-spits out completely different ones from what was sent.
-</para>
-
-<para>
-<indexterm><primary>lp</primary></indexterm>
-<indexterm><primary>Implicit Classes</primary></indexterm>
-<indexterm><primary>BrowseShortNames</primary></indexterm>
-It is a bad idea to name any printer <quote>lp</quote>. This is the traditional UNIX name for the default
-printer. CUPS may be set up to do an automatic creation of Implicit Classes. This means, to group all printers
-with the same name to a pool of devices and load-balance the jobs across them in a round-robin fashion.
-Chances are high that someone else has a printer named <quote>lp</quote> too. You may receive that person's
-jobs and send your own to his or her device unwittingly. To have tight control over the printer names, set
-<parameter>BrowseShortNames No</parameter>. It will present any printer as
-<replaceable>printername@cupshost</replaceable>, which gives you better control over what may happen in a
-large networked environment.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Location of Adobe PostScript Driver Files for <quote>cupsaddsmb</quote></title>
-
-<para>
-Use <command>smbclient</command> to connect to any Windows box with a shared PostScript printer:
-<command>smbclient //windowsbox/print\$ -U guest</command>. You can navigate to the
-<filename>W32X86/2</filename> subdir to <command>mget ADOBE*</command> and other files or to
-<filename>WIN40/0</filename> to do the same. Another option is to download the <filename>*.exe</filename>
-packaged files from the Adobe Web site.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Overview of the CUPS Printing Processes</title>
-
-<para>
-A complete overview of the CUPS printing processes can be found in <link linkend="a_small">the CUPS
-Printing Overview diagram</link>.
-</para>
-
-<figure id="a_small">
- <title>CUPS Printing Overview.</title>
- <imagefile scale="45">a_small</imagefile>
-</figure>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="ChangeNotes">
-<chapterinfo>
- &author.jht;
- &author.jerry;
-</chapterinfo>
-
-<title>Important and Critical Change Notes for the Samba 3.x Series</title>
-<para>
-Please read this chapter carefully before update or upgrading Samba. You should expect to find only critical
-or very important information here. Comprehensive change notes and guidance information can be found in the
-section <link linkend="upgrading-to-3.0">Updating and Upgrading Samba</link>.
-</para>
-
-<sect1>
-
-<title>Important Samba-3.2.x Change Notes</title>
-<para>
-!!!!!!!!!!!!Add all critical update notes here!!!!!!!!!!!!!
-</para>
-
-</sect1>
-
-<sect1>
-
-<title>Important Samba-3.0.x Change Notes</title>
-<para>
-These following notes pertain in particular to Samba 3.0.23 through Samba 3.0.25c (or more recent 3.0.25
-update). Samba is a fluid and ever changing project. Changes throughout the 3.0.x series release are
-documented in this documention - See <link linkend="oldupdatenotes">Upgrading from Samba-2.x to Samba-3.0.25</link>.
-</para>
-
-<para>
-Sometimes it is difficult to figure out which part, or parts, of the HOWTO documentation should be updated to
-reflect the impact of new or modified features. At other times it becomes clear that the documentation is in
-need of being restructured.
-</para>
-
-<para>
-In recent times a group of Samba users has joined the thrust to create a new <ulink
-url="http://wiki.samba.org/">Samba Wiki</ulink> that is slated to become the all-singing and all-dancing
-new face of Samba documentation. Hopefully, the Wiki will benefit from greater community input and
-thus may be kept more up to date. Until that golden dream materializes and matures it is necessary to
-continue to maintain the HOWTO. This chapter will document major departures from earlier behavior until
-such time as the body of this HOWTO is restructured or modified.
-</para>
-
-<para>
-This chapter is new to the release of the HOWTO for Samba 3.0.23. It includes much of the notes provided
-in the <filename>WHATSNEW.txt</filename> file that is included with the Samba source code release tarball.
-</para>
-
-<sect2>
-<title>User and Group Changes</title>
-
-<para>
-The change documented here affects unmapped user and group accounts only.
-</para>
-
-<para>
-<indexterm><primary>user</primary></indexterm>
-<indexterm><primary>group</primary></indexterm>
-<indexterm><primary>Relative Identifiers</primary><see>RID</see></indexterm>
-<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
-The user and group internal management routines have been rewritten to prevent overlaps of
-assigned Relative Identifiers (RIDs). In the past the has been a potential problem when
-either manually mapping Unix groups with the <command>net groupmap</command> command or
-when migrating a Windows domain to a Samba domain by executing:
-<command>net rpc vampire</command>.
-</para>
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
-<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
-Unmapped users are now assigned a SID in the <literal>S-1-22-1</literal> domain and unmapped
-groups are assigned a SID in the <literal>S-1-22-2</literal> domain. Previously they were
-assigned a RID within the SAM on the Samba server. For a domain controller this would have been under the
-authority of the domain SID where as on a member server or standalone server, this would have
-been under the authority of the local SAM (see the man page for <command>net getlocalsid</command>).
-</para>
-
-<para>
-<indexterm><primary>unmapped users</primary></indexterm>
-<indexterm><primary>unmapped groups</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>NTFS</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-The result is that any unmapped users or groups on an upgraded Samba domain controller may
-be assigned a new SID. Because the SID rather than a name is stored in Windows security
-descriptors, this can cause a user to no longer have access to a resource for example if a
-file was copied from a Samba file server to a local Windows client NTFS partition. Any files
-stored on the Samba server itself will continue to be accessible because UNIX stores the UNIX
-GID and not the SID for authorization checks.
-</para>
-
-<para>
-An example helps to illustrate the change:
-</para>
-
-<para>
-<indexterm><primary>group mapping</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>ACL</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-Assume that a group named <emphasis>developers</emphasis> exists with a UNIX GID of 782. In this
-case this group does not exist in Samba's group mapping table. It would be perfectly normal for
-this group to be appear in an ACL editor. Prior to Samba-3.0.23, the group SID might appear as
-<literal>S-1-5-21-647511796-4126122067-3123570092-2565</literal>.
-</para>
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>NTFS</primary></indexterm>
-<indexterm><primary>access</primary></indexterm>
-<indexterm><primary>group permissions</primary></indexterm>
-With the release of Samba-3.0.23, the group SID would be reported as <literal>S-1-22-2-782</literal>. Any
-security descriptors associated with files stored on a Windows NTFS disk partition will not allow access based
-on the group permissions if the user was not a member of the
-<literal>S-1-5-21-647511796-4126122067-3123570092-2565</literal> group. Because this group SID is
-<literal>S-1-22-2-782</literal> and not reported in a user's token, Windows would fail the authorization check
-even though both SIDs in some respect refer to the same UNIX group.
-</para>
-
-<para>
-<indexterm><primary>group mapping</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-The workaround for versions of Samba prior to 3.0.23, is to create a manual domain group mapping
-entry for the group <emphasis>developers</emphasis> to point at the
-<literal>S-1-5-21-647511796-4126122067-3123570092-2565</literal> SID. With the release of Samba-3.0.23 this
-workaround is no longer needed.
-</para>
-</sect2>
-
-<sect2>
-<title>Essential Group Mappings</title>
-<para>
-Samba 3.0.x series releases before 3.0.23 automatically created group mappings for the essential Windows
-domain groups <literal>Domain Admins, Domain Users, Domain Guests</literal>. Commencing with Samba 3.0.23
-these mappings need to be created by the Samba administrator. Failure to do this may result in a failure to
-correctly authenticate and recoognize valid domain users. When this happens users will not be able to log onto
-the Windows client.
-</para>
-
-<note><para>
-Group mappings are essentail only if the Samba servers is running as a PDC/BDC. Stand-alone servers do not
-require these group mappings.
-</para></note>
-
-<para>
-The following mappings are required:
-</para>
-
-<table frame="all" id="TOSH-domgroups">
- <title>Essential Domain Group Mappings</title>
- <tgroup align="center" cols="3">
- <thead>
- <row><entry>Domain Group</entry><entry>RID</entry><entry>Example UNIX Group</entry></row>
- </thead>
- <tbody>
- <row><entry>Domain Admins</entry><entry>512</entry><entry>root</entry></row>
- <row><entry>Domain Users</entry><entry>513</entry><entry>users</entry></row>
- <row><entry>Domain Guests</entry><entry>514</entry><entry>nobody</entry></row>
- </tbody>
- </tgroup>
-</table>
-
-<para>
-When the POSIX (UNIX) groups are stored in LDAP, it may be desirable to call these <literal>domadmins, domusers,
-domguests</literal> respectively.
-</para>
-
-<para>
-For further information regarding group mappings see <link linkend="groupmapping">Group Mapping: MS Windows
-and UNIX</link>.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Passdb Changes</title>
-
-<para>
-<indexterm><primary>backends</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>SQL</primary></indexterm>
-<indexterm><primary>XML</primary></indexterm>
-The <smbconfoption name="passdb backend"/> parameter no longer accepts multiple passdb backends in a
-chained configuration. Also be aware that the SQL and XML based passdb modules have been
-removed in the Samba-3.0.23 release. More information regarding external support for a SQL
-passdb module can be found on the <ulink url="http://pdbsql.sourceforge.net/">pdbsql</ulink> web site.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Group Mapping Changes in Samba-3.0.23</title>
-
-<para>
-<indexterm><primary>default mapping</primary></indexterm>
-<indexterm><primary>Domain Admins</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>group mappings</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>IDMAP</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>domain groups</primary></indexterm>
-The default mapping entries for groups such as <literal>Domain Admins</literal> are no longer
-created when using an <literal>smbpasswd</literal> file or a <literal>tdbsam</literal> passdb
-backend. This means that it is necessary to explicitly execute the <command>net groupmap add</command>
-to create group mappings, rather than use the <command>net groupmap modify</command> method to create the
-Windows group SID to UNIX GID mappings. This change has no effect on winbindd's IDMAP functionality
-for domain groups.
-</para>
-
-</sect2>
-
-<sect2>
-<title>LDAP Changes in Samba-3.0.23</title>
-
-<para>
-<indexterm><primary>LDAP schema</primary></indexterm>
-<indexterm><primary>sambaSID</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>slapindex</primary></indexterm>
-<indexterm><primary>slapd.conf</primary></indexterm>
-There has been a minor update the Samba LDAP schema file. A substring matching rule has been
-added to the <literal>sambaSID</literal> attribute definition. For OpenLDAP servers, this
-will require the addition of <literal>index sambaSID sub</literal> to the
-<filename>slapd.conf</filename> configuration file. It will be necessary to execute the
-<command>slapindex</command> command after making this change. There has been no change to the
-actual data storage schema.
-</para>
-
-</sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="compiling">
-<chapterinfo>
- &author.jelmer;
- &author.jht;
- &author.tridge;
-
- <pubdate> 22 May 2001 </pubdate>
- <pubdate> 18 March 2003 </pubdate>
- <pubdate> June 2005 </pubdate>
-</chapterinfo>
-
-<title>How to Compile Samba</title>
-
-<para>
-You can obtain the Samba source file from the
-<ulink url="https://www.samba.org/">Samba Web site</ulink>. To obtain a development version,
-you can download Samba from Subversion or using <command>rsync</command>.
-</para>
-
-<sect1>
-<title>Access Samba Source Code via GIT</title>
-
-
-<sect2>
-<title>Introduction</title>
-
-<para>
-<indexterm><primary>Subversion</primary></indexterm>
-Samba is developed in an open environment. Developers use
-GIT to <quote>checkin</quote> (also known as
-<quote>commit</quote>) new source code. See the
-<ulink noescape="1"
- url="https://wiki.samba.org/index.php/Using_Git_for_Samba_Development">Using
-Git for Samba Development page</ulink> in the Samba wiki.
-</para>
-
-</sect2>
-
-
-</sect1>
-
-<sect1>
- <title>Accessing the Samba Sources via rsync and ftp</title>
-
-
- <para>
- <indexterm><primary>rsync</primary></indexterm>
- <indexterm><primary>ftp</primary></indexterm>
- <parameter>pserver.samba.org</parameter> also exports unpacked copies of most parts of the Subversion tree
- at the Samba <ulink noescape="1" url="ftp://samba.org/pub/unpacked">unpacked</ulink> location and also
- via anonymous rsync at the Samba <ulink noescape="1"
- url="rsync://samba.org/ftp/unpacked/">rsync</ulink> server location. I recommend using rsync rather
- than ftp, because rsync is capable of compressing data streams, but it is also more useful than FTP because
- during a partial update it will transfer only the data that is missing plus a small overhead. See <ulink
- noescape="1" url="http://rsync.samba.org/">the rsync home page</ulink> for more info on rsync.
- </para>
-
- <para>
- The disadvantage of the unpacked trees is that they do not support automatic
- merging of local changes as GIT does. <command>rsync</command> access is most convenient
- for an initial install.
- </para>
-</sect1>
-
-<sect1>
-<title>Verifying Samba's PGP Signature</title>
-
-<para>
-<indexterm><primary>GPG</primary></indexterm>
-<indexterm><primary>PGP</primary></indexterm>
-It is strongly recommended that you verify the PGP signature for any source file before
-installing it. Even if you're not downloading from a mirror site, verifying PGP signatures
-should be a standard reflex. Many people today use the GNU GPG tool set in place of PGP.
-GPG can substitute for PGP.
-</para>
-
-
-<para>
-With that said, go ahead and download the following files:
-</para>
-
-<para><screen>
-&prompt;<userinput>wget https://www.samba.org/samba/ftp/samba-latest.tar.asc</userinput>
-&prompt;<userinput>wget https://www.samba.org/samba/ftp/samba-latest.tar.gz</userinput>
-&prompt;<userinput>wget https://www.samba.org/samba/ftp/samba-pubkey.asc</userinput>
-</screen></para>
-
-
-<para>
-<indexterm><primary>PGP</primary></indexterm>
-The first file is the PGP signature for the Samba source file; the other is the Samba public
-PGP key itself. Import the public PGP key with:
-<screen>
-&prompt;<userinput>gpg --import samba-pubkey.asc</userinput>
-</screen>
-and verify the Samba source code integrity with:
-<screen>
-&prompt;<userinput>gzip -d samba-latest.tar.gz</userinput>
-&prompt;<userinput>gpg --verify samba-latest.tar.asc</userinput>
-</screen>
-</para>
-
-<para>
-If you receive a message like, <quote>Good signature from Samba Distribution Verification Key...,</quote>
-then all is well. The warnings about trust relationships can be ignored. An
-example of what you would not want to see would be:
-<screen>
-gpg: BAD signature from <quote>Samba Distribution Verification Key</quote>
-</screen>
-</para>
-
-</sect1>
-
-<sect1>
- <title>Building the Binaries</title>
-
- <para>
- <indexterm><primary>configure</primary></indexterm>
- To build the binaries, run the program <userinput>./configure
- </userinput> in the top level directory of the source tree. This should automatically
- configure Samba for your operating system. If you have unusual
- needs, then you may wish to first run:
-<screen>
-&rootprompt;<userinput>./configure --help</userinput>
-</screen>
-</para>
-
- <para>
- This will help you to see what special options can be enabled. Now execute
- <userinput>./configure</userinput> with any arguments it might need:
-<screen>
-&rootprompt;<userinput>./configure <replaceable>[... arguments ...]</replaceable></userinput>
-</screen>
- </para>
-
- <para>
- <indexterm><primary>make</primary></indexterm>
- Execute the following create the binaries:
-<screen>
-&rootprompt; <userinput>make</userinput>
-</screen>
- Once it is successfully compiled, you can execute the command shown here to
- install the binaries and manual pages:
-<screen>
-&rootprompt; <userinput>make install</userinput>
-</screen>
- </para>
-
- <sect2>
- <title>Compiling Samba with Active Directory Support</title>
-
- <para>
- In order to compile Samba with ADS support, you need to have installed
- on your system:
- </para>
-
- <itemizedlist>
-
- <listitem><para>
- The MIT or Heimdal Kerberos development libraries
- (either install from the sources or use a package).
- </para></listitem>
-
- <listitem><para>
- The OpenLDAP development libraries.
- </para></listitem>
-
- </itemizedlist>
-
- <para>
- If your Kerberos libraries are in a nonstandard location, then
- remember to add the configure option
- <option>--with-krb5=<replaceable>DIR</replaceable></option>.
- </para>
-
- <para>
- After you run configure, make sure that the
- <filename>bin/default/include/config.h</filename> it generates contain lines like this:
-<programlisting>
-#define HAVE_KRB5 1
-#define HAVE_LDAP 1
-</programlisting>
- </para>
-
- <para>
- If it does not, configure did not find your KRB5 libraries or
- your LDAP libraries. Look in <filename>bin/config.log</filename> to figure
- out why and fix it.
- </para>
-
- <sect3>
- <title>Installing the Required Packages for Debian</title>
-
- <para>On Debian, you need to install the following packages:</para>
- <para>
- <itemizedlist>
- <listitem><para>libkrb5-dev</para></listitem>
- <listitem><para>krb5-user</para></listitem>
- </itemizedlist>
- </para>
- </sect3>
-
- <sect3>
- <title>Installing the Required Packages for Red Hat Linux</title>
-
- <para>On Red Hat Linux, this means you should have at least: </para>
- <para>
- <itemizedlist>
- <listitem><para>krb5-workstation (for kinit)</para></listitem>
- <listitem><para>krb5-libs (for linking with)</para></listitem>
- <listitem><para>krb5-devel (because you are compiling from source)</para></listitem>
- </itemizedlist>
- </para>
-
- <para>in addition to the standard development environment.</para>
-
- <para>If these files are not installed on your system, you should check the installation
- CDs to find which has them and install the files using your tool of choice. If in doubt
- about what tool to use, refer to the Red Hat Linux documentation.</para>
-
- </sect3>
-
- <sect3>
- <title>SuSE Linux Package Requirements</title>
-
- <para>
- SuSE Linux installs Heimdal packages that may be required to allow you to build
- binary packages. You should verify that the development libraries have been installed on
- your system.
- </para>
-
- <para>
- SuSE Linux Samba RPMs support Kerberos. Please refer to the documentation for
- your SuSE Linux system for information regarding SuSE Linux specific configuration.
- Additionally, SuSE is very active in the maintenance of Samba packages that provide
- the maximum capabilities that are available. You should consider using SuSE-provided
- packages where they are available.
- </para>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-<sect1 id="startingSamba">
- <title>Starting the &smbd; &nmbd; and &winbindd;</title>
-
-
- <para>
- <indexterm><primary>inetd</primary></indexterm>
- You must choose to start &smbd;, &winbindd; and &nmbd; either as daemons or from
- <application>inetd</application>. Don't try to do both! Either you can put
- them in <filename> inetd.conf</filename> and have them started on demand by
- <application>inetd</application> or <application>xinetd</application>, or you
- can start them as daemons either from the command-line or in
- <filename>/etc/rc.local</filename>. See the man pages for details on the
- command line options. Take particular care to read the bit about what user
- you need to have to start Samba. In many cases, you must be root.
- </para>
-
- <para>
- The main advantage of starting &smbd; and &nmbd; using the recommended daemon method
- is that they will respond slightly more quickly to an initial connection request.
- </para>
-
- <sect2>
- <title>Starting &smbd; as a Daemon</title>
-
- <para>
- <indexterm><primary>daemon</primary></indexterm>
-<indexterm><primary>startsmb</primary></indexterm>
- To start the server as a daemon, you should create a script something
- like this one, perhaps calling it <filename>startsmb</filename>.
- </para>
-
-<para><programlisting>
-#!/bin/sh
-/usr/local/samba/sbin/smbd -D
-/usr/local/samba/sbin/winbindd -D
-/usr/local/samba/sbin/nmbd -D
-</programlisting></para>
-
- <para>
- Make it executable with <command>chmod +x startsmb</command>.
- </para>
-
- <para>
- You can then run <command>startsmb</command> by hand or execute
- it from <filename>/etc/rc.local</filename>.
- </para>
-
- <para>
- To kill it, send a kill signal to the processes &nmbd; and &smbd;.
- </para>
-
- <note><para>
- If you use the SVR4-style init system, you may like to look at the
- <filename>examples/svr4-startup</filename> script to make Samba fit
- into that system.
- </para></note>
-
- <sect3>
- <title>Starting Samba for Red Hat Linux</title>
- <para>
- The process for starting Samba will now be outlined. Be sure to configure Samba's &smb.conf;
- file before starting Samba. When configured, start Samba by executing:
-<screen>
-&rootprompt; service smb start
-&rootprompt; service winbind start
-</screen>
- These steps will start &nmbd;, &smbd; and &winbindd;.
- </para>
-
- <para>
- To ensure that these services will be automatically restarted when the system is rebooted
- execute:
-<screen>
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig winbind on
-</screen>
- Samba will be started automatically at every system reboot.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Starting Samba for Novell SUSE Linux</title>
-
- <para>
- Novell SUSE Linux products automatically install all essential Samba components in a default installation.
- Configure your &smb.conf; file, then execute the following to start Samba:
-<screen>
-&rootprompt; rcnmb start
-&rootprompt; rcsmb start
-&rootprompt; rcwinbind start
-</screen>
- Now execute these commands so that Samba will be started automatically following a system
- reboot:
-<screen>
-&rootprompt; chkconfig nmb on
-&rootprompt; chkconfig smb on
-&rootprompt; chkconfig winbind on
-</screen>
- The Samba services will now be started automatically following a system reboot.
- </para>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="cfgsmarts">
-<chapterinfo>
- &author.jht;
- <pubdate>June 30, 2005</pubdate>
-</chapterinfo>
-<title>Advanced Configuration Techniques</title>
-
-<para>
-<indexterm><primary>configuration techniques</primary></indexterm>
-<indexterm><primary>include</primary></indexterm>
-Since the release of the first edition of this book there have been repeated requests to better document
-configuration techniques that may help a network administrator to get more out of Samba. Some users have asked
-for documentation regarding the use of the <smbconfoption name="include">file-name</smbconfoption> parameter.
-</para>
-
-<para>
-<indexterm><primary>multiple servers</primary></indexterm>
-<indexterm><primary>multiple server personalities</primary></indexterm>
-Commencing around mid-2004 there has been increasing interest in the ability to host multiple Samba servers on
-one machine. There has also been an interest in the hosting of multiple Samba server personalities on one
-server.
-</para>
-
-<para>
-<indexterm><primary>technical reviewers</primary></indexterm>
-<indexterm><primary>reviewers</primary></indexterm>
-Feedback from technical reviewers made the inclusion of this chapter a necessity. So, here is an
-answer the questions that have to date not been adequately addressed. Additional user input is welcome as
-it will help this chapter to mature. What is presented here is just a small beginning.
-</para>
-
-<para>
-<indexterm><primary>multiple servers</primary></indexterm>
-<indexterm><primary>multiple hosting</primary></indexterm>
-<indexterm><primary>domain controllers</primary></indexterm>
-There are a number of ways in which multiple servers can be hosted on a single Samba server. Multiple server
-hosting makes it possible to host multiple domain controllers on one machine. Each such machine is
-independent, and each can be stopped or started without affecting another.
-</para>
-
-<para>
-<indexterm><primary>multiple servers</primary></indexterm>
-<indexterm><primary>DMS</primary></indexterm>
-<indexterm><primary>anonymous server</primary></indexterm>
-Sometimes it is desirable to host multiple servers, each with its own security mode. For example, a single
-UNIX/Linux host may be a domain member server (DMS) as well as a generic anonymous print server. In this case,
-only domain member machines and domain users can access the DMS, but even guest users can access the generic
-print server. Another example of a situation where it may be beneficial to host a generic (anonymous) server
-is to host a CDROM server.
-</para>
-
-<para>
-<indexterm><primary>separate servers</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-Some environments dictate the need to have separate servers, each with their own resources, each of which are
-accessible only by certain users or groups. This is one of the simple, but highly effective, ways that Samba
-can replace many physical Windows servers in one Samba installation.
-</para>
-
-<sect1>
-<title>Implementation</title>
-
-<para>
-</para>
-
-<sect2>
-<title>Multiple Server Hosting</title>
-
-<para>
-<indexterm><primary>multiple server hosting</primary></indexterm>
-<indexterm><primary>separate instances</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>recompiling</primary></indexterm>
-<indexterm><primary>TDB</primary></indexterm>
-The use of multiple server hosting involves running multiple separate instances of Samba, each with it's own
-configuration file. This method is complicated by the fact that each instance of &nmbd;, &smbd; and &winbindd;
-must have write access to entirely separate TDB files. The ability to keep separate the TDB files used by
-&nmbd;, &smbd; and &winbindd; can be enabled either by recompiling Samba for each server hosted so each has its
-own default TDB directories, or by configuring these in the &smb.conf; file, in which case each instance of
-&nmbd;, &smbd; and &winbindd; must be told to start up with its own &smb.conf; configuration file.
-</para>
-
-<para>
-<indexterm><primary>independent</primary></indexterm>
-<indexterm><primary>listen own socket</primary></indexterm>
-<indexterm><primary>socket</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-Each instance should operate on its own IP address (that independent IP address can be an IP Alias).
-Each instance of &nmbd;, &smbd; and &winbindd; should listen only on its own IP socket. This can be secured
-using the <smbconfoption name="socket address"/> parameter. Each instance of the Samba server will have its
-own SID also, this means that the servers are discrete and independent of each other.
-</para>
-
-<para>
-<indexterm><primary>multiple server hosting</primary></indexterm>
-<indexterm><primary>private dir</primary></indexterm>
-<indexterm><primary>pid directory</primary></indexterm>
-<indexterm><primary>lock directory</primary></indexterm>
-<indexterm><primary>interfaces</primary></indexterm>
-<indexterm><primary>bind interfaces only</primary></indexterm>
-<indexterm><primary>netbios name</primary></indexterm>
-<indexterm><primary>workgroup</primary></indexterm>
-<indexterm><primary>socket address</primary></indexterm>
-The user of multiple server hosting is non-trivial, and requires careful configuration of each aspect of
-process management and start up. The &smb.conf; parameters that must be carefully configured includes:
-<smbconfoption name="private dir"/>, <smbconfoption name="pid directory"/>,<smbconfoption name="lock
-directory"/>, <smbconfoption name="interfaces"/>, <smbconfoption name="bind interfaces only"/>, <smbconfoption
-name="netbios name"/>, <smbconfoption name="workgroup"/>, <smbconfoption name="socket address"/>.
-</para>
-
-<para>
-<indexterm><primary>multiple servers</primary></indexterm>
-<indexterm><primary>contribute</primary></indexterm>
-<indexterm><primary>comprehensive documentation</primary></indexterm>
-Those who elect to create multiple Samba servers should have the ability to read and follow
-the Samba source code, and to modify it as needed. This mode of deployment is considered beyond the scope of
-this book. However, if someone will contribute more comprehensive documentation we will gladly review it, and
-if it is suitable extend this section of this chapter. Until such documentation becomes available the hosting
-of multiple samba servers on a single host is considered not supported for Samba by the Samba Team.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Multiple Virtual Server Personalities</title>
-
-<para>
-<indexterm><primary>multiple virtual servers</primary></indexterm>
-<indexterm><primary>netbios alias</primary></indexterm>
-<indexterm><primary>meta-services</primary></indexterm>
-Samba has the ability to host multiple virtual servers, each of which have their own personality. This is
-achieved by configuring an &smb.conf; file that is common to all personalities hosted. Each server
-personality is hosted using its own <smbconfoption name="netbios alias"/> name, and each has its own distinct
-<smbconfoption name="[global]"/> section. Each server may have its own stanzas for services and meta-services.
-</para>
-
-<para>
-<indexterm><primary>workgroup</primary></indexterm>
-<indexterm><primary>security</primary></indexterm>
-<indexterm><primary>netbios aliases</primary></indexterm>
-When hosting multiple virtual servers, each with their own personality, each can be in a different workgroup.
-Only the primary server can be a domain member or a domain controller. The personality is defined by the
-combination of the <smbconfoption name="security"/> mode it is operating in, the <smbconfoption name="netbios
-aliases"/> it has, and the <smbconfoption name="workgroup"/> that is defined for it.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS name</primary></indexterm>
-<indexterm><primary>NetBIOS-less SMB</primary></indexterm>
-<indexterm><primary>smb ports</primary></indexterm>
-<indexterm><primary>TCP port 139</primary></indexterm>
-<indexterm><primary>TCP port 445</primary></indexterm>
-<indexterm><primary>%L</primary></indexterm>
-This configuration style can be used either with NetBIOS names, or using NetBIOS-less SMB over TCP services.
-If run using NetBIOS mode (the most common method) it is important that the parameter <smbconfoption name="smb
-ports">139</smbconfoption> should be specified in the primary &smb.conf; file. Failure to do this will result
-in Samba operating over TCP port 445 and problematic operation at best, and at worst only being able to obtain
-the functionality that is specified in the primary &smb.conf; file. The use of NetBIOS over TCP/IP using only
-TCP port 139 means that the use of the <literal>%L</literal> macro is fully enabled. If the <smbconfoption
-name="smb ports">139</smbconfoption> is not specified (the default is <parameter>445 139</parameter>, or if
-the value of this parameter is set at <parameter>139 445</parameter> then the <literal>%L</literal> macro
-is not serviceable.
-</para>
-
-<para>
-<indexterm><primary>host multiple servers</primary></indexterm>
-<indexterm><primary>multiple personality</primary></indexterm>
-<indexterm><primary>NetBIOS-less</primary></indexterm>
-<indexterm><primary>%i macro</primary></indexterm>
-It is possible to host multiple servers, each with their own personality, using port 445 (the NetBIOS-less SMB
-port), in which case the <literal>%i</literal> macro can be used to provide separate server identities (by
-IP Address). Each can have its own <smbconfoption name="security"/> mode. It will be necessary to use the
-<smbconfoption name="interfaces"/>, <smbconfoption name="bind interfaces only"/> and IP aliases in addition to
-the <smbconfoption name="netbios name"/> parameters to create the virtual servers. This method is considerably
-more complex than that using NetBIOS names only using TCP port 139.
-</para>
-
-<para>
-<indexterm><primary>anonymous file server</primary></indexterm>
-Consider an example environment that consists of a standalone, user-mode security Samba server and a read-only
-Windows 95 file server that has to be replaced. Instead of replacing the Windows 95 machine with a new PC, it
-is possible to add this server as a read-only anonymous file server that is hosted on the Samba server. Here
-are some parameters:
-</para>
-
-<para>
-The Samba server is called <literal>ELASTIC</literal>, its workgroup name is <literal>ROBINSNEST</literal>.
-The CDROM server is called <literal>CDSERVER</literal> and its workgroup is <literal>ARTSDEPT</literal>. A
-possible implementation is shown here:
-</para>
-
-<para>
-<indexterm><primary>/etc/samba</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>smb.conf</primary></indexterm>
-The &smb.conf; file for the master server is shown in <link linkend="elastic">Elastic smb.conf File</link>.
-This file is placed in the <filename>/etc/samba</filename> directory. Only the &nmbd; and the &smbd; daemons
-are needed. When started the server will appear in Windows Network Neighborhood as the machine
-<literal>ELASTIC</literal> under the workgroup <literal>ROBINSNEST</literal>. It is helpful if the Windows
-clients that must access this server are also in the workgroup <literal>ROBINSNEST</literal> as this will make
-browsing much more reliable.
-</para>
-
-<example id="elastic">
-<title>Elastic smb.conf File</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">ROBINSNEST</smbconfoption>
-<smbconfoption name="netbios name">ELASTIC</smbconfoption>
-<smbconfoption name="netbios aliases">CDSERVER</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-<smbconfoption name="disable spoolss">Yes</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-<smbconfoption name="include">/etc/samba/smb-%L.conf</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[office]"/>
-<smbconfoption name="comment">Data</smbconfoption>
-<smbconfoption name="path">/data</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="create mask">0600</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>smb-cdserver.conf</primary></indexterm>
-The configuration file for the CDROM server is listed in <link linkend="cdserver">CDROM Server
-smb-cdserver.conf file</link>. This file is called <filename>smb-cdserver.conf</filename> and it should be
-located in the <filename>/etc/samba</filename> directory. Machines that are in the workgroup
-<literal>ARTSDEPT</literal> will be able to browse this server freely.
-</para>
-
-<example id="cdserver">
-<title>CDROM Server smb-cdserver.conf file</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">ARTSDEPT</smbconfoption>
-<smbconfoption name="netbios name">CDSERVER</smbconfoption>
-<smbconfoption name="map to guest">Bad User</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-
-<smbconfsection name="[carousel]"/>
-<smbconfoption name="comment">CDROM Share</smbconfoption>
-<smbconfoption name="path">/export/cddata</smbconfoption>
-<smbconfoption name="read only">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>different resources</primary></indexterm>
-<indexterm><primary>separate workgroups</primary></indexterm>
-<indexterm><primary>read-only access</primary></indexterm>
-<indexterm><primary>nobody account</primary></indexterm>
-The two servers have different resources and are in separate workgroups. The server <literal>ELASTIC</literal>
-can only be accessed by uses who have an appropriate account on the host server. All users will be able to
-access the CDROM data that is stored in the <filename>/export/cddata</filename> directory. File system
-permissions should set so that the <literal>others</literal> user has read-only access to the directory and its
-contents. The files can be owned by root (any user other than the nobody account).
-</para>
-
-</sect2>
-
-<sect2>
-<title>Multiple Virtual Server Hosting</title>
-
-<para>
-<indexterm><primary>primary domain controller</primary></indexterm>
-<indexterm><primary>extra machine</primary></indexterm>
-<indexterm><primary>same domain/workgroup</primary></indexterm>
-In this example, the requirement is for a primary domain controller for the domain called
-<literal>MIDEARTH</literal>. The PDC will be called <literal>MERLIN</literal>. An extra machine called
-<literal>SAURON</literal> is required. Each machine will have only its own shares. Both machines belong to the
-same domain/workgroup.
-</para>
-
-<para>
-<indexterm><primary>master smb.conf</primary></indexterm>
-<indexterm><primary>/etc/samba</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-The master &smb.conf; file is shown in <link linkend="mastersmbc">the Master smb.conf File Global Section</link>.
-The two files that specify the share information for each server are shown in <link linkend="merlinsmbc">the
-smb-merlin.conf File Share Section</link>, and <link linkend="sauronsmbc">the smb-sauron.conf File Share
-Section</link>. All three files are locate in the <filename>/etc/samba</filename> directory.
-</para>
-
-<example id="mastersmbc">
-<title>Master smb.conf File Global Section</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">MERLIN</smbconfoption>
-<smbconfoption name="netbios aliases">SAURON</smbconfoption>
-<smbconfoption name="passdb backend">tdbsam</smbconfoption>
-<smbconfoption name="smb ports">139</smbconfoption>
-<smbconfoption name="syslog">0</smbconfoption>
-<smbconfoption name="printcap name">CUPS</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="add user script">/usr/sbin/useradd -m '%u'</smbconfoption>
-<smbconfoption name="delete user script">/usr/sbin/userdel -r '%u'</smbconfoption>
-<smbconfoption name="add group script">/usr/sbin/groupadd '%g'</smbconfoption>
-<smbconfoption name="delete group script">/usr/sbin/groupdel '%g'</smbconfoption>
-<smbconfoption name="add user to group script">/usr/sbin/usermod -G '%g' '%u'</smbconfoption>
-<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'</smbconfoption>
-<smbconfoption name="logon script">scripts\login.bat</smbconfoption>
-<smbconfoption name="logon path"> </smbconfoption>
-<smbconfoption name="logon drive">X:</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="wins support">Yes</smbconfoption>
-<smbconfoption name="printing">CUPS</smbconfoption>
-<smbconfoption name="include">/etc/samba/smb-%L.conf</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="merlinsmbc">
-<title>MERLIN smb-merlin.conf File Share Section</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">MERLIN</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[office]"/>
-<smbconfoption name="comment">Data</smbconfoption>
-<smbconfoption name="path">/data</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">NETLOGON</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="read only">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="sauronsmbc">
-<title>SAURON smb-sauron.conf File Share Section</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">SAURON</smbconfoption>
-
-<smbconfsection name="[www]"/>
-<smbconfoption name="comment">Web Pages</smbconfoption>
-<smbconfoption name="path">/srv/www/htdocs</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-</smbconfblock>
-</example>
-
-</sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="DNSDHCP">
-<chapterinfo>
- &author.jht;
-</chapterinfo>
-
-<title>DNS and DHCP Configuration Guide</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>Dynamic Host Configuration Protocol</primary><see>DHCP</see></indexterm>
-<indexterm><primary>Domain Name System</primary><see>DNS</see></indexterm>
-There are few subjects in the UNIX world that might raise as much contention as
-Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP).
-Not all opinions held for or against particular implementations of DNS and DHCP
-are valid.
-</para>
-
-<para>
-We live in a modern age where many information technology users demand mobility
-and freedom. Microsoft Windows users in particular expect to be able to plug their
-notebook computer into a network port and have things <quote>just work.</quote>
-</para>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-UNIX administrators have a point. Many of the normative practices in the Microsoft
-Windows world at best border on bad practice from a security perspective.
-Microsoft Windows networking protocols allow workstations to arbitrarily register
-themselves on a network. Windows 2000 Active Directory registers entries in the DNS namespace
-that are equally perplexing to UNIX administrators. Welcome to the new world!
-</para>
-
-
-<para>
-<indexterm><primary>ISC</primary><secondary>DNS</secondary></indexterm>
-<indexterm><primary>ISC</primary><secondary>DHCP</secondary></indexterm>
-<indexterm><primary>Dynamic DNS</primary><see>DDNS</see></indexterm>
-The purpose of this chapter is to demonstrate the configuration of the Internet
-Software Consortium (ISC) DNS and DHCP servers to provide dynamic services that are
-compatible with their equivalents in the Microsoft Windows 2000 Server products.
-</para>
-
-<para>
-This chapter provides no more than a working example of configuration files for both DNS and DHCP servers. The
-examples used match configuration examples used elsewhere in this document.
-</para>
-
-<para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>DHCP</primary></indexterm>
-<indexterm><primary>BIND9.NET</primary></indexterm>
-This chapter explicitly does not provide a tutorial, nor does it pretend to be a reference guide on DNS and
-DHCP, as this is well beyond the scope and intent of this document as a whole. Anyone who wants more detailed
-reference materials on DNS or DHCP should visit the ISC Web site at <ulink noescape="1"
-url="http://www.isc.org"> http://www.isc.org</ulink>. Those wanting a written text might also be interested
-in the O'Reilly publications on DNS, see the <ulink
-url="http://www.oreilly.com/catalog/dns/index.htm">O'Reilly</ulink> web site, and the <ulink
-url="http://www.bind9.net/books-dhcp">BIND9.NET</ulink> web site for details.
-The books are:
-</para>
-
-<orderedlist>
- <listitem><para>DNS and BIND, By Cricket Liu, Paul Albitz, ISBN: 1-56592-010-4</para></listitem>
- <listitem><para>DNS & Bind Cookbook, By Cricket Liu, ISBN: 0-596-00410-9</para></listitem>
- <listitem><para>The DHCP Handbook (2nd Edition), By: Ralph Droms, Ted Lemon, ISBN 0-672-32327-3</para></listitem>
-</orderedlist>
-
-</sect1>
-
-<sect1>
-<title>Example Configuration</title>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-The DNS is to the Internet what water is to life. Nearly all information resources (host names) are resolved
-to their Internet protocol (IP) addresses through DNS. Windows networking tried hard to avoid the
-complexities of DNS, but alas, DNS won. <indexterm><primary>WINS</primary></indexterm> The alternative to
-DNS, the Windows Internet Name Service (WINS) &smbmdash; an artifact of NetBIOS networking over the TCP/IP
-protocols &smbmdash; has demonstrated scalability problems as well as a flat, nonhierarchical namespace that
-became unmanageable as the size and complexity of information technology networks grew.
-</para>
-
-<para>
-<indexterm><primary>RFC 1001</primary></indexterm>
-<indexterm><primary>RFC 1002</primary></indexterm>
-WINS is a Microsoft implementation of the RFC1001/1002 NetBIOS Name Service (NBNS).
-It allows NetBIOS clients (like Microsoft Windows machines) to register an arbitrary
-machine name that the administrator or user has chosen together with the IP
-address that the machine has been given. Through the use of WINS, network client machines
-could resolve machine names to their IP address.
-</para>
-
-<para>
-The demand for an alternative to the limitations of NetBIOS networking finally drove
-Microsoft to use DNS and Active Directory. Microsoft's new implementation attempts
-to use DNS in a manner similar to the way that WINS is used for NetBIOS networking.
-Both WINS and Microsoft DNS rely on dynamic name registration.
-</para>
-
-<para>
-Microsoft Windows clients can perform dynamic name registration to the DNS server
-on startup. Alternatively, where DHCP is used to assign workstation IP addresses,
-it is possible to register hostnames and their IP address by the DHCP server as
-soon as a client acknowledges an IP address lease. Finally, Microsoft DNS can resolve
-hostnames via Microsoft WINS.
-</para>
-
-<para>
-The following configurations demonstrate a simple, insecure dynamic DNS server and
-a simple DHCP server that matches the DNS configuration.
-</para>
-
- <sect2>
- <title>Dynamic DNS</title>
-
- <para>
- <indexterm><primary>DNS</primary><secondary>Dynamic</secondary></indexterm>
- The example DNS configuration is for a private network in the IP address
- space for network 192.168.1.0/24. The private class network address space
- is set forth in RFC1918.
- </para>
-
-
- <para>
- <indexterm><primary>BIND</primary></indexterm>
- It is assumed that this network will be situated behind a secure firewall.
- The files that follow work with ISC BIND version 9. BIND is the Berkeley
- Internet Name Daemon.
- </para>
-
- <para>
- The master configuration file <filename>/etc/named.conf</filename>
- determines the location of all further configuration files used.
- The location and name of this file is specified in the startup script
- that is part of the operating system.
-<programlisting>
-# Quenya.Org configuration file
-
-acl mynet {
- 192.168.1.0/24;
- 127.0.0.1;
-};
-
-options {
-
- directory "/var/named";
- listen-on-v6 { any; };
- notify no;
- forward first;
- forwarders {
- 192.168.1.1;
- };
- auth-nxdomain yes;
- multiple-cnames yes;
- listen-on {
- mynet;
- };
-};
-
-# The following three zone definitions do not need any modification.
-# The first one defines localhost while the second defines the
-# reverse lookup for localhost. The last zone "." is the
-# definition of the root name servers.
-
-zone "localhost" in {
- type master;
- file "localhost.zone";
-};
-
-zone "0.0.127.in-addr.arpa" in {
- type master;
- file "127.0.0.zone";
-};
-
-zone "." in {
- type hint;
- file "root.hint";
-};
-
-# You can insert further zone records for your own domains below.
-
-zone "quenya.org" {
- type master;
- file "/var/named/quenya.org.hosts";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
- };
-
-zone "1.168.192.in-addr.arpa" {
- type master;
- file "/var/named/192.168.1.0.rev";
- allow-query {
- mynet;
- };
- allow-transfer {
- mynet;
- };
- allow-update {
- mynet;
- };
-};
-</programlisting>
- </para>
-
- <para>
- The following files are all located in the directory <filename>/var/named</filename>.
- This is the <filename>/var/named/localhost.zone</filename> file:
-<programlisting>
-$TTL 1W
-@ IN SOA @ root (
- 42 ; serial (d. adams)
- 2D ; refresh
- 4H ; retry
- 6W ; expiry
- 1W ) ; minimum
-
- IN NS @
- IN A 127.0.0.1
- </programlisting>
- </para>
-
- <para>
- The <filename>/var/named/127.0.0.zone</filename> file:
-<programlisting>
-$TTL 1W
-@ IN SOA localhost. root.localhost. (
- 42 ; serial (d. adams)
- 2D ; refresh
- 4H ; retry
- 6W ; expiry
- 1W ) ; minimum
-
- IN NS localhost.
-1 IN PTR localhost.
-</programlisting>
- </para>
-
- <para>
- The <filename>/var/named/quenya.org.host</filename> file:
-<programlisting>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-quenya.org IN SOA marvel.quenya.org. root.quenya.org. (
- 2003021832 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS marvel.quenya.org.
- MX 10 mail.quenya.org.
-$ORIGIN quenya.org.
-frodo A 192.168.1.1
-marvel A 192.168.1.2
-;
-mail CNAME marvel
-www CNAME marvel
-</programlisting>
-</para>
-
-<para>
- The <filename>/var/named/192.168.1.0.rev</filename> file:
-<programlisting>
-$ORIGIN .
-$TTL 38400 ; 10 hours 40 minutes
-1.168.192.in-addr.arpa IN SOA marvel.quenya.org. root.quenya.org. (
- 2003021824 ; serial
- 10800 ; refresh (3 hours)
- 3600 ; retry (1 hour)
- 604800 ; expire (1 week)
- 38400 ; minimum (10 hours 40 minutes)
- )
- NS marvel.quenya.org.
-$ORIGIN 1.168.192.in-addr.arpa.
-1 PTR frodo.quenya.org.
-2 PTR marvel.quenya.org.
-</programlisting>
- </para>
-
- <para>
-<indexterm><primary>BIND</primary></indexterm>
-<indexterm><primary>dynamic registration files</primary></indexterm>
- The configuration files shown here were copied from a fully working system. All dynamically registered
- entries have been removed. In addition to these files, BIND version 9 will
- create for each of the dynamic registration files a file that has a
- <filename>.jnl</filename> extension. Do not edit or tamper with the configuration
- files or with the <filename>.jnl</filename> files that are created.
- </para>
-
- </sect2>
-
- <sect2 id="DHCP">
- <title>DHCP Server</title>
-
- <para>
- The following file is used with the ISC DHCP Server version 3.
- The file is located in <filename>/etc/dhcpd.conf</filename>:
- </para>
-
- <para>
- <programlisting>
-ddns-updates on;
-ddns-domainname "quenya.org";
-option ntp-servers 192.168.1.2;
-ddns-update-style ad-hoc;
-allow unknown-clients;
-default-lease-time 86400;
-max-lease-time 172800;
-
-option domain-name "quenya.org";
-option domain-name-servers 192.168.1.2;
-option netbios-name-servers 192.168.1.2;
-option netbios-dd-server 192.168.1.2;
-option netbios-node-type 8;
-
-subnet 192.168.1.0 netmask 255.255.255.0 {
- range dynamic-bootp 192.168.1.60 192.168.1.254;
- option subnet-mask 255.255.255.0;
- option routers 192.168.1.2;
- allow unknown-clients;
-}
-</programlisting>
- </para>
-
- <para>
- In this example, IP addresses between 192.168.1.1 and 192.168.1.59 are
- reserved for fixed-address (commonly called <constant>hard-wired</constant>) IP addresses. The
- addresses between 192.168.1.60 and 192.168.1.254 are allocated for dynamic use.
- </para>
-
- </sect2>
-
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="diagnosis">
-<chapterinfo>
- &author.tridge;
- &author.jelmer;
- &author.danshearer;
- <pubdate>Wed Jan 15</pubdate>
-</chapterinfo>
-
-<title>The Samba Checklist</title>
-
-<sect1>
-<title>Introduction</title>
-
-<para>
-<indexterm><primary>validate</primary></indexterm>
-This file contains a list of tests you can perform to validate your
-Samba server. It also tells you what the likely cause of the problem
-is if it fails any one of these steps. If it passes all these tests,
-then it is probably working fine.
-</para>
-
-<para>
-You should do all the tests in the order shown. We have tried to
-carefully choose them so later tests only use capabilities verified in
-the earlier tests. However, do not stop at the first error: there
-have been some instances when continuing with the tests has helped
-to solve a problem.
-</para>
-
-<para>
-If you send one of the Samba mailing lists an email saying, <quote>It does not work,</quote>
-and you have not followed this test procedure, you should not be surprised
-if your email is ignored.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Assumptions</title>
-
-<para>
-In all of the tests, it is assumed you have a Samba server called
-BIGSERVER and a PC called ACLIENT, both in workgroup TESTGROUP.
-</para>
-
-<para>
-The procedure is similar for other types of clients.
-</para>
-
-<para>
-It is also assumed you know the name of an available share in your
-&smb.conf;. I for our examples this share is called <smbconfsection name="tmp"/>.
-You can add a <smbconfsection name="tmp"/> share like this by adding the
-lines shown in <link linkend="tmpshare">the next example</link>.
-</para>
-
-<example id="tmpshare">
-<title>smb.conf with [tmp] Share</title>
-<smbconfblock>
-<smbconfsection name="[tmp]"/>
-<smbconfoption name="comment">temporary files </smbconfoption>
-<smbconfoption name="path">/tmp</smbconfoption>
-<smbconfoption name="read only">yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<note><para>
-These tests assume version 3.0.0 or later of the Samba suite.
-Some commands shown did not exist in earlier versions.
-</para></note>
-
-<para>
-<indexterm><primary>error messages</primary></indexterm>
-<indexterm><primary>name resolution</primary></indexterm>
-<indexterm><primary>/etc/resolv.conf</primary></indexterm>
-Please pay attention to the error messages you receive. If any error message
-reports that your server is being unfriendly, you should first check that your
-IP name resolution is correctly set up. Make sure your <filename>/etc/resolv.conf</filename>
-file points to name servers that really do exist.
-</para>
-
-<para>
-<indexterm><primary>DNS server access</primary></indexterm>
-<indexterm><primary>name resolution</primary></indexterm>
-<indexterm><primary>dns proxy</primary></indexterm>
-<indexterm><primary>testparm</primary></indexterm>
-Also, if you do not have DNS server access for name resolution, please check
-that the settings for your &smb.conf; file results in <parameter>dns proxy = no</parameter>. The
-best way to check this is with <command>testparm smb.conf</command>.
-</para>
-
-
-<para>
-<indexterm><primary>log files</primary></indexterm>
-<indexterm><primary>tail</primary></indexterm>
-<indexterm><primary>/usr/local/samba/var</primary></indexterm>
-<indexterm><primary>/var/log/samba</primary></indexterm>
-<indexterm><primary>log files</primary><secondary>monitoring</secondary></indexterm>
-It is helpful to monitor the log files during testing by using the
-<command>tail -F log_file_name</command> in a separate
-terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X).
-Relevant log files can be found (for default installations) in
-<filename>/usr/local/samba/var</filename>. Also, connection logs from
-machines can be found here or possibly in <filename>/var/log/samba</filename>,
-depending on how or if you specified logging in your &smb.conf; file.
-</para>
-
-<para>
-If you make changes to your &smb.conf; file while going through these test,
-remember to restart &smbd; and &nmbd;.
-</para>
-
-</sect1>
-
-<sect1>
-<title>The Tests</title>
-<procedure>
-<title>Diagnosing Your Samba Server</title>
-
-
-<step performance="required">
-<para>
-<indexterm><primary>testparm</primary></indexterm>
-In the directory in which you store your &smb.conf; file, run the command
-<command>testparm smb.conf</command>. If it reports any errors, then your &smb.conf;
-configuration file is faulty.
-</para>
-
-<note><para>
-<indexterm><primary>/etc/samba</primary></indexterm>
-<indexterm><primary>/usr/local/samba/etc</primary></indexterm>
-Your &smb.conf; file may be located in <filename>/etc/samba</filename>
-or in <filename>/usr/local/samba/etc</filename>.
-</para></note>
-</step>
-
-<step performance="required">
-<para>
-<indexterm><primary>ping</primary></indexterm>
-Run the command <command>ping BIGSERVER</command> from the PC and
-<command>ping ACLIENT</command> from the UNIX box. If you do not get a valid response,
-then your TCP/IP software is not correctly installed.
-</para>
-
-<para>
-You will need to start a <quote>DOS prompt</quote> window on the PC to run ping.
-</para>
-
-<para>
-<indexterm><primary>/etc/hosts</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>/etc/resolv.conf</primary></indexterm>
-If you get a message saying <quote><errorname>host not found</errorname></quote> or a similar message, then
-your DNS software or <filename>/etc/hosts</filename> file is not correctly set up. If using DNS, check that
-the <filename>/etc/resolv.conf</filename> has correct, current, entries in it. It is possible to run
-Samba without DNS entries for the server and client, but it is assumed you do have correct entries for the
-remainder of these tests.
-</para>
-
-<para>
-<indexterm><primary>firewall</primary></indexterm>
-<indexterm><primary>iptables</primary></indexterm>
-<indexterm><primary>ipchains</primary></indexterm>
-Another reason why ping might fail is if your host is running firewall
-software. You will need to relax the rules to let in the workstation
-in question, perhaps by allowing access from another subnet (on Linux
-this is done via the appropriate firewall maintenance commands <command>ipchains</command>
-or <command>iptables</command>).
-</para>
-
-<note>
-<para>
-Modern Linux distributions install ipchains/iptables by default.
-This is a common problem that is often overlooked.
-</para>
-</note>
-
-<para>
-<indexterm><primary>iptables</primary></indexterm>
-<indexterm><primary>ipchains</primary></indexterm>
-If you wish to check what firewall rules may be present in a system under test, simply run
-<command>iptables -L -v</command>, or if <parameter>ipchains</parameter>-based firewall rules are in use,
-<command>ipchains -L -v</command>.
-</para>
-
-<para>
-Here is a sample listing from a system that has an external Ethernet interface (eth1) on which Samba
-is not active and an internal (private network) interface (eth0) on which Samba is active:
-<screen>
-frodo:~ # iptables -L -v
-Chain INPUT (policy DROP 98496 packets, 12M bytes)
- pkts bytes target prot opt in out source destination
- 187K 109M ACCEPT all -- lo any anywhere anywhere
- 892K 125M ACCEPT all -- eth0 any anywhere anywhere
-1399K 1380M ACCEPT all -- eth1 any anywhere anywhere \
- state RELATED,ESTABLISHED
-
-Chain FORWARD (policy DROP 0 packets, 0 bytes)
- pkts bytes target prot opt in out source destination
- 978K 1177M ACCEPT all -- eth1 eth0 anywhere anywhere \
- state RELATED,ESTABLISHED
- 658K 40M ACCEPT all -- eth0 eth1 anywhere anywhere
- 0 0 LOG all -- any any anywhere anywhere \
- LOG level warning
-
-Chain OUTPUT (policy ACCEPT 2875K packets, 1508M bytes)
- pkts bytes target prot opt in out source destination
-
-Chain reject_func (0 references)
- pkts bytes target prot opt in out source destination
-</screen>
-</para>
-
-</step>
-
-<step performance="required">
-<para>
-Run the command <command>smbclient -L BIGSERVER</command>
-on the UNIX box. You should get back a list of available shares.
-</para>
-
-<para>
-<indexterm><primary>bad password</primary></indexterm>
-<indexterm><primary>hosts allow</primary></indexterm>
-<indexterm><primary>hosts deny</primary></indexterm>
-<indexterm><primary>valid users</primary></indexterm>
-<indexterm><primary>guest account</primary></indexterm>
-<indexterm><primary>invalid users</primary></indexterm>
-If you get an error message containing the string <quote>bad password</quote>, then
-you probably have either an incorrect <parameter>hosts allow</parameter>,
-<parameter>hosts deny</parameter>, or <parameter>valid users</parameter> line in your
-&smb.conf;, or your guest account is not valid. Check what your guest account is using &testparm; and
-temporarily remove any <parameter>hosts allow</parameter>, <parameter>hosts deny</parameter>,
-<parameter>valid users</parameter>, or <parameter>invalid users</parameter> lines.
-</para>
-
-<para>
-<indexterm><primary>inetd.conf</primary></indexterm>
-If you get a message <literal>connection refused</literal> response, then the <command>smbd</command> server may
-not be running. If you installed it in <filename>inetd.conf</filename>, then you probably edited
-that file incorrectly. If you installed it as a daemon, then check that
-it is running and check that the netbios-ssn port is in a LISTEN
-state using <command>netstat -a</command>.
-</para>
-
-<note><para>
-<indexterm><primary>inetd</primary></indexterm>
-<indexterm><primary>xinetd</primary><see>inetd</see></indexterm>
-Some UNIX/Linux systems use <command>xinetd</command> in place of
-<command>inetd</command>. Check your system documentation for the location
-of the control files for your particular system implementation of
-the network super daemon.
-</para></note>
-
-<para>
-If you get a message saying <literal>session request failed,</literal> the server refused the
-connection. If it says <quote>Your server software is being unfriendly,</quote> then
-it's probably because you have invalid command line parameters to &smbd;,
-or a similar fatal problem with the initial startup of &smbd;. Also
-check your config file (&smb.conf;) for syntax errors with &testparm;
-and that the various directories where Samba keeps its log and lock
-files exist.
-</para>
-
-<para>
-There are a number of reasons for which smbd may refuse or decline
-a session request. The most common of these involve one or more of
-the &smb.conf; file entries as shown in <link linkend="modif1">the next example</link>.
-</para>
-
-
-<example id="modif1">
-<title>Configuration for Allowing Connections Only from a Certain Subnet</title>
-<smbconfblock>
-<smbconfsection name="[globals]"/>
-<smbconfoption name="hosts deny">ALL</smbconfoption>
-<smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy</smbconfoption>
-<smbconfoption name="interfaces">eth0</smbconfoption>
-<smbconfoption name="bind interfaces only">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>loopback adapter</primary></indexterm>
-In <link linkend="modif1">Configuration for Allowing Connections Only from a Certain Subnet</link>, no
-allowance has been made for any session requests that will automatically translate to the loopback adapter
-address 127.0.0.1. To solve this problem, change these lines as shown in <link linkend="modif2">the following
-example</link>.
-</para>
-
-<example id="modif2">
-<title>Configuration for Allowing Connections from a Certain Subnet and localhost</title>
-<smbconfblock>
-<smbconfsection name="[globals]"/>
-<smbconfoption name="hosts deny">ALL</smbconfoption>
-<smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy 127.</smbconfoption>
-<smbconfoption name="interfaces">eth0 lo</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>inetd</primary></indexterm>
-<indexterm><primary>smbclient</primary></indexterm>
-Another common cause of these two errors is having something already running on port <constant>139</constant>,
-such as Samba (&smbd; is running from <application>inetd</application> already) or Digital's Pathworks. Check
-your <filename>inetd.conf</filename> file before trying to start &smbd; as a daemon &smbmdash; it can avoid a
-lot of frustration!
-</para>
-
-<para>
-<indexterm><primary>subnet mask</primary></indexterm>
-<indexterm><primary>broadcast address</primary></indexterm>
-<indexterm><primary>log.nmbd</primary></indexterm>
-<indexterm><primary>network interface</primary></indexterm>
-<indexterm><primary>IP address</primary></indexterm>
-And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address
-settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask
-settings are correct and that Samba has correctly noted these in the <filename>log.nmbd</filename> file.
-</para>
-
-</step>
-
-<step performance="required">
-
-<para>
-<indexterm><primary>nmblookup</primary></indexterm>
-Run the command <command>nmblookup -B BIGSERVER __SAMBA__</command>.
-You should get back the IP address of your Samba server.
-</para>
-
-<para>
-<indexterm><primary>inetd.conf</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>port 137</primary></indexterm>
-If you do not, then &nmbd; is incorrectly installed. Check your <filename>inetd.conf</filename>
-if you run it from there, or that the daemon is running and listening to UDP port 137.
-</para>
-
-<para>
-One common problem is that many inetd implementations can't take many
-parameters on the command line. If this is the case, then create a
-one-line script that contains the right parameters and run that from
-inetd.
-</para>
-
-</step>
-
-<step performance="required">
-
-<para>
-<indexterm><primary>nmblookup</primary></indexterm>
-Run the command <command>nmblookup -B ACLIENT `*'</command>.
-</para>
-
-<para>
-You should get the PC's IP address back. If you do not, then the client
-software on the PC isn't installed correctly, or isn't started, or you
-got the name of the PC wrong.
-</para>
-
-<para>
-If ACLIENT does not resolve via DNS, then use the IP address of the
-client in the above test.
-</para>
-
-</step>
-
-<step performance="required">
-
-<para>
-Run the command <command>nmblookup -d 2 `*'</command>.
-</para>
-
-<para>
-This time we are trying the same as the previous test but are trying
-it via a broadcast to the default broadcast address. A number of
-NetBIOS/TCP/IP hosts on the network should respond, although Samba may
-not catch all of the responses in the short time it listens. You
-should see the <literal>got a positive name query response</literal>
-messages from several hosts.
-</para>
-
-<para>
-<indexterm><primary>nmblookup</primary></indexterm>
-If this does not give a result similar to the previous test, then nmblookup isn't correctly getting your
-broadcast address through its automatic mechanism. In this case you should experiment with the <smbconfoption
-name="interfaces"/> option in &smb.conf; to manually configure your IP address, broadcast, and netmask.
-</para>
-
-<para>
-If your PC and server aren't on the same subnet, then you will need to use the
-<option>-B</option> option to set the broadcast address to that of the PC's subnet.
-</para>
-
-<para>
-This test will probably fail if your subnet mask and broadcast address are
-not correct. (Refer to test 3 notes above).
-</para>
-
-</step>
-
-<step performance="required">
-
-
-<para>
-<indexterm><primary>smbclient</primary></indexterm>
-Run the command <command>smbclient //BIGSERVER/TMP</command>. You should
-then be prompted for a password. You should use the password of the account
-with which you are logged into the UNIX box. If you want to test with
-another account, then add the <option>-U accountname</option> option to the end of
-the command line &smbmdash; for example, <command>smbclient //bigserver/tmp -Ujohndoe</command>.
-</para>
-
-<note><para>
-It is possible to specify the password along with the username as follows:
-<command>smbclient //bigserver/tmp -Ujohndoe%secret</command>.
-</para></note>
-
-<para>
-Once you enter the password, you should get the <prompt>smb></prompt> prompt. If you
-do not, then look at the error message. If it says <quote><errorname>invalid network
-name,</errorname></quote> then the service <smbconfsection name="tmp"/> is not correctly set up in your &smb.conf;.
-</para>
-
-<para>
-If it says <quote><errorname>bad password,</errorname></quote> then the likely causes are:
-</para>
-
-<orderedlist>
-<listitem>
- <para>
- Password encryption is enabled by default, but you have not
- yet set a password for your samba user. Run
- <command>smbpasswd -a username</command>
- </para>
-</listitem>
-
-<listitem>
- <para>
- Your <smbconfoption name="valid users"/> configuration is incorrect.
- </para>
-</listitem>
-
-<listitem>
- <para>
- You have explicitly disabled encrypted passwords with
- <smbconfoption name="encrypt passwords">no</smbconfoption> have a mixed-case password.
- </para>
-</listitem>
-
-<listitem>
- <para>
- The <smbconfoption name="path"/> line in &smb.conf; is incorrect. Check it with &testparm;.
- </para>
-</listitem>
-
-</orderedlist>
-
-<para>
-<indexterm><primary>dir</primary></indexterm>
-<indexterm><primary>get</primary></indexterm>
-<indexterm><primary>put</primary></indexterm>
-<indexterm><primary>help command</primary></indexterm>
-Once connected, you should be able to use the commands <command>dir</command>, <command>get</command>,
-<command>put</command>, and so on. Type <command>help command</command> for instructions. You should
-especially check that the amount of free disk space shown is correct when you type <command>dir</command>.
-</para>
-
-</step>
-
-<step performance="required">
-
-<para>
-<indexterm><primary>net view</primary></indexterm>
-On the PC, type the command <command>net view \\BIGSERVER</command>. You will
-need to do this from within a DOS prompt window. You should get back a
-list of shares available on the server.
-</para>
-
-<para>
-<indexterm><primary>nmbd</primary></indexterm>
-If you get a message <literal>network name not found</literal> or similar error, then NetBIOS
-name resolution is not working. This is usually caused by a problem in <command>nmbd</command>.
-To overcome it, you could do one of the following (you only need to choose one of them):
-</para>
-
-<orderedlist>
-<listitem><para>
- Fix the &nmbd; installation.
-</para></listitem>
-
-<listitem><para>
- Add the IP address of BIGSERVER to the <command>wins server</command> box in the
- advanced TCP/IP setup on the PC.
-</para></listitem>
-
-<listitem><para>
- Enable Windows name resolution via DNS in the advanced section of the TCP/IP setup.
-</para></listitem>
-
-<listitem><para>
- Add BIGSERVER to your lmhosts file on the PC.
-</para></listitem>
-</orderedlist>
-
-<para>
-If you get a message <quote><errorname>invalid network name</errorname></quote> or
-<quote><errorname>bad password error,</errorname></quote> then apply the
-same fixes as for the <command>smbclient -L</command> test. In
-particular, make sure your <command>hosts allow</command> line is correct (see the man pages).
-</para>
-
-<para>
-Also, do not overlook that fact that when the workstation requests the
-connection to the Samba server, it will attempt to connect using the
-name with which you logged onto your Windows machine. You need to make
-sure that an account exists on your Samba server with that exact same
-name and password.
-</para>
-
-<para>
-If you get a message <quote><errorname>specified computer is not receiving requests</errorname></quote> or similar error,
-it probably means that the host is not contactable via TCP services.
-Check to see if the host is running TCP wrappers, and if so, add an entry in
-the <filename>hosts.allow</filename> file for your client (or subnet, and so on.)
-</para>
-
-</step>
-
-<step performance="required">
-
-<para>
-Run the command <command>net use x: \\BIGSERVER\TMP</command>. You should
-be prompted for a password, then you should get a <computeroutput>command completed
-successfully</computeroutput> message. If not, then your PC software is incorrectly
-installed or your &smb.conf; is incorrect. Make sure your <parameter>hosts allow</parameter>
-and other config lines in &smb.conf; are correct.
-</para>
-
-<para>
-By default, most clients only sends encrypted passwords
-and you have <smbconfoption name="encrypt passwords">no</smbconfoption> in &smb.conf;.
-Change this setting to `yes' to fix this.
-</para>
-
-</step>
-
-<step performance="required">
-
-<para>
-Run the command <command>nmblookup -M <parameter>testgroup</parameter></command> where
-<parameter>testgroup</parameter> is the name of the workgroup that your Samba server and
-Windows PCs belong to. You should get back the IP address of the
-master browser for that workgroup.
-</para>
-
-<para>
-If you do not, then the election process has failed. Wait a minute to
-see if it is just being slow, then try again. If it still fails after
-that, then look at the browsing options you have set in &smb.conf;. Make
-sure you have <smbconfoption name="preferred master">yes</smbconfoption> to ensure that
-an election is held at startup.
-</para>
-
-</step>
-
-<step performance="required">
-
-<para>
-From file manager, try to browse the server. Your Samba server should
-appear in the browse list of your local workgroup (or the one you
-specified in &smb.conf;). You should be able to double-click on the name
-of the server and get a list of shares. If you get the error message <quote>invalid password,</quote>
-your client may be refusing to browse a server that has no encrypted password
-capability. In this case make sure <smbconfoption name="encrypt passwords"/> is
-set to <quote>yes</quote> and repeat the steps in this gude.
-</para>
-
-</step>
-</procedure>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="domain-member">
-
-<chapterinfo>
- &author.jht;
- &author.jeremy;
- &author.jerry;
- &author.tridge;
- &author.jelmer;
- <author>&person.gd;<contrib>LDAP updates</contrib></author>
-</chapterinfo>
-
-<title>Domain Membership</title>
-
-<para>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>machine trust account</primary></indexterm>
-<indexterm><primary>domain security</primary></indexterm>
-Domain membership is a subject of vital concern. Samba must be able to
-participate as a member server in a Microsoft domain security context, and
-Samba must be capable of providing domain machine member trust accounts;
-otherwise it would not be able to offer a viable option for many users.
-</para>
-
-<para>
-<indexterm><primary>domain membership</primary></indexterm>
-<indexterm><primary>misinformation</primary></indexterm>
-This chapter covers background information pertaining to domain membership,
-the Samba configuration for it, and MS Windows client procedures for joining a
-domain. Why is this necessary? Because both are areas in which there exists
-within the current MS Windows networking world, and particularly in the
-UNIX/Linux networking and administration world, a considerable level of
-misinformation, incorrect understanding, and lack of knowledge. Hopefully
-this chapter will fill the voids.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>domain security</primary></indexterm>
-<indexterm><primary>single sign-on</primary></indexterm>
-<indexterm><primary>SSO</primary></indexterm>
-MS Windows workstations and servers that want to participate in domain security need to
-be made domain members. Participating in domain security is often called
-<emphasis>single sign-on</emphasis>, or <acronym>SSO</acronym> for short. This
-chapter describes the process that must be followed to make a workstation
-(or another server &smbmdash; be it an <application>MS Windows NT4/200x</application>
-server) or a Samba server a member of an MS Windows domain security context.
-</para>
-
-<para>
-<indexterm><primary>native member</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>domain control</primary></indexterm>
-<indexterm><primary>Server Type</primary><secondary>Domain Member</secondary></indexterm>
-Samba can join an MS Windows NT4-style domain as a native member server, an
-MS Windows Active Directory domain as a native member server, or a Samba domain
-control network. Domain membership has many advantages:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>SAM</primary></indexterm>
- MS Windows workstation users get the benefit of SSO.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>access rights</primary></indexterm>
- <indexterm><primary>file ownership</primary></indexterm>
- <indexterm><primary>access controls</primary></indexterm>
- <indexterm><primary>SAM</primary></indexterm>
- Domain user access rights and file ownership/access controls can be set
- from the single Domain Security Account Manager (SAM) database
- (works with domain member servers as well as with MS Windows workstations
- that are domain members).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>domain members</primary></indexterm>
- <indexterm><primary>network logon</primary></indexterm>
- Only <application>MS Windows NT4/200x/XP Professional</application>
- workstations that are domain members can use network logon facilities.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>domain member</primary></indexterm>
- <indexterm><primary>policy files</primary></indexterm>
- <indexterm><primary>NTConfig.POL</primary></indexterm>
- <indexterm><primary>desktop profiles</primary></indexterm>
- Domain member workstations can be better controlled through the use of
- policy files (<filename>NTConfig.POL</filename>) and desktop profiles.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>logon script</primary></indexterm>
- <indexterm><primary>transparent access</primary></indexterm>
- <indexterm><primary>application servers</primary></indexterm>
- Through the use of logon scripts, users can be given transparent access to network
- applications that run off application servers.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>user access management</primary></indexterm>
- <indexterm><primary>SAM</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- Network administrators gain better application and user access management
- abilities because there is no need to maintain user accounts on any network
- client or server other than the central domain database
- (either NT4/Samba SAM-style domain, NT4 domain that is backend-ed with an
- LDAP directory, or via an Active Directory infrastructure).
- </para></listitem>
-</itemizedlist>
-
-</sect1>
-
-<sect1 id="machine-trust-accounts">
-<title>MS Windows Workstation/Server Machine Trust Accounts</title>
-
-<para>
-<indexterm><primary>Machine Trust Accounts</primary></indexterm>
-<indexterm><primary>authenticate</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>rogue user</primary></indexterm>
-A Machine Trust Account is an account that is used to authenticate a client machine (rather than a user) to
-the domain controller server. In Windows terminology, this is known as a <quote>computer account.</quote> The
-purpose of the machine trust account is to prevent a rogue user and domain controller from colluding to gain
-access to a domain member workstation.
-</para>
-
-<para>
-<indexterm><primary>machine trust account</primary><secondary>password</secondary></indexterm>
-<indexterm><primary>shared secret</primary></indexterm>
-<indexterm><primary>unauthorized</primary></indexterm>
-<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
-<indexterm><primary>Windows 9x/Me/XP Home</primary></indexterm>
-The password of a Machine Trust Account acts as the shared secret for secure communication with the domain
-controller. This is a security feature to prevent an unauthorized machine with the same NetBIOS name from
-joining the domain, participating in domain security operations, and gaining access to domain user/group
-accounts. Windows NT/200x/XP Professional clients use machine trust accounts, but Windows 9x/Me/XP Home
-clients do not. Hence, a Windows 9x/Me/XP Home client is never a true member of a domain because it does not
-possess a Machine Trust Account, and, thus, has no shared secret with the domain controller.
-</para>
-
-<para>
-<indexterm><primary>Windows Registry</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>Machine Trust Account</primary></indexterm>
-A Windows NT4 PDC stores each Machine Trust Account in the Windows Registry.
-The introduction of MS Windows 2000 saw the introduction of Active Directory,
-the new repository for Machine Trust Accounts. A Samba PDC, however, stores
-each Machine Trust Account in two parts,
-as follows:
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>domain security account</primary></indexterm>
- <indexterm><primary>account information</primary></indexterm>
- <indexterm><primary>backend database</primary></indexterm>
- A domain security account (stored in the <smbconfoption name="passdb backend"/>) that has been configured in
- the &smb.conf; file. The precise nature of the account information that is stored depends on the type of
- backend database that has been chosen.
- </para>
-
- <para>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>UNIX login ID</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>LanMan</primary></indexterm>
- <indexterm><primary>NT-encrypted password</primary></indexterm>
- <indexterm><primary>UNIX user identifier</primary><see>UID</see></indexterm>
- The older format of this data is the <filename>smbpasswd</filename> database
- that contains the UNIX login ID, the UNIX user identifier (UID), and the
- LanMan and NT-encrypted passwords. There is also some other information in
- this file that we do not need to concern ourselves with here.
- </para>
-
- <para>
- <indexterm><primary>database</primary></indexterm>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>account controls</primary></indexterm>
- The two newer database types are called ldapsam and tdbsam. Both store considerably more data than the older
- <filename>smbpasswd</filename> file did. The extra information enables new user account controls to be
- implemented.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>UNIX account</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- A corresponding UNIX account, typically stored in <filename>/etc/passwd</filename>. Work is in progress to
- allow a simplified mode of operation that does not require UNIX user accounts, but this has not been a feature
- of the early releases of Samba, and is not currently planned for release either.
- </para></listitem>
-</itemizedlist>
-</para>
-
-<?latex \newpage ?>
-<para>
-<indexterm><primary>Machine Trust Accounts</primary><secondary>creating</secondary></indexterm>
-There are three ways to create Machine Trust Accounts:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>manual UNIX account creation</primary></indexterm>
- Manual creation from the UNIX/Linux command line. Here, both the Samba and
- corresponding UNIX account are created by hand.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Server Manager</primary></indexterm>
- <indexterm><primary>Nexus toolkit</primary></indexterm>
- Using the MS Windows NT4 Server Manager, either from an NT4 domain member
- server or using the Nexus toolkit available from the Microsoft Web site.
- This tool can be run from any MS Windows machine as long as the user is
- logged on as the administrator account.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>Machine Trust Account</primary></indexterm>
- <indexterm><primary>joined client</primary></indexterm>
- <quote>On-the-fly</quote> creation. The Samba Machine Trust Account is automatically
- created by Samba at the time the client is joined to the domain.
- (For security, this is the recommended method.) The corresponding UNIX
- account may be created automatically or manually.
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>enforcing</primary></indexterm>
-<indexterm><primary>machine trust account</primary><secondary>creation</secondary></indexterm>
-Neither MS Windows NT4/200x/XP Professional, nor Samba, provide any method for enforcing the method of machine
-trust account creation. This is a matter of the administrator's choice.
-</para>
-
-<sect2>
-<title>Manual Creation of Machine Trust Accounts</title>
-
-<para>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-<indexterm><primary>useradd</primary></indexterm>
-<indexterm><primary>vipw</primary></indexterm>
-The first step in manually creating a Machine Trust Account is to manually
-create the corresponding UNIX account in <filename>/etc/passwd</filename>.
-This can be done using <command>vipw</command> or another <quote>adduser</quote> command
-that is normally used to create new UNIX accounts. The following is an example for
-a Linux-based Samba server:
-<screen>
-&rootprompt;<userinput>/usr/sbin/useradd -g machines -d /var/lib/nobody \
- -c <replaceable>"machine nickname"</replaceable> \
- -s /bin/false <replaceable>machine_name</replaceable>$ </userinput>
-
-&rootprompt;<userinput>passwd -l <replaceable>machine_name</replaceable>$</userinput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>primary group</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>machine accounts</primary></indexterm>
-In the example above there is an existing system group <quote>machines</quote> which is used
-as the primary group for all machine accounts. In the following examples the <quote>machines</quote> group
-numeric GID is 100.
-</para>
-
-<para>
-<indexterm><primary>chpass</primary></indexterm>
-<indexterm><primary>BSD</primary></indexterm>
-On *BSD systems, this can be done using the <command>chpass</command> utility:
-<screen>
-&rootprompt;<userinput>chpass -a \
-'<replaceable>machine_name</replaceable>$:*:101:100::0:0:Windows <replaceable>machine_name</replaceable>:/dev/null:/sbin/nologin'</userinput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>$</primary></indexterm>
-<indexterm><primary>null shell</primary></indexterm>
-<indexterm><primary>home directory</primary></indexterm>
-The <filename>/etc/passwd</filename> entry will list the machine name
-with a <quote>$</quote> appended, and will not have a password, will have a null shell and no
-home directory. For example, a machine named <quote>doppy</quote> would have an
-<filename>/etc/passwd</filename> entry like this:
-<programlisting>
-doppy$:x:505:100:<replaceable>machine_nickname</replaceable>:/dev/null:/bin/false
-</programlisting>
-</para>
-
-<para>
-<indexterm><primary>machine_nickname</primary></indexterm>
-<indexterm><primary>machine_name</primary></indexterm>
-<indexterm><primary>Machine Trust Account</primary></indexterm>
-in which <replaceable>machine_nickname</replaceable> can be any
-descriptive name for the client, such as BasementComputer.
-<replaceable>machine_name</replaceable> absolutely must be the NetBIOS
-name of the client to be joined to the domain. The <quote>$</quote> must be
-appended to the NetBIOS name of the client or Samba will not recognize
-this as a Machine Trust Account.
-</para>
-
-<para>
-<indexterm><primary>UNIX account</primary></indexterm>
-<indexterm><primary>Samba account</primary></indexterm>
-<indexterm><primary>Machine Trust Account</primary><secondary>password</secondary></indexterm>
-Now that the corresponding UNIX account has been created, the next step is to create
-the Samba account for the client containing the well-known initial
-Machine Trust Account password. This can be done using the
-<command>smbpasswd</command> command
-as shown here:
-<screen>
-&rootprompt;<userinput>smbpasswd -a -m <replaceable>machine_name</replaceable></userinput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>machine_name</primary></indexterm>
-<indexterm><primary>NetBIOS name</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-where <replaceable>machine_name</replaceable> is the machine's NetBIOS
-name. The RID of the new machine account is generated from the UID of
-the corresponding UNIX account.
-</para>
-
-<warning>
-<title>Join the client to the domain immediately</title>
-
-<para>
-<indexterm><primary>Machine Trust Account</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>Server Manager</primary></indexterm>
-<indexterm><primary>changes password</primary></indexterm>
-<indexterm><primary>NetBIOS name</primary></indexterm>
-Manually creating a Machine Trust Account using this method is the
-equivalent of creating a Machine Trust Account on a Windows NT PDC using
-<indexterm><primary>Server Manager</primary></indexterm>
-the <application>Server Manager</application>. From the time at which the
-account is created to the time the client joins the domain and
-changes the password, your domain is vulnerable to an intruder joining
-your domain using a machine with the same NetBIOS name. A PDC inherently
-trusts members of the domain and will serve out a large degree of user
-information to such clients. You have been warned!
-</para>
-</warning>
-</sect2>
-
-<sect2>
-<title>Managing Domain Machine Accounts using NT4 Server Manager</title>
-
-<para>
-<indexterm><primary>machine trust accounts</primary></indexterm>
-<indexterm><primary>automatic account creation</primary></indexterm>
-<indexterm><primary>Server Manager</primary></indexterm>
-A working <smbconfoption name="add machine script"/> is essential
-for machine trust accounts to be automatically created. This applies no matter whether
-you use automatic account creation or the NT4 Domain Server Manager.
-</para>
-
-<para>
-<indexterm><primary>SRVTOOLS.EXE</primary></indexterm>
-<indexterm><primary>SrvMgr.exe</primary></indexterm>
-<indexterm><primary>UsrMgr.exe</primary></indexterm>
-<indexterm><primary>domain management tools</primary></indexterm>
-If the machine from which you are trying to manage the domain is an
-<application>MS Windows NT4 workstation or MS Windows 200x/XP Professional</application>,
-the tool of choice is the package called <command>SRVTOOLS.EXE</command>.
-When executed in the target directory it will unpack <command>SrvMgr.exe</command>
-and <command>UsrMgr.exe</command> (both are domain management tools for MS Windows NT4 workstation).
-</para>
-
-<para>
-<indexterm><primary>Nexus.exe</primary></indexterm>
-<indexterm><primary>Microsoft Windows 9x/Me</primary></indexterm>
-If your workstation is a <application>Microsoft Windows 9x/Me</application> family product,
- you should download the <command>Nexus.exe</command> package from the Microsoft Web site.
-When executed from the target directory, it will unpack the same tools but for use on
-this platform.
-</para>
-
-<para>
-Further information about these tools may be obtained from Knowledge Base articles
-<ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673">173673</ulink>, and
-<ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540">172540</ulink>
-</para>
-
-<para>
-<indexterm><primary>srvmgr.exe</primary></indexterm>
-<indexterm><primary>Server Manager for Domains</primary></indexterm>
-Launch the <command>srvmgr.exe</command> (Server Manager for Domains) and follow these steps:
-</para>
-
-<procedure>
-<title>Server Manager Account Machine Account Management</title>
- <step><para>
- From the menu select <guimenu>Computer</guimenu>.
- </para></step>
-
- <step><para>
- Click <guimenuitem>Select Domain</guimenuitem>.
- </para></step>
-
- <step><para>
- Click the name of the domain you wish to administer in the
- <guilabel>Select Domain</guilabel> panel and then click
- <guibutton>OK</guibutton>.
- </para></step>
-
- <step><para>
- Again from the menu select <guimenu>Computer</guimenu>.
- </para></step>
-
- <step><para>
- Select <guimenuitem>Add to Domain</guimenuitem>.
- </para></step>
-
- <step><para>
- In the dialog box, click the radio button to
- <guilabel>Add NT Workstation of Server</guilabel>, then
- enter the machine name in the field provided, and click the
- <guibutton>Add</guibutton> button.
- </para></step>
-</procedure>
-
-</sect2>
-
-<sect2>
-<title>On-the-Fly Creation of Machine Trust Accounts</title>
-
-<para>
-<indexterm><primary>Machine Trust Account</primary><secondary>creation</secondary></indexterm>
-The third (and recommended) way of creating Machine Trust Accounts is simply to allow the Samba server to
-create them as needed when the client is joined to the domain.
-</para>
-
-<para>
-<indexterm><primary>Machine Trust Account</primary><secondary>UNIX account</secondary></indexterm>
-<indexterm><primary>UNIX account</primary></indexterm>
-<indexterm><primary>add machine script</primary></indexterm>
-Since each Samba Machine Trust Account requires a corresponding UNIX account, a method
-for automatically creating the UNIX account is usually supplied; this requires configuration of the
-add machine script option in &smb.conf;. This method is not required; however, corresponding UNIX
-accounts may also be created manually.
-</para>
-
-
-<para>
-<indexterm><primary>useradd</primary></indexterm>
-<indexterm><primary>Red Hat Linux</primary></indexterm>
-Here is an example for a Red Hat Linux system:
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="add machine script">/usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u</smbconfoption>
-</smbconfblock>
-</para>
-
-</sect2>
-
-<sect2><title>Making an MS Windows Workstation or Server a Domain Member</title>
-
-<para>
-The procedure for making an MS Windows workstation or server a member of the domain varies
-with the version of Windows.
-</para>
-
-<sect3>
- <title>Windows 200x/XP Professional Client</title>
-
- <para>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>machine trust account</primary><secondary>create privilege</secondary></indexterm>
-<indexterm><primary>privileges</primary></indexterm>
-<indexterm><primary>root</primary></indexterm>
- When the user elects to make the client a domain member, Windows 200x prompts for
- an account and password that has privileges to create machine accounts in the domain.
- </para>
-
- <para>
- A Samba administrator account (i.e., a Samba account that has <literal>root</literal> privileges on the
- Samba server) must be entered here; the operation will fail if an ordinary user account is given.
- The necessary privilege can be assured by creating a Samba SAM account for <literal>root</literal> or
- by granting the <literal>SeMachineAccountPrivilege</literal> privilege to the user account.
- </para>
-
- <para>
-<indexterm><primary>administrator account</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
- For security reasons, the password for this administrator account should be set
- to a password that is other than that used for the root user in <filename>/etc/passwd</filename>.
- </para>
-
- <para>
-<indexterm><primary>account</primary></indexterm>
-<indexterm><primary>create domain member</primary></indexterm>
-<indexterm><primary>root</primary></indexterm>
-<indexterm><primary>map</primary></indexterm>
- The name of the account that is used to create domain member machine trust accounts can be
- anything the network administrator may choose. If it is other than <constant>root</constant>,
- then this is easily mapped to <constant>root</constant> in the file named in the &smb.conf; parameter
- <smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>.
- </para>
-
- <para>
-<indexterm><primary>administrator account</primary></indexterm>
-<indexterm><primary>encryption key</primary></indexterm>
-<indexterm><primary>machine trust account</primary></indexterm>
- The session key of the Samba administrator account acts as an encryption key for setting the password of the machine trust
- account. The Machine Trust Account will be created on-the-fly, or updated if it already exists.
- </para>
-</sect3>
-
-<sect3>
- <title>Windows NT4 Client</title>
-
- <para>
-<indexterm><primary>Machine Trust Account</primary></indexterm>
-<indexterm><primary>Create a Computer Account</primary></indexterm>
-<indexterm><primary>join the machine</primary></indexterm>
- If the Machine Trust Account was created manually, on the
- Identification Changes menu enter the domain name, but do not
- check the box <guilabel>Create a Computer Account in the Domain</guilabel>.
- In this case, the existing Machine Trust Account is used to join the machine
- to the domain.
- </para>
-
- <para>
-<indexterm><primary>Machine Trust Account</primary></indexterm>
-<indexterm><primary>on the fly</primary></indexterm>
-<indexterm><primary>Computer Account</primary></indexterm>
-<indexterm><primary>administrator account</primary></indexterm>
- If the Machine Trust Account is to be created on the fly, on the Identification Changes menu enter the domain
- name and check the box <guilabel>Create a Computer Account in the Domain</guilabel>. In this case, joining
- the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrator account when
- prompted).
- </para>
-</sect3>
-
-<sect3>
- <title>Samba Client</title>
-
- <para>
-<indexterm><primary></primary></indexterm>
- Joining a Samba client to a domain is documented in <link linkend="domain-member-server">the next section</link>.
- </para>
-</sect3>
-
-</sect2>
-</sect1>
-
-<sect1 id="domain-member-server">
-<title>Domain Member Server</title>
-
-<para>
-<indexterm><primary>domain security</primary></indexterm>
-<indexterm><primary>security context</primary></indexterm>
-<indexterm><primary>authentication regime</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-This mode of server operation involves the Samba machine being made a member
-of a domain security context. This means by definition that all user
-authentication will be done from a centrally defined authentication regime.
-The authentication regime may come from an NT3/4-style (old domain technology)
-server, or it may be provided from an Active Directory server (ADS) running on
-MS Windows 2000 or later.
-</para>
-
-<para>
-<emphasis>
-<indexterm><primary>authentication</primary><secondary>backend</secondary></indexterm>
-<indexterm><primary>distributed directory</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>iPlanet</primary></indexterm>
-<indexterm><primary>Sun</primary></indexterm>
-<indexterm><primary>Novell</primary></indexterm>
-<indexterm><primary>e-Directory</primary></indexterm>
-Of course it should be clear that the authentication backend itself could be
-from any distributed directory architecture server that is supported by Samba.
-This can be LDAP (from OpenLDAP), or Sun's iPlanet, or Novell e-Directory
-Server, and so on.
-</emphasis>
-</para>
-
-<note><para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>identity management</primary></indexterm>
-<indexterm><primary>machine authentication</primary></indexterm>
-When Samba is configured to use an LDAP or other identity management and/or
-directory service, it is Samba that continues to perform user and machine
-authentication. It should be noted that the LDAP server does not perform
-authentication handling in place of what Samba is designed to do.
-</para></note>
-
-<para>
-<indexterm><primary>create a domain machine account</primary></indexterm>
-<indexterm><primary>domain member server</primary></indexterm>
-<indexterm><primary>join the domain</primary></indexterm>
-Please refer to <link linkend="samba-pdc">Domain Control</link>, for more information regarding
-how to create a domain machine account for a domain member server as well as for
-information on how to enable the Samba domain member machine to join the domain
-and be fully trusted by it.
-</para>
-
-<sect2>
-<title>Joining an NT4-type Domain with Samba</title>
-
-<para><link linkend="assumptions">Assumptions</link> lists names that are used in the remainder of this chapter.</para>
-
-<table frame="all" id="assumptions"><title>Assumptions</title>
- <tgroup cols="2">
- <colspec align="right"/>
- <colspec align="left"/>
- <tbody>
- <row>
- <entry>Samba DMS NetBIOS name:</entry><entry>SERV1</entry>
- </row>
- <row>
- <entry>Windows 200x/NT domain name:</entry><entry>&example.workgroup;</entry>
- </row>
- <row>
- <entry>Domain's PDC NetBIOS name:</entry><entry>DOMPDC</entry>
- </row>
- <row>
- <entry>Domain's BDC NetBIOS names:</entry><entry>DOMBDC1 and DOMBDC2</entry>
- </row>
- </tbody>
- </tgroup>
-</table>
-
-<para>
-<indexterm><primary></primary></indexterm>
-First, you must edit your &smb.conf; file to tell Samba it should now use domain security.
-</para>
-
-<para>
-<indexterm><primary>security = user</primary></indexterm>
-<indexterm><primary>standalone server</primary></indexterm>
-<indexterm><primary>domain member server</primary></indexterm>
-<indexterm><primary>domain security</primary></indexterm>
-Change (or add) your <smbconfoption name="security"/> line in the [global] section
-of your &smb.conf; to read:
-<smbconfblock>
-<smbconfoption name="security">domain</smbconfoption>
-</smbconfblock>
-Note that if the parameter <parameter>security = user</parameter> is used, this machine would function as a
-standalone server and not as a domain member server. Domain security mode causes Samba to work within the
-domain security context.
-</para>
-
-<para>
-Next change the <smbconfoption name="workgroup"/> line in the <smbconfsection name="[global]"/>
-section to read:
-<smbconfblock>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-</smbconfblock>
-This is the name of the domain we are joining.
-</para>
-
-<para>
-<indexterm><primary>authenticate</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-You must also have the parameter <smbconfoption name="encrypt passwords"/>
-set to <constant>yes</constant> in order for your users to authenticate to the NT PDC.
-This is the default setting if this parameter is not specified. There is no need to specify this
-parameter, but if it is specified in the &smb.conf; file, it must be set to <constant>Yes</constant>.
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>authenticate users</primary></indexterm>
-<indexterm><primary>domain controllers</primary></indexterm>
-Finally, add (or modify) a <smbconfoption name="password server"/> line in the [global]
-section to read:
-<smbconfblock>
-<smbconfoption name="password server">DOMPDC DOMBDC1 DOMBDC2</smbconfoption>
-</smbconfblock>
-These are the PDC and BDCs Samba
-will attempt to contact in order to authenticate users. Samba will
-try to contact each of these servers in order, so you may want to
-rearrange this list in order to spread out the authentication load
-among Domain Controllers.
-</para>
-
-<para>
-<indexterm><primary>list of domain controllers</primary></indexterm>
-<indexterm><primary>mechanism</primary></indexterm>
-<indexterm><primary>broadcast-based name resolution</primary></indexterm>
-<indexterm><primary>DNS name resolution</primary></indexterm>
-Alternatively, if you want smbd to determine automatically the list of domain controllers to use for
-authentication, you may set this line to be:
-<smbconfblock>
-<smbconfoption name="password server">*</smbconfoption>
-</smbconfblock>
-<indexterm><primary>WINS</primary></indexterm>
-This method allows Samba to use exactly the same mechanism that NT does. The
-method either uses broadcast-based name resolution, performs a WINS database
-lookup in order to find a domain controller against which to authenticate,
-or locates the domain controller using DNS name resolution.
-</para>
-
-<para>
-To join the domain, run this command:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
-<screen>
-&rootprompt;<userinput>net rpc join -S DOMPDC -U<replaceable>Administrator%password</replaceable></userinput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>NetBIOS name</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>WINS lookup</primary></indexterm>
-<indexterm><primary>NetBIOS broadcast</primary></indexterm>
-If the <option>-S DOMPDC</option> argument is not given, the domain name will be obtained from &smb.conf; and
-the NetBIOS name of the PDC will be obtained either using a WINS lookup or via NetBIOS broadcast based name
-look up.
-</para>
-
-<para>
-<indexterm><primary>joining the domain</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>Administrator%password</primary></indexterm>
-<indexterm><primary>Joined domain</primary></indexterm>
-The machine is joining the domain DOM, and the PDC for that domain (the only machine
-that has write access to the domain SAM database) is DOMPDC; therefore, use the <option>-S</option>
-option. The <replaceable>Administrator%password</replaceable> is the login name and
-password for an account that has the necessary privilege to add machines to the
-domain. If this is successful, you will see the following message in your terminal window.
-Where the older NT4-style domain architecture is used:
-<screen>
-<computeroutput>Joined domain DOM.</computeroutput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>join the ADS domain</primary></indexterm>
-Where Active Directory is used, the command used to join the ADS domain is:
-<screen>
-&rootprompt; net ads join -U<replaceable>Administrator%password</replaceable>
-</screen>
-And the following output is indicative of a successful outcome:
-<screen>
-<computeroutput>Joined SERV1 to realm MYREALM.</computeroutput>
-</screen>
-</para>
-
-<para>
-Refer to the <command>net</command> man page and to <link linkend="NetCommand">the chapter on remote
-administration</link> for further information.
-</para>
-
-<para>
-<indexterm><primary>join the domain</primary></indexterm>
-<indexterm><primary>create machine trust account</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-This process joins the server to the domain without separately having to create the machine
-trust account on the PDC beforehand.
-</para>
-
-<para>
-<indexterm><primary>machine account password</primary><secondary>change protocol</secondary></indexterm>
-<indexterm><primary>random machine account password</primary></indexterm>
-<indexterm><primary>/usr/local/samba/private/secrets.tdb</primary></indexterm>
-<indexterm><primary>/etc/samba/secrets.tdb</primary></indexterm>
-This command goes through the machine account password change protocol, then writes the new (random) machine
-account password for this Samba server into a file in the same directory in which a smbpasswd file would be
-normally stored. The trust account information that is needed by the DMS is written into the file
-<filename>/usr/local/samba/private/secrets.tdb</filename> or <filename>/etc/samba/secrets.tdb</filename>.
-</para>
-
-<para>
-<indexterm><primary>domain-level security</primary></indexterm>
-<indexterm><primary>shadow password file</primary></indexterm>
-This file is created and owned by root and is not readable by any other user. It is
-the key to the domain-level security for your system and should be treated as carefully
-as a shadow password file.
-</para>
-
-<para>
-<indexterm><primary>Samba daemons</primary></indexterm>
-<indexterm><primary>distribution</primary></indexterm>
-<indexterm><primary>/etc/init.d/samba</primary></indexterm>
-Finally, restart your Samba daemons and get ready for clients to begin using domain
-security. The way you can restart your Samba daemons depends on your distribution,
-but in most cases the following will suffice:
-<screen>
-&rootprompt;/etc/init.d/samba restart
-</screen>
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="ads-member">
-<title>Samba ADS Domain Membership</title>
-
-<para>
-<indexterm significance="preferred"><primary>Active Directory</primary></indexterm>
-<indexterm significance="preferred"><primary>ADS</primary><see>Active Directory</see></indexterm>
-<indexterm><primary>KDC</primary></indexterm>
-<indexterm><primary>Kerberos</primary></indexterm>
-This is a rough guide to setting up Samba with Kerberos authentication against a
-Windows 200x KDC. A familiarity with Kerberos is assumed.
-</para>
-
-<sect2>
-<title>Configure &smb.conf;</title>
-
-<para>
-You must use at least the following three options in &smb.conf;:
-</para>
-
-<smbconfblock>
-<smbconfoption name="realm">your.kerberos.REALM</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfcomment>The following parameter need only be specified if present.</smbconfcomment>
-<smbconfcomment>The default setting if not present is Yes.</smbconfcomment>
-<smbconfoption name="encrypt passwords">yes</smbconfoption>
-</smbconfblock>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>realm</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>ADS DC</primary></indexterm>
-<indexterm><primary>password server</primary></indexterm>
-In case samba cannot correctly identify the appropriate ADS server using the realm name, use the
-<smbconfoption name="password server"/> option in &smb.conf;:
-<smbconfblock>
-<smbconfoption name="password server">your.kerberos.server</smbconfoption>
-</smbconfblock>
-The most common reason for which Samba may not be able to locate the ADS domain controller is a consequence of
-sites maintaining some DNS servers on UNIX systems without regard for the DNS requirements of the ADS
-infrastructure. There is no harm in specifying a preferred ADS domain controller using the <parameter>password
-server</parameter>.
-</para>
-
-<note><para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>authenticated</primary></indexterm>
-You do <emphasis>not</emphasis> need an smbpasswd file, and older clients will be authenticated as
-if <smbconfoption name="security">domain</smbconfoption>, although it will not do any harm and
-allows you to have local users not in the domain.
-</para></note>
-
-</sect2>
-
-<sect2>
-<title>Configure <filename>/etc/krb5.conf</filename></title>
-
-<para>
-<indexterm><primary>/etc/krb5.conf</primary></indexterm>
-<indexterm><primary>Kerberos</primary><secondary>/etc/krb5.conf</secondary></indexterm>
-<indexterm><primary>MIT</primary></indexterm>
-<indexterm><primary>Heimdal</primary></indexterm>
-With both MIT and Heimdal Kerberos, it is unnecessary to configure the <filename>/etc/krb5.conf</filename>,
-and it may be detrimental.
-</para>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>SRV records</primary></indexterm>
-<indexterm><primary>DNS zon</primary></indexterm>
-<indexterm><primary>KDC</primary></indexterm>
-<indexterm><primary>_kerberos.REALM.NAME</primary></indexterm>
-Microsoft ADS automatically create SRV records in the DNS zone
-<parameter>_kerberos._tcp.REALM.NAME</parameter> for each KDC in the realm. This is part
-of the installation and configuration process used to create an Active Directory domain.
-A KDC is a Kerberos Key Distribution Center and forms an integral part of the Microsoft
-active directory infrastructure.
-</para>
-
-<para>
-<indexterm><primary>kinit</primary></indexterm>
-<indexterm><primary>DES-CBC-MD5</primary></indexterm>
-<indexterm><primary>DES-CBC-CRC</primary></indexterm>
-<indexterm><primary>encryption types</primary></indexterm>
-<indexterm><primary>kerberos</primary></indexterm>
-<indexterm><primary>Windows 2000</primary></indexterm>
-UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows
-2000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the
-Microsoft Windows 2000 Kerberos <ulink
-url="http://www.microsoft.com/windows2000/techinfo/planning/security/kerbsteps.asp">Interoperability</ulink>
-guide. Another very useful document that may be referred to for general information regarding Kerberos
-interoperability is <ulink url="http://www.ietf.org/rfc/rfc1510.txt?number=1510">RFC1510</ulink>. This RFC
-explains much of the magic behind the operation of Kerberos.
-</para>
-
-<para>
-<indexterm><primary>MIT</primary></indexterm>
-<indexterm><primary>KRB5</primary></indexterm>
-<indexterm><primary>SRV records</primary></indexterm>
-<indexterm><primary>krb5.conf</primary></indexterm>
-<indexterm><primary>DNS lookup</primary></indexterm>
-<indexterm><primary>libraries</primary></indexterm>
-MIT's, as well as Heimdal's, recent KRB5 libraries default to checking for SRV records, so they will
-automatically find the KDCs. In addition, <filename>krb5.conf</filename> only allows specifying
-a single KDC, even there if there may be more than one. Using the DNS lookup allows the KRB5
-libraries to use whichever KDCs are available.
-</para>
-
-<para>
-<indexterm><primary>krb5.conf</primary></indexterm>
-When manually configuring <filename>krb5.conf</filename>, the minimal configuration is:
-<screen>
-[libdefaults]
- default_realm = YOUR.KERBEROS.REALM
- dns_lookup_kdc = true
-
-[domain_realms]
- .kerberos.server = YOUR.KERBEROS.REALM
-</screen>
-</para>
-
-<para>
-If you must specify the KDC directly, the minimal configuration is:
-<screen>
-[libdefaults]
- default_realm = YOUR.KERBEROS.REALM
-
-[realms]
- YOUR.KERBEROS.REALM = {
- kdc = your.kerberos.server
- }
-
-[domain_realms]
- .kerberos.server = YOUR.KERBEROS.REALM
-</screen>
-</para>
-
-<para>
-<indexterm><primary>KDC</primary></indexterm>
-<indexterm><primary>kinit</primary></indexterm>
-Test your config by doing a <userinput>kinit
-<replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput> and
-making sure that your password is accepted by the Win2000 KDC.
-</para>
-
-<note><para>
-<indexterm><primary>realm</primary></indexterm>
-<indexterm><primary>uppercase</primary></indexterm>
-<indexterm><primary>KDC</primary></indexterm>
-The realm must be in uppercase or you will get a <quote><errorname>Cannot find KDC for
-requested realm while getting initial credentials</errorname></quote> error (Kerberos
-is case-sensitive!).
-</para></note>
-
-<note><para>
-<indexterm><primary>synchronize</primary></indexterm>
-<indexterm><primary>credentials</primary></indexterm>
-<indexterm><primary>time difference</primary></indexterm>
-<indexterm><primary>clock skew</primary></indexterm>
-Time between the two servers must be synchronized. You will get a <quote><errorname>kinit(v5): Clock skew too
-great while getting initial credentials</errorname></quote> if the time difference (clock skew) is more than five minutes.
-</para></note>
-
-<para>
-<indexterm><primary>clock skew</primary></indexterm>
-<indexterm><primary>Kerberos</primary></indexterm>
-Clock skew limits are configurable in the Kerberos protocols. The default setting is five minutes.
-</para>
-
-<para>
-<indexterm><primary>Kerberos</primary></indexterm>
-<indexterm><primary>Create the Computer Account</primary></indexterm>
-<indexterm><primary>Testing Server Setup</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-If all you want is Kerberos support in &smbclient;, then you can skip directly to <link
-linkend="ads-test-smbclient">Testing with &smbclient;</link> now. <link
-linkend="ads-create-machine-account">Create the Computer Account</link> and <link
-linkend="ads-test-server">Testing Server Setup</link> are needed only if you want Kerberos support for &smbd;
-and &winbindd;.
-</para>
-
-</sect2>
-
-<sect2 id="ads-create-machine-account">
-<title>Create the Computer Account</title>
-
-<para>
-<indexterm><primary>write permission</primary></indexterm>
-<indexterm><primary>Samba private directory</primary></indexterm>
-<indexterm><primary>Administrator account</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-As a user who has write permission on the Samba private directory (usually root), run:
-<screen>
-&rootprompt; <userinput>net ads join -U Administrator%password</userinput>
-</screen>
-The Administrator account can be any account that has been designated in the ADS domain security settings with
-permission to add machines to the ADS domain. It is, of course, a good idea to use an account other than Administrator.
-On the UNIX/Linux system, this command must be executed by an account that has UID=0 (root).
-</para>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>machine trust account</primary></indexterm>
-<indexterm><primary>organizational unit</primary></indexterm>
-<indexterm><primary>ADS manager</primary></indexterm>
-<indexterm><primary>kinit</primary></indexterm>
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
-When making a Windows client a member of an ADS domain within a complex organization, you
-may want to create the machine trust account within a particular organizational unit. Samba permits
-this to be done using the following syntax:
-<screen>
-&rootprompt; <userinput>kinit Administrator@your.kerberos.REALM</userinput>
-&rootprompt; <userinput>net ads join createcomputer="organizational_unit"</userinput>
-</screen>
-Your ADS manager will be able to advise what should be specified for the "organizational_unit" parameter.
-</para>
-
-<para>
-<indexterm><primary>organizational directory</primary></indexterm>
-<indexterm><primary>machine trust account</primary></indexterm>
-<indexterm><primary>container</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-For example, you may want to create the machine trust account in a container called <quote>Servers</quote>
-under the organizational directory <quote>Computers/BusinessUnit/Department,</quote> like this:
-<screen>
-&rootprompt; <userinput>net ads join "Computers/BusinessUnit/Department/Servers"</userinput>
-</screen>
-This command will place the Samba server machine trust account in the container
-<literal>Computers/BusinessUnit/Department/Servers</literal>. The container should exist in the ADS directory
-before executing this command. Please note that forward slashes must be used, because backslashes are both
-valid characters in an OU name and used as escapes for other characters. If you need a backslash in an OU
-name, it may need to be quadrupled to pass through the shell escape and ldap escape.
-</para>
-
-<sect3>
-<title>Possible Errors</title>
-
-<para>
-<variablelist>
- <varlistentry><term><errorname>ADS support not compiled in</errorname></term>
- <listitem><para>
- <indexterm><primary>config.cache</primary></indexterm>
- <indexterm><primary>Kerberos</primary></indexterm>
- <indexterm><primary>headers files</primary></indexterm>
- Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the
- Kerberos libraries and headers files are installed.
- </para></listitem></varlistentry>
-
- <varlistentry><term><errorname>net ads join prompts for user name</errorname></term>
- <listitem><para>
- <indexterm><primary>kinit</primary></indexterm>
- <indexterm><primary>rights</primary></indexterm>
- You need to login to the domain using <userinput>kinit
- <replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput>.
- <replaceable>USERNAME</replaceable> must be a user who has rights to add a machine to the domain.
- </para></listitem></varlistentry>
-</variablelist>
-</para>
-
-</sect3>
-
-</sect2>
-
-<sect2 id="ads-test-server">
-<title>Testing Server Setup</title>
-
-<para>
-<indexterm><primary>successful join</primary></indexterm>
-<indexterm><primary>computer account</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-If the join was successful, you will see a new computer account with the
-NetBIOS name of your Samba server in Active Directory (in the <quote>Computers</quote>
-folder under Users and Computers.
-</para>
-
-<para>
-<indexterm><primary>Windows 2000</primary></indexterm>
-<indexterm><primary>net</primary><secondary>use</secondary></indexterm>
-<indexterm><primary>DES-CBC-MD5</primary></indexterm>
-On a Windows 2000 client, try <userinput>net use * \\server\share</userinput>. It should be possible
-to login with Kerberos without needing to know a password. If this fails, then run
-<userinput>klist tickets</userinput>. Did you get a ticket for the server? Does it have
-an encryption type of DES-CBC-MD5?
-</para>
-
-<note><para>
-<indexterm><primary>DES-CBC-MD5</primary></indexterm>
-<indexterm><primary>ARCFOUR-HMAC-MD5</primary></indexterm>
-<indexterm><primary>encoding</primary></indexterm>
-Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding.
-</para></note>
-
-</sect2>
-
-<sect2 id="ads-test-smbclient">
-<title>Testing with &smbclient;</title>
-
-<para>
-<indexterm><primary>smbclient</primary></indexterm>
-<indexterm><primary>Kerberos</primary></indexterm>
-<indexterm><primary>Kerberos authentication</primary></indexterm>
-On your Samba server try to login to a Windows 2000 server or your Samba
-server using &smbclient; and Kerberos. Use &smbclient; as usual, but
-specify the <option>-k</option> option to choose Kerberos authentication.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Sharing User ID Mappings between Samba Domain Members</title>
-
-<para>
-<indexterm><primary>maps UNIX users and groups</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs).
-These mappings are done by the <parameter>idmap</parameter> subsystem of Samba.
-</para>
-
-<para>
-<indexterm><primary>mappings</primary></indexterm>
-<indexterm><primary>CIFS</primary></indexterm>
-<indexterm><primary>NFS</primary></indexterm>
-In some cases it is useful to share these mappings between Samba domain members,
-so <emphasis>name->id</emphasis> mapping is identical on all machines.
-This may be needed in particular when sharing files over both CIFS and NFS.
-</para>
-
-<para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>ldap idmap suffix</primary></indexterm>
-To use the <emphasis>LDAP</emphasis> <parameter>ldap idmap suffix</parameter>, set:
-</para>
-
-<smbconfblock>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-</smbconfblock>
-
-<para>
-See the &smb.conf; man page entry for the <smbconfoption name="ldap idmap suffix"></smbconfoption>
-parameter for further information.
-</para>
-
-<para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>LDAP administrative password</primary></indexterm>
-<indexterm><primary>secrets.tdb</primary></indexterm>
-Do not forget to specify also the <smbconfoption name="ldap admin dn"/>
-and to make certain to set the LDAP administrative password into the <filename>secrets.tdb</filename> using:
-<screen>
-&rootprompt; smbpasswd -w ldap-admin-password
-</screen>
-In place of <literal>ldap-admin-password</literal>, substitute the LDAP administration password for your
-system.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>machine trust accounts</primary></indexterm>
-In the process of adding/deleting/re-adding domain member machine trust accounts, there are
-many traps for the unwary player and many <quote>little</quote> things that can go wrong.
-It is particularly interesting how often subscribers on the Samba mailing list have concluded
-after repeated failed attempts to add a machine account that it is necessary to <quote>reinstall</quote>
-MS Windows on the machine. In truth, it is seldom necessary to reinstall because of this type
-of problem. The real solution is often quite simple, and with an understanding of how MS Windows
-networking functions, it is easy to overcome.
-</para>
-
-<sect2>
-<title>Cannot Add Machine Back to Domain</title>
-
-<para>
-<indexterm><primary>machine trust account</primary></indexterm>
-<indexterm><primary>already exists</primary></indexterm>
-<quote>A Windows workstation was reinstalled. The original domain machine trust
-account was deleted and added immediately. The workstation will not join the domain if I use
-the same machine name. Attempts to add the machine fail with a message that the machine already
-exists on the network &smbmdash; I know it does not. Why is this failing?</quote>
-</para>
-
-<para>
-<indexterm><primary>NetBIOS name cache</primary></indexterm>
-<indexterm><primary>nbtstat</primary></indexterm>
-The original name is still in the NetBIOS name cache and must expire after machine account
-deletion before adding that same name as a domain member again. The best advice is to delete
-the old account and then add the machine with a new name. Alternately, the name cache can be flushed and
-reloaded with current data using the <command>nbtstat</command> command on the Windows client:
-<screen>
-&dosprompt; nbtstat -R
-</screen>
-</para>
-
-</sect2>
-
-<sect2>
-<title>Adding Machine to Domain Fails</title>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>fails</primary></indexterm>
-<quote>Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a
-message that says, <errorname>"The machine could not be added at this time, there is a network problem.
-Please try again later."</errorname> Why?</quote>
-</para>
-
-<para>
-<indexterm><primary>check logs</primary></indexterm>
-You should check that there is an <smbconfoption name="add machine script"/> in your &smb.conf;
-file. If there is not, please add one that is appropriate for your OS platform. If a script
-has been defined, you will need to debug its operation. Increase the <smbconfoption name="log level"></smbconfoption>
-in the &smb.conf; file to level 10, then try to rejoin the domain. Check the logs to see which
-operation is failing.
-</para>
-
-<para>
-Possible causes include:
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>script</primary></indexterm>
-<indexterm><primary>path specified</primary></indexterm>
- The script does not actually exist, or could not be located in the path specified.
- </para>
-
- <para>
-<indexterm><primary>UNIX system account</primary></indexterm>
-<indexterm><primary>Samba SAM account</primary></indexterm>
- <emphasis>Corrective action:</emphasis> Fix it. Make sure when run manually
- that the script will add both the UNIX system account and the Samba SAM account.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>UNIX system account</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
- The machine could not be added to the UNIX system accounts file <filename>/etc/passwd</filename>.
- </para>
-
- <para>
-<indexterm><primary>legal UNIX system account name</primary></indexterm>
-<indexterm><primary>uppercase</primary></indexterm>
- <emphasis>Corrective action:</emphasis> Check that the machine name is a legal UNIX
- system account name. If the UNIX utility <command>useradd</command> is called,
- then make sure that the machine name you are trying to add can be added using this
- tool. <command>Useradd</command> on some systems will not allow any uppercase characters
- nor will it allow spaces in the name.
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>backend database</primary></indexterm>
-<indexterm><primary>UNIX system account</primary></indexterm>
-<indexterm><primary>Samba backend database</primary></indexterm>
-The <smbconfoption name="add machine script"/> does not create the
-machine account in the Samba backend database; it is there only to create a UNIX system
-account to which the Samba backend database account can be mapped.
-</para>
-
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="FastStart">
-<chapterinfo>
- &author.jht;
-</chapterinfo>
-
-<title>Fast Start: Cure for Impatience</title>
-
-<para>
-When we first asked for suggestions for inclusion in the Samba HOWTO documentation,
-someone wrote asking for example configurations &smbmdash; and lots of them. That is remarkably
-difficult to do without losing a lot of value that can be derived from presenting
-many extracts from working systems. That is what the rest of this document does.
-It does so with extensive descriptions of the configuration possibilities within the
-context of the chapter that covers it. We hope that this chapter is the medicine
-that has been requested.
-</para>
-
-<para>
-The information in this chapter is very sparse compared with the book <quote>Samba-3 by Example</quote>
-that was written after the original version of this book was nearly complete. <quote>Samba-3 by Example</quote>
-was the result of feedback from reviewers during the final copy editing of the first edition. It
-was interesting to see that reader feedback mirrored that given by the original reviewers.
-In any case, a month and a half was spent in doing basic research to better understand what
-new as well as experienced network administrators would best benefit from. The book <quote>Samba-3 by Example</quote>
-is the result of that research. What is presented in the few pages of this book is covered
-far more comprehensively in the second edition of <quote>Samba-3 by Example</quote>. The second edition
-of both books will be released at the same time.
-</para>
-
-<para>
-So in summary, the book <quote>The Official Samba-3 HOWTO & Reference Guide</quote> is intended
-as the equivalent of an auto mechanic's repair guide. The book <quote>Samba-3 by Example</quote> is the
-equivalent of the driver's guide that explains how to drive the car. If you want complete network
-configuration examples, go to <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample.pdf">Samba-3 by
-Example</ulink>.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-Samba needs very little configuration to create a basic working system.
-In this chapter we progress from the simple to the complex, for each providing
-all steps and configuration file changes needed to make each work. Please note
-that a comprehensively configured system will likely employ additional smart
-features. These additional features are covered in the remainder of this document.
-</para>
-
-<para>
-The examples used here have been obtained from a number of people who made
-requests for example configurations. All identities have been obscured to protect
-the guilty, and any resemblance to unreal nonexistent sites is deliberate.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Description of Example Sites</title>
-
-<para>
-In the first set of configuration examples we consider the case of exceptionally simple system requirements.
-There is a real temptation to make something that should require little effort much too complex.
-</para>
-
-<para>
-<link linkend="anon-ro"></link> documents the type of server that might be sufficient to serve CD-ROM images,
-or reference document files for network client use. This configuration is also discussed in <link
-linkend="StandAloneServer"></link>, <link linkend="RefDocServer"></link>. The purpose for this configuration
-is to provide a shared volume that is read-only that anyone, even guests, can access.
-</para>
-
-<para>
-The second example shows a minimal configuration for a print server that anyone can print to as long as they
-have the correct printer drivers installed on their computer. This is a mirror of the system described in
-<link linkend="StandAloneServer"></link>, <link linkend="SimplePrintServer"></link>.
-</para>
-
-<para>
-The next example is of a secure office file and print server that will be accessible only to users who have an
-account on the system. This server is meant to closely resemble a workgroup file and print server, but has to
-be more secure than an anonymous access machine. This type of system will typically suit the needs of a small
-office. The server provides no network logon facilities, offers no domain control; instead it is just a
-network-attached storage (NAS) device and a print server.
-</para>
-
-<para>
-The later example consider more complex systems that will either integrate into existing MS Windows networks
-or replace them entirely. These cover domain member servers as well as Samba domain control (PDC/BDC) and
-finally describes in detail a large distributed network with branch offices in remote locations.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Worked Examples</title>
-
-<para>
-The configuration examples are designed to cover everything necessary to get Samba
-running. They do not cover basic operating system platform configuration, which is
-clearly beyond the scope of this text.
-</para>
-
-<para>
-It is also assumed that Samba has been correctly installed, either by way of installation
-of the packages that are provided by the operating system vendor or through other means.
-</para>
-
- <sect2>
- <title>Standalone Server</title>
-
- <para>
- <indexterm><primary>Server Type</primary><secondary>Stand-alone</secondary></indexterm>
- A standalone server implies no more than the fact that it is not a domain controller
- and it does not participate in domain control. It can be a simple, workgroup-like
- server, or it can be a complex server that is a member of a domain security context.
- </para>
-
- <para>
- As the examples are developed, every attempt is made to progress the system toward greater capability, just as
- one might expect would happen in a real business office as that office grows in size and its needs change.
- </para>
-
- <sect3 id="anon-ro">
- <title>Anonymous Read-Only Document Server</title>
-
- <para>
- <indexterm><primary>read only</primary><secondary>server</secondary></indexterm>
- The purpose of this type of server is to make available to any user
- any documents or files that are placed on the shared resource. The
- shared resource could be a CD-ROM drive, a CD-ROM image, or a file
- storage area.
- </para>
-
- <itemizedlist>
- <listitem><para>
- The file system share point will be <filename>/export</filename>.
- </para></listitem>
-
- <listitem><para>
- All files will be owned by a user called Jack Baumbach.
- Jack's login name will be <emphasis>jackb</emphasis>. His password will be
- <emphasis>m0r3pa1n</emphasis> &smbmdash; of course, that's just the example we are
- using; do not use this in a production environment because
- all readers of this document will know it.
- </para></listitem>
- </itemizedlist>
-
- <procedure>
- <title>Installation Procedure: Read-Only Server</title>
- <step><para>
- Add user to system (with creation of the user's home directory):
-<screen>
-&rootprompt;<userinput>useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Create directory, and set permissions and ownership:
-<screen>
-&rootprompt;<userinput>mkdir /export</userinput>
-&rootprompt;<userinput>chmod u+rwx,g+rx,o+rx /export</userinput>
-&rootprompt;<userinput>chown jackb.users /export</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Copy the files that should be shared to the <filename>/export</filename>
- directory.
- </para></step>
-
- <step><para>
- Install the Samba configuration file (<filename>/etc/samba/smb.conf</filename>)
- as shown in <link linkend="anon-example">Anonymous Read-Only Server Configuration</link>.
- </para></step>
-
-<example id="anon-example">
-<title>Anonymous Read-Only Server Configuration</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">HOBBIT</smbconfoption>
-<smbconfoption name="security">user</smbconfoption>
-<smbconfoption name="map to guest">bad user</smbconfoption>
-
-<smbconfsection name="[data]"/>
-<smbconfoption name="comment">Data</smbconfoption>
-<smbconfoption name="path">/export</smbconfoption>
-<smbconfoption name="read only">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <step><para>
- Test the configuration file by executing the following command:
-<screen>
-&rootprompt;<userinput>testparm</userinput>
-</screen>
- Alternatively, where you are operating from a master configuration file called
- <filename>smb.conf.master</filename>, the following sequence of commands might prove
- more appropriate:
-<screen>
-&rootprompt; cd /etc/samba
-&rootprompt; testparm -s smb.conf.master > smb.conf
-&rootprompt; testparm
-</screen>
- Note any error messages that might be produced. Proceed only if error-free output has been
- obtained. An example of typical output that should be generated from the above configuration
- file is shown here:
-<screen>
-Load smb config files from /etc/samba/smb.conf
-Processing section "[data]"
-Loaded services file OK.
-Server role: ROLE_STANDALONE
-Press enter to see a dump of your service definitions
-<userinput>[Press enter]</userinput>
-
-# Global parameters
-[global]
- workgroup = MIDEARTH
- netbios name = HOBBIT
- security = user
- map to guest = bad user
-
-[data]
- comment = Data
- path = /export
- read only = Yes
- guest only = Yes
-</screen>
- </para></step>
-
- <step><para>
- Start Samba using the method applicable to your operating system platform. The method that
- should be used is platform dependent. Refer to <link linkend="startingSamba">Starting Samba</link>
- for further information regarding the starting of Samba.
- </para></step>
-
- <step><para>
- Configure your MS Windows client for workgroup <emphasis>MIDEARTH</emphasis>,
- set the machine name to ROBBINS, reboot, wait a few (2 - 5) minutes,
- then open Windows Explorer and visit the Network Neighborhood.
- The machine HOBBIT should be visible. When you click this machine
- icon, it should open up to reveal the <emphasis>data</emphasis> share. After
- you click the share, it should open up to reveal the files previously
- placed in the <filename>/export</filename> directory.
- </para></step>
- </procedure>
-
- <para>
- The information above (following # Global parameters) provides the complete
- contents of the <filename>/etc/samba/smb.conf</filename> file.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Anonymous Read-Write Document Server</title>
-
- <para>
- <indexterm><primary>anonymous</primary><secondary>read-write server</secondary></indexterm>
- We should view this configuration as a progression from the previous example.
- The difference is that shared access is now forced to the user identity of jackb
- and to the primary group jackb belongs to. One other refinement we can make is to
- add the user <emphasis>jackb</emphasis> to the <filename>smbpasswd</filename> file.
- To do this, execute:
-<screen>
-&rootprompt;<userinput>smbpasswd -a jackb</userinput>
-New SMB password: <userinput>m0r3pa1n</userinput>
-Retype new SMB password: <userinput>m0r3pa1n</userinput>
-Added user jackb.
-</screen>
- Addition of this user to the <filename>smbpasswd</filename> file allows all files
- to be displayed in the Explorer Properties boxes as belonging to <emphasis>jackb</emphasis>
- instead of to <emphasis>User Unknown</emphasis>.
- </para>
-
- <para>
- The complete, modified &smb.conf; file is as shown in <link linkend="anon-rw"/>.
- </para>
-
-<example id="anon-rw">
-<title>Modified Anonymous Read-Write smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">HOBBIT</smbconfoption>
-<smbconfoption name="security">USER</smbconfoption>
-<smbconfoption name="map to guest">bad user</smbconfoption>
-
-<smbconfsection name="[data]"/>
-<smbconfoption name="comment">Data</smbconfoption>
-<smbconfoption name="path">/export</smbconfoption>
-<smbconfoption name="force user">jackb</smbconfoption>
-<smbconfoption name="force group">users</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- </sect3>
-
- <sect3>
- <title>Anonymous Print Server</title>
-
- <para>
- <indexterm><primary>anonymous</primary><secondary>print server</secondary></indexterm>
- An anonymous print server serves two purposes:
- </para>
-
- <itemizedlist>
- <listitem><para>
- It allows printing to all printers from a single location.
- </para></listitem>
-
- <listitem><para>
- It reduces network traffic congestion due to many users trying
- to access a limited number of printers.
- </para></listitem>
- </itemizedlist>
-
- <para>
- In the simplest of anonymous print servers, it is common to require the installation
- of the correct printer drivers on the Windows workstation. In this case the print
- server will be designed to just pass print jobs through to the spooler, and the spooler
- should be configured to do raw pass-through to the printer. In other words, the print
- spooler should not filter or process the data stream being passed to the printer.
- </para>
-
- <para>
- In this configuration, it is undesirable to present the Add Printer Wizard, and we do
- not want to have automatic driver download, so we disable it in the following
- configuration. <link linkend="anon-print"></link> is the resulting &smb.conf; file.
- </para>
-
-<example id="anon-print">
-<title>Anonymous Print Server smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">LUTHIEN</smbconfoption>
-<smbconfoption name="security">user</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- The above configuration is not ideal. It uses no smart features, and it deliberately
- presents a less than elegant solution. But it is basic, and it does print. Samba makes
- use of the direct printing application program interface that is provided by CUPS.
- When Samba has been compiled and linked with the CUPS libraries, the default printing
- system will be CUPS. By specifying that the printcap name is CUPS, Samba will use
- the CUPS library API to communicate directly with CUPS for all printer functions.
- It is possible to force the use of external printing commands by setting the value
- of the <parameter>printing</parameter> to either SYSV or BSD, and thus the value of
- the parameter <parameter>printcap name</parameter> must be set to something other than
- CUPS. In such case, it could be set to the name of any file that contains a list
- of printers that should be made available to Windows clients.
- </para>
-
- <note><para>
- Windows users will need to install a local printer and then change the print
- to device after installation of the drivers. The print to device can then be set to
- the network printer on this machine.
- </para></note>
-
- <para>
- Make sure that the directory <filename>/var/spool/samba</filename> is capable of being used
- as intended. The following steps must be taken to achieve this:
- </para>
-
- <itemizedlist>
- <listitem><para>
- The directory must be owned by the superuser (root) user and group:
-<screen>
-&rootprompt;<userinput>chown root.root /var/spool/samba</userinput>
-</screen>
- </para></listitem>
-
- <listitem><para>
- Directory permissions should be set for public read-write with the
- sticky bit set as shown:
-<screen>
-&rootprompt;<userinput>chmod a+twrx /var/spool/samba</userinput>
-</screen>
- The purpose of setting the sticky bit is to prevent who does not own the temporary print file
- from being able to take control of it with the potential for devious misuse.
- </para></listitem>
- </itemizedlist>
-
-
- <note><para>
- <indexterm><primary>MIME</primary><secondary>raw</secondary></indexterm>
- <indexterm><primary>raw printing</primary></indexterm>
- On CUPS-enabled systems there is a facility to pass raw data directly to the printer without
- intermediate processing via CUPS print filters. Where use of this mode of operation is desired,
- it is necessary to configure a raw printing device. It is also necessary to enable the raw mime
- handler in the <filename>/etc/mime.conv</filename> and <filename>/etc/mime.types</filename>
- files. Refer to <link linkend="cups-raw"></link>.
- </para></note>
-
- </sect3>
-
- <sect3>
-
- <title>Secure Read-Write File and Print Server</title>
-
- <para>
- We progress now from simple systems to a server that is slightly more complex.
- </para>
-
- <para>
- Our new server will require a public data storage area in which only authenticated
- users (i.e., those with a local account) can store files, as well as a home directory.
- There will be one printer that should be available for everyone to use.
- </para>
-
- <para>
- In this hypothetical environment (no espionage was conducted to obtain this data),
- the site is demanding a simple environment that is <emphasis>secure enough</emphasis>
- but not too difficult to use.
- </para>
-
- <para>
- Site users will be Jack Baumbach, Mary Orville, and Amed Sehkah. Each will have
- a password (not shown in further examples). Mary will be the printer administrator and will
- own all files in the public share.
- </para>
-
- <para>
- This configuration will be based on <emphasis>user-level security</emphasis> that
- is the default, and for which the default is to store Microsoft Windows-compatible
- encrypted passwords in a file called <filename>/etc/samba/smbpasswd</filename>.
- The default &smb.conf; entry that makes this happen is
- <smbconfoption name="passdb backend">smbpasswd</smbconfoption>. Since this is the default,
- it is not necessary to enter it into the configuration file.
- </para>
-
-
- <procedure>
- <title>Installing the Secure Office Server</title>
- <step><para>
- <indexterm><primary>office server</primary></indexterm>
- Add all users to the operating system:
-<screen>
-&rootprompt;<userinput>useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb</userinput>
-&rootprompt;<userinput>useradd -c "Mary Orville" -m -g users -p secret maryo</userinput>
-&rootprompt;<userinput>useradd -c "Amed Sehkah" -m -g users -p secret ameds</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Configure the Samba &smb.conf; file as shown in <link linkend="OfficeServer"/>.
- </para></step>
-
-<example id="OfficeServer">
-<title>Secure Office Server smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">OLORIN</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[public]"/>
-<smbconfoption name="comment">Data</smbconfoption>
-<smbconfoption name="path">/export</smbconfoption>
-<smbconfoption name="force user">maryo</smbconfoption>
-<smbconfoption name="force group">users</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="create mask">0600</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
- <step><para>
- Initialize the Microsoft Windows password database with the new users:
-<screen>
-&rootprompt;<userinput>smbpasswd -a root</userinput>
-New SMB password: <userinput>bigsecret</userinput>
-Reenter smb password: <userinput>bigsecret</userinput>
-Added user root.
-
-&rootprompt;<userinput>smbpasswd -a jackb</userinput>
-New SMB password: <userinput>m0r3pa1n</userinput>
-Retype new SMB password: <userinput>m0r3pa1n</userinput>
-Added user jackb.
-
-&rootprompt;<userinput>smbpasswd -a maryo</userinput>
-New SMB password: <userinput>secret</userinput>
-Reenter smb password: <userinput>secret</userinput>
-Added user maryo.
-
-&rootprompt;<userinput>smbpasswd -a ameds</userinput>
-New SMB password: <userinput>mysecret</userinput>
-Reenter smb password: <userinput>mysecret</userinput>
-Added user ameds.
-</screen>
- </para></step>
-
- <step><para>
- Install printer using the CUPS Web interface. Make certain that all
- printers that will be shared with Microsoft Windows clients are installed
- as raw printing devices.
- </para></step>
-
- <step><para>
- Start Samba using the operating system administrative interface.
- Alternately, this can be done manually by executing:
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
-<screen>
-&rootprompt;<userinput> nmbd; smbd;</userinput>
-</screen>
- Both applications automatically execute as daemons. Those who are paranoid about
- maintaining control can add the <constant>-D</constant> flag to coerce them to start
- up in daemon mode.
- </para></step>
-
- <step><para>
- Configure the <filename>/export</filename> directory:
-<screen>
-&rootprompt;<userinput>mkdir /export</userinput>
-&rootprompt;<userinput>chown maryo.users /export</userinput>
-&rootprompt;<userinput>chmod u=rwx,g=rwx,o-rwx /export</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Check that Samba is running correctly:
-<screen>
-&rootprompt;<userinput>smbclient -L localhost -U%</userinput>
-Domain=[MIDEARTH] OS=[UNIX] Server=[Samba-3.0.20]
-
-Sharename Type Comment
---------- ---- -------
-public Disk Data
-IPC$ IPC IPC Service (Samba-3.0.20)
-ADMIN$ IPC IPC Service (Samba-3.0.20)
-hplj4 Printer hplj4
-
-Server Comment
---------- -------
-OLORIN Samba-3.0.20
-
-Workgroup Master
---------- -------
-MIDEARTH OLORIN
-</screen>
- The following error message indicates that Samba was not running:
-<screen>
-&rootprompt; smbclient -L olorin -U%
-Error connecting to 192.168.1.40 (Connection refused)
-Connection to olorin failed
-</screen>
- </para></step>
-
- <step><para>
- Connect to OLORIN as maryo:
-<screen>
-&rootprompt;<userinput>smbclient //olorin/maryo -Umaryo%secret</userinput>
-OS=[UNIX] Server=[Samba-3.0.20]
-smb: \> <userinput>dir</userinput>
-. D 0 Sat Jun 21 10:58:16 2003
-.. D 0 Sat Jun 21 10:54:32 2003
-Documents D 0 Fri Apr 25 13:23:58 2003
-DOCWORK D 0 Sat Jun 14 15:40:34 2003
-OpenOffice.org D 0 Fri Apr 25 13:55:16 2003
-.bashrc H 1286 Fri Apr 25 13:23:58 2003
-.netscape6 DH 0 Fri Apr 25 13:55:13 2003
-.mozilla DH 0 Wed Mar 5 11:50:50 2003
-.kermrc H 164 Fri Apr 25 13:23:58 2003
-.acrobat DH 0 Fri Apr 25 15:41:02 2003
-
- 55817 blocks of size 524288. 34725 blocks available
-smb: \> <userinput>q</userinput>
-</screen>
- </para></step>
- </procedure>
-
- <para>
- By now you should be getting the hang of configuration basics. Clearly, it is time to
- explore slightly more complex examples. For the remainder of this chapter we abbreviate
- instructions, since there are previous examples.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Domain Member Server</title>
-
- <para>
- <indexterm><primary>Server Type</primary><secondary>Domain Member</secondary></indexterm>
- In this instance we consider the simplest server configuration we can get away with
- to make an accounting department happy. Let's be warned, the users are accountants and they
- do have some nasty demands. There is a budget for only one server for this department.
- </para>
-
- <para>
- The network is managed by an internal Information Services Group (ISG), to which we belong.
- Internal politics are typical of a medium-sized organization; Human Resources is of the
- opinion that they run the ISG because they are always adding and disabling users. Also,
- departmental managers have to fight tooth and nail to gain basic network resources access for
- their staff. Accounting is different, though, they get exactly what they want. So this should
- set the scene.
- </para>
-
- <para>
- We use the users from the last example. The accounting department
- has a general printer that all departmental users may use. There is also a check printer
- that may be used only by the person who has authority to print checks. The chief financial
- officer (CFO) wants that printer to be completely restricted and for it to be located in the
- private storage area in her office. It therefore must be a network printer.
- </para>
-
- <para>
- The accounting department uses an accounting application called <emphasis>SpytFull</emphasis>
- that must be run from a central application server. The software is licensed to run only off
- one server, there are no workstation components, and it is run off a mapped share. The data
- store is in a UNIX-based SQL backend. The UNIX gurus look after that, so this is not our
- problem.
- </para>
-
- <para>
- The accounting department manager (maryo) wants a general filing system as well as a separate
- file storage area for form letters (nastygrams). The form letter area should be read-only to
- all accounting staff except the manager. The general filing system has to have a structured
- layout with a general area for all staff to store general documents as well as a separate
- file area for each member of her team that is private to that person, but she wants full
- access to all areas. Users must have a private home share for personal work-related files
- and for materials not related to departmental operations.
- </para>
-
- <sect3>
- <title>Example Configuration</title>
-
- <para>
- The server <emphasis>valinor</emphasis> will be a member server of the company domain.
- Accounting will have only a local server. User accounts will be on the domain controllers,
- as will desktop profiles and all network policy files.
- </para>
-
- <procedure>
- <step><para>
- Do not add users to the UNIX/Linux server; all of this will run off the
- central domain.
- </para></step>
-
- <step><para>
- Configure &smb.conf; according to <link linkend="fast-member-server">Member server smb.conf
- (globals)</link> and <link linkend="fast-memberserver-shares">Member server smb.conf (shares
- and services)</link>.
- </para></step>
-
-<example id="fast-member-server">
-<title>Member Server smb.conf (Globals)</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">VALINOR</smbconfoption>
-<smbconfoption name="security">DOMAIN</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-<smbconfoption name="disable spoolss">Yes</smbconfoption>
-<smbconfoption name="show add printer wizard">No</smbconfoption>
-<smbconfoption name="idmap uid">15000-20000</smbconfoption>
-<smbconfoption name="idmap gid">15000-20000</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="fast-memberserver-shares">
-<title>Member Server smb.conf (Shares and Services)</title>
-<smbconfblock>
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[spytfull]"/>
-<smbconfoption name="comment">Accounting Application Only</smbconfoption>
-<smbconfoption name="path">/export/spytfull</smbconfoption>
-<smbconfoption name="valid users">@Accounts</smbconfoption>
-<smbconfoption name="admin users">maryo</smbconfoption>
-<smbconfoption name="read only">Yes</smbconfoption>
-
-<smbconfsection name="[public]"/>
-<smbconfoption name="comment">Data</smbconfoption>
-<smbconfoption name="path">/export/public</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="create mask">0600</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>rpc</secondary></indexterm>
- Join the domain. Note: Do not start Samba until this step has been completed!
-<screen>
-&rootprompt;<userinput>net rpc join -Uroot%'bigsecret'</userinput>
-Joined domain MIDEARTH.
-</screen>
- </para></step>
-
- <step><para>
- Make absolutely certain that you disable (shut down) the <command>nscd</command>
- daemon on any system on which <command>winbind</command> is configured to run.
- </para></step>
-
- <step><para>
- Start Samba following the normal method for your operating system platform.
- If you wish to do this manually, execute as root:
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
-<screen>
-&rootprompt;<userinput>nmbd; smbd; winbindd;</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Configure the name service switch (NSS) control file on your system to resolve user and group names
- via winbind. Edit the following lines in <filename>/etc/nsswitch.conf</filename>:
-<programlisting>
-passwd: files winbind
-group: files winbind
-hosts: files dns winbind
-</programlisting>
- </para></step>
-
- <step><para>
- Set the password for <command>wbinfo</command> to use:
-<screen>
-&rootprompt;<userinput>wbinfo --set-auth-user=root%'bigsecret'</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Validate that domain user and group credentials can be correctly resolved by executing:
-<screen>
-&rootprompt;<userinput>wbinfo -u</userinput>
-MIDEARTH\maryo
-MIDEARTH\jackb
-MIDEARTH\ameds
-...
-MIDEARTH\root
-
-&rootprompt;<userinput>wbinfo -g</userinput>
-MIDEARTH\Domain Users
-MIDEARTH\Domain Admins
-MIDEARTH\Domain Guests
-...
-MIDEARTH\Accounts
-</screen>
- </para></step>
-
- <step><para>
- Check that <command>winbind</command> is working. The following demonstrates correct
- username resolution via the <command>getent</command> system utility:
-<screen>
-&rootprompt;<userinput>getent passwd maryo</userinput>
-maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
-</screen>
- </para></step>
-
- <step><para>
- A final test that we have this under control might be reassuring:
-<screen>
-&rootprompt;<userinput>touch /export/a_file</userinput>
-&rootprompt;<userinput>chown maryo /export/a_file</userinput>
-&rootprompt;<userinput>ls -al /export/a_file</userinput>
-...
--rw-r--r-- 1 maryo users 11234 Jun 21 15:32 a_file
-...
-
-&rootprompt;<userinput>rm /export/a_file</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Configuration is now mostly complete, so this is an opportune time
- to configure the directory structure for this site:
-<screen>
-&rootprompt;<userinput>mkdir -p /export/{spytfull,public}</userinput>
-&rootprompt;<userinput>chmod ug=rwxS,o=x /export/{spytfull,public}</userinput>
-&rootprompt;<userinput>chown maryo.Accounts /export/{spytfull,public}</userinput>
-</screen>
- </para></step>
- </procedure>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Domain Controller</title>
-
-
- <para>
- <indexterm><primary>Server Type</primary><secondary>Domain Controller</secondary></indexterm>
- For the remainder of this chapter the focus is on the configuration of domain control.
- The examples that follow are for two implementation strategies. Remember, our objective is
- to create a simple but working solution. The remainder of this book should help to highlight
- opportunity for greater functionality and the complexity that goes with it.
- </para>
-
- <para>
- A domain controller configuration can be achieved with a simple configuration using the new
- tdbsam password backend. This type of configuration is good for small
- offices, but has limited scalability (cannot be replicated), and performance can be expected
- to fall as the size and complexity of the domain increases.
- </para>
-
- <para>
- The use of tdbsam is best limited to sites that do not need
- more than a Primary Domain Controller (PDC). As the size of a domain grows the need
- for additional domain controllers becomes apparent. Do not attempt to under-resource
- a Microsoft Windows network environment; domain controllers provide essential
- authentication services. The following are symptoms of an under-resourced domain control
- environment:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Domain logons intermittently fail.
- </para></listitem>
-
- <listitem><para>
- File access on a domain member server intermittently fails, giving a permission denied
- error message.
- </para></listitem>
- </itemizedlist>
-
- <para>
- A more scalable domain control authentication backend option might use
- Microsoft Active Directory or an LDAP-based backend. Samba provides
- for both options as a domain member server. As a PDC, Samba is not able to provide
- an exact alternative to the functionality that is available with Active Directory.
- Samba can provide a scalable LDAP-based PDC/BDC solution.
- </para>
-
- <para>
- The tdbsam authentication backend provides no facility to replicate
- the contents of the database, except by external means (i.e., there is no self-contained protocol
- in Samba for Security Account Manager database [SAM] replication).
- </para>
-
- <note><para>
- If you need more than one domain controller, do not use a tdbsam authentication backend.
- </para></note>
-
- <sect3>
- <title>Example: Engineering Office</title>
-
- <para>
- The engineering office network server we present here is designed to demonstrate use
- of the new tdbsam password backend. The tdbsam
- facility is new to Samba. It is designed to provide many user and machine account controls
- that are possible with Microsoft Windows NT4. It is safe to use this in smaller networks.
- </para>
-
- <procedure>
- <step><para>
- A working PDC configuration using the tdbsam
- password backend can be found in <link linkend="fast-engoffice-global">Engineering Office smb.conf
- (globals)</link> together with <link linkend="fast-engoffice-shares">Engineering Office smb.conf
- (shares and services)</link>:
- <indexterm><primary>pdbedit</primary></indexterm>
- </para></step>
-
-<example id="fast-engoffice-global">
-<title>Engineering Office smb.conf (globals)</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">FRODO</smbconfoption>
-<smbconfoption name="passdb backend">tdbsam</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-<smbconfoption name="add user script">/usr/sbin/useradd -m %u</smbconfoption>
-<smbconfoption name="delete user script">/usr/sbin/userdel -r %u</smbconfoption>
-<smbconfoption name="add group script">/usr/sbin/groupadd %g</smbconfoption>
-<smbconfoption name="delete group script">/usr/sbin/groupdel %g</smbconfoption>
-<smbconfoption name="add user to group script">/usr/sbin/groupmod -A %u %g</smbconfoption>
-<smbconfoption name="delete user from group script">/usr/sbin/groupmod -R %u %g</smbconfoption>
-<smbconfoption name="add machine script">/usr/sbin/useradd -s /bin/false -d /var/lib/nobody %u</smbconfoption>
-<smbconfcomment>Note: The following specifies the default logon script.</smbconfcomment>
-<smbconfcomment>Per user logon scripts can be specified in the user account using pdbedit </smbconfcomment>
-<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
-<smbconfcomment>This sets the default profile path. Set per user paths with pdbedit</smbconfcomment>
-<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">H:</smbconfoption>
-<smbconfoption name="logon home">\\%L\%U</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="os level">35</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="domain master">Yes</smbconfoption>
-<smbconfoption name="idmap uid">15000-20000</smbconfoption>
-<smbconfoption name="idmap gid">15000-20000</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-</smbconfblock>
-</example>
-
-<example id="fast-engoffice-shares">
-<title>Engineering Office smb.conf (shares and services)</title>
-<smbconfblock>
-<smbconfsection name="[homes]"/>
-<smbconfoption name="comment">Home Directories</smbconfoption>
-<smbconfoption name="valid users">%S</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfcomment>Printing auto-share (makes printers available thru CUPS)</smbconfcomment>
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="create mask">0600</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Drivers Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/drivers</smbconfoption>
-<smbconfoption name="write list">maryo, root</smbconfoption>
-
-<smbconfcomment>Needed to support domain logons</smbconfcomment>
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network Logon Service</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="admin users">root, maryo</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-
-<smbconfcomment>For profiles to work, create a user directory under the path</smbconfcomment>
-<smbconfcomment> shown. i.e., mkdir -p /var/lib/samba/profiles/maryo</smbconfcomment>
-<smbconfsection name="[Profiles]"/>
-<smbconfoption name="comment">Roaming Profile Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
-<smbconfoption name="read only">No</smbconfoption>
-<smbconfoption name="profile acls">Yes</smbconfoption>
-
-<smbconfcomment>Other resource (share/printer) definitions would follow below.</smbconfcomment>
-</smbconfblock>
-</example>
-
- <step><para>
- Create UNIX group accounts as needed using a suitable operating system tool:
-<screen>
-&rootprompt;<userinput>groupadd ntadmins</userinput>
-&rootprompt;<userinput>groupadd designers</userinput>
-&rootprompt;<userinput>groupadd engineers</userinput>
-&rootprompt;<userinput>groupadd qateam</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Create user accounts on the system using the appropriate tool
- provided with the operating system. Make sure all user home directories
- are created also. Add users to groups as required for access control
- on files, directories, printers, and as required for use in the Samba
- environment.
- </para></step>
-
-
- <step><para>
- <indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
- <indexterm><primary>initGroups.sh</primary></indexterm>
- Assign each of the UNIX groups to NT groups by executing this shell script
- (You could name the script <filename>initGroups.sh</filename>):
-<screen>
-#!/bin/bash
-#### Keep this as a shell script for future re-use
-
-# First assign well known groups
-net groupmap add ntgroup="Domain Admins" unixgroup=ntadmins rid=512 type=d
-net groupmap add ntgroup="Domain Users" unixgroup=users rid=513 type=
-net groupmap add ntgroup="Domain Guests" unixgroup=nobody rid=514 type=d
-
-# Now for our added Domain Groups
-net groupmap add ntgroup="Designers" unixgroup=designers type=d
-net groupmap add ntgroup="Engineers" unixgroup=engineers type=d
-net groupmap add ntgroup="QA Team" unixgroup=qateam type=d
-</screen>
- </para></step>
-
- <step><para>
- Create the <filename>scripts</filename> directory for use in the
- <smbconfsection name="[NETLOGON]"/> share:
-<screen>
-&rootprompt;<userinput>mkdir -p /var/lib/samba/netlogon/scripts</userinput>
-</screen>
- Place the logon scripts that will be used (batch or cmd scripts)
- in this directory.
- </para></step>
- </procedure>
-
- <para>
- The above configuration provides a functional PDC
- system to which must be added file shares and printers as required.
- </para>
-
- </sect3>
-
- <sect3>
- <title>A Big Organization</title>
-
- <para>
- In this section we finally get to review in brief a Samba configuration that
- uses a Lightweight Directory Access (LDAP)-based authentication backend. The
- main reasons for this choice are to provide the ability to host primary
- and Backup Domain Control (BDC), as well as to enable a higher degree of
- scalability to meet the needs of a very distributed environment.
- </para>
-
- <sect4>
- <title>The Primary Domain Controller</title>
-
- <para>
- This is an example of a minimal configuration to run a Samba PDC
- using an LDAP authentication backend. It is assumed that the operating system
- has been correctly configured.
- </para>
-
- <para>
- The Idealx scripts (or equivalent) are needed to manage LDAP-based POSIX and/or
- SambaSamAccounts. The Idealx scripts may be downloaded from the <ulink url="http://www.idealx.org">
- Idealx</ulink> Web site. They may also be obtained from the Samba tarball. Linux
- distributions tend to install the Idealx scripts in the
- <filename>/usr/share/doc/packages/sambaXXXXXX/examples/LDAP/smbldap-tools</filename> directory.
- Idealx scripts version <constant>smbldap-tools-0.9.1</constant> are known to work well.
- </para>
-
- <procedure>
- <step><para>
- Obtain from the Samba sources <filename>~/examples/LDAP/samba.schema</filename>
- and copy it to the <filename>/etc/openldap/schema/</filename> directory.
- </para></step>
-
- <step><para>
- Set up the LDAP server. This example is suitable for OpenLDAP 2.1.x.
- The <filename>/etc/openldap/slapd.conf</filename> file.
- <indexterm><primary>/etc/openldap/slapd.conf</primary></indexterm>
-<title>Example slapd.conf File</title>
-<screen>
-# Note commented out lines have been removed
-include /etc/openldap/schema/core.schema
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/nis.schema
-include /etc/openldap/schema/samba.schema
-
-pidfile /var/run/slapd/slapd.pid
-argsfile /var/run/slapd/slapd.args
-
-database bdb
-suffix "dc=quenya,dc=org"
-rootdn "cn=Manager,dc=quenya,dc=org"
-rootpw {SSHA}06qDkonA8hk6W6SSnRzWj0/pBcU3m0/P
-# The password for the above is 'nastyon3'
-
-directory /var/lib/ldap
-
-index objectClass eq
-index cn pres,sub,eq
-index sn pres,sub,eq
-index uid pres,sub,eq
-index displayName pres,sub,eq
-index uidNumber eq
-index gidNumber eq
-index memberUid eq
-index sambaSID eq
-index sambaPrimaryGroupSID eq
-index sambaDomainName eq
-index default sub
-</screen>
- </para></step>
-
- <step><para>
- Create the following file <filename>initdb.ldif</filename>:
- <indexterm><primary>initdb.ldif</primary></indexterm>
-<programlisting>
-# Organization for SambaXP Demo
-dn: dc=quenya,dc=org
-objectclass: dcObject
-objectclass: organization
-dc: quenya
-o: SambaXP Demo
-description: The SambaXP Demo LDAP Tree
-
-# Organizational Role for Directory Management
-dn: cn=Manager,dc=quenya,dc=org
-objectclass: organizationalRole
-cn: Manager
-description: Directory Manager
-
-# Setting up the container for users
-dn: ou=People, dc=quenya, dc=org
-objectclass: top
-objectclass: organizationalUnit
-ou: People
-
-# Set up an admin handle for People OU
-dn: cn=admin, ou=People, dc=quenya, dc=org
-cn: admin
-objectclass: top
-objectclass: organizationalRole
-objectclass: simpleSecurityObject
-userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb
-# The password for above is 'mordonL8'
-</programlisting>
- </para></step>
-
- <step><para>
- Load the initial data above into the LDAP database:
-<screen>
-&rootprompt;<userinput>slapadd -v -l initdb.ldif</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Start the LDAP server using the appropriate tool or method for
- the operating system platform on which it is installed.
- </para></step>
-
- <step><para>
- Install the Idealx script files in the <filename>/usr/local/sbin</filename> directory,
- then configure the smbldap_conf.pm file to match your system configuration.
- </para></step>
-
- <step><para>
- The &smb.conf; file that drives this backend can be found in example <link
- linkend="fast-ldap">LDAP backend smb.conf for PDC</link>. Add additional stanzas
- as required.
- </para></step>
-
-<example id="fast-ldap">
-<title>LDAP backend smb.conf for PDC</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">FRODO</smbconfoption>
-<smbconfoption name="passdb backend">ldapsam:ldap://localhost</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-<smbconfoption name="add user script">/usr/local/sbin/smbldap-useradd -m '%u'</smbconfoption>
-<smbconfoption name="delete user script">/usr/local/sbin/smbldap-userdel %u</smbconfoption>
-<smbconfoption name="add group script">/usr/local/sbin/smbldap-groupadd -p '%g'</smbconfoption>
-<smbconfoption name="delete group script">/usr/local/sbin/smbldap-groupdel '%g'</smbconfoption>
-<smbconfoption name="add user to group script">/usr/local/sbin/smbldap-groupmod -m '%u' '%g'</smbconfoption>
-<smbconfoption name="delete user from group script">/usr/local/sbin/smbldap-groupmod -x '%u' '%g'</smbconfoption>
-<smbconfoption name="set primary group script">/usr/local/sbin/smbldap-usermod -g '%g' '%u'</smbconfoption>
-<smbconfoption name="add machine script">/usr/local/sbin/smbldap-useradd -w '%u'</smbconfoption>
-<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
-<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">H:</smbconfoption>
-<smbconfoption name="logon home">\\%L\%U</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="os level">35</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="domain master">Yes</smbconfoption>
-<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager,dc=quenya,dc=org</smbconfoption>
-<smbconfoption name="ldap ssl">no</smbconfoption>
-<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
-<smbconfoption name="idmap uid">15000-20000</smbconfoption>
-<smbconfoption name="idmap gid">15000-20000</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-</smbconfblock>
-</example>
-
- <step><para>
- Add the LDAP password to the <filename>secrets.tdb</filename> file so Samba can update
- the LDAP database:
-<screen>
-&rootprompt;<userinput>smbpasswd -w mordonL8</userinput>
-</screen>
- </para></step>
-
- <step><para>
- Add users and groups as required. Users and groups added using Samba tools
- will automatically be added to both the LDAP backend and the operating
- system as required.
- </para></step>
-
- </procedure>
-
- </sect4>
-
- <sect4>
- <title>Backup Domain Controller</title>
-
- <para>
- <link linkend="fast-bdc"/> shows the example configuration for the BDC. Note that
- the &smb.conf; file does not specify the smbldap-tools scripts &smbmdash; they are
- not needed on a BDC. Add additional stanzas for shares and printers as required.
- </para>
-
- <procedure>
- <step><para>
- Decide if the BDC should have its own LDAP server or not. If the BDC is to be
- the LDAP server, change the following &smb.conf; as indicated. The default
- configuration in <link linkend="fast-bdc">Remote LDAP BDC smb.conf</link>
- uses a central LDAP server.
- </para></step>
-
-<example id="fast-bdc">
-<title>Remote LDAP BDC smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MIDEARTH</smbconfoption>
-<smbconfoption name="netbios name">GANDALF</smbconfoption>
-<smbconfoption name="passdb backend">ldapsam:ldap://frodo.quenya.org</smbconfoption>
-<smbconfoption name="username map">/etc/samba/smbusers</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-<smbconfoption name="logon script">scripts\logon.bat</smbconfoption>
-<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">H:</smbconfoption>
-<smbconfoption name="logon home">\\%L\%U</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="os level">33</smbconfoption>
-<smbconfoption name="preferred master">Yes</smbconfoption>
-<smbconfoption name="domain master">No</smbconfoption>
-<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager,dc=quenya,dc=org</smbconfoption>
-<smbconfoption name="ldap ssl">no</smbconfoption>
-<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
-<smbconfoption name="idmap uid">15000-20000</smbconfoption>
-<smbconfoption name="idmap gid">15000-20000</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-</smbconfblock>
-</example>
-
- <step><para>
- Configure the NETLOGON and PROFILES directory as for the PDC in <link linkend="fast-bdc"/>.
- </para></step>
- </procedure>
-
- </sect4>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="Further-Resources">
-<chapterinfo>
- &author.jelmer;
- <pubdate>May 1, 2003</pubdate>
-</chapterinfo>
-
-<title>Further Resources</title>
-
-<sect1>
- <title>Web sites</title>
-
-<itemizedlist>
-
- <listitem><para>
- <ulink url="http://hr.uoregon.edu/davidrl/cifs.txt">
- <emphasis>CIFS: Common Insecurities Fail Scrutiny</emphasis> by <quote>Hobbit</quote></ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://afr.com/it/2002/10/01/FFXDF43AP6D.html">
- <emphasis>Doing the Samba on Windows</emphasis> by Financial Review
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://ubiqx.org/cifs/">
- <emphasis>Implementing CIFS</emphasis> by Christopher R. Hertel
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://samba.anu.edu.au/cifs/docs/what-is-smb.html">
- <emphasis>Just What Is SMB?</emphasis> by Richard Sharpe
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.linux-mag.com/1999-05/samba_01.html">
- <emphasis>Opening Windows Everywhere</emphasis> by Mike Warfield
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.tldp.org/HOWTO/SMB-HOWTO.html">
- <emphasis>SMB HOWTO</emphasis> by David Wood
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.phrack.org/phrack/60/p60-0x0b.txt">
- <emphasis>SMB/CIFS by The Root</emphasis> by <quote>ledin</quote>
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.linux-mag.com/1999-09/samba_01.html">
- <emphasis>The Story of Samba</emphasis> by Christopher R. Hertel
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://hr.uoregon.edu/davidrl/samba/">
- <emphasis>The Unofficial Samba HOWTO</emphasis> by David Lechnyr
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.linux-mag.com/2001-05/smb_01.html">
- <emphasis>Understanding the Network Neighborhood</emphasis> by Christopher R. Hertel
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.linux-mag.com/2002-02/samba_01.html">
- <emphasis>Using Samba as a PDC</emphasis> by Andrew Bartlett
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://ru.samba.org/samba/ftp/docs/Samba24Hc13.pdf">
- <emphasis>PDF version of the Troubleshooting Techniques chapter</emphasis>
- from the second edition of Sam's Teach Yourself Samba in 24 Hours
- (publishing date of Dec. 12, 2001)</ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://ru.samba.org/samba/ftp/slides/">
- <emphasis>Slide presentations</emphasis> by Samba Team members
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html">
- <emphasis>Introduction to Samba-3.0</emphasis> by Motonobu Takahashi
- (written in Japanese). </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.linux-mag.com/2001-05/smb_01.html">
- <emphasis>Understanding the Network Neighborhood</emphasis>, by team member
- Chris Hertel. This article appeared in the May 2001 issue of
- Linux Magazine.
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="ftp://ftp.stratus.com/pub/vos/customers/samba/">
- <emphasis>Samba 2.0.x Troubleshooting guide</emphasis> from Paul Green
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="https://www.samba.org/samba/docs/10years.html">
- <emphasis>Ten Years of Samba</emphasis>
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://tldp.org/HOWTO/Samba-Authenticated-Gateway-HOWTO.html">
- <emphasis>Samba Authenticated Gateway HOWTO</emphasis>
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="https://www.samba.org/samba/docs/SambaIntro.html">
- <emphasis>An Introduction to Samba</emphasis>
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://www.samba.org/cifs/">
- <emphasis>What is CIFS?</emphasis>
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://support.microsoft.com/support/kb/articles/q92/5/88.asp">
- <emphasis>WFWG: Password Caching and How It Affects LAN Manager
- Security</emphasis> at Microsoft Knowledge Base
- </ulink>
- </para></listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1>
- <title>Related updates from Microsoft</title>
-
-<itemizedlist>
- <listitem><para>
- <ulink url="http://support.microsoft.com/support/kb/articles/q92/5/88.asp">
- <emphasis>Enhanced Encryption for Windows 95 Password Cache</emphasis>
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://support.microsoft.com/support/kb/articles/q136/4/18.asp">
- <emphasis>Windows '95 File Sharing Updates</emphasis>
- </ulink>
- </para></listitem>
-
- <listitem><para>
- <ulink url="http://support.microsoft.com/support/kb/articles/q136/4/18.asp">
- <emphasis>Windows for Workgroups Sharing Updates</emphasis>
- </ulink>
- </para></listitem>
-
-</itemizedlist>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="groupmapping">
-<chapterinfo>
- &author.jht;
- <author>
- <firstname>Jean François</firstname><surname>Micouleau</surname>
- </author>
- &author.jerry;
-</chapterinfo>
-<title>Group Mapping: MS Windows and UNIX</title>
-
-
- <para>
-<indexterm significance="preferred"><primary>groups</primary><secondary>mapping</secondary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>associations</primary></indexterm>
-<indexterm><primary>UNIX groups</primary></indexterm>
-<indexterm><primary>groupmap</primary></indexterm>
-<indexterm><primary>net</primary></indexterm>
- Starting with Samba-3, new group mapping functionality is available to create associations
- between Windows group SIDs and UNIX group GIDs. The <command>groupmap</command> subcommand
- included with the &net; tool can be used to manage these associations.
- </para>
-
- <para>
-<indexterm><primary>group mapping</primary></indexterm>
-<indexterm><primary>domain groups</primary></indexterm>
- The new facility for mapping NT groups to UNIX system groups allows the administrator to decide
- which NT domain groups are to be exposed to MS Windows clients. Only those NT groups that map
- to a UNIX group that has a value other than the default (<constant>-1</constant>) will be exposed
- in group selection lists in tools that access domain users and groups.
- </para>
-
- <warning>
- <para>
- <indexterm><primary>domain admin group</primary></indexterm>
-<indexterm><primary>Windows group</primary></indexterm>
- The <parameter>domain admin group</parameter> parameter has been removed in Samba-3 and should no longer
- be specified in &smb.conf;. In Samba-2.2.x, this parameter was used to give the listed users membership in the
- <constant>Domain Admins</constant> Windows group, which gave local admin rights on their workstations
- (in default configurations).
- </para>
- </warning>
-
-<sect1>
-<title>Features and Benefits</title>
-
- <para>
- Samba allows the administrator to create MS Windows NT4/200x group accounts and to
- arbitrarily associate them with UNIX/Linux group accounts.
- </para>
-
- <para>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>GID</primary></indexterm>
- <indexterm><primary>idmap uid</primary></indexterm>
-<indexterm><primary>MMC</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>ID range</primary></indexterm>
-<indexterm><primary>group accounts</primary></indexterm>
- Group accounts can be managed using the MS Windows NT4 or MS Windows 200x/XP Professional MMC tools.
- Appropriate interface scripts should be provided in &smb.conf; if it is desired that UNIX/Linux system
- accounts should be automatically created when these tools are used. In the absence of these scripts, and
- so long as <command>winbindd</command> is running, Samba group accounts that are created using these
- tools will be allocated UNIX UIDs and GIDs from the ID range specified by the
- <smbconfoption name="idmap uid"/>/<smbconfoption name="idmap gid"/>
- parameters in the &smb.conf; file.
- </para>
-
- <figure id="idmap-sid2gid">
- <title>IDMAP: Group SID-to-GID Resolution.</title>
- <imagefile scale="50">idmap-sid2gid</imagefile>
- </figure>
-
- <figure id="idmap-gid2sid">
- <title>IDMAP: GID Resolution to Matching SID.</title>
- <imagefile scale="50">idmap-gid2sid</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>IDMAP</primary></indexterm>
-<indexterm><primary>SID-to-GID</primary></indexterm>
-<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
-<indexterm><primary>group mappings</primary></indexterm>
- In both cases, when winbindd is not running, only locally resolvable groups can be recognized. Please refer to
- <link linkend="idmap-sid2gid">IDMAP: Group SID-to-GID Resolution</link> and <link
- linkend="idmap-gid2sid">IDMAP: GID Resolution to Matching SID</link>. The <command>net groupmap</command> is
- used to establish UNIX group to NT SID mappings as shown in <link linkend="idmap-store-gid2sid">IDMAP: storing
- group mappings</link>.
- </para>
-
- <figure id="idmap-store-gid2sid">
- <title>IDMAP Storing Group Mappings.</title>
- <imagefile scale="50">idmap-store-gid2sid</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>groupadd</primary></indexterm>
- <indexterm><primary>groupdel</primary></indexterm>
-<indexterm><primary>shadow utilities</primary></indexterm>
-<indexterm><primary>groupmod</primary></indexterm>
- Administrators should be aware that where &smb.conf; group interface scripts make
- direct calls to the UNIX/Linux system tools (the shadow utilities, <command>groupadd</command>,
- <command>groupdel</command>, and <command>groupmod</command>), the resulting UNIX/Linux group names will be subject
- to any limits imposed by these tools. If the tool does not allow uppercase characters
- or space characters, then the creation of an MS Windows NT4/200x-style group of
- <literal>Engineering Managers</literal> will attempt to create an identically named
- UNIX/Linux group, an attempt that will of course fail.
- </para>
-
- <para>
- <indexterm><primary>GID</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- There are several possible workarounds for the operating system tools limitation. One
- method is to use a script that generates a name for the UNIX/Linux system group that
- fits the operating system limits and that then just passes the UNIX/Linux group ID (GID)
- back to the calling Samba interface. This will provide a dynamic workaround solution.
- </para>
-
- <para>
-<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
- Another workaround is to manually create a UNIX/Linux group, then manually create the
- MS Windows NT4/200x group on the Samba server, and then use the <command>net groupmap</command>
- tool to connect the two to each other.
- </para>
-
-</sect1>
-
-<sect1>
-<title>Discussion</title>
-
- <para>
-<indexterm><primary>Windows NT4/200x</primary></indexterm>
-<indexterm><primary>group privileges</primary></indexterm>
- When you install <application>MS Windows NT4/200x</application> on a computer, the installation
- program creates default users and groups, notably the <constant>Administrators</constant> group,
- and gives that group privileges necessary to perform essential system tasks,
- such as the ability to change the date and time or to kill (or close) any process running on the
- local machine.
- </para>
-
- <para>
- <indexterm><primary>Administrator</primary></indexterm>
- The <constant>Administrator</constant> user is a member of the <constant>Administrators</constant> group, and thus inherits
- <constant>Administrators</constant> group privileges. If a <constant>joe</constant> user is created to be a member of the
- <constant>Administrators</constant> group, <constant>joe</constant> has exactly the same rights as the user
- <constant>Administrator</constant>.
- </para>
-
- <para>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>Domain Admins</primary></indexterm>
-<indexterm><primary>inherits rights</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
- When an MS Windows NT4/200x/XP machine is made a domain member, the <quote>Domain Admins</quote> group of the
- PDC is added to the local <constant>Administrators</constant> group of the workstation. Every member of the
- <constant>Domain Admins</constant> group inherits the rights of the local <constant>Administrators</constant> group when
- logging on the workstation.
- </para>
-
- <para>
-<indexterm><primary>Domain Admins</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
- The following steps describe how to make Samba PDC users members of the <constant>Domain Admins</constant> group.
- </para>
-
- <orderedlist>
- <listitem><para>
- Create a UNIX group (usually in <filename>/etc/group</filename>); let's call it <constant>domadm</constant>.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>/etc/group</primary></indexterm>
- Add to this group the users that must be <quote>Administrators</quote>. For example,
- if you want <constant>joe, john</constant>, and <constant>mary</constant> to be administrators,
- your entry in <filename>/etc/group</filename> will look like this:
- </para>
-
- <para><programlisting>
- domadm:x:502:joe,john,mary
- </programlisting>
- </para></listitem>
-
- <listitem><para>
- Map this domadm group to the <quote>Domain Admins</quote> group by executing the command:
- </para>
-
- <para>
-<screen>
-&rootprompt;<userinput>net groupmap add ntgroup="Domain Admins" unixgroup=domadm rid=512 type=d</userinput>
-</screen>
- </para>
-
- <para>
- <indexterm><primary>Domain Admins group</primary></indexterm>
- The quotes around <quote>Domain Admins</quote> are necessary due to the space in the group name.
- Also make sure to leave no white space surrounding the equal character (=).
- </para></listitem>
- </orderedlist>
-
- <para>
- Now <constant>joe, john</constant>, and <constant>mary</constant> are domain administrators.
- </para>
-
- <para>
- <indexterm><primary>groups</primary><secondary>domain</secondary></indexterm>
- It is possible to map any arbitrary UNIX group to any Windows NT4/200x group as well as
- to make any UNIX group a Windows domain group. For example, if you wanted to include a
- UNIX group (e.g., acct) in an ACL on a local file or printer on a Domain Member machine,
- you would flag that group as a domain group by running the following on the Samba PDC:
- </para>
-
- <para>
-<screen>
-&rootprompt;<userinput>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct type=d</userinput>
-</screen>
- The <literal>ntgroup</literal> value must be in quotes if it contains space characters to prevent
- the space from being interpreted as a command delimiter.
- </para>
-
- <para>
-<indexterm><primary>RID</primary></indexterm>
-<indexterm><primary>assigned RID</primary></indexterm>
- Be aware that the RID parameter is an unsigned 32-bit integer that should
- normally start at 1000. However, this RID must not overlap with any RID assigned
- to a user. Verification for this is done differently depending on the passdb backend
- you are using. Future versions of the tools may perform the verification automatically,
- but for now the burden is on you.
- </para>
-
- <sect2>
- <title>Warning: User Private Group Problems</title>
-
- <para>
-<indexterm><primary>group accounts</primary></indexterm>
-<indexterm><primary>Red Hat Linux</primary></indexterm>
-<indexterm><primary>private groups</primary></indexterm>
- Windows does not permit user and group accounts to have the same name.
- This has serious implications for all sites that use private group accounts.
- A private group account is an administrative practice whereby users are each
- given their own group account. Red Hat Linux, as well as several free distributions
- of Linux, by default create private groups.
- </para>
-
- <para>
-<indexterm><primary>UNIX/Linux group</primary></indexterm>
-<indexterm><primary>Windows group</primary></indexterm>
- When mapping a UNIX/Linux group to a Windows group account, all conflict can
- be avoided by assuring that the Windows domain group name does not overlap
- with any user account name.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Nested Groups: Adding Windows Domain Groups to Windows Local Groups</title>
-
- <indexterm><primary>groups</primary><secondary>nested</secondary></indexterm>
-
- <para>
-<indexterm><primary>nested groups</primary></indexterm>
- This functionality is known as <constant>nested groups</constant> and was first added to
- Samba-3.0.3.
- </para>
-
- <para>
-<indexterm><primary>nested groups</primary></indexterm>
- All MS Windows products since the release of Windows NT 3.10 support the use of nested groups.
- Many Windows network administrators depend on this capability because it greatly simplifies security
- administration.
- </para>
-
- <para>
-<indexterm><primary>nested group</primary></indexterm>
-<indexterm><primary>group membership</primary></indexterm>
-<indexterm><primary>domain security</primary></indexterm>
-<indexterm><primary>domain member server</primary></indexterm>
-<indexterm><primary>local groups</primary></indexterm>
-<indexterm><primary>domain global groups</primary></indexterm>
-<indexterm><primary>domain global users</primary></indexterm>
- The nested group architecture was designed with the premise that day-to-day user and group membership
- management should be performed on the domain security database. The application of group security
- should be implemented on domain member servers using only local groups. On the domain member server,
- all file system security controls are then limited to use of the local groups, which will contain
- domain global groups and domain global users.
- </para>
-
- <para>
-<indexterm><primary>individual domain user</primary></indexterm>
-<indexterm><primary>domain group settings</primary></indexterm>
-<indexterm><primary>Account Unknown</primary></indexterm>
- You may ask, What are the benefits of this arrangement? The answer is obvious to those who have plumbed
- the dark depths of Windows networking architecture. Consider for a moment a server on which are stored
- 200,000 files, each with individual domain user and domain group settings. The company that owns the
- file server is bought by another company, resulting in the server being moved to another location, and then
- it is made a member of a different domain. Who would you think now owns all the files and directories?
- Answer: Account Unknown.
- </para>
-
- <para>
-<indexterm><primary>directory access control</primary></indexterm>
-<indexterm><primary>local groups</primary></indexterm>
-<indexterm><primary>ACL</primary></indexterm>
-<indexterm><primary>Account Unknown</primary></indexterm>
- Unraveling the file ownership mess is an unenviable administrative task that can be avoided simply
- by using local groups to control all file and directory access control. In this case, only the members
- of the local groups will have been lost. The files and directories in the storage subsystem will still
- be owned by the local groups. The same goes for all ACLs on them. It is administratively much simpler
- to delete the <constant>Account Unknown</constant> membership entries inside local groups with appropriate
- entries for domain global groups in the new domain that the server has been made a member of.
- </para>
-
- <para>
-<indexterm><primary>nested groups</primary></indexterm>
-<indexterm><primary>administrative privileges</primary></indexterm>
-<indexterm><primary>domain member workstations</primary></indexterm>
-<indexterm><primary>domain member servers</primary></indexterm>
-<indexterm><primary>member machine</primary></indexterm>
-<indexterm><primary>full rights</primary></indexterm>
-<indexterm><primary>Domain Admins</primary></indexterm>
-<indexterm><primary>local administrative privileges</primary></indexterm>
- Another prominent example of the use of nested groups involves implementation of administrative privileges
- on domain member workstations and servers. Administrative privileges are given to all members of the
- built-in local group <constant>Administrators</constant> on each domain member machine. To ensure that all domain
- administrators have full rights on the member server or workstation, on joining the domain, the
- <constant>Domain Admins</constant> group is added to the local Administrators group. Thus everyone who is
- logged into the domain as a member of the Domain Admins group is also granted local administrative
- privileges on each domain member.
- </para>
-
- <para>
-<indexterm><primary>nested groups</primary></indexterm>
-<indexterm><primary>auxiliary members</primary></indexterm>
-<indexterm><primary>/etc/group</primary></indexterm>
-<indexterm><primary>winbind</primary></indexterm>
- UNIX/Linux has no concept of support for nested groups, and thus Samba has for a long time not supported
- them either. The problem is that you would have to enter UNIX groups as auxiliary members of a group in
- <filename>/etc/group</filename>. This does not work because it was not a design requirement at the time
- the UNIX file system security model was implemented. Since Samba-2.2, the winbind daemon can provide
- <filename>/etc/group</filename> entries on demand by obtaining user and group information from the domain
- controller that the Samba server is a member of.
- </para>
-
- <para>
-<indexterm><primary>/etc/group</primary></indexterm>
-<indexterm><primary>libnss_winbind</primary></indexterm>
-<indexterm><primary>local groups</primary></indexterm>
-<indexterm><primary>Domain Users</primary></indexterm>
-<indexterm><primary>alias group</primary></indexterm>
- In effect, Samba supplements the <filename>/etc/group</filename> data via the dynamic
- <command>libnss_winbind</command> mechanism. Beginning with Samba-3.0.3, this facility is used to provide
- local groups in the same manner as Windows. It works by expanding the local groups on the
- fly as they are accessed. For example, the <constant>Domain Users</constant> group of the domain is made
- a member of the local group <constant>demo</constant>. Whenever Samba needs to resolve membership of the
- <constant>demo</constant> local (alias) group, winbind asks the domain controller for demo members of the Domain Users
- group. By definition, it can only contain user objects, which can then be faked to be member of the
- UNIX/Linux group <constant>demo</constant>.
- </para>
-
- <para>
-<indexterm><primary>nested groups</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>winbind</primary></indexterm>
-<indexterm><primary>local groups</primary></indexterm>
-<indexterm><primary>Domain User Manager</primary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group</tertiary></indexterm>
- To enable the use of nested groups, <command>winbindd</command> must be used with NSS winbind.
- Creation and administration of the local groups is done best via the Windows Domain User Manager or its
- Samba equivalent, the utility <command>net rpc group</command>. Creating the local group
- <constant>demo</constant> is achieved by executing:
- <screen>
- &rootprompt; net rpc group add demo -L -Uroot%not24get
- </screen>
-<indexterm><primary>addmem</primary></indexterm>
-<indexterm><primary>delmem</primary></indexterm>
- Here the -L switch means that you want to create a local group. It may be necessary to add -S and -U
- switches for accessing the correct host with appropriate user or root privileges. Adding and removing
- group members can be done via the <constant>addmem</constant> and <constant>delmem</constant> subcommands of
- <command>net rpc group</command> command. For example, addition of <quote>DOM\Domain Users</quote> to the
- local group <constant>demo</constant> is done by executing:
- <screen>
- net rpc group addmem demo "DOM\Domain Users"
- </screen>
-<indexterm><primary>getent group demo</primary></indexterm>
-<indexterm><primary>trusted domain</primary></indexterm>
-<indexterm><primary>foreign domain</primary></indexterm>
-<indexterm><primary>local access permissions</primary></indexterm>
- Having completed these two steps, the execution of <command>getent group demo</command> will show demo
- members of the global <constant>Domain Users</constant> group as members of the group
- <constant>demo</constant>. This also works with any local or domain user. In case the domain DOM trusts
- another domain, it is also possible to add global users and groups of the trusted domain as members of
- <constant>demo</constant>. The users from the foreign domain who are members of the group that has been
- added to the <constant>demo</constant> group now have the same local access permissions as local domain
- users have.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Important Administrative Information</title>
-
- <para>
- Administrative rights are necessary in two specific forms:
- </para>
-
- <orderedlist>
- <listitem><para>For Samba domain controllers and domain member servers/clients.</para></listitem>
- <listitem><para>To manage domain member Windows workstations.</para></listitem>
- </orderedlist>
-
- <para>
-<indexterm><primary>rights and privileges</primary></indexterm>
-<indexterm><primary>domain member client</primary></indexterm>
-<indexterm><primary>group account</primary></indexterm>
- Versions of Samba up to and including 3.0.10 do not provide a means for assigning rights and privileges
- that are necessary for system administration tasks from a Windows domain member client machine, so
- domain administration tasks such as adding, deleting, and changing user and group account information, and
- managing workstation domain membership accounts, can be handled by any account other than root.
- </para>
-
- <para>
-<indexterm><primary>privilege management</primary></indexterm>
-<indexterm><primary>delegated</primary></indexterm>
-<indexterm><primary>Administrator</primary></indexterm>
- Samba-3.0.11 introduced a new privilege management interface (see <link linkend="rights">User Rights and Privileges</link>)
- that permits these tasks to be delegated to non-root (i.e., accounts other than the equivalent of the
- MS Windows Administrator) accounts.
- </para>
-
- <para>
-<indexterm><primary>mapped</primary></indexterm>
-<indexterm><primary>Domain Admins</primary></indexterm>
- Administrative tasks on a Windows domain member workstation can be done by anyone who is a member of the
- <constant>Domain Admins</constant> group. This group can be mapped to any convenient UNIX group.
- </para>
-
- <sect3>
- <title>Applicable Only to Versions Earlier than 3.0.11</title>
-
- <para>
-<indexterm><primary>privilege</primary></indexterm>
- Administrative tasks on UNIX/Linux systems, such as adding users or groups, requires
- <constant>root</constant>-level privilege. The addition of a Windows client to a Samba domain involves the
- addition of a user account for the Windows client.
- </para>
-
- <para>
-<indexterm><primary>system security</primary></indexterm>
-<indexterm><primary>privileges</primary></indexterm>
- Many UNIX administrators continue to request that the Samba Team make it possible to add Windows workstations, or
- the ability to add, delete, or modify user accounts, without requiring <constant>root</constant> privileges.
- Such a request violates every understanding of basic UNIX system security.
- </para>
-
- <para>
-<indexterm><primary>privileges</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>Domain Server Manager</primary></indexterm>
-<indexterm><primary>Domain User Manager</primary></indexterm>
-<indexterm><primary>manage share-level ACL</primary></indexterm>
-<indexterm><primary>share-level ACLs</primary></indexterm>
- There is no safe way to provide access on a UNIX/Linux system without providing
- <constant>root</constant>-level privileges. Provision of <constant>root</constant> privileges can be done
- either by logging on to the Domain as the user <constant>root</constant> or by permitting particular users to
- use a UNIX account that has a UID=0 in the <filename>/etc/passwd</filename> database. Users of such accounts
- can use tools like the NT4 Domain User Manager and the NT4 Domain Server Manager to manage user and group
- accounts as well as domain member server and client accounts. This level of privilege is also needed to manage
- share-level ACLs.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Default Users, Groups, and Relative Identifiers</title>
-
- <para>
- <indexterm><primary>Relative Identifier</primary><see>RID</see></indexterm>
- <indexterm><primary>RID</primary></indexterm>
-<indexterm><primary>Windows NT4/200x/XP</primary></indexterm>
-<indexterm><primary>well-known RID</primary></indexterm>
-<indexterm><primary>domain groups</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>NT groups</primary></indexterm>
- When first installed, Windows NT4/200x/XP are preconfigured with certain user, group, and
- alias entities. Each has a well-known RID. These must be preserved for continued
- integrity of operation. Samba must be provisioned with certain essential domain groups that require
- the appropriate RID value. When Samba is configured to use <constant>tdbsam</constant>, the essential
- domain groups are automatically created. It is the LDAP administrator's responsibility to create
- (provision) the default NT groups.
- </para>
-
- <para>
-<indexterm><primary>default users</primary></indexterm>
-<indexterm><primary>default groups</primary></indexterm>
-<indexterm><primary>default aliases</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
- Each essential domain group must be assigned its respective well-known RID. The default users, groups,
- aliases, and RIDs are shown in <link linkend="WKURIDS">Well-Known User Default RIDs</link>.
- </para>
-
- <note><para>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>ldapsam</primary></indexterm>
-<indexterm><primary>domain groups</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
- It is the administrator's responsibility to create the essential domain groups and to assign each
- its default RID.
- </para></note>
-
- <para>
-<indexterm><primary>domain groups</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
- It is permissible to create any domain group that may be necessary; just make certain that the essential
- domain groups (well known) have been created and assigned their default RIDs. Other groups you create may
- be assigned any arbitrary RID you care to use.
- </para>
-
- <para>
- Be sure to map each domain group to a UNIX system group. That is the only way to ensure that the group
- will be available for use as an NT domain group.
- </para>
-
- <para>
- <table frame="all" id="WKURIDS">
- <title>Well-Known User Default RIDs</title>
- <tgroup cols="4" align="left">
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="center"/>
- <thead>
- <row>
- <entry>Well-Known Entity</entry>
- <entry>RID</entry>
- <entry>Type</entry>
- <entry>Essential</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>Domain Administrator</entry>
- <entry>500</entry>
- <entry>User</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain Guest</entry>
- <entry>501</entry>
- <entry>User</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain KRBTGT</entry>
- <entry>502</entry>
- <entry>User</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain Admins</entry>
- <entry>512</entry>
- <entry>Group</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry>Domain Users</entry>
- <entry>513</entry>
- <entry>Group</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry>Domain Guests</entry>
- <entry>514</entry>
- <entry>Group</entry>
- <entry>Yes</entry>
- </row>
- <row>
- <entry>Domain Computers</entry>
- <entry>515</entry>
- <entry>Group</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain Controllers</entry>
- <entry>516</entry>
- <entry>Group</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain Certificate Admins</entry>
- <entry>517</entry>
- <entry>Group</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain Schema Admins</entry>
- <entry>518</entry>
- <entry>Group</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain Enterprise Admins</entry>
- <entry>519</entry>
- <entry>Group</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Domain Policy Admins</entry>
- <entry>520</entry>
- <entry>Group</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin Admins</entry>
- <entry>544</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin users</entry>
- <entry>545</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin Guests</entry>
- <entry>546</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin Power Users</entry>
- <entry>547</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin Account Operators</entry>
- <entry>548</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin System Operators</entry>
- <entry>549</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin Print Operators</entry>
- <entry>550</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin Backup Operators</entry>
- <entry>551</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin Replicator</entry>
- <entry>552</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>Builtin RAS Servers</entry>
- <entry>553</entry>
- <entry>Alias</entry>
- <entry>No</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Example Configuration</title>
-
- <para>
-<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
- You can list the various groups in the mapping database by executing
- <command>net groupmap list</command>. Here is an example:
- </para>
-
- <para>
-<indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
-<screen>
-&rootprompt; <userinput>net groupmap list</userinput>
-Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
-Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
-Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
-</screen>
- </para>
-
- <para>
- For complete details on <command>net groupmap</command>, refer to the net(8) man page.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Configuration Scripts</title>
-
- <para>
- Everyone needs tools. Some of us like to create our own, others prefer to use canned tools
- (i.e., prepared by someone else for general use).
- </para>
-
- <sect2>
- <title>Sample &smb.conf; Add Group Script</title>
-
- <para>
- <indexterm><primary>smbgrpadd.sh</primary></indexterm>
- <indexterm><primary>groupadd limitations</primary></indexterm>
- <indexterm><primary>smbgrpadd.sh</primary></indexterm>
-<indexterm><primary>/etc/group</primary></indexterm>
-<indexterm><primary>groupadd</primary></indexterm>
- A script to create complying group names for use by the Samba group interfaces
- is provided in <link linkend="smbgrpadd.sh">smbgrpadd.sh</link>. This script
- adds a temporary entry in the <filename>/etc/group</filename> file and then renames
- it to the desired name. This is an example of a method to get around operating
- system maintenance tool limitations such as those present in some version of the
- <command>groupadd</command> tool.
-<example id="smbgrpadd.sh">
-<title>smbgrpadd.sh</title>
-<programlisting>
-#!/bin/bash
-
-# Add the group using normal system groupadd tool.
-groupadd smbtmpgrp00
-
-thegid=`cat /etc/group | grep ^smbtmpgrp00 | cut -d ":" -f3`
-
-# Now change the name to what we want for the MS Windows networking end
-cp /etc/group /etc/group.bak
-cat /etc/group.bak | sed "s/^smbtmpgrp00/$1/g" > /etc/group
-rm /etc/group.bak
-
-# Now return the GID as would normally happen.
-echo $thegid
-exit 0
-</programlisting>
-</example>
-</para>
-
- <para>
- The &smb.conf; entry for the above script shown in <link linkend="smbgrpadd">the configuration of
- &smb.conf; for the add group Script</link> demonstrates how it may be used.
-
-<example id="smbgrpadd">
-<title>Configuration of &smb.conf; for the add group Script</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="add group script">/path_to_tool/smbgrpadd.sh "%g"</smbconfoption>
-</smbconfblock>
-</example>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Script to Configure Group Mapping</title>
-
- <para>
-<indexterm><primary>initGroups.sh</primary></indexterm>
- In our example we have created a UNIX/Linux group called <literal>ntadmin</literal>.
- Our script will create the additional groups <literal>Orks</literal>, <literal>Elves</literal>, and <literal>Gnomes</literal>.
- It is a good idea to save this shell script for later use just in case you ever need to rebuild your mapping database.
- For the sake of convenience we elect to save this script as a file called <filename>initGroups.sh</filename>.
- This script is given in <link linkend="set-group-map">intGroups.sh</link>.
-<indexterm><primary>initGroups.sh</primary></indexterm>
-<example id="set-group-map">
-<title>Script to Set Group Mapping</title>
-<programlisting>
-#!/bin/bash
-
-net groupmap add ntgroup="Domain Admins" unixgroup=ntadmin rid=512 type=d
-net groupmap add ntgroup="Domain Users" unixgroup=users rid=513 type=d
-net groupmap add ntgroup="Domain Guests" unixgroup=nobody rid=514 type=d
-
-groupadd Orks
-groupadd Elves
-groupadd Gnomes
-
-net groupmap add ntgroup="Orks" unixgroup=Orks type=d
-net groupmap add ntgroup="Elves" unixgroup=Elves type=d
-net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d
-</programlisting>
-</example>
- </para>
-
- <para>
- Of course it is expected that the administrator will modify this to suit local needs.
- For information regarding the use of the <command>net groupmap</command> tool please
- refer to the man page.
- </para>
-
- <note><para>
- Versions of Samba-3 prior to 3.0.23 automatically create default group mapping for the
- <literal>Domain Admins, Domain Users</literal> and <literal>Domain Guests</literal> Windows
- groups, but do not map them to UNIX GIDs. This was a cause of administrative confusion and
- trouble. Commencing with Samba-3.0.23 this anomaly has been fixed - thus all Windows groups
- must now be manually and explicitly created and mapped to a valid UNIX GID by the Samba
- administrator.
- </para></note>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-At this time there are many little surprises for the unwary administrator. In a real sense
-it is imperative that every step of automated control scripts be carefully tested
-manually before putting it into active service.
-</para>
-
- <sect2>
- <title>Adding Groups Fails</title>
-
- <para>
-<indexterm><primary>groupadd</primary></indexterm>
- This is a common problem when the <command>groupadd</command> is called directly
- by the Samba interface script for the <smbconfoption name="add group script"/> in
- the &smb.conf; file.
- </para>
-
- <para>
-<indexterm><primary>uppercase character</primary></indexterm>
-<indexterm><primary>space character</primary></indexterm>
- The most common cause of failure is an attempt to add an MS Windows group account
- that has an uppercase character and/or a space character in it.
- </para>
-
- <para>
-<indexterm><primary>groupadd</primary></indexterm>
- There are three possible workarounds. First, use only group names that comply
- with the limitations of the UNIX/Linux <command>groupadd</command> system tool.
- Second, it involves the use of the script mentioned earlier in this chapter, and
- third is the option is to manually create a UNIX/Linux group account that can substitute
- for the MS Windows group name, then use the procedure listed above to map that group
- to the MS Windows group.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Adding Domain Users to the Workstation Power Users Group</title>
-
- <para><quote>
- What must I do to add domain users to the Power Users group?
- </quote></para>
-
- <para>
-<indexterm><primary>Domain Users group</primary></indexterm>
- The Power Users group is a group that is local to each Windows 200x/XP Professional workstation.
- You cannot add the Domain Users group to the Power Users group automatically, it must be done on
- each workstation by logging in as the local workstation <emphasis>administrator</emphasis> and
- then using the following procedure:
- </para>
-
- <procedure>
- <step><para>
- Click <guimenu>Start -> Control Panel -> Users and Passwords</guimenu>.
- </para></step>
-
- <step><para>
- Click the <guimenuitem>Advanced</guimenuitem> tab.
- </para></step>
-
- <step><para>
- Click the <guibutton>Advanced</guibutton> button.
- </para></step>
-
- <step><para>
- Click <constant>Groups</constant>.
- </para></step>
-
- <step><para>
- Double-click <constant>Power Users</constant>. This will launch the panel to add users or groups
- to the local machine <constant>Power Users</constant> group.
- </para></step>
-
- <step><para>
- Click the <guibutton>Add</guibutton> button.
- </para></step>
-
- <step><para>
- Select the domain from which the <constant>Domain Users</constant> group is to be added.
- </para></step>
-
- <step><para>
- Double-click the <constant>Domain Users</constant> group.
- </para></step>
-
- <step><para>
- Click the <guibutton>OK</guibutton> button. If a logon box is presented during this process,
- please remember to enter the connect as <constant>DOMAIN\UserName</constant>, that is, for the
- domain <constant>MIDEARTH</constant> and the user <constant>root</constant> enter
- <constant>MIDEARTH\root</constant>.
- </para></step>
- </procedure>
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="idmapper">
-<chapterinfo>
- &author.jht;
-</chapterinfo>
-
-<title>Identity Mapping (IDMAP)</title>
-
-<para>
-<indexterm><primary>Windows</primary></indexterm>
-<indexterm><primary>interoperability</primary></indexterm>
-<indexterm><primary>IDMAP</primary></indexterm>
-<indexterm><primary>Windows Security Identifiers</primary><see>SID</see></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-The Microsoft Windows operating system has a number of features that impose specific challenges
-to interoperability with the operating systems on which Samba is implemented. This chapter deals
-explicitly with the mechanisms Samba (version 3.0.8 and later) uses to overcome one of the
-key challenges in the integration of Samba servers into an MS Windows networking environment.
-This chapter deals with identity mapping (IDMAP) of Windows security identifiers (SIDs)
-to UNIX UIDs and GIDs.
-</para>
-
-<para>
-To ensure sufficient coverage, each possible Samba deployment type is discussed.
-This is followed by an overview of how the IDMAP facility may be implemented.
-</para>
-
-<para>
-<indexterm><primary>network client</primary></indexterm>
-<indexterm><primary>IDMAP</primary></indexterm>
-<indexterm><primary>IDMAP infrastructure</primary></indexterm>
-<indexterm><primary>default behavior</primary></indexterm>
-The IDMAP facility is of concern where more than one Samba server (or Samba network client)
-is installed in a domain. Where there is a single Samba server, do not be too concerned regarding
-the IDMAP infrastructure &smbmdash; the default behavior of Samba is nearly always sufficient.
-Where multiple Samba servers are used it is often necessary to move data off one server and onto
-another, and that is where the fun begins!
-</para>
-
-<para>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>nss_ldap</primary></indexterm>
-<indexterm><primary>NT4 domain members</primary></indexterm>
-<indexterm><primary>ADS domain members</primary></indexterm>
-<indexterm><primary>security name-space</primary></indexterm>
-Where user and group account information is stored in an LDAP directory every server can have the same
-consistent UID and GID for users and groups. This is achieved using NSS and the nss_ldap tool. Samba
-can be configured to use only local accounts, in which case the scope of the IDMAP problem is somewhat
-reduced. This works reasonably well if the servers belong to a single domain, and interdomain trusts
-are not needed. On the other hand, if the Samba servers are NT4 domain members, or ADS domain members,
-or if there is a need to keep the security name-space separate (i.e., the user
-<literal>DOMINICUS\FJones</literal> must not be given access to the account resources of the user
-<literal>FRANCISCUS\FJones</literal><footnote><para>Samba local account mode results in both
-<literal>DOMINICUS\FJones</literal> and <literal>FRANCISCUS\FJones</literal> mapping to the UNIX user
-<literal>FJones</literal>.</para></footnote> free from inadvertent cross-over, close attention should be given
-to the way that the IDMAP facility is configured.
-</para>
-
-<para>
-<indexterm><primary>IDMAP</primary></indexterm>
-<indexterm><primary>domain access</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>one domain</primary></indexterm>
-The use of IDMAP is important where the Samba server will be accessed by workstations or servers from
-more than one domain, in which case it is important to run winbind so it can handle the resolution (ID mapping)
-of foreign SIDs to local UNIX UIDs and GIDs.
-</para>
-
-<para>
-<indexterm><primary>winbindd</primary></indexterm>
-The use of the IDMAP facility requires the execution of the <command>winbindd</command> upon Samba startup.
-</para>
-
-<sect1>
-<title>Samba Server Deployment Types and IDMAP</title>
-
-<para>
-<indexterm><primary>Server Types</primary></indexterm>
-There are four basic server deployment types, as documented in <link linkend="ServerType">the chapter
-on Server Types and Security Modes</link>.
-</para>
-
- <sect2>
- <title>Standalone Samba Server</title>
-
- <para>
- <indexterm><primary>stand-alone server</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>NT4 Domain</primary></indexterm>
- A standalone Samba server is an implementation that is not a member of a Windows NT4 domain,
- a Windows 200X Active Directory domain, or a Samba domain.
- </para>
-
- <para>
- <indexterm><primary>IDMAP</primary></indexterm>
- <indexterm><primary>identity</primary></indexterm>
- <indexterm><primary>local user</primary></indexterm>
- By definition, this means that users and groups will be created and controlled locally, and
- the identity of a network user must match a local UNIX/Linux user login. The IDMAP facility
- is therefore of little to no interest, winbind will not be necessary, and the IDMAP facility
- will not be relevant or of interest.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Domain Member Server or Domain Member Client</title>
-
- <para>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>NT4</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- Samba can act as a Windows NT4 PDC or BDC, thereby providing domain control protocols that
- are compatible with Windows NT4. Samba file and print sharing protocols are compatible with
- all versions of MS Windows products. Windows NT4, as with MS Active Directory,
- extensively makes use of Windows SIDs.
- </para>
-
- <para>
- <indexterm><primary>MS Windows SID</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>GID</primary></indexterm>
- Samba domain member servers and clients must interact correctly with MS Windows SIDs. Incoming
- Windows SIDs must be translated to local UNIX UIDs and GIDs. Outgoing information from the Samba
- server must provide to MS Windows clients and servers appropriate SIDs.
- </para>
-
- <para>
- <indexterm><primary>ADS</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- A Samba member of a Windows networking domain (NT4-style or ADS) can be configured to handle
- identity mapping in a variety of ways. The mechanism it uses depends on whether or not
- the <command>winbindd</command> daemon is used and how the winbind functionality is configured.
- The configuration options are briefly described here:
- </para>
-
- <variablelist>
- <varlistentry><term>Winbind is not used; users and groups are local: </term>
- <listitem>
- <para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>network traffic</primary></indexterm>
- <indexterm><primary>LoginID</primary></indexterm>
- <indexterm><primary>account name</primary></indexterm>
- <indexterm><primary>getpwnam</primary></indexterm>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>local users</primary></indexterm>
- <indexterm><primary>local groups</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- <indexterm><primary>/etc/group</primary></indexterm>
- Where <command>winbindd</command> is not used Samba (<command>smbd</command>)
- uses the underlying UNIX/Linux mechanisms to resolve the identity of incoming
- network traffic. This is done using the LoginID (account name) in the
- session setup request and passing it to the getpwnam() system function call.
- This call is implemented using the name service switch (NSS) mechanism on
- modern UNIX/Linux systems. By saying "users and groups are local,"
- we are implying that they are stored only on the local system, in the
- <filename>/etc/passwd</filename> and <filename>/etc/group</filename> respectively.
- </para>
-
- <para>
- <indexterm><primary>SessionSetupAndX</primary></indexterm>
- <indexterm><primary>/etc/passwd</primary></indexterm>
- For example, when the user <literal>BERYLIUM\WambatW</literal> tries to open a
- connection to a Samba server the incoming SessionSetupAndX request will make a
- system call to look up the user <literal>WambatW</literal> in the
- <filename>/etc/passwd</filename> file.
- </para>
-
- <para>
- <indexterm><primary>standalone</primary></indexterm>
- <indexterm><primary>domain member server</primary></indexterm>
- <indexterm><primary>NT4</primary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- This configuration may be used with standalone Samba servers, domain member
- servers (NT4 or ADS), and for a PDC that uses either an smbpasswd
- or a tdbsam-based Samba passdb backend.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>Winbind is not used; users and groups resolved via NSS: </term>
- <listitem>
- <para>
- <indexterm><primary>user accounts</primary></indexterm>
- <indexterm><primary>group accounts</primary></indexterm>
- <indexterm><primary>local accounts</primary></indexterm>
- <indexterm><primary>repository</primary></indexterm>
- <indexterm><primary>NIS</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- In this situation user and group accounts are treated as if they are local
- accounts. The only way in which this differs from having local accounts is
- that the accounts are stored in a repository that can be shared. In practice
- this means that they will reside in either an NIS-type database or else in LDAP.
- </para>
-
- <para>
- <indexterm><primary>standalone</primary></indexterm>
- <indexterm><primary>domain member server</primary></indexterm>
- <indexterm><primary>NT4</primary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- This configuration may be used with standalone Samba servers, domain member
- servers (NT4 or ADS), and for a PDC that uses either an smbpasswd
- or a tdbsam-based Samba passdb backend.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>Winbind/NSS with the default local IDMAP table: </term>
- <listitem>
- <para>
- <indexterm><primary>NT4 domain</primary></indexterm>
- <indexterm><primary>ADS domain</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>domain control</primary></indexterm>
- There are many sites that require only a simple Samba server or a single Samba
- server that is a member of a Windows NT4 domain or an ADS domain. A typical example
- is an appliance like file server on which no local accounts are configured and
- winbind is used to obtain account credentials from the domain controllers for the
- domain. The domain control can be provided by Samba, MS Windows NT4, or MS Windows
- Active Directory.
- </para>
-
- <para>
- <indexterm><primary>UID numbers</primary></indexterm>
- <indexterm><primary>GID numbers</primary></indexterm>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- Winbind is a great convenience in this situation. All that is needed is a range of
- UID numbers and GID numbers that can be defined in the &smb.conf; file. The
- <filename>/etc/nsswitch.conf</filename> file is configured to use <command>winbind</command>,
- which does all the difficult work of mapping incoming SIDs to appropriate UIDs and GIDs.
- The SIDs are allocated a UID/GID in the order in which winbind receives them.
- </para>
-
- <para>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>GID</primary></indexterm>
- <indexterm><primary>IDMAP</primary></indexterm>
- <indexterm><primary>corrupted file</primary></indexterm>
- This configuration is not convenient or practical in sites that have more than one
- Samba server and that require the same UID or GID for the same user or group across
- all servers. One of the hazards of this method is that in the event that the winbind
- IDMAP file becomes corrupted or lost, the repaired or rebuilt IDMAP file may allocate
- UIDs and GIDs to different users and groups from what was there previously with the
- result that MS Windows files that are stored on the Samba server may now not belong to
- the rightful owners.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>Winbind/NSS uses RID based IDMAP: </term>
- <listitem>
- <para>
- <indexterm><primary>RID</primary></indexterm>
- <indexterm><primary>idmap_rid</primary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- The IDMAP_RID facility is new to Samba version 3.0.8. It was added to make life easier
- for a number of sites that are committed to use of MS ADS, that do not apply
- an ADS schema extension, and that do not have an installed an LDAP directory server just for
- the purpose of maintaining an IDMAP table. If you have a single ADS domain (not a forest of
- domains, and not multiple domain trees) and you want a simple cookie-cutter solution to the
- IDMAP table problem, then IDMAP_RID is an obvious choice.
- </para>
-
- <para>
- <indexterm><primary>idmap_rid</primary></indexterm>
- <indexterm><primary>idmap uid</primary></indexterm>
- <indexterm><primary>idmap gid</primary></indexterm>
- <indexterm><primary>RID</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>idmap backend</primary></indexterm>
- <indexterm><primary>automatic mapping</primary></indexterm>
- This facility requires the allocation of the <parameter>idmap uid</parameter> and the
- <parameter>idmap gid</parameter> ranges, and within the <parameter>idmap uid</parameter>
- it is possible to allocate a subset of this range for automatic mapping of the relative
- identifier (RID) portion of the SID directly to the base of the UID plus the RID value.
- For example, if the <parameter>idmap uid</parameter> range is <constant>1000-100000000</constant>
- and the <parameter>idmap backend = idmap_rid:DOMAIN_NAME=1000-50000000</parameter>, and
- a SID is encountered that has the value <constant>S-1-5-21-34567898-12529001-32973135-1234</constant>,
- the resulting UID will be <constant>1000 + 1234 = 2234</constant>.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>Winbind with an NSS/LDAP backend-based IDMAP facility: </term>
- <listitem>
- <para>
- <indexterm><primary>Domain Member</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>GID</primary></indexterm>
- <indexterm><primary>idmap gid</primary></indexterm>
- <indexterm><primary>idmap uid</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- In this configuration <command>winbind</command> resolved SIDs to UIDs and GIDs from
- the <parameter>idmap uid</parameter> and <parameter>idmap gid</parameter> ranges specified
- in the &smb.conf; file, but instead of using a local winbind IDMAP table, it is stored
- in an LDAP directory so that all domain member machines (clients and servers) can share
- a common IDMAP table.
- </para>
-
- <para>
- <indexterm><primary>idmap backend</primary></indexterm>
- <indexterm><primary>LDAP server</primary></indexterm>
- <indexterm><primary>LDAP redirects</primary></indexterm>
- It is important that all LDAP IDMAP clients use only the master LDAP server because the
- <parameter>idmap backend</parameter> facility in the &smb.conf; file does not correctly
- handle LDAP redirects.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>Winbind with NSS to resolve UNIX/Linux user and group IDs: </term>
- <listitem>
- <para>
- The use of LDAP as the passdb backend is a smart solution for PDC, BDC, and
- domain member servers. It is a neat method for assuring that UIDs, GIDs, and the matching
- SIDs are consistent across all servers.
- </para>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>PADL</primary></indexterm>
- The use of the LDAP-based passdb backend requires use of the PADL nss_ldap utility or
- an equivalent. In this situation winbind is used to handle foreign SIDs, that is, SIDs from
- standalone Windows clients (i.e., not a member of our domain) as well as SIDs from
- another domain. The foreign UID/GID is mapped from allocated ranges (idmap uid and idmap gid)
- in precisely the same manner as when using winbind with a local IDMAP table.
- </para>
-
- <para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- <indexterm><primary>AD4UNIX</primary></indexterm>
- <indexterm><primary>MMC</primary></indexterm>
- The nss_ldap tool set can be used to access UIDs and GIDs via LDAP as well as via Active
- Directory. In order to use Active Directory, it is necessary to modify the ADS schema by
- installing either the AD4UNIX schema extension or using the Microsoft Services for UNIX
- version 3.5 or later to extend the ADS schema so it maintains UNIX account credentials.
- Where the ADS schema is extended, a Microsoft Management Console (MMC) snap-in is also
- installed to permit the UNIX credentials to be set and managed from the ADS User and Computer
- Management tool. Each account must be separately UNIX-enabled before the UID and GID data can
- be used by Samba.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
-
- </sect2>
-
- <sect2>
- <title>Primary Domain Controller</title>
-
- <para>
- <indexterm><primary>domain security</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>RID</primary></indexterm>
- <indexterm><primary>algorithmic mapping</primary></indexterm>
- Microsoft Windows domain security systems generate the user and group SID as part
- of the process of creation of an account. Windows does not have a concept of the UNIX UID or a GID; rather,
- it has its own type of security descriptor. When Samba is used as a domain controller, it provides a method
- of producing a unique SID for each user and group. Samba generates a machine and a domain SID to which it
- adds an RID that is calculated algorithmically from a base value that can be specified
- in the &smb.conf; file, plus twice (2x) the UID or GID. This method is called <quote>algorithmic mapping</quote>.
- </para>
-
- <para>
- <indexterm><primary>RID base</primary></indexterm>
- For example, if a user has a UID of 4321, and the algorithmic RID base has a value of 1000, the RID will
- be <literal>1000 + (2 x 4321) = 9642</literal>. Thus, if the domain SID is
- <literal>S-1-5-21-89238497-92787123-12341112</literal>, the resulting SID is
- <literal>S-1-5-21-89238497-92787123-12341112-9642</literal>.
- </para>
-
- <para>
- <indexterm><primary>on-the-fly</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>ldapsam</primary></indexterm>
- The foregoing type of SID is produced by Samba as an automatic function and is either produced on the fly
- (as is the case when using a <parameter>passdb backend = [tdbsam | smbpasswd]</parameter>), or may be stored
- as a permanent part of an account in an LDAP-based ldapsam.
- </para>
-
- <para>
- <indexterm><primary>SFU 3.5</primary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- <indexterm><primary>directory schema</primary></indexterm>
- <indexterm><primary>account attributes</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>GID</primary></indexterm>
- <indexterm><primary>ADS schema</primary></indexterm>
- <indexterm><primary>account management</primary></indexterm>
- <indexterm><primary>MMC</primary></indexterm>
- ADS uses a directory schema that can be extended to accommodate additional
- account attributes such as UIDs and GIDs. The installation of Microsoft Service for UNIX 3.5 will expand
- the normal ADS schema to include UNIX account attributes. These must of course be managed separately
- through a snap-in module to the normal ADS account management MMC interface.
- </para>
-
- <para>
- <indexterm><primary>PDC</primary></indexterm>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>LDAP backend</primary></indexterm>
- Security identifiers used within a domain must be managed to avoid conflict and to preserve integrity.
- In an NT4 domain context, the PDC manages the distribution of all security credentials to the backup
- domain controllers (BDCs). At this time the only passdb backend for a Samba domain controller that is suitable
- for such information is an LDAP backend.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Backup Domain Controller</title>
-
- <para>
- <indexterm><primary>BDC</primary></indexterm>
- <indexterm><primary>read-only access</primary></indexterm>
- <indexterm><primary>security credentials</primary></indexterm>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>group account</primary></indexterm>
- <indexterm><primary>write changes</primary></indexterm>
- <indexterm><primary>directory</primary></indexterm>
- BDCs have read-only access to security credentials that are stored in LDAP.
- Changes in user or group account information are passed by the BDC to the PDC. Only the PDC can write
- changes to the directory.
- </para>
-
- <para>
- IDMAP information can be written directly to the LDAP server so long as all domain controllers
- have access to the master (writable) LDAP server. Samba at this time does not handle LDAP redirects
- in the IDMAP backend. This means that it is is unsafe to use a slave (replicate) LDAP server with
- the IDMAP facility.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Examples of IDMAP Backend Usage</title>
-
-<para>
-<indexterm><primary>Domain Member Server</primary><see>DMS</see></indexterm>
-<indexterm><primary>Domain Member Client</primary><see>DMC</see></indexterm>
-<indexterm><primary>DMS</primary></indexterm>
-<indexterm><primary>DMC</primary></indexterm>
-<indexterm><primary>winbind</primary></indexterm>
-Anyone who wishes to use <command>winbind</command> will find the following example configurations helpful.
-Remember that in the majority of cases <command>winbind</command> is of primary interest for use with
-domain member servers (DMSs) and domain member clients (DMCs).
-</para>
-
- <sect2>
- <title>Default Winbind TDB</title>
-
- <para>
- Two common configurations are used:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Networks that have an NT4 PDC (with or without BDCs) or a Samba PDC (with or without BDCs).
- </para></listitem>
-
- <listitem><para>
- Networks that use MS Windows 200x ADS.
- </para></listitem>
- </itemizedlist>
-
- <sect3>
- <title>NT4-Style Domains (Includes Samba Domains)</title>
-
- <para>
- <link linkend="idmapnt4dms">NT4 Domain Member Server smb.con</link> is a simple example of an NT4 DMS
- &smb.conf; file that shows only the global section.
- </para>
-
-<example id="idmapnt4dms">
-<title>NT4 Domain Member Server smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">MEGANET2</smbconfoption>
-<smbconfoption name="security">DOMAIN</smbconfoption>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfoption name="template primary group">"Domain Users"</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The use of <command>winbind</command> requires configuration of NSS. Edit the <filename>/etc/nsswitch.conf</filename>
- so it includes the following entries:
-<screen>
-...
-passwd: files winbind
-shadow: files winbind
-group: files winbind
-...
-hosts: files [dns] wins
-...
-</screen>
- The use of DNS in the hosts entry should be made only if DNS is used on site.
- </para>
-
- <para>
- The creation of the DMS requires the following steps:
- </para>
-
- <procedure>
- <step><para>
- Create or install an &smb.conf; file with the above configuration.
- </para></step>
-
- <step><para>
- Execute:
-<screen>
-&rootprompt; net rpc join -UAdministrator%password
-Joined domain MEGANET2.
-</screen>
- <indexterm><primary>join</primary></indexterm>
- The success of the join can be confirmed with the following command:
-<screen>
-&rootprompt; net rpc testjoin
-Join to 'MIDEARTH' is OK
-</screen>
- A failed join would report an error message like the following:
- <indexterm><primary>failed join</primary></indexterm>
-<screen>
-&rootprompt; net rpc testjoin
-[2004/11/05 16:34:12, 0] utils/net_rpc_join.c:net_rpc_join_ok(66)
-Join to domain 'MEGANET2' is not valid
-</screen>
- </para></step>
-
- <step><para>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>winbind</primary></indexterm>
- <indexterm><primary>smbd</primary></indexterm>
- Start the <command>nmbd, winbind,</command> and <command>smbd</command> daemons in the order shown.
- </para></step>
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>ADS Domains</title>
-
- <para>
- <indexterm><primary>domain join</primary></indexterm>
- <indexterm><primary>ADS domain</primary></indexterm>
- The procedure for joining an ADS domain is similar to the NT4 domain join, except the &smb.conf; file
- will have the contents shown in <link linkend="idmapadsdms">ADS Domain Member Server smb.conf</link>
- </para>
-
-<example id="idmapadsdms">
-<title>ADS Domain Member Server smb.conf</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">BUTTERNET</smbconfoption>
-<smbconfoption name="netbios name">GARGOYLE</smbconfoption>
-<smbconfoption name="realm">BUTTERNET.BIZ</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="idmap uid">500-10000000</smbconfoption>
-<smbconfoption name="idmap gid">500-10000000</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-<smbconfoption name="winbind nested groups">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>KRB</primary></indexterm>
- <indexterm><primary>kerberos</primary></indexterm>
- <indexterm><primary>/etc/krb5.conf</primary></indexterm>
- <indexterm><primary>MIT</primary></indexterm>
- <indexterm><primary>MIT kerberos</primary></indexterm>
- <indexterm><primary>Heimdal</primary></indexterm>
- <indexterm><primary>Heimdal kerberos</primary></indexterm>
- ADS DMS operation requires use of kerberos (KRB). For this to work, the <filename>krb5.conf</filename>
- must be configured. The exact requirements depends on which version of MIT or Heimdal Kerberos is being
- used. It is sound advice to use only the latest version, which at this time are MIT Kerberos version
- 1.3.5 and Heimdal 0.61.
- </para>
-
- <para>
- The creation of the DMS requires the following steps:
- </para>
-
- <procedure>
- <step><para>
- Create or install an &smb.conf; file with the above configuration.
- </para></step>
-
- <step><para>
- Edit the <filename>/etc/nsswitch.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Execute:
- <indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
-<screen>
-&rootprompt; net ads join -UAdministrator%password
-Joined domain BUTTERNET.
-</screen>
- The success or failure of the join can be confirmed with the following command:
-<screen>
-&rootprompt; net ads testjoin
-Using short domain name -- BUTTERNET
-Joined 'GARGOYLE' to realm 'BUTTERNET.BIZ'
-</screen>
- </para>
-
- <para>
- An invalid or failed join can be detected by executing:
-<screen>
-&rootprompt; net ads testjoin
-GARGOYLE$@'s password:
-[2004/11/05 16:53:03, 0] utils/net_ads.c:ads_startup(186)
- ads_connect: No results returned
-Join to domain is not valid
-</screen>
- <indexterm><primary>error message</primary></indexterm>
- <indexterm><primary>failure</primary></indexterm>
- <indexterm><primary>log level</primary></indexterm>
- <indexterm><primary>identify</primary></indexterm>
- The specific error message may differ from the above because it depends on the type of failure that
- may have occurred. Increase the <parameter>log level</parameter> to 10, repeat the test,
- and then examine the log files produced to identify the nature of the failure.
- </para></step>
-
- <step><para>
- Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
- </para></step>
-
- </procedure>
-
- </sect3>
- </sect2>
-
- <sect2>
- <title>IDMAP_RID with Winbind</title>
-
- <para>
- <indexterm><primary>idmap_rid</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>RID</primary></indexterm>
- <indexterm><primary>IDMAP</primary></indexterm>
- The <command>idmap_rid</command> facility is a new tool that, unlike native winbind, creates a
- predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method
- of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data
- in a central place. The downside is that it can be used only within a single ADS domain and
- is not compatible with trusted domain implementations.
- </para>
-
- <para>
- <indexterm><primary>SID</primary></indexterm>
- <indexterm><primary>allow trusted domains</primary></indexterm>
- <indexterm><primary>idmap uid</primary></indexterm>
- <indexterm><primary>idmap gid</primary></indexterm>
- This alternate method of SID to UID/GID mapping can be achieved using the idmap_rid
- plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the
- RID to a base value specified. This utility requires that the parameter
- <quote>allow trusted domains = No</quote> be specified, as it is not compatible
- with multiple domain environments. The <parameter>idmap uid</parameter> and
- <parameter>idmap gid</parameter> ranges must be specified.
- </para>
-
- <para>
- <indexterm><primary>idmap_rid</primary></indexterm>
- <indexterm><primary>realm</primary></indexterm>
- The idmap_rid facility can be used both for NT4/Samba-style domains and Active Directory.
- To use this with an NT4 domain, do not include the <parameter>realm</parameter> parameter; additionally, the
- method used to join the domain uses the <constant>net rpc join</constant> process.
- </para>
-
- <para>
- An example &smb.conf; file for and ADS domain environment is shown in <link linkend="idmapadsridDMS">ADS
- Domain Member smb.conf using idmap_rid</link>.
- </para>
-
-<example id="idmapadsridDMS">
-<title>ADS Domain Member smb.conf using idmap_rid</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">KPAK</smbconfoption>
-<smbconfoption name="netbios name">BIGJOE</smbconfoption>
-<smbconfoption name="realm">CORP.KPAK.COM</smbconfoption>
-<smbconfoption name="server string">Office Server</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="allow trusted domains">No</smbconfoption>
-<smbconfoption name="idmap backend">idmap_rid:KPAK=500-100000000</smbconfoption>
-<smbconfoption name="idmap uid">500-100000000</smbconfoption>
-<smbconfoption name="idmap gid">500-100000000</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-<smbconfoption name="winbind enum users">No</smbconfoption>
-<smbconfoption name="winbind enum groups">No</smbconfoption>
-<smbconfoption name="winbind nested groups">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>large domain</primary></indexterm>
- <indexterm><primary>Active Directory</primary></indexterm>
- <indexterm><primary>response</primary></indexterm>
- <indexterm><primary>getent</primary></indexterm>
- In a large domain with many users it is imperative to disable enumeration of users and groups.
- For example, at a site that has 22,000 users in Active Directory the winbind-based user and
- group resolution is unavailable for nearly 12 minutes following first startup of
- <command>winbind</command>. Disabling enumeration resulted in instantaneous response.
- The disabling of user and group enumeration means that it will not be possible to list users
- or groups using the <command>getent passwd</command> and <command>getent group</command>
- commands. It will be possible to perform the lookup for individual users, as shown in the following procedure.
- </para>
-
- <para>
- <indexterm><primary>NSS</primary></indexterm>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The use of this tool requires configuration of NSS as per the native use of winbind. Edit the
- <filename>/etc/nsswitch.conf</filename> so it has the following parameters:
-<screen>
-...
-passwd: files winbind
-shadow: files winbind
-group: files winbind
-...
-hosts: files wins
-...
-</screen>
- </para>
-
- <para>
- The following procedure can use the idmap_rid facility:
- </para>
-
- <procedure>
- <step><para>
- Create or install an &smb.conf; file with the above configuration.
- </para></step>
-
- <step><para>
- Edit the <filename>/etc/nsswitch.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Execute:
-<screen>
-&rootprompt; net ads join -UAdministrator%password
-Using short domain name -- KPAK
-Joined 'BIGJOE' to realm 'CORP.KPAK.COM'
-</screen>
- </para>
-
- <para>
- <indexterm><primary>failed join</primary></indexterm>
- An invalid or failed join can be detected by executing:
-<screen>
-&rootprompt; net ads testjoin
-BIGJOE$@'s password:
-[2004/11/05 16:53:03, 0] utils/net_ads.c:ads_startup(186)
- ads_connect: No results returned
-Join to domain is not valid
-</screen>
- The specific error message may differ from the above because it depends on the type of failure that
- may have occurred. Increase the <parameter>log level</parameter> to 10, repeat the test,
- and then examine the log files produced to identify the nature of the failure.
- </para></step>
-
- <step><para>
- Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
- </para></step>
-
- <step><para>
- Validate the operation of this configuration by executing:
- <indexterm><primary></primary></indexterm>
-<screen>
-&rootprompt; getent passwd administrator
-administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
-</screen>
- </para></step>
- </procedure>
-
- </sect2>
-
- <sect2>
- <title>IDMAP Storage in LDAP Using Winbind</title>
-
- <para>
- <indexterm><primary>ADAM</primary></indexterm>
- <indexterm><primary>ADS</primary></indexterm>
- The storage of IDMAP information in LDAP can be used with both NT4/Samba-style domains and
- ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any
- standards-complying LDAP server can be used. It is therefore possible to deploy this IDMAP
- configuration using the Sun iPlanet LDAP server, Novell eDirectory, Microsoft ADS plus ADAM,
- and so on.
- </para>
-
- <para>
- An example is for an ADS domain is shown in <link linkend="idmapldapDMS">ADS Domain Member Server using
- LDAP</link>.
- </para>
-
-<example id="idmapldapDMS">
-<title>ADS Domain Member Server using LDAP</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">SNOWSHOW</smbconfoption>
-<smbconfoption name="netbios name">GOODELF</smbconfoption>
-<smbconfoption name="realm">SNOWSHOW.COM</smbconfoption>
-<smbconfoption name="server string">Samba Server</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="log level">1 ads:10 auth:10 sam:10 rpc:10</smbconfoption>
-<smbconfoption name="ldap admin dn">cn=Manager,dc=SNOWSHOW,dc=COM</smbconfoption>
-<smbconfoption name="ldap idmap suffix">ou=Idmap</smbconfoption>
-<smbconfoption name="ldap suffix">dc=SNOWSHOW,dc=COM</smbconfoption>
-<smbconfoption name="idmap backend">ldap:ldap://ldap.snowshow.com</smbconfoption>
-<smbconfoption name="idmap uid">150000-550000</smbconfoption>
-<smbconfoption name="idmap gid">150000-550000</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>realm</primary></indexterm>
- In the case of an NT4 or Samba-style domain the <parameter>realm</parameter> is not used, and the
- command used to join the domain is <command>net rpc join</command>. The above example also demonstrates
- advanced error-reporting techniques that are documented in <link linkend="dbglvl">Reporting Bugs</link>.
- </para>
-
- <para>
- <indexterm><primary>MIT kerberos</primary></indexterm>
- <indexterm><primary>Heimdal kerberos</primary></indexterm>
- <indexterm><primary>/etc/krb5.conf</primary></indexterm>
- Where MIT kerberos is installed (version 1.3.4 or later), edit the <filename>/etc/krb5.conf</filename>
- file so it has the following contents:
-<screen>
-[logging]
- default = FILE:/var/log/krb5libs.log
- kdc = FILE:/var/log/krb5kdc.log
- admin_server = FILE:/var/log/kadmind.log
-
-[libdefaults]
- default_realm = SNOWSHOW.COM
- dns_lookup_realm = false
- dns_lookup_kdc = true
-
-[appdefaults]
- pam = {
- debug = false
- ticket_lifetime = 36000
- renew_lifetime = 36000
- forwardable = true
- krb4_convert = false
- }
-</screen>
- </para>
-
- <para>
- Where Heimdal kerberos is installed, edit the <filename>/etc/krb5.conf</filename>
- file so it is either empty (i.e., no contents) or it has the following contents:
-<screen>
-[libdefaults]
- default_realm = SNOWSHOW.COM
- clockskew = 300
-
-[realms]
- SNOWSHOW.COM = {
- kdc = ADSDC.SHOWSHOW.COM
- }
-
-[domain_realm]
- .snowshow.com = SNOWSHOW.COM
-</screen>
- </para>
-
- <note><para>
- Samba cannot use the Heimdal libraries if there is no <filename>/etc/krb5.conf</filename> file.
- So long as there is an empty file, the Heimdal kerberos libraries will be usable. There is no
- need to specify any settings because Samba, using the Heimdal libraries, can figure this out automatically.
- </para></note>
-
- <para>
- Edit the NSS control file <filename>/etc/nsswitch.conf</filename> so it has the following entries:
-<screen>
-...
-passwd: files ldap
-shadow: files ldap
-group: files ldap
-...
-hosts: files wins
-...
-</screen>
- </para>
-
- <para>
- <indexterm><primary>PADL</primary></indexterm>
- <indexterm><primary>/etc/ldap.conf</primary></indexterm>
- You will need the <ulink url="http://www.padl.com">PADL</ulink> <command>nss_ldap</command>
- tool set for this solution. Configure the <filename>/etc/ldap.conf</filename> file so it has
- the information needed. The following is an example of a working file:
-<screen>
-host 192.168.2.1
-base dc=snowshow,dc=com
-binddn cn=Manager,dc=snowshow,dc=com
-bindpw not24get
-
-pam_password exop
-
-nss_base_passwd ou=People,dc=snowshow,dc=com?one
-nss_base_shadow ou=People,dc=snowshow,dc=com?one
-nss_base_group ou=Groups,dc=snowshow,dc=com?one
-ssl no
-</screen>
- </para>
-
- <para>
- The following procedure may be followed to effect a working configuration:
- </para>
-
- <procedure>
- <step><para>
- Configure the &smb.conf; file as shown above.
- </para></step>
-
- <step><para>
- Create the <filename>/etc/krb5.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Configure the <filename>/etc/nsswitch.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Download, build, and install the PADL nss_ldap tool set. Configure the
- <filename>/etc/ldap.conf</filename> file as shown above.
- </para></step>
-
- <step><para>
- Configure an LDAP server and initialize the directory with the top-level entries needed by IDMAP,
- shown in the following LDIF file:
-<screen>
-dn: dc=snowshow,dc=com
-objectClass: dcObject
-objectClass: organization
-dc: snowshow
-o: The Greatest Snow Show in Singapore.
-description: Posix and Samba LDAP Identity Database
-
-dn: cn=Manager,dc=snowshow,dc=com
-objectClass: organizationalRole
-cn: Manager
-description: Directory Manager
-
-dn: ou=Idmap,dc=snowshow,dc=com
-objectClass: organizationalUnit
-ou: idmap
-</screen>
- </para></step>
-
- <step><para>
- Execute the command to join the Samba DMS to the ADS domain as shown here:
-<screen>
-&rootprompt; net ads testjoin
-Using short domain name -- SNOWSHOW
-Joined 'GOODELF' to realm 'SNOWSHOW.COM'
-</screen>
- </para></step>
-
- <step><para>
- Store the LDAP server access password in the Samba <filename>secrets.tdb</filename> file as follows:
-<screen>
-&rootprompt; smbpasswd -w not24get
-</screen>
- </para></step>
-
- <step><para>
- Start the <command>nmbd</command>, <command>winbind</command>, and <command>smbd</command> daemons in the order shown.
- </para></step>
- </procedure>
-
- <para>
- <indexterm><primary>diagnostic</primary></indexterm>
- Follow the diagnositic procedures shown earlier in this chapter to identify success or failure of the join.
- In many cases a failure is indicated by a silent return to the command prompt with no indication of the
- reason for failure.
- </para>
-
- </sect2>
-
- <sect2>
- <title>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</title>
-
- <para>
- <indexterm><primary>rfc2307bis</primary></indexterm>
- <indexterm><primary>schema</primary></indexterm>
- The use of this method is messy. The information provided in the following is for guidance only
- and is very definitely not complete. This method does work; it is used in a number of large sites
- and has an acceptable level of performance.
- </para>
-
- <para>
- An example &smb.conf; file is shown in <link linkend="idmaprfc2307">ADS Domain Member Server using
-RFC2307bis Schema Extension Date via NSS</link>.
- </para>
-
-<example id="idmaprfc2307">
-<title>ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</title>
-<smbconfblock>
-<smbconfcomment>Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">BOBBY</smbconfoption>
-<smbconfoption name="realm">BOBBY.COM</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-<smbconfoption name="idmap uid">150000-550000</smbconfoption>
-<smbconfoption name="idmap gid">150000-550000</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-<smbconfoption name="winbind cache time">5</smbconfoption>
-<smbconfoption name="winbind use default domain">Yes</smbconfoption>
-<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
-<smbconfoption name="winbind nested groups">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>nss_ldap</primary></indexterm>
- The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary
- to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the
- following:
-<screen>
-./configure --enable-rfc2307bis --enable-schema-mapping
-make install
-</screen>
- </para>
-
- <para>
- <indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- The following <filename>/etc/nsswitch.conf</filename> file contents are required:
-<screen>
-...
-passwd: files ldap
-shadow: files ldap
-group: files ldap
-...
-hosts: files wins
-...
-</screen>
- </para>
-
- <para>
- <indexterm><primary>/etc/ldap.conf</primary></indexterm>
- <indexterm><primary>nss_ldap</primary></indexterm>
- The <filename>/etc/ldap.conf</filename> file must be configured also. Refer to the PADL documentation
- and source code for nss_ldap to specific instructions.
- </para>
-
- <para>
- The next step involves preparation of the ADS schema. This is briefly discussed in the remaining
- part of this chapter.
- </para>
-
- <sect3>
- <title>IDMAP, Active Directory, and MS Services for UNIX 3.5</title>
-
- <para>
- <indexterm><primary>SFU</primary></indexterm>
- The Microsoft Windows Service for UNIX (SFU) version 3.5 is available for free
- <ulink url="http://www.microsoft.com/windows/sfu/">download</ulink>
- from the Microsoft Web site. You will need to download this tool and install it following
- Microsoft instructions.
- </para>
-
- </sect3>
-
- <sect3>
- <title>IDMAP, Active Directory and AD4UNIX</title>
-
- <para>
- Instructions for obtaining and installing the AD4UNIX tool set can be found from the
- <ulink url="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?LDAP01/An_Alternative_Approach">
- Geekcomix</ulink> Web site.
- </para>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="install">
-<chapterinfo>
- &author.tridge;
- &author.jelmer;
- &author.jht;
- &author.kauer;
- &author.danshearer;
- <!-- Isn't some of this written by others as well? -->
-
-</chapterinfo>
-
-<title>How to Install and Test SAMBA</title>
-
-<sect1>
- <title>Obtaining and Installing Samba</title>
-
- <para>
- <indexterm><primary>packages</primary></indexterm>
- Binary packages of Samba are included in almost any Linux or UNIX distribution. There are also some
- packages available at <ulink url="https://www.samba.org/">the Samba home page</ulink>. Refer to the manual of your
- operating system for details on installing packages for your specific operating system.
- </para>
-
- <para>
- <indexterm><primary>compile</primary></indexterm>
- If you need to compile Samba from source, check <link linkend="compiling">How to Compile Samba</link>.
- </para>
-
-</sect1>
-
-<sect1>
- <title>Configuring Samba (smb.conf)</title>
-
- <para>
- <indexterm><primary>/etc/samba/smb.conf</primary></indexterm>
- <indexterm><primary>SWAT</primary></indexterm>
- Samba's configuration is stored in the &smb.conf; file, which usually resides in
- <filename>/etc/samba/smb.conf</filename> or <filename>/usr/local/samba/lib/smb.conf</filename>. You can either
- edit this file yourself or do it using one of the many graphical tools that are available, such as the
- Web-based interface SWAT, that is included with Samba.
- </para>
-
- <sect2>
- <title>Configuration File Syntax</title>
-
- <para>
- <indexterm><primary>section name</primary></indexterm>
- The &smb.conf; file uses the same syntax as the various old <filename>.ini</filename> files in Windows
- 3.1: Each file consists of various sections, which are started by putting the section name between brackets
- (<literal>[]</literal>) on a new line. Each contains zero or more key/value pairs separated by an equality
- sign (<literal>=</literal>). The file is just a plaintext file, so you can open and edit it with your favorite
- editing tool.
- </para>
-
- <para>
- <indexterm><primary>meta-service</primary></indexterm>
- <indexterm><primary>print</primary><secondary>queue</secondary></indexterm>
- <indexterm><primary>share</primary></indexterm>
- <indexterm><primary>spooler.</primary></indexterm>
- <indexterm><primary>print</primary><secondary>spooler</secondary></indexterm>
- <indexterm><primary>spool</primary><secondary>directory</secondary></indexterm>
- Each section in the &smb.conf; file represents either a share or a meta-service on the Samba server. The
- section <literal>[global]</literal> is special, since it contains settings that apply to the whole Samba
- server. Samba supports a number of meta-services, each of which serves its own purpose. For example, the
- <literal>[homes]</literal> share is a meta-service that causes Samba to provide a personal home share for
- each user. The <literal>[printers]</literal> share is a meta-service that establishes print queue support
- and that specifies the location of the intermediate spool directory into which print jobs are received
- from Windows clients prior to being dispatched to the UNIX/Linux print spooler.
- </para>
-
- <para>
-<indexterm><primary>printers</primary></indexterm>
-<indexterm><primary>meta-service</primary></indexterm>
-<indexterm><primary>printcap</primary></indexterm>
-<indexterm><primary>lpstat</primary></indexterm>
-<indexterm><primary>CUPS API</primary></indexterm>
-<indexterm><primary>browseable</primary></indexterm>
- The <literal>printers</literal> meta-service will cause every printer that is either specified in a
- <literal>printcap</literal> file, via the <command>lpstat</command>, or via the CUPS API, to be
- published as a shared print queue. The <literal>printers</literal> stanza in the &smb.conf; file can
- be set as not browseable. If it is set to be browseable, then it will be visible as if it is a share.
- That makes no sense given that this meta-service is responsible only for making UNIX system printers
- available as Windows print queues. If a <literal>comment</literal> parameter is specified, the value
- of it will be displayed as part of the printer name in Windows Explorer browse lists.
- </para>
-
- <para>
- <indexterm><primary>stanza</primary></indexterm>
- Each section of the &smb.conf; file that specifies a share, or a meta-service, is called a stanza.
- The <literal>global</literal> stanza specifies settings that affect all the other stanzas in the
- &smb.conf; file. Configuration parameters are documented in the &smb.conf; man page. Some parameters
- can be used only in the <literal>global</literal> stanza, some only in share or meta-service stanzas,
- and some can be used globally or just within a share or meta-service stanza.
- </para>
-
- <para>
- <indexterm><primary>minimal</primary><secondary>configuration</secondary></indexterm>
- <link linkend="smbconfminimal">A minimal smb.conf</link> contains a very minimal &smb.conf;.
- <indexterm><primary>minimal configuration</primary></indexterm>
- </para>
-
- <example id="smbconfminimal">
- <title>A minimal smb.conf</title>
- <smbconfblock>
-
- <smbconfsection name="[global]"/>
- <smbconfoption name="workgroup">WKG</smbconfoption>
- <smbconfoption name="netbios name">MYNAME</smbconfoption>
- <smbconfsection name="[share1]"/>
- <smbconfoption name="path">/tmp</smbconfoption>
-
- <smbconfsection name="[share2]"/>
- <smbconfoption name="path">/my_shared_folder</smbconfoption>
- <smbconfoption name="comment">Some random files</smbconfoption>
- </smbconfblock>
- </example>
-
-</sect2>
-
-<sect2 id="tdbdocs">
- <title>TDB Database File Information</title>
-
- <para>
- This section contains brief descriptions of the databases that are used by Samba.
- </para>
-
- <para>
-<indexterm><primary>tdb file locations</primary></indexterm>
- The directory in which Samba stores the tdb files is determined by compile-time directives. Samba stores
- tdb files in two locations. The best way to determine these locations is to execute the following
- command:
-<screen>
-&rootprompt; smbd -b | grep PRIVATE_DIR
- PRIVATE_DIR: /etc/samba/private
-</screen>
- This means that the confidential tdb files are stored in the <filename>/etc/samba/private</filename>
- directory. Samba also uses a number of tdb files that contain more mundane data. The location of
- these files can be found by executing:
-<screen>
-&rootprompt; smbd -b | grep LOCKDIR
- LOCKDIR: /var/lib/samba
-</screen>
- Therefore the remaining control files will, in the example shown, be stored in the
- <filename>/var/lib/samba</filename> directory.
- </para>
-
- <para>
-<indexterm><primary>tdb file descriptions</primary></indexterm>
- The persistent tdb files are described in <link linkend="tdbpermfiledesc">the Persistent TDB File
- Descriptions table</link>. All persistent tdb files should be regularly backed up. Use the
- <command>tdbbackup</command> utility to backup the tdb files. All persistent tdb files must be
- preserved during machine migrations, updates and upgrades.
- </para>
-
- <para>
- The temporary tdb files do not need to be backed up, nor do they need to be preseved across machine
- migrations, updates or upgrades. The temporary tdb files are described in <link linkend="tdbtempfiledesc">
- the Temporary TDB File Descriptions</link>.
- </para>
-
- <table frame='all' id="tdbpermfiledesc"><title>Persistent TDB File Descriptions</title>
- <tgroup cols='2'>
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry align="left">Name</entry>
- <entry align="justify">Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>account_policy</entry>
- <entry><para>Samba/NT account policy settings, includes password expiration settings.</para></entry>
- </row>
- <row>
- <entry>group_mapping</entry>
- <entry><para>Mapping table from Windows groups/SID to UNIX groups.</para></entry>
- </row>
- <row>
- <entry>ntdrivers</entry>
- <entry><para>Stores per-printer installed driver information.</para></entry>
- </row>
- <row>
- <entry>ntforms</entry>
- <entry><para>Stores per-printer installed forms information.</para></entry>
- </row>
- <row>
- <entry>ntprinters</entry>
- <entry><para>Stores the per-printer devmode configuration settings.</para></entry>
- </row>
- <row>
- <entry>passdb</entry>
- <entry><para>
- Exists only when the tdbsam passwd backend is used. This file stores the
- SambaSAMAccount information. Note: This file requires that user POSIX account information is
- available from either the /etc/passwd file, or from an alternative system source.
- </para></entry>
- </row>
- <row>
- <entry>registry</entry>
- <entry><para>
- Read-only Samba database of a Windows registry skeleton that provides support for exporting
- various database tables via the winreg RPCs.
- </para></entry>
- </row>
- <row>
- <entry>secrets</entry>
- <entry><para>
- This file stores the Workgroup/Domain/Machine SID, the LDAP directory update password, and
- a further collection of critical environmental data that is necessary for Samba to operate
- correctly. This file contains very sensitive information that must be protected. It is stored
- in the PRIVATE_DIR directory.
- </para></entry>
- </row>
- <row>
- <entry>share_info</entry>
- <entry><para>Stores per-share ACL information.</para></entry>
- </row>
- <row>
- <entry>winbindd_idmap</entry>
- <entry><para>Winbindd's local IDMAP database.</para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <table frame='all' id="tdbtempfiledesc"><title>Temporary TDB File Descriptions</title>
- <tgroup cols='3'>
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry align="left">Name</entry>
- <entry align="justify">Description</entry>
- <entry align="center">Backup</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>brlock</entry>
- <entry><para>Byte-range locking information.</para></entry>
- <entry>No</entry>
- </row>
- <row>
- <entry>connections</entry>
- <entry><para>A temporary cache for current connection information used to enforce max connections.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>eventlog/*tdb</entry>
- <entry><para>Records of eventlog entries. In most circumstances this is just a cache of system logs.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>gencache</entry>
- <entry><para>Generic caching database for dead WINS servers and trusted domain data.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>login_cache</entry>
- <entry><para>A temporary cache for login information, in particular bad password attempts.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>messages</entry>
- <entry><para>Temporary storage of messages being processed by smbd.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>netsamlogon_cache</entry>
- <entry><para>Caches user net_info_3 structure data from net_samlogon requests (as a domain member).</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>perfmon/*.tdb</entry>
- <entry><para>Performance counter information.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>printing/*.tdb</entry>
- <entry><para>Cached output from lpq command created on a per-print-service basis.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>schannel_store</entry>
- <entry><para>
- A confidential file, stored in the PRIVATE_DIR, containing crytographic connection
- information so that clients that have temporarily disconnected can reconnect without
- needing to renegotiate the connection setup process.
- </para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>sessionid</entry>
- <entry><para>Temporary cache for miscellaneous session information and for utmp handling.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>unexpected</entry>
- <entry><para>Stores packets received for which no process is actively listening.</para></entry>
- <entry>no</entry>
- </row>
- <row>
- <entry>winbindd_cache</entry>
- <entry><para>Cache of Identity information received from an NT4 domain or from ADS. Includes user
- lists, etc.</para></entry>
- <entry>yes</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
-</sect2>
-
-<sect2>
- <title>Starting Samba</title>
-
- <para>
- <indexterm><primary>daemon</primary></indexterm>
- Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services.
- An example of a service is the Apache Web server for which the daemon is called <command>httpd</command>. In the case of Samba there
- are three daemons, two of which are needed as a minimum.
- </para>
-
- <para>
- The Samba server is made up of the following daemons:
- </para>
-
- <variablelist>
- <varlistentry><term>nmbd</term>
- <listitem><para>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
- This daemon handles all name registration and resolution requests. It is the primary vehicle involved
- in network browsing. It handles all UDP-based protocols. The <command>nmbd</command> daemon should
- be the first command started as part of the Samba startup process.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>smbd</term>
- <listitem><para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
- This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
- manages local authentication. It should be started immediately following the startup of <command>nmbd</command>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>winbindd</term>
- <listitem><para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
- This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
- Samba has trust relationships with another domain. The <command>winbindd</command> daemon will check the
- &smb.conf; file for the presence of the <parameter>idmap uid</parameter> and <parameter>idmap gid</parameter>
- parameters. If they are are found, <command>winbindd</command> will use the values specified for
- for UID and GID allocation. If these parameters are not specified, <command>winbindd</command>
- will start but it will not be able to allocate UIDs or GIDs.
- </para></listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- <indexterm><primary>startup</primary><secondary>process</secondary></indexterm>
- When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its
- integration into the platform as a whole. Please refer to your operating system platform administration manuals for
- specific information pertaining to correct management of Samba startup.
- </para>
-
-</sect2>
-
-<sect2>
- <title>Example Configuration</title>
-
- <para>
- <indexterm><primary>examples</primary></indexterm>
- <indexterm><primary>source code</primary></indexterm>
- <indexterm><primary>distribution</primary></indexterm>
- <indexterm><primary>tarball</primary></indexterm>
- <indexterm><primary>package</primary></indexterm>
- There are sample configuration files in the examples subdirectory in the source code distribution tarball
- package. It is suggested you read them carefully so you can see how the options go together in practice. See
- the man page for all the options. It might be worthwhile to start out with the
- <filename>smb.conf.default</filename> configuration file and adapt it to your needs. It contains plenty of comments.
- </para>
-
- <para>
- <indexterm><primary>simplest</primary><secondary>configuration</secondary></indexterm>
- The simplest useful configuration file would contain something like that shown in
- <link linkend="simple-example">Another simple smb.conf File</link>.
- <indexterm><primary>simple configuration</primary></indexterm>
- </para>
-
-<example id="simple-example">
-<title>Another simple smb.conf File</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-
-<smbconfsection name="[homes]"/>
-<smbconfoption name="guest ok">no</smbconfoption>
-<smbconfoption name="read only">no</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
- <indexterm><primary>connections</primary></indexterm>
- <indexterm><primary>account</primary></indexterm>
- <indexterm><primary>login name</primary></indexterm>
- <indexterm><primary>service name</primary></indexterm>
- This will allow connections by anyone with an account on the server, using either
- their login name or <smbconfsection name="homes"/> as the service name.
- (Note: The workgroup that Samba should appear in must also be set. The default
- workgroup name is WORKGROUP.)
- </para>
-
- <para>
- <indexterm><primary>smbd</primary></indexterm>
- Make sure you put the &smb.conf; file in the correct place. Note, the correct location of this file
- depends on how the binary files were built. You can discover the correct location by executing from
- the directory that contains the <command>smbd</command> command file:
-<screen>
-&rootprompt; smbd -b | grep smb.conf
-</screen>
- </para>
-
- <para>
- <indexterm><primary>security</primary><secondary>settings</secondary></indexterm>
- For more information about security settings for the <smbconfsection name="[homes]"/> share, please refer to
- <link linkend="securing-samba">Securing Samba</link>.
- </para>
-
-<sect3>
- <title>Test Your Config File with <command>testparm</command></title>
-
- <para>
- <indexterm><primary>validate</primary></indexterm>
- <indexterm><primary>testparm</primary></indexterm>
- <indexterm><primary>misconfigurations</primary></indexterm>
- It's important to validate the contents of the &smb.conf; file using the &testparm; program.
- If testparm runs correctly, it will list the loaded services. If not, it will give an error message.
- Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command:
- <screen>
- &rootprompt; testparm /etc/samba/smb.conf
- </screen>
- Testparm will parse your configuration file and report any unknown parameters or incorrect syntax.
- It also performs a check for common misconfigurations and will issue a warning if one is found.
- </para>
-
- <para>
- Always run testparm again whenever the &smb.conf; file is changed!
- </para>
-
- <para>
- <indexterm><primary>smbd</primary></indexterm>
- <indexterm><primary>nmbd</primary></indexterm>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>configuration</primary><secondary>documentation</secondary></indexterm>
- The &smb.conf; file is constantly checked by the Samba daemons <command>smbd</command> and every instance of
- itself that it spawns, <command>nmbd</command> and <command>winbindd</command>. It is good practice to
- keep this file as small as possible. Many administrators prefer to document Samba configuration settings
- and thus the need to keep this file small goes against good documentation wisdom. One solution that may
- be adopted is to do all documentation and configuration in a file that has another name, such as
- <filename>smb.conf.master</filename>. The <command>testparm</command> utility can be used to generate a
- fully optimized &smb.conf; file from this master configuration and documentation file as shown here:
-<screen>
-&rootprompt; testparm -s smb.conf.master > smb.conf
-</screen>
- This administrative method makes it possible to maintain detailed configuration change records while at
- the same time keeping the working &smb.conf; file size to the minimum necessary.
- </para>
-
-</sect3>
-</sect2>
-
-<sect2>
- <title>SWAT</title>
-
- <para>
- <indexterm><primary>swat</primary></indexterm>
- SWAT is a Web-based interface that can be used to facilitate the configuration of Samba. SWAT might not
- be available in the Samba package that shipped with your platform, but in a separate package. If you need to build SWAT please read the SWAT man page regarding compilation, installation, and
- configuration of SWAT from the source code.
- </para>
-
- <para>
- To launch SWAT, just run your favorite Web browser and point it to
- <ulink url="http://localhost:901/" noescape="1">http://localhost:901/</ulink>.
- Replace <replaceable>localhost</replaceable> with the name of the computer on which
- Samba is running if that is a different computer than your browser.
- </para>
-
- <para>
- SWAT can be used from a browser on any IP-connected machine, but be aware that connecting from a remote
- machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear.
- </para>
-
- <para>
- Please note that re-writing the configuration file using SWAT will
- remove all comments!
- More information about SWAT can be found in <link linkend="SWAT">The Samba Web Administration Tool</link>.
- </para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
- <title>List Shares Available on the Server</title>
-
- <para>
- To list shares that are available from the configured Samba server, execute the
- following command:
- </para>
-
-<para><screen>
-&prompt;<userinput>smbclient -L <replaceable>yourhostname</replaceable></userinput>
-</screen></para>
-
- <para>
- You should see a list of shares available on your server. If you do not, then
- something is incorrectly configured. This method can also be used to see what shares
- are available on other SMB servers, such as Windows 2000.
- </para>
-
- <para>
- If you choose user-level security, you may find that Samba requests a password
- before it will list the shares. See the <command>smbclient</command> man page for details.
- You can force it to list the shares without a password by adding the option
- <option>-N</option> to the command line.
- </para>
-</sect1>
-
-<sect1>
- <title>Connect with a UNIX Client</title>
-
- <para>
- Enter the following command:
-<screen>
-&prompt;<userinput>smbclient <replaceable> //yourhostname/aservice</replaceable></userinput>
-</screen></para>
-
- <para>Typically <replaceable>yourhostname</replaceable> is the name of the host on which &smbd;
- has been installed. The <replaceable>aservice</replaceable> is any service that has been defined in the &smb.conf;
- file. Try your username if you just have a <smbconfsection name="[homes]"/> section in the &smb.conf; file.</para>
-
- <para>Example: If the UNIX host is called <replaceable>bambi</replaceable> and a valid login name
- is <replaceable>fred</replaceable>, you would type:</para>
-
-<para><screen>
-&prompt;<userinput>smbclient //<replaceable>bambi</replaceable>/<replaceable>fred</replaceable></userinput>
-</screen></para>
-</sect1>
-
-<sect1>
- <title>Connect from a Remote SMB Client</title>
-
- <para>
- Now that Samba is working correctly locally, you can try to access it from other clients. Within a few
- minutes, the Samba host should be listed in the Network Neighborhood on all Windows clients of its subnet.
- Try browsing the server from another client or "mounting" it.
- </para>
-
- <para>
- Mounting disks from a DOS, Windows, or OS/2 client can be done by running a command such as:
-<screen>
-&dosprompt;<userinput>net use m: \\servername\service</userinput>
-</screen>
- Where the drive letter m: is any available drive letter. It is important to double-check that the
- service (share) name that you used does actually exist.
- </para>
-
- <para>
- Try printing, for example,
-<screen>
-&dosprompt;<userinput>net use lpt1: \\servername\spoolservice</userinput>
-</screen>
- The <literal>spoolservice</literal> is the name of the printer (actually the print queue) on the target
- server. This will permit all print jobs that are captured by the lpt1: port on the Windows client to
- be sent to the printer that owns the spoolservice that has been specified.
- </para>
-
-<para>
-<screen>&dosprompt;<userinput>print filename</userinput>
-</screen></para>
-
- <sect2>
- <title>What If Things Don't Work?</title>
-
- <para>
- You might want to read <link linkend="diagnosis">The Samba Checklist</link>. If you are still
- stuck, refer to <link linkend="problems">Analyzing and Solving Samba Problems</link>. Samba has
- been successfully installed at thousands of sites worldwide. It is unlikely that your particular problem is
- unique, so it might be productive to perform an Internet search to see if someone else has encountered your
- problem and has found a way to overcome it.
- </para>
-
- <para>
- If you are new to Samba, and particularly if you are new to Windows networking, or to UNIX/Linux,
- the book <quote>Samba-3 by Example</quote> will help you to create a validated network environment.
- Simply choose from the first five chapters the network design that most closely matches site needs,
- then follow the simple step-by-step procedure to deploy it. Later, when you have a working network
- you may well want to refer back to this book for further insight into opportunities for improvement.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Still Stuck?</title>
-
- <para>
- The best advice under the stress of abject frustration is to cool down! That may be challenging
- of itself, but while you are angry or annoyed your ability to seek out a solution is somewhat
- undermined. A cool head clears the way to finding the answer you are looking for. Just remember,
- every problem has a solution &smbmdash; there is a good chance that someone else has found it
- even though you can't right now. That will change with time, patience and learning.
- </para>
-
- <para>
- Now that you have cooled down a bit, please refer to <link linkend="diagnosis">the Samba Checklist</link>
- for a process that can be followed to identify the cause of your problem.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-The following questions and issues are raised repeatedly on the Samba mailing list.
-</para>
-
-<sect2>
- <title>Large Number of smbd Processes</title>
-
- <para>
- Samba consists of three core programs: &nmbd;, &smbd;, and &winbindd;. &nmbd; is the name server message daemon,
- &smbd; is the server message daemon, and &winbindd; is the daemon that handles communication with domain controllers.
- </para>
-
- <para>
- If Samba is <emphasis>not</emphasis> running as a WINS server, then there will be one single instance of
- &nmbd; running on your system. If it is running as a WINS server, then there will be
- two instances &smbmdash; one to handle the WINS requests.
- </para>
-
- <para>
- &smbd; handles all connection requests. It spawns a new process for each client
- connection made. That is why you may see so many of them, one per client connection.
- </para>
-
- <para>
- &winbindd; will run as many processes depending in part on how many
- domains it needs to contact.
- </para>
-
- </sect2>
-
- <sect2>
- <title><quote><errorname>The network name cannot be found</errorname></quote></title>
-
- <para>
- This error can be caused by one of these misconfigurations:
- </para>
-
- <itemizedlist>
- <listitem><para>You specified a nonexisting path
- for the share in &smb.conf;.</para></listitem>
-
- <listitem><para>The user you are trying to access the share with does not
- have sufficient permissions to access the path for
- the share. Both read (r) and access (x) should be possible.</para></listitem>
-
- <listitem><para>The share you are trying to access does not exist.</para></listitem>
- </itemizedlist>
-
- </sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="integrate-ms-networks">
-
-<chapterinfo>
- &author.jht;
- <pubdate> (Jan 01 2001) </pubdate>
-</chapterinfo>
-
-<title>Integrating MS Windows Networks with Samba</title>
-
-<para>
-<indexterm><primary>NetBIOS</primary></indexterm>
-This chapter deals with NetBIOS over TCP/IP name to IP address resolution. If
-your MS Windows clients are not configured to use NetBIOS over TCP/IP, then this
-section does not apply to your installation. If your installation involves the use of
-NetBIOS over TCP/IP, then this chapter may help you to resolve networking problems.
-</para>
-
-<note>
-<para>
-<indexterm><primary>NetBEUI</primary></indexterm>
-<indexterm><primary>LLC</primary></indexterm>
-NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
-over Logical Link Control (LLC). On modern networks it is highly advised
-to not run NetBEUI at all. Note also that there is no such thing as
-NetBEUI over TCP/IP &smbmdash; the existence of such a protocol is a complete
-and utter misapprehension.
-</para>
-</note>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-Many MS Windows network administrators have never been exposed to basic TCP/IP
-networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and
-Linux administrators have not been exposed to the intricacies of MS Windows TCP/IP-based
-networking (and may have no desire to be, either).
-</para>
-
-<para>
-This chapter gives a short introduction to the basics of how a name can be resolved to
-its IP address for each operating system environment.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Background Information</title>
-
-<para>
-<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
-<indexterm><primary>UDP port 137</primary></indexterm>
-<indexterm><primary>TCP port 139</primary></indexterm>
-<indexterm><primary>TCP port 445</primary></indexterm>
-<indexterm><primary>UDP port 137</primary></indexterm>
-Since the introduction of MS Windows 2000, it is possible to run MS Windows networking
-without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
-name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
-TCP/IP is disabled on MS Windows 2000 and later clients, then only the TCP port 445 is
-used, and the UDP port 137 and TCP port 139 are not.
-</para>
-
-<note>
-<para>
-When using Windows 2000 or later clients, if NetBIOS over TCP/IP is not disabled, then
-the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
-Name Service, or WINS), TCP port 139, and TCP port 445 (for actual file and print traffic).
-</para>
-</note>
-
-<para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>DDNS</primary></indexterm>
-<indexterm><primary>SRV RR</primary></indexterm>
-<indexterm><primary>IXFR</primary></indexterm>
-<indexterm><primary>DHCP</primary></indexterm>
-When NetBIOS over TCP/IP is disabled, the use of DNS is essential. Most installations that disable NetBIOS
-over TCP/IP today use MS Active Directory Service (ADS). ADS requires
-<indexterm><primary>DNS</primary><secondary>Dynamic</secondary></indexterm> dynamic DNS with Service Resource
-Records (SRV RR) and with Incremental Zone Transfers (IXFR). <indexterm><primary>DHCP</primary></indexterm>
-Use of DHCP with ADS is recommended as a further means of maintaining central control over the client
-workstation network configuration.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Name Resolution in a Pure UNIX/Linux World</title>
-
-<para>
-The key configuration files covered in this section are:
-</para>
-
-<indexterm><primary>/etc/hosts</primary></indexterm>
-<indexterm><primary>/etc/resolv.conf</primary></indexterm>
-<indexterm><primary>/etc/host.conf</primary></indexterm>
-<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
-
-<itemizedlist>
- <listitem><para><filename>/etc/hosts</filename></para></listitem>
- <listitem><para><filename>/etc/resolv.conf</filename></para></listitem>
- <listitem><para><filename>/etc/host.conf</filename></para></listitem>
- <listitem><para><filename>/etc/nsswitch.conf</filename></para></listitem>
-</itemizedlist>
-
-<sect2>
-<title><filename>/etc/hosts</filename></title>
-
-<para>
-This file contains a static list of IP addresses and names.
-<programlisting>
-127.0.0.1 localhost localhost.localdomain
-192.168.1.1 bigbox.quenya.org bigbox alias4box
-</programlisting>
-</para>
-
-<para>
-<indexterm><primary>/etc/hosts></primary></indexterm>
-<indexterm><primary>name resolution</primary></indexterm>
-The purpose of <filename>/etc/hosts</filename> is to provide a
-name resolution mechanism so users do not need to remember
-IP addresses.
-</para>
-
-<para>
-<indexterm><primary>IP addresses</primary></indexterm>
-<indexterm><primary>MAC address</primary></indexterm>
-<indexterm><primary>physical network transport layer</primary></indexterm>
-Network packets that are sent over the physical network transport
-layer communicate not via IP addresses but rather using the Media
-Access Control address, or MAC address. IP addresses are currently
-32 bits in length and are typically presented as four decimal
-numbers that are separated by a dot (or period) &smbmdash; for example, 168.192.1.1.
-</para>
-
-<para>
-<indexterm><primary>MAC Addresses</primary></indexterm>
-MAC addresses use 48 bits (or 6 bytes) and are typically represented
-as two-digit hexadecimal numbers separated by colons: 40:8e:0a:12:34:56.
-</para>
-
-<para>
-Every network interface must have a MAC address. Associated with a MAC address may be one or more IP
-addresses. There is no relationship between an IP address and a MAC address; all such assignments are
-arbitrary or discretionary in nature. At the most basic level, all network communications take place using MAC
-addressing. Since MAC addresses must be globally unique and generally remain fixed for any particular
-interface, the assignment of an IP address makes sense from a network management perspective. More than one IP
-address can be assigned per MAC address. One address must be the primary IP address &smbmdash; this is the
-address that will be returned in the Address Resolution Protocol (ARP) reply.
-</para>
-
-<para>
-<indexterm><primary>machine name</primary></indexterm>
-When a user or a process wants to communicate with another machine,
-the protocol implementation ensures that the <quote>machine name</quote> or <quote>host
-name</quote> is resolved to an IP address in a manner that is controlled
-by the TCP/IP configuration control files. The file
-<filename>/etc/hosts</filename> is one such file.
-</para>
-
-<para>
-<indexterm><primary>ARP/RARP</primary></indexterm>
-When the IP address of the destination interface has been determined, a protocol called ARP/RARP is used to
-identify the MAC address of the target interface. ARP is a broadcast-oriented method that uses User Datagram
-Protocol (UDP) to send a request to all interfaces on the local network segment using the all 1s MAC address.
-Network interfaces are programmed to respond to two MAC addresses only; their own unique address and the
-address ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will contain the MAC address and the primary
-IP address for each interface.
-</para>
-
-<para>
-<indexterm><primary>/etc/hosts</primary></indexterm>
-The <filename>/etc/hosts</filename> file is foundational to all
-UNIX/Linux TCP/IP installations and as a minimum will contain
-the localhost and local network interface IP addresses and the
-primary names by which they are known within the local machine.
-This file helps to prime the pump so a basic level of name
-resolution can exist before any other method of name resolution
-becomes available.
-</para>
-
-</sect2>
-
-
-<sect2>
-<title><filename>/etc/resolv.conf</filename></title>
-
-<para>
-This file tells the name resolution libraries:
-</para>
-
-<itemizedlist>
- <listitem><para>The name of the domain to which the machine
- belongs.
- </para></listitem>
-
- <listitem><para>The name(s) of any domains that should be
- automatically searched when trying to resolve unqualified
- host names to their IP address.
- </para></listitem>
-
- <listitem><para>The name or IP address of available domain
- name servers that may be asked to perform name-to-address
- translation lookups.
- </para></listitem>
-</itemizedlist>
-
-</sect2>
-
-
-<sect2>
-<title><filename>/etc/host.conf</filename></title>
-
-
-<para>
-<indexterm><primary>/etc/host.conf</primary></indexterm>
-<filename>/etc/host.conf</filename> is the primary means by which the setting in
-<filename>/etc/resolv.conf</filename> may be effected. It is a critical configuration file. This file controls
-the order by which name resolution may proceed. The typical structure is:
-<programlisting>
-order hosts,bind
-multi on
-</programlisting></para>
-
-<para>Both addresses should be returned. Please refer to the
-man page for <filename>host.conf</filename> for further details.
-</para>
-
-</sect2>
-
-
-<sect2>
-<title><filename>/etc/nsswitch.conf</filename></title>
-
-<para>
-<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
-This file controls the actual name resolution targets. The
-file typically has resolver object specifications as follows:
-<programlisting>
-# /etc/nsswitch.conf
-#
-# Name Service Switch configuration file.
-#
-
-passwd: compat
-# Alternative entries for password authentication are:
-# passwd: compat files nis ldap winbind
-shadow: compat
-group: compat
-
-hosts: files nis dns
-# Alternative entries for host name resolution are:
-# hosts: files dns nis nis+ hesiod db compat ldap wins
-networks: nis files dns
-
-ethers: nis files
-protocols: nis files
-rpc: nis files
-services: nis files
-</programlisting></para>
-
-<para>
-Of course, each of these mechanisms requires that the appropriate
-facilities and/or services are correctly configured.
-</para>
-
-<para>
-It should be noted that unless a network request/message must be
-sent, TCP/IP networks are silent. All TCP/IP communications assume a
-principal of speaking only when necessary.
-</para>
-
-
-<para>
-<indexterm><primary>libnss_wins.so</primary></indexterm>
-<indexterm><primary>NetBIOS names</primary></indexterm>
-<indexterm><primary>make</primary></indexterm>
-<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
-<indexterm><primary>wins</primary></indexterm>
-Starting with version 2.2.0, Samba has Linux support for extensions to
-the name service switch infrastructure so Linux clients will
-be able to obtain resolution of MS Windows NetBIOS names to IP
-addresses. To gain this functionality, Samba needs to be compiled
-with appropriate arguments to the make command (i.e., <userinput>make
-nsswitch/libnss_wins.so</userinput>). The resulting library should
-then be installed in the <filename>/lib</filename> directory, and
-the <parameter>wins</parameter> parameter needs to be added to the <quote>hosts:</quote> line in
-the <filename>/etc/nsswitch.conf</filename> file. At this point, it
-will be possible to ping any MS Windows machine by its NetBIOS
-machine name, as long as that machine is within the workgroup to
-which both the Samba machine and the MS Windows machine belong.
-</para>
-
-</sect2>
-</sect1>
-
-
-<sect1>
-<title>Name Resolution as Used within MS Windows Networking</title>
-
-<para>
-<indexterm><primary>computer name</primary></indexterm>
-<indexterm><primary>machine name</primary></indexterm>
-<indexterm><primary>NetBIOS name</primary></indexterm>
-<indexterm><primary>SMB name</primary></indexterm>
-MS Windows networking is predicated on the name each machine is given. This name is known variously (and
-inconsistently) as the <quote>computer name,</quote> <quote>machine name,</quote> <quote>networking
-name,</quote> <quote>NetBIOS name,</quote> or <quote>SMB name.</quote> All terms mean the same thing with the
-exception of <quote>NetBIOS name,</quote> which can also apply to the name of the workgroup or the domain
-name. The terms <quote>workgroup</quote> and <quote>domain</quote> are really just a simple name with which
-the machine is associated. All NetBIOS names are exactly 16 characters in length. The
-16<superscript>th</superscript> character is reserved. It is used to store a 1-byte value that indicates
-service level information for the NetBIOS name that is registered. A NetBIOS machine name is therefore
-registered for each service type that is provided by the client/server.
-</para>
-
-<para>
-<link linkend="uniqnetbiosnames">Unique NetBIOS names</link> and <link linkend="netbiosnamesgrp">group names</link> tables
-list typical NetBIOS name/service type registrations.
-</para>
-
-<table frame="all" id="uniqnetbiosnames">
-<title>Unique NetBIOS Names</title>
-<tgroup cols="2">
-<colspec align="left"/>
-<colspec align="justify"/>
-<tbody>
-<row><entry>MACHINENAME<00></entry><entry>Server Service is running on MACHINENAME</entry></row>
-<row><entry>MACHINENAME<03></entry><entry>Generic machine name (NetBIOS name)</entry></row>
-<row><entry>MACHINENAME<20></entry><entry>LanMan server service is running on MACHINENAME</entry></row>
-<row><entry>WORKGROUP<1b></entry><entry>Domain master browser</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<table frame="all" id="netbiosnamesgrp">
-<title>Group Names</title>
-<tgroup cols="2">
-<colspec align="left"/>
-<colspec align="justify"/>
-<tbody>
-<row><entry>WORKGROUP<03></entry><entry>Generic name registered by all members of WORKGROUP</entry></row>
-<row><entry>WORKGROUP<1c></entry><entry>Domain cntrollers/netlogon servers</entry></row>
-<row><entry>WORKGROUP<1d></entry><entry>Local master browsers</entry></row>
-<row><entry>WORKGROUP<1e></entry><entry>Browser election service</entry></row>
-</tbody>
-</tgroup>
-</table>
-
-<para>
-<indexterm><primary>NetBIOS</primary></indexterm>
-It should be noted that all NetBIOS machines register their own
-names as per <link linkend="uniqnetbiosnames">Unique NetBIOS names</link> and <link
-linkend="netbiosnamesgrp">group names</link>. This is in vast contrast to TCP/IP
-installations where the system administrator traditionally
-determines in the <filename>/etc/hosts</filename> or in the DNS database what names
-are associated with each IP address.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>/etc/hosts</primary></indexterm>
-<indexterm><primary>NetBIOS name</primary></indexterm>
-One further point of clarification should be noted. The <filename>/etc/hosts</filename>
-file and the DNS records do not provide the NetBIOS name information
-that MS Windows clients depend on to locate the type of service that may
-be needed. An example of this is what happens when an MS Windows client
-wants to locate a domain logon server. It finds this service and the IP
-address of a server that provides it by performing a lookup (via a
-NetBIOS broadcast) for enumeration of all machines that have
-registered the name type *<1C>. A logon request is then sent to each
-IP address that is returned in the enumerated list of IP addresses.
-Whichever machine first replies, it then ends up providing the logon services.
-</para>
-
-<para>
-<indexterm><primary>domain</primary></indexterm>
-<indexterm><primary>workgroup</primary></indexterm>
-The name <quote>workgroup</quote> or <quote>domain</quote> really can be confusing, since these
-have the added significance of indicating what is the security
-architecture of the MS Windows network. The term <quote>workgroup</quote> indicates
-that the primary nature of the network environment is that of a
-peer-to-peer design. In a workgroup, all machines are responsible for
-their own security, and generally such security is limited to the use of
-just a password (known as share-level security). In most situations
-with peer-to-peer networking, the users who control their own machines
-will simply opt to have no security at all. It is possible to have
-user-level security in a workgroup environment, thus requiring the use
-of a username and a matching password.
-</para>
-
-<para>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>Network Basic Input/Output System</primary><see>NetBIOS</see></indexterm>
-<indexterm><primary>Logical Link Control</primary><see>LLC</see></indexterm>
-<indexterm><primary>Network Basic Extended User Interface</primary><see>NetBEUI</see></indexterm>
-<indexterm><primary>Internetworking Packet Exchange</primary><see>IPX</see></indexterm>
-<indexterm><primary>NetWare</primary></indexterm>
-<indexterm><primary>NetBT</primary></indexterm>
-<indexterm><primary>NBT</primary></indexterm>
-MS Windows networking is thus predetermined to use machine names
-for all local and remote machine message passing. The protocol used is
-called Server Message Block (SMB), and this is implemented using
-the NetBIOS protocol (Network Basic Input/Output System). NetBIOS can
-be encapsulated using LLC (Logical Link Control) protocol &smbmdash; in which case
-the resulting protocol is called NetBEUI (Network Basic Extended User
-Interface). NetBIOS can also be run over IPX (Internetworking Packet
-Exchange) protocol as used by Novell NetWare, and it can be run
-over TCP/IP protocols &smbmdash; in which case the resulting protocol is called
-NBT or NetBT, the NetBIOS over TCP/IP.
-</para>
-
-<para>
-MS Windows machines use a complex array of name resolution mechanisms.
-Since we are primarily concerned with TCP/IP, this demonstration is
-limited to this area.
-</para>
-
-<sect2>
-<title>The NetBIOS Name Cache</title>
-
-<para>
-<indexterm><primary>n-memory buffer</primary></indexterm>
-<indexterm><primary>local cache</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-All MS Windows machines employ an in-memory buffer in which is
-stored the NetBIOS names and IP addresses for all external
-machines that machine has communicated with over the
-past 10 to 15 minutes. It is more efficient to obtain an IP address
-for a machine from the local cache than it is to go through all the
-configured name resolution mechanisms.
-</para>
-
-<para>
-<indexterm><primary>name lookup</primary></indexterm>
-If a machine whose name is in the local name cache is shut
-down before the name is expired and flushed from the cache, then
-an attempt to exchange a message with that machine will be subject
-to timeout delays. Its name is in the cache, so a name resolution
-lookup will succeed, but the machine cannot respond. This can be
-frustrating for users but is a characteristic of the protocol.
-</para>
-
-<para>
-<indexterm><primary>nbtstat</primary></indexterm>
-<indexterm><primary>nmblookup</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-The MS Windows utility that allows examination of the NetBIOS
-name cache is called <quote>nbtstat.</quote> The Samba equivalent
-is called <command>nmblookup</command>.
-</para>
-
-</sect2>
-
-<sect2>
-<title>The LMHOSTS File</title>
-
-<para>
-<indexterm><primary>LMHOSTS</primary></indexterm>
-This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory
-<filename>%SystemRoot%\SYSTEM32\DRIVERS\ETC</filename> and contains the IP address
-and the machine name in matched pairs. The <filename>LMHOSTS</filename> file
-performs NetBIOS name to IP address mapping.
-</para>
-
-<para>
-It typically looks like this:
-</para>
-
-<para><programlisting>
-# Copyright (c) 1998 Microsoft Corp.
-#
-# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
-# over TCP/IP) stack for Windows98
-#
-# This file contains the mappings of IP addresses to NT computer names
-# (NetBIOS) names. Each entry should be kept on an individual line.
-# The IP address should be placed in the first column followed by the
-# corresponding computer name. The address and the computer name
-# should be separated by at least one space or tab. The "#" character
-# is generally used to denote the start of a comment (see the exceptions
-# below).
-#
-# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
-# files and offers the following extensions:
-#
-# #PRE
-# #DOM:<domain>
-# #INCLUDE <filename>
-# #BEGIN_ALTERNATE
-# #END_ALTERNATE
-# \0xnn (non-printing character support)
-#
-# Following any entry in the file with the characters "#PRE" will cause
-# the entry to be preloaded into the name cache. By default, entries are
-# not preloaded, but are parsed only after dynamic name resolution fails.
-#
-# Following an entry with the "#DOM:<domain>" tag will associate the
-# entry with the domain specified by <domain>. This effects how the
-# browser and logon services behave in TCP/IP environments. To preload
-# the host name associated with #DOM entry, it is necessary to also add a
-# #PRE to the line. The <domain> is always pre-loaded although it will not
-# be shown when the name cache is viewed.
-#
-# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
-# software to seek the specified <filename> and parse it as if it were
-# local. <filename> is generally a UNC-based name, allowing a
-# centralized lmhosts file to be maintained on a server.
-# It is ALWAYS necessary to provide a mapping for the IP address of the
-# server prior to the #INCLUDE. This mapping must use the #PRE directive.
-# In addition the share "public" in the example below must be in the
-# LanMan Server list of "NullSessionShares" in order for client machines to
-# be able to read the lmhosts file successfully. This key is under
-# \machine\system\currentcontrolset\services\lanmanserver\
-# parameters\nullsessionshares
-# in the registry. Simply add "public" to the list found there.
-#
-# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
-# statements to be grouped together. Any single successful include
-# will cause the group to succeed.
-#
-# Finally, non-printing characters can be embedded in mappings by
-# first surrounding the NetBIOS name in quotations, then using the
-# \0xnn notation to specify a hex value for a non-printing character.
-#
-# The following example illustrates all of these extensions:
-#
-# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
-# 102.54.94.102 "appname \0x14" #special app server
-# 102.54.94.123 popular #PRE #source server
-# 102.54.94.117 localsrv #PRE #needed for the include
-#
-# #BEGIN_ALTERNATE
-# #INCLUDE \\localsrv\public\lmhosts
-# #INCLUDE \\rhino\public\lmhosts
-# #END_ALTERNATE
-#
-# In the above example, the "appname" server contains a special
-# character in its name, the "popular" and "localsrv" server names are
-# pre-loaded, and the "rhino" server name is specified so it can be used
-# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
-# system is unavailable.
-#
-# Note that the whole file is parsed including comments on each lookup,
-# so keeping the number of comments to a minimum will improve performance.
-# Therefore it is not advisable to simply add lmhosts file entries onto the
-# end of this file.
-</programlisting></para>
-
-</sect2>
-
-<sect2>
-<title>HOSTS File</title>
-
-<para>
-This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in
-the directory <filename>%SystemRoot%\SYSTEM32\DRIVERS\ETC</filename> and contains
-the IP address and the IP hostname in matched pairs. It can be
-used by the name resolution infrastructure in MS Windows, depending
-on how the TCP/IP environment is configured. This file is in
-every way the equivalent of the UNIX/Linux <filename>/etc/hosts</filename> file.
-</para>
-</sect2>
-
-
-<sect2>
-<title>DNS Lookup</title>
-
-
-<para>
-<indexterm><primary>DNS</primary></indexterm>
-This capability is configured in the TCP/IP setup area in the network
-configuration facility. If enabled, an elaborate name resolution sequence
-is followed, the precise nature of which is dependent on how the NetBIOS
-Node Type parameter is configured. A Node Type of 0 means that
-NetBIOS broadcast (over UDP broadcast) is used if the name
-that is the subject of a name lookup is not found in the NetBIOS name
-cache. If that fails, then DNS, HOSTS, and LMHOSTS are checked. If set to
-Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the
-WINS server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast
-lookup is used.
-</para>
-
-</sect2>
-
-<sect2>
-<title>WINS Lookup</title>
-
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>Windows Internet Name Server</primary><see>WINS</see></indexterm>
-<indexterm><primary>NetBIOS Name Server</primary><see>NBNS</see></indexterm>
-A WINS (Windows Internet Name Server) service is the equivalent of the
-rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
-the names and IP addresses that are registered by a Windows client
-if the TCP/IP setup has been given at least one WINS server IP address.
-</para>
-
-<para>
-To configure Samba to be a WINS server, the following parameter needs
-to be added to the &smb.conf; file:
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="wins support">Yes</smbconfoption>
-</smbconfblock></para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-To configure Samba to use a WINS server, the following parameters are
-needed in the &smb.conf; file:
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="wins support">No</smbconfoption>
-<smbconfoption name="wins server">xxx.xxx.xxx.xxx</smbconfoption>
-</smbconfblock></para>
-
-<para>
-where <replaceable>xxx.xxx.xxx.xxx</replaceable> is the IP address
-of the WINS server.
-</para>
-
-<para>For information about setting up Samba as a WINS server, read
-<link linkend="NetworkBrowsing">Network Browsing</link>.</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-TCP/IP network configuration problems find every network administrator sooner or later.
-The cause can be anything from keyboard mishaps to forgetfulness to simple mistakes to
-carelessness. Of course, no one is ever deliberately careless!
-</para>
-
- <sect2>
- <title>Pinging Works Only One Way</title>
-
- <para>
- <quote>I can ping my Samba server from Windows, but I cannot ping my Windows
- machine from the Samba server.</quote>
- </para>
-
- <para>
- The Windows machine was at IP address 192.168.1.2 with netmask 255.255.255.0, the
- Samba server (Linux) was at IP address 192.168.1.130 with netmask 255.255.255.128.
- The machines were on a local network with no external connections.
- </para>
-
- <para>
- Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while
- the Samba server was on network 192.168.1.128/25 &smbmdash; logically a different network.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Very Slow Network Connections</title>
-
- <para>
- A common cause of slow network response includes:
- </para>
-
- <itemizedlist>
- <listitem><para>Client is configured to use DNS and the DNS server is down.</para></listitem>
- <listitem><para>Client is configured to use remote DNS server, but the
- remote connection is down.</para></listitem>
- <listitem><para>Client is configured to use a WINS server, but there is no WINS server.</para></listitem>
- <listitem><para>Client is not configured to use a WINS server, but there is a WINS server.</para></listitem>
- <listitem><para>Firewall is filtering out DNS or WINS traffic.</para></listitem>
- </itemizedlist>
-
- </sect2>
-
- <sect2>
- <title>Samba Server Name-Change Problem</title>
-
- <para>
- <quote>The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be
- pinged by its new name from an MS Windows NT4 workstation, but it does still respond to pinging using
- the old name. Why?</quote>
- </para>
-
- <para>
- From this description, three things are obvious:
- </para>
-
- <itemizedlist>
- <listitem><para>WINS is not in use; only broadcast-based name resolution is used.</para></listitem>
- <listitem><para>The Samba server was renamed and restarted within the last 10 or 15 minutes.</para></listitem>
- <listitem><para>The old Samba server name is still in the NetBIOS name cache on the MS Windows NT4 workstation.</para></listitem>
- </itemizedlist>
-
- <para>
- To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine,
- open a <command>cmd</command> shell and then:
- </para>
-
- <para>
-<screen>
-&dosprompt;<userinput>nbtstat -n</userinput>
-
- NetBIOS Local Name Table
-
- Name Type Status
-------------------------------------------------
-&example.workstation.windows; <03> UNIQUE Registered
-ADMINISTRATOR <03> UNIQUE Registered
-&example.workstation.windows; <00> UNIQUE Registered
-SARDON <00> GROUP Registered
-&example.workstation.windows; <20> UNIQUE Registered
-&example.workstation.windows; <1F> UNIQUE Registered
-
-
-&dosprompt;nbtstat -c
-
- NetBIOS Remote Cache Name Table
-
- Name Type Host Address Life [sec]
---------------------------------------------------------------
-&example.server.samba; <20> UNIQUE 192.168.1.1 240
-
-&dosprompt;
-</screen>
- </para>
-
- <para>
- In this example, &example.server.samba; is the Samba server and &example.workstation.windows; is the MS Windows NT4 workstation.
- The first listing shows the contents of the Local Name Table (i.e., identity information on
- the MS Windows workstation), and the second shows the NetBIOS name in the NetBIOS name cache.
- The name cache contains the remote machines known to this workstation.
- </para>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="InterdomainTrusts">
-<chapterinfo>
- &author.jht;
- &author.mimir;
- <author>&person.jelmer;<contrib>drawing</contrib></author>
- <author>
- <firstname>Stephen</firstname><surname>Langasek</surname>
- <affiliation>
- <address><email>vorlon@netexpress.net</email></address>
- </affiliation>
- </author>
- <pubdate>April 3, 2003</pubdate>
-</chapterinfo>
-
-<title>Interdomain Trust Relationships</title>
-
-
-<para>
-<indexterm><primary>Interdomain Trusts</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>trusts</primary></indexterm>
-<indexterm><primary>samba-to-samba trusts</primary></indexterm>
-<indexterm><primary>Active Directory</primary></indexterm>
-<indexterm><primary>NT4-style domain</primary></indexterm>
-<indexterm><primary>trust relationships</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>LDAP-based</primary></indexterm>
-Samba supports NT4-style domain trust relationships. This is a feature that many sites
-will want to use if they migrate to Samba from an NT4-style domain and do not want to
-adopt Active Directory or an LDAP-based authentication backend. This chapter explains
-some background information regarding trust relationships and how to create them. It is now
-possible for Samba to trust NT4 (and vice versa), as well as to create Samba-to-Samba
-trusts.
-</para>
-
-<para>
-<indexterm><primary>winbind</primary></indexterm>
-<indexterm><primary>UID range</primary></indexterm>
-<indexterm><primary>GID range</primary></indexterm>
-<indexterm><primary>daemon</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-The use of interdomain trusts requires use of <command>winbind</command>, so the
-<command>winbindd</command> daemon must be running. Winbind operation in this mode is
-dependent on the specification of a valid UID range and a valid GID range in the &smb.conf; file.
-These are specified respectively using:
-<smbconfblock>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-</smbconfblock>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>POSIX user accounts</primary></indexterm>
-<indexterm><primary>maximum value</primary></indexterm>
-<indexterm><primary>4294967295</primary></indexterm>
-The range of values specified must not overlap values used by the host operating system and must
-not overlap values used in the passdb backend for POSIX user accounts. The maximum value is
-limited by the upper-most value permitted by the host operating system. This is a UNIX kernel
-limited parameter. Linux kernel 2.6-based systems support a maximum value of 4294967295
-(32-bit unsigned variable).
-</para>
-
-<note><para>
-<indexterm><primary>winbind</primary></indexterm>
-<indexterm><primary>trusting domain</primary></indexterm>
-<indexterm><primary>trusted domain</primary></indexterm>
-The use of winbind is necessary only when Samba is the trusting domain, not when it is the
-trusted domain.
-</para></note>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>scalability</primary></indexterm>
-<indexterm><primary>trust relationships</primary></indexterm>
-Samba can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style
-trust relationships. This imparts to Samba scalability similar to that with MS Windows NT4.
-</para>
-
-<para>
-<indexterm><primary>scalable backend</primary></indexterm>
-<indexterm><primary>authentication database</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>interdomain trusts</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-Given that Samba can function with a scalable backend authentication database such as LDAP, and given its
-ability to run in primary as well as backup domain control modes, the administrator would be well-advised to
-consider alternatives to the use of interdomain trusts simply because, by the very nature of how trusts
-function, this system is fragile. That was, after all, a key reason for the development and adoption of
-Microsoft Active Directory.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Trust Relationship Background</title>
-
-<para>
-<indexterm><primary>security domains</primary></indexterm>
-<indexterm><primary>nonhierarchical</primary></indexterm>
-<indexterm><primary>security structure</primary></indexterm>
-<indexterm><primary>large organizations</primary></indexterm>
-<indexterm><primary>delegation</primary></indexterm>
-<indexterm><primary>administrative responsibilities</primary></indexterm>
-MS Windows NT3/4-type security domains employ a nonhierarchical security structure.
-The limitations of this architecture as it effects the scalability of MS Windows networking
-in large organizations is well known. Additionally, the flat namespace that results from
-this design significantly impacts the delegation of administrative responsibilities in
-large and diverse organizations.
-</para>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>Kerberos</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>limitations</primary></indexterm>
-<indexterm><primary>domain security</primary></indexterm>
-Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
-of circumventing the limitations of the older technologies. Not every organization is ready
-or willing to embrace ADS. For small companies the older NT4-style domain security paradigm
-is quite adequate, and so there remains an entrenched user base for whom there is no direct
-desire to go through a disruptive change to adopt ADS.
-</para>
-
-<para>
-<indexterm><primary>security domains</primary></indexterm>
-<indexterm><primary>access rights</primary></indexterm>
-<indexterm><primary>privileges</primary></indexterm>
-<indexterm><primary>trusts</primary></indexterm>
-<indexterm><primary>trusted domain</primary></indexterm>
-<indexterm><primary>trusting domain</primary></indexterm>
-<indexterm><primary>one direction</primary></indexterm>
-With Windows NT, Microsoft introduced the ability to allow different security domains
-to effect a mechanism so users from one domain may be given access rights and privileges
-in another domain. The language that describes this capability is couched in terms of
-<emphasis>trusts</emphasis>. Specifically, one domain will <emphasis>trust</emphasis> the users
-from another domain. The domain from which users can access another security domain is
-said to be a trusted domain. The domain in which those users have assigned rights and privileges
-is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
-so if users in both domains are to have privileges and rights in each others' domain, then it is
-necessary to establish two relationships, one in each direction.
-</para>
-
-<para>
-<indexterm><primary>security domain</primary></indexterm>
-<indexterm><primary>nontransitive</primary></indexterm>
-<indexterm><primary>trust relationship</primary></indexterm>
-<indexterm><primary>transitive</primary></indexterm>
-<indexterm><primary>explicit trust</primary></indexterm>
-Further, in an NT4-style MS security domain, all trusts are nontransitive. This means that if there are three
-domains (let's call them red, white, and blue), where red and white have a trust relationship, and white and
-blue have a trust relationship, then it holds that there is no implied trust between the red and blue domains.
-Relationships are explicit and not transitive.
-</para>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>security contexts</primary></indexterm>
-<indexterm><primary>trust relationships</primary></indexterm>
-<indexterm><primary>two-way trust</primary></indexterm>
-<indexterm><primary>Windows 2000</primary></indexterm>
-<indexterm><primary>security domains</primary></indexterm>
-<indexterm><primary>NT4-style domains</primary></indexterm>
-New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way by default.
-Also, all inter-ADS domain trusts are transitive. In the case of the red, white, and blue domains, with
-Windows 2000 and ADS, the red and blue domains can trust each other. This is an inherent feature of ADS
-domains. Samba implements MS Windows NT4-style interdomain trusts and interoperates with MS Windows 200x ADS
-security domains in similar manner to MS Windows NT4-style domains.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Native MS Windows NT4 Trusts Configuration</title>
-
-<para>
-<indexterm><primary>Interdomain Trusts</primary><secondary>creating</secondary></indexterm>
-<indexterm><primary>two-way trust</primary></indexterm>
-<indexterm><primary>security credentials</primary></indexterm>
-There are two steps to creating an interdomain trust relationship. To effect a two-way trust
-relationship, it is necessary for each domain administrator to create a trust account for the
-other domain to use in verifying security credentials.
-</para>
-
-
-<sect2>
-<title>Creating an NT4 Domain Trust</title>
-
-<para>
-<indexterm><primary>domain trust</primary></indexterm>
-<indexterm><primary>trust relationships</primary></indexterm>
-<indexterm><primary>>Domain User Manager</primary></indexterm>
-<indexterm><primary>remote domain</primary></indexterm>
-<indexterm><primary>standard confirmation</primary></indexterm>
-For MS Windows NT4, all domain trust relationships are configured using the
-<application>Domain User Manager</application>. This is done from the Domain User Manager Policies
-entry on the menu bar. From the <guimenu>Policy</guimenu> menu, select
-<guimenuitem>Trust Relationships</guimenuitem>. Next to the lower box labeled
-<guilabel>Permitted to Trust this Domain</guilabel> are two buttons, <guibutton>Add</guibutton>
-and <guibutton>Remove</guibutton>. The <guibutton>Add</guibutton> button will open a panel in which
-to enter the name of the remote domain that will be able to assign access rights to users in
-your domain. You will also need to enter a password for this trust relationship, which the
-trusting domain will use when authenticating users from the trusted domain.
-The password needs to be typed twice (for standard confirmation).
-</para>
-
-</sect2>
-
-
-<sect2>
-<title>Completing an NT4 Domain Trust</title>
-
-<para>
-<indexterm><primary>trust relationship</primary></indexterm>
-<indexterm><primary>trusting domain</primary></indexterm>
-<indexterm><primary>trusted domain</primary></indexterm>
-<indexterm><primary>remote domain</primary></indexterm>
-<indexterm><primary>password assigned</primary></indexterm>
-<indexterm><primary>Interdomain Trusts</primary><secondary>Completing</secondary></indexterm>
-A trust relationship will work only when the other (trusting) domain makes the appropriate connections
-with the trusted domain. To consummate the trust relationship, the administrator launches the
-Domain User Manager from the menu selects <guilabel>Policies</guilabel>, then select
-<guilabel>Trust Relationships</guilabel>, and clicks on the <guibutton>Add</guibutton> button
-next to the box that is labeled <guilabel>Trusted Domains</guilabel>. A panel opens in which
-must be entered the name of the remote domain as well as the password assigned to that trust.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Interdomain Trust Facilities</title>
-
-
-<para>
-<indexterm><primary>two-way trust</primary></indexterm>
-<indexterm><primary>trust relationship</primary></indexterm>
-<indexterm><primary>trust established</primary></indexterm>
-<indexterm><primary>one-way trust</primary></indexterm>
-<indexterm><primary>Windows NT4 domains</primary></indexterm>
-<indexterm><primary>Interdomain Trusts</primary><secondary>Facilities</secondary></indexterm>
-A two-way trust relationship is created when two one-way trusts are created, one in each direction.
-Where a one-way trust has been established between two MS Windows NT4 domains (let's call them
-DomA and DomB), the following facilities are created:
-</para>
-
-<figure id="trusts1">
- <title>Trusts overview.</title>
- <imagefile>trusts1</imagefile>
-</figure>
-
-<itemizedlist>
- <listitem><para>
- DomA (completes the trust connection) <parameter>Trusts</parameter> DomB.
- </para></listitem>
-
- <listitem><para>
- DomA is the <parameter>Trusting</parameter> domain.
- </para></listitem>
-
- <listitem><para>
- DomB is the <parameter>Trusted</parameter> domain (originates the trust account).
- </para></listitem>
-
- <listitem><para>
- Users in DomB can access resources in DomA.
- </para></listitem>
-
- <listitem><para>
- Users in DomA cannot access resources in DomB.
- </para></listitem>
-
- <listitem><para>
- Global groups from DomB can be used in DomA.
- </para></listitem>
-
- <listitem><para>
- Global groups from DomA cannot be used in DomB.
- </para></listitem>
-
- <listitem><para>
- DomB does appear in the logon dialog box on client workstations in DomA.
- </para></listitem>
-
- <listitem><para>
- DomA does not appear in the logon dialog box on client workstations in DomB.
- </para></listitem>
-</itemizedlist>
-
-<itemizedlist>
- <listitem><para>
- Users and groups in a trusting domain cannot be granted rights, permissions, or access
- to a trusted domain.
- </para></listitem>
-
- <listitem><para>
- The trusting domain can access and use accounts (users/global groups) in the
- trusted domain.
- </para></listitem>
-
- <listitem><para>
- Administrators of the trusted domain can be granted administrative rights in the
- trusting domain.
- </para></listitem>
-
- <listitem><para>
- Users in a trusted domain can be given rights and privileges in the trusting
- domain.
- </para></listitem>
-
- <listitem><para>
- Trusted domain global groups can be given rights and permissions in the trusting
- domain.
- </para></listitem>
-
- <listitem><para>
- Global groups from the trusted domain can be made members in local groups on
- MS Windows domain member machines.
- </para></listitem>
-</itemizedlist>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Configuring Samba NT-Style Domain Trusts</title>
-
-<para>
-<indexterm><primary>interdomain trust</primary></indexterm>
-This description is meant to be a fairly short introduction about how to set up a Samba server so
-that it can participate in interdomain trust relationships. Trust relationship support in Samba
-is at an early stage, so do not be surprised if something does not function as it should.
-</para>
-
-<para>
-<indexterm><primary>peer domain</primary></indexterm>
-<indexterm><primary>trust relationship</primary></indexterm>
-<indexterm><primary>Windows NT4 Server</primary></indexterm>
-<indexterm><primary>between domains</primary></indexterm>
-Each of the procedures described next assumes the peer domain in the trust relationship is controlled by a
-Windows NT4 server. However, the remote end could just as well be another Samba domain. It can be clearly
-seen, after reading this document, that combining Samba-specific parts of what's written in the following
-sections leads to trust between domains in a purely Samba environment.
-</para>
-
-<sect2 id="samba-trusted-domain">
-<title>Samba as the Trusted Domain</title>
-
-<para>
-<indexterm><primary>trusted party</primary></indexterm>
-<indexterm><primary>special account</primary></indexterm>
-<indexterm><primary>trusting party</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
-In order to set the Samba PDC to be the trusted party of the relationship, you first need
-to create a special account for the domain that will be the trusting party. To do that,
-you can use the <command>smbpasswd</command> utility. Creating the trusted domain account is
-similar to creating a trusted machine account. Suppose, your domain is
-called SAMBA, and the remote domain is called RUMBA. The first step
-will be to issue this command from your favorite shell:
-</para>
-
-<para>
-<screen>
-&rootprompt; <userinput>smbpasswd -a -i rumba</userinput>
-New SMB password: <userinput>XXXXXXXX</userinput>
-Retype SMB password: <userinput>XXXXXXXX</userinput>
-Added user rumba$
-</screen>
-
-where <option>-a</option> means to add a new account into the
-passdb database and <option>-i</option> means to <quote>create this
-account with the Interdomain trust flag</quote>.
-</para>
-
-<para>
-<indexterm><primary>account name</primary></indexterm>
-<indexterm><primary>remote domain</primary></indexterm>
-<indexterm><primary>password database</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-The account name will be <quote>rumba$</quote> (the name of the remote domain).
-If this fails, you should check that the trust account has been added to the system
-password database (<filename>/etc/passwd</filename>). If it has not been added, you
-can add it manually and then repeat the previous step.
-</para>
-
-<para>
-<indexterm><primary>password</primary></indexterm>
-<indexterm><primary>new account</primary></indexterm>
-<indexterm><primary>confirm the trust</primary></indexterm>
-<indexterm><primary>Windows NT Server</primary></indexterm>
-After issuing this command, you will be asked to enter the password for the account. You can use any password
-you want, but be aware that Windows NT will not change this password until 7 days following account creation.
-After the command returns successfully, you can look at the entry for the new account (in the standard way as
-appropriate for your configuration) and see that the account's name is really RUMBA$ and it has the
-<quote>I</quote> flag set in the flags field. Now you are ready to confirm the trust by establishing it from
-Windows NT Server.
-</para>
-
-
-<para>
-<indexterm><primary>User Manager</primary></indexterm>
-<indexterm><primary>trusted domain name</primary></indexterm>
-<indexterm><primary>relationship password</primary></indexterm>
-<indexterm><primary>remote domain</primary></indexterm>
-<indexterm><primary>established</primary></indexterm>
-Open <application>User Manager for Domains</application> and from the <guimenu>Policies</guimenu> menu, select
-<guimenuitem>Trust Relationships...</guimenuitem>. Beside the <guilabel>Trusted domains</guilabel> list box,
-click the <guimenu>Add...</guimenu> button. You will be prompted for the trusted domain name and the
-relationship password. Type in SAMBA, as this is the name of the remote domain and the password used at the
-time of account creation. Click on <guibutton>OK</guibutton> and, if everything went without incident, you
-will see the <computeroutput>Trusted domain relationship successfully established</computeroutput> message.
-</para>
-
-</sect2>
-<sect2>
-<title>Samba as the Trusting Domain</title>
-
-<para>
-<indexterm><primary>NT-controlled domain</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-This time activities are somewhat reversed. Again, we'll assume that your domain
-controlled by the Samba PDC is called SAMBA and the NT-controlled domain is called RUMBA.
-</para>
-
-<para>
-The very first step is to add an account for the SAMBA domain on RUMBA's PDC.
-</para>
-
-
-<para>
-<indexterm><primary>User Manager</primary></indexterm>
-<indexterm><primary>trusted domain</primary></indexterm>
-<indexterm><primary>password</primary></indexterm>
-Launch the <application>Domain User Manager</application>, then from the menu select
-<guimenu>Policies</guimenu>, <guimenuitem>Trust Relationships</guimenuitem>.
-Now, next to the <guilabel>Trusting Domains</guilabel> box, press the <guibutton>Add</guibutton>
-button and type in the name of the trusted domain (SAMBA) and the password to use in securing
-the relationship.
-</para>
-
-<para>
-<indexterm><primary>password</primary></indexterm>
-<indexterm><primary>confirm the password</primary></indexterm>
-The password can be arbitrarily chosen. It is easy to change the password from the Samba server whenever you
-want. After you confirm the password, your account is ready for use. Now its Samba's turn.
-</para>
-
-<para>
-Using your favorite shell while logged in as root, issue this command:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom establish</tertiary></indexterm>
-</para>
-
-<para>
-&rootprompt;<userinput>net rpc trustdom establish rumba</userinput>
-</para>
-
-<para>
-<indexterm><primary>password</primary></indexterm>
-<indexterm><primary>interdomain connection</primary></indexterm>
-<indexterm><primary>ordinary connection</primary></indexterm>
-You will be prompted for the password you just typed on your Windows NT4 Server box.
-An error message, <literal>"NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT,"</literal>
-that may be reported periodically is of no concern and may safely be ignored.
-It means the password you gave is correct and the NT4 server says the account is ready for
-interdomain connection and not for ordinary connection. After that, be patient;
-it can take a while (especially in large networks), but eventually you should see
-the <literal>Success</literal> message. Congratulations! Your trust
-relationship has just been established.
-</para>
-
-<note><para>
-You have to run this command as root because you must have write access to
-the <filename>secrets.tdb</filename> file.
-</para></note>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>NT4-Style Domain Trusts with Windows 2000</title>
-
-<para>
-<indexterm><primary>trust relationship</primary></indexterm>
-<indexterm><primary>Windows 2000 server</primary></indexterm>
-<indexterm><primary>NT4-style</primary></indexterm>
-<indexterm><primary>mixed mode</primary></indexterm>
-Although <application>Domain User Manager</application> is not present in Windows 2000, it is
-also possible to establish an NT4-style trust relationship with a Windows 2000 domain
-controller running in mixed mode as the trusting server. It should also be possible for
-Samba to trust a Windows 2000 server; however, more testing is still needed in this area.
-</para>
-
-<para>
-<indexterm><primary>interdomain trust</primary></indexterm>
-<indexterm><primary>trust account</primary></indexterm>
-<indexterm><primary>not transitive</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-After <link linkend="samba-trusted-domain">creating the interdomain trust account on the Samba server</link>
-as described previously, open <application>Active Directory Domains and Trusts</application> on the AD
-controller of the domain whose resources you wish Samba users to have access to. Remember that since NT4-style
-trusts are not transitive, if you want your users to have access to multiple mixed-mode domains in your AD
-forest, you will need to repeat this process for each of those domains. With <application>Active Directory
-domains and trusts</application> open, right-click on the name of the Active Directory domain that will trust
-our Samba domain and choose <guimenuitem>Properties</guimenuitem>, then click on the
-<guilabel>Trusts</guilabel> tab. In the upper part of the panel, you will see a list box labeled
-<guilabel>Domains trusted by this domain:</guilabel> and an <guilabel>Add...</guilabel> button next to it.
-Press this button and, just as with NT4, you will be prompted for the trusted domain name and the relationship
-password. Press <emphasis>OK</emphasis> and after a moment, Active Directory will respond with
-<computeroutput>The trusted domain has been added and the trust has been verified.</computeroutput> Your
-Samba users can now be granted access to resources in the AD domain.
-</para>
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-Interdomain trust relationships should not be attempted on networks that are unstable
-or that suffer regular outages. Network stability and integrity are key concerns with
-distributed trusted domains.
-</para>
-
-<sect2>
-<title>Browsing of Trusted Domain Fails</title>
-
-<para>
-<emphasis>Browsing from a machine in a trusted Windows 200x domain to a Windows 200x member of
-a trusting Samba domain, I get the following error:</emphasis>
-<screen>
-The system detected a possible attempt to compromise security. Please
-ensure that you can contact the server that authenticated you.
-</screen>
-</para>
-
-<para>
-<emphasis>The event logs on the box I'm trying to connect to have entries regarding group
-policy not being applied because it is a member of a down-level domain.</emphasis>
-</para>
-
-<para>If there is a computer account in the Windows
-200x domain for the machine in question, and it is disabled, this problem can
-occur. If there is no computer account (removed or never existed), or if that
-account is still intact (i.e., you just joined it to another domain), everything
-seems to be fine. By default, when you unjoin a domain (the Windows 200x
-domain), the computer tries to automatically disable the computer account in
-the domain. If you are running as an account that has privileges to do this
-when you unjoin the machine, it is done; otherwise it is not done.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Problems with LDAP ldapsam and Older Versions of smbldap-tools</title>
-
-<para>
-If you use the <command>smbldap-useradd</command> script to create a trust
-account to set up interdomain trusts, the process of setting up the trust will
-fail. The account that was created in the LDAP database will have an account
-flags field that has <literal>[W ]</literal>, when it must have
-<literal>[I ]</literal> for interdomain trusts to work.
-</para>
-
-<para>Here is a simple solution.
-Create a machine account as follows:
-<screen>
-&rootprompt; smbldap-useradd -w domain_name
-</screen>
-Then set the desired trust account password as shown here:
-<screen>
-&rootprompt; smbldap-passwd domain_name\$
-</screen>
-Using a text editor, create the following file:
-<screen>
-dn: uid=domain_name$,ou=People,dc={your-domain},dc={your-top-level-domain}
-changetype: modify
-sambaAcctFlags: [I ]
-</screen>
-Then apply the text file to the LDAP database as follows:
-<screen>
-&rootprompt; ldapmodify -x -h localhost \
- -D "cn=Manager,dc={your-domain},dc={your-top-level-domain}" \
- -W -f /path-to/foobar
-</screen>
-Create a single-sided trust under the NT4 Domain User Manager, then execute:
-<screen>
-&rootprompt; net rpc trustdom establish domain_name
-</screen>
-</para>
-
-<para>
-It works with Samba and NT4 domains, and also with Samba-3 and Windows 200x ADS in mixed mode.
-Both domain controllers, Samba and NT must have the same WINS server; otherwise,
-the trust will never work.
-</para>
-
-</sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<preface id="IntroSMB">
-<prefaceinfo>
- &author.jht;
- <pubdate>June 29, 2003</pubdate>
-</prefaceinfo>
-
-<title>Introduction</title>
-
-<para><quote>
-A man's gift makes room for him before great men. Gifts are like hooks that can catch
-hold of the mind taking it beyond the reach of forces that otherwise might constrain it.
-</quote> --- Anon.
-</para>
-
-
-<para>
-This is a book about Samba. It is a tool, a derived work of the labors
-of many and of the diligence and goodwill of more than a few.
-This book contains material that has been contributed in a persistent belief
-that each of us can add value to our neighbors as well as to those who will
-follow us.
-</para>
-
-<para>
-This book is designed to meet the needs of the Microsoft network administrator.
-UNIX administrators will benefit from this book also, though they may complain
-that it is hard to find the information they think they need. So if you are a
-Microsoft certified specialist, this book should meet your needs rather well.
-If you are a UNIX or Linux administrator, there is no need to feel badly &smbmdash; you
-should have no difficulty finding answers to your current concerns also.
-</para>
-
-<sect1>
-<title>What Is Samba?</title>
-
- <para>
- Samba is a big, complex project. The Samba project is ambitious and exciting.
- The team behind Samba is a group of some thirty individuals who are spread
- the world over and come from an interesting range of backgrounds. This team
- includes scientists, engineers, programmers, business people, and students.
- </para>
-
- <para>
- Team members were drawn into active participation through the desire to help
- deliver an exciting level of transparent interoperability between Microsoft
- Windows and the non-Microsoft information
- technology world.
- </para>
-
- <para>
- The slogan that unites the efforts behind the Samba project says:
- <emphasis>Samba, Opening Windows to a Wider World!</emphasis> The goal
- behind the project is one of removing barriers to interoperability.
- </para>
-
- <para>
- Samba provides file and print services for Microsoft Windows clients. These
- services may be hosted off any TCP/IP-enabled platform. The original deployment
- platforms were UNIX and Linux, though today it is in common use across
- a broad variety of systems.
- </para>
-
- <para>
- The Samba project includes not only an impressive feature set in file and print
- serving capabilities, but has been extended to include client functionality,
- utilities to ease migration to Samba, tools to aid interoperability with
- Microsoft Windows, and administration tools.
- </para>
-
- <para>
- The real people behind Samba are users like you. You have inspired the
- developers (the Samba Team) to do more than any of them imagined could or should
- be done. User feedback drives Samba development. Samba in particular incorporates
- a huge amount of work done as a result of user requests, suggestions and direct
- code contributions.
- </para>
-
-</sect1>
-
-<sect1>
-<title>Why This Book?</title>
-
- <para>
- There is admittedly a large number of Samba books on the market today and
- each book has its place. Despite the apparent plethora of books, Samba
- as a project continues to receive much criticism for failing to provide
- sufficient documentation. Samba is also criticized for being too complex
- and too difficult to configure. In many ways this is evidence of the
- success of Samba as there would be no complaints if it was not successful.
- </para>
-
- <para>
- The Samba Team members work predominantly with UNIX and Linux, so
- it is hardly surprising that existing Samba documentation should reflect
- that orientation. The original HOWTO text documents were intended to provide
- some tips, a few golden nuggets, and if they helped anyone then that was
- just wonderful. But the HOWTO documents lacked structure and context. They were
- isolated snapshots of information that were written to pass information
- on to someone else who might benefit. They reflected a need to transmit
- more information that could be conveniently put into manual pages.
- </para>
-
- <para>
- The original HOWTO documents were written by different authors. Most HOWTO
- documents are the result of feedback and contributions from numerous
- authors. In this book we took care to preserve as much original content as
- possible. As you read this book you will note that chapters were written by
- multiple authors, each of whom has his own style. This demonstrates
- the nature of the Open Source software development process.
- </para>
-
- <para>
- Out of the original HOWTO documents sprang a collection of unofficial
- HOWTO documents that are spread over the Internet. It is sincerely intended
- that this work will <emphasis>not</emphasis> replace the valuable unofficial
- HOWTO work that continues to flourish. If you are involved in unofficial
- HOWTO production then please continue your work!
- </para>
-
- <para>
- Those of you who have dedicated your labors to the production of unofficial
- HOWTOs, to Web page information regarding Samba, or to answering questions
- on the mailing lists or elsewhere, may be aware that this is a labor
- of love. We would like to know about your contribution and willingly receive
- the precious pearls of wisdom you have collected. Please email your contribution to
- <ulink noescape="1" url="mailto:jht@samba.org">John H. Terpstra (jht@samba.org)</ulink>.
- As a service to other users we will gladly adopt material that is technically accurate.
- </para>
-
- <para>
- Existing Samba books are largely addressed to the UNIX administrator.
- From the perspective of this target group the existing books serve
- an adequate purpose, with one exception &smbmdash; now that Samba is out
- they need to be updated!
- </para>
-
- <para>
- This book, the <emphasis>Official Samba-3 HOWTO and Reference Guide</emphasis>,
- includes the Samba-HOWTO-Collection.pdf that ships with Samba.
- These documents have been written with a new design intent and purpose.
- </para>
-
- <para>
- Over the past two years many Microsoft network administrators have adopted
- Samba and have become interested in its deployment. Their information needs
- are very different from that of the UNIX administrator. This book has been
- arranged and the information presented from the perspective of someone with previous
- Microsoft Windows network administrative training and experience.
- </para>
-
-</sect1>
-
-<sect1>
-<title>Book Structure and Layout</title>
-
- <para>
- This book is presented in six parts:
- </para>
-
- <variablelist>
- <varlistentry><term>General Installation</term>
- <listitem><para>
- Designed to help you get Samba running quickly.
- The Fast Start chapter is a direct response to requests from
- Microsoft network administrators for some sample configurations
- that <emphasis>just work</emphasis>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Server Configuration Basics</term>
- <listitem><para>
- The purpose of this section is to aid the transition from existing
- Microsoft Windows network knowledge to Samba terminology and norms.
- The chapters in this part each cover the installation of one type of
- Samba server.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Advanced Configuration</term>
- <listitem><para>
- The mechanics of network browsing have long been the Achilles heel of
- all Microsoft Windows users. Samba introduces new user and machine
- account management facilities, a new way to map UNIX groups and Windows
- groups, Interdomain trusts, new loadable file system drivers (VFS), and
- more. New with this document is expanded printing documentation, as well
- as a wealth of information regarding desktop and user policy handling,
- use of desktop profiles, and techniques for enhanced network integration.
- This section makes up the core of the book. Read and enjoy.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Migration and Updating</term>
- <listitem><para>
- A much requested addition to the book is information on how to migrate
- from Microsoft Windows NT4 to Samba-3, as well as an overview of what the
- issues are when moving from Samba-2.x to Samba-3.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Troubleshooting</term>
- <listitem><para>
- This short section should help you when all else fails.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Reference Section</term>
- <listitem><para>
- Here you will find a collection of things that are either too peripheral
- for most users, or are a little left of field to be included in the
- main body of information.
- </para></listitem>
- </varlistentry>
- </variablelist>
-
-<para>
-Welcome to Samba and the first published document to help you and your users to enjoy a whole
-new world of interoperability between Microsoft Windows and the rest of the world.
-</para>
-
-</sect1>
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="largefile">
-<chapterinfo>
- &author.jeremy;
- &author.jht;
- <pubdate>March 5, 2005</pubdate>
-</chapterinfo>
-<title>Handling Large Directories</title>
-
-<para>
-<indexterm><primary>performance degradation</primary></indexterm>
-<indexterm><primary>large numbers of files</primary></indexterm>
-<indexterm><primary>large directory</primary></indexterm>
-Samba-3.0.12 and later implements a solution for sites that have experienced performance degradation due to the
-problem of using Samba-3 with applications that need large numbers of files (100,000 or more) per directory.
-</para>
-
-<para>
-<indexterm><primary>read directory into memory</primary></indexterm>
-<indexterm><primary>strange delete semantics</primary></indexterm>
-The key was fixing the directory handling to read only the current list requested instead of the old
-(up to samba-3.0.11) behavior of reading the entire directory into memory before doling out names.
-Normally this would have broken OS/2 applications, which have very strange delete semantics, but by
-stealing logic from Samba4 (thanks, Tridge), the current code in 3.0.12 handles this correctly.
-</para>
-
-<para>
-<indexterm><primary>large directory</primary></indexterm>
-<indexterm><primary>performance</primary></indexterm>
-To set up an application that needs large numbers of files per directory in a way that does not
-damage performance unduly, follow these steps:
-</para>
-
-<para>
-<indexterm><primary>canonicalize files</primary></indexterm>
-First, you need to canonicalize all the files in the directory to have one case, upper or lower &smbmdash; take your
-pick (I chose upper because all my files were already uppercase names). Then set up a new custom share for the
-application as follows:
-<smbconfblock>
-<smbconfsection name="[bigshare]"/>
-<smbconfoption name="path">/data/manyfilesdir</smbconfoption>
-<smbconfoption name="read only">no</smbconfoption>
-<smbconfoption name="case sensitive">True</smbconfoption>
-<smbconfoption name="default case">upper</smbconfoption>
-<smbconfoption name="preserve case">no</smbconfoption>
-<smbconfoption name="short preserve case">no</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-<indexterm><primary>case options</primary></indexterm>
-<indexterm><primary>match case</primary></indexterm>
-<indexterm><primary>uppercase</primary></indexterm>
-Of course, use your own path and settings, but set the case options to match the case of all the files in your
-directory. The path should point at the large directory needed for the application &smbmdash; any new files created in
-there and in any paths under it will be forced by smbd into uppercase, but smbd will no longer have to scan
-the directory for names: it knows that if a file does not exist in uppercase, then it doesn't exist at all.
-</para>
-
-<para>
-<indexterm><primary>case-insensitive</primary></indexterm>
-<indexterm><primary>consistent case</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-The secret to this is really in the <smbconfoption name="case sensitive">True</smbconfoption>
-line. This tells smbd never to scan for case-insensitive versions of names. So if an application asks for a file
-called <filename>FOO</filename>, and it cannot be found by a simple stat call, then smbd will return file not
-found immediately without scanning the containing directory for a version of a different case. The other
-<filename>xxx case xxx</filename> lines make this work by forcing a consistent case on all files created by
-&smbd;.
-</para>
-
-<para>
-<indexterm><primary>uppercase</primary></indexterm>
-<indexterm><primary>stanza</primary></indexterm>
-<indexterm><primary>lowercase filenames</primary></indexterm>
-Remember, all files and directories under the <parameter>path</parameter> directory must be in uppercase
-with this &smb.conf; stanza because &smbd; will not be able to find lowercase filenames with these settings. Also
-note that this is done on a per-share basis, allowing this parameter to be set only for a share servicing an application with
-this problematic behavior (using large numbers of entries in a directory) &smbmdash; the rest of your &smbd; shares
-don't need to be affected.
-</para>
-
-<para>
-This makes smbd much faster when dealing with large directories. My test case has over 100,000 files, and
-smbd now deals with this very efficiently.
-</para>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="NT4Migration">
-<chapterinfo>
- &author.jht;
- <pubdate>April 3, 2003</pubdate>
-</chapterinfo>
-
-<title>Migration from NT4 PDC to Samba PDC</title>
-
-<para>
-<indexterm><primary>migrate</primary></indexterm>
-<indexterm><primary>domain control</primary></indexterm>
-This is a rough guide to assist those wishing to migrate from NT4 domain control to
-Samba-based domain control.
-</para>
-
-<sect1>
-<title>Planning and Getting Started</title>
-
-<para>
-<indexterm><primary>show-stopper-type</primary></indexterm>
-In the IT world there is often a saying that all problems are encountered because of
-poor planning. The corollary to this saying is that not all problems can be anticipated
-and planned for. Then again, good planning will anticipate most show-stopper-type situations.
-</para>
-
-<para>
-<indexterm><primary>migration plan</primary></indexterm>
-Those wishing to migrate from MS Windows NT4 domain control to a Samba domain control
-environment would do well to develop a detailed migration plan. So here are a few pointers to
-help migration get underway.
-</para>
-
-<sect2>
-<title>Objectives</title>
-
-<para>
-<indexterm><primary>migration process</primary></indexterm>
-The key objective for most organizations is to make the migration from MS Windows NT4
-to Samba domain control as painless as possible. One of the challenges you may experience
-in your migration process may well be convincing management that the new environment
-should remain in place. Many who have introduced open source technologies have experienced
-pressure to return to a Microsoft-based platform solution at the first sign of trouble.
-</para>
-
-<para>
-<indexterm><primary>change motivations</primary></indexterm>
-Before attempting a migration to a Samba-controlled network, make every possible effort to
-gain all-round commitment to the change. Know precisely <emphasis>why</emphasis> the change
-is important for the organization. Possible motivations to make a change include:
-</para>
-
-<indexterm><primary>manageability</primary></indexterm>
-<indexterm><primary>functionality</primary></indexterm>
-<indexterm><primary>operating costs</primary></indexterm>
-<indexterm><primary>support exposure</primary></indexterm>
-<indexterm><primary>licensing</primary></indexterm>
-
-<itemizedlist>
- <listitem><para>Improve network manageability.</para></listitem>
- <listitem><para>Obtain better user-level functionality.</para></listitem>
- <listitem><para>Reduce network operating costs.</para></listitem>
- <listitem><para>Reduce exposure caused by Microsoft withdrawal of NT4 support.</para></listitem>
- <listitem><para>Avoid MS License 6 implications.</para></listitem>
- <listitem><para>Reduce organization's dependency on Microsoft.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>alternative solution</primary></indexterm>
-<indexterm><primary>advantages</primary></indexterm>
-<indexterm><primary>core values</primary></indexterm>
-<indexterm><primary>migration</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>without ADS</primary></indexterm>
-Make sure everyone knows that Samba is not MS Windows NT4. Samba-3 offers
-an alternative solution that is both different from MS Windows NT4 and offers
-advantages compared with it. Gain recognition that Samba lacks many of the
-features that Microsoft has promoted as core values in migration from MS Windows NT4 to
-MS Windows 2000 and beyond (with or without Active Directory services).
-</para>
-
-<para>
-What are the features that Samba cannot provide?
-</para>
-
-<indexterm><primary>Active Directory Server</primary></indexterm>
-<indexterm><primary>Group Policy Objects</primary></indexterm>
-<indexterm><primary>Machine Policy Objects</primary></indexterm>
-<indexterm><primary>Logon Scripts</primary></indexterm>
-<indexterm><primary>Access Controls</primary></indexterm>
-
-<itemizedlist>
- <listitem><para>Active Directory Server.</para></listitem>
- <listitem><para>Group Policy Objects (in Active Directory).</para></listitem>
- <listitem><para>Machine Policy Objects.</para></listitem>
- <listitem><para>Logon Scripts in Active Directory.</para></listitem>
- <listitem><para>Software Application and Access Controls in Active Directory.</para></listitem>
-</itemizedlist>
-
-<para>
-The features that Samba does provide and that may be of compelling interest to your site
-include:
-</para>
-
-<indexterm><primary>ownership cost</primary></indexterm>
-<indexterm><primary>Global support</primary></indexterm>
-<indexterm><primary>Dynamic SMB servers</primary></indexterm>
-<indexterm><primary>on-the-fly logon scripts</primary></indexterm>
-<indexterm><primary>on-the-fly policy files</primary></indexterm>
-<indexterm><primary>stability</primary></indexterm>
-<indexterm><primary>reliability</primary></indexterm>
-<indexterm><primary>performance</primary></indexterm>
-<indexterm><primary>availability</primary></indexterm>
-<indexterm><primary>Manageability</primary></indexterm>
-<indexterm><primary>backend authentication</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>ldapsam</primary></indexterm>
-<indexterm><primary>single-sign-on</primary></indexterm>
-<indexterm><primary>distribute authentication systems</primary></indexterm>
-
-<itemizedlist>
- <listitem><para>Lower cost of ownership.</para></listitem>
- <listitem><para>Global availability of support with no strings attached.</para></listitem>
- <listitem><para>Dynamic SMB servers (can run more than one SMB/CIFS server per UNIX/Linux system).</para></listitem>
- <listitem><para>Creation of on-the-fly logon scripts.</para></listitem>
- <listitem><para>Creation of on-the-fly policy files.</para></listitem>
- <listitem><para>Greater stability, reliability, performance, and availability.</para></listitem>
- <listitem><para>Manageability via an SSH connection.</para></listitem>
- <listitem><para>Flexible choices of backend authentication technologies (tdbsam, ldapsam).</para></listitem>
- <listitem><para>Ability to implement a full single-sign-on architecture.</para></listitem>
- <listitem><para>Ability to distribute authentication systems for absolute minimum wide-area network bandwidth demand.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>successful migration</primary></indexterm>
-Before migrating a network from MS Windows NT4 to Samba, consider all necessary factors. Users
-should be educated about changes they may experience so the change will be a welcome one
-and not become an obstacle to the work they need to do. The following sections explain factors that will
-help ensure a successful migration.
-</para>
-
-<sect3>
-<title>Domain Layout</title>
-
-<para>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>backup domain controller</primary></indexterm>
-<indexterm><primary>secondary controller</primary></indexterm>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>standalone server</primary></indexterm>
-<indexterm><primary>network security</primary></indexterm>
-<indexterm><primary>domain context</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDCs</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>authentication backend</primary></indexterm>
-<indexterm><primary>complex organization</primary></indexterm>
-<indexterm><primary>LDAP database</primary></indexterm>
-<indexterm><primary>master server</primary></indexterm>
-<indexterm><primary>slave servers</primary></indexterm>
-<indexterm><primary>multiple domains</primary></indexterm>
-Samba can be configured as a domain controller, a backup domain controller (probably best called
-a secondary controller), a domain member, or a standalone server. The Windows network security
-domain context should be sized and scoped before implementation. Particular attention needs to be
-paid to the location of the Primary Domain Controller (PDC) as well as backup controllers (BDCs).
-One way in which Samba differs from Microsoft technology is that if one chooses to use an LDAP
-authentication backend, then the same database can be used by several different domains. In a
-complex organization, there can be a single LDAP database, which itself can be distributed (have
-a master server and multiple slave servers) that can simultaneously serve multiple domains.
-</para>
-
-<para>
-<indexterm><primary>network bandwidth</primary></indexterm>
-From a design perspective, the number of users per server as well as the number of servers per
-domain should be scaled taking into consideration server capacity and network bandwidth.
-</para>
-
-<para>
-<indexterm><primary>network segment</primary></indexterm>
-<indexterm><primary>multiple network segments</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>ping</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>remote segment</primary></indexterm>
-A physical network segment may house several domains. Each may span multiple network segments.
-Where domains span routed network segments, consider and test the performance implications of
-the design and layout of a network. A centrally located domain controller that is designed to
-serve multiple routed network segments may result in severe performance problems. Check the
-response time (ping timing) between the remote segment and the PDC. If it's long (more than 100 ms),
-locate a BDC on the remote segment to serve as the local authentication and access control server.
-</para>
-</sect3>
-
-<sect3>
-<title>Server Share and Directory Layout</title>
-
-<para>
-<indexterm><primary>Simplicity is king</primary></indexterm>
-<indexterm><primary>well-controlled network</primary></indexterm>
-There are cardinal rules to effective network design that cannot be broken with impunity.
-The most important rule: Simplicity is king in every well-controlled network. Every part of
-the infrastructure must be managed; the more complex it is, the greater will be the demand
-of keeping systems secure and functional.
-</para>
-
-<para>
-<indexterm><primary>disk space</primary></indexterm>
-<indexterm><primary>backed up</primary></indexterm>
-<indexterm><primary>tape</primary></indexterm>
-<indexterm><primary>backup</primary></indexterm>
-<indexterm><primary>validate every backup</primary></indexterm>
-<indexterm><primary>disaster recovery</primary></indexterm>
-Keep in mind the nature of how data must be shared. Physical disk space layout should be considered
-carefully. Some data must be backed up. The simpler the disk layout, the easier it will be to
-keep track of backup needs. Identify what backup media will meet your needs; consider backup to tape,
-CD-ROM or DVD-ROM, or other offline storage medium. Plan and implement for minimum
-maintenance. Leave nothing to chance in your design; above all, do not leave backups to chance:
-backup, test, and validate every backup; create a disaster recovery plan and prove that it works.
-</para>
-
-<para>
-<indexterm><primary>access control needs</primary></indexterm>
-<indexterm><primary>group permissions</primary></indexterm>
-<indexterm><primary>sticky bit</primary></indexterm>
-Users should be grouped according to data access control needs. File and directory access
-is best controlled via group permissions, and the use of the <quote>sticky bit</quote> on group-controlled
-directories may substantially avoid file access complaints from Samba share users.
-</para>
-
-<para>
-<indexterm><primary>network administrators</primary></indexterm>
-<indexterm><primary>document design</primary></indexterm>
-<indexterm><primary>simple access controls</primary></indexterm>
-<indexterm><primary>obtuse complexity</primary></indexterm>
-<indexterm><primary>document design</primary></indexterm>
-Inexperienced network administrators often attempt elaborate techniques to set access
-controls on files, directories, shares, as well as in share definitions.
-Keep your design and implementation simple and document your design extensively. Have others
-audit your documentation. Do not create a complex mess that your successor will not understand.
-Remember, job security through complex design and implementation may cause loss of operations
-and downtime to users as the new administrator learns to untangle your knots. Keep access
-controls simple and effective, and make sure that users will never be interrupted by obtuse
-complexity.
-</para>
-</sect3>
-
-<sect3>
-<title>Logon Scripts</title>
-
-<para>
-<indexterm><primary>Logon scripts</primary></indexterm>
-Logon scripts can help to ensure that all users gain the share and printer connections they need.
-</para>
-
-<para>
-Logon scripts can be created on the fly so all commands executed are specific to the
-rights and privileges granted to the user. The preferred controls should be effected through
-group membership so group information can be used to create a custom logon script using
-the <smbconfoption name="root preexec"/> parameters to the <smbconfsection name="NETLOGON"/> share.
-</para>
-
-<para>
-<indexterm><primary>kixstart</primary></indexterm>
-Some sites prefer to use a tool such as <command>kixstart</command> to establish a controlled
-user environment. In any case, you may wish to do a Google search for logon script process controls.
-In particular, you may wish to explore the use of the Microsoft Knowledge Base article KB189105 that
-deals with how to add printers without user intervention via the logon script process.
-</para>
-</sect3>
-
-<sect3>
-<title>Profile Migration/Creation</title>
-
-<para>
-User and group profiles may be migrated using the tools described in the section titled Desktop Profile
-Management.
-</para>
-
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>NTuser.DAT</primary></indexterm>
-Profiles may also be managed using the Samba tool <command>profiles</command>. This tool allows the MS
-Windows NT-style security identifiers (SIDs) that are stored inside the profile
-<filename>NTuser.DAT</filename> file to be changed to the SID of the Samba domain.
-</para>
-</sect3>
-
-<sect3>
-<title>User and Group Accounts</title>
-
-<para>
-<indexterm><primary>migrate account settings</primary></indexterm>
-<indexterm><primary>migrate user</primary></indexterm>
-<indexterm><primary>migrate group</primary></indexterm>
-<indexterm><primary>map</primary></indexterm>
-It is possible to migrate all account settings from an MS Windows NT4 domain to Samba. Before
-attempting to migrate user and group accounts, you are STRONGLY advised to create in Samba the
-groups that are present on the MS Windows NT4 domain <emphasis>AND</emphasis> to map them to
-suitable UNIX/Linux groups. By following this simple advice, all user and group attributes
-should migrate painlessly.
-</para>
-</sect3>
-
-</sect2>
-
-<sect2>
-<title>Steps in Migration Process</title>
-
-<para>
-The approximate migration process is described below.
-</para>
-
-<itemizedlist>
- <listitem><para>
- You have an NT4 PDC that has the users, groups, policies, and profiles to be migrated.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>netlogon share</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
- Samba is set up as a domain controller with netlogon share, profile share, and so on. Configure the &smb.conf; file
- to function as a BDC: <parameter>domain master = No</parameter>.
- </para></listitem>
-</itemizedlist>
-
-<procedure>
-<title>The Account Migration Process</title>
-
- <step><para>
- <indexterm><primary>pdbedit</primary></indexterm>
- Create a BDC account in the old NT4 domain for the Samba server using NT Server Manager.
- <emphasis>Samba must not be running.</emphasis>
- </para></step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
- <userinput>net rpc join -S <replaceable>NT4PDC</replaceable> -w <replaceable>DOMNAME</replaceable> -U
- Administrator%<replaceable>passwd</replaceable></userinput>
- </para></step>
-
- <step><para>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
- <userinput>net rpc vampire -S <replaceable>NT4PDC</replaceable> -U
- administrator%<replaceable>passwd</replaceable></userinput>
- </para></step>
-
-<indexterm><primary>pdbedit</primary></indexterm>
- <step><para><userinput>pdbedit -L</userinput></para>
- <para>Note: Did the users migrate?</para>
- </step>
-
- <step><para>
- <indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
- <indexterm><primary>initGroups.sh</primary></indexterm>
- Now assign each of the UNIX groups to NT groups:
- (It may be useful to copy this text to a script called <filename>initGroups.sh</filename>)
- <programlisting>
-#!/bin/bash
-#### Keep this as a shell script for future re-use
-
-# First assign well known domain global groups
-net groupmap add ntgroup="Domain Admins" unixgroup=root rid=512 type=d
-net groupmap add ntgroup="Domain Users" unixgroup=users rid=513 type=d
-net groupmap add ntgroup="Domain Guests" unixgroup=nobody rid=514 type=d
-
-# Now for our added domain global groups
-net groupmap add ntgroup="Designers" unixgroup=designers type=d
-net groupmap add ntgroup="Engineers" unixgroup=engineers type=d
-net groupmap add ntgroup="QA Team" unixgroup=qateam type=d
-</programlisting>
- </para></step>
-
- <step><para><userinput>net groupmap list</userinput></para>
- <para>Check that all groups are recognized.
- </para></step>
-</procedure>
-
-<para>
-Migrate all the profiles, then migrate all policy files.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Migration Options</title>
-
-<para>
-Sites that wish to migrate from MS Windows NT4 domain control to a Samba-based solution
-generally fit into three basic categories. <link linkend="majtypes">Following table</link> shows the possibilities.
-</para>
-
-<table frame="all" id="majtypes"><title>The Three Major Site Types</title>
-<tgroup cols="2">
- <colspec align="left"/>
- <colspec align="justify"/>
- <thead>
- <row><entry>Number of Users</entry><entry>Description</entry></row>
- </thead>
- <tbody>
- <row><entry>< 50</entry><entry><para>Want simple conversion with no pain.</para></entry></row>
- <row><entry>50 - 250</entry><entry><para>Want new features; can manage some inhouse complexity.</para></entry></row>
- <row><entry>> 250</entry><entry><para>Solution/implementation must scale well; complex needs.
- Cross-departmental decision process. Local expertise in most areas.</para></entry></row>
- </tbody>
-</tgroup>
-</table>
-
-<sect2>
-<title>Planning for Success</title>
-
-<para>
-There are three basic choices for sites that intend to migrate from MS Windows NT4
-to Samba:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Simple conversion (total replacement).
- </para></listitem>
-
- <listitem><para>
- Upgraded conversion (could be one of integration).
- </para></listitem>
-
- <listitem><para>
- Complete redesign (completely new solution).
- </para></listitem>
-</itemizedlist>
-
-<para>
-Minimize downstream problems by:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Taking sufficient time.
- </para></listitem>
-
- <listitem><para>
- Avoiding panic.
- </para></listitem>
-
- <listitem><para>
- Testing all assumptions.
- </para></listitem>
-
- <listitem><para>
- Testing the full roll-out program, including workstation deployment.
- </para></listitem>
-</itemizedlist>
-
-<para><link linkend="natconchoices">Following table</link> lists the conversion choices given the type of migration
-being contemplated.
-</para>
-
-<table frame="all" id="natconchoices"><title>Nature of the Conversion Choices</title>
-<tgroup cols="3">
- <colspec align="justify" colwidth="1*"/>
- <colspec align="justify" colwidth="1*"/>
- <colspec align="justify" colwidth="1*"/>
- <thead>
- <row><entry>Simple Install</entry><entry>Upgrade Decisions</entry><entry>Redesign Decisions</entry></row>
- </thead>
- <tbody>
- <row>
- <entry><para>Make use of minimal OS-specific features</para></entry>
- <entry><para>Translate NT4 features to new host OS features</para></entry>
- <entry><para>Improve on NT4 functionality, enhance management capabilities</para></entry>
- </row>
- <row>
- <entry><para>Move all accounts from NT4 into Samba</para></entry>
- <entry><para>Copy and improve</para></entry>
- <entry><para>Authentication regime (database location and access)</para></entry>
- </row>
- <row>
- <entry><para>Make least number of operational changes</para></entry>
- <entry><para>Make progressive improvements</para></entry>
- <entry><para>Desktop management methods</para></entry>
- </row>
- <row>
- <entry><para>Take least amount of time to migrate</para></entry>
- <entry><para>Minimize user impact</para></entry>
- <entry><para>Better control of Desktops/Users</para></entry>
- </row>
- <row>
- <entry><para>Live versus isolated conversion</para></entry>
- <entry><para>Maximize functionality</para></entry>
- <entry><para>Identify Needs for: <emphasis>Manageability, Scalability, Security, Availability</emphasis></para></entry>
- </row>
- <row>
- <entry><para>Integrate Samba, then migrate while users are active, then change of control (swap out)</para></entry>
- <entry><para>Take advantage of lower maintenance opportunity</para></entry>
- <entry><para></para></entry>
- </row>
- </tbody>
-</tgroup>
-</table>
-</sect2>
-
-<sect2>
-<title>Samba Implementation Choices</title>
-
-<variablelist>
- <varlistentry><term>Authentication Database/Backend</term><listitem>
- <para>
- Samba can use an external authentication backend:
- </para>
-
- <para>
- <itemizedlist>
- <listitem><para>Winbind (external Samba or NT4/200x server).</para></listitem>
- <listitem><para>External server could use Active Directory or NT4 domain.</para></listitem>
- <listitem><para>Can use pam_mkhomedir.so to autocreate home directories.</para></listitem>
- <listitem><para> Samba can use a local authentication backend: <parameter>smbpasswd</parameter>,
- <parameter>tdbsam</parameter>, <parameter>ldapsam</parameter>
- </para></listitem>
- </itemizedlist></para></listitem>
- </varlistentry>
-
- <varlistentry><term>Access Control Points</term><listitem>
- <para>
- Samba permits Access Control points to be set:
- </para>
-
-<indexterm><primary>share ACLs</primary></indexterm>
-<indexterm><primary>UNIX permissions</primary></indexterm>
-<indexterm><primary>POSIX ACLS</primary></indexterm>
-<indexterm><primary>share stanza controls</primary></indexterm>
-
- <itemizedlist>
- <listitem><para>On the share itself &smbmdash; using share ACLs.</para></listitem>
- <listitem><para>On the file system &smbmdash; using UNIX permissions on files and directories.</para>
- <para>Note: Can enable Posix ACLs in file system also.</para></listitem>
- <listitem><para>Through Samba share parameters &smbmdash; not recommended except as last resort.</para></listitem>
- </itemizedlist></listitem>
- </varlistentry>
-
- <varlistentry><term>Policies (migrate or create new ones)</term><listitem>
- <para>
-<indexterm><primary>policies</primary></indexterm>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
- Exercise great caution when making registry changes; use the right tool and be aware
- that changes made through NT4-style <filename>NTConfig.POL</filename> files can leave
- permanent changes.
-<indexterm><primary>Group Policy Editor</primary></indexterm>
-<indexterm><primary>tattoo effect</primary></indexterm>
-<indexterm><primary>permanent changes</primary></indexterm>
- </para>
- <itemizedlist>
- <listitem><para>Using Group Policy Editor (NT4).</para></listitem>
- <listitem><para>Watch out for tattoo effect.</para></listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>User and Group Profiles</term><listitem>
- <para>
-<indexterm><primary>NTUser.DAT</primary></indexterm>
-<indexterm><primary>SIDs</primary></indexterm>
- Platform-specific, so use platform tool to change from a local to a roaming profile.
- Can use new profiles tool to change SIDs (<filename>NTUser.DAT</filename>).
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>Logon Scripts</term><listitem>
- <para>
- Know how they work.
- </para>
- </listitem>
- </varlistentry>
-
-
- <varlistentry><term>User and Group Mapping to UNIX/Linux</term><listitem>
- <para>
- <indexterm><primary>pdbedit</primary></indexterm>
- User and group mapping code is new. Many problems have been experienced as network administrators
- who are familiar with Samba-2.2.x migrate to Samba-3. Carefully study the chapters that document
- the new password backend behavior and the new group mapping functionality.
- </para>
- <itemizedlist>
- <listitem><para>The <parameter>username map</parameter> facility may be needed.</para></listitem>
- <listitem><para>Use <command>net groupmap</command> to connect NT4 groups to UNIX groups.</para></listitem>
- <listitem><para>
- Use <command>pdbedit</command> to set/change user configuration.
- </para>
-
- <para>
- When migrating to LDAP backend, it may be easier to dump the initial
- LDAP database to LDIF, edit, then reload into LDAP.
- </para></listitem>
- </itemizedlist></listitem>
- </varlistentry>
-
- <varlistentry><term>OS-Specific Scripts/Programs May be Needed</term><listitem>
- <para>
- Every operating system has its peculiarities. These are the result of engineering decisions
- that were based on the experience of the designer and may have side effects that were not
- anticipated. Limitations that may bite the Windows network administrator include:
- </para>
- <itemizedlist>
- <listitem><para>Add/Delete Users: Note OS limits on size of name
- (Linux 8 chars, NT4 up to 254 chars).</para></listitem>
- <listitem><para>Add/Delete Machines: Applied only to domain members
- (Note: machine names may be limited to 16 characters).</para></listitem>
- <listitem><para>Use <command>net groupmap</command> to connect NT4 groups to UNIX groups.</para></listitem>
- <listitem><para>Add/Delete Groups: Note OS limits on size and nature.
- Linux limit is 16 char, no spaces, and no uppercase chars (<command>groupadd</command>).</para></listitem>
- </itemizedlist></listitem>
- </varlistentry>
-
- <varlistentry><term>Migration Tools</term><listitem>
- <para>
- <indexterm><primary>pdbedit</primary></indexterm>
- Domain Control (NT4-Style) Profiles, Policies, Access Controls, Security
- <itemizedlist>
- <listitem><para>Samba: <command>net, rpcclient, smbpasswd, pdbedit, profiles</command></para></listitem>
- <listitem><para>Windows: <command>NT4 Domain User Manager, Server Manager (NEXUS)</command></para></listitem>
- </itemizedlist></para></listitem>
- </varlistentry>
-</variablelist>
-
-</sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="NetworkBrowsing">
-<chapterinfo>
- &author.jht;
- &author.jelmer;
- <author>
- <firstname>Jonathan</firstname><surname>Johnson</surname>
- <affiliation>
- <orgname>Sutinen Consulting, Inc.</orgname>
- <address><email>jon@sutinen.com</email></address>
- </affiliation>
- </author>
- <pubdate>July 5, 1998</pubdate>
- <pubdate>Updated: September 20, 2006</pubdate>
-</chapterinfo>
-
-<title>Network Browsing</title>
-
-<para>
-<indexterm><primary>browsing across subnets</primary></indexterm>
-<indexterm><primary>resolution of NetBIOS names</primary></indexterm>
-<indexterm><primary>browse list handling</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-This chapter contains detailed information as well as a fast-track guide to
-implementing browsing across subnets and/or across workgroups (or domains).
-WINS is the best tool for resolution of NetBIOS names to IP addresses; however, WINS is
-not involved in browse list handling except by way of name-to-address resolution.
-</para>
-
-<note><para>
-<indexterm><primary>WINS</primary></indexterm>
-What is WINS?
-</para>
-<para>
-WINS is a facility that provides resolution of a NetBIOS name to its IP address. WINS is like a
-Dynamic-DNS service for NetBIOS networking names.
-</para></note>
-
-<note><para>
-<indexterm><primary>Windows 2000</primary></indexterm>
-<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-MS Windows 2000 and later versions can be configured to operate with no NetBIOS
-over TCP/IP. Samba and later versions also support this mode of operation.
-When the use of NetBIOS over TCP/IP has been disabled, the primary
-means for resolution of MS Windows machine names is via DNS and Active Directory.
-The following information assumes that your site is running NetBIOS over TCP/IP.
-</para></note>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-Charles Dickens once referred to the past in these words: <quote><emphasis>It was the best of times,
-it was the worst of times.</emphasis></quote> The more we look back, the more we long for what was and
-hope it never returns.
-</para>
-
-
-<para>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>NetBIOS networking</primary></indexterm>
-<indexterm><primary>fickle</primary></indexterm>
-For many MS Windows network administrators, that statement sums up their feelings about
-NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle
-nature was just par for the course. For those who never quite managed to tame its
-lusty features, NetBIOS is like Paterson's Curse.
-</para>
-
-<para>
-For those not familiar with botanical problems in Australia, Paterson's Curse,
-<emphasis>Echium plantagineum</emphasis>, was introduced to Australia from Europe during the mid-19th
-century. Since then it has spread rapidly. The high seed production, with densities of
-thousands of seeds per square meter, a seed longevity of more than 7 years, and an
-ability to germinate at any time of year, given the right conditions, are some of the
-features that make it such a persistent weed.
-</para>
-
-<para>
-<indexterm><primary>Network Basic Input/Output System</primary><see>NetBIOS</see></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>TCP/IP</primary></indexterm>
-<indexterm><primary>Windows network clients</primary></indexterm>
-In this chapter we explore vital aspects of Server Message Block (SMB) networking with
-a particular focus on SMB as implemented through running NetBIOS (Network Basic
-Input/Output System) over TCP/IP. Since Samba does not implement SMB or NetBIOS over
-any other protocols, we need to know how to configure our network environment and simply
-remember to use nothing but TCP/IP on all our MS Windows network clients.
-</para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>MS WINS</primary></indexterm>
-Samba provides the ability to implement a WINS (Windows Internetworking Name Server)
-and implements extensions to Microsoft's implementation of WINS. These extensions
-help Samba to effect stable WINS operations beyond the normal scope of MS WINS.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
-<indexterm><primary>NetBIOS disabled</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-WINS is exclusively a service that applies only to those systems
-that run NetBIOS over TCP/IP. MS Windows 200x/XP have the capacity to operate with
-support for NetBIOS disabled, in which case WINS is of no relevance. Samba supports this also.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS disabled</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-For those networks on which NetBIOS has been disabled (i.e., WINS is not required),
-the use of DNS is necessary for hostname resolution.
-</para>
-
-</sect1>
-
-<sect1>
-<title>What Is Browsing?</title>
-
-<para>
-<indexterm><primary>browsing</primary></indexterm>
-<indexterm><primary>Network Neighborhood</primary></indexterm>
-<indexterm><primary>shares</primary></indexterm>
-<indexterm><primary>printers available</primary></indexterm>
-To most people, browsing means they can see the MS Windows and Samba servers
-in the Network Neighborhood, and when the computer icon for a particular server is
-clicked, it opens up and shows the shares and printers available on the target server.
-</para>
-
-<para>
-What seems so simple is in fact a complex interaction of different technologies.
-The technologies (or methods) employed in making all of this work include:
-</para>
-
-<itemizedlist>
- <listitem><para>MS Windows machines register their presence to the network.</para></listitem>
- <listitem><para>Machines announce themselves to other machines on the network.</para></listitem>
- <listitem><para>One or more machines on the network collate the local announcements.</para></listitem>
- <listitem><para>The client machine finds the machine that has the collated list of machines.</para></listitem>
- <listitem><para>The client machine is able to resolve the machine names to IP addresses.</para></listitem>
- <listitem><para>The client machine is able to connect to a target machine.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>browse list management</primary></indexterm>
-<indexterm><primary>name resolution</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-The Samba application that controls browse list management and name resolution is
-called <filename>nmbd</filename>. The configuration parameters involved in nmbd's operation are:
-</para>
-
-<para>
-Browsing options:
-</para>
-<itemizedlist>
- <listitem><smbconfoption name="os level"/></listitem>
- <listitem><smbconfoption name="lm announce"/></listitem>
- <listitem><smbconfoption name="lm interval"/></listitem>
- <listitem><smbconfoption name="preferred master"/>(*)</listitem>
- <listitem><smbconfoption name="local master"/>(*)</listitem>
- <listitem><smbconfoption name="domain master"/>(*)</listitem>
- <listitem><smbconfoption name="browse list"/></listitem>
- <listitem><smbconfoption name="enhanced browsing"/></listitem>
-</itemizedlist>
-
-<para>
-Name Resolution Method:
-</para>
-<itemizedlist>
- <listitem><smbconfoption name="name resolve order"/>(*)</listitem>
-</itemizedlist>
-
-<para>
-WINS options:
-</para>
-<itemizedlist>
- <listitem><smbconfoption name="dns proxy"/></listitem>
- <listitem><smbconfoption name="wins proxy"/></listitem>
- <listitem><smbconfoption name="wins server"/>(*)</listitem>
- <listitem><smbconfoption name="wins support"/>(*)</listitem>
- <listitem><smbconfoption name="wins hook"/></listitem>
-</itemizedlist>
-
-<para>
-Those marked with an (*) are the only options that commonly may need to be modified. Even if none of these
-parameters is set, <filename>nmbd</filename> will still do its job.
-</para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>WINS Server</primary></indexterm>
-<indexterm><primary>WINS Support</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>mutually exclusive options</primary></indexterm>
-For Samba, the WINS Server and WINS Support are mutually exclusive options. When <command>nmbd</command> is
-started it will fail to execute if both options are set in the &smb.conf; file. The <command>nmbd</command>
-understands that when it spawns an instance of itself to run as a WINS server that it has to use its own WINS
-server also.
-</para>
-
-</sect1>
-
-<sect1 id="netdiscuss">
-<title>Discussion</title>
-
-<para>
-<indexterm><primary>SMB-based messaging</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>phasing out NetBIOS</primary></indexterm>
-All MS Windows networking uses SMB-based messaging. SMB messaging may be implemented with or without NetBIOS.
-MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft appears intent on phasing
-out NetBIOS support.
-</para>
-
-<sect2>
-<title>NetBIOS over TCP/IP</title>
-
-<para>
-<indexterm><primary>encapsulating</primary></indexterm>
-<indexterm><primary>broadcast</primary></indexterm>
-<indexterm><primary>unicast</primary></indexterm>
-<indexterm><primary>UDP</primary></indexterm>
-Samba implements NetBIOS, as does MS Windows NT/200x/XP, by encapsulating it over TCP/IP.
-NetBIOS-based networking uses broadcast messaging to effect browse list management. When running NetBIOS over
-TCP/IP, this uses UDP-based messaging. UDP messages can be broadcast or unicast.
-</para>
-
-<para>
-<indexterm><primary>UDP</primary></indexterm>
-Normally, only unicast UDP messaging can be forwarded by routers. The <smbconfoption name="remote announce"/>
-parameter to smb.conf helps to project browse announcements to remote network segments via unicast UDP.
-Similarly, the <smbconfoption name="remote browse sync"/> parameter of &smb.conf; implements browse list
-collation using unicast UDP.
-</para>
-
-<para>
-The methods used by MS Windows to perform name lookup requests (name resolution) is determined by a
-configuration parameter called the NetBIOS node-type. There are four basic NetBIOS node types:
-</para>
-
-<indexterm><primary>b-node</primary></indexterm>
-<indexterm><primary>p-node</primary></indexterm>
-<indexterm><primary>m-node</primary></indexterm>
-<indexterm><primary>h-node</primary></indexterm>
-<indexterm><primary>node-type</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>broadcast</primary></indexterm>
-<indexterm><primary>unicast</primary></indexterm>
-<itemizedlist>
- <listitem><para><emphasis>b-node (type 0x01):</emphasis> The Windows client will use only
- NetBIOS broadcast requests using UDP broadcast.</para></listitem>
- <listitem><para><emphasis>p-node (type 0x02):</emphasis> The Windows client will use point-to-point
- (NetBIOS unicast) requests using UDP unicast directed to a WINS server.</para></listitem>
- <listitem><para><emphasis>m-node (type 0x04):</emphasis> The Windows client will first use
- NetBIOS broadcast requests using UDP broadcast, then it will use (NetBIOS unicast)
- requests using UDP unicast directed to a WINS server.</para></listitem>
- <listitem><para><emphasis>h-node (type 0x08):</emphasis> The Windows client will use
- (NetBIOS unicast) requests using UDP unicast directed to a WINS server, then it will use
- NetBIOS broadcast requests using UDP broadcast.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>h-node</primary></indexterm>
-<indexterm><primary>hybrid</primary></indexterm>
-<indexterm><primary>enables NetBIOS over TCP/IP</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>broadcast-based</primary></indexterm>
-<indexterm><primary>name resolution</primary></indexterm>
-The default Windows network client (or server) network configuration enables NetBIOS over TCP/IP
-and b-node configuration. The use of WINS makes most sense with h-node (hybrid mode) operation so that
-in the event of a WINS breakdown or non-availability, the client can use broadcast-based name resolution.
-</para>
-
-<para>
-<indexterm><primary>LMB</primary><see>Local Master Browser</see></indexterm>
-<indexterm><primary>Local Master Browser</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>cross-segment browsing</primary></indexterm>
-<indexterm><primary>network segment</primary></indexterm>
-In those networks where Samba is the only SMB server technology, wherever possible <filename>nmbd</filename>
-should be configured on one machine as the WINS server. This makes it easy to manage the browsing environment.
-If each network segment is configured with its own Samba WINS server, then the only way to get cross-segment
-browsing to work is by using the <smbconfoption name="remote announce"/> and the <smbconfoption name="remote
-browse sync"/> parameters to your &smb.conf; file.
-</para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-If only one WINS server is used for an entire multisegment network, then
-the use of the <smbconfoption name="remote announce"/> and the
-<smbconfoption name="remote browse sync"/> parameters should not be necessary.
-</para>
-
-<para>
-<indexterm><primary>replication</primary><secondary>WINS</secondary></indexterm>
-As of Samba-3, WINS replication is being worked on. The bulk of the code has been committed, but it still
-needs maturation. This is not a supported feature of the Samba-3.0.20 release. Hopefully, this will become a
-supported feature of one of the Samba-3 release series. The delay is caused by the fact that this feature has
-not been of sufficient significance to inspire someone to pay a developer to complete it.
-</para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>MS-WINS replication</primary></indexterm>
-<indexterm><primary>redundancy</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>NetBIOSless SMB over TCP/IP</primary></indexterm>
-<indexterm><primary>local names</primary></indexterm>
-<indexterm><primary>subnets</primary></indexterm>
-<indexterm><primary>multiple WINS servers</primary></indexterm>
-Right now Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS
-server, there must only be one <filename>nmbd</filename> configured as a WINS server on the network. Some
-sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used
-<smbconfoption name="remote browse sync"/> and <smbconfoption name="remote announce"/> to effect browse list
-collation across all segments. Note that this means clients will only resolve local names and must be
-configured to use DNS to resolve names on other subnets in order to resolve the IP addresses of the servers
-they can see on other subnets. This setup is not recommended but is mentioned as a practical consideration
-(i.e., an <quote>if all else fails</quote> scenario). NetBIOS over TCP/IP is an ugly and difficult to manage
-protocol. Its replacement, NetBIOSless SMB over TCP/IP is not without its own manageability concerns. NetBIOS
-based networking is a life of compromise and trade-offs. WINS stores information that cannot be stored in
-DNS; consequently, DNS is a poor substitute for WINS given that when NetBIOS over TCP/IP is used, Windows
-clients are designed to use WINS.
-</para>
-
-<para>
-<indexterm><primary>broadcast messages</primary></indexterm>
-<indexterm><primary>repeated intervals</primary></indexterm>
-<indexterm><primary>across network segments</primary></indexterm>
-Lastly, take note that browse lists are a collection of unreliable broadcast
-messages that are repeated at intervals of not more than 15 minutes. This means
-that it will take time to establish a browse list, and it can take up to 45
-minutes to stabilize, particularly across network segments.
-</para>
-
-<para>
-<indexterm><primary>Windows 200x/XP</primary></indexterm>
-When an MS Windows 200x/XP system attempts to resolve a host name to an IP address, it follows a defined path:
-</para>
-
-<orderedlist>
- <listitem><para>
- Checks the <filename>hosts</filename> file. It is located in <filename>%SystemRoot%\System32\Drivers\etc</filename>.
- </para></listitem>
-
- <listitem><para>
- Does a DNS lookup.
- </para></listitem>
-
- <listitem><para>
- Checks the NetBIOS name cache.
- </para></listitem>
-
- <listitem><para>
- Queries the WINS server.
- </para></listitem>
-
- <listitem><para>
- Does a broadcast name lookup over UDP.
- </para></listitem>
-
- <listitem><para>
- Looks up entries in LMHOSTS, located in <filename>%SystemRoot%\System32\Drivers\etc</filename>.
- </para></listitem>
-</orderedlist>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
-<indexterm><primary>name lookups</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-Given the nature of how the NetBIOS over TCP/IP protocol is implemented, only WINS is capable of resolving
-with any reliability name lookups for service-oriented names such as TEMPTATION<1C> &smbmdash; a NetBIOS
-name query that seeks to find network logon servers. DNS has no concept of service-oriented names such as
-this. In fact, the Microsoft ADS implementation specifically manages a whole range of extended
-service-oriented DNS entries. This type of facility is not implemented and is not supported for the NetBIOS
-over TCP/IP protocol namespace.
-</para>
-
-</sect2>
-
-<sect2>
-<title>TCP/IP without NetBIOS</title>
-
-<para>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>NetBIOS-less</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-All TCP/IP-enabled systems use various forms of hostname resolution. The primary
-methods for TCP/IP hostname resolution involve either a static file (<filename>/etc/hosts</filename>)
-or the Domain Name System (DNS). DNS is the technology that makes
-the Internet usable. DNS-based hostname resolution is supported by nearly all
-TCP/IP-enabled systems. Only a few embedded TCP/IP systems do not support DNS.
-</para>
-
-<para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>DDNS</primary></indexterm>
-<indexterm><primary>ipconfig</primary></indexterm>
-<indexterm><primary>Dynamic DNS</primary><see>DDNS</see></indexterm>
-Windows 200x/XP can register its hostname with a Dynamic DNS server (DDNS). It is possible to force register with a
-dynamic DNS server in Windows 200x/XP using <command>ipconfig /registerdns</command>.
-</para>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>severely impaired</primary></indexterm>
-With Active Directory, a correctly functioning DNS server is absolutely essential. In the absence of a working
-DNS server that has been correctly configured, MS Windows clients and servers will be unable to locate each
-other, so network services consequently will be severely impaired.
-</para>
-
-<para>
-<indexterm><primary>raw SMB over TCP/IP</primary></indexterm>
-<indexterm><primary>No NetBIOS layer</primary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>domain member server</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-Use of raw SMB over TCP/IP (No NetBIOS layer) can be done only with Active Directory domains. Samba is not an
-Active Directory domain controller: ergo, it is not possible to run Samba as a domain controller and at the same
-time <emphasis>not</emphasis> use NetBIOS. Where Samba is used as an Active Directory domain member server
-(DMS) it is possible to configure Samba to not use NetBIOS over TCP/IP. A Samba DMS can integrate fully into
-an Active Directory domain, however, if NetBIOS over TCP/IP is disabled, it is necessary to manually create
-appropriate DNS entries for the Samba DMS because they will not be automatically generated either by Samba, or
-by the ADS environment.
-</para>
-
-</sect2>
-
-<sect2 id="adsdnstech">
-<title>DNS and Active Directory</title>
-
-<para>
-<indexterm><primary>DNS</primary><secondary>Active Directory</secondary></indexterm>
-<indexterm><primary>DDNS</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>SRV records</primary></indexterm>
-<indexterm><primary>DNS</primary><secondary>SRV records</secondary></indexterm>
-Occasionally we hear from UNIX network administrators who want to use a UNIX-based DDNS server in place
-of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is
-autoconfigured to work with Active Directory. It is possible to use BIND version 8 or 9, but it will almost
-certainly be necessary to create service records (SRV records) so MS Active Directory clients can resolve
-hostnames to locate essential network services. The following are some of the default service records that
-Active Directory requires:
-</para>
-
-<para>
-<indexterm><primary>DDNS</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>BIND9</primary></indexterm>
-The use of DDNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for
-its ability to adequately support the SRV (service) records that are needed for Active Directory. Of course,
-when running ADS, it makes sense to use Microsoft's own DDNS server because of the natural affinity between ADS
-and MS DNS.
-</para>
-
-<variablelist>
-<varlistentry>
- <term>_ldap._tcp.pdc._msdcs.<emphasis>Domain</emphasis></term>
- <listitem>
- <para>
- This provides the address of the Windows NT PDC for the domain.
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term>_ldap._tcp.pdc._msdcs.<emphasis>DomainTree</emphasis></term>
- <listitem>
- <para>
- Resolves the addresses of global catalog servers in the domain.
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term>_ldap._tcp.<emphasis>site</emphasis>.sites.writable._msdcs.<emphasis>Domain</emphasis></term>
- <listitem>
- <para>
- Provides list of domain controllers based on sites.
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term>_ldap._tcp.writable._msdcs.<emphasis>Domain</emphasis></term>
- <listitem>
- <para>
- Enumerates list of domain controllers that have the writable copies of the Active Directory data store.
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term>_ldap._tcp.<emphasis>GUID</emphasis>.domains._msdcs.<emphasis>DomainTree</emphasis></term>
- <listitem>
- <para>
- Entry used by MS Windows clients to locate machines using the global unique identifier.
- </para>
- </listitem>
-</varlistentry>
-<varlistentry>
- <term>_ldap._tcp.<emphasis>Site</emphasis>.gc._msdcs.<emphasis>DomainTree</emphasis></term>
- <listitem>
- <para>
- Used by Microsoft Windows clients to locate the site configuration-dependent global catalog server.
- </para>
- </listitem>
-</varlistentry>
-</variablelist>
-
- <para>
- Specific entries used by Microsoft clients to locate essential services for an example domain
- called <constant>quenya.org</constant> include:
- </para>
-
- <itemizedlist>
- <listitem><para>
- _kerberos._udp.quenya.org &smbmdash; Used to contact the KDC server via UDP.
- This entry must list port 88 for each KDC.
- </para></listitem>
-
- <listitem><para>
- _kpasswd._udp.quenya.org &smbmdash; Used to locate the <constant>kpasswd</constant> server
- when a user password change must be processed. This record must list port 464 on the
- master KDC.
- </para></listitem>
-
- <listitem><para>
- _kerberos._tcp.quenya.org &smbmdash; Used to locate the KDC server via TCP.
- This entry must list port 88 for each KDC.
- </para></listitem>
-
- <listitem><para>
- _ldap._tcp.quenya.org &smbmdash; Used to locate the LDAP service on the PDC.
- This record must list port 389 for the PDC.
- </para></listitem>
-
- <listitem><para>
- _kpasswd._tcp.quenya.org &smbmdash; Used to locate the <constant>kpasswd</constant> server
- to permit user password changes to be processed. This must list port 464.
- </para></listitem>
-
- <listitem><para>
- _gc._tcp.quenya.org &smbmdash; Used to locate the global catalog server for the
- top of the domain. This must list port 3268.
- </para></listitem>
- </itemizedlist>
-
- <para>
- The following records are also used by the Windows domain member client to locate vital
- services on the Windows ADS domain controllers.
- </para>
-
- <itemizedlist>
- <listitem><para>
- _ldap._tcp.pdc._msdcs.quenya.org
- </para></listitem>
-
- <listitem><para>
- _ldap.gc._msdcs.quenya.org
- </para></listitem>
-
- <listitem><para>
- _ldap.default-first-site-name._sites.gc._msdcs.quenya.org
- </para></listitem>
-
- <listitem><para>
- _ldap.{SecID}.domains._msdcs.quenya.org
- </para></listitem>
-
- <listitem><para>
- _ldap._tcp.dc._msdcs.quenya.org
- </para></listitem>
-
- <listitem><para>
- _kerberos._tcp.dc._msdcs.quenya.org
- </para></listitem>
-
- <listitem><para>
- _ldap.default-first-site-name._sites.dc._msdcs.quenya.org
- </para></listitem>
-
- <listitem><para>
- _kerberos.default-first-site-name._sites.dc._msdcs.queyna.org
- </para></listitem>
-
- <listitem><para>
- SecID._msdcs.quenya.org
- </para></listitem>
- </itemizedlist>
-
- <para>
- Presence of the correct DNS entries can be validated by executing:
-<screen>
-&rootprompt; dig @frodo -t any _ldap._tcp.dc._msdcs.quenya.org
-
-; <lt;>> DiG 9.2.2 <lt;>> @frodo -t any _ldap._tcp.dc._msdcs.quenya.org
-;; global options: printcmd
-;; Got answer:
-;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3072
-;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
-
-
-;; QUESTION SECTION:
-;_ldap._tcp.dc._msdcs.quenya.org. IN ANY
-
-
-;; ANSWER SECTION:
-_ldap._tcp.dc._msdcs.quenya.org. 600 IN SRV 0 100 389 frodo.quenya.org.
-_ldap._tcp.dc._msdcs.quenya.org. 600 IN SRV 0 100 389 noldor.quenya.org.
-
-
-;; ADDITIONAL SECTION:
-frodo.quenya.org. 3600 IN A 10.1.1.16
-noldor.quenya.org. 1200 IN A 10.1.1.17
-
-
-;; Query time: 0 msec
-;; SERVER: frodo#53(10.1.1.16)
-;; WHEN: Wed Oct 7 14:39:31 2004
-;; MSG SIZE rcvd: 171
-</screen>
- </para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>How Browsing Functions</title>
-
-<para>
-<indexterm><primary>register NetBIOS names</primary></indexterm>
-<indexterm><primary>LMHOSTS</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>WINS server address</primary></indexterm>
-MS Windows machines register their NetBIOS names (i.e., the machine name for each service type in operation)
-on startup. The exact method by which this name registration takes place is determined by whether or not the
-MS Windows client/server has been given a WINS server address, whether or not LMHOSTS lookup is enabled,
-whether or not DNS for NetBIOS name resolution is enabled, and so on.
-</para>
-
-<para>
-<indexterm><primary>WINS server</primary></indexterm>
-<indexterm><primary>name lookups</primary></indexterm>
-<indexterm><primary>UDP</primary></indexterm>
-In the case where there is no WINS server, all name registrations as well as name lookups are done by UDP
-broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all names and IP
-addresses. In such situations, Samba provides a means by which the Samba server name may be forcibly injected
-into the browse list of a remote MS Windows network (using the <smbconfoption name="remote announce"/>
-parameter).
-</para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>UDP unicast</primary></indexterm>
-<indexterm><primary>name resolution across routed networks</primary></indexterm>
-Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such
-packets can be routed, and thus WINS allows name resolution to function across routed networks.
-</para>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>local master browser</primary><see>LMB</see></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>LMHOSTS</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>browse list</primary></indexterm>
-<indexterm><primary>election</primary></indexterm>
-<indexterm><primary>election criteria</primary></indexterm>
-During the startup process, an election takes place to create a local master browser (LMB) if one does not
-already exist. On each NetBIOS network one machine will be elected to function as the domain master browser
-(DMB). This domain browsing has nothing to do with MS security Domain Control. Instead, the DMB serves the
-role of contacting each LMB (found by asking WINS or from LMHOSTS) and exchanging browse list contents. This
-way every master browser will eventually obtain a complete list of all machines that are on the network. Every
-11 to 15 minutes an election is held to determine which machine will be the master browser. By the nature of
-the election criteria used, the machine with the highest uptime, or the most senior protocol version or other
-criteria, will win the election as DMB.
-</para>
-
-<para>
-<indexterm><primary>WINS server</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>NetBIOS name type</primary></indexterm>
-<indexterm><primary>n security context</primary></indexterm>
-<indexterm><primary>network segment</primary></indexterm>
-<indexterm><primary>authoritive</primary></indexterm>
-<indexterm><primary>browse list maintainers</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-Where a WINS server is used, the DMB registers its IP address with the WINS server using the name of the
-domain and the NetBIOS name type 1B (e.g., DOMAIN<1B>). All LMBs register their IP addresses with the WINS
-server, also with the name of the domain and the NetBIOS name type of 1D. The 1B name is unique to one
-server within the domain security context, and only one 1D name is registered for each network segment.
-Machines that have registered the 1D name will be authoritive browse list maintainers for the network segment
-they are on. The DMB is responsible for synchronizing the browse lists it obtains from the LMBs.
-</para>
-
-<para>
-<indexterm><primary>name resolution</primary></indexterm>
-Clients wishing to browse the network make use of this list but also depend on the availability of correct
-name resolution to the respective IP address or addresses.
-</para>
-
-<para>
-<indexterm><primary>browsing intrinsics</primary></indexterm>
-Any configuration that breaks name resolution and/or browsing intrinsics will annoy users because they will
-have to put up with protracted inability to use the network services.
-</para>
-
-<para>
-<indexterm><primary>forced synchronization</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>bridges networks</primary></indexterm>
-<indexterm><primary>cross-subnet browsing</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>/etc/hosts</primary></indexterm>
-Samba supports a feature that allows forced synchronization of browse lists across routed networks using the
-<smbconfoption name="remote browse sync"/> parameter in the &smb.conf; file. This causes Samba to contact the
-LMB on a remote network and to request browse list synchronization. This effectively bridges two networks that
-are separated by routers. The two remote networks may use either broadcast-based name resolution or WINS-based
-name resolution, but it should be noted that the <smbconfoption name="remote browse sync"/> parameter provides
-browse list synchronization &smbmdash; and that is distinct from name-to-address resolution. In other words,
-for cross-subnet browsing to function correctly, it is essential that a name-to-address resolution mechanism
-be provided. This mechanism could be via DNS, <filename>/etc/hosts</filename>, and so on.
-</para>
-
-<sect2 id="DMB">
-<title>Configuring Workgroup Browsing</title>
-
-<para>
-<indexterm><primary>cross-subnet browsing</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>isolated workgroup</primary></indexterm>
-<indexterm><primary>workgroup</primary></indexterm>
-To configure cross-subnet browsing on a network containing machines in a workgroup, not an NT domain, you need
-to set up one Samba server to be the DMB (note that this is not the same as a Primary Domain Controller,
-although in an NT domain the same machine plays both roles). The role of a DMB is to collate the browse lists
-from LMB on all the subnets that have a machine participating in the workgroup. Without one machine configured
-as a DMB, each subnet would be an isolated workgroup unable to see any machines on another subnet. It is the
-presence of a DMB that makes cross-subnet browsing possible for a workgroup.
-</para>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-In a workgroup environment the DMB must be a Samba server, and there must only be one DMB per workgroup name.
-To set up a Samba server as a DMB, set the following option in the <smbconfsection name="[global]"/> section
-of the &smb.conf; file:
-</para>
-
-<para>
-<smbconfblock>
-<smbconfoption name="domain master">yes</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-The DMB should preferably be the LMB for its own subnet. In order to achieve this, set the following options
-in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown in <link
-linkend="dmbexample">Domain Master Browser smb.conf</link>
-</para>
-
-<example id="dmbexample">
-<title>Domain Master Browser smb.conf</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="domain master">yes</smbconfoption>
-<smbconfoption name="local master">yes</smbconfoption>
-<smbconfoption name="preferred master">yes</smbconfoption>
-<smbconfoption name="os level">65</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>WINS server</primary></indexterm>
-The DMB may be the same machine as the WINS server, if necessary.
-</para>
-
-<para>
-<indexterm><primary>subnets</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>rebooted</primary></indexterm>
-Next, you should ensure that each of the subnets contains a machine that can act as an LMB for the workgroup.
-Any MS Windows NT/200x/XP machine should be able to do this, as will Windows 9x/Me machines (although these
-tend to get rebooted more often, so it is not such a good idea to use them). To make a Samba server an LMB,
-set the following options in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown in
-<link linkend="lmbexample">Local master browser smb.conf</link>
-</para>
-
-<example id="lmbexample">
-<title>Local master browser smb.conf</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="domain master">no</smbconfoption>
-<smbconfoption name="local master">yes</smbconfoption>
-<smbconfoption name="preferred master">yes</smbconfoption>
-<smbconfoption name="os level">65</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-Do not do this for more than one Samba server on each subnet, or they will war with
-each other over which is to be the LMB.
-</para>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>browser election</primary></indexterm>
-The <smbconfoption name="local master"/> parameter allows Samba to act as a
-LMB. The <smbconfoption name="preferred master"/> causes <command>nmbd</command>
-to force a browser election on startup and the <smbconfoption name="os level"/>
-parameter sets Samba high enough so it should win any browser elections.
-</para>
-
-<para>
-<indexterm><primary>disable LMB</primary></indexterm>
-If you have an NT machine on the subnet that you wish to be the LMB, you can disable Samba from
-becoming an LMB by setting the following options in the <smbconfsection name="[global]"/> section of the
-&smb.conf; file as shown in <link linkend="nombexample">smb.conf for Not Being a Master Browser</link>.
-</para>
-
-<para>
-<example id="nombexample">
-<title>smb.conf for Not Being a Master Browser</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="domain master">no</smbconfoption>
-<smbconfoption name="local master">no</smbconfoption>
-<smbconfoption name="preferred master">no</smbconfoption>
-<smbconfoption name="os level">0</smbconfoption>
-</smbconfblock>
-</example>
-</para>
-
-</sect2>
-
-<sect2>
-<title>Domain Browsing Configuration</title>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>registers</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-If you are adding Samba servers to a Windows NT domain, then you must not set up a Samba server as a DMB. By
-default, a Windows NT PDC for a domain is also the DMB for that domain. Network browsing may break if a Samba
-server other than the PDC registers the DMB NetBIOS name (<replaceable>DOMAIN</replaceable><1B>) with
-WINS.
-</para>
-
-<para>
-<indexterm><primary>Local Master Browser</primary></indexterm>
-For subnets other than the one containing the Windows NT PDC, you may set up Samba servers as LMBs as
-described. To make a Samba server a Local Master Browser, set the following options in the <smbconfsection
-name="[global]"/> section of the &smb.conf; file as shown in <link linkend="remsmb">Local Master Browser
-smb.conf</link>
-</para>
-
-<example id="remsmb">
-<title>Local Master Browser smb.conf</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="domain master">no</smbconfoption>
-<smbconfoption name="local master">yes</smbconfoption>
-<smbconfoption name="preferred master">yes</smbconfoption>
-<smbconfoption name="os level">65</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>election</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-If you wish to have a Samba server fight the election with machines on the same subnet, you may set the
-<smbconfoption name="os level"/> parameter to lower levels. By doing this you can tune the order of machines
-that will become LMBs if they are running. For more details on this, refer to <link
-linkend="browse-force-master">Forcing Samba to Be the Master</link>.
-</para>
-
-<para>
-<indexterm><primary>domain members</primary></indexterm>
-<indexterm><primary>browser elections</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-If you have Windows NT machines that are members of the domain on all subnets and you are sure they will
-always be running, you can disable Samba from taking part in browser elections and ever becoming an LMB by
-setting the following options in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown
-in <link linkend="xremmb">&smb.conf; for Not Being a master browser</link>
-</para>
-
-<para>
-<example id="xremmb">
-<title>&smb.conf; for Not Being a master browser</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="domain master">no</smbconfoption>
-<smbconfoption name="local master">no</smbconfoption>
-<smbconfoption name="preferred master">no</smbconfoption>
-<smbconfoption name="os level">0</smbconfoption>
-</smbconfblock>
-</example>
-</para>
-
-</sect2>
-
-<sect2 id="browse-force-master">
-<title>Forcing Samba to Be the Master</title>
-
-<para>
-<indexterm><primary>master browser</primary></indexterm>
-<indexterm><primary>election process</primary></indexterm>
-<indexterm><primary>broadcasts</primary></indexterm>
-<indexterm><primary>election packet</primary></indexterm>
-<indexterm><primary>bias</primary></indexterm>
-<indexterm><primary>election</primary></indexterm>
-<indexterm><primary>precedence</primary></indexterm>
-Who becomes the master browser is determined by an election process using broadcasts. Each election packet
-contains a number of parameters that determine what precedence (bias) a host should have in the election. By
-default Samba uses a low precedence and thus loses elections to just about every Windows network server or
-client.
-</para>
-
-<para>
-If you want Samba to win elections, set the <smbconfoption name="os level"/> global option in &smb.conf; to a
-higher number. It defaults to 20. Using 34 would make it win all elections over every other system (except
-other Samba systems).
-</para>
-
-<para>
-An <smbconfoption name="os level"/> of two would make it beat Windows for Workgroups and Windows 9x/Me, but
-not MS Windows NT/200x Server. An MS Windows NT/200x Server domain controller uses level 32. The maximum os
-level is 255.
-</para>
-
-<para>
-<indexterm><primary>force an election</primary></indexterm>
-<indexterm><primary>potential master browsers</primary></indexterm>
-<indexterm><primary>local subnet</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-If you want Samba to force an election on startup, set the <smbconfoption name="preferred master"/> global
-option in &smb.conf; to <constant>yes</constant>. Samba will then have a slight advantage over other
-potential master browsers that are not preferred master browsers. Use this parameter with care, because if
-you have two hosts (whether they are Windows 9x/Me or NT/200x/XP or Samba) on the same local subnet both set
-with <smbconfoption name="preferred master"/> to <constant>yes</constant>, then periodically and continually
-they will force an election in order to become the LMB.
-</para>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>LAN</primary></indexterm>
-<indexterm><primary>WAN</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>broadcast isolated subnet</primary></indexterm>
-If you want Samba to be a <emphasis>DMB</emphasis>, then it is recommended that you also set <smbconfoption
-name="preferred master"/> to <constant>yes</constant>, because Samba will not become a DMB for the whole of
-your LAN or WAN if it is not also a LMB on its own broadcast isolated subnet.
-</para>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>automatic redundancy</primary></indexterm>
-<indexterm><primary>UDP</primary></indexterm>
-<indexterm><primary>network bandwidth</primary></indexterm>
-<indexterm><primary>browser elections</primary></indexterm>
-It is possible to configure two Samba servers to attempt to become the DMB for a domain. The first server that
-comes up will be the DMB. All other Samba servers will attempt to become the DMB every 5 minutes. They will
-find that another Samba server is already the DMB and will fail. This provides automatic redundancy should the
-current DMB fail. The network bandwidth overhead of browser elections is relatively small, requiring
-approximately four UDP packets per machine per election. The maximum size of a UDP packet is 576 bytes.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Making Samba the Domain Master</title>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>collating</primary></indexterm>
-<indexterm><primary>browse lists</primary></indexterm>
-<indexterm><primary>browsing</primary></indexterm>
-The domain master browser is responsible for collating the browse lists of multiple subnets so browsing can
-occur between subnets. You can make Samba act as the domain master browser by setting <smbconfoption name="domain
-master">yes</smbconfoption> in &smb.conf;. By default it will not be a domain master browser.
-</para>
-
-<para>
-<indexterm><primary>workgroup</primary></indexterm>
-<indexterm><primary>network browsing problems</primary></indexterm>
-Do not set Samba to be the domain master for a workgroup that has the same name as an NT/200x domain. If
-Samba is configured to be the domain master for a workgroup that is present on the same network as a Windows
-NT/200x domain that has the same name, network browsing problems will certainly be experienced.
-</para>
-
-<para>
-When Samba is the domain master and the master browser, it will listen for master announcements (made roughly
-every 12 minutes) from LMBs on other subnets and then contact them to synchronize browse lists.
-</para>
-
-<para>
-<indexterm><primary>win election</primary></indexterm>
-<indexterm><primary>force election</primary></indexterm>
-If you want Samba to be the domain master, you should also set the <smbconfoption name="os level"/> high
-enough to make sure it wins elections, and set <smbconfoption name="preferred master"/> to
-<constant>yes</constant>, to get Samba to force an election on startup.
-</para>
-
-<para>
-<indexterm><primary>WINS server</primary></indexterm>
-<indexterm><primary>resolve NetBIOS names</primary></indexterm>
-All servers (including Samba) and clients should be using a WINS server to resolve NetBIOS names. If your
-clients are only using broadcasting to resolve NetBIOS names, then two things will occur:
-</para>
-
-<orderedlist>
-<listitem>
- <para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
- LMBs will be unable to find a DMB because they will be looking only on the local subnet.
- </para>
-</listitem>
-
-<listitem>
- <para>
-<indexterm><primary>domain-wide browse list</primary></indexterm>
- If a client happens to get hold of a domain-wide browse list and a user attempts to access a
- host in that list, it will be unable to resolve the NetBIOS name of that host.
- </para>
-</listitem>
-</orderedlist>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-If, however, both Samba and your clients are using a WINS server, then:
-</para>
-
-<orderedlist>
-<listitem>
- <para>
- LMBs will contact the WINS server and, as long as Samba has registered that it is a DMB with the WINS
- server, the LMB will receive Samba's IP address as its DMB.
- </para>
-</listitem>
-
-<listitem>
- <para>
- When a client receives a domain-wide browse list and a user attempts to access a host in that list, it will
- contact the WINS server to resolve the NetBIOS name of that host. As long as that host has registered its
- NetBIOS name with the same WINS server, the user will be able to see that host..
- </para>
-</listitem>
-</orderedlist>
-
-</sect2>
-
-<sect2>
-<title>Note about Broadcast Addresses</title>
-
-<para>
-<indexterm><primary>zero-based broadcast</primary></indexterm>
-If your network uses a zero-based broadcast address (for example, if it ends in a 0), then you will strike
-problems. Windows for Workgroups does not seem to support a zeros broadcast, and you will probably find that
-browsing and name lookups will not work.
-</para>
-</sect2>
-
-<sect2>
-<title>Multiple Interfaces</title>
-
-<para>
-<indexterm><primary>multiple network interfaces</primary></indexterm>
-Samba supports machines with multiple network interfaces. If you have multiple interfaces, you will
-need to use the <smbconfoption name="interfaces"/> option in &smb.conf; to configure them. For example, the
-machine you are working with has 4 network interfaces; <literal>eth0</literal>, <literal>eth1</literal>,
-<literal>eth2</literal>, <literal>eth3</literal> and only interfaces <literal>eth1</literal> and
-<literal>eth4</literal> should be used by Samba. In this case, the following &smb.conf; file entries would
-permit that intent:
-<smbconfblock>
-<smbconfoption name="interfaces">eth1, eth4</smbconfoption>
-<smbconfoption name="bind interfaces only">Yes</smbconfoption>
-</smbconfblock>
-<indexterm><primary>port 135</primary></indexterm>
-<indexterm><primary>port 137</primary></indexterm>
-<indexterm><primary>port 138</primary></indexterm>
-<indexterm><primary>port 139</primary></indexterm>
-<indexterm><primary>port 445</primary></indexterm>
-<indexterm><primary>UDP</primary></indexterm>
-<indexterm><primary>TCP</primary></indexterm>
-The <smbconfoption name="bind interfaces only">Yes</smbconfoption> is necessary to exclude TCP/IP session
-services (ports 135, 139, and 445) over the interfaces that are not specified. Please be aware that
-<command>nmbd</command> will listen for incoming UDP port 137 packets on the unlisted interfaces, but it will
-not answer them. It will, however, send its broadcast packets over the unlisted interfaces. Total isolation of
-ethernet interface requires the use of a firewall to block ports 137 and 138 (UDP), and ports 135, 139, and
-445 (TCP) on all network interfaces that must not be able to access the Samba server.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Use of the Remote Announce Parameter</title>
-<para>
-The <smbconfoption name="remote announce"/> parameter of &smb.conf; can be used to forcibly ensure that all
-the NetBIOS names on a network get announced to a remote network. The syntax of the <smbconfoption
-name="remote announce"/> parameter is:
-<smbconfblock>
-<smbconfoption name="remote announce">192.168.12.23 [172.16.21.255] ...</smbconfoption>
-</smbconfblock>
-<emphasis>or</emphasis>
-<smbconfblock>
-<smbconfoption name="remote announce">192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...</smbconfoption>
-</smbconfblock>
-
-where:
-<variablelist>
- <varlistentry><term><replaceable>192.168.12.23</replaceable> and <replaceable>172.16.21.255</replaceable></term>
- <listitem><para>
-<indexterm><primary>LMB</primary><see>Local Master Browser</see></indexterm>
-<indexterm><primary>Local Master Browser</primary></indexterm>
- is either the LMB IP address or the broadcast address of the remote network.
- That is, the LMB is at 192.168.1.23, or the address could be given as 172.16.21.255 where the netmask
- is assumed to be 24 bits (255.255.255.0). When the remote announcement is made to the broadcast
- address of the remote network, every host will receive our announcements. This is noisy and therefore
- undesirable but may be necessary if we do not know the IP address of the remote LMB.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term><replaceable>WORKGROUP</replaceable></term>
- <listitem><para>is optional and can be either our own workgroup or that of the remote network. If you use the
- workgroup name of the remote network, our NetBIOS machine names will end up looking like
- they belong to that workgroup. This may cause name resolution problems and should be avoided.
- </para></listitem>
- </varlistentry>
-</variablelist>
-</para>
-
-</sect2>
-
-<sect2>
-<title>Use of the Remote Browse Sync Parameter</title>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>synchronize</primary></indexterm>
-The <smbconfoption name="remote browse sync"/> parameter of &smb.conf; is used to announce to another LMB that
-it must synchronize its NetBIOS name list with our Samba LMB. This works only if the Samba server that has
-this option is simultaneously the LMB on its network segment.
-</para>
-
-<para>
-The syntax of the <smbconfoption name="remote browse sync"/> parameter is:
-
-<smbconfblock>
-<smbconfoption name="remote browse sync"><replaceable>192.168.10.40</replaceable></smbconfoption>
-</smbconfblock>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>remote segment</primary></indexterm>
-where <replaceable>192.168.10.40</replaceable> is either the IP address of the
-remote LMB or the network broadcast address of the remote segment.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>WINS: The Windows Internetworking Name Server</title>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>name_type</primary></indexterm>
-<indexterm><primary>LanManager-compatible</primary></indexterm>
-Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly
-recommended. Every NetBIOS machine registers its name together with a
-name_type value for each of several types of service it has available.
-It registers its name directly as a unique (the type 0x03) name.
-It also registers its name if it is running the LanManager-compatible
-server service (used to make shares and printers available to other users)
-by registering the server (the type 0x20) name.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS name length</primary></indexterm>
-<indexterm><primary>name_type</primary></indexterm>
-All NetBIOS names are up to 15 characters in length. The name_type variable
-is added to the end of the name, thus creating a 16 character name. Any
-name that is shorter than 15 characters is padded with spaces to the 15th
-character. Thus, all NetBIOS names are 16 characters long (including the
-name_type information).
-</para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>registered</primary></indexterm>
-<indexterm><primary>NetLogon service</primary></indexterm>
-<indexterm><primary>lmhosts</primary></indexterm>
-WINS can store these 16-character names as they get registered. A client
-that wants to log onto the network can ask the WINS server for a list
-of all names that have registered the NetLogon service name_type. This saves
-broadcast traffic and greatly expedites logon processing. Since broadcast
-name resolution cannot be used across network segments, this type of
-information can only be provided via WINS or via a statically configured
-<filename>lmhosts</filename> file that must reside on all clients in the
-absence of WINS.
-</para>
-
-<para>
-<indexterm><primary>synchronization</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>browse list</primary></indexterm>
-WINS also forces browse list synchronization by all LMBs. LMBs must synchronize their browse list with the
-DMB, and WINS helps the LMB to identify its DMB. By definition this will work only within a single workgroup.
-Note that the DMB has nothing to do with what is referred to as an MS Windows NT domain. The latter is a
-reference to a security environment, while the DMB refers to the master controller for browse list information
-only.
-</para>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>TCP/IP protocol stack</primary></indexterm>
-<indexterm><primary>WINS servers</primary></indexterm>
-<indexterm><primary>name-to-address</primary></indexterm>
-WINS will work correctly only if every client TCP/IP protocol stack
-is configured to use the WINS servers. Any client that is not
-configured to use the WINS server will continue to use only broadcast-based
-name registration, so WINS may never get to know about it. In any case,
-machines that have not registered with a WINS server will fail name-to-address
-lookup attempts by other clients and will therefore cause workstation access
-errors.
-</para>
-
-<para>
-To configure Samba as a WINS server, just add
-<smbconfoption name="wins support">yes</smbconfoption> to the &smb.conf;
-file [global] section.
-</para>
-
-<para>
-To configure Samba to register with a WINS server, just add <smbconfoption name="wins
-server">10.0.0.18</smbconfoption> to your &smb.conf; file <smbconfsection name="[global]"/> section.
-</para>
-
-<important><para>
-Never use <smbconfoption name="wins support">yes</smbconfoption> together with <smbconfoption name="wins
-server">10.0.0.18</smbconfoption> particularly not using its own IP address. Specifying both will cause &nmbd;
-to refuse to start!
-</para></important>
-
-<sect2>
-<title>WINS Server Configuration</title>
-
-<para>
-<indexterm><primary>WINS</primary></indexterm>
-Either a Samba server or a Windows NT server machine may be set up
-as a WINS server. To configure a Samba server to be a WINS server, you must
-add to the &smb.conf; file on the selected Server the following line to
-the <smbconfsection name="[global]"/> section:
-</para>
-
-<para>
-<smbconfblock>
-<smbconfoption name="wins support">yes</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-<indexterm><primary>Samba 1.9.17</primary></indexterm>
-Versions of Samba prior to 1.9.17 had this parameter default to
-yes. If you have any older versions of Samba on your network, it is
-strongly suggested you upgrade to a recent version, or at the very
-least set the parameter to <quote>no</quote> on all these machines.
-</para>
-
-<para>
-Machines configured with <smbconfoption name="wins support">yes</smbconfoption> will keep a list of
-all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
-</para>
-
-<para>
-<indexterm><primary>only one WINS server</primary></indexterm>
-It is strongly recommended to set up only one WINS server. Do not set the <smbconfoption name="wins
-support">yes</smbconfoption> option on more than one Samba server on a network.
-</para>
-
-<para>
-<indexterm><primary>replication</primary><secondary>WINS</secondary></indexterm>
-<indexterm><primary>Windows NT/200x</primary></indexterm>
-<indexterm><primary>WINS service</primary></indexterm>
-<indexterm><primary>replication protocols</primary></indexterm>
-<indexterm><primary>WINS server</primary></indexterm>
-To configure Windows NT/200x Server as a WINS server, install and configure the WINS service. See the Windows
-NT/200x documentation for details. Windows NT/200x WINS servers can replicate to each other, allowing more
-than one to be set up in a complex subnet environment. Because Microsoft refuses to document the replication
-protocols, Samba cannot currently participate in these replications. It is possible that a Samba-to-Samba WINS
-replication protocol may be defined in the future, in which case more than one Samba machine could be set up
-as a WINS server. Currently only one Samba server should have the <smbconfoption name="wins
-support">yes</smbconfoption> parameter set.
-</para>
-
-<para>
-<indexterm><primary>WINS server</primary></indexterm>
-<indexterm><primary>Primary WINS Server</primary></indexterm>
-After the WINS server has been configured, you must ensure that all machines participating on the network are
-configured with the address of this WINS server. If your WINS server is a Samba machine, fill in the Samba
-machine IP address in the <guilabel>Primary WINS Server</guilabel> field of the <guilabel>Control
-Panel->Network->Protocols->TCP->WINS Server</guilabel> dialogs in Windows 9x/Me or Windows NT/200x. To tell a
-Samba server the IP address of the WINS server, add the following line to the <smbconfsection
-name="[global]"/> section of all &smb.conf; files:
-<smbconfblock>
-<smbconfoption name="wins server"><name or IP address></smbconfoption>
-</smbconfblock>
-where <name or IP address> is either the DNS name of the WINS server
-machine or its IP address.
-</para>
-
-<para>
-This line must not be set in the &smb.conf; file of the Samba
-server acting as the WINS server itself. If you set both the
-<smbconfoption name="wins support">yes</smbconfoption> option and the
-<smbconfoption name="wins server"><name></smbconfoption> option then
-<command>nmbd</command> will fail to start.
-</para>
-
-<para>
-<indexterm><primary>cross-subnet browsing</primary></indexterm>
-<indexterm><primary>Windows 9x/Me</primary></indexterm>
-<indexterm><primary>Windows NT/200x</primary></indexterm>
-<indexterm><primary>not part of domain</primary></indexterm>
-There are two possible scenarios for setting up cross-subnet browsing.
-The first details setting up cross-subnet browsing on a network containing
-Windows 9x/Me, Samba, and Windows NT/200x machines that are not configured as
-part of a Windows NT domain. The second details setting up cross-subnet
-browsing on networks that contain NT domains.
-</para>
-
-</sect2>
-
-<sect2>
-<title>WINS Replication</title>
-
-<para>
-<indexterm><primary>replication</primary><secondary>WINS</secondary></indexterm>
-<indexterm><primary>WINS replication</primary></indexterm>
-Samba-3 does not support native WINS replication. There was an approach to implement it, called
-<filename>wrepld</filename>, but it was never ready for action and the development is now discontinued.
-</para>
-<para>
-Meanwhile, there is a project named <filename>samba4WINS</filename>, which makes it possible to
-run the Samba-4 WINS server parallel to Samba-3 since version 3.0.21. More information about
-<filename>samba4WINS</filename> are available at http://ftp.sernet.de/pub/samba4WINS.
-
-</para>
-
-</sect2>
-<sect2>
-<title>Static WINS Entries</title>
-
-<para>
-<indexterm><primary>static WINS entries</primary></indexterm>
-<indexterm><primary>wins.dat</primary></indexterm>
-<indexterm><primary>/usr/local/samba/var/locks</primary></indexterm>
-<indexterm><primary>/var/run/samba</primary></indexterm>
-Adding static entries to your Samba WINS server is actually fairly easy. All you have to do is add a line to
-<filename>wins.dat</filename>, typically located in <filename
-class="directory">/usr/local/samba/var/locks</filename> or <filename>/var/run/samba</filename>.
-</para>
-
-<para>
-Entries in <filename>wins.dat</filename> take the form of:
-<programlisting>
-"NAME#TYPE" TTL ADDRESS+ FLAGS
-</programlisting>
-<indexterm><primary>TTL</primary></indexterm>
-<indexterm><primary>time-to-live</primary><see>TTL</see></indexterm>
-where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the time-to-live as an absolute time in
-seconds, ADDRESS+ is one or more addresses corresponding to the registration, and FLAGS are the NetBIOS flags
-for the registration.
-</para>
-
-<note><para>
-A change that has been made to the <filename>wins.dat</filename> will not take effect until &nmbd; has been
-restarted. It should be noted that since the <filename>wins.dat</filename> file changes dynamically, &nmbd;
-should be stopped before editting this file. Do not forget to restart &nmbd; when this file has been editted.
-</para></note>
-
-<para>
-A typical dynamic entry looks like this:
-<programlisting>
-"MADMAN#03" 1155298378 192.168.1.2 66R
-</programlisting>
-To make a NetBIOS name static (permanent), simply set the TTL to 0, like this:
-<programlisting>
-"MADMAN#03" 0 192.168.1.2 66R
-</programlisting>
-</para>
-
-<para>
-<indexterm><primary>NetBIOS flags</primary></indexterm>
-<indexterm><primary>Broadcast node</primary></indexterm>
-<indexterm><primary>Peer node</primary></indexterm>
-<indexterm><primary>Meta node</primary></indexterm>
-<indexterm><primary>Hybrid node</primary></indexterm>
-<indexterm><primary>Permanent name</primary></indexterm>
-<indexterm><primary>nameserv.h</primary></indexterm>
-The NetBIOS flags may be interpreted as additive hexadecimal values: 00 - Broadcast node registration, 20 -
-Peer node registration, 40 - Meta node registration, 60 - Hybrid node registration, 02 - Permanent name, 04 -
-Active name, 80 - Group name. The 'R' indicates this is a registration record. Thus 66R means: Hybrid node
-active and permanent NetBIOS name. These values may be found in the <filename>nameserv.h</filename> header
-file from the Samba source code repository. These are the values for the NB flags.
-</para>
-
-<para>
-<indexterm><primary>WINS replication</primary></indexterm>
-Though this method works with early Samba-3 versions, there is a possibility that it may change in future
-versions if WINS replication is added.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Helpful Hints</title>
-
-<para>
-The following hints should be carefully considered because they are stumbling points
-for many new network administrators.
-</para>
-
-<sect2>
-<title>Windows Networking Protocols</title>
-
-<para>
-<indexterm><primary>browsing problems</primary></indexterm>
-<indexterm><primary>more than one protocol</primary></indexterm>
-A common cause of browsing problems results from the installation of more than one protocol on an MS Windows
-machine.
-</para>
-
-<warning><para>
-Do not use more than one protocol on MS Windows clients.
-</para></warning>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
-every 15 minutes. A set of election criteria is used to determine the order
-of precedence for winning this election process. A machine running Samba or
-Windows NT will be biased, so the most suitable machine will predictably
-win and thus retain its role.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS network interface</primary></indexterm>
-<indexterm><primary>TCP/IP</primary></indexterm>
-<indexterm><primary>IPX</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>Windows 9x/Me</primary></indexterm>
-<indexterm><primary>TCP/IP-only</primary></indexterm>
-The election process is <emphasis>fought out, so to speak</emphasis> over every NetBIOS network interface. In
-the case of a Windows 9x/Me machine that has both TCP/IP and IPX installed and has NetBIOS enabled over both
-protocols, the election will be decided over both protocols. As often happens, if the Windows 9x/Me machine is
-the only one with both protocols, then the LMB may be won on the NetBIOS interface over the IPX protocol.
-Samba will then lose the LMB role because Windows 9x/Me will insist it knows who the LMB is. Samba will then
-cease to function as an LMB, and browse list operation on all TCP/IP-only machines will therefore fail.
-</para>
-
-<para>
-<indexterm><primary>Windows 9x/Me</primary></indexterm>
-<indexterm><primary>extended protocol</primary></indexterm>
-Windows 95, 98, 98se, and Me are referred to generically as Windows 9x/Me. The Windows NT4, 200x, and XP use
-common protocols. These are roughly referred to as the Windows NT family, but it should be recognized that
-2000 and XP/2003 introduce new protocol extensions that cause them to behave differently from MS Windows NT4.
-Generally, where a server does not support the newer or extended protocol, these will fall back to the NT4
-protocols.
-</para>
-
-<para>
-The safest rule of all to follow is: Use only one protocol!
-</para>
-
-</sect2>
-
-<sect2>
-<title>Name Resolution Order</title>
-
-<para>
-<indexterm><primary>NetBIOS names</primary></indexterm>
-<indexterm><primary>name_type</primary></indexterm>
-Resolution of NetBIOS names to IP addresses can take place using a number
-of methods. The only ones that can provide NetBIOS name_type information
-are:
-</para>
-
-<itemizedlist>
- <listitem><para>WINS &smbmdash; the best tool.</para></listitem>
- <listitem><para>LMHOSTS &smbmdash; static and hard to maintain.</para></listitem>
- <listitem><para>Broadcast &smbmdash; uses UDP and cannot resolve names across remote segments.</para></listitem>
-</itemizedlist>
-
-<para>
-Alternative means of name resolution include:
-</para>
-<itemizedlist>
-<listitem><para>Static <filename>/etc/hosts</filename> &smbmdash; hard to maintain and lacks name_type info.</para></listitem>
-<listitem><para>DNS &smbmdash; is a good choice but lacks essential NetBIOS name_type information.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>restrict DNS</primary></indexterm>
-<indexterm><primary>name resolve order</primary></indexterm>
-Many sites want to restrict DNS lookups and avoid broadcast name
-resolution traffic. The <parameter>name resolve order</parameter> parameter is of great help here.
-The syntax of the <parameter>name resolve order</parameter> parameter is:
-<smbconfblock>
-<smbconfoption name="name resolve order">wins lmhosts bcast host</smbconfoption>
-</smbconfblock>
-<emphasis>or</emphasis>
-<smbconfblock>
-<smbconfoption name="name resolve order">wins lmhosts (eliminates bcast and host)</smbconfoption>
-</smbconfblock>
-The default is:
-<smbconfblock>
-<smbconfoption name="name resolve order">host lmhost wins bcast</smbconfoption>,
-</smbconfblock>
-<indexterm><primary>gethostbyname() function call</primary></indexterm>
-where <quote>host</quote> refers to the native methods used by the UNIX system to implement the
-gethostbyname() function call. This is normally controlled by <filename>/etc/host.conf</filename>,
-<filename>/etc/nsswitch.conf</filename> and <filename>/etc/resolv.conf</filename>.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Technical Overview of Browsing</title>
-
-<para>
-<indexterm><primary>SMB</primary></indexterm>
-SMB networking provides a mechanism by which clients can access a list
-of machines in a network called <smbconfoption name="browse list"/>. This list
-contains machines that are ready to offer file and/or print services
-to other machines within the network. It therefore does not include
-machines that aren't currently able to do server tasks. The browse
-list is heavily used by all SMB clients. Configuration of SMB
-browsing has been problematic for some Samba users, hence this
-document.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
-<indexterm><primary>DNS/LDAP/ADS</primary></indexterm>
-<indexterm><primary>name resolution</primary></indexterm>
-MS Windows 2000 and later versions, as with Samba and later versions, can be
-configured to not use NetBIOS over TCP/IP. When configured this way,
-it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
-configured and operative. Browsing will not work if name resolution
-from SMB machine names to IP addresses does not function correctly.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-Where NetBIOS over TCP/IP is enabled, use of a WINS server is highly
-recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
-WINS allows remote segment clients to obtain NetBIOS name_type information
-that cannot be provided by any other means of name resolution.
-</para>
-
-<sect2>
-<title>Browsing Support in Samba</title>
-
-<para>
-<indexterm><primary>browsing</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>domain logons</primary></indexterm>
-<indexterm><primary>scripts</primary></indexterm>
-Samba facilitates browsing. The browsing is supported by &nmbd;
-and is also controlled by options in the &smb.conf; file.
-Samba can act as an LMB for a workgroup, and the ability
-to support domain logons and scripts is now available.
-</para>
-
-<para>
-<indexterm><primary>DMB for a workgroup</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-Samba can also act as a DMB for a workgroup. This
-means that it will collate lists from LMBs into a
-wide-area network server list. In order for browse clients to
-resolve the names they may find in this list, it is recommended that
-both Samba and your clients use a WINS server.
-</para>
-
-<para>
-<indexterm><primary>domain master</primary></indexterm>
-Do not set Samba to be the domain master for a workgroup that has the same
-name as an NT Domain. On each wide-area network, you must only ever have one
-DMB per workgroup, regardless of whether it is NT, Samba,
-or any other type of domain master that is providing this service.
-</para>
-
-<note><para>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>WINS server</primary></indexterm>
-<command>nmbd</command> can be configured as a WINS server, but it is not
-necessary to specifically use Samba as your WINS server. MS Windows
-NT4, Server or Advanced Server 200x can be configured as
-your WINS server. In a mixed NT/200x server and Samba environment on
-a WAN, it is recommended that you use the Microsoft
-WINS server capabilities. In a Samba-only environment, it is
-recommended that you use one and only one Samba server as the WINS server.
-</para></note>
-
-<para>
-<indexterm><primary>nmbd</primary></indexterm>
-To get browsing to work, you need to run <command>nmbd</command> as usual, but must
-use the <smbconfoption name="workgroup"/> option in &smb.conf;
-to control what workgroup Samba becomes a part of.
-</para>
-
-<para>
-<indexterm><primary>browsing another subnet</primary></indexterm>
-Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is
-recommended that this option is used only for <quote>unusual</quote> purposes: announcements over the
-Internet, for example. See <smbconfoption name="remote announce"/> in the &smb.conf; man page.
-</para>
-</sect2>
-
-<sect2>
-<title>Problem Resolution</title>
-
-<para>
-<indexterm><primary>log.nmbd</primary></indexterm>
-<indexterm><primary>browse.dat</primary></indexterm>
-If something does not work, the <filename>log.nmbd</filename> file will help
-to track down the problem. Try a <smbconfoption name="log level"></smbconfoption> of 2 or 3 for finding
-problems. Also note that the current browse list usually gets stored
-in text form in a file called <filename>browse.dat</filename>.
-</para>
-
-<para>
-<indexterm><primary>\\SERVER</primary></indexterm>
-<indexterm><primary>filemanager</primary></indexterm>
-If it does not work, you should still be able to
-type the server name as <filename>\\SERVER</filename> in <command>filemanager</command>, then
-press enter, and <command>filemanager</command> should display the list of available shares.
-</para>
-
-<para>
-<indexterm><primary>IPC$</primary></indexterm>
-<indexterm><primary>guest account</primary></indexterm>
-Some people find browsing fails because they do not have the global
-<smbconfoption name="guest account"/> set to a valid account. Remember that the
-IPC$ connection that lists the shares is done as guest and so you must have a valid guest account.
-</para>
-
-<note><para>
-<indexterm><primary>IPC$</primary></indexterm>
-<indexterm><primary>Windows Explorer</primary></indexterm>
-<indexterm><primary>browse resources</primary></indexterm>
-<indexterm><primary>Network Neighborhood</primary></indexterm>
-<indexterm><primary>My Network Places</primary></indexterm>
-The <literal>IPC$</literal> share is used by all SMB/CIFS clients to obtain the list of resources that is
-available on the server. This is the source of the list of shares and printers when browsing an SMB/CIFS
-server (also Windows machines) using the Windows Explorer to browse resources through the Windows Network
-Neighborhood (also called My Network Places) through to a Windows server. At this point, the client has opened
-a connection to the <literal>\\server\IPC4</literal> resource. Clicking on a share will then open up a
-connection to the <literal>\\server\share</literal>.
-</para></note>
-
-<para>
-<indexterm><primary>guest account</primary></indexterm>
-<indexterm><primary>anonymous access</primary></indexterm>
-<indexterm><primary>IPC$</primary></indexterm>
-<indexterm><primary>browse server resources</primary></indexterm>
-MS Windows 2000 and later (as with Samba) can be configured to disallow
-anonymous (i.e., guest account) access to the IPC$ share. In that case, the
-MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
-name of the currently logged-in user to query the IPC$ share. MS Windows
-9x/Me clients are not able to do this and thus will not be able to browse
-server resources.
-</para>
-
-<para>
-<indexterm><primary>broadcast address</primary></indexterm>
-The other big problem people have is that their broadcast address,
-netmask, or IP address is wrong (specified with the <smbconfoption name="interfaces"></smbconfoption> option
-in &smb.conf;)
-</para>
-</sect2>
-
-<sect2>
-<title>Cross-Subnet Browsing</title>
-
-<para>
-<indexterm><primary>replication</primary><secondary>browse lists</secondary></indexterm>
-<indexterm><primary>browse across subnet</primary></indexterm>
-Since the release of Samba 1.9.17 (alpha1), Samba has supported the replication of browse lists across subnet
-boundaries. This section describes how to set this feature up in different settings.
-</para>
-
-<para>
-<indexterm><primary>browse lists</primary></indexterm>
-<indexterm><primary>broadcast traffic</primary></indexterm>
-<indexterm><primary>UDP</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>remote announce</primary></indexterm>
-<indexterm><primary>remote browse sync</primary></indexterm>
-To see browse lists that span TCP/IP subnets (i.e., networks separated by routers that do not pass broadcast
-traffic), you must set up at least one WINS server. The WINS server acts as a DNS for NetBIOS names. This will
-allow NetBIOS name-to-IP address translation to be completed by a direct query of the WINS server. This is
-done via a directed UDP packet on port 137 to the WINS server machine. The WINS server avoids the necessity of
-default NetBIOS name-to-IP address translation, which is done using UDP broadcasts from the querying machine.
-This means that machines on one subnet will not be able to resolve the names of machines on another subnet
-without using a WINS server. The Samba hacks, <parameter>remote browse sync</parameter>, and <parameter>remote
-announce</parameter> are designed to get around the natural limitations that prevent UDP broadcast
-propagation. The hacks are not a universal solution and they should not be used in place of WINS, they are
-considered last resort methods.
-</para>
-
-<para>
-<indexterm><primary>DHCP</primary></indexterm>
-<indexterm><primary>browsing across subnets</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>Network settings</primary></indexterm>
-Remember, for browsing across subnets to work correctly, all machines, be they Windows 95, Windows NT, or
-Samba servers, must have the IP address of a WINS server given to them by a DHCP server or by manual
-configuration: for Windows 9x/Me and Windows NT/200x/XP, this is in the TCP/IP Properties, under Network
-settings; for Samba, this is in the &smb.conf; file.
-</para>
-
-<para>
-<indexterm><primary>NetBIOS over TCP/IP</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-It is possible to operate Samba without NetBIOS over TCP/IP. If you do this, be warned that if used outside
-of MS ADS, this will forgo network browsing support. ADS permits network browsing support through DNS,
-providing appropriate DNS records are inserted for all Samba servers.
-</para>
-
-<sect3>
-<title>Behavior of Cross-Subnet Browsing</title>
-
-<para>
-<indexterm><primary>cross-subnet browsing</primary></indexterm>
-<indexterm><primary>complicated</primary></indexterm>
-Cross-subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several
-years to get the code that correctly achieves this, and Samba lags behind in some areas. Samba is capable of
-cross-subnet browsing when configured correctly.
-</para>
-
-<para>
-Consider a network set up as in <link linkend="browsing1">Cross-Subnet Browsing Example</link>.
-</para>
-
-<figure id="browsing1">
- <title>Cross-Subnet Browsing Example.</title>
- <imagefile scale="40">browsing1</imagefile>
-</figure>
-
-<para>
-<indexterm><primary>broadcasts</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-This consists of three subnets (1, 2, 3) connected by two routers (R1, R2), which do not pass broadcasts.
-Subnet 1 has five machines on it, subnet 2 has four machines, and subnet 3 has four machines. Assume for the
-moment that all machines are configured to be in the same workgroup (for simplicity's sake). Machine N1_C on
-subnet 1 is configured as the DMB (i.e., it will collate the browse lists for the workgroup). Machine N2_D is
-configured as a WINS server, and all the other machines are configured to register their NetBIOS names with
-it.
-</para>
-
-<para>
-<indexterm><primary>master browsers</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-As these machines are booted up, elections for master browsers
-take place on each of the three subnets. Assume that machine
-N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on
-subnet 3. These machines are known as LMBs for
-their particular subnet. N1_C has an advantage in winning as the
-LMB on subnet 1 because it is set up as DMB.
-</para>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>browse list</primary></indexterm>
-On each of the three networks, machines that are configured to offer sharing services will broadcast that they
-are offering these services. The LMB on each subnet will receive these broadcasts and keep a record of the
-fact that the machine is offering a service. This list of records is the basis of the browse list. For this
-case, assume that all the machines are configured to offer services, so all machines will be on the browse
-list.
-</para>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>authoritative</primary></indexterm>
-<indexterm><primary>verifiable</primary></indexterm>
-<indexterm><primary>trusted</primary></indexterm>
-<indexterm><primary>non-authoritative</primary></indexterm>
-For each network, the LMB on that network is
-considered <emphasis>authoritative</emphasis> for all the names it receives via
-local broadcast. This is because a machine seen by the LMB
-via a local broadcast must be on the same network as the
-Local Master Browser and thus is a <emphasis>trusted</emphasis>
-and <emphasis>verifiable</emphasis> resource. Machines on other networks that
-the LMBs learn about when collating their
-browse lists have not been directly seen. These records are
-called <emphasis>non-authoritative.</emphasis>
-</para>
-
-<para>
-<indexterm><primary>network neighborhood</primary></indexterm>
-At this point the browse lists appear as shown in <link linkend="browsubnet">Browse Subnet Example 1</link>
-(these are the machines you would see in your network neighborhood if you looked in it on a particular network
-right now).
-</para>
-
-<para>
-<table frame="all" id="browsubnet">
- <title>Browse Subnet Example 1</title>
- <tgroup align="left" cols="3">
- <thead>
- <row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
- </thead>
-
- <tbody>
- <row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E</entry></row>
- <row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D</entry></row>
- <row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D</entry></row>
- </tbody>
- </tgroup>
-</table>
-</para>
-
-<para>
-At this point all the subnets are separate, and no machine is seen across any of the subnets.
-</para>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>synchronize</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-Now examine subnet 2 in <link linkend="brsbex">Browse Subnet Example 2</link>. As soon as N2_B has become the
-LMB, it looks for a DMB with which to synchronize its browse list. It does this by querying the WINS server
-(N2_D) for the IP address associated with the NetBIOS name WORKGROUP<1B>. This name was registered by
-the DMB (N1_C) with the WINS server as soon as it was started.
-</para>
-
-<para>
-<indexterm><primary>MasterAnnouncement</primary></indexterm>
-<indexterm><primary>NetServerEnum2</primary></indexterm>
-<indexterm><primary>synchronization</primary></indexterm>
-<indexterm><primary>browse lists</primary></indexterm>
-Once N2_B knows the address of the DMB, it tells the DMB that it is the LMB
-for subnet 2 by sending the DMB a
-<emphasis>MasterAnnouncement</emphasis> packet to UDP port 138. It then
-synchronizes with the DMB by
-doing a <emphasis>NetServerEnum2</emphasis> call. This tells the DMB to
-send the sender all the server names it knows
-about. Once the DMB receives the <emphasis>MasterAnnouncement</emphasis> packet, it schedules a
-synchronization request to the sender of that packet. After both synchronizations are complete, the browse
-lists look like those in <link linkend="brsbex">Browse Subnet Example 2</link>
-</para>
-
-<table frame="all" id="brsbex">
- <title>Browse Subnet Example 2</title>
- <tgroup cols="3">
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <thead>
- <row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
- </thead>
-
- <tbody>
- <row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E,
-N2_A(*), N2_B(*), N2_C(*), N2_D(*)</entry></row>
- <row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*)</entry></row>
- <row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D</entry></row>
- </tbody>
- </tgroup>
-</table>
-
-<para>
-<indexterm><primary>non-authoritative</primary></indexterm>
-Servers with an (*) after them are non-authoritative names.
-</para>
-
-<para>
-<indexterm><primary>Network Neighborhood</primary></indexterm>
-At this point users looking in their Network Neighborhood on subnets 1 or 2 will see all the servers on both;
-users on subnet 3 will still see only the servers on their own subnet.
-</para>
-
-<para>
-<indexterm><primary>DMB</primary></indexterm>
-The same sequence of events that occurred for N2_B now occurs for the LMB on subnet 3 (N3_D). When it
-synchronizes browse lists with the DMB (N1_A) it gets both the server entries on subnet 1 and those on subnet
-2. After N3_D has synchronized with N1_C and vica versa, the browse lists will appear as shown in <link
-linkend="brsex2">Browse Subnet Example 3</link>
-</para>
-
-<table frame="all" id="brsex2">
- <title>Browse Subnet Example 3</title>
- <tgroup cols="3" align="left">
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
-
- <thead>
- <row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
- </thead>
-
- <tbody>
- <row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E,
-N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</entry></row>
- <row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*)</entry></row>
- <row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</entry></row>
- </tbody>
- </tgroup>
-</table>
-
-<para>
-Servers with an (*) after them are non-authoritative names.
-</para>
-
-<para>
-At this point, users looking in their Network Neighborhood on
-subnets 1 or 3 will see all the servers on all subnets, while users on
-subnet 2 will still see only the servers on subnets 1 and 2, but not 3.
-</para>
-
-<para>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>browse lists</primary></indexterm>
-Finally, the LMB for subnet 2 (N2_B) will sync again
-with the DMB (N1_C) and will receive the missing
-server entries. Finally, as when a steady state (if no machines
-are removed or shut off) has been achieved, the browse lists will appear
-as shown in <link linkend="brsex3">Browse Subnet Example 4</link>.
-</para>
-
-<table frame="all" id="brsex3">
- <title>Browse Subnet Example 4</title>
- <tgroup cols="3" align="left">
- <colspec align="left"/>
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
-
- <thead>
- <row><entry>Subnet</entry><entry>Browse Master</entry><entry>List</entry></row>
- </thead>
-
- <tbody>
- <row><entry>Subnet1</entry><entry>N1_C</entry><entry>N1_A, N1_B, N1_C, N1_D, N1_E,
-N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*),
-N3_C(*), N3_D(*)</entry></row>
- <row><entry>Subnet2</entry><entry>N2_B</entry><entry>N2_A, N2_B, N2_C, N2_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*),
-N3_C(*), N3_D(*)</entry></row>
- <row><entry>Subnet3</entry><entry>N3_D</entry><entry>N3_A, N3_B, N3_C, N3_D, N1_A(*),
-N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*),
-N2_C(*), N2_D(*)</entry></row>
- </tbody>
- </tgroup>
-</table>
-
-<para>
-Servers with an (*) after them are non-authoritative names.
-</para>
-
-<para>
-Synchronizations between the DMB and LMBs
-will continue to occur, but this should remain a
-steady-state operation.
-</para>
-
-<para>
-If either router R1 or R2 fails, the following will occur:
-</para>
-
-<orderedlist>
-<listitem>
- <para>
-<indexterm><primary>Network Neighborhood</primary></indexterm>
- Names of computers on each side of the inaccessible network fragments
- will be maintained for as long as 36 minutes in the Network Neighborhood
- lists.
- </para>
-</listitem>
-
-<listitem>
- <para>
- Attempts to connect to these inaccessible computers will fail, but the
- names will not be removed from the Network Neighborhood lists.
- </para>
-</listitem>
-
-<listitem>
- <para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>NetBIOS name resolution</primary></indexterm>
-<indexterm><primary>DNS server</primary></indexterm>
- If one of the fragments is cut off from the WINS server, it will only
- be able to access servers on its local subnet using subnet-isolated
- broadcast NetBIOS name resolution. The effect is similar to that of
- losing access to a DNS server.
- </para>
-</listitem>
-</orderedlist>
-</sect3>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-<indexterm><primary>browsing problems</primary></indexterm>
-<indexterm><primary>name resolution</primary></indexterm>
-Many questions are asked on the mailing lists regarding browsing. The majority of browsing
-problems originate from incorrect configuration of NetBIOS name resolution. Some are of
-particular note.
-</para>
-
-<sect2>
-<title>Flushing the Samba NetBIOS Name Cache</title>
-
-<para>
-How Can One Flush the Samba NetBIOS Name Cache without Restarting Samba?
-</para>
-
-<para>
-<indexterm><primary>flush name cache</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>NetBIOS name cache</primary></indexterm>
-<indexterm><primary>rogue machine</primary></indexterm>
-Samba's <command>nmbd</command> process controls all browse list handling. Under normal circumstances it is
-safe to restart <command>nmbd</command>. This will effectively flush the Samba NetBIOS name cache and cause it
-to be rebuilt. This does not make certain that a rogue machine name will not reappear
-in the browse list. When <command>nmbd</command> is taken out of service, another machine on the network will
-become the browse master. This new list may still have the rogue entry in it. If you really
-want to clear a rogue machine from the list, every machine on the network must be
-shut down and restarted after all machines are down. Failing a complete restart, the only
-other thing you can do is wait until the entry times out and is then flushed from the list.
-This may take a long time on some networks (perhaps months).
-</para>
-
-</sect2>
-
-<sect2>
- <title>Server Resources Cannot Be Listed</title>
-
-<para><quote>My Client Reports "<quote>This server is not configured to list shared resources."</quote></quote></para>
-
-
-<para>
-Your guest account is probably invalid for some reason. Samba uses the
-guest account for browsing in <command>smbd</command>. Check that your guest account is
-valid.
-</para>
-
-<para>Also see <smbconfoption name="guest account"/> in the &smb.conf; man page.</para>
-
-</sect2>
-
-<sect2>
- <title>I Get an "<errorname>Unable to browse the network</errorname>" Error</title>
-
- <para>This error can have multiple causes:
-<indexterm><primary>browsing problems</primary></indexterm>
- </para>
-
- <itemizedlist>
- <listitem><para>There is no LMB. Configure &nmbd;
- or any other machine to serve as LMB.</para></listitem>
- <listitem><para>You cannot log onto the machine that is the LMB.
- Can you log on to it as a guest user? </para></listitem>
- <listitem><para>There is no IP connectivity to the LMB.
- Can you reach it by broadcast?</para></listitem>
-</itemizedlist>
-</sect2>
-
-<sect2>
-<title>Browsing of Shares and Directories is Very Slow</title>
-
-<para><quote>
-<indexterm><primary>slow browsing</primary></indexterm>
-There are only two machines on a test network. One is a Samba server, the other a Windows XP machine.
-Authentication and logons work perfectly, but when I try to explore shares on the Samba server, the
-Windows XP client becomes unresponsive. Sometimes it does not respond for some minutes. Eventually,
-Windows Explorer will respond and displays files and directories without problem.
-</quote>
-</para>
-
-<para><quote>
-<indexterm><primary>cmd</primary></indexterm>
-But, the share is immediately available from a command shell (<command>cmd</command>, followed by
-exploration with DOS command. Is this a Samba problem, or is it a Windows problem? How can I solve this?
-</quote></para>
-
-<para>
-Here are a few possibilities:
-</para>
-
-<variablelist>
- <varlistentry>
- <term>Bad Networking Hardware</term>
- <listitem><para>
-<indexterm><primary>bad hardware</primary></indexterm>
-<indexterm><primary>WebClient</primary></indexterm>
-<indexterm><primary>defective hardware</primary></indexterm>
-<indexterm><primary>Bad networking hardware</primary></indexterm>
-<indexterm><primary>data corruption</primary></indexterm>
- Most common defective hardware problems center around low cost or defective hubs, routers,
- network interface controllers (NICs), and bad wiring. If one piece of hardware is defective,
- the whole network may suffer. Bad networking hardware can cause data corruption. Most bad
- networking hardware problems are accompanied by an increase in apparent network traffic,
- but not all.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>The Windows XP WebClient</term>
- <listitem><para>
-<indexterm><primary>network browsing problems</primary></indexterm>
- A number of sites have reported similar slow network browsing problems and found that when
- the WebClient service is turned off, the problem disappears. This is certainly something
- that should be explored because it is a simple solution &smbmdash; if it works.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Inconsistent WINS Configuration</term>
- <listitem><para>
-<indexterm><primary>WINS Configuration</primary></indexterm>
-<indexterm><primary>WINS server</primary></indexterm>
- This type of problem is common when one client is configured to use a WINS server (that is
- a TCP/IP configuration setting) and there is no WINS server on the network. Alternatively,
- this will happen if there is a WINS server and Samba is not configured to use it. The use of
- WINS is highly recommended if the network is using NetBIOS over TCP/IP protocols. If use
- of NetBIOS over TCP/IP is disabled on all clients, Samba should not be configured as a WINS
- server, nor should it be configured to use one.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Incorrect DNS Configuration</term>
- <listitem><para>
-<indexterm><primary>DNS Configuration</primary></indexterm>
-<indexterm><primary>NetBIOS over TCP/IP disabled</primary></indexterm>
- If use of NetBIOS over TCP/IP is disabled, Active Directory is in use and the DNS server
- has been incorrectly configured. For further information refer to
- <link linkend="adsdnstech">DNS and Active Directory</link>.
- </para></listitem>
- </varlistentry>
-</variablelist>
-
-</sect2>
-<sect2>
-<title>Invalid Cached Share References Affects Network Browsing</title>
-<para>
-<indexterm><primary>cached references</primary></indexterm>
-<indexterm><primary>stale network links</primary></indexterm>
-Cached references on your MS Windows client (workstation or server) to shares or servers that no longer exist
-can cause MS Windows Explorer to appear unresponsive as it tries to connect to these shares. After a delay
-(can take a long time) it times out and browsing will appear to be mostly normal again.
-</para>
-
-<para>
-To eliminate the problem the stale cached references should be removed. This does not happen automatically and
-requires manual intervention. This is a design feature of MS Windows and not anything that Samba can change.
-To remove the stale shortcuts found in <emphasis>My Network Places</emphasis> which refer to what are now
-invalid shares or servers it is necessary to edit the Windows Registry under
-<literal>HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\</literal>. Edit the entry
-<literal>MountPoints2</literal> (on Windows XP and later, or <literal>MountPoints</literal> on Windows 2000
-and earlier). Remove all keys named <literal>\\server\share</literal> (where 'server' and 'share' refer to a
-non-existent server or share).
-</para>
-
-<note><para>
-Removal of stale network links needs to be done on a per-user basis. Alternately, you can delete the
-shortcuts from the MS Windows Explorer in <literal>My Network Places</literal> just by right-clicking them and
-selecting <emphasis>Delete.</emphasis>
-</para></note>
-
-<para>
-<indexterm><primary>slow network browsing</primary></indexterm>
-Samba users have reported that these stale references negatively affect network browsing with Windows, Samba,
-and Novell servers. It is suspected to be a universal problem not directly related to the Samba
-server. Samba users may experience this more often due to Samba being somewhat viewed as an experimenter's
-toolkit. This results from the fact that a user might go through several reconfigurations and incarnations of
-their Samba server, by different names, with different shares, increasing the chances for having stale
-(invalid) cached share references. Windows clients do not expire these references thus necessitating manual
-removal.
-</para>
-
-<para>
-It is common for <emphasis>Open</emphasis> dialog boxes (for example; in Word and Excel) to respond very
-slowly, as they attempt to locate all of the cached references, even if they are not in the current directory
-being accessed.
-</para>
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="pam">
-<chapterinfo>
- &author.jht;
- <author>
- <firstname>Stephen</firstname><surname>Langasek</surname>
- <affiliation>
- <address><email>vorlon@netexpress.net</email></address>
- </affiliation>
- </author>
- <pubdate>May 31, 2003</pubdate>
-</chapterinfo>
-
-<title>PAM-Based Distributed Authentication</title>
-
-<para>
-<indexterm><primary>PAM-enabled</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>Winbind-based authentication</primary></indexterm>
-This chapter should help you to deploy Winbind-based authentication on any PAM-enabled
-UNIX/Linux system. Winbind can be used to enable user-level application access authentication
-from any MS Windows NT domain, MS Windows 200x Active Directory-based
-domain, or any Samba-based domain environment. It will also help you to configure PAM-based local host access
-controls that are appropriate to your Samba configuration.
-</para>
-
-<para>
-<indexterm><primary>PAM management</primary></indexterm>
-<indexterm><primary>pam_smbpass.so</primary></indexterm>
-In addition to knowing how to configure Winbind into PAM, you will learn generic PAM management
-possibilities and in particular how to deploy tools like <filename>pam_smbpass.so</filename> to your advantage.
-</para>
-
-<note><para>
-The use of Winbind requires more than PAM configuration alone.
-Please refer to <link linkend="winbind">Winbind: Use of Domain Accounts</link>, for further information regarding Winbind.
-</para></note>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>Sun Solaris</primary></indexterm>
-<indexterm><primary>xxxxBSD</primary></indexterm>
-<indexterm><primary>Linux</primary></indexterm>
-<indexterm><primary>Pluggable Authentication Modules</primary><see>PAM</see></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>login</primary></indexterm>
-<indexterm><primary>passwd</primary></indexterm>
-<indexterm><primary>chown</primary></indexterm>
-A number of UNIX systems (e.g., Sun Solaris), as well as the xxxxBSD family and Linux,
-now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication,
-authorization, and resource control services. Prior to the introduction of PAM, a decision
-to use an alternative to the system password database (<filename>/etc/passwd</filename>)
-would require the provision of alternatives for all programs that provide security services.
-Such a choice would involve provision of alternatives to programs such as <command>login</command>,
-<command>passwd</command>, <command>chown</command>, and so on.
-</para>
-
-<para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>/etc/pam.conf</primary></indexterm>
-<indexterm><primary>Solaris</primary></indexterm>
-<indexterm><primary>/etc/pam.d</primary></indexterm>
-PAM provides a mechanism that disconnects these security programs from the underlying
-authentication/authorization infrastructure. PAM is configured by making appropriate modifications to one file,
-<filename>/etc/pam.conf</filename> (Solaris), or by editing individual control files that are
-located in <filename>/etc/pam.d</filename>.
-</para>
-
-<para>
-<indexterm><primary>PAM-enabled</primary></indexterm>
-<indexterm><primary>dynamically loadable library modules</primary></indexterm>
-On PAM-enabled UNIX/Linux systems, it is an easy matter to configure the system to use any
-authentication backend so long as the appropriate dynamically loadable library modules
-are available for it. The backend may be local to the system or may be centralized on a
-remote server.
-</para>
-
-<para>
-PAM support modules are available for:
-</para>
-
-<variablelist>
- <varlistentry><term><filename>/etc/passwd</filename></term><listitem>
- <para>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>PAM modules</primary></indexterm>
-<indexterm><primary>pam_unix.so</primary></indexterm>
-<indexterm><primary>pam_unix2.so</primary></indexterm>
-<indexterm><primary>pam_pwdb.so</primary></indexterm>
-<indexterm><primary>pam_userdb.so</primary></indexterm>
- There are several PAM modules that interact with this standard UNIX user database. The most common are called
- <filename>pam_unix.so</filename>, <filename>pam_unix2.so</filename>, <filename>pam_pwdb.so</filename> and
- <filename>pam_userdb.so</filename>.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term>Kerberos</term><listitem>
- <para>
-<indexterm><primary>pam_krb5.so</primary></indexterm>
-<indexterm><primary>Kerberos</primary></indexterm>
-<indexterm><primary>Heimdal</primary></indexterm>
-<indexterm><primary>MIT Kerberos</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
- The <filename>pam_krb5.so</filename> module allows the use of any Kerberos-compliant server.
- This tool is used to access MIT Kerberos, Heimdal Kerberos, and potentially
- Microsoft Active Directory (if enabled).
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term>LDAP</term><listitem>
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>pam_ldap.so</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>Sun ONE iDentity server</primary></indexterm>
-<indexterm><primary>Novell eDirectory server</primary></indexterm>
-<indexterm><primary>Microsoft Active Directory</primary></indexterm>
- The <filename>pam_ldap.so</filename> module allows the use of any LDAP v2- or v3-compatible backend
- server. Commonly used LDAP backend servers include OpenLDAP v2.0 and v2.1,
- Sun ONE iDentity server, Novell eDirectory server, and Microsoft Active Directory.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term>NetWare Bindery</term><listitem>
- <para>
-<indexterm><primary>NetWare Bindery</primary></indexterm>
-<indexterm><primary>pam_ncp_auth.so</primary></indexterm>
-<indexterm><primary>bindery-enabled</primary></indexterm>
-<indexterm><primary>NetWare Core Protocol-based server</primary></indexterm>
- The <filename>pam_ncp_auth.so</filename> module allows authentication off any bindery-enabled
- NetWare Core Protocol-based server.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term>SMB Password</term><listitem>
- <para>
-<indexterm><primary>SMB Password</primary></indexterm>
-<indexterm><primary>pam_smbpass.so</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
- This module, called <filename>pam_smbpass.so</filename>, allows user authentication of
- the passdb backend that is configured in the Samba &smb.conf; file.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term>SMB Server</term><listitem>
- <para>
-<indexterm><primary>SMB Server</primary></indexterm>
-<indexterm><primary>pam_smb_auth.so</primary></indexterm>
- The <filename>pam_smb_auth.so</filename> module is the original MS Windows networking authentication
- tool. This module has been somewhat outdated by the Winbind module.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term>Winbind</term><listitem>
- <para>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>pam_winbind.so</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
- The <filename>pam_winbind.so</filename> module allows Samba to obtain authentication from any
- MS Windows domain controller. It can just as easily be used to authenticate
- users for access to any PAM-enabled application.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term>RADIUS</term><listitem>
- <para>
-<indexterm><primary>Remote Access Dial-In User Service</primary><see>RADIUS</see></indexterm>
- There is a PAM RADIUS (Remote Access Dial-In User Service) authentication
- module. In most cases, administrators need to locate the source code
- for this tool and compile and install it themselves. RADIUS protocols are
- used by many routers and terminal servers.
- </para>
- </listitem></varlistentry>
-</variablelist>
-
-<para>
-<indexterm><primary>pam_smbpasswd.so</primary></indexterm>
-<indexterm><primary>pam_winbind.so</primary></indexterm>
-Of the modules listed, Samba provides the <filename>pam_smbpasswd.so</filename> and the
-<filename>pam_winbind.so</filename> modules alone.
-</para>
-
-<para>
-<indexterm><primary>wide-area network bandwidth</primary></indexterm>
-<indexterm><primary>efficient authentication</primary></indexterm>
-<indexterm><primary>PAM-capable</primary></indexterm>
-<indexterm><primary>centrally managed</primary></indexterm>
-Once configured, these permit a remarkable level of flexibility in the location and use
-of distributed Samba domain controllers that can provide wide-area network bandwidth,
-efficient authentication services for PAM-capable systems. In effect, this allows the
-deployment of centrally managed and maintained distributed authentication from a
-single-user account database.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Technical Discussion</title>
-
-<para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>privilege-granting applications</primary></indexterm>
-<indexterm><primary>/etc/pam.conf</primary></indexterm>
-<indexterm><primary>/etc/pam.d/</primary></indexterm>
-PAM is designed to provide system administrators with a great deal of flexibility in
-configuration of the privilege-granting applications of their system. The local
-configuration of system security controlled by PAM is contained in one of two places:
-either the single system file <filename>/etc/pam.conf</filename> or the
-<filename>/etc/pam.d/</filename> directory.
-</para>
-
-<sect2>
-<title>PAM Configuration Syntax</title>
-
-<para>
-<indexterm><primary>PAM-specific tokens</primary></indexterm>
-<indexterm><primary>case sensitivity</primary></indexterm>
-In this section we discuss the correct syntax of and generic options respected by entries to these files.
-PAM-specific tokens in the configuration file are case insensitive. The module paths, however, are case
-sensitive, since they indicate a file's name and reflect the case dependence of typical file systems. The
-case sensitivity of the arguments to any given module is defined for each module in turn.
-</para>
-
-<para>
-In addition to the lines described below, there are two special characters provided for the convenience
-of the system administrator: comments are preceded by a <quote>#</quote> and extend to the next end-of-line; also,
-module specification lines may be extended with a <quote>\</quote>-escaped newline.
-</para>
-
-<para>
-<indexterm><primary>PAM authentication module</primary></indexterm>
-<indexterm><primary>/lib/security</primary></indexterm>
-If the PAM authentication module (loadable link library file) is located in the
-default location, then it is not necessary to specify the path. In the case of
-Linux, the default location is <filename>/lib/security</filename>. If the module
-is located outside the default, then the path must be specified as:
-<programlisting>
-auth required /other_path/pam_strange_module.so
-</programlisting>
-</para>
-
-<sect3>
-<title>Anatomy of <filename>/etc/pam.d</filename> Entries</title>
-
-<para>
-The remaining information in this subsection was taken from the documentation of the Linux-PAM
-project. For more information on PAM, see
-<ulink url="http://ftp.kernel.org/pub/linux/libs/pam/">the Official Linux-PAM home page</ulink>.
-</para>
-
-<para>
-<indexterm><primary>/etc/pam.conf</primary></indexterm>
-A general configuration line of the <filename>/etc/pam.conf</filename> file has the following form:
-<programlisting>
-service-name module-type control-flag module-path args
-</programlisting>
-</para>
-
-<para>
-We explain the meaning of each of these tokens. The second (and more recently adopted)
-way of configuring Linux-PAM is via the contents of the <filename>/etc/pam.d/</filename> directory.
-Once we have explained the meaning of the tokens, we describe this method.
-</para>
-
-<variablelist>
- <varlistentry><term>service-name</term><listitem>
- <para>
-<indexterm><primary>ftpd</primary></indexterm>
-<indexterm><primary>rlogind</primary></indexterm>
-<indexterm><primary>su</primary></indexterm>
- The name of the service associated with this entry. Frequently, the service-name is the conventional
- name of the given application &smbmdash; for example, <command>ftpd</command>, <command>rlogind</command> and
- <command>su</command>, and so on.
- </para>
-
- <para>
- There is a special service-name reserved for defining a default authentication mechanism. It has
- the name <parameter>OTHER</parameter> and may be specified in either lower- or uppercase characters.
- Note, when there is a module specified for a named service, the <parameter>OTHER</parameter>
- entries are ignored.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>module-type</term><listitem>
- <para>
- One of (currently) four types of module. The four types are as follows:
- </para>
-
- <itemizedlist>
- <listitem><para>
-<indexterm><primary>auth</primary></indexterm>
-<indexterm><primary>/etc/groups</primary></indexterm>
- <parameter>auth:</parameter> This module type provides two aspects of authenticating the user.
- It establishes that the user is who he or she claims to be by instructing the application
- to prompt the user for a password or other means of identification. Second, the module can
- grant group membership (independently of the <filename>/etc/groups</filename> file)
- or other privileges through its credential-granting properties.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>account</primary></indexterm>
-<indexterm><primary>non-authentication-based account management</primary></indexterm>
- <parameter>account:</parameter> This module performs non-authentication-based account management.
- It is typically used to restrict/permit access to a service based on the time of day, currently
- available system resources (maximum number of users), or perhaps the location of the user
- login. For example, the <quote>root</quote> login may be permitted only on the console.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>session</primary></indexterm>
- <parameter>session:</parameter> Primarily, this module is associated with doing things that need
- to be done for the user before and after he or she can be given service. Such things include logging
- information concerning the opening and closing of some data exchange with a user, mounting
- directories, and so on.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>password</primary></indexterm>
- <parameter>password:</parameter> This last module type is required for updating the authentication
- token associated with the user. Typically, there is one module for each
- <quote>challenge/response</quote> authentication <parameter>(auth)</parameter> module type.
- </para></listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>control-flag</term><listitem>
- <para>
- The control-flag is used to indicate how the PAM library will react to the success or failure of the
- module it is associated with. Since modules can be stacked (modules of the same type execute in series,
- one after another), the control-flags determine the relative importance of each module. The application
- is not made aware of the individual success or failure of modules listed in the
- <filename>/etc/pam.conf</filename> file. Instead, it receives a summary success or fail response from
- the Linux-PAM library. The order of execution of these modules is that of the entries in the
- <filename>/etc/pam.conf</filename> file; earlier entries are executed before later ones.
- As of Linux-PAM v0.60, this control-flag can be defined with one of two syntaxes.
- </para>
-
- <para>
-<indexterm><primary>required</primary></indexterm>
-<indexterm><primary>requisite</primary></indexterm>
-<indexterm><primary>sufficient</primary></indexterm>
-<indexterm><primary>optional</primary></indexterm>
- The simpler (and historical) syntax for the control-flag is a single keyword defined to indicate the
- severity of concern associated with the success or failure of a specific module. There are four such
- keywords: <parameter>required</parameter>, <parameter>requisite</parameter>,
- <parameter>sufficient</parameter>, and <parameter>optional</parameter>.
- </para>
-
- <para>
- The Linux-PAM library interprets these keywords in the following manner:
- </para>
-
- <itemizedlist>
- <listitem><para>
- <parameter>required:</parameter> This indicates that the success of the module is required for the
- module-type facility to succeed. Failure of this module will not be apparent to the user until all
- of the remaining modules (of the same module-type) have been executed.
- </para></listitem>
-
- <listitem><para>
- <parameter>requisite:</parameter> Like required, except that if such a module returns a
- failure, control is directly returned to the application. The return value is that associated with
- the first required or requisite module to fail. This flag can be used to protect against the
- possibility of a user getting the opportunity to enter a password over an unsafe medium. It is
- conceivable that such behavior might inform an attacker of valid accounts on a system. This
- possibility should be weighed against the not insignificant concerns of exposing a sensitive
- password in a hostile environment.
- </para></listitem>
-
- <listitem><para>
- <parameter>sufficient:</parameter> The success of this module is deemed <parameter>sufficient</parameter> to satisfy
- the Linux-PAM library that this module-type has succeeded in its purpose. In the event that no
- previous required module has failed, no more <quote>stacked</quote> modules of this type are invoked.
- (In this case, subsequent required modules are not invoked). A failure of this module is not deemed
- as fatal to satisfying the application that this module-type has succeeded.
- </para></listitem>
-
- <listitem><para>
- <parameter>optional:</parameter> As its name suggests, this control-flag marks the module as not
- being critical to the success or failure of the user's application for service. In general,
- Linux-PAM ignores such a module when determining if the module stack will succeed or fail.
- However, in the absence of any definite successes or failures of previous or subsequent stacked
- modules, this module will determine the nature of the response to the application. One example of
- this latter case is when the other modules return something like PAM_IGNORE.
- </para></listitem>
- </itemizedlist>
-
- <para>
- The more elaborate (newer) syntax is much more specific and gives the administrator a great deal of control
- over how the user is authenticated. This form of the control-flag is delimited with square brackets and
- consists of a series of <parameter>value=action</parameter> tokens:
- </para>
-
-<para><programlisting>
-[value1=action1 value2=action2 ...]
-</programlisting></para>
-
- <para>
- Here, <parameter>value1</parameter> is one of the following return values:
-<screen>
-<parameter>success; open_err; symbol_err; service_err; system_err; buf_err;</parameter>
-<parameter>perm_denied; auth_err; cred_insufficient; authinfo_unavail;</parameter>
-<parameter>user_unknown; maxtries; new_authtok_reqd; acct_expired; session_err;</parameter>
-<parameter>cred_unavail; cred_expired; cred_err; no_module_data; conv_err;</parameter>
-<parameter>authtok_err; authtok_recover_err; authtok_lock_busy;</parameter>
-<parameter>authtok_disable_aging; try_again; ignore; abort; authtok_expired;</parameter>
-<parameter>module_unknown; bad_item;</parameter> and <parameter>default</parameter>.
-</screen>
-</para>
-
- <para>
- The last of these (<parameter>default</parameter>) can be used to set the action for those return values that are not explicitly defined.
- </para>
-
- <para>
- The <parameter>action1</parameter> can be a positive integer or one of the following tokens:
- <parameter>ignore</parameter>; <parameter>ok</parameter>; <parameter>done</parameter>;
- <parameter>bad</parameter>; <parameter>die</parameter>; and <parameter>reset</parameter>.
- A positive integer, J, when specified as the action, can be used to indicate that the next J modules of the
- current module-type will be skipped. In this way, the administrator can develop a moderately sophisticated
- stack of modules with a number of different paths of execution. Which path is taken can be determined by the
- reactions of individual modules.
- </para>
-
- <itemizedlist>
- <listitem><para>
- <parameter>ignore:</parameter> When used with a stack of modules, the module's return status will not
- contribute to the return code the application obtains.
- </para></listitem>
-
- <listitem><para>
- <parameter>bad:</parameter> This action indicates that the return code should be thought of as indicative
- of the module failing. If this module is the first in the stack to fail, its status value will be used
- for that of the whole stack.
- </para></listitem>
-
- <listitem><para>
- <parameter>die:</parameter> Equivalent to bad with the side effect of terminating the module stack and
- PAM immediately returning to the application.
- </para></listitem>
-
- <listitem><para>
- <parameter>ok:</parameter> This tells PAM that the administrator thinks this return code should
- contribute directly to the return code of the full stack of modules. In other words, if the former
- state of the stack would lead to a return of PAM_SUCCESS, the module's return code will override
- this value. Note, if the former state of the stack holds some value that is indicative of a module's
- failure, this <parameter>ok</parameter> value will not be used to override that value.
- </para></listitem>
-
- <listitem><para>
- <parameter>done:</parameter> Equivalent to <parameter>ok</parameter> with the side effect of terminating the module stack and
- PAM immediately returning to the application.
- </para></listitem>
-
- <listitem><para>
- <parameter>reset:</parameter> Clears all memory of the state of the module stack and starts again with
- the next stacked module.
- </para></listitem>
- </itemizedlist>
-
- <para>
- Each of the four keywords, <parameter>required</parameter>; <parameter>requisite</parameter>;
- <parameter>sufficient</parameter>; and <parameter>optional</parameter>, have an equivalent expression in terms
- of the [...] syntax. They are as follows:
- </para>
-
- <para>
- <itemizedlist>
- <listitem><para>
- <parameter>required</parameter> is equivalent to <parameter>[success=ok new_authtok_reqd=ok ignore=ignore default=bad]</parameter>.
- </para></listitem>
-
- <listitem><para>
- <parameter>requisite</parameter> is equivalent to <parameter>[success=ok new_authtok_reqd=ok ignore=ignore default=die]</parameter>.
- </para></listitem>
-
- <listitem><para>
- <parameter>sufficient</parameter> is equivalent to <parameter>[success=done new_authtok_reqd=done default=ignore]</parameter>.
- </para></listitem>
-
- <listitem><para>
- <parameter>optional</parameter> is equivalent to <parameter>[success=ok new_authtok_reqd=ok default=ignore]</parameter>.
- </para></listitem>
- </itemizedlist>
- </para>
-
- <para>
- Just to get a feel for the power of this new syntax, here is a taste of what you can do with it. With Linux-PAM-0.63,
- the notion of client plug-in agents was introduced. This makes it possible for PAM to support
- machine-machine authentication using the transport protocol inherent to the client/server application. With the
- <parameter>[ ... value=action ... ]</parameter> control syntax, it is possible for an application to be configured
- to support binary prompts with compliant clients, but to gracefully fail over into an alternative authentication
- mode for legacy applications.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>module-path</term><listitem>
- <para>
- The pathname of the dynamically loadable object file; the pluggable module itself. If the first character of the
- module path is <quote>/</quote>, it is assumed to be a complete path. If this is not the case, the given module path is appended
- to the default module path: <filename>/lib/security</filename> (but see the previous notes).
- </para>
-
- <para>
- The arguments are a list of tokens that are passed to the module when it is invoked, much like arguments to a typical
- Linux shell command. Generally, valid arguments are optional and are specific to any given module. Invalid arguments
- are ignored by a module; however, when encountering an invalid argument, the module is required to write an error
- to syslog(3). For a list of generic options, see the next section.
- </para>
-
- <para>
- If you wish to include spaces in an argument, you should surround that argument with square brackets. For example:
- </para>
-
-<para><programlisting>
-squid auth required pam_mysql.so user=passwd_query passwd=mada \
-db=eminence [query=select user_name from internet_service where \
-user_name=<quote>%u</quote> and password=PASSWORD(<quote>%p</quote>) and service=<quote>web_proxy</quote>]
-</programlisting></para>
-
- <para>
- When using this convention, you can include <quote>[</quote> characters inside the string, and if you wish to have a <quote>]</quote>
- character inside the string that will survive the argument parsing, you should use <quote>\[</quote>. In other words,
- </para>
-
-<para><programlisting>
-[..[..\]..] --> ..[..]..
-</programlisting></para>
-
- <para>
- Any line in one of the configuration files that is not formatted correctly will generally tend (erring on the
- side of caution) to make the authentication process fail. A corresponding error is written to the system log files
- with a call to syslog(3).
- </para>
- </listitem>
- </varlistentry>
-</variablelist>
-
-</sect3>
-
-</sect2>
-
-<sect2>
-<title>Example System Configurations</title>
-
-<para>
-The following is an example <filename>/etc/pam.d/login</filename> configuration file.
-This example had all options uncommented and is probably not usable
-because it stacks many conditions before allowing successful completion
-of the login process. Essentially, all conditions can be disabled
-by commenting them out, except the calls to <filename>pam_pwdb.so</filename>.
-</para>
-
-<sect3>
-<title>PAM: Original Login Config</title>
-
-<para>
- <programlisting>
-#%PAM-1.0
-# The PAM configuration file for the <quote>login</quote> service
-#
-auth required pam_securetty.so
-auth required pam_nologin.so
-# auth required pam_dialup.so
-# auth optional pam_mail.so
-auth required pam_pwdb.so shadow md5
-# account requisite pam_time.so
-account required pam_pwdb.so
-session required pam_pwdb.so
-# session optional pam_lastlog.so
-# password required pam_cracklib.so retry=3
-password required pam_pwdb.so shadow md5
-</programlisting>
-</para>
-
-</sect3>
-
-<sect3>
-<title>PAM: Login Using <filename>pam_smbpass</filename></title>
-
-<para>
-PAM allows use of replaceable modules. Those available on a sample system include:
-</para>
-
-<para><prompt>$</prompt><userinput>/bin/ls /lib/security</userinput>
-<programlisting>
-pam_access.so pam_ftp.so pam_limits.so
-pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so
-pam_cracklib.so pam_group.so pam_listfile.so
-pam_nologin.so pam_rootok.so pam_tally.so
-pam_deny.so pam_issue.so pam_mail.so
-pam_permit.so pam_securetty.so pam_time.so
-pam_dialup.so pam_lastlog.so pam_mkhomedir.so
-pam_pwdb.so pam_shells.so pam_unix.so
-pam_env.so pam_ldap.so pam_motd.so
-pam_radius.so pam_smbpass.so pam_unix_acct.so
-pam_wheel.so pam_unix_auth.so pam_unix_passwd.so
-pam_userdb.so pam_warn.so pam_unix_session.so
-</programlisting></para>
-
-<para>
-The following example for the login program replaces the use of
-the <filename>pam_pwdb.so</filename> module that uses the system
-password database (<filename>/etc/passwd</filename>,
-<filename>/etc/shadow</filename>, <filename>/etc/group</filename>) with
-the module <filename>pam_smbpass.so</filename>, which uses the Samba
-database containing the Microsoft MD4 encrypted password
-hashes. This database is stored either in
-<filename>/usr/local/samba/private/smbpasswd</filename>,
-<filename>/etc/samba/smbpasswd</filename> or in
-<filename>/etc/samba.d/smbpasswd</filename>, depending on the
-Samba implementation for your UNIX/Linux system. The
-<filename>pam_smbpass.so</filename> module is provided by
-Samba version 2.2.1 or later. It can be compiled by specifying the
-<option>--with-pam_smbpass</option> options when running Samba's
-<command>configure</command> script. For more information
-on the <filename>pam_smbpass</filename> module, see the documentation
-in the <filename>source/pam_smbpass</filename> directory of the Samba
-source distribution.
-</para>
-
-<para>
- <programlisting>
-#%PAM-1.0
-# The PAM configuration file for the <quote>login</quote> service
-#
-auth required pam_smbpass.so nodelay
-account required pam_smbpass.so nodelay
-session required pam_smbpass.so nodelay
-password required pam_smbpass.so nodelay
-</programlisting></para>
-
-<para>
-The following is the PAM configuration file for a particular
-Linux system. The default condition uses <filename>pam_pwdb.so</filename>.
-</para>
-
-<para>
- <programlisting>
-#%PAM-1.0
-# The PAM configuration file for the <quote>samba</quote> service
-#
-auth required pam_pwdb.so nullok nodelay shadow audit
-account required pam_pwdb.so audit nodelay
-session required pam_pwdb.so nodelay
-password required pam_pwdb.so shadow md5
-</programlisting></para>
-
-<para>
-In the following example, the decision has been made to use the
-<command>smbpasswd</command> database even for basic Samba authentication. Such a
-decision could also be made for the <command>passwd</command> program and would
-thus allow the <command>smbpasswd</command> passwords to be changed using the
-<command>passwd</command> program:
-</para>
-
-<para>
- <programlisting>
-#%PAM-1.0
-# The PAM configuration file for the <quote>samba</quote> service
-#
-auth required pam_smbpass.so nodelay
-account required pam_pwdb.so audit nodelay
-session required pam_pwdb.so nodelay
-password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
-</programlisting>
-</para>
-
-<note><para>PAM allows stacking of authentication mechanisms. It is
-also possible to pass information obtained within one PAM module through
-to the next module in the PAM stack. Please refer to the documentation for
-your particular system implementation for details regarding the specific
-capabilities of PAM in this environment. Some Linux implementations also
-provide the <filename>pam_stack.so</filename> module that allows all
-authentication to be configured in a single central file. The
-<filename>pam_stack.so</filename> method has some devoted followers
-on the basis that it allows for easier administration. As with all issues in
-life, though, every decision has trade-offs, so you may want to examine the
-PAM documentation for further helpful information.
-</para></note>
-
-</sect3>
-
-</sect2>
-
-<sect2>
-<title>&smb.conf; PAM Configuration</title>
-
-<para>
-There is an option in &smb.conf; called <smbconfoption name="obey pam restrictions"/>.
-The following is from the online help for this option in SWAT:
-</para>
-
-<blockquote>
-<para>
-When Samba is configured to enable PAM support (i.e., <option>--with-pam</option>), this parameter will
-control whether or not Samba should obey PAM's account and session management directives. The default behavior
-is to use PAM for clear-text authentication only and to ignore any account or session management. Samba always
-ignores PAM for authentication in the case of <smbconfoption name="encrypt passwords">yes</smbconfoption>.
-The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB
-password encryption.
-</para>
-
-<para>Default: <smbconfoption name="obey pam restrictions">no</smbconfoption></para>
-</blockquote>
-
-</sect2>
-
-<sect2>
-<title>Remote CIFS Authentication Using <filename>winbindd.so</filename></title>
-
-<para>
-All operating systems depend on the provision of user credentials acceptable to the platform.
-UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID).
-These are both simple integer numbers that are obtained from a password backend such
-as <filename>/etc/passwd</filename>.
-</para>
-
-<para>
-Users and groups on a Windows NT server are assigned a relative ID (RID) which is unique for
-the domain when the user or group is created. To convert the Windows NT user or group into
-a UNIX user or group, a mapping between RIDs and UNIX user and group IDs is required. This
-is one of the jobs that winbind performs.
-</para>
-
-<para>
-As winbind users and groups are resolved from a server, user and group IDs are allocated
-from a specified range. This is done on a first come, first served basis, although all
-existing users and groups will be mapped as soon as a client performs a user or group
-enumeration command. The allocated UNIX IDs are stored in a database file under the Samba
-lock directory and will be remembered.
-</para>
-
-<para>
-The astute administrator will realize from this that the combination of <filename>pam_smbpass.so</filename>,
-<command>winbindd</command>, and a distributed <smbconfoption name="passdb backend"></smbconfoption>
-such as <parameter>ldap</parameter> will allow the establishment of a centrally managed, distributed user/password
-database that can also be used by all PAM-aware (e.g., Linux) programs and applications. This arrangement can have
-particularly potent advantages compared with the use of Microsoft Active Directory Service (ADS) insofar as
-the reduction of wide-area network authentication traffic.
-</para>
-
-<warning><para>
-The RID to UNIX ID database is the only location where the user and group mappings are
-stored by <command>winbindd</command>. If this file is deleted or corrupted, there is no way for <command>winbindd</command>
-to determine which user and group IDs correspond to Windows NT user and group RIDs.
-</para></warning>
-
-</sect2>
-
-<sect2>
-<title>Password Synchronization Using <filename>pam_smbpass.so</filename></title>
-
-<para>
-<filename>pam_smbpass</filename> is a PAM module that can be used on conforming systems to
-keep the <filename>smbpasswd</filename> (Samba password) database in sync with the UNIX
-password file. PAM is an API supported
-under some UNIX operating systems, such as Solaris, HPUX, and Linux, that provides a
-generic interface to authentication mechanisms.
-</para>
-
-<para>
-This module authenticates a local <filename>smbpasswd</filename> user database. If you require
-support for authenticating against a remote SMB server, or if you are
-concerned about the presence of SUID root binaries on your system, it is
-recommended that you use <filename>pam_winbind</filename> instead.
-</para>
-
-<para>
-Options recognized by this module are shown in <link linkend="smbpassoptions">next table</link>.
-<table frame="all" id="smbpassoptions">
- <title>Options recognized by <parameter>pam_smbpass</parameter></title>
- <tgroup cols="2" align="left">
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <tbody>
- <row><entry>debug</entry><entry>Log more debugging info.</entry></row>
- <row><entry>audit</entry><entry>Like debug, but also logs unknown usernames.</entry></row>
- <row><entry>use_first_pass</entry><entry>Do not prompt the user for passwords; take them from PAM_ items instead.</entry></row>
- <row><entry>try_first_pass</entry><entry>Try to get the password from a previous PAM module; fall back to prompting the user.</entry></row>
- <row><entry>use_authtok</entry>
- <entry>Like try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set (intended for stacking password modules only).</entry></row>
- <row><entry>not_set_pass</entry><entry>Do not make passwords used by this module available to other modules.</entry></row>
- <row><entry>nodelay</entry><entry>dDo not insert ~1-second delays on authentication failure.</entry></row>
- <row><entry>nullok</entry><entry>Null passwords are allowed.</entry></row>
- <row><entry>nonull</entry><entry>Null passwords are not allowed. Used to override the Samba configuration.</entry></row>
- <row><entry>migrate</entry><entry>Only meaningful in an <quote>auth</quote> context; used to update smbpasswd file with a password used for successful authentication.</entry></row>
- <row><entry>smbconf=<replaceable>file</replaceable></entry><entry>Specify an alternate path to the &smb.conf; file.</entry></row>
- </tbody>
-</tgroup>
-</table>
-</para>
-
-<para>
-The following are examples of the use of <filename>pam_smbpass.so</filename> in the format of the Linux
-<filename>/etc/pam.d/</filename> files structure. Those wishing to implement this
-tool on other platforms will need to adapt this appropriately.
-</para>
-
-<sect3>
-<title>Password Synchronization Configuration</title>
-
-<para>
-The following is a sample PAM configuration that shows the use of pam_smbpass to make
-sure <filename>private/smbpasswd</filename> is kept in sync when <filename>/etc/passwd (/etc/shadow)</filename>
-is changed. It is useful when an expired password might be changed by an
-application (such as <command>ssh</command>).
-</para>
-
-<para>
- <programlisting>
-#%PAM-1.0
-# password-sync
-#
-auth requisite pam_nologin.so
-auth required pam_unix.so
-account required pam_unix.so
-password requisite pam_cracklib.so retry=3
-password requisite pam_unix.so shadow md5 use_authtok try_first_pass
-password required pam_smbpass.so nullok use_authtok try_first_pass
-session required pam_unix.so
-</programlisting></para>
-</sect3>
-
-<sect3>
-<title>Password Migration Configuration</title>
-
-<para>
-The following PAM configuration shows the use of <filename>pam_smbpass</filename> to migrate
-from plaintext to encrypted passwords for Samba. Unlike other methods,
-this can be used for users who have never connected to Samba shares:
-password migration takes place when users <command>ftp</command> in, login using <command>ssh</command>, pop
-their mail, and so on.
-</para>
-
-<para>
- <programlisting>
-#%PAM-1.0
-# password-migration
-#
-auth requisite pam_nologin.so
-# pam_smbpass is called IF pam_unix succeeds.
-auth requisite pam_unix.so
-auth optional pam_smbpass.so migrate
-account required pam_unix.so
-password requisite pam_cracklib.so retry=3
-password requisite pam_unix.so shadow md5 use_authtok try_first_pass
-password optional pam_smbpass.so nullok use_authtok try_first_pass
-session required pam_unix.so
-</programlisting></para>
-</sect3>
-
-<sect3>
-<title>Mature Password Configuration</title>
-
-<para>
-The following is a sample PAM configuration for a mature <filename>smbpasswd</filename> installation.
-<filename>private/smbpasswd</filename> is fully populated, and we consider it an error if
-the SMB password does not exist or does not match the UNIX password.
-</para>
-
-<para>
-<programlisting>
-#%PAM-1.0
-# password-mature
-#
-auth requisite pam_nologin.so
-auth required pam_unix.so
-account required pam_unix.so
-password requisite pam_cracklib.so retry=3
-password requisite pam_unix.so shadow md5 use_authtok try_first_pass
-password required pam_smbpass.so use_authtok use_first_pass
-session required pam_unix.so
-</programlisting></para>
-</sect3>
-
-<sect3>
-<title>Kerberos Password Integration Configuration</title>
-
-<para>
-The following is a sample PAM configuration that shows <parameter>pam_smbpass</parameter> used together with
-<parameter>pam_krb5</parameter>. This could be useful on a Samba PDC that is also a member of
-a Kerberos realm.
-</para>
-
-<para>
- <programlisting>
-#%PAM-1.0
-# kdc-pdc
-#
-auth requisite pam_nologin.so
-auth requisite pam_krb5.so
-auth optional pam_smbpass.so migrate
-account required pam_krb5.so
-password requisite pam_cracklib.so retry=3
-password optional pam_smbpass.so nullok use_authtok try_first_pass
-password required pam_krb5.so use_authtok try_first_pass
-session required pam_krb5.so
-</programlisting></para>
-
-</sect3>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-PAM can be fickle and sensitive to configuration glitches. Here we look at a few cases from
-the Samba mailing list.
-</para>
-
- <sect2>
- <title>pam_winbind Problem</title>
-
- <para>
- A user reported, <emphasis>I have the following PAM configuration</emphasis>:
- </para>
-
-<para>
-<programlisting>
-auth required /lib/security/pam_securetty.so
-auth sufficient /lib/security/pam_winbind.so
-auth sufficient /lib/security/pam_unix.so use_first_pass nullok
-auth required /lib/security/pam_stack.so service=system-auth
-auth required /lib/security/pam_nologin.so
-account required /lib/security/pam_stack.so service=system-auth
-account required /lib/security/pam_winbind.so
-password required /lib/security/pam_stack.so service=system-auth
-</programlisting>
-</para>
-
- <para>
- <emphasis>When I open a new console with [ctrl][alt][F1], I can't log in with my user <quote>pitie.</quote>
- I have tried with user <quote>scienceu\pitie</quote> also.</emphasis>
- </para>
-
- <para>
- The problem may lie with the inclusion of <parameter>pam_stack.so
- service=system-auth</parameter>. That file often contains a lot of stuff that may
- duplicate what you are already doing. Try commenting out the <parameter>pam_stack</parameter> lines
- for <parameter>auth</parameter> and <parameter>account</parameter> and see if things work. If they do, look at
- <filename>/etc/pam.d/system-auth</filename> and copy only what you need from it into your
- <filename>/etc/pam.d/login</filename> file. Alternatively, if you want all services to use
- Winbind, you can put the Winbind-specific stuff in <filename>/etc/pam.d/system-auth</filename>.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Winbind Is Not Resolving Users and Groups</title>
-
- <para>
- <quote>
- My &smb.conf; file is correctly configured. I have specified
- <smbconfoption name="idmap uid">12000</smbconfoption>
- and <smbconfoption name="idmap gid">3000-3500,</smbconfoption>
- and <command>winbind</command> is running. When I do the following it all works fine.
- </quote>
- </para>
-
-<para><screen>
-&rootprompt;<userinput>wbinfo -u</userinput>
-MIDEARTH\maryo
-MIDEARTH\jackb
-MIDEARTH\ameds
-...
-MIDEARTH\root
-
-&rootprompt;<userinput>wbinfo -g</userinput>
-MIDEARTH\Domain Users
-MIDEARTH\Domain Admins
-MIDEARTH\Domain Guests
-...
-MIDEARTH\Accounts
-
-&rootprompt;<userinput>getent passwd</userinput>
-root:x:0:0:root:/root:/bin/bash
-bin:x:1:1:bin:/bin:/bin/bash
-...
-maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
-</screen></para>
-
- <para>
- <quote>
- But this command fails:
- </quote>
-<screen>
-&rootprompt;<userinput>chown maryo a_file</userinput>
-chown: 'maryo': invalid user
-</screen>
- <quote>This is driving me nuts! What can be wrong?</quote>
- </para>
-
- <para>
- Your system is likely running <command>nscd</command>, the name service
- caching daemon. Shut it down, do not restart it! You will find your problem resolved.
- </para>
-
- </sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="samba-pdc">
-
-<chapterinfo>
- &author.jht;
- &author.jerry;
- &author.dbannon;
- <author>&person.gd; <contrib>LDAP updates</contrib></author>
-</chapterinfo>
-
-<title>Domain Control</title>
-
-<para>
-There are many who approach MS Windows networking with incredible misconceptions.
-That's okay, because it gives the rest of us plenty of opportunity to be of assistance.
-Those who really want help are well advised to become familiar with information
-that is already available.
-</para>
-
-<para>
-<indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
-You are advised not to tackle this section without having first understood
-and mastered some basics. MS Windows networking is not particularly forgiving of
-misconfiguration. Users of MS Windows networking are likely to complain
-of persistent niggles that may be caused by a broken network configuration.
-To a great many people, however, MS Windows networking starts with a domain controller
-that in some magical way is expected to solve all network operational ills.
-</para>
-
-<para>
-<link linkend="domain-example">The Example Domain Illustration</link> shows a typical MS Windows domain security
-network environment. Workstations A, B, and C are representative of many physical MS Windows
-network clients.
-</para>
-
-<figure id="domain-example">
- <title>An Example Domain.</title>
- <imagefile scale="40">domain</imagefile>
-</figure>
-
-<para>
-From the Samba mailing list we can readily identify many common networking issues.
-If you are not clear on the following subjects, then it will do much good to read the
-sections of this HOWTO that deal with it. These are the most common causes of MS Windows
-networking problems:
-</para>
-
-<itemizedlist>
- <listitem><para>Basic TCP/IP configuration.</para></listitem>
- <listitem><para>NetBIOS name resolution.</para></listitem>
- <listitem><para>Authentication configuration.</para></listitem>
- <listitem><para>User and group configuration.</para></listitem>
- <listitem><para>Basic file and directory permission control in UNIX/Linux.</para></listitem>
- <listitem><para>Understanding how MS Windows clients interoperate in a network environment.</para></listitem>
-</itemizedlist>
-
-<para>
-Do not be put off; on the surface of it MS Windows networking seems so simple that anyone
-can do it. In fact, it is not a good idea to set up an MS Windows network with
-inadequate training and preparation. But let's get our first indelible principle out of the
-way: <emphasis>It is perfectly okay to make mistakes!</emphasis> In the right place and at
-the right time, mistakes are the essence of learning. It is very much not okay to make
-mistakes that cause loss of productivity and impose an avoidable financial burden on an
-organization.
-</para>
-
-<para>
-Where is the right place to make mistakes? Only out of harms way. If you are going to
-make mistakes, then please do it on a test network, away from users, and in such a way as
-to not inflict pain on others. Do your learning on a test network.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>domain security</primary></indexterm>
-<emphasis>What is the key benefit of Microsoft Domain Security?</emphasis>
-</para>
-
-<para>
-<indexterm><primary>single sign-on</primary><see>SSO</see></indexterm>
-<indexterm><primary>trust</primary></indexterm>
-<indexterm><primary>account</primary></indexterm>
-<indexterm><primary>domain</primary><secondary>security</secondary><tertiary>protocols</tertiary></indexterm>
-In a word, <emphasis>single sign-on</emphasis>, or SSO for short. To many, this is the Holy Grail of MS
-Windows NT and beyond networking. SSO allows users in a well-designed network to log onto any workstation that
-is a member of the domain that contains their user account (or in a domain that has an appropriate trust
-relationship with the domain they are visiting) and they will be able to log onto the network and access
-resources (shares, files, and printers) as if they are sitting at their home (personal) workstation. This is a
-feature of the domain security protocols.
-</para>
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
-<indexterm><primary>relative identifier</primary><see>RID</see></indexterm>
-<indexterm><primary>security identifier</primary><see>SID</see></indexterm>
-<indexterm><primary>access control</primary></indexterm>
-The benefits of domain security are available to those sites that deploy a Samba PDC. A domain provides a
-unique network security identifier (SID). Domain user and group security identifiers are comprised of the
-network SID plus a relative identifier (RID) that is unique to the account. User and group SIDs (the network
-SID plus the RID) can be used to create access control lists (ACLs) attached to network resources to provide
-organizational access control. UNIX systems recognize only local security identifiers.
-</para>
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-A SID represents a security context. For example, every Windows machine has local accounts within the security
-context of the local machine which has a unique SID. Every domain (NT4, ADS, Samba) contains accounts that
-exist within the domain security context which is defined by the domain SID.
-</para>
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
-A domain member server will have a SID that differs from the domain SID. The domain member server can be
-configured to regard all domain users as local users. It can also be configured to recognize domain users and
-groups as non-local. SIDs are persistent. A typical domain of user SID looks like this:
-<screen>
-S-1-5-21-726309263-4128913605-1168186429
-</screen>
-Every account (user, group, machine, trust, etc.) is assigned a RID. This is done automatically as an account
-is created. Samba produces the RID algorithmically. The UNIX operating system uses a separate name space for
-user and group identifiers (the UID and GID) but Windows allocates the RID from a single name space. A Windows
-user and a Windows group can not have the same RID. Just as the UNIX user <literal>root</literal> has the
-UID=0, the Windows Administrator has the well-known RID=500. The RID is catenated to the Windows domain SID,
-so Administrator account for a domain that has the above SID will have the user SID
-<screen>
-S-1-5-21-726309263-4128913605-1168186429-500
-</screen>
-The result is that every account in the Windows networking world has a globally unique security identifier.
-</para>
-
-<note><para>
-<indexterm><primary>domain</primary><secondary>member</secondary></indexterm>
-<indexterm><primary>machine account</primary></indexterm>
-<indexterm><primary>domain</primary><secondary>trust account</secondary></indexterm>
-Network clients of an MS Windows domain security environment must be domain members to be able to gain access
-to the advanced features provided. Domain membership involves more than just setting the workgroup name to the
-domain name. It requires the creation of a domain trust account for the workstation (called a machine
-account). Refer to <link linkend="domain-member">Domain Membership</link> for more information.
-</para></note>
-
-<para>
-The following functionalities are an overview of some of the features
-in the Samba-4 release:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>account</primary><secondary>backend</secondary></indexterm>
- Samba-4 supports the use of a choice of backends that may be used in which user, group and machine
- accounts may be stored, but only when acting as a classic
- (NT4) domain controller,
- but not when it is acting as an Active Directory Domain Controller.
- </para>
-
- <para>
- <indexterm><primary>LDAP</primary></indexterm>
- <indexterm><primary>replicated</primary></indexterm>
- <indexterm><primary>distributed</primary></indexterm>
- <indexterm><primary>scalability</primary></indexterm>
- <indexterm><primary>reliability</primary></indexterm>
- An LDAP passdb backend confers the benefit that the account backend can be distributed and replicated,
- which is of great value because it confers scalability and
- provides a high degree of reliability. This may be used when
- Samba-4 is acting as an classic (NT4-like) domain controller,
- but not when it is acting as an Active Directory Domain Controller.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>interdomain</primary><secondary>trust</secondary><tertiary>account</tertiary></indexterm>
- <indexterm><primary>trust account</primary><secondary>interdomain</secondary></indexterm>
- <indexterm><primary>interoperability</primary></indexterm>
- Windows NT4 domain trusts. Samba-4 supports workstation and server (machine) trust accounts. It also
- supports Windows NT4 style interdomain trust accounts, which further assists in network scalability
- and interoperability, but only when itself is an classic
- (NT4-like) domain controller.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>NetBIOS</primary></indexterm>
- <indexterm><primary>raw SMB</primary></indexterm>
- <indexterm><primary>active directory</primary></indexterm>
- <indexterm><primary>domain</primary><secondary>member server</secondary></indexterm>
- <indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
- <indexterm><primary>network</primary><secondary>browsing</secondary></indexterm>
- Operation without NetBIOS over TCP/IP, rather using the raw SMB over TCP/IP. Note, this is feasible
- only when operating as a Microsoft active directory domain
- member server. When acting as a Samba classic (NT4-like) domain
- controller the use of NetBIOS is necessary to provide network browsing support.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>TCP port</primary></indexterm>
- <indexterm><primary>session services</primary></indexterm>
- Samba-4 provides NetBIOS name services (WINS), NetBIOS over TCP/IP (TCP port 139) session services, SMB over
- TCP/IP (TCP port 445) session services, and Microsoft compatible ONC DCE RPC services (TCP port 135)
- services.
- </para></listitem>
-
-
- <listitem><para>
- <indexterm><primary>kerberos</primary></indexterm>
- <indexterm><primary>active directory</primary></indexterm>
- Acting as a Windows 2000 active directory domain controller
- (i.e., Kerberos and Active Directory).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>MMC</primary></indexterm>
- <indexterm><primary>SVRTOOLS.EXE</primary></indexterm>
- <indexterm><primary>Microsoft management console</primary><see>MMC</see></indexterm>
- The Windows 200x/XP Microsoft Management Console (MMC) can be
- used to manage a Samba-4 server, when it is an Active
- Directory Domain Controller. When acting as a classic (NT4)
- domain controller, you
- can use only the MS Windows NT4 Domain Server Manager and the MS Windows NT4 Domain User Manager. Both are
- part of the SVRTOOLS.EXE package mentioned later.
- </para></listitem>
-</itemizedlist>
-
-<para>
-The following functionalities are not provided by Samba-4:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>SAM</primary></indexterm>
- <indexterm><primary>replication</primary></indexterm>
- SAM replication with Windows NT4 domain controllers (i.e., a Samba PDC and a Windows NT BDC, or vice versa).
- This means Samba cannot operate as a BDC when the PDC is Microsoft-based Windows NT PDC. Samba-4 can not
- participate in replication of account data to Windows PDCs and BDCs.
- </para></listitem>
-
-</itemizedlist>
-
-<para>
-<indexterm><primary>group</primary><secondary>mapping</secondary></indexterm>
-Samba implements group mapping between Windows NT groups and UNIX groups (this is really quite complicated
-to explain in a short space). This is discussed more fully in <link linkend="groupmapping">Group Mapping: MS
-Windows and UNIX</link>.
-</para>
-
-<para>
-<indexterm><primary>machine trust account</primary></indexterm>
-<indexterm><primary>trust account</primary><secondary>machine</secondary></indexterm>
-<indexterm><primary>machine account</primary></indexterm>
-Samba-4, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store user and Machine Trust
-Account information in a suitable backend data-store. Refer to <link linkend="machine-trust-accounts">MS
-Windows Workstation/Server Machine Trust Accounts</link>. A complete discussion of account database backends can be found in <link linkend="passdb">Account
-Information Databases</link>.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Single Sign-On and Domain Security</title>
-
-<para>
-<indexterm><primary>single sign-on</primary><see>SSO</see></indexterm>
-<indexterm><primary>SSO</primary></indexterm>
-<indexterm><primary>active directory</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-<indexterm><primary>validation</primary></indexterm>
-<indexterm><primary>password uniqueness</primary></indexterm>
-<indexterm><primary>password history</primary></indexterm>
-When network administrators are asked to describe the benefits of Windows NT4 and active directory networking
-the most often mentioned feature is that of single sign-on (SSO). Many companies have implemented SSO
-solutions. The mode of implementation of a single sign-on solution is an important factor in the practice of
-networking in general, and is critical in respect of Windows networking. A company may have a wide variety of
-information systems, each of which requires a form of user authentication and validation, thus it is not
-uncommon that users may need to remember more than ten login IDs and passwords. This problem is compounded
-when the password for each system must be changed at regular intervals, and particularly so where password
-uniqueness and history limits are applied.
-</para>
-
-<para>
-<indexterm><primary>management overheads</primary></indexterm>
-There is a broadly held perception that SSO is the answer to the problem of users having to deal with too many
-information system access credentials (username/password pairs). Many elaborate schemes have been devised to
-make it possible to deliver a user-friendly SSO solution. The trouble is that if this implementation is not
-done correctly, the site may end up paying dearly by way of complexity and management overheads. Simply put,
-many SSO solutions are an administrative nightmare.
-</para>
-
-<para>
-<indexterm><primary>identity management</primary></indexterm>
-<indexterm><primary>authentication system</primary></indexterm>
-<indexterm><primary>SSO</primary></indexterm>
-SSO implementations utilize centralization of all user account information. Depending on environmental
-complexity and the age of the systems over which a SSO solution is implemented, it may not be possible to
-change the solution architecture so as to accommodate a new identity management and user authentication system.
-Many SSO solutions involving legacy systems consist of a new super-structure that handles authentication on
-behalf of the user. The software that gets layered over the old system may simply implement a proxy
-authentication system. This means that the addition of SSO increases over-all information systems complexity.
-Ideally, the implementation of SSO should reduce complexity and reduce administative overheads.
-</para>
-
-<para>
-<indexterm><primary>centralized identity management</primary></indexterm>
-<indexterm><primary>identity management</primary><secondary>centralized</secondary></indexterm>
-<indexterm><primary>centralized</primary><secondary>authentication</secondary></indexterm>
-<indexterm><primary>legacy systems</primary></indexterm>
-<indexterm><primary>access control</primary></indexterm>
-The initial goal of many network administrators is often to create and use a centralized identity management
-system. It is often assumed that such a centralized system will use a single authentication infrastructure
-that can be used by all information systems. The Microsoft Windows NT4 security domain architecture and the
-Microsoft active directory service are often put forward as the ideal foundation for such a system. It is
-conceptually simple to install an external authentication agent on each of the disparate infromation systems
-that can then use the Microsoft (NT4 domain or ads service) for user authentication and access control. The
-wonderful dream of a single centralized authentication service is commonly broken when realities are realized.
-The problem with legacy systems is often the inability to externalize the authentication and access control
-system it uses because its implementation will be excessively invasive from a re-engineering perspective, or
-because application software has built-in dependencies on particular elements of the way user authentication
-and access control were designed and built.
-</para>
-
-<para>
-<indexterm><primary>meta-directory</primary></indexterm>
-<indexterm><primary>credentials</primary></indexterm>
-<indexterm><primary>disparate information systems</primary></indexterm>
-<indexterm><primary>management procedures</primary></indexterm>
-<indexterm><primary>work-flow protocol</primary></indexterm>
-<indexterm><primary>rights</primary></indexterm>
-<indexterm><primary>privileges</primary></indexterm>
-<indexterm><primary>provisioned</primary></indexterm>
-Over the past decade an industry has been developed around the various methods that have been built to get
-around the key limitations of legacy information technology systems. One approach that is often used involves
-the use of a meta-directory. The meta-directory stores user credentials for all disparate information systems
-in the format that is particular to each system. An elaborate set of management procedures is coupled with a
-rigidly enforced work-flow protocol for managing user rights and privileges within the maze of systems that
-are provisioned by the new infrastructure makes possible user access to all systems using a single set of user
-credentials.
-</para>
-
-<para>
-<indexterm><primary>Organization for the Advancement of Structured Information Standards</primary><see>OASIS</see></indexterm>
-<indexterm><primary>Security Assertion Markup Language</primary><see>SAML</see></indexterm>
-<indexterm><primary>Federated Identity Management</primary><see>FIM</see></indexterm>
-<indexterm><primary>secure access</primary></indexterm>
-The Organization for the Advancement of Structured Information Standards (OASIS) has developed the Security
-Assertion Markup Language (SAML), a structured method for communication of authentication information. The
-over-all umbrella name for the technologies and methods that deploy SAML is called Federated Identity
-Management (FIM). FIM depends on each system in the complex maze of disparate information systems to
-authenticate their respective users and vouch for secure access to the services each provides.
-</para>
-
-<para>
-<indexterm><primary>Simple Object Access Protocol</primary><see>SOAP</see></indexterm>
-<indexterm><primary>federated organizations</primary></indexterm>
-<indexterm><primary>Liberty Alliance</primary></indexterm>
-<indexterm><primary>federated-identity</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-<indexterm><primary></primary></indexterm>
-SAML documents can be wrapped in a Simple Object Access Protocol (SOAP) message for the computer-to-computer
-communications needed for Web services. Or they may be passed between Web servers of federated organizations
-that share live services. The Liberty Alliance, an industry group formed to promote federated-identity
-standards, has adopted SAML 1.1 as part of its application framework. Microsoft and IBM have proposed an
-alternative specification called WS-Security. Some believe that the competing technologies and methods may
-converge when the SAML 2.0 standard is introduced. A few Web access-management products support SAML today,
-but implementation of the technology mostly requires customization to integrate applications and develop user
-interfaces. In a nutshell, that is why FIM is a big and growing industry.
-</para>
-
-<para>
-<indexterm><primary>interoperability</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>GSSAPI</primary></indexterm>
-<indexterm><primary>general security service application programming interface</primary><see>GSSAPI</see></indexterm>
-Ignoring the bigger picture, which is beyond the scope of this book, the migration of all user and group
-management to a centralized system is a step in the right direction. It is essential for interoperability
-reasons to locate the identity management system data in a directory such as Microsoft Active Directory
-Service (ADS), or any proprietary or open source system that provides a standard protocol for information
-access (such as LDAP) and that can be coupled with a flexible array of authentication mechanisms (such as
-kerberos) that use the protocols that are defined by the various general security service application
-programming interface (GSSAPI) services.
-</para>
-
-<para>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>authentication agents</primary></indexterm>
-A growing number of companies provide authentication agents for disparate legacy platforms to permit the use
-of LDAP systems. Thus the use of OpenLDAP, the dominant open source software implementation of the light
-weight directory access protocol standard. This fact, means that by providing support in Samba for the use of
-LDAP and Microsoft ADS make Samba a highly scalable and forward reaching organizational networking technology.
-</para>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>authentication architecture</primary></indexterm>
-<indexterm><primary>ntlm_auth</primary></indexterm>
-<indexterm><primary>SQUID</primary></indexterm>
-<indexterm><primary>FIM</primary></indexterm>
-Microsoft ADS provides purely proprietary services that, with limitation, can be extended to provide a
-centralized authentication infrastructure. Samba plus LDAP provides a similar opportunity for extension of a
-centralized authentication architecture, but it is the fact that the Samba Team are pro-active in introducing
-the extension of authentication services, using LDAP or otherwise, to applications such as SQUID (the open
-source proxy server) through tools such as the <command>ntlm_auth</command> utility, that does much to create
-sustainable choice and competition in the FIM market place.
-</para>
-
-<para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>identity information</primary></indexterm>
-Primary domain control, if it is to be scalable to meet the needs of large sites, must therefore be capable of
-using LDAP. The rapid adoption of OpenLDAP, and Samba configurations that use it, is ample proof that the era
-of the directory has started. Samba does not demand the use of LDAP, but the demand for a mechanism by which
-user and group identity information can be distributed makes it an an unavoidable option.
-</para>
-
-<para>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>e-Directory</primary></indexterm>
-At this time, the use of Samba based BDCs, necessitates the use of
-either the Samba-4 Active Directory Domain controller or, for classic
-(NT4-like)domains an LDAP backend. The most commonly used LDAP
-implementation used by Samba sites is OpenLDAP. It is possible to use any standards compliant LDAP server.
-Those known to work includes those manufactured by: IBM, CA, Novell (e-Directory), and others.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Basics of Domain Control</title>
-
-<para>
-<indexterm><primary>domain control</primary></indexterm>
-Over the years, public perceptions of what domain control really is has taken on an almost mystical nature.
-Before we branch into a brief overview of domain control, there are three basic types of domain controllers.
-</para>
-
-<sect2>
-<title>Domain Controller Types</title>
-
-<itemizedlist>
- <listitem><para>NT4 style Primary Domain Controller</para></listitem>
- <listitem><para>NT4 style Backup Domain Controller</para></listitem>
- <listitem><para>ADS Domain Controller</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>powerful</primary></indexterm>
-<indexterm><primary>network</primary><secondary>performance</secondary></indexterm>
-<indexterm><primary>domain</primary><secondary>member</secondary><tertiary>server</tertiary></indexterm>
-The <emphasis>Primary Domain Controller</emphasis> or PDC plays an important role in MS Windows NT4. In
-Windows 200x domain control architecture, this role is held by domain controllers. Folklore dictates that
-because of its role in the MS Windows network, the domain controller should be the most powerful and most
-capable machine in the network. As strange as it may seem to say this here, good overall network performance
-dictates that the entire infrastructure needs to be balanced. It is advisable to invest more in standalone
-(domain member) servers than in the domain controllers.
-</para>
-
-<para>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>authenticatior</primary></indexterm>
-<indexterm><primary>synchronization</primary></indexterm>
-<indexterm><primary>FSMO</primary></indexterm>
-<indexterm><primary>Flexible Single Master Operator</primary><see>FSMO</see></indexterm>
-<indexterm><primary>Security Account Manager</primary><see>SAM</see></indexterm>
-In the case of MS Windows NT4-style domains, it is the PDC that initiates a new domain control database.
-This forms a part of the Windows registry called the Security Account Manager (SAM). It plays a key
-part in NT4-type domain user authentication and in synchronization of the domain authentication
-database with BDCs. With Active Directory domains, while some servers
-may be a Flexible Single Master Operator (FSMO) role owner (and
-therefore hold the monopoly for certain operations), it is in general
-a distributed, multi-master replicated directory.
-</para>
-
-<para>
-<indexterm><primary>backend database</primary></indexterm>
-<indexterm><primary>registry</primary></indexterm>
-Samba-4 can use a backend database that holds the same type of data as the NT4-style SAM
-database (one of the registry files). For BDC/BDC operations in a
-classic domain, this functionality can be implemented using an
-LDAP-based user and machine account backend. The Samba-4 Active
-Directory Domain controller implements the required storage internally.<footnote><para>See also <link linkend="passdb">Account Information
-Databases</link>.</para></footnote>
-</para>
-
-<para>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-<indexterm><primary>netlogon</primary></indexterm>
-<indexterm><primary>name lookup</primary></indexterm>
-The <emphasis>Backup Domain Controller</emphasis> or BDC plays a key role in servicing network authentication
-requests. The BDC is biased to answer logon requests in preference to the PDC. On a network segment that has
-a BDC and a PDC, the BDC will most likely service network logon requests. The PDC will answer network logon
-requests when the BDC is too busy (high load). When a user logs onto a Windows domain member client the
-workstation will query the network to locate the nearest network logon server. Where a WINS server is used,
-this is done via a query to the WINS server. If a netlogon server can not be found from the WINS query, or in
-the absence of a WINS server, the workstation will perform a NetBIOS name lookup via a mailslot broadcast over
-the UDP broadcast protocol. This means that the netlogon server that the windows client will use is influenced
-by a number of variables, thus there is no simple determinant of whether a PDC or a BDC will serve a
-particular logon authentication request.
-</para>
-
-<para>
-<indexterm><primary>promote</primary></indexterm>
-<indexterm><primary>demote</primary></indexterm>
-A Windows NT4 BDC can be promoted to a PDC. If the PDC is online at the time that a BDC is promoted to PDC,
-the previous PDC is automatically demoted to a BDC. With Samba, this is not an automatic operation; the PDC
-and BDC must be manually configured, and other appropriate changes also need to be made.
-</para>
-
-<para>
-<indexterm><primary>domain</primary><secondary>controller</secondary><tertiary>convert</tertiary></indexterm>
-With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be.
-It is possible to promote a BDC to a PDC, and vice versa. The only method Microsoft provide to convert a
-Windows NT4 domain controller to a domain member server or a standalone server is to reinstall it. The install
-time choices offered are:
-</para>
-
-<itemizedlist>
- <listitem><para><emphasis>Primary Domain Controller</emphasis> &smbmdash; the one that seeds the domain SAM.</para></listitem>
- <listitem><para><emphasis>Backup Domain Controller</emphasis> &smbmdash; one that obtains a copy of the domain SAM.</para></listitem>
- <listitem><para><emphasis>Domain Member Server</emphasis> &smbmdash; one that has no copy of the domain SAM; rather
- it obtains authentication from a domain controller for all access controls.</para></listitem>
- <listitem><para><emphasis>Standalone Server</emphasis> &smbmdash; one that plays no part in SAM synchronization,
- has its own authentication database, and plays no role in domain security.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>domain</primary><secondary>control</secondary><tertiary>role</tertiary></indexterm>
-<indexterm><primary>native member</primary></indexterm>
-Samba servers can readily be converted to and from domain controller roles through simple changes to the
-&smb.conf; file. Samba is capable of acting fully as a native member of a Windows 200x server Active
-Directory domain.
-</para>
-
-<para>
-<indexterm><primary>convert</primary><secondary>domain member server</secondary></indexterm>
-For the sake of providing a complete picture, MS Windows 2000 domain control configuration is done after the server has been
-installed. Please refer to Microsoft documentation for the procedures that should be followed to convert a
-domain member server to or from a domain control, and to install or remove active directory service support.
-</para>
-
-<para>
-<indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
-<indexterm><primary>SAM</primary><secondary>replication</secondary></indexterm>
-New to Samba is the ability to function fully as an MS Windows NT4-style domain controller,
-excluding the SAM replication components. However, please be aware that Samba also supports the
-MS Windows 200x domain control protocols.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Preparing for Domain Control</title>
-
-<para>
-<indexterm><primary>standalone</primary></indexterm>
-<indexterm><primary>workgroup</primary></indexterm>
-<indexterm><primary>member</primary></indexterm>
-<indexterm><primary>security</primary></indexterm>
-There are two ways that MS Windows machines may interact with each other, with other servers,
-and with domain controllers: either as <emphasis>standalone</emphasis> systems, more commonly
-called <emphasis>workgroup</emphasis> members, or as full participants in a security system,
-more commonly called <emphasis>domain</emphasis> members.
-</para>
-
-<para>
-<indexterm><primary>workgroup</primary></indexterm>
-<indexterm><primary>workgroup</primary><secondary>membership</secondary></indexterm>
-<indexterm><primary>machine trust account</primary></indexterm>
-It should be noted that workgroup membership involves no special configuration other than the machine being
-configured so the network configuration has a commonly used name for its workgroup entry. It is not uncommon
-for the name WORKGROUP to be used for this. With this mode of configuration, there are no Machine Trust
-Accounts, and any concept of membership as such is limited to the fact that all machines appear in the network
-neighborhood to be logically grouped together. Again, just to be clear: <emphasis>workgroup mode does not
-involve security machine accounts</emphasis>.
-</para>
-
-<para>
-<indexterm><primary>domain membership</primary></indexterm>
-<indexterm><primary>machine trust account</primary><secondary>password</secondary></indexterm>
-<indexterm><primary>trigger</primary></indexterm>
-Domain member machines have a machine trust account in the domain accounts database. A special procedure
-must be followed on each machine to effect domain membership. This procedure, which can be done
-only by the local machine Administrator account, creates the domain machine account (if it does
-not exist), and then initializes that account. When the client first logs onto the
-domain, a machine trust account password change will be automatically triggered.
-</para>
-
-<note><para>
-<indexterm><primary>domain member</primary></indexterm>
-When Samba is configured as a domain controller, secure network operation demands that
-all MS Windows NT4/200x/XP Professional clients should be configured as domain members.
-If a machine is not made a member of the domain, then it will operate like a workgroup
-(standalone) machine. Please refer to <link linkend="domain-member">Domain Membership</link>, for
-information regarding domain membership.
-</para></note>
-
-<para>
-The following are necessary for configuring Samba as an MS Windows NT4-style PDC for MS Windows
-NT4/200x/XP clients:
-</para>
-
-<itemizedlist>
- <listitem><para>Configuration of basic TCP/IP and MS Windows networking.</para></listitem>
- <listitem><para>Correct designation of the server role (<smbconfoption name="security">user</smbconfoption>).</para></listitem>
- <listitem><para>Consistent configuration of name resolution.<footnote><para>See <link linkend="NetworkBrowsing">Network Browsing</link>, and
- <link linkend="integrate-ms-networks">Integrating MS Windows Networks with Samba</link>.</para></footnote></para></listitem>
- <listitem><para>Domain logons for Windows NT4/200x/XP Professional clients.</para></listitem>
- <listitem><para>Configuration of roaming profiles or explicit configuration to force local profile usage.</para></listitem>
- <listitem><para>Configuration of network/system policies.</para></listitem>
- <listitem><para>Adding and managing domain user accounts.</para></listitem>
- <listitem><para>Configuring MS Windows NT4/2000 Professional and Windows XP Professional client machines to become domain members.</para></listitem>
-</itemizedlist>
-
-<note><para>
-<indexterm><primary>roaming profiles</primary></indexterm>
-<indexterm><primary>account policies</primary></indexterm>
-Roaming profiles and system/network policies are advanced network administration topics
-that are covered in <link linkend="ProfileMgmt">Desktop Profile Management</link> and
-<link linkend="PolicyMgmt">System and Account Policies</link> of this document. However, these are not
-necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts.
-</para></note>
-
-<para>
-A domain controller is an SMB/CIFS server that:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>NetBIOS</primary><secondary>brooadcast</secondary></indexterm>
- <indexterm><primary>WINS</primary></indexterm>
- <indexterm><primary>UDP</primary></indexterm>
- <indexterm><primary>DNS</primary></indexterm>
- <indexterm><primary>active directory</primary></indexterm>
- Registers and advertises itself as a domain controller (through NetBIOS broadcasts
- as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast,
- to a WINS server over UDP unicast, or via DNS and Active Directory).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>NETLOGON</primary></indexterm>
- <indexterm><primary>LanMan logon service</primary></indexterm>
- Provides the NETLOGON service. (This is actually a collection of services that runs over
- multiple protocols. These include the LanMan logon service, the Netlogon service,
- the Local Security Account service, and variations of them.)
- </para></listitem>
-
- <listitem><para>
- Provides a share called NETLOGON.
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>domain</primary><secondary>master</secondary><tertiary>browser</tertiary></indexterm>
-<indexterm><primary>local</primary><secondary>master</secondary><tertiary>browser</tertiary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>LMB</primary></indexterm>
-<indexterm><primary>browse list</primary></indexterm>
-It is rather easy to configure Samba to provide these. Each Samba domain controller must provide the NETLOGON
-service that Samba calls the <smbconfoption name="domain logons"/> functionality (after the name of the
-parameter in the &smb.conf; file). Additionally, one server in a Samba domain must advertise itself as the
-domain master browser.<footnote><para>See <link linkend="NetworkBrowsing">Network
-Browsing</link>.</para></footnote> This causes the PDC to claim a domain-specific NetBIOS name that identifies
-it as a DMB for its given domain or workgroup. Local master browsers (LMBs) in the same domain or workgroup on
-broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide-area network.
-Browser clients then contact their LMB, and will receive the domain-wide browse list instead of just the list
-for their broadcast-isolated subnet.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Domain Control: Example Configuration</title>
-
-<para>
-The first step in creating a working Samba PDC is to understand the parameters necessary
-in &smb.conf;. An example &smb.conf; for acting as a PDC can be found in <link linkend="pdc-example">the
-smb.conf file for an example PDC</link>.
-</para>
-
-<example id="pdc-example">
-<title>smb.conf for being a PDC</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="netbios name"><replaceable>BELERIAND</replaceable></smbconfoption>
-<smbconfoption name="workgroup"><replaceable>&example.workgroup;</replaceable></smbconfoption>
-<smbconfoption name="passdb backend">tdbsam</smbconfoption>
-<smbconfoption name="security">user</smbconfoption>
-<smbconfoption name="domain logons">yes</smbconfoption>
-<smbconfoption name="logon path">\\%N\profiles\%U</smbconfoption>
-<smbconfoption name="logon drive">H:</smbconfoption>
-<smbconfoption name="logon home">\\homeserver\%U\winprofile</smbconfoption>
-<smbconfoption name="logon script">logon.cmd</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="read only">yes</smbconfoption>
-<smbconfoption name="write list"><replaceable>ntadmin</replaceable></smbconfoption>
-
-<smbconfsection name="[profiles]"/>
-<smbconfoption name="path">/var/lib/samba/profiles</smbconfoption>
-<smbconfoption name="read only">no</smbconfoption>
-<smbconfoption name="create mask">0600</smbconfoption>
-<smbconfoption name="directory mask">0700</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-The basic options shown in <link linkend="pdc-example">this example</link> are explained as follows:
-</para>
-
-<variablelist>
- <varlistentry><term>passdb backend </term>
- <listitem><para>
- <indexterm><primary>group</primary><secondary>account</secondary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- <indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>guest</primary></indexterm>
- <indexterm><primary>default accounts</primary></indexterm>
- This contains all the user and group account information. Acceptable values for a PDC
- are: <emphasis>smbpasswd, tdbsam, and ldapsam</emphasis>. The <quote>guest</quote> entry provides
- default accounts and is included by default; there is no need to add it explicitly.
- </para>
-
- <para>
- <indexterm><primary>passdb backend</primary></indexterm>
- <indexterm><primary>distributed</primary></indexterm>
- <indexterm><primary>smbpasswd</primary></indexterm>
- <indexterm><primary>tdbsam</primary></indexterm>
- Where use of BDCs is intended, the only logical choice is
- to use LDAP so the passdb backend can be distributed. The tdbsam and smbpasswd files
- cannot effectively be distributed and therefore should not be used.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Domain Control Parameters </term>
- <listitem><para>
- <indexterm><primary>network</primary><secondary>logon</secondary></indexterm>
- The parameters <emphasis>domain logons</emphasis>
- parameter is the key parameter indicating domain
- control and network logon support.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Environment Parameters </term>
- <listitem><para>
- <indexterm><primary>logon path</primary></indexterm>
- <indexterm><primary>logon home</primary></indexterm>
- <indexterm><primary>logon drive</primary></indexterm>
- <indexterm><primary>logon script</primary></indexterm>
- The parameters <emphasis>logon path, logon home, logon drive</emphasis>, and <emphasis>logon script</emphasis> are
- environment support settings that help to facilitate client logon operations and that help
- to provide automated control facilities to ease network management overheads. Please refer
- to the man page information for these parameters.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>NETLOGON Share </term>
- <listitem><para>
- <indexterm><primary>NETLOGON</primary></indexterm>
- <indexterm><primary>logon processing</primary></indexterm>
- <indexterm><primary>domain logon</primary></indexterm>
- <indexterm><primary>domain membership</primary></indexterm>
- <indexterm><primary>group policy</primary></indexterm>
- <indexterm><primary>NTConfig.POL</primary></indexterm>
- The NETLOGON share plays a central role in domain logon and domain membership support.
- This share is provided on all Microsoft domain controllers. It is used to provide logon
- scripts, to store group policy files (NTConfig.POL), as well as to locate other common
- tools that may be needed for logon processing. This is an essential share on a domain controller.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>PROFILE Share </term>
- <listitem><para>
- <indexterm><primary>desktop profile</primary></indexterm>
- <indexterm><primary>VFS</primary></indexterm>
- <indexterm><primary>fake_permissions</primary></indexterm>
- <indexterm><primary>profile</primary></indexterm>
- <indexterm><primary></primary></indexterm>
- This share is used to store user desktop profiles. Each user must have a directory at the root
- of this share. This directory must be write-enabled for the user and must be globally read-enabled.
- Samba has a VFS module called <quote>fake_permissions</quote> that may be installed on this share. This will
- allow a Samba administrator to make the directory read-only to everyone. Of course this is useful
- only after the profile has been properly created.
- </para></listitem>
- </varlistentry>
-</variablelist>
-
-<note><para>
-The above parameters make for a full set of functionality that may define the server's mode
-of operation. The following &smb.conf; parameters are the essentials alone:
-</para>
-
-<para>
-<smbconfblock>
-<smbconfoption name="netbios name">BELERIAND</smbconfoption>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="security">User</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-The additional parameters shown in the longer listing in this section just make for
-a more complete explanation.
-</para></note>
-
-</sect1>
-
-<sect1>
-<title>Samba ADS Domain Control</title>
-
-<para>
-<indexterm><primary>active directory</primary></indexterm>
-Samba-4 is also available as an Active Directory server. It can truly function as an Active Directory
-PDC. The protocols for some of the functionality of Active Directory
-domain controllers has been implemented.
-</para>
-
-<para>
-<indexterm><primary>domain controllers</primary></indexterm>
-<indexterm><primary>active directory</primary></indexterm>
-<indexterm><primary>classic domain support</primary></indexterm>
-To be sure, Samba-4 is also designed to provide most of the functionality that Microsoft Windows NT4-style
-domain controllers have. Samba-4 does not have all the capabilities of Windows NT4, but it does have
-a number of features that Windows NT4 domain controllers do not
-have. We call it a <emphasis>classic domain</emphasis> controller for
-this reason, as in short, Samba-4 when acting in this mode is not NT4,
-and the Active Directory Domain Control aspect is a distinct capability.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Domain and Network Logon Configuration</title>
-
-<para>
-<indexterm><primary>domain logon</primary></indexterm>
-The subject of network or domain logons is discussed here because it forms
-an integral part of the essential functionality that is provided by a domain controller.
-</para>
-
-<sect2>
-<title>Domain Network Logon Service</title>
-
-<para>
-<indexterm><primary>domain logon</primary></indexterm>
-All domain controllers must run the netlogon service (<emphasis>domain logons</emphasis>
-in Samba). One domain controller must be configured without the
-<smbconfoption name="domain master"></smbconfoption> parameter
-(the PDC); on all BDCs set the parameter <smbconfoption name="domain master">No</smbconfoption>.
-</para>
-
-<sect3>
-<title>Example Configuration</title>
-
-<example id="PDC-config">
-<title>smb.conf for being a PDC</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-<smbconfoption name="domain master">(omit on PDC, No on BDCs)</smbconfoption>
-
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Network Logon Service</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
-</sect3>
-<sect3>
-<title>The Special Case of MS Windows Home Editions</title>
-
-<para>
-<indexterm><primary>Windows Home editions</primary></indexterm>
-To be completely clear: If you want MS Windows Home Editions to integrate with your
-MS Windows NT4 or Active Directory domain security, understand it cannot be done.
-The only option is to purchase the upgrade from MS Windows Home Edition to
-a MS Windows Professional edition.
-</para>
-
-<note><para>
-MS Windows Home Editions do not have the ability to join any type of domain
-security facility. Unlike MS Windows 9x/Me, MS Windows Home Edition
-deliberatly lacks the ability to log onto a network.
-</para></note>
-
-<para>
-Now that this has been said, please do not ask the mailing list or email any of the
-Samba Team members with your questions asking how to make this work. It can't be done.
-If it can be done, then to do so would violate your software license agreement with
-Microsoft, and we recommend that you do not do that.
-</para>
-
-</sect3>
-
-</sect2>
-
-<sect2>
-<title>Security Mode and Master Browsers</title>
-
-<para>
-<indexterm><primary>security mode</primary></indexterm>
-<indexterm><primary>user-mode security</primary></indexterm>
-<indexterm><primary>share-mode security</primary></indexterm>
-There are a few comments to make in order to tie up some loose ends. There has been much debate over the issue
-of whether it is okay to configure Samba as a domain controller that operates with security mode other than
-user-mode. The only security mode that will not work due to technical reasons is share-mode security. Domain
-and server mode security are really just a variation on SMB user-level security.
-</para>
-
-<para>
-<indexterm><primary>DOMAIN<1C></primary></indexterm>
-<indexterm><primary>DOMAIN<1B></primary></indexterm>
-<indexterm><primary>DMB</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>NetBIOS name</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>election</primary></indexterm>
-Actually, this issue is also closely tied to the debate on whether Samba must be the DMB for its workgroup
-when operating as a domain controller. In a pure Microsoft Windows NT domain, the PDC wins the election to be
-the DMB, and then registers the DOMAIN<1B> NetBIOS name. This is not the name used by Windows clients
-to locate the domain controller, all domain controllers register the DOMAIN<1C> name and Windows clients
-locate a network logon server by seraching for the DOMAIN<1C> name. A DMB is a Domain Master Browser
-&smbmdash; see <link linkend="NetworkBrowsing">The Network Browsing Chapter</link>, <link
-linkend="DMB">Configuring WORKGROUP Browsing</link>; Microsoft PDCs expect to win the election to become the
-DMB, if it loses that election it will report a continuous and rapid sequence of warning messages to its
-Windows event logger complaining that it has lost the election to become a DMB. For this reason, in networks
-where a Samba server is the PDC it is wise to configure the Samba domain controller as the DMB.
-</para>
-
-<note><para>
-<indexterm><primary>DOMAIN<1D></primary></indexterm>
-<indexterm><primary>synchronization</primary></indexterm>
-<indexterm><primary>domain control</primary></indexterm>
-<indexterm><primary>browse list management</primary></indexterm>
-<indexterm><primary>network</primary><secondary>logon</secondary><tertiary>service</tertiary></indexterm>
-SMB/CIFS servers that register the DOMAIN<1C> name do so because they provide the network logon
-service. Server that register the DOMAIN<1B> name are DMBs &smbmdash; meaning that they are responsible
-for browse list synchronization across all machines that have registered the DOMAIN<1D> name. The later
-are LMBs that have the responsibility to listen to all NetBIOS name registrations that occur locally to their
-own network segment. The network logon service (NETLOGON) is germane to domain control and has nothing to do
-with network browsing and browse list management. The 1C and 1B/1D name services are orthogonal to each
-other.
-</para></note>
-
-<para>
-Now back to the issue of configuring a Samba domain controller to use a mode other than <smbconfoption
-name="security">user</smbconfoption>. If a Samba host is configured to use another SMB server or domain
-controller in order to validate user connection requests, it is a fact that some other machine on the network
-(the <smbconfoption name="password server"/>) knows more about the user than the Samba host. About 99 percent
-of the time, this other host is a domain controller. Now to operate in domain mode security, the
-<smbconfoption name="workgroup"/> parameter must be set to the name of the Windows NT domain (which already
-has a domain controller). If the domain does not already have a domain controller, you do not yet have a
-domain.
-</para>
-
-<para>
-Configuring a Samba box as a domain controller for a domain that already by definition has a
-PDC is asking for trouble. Therefore, you should always configure the Samba domain controller
-to be the DMB for its domain and set <smbconfoption name="security">user</smbconfoption>.
-This is the only officially supported mode of operation.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<sect2>
-<title><quote>$</quote> Cannot Be Included in Machine Name</title>
-
-<para>
-<indexterm><primary>BSD</primary></indexterm>
-<indexterm><primary>FreeBSD</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-A machine account, typically stored in <filename>/etc/passwd</filename>, takes the form of the machine
-name with a <quote>$</quote> appended. Some BSD systems will not create a user with a <quote>$</quote> in the name.
-Recent versions of FreeBSD have removed this limitation, but older releases are still in common use.
-</para>
-
-<para>
-<indexterm><primary>vipw</primary></indexterm>
-The problem is only in the program used to make the entry. Once made, it works perfectly. Create a user
-without the <quote>$</quote>. Then use <command>vipw</command> to edit the entry, adding the <quote>$</quote>.
-Or create the whole entry with vipw if you like; make sure you use a unique user login ID.
-</para>
-
-<note><para>The machine account must have the exact name that the workstation has.</para></note>
-
-<note><para>
-The UNIX tool <command>vipw</command> is a common tool for directly editing the <filename>/etc/passwd</filename> file.
-The use of vipw will ensure that shadow files (where used) will remain current with the passwd file. This is
-important for security reasons.
-</para></note>
-
-</sect2>
-
-<sect2>
-<title>Joining Domain Fails Because of Existing Machine Account</title>
-
-<para>
-<indexterm><primary>join domain</primary></indexterm>
-<quote>I get told, `You already have a connection to the Domain....' or `Cannot join domain, the
-credentials supplied conflict with an existing set...' when creating a Machine Trust Account.</quote>
-</para>
-
-<para>
-This happens if you try to create a Machine Trust Account from the machine itself and already have a
-connection (e.g., mapped drive) to a share (or IPC$) on the Samba PDC. The following command will remove all
-network drive connections:
-<screen>
-&dosprompt;<userinput>net use * /d</userinput>
-</screen>
-This will break all network connections.
-</para>
-
-<para>
-Further, if the machine is already a <quote>member of a workgroup</quote> that is the same name as the domain
-you are joining (bad idea), you will get this message. Change the workgroup name to something else &smbmdash;
-it does not matter what &smbmdash; reboot, and try again.
-</para>
-
-</sect2>
-
-<sect2>
-<title>The System Cannot Log You On (C000019B)</title>
-
-<para><quote>
-I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message,
-<errorname>`The system cannot log you on (C000019B). Please try again or consult your system
-administrator</errorname> when attempting to logon.'</quote>
-</para>
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-This occurs when the domain SID stored in the secrets.tdb database is changed. The most common cause of a
-change in domain SID is when the domain name and/or the server name (NetBIOS name) is changed. The only way
-to correct the problem is to restore the original domain SID or remove the domain client from the domain and
-rejoin. The domain SID may be reset using either the net or rpcclient utilities.
-</para>
-
-<para>
-To reset or change the domain SID you can use the net command as follows:
-
-<screen>
-&rootprompt;<userinput>net getlocalsid 'OLDNAME'</userinput>
-&rootprompt;<userinput>net setlocalsid 'SID'</userinput>
-</screen>
-</para>
-
-<para>
-Workstation Machine Trust Accounts work only with the domain (or network) SID. If this SID changes,
-domain members (workstations) will not be able to log onto the domain. The original domain SID
-can be recovered from the secrets.tdb file. The alternative is to visit each workstation to rejoin
-it to the domain.
-</para>
-
-</sect2>
-
-<sect2>
-<title>The Machine Trust Account Is Not Accessible</title>
-
-<para>
-<quote>When I try to join the domain I get the message, <errorname>"The machine account
-for this computer either does not exist or is not accessible</errorname>." What's wrong?</quote>
-</para>
-
-<para>
-This problem is caused by the PDC not having a suitable Machine Trust Account. If you are using the
-<smbconfoption name="add machine script"/> method to create accounts, then this would indicate that it has not
-worked. Ensure the domain admin user system is working.
-</para>
-
-<para>
-Alternately, if you are creating account entries manually, then they have not been created correctly. Make
-sure that you have the entry correct for the Machine Trust Account in <filename>smbpasswd</filename> file on
-the Samba PDC. If you added the account using an editor rather than using the smbpasswd utility, make sure
-that the account name is the machine NetBIOS name with a <quote>$</quote> appended to it (i.e.,
-computer_name$). There must be an entry in both the POSIX UNIX system account backend as well as in the
-SambaSAMAccount backend. The default backend for Samba (i.e., the parameter <parameter>passdb
-backend</parameter> is not specified in the &smb.conf; file, or if specified is set to
-<literal>smbpasswd</literal>, are respectively the <filename>/etc/passwd</filename> and
-<filename>/etc/samba/smbpasswd</filename> (or <filename>/usr/local/samba/lib/private/smbpasswd</filename> if
-compiled using Samba Team default settings). The use of the <filename>/etc/passwd</filename> can be overridden
-by alternative settings in the NSS <filename>/etc/nsswitch.conf</filename> file.
-</para>
-
-<para>
-Some people have also reported that inconsistent subnet masks between the Samba server and the NT
-client can cause this problem. Make sure that these are consistent for both client and server.
-</para>
-</sect2>
-
-<sect2>
-<title>Account Disabled</title>
-
-<para><quote>When I attempt to log in to a Samba domain from a NT4/W200x workstation,
-I get a message about my account being disabled.</quote></para>
-
-<para>
-Enable the user accounts with <userinput>smbpasswd -e <replaceable>username</replaceable>
-</userinput>. This is normally done as an account is created.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Domain Controller Unavailable</title>
-
-<para><quote>Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'</quote></para>
-
-<para>
-A domain controller has to announce its role on the network. This usually takes a while. Be patient for up to 15 minutes,
-then try again.
-</para>
-</sect2>
-
-<sect2>
-<title>Cannot Log onto Domain Member Workstation After Joining Domain</title>
-
-<para>
-<indexterm><primary>schannel</primary></indexterm>
-<indexterm><primary>signing</primary></indexterm>
-After successfully joining the domain, user logons fail with one of two messages: one to the
-effect that the domain controller cannot be found; the other claims that the account does not
-exist in the domain or that the password is incorrect. This may be due to incompatible
-settings between the Windows client and the Samba server for <emphasis>schannel</emphasis>
-(secure channel) settings or <emphasis>smb signing</emphasis> settings. Check your Samba
-settings for <emphasis>client schannel</emphasis>, <emphasis>server schannel</emphasis>,
-<emphasis>client signing</emphasis>, <emphasis>server signing</emphasis> by executing:
-<screen>
-<command>testparm -v | grep channel</command> and looking for the value of these parameters.
-</screen>
-</para>
-
-<para>
-Also use the MMC &smbmdash; Local Security Settings. This tool is available from the
-Control Panel. The Policy settings are found in the Local Policies/Security Options area and are prefixed by
-<emphasis>Secure Channel:..., and Digitally sign...</emphasis>.
-</para>
-
-<para>
-It is important that these be set consistently with the Samba server settings.
-</para>
-
-</sect2>
-
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="passdb">
-<chapterinfo>
- &author.jelmer;
- &author.jht;
- &author.jerry;
- &author.jeremy;
- <author>&person.gd;<contrib>LDAP updates</contrib></author>
- <author>
- <firstname>Olivier (lem)</firstname><surname>Lemaire</surname>
- <affiliation>
- <orgname>IDEALX</orgname>
- <address><email>olem@IDEALX.org</email></address>
- </affiliation>
- </author>
-
- <pubdate>May 24, 2003</pubdate>
-</chapterinfo>
-<title>Account Information Databases</title>
-
-<para>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>ldapsam</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>single repository</primary></indexterm>
-The three passdb backends that are fully maintained (actively supported) by the Samba Team are:
-<literal>smbpasswd</literal> (being obsoleted), <literal>tdbsam</literal> (a tdb-based binary file format),
-and <literal>ldapsam</literal> (LDAP directory). Of these, only the <literal>ldapsam</literal> backend
-stores both POSIX (UNIX) and Samba user and group account information in a single repository. The
-<literal>smbpasswd</literal> and <literal>tdbsam</literal> backends store only Samba user accounts.
-</para>
-
-<para>
-In a strict sense, there are three supported account storage and access systems. One of these is considered
-obsolete (smbpasswd). It is recommended to use the <literal>tdbsam</literal> method for all simple systems. Use
-<literal>ldapsam</literal> for larger and more complex networks.
-</para>
-
-<para>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>account storage mechanisms</primary></indexterm>
-<indexterm><primary>account storage system</primary></indexterm>
-<indexterm><primary>user and trust accounts</primary></indexterm>
-<indexterm><primary>machine trust accounts</primary></indexterm>
-<indexterm><primary>computer accounts</primary></indexterm>
-<indexterm><primary>interdomain trust accounts</primary></indexterm>
-In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice
-of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the
-nature of the account storage system with a focus on user and trust accounts. Trust accounts have two forms,
-machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like
-entities.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<sect2>
- <title>Backward Compatibility Account Storage Systems</title>
-
-<variablelist>
- <varlistentry><term>Plaintext</term>
- <listitem>
- <para>
-<indexterm><primary>plaintext</primary></indexterm>
-<indexterm><primary>plaintext authentication</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>/etc/shadow</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
- This isn't really a backend at all, but is listed here for simplicity. Samba can be configured to pass
- plaintext authentication requests to the traditional UNIX/Linux <filename>/etc/passwd</filename> and
- <filename>/etc/shadow</filename>-style subsystems. On systems that have Pluggable Authentication Modules
- (PAM) support, all PAM modules are supported. The behavior is just as it was with Samba-2.2.x, and the
- protocol limitations imposed by MS Windows clients apply likewise. Please refer to <link
- linkend="passdbtech">Technical Information</link>, for more information regarding the limitations of plaintext
- password usage.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>smbpasswd</term>
- <listitem>
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>LanMan passwords</primary></indexterm>
-<indexterm><primary>NT-encrypted passwords</primary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
- This option allows continued use of the <filename>smbpasswd</filename>
- file that maintains a plain ASCII (text) layout that includes the MS Windows
- LanMan and NT-encrypted passwords as well as a field that stores some
- account information. This form of password backend does not store any of
- the MS Windows NT/200x SAM (Security Account Manager) information required to
- provide the extended controls that are needed for more comprehensive
- interoperation with MS Windows NT4/200x servers.
- </para>
-
- <para>
- This backend should be used only for backward compatibility with older
- versions of Samba. It may be deprecated in future releases.
- </para>
- </listitem>
- </varlistentry>
-</variablelist>
-
-</sect2>
-
-<sect2>
-<title>New Account Storage Systems</title>
-
-<para>
-Samba introduces a number of new password backend capabilities.
-<indexterm><primary>SAM backend</primary><secondary>tdbsam</secondary></indexterm>
-<indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm>
-</para>
-
-<variablelist>
- <varlistentry><term>tdbsam</term>
- <listitem>
- <para>
-<indexterm><primary>rich database backend</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
- This backend provides a rich database backend for local servers. This
- backend is not suitable for multiple domain controllers (i.e., PDC + one
- or more BDC) installations.
- </para>
-
- <para>
-<indexterm><primary>extended SAM</primary></indexterm>
-<indexterm><primary>TDB</primary></indexterm>
-<indexterm><primary>binary format TDB</primary></indexterm>
-<indexterm><primary>trivial database</primary></indexterm>
-<indexterm><primary>system access controls</primary></indexterm>
-<indexterm><primary>MS Windows NT4/200x</primary></indexterm>
- The <emphasis>tdbsam</emphasis> password backend stores the old <emphasis>
- smbpasswd</emphasis> information plus the extended MS Windows NT/200x
- SAM information into a binary format TDB (trivial database) file.
- The inclusion of the extended information makes it possible for Samba
- to implement the same account and system access controls that are possible
- with MS Windows NT4/200x-based systems.
- </para>
-
- <para>
-<indexterm><primary>simple operation</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
- The inclusion of the <emphasis>tdbsam</emphasis> capability is a direct
- response to user requests to allow simple site operation without the overhead
- of the complexities of running OpenLDAP. It is recommended to use this only
- for sites that have fewer than 250 users. For larger sites or implementations,
- the use of OpenLDAP or of Active Directory integration is strongly recommended.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>ldapsam</term>
- <listitem>
- <para>
-<indexterm><primary>rich directory backend</primary></indexterm>
-<indexterm><primary>distributed account</primary></indexterm>
- This provides a rich directory backend for distributed account installation.
- </para>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>Samba schema</primary></indexterm>
-<indexterm><primary>schema file</primary></indexterm>
-<indexterm><primary>examples/LDAP</primary></indexterm>
- Samba has a new and extended LDAP implementation that requires configuration
- of OpenLDAP with a new format Samba schema. The new format schema file is
- included in the <filename class="directory">examples/LDAP</filename> directory of the Samba distribution.
- </para>
-
- <para>
-<indexterm><primary>expands control abilities</primary></indexterm>
-<indexterm><primary>profile</primary></indexterm>
-<indexterm><primary>home directories</primary></indexterm>
-<indexterm><primary>account access controls</primary></indexterm>
-<indexterm><primary>greater scalability</primary></indexterm>
- The new LDAP implementation significantly expands the control abilities that
- were possible with prior versions of Samba. It is now possible to specify
- <quote>per-user</quote> profile settings, home directories, account access controls, and
- much more. Corporate sites will see that the Samba Team has listened to their
- requests both for capability and greater scalability.
- </para>
- </listitem>
- </varlistentry>
-
-</variablelist>
-
-</sect2>
-
-</sect1>
-
-<sect1 id="passdbtech">
- <title>Technical Information</title>
-
- <para>
-<indexterm><primary>plaintext passwords</primary></indexterm>
-<indexterm><primary>encrypted passwords</primary></indexterm>
- Old Windows clients send plaintext passwords over the wire. Samba can check these
- passwords by encrypting them and comparing them to the hash stored in the UNIX user database.
- </para>
-
- <para>
-<indexterm><primary>encrypted passwords</primary></indexterm>
-<indexterm><primary>LanMan</primary></indexterm>
-<indexterm><primary>plaintext passwords</primary></indexterm>
-<indexterm><primary>registry</primary></indexterm>
- Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over
- the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless
- their registry is tweaked.
- </para>
-
- <para>
-<indexterm><primary>UNIX-style encrypted passwords</primary></indexterm>
-<indexterm><primary>converted</primary></indexterm>
- Many people ask why Samba cannot simply use the UNIX password database. Windows requires
- passwords that are encrypted in its own format. The UNIX passwords can't be converted to
- Windows-style encrypted passwords. Because of that, you can't use the standard UNIX user
- database, and you have to store the LanMan and NT hashes somewhere else.
- </para>
-
- <para>
-<indexterm><primary>differently encrypted passwords</primary></indexterm>
-<indexterm><primary>profile</primary></indexterm>
-<indexterm><primary>workstations</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
- In addition to differently encrypted passwords, Windows also stores certain data for each
- user that is not stored in a UNIX user database: for example, workstations the user may logon from,
- the location where the user's profile is stored, and so on. Samba retrieves and stores this
- information using a <smbconfoption name="passdb backend"/>. Commonly available backends are LDAP,
- tdbsam, and plain text file. For more information, see the man page for &smb.conf; regarding the
- <smbconfoption name="passdb backend"/> parameter.
- </para>
-
-
- <figure id="idmap-sid2uid">
- <title>IDMAP: Resolution of SIDs to UIDs.</title>
- <imagefile scale="40">idmap-sid2uid</imagefile>
- </figure>
-
- <para>
- <indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
- The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd
- is not running or cannot be contacted, then only local SID/UID resolution is possible. See <link
- linkend="idmap-sid2uid">resolution of SIDs to UIDs</link> and <link linkend="idmap-uid2sid">resolution of UIDs
- to SIDs</link> diagrams.
- </para>
-
- <figure id="idmap-uid2sid">
- <title>IDMAP: Resolution of UIDs to SIDs.</title>
- <imagefile scale="50">idmap-uid2sid</imagefile>
- </figure>
-
- <sect2>
- <title>Important Notes About Security</title>
-
- <para>
-<indexterm><primary>SMB password encryption</primary></indexterm>
-<indexterm><primary>clear-text passwords</primary></indexterm>
-<indexterm><primary>hashed password equivalent</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>secret</primary></indexterm>
- The UNIX and SMB password encryption techniques seem similar on the surface. This
- similarity is, however, only skin deep. The UNIX scheme typically sends clear-text
- passwords over the network when logging in. This is bad. The SMB encryption scheme
- never sends the clear-text password over the network, but it does store the 16-byte
- hashed values on disk. This is also bad. Why? Because the 16 byte hashed values
- are a <quote>password equivalent.</quote> You cannot derive the user's password from them, but
- they could potentially be used in a modified client to gain access to a server.
- This would require considerable technical knowledge on behalf of the attacker but
- is perfectly possible. You should therefore treat the data stored in whatever passdb
- backend you use (smbpasswd file, LDAP) as though it contained the clear-text
- passwords of all your users. Its contents must be kept secret, and the file should
- be protected accordingly.
- </para>
-
- <para>
-<indexterm><primary>password scheme</primary></indexterm>
-<indexterm><primary>plaintext passwords</primary></indexterm>
-<indexterm><primary>compatible</primary></indexterm>
- Ideally, we would like a password scheme that involves neither plaintext passwords
- on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with
- having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me).
- </para>
-
- <para>
-<indexterm><primary>encrypted passwords</primary></indexterm>
-<indexterm><primary>plaintext passwords</primary></indexterm>
- Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords
- are disabled from being sent over the wire. This mandates either the use of encrypted
- password support or editing the Windows NT registry to re-enable plaintext passwords.
- </para>
-
- <para>
-<indexterm><primary>domain security</primary></indexterm>
-<indexterm><primary>domain environment</primary></indexterm>
- The following versions of Microsoft Windows do not support full domain security protocols,
- although they may log onto a domain environment:
- </para>
-
- <itemizedlist>
- <listitem><para>MS DOS Network client 3.0 with the basic network redirector installed.</para></listitem>
- <listitem><para>Windows 95 with the network redirector update installed.</para></listitem>
- <listitem><para>Windows 98 [Second Edition].</para></listitem>
- <listitem><para>Windows Me.</para></listitem>
- </itemizedlist>
-
- <note>
- <para>
-<indexterm><primary>Windows Home edition</primary></indexterm>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>domain logons</primary></indexterm>
- MS Windows Home editions do not have facilities to become a domain member, and cannot participate in domain logons.
- </para>
- </note>
-
- <para>
- The following versions of MS Windows fully support domain security protocols.
- </para>
-
- <itemizedlist>
- <listitem><para>Windows NT 3.5x.</para></listitem>
- <listitem><para>Windows NT 4.0.</para></listitem>
- <listitem><para>Windows editions labeled Professional.</para></listitem>
- <listitem><para>Windows editions labeled Server/Advanced Server.</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>SMB/CIFS</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-<indexterm><primary>challenge/response mechanism</primary></indexterm>
-<indexterm><primary>clear-text</primary></indexterm>
-<indexterm><primary>encrypted</primary></indexterm>
-<indexterm><primary>negotiate</primary></indexterm>
- All current releases of Microsoft SMB/CIFS clients support authentication via the
- SMB challenge/response mechanism described here. Enabling clear-text authentication
- does not disable the ability of the client to participate in encrypted authentication.
- Instead, it allows the client to negotiate either plaintext or encrypted password
- handling.
- </para>
-
- <para>
-<indexterm><primary>cached encrypted password</primary></indexterm>
-<indexterm><primary>plaintext passwords</primary></indexterm>
-<indexterm><primary>registry change</primary></indexterm>
-<indexterm><primary>auto-reconnect</primary></indexterm>
-<indexterm><primary>encrypted passwords</primary></indexterm>
- MS Windows clients will cache the encrypted password alone. Where plaintext passwords
- are re-enabled through the appropriate registry change, the plaintext password is never
- cached. This means that in the event that a network connections should become disconnected
- (broken), only the cached (encrypted) password will be sent to the resource server to
- effect an auto-reconnect. If the resource server does not support encrypted passwords, the
- auto-reconnect will fail. Use of encrypted passwords is strongly advised.
- </para>
-
- <sect3>
- <title>Advantages of Encrypted Passwords</title>
-
- <itemizedlist>
- <listitem><para>
-<indexterm><primary>passed across the network</primary></indexterm>
-<indexterm><primary>network sniffer</primary></indexterm>
-<indexterm><primary>SMB server</primary></indexterm>
- Plaintext passwords are not passed across the network. Someone using a network sniffer
- cannot just record passwords going to the SMB server.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>not stored anywhere</primary></indexterm>
-<indexterm><primary>memory</primary></indexterm>
-<indexterm><primary>disk</primary></indexterm>
- Plaintext passwords are not stored anywhere in memory or on disk.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>encrypted passwords</primary></indexterm>
-<indexterm><primary>user-level security</primary></indexterm>
-<indexterm><primary>password prompt</primary></indexterm>
-<indexterm><primary>SMB encryption</primary></indexterm>
- Windows NT does not like talking to a server that does not support encrypted passwords. It will refuse to
- browse the server. It will insist on prompting the user for
- the password on each connection, which is very annoying. The only thing you can do to stop this is to use SMB
- encryption.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>encrypted password</primary></indexterm>
-<indexterm><primary>automatic reconnects</primary></indexterm>
- Encrypted password support allows automatic share (resource) reconnects.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
- Encrypted passwords are essential for PDC/BDC operation.
- </para></listitem>
- </itemizedlist>
- </sect3>
-
-
- <sect3>
- <title>Advantages of Non-Encrypted Passwords</title>
-
- <itemizedlist>
- <listitem><para>
-<indexterm><primary>cached in memory</primary></indexterm>
- Plaintext passwords are not kept on disk and are not cached in memory.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>Login</primary></indexterm>
-<indexterm><primary>FTP</primary></indexterm>
- Plaintext passwords use the same password file as other UNIX services, such as Login and FTP.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>Telnet</primary></indexterm>
-<indexterm><primary>FTP</primary></indexterm>
- Use of other services (such as Telnet and FTP) that send plaintext passwords over
- the network makes sending them for SMB not such a big deal.
- </para></listitem>
- </itemizedlist>
- </sect3>
- </sect2>
-
- <sect2>
- <title>Mapping User Identifiers between MS Windows and UNIX</title>
-
- <para>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>mapping</primary></indexterm>
- Every operation in UNIX/Linux requires a user identifier (UID), just as in
- MS Windows NT4/200x this requires a security identifier (SID). Samba provides
- two means for mapping an MS Windows user to a UNIX/Linux UID.
- </para>
-
- <para>
-<indexterm><primary>Samba SAM</primary></indexterm>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>account information database</primary></indexterm>
-<indexterm><primary>local user account</primary></indexterm>
- First, all Samba SAM database accounts require a UNIX/Linux UID that the account will map to. As users are
- added to the account information database, Samba will call the <smbconfoption name="add user script"/>
- interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local
- user account.
- </para>
-
- <para>
- <indexterm><primary>idmap uid</primary></indexterm>
- <indexterm><primary>idmap gid</primary></indexterm>
- <indexterm><primary>UID</primary></indexterm>
- <indexterm><primary>SAM</primary></indexterm>
- <indexterm><primary>foreign domain</primary></indexterm>
- <indexterm><primary>non-member Windows client</primary></indexterm>
- <indexterm><primary>SID</primary></indexterm>
- The second way to map Windows SID to UNIX UID is via the <emphasis>idmap uid</emphasis> and
- <emphasis>idmap gid</emphasis> parameters in &smb.conf;. Please refer to the man page for information about
- these parameters. These parameters are essential when mapping users from a remote (non-member Windows client
- or a member of a foreign domain) SAM server.
- </para>
-
- </sect2>
-
- <sect2 id="idmapbackend">
- <title>Mapping Common UIDs/GIDs on Distributed Machines</title>
-
- <para>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>domain member servers</primary></indexterm>
-<indexterm><primary>NFS</primary></indexterm>
-<indexterm><primary>rsync</primary></indexterm>
- Samba has a special facility that makes it possible to maintain identical UIDs and GIDs
- on all servers in a distributed network. A distributed network is one where there exists
- a PDC, one or more BDCs, and/or one or more domain member servers. Why is this important?
- This is important if files are being shared over more than one protocol (e.g., NFS) and where
- users are copying files across UNIX/Linux systems using tools such as <command>rsync</command>.
- </para>
-
- <para>
-<indexterm><primary>LDAP-based</primary></indexterm>
-<indexterm><primary>idmap backend</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>SAM backend</primary></indexterm>
-<indexterm><primary>LDAP idmap Backend</primary></indexterm>
- <indexterm><primary>idmap backend</primary></indexterm>
- The special facility is enabled using a parameter called <parameter>idmap backend</parameter>.
- The default setting for this parameter is an empty string. Technically it is possible to use
- an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for
- network configurations that also use LDAP for the SAM backend.
- <link linkend="idmapbackendexample">Example Configuration with the LDAP idmap Backend</link>
- shows that configuration.
- </para>
-
-<indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm>
-<example id="idmapbackendexample">
-<title>Example Configuration with the LDAP idmap Backend</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="idmap backend">ldap:ldap://ldap-server.quenya.org:636</smbconfoption>
-<smbconfcomment>Alternatively, this could be specified as:</smbconfcomment>
-<smbconfoption name="idmap backend">ldap:ldaps://ldap-server.quenya.org</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
-<indexterm><primary>LDAP backends</primary></indexterm>
-<indexterm><primary>PADL Software</primary></indexterm>
- A network administrator who wants to make significant use of LDAP backends will sooner or later be
- exposed to the excellent work done by PADL Software. PADL <ulink url="http://www.padl.com"/> have
- produced and released to open source an array of tools that might be of interest. These tools include:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
-<indexterm><primary>nss_ldap</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>AIX</primary></indexterm>
-<indexterm><primary>Linux</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>Solaris</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
- <emphasis>nss_ldap:</emphasis> An LDAP name service switch (NSS) module to provide native
- name service support for AIX, Linux, Solaris, and other operating systems. This tool
- can be used for centralized storage and retrieval of UIDs and GIDs.
- </para>
- </listitem>
-
- <listitem>
- <para>
-<indexterm><primary>pam_ldap</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>access authentication</primary></indexterm>
- <emphasis>pam_ldap:</emphasis> A PAM module that provides LDAP integration for UNIX/Linux
- system access authentication.
- </para>
- </listitem>
-
- <listitem>
- <para>
-<indexterm><primary>idmap_ad</primary></indexterm>
-<indexterm><primary>IDMAP backend</primary></indexterm>
-<indexterm><primary>RFC 2307</primary></indexterm>
-<indexterm><primary>PADL</primary></indexterm>
- <emphasis>idmap_ad:</emphasis> An IDMAP backend that supports the Microsoft Services for
- UNIX RFC 2307 schema available from the PADL Web
- <ulink url="http://www.padl.com/download/xad_oss_plugins.tar.gz">site</ulink>.
- </para>
- </listitem>
- </itemizedlist>
-
- </sect2>
-
- <sect2>
- <title>Comments Regarding LDAP</title>
-
- <para>
-<indexterm><primary>LDAP</primary><secondary>directories</secondary></indexterm>
-<indexterm><primary>architecture</primary></indexterm>
-<indexterm><primary>FIM</primary></indexterm>
-<indexterm><primary>SSO</primary></indexterm>
- There is much excitement and interest in LDAP directories in the information technology world
- today. The LDAP architecture was designed to be highly scalable. It was also designed for
- use across a huge number of potential areas of application encompassing a wide range of operating
- systems and platforms. LDAP technologies are at the heart of the current generations of Federated
- Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment.
- </para>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>eDirectory</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
- LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft
- Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the
- directory services LDAP involves interaction with legacy as well as new generation applications, all of which
- depend on some form of authentication services.
- </para>
-
- <para>
-<indexterm><primary>LDAP directory</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-<indexterm><primary>access controls</primary></indexterm>
-<indexterm><primary>intermediate tools</primary></indexterm>
-<indexterm><primary>middle-ware</primary></indexterm>
-<indexterm><primary>central environment</primary></indexterm>
-<indexterm><primary>infrastructure</primary></indexterm>
-<indexterm><primary>login shells</primary></indexterm>
-<indexterm><primary>mail</primary></indexterm>
-<indexterm><primary>messaging systems</primary></indexterm>
-<indexterm><primary>quota controls</primary></indexterm>
-<indexterm><primary>printing systems</primary></indexterm>
-<indexterm><primary>DNS servers</primary></indexterm>
-<indexterm><primary>DHCP servers</primary></indexterm>
- UNIX services can utilize LDAP directory information for authentication and access controls
- through intermediate tools and utilities. The total environment that consists of the LDAP directory
- and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform
- to be managed from a central environment and yet distributed to wherever the point of need may
- be physically located. Applications that benefit from this infrastructure include: UNIX login
- shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers,
- and also Samba.
- </para>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>scalable</primary></indexterm>
-<indexterm><primary>SAM backend</primary></indexterm>
-<indexterm><primary>LDAP directory</primary></indexterm>
-<indexterm><primary>management costs</primary></indexterm>
- Many sites are installing LDAP for the first time in order to provide a scalable passdb backend
- for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such
- as for the Samba SAM backend. Whatever your particular need and attraction to Samba may be,
- decisions made in respect of the design of the LDAP directory structure and its implementation
- are of a durable nature for the site. These have far-reaching implications that affect long-term
- information systems management costs.
- </para>
-
- <para>
-<indexterm><primary>LDAP deployment</primary></indexterm>
-<indexterm><primary>Directory Information Tree</primary><see>DIT</see></indexterm>
- Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory
- Information Tree (DIT) may impact current and future site needs, as well as the ability to meet
- them. The way that Samba SAM information should be stored within the DIT varies from site to site
- and with each implementation new experience is gained. It is well understood by LDAP veterans that
- first implementations create awakening, second implementations of LDAP create fear, and
- third-generation deployments bring peace and tranquility.
- </para>
-
- <sect3>
- <title>Caution Regarding LDAP and Samba</title>
-
- <para>
-<indexterm><primary>POSIX identity</primary></indexterm>
-<indexterm><primary>networking environment</primary></indexterm>
-<indexterm><primary>user accounts</primary></indexterm>
-<indexterm><primary>group accounts</primary></indexterm>
-<indexterm><primary>machine trust accounts</primary></indexterm>
-<indexterm><primary>interdomain trust accounts</primary></indexterm>
-<indexterm><primary>intermediate information</primary></indexterm>
- Samba requires UNIX POSIX identity information as well as a place to store information that is
- specific to Samba and the Windows networking environment. The most used information that must
- be dealt with includes: user accounts, group accounts, machine trust accounts, interdomain
- trust accounts, and intermediate information specific to Samba internals.
- </para>
-
- <para>
-<indexterm><primary>deployment guidelines</primary></indexterm>
-<indexterm><primary>HOWTO documents</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
- The example deployment guidelines in this book, as well as other books and HOWTO documents
- available from the internet may not fit with established directory designs and implementations.
- The existing DIT may not be able to accommodate the simple information layout proposed in common
- sources. Additionally, you may find that the common scripts and tools that are used to provision
- the LDAP directory for use with Samba may not suit your needs.
- </para>
-
- <para>
-<indexterm><primary>existing LDAP DIT</primary></indexterm>
- It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a
- set of site-specific scripts and utilities to make it possible to deploy Samba within the
- scope of site operations. The way that user and group accounts are distributed throughout
- the DIT may make this a challenging matter. The solution will, of course, be rewarding, but
- the journey to it may be challenging. Take time to understand site needs and do not rush
- into deployment.
- </para>
-
- <para>
-<indexterm><primary>scripts</primary></indexterm>
-<indexterm><primary>tools</primary></indexterm>
- Above all, do not blindly use scripts and tools that are not suitable for your site. Check
- and validate all scripts before you execute them to make sure that the existing infrastructure
- will not be damaged by inadvertent use of an inappropriate tool.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>LDAP Directories and Windows Computer Accounts</title>
-
- <para>
-<indexterm><primary>turnkey solution</primary></indexterm>
-<indexterm><primary>LDAP.</primary></indexterm>
-<indexterm><primary>frustrating experience</primary></indexterm>
- Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and
- configuration of an LDAP directory prior to integration with Samba. A working knowledge
- of LDAP makes Samba integration easy, and the lack of a working knowledge of LDAP can make
- it a frustrating experience.
- </para>
-
- <para>
-<indexterm><primary>computer accounts</primary></indexterm>
-<indexterm><primary>machine accounts</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
- Computer (machine) accounts can be placed wherever you like in an LDAP directory subject
- to some constraints that are described in this chapter.
- </para>
-
- <para>
-<indexterm><primary>POSIX</primary></indexterm>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>computer accounts</primary></indexterm>
-<indexterm><primary>machine accounts</primary></indexterm>
-<indexterm><primary>Windows NT4/200X</primary></indexterm>
-<indexterm><primary>user account</primary></indexterm>
-<indexterm><primary>trust accounts</primary></indexterm>
- The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
- Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
- them. A user account and a machine account are indistinguishable from each other, except that
- the machine account ends in a $ character, as do trust accounts.
- </para>
-
- <para>
-<indexterm><primary>user</primary></indexterm>
-<indexterm><primary>group</primary></indexterm>
-<indexterm><primary>machine</primary></indexterm>
-<indexterm><primary>trust</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
- The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX
- UID is a design decision that was made a long way back in the history of Samba development. It
- is unlikely that this decision will be reversed or changed during the remaining life of the
- Samba-3.x series.
- </para>
-
- <para>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
- The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
- must refer back to the host operating system on which Samba is running. The NSS is the preferred
- mechanism that shields applications (like Samba) from the need to know everything about every
- host OS it runs on.
- </para>
-
- <para>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>passwd</primary></indexterm>
-<indexterm><primary>shadow</primary></indexterm>
-<indexterm><primary>group</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
- Samba asks the host OS to provide a UID via the <quote>passwd</quote>, <quote>shadow</quote>,
- and <quote>group</quote> facilities in the NSS control (configuration) file. The best tool
- for achieving this is left up to the UNIX administrator to determine. It is not imposed by
- Samba. Samba provides winbindd with its support libraries as one method. It is
- possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
- all account entities can be located in an LDAP directory.
- </para>
-
- <para>
-<indexterm><primary>PADL</primary></indexterm>
-<indexterm><primary>nss_ldap</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>documentation</primary></indexterm>
- For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
- be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
- is fundamentally an LDAP design question. The information provided on the Samba list and
- in the documentation is directed at providing working examples only. The design
- of an LDAP directory is a complex subject that is beyond the scope of this documentation.
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1 id="acctmgmttools">
-<title>Account Management Tools</title>
-
-<para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>machine accounts</primary></indexterm>
-<indexterm><primary>management tools</primary></indexterm>
-Samba provides two tools for management of user and machine accounts:
-<command>smbpasswd</command> and <command>pdbedit</command>.
-</para>
-
-<para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>password aging</primary></indexterm>
-<indexterm><primary>failed logins</primary></indexterm>
-The <command>pdbedit</command> can be used to manage account policies in addition to
-Samba user account information. The policy management capability is used to administer
-domain default settings for password aging and management controls to handle failed login
-attempts.
-</para>
-
-<para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>storage mechanism</primary></indexterm>
-<indexterm><primary>SambaSAMAccount</primary></indexterm>
-<indexterm><primary>net</primary></indexterm>
-Some people are confused when reference is made to <literal>smbpasswd</literal> because the
-name refers to a storage mechanism for SambaSAMAccount information, but it is also the name
-of a utility tool. That tool is destined to eventually be replaced by new functionality that
-is being added to the <command>net</command> toolset (see <link linkend="NetCommand">the Net Command</link>).
-</para>
-
- <sect2>
- <title>The <command>smbpasswd</command> Tool</title>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>passwd</primary></indexterm>
-<indexterm><primary>yppasswd</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>storage methods</primary></indexterm>
- The <command>smbpasswd</command> utility is similar to the <command>passwd</command>
- and <command>yppasswd</command> programs. It maintains the two 32 byte password
- fields in the passdb backend. This utility operates independently of the actual
- account and password storage methods used (as specified by the <parameter>passdb
- backend</parameter> in the &smb.conf; file).
- </para>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>client-server mode</primary></indexterm>
- <command>smbpasswd</command> works in a client-server mode where it contacts the
- local smbd to change the user's password on its behalf. This has enormous benefits.
- </para>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>change passwords</primary></indexterm>
- <command>smbpasswd</command> has the capability to change passwords on Windows NT
- servers (this only works when the request is sent to the NT PDC if changing an NT
- domain user's password).
- </para>
-
- <para>
- <indexterm><primary>user management</primary></indexterm>
- <indexterm><primary>user account</primary><secondary>Adding/Deleting</secondary></indexterm>
- <command>smbpasswd</command> can be used to:
- </para>
-
- <itemizedlist>
- <listitem><para><emphasis>add</emphasis> user or machine accounts.</para></listitem>
- <listitem><para><emphasis>delete</emphasis> user or machine accounts.</para></listitem>
- <listitem><para><emphasis>enable</emphasis> user or machine accounts.</para></listitem>
- <listitem><para><emphasis>disable</emphasis> user or machine accounts.</para></listitem>
- <listitem><para><emphasis>set to NULL</emphasis> user passwords.</para></listitem>
- <listitem><para><emphasis>manage</emphasis> interdomain trust accounts.</para></listitem>
- </itemizedlist>
-
- <para>
- To run smbpasswd as a normal user, just type:
- </para>
-
- <para>
-<screen>
-&prompt;<userinput>smbpasswd</userinput>
-<prompt>Old SMB password: </prompt><userinput><replaceable>secret</replaceable></userinput>
-</screen>
- For <replaceable>secret</replaceable>, type the old value here or press return if
- there is no old password.
-<screen>
-<prompt>New SMB Password: </prompt><userinput><replaceable>new secret</replaceable></userinput>
-<prompt>Repeat New SMB Password: </prompt><userinput><replaceable>new secret</replaceable></userinput>
-</screen>
- </para>
-
- <para>
- If the old value does not match the current value stored for that user, or the two
- new values do not match each other, then the password will not be changed.
- </para>
-
- <para>
-<indexterm><primary>SMB password</primary></indexterm>
- When invoked by an ordinary user, the command will allow only the user to change his or her own
- SMB password.
- </para>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>SMB password</primary></indexterm>
- When run by root, <command>smbpasswd</command> may take an optional argument specifying
- the username whose SMB password you wish to change. When run as root, <command>smbpasswd</command>
- does not prompt for or check the old password value, thus allowing root to set passwords
- for users who have forgotten their passwords.
- </para>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>passwd</primary></indexterm>
-<indexterm><primary>yppasswd</primary></indexterm>
-<indexterm><primary>change capabilities</primary></indexterm>
- <command>smbpasswd</command> is designed to work in the way familiar to UNIX
- users who use the <command>passwd</command> or <command>yppasswd</command> commands.
- While designed for administrative use, this tool provides essential user-level
- password change capabilities.
- </para>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
- For more details on using <command>smbpasswd</command>, refer to the man page (the
- definitive reference).
- </para>
- </sect2>
-
- <sect2 id="pdbeditthing">
- <title>The <command>pdbedit</command> Tool</title>
-
- <para>
- <indexterm><primary>pdbedit</primary></indexterm>
- <indexterm><primary>User Management</primary></indexterm>
- <indexterm><primary>account policy</primary></indexterm>
- <indexterm><primary>User Accounts</primary><secondary>Adding/Deleting</secondary></indexterm>
- <command>pdbedit</command> is a tool that can be used only by root. It is used to
- manage the passdb backend, as well as domain-wide account policy settings. <command>pdbedit</command>
- can be used to:
- </para>
-
- <itemizedlist>
- <listitem><para>add, remove, or modify user accounts.</para></listitem>
- <listitem><para>list user accounts.</para></listitem>
- <listitem><para>migrate user accounts.</para></listitem>
- <listitem><para>migrate group accounts.</para></listitem>
- <listitem><para>manage account policies.</para></listitem>
- <listitem><para>manage domain access policy settings.</para></listitem>
- </itemizedlist>
-
- <para>
- <indexterm><primary>Sarbanes-Oxley</primary></indexterm>
- Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to
- implement a series of <literal>internal controls</literal> and procedures to communicate, store,
- and protect financial data. The Sarbanes-Oxley Act has far reaching implications in respect of:
- </para>
-
- <orderedlist>
- <listitem><para>Who has access to information systems that store financial data.</para></listitem>
- <listitem><para>How personal and financial information is treated among employees and business
- partners.</para></listitem>
- <listitem><para>How security vulnerabilities are managed.</para></listitem>
- <listitem><para>Security and patch level maintenance for all information systems.</para></listitem>
- <listitem><para>How information systems changes are documented and tracked.</para></listitem>
- <listitem><para>How information access controls are implemented and managed.</para></listitem>
- <listitem><para>Auditability of all information systems in respect of change and security.</para></listitem>
- <listitem><para>Disciplinary procedures and controls to ensure privacy.</para></listitem>
- </orderedlist>
-
- <para>
- <indexterm><primary>accountability</primary></indexterm>
- <indexterm><primary>compliance</primary></indexterm>
- In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of
- business related information systems so as to ensure the compliance of all information systems that
- are used to store personal information and particularly for financial records processing. Similar
- accountabilities are being demanded around the world.
- </para>
-
- <para>
- <indexterm><primary>laws</primary></indexterm>
- <indexterm><primary>regulations</primary></indexterm>
- <indexterm><primary>pdbedit</primary></indexterm>
- <indexterm><primary>access controls</primary></indexterm>
- <indexterm><primary>manage accounts</primary></indexterm>
- The need to be familiar with the Samba tools and facilities that permit information systems operation
- in compliance with government laws and regulations is clear to all. The <command>pdbedit</command> is
- currently the only Samba tool that provides the capacity to manage account and systems access controls
- and policies. During the remaining life-cycle of the Samba series it is possible the new tools may
- be implemented to aid in this important area.
- </para>
-
- <para>
- Domain global policy controls available in Windows NT4 compared with Samba
- is shown in <link linkend="policycontrols">NT4 Domain v's Samba Policy Controls</link>.
- </para>
-
- <table id="policycontrols">
- <title>NT4 Domain v's Samba Policy Controls</title>
- <tgroup cols="5">
- <colspec align="left" colwidth="2*"/>
- <colspec align="left" colwidth="2*"/>
- <colspec align="center" colwidth="1*"/>
- <colspec align="center" colwidth="1*"/>
- <colspec align="center" colwidth="1*"/>
- <thead>
- <row>
- <entry><para>NT4 policy Name</para></entry>
- <entry><para>Samba Policy Name</para></entry>
- <entry><para>NT4 Range</para></entry>
- <entry><para>Samba Range</para></entry>
- <entry><para>Samba Default</para></entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><para>Maximum Password Age</para></entry>
- <entry><para>maximum password age</para></entry>
- <entry><para>0 - 999 (days)</para></entry>
- <entry><para>0 - 4294967295 (sec)</para></entry>
- <entry><para>4294967295</para></entry>
- </row>
- <row>
- <entry><para>Minimum Password Age</para></entry>
- <entry><para>minimum password age</para></entry>
- <entry><para>0 - 999 (days)</para></entry>
- <entry><para>0 - 4294967295 (sec)</para></entry>
- <entry><para>0</para></entry>
- </row>
- <row>
- <entry><para>Minimum Password Length</para></entry>
- <entry><para>min password length</para></entry>
- <entry><para>1 - 14 (Chars)</para></entry>
- <entry><para>0 - 4294967295 (Chars)</para></entry>
- <entry><para>5</para></entry>
- </row>
- <row>
- <entry><para>Password Uniqueness</para></entry>
- <entry><para>password history</para></entry>
- <entry><para>0 - 23 (#)</para></entry>
- <entry><para>0 - 4294967295 (#)</para></entry>
- <entry><para>0</para></entry>
- </row>
- <row>
- <entry><para>Account Lockout - Reset count after</para></entry>
- <entry><para>reset count minutes</para></entry>
- <entry><para>1 - 99998 (min)</para></entry>
- <entry><para>0 - 4294967295 (min)</para></entry>
- <entry><para>30</para></entry>
- </row>
- <row>
- <entry><para>Lockout after bad logon attempts</para></entry>
- <entry><para>bad lockout attempt</para></entry>
- <entry><para>0 - 998 (#)</para></entry>
- <entry><para>0 - 4294967295 (#)</para></entry>
- <entry><para>0</para></entry>
- </row>
- <row>
- <entry><para>*** Not Known ***</para></entry>
- <entry><para>disconnect time</para></entry>
- <entry><para>TBA</para></entry>
- <entry><para>0 - 4294967295</para></entry>
- <entry><para>0</para></entry>
- </row>
- <row>
- <entry><para>Lockout Duration</para></entry>
- <entry><para>lockout duration</para></entry>
- <entry><para>1 - 99998 (min)</para></entry>
- <entry><para>0 - 4294967295 (min)</para></entry>
- <entry><para>30</para></entry>
- </row>
- <row>
- <entry><para>Users must log on in order to change password</para></entry>
- <entry><para>user must logon to change password</para></entry>
- <entry><para>0/1</para></entry>
- <entry><para>0 - 4294967295</para></entry>
- <entry><para>0</para></entry>
- </row>
- <row>
- <entry><para>*** Registry Setting ***</para></entry>
- <entry><para>refuse machine password change</para></entry>
- <entry><para>0/1</para></entry>
- <entry><para>0 - 4294967295</para></entry>
- <entry><para>0</para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
- <indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>policy settings</primary></indexterm>
-<indexterm><primary>account security</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
- The <command>pdbedit</command> tool is the only one that can manage the account
- security and policy settings. It is capable of all operations that smbpasswd can
- do as well as a superset of them.
- </para>
-
- <para>
- <indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>account import/export</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
- One particularly important purpose of the <command>pdbedit</command> is to allow
- the import/export of account information from one passdb backend to another.
- </para>
-
- <sect3>
- <title>User Account Management</title>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>system accounts</primary></indexterm>
-<indexterm><primary>user account</primary></indexterm>
-<indexterm><primary>domain user manager</primary></indexterm>
-<indexterm><primary>add user script</primary></indexterm>
-<indexterm><primary>interface scripts</primary></indexterm>
- The <command>pdbedit</command> tool, like the <command>smbpasswd</command> tool, requires
- that a POSIX user account already exists in the UNIX/Linux system accounts database (backend).
- Neither tool will call out to the operating system to create a user account because this is
- considered to be the responsibility of the system administrator. When the Windows NT4 domain
- user manager is used to add an account, Samba will implement the <literal>add user script</literal>
- (as well as the other interface scripts) to ensure that user, group and machine accounts are
- correctly created and changed. The use of the <command>pdbedit</command> tool does not
- make use of these interface scripts.
- </para>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>POSIX account</primary></indexterm>
- Before attempting to use the <command>pdbedit</command> tool to manage user and machine
- accounts, make certain that a system (POSIX) account has already been created.
- </para>
-
- <sect4>
- <title>Listing User and Machine Accounts</title>
-
- <para>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>password backend</primary></indexterm>
- The following is an example of the user account information that is stored in
- a tdbsam password backend. This listing was produced by running:
-<screen>
-&prompt;<userinput>pdbedit -Lv met</userinput>
-UNIX username: met
-NT username: met
-Account Flags: [U ]
-User SID: S-1-5-21-1449123459-1407424037-3116680435-2004
-Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201
-Full Name: Melissa E Terpstra
-Home Directory: \\frodo\met\Win9Profile
-HomeDir Drive: H:
-Logon Script: scripts\logon.bat
-Profile Path: \\frodo\Profiles\met
-Domain: &example.workgroup;
-Account desc:
-Workstations: melbelle
-Munged dial:
-Logon time: 0
-Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Password last set: Sat, 14 Dec 2002 14:37:03 GMT
-Password can change: Sat, 14 Dec 2002 14:37:03 GMT
-Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-</screen>
- </para>
-
- <para>
-<indexterm><primary>smbpasswd format</primary></indexterm>
- Accounts can also be listed in the older <literal>smbpasswd</literal> format:
-<screen>
-&rootprompt;<userinput>pdbedit -Lw</userinput>
-root:0:84B0D8E14D158FF8417EAF50CFAC29C3:
- AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[U ]:LCT-42681AB8:
-jht:1000:6BBC4159020A52741486235A2333E4D2:
- CC099521AD554A3C3CF2556274DBCFBC:[U ]:LCT-40D75B5B:
-rcg:1002:E95D4331A6F23AF8AAD3B435B51404EE:
- BB0F2C39B04CA6100F0E535DF8314B43:[U ]:LCT-40D7C5A3:
-afw:1003:1AAFA7F9F6DC1DEAAAD3B435B51404EE:
- CE92C2F9471594CDC4E7860CA6BC62DB:[T ]:LCT-40DA501F:
-met:1004:A2848CB7E076B435AAD3B435B51404EE:
- F25F5D3405085C555236B80B7B22C0D2:[U ]:LCT-4244FAB8:
-aurora$:1005:060DE593EA638B8ACC4A19F14D2FF2BB:
- 060DE593EA638B8ACC4A19F14D2FF2BB:[W ]:LCT-4173E5CC:
-temptation$:1006:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
- A96703C014E404E33D4049F706C45EE9:[W ]:LCT-42BF0C57:
-vaioboss$:1001:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
- 88A30A095160072784C88F811E89F98A:[W ]:LCT-41C3878D:
-frodo$:1008:15891DC6B843ECA41249940C814E316B:
- B68EADCCD18E17503D3DAD3E6B0B9A75:[W ]:LCT-42B7979F:
-marvel$:1011:BF709959C3C94E0B3958B7B84A3BB6F3:
- C610EFE9A385A3E8AA46ADFD576E6881:[W ]:LCT-40F07A4
-</screen>
-<indexterm><primary>login id</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>LanManger password</primary></indexterm>
-<indexterm><primary>NT password</primary></indexterm>
-<indexterm><primary>Account Flags</primary></indexterm>
-<indexterm><primary>LCT</primary><see>last change time</see></indexterm>
- The account information that was returned by this command in order from left to right
- consists of the following colon separated data:
- </para>
-
- <itemizedlist>
- <listitem><para>Login ID.</para></listitem>
- <listitem><para>UNIX UID.</para></listitem>
- <listitem>
- <para>Microsoft LanManager password hash (password converted to upper-case then hashed).</para>
- </listitem>
- <listitem><para>Microsoft NT password hash (hash of the case-preserved password).</para></listitem>
- <listitem><para>Samba SAM Account Flags.</para></listitem>
- <listitem><para>The LCT data (password last change time).</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>Account Flags</primary></indexterm>
-<indexterm><primary>pdbedit</primary></indexterm>
- The Account Flags parameters are documented in the <command>pdbedit</command> man page, and are
- briefly documented in <link linkend="TOSHARG-acctflags">the Account Flags Management section</link>.
- </para>
-
- <para>
-<indexterm><primary>last change time</primary></indexterm>
- The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of
- the time when the password was last changed.
- </para>
-
- </sect4>
-
- <sect4>
- <title>Adding User Accounts</title>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>add a user account</primary></indexterm>
-<indexterm><primary>standalone server</primary></indexterm>
-<indexterm><primary>domain</primary></indexterm>
-<indexterm><primary>SambaSAMAccount</primary></indexterm>
- The <command>pdbedit</command> can be used to add a user account to a standalone server
- or to a domain. In the example shown here the account for the user <literal>vlaan</literal>
- has been created before attempting to add the SambaSAMAccount.
-<screen>
-&rootprompt; pdbedit -a vlaan
-new password: secretpw
-retype new password: secretpw
-Unix username: vlaan
-NT username: vlaan
-Account Flags: [U ]
-User SID: S-1-5-21-726309263-4128913605-1168186429-3014
-Primary Group SID: S-1-5-21-726309263-4128913605-1168186429-513
-Full Name: Victor Laan
-Home Directory: \\frodo\vlaan
-HomeDir Drive: H:
-Logon Script: scripts\logon.bat
-Profile Path: \\frodo\profiles\vlaan
-Domain: &example.workgroup;
-Account desc: Guest User
-Workstations:
-Munged dial:
-Logon time: 0
-Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Password last set: Wed, 29 Jun 2005 19:35:12 GMT
-Password can change: Wed, 29 Jun 2005 19:35:12 GMT
-Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-Last bad password : 0
-Bad password count : 0
-Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
-</screen>
- </para>
-
- </sect4>
-
- <sect4>
- <title>Deleting Accounts</title>
-
- <para>
-<indexterm><primary>account deleted</primary></indexterm>
-<indexterm><primary>SambaSAMAccount</primary></indexterm>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
- An account can be deleted from the SambaSAMAccount database
-<screen>
-&rootprompt; pdbedit -x vlaan
-</screen>
- The account is removed without further screen output. The account is removed only from the
- SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend.
- </para>
-
- <para>
-<indexterm><primary>delete user script</primary></indexterm>
-<indexterm><primary>pdbedit</primary></indexterm>
- The use of the NT4 domain user manager to delete an account will trigger the <parameter>delete user
- script</parameter>, but not the <command>pdbedit</command> tool.
- </para>
-
- </sect4>
-
- <sect4>
- <title>Changing User Accounts</title>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
- Refer to the <command>pdbedit</command> man page for a full synopsis of all operations
- that are available with this tool.
- </para>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
- An example of a simple change in the user account information is the change of the full name
- information shown here:
-<screen>
-&rootprompt; pdbedit -r --fullname="Victor Aluicious Laan" vlaan
-...
-Primary Group SID: S-1-5-21-726309263-4128913605-1168186429-513
-Full Name: Victor Aluicious Laan
-Home Directory: \\frodo\vlaan
-...
-</screen>
- </para>
-
- <para>
-<indexterm><primary>grace time</primary></indexterm>
-<indexterm><primary>password expired</primary></indexterm>
-<indexterm><primary>expired password</primary></indexterm>
- Let us assume for a moment that a user's password has expired and the user is unable to
- change the password at this time. It may be necessary to give the user additional grace time
- so that it is possible to continue to work with the account and the original password. This
- demonstrates how the password expiration settings may be updated
-<screen>
-&rootprompt; pdbedit -Lv vlaan
-...
-Password last set: Sun, 09 Sep 2001 22:21:40 GMT
-Password can change: Thu, 03 Jan 2002 15:08:35 GMT
-Password must change: Thu, 03 Jan 2002 15:08:35 GMT
-Last bad password : Thu, 03 Jan 2002 15:08:35 GMT
-Bad password count : 2
-...
-</screen>
-<indexterm><primary>bad logon attempts</primary></indexterm>
-<indexterm><primary>lock the account</primary></indexterm>
- The user has recorded 2 bad logon attempts and the next will lock the account, but the
- password is also expired. Here is how this account can be reset:
-<screen>
-&rootprompt; pdbedit -z vlaan
-...
-Password last set: Sun, 09 Sep 2001 22:21:40 GMT
-Password can change: Thu, 03 Jan 2002 15:08:35 GMT
-Password must change: Thu, 03 Jan 2002 15:08:35 GMT
-Last bad password : 0
-Bad password count : 0
-...
-</screen>
- The <literal>Password must change:</literal> parameter can be reset like this:
-<screen>
-&rootprompt; pdbedit --pwd-must-change-time=1200000000 vlaan
-...
-Password last set: Sun, 09 Sep 2001 22:21:40 GMT
-Password can change: Thu, 03 Jan 2002 15:08:35 GMT
-Password must change: Thu, 10 Jan 2008 14:20:00 GMT
-...
-</screen>
- Another way to use this tools is to set the date like this:
-<screen>
-&rootprompt; pdbedit --pwd-must-change-time="2010-01-01" \
- --time-format="%Y-%m-%d" vlaan
-...
-Password last set: Sun, 09 Sep 2001 22:21:40 GMT
-Password can change: Thu, 03 Jan 2002 15:08:35 GMT
-Password must change: Fri, 01 Jan 2010 00:00:00 GMT
-...
-</screen>
-<indexterm><primary>strptime</primary></indexterm>
-<indexterm><primary>time format</primary></indexterm>
- Refer to the strptime man page for specific time format information.
- </para>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>SambaSAMAccount</primary></indexterm>
- Please refer to the pdbedit man page for further information relating to SambaSAMAccount
- management.
- </para>
-
- <sect5 id="TOSHARG-acctflags">
- <title>Account Flags Management</title>
-
- <para>
-<indexterm><primary>Samba SAM account flags</primary></indexterm>
-<indexterm><primary>account control block</primary><see>ACB</see></indexterm>
-<indexterm><primary>account encode_bits</primary></indexterm>
-<indexterm><primary>account control flags</primary></indexterm>
- The Samba SAM account flags are properly called the ACB (account control block) within
- the Samba source code. In some parts of the Samba source code they are referred to as the
- account encode_bits, and also as the account control flags.
- </para>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>user account</primary></indexterm>
-<indexterm><primary>machine account</primary></indexterm>
-<indexterm><primary>trust account</primary></indexterm>
-<indexterm><primary>damaged data</primary></indexterm>
- The manual adjustment of user, machine (workstation or server) or an inter-domain trust
- account account flgas should not be necessary under normal conditions of use of Samba. On the other hand,
- where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly
- useful. The tool of choice by which such correction can be affected is the <command>pdbedit</command> utility.
- </para>
-
- <para>
-<indexterm><primary>account flags</primary></indexterm>
-<indexterm><primary>LDAP directory</primary></indexterm>
- There have been a few requests for information regarding the account flags from developers
- who are creating their own Samba management tools. An example of a need for information regarding
- the proper management of the account flags is evident when developing scripts that will be used
- to manage an LDAP directory.
- </para>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>account flag order</primary></indexterm>
- The account flag field can contain up to 16 characters. Presently, only 11 are in use.
- These are listed in <link linkend="accountflags">Samba SAM Account Control Block Flags</link>.
- The order in which the flags are specified to the <command>pdbedit</command> command is not important.
- In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory.
- </para>
-
- <table frame="all" id="accountflags">
- <title>Samba SAM Account Control Block Flags</title>
- <tgroup cols="2" align="center">
- <thead>
- <row><entry align="center">Flag</entry><entry>Description</entry></row>
- </thead>
- <tbody>
- <row>
- <entry align="center">D</entry>
- <entry align="left">Account is disabled.</entry>
- </row>
- <row>
- <entry align="center">H</entry>
- <entry align="left">A home directory is required.</entry>
- </row>
- <row>
- <entry align="center">I</entry>
- <entry align="left">An inter-domain trust account.</entry>
- </row>
- <row>
- <entry align="center">L</entry>
- <entry align="left">Account has been auto-locked.</entry>
- </row>
- <row>
- <entry align="center">M</entry>
- <entry align="left">An MNS (Microsoft network service) logon account.</entry>
- </row>
- <row>
- <entry align="center">N</entry>
- <entry align="left">Password not required.</entry>
- </row>
- <row>
- <entry align="center">S</entry>
- <entry align="left">A server trust account.</entry>
- </row>
- <row>
- <entry align="center">T</entry>
- <entry align="left">Temporary duplicate account entry.</entry>
- </row>
- <row>
- <entry align="center">U</entry>
- <entry align="left">A normal user account.</entry>
- </row>
- <row>
- <entry align="center">W</entry>
- <entry align="left">A workstation trust account.</entry>
- </row>
- <row>
- <entry align="center">X</entry>
- <entry align="left">Password does not expire.</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>account control flags</primary></indexterm>
- An example of use of the <command>pdbedit</command> utility to set the account control flags
- is shown here:
-<screen>
-&rootprompt; pdbedit -r -c "[DLX]" jht
-Unix username: jht
-NT username: jht
-Account Flags: [DHULX ]
-User SID: S-1-5-21-729263-4123605-1186429-3000
-Primary Group SID: S-1-5-21-729263-4123605-1186429-513
-Full Name: John H Terpstra,Utah Office
-Home Directory: \\aurora\jht
-HomeDir Drive: H:
-Logon Script: scripts\logon.bat
-Profile Path: \\aurora\profiles\jht
-Domain: MIDEARTH
-Account desc: BluntObject
-Workstations:
-Logon time: 0
-Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Kickoff time: 0
-Password last set: Sun, 03 Jul 2005 23:19:18 GMT
-Password can change: Sun, 03 Jul 2005 23:19:18 GMT
-Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-Last bad password : 0
-Bad password count : 0
-Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
-</screen>
-<indexterm><primary>default settings</primary></indexterm>
- The flags can be reset to the default settings by executing:
-<screen>
-&rootprompt; pdbedit -r -c "[]" jht
-Unix username: jht
-NT username: jht
-Account Flags: [U ]
-User SID: S-1-5-21-729263-4123605-1186429-3000
-Primary Group SID: S-1-5-21-729263-4123605-1186429-513
-Full Name: John H Terpstra,Utah Office
-Home Directory: \\aurora\jht
-HomeDir Drive: H:
-Logon Script: scripts\logon.bat
-Profile Path: \\aurora\profiles\jht
-Domain: MIDEARTH
-Account desc: BluntObject
-Workstations:
-Logon time: 0
-Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
-Kickoff time: 0
-Password last set: Sun, 03 Jul 2005 23:19:18 GMT
-Password can change: Sun, 03 Jul 2005 23:19:18 GMT
-Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-Last bad password : 0
-Bad password count : 0
-Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
-</screen>
- </para>
-
- </sect5>
-
- </sect4>
-
- <sect4>
- <title>Domain Account Policy Managment</title>
-
- <para>
-<indexterm><primary>domain account access policies</primary></indexterm>
-<indexterm><primary>access policies</primary></indexterm>
- To view the domain account access policies that may be configured execute:
-<screen>
-&rootprompt; pdbedit -P ?
-No account policy by that name
-Account policy names are :
-min password length
-password history
-user must logon to change password
-maximum password age
-minimum password age
-lockout duration
-reset count minutes
-bad lockout attempt
-disconnect time
-refuse machine password change
-</screen>
- </para>
-
- <para>
- Commands will be executed to establish controls for our domain as follows:
- </para>
-
- <orderedlist>
- <listitem><para>min password length = 8 characters.</para></listitem>
- <listitem><para>password history = last 4 passwords.</para></listitem>
- <listitem><para>maximum password age = 90 days.</para></listitem>
- <listitem><para>minimum password age = 7 days.</para></listitem>
- <listitem><para>bad lockout attempt = 8 bad logon attempts.</para></listitem>
- <listitem><para>lockout duration = forever, account must be manually re-enabled.</para></listitem>
- </orderedlist>
-
- <para>
- The following command execution will achieve these settings:
-<screen>
-&rootprompt; pdbedit -P "min password length" -C 8
-account policy value for min password length was 5
-account policy value for min password length is now 8
-&rootprompt; pdbedit -P "password history" -C 4
-account policy value for password history was 0
-account policy value for password history is now 4
-&rootprompt; pdbedit -P "maximum password age" -C 7776000
-account policy value for maximum password age was 4294967295
-account policy value for maximum password age is now 7776000
-&rootprompt; pdbedit -P "minimum password age" -C 604800
-account policy value for minimum password age was 0
-account policy value for minimum password age is now 7
-&rootprompt; pdbedit -P "bad lockout attempt" -C 8
-account policy value for bad lockout attempt was 0
-account policy value for bad lockout attempt is now 8
-&rootprompt; pdbedit -P "lockout duration" -C -1
-account policy value for lockout duration was 30
-account policy value for lockout duration is now 4294967295
-</screen>
- </para>
-
-<note><para>
-To set the maximum (infinite) lockout time use the value of -1.
-</para></note>
-
-<warning><para>
-Account policies must be set individually on each PDC and BDC. At this time (Samba 3.0.11 to Samba 3.0.14a)
-account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some
-time there after. Please check the WHATSNEW.txt file in the Samba tarball for specific update notiations
-regarding this facility.
-</para></warning>
-
- </sect4>
-
- </sect3>
-
- <sect3>
- <title>Account Import/Export</title>
-
- <para>
- <indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>account import/export</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
- The <command>pdbedit</command> tool allows import/export of authentication (account)
- databases from one backend to another. For example, to import/export accounts from an
- old <filename>smbpasswd</filename> database to a <parameter>tdbsam</parameter>
- backend:
- </para>
-
- <procedure>
- <step><para>
-<indexterm><primary>pdbedit</primary></indexterm>
-<screen>
-&rootprompt;<userinput>pdbedit -i smbpasswd -e tdbsam</userinput>
-</screen>
- </para></step>
-
- <step><para>
-<indexterm><primary>smbpasswd</primary></indexterm>
- Replace the <parameter>smbpasswd</parameter> with <parameter>tdbsam</parameter> in the
- <parameter>passdb backend</parameter> configuration in &smb.conf;.
- </para></step>
- </procedure>
-
- </sect3>
- </sect2>
-</sect1>
-
-<sect1>
-<title>Password Backends</title>
-
- <sect2>
- <title>Plaintext</title>
-
- <para>
-<indexterm><primary>user database</primary></indexterm>
-<indexterm><primary>/etc/samba/smbpasswd</primary></indexterm>
-<indexterm><primary>/etc/smbpasswd</primary></indexterm>
-<indexterm><primary>password encryption</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
- Older versions of Samba retrieved user information from the UNIX user database
- and eventually some other fields from the file <filename>/etc/samba/smbpasswd</filename>
- or <filename>/etc/smbpasswd</filename>. When password encryption is disabled, no
- SMB-specific data is stored at all. Instead, all operations are conducted via the way
- that the Samba host OS will access its <filename>/etc/passwd</filename> database.
- On most Linux systems, for example, all user and group resolution is done via PAM.
- </para>
-
- </sect2>
-
- <sect2>
- <title>smbpasswd: Encrypted Password Database</title>
-
- <para>
- <indexterm><primary>SAM backend</primary><secondary>smbpasswd</secondary></indexterm>
-<indexterm><primary>user account</primary></indexterm>
-<indexterm><primary>LM/NT password hashes</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
- Traditionally, when configuring <smbconfoption name="encrypt passwords">yes</smbconfoption>
- in Samba's &smb.conf; file, user account information such as username, LM/NT password hashes,
- password change times, and account flags have been stored in the <filename>smbpasswd(5)</filename>
- file. There are several disadvantages to this approach for sites with large numbers of users
- (counted in the thousands).
- </para>
-
- <itemizedlist>
- <listitem><para>
-<indexterm><primary>lookups</primary></indexterm>
- The first problem is that all lookups must be performed sequentially. Given that
- there are approximately two lookups per domain logon (one during initial logon validation
- and one for a session connection setup, such as when mapping a network drive or printer), this
- is a performance bottleneck for large sites. What is needed is an indexed approach
- such as that used in databases.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>replicate</primary></indexterm>
-<indexterm><primary>rsync</primary></indexterm>
-<indexterm><primary>ssh</primary></indexterm>
-<indexterm><primary>custom scripts</primary></indexterm>
- The second problem is that administrators who desire to replicate an smbpasswd file
- to more than one Samba server are left to use external tools such as
- <command>rsync(1)</command> and <command>ssh(1)</command> and write custom,
- in-house scripts.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>home directory</primary></indexterm>
-<indexterm><primary>password expiration</primary></indexterm>
-<indexterm><primary>relative identifier</primary></indexterm>
-<indexterm><primary>relative identifier</primary><see>RID</see></indexterm>
- Finally, the amount of information that is stored in an smbpasswd entry leaves
- no room for additional attributes such as a home directory, password expiration time,
- or even a relative identifier (RID).
- </para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>user attributes</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>API</primary></indexterm>
-<indexterm><primary>samdb interface</primary></indexterm>
- As a result of these deficiencies, a more robust means of storing user attributes
- used by smbd was developed. The API that defines access to user accounts
- is commonly referred to as the samdb interface (previously, this was called the passdb
- API and is still so named in the Samba source code trees).
- </para>
-
- <para>
-<indexterm><primary>passdb backends</primary></indexterm>
-<indexterm><primary>smbpasswd plaintext database</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>ldapsam</primary></indexterm>
-<indexterm><primary>enterprise</primary></indexterm>
- Samba provides an enhanced set of passdb backends that overcome the deficiencies
- of the smbpasswd plaintext database. These are tdbsam and ldapsam.
- Of these, ldapsam will be of most interest to large corporate or enterprise sites.
- </para>
-
- </sect2>
-
- <sect2>
- <title>tdbsam</title>
-
- <para>
- <indexterm><primary>SAM backend</primary><secondary>tdbsam</secondary></indexterm>
-<indexterm><primary>trivial database</primary><see>TDB</see></indexterm>
-<indexterm><primary>machine account</primary></indexterm>
- Samba can store user and machine account data in a <quote>TDB</quote> (trivial database).
- Using this backend does not require any additional configuration. This backend is
- recommended for new installations that do not require LDAP.
- </para>
-
- <para>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>scalability</primary></indexterm>
- As a general guide, the Samba Team does not recommend using the tdbsam backend for sites
- that have 250 or more users. Additionally, tdbsam is not capable of scaling for use
- in sites that require PDB/BDC implementations that require replication of the account
- database. Clearly, for reason of scalability, the use of ldapsam should be encouraged.
- </para>
-
- <para>
-<indexterm><primary>250-user limit</primary></indexterm>
-<indexterm><primary>performance-based</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
- The recommendation of a 250-user limit is purely based on the notion that this
- would generally involve a site that has routed networks, possibly spread across
- more than one physical location. The Samba Team has not at this time established
- the performance-based scalability limits of the tdbsam architecture.
- </para>
-
- <para>
-<indexterm><primary>4,500 user accounts</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>tdbsam</primary></indexterm>
-<indexterm><primary>SambaSAMAccount</primary></indexterm>
- There are sites that have thousands of users and yet require only one server.
- One site recently reported having 4,500 user accounts on one UNIX system and
- reported excellent performance with the <literal>tdbsam</literal> passdb backend.
- The limitation of where the <literal>tdbsam</literal> passdb backend can be used
- is not one pertaining to a limitation in the TDB storage system, it is based
- only on the need for a reliable distribution mechanism for the SambaSAMAccount
- backend.
- </para>
-
- </sect2>
-
- <sect2>
- <title>ldapsam</title>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>ldapsam</primary></indexterm>
- <indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm>
- There are a few points to stress that the ldapsam does not provide. The LDAP
- support referred to in this documentation does not include:
- </para>
-
- <itemizedlist>
- <listitem><para>A means of retrieving user account information from
- a Windows 200x Active Directory server.</para></listitem>
- <listitem><para>A means of replacing /etc/passwd.</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>LGPL</primary></indexterm>
- The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be
- obtained from <ulink url="http://www.padl.com/">PADL Software</ulink>. More information about the
- configuration of these packages may be found in <ulink url="http://safari.oreilly.com/?XmlId=1-56592-491-6">
- <emphasis>LDAP, System Administration</emphasis> by Gerald Carter, Chapter 6, Replacing NIS"</ulink>.
- </para>
-
- <para>
-<indexterm><primary>LDAP directory</primary></indexterm>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>directory server</primary></indexterm>
- This document describes how to use an LDAP directory for storing Samba user
- account information traditionally stored in the smbpasswd(5) file. It is
- assumed that the reader already has a basic understanding of LDAP concepts
- and has a working directory server already installed. For more information
- on LDAP architectures and directories, please refer to the following sites:
- </para>
-
- <itemizedlist>
- <listitem><para><ulink url="http://www.openldap.org/">OpenLDAP</ulink></para></listitem>
- <listitem><para><ulink url="http://www.sun.com/software/products/directory_srvr_ee/index.xml">
- Sun One Directory Server</ulink></para></listitem>
- <listitem><para><ulink url="http://www.novell.com/products/edirectory/">Novell eDirectory</ulink></para></listitem>
- <listitem><para><ulink url="http://www-306.ibm.com/software/tivoli/products/directory-server/">IBM
- Tivoli Directory Server</ulink></para></listitem>
- <listitem><para><ulink url="http://www.redhat.com/software/rha/directory/">Red Hat Directory
- Server</ulink></para></listitem>
- <listitem><para><ulink url="http://www.linuxsecurity.com/content/view/119229">Fedora Directory
- Server</ulink></para></listitem>
- </itemizedlist>
-
- <para>
- Two additional Samba resources that may prove to be helpful are:
- </para>
-
- <itemizedlist>
- <listitem><para>
-<indexterm><primary>Samba-PDC-LDAP-HOWTO</primary></indexterm>
- The <ulink url="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html">Samba-PDC-LDAP-HOWTO</ulink>
- maintained by Ignacio Coupeau.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>IDEALX</primary></indexterm>
-<indexterm><primary>NT migration scripts</primary></indexterm>
-<indexterm><primary>smbldap-tools</primary></indexterm>
- The NT migration scripts from <ulink url="http://samba.idealx.org/">IDEALX</ulink> that are
- geared to manage users and groups in such a Samba-LDAP domain controller configuration.
- Idealx also produced the smbldap-tools and the Interactive Console Management tool.
- </para></listitem>
- </itemizedlist>
-
- <sect3>
- <title>Supported LDAP Servers</title>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>ldapsam</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>Netscape's Directory Server</primary></indexterm>
- The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x server and
- client libraries. The same code should work with Netscape's Directory Server and client SDK.
- However, there are bound to be compile errors and bugs. These should not be hard to fix.
- Please submit fixes via the process outlined in <link linkend="bugreport">Reporting Bugs</link>.
- </para>
-
- <para>
- Samba is capable of working with any standards-compliant LDAP server.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Schema and Relationship to the RFC 2307 posixAccount</title>
-
-
- <para>
- Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the
- <filename>examples/LDAP/samba.schema</filename> directory of the source code distribution
- tarball. The schema entry for the sambaSamAccount ObjectClass is shown here:
-<programlisting>
-ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
- DESC 'Samba-3.0 Auxiliary SAM Account'
- MUST ( uid $ sambaSID )
- MAY ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $
- sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $
- sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $
- displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $
- sambaProfilePath $ description $ sambaUserWorkstations $
- sambaPrimaryGroupSID $ sambaDomainName ))
-</programlisting>
- </para>
-
- <para>
-<indexterm><primary>samba.schema</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>OID</primary></indexterm>
- The <filename>samba.schema</filename> file has been formatted for OpenLDAP 2.0/2.1.
- The Samba Team owns the OID space used by the above schema and recommends its use.
- If you translate the schema to be used with Netscape DS, please submit the modified
- schema file as a patch to <ulink url="mailto:jerry@samba.org">jerry@samba.org</ulink>.
- </para>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>AUXILIARY</primary></indexterm>
-<indexterm><primary>ObjectClass</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>RFC 2307.</primary></indexterm>
- Just as the smbpasswd file is meant to store information that provides information
- additional to a user's <filename>/etc/passwd</filename> entry, so is the sambaSamAccount
- object meant to supplement the UNIX user account information. A sambaSamAccount is an
- <constant>AUXILIARY</constant> ObjectClass, so it can be used to augment existing
- user account information in the LDAP directory, thus providing information needed
- for Samba account handling. However, there are several fields (e.g., uid) that overlap
- with the posixAccount ObjectClass outlined in RFC 2307. This is by design.
- </para>
-
- <para>
-<indexterm><primary>account information</primary></indexterm>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>posixAccount</primary></indexterm>
-<indexterm><primary>ObjectClasses</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>getpwnam</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>NIS</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
- In order to store all user account information (UNIX and Samba) in the directory,
- it is necessary to use the sambaSamAccount and posixAccount ObjectClasses in
- combination. However, <command>smbd</command> will still obtain the user's UNIX account
- information via the standard C library calls, such as getpwnam().
- This means that the Samba server must also have the LDAP NSS library installed
- and functioning correctly. This division of information makes it possible to
- store all Samba account information in LDAP, but still maintain UNIX account
- information in NIS while the network is transitioning to a full LDAP infrastructure.
- </para>
- </sect3>
-
- <sect3>
- <title>OpenLDAP Configuration</title>
-
- <para>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>OpenLDAP</primary></indexterm>
-<indexterm><primary>slapd</primary></indexterm>
-<indexterm><primary>samba.schema</primary></indexterm>
- To include support for the sambaSamAccount object in an OpenLDAP directory
- server, first copy the samba.schema file to slapd's configuration directory.
- The samba.schema file can be found in the directory <filename>examples/LDAP</filename>
- in the Samba source distribution.
-<screen>
-&rootprompt;<userinput>cp samba.schema /etc/openldap/schema/</userinput>
-</screen>
- </para>
-
- <para>
-<indexterm><primary>samba.schema</primary></indexterm>
-<indexterm><primary>slapd.conf</primary></indexterm>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>cosine.schema</primary></indexterm>
-<indexterm><primary>uid</primary></indexterm>
-<indexterm><primary>inetorgperson.schema</primary></indexterm>
-<indexterm><primary>displayName</primary></indexterm>
-<indexterm><primary>attribute</primary></indexterm>
- Next, include the <filename>samba.schema</filename> file in <filename>slapd.conf</filename>.
- The sambaSamAccount object contains two attributes that depend on other schema
- files. The <parameter>uid</parameter> attribute is defined in <filename>cosine.schema</filename> and
- the <parameter>displayName</parameter> attribute is defined in the <filename>inetorgperson.schema</filename>
- file. Both of these must be included before the <filename>samba.schema</filename> file.
-<programlisting>
-## /etc/openldap/slapd.conf
-
-## schema files (core.schema is required by default)
-include /etc/openldap/schema/core.schema
-
-## needed for sambaSamAccount
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/nis.schema
-include /etc/openldap/schema/samba.schema
-....
-</programlisting>
- </para>
-
- <para>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>posixAccount</primary></indexterm>
-<indexterm><primary>posixGroup</primary></indexterm>
-<indexterm><primary>ObjectClasses</primary></indexterm>
- It is recommended that you maintain some indices on some of the most useful attributes,
- as in the following example, to speed up searches made on sambaSamAccount ObjectClasses
- (and possibly posixAccount and posixGroup as well):
- </para>
-
-<para>
-<programlisting>
-# Indices to maintain
-## required by OpenLDAP
-index objectclass eq
-
-index cn pres,sub,eq
-index sn pres,sub,eq
-## required to support pdb_getsampwnam
-index uid pres,sub,eq
-## required to support pdb_getsambapwrid()
-index displayName pres,sub,eq
-
-## uncomment these if you are storing posixAccount and
-## posixGroup entries in the directory as well
-##index uidNumber eq
-##index gidNumber eq
-##index memberUid eq
-
-index sambaSID eq
-index sambaPrimaryGroupSID eq
-index sambaDomainName eq
-index default sub
-</programlisting>
-</para>
-
- <para>
- Create the new index by executing:
-<screen>
-&rootprompt;./sbin/slapindex -f slapd.conf
-</screen>
- </para>
-
- <para>
- Remember to restart slapd after making these changes:
-<screen>
-&rootprompt;<userinput>/etc/init.d/slapd restart</userinput>
-</screen>
- </para>
-
- </sect3>
-
- <sect3>
- <title>Initialize the LDAP Database</title>
-
- <para>
-<indexterm><primary>LDAP database</primary></indexterm>
-<indexterm><primary>account containers</primary></indexterm>
-<indexterm><primary>LDIF file</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
- Before you can add accounts to the LDAP database, you must create the account containers
- that they will be stored in. The following LDIF file should be modified to match your
- needs (DNS entries, and so on):
-<programlisting>
-# Organization for Samba Base
-dn: dc=quenya,dc=org
-objectclass: dcObject
-objectclass: organization
-dc: quenya
-o: Quenya Org Network
-description: The Samba Network LDAP Example
-
-# Organizational Role for Directory Management
-dn: cn=Manager,dc=quenya,dc=org
-objectclass: organizationalRole
-cn: Manager
-description: Directory Manager
-
-# Setting up container for Users OU
-dn: ou=People,dc=quenya,dc=org
-objectclass: top
-objectclass: organizationalUnit
-ou: People
-
-# Setting up admin handle for People OU
-dn: cn=admin,ou=People,dc=quenya,dc=org
-cn: admin
-objectclass: top
-objectclass: organizationalRole
-objectclass: simpleSecurityObject
-userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
-
-# Setting up container for groups
-dn: ou=Groups,dc=quenya,dc=org
-objectclass: top
-objectclass: organizationalUnit
-ou: Groups
-
-# Setting up admin handle for Groups OU
-dn: cn=admin,ou=Groups,dc=quenya,dc=org
-cn: admin
-objectclass: top
-objectclass: organizationalRole
-objectclass: simpleSecurityObject
-userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
-
-# Setting up container for computers
-dn: ou=Computers,dc=quenya,dc=org
-objectclass: top
-objectclass: organizationalUnit
-ou: Computers
-
-# Setting up admin handle for Computers OU
-dn: cn=admin,ou=Computers,dc=quenya,dc=org
-cn: admin
-objectclass: top
-objectclass: organizationalRole
-objectclass: simpleSecurityObject
-userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
-</programlisting>
- </para>
-
- <para>
-<indexterm><primary>userPassword</primary></indexterm>
-<indexterm><primary>slappasswd</primary></indexterm>
- The userPassword shown above should be generated using <command>slappasswd</command>.
- </para>
-
- <para>
-<indexterm><primary>LDIF</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
- The following command will then load the contents of the LDIF file into the LDAP
- database.
-<indexterm><primary>slapadd</primary></indexterm>
-<screen>
-&prompt;<userinput>slapadd -v -l initldap.dif</userinput>
-</screen>
- </para>
-
- <para>
- Do not forget to secure your LDAP server with an adequate access control list
- as well as an admin password.
- </para>
-
- <note><para>
-<indexterm><primary>secrets.tdb</primary></indexterm>
- Before Samba can access the LDAP server, you need to store the LDAP admin password
- in the Samba <filename>secrets.tdb</filename> database by:
-<indexterm><primary>smbpasswd</primary></indexterm>
-<screen>
-&rootprompt;<userinput>smbpasswd -w <replaceable>secret</replaceable></userinput>
-</screen>
- </para></note>
-
- </sect3>
-
- <sect3>
- <title>Configuring Samba</title>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
- The following parameters are available in &smb.conf; only if your version of Samba was built with
- LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The
- best method to verify that Samba was built with LDAP support is:
-<screen>
-&rootprompt; smbd -b | grep LDAP
- HAVE_LDAP_H
- HAVE_LDAP
- HAVE_LDAP_DOMAIN2HOSTLIST
- HAVE_LDAP_INIT
- HAVE_LDAP_INITIALIZE
- HAVE_LDAP_SET_REBIND_PROC
- HAVE_LIBLDAP
- LDAP_SET_REBIND_PROC_ARGS
-</screen>
- If the build of the <command>smbd</command> command you are using does not produce output
- that includes <literal>HAVE_LDAP_H</literal> it is necessary to discover why the LDAP headers
- and libraries were not found during compilation.
- </para>
-
- <para>LDAP-related smb.conf options include these:
- <smbconfblock>
- <smbconfoption name="passdb backend">ldapsam:url</smbconfoption>
- <smbconfoption name="ldap admin dn"/>
- <smbconfoption name="ldap delete dn"/>
- <smbconfoption name="ldap filter"/>
- <smbconfoption name="ldap group suffix"/>
- <smbconfoption name="ldap idmap suffix"/>
- <smbconfoption name="ldap machine suffix"/>
- <smbconfoption name="ldap passwd sync"/>
- <smbconfoption name="ldap ssl"/>
- <smbconfoption name="ldap suffix"/>
- <smbconfoption name="ldap user suffix"/>
- <smbconfoption name="ldap replication sleep"/>
- <smbconfoption name="ldap timeout"/>
- <smbconfoption name="ldap page size"/>
- </smbconfblock>
- </para>
-
- <para>
- These are described in the &smb.conf; man page and so are not repeated here. However, an example
- for use with an LDAP directory is shown in <link linkend="confldapex">the Configuration with LDAP.</link>
- </para>
-
-<example id="confldapex">
-<title>Configuration with LDAP</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="security">user</smbconfoption>
-<smbconfoption name="encrypt passwords">yes</smbconfoption>
-<smbconfoption name="netbios name">MORIA</smbconfoption>
-<smbconfoption name="workgroup">NOLDOR</smbconfoption>
-
-<smbconfcomment>LDAP related parameters:</smbconfcomment>
-
-<smbconfcomment>Define the DN used when binding to the LDAP servers.</smbconfcomment>
-<smbconfcomment>The password for this DN is not stored in smb.conf</smbconfcomment>
-<smbconfcomment>Set it using 'smbpasswd -w secret' to store the</smbconfcomment>
-<smbconfcomment>passphrase in the secrets.tdb file.</smbconfcomment>
-<smbconfcomment>If the "ldap admin dn" value changes, it must be reset.</smbconfcomment>
-<smbconfoption name="ldap admin dn">"cn=Manager,dc=quenya,dc=org"</smbconfoption>
-
-<smbconfcomment>SSL directory connections can be configured by:</smbconfcomment>
-<smbconfcomment>('off', 'start tls', or 'on' (default))</smbconfcomment>
-<smbconfoption name="ldap ssl">start tls</smbconfoption>
-
-<smbconfcomment>syntax: passdb backend = ldapsam:ldap://server-name[:port]</smbconfcomment>
-<smbconfoption name="passdb backend">ldapsam:ldap://frodo.quenya.org</smbconfoption>
-
-<smbconfcomment>smbpasswd -x delete the entire dn-entry</smbconfcomment>
-<smbconfoption name="ldap delete dn">no</smbconfoption>
-
-<smbconfcomment>The machine and user suffix are added to the base suffix</smbconfcomment>
-<smbconfcomment>wrote WITHOUT quotes. NULL suffixes by default</smbconfcomment>
-<smbconfoption name="ldap user suffix">ou=People</smbconfoption>
-<smbconfoption name="ldap group suffix">ou=Groups</smbconfoption>
-<smbconfoption name="ldap machine suffix">ou=Computers</smbconfoption>
-
-<smbconfcomment>Trust UNIX account information in LDAP</smbconfcomment>
-<smbconfcomment> (see the smb.conf man page for details)</smbconfcomment>
-
-<smbconfcomment>Specify the base DN to use when searching the directory</smbconfcomment>
-<smbconfoption name="ldap suffix">dc=quenya,dc=org</smbconfoption>
-</smbconfblock>
-</example>
-
- </sect3>
-
- <sect3>
- <title>Accounts and Groups Management</title>
-
- <para>
- <indexterm><primary>User Management</primary></indexterm>
- <indexterm><primary>User Accounts</primary><secondary>Adding/Deleting</secondary></indexterm>
- Because user accounts are managed through the sambaSamAccount ObjectClass, you should
- modify your existing administration tools to deal with sambaSamAccount attributes.
- </para>
-
- <para>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>/etc/openldap/sldap.conf</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
- Machine accounts are managed with the sambaSamAccount ObjectClass, just
- like user accounts. However, it is up to you to store those accounts
- in a different tree of your LDAP namespace. You should use
- <quote>ou=Groups,dc=quenya,dc=org</quote> to store groups and
- <quote>ou=People,dc=quenya,dc=org</quote> to store users. Just configure your
- NSS and PAM accordingly (usually, in the <filename>/etc/openldap/sldap.conf</filename>
- configuration file).
- </para>
-
- <para>
-<indexterm><primary>POSIX</primary></indexterm>
-<indexterm><primary>posixGroup</primary></indexterm>
-<indexterm><primary>Domain Groups</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
- In Samba, the group management system is based on POSIX
- groups. This means that Samba makes use of the posixGroup ObjectClass.
- For now, there is no NT-like group system management (global and local
- groups). Samba knows only about <constant>Domain Groups</constant>
- and, unlike MS Windows 2000 and Active Directory, Samba does not
- support nested groups.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Security and sambaSamAccount</title>
-
-
- <para>
-<indexterm><primary>sambaSAMAccount</primary></indexterm>
- There are two important points to remember when discussing the security
- of sambaSAMAccount entries in the directory.
- </para>
-
- <itemizedlist>
- <listitem><para><emphasis>Never</emphasis> retrieve the SambaLMPassword or
-<indexterm><primary>SambaNTPassword</primary></indexterm>
- SambaNTPassword attribute values over an unencrypted LDAP session.</para></listitem>
- <listitem><para><emphasis>Never</emphasis> allow non-admin users to
- view the SambaLMPassword or SambaNTPassword attribute values.</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>clear-text</primary></indexterm>
-<indexterm><primary>impersonate</primary></indexterm>
-<indexterm><primary>LM/NT password hashes</primary></indexterm>
- These password hashes are clear-text equivalents and can be used to impersonate
- the user without deriving the original clear-text strings. For more information
- on the details of LM/NT password hashes, refer to <link linkend="passdb">the
- Account Information Database section</link>.
- </para>
-
- <para>
-<indexterm><primary>encrypted session</primary></indexterm>
-<indexterm><primary>StartTLS</primary></indexterm>
-<indexterm><primary>LDAPS</primary></indexterm>
-<indexterm><primary>secure communications</primary></indexterm>
- To remedy the first security issue, the <smbconfoption name="ldap ssl"/> &smb.conf;
- parameter defaults to require an encrypted session (<smbconfoption name="ldap
- ssl">on</smbconfoption>) using the default port of <constant>636</constant> when
- contacting the directory server. When using an OpenLDAP server, it
- is possible to use the StartTLS LDAP extended operation in the place of LDAPS.
- In either case, you are strongly encouraged to use secure communications protocols
- (so do not set <smbconfoption name="ldap ssl">off</smbconfoption>).
- </para>
-
- <para>
-<indexterm><primary>LDAPS</primary></indexterm>
-<indexterm><primary>StartTLS</primary></indexterm>
-<indexterm><primary>LDAPv3</primary></indexterm>
- Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
- extended operation. However, the OpenLDAP library still provides support for
- the older method of securing communication between clients and servers.
- </para>
-
- <para>
-<indexterm><primary>harvesting password hashes</primary></indexterm>
-<indexterm><primary>ACL</primary></indexterm>
-<indexterm><primary>slapd.conf</primary></indexterm>
- The second security precaution is to prevent non-administrative users from
- harvesting password hashes from the directory. This can be done using the
- following ACL in <filename>slapd.conf</filename>:
- </para>
-
-<para>
-<programlisting>
-## allow the "ldap admin dn" access, but deny everyone else
-access to attrs=SambaLMPassword,SambaNTPassword
- by dn="cn=Samba Admin,ou=People,dc=quenya,dc=org" write
- by * none
-</programlisting>
-</para>
-
- </sect3>
-
- <sect3>
- <title>LDAP Special Attributes for sambaSamAccounts</title>
-
- <para> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <link
- linkend="attribobjclPartA">Part A</link>, and <link linkend="attribobjclPartB">Part B</link>.
- </para>
-
- <table frame="all" id="attribobjclPartA">
- <title>Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</title>
- <tgroup cols="2" align="justify">
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <tbody>
- <row><entry><constant>sambaLMPassword</constant></entry><entry>The LanMan password 16-byte hash stored as a character
- representation of a hexadecimal string.</entry></row>
- <row><entry><constant>sambaNTPassword</constant></entry><entry>The NT password 16-byte hash stored as a character
- representation of a hexadecimal string.</entry></row>
- <row><entry><constant>sambaPwdLastSet</constant></entry><entry>The integer time in seconds since 1970 when the
- <constant>sambaLMPassword</constant> and <constant>sambaNTPassword</constant> attributes were last set.
- </entry></row>
-
- <row><entry><constant>sambaAcctFlags</constant></entry><entry>String of 11 characters surrounded by square brackets [ ]
- representing account flags such as U (user), W (workstation), X (no password expiration),
- I (domain trust account), H (home dir required), S (server trust account),
- and D (disabled).</entry></row>
-
- <row><entry><constant>sambaLogonTime</constant></entry><entry>Integer value currently unused.</entry></row>
-
- <row><entry><constant>sambaLogoffTime</constant></entry><entry>Integer value currently unused.</entry></row>
-
- <row><entry><constant>sambaKickoffTime</constant></entry><entry>Specifies the time (UNIX time format) when the user
- will be locked down and cannot login any longer. If this attribute is omitted, then the account will never expire.
- Using this attribute together with shadowExpire of the shadowAccount ObjectClass will enable accounts to
- expire completely on an exact date.</entry></row>
-
- <row><entry><constant>sambaPwdCanChange</constant></entry><entry>Specifies the time (UNIX time format)
- after which the user is allowed to change his password. If this attribute is not set, the user will be free
- to change his password whenever he wants.</entry></row>
-
- <row><entry><constant>sambaPwdMustChange</constant></entry><entry>Specifies the time (UNIX time format) when the user is
- forced to change his password. If this value is set to 0, the user will have to change his password at first login.
- If this attribute is not set, then the password will never expire.</entry></row>
-
- <row><entry><constant>sambaHomeDrive</constant></entry><entry>Specifies the drive letter to which to map the
- UNC path specified by sambaHomePath. The drive letter must be specified in the form <quote>X:</quote>
- where X is the letter of the drive to map. Refer to the <quote>logon drive</quote> parameter in the
- smb.conf(5) man page for more information.</entry></row>
-
- <row><entry><constant>sambaLogonScript</constant></entry><entry>The sambaLogonScript property specifies the path of
- the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
- is relative to the netlogon share. Refer to the <smbconfoption name="logon script"/> parameter in the
- &smb.conf; man page for more information.</entry></row>
-
- <row><entry><constant>sambaProfilePath</constant></entry><entry>Specifies a path to the user's profile.
- This value can be a null string, a local absolute path, or a UNC path. Refer to the
- <smbconfoption name="logon path"/> parameter in the &smb.conf; man page for more information.</entry></row>
-
- <row><entry><constant>sambaHomePath</constant></entry><entry>The sambaHomePath property specifies the path of
- the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies
- a drive letter, sambaHomePath should be a UNC path. The path must be a network
- UNC path of the form <filename>\\server\share\directory</filename>. This value can be a null string.
- Refer to the <command>logon home</command> parameter in the &smb.conf; man page for more information.
- </entry></row>
- </tbody>
- </tgroup></table>
-
-
- <table frame="all" id="attribobjclPartB">
- <title>Attributes in the sambaSamAccount ObjectClass (LDAP), Part B</title>
- <tgroup cols="2" align="justify">
- <colspec align="left"/>
- <colspec align="justify" colwidth="1*"/>
- <tbody>
- <row><entry><constant>sambaUserWorkstations</constant></entry><entry>Here you can give a comma-separated list of machines
- on which the user is allowed to login. You may observe problems when you try to connect to a Samba domain member.
- Because domain members are not in this list, the domain controllers will reject them. Where this attribute is omitted,
- the default implies no restrictions.
- </entry></row>
-
- <row><entry><constant>sambaSID</constant></entry><entry>The security identifier(SID) of the user.
- The Windows equivalent of UNIX UIDs.</entry></row>
-
- <row><entry><constant>sambaPrimaryGroupSID</constant></entry><entry>The security identifier (SID) of the primary group
- of the user.</entry></row>
-
- <row><entry><constant>sambaDomainName</constant></entry><entry>Domain the user is part of.</entry></row>
- </tbody>
- </tgroup></table>
-
-
- <para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
- The majority of these parameters are only used when Samba is acting as a PDC of
- a domain (refer to <link linkend="samba-pdc">Domain Control</link>, for details on
- how to configure Samba as a PDC). The following four attributes
- are only stored with the sambaSamAccount entry if the values are non-default values:
- </para>
-
- <itemizedlist>
-<indexterm><primary>sambaHomePath</primary></indexterm>
-<indexterm><primary>sambaLogonScript</primary></indexterm>
-<indexterm><primary>sambaProfilePath</primary></indexterm>
-<indexterm><primary>sambaHomeDrive</primary></indexterm>
- <listitem><para>sambaHomePath</para></listitem>
- <listitem><para>sambaLogonScript</para></listitem>
- <listitem><para>sambaProfilePath</para></listitem>
- <listitem><para>sambaHomeDrive</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>sambaSamAccount</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>smbHome</primary></indexterm>
- These attributes are only stored with the sambaSamAccount entry if
- the values are non-default values. For example, assume MORIA has now been
- configured as a PDC and that <smbconfoption name="logon home">\\%L\%u</smbconfoption> was defined in
- its &smb.conf; file. When a user named <quote>becky</quote> logs on to the domain,
- the <smbconfoption name="logon home"/> string is expanded to \\MORIA\becky.
- If the smbHome attribute exists in the entry <quote>uid=becky,ou=People,dc=samba,dc=org</quote>,
- this value is used. However, if this attribute does not exist, then the value
- of the <smbconfoption name="logon home"/> parameter is used in its place. Samba
- will only write the attribute value to the directory entry if the value is
- something other than the default (e.g., <filename>\\MOBY\becky</filename>).
- </para>
-
- </sect3>
-
- <sect3>
- <title>Example LDIF Entries for a sambaSamAccount</title>
-
- <para>
- The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass:
-<programlisting>
-dn: uid=guest2, ou=People,dc=quenya,dc=org
-sambaLMPassword: 878D8014606CDA29677A44EFA1353FC7
-sambaPwdMustChange: 2147483647
-sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513
-sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE
-sambaPwdLastSet: 1010179124
-sambaLogonTime: 0
-objectClass: sambaSamAccount
-uid: guest2
-sambaKickoffTime: 2147483647
-sambaAcctFlags: [UX ]
-sambaLogoffTime: 2147483647
-sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006
-sambaPwdCanChange: 0
-</programlisting>
- </para>
-
- <para>
- The following is an LDIF entry for using both the sambaSamAccount and
- posixAccount ObjectClasses:
-<programlisting>
-dn: uid=gcarter, ou=People,dc=quenya,dc=org
-sambaLogonTime: 0
-displayName: Gerald Carter
-sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE
-sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201
-objectClass: posixAccount
-objectClass: sambaSamAccount
-sambaAcctFlags: [UX ]
-userPassword: {crypt}BpM2ej8Rkzogo
-uid: gcarter
-uidNumber: 9000
-cn: Gerald Carter
-loginShell: /bin/bash
-logoffTime: 2147483647
-gidNumber: 100
-sambaKickoffTime: 2147483647
-sambaPwdLastSet: 1010179230
-sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004
-homeDirectory: /home/moria/gcarter
-sambaPwdCanChange: 0
-sambaPwdMustChange: 2147483647
-sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
-</programlisting>
- </para>
-
- </sect3>
-
- <sect3>
- <title>Password Synchronization</title>
-
- <para>
- Samba and later can update the non-Samba (LDAP) password stored with an account. When
- using pam_ldap, this allows changing both UNIX and Windows passwords at once.
- </para>
-
- <para>The <smbconfoption name="ldap passwd sync"/> options can have the values shown in
- <link linkend="ldappwsync">Possible <emphasis>ldap passwd sync</emphasis> Values</link>.</para>
-
- <table frame="all" id="ldappwsync">
- <title>Possible <parameter>ldap passwd sync</parameter> Values</title>
- <tgroup cols="2">
- <colspec align="left" colwidth="1*"/>
- <colspec align="justify" colwidth="4*"/>
- <thead>
- <row><entry align="left">Value</entry><entry align="center">Description</entry></row>
- </thead>
- <tbody>
- <row><entry>yes</entry><entry><para>When the user changes his password, update
- <constant>SambaNTPassword</constant>, <constant>SambaLMPassword</constant>,
- and the <constant>password</constant> fields.</para></entry></row>
-
- <row><entry>no</entry><entry><para>Only update <constant>SambaNTPassword</constant> and
- <constant>SambaLMPassword</constant>.</para></entry></row>
-
- <row><entry>only</entry><entry><para>Only update the LDAP password and let the LDAP server
- worry about the other fields. This option is only available on some LDAP servers and
- only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</para></entry></row>
- </tbody>
- </tgroup>
- </table>
-
-
- <para>More information can be found in the &smb.conf; man page.</para>
-
- </sect3>
-
- <sect3>
- <title>Using OpenLDAP Overlay for Password Synchronization</title>
-
- <para>
- Howard Chu has written a special overlay called <command>smbk5pwd</command>. This tool modifies the
- <literal>SambaNTPassword</literal>, <literal>SambaLMPassword</literal> and <literal>Heimdal</literal>
- hashes in an OpenLDAP entry when an LDAP_EXOP_X_MODIFY_PASSWD operation is performed.
- </para>
-
- <para>
- The overlay is shipped with OpenLDAP-2.3 and can be found in the
- <filename>contrib/slapd-modules/smbk5pwd</filename> subdirectory. This module can also be used with
- OpenLDAP-2.2.
- </para>
-
- </sect3>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
- <sect2>
- <title>Users Cannot Logon</title>
-
- <para><quote>I've installed Samba, but now I can't log on with my UNIX account! </quote></para>
-
- <para>Make sure your user has been added to the current Samba <smbconfoption name="passdb backend"/>.
- Read the <link linkend="acctmgmttools">Account Management Tools</link> for details.</para>
-
- </sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="PolicyMgmt">
-<chapterinfo>
- &author.jht;
- <pubdate>April 3 2003</pubdate>
-</chapterinfo>
-
-<title>System and Account Policies</title>
-
-<para>
-<indexterm><primary>validation</primary></indexterm>
-This chapter summarizes the current state of knowledge derived from personal
-practice and knowledge from Samba mailing list subscribers. Before reproduction
-of posted information, every effort has been made to validate the information given.
-Where additional information was uncovered through this validation, it is provided
-also.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>Group Policies</primary></indexterm>
-<indexterm><primary>users</primary></indexterm>
-<indexterm><primary>groups</primary></indexterm>
-When MS Windows NT 3.5 was introduced, the hot new topic was the ability to implement
-Group Policies for users and groups. Then along came MS Windows NT4 and a few sites
-started to adopt this capability. How do we know that? By the number of <quote>boo-boos</quote>
-(or mistakes) administrators made and then requested help to resolve.
-</para>
-
-<para>
-<indexterm><primary>group policies</primary></indexterm>
-<indexterm><primary>Group Policy Objects</primary><see>GPO</see></indexterm>
-<indexterm><primary>GPOs</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>group policy objects</primary><see>GPOs</see></indexterm>
-By the time that MS Windows 2000 and Active Directory was released, administrators
-got the message: Group Policies are a good thing! They can help reduce administrative
-costs and actually make happier users. But adoption of the true
-potential of MS Windows 200x Active Directory and Group Policy Objects (GPOs) for users
-and machines were picked up on rather slowly. This was obvious from the Samba
-mailing list back in 2000 and 2001 when there were few postings regarding GPOs and
-how to replicate them in a Samba environment.
-</para>
-
-<para>
-<indexterm><primary>exploit opportunities</primary></indexterm>
-Judging by the traffic volume since mid 2002, GPOs have become a standard part of
-the deployment in many sites. This chapter reviews techniques and methods that can
-be used to exploit opportunities for automation of control over user desktops and
-network client workstations.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Creating and Managing System Policies</title>
-
-<para>
-<indexterm><primary>NETLOGON</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>registry</primary></indexterm>
-<indexterm><primary>affect users</primary></indexterm>
-Under MS Windows platforms, particularly those following the release of MS Windows
-NT4 and MS Windows 95, it is possible to create a type of file that would be placed
-in the NETLOGON share of a domain controller. As the client logs onto the network,
-this file is read and the contents initiate changes to the registry of the client
-machine. This file allows changes to be made to those parts of the registry that
-affect users, groups of users, or machines.
-</para>
-
-<para>
-<indexterm><primary>Config.POL</primary></indexterm>
-<indexterm><primary>poledit.exe</primary></indexterm>
-<indexterm><primary>policy editor</primary></indexterm>
-For MS Windows 9x/Me, this file must be called <filename>Config.POL</filename> and may
-be generated using a tool called <filename>poledit.exe</filename>, better known as the
-Policy Editor. The policy editor was provided on the Windows 98 installation CD-ROM, but
-disappeared again with the introduction of MS Windows Me. From
-comments of MS Windows network administrators, it would appear that this tool became
-a part of the MS Windows Me Resource Kit.
-</para>
-
-<para>
-<indexterm><primary>System Policy Editor</primary></indexterm>
-MS Windows NT4 server products include the <emphasis>System Policy Editor</emphasis>
-under <guimenu>Start -> Programs -> Administrative Tools</guimenu>.
-For MS Windows NT4 and later clients, this file must be called <filename>NTConfig.POL</filename>.
-</para>
-
-<para>
-<indexterm><primary>MMC</primary></indexterm>
-New with the introduction of MS Windows 2000 was the Microsoft Management Console
-or MMC. This tool is the new wave in the ever-changing landscape of Microsoft
-methods for management of network access and security. Every new Microsoft product
-or technology seems to make the old rules obsolete and introduces newer and more
-complex tools and methods. To Microsoft's credit, the MMC does appear to
-be a step forward, but improved functionality comes at a great price.
-</para>
-
-<para>
-<indexterm><primary>network policies</primary></indexterm>
-<indexterm><primary>system policies</primary></indexterm>
-<indexterm><primary>Profiles</primary></indexterm>
-<indexterm><primary>Policies</primary></indexterm>
-Before embarking on the configuration of network and system policies, it is highly
-advisable to read the documentation available from Microsoft's Web site regarding
-<ulink url="http://www.microsoft.com/ntserver/techresources/management/prof_policies.asp">
-Implementing Profiles and Policies in Windows NT 4.0</ulink>.
-There are a large number of documents in addition to this old one that should also
-be read and understood. Try searching on the Microsoft Web site for <quote>Group Policies</quote>.
-</para>
-
-<para>
-What follows is a brief discussion with some helpful notes. The information provided
-here is incomplete &smbmdash; you are warned.
-</para>
-
- <sect2>
- <title>Windows 9x/ME Policies</title>
-
- <para>
-<indexterm><primary>Group Policy Editor</primary></indexterm>
-<indexterm><primary>tools\reskit\netadmin\poledit</primary></indexterm>
- You need the Windows 98 Group Policy Editor to set up Group Profiles under Windows 9x/Me.
- It can be found on the original full-product Windows 98 installation CD-ROM under
- <filename>tools\reskit\netadmin\poledit</filename>. Install this using the
- Add/Remove Programs facility, and then click on <guiicon>Have Disk</guiicon>.
- </para>
-
-
- <para>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-<indexterm><primary>Config.POL</primary></indexterm>
- Use the Group Policy Editor to create a policy file that specifies the location of
- user profiles and/or <filename>My Documents</filename>, and so on. Then save these
- settings in a file called <filename>Config.POL</filename> that needs to be placed in the
- root of the <smbconfsection name="[NETLOGON]"/> share. If Windows 98 is configured to log onto
- the Samba domain, it will automatically read this file and update the Windows 9x/Me registry
- of the machine as it logs on.
- </para>
-
- <para>
- Further details are covered in the Windows 98 Resource Kit documentation.
- </para>
-
- <para>
-<indexterm><primary>registry</primary></indexterm>
- If you do not take the correct steps, then every so often Windows 9x/Me will check the
- integrity of the registry and restore its settings from the backup
- copy of the registry it stores on each Windows 9x/Me machine. So, you will
- occasionally notice things changing back to the original settings.
- </para>
-
- <para>
-<indexterm><primary>grouppol.inf</primary></indexterm>
-<indexterm><primary>Group Policy</primary></indexterm>
- Install the Group Policy handler for Windows 9x/Me to pick up Group Policies. Look on the
- Windows 98 CD-ROM in <filename>\tools\reskit\netadmin\poledit</filename>.
- Install Group Policies on a Windows 9x/Me client by double-clicking on
- <filename>grouppol.inf</filename>. Log off and on again a couple of times and see
- if Windows 98 picks up Group Policies. Unfortunately, this needs to be done on every
- Windows 9x/Me machine that uses Group Policies.
- </para>
-
- </sect2>
- <sect2>
- <title>Windows NT4-Style Policy Files</title>
-
- <para>
-<indexterm><primary>ntconfig.pol</primary></indexterm>
-<indexterm><primary>poledit.exe</primary></indexterm>
-<indexterm><primary>Policy Editor</primary></indexterm>
-<indexterm><primary>domain policies</primary></indexterm>
- To create or edit <filename>ntconfig.pol</filename>, you must use the NT Server
- Policy Editor, <command>poledit.exe</command>, which is included with NT4 Server
- but not with NT workstation. There is a Policy Editor on an NT4
- Workstation but it is not suitable for creating domain policies.
- Furthermore, although the Windows 95 Policy Editor can be installed on an NT4
- workstation/server, it will not work with NT clients. However, the files from
- the NT Server will run happily enough on an NT4 workstation.
- </para>
-
- <para>
-<indexterm><primary>poledit.exe</primary></indexterm>
-<indexterm><primary>common.adm</primary></indexterm>
-<indexterm><primary>winnt.adm</primary></indexterm>
-<indexterm><primary>c:\winnt\inf</primary></indexterm>
- You need <filename>poledit.exe</filename>, <filename>common.adm</filename>, and <filename>winnt.adm</filename>.
- It is convenient to put the two <filename>*.adm</filename> files in the <filename>c:\winnt\inf</filename>
- directory, which is where the binary will look for them unless told otherwise. This
- directory is normally <quote>hidden.</quote>
- </para>
-
- <para>
-<indexterm><primary>Policy Editor</primary></indexterm>
-<indexterm><primary>Nt4sp6ai.exe</primary></indexterm>
-<indexterm><primary>poledit.exe</primary></indexterm>
-<indexterm><primary>Zero Administration Kit</primary></indexterm>
- The Windows NT Policy Editor is also included with the Service Pack 3 (and
- later) for Windows NT 4.0. Extract the files using <command>servicepackname /x</command>
- &smbmdash; that's <command>Nt4sp6ai.exe /x</command> for Service Pack 6a. The Policy Editor,
- <command>poledit.exe</command>, and the associated template files (*.adm) should
- be extracted as well. It is also possible to download the policy template
- files for Office97 and get a copy of the Policy Editor. Another possible
- location is with the Zero Administration Kit available for download from Microsoft.
- </para>
-
- <sect3>
- <title>Registry Spoiling</title>
-
- <para>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-<indexterm><primary>HKEY_LOCAL_MACHINE</primary></indexterm>
- With NT4-style registry-based policy changes, a large number of settings are not
- automatically reversed as the user logs off. The settings that were in the
- <filename>NTConfig.POL</filename> file were applied to the client machine registry and apply to the
- hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
- as tattooing. It can have serious consequences downstream, and the administrator must
- be extremely careful not to lock out the ability to manage the machine at a later date.
- </para>
-
- </sect3>
- </sect2>
- <sect2>
- <title>MS Windows 200x/XP Professional Policies</title>
-
- <para>
-<indexterm><primary>registry</primary></indexterm>
- Windows NT4 system policies allow the setting of registry parameters specific to
- users, groups, and computers (client workstations) that are members of the NT4-style
- domain. Such policy files will work with MS Windows 200x/XP clients also.
- </para>
-
- <para>
- New to MS Windows 2000, Microsoft recently introduced a style of Group Policy that confers
- a superset of capabilities compared with NT4-style policies. Obviously, the tool used
- to create them is different, and the mechanism for implementing them is much improved.
- </para>
-
- <para>
- <indexterm><primary>GPOs</primary></indexterm>
-<indexterm><primary>Administrative Templates</primary></indexterm>
- The older NT4-style registry-based policies are known as <emphasis>Administrative Templates</emphasis>
- in MS Windows 2000/XP GPOs. The latter includes the ability to set various security
- configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
- users desktop (including the location of <filename>My Documents</filename> files, as
- well as intrinsics of where menu items will appear in the Start menu). An additional new
- feature is the ability to make available particular software Windows applications to particular
- users and/or groups.
- </para>
-
- <para>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-<indexterm><primary>NETLOGON</primary></indexterm>
-<indexterm><primary>local registry values</primary></indexterm>
- Remember, NT4 policy files are named <filename>NTConfig.POL</filename> and are stored in the root
- of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username and password
- and selects the domain name to which the logon will attempt to take place. During the logon process,
- the client machine reads the <filename>NTConfig.POL</filename> file from the NETLOGON share on
- the authenticating server and modifies the local registry values according to the settings in this file.
- </para>
-
- <para>
-<indexterm><primary>SYSVOL</primary></indexterm>
-<indexterm><primary>NETLOGON</primary></indexterm>
-<indexterm><primary>replicated</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>domain controllers</primary></indexterm>
-<indexterm><primary>Group Policy Container</primary><see>GPC</see></indexterm>
-<indexterm><primary>Group Policy Template</primary><see>GPT</see></indexterm>
-<indexterm><primary>replicated SYSVOL</primary></indexterm>
- Windows 200x GPOs are feature-rich. They are not stored in the NETLOGON share, but rather part of
- a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
- in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
- Directory domain controllers. The part that is stored in the Active Directory itself is called the
- Group Policy Container (GPC), and the part that is stored in the replicated share called SYSVOL is
- known as the Group Policy Template (GPT).
- </para>
-
- <para>
-<indexterm><primary>GPOs</primary></indexterm>
- With NT4 clients, the policy file is read and executed only as each user logs onto the network.
- MS Windows 200x policies are much more complex &smbmdash; GPOs are processed and applied at client machine
- startup (machine specific part), and when the user logs onto the network, the user-specific part
- is applied. In MS Windows 200x-style policy management, each machine and/or user may be subject
- to any number of concurrently applicable (and applied) policy sets (GPOs). Active Directory allows
- the administrator to also set filters over the policy settings. No such equivalent capability
- exists with NT4-style policy files.
- </para>
-
- <sect3>
- <title>Administration of Windows 200x/XP Policies</title>
-
- <para>
- <indexterm><primary>GPOs</primary></indexterm>
- <indexterm><primary>System Policy Editor</primary></indexterm>
-<indexterm><primary>poledit.exe</primary></indexterm>
-<indexterm><primary>MMC snap-in</primary></indexterm>
-<indexterm><primary>Poledit</primary></indexterm>
- Instead of using the tool called <application>the System Policy Editor</application>, commonly called Poledit (from the
- executable name <command>poledit.exe</command>), <acronym>GPOs</acronym> are created and managed using a
- <application>Microsoft Management Console</application> <acronym>(MMC)</acronym> snap-in as follows:</para>
- <procedure>
- <step><para>
- Go to the Windows 200x/XP menu <guimenu>Start->Programs->Administrative Tools</guimenu>
- and select the MMC snap-in called <guimenuitem>Active Directory Users and Computers</guimenuitem>
- </para></step>
-
- <step><para>
-<indexterm><primary>organizational unit</primary><see>OU</see></indexterm>
- Select the domain or organizational unit (OU) that you wish to manage, then right-click
- to open the context menu for that object, and select the <guibutton>Properties</guibutton>.
- </para></step>
-
- <step><para>
- Left-click on the <guilabel>Group Policy</guilabel> tab, then
- left-click on the New tab. Type a name
- for the new policy you will create.
- </para></step>
-
- <step><para>
- Left-click on the <guilabel>Edit</guilabel> tab to commence the steps needed to create the GPO.
- </para></step>
- </procedure>
-
- <para>
- All policy configuration options are controlled through the use of policy administrative
- templates. These files have an .adm extension, both in NT4 as well as in Windows 200x/XP.
- Beware, however, the .adm files are not interchangeable across NT4 and Windows 200x.
- The latter introduces many new features as well as extended definition capabilities. It is
- well beyond the scope of this documentation to explain how to program .adm files; for that,
- refer to the Microsoft Windows Resource Kit for your particular
- version of MS Windows.
- </para>
-
- <note>
- <para>
-<indexterm><primary>gpolmig.exe</primary></indexterm>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-<indexterm><primary>resource kit</primary></indexterm>
- The MS Windows 2000 Resource Kit contains a tool called <command>gpolmig.exe</command>. This tool can be used
- to migrate an NT4 <filename>NTConfig.POL</filename> file into a Windows 200x style GPO. Be VERY careful how you
- use this powerful tool. Please refer to the resource kit manuals for specific usage information.
- </para>
- </note>
-
- </sect3>
-
- <sect3>
- <title>Custom System Policy Templates</title>
-
- <para>
- Over the past year, there has been a bit of talk regarding the creation of customized
- templates for the Windows Sytem Policy Editor. A recent announcement on the Samba mailing
- list is worthy of mention.
- </para>
-
- <para>
- Mike Petersen has announced the availability of a template file he has created. This custom System Policy
- Editor Template will allow you to successfully control Microsoft Windows workstations from an SMB server, such
- as Samba. This template has been tested on a few networks, although if you find any problems with any of these
- policies, or have any ideas for additional policies, let me know at mailto:mgpeter@pcc-services.com. This
- Template includes many policies for Windows XP to allow it to behave better in a professional environment.
- </para>
-
- <para>
- For further information please see the <ulink
- url="http://www.pcc-services.com/custom_poledit.html">Petersen</ulink> Computer Consulting web site. There is
- a download link for the template file.
- </para>
-
- </sect3>
- </sect2>
-</sect1>
-
-<sect1>
-<title>Managing Account/User Policies</title>
-
-<para>
-<indexterm><primary>Policies</primary></indexterm>
-<indexterm><primary>policy file </primary></indexterm>
-<indexterm><primary>registry settings</primary></indexterm>
-Policies can define a specific user's settings or the settings for a group of users. The resulting
-policy file contains the registry settings for all users, groups, and computers that will be using
-the policy file. Separate policy files for each user, group, or computer are not necessary.
-</para>
-
-<para>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-If you create a policy that will be automatically downloaded from validating domain controllers,
-you should name the file <filename>NTConfig.POL</filename>. As system administrator, you have the option of renaming the
-policy file and, by modifying the Windows NT-based workstation, directing the computer to update
-the policy from a manual path. You can do this by either manually changing the registry or by using
-the System Policy Editor. This can even be a local path such that each machine has its own policy file,
-but if a change is necessary to all machines, it must be made individually to each workstation.
-</para>
-
-<para>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-<indexterm><primary>NETLOGON</primary></indexterm>
-When a Windows NT4/200x/XP machine logs onto the network, the client looks in the NETLOGON share on
-the authenticating domain controller for the presence of the <filename>NTConfig.POL</filename> file. If one exists, it is
-downloaded, parsed, and then applied to the user's part of the registry.
-</para>
-
-<para>
-<indexterm><primary>GPOs</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-<indexterm><primary>NT4 style policy updates</primary></indexterm>
-MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally
-acquire policy settings through GPOs that are defined and stored in Active Directory
-itself. The key benefit of using AD GPOs is that they impose no registry <emphasis>spoiling</emphasis> effect.
-This has considerable advantage compared with the use of <filename>NTConfig.POL</filename> (NT4) style policy updates.
-</para>
-
-<para>
-<indexterm><primary>account restrictions</primary></indexterm>
-<indexterm><primary>Common restrictions</primary></indexterm>
-In addition to user access controls that may be imposed or applied via system and/or group policies
-in a manner that works in conjunction with user profiles, the user management environment under
-MS Windows NT4/200x/XP allows per-domain as well as per-user account restrictions to be applied.
-Common restrictions that are frequently used include:
-</para>
-
-<para>
-<indexterm><primary>Account Controls</primary></indexterm>
-<itemizedlist>
- <listitem><para>Logon hours</para></listitem>
- <listitem><para>Password aging</para></listitem>
- <listitem><para>Permitted logon from certain machines only</para></listitem>
- <listitem><para>Account type (local or global)</para></listitem>
- <listitem><para>User rights</para></listitem>
-</itemizedlist>
-</para>
-
-<para>
-<indexterm><primary>Domain User Manager</primary></indexterm>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-Samba-3.0.20 does not yet implement all account controls that are common to MS Windows NT4/200x/XP.
-While it is possible to set many controls using the Domain User Manager for MS Windows NT4, only password
-expiry is functional today. Most of the remaining controls at this time have only stub routines
-that may eventually be completed to provide actual control. Do not be misled by the fact that a
-parameter can be set using the NT4 Domain User Manager or in the <filename>NTConfig.POL</filename>.
-</para>
-
-</sect1>
-<sect1>
-<title>Management Tools</title>
-
-<para>
-Anyone who wishes to create or manage Group Policies will need to be familiar with a number of tools.
-The following sections describe a few key tools that will help you to create a low-maintenance user
-environment.
-</para>
-
- <sect2>
- <title>Samba Editreg Toolset</title>
-
- <para>
- <indexterm><primary>editreg</primary></indexterm>
- <indexterm><primary>NTUser.DAT</primary></indexterm>
- <indexterm><primary>NTConfig.POL</primary></indexterm>
- A new tool called <command>editreg</command> is under development. This tool can be used
- to edit registry files (called <filename>NTUser.DAT</filename>) that are stored in user
- and group profiles. <filename>NTConfig.POL</filename> files have the same structure as the
- <filename>NTUser.DAT</filename> file and can be edited using this tool. <command>editreg</command>
- is being built with the intent to enable <filename>NTConfig.POL</filename> files to be saved in text format and to
- permit the building of new <filename>NTConfig.POL</filename> files with extended capabilities. It is proving difficult
- to realize this capability, so do not be surprised if this feature does not materialize. Formal
- capabilities will be announced at the time that this tool is released for production use.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Windows NT4/200x</title>
-
- <para>
-<indexterm><primary>regedt32.exe</primary></indexterm>
-<indexterm><primary>Group Policy Editor</primary></indexterm>
-<indexterm><primary>MMC</primary></indexterm>
- The tools that may be used to configure these types of controls from the MS Windows environment are
- the NT4 User Manager for Domains, the NT4 System and Group Policy Editor, and the Registry Editor (regedt32.exe).
- Under MS Windows 200x/XP, this is done using the MMC with appropriate
- <quote>snap-ins,</quote> the registry editor, and potentially also the NT4 System and Group Policy Editor.
- </para>
- </sect2>
-
- <sect2>
- <title>Samba PDC</title>
-
- <para>
-<indexterm><primary>smbpasswd</primary></indexterm>
-<indexterm><primary>pdbedit</primary></indexterm>
-<indexterm><primary>NET</primary></indexterm>
-<indexterm><primary>rpcclient</primary></indexterm>
- With a Samba domain controller, the new tools for managing user account and policy information include:
- <command>smbpasswd</command>, <command>pdbedit</command>, <command>net</command>, and <command>rpcclient</command>.
- The administrator should read the man pages for these tools and become familiar with their use.
- </para>
-
- </sect2>
-</sect1>
-
-<sect1>
-<title>System Startup and Logon Processing Overview</title>
-
-<para>
-The following attempts to document the order of processing the system and user policies following a system
-reboot and as part of the user logon:
-</para>
-
-<orderedlist>
- <listitem><para>
-<indexterm><primary>Remote Procedure Call System Service</primary><see>RPCSS</see></indexterm>
-<indexterm><primary>multiple universal naming convention provider</primary><see>MUP</see></indexterm>
- Network starts, then Remote Procedure Call System Service (RPCSS) and multiple universal naming
- convention provider (MUP) start.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>GPOs</primary></indexterm>
- Where Active Directory is involved, an ordered list of GPOs is downloaded
- and applied. The list may include GPOs that:
-<itemizedlist>
- <listitem><para>Apply to the location of machines in a directory.</para></listitem>
- <listitem><para>Apply only when settings have changed.</para></listitem>
- <listitem><para>Depend on configuration of the scope of applicability: local,
- site, domain, organizational unit, and so on.</para></listitem>
-</itemizedlist>
- No desktop user interface is presented until the above have been processed.
- </para></listitem>
-
- <listitem><para>
- Execution of startup scripts (hidden and synchronous by default).
- </para></listitem>
-
- <listitem><para>
- A keyboard action to effect start of logon (Ctrl-Alt-Del).
- </para></listitem>
-
- <listitem><para>
- User credentials are validated, user profile is loaded (depends on policy settings).
- </para></listitem>
-
- <listitem><para>
- An ordered list of user GPOs is obtained. The list contents depends on what is configured in respect of:
-
-<itemizedlist>
- <listitem><para>Is the user a domain member, thus subject to particular policies?</para></listitem>
- <listitem><para>Loopback enablement, and the state of the loopback policy (merge or replace).</para></listitem>
- <listitem><para>Location of the Active Directory itself.</para></listitem>
- <listitem><para>Has the list of GPOs changed? No processing is needed if not changed.</para></listitem>
-</itemizedlist>
- </para></listitem>
-
- <listitem><para>
- User policies are applied from Active Directory. Note: There are several types.
- </para></listitem>
-
- <listitem><para>
- Logon scripts are run. New to Windows 200x and Active Directory, logon scripts may be obtained based on GPOs
- (hidden and executed synchronously). NT4-style logon scripts are then run in a normal
- window.
- </para></listitem>
-
- <listitem><para>
- The user interface as determined from the GPOs is presented. Note: In a Samba domain (like an NT4
- domain), machine (system) policies are applied at startup; user policies are applied at logon.
- </para></listitem>
-</orderedlist>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-Policy-related problems can be quite difficult to diagnose and even more difficult to rectify. The following
-collection demonstrates only basic issues.
-</para>
-
-<sect2>
-<title>Policy Does Not Work</title>
-
-<para>
-<quote>We have created the <filename>Config.POL</filename> file and put it in the <emphasis>NETLOGON</emphasis> share.
-It has made no difference to our Win XP Pro machines, they just do not see it. It worked fine with Win 98 but does not
-work any longer since we upgraded to Win XP Pro. Any hints?</quote>
-</para>
-
-<para>
-Policy files are not portable between Windows 9x/Me and MS Windows NT4/200x/XP-based platforms. You need to
-use the NT4 Group Policy Editor to create a file called <filename>NTConfig.POL</filename> so it is in the
-correct format for your MS Windows XP Pro clients.
-</para>
-
-</sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="classicalprinting">
-
-<chapterinfo>
- <author>
- <firstname>Kurt</firstname><surname>Pfeifle</surname>
- <affiliation>
- <orgname>Danka Deutschland GmbH</orgname>
- <address><email>kpfeifle@danka.de</email></address>
- </affiliation>
- </author>
- &author.jerry;
- &author.jht;
- <pubdate>May 31, 2003</pubdate>
-</chapterinfo>
-
-<title>Classical Printing Support</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>mission-critical</primary></indexterm>
-Printing is often a mission-critical service for the users. Samba can provide this service reliably and
-seamlessly for a client network consisting of Windows workstations.
-</para>
-
-<para>
-<indexterm><primary>print service</primary></indexterm>
-<indexterm><primary>domain member server</primary></indexterm>
-<indexterm><primary>standalone server</primary></indexterm>
-<indexterm><primary>file serving</primary></indexterm>
-<indexterm><primary>dedicated print server</primary></indexterm>
-<indexterm><primary>print server</primary></indexterm>
-<indexterm><primary>printing support</primary></indexterm>
-<indexterm><primary>Point'n'Print</primary></indexterm>
-<indexterm><primary>Add Printer Wizard</primary></indexterm>
-<indexterm><primary>upload drivers</primary></indexterm>
-<indexterm><primary>manage drivers</primary></indexterm>
-<indexterm><primary>install drivers</primary></indexterm>
-<indexterm><primary>print accounting</primary></indexterm>
-<indexterm><primary>Common UNIX Printing System</primary><see>CUPS</see></indexterm>
-A Samba print service may be run on a standalone or domain member server, side by side with file serving
-functions, or on a dedicated print server. It can be made as tightly or as loosely secured as needs dictate.
-Configurations may be simple or complex. Available authentication schemes are essentially the same as
-described for file services in previous chapters. Overall, Samba's printing support is now able to replace an
-NT or Windows 2000 print server full-square, with additional benefits in many cases. Clients may download and
-install drivers and printers through their familiar <literal>Point'n'Print</literal> mechanism. Printer
-installations executed by <literal>Logon Scripts</literal> are no problem. Administrators can upload and manage
-drivers to be used by clients through the familiar <literal>Add Printer Wizard</literal>. As an additional
-benefit, driver and printer management may be run from the command line or through scripts, making it more
-efficient in case of large numbers of printers. If a central accounting of print jobs (tracking every single
-page and supplying the raw data for all sorts of statistical reports) is required, this function is best
-supported by the newer Common UNIX Printing System (CUPS) as the print subsystem underneath the Samba hood.
-</para>
-
-<para>
-<indexterm><primary>BSD</primary></indexterm>
-<indexterm><primary>CUPS</primary></indexterm>
-This chapter outlines the fundamentals of Samba printing as implemented by the more traditional UNIX
-BSD- and System V-style printing systems. Much of the information in this chapter applies also to CUPS. If
-you use CUPS, you may be tempted to jump to the next chapter, but you will certainly miss a few things if you
-do. For further information refer to <link linkend="CUPS-printing">CUPS Printing Support</link>.
-</para>
-
-<note>
-<para>
-<indexterm><primary>Windows XP Professional</primary></indexterm>
-<indexterm><primary>Windows 200x/XP</primary></indexterm>
-<indexterm><primary>Windows NT4</primary></indexterm>
-Most of the following examples have been verified on Windows XP Professional clients. Where this document
-describes the responses to commands given, bear in mind that Windows 200x/XP clients are quite similar but may
-differ in minor details. Windows NT4 is somewhat different again.
-</para>
-</note>
-
-</sect1>
-
-<sect1>
-<title>Technical Introduction</title>
-
-<para>
-<indexterm><primary>printing support</primary></indexterm>
-<indexterm><primary>print subsystem</primary></indexterm>
-<indexterm><primary>printing system</primary></indexterm>
-Samba's printing support always relies on the installed print subsystem of the UNIX OS it runs on. Samba is a
-<literal>middleman.</literal> It takes print files from Windows (or other SMB) clients and passes them to the real
-printing system for further processing; therefore, it needs to communicate with both sides: the Windows print
-clients and the UNIX printing system. Hence, we must differentiate between the various client OS types, each
-of which behave differently, as well as the various UNIX print subsystems, which themselves have different
-features and are accessed differently.
-</para>
-
-<para>
-<indexterm><primary>UNIX printing</primary></indexterm>
-<indexterm><primary>CUPS</primary></indexterm>
-This chapter deals with the traditional way of UNIX printing. The next chapter covers in great detail the more
-modern CUPS.
-</para>
-
-<important><para>
-<indexterm><primary>CUPS</primary></indexterm>
-CUPS users, be warned: do not just jump on to the next chapter. You might miss important information only found here!
-</para></important>
-
-<para>
-<indexterm><primary>print configuration</primary></indexterm>
-<indexterm><primary>problematic print</primary></indexterm>
-<indexterm><primary>print processing</primary></indexterm>
-<indexterm><primary>print filtering</primary></indexterm>
-It is apparent from postings on the Samba mailing list that print configuration is one of the most problematic
-aspects of Samba administration today. Many new Samba administrators have the impression that Samba performs
-some sort of print processing. Rest assured, Samba does not perform any type of print processing. It does not
-do any form of print filtering.
-</para>
-
-<para>
-<indexterm><primary>data stream</primary></indexterm>
-<indexterm><primary>local spool area</primary></indexterm>
-<indexterm><primary>spooled file</primary></indexterm>
-<indexterm><primary>local system printing</primary></indexterm>
-Samba obtains from its clients a data stream (print job) that it spools to a local spool area. When the entire
-print job has been received, Samba invokes a local UNIX/Linux print command and passes the spooled file to it.
-It is up to the local system printing subsystems to correctly process the print job and to submit it to the
-printer.
-</para>
-
-<sect2>
-<title>Client to Samba Print Job Processing</title>
-
-<para>
-Successful printing from a Windows client via a Samba print server to a UNIX
-printer involves six (potentially seven) stages:
-</para>
-
-<orderedlist>
- <listitem><para>Windows opens a connection to the printer share.</para></listitem>
-
- <listitem><para>Samba must authenticate the user.</para></listitem>
-
- <listitem><para>Windows sends a copy of the print file over the network
- into Samba's spooling area.</para></listitem>
-
- <listitem><para>Windows closes the connection.</para></listitem>
-
- <listitem><para>Samba invokes the print command to hand the file over
- to the UNIX print subsystem's spooling area.</para></listitem>
-
- <listitem><para>The UNIX print subsystem processes the print job.</para></listitem>
-
- <listitem><para>The print file may need to be explicitly deleted
- from the Samba spooling area. This item depends on your print spooler
- configuration settings.</para></listitem>
-</orderedlist>
-</sect2>
-
-<sect2>
-<title>Printing-Related Configuration Parameters</title>
-
-<para>
-<indexterm><primary>global-level</primary></indexterm>
-<indexterm><primary>service-level</primary></indexterm>
-<indexterm><primary>printing behavior</primary></indexterm>
-There are a number of configuration parameters to control Samba's printing behavior. Please refer to the man
-page for &smb.conf; for an overview of these. As with other parameters, there are global-level (tagged with a
-<emphasis>G</emphasis> in the listings) and service-level (<emphasis>S</emphasis>) parameters.
-</para>
-
-<variablelist>
- <varlistentry><term>Global Parameters</term>
- <listitem><para> These <emphasis>may not</emphasis> go into
- individual share definitions. If they go in by error,
- the <command>testparm</command> utility can discover this
- (if you run it) and tell you so.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Service-Level Parameters</term>
- <listitem><para> These may be specified in the
- <smbconfsection name="[global]"/> section of &smb.conf;.
- In this case they define the default behavior of all individual
- or service-level shares (provided they do not have a different
- setting defined for the same parameter, thus overriding the
- global default).
- </para></listitem>
- </varlistentry>
-</variablelist>
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Simple Print Configuration</title>
-
-<para>
-<indexterm><primary>BSD Printing</primary></indexterm>
-<indexterm><primary>simple printing</primary></indexterm>
-<indexterm><primary>enables clients to print</primary></indexterm>
-<indexterm><primary>print environment</primary></indexterm>
-<link linkend="simpleprc">Simple Configuration with BSD Printing</link> shows a simple printing configuration.
-If you compare this with your own, you may find additional parameters that have been preconfigured by your OS
-vendor. Following is a discussion and explanation of the parameters. This example does not use many
-parameters. However, in many environments these are enough to provide a valid &smb.conf; file that enables
-all clients to print.
-</para>
-
-<example id="simpleprc">
-<title>Simple Configuration with BSD Printing</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="printing">bsd</smbconfoption>
-<smbconfoption name="load printers">yes</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="printable">yes</smbconfoption>
-<smbconfoption name="public">yes</smbconfoption>
-<smbconfoption name="writable">no</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>testparm</primary></indexterm>
-<indexterm><primary>misconfigured settings</primary></indexterm>
-<indexterm><primary>pager program</primary></indexterm>
-This is only an example configuration. Samba assigns default values to all configuration parameters. The
-defaults are conservative and sensible. When a parameter is specified in the &smb.conf; file, this overwrites
-the default value. The <command>testparm</command> utility when run as root is capable of reporting all
-settings, both default as well as &smb.conf; file settings. <command>Testparm</command> gives warnings for all
-misconfigured settings. The complete output is easily 360 lines and more, so you may want to pipe it through a
-pager program.
-</para>
-
-<para>
-<indexterm><primary>configuration syntax</primary></indexterm>
-<indexterm><primary>syntax tolerates spelling errors</primary></indexterm>
-<indexterm><primary>case-insensitive</primary></indexterm>
-The syntax for the configuration file is easy to grasp. You should know that is not very picky about its
-syntax. As has been explained elsewhere in this book, Samba tolerates some spelling errors (such as
-<smbconfoption name="browseable"/> instead of <smbconfoption name="browsable"/>), and spelling is
-case-insensitive. It is permissible to use <parameter>Yes/No</parameter> or <parameter>True/False</parameter>
-for Boolean settings. Lists of names may be separated by commas, spaces, or tabs.
-</para>
-
-<sect2>
-<title>Verifying Configuration with <command>testparm</command></title>
-
-<para>
-<indexterm><primary>printing-related settings</primary></indexterm>
-<indexterm><primary>lp</primary></indexterm>
-<indexterm><primary>print</primary></indexterm>
-<indexterm><primary>spool</primary></indexterm>
-<indexterm><primary>driver</primary></indexterm>
-<indexterm><primary>ports</primary></indexterm>
-<indexterm><primary>testparm</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>print configuration</primary></indexterm>
-<indexterm><primary>printer shares </primary></indexterm>
-<indexterm><primary>spooling path</primary></indexterm>
-To see all (or at least most) printing-related settings in Samba, including the implicitly used ones, try the
-command outlined below. This command greps for all occurrences of <constant>lp</constant>,
-<constant>print</constant>, <constant>spool</constant>, <constant>driver</constant>,
-<constant>ports</constant>, and <constant>[</constant> in <command>testparm</command>'s output. This provides
-a convenient overview of the running <command>smbd</command> print configuration. This command does not show
-individually created printer shares or the spooling paths they may use. Here is the output of my Samba setup,
-with settings shown in <link linkend="simpleprc">the example above</link>:
-<screen>
-&rootprompt;<userinput>testparm -s -v | egrep "(lp|print|spool|driver|ports|\[)"</userinput>
- Load smb config files from /etc/samba/smb.conf
- Processing section "[homes]"
- Processing section "[printers]"
-
- [global]
- smb ports = 139 445
- lpq cache time = 10
- load printers = Yes
- printcap name = /etc/printcap
- disable spoolss = No
- enumports command =
- addprinter command =
- deleteprinter command =
- show add printer wizard = Yes
- os2 driver map =
- min print space = 0
- max print jobs = 1000
- printable = No
- printing = bsd
- print command = lpr -r -P'%p' %s
- lpq command = lpq -P'%p'
- lprm command = lprm -P'%p' %j
- lppause command =
- lpresume command =
- printer name =
- use client driver = No
-
- [homes]
-
- [printers]
- path = /var/spool/samba
- printable = Yes
-</screen>
-</para>
-
-<para>
-You can easily verify which settings were implicitly added by Samba's default behavior. <emphasis>Remember: it
-may be important in your future dealings with Samba.</emphasis>
-</para>
-
-<note><para>
-The <command>testparm</command> in Samba-3 behaves differently from that in 2.2.x: used without the
-<quote>-v</quote> switch, it only shows you the settings actually written into! To see the complete
-configuration used, add the <quote>-v</quote> parameter to testparm.
-</para></note>
-
-</sect2>
-
-<sect2>
-<title>Rapid Configuration Validation</title>
-
-<para>
-<indexterm><primary>troubleshoot</primary></indexterm>
-<indexterm><primary>testparm</primary></indexterm>
-<indexterm><primary>parameters</primary></indexterm>
-<indexterm><primary>verify</primary></indexterm>
-Should you need to troubleshoot at any stage, please always come back to this point first and verify if
-<command>testparm</command> shows the parameters you expect. To give you a warning from personal experience,
-try to just comment out the <smbconfoption name="load printers"/> parameter. If your 2.2.x system behaves like
-mine, you'll see this:
-</para>
-
-<para><screen>
-&rootprompt;grep "load printers" /etc/samba/smb.conf
- # load printers = Yes
- # This setting is commented out!!
-
-&rootprompt;testparm -v /etc/samba/smb.conf | egrep "(load printers)"
- load printers = Yes
-</screen></para>
-
-<para>
-<indexterm><primary>commenting out setting</primary></indexterm>
-<indexterm><primary>publishing printers</primary></indexterm>
-I assumed that commenting out of this setting should prevent Samba from
-publishing my printers, but it still did. It took some time to figure out
-the reason. But I am no longer fooled ... at least not by this.
-<screen>
-&rootprompt;<userinput>grep -A1 "load printers" /etc/samba/smb.conf</userinput>
- load printers = No
- # The above setting is what I want!
- # load printers = Yes
- # This setting is commented out!
-
-&rootprompt;<userinput>testparm -s -v smb.conf.simpleprinting | egrep "(load printers)"</userinput>
- load printers = No
-</screen></para>
-
-<para>
-<indexterm><primary>explicitly set</primary></indexterm>
-Only when the parameter is explicitly set to <smbconfoption name="load printers">No</smbconfoption> would
-Samba conform with my intentions. So, my strong advice is:
-</para>
-
-<itemizedlist>
- <listitem><para>Never rely on commented-out parameters.</para></listitem>
-
- <listitem><para>Always set parameters explicitly as you intend them to
- behave.</para></listitem>
-
- <listitem><para>Use <command>testparm</command> to uncover hidden
- settings that might not reflect your intentions.</para></listitem>
-</itemizedlist>
-
-<para>
-The following is the most minimal configuration file:
-<screen>
-&rootprompt;<userinput>cat /etc/samba/smb.conf-minimal</userinput>
- [printers]
-</screen></para>
-
-<para>
-<indexterm><primary>testparm</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-This example should show that you can use <command>testparm</command> to test any Samba configuration file.
-Actually, we encourage you <emphasis>not</emphasis> to change your working system (unless you know exactly
-what you are doing). Don't rely on the assumption that changes will only take effect after you restart smbd!
-This is not the case. Samba rereads it every 60 seconds and on each new client connection. You might have to
-face changes for your production clients that you didn't intend to apply. You will now note a few more
-interesting things; <command>testparm</command> is useful to identify what the Samba print configuration would
-be if you used this minimalistic configuration. Here is what you can expect to find:
-<screen>
-&rootprompt;<userinput>testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"</userinput>
- Processing section "[printers]"
- WARNING: [printers] service MUST be printable!
- No path in service printers - using /tmp
-
- lpq cache time = 10
- load printers = Yes
- printcap name = /etc/printcap
- disable spoolss = No
- enumports command =
- addprinter command =
- deleteprinter command =
- show add printer wizard = Yes
- os2 driver map =
- min print space = 0
- max print jobs = 1000
- printable = No
- printing = bsd
- print command = lpr -r -P%p %s
- lpq command = lpq -P%p
- printer name =
- use client driver = No
-
- [printers]
- printable = Yes
-</screen></para>
-
-<para>
-<command>testparm</command> issued two warnings:
-</para>
-
-<itemizedlist>
- <listitem><para>We did not specify the <smbconfsection name="[printers]"/> section as printable.</para></listitem>
- <listitem><para>We did not tell Samba which spool directory to use.</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>compile-time options</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-<indexterm><primary></primary></indexterm>
-<indexterm><primary></primary></indexterm>
-However, this was not fatal, and Samba will default to values that will work. Please, do not rely on this and
-do not use this example. This was included to encourage you to be careful to design and specify your setup to
-do precisely what you require. The outcome on your system may vary for some parameters given, since Samba may
-have been built with different compile-time options. <emphasis>Warning:</emphasis> do not put a comment sign
-<emphasis>at the end</emphasis> of a valid line. It will cause the parameter to be ignored (just as if you had
-put the comment sign at the front). At first I regarded this as a bug in my Samba versions. But the man page
-clearly says: <literal>Internal whitespace in a parameter value is retained verbatim.</literal> This means
-that a line consisting of, for example,
-<smbconfblock>
-<smbconfcomment>This defines LPRng as the printing system</smbconfcomment>
-<smbconfoption name="printing"> lprng</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-will regard the whole of the string after the <literal>=</literal> sign as the value you want to define. This
-is an invalid value that will be ignored, and a default value will be used in its place.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Extended Printing Configuration</title>
-
-<para>
-<indexterm><primary>Extended BSD Printing</primary></indexterm>
-<indexterm><primary>BSD-style printing</primary></indexterm>
-<indexterm><primary>CUPS</primary></indexterm>
-<indexterm><primary>testparm</primary></indexterm>
-<link linkend="extbsdpr">Extended BSD Printing Configuration</link> shows a more verbose configuration for
-print-related settings in a BSD-style printing environment. What follows is a discussion and explanation of
-the various parameters. We chose to use BSD-style printing here because it is still the most commonly used
-system on legacy UNIX/Linux installations. New installations predominantly use CUPS, which is discussed in a
-separate chapter. The example explicitly names many parameters that do not need to be specified because they
-are set by default. You could use a much leaner &smb.conf; file, or you can use <command>testparm</command> or
-<command>SWAT</command> to optimize the &smb.conf; file to remove all parameters that are set at default.
-</para>
-
-<example id="extbsdpr">
-<title>Extended BSD Printing Configuration</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="printing">bsd</smbconfoption>
-<smbconfoption name="load printers">yes</smbconfoption>
-<smbconfoption name="show add printer wizard">yes</smbconfoption>
-<smbconfoption name="printcap name">/etc/printcap</smbconfoption>
-<smbconfoption name="max print jobs">100</smbconfoption>
-<smbconfoption name="lpq cache time">20</smbconfoption>
-<smbconfoption name="use client driver">no</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="printable">yes</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="browseable">no</smbconfoption>
-<smbconfoption name="guest ok">yes</smbconfoption>
-<smbconfoption name="public">yes</smbconfoption>
-<smbconfoption name="read only">yes</smbconfoption>
-<smbconfoption name="writable">no </smbconfoption>
-
-<smbconfsection name="[my_printer_name]"/>
-<smbconfoption name="comment">Printer with Restricted Access</smbconfoption>
-<smbconfoption name="path">/var/spool/samba_my_printer</smbconfoption>
-<smbconfoption name="browseable">yes</smbconfoption>
-<smbconfoption name="printable">yes</smbconfoption>
-<smbconfoption name="writable">no</smbconfoption>
-<smbconfoption name="hosts allow">0.0.0.0</smbconfoption>
-<smbconfoption name="hosts deny">turbo_xp, 10.160.50.23, 10.160.51.60</smbconfoption>
-<smbconfoption name="guest ok">no</smbconfoption>
-</smbconfblock></example>
-
-<para>
-<indexterm><primary></primary></indexterm>
-<indexterm><primary></primary></indexterm>
-<indexterm><primary></primary></indexterm>
-This is an example configuration. You may not find all the settings that are in the configuration file that
-was provided by the OS vendor. Samba configuration parameters, if not explicitly set, default to a sensible
-value. To see all settings, as <constant>root</constant> use the <command>testparm</command> utility.
-<command>testparm</command> gives warnings for misconfigured settings.
-</para>
-
-<sect2>
-<title>Detailed Explanation Settings</title>
-
-<para>
-The following is a discussion of the settings from <link linkend="extbsdpr">Extended BSD Printing
-Configuration</link>.
-</para>
-
-<sect3>
-<title>The [global] Section</title>
-
-<para>
-<indexterm><primary>global section</primary></indexterm>
-<indexterm><primary>special sections</primary></indexterm>
-<indexterm><primary>individual section</primary></indexterm>
-<indexterm><primary>share</primary></indexterm>
-The <smbconfsection name="[global]"/> section is one of four special sections (along with <smbconfsection
-name="[homes]"/>, <smbconfsection name="[printers]"/>, and <smbconfsection name="[print$]"/>). The
-<smbconfsection name="[global]"/> contains all parameters that apply to the server as a whole. It is the place
-for parameters that have only a global meaning. It may also contain service-level parameters that define
-default settings for all other sections and shares. This way you can simplify the configuration and avoid
-setting the same value repeatedly. (Within each individual section or share, you may, however, override these
-globally set share settings and specify other values).
-</para>
-
-<variablelist>
- <varlistentry><term><smbconfoption name="printing">bsd </smbconfoption></term>
- <listitem><para>
-<indexterm><primary>default print commands</primary></indexterm>
-<indexterm><primary>RFC 1179</primary></indexterm>
-<indexterm><primary>printing</primary></indexterm>
-<indexterm><primary>CUPS</primary></indexterm>
-<indexterm><primary>LPD</primary></indexterm>
-<indexterm><primary>LPRNG</primary></indexterm>
-<indexterm><primary>SYSV</primary></indexterm>
-<indexterm><primary>HPUX</primary></indexterm>
-<indexterm><primary>AIX</primary></indexterm>
-<indexterm><primary>QNX</primary></indexterm>
-<indexterm><primary>PLP</primary></indexterm>
-<indexterm><primary>queue control</primary></indexterm>
- Causes Samba to use default print commands applicable for the BSD (also known as RFC 1179 style or LPR/LPD)
- printing system. In general, the <parameter>printing</parameter> parameter informs Samba about the print
- subsystem it should expect. Samba supports CUPS, LPD, LPRNG, SYSV, HPUX, AIX, QNX, and PLP. Each of these
- systems defaults to a different <smbconfoption name="print command"/> (and other queue control commands).
- </para>
-
- <caution><para>
-<indexterm><primary>service-level</primary></indexterm>
-<indexterm><primary>SOFTQ printing system</primary></indexterm>
- The <smbconfoption name="printing"/> parameter is normally a service-level parameter. Since it is included
- here in the <smbconfsection name="[global]"/> section, it will take effect for all printer shares that are not
- defined differently. Samba no longer supports the SOFTQ printing system.
- </para></caution>
- </listitem></varlistentry>
-
- <varlistentry><term><smbconfoption name="load printers">yes </smbconfoption></term>
- <listitem><para>
-<indexterm><primary>printer shares</primary></indexterm>
-<indexterm><primary>printcap</primary></indexterm>
-<indexterm><primary>separate shares</primary></indexterm>
-<indexterm><primary>UNIX printer</primary></indexterm>
- Tells Samba to create automatically all available printer shares. Available printer shares are discovered by
- scanning the printcap file. All created printer shares are also loaded for browsing. If you use this
- parameter, you do not need to specify separate shares for each printer. Each automatically created printer
- share will clone the configuration options found in the <smbconfsection name="[printers]"/> section. (The
- <parameter>load printers = no</parameter> setting will allow you to specify each UNIX printer you want to
- share separately, leaving out some you do not want to be publicly visible and available).
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term><smbconfoption name="show add printer wizard">yes </smbconfoption></term>
- <listitem><para>
-<indexterm><primary>Add Printer Wizard</primary></indexterm>
-<indexterm><primary>Printers</primary></indexterm>
-<indexterm><primary>Network Neighborhood</primary></indexterm>
-<indexterm><primary>net view</primary></indexterm>
-<indexterm><primary>uploaded driver</primary></indexterm>
- Setting is normally enabled by default (even if the parameter is not specified in &smb.conf;). It causes the
- <guiicon>Add Printer Wizard</guiicon> icon to appear in the <guiicon>Printers</guiicon> folder of the Samba
- host's share listing (as shown in <guiicon>Network Neighborhood</guiicon> or by the <command>net
- view</command> command). To disable it, you need to explicitly set it to <constant>no</constant> (commenting
- it out will not suffice). The <parameter>Add Printer Wizard</parameter> lets you upload a printer driver to
- the <smbconfsection name="[print$]"/> share and associate it with a printer (if the respective queue exists
- before the action), or exchange a printer's driver for any other previously uploaded driver.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term><smbconfoption name="max print jobs">100 </smbconfoption></term>
- <listitem><para>
-<indexterm><primary>print jobs</primary></indexterm>
- Sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client
- submit a job that exceeds this number, a "no more space available on server" type of error message will be
- returned by Samba to the client. A setting of zero (the default) means there is <emphasis>no</emphasis> limit
- at all.
- </para>
- </listitem></varlistentry>
-
- <varlistentry><term><smbconfoption name="printcap name">/etc/printcap </smbconfoption></term>
- <listitem><para>
-<indexterm><primary>CUPS</primary></indexterm>
-<indexterm><primary>available printerd</primary></indexterm>
-<indexterm><primary>printcap</primary></indexterm>
- Tells Samba where to look for a list of available printer names. Where CUPS is used, make sure that a printcap
- file is written. This is controlled by the <constant>Printcap</constant> directive in the
- <filename>cupsd.conf</filename> file.
- </para></listitem></varlistentry>
-
- <varlistentry><term><smbconfoption name="lpq cache time">20 </smbconfoption></term>
- <listitem><para>
-<indexterm><primary>lpq command</primary></indexterm>
-<indexterm><primary>lpq cache time</primary></indexterm>
- Controls the cache time for the results of the lpq command. It prevents the lpq command being called too often
- and reduces the load on a heavily used print server.
- </para></listitem></varlistentry>
-
- <varlistentry><term><smbconfoption name="use client driver">no </smbconfoption></term>
- <listitem><para>
-<indexterm><primary>Windows NT/200x/XP</primary></indexterm>
- If set to <constant>yes</constant>, only takes effect for Windows NT/200x/XP clients (and not for Win
- 95/98/ME). Its default value is <constant>No</constant> (or <constant>False</constant>). It must
- <emphasis>not</emphasis> be enabled on print shares (with a <constant>yes</constant> or
- <constant>true</constant> setting) that have valid drivers installed on the Samba server. For more detailed
- explanations, see the &smb.conf; man page.
- </para></listitem></varlistentry>
-</variablelist>
-
-</sect3>
-
-<sect3 id="ptrsect">
-<title>The [printers] Section</title>
-
-<para>
-<indexterm><primary>printers section</primary></indexterm>
-<indexterm><primary>printcap</primary></indexterm>
-The printers section is the second special section. If a section with this name appears in the &smb.conf;,
-users are able to connect to any printer specified in the Samba host's printcap file, because Samba on startup
-then creates a printer share for every printer name it finds in the printcap file. You could regard this
-section as a convenient shortcut to share all printers with minimal configuration. It is also a container for
-settings that should apply as default to all printers. (For more details, see the &smb.conf; man page.)
-Settings inside this container must be share-level parameters.
-</para>
-
-<variablelist>
- <varlistentry><term><smbconfoption name="comment">All printers </smbconfoption></term>
- <listitem><para>
- The <smbconfoption name="comment"/> is shown next to the share if
- a client queries the server, either via <guiicon>Network Neighborhood</guiicon> or with
- the <command>net view</command> command, to list available shares.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="printable">yes </smbconfoption></term>
- <listitem><para>
- The <smbconfsection name="[printers]"/> service <emphasis>must</emphasis>
- be declared as printable. If you specify otherwise, smbd will refuse to load at
- startup. This parameter allows connected clients to open, write to, and submit spool files
- into the directory specified with the <smbconfoption name="path"/>
- parameter for this service. It is used by Samba to differentiate printer shares from
- file shares.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="path">/var/spool/samba </smbconfoption></term>
- <listitem><para>
- Must point to a directory used by Samba to spool incoming print files. <emphasis>It
- must not be the same as the spool directory specified in the configuration of your UNIX
- print subsystem!</emphasis> The path typically points to a directory that is world
- writable, with the <emphasis>sticky</emphasis> bit set to it.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="browseable">no </smbconfoption></term>
- <listitem><para>
- Is always set to <constant>no</constant> if
- <smbconfoption name="printable">yes</smbconfoption>. It makes
- the <smbconfsection name="[printer]"/> share itself invisible in the list of
- available shares in a <command>net view</command> command or in the Explorer browse
- list. (You will of course see the individual printers.)
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="guest ok">yes </smbconfoption></term>
- <listitem><para>
- If this parameter is set to <constant>yes</constant>, no password is required to
- connect to the printer's service. Access will be granted with the privileges of the
- <smbconfoption name="guest account"/>. On many systems the guest
- account will map to a user named "nobody." This user will usually be found
- in the UNIX passwd file with an empty password, but with no valid UNIX login. On some
- systems the guest account might not have the privilege to be able to print. Test this
- by logging in as your guest user using <command>su - guest</command> and run a system
- print command like:
- </para>
-
- <para>
- <userinput>lpr -P printername /etc/motd</userinput>
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="public">yes </smbconfoption></term>
- <listitem><para>
- Is a synonym for <smbconfoption name="guest ok">yes</smbconfoption>.
- Since we have <smbconfoption name="guest ok">yes</smbconfoption>, it
- really does not need to be here. (This leads to the interesting question, <quote>What if I
- by accident have two contradictory settings for the same share?</quote> The answer is that the
- last one encountered by Samba wins. <command>testparm</command> does not complain about different settings
- of the same parameter for the same share. You can test this by setting up multiple
- lines for the <parameter>guest account</parameter> parameter with different usernames,
- and then run testparm to see which one is actually used by Samba.)
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="read only">yes </smbconfoption></term>
- <listitem><para>
- Normally (for other types of shares) prevents users from creating or modifying files
- in the service's directory. However, in a <emphasis>printable</emphasis> service, it is
- <emphasis>always</emphasis> allowed to write to the directory (if user privileges allow the
- connection), but only via print spooling operations. Normal write operations are not permitted.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="writable">no </smbconfoption></term>
- <listitem><para>
- Is a synonym for <smbconfoption name="read only">yes</smbconfoption>.
- </para></listitem>
- </varlistentry>
-</variablelist>
-</sect3>
-
-<sect3>
-<title>Any [my_printer_name] Section</title>
-
-<para>
-<indexterm><primary>loading printer drivers</primary></indexterm>
-<indexterm><primary>name conflict</primary></indexterm>
-If a <parameter>[my_printer_name]</parameter> section appears in the &smb.conf; file, which includes the
-parameter <smbconfoption name="printable">yes</smbconfoption> Samba will configure it as a printer share.
-Windows 9x/Me clients may have problems with connecting or loading printer drivers if the share name has more
-than eight characters. Do not name a printer share with a name that may conflict with an existing user or file
-share name. On client connection requests, Samba always tries to find file shares with that name first. If it
-finds one, it will connect to this and will not connect to a printer with the same name!
-</para>
-
-<?latex \newpage ?>
-<variablelist>
- <varlistentry><term><smbconfoption name="comment">Printer with Restricted Access </smbconfoption></term>
- <listitem><para>
- The comment says it all.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="path">/var/spool/samba_my_printer </smbconfoption></term>
- <listitem><para>
- Sets the spooling area for this printer to a directory other than the default. It is not
- necessary to set it differently, but the option is available.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="browseable">yes </smbconfoption></term>
- <listitem><para>
- This makes the printer browseable so the clients may conveniently find it when browsing the
- <guiicon>Network Neighborhood</guiicon>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="printable">yes </smbconfoption></term>
- <listitem><para>
- See <link linkend="ptrsect">Section 20.4.1.2</link>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="writable">no </smbconfoption></term>
- <listitem><para>
- See <link linkend="ptrsect">Section 20.4.1.2</link>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="hosts allow">10.160.50.,10.160.51. </smbconfoption></term>
- <listitem><para>
- Here we exercise a certain degree of access control by using the <smbconfoption name="hosts allow"/>
- and <smbconfoption name="hosts deny"/> parameters. This is not by any means a safe bet. It is not a
- way to secure your printers. This line accepts all clients from a certain subnet in a first evaluation of
- access control.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="hosts deny">turbo_xp,10.160.50.23,10.160.51.60 </smbconfoption></term>
- <listitem><para>
- All listed hosts are not allowed here (even if they belong to the allowed subnets). As
- you can see, you could name IP addresses as well as NetBIOS hostnames here.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="guest ok">no </smbconfoption></term>
- <listitem><para>
- This printer is not open for the guest account.
- </para></listitem>
- </varlistentry>
-</variablelist>
-</sect3>
-
-<sect3>
-<title>Print Commands</title>
-
-<para>
-<indexterm><primary>print command</primary></indexterm>
-<indexterm><primary>print subsystem</primary></indexterm>
-<indexterm><primary>temporary location</primary></indexterm>
-<indexterm><primary>shell scripts</primary></indexterm>
-In each section defining a printer (or in the <smbconfsection name="[printers]"/> section),
-a <parameter>print command</parameter> parameter may be defined. It sets a command to process the files
-that have been placed into the Samba print spool directory for that printer. (That spool directory was,
-if you remember, set up with the <smbconfoption name="path"/> parameter). Typically,
-this command will submit the spool file to the Samba host's print subsystem, using the suitable system
-print command. But there is no requirement that this needs to be the case. For debugging or
-some other reason, you may want to do something completely different than print the file. An example is a
-command that just copies the print file to a temporary location for further investigation when you need
-to debug printing. If you craft your own print commands (or even develop print command shell scripts),
-make sure you pay attention to the need to remove the files from the Samba spool directory. Otherwise,
-your hard disk may soon suffer from shortage of free space.
-</para>
-</sect3>
-
-<sect3>
-<title>Default UNIX System Printing Commands</title>
-
-<para>
-<indexterm><primary>default print command</primary></indexterm>
-You learned earlier that Samba, in most cases, uses its built-in settings for many parameters if it cannot
-find an explicitly stated one in its configuration file. The same is true for the <smbconfoption name="print
-command"/>. The default print command varies depending on the <smbconfoption name="printing"/> parameter
-setting. In the commands listed in <link linkend="printOptions">Default Printing Settings</link> , you will
-notice some parameters of the form <emphasis>%X</emphasis> where <emphasis>X</emphasis> is <emphasis>p, s,
-J</emphasis>, and so on. These letters stand for printer name, spool file, and job ID, respectively. They are
-explained in more detail in <link linkend="printOptions">Default Printing Settings</link> presents an overview
-of key printing options but excludes the special case of CUPS, is discussed in <link
-linkend="CUPS-printing">CUPS Printing Support</link>.
-</para>
-
-<table frame='all' id="printOptions">
- <title>Default Printing Settings</title>
- <tgroup cols='2' align='left' colsep='1' rowsep='1'>
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry>Setting</entry>
- <entry>Default Printing Commands</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
- <entry>print command is <command>lpr -r -P%p %s</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
- <entry>print command is <command>lp -c -P%p %s; rm %s</command></entry>
- </row>
- <row>
- <entry> <smbconfoption name="printing">qnx</smbconfoption></entry>
- <entry>print command is <command>lp -r -P%p -s %s</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
- <entry>lpq command is <command>lpq -P%p</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
- <entry>lpq command is <command>lpstat -o%p</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">qnx</smbconfoption></entry>
- <entry>lpq command is <command>lpq -P%p</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
- <entry>lprm command is <command>lprm -P%p %j</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
- <entry>lprm command is <command>cancel %p-%j</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">qnx</smbconfoption></entry>
- <entry>lprm command is <command>cancel %p-%j</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
- <entry>lppause command is <command>lp -i %p-%j -H hold</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
- <entry>lppause command (...is empty)</entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">qnx</smbconfoption></entry>
- <entry>lppause command (...is empty)</entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">bsd|aix|lprng|plp</smbconfoption></entry>
- <entry>lpresume command is <command>lp -i %p-%j -H resume</command></entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">sysv|hpux</smbconfoption></entry>
- <entry>lpresume command (...is empty)</entry>
- </row>
- <row>
- <entry><smbconfoption name="printing">qnx</smbconfoption></entry>
- <entry>lpresume command (...is empty)</entry>
- </row>
- </tbody>
- </tgroup>
-</table>
-
-<para>
-<indexterm><primary>CUPS API</primary></indexterm>
-<indexterm><primary>cupsd.conf</primary></indexterm>
-<indexterm><primary>autogenerated printcap</primary></indexterm>
-<indexterm><primary>libcups</primary></indexterm>
-For <parameter>printing = CUPS</parameter>, if Samba is compiled against libcups, it uses the CUPS API to
-submit jobs. (It is a good idea also to set <smbconfoption name="printcap">cups</smbconfoption> in case your
-<filename>cupsd.conf</filename> is set to write its autogenerated printcap file to an unusual place).
-Otherwise, Samba maps to the System V printing commands with the -oraw option for printing; that is, it uses
-<command>lp -c -d%p -oraw; rm %s</command>. With <parameter>printing = cups</parameter>, and if Samba is
-compiled against libcups, any manually set print command will be ignored!
-</para>
-
-</sect3>
-
-<sect3>
-<title>Custom Print Commands</title>
-
-<para>
-<indexterm><primary>print job</primary></indexterm>
-<indexterm><primary>spooling</primary></indexterm>
-After a print job has finished spooling to a service, the <smbconfoption name="print command"/> will be used
-by Samba via a system() call to process the spool file. Usually the command specified will submit the spool
-file to the host's printing subsystem. But there is no requirement at all that this must be the case. The
-print subsystem may not remove the spool file on its own, so whatever command you specify, you should ensure
-that the spool file is deleted after it has been processed.
-</para>
-
-<para>
-<indexterm><primary>traditional printing</primary></indexterm>
-<indexterm><primary>customized print commands</primary></indexterm>
-<indexterm><primary>built-in commands</primary></indexterm>
-<indexterm><primary>macros</primary></indexterm>
-There is no difficulty with using your own customized print commands with the traditional printing systems.
-However, if you do not wish to roll your own, you should be well informed about the default built-in commands
-that Samba uses for each printing subsystem (see <link linkend="printOptions">Default Printing
-Settings</link>). In all the commands listed in the last paragraphs, you see parameters of the form
-<emphasis>%X</emphasis>. These are <emphasis>macros</emphasis>, or shortcuts, used as placeholders for the
-names of real objects. At the time of running a command with such a placeholder, Samba will insert the
-appropriate value automatically. Print commands can handle all Samba macro substitutions. In regard to
-printing, the following ones do have special relevance:
-</para>
-
-<itemizedlist>
- <listitem><para><parameter>%s, %f</parameter> &smbmdash; the path to the spool file name.</para></listitem>
- <listitem><para><parameter>%p</parameter> &smbmdash; the appropriate printer name.</para></listitem>
- <listitem><para><parameter>%J</parameter> &smbmdash; the job name as transmitted by the client.</para></listitem>
- <listitem><para><parameter>%c</parameter> &smbmdash; the number of printed pages of the spooled job (if known).</para></listitem>
- <listitem><para><parameter>%z</parameter> &smbmdash; the size of the spooled print job (in bytes).</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>default printer</primary></indexterm>
-The print command must contain at least one occurrence of <parameter>%s</parameter> or
-<parameter>%f</parameter>. The <parameter>%p</parameter> is optional. If no printer name is supplied,
-the <parameter>%p</parameter> will be silently removed from the print command. In this case, the job is
-sent to the default printer.
-</para>
-
-<para>
-<indexterm><primary>global print command</primary></indexterm>
-<indexterm><primary>spool files</primary></indexterm>
-If specified in the <smbconfsection name="[global]"/> section, the print command given will be
-used for any printable service that does not have its own print command specified. If there is neither a
-specified print command for a printable service nor a global print command, spool files will be created
-but not processed! Most importantly, print files will not be removed, so they will consume disk space.
-</para>
-
-<para>
-<indexterm><primary>nobody account</primary></indexterm>
-<indexterm><primary>guest account</primary></indexterm>
-Printing may fail on some UNIX systems when using the <emphasis>nobody</emphasis> account. If this happens, create an
-alternative guest account and give it the privilege to print. Set up this guest account in the
-<smbconfsection name="[global]"/> section with the <parameter>guest account</parameter> parameter.
-</para>
-
-<para>
-<indexterm><primary>environment variables</primary></indexterm>
-<indexterm><primary>print commands</primary></indexterm>
-<indexterm><primary>print job</primary></indexterm>
-You can form quite complex print commands. You need to realize that print commands are just
-passed to a UNIX shell. The shell is able to expand the included environment variables as
-usual. (The syntax to include a UNIX environment variable <parameter>$variable</parameter>
-in the Samba print command is <parameter>%$variable</parameter>.) To give you a working
-<smbconfoption name="print command"/> example, the following will log a print job
-to <filename>/tmp/print.log</filename>, print the file, then remove it. The semicolon (<quote>;</quote>)
-is the usual separator for commands in shell scripts:
-</para>
-
-<para><smbconfblock>
- <smbconfoption name="print command">echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</smbconfoption>
-</smbconfblock></para>
-
-<para>
-You may have to vary your own command considerably from this example depending on how you normally print
-files on your system. The default for the <smbconfoption name="print command"/>
-parameter varies depending on the setting of the <smbconfoption name="printing"/>
-parameter. Another example is:
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="print command">/usr/local/samba/bin/myprintscript %p %s</smbconfoption>
-</smbconfblock></para>
-</sect3>
-</sect2>
-</sect1>
-
-<sect1 id="cups-msrpc">
-<title>Printing Developments Since Samba-2.2</title>
-
-<para>
-<indexterm><primary>LanMan</primary></indexterm>
-<indexterm><primary>MS-RPC</primary></indexterm>
-<indexterm><primary>SPOOLSS</primary></indexterm>
-Prior to Samba-2.2.x, print server support for Windows clients was limited to <emphasis>LanMan</emphasis>
-printing calls. This is the same protocol level as Windows 9x/Me PCs offer when they share printers.
-Beginning with the 2.2.0 release, Samba started to support the native Windows NT printing mechanisms. These
-are implemented via <emphasis>MS-RPC</emphasis> (Remote Procedure Calls).
-MS-RPCs use the <emphasis>SPOOLSS</emphasis> named pipe for all printing.
-</para>
-
-<para>
-The additional functionality provided by the new SPOOLSS support includes:
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>Point'n'Print</primary></indexterm>
- Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon
- demand (<emphasis>Point'n'Print</emphasis>).
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>Add Printer Wizard</primary></indexterm>
- Uploading of printer drivers via the Windows NT <emphasis>Add Printer Wizard</emphasis> (APW)
- or the <ulink url="http://imprints.sourceforge.net/">Imprints</ulink> tool set.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>MS-RPC</primary></indexterm>
-<indexterm><primary>printing calls</primary></indexterm>
-<indexterm><primary>StartDocPrinter</primary></indexterm>
-<indexterm><primary>EnumJobs()</primary></indexterm>
-<indexterm><primary>Win32 printing API</primary></indexterm>
- Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), and so on. (See the
- <ulink url="http://msdn.microsoft.com/">MSDN documentation</ulink> for more information on the
- Win32 printing API).
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>ACL</primary></indexterm>
-<indexterm><primary>printer objects</primary></indexterm>
- Support for NT Access Control Lists (ACL) on printer objects.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>printer queue</primary></indexterm>
- Improved support for printer queue manipulation through the use of internal databases for spooled
- job information (implemented by various <filename>*.tdb</filename> files).
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>LDAP</primary></indexterm>
-A benefit of updating is that Samba is able to publish its printers to Active Directory (or LDAP).
-</para>
-
-<para>
-<indexterm><primary>publish printers</primary></indexterm>
-A fundamental difference exists between MS Windows NT print servers and Samba operation. Windows NT
-permits the installation of local printers that are not shared. This is an artifact of the fact that
-any Windows NT machine (server or client) may be used by a user as a workstation. Samba will publish all
-printers that are made available, either by default or by specific declaration via printer-specific shares.
-</para>
-
-<para>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>MS-RPC</primary></indexterm>
-<indexterm><primary>Everyone group</primary></indexterm>
-<indexterm><primary>privileges</primary></indexterm>
-<indexterm><primary>printer default permissions</primary></indexterm>
-Windows NT/200x/XP Professional clients do not have to use the standard SMB printer share; they can
-print directly to any printer on another Windows NT host using MS-RPC. This, of course, assumes that
-the client has the necessary privileges on the remote host that serves the printer resource. The
-default permissions assigned by Windows NT to a printer gives the print permissions to the well-known
-<emphasis>Everyone</emphasis> group. (The older clients of type Windows 9x/Me can only print to shared
-printers.)
-</para>
-
-<sect2>
-<title>Point'n'Print Client Drivers on Samba Servers</title>
-
-<para>
-<indexterm><primary>printer drivers</primary></indexterm>
-There is much confusion about what all this means. The question is often asked, <quote>Is it or is
-it not necessary for printer drivers to be installed on a Samba host in order to support printing from
-Windows clients?</quote> The answer to this is no, it is not necessary.
-</para>
-
-<para>
-<indexterm><primary>install drivers</primary></indexterm>
-<indexterm><primary>print queue</primary></indexterm>
-Windows NT/2000 clients can, of course, also run their APW to install drivers <emphasis>locally</emphasis>
-(which then connect to a Samba-served print queue). This is the same method used by Windows 9x/Me
-clients. (However, a bug existed in Samba 2.2.0 that made Windows NT/2000 clients
-require that the Samba server possess a valid driver for the printer. This was fixed in Samba 2.2.1).
-</para>
-
-<para>
-<indexterm><primary>printer drivers</primary></indexterm>
-<indexterm><primary>uploading</primary></indexterm>
-But it is a new capability to install the printer drivers into the <smbconfsection name="[print$]"/>
-share of the Samba server, and a big convenience, too. Then <emphasis>all</emphasis> clients
-(including 95/98/ME) get the driver installed when they first connect to this printer share. The
-<emphasis>uploading</emphasis> or <emphasis>depositing</emphasis> of the driver into this
-<smbconfsection name="[print$]"/> share and the following binding of this driver to an existing
-Samba printer share can be achieved by different means:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Running the <emphasis>APW</emphasis> on an NT/200x/XP Professional client (this does not work from 95/98/ME clients).
- </para></listitem>
-
- <listitem><para>
- Using the <emphasis>Imprints</emphasis> toolset.
- </para></listitem>
-
- <listitem><para>
- Using the <emphasis>smbclient</emphasis> and <emphasis>rpcclient</emphasis> command-line tools.
- </para></listitem>
-
- <listitem><para>
- Using <emphasis>cupsaddsmb</emphasis> (only works for the CUPS printing system, not for LPR/LPD, LPRng, and so on).
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>uploaded drivers</primary></indexterm>
-<indexterm><primary>Point'n'Print</primary></indexterm>
-Samba does not use these uploaded drivers in any way to process spooled files. These drivers are utilized
-entirely by the clients who download and install them via the <quote>Point'n'Print</quote> mechanism
-supported by Samba. The clients use these drivers to generate print files in the format the printer
-(or the UNIX print system) requires. Print files received by Samba are handed over to the UNIX printing
-system, which is responsible for all further processing, as needed.
-</para>
-</sect2>
-
-<sect2>
-<title>The Obsoleted [printer$] Section</title>
-
- <para>
-<indexterm><primary>printer$ share</primary></indexterm>
-<indexterm><primary>printer driver</primary></indexterm>
- Versions of Samba prior to 2.2 made it possible to use a share named <parameter>[printer$]</parameter>. This
- name was taken from the same named service created by Windows 9x/Me clients when a printer was shared by them.
- Windows 9x/Me printer servers always have a <smbconfsection name="[printer$]"/> service that provides
- read-only access (with no password required) to support printer driver downloads. However, Samba's initial
- implementation allowed for a parameter named <parameter>printer driver location</parameter> to be used on a
- per-share basis. This specified the location of the driver files associated with that printer. Another
- parameter named <parameter>printer driver</parameter> provided a means of defining the printer driver name to
- be sent to the client.
- </para>
-
- <para>
-<indexterm><primary>printer driver file</primary></indexterm>
-<indexterm><primary>read-write access</primary></indexterm>
-<indexterm><primary>ACLs</primary></indexterm>
- These parameters, including the <parameter>printer driver file</parameter> parameter,
- are now removed and cannot be used in installations of Samba. The share name
- <smbconfsection name="[print$]"/> is now used for the location of downloadable printer
- drivers. It is taken from the <smbconfsection name="[print$]"/> service created
- by Windows NT PCs when a printer is shared by them. Windows NT print servers always have a
- <smbconfsection name="[print$]"/> service that provides read-write access (in the context
- of its ACLs) to support printer driver downloads and uploads. This does not mean Windows
- 9x/Me clients are now thrown aside. They can use Samba's <smbconfsection name="[print$]"/>
- share support just fine.
- </para>
-</sect2>
-
-<sect2>
-<title>Creating the [print$] Share</title>
-
-<para>
-<indexterm><primary>printer driver</primary></indexterm>
-In order to support the uploading and downloading of printer driver files, you must first configure a
-file share named <smbconfsection name="[print$]"/>. The public name of this share is hard coded
-in the MS Windows clients. It cannot be renamed, since Windows clients are programmed to search for a
-service of exactly this name if they want to retrieve printer driver files.
-</para>
-
-<para>
-You should modify the server's file to add the global parameters and create the
-<smbconfsection name="[print$]"/> file share (of course, some of the parameter values, such
-as <smbconfoption name="path"/>, are arbitrary and should be replaced with appropriate values for your
-site). See <link linkend="prtdollar">[print\$] Example</link>.
-</para>
-
-<example id="prtdollar">
-<title>[print$] Example</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfcomment>...</smbconfcomment>
-
-<smbconfsection name="[printers]"/>
-<smbconfcomment>...</smbconfcomment>
-
-<smbconfsection name="[print$]"/>
-<smbconfoption name="comment">Printer Driver Download Area</smbconfoption>
-<smbconfoption name="path">/etc/samba/drivers</smbconfoption>
-<smbconfoption name="browseable">yes</smbconfoption>
-<smbconfoption name="guest ok">yes</smbconfoption>
-<smbconfoption name="read only">yes</smbconfoption>
-<smbconfoption name="write list">@ntadmin, root</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-Of course, you also need to ensure that the directory named by the
-<smbconfoption name="path"/> parameter exists on the UNIX file system.
-</para>
-
-</sect2>
-
-<sect2>
-<title>[print$] Stanza Parameters</title>
-
-<para>
-<indexterm><primary>special section</primary></indexterm>
-<indexterm><primary>special stanza</primary></indexterm>
-<indexterm><primary>potential printer</primary></indexterm>
-<indexterm><primary>driver download</primary></indexterm>
-<indexterm><primary>local print driver</primary></indexterm>
-The <smbconfsection name="[print$]"/> is a special section in &smb.conf;. It contains settings relevant to
-potential printer driver download and is used by Windows clients for local print driver installation.
-The following parameters are frequently needed in this share section:
-</para>
-
-<variablelist>
- <varlistentry><term><smbconfoption name="comment">Printer Driver Download Area </smbconfoption></term>
- <listitem><para>
- The comment appears next to the share name if it is listed in a share list (usually Windows
- clients will not see it, but it will also appear up in a <command>smbclient -L sambaserver
- </command> output).
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="path">/etc/samba/printers </smbconfoption></term>
- <listitem><para>
- The path to the location of the Windows driver file deposit from the UNIX point of view.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="browseable">no </smbconfoption></term>
- <listitem><para>
- Makes the <smbconfsection name="[print$]"/> share invisible to clients from the
- <guimenu>Network Neighborhood</guimenu>. By excuting from a <command>cmd</command> shell:
-<screen>
-&dosprompt; <command>net use g:\\sambaserver\print$</command>
-</screen>
- you can still mount it from any client. This can also be done from the
- <guimenu>Connect network drive</guimenu> menu from Windows Explorer.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="guest ok">yes </smbconfoption></term>
- <listitem><para>
- Gives read-only access to this share for all guest users. Access may be granted to
- download and install printer drivers on clients. The requirement for <parameter>guest ok
- = yes</parameter> depends on how your site is configured. If users will be guaranteed
- to have an account on the Samba host, then this is a non-issue.
- </para>
-
- <note><para>
- If all your Windows NT users are guaranteed to be authenticated by the Samba server
- (for example, if Samba authenticates via an NT domain server and the user has already been
- validated by the domain controller in order to log on to the Windows NT session), then guest
- access is not necessary. Of course, in a workgroup environment where you just want
- to print without worrying about silly accounts and security, then configure the share for
- guest access. You should consider adding <smbconfoption name="map to guest">Bad User</smbconfoption>
- in the <smbconfsection name="[global]"/> section as well. Make sure you understand what this
- parameter does before using it.
- </para></note>
- </listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="read only">yes </smbconfoption></term>
- <listitem><para>
- Because we do not want everybody to upload driver files (or even change driver settings),
- we tagged this share as not writable.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term><smbconfoption name="write list">@ntadmin, root </smbconfoption></term>
- <listitem><para>
- The <smbconfsection name="[print$]"/> was made read-only by the previous
- setting so we should create a <parameter>write list</parameter> entry also. UNIX
- groups are denoted with a leading <quote>@</quote> character. Users listed here are allowed
- write-access (as an exception to the general public's read-only access), which they need to
- update files on the share. Normally, you will want to name only administrative-level user
- account in this setting. Check the file system permissions to make sure these accounts
- can copy files to the share.
- </para></listitem>
- </varlistentry>
-</variablelist>
-
-</sect2>
-
-<sect2>
-<title>The [print$] Share Directory</title>
-
-<para>
-In order for a Windows NT print server to support the downloading of driver files by multiple client
-architectures, you must create several subdirectories within the <smbconfsection name="[print$]"/>
-service (i.e., the UNIX directory named by the <smbconfoption name="path"/>
-parameter). These correspond to each of the supported client architectures. Samba follows this model as
-well. Just like the name of the <smbconfsection name="[print$]"/> share itself, the subdirectories
-must be exactly the names listed below (you may leave out the subdirectories of architectures you do
-not need to support).
-</para>
-
-<para>
-Therefore, create a directory tree below the
-<smbconfsection name="[print$]"/> share for each architecture you wish
-to support like this:
-<programlisting>
-[print$]--+
- |--W32X86 # serves drivers to Windows NT x86
- |--WIN40 # serves drivers to Windows 95/98
- |--W32ALPHA # serves drivers to Windows NT Alpha_AXP
- |--W32MIPS # serves drivers to Windows NT R4000
- |--W32PPC # serves drivers to Windows NT PowerPC
-</programlisting>
-</para>
-
-<important><title>Required Permissions</title>
- <para>
- In order to add a new driver to your Samba host, one of two conditions must hold true:
- </para>
-
- <itemizedlist>
- <listitem><para>
- The account used to connect to the Samba host must have a UID of 0 (i.e., a root account).
- </para></listitem>
- </itemizedlist>
-
- <para>
- Of course, the connected account must still have write access to add files to the subdirectories beneath
- <smbconfsection name="[print$]"/>. Remember that all file shares are set to <quote>read-only</quote> by default.
- </para>
-</important>
-
-<para>
-Once you have created the required <smbconfsection name="[print$]"/> service and
-associated subdirectories, go to a Windows NT 4.0/200x/XP client workstation. Open <guiicon>Network
-Neighborhood</guiicon> or <guiicon>My Network Places</guiicon> and browse for the Samba host. Once you
-have located the server, navigate to its <guiicon>Printers and Faxes</guiicon> folder. You should see
-an initial listing of printers that matches the printer shares defined on your Samba host.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Installing Drivers into [print$]</title>
-
-<para>
-Have you successfully created the <smbconfsection name="[print$]"/> share in &smb.conf;, and have you forced
-Samba to reread its &smb.conf; file? Good. But you are not yet ready to use the new facility. The client
-driver files need to be installed into this share. So far, it is still an empty share. Unfortunately, it is
-not enough to just copy the driver files over. They need to be correctly installed so that appropriate records
-for each driver will exist in the Samba internal databases so it can provide the correct drivers as they are
-requested from MS Windows clients. And that is a bit tricky, to say the least. We now discuss two alternative
-ways to install the drivers into <smbconfsection name="[print$]"/>:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Using the Samba command-line utility <command>rpcclient</command> with its various subcommands (here,
- <command>adddriver</command> and <command>setdriver</command>) from any UNIX workstation.
- </para></listitem>
-
- <listitem><para>
- Running a GUI (<guiicon>Printer Properties</guiicon> and <guiicon>Add Printer Wizard</guiicon>)
- from any Windows NT/200x/XP client workstation.
- </para></listitem>
-</itemizedlist>
-
-<para>
-The latter option is probably the easier one (even if the process may seem a little bit weird at first).
-</para>
-
-<sect2>
-<title>Add Printer Wizard Driver Installation</title>
-
-<para>
-The printers initially listed in the Samba host's <guiicon>Printers</guiicon> folder accessed from a
-client's Explorer will have no real printer driver assigned to them. By default this driver name is set
-to a null string. This must be changed now. The local <guiicon>Add Printer Wizard</guiicon> (APW), run from
-NT/2000/XP clients, will help us in this task.
-</para>
-
-<para>
-Installation of a valid printer driver is not straightforward. You must attempt to view the printer properties
-for the printer to which you want the driver assigned. Open Windows Explorer, open <guiicon>Network
-Neighborhood</guiicon>, browse to the Samba host, open Samba's <guiicon>Printers</guiicon> folder, right-click
-on the printer icon, and select <guimenu>Properties...</guimenu>. You are now trying to view printer and
-driver properties for a queue that has this default <constant>NULL</constant> driver assigned. This will
-result in the following error message: <quote> Device settings cannot be displayed. The driver for the
-specified printer is not installed, only spooler properties will be displayed. Do you want to install the
-driver now?</quote>
-</para>
-
-<para>
-Do <emphasis>not</emphasis> click on <guibutton>Yes</guibutton>! Instead, click on <guibutton>No</guibutton>
-in the error dialog. Now you will be presented with the printer properties window. From here, the way to
-assign a driver to a printer is open. You now have the choice of:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Select a driver from the pop-up list of installed drivers. Initially this list will be empty.
- </para></listitem>
-
- <listitem><para>
- Click on <guibutton>New Driver</guibutton> to install a new printer driver (which will
- start up the APW).
- </para></listitem>
-</itemizedlist>
-
-<para>
-Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we
-assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure
-your connection is, in fact, set up as a user with printer administrator privileges
-(if in doubt, use <command>smbstatus</command> to check for this). If you wish to install
-printer drivers for client operating systems other than <application>Windows NT x86</application>,
-you will need to use the <guilabel>Sharing</guilabel> tab of the printer properties dialog.
-</para>
-
-<para>
-Assuming you have connected with an administrative (or root) account, you will also be able to modify
-other printer properties such as ACLs and default device settings using this dialog. For the default
-device settings, please consider the advice given further in <link linkend="inst-rpc">Installing
-Print Drivers Using <command>rpcclient</command></link>.
-</para>
-</sect2>
-
-<sect2 id="inst-rpc">
-<title>Installing Print Drivers Using <command>rpcclient</command></title>
-
-<para>
-The second way to install printer drivers into <smbconfsection name="[print$]"/> and set them
-up in a valid way is to do it from the UNIX command line. This involves four distinct steps:
-</para>
-
-<orderedlist>
- <listitem><para>
- Gather information about required driver files and collect the files.
- </para></listitem>
-
- <listitem><para>
- Deposit the driver files into the <smbconfsection name="[print$]"/> share's correct subdirectories
- (possibly by using <command>smbclient</command>).
- </para></listitem>
-
- <listitem><para>
- Run the <command>rpcclient</command> command-line utility once with the <command>adddriver</command>
- subcommand.
- </para></listitem>
-
- <listitem><para>
- Run <command>rpcclient</command> a second time with the <command>setdriver</command> subcommand.
- </para></listitem>
-</orderedlist>
-
-<para>
-We provide detailed hints for each of these steps in the paragraphs that follow.
-</para>
-
-<sect3>
-<title>Identifying Driver Files</title>
-
-<para>
-<indexterm><primary>driver files</primary></indexterm>
-<indexterm><primary>driver CDROM</primary></indexterm>
-<indexterm><primary>inf file</primary></indexterm>
-To find out about the driver files, you have two options. You can check the contents of the driver
-CDROM that came with your printer. Study the <filename>*.inf</filename> files located on the CD-ROM. This
-may not be possible, since the <filename>*.inf</filename> file might be missing. Unfortunately, vendors have now started
-to use their own installation programs. These installations packages are often in some Windows platform
-archive format. Additionally, the files may be re-named during the installation process. This makes it
-extremely difficult to identify the driver files required.
-</para>
-
-<para>
-<indexterm><primary>W32X86</primary></indexterm>
-Then you have the second option. Install the driver locally on a Windows client and
-investigate which filenames and paths it uses after they are installed. (You need to repeat
-this procedure for every client platform you want to support. We show it here for the
-<application>W32X86</application> platform only, a name used by Microsoft for all Windows NT/200x/XP
-clients.)
-</para>
-
-<para>
-<indexterm><primary>driver files</primary></indexterm>
-A good method to recognize the driver files is to print the test page from the driver's
-<guilabel>Properties</guilabel> dialog (<guilabel>General</guilabel> tab). Then look at the list of
-driver files named on the printout. You'll need to recognize what Windows (and Samba) are calling the
-<guilabel>Driver File</guilabel>, <guilabel>Data File</guilabel>, <guilabel>Config File</guilabel>,
-<guilabel>Help File</guilabel>, and (optionally) <guilabel>Dependent Driver Files</guilabel>
-(this may vary slightly for Windows NT). You need to note all filenames for the next steps.
-</para>
-
-<para>
-<indexterm><primary>rpcclient</primary></indexterm>
-<indexterm><primary>enumdrivers</primary></indexterm>
-<indexterm><primary>getdriver</primary></indexterm>
-Another method to quickly test the driver filenames and related paths is provided by the
-<command>rpcclient</command> utility. Run it with <command>enumdrivers</command> or with the
-<command>getdriver</command> subcommand, each at the <filename>3</filename> info level. In the following example,
-<emphasis>TURBO_XP</emphasis> is the name of the Windows PC (in this case it was a Windows XP Professional
-laptop). I installed the driver locally to TURBO_XP from a Samba server called <constant>KDE-BITSHOP</constant>.
-We could run an interactive <command>rpcclient</command> session; then we would get an
-<command>rpcclient /></command> prompt and would type the subcommands at this prompt. This is left as
-a good exercise for you. For now, we use <command>rpcclient</command> with the <option>-c</option>
-parameter to execute a single subcommand line and exit again. This is the method you use if you
-want to create scripts to automate the procedure for a large number of printers and drivers. Note the
-different quotation marks used to overcome the different spaces between words:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>rpcclient -U'Danka%xxxx' -c \
- 'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP</userinput>
-cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
-
-[Windows NT x86]
-Printer Driver Info 3:
- Version: [2]
- Driver Name: [Heidelberg Digimaster 9110 (PS)]
- Architecture: [Windows NT x86]
- Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL]
- Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd]
- Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL]
- Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP]
-
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll]
- Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF]
-
- Monitorname: []
- Defaultdatatype: []
-</screen></para>
-
-<para>
-<indexterm><primary>Driver File</primary></indexterm>
-<indexterm><primary>Driver Path</primary></indexterm>
-<indexterm><primary>WIN40</primary></indexterm>
-<indexterm><primary>W32X86</primary></indexterm>
-You may notice that this driver has quite a large number of <guilabel>Dependent files</guilabel>
-(there are worse cases, however). Also, strangely, the
-<guilabel>Driver File</guilabel> is tagged here
-<guilabel>Driver Path</guilabel>. We do not yet have support for the so-called
-<application>WIN40</application> architecture installed. This name is used by Microsoft for the Windows
-9x/Me platforms. If we want to support these, we need to install the Windows 9x/Me driver files in
-addition to those for <application>W32X86</application> (i.e., the Windows NT 2000/XP clients) onto a
-Windows PC. This PC can also host the Windows 9x/Me drivers, even if it runs on Windows NT, 2000, or XP.
-</para>
-
-<para>
-<indexterm><primary>UNC notation</primary></indexterm>
-<indexterm><primary>Windows Explorer</primary></indexterm>
-Since the <smbconfsection name="[print$]"/> share is usually accessible through the <guiicon>Network
-Neighborhood</guiicon>, you can also use the UNC notation from Windows Explorer to poke at it. The Windows
-9x/Me driver files will end up in subdirectory <filename>0</filename> of the <filename>WIN40</filename>
-directory. The full path to access them is <filename>\\WINDOWSHOST\print$\WIN40\0\</filename>.
-</para>
-
-<note><para>
-More recent drivers on Windows 2000 and Windows XP are installed into the <quote>3</quote> subdirectory
-instead of the <quote>2</quote>. The version 2 of drivers, as used in Windows NT, were running in kernel
-mode. Windows 2000 changed this. While it still can use the kernel mode drivers (if this is enabled by
-the Admin), its native mode for printer drivers is user mode execution. This requires drivers designed
-for this purpose. These types of drivers install into the <quote>3</quote> subdirectory.
-</para></note>
-</sect3>
-
-<sect3>
-<title>Obtaining Driver Files from Windows Client [print$] Shares</title>
-
-<para>
-Now we need to collect all the driver files we identified in our previous step. Where do we get them
-from? Well, why not retrieve them from the very PC and the same <smbconfsection name="[print$]"/>
-share that we investigated in our last step to identify the files? We can use <command>smbclient</command>
-to do this. We will use the paths and names that were leaked to us by <command>getdriver</command>. The
-listing is edited to include line breaks for readability:
-<screen>
-&rootprompt;<userinput>smbclient //TURBO_XP/print\$ -U'Danka%xxxx' \
- -c 'cd W32X86/2;mget HD*_de.* hd*ppd Hd*_de.* Hddm*dll HDN*Aux.DLL'</userinput>
-
-added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-Got a positive name query response from 10.160.50.8 ( 10.160.50.8 )
-Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
-<prompt>Get file Hddm91c1_de.ABD? </prompt><userinput>n</userinput>
-<prompt>Get file Hddm91c1_de.def? </prompt><userinput>y</userinput>
-getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def
-<prompt>Get file Hddm91c1_de.DLL? </prompt><userinput>y</userinput>
-getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL
-[...]
-</screen></para>
-
-<para>
-After this command is complete, the files are in our current local directory. You probably have noticed
-that this time we passed several commands to the <option>-c</option> parameter, separated by semicolons.
-This ensures that all commands are executed in sequence on the remote Windows server before
-<command>smbclient</command> exits again.
-</para>
-
-<para>
-<indexterm><primary>WIN40</primary></indexterm>
-Remember to repeat the procedure for the <application>WIN40</application> architecture should you need to
-support Windows 9x/Me/XP clients. Remember too, the files for these architectures are in the
-<filename>WIN40/0/</filename> subdirectory. Once this is complete, we can run <command>smbclient. .
-.put</command> to store the collected files on the Samba server's <smbconfsection name="[print$]"/> share.
-</para>
-</sect3>
-
-<sect3>
-<title>Installing Driver Files into [print$]</title>
-
-<para>
-We are now going to locate the driver files into the <smbconfsection name="[print$]"/> share. Remember, the
-UNIX path to this share has been defined previously in your &smb.conf; file. You also have created
-subdirectories for the different Windows client types you want to support. If, for example, your
-<smbconfsection name="[print$]"/> share maps to the UNIX path <filename>/etc/samba/drivers/</filename>, your
-driver files should now go here:
-</para>
-
-<itemizedlist>
- <listitem><para>
- For all Windows NT, 2000, and XP clients, <filename>/etc/samba/drivers/W32X86/</filename> but
- not (yet) into the <filename>2</filename> subdirectory.
- </para></listitem>
-
- <listitem><para>
- For all Windows 95, 98, and Me clients, <filename>/etc/samba/drivers/WIN40/</filename> but not
- (yet) into the <filename>0</filename> subdirectory.
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>smbclient</primary></indexterm>
-<indexterm><primary>getdriver</primary></indexterm>
-We again use smbclient to transfer the driver files across the network. We specify the same files
-and paths as were leaked to us by running <command>getdriver</command> against the original
-<emphasis>Windows</emphasis> install. However, now we are going to store the files into a
-<emphasis>Samba/UNIX</emphasis> print server's <smbconfsection name="[print$]"/> share.
-<screen>
-&rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c \
- 'cd W32X86; put HDNIS01_de.DLL; \
- put Hddm91c1_de.ppd; put HDNIS01U_de.DLL; \
- put HDNIS01U_de.HLP; put Hddm91c1_de.DLL; \
- put Hddm91c1_de.INI; put Hddm91c1KMMin.DLL; \
- put Hddm91c1_de.dat; put Hddm91c1_de.dat; \
- put Hddm91c1_de.def; put Hddm91c1_de.hre; \
- put Hddm91c1_de.vnd; put Hddm91c1_de.hlp; \
- put Hddm91c1_de_reg.HLP; put HDNIS01Aux.dll; \
- put HDNIS01_de.NTF'</userinput>
-
-added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
-Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
-putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL
-putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd
-putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL
-putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP
-putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL
-putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI
-putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL
-putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
-putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
-putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def
-putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre
-putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd
-putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp
-putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP
-putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll
-putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF
-</screen>
-<indexterm><primary>PPD</primary></indexterm>
-<indexterm><primary>PostScript driver</primary></indexterm>
-<indexterm><primary>adddriver</primary></indexterm>
-Whew &smbmdash; that was a lot of typing! Most drivers are a lot smaller &smbmdash; many have only three generic
-PostScript driver files plus one PPD. While we did retrieve the files from the <filename>2</filename>
-subdirectory of the <filename>W32X86</filename> directory from the Windows box, we do not put them
-(for now) in this same subdirectory of the Samba box. This relocation will automatically be done by the
-<command>adddriver</command> command, which we will run shortly (and do not forget to also put the files
-for the Windows 9x/Me architecture into the <filename>WIN40/</filename> subdirectory should you need them).
-</para>
-
-</sect3>
-
-<sect3>
-<title><command>smbclient</command> to Confirm Driver Installation</title>
-
-<para>
-<indexterm><primary>smbclient</primary></indexterm>
-<indexterm><primary>SSH</primary></indexterm>
-For now we verify that our files are there. This can be done with <command>smbclient</command>, too
-(but, of course, you can log in via SSH also and do this through a standard UNIX shell access):
-</para>
-
-<para><screen>
-&rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' \
- -c 'cd W32X86; pwd; dir; cd 2; pwd; dir'</userinput>
- added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
-Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.8a]
-
-Current directory is \\SAMBA-CUPS\print$\W32X86\
-. D 0 Sun May 4 03:56:35 2003
-.. D 0 Thu Apr 10 23:47:40 2003
-2 D 0 Sun May 4 03:56:18 2003
-HDNIS01Aux.dll A 15356 Sun May 4 03:58:59 2003
-Hddm91c1KMMin.DLL A 46966 Sun May 4 03:58:59 2003
-HDNIS01_de.DLL A 434400 Sun May 4 03:58:59 2003
-HDNIS01_de.NTF A 790404 Sun May 4 03:56:35 2003
-Hddm91c1_de.DLL A 876544 Sun May 4 03:58:59 2003
-Hddm91c1_de.INI A 101 Sun May 4 03:58:59 2003
-Hddm91c1_de.dat A 5044 Sun May 4 03:58:59 2003
-Hddm91c1_de.def A 428 Sun May 4 03:58:59 2003
-Hddm91c1_de.hlp A 37699 Sun May 4 03:58:59 2003
-Hddm91c1_de.hre A 323584 Sun May 4 03:58:59 2003
-Hddm91c1_de.ppd A 26373 Sun May 4 03:58:59 2003
-Hddm91c1_de.vnd A 45056 Sun May 4 03:58:59 2003
-HDNIS01U_de.DLL A 165888 Sun May 4 03:58:59 2003
-HDNIS01U_de.HLP A 19770 Sun May 4 03:58:59 2003
-Hddm91c1_de_reg.HLP A 228417 Sun May 4 03:58:59 2003
- 40976 blocks of size 262144. 709 blocks available
-
-Current directory is \\SAMBA-CUPS\print$\W32X86\2\
-. D 0 Sun May 4 03:56:18 2003
-.. D 0 Sun May 4 03:56:35 2003
-ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003
-laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003
-ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003
-ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003
-PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003
- 40976 blocks of size 262144. 709 blocks available
-</screen></para>
-
-<para>
-<indexterm><primary>Point'n'Print</primary></indexterm>
-<indexterm><primary>printer driver files</primary></indexterm>
-<indexterm><primary>print queue</primary></indexterm>
-Notice that there are already driver files present in the <filename>2</filename> subdirectory (probably from a
-previous installation). Once the files for the new driver are there too, you are still a few steps away from
-being able to use them on the clients. The only thing you could do now is retrieve them from a client just
-like you retrieve ordinary files from a file share, by opening print$ in Windows Explorer. But that wouldn't
-install them per Point'n'Print. The reason is that Samba does not yet know that these files are something
-special, namely <emphasis>printer driver files</emphasis>, and it does not know to which print queue(s) these
-driver files belong.
-</para>
-</sect3>
-
-<sect3>
-<title>Running <command>rpcclient</command> with <command>adddriver</command></title>
-
-<para>
-<indexterm><primary>adddriver</primary></indexterm>
-<indexterm><primary>register driver files</primary></indexterm>
-<indexterm><primary>TDB database</primary></indexterm>
-Next, you must tell Samba about the special category of the files you just uploaded into the
-<smbconfsection name="[print$]"/> share. This is done by the <command>adddriver</command>
-command. It will prompt Samba to register the driver files into its internal TDB database files. The
-following command and its output has been edited for readability:
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
- "dm9110:HDNIS01_de.DLL: \
- Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \
- NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
- Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
- Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
- HDNIS01Aux.dll,HDNIS01_de.NTF, \
- Hddm91c1_de_reg.HLP' SAMBA-CUPS</userinput>
-
-cmd = adddriver "Windows NT x86" \
- "dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL: \
- HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
- Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
- Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
- HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
-
-Printer Driver dm9110 successfully installed.
-</screen></para>
-
-<para>
-<indexterm><primary>NT_STATUS_UNSUCCESSFUL</primary></indexterm>
-<indexterm><primary>error message</primary></indexterm>
-<indexterm><primary>adddriver</primary></indexterm>
-After this step, the driver should be recognized by Samba on the print server. You need to be very
-careful when typing the command. Don't exchange the order of the fields. Some changes would lead to
-an <computeroutput>NT_STATUS_UNSUCCESSFUL</computeroutput> error message. These become obvious. Other
-changes might install the driver files successfully but render the driver unworkable. So take care!
-Hints about the syntax of the adddriver command are in the man page.
-provides a more detailed description, should you need it.
-</para>
-</sect3>
-
-<sect3>
-<title>Checking <command>adddriver</command> Completion</title>
-
-<para>
-One indication for Samba's recognition of the files as driver files is the <computeroutput>successfully
-installed</computeroutput> message. Another one is the fact that our files have been moved by the
-<command>adddriver</command> command into the <filename>2</filename> subdirectory. You can check this
-again with <command>smbclient</command>:
-<screen>
-&rootprompt;<userinput>smbclient //SAMBA-CUPS/print\$ -Uroot%xx \
- -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'</userinput>
- added interface ip=10.160.51.162 bcast=10.160.51.255 nmask=255.255.252.0
- Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
-
- Current directory is \\SAMBA-CUPS\print$\W32X86\
- . D 0 Sun May 4 04:32:48 2003
- .. D 0 Thu Apr 10 23:47:40 2003
- 2 D 0 Sun May 4 04:32:48 2003
- 40976 blocks of size 262144. 731 blocks available
-
- Current directory is \\SAMBA-CUPS\print$\W32X86\2\
- . D 0 Sun May 4 04:32:48 2003
- .. D 0 Sun May 4 04:32:48 2003
- DigiMaster.PPD A 148336 Thu Apr 24 01:07:00 2003
- ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003
- laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003
- ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003
- ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003
- PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003
- HDNIS01Aux.dll A 15356 Sun May 4 04:32:18 2003
- Hddm91c1KMMin.DLL A 46966 Sun May 4 04:32:18 2003
- HDNIS01_de.DLL A 434400 Sun May 4 04:32:18 2003
- HDNIS01_de.NTF A 790404 Sun May 4 04:32:18 2003
- Hddm91c1_de.DLL A 876544 Sun May 4 04:32:18 2003
- Hddm91c1_de.INI A 101 Sun May 4 04:32:18 2003
- Hddm91c1_de.dat A 5044 Sun May 4 04:32:18 2003
- Hddm91c1_de.def A 428 Sun May 4 04:32:18 2003
- Hddm91c1_de.hlp A 37699 Sun May 4 04:32:18 2003
- Hddm91c1_de.hre A 323584 Sun May 4 04:32:18 2003
- Hddm91c1_de.ppd A 26373 Sun May 4 04:32:18 2003
- Hddm91c1_de.vnd A 45056 Sun May 4 04:32:18 2003
- HDNIS01U_de.DLL A 165888 Sun May 4 04:32:18 2003
- HDNIS01U_de.HLP A 19770 Sun May 4 04:32:18 2003
- Hddm91c1_de_reg.HLP A 228417 Sun May 4 04:32:18 2003
- 40976 blocks of size 262144. 731 blocks available
-</screen></para>
-
-<para>
-Another verification is that the timestamp of the printing TDB files is now updated
-(and possibly their file size has increased).
-</para>
-</sect3>
-
-<sect3>
-<title>Check Samba for Driver Recognition</title>
-
-<para>
-<indexterm><primary>registered</primary></indexterm>
-Now the driver should be registered with Samba. We can easily verify this and will do so in a
-moment. However, this driver is not yet associated with a particular printer. We may check the driver
-status of the files by at least three methods:
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>Network Neighborhood</primary></indexterm>
-<indexterm><primary>Printers and Faxes</primary></indexterm>
-<indexterm><primary>printer icon</primary></indexterm>
-<indexterm><primary>Windows95/98/ME</primary></indexterm>
-<indexterm><primary>Windows NT/2000/XP</primary></indexterm>
- From any Windows client browse Network Neighborhood, find the Samba host, and open the Samba
- <guiicon>Printers and Faxes</guiicon> folder. Select any printer icon, right-click and select
- the printer <guimenuitem>Properties</guimenuitem>. Click the <guilabel>Advanced</guilabel>
- tab. Here is a field indicating the driver for that printer. A drop-down menu allows you to
- change that driver (be careful not to do this unwittingly). You can use this list to view
- all drivers known to Samba. Your new one should be among them. (Each type of client will
- see only its own architecture's list. If you do not have every driver installed for each platform,
- the list will differ if you look at it from Windows95/98/ME or Windows NT/2000/XP.)
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>Network Neighborhood</primary></indexterm>
- From a Windows 200x/XP client (not Windows NT) browse <guiicon>Network Neighborhood</guiicon>,
- search for the Samba server, open the server's <guiicon>Printers</guiicon> folder,
- and right-click on the white background (with no printer highlighted). Select <guimenuitem>Server
- Properties</guimenuitem>. On the <guilabel>Drivers</guilabel> tab you will see the new driver
- listed. This view enables you to also inspect the list of files belonging to that driver
- (this does not work on Windows NT, but only on Windows 2000 and Windows XP; Windows NT does not
- provide the <guimenuitem>Drivers</guimenuitem> tab). An alternative and much quicker method for
- Windows 2000/XP to start this dialog is by typing into a DOS box (you must of course adapt the
- name to your Samba server instead of <replaceable>SAMBA-CUPS</replaceable>):
- <screen>
- <userinput>rundll32 printui.dll,PrintUIEntry /s /t2 /n\\<replaceable>SAMBA-CUPS</replaceable></userinput>
- </screen>
- </para>
- </listitem>
-
- <listitem><para>
- From a UNIX prompt, run this command (or a variant thereof), where
- <replaceable>SAMBA-CUPS</replaceable> is the name of the Samba host and xxxx represents the
- actual Samba password assigned to root:
- <screen>
- <userinput>rpcclient -U'root%xxxx' -c 'enumdrivers' <replaceable>SAMBA-CUPS</replaceable></userinput>
- </screen>
- </para>
-
- <para>
- You will see a listing of all drivers Samba knows about. Your new one should be among
- them. But it is only listed under the <parameter>[Windows NT x86]</parameter> heading, not under
- <smbconfsection name="[Windows 4.0]"/>, since you didn't install that part. Or did you?
- In our example it is named <constant>dm9110</constant>. Note that the third column shows the other
- installed drivers twice, one time for each supported architecture. Our new driver only shows up
- for <application>Windows NT 4.0 or 2000</application>. To have it present for <application>Windows
- 95, 98, and Me</application>, you'll have to repeat the whole procedure with the WIN40 architecture
- and subdirectory.
- </para></listitem>
-</itemizedlist>
-</sect3>
-
-<sect3>
-<title>Specific Driver Name Flexibility</title>
-
-<para>
-<indexterm><primary>adddriver</primary></indexterm>
-You can name the driver as you like. If you repeat the <command>adddriver</command> step with the same
-files as before but with a different driver name, it will work the same:
-<screen>
-&rootprompt;<userinput>rpcclient -Uroot%xxxx \
- -c 'adddriver "Windows NT x86" \
- "mydrivername:HDNIS01_de.DLL: \
- Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \
- NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
- Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
- Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
- HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
- </userinput>
-
-cmd = adddriver "Windows NT x86" \
- "mydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\
- HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
- Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \
- Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
- HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
-
-Printer Driver mydrivername successfully installed.
-</screen></para>
-
-<para>
-<indexterm><primary>print queue</primary></indexterm>
-<indexterm><primary>rpcclient</primary></indexterm>
-<indexterm><primary>adddriver</primary></indexterm>
-You will be able to bind that driver to any print queue (however, you are responsible that
-you associate drivers to queues that make sense with respect to target printers). You cannot run the
-<command>rpcclient</command> <command>adddriver</command> command repeatedly. Each run consumes the
-files you had put into the <smbconfsection name="[print$]"/> share by moving them into the
-respective subdirectories, so you must execute an <command>smbclient ... put</command> command before
-each <command>rpcclient ... adddriver</command> command.
-</para>
-</sect3>
-
-<sect3>
-<title>Running <command>rpcclient</command> with <command>setdriver</command></title>
-
-<para>
-<indexterm><primary>mapping printer driver</primary></indexterm>
-<indexterm><primary>TDB</primary></indexterm>
-Samba needs to know which printer owns which driver. Create a mapping of the driver to a printer, and
-store this information in Samba's memory, the TDB files. The <command>rpcclient setdriver</command> command
-achieves exactly this:
-<screen>
-&rootprompt;<userinput>rpcclient -U'root%xxxx' -c 'setdriver dm9110 mydrivername' <replaceable>SAMBA-CUPS</replaceable></userinput>
- cmd = setdriver dm9110 mydrivername
-
-Successfully set dm9110 to driver mydrivername.
-</screen></para>
-
-<para>
-Ah, no, I did not want to do that. Repeat, this time with the name I intended:
-<screen>
-&rootprompt;<userinput>rpcclient -U'root%xxxx' -c 'setdriver dm9110 dm9110' <replaceable>SAMBA-CUPS</replaceable></userinput>
- cmd = setdriver dm9110 dm9110
-Successfully set dm9110 to driver dm9110.
-</screen></para>
-
-<para>
-The syntax of the command is:
-<screen>
-<userinput>rpcclient -U'root%<replaceable>sambapassword</replaceable>' -c 'setdriver <replaceable>printername</replaceable> \
- <replaceable>drivername</replaceable>' <replaceable>SAMBA-Hostname</replaceable></userinput>.
-</screen>
-Now we have done most of the work, but not all of it.
-</para>
-
-<note><para>
-The <command>setdriver</command> command will only succeed if the printer is already known to Samba. A
-bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba,
-or at least send an HUP signal to all running smbd processes to work around this: <userinput>kill -HUP
-`pidof smbd`</userinput>.
-</para></note>
-</sect3>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Client Driver Installation Procedure</title>
-
-<para>
-As Don Quixote said, <quote>The proof of the pudding is in the eating.</quote> The proof
-for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is
-not as straightforward as it may seem. Read on.
-</para>
-
-<sect2>
-<title>First Client Driver Installation</title>
-
-<para>
-Especially important is the installation onto the first client PC (for each architectural platform
-separately). Once this is done correctly, all further clients are easy to set up and shouldn't need further
-attention. What follows is a description for the recommended first procedure. You now work from a client
-workstation. You should check that your connection is not unwittingly mapped to <emphasis>bad
-user</emphasis> nobody. In a DOS box type:
-</para>
-
-<para><userinput>net use \\<replaceable>SAMBA-SERVER</replaceable>\print$ /user:root</userinput></para>
-
-<para>
-Replace root, if needed, by another valid printer administrator user as given in
-the definition. Should you already be connected as a different user, you will get an error message. There
-is no easy way to get rid of that connection, because Windows does not seem to know a concept of logging
-off from a share connection (do not confuse this with logging off from the local workstation; that is
-a different matter). On Windows NT/200x, you can force a logoff from all smb/cifs connections by restarting the
-<emphasis>workstation</emphasis> service. You can try to close all Windows file explorers and Internet Explorer for
-Windows. As a last resort, you may have to reboot. Make sure there is no automatic reconnection set up. It may be
-easier to go to a different workstation and try from there. After you have made sure you are connected
-as a printer admin user (you can check this with the <command>smbstatus</command> command on Samba),
-do this from the Windows workstation:
-</para>
-
-<procedure>
- <step><para>
- Open <guiicon>Network Neighborhood</guiicon>.
- </para></step>
-
- <step><para>
- Browse to Samba server.
- </para></step>
-
- <step><para>
- Open its <guiicon>Printers and Faxes</guiicon> folder.
- </para></step>
-
- <step><para>
- Highlight and right-click on the printer.
- </para></step>
-
- <step><para>
- Select <guimenuitem>Connect</guimenuitem> (for Windows NT4/200x
- it is possibly <guimenuitem>Install</guimenuitem>).
- </para></step>
-</procedure>
-
-<para>
-A new printer (named <replaceable>printername</replaceable> on Samba server) should now have
-appeared in your <emphasis>local</emphasis> Printer folder (check <guimenu>Start</guimenu> ->
-<guimenuitem>Settings</guimenuitem> -> <guimenuitem>Control Panel</guimenuitem> -> <guiicon>Printers
-and Faxes</guiicon>).
-</para>
-
-<para>
-<indexterm><primary>print test page</primary></indexterm>
-Most likely you are tempted to try to print a test page. After all, you now can open the printer
-properties, and on the <guimenu>General</guimenu> tab there is a button offering to do just that. But
-chances are that you get an error message saying "<literal>Unable to print Test Page</literal>." The
-reason might be that there is not yet a valid device mode set for the driver or that the <quote>printer
-driver data</quote> set is still incomplete.
-</para>
-
-<para>
-You must make sure that a valid <parameter>device mode</parameter> is set for the
-driver. We now explain what that means.
-</para>
-</sect2>
-
-<sect2 id="prt-modeset">
-<title>Setting Device Modes on New Printers</title>
-
-<para>
-For a printer to be truly usable by a Windows NT/200x/XP client, it must possess:
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>device mode</primary></indexterm>
- A valid <emphasis>device mode</emphasis> generated by the driver for the printer (defining things
- like paper size, orientation and duplex settings).
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>printer driver data</primary></indexterm>
- A complete set of <emphasis>printer driver data</emphasis> generated by the driver.
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>ntprinters.tdb</primary></indexterm>
-<indexterm><primary>ntdrivers.tdb</primary></indexterm>
-<indexterm><primary>printing.tdb</primary></indexterm>
-<indexterm><primary>ntforms.tdb</primary></indexterm>
-<indexterm><primary>TDB database files</primary></indexterm>
-If either of these is incomplete, the clients can produce less than optimal output at best. In the
-worst cases, unreadable garbage or nothing at all comes from the printer, or it produces a harvest of
-error messages when attempting to print. Samba stores the named values and all printing-related information in
-its internal TDB database files <filename>(ntprinters.tdb</filename>, <filename>ntdrivers.tdb</filename>,
-<filename>printing.tdb</filename>, and <filename>ntforms.tdb</filename>).
-</para>
-
-<para>
-The device mode and the set of printer driver data are basically collections
-of settings for all print queue properties, initialized in a sensible way. Device modes and
-printer driver data should initially be set on the print server (the Samba host) to healthy
-values so the clients can start to use them immediately. How do we set these initial healthy values?
-This can be achieved by accessing the drivers remotely from an NT (or 200x/XP) client, as discussed
-in the following paragraphs.
-</para>
-
-<para>
-Be aware that a valid device mode can only be initiated by a printer administrator or root
-(the reason should be obvious). Device modes can be correctly set only by executing the printer driver program
-itself. Since Samba cannot execute this Win32 platform driver code, it sets this field initially to NULL
-(which is not a valid setting for clients to use). Fortunately, most drivers automatically generate the
-printer driver data that is needed when they are uploaded to the <smbconfsection name="[print$]"/> share with
-the help of the APW or rpcclient.
-</para>
-
-<para>
-The generation and setting of a first valid device mode, however, requires some tickling from a client
-to set it on the Samba server. The easiest means of doing so is to simply change the page orientation on
-the server's printer. This executes enough of the printer driver program on the client for the desired
-effect to happen and feeds back the new device mode to our Samba server. You can use the native Windows
-NT/200x/XP printer properties page from a Window client for this:
-</para>
-
-<procedure>
-<title>Procedure to Initialize the Printer Driver Settings</title>
- <step><para>
- Browse the <guiicon>Network Neighborhood</guiicon>.
- </para></step>
-
- <step><para>
- Find the Samba server.
- </para></step>
-
- <step><para>
- Open the Samba server's <guiicon>Printers and Faxes</guiicon> folder.
- </para></step>
-
- <step><para>
- Highlight the shared printer in question.
- </para></step>
-
- <step><para>
- Right-click on the printer (you may already be here if you followed the last section's description).
- </para></step>
-
- <step><para>
- At the bottom of the context menu select <guimenu>Properties</guimenu> (if the menu still offers the
- <guimenuitem>Connect</guimenuitem> entry further above, you
- need to click on that one first to achieve the driver
- installation, as shown in the last section).
- </para></step>
-
- <step><para>
- Go to the <guilabel>Advanced</guilabel> tab; click on <guibutton>Printing Defaults</guibutton>.
- </para></step>
-
- <step><para>
- Change the <guimenuitem>Portrait</guimenuitem> page setting to <guimenuitem>Landscape</guimenuitem> (and back).
- </para></step>
-
- <step><para>
- Make sure to apply changes between swapping the page orientation to cause the change to actually take effect.
- </para></step>
-
- <step><para>
- While you are at it, you may also want to set the desired printing defaults here, which then apply to all future
- client driver installations.
- </para></step>
-</procedure>
-
-<para>
-This procedure executes the printer driver program on the client platform and feeds back the correct
-device mode to Samba, which now stores it in its TDB files. Once the driver is installed on the client,
-you can follow the analogous steps by accessing the <emphasis>local</emphasis> <guiicon>Printers</guiicon>
-folder, too, if you are a Samba printer admin user. From now on, printing should work as expected.
-</para>
-
-<para>
-<indexterm><primary>default devmode</primary></indexterm>
-Samba includes a service-level parameter name <parameter>default devmode</parameter> for generating a default
-device mode for a printer. Some drivers function well with Samba's default set of properties. Others
-may crash the client's spooler service. So use this parameter with caution. It is always better to have
-the client generate a valid device mode for the printer and store it on the server for you.
-</para>
-</sect2>
-
-<sect2>
-<title>Additional Client Driver Installation</title>
-
-<para>
-<indexterm><primary>additional driver</primary></indexterm>
-Every additional driver may be installed in the same way as just described. Browse <command>Network
-Neighborhood</command>, open the <guiicon>Printers</guiicon> folder on Samba server, right-click on
-<guiicon>Printer</guiicon>, and choose <guimenuitem>Connect...</guimenuitem>. Once this completes (should be
-not more than a few seconds, but could also take a minute, depending on network conditions), you should find
-the new printer in your client workstation local <guiicon>Printers and Faxes</guiicon> folder.
-</para>
-
-<para>
-You can also open your local <guiicon>Printers and Faxes</guiicon> folder by
-using this command on Windows 200x/XP Professional workstations:
-<screen>
-<userinput>rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder</userinput>
-</screen>
-or this command on Windows NT 4.0 workstations:
-<indexterm><primary>rundll32</primary></indexterm>
-<screen>
-<userinput>rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2</userinput>
-</screen>
-</para>
-
-<para>
-You can enter the commands either inside a <guilabel>DOS box</guilabel> window or in the <guimenuitem>Run
-command...</guimenuitem> field from the <guimenu>Start</guimenu> menu.
-</para>
-</sect2>
-
-<sect2>
-<title>Always Make First Client Connection as root or printer administrator</title>
-
-<para>
-After you installed the driver on the Samba server (in its <smbconfsection name="[print$]"/> share), you
-should always make sure that your first client installation completes correctly. Make it a habit for yourself
-to build the very first connection from a client as a printer administrator"/>. This is to make
-sure that:
-</para>
-
-<itemizedlist>
- <listitem><para>
- A first valid <emphasis>device mode</emphasis> is really initialized (see above <link
- linkend="prt-modeset">Setting Device Modes on New Printers</link>) for more explanation details).
- </para></listitem>
-
- <listitem><para>
- The default print settings of your printer for all further client installations are as you want them.
- </para></listitem>
-</itemizedlist>
-
-<para>
-Do this by changing the orientation to landscape, click on <guiicon>Apply</guiicon>, and then change it
-back again. Next, modify the other settings (for example, you do not want the default media size set to
-<guiicon>Letter</guiicon> when you are all using <guiicon>A4</guiicon>, right? You may want to set the
-printer for <guiicon>duplex</guiicon> as the default, and so on).
-</para>
-
-<para>
-<indexterm><primary>runas</primary></indexterm>
-To connect as root to a Samba printer, try this command from a Windows 200x/XP DOS box command prompt:
-<screen>
-&dosprompt;<userinput>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n
- \\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printername</replaceable>"</userinput>
-</screen>
-</para>
-
-<para>
-You will be prompted for <constant>root</constant>'s Samba password; type it, wait a few seconds, click on
-<guibutton>Printing Defaults</guibutton>, and proceed to set the job options that should be used as defaults
-by all clients. Alternatively, instead of root you can give one other member printer adminadministrator
-privileges.
-</para>
-
-<para>
-Now all the other users downloading and installing the driver the same way (using
-<literal>Point'n'Print</literal>) will have the same defaults set for them. If you miss this step, you'll get a
-lot of help desk calls from your users, but maybe you like to talk to people.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Other Gotchas</title>
-
-<para>
-Your driver is installed. It is now ready for Point'n'Print installation by the clients. You may have tried to
-download and use it on your first client machine, but wait. Let's make sure you are acquainted first with a
-few tips and tricks you may find useful. For example, suppose you did not set the defaults on the printer, as
-advised in the preceding paragraphs. Your users complain about various issues (such as, <quote>We need to set
-the paper size for each job from Letter to A4 and it will not store it</quote>).
-</para>
-
-<sect2>
-<title>Setting Default Print Options for Client Drivers</title>
-
-<para>
-The last sentence might be viewed with mixed feelings by some users and Admins. They have struggled for hours
-and could not arrive at a point where their settings seemed to be saved. It is not their fault. The confusing
-thing is that in the multitabbed dialog that pops up when you right-click on the printer name and select
-<guimenuitem>Properties</guimenuitem>, you can arrive at two dialogs that appear identical, each claiming that
-they help you to set printer options in three different ways. Here is the definitive answer to the Samba
-default driver setting FAQ:
-</para>
-
-<formalpara><title><quote>I can not set and save default print options
-for all users on Windows 200x/XP. Why not?</quote></title>
-
-<para>
-How are you doing it? I bet the wrong way. (It is not easy to find out, though.) There are three different
-ways to bring you to a dialog that seems to set everything. All three dialogs look the same, but only one of
-them does what you intend. You need to be Administrator or Print Administrator to do this for all users. Here
-is how I reproduce it in an XP Professional:
-</para>
-
-<orderedlist numeration="upperalpha">
- <listitem><para>The first <quote>wrong</quote> way:
- <orderedlist numeration="arabic">
- <listitem><para>Open the <guiicon>Printers</guiicon> folder.</para></listitem>
-
- <listitem><para>Right-click on the printer (<emphasis>remoteprinter on cupshost</emphasis>) and
- select in context menu <guimenu>Printing Preferences...</guimenu>.</para></listitem>
-
- <listitem><para>Look at this dialog closely and remember what it looks like.</para></listitem>
- </orderedlist></para></listitem>
-
- <listitem><para>The second <quote>wrong</quote> way:
- <orderedlist numeration="arabic">
- <listitem><para>Open the <guimenu>Printers</guimenu> folder.</para></listitem>
-
- <listitem><para>Right-click on the printer (<emphasis>remoteprinter on
- cupshost</emphasis>) and select in the context menu
- <guimenuitem>Properties</guimenuitem></para></listitem>.
-
- <listitem><para>Click on the <guilabel>General</guilabel>
- tab.</para></listitem>
-
- <listitem><para>Click on the <guibutton>Printing
- Preferences...</guibutton> button.</para></listitem>
-
- <listitem><para>A new dialog opens. Keep this dialog open and go back
- to the parent dialog.</para></listitem>
- </orderedlist>
- </para></listitem>
-
- <listitem><para>
- The third and correct way (should you do this from the beginning, just carry out steps 1
- and 2 from the second method above):
- </para>
-
- <orderedlist numeration="arabic">
- <listitem><para>Click on the <guilabel>Advanced</guilabel>
- tab. (If everything is <quote>grayed out,</quote> then you are not logged
- in as a user with enough privileges.)</para></listitem>
-
- <listitem><para>Click on the <guibutton>Printing
- Defaults</guibutton> button.</para></listitem>
-
- <listitem><para>On any of the two new tabs,
- click on the
- <guilabel>Advanced</guilabel> button.</para></listitem>
-
- <listitem><para>A new dialog opens. Compare
- this one to the other. Are they
- identical when you compare one from
- <quote>B.5</quote> and one from A.3?</para></listitem>
- </orderedlist>
- </listitem>
-</orderedlist>
-
-<para>
-Do you see any difference in the two settings dialogs? I do not either. However, only the last one, which you
-arrived at with steps C.1 through C.6 will permanently save any settings which will then become the defaults
-for new users. If you want all clients to have the same defaults, you need to conduct these steps as
-administrator before a client downloads the driver (the clients can
-later set their own per-user defaults by following procedures A or B above). Windows 200x/XP allow per-user
-default settings and the ones the administrator gives them before they set up their own. The parents of the
-identical-looking dialogs have a slight difference in their window names; one is called
-<computeroutput>Default Print Values for Printer Foo on Server Bar</computeroutput> (which is the one you
-need) and the other is called <quote><computeroutput>Print Settings for Printer Foo on Server
-Bar</computeroutput></quote>. The last one is the one you arrive at when you right-click on the printer and
-select <guimenuitem>Print Settings...</guimenuitem>. This is the one that you were taught to use back in the
-days of Windows NT, so it is only natural to try the same way with Windows 200x/XP. You would not dream that
-there is now a different path to arrive at an identical-looking, but functionally different, dialog to set
-defaults for all users.
-</para></formalpara>
-
-<tip><para>Try (on Windows 200x/XP) to run this command (as a user with the right privileges):
-<indexterm><primary>rundll32</primary></indexterm>
-</para>
-
-<para><userinput>
-rundll32 printui.dll,PrintUIEntry /p /t3 /n\\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
-</userinput></para>
-
-<para>
-To see the tab with the <guilabel>Printing Defaults</guilabel> button (the one you need), also run this command:
-</para>
-
-<para><userinput>
-rundll32 printui.dll,PrintUIEntry /p /t0 /n\\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
-</userinput></para>
-
-<para>
-To see the tab with the <guilabel>Printing Preferences</guilabel>
-button (the one that does not set systemwide defaults), you can
-start the commands from inside a DOS box or from <guimenu>Start</guimenu> -> <guimenuitem>Run</guimenuitem>.
-</para>
-</tip>
-
-</sect2>
-
-<sect2>
-<title>Supporting Large Numbers of Printers</title>
-
-<para>
-One issue that has arisen during the recent development phase of Samba is the need to support driver
-downloads for hundreds of printers. Using Windows NT APW for this task is somewhat awkward (to say the least). If
-you do not want to acquire RSS pains from the printer installation clicking orgy alone, you need
-to think about a non-interactive script.
-</para>
-
-<para>
-If more than one printer is using the same driver, the <command>rpcclient setdriver</command>
-command can be used to set the driver associated with an installed queue. If the driver is uploaded to
-<smbconfsection name="[print$]"/> once and registered with the printing TDBs, it can be used by
-multiple print queues. In this case, you just need to repeat the <command>setprinter</command> subcommand of
-<command>rpcclient</command> for every queue (without the need to conduct the <command>adddriver</command>
-repeatedly). The following is an example of how this can be accomplished:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumdrivers'</userinput>
- cmd = enumdrivers
-
- [Windows NT x86]
- Printer Driver Info 1:
- Driver Name: [infotec IS 2075 PCL 6]
-
- Printer Driver Info 1:
- Driver Name: [DANKA InfoStream]
-
- Printer Driver Info 1:
- Driver Name: [Heidelberg Digimaster 9110 (PS)]
-
- Printer Driver Info 1:
- Driver Name: [dm9110]
-
- Printer Driver Info 1:
- Driver Name: [mydrivername]
-
- [....]
-</screen>
-
-<screen>
-&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
- cmd = enumprinters
- flags:[0x800000]
- name:[\\SAMBA-CUPS\dm9110]
- description:[\\SAMBA-CUPS\dm9110,,110ppm HiVolume DANKA Stuttgart]
- comment:[110 ppm HiVolume DANKA Stuttgart]
- [....]
-</screen>
-
-<screen>
-&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c \
- 'setdriver <replaceable>dm9110</replaceable> "<replaceable>Heidelberg Digimaster 9110 (PS)</replaceable>"'</userinput>
- cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD)
- Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS).
-</screen>
-
-<screen>
-&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
- cmd = enumprinters
- flags:[0x800000]
- name:[\\SAMBA-CUPS\dm9110]
- description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),\
- 110ppm HiVolume DANKA Stuttgart]
- comment:[110ppm HiVolume DANKA Stuttgart]
- [....]
-</screen>
-
-<screen>
-&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'setdriver <replaceable>dm9110</replaceable> <replaceable>mydrivername</replaceable>'</userinput>
- cmd = setdriver dm9110 mydrivername
- Successfully set dm9110 to mydrivername.
-</screen>
-
-<screen>
-&rootprompt;<userinput>rpcclient <replaceable>SAMBA-CUPS</replaceable> -U root%<replaceable>secret</replaceable> -c 'enumprinters'</userinput>
- cmd = enumprinters
- flags:[0x800000]
- name:[\\SAMBA-CUPS\dm9110]
- description:[\\SAMBA-CUPS\dm9110,mydrivername,\
- 110ppm HiVolume DANKA Stuttgart]
- comment:[110ppm HiVolume DANKA Stuttgart]
- [....]
-</screen></para>
-
-<para>
-It may not be easy to recognize that the first call to <command>enumprinters</command> showed the
-<quote>dm9110</quote> printer with an empty string where the driver should have been listed (between
-the two commas in the description field). After the <command>setdriver</command> command
-succeeds, all is well.
-</para>
-</sect2>
-
-<sect2>
-<title>Adding New Printers with the Windows NT APW</title>
-
-<para>
-By default, Samba exhibits all printer shares defined in &smb.conf; in the <guiicon>Printers</guiicon>
-folder. Also located in this folder is the Windows NT Add Printer Wizard icon. The APW will be shown only if:
-</para>
-
-<itemizedlist>
- <listitem><para>
- The connected user is able to successfully execute an <command>OpenPrinterEx(\\server)</command> with
- administrative privileges (i.e., root or a printer administrator).
- </para>
-
- <tip><para> Try this from a Windows 200x/XP DOS box command prompt:
- </para>
-
- <para><userinput>
- runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\<replaceable>SAMBA-SERVER</replaceable>\<replaceable>printersharename</replaceable>
- </userinput></para>
-
- <para>
- Click on <guibutton>Printing Preferences</guibutton>.
- </para></tip></listitem>
-
- <listitem><para>... contains the setting
- <smbconfoption name="show add printer wizard">yes</smbconfoption> (the
- default).</para></listitem>
-</itemizedlist>
-
-<para>
-The APW can do various things:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Upload a new driver to the Samba <smbconfsection name="[print$]"/> share.
- </para></listitem>
-
- <listitem><para>
- Associate an uploaded driver with an existing (but still driverless) print queue.
- </para></listitem>
-
- <listitem><para>
- Exchange the currently used driver for an existing print queue with one that has been uploaded before.
- </para></listitem>
-
- <listitem><para>
- Add an entirely new printer to the Samba host (only in conjunction with a working
- <smbconfoption name="add printer command"/>. A corresponding
- <smbconfoption name="delete printer command"/> for removing entries from the
- <guiicon>Printers</guiicon> folder may also be provided).
- </para></listitem>
-</itemizedlist>
-
-<para>
-The last one (add a new printer) requires more effort than the previous ones. To use the APW to successfully
-add a printer to a Samba server, the <smbconfoption name="add printer command"/> must have a defined value.
-The program hook must successfully add the printer to the UNIX print system (i.e., to
-<filename>/etc/printcap</filename>, <filename>/etc/cups/printers.conf</filename> or other appropriate files)
-and to &smb.conf; if necessary.
-</para>
-
-<para>
-When using the APW from a client, if the named printer share does not exist, smbd will execute the
-<smbconfoption name="add printer command"/> and reparse to attempt to locate the new printer share. If the
-share is still not defined, an error of "<errorname>Access Denied"</errorname> is returned to the client. The
-<smbconfoption name="add printer command"/> is executed under the context of the connected user, not
-necessarily a root account. A <smbconfoption name="map to guest">bad user</smbconfoption> may have connected
-you unwittingly under the wrong privilege. You should check it by using the <command>smbstatus</command>
-command.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Error Message: <quote>Cannot connect under a different Name</quote></title>
-
-<para>
-Once you are connected with the wrong credentials, there is no means to reverse the situation other than
-to close all Explorer windows, and perhaps reboot.
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>net use</primary></indexterm>
- The <command>net use \\SAMBA-SERVER\sharename /user:root</command> gives you an error message:
- <quote>Multiple connections to a server or a shared resource by the same user utilizing
- several user names are not allowed. Disconnect all previous connections to the server,
- esp. the shared resource, and try again.</quote>
- </para></listitem>
-
- <listitem><para>
- Every attempt to <quote>connect a network drive</quote> to <filename>\\SAMBASERVER\\print$</filename>
- to <constant>z:</constant> is countered by the pertinacious message: <quote>This
- network folder is currently connected under different credentials (username and password).
- Disconnect first any existing connection to this network share in order to connect again under
- a different username and password</quote>.
- </para></listitem>
-</itemizedlist>
-
-<para>
-So you close all connections. You try again. You get the same message. You check from the Samba side, using
-<command>smbstatus</command>. Yes, there are more connections. You kill them all. The client still gives you
-the same error message. You watch the smbd.log file on a high debug level and try reconnect. Same error
-message, but not a single line in the log. You start to wonder if there was a connection attempt at all. You
-run ethereal and tcpdump while you try to connect. Result: not a single byte goes on the wire. Windows still
-gives the error message. You close all Explorer windows and start it again. You try to connect &smbmdash; and
-this times it works! Windows seems to cache connection information somewhere and does not keep it up to date
-(if you are unlucky, you might need to reboot to get rid of the error message).
-</para>
-
-<para>
-The easiest way to forcefully terminate all connections from your client to a server is by executing:
-<screen>
-&dosprompt; net use * /delete
-</screen>
-This will also disconnect all mapped drives and will allow you create fresh connection as required.
-</para>
-</sect2>
-
-<sect2>
-<title>Take Care When Assembling Driver Files</title>
-
-<para>
-You need to be extremely careful when you take notes about the files belonging to a particular
-driver. Don't confuse the files for driver version <quote>0</quote> (for Windows 9x/Me, going into
-<filename>[print$]/WIN/0/</filename>), driver version <filename>2</filename> (kernel mode driver for Windows NT,
-going into <filename>[print$]/W32X86/2/</filename>; may be used on Windows 200x/XP also), and
-driver version <quote>3</quote> (non-kernel mode driver going into <filename>[print$]/W32X86/3/</filename>;
-cannot be used on Windows NT). Quite often these different driver versions contain
-files that have the same name but actually are very different. If you look at them from
-the Windows Explorer (they reside in <filename>%WINDOWS%\system32\spool\drivers\W32X86\</filename>),
-you will probably see names in capital letters, while an <command>enumdrivers</command> command from Samba
-would show mixed or lowercase letters, so it is easy to confuse them. If you install them manually using
-<command>rpcclient</command> and subcommands, you may even succeed without an error message. Only later,
-when you try install on a client, you will encounter error messages like <computeroutput>This server
-has no appropriate driver for the printer</computeroutput>.
-</para>
-
-<para>
-Here is an example. You are invited to look closely at the various files, compare their names and
-their spelling, and discover the differences in the composition of the version 2 and 3 sets. Note: the
-version 0 set contained 40 <parameter>Dependentfiles</parameter>, so I left it out for space reasons:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>rpcclient -U 'Administrator%<replaceable>secret</replaceable>' -c 'enumdrivers 3' 10.160.50.8 </userinput>
-
- Printer Driver Info 3:
- Version: [3]
- Driver Name: [Canon iR8500 PS3]
- Architecture: [Windows NT x86]
- Driver Path: [\\10.160.50.8\print$\W32X86\3\cns3g.dll]
- Datafile: [\\10.160.50.8\print$\W32X86\3\iR8500sg.xpd]
- Configfile: [\\10.160.50.8\print$\W32X86\3\cns3gui.dll]
- Helpfile: [\\10.160.50.8\print$\W32X86\3\cns3g.hlp]
-
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aucplmNT.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\ucs32p.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\tnl32.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussdrv.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cnspdc.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussapi.dat]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3407.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\CnS3G.cnt]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBAPI.DLL]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBIPC.DLL]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcview.exe]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcdspl.exe]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcedit.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm.exe]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcspl.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cfine32.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcr407.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\Cpcqm407.hlp]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm407.cnt]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3ggr.dll]
-
- Monitorname: []
- Defaultdatatype: []
-
- Printer Driver Info 3:
- Version: [2]
- Driver Name: [Canon iR5000-6000 PS3]
- Architecture: [Windows NT x86]
- Driver Path: [\\10.160.50.8\print$\W32X86\2\cns3g.dll]
- Datafile: [\\10.160.50.8\print$\W32X86\2\IR5000sg.xpd]
- Configfile: [\\10.160.50.8\print$\W32X86\2\cns3gui.dll]
- Helpfile: [\\10.160.50.8\print$\W32X86\2\cns3g.hlp]
-
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\AUCPLMNT.DLL]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussdrv.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cnspdc.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussapi.dat]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3407.dll]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\CnS3G.cnt]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBAPI.DLL]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBIPC.DLL]
- Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3gum.dll]
-
- Monitorname: [CPCA Language Monitor2]
- Defaultdatatype: []
-
-</screen></para>
-
-<para>
-If we write the <quote>version 2</quote> files and the <quote>version 3</quote> files
-into different text files and compare the result, we see this
-picture:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>sdiff 2-files 3-files</userinput>
-
-<![CDATA[
- cns3g.dll cns3g.dll
- iR8500sg.xpd iR8500sg.xpd
- cns3gui.dll cns3gui.dll
- cns3g.hlp cns3g.hlp
- AUCPLMNT.DLL | aucplmNT.dll
- > ucs32p.dll
- > tnl32.dll
- aussdrv.dll aussdrv.dll
- cnspdc.dll cnspdc.dll
- aussapi.dat aussapi.dat
- cns3407.dll cns3407.dll
- CnS3G.cnt CnS3G.cnt
- NBAPI.DLL NBAPI.DLL
- NBIPC.DLL NBIPC.DLL
- cns3gum.dll | cpcview.exe
- > cpcdspl.exe
- > cpcqm.exe
- > cpcspl.dll
- > cfine32.dll
- > cpcr407.dll
- > Cpcqm407.hlp
- > cpcqm407.cnt
- > cns3ggr.dll
-]]>
-</screen>
-
-Do not be fooled! Driver files for each version with identical
-names may be different in their content, as you can see from this size
-comparison:
-</para>
-
-<para><screen>
-&rootprompt;<userinput>for i in cns3g.hlp cns3gui.dll cns3g.dll; do \
- smbclient //10.160.50.8/print\$ -U 'Administrator%xxxx' \
- -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i"; \
- done</userinput>
-
- CNS3G.HLP A 122981 Thu May 30 02:31:00 2002
- CNS3G.HLP A 99948 Thu May 30 02:31:00 2002
-
- CNS3GUI.DLL A 1805824 Thu May 30 02:31:00 2002
- CNS3GUI.DLL A 1785344 Thu May 30 02:31:00 2002
-
- CNS3G.DLL A 1145088 Thu May 30 02:31:00 2002
- CNS3G.DLL A 15872 Thu May 30 02:31:00 2002
-</screen></para>
-
-<para>
-In my example were even more differences than shown here. Conclusion: you must be careful to select the
-correct driver files for each driver version. Don't rely on the names alone, and don't interchange files
-belonging to different driver versions.
-</para>
-</sect2>
-
-<sect2>
-<title>Samba and Printer Ports</title>
-
-<para>
-<indexterm><primary>LPT1:</primary></indexterm>
-<indexterm><primary>COM1:</primary></indexterm>
-<indexterm><primary>FILE:</primary></indexterm>
-<indexterm><primary>available port</primary></indexterm>
-Windows NT/2000 print servers associate a port with each printer. These normally take the form of
-<filename>LPT1:</filename>, <filename>COM1:</filename>, <filename>FILE:</filename>, and so on. Samba must also
-support the concept of ports associated with a printer. By default, only one printer port, named <quote>Samba
-Printer Port</quote>, exists on a system. Samba does not really need such a <quote>port</quote> in order to
-print; rather it is a requirement of Windows clients. They insist on being told about an available port when
-they request this information; otherwise, they throw an error message at you. So Samba fakes the port
-information to keep the Windows clients happy.
-</para>
-
-<para>
-<indexterm><primary>Printer Pooling</primary></indexterm>
-Samba does not support the concept of <constant>Printer Pooling</constant> internally either. Printer
-pooling assigns a logical printer to multiple ports as a form of load balancing or failover.
-</para>
-
-<para>
-If you require multiple ports to be defined for some reason or another (my users and my boss should not know
-that they are working with Samba), configure the <smbconfoption name="enumports command"/>,
-which can be used to define an external program that generates a listing of ports on a system.
-</para>
-</sect2>
-
-<sect2>
-<title>Avoiding Common Client Driver Misconfiguration</title>
-
-<para>
-So now the printing works, but there are still problems. Most jobs print well, some do not print at
-all. Some jobs have problems with fonts, which do not look good. Some jobs print fast and some
-are dead-slow. We cannot cover it all, but we want to encourage you to read the brief paragraph about
-<quote>Avoiding the Wrong PostScript Driver Settings</quote> in <link linkend="CUPS-printing">CUPS Printing
-Chapter</link>, <link linkend="cups-avoidps1">Avoiding Critical PostScript Driver Settings on the
-Client</link>.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>The Imprints Toolset</title>
-
-<para>
-<indexterm><primary>Imprints</primary></indexterm>
-The Imprints tool set provides a UNIX equivalent of the Windows NT APW. For complete information, please
-refer to the <ulink url="http://imprints.sourceforge.net/">Imprints</ulink> Web site as well as the
-documentation included with the Imprints source distribution. This section provides only a brief introduction
-to the features of Imprints.
-</para>
-
-<para>
-Unfortunately, the Imprints toolset is no longer maintained. As of December 2000, the project is in
-need of a new maintainer. The most important skill to have is Perl coding and an interest in MS-RPC-based
-printing used in Samba. If you wish to volunteer, please coordinate your efforts on the Samba technical
-mailing list. The toolset is still in usable form, but only for a series of older printer models where
-there are prepared packages to use. Packages for more up-to-date print devices are needed if Imprints
-should have a future. Information regarding the Imprints toolset can be obtained from the <ulink
-url="http://imprints.sourceforge.net/">Imprints</ulink> home page.
-</para>
-
-<sect2>
-<title>What Is Imprints?</title>
-
-<para>
-Imprints is a collection of tools for supporting these goals:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Providing a central repository of information regarding Windows NT and 95/98 printer driver packages.
- </para></listitem>
-
- <listitem><para>
- Providing the tools necessary for creating the Imprints printer driver packages.
- </para></listitem>
-
- <listitem><para>
- Providing an installation client that will obtain printer drivers from a central Internet (or intranet) Imprints Server
- repository and install them on remote Samba and Windows NT4 print servers.
- </para></listitem>
-</itemizedlist>
-</sect2>
-
-<sect2>
-<title>Creating Printer Driver Packages</title>
-
-<para>
-The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt,
-included with the Samba distribution for more information). In short, an Imprints driver package
-is a gzipped tarball containing the driver files, related INF files, and a control file needed by the
-installation client.
-</para>
-</sect2>
-
-<sect2>
-<title>The Imprints Server</title>
-
-<para>
-The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each
-printer entry in the database has an associated URL for the actual downloading of the package. Each
-package is digitally signed via GnuPG, which can be used to verify that
-the package downloaded is actually
-the one referred in the Imprints database. It is strongly recommended that this security check
-not be disabled.
-</para>
-</sect2>
-
-<sect2>
-<title>The Installation Client</title>
-
-<para>
-More information regarding the Imprints installation client is available from the documentation file
-<filename>Imprints-Client-HOWTO.ps</filename> that is included with the Imprints source package. The Imprints
-installation client comes in two forms:
-</para>
-
-<itemizedlist>
- <listitem><para>A set of command-line Perl scripts.</para></listitem>
- <listitem><para>A GTK+-based graphical interface to the command-line Perl scripts.</para></listitem>
-</itemizedlist>
-
-<para>
-The installation client (in both forms) provides a means of querying the Imprints database server for
-a matching list of known printer model names as well as a means to download and install the drivers on
-remote Samba and Windows NT print servers.
-</para>
-
-<para>
-The basic installation process is in four steps, and Perl code is wrapped around smbclient and rpcclient.
-</para>
-
-<itemizedlist>
- <listitem><para>
- For each supported architecture for a given driver:
- <orderedlist>
- <listitem><para>rpcclient: Get the appropriate upload directory on the remote server.</para></listitem>
- <listitem><para>smbclient: Upload the driver files.</para></listitem>
- <listitem><para>rpcclient: Issues an AddPrinterDriver() MS-RPC.</para></listitem>
- </orderedlist>
- </para></listitem>
-
- <listitem><para>rpcclient: Issues an AddPrinterEx() MS-RPC to actually create the printer.</para></listitem>
-</itemizedlist>
-
-<para>
-One of the problems encountered when implementing the Imprints tool set was the namespace issues between
-various supported client architectures. For example, Windows NT includes a driver named <quote>Apple LaserWriter
-II NTX v51.8</quote>, and Windows 95 calls its version of this driver <quote>Apple LaserWriter II NTX</quote>.
-</para>
-
-<para>
-The problem is how to know what client drivers have been uploaded for a printer. An astute reader will
-remember that the Windows NT Printer Properties dialog only includes space for one printer driver name. A
-quick look in the Windows NT 4.0 system registry at:
-</para>
-
-<para><filename>
- HKLM\System\CurrentControlSet\Control\Print\Environment
-</filename></para>
-
-<para>
-will reveal that Windows NT always uses the NT driver name. This is okay because Windows NT always requires
-that at least the Windows NT version of the printer driver is present. Samba does not have the
-requirement internally; therefore, <quote>How can you use the NT driver name if it has not already been installed?</quote>
-</para>
-
-<para>
-The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and
-95/98 printer drivers and that the NT driver is installed first.
-</para>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Adding Network Printers without User Interaction</title>
-
-<para>
-The following MS Knowledge Base article may be of some help if you need to handle Windows 2000 clients:
-<emphasis>How to Add Printers with No User Interaction in Windows 2000,</emphasis> (<ulink
-url="http://support.microsoft.com/default.aspx?scid=kb;en-us;189105">Microsoft KB 189105</ulink>). It also
-applies to Windows XP Professional clients. The ideas sketched out in this section are inspired by this
-article, which describes a command-line method that can be applied to install network and local printers and
-their drivers. This is most useful if integrated in Logon Scripts. You can see what options are available by
-typing in the command prompt (<command>DOS box</command>):
-</para>
-
-<para><userinput>rundll32 printui.dll,PrintUIEntry /?</userinput></para>
-
-<para>
-A window pops up that shows you all of the command-line switches available. An extensive list of examples
-is also provided. This is only for Windows 200x/XP; it does not work on Windows NT. Windows NT probably has
-some other tools in the respective Resource Kit. Here is a suggestion about what a client logon script
-might contain, with a short explanation of what the lines actually do (it works if 200x/XP Windows
-clients access printers via Samba, and works for Windows-based print servers too):
-</para>
-
-<para><screen>
-<userinput>rundll32 printui.dll,PrintUIEntry /dn /n "\\cupsserver\infotec2105-IPDS" /q</userinput>
-<userinput>rundll32 printui.dll,PrintUIEntry /in /n "\\cupsserver\infotec2105-PS"</userinput>
-<userinput>rundll32 printui.dll,PrintUIEntry /y /n "\\cupsserver\infotec2105-PS"</userinput>
-</screen></para>
-
-<para>
-Here is a list of the used command-line parameters:
-</para>
-
-<variablelist>
- <varlistentry><term>/dn</term>
- <listitem><para>deletes a network printer.</para></listitem>
- </varlistentry>
- <varlistentry><term>/q</term>
- <listitem><para>quiet modus.</para></listitem>
- </varlistentry>
- <varlistentry><term>/n</term>
- <listitem><para>names a printer.</para></listitem>
- </varlistentry>
- <varlistentry><term>/in</term>
- <listitem><para>adds a network printer connection.</para></listitem>
- </varlistentry>
- <varlistentry><term>/y</term>
- <listitem><para>sets printer as default printer.</para></listitem>
- </varlistentry>
-</variablelist>
-
-<itemizedlist>
- <listitem><para>
- Line 1 deletes a possibly existing previous network printer <emphasis>infotec2105-IPDS</emphasis>
- (which had used native Windows drivers with LPRng that were removed from the server that was
- converted to CUPS). The <command>/q</command> at the end prevents confirm
- or error dialog boxes from popping up. They should not be presented to the user logging on.
- </para></listitem>
-
- <listitem><para>
- Line 2 adds the new printer
- <emphasis>infotec2105-PS</emphasis> (which actually is the same
- physical device but is now run by the new CUPS printing system and associated with the
- CUPS/Adobe PS drivers). The printer and its driver must have been added to Samba prior to
- the user logging in (e.g., by a procedure as discussed earlier in this chapter or by running
- <command>cupsaddsmb</command>). The driver is now autodownloaded to the client PC where the
- user is about to log in.
- </para></listitem>
-
- <listitem><para>
- Line 3 sets the default printer to this new network printer (there might be several other
- printers installed with this same method, and some may be local as well, so we decide for a
- default printer). The default printer selection may, of course, be different for different users.
- </para></listitem>
-</itemizedlist>
-
-<para>
-The second line only works if the printer <emphasis>infotec2105-PS</emphasis> has an already working
-print queue on the <constant>cupsserver</constant> and if the
-printer drivers have been successfully uploaded
-(via the <command>APW</command>, <command>smbclient/rpcclient</command>, or <command>cupsaddsmb</command>)
-into the <smbconfsection name="[print$]"/> driver repository of Samba. Some Samba versions
-prior to version 3.0 required a restart of smbd after the printer install and the driver upload;
-otherwise the script (or any other client driver download) would fail.
-</para>
-
-<para>
-Since there is no easy way to test for the existence of an installed network printer from the logon script,
-do not bother checking. Just allow the de-installation/re-installation to occur every time a user logs in;
-it's really quick anyway (1 to 2 seconds).
-</para>
-
-<para>
-The additional benefits for this are:
-</para>
-
-<itemizedlist>
- <listitem><para>
- It puts in place any printer default setup changes automatically at every user logon.
- </para></listitem>
-
- <listitem><para>
- It allows for <quote>roaming</quote> users' login to the domain from different workstations.
- </para></listitem>
-</itemizedlist>
-
-<para>
-Since network printers are installed per user, this much simplifies the process of keeping the installation
-up to date. The few extra seconds at logon time will not really be noticeable. Printers can be centrally
-added, changed, and deleted at will on the server with no user intervention required from the clients
-(you just need to keep the logon scripts up to date).
-</para>
-</sect1>
-
-<sect1>
-<title>The <command>addprinter</command> Command</title>
-
-<para>
-The <command>addprinter</command> command can be configured to be a shell script or program executed by
-Samba. It is triggered by running the APW from a client against the Samba print server. The APW asks
-the user to fill in several fields (such as printer name, driver to be used, comment, port monitor,
-and so on). These parameters are passed on to Samba by the APW. If the addprinter command is designed in a
-way that it can create a new printer (through writing correct printcap entries on legacy systems or
-by executing the <command>lpadmin</command> command on more modern systems) and create the associated share,
-then the APW will in effect really create a new printer on Samba and the UNIX print subsystem!
-</para>
-</sect1>
-
-<sect1>
-<title>Migration of Classical Printing to Samba</title>
-
-<para>
-The basic NT-style printer driver management has not changed considerably in 3.0 over the 2.2.x releases
-(apart from many small improvements). Here migration should be quite easy, especially if you followed
-previous advice to stop using deprecated parameters in your setup. For migrations from an existing 2.0.x
-setup, or if you continued Windows 9x/Me-style printing in your Samba 2.2 installations, it is more of
-an effort. Please read the appropriate release notes and the HOWTO Collection for Samba-2.2.x. You can
-follow several paths. Here are possible scenarios for migration:
-</para>
-
-<itemizedlist>
- <listitem><para>
- You need to study and apply the new Windows NT printer and driver support. Previously used
- parameters <parameter>printer driver file</parameter>, <parameter>printer driver</parameter>,
- and <parameter>printer driver location</parameter> are no longer supported.
- </para></listitem>
-
- <listitem><para>
- If you want to take advantage of Windows NT printer driver support, you also need to migrate the
- Windows 9x/Me drivers to the new setup.
- </para></listitem>
-
- <listitem><para>
- An existing <filename>printers.def</filename> file (the one specified in the now removed parameter
- <parameter>printer driver file</parameter>) will no longer work with Samba. In 3.0, smbd attempts
- to locate Windows 9x/Me driver files for the printer in <smbconfsection name="[print$]"/>
- and additional settings in the TDB and only there; if it fails, it will <emphasis>not</emphasis>
- (as 2.2.x used to do) drop down to using a <filename>printers.def</filename> (and all associated
- parameters). The make_printerdef tool is removed and there is no backward compatibility for this.
- </para></listitem>
-
- <listitem><para>You need to install a Windows 9x/Me driver into the
- <smbconfsection name="[print$]"/> share for a printer on your Samba
- host. The driver files will be stored in the <quote>WIN40/0</quote> subdirectory of
- <smbconfsection name="[print$]"/>, and some other settings and information go
- into the printing-related TDBs.</para></listitem>
-
- <listitem><para>
- If you want to migrate an existing <filename>printers.def</filename> file into the new setup, the only current
- solution is to use the Windows NT APW to install the NT drivers and the 9x/Me drivers. This can be scripted
- using smbclient and rpcclient. See the Imprints installation client on the <ulink noescape="1"
- url="http://imprints.sourceforge.net/">Imprints</ulink> web site for example. See also the discussion of
- rpcclient usage in <link linkend="CUPS-printing">CUPS Printing</link>.
- </para></listitem>
-</itemizedlist>
-</sect1>
-
-<sect1>
-<title>Publishing Printer Information in Active Directory or LDAP</title>
-
-<para>
-This topic has also been addressed in <link linkend="NetCommand">Remote and Local Management &smbmdash; The
-Net Command</link>. If you wish to volunteer your services to help document this further, please contact
-<ulink url="mail://jht@samba.org">John H. Terpstra</ulink>.
-</para>
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<sect2>
-<title>I Give My Root Password but I Do Not Get Access</title>
-
-<para>
-Do not confuse the root password, which is valid for the UNIX system (and in most cases stored in the
-form of a one-way hash in a file named <filename>/etc/shadow</filename>), with the password used to
-authenticate against Samba. Samba does not know the UNIX password. Root access to Samba resources
-requires that a Samba account for root must first be created. This is done with the <command>smbpasswd</command>
-command as follows:
-<screen>
-&rootprompt; smbpasswd -a root
-New SMB password: secret
-Retype new SMB password: secret
-</screen>
-</para>
-
-</sect2>
-
-<sect2>
-<title>My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost</title>
-
-<para>
-Do not use the existing UNIX print system spool directory for the Samba spool directory. It may seem
-convenient and a savings of space, but it only leads to problems. The two must be separate. The UNIX/Linux
-system print spool directory (e.g., <filename>/var/spool/cups</filename>) is typically owned by a
-non-privileged user such as <literal>cups</literal> or <literal>lp</literal>. Additionally. the permissions on
-the spool directory are typically restrictive to the owner and/or group. On the other hand, the Samba
-spool directory must be world writable, and should have the 't' bit set to ensure that only a temporary
-spool file owner can change or delete the file.
-</para>
-
-<para>
-Depending on the type of print spooling system in use on the UNIX/Linux host, files that the spool
-management application finds and that are not currently part of job queue that it is managing can be deleted.
-This may explain the observation that jobs are spooled (by Samba) into this directory and just disappear.
-</para>
-
-</sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="problems">
-
-<chapterinfo>
- &author.jerry;
- &author.jelmer;
- &author.dbannon;
- &author.danshearer;
- <pubdate>8 Apr 2003</pubdate>
-</chapterinfo>
-
-<title>Analyzing and Solving Samba Problems</title>
-
-<para>
-<indexterm><primary>RFCs</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>documentation</primary></indexterm>
-There are many sources of information available in the form of mailing lists, RFCs, and documentation. The
-documentation that comes with the Samba distribution contains good explanations of general SMB topics such as
-browsing.
-</para>
-
-<sect1>
-<title>Diagnostics Tools</title>
-
-<para>
-<indexterm><primary>sniffer</primary></indexterm>
-<indexterm><primary>LAN</primary></indexterm>
-<indexterm><primary>analyzes data</primary></indexterm>
-<indexterm><primary>SMB networking</primary></indexterm>
-<indexterm><primary>network analyzer</primary></indexterm>
-With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself
-provides rather useful information, but in some cases you might have to fall back to using a
-<emphasis>sniffer</emphasis>. A sniffer is a program that listens on your LAN, analyzes the data sent on it,
-and displays it on the screen.
-</para>
-
-<sect2>
-<title>Debugging with Samba Itself</title>
-
-<para>
-<indexterm><primary>diagnostic tools</primary></indexterm>
-<indexterm><primary>debugging problems</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>debugging passwords</primary></indexterm>
-<indexterm><primary>debug level</primary></indexterm>
-<indexterm><primary>log level</primary></indexterm>
-One of the best diagnostic tools for debugging problems is Samba itself. You can use the <option>-d
-option</option> for both &smbd; and &nmbd; to specify the <smbconfoption name="debug level"/> at which to run.
-See the man pages for <command>smbd, nmbd</command>, and &smb.conf; for more information regarding debugging
-options. The debug level (log level) can range from 1 (the default) to 10 (100 for debugging passwords).
-</para>
-
-<para>
-<indexterm><primary>debugging</primary></indexterm>
-<indexterm><primary>gcc</primary></indexterm>
-<indexterm><primary>gdb</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>LsaEnumTrustedDomains</primary></indexterm>
-<indexterm><primary>attach gdb</primary></indexterm>
-Another helpful method of debugging is to compile Samba using the <command>gcc -g </command> flag. This will
-include debug information in the binaries and allow you to attach <command>gdb</command> to the running
-<command>smbd/nmbd</command> process. To attach <command>gdb</command> to an <command>smbd</command> process
-for an NT workstation, first get the workstation to make the connection. Pressing ctrl-alt-delete and going
-down to the domain box is sufficient (at least, the first time you join the domain) to generate a
-<parameter>LsaEnumTrustedDomains</parameter>. Thereafter, the workstation maintains an open connection and
-there will be an smbd process running (assuming that you haven't set a really short smbd idle timeout). So, in
-between pressing <command>ctrl-alt-delete</command> and actually typing in your password, you can attach
-<command>gdb</command> and continue.
-</para>
-
-<para>
-Some useful Samba commands worth investigating are:
-<indexterm><primary>testparm</primary></indexterm>
-<indexterm><primary>smbclient</primary></indexterm>
-<screen>
-&prompt;<userinput>testparm | more</userinput>
-&prompt;<userinput>smbclient -L //{netbios name of server}</userinput>
-</screen>
-</para>
-
-</sect2>
-
-<sect2>
- <title>Tcpdump</title>
-
-<para>
-<indexterm><primary>tcpdump</primary></indexterm>
-<indexterm><primary>tethereal</primary></indexterm>
-<indexterm><primary>ethereal</primary></indexterm>
-<ulink url="http://www.tcpdump.org/">Tcpdump</ulink> was the first
-UNIX sniffer with SMB support. It is a command-line utility and
-now, its SMB support is somewhat lagging that of <command>ethereal</command>
-and <command>tethereal</command>.
-</para>
-
-</sect2>
-
-<sect2>
- <title>Ethereal</title>
-
-<para>
-<indexterm><primary>ethereal</primary></indexterm>
-<ulink url="http://www.ethereal.com/">Ethereal</ulink> is a graphical sniffer, available for both UNIX (Gtk)
-and Windows. Ethereal's SMB support is quite good. For details on the use of <command>ethereal</command>, read
-the well-written Ethereal User Guide.
-</para>
-
-<figure id="ethereal1"><title>Starting a Capture.</title><imagefile>ethereal1</imagefile></figure>
-
-<para>
-<indexterm><primary>ports</primary></indexterm>
-Listen for data on ports 137, 138, 139, and 445. For example, use the filter <userinput>port 137, port 138,
-port 139, or port 445</userinput> as seen in <link linkend="ethereal1">Starting a Capture</link> snapshot.
-</para>
-
-<para>
-A console version of ethereal is available as well and is called <command>tethereal</command>.
-</para>
-
-<figure id="ethereal2"><title>Main Ethereal Data Window.</title><imagefile>ethereal2</imagefile></figure>
-
-</sect2>
-
-<sect2>
-<title>The Windows Network Monitor</title>
-
-<para>
-<indexterm><primary>Network Monitor</primary></indexterm>
-<indexterm><primary>Netmon</primary></indexterm>
-<indexterm><primary>Microsoft Developer Network CDs</primary></indexterm>
-<indexterm><primary>SMS</primary></indexterm>
-<indexterm><primary>promiscuous mode</primary></indexterm>
-<indexterm><primary>ethereal</primary></indexterm>
-For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer
-Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS
-allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous
-mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the
-local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write Netmon formatted
-files.
-</para>
-
-<sect3>
-<title>Installing Network Monitor on an NT Workstation</title>
-
-<para>
-<indexterm><primary>Netmon.</primary></indexterm>
-Installing Netmon on an NT workstation requires a couple of steps. The following are instructions for
-installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
-Workstation 4.0. The process should be similar for other versions of Windows NT version of Netmon. You will
-need both the Microsoft Windows NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
-</para>
-
-<para>
-<indexterm><primary>Network Monitor Tools and Agent</primary></indexterm>
-Initially you will need to install <application>Network Monitor Tools and Agent</application>
-on the NT Server to do this:
-</para>
-
-<itemizedlist>
- <listitem><para>Go to <guibutton>Start</guibutton> -> <guibutton>Settings</guibutton> -> <guibutton>Control Panel</guibutton> ->
- <guibutton>Network</guibutton> -> <guibutton>Services</guibutton> -> <guibutton>Add</guibutton>.</para></listitem>
-
- <listitem><para>Select the <guilabel>Network Monitor Tools and Agent</guilabel> and click on <guibutton>OK</guibutton>.</para></listitem>
-
- <listitem><para>Click on <guibutton>OK</guibutton> on the Network Control Panel.</para></listitem>
-
- <listitem><para>Insert the Windows NT Server 4.0 install CD when prompted.</para></listitem>
-</itemizedlist>
-
-<para>
-At this point, the Netmon files should exist in <filename>%SYSTEMROOT%\System32\netmon\*.*</filename>.
-Two subdirectories exist as well: <filename>parsers\</filename>, which contains the necessary DLLs
-for parsing the Netmon packet dump, and <filename>captures\</filename>.
-</para>
-
-<para>
-To install the Netmon tools on an NT Workstation, you will first need to install the
-Network Monitor Agent from the Workstation install CD.
-</para>
-
-<itemizedlist>
- <listitem><para>Go to <guibutton>Start</guibutton> -> <guibutton>Settings</guibutton> ->
- <guibutton>Control Panel</guibutton> -> <guibutton>Network</guibutton> ->
- <guibutton>Services</guibutton> -> <guibutton>Add</guibutton>.</para></listitem>
-
- <listitem><para>Select the <guilabel>Network Monitor Agent</guilabel>, click on
- <guibutton>OK</guibutton>.</para></listitem>
-
- <listitem><para>Click on <guibutton>OK</guibutton> in the Network Control Panel.
- </para></listitem>
-
- <listitem><para>Insert the Windows NT Workstation 4.0 install CD when prompted.</para></listitem>
-</itemizedlist>
-
-<para>
-Now copy the files from the NT Server in <filename>%SYSTEMROOT%\System32\netmon</filename>
-to <filename>%SYSTEMROOT%\System32\netmon</filename> on the workstation and set permissions
-as you deem appropriate for your site. You will need administrative rights on the NT box to run Netmon.
-</para>
-
-</sect3>
-<sect3>
-<title>Installing Network Monitor on Windows 9x/Me</title>
-<para>
-To install Netmon on Windows 9x/Me, install the Network Monitor Agent
-from the Windows 9x/Me CD (<filename>\admin\nettools\netmon</filename>).
-There is a readme file included with the Netmon driver files on the CD if you need
-information on how to do this. Copy the files from a working Netmon installation.
-</para>
-</sect3>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Useful URLs</title>
-<itemizedlist>
-
-<listitem><para>FTP site for older SMB specs,
- <ulink noescape="1" url="ftp://ftp.microsoft.com/developr/drg/CIFS/">
- ftp://ftp.microsoft.com/developr/drg/CIFS/</ulink></para></listitem>.
-
-</itemizedlist>
-
-</sect1>
-
-<sect1>
-<title>Getting Mailing List Help</title>
-
-<para>
-There are a number of Samba-related mailing lists. Go to <ulink
-noescape="1" url="https://www.samba.org">https://www.samba.org</ulink>, click on your nearest mirror,
-and then click on <command>Support</command>. Next, click on <command>
-Samba-related mailing lists</command>.
-</para>
-
-<para>
-For questions relating to Samba TNG, go to
-<ulink noescape="1" url="http://www.samba-tng.org/">http://www.samba-tng.org/</ulink>.
-It has been requested that you do not post questions about Samba-TNG to the
-mainstream Samba lists.</para>
-
-<para>
-If you do post a message to one of the lists, please observe the following guidelines:
-</para>
-
-<itemizedlist>
-
- <listitem><para>
-<indexterm><primary>volunteers</primary></indexterm>
- Always remember that the developers are volunteers; they are
- not paid and they never guarantee to produce a particular feature at
- a particular time. Any timelines are <quote>best guess,</quote> and nothing more.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>PDC</primary></indexterm>
- Always mention what version of Samba you are using and what
- operating system it's running under. You should list the relevant sections of
- your &smb.conf; file, at least the options in <smbconfsection name="[global]"/>
- that affect PDC support.
- </para></listitem>
-
- <listitem><para>In addition to the version, if you obtained Samba via
- CVS, mention the date when you last checked it out.</para></listitem>
-
- <listitem><para> Try to make your questions clear and brief. Lots of long,
- convoluted questions get deleted before they are completely read!
- Do not post HTML-encoded messages. Most people on mailing lists simply delete
- them.
- </para></listitem>
-
- <listitem><para> If you run one of those nifty <quote>I'm on holiday</quote> things when
- you are away, make sure its configured to not answer mailing list traffic. Autoresponses
- to mailing lists really irritate the thousands of people who end up having to deal
- with such bad netiquet bahavior.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>cross post</primary></indexterm>
- Don't cross post. Work out which is the best list to post to
- and see what happens. Do not post to both samba-ntdom and samba-technical.
- Many people active on the lists subscribe to more
- than one list and get annoyed to see the same message two or more times.
- Often someone who thinks a message would be better dealt
- with on another list will forward it on for you.</para></listitem>
-
- <listitem><para>You might include <emphasis>partial</emphasis>
- log files written at a log level set to as much as 20.
- Please do not send the entire log but just enough to give the context of the
- error messages.</para></listitem>
-
- <listitem><para>If you have a complete Netmon trace (from the opening of
- the pipe to the error), you can send the *.CAP file as well.</para></listitem>
-
- <listitem><para>Please think carefully before attaching a document to an email.
- Consider pasting the relevant parts into the body of the message. The Samba
- mailing lists go to a huge number of people. Do they all need a copy of your
- &smb.conf; in their attach directory?</para></listitem>
-
-</itemizedlist>
-
-</sect1>
-
-<sect1>
-<title>How to Get Off the Mailing Lists</title>
-
-<para>To have your name removed from a Samba mailing list, go to the same
-place where you went to
-subscribe to it, go to <ulink noescape="1" url="http://lists.samba.org/">http://lists.samba.org</ulink>,
-click on your nearest mirror, click on <command>Support</command>, and
-then click on <command>Samba-related mailing lists</command>.
-</para>
-
-<para>
-Please do not post messages to the list asking to be removed. You will only
-be referred to the above address (unless that process failed in some way).
-</para>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="ProfileMgmt">
-<chapterinfo>
- &author.jht;
- <pubdate>April 3 2003</pubdate>
-</chapterinfo>
-
-<title>Desktop Profile Management</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>roaming profiles</primary></indexterm>
-Roaming profiles are feared by some, hated by a few, loved by many, and a godsend for
-some administrators.
-</para>
-
-<para>
-<indexterm><primary>manage roaming profiles</primary></indexterm>
-Roaming profiles allow an administrator to make available a consistent user desktop
-as the user moves from one machine to another. This chapter provides much information
-regarding how to configure and manage roaming profiles.
-</para>
-
-<para>
-<indexterm><primary>local profiles</primary></indexterm>
-While roaming profiles might sound like nirvana to some, they are a real and tangible
-problem to others. In particular, users of mobile computing tools, where often there may not
-be a sustained network connection, are often better served by purely local profiles.
-This chapter provides information to help the Samba administrator deal with those
-situations.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Roaming Profiles</title>
-
-<warning>
-<para>
-Roaming profiles support is different for Windows 9x/Me and Windows NT4/200x.
-</para>
-</warning>
-
-<para>
-Before discussing how to configure roaming profiles, it is useful to see how
-Windows 9x/Me and Windows NT4/200x clients implement these features.
-</para>
-
-<para>
-<indexterm><primary>NetUserGetInfo</primary></indexterm>
-Windows 9x/Me clients send a NetUserGetInfo request to the server to get the user's
-profiles location. However, the response does not have room for a separate
-profiles location field, only the user's home share. This means that Windows 9x/Me
-profiles are restricted to being stored in the user's home directory.
-</para>
-
-
-<para>
-<indexterm><primary>NetSAMLogon</primary></indexterm>
-<indexterm><primary>RPC</primary></indexterm>
-Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields
-including a separate field for the location of the user's profiles.
-</para>
-
-<sect2>
-<title>Samba Configuration for Profile Handling</title>
-
-<para>
-This section documents how to configure Samba for MS Windows client profile support.
-</para>
-
-<sect3>
-<title>NT4/200x User Profiles</title>
-
-<para>
-For example, to support Windows NT4/200x clients, set the following in the [global] section of the &smb.conf; file:
-</para>
-
-<smbconfblock>
- <smbconfoption name="logon path"> \\profileserver\profileshare\profilepath\%U\moreprofilepath</smbconfoption>
-</smbconfblock>
-
-<para>
-This is typically implemented like:
-<smbconfblock>
-<smbconfoption name="logon path">\\%L\Profiles\%U</smbconfoption>
-</smbconfblock>
-where <quote>%L</quote> translates to the name of the Samba server and <quote>%U</quote> translates to the username.
-</para>
-
-<para>
-The default for this option is <filename>\\%N\%U\profile</filename>, namely, <filename>\\sambaserver\username\profile</filename>.
-The <filename>\\%N\%U</filename> service is created automatically by the [homes] service. If you are using
-a Samba server for the profiles, you must make the share that is specified in the logon path
-browseable. Please refer to the man page for &smb.conf; regarding the different
-semantics of <quote>%L</quote> and <quote>%N</quote>, as well as <quote>%U</quote> and <quote>%u</quote>.
-</para>
-
-<note><para>
-<indexterm><primary>logons</primary></indexterm>
-<indexterm><primary>disconnect a connection</primary></indexterm>
-MS Windows NT/200x clients at times do not disconnect a connection to a server between logons. It is recommended
-to not use the <smbconfsection name="homes"/> metaservice name as part of the profile share path.
-</para></note>
-</sect3>
-
-<sect3>
-<title>Windows 9x/Me User Profiles</title>
-
-<para>
-<indexterm><primary>net use /home</primary></indexterm>
-<indexterm><primary>logon home</primary></indexterm>
-To support Windows 9x/Me clients, you must use the <smbconfoption name="logon home"/>
-parameter. Samba has been fixed so <userinput>net use /home</userinput> now works as well and it, too, relies
-on the <parameter>logon home</parameter> parameter.
-</para>
-
-<para>
-<indexterm><primary>logon home</primary></indexterm>
-<indexterm><primary>\\%L\%U\.profiles</primary></indexterm>
-<indexterm><primary>.profiles</primary></indexterm>
-By using the <parameter>logon home</parameter> parameter, you are restricted to putting Windows 9x/Me profiles
-in the user's home directory. But wait! There is a trick you can use. If you set the following in the
-<smbconfsection name="[global]"/> section of your &smb.conf; file:
-<smbconfblock>
-<smbconfoption name="logon home">\\%L\%U\.profiles</smbconfoption>
-</smbconfblock>
-then your Windows 9x/Me clients will dutifully put their clients in a subdirectory
-of your home directory called <filename>.profiles</filename> (making them hidden).
-</para>
-
-<para>
-<indexterm><primary>net use /home</primary></indexterm>
-Not only that, but <userinput>net use /home</userinput> will also work because of a feature in
-Windows 9x/Me. It removes any directory stuff off the end of the home directory area
-and only uses the server and share portion. That is, it looks like you
-specified <filename>\\%L\%U</filename> for <smbconfoption name="logon home"/>.
-</para>
-</sect3>
-
-<sect3>
-<title>Mixed Windows Windows 9x/Me and NT4/200x User Profiles</title>
-
-<para>
-You can support profiles for Windows 9x and Windows NT clients by setting both the
-<smbconfoption name="logon home"/> and <smbconfoption name="logon path"/> parameters. For example,
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="logon home">\\%L\%U\.profiles</smbconfoption>
-<smbconfoption name="logon path">\\%L\profiles\%U</smbconfoption>
-</smbconfblock></para>
-
-<para>
-<indexterm><primary>mixed profile</primary></indexterm>
-Windows 9x/Me and NT4 and later profiles should not be stored in the same location because
-Windows NT4 and later will experience problems with mixed profile environments.
-</para>
-
-</sect3>
-<sect3>
-<title>Disabling Roaming Profile Support</title>
-
-<para>
-<indexterm><primary>disable roaming profiles</primary></indexterm>
-The question often asked is, <quote>How may I enforce use of local profiles?</quote> or
-<quote>How do I disable roaming profiles?</quote>
-</para>
-
-<para>
-<indexterm><primary>roaming profiles</primary></indexterm>
-There are three ways of doing this:
-</para>
-
-<indexterm><primary>windows registry settings</primary><secondary>roaming profiles</secondary></indexterm>
-
-<variablelist>
- <varlistentry>
- <term>In &smb.conf;</term>:
- <listitem><para>
- Affect the following settings and ALL clients will be forced to use a local profile:
- <smbconfoption name="logon home"> </smbconfoption> and <smbconfoption name="logon path"> </smbconfoption>
- </para>
-
- <para>
- The arguments to these parameters must be left blank. It is necessary to include the <constant>=</constant> sign
- to specifically assign the empty value.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>MS Windows Registry:</term>
- <listitem><para>
-<indexterm><primary>MMC</primary></indexterm>
-<indexterm><primary>local profile</primary></indexterm>
- Use the Microsoft Management Console (MMC) <command>gpedit.msc</command> to instruct your MS Windows XP
- machine to use only a local profile. This, of course, modifies registry settings. The full
- path to the option is:
-<screen>
-Local Computer Policy\
- Computer Configuration\
- Administrative Templates\
- System\
- User Profiles\
-
-Disable: Only Allow Local User Profiles
-Disable: Prevent Roaming Profile Change from Propagating to the Server
-</screen>
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Change of Profile Type:</term>
-<indexterm><primary>Profile Type</primary></indexterm>
- <listitem><para>From the start menu right-click on the <guiicon>My Computer</guiicon> icon,
- select <guimenuitem>Properties</guimenuitem>, click on the <guilabel>User Profiles</guilabel>
- tab, select the profile you wish to change from
- <guimenu>Roaming</guimenu> type to <guimenu>Local</guimenu>, and click on
- <guibutton>Change Type</guibutton>.
- </para></listitem>
- </varlistentry>
-</variablelist>
-
-<para>
-Consult the MS Windows registry guide for your particular MS Windows version for more information
-about which registry keys to change to enforce use of only local user profiles.
-</para>
-
-<note><para>
-<indexterm><primary>Windows Resource Kit</primary></indexterm>
-The specifics of how to convert a local profile to a roaming profile, or a roaming profile
-to a local one, vary according to the version of MS Windows you are running. Consult the Microsoft MS
-Windows Resource Kit for your version of Windows for specific information.
-</para></note>
-
-</sect3>
-</sect2>
-
-<sect2>
-<title>Windows Client Profile Configuration Information</title>
-
-<sect3>
-<title>Windows 9x/Me Profile Setup</title>
-
-<para>
-When a user first logs in on Windows 9x, the file user.DAT is created, as are folders <filename>Start
-Menu</filename>, <filename>Desktop</filename>, <filename>Programs</filename>, and
-<filename>Nethood</filename>. These directories and their contents will be merged with the local versions
-stored in <filename>c:\windows\profiles\username</filename> on subsequent logins, taking the most recent from
-each. You will need to use the <smbconfsection name="[global]"/> options <smbconfoption name="preserve
-case">yes</smbconfoption>, <smbconfoption name="short preserve case">yes</smbconfoption>, and <smbconfoption
-name="case sensitive">no</smbconfoption> in order to maintain capital letters in shortcuts in any of the
-profile folders.
-</para>
-
-<para>
-<indexterm><primary>user.DAT</primary></indexterm>
-<indexterm><primary>user.MAN</primary></indexterm>
-The <filename>user.DAT</filename> file contains all the user's preferences. If you wish to enforce a set of preferences,
-rename their <filename>user.DAT</filename> file to <filename>user.MAN</filename>, and deny them write access to this file.
-</para>
-
-<orderedlist>
- <listitem> <para>
- On the Windows 9x/Me machine, go to <guimenu>Control Panel</guimenu> ->
- <guimenuitem>Passwords</guimenuitem> and select the <guilabel>User Profiles</guilabel> tab.
- Select the required level of roaming preferences. Press <guibutton>OK</guibutton>, but do not
- allow the computer to reboot.
- </para> </listitem>
-
- <listitem> <para>
- On the Windows 9x/Me machine, go to <guimenu>Control Panel</guimenu> ->
- <guimenuitem>Network</guimenuitem> -> <guimenuitem>Client for Microsoft Networks</guimenuitem>
- -> <guilabel>Preferences</guilabel>. Select <guilabel>Log on to NT Domain</guilabel>. Then,
- ensure that the Primary Logon is <guilabel>Client for Microsoft Networks</guilabel>. Press
- <guibutton>OK</guibutton>, and this time allow the computer to reboot.
- </para> </listitem>
-</orderedlist>
-
-<para>
-<indexterm><primary>Primary Logon</primary></indexterm>
-<indexterm><primary>Client for Novell Networks</primary></indexterm>
-<indexterm><primary>Novell</primary></indexterm>
-<indexterm><primary>Windows Logon</primary></indexterm>
-Under Windows 9x/Me, profiles are downloaded from the Primary Logon. If you have the Primary Logon
-as <quote>Client for Novell Networks</quote>, then the profiles and logon script will be downloaded from
-your Novell server. If you have the Primary Logon as <quote>Windows Logon</quote>, then the profiles will
-be loaded from the local machine &smbmdash; a bit against the concept of roaming profiles, it would seem!
-</para>
-
-<para>
-<indexterm><primary>domain logon server</primary></indexterm>
-You will now find that the Microsoft Networks Login box contains <constant>[user, password, domain]</constant> instead
-of just <constant>[user, password]</constant>. Type in the Samba server's domain name (or any other domain known to exist,
-but bear in mind that the user will be authenticated against this domain and profiles downloaded from it
-if that domain logon server supports it), user name and user's password.
-</para>
-
-<para>
-Once the user has been successfully validated, the Windows 9x/Me machine informs you that
-<computeroutput>The user has not logged on before</computeroutput> and asks <computeroutput>Do you
-wish to save the user's preferences?</computeroutput> Select <guibutton>Yes</guibutton>.
-</para>
-
-<para>
-Once the Windows 9x/Me client comes up with the desktop, you should be able to examine the
-contents of the directory specified in the <smbconfoption name="logon path"/> on
-the Samba server and verify that the <filename>Desktop</filename>, <filename>Start Menu</filename>,
-<filename>Programs</filename>, and <filename>Nethood</filename> folders have been created.
-</para>
-
-<para>
-<indexterm><primary>cached locally</primary></indexterm>
-<indexterm><primary>shortcuts</primary></indexterm>
-<indexterm><primary>profile directory</primary></indexterm>
-These folders will be cached locally on the client and updated when the user logs off (if
-you haven't made them read-only by then). You will find that if the user creates further folders or
-shortcuts, the client will merge the profile contents downloaded with the contents of the profile
-directory already on the local client, taking the newest folders and shortcut from each set.
-</para>
-
-<para>
-<indexterm><primary>local profile</primary></indexterm>
-<indexterm><primary>remote profile</primary></indexterm>
-<indexterm><primary>ownership rights</primary></indexterm>
-<indexterm><primary>profile directory</primary></indexterm>
-If you have made the folders/files read-only on the Samba server, then you will get errors from
-the Windows 9x/Me machine on logon and logout as it attempts to merge the local and remote profile.
-Basically, if you have any errors reported by the Windows 9x/Me machine, check the UNIX file permissions
-and ownership rights on the profile directory contents, on the Samba server.
-</para>
-
-<para>
-<indexterm><primary>windows registry settings</primary></indexterm>
-<indexterm><primary>profile path</primary></indexterm>
-<indexterm><primary>user profiles</primary></indexterm>
-<indexterm><primary>desktop cache</primary></indexterm>
-<indexterm><primary>windows registry settings</primary><secondary>profile path</secondary></indexterm>
-If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below.
-When this user next logs in, the user will be told that he/she is logging in <quote>for the first
-time</quote>.
-</para>
-
-
-<orderedlist>
- <listitem><para>
- Instead of logging in under the [user, password, domain] dialog, press <guibutton>escape</guibutton>.
- </para> </listitem>
-
- <listitem><para>
- Run the <command>regedit.exe</command> program, and look in:
- </para>
-
- <para>
- <filename>HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList</filename>
- </para>
-
- <para>
- You will find an entry for each user of ProfilePath. Note the contents of this key
- (likely to be <filename>c:\windows\profiles\username</filename>), then delete the key
- <parameter>ProfilePath</parameter> for the required user.
- </para></listitem>
-
- <listitem><para>
- Exit the registry editor.
- </para></listitem>
-
- <listitem><para>
- Search for the user's .PWL password-caching file in the <filename>c:\windows</filename> directory, and delete it.
- </para></listitem>
-
- <listitem><para>
- Log off the Windows 9x/Me client.
- </para></listitem>
-
- <listitem><para>
- Check the contents of the profile path (see <smbconfoption name="logon path"/>
- described above) and delete the <filename>user.DAT</filename> or <filename>user.MAN</filename>
- file for the user, making a backup if required.
- </para></listitem>
-</orderedlist>
-
-<warning><para>
-<indexterm><primary>ProfilePath</primary></indexterm>
-Before deleting the contents of the directory listed in the <parameter>ProfilePath</parameter>
-(this is likely to be <filename>c:\windows\profiles\username)</filename>, ask whether the owner has
-any important files stored on his or her desktop or start menu. Delete the contents of the
-directory <parameter>ProfilePath</parameter> (making a backup if any of the files are needed).
-</para>
-
-<para>
-This will have the effect of removing the local (read-only hidden system file) <filename>user.DAT</filename>
-in their profile directory, as well as the local <quote>desktop,</quote> <quote>nethood,</quote>
-<quote>start menu,</quote> and <quote>programs</quote> folders.
-</para></warning>
-
-<para>
-<indexterm><primary>log level</primary></indexterm>
-<indexterm><primary>packet sniffer</primary></indexterm>
-<indexterm><primary>ethereal</primary></indexterm>
-<indexterm><primary>netmon.exe</primary></indexterm>
-If all else fails, increase Samba's debug log levels to between 3 and 10, and/or run a packet
-sniffer program such as ethereal or <command>netmon.exe</command>, and look for error messages.
-</para>
-
-<para>
-<indexterm><primary>roaming profiles</primary></indexterm>
-<indexterm><primary>packet trace</primary></indexterm>
-If you have access to an Windows NT4/200x server, then first set up roaming profiles and/or
-netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces
-provided with Windows NT4/200x server, and see what the differences are with the equivalent Samba trace.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Windows NT4 Workstation</title>
-
-<para>
-When a user first logs in to a Windows NT workstation, the profile NTuser.DAT is created. The profile
-location can be now specified through the <smbconfoption name="logon path"/> parameter.
-</para>
-
-<para>
-There is a parameter that is now available for use with NT Profiles: <smbconfoption name="logon drive"/>.
-This should be set to <filename>H:</filename> or any other drive, and should be used in conjunction with
-the new <smbconfoption name="logon home"/> parameter.
-</para>
-
-<para>
-<indexterm><primary>.PDS extension</primary></indexterm>
-<indexterm><primary>profile path</primary></indexterm>
-The entry for the NT4 profile is a directory, not a file. The NT help on profiles mentions that a
-directory is also created with a .PDS extension. The user, while logging in, must have write permission
-to create the full profile path (and the folder with the .PDS extension for those situations where it
-might be created).
-</para>
-
-<para>
-<indexterm><primary>NTuser.DAT</primary></indexterm>
-In the profile directory, Windows NT4 creates more folders than Windows 9x/Me. It creates
-<filename>Application Data</filename> and others, as well as <filename>Desktop</filename>,
-<filename>Nethood</filename>, <filename>Start Menu,</filename> and <filename>Programs</filename>.
-The profile itself is stored in a file <filename>NTuser.DAT</filename>. Nothing appears to be stored
-in the .PDS directory, and its purpose is currently unknown.
-</para>
-
-<para>
-<indexterm><primary>NTuser.DAT</primary></indexterm>
-<indexterm><primary>NTuser.MAN</primary></indexterm>
-You can use the <application>System Control Panel</application> to copy a local profile onto
-a Samba server (see NT help on profiles; it is also capable of firing up the correct location in the
-<application>System Control Panel</application> for you). The NT help file also mentions that renaming
-<filename>NTuser.DAT</filename> to <filename>NTuser.MAN</filename> turns a profile into a mandatory one.
-</para>
-
-<para>
-The case of the profile is significant. The file must be called <filename>NTuser.DAT</filename>
-or, for a mandatory profile, <filename>NTuser.MAN</filename>.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Windows 2000/XP Professional</title>
-
-<para>
-You must first convert the profile from a local profile to a domain profile on the MS Windows
-workstation as follows: </para>
-
-<procedure>
- <step><para> Log on as the <emphasis>local</emphasis> workstation administrator. </para></step>
-
- <step><para> Right-click on the <guiicon>My Computer</guiicon> icon, and select
- <guimenuitem>Properties</guimenuitem>.</para></step>
-
- <step><para> Click on the <guilabel>User Profiles</guilabel> tab.</para></step>
-
- <step><para> Select the profile you wish to convert (click it once).</para></step>
-
- <step><para> Click on the <guibutton>Copy To</guibutton> button.</para></step>
-
- <step><para> In the <guilabel>Permitted to use</guilabel> box, click on the
- <guibutton>Change</guibutton> button. </para></step>
-
- <step><para> Click on the <guilabel>Look in</guilabel> area that lists the machine name. When you click here, it will
- open up a selection box. Click on the domain to which the profile must be accessible. </para>
-
- <note><para>You will need to log on if a logon box opens up.
- For example, connect as <replaceable>DOMAIN</replaceable>\root, password:
- <replaceable>mypassword</replaceable>.</para></note> </step>
-
- <step><para> To make the profile capable of being used by anyone, select <quote>Everyone</quote>. </para></step>
-
- <step><para> Click on <guibutton>OK</guibutton> and the Selection box will close. </para></step>
-
- <step><para> Now click on <guibutton>OK</guibutton> to create the profile in the path
- you nominated. </para></step>
-</procedure>
-
-<para>
-Done. You now have a profile that can be edited using the Samba <command>profiles</command> tool.
-</para>
-
-<note><para>
-Under Windows NT/200x, the use of mandatory profiles forces the use of MS Exchange storage of mail
-data and keeps it out of the desktop profile. That keeps desktop profiles from becoming unusable.
-</para></note>
-
-<sect4>
-<title>Windows XP Service Pack 1</title>
- <para>
- There is a security check new to Windows XP (or maybe only Windows XP service pack 1).
- It can be disabled via a group policy in the Active Directory. The policy is called:
-<screen>
-Computer Configuration\Administrative Templates\System\User Profiles\
- Do not check for user ownership of Roaming Profile Folders
-</screen>
- </para>
-
- <para>
- This should be set to <constant>Enabled</constant>.
- </para>
-
- <para>
- Does the new version of Samba have an Active Directory analogue? If so, then you may be able to set the policy through this.
- </para>
-
- <para>If you cannot set group policies in Samba, then you may be able to set the policy locally on
- each machine. If you want to try this, then do the following:
- </para>
-
-
-<procedure>
- <step><para>On the XP workstation, log in with an administrative account.</para></step>
-
- <step><para>Click on <guimenu>Start</guimenu> -> <guimenuitem>Run</guimenuitem>.</para></step>
- <step><para>Type <command>mmc</command>.</para></step>
- <step><para>Click on <guibutton>OK</guibutton>.</para></step>
- <step><para>A Microsoft Management Console should appear.</para></step>
- <step><para>Click on <guimenu>File</guimenu> -> <guimenuitem>Add/Remove Snap-in</guimenuitem> -> <guimenuitem>Add</guimenuitem>.</para></step>
- <step><para>Double-click on <guiicon>Group Policy</guiicon>.</para></step>
- <step><para>Click on <guibutton>Finish</guibutton> -> <guibutton>Close</guibutton>.</para></step>
- <step><para>Click on <guibutton>OK</guibutton>.</para></step>
- <step><para>In the <quote>Console Root</quote> window expand <guiicon>Local Computer Policy</guiicon> ->
- <guiicon>Computer Configuration</guiicon> -> <guiicon>Administrative Templates</guiicon> ->
- <guiicon>System</guiicon> -> <guiicon>User Profiles</guiicon>.</para></step>
- <step><para>Double-click on <guilabel>Do not check for user ownership of Roaming Profile Folders</guilabel>.</para></step>
- <step><para>Select <guilabel>Enabled</guilabel>.</para></step>
- <step><para>Click on <guibutton>OK</guibutton>.</para></step>
- <step><para>Close the whole console. You do not need to save the settings (this refers to the
- console settings rather than the policies you have changed).</para></step>
- <step><para>Reboot.</para></step>
-</procedure>
-</sect4>
-</sect3>
-</sect2>
-
-<sect2>
-<title>User Profile Hive Cleanup Service</title>
-
-<para>
-There are certain situations that cause a cached local copy of roaming profile not to be deleted on exit, even if
-the policy to force such deletion is set. To deal with that situation, a special service was created. The application
-<command>UPHClean</command> (User Profile Hive Cleanup) can be installed as a service on Windows NT4/2000/XP Professional
-and Windows 2003.
-</para>
-
-<para>
-The UPHClean software package can be downloaded from the User Profile Hive Cleanup
-Service<footnote><para>http://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en</para></footnote>
-web site.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</title>
-
-<para>
-<indexterm><primary>profile sharing</primary></indexterm>
-<indexterm><primary>profile contents</primary></indexterm>
-Sharing of desktop profiles between Windows versions is not recommended. Desktop profiles are an
-evolving phenomenon, and profiles for later versions of MS Windows clients add features that may interfere
-with earlier versions of MS Windows clients. Probably the more salient reason to not mix profiles is
-that when logging off an earlier version of MS Windows, the older format of profile contents may overwrite
-information that belongs to the newer version, resulting in loss of profile information content when that
-user logs on again with the newer version of MS Windows.
-</para>
-
-<para>
-If you then want to share the same Start Menu and Desktop with Windows 9x/Me, you must specify a common
-location for the profiles. The &smb.conf; parameters that need to be common are
-<smbconfoption name="logon path"/> and <smbconfoption name="logon home"/>.
-</para>
-
-<para>
-<indexterm><primary>user.DAT</primary></indexterm>
-<indexterm><primary>NTuser.DAT</primary></indexterm>
-If you have this set up correctly, you will find separate <filename>user.DAT</filename> and
-<filename>NTuser.DAT</filename> files in the same profile directory.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Profile Migration from Windows NT4/200x Server to Samba</title>
-
-<para>
-<indexterm><primary>encrypted passwords</primary></indexterm>
-There is nothing to stop you from specifying any path that you like for the location of users' profiles.
-Therefore, you could specify that the profile be stored on a Samba server or any other SMB server,
-as long as that SMB server supports encrypted passwords.
-</para>
-
-<sect3 id="profilemigrn">
-<title>Windows NT4 Profile Management Tools</title>
-
-<para>
-<indexterm><primary>resource kit</primary></indexterm>
-Unfortunately, the resource kit information is specific to the version of MS Windows NT4/200x. The
-correct resource kit is required for each platform.
-</para>
-
-<para>Here is a quick guide:</para>
-
-<procedure>
-<title>Profile Migration Procedure</title>
-
- <step><para> On your NT4 domain controller, right-click on <guiicon>My Computer</guiicon>, then select
- <guilabel>Properties</guilabel>, then the tab labeled <guilabel>User Profiles</guilabel>. </para></step>
-
- <step><para> Select a user profile you want to migrate and click on it. </para>
-
- <note><para>I am using the term <quote>migrate</quote> loosely. You can copy a profile to create a group
- profile. You can give the user <parameter>Everyone</parameter> rights to the profile you copy this to. That
- is what you need to do, since your Samba domain is not a member of a trust relationship with your NT4
- PDC.</para></note></step>
-
- <step><para>Click on the <guibutton>Copy To</guibutton> button.</para></step>
-
- <step><para>In the box labeled <guilabel>Copy Profile to</guilabel> add your new path, such as,
- <filename>c:\temp\foobar</filename></para></step>
-
- <step><para>Click on <guibutton>Change</guibutton> in the <guilabel>Permitted to use</guilabel> box.</para></step>
-
- <step><para>Click on the group <quote>Everyone</quote>, click on <guibutton>OK</guibutton>. This
- closes the <quote>choose user</quote> box.</para></step>
-
- <step><para>Now click on <guibutton>OK</guibutton>.</para></step>
-</procedure>
-
-<para>
-Follow these steps for every profile you need to migrate.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Side Bar Notes</title>
-
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>info</tertiary></indexterm>
-You should obtain the SID of your NT4 domain. You can use the <command>net rpc info</command> to do this.
-See <link linkend="NetCommand">The Net Command Chapter</link>, <link linkend="netmisc1">Other Miscellaneous Operations</link> for more information.
-</para>
-
-</sect3>
-
-<sect3>
-<title>moveuser.exe</title>
-
-<para>
-<indexterm><primary>moveuser.exe</primary></indexterm>
-The Windows 200x professional resource kit has <command>moveuser.exe</command>.
-<command>moveuser.exe</command> changes the security of a profile from one user to another. This allows the
-account domain to change and/or the username to change.
-</para>
-
-<para>
-This command is like the Samba <command>profiles</command> tool.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Get SID</title>
-
-<para>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>GetSID.exe</primary></indexterm>
-You can identify the SID by using <command>GetSID.exe</command> from the Windows NT Server 4.0 Resource Kit.
-</para>
-
-<para>
-Windows NT 4.0 stores the local profile information in the registry under the following key:
-<filename>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</filename>
-</para>
-
-<para>
-Under the ProfileList key, there will be subkeys named with the SIDs of the users who have logged
-on to this computer. (To find the profile information for the user whose locally cached profile you want
-to move, find the SID for the user with the <command>GetSID.exe</command> utility.) Inside the appropriate user's subkey,
-you will see a string value named <parameter>ProfileImagePath</parameter>.
-</para>
-
-</sect3>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Mandatory Profiles</title>
-
-<para>
-<indexterm><primary>mandatory profiles</primary></indexterm>
-A mandatory profile is a profile that the user does not have the ability to overwrite. During the
-user's session, it may be possible to change the desktop environment; however, as the user logs out, all changes
-made will be lost. If it is desired to not allow the user any ability to change the desktop environment,
-then this must be done through policy settings. See <link linkend="PolicyMgmt">System and Account
-Policies</link>.
-</para>
-
-<note><para>
-<indexterm><primary>fake-permissions module</primary></indexterm>
-<indexterm><primary>VFS module</primary></indexterm>
-<indexterm><primary>fake_perms</primary></indexterm>
-Under NO circumstances should the profile directory (or its contents) be made read-only because this may
-render the profile unusable. Where it is essential to make a profile read-only within the UNIX file system,
-this can be done, but then you absolutely must use the <command>fake-permissions</command> VFS module to
-instruct MS Windows NT/200x/XP clients that the Profile has write permission for the user. See <link
-linkend="fakeperms">fake_perms VFS module</link>.
-</para></note>
-
-<para>
-<indexterm><primary>NTUser.MAN</primary></indexterm>
-<indexterm><primary>NTUser.DAT</primary></indexterm>
-For MS Windows NT4/200x/XP, the procedure shown in <link linkend="profilemigrn">Profile Migration from Windows
-NT4/200x Server to Samba</link> can also be used to create mandatory profiles. To convert a group profile into
-a mandatory profile, simply locate the <filename>NTUser.DAT</filename> file in the copied profile and rename
-it to <filename>NTUser.MAN</filename>.
-</para>
-
-<para>
-<indexterm><primary>User.MAN</primary></indexterm>
-For MS Windows 9x/Me, it is the <filename>User.DAT</filename> file that must be renamed to
-<filename>User.MAN</filename> to effect a mandatory profile.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Creating and Managing Group Profiles</title>
-
-<para>
-<indexterm><primary>group profiles</primary></indexterm>
-<indexterm><primary>template</primary></indexterm>
-<indexterm><primary>profile migration tool</primary></indexterm>
-<indexterm><primary>profile access rights</primary></indexterm>
-Most organizations are arranged into departments. There is a nice benefit in this fact, since usually
-most users in a department require the same desktop applications and the same desktop layout. MS
-Windows NT4/200x/XP will allow the use of group profiles. A group profile is a profile that is created
-first using a template (example) user. Then using the profile migration tool (see above), the profile is
-assigned access rights for the user group that needs to be given access to the group profile.
-</para>
-
-<para>
-<indexterm><primary>User Manager</primary></indexterm>
-The next step is rather important. Instead of assigning a group profile to users (Using User Manager)
-on a <quote>per-user</quote> basis, the group itself is assigned the now modified profile.
-</para>
-
-<note><para>
-Be careful with group profiles. If the user who is a member of a group also has a personal
-profile, then the result will be a fusion (merge) of the two.
-</para></note>
-
-</sect1>
-
-<sect1>
-<title>Default Profile for Windows Users</title>
-
-<para>
-<indexterm><primary>default profile</primary></indexterm>
-<indexterm><primary>registry keys</primary></indexterm>
-MS Windows 9x/Me and NT4/200x/XP will use a default profile for any user for whom a profile
-does not already exist. Armed with a knowledge of where the default profile is located on the Windows
-workstation, and knowing which registry keys affect the path from which the default profile is created,
-it is possible to modify the default profile to one that has been optimized for the site. This has
-significant administrative advantages.
-</para>
-
-<sect2>
-<title>MS Windows 9x/Me</title>
-
-<para>
-<indexterm><primary>System Policy Editor</primary></indexterm>
-<indexterm><primary>registry</primary></indexterm>
-To enable default per-use profiles in Windows 9x/Me, you can either use the <application>Windows
-98 System Policy Editor</application> or change the registry directly.
-</para>
-
-<para>
-To enable default per-user profiles in Windows 9x/Me, launch the <application>System Policy
-Editor</application>, then select <guimenu>File</guimenu> -> <guimenuitem>Open Registry</guimenuitem>.
-Next click on the <guiicon>Local Computer</guiicon> icon, click on <guilabel>Windows 98 System</guilabel>,
-select <guilabel>User Profiles</guilabel>, and click on the enable box. Remember to save the registry
-changes.
-</para>
-
-<para>
-<indexterm><primary>regedit.exe</primary></indexterm>
-To modify the registry directly, launch the <application>Registry Editor</application>
-(<command>regedit.exe</command>) and select the hive <filename>HKEY_LOCAL_MACHINE\Network\Logon</filename>.
-Now add a DWORD type key with the name <quote>User Profiles.</quote> To enable user profiles to set the value
-to 1; to disable user profiles set it to 0.
-</para>
-
-<sect3>
-<title>User Profile Handling with Windows 9x/Me</title>
-
-<para>
-When a user logs on to a Windows 9x/Me machine, the local profile path,
-<filename>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</filename>, is checked
-for an existing entry for that user.
-</para>
-
-<para>
-If the user has an entry in this registry location, Windows 9x/Me checks for a locally cached
-version of the user profile. Windows 9x/Me also checks the user's home directory (or other specified
-directory if the location has been modified) on the server for the user profile. If a profile exists
-in both locations, the newer of the two is used. If the user profile exists on the server but does not
-exist on the local machine, the profile on the server is downloaded and used. If the user profile only
-exists on the local machine, that copy is used.
-</para>
-
-<para>
-If a user profile is not found in either location, the default user profile from the Windows
-9x/Me machine is used and copied to a newly created folder for the logged on user. At log off, any
-changes that the user made are written to the user's local profile. If the user has a roaming profile,
-the changes are written to the user's profile on the server.
-</para>
-
-</sect3>
-</sect2>
-
-<sect2>
-<title>MS Windows NT4 Workstation</title>
-
-<para>
-On MS Windows NT4, the default user profile is obtained from the location
-<filename>%SystemRoot%\Profiles</filename>, which in a default installation will translate to
-<filename>C:\Windows NT\Profiles</filename>. Under this directory on a clean install, there will be three
-directories: <filename>Administrator</filename>, <filename>All
-Users,</filename> and <filename>Default
-User</filename>.
-</para>
-
-<para>
-The <filename>All Users</filename> directory contains menu settings that are common across all
-system users. The <filename>Default User</filename> directory contains menu entries that are customizable
-per user depending on the profile settings chosen/created.
-</para>
-
-<para>
-When a new user first logs onto an MS Windows NT4 machine, a new profile is created from:
-</para>
-
-<itemizedlist>
- <listitem><para>All Users settings.</para></listitem>
- <listitem><para>Default User settings (contains the default <filename>NTUser.DAT</filename> file).</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-When a user logs on to an MS Windows NT4 machine that is a member of a Microsoft security domain,
-the following steps are followed for profile handling:
-</para>
-
-<procedure>
- <step> <para> The user's account information that is obtained during the logon process
- contains the location of the user's desktop profile. The profile path may be local to
- the machine or it may be located on a network share. If there exists a profile at the
- location of the path from the user account, then this profile is copied to the location
- <filename>%SystemRoot%\Profiles\%USERNAME%</filename>. This profile then inherits the settings
- in the <filename>All Users</filename> profile in the <filename>%SystemRoot%\Profiles</filename>
- location. </para> </step>
-
- <step> <para> If the user account has a profile path, but at its location a profile does not
- exist, then a new profile is created in the <filename>%SystemRoot%\Profiles\%USERNAME%</filename>
- directory from reading the <filename>Default User</filename> profile. </para> </step>
-
- <step> <para>
-<indexterm><primary>NTConfig.POL</primary></indexterm>
-<indexterm><primary>NETLOGON</primary></indexterm>
-<indexterm><primary>authenticating server</primary></indexterm>
-<indexterm><primary>logon server</primary></indexterm>
-<indexterm><primary>HKEY_CURRENT_USER</primary></indexterm>
- If the NETLOGON share on the authenticating server (logon server) contains
- a policy file (<filename>NTConfig.POL</filename>), then its contents are applied to the
- <filename>NTUser.DAT</filename>, which is applied to the <filename>HKEY_CURRENT_USER</filename>
- part of the registry.
- </para> </step>
-
- <step> <para> When the user logs out, if the profile is set to be a roaming profile, it will be
- written out to the location of the profile. The <filename>NTuser.DAT</filename> file is then
- re-created from the contents of the <filename>HKEY_CURRENT_USER</filename> contents. Thus,
- should there not exist in the NETLOGON share an <filename>NTConfig.POL</filename> at the next
- logon, the effect of the previous <filename>NTConfig.POL</filename> will still be held in the
- profile. The effect of this is known as tattooing.
- </para> </step>
-</procedure>
-
-<para>
-MS Windows NT4 profiles may be <emphasis>local</emphasis> or <emphasis>roaming</emphasis>. A local
-profile is stored in the <filename>%SystemRoot%\Profiles\%USERNAME%</filename> location. A roaming
-profile will also remain stored in the same way, unless the following registry key is created:
-<screen>
-HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
-winlogon\"DeleteRoamingCache"=dword:0000000
-</screen>
-In this case, the local copy (in <filename>%SystemRoot%\Profiles\%USERNAME%</filename>) will be deleted
-on logout.
-</para>
-
-<para>
-<indexterm><primary>regedt32</primary></indexterm>
-Under MS Windows NT4, default locations for common resources like <filename>My Documents</filename>
-may be redirected to a network share by modifying the following registry keys. These changes may be
-made via use of the System Policy Editor. To do so may require that you create your own template
-extension for the Policy Editor to allow this to be done through the GUI. Another way to do this is by
-first creating a default user profile, then while logged in as that user, running <command>regedt32</command> to edit
-the key settings.
-</para>
-
-<para>
-The Registry Hive key that affects the behavior of folders that are part of the default user
-profile are controlled by entries on Windows NT4 is:
-<screen>
-HKEY_CURRENT_USER
- \Software
- \Microsoft
- \Windows
- \CurrentVersion
- \Explorer
- \User Shell Folders
-</screen>
-<indexterm><primary>windows registry settings</primary><secondary>default profile locations</secondary></indexterm>
-</para>
-
-<para> The above hive key contains a list of automatically managed
-folders. The default entries are shown in <link linkend="ProfileLocs">the next table</link>.
-</para>
-
-<table frame="all" id="ProfileLocs">
- <title>User Shell Folder Registry Keys Default Values</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row><entry>Name</entry><entry>Default Value</entry></row>
- </thead>
- <tbody>
- <row><entry>AppData</entry><entry>%USERPROFILE%\Application Data</entry></row>
- <row><entry>Desktop</entry><entry>%USERPROFILE%\Desktop</entry></row>
- <row><entry>Favorites</entry><entry>%USERPROFILE%\Favorites</entry></row>
- <row><entry>NetHood</entry><entry>%USERPROFILE%\NetHood</entry></row>
- <row><entry>PrintHood</entry><entry>%USERPROFILE%\PrintHood</entry></row>
- <row><entry>Programs</entry><entry>%USERPROFILE%\Start Menu\Programs</entry></row>
- <row><entry>Recent</entry><entry>%USERPROFILE%\Recent</entry></row>
- <row><entry>SendTo</entry><entry>%USERPROFILE%\SendTo</entry></row>
- <row><entry>Start Menu </entry><entry>%USERPROFILE%\Start Menu</entry></row>
- <row><entry>Startup</entry><entry>%USERPROFILE%\Start Menu\Programs\Startup</entry></row>
- </tbody>
- </tgroup>
-</table>
-
-<para> The registry key that contains the location of the default profile settings is:
-<screen>
-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\
-User Shell Folders
-</screen>
-</para>
-
-<para>
-The default entries are shown in <link linkend="regkeys">Defaults of Profile Settings Registry Keys</link>.
-</para>
-
-<table frame="all" id="regkeys">
- <title>Defaults of Profile Settings Registry Keys</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="left"/>
- <tbody>
- <row><entry>Common Desktop</entry><entry>%SystemRoot%\Profiles\All Users\Desktop</entry></row>
- <row><entry>Common Programs</entry><entry>%SystemRoot%\Profiles\All Users\Programs</entry></row>
- <row><entry>Common Start Menu</entry><entry>%SystemRoot%\Profiles\All Users\Start Menu</entry></row>
- <row><entry>Common Startup</entry><entry>%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</entry></row>
- </tbody>
- </tgroup>
-</table>
-
-</sect2>
-
-<sect2>
-<title>MS Windows 200x/XP</title>
-
-<note><para>
-<indexterm><primary>GPOs</primary></indexterm>
-<indexterm><primary>Windows XP Home Edition</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>domain security</primary></indexterm>
-MS Windows XP Home Edition does use default per-user profiles, but cannot participate
-in domain security, cannot log onto an NT/ADS-style domain, and thus can obtain the profile only
-from itself. While there are benefits in doing this, the beauty of those MS Windows clients that
-can participate in domain logon processes is that they allow the administrator to create a global default
-profile and enforce it through the use of Group Policy Objects (GPOs).
-</para></note>
-
-<para>
-<indexterm><primary>Default User</primary></indexterm>
-When a new user first logs onto an MS Windows 200x/XP machine, the default profile is obtained from
-<filename>C:\Documents and Settings\Default User</filename>. The administrator can modify or change the
-contents of this location, and MS Windows 200x/XP will gladly use it. This is far from the optimum arrangement,
-since it will involve copying a new default profile to every MS Windows 200x/XP client workstation.
-</para>
-
-<para>
-<indexterm><primary>NETLOGON</primary></indexterm>
-When MS Windows 200x/XP participates in a domain security context, and if the default user profile is not
-found, then the client will search for a default profile in the NETLOGON share of the authenticating server.
-In MS Windows parlance, it is <filename>%LOGONSERVER%\NETLOGON\Default User,</filename>
-and if one exists there, it will copy this to the workstation in the <filename>C:\Documents and
-Settings\</filename> under the Windows login name of the use.
-</para>
-
-<note> <para> This path translates, in Samba parlance, to the &smb.conf;
-<smbconfsection name="[NETLOGON]"/> share. The directory should be created at the root
-of this share and must be called <filename>Default User</filename>.
-</para> </note>
-
-<para> If a default profile does not exist in this location, then MS Windows 200x/XP will use the local
-default profile. </para>
-
-<para> On logging out, the user's desktop profile is stored to the location specified in the registry
-settings that pertain to the user. If no specific policies have been created or passed to the client
-during the login process (as Samba does automatically), then the user's profile is written to the
-local machine only under the path <filename>C:\Documents and Settings\%USERNAME%</filename>. </para>
-
-<para> Those wishing to modify the default behavior can do so through these three methods: </para>
-
-<itemizedlist>
- <listitem> <para> Modify the registry keys on the local machine manually and place the new
- default profile in the NETLOGON share root. This is not recommended because it is maintenance intensive.
- </para> </listitem>
-
- <listitem> <para> Create an NT4-style NTConfig.POL file that specifies this behavior and locate
- this file in the root of the NETLOGON share along with the new default profile. </para> </listitem>
-
- <listitem> <para> Create a GPO that enforces this through Active Directory, and place the new
- default profile in the NETLOGON share. </para> </listitem>
-</itemizedlist>
-
-<para>The registry hive key that affects the behavior of folders that are part of the default user
-profile are controlled by entries on Windows 200x/XP is: </para>
-
-<para> <filename>HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell
-Folders\</filename> </para>
-
-<para>
-This hive key contains a list of automatically managed folders. The default entries are shown
-in <link linkend="defregpthkeys">the next table</link>
-<indexterm><primary>windows registry settings</primary><secondary>default profile locations</secondary></indexterm>
-</para>
-
-
-<table frame="all" id="defregpthkeys">
- <title>Defaults of Default User Profile Paths Registry Keys</title>
- <tgroup cols="2">
- <colspec align="left"/>
- <colspec align="left"/>
- <thead>
- <row><entry>Name</entry><entry>Default Value</entry></row>
- </thead>
- <tbody>
- <row><entry>AppData</entry><entry>%USERPROFILE%\Application Data</entry></row>
- <row><entry>Cache</entry><entry>%USERPROFILE%\Local Settings\Temporary Internet Files</entry></row>
- <row><entry>Cookies</entry><entry>%USERPROFILE%\Cookies</entry></row>
- <row><entry>Desktop</entry><entry>%USERPROFILE%\Desktop</entry></row>
- <row><entry>Favorites</entry><entry>%USERPROFILE%\Favorites</entry></row>
- <row><entry>History</entry><entry>%USERPROFILE%\Local Settings\History</entry></row>
- <row><entry>Local AppData</entry><entry>%USERPROFILE%\Local Settings\Application Data</entry></row>
- <row><entry>Local Settings</entry><entry>%USERPROFILE%\Local Settings</entry></row>
- <row><entry>My Pictures</entry><entry>%USERPROFILE%\My Documents\My Pictures</entry></row>
- <row><entry>NetHood</entry><entry>%USERPROFILE%\NetHood</entry></row>
- <row><entry>Personal</entry><entry>%USERPROFILE%\My Documents</entry></row>
- <row><entry>PrintHood</entry><entry>%USERPROFILE%\PrintHood</entry></row>
- <row><entry>Programs</entry><entry>%USERPROFILE%\Start Menu\Programs</entry></row>
- <row><entry>Recent</entry><entry>%USERPROFILE%\Recent</entry></row>
- <row><entry>SendTo</entry><entry>%USERPROFILE%\SendTo</entry></row>
- <row><entry>Start Menu</entry><entry>%USERPROFILE%\Start Menu</entry></row>
- <row><entry>Startup</entry><entry>%USERPROFILE%\Start Menu\Programs\Startup</entry></row>
- <row><entry>Templates</entry><entry>%USERPROFILE%\Templates</entry></row>
- </tbody>
- </tgroup>
-</table>
-
-<para> There is also an entry called <quote>Default</quote> that has no value set. The default entry is
-of type <constant>REG_SZ</constant>; all the others are of type <constant>REG_EXPAND_SZ</constant>. </para>
-
-<para> It makes a huge difference to the speed of handling roaming user profiles if all the folders are
-stored on a dedicated location on a network server. This means that it will not be necessary to write
-the Outlook PST file over the network for every login and logout. </para>
-
-<para>
-To set this to a network location, you could use the following examples:
-<screen>
-%LOGONSERVER%\%USERNAME%\Default Folders
-</screen>
-This stores the folders in the user's home directory under a directory called <filename>Default
-Folders</filename>. You could also use:
-<screen>
-\\<replaceable>SambaServer</replaceable>\<replaceable>FolderShare</replaceable>\%USERNAME%
-</screen>
-</para>
-
-<para>
-in which case the default folders are stored in the server named <replaceable>SambaServer</replaceable>
-in the share called <replaceable>FolderShare</replaceable> under a directory that has the name of the
-MS Windows user as seen by the Linux/UNIX file system. </para>
-
-<para> Please note that once you have created a default profile share, you <emphasis>must</emphasis> migrate a user's profile
-(default or custom) to it. </para>
-
-<para> MS Windows 200x/XP profiles may be <emphasis>local</emphasis> or <emphasis>roaming</emphasis>.
- A roaming profile is cached locally unless the following registry key is created:
-
-<indexterm><primary>delete roaming profiles</primary></indexterm>
-</para>
-
-
-<para> <programlisting> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
- winlogon\"DeleteRoamingCache"=dword:00000001</programlisting></para>
-
-<para>
-In this case, the local cache copy is deleted on logout.
-</para>
-</sect2>
-</sect1>
-
-<sect1> <title>Common Errors</title>
-
-<para>
-The following are some typical errors, problems, and questions that have been asked on the Samba mailing lists.
-</para>
-
-<sect2>
-<title>Configuring Roaming Profiles for a Few Users or Groups</title>
-
-<para>
-With Samba-2.2.x, the choice you have is to enable or disable roaming profiles support. It is a
-global-only setting. The default is to have roaming profiles, and the default path will locate them in
-the user's home directory.
-</para>
-
-<para>
-If disabled globally, then no one will have roaming profile ability. If enabled and you want it
-to apply only to certain machines, then on those machines on which roaming profile support is not wanted,
-it is necessary to disable roaming profile handling in the registry of each such machine.
-</para>
-
-<para>
-With Samba, you can have a global profile setting in &smb.conf;, and you can override this by
-per-user settings using the Domain User Manager (as with MS Windows NT4/200x). </para>
-
-<para> In any case, you can configure only one profile per user. That profile can be either: </para>
-
-<itemizedlist>
- <listitem><para>A profile unique to that user.</para></listitem>
- <listitem><para>A mandatory profile (one the user cannot change).</para></listitem>
- <listitem><para>A group profile (really should be mandatory &smbmdash; that is, unchangeable).</para></listitem>
-</itemizedlist>
-
-</sect2>
-
-<sect2> <title>Cannot Use Roaming Profiles</title>
-
-<para> A user requested the following: <quote> I do not want roaming profiles to be implemented. I want
-to give users a local profile alone. I am totally lost with this error. For the past
-two days I tried everything, I googled around but found no useful pointers. Please help me. </quote></para>
-
-<para> The choices are: </para>
-
-<variablelist>
- <varlistentry>
- <term>Local profiles</term> <listitem><para> I know of no registry keys that will allow
- autodeletion of LOCAL profiles on log out.</para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Roaming profiles</term> <listitem><para> As a user logs onto the network, a centrally
- stored profile is copied to the workstation to form a local profile. This local profile
- will persist (remain on the workstation disk) unless a registry key is changed that will
- cause this profile to be automatically deleted on logout. </para></listitem>
- </varlistentry>
-</variablelist>
-
-<para>The roaming profile choices are: </para>
-
-<variablelist>
- <varlistentry>
- <term>Personal roaming profiles</term> <listitem><para> These are typically stored in
- a profile share on a central (or conveniently located local) server. </para>
-
- <para> Workstations cache (store) a local copy of the profile. This cached
- copy is used when the profile cannot be downloaded at next logon. </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Group profiles</term> <listitem><para>These are loaded from a central profile
- server.</para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Mandatory profiles</term> <listitem><para> Mandatory profiles can be created for
- a user as well as for any group that a user is a member of. Mandatory profiles cannot be
- changed by ordinary users. Only the administrator can change or reconfigure a mandatory
- profile. </para></listitem>
- </varlistentry>
-</variablelist>
-
-<para> A Windows NT4/200x/XP profile can vary in size from 130KB to very large. Outlook PST files are
-most often part of the profile and can be many gigabytes in size. On average (in a well controlled environment),
-roaming profile size of 2MB is a good rule of thumb to use for planning purposes. In an undisciplined
-environment, I have seen up to 2GB profiles. Users tend to complain when it takes an hour to log onto a
-workstation, but they harvest the fruits of folly (and ignorance). </para>
-
-<para> The point of this discussion is to show that roaming profiles and good controls of how they can be
-changed as well as good discipline make for a problem-free site. </para>
-
-<para> Microsoft's answer to the PST problem is to store all email in an MS Exchange Server backend. This
-removes the need for a PST file. </para>
-
-<para>Local profiles mean: </para>
-
-<itemizedlist>
- <listitem><para>If each machine is used by many users, then much local disk storage is needed
- for local profiles.</para></listitem> <listitem><para>Every workstation the user logs into has
- its own profile; these can be very different from machine to machine.</para></listitem>
-</itemizedlist>
-
-<para> On the other hand, use of roaming profiles means: </para>
-
-<itemizedlist>
- <listitem><para>The network administrator can control the desktop environment of all users.</para></listitem>
- <listitem><para>Use of mandatory profiles drastically reduces network management overheads.</para></listitem>
- <listitem><para>In the long run, users will experience fewer problems.</para></listitem>
-</itemizedlist>
-
-</sect2>
-
-<sect2>
-<title>Changing the Default Profile</title>
-
-<para><quote>When the client logs onto the domain controller, it searches
-for a profile to download. Where do I put this default profile?</quote></para>
-
-<para>
-<indexterm><primary>default profile</primary></indexterm>
-First, the Samba server needs to be configured as a domain controller. This can be done by
-setting in &smb.conf;: </para>
-
-<smbconfblock>
-<smbconfoption name="security">user</smbconfoption>
-<smbconfoption name="os level">32 (or more)</smbconfoption>
-<smbconfoption name="domain logons">Yes</smbconfoption>
-</smbconfblock>
-
-<para> There must be a <smbconfsection name="[netlogon]"/> share that is world readable. It is
-a good idea to add a logon script to preset printer and drive connections. There is also a facility
-for automatically synchronizing the workstation time clock with that of the logon server (another good
-thing to do). </para>
-
-<note><para> To invoke autodeletion of roaming profiles from the local workstation cache (disk storage), use
-the <application>Group Policy Editor</application> to create a file called <filename>NTConfig.POL</filename>
-with the appropriate entries. This file needs to be located in the <smbconfsection name="netlogon"/>
-share root directory.</para></note>
-
-<para> Windows clients need to be members of the domain. Workgroup machines do not use network logons,
-so they do not interoperate with domain profiles. </para>
-
-<para> For roaming profiles, add to &smb.conf;: </para>
-
-<smbconfblock>
-<smbconfoption name="logon path">\\%N\profiles\%U</smbconfoption>
-<smbconfcomment>Default logon drive is Z:</smbconfcomment>
-<smbconfoption name="logon drive">H:</smbconfoption>
-<smbconfcomment>This requires a PROFILES share that is world writable.</smbconfcomment>
-</smbconfblock>
-
-</sect2>
-
-<sect2>
-<title>Debugging Roaming Profiles and NT4-style Domain Policies</title>
-
-<para>
-Roaming profiles and domain policies are implemented via <command>USERENV.DLL</command>.
-Microsoft Knowledge Base articles <ulink
-url="http://support.microsoft.com/default.aspx?scid=kb;en-us;221833">221833</ulink> and
-<ulink url="http://support.microsoft.com/default.aspx?scid=kb;en-us;154120">154120</ulink>
- describe how to instruct that DLL to debug the login process.
-</para>
-
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="rights">
-<chapterinfo>
- &author.jerry;
- &author.jht;
-</chapterinfo>
-
-<title>User Rights and Privileges</title>
-
-<para>
-<indexterm><primary>Windows user</primary></indexterm>
-<indexterm><primary>Windows group</primary></indexterm>
-<indexterm><primary>machine accounts</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-The administration of Windows user, group, and machine accounts in the Samba
-domain-controlled network necessitates interfacing between the MS Windows
-networking environment and the UNIX operating system environment. The right
-(permission) to add machines to the Windows security domain can be assigned
-(set) to non-administrative users both in Windows NT4 domains and
-Active Directory domains.
-</para>
-
-<para>
-<indexterm><primary>Windows NT4/2kX/XPPro</primary></indexterm>
-<indexterm><primary>machine account</primary></indexterm>
-<indexterm><primary>trusted</primary></indexterm>
-<indexterm><primary>user logons</primary></indexterm>
-The addition of Windows NT4/2kX/XPPro machines to the domain necessitates the
-creation of a machine account for each machine added. The machine account is
-a necessity that is used to validate that the machine can be trusted to permit
-user logons.
-</para>
-
-<para>
-<indexterm><primary>user accounts</primary></indexterm>
-<indexterm><primary>special account</primary></indexterm>
-<indexterm><primary>account name</primary></indexterm>
-<indexterm><primary>/bin/false</primary></indexterm>
-<indexterm><primary>/dev/null</primary></indexterm>
-<indexterm><primary>man-in-the-middle</primary></indexterm>
-Machine accounts are analogous to user accounts, and thus in implementing them on a UNIX machine that is
-hosting Samba (i.e., on which Samba is running), it is necessary to create a special type of user account.
-Machine accounts differ from normal user accounts in that the account name (login ID) is terminated with a
-<literal>$</literal> sign. An additional difference is that this type of account should not ever be able to
-log into the UNIX environment as a system user and therefore is set to have a shell of
-<command>/bin/false</command> and a home directory of <command>/dev/null.</command> The machine
-account is used only to authenticate domain member machines during start-up. This security measure
-is designed to block man-in-the-middle attempts to violate network integrity.
-</para>
-
-<note><para>
-<indexterm><primary>computer accounts</primary></indexterm>
-<indexterm><primary>domain member servers</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>credentials</primary></indexterm>
-<indexterm><primary>secure authentication</primary></indexterm>
-Machine (computer) accounts are used in the Windows NT OS family to store security
-credentials for domain member servers and workstations. When the domain member
-starts up, it goes through a validation process that includes an exchange of
-credentials with a domain controller. If the domain member fails to authenticate
-using the credentials known for it by domain controllers, the machine will be refused
-all access by domain users. The computer account is essential to the way that MS
-Windows secures authentication.
-</para></note>
-
-<para>
-<indexterm><primary>UNIX system accounts</primary></indexterm>
-<indexterm><primary>system administrator</primary></indexterm>
-<indexterm><primary>root</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-The creation of UNIX system accounts has traditionally been the sole right of
-the system administrator, better known as the <constant>root</constant> account.
-It is possible in the UNIX environment to create multiple users who have the
-same UID. Any UNIX user who has a UID=0 is inherently the same as the
-<constant>root</constant> account user.
-</para>
-
-<para>
-<indexterm><primary>system interface scripts</primary></indexterm>
-<indexterm><primary>CIFS function calls</primary></indexterm>
-<indexterm><primary>root account</primary></indexterm>
-<indexterm><primary>UNIX host system</primary></indexterm>
-All versions of Samba call system interface scripts that permit CIFS function
-calls that are used to manage users, groups, and machine accounts
-in the UNIX environment. All versions of Samba up to and including version 3.0.10
-required the use of a Windows administrator account that unambiguously maps to
-the UNIX <constant>root</constant> account to permit the execution of these
-interface scripts. The requirement to do this has understandably met with some
-disdain and consternation among Samba administrators, particularly where it became
-necessary to permit people who should not possess <constant>root</constant>-level
-access to the UNIX host system.
-</para>
-
-<sect1>
-<title>Rights Management Capabilities</title>
-
-<para>
-<indexterm><primary>Windows privilege model</primary></indexterm>
-<indexterm><primary>privilege model</primary></indexterm>
-<indexterm><primary>rights assigned</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-Samba 3.0.11 introduced support for the Windows privilege model. This model
-allows certain rights to be assigned to a user or group SID. In order to enable
-this feature, <smbconfoption name="enable privileges">yes</smbconfoption>
-must be defined in the <smbconfsection name="global"/> section of the &smb.conf; file.
-</para>
-
-<para>
-<indexterm><primary>rights</primary></indexterm>
-<indexterm><primary>privileges</primary></indexterm>
-<indexterm><primary>manage privileges</primary></indexterm>
-Currently, the rights supported in Samba are listed in <link linkend="rp-privs"/>.
-The remainder of this chapter explains how to manage and use these privileges on Samba servers.
-</para>
-
-<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
-<indexterm><primary>SePrintOperatorPrivilege</primary></indexterm>
-<indexterm><primary>SeAddUsersPrivilege</primary></indexterm>
-<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
-<indexterm><primary>SeDiskOperatorPrivilege</primary></indexterm>
-<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
-<table id="rp-privs">
- <title>Current Privilege Capabilities</title>
- <tgroup cols="2">
- <colspec align="right"/>
- <colspec align="left"/>
- <thead>
- <row>
- <entry align="left">Privilege</entry>
- <entry align="left">Description</entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry><para>SeMachineAccountPrivilege</para></entry>
- <entry><para>Add machines to domain</para></entry>
- </row>
- <row>
- <entry><para>SePrintOperatorPrivilege</para></entry>
- <entry><para>Manage printers</para></entry>
- </row>
- <row>
- <entry><para>SeAddUsersPrivilege</para></entry>
- <entry><para>Add users and groups to the domain</para></entry>
- </row>
- <row>
- <entry><para>SeRemoteShutdownPrivilege</para></entry>
- <entry><para>Force shutdown from a remote system</para></entry>
- </row>
- <row>
- <entry><para>SeDiskOperatorPrivilege</para></entry>
- <entry><para>Manage disk share</para></entry>
- </row>
-<!-- These are not used at this time - so void them from the docs.
- <row>
- <entry><para>SeBackupPrivilege</para></entry>
- <entry><para>Back up files and directories</para></entry>
- </row>
- <row>
- <entry><para>SeRestorePrivilege</para></entry>
- <entry><para>Restore files and directories</para></entry>
- </row>
-**** End of commented out section **** -->
- <row>
- <entry><para>SeTakeOwnershipPrivilege</para></entry>
- <entry><para>Take ownership of files or other objects</para></entry>
- </row>
- </tbody>
- </tgroup>
-</table>
-
-<sect2>
-<title>Using the <quote>net rpc rights</quote> Utility</title>
-
-<para>
-<indexterm><primary>managing rights</primary></indexterm>
-<indexterm><primary>rights assigned</primary></indexterm>
-<indexterm><primary>NT4 User Manager for Domains</primary></indexterm>
-<indexterm><primary>command-line utility</primary></indexterm>
-<indexterm><primary>administrative actions</primary></indexterm>
-There are two primary means of managing the rights assigned to users and groups
-on a Samba server. The <command>NT4 User Manager for Domains</command> may be
-used from any Windows NT4, 2000, or XP Professional domain member client to
-connect to a Samba domain controller and view/modify the rights assignments.
-This application, however, appears to have bugs when run on a client running
-Windows 2000 or later; therefore, Samba provides a command-line utility for
-performing the necessary administrative actions.
-</para>
-
-<para>
-The <command>net rpc rights</command> utility in Samba 3.0.11 has three new subcommands:
-</para>
-
-<variablelist>
- <varlistentry><term>list [name|accounts]</term>
- <listitem><para>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>list</tertiary></indexterm>
-<indexterm><primary>available rights</primary></indexterm>
-<indexterm><primary>privileges assigned</primary></indexterm>
-<indexterm><primary>privileged accounts</primary></indexterm>
- When called with no arguments, <command>net rpc list</command>
- simply lists the available rights on the server. When passed
- a specific user or group name, the tool lists the privileges
- currently assigned to the specified account. When invoked using
- the special string <constant>accounts</constant>,
- <command>net rpc rights list</command> returns a list of all
- privileged accounts on the server and the assigned rights.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>grant <user> <right [right ...]></term>
- <listitem><para>
-<indexterm><primary>assign rights</primary></indexterm>
-<indexterm><primary>grant rights</primary></indexterm>
-<indexterm><primary>add client machines</primary></indexterm>
-<indexterm><primary>user or group</primary></indexterm>
- When called with no arguments, this function is used to assign
- a list of rights to a specified user or group. For example,
- to grant the members of the Domain Admins group on a Samba domain controller,
- the capability to add client machines to the domain, one would run:
-<screen>
-&rootprompt; net -S server -U domadmin rpc rights grant \
- 'DOMAIN\Domain Admins' SeMachineAccountPrivilege
-</screen>
- The following syntax has the same result:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights grant</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc rights grant 'DOMAIN\Domain Admins' \
- SeMachineAccountPrivilege -S server -U domadmin
-</screen>
- More than one privilege can be assigned by specifying a
- list of rights separated by spaces. The parameter 'Domain\Domain Admins'
- must be quoted with single ticks or using double-quotes to prevent
- the backslash and the space from being interpreted by the system shell.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>revoke <user> <right [right ...]></term>
- <listitem><para>
- This command is similar in format to <command>net rpc rights grant</command>. Its
- effect is to remove an assigned right (or list of rights) from a user or group.
- </para></listitem>
- </varlistentry>
-
-</variablelist>
-
-<note><para>
-<indexterm><primary>member</primary></indexterm>
-<indexterm><primary>Domain Admins</primary></indexterm>
-<indexterm><primary>revoke privileges</primary></indexterm>
-You must be connected as a member of the Domain Admins group to be able to grant or revoke privileges assigned
-to an account. This capability is inherent to the Domain Admins group and is not configurable. There are no
-default rights and privileges, except the ability for a member of the Domain Admins group to assign them.
-This means that all administrative rights and privileges (other than the ability to assign them) must be
-explicitly assigned, even for the Domain Admins group.
-</para></note>
-
-<para>
-<indexterm><primary>performed as root</primary></indexterm>
-<indexterm><primary>necessary rights</primary></indexterm>
-<indexterm><primary>add machine script</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-By default, no privileges are initially assigned to any account because certain actions will be performed as
-root once smbd determines that a user has the necessary rights. For example, when joining a client to a
-Windows domain, <parameter>add machine script</parameter> must be executed with superuser rights in most
-cases. For this reason, you should be very careful about handing out privileges to accounts.
-</para>
-
-<para>
-<indexterm><primary>Access</primary></indexterm>
-<indexterm><primary>root user</primary></indexterm>
-<indexterm><primary>bypasses privilege</primary></indexterm>
-Access as the root user (UID=0) bypasses all privilege checks.
-</para>
-
-</sect2>
-
-<sect2>
-<title>Description of Privileges</title>
-
-<para>
-<indexterm><primary>privileges</primary></indexterm>
-<indexterm><primary>additional privileges</primary></indexterm>
-<indexterm><primary>house-keeping</primary></indexterm>
-The privileges that have been implemented in Samba-3.0.11 are shown below. It is possible, and likely, that
-additional privileges may be implemented in later releases of Samba. It is also likely that any privileges
-currently implemented but not used may be removed from future releases as a housekeeping matter, so it is
-important that the successful as well as unsuccessful use of these facilities should be reported on the Samba
-mailing lists.
-</para>
-
-<variablelist>
- <varlistentry><term>SeAddUsersPrivilege</term>
- <listitem><para>
-<indexterm><primary>SeAddUsersPrivilege</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>net rpc user add</primary></indexterm>
- This right determines whether or not smbd will allow the
- user to create new user or group accounts via such tools
- as <command>net rpc user add</command> or
- <command>NT4 User Manager for Domains.</command>
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>SeDiskOperatorPrivilege</term>
- <listitem><para>
-<indexterm><primary>SeDiskOperatorPrivilege</primary></indexterm>
-<indexterm><primary>add/delete/change share</primary></indexterm>
-<indexterm><primary>ACL</primary></indexterm>
- Accounts that possess this right will be able to execute
- scripts defined by the <command>add/delete/change</command>
- share command in &smb.conf; file as root. Such users will
- also be able to modify the ACL associated with file shares
- on the Samba server.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>SeMachineAccountPrivilege</term>
- <listitem><para>
-<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
-<indexterm><primary>right to join domain</primary></indexterm>
-<indexterm><primary>join client</primary></indexterm>
- This right controls whether or not the user can join client
- machines to a Samba-controlled domain.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>SePrintOperatorPrivilege</term>
- <listitem><para>
-<indexterm><primary>SePrintOperatorPrivilege</primary></indexterm>
-<indexterm><primary>privilege</primary></indexterm>
-<indexterm><primary>global right</primary></indexterm>
-<indexterm><primary>administrative rights</primary></indexterm>
-<indexterm><primary>printers admin</primary></indexterm>
- Administrative rights to printers are only controlled exclusively
- by this right and the security descriptor associated with the
- printer object in the registry.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>SeRemoteShutdownPrivilege</term>
- <listitem><para>
-<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
-<indexterm><primary>rebooting server</primary></indexterm>
-<indexterm><primary>aborting shutdown</primary></indexterm>
- Samba provides two hooks for shutting down or rebooting
- the server and for aborting a previously issued shutdown
- command. Since this is an operation normally limited by
- the operating system to the root user, an account must possess this
- right to be able to execute either of these hooks.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>SeTakeOwnershipPrivilege</term>
- <listitem><para>
-<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
-<indexterm><primary>take ownership</primary></indexterm>
- This right permits users to take ownership of files and directories.
- </para></listitem>
- </varlistentry>
-
-</variablelist>
-
-</sect2>
-
-<sect2>
-<title>Privileges Supported by Windows 2000 Domain Controllers</title>
-
-<para>
- For reference purposes, a Windows NT4 Primary Domain Controller reports support for the following
- privileges:
-<indexterm><primary>SeCreateTokenPrivilege</primary></indexterm>
-<indexterm><primary>SeAssignPrimaryTokenPrivilege</primary></indexterm>
-<indexterm><primary>SeLockMemoryPrivilege</primary></indexterm>
-<indexterm><primary>SeIncreaseQuotaPrivilege</primary></indexterm>
-<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
-<indexterm><primary>SeTcbPrivilege</primary></indexterm>
-<indexterm><primary>SeSecurityPrivilege</primary></indexterm>
-<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
-<indexterm><primary>SeLoadDriverPrivilege</primary></indexterm>
-<indexterm><primary>SeSystemProfilePrivilege</primary></indexterm>
-<indexterm><primary>SeSystemtimePrivilege</primary></indexterm>
-<indexterm><primary>SeProfileSingleProcessPrivilege</primary></indexterm>
-<indexterm><primary>SeIncreaseBasePriorityPrivilege</primary></indexterm>
-<indexterm><primary>SeCreatePagefilePrivilege</primary></indexterm>
-<indexterm><primary>SeCreatePermanentPrivilege</primary></indexterm>
-<indexterm><primary>SeBackupPrivilege</primary></indexterm>
-<indexterm><primary>SeRestorePrivilege</primary></indexterm>
-<indexterm><primary>SeShutdownPrivilege</primary></indexterm>
-<indexterm><primary>SeDebugPrivilege</primary></indexterm>
-<indexterm><primary>SeAuditPrivilege</primary></indexterm>
-<indexterm><primary>SeSystemEnvironmentPrivilege</primary></indexterm>
-<indexterm><primary>SeChangeNotifyPrivilege</primary></indexterm>
-<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
-<screen>
- SeCreateTokenPrivilege Create a token object
- SeAssignPrimaryTokenPrivilege Replace a process level token
- SeLockMemoryPrivilege Lock pages in memory
- SeIncreaseQuotaPrivilege Increase quotas
- SeMachineAccountPrivilege Add workstations to domain
- SeTcbPrivilege Act as part of the operating system
- SeSecurityPrivilege Manage auditing and security log
- SeTakeOwnershipPrivilege Take ownership of files or other objects
- SeLoadDriverPrivilege Load and unload device drivers
- SeSystemProfilePrivilege Profile system performance
- SeSystemtimePrivilege Change the system time
-SeProfileSingleProcessPrivilege Profile single process
-SeIncreaseBasePriorityPrivilege Increase scheduling priority
- SeCreatePagefilePrivilege Create a pagefile
- SeCreatePermanentPrivilege Create permanent shared objects
- SeBackupPrivilege Back up files and directories
- SeRestorePrivilege Restore files and directories
- SeShutdownPrivilege Shut down the system
- SeDebugPrivilege Debug programs
- SeAuditPrivilege Generate security audits
- SeSystemEnvironmentPrivilege Modify firmware environment values
- SeChangeNotifyPrivilege Bypass traverse checking
- SeRemoteShutdownPrivilege Force shutdown from a remote system
-</screen>
- And Windows 200x/XP Domain Controllers and workstations reports to support the following privileges:
-<indexterm><primary>SeCreateTokenPrivilege</primary></indexterm>
-<indexterm><primary>SeAssignPrimaryTokenPrivilege</primary></indexterm>
-<indexterm><primary>SeLockMemoryPrivilege</primary></indexterm>
-<indexterm><primary>SeIncreaseQuotaPrivilege</primary></indexterm>
-<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
-<indexterm><primary>SeTcbPrivilege</primary></indexterm>
-<indexterm><primary>SeSecurityPrivilege</primary></indexterm>
-<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
-<indexterm><primary>SeLoadDriverPrivilege</primary></indexterm>
-<indexterm><primary>SeSystemProfilePrivilege</primary></indexterm>
-<indexterm><primary>SeSystemtimePrivilege</primary></indexterm>
-<indexterm><primary>SeProfileSingleProcessPrivilege</primary></indexterm>
-<indexterm><primary>SeIncreaseBasePriorityPrivilege</primary></indexterm>
-<indexterm><primary>SeCreatePagefilePrivilege</primary></indexterm>
-<indexterm><primary>SeCreatePermanentPrivilege</primary></indexterm>
-<indexterm><primary>SeBackupPrivilege</primary></indexterm>
-<indexterm><primary>SeRestorePrivilege</primary></indexterm>
-<indexterm><primary>SeShutdownPrivilege</primary></indexterm>
-<indexterm><primary>SeDebugPrivilege</primary></indexterm>
-<indexterm><primary>SeAuditPrivilege</primary></indexterm>
-<indexterm><primary>SeSystemEnvironmentPrivilege</primary></indexterm>
-<indexterm><primary>SeChangeNotifyPrivilege</primary></indexterm>
-<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
-<indexterm><primary>SeUndockPrivilege</primary></indexterm>
-<indexterm><primary>SeSyncAgentPrivilege</primary></indexterm>
-<indexterm><primary>SeEnableDelegationPrivilege</primary></indexterm>
-<indexterm><primary>SeManageVolumePrivilege</primary></indexterm>
-<indexterm><primary>SeImpersonatePrivilege</primary></indexterm>
-<indexterm><primary>SeCreateGlobalPrivilege</primary></indexterm>
-<screen>
- SeCreateTokenPrivilege Create a token object
- SeAssignPrimaryTokenPrivilege Replace a process level token
- SeLockMemoryPrivilege Lock pages in memory
- SeIncreaseQuotaPrivilege Increase quotas
- SeMachineAccountPrivilege Add workstations to domain
- SeTcbPrivilege Act as part of the operating system
- SeSecurityPrivilege Manage auditing and security log
- SeTakeOwnershipPrivilege Take ownership of files or other objects
- SeLoadDriverPrivilege Load and unload device drivers
- SeSystemProfilePrivilege Profile system performance
- SeSystemtimePrivilege Change the system time
-SeProfileSingleProcessPrivilege Profile single process
-SeIncreaseBasePriorityPrivilege Increase scheduling priority
- SeCreatePagefilePrivilege Create a pagefile
- SeCreatePermanentPrivilege Create permanent shared objects
- SeBackupPrivilege Back up files and directories
- SeRestorePrivilege Restore files and directories
- SeShutdownPrivilege Shut down the system
- SeDebugPrivilege Debug programs
- SeAuditPrivilege Generate security audits
- SeSystemEnvironmentPrivilege Modify firmware environment values
- SeChangeNotifyPrivilege Bypass traverse checking
- SeRemoteShutdownPrivilege Force shutdown from a remote system
- SeUndockPrivilege Remove computer from docking station
- SeSyncAgentPrivilege Synchronize directory service data
- SeEnableDelegationPrivilege Enable computer and user accounts to
- be trusted for delegation
- SeManageVolumePrivilege Perform volume maintenance tasks
- SeImpersonatePrivilege Impersonate a client after authentication
- SeCreateGlobalPrivilege Create global objects
-</screen>
-<indexterm><primary>equivalence</primary></indexterm>
- The Samba Team is implementing only those privileges that are logical and useful in the UNIX/Linux
- environment. Many of the Windows 200X/XP privileges have no direct equivalence in UNIX.
- </para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>The Administrator Domain SID</title>
-
-<para>
-<indexterm><primary>domain Administrator</primary></indexterm>
-<indexterm><primary>User Rights and Privileges</primary></indexterm>
-<indexterm><primary>passdb backend</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>net getlocalsid</primary></indexterm>
-Please note that every Windows NT4 and later server requires a domain Administrator account. Samba versions
-commencing with 3.0.11 permit Administrative duties to be performed via assigned rights and privileges
-(see <link linkend="rights">User Rights and Privileges</link>). An account in the server's passdb backend can
-be set to the well-known RID of the default administrator account. To obtain the domain SID on a Samba domain
-controller, run the following command:
-<screen>
-&rootprompt; net getlocalsid
-SID for domain FOO is: S-1-5-21-4294955119-3368514841-2087710299
-</screen>
-<indexterm><primary>RID</primary></indexterm>
-You may assign the domain administrator RID to an account using the <command>pdbedit</command>
-command as shown here:
-<indexterm><primary>pdbedit</primary></indexterm>
-<screen>
-&rootprompt; pdbedit -U S-1-5-21-4294955119-3368514841-2087710299-500 -u root -r
-</screen>
-</para>
-
-<note><para>
-<indexterm><primary>RID 500</primary></indexterm>
-<indexterm><primary>well known RID</primary></indexterm>
-<indexterm><primary>rights and privileges</primary></indexterm>
-<indexterm><primary>root account</primary></indexterm>
-The RID 500 is the well known standard value of the default Administrator account. It is the RID
-that confers the rights and privileges that the Administrator account has on a Windows machine
-or domain. Under UNIX/Linux the equivalent is UID=0 (the root account).
-</para></note>
-
-<para>
-<indexterm><primary>without Administrator account</primary></indexterm>
-<indexterm><primary>equivalent rights and privileges</primary></indexterm>
-<indexterm><primary>Windows group account</primary></indexterm>
-<indexterm><primary>3.0.11</primary></indexterm>
-Releases of Samba version 3.0.11 and later make it possible to operate without an Administrator account
-provided equivalent rights and privileges have been established for a Windows user or a Windows
-group account.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
- <sect2>
- <title>What Rights and Privileges Will Permit Windows Client Administration?</title>
-
- <para>
-<indexterm><primary>domain global</primary></indexterm>
-<indexterm><primary>local group</primary></indexterm>
-<indexterm><primary>administrative rights</primary></indexterm>
-<indexterm><primary>Windows client</primary></indexterm>
- When a Windows NT4 (or later) client joins a domain, the domain global <literal>Domain Admins</literal> group
- is added to the membership of the local <literal>Administrators</literal> group on the client. Any user who is
- a member of the domain global <literal>Domain Admins</literal> group will have administrative rights on the
- Windows client.
- </para>
-
- <para>
-<indexterm><primary>desirable solution</primary></indexterm>
-<indexterm><primary>administrative rights and privileges</primary></indexterm>
-<indexterm><primary>Power Users</primary></indexterm>
-<indexterm><primary>domain global user</primary></indexterm>
-<indexterm><primary>domain global group</primary></indexterm>
- This is often not the most desirable solution because it means that the user will have administrative
- rights and privileges on domain servers also. The <literal>Power Users</literal> group on Windows client
- workstations permits local administration of the workstation alone. Any domain global user or domain global
- group can be added to the membership of the local workstation group <literal>Power Users</literal>.
- </para>
-
- <para>
-<indexterm><primary>Nested Group Support</primary></indexterm>
-<indexterm><primary>add domain users and groups to a local group</primary></indexterm>
-<indexterm><primary>net</primary></indexterm>
-<indexterm><primary>Windows workstation.</primary></indexterm>
- See <link linkend="nestedgrpmgmgt">Nested Group Support</link> for an example of how to add domain users
- and groups to a local group that is on a Windows workstation. The use of the <command>net</command>
- command permits this to be done from the Samba server.
- </para>
-
- <para>
-<indexterm><primary>cmd</primary></indexterm>
-<indexterm><primary>cmd shell</primary></indexterm>
-<indexterm><primary>net</primary><secondary>localgroup</secondary></indexterm>
- Another way this can be done is to log onto the Windows workstation as the user
- <literal>Administrator</literal>, then open a <command>cmd</command> shell, then execute:
-<screen>
-&dosprompt; net localgroup administrators /add <userinput>domain_name\entity</userinput>
-</screen>
- where <literal>entity</literal> is either a domain user or a domain group account name.
- </para>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="ch-ldap-tls">
-<chapterinfo>
- &author.ghenry;
- <pubdate>July 8, 2005</pubdate>
-</chapterinfo>
-<title>LDAP and Transport Layer Security</title>
-
-<sect1 id="s1-intro-ldap-tls">
-<title>Introduction</title>
-
- <para>
- <indexterm><primary>Transport Layer Seccurity, TLS</primary><secondary>Introduction</secondary></indexterm>
-<indexterm><primary>ACL</primary></indexterm>
- Up until now, we have discussed the straightforward configuration of <trademark>OpenLDAP</trademark>,
- with some advanced features such as ACLs. This does not however, deal with the fact that the network
- transmissions are still in plain text. This is where <firstterm>Transport Layer Security (TLS)</firstterm>
- comes in.
- </para>
-
- <para>
-<indexterm><primary>RFC 2830</primary></indexterm>
- <trademark>OpenLDAP</trademark> clients and servers are capable of using the Transport Layer Security (TLS)
- framework to provide integrity and confidentiality protections in accordance with <ulink
- url="http://rfc.net/rfc2830.html">RFC 2830</ulink>; <emphasis>Lightweight Directory Access Protocol (v3):
- Extension for Transport Layer Security.</emphasis>
- </para>
-
- <para>
-<indexterm><primary>X.509 certificates</primary></indexterm>
- TLS uses X.509 certificates. All servers are required to have valid certificates, whereas client certificates
- are optional. We will only be discussing server certificates.
- </para>
-
- <tip><para>
-<indexterm><primary>DN</primary></indexterm>
-<indexterm><primary>CN</primary></indexterm>
-<indexterm><primary>FQDN</primary></indexterm>
- The DN of a server certificate must use the CN attribute to name the server, and the CN must carry the
- server's fully qualified domain name (FQDN). Additional alias names and wildcards may be present in the
- <option>subjectAltName</option> certificate extension. More details on server certificate names are in <ulink
- url="http://rfc.net/rfc2830.html">RFC2830</ulink>.
- </para></tip>
-
- <para>
- We will discuss this more in the next sections.
- </para>
-
- </sect1>
-
- <sect1 id="s1-config-ldap-tls">
- <title>Configuring</title>
-
- <para>
- <indexterm><primary>Transport Layer Seccurity, TLS</primary><secondary>Configuring</secondary></indexterm>
- Now on to the good bit.
- </para>
-
- <sect2 id="s1-config-ldap-tls-certs">
- <title>Generating the Certificate Authority</title>
-
- <para>
-<indexterm><primary>Certificate Authority</primary><see>CA</see></indexterm>
- In order to create the relevant certificates, we need to become our own Certificate Authority (CA).
- <footnote><para>We could however, get our generated server certificate signed by proper CAs, like <ulink
- url="http://www.thawte.com/">Thawte</ulink> and <ulink url="http://www.verisign.com/">VeriSign</ulink>, which
- you pay for, or the free ones, via <ulink url="http://www.cacert.org/">CAcert</ulink>
- </para></footnote> This is necessary, so we can sign the server certificate.
- </para>
-
- <para>
-<indexterm><primary>OpenSSL</primary></indexterm>
- We will be using the <ulink url="http://www.openssl.org">OpenSSL</ulink> <footnote><para>The downside to
- making our own CA, is that the certificate is not automatically recognized by clients, like the commercial
- ones are.</para></footnote> software for this, which is included with every great <trademark
- class="registered">Linux</trademark> distribution.
- </para>
-
- <para>
- TLS is used for many types of servers, but the instructions<footnote><para>For information straight from the
- horse's mouth, please visit <ulink
- url="http://www.openssl.org/docs/HOWTO/">http://www.openssl.org/docs/HOWTO/</ulink>; the main OpenSSL
- site.</para></footnote> presented here, are tailored for &OL;.
- </para>
-
- <note><para>
- The <emphasis>Common Name (CN)</emphasis>, in the following example, <emphasis>MUST</emphasis> be
- the fully qualified domain name (FQDN) of your ldap server.
- </para></note>
-
- <para>
- First we need to generate the CA:
-<screen width="90">
-<computeroutput>
-&rootprompt; mkdir myCA
-</computeroutput>
-</screen>
- Move into that directory:
-<screen width="90">
-<computeroutput>
-&rootprompt; cd myCA
-</computeroutput>
-</screen>
- Now generate the CA:<footnote><para>Your <filename>CA.pl</filename> or <filename>CA.sh</filename> might not be
- in the same location as mine is, you can find it by using the <command>locate</command> command, i.e.,
- <command>locate CA.pl</command>. If the command complains about the database being too old, run
- <command>updatedb</command> as <emphasis>root</emphasis> to update it.</para></footnote>
-<screen width="90">
-<computeroutput>
-&rootprompt; /usr/share/ssl/misc/CA.pl -newca
-CA certificate filename (or enter to create)
-
-Making CA certificate ...
-Generating a 1024 bit RSA private key
-.......................++++++
-.............................++++++
-writing new private key to './demoCA/private/cakey.pem'
-Enter PEM pass phrase:
-Verifying - Enter PEM pass phrase:
------
-You are about to be asked to enter information that will be incorporated
-into your certificate request.
-What you are about to enter is what is called a Distinguished Name or a DN.
-There are quite a few fields but you can leave some blank
-For some fields there will be a default value,
-If you enter '.', the field will be left blank.
------
-Country Name (2 letter code) [AU]:AU
-State or Province Name (full name) [Some-State]:NSW
-Locality Name (eg, city) []:Sydney
-Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abmas
-Organizational Unit Name (eg, section) []:IT
-Common Name (eg, YOUR name) []:ldap.abmas.biz
-Email Address []:support@abmas.biz
-</computeroutput>
-</screen>
- </para>
-
- <para>
- There are some things to note here.
- </para>
-
- <orderedlist>
- <listitem>
- <para>
- You <emphasis>MUST</emphasis> remember the password, as we will need
- it to sign the server certificate..
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <emphasis>Common Name (CN)</emphasis>, <emphasis>MUST</emphasis> be the
- fully qualified domain name (FQDN) of your ldap server.
- </para>
- </listitem>
- </orderedlist>
-
- </sect2>
-
- <sect2 id="s1-config-ldap-tls-server">
- <title>Generating the Server Certificate</title>
-
- <para>
- Now we need to generate the server certificate:
-<screen width="90">
-<computeroutput>
-&rootprompt; openssl req -new -nodes -keyout newreq.pem -out newreq.pem
-Generating a 1024 bit RSA private key
-.............++++++
-........................................................++++++
-writing new private key to 'newreq.pem'
------
-You are about to be asked to enter information that will be incorporated
-into your certificate request.
-What you are about to enter is what is called a Distinguished Name or a DN.
-There are quite a few fields but you can leave some blank
-For some fields there will be a default value,
-If you enter '.', the field will be left blank.
------
-Country Name (2 letter code) [AU]:AU
-State or Province Name (full name) [Some-State]:NSW
-Locality Name (eg, city) []:Sydney
-Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abmas
-Organizational Unit Name (eg, section) []:IT
-Common Name (eg, YOUR name) []:ldap.abmas.biz
-Email Address []:support@abmas.biz
-
-Please enter the following 'extra' attributes
-to be sent with your certificate request
-A challenge password []:
-An optional company name []:
-</computeroutput>
-</screen>
- </para>
-
- <para>
- Again, there are some things to note here.
- </para>
-
- <orderedlist>
- <listitem>
- <para>
- You should <emphasis>NOT</emphasis> enter a password.
- </para>
- </listitem>
-
- <listitem>
- <para>
- The <emphasis>Common Name (CN)</emphasis>, <emphasis>MUST</emphasis> be
- the fully qualified domain name (FQDN) of your ldap server.
- </para>
- </listitem>
- </orderedlist>
-
- <para>
- Now we sign the certificate with the new CA:
-<screen width="90">
-<computeroutput>
-&rootprompt; /usr/share/ssl/misc/CA.pl -sign
-Using configuration from /etc/ssl/openssl.cnf
-Enter pass phrase for ./demoCA/private/cakey.pem:
-Check that the request matches the signature
-Signature ok
-Certificate Details:
-Serial Number: 1 (0x1)
-Validity
- Not Before: Mar 6 18:22:26 2005 EDT
- Not After : Mar 6 18:22:26 2006 EDT
-Subject:
- countryName = AU
- stateOrProvinceName = NSW
- localityName = Sydney
- organizationName = Abmas
- organizationalUnitName = IT
- commonName = ldap.abmas.biz
- emailAddress = support@abmas.biz
-X509v3 extensions:
- X509v3 Basic Constraints:
- CA:FALSE
- Netscape Comment:
- OpenSSL Generated Certificate
- X509v3 Subject Key Identifier:
- F7:84:87:25:C4:E8:46:6D:0F:47:27:91:F0:16:E0:86:6A:EE:A3:CE
- X509v3 Authority Key Identifier:
- keyid:27:44:63:3A:CB:09:DC:B1:FF:32:CC:93:23:A4:F1:B4:D5:F0:7E:CC
- DirName:/C=AU/ST=NSW/L=Sydney/O=Abmas/OU=IT/
- CN=ldap.abmas.biz/emailAddress=support@abmas.biz
- serial:00
-
-Certificate is to be certified until Mar 6 18:22:26 2006 EDT (365 days)
-Sign the certificate? [y/n]:y
-
-
-1 out of 1 certificate requests certified, commit? [y/n]y
-Write out database with 1 new entries
-Data Base Updated
-Signed certificate is in newcert.pem
-</computeroutput>
-</screen>
- </para>
-
- <para>
- That completes the server certificate generation.
- </para>
-
- </sect2>
-
- <sect2 id="s1-config-ldap-tls-install">
- <title>Installing the Certificates</title>
-
- <para>
- Now we need to copy the certificates to the right configuration directories,
- rename them at the same time (for convenience), change the ownership and
- finally the permissions:
-<screen width="90">
-<computeroutput>
-&rootprompt; cp demoCA/cacert.pem /etc/openldap/
-&rootprompt; cp newcert.pem /etc/openldap/servercrt.pem
-&rootprompt; cp newreq.pem /etc/openldap/serverkey.pem
-&rootprompt; chown ldap.ldap /etc/openldap/*.pem
-&rootprompt; chmod 640 /etc/openldap/cacert.pem;
-&rootprompt; chmod 600 /etc/openldap/serverkey.pem
-</computeroutput>
-</screen>
- </para>
-
- <para>
- Now we just need to add these locations to <filename>slapd.conf</filename>,
- anywhere before the <option>database</option> declaration as shown here:
-<screen width="90">
-<computeroutput>
-TLSCertificateFile /etc/openldap/servercrt.pem
-TLSCertificateKeyFile /etc/openldap/serverkey.pem
-TLSCACertificateFile /etc/openldap/cacert.pem
-</computeroutput>
-</screen>
- </para>
-
- <para>
- Here is the declaration and <filename>ldap.conf</filename>:
-<filename>ldap.conf</filename>
-<screen width="90">
-<computeroutput>
-TLS_CACERT /etc/openldap/cacert.pem
-</computeroutput>
-</screen>
- </para>
-
- <para>
- That's all there is to it. Now on to <xref linkend="s1-test-ldap-tls"></xref>
- </para>
-
- </sect2>
-
-</sect1>
-
-<sect1 id="s1-test-ldap-tls">
-<title>Testing</title>
-
-<para>
-<indexterm><primary>Transport Layer Security, TLS</primary><secondary>Testing</secondary></indexterm>
-This is the easy part. Restart the server:
-<screen width="90">
-<computeroutput>
-&rootprompt; /etc/init.d/ldap restart
-Stopping slapd: [ OK ]
-Checking configuration files for slapd: config file testing succeeded
-Starting slapd: [ OK ]
-</computeroutput>
-</screen>
- Then, using <command>ldapsearch</command>, test an anonymous search with the
- <option>-ZZ</option><footnote><para>See <command>man ldapsearch</command></para></footnote> option:
-<screen width="90">
-<computeroutput>
-&rootprompt; ldapsearch -x -b "dc=ldap,dc=abmas,dc=biz" \
- -H 'ldap://ldap.abmas.biz:389' -ZZ
-</computeroutput>
-</screen>
- Your results should be the same as before you restarted the server, for example:
-<screen width="90">
-<computeroutput>
-&rootprompt; ldapsearch -x -b "dc=ldap,dc=abmas,dc=biz" \
- -H 'ldap://ldap.abmas.biz:389' -ZZ
-
-# extended LDIF
-#
-# LDAPv3
-# base <> with scope sub
-# filter: (objectclass=*)
-# requesting: ALL
-#
-
-# abmas.biz
-dn: dc=ldap,dc=abmas,dc=biz
-objectClass: dcObject
-objectClass: organization
-o: Abmas
-dc: abmas
-
-# Manager, ldap.abmas.biz
-dn: cn=Manager,dc=ldap,dc=abmas,dc=biz
-objectClass: organizationalRole
-cn: Manager
-
-# ABMAS, abmas.biz
-dn: sambaDomainName=ABMAS,dc=ldap,dc=abmas,dc=biz
-sambaDomainName: ABMAS
-sambaSID: S-1-5-21-238355452-1056757430-1592208922
-sambaAlgorithmicRidBase: 1000
-objectClass: sambaDomain
-sambaNextUserRid: 67109862
-sambaNextGroupRid: 67109863
-</computeroutput>
-</screen>
- If you have any problems, please read <xref linkend="s1-int-ldap-tls"></xref>
-</para>
-
-</sect1>
-
-<sect1 id="s1-int-ldap-tls">
-<title>Troubleshooting</title>
-
-<para>
-<indexterm><primary>Transport Layer Security, TLS</primary><secondary>Troubleshooting</secondary></indexterm>
-The most common error when configuring TLS, as I have already mentioned numerous times, is that the
-<emphasis>Common Name (CN)</emphasis> you entered in <xref linkend="s1-config-ldap-tls-server"></xref> is
-<emphasis>NOT</emphasis> the Fully Qualified Domain Name (FQDN) of your ldap server.
-</para>
-
-<para>
-Other errors could be that you have a typo somewhere in your <command>ldapsearch</command> command, or that
-your have the wrong permissions on the <filename>servercrt.pem</filename> and <filename>cacert.pem</filename>
-files. They should be set with <command>chmod 640</command>, as per <xref
-linkend="s1-config-ldap-tls-install"></xref>.
-</para>
-
-<para>
-For anything else, it's best to read through your ldap logfile or join the &OL; mailing list.
-</para>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="securing-samba">
-
-<chapterinfo>
- &author.tridge;
- &author.jht;
- <pubdate>May 26, 2003</pubdate>
-</chapterinfo>
-
-<title>Securing Samba</title>
-
-<sect1>
-<title>Introduction</title>
-
-<para>
-<indexterm><primary>security</primary></indexterm>
-<indexterm><primary>direct internet access</primary></indexterm>
-<indexterm><primary>firewall</primary></indexterm>
-<indexterm><primary>private network</primary></indexterm>
-<indexterm><primary>barriers</primary></indexterm>
-<indexterm><primary>deterents</primary></indexterm>
-<indexterm><primary>secured networks</primary></indexterm>
-The information contained in this chapter applies in general to all Samba installations. Security is
-everyone's concern in the information technology world. A surprising number of Samba servers are being
-installed on machines that have direct internet access, thus security is made more critical than it would have been had the
-server been located behind a firewall and on a private network. Paranoia regarding server security is causing
-some network administrators to insist on the installation of robust firewalls even on servers that are located
-inside secured networks. This chapter provides information to assist the administrator who understands
-how to create the needed barriers and deterents against <quote>the enemy</quote>, no matter where [s]he may
-come from.
-</para>
-
-<blockquote>
-<para>
-A new apprentice reported for duty to the chief engineer of a boiler house. He said, <quote>Here I am,
-if you will show me the boiler I'll start working on it.</quote> Then engineer replied, <quote>You're leaning
-on it!</quote>
-</para>
-</blockquote>
-
-<para>
-Security concerns are just like that. You need to know a little about the subject to appreciate
-how obvious most of it really is. The challenge for most of us is to discover that first morsel
-of knowledge with which we may unlock the secrets of the masters.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>moderately secure</primary></indexterm>
-<indexterm><primary>perimeter firewall</primary></indexterm>
-<indexterm><primary>host security</primary></indexterm>
-<indexterm><primary>Samba security</primary></indexterm>
-There are three levels at which security principles must be observed in order to render a site
-at least moderately secure. They are the perimeter firewall, the configuration of the host
-server that is running Samba, and Samba itself.
-</para>
-
-<para>
-Samba permits a most flexible approach to network security. As far as possible Samba implements
-the latest protocols to permit more secure MS Windows file and print operations.
-</para>
-
-<para>
-<indexterm><primary>host-based protection</primary></indexterm>
-<indexterm><primary>interface-based exclusion</primary></indexterm>
-<indexterm><primary>resource-based exclusion</primary></indexterm>
-Samba can be secured from connections that originate from outside the local network. This can be done using
-<emphasis>host-based protection</emphasis>, using Samba's implementation of a technology known as
-<quote>tcpwrappers,</quote> or it may be done be using <emphasis>interface-based exclusion</emphasis> so
-&smbd; will bind only to specifically permitted interfaces. It is also possible to set specific share- or
-resource-based exclusions, for example, on the <smbconfsection name="[IPC$]"/> autoshare. The <smbconfsection
-name="[IPC$]"/> share is used for browsing purposes as well as to establish TCP/IP connections.
-</para>
-
-<para>
-<indexterm><primary>Access Control Entries</primary><see>ACE</see></indexterm>
-<indexterm><primary>ACL</primary></indexterm>
-<indexterm><primary>controls</primary></indexterm>
-Another method by which Samba may be secured is by setting Access Control Entries (ACEs) in an Access
-Control List (ACL) on the shares themselves. This is discussed in
-<link linkend="AccessControls">File, Directory, and Share Access Controls</link>.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Technical Discussion of Protective Measures and Issues</title>
-
-<para>
-The key challenge of security is that protective measures suffice at best
-only to close the door on known exploits and breach techniques. Never assume that
-because you have followed these few measures, the Samba server is now an impenetrable
-fortress! Given the history of information systems so far, it is only a matter of time
-before someone will find yet another vulnerability.
-</para>
-
- <sect2>
- <title>Using Host-Based Protection</title>
-
- <para>
-<indexterm><primary>outside threat</primary></indexterm>
-<indexterm><primary>insecure</primary></indexterm>
-<indexterm><primary>Internet</primary></indexterm>
- In many installations of Samba, the greatest threat comes from outside
- your immediate network. By default, Samba accepts connections from
- any host, which means that if you run an insecure version of Samba on
- a host that is directly connected to the Internet, you can be
- especially vulnerable.
- </para>
-
- <para>
-<indexterm><primary>allow access</primary></indexterm>
-<indexterm><primary>range of hosts</primary></indexterm>
- One of the simplest fixes in this case is to use the <smbconfoption name="hosts allow"/> and
- <smbconfoption name="hosts deny"/> options in the Samba &smb.conf; configuration file to
- allow access to your server only from a specific range of hosts. An example might be:
- <smbconfblock>
- <smbconfoption name="hosts allow">127.0.0.1 192.168.2.0/24 192.168.3.0/24</smbconfoption>
- <smbconfoption name="hosts deny">0.0.0.0/0</smbconfoption>
- </smbconfblock>
- </para>
-
- <para>
-<indexterm><primary>localhost</primary></indexterm>
-<indexterm><primary>private networks</primary></indexterm>
-<indexterm><primary>called name</primary></indexterm>
- The above will allow SMB connections only from <constant>localhost</constant> (your own
- computer) and from the two private networks 192.168.2 and 192.168.3. All other
- connections will be refused as soon as the client sends its first packet. The refusal
- will be marked as <literal>not listening on called name</literal> error.
- </para>
-
- </sect2>
-
- <sect2>
- <title>User-Based Protection</title>
-
- <para>
- If you want to restrict access to your server to valid users only, then the following
- method may be of use. In the &smb.conf; <smbconfsection name="[global]"/> section put:
- <smbconfblock>
- <smbconfoption name="valid users">@smbusers, jacko</smbconfoption>
- </smbconfblock>
- </para>
-
- <para>
-<indexterm><primary>smbusers</primary></indexterm>
- This restricts all server access either to the user <emphasis>jacko</emphasis>
- or to members of the system group <emphasis>smbusers</emphasis>.
- </para>
-
- </sect2>
-
- <sect2>
-
- <title>Using Interface Protection</title>
-
- <para>
-<indexterm><primary>network interface</primary></indexterm>
-<indexterm><primary>accept connections</primary></indexterm>
-<indexterm><primary>Internet</primary></indexterm>
- By default, Samba accepts connections on any network interface that
- it finds on your system. That means if you have an ISDN line or a PPP
- connection to the Internet then Samba will accept connections on those
- links. This may not be what you want.
- </para>
-
- <para>
- You can change this behavior using options like this:
- <smbconfblock>
- <smbconfoption name="interfaces">eth* lo</smbconfoption>
- <smbconfoption name="bind interfaces only">yes</smbconfoption>
- </smbconfblock>
- </para>
-
- <para>
-<indexterm><primary>interfaces</primary></indexterm>
-<indexterm><primary>loopback interface</primary></indexterm>
-<indexterm><primary>Ethernet adapters</primary></indexterm>
-<indexterm><primary>listen for connections</primary></indexterm>
- This tells Samba to listen for connections only on interfaces with a name starting with
- <constant>eth</constant> such as <constant>eth0</constant> or <constant>eth1</constant>, plus on the loopback interface called
- <constant>lo</constant>. The name you will need to use depends on what OS you are using. In the above, I used
- the common name for Ethernet adapters on Linux.
- </para>
-
- <para>
-<indexterm><primary>PPP</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>cracker</primary></indexterm>
-<indexterm><primary>confirm address</primary></indexterm>
- If you use the above and someone tries to make an SMB connection to your host over a PPP interface called
- <constant>ppp0</constant>, then [s]he will get a TCP connection refused reply. In that case, no Samba code
- is run at all, because the operating system has been told not to pass connections from that interface to any
- Samba process. However, the refusal helps a would-be cracker by confirming that the IP address provides
- valid active services.
- </para>
-
- <para>
-<indexterm><primary>ignore connection</primary></indexterm>
-<indexterm><primary>refusing connection</primary></indexterm>
-<indexterm><primary>exploitation</primary></indexterm>
-<indexterm><primary>denial of service</primary></indexterm>
-<indexterm><primary>firewall</primary></indexterm>
- A better response would be to ignore the connection (from, for example, ppp0) altogether. The
- advantage of ignoring the connection attempt, as compared with refusing it, is that it foils those who
- probe an interface with the sole intention of finding valid IP addresses for later use in exploitation
- or denial of service attacks. This method of dealing with potential malicious activity demands the
- use of appropriate firewall mechanisms.
- </para>
-
- </sect2>
-
- <sect2 id="firewallports">
- <title>Using a Firewall</title>
-
- <para>
-<indexterm><primary>deny access</primary></indexterm>
-<indexterm><primary>exposed</primary></indexterm>
-<indexterm><primary>firewall active</primary></indexterm>
- Many people use a firewall to deny access to services they do not want exposed outside their network. This can
- be a good idea, although I recommend using it in conjunction with the above methods so you are protected even
- if your firewall is not active for some reason.
- </para>
-
- <para>
- If you are setting up a firewall, you need to know what TCP and UDP ports to allow and block. Samba uses
- the following:
-<indexterm><primary>Port 135/TCP</primary></indexterm>
-<indexterm><primary>Port 137/UDP</primary></indexterm>
-<indexterm><primary>Port 138/UDP</primary></indexterm>
-<indexterm><primary>Port 139/TCP</primary></indexterm>
-<indexterm><primary>Port 445/TCP</primary></indexterm>
- </para>
-
- <simplelist>
- <member>Port 135/TCP - used by smbd</member>
- <member>Port 137/UDP - used by nmbd</member>
- <member>Port 138/UDP - used by nmbd</member>
- <member>Port 139/TCP - used by smbd</member>
- <member>Port 445/TCP - used by smbd</member>
- </simplelist>
-
- <para>
-<indexterm><primary>firewall setups</primary></indexterm>
- The last one is important because many older firewall setups may not be aware of it, given that this port
- was only added to the protocol in recent years.
- </para>
-
- <para>
-<indexterm><primary>configuring a firewall</primary></indexterm>
-<indexterm><primary>high order ports</primary></indexterm>
-<indexterm><primary>block incoming packets</primary></indexterm>
- When configuring a firewall, the high order ports (1024-65535) are often used for outgoing connections and
- therefore should be permitted through the firewall. It is prudent to block incoming packets on the high order
- ports except for established connections.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Using IPC$ Share-Based Denials </title>
-
- <para>
-<indexterm><primary>IPC$</primary></indexterm>
-<indexterm><primary>deny</primary></indexterm>
-<indexterm><primary>security hole</primary></indexterm>
- If the above methods are not suitable, then you could also place a more specific deny on the IPC$ share that
- is used in the recently discovered security hole. This allows you to offer access to other shares while
- denying access to IPC$ from potentially untrustworthy hosts.
- </para>
-
- <para>
- To do this you could use:
- <smbconfblock>
- <smbconfsection name="[IPC$]"/>
- <smbconfoption name="hosts allow">192.168.115.0/24 127.0.0.1</smbconfoption>
- <smbconfoption name="hosts deny">0.0.0.0/0</smbconfoption>
- </smbconfblock>
- </para>
-
- <para>
-<indexterm><primary>IPC$</primary></indexterm>
-<indexterm><primary>protection against attackers</primary></indexterm>
-<indexterm><primary>valid username/password</primary></indexterm>
- This instructs Samba that IPC$ connections are not allowed from anywhere except the two listed network
- addresses (localhost and the 192.168.115 subnet). Connections to other shares are still allowed. Because the
- IPC$ share is the only share that is always accessible anonymously, this provides some level of protection
- against attackers who do not know a valid username/password for your host.
- </para>
-
- <para>
-<indexterm><primary>access denied</primary></indexterm>
-<indexterm><primary>IPC$</primary></indexterm>
-<indexterm><primary>browse shares</primary></indexterm>
- If you use this method, then clients will be given an <literal>`access denied'</literal> reply when they try
- to access the IPC$ share. Those clients will not be able to browse shares and may also be unable to access
- some other resources. This is not recommended unless for some reason you cannot use one of the other methods
- just discussed.
- </para>
-
- </sect2>
-
- <sect2>
- <title>NTLMv2 Security</title>
-
- <para>
-<indexterm><primary>NTLMv2</primary></indexterm>
- To configure NTLMv2 authentication, the following registry keys are worth knowing about:
- </para>
-
- <para>
- <screen>
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
- "lmcompatibilitylevel"=dword:00000003
- </screen>
- </para>
-
- <para>
- The value 0x00000003 means to send NTLMv2 response only. Clients will use NTLMv2 authentication;
- use NTLMv2 session security if the server supports it. Domain controllers accept LM,
- NTLM, and NTLMv2 authentication.
- </para>
-
- <para>
- <screen>
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
- "NtlmMinClientSec"=dword:00080000
- </screen>
- </para>
-
- <para>
- The value 0x00080000 means permit only NTLMv2 session security. If either NtlmMinClientSec or
- NtlmMinServerSec is set to 0x00080000, the connection will fail if NTLMv2
- session security is negotiated.
- </para>
- </sect2>
-</sect1>
-
-<sect1>
-<title>Upgrading Samba</title>
-
-<para>
-<indexterm><primary>updates</primary></indexterm>
-<indexterm><primary>important announcements</primary></indexterm>
-<indexterm><primary>security vulnerability</primary></indexterm>
-Please check regularly on <ulink noescape="1" url="http://www.samba.org/">http://www.samba.org/</ulink> for
-updates and important announcements. Occasionally security releases are made, and it is highly recommended to
-upgrade Samba promptly when a security vulnerability is discovered. Check with your OS vendor for OS-specific
-upgrades.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-If all Samba and host platform configurations were really as intuitive as one might like them to be, this
-chapter would not be necessary. Security issues are often vexing for a support person to resolve, not because
-of the complexity of the problem, but because most administrators who post what turns out to be a security
-problem request are totally convinced that the problem is with Samba.
-</para>
-
- <sect2>
- <title>Smbclient Works on Localhost, but the Network Is Dead</title>
-
- <para>
- This is a common problem. Linux vendors tend to install a default firewall.
- With the default firewall in place, only traffic on the loopback adapter (IP address 127.0.0.1)
- is allowed through the firewall.
- </para>
-
- <para>
- The solution is either to remove the firewall (stop it) or modify the firewall script to
- allow SMB networking traffic through. See <link linkend="firewallports">the Using a
- Firewall</link> section.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Why Can Users Access Other Users' Home Directories?</title>
-
- <para>
- <quote>
-<indexterm><primary>mapping home directory</primary></indexterm>
-<indexterm><primary>own home directory</primary></indexterm>
- We are unable to keep individual users from mapping to any other user's home directory once they have
- supplied a valid password! They only need to enter their own password. I have not found any method to
- configure Samba so that users may map only their own home directory.
- </quote>
- </para>
-
- <para><quote>
- User xyzzy can map his home directory. Once mapped, user xyzzy can also map anyone else's home directory.
- </quote></para>
-
- <para>
-<indexterm><primary>security flaw</primary></indexterm>
-<indexterm><primary>defined shares</primary></indexterm>
- This is not a security flaw, it is by design. Samba allows users to have exactly the same access to the UNIX
- file system as when they were logged on to the UNIX box, except that it only allows such views onto the file
- system as are allowed by the defined shares.
- </para>
-
- <para>
-<indexterm><primary>UNIX home directories</primary></indexterm>
-<indexterm><primary>permissions</primary></indexterm>
- If your UNIX home directories are set up so that one user can happily <command>cd</command>
- into another user's directory and execute <command>ls</command>, the UNIX security solution is to change file
- permissions on the user's home directories so that the <command>cd</command> and <command>ls</command> are denied.
- </para>
-
- <para>
-<indexterm><primary>security policies</primary></indexterm>
-<indexterm><primary>permissions</primary></indexterm>
- Samba tries very hard not to second guess the UNIX administrator's security policies and
- trusts the UNIX admin to set the policies and permissions he or she desires.
- </para>
-
- <para>
- Samba allows the behavior you require. Simply put the <smbconfoption name="only user">%S</smbconfoption>
- option in the <smbconfsection name="[homes]"/> share definition.
- </para>
-
- <para>
- The <smbconfoption name="only user"></smbconfoption> works in conjunction with the <smbconfoption name="users">list</smbconfoption>,
- so to get the behavior you require, add the line:
- <smbconfblock>
- <smbconfoption name="users">%S</smbconfoption>
- </smbconfblock>
- This is equivalent to adding
- <smbconfblock>
- <smbconfoption name="valid users">%S</smbconfoption>
- </smbconfblock>
- to the definition of the <smbconfsection name="[homes]"/> share, as recommended in
- the &smb.conf; man page.
- </para>
- </sect2>
-
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="ServerType">
-<chapterinfo>
- &author.tridge;
- &author.jelmer;
- &author.jht;
-</chapterinfo>
-
-<title>Server Types and Security Modes</title>
-
-<para>
-<indexterm><primary>migrate</primary></indexterm>
-<indexterm><primary>security mode</primary></indexterm>
-This chapter provides information regarding the types of server that Samba may be configured to be. A
-Microsoft network administrator who wishes to migrate to or use Samba will want to know the meaning, within a
-Samba context, of terms familiar to the MS Windows administrator. This means that it is essential also to
-define how critical security modes function before we get into the details of how to configure the server
-itself.
-</para>
-
-<para>
-This chapter provides an overview of the security modes of which Samba is capable and how they relate to MS
-Windows servers and clients.
-</para>
-
-<para>
-A question often asked is, <quote>Why would I want to use Samba?</quote> Most chapters contain a section that
-highlights features and benefits. We hope that the information provided will help to answer this question. Be
-warned though, we want to be fair and reasonable, so not all features are positive toward Samba. The benefit
-may be on the side of our competition.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It
-hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion
-and fury befitting his anguish. The other looked at the stone and said, <quote>This is a garnet.
-I can turn that into a precious gem and some day it will make a princess very happy!</quote>
-</para>
-
-<para>
-The moral of this tale: Two men, two very different perspectives regarding the same stone.
-Like it or not, Samba is like that stone. Treat it the right way and it can bring great
-pleasure, but if you are forced to use it and have no time for its secrets, then it can be
-a source of discomfort.
-</para>
-
-<para>
-<indexterm><primary>UNIX</primary><secondary>server</secondary></indexterm>
-<indexterm><primary>interoperability</primary></indexterm>
-Samba started out as a project that sought to provide interoperability for MS Windows 3.x
-clients with a UNIX server. It has grown up a lot since its humble beginnings and now provides
-features and functionality fit for large-scale deployment. It also has some warts. In sections
-like this one, we tell of both.
-</para>
-
-<para>
-So, what are the benefits of the features mentioned in this chapter?
-</para>
-
-<itemizedlist>
- <listitem><para>
- <indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
- Samba can replace an MS Windows NT4 domain controller.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>active directory</primary></indexterm>
- Samba offers excellent interoperability with MS Windows NT4-style
- domains as well as natively with Microsoft Active Directory domains.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>interdomain</primary><secondary>trustrs</secondary></indexterm>
- Samba permits full NT4-style interdomain trusts.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>authentication</primary></indexterm>
- <indexterm><primary>security</primary><secondary>modes</secondary></indexterm>
- Samba has security modes that permit more flexible authentication
- than is possible with MS Windows NT4 domain controllers.
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>account</primary><secondary>database</secondary><tertiary>backends</tertiary></indexterm>
- <indexterm><primary>encrypted</primary></indexterm>
- Samba permits use of multiple account database backends.
- (Encrypted passwords that are stored in the account database are in
- formats that are unique to Windows networking).
- </para></listitem>
-
- <listitem><para>
- <indexterm><primary>replicated</primary></indexterm>
- The account database backends can be distributed
- and replicated using multiple methods. This gives Samba
- greater flexibility than MS Windows NT4 and in many cases a
- significantly higher utility than Active Directory domains
- with MS Windows 200x.
- </para></listitem>
-</itemizedlist>
-
-</sect1>
-
-<sect1>
-<title>Server Types</title>
-
-
-<para>
-<indexterm><primary>Server Type</primary></indexterm>
-Administrators of Microsoft networks often refer to three different types of servers:
-</para>
-
-<itemizedlist>
- <listitem><para>Domain Controller</para>
- <itemizedlist>
- <listitem><para>Primary Domain Controller (PDC)</para></listitem>
- <listitem><para>Backup Domain Controller (BDC)</para></listitem>
- <listitem><para>ADS Domain Controller</para></listitem>
- </itemizedlist>
- </listitem>
- <listitem><para>Domain Member Server</para>
- <itemizedlist>
- <listitem><para>Active Directory Domain Server</para></listitem>
- <listitem><para>NT4 Style Domain Domain Server</para></listitem>
- </itemizedlist>
- </listitem>
- <listitem><para>Standalone Server</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>domain</primary><secondary>control</secondary></indexterm>
-<indexterm><primary>domain</primary><secondary>member</secondary></indexterm>
-<indexterm><primary>domain control</primary><secondary>primary</secondary></indexterm>
-<indexterm><primary>domain control</primary><secondary>backup</secondary></indexterm>
-The chapters covering domain control (<link linkend="samba-pdc">Domain Control</link>),
-backup domain control (<link linkend="samba-bdc">Backup Domain Control</link>), and
-domain membership (<link linkend="domain-member">Domain Membership</link>) provide
-pertinent information regarding Samba configuration for each of these server roles.
-You are strongly encouraged to become intimately familiar with these chapters because
-they lay the foundation for deployment of Samba domain security.
-</para>
-
-<para>
-<indexterm><primary>standalone</primary></indexterm>
-A Standalone server is autonomous in respect of the source of its account backend.
-Refer to <link linkend="StandAloneServer">Standalone Servers</link> to gain a wider appreciation
-of what is meant by a server being configured as a <emphasis>standalone</emphasis> server.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Samba Security Modes</title>
-
-
-<para>
-<indexterm><primary>Security Mode</primary></indexterm>
-<indexterm><primary>security</primary></indexterm>
-In this section, the function and purpose of Samba's security modes are described. An accurate understanding of
-how Samba implements each security mode as well as how to configure MS Windows clients for each mode will
-significantly reduce user complaints and administrator heartache.
-</para>
-
-<para>
-<indexterm><primary>Server Message Block</primary><see>SMB</see></indexterm>
-<indexterm><primary>Common Internet Filesystem</primary><see>CIFS</see></indexterm>
-Microsoft Windows networking uses a protocol that was originally called the Server Message Block (SMB)
-protocol. Since some time around 1996 the protocol has been better known as the Common Internet Filesystem
-(CIFS) protocol.
-</para>
-
-<para>
-<indexterm><primary>security levels</primary></indexterm>
-<indexterm><primary>security modes</primary></indexterm>
-<indexterm><primary>user-level</primary></indexterm>
-Samba has three ways of implementing <emphasis>user-level</emphasis> security. Collectively, we call the Samba
-implementations of the security levels <emphasis>security modes</emphasis>. They are known as
-<emphasis>user</emphasis>, <emphasis>domain</emphasis> and
-<emphasis>ADS</emphasis> modes. They are documented in this chapter.
-</para>
-
-<para>
-The term <literal>client</literal> refers to all agents whether it is a Windows workstation, a Windows server,
-another Samba server, or any vanilla SMB or CIFS client application (e.g., <command>smbclient</command>) that
-make use of services provided by an SMB/CIFS server.
-</para>
-
-<sect2>
-<title>User Level Security</title>
-
-<para>
-<indexterm><primary>user-level</primary></indexterm>
-We describe user-level security first because its simpler. In user-level security, the client sends a session
-setup request directly following protocol negotiation. This request provides a username and password. The
-server can either accept or reject that username/password combination. At this stage the server has no idea
-what share the client will eventually try to connect to, so it can't base the
-<emphasis>accept/reject</emphasis> on anything other than:
-</para>
-
-<orderedlist>
-<listitem><para>the username/password.</para></listitem>
-<listitem><para>the name of the client machine.</para></listitem>
-</orderedlist>
-
-<para>
-<indexterm><primary>credentials</primary></indexterm>
-If the server accepts the username/password credentials, the client expects to be able to mount shares (using
-a <emphasis>tree connection</emphasis>) without further specifying a password. It expects that all access
-rights will be as the username/password credentials set that was specified in the initial <emphasis>session
-setup</emphasis>.
-</para>
-
-<para>
-<indexterm><primary>session setup</primary></indexterm>
-It is also possible for a client to send multiple <emphasis>session setup</emphasis>
-requests. When the server responds, it gives the client a <emphasis>uid</emphasis> to use
-as an authentication tag for that username/password. The client can maintain multiple
-authentication contexts in this way (WinDD is an example of an application that does this).
-</para>
-
-<para>
-<indexterm><primary>LanManager</primary></indexterm>
-<indexterm><primary>case-preserving</primary></indexterm>
-<indexterm><primary>case-insensitive</primary></indexterm>
-<indexterm><primary>upper-case</primary></indexterm>
-<indexterm><primary>lower-case</primary></indexterm>
-Windows networking user account names are case-insensitive, meaning that upper-case and lower-case characters
-in the account name are considered equivalent. They are said to be case-preserving, but not case significant.
-Windows and LanManager systems previous to Windows NT version 3.10 have case-insensitive passwords that were
-not necessarily case-preserving. All Windows NT family systems treat passwords as case-preserving and
-case-sensitive.
-</para>
-
-<sect3>
-<title>Example Configuration</title>
-
-<para>
-The &smb.conf; parameter that sets user-level security is:
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="security">user</smbconfoption>
-</smbconfblock></para>
-
-<para>
-This is the default setting since Samba-2.2.x.
-</para>
-
-</sect3>
-
-</sect2>
-<sect2>
-<title>Domain Security Mode (User-Level Security)</title>
-
-<para>
-<indexterm><primary>domain</primary><secondary>controllers</secondary></indexterm>
-<indexterm><primary>security</primary><secondary>controllers</secondary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>logon</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-Domain security provides a mechanism for storing all user and group accounts in a central, shared, account
-repository. The centralized account repository is shared between domain (security) controllers. Servers that
-act as domain controllers provide authentication and validation services to all machines that participate in
-the security context for the domain. A primary domain controller (PDC) is a server that is responsible for
-maintaining the integrity of the security account database. Backup domain controllers (BDCs) provide only domain
-logon and authentication services. Usually, BDCs will answer network logon requests more responsively than
-will a PDC.
-</para>
-
-<para>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>trust account</primary></indexterm>
-<indexterm><primary>trust</primary><secondary>account</secondary></indexterm>
-<indexterm><primary>domain</primary><secondary>security</secondary></indexterm>
-<indexterm><primary>domain</primary><secondary>controller</secondary></indexterm>
-When Samba is operating in <smbconfoption name="security">domain</smbconfoption> mode, the Samba server has a
-domain security trust account (a machine account) and causes all authentication requests to be passed through
-to the domain controllers. In other words, this configuration makes the Samba server a domain member server,
-even when it is in fact acting as a domain controller. All machines that participate in domain security must
-have a machine account in the security database.
-</para>
-
-<para>
-<indexterm><primary>account</primary><secondary>database</secondary></indexterm>
-<indexterm><primary>machine</primary><secondary>account</secondary></indexterm>
-<indexterm><primary>NetBIOS</primary><secondary>name</secondary></indexterm>
-<indexterm><primary>NetBIOS</primary></indexterm>
-Within the domain security environment, the underlying security architecture uses user-level security. Even
-machines that are domain members must authenticate on startup. The machine account consists of an account
-entry in the accounts database, the name of which is the NetBIOS name of the machine and of which the password
-is randomly generated and known to both the domain controllers and the member machine. If the machine account
-cannot be validated during startup, users will not be able to log on to the domain using this machine because
-it cannot be trusted. The machine account is referred to as a machine trust account.
-</para>
-
-<para>
-There are three possible domain member configurations:
-</para>
-
-<orderedlist>
- <listitem><para>Primary domain controller (PDC) - of which there is one per domain.</para></listitem>
- <listitem><para>Backup domain controller (BDC) - of which there can be any number per domain.</para></listitem>
- <listitem><para>Domain member server (DMS) - of which there can be any number per domain.</para></listitem>
-</orderedlist>
-
-<para>
-<indexterm><primary>DMS</primary></indexterm>
-We will discuss each of these in separate chapters. For now, we are most interested in basic DMS
-configuration.
-</para>
-
-<sect3>
-<title>Example Configuration</title>
-<para><emphasis>
-Samba as a Domain Member Server
-</emphasis></para>
-
-
-<para>
-<indexterm><primary>server type</primary><secondary>domain member</secondary></indexterm>
-This method involves addition of the following parameters in the &smb.conf; file:
-<smbconfblock>
-<smbconfoption name="security">domain</smbconfoption>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-In order for this method to work, the Samba server needs to join the MS Windows NT
-security domain. This is done as follows:
-<indexterm><primary>net</primary><secondary>rpc</secondary></indexterm>
-<indexterm><primary>Domain Member</primary><secondary>joining</secondary></indexterm>
-</para>
-
-
-<procedure>
- <step><para>On the UNIX/Linux system execute:</para>
-
- <para><screen>&rootprompt;<userinput>net rpc join -U administrator%password</userinput></screen></para>
- </step>
-</procedure>
-
-<para>
-<indexterm><primary>invalid shell</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>/bin/false</primary></indexterm>
-Use of this mode of authentication requires there to be a standard UNIX account for each user in order to
-assign a UID once the account has been authenticated by the Windows domain controller. This account can be
-blocked to prevent logons by clients other than MS Windows through means such as setting an invalid shell in
-the <filename>/etc/passwd</filename> entry. The best way to allocate an invalid shell to a user account is to
-set the shell to the file <filename>/bin/false</filename>.
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-Domain controllers can be located anywhere that is convenient. The best advice is to have a BDC on every
-physical network segment, and if the PDC is on a remote network segment the use of WINS (see <link
-linkend="NetworkBrowsing">Network Browsing</link> for more information) is almost essential.
-</para>
-
-<para>
-An alternative to assigning UIDs to Windows users on a Samba member server is presented in <link
-linkend="winbind">Winbind</link>, <link linkend="winbind">Winbind: Use of Domain Accounts</link>.
-</para>
-
-<para>
-For more information regarding domain membership, <link linkend="domain-member">Domain Membership</link>.
-</para>
-
-</sect3>
-</sect2>
-
-<sect2>
-<title>ADS Security Mode (User-Level Security)</title>
-
-<para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>native mode</primary></indexterm>
-Samba can join an Active Directory domain using NT4 style RPC based security. This is
-possible if the domain is run in native mode. Active Directory in native mode perfectly allows NT4-style
-domain members. This is contrary to popular belief.
-</para>
-
-<para>
-If you are using Active Directory, starting with Samba you can join as a native AD member. Why would you
-want to do that? Your security policy might prohibit the use of NT-compatible authentication protocols. All
-your machines are running Windows 2000 and above and all use Kerberos. In this case, Samba, as an NT4-style
-domain, would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos
-tickets.
-</para>
-
-<para>
-<indexterm><primary>realm</primary></indexterm>
-<indexterm><primary>mixed mode</primary></indexterm>
-Sites that use Microsoft Windows active directory services (ADS) should be aware of the significance of the
-terms: <literal>native mode</literal> and <literal>mixed mode</literal> ADS operation. The term
-<literal>realm</literal> is used to describe a Kerberos-based security architecture (such as is used by
-Microsoft ADS).
-</para>
-
-<sect3>
-<title>Example Configuration</title>
-
-<para><smbconfblock>
-<smbconfoption name="realm">your.kerberos.REALM</smbconfoption>
-<smbconfoption name="security">ADS</smbconfoption>
-</smbconfblock></para>
-
-<para>
-The following parameter may be required:
-</para>
-
-<para><smbconfblock>
-<smbconfoption name="password server">your.kerberos.server</smbconfoption>
-</smbconfblock></para>
-
-<para>
-Please refer to <link linkend="domain-member">Domain Membership</link>, and <link linkend="ads-member">Samba
-ADS Domain Membership</link> for more information regarding this configuration option.
-</para>
-
-</sect3>
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Password Checking</title>
-
-<para>
-MS Windows clients may use encrypted passwords as part of a challenge/response
-authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or clear-text strings for simple
-password-based authentication. It should be realized that with the SMB protocol,
-the password is passed over the network either in plaintext or encrypted, but
-not both in the same authentication request.
-</para>
-
-<para>
-<indexterm><primary>encrypted passwords</primary></indexterm>
-<indexterm><primary>encrypted</primary></indexterm>
-When encrypted passwords are used, a password that has been entered by the user
-is encrypted in two ways:
-</para>
-
-<itemizedlist>
- <listitem><para>An MD4 hash of the unicode of the password
- string. This is known as the NT hash.
- </para></listitem>
-
- <listitem><para>The password is converted to uppercase,
- and then padded or truncated to 14 bytes. This string is
- then appended with 5 bytes of NULL characters and split to
- form two 56-bit DES keys to encrypt a "magic" 8-byte value.
- The resulting 16 bytes form the LanMan hash.
- </para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>plain-text</primary><secondary>passwords</secondary></indexterm>
-MS Windows 95 pre-service pack 1 and MS Windows NT versions 3.x and version 4.0 pre-service pack 3 will use
-either mode of password authentication. All versions of MS Windows that follow these versions no longer
-support plain-text passwords by default.
-</para>
-
-<para>
-<indexterm><primary>cached</primary><secondary>password</secondary></indexterm>
-MS Windows clients have a habit of dropping network mappings that have been idle
-for 10 minutes or longer. When the user attempts to use the mapped drive
-connection that has been dropped, the client re-establishes the connection using
-a cached copy of the password.
-</para>
-
-<para>
-When Microsoft changed the default password mode, support was dropped for caching
-of the plaintext password. This means that when the registry parameter is changed
-to re-enable use of plaintext passwords, it appears to work, but when a dropped
-service connection mapping attempts to revalidate, this will fail if the remote
-authentication server does not support encrypted passwords. It is definitely not
-a good idea to re-enable plaintext password support in such clients.
-</para>
-
-<para>
-The following parameters can be used to work around the issue of Windows 9x/Me clients
-uppercasing usernames and passwords before transmitting them to the SMB server
-when using clear-text authentication:
-</para>
-
-
-<?latex \newpage ?>
-<smbconfblock>
-<smbconfoption name="username level"><replaceable>integer</replaceable></smbconfoption>
-</smbconfblock>
-
-<para>
-By default Samba will convert to lowercase the username before attempting to lookup the user
-in the database of local system accounts. Because UNIX usernames conventionally
-only contain lowercase characters, the <smbconfoption name="username-level"/> parameter
-is rarely needed.
-</para>
-
-<para>
-<indexterm><primary>clear-text</primary></indexterm>
-However, passwords on UNIX systems often make use of mixed-case characters. This means that in order for a
-user on a Windows 9x/Me client to connect to a Samba server using clear-text authentication, the
-password must be in lower case.
-</para>
-
-<para>
-The best option to adopt is to enable support for encrypted passwords wherever
-Samba is used. Most attempts to apply the registry change to re-enable plaintext
-passwords will eventually lead to user complaints and unhappiness.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-We all make mistakes. It is okay to make mistakes, as long as they are made in the right places
-and at the right time. A mistake that causes lost productivity is seldom tolerated; however, a mistake
-made in a developmental test lab is expected.
-</para>
-
-<para>
-Here we look at common mistakes and misapprehensions that have been the subject of discussions
-on the Samba mailing lists. Many of these are avoidable by doing your homework before attempting
-a Samba implementation. Some are the result of a misunderstanding of the English language,
-which has many phrases that are potentially vague and may be highly confusing
-to those for whom English is not their native tongue.
-</para>
-
-<sect2>
-<title>What Makes Samba a Domain Controller?</title>
-
-<para>
-<indexterm><primary>server-mode</primary></indexterm>
-The &smb.conf; parameter <smbconfoption name="security">domain</smbconfoption> does not really make Samba behave
-as a domain controller. This setting means we want Samba to be a domain member. See <link
-linkend="samba-pdc">Samba as a PDC</link> for more information.
-</para>
-
-</sect2>
-
-<sect2>
-<title>What Makes Samba a Domain Member?</title>
-
-<para>
-Guess! So many others do. But whatever you do, do not think that <smbconfoption name="security">user</smbconfoption>
-makes Samba act as a domain member. Read the manufacturer's manual before the warranty expires. See
-<link linkend="domain-member">Domain Membership</link>, for more information.
-</para>
-
-</sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="StandAloneServer">
-<chapterinfo>
- &author.jht;
-</chapterinfo>
-<title>Standalone Servers</title>
-
-<para>
-<indexterm><primary>standalone server</primary></indexterm>
-<indexterm><primary>not domain members</primary></indexterm>
-<indexterm><primary>minimum security control</primary></indexterm>
-Standalone servers are independent of domain controllers on the network.
-They are not domain members and function more like workgroup servers. In many
-cases a standalone server is configured with a minimum of security control
-with the intent that all data served will be readily accessible to all users.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>secure</primary></indexterm>
-<indexterm><primary>insecure</primary></indexterm>
-Standalone servers can be as secure or as insecure as needs dictate. They can
-have simple or complex configurations. Above all, despite the hoopla about
-domain security, they remain a common installation.
-</para>
-
-<para>
-<indexterm><primary>read-only files</primary></indexterm>
-<indexterm><primary>share-mode</primary></indexterm>
-<indexterm><primary>read-only</primary></indexterm>
-<indexterm><primary>standalone server</primary></indexterm>
-If all that is needed is a server for read-only files, or for
-printers alone, it may not make sense to effect a complex installation.
-For example, a drafting office needs to store old drawings and reference
-standards. Nobody can write files to the server because it is legislatively
-important that all documents remain unaltered. A share-mode read-only standalone
-server is an ideal solution.
-</para>
-
-<para>
-<indexterm><primary>simplicity</primary></indexterm>
-<indexterm><primary>printers</primary></indexterm>
-<indexterm><primary>share-mode server</primary></indexterm>
-Another situation that warrants simplicity is an office that has many printers
-that are queued off a single central server. Everyone needs to be able to print
-to the printers, there is no need to effect any access controls, and no files will
-be served from the print server. Again, a share-mode standalone server makes
-a great solution.
-</para>
-</sect1>
-
-<sect1>
-<title>Background</title>
-
-<para>
-<indexterm><primary>standalone server</primary></indexterm>
-<indexterm><primary>local authentication</primary></indexterm>
-<indexterm><primary>access control</primary></indexterm>
-The term <emphasis>standalone server</emphasis> means that it will provide local authentication and access
-control for all resources that are available from it. In general this means that there will be a local user
-database. In more technical terms, it means resources on the machine will be made available in either
-<emphasis>share</emphasis> mode or in <emphasis>user</emphasis> mode.
-</para>
-
-<para>
-<indexterm><primary>create user accounts</primary></indexterm>
-<indexterm><primary>no network logon service</primary></indexterm>
-<indexterm><primary>independent</primary></indexterm>
-No special action is needed other than to create user accounts. Standalone
-servers do not provide network logon services. This means that machines that
-use this server do not perform a domain logon to it. Whatever logon facility
-the workstations are subject to is independent of this machine. It is, however,
-necessary to accommodate any network user so the logon name he or she uses will
-be translated (mapped) locally on the standalone server to a locally known
-user name. There are several ways this can be done.
-</para>
-
-<para>
-<indexterm><primary>local authentication database</primary></indexterm>
-<indexterm><primary>SMB</primary></indexterm>
-<indexterm><primary>not domain member</primary></indexterm>
-Samba tends to blur the distinction a little in defining
-a standalone server. This is because the authentication database may be
-local or on a remote server, even if from the SMB protocol perspective
-the Samba server is not a member of a domain security context.
-</para>
-
-<para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>UNIX-user database</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>/etc/shadow</primary></indexterm>
-<indexterm><primary>local smbpasswd file</primary></indexterm>
-<indexterm><primary>LDAP backend</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-Through the use of Pluggable Authentication Modules (PAM) (see <link linkend="pam">the chapter on PAM</link>)
-and the name service switcher (NSS), which maintains the UNIX-user database, the source of authentication may
-reside on another server. We would be inclined to call this the authentication server. This means that the
-Samba server may use the local UNIX/Linux system password database (<filename>/etc/passwd</filename> or
-<filename>/etc/shadow</filename>), may use a local smbpasswd file, or may use an LDAP backend, or even via PAM
-and Winbind another CIFS/SMB server for authentication.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Example Configuration</title>
-
-<para>
-<indexterm><primary>inspire simplicity</primary></indexterm>
-<indexterm><primary>complexity</primary></indexterm>
-<link linkend="simplynice">The example Reference Documentation Server</link> and <link
-linkend="SimplePrintServer">Central Print Serving</link> are designed to inspire simplicity. It is too easy to
-attempt a high level of creativity and to introduce too much complexity in server and network design.
-</para>
-
-<sect2 id="RefDocServer">
-<title>Reference Documentation Server</title>
-
-<para>
-<indexterm><primary>read-only</primary></indexterm>
-<indexterm><primary>reference documents</primary></indexterm>
-<indexterm><primary>/export</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-Configuration of a read-only data server that everyone can access is very simple. By default, all shares are
-read-only, unless set otherwise in the &smb.conf; file. <link linkend="simplynice">The example - Reference
-Documentation Server</link> is the &smb.conf; file that will do this. Assume that all the reference documents
-are stored in the directory <filename>/export</filename>, and the documents are owned by a user other than
-nobody. No home directories are shared, and there are no users in the <filename>/etc/passwd</filename> UNIX
-system database. This is a simple system to administer.
-</para>
-
-<example id="simplynice">
-<title>smb.conf for Reference Documentation Server</title>
-<smbconfblock>
-<smbconfcomment> Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-<smbconfoption name="netbios name">&example.server.samba;</smbconfoption>
-<smbconfoption name="security">SHARE</smbconfoption>
-<smbconfoption name="passdb backend">guest</smbconfoption>
-<smbconfoption name="wins server">192.168.1.1</smbconfoption>
-<smbconfsection name="[data]"/>
-<smbconfoption name="comment">Data</smbconfoption>
-<smbconfoption name="path">/export</smbconfoption>
-<smbconfoption name="guest only">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<blockquote>
-<attribution>Mark Twain</attribution>
-<para>
-I would have spoken more briefly, if I'd had more time to prepare.
-</para>
-</blockquote>
-
-<para>
-<indexterm><primary>password backend</primary></indexterm>
-<indexterm><primary>guest</primary></indexterm>
-<indexterm><primary>unprivileged account names</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-In <link linkend="simplynice">this example</link>, the machine name is set to &example.server.samba;, and the
-workgroup is set to the name of the local workgroup (&example.workgroup;) so the machine will appear together
-with systems with which users are familiar. The only password backend required is the <quote>guest</quote>
-backend to allow default unprivileged account names to be used. As there is a WINS server on this network, we
-of course make use of it.
-</para>
-
-<para>
-A US Air Force Colonel was renowned for saying: <quote>Better is the enemy of good enough!</quote> There are often
-sound reasons for avoiding complexity as well as for avoiding a technically perfect solution. Unfortunately,
-many network administrators still need to learn the art of doing just enough to keep out of trouble.
-</para>
-
-</sect2>
-
-<sect2 id="SimplePrintServer">
-<title>Central Print Serving</title>
-
-<para>
-<indexterm><primary>simple print server</primary></indexterm>
-<indexterm><primary>tools</primary></indexterm>
-Configuration of a simple print server is easy if you have all the right tools on your system.
-</para>
-
-<orderedlist>
-<title> Assumptions</title>
- <listitem><para>
- The print server must require no administration.
- </para></listitem>
-
- <listitem><para>
- The print spooling and processing system on our print server will be CUPS.
- (Please refer to <link linkend="CUPS-printing">CUPS Printing Support</link>, for more information).
- </para></listitem>
-
- <listitem><para>
- The print server will service only network printers. The network administrator
- will correctly configure the CUPS environment to support the printers.
- </para></listitem>
-
- <listitem><para>
- All workstations will use only PostScript drivers. The printer driver
- of choice is the one shipped with the Windows OS for the Apple Color LaserWriter.
- </para></listitem>
-</orderedlist>
-
-<para>
-<indexterm><primary>print server</primary></indexterm>
-<indexterm><primary>/var/spool/samba</primary></indexterm>
-<indexterm><primary>anonymous</primary></indexterm>
-In this example our print server will spool all incoming print jobs to
-<filename>/var/spool/samba</filename> until the job is ready to be submitted by
-Samba to the CUPS print processor. Since all incoming connections will be as
-the anonymous (guest) user, two things will be required to enable anonymous printing.
-</para>
-
-<itemizedlist>
-<title>Enabling Anonymous Printing</title>
- <listitem><para>
-<indexterm><primary>guest account</primary></indexterm>
-<indexterm><primary>nobody</primary></indexterm>
-<indexterm><primary>testparm</primary></indexterm>
- The UNIX/Linux system must have a <command>guest</command> account.
- The default for this is usually the account <command>nobody</command>.
- To find the correct name to use for your version of Samba, do the
- following:
-<screen>
-&prompt;<userinput>testparm -s -v | grep "guest account"</userinput>
-</screen>
-<indexterm><primary>/etc/passwd</primary></indexterm>
- Make sure that this account exists in your system password
- database (<filename>/etc/passwd</filename>).
- </para>
-
- <para>
-<indexterm><primary>set a password</primary></indexterm>
-<indexterm><primary>lock password</primary></indexterm>
-<indexterm><primary>passwd</primary></indexterm>
- It is a good idea either to set a password on this account, or else to lock it
- from UNIX use. Assuming that the guest account is called <literal>pcguest</literal>,
- it can be locked by executing:
-<screen>
-&rootprompt; passwd -l pcguest
-</screen>
- The exact command may vary depending on your UNIX/Linux distribution.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>directory</primary></indexterm>
-<indexterm><primary>guest account</primary></indexterm>
-<indexterm><primary>available</primary></indexterm>
-<indexterm><primary>mkdir</primary></indexterm>
-<indexterm><primary>chown</primary></indexterm>
-<indexterm><primary>chmod</primary></indexterm>
- The directory into which Samba will spool the file must have write
- access for the guest account. The following commands will ensure that
- this directory is available for use:
-<screen>
-&rootprompt;<userinput>mkdir /var/spool/samba</userinput>
-&rootprompt;<userinput>chown nobody.nobody /var/spool/samba</userinput>
-&rootprompt;<userinput>chmod a+rwt /var/spool/samba</userinput>
-</screen>
- </para></listitem>
-</itemizedlist>
-
-<para>
-The contents of the &smb.conf; file is shown in <link linkend="AnonPtrSvr">the Anonymous Printing example</link>.
-</para>
-
-<example id="AnonPtrSvr">
-<title>&smb.conf; for Anonymous Printing</title>
-<smbconfblock>
-<smbconfcomment> Global parameters</smbconfcomment>
-<smbconfsection name="[global]"/>
-<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
-<smbconfoption name="netbios name">&example.server.samba;</smbconfoption>
-<smbconfoption name="security">SHARE</smbconfoption>
-<smbconfoption name="passdb backend">guest</smbconfoption>
-<smbconfoption name="printing">cups</smbconfoption>
-<smbconfoption name="printcap name">cups</smbconfoption>
-
-<smbconfsection name="[printers]"/>
-<smbconfoption name="comment">All Printers</smbconfoption>
-<smbconfoption name="path">/var/spool/samba</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-<smbconfoption name="printable">Yes</smbconfoption>
-<smbconfoption name="use client driver">Yes</smbconfoption>
-<smbconfoption name="browseable">No</smbconfoption>
-</smbconfblock>
-</example>
-
-
-<note><para>
-<indexterm><primary>MIME</primary><secondary>raw</secondary></indexterm>
-<indexterm><primary>raw printing</primary></indexterm>
-<indexterm><primary>/etc/mime.conv</primary></indexterm>
-<indexterm><primary>/etc/mime.types</primary></indexterm>
-<indexterm><primary>CUPS print filters</primary></indexterm>
-On CUPS-enabled systems there is a facility to pass raw data directly to the printer without intermediate
-processing via CUPS print filters. Where use of this mode of operation is desired, it is necessary to
-configure a raw printing device. It is also necessary to enable the raw mime handler in the
-<filename>/etc/mime.conv</filename> and <filename>/etc/mime.types</filename> files. Refer to <link
-linkend="CUPS-printing">CUPS Printing Support</link>, <link linkend="cups-raw">Explicitly Enable raw Printing
-for application/octet-stream</link>.
-</para></note>
-
-<para>
-<indexterm><primary>CUPS libarary API</primary></indexterm>
-<indexterm><primary>no printcap file</primary></indexterm>
-<indexterm><primary>PDF filter</primary></indexterm>
-<indexterm><primary>printcap name</primary></indexterm>
-The example in <link linkend="AnonPtrSvr">the Anonymous Printing example</link> uses CUPS for direct printing
-via the CUPS libarary API. This means that all printers will be exposed to Windows users without need to
-configure a printcap file. If there is necessity to expose only a sub-set of printers, or to define a special
-type of printer (for example, a PDF filter) the <parameter>printcap name = cups</parameter> can be replaced
-with the entry <parameter>printcap name = /etc/samba/myprintcap</parameter>. In this case the file specified
-should contain a list of the printer names that should be exposed to Windows network users.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-<indexterm><primary>greatest mistake</primary></indexterm>
-<indexterm><primary>configuration too complex</primary></indexterm>
-The greatest mistake so often made is to make a network configuration too complex.
-It pays to use the simplest solution that will meet the needs of the moment.
-</para>
-
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<chapter lang="en-US">
-<title>Samba Support</title>
-
-<para>
-<indexterm><primary>support</primary></indexterm>
-One of the most difficult to answer questions in the information technology industry is, <quote>What is
-support?</quote>. That question irritates some folks, as much as common answers may annoy others.
-</para>
-
-<para>
-<indexterm><primary>customers</primary></indexterm>
-The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to
-an Internet service provider who, instead of listening to the problem to find a solution, blandly replies:
-<quote>Oh, Linux? We do not support Linux!</quote>. It has happened to me, and similar situations happen
-through-out the IT industry. Answers like that are designed to inform us that there are some customers
-that a business just does not want to deal with, and well may we feel the anguish of the rejection that
-is dished out.
-</para>
-
-<para>
-One way to consider support is to view it as consisting of the right answer, in the right place,
-at the right time, no matter the situation. Support is all that it takes to take away pain, disruption,
-inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.
-</para>
-
-<para>
-<indexterm><primary>provided services</primary></indexterm>
-<indexterm><primary>services provided</primary></indexterm>
-<indexterm><primary>customer expected</primary></indexterm>
-One of the forces that has become a driving force for the adoption of open source software is the fact that
-many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or
-that have been found wanting for other reasons.
-</para>
-
-<para>
-<indexterm><primary>consumer expects</primary></indexterm>
-<indexterm><primary>problem resolution</primary></indexterm>
-In recognition of the need for needs satisfaction as the primary experience an information technology user or
-consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience
-in respect of problem resolution.
-</para>
-
-<para>
-<indexterm><primary>free support</primary></indexterm>
-<indexterm><primary>paid-for support</primary></indexterm>
-<indexterm><primary>commercial support</primary></indexterm>
-In the open source software arena there are two support options: free support and paid-for (commercial)
-support.
-</para>
-
- <sect1>
- <title>Free Support</title>
-
- <para>
-<indexterm><primary>user groups</primary></indexterm>
-<indexterm><primary>mailing lists</primary></indexterm>
-<indexterm><primary>interactive help</primary></indexterm>
-<indexterm><primary>help</primary></indexterm>
-<indexterm><primary>mutual assistance</primary></indexterm>
-<indexterm><primary>assistance</primary></indexterm>
- Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help
- facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user
- supported mutual assistance.
- </para>
-
- <para>
-<indexterm><primary>mailing list</primary></indexterm>
-<indexterm><primary>deployment</primary></indexterm>
-<indexterm><primary>subscription</primary></indexterm>
-<indexterm><primary>IRC</primary></indexterm>
-<indexterm><primary>project</primary></indexterm>
- The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments.
- Information regarding subscription to the Samba mailing list can be found on the Samba <ulink
- url="https://lists.samba.org/mailman/">web</ulink> site. The public mailing list that can be used to obtain
- free, user contributed, support is called the <literal>samba</literal> list. The email address for this list
- is at <literal>mail:samba@lists.samba.org</literal>. Information regarding the Samba IRC channels may be found on
- the Samba <ulink url="http://www.samba.org/samba.irc.html">IRC</ulink> web page.
- </para>
-
- <para>
-<indexterm><primary>free support</primary></indexterm>
-<indexterm><primary>qualified problem</primary></indexterm>
-<indexterm><primary>requesting payment</primary></indexterm>
-<indexterm><primary>professional support</primary></indexterm>
- As a general rule, it is considered poor net behavior to contact a Samba Team member directly
- for free support. Most active members of the Samba Team work exceptionally long hours to assist
- users who have demonstrated a qualified problem. Some team members may respond to direct email
- or telephone contact, with requests for assistance, by requesting payment. A few of the Samba
- Team members actually provide professional paid-for Samba support and it is therefore wise
- to show appropriate discretion and reservation in all direct contact.
- </para>
-
- <para>
-<indexterm><primary>bug report</primary></indexterm>
-<indexterm><primary>problem report</primary></indexterm>
-<indexterm><primary>code maintainer</primary></indexterm>
- When you stumble across a Samba bug, often the quickest way to get it resolved is by posting
- a bug <ulink url="https://bugzilla.samba.org/">report</ulink>. All such reports are mailed to
- the responsible code maintainer for action. The better the report, and the more serious it is,
- the sooner it will be dealt with. On the other hand, if the responsible person can not duplicate
- the reported bug it is likely to be rejected. It is up to you to provide sufficient information
- that will permit the problem to be reproduced.
- </para>
-
- <para>
-<indexterm><primary>purchase support</primary></indexterm>
- We all recognize that sometimes free support does not provide the answer that is sought within
- the time-frame required. At other times the problem is elusive and you may lack the experience
- necessary to isolate the problem and thus to resolve it. This is a situation where is may be
- prudent to purchase paid-for support.
- </para>
-
- </sect1>
-
- <sect1>
- <title>Commercial Support</title>
-
- <para>
- There are six basic support oriented services that are most commonly sought by Samba sites:
- </para>
-
- <itemizedlist>
- <listitem><para>Assistance with network design</para></listitem>
- <listitem><para>Staff Training</para></listitem>
- <listitem><para>Assistance with Samba network deployment and installation</para></listitem>
- <listitem><para>Priority telephone or email Samba configuration assistance</para></listitem>
- <listitem><para>Trouble-shooting and diagnostic assistance</para></listitem>
- <listitem><para>Provision of quality assured ready-to-install Samba binary packages</para></listitem>
- </itemizedlist>
-
- <para>
-<indexterm><primary>commercial support</primary></indexterm>
-<indexterm><primary>country of origin</primary></indexterm>
- Information regarding companies that provide professional Samba support can be obtained by performing a Google
- search, as well as by reference to the Samba <ulink
- url="http://www.samba.org/samba/support.html">Support</ulink> web page. Companies who notify the Samba Team
- that they provide commercial support are given a free listing that is sorted by the country of origin.
- Multiple listings are permitted, however no guarantee is offered. It is left to you to qualify a support
- provider and to satisfy yourself that both the company and its staff are able to deliver what is required of
- them.
- </para>
-
- <para>
-<indexterm><primary>commercial support</primary></indexterm>
- The policy within the Samba Team is to treat all commercial support providers equally and to show no
- preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else.
- You are encouraged to obtain the services needed from a company in your local area. The open source movement
- is pro-community; so do what you can to help a local business to prosper.
- </para>
-
- <para>
-<indexterm><primary>unsupported software</primary></indexterm>
- Open source software support can be found in any quality, at any price and in any place you can
- to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for
- suffering in the mistaken belief that Samba is unsupported software &smbmdash; it is supported.
- </para>
-
- </sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="tdb">
-
-<chapterinfo>
- &author.jht;
-
- <pubdate>May 28, 2008</pubdate>
-</chapterinfo>
-
-<title>Managing TDB Files</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
- <para>
-<indexterm><primary>tdb</primary></indexterm>
-<indexterm><primary>Trivial Database</primary></indexterm>
- Samba uses a lightweight database called Trivial Database (tdb) in which it stores persistent and transient data.
- Some tdb files can be disposed of before restarting Samba, but others are used to store information that is vital
- to Samba configuration and behavior. The following information is provided to help administrators who are seeking
- to better manage their Samba installations.
- </para>
-
- <para>
-<indexterm><primary>tdb</primary></indexterm>
-<indexterm><primary>corrupted</primary></indexterm>
-<indexterm><primary>backup</primary></indexterm>
-<indexterm><primary>restore</primary></indexterm>
- Those who package Samba for commercial distribution with operating systems and appliances would do well to take
- note that tdb files can get corrupted, and for this reason ought to be backed up regularly. An appropriate time
- is at system shutdown (backup) and startup (restore from backup).
- </para>
-
-<table frame="all" id="TOSH-TDB">
- <title>Samba's Trivial Database Files</title>
- <tgroup align="center" cols="2">
- <thead>
- <row><entry>File name</entry><entry>Preserve</entry><entry>Description</entry></row>
- </thead>
-
- <tbody>
- <row><entry>account_policy.tdb</entry><entry>Y</entry>
- <entry><para>NT account policy settings such as pw expiration, etc...</para></entry></row>
- <row><entry>brlock.tdb</entry><entry>N</entry>
- <entry><para>Byte range locks.</para></entry></row>
- <row><entry>browse.dat</entry><entry>N</entry>
- <entry><para>Browse lists - gets rebuilt automatically.</para></entry></row>
- <row><entry>connections.tdb</entry><entry>N</entry>
- <entry><para>Share connections. Used to enforce max connections, etc.</para></entry></row>
- <row><entry>gencache.tdb</entry><entry>N</entry>
- <entry><para>Generic caching database.</para></entry></row>
- <row><entry>group_mapping.tdb</entry><entry>Y</entry>
- <entry><para>Stores group mapping information. Not used when using LDAP backend.</para></entry></row>
- <row><entry> lang_en.tdb</entry><entry>Y</entry>
- <entry><para>Stores language encoding information.</para></entry></row>
- <row><entry>locking.tdb</entry><entry>N</entry>
- <entry><para>Stores share mode and oplock information.</para></entry></row>
- <row><entry>login_cache.tdb</entry><entry>N</entry>
- <entry><para>Keeps a log of bad pw attempts.</para></entry></row>
- <row><entry>messages.tdb</entry><entry>N</entry>
- <entry><para>Used to keep track of Samba internal messaging.</para></entry></row>
- <row><entry>netsamlogon_cache.tdb</entry><entry>Y</entry>
- <entry><para>
- Cache of user net_info_3 struct from <emphasis>net_samlogon()</emphasis>
- requests from domain member machines.
- </para></entry></row>
- <row><entry>ntdrivers.tdb</entry><entry>Y</entry>
- <entry><para>Stores installed printer driver information.</para></entry></row>
- <row><entry>ntforms.tdb</entry><entry>Y</entry>
- <entry><para>Stores installed printer forms information.</para></entry></row>
- <row><entry>ntprinters.tdb</entry><entry>Y</entry>
- <entry><para>Stores installed printers information.</para></entry></row>
- <row><entry>printing directory</entry><entry>Y</entry>
- <entry><para>Directory containing tdb per print queue of cached lpq output.</para></entry></row>
- <row><entry>registry.tdb</entry><entry>Y</entry>
- <entry><para>Windows registry skeleton (connect via regedit.exe).</para></entry></row>
- <row><entry>sessionid.tdb</entry><entry>N</entry>
- <entry><para>Session information to support <literal>utmp = yes</literal> capabilities.</para></entry></row>
- <row><entry>share_info.tdb</entry><entry>Y</entry>
- <entry><para>Stores share-level ACL configuration settings.
- Default ACL is <emphasis>Everyone - Full Control</emphasis>.
- </para></entry></row>
- <row><entry>unexpected.tdb</entry><entry>N</entry>
- <entry><para>
- Unexpected packet queue needed to support windows clients that respond on a
- different port that the originating reques.
- </para></entry></row>
- <row><entry>winbindd_cache.tdb</entry><entry>N</entry>
- <entry><para>Winbind's cache of user lists.</para></entry></row>
- <row><entry>winbindd_idmap.tdb</entry><entry>Y</entry>
- <entry><para>Winbind's local IDMAP database.</para></entry></row>
- <row><entry>wins.dat</entry><entry>N</entry>
- <entry><para>
- WINS database iused only when <parameter>wins support = yes</parameter>
- has been set. This gets rebuilt or updated at every restart.
- </para></entry></row>
- <row><entry>wins.tdb</entry><entry>Y</entry>
- <entry><para>
- The working permanent storage for all WINS data. This database is used only
- when <parameter>wins support = yes</parameter> has been set in the &smb.conf; file.
- Note: This retains all manually configured WINS entries. Manual setting can be done use the net utility.
- </para></entry></row>
- <row><entry>secrets.tdb</entry><entry>Y</entry>
- <entry><para>
- This tdb file stores internal settings such as the machine and the domain SID, secret passwords
- that are used with LDAP, the machine secret token, etc. This is an essential file that is stored
- in a secure area. Vendors locate this in various folders. Check <command>smbd -b</command> to
- find its location on your system.
- </para></entry></row>
- <row><entry>schannel_store.tdb</entry><entry>Y</entry>
- <entry><para>
- This stores secure channel access token information used with SMB signing.
- </para></entry></row>
- <row><entry>passdb.tdb</entry><entry>Y</entry>
- <entry><para>
- This stores the Samba SAM account information when using a tdbsam password backend.
- </para></entry></row>
- </tbody>
- </tgroup>
- </table>
-
-</sect1>
-
-<sect1>
-<title>Managing TDB Files</title>
-
- <para>
- The <command>tdbbackup</command> utility is a tool that may be used to backup samba tdb files.
- This tool may also be used to verify the integrity of the tdb files prior to Samba startup or
- during normal operation. If it finds file damage it will search for a prior backup the backup
- file from which the damaged tdb file will be restored. The <command>tdbbackup</command>
- utility can safely be run at any time. It was designed so that it can be used at any time to
- validate the integrity of tdb files, even during Samba operation.
- </para>
-
- <para>
- It is recommended to backup all tdb files as part of the Samba start-up scripts on a Samba
- server. The following command syntax can be used:
- </para>
-<screen>
-myserver# > cd /var/lib/samba
-myserver@ > tdbbackup *.tdb
-</screen>
- <para>
- The default extension is <filename>.bak</filename>. Any alternate extension can be specified
- by executing <literal>tdbbackup -s 'new_extension' *.tdb</literal> as part of your startup script.
- </para>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<chapter id="NetCommand">
-<chapterinfo>
- &author.jht;
- &author.vl;
- &author.gd;
- <pubdate>May 9, 2005</pubdate>
-</chapterinfo>
-
-<title>Remote and Local Management: The Net Command</title>
-
-<para>
-<indexterm><primary>net</primary></indexterm>
-<indexterm><primary>remote management</primary></indexterm>
-<indexterm><primary>command-line</primary></indexterm>
-<indexterm><primary>scripted control</primary></indexterm>
-The <command>net</command> command is one of the new features of Samba and is an attempt to provide a useful
-tool for the majority of remote management operations necessary for common tasks. The <command>net</command>
-tool is flexible by design and is intended for command-line use as well as for scripted control application.
-</para>
-
-<para>
-<indexterm><primary>net</primary></indexterm>
-<indexterm><primary>network administrator's toolbox</primary></indexterm>
-<indexterm><primary>smbgroupedit</primary></indexterm>
-<indexterm><primary>rpcclient</primary></indexterm>
-Originally introduced with the intent to mimic the Microsoft Windows command that has the same name, the
-<command>net</command> command has morphed into a very powerful instrument that has become an essential part
-of the Samba network administrator's toolbox. The Samba Team has introduced tools, such as
-<command>smbgroupedit</command> and <command>rpcclient</command>, from which really useful capabilities have
-been integrated into the <command>net</command>. The <command>smbgroupedit</command> command was absorbed
-entirely into the <command>net</command>, while only some features of the <command>rpcclient</command> command
-have been ported to it. Anyone who finds older references to these utilities and to the functionality they
-provided should look at the <command>net</command> command before searching elsewhere.
-</para>
-
-<para>
-A Samba administrator cannot afford to gloss over this chapter because to do so will almost certainly cause
-the infliction of self-induced pain, agony, and desperation. Be warned: this is an important chapter.
-</para>
-
- <sect1>
- <title>Overview</title>
-
- <para>
-<indexterm><primary>standalone</primary></indexterm>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>DMS</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
- The tasks that follow the installation of a Samba server, whether standalone or domain member, of a
- domain controller (PDC or BDC) begins with the need to create administrative rights. Of course, the
- creation of user and group accounts is essential for both a standalone server and a PDC.
- In the case of a BDC or a Domain Member server (DMS), domain user and group accounts are obtained from
- the central domain authentication backend.
- </para>
-
- <para>
-<indexterm><primary>server type</primary></indexterm>
-<indexterm><primary>local UNIX groups</primary></indexterm>
-<indexterm><primary>mapped</primary></indexterm>
-<indexterm><primary>domain global group</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>access rights</primary></indexterm>
-<indexterm><primary>net</primary></indexterm>
- Regardless of the type of server being installed, local UNIX groups must be mapped to the Windows
- networking domain global group accounts. Do you ask why? Because Samba always limits its access to
- the resources of the host server by way of traditional UNIX UID and GID controls. This means that local
- groups must be mapped to domain global groups so that domain users who are members of the domain
- global groups can be given access rights based on UIDs and GIDs local to the server that is hosting
- Samba. Such mappings are implemented using the <command>net</command> command.
- </para>
-
- <para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-<indexterm><primary>DMS</primary></indexterm>
-<indexterm><primary>security account</primary></indexterm>
-<indexterm><primary>domain authentication</primary></indexterm>
-<indexterm><primary>trust accounts</primary></indexterm>
-<indexterm><primary>net</primary></indexterm>
- UNIX systems that are hosting a Samba server that is running as a member (PDC, BDC, or DMS) must have
- a machine security account in the domain authentication database (or directory). The creation of such
- security (or trust) accounts is also handled using the <command>net</command> command.
- </para>
-
- <para>
-<indexterm><primary>interdomain trusts</primary></indexterm>
-<indexterm><primary>net</primary></indexterm>
-<indexterm><primary>administrative duties</primary></indexterm>
-<indexterm><primary>user management</primary></indexterm>
-<indexterm><primary>group management</primary></indexterm>
-<indexterm><primary>share management</primary></indexterm>
-<indexterm><primary>printer management</primary></indexterm>
-<indexterm><primary>printer migration</primary></indexterm>
-<indexterm><primary>SID management</primary></indexterm>
- The establishment of interdomain trusts is achieved using the <command>net</command> command also, as
- may a plethora of typical administrative duties such as user management, group management, share and
- printer management, file and printer migration, security identifier management, and so on.
- </para>
-
- <para>
-<indexterm><primary>net</primary></indexterm>
-<indexterm><primary>man pages</primary></indexterm>
- The overall picture should be clear now: the <command>net</command> command plays a central role
- on the Samba stage. This role will continue to be developed. The inclusion of this chapter is
- evidence of its importance, one that has grown in complexity to the point that it is no longer considered
- prudent to cover its use fully in the online UNIX man pages.
- </para>
-
- </sect1>
-
- <sect1>
- <title>Administrative Tasks and Methods</title>
-
- <para>
-<indexterm><primary>net</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>Distributed Computing Environment</primary><see>DCE</see></indexterm>
-<indexterm><primary>Remote Procedure Call</primary><see>RPC</see></indexterm>
- The basic operations of the <command>net</command> command are documented here. This documentation is not
- exhaustive, and thus it is incomplete. Since the primary focus is on migration from Windows servers to a Samba
- server, the emphasis is on the use of the Distributed Computing Environment Remote Procedure Call (DCE RPC)
- mode of operation. When used against a server that is a member of an Active Directory domain, it is preferable
- (and often necessary) to use ADS mode operations. The <command>net</command> command supports both, but not
- for every operation. For most operations, if the mode is not specified, <command>net</command> will
- automatically fall back via the <constant>ads</constant>, <constant>rpc</constant>, and
- <constant>rap</constant> modes. Please refer to the man page for a more comprehensive overview of the
- capabilities of this utility.
- </para>
-
- </sect1>
-
- <sect1>
- <title>UNIX and Windows Group Management</title>
-
- <para>
-<indexterm><primary>Active Directory</primary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary></indexterm>
-<indexterm><primary>net</primary><secondary>ads</secondary></indexterm>
-<indexterm><primary>net</primary><secondary>rap</secondary></indexterm>
-<indexterm><primary>RAP</primary></indexterm>
- As stated, the focus in most of this chapter is on use of the <command>net rpc</command> family of
- operations that are supported by Samba. Most of them are supported by the <command>net ads</command>
- mode when used in connection with Active Directory. The <command>net rap</command> operating mode is
- also supported for some of these operations. RAP protocols are used by IBM OS/2 and by several
- earlier SMB servers.
- </para>
-
- <para>
-<indexterm><primary>net</primary></indexterm>
-<indexterm><primary>user management</primary></indexterm>
-<indexterm><primary>group management</primary></indexterm>
- Samba's <command>net</command> tool implements sufficient capability to permit all common administrative
- tasks to be completed from the command line. In this section each of the essential user and group management
- facilities are explored.
- </para>
-
- <para>
-<indexterm><primary>groups</primary></indexterm>
-<indexterm><primary>domain</primary><secondary>groups</secondary></indexterm>
-<indexterm><primary>local</primary><secondary>groups</secondary></indexterm>
-<indexterm><primary>domain user accounts</primary></indexterm>
- Samba recognizes two types of groups: <emphasis>domain groups</emphasis> and <emphasis>local
- groups</emphasis>. Domain groups can contain (have as members) only domain user accounts. Local groups
- can contain local users, domain users, and domain groups as members.
- </para>
-
- <para>
- The purpose of a local group is to permit file permission to be set for a group account that, like the
- usual UNIX/Linux group, is persistent across redeployment of a Windows file server.
- </para>
-
- <sect2>
- <title>Adding, Renaming, or Deletion of Group Accounts</title>
-
- <para>
- Samba provides file and print services to Windows clients. The file system resources it makes available
- to the Windows environment must, of necessity, be provided in a manner that is compatible with the
- Windows networking environment. UNIX groups are created and deleted as required to serve operational
- needs in the UNIX operating system and its file systems.
- </para>
-
- <para>
- In order to make available to the Windows environment, Samba has a facility by which UNIX groups can
- be mapped to a logical entity, called a Windows (or domain) group. Samba supports two types of Windows
- groups, local and global. Global groups can contain as members, global users. This membership is
- affected in the normal UNIX manner, but adding UNIX users to UNIX groups. Windows user accounts consist
- of a mapping between a user SambaSAMAccount (logical entity) and a UNIX user account. Therefore,
- a UNIX user is mapped to a Windows user (i.e., is given a Windows user account and password) and the
- UNIX groups to which that user belongs, is mapped to a Windows group account. The result is that in
- the Windows account environment that user is also a member of the Windows group account by virtue
- of UNIX group memberships.
- </para>
-
- <para>
- The following sub-sections that deal with management of Windows groups demonstrates the relationship
- between the UNIX group account and its members to the respective Windows group accounts. It goes on to
- show how UNIX group members automatically pass-through to Windows group membership as soon as a logical
- mapping has been created.
- </para>
-
- <sect3>
- <title>Adding or Creating a New Group</title>
-
- <para>
- Before attempting to add a Windows group account, the currently available groups can be listed as shown
- here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group</tertiary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group list</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc group list -Uroot%not24get
-Password:
-Domain Admins
-Domain Users
-Domain Guests
-Print Operators
-Backup Operators
-Replicator
-Domain Computers
-Engineers
-</screen>
- </para>
-
-<?latex \newpage ?>
- <para>
- A Windows group account called <quote>SupportEngrs</quote> can be added by executing the following
-command:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group add</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc group add "SupportEngrs" -Uroot%not24get
-</screen>
- The addition will result in immediate availability of the new group account as validated by executing
-this command:
-<screen>
-&rootprompt; net rpc group list -Uroot%not24get
-Password:
-Domain Admins
-Domain Users
-Domain Guests
-Print Operators
-Backup Operators
-Replicator
-Domain Computers
-Engineers
-SupportEngrs
-</screen>
- </para>
-
- <para>
-<indexterm><primary>POSIX</primary></indexterm>
-<indexterm><primary>smbldap-groupadd</primary></indexterm>
-<indexterm><primary>getent</primary></indexterm>
- The following demonstrates that the POSIX (UNIX/Linux system account) group has been created by calling
- the <smbconfoption name="add group script">/opt/IDEALX/sbin/smbldap-groupadd -p "%g"</smbconfoption> interface
- script:
-<screen>
-&rootprompt; getent group
-...
-Domain Admins:x:512:root
-Domain Users:x:513:jht,lct,ajt,met
-Domain Guests:x:514:
-Print Operators:x:550:
-Backup Operators:x:551:
-Replicator:x:552:
-Domain Computers:x:553:
-Engineers:x:1002:jht
-SupportEngrs:x:1003:
-</screen>
- The following demonstrates that the use of the <command>net</command> command to add a group account
-results in immediate mapping of the POSIX group that has been created to the Windows group account as shown
-here:
-<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>list</tertiary></indexterm>
-<screen>
-&rootprompt; net groupmap list
-Domain Admins (S-1-5-21-72630-4128915-11681869-512) -> Domain Admins
-Domain Users (S-1-5-21-72630-4128915-11681869-513) -> Domain Users
-Domain Guests (S-1-5-21-72630-4128915-11681869-514) -> Domain Guests
-Print Operators (S-1-5-21-72630-4128915-11681869-550) -> Print Operators
-Backup Operators (S-1-5-21-72630-4128915-11681869-551) -> Backup Operators
-Replicator (S-1-5-21-72630-4128915-11681869-552) -> Replicator
-Domain Computers (S-1-5-21-72630-4128915-11681869-553) -> Domain Computers
-Engineers (S-1-5-21-72630-4128915-11681869-3005) -> Engineers
-SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -> SupportEngrs
-</screen>
- </para>
-
- </sect3>
-
- <sect3>
- <title>Mapping Windows Groups to UNIX Groups</title>
-
- <para>
-<indexterm><primary>mapped</primary></indexterm>
-<indexterm><primary>Windows groups</primary></indexterm>
-<indexterm><primary>system groups</primary></indexterm>
-<indexterm><primary>access controls</primary></indexterm>
- Windows groups must be mapped to UNIX system (POSIX) groups so that file system access controls
- can be asserted in a manner that is consistent with the methods appropriate to the operating
- system that is hosting the Samba server.
- </para>
-
- <para>
-<indexterm><primary>access controls</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>locally known UID</primary></indexterm>
- All file system (file and directory) access controls, within the file system of a UNIX/Linux server that is
- hosting a Samba server, are implemented using a UID/GID identity tuple. Samba does not in any way override
- or replace UNIX file system semantics. Thus it is necessary that all Windows networking operations that
- access the file system provide a mechanism that maps a Windows user to a particular UNIX/Linux group
- account. The user account must also map to a locally known UID. Note that the <command>net</command>
- command does not call any RPC-functions here but directly accesses the passdb.
- </para>
-
- <para>
-<indexterm><primary>default mappings</primary></indexterm>
-<indexterm><primary>Domain Admins</primary></indexterm>
-<indexterm><primary>Domain Users</primary></indexterm>
-<indexterm><primary>Domain Guests</primary></indexterm>
-<indexterm><primary>Windows group</primary></indexterm>
-<indexterm><primary>UNIX group</primary></indexterm>
-<indexterm><primary>mapping</primary></indexterm>
- Samba depends on default mappings for the <constant>Domain Admins, Domain Users</constant>, and
- <constant>Domain Guests</constant> global groups. Additional groups may be added as shown in the
- examples just given. There are times when it is necessary to map an existing UNIX group account
- to a Windows group. This operation, in effect, creates a Windows group account as a consequence
- of creation of the mapping.
- </para>
-
- <para>
-<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>modify</tertiary></indexterm>
-<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>add</tertiary></indexterm>
-<indexterm><primary>net</primary><secondary>groupmap</secondary><tertiary>delete</tertiary></indexterm>
- The operations that are permitted include: <constant>add</constant>, <constant>modify</constant>,
- and <constant>delete</constant>. An example of each operation is shown here.
- </para>
-
- <note><para>
- Commencing with Samba-3.0.23 Windows Domain Groups must be explicitly created. By default, all
- UNIX groups are exposed to Windows networking as Windows local groups.
- </para></note>
-
- <para>
- An existing UNIX group may be mapped to an existing Windows group by this example:
-<screen>
-&rootprompt; net groupmap modify ntgroup="Domain Users" unixgroup=users
-</screen>
- An existing UNIX group may be mapped to a new Windows group as shown here:
-<screen>
-&rootprompt; net groupmap add ntgroup="EliteEngrs" unixgroup=Engineers type=d
-</screen>
- Supported mapping types are 'd' (domain global) and 'l' (domain local).
- A Windows group may be deleted, and then a new Windows group can be mapped to the UNIX group by
- executing these commands:
-<screen>
-&rootprompt; net groupmap delete ntgroup=Engineers
-&rootprompt; net groupmap add ntgroup=EngineDrivers unixgroup=Engineers type=d
-</screen>
- The deletion and addition operations affected only the logical entities known as Windows groups, or domain
- groups. These operations are inert to UNIX system groups, meaning that they neither delete nor create UNIX
- system groups. The mapping of a UNIX group to a Windows group makes the UNIX group available as Windows
- groups so that files and folders on domain member clients (workstations and servers) can be given
- domain-wide access controls for domain users and groups.
- </para>
-
- <para>
- Two types of Windows groups can be created: <constant>domain (global)</constant> and <constant>local</constant>.
- In the previous examples the Windows groups created were of type <constant>domain</constant> or global. The
- following command will create a Windows group of type <constant>local</constant>.
-<screen>
-&rootprompt; net groupmap add ntgroup=Pixies unixgroup=pixies type=l
-</screen>
- Supported mapping types are 'd' (domain global) and 'l' (domain local), a domain local group in Samba is
- treated as local to the individual Samba server. Local groups can be used with Samba to enable multiple
- nested group support.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Deleting a Group Account</title>
-
- <para>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group delete</tertiary></indexterm>
- A group account may be deleted by executing the following command:
-<screen>
-&rootprompt; net rpc group delete SupportEngineers -Uroot%not24get
-</screen>
- </para>
-
- <para>
- Validation of the deletion is advisable. The same commands may be executed as shown above.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Rename Group Accounts</title>
-
- <note><para>
- This command is not documented in the man pages; it is implemented in the source code, but it does not
- work at this time. The example given documents, from the source code, how it should work. Watch the
- release notes of a future release to see when this may have been fixed.
- </para></note>
-
- <para>
- Sometimes it is necessary to rename a group account. Good administrators know how painful some managers'
- demands can be if this simple request is ignored. The following command demonstrates how the Windows group
- <quote>SupportEngrs</quote> can be renamed to <quote>CustomerSupport</quote>:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group rename</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc group rename SupportEngrs \
- CustomerSupport -Uroot%not24get
-</screen>
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2 id="grpmemshipchg">
- <title>Manipulating Group Memberships</title>
-
- <para>
- Three operations can be performed regarding group membership. It is possible to (1) add Windows users
- to a Windows group, to (2) delete Windows users from Windows groups, and to (3) list the Windows users that are
- members of a Windows group.
- </para>
-
- <para>
- To avoid confusion, it makes sense to check group membership before attempting to make any changes.
- The <command>getent group</command> will list UNIX/Linux group membership. UNIX/Linux group members are
- seen also as members of a Windows group that has been mapped using the <command>net groupmap</command>
- command (see <link linkend="groupmapping"/>). The following list of UNIX/Linux group membership shows
- that the user <constant>ajt</constant> is a member of the UNIX/Linux group <constant>Engineers</constant>.
-<screen>
-&rootprompt; getent group
-...
-Domain Admins:x:512:root
-Domain Users:x:513:jht,lct,ajt,met,vlendecke
-Domain Guests:x:514:
-Print Operators:x:550:
-Backup Operators:x:551:
-Replicator:x:552:
-Domain Computers:x:553:
-Engineers:x:1000:jht,ajt
-</screen>
- The UNIX/Linux groups have been mapped to Windows groups, as is shown here:
-<screen>
-&rootprompt; net groupmap list
-Domain Admins (S-1-5-21-72630-412605-116429-512) -> Domain Admins
-Domain Users (S-1-5-21-72630-412605-116429-513) -> Domain Users
-Domain Guests (S-1-5-21-72630-412605-116429-514) -> Domain Guests
-Print Operators (S-1-5-21-72630-412605-116429-550) -> Print Operators
-Backup Operators (S-1-5-21-72630-412605-116429-551) -> Backup Operators
-Replicator (S-1-5-21-72630-412605-116429-552) -> Replicator
-Domain Computers (S-1-5-21-72630-412605-116429-553) -> Domain Computers
-Engineers (S-1-5-21-72630-412605-116429-3001) -> Engineers
-</screen>
- </para>
-
- <para>
- Given that the user <constant>ajt</constant> is already a member of the UNIX/Linux group and, via the
- group mapping, a member of the Windows group, an attempt to add this account again should fail. This is
- demonstrated here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group addmem</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc group addmem "MIDEARTH\Engineers" ajt -Uroot%not24get
-Could not add ajt to MIDEARTH\Engineers: NT_STATUS_MEMBER_IN_GROUP
-</screen>
- This shows that the group mapping between UNIX/Linux groups and Windows groups is effective and
- transparent.
- </para>
-
- <para>
- To permit the user <constant>ajt</constant> to be added using the <command>net rpc group</command> utility,
- this account must first be removed. The removal and confirmation of its effect is shown here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group delmem</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc group delmem "MIDEARTH\Engineers" ajt -Uroot%not24get
-&rootprompt; getent group Engineers
-Engineers:x:1000:jht
-&rootprompt; net rpc group members Engineers -Uroot%not24get
-MIDEARTH\jht
-</screen>
- In this example both at the UNIX/Linux system level, the group no longer has the <constant>ajt</constant>
- as a member. The above also shows this to be the case for Windows group membership.
- </para>
-
- <para>
- The account is now added again, using the <command>net rpc group</command> utility:
-<screen>
-&rootprompt; net rpc group addmem "MIDEARTH\Engineers" ajt -Uroot%not24get
-&rootprompt; getent group Engineers
-Engineers:x:1000:jht,ajt
-&rootprompt; net rpc group members Engineers -Uroot%not24get
-MIDEARTH\jht
-MIDEARTH\ajt
-</screen>
- </para>
-
- <para>
- In this example the members of the Windows <constant>Domain Users</constant> account are validated using
- the <command>net rpc group</command> utility. Note the this contents of the UNIX/Linux group was shown
- four paragraphs earlier. The Windows (domain) group membership is shown here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group members</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc group members "Domain Users" -Uroot%not24get
-MIDEARTH\jht
-MIDEARTH\lct
-MIDEARTH\ajt
-MIDEARTH\met
-MIDEARTH\vlendecke
-</screen>
- This express example shows that Windows group names are treated by Samba (as with
- MS Windows) in a case-insensitive manner:
-<screen>
-&rootprompt; net rpc group members "DomAiN USerS" -Uroot%not24get
-MIDEARTH\jht
-MIDEARTH\lct
-MIDEARTH\ajt
-MIDEARTH\met
-MIDEARTH\vlendecke
-</screen>
- </para>
-
- <note><para>
- An attempt to specify the group name as <constant>MIDEARTH\Domain Users</constant> in place of
- just simply <constant>Domain Users</constant> will fail. The default behavior of the net rpc group
- is to direct the command at the local machine. The Windows group is treated as being local to the machine.
- If it is necessary to query another machine, its name can be specified using the <constant>-S
- servername</constant> parameter to the <command>net</command> command.
- </para></note>
-
- </sect2>
-
- <sect2 id="nestedgrpmgmgt">
- <title>Nested Group Support</title>
-
- <para>
- It is possible in Windows (and now in Samba also) to create a local group that has members (contains),
- domain users, and domain global groups. Creation of the local group <constant>demo</constant> is
- achieved by executing:
-<screen>
-&rootprompt; net rpc group add demo -L -S MORDON -Uroot%not24get
-</screen>
- The -L switch means create a local group. Use the -S argument to direct the operation to a particular
- server. The parameters to the -U argument should be for a user who has appropriate administrative right
- and privileges on the machine.
- </para>
-
- <para>
- Addition and removal of group members can be achieved using the <constant>addmem</constant> and
- <constant>delmem</constant> subcommands of <command>net rpc group</command> command. For example,
- addition of <quote>DOM\Domain Users</quote> to the local group <constant>demo</constant> would be
- done by executing:
-<screen>
-&rootprompt; net rpc group addmem demo "DOM\Domain Users" -Uroot%not24get
-</screen>
- </para>
-
- <para>
- The members of a nested group can be listed by executing the following:
-<screen>
-&rootprompt; net rpc group members demo -Uroot%not24get
-DOM\Domain Users
-DOM\Engineers
-DOM\jamesf
-DOM\jht
-</screen>
- </para>
-
- <para>
- Nested group members can be removed (deleted) as shown here:
-<screen>
-&rootprompt; net rpc group delmem demo "DOM\jht" -Uroot%not24get
-</screen>
- </para>
-
- <sect3>
- <title>Managing Nest Groups on Workstations from the Samba Server</title>
-
- <para>
- Windows network administrators often ask on the Samba mailing list how it is possible to grant everyone
- administrative rights on their own workstation. This is of course a very bad practice, but commonly done
- to avoid user complaints. Here is how it can be done remotely from a Samba PDC or BDC:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group addmem</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc group addmem "Administrators" "Domain Users" \
- -S WINPC032 -Uadministrator%secret
-</screen>
- </para>
-
- <para>
- This can be scripted, and can therefore be performed as a user logs onto the domain from a Windows
- workstation. Here is a simple example that shows how this can be done.
- </para>
-
- <procedure>
- <title>Automating User Addition to the Workstation Power Users Group</title>
-
- <step><para>
- Create the script shown in <link linkend="autopoweruserscript"></link> and locate it in
- the directory <filename>/etc/samba/scripts</filename>, named as <filename>autopoweruser.sh</filename>.
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>group addmem</tertiary></indexterm>
-<indexterm><primary>autopoweruser.sh</primary></indexterm>
-<indexterm><primary>/etc/samba/scripts</primary></indexterm>
- </para></step>
-
-<example id="autopoweruserscript">
-<title>Script to Auto-add Domain Users to Workstation Power Users Group</title>
-<screen>
-#!/bin/bash
-
-/usr/bin/net rpc group addmem "Power Users" "DOMAIN_NAME\$1" \
- -UAdministrator%secret -S $2
-
-exit 0
-</screen>
-</example>
-
- <step><para>
- Set the permissions on this script to permit it to be executed as part of the logon process:
-<screen>
-&rootprompt; chown root:root /etc/samba/autopoweruser.sh
-&rootprompt; chmod 755 /etc/samba/autopoweruser.sh
-</screen>
- </para></step>
-
- <step><para>
- Modify the &smb.conf; file so the <literal>NETLOGON</literal> stanza contains the parameters
- shown in <link linkend="magicnetlogon">the Netlogon Example smb.conf file</link> as shown.
- </para></step>
-
-<example id="magicnetlogon">
-<title>A Magic Netlogon Share</title>
-<smbconfblock>
-<smbconfsection name="[netlogon]"/>
-<smbconfoption name="comment">Netlogon Share</smbconfoption>
-<smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption>
-<smbconfoption name="root preexec">/etc/samba/scripts/autopoweruser.sh %U %m</smbconfoption>
-<smbconfoption name="read only">Yes</smbconfoption>
-<smbconfoption name="guest ok">Yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <step><para>
- Ensure that every Windows workstation Administrator account has the same password that you
- have used in the script shown in <link linkend="magicnetlogon">the Netlogon Example smb.conf
- file</link>
- </para></step>
-
-</procedure>
-
- <para>
- This script will be executed every time a user logs on to the network. Therefore every user will
- have local Windows workstation management rights. This could of course be assigned using a group,
- in which case there is little justification for the use of this procedure. The key justification
- for the use of this method is that it will guarantee that all users have appropriate rights on
- the workstation.
- </para>
-
- </sect3>
-
- </sect2>
-
- </sect1>
-
- <sect1>
- <title>UNIX and Windows User Management</title>
-
- <para>
-<indexterm><primary>user account</primary></indexterm>
-<indexterm><primary>UNIX/Linux user account</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>POSIX account</primary></indexterm>
-<indexterm><primary>range</primary></indexterm>
-<indexterm><primary>Windows user accounts</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>account information</primary></indexterm>
- Every Windows network user account must be translated to a UNIX/Linux user account. In actual fact,
- the only account information the UNIX/Linux Samba server needs is a UID. The UID is available either
- from a system (POSIX) account or from a pool (range) of UID numbers that is set aside for the purpose
- of being allocated for use by Windows user accounts. In the case of the UID pool, the UID for a
- particular user will be allocated by <command>winbindd</command>.
- </para>
-
- <para>
- Although this is not the appropriate place to discuss the <smbconfoption name="username map"/> facility,
- this interface is an important method of mapping a Windows user account to a UNIX account that has a
- different name. Refer to the man page for the &smb.conf; file for more information regarding this
- facility. User name mappings cannot be managed using the <command>net</command> utility.
- </para>
-
- <sect2 id="sbeuseraddn">
- <title>Adding User Accounts</title>
-
- <para>
- The syntax for adding a user account via the <command>net</command> (according to the man page) is shown
- here:
-<screen>
-net [<method>] user ADD <name> [-c container] [-F user flags] \
- [misc. options] [targets]
-</screen>
- The user account password may be set using this syntax:
-<screen>
-net rpc password <username> [<password>] -Uadmin_username%admin_pass
-</screen>
- </para>
-
- <para>
- The following demonstrates the addition of an account to the server <constant>FRODO</constant>:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user add</tertiary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user password</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc user add jacko -S FRODO -Uroot%not24get
-Added user jacko
-</screen>
- The account password can be set with the following methods (all show the same operation):
-<screen>
-&rootprompt; net rpc password jacko f4sth0rse -S FRODO -Uroot%not24get
-&rootprompt; net rpc user password jacko f4sth0rse \
- -S FRODO -Uroot%not24get
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Deletion of User Accounts</title>
-
- <para>
- Deletion of a user account can be done using the following syntax:
-<screen>
-net [<method>] user DELETE <name> [misc. options] [targets]
-</screen>
- The following command will delete the user account <constant>jacko</constant>:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user delete</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc user delete jacko -Uroot%not24get
-Deleted user account
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Managing User Accounts</title>
-
- <para>
- Two basic user account operations are routinely used: change of password and querying which groups a user
- is a member of. The change of password operation is shown in <link linkend="sbeuseraddn"/>.
- </para>
-
- <para>
- The ability to query Windows group membership can be essential. Here is how a remote server may be
- interrogated to find which groups a user is a member of:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user info</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc user info jacko -S SAURON -Uroot%not24get
-net rpc user info jacko -S SAURON -Uroot%not24get
-Domain Users
-Domain Admins
-Engineers
-TorridGroup
-BOP Shop
-Emergency Services
-</screen>
- </para>
-
- <para>
- It is also possible to rename user accounts:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user rename</tertiary></indexterm>oldusername newusername
- Note that this operation does not yet work against Samba Servers. It is, however, possible to rename useraccounts on
- Windows Servers.
-
- </para>
-
- </sect2>
-
- <sect2>
- <title>User Mapping</title>
-
- <para>
-<indexterm><primary>logon name</primary></indexterm>
-<indexterm><primary>/etc/samba/smbusers</primary></indexterm>
-<indexterm><primary>username map</primary></indexterm>
- In some situations it is unavoidable that a user's Windows logon name will differ from the login ID
- that user has on the Samba server. It is possible to create a special file on the Samba server that
- will permit the Windows user name to be mapped to a different UNIX/Linux user name. The &smb.conf;
- file must also be amended so that the <constant>[global]</constant> stanza contains the parameter:
-<screen>
-username map = /etc/samba/smbusers
-</screen>
- The content of the <filename>/etc/samba/smbusers</filename> file is shown here:
-<screen>
-parsonsw: "William Parsons"
-marygee: geeringm
-</screen>
- In this example the Windows user account <quote>William Parsons</quote> will be mapped to the UNIX user
- <constant>parsonsw</constant>, and the Windows user account <quote>geeringm</quote> will be mapped to the
- UNIX user <constant>marygee</constant>.
- </para>
-
- </sect2>
-
- </sect1>
-
- <sect1>
- <title>Administering User Rights and Privileges</title>
-
- <para>
-<indexterm><primary>credentials</primary></indexterm>
-<indexterm><primary>manage printers</primary></indexterm>
-<indexterm><primary>manage shares</primary></indexterm>
-<indexterm><primary>manage groups</primary></indexterm>
-<indexterm><primary>manage users</primary></indexterm>
- With all versions of Samba earlier than 3.0.11 the only account on a Samba server that could
- manage users, groups, shares, printers, and such was the <constant>root</constant> account. This caused
- problems for some users and was a frequent source of scorn over the necessity to hand out the
- credentials for the most security-sensitive account on a UNIX/Linux system.
- </para>
-
- <para>
-<indexterm><primary>delegate administrative privileges</primary></indexterm>
-<indexterm><primary>normal user</primary></indexterm>
-<indexterm><primary>rights and privilege</primary></indexterm>
-<indexterm><primary>privilege management</primary></indexterm>
-<indexterm><primary>groups of users</primary></indexterm>
- New to Samba version 3.0.11 is the ability to delegate administrative privileges as necessary to either
- a normal user or to groups of users. The significance of the administrative privileges is documented
- in <link linkend="rights"/>. Examples of use of the <command>net</command> for user rights and privilege
- management is appropriate to this chapter.
- </para>
-
- <note><para>
- When user rights and privileges are correctly set, there is no longer a need for a Windows
- network account for the <constant>root</constant> user (nor for any synonym of it) with a UNIX UID=0.
- Initial user rights and privileges can be assigned by any account that is a member of the <constant>
- Domain Admins</constant> group. Rights can be assigned to user as well as group accounts.
- </para></note>
-
- <para>
- By default, no privileges and rights are assigned. This is demonstrated by executing the command
- shown here:
-<screen>
-&rootprompt; net rpc rights list accounts -U root%not24get
-BUILTIN\Print Operators
-No privileges assigned
-
-BUILTIN\Account Operators
-No privileges assigned
-
-BUILTIN\Backup Operators
-No privileges assigned
-
-BUILTIN\Server Operators
-No privileges assigned
-
-BUILTIN\Administrators
-No privileges assigned
-
-Everyone
-No privileges assigned
-</screen>
- </para>
-
- <para>
- The <command>net</command> command can be used to obtain the currently supported capabilities for rights
- and privileges using this method:
-<indexterm><primary>SeMachineAccountPrivilege</primary></indexterm>
-<indexterm><primary>SePrintOperatorPrivilege</primary></indexterm>
-<indexterm><primary>SeAddUsersPrivilege</primary></indexterm>
-<indexterm><primary>SeRemoteShutdownPrivilege</primary></indexterm>
-<indexterm><primary>SeDiskOperatorPrivilege</primary></indexterm>
-<indexterm><primary>SeBackupPrivilege</primary></indexterm>
-<indexterm><primary>SeRestorePrivilege</primary></indexterm>
-<indexterm><primary>SeTakeOwnershipPrivilege</primary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights list</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc rights list -U root%not24get
- SeMachineAccountPrivilege Add machines to domain
- SePrintOperatorPrivilege Manage printers
- SeAddUsersPrivilege Add users and groups to the domain
- SeRemoteShutdownPrivilege Force shutdown from a remote system
- SeDiskOperatorPrivilege Manage disk shares
- SeBackupPrivilege Back up files and directories
- SeRestorePrivilege Restore files and directories
- SeTakeOwnershipPrivilege Take ownership of files or other objects
-</screen>
- Machine account privilege is necessary to permit a Windows NT4 or later network client to be added to the
- domain. The disk operator privilege is necessary to permit the user to manage share ACLs and file and
- directory ACLs for objects not owned by the user.
- </para>
-
- <para>
- In this example, all rights are assigned to the <constant>Domain Admins</constant> group. This is a good
- idea since members of this group are generally expected to be all-powerful. This assignment makes that
- the reality:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights grant</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc rights grant "MIDEARTH\Domain Admins" \
- SeMachineAccountPrivilege SePrintOperatorPrivilege \
- SeAddUsersPrivilege SeRemoteShutdownPrivilege \
- SeDiskOperatorPrivilege -U root%not24get
-Successfully granted rights.
-</screen>
- Next, the domain user <constant>jht</constant> is given the privileges needed for day-to-day
- administration:
-<screen>
-&rootprompt; net rpc rights grant "MIDEARTH\jht" \
- SeMachineAccountPrivilege SePrintOperatorPrivilege \
- SeAddUsersPrivilege SeDiskOperatorPrivilege \
- -U root%not24get
-Successfully granted rights.
-</screen>
- </para>
-
- <para>
- The following step permits validation of the changes just made:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>rights list accounts</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc rights list accounts -U root%not24get
-MIDEARTH\jht
-SeMachineAccountPrivilege
-SePrintOperatorPrivilege
-SeAddUsersPrivilege
-SeDiskOperatorPrivilege
-
-BUILTIN\Print Operators
-No privileges assigned
-
-BUILTIN\Account Operators
-No privileges assigned
-
-BUILTIN\Backup Operators
-No privileges assigned
-
-BUILTIN\Server Operators
-No privileges assigned
-
-BUILTIN\Administrators
-No privileges assigned
-
-Everyone
-No privileges assigned
-
-MIDEARTH\Domain Admins
-SeMachineAccountPrivilege
-SePrintOperatorPrivilege
-SeAddUsersPrivilege
-SeRemoteShutdownPrivilege
-SeDiskOperatorPrivilege
-</screen>
- </para>
-
- </sect1>
-
- <sect1>
- <title>Managing Trust Relationships</title>
-
- <para>
- There are essentially two types of trust relationships: the first is between domain controllers and domain
- member machines (network clients), the second is between domains (called interdomain trusts). All
- Samba servers that participate in domain security require a domain membership trust account, as do like
- Windows NT/200x/XP workstations.
- </para>
-
- <sect2>
- <title>Machine Trust Accounts</title>
-
- <para>
- The net command looks in the &smb.conf; file to obtain its own configuration settings. Thus, the following
- command 'knows' which domain to join from the &smb.conf; file.
- </para>
-
- <para>
- A Samba server domain trust account can be validated as shown in this example:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>testjoin</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc testjoin
-Join to 'MIDEARTH' is OK
-</screen>
- Where there is no domain membership account, or when the account credentials are not valid, the following
- results will be observed:
-<screen>
-net rpc testjoin -S DOLPHIN
-Join to domain 'WORLDOCEAN' is not valid
-</screen>
- </para>
-
- <para>
- The equivalent command for joining a Samba server to a Windows ADS domain is shown here:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>testjoin</tertiary></indexterm>
-<screen>
-&rootprompt; net ads testjoin
-Using short domain name -- TAKEAWAY
-Joined 'LEMONADE' to realm 'TAKEAWAY.BIZ'
-</screen>
- In the event that the ADS trust was not established, or is broken for one reason or another, the following
- error message may be obtained:
-<screen>
-&rootprompt; net ads testjoin -UAdministrator%secret
-Join to domain is not valid
-</screen>
- </para>
-
- <para>
- The following demonstrates the process of creating a machine trust account in the target domain for the
- Samba server from which the command is executed:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc join -S FRODO -Uroot%not24get
-Joined domain MIDEARTH.
-</screen>
- The joining of a Samba server to a Samba domain results in the creation of a machine account. An example
- of this is shown here:
-<screen>
-&rootprompt; pdbedit -Lw merlin\$
-merlin$:1009:9B4489D6B90461FD6A3EC3AB96147E16:\
-176D8C554E99914BDF3407DEA2231D80:[S ]:LCT-42891919:
-</screen>
- The S in the square brackets means this is a server (PDC/BDC) account. The domain join can be cast to join
- purely as a workstation, in which case the S is replaced with a W (indicating a workstation account). The
- following command can be used to affect this:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join member</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc join member -S FRODO -Uroot%not24get
-Joined domain MIDEARTH.
-</screen>
- Note that the command-line parameter <constant>member</constant> makes this join specific. By default
- the type is deduced from the &smb.conf; file configuration. To specifically join as a PDC or BDC, the
- command-line parameter will be <constant>[PDC | BDC]</constant>. For example:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join bdc</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc join bdc -S FRODO -Uroot%not24get
-Joined domain MIDEARTH.
-</screen>
- It is best to let Samba figure out the domain join type from the settings in the &smb.conf; file.
- </para>
-
- <para>
- The command to join a Samba server to a Windows ADS domain is shown here:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>join</tertiary></indexterm>
-<screen>
-&rootprompt; net ads join -UAdministrator%not24get
-Using short domain name -- GDANSK
-Joined 'FRANDIMITZ' to realm 'GDANSK.ABMAS.BIZ'
-</screen>
- </para>
-
- <para>
- There is no specific option to remove a machine account from an NT4 domain. When a domain member that is a
- Windows machine is withdrawn from the domain, the domain membership account is not automatically removed
- either. Inactive domain member accounts can be removed using any convenient tool. If necessary, the
- machine account can be removed using the following <command>net</command> command:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>user delete</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc user delete HERRING\$ -Uroot%not24get
-Deleted user account.
-</screen>
- The removal is made possible because machine accounts are just like user accounts with a trailing $
- character. The account management operations treat user and machine accounts in like manner.
- </para>
-
- <para>
- A Samba server that is a Windows ADS domain member can execute the following command to detach from the
- domain:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>leave</tertiary></indexterm>
-<screen>
-&rootprompt; net ads leave
-</screen>
- </para>
-
- <para>
- Detailed information regarding an ADS domain can be obtained by a Samba DMS machine by executing the
- following:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>status</tertiary></indexterm>
-<screen>
-&rootprompt; net ads status
-</screen>
- The volume of information is extensive. Please refer to the book <quote>Samba-3 by Example</quote>,
- Chapter 7 for more information regarding its use. This book may be obtained either in print or online from
- the <ulink url="http://www.samba.org/samba/docs/Samba3-ByExample.pdf">Samba-3 by Example</ulink>.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Interdomain Trusts</title>
-
- <para>
- Interdomain trust relationships form the primary mechanism by which users from one domain can be granted
- access rights and privileges in another domain.
- </para>
-
- <para>
- To discover what trust relationships are in effect, execute this command:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom list</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc trustdom list -Uroot%not24get
-Trusted domains list:
-
-none
-
-Trusting domains list:
-
-none
-</screen>
- There are no interdomain trusts at this time; the following steps will create them.
- </para>
-
- <para>
- It is necessary to create a trust account in the local domain. A domain controller in a second domain can
- create a trusted connection with this account. That means that the foreign domain is being trusted
- to access resources in the local domain. This command creates the local trust account:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom add</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc trustdom add DAMNATION f00db4r -Uroot%not24get
-</screen>
- The account can be revealed by using the <command>pdbedit</command> as shown here:
-<screen>
-&rootprompt; pdbedit -Lw DAMNATION\$
-DAMNATION$:1016:9AC1F121DF897688AAD3B435B51404EE: \
-7F845808B91BB9F7FEF44B247D9DC9A6:[I ]:LCT-428934B1:
-</screen>
- A trust account will always have an I in the field within the square brackets.
- </para>
-
- <para>
- If the trusting domain is not capable of being reached, the following command will fail:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom list</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc trustdom list -Uroot%not24get
-Trusted domains list:
-
-none
-
-Trusting domains list:
-
-DAMNATION S-1-5-21-1385457007-882775198-1210191635
-</screen>
- The above command executed successfully; a failure is indicated when the following response is obtained:
-<screen>
-net rpc trustdom list -Uroot%not24get
-Trusted domains list:
-
-DAMNATION S-1-5-21-1385457007-882775198-1210191635
-
-Trusting domains list:
-
-DAMNATION domain controller is not responding
-</screen>
- </para>
-
- <para>
- Where a trust account has been created on a foreign domain, Samba is able to establish the trust (connect with)
- the foreign account. In the process it creates a one-way trust to the resources on the remote domain. This
- command achieves the objective of joining the trust relationship:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom establish</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc trustdom establish DAMNATION
-Password: xxxxxxx == f00db4r
-Could not connect to server TRANSGRESSION
-Trust to domain DAMNATION established
-</screen>
- Validation of the two-way trust now established is possible as shown here:
-<screen>
-&rootprompt; net rpc trustdom list -Uroot%not24get
-Trusted domains list:
-
-DAMNATION S-1-5-21-1385457007-882775198-1210191635
-
-Trusting domains list:
-
-DAMNATION S-1-5-21-1385457007-882775198-1210191635
-</screen>
- </para>
-
- <para>
- Sometimes it is necessary to remove the ability for local users to access a foreign domain. The trusting
- connection can be revoked as shown here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>trustdom revoke</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc trustdom revoke DAMNATION -Uroot%not24get
-</screen>
- At other times it becomes necessary to remove the ability for users from a foreign domain to be able to
- access resources in the local domain. The command shown here will do that:
-<screen>
-&rootprompt; net rpc trustdom del DAMNATION -Uroot%not24get
-</screen>
-
- </para>
-
- </sect2>
-
- </sect1>
-
- <sect1>
- <title>Managing Security Identifiers (SIDS)</title>
-
- <para>
-<indexterm><primary>security identifier</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>desktop profiles</primary></indexterm>
-<indexterm><primary>user encoded</primary></indexterm>
-<indexterm><primary>group SID</primary></indexterm>
- The basic security identifier that is used by all Windows networking operations is the Windows security
- identifier (SID). All Windows network machines (servers and workstations), users, and groups are
- identified by their respective SID. All desktop profiles are also encoded with user and group SIDs that
- are specific to the SID of the domain to which the user belongs.
- </para>
-
- <para>
-<indexterm><primary>machine SID</primary></indexterm>
-<indexterm><primary>domain SID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>rejoin</primary></indexterm>
- It is truly prudent to store the machine and/or domain SID in a file for safekeeping. Why? Because
- a change in hostname or in the domain (workgroup) name may result in a change in the SID. When you
- have the SID on hand, it is a simple matter to restore it. The alternative is to suffer the pain of
- having to recover user desktop profiles and perhaps rejoin all member machines to the domain.
- </para>
-
- <para>
- First, do not forget to store the local SID in a file. It is a good idea to put this in the directory
- in which the &smb.conf; file is also stored. Here is a simple action to achieve this:
-<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
-<screen>
-&rootprompt; net getlocalsid > /etc/samba/my-sid
-</screen>
- Good, there is now a safe copy of the local machine SID. On a PDC/BDC this is the domain SID also.
- </para>
-
- <para>
- The following command reveals what the former one should have placed into the file called
- <filename>my-sid</filename>:
-<screen>
-&rootprompt; net getlocalsid
-SID for domain MERLIN is: S-1-5-21-726309263-4128913605-1168186429
-</screen>
- </para>
-
- <para>
- If ever it becomes necessary to restore the SID that has been stored in the <filename>my-sid</filename>
- file, simply copy the SID (the string of characters that begins with <constant>S-1-5-21</constant>) to
- the command line shown here:
-<indexterm><primary>net</primary><secondary>setlocalsid</secondary></indexterm>
-<screen>
-&rootprompt; net setlocalsid S-1-5-21-1385457007-882775198-1210191635
-</screen>
- Restoration of a machine SID is a simple operation, but the absence of a backup copy can be very
- problematic.
- </para>
-
- <para>
- The following operation is useful only for machines that are being configured as a PDC or a BDC.
- DMS and workstation clients should have their own machine SID to avoid
- any potential namespace collision. Here is the way that the BDC SID can be synchronized to that
- of the PDC (this is the default NT4 domain practice also):
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>getsid</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc getsid -S FRODO -Uroot%not24get
-Storing SID S-1-5-21-726309263-4128913605-1168186429 \
- for Domain MIDEARTH in secrets.tdb
-</screen>
- Usually it is not necessary to specify the target server (-S FRODO) or the administrator account
- credentials (-Uroot%not24get).
- </para>
-
- </sect1>
-
- <sect1>
- <title>Share Management</title>
-
- <para>
- Share management is central to all file serving operations. Typical share operations include:
- </para>
-
- <itemizedlist>
- <listitem><para>Creation/change/deletion of shares</para></listitem>
- <listitem><para>Setting/changing ACLs on shares</para></listitem>
- <listitem><para>Moving shares from one server to another</para></listitem>
- <listitem><para>Change of permissions of share contents</para></listitem>
- </itemizedlist>
-
- <para>
- Each of these are dealt with here insofar as they involve the use of the <command>net</command>
- command. Operations outside of this command are covered elsewhere in this document.
- </para>
-
- <sect2>
- <title>Creating, Editing, and Removing Shares</title>
-
- <para>
- A share can be added using the <command>net rpc share</command> command capabilities.
- The target machine may be local or remote and is specified by the -S option. It must be noted
- that the addition and deletion of shares using this tool depends on the availability of a suitable
- interface script. The interface scripts Sambas <command>smbd</command> uses are called
- <smbconfoption name="add share command"/>, <smbconfoption name="delete share command"/> and
- <smbconfoption name="change share command"/>. A set of example scripts are provided in the Samba source
- code tarball in the directory <filename>~samba/examples/scripts</filename>.
- </para>
-
- <para>
- The following steps demonstrate the use of the share management capabilities of the <command>net</command>
- utility. In the first step a share called <constant>Bulge</constant> is added. The sharepoint within the
- file system is the directory <filename>/data</filename>. The command that can be executed to perform the
- addition of this share is shown here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share add</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc share add Bulge=/data -S MERLIN -Uroot%not24get
-</screen>
- Validation is an important process, and by executing the command <command>net rpc share</command>
- with no other operators it is possible to obtain a listing of available shares, as shown here:
-<screen>
-&rootprompt; net rpc share -S MERLIN -Uroot%not24get
-profdata
-archive
-Bulge <--- This one was added
-print$
-netlogon
-profiles
-IPC$
-kyocera
-ADMIN$
-</screen>
- </para>
-
- <para>
- Often it is desirable also to permit a share to be removed using a command-line tool.
- The following step permits the share that was previously added to be removed:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share delete</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc share delete Bulge -S MERLIN -Uroot%not24get
-</screen>
- A simple validation shown here demonstrates that the share has been removed:
-<screen>
-&rootprompt; net rpc share -S MERLIN -Uroot%not24get
-profdata
-archive
-print$
-netlogon
-profiles
-IPC$
-ADMIN$
-kyocera
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Creating and Changing Share ACLs</title>
-
- <para>
- At this time the <command>net</command> tool cannot be used to manage ACLs on Samba shares. In MS Windows
- language this is called Share Permissions.
- </para>
-
- <para>
- It is possible to set ACLs on Samba shares using either the SRVTOOLS NT4 Domain Server Manager
- or using the Computer Management MMC snap-in. Neither is covered here,
- but see <link linkend="AccessControls"/>.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Share, Directory, and File Migration</title>
-
- <para>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>vampire</tertiary></indexterm>
- Shares and files can be migrated in the same manner as user, machine, and group accounts.
- It is possible to preserve access control settings (ACLs) as well as security settings
- throughout the migration process. The <command>net rpc vampire</command> facility is used
- to migrate accounts from a Windows NT4 (or later) domain to a Samba server. This process
- preserves passwords and account security settings and is a precursor to the migration
- of shares and files.
- </para>
-
- <para>
- The <command>net rpc share</command> command may be used to migrate shares, directories,
- files, and all relevant data from a Windows server to a Samba server.
- </para>
-
- <para>
- A set of command-line switches permit the creation of almost direct clones of Windows file
- servers. For example, when migrating a fileserver, file ACLs and DOS file attributes from
- the Windows server can be included in the migration process and will reappear, almost identically,
- on the Samba server when the migration has been completed.
- </para>
-
- <para>
- The migration process can be completed only with the Samba server already being fully operational.
- The user and group accounts must be migrated before attempting to migrate data
- share, files, and printers. The migration of files and printer configurations involves the use
- of both SMB and MS DCE RPC services. The benefit of the manner in which the migration process has
- been implemented is that the possibility now exists to use a Samba server as a man-in-middle migration
- service that affects a transfer of data from one server to another. For example, if the Samba
- server is called MESSER, the source Windows NT4 server is called PEPPY, and the target Samba
- server is called GONZALES, the machine MESSER can be used to effect the migration of all data
- (files and shares) from PEPPY to GONZALES. If the target machine is not specified, the local
- server is assumed by default - as net's general rule of thumb .
- </para>
-
- <para>
- The success of server migration requires a firm understanding of the structure of the source
- server (or domain) as well as the processes on which the migration is critically dependant.
- </para>
-
- <para>
- There are two known limitations to the migration process:
- </para>
-
- <orderedlist>
- <listitem><para>
- The <command>net</command> command requires that the user credentials provided exist on both
- the migration source and the migration target.
- </para></listitem>
-
- <listitem><para>
- Printer settings may not be fully or may be incorrectly migrated. This might in particular happen
- when migrating a Windows 2003 print server to Samba.
- </para></listitem>
- </orderedlist>
-
- <sect3>
- <title>Share Migration</title>
-
- <para>
- The <command>net rpc share migrate</command> command operation permits the migration of plain
- share stanzas. A stanza contains the parameters within which a file or print share are defined.
- The use of this migration method will create share stanzas that have as parameters the file
- system directory path, an optional description, and simple security settings that permit write
- access to files. One of the first steps necessary following migration is to review the share
- stanzas to ensure that the settings are suitable for use.
- </para>
-
- <para>
- The shares are created on the fly as part of the migration process. The <command>smbd</command>
- application does this by calling on the operating system to execute the script specified by the
- &smb.conf; parameter <parameter>add share command</parameter>.
- </para>
-
- <para>
- There is a suitable example script for the <parameter>add share command</parameter> in the
- <filename>$SAMBA_SOURCES/examples/scripts</filename> directory. It should be noted that
- the account that is used to drive the migration must, of necessity, have appropriate file system
- access privileges and have the right to create shares and to set ACLs on them. Such rights are
- conferred by these rights: <parameter>SeAddUsersPrivilege</parameter> and <parameter>SeDiskOperatorPrivilege</parameter>.
- For more information regarding rights and privileges please refer to <link linkend="rights"/>.
- </para>
-
- <para>
- The syntax of the share migration command is shown here:
-<screen>
-net rpc share MIGRATE SHARES <share-name> -S <source>
- [--destination=localhost] [--exclude=share1,share2] [-v]
-</screen>
- When the parameter <share-name> is omitted, all shares will be migrated. The potentially
- large list of available shares on the system that is being migrated can be limited using the
- <parameter>--exclude</parameter> switch. For example:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc share migrate shares myshare\
- -S win2k -U administrator%secret"
-</screen>
- This will migrate the share <constant>myshare</constant> from the server <constant>win2k</constant>
- to the Samba Server using the permissions that are tied to the account <constant>administrator</constant>
- with the password <constant>secret</constant>. The account that is used must be the same on both the
- migration source server and the target Samba server. The use of the <command>net rpc
- vampire</command>, prior to attempting the migration of shares, will ensure that accounts will be
- identical on both systems. One precaution worth taking before commencement of migration of shares is
- to validate that the migrated accounts (on the Samba server) have the needed rights and privileges.
- This can be done as shown here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>right list accounts</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc right list accounts -Uroot%not24get
-</screen>
- The steps taken so far perform only the migration of shares. Directories and directory contents
- are not migrated by the steps covered up to this point.
- </para>
-
- </sect3>
-
- <sect3>
- <title>File and Directory Migration</title>
-
- <para>
- Everything covered to this point has been done in preparation for the migration of file and directory
- data. For many people preparation is potentially boring and the real excitement only begins when file
- data can be used. The next steps demonstrate the techniques that can be used to transfer (migrate)
- data files using the <command>net</command> command.
- </para>
-
- <para>
- Transfer of files from one server to another has always been a challenge for MS Windows
- administrators because Windows NT and 200X servers do not always include the tools needed. The
- <command>xcopy</command> from Windows NT is not capable of preserving file and directory ACLs,
- it does so only with Windows 200x. Microsoft does provide a
- utility that can copy ACLs (security settings) called <command>scopy</command>, but it is provided only
- as part of the Windows NT or 200X Server Resource Kit.
- </para>
-
- <para>
- There are several tools, both commercial and freeware, that can be used from a Windows server to copy files
- and directories with full preservation of security settings. One of the best known of the free tools is
- called <command>robocopy</command>.
- </para>
-
- <para>
- The <command>net</command> utility can be used to copy files and directories with full preservation of
- ACLs as well as DOS file attributes. Note that including ACLs makes sense only where the destination
- system will operate within the same security context as the source system. This applies both to a
- DMS and to domain controllers that result from a vampired domain.
- Before file and directory migration, all shares must already exist.
- </para>
-
- <para>
- The syntax for the migration commands is shown here:
-<screen>
-net rpc share MIGRATE FILES <share-name> -S <source>
- [--destination=localhost] [--exclude=share1,share2]
- [--acls] [--attrs] [--timestamps] [-v]
-</screen>
- If the <share-name> parameter is omitted, all shares will be migrated. The potentially large
- list of shares on the source system can be restricted using the <parameter>--exclude</parameter> command
- switch.
- </para>
-
- <para>
- Where it is necessary to preserve all file ACLs, the <parameter>--acls</parameter> switch should be added
- to the above command line. Original file timestamps can be preserved by specifying the
- <parameter>--timestamps</parameter> switch, and the DOS file attributes (i.e., hidden, archive, etc.) can
- be preserved by specifying the <parameter>--attrs</parameter> switch.
- </para>
-
- <note><para>
- The ability to preserve ACLs depends on appropriate support for ACLs as well as the general file system
- semantics of the host operating system on the target server. A migration from one Windows file server to
- another will perfectly preserve all file attributes. Because of the difficulty of mapping Windows ACLs
- onto a POSIX ACLs-supporting system, there can be no perfect migration of Windows ACLs to a Samba server.
- </para></note>
-
- <para>
- The ACLs that result on a Samba server will most probably not match the originating ACLs. Windows supports
- the possibility of files that are owned only by a group. Group-alone file ownership is not possible under
- UNIX/Linux. Errors in migrating group-owned files can be avoided by using the &smb.conf; file
- <smbconfoption name="force unknown acl user">yes</smbconfoption> parameter. This facility will
- automatically convert group-owned files into correctly user-owned files on the Samba server.
- </para>
-
- <para>
- An example for migration of files from a machine called <constant>nt4box</constant> to the Samba server
- from which the process will be handled is shown here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate files</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc share migrate files -S nt4box --acls \
- --attrs -U administrator%secret
-</screen>
- </para>
-
- <para>
- This command will migrate all files and directories from all file shares on the Windows server called
- <constant>nt4box</constant> to the Samba server from which migration is initiated. Files that are group-owned
- will be owned by the user account <constant>administrator</constant>.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Share-ACL Migration</title>
- <para>
- It is possible to have share-ACLs (security descriptors) that won't allow you, even as Administrator, to
- copy any files or directories into it. Therefor the migration of the share-ACLs has been put into a separate
- function:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate security</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc share migrate security -S nt4box -U administrator%secret
-</screen>
- </para>
-
- <para>
- This command will only copy the share-ACL of each share on nt4box to your local samba-system.
- </para>
- </sect3>
-
- <sect3>
- <title>Simultaneous Share and File Migration</title>
-
- <para>
- The operating mode shown here is just a combination of the previous three. It first migrates
- share definitions and then all shared files and directories and finally migrates the share-ACLs:
-<screen>
-net rpc share MIGRATE ALL <share-name> -S <source>
- [--exclude=share1, share2] [--acls] [--attrs] [--timestamps] [-v]
-</screen>
- </para>
-
- <para>
- An example of simultaneous migration is shown here:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>share migrate all</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc share migrate all -S w2k3server -U administrator%secret
-</screen>
- This will generate a complete server clone of the <parameter>w2k3server</parameter> server.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Printer Migration</title>
-
- <para>
- The installation of a new server, as with the migration to a new network environment, often is similar to
- building a house; progress is very rapid from the laying of foundations up to the stage at which
- the house can be locked up, but the finishing off appears to take longer and longer as building
- approaches completion.
- </para>
-
- <para>
- Printing needs vary greatly depending on the network environment and may be very simple or complex. If
- the need is very simple, the best solution to the implementation of printing support may well be to
- re-install everything from a clean slate instead of migrating older configurations. On the other hand,
- a complex network that is integrated with many international offices and a complex arrangement of local branch
- offices, each of which form an inter-twined maze of printing possibilities, the ability to migrate all
- printer configurations is decidedly beneficial. To manually re-establish a complex printing network
- will take much time and frustration. Often it will not be possible to find driver files that are
- currently in use, necessitating the installation of newer drivers. Newer drivers often implement
- printing features that will necessitate a change in the printer usage. Additionally, with very complex
- printer configurations it becomes almost impossible to re-create the same environment &smbmdash; no matter
- how extensively it has been documented.
- </para>
-
- <para>
- The migration of an existing printing architecture involves the following:
- </para>
-
- <itemizedlist>
- <listitem><para>Establishment of print queues.</para></listitem>
-
- <listitem><para>Installation of printer drivers (both for the print server and for Windows clients.</para></listitem>
-
- <listitem><para>Configuration of printing forms.</para></listitem>
-
- <listitem><para>Implementation of security settings.</para></listitem>
-
- <listitem><para>Configuration of printer settings.</para></listitem>
- </itemizedlist>
-
- <para>
- The Samba <command>net</command> utility permits printer migration from one Windows print server
- to another. When this tool is used to migrate printers to a Samba server <command>smbd</command>,
- the application that receives the network requests to create the necessary services must call out
- to the operating system in order to create the underlying printers. The call-out is implemented
- by way of an interface script that can be specified by the &smb.conf; file parameter
- <smbconfoption name="add printer script"/>. This script is essential to the migration process.
- A suitable example script may be obtained from the <filename>$SAMBA_SOURCES/examples/scripts</filename>
- directory. Take note that this script must be customized to suit the operating system environment
- and may use its tools to create a print queue.
- </para>
-
- <para>
- Each of the components listed above can be completed separately, or they can be completed as part of an
- automated operation. Many network administrators prefer to deal with migration issues in a manner that
- gives them the most control, particularly when things go wrong. The syntax for each operation is now
- briefly described.
- </para>
-
- <para>
- Printer migration from a Windows print server (NT4 or 200x) is shown. This instruction causes the
- printer share to be created together with the underlying print queue:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate printers</tertiary></indexterm>
-<screen>
-net rpc printer MIGRATE PRINTERS [printer] [misc. options] [targets]
-</screen>
- Printer drivers can be migrated from the Windows print server to the Samba server using this
- command-line instruction:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate drivers</tertiary></indexterm>
-<screen>
-net rpc printer MIGRATE DRIVERS [printer] [misc. options] [targets]
-</screen>
- Printer forms can be migrated with the following operation:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate forms</tertiary></indexterm>
-<screen>
-net rpc printer MIGRATE FORMS [printer] [misc. options] [targets]
-</screen>
- Printer security settings (ACLs) can be migrated from the Windows server to the Samba server using this command:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate security</tertiary></indexterm>
-<screen>
-net rpc printer MIGRATE SECURITY [printer] [misc. options] [targets]
-</screen>
- Printer configuration settings include factors such as paper size and default paper orientation.
- These can be migrated from the Windows print server to the Samba server with this command:
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>printer migrate settings</tertiary></indexterm>
-<screen>
-net rpc printer MIGRATE SETTINGS [printer] [misc. options] [targets]
-</screen>
- </para>
-
- <para>
- Migration of printers including the above-mentioned sets of information may be completed
- with a single command using this syntax:
-<screen>
-net rpc printer MIGRATE ALL [printer] [misc. options] [targets]
-</screen>
- </para>
-
- </sect2>
-
- </sect1>
-
- <sect1>
- <title>Controlling Open Files</title>
-
- <para>
- The man page documents the <command>net file</command> function suite, which provides the tools to
- close open files using either RAP or RPC function calls. Please refer to the man page for specific
- usage information.
- </para>
-
- </sect1>
-
- <sect1>
- <title>Session and Connection Management</title>
-
- <para>
- The session management interface of the <command>net session</command> command uses the old RAP
- method to obtain the list of connections to the Samba server, as shown here:
-<indexterm><primary>net</primary><secondary>rap</secondary><tertiary>session</tertiary></indexterm>
-<screen>
-&rootprompt; net rap session -S MERLIN -Uroot%not24get
-Computer User name Client Type Opens Idle time
-------------------------------------------------------------------------------
-\\merlin root Unknown Client 0 00:00:00
-\\marvel jht Unknown Client 0 00:00:00
-\\maggot jht Unknown Client 0 00:00:00
-\\marvel jht Unknown Client 0 00:00:00
-</screen>
- </para>
-
- <para>
- A session can be closed by executing a command as shown here:
-<screen>
-&rootprompt; net rap session close marvel -Uroot%not24get
-</screen>
- </para>
-
- </sect1>
-
- <sect1>
- <title>Printers and ADS</title>
-
- <para>
- When Samba is used within an MS Windows ADS environment, printers shared via Samba will not be browseable
- until they have been published to the ADS domain. Information regarding published printers may be obtained
- from the ADS server by executing the <command>net ads print info</command> command following this syntax:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer info</tertiary></indexterm>
-<screen>
-net ads printer info <printer_name> <server_name> -Uadministrator%secret
-</screen>
- If the asterisk (*) is used in place of the printer_name argument, a list of all printers will be
- returned.
- </para>
-
- <para>
- To publish (make available) a printer to ADS, execute the following command:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer publish</tertiary></indexterm>
-<screen>
-net ads printer publish <printer_name> -Uadministrator%secret
-</screen>
- This publishes a printer from the local Samba server to ADS.
- </para>
-
- <para>
- Removal of a Samba printer from ADS is achieved by executing this command:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer remove</tertiary></indexterm>
-<screen>
-net ads printer remove <printer_name> -Uadministrator%secret
-</screen>
- </para>
-
- <para>
- A generic search (query) can also be made to locate a printer across the entire ADS domain by executing:
-<indexterm><primary>net</primary><secondary>ads</secondary><tertiary>printer search</tertiary></indexterm>
-<screen>
-net ads printer search <printer_name> -Uadministrator%secret
-</screen>
- </para>
-
- </sect1>
-
- <sect1>
- <title>Manipulating the Samba Cache</title>
-
- <para>
- Please refer to the <command>net</command> command man page for information regarding cache management.
- </para>
-
- </sect1>
-
- <sect1>
- <title>Managing IDMAP UID/SID Mappings</title>
-
- <para>
- The IDMAP UID to SID, and SID to UID, mappings that are created by <command>winbindd</command> can be
- backed up to a text file. The text file can be manually edited, although it is highly recommended that
- you attempt this only if you know precisely what you are doing.
- </para>
-
- <para>
- An IDMAP text dump file can be restored (or reloaded). There are two situations that may necessitate
- this action: a) The existing IDMAP file is corrupt, b) It is necessary to install an editted version
- of the mapping information.
- </para>
-
- <para>
- Winbind must be shut down to dump the IDMAP file. Before restoring a dump file, shut down
- <command>winbindd</command> and delete the old <filename>winbindd_idmap.tdb</filename> file.
- </para>
-
- <sect2>
- <title>Creating an IDMAP Database Dump File</title>
-
- <para>
- The IDMAP database can be dumped to a text file as shown here:
-<screen>
-net idmap dump <full_path_and_tdb_filename> > dumpfile.txt
-</screen>
- Where a particular build of Samba the run-time tdb files are stored in the
- <filename>/var/lib/samba</filename> directory the following commands to create the dump file will suffice:
-<screen>
-net idmap dump /var/lib/samba/winbindd_idmap.tdb > idmap_dump.txt
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Restoring the IDMAP Database Dump File</title>
-
- <para>
- The IDMAP dump file can be restored using the following command:
-<screen>
-net idmap restore idmap_dump.txt
-</screen>
- Where the Samba run-time tdb files are stored in the <filename>/var/lib/samba</filename> directory
- the following command can be used to restore the data to the tdb file:
-<screen>
-net idmap restore /var/lib/samba/winbindd_idmap.tdb < idmap_dump.txt
-</screen>
- </para>
-
- </sect2>
-
- </sect1>
-
- <sect1 id="netmisc1">
- <title>Other Miscellaneous Operations</title>
-
- <para>
- The following command is useful for obtaining basic statistics regarding a Samba domain. This command does
- not work with current Windows XP Professional clients.
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>info</tertiary></indexterm>
-<screen>
-&rootprompt; net rpc info
-Domain Name: RAPIDFLY
-Domain SID: S-1-5-21-399034208-633907489-3292421255
-Sequence number: 1116312355
-Num users: 720
-Num domain groups: 27
-Num local groups: 6
-</screen>
- </para>
-
- <para>
- Another useful tool is the <command>net time</command> tool set. This tool may be used to query the
- current time on the target server as shown here:
-<indexterm><primary>net</primary><secondary>time</secondary></indexterm>
-<screen>
-&rootprompt; net time -S SAURON
-Tue May 17 00:50:43 2005
-</screen>
- In the event that it is the intent to pass the time information obtained to the UNIX
- <command>/bin/time</command>, it is a good idea to obtain the time from the target server in a format
- that is ready to be passed through. This may be done by executing:
-<indexterm><primary>net</primary><secondary>time</secondary><tertiary>system</tertiary></indexterm>
-<screen>
-&rootprompt; net time system -S FRODO
-051700532005.16
-</screen>
- The time can be set on a target server by executing:
-<indexterm><primary>net</primary><secondary>time</secondary><tertiary>set</tertiary></indexterm>
-<screen>
-&rootprompt; net time set -S MAGGOT -U Administrator%not24get
-Tue May 17 00:55:30 MDT 2005
-</screen>
- It is possible to obtain the time zone of a server by executing the following command against it:
-<indexterm><primary>net</primary><secondary>time</secondary><tertiary>zone</tertiary></indexterm>
-<screen>
-&rootprompt; net time zone -S SAURON
--0600
-</screen>
- </para>
-
- </sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="unicode">
-<chapterinfo>
- &author.jelmer;
- &author.jht;
- <author>
- <firstname>TAKAHASHI</firstname><surname>Motonobu</surname>
- <affiliation>
- <address><email>monyo@home.monyo.com</email></address>
- </affiliation>
- <contrib>Japanese character support</contrib>
- </author>
- <pubdate>25 March 2003</pubdate>
-</chapterinfo>
-
-<title>Unicode/Charsets</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>use computer anywhere</primary></indexterm>
-Every industry eventually matures. One of the great areas of maturation is in
-the focus that has been given over the past decade to make it possible for anyone
-anywhere to use a computer. It has not always been that way. In fact, not so long
-ago, it was common for software to be written for exclusive use in the country of
-origin.
-</para>
-
-<para>
-Of all the effort that has been brought to bear on providing native
-language support for all computer users, the efforts of the
-<ulink url="http://www.openi18n.org/">Openi18n organization</ulink>
-is deserving of special mention.
-</para>
-
-<para>
-<indexterm><primary>codepages</primary></indexterm>
-Samba-2.x supported a single locale through a mechanism called
-<emphasis>codepages</emphasis>. Samba is destined to become a truly transglobal
-file- and printer-sharing platform.
-</para>
-
-</sect1>
-
-<sect1>
-<title>What Are Charsets and Unicode?</title>
-
-<para>
-<indexterm><primary>character set</primary></indexterm>
-Computers communicate in numbers. In texts, each number is
-translated to a corresponding letter. The meaning that will be assigned
-to a certain number depends on the <emphasis>character set (charset)
-</emphasis> that is used.
-</para>
-
-<para>
-<indexterm><primary>charset</primary></indexterm>
-<indexterm><primary>ASCII</primary></indexterm>
-A charset can be seen as a table that is used to translate numbers to
-letters. Not all computers use the same charset (there are charsets
-with German umlauts, Japanese characters, and so on). The American Standard Code
-for Information Interchange (ASCII) encoding system has been the normative character
-encoding scheme used by computers to date. This employs a charset that contains
-256 characters. Using this mode of encoding, each character takes exactly one byte.
-</para>
-
-<para>
-<indexterm><primary>multibyte charsets</primary></indexterm>
-<indexterm><primary>extended characters</primary></indexterm>
-There are also charsets that support extended characters, but those need at least
-twice as much storage space as does ASCII encoding. Such charsets can contain
-<command>256 * 256 = 65536</command> characters, which is more than all possible
-characters one could think of. They are called multibyte charsets because they use
-more then one byte to store one character.
-</para>
-
-<para>
-<indexterm><primary>unicode</primary></indexterm>
-One standardized multibyte charset encoding scheme is known as
-<ulink url="http://www.unicode.org/">unicode</ulink>. A big advantage of using a
-multibyte charset is that you only need one. There is no need to make sure two
-computers use the same charset when they are communicating.
-</para>
-
-<para>
-<indexterm><primary>single-byte charsets</primary></indexterm>
-<indexterm><primary>SMB/CIFS</primary></indexterm>
-<indexterm><primary>negotiating the charset</primary></indexterm>
-Old Windows clients use single-byte charsets, named
-<parameter>codepages</parameter>, by Microsoft. However, there is no support for
-negotiating the charset to be used in the SMB/CIFS protocol. Thus, you
-have to make sure you are using the same charset when talking to an older client.
-Newer clients (Windows NT, 200x, XP) talk Unicode over the wire.
-</para>
-</sect1>
-
-<sect1>
-<title>Samba and Charsets</title>
-
-<para>
-<indexterm><primary>Unicode</primary></indexterm>
-<indexterm><primary>character sets</primary></indexterm>
-As of Samba-3, Samba can (and will) talk Unicode over the wire. Internally,
-Samba knows of three kinds of character sets:
-</para>
-
-<variablelist>
- <varlistentry>
- <term><smbconfoption name="unix charset"/></term>
- <listitem><para>
-<indexterm><primary>UTF-8</primary></indexterm>
-<indexterm><primary>CP850</primary></indexterm>
- This is the charset used internally by your operating system.
- The default is <constant>UTF-8</constant>, which is fine for most
- systems and covers all characters in all languages. The default
- in previous Samba releases was to save filenames in the encoding of the
- clients &smbmdash; for example, CP850 for Western European countries.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term><smbconfoption name="display charset"/></term>
- <listitem><para>This is the charset Samba uses to print messages
- on your screen. It should generally be the same as the <parameter>unix charset</parameter>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term><smbconfoption name="dos charset"/></term>
- <listitem><para>This is the charset Samba uses when communicating with
- DOS and Windows 9x/Me clients. It will talk Unicode to all newer clients.
- The default depends on the charsets you have installed on your system.
- Run <command>testparm -v | grep "dos charset"</command> to see
- what the default is on your system.
- </para></listitem>
- </varlistentry>
-</variablelist>
-
-</sect1>
-
-<sect1>
-<title>Conversion from Old Names</title>
-
-<para>
-<indexterm><primary>charset conversion</primary></indexterm>
-Because previous Samba versions did not do any charset conversion,
-characters in filenames are usually not correct in the UNIX charset but only
-for the local charset used by the DOS/Windows clients.
-</para>
-
-<para>Bjoern Jacke has written a utility named <ulink url="http://j3e.de/linux/convmv/">convmv</ulink>
-that can convert whole directory structures to different charsets with one single command.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Japanese Charsets</title>
-
-<para>
-Setting up Japanese charsets is quite difficult. This is mainly because:
-</para>
-
-<itemizedlist>
- <listitem><para>
-<indexterm><primary>JIS X 0208</primary></indexterm>
- The Windows character set is extended from the original legacy Japanese
- standard (JIS X 0208) and is not standardized. This means that the strictly
- standardized implementation cannot support the full Windows character set.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>Shift_JIS</primary></indexterm>
-<indexterm><primary>EUC-JP</primary></indexterm>
-<indexterm><primary>CAP</primary></indexterm>
-<indexterm><primary>HEX</primary></indexterm>
-<indexterm><primary>Japanese</primary></indexterm>
- Mainly for historical reasons, there are several encoding methods in
- Japanese, which are not fully compatible with each other. There are
- two major encoding methods. One is the Shift_JIS series used in Windows
- and some UNIXes. The other is the EUC-JP series used in most UNIXes
- and Linux. Moreover, Samba previously also offered several unique encoding
- methods, named CAP and HEX, to keep interoperability with CAP/NetAtalk and
- UNIXes that can't use Japanese filenames. Some implementations of the
- EUC-JP series can't support the full Windows character set.
- </para></listitem>
-
- <listitem><para>There are some code conversion tables between Unicode and legacy
- Japanese character sets. One is compatible with Windows, another one
- is based on the reference of the Unicode consortium, and others are
- a mixed implementation. The Unicode consortium does not officially
- define any conversion tables between Unicode and legacy character
- sets, so there cannot be standard one.
- </para></listitem>
-
- <listitem><para>The character set and conversion tables available in iconv() depend
- on the iconv library that is available. Next to that, the Japanese locale
- names may be different on different systems. This means that the value of
- the charset parameters depends on the implementation of iconv() you are using.
- </para>
-
- <para>
-<indexterm><primary>UCS-2</primary></indexterm>
-<indexterm><primary>Shift_JIS</primary></indexterm>
-<indexterm><primary>ASCII</primary></indexterm>
-<indexterm><primary>English</primary></indexterm>
- Though 2-byte fixed UCS-2 encoding is used in Windows internally,
- Shift_JIS series encoding is usually used in Japanese environments
- as ASCII encoding is in English environments.
- </para></listitem>
-</itemizedlist>
-
-<sect2><title>Basic Parameter Setting</title>
-
- <para>
-<indexterm><primary>CP932</primary></indexterm>
- The <smbconfoption name="dos charset"/> and
- <smbconfoption name="display charset"/>
- should be set to the locale compatible with the character set
- and encoding method used on Windows. This is usually CP932
- but sometimes has a different name.
- </para>
-
- <para>
-<indexterm><primary>Shift_JIS</primary></indexterm>
-<indexterm><primary>UTF-8</primary></indexterm>
-<indexterm><primary>EUC-JP</primary></indexterm>
- The <smbconfoption name="unix charset"/> can be either Shift_JIS series,
- EUC-JP series, or UTF-8. UTF-8 is always available, but the availability of other locales
- and the name itself depends on the system.
- </para>
-
- <para>
- Additionally, you can consider using the Shift_JIS series as the
- value of the <smbconfoption name="unix charset"/>
- parameter by using the vfs_cap module, which does the same thing as
- setting <quote>coding system = CAP</quote> in the Samba 2.2 series.
- </para>
-
- <para>
- Where to set <smbconfoption name="unix charset"/>
- to is a difficult question. Here is a list of details, advantages, and
- disadvantages of using a certain value.
- </para>
-
- <variablelist>
- <varlistentry><term>Shift_JIS series</term>
- <listitem><para>
- Shift_JIS series means a locale that is equivalent to <constant>Shift_JIS</constant>,
- used as a standard on Japanese Windows. In the case of <constant>Shift_JIS</constant>,
- for example, if a Japanese filename consists of 0x8ba4 and 0x974c
- (a 4-bytes Japanese character string meaning <quote>share</quote>) and <quote>.txt</quote>
- is written from Windows on Samba, the filename on UNIX becomes
- 0x8ba4, 0x974c, <quote>.txt</quote> (an 8-byte BINARY string), same as Windows.
- </para>
-
- <para>Since Shift_JIS series is usually used on some commercial-based
- UNIXes; hp-ux and AIX as the Japanese locale (however, it is also possible
- to use the EUC-JP locale series). To use Shift_JIS series on these platforms,
- Japanese filenames created from Windows can be referred to also on
- UNIX.</para>
-
- <para>
- If your UNIX is already working with Shift_JIS and there is a user
- who needs to use Japanese filenames written from Windows, the
- Shift_JIS series is the best choice. However, broken filenames
- may be displayed, and some commands that cannot handle non-ASCII
- filenames may be aborted during parsing filenames. Especially, there
- may be <quote>\ (0x5c)</quote> in filenames, which need to be handled carefully.
- It is best to not touch filenames written from Windows on UNIX.
- </para>
-
- <para>
- Note that most Japanized free software actually works with EUC-JP
- only. It is good practice to verify that the Japanized free software can work
- with Shift_JIS.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>EUC-JP series</term>
- <listitem><para>
-<indexterm><primary>EUC-JP</primary></indexterm>
-<indexterm><primary>Japanese UNIX</primary></indexterm>
- EUC-JP series means a locale that is equivalent to the industry
- standard called EUC-JP, widely used in Japanese UNIX (although EUC
- contains specifications for languages other than Japanese, such as
- EUC-KR). In the case of EUC-JP series, for example, if a Japanese
- filename consists of 0x8ba4 and 0x974c and <quote>.txt</quote> is written from
- Windows on Samba, the filename on UNIX becomes 0xb6a6, 0xcdad,
- <quote>.txt</quote> (an 8-byte BINARY string).
- </para>
-
- <para>
-<indexterm><primary>EUC-JP</primary></indexterm>
-<indexterm><primary>UNIX</primary></indexterm>
-<indexterm><primary>Linux</primary></indexterm>
-<indexterm><primary>FreeBSD</primary></indexterm>
-<indexterm><primary>Solaris</primary></indexterm>
-<indexterm><primary>IRIX</primary></indexterm>
-<indexterm><primary>Tru64 UNIX</primary></indexterm>
-<indexterm><primary>Japanese locale</primary></indexterm>
-<indexterm><primary>Shift_JIS</primary></indexterm>
-<indexterm><primary>UTF-8</primary></indexterm>
- Since EUC-JP is usually used on open source UNIX, Linux, and FreeBSD, and on commercial-based UNIX, Solaris,
- IRIX, and Tru64 UNIX as Japanese locale (however, it is also possible on Solaris to use Shift_JIS and UTF-8,
- and on Tru64 UNIX it is possible to use Shift_JIS). To use EUC-JP series, most Japanese filenames created from
- Windows can be referred to also on UNIX. Also, most Japanized free software works mainly with EUC-JP only.
- </para>
-
- <para>
- It is recommended to choose EUC-JP series when using Japanese filenames on UNIX.
- </para>
-
- <para>
- Although there is no character that needs to be carefully treated
- like <quote>\ (0x5c)</quote>, broken filenames may be displayed and some
- commands that cannot handle non-ASCII filenames may be aborted
- during parsing filenames.
- </para>
-
- <para>
-<indexterm><primary>eucJP-ms locale</primary></indexterm>
- Moreover, if you built Samba using differently installed libiconv,
- the eucJP-ms locale included in libiconv and EUC-JP series locale
- included in the operating system may not be compatible. In this case, you may need to
- avoid using incompatible characters for filenames.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>UTF-8</term>
- <listitem><para>
- UTF-8 means a locale equivalent to UTF-8, the international standard defined by the Unicode consortium. In
- UTF-8, a <parameter>character</parameter> is expressed using 1 to 3 bytes. In case of the Japanese language,
- most characters are expressed using 3 bytes. Since on Windows Shift_JIS, where a character is expressed with 1
- or 2 bytes is used to express Japanese, basically a byte length of a UTF-8 string the length of the UTF-8
- string is 1.5 times that of the original Shift_JIS string. In the case of UTF-8, for example, if a Japanese
- filename consists of 0x8ba4 and 0x974c, and <quote>.txt</quote> is written from Windows on Samba, the filename
- on UNIX becomes 0xe585, 0xb1e6, 0x9c89, <quote>.txt</quote> (a 10-byte BINARY string).
- </para>
-
- <para>
- For systems where iconv() is not available or where iconv()'s locales
- are not compatible with Windows, UTF-8 is the only locale available.
- </para>
-
- <para>
- There are no systems that use UTF-8 as the default locale for Japanese.
- </para>
-
- <para>
- Some broken filenames may be displayed, and some commands that
- cannot handle non-ASCII filenames may be aborted during parsing
- filenames. Especially, there may be <quote>\ (0x5c)</quote> in filenames, which
- must be handled carefully, so you had better not touch filenames
- written from Windows on UNIX.
- </para>
-
- <para>
-<indexterm><primary>Windows</primary></indexterm>
-<indexterm><primary>Java</primary></indexterm>
-<indexterm><primary>Unicode UTF-8</primary></indexterm>
- In addition, although it is not directly concerned with Samba, since
- there is a delicate difference between the iconv() function, which is
- generally used on UNIX, and the functions used on other platforms,
- such as Windows and Java, so far is concerns the conversion between
- Shift_JIS and Unicode UTF-8 must be done with care and recognition
- of the limitations involved in the process.
- </para>
-
- <para>
-<indexterm><primary>Mac OS X </primary></indexterm>
- Although Mac OS X uses UTF-8 as its encoding method for filenames,
- it uses an extended UTF-8 specification that Samba cannot handle, so
- UTF-8 locale is not available for Mac OS X.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>Shift_JIS series + vfs_cap (CAP encoding)</term>
- <listitem><para>
-<indexterm><primary>CAP</primary></indexterm>
-<indexterm><primary>NetAtalk</primary></indexterm>
-<indexterm><primary>Macintosh</primary></indexterm>
- CAP encoding means a specification used in CAP and NetAtalk, file
- server software for Macintosh. In the case of CAP encoding, for
- example, if a Japanese filename consists of 0x8ba4 and 0x974c, and
- <quote>.txt</quote> is written from Windows on Samba, the filename on UNIX
- becomes <quote>:8b:a4:97L.txt</quote> (a 14 bytes ASCII string).
- </para>
-
- <para>
- For CAP encoding, a byte that cannot be expressed as an ASCII
- character (0x80 or above) is encoded in an <quote>:xx</quote> form. You need to take
- care of containing a <quote>\(0x5c)</quote> in a filename, but filenames are not
- broken in a system that cannot handle non-ASCII filenames.
- </para>
-
- <para>
- The greatest merit of CAP encoding is the compatibility of encoding
- filenames with CAP or NetAtalk. These are respectively the Columbia Appletalk
- Protocol, and the NetAtalk Open Source software project.
- Since these software applications write a file name on UNIX with CAP encoding, if a
- directory is shared with both Samba and NetAtalk, you need to use
- CAP encoding to avoid non-ASCII filenames from being broken.
- </para>
-
- <para>
- However, recently, NetAtalk has been
- patched on some systems to write filenames with EUC-JP (e.g., Japanese original Vine Linux).
- In this case, you need to choose EUC-JP series instead of CAP encoding.
- </para>
-
- <para>
- vfs_cap itself is available for non-Shift_JIS series locales for
- systems that cannot handle non-ASCII characters or systems that
- share files with NetAtalk.
- </para>
-
- <para>
- To use CAP encoding on Samba, you should use the unix charset parameter and VFS
- as in <link linkend="vfscap-intl">the VFS CAP smb.conf file</link>.
- </para>
-
-<example id="vfscap-intl">
-<title>VFS CAP</title>
- <smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfcomment>the locale name "CP932" may be different</smbconfcomment>
-<smbconfoption name="dos charset">CP932</smbconfoption>
-<smbconfoption name="unix charset">CP932</smbconfoption>
-
-<smbconfsection name="[cap-share]"/>
-<smbconfoption name="vfs option">cap</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
-<indexterm><primary>CP932</primary></indexterm>
-<indexterm><primary>libiconv</primary></indexterm>
-<indexterm><primary>unix charset</primary></indexterm>
-<indexterm><primary>cap-share</primary></indexterm>
- You should set CP932 if using GNU libiconv for unix charset. With this setting,
- filenames in the <quote>cap-share</quote> share are written with CAP encoding.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
-</sect2>
-
-<sect2><title>Individual Implementations</title>
-
-<para>
-Here is some additional information regarding individual implementations:
-</para>
-
- <variablelist>
- <varlistentry><term>GNU libiconv</term>
- <listitem><para>
- To handle Japanese correctly, you should apply the patch
- <ulink url="http://www2d.biglobe.ne.jp/~msyk/software/libiconv-patch.html">libiconv-1.8-cp932-patch.diff.gz</ulink>
- to libiconv-1.8.
- </para>
-
- <para>
- Using the patched libiconv-1.8, these settings are available:
- </para>
-
-<programlisting>
-dos charset = CP932
-unix charset = CP932 / eucJP-ms / UTF-8
- | |
- | +-- EUC-JP series
- +-- Shift_JIS series
-display charset = CP932
-</programlisting>
-
- <para>
- Other Japanese locales (for example, Shift_JIS and EUC-JP) should not
- be used because of the lack of the compatibility with Windows.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry><term>GNU glibc</term>
- <listitem><para>
- To handle Japanese correctly, you should apply a <ulink url="http://www2d.biglobe.ne.jp/~msyk/software/glibc/">patch</ulink>
- to glibc-2.2.5/2.3.1/2.3.2 or should use the patch-merged versions, glibc-2.3.3 or later.
- </para>
-
- <para>
- Using the above glibc, these setting are available:
- <smbconfblock>
- <smbconfoption name="dos charset">CP932</smbconfoption>
- <smbconfoption name="unix charset">CP932 / eucJP-ms / UTF-8</smbconfoption>
- <smbconfoption name="display charset">CP932</smbconfoption>
- </smbconfblock>
- </para>
-
- <para>
- Other Japanese locales (for example, Shift_JIS and EUC-JP) should not
- be used because of the lack of the compatibility with Windows.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
-
-</sect2>
-
-<sect2>
- <title>Migration from Samba-2.2 Series</title>
-
-<para>
-Prior to Samba-2.2 series, the <quote>coding system</quote> parameter was used. The default codepage in Samba
-2.x was code page 850. In the Samba-3 series this has been replaced with the <smbconfoption name="unix
-charset"/> parameter. <link linkend="japancharsets">Japanese Character Sets in Samba-2.2 and Samba-3</link>
-shows the mapping table when migrating from the Samba-2.2 series to Samba-3.
-</para>
-
- <table frame="all" id="japancharsets">
- <title>Japanese Character Sets in Samba-2.2 and Samba-3</title>
-
- <tgroup cols="2" align="center">
- <colspec align="center"/>
- <colspec align="center"/>
- <thead>
- <row><entry>Samba-2.2 Coding System</entry><entry>Samba-3 unix charset</entry></row>
- </thead>
- <tbody>
- <row><entry>SJIS</entry><entry>Shift_JIS series</entry></row>
- <row><entry>EUC</entry><entry>EUC-JP series</entry></row>
- <row><entry>EUC3<footnote><para>Only exists in Japanese Samba version</para></footnote></entry><entry>EUC-JP series</entry></row>
- <row><entry>CAP</entry><entry>Shift_JIS series + VFS</entry></row>
- <row><entry>HEX</entry><entry>currently none</entry></row>
- <row><entry>UTF8</entry><entry>UTF-8</entry></row>
- <row><entry>UTF8-Mac<footnote><para>Only exists in Japanese Samba version</para></footnote></entry><entry>currently none</entry></row>
- <row><entry>others</entry><entry>none</entry></row>
- </tbody>
- </tgroup>
- </table>
-
-</sect2>
-
-</sect1>
-
-<sect1>
- <title>Common Errors</title>
-
- <sect2>
- <title>CP850.so Can't Be Found</title>
-
- <para><quote>Samba is complaining about a missing <filename>CP850.so</filename> file.</quote></para>
-
- <para>
- CP850 is the default <smbconfoption name="dos charset"/>.
- The <smbconfoption name="dos charset"/> is used to convert data to the codepage used by your DOS clients.
- If you do not have any DOS clients, you can safely ignore this message. </para>
-
- <para>
- CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed.
- If you compiled Samba from source, make sure that the configure process found iconv. This can be
- confirmed by checking the <filename>config.log</filename> file that is generated when
- <command>configure</command> is executed.</para>
- </sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="VFS">
-<chapterinfo>
- &author.jelmer;
- &author.jht;
- &author.tpot;
- <author><firstname>Simo</firstname><surname>Sorce</surname><contrib>original vfs_skel README</contrib></author>
- <author><firstname>Alexander</firstname><surname>Bokovoy</surname><contrib>original vfs_netatalk docs</contrib></author>
- <author><firstname>Stefan</firstname><surname>Metzmacher</surname><contrib>Update for multiple modules</contrib></author>
- <author><firstname>Ed</firstname><surname>Riddle</surname><contrib>original shadow_copy docs</contrib></author>
-</chapterinfo>
-<title>Stackable VFS modules</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>Virtual File System</primary><see>VFS</see></indexterm>
-<indexterm><primary>modules</primary></indexterm>
-<indexterm><primary>loaded modules</primary></indexterm>
-Stackable VFS (Virtual File System) modules support was new to Samba-3 and has proven quite popular. Samba
-passes each request to access the UNIX file system through the loaded VFS modules. This chapter covers the
-modules that come with the Samba source and provides references to some external modules.
-</para>
-
-
-</sect1>
-
-<sect1>
-<title>Discussion</title>
-
-<para>
-<indexterm><primary>IRIX</primary></indexterm>
-<indexterm><primary>GNU/Linux</primary></indexterm>
-If not supplied with your platform distribution binary Samba package, you may have problems compiling these
-modules, as shared libraries are compiled and linked in different ways on different systems.
-</para>
-
-<para>
-<indexterm><primary>VFS modules</primary></indexterm>
-<indexterm><primary>modules</primary></indexterm>
-<indexterm><primary>recycle bin</primary></indexterm>
-To use the VFS modules, create a share similar to the one below. The important parameter is the <smbconfoption
-name="vfs objects"/> parameter where you can list one or more VFS modules by name. For example, to log all
-access to files and put deleted files in a recycle bin, see <link linkend="vfsrecyc">the smb.conf with VFS
-modules example</link>:
-</para>
-
-<example id="vfsrecyc">
-<title>smb.conf with VFS modules</title>
-<smbconfblock>
-<smbconfsection name="[audit]"/>
-<smbconfoption name="comment">Audited /data directory</smbconfoption>
-<smbconfoption name="path">/data</smbconfoption>
-<smbconfoption name="vfs objects">audit recycle</smbconfoption>
-<smbconfoption name="writeable">yes</smbconfoption>
-<smbconfoption name="browseable">yes</smbconfoption>
-</smbconfblock>
-</example>
-
-<para>
-<indexterm><primary>virus scanner</primary></indexterm>
-<indexterm><primary>scanner module</primary></indexterm>
-<indexterm><primary>recycle bin</primary></indexterm>
-The modules are used in the order in which they are specified. Let's say that you want to both have a virus
-scanner module and a recycle bin module. It is wise to put the virus scanner module as the first one so that
-it is the first to get run and may detect a virus immediately, before any action is performed on that file.
-<smbconfoption name="vfs objects">vscan-clamav recycle</smbconfoption>
-</para>
-
-<para>
-<indexterm><primary>/usr/local/samba/lib/vfs</primary></indexterm>
-<indexterm><primary>/usr/lib/samba/vfs</primary></indexterm>
-Samba will attempt to load modules from the <filename>/lib</filename> directory in the root directory of the
-Samba installation (usually <filename>/usr/lib/samba/vfs</filename> or
-<filename>/usr/local/samba/lib/vfs</filename>).
-</para>
-
-<para>
-<indexterm><primary>modules</primary></indexterm>
-<indexterm><primary>VFS</primary></indexterm>
-<indexterm><primary>multiple modules</primary></indexterm>
-<indexterm><primary>multiple VFS</primary></indexterm>
-Some modules can be used twice for the same share. This can be done using a configuration similar to the one
-shown in <link linkend="multimodule">the smb.conf with multiple VFS modules</link>.
-
-<example id="multimodule">
-<title>smb.conf with multiple VFS modules</title>
-<smbconfblock>
-<smbconfsection name="[test]"/>
-<smbconfoption name="comment">VFS TEST</smbconfoption>
-<smbconfoption name="path">/data</smbconfoption>
-<smbconfoption name="writeable">yes</smbconfoption>
-<smbconfoption name="browseable">yes</smbconfoption>
-<smbconfoption name="vfs objects">example:example1 example example:test</smbconfoption>
-<smbconfoption name="example1: parameter">1</smbconfoption>
-<smbconfoption name="example: parameter">5</smbconfoption>
-<smbconfoption name="test: parameter">7</smbconfoption>
-</smbconfblock>
-</example>
-</para>
-
-</sect1>
-
-<sect1>
-<title>Included Modules</title>
-
- <sect2>
- <title>audit</title>
-
- <para>
-<indexterm><primary>audit file access</primary></indexterm>
- A simple module to audit file access to the syslog facility. The following operations are logged:
- <itemizedlist>
- <listitem><para>share</para></listitem>
- <listitem><para>connect/disconnect</para></listitem>
- <listitem><para>directory opens/create/remove</para></listitem>
- <listitem><para>file open/close/rename/unlink/chmod</para></listitem>
- </itemizedlist>
- </para>
-
- </sect2>
-
- <sect2>
- <title>default_quota</title>
-
- <para>
- This module allows the default quota values, in the windows explorer GUI, to be stored on a Samba server.
- The challenge is that linux filesystems only store quotas for users and groups, but no default quotas.
- </para>
-
- <para>
- Samba returns NO_LIMIT as the default quotas by default and refuses to update them. With this module you
- can store the default quotas that are reported to a windows client, in the quota record of a user. By
- default the root user is taken because quota limits for root are typically not enforced.
- </para>
-
- <para>
- This module takes 2 parametric entries in the &smb.conf; file. The default prefix for each is the
- <quote>default_quota</quote>. This can be overwrittem when you load the module in the <emphasis>vfs
- modules</emphasis> parameter like this:
-<screen>
-vfs objects = default_quota:myprefix
-</screen>
- </para>
-
- <para>
- The parametric entries that may be specified for the default_quotas module are:
- </para>
-
- <variablelist>
- <varlistentry>
- <term>myprefix:uid</term>
- <listitem><para>
- This parameter takes a integer argument that specifies the uid of the quota record that will be
- used for storing the default user quotas.
- </para>
-
- <para>
- The default value is 0 (for root user). An example of use is:
-<screen>
-vfs objects = default_quota
-default_quota: uid = 65534
-</screen>
- The above demonstrates the case where the <constant>myprefix</constant> was omitted, thus the
- default prefix is the name of the module. When a <constant>myprefix</constant> parameter is
- specified the above can be re-written like this:
-<screen>
-vfs objects = default_quota:myprefix
-myprefix: uid = 65534
-</screen>
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>myprefix:uid nolimit</term>
- <listitem><para>
- This parameter takes a boolean argument that specifies if the stored default quota values also be
- reported for the user record, or if the value <constant>NO_LIMIT</constant> should be reported to
- the windows client for the user specified by the <parameter>prefix:uid</parameter> parameter.
- </para>
-
- <para>
- The default value is <constant>yes</constant> (which means to report NO_LIMIT). An example of use
- is shown here:
-<screen>
-vfs objects = default_quota:myprefix
-myprefix: uid nolimit = no
-</screen>
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>myprefix:gid</term>
- <listitem><para>
- This parameter takes an integer argument, it's just like the <parameter>prefix>:uid</parameter> but
- for group quotas. NOTE: group quotas are not supported from the windows explorer.
- </para>
-
- <para>
- The default value is 0 (for root group). An example of use is shown here:
-<screen>
-vfs objects = default_quota
-default_quota: gid = 65534
-</screen>
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>myprefix:gid nolimit</term>
- <listitem><para>
- This parameter takes a boolean argument, just like the <parameter>prefix>:uid nolimit</parameter>
- but for group quotas. NOTE: group quotas are not supported from the windows explorer.
- </para>
-
- <para>
- The default value is <constant>yes</constant> (which means to report NO_LIMIT). An example of use
- is shown here:
-<screen>
-vfs objects = default_quota
-default_quota: uid nolimit = no
-</screen>
- </para></listitem>
- </varlistentry>
- </variablelist>
-
- <para>
- An example of use of multiple parametric specifications is shown here:
-<screen>
-...
-vfs objects = default_quota:quotasettings
-quotasettings: uid nolimit = no
-quotasettings: gid = 65534
-quotasettings: gid nolimit = no
-...
-</screen>
- </para>
-
- </sect2>
-
- <sect2>
- <title>extd_audit</title>
-
- <para>
-<indexterm><primary>audit module</primary></indexterm>
-<indexterm><primary>extd_audit module</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
- This module is identical with the <command>audit</command> module above except
- that it sends audit logs to both syslog as well as the <command>smbd</command> log files. The
- <smbconfoption name="log level"/> for this module is set in the &smb.conf; file.
- </para>
-
- <para>
- Valid settings and the information that will be recorded are shown in <link linkend="xtdaudit">the next table</link>.
- </para>
-
- <table frame="all" id="xtdaudit">
- <title>Extended Auditing Log Information</title>
- <tgroup cols="2" align="center">
- <thead>
- <row><entry align="center">Log Level</entry><entry>Log Details - File and Directory Operations</entry></row>
- </thead>
- <tbody>
- <row><entry align="center">0</entry><entry align="left">Make Directory, Remove Directory, Unlink</entry></row>
- <row><entry align="center">1</entry><entry align="left">Open Directory, Rename File, Change Permissions/ACLs</entry></row>
- <row><entry align="center">2</entry><entry align="left">Open & Close File</entry></row>
- <row><entry align="center">10</entry><entry align="left">Maximum Debug Level</entry></row>
- </tbody>
- </tgroup>
- </table>
-
- <sect3>
- <title>Configuration of Auditing</title>
-
- <para>
-<indexterm><primary>logging</primary></indexterm>
- This auditing tool is more flexible than most people will readily recognize. There are a number of ways
- by which useful logging information can be recorded.
- </para>
-
- <itemizedlist>
- <listitem><para>Syslog can be used to record all transaction. This can be disabled by setting
- in the &smb.conf; file <parameter>syslog = 0</parameter>.</para></listitem>
- <listitem><para>Logging can take place to the default log file (<filename>log.smbd</filename>)
- for all loaded VFS modules just by setting in the &smb.conf; file
- <parameter>log level = 0 vfs:x</parameter>, where x is the log level.
- This will disable general logging while activating all logging of VFS
- module activity at the log level specified.</para></listitem>
- <listitem><para>Detailed logging can be obtained per user, per client machine, etc.
- This requires the above together with the creative use of the
- <parameter>log file</parameter> settings.</para>
- <para>An example of detailed per-user and per-machine logging can
- be obtained by setting
- <smbconfoption name="log file">/var/log/samba/%U.%m.log</smbconfoption>.
- </para></listitem>
- </itemizedlist>
-
- <para>
- Auditing information often must be preserved for a long time. So that the log files do not get rotated
- it is essential that the <smbconfoption name="max log size">0</smbconfoption> be set
- in the &smb.conf; file.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2 id="fakeperms">
- <title>fake_perms</title>
-
- <para>
-<indexterm><primary>fake_perms</primary></indexterm>
-<indexterm><primary>Roaming Profile</primary></indexterm>
-<indexterm><primary>writeable</primary></indexterm>
-<indexterm><primary>read only</primary></indexterm>
- This module was created to allow Roaming Profile files and directories to be set (on the Samba server
- under UNIX) as read only. This module will, if installed on the Profiles share, report to the client
- that the Profile files and directories are writeable. This satisfies the client even though the files
- will never be overwritten as the client logs out or shuts down.
- </para>
-
- </sect2>
-
- <sect2>
- <title>recycle</title>
-
- <para>
-<indexterm><primary>recycle</primary></indexterm>
-<indexterm><primary>unlink calls</primary></indexterm>
-<indexterm><primary>recycle directory</primary></indexterm>
- A Recycle Bin-like module. Where used, unlink calls will be intercepted and files moved
- to the recycle directory instead of being deleted. This gives the same effect as the
- <guiicon>Recycle Bin</guiicon> on Windows computers.
- </para>
-
- <para>
-<indexterm><primary>recycle</primary></indexterm>
-<indexterm><primary>.recycle</primary></indexterm>
-<indexterm><primary>recycle:keeptree</primary></indexterm>
-<indexterm><primary>deleted files</primary></indexterm>
- The <guiicon>Recycle Bin</guiicon> will not appear in
- <application>Windows Explorer</application> views of the network
- file system (share) nor on any mapped drive. Instead, a directory
- called <filename>.recycle</filename> will be automatically created
- when the first file is deleted and <parameter>recycle:repository</parameter>
- is not configured.
- If <parameter>recycle:repository</parameter> is configured, the name
- of the created directory depends on <parameter>recycle:repository</parameter>.
- Users can recover files from the recycle bin. If the
- <parameter>recycle:keeptree</parameter> has been specified, deleted
- files will be found in a path identical with that from which the
- file was deleted.
- </para>
-
- <para>Supported options for the <command>recycle</command> module are as follow:
- <variablelist>
- <varlistentry>
- <term>recycle:repository</term>
- <listitem><para>
-<indexterm><primary>recycle:repository</primary></indexterm>
- Path of the directory where deleted files should be moved.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:directory_mode</term>
- <listitem><para>
-<indexterm><primary>directory_mode</primary></indexterm>
- Set it to the octal mode you want for the recycle directory. With
- this mode the recycle directory will be created if it not
- exists and the first file is deleted.
- If <parameter>recycle:subdir_mode</parameter> is not set, these
- mode also apply to sub directories.
- If <parameter>directory_mode</parameter> not exists, the default
- mode 0700 is used.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:subdir_mode</term>
- <listitem><para>
-<indexterm><primary>recycle:subdir_mode</primary></indexterm>
- Set it to the octal mode you want for the sub directories of
- the recycle directory. With this mode the sub directories will
- be created.
- If <parameter>recycle:subdir_mode</parameter> is not set, the
- sub directories will be created with the mode from
- <parameter>directory_mode</parameter>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:keeptree</term>
- <listitem><para>
-<indexterm><primary>recycle:keeptree</primary></indexterm>
- Specifies whether the directory structure should be kept or if the files in the directory that is being
- deleted should be kept separately in the recycle bin.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:versions</term>
- <listitem><para>
-<indexterm><primary>recycle:versions</primary></indexterm>
- If this option is set, two files
- with the same name that are deleted will both
- be kept in the recycle bin. Newer deleted versions
- of a file will be called <quote>Copy #x of <replaceable>filename</replaceable></quote>.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:touch</term>
- <listitem><para>
-<indexterm><primary>recycle:touch</primary></indexterm>
- Specifies whether a file's access date should be touched when the file is moved to the recycle bin.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:touch_mtime</term>
- <listitem><para>
-<indexterm><primary>recycle:touch</primary></indexterm>
- Specifies whether a file's last modify date date should be touched when the file is moved to the recycle bin.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:maxsize</term>
- <listitem><para>
-<indexterm><primary>recycle:maxsize</primary></indexterm>
- Files that are larger than the number of bytes specified by this parameter will not be put into the recycle bin.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:exclude</term>
- <listitem><para>
-<indexterm><primary>recycle:exclude</primary></indexterm>
- List of files that should not be put into the recycle bin when deleted, but deleted in the regular way.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:exclude_dir</term>
- <listitem><para>
-<indexterm><primary>recycle:exclude_dir</primary></indexterm>
- Contains a list of directories. When files from these directories are
- deleted, they are not put into the
- recycle bin but are deleted in the
- regular way.
- </para></listitem>
- </varlistentry>
-
- <varlistentry>
- <term>recycle:noversions</term>
- <listitem><para>
-<indexterm><primary>recycle:noversions</primary></indexterm>
- Specifies a list of paths (wildcards such as * and ? are supported) for which no versioning
- should be used. Only useful when <emphasis>recycle:versions</emphasis> is enabled.
- </para></listitem>
- </varlistentry>
- </variablelist>
- </para>
-
- </sect2>
-
- <sect2>
- <title>netatalk</title>
-
- <para>
-<indexterm><primary>netatalk</primary></indexterm>
- A netatalk module will ease co-existence of Samba and netatalk file sharing services.
- </para>
-
- <para>Advantages compared to the old netatalk module:
- <itemizedlist>
-<indexterm><primary>.AppleDouble</primary></indexterm>
- <listitem><para>Does not care about creating .AppleDouble forks, just keeps them in sync.</para></listitem>
- <listitem><para>If a share in &smb.conf; does not contain .AppleDouble item in hide or veto list, it will be added automatically.</para></listitem>
- </itemizedlist>
- </para>
-
- </sect2>
-
- <sect2>
- <title>shadow_copy</title>
-
- <warning><para>
-<indexterm><primary>shadow_copy</primary></indexterm>
- <emphasis>THIS IS NOT A BACKUP, ARCHIVAL, OR VERSION CONTROL SOLUTION!</emphasis>
- </para>
-
- <para>
-<indexterm><primary>version control</primary></indexterm>
- With Samba or Windows servers, shadow_copy is designed to be an end-user tool only. It does not replace or
- enhance your backup and archival solutions and should in no way be considered as such. Additionally, if you
- need version control, implement a version control system. You have been warned.
- </para></warning>
-
-
- <para>
- The shadow_copy module allows you to setup functionality that is similar to MS shadow copy services. When
- setup properly, this module allows Microsoft shadow copy clients to browse "shadow copies" on Samba shares.
- You will need to install the shadow copy client. You can get the MS shadow copy client <ulink noescape="1"
- url="http://www.microsoft.com/windowsserver2003/downloads/shadowcopyclient.mspx">here.</ulink>. Note the
- additional requirements for pre-Windows XP clients. I did not test this functionality with any pre-Windows XP
- clients. You should be able to get more information about MS Shadow Copy <ulink noescape="1"
- url="http://www.microsoft.com/windowsserver2003/techinfo/overview/scr.mspx">from the Microsoft's site</ulink>.
- </para>
-
- <para>
-<indexterm><primary>shadow_copy</primary></indexterm>
-<indexterm><primary>VFS module</primary></indexterm>
-<indexterm><primary>shadow_copy module</primary></indexterm>
-<indexterm><primary>LVM</primary></indexterm>
-<indexterm><primary>EVMS</primary></indexterm>
-<indexterm><primary>Logical Volume Manager</primary><see>LVM</see></indexterm>
- The shadow_copy VFS module requires some underlying file system setup with some sort of Logical Volume Manager
- (LVM) such as LVM1, LVM2, or EVMS. Setting up LVM is beyond the scope of this document; however, we will
- outline the steps we took to test this functionality for <emphasis>example purposes only.</emphasis> You need
- to make sure the LVM implementation you choose to deploy is ready for production. Make sure you do plenty of
- tests.
- </para>
-
- <para>
- Here are some common resources for LVM and EVMS:
- </para>
-
- <itemizedlist>
- <listitem>
- <para><ulink noescape="1"
- url="http://www.sistina.com/products_lvm_download.htm">Sistina's
- LVM1 and LVM2</ulink></para>
- </listitem>
- <listitem>
- <para><ulink url="http://evms.sourceforge.net/">Enterprise Volume Management System (EVMS)</ulink></para>
- </listitem>
- <listitem>
- <para><ulink url="http://tldp.org/HOWTO/LVM-HOWTO/">The LVM HOWTO</ulink></para>
- </listitem>
- <listitem>
- <para>
- See <ulink url="http://www-106.ibm.com/developerworks/linux/library/l-lvm/">Learning
- Linux LVM, Part 1</ulink> and <ulink url="http://www-106.ibm.com/developerworks/library/l-lvm2.html">Learning
- Linux LWM, Part 2</ulink> for Daniel Robbins' well-written, two part tutorial on Linux and LVM using LVM
- source code and reiserfs.</para>
- </listitem>
- </itemizedlist>
-
- <sect3>
- <title>Shadow Copy Setup</title>
- <para>
-<indexterm><primary>XFS file system</primary></indexterm>
-<indexterm><primary>Debian Sarge</primary></indexterm>
- At the time of this writing, not much testing has been done. I tested the shadow copy VFS module with a
- specific scenario which was not deployed in a production environment, but more as a proof of concept. The
- scenario involved a Samba file server on Debian Sarge with an XFS file system and LVM1. I do NOT recommend
- you use this as a solution without doing your own due diligence with regard to all the components presented
- here. That said, following is an basic outline of how I got things going.
- </para>
-
- <orderedlist>
- <listitem>
- <formalpara><title>Installed Operating System </title>
- <para>
- In my tests, I used <ulink url="http://www.debian.org/devel/debian-installer/">Debian
- Sarge</ulink> (i.e., testing) on an XFS file system. Setting up the OS is a bit beyond the scope of this
- document. It is assumed that you have a working OS capable of running Samba.
- </para></formalpara>
- </listitem>
-
- <listitem>
- <formalpara><title>Install & Configure Samba</title>
- <para>
- See the <link linkend="introduction">installation section</link> of this HOWTO for more detail on this.
- It doesn't matter if it is a Domain Controller or Member File Server, but it is assumed that you have a
- working Samba 3.0.3 or later server running.
- </para></formalpara>
- </listitem>
-
- <listitem>
- <formalpara><title>Install & Configure LVM</title>
- <para>
-<indexterm><primary>shadow copies</primary></indexterm>
-<indexterm><primary>Snapshots</primary></indexterm>
- Before you can make shadow copies available to the client, you have to create the shadow copies. This is
- done by taking some sort of file system snapshot. Snapshots are a typical feature of Logical Volume
- Managers such as LVM, so we first need to have that setup.
- </para></formalpara>
-
- <itemizedlist>
- <para>
- The following is provided as an example and will be most helpful for Debian users. Again, this was tested
- using the "testing" or "Sarge" distribution.
- </para>
-
- <listitem>
- <para>
-<indexterm><primary>lvm10 package</primary></indexterm>
-<indexterm><primary>devfsd package</primary></indexterm>
-<indexterm><primary>Debian</primary></indexterm>
-<indexterm><primary>xfsprogs</primary></indexterm>
-<indexterm><primary>apt-get</primary></indexterm>
- Install lvm10 and devfsd packages if you have not done so already. On Debian systems, you are warned of the
- interaction of devfs and lvm1 which requires the use of devfs filenames. Running <command>apt-get update
- && apt-get install lvm10 devfsd xfsprogs</command> should do the trick for this example.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>create volume</primary></indexterm>
-<indexterm><primary>create partition</primary></indexterm>
-<indexterm><primary>fdisk</primary></indexterm>
-<indexterm><primary>cfdisk</primary></indexterm>
-<indexterm><primary>Linux LVM</primary></indexterm>
- Now you need to create a volume. You will need to create a partition (or partitions) to add to your volume.
- Use your favorite partitioning tool (e.g., Linux fdisk, cfdisk, etc.). The partition type should be set to
- 0x8e for "Linux LVM." In this example, we will use /dev/hdb1.
- </para>
-
- <para>
-<indexterm><primary>Linux LVM partition</primary></indexterm>
-<indexterm><primary>LVM volume</primary></indexterm>
-<indexterm><primary>modprobe</primary></indexterm>
- Once you have the Linux LVM partition (type 0x8e), you can run a series of commands to create the LVM volume.
- You can use several disks and/or partitions, but we will use only one in this example. You may also need to
- load the kernel module with something like <command>modprobe lvm-mod</command> and set your system up to load
- it on reboot by adding it to (<filename>/etc/modules</filename>).
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>pvcreate</primary></indexterm>
- Create the physical volume with <command>pvcreate /dev/hdb1</command>
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>vgcreate</primary></indexterm>
-<indexterm><primary>volume group</primary></indexterm>
- Create the volume group and add /dev/hda1 to it with <command>vgcreate shadowvol /dev/hdb1</command>
- </para>
-
- <para>
-<indexterm><primary>vgdisplay</primary></indexterm>
- You can use <command>vgdisplay</command> to review information about the volume group.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>lvcreate</primary></indexterm>
- Now you can create the logical volume with something like <command>lvcreate -L400M -nsh_test shadowvol</command>
- </para>
-
- <para>
-<indexterm><primary>/dev/shadowvol</primary></indexterm>
- This creates the logical volume of 400 MBs named "sh_test" in the volume group we created called shadowvol.
- If everything is working so far, you should see them in <filename>/dev/shadowvol</filename>.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>mkfs.xfs</primary></indexterm>
- Now we should be ready to format the logical volume we named sh_test with <command>mkfs.xfs
- /dev/shadowvol/sh_test</command>
- </para>
-
- <para>
-<indexterm><primary>logical volume</primary></indexterm>
-<indexterm><primary>LVM</primary></indexterm>
-<indexterm><primary>freezing</primary></indexterm>
-<indexterm><primary>resizing</primary></indexterm>
-<indexterm><primary>growing</primary></indexterm>
- You can format the logical volume with any file system you choose, but make sure to use one that allows you to
- take advantage of the additional features of LVM such as freezing, resizing, and growing your file systems.
- </para>
-
- <para>
-<indexterm><primary>LVM volume</primary></indexterm>
-<indexterm><primary>shadow_copy</primary></indexterm>
-<indexterm><primary>module</primary></indexterm>
- Now we have an LVM volume where we can play with the shadow_copy VFS module.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>mkdir</primary></indexterm>
-<indexterm><primary>permissions</primary></indexterm>
-<indexterm><primary>chmod</primary></indexterm>
- Now we need to prepare the directory with something like
-<screen>
-&rootprompt; mkdir -p /data/shadow_share
-</screen>
- or whatever you want to name your shadow copy-enabled Samba share. Make sure you set the permissions so that
- you can use it. If in doubt, use <command>chmod 777 /data/shadow_share</command> and tighten the permissions
- once you get things working.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>mount</primary></indexterm>
- Mount the LVM volume using something like <command>mount /dev/shadowvol/sh_test /data/shadow_share</command>
- </para>
-
- <para>
-<indexterm><primary>/etc/fstab</primary></indexterm>
- You may also want to edit your <filename>/etc/fstab</filename> so that this partition mounts during the system boot.
- </para></listitem>
- </itemizedlist>
-
- </listitem>
-
- <listitem>
- <formalpara><title>Install & Configure the shadow_copy VFS Module</title>
- <para>
- Finally we get to the actual shadow_copy VFS module. The shadow_copy VFS module should be available in Samba
- 3.0.3 and higher. The smb.conf configuration is pretty standard. Here is our example of a share configured
- with the shadow_copy VFS module:
- </para></formalpara>
-
- <example id="vfsshadow">
- <title>Share With shadow_copy VFS</title>
- <smbconfblock>
- <smbconfsection name="[shadow_share]"/>
- <smbconfoption name="comment">Shadow Copy Enabled Share</smbconfoption>
- <smbconfoption name="path">/data/shadow_share</smbconfoption>
- <smbconfoption name="vfs objects">shadow_copy</smbconfoption>
- <smbconfoption name="writeable">yes</smbconfoption>
- <smbconfoption name="browseable">yes</smbconfoption>
- </smbconfblock>
- </example>
-
- </listitem>
-
- <listitem>
- <formalpara><title>Create Snapshots and Make Them Available to shadow_copy.so</title>
- <para>
-<indexterm><primary>shadow_copy</primary></indexterm>
-<indexterm><primary>LVM snapshots</primary></indexterm>
-<indexterm><primary>module</primary></indexterm>
- Before you can browse the shadow copies, you must create them and mount them. This will most likely be done
- with a script that runs as a cron job. With this particular solution, the shadow_copy VFS module is used to
- browse LVM snapshots. Those snapshots are not created by the module. They are not made available by the
- module either. This module allows the shadow copy-enabled client to browse the snapshots you take and make
- available.
- </para></formalpara>
-
- <para>
- Here is a simple script used to create and mount the snapshots:
-<screen>
-#!/bin/bash
-# This is a test, this is only a test
-SNAPNAME=`date +%Y.%m.%d-%H.%M.%S`
-xfs_freeze -f /data/shadow_share/
-lvcreate -L10M -s -n $SNAPNAME /dev/shadowvol/sh_test
-xfs_freeze -u /data/shadow_share/
-mkdir /data/shadow_share/@GMT-$SNAPNAME
-mount /dev/shadowvol/$SNAPNAME \
- /data/shadow_share/@GMT-$SNAPNAME -onouuid,ro
-</screen>
- Note that the script does not handle other things like remounting snapshots on reboot.
- </para></listitem>
-
- <listitem>
- <formalpara><title>Test From Client</title>
- <para>
- To test, you will need to install the shadow copy client which you can obtain from the <ulink
- url="http://www.microsoft.com/windowsserver2003/downloads/shadowcopyclient.mspx">Microsoft web site.</ulink> I
- only tested this with an XP client so your results may vary with other pre-XP clients. Once installed, with
- your XP client you can right-click on specific files or in the empty space of the shadow_share and view the
- "properties." If anything has changed, then you will see it on the "Previous Versions" tab of the properties
- window.
- </para></formalpara>
- </listitem>
- </orderedlist>
-
- </sect3>
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>VFS Modules Available Elsewhere</title>
-
-<para>
-<indexterm><primary>VFS modules</primary></indexterm>
-This section contains a listing of various other VFS modules that have been posted but do not currently reside
-in the Samba CVS tree for one reason or another (e.g., it is easy for the maintainer to have his or her own
-CVS tree).
-</para>
-
-<para>
-No statements about the stability or functionality of any module should be implied due to its presence here.
-</para>
-
-<sect2>
-<title>DatabaseFS</title>
-
-<para>
-<indexterm><primary>DatabaseFS</primary></indexterm>
-URL: <ulink noescape="1" url="http://www.css.tayloru.edu/~elorimer/databasefs/index.php">
-Taylors University DatabaeFS</ulink>
-</para>
-
-<para>By <ulink url="mailto:elorimer@css.tayloru.edu">Eric Lorimer.</ulink></para>
-
-<para>
-I have created a VFS module that implements a fairly complete read-only filesystem. It presents information
-from a database as a filesystem in a modular and generic way to allow different databases to be used.
-(Originally designed for organizing MP3s under directories such as <quote>Artists,</quote> <quote>Song
-Keywords,</quote> and so on. I have since easily applied it to a student roster database.) The directory
-structure is stored in the database itself and the module makes no assumptions about the database structure
-beyond the table it requires to run.
-</para>
-
-<para>
-Any feedback would be appreciated: comments, suggestions, patches, and so on. If nothing else, it
-might prove useful for someone else who wishes to create a virtual filesystem.
-</para>
-
-</sect2>
-
-<sect2>
-<title>vscan</title>
-
-<indexterm><primary>vscan</primary></indexterm>
-<para>URL: <ulink noescape="1" url="http://www.openantivirus.org/projects.php#samba-vscan">
-Open Anti-Virus vscan</ulink>
-</para>
-
-<para>
-<indexterm><primary>samba-vscan</primary></indexterm>
-samba-vscan is a proof-of-concept module for Samba, which provides on-access anti-virus support for files
-shared using Samba. samba-vscan supports various virus scanners and is maintained by Rainer Link.
-</para>
-
-</sect2>
-
-<sect2>
-<title>vscan-clamav</title>
-<para>
-Samba users have been using the RPMS from SerNet without a problem.
-OpenSUSE Linux users have also used the vscan scanner for quite some time
-with excellent results. It does impact overall write performance though.
-</para>
-
-<para>
-The following share stanza is a good guide for those wanting to configure vscan-clamav:
-</para>
-
-<screen>
-[share]
-vfs objects = vscan-clamav
-vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
-</screen>
-
-<para>
-The following example of the <filename>vscan-clamav.conf</filename> file may help to get this
-fully operational:
-</para>
-
-<screen>
-<title>VFS: Vscan ClamAV Control File</title>
-#
-# /etc/samba/vscan-clamav.conf
-#
-
-[samba-vscan]
-; run-time configuration for vscan-samba using
-; clamd
-; all options are set to default values
-
-; do not scan files larger than X bytes. If set to 0 (default),
-; this feature is disable (i.e. all files are scanned)
-max file size = 10485760
-
-; log all file access (yes/no). If set to yes, every access will
-; be logged. If set to no (default), only access to infected files
-; will be logged
-verbose file logging = no
-
-; if set to yes (default), a file will be scanned while opening
-scan on open = yes
-; if set to yes, a file will be scanned while closing (default is yes)
-scan on close = yes
-
-; if communication to clamd fails, should access to file denied?
-; (default: yes)
-deny access on error = no
-
-; if daemon failes with a minor error (corruption, etc.),
-; should access to file denied?
-; (default: yes)
-deny access on minor error = no
-
-; send a warning message via Windows Messenger service
-; when virus is found?
-; (default: yes)
-send warning message = yes
-
-; what to do with an infected file
-; quarantine: try to move to quantine directory
-; delete: delete infected file
-; nothing: do nothing (default)
-infected file action = quarantine
-
-; where to put infected files - you really want to change this!
-quarantine directory = /opt/clamav/quarantine
-; prefix for files in quarantine
-quarantine prefix = vir-
-
-; as Windows tries to open a file multiple time in a (very) short time
-; of period, samba-vscan use a last recently used file mechanism to avoid
-; multiple scans of a file. This setting specified the maximum number of
-; elements of the last recently used file list. (default: 100)
-max lru files entries = 100
-
-; an entry is invalidad after lru file entry lifetime (in seconds).
-; (Default: 5)
-lru file entry lifetime = 5
-
-; exclude files from being scanned based on the MIME-type! Semi-colon
-; separated list (default: empty list). Use this with care!
-exclude file types =
-
-; socket name of clamd (default: /var/run/clamd). Setting will be ignored if
-; libclamav is used
-clamd socket name = /tmp/clamd
-
-; limits, if vscan-clamav was build for using the clamav library (libclamav)
-; instead of clamd
-
-; maximum number of files in archive (default: 1000)
-libclamav max files in archive = 1000
-
-; maximum archived file size, in bytes (default: 10 MB)
-libclamav max archived file size = 5242880
-
-; maximum recursion level (default: 5)
-libclamav max recursion level = 5
-</screen>
-
-<para>
-Obviously, a running clam daemon is necessary for this to work. This is a working example for me using ClamAV.
-The ClamAV documentation should provide additional configuration examples. On your system these may be located
-under the <filename>/usr/share/doc/</filename> directory. Some examples may also target other virus scanners,
-any of which can be used.
-</para>
-
-</sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="winbind">
-
-<chapterinfo>
- <author>
- <firstname>Tim</firstname><surname>Potter</surname>
- <affiliation>
- <orgname>Samba Team</orgname>
- <address><email>tpot@linuxcare.com.au</email></address>
- </affiliation>
- </author>
- &author.tridge;
- <author>
- <firstname>Naag</firstname><surname>Mummaneni</surname>
- <affiliation>
- <address><email>getnag@rediffmail.com</email></address>
- </affiliation>
- <contrib>Notes for Solaris</contrib>
- </author>
- <author>
- <firstname>John</firstname><surname>Trostel</surname>
- <affiliation>
- <orgname>SNAP</orgname>
- <address><email>jtrostel@snapserver.com</email></address>
- </affiliation>
- </author>
- &author.jelmer;
- &author.jht;
- <pubdate>June 15, 2005</pubdate>
-</chapterinfo>
-
-<title>Winbind: Use of Domain Accounts</title>
-
-<sect1>
- <title>Features and Benefits</title>
-
- <para>
-<indexterm><primary>holy grail</primary></indexterm>
-<indexterm><primary>heterogeneous computing</primary></indexterm>
- Integration of UNIX and Microsoft Windows NT through a unified logon has
- been considered a <quote>holy grail</quote> in heterogeneous computing environments for
- a long time.
- </para>
-
- <para>
-<indexterm><primary>interoperability</primary></indexterm>
-<indexterm><primary>domain user</primary></indexterm>
-<indexterm><primary>domain group</primary></indexterm>
-<indexterm><primary>group ownership</primary></indexterm>
- There is one other facility without which UNIX and Microsoft Windows network
- interoperability would suffer greatly. It is imperative that there be a
- mechanism for sharing files across UNIX systems and to be able to assign
- domain user and group ownerships with integrity.
- </para>
-
- <para>
-<indexterm><primary>Pluggable Authentication Modules</primary><see>PAM</see></indexterm>
-<indexterm><primary>winbind</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>RPC</primary></indexterm>
- <emphasis>winbind</emphasis> is a component of the Samba suite of programs that
- solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft
- RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to
- allow Windows NT domain users to appear and operate as UNIX users on a UNIX
- machine. This chapter describes the Winbind system, the functionality
- it provides, how it is configured, and how it works internally.
- </para>
-
- <para>
- Winbind provides three separate functions:
- </para>
-
- <itemizedlist>
- <listitem><para>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>NT4 domain</primary></indexterm>
- Authentication of user credentials (via PAM). This makes it possible to
- log onto a UNIX/Linux system using user and group accounts from a Windows
- NT4 (including a Samba domain) or an Active Directory domain.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>identity resolution</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
- Identity resolution (via NSS). This is the default when winbind is not used.
- </para></listitem>
-
- <listitem><para>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
-<indexterm><primary>idmap uid</primary></indexterm>
-<indexterm><primary>idmap gid</primary></indexterm>
-<indexterm><primary>idmap backend</primary></indexterm>
- Winbind maintains a database called winbind_idmap.tdb in which it stores
- mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only
- for users and groups that do not have a local UID/GID. It stores the UID/GID
- allocated from the idmap uid/gid range that it has mapped to the NT SID.
- If <parameter>idmap backend</parameter> has been specified as <constant>ldap:ldap://hostname[:389]</constant>,
- then instead of using a local mapping, Winbind will obtain this information
- from the LDAP database.
- </para></listitem>
- </itemizedlist>
-
- <note><para>
- <indexterm><primary>winbindd</primary></indexterm>
- <indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>/etc/group</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
- If <command>winbindd</command> is not running, smbd (which calls <command>winbindd</command>) will fall back to
- using purely local information from <filename>/etc/passwd</filename> and <filename>/etc/group</filename> and no dynamic
- mapping will be used. On an operating system that has been enabled with the NSS,
- the resolution of user and group information will be accomplished via NSS.
- </para></note>
-
-
- <figure id="winbind_idmap">
- <title>Winbind Idmap</title>
- <imagefile scale="45">idmap_winbind_no_loop</imagefile>
- </figure>
-
-</sect1>
-
-
-<sect1>
- <title>Introduction</title>
-
- <para>It is well known that UNIX and Microsoft Windows NT have
- different models for representing user and group information and
- use different technologies for implementing them. This fact has
- made it difficult to integrate the two systems in a satisfactory
- manner.</para>
-
- <para>
-<indexterm><primary>synchronization problems</primary></indexterm>
-<indexterm><primary>passwords</primary></indexterm>
- One common solution in use today has been to create
- identically named user accounts on both the UNIX and Windows systems
- and use the Samba suite of programs to provide file and print services
- between the two. This solution is far from perfect, however, because
- adding and deleting users on both sets of machines becomes a chore,
- and two sets of passwords are required &smbmdash; both of which
- can lead to synchronization problems between the UNIX and Windows
- systems and confusion for users.</para>
-
- <para>We divide the unified logon problem for UNIX machines into
- three smaller problems:</para>
-
- <itemizedlist>
- <listitem><para>Obtaining Windows NT user and group information.
- </para></listitem>
-
- <listitem><para>Authenticating Windows NT users.
- </para></listitem>
-
- <listitem><para>Password changing for Windows NT users.
- </para></listitem>
- </itemizedlist>
-
-
- <para>
-<indexterm><primary>unified logon</primary></indexterm>
-<indexterm><primary>duplication of information</primary></indexterm>
- Ideally, a prospective solution to the unified logon problem
- would satisfy all the above components without duplication of
- information on the UNIX machines and without creating additional
- tasks for the system administrator when maintaining users and
- groups on either system. The Winbind system provides a simple
- and elegant solution to all three components of the unified logon
- problem.</para>
-</sect1>
-
-
-<sect1>
- <title>What Winbind Provides</title>
-
- <para>
-<indexterm><primary>Windows account management</primary></indexterm>
-<indexterm><primary>UNIX users</primary></indexterm>
-<indexterm><primary>UNIX groups</primary></indexterm>
-<indexterm><primary>NT domain</primary></indexterm>
- Winbind unifies UNIX and Windows NT account management by
- allowing a UNIX box to become a full member of an NT domain. Once
- this is done, the UNIX box will see NT users and groups as if
- they were <quote>native</quote> UNIX users and groups, allowing the NT domain
- to be used in much the same manner that NIS+ is used within
- UNIX-only environments.</para>
-
- <para>
-<indexterm><primary>Winbind hooks</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>redirection</primary></indexterm>
- The end result is that whenever a
- program on the UNIX machine asks the operating system to look up
- a user or group name, the query will be resolved by asking the
- NT domain controller for the specified domain to do the lookup.
- Because Winbind hooks into the operating system at a low level
- (via the NSS name resolution modules in the C library), this
- redirection to the NT domain controller is completely
- transparent.</para>
-
- <para>
-<indexterm><primary>user and group</primary></indexterm>
-<indexterm><primary>domain user</primary></indexterm>
- Users on the UNIX machine can then use NT user and group
- names as they would <quote>native</quote> UNIX names. They can chown files
- so they are owned by NT domain users or even login to the
- UNIX machine and run a UNIX X Window session as a domain user.</para>
-
- <para>
-<indexterm><primary>domain controller</primary></indexterm>
- The only obvious indication that Winbind is being used is
- that user and group names take the form <constant>DOMAIN\user</constant> and
- <constant>DOMAIN\group</constant>. This is necessary because it allows Winbind to determine
- that redirection to a domain controller is wanted for a particular
- lookup and which trusted domain is being referenced.</para>
-
- <para>
-<indexterm><primary>PAM-enabled</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
- Additionally, Winbind provides an authentication service that hooks into the PAM system
- to provide authentication via an NT domain to any PAM-enabled
- applications. This capability solves the problem of synchronizing
- passwords between systems, since all passwords are stored in a single
- location (on the domain controller).</para>
-
- <sect2>
- <title>Target Uses</title>
-
- <para>
-<indexterm><primary>infrastructure</primary></indexterm>
- Winbind is targeted at organizations that have an
- existing NT-based domain infrastructure into which they wish
- to put UNIX workstations or servers. Winbind will allow these
- organizations to deploy UNIX workstations without having to
- maintain a separate account infrastructure. This greatly
- simplifies the administrative overhead of deploying UNIX
- workstations into an NT-based organization.</para>
-
- <para>
-<indexterm><primary>Appliances</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
- Another interesting way in which we expect Winbind to
- be used is as a central part of UNIX-based appliances. Appliances
- that provide file and print services to Microsoft-based networks
- will be able to use Winbind to provide seamless integration of
- the appliance into the domain.</para>
- </sect2>
-
- <sect2>
- <title>Handling of Foreign SIDs</title>
-
- <para>
-<indexterm><primary>foreign SID</primary></indexterm>
- The term <emphasis>foreign SID</emphasis> is often met with the reaction that it
- is not relevant to a particular environment. The following documents an interchange
- that took place on the Samba mailing list. It is a good example of the confusion
- often expressed regarding the use of winbind.
- </para>
-
- <para>
-<indexterm><primary>local domain</primary></indexterm>
- Fact: Winbind is needed to handle users who use workstations that are NOT part
- of the local domain.
- </para>
-
- <para>
-<indexterm><primary>PDC</primary></indexterm>
- Response: <quote>Why? I've used Samba with workstations that are not part of my domains
- lots of times without using winbind. I thought winbind was for using Samba as a member server
- in a domain controlled by another Samba/Windows PDC.</quote>
- </para>
-
- <para>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>foreign user</primary></indexterm>
- If the Samba server will be accessed from a domain other than the local Samba domain, or
- if there will be access from machines that are not local domain members, winbind will
- permit the allocation of UIDs and GIDs from the assigned pool that will keep the identity
- of the foreign user separate from users that are members of the Samba domain.
- </para>
-
- <para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>domain non-member</primary></indexterm>
-<indexterm><primary>SID</primary></indexterm>
- This means that winbind is eminently useful in cases where a single
- Samba PDC on a local network is combined with both domain member and domain non-member workstations.
- If winbind is not used, the user george on a Windows workstation that is not a domain
- member will be able to access the files of a user called george in the account database
- of the Samba server that is acting as a PDC. When winbind is used, the default condition
- is that the local user george will be treated as the account DOMAIN\george and the
- foreign (non-member of the domain) account will be treated as MACHINE\george because
- each has a different SID.
- </para>
-
- </sect2>
-</sect1>
-
-
-
-<sect1>
- <title>How Winbind Works</title>
-
- <para>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>UNIX domain socket</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
- The Winbind system is designed around a client/server
- architecture. A long-running <command>winbindd</command> daemon
- listens on a UNIX domain socket waiting for requests
- to arrive. These requests are generated by the NSS and PAM
- clients and are processed sequentially.</para>
-
- <para>The technologies used to implement Winbind are described
- in detail below.</para>
-
- <sect2>
- <title>Microsoft Remote Procedure Calls</title>
-
- <para>
-<indexterm><primary>Microsoft Remote Procedure Call</primary><see>MSRPC</see></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>remote management</primary></indexterm>
-<indexterm><primary>user authentication</primary></indexterm>
-<indexterm><primary>print spooling</primary></indexterm>
- Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of
- the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations
- between Windows NT machines, including remote management, user authentication, and print spooling. Although
- initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in
- Samba, it has also yielded a body of code that can be used for other purposes.
- </para>
-
- <para>
-<indexterm><primary>MSRPC</primary></indexterm>
-<indexterm><primary>enumerate domain users</primary></indexterm>
-<indexterm><primary>enumerate domain groups</primary></indexterm>
- Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about
- individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user
- passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account
- information onto UNIX user and group names.
- </para>
- </sect2>
-
- <sect2>
- <title>Microsoft Active Directory Services</title>
-
- <para>
-<indexterm><primary>LDAP</primary></indexterm>
-<indexterm><primary>Kerberos</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>native mode</primary></indexterm>
- Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its <quote>native
- mode</quote> protocols rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running
- Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing
- provide a much more efficient and effective Winbind implementation.
- </para>
- </sect2>
-
- <sect2>
- <title>Name Service Switch</title>
-
- <para>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>networked workstation</primary></indexterm>
-<indexterm><primary>NIS</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
- The NSS is a feature that is present in many UNIX operating systems. It allows system
- information such as hostnames, mail aliases, and user information
- to be resolved from different sources. For example, a standalone
- UNIX workstation may resolve system information from a series of
- flat files stored on the local file system. A networked workstation
- may first attempt to resolve system information from local files,
- and then consult an NIS database for user information or a DNS server
- for hostname information.</para>
-
- <para>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>MSRPC</primary></indexterm>
-<indexterm><primary>trusted domain</primary></indexterm>
-<indexterm><primary>local users</primary></indexterm>
-<indexterm><primary>local groups</primary></indexterm>
- The NSS application programming interface allows Winbind to present itself as a source of system
- information when resolving UNIX usernames and groups. Winbind uses this interface and information obtained
- from a Windows NT server using MSRPC calls to provide a new source of account enumeration. Using standard UNIX
- library calls, you can enumerate the users and groups on a UNIX machine running Winbind and see all users and
- groups in an NT domain plus any trusted domain as though they were local users and groups.
- </para>
-
- <para>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
-<indexterm><primary>passwd</primary></indexterm>
- The primary control file for NSS is <filename>/etc/nsswitch.conf</filename>. When a UNIX application
- makes a request to do a lookup, the C library looks in <filename>/etc/nsswitch.conf</filename> for a line that
- matches the service type being requested; for example, the <quote>passwd</quote> service type is used when
- user or group names are looked up. This config line specifies which implementations of that service should be
- tried and in what order. If the passwd config line is:
-<screen>
-passwd: files example
-</screen>
-<indexterm><primary>/lib/libnss_files.so</primary></indexterm>
-<indexterm><primary>/lib/libnss_example.so</primary></indexterm>
-<indexterm><primary>resolver functions</primary></indexterm>
- then the C library will first load a module called <filename>/lib/libnss_files.so</filename> followed
- by the module <filename>/lib/libnss_example.so</filename>. The C library will dynamically load each of these
- modules in turn and call resolver functions within the modules to try to resolve the request. Once the request
- is resolved, the C library returns the result to the application.
- </para>
-
- <para>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>libnss_winbind.so</primary></indexterm>
-<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
- This NSS interface provides an easy way for Winbind to hook into the operating system. All that needs
- to be done is to put <filename>libnss_winbind.so</filename> in <filename>/lib/</filename> then add
- <quote>winbind</quote> into <filename>/etc/nsswitch.conf</filename> at the appropriate place. The C library
- will then call Winbind to resolve user and group names.
- </para>
- </sect2>
-
- <sect2>
- <title>Pluggable Authentication Modules</title>
-
- <para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>authentication methods</primary></indexterm>
-<indexterm><primary>authorization</primary></indexterm>
-<indexterm><primary>NIS database</primary></indexterm>
- PAMs provide a system for abstracting authentication and authorization technologies. With a PAM
- module, it is possible to specify different authentication methods for different system applications without
- having to recompile these applications. PAM is also useful for implementing a particular policy for
- authorization. For example, a system administrator may only allow console logins from users stored in the
- local password file but only allow users resolved from an NIS database to log in over the network.
- </para>
-
- <para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>authentication management</primary></indexterm>
-<indexterm><primary>password management</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
- Winbind uses the authentication management and password management PAM interface to integrate Windows
- NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated
- against a suitable PDC. These users can also change their passwords and have this change take effect directly
- on the PDC.
- </para>
-
- <para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>/etc/pam.d/</primary></indexterm>
-<indexterm><primary>pam_winbind.so</primary></indexterm>
-<indexterm><primary>/lib/security/</primary></indexterm>
- PAM is configured by providing control files in the directory <filename>/etc/pam.d/</filename> for
- each of the services that require authentication. When an authentication request is made by an application,
- the PAM code in the C library looks up this control file to determine what modules to load to do the
- authentication check and in what order. This interface makes adding a new authentication service for Winbind
- very easy: simply copy the <filename>pam_winbind.so</filename> module to <filename>/lib/security/</filename>,
- and the PAM control files for relevant services are updated to allow authentication via Winbind. See the PAM
- documentation in <link linkend="pam">PAM-Based Distributed Authentication</link>, for more information.
- </para>
- </sect2>
-
- <sect2>
- <title>User and Group ID Allocation</title>
-
- <para>
-<indexterm><primary>RID</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>UNIX ID</primary></indexterm>
- When a user or group is created under Windows NT/200x, it is allocated a numerical relative identifier
- (RID). This is slightly different from UNIX, which has a range of numbers that are used to identify users and
- the same range used to identify groups. It is Winbind's job to convert RIDs to UNIX ID numbers and vice versa.
- When Winbind is configured, it is given part of the UNIX user ID space and a part of the UNIX group ID space
- in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is
- allocated the next UNIX ID from the range. The same process applies for Windows NT groups. Over time, Winbind
- will have mapped all Windows NT users and groups to UNIX user IDs and group IDs.
- </para>
-
- <para>
-<indexterm><primary>ID mapping database</primary></indexterm>
-<indexterm><primary>tdb</primary></indexterm>
-<indexterm><primary>UNIX ID</primary></indexterm>
-<indexterm><primary>RID</primary></indexterm>
- The results of this mapping are stored persistently in an ID mapping database held in a tdb database.
- This ensures that RIDs are mapped to UNIX IDs in a consistent way.
- </para>
- </sect2>
-
- <sect2>
- <title>Result Caching</title>
-
- <para>
-<indexterm><primary>SAM</primary></indexterm>
-<indexterm><primary>caching scheme</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>ADS</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
- An active directory system can generate a lot of user and group name lookups. To reduce the network
- cost of these lookups, Winbind uses a caching scheme based on the SAM sequence number supplied by NT domain
- controllers. User or group information returned by a PDC is cached by Winbind along with a sequence number
- also returned by the PDC. This sequence number is incremented by Windows NT whenever any user or group
- information is modified. If a cached entry has expired, the sequence number is requested from the PDC and
- compared against the sequence number of the cached entry. If the sequence numbers do not match, then the
- cached information is discarded and up-to-date information is requested directly from the PDC.
- </para>
- </sect2>
-</sect1>
-
-
-<sect1>
- <title>Installation and Configuration</title>
-
-<sect2>
-<title>Introduction</title>
-
-<para>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>authentication control</primary></indexterm>
-This section describes the procedures used to get Winbind up and running. Winbind is capable of providing
-access and authentication control for Windows Domain users through an NT or Windows 200x PDC for regular
-services, such as telnet and ftp, as well for Samba services.
-</para>
-
-<itemizedlist>
-<listitem>
- <para>
- <emphasis>Why should I do this?</emphasis>
- </para>
-
- <para>
-<indexterm><primary>Samba administrator</primary></indexterm>
-<indexterm><primary>authentication mechanisms</primary></indexterm>
-<indexterm><primary>domain members</primary></indexterm>
-<indexterm><primary>accounts</primary></indexterm>
-This allows the Samba administrator to rely on the authentication mechanisms on the Windows NT/200x PDC
-for the authentication of domain members. Windows NT/200x users no longer need to have separate accounts on
-the Samba server.
- </para>
-</listitem>
-
-<listitem>
- <para>
- <emphasis>Who should be reading this document?</emphasis>
- </para>
-
- <para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>Windows NT/200x</primary></indexterm>
-This document is designed for system administrators. If you are implementing Samba on a file server and wish
-to (fairly easily) integrate existing Windows NT/200x users from your PDC onto the Samba server, this document
-is for you.
- </para>
-</listitem>
-</itemizedlist>
-</sect2>
-
-
-<sect2>
-<title>Requirements</title>
-
-<para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>back up</primary></indexterm>
-<indexterm><primary>boot disk</primary></indexterm>
-If you have a Samba configuration file that you are currently using, <emphasis>BACK IT UP!</emphasis>
-If your system already uses PAM, <emphasis>back up the <filename>/etc/pam.d</filename> directory
-contents!</emphasis> If you haven't already made a boot disk, <emphasis>MAKE ONE NOW!</emphasis>
-</para>
-
-<para>
-<indexterm><primary>PAM configuration</primary></indexterm>
-<indexterm><primary>/etc/pam.d</primary></indexterm>
-<indexterm><primary>single-user mode</primary></indexterm>
-Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's
-why you want to be able to boot back into your machine in single-user mode and restore your
-<filename>/etc/pam.d</filename> to the original state it was in if you get frustrated with the
-way things are going.
-</para>
-
-<para>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>daemon</primary></indexterm>
-The latest version of Samba includes a functioning winbindd daemon. Please refer to the <ulink
-url="https://www.samba.org/">main Samba Web page</ulink>, or better yet, your closest Samba mirror site for
-instructions on downloading the source code.
-</para>
-
-<para>
-<indexterm><primary>domain users</primary></indexterm>
-<indexterm><primary>shares and files</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>development libraries</primary></indexterm>
-To allow domain users the ability to access Samba shares and files, as well as potentially other services
-provided by your Samba machine, PAM must be set up properly on your
-machine. In order to compile the Winbind modules, the PAM development libraries should be installed
-on your system. Please refer to the <ulink url="http://www.kernel.org/pub/linux/libs/pam/">PAM Web Site</ulink>.
-</para>
-</sect2>
-
-<sect2>
-<title>Testing Things Out</title>
-
-<para>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>/etc/pam.d</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
-Before starting, it is probably best to kill off all the Samba-related daemons running on your server.
-Kill off all &smbd;, &nmbd;, and &winbindd; processes that may be running. To use PAM,
-make sure that you have the standard PAM package that supplies the <filename>/etc/pam.d</filename>
-directory structure, including the PAM modules that are used by PAM-aware services, several PAM libraries,
-and the <filename>/usr/doc</filename> and <filename>/usr/man</filename> entries for PAM. Winbind is built
-better in Samba if the pam-devel package is also installed. This package includes the header files
-needed to compile PAM-aware applications.
-</para>
-
-<sect3>
-<title>Configure <filename>nsswitch.conf</filename> and the Winbind Libraries on Linux and Solaris</title>
-
-<para>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>pam-devel</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
-PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install
-the <filename>pam-devel</filename> libraries that are needed to build PAM-enabled Samba. Additionally, Samba
-may auto-install the Winbind files into their correct locations on your system, so before you get too far down
-the track, be sure to check if the following configuration is really
-necessary. You may only need to configure
-<filename>/etc/nsswitch.conf</filename>.
-</para>
-
-<para>
-The libraries needed to run the &winbindd; daemon through nsswitch need to be copied to their proper locations:
-</para>
-
-<para>
-<indexterm><primary>libnss_winbind.so</primary></indexterm>
-<screen>
-&rootprompt;<userinput>cp ../samba/source/nsswitch/libnss_winbind.so /lib</userinput>
-</screen>
-</para>
-
-<para>
-I also found it necessary to make the following symbolic link:
-</para>
-
-<para>
-&rootprompt; <userinput>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</userinput>
-</para>
-
-<para>And, in the case of Sun Solaris:
-<indexterm><primary>nss_winbind.so.1</primary></indexterm>
-<screen>
-&rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</userinput>
-&rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</userinput>
-&rootprompt;<userinput>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</userinput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>/etc/nsswitch.conf</primary></indexterm>
-As root, edit <filename>/etc/nsswitch.conf</filename> to allow user and group entries to be visible from the
-&winbindd; daemon. My <filename>/etc/nsswitch.conf</filename> file looked like this after editing:
-<programlisting>
-passwd: files winbind
-shadow: files
-group: files winbind
-</programlisting></para>
-
-<para>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>ldconfig</primary></indexterm>
-<indexterm><primary>libnss_winbind</primary></indexterm>
-<indexterm><primary>grep</primary></indexterm>
-<indexterm><primary>dynamic link loader</primary></indexterm>
-The libraries needed by the <command>winbindd</command> daemon will be automatically
-entered into the <command>ldconfig</command> cache the next time
-your system reboots, but it is faster (and you do not need to reboot) if you do it manually:
-<screen>
-&rootprompt;<userinput>/sbin/ldconfig -v | grep winbind</userinput>
-</screen>
-This makes <filename>libnss_winbind</filename> available to winbindd and reports the current
-search path that is used by the dynamic link loader. The use of the <command>grep</command>
-filters the output of the <command>ldconfig</command> command so that we may see proof that
-this library is indeed recognized by the dynamic link loader.
-</para>
-
-<para>
-<indexterm><primary>dynamic link loader</primary></indexterm>
-<indexterm><primary>crle</primary></indexterm>
-<indexterm><primary>/usr/local/lib</primary></indexterm>
-<indexterm><primary>link loader configuration</primary></indexterm>
-<indexterm><primary>object module dependencies</primary></indexterm>
-The Sun Solaris dynamic link loader management tool is called <command>crle</command>. The
-use of this tool is necessary to instruct the dynamic link loader to search directories that
-contain library files that were not supplied as part of the original operating system platform.
-The following example shows how to use this tool to add the directory <filename>/usr/local/lib</filename>
-to the dynamic link loader's search path:
-<screen>
-&rootprompt; crle -u -l /usr/lib:/usr/local/lib
-</screen>
-When executed without arguments, <command>crle</command> reports the current dynamic
-link loader configuration. This is demonstrated here:
-<screen>
-&rootprompt; crle
-
-Configuration file [version 4]: /var/ld/ld.config
- Default Library Path (ELF): /lib:/usr/lib:/usr/local/lib
- Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system default)
-
-Command line:
- crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/local/lib
-</screen>
-From this it is apparent that the <filename>/usr/local/lib</filename> directory is included
-in the search dynamic link libraries in order to satisfy object module dependencies.
-</para>
-
-</sect3>
-
-<sect3>
-<title>NSS Winbind on AIX</title>
-
-<para>(This section is only for those running AIX.)</para>
-
-<para>
-<indexterm><primary>AIX</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>/usr/lib/security</primary></indexterm>
-<indexterm><primary>authentication module API</primary></indexterm>
-<indexterm><primary>/usr/lib/security/methods.cfg</primary></indexterm>
-<indexterm><primary>PAM module</primary></indexterm>
-The Winbind AIX identification module gets built as <filename>libnss_winbind.so</filename> in the
-nsswitch directory of the Samba source. This file can be copied to <filename>/usr/lib/security</filename>,
-and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following:
-<programlisting>
-WINBIND:
- program = /usr/lib/security/WINBIND
- options = authonly
-</programlisting>
-can then be added to <filename>/usr/lib/security/methods.cfg</filename>. This module only supports
-identification, but there have been reports of success using the standard Winbind PAM module for
-authentication. Use caution configuring loadable authentication modules, since misconfiguration can make
-it impossible to log on to the system. Information regarding the AIX authentication module API can
-be found in the <quote>Kernel Extensions and Device Support Programming Concepts for AIX</quote> document that
-describes the <ulink url="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/kernextc/sec_load_mod.htm">
-Loadable Authentication Module Programming Interface</ulink> for AIX. Further information on administering the modules
-can be found in the <ulink url="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm">System
-Management Guide: Operating System and Devices.</ulink>
-</para>
-</sect3>
-
-<sect3>
-<title>Configure smb.conf</title>
-
-<para>
-<indexterm><primary>winbind</primary></indexterm>
-<indexterm><primary>man page</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-Several parameters are needed in the &smb.conf; file to control the behavior of &winbindd;. These
-are described in more detail in the <citerefentry><refentrytitle>winbindd</refentrytitle>
-<manvolnum>8</manvolnum></citerefentry> man page. My &smb.conf; file, as shown in <link
-linkend="winbindcfg">the smb.conf for Winbind Setup</link>, was modified to include the necessary entries in the [global] section.
-</para>
-
-<example id="winbindcfg">
-<title>smb.conf for Winbind Setup</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfcomment> separate domain and username with '\', like DOMAIN\username</smbconfcomment>
-<smbconfoption name="winbind separator">\</smbconfoption>
-<smbconfcomment> use uids from 10000 to 20000 for domain users</smbconfcomment>
-<smbconfoption name="idmap uid">10000-20000</smbconfoption>
-<smbconfcomment> use gids from 10000 to 20000 for domain groups</smbconfcomment>
-<smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfcomment> allow enumeration of winbind users and groups</smbconfcomment>
-<smbconfoption name="winbind enum users">yes</smbconfoption>
-<smbconfoption name="winbind enum groups">yes</smbconfoption>
-<smbconfcomment> give winbind users a real shell (only needed if they have telnet access)</smbconfcomment>
-<smbconfoption name="template homedir">/home/winnt/%D/%U</smbconfoption>
-<smbconfoption name="template shell">/bin/bash</smbconfoption>
-</smbconfblock>
-</example>
-
-</sect3>
-
-
-<sect3>
-<title>Join the Samba Server to the PDC Domain</title>
-
-<para>
-<indexterm><primary>domain security</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>BDC</primary></indexterm>
-All machines that will participate in domain security should be members of
-the domain. This applies also to the PDC and all BDCs.
-</para>
-
-<para>
-<indexterm><primary>joining domain</primary></indexterm>
-<indexterm><primary>domain join</primary></indexterm>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>MS DCE RPC</primary></indexterm>
-<indexterm><primary>DCE RPC</primary></indexterm>
-<indexterm><primary>RPC</primary></indexterm>
-The process of joining a domain requires the use of the <command>net rpc join</command>
-command. This process communicates with the domain controller it will register with
-(usually the PDC) via MS DCE RPC. This means, of course, that the <command>smbd</command>
-process must be running on the target domain controller. It is therefore necessary to temporarily
-start Samba on a PDC so that it can join its own domain.
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>administrative privileges</primary></indexterm>
-<indexterm><primary>Administrator</primary></indexterm>
-Enter the following command to make the Samba server join the domain, where <replaceable>PDC</replaceable> is
-the name of your PDC and <replaceable>Administrator</replaceable> is a domain user who has administrative
-privileges in the domain.
-</para>
-
-<note><para>
-<indexterm><primary>domain controller</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>tcp ports</primary></indexterm>
-<indexterm><primary>udp ports</primary></indexterm>
-Before attempting to join a machine to the domain, verify that Samba is running
-on the target domain controller (usually PDC) and that it is capable of being reached via ports
-137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx).
-</para></note>
-
-<para>
-<indexterm><primary>net</primary><secondary>rpc</secondary><tertiary>join</tertiary></indexterm>
-The use of the <command>net rpc join</command> facility is shown here:
-<screen>
-&rootprompt;<userinput>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</userinput>
-</screen>
-The proper response to the command should be <quote>Joined the domain
-<replaceable>DOMAIN</replaceable></quote> where <replaceable>DOMAIN</replaceable>
-is your domain name.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Starting and Testing the <command>winbindd</command> Daemon</title>
-
-<para>
-<indexterm><primary>startup script</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>Winbind services</primary></indexterm>
-Eventually, you will want to modify your Samba startup script to automatically invoke the winbindd daemon when
-the other parts of Samba start, but it is possible to test out just the Winbind portion first. To start up
-Winbind services, enter the following command as root:
-<screen>
-&rootprompt;<userinput>/usr/local/samba/sbin/winbindd</userinput>
-</screen>
-Use the appropriate path to the location of the <command>winbindd</command> executable file.
-</para>
-
-<note><para>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>/usr/local/samba</primary></indexterm>
-The command to start up Winbind services assumes that Samba has been installed in the
-<filename>/usr/local/samba</filename> directory tree. You may need to search for the location of Samba files
-if this is not the location of <command>winbindd</command> on your system.
-</para></note>
-
-<para>
-<indexterm><primary>paranoid</primary></indexterm>
-<indexterm><primary>daemon running</primary></indexterm>
-I'm always paranoid and like to make sure the daemon is really running.
-<screen>
-&rootprompt;<userinput>ps -ae | grep winbindd</userinput>
-</screen>
-</para>
-
-<para>
-<indexterm><primary>winbindd</primary></indexterm>
-This command should produce output like the following if the daemon is running.
-<screen>
-3025 ? 00:00:00 winbindd
-</screen>
-</para>
-
-<para>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>wbinfo</primary></indexterm>
-Now, for the real test, try to get some information about the users on your PDC:
-<screen>
-&rootprompt;<userinput>/usr/local/samba/bin/wbinfo -u</userinput>
-</screen>
-This should echo back a list of users on your Windows users on your PDC. For example, I get the following
-response:
-<screen>
-CEO\Administrator
-CEO\burdell
-CEO\Guest
-CEO\jt-ad
-CEO\krbtgt
-CEO\TsInternetUser
-</screen>
-Obviously, I have named my domain <quote>CEO</quote> and my <smbconfoption name="winbind separator"/> is
-<quote>\</quote>.
-</para>
-
-<para>
-<indexterm><primary>wbinfo</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-You can do the same sort of thing to get group information from the PDC:
-<screen>
-&rootprompt;<userinput>/usr/local/samba/bin/wbinfo -g</userinput>
-CEO\Domain Admins
-CEO\Domain Users
-CEO\Domain Guests
-CEO\Domain Computers
-CEO\Domain Controllers
-CEO\Cert Publishers
-CEO\Schema Admins
-CEO\Enterprise Admins
-CEO\Group Policy Creator Owners
-</screen></para>
-
-<para>
-<indexterm><primary>getent</primary></indexterm>
-<indexterm><primary>PDC</primary></indexterm>
-<indexterm><primary>/etc/passwd</primary></indexterm>
-<indexterm><primary>UID</primary></indexterm>
-<indexterm><primary>GID</primary></indexterm>
-<indexterm><primary>home directories</primary></indexterm>
-<indexterm><primary>default shells</primary></indexterm>
-The function <command>getent</command> can now be used to get unified lists of both local and PDC users and
-groups. Try the following command:
-<screen>
-&rootprompt;<userinput>getent passwd</userinput>
-</screen>
-You should get a list that looks like your <filename>/etc/passwd</filename>
-list followed by the domain users with their new UIDs, GIDs, home
-directories, and default shells.
-</para>
-
-<para>
-The same thing can be done for groups with the command:
-<screen>
-&rootprompt;<userinput>getent group</userinput>
-</screen>
-</para>
-
-</sect3>
-
-
-<sect3>
-<title>Fix the init.d Startup Scripts</title>
-
-<sect4>
-<title>Linux</title>
-
-<para>
-<indexterm><primary>winbindd daemon</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>/etc/init.d/smb</primary></indexterm>
-<indexterm><primary>/etc/init.d/samba</primary></indexterm>
-<indexterm><primary>/usr/local/samba/bin</primary></indexterm>
-The &winbindd; daemon needs to start up after the &smbd; and &nmbd; daemons are running. To accomplish this
-task, you need to modify the startup scripts of your system. They are located at
-<filename>/etc/init.d/smb</filename> in Red Hat Linux and in <filename>/etc/init.d/samba</filename> in Debian
-Linux. Edit your script to add commands to invoke this daemon in the proper sequence. My startup script starts
-up &smbd;, &nmbd;, and &winbindd; from the <filename>/usr/local/samba/bin</filename> directory directly. The
-<command>start</command> function in the script looks like this:
-<programlisting>
-start() {
- KIND="SMB"
- echo -n $"Starting $KIND services: "
- daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
- RETVAL=$?
- echo
- KIND="NMB"
- echo -n $"Starting $KIND services: "
- daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
- RETVAL2=$?
- echo
- KIND="Winbind"
- echo -n $"Starting $KIND services: "
- daemon /usr/local/samba/sbin/winbindd
- RETVAL3=$?
- echo
- [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
- touch /var/lock/subsys/smb || RETVAL=1
- return $RETVAL
-}
-</programlisting></para>
-
-<para>If you would like to run winbindd in dual daemon mode, replace the line:
-<programlisting>
- daemon /usr/local/samba/sbin/winbindd
-</programlisting>
-
-in the example above with:
-
-<programlisting>
- daemon /usr/local/samba/sbin/winbindd -D
-</programlisting>.
-</para>
-
-<para>
-The <command>stop</command> function has a corresponding entry to shut down the services and looks like this:
-</para>
-
-<para><programlisting>
-stop() {
- KIND="SMB"
- echo -n $"Shutting down $KIND services: "
- killproc smbd
- RETVAL=$?
- echo
- KIND="NMB"
- echo -n $"Shutting down $KIND services: "
- killproc nmbd
- RETVAL2=$?
- echo
- KIND="Winbind"
- echo -n $"Shutting down $KIND services: "
- killproc winbindd
- RETVAL3=$?
- [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
- rm -f /var/lock/subsys/smb
- echo ""
- return $RETVAL
-}
-</programlisting></para>
-</sect4>
-
-<sect4>
-<title>Solaris</title>
-
-<para>
-Winbind does not work on Solaris 9; see <link linkend="winbind-solaris9">Winbind on Solaris 9 section</link>
-for details.
-</para>
-
-<para>
-<indexterm><primary>Solaris 9</primary></indexterm>
-<indexterm><primary>/etc/init.d/samba.server</primary></indexterm>
-<indexterm><primary>/usr/local/samba/bin</primary></indexterm>
-<indexterm><primary>smbd</primary></indexterm>
-<indexterm><primary>nmbd</primary></indexterm>
-<indexterm><primary>winbindd</primary></indexterm>
-On Solaris, you need to modify the <filename>/etc/init.d/samba.server</filename> startup script. It
-usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in
-<filename>/usr/local/samba/bin</filename>, the file could contains something like this:
-</para>
-
-<para>
- <programlisting>
- ##
- ## samba.server
- ##
-
- if [ ! -d /usr/bin ]
- then # /usr not mounted
- exit
- fi
-
- killproc() { # kill the named process(es)
- pid=`/usr/bin/ps -e |
- /usr/bin/grep -w $1 |
- /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
- [ "$pid" != "" ] && kill $pid
- }
-
- # Start/stop processes required for Samba server
-
- case "$1" in
-
- 'start')
- #
- # Edit these lines to suit your installation (paths, workgroup, host)
- #
- echo Starting SMBD
- /usr/local/samba/bin/smbd -D -s \
- /usr/local/samba/smb.conf
-
- echo Starting NMBD
- /usr/local/samba/bin/nmbd -D -l \
- /usr/local/samba/var/log -s /usr/local/samba/smb.conf
-
- echo Starting Winbind Daemon
- /usr/local/samba/sbin/winbindd
- ;;
-
- 'stop')
- killproc nmbd
- killproc smbd
- killproc winbindd
- ;;
-
- *)
- echo "Usage: /etc/init.d/samba.server { start | stop }"
- ;;
- esac
-</programlisting></para>
-
-<para>
-Again, if you would like to run winbindd in dual daemon mode, replace:
-<programlisting>
-/usr/local/samba/sbin/winbindd
-</programlisting>
-in the script above with:
-<programlisting>
-/usr/local/samba/sbin/winbindd -D
-</programlisting>
-</para>
-
-</sect4>
-
-<sect4>
-<title>Restarting</title>
-<para>
-<indexterm><primary>daemons</primary></indexterm>
-<indexterm><primary>local user</primary></indexterm>
-If you restart the &smbd;, &nmbd;, and &winbindd; daemons at this point, you
-should be able to connect to the Samba server as a domain member just as
-if you were a local user.
-</para>
-</sect4>
-</sect3>
-
-<sect3>
-<title>Configure Winbind and PAM</title>
-
-<para>
-<indexterm><primary>winbindd</primary></indexterm>
-<indexterm><primary>authentication</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>/etc/pam.d</primary></indexterm>
-If you have made it this far, you know that <command>winbindd</command> and Samba are working together. If you
-want to use Winbind to provide authentication for other services, keep reading. The PAM configuration files
-need to be altered in this step. (Did you remember to make backups of your original
-<filename>/etc/pam.d</filename> files? If not, do it now.)
-</para>
-
-<para>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>../source/nsswitch</primary></indexterm>
-<indexterm><primary>pam_winbind.so</primary></indexterm>
-<indexterm><primary>/lib/security</primary></indexterm>
-<indexterm><primary>Solaris</primary></indexterm>
-<indexterm><primary>/usr/lib/security</primary></indexterm>
-You will need a PAM module to use winbindd with these other services. This module will be compiled in the
-<filename>../source/nsswitch</filename> directory by invoking the command:
-<screen>
-&rootprompt;<userinput>make nsswitch/pam_winbind.so</userinput>
-</screen>
-from the <filename>../source</filename> directory. The <filename>pam_winbind.so</filename> file should be
-copied to the location of your other PAM security modules. On my Red Hat system, this was the
-<filename>/lib/security</filename> directory. On Solaris, the PAM security modules reside in
-<filename>/usr/lib/security</filename>.
-<screen>
-&rootprompt;<userinput>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</userinput>
-</screen>
-</para>
-
-<sect4>
-<title>Linux/FreeBSD-Specific PAM Configuration</title>
-
-<para>
-<indexterm><primary>/etc/pam.d/samba</primary></indexterm>
-The <filename>/etc/pam.d/samba</filename> file does not need to be changed. I just left this file as it was:
-<programlisting>
-auth required /lib/security/pam_stack.so service=system-auth
-account required /lib/security/pam_stack.so service=system-auth
-</programlisting></para>
-
-<para>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>authentication service</primary></indexterm>
-<indexterm><primary>login</primary></indexterm>
-<indexterm><primary>console</primary></indexterm>
-<indexterm><primary>telnet logins</primary></indexterm>
-<indexterm><primary>ftp service</primary></indexterm>
-<indexterm><primary>/etc/xinetd.d</primary></indexterm>
-<indexterm><primary>/etc/inetd.conf</primary></indexterm>
-<indexterm><primary>/etc/xinetd.d/telnet</primary></indexterm>
-The other services that I modified to allow the use of Winbind as an authentication service were the normal
-login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these
-services, you may first need to change the entries in <filename>/etc/xinetd.d</filename> (or
-<filename>/etc/inetd.conf</filename>). Red Hat Linux 7.1 and later uses the new xinetd.d structure, in this
-case you need to change the lines in <filename>/etc/xinetd.d/telnet</filename> and
-<filename>/etc/xinetd.d/wu-ftp</filename> from:
-<programlisting>
- enable = no
-</programlisting>
-to
-<programlisting>
- enable = yes
-</programlisting></para>
-
-<para>
-<indexterm><primary>ftp services</primary></indexterm>
-<indexterm><primary>home directory template</primary></indexterm>
-<indexterm><primary>domain users</primary></indexterm>
-For ftp services to work properly, you will also need to either have individual directories for the domain
-users already present on the server or change the home directory template to a general directory for all
-domain users. These can be easily set using the &smb.conf; global entry <smbconfoption name="template
-homedir"/>.
-</para>
-
-<note><para>
-<indexterm><primary>pam_mkhomedir</primary></indexterm>
-The directory in <smbconfoption name="template homedir"/> is not created automatically! Use pam_mkhomedir or
-pre-create the directories of users to make sure users can log in on UNIX with their own home directory.
-</para></note>
-
-<para>
-<indexterm><primary>/etc/pam.d/ftp</primary></indexterm>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>ftp access</primary></indexterm>
-The <filename>/etc/pam.d/ftp</filename> file can be changed to allow Winbind ftp access in a manner similar to
-the <filename>/etc/pam.d/samba</filename>Samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this:
-<programlisting>
-auth required /lib/security/pam_listfile.so item=user sense=deny \
- file=/etc/ftpusers onerr=succeed
-auth sufficient /lib/security/pam_winbind.so
-auth required /lib/security/pam_stack.so service=system-auth
-auth required /lib/security/pam_shells.so
-account sufficient /lib/security/pam_winbind.so
-account required /lib/security/pam_stack.so service=system-auth
-session required /lib/security/pam_stack.so service=system-auth
-</programlisting></para>
-
-<para>
-<indexterm><primary>/etc/pam.d/login</primary></indexterm>
-The <filename>/etc/pam.d/login</filename> file can be changed in nearly the same way. It now looks like this:
-<programlisting>
-auth required /lib/security/pam_securetty.so
-auth sufficient /lib/security/pam_winbind.so
-auth sufficient /lib/security/pam_unix.so use_first_pass
-auth required /lib/security/pam_stack.so service=system-auth
-auth required /lib/security/pam_nologin.so
-account sufficient /lib/security/pam_winbind.so
-account required /lib/security/pam_stack.so service=system-auth
-password required /lib/security/pam_stack.so service=system-auth
-session required /lib/security/pam_stack.so service=system-auth
-session optional /lib/security/pam_console.so
-</programlisting>
-<indexterm><primary>pam_winbind.so</primary></indexterm>
-<indexterm><primary>pam_securetty.so</primary></indexterm>
-<indexterm><primary>pam_unix.so</primary></indexterm>
-In this case, I added the <programlisting>auth sufficient /lib/security/pam_winbind.so</programlisting> lines
-as before, but also added the <programlisting>required pam_securetty.so</programlisting> above it to disallow
-root logins over the network. I also added a <programlisting>sufficient /lib/security/pam_unix.so
-use_first_pass</programlisting> line after the <command>winbind.so</command> line to get rid of annoying
-double prompts for passwords.
-</para>
-
-</sect4>
-
-<sect4>
-<title>Solaris-Specific Configuration</title>
-
-<para>
-<indexterm><primary>/etc/pam.conf</primary></indexterm>
-<indexterm><primary></primary></indexterm>
-The <filename>/etc/pam.conf</filename> needs to be changed. I changed this file so my Domain
-users can log on both locally as well as with telnet. The following are the changes
-that I made. You can customize the <filename>pam.conf</filename> file as per your requirements, but
-be sure of those changes because in the worst case it will leave your system
-nearly impossible to boot.
-<programlisting>
-#
-#ident "@(#)pam.conf 1.14 99/09/16 SMI"
-#
-# Copyright (c) 1996-1999, Sun Microsystems, Inc.
-# All Rights Reserved.
-#
-# PAM configuration
-#
-# Authentication management
-#
-login auth required /usr/lib/security/pam_winbind.so
-login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass
-#
-rlogin auth sufficient /usr/lib/security/pam_winbind.so
-rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
-rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-dtlogin auth sufficient /usr/lib/security/pam_winbind.so
-dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1
-other auth sufficient /usr/lib/security/pam_winbind.so
-other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-# Account management
-#
-login account sufficient /usr/lib/security/pam_winbind.so
-login account requisite /usr/lib/security/$ISA/pam_roles.so.1
-login account required /usr/lib/security/$ISA/pam_unix.so.1
-#
-dtlogin account sufficient /usr/lib/security/pam_winbind.so
-dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1
-dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1
-#
-other account sufficient /usr/lib/security/pam_winbind.so
-other account requisite /usr/lib/security/$ISA/pam_roles.so.1
-other account required /usr/lib/security/$ISA/pam_unix.so.1
-#
-# Session management
-#
-other session required /usr/lib/security/$ISA/pam_unix.so.1
-#
-# Password management
-#
-#other password sufficient /usr/lib/security/pam_winbind.so
-other password required /usr/lib/security/$ISA/pam_unix.so.1
-dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
-#
-# Support for Kerberos V5 authentication (uncomment to use Kerberos)
-#
-#rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other session optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-</programlisting></para>
-
-<para>
-<indexterm><primary>winbind.so</primary></indexterm>
-I also added a <parameter>try_first_pass</parameter> line after the <filename>winbind.so</filename>
-line to get rid of annoying double prompts for passwords.
-</para>
-
-<para>
-Now restart your Samba and try connecting through your application that you
-configured in the pam.conf.
-</para>
-
-</sect4>
-
-</sect3>
-
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>Conclusion</title>
-
-<para>
-<indexterm><primary>Winbind</primary></indexterm>
-<indexterm><primary>NSS</primary></indexterm>
-<indexterm><primary>PAM</primary></indexterm>
-<indexterm><primary>RPC calls</primary></indexterm>
-<indexterm><primary>domain users</primary></indexterm>
-The Winbind system, through the use of the NSS, PAMs, and appropriate Microsoft RPC calls, have allowed us to
-provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great
-reduction in the administrative cost of running a mixed UNIX and NT network.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
- <para>
- Winbind has a number of limitations in its current released version that we hope to overcome in future releases:
- </para>
-
- <itemizedlist>
- <listitem><para>
- Winbind is currently only available for the Linux, Solaris, AIX, and IRIX operating systems, although
- ports to other operating systems are certainly possible. For such ports to be feasible, we require the C
- library of the target operating system to support the NSS and PAM systems. This is becoming more common as NSS
- and PAM gain support among UNIX vendors.
- </para></listitem>
-
- <listitem><para>
- The mappings of Windows NT RIDs to UNIX IDs is not made algorithmically and depends on the order in
- which unmapped users or groups are seen by Winbind. It may be difficult to recover the mappings of RID to UNIX
- ID if the file containing this information is corrupted or destroyed.
- </para></listitem>
-
- <listitem><para>
- Currently the Winbind PAM module does not take into account possible workstation and logon time
- restrictions that may be set for Windows NT users; this is instead up to the PDC to enforce.
- </para></listitem>
- </itemizedlist>
-
- <sect2>
- <title>NSCD Problem Warning</title>
-
- <warning><para>
- Do not under any circumstances run <command>nscd</command> on any system
- on which <command>winbindd</command> is running.
- </para></warning>
-
- <para>
- If <command>nscd</command> is running on the UNIX/Linux system, then
- even though NSSWITCH is correctly configured, it will not be possible to resolve
- domain users and groups for file and directory controls.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Winbind Is Not Resolving Users and Groups</title>
-
- <para><quote>
- My &smb.conf; file is correctly configured. I have specified <smbconfoption name="idmap uid">12000</smbconfoption>,
- and <smbconfoption name="idmap gid">3000-3500</smbconfoption> and <command>winbind</command> is running.
- When I do the following, it all works fine.
- </quote></para>
-
-<para><screen>
-&rootprompt;<userinput>wbinfo -u</userinput>
-MIDEARTH\maryo
-MIDEARTH\jackb
-MIDEARTH\ameds
-...
-MIDEARTH\root
-
-&rootprompt;<userinput>wbinfo -g</userinput>
-MIDEARTH\Domain Users
-MIDEARTH\Domain Admins
-MIDEARTH\Domain Guests
-...
-MIDEARTH\Accounts
-
-&rootprompt;<userinput>getent passwd</userinput>
-root:x:0:0:root:/root:/bin/bash
-bin:x:1:1:bin:/bin:/bin/bash
-...
-maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
-</screen></para>
-
-<para><quote>
-But the following command just fails:
-</quote>
-<screen>
-&rootprompt;<userinput>chown maryo a_file</userinput>
-chown: `maryo': invalid user
-</screen>
-<quote>
-This is driving me nuts! What can be wrong?
-</quote></para>
-
-<para>
-Same problem as the one above.
-Your system is likely running <command>nscd</command>, the name service
-caching daemon. Shut it down, do not restart it! You will find your problem resolved.
-Alternately, fix the operation of nscd to resolve the problem.
-</para>
-
-</sect2>
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="ClientConfig">
-<chapterinfo>
- &author.jht;
-</chapterinfo>
-
-<title>MS Windows Network Configuration Guide</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>network difficulty</primary></indexterm>
-<indexterm><primary>network client</primary></indexterm>
-<indexterm><primary>client instructions</primary></indexterm>
-Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate
-correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way
-to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x
-servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.
-</para>
-
-<para>
-<indexterm><primary>graphically illustrated client configuration</primary></indexterm>
-<indexterm><primary>critical aspects of configuration</primary></indexterm>
-The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common
-critical aspects of such configuration. An experienced network administrator will not be interested in the
-details of this chapter.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Technical Details</title>
-
-<para>
-<indexterm><primary>TCP/IP protocol configuration</primary></indexterm>
-<indexterm><primary>network membership</primary></indexterm>
-This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms
-that are in common use today. These are:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Microsoft Windows XP Professional
- </para></listitem>
- <listitem><para>
- Windows 2000 Professional
- </para></listitem>
- <listitem><para>
- Windows Millennium edition (Me)
- </para></listitem>
-</itemizedlist>
-
- <sect2>
- <title>TCP/IP Configuration</title>
-
- <para>
-<indexterm><primary>network configuration problems</primary></indexterm>
-<indexterm><primary>plague network users</primary></indexterm>
- The builder of a house must ensure that all construction takes place on a firm foundation.
- The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems
- will plague all network users until they are resolved.
- </para>
-
- <para>
-<indexterm><primary>fixed IP addresses</primary></indexterm>
-<indexterm><primary>DHCP</primary></indexterm>
- MS Windows workstations and servers can be configured either with fixed
- IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP
- and make only passing reference to those situations where fixed IP configuration
- settings can be effected.
- </para>
-
- <para>
-<indexterm><primary>shortcuts</primary></indexterm>
-<indexterm><primary>abbreviated keystrokes</primary></indexterm>
- It is possible to use shortcuts or abbreviated keystrokes to arrive at a
- particular configuration screen. The decision was made to base all examples in this
- chapter on use of the <guibutton>Start</guibutton> button.
- </para>
-
- <sect3>
- <title>MS Windows XP Professional</title>
-
- <para>
-<indexterm><primary>Windows XP TCP/IP</primary></indexterm>
- There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:
- </para>
-
- <para>
- Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>.
- </para>
-
- <para>
- <emphasis>Alternately,</emphasis> click <guimenu>Start -></guimenu>, and right-click <guimenu>My Network Places</guimenu>
- then select <guimenuitem>Properties</guimenuitem>.
- </para>
-
- <para>
-<indexterm><primary>Windows XP Professional</primary></indexterm>
- The following procedure steps through the Windows XP Professional TCP/IP configuration process:
- </para>
-
- <procedure>
- <step><para>
-<indexterm><primary>Local Area Connection</primary></indexterm>
-<indexterm><primary>Network Bridge</primary></indexterm>
-<indexterm><primary>interface</primary></indexterm>
- On some installations the interface will be called <guimenu>Local Area Connection</guimenu> and
- on others it will be called <guimenu>Network Bridge</guimenu>. On our system it is called <guimenu>Network Bridge</guimenu>.
- Right-click on <guimenu>Network Bridge -> Properties</guimenu>. See <link linkend="WXPP002"/>.
- <figure id="WXPP002"><title>Network Bridge Configuration.</title><imagefile>WXPP002</imagefile></figure>
- </para>
- </step>
-
- <step><para>
-<indexterm><primary>TCP/IP protocol settings</primary></indexterm>
-<indexterm><primary>Network Bridge Configuration</primary></indexterm>
- The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings.
- In <guimenuitem>This connection uses the following items:</guimenuitem> box,
- click on <guimenu>Internet Protocol (TCP/IP)</guimenu>, then click on <guibutton>Properties</guibutton>.
- </para>
-
- <para>
-<indexterm><primary>DHCP-enabled operation</primary></indexterm>
-<indexterm><primary>IP address automatically</primary></indexterm>
- The default setting is DHCP-enabled operation
- (i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="WXPP003"/>.
- <figure id="WXPP003">
- <title>Internet Protocol (TCP/IP) Properties.</title>
- <imagefile>WXPP003</imagefile>
- </figure>
- </para>
-
- <para>
-<indexterm><primary>DHCP</primary></indexterm>
-<indexterm><primary>TCP/IP</primary></indexterm>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>ISC DHCP server</primary></indexterm>
- Many network administrators will want to use DHCP to configure all client TCP/IP
- protocol stack settings. (For information on how to configure the ISC DHCP server
- for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
- <link linkend="DHCP">DHCP Server</link>).
- </para>
-
- <para>
-<indexterm><primary>fixed IP address</primary></indexterm>
-<indexterm><primary>subnet mask</primary></indexterm>
-<indexterm><primary>gateway address</primary></indexterm>
- If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
- IP Address, the subnet mask, and the default gateway address in the boxes provided.
- </para></step>
-
- <step><para>
-<indexterm><primary>Advanced TCP/IP configuration</primary></indexterm>
-<indexterm><primary>TCP/IP configuration</primary></indexterm>
-<indexterm><primary>IP aliases</primary></indexterm>
-<indexterm><primary>default gateways</primary></indexterm>
- Click the <guibutton>Advanced</guibutton> button to proceed with TCP/IP configuration.
- This opens a panel in which it is possible to create additional IP addresses for this interface.
- The technical name for the additional addresses is <emphasis>IP aliases</emphasis>, and additionally this
- panel permits the setting of more default gateways (routers). In most cases where DHCP is used, it will not be
- necessary to create additional settings. See <link linkend="WXPP005"></link> to see the appearance of this panel.
- <figure id="WXPP005"><title>Advanced Network Settings</title><imagefile>WXPP005</imagefile></figure>
- </para>
-
- <para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>DHCP</primary></indexterm>
- Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
- </para></step>
-
- <step><para>
-<indexterm><primary>DNS server settings</primary></indexterm>
-<indexterm><primary>manually configured DNS settings</primary></indexterm>
- Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
- The example system uses manually configured DNS settings. When finished making changes, click the
- <guibutton>OK</guibutton> to commit the settings. See <link linkend="WXPP014"/>.
- <figure id="WXPP014"> <title>DNS Configuration.</title> <imagefile>WXPP014</imagefile> </figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>manual WINS server entries</primary></indexterm>
- Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
- This step demonstrates an example system that uses manually configured WINS settings.
- When finished making changes, click <guibutton>OK</guibutton> to commit
- the settings. See <link linkend="WXPP009"></link>.
- <figure id="WXPP009"><title>WINS Configuration</title><imagefile>WXPP009</imagefile></figure>
- </para></step>
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>MS Windows 2000</title>
-
- <para>
-<indexterm><primary>Windows 2000 Professional TCP/IP</primary></indexterm>
-<indexterm><primary>TCP/IP configuration panel</primary></indexterm>
- There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:
- </para>
-
- <para>
- Click <guimenu>Start -> Control Panel -> Network and Dial-up Connections</guimenu>.
- </para>
-
- <para>
- <emphasis>Alternatively,</emphasis> click <guimenu>Start</guimenu>, then right-click <guimenu>My Network Places</guimenu>, and
- select <guimenuitem>Properties</guimenuitem>.
- </para>
-
- <para>
-<indexterm><primary>Windows XP Professional TCP/IP</primary></indexterm>
- The following procedure steps through the Windows XP Professional TCP/IP configuration process:
- </para>
-
- <procedure>
- <step><para>
- Right-click on <guimenu>Local Area Connection</guimenu>, then click
- <guimenuitem>Properties</guimenuitem>. See <link linkend="w2kp001"></link>.
- <figure id="w2kp001"><title>Local Area Connection Properties.</title><imagefile>w2kp001</imagefile></figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>Local Area Connection Properties</primary></indexterm>
-<indexterm><primary>TCP/IP protocol settings</primary></indexterm>
- The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on
- <guimenu>Internet Protocol (TCP/IP)</guimenu> in the <guimenuitem>Components checked are used by this
- connection:</guimenuitem> box, then click the <guibutton>Properties</guibutton> button.
- </para></step>
-
- <step><para>
-<indexterm><primary>DHCP-enabled</primary></indexterm>
-<indexterm><primary>IP address automatically</primary></indexterm>
- The default setting is DHCP-enabled operation
- (i.e., <quote>Obtain an IP address automatically</quote>). See <link linkend="w2kp002"/>.
- <figure id="w2kp002"><title>Internet Protocol (TCP/IP) Properties.</title><imagefile>w2kp002</imagefile></figure>
- </para>
-
- <para>
-<indexterm><primary>DHCP</primary></indexterm>
-<indexterm><primary>protocol stack settings</primary></indexterm>
- Many network administrators will want to use DHCP to configure all client TCP/IP
- protocol stack settings. (For information on how to configure the ISC DHCP server
- for Windows client support, see, <link linkend="DHCP"></link>).
- </para>
-
- <para>
-<indexterm><primary>fixed IP address</primary></indexterm>
-<indexterm><primary>network clients</primary></indexterm>
- If it is necessary to provide a fixed IP address, click on <quote>Use the following IP address</quote> and enter the
- IP Address, the subnet mask, and the default gateway address in the boxes provided.
- For this example we are assuming that all network clients will be configured using DHCP.
- </para></step>
-
- <step><para>
- Click the <guimenu>Advanced</guimenu> button to proceed with TCP/IP configuration.
- Refer to <link linkend="w2kp003"></link>.
- <figure id="w2kp003"><title>Advanced Network Settings.</title><imagefile>w2kp003</imagefile></figure>
- </para>
-
- <para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>DHCP</primary></indexterm>
- Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
- </para></step>
-
- <step><para>
-<indexterm><primary>DNS server settings</primary></indexterm>
-<indexterm><primary>commit the settings</primary></indexterm>
- Click the <guimenu>DNS</guimenu> tab to add DNS server settings.
- The example system uses manually configured DNS settings. When finished making changes,
- click <guibutton>OK</guibutton> to commit the settings. See <link linkend="w2kp004"></link>.
- <figure id="w2kp004"><title>DNS Configuration.</title><imagefile>w2kp004</imagefile></figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>manual WINS server entries</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
- Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries.
- This step demonstrates an example system that uses manually configured WINS settings.
- When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
- See <link linkend="w2kp005"></link>.
- <figure id="w2kp005">
- <title>WINS Configuration.</title><imagefile>w2kp005</imagefile>
- </figure>
- </para></step>
-
- </procedure>
-
- </sect3>
-
- <sect3>
- <title>MS Windows Me</title>
-
- <para>
-<indexterm><primary>Windows Millennium edition (Me) TCP/IP</primary></indexterm>
-<indexterm><primary>Windows Millennium</primary></indexterm>
-<indexterm><primary>TCP/IP configuration</primary></indexterm>
- There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:
- </para>
-
- <para>
- Click <guimenu>Start -> Control Panel -> Network Connections</guimenu>.
- </para>
-
- <para>
-<indexterm><primary>My Network Places</primary></indexterm>
-<indexterm><primary>Properties</primary></indexterm>
- <emphasis>Alternatively,</emphasis> click on <guimenu>Start -></guimenu>, and right click on <guimenu>My Network Places</guimenu>
- then select <guimenuitem>Properties</guimenuitem>.
- </para>
-
- <para>
-<indexterm><primary>Windows Me TCP/IP</primary></indexterm>
- The following procedure steps through the Windows Me TCP/IP configuration process:
- </para>
-
- <procedure>
- <step><para>
-<indexterm><primary>Internet Protocol TCP/IP</primary></indexterm>
- In the box labeled <guimenuitem>The following network components are installed:</guimenuitem>,
- click on <guimenu>Internet Protocol TCP/IP</guimenu>, then click on the <guibutton>Properties</guibutton> button.
- See <link linkend="WME001"></link>.
- <figure id="WME001">
- <title>The Windows Me Network Configuration Panel.</title>
- <imagefile>WME001</imagefile>
- </figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>DHCP</primary></indexterm>
-<indexterm><primary>TCP/IP</primary></indexterm>
-<indexterm><primary>ISC DHCP server</primary></indexterm>
- Many network administrators will want to use DHCP to configure all client TCP/IP
- protocol stack settings. (For information on how to configure the ISC DHCP server
- for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>,
- <link linkend="DHCP">DHCP Server</link>). The default setting on Windows Me workstations is for DHCP-enabled operation
- (i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled). See <link linkend="WME002"></link>.
- <figure id="WME002"><title>IP Address.</title><imagefile>WME002</imagefile></figure>
- </para>
-
- <para>
-<indexterm><primary>Specify an IP address</primary></indexterm>
-<indexterm><primary>subnet mask</primary></indexterm>
-<indexterm><primary>DHCP</primary></indexterm>
- If it is necessary to provide a fixed IP address, click on <guimenuitem>Specify an IP address</guimenuitem> and enter the
- IP Address and the subnet mask in the boxes provided. For this example we are assuming that all
- network clients will be configured using DHCP.
- </para></step>
-
- <step><para>
-<indexterm><primary>DNS</primary></indexterm>
-<indexterm><primary>WINS</primary></indexterm>
- Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.
- </para></step>
-
- <step><para>
-<indexterm><primary>WINS server settings</primary></indexterm>
- If necessary, click the <guimenu>DNS Configuration</guimenu> tab to add DNS server settings.
- Click the <guibutton>WINS Configuration</guibutton> tab to add WINS server settings.
- The <guimenu>Gateway</guimenu> tab allows additional gateways (router addresses) to be added to the network
- interface settings. In most cases where DHCP is used, it will not be necessary to
- create these manual settings.
- </para></step>
-
- <step><para>
-<indexterm><primary>WINS</primary></indexterm>
-<indexterm><primary>manually configured</primary></indexterm>
- The following example uses manually configured WINS settings. See <link linkend="WME005"></link>.
- When finished making changes, click <guibutton>OK</guibutton> to commit the settings.
- <figure id="WME005"><title>DNS Configuration.</title><imagefile>WME005</imagefile></figure>
- </para>
-
- <para>
-<indexterm><primary>single DHCP server</primary></indexterm>
-<indexterm><primary>multiple Windows workgroups or domains</primary></indexterm>
- This is an example of a system that uses manually configured WINS settings. One situation where
- this might apply is on a network that has a single DHCP server that provides settings for multiple
- Windows workgroups or domains. See <link linkend="WME003"></link>.
- <figure id="WME003"><title>WINS Configuration.</title><imagefile>WME003</imagefile></figure>
- </para></step>
- </procedure>
-
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Joining a Domain: Windows 2000/XP Professional</title>
-
- <para>
-<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
-<indexterm><primary>domain security</primary></indexterm>
-<indexterm><primary>domain member</primary></indexterm>
-<indexterm><primary>domain joining</primary></indexterm>
- Microsoft Windows NT/200x/XP Professional platforms can participate in domain security.
- This section steps through the process for making a Windows 200x/XP Professional machine a
- member of a domain security environment. It should be noted that this process is identical
- when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC.
- </para>
-
- <procedure>
- <step><para>
- Click <guimenu>Start</guimenu>.
- </para></step>
-
- <step><para>
- Right-click <guimenu>My Computer</guimenu>, then select <guimenuitem>Properties</guimenuitem>.
- </para></step>
-
- <step><para>
-<indexterm><primary>Control Panel</primary></indexterm>
- The opening panel is the same one that can be reached by clicking <guimenu>System</guimenu> on the Control Panel.
- See <link linkend="wxpp001"></link>.
- <figure id="wxpp001"><title>The General Panel.</title><imagefile>wxpp001</imagefile></figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>Computer Name</primary></indexterm>
- Click the <guimenu>Computer Name</guimenu> tab.
- This panel shows the <guimenuitem>Computer Description</guimenuitem>, the <guimenuitem>Full computer name</guimenuitem>,
- and the <guimenuitem>Workgroup</guimenuitem> or <guimenuitem>Domain name</guimenuitem>.
- </para>
-
- <para>
-<indexterm><primary>Network ID</primary></indexterm>
-<indexterm><primary>configuration wizard</primary></indexterm>
- Clicking the <guimenu>Network ID</guimenu> button will launch the configuration wizard. Do not use this with
- Samba. If you wish to change the computer name or join or leave the domain, click the <guimenu>Change</guimenu> button.
- See <link linkend="wxpp004"></link>.
- <figure id="wxpp004"><title>The Computer Name Panel.</title><imagefile>wxpp004</imagefile></figure>
- </para></step>
-
- <step><para>
- Click on <guimenu>Change</guimenu>. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP.
- We will join the domain called MIDEARTH. See <link linkend="wxpp006"></link>.
- <figure id="wxpp006"><title>The Computer Name Changes Panel.</title><imagefile>wxpp006</imagefile></figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>domain radio button</primary></indexterm>
- Enter the name <guimenu>MIDEARTH</guimenu> in the field below the domain radio button.
- </para>
-
- <para>
- This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See <link linkend="wxpp007"></link>.
- <figure id="wxpp007"><title>The Computer Name Changes Panel &smbmdash; Domain MIDEARTH.</title><imagefile>wxpp007</imagefile></figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>credentials</primary></indexterm>
-<indexterm><primary>username and password</primary></indexterm>
- Now click the <guimenu>OK</guimenu> button. A dialog box should appear to allow you to provide the
- credentials (username and password) of a domain administrative account that has the rights to add machines to
- the domain.
- </para>
-
- <para>
-<indexterm><primary>root</primary></indexterm>
- Enter the name <quote>root</quote> and the root password from your Samba server. See <link linkend="wxpp008"></link>.
- <figure id="wxpp008">
- <title>Computer Name Changes &smbmdash; Username and Password Panel.</title><imagefile>wxpp008</imagefile>
- </figure>
- </para></step>
-
- <step><para>
- Click on <guimenu>OK</guimenu>.
- </para>
-
- <para>
-<indexterm><primary>Welcome</primary></indexterm>
-<indexterm><primary>rebooted</primary></indexterm>
- The <quote>Welcome to the MIDEARTH domain.</quote> dialog box should appear. At this point the machine must be rebooted.
- Joining the domain is now complete.
- </para></step>
-
- </procedure>
-
- </sect2>
-
- <sect2>
- <title>Domain Logon Configuration: Windows 9x/Me</title>
-
- <para>
-<indexterm><primary>Windows 9x/Me</primary></indexterm>
-<indexterm><primary>domain logon</primary></indexterm>
-<indexterm><primary>LanManager</primary></indexterm>
- We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is
- that these platforms can use only the LanManager network logon protocols.
- </para>
-
- <note><para>
-<indexterm><primary>Windows XP Home edition</primary></indexterm>
-<indexterm><primary>LanManager</primary></indexterm>
-<indexterm><primary>network logon</primary></indexterm>
- Windows XP Home edition cannot participate in domain or LanManager network logons.
- </para></note>
-
- <procedure>
- <step><para>
- Right-click on the <guimenu>Network Neighborhood</guimenu> icon.
- </para></step>
-
- <step><para>
- The Network Configuration Panel allows all common network settings to be changed.
- See <link linkend="WME009"></link>.
- <figure id="WME009"><title>The Network Panel.</title><imagefile>WME009</imagefile></figure>
- </para>
-
- <para>
-<indexterm><primary>Client for Microsoft Networks</primary></indexterm>
-<indexterm><primary>Properties</primary></indexterm>
- Make sure that the <guimenu>Client for Microsoft Networks</guimenu> driver is installed as shown.
- Click on the <guimenu>Client for Microsoft Networks</guimenu> entry in <guimenu>The following network
- components are installed:</guimenu> box. Then click the <guibutton>Properties</guibutton> button.
- </para></step>
-
- <step><para>
-<indexterm><primary>Networks Properties</primary></indexterm>
-<indexterm><primary>network logon</primary></indexterm>
- The Client for Microsoft Networks Properties panel is the correct location to configure network logon
- settings. See <link linkend="WME010"></link>.
- <figure id="WME010"><title>Client for Microsoft Networks Properties Panel.</title><imagefile>WME010</imagefile></figure>
- </para>
-
- <para>
-<indexterm><primary>Windows NT domain name</primary></indexterm>
-<indexterm><primary>domain name</primary></indexterm>
- Enter the Windows NT domain name, check the <guimenu>Log on to Windows NT domain</guimenu> box,
- and click <guimenu>OK</guimenu>.
- </para></step>
-
- <step><para>
-<indexterm><primary>Identification</primary></indexterm>
-<indexterm><primary>workgroup</primary></indexterm>
-<indexterm><primary>computer name</primary></indexterm>
- Click on the <guimenu>Identification</guimenu> button. This is the location at which the workgroup
- (domain) name and the machine name (computer name) need to be set. See <link linkend="WME013"></link>.
- <figure id="WME013"><title>Identification Panel.</title><imagefile>WME013</imagefile></figure>
- </para></step>
-
- <step><para>
-<indexterm><primary>Access Control</primary></indexterm>
-<indexterm><primary>group accounts</primary></indexterm>
-<indexterm><primary>domain user</primary></indexterm>
-<indexterm><primary>User-level access control</primary></indexterm>
- Now click the <guimenu>Access Control</guimenu> button. If you want to be able to assign share access
- permissions using domain user and group accounts, it is necessary to enable
- <guimenu>User-level access control</guimenu> as shown in this panel. See <link linkend="WME014"></link>.
- <figure id="WME014"><title>Access Control Panel.</title><imagefile>WME014</imagefile></figure>
- </para></step>
-
- </procedure>
-
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-<indexterm><primary>networking systems</primary></indexterm>
-<indexterm><primary>errors that can afflict</primary></indexterm>
-The most common errors that can afflict Windows networking systems include:
-</para>
-
-<itemizedlist>
- <listitem><para>Incorrect IP address.</para></listitem>
- <listitem><para>Incorrect or inconsistent netmasks.</para></listitem>
- <listitem><para>Incorrect router address.</para></listitem>
- <listitem><para>Incorrect DNS server address.</para></listitem>
- <listitem><para>Incorrect WINS server address.</para></listitem>
- <listitem><para>Use of a Network Scope setting &smbmdash; watch out for this one!</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm><primary>Windows NT/200x/XP Professional</primary></indexterm>
-<indexterm><primary>cannot join domain</primary></indexterm>
-The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:
-</para>
-
-<itemizedlist>
- <listitem><para>&smb.conf; does not have correct <smbconfoption name="add machine script"/> settings.</para></listitem>
- <listitem><para><quote>root</quote> account is not in password backend database.</para></listitem>
- <listitem><para>Attempt to use a user account instead of the <quote>root</quote> account to join a machine to the domain.</para></listitem>
- <listitem><para>Open connections from the workstation to the server.</para></listitem>
- <listitem><para>Firewall or filter configurations in place on either the client or the Samba server.</para></listitem>
-</itemizedlist>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version='1.0'?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<preface>
-<title>Foreword</title>
-
-<para>
-When John first asked me to write an introductory piece for his latest book, I was somewhat mystified as to
-why he chose me. A conversation with John provided some of the rationale, and he left it to me to fill in the
-<emphasis>rest</emphasis> of the story. So, if you are willing to endure a little bit of background, I will
-provide the part of the story that John wouldn't provide.
-</para>
-
-<para>
-I am the Director of Corporate Standards at Sun Microsystems, and manage Sun's standards portfolio. Before
-that, I was the Director of Standards at Netscape, which was when I met John. Before Sun, there was Digital
-Equipment Corporation, also standards. I've written several books on standards, and tend to observe (and
-occasionally help) the technical and business trends that drive standardization as a discipline. I tend to see
-standardization as a management tool, not as a technical discipline and this is part of the rationale that
-John provided.
-</para>
-
-<para>
-The book that you have before you focuses on a particular standardized way of doing something hence, it is a
-book about a standard. The most important thing to keep in mind about a standard is the rationale for its
-creation. Standards are created not for technical reasons, not for business reasons, but for a deeper and much
-more compelling reason. Standards are created and used to allow people to communicate in a meaningful way.
-Every standard, if it is a true standard, has as its entire (and only) goal set the increasing of relevant
-communication between people.
-</para>
-
-<para>
-This primary goal cannot be met however, unless the standard is documented. I have been involved in too many
-standardization efforts when it became apparent that <emphasis>everybody knows</emphasis> was the dominant
-emotion of those providing documentation. <emphasis>They</emphasis> of the ever present <emphasis>they
-say</emphasis> and <emphasis>they know</emphasis> are the bane of good standards. If <emphasis>they
-know</emphasis>, why are you doing a standard?
-</para>
-
-<para>
-A <emphasis>good standard</emphasis> survives because people know how to use it. People know how to use a
-standard when it is so transparent, so obvious, and so easy that it becomes invisible. And a standard becomes
-invisible only when the documentation describing how to deploy it is clear, unambiguous, and correct. These
-three elements must be present for a standard to be useful, allowing communication and interaction between two
-separate and distinct entities to occur without obvious effort. As you read this book, look for the evidence
-of these three characteristics and notice how they are seamlessly woven into John's text. Clarity and
-unambiguity without <emphasis>correctness</emphasis> provide a technical nightmare. Correctness and clarity
-with ambiguity create <emphasis>maybe bits,</emphasis> and correctness and unambiguity without clarity provide
-a <emphasis>muddle through</emphasis> scenario.
-</para>
-
-<para>
-And this is <emphasis>the rest of the story</emphasis> that John couldn't (or wouldn't) bring himself to
-state. This book provides a clear, concise, unambiguous, and technically valid presentation of Samba to make
-it useful to a user to someone who wants to use the standard to increase communication and the capability
-for communication between two or more entities whether person-machine, machine-machine, or person-person.
-The intent of this book is not to convince anyone of any agenda political, technical, or social. The intent
-is to provide documentation for users who need to know about Samba, how to use it, and how to get on with
-their primary responsibilities. While there is pride on John's part because of the tremendous success of
-the Samba documentation, he writes for the person who needs a tool to accomplish a particular job, and who has
-selected Samba to be that tool.
-</para>
-
-<para>
-The book is a monument to John's perseverance and dedication to Samba and in my opinion to the goal of
-standardization. By writing this book, John has provided the users of Samba those that want to deploy it to
-make things better a clear, easy, and ultimately valuable resource. Additionally, he has increased the
-understanding and utility of a highly useful standard, and for this, as much as for the documentation, he is
-owed a debt of gratitude by those of us who rely on standards to make our lives more manageable.
-</para>
-
-<para>
-<simplelist>
- <member>Carl Cargill, Senior Director</member>
- <member>Corporate Standardization, The Office of the CTO</member>
- <member>Sun Microsystems</member>
-</simplelist>
-</para>
-
-</preface>
+++ /dev/null
-<?xml version='1.0'?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<preface>
-<title>Foreword</title>
-
-<para>
-Over the last few years, the Samba project has undergone a major
-transformation. From a small project used only by people who dream in
-machine code, Samba has grown to be an integral part of the IT
-infrastructure of many businesses. Along with the growth in the
-popularity of Samba there has been a corresponding growth in the ways
-that it can be used, and a similar growth in the number of
-configuration options and the interactions between them.
-</para>
-
-<para>
-To address this increasing complexity a wealth of documentation has
-been written on Samba, including numerous HOWTOs, diagnostic tips,
-manual pages, and explanations of important pieces of technology that
-Samba relies on. While it has been gratifying to see so much
-documentation being written, the sheer volume of different types of
-documentation has proved difficult to navigate, thus reducing its
-value to system administrators trying to cope with the complexity.
-</para>
-
-<para>
-This book gathers together that wealth of information into a much more
-accessible form, to allow system administrators to quickly find what
-they need. The breadth of technical information provided ensures that
-even the most demanding administrators will find something helpful.
-</para>
-
-<para>
-I am delighted that the Samba documentation has now developed to the
-extent that it can be presented usefully as a book, and I am grateful
-for the efforts of the many people who have contributed so much
-toward this result. Enjoy!
-</para>
-
-<para>
-<simplelist>
- <member>Andrew Tridgell</member>
- <member><emphasis>President, Samba Team</emphasis></member>
- <member><emphasis>July 2003</emphasis></member>
-</simplelist>
-</para>
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE glossary PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<glossary>
- <title>Glossary</title>
-
- <glossentry>
- <glossterm>Access Control List</glossterm>
- <acronym>ACL</acronym>
- <glossdef><para>
- A detailed list of permissions granted to users or groups with respect to file and network resource access.
- See <link linkend="AccessControls"/>,
- for details.</para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Active Directory Service</glossterm>
- <acronym>ADS</acronym>
- <glossdef><para>
- A service unique to Microsoft Windows 200x servers that provides a centrally managed
- directory for management of user identities and computer objects, as well as the permissions
- each user or computer may be granted to access
- distributed network resources. ADS uses Kerberos-based
- authentication and LDAP over Kerberos for directory access.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Common Internet File System</glossterm>
- <acronym>CIFS</acronym>
- <glossdef><para>The new name for SMB. Microsoft renamed the
- SMB protocol to CIFS during the Internet hype in the nineties.
- At about the time that the SMB protocol was renamed to CIFS, an
- additional dialect of the SMB protocol was in development.
- The need for the deployment of the NetBIOS layer was also
- removed, thus paving the way for use of the SMB protocol natively
- over TCP/IP (known as NetBIOS-less SMB or <quote>naked</quote> TCP transport).
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Common UNIX Printing System</glossterm>
- <acronym>CUPS</acronym>
- <glossdef><para>
- A recent implementation of a high capability printing system for UNIX developed by
- <ulink url="http://www.easysw.com/"></ulink>. The design objective of CUPS was to provide
- a rich print processing system that has built-in intelligence capable of correctly rendering (processing)
- a file that is submitted for printing even if it was formatted for an entirely different printer.
- </para>
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Domain Master Browser</glossterm>
- <acronym>DMB</acronym>
- <glossdef><para>The domain master browser maintains a list of all the servers that
- have announced their services within a given workgroup or NT domain. See <link linkend="DMB"/> for details.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Domain Name Service</glossterm>
- <acronym>DNS</acronym>
- <glossdef><para>
- A protocol by which computer hostnames may be resolved to the matching IP address/es. DNS is implemented
- by the Berkeley Internet Name Daemon. There exists a recent version of DNS that allows dynamic name registration
- by network clients or by a DHCP server. This recent protocol is known as dynamic DNS (DDNS).
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Dynamic Host Configuration Protocol</glossterm>
- <acronym>DHCP</acronym>
- <glossdef><para>
- A protocol that was based on the BOOTP protocol that may be used to dynamically assign an IP address,
- from a reserved pool of addresses, to a network client or device. Additionally, DHCP may assign all
- network configuration settings and may be used to register a computer name and its address with a
- dynamic DNS server.
- </para></glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Extended Meta-file Format</glossterm>
- <acronym>EMF</acronym>
- <glossdef>
- <para>
- An intermediate file format used by Microsoft Windows-based servers and clients. EMF files may be
- rendered into a page description language by a print processor.
- </para>
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Graphical Device Interface</glossterm>
- <acronym>GDI</acronym>
- <glossdef><para>
- Device-independent format for printing used by Microsoft Windows.
- It is quite similar to what PostScript is for UNIX. Printing jobs are first generated in GDI and
- then converted to a device-specific format. See <link linkend="gdipost"/> for details.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Group IDentifier</glossterm>
- <acronym>GID</acronym>
- <glossdef><para>
- The UNIX system group identifier; on older systems, a 32-bit unsigned integer, and on newer systems
- an unsigned 64-bit integer. The GID is used in UNIX-like operating systems for all group-level access
- control.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Internet Print Protocol</glossterm>
- <acronym>IPP</acronym>
- <glossdef><para>An IETF standard for network printing. CUPS
- implements IPP.</para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Key Distribution Center</glossterm>
- <acronym>KDC</acronym>
- <glossdef><para>The Kerberos authentication protocol makes use of security keys (also called a ticket)
- by which access to network resources is controlled. The issuing of Kerberos tickets is effected by
- a KDC.</para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>NetBIOS Extended User Interface</glossterm>
- <acronym>NetBEUI</acronym>
- <glossdef><para>
- Very simple network protocol invented by IBM and Microsoft. It is used
- to do NetBIOS over Ethernet with low overhead. NetBEUI is a nonroutable
- protocol.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Network Basic Input/Output System</glossterm>
- <acronym>NetBIOS</acronym>
- <glossdef><para>
- NetBIOS is a simple application programming interface (API) invented in the 1980s
- that allows programs to send data to certain network names.
- NetBIOS is always run over another network protocol such
- as IPX/SPX, TCP/IP, or Logical Link Control (LLC). NetBIOS run over LLC
- is best known as NetBEUI (NetBIOS Extended User Interface &smbmdash; a complete misnomer!).
- </para></glossdef>
- </glossentry>
-
-
- <glossentry>
- <glossterm>NetBT</glossterm>
- <acronym>NBT</acronym>
- <glossdef><para>Protocol for transporting NetBIOS frames over TCP/IP. Uses ports 137, 138, and 139.
- NetBT is a fully routable protocol.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Local Master Browser</glossterm>
- <acronym>LMB</acronym>
- <glossdef><para>The local master browser maintains a list
- of all servers that have announced themselves within a given workgroup or NT domain on a particular
- broadcast-isolated subnet. See <link linkend="DMB"/> for details.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Printer Command Language</glossterm>
- <acronym>PCL</acronym>
- <glossdef><para>
- A printer page description language that was developed by Hewlett-Packard
- and is in common use today.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Portable Document Format</glossterm>
- <acronym>PDF</acronym>
- <glossdef>
- <para>
- A highly compressed document format, based on PostScript, used as a document distribution format
- that is supported by Web browsers as well as many applications. Adobe also distributes an application
- called <quote>Acrobat,</quote> which is a PDF reader.
- </para>
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Page Description Language</glossterm>
- <acronym>PDL</acronym>
- <glossdef><para>A language for describing the layout and contents of a printed page.
- The best-known PDLs are Adobe PostScript and Hewlett-Packard PCL (Printer Control Language),
- both of which are used to control laser printers.</para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>PostScript Printer Description</glossterm>
- <acronym>PPD</acronym>
- <glossdef><para>
- PPDs specify and control options supported by PostScript printers, such as duplexing, stapling,
- and DPI. See also <link linkend="post-and-ghost"/>. PPD files can be read by printing applications
- to enable correct PostScript page layout for a particular PostScript printer.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Remote Procedure Call</glossterm>
- <acronym>RPC</acronym>
- <glossdef><para>
- RPCs are a means for executing network operations. The RPC protocol is independent of transport protocols. RPC
- does not try to implement any kind of reliability and the application that uses RPCs must be aware of the type
- of transport protocol underneath RPC. An RPC is like a programmatic jump subroutine over a network. RPCs used
- in the UNIX environment are specified in RFC 1050. RPC is a powerful technique for constructing distributed,
- client-server based applications. It is based on extending the notion of conventional, or local procedure
- calling, so that the called procedure need not exist in the same address space as the calling procedure. The
- two processes may be on the same system, or they may be on different systems with a network connecting them.
- By using RPC, programmers of distributed applications avoid the details of the interface with the network. The
- transport independence of RPC isolates the application from the physical and logical elements of the data
- communications mechanism and allows the application to use a variety of transports.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Server Message Block</glossterm>
- <acronym>SMB</acronym>
- <glossdef><para>
- SMB was the original name of the protocol `spoken' by
- Samba. It was invented in the 1980s by IBM and adopted
- and extended further by Microsoft. Microsoft
- renamed the protocol to CIFS during the Internet hype in the
- 1990s.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>User IDentifier</glossterm>
- <acronym>UID</acronym>
- <glossdef><para>
- The UNIX system user identifier; on older systems a 32-bit unsigned integer, and on newer systems,
- an unsigned 64-bit integer. The UID is used in UNIX-like operating systems for all user-level access
- control.
- </para></glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm>Universal Naming Convention</glossterm>
- <acronym>UNC</acronym>
- <glossdef><para>A syntax for specifying the location of network resources (such as file shares).
- The UNC syntax was developed in the early days of MS DOS 3.x and is used internally by the SMB protocol.
- </para></glossdef>
- </glossentry>
-
-
-
-</glossary>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<preface lang="en-US">
-<title>About the Cover Artwork</title>
-
- <para>
- The cover artwork of this book continues the freedom theme of the first edition of <quote>The Official Samba-3
- HOWTO and Reference Guide</quote>. We may look back upon the past to question the motives of those who have
- gone before us. Seldom do we realise that the past owes us no answer, and despite what we may think of the
- actions of those who have travelled lifes' road before us, we must feel a sense of pride and gratitude for
- those who, in the past, have protected our liberties.
- </para>
-
- <para>
- Developments in information technology continue to move at an alarming pace. Human nature causes us
- to adopt and embrace new developments that appear to answer the needs of the moment, but that can entrap
- us at a future date. There are many examples in the short history of information technology. MS-DOS was
- seen as a tool that liberated users from the tyrany of large computer system operating costs, and that
- made possible the rapid progres we are beneficiaries of today. Yet today we are inclined to look back with
- disdain on MS-DOS as an obsolete and constraining technology that belongs are an era that is best
- forgotten.
- </para>
-
- <para>
- The embrace of Windows networking, Windows NT4, and MS Active Directory in more recent times, may seem
- modern and progressive today, but sooner or later something better will replace them. The current
- preoccupation with extended identity management solutions and with directories is not unexpected.
- The day will come that these too will be evaluated, and what may seem refreshing and powerful may
- be better recogized as the chilly winds of the night. To argue against progress is unthinkable,
- no matter what may lie ahead.
- </para>
-
- <para>
- The development of Samba is moving forwards. The changes since Samba 3.0.0 are amazing, yet many
- users would like to see more and faster progress. The benefits of recent developments can be realized
- quickly, but documentation is necessary to unlock the pandoras' box. It is our hope that this book
- will help the network administrator to rapidly deploy the new features with minimum effort. As you
- deploy and gain mileage from the new enablement, take the time to think through what may lie ahead.
- Above all, take stock of the freedom of choice that Samba provides in your world, and enjoy the new
- potential for seamless interoperability.
- </para>
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="locking">
-<chapterinfo>
- &author.jeremy;
- &author.jelmer;
- &author.jht;
- &author.eroseme;
-</chapterinfo>
-<title>File and Record Locking</title>
-
-<para>
-<indexterm><primary>locking</primary></indexterm>
-One area that causes trouble for many network administrators is locking.
-The extent of the problem is readily evident from searches over the Internet.
-</para>
-
-<sect1>
-<title>Features and Benefits</title>
-
-<para>
-<indexterm><primary>locking semantics</primary></indexterm>
-Samba provides all the same locking semantics that MS Windows clients expect
-and that MS Windows NT4/200x servers also provide.
-</para>
-
-<para>
-<indexterm><primary>locking</primary></indexterm>
-The term <emphasis>locking</emphasis> has exceptionally broad meaning and covers
-a range of functions that are all categorized under this one term.
-</para>
-
-<para>
-<indexterm><primary>opportunistic locking</primary></indexterm>
-<indexterm><primary>locking protocol</primary></indexterm>
-<indexterm><primary>performance advantage</primary></indexterm>
-Opportunistic locking is a desirable feature when it can enhance the
-perceived performance of applications on a networked client. However, the
-opportunistic locking protocol is not robust and therefore can
-encounter problems when invoked beyond a simplistic configuration or
-on extended slow or faulty networks. In these cases, operating
-system management of opportunistic locking and/or recovering from
-repetitive errors can offset the perceived performance advantage that
-it is intended to provide.
-</para>
-
-<para>
-<indexterm><primary>registry</primary></indexterm>
-The MS Windows network administrator needs to be aware that file and record
-locking semantics (behavior) can be controlled either in Samba or by way of registry
-settings on the MS Windows client.
-</para>
-
-<note>
-<para>
-<indexterm><primary>disable locking</primary></indexterm>
-Sometimes it is necessary to disable locking control settings on the Samba
-server as well as on each MS Windows client!
-</para>
-</note>
-
-</sect1>
-
-<sect1>
-<title>Discussion</title>
-
-<para>
-<indexterm><primary>record locking</primary></indexterm>
-<indexterm><primary>deny modes</primary></indexterm>
-There are two types of locking that need to be performed by an SMB server.
-The first is <emphasis>record locking</emphasis> that allows a client to lock
-a range of bytes in an open file. The second is the <emphasis>deny modes</emphasis>
-that are specified when a file is open.
-</para>
-
-<para>
-<indexterm><primary>locking semantics</primary></indexterm>
-<indexterm><primary>record locking</primary></indexterm>
-<indexterm><primary>locking</primary></indexterm>
-<indexterm><primary>byte ranges</primary></indexterm>
-<indexterm><primary>UNIX locking</primary></indexterm>
-Record locking semantics under UNIX are very different from record locking under
-Windows. Versions of Samba before 2.2 have tried to use the native fcntl() UNIX
-system call to implement proper record locking between different Samba clients.
-This cannot be fully correct for several reasons. The simplest is
-that a Windows client is allowed to lock a byte range up to 2^32 or 2^64,
-depending on the client OS. The UNIX locking only supports byte ranges up to 2^31.
-So it is not possible to correctly satisfy a lock request above 2^31. There are
-many more differences, too many to be listed here.
-</para>
-
-<para>
-<indexterm><primary>record locking</primary></indexterm>
-<indexterm><primary>byte-range lock</primary></indexterm>
-Samba 2.2 and above implement record locking completely independently of the
-underlying UNIX system. If a byte-range lock that the client requests happens
-to fall into the range of 0 to 2^31, Samba hands this request down to the UNIX system.
-No other locks can be seen by UNIX, anyway.
-</para>
-
-<para>
-<indexterm><primary>check for locks</primary></indexterm>
-<indexterm><primary>rpc.lockd</primary></indexterm>
-Strictly speaking, an SMB server should check for locks before every read and write call on
-a file. Unfortunately, with the way fcntl() works, this can be slow and may overstress
-the <command>rpc.lockd</command>. This is almost always unnecessary because clients are
-independently supposed to make locking calls before reads and writes if locking is
-important to them. By default, Samba only makes locking calls when explicitly asked
-to by a client, but if you set <smbconfoption name="strict locking">yes</smbconfoption>, it
-will make lock checking calls on <emphasis>every</emphasis> read and write call.
-</para>
-
-<para>
-<indexterm><primary>byte-range locking</primary></indexterm>
-You can also disable byte-range locking completely by using
-<smbconfoption name="locking">no</smbconfoption>.
-This is useful for those shares that do not support locking or do not need it
-(such as CD-ROMs). In this case, Samba fakes the return codes of locking calls to
-tell clients that everything is okay.
-</para>
-
-<para>
-<indexterm><primary>deny modes</primary></indexterm>
-<indexterm><primary>DENY_NONE</primary></indexterm>
-<indexterm><primary>DENY_READ</primary></indexterm>
-<indexterm><primary>DENY_WRITE</primary></indexterm>
-<indexterm><primary>DENY_ALL</primary></indexterm>
-<indexterm><primary>DENY_FCB</primary></indexterm>
-<indexterm><primary>DENY_DOS</primary></indexterm>
-The second class of locking is the <emphasis>deny modes</emphasis>. These
-are set by an application when it opens a file to determine what types of
-access should be allowed simultaneously with its open. A client may ask for
-<constant>DENY_NONE</constant>, <constant>DENY_READ</constant>,
-<constant>DENY_WRITE</constant>, or <constant>DENY_ALL</constant>. There are also special compatibility
-modes called <constant>DENY_FCB</constant> and <constant>DENY_DOS</constant>.
-</para>
-
-<sect2>
-<title>Opportunistic Locking Overview</title>
-
-<para>
-<indexterm><primary>opportunistic locking</primary></indexterm>
-<indexterm><primary>oplocks</primary></indexterm>
-<indexterm><primary>caching</primary></indexterm>
-Opportunistic locking (oplocks) is invoked by the Windows file system
-(as opposed to an API) via registry entries (on the server and the client)
-for the purpose of enhancing network performance when accessing a file
-residing on a server. Performance is enhanced by caching the file
-locally on the client that allows the following:
-</para>
-
-<variablelist>
- <varlistentry><term>Read-ahead:</term>
- <listitem><para>
-<indexterm><primary>Read-ahead</primary></indexterm>
- The client reads the local copy of the file, eliminating network latency.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Write caching:</term>
- <listitem><para>
-<indexterm><primary>Write caching</primary></indexterm>
- The client writes to the local copy of the file, eliminating network latency.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Lock caching:</term>
- <listitem><para>
-<indexterm><primary>Lock caching</primary></indexterm>
- The client caches application locks locally, eliminating network latency.
- </para></listitem>
- </varlistentry>
-</variablelist>
-
-<para>
-<indexterm><primary>performance enhancement</primary></indexterm>
-<indexterm><primary>oplocks</primary></indexterm>
-<indexterm><primary>deny-none</primary></indexterm>
-The performance enhancement of oplocks is due to the opportunity of
-exclusive access to the file &smbmdash; even if it is opened with deny-none &smbmdash;
-because Windows monitors the file's status for concurrent access from
-other processes.
-</para>
-
-<variablelist>
-<title>Windows Defines Four Kinds of Oplocks:</title>
-
- <varlistentry><term>Level1 Oplock</term>
- <listitem><para>
-<indexterm><primary>Level1 Oplock</primary></indexterm>
-<indexterm><primary>redirector</primary></indexterm>
-<indexterm><primary>concurrent access</primary></indexterm>
-<indexterm><primary>cached local file</primary></indexterm>
- The redirector sees that the file was opened with deny
- none (allowing concurrent access), verifies that no
- other process is accessing the file, checks that
- oplocks are enabled, then grants deny-all/read-write/exclusive
- access to the file. The client now performs
- operations on the cached local file.
- </para>
-
- <para>
-<indexterm><primary>oplock break</primary></indexterm>
-<indexterm><primary>flush local locks</primary></indexterm>
-<indexterm><primary>deferred open</primary></indexterm>
-<indexterm><primary>byte-range locking</primary></indexterm>
- If a second process attempts to open the file, the open
- is deferred while the redirector "breaks" the original
- oplock. The oplock break signals the caching client to
- write the local file back to the server, flush the
- local locks, and discard read-ahead data. The break is
- then complete, the deferred open is granted, and the
- multiple processes can enjoy concurrent file access as
- dictated by mandatory or byte-range locking options.
- However, if the original opening process opened the
- file with a share mode other than deny-none, then the
- second process is granted limited or no access, despite
- the oplock break.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Level2 Oplock</term>
- <listitem><para>
-<indexterm><primary>Level2 Oplock</primary></indexterm>
-<indexterm><primary>Level1 oplock</primary></indexterm>
-<indexterm><primary>caching</primary></indexterm>
- Performs like a Level1 oplock, except caching is only
- operative for reads. All other operations are performed
- on the server disk copy of the file.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Filter Oplock</term>
- <listitem><para>
-<indexterm><primary>Filter Oplock</primary></indexterm>
- Does not allow write or delete file access.
- </para></listitem>
- </varlistentry>
-
- <varlistentry><term>Batch Oplock</term>
- <listitem><para>
-<indexterm><primary>Batch Oplock</primary></indexterm>
- Manipulates file openings and closings and allows caching
- of file attributes.
- </para></listitem>
- </varlistentry>
-</variablelist>
-
-<para>
-<indexterm><primary>oplocks</primary></indexterm>
-An important detail is that oplocks are invoked by the file system, not
-an application API. Therefore, an application can close an oplocked
-file, but the file system does not relinquish the oplock. When the
-oplock break is issued, the file system then simply closes the file in
-preparation for the subsequent open by the second process.
-</para>
-
-<para>
-<indexterm><primary>Opportunistic locking</primary></indexterm>
-<indexterm><primary>client-side data caching</primary></indexterm>
-<indexterm><primary>data caching</primary></indexterm>
-<indexterm><primary>oplock break</primary></indexterm>
-<emphasis>Opportunistic locking</emphasis> is actually an improper name for this feature.
-The true benefit of this feature is client-side data caching, and
-oplocks is merely a notification mechanism for writing data back to the
-networked storage disk. The limitation of oplocks is the
-reliability of the mechanism to process an oplock break (notification)
-between the server and the caching client. If this exchange is faulty
-(usually due to timing out for any number of reasons), then the
-client-side caching benefit is negated.
-</para>
-
-<para>
-<indexterm><primary>client-side caching</primary></indexterm>
-The actual decision that a user or administrator should consider is
-whether it is sensible to share among multiple users data that will
-be cached locally on a client. In many cases the answer is no.
-Deciding when to cache or not cache data is the real question, and thus
-oplocks should be treated as a toggle for client-side
-caching. Turn it <quote>on</quote> when client-side caching is desirable and
-reliable. Turn it <quote>off</quote> when client-side caching is redundant,
-unreliable, or counterproductive.
-</para>
-
-<para>
-<indexterm><primary>oplocks</primary></indexterm>
-Oplocks is by default set to <quote>on</quote> by Samba on all
-configured shares, so careful attention should be given to each case to
-determine if the potential benefit is worth the potential for delays.
-The following recommendations will help to characterize the environment
-where oplocks may be effectively configured.
-</para>
-
-<para>
-<indexterm><primary>oplocks</primary></indexterm>
-<indexterm><primary>high-availability</primary></indexterm>
-Windows oplocks is a lightweight performance-enhancing
-feature. It is not a robust and reliable protocol. Every
-implementation of oplocks should be evaluated as a
-trade-off between perceived performance and reliability. Reliability
-decreases as each successive rule above is not enforced. Consider a
-share with oplocks enabled, over a wide-area network, to a client on a
-South Pacific atoll, on a high-availability server, serving a
-mission-critical multiuser corporate database during a tropical
-storm. This configuration will likely encounter problems with oplocks.
-</para>
-
-<para>
-<indexterm><primary>mission-critical</primary></indexterm>
-Oplocks can be beneficial to perceived client performance when treated
-as a configuration toggle for client-side data caching. If the data
-caching is likely to be interrupted, then oplock usage should be
-reviewed. Samba enables oplocks by default on all
-shares. Careful attention should be given to the client usage of
-shared data on the server, the server network reliability, and the
-oplocks configuration of each share.
-In mission-critical, high-availability environments, data integrity is
-often a priority. Complex and expensive configurations are implemented
-to ensure that if a client loses connectivity with a file server, a
-failover replacement will be available immediately to provide
-continuous data availability.
-</para>
-
-<para>
-<indexterm><primary>Windows client failover</primary></indexterm>
-<indexterm><primary>transport connection loss</primary></indexterm>
-Windows client failover behavior is more at risk of application
-interruption than other platforms because it is dependent upon an
-established TCP transport connection. If the connection is interrupted
-&smbmdash; as in a file server failover &smbmdash; a new session must be established.
-It is rare for Windows client applications to be coded to recover
-correctly from a transport connection loss; therefore, most applications
-will experience some sort of interruption &smbmdash; at worst, abort and
-require restarting.
-</para>
-
-<para>
-<indexterm><primary>caching writes</primary></indexterm>
-<indexterm><primary>caching reads</primary></indexterm>
-<indexterm><primary>oplock break</primary></indexterm>
-If a client session has been caching writes and reads locally due to
-oplocks, it is likely that the data will be lost when the
-application restarts or recovers from the TCP interrupt. When the TCP
-connection drops, the client state is lost. When the file server
-recovers, an oplock break is not sent to the client. In this case, the
-work from the prior session is lost. Observing this scenario with
-oplocks disabled and with the client writing data to the file server
-real-time, the failover will provide the data on disk as it
-existed at the time of the disconnect.
-</para>
-
-<para>
-In mission-critical, high-availability environments, careful attention
-should be given to oplocks. Ideally, comprehensive
-testing should be done with all affected applications with oplocks
-enabled and disabled.
-</para>
-
-<sect3>
-<title>Exclusively Accessed Shares</title>
-
-<para>
-Oplocks is most effective when it is confined to shares
-that are exclusively accessed by a single user, or by only one user at
-a time. Because the true value of oplocks is the local
-client caching of data, any operation that interrupts the caching
-mechanism will cause a delay.
-</para>
-
-<para>
-Home directories are the most obvious examples of where the performance
-benefit of oplocks can be safely realized.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Multiple-Accessed Shares or Files</title>
-
-<para>
-As each additional user accesses a file in a share with oplocks
-enabled, the potential for delays and resulting perceived poor
-performance increases. When multiple users are accessing a file on a
-share that has oplocks enabled, the management impact of sending and
-receiving oplock breaks and the resulting latency while other clients
-wait for the caching client to flush data offset the performance gains
-of the caching user.
-</para>
-
-<para>
-As each additional client attempts to access a file with oplocks set,
-the potential performance improvement is negated and eventually results
-in a performance bottleneck.
-</para>
-
-</sect3>
-
-<sect3>
-<title>UNIX or NFS Client-Accessed Files</title>
-
-<para>
-<indexterm><primary>NFS clients</primary></indexterm>
-<indexterm><primary>data corruption</primary></indexterm>
-Local UNIX and NFS clients access files without a mandatory
-file-locking mechanism. Thus, these client platforms are incapable of
-initiating an oplock break request from the server to a Windows client
-that has a file cached. Local UNIX or NFS file access can therefore
-write to a file that has been cached by a Windows client, which
-exposes the file to likely data corruption.
-</para>
-
-<para>
-If files are shared between Windows clients and either local UNIX
-or NFS users, turn oplocks off.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Slow and/or Unreliable Networks</title>
-
-<para>
-<indexterm><primary>performance improvement</primary></indexterm>
-<indexterm><primary>WAN</primary></indexterm>
-<indexterm><primary>latency</primary></indexterm>
-The biggest potential performance improvement for oplocks
-occurs when the client-side caching of reads and writes delivers the
-most differential over sending those reads and writes over the wire.
-This is most likely to occur when the network is extremely slow,
-congested, or distributed (as in a WAN). However, network latency also
-has a high impact on the reliability of the oplock break
-mechanism, and thus increases the likelihood of encountering oplock
-problems that more than offset the potential perceived performance
-gain. Of course, if an oplock break never has to be sent, then this is
-the most advantageous scenario in which to utilize oplocks.
-</para>
-
-<para>
-If the network is slow, unreliable, or a WAN, then do not configure
-oplocks if there is any chance of multiple users
-regularly opening the same file.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Multiuser Databases</title>
-
-<para>
-<indexterm><primary>Multiuser databases</primary></indexterm>
-<indexterm><primary>management bottleneck</primary></indexterm>
-<indexterm><primary>oplocks disabled</primary></indexterm>
-Multiuser databases clearly pose a risk due to their very nature &smbmdash; they are typically heavily
-accessed by numerous users at random intervals. Placing a multiuser database on a share with oplocks enabled
-will likely result in a locking management bottleneck on the Samba server. Whether the database application is
-developed in-house or a commercially available product, ensure that the share has oplocks disabled.
-</para>
-
-</sect3>
-
-<sect3>
-<title>PDM Data Shares</title>
-
-<para>
-<indexterm><primary>PDM</primary></indexterm>
-<indexterm><primary>Process data management</primary></indexterm>
-<indexterm><primary>client-side data caching</primary></indexterm>
-<indexterm><primary>oplocks management</primary></indexterm>
-<indexterm><primary>disabling oplocks</primary></indexterm>
-Process data management (PDM) applications such as IMAN, Enovia, and Clearcase are increasing in usage with
-Windows client platforms and therefore with SMB datastores. PDM applications manage multiuser environments for
-critical data security and access. The typical PDM environment is usually associated with sophisticated client
-design applications that will load data locally as demanded. In addition, the PDM application will usually
-monitor the data state of each client. In this case, client-side data caching is best left to the local
-application and PDM server to negotiate and maintain. It is appropriate to eliminate the client OS from any
-caching tasks, and the server from any oplocks management, by disabling oplocks on the share.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Beware of Force User</title>
-
-<para>
-<indexterm><primary>oplock break</primary></indexterm>
-Samba includes an &smb.conf; parameter called <smbconfoption name="force user"/> that changes the user
-accessing a share from the incoming user to whatever user is defined by the &smb.conf; variable. If oplocks is
-enabled on a share, the change in user access causes an oplock break to be sent to the client, even if the
-user has not explicitly loaded a file. In cases where the network is slow or unreliable, an oplock break can
-become lost without the user even accessing a file. This can cause apparent performance degradation as the
-client continually reconnects to overcome the lost oplock break.
-</para>
-
-<para>
-Avoid the combination of the following:
-</para>
-
-<itemizedlist>
- <listitem><para>
- <smbconfoption name="force user"/> in the &smb.conf; share configuration.
- </para></listitem>
-
- <listitem><para>
- Slow or unreliable networks.
- </para></listitem>
-
- <listitem><para>
- Oplocks enabled.
- </para></listitem>
-</itemizedlist>
-
-</sect3>
-
-<sect3>
-<title>Advanced Samba Oplocks Parameters</title>
-
-<para>
-<indexterm><primary>oplock parameters</primary></indexterm>
-<indexterm><primary>oplock mechanism</primary></indexterm>
-<indexterm><primary>implementing oplocks</primary></indexterm>
-Samba provides oplock parameters that allow the
-administrator to adjust various properties of the oplock mechanism to
-account for timing and usage levels. These parameters provide good
-versatility for implementing oplocks in environments where they would
-likely cause problems. The parameters are
-<smbconfoption name="oplock break wait time"/>, and
-<smbconfoption name="oplock contention limit"/>.
-</para>
-
-<para>
-<indexterm><primary>turn oplocks off</primary></indexterm>
-For most users, administrators, and environments, if these parameters
-are required, then the better option is simply to turn oplocks off.
-The Samba SWAT help text for both parameters reads: <quote>Do not change
-this parameter unless you have read and understood the Samba oplock code.</quote>
-This is good advice.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Mission-Critical, High-Availability</title>
-
-<para>
-In mission-critical, high-availability environments, data integrity is
-often a priority. Complex and expensive configurations are implemented
-to ensure that if a client loses connectivity with a file server, a
-failover replacement will be available immediately to provide
-continuous data availability.
-</para>
-
-<para>
-Windows client failover behavior is more at risk of application
-interruption than other platforms because it is dependent upon an
-established TCP transport connection. If the connection is interrupted
-&smbmdash; as in a file server failover &smbmdash; a new session must be established.
-It is rare for Windows client applications to be coded to recover
-correctly from a transport connection loss; therefore, most applications
-will experience some sort of interruption &smbmdash; at worst, abort and
-require restarting.
-</para>
-
-<para>
-If a client session has been caching writes and reads locally due to
-oplocks, it is likely that the data will be lost when the
-application restarts or recovers from the TCP interrupt. When the TCP
-connection drops, the client state is lost. When the file server
-recovers, an oplock break is not sent to the client. In this case, the
-work from the prior session is lost. Observing this scenario with
-oplocks disabled, if the client was writing data to the file server
-real-time, then the failover will provide the data on disk as it
-existed at the time of the disconnect.
-</para>
-
-<para>
-In mission-critical, high-availability environments, careful attention
-should be given to oplocks. Ideally, comprehensive
-testing should be done with all affected applications with oplocks
-enabled and disabled.
-</para>
-
-</sect3>
-</sect2>
-</sect1>
-
-<sect1>
-<title>Samba Oplocks Control</title>
-
-<para>
-Oplocks is a unique Windows file locking feature. It is
-not really file locking, but is included in most discussions of Windows
-file locking, so is considered a de facto locking feature.
-Oplocks is actually part of the Windows client file
-caching mechanism. It is not a particularly robust or reliable feature
-when implemented on the variety of customized networks that exist in
-enterprise computing.
-</para>
-
-<para>
-Like Windows, Samba implements oplocks as a server-side
-component of the client caching mechanism. Because of the lightweight
-nature of the Windows feature design, effective configuration of
-oplocks requires a good understanding of its limitations,
-and then applying that understanding when configuring data access for
-each particular customized network and client usage state.
-</para>
-
-<para>
-Oplocks essentially means that the client is allowed to download and cache
-a file on its hard drive while making changes; if a second client wants to access the
-file, the first client receives a break and must synchronize the file back to the server.
-This can give significant performance gains in some cases; some programs insist on
-synchronizing the contents of the entire file back to the server for a single change.
-</para>
-
-<para>
-Level1 Oplocks (also known as just plain <quote>oplocks</quote>) is another term for opportunistic locking.
-</para>
-
-<para>
-Level2 Oplocks provides opportunistic locking for a file that will be treated as
-<emphasis>read only</emphasis>. Typically this is used on files that are read-only or
-on files that the client has no initial intention to write to at time of opening the file.
-</para>
-
-<para>
-Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with
-Samba's oplocked files, although this has provided better integration of MS Windows network
-file locking with the underlying OS. SGI IRIX and Linux are the only two OSs that are
-oplock-aware at this time.
-</para>
-
-<para>
-Unless your system supports kernel oplocks, you should disable oplocks if you are
-accessing the same files from both UNIX/Linux and SMB clients. Regardless, oplocks should
-always be disabled if you are sharing a database file (e.g., Microsoft Access) between
-multiple clients, because any break the first client receives will affect synchronization of
-the entire file (not just the single record), which will result in a noticeable performance
-impairment and, more likely, problems accessing the database in the first place. Notably,
-Microsoft Outlook's personal folders (*.pst) react quite badly to oplocks. If in doubt,
-disable oplocks and tune your system from that point.
-</para>
-
-<para>
-If client-side caching is desirable and reliable on your network, you will benefit from
-turning on oplocks. If your network is slow and/or unreliable, or you are sharing your
-files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people
-will be accessing the same files frequently, you probably will not benefit from the overhead
-of your client sending oplock breaks and will instead want to disable oplocks for the share.
-</para>
-
-<para>
-Another factor to consider is the perceived performance of file access. If oplocks provide no
-measurable speed benefit on your network, it might not be worth the hassle of dealing with them.
-</para>
-
-<sect2>
-<title>Example Configuration</title>
-
-<para>
-In the following section we examine two distinct aspects of Samba locking controls.
-</para>
-
-<sect3>
-<title>Disabling Oplocks</title>
-
-<para>
-You can disable oplocks on a per-share basis with the following:
-</para>
-
-<para>
-<smbconfblock>
-<smbconfsection name="[acctdata]"/>
-<smbconfoption name="oplocks">False</smbconfoption>
-<smbconfoption name="level2 oplocks">False</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-The default oplock type is Level1. Level2 oplocks are enabled on a per-share basis
-in the &smb.conf; file.
-</para>
-
-<para>
-Alternately, you could disable oplocks on a per-file basis within the share:
-</para>
-
-<para>
- <smbconfblock>
-<smbconfoption name="veto oplock files">/*.mdb/*.MDB/*.dbf/*.DBF/</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-If you are experiencing problems with oplocks, as apparent from Samba's log entries,
-you may want to play it safe and disable oplocks and Level2 oplocks.
-</para>
-
-</sect3>
-
-<sect3>
-<title>Disabling Kernel Oplocks</title>
-
-<para>
-Kernel oplocks is an &smb.conf; parameter that notifies Samba (if
-the UNIX kernel has the capability to send a Windows client an oplock
-break) when a UNIX process is attempting to open the file that is
-cached. This parameter addresses sharing files between UNIX and
-Windows with oplocks enabled on the Samba server: the UNIX process
-can open the file that is Oplocked (cached) by the Windows client and
-the smbd process will not send an oplock break, which exposes the file
-to the risk of data corruption. If the UNIX kernel has the ability to
-send an oplock break, then the kernel oplocks parameter enables Samba
-to send the oplock break. Kernel oplocks are enabled on a per-server
-basis in the &smb.conf; file.
-</para>
-
-<para>
-<smbconfblock>
-<smbconfoption name="kernel oplocks">yes</smbconfoption>
-</smbconfblock>
-The default is no.
-</para>
-
-<para>
-<emphasis>Veto oplocks</emphasis> is an &smb.conf; parameter that identifies specific files for
-which oplocks are disabled. When a Windows client opens a file that
-has been configured for veto oplocks, the client will not be granted
-the oplock, and all operations will be executed on the original file on
-disk instead of a client-cached file copy. By explicitly identifying
-files that are shared with UNIX processes and disabling oplocks for
-those files, the server-wide oplock configuration can be enabled to
-allow Windows clients to utilize the performance benefit of file
-caching without the risk of data corruption. Veto oplocks can be
-enabled on a per-share basis, or globally for the entire server, in the
-&smb.conf; file as shown in <link linkend="far1"/>.
-</para>
-
-<para>
-<example id="far1">
-<title>Share with Some Files Oplocked</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="veto oplock files">/filename.htm/*.txt/</smbconfoption>
-
-<smbconfsection name="[share_name]"/>
-<smbconfoption name="veto oplock files">/*.exe/filename.ext/</smbconfoption>
-</smbconfblock>
-</example>
-</para>
-
-<para>
-<smbconfoption name="oplock break wait time"/> is an &smb.conf; parameter
-that adjusts the time interval for Samba to reply to an oplock break request. Samba recommends:
-<quote>Do not change this parameter unless you have read and understood the Samba oplock code.</quote>
-Oplock break wait time can only be configured globally in the &smb.conf; file as shown:
-</para>
-
-<para>
- <smbconfblock>
-<smbconfoption name="oplock break wait time"> 0 (default)</smbconfoption>
-</smbconfblock>
-</para>
-
-<para>
-<emphasis>Oplock break contention limit</emphasis> is an &smb.conf; parameter that limits the
-response of the Samba server to grant an oplock if the configured
-number of contending clients reaches the limit specified by the parameter. Samba recommends
-<quote>Do not change this parameter unless you have read and understood the Samba oplock code.</quote>
-Oplock break contention limit can be enabled on a per-share basis, or globally for
-the entire server, in the &smb.conf; file as shown in <link linkend="far3"/>.
-</para>
-
-<para>
-<example id="far3">
-<title>Configuration with Oplock Break Contention Limit</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="oplock break contention limit"> 2 (default)</smbconfoption>
-
-<smbconfsection name="[share_name]"/>
-<smbconfoption name="oplock break contention limit"> 2 (default)</smbconfoption>
-</smbconfblock>
-</example>
-</para>
-
-</sect3>
-</sect2>
-
-</sect1>
-
-<sect1>
-<title>MS Windows Oplocks and Caching Controls</title>
-
-<para>
-There is a known issue when running applications (like Norton Antivirus) on a Windows 2000/ XP
-workstation computer that can affect any application attempting to access shared database files
-across a network. This is a result of a default setting configured in the Windows 2000/XP
-operating system. When a workstation
-attempts to access shared data files located on another Windows 2000/XP computer,
-the Windows 2000/XP operating system will attempt to increase performance by locking the
-files and caching information locally. When this occurs, the application is unable to
-properly function, which results in an <quote>Access Denied</quote>
- error message being displayed during network operations.
-</para>
-
-<para>
-All Windows operating systems in the NT family that act as database servers for data files
-(meaning that data files are stored there and accessed by other Windows PCs) may need to
-have oplocks disabled in order to minimize the risk of data file corruption.
-This includes Windows 9x/Me, Windows NT, Windows 200x, and Windows XP.
-<footnote><para>Microsoft has documented this in Knowledge Base article 300216.</para></footnote>
-</para>
-
-<para>
-If you are using a Windows NT family workstation in place of a server, you must also
-disable oplocks on that workstation. For example, if you use a
-PC with the Windows NT Workstation operating system instead of Windows NT Server, and you
-have data files located on it that are accessed from other Windows PCs, you may need to
-disable oplocks on that system.
-</para>
-
-<para>
-The major difference is the location in the Windows registry where the values for disabling
-oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location
-may be used.
-</para>
-
-<para>
-You can verify (change or add, if necessary) this registry value using the Windows
-Registry Editor. When you change this registry value, you will have to reboot the PC
-to ensure that the new setting goes into effect.
-</para>
-
-<para>
-The location of the client registry entry for oplocks has changed in
-Windows 2000 from the earlier location in Microsoft Windows NT.
-</para>
-
-<note><para>
-Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks
-in earlier versions of Windows.
-</para></note>
-
-<para>
-You can also deny the granting of oplocks by changing the following registry entries:
-</para>
-
-<para>
-<programlisting>
- HKEY_LOCAL_MACHINE\System\
- CurrentControlSet\Services\MRXSmb\Parameters\
-
- OplocksDisabled REG_DWORD 0 or 1
- Default: 0 (not disabled)
-</programlisting>
-</para>
-
-<note><para>
-The OplocksDisabled registry value configures Windows clients to either request or not
-request oplocks on a remote file. To disable oplocks, the value of
- OplocksDisabled must be set to 1.
-</para></note>
-
-<para>
-<programlisting>
- HKEY_LOCAL_MACHINE\System\
- CurrentControlSet\Services\LanmanServer\Parameters
-
- EnableOplocks REG_DWORD 0 or 1
- Default: 1 (Enabled by Default)
-
- EnableOpLockForceClose REG_DWORD 0 or 1
- Default: 0 (Disabled by Default)
-</programlisting>
-</para>
-
-<note><para>
-The EnableOplocks value configures Windows-based servers (including Workstations sharing
-files) to allow or deny oplocks on local files.
-</para></note>
-
-<para>
-To force closure of open oplocks on close or program exit, EnableOpLockForceClose must be set to 1.
-</para>
-
-<para>
-An illustration of how Level2 oplocks work follows:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Station 1 opens the file requesting oplock.
- </para></listitem>
- <listitem><para>
- Since no other station has the file open, the server grants station 1 exclusive oplock.
- </para></listitem>
- <listitem><para>
- Station 2 opens the file requesting oplock.
- </para></listitem>
- <listitem><para>
- Since station 1 has not yet written to the file, the server asks station 1 to break
- to Level2 oplock.
- </para></listitem>
- <listitem><para>
- Station 1 complies by flushing locally buffered lock information to the server.
- </para></listitem>
- <listitem><para>
- Station 1 informs the server that it has broken to level2 Oplock (alternately,
- station 1 could have closed the file).
- </para></listitem>
- <listitem><para>
- The server responds to station 2's open request, granting it Level2 oplock.
- Other stations can likewise open the file and obtain Level2 oplock.
- </para></listitem>
- <listitem><para>
- Station 2 (or any station that has the file open) sends a write request SMB.
- The server returns the write response.
- </para></listitem>
- <listitem><para>
- The server asks all stations that have the file open to break to none, meaning no
- station holds any oplock on the file. Because the workstations can have no cached
- writes or locks at this point, they need not respond to the break-to-none advisory;
- all they need do is invalidate locally cashed read-ahead data.
- </para></listitem>
-</itemizedlist>
-
-<sect2>
-<title>Workstation Service Entries</title>
-
-<para><programlisting>
- \HKEY_LOCAL_MACHINE\System\
- CurrentControlSet\Services\LanmanWorkstation\Parameters
-
- UseOpportunisticLocking REG_DWORD 0 or 1
- Default: 1 (true)
-</programlisting></para>
-
-<para>
-This indicates whether the redirector should use oplocks performance
-enhancement. This parameter should be disabled only to isolate problems.
-</para>
-
-</sect2>
-<sect2>
-<title>Server Service Entries</title>
-
-<para><programlisting>
- \HKEY_LOCAL_MACHINE\System\
- CurrentControlSet\Services\LanmanServer\Parameters
-
- EnableOplocks REG_DWORD 0 or 1
- Default: 1 (true)
-</programlisting></para>
-
-<para>
-This specifies whether the server allows clients to use oplocks on files. Oplocks are a
-significant performance enhancement, but have the potential to cause lost cached
-data on some networks, particularly WANs.
-</para>
-
-<para><programlisting>
- MinLinkThroughput REG_DWORD 0 to infinite bytes per second
- Default: 0
-</programlisting></para>
-
-<para>
-This specifies the minimum link throughput allowed by the server before it disables
-raw I/O and oplocks for this connection.
-</para>
-
-<para><programlisting>
- MaxLinkDelay REG_DWORD 0 to 100,000 seconds
- Default: 60
-</programlisting></para>
-
-<para>
-This specifies the maximum time allowed for a link delay. If delays exceed this number,
-the server disables raw I/O and oplocks for this connection.
-</para>
-
-<para><programlisting>
- OplockBreakWait REG_DWORD 10 to 180 seconds
- Default: 35
-</programlisting></para>
-
-<para>
-This specifies the time that the server waits for a client to respond to an oplock break
-request. Smaller values can allow detection of crashed clients more quickly but can
-potentially cause loss of cached data.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1>
-<title>Persistent Data Corruption</title>
-
-<para>
-If you have applied all of the settings discussed in this chapter but data corruption problems
-and other symptoms persist, here are some additional things to check out.
-</para>
-
-<para>
-We have credible reports from developers that faulty network hardware, such as a single
-faulty network card, can cause symptoms similar to read caching and data corruption.
-If you see persistent data corruption even after repeated re-indexing, you may have to
-rebuild the data files in question. This involves creating a new data file with the
-same definition as the file to be rebuilt and transferring the data from the old file
-to the new one. There are several known methods for doing this that can be found in
-our knowledge base.
-</para>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
-
-<para>
-In some sites locking problems surface as soon as a server is installed; in other sites
-locking problems may not surface for a long time. Almost without exception, when a locking
-problem does surface, it will cause embarrassment and potential data corruption.
-</para>
-
-<para>
-Over the past few years there have been a number of complaints on the Samba mailing lists
-that have claimed that Samba caused data corruption. Three causes have been identified
-so far:
-</para>
-
-<itemizedlist>
- <listitem><para>
- Incorrect configuration of oplocks (incompatible with the application
- being used). This is a common problem even where MS Windows NT4 or MS Windows
- 200x-based servers were in use. It is imperative that the software application vendors'
- instructions for configuration of file locking should be followed. If in doubt,
- disable oplocks on both the server and the client. Disabling of all forms of file
- caching on the MS Windows client may be necessary also.
- </para></listitem>
-
- <listitem><para>
- Defective network cards, cables, or hubs/switches. This is generally a more
- prevalent factor with low-cost networking hardware, although occasionally there
- have also been problems with incompatibilities in more up-market hardware.
- </para></listitem>
-
- <listitem><para>
- There have been some random reports of Samba log files being written over data
- files. This has been reported by very few sites (about five in the past 3 years)
- and all attempts to reproduce the problem have failed. The Samba Team has been
- unable to catch this happening and thus unable to isolate any particular
- cause. Considering the millions of systems that use Samba, for the sites that have
- been affected by this as well as for the Samba Team, this is a frustrating and
- vexing challenge. If you see this type of thing happening, please create a bug
- report on Samba <ulink url="https://bugzilla.samba.org">Bugzilla</ulink> without delay.
- Make sure that you give as much information as you possibly can to help isolate the
- cause and to allow replication of the problem (an essential step in problem isolation and correction).
- </para></listitem>
-</itemizedlist>
-
- <sect2>
- <title>locking.tdb Error Messages</title>
-
- <para>
- <quote>
- We are seeing lots of errors in the Samba logs, like:
- </quote>
-<programlisting>
-tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
- 0x4d6f4b61 at offset=36116
-</programlisting>
-
- <quote>
- What do these mean?
- </quote>
- </para>
-
- <para>
- This error indicates a corrupted tdb. Stop all instances of smbd, delete locking.tdb, and restart smbd.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Problems Saving Files in MS Office on Windows XP</title>
-
-<indexterm><primary>KB 812937</primary></indexterm>
- <para>This is a bug in Windows XP. More information can be
- found in <ulink url="http://support.microsoft.com/?id=812937">Microsoft Knowledge Base article 812937</ulink></para>.
-
- </sect2>
-
- <sect2>
- <title>Long Delays Deleting Files over Network with XP SP1</title>
-
- <para><quote>It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied.</quote></para>
-
-<indexterm><primary>KB 811492</primary></indexterm>
- <para>This is a bug in Windows XP. More information can be found in <ulink url="http://support.microsoft.com/?id=811492">
- Microsoft Knowledge Base article 811492</ulink></para>.
- </sect2>
-
-</sect1>
-
-<sect1>
-<title>Additional Reading</title>
-
-<para>
-You may want to check for an updated documentation regarding file and record locking issues on the Microsoft
-<ulink url="http://support.microsoft.com/">Support</ulink> web site. Additionally, search for the word
-<literal>locking</literal> on the Samba <ulink url="http://www.samba.org/">web</ulink> site.
-</para>
-
-<para>
-Section of the Microsoft MSDN Library on opportunistic locking:
-</para>
-
-<para>
-<indexterm><primary>KB 224992</primary></indexterm>
-Microsoft Knowledge Base, <quote>Maintaining Transactional Integrity with OPLOCKS</quote>,
-Microsoft Corporation, April 1999, <ulink noescape="1" url="http://support.microsoft.com/?id=224992">Microsoft
-KB Article 224992</ulink>.
-</para>
-
-<para>
-<indexterm><primary>KB 296264</primary></indexterm>
-Microsoft Knowledge Base, <quote>Configuring Opportunistic Locking in Windows 2000</quote>,
-Microsoft Corporation, April 2001 <ulink noescape="1" url="http://support.microsoft.com/?id=296264">Microsoft KB Article 296264</ulink>.
-</para>
-
-<para>
-<indexterm><primary>KB 129202</primary></indexterm>
-Microsoft Knowledge Base, <quote>PC Ext: Explanation of Opportunistic Locking on Windows NT</quote>,
-Microsoft Corporation, April 1995 <ulink noescape="1" url="http://support.microsoft.com/?id=129202">Microsoft
-KB Article 129202</ulink>.
-</para>
-
-</sect1>
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<chapter id="msdfs">
-
-<chapterinfo>
- <author>
- <firstname>Shirish</firstname><surname>Kalele</surname>
- <affiliation>
- <orgname>Samba Team & Veritas Software</orgname>
- <address>
- <email>samba@lists.samba.org</email>
- </address>
- </affiliation>
- </author>
- &author.jht;
-
- <pubdate>12 Jul 2000</pubdate>
-</chapterinfo>
-
-<title>Hosting a Microsoft Distributed File System Tree</title>
-
-<sect1>
-<title>Features and Benefits</title>
-
- <para>
-<indexterm><primary>distributed file system</primary><see>DFS</see></indexterm>
-<indexterm><primary>physical locations</primary></indexterm>
-<indexterm><primary>higher availability</primary></indexterm>
-<indexterm><primary>load balancing</primary></indexterm>
-<indexterm><primary>logical directories</primary></indexterm>
- The distributed file system (DFS) provides a means of separating the logical
- view of files and directories that users see from the actual physical locations
- of these resources on the network. It allows for higher availability, smoother
- storage expansion, load balancing, and so on.
- </para>
-
- <para>
-<indexterm><primary>DFS</primary></indexterm>
-<indexterm><primary>DFS tree</primary></indexterm>
-<indexterm><primary>DFS-aware</primary></indexterm>
- For information about DFS, refer to the <ulink
- url="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp">Microsoft
- documentation</ulink>. This document explains how to host a DFS tree on a UNIX machine (for DFS-aware clients
- to browse) using Samba.
- </para>
-
- <para>
-<indexterm><primary>DFS server</primary></indexterm>
-<indexterm><primary>share-level</primary></indexterm>
-<indexterm><primary>DFS junction</primary></indexterm>
-<indexterm><primary>DFS-aware</primary></indexterm>
- A Samba server can be made a DFS server by setting the global Boolean <smbconfoption name="host msdfs"/>
- parameter in the &smb.conf; file. You designate a share as a DFS root using the share-level Boolean
- <smbconfoption name="msdfs root"/> parameter. A DFS root directory on Samba hosts DFS links in the form of
- symbolic links that point to other servers. For example, a symbolic link
- <filename>junction->msdfs:storage1\share1</filename> in the share directory acts as the DFS junction. When
- DFS-aware clients attempt to access the junction link, they are redirected to the storage location (in this
- case, <parameter>\\storage1\share1</parameter>).
- </para>
-
- <para>
-<indexterm><primary>DFS-aware</primary></indexterm>
-<indexterm><primary>DFS tree</primary></indexterm>
-<indexterm><primary>DFS links</primary></indexterm>
-<indexterm><primary>DFS</primary></indexterm>
- DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x.
- <link linkend="dfscfg">The following sample configuration</link> shows how to setup a DFS tree on a Samba server.
- In the <filename>/export/dfsroot</filename> directory, you set up your DFS links to
- other servers on the network.
-<screen>
-&rootprompt;<userinput>cd /export/dfsroot</userinput>
-&rootprompt;<userinput>chown root /export/dfsroot</userinput>
-&rootprompt;<userinput>chmod 755 /export/dfsroot</userinput>
-&rootprompt;<userinput>ln -s msdfs:storageA\\shareA linka</userinput>
-&rootprompt;<userinput>ln -s msdfs:serverB\\share,serverC\\share linkb</userinput>
-</screen>
-</para>
-
-<example id="dfscfg">
-<title>smb.conf with DFS Configured</title>
-<smbconfblock>
-<smbconfsection name="[global]"/>
-<smbconfoption name="netbios name">&example.server.samba;</smbconfoption>
-<smbconfoption name="host msdfs ">yes</smbconfoption>
-
-<smbconfsection name="[dfs]"/>
-<smbconfoption name="path">/export/dfsroot</smbconfoption>
-<smbconfoption name="msdfs root">yes</smbconfoption>
-</smbconfblock>
-</example>
-
- <para>
-<indexterm><primary>DFS root</primary></indexterm>
-<indexterm><primary>msdfs links</primary></indexterm>
-<indexterm><primary>symbolic links</primary></indexterm>
- You should set up the permissions and ownership of the directory acting as the DFS root so that only
- designated users can create, delete, or modify the msdfs links. Also note that symlink names should be all
- lowercase. This limitation exists to have Samba avoid trying all the case combinations to get at the link
- name. Finally, set up the symbolic links to point to the network shares you want and start Samba.
- </para>
-
- <para>
-<indexterm><primary>DFS-aware clients</primary></indexterm>
-<indexterm><primary>DFS tree</primary></indexterm>
- Users on DFS-aware clients can now browse the DFS tree on the Samba server at
- <constant>\\samba\dfs</constant>. Accessing links linka or linkb (which appear as directories to the client)
- takes users directly to the appropriate shares on the network.
- </para>
-
-</sect1>
-
-<sect1>
-<title>Common Errors</title>
- <itemizedlist>
- <listitem><para>Windows clients need to be rebooted
- if a previously mounted non-DFS share is made a DFS
- root, or vice versa. A better way is to introduce a
- new share and make it the DFS root.</para>
- </listitem>
-
- <listitem><para>Currently, there's a restriction that msdfs
- symlink names should all be lowercase.</para>
- </listitem>
-
- <listitem><para>For security purposes, the directory
- acting as the root of the DFS tree should have ownership
- and permissions set so only designated users can
- modify the symbolic links in the directory.</para>
- </listitem>
- </itemizedlist>
-
- <sect2>
- <title>MSDFS UNIX Path Is Case-Critical</title>
-
- <para>
- A network administrator sent advice to the Samba mailing list
- after long sessions trying to determine why DFS was not working.
- His advice is worth noting.
- </para>
-
- <para><quote>
- I spent some time trying to figure out why my particular
- DFS root wasn't working. I noted in the documentation that
- the symlink should be in all lowercase. It should be
- amended that the entire path to the symlink should all be
- in lowercase as well.
- </quote></para>
-
- <para>
- <quote>For example, I had a share defined as such:</quote>
- <smbconfblock>
- <smbconfsection name="[pub]"/>
- <smbconfoption name="path">/export/home/Shares/public_share</smbconfoption>
- <smbconfoption name="msdfs root">yes</smbconfoption>
- </smbconfblock>
- <quote>and I could not make my Windows 9x/Me (with the dfs client installed) follow this symlink:</quote>
- <screen>
- damage1 -> msdfs:damage\test-share
- </screen>
- </para>
-
- <para>
- <quote>Running a debug level of 10 reveals:</quote>
- <programlisting>
- [2003/08/20 11:40:33, 5] msdfs/msdfs.c:is_msdfs_link(176)
- is_msdfs_link: /export/home/shares/public_share/* does not exist.
- </programlisting>
- <quote>Curious. So I changed the directory name from <constant>.../Shares/...</constant> to
- <constant>.../shares/...</constant> (along with my service definition) and it worked!</quote>
- </para>
-
- </sect2>
-
-</sect1>
-
-</chapter>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<preface id="TOSHpreface">
-<title>Preface</title>
-
-<para>
-The editors wish to thank you for your decision to purchase this book.
-The Official Samba-3 HOWTO and Reference Guide is the result of many years
-of accumulation of information, feedback, tips, hints, and happy solutions.
-</para>
-
-<para>
-Please note that this book is a living document, the contents of which are
-constantly being updated. We encourage you to contribute your tips, techniques,
-helpful hints, and your special insight into the Windows networking world to
-help make the next generation of this book even more valuable to Samba users.
-</para>
-
-<para>
-We have made a concerted effort to document more comprehensively than has been
-done previously the information that may help you to better deploy Samba and to
-gain more contented network users.
-</para>
-
-<para>
-This book provides example configurations, it documents key aspects of Microsoft
-Windows networking, provides in-depth insight into the important configuration of
-Samba, and helps to put all of these into a useful framework.
-</para>
-
-<para>
-The most recent electronic versions of this document can be found at
-<ulink noescape="1" url="http://www.samba.org/">http://www.samba.org/</ulink>
-on the <quote>Documentation</quote> page.
-</para>
-
-<para>
-Updates, patches and corrections are most welcome. Please email your contributions
-to any one of the following:
-</para>
-
-<para>
-<simplelist>
-<member><ulink noescape="1" url="mailto:jelmer@samba.org">Jelmer Vernooij (jelmer@samba.org)</ulink></member>
-<member><ulink noescape="1" url="mailto:jht@samba.org">John H. Terpstra (jht@samba.org)</ulink></member>
-<member><ulink noescape="1" url="mailto:jerry@samba.org">Gerald (Jerry) Carter (jerry@samba.org)</ulink></member>
-</simplelist>
-</para>
-
-<para>
-We wish to advise that only original and unencumbered material can be published. Please do not submit
-content that is not your own work unless proof of consent from the copyright holder accompanies your
-submission.
-</para>
-
- <!-- the conventions used in this book -->
- <xi:include href="conventions.xml" xmlns:xi="http://www.w3.org/2003/XInclude" />
-
-
-</preface>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
- <sect1>
- <title>Conventions Used</title>
-
- <para>
- The following notation conventions are used throughout this book:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- TOSHARG2 is used as an abbreviation for the book, <quote>The Official Samba-3
- HOWTO and Reference Guide, Second Edition</quote> Editors: John H. Terpstra and Jelmer R. Vernooij,
- Publisher: Prentice Hall, ISBN: 0131882228.
- </para>
- </listitem>
-
- <listitem>
- <para>
- S3bE2 is used as an abbreviation for the book, <quote>Samba-3 by Example, Second Edition</quote>
- Editors: John H. Terpstra, Publisher: Prentice Hall, ISBN: 013188221X.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Directories and filenames appear in mono-font. For example,
- <filename>/etc/pam.conf</filename>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Executable names are bolded. For example, <command>smbd</command>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Menu items and buttons appear in bold. For example, click <guibutton>Next</guibutton>.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Selecting a menu item is indicated as:
- <menuchoice>
- <guimenu>Start</guimenu>
- <guimenuitem>Control Panel</guimenuitem>
- <guimenuitem>Administrative Tools</guimenuitem>
- <guimenuitem>Active Directory Users and Computers</guimenuitem>
- </menuchoice>
- </para>
- </listitem>
- </itemizedlist>
-
- </sect1>
-
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-<appendix>
- <title>
- <acronym>GNU</acronym> General Public License version 3
- </title>
- <para>
- Version 3, 29 June 2007
- </para>
- <para>
- Copyright © 2007 Free Software Foundation, Inc.
- <ulink url="http://fsf.org/">http://fsf.org/</ulink>
- </para>
- <para>
- Everyone is permitted to copy and distribute verbatim copies of this license
- document, but changing it is not allowed.
- </para>
- <bridgehead renderas="sect1">
- Preamble
- </bridgehead>
- <para>
- The <acronym>GNU</acronym> General Public License is a free, copyleft
- license for software and other kinds of works.
- </para>
- <para>
- The licenses for most software and other practical works are designed to
- take away your freedom to share and change the works. By contrast, the
- <acronym>GNU</acronym> General Public License is intended to guarantee your
- freedom to share and change all versions of a program—to make sure it
- remains free software for all its users. We, the Free Software Foundation,
- use the <acronym>GNU</acronym> General Public License for most of our
- software; it applies also to any other work released this way by its
- authors. You can apply it to your programs, too.
- </para>
- <para>
- When we speak of free software, we are referring to freedom, not price. Our
- General Public Licenses are designed to make sure that you have the freedom
- to distribute copies of free software (and charge for them if you wish),
- that you receive source code or can get it if you want it, that you can
- change the software or use pieces of it in new free programs, and that you
- know you can do these things.
- </para>
- <para>
- To protect your rights, we need to prevent others from denying you these
- rights or asking you to surrender the rights. Therefore, you have certain
- responsibilities if you distribute copies of the software, or if you modify
- it: responsibilities to respect the freedom of others.
- </para>
- <para>
- For example, if you distribute copies of such a program, whether gratis or
- for a fee, you must pass on to the recipients the same freedoms that you
- received. You must make sure that they, too, receive or can get the source
- code. And you must show them these terms so they know their rights.
- </para>
- <para>
- Developers that use the <acronym>GNU</acronym> <acronym>GPL</acronym>
- protect your rights with two steps: (1) assert copyright on the software,
- and (2) offer you this License giving you legal permission to copy,
- distribute and/or modify it.
- </para>
- <para>
- For the developers’ and authors’ protection, the
- <acronym>GPL</acronym> clearly explains that there is no warranty for this
- free software. For both users’ and authors’ sake, the
- <acronym>GPL</acronym> requires that modified versions be marked as changed,
- so that their problems will not be attributed erroneously to authors of
- previous versions.
- </para>
- <para>
- Some devices are designed to deny users access to install or run modified
- versions of the software inside them, although the manufacturer can do so.
- This is fundamentally incompatible with the aim of protecting users’
- freedom to change the software. The systematic pattern of such abuse occurs
- in the area of products for individuals to use, which is precisely where it
- is most unacceptable. Therefore, we have designed this version of the
- <acronym>GPL</acronym> to prohibit the practice for those products. If such
- problems arise substantially in other domains, we stand ready to extend this
- provision to those domains in future versions of the <acronym>GPL</acronym>,
- as needed to protect the freedom of users.
- </para>
- <para>
- Finally, every program is threatened constantly by software patents. States
- should not allow patents to restrict development and use of software on
- general-purpose computers, but in those that do, we wish to avoid the
- special danger that patents applied to a free program could make it
- effectively proprietary. To prevent this, the <acronym>GPL</acronym>
- assures that patents cannot be used to render the program non-free.
- </para>
- <para>
- The precise terms and conditions for copying, distribution and modification
- follow.
- </para>
- <bridgehead>
- TERMS AND CONDITIONS
- </bridgehead>
- <bridgehead renderas="sect1">
- 0. Definitions.
- </bridgehead>
- <para>
- “This License” refers to version 3 of the <acronym>GNU</acronym>
- General Public License.
- </para>
- <para>
- “Copyright” also means copyright-like laws that apply to other
- kinds of works, such as semiconductor masks.
- </para>
- <para>
- “The Program” refers to any copyrightable work licensed under
- this License. Each licensee is addressed as “you”.
- “Licensees” and “recipients” may be individuals or
- organizations.
- </para>
- <para>
- To “modify” a work means to copy from or adapt all or part of
- the work in a fashion requiring copyright permission, other than the making
- of an exact copy. The resulting work is called a “modified
- version” of the earlier work or a work “based on” the
- earlier work.
- </para>
- <para>
- A “covered work” means either the unmodified Program or a work
- based on the Program.
- </para>
- <para>
- To “propagate” a work means to do anything with it that, without
- permission, would make you directly or secondarily liable for infringement
- under applicable copyright law, except executing it on a computer or
- modifying a private copy. Propagation includes copying, distribution (with
- or without modification), making available to the public, and in some
- countries other activities as well.
- </para>
- <para>
- To “convey” a work means any kind of propagation that enables
- other parties to make or receive copies. Mere interaction with a user
- through a computer network, with no transfer of a copy, is not conveying.
- </para>
- <para>
- An interactive user interface displays “Appropriate Legal
- Notices” to the extent that it includes a convenient and prominently
- visible feature that (1) displays an appropriate copyright notice, and (2)
- tells the user that there is no warranty for the work (except to the extent
- that warranties are provided), that licensees may convey the work under this
- License, and how to view a copy of this License. If the interface presents
- a list of user commands or options, such as a menu, a prominent item in the
- list meets this criterion.
- </para>
- <bridgehead renderas="sect1">
- 1. Source Code.
- </bridgehead>
- <para>
- The “source code” for a work means the preferred form of the
- work for making modifications to it. “Object code” means any
- non-source form of a work.
- </para>
- <para>
- A “Standard Interface” means an interface that either is an
- official standard defined by a recognized standards body, or, in the case of
- interfaces specified for a particular programming language, one that is
- widely used among developers working in that language.
- </para>
- <para>
- The “System Libraries” of an executable work include anything,
- other than the work as a whole, that (a) is included in the normal form of
- packaging a Major Component, but which is not part of that Major Component,
- and (b) serves only to enable use of the work with that Major Component, or
- to implement a Standard Interface for which an implementation is available
- to the public in source code form. A “Major Component”, in this
- context, means a major essential component (kernel, window system, and so
- on) of the specific operating system (if any) on which the executable work
- runs, or a compiler used to produce the work, or an object code interpreter
- used to run it.
- </para>
- <para>
- The “Corresponding Source” for a work in object code form means
- all the source code needed to generate, install, and (for an executable
- work) run the object code and to modify the work, including scripts to
- control those activities. However, it does not include the work’s
- System Libraries, or general-purpose tools or generally available free
- programs which are used unmodified in performing those activities but which
- are not part of the work. For example, Corresponding Source includes
- interface definition files associated with source files for the work, and
- the source code for shared libraries and dynamically linked subprograms that
- the work is specifically designed to require, such as by intimate data
- communication or control flow between those subprograms and other parts of
- the work.
- </para>
- <para>
- The Corresponding Source need not include anything that users can regenerate
- automatically from other parts of the Corresponding Source.
- </para>
- <para>
- The Corresponding Source for a work in source code form is that same work.
- </para>
- <bridgehead renderas="sect1">
- 2. Basic Permissions.
- </bridgehead>
- <para>
- All rights granted under this License are granted for the term of copyright
- on the Program, and are irrevocable provided the stated conditions are met.
- This License explicitly affirms your unlimited permission to run the
- unmodified Program. The output from running a covered work is covered by
- this License only if the output, given its content, constitutes a covered
- work. This License acknowledges your rights of fair use or other
- equivalent, as provided by copyright law.
- </para>
- <para>
- You may make, run and propagate covered works that you do not convey,
- without conditions so long as your license otherwise remains in force. You
- may convey covered works to others for the sole purpose of having them make
- modifications exclusively for you, or provide you with facilities for
- running those works, provided that you comply with the terms of this License
- in conveying all material for which you do not control copyright. Those
- thus making or running the covered works for you must do so exclusively on
- your behalf, under your direction and control, on terms that prohibit them
- from making any copies of your copyrighted material outside their
- relationship with you.
- </para>
- <para>
- Conveying under any other circumstances is permitted solely under the
- conditions stated below. Sublicensing is not allowed; section 10 makes it
- unnecessary.
- </para>
- <bridgehead renderas="sect1">
- 3. Protecting Users’ Legal Rights From Anti-Circumvention Law.
- </bridgehead>
- <para>
- No covered work shall be deemed part of an effective technological measure
- under any applicable law fulfilling obligations under article 11 of the WIPO
- copyright treaty adopted on 20 December 1996, or similar laws prohibiting or
- restricting circumvention of such measures.
- </para>
- <para>
- When you convey a covered work, you waive any legal power to forbid
- circumvention of technological measures to the extent such circumvention is
- effected by exercising rights under this License with respect to the covered
- work, and you disclaim any intention to limit operation or modification of
- the work as a means of enforcing, against the work’s users, your or
- third parties’ legal rights to forbid circumvention of technological
- measures.
- </para>
- <bridgehead renderas="sect1">
- 4. Conveying Verbatim Copies.
- </bridgehead>
- <para>
- You may convey verbatim copies of the Program’s source code as you
- receive it, in any medium, provided that you conspicuously and appropriately
- publish on each copy an appropriate copyright notice; keep intact all
- notices stating that this License and any non-permissive terms added in
- accord with section 7 apply to the code; keep intact all notices of the
- absence of any warranty; and give all recipients a copy of this License
- along with the Program.
- </para>
- <para>
- You may charge any price or no price for each copy that you convey, and you
- may offer support or warranty protection for a fee.
- </para>
- <bridgehead renderas="sect1">
- 5. Conveying Modified Source Versions.
- </bridgehead>
- <para>
- You may convey a work based on the Program, or the modifications to produce
- it from the Program, in the form of source code under the terms of section
- 4, provided that you also meet all of these conditions:
- </para>
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>
- The work must carry prominent notices stating that you modified it, and
- giving a relevant date.
- </para>
- </listitem>
- <listitem>
- <para>
- The work must carry prominent notices stating that it is released under
- this License and any conditions added under section 7. This requirement
- modifies the requirement in section 4 to “keep intact all
- notices”.
- </para>
- </listitem>
- <listitem>
- <para>
- You must license the entire work, as a whole, under this License to
- anyone who comes into possession of a copy. This License will therefore
- apply, along with any applicable section 7 additional terms, to the
- whole of the work, and all its parts, regardless of how they are
- packaged. This License gives no permission to license the work in any
- other way, but it does not invalidate such permission if you have
- separately received it.
- </para>
- </listitem>
- <listitem>
- <para>
- If the work has interactive user interfaces, each must display
- Appropriate Legal Notices; however, if the Program has interactive
- interfaces that do not display Appropriate Legal Notices, your work need
- not make them do so.
- </para>
- </listitem>
- </orderedlist>
- <para>
- A compilation of a covered work with other separate and independent works,
- which are not by their nature extensions of the covered work, and which are
- not combined with it such as to form a larger program, in or on a volume of
- a storage or distribution medium, is called an “aggregate” if
- the compilation and its resulting copyright are not used to limit the access
- or legal rights of the compilation’s users beyond what the individual works
- permit. Inclusion of a covered work in an aggregate does not cause
- this License to apply to the other parts of the aggregate.
- </para>
- <bridgehead renderas="sect1">
- 6. Conveying Non-Source Forms.
- </bridgehead>
- <para>
- You may convey a covered work in object code form under the terms of
- sections 4 and 5, provided that you also convey the machine-readable
- Corresponding Source under the terms of this License, in one of these ways:
- </para>
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>
- Convey the object code in, or embodied in, a physical product (including
- a physical distribution medium), accompanied by the Corresponding Source
- fixed on a durable physical medium customarily used for software
- interchange.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey the object code in, or embodied in, a physical product (including
- a physical distribution medium), accompanied by a written offer, valid
- for at least three years and valid for as long as you offer spare parts
- or customer support for that product model, to give anyone who possesses
- the object code either (1) a copy of the Corresponding Source for all
- the software in the product that is covered by this License, on a
- durable physical medium customarily used for software interchange, for a
- price no more than your reasonable cost of physically performing this
- conveying of source, or (2) access to copy the Corresponding Source from
- a network server at no charge.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey individual copies of the object code with a copy of the written
- offer to provide the Corresponding Source. This alternative is allowed
- only occasionally and noncommercially, and only if you received the
- object code with such an offer, in accord with subsection 6b.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey the object code by offering access from a designated place
- (gratis or for a charge), and offer equivalent access to the
- Corresponding Source in the same way through the same place at no
- further charge. You need not require recipients to copy the
- Corresponding Source along with the object code. If the place to copy
- the object code is a network server, the Corresponding Source may be on
- a different server (operated by you or a third party) that supports
- equivalent copying facilities, provided you maintain clear directions
- next to the object code saying where to find the Corresponding Source.
- Regardless of what server hosts the Corresponding Source, you remain
- obligated to ensure that it is available for as long as needed to
- satisfy these requirements.
- </para>
- </listitem>
- <listitem>
- <para>
- Convey the object code using peer-to-peer transmission, provided you
- inform other peers where the object code and Corresponding Source of the
- work are being offered to the general public at no charge under
- subsection 6d.
- </para>
- </listitem>
- </orderedlist>
- <para>
- A separable portion of the object code, whose source code is excluded from
- the Corresponding Source as a System Library, need not be included in
- conveying the object code work.
- </para>
- <para>
- A “User Product” is either (1) a “consumer product”,
- which means any tangible personal property which is normally used for
- personal, family, or household purposes, or (2) anything designed or sold
- for incorporation into a dwelling. In determining whether a product is a
- consumer product, doubtful cases shall be resolved in favor of coverage.
- For a particular product received by a particular user, “normally
- used” refers to a typical or common use of that class of product,
- regardless of the status of the particular user or of the way in which the
- particular user actually uses, or expects or is expected to use, the
- product. A product is a consumer product regardless of whether the product
- has substantial commercial, industrial or non-consumer uses, unless such
- uses represent the only significant mode of use of the product.
- </para>
- <para>
- “Installation Information” for a User Product means any methods,
- procedures, authorization keys, or other information required to install and
- execute modified versions of a covered work in that User Product from a
- modified version of its Corresponding Source. The information must suffice
- to ensure that the continued functioning of the modified object code is in
- no case prevented or interfered with solely because modification has been
- made.
- </para>
- <para>
- If you convey an object code work under this section in, or with, or
- specifically for use in, a User Product, and the conveying occurs as part of
- a transaction in which the right of possession and use of the User Product
- is transferred to the recipient in perpetuity or for a fixed term
- (regardless of how the transaction is characterized), the Corresponding
- Source conveyed under this section must be accompanied by the Installation
- Information. But this requirement does not apply if neither you nor any
- third party retains the ability to install modified object code on the User
- Product (for example, the work has been installed in
- <acronym>ROM</acronym>).
- </para>
- <para>
- The requirement to provide Installation Information does not include a
- requirement to continue to provide support service, warranty, or updates for
- a work that has been modified or installed by the recipient, or for the User
- Product in which it has been modified or installed. Access to a network may
- be denied when the modification itself materially and adversely affects the
- operation of the network or violates the rules and protocols for
- communication across the network.
- </para>
- <para>
- Corresponding Source conveyed, and Installation Information provided, in
- accord with this section must be in a format that is publicly documented
- (and with an implementation available to the public in source code form),
- and must require no special password or key for unpacking, reading or
- copying.
- </para>
- <bridgehead renderas="sect1">
- 7. Additional Terms.
- </bridgehead>
- <para>
- “Additional permissions” are terms that supplement the terms of
- this License by making exceptions from one or more of its conditions.
- Additional permissions that are applicable to the entire Program shall be
- treated as though they were included in this License, to the extent that
- they are valid under applicable law. If additional permissions apply only
- to part of the Program, that part may be used separately under those
- permissions, but the entire Program remains governed by this License
- without regard to the additional permissions.
- </para>
- <para>
- When you convey a copy of a covered work, you may at your option remove any
- additional permissions from that copy, or from any part of it. (Additional
- permissions may be written to require their own removal in certain cases
- when you modify the work.) You may place additional permissions on
- material, added by you to a covered work, for which you have or can give
- appropriate copyright permission.
- </para>
- <para>
- Notwithstanding any other provision of this License, for material you add
- to a covered work, you may (if authorized by the copyright holders of that
- material) supplement the terms of this License with terms:
- </para>
- <orderedlist numeration="loweralpha">
- <listitem>
- <para>
- Disclaiming warranty or limiting liability differently from the terms
- of sections 15 and 16 of this License; or
- </para>
- </listitem>
- <listitem>
- <para>
- Requiring preservation of specified reasonable legal notices or author
- attributions in that material or in the Appropriate Legal Notices
- displayed by works containing it; or
- </para>
- </listitem>
- <listitem>
- <para>
- Prohibiting misrepresentation of the origin of that material, or
- requiring that modified versions of such material be marked in
- reasonable ways as different from the original version; or
- </para>
- </listitem>
- <listitem>
- <para>
- Limiting the use for publicity purposes of names of licensors or
- authors of the material; or
- </para>
- </listitem>
- <listitem>
- <para>
- Declining to grant rights under trademark law for use of some trade
- names, trademarks, or service marks; or
- </para>
- </listitem>
- <listitem>
- <para>
- Requiring indemnification of licensors and authors of that material by
- anyone who conveys the material (or modified versions of it) with
- contractual assumptions of liability to the recipient, for any
- liability that these contractual assumptions directly impose on those
- licensors and authors.
- </para>
- </listitem>
- </orderedlist>
- <para>
- All other non-permissive additional terms are considered “further
- restrictions” within the meaning of section 10. If the Program as
- you received it, or any part of it, contains a notice stating that it is
- governed by this License along with a term that is a further restriction,
- you may remove that term. If a license document contains a further
- restriction but permits relicensing or conveying under this License, you
- may add to a covered work material governed by the terms of that license
- document, provided that the further restriction does not survive such
- relicensing or conveying.
- </para>
- <para>
- If you add terms to a covered work in accord with this section, you must
- place, in the relevant source files, a statement of the additional terms
- that apply to those files, or a notice indicating where to find the
- applicable terms.
- </para>
- <para>
- Additional terms, permissive or non-permissive, may be stated in the form
- of a separately written license, or stated as exceptions; the above
- requirements apply either way.
- </para>
- <bridgehead renderas="sect1">
- 8. Termination.
- </bridgehead>
- <para>
- You may not propagate or modify a covered work except as expressly provided
- under this License. Any attempt otherwise to propagate or modify it is
- void, and will automatically terminate your rights under this License
- (including any patent licenses granted under the third paragraph of section
- 11).
- </para>
- <para>
- However, if you cease all violation of this License, then your license from
- a particular copyright holder is reinstated (a) provisionally, unless and
- until the copyright holder explicitly and finally terminates your license,
- and (b) permanently, if the copyright holder fails to notify you of the
- violation by some reasonable means prior to 60 days after the cessation.
- </para>
- <para>
- Moreover, your license from a particular copyright holder is reinstated
- permanently if the copyright holder notifies you of the violation by some
- reasonable means, this is the first time you have received notice of
- violation of this License (for any work) from that copyright holder, and
- you cure the violation prior to 30 days after your receipt of the notice.
- </para>
- <para>
- Termination of your rights under this section does not terminate the
- licenses of parties who have received copies or rights from you under this
- License. If your rights have been terminated and not permanently
- reinstated, you do not qualify to receive new licenses for the same
- material under section 10.
- </para>
- <bridgehead renderas="sect1">
- 9. Acceptance Not Required for Having Copies.
- </bridgehead>
- <para>
- You are not required to accept this License in order to receive or run a
- copy of the Program. Ancillary propagation of a covered work occurring
- solely as a consequence of using peer-to-peer transmission to receive a
- copy likewise does not require acceptance. However, nothing other than
- this License grants you permission to propagate or modify any covered work.
- These actions infringe copyright if you do not accept this License.
- Therefore, by modifying or propagating a covered work, you indicate your
- acceptance of this License to do so.
- </para>
- <bridgehead renderas="sect1">
- 10. Automatic Licensing of Downstream Recipients.
- </bridgehead>
- <para>
- Each time you convey a covered work, the recipient automatically receives a
- license from the original licensors, to run, modify and propagate that
- work, subject to this License. You are not responsible for enforcing
- compliance by third parties with this License.
- </para>
- <para>
- An “entity transaction” is a transaction transferring control
- of an organization, or substantially all assets of one, or subdividing an
- organization, or merging organizations. If propagation of a covered work
- results from an entity transaction, each party to that transaction who
- receives a copy of the work also receives whatever licenses to the work the
- party’s predecessor in interest had or could give under the previous
- paragraph, plus a right to possession of the Corresponding Source of the
- work from the predecessor in interest, if the predecessor has it or can get
- it with reasonable efforts.
- </para>
- <para>
- You may not impose any further restrictions on the exercise of the rights
- granted or affirmed under this License. For example, you may not impose a
- license fee, royalty, or other charge for exercise of rights granted under
- this License, and you may not initiate litigation (including a cross-claim
- or counterclaim in a lawsuit) alleging that any patent claim is infringed
- by making, using, selling, offering for sale, or importing the Program or
- any portion of it.
- </para>
- <bridgehead renderas="sect1">
- 11. Patents.
- </bridgehead>
- <para>
- A “contributor” is a copyright holder who authorizes use under
- this License of the Program or a work on which the Program is based. The
- work thus licensed is called the contributor’s “contributor
- version”.
- </para>
- <para>
- A contributor’s “essential patent claims” are all patent
- claims owned or controlled by the contributor, whether already acquired or
- hereafter acquired, that would be infringed by some manner, permitted by
- this License, of making, using, or selling its contributor version, but do
- not include claims that would be infringed only as a consequence of further
- modification of the contributor version. For purposes of this definition,
- “control” includes the right to grant patent sublicenses in a
- manner consistent with the requirements of this License.
- </para>
- <para>
- Each contributor grants you a non-exclusive, worldwide, royalty-free patent
- license under the contributor’s essential patent claims, to make, use,
- sell, offer for sale, import and otherwise run, modify and propagate the
- contents of its contributor version.
- </para>
- <para>
- In the following three paragraphs, a “patent license” is any
- express agreement or commitment, however denominated, not to enforce a
- patent (such as an express permission to practice a patent or covenant not
- to sue for patent infringement). To “grant” such a patent
- license to a party means to make such an agreement or commitment not to
- enforce a patent against the party.
- </para>
- <para>
- If you convey a covered work, knowingly relying on a patent license, and the
- Corresponding Source of the work is not available for anyone to copy, free
- of charge and under the terms of this License, through a publicly available
- network server or other readily accessible means, then you must either (1)
- cause the Corresponding Source to be so available, or (2) arrange to deprive
- yourself of the benefit of the patent license for this particular work, or
- (3) arrange, in a manner consistent with the requirements of this License,
- to extend the patent license to downstream recipients. “Knowingly
- relying” means you have actual knowledge that, but for the patent
- license, your conveying the covered work in a country, or your
- recipient’s use of the covered work in a country, would infringe one
- or more identifiable patents in that country that you have reason to believe
- are valid.
- </para>
- <para>
- If, pursuant to or in connection with a single transaction or arrangement,
- you convey, or propagate by procuring conveyance of, a covered work, and
- grant a patent license to some of the parties receiving the covered work
- authorizing them to use, propagate, modify or convey a specific copy of the
- covered work, then the patent license you grant is automatically extended to
- all recipients of the covered work and works based on it.
- </para>
- <para>
- A patent license is “discriminatory” if it does not include
- within the scope of its coverage, prohibits the exercise of, or is
- conditioned on the non-exercise of one or more of the rights that are
- specifically granted under this License. You may not convey a covered work
- if you are a party to an arrangement with a third party that is in the
- business of distributing software, under which you make payment to the third
- party based on the extent of your activity of conveying the work, and under
- which the third party grants, to any of the parties who would receive the
- covered work from you, a discriminatory patent license (a) in connection
- with copies of the covered work conveyed by you (or copies made from those
- copies), or (b) primarily for and in connection with specific products or
- compilations that contain the covered work, unless you entered into that
- arrangement, or that patent license was granted, prior to 28 March 2007.
- </para>
- <para>
- Nothing in this License shall be construed as excluding or limiting any
- implied license or other defenses to infringement that may otherwise be
- available to you under applicable patent law.
- </para>
- <bridgehead renderas="sect1">
- 12. No Surrender of Others’ Freedom.
- </bridgehead>
- <para>
- If conditions are imposed on you (whether by court order, agreement or
- otherwise) that contradict the conditions of this License, they do not
- excuse you from the conditions of this License. If you cannot convey a
- covered work so as to satisfy simultaneously your obligations under this
- License and any other pertinent obligations, then as a consequence you may
- not convey it at all. For example, if you agree to terms that obligate you
- to collect a royalty for further conveying from those to whom you convey the
- Program, the only way you could satisfy both those terms and this License
- would be to refrain entirely from conveying the Program.
- </para>
- <bridgehead renderas="sect1">
- 13. Use with the <acronym>GNU</acronym> Affero General Public License.
- </bridgehead>
- <para>
- Notwithstanding any other provision of this License, you have permission to
- link or combine any covered work with a work licensed under version 3 of the
- <acronym>GNU</acronym> Affero General Public License into a single combined
- work, and to convey the resulting work. The terms of this License will
- continue to apply to the part which is the covered work, but the special
- requirements of the <acronym>GNU</acronym> Affero General Public License,
- section 13, concerning interaction through a network will apply to the
- combination as such.
- </para>
- <bridgehead renderas="sect1">
- 14. Revised Versions of this License.
- </bridgehead>
- <para>
- The Free Software Foundation may publish revised and/or new versions of the
- <acronym>GNU</acronym> General Public License from time to time. Such new
- versions will be similar in spirit to the present version, but may differ in
- detail to address new problems or concerns.
- </para>
- <para>
- Each version is given a distinguishing version number. If the Program
- specifies that a certain numbered version of the <acronym>GNU</acronym>
- General Public License “or any later version” applies to it, you
- have the option of following the terms and conditions either of that
- numbered version or of any later version published by the Free Software
- Foundation. If the Program does not specify a version number of the
- <acronym>GNU</acronym> General Public License, you may choose any version
- ever published by the Free Software Foundation.
- </para>
- <para>
- If the Program specifies that a proxy can decide which future versions of
- the <acronym>GNU</acronym> General Public License can be used, that
- proxy’s public statement of acceptance of a version permanently
- authorizes you to choose that version for the Program.
- </para>
- <para>
- Later license versions may give you additional or different permissions.
- However, no additional obligations are imposed on any author or copyright
- holder as a result of your choosing to follow a later version.
- </para>
- <bridgehead renderas="sect1">
- 15. Disclaimer of Warranty.
- </bridgehead>
- <para>
- THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
- LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
- OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF
- ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
- THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
- YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
- NECESSARY SERVICING, REPAIR OR CORRECTION.
- </para>
- <bridgehead renderas="sect1">
- 16. Limitation of Liability.
- </bridgehead>
- <para>
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
- ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
- PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
- GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE
- OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA
- OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
- PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
- EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGES.
- </para>
- <bridgehead renderas="sect1">
- 17. Interpretation of Sections 15 and 16.
- </bridgehead>
- <para>
- If the disclaimer of warranty and limitation of liability provided above
- cannot be given local legal effect according to their terms, reviewing
- courts shall apply local law that most closely approximates an absolute
- waiver of all civil liability in connection with the Program, unless a
- warranty or assumption of liability accompanies a copy of the Program in
- return for a fee.
- </para>
- <bridgehead>
- END OF TERMS AND CONDITIONS
- </bridgehead>
- <bridgehead renderas="sect1">
- How to Apply These Terms to Your New Programs
- </bridgehead>
- <para>
- If you develop a new program, and you want it to be of the greatest possible
- use to the public, the best way to achieve this is to make it free software
- which everyone can redistribute and change under these terms.
- </para>
- <para>
- To do so, attach the following notices to the program. It is safest to
- attach them to the start of each source file to most effectively state the
- exclusion of warranty; and each file should have at least the
- “copyright” line and a pointer to where the full notice is
- found.
- </para>
- <screen>
-<replaceable>one line to give the program’s name and a brief idea of what it does.</replaceable>
-Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
-
-This program is free software: you can redistribute it and/or modify
-it under the terms of the <acronym>GNU</acronym> General Public License as published by
-the Free Software Foundation, either version 3 of the License, or
-(at your option) any later version.
-
-This program 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. See the
-<acronym>GNU</acronym> General Public License for more details.
-
-You should have received a copy of the <acronym>GNU</acronym> General Public License
-along with this program. If not, see <ulink url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
- </screen>
- <para>
- Also add information on how to contact you by electronic and paper mail.
- </para>
- <para>
- If the program does terminal interaction, make it output a short notice like
- this when it starts in an interactive mode:
- </para>
- <screen>
-<replaceable>program</replaceable> Copyright (C) <replaceable>year</replaceable> <replaceable>name of author</replaceable>
-This program comes with ABSOLUTELY NO WARRANTY; for details type ‘<literal>show w</literal>’.
-This is free software, and you are welcome to redistribute it
-under certain conditions; type ‘<literal>show c</literal>’ for details.
- </screen>
- <para>
- The hypothetical commands ‘<literal>show w</literal>’ and
- ‘<literal>show c</literal>’ should show the appropriate parts of
- the General Public License. Of course, your program’s commands might be
- different; for a GUI interface, you would use an “about box”.
- </para>
- <para>
- You should also get your employer (if you work as a programmer) or school,
- if any, to sign a “copyright disclaimer” for the program, if
- necessary. For more information on this, and how to apply and follow the
- <acronym>GNU</acronym> <acronym>GPL</acronym>, see <ulink
- url="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</ulink>.
- </para>
- <para>
- The <acronym>GNU</acronym> General Public License does not permit
- incorporating your program into proprietary programs. If your program is a
- subroutine library, you may consider it more useful to permit linking
- proprietary applications with the library. If this is what you want to do,
- use the <acronym>GNU</acronym> Lesser General Public License instead of this
- License. But first, please read <ulink
- url="http://www.gnu.org/philosophy/why-not-lgpl.html">http://www.gnu.org/philosophy/why-not-lgpl.html</ulink>.
- </para>
-</appendix>
+++ /dev/null
-- Broadcast messaging
-- Profile Recovery
-- smbfs/cifsfs
-- Anti-Virus
-- Krb5 TGT usage
-- Static WINS entries
-- Disabling Roaming Profiles
-- BAD SID issues
-- VPN
-- incorporation in apache and squid (ntlm_auth)
-- smbldap-tools
-- kinit issues (you need to have kerberos updated in order to run win2k3, etc)
-- pam_smb and why not to use it
-- quotas
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="30.1cm"
- height="13.348cm"
- viewBox="1.35 1.15 31.45 14.498"
- id="svg2">
- <defs
- id="defs99" />
- <rect
- width="4.4000001"
- height="1.1"
- x="1.4"
- y="1.2"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="1.4"
- y="1.2"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3"
- y="2"
- id="text8"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">type</text>
- <rect
- width="4.4000001"
- height="1.1"
- x="6.5"
- y="1.2"
- id="rect10"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="6.5"
- y="1.2"
- id="rect12"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="7.8000002"
- y="2"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">users</text>
- <rect
- width="4.4000001"
- height="1.1"
- x="11.5"
- y="1.2"
- id="rect16"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="11.5"
- y="1.2"
- id="rect18"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="12.6"
- y="2"
- id="text20"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">group</text>
- <rect
- width="4.4000001"
- height="1.1"
- x="16.5"
- y="1.2"
- id="rect22"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="16.5"
- y="1.2"
- id="rect24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="17.700001"
- y="2"
- id="text26"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">others</text>
- <rect
- width="4.4000001"
- height="1.1"
- x="1.4"
- y="2.7"
- id="rect28"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="1.4"
- y="2.7"
- id="rect30"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3.2"
- y="3.5"
- id="text32"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">d l</text>
- <rect
- width="4.4000001"
- height="1.1"
- x="6.5"
- y="2.7"
- id="rect34"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="6.5"
- y="2.7"
- id="rect36"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="7.9000001"
- y="3.5"
- id="text38"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">r w x</text>
- <rect
- width="4.4000001"
- height="1.1"
- x="11.5"
- y="2.7"
- id="rect40"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="11.5"
- y="2.7"
- id="rect42"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="13"
- y="3.5"
- id="text44"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">r w x</text>
- <rect
- width="4.4000001"
- height="1.1"
- x="16.5"
- y="2.7"
- id="rect46"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.4000001"
- height="1.1"
- x="16.5"
- y="2.7"
- id="rect48"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="17.9"
- y="3.5"
- id="text50"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">r w x</text>
- <text
- x="22.700001"
- y="6.0999999"
- id="text52"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Execute, List files</text>
- <text
- x="22.700001"
- y="6.9000001"
- id="text54"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Write, Create files</text>
- <text
- x="22.700001"
- y="7.6999998"
- id="text56"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Read, Read files</text>
- <text
- x="22.700001"
- y="8.5"
- id="text58"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Execute, List files</text>
- <text
- x="22.700001"
- y="9.3000002"
- id="text60"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Write, Create files</text>
- <text
- x="22.700001"
- y="10.1"
- id="text62"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Read, Read files</text>
- <text
- x="22.700001"
- y="10.9"
- id="text64"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Execute, List files</text>
- <text
- x="22.700001"
- y="11.7"
- id="text66"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Write, Create files</text>
- <text
- x="22.700001"
- y="12.5"
- id="text68"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Can Read, Read files</text>
- <text
- x="22.700001"
- y="13.3"
- id="text70"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Is a symbolic link</text>
- <text
- x="22.700001"
- y="14.1"
- id="text72"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:monospace">Is a directory</text>
- <line
- x1="18.700001"
- y1="3.8"
- x2="18.700001"
- y2="6.6999998"
- stroke="#000000"
- stroke-width="0.100"
- id="line74"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="18.700001"
- y1="6.6999998"
- x2="22.1"
- y2="6.6999998"
- stroke="#000000"
- stroke-width="0.100"
- id="line76"
- style="stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="18.000,3.800 18.000,3.800 18.000,7.500 22.100,7.500 "
- id="polyline78"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="14.400,3.700 14.400,3.700 14.400,8.300 22.100,8.300 "
- id="polyline80"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="13.700,3.800 13.700,3.800 13.700,9.100 22.100,9.100 "
- id="polyline82"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="13.100,3.800 13.000,3.800 13.000,9.900 22.100,9.900 "
- id="polyline84"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="9.200,3.800 9.300,3.800 9.300,10.700 22.100,10.700 "
- id="polyline86"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="8.700,3.800 8.800,3.800 8.800,11.500 22.100,11.500 "
- id="polyline88"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="8.000,3.800 8.100,3.800 8.100,12.300 22.100,12.300 "
- id="polyline90"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="3.900,3.800 3.900,3.800 3.900,13.100 22.100,13.100 "
- id="polyline92"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="3.300,3.800 3.300,3.800 3.300,13.900 22.100,13.900 "
- id="polyline94"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="19.200,3.800 19.200,3.800 19.200,5.900 22.100,5.900 "
- id="polyline96"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="29.107cm"
- height="18.84cm"
- viewBox="-2.808 0.758 26.299 19.598"
- id="svg2">
- <defs
- id="defs689" />
- <rect
- width="1.534"
- height="3.5799999"
- x="2.007"
- y="2.0139999"
- id="rect4"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.534"
- height="3.5799999"
- x="2.007"
- y="2.0139999"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.227"
- height="0.40900001"
- x="2.1600001"
- y="2.2279999"
- id="rect8"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.227"
- height="0.40900001"
- x="2.1600001"
- y="2.638"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.227"
- height="0.40900001"
- x="2.1600001"
- y="3.0469999"
- id="rect12"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.227"
- height="0.40900001"
- x="2.1600001"
- y="3.4560001"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76700002"
- height="0.245"
- x="2.1600001"
- y="3.947"
- id="rect16"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="3.3110001"
- cy="3.9879999"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse18"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="3.3110001"
- cy="3.9879999"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse20"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="3.3110001"
- cy="4.151"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse22"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="3.3110001"
- cy="4.151"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse24"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.184"
- height="0.164"
- x="3.0039999"
- y="4.0279999"
- id="rect26"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.184"
- height="0.164"
- x="3.0039999"
- y="4.0279999"
- id="rect28"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.263,4.519 L 2.263,5.414"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.518,4.519 L 2.518,5.414"
- id="path32"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.774,4.519 L 2.774,5.414"
- id="path34"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 3.03,4.519 L 3.03,5.414"
- id="path36"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 3.285,4.519 L 3.285,5.414"
- id="path38"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 3.541,4.519 L 3.541,5.414"
- id="path40"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="1.7,5.9 2.007,5.286 2.007,5.593 3.541,5.593 3.541,5.286 3.95,5.9 1.7,5.9 "
- id="polygon42"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="1.7,5.9 2.007,5.286 2.007,5.593 3.541,5.593 3.541,5.286 3.95,5.9 1.7,5.9 "
- id="polygon44"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.595"
- height="3.7219999"
- x="6.119"
- y="2"
- id="rect46"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.595"
- height="3.7219999"
- x="6.119"
- y="2"
- id="rect48"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.276"
- height="0.42500001"
- x="6.2789998"
- y="2.223"
- id="rect50"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.276"
- height="0.42500001"
- x="6.2789998"
- y="2.6489999"
- id="rect52"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.276"
- height="0.42500001"
- x="6.2789998"
- y="3.0739999"
- id="rect54"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.276"
- height="0.42500001"
- x="6.2789998"
- y="3.4990001"
- id="rect56"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.79799998"
- height="0.255"
- x="6.2789998"
- y="4.0100002"
- id="rect58"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="7.4749999"
- cy="4.052"
- rx="0.056000002"
- ry="0.056000002"
- id="ellipse60"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="7.4749999"
- cy="4.052"
- rx="0.056000002"
- ry="0.056000002"
- id="ellipse62"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="7.4749999"
- cy="4.223"
- rx="0.056000002"
- ry="0.056000002"
- id="ellipse64"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="7.4749999"
- cy="4.223"
- rx="0.056000002"
- ry="0.056000002"
- id="ellipse66"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.191"
- height="0.17"
- x="7.1560001"
- y="4.0949998"
- id="rect68"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.191"
- height="0.17"
- x="7.1560001"
- y="4.0949998"
- id="rect70"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.385,4.605 L 6.385,5.536"
- id="path72"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.651,4.605 L 6.651,5.536"
- id="path74"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 6.917,4.605 L 6.917,5.536"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 7.182,4.605 L 7.182,5.536"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 7.448,4.605 L 7.448,5.536"
- id="path80"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 7.714,4.605 L 7.714,5.536"
- id="path82"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="5.8,6.041 6.119,5.403 6.119,5.722 7.714,5.722 7.714,5.403 8.139,6.041 5.8,6.041 "
- id="polygon84"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="5.8,6.041 6.119,5.403 6.119,5.722 7.714,5.722 7.714,5.403 8.139,6.041 5.8,6.041 "
- id="polygon86"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.618"
- height="3.776"
- x="10.124"
- y="1.9"
- id="rect88"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.618"
- height="3.776"
- x="10.124"
- y="1.9"
- id="rect90"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.295"
- height="0.43200001"
- x="10.286"
- y="2.1270001"
- id="rect92"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.295"
- height="0.43200001"
- x="10.286"
- y="2.5580001"
- id="rect94"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.295"
- height="0.43200001"
- x="10.286"
- y="2.99"
- id="rect96"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.295"
- height="0.43200001"
- x="10.286"
- y="3.421"
- id="rect98"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.80900002"
- height="0.259"
- x="10.286"
- y="3.9389999"
- id="rect100"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="11.499"
- cy="3.9820001"
- rx="0.057"
- ry="0.057"
- id="ellipse102"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="11.499"
- cy="3.9820001"
- rx="0.057"
- ry="0.057"
- id="ellipse104"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="11.499"
- cy="4.1550002"
- rx="0.057"
- ry="0.057"
- id="ellipse106"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="11.499"
- cy="4.1550002"
- rx="0.057"
- ry="0.057"
- id="ellipse108"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.19400001"
- height="0.17299999"
- x="11.176"
- y="4.026"
- id="rect110"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.19400001"
- height="0.17299999"
- x="11.176"
- y="4.026"
- id="rect112"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.393,4.543 L 10.393,5.487"
- id="path114"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.663,4.543 L 10.663,5.487"
- id="path116"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.933,4.543 L 10.933,5.487"
- id="path118"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 11.203,4.543 L 11.203,5.487"
- id="path120"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 11.472,4.543 L 11.472,5.487"
- id="path122"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 11.742,4.543 L 11.742,5.487"
- id="path124"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="9.8,6 10.124,5.353 10.124,5.676 11.742,5.676 11.742,5.353 12.174,6 9.8,6 "
- id="polygon126"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="9.8,6 10.124,5.353 10.124,5.676 11.742,5.676 11.742,5.353 12.174,6 9.8,6 "
- id="polygon128"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="2.2"
- y="1.4"
- id="text130"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_A</text>
- <text
- x="6.1999998"
- y="1.4"
- id="text132"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_B</text>
- <text
- x="10.1"
- y="1.3"
- id="text134"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_C (DMB)</text>
- <rect
- width="1.631"
- height="3.806"
- x="14.726"
- y="1.8"
- id="rect136"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.631"
- height="3.806"
- x="14.726"
- y="1.8"
- id="rect138"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.3049999"
- height="0.435"
- x="14.889"
- y="2.0280001"
- id="rect140"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3049999"
- height="0.435"
- x="14.889"
- y="2.4630001"
- id="rect142"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3049999"
- height="0.435"
- x="14.889"
- y="2.898"
- id="rect144"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.3049999"
- height="0.435"
- x="14.889"
- y="3.3329999"
- id="rect146"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.815"
- height="0.26100001"
- x="14.889"
- y="3.855"
- id="rect148"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="16.113001"
- cy="3.8989999"
- rx="0.057"
- ry="0.057"
- id="ellipse150"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="16.113001"
- cy="3.8989999"
- rx="0.057"
- ry="0.057"
- id="ellipse152"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="16.113001"
- cy="4.073"
- rx="0.057"
- ry="0.057"
- id="ellipse154"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="16.113001"
- cy="4.073"
- rx="0.057"
- ry="0.057"
- id="ellipse156"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.19599999"
- height="0.17399999"
- x="15.786"
- y="3.9419999"
- id="rect158"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.19599999"
- height="0.17399999"
- x="15.786"
- y="3.9419999"
- id="rect160"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.998,4.464 L 14.998,5.415"
- id="path162"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.27,4.464 L 15.27,5.415"
- id="path164"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.542,4.464 L 15.542,5.415"
- id="path166"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.814,4.464 L 15.814,5.415"
- id="path168"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 16.085,4.464 L 16.085,5.415"
- id="path170"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 16.357,4.464 L 16.357,5.415"
- id="path172"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="14.4,5.932 14.726,5.279 14.726,5.606 16.357,5.606 16.357,5.279 16.792,5.932 14.4,5.932 "
- id="polygon174"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="14.4,5.932 14.726,5.279 14.726,5.606 16.357,5.606 16.357,5.279 16.792,5.932 14.4,5.932 "
- id="polygon176"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.9"
- y1="7.0999999"
- x2="2.5999999"
- y2="7.0999999"
- stroke="#000000"
- stroke-width="0.100"
- id="line178"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="2.825"
- y1="5.9000001"
- x2="2.8"
- y2="7"
- stroke="#000000"
- stroke-width="0.100"
- id="line180"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="6.9699998"
- y1="6.0409999"
- x2="6.9000001"
- y2="7"
- stroke="#000000"
- stroke-width="0.100"
- id="line182"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="10.987"
- y1="6"
- x2="11"
- y2="7.0999999"
- stroke="#000000"
- stroke-width="0.100"
- id="line184"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="15.596"
- y1="5.9320002"
- x2="15.6"
- y2="7.0999999"
- stroke="#000000"
- stroke-width="0.100"
- id="line186"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.645"
- height="3.839"
- x="18.929001"
- y="1.85"
- id="rect188"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.645"
- height="3.839"
- x="18.929001"
- y="1.85"
- id="rect190"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.316"
- height="0.43900001"
- x="19.094"
- y="2.0799999"
- id="rect192"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.316"
- height="0.43900001"
- x="19.094"
- y="2.5190001"
- id="rect194"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.316"
- height="0.43900001"
- x="19.094"
- y="2.9579999"
- id="rect196"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.316"
- height="0.43900001"
- x="19.094"
- y="3.3970001"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.82300001"
- height="0.26300001"
- x="19.094"
- y="3.9230001"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="20.327999"
- cy="3.967"
- rx="0.057999998"
- ry="0.057999998"
- id="ellipse202"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="20.327999"
- cy="3.967"
- rx="0.057999998"
- ry="0.057999998"
- id="ellipse204"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="20.327999"
- cy="4.1420002"
- rx="0.057999998"
- ry="0.057999998"
- id="ellipse206"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="20.327999"
- cy="4.1420002"
- rx="0.057999998"
- ry="0.057999998"
- id="ellipse208"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.197"
- height="0.176"
- x="19.999001"
- y="4.0110002"
- id="rect210"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.197"
- height="0.176"
- x="19.999001"
- y="4.0110002"
- id="rect212"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 19.203,4.537 L 19.203,5.497"
- id="path214"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 19.478,4.537 L 19.478,5.497"
- id="path216"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 19.752,4.537 L 19.752,5.497"
- id="path218"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 20.026,4.537 L 20.026,5.497"
- id="path220"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 20.3,4.537 L 20.3,5.497"
- id="path222"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 20.574,4.537 L 20.574,5.497"
- id="path224"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="18.6,6.018 18.929,5.36 18.929,5.689 20.574,5.689 20.574,5.36 21.013,6.018 18.6,6.018 "
- id="polygon226"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="18.6,6.018 18.929,5.36 18.929,5.689 20.574,5.689 20.574,5.36 21.013,6.018 18.6,6.018 "
- id="polygon228"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.799999"
- y1="7.0999999"
- x2="19.806999"
- y2="6.0180001"
- stroke="#000000"
- stroke-width="0.100"
- id="line230"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="14.6"
- y="1.3"
- id="text232"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_D</text>
- <text
- x="18.9"
- y="1.3"
- id="text234"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N1_E</text>
- <line
- x1="2.5999999"
- y1="7"
- x2="2.5999999"
- y2="8.6000004"
- stroke="#000000"
- stroke-width="0.100"
- id="line236"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.3499999"
- height="2.3499999"
- x="1.4"
- y="8.6000004"
- id="rect238"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="2.3499999"
- height="2.3499999"
- x="1.4"
- y="8.6000004"
- id="rect240"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.3499999"
- height="2.3499999"
- x="1.4"
- y="8.6000004"
- id="rect242"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 2.72,8.98 C 2.72,10.155 2.955,9.92 1.78,9.92"
- id="path244"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 2.72,8.98 C 2.72,10.155 2.955,9.92 1.78,9.92"
- id="path246"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="2.833,9.164 2.716,8.929 2.599,9.164 2.833,9.164 "
- id="polygon248"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="2.833,9.164 2.716,8.929 2.599,9.164 2.833,9.164 "
- id="polygon250"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="1.964,9.798 1.729,9.916 1.964,10.034 1.964,9.798 "
- id="polygon252"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="1.964,9.798 1.729,9.916 1.964,10.034 1.964,9.798 "
- id="polygon254"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 3.418,9.641 C 2.243,9.641 2.478,9.406 2.478,10.581"
- id="path256"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 3.418,9.641 C 2.243,9.641 2.478,9.406 2.478,10.581"
- id="path258"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="3.21,9.752 3.445,9.634 3.21,9.516 3.21,9.752 "
- id="polygon260"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.21,9.752 3.445,9.634 3.21,9.516 3.21,9.752 "
- id="polygon262"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="2.34,10.386 2.458,10.621 2.575,10.386 2.34,10.386 "
- id="polygon264"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="2.34,10.386 2.458,10.621 2.575,10.386 2.34,10.386 "
- id="polygon266"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="4.5"
- y="10.1"
- id="text268"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Router 1</text>
- <text
- x="9.8999996"
- y="8.1000004"
- id="text270"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Subnet 1</text>
- <line
- x1="19.9"
- y1="7"
- x2="19.9"
- y2="8.6999998"
- stroke="#000000"
- stroke-width="0.100"
- id="line272"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.4000001"
- height="2.4000001"
- x="18.700001"
- y="8.6999998"
- id="rect274"
- style="fill:#9f9f9f;stroke:none;stroke-width:0" />
- <rect
- width="2.4000001"
- height="2.4000001"
- x="18.700001"
- y="8.6999998"
- id="rect276"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.4000001"
- height="2.4000001"
- x="18.700001"
- y="8.6999998"
- id="rect278"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 20.048,9.088 C 20.048,10.288 20.288,10.048 19.088,10.048"
- id="path280"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 20.048,9.088 C 20.048,10.288 20.288,10.048 19.088,10.048"
- id="path282"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="20.164,9.276 20.044,9.036 19.924,9.276 20.164,9.276 "
- id="polygon284"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="20.164,9.276 20.044,9.036 19.924,9.276 20.164,9.276 "
- id="polygon286"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.276,9.924 19.036,10.044 19.276,10.164 19.276,9.924 "
- id="polygon288"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.276,9.924 19.036,10.044 19.276,10.164 19.276,9.924 "
- id="polygon290"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <path
- d="M 20.761,9.764 C 19.561,9.764 19.801,9.524 19.801,10.724"
- id="path292"
- style="fill:none;stroke:#ffffff;stroke-width:0.13" />
- <path
- d="M 20.761,9.764 C 19.561,9.764 19.801,9.524 19.801,10.724"
- id="path294"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <polygon
- points="20.548,9.876 20.788,9.756 20.548,9.636 20.548,9.876 "
- id="polygon296"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="20.548,9.876 20.788,9.756 20.548,9.636 20.548,9.876 "
- id="polygon298"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="19.66,10.524 19.78,10.764 19.9,10.524 19.66,10.524 "
- id="polygon300"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.66,10.524 19.78,10.764 19.9,10.524 19.66,10.524 "
- id="polygon302"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="15.5"
- y="10.1"
- id="text304"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Router 2</text>
- <line
- x1="2.575"
- y1="10.95"
- x2="2.5999999"
- y2="12.4"
- stroke="#000000"
- stroke-width="0.100"
- id="line306"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="8"
- y1="12.4"
- x2="-1.7"
- y2="12.4"
- stroke="#000000"
- stroke-width="0.100"
- id="line308"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="3.4000001"
- y="12"
- id="text310"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Subnet 2</text>
- <rect
- width="1.493"
- height="3.483"
- x="7.099"
- y="13.5"
- id="rect312"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.493"
- height="3.483"
- x="7.099"
- y="13.5"
- id="rect314"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.194"
- height="0.398"
- x="7.2480001"
- y="13.709"
- id="rect316"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.194"
- height="0.398"
- x="7.2480001"
- y="14.107"
- id="rect318"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.194"
- height="0.398"
- x="7.2480001"
- y="14.505"
- id="rect320"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.194"
- height="0.398"
- x="7.2480001"
- y="14.903"
- id="rect322"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.74599999"
- height="0.23899999"
- x="7.2480001"
- y="15.381"
- id="rect324"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="8.3669996"
- cy="15.421"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse326"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="8.3669996"
- cy="15.421"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse328"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="8.3669996"
- cy="15.58"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse330"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="8.3669996"
- cy="15.58"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse332"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17900001"
- height="0.15899999"
- x="8.0690002"
- y="15.461"
- id="rect334"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.17900001"
- height="0.15899999"
- x="8.0690002"
- y="15.461"
- id="rect336"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 7.347,15.938 L 7.347,16.809"
- id="path338"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 7.596,15.938 L 7.596,16.809"
- id="path340"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 7.845,15.938 L 7.845,16.809"
- id="path342"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 8.094,15.938 L 8.094,16.809"
- id="path344"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 8.343,15.938 L 8.343,16.809"
- id="path346"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 8.591,15.938 L 8.591,16.809"
- id="path348"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="6.8,17.282 7.099,16.685 7.099,16.983 8.591,16.983 8.591,16.685 8.989,17.282 6.8,17.282 "
- id="polygon350"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="6.8,17.282 7.099,16.685 7.099,16.983 8.591,16.983 8.591,16.685 8.989,17.282 6.8,17.282 "
- id="polygon352"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="7.895"
- y1="13.5"
- x2="7.9000001"
- y2="12.3"
- stroke="#000000"
- stroke-width="0.100"
- id="line354"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.535"
- height="3.582"
- x="3.707"
- y="13.489"
- id="rect356"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.535"
- height="3.582"
- x="3.707"
- y="13.489"
- id="rect358"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.228"
- height="0.40900001"
- x="3.8599999"
- y="13.703"
- id="rect360"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="3.8599999"
- y="14.113"
- id="rect362"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="3.8599999"
- y="14.522"
- id="rect364"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="3.8599999"
- y="14.931"
- id="rect366"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76700002"
- height="0.24600001"
- x="3.8599999"
- y="15.423"
- id="rect368"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="5.0120001"
- cy="15.464"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse370"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="5.0120001"
- cy="15.464"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse372"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="5.0120001"
- cy="15.627"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse374"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="5.0120001"
- cy="15.627"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse376"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.184"
- height="0.164"
- x="4.7049999"
- y="15.505"
- id="rect378"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.184"
- height="0.164"
- x="4.7049999"
- y="15.505"
- id="rect380"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 3.963,15.996 L 3.963,16.891"
- id="path382"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 4.219,15.996 L 4.219,16.891"
- id="path384"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 4.474,15.996 L 4.474,16.891"
- id="path386"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 4.73,15.996 L 4.73,16.891"
- id="path388"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 4.986,15.996 L 4.986,16.891"
- id="path390"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 5.242,15.996 L 5.242,16.891"
- id="path392"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="3.4,17.377 3.707,16.763 3.707,17.07 5.242,17.07 5.242,16.763 5.651,17.377 3.4,17.377 "
- id="polygon394"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="3.4,17.377 3.707,16.763 3.707,17.07 5.242,17.07 5.242,16.763 5.651,17.377 3.4,17.377 "
- id="polygon396"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.526"
- y1="13.489"
- x2="4.5999999"
- y2="12.4"
- stroke="#000000"
- stroke-width="0.100"
- id="line398"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="7"
- y="18.4"
- id="text400"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_D</text>
- <text
- x="7"
- y="19.200001"
- id="text402"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(WINS)</text>
- <text
- x="3.9000001"
- y="18.4"
- id="text404"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_C</text>
- <rect
- width="1.535"
- height="3.582"
- x="0.60699999"
- y="13.5"
- id="rect406"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.535"
- height="3.582"
- x="0.60699999"
- y="13.5"
- id="rect408"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.228"
- height="0.40900001"
- x="0.75999999"
- y="13.715"
- id="rect410"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="0.75999999"
- y="14.124"
- id="rect412"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="0.75999999"
- y="14.534"
- id="rect414"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="0.75999999"
- y="14.943"
- id="rect416"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76700002"
- height="0.24600001"
- x="0.75999999"
- y="15.434"
- id="rect418"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="1.9119999"
- cy="15.475"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse420"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="1.9119999"
- cy="15.475"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse422"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="1.9119999"
- cy="15.639"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse424"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="1.9119999"
- cy="15.639"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse426"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.184"
- height="0.164"
- x="1.605"
- y="15.516"
- id="rect428"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.184"
- height="0.164"
- x="1.605"
- y="15.516"
- id="rect430"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 0.863,16.007 L 0.863,16.903"
- id="path432"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.119,16.007 L 1.119,16.903"
- id="path434"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.374,16.007 L 1.374,16.903"
- id="path436"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.63,16.007 L 1.63,16.903"
- id="path438"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 1.886,16.007 L 1.886,16.903"
- id="path440"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 2.142,16.007 L 2.142,16.903"
- id="path442"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="0.3,17.389 0.607,16.775 0.607,17.082 2.142,17.082 2.142,16.775 2.551,17.389 0.3,17.389 "
- id="polygon444"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="0.3,17.389 0.607,16.775 0.607,17.082 2.142,17.082 2.142,16.775 2.551,17.389 0.3,17.389 "
- id="polygon446"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.426"
- y1="13.5"
- x2="1.5"
- y2="12.411"
- stroke="#000000"
- stroke-width="0.100"
- id="line448"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="0.80000001"
- y="18.410999"
- id="text450"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_B</text>
- <rect
- width="1.535"
- height="3.582"
- x="-2.493"
- y="13.5"
- id="rect452"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.535"
- height="3.582"
- x="-2.493"
- y="13.5"
- id="rect454"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.228"
- height="0.40900001"
- x="-2.3399999"
- y="13.715"
- id="rect456"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="-2.3399999"
- y="14.124"
- id="rect458"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="-2.3399999"
- y="14.534"
- id="rect460"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="-2.3399999"
- y="14.943"
- id="rect462"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76700002"
- height="0.24600001"
- x="-2.3399999"
- y="15.434"
- id="rect464"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="-1.188"
- cy="15.475"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse466"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="-1.188"
- cy="15.475"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse468"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="-1.188"
- cy="15.639"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse470"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="-1.188"
- cy="15.639"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse472"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.184"
- height="0.164"
- x="-1.495"
- y="15.516"
- id="rect474"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.184"
- height="0.164"
- x="-1.495"
- y="15.516"
- id="rect476"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M -2.237,16.007 L -2.237,16.903"
- id="path478"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M -1.981,16.007 L -1.981,16.903"
- id="path480"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M -1.726,16.007 L -1.726,16.903"
- id="path482"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M -1.47,16.007 L -1.47,16.903"
- id="path484"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M -1.214,16.007 L -1.214,16.903"
- id="path486"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M -0.958,16.007 L -0.958,16.903"
- id="path488"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="-2.8,17.389 -2.493,16.775 -2.493,17.082 -0.958,17.082 -0.958,16.775 -0.549,17.389 -2.8,17.389 "
- id="polygon490"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="-2.8,17.389 -2.493,16.775 -2.493,17.082 -0.958,17.082 -0.958,16.775 -0.549,17.389 -2.8,17.389 "
- id="polygon492"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="-1.674"
- y1="13.5"
- x2="-1.6"
- y2="12.411"
- stroke="#000000"
- stroke-width="0.100"
- id="line494"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="-2.4000001"
- y="18.4"
- id="text496"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N2_A</text>
- <line
- x1="19.9"
- y1="11.1"
- x2="19.9"
- y2="12.6"
- stroke="#000000"
- stroke-width="0.100"
- id="line498"
- style="stroke:#000000;stroke-width:0.1" />
- <line
- x1="25.299999"
- y1="12.6"
- x2="15.6"
- y2="12.6"
- stroke="#000000"
- stroke-width="0.100"
- id="line500"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="20.700001"
- y="12.2"
- id="text502"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Subnet 3</text>
- <rect
- width="1.493"
- height="3.483"
- x="24.399"
- y="13.7"
- id="rect504"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.493"
- height="3.483"
- x="24.399"
- y="13.7"
- id="rect506"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.194"
- height="0.398"
- x="24.548"
- y="13.909"
- id="rect508"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.194"
- height="0.398"
- x="24.548"
- y="14.307"
- id="rect510"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.194"
- height="0.398"
- x="24.548"
- y="14.705"
- id="rect512"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.194"
- height="0.398"
- x="24.548"
- y="15.103"
- id="rect514"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.74599999"
- height="0.23899999"
- x="24.548"
- y="15.581"
- id="rect516"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="25.667"
- cy="15.621"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse518"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="25.667"
- cy="15.621"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse520"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="25.667"
- cy="15.78"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse522"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="25.667"
- cy="15.78"
- rx="0.052000001"
- ry="0.052000001"
- id="ellipse524"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.17900001"
- height="0.15899999"
- x="25.368999"
- y="15.661"
- id="rect526"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.17900001"
- height="0.15899999"
- x="25.368999"
- y="15.661"
- id="rect528"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 24.647,16.138 L 24.647,17.009"
- id="path530"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 24.896,16.138 L 24.896,17.009"
- id="path532"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 25.145,16.138 L 25.145,17.009"
- id="path534"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 25.394,16.138 L 25.394,17.009"
- id="path536"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 25.643,16.138 L 25.643,17.009"
- id="path538"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 25.891,16.138 L 25.891,17.009"
- id="path540"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="24.1,17.482 24.399,16.885 24.399,17.183 25.891,17.183 25.891,16.885 26.289,17.482 24.1,17.482 "
- id="polygon542"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="24.1,17.482 24.399,16.885 24.399,17.183 25.891,17.183 25.891,16.885 26.289,17.482 24.1,17.482 "
- id="polygon544"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="25.195"
- y1="13.7"
- x2="25.200001"
- y2="12.5"
- stroke="#000000"
- stroke-width="0.100"
- id="line546"
- style="stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.535"
- height="3.582"
- x="21.007"
- y="13.689"
- id="rect548"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.535"
- height="3.582"
- x="21.007"
- y="13.689"
- id="rect550"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.228"
- height="0.40900001"
- x="21.16"
- y="13.903"
- id="rect552"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="21.16"
- y="14.313"
- id="rect554"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="21.16"
- y="14.722"
- id="rect556"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="21.16"
- y="15.131"
- id="rect558"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76700002"
- height="0.24600001"
- x="21.16"
- y="15.623"
- id="rect560"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="22.312"
- cy="15.664"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse562"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="22.312"
- cy="15.664"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse564"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="22.312"
- cy="15.827"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse566"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="22.312"
- cy="15.827"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse568"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.184"
- height="0.164"
- x="22.004999"
- y="15.705"
- id="rect570"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.184"
- height="0.164"
- x="22.004999"
- y="15.705"
- id="rect572"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 21.263,16.196 L 21.263,17.091"
- id="path574"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 21.519,16.196 L 21.519,17.091"
- id="path576"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 21.774,16.196 L 21.774,17.091"
- id="path578"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 22.03,16.196 L 22.03,17.091"
- id="path580"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 22.286,16.196 L 22.286,17.091"
- id="path582"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 22.542,16.196 L 22.542,17.091"
- id="path584"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="20.7,17.577 21.007,16.963 21.007,17.27 22.542,17.27 22.542,16.963 22.951,17.577 20.7,17.577 "
- id="polygon586"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="20.7,17.577 21.007,16.963 21.007,17.27 22.542,17.27 22.542,16.963 22.951,17.577 20.7,17.577 "
- id="polygon588"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.826"
- y1="13.689"
- x2="21.9"
- y2="12.6"
- stroke="#000000"
- stroke-width="0.100"
- id="line590"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="24.299999"
- y="18.6"
- id="text592"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_D</text>
- <text
- x="21.200001"
- y="18.6"
- id="text594"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_C</text>
- <rect
- width="1.535"
- height="3.582"
- x="17.907"
- y="13.7"
- id="rect596"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.535"
- height="3.582"
- x="17.907"
- y="13.7"
- id="rect598"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.228"
- height="0.40900001"
- x="18.059999"
- y="13.915"
- id="rect600"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="18.059999"
- y="14.324"
- id="rect602"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="18.059999"
- y="14.734"
- id="rect604"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="18.059999"
- y="15.143"
- id="rect606"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76700002"
- height="0.24600001"
- x="18.059999"
- y="15.634"
- id="rect608"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="19.212"
- cy="15.675"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse610"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="19.212"
- cy="15.675"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse612"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="19.212"
- cy="15.839"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse614"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="19.212"
- cy="15.839"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse616"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.184"
- height="0.164"
- x="18.905001"
- y="15.716"
- id="rect618"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.184"
- height="0.164"
- x="18.905001"
- y="15.716"
- id="rect620"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 18.163,16.207 L 18.163,17.103"
- id="path622"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 18.419,16.207 L 18.419,17.103"
- id="path624"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 18.674,16.207 L 18.674,17.103"
- id="path626"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 18.93,16.207 L 18.93,17.103"
- id="path628"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 19.186,16.207 L 19.186,17.103"
- id="path630"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 19.442,16.207 L 19.442,17.103"
- id="path632"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="17.6,17.589 17.907,16.975 17.907,17.282 19.442,17.282 19.442,16.975 19.851,17.589 17.6,17.589 "
- id="polygon634"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="17.6,17.589 17.907,16.975 17.907,17.282 19.442,17.282 19.442,16.975 19.851,17.589 17.6,17.589 "
- id="polygon636"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="18.726"
- y1="13.7"
- x2="18.799999"
- y2="12.611"
- stroke="#000000"
- stroke-width="0.100"
- id="line638"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="18.1"
- y="18.611"
- id="text640"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_B</text>
- <rect
- width="1.535"
- height="3.582"
- x="14.807"
- y="13.7"
- id="rect642"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.535"
- height="3.582"
- x="14.807"
- y="13.7"
- id="rect644"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.228"
- height="0.40900001"
- x="14.96"
- y="13.915"
- id="rect646"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="14.96"
- y="14.324"
- id="rect648"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="14.96"
- y="14.734"
- id="rect650"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.228"
- height="0.40900001"
- x="14.96"
- y="15.143"
- id="rect652"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.76700002"
- height="0.24600001"
- x="14.96"
- y="15.634"
- id="rect654"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="16.112"
- cy="15.675"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse656"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="16.112"
- cy="15.675"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse658"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="16.112"
- cy="15.839"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse660"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="16.112"
- cy="15.839"
- rx="0.054000001"
- ry="0.054000001"
- id="ellipse662"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.184"
- height="0.164"
- x="15.805"
- y="15.716"
- id="rect664"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.184"
- height="0.164"
- x="15.805"
- y="15.716"
- id="rect666"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.063,16.207 L 15.063,17.103"
- id="path668"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.319,16.207 L 15.319,17.103"
- id="path670"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.574,16.207 L 15.574,17.103"
- id="path672"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.83,16.207 L 15.83,17.103"
- id="path674"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 16.086,16.207 L 16.086,17.103"
- id="path676"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 16.342,16.207 L 16.342,17.103"
- id="path678"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="14.5,17.589 14.807,16.975 14.807,17.282 16.342,17.282 16.342,16.975 16.751,17.589 14.5,17.589 "
- id="polygon680"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="14.5,17.589 14.807,16.975 14.807,17.282 16.342,17.282 16.342,16.975 16.751,17.589 14.5,17.589 "
- id="polygon682"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.626"
- y1="13.7"
- x2="15.7"
- y2="12.611"
- stroke="#000000"
- stroke-width="0.100"
- id="line684"
- style="stroke:#000000;stroke-width:0.1" />
- <text
- x="14.9"
- y="18.6"
- id="text686"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">N3_A</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="27.950001cm"
- height="23.34cm"
- viewBox="0.8 0.857 28.75 24.198"
- id="svg2">
- <defs
- id="defs117" />
- <text
- x="0.80000001"
- y="1.4"
- id="text4"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">CUPS in and of itself has this (general) filter chain (italic letters</text>
- <text
- x="0.80000001"
- y="2.2"
- id="text6"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">are file-formats or MIME types, other are filters (this is</text>
- <text
- x="0.80000001"
- y="3"
- id="text8"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):</text>
- <text
- x="2.0999999"
- y="4.9000001"
- id="text10"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something-fileformat</text>
- <polygon
- points="4.625,5.6 4.625,6.45 4.2,6.45 5.05,7.3 5.9,6.45 5.475,6.45 5.475,5.6 4.625,5.6 "
- id="polygon12"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.625,5.6 4.625,6.45 4.2,6.45 5.05,7.3 5.9,6.45 5.475,6.45 5.475,5.6 4.625,5.6 "
- id="polygon14"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.625,5.6 4.625,6.45 4.2,6.45 5.05,7.3 5.9,6.45 5.475,6.45 5.475,5.6 4.625,5.6 "
- id="polygon16"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="2.0999999"
- y="11.9"
- id="text18"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/postscript</text>
- <polygon
- points="4.725,12.6 4.725,13.45 4.3,13.45 5.15,14.3 6,13.45 5.575,13.45 5.575,12.6 4.725,12.6 "
- id="polygon20"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.725,12.6 4.725,13.45 4.3,13.45 5.15,14.3 6,13.45 5.575,13.45 5.575,12.6 4.725,12.6 "
- id="polygon22"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.725,12.6 4.725,13.45 4.3,13.45 5.15,14.3 6,13.45 5.575,13.45 5.575,12.6 4.725,12.6 "
- id="polygon24"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="4.625,9 4.625,9.85 4.2,9.85 5.05,10.7 5.9,9.85 5.475,9.85 5.475,9 4.625,9 "
- id="polygon26"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.625,9 4.625,9.85 4.2,9.85 5.05,10.7 5.9,9.85 5.475,9.85 5.475,9 4.625,9 "
- id="polygon28"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.625,9 4.625,9.85 4.2,9.85 5.05,10.7 5.9,9.85 5.475,9.85 5.475,9 4.625,9 "
- id="polygon30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="2.8"
- y="8.3000002"
- id="text32"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">somethingtops</text>
- <text
- x="4.0999999"
- y="15.3"
- id="text34"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
- <polygon
- points="4.725,15.8 4.725,16.65 4.3,16.65 5.15,17.5 6,16.65 5.575,16.65 5.575,15.8 4.725,15.8 "
- id="polygon36"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.725,15.8 4.725,16.65 4.3,16.65 5.15,17.5 6,16.65 5.575,16.65 5.575,15.8 4.725,15.8 "
- id="polygon38"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.725,15.8 4.725,16.65 4.3,16.65 5.15,17.5 6,16.65 5.575,16.65 5.575,15.8 4.725,15.8 "
- id="polygon40"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="1.2"
- y="18.4"
- id="text42"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-postscript</text>
- <text
- x="14.8"
- y="18.4"
- id="text44"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstoraster</text>
- <text
- x="13.4"
- y="14.8"
- id="text46"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-raster</text>
- <text
- x="14.2"
- y="11.2"
- id="text48"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">rastertosomething</text>
- <text
- x="13.3"
- y="7.6999998"
- id="text50"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something-device-specific</text>
- <text
- x="25.6"
- y="7.6999998"
- id="text52"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">backend</text>
- <polygon
- points="11.2,17.625 12.5,17.625 12.5,17.2 13.8,18.05 12.5,18.9 12.5,18.475 11.2,18.475 11.2,17.625 "
- id="polygon54"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="11.2,17.625 12.5,17.625 12.5,17.2 13.8,18.05 12.5,18.9 12.5,18.475 11.2,18.475 11.2,17.625 "
- id="polygon56"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.2,17.625 12.5,17.625 12.5,17.2 13.8,18.05 12.5,18.9 12.5,18.475 11.2,18.475 11.2,17.625 "
- id="polygon58"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="16.35,17.5 16.35,16.35 15.9,16.35 16.8,15.2 17.7,16.35 17.25,16.35 17.25,17.5 16.35,17.5 "
- id="polygon60"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="16.35,17.5 16.35,16.35 15.9,16.35 16.8,15.2 17.7,16.35 17.25,16.35 17.25,17.5 16.35,17.5 "
- id="polygon62"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="16.35,17.5 16.35,16.35 15.9,16.35 16.8,15.2 17.7,16.35 17.25,16.35 17.25,17.5 16.35,17.5 "
- id="polygon64"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="16.35,14 16.35,12.85 15.9,12.85 16.8,11.7 17.7,12.85 17.25,12.85 17.25,14 16.35,14 "
- id="polygon66"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="16.35,14 16.35,12.85 15.9,12.85 16.8,11.7 17.7,12.85 17.25,12.85 17.25,14 16.35,14 "
- id="polygon68"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="16.35,14 16.35,12.85 15.9,12.85 16.8,11.7 17.7,12.85 17.25,12.85 17.25,14 16.35,14 "
- id="polygon70"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="16.35,10.3 16.35,9.15 15.9,9.15 16.8,8 17.7,9.15 17.25,9.15 17.25,10.3 16.35,10.3 "
- id="polygon72"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="16.35,10.3 16.35,9.15 15.9,9.15 16.8,8 17.7,9.15 17.25,9.15 17.25,10.3 16.35,10.3 "
- id="polygon74"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="16.35,10.3 16.35,9.15 15.9,9.15 16.8,8 17.7,9.15 17.25,9.15 17.25,10.3 16.35,10.3 "
- id="polygon76"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="21.9,7.025 23.2,7.025 23.2,6.6 24.5,7.45 23.2,8.3 23.2,7.875 21.9,7.875 21.9,7.025 "
- id="polygon78"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="21.9,7.025 23.2,7.025 23.2,6.6 24.5,7.45 23.2,8.3 23.2,7.875 21.9,7.875 21.9,7.025 "
- id="polygon80"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="21.9,7.025 23.2,7.025 23.2,6.6 24.5,7.45 23.2,8.3 23.2,7.875 21.9,7.875 21.9,7.025 "
- id="polygon82"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="8.1000004"
- height="2.7"
- x="20.200001"
- y="10"
- id="rect84"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="8.1000004"
- height="2.7"
- x="20.200001"
- y="10"
- id="rect86"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="20.5"
- y="10.7"
- id="text88"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">e.g. Gimp-Print filters</text>
- <text
- x="20.5"
- y="11.5"
- id="text90"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">may be plugged in here</text>
- <text
- x="20.5"
- y="12.3"
- id="text92"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= "raster driver")</text>
- <text
- x="1.5"
- y="20.700001"
- id="text94"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">ESP PrintPro has some enhanced "rastertosomething" filters as compared to</text>
- <text
- x="1.5"
- y="21.5"
- id="text96"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">CUPS, and also a somewhat improved "pstoraster" filter.</text>
- <text
- x="1.6"
- y="23"
- id="text98"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to</text>
- <text
- x="1.6"
- y="23.799999"
- id="text100"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">CUPS and ESP PrintPro plug-in where rastertosomething is noted.</text>
- <rect
- width="10.1"
- height="4.4000001"
- x="18.6"
- y="15.5"
- id="rect102"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="10.1"
- height="4.4000001"
- x="18.6"
- y="15.5"
- id="rect104"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="19"
- y="16.4"
- id="text106"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">as shipped with CUPS,</text>
- <text
- x="19"
- y="17.200001"
- id="text108"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">independent from any</text>
- <text
- x="19"
- y="18"
- id="text110"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">GhostScript installation on the</text>
- <text
- x="19"
- y="18.799999"
- id="text112"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">system</text>
- <text
- x="19"
- y="19.6"
- id="text114"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= "postscript interpreter")</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="24.681999cm"
- height="42.34cm"
- viewBox="0.268 0.758 24.95 43.098"
- id="svg2">
- <defs
- id="defs139" />
- <text
- x="1"
- y="1.3"
- id="text4"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something-fileformat</text>
- <polygon
- points="3.163,1.9 3.163,2.825 2.7,2.825 3.625,3.75 4.55,2.825 4.088,2.825 4.088,1.9 3.163,1.9 "
- id="polygon6"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.163,1.9 3.163,2.825 2.7,2.825 3.625,3.75 4.55,2.825 4.088,2.825 4.088,1.9 3.163,1.9 "
- id="polygon8"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.163,1.9 3.163,2.825 2.7,2.825 3.625,3.75 4.55,2.825 4.088,2.825 4.088,1.9 3.163,1.9 "
- id="polygon10"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="1.7"
- y="4.8000002"
- id="text12"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">somethingtops</text>
- <text
- x="1.4"
- y="8.3000002"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/postscript</text>
- <polygon
- points="3.262,5.4 3.262,6.325 2.8,6.325 3.725,7.25 4.65,6.325 4.188,6.325 4.188,5.4 3.262,5.4 "
- id="polygon16"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.262,5.4 3.262,6.325 2.8,6.325 3.725,7.25 4.65,6.325 4.188,6.325 4.188,5.4 3.262,5.4 "
- id="polygon18"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.262,5.4 3.262,6.325 2.8,6.325 3.725,7.25 4.65,6.325 4.188,6.325 4.188,5.4 3.262,5.4 "
- id="polygon20"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="2.8"
- y="11.5"
- id="text22"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
- <polygon
- points="3.262,8.7 3.262,9.625 2.8,9.625 3.725,10.55 4.65,9.625 4.188,9.625 4.188,8.7 3.262,8.7 "
- id="polygon24"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.262,8.7 3.262,9.625 2.8,9.625 3.725,10.55 4.65,9.625 4.188,9.625 4.188,8.7 3.262,8.7 "
- id="polygon26"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.262,8.7 3.262,9.625 2.8,9.625 3.725,10.55 4.65,9.625 4.188,9.625 4.188,8.7 3.262,8.7 "
- id="polygon28"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="3.362,12.1 3.362,13.025 2.9,13.025 3.825,13.95 4.75,13.025 4.287,13.025 4.287,12.1 3.362,12.1 "
- id="polygon30"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.362,12.1 3.362,13.025 2.9,13.025 3.825,13.95 4.75,13.025 4.287,13.025 4.287,12.1 3.362,12.1 "
- id="polygon32"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.362,12.1 3.362,13.025 2.9,13.025 3.825,13.95 4.75,13.025 4.287,13.025 4.287,12.1 3.362,12.1 "
- id="polygon34"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="0.30000001"
- y="15"
- id="text36"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-postscript</text>
- <polygon
- points="10.5,14.275 12,14.275 12,13.8 13.5,14.75 12,15.7 12,15.225 10.5,15.225 10.5,14.275 "
- id="polygon38"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.5,14.275 12,14.275 12,13.8 13.5,14.75 12,15.7 12,15.225 10.5,15.225 10.5,14.275 "
- id="polygon40"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="10.5,14.275 12,14.275 12,13.8 13.5,14.75 12,15.7 12,15.225 10.5,15.225 10.5,14.275 "
- id="polygon42"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="14.2"
- y="14.9"
- id="text44"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">cupsomatic</text>
- <rect
- width="10.5"
- height="3.8"
- x="14.4"
- y="10"
- id="rect46"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="10.5"
- height="3.8"
- x="14.4"
- y="10"
- id="rect48"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="14.9"
- y="11"
- id="text50"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(constructs complicated</text>
- <text
- x="14.9"
- y="11.8"
- id="text52"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Ghostscript commandline</text>
- <text
- x="14.9"
- y="12.6"
- id="text54"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">to let the file be processed by a</text>
- <text
- x="14.9"
- y="13.4"
- id="text56"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">"-sDEVICE-s.th." call...)</text>
- <polygon
- points="3.462,15.7 3.462,16.625 3,16.625 3.925,17.55 4.85,16.625 4.388,16.625 4.388,15.7 3.462,15.7 "
- id="polygon58"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.462,15.7 3.462,16.625 3,16.625 3.925,17.55 4.85,16.625 4.388,16.625 4.388,15.7 3.462,15.7 "
- id="polygon60"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.462,15.7 3.462,16.625 3,16.625 3.925,17.55 4.85,16.625 4.388,16.625 4.388,15.7 3.462,15.7 "
- id="polygon62"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="2.6159999"
- y="18.299999"
- id="text64"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstoraster</text>
- <text
- x="0.26800001"
- y="19.1"
- id="text66"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= "postscript interpreter")</text>
- <polygon
- points="3.562,19.4 3.562,20.325 3.1,20.325 4.025,21.25 4.95,20.325 4.487,20.325 4.487,19.4 3.562,19.4 "
- id="polygon68"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.562,19.4 3.562,20.325 3.1,20.325 4.025,21.25 4.95,20.325 4.487,20.325 4.487,19.4 3.562,19.4 "
- id="polygon70"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.562,19.4 3.562,20.325 3.1,20.325 4.025,21.25 4.95,20.325 4.487,20.325 4.487,19.4 3.562,19.4 "
- id="polygon72"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="0.80000001"
- y="22.299999"
- id="text74"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-raster</text>
- <polygon
- points="3.663,23 3.663,23.925 3.2,23.925 4.125,24.85 5.05,23.925 4.588,23.925 4.588,23 3.663,23 "
- id="polygon76"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.663,23 3.663,23.925 3.2,23.925 4.125,24.85 5.05,23.925 4.588,23.925 4.588,23 3.663,23 "
- id="polygon78"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.663,23 3.663,23.925 3.2,23.925 4.125,24.85 5.05,23.925 4.588,23.925 4.588,23 3.663,23 "
- id="polygon80"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="1.7"
- y="25.5"
- id="text82"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">rastertosomething</text>
- <text
- x="1.7"
- y="26.299999"
- id="text84"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">(= "raster driver")</text>
- <polygon
- points="16.915,16.1 16.915,17.129 16.4,17.129 17.429,18.159 18.459,17.129 17.944,17.129 17.944,16.1 16.915,16.1 "
- id="polygon86"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="16.915,16.1 16.915,17.129 16.4,17.129 17.429,18.159 18.459,17.129 17.944,17.129 17.944,16.1 16.915,16.1 "
- id="polygon88"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="16.915,16.1 16.915,17.129 16.4,17.129 17.429,18.159 18.459,17.129 17.944,17.129 17.944,16.1 16.915,16.1 "
- id="polygon90"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="3.762,26.8 3.762,27.725 3.3,27.725 4.225,28.65 5.15,27.725 4.688,27.725 4.688,26.8 3.762,26.8 "
- id="polygon92"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.762,26.8 3.762,27.725 3.3,27.725 4.225,28.65 5.15,27.725 4.688,27.725 4.688,26.8 3.762,26.8 "
- id="polygon94"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.762,26.8 3.762,27.725 3.3,27.725 4.225,28.65 5.15,27.725 4.688,27.725 4.688,26.8 3.762,26.8 "
- id="polygon96"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="1"
- y="29.6"
- id="text98"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">something device specific</text>
- <polygon
- points="3.762,30.3 3.762,31.225 3.3,31.225 4.225,32.15 5.15,31.225 4.688,31.225 4.688,30.3 3.762,30.3 "
- id="polygon100"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="3.762,30.3 3.762,31.225 3.3,31.225 4.225,32.15 5.15,31.225 4.688,31.225 4.688,30.3 3.762,30.3 "
- id="polygon102"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="3.762,30.3 3.762,31.225 3.3,31.225 4.225,32.15 5.15,31.225 4.688,31.225 4.688,30.3 3.762,30.3 "
- id="polygon104"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="3.2"
- y="33.299999"
- id="text106"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">backend</text>
- <polygon
- points="11.65,32.413 10.625,32.413 10.625,31.9 9.6,32.925 10.625,33.95 10.625,33.438 11.65,33.438 11.65,32.413 "
- id="polygon108"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="11.65,32.413 10.625,32.413 10.625,31.9 9.6,32.925 10.625,33.95 10.625,33.438 11.65,33.438 11.65,32.413 "
- id="polygon110"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.65,32.413 10.625,32.413 10.625,31.9 9.6,32.925 10.625,33.95 10.625,33.438 11.65,33.438 11.65,32.413 "
- id="polygon112"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="7.5"
- height="14.3"
- x="14.6"
- y="19.4"
- id="rect114"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="7.5"
- height="14.3"
- x="14.6"
- y="19.4"
- id="rect116"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="15.28"
- y="26.6"
- id="text118"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Ghostscript at work....</text>
- <text
- x="1.2"
- y="35.5"
- id="text120"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Note, that cupsomatic "kidnaps" the printfile after the</text>
- <text
- x="1.2"
- y="36.299999"
- id="text122"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">application/vnd.cups-postscript stage and deviates it gh</text>
- <text
- x="1.2"
- y="37.099998"
- id="text124"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">the CUPS-external, systemwide Ghostscript installation, bypassing the</text>
- <text
- x="1.2"
- y="37.900002"
- id="text126"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">"pstoraster" filter (therefore also bypassing the CUPS-raster-drivers</text>
- <text
- x="1.2"
- y="38.700001"
- id="text128"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">"rastertosomething", and hands the rasterized file directly to the CUPS</text>
- <text
- x="1.2"
- y="39.5"
- id="text130"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">backend...</text>
- <text
- x="1.2"
- y="41.099998"
- id="text132"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">cupsomatic is not made by the CUPS developers. It is an independent</text>
- <text
- x="1.2"
- y="41.900002"
- id="text134"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">contribution to printing development, made by people from</text>
- <text
- x="1.2"
- y="42.700001"
- id="text136"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Linuxprinting.org. (see also http://www.cups.org/cups-help.html)</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="30cm"
- height="19.163cm"
- viewBox="0.15 0.887 30.15 20.05"
- id="svg2">
- <defs
- id="defs603" />
- <ellipse
- cx="15.15"
- cy="11.2"
- rx="14.95"
- ry="8.8000002"
- id="ellipse4"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.1830001"
- height="6.5500002"
- x="8.1999998"
- y="3.9000001"
- id="rect6"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.1830001"
- height="6.5500002"
- x="8.1999998"
- y="3.9000001"
- id="rect8"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.1830001"
- height="6.5500002"
- x="8.1999998"
- y="3.9000001"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.747"
- height="2.6199999"
- x="8.4180002"
- y="4.118"
- id="rect12"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.747"
- height="2.6199999"
- x="8.4180002"
- y="4.118"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.747"
- height="2.6199999"
- x="8.4180002"
- y="4.118"
- id="rect16"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.4180002"
- y1="4.5549998"
- x2="10.165"
- y2="4.5549998"
- stroke="#000000"
- stroke-width="0.010"
- id="line18"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.165"
- y1="4.9920001"
- x2="8.4180002"
- y2="4.9920001"
- stroke="#000000"
- stroke-width="0.010"
- id="line20"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.4180002"
- y1="5.428"
- x2="10.165"
- y2="5.428"
- stroke="#000000"
- stroke-width="0.010"
- id="line22"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.4180002"
- y1="5.8649998"
- x2="10.165"
- y2="5.8649998"
- stroke="#000000"
- stroke-width="0.010"
- id="line24"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.165"
- y1="6.302"
- x2="8.4180002"
- y2="6.302"
- stroke="#000000"
- stroke-width="0.010"
- id="line26"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.201"
- height="0.65499997"
- x="8.4180002"
- y="6.9569998"
- id="rect28"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.201"
- height="0.65499997"
- x="8.4180002"
- y="6.9569998"
- id="rect30"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.201"
- height="0.65499997"
- x="8.4180002"
- y="6.9569998"
- id="rect32"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.1999998"
- y1="8.0480003"
- x2="10.383"
- y2="8.0480003"
- stroke="#000000"
- stroke-width="0.010"
- id="line34"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.109"
- height="0.109"
- x="9.1820002"
- y="8.2670002"
- id="rect36"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.109"
- height="0.109"
- x="9.1820002"
- y="8.2670002"
- id="rect38"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.109"
- height="0.109"
- x="9.1820002"
- y="8.2670002"
- id="rect40"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.109"
- height="0.109"
- x="9.6190004"
- y="8.2670002"
- id="rect42"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.109"
- height="0.109"
- x="9.6190004"
- y="8.2670002"
- id="rect44"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.109"
- height="0.109"
- x="9.6190004"
- y="8.2670002"
- id="rect46"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.109"
- height="0.109"
- x="10.056"
- y="8.2670002"
- id="rect48"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.109"
- height="0.109"
- x="10.056"
- y="8.2670002"
- id="rect50"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.109"
- height="0.109"
- x="10.056"
- y="8.2670002"
- id="rect52"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.21799999"
- height="0.21799999"
- x="9.9469995"
- y="7.612"
- id="rect54"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.21799999"
- height="0.21799999"
- x="9.9469995"
- y="7.612"
- id="rect56"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.21799999"
- height="0.21799999"
- x="9.9469995"
- y="7.612"
- id="rect58"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.4180002"
- y1="7.2839999"
- x2="9.6190004"
- y2="7.2839999"
- stroke="#000000"
- stroke-width="0.010"
- id="line60"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.32800001"
- height="0.32800001"
- x="8.4180002"
- y="8.1569996"
- id="rect62"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.32800001"
- height="0.32800001"
- x="8.4180002"
- y="8.1569996"
- id="rect64"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.32800001"
- height="0.32800001"
- x="8.4180002"
- y="8.1569996"
- id="rect66"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.528"
- height="0.109"
- x="8.5270004"
- y="6.4109998"
- id="rect68"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.528"
- height="0.109"
- x="8.5270004"
- y="6.4109998"
- id="rect70"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.528"
- height="0.109"
- x="8.5270004"
- y="6.4109998"
- id="rect72"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.5270004"
- y1="7.066"
- x2="9.5100002"
- y2="7.066"
- stroke="#000000"
- stroke-width="0.010"
- id="line74"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.5100002"
- y1="7.1750002"
- x2="9.401"
- y2="7.1750002"
- stroke="#000000"
- stroke-width="0.010"
- id="line76"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.5270004"
- y1="7.1750002"
- x2="8.6370001"
- y2="7.1750002"
- stroke="#000000"
- stroke-width="0.010"
- id="line78"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.546"
- height="0.109"
- x="8.7460003"
- y="7.066"
- id="rect80"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.546"
- height="0.109"
- x="8.7460003"
- y="7.066"
- id="rect82"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.546"
- height="0.109"
- x="8.7460003"
- y="7.066"
- id="rect84"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.5270004"
- y1="6.6290002"
- x2="8.6370001"
- y2="6.6290002"
- stroke="#000000"
- stroke-width="0.010"
- id="line86"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.7460003"
- y1="6.6290002"
- x2="8.8549995"
- y2="6.6290002"
- stroke="#000000"
- stroke-width="0.010"
- id="line88"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="9.8369999"
- y1="6.6290002"
- x2="10.056"
- y2="6.6290002"
- stroke="#000000"
- stroke-width="0.010"
- id="line90"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.309"
- y1="10.341"
- x2="10.274"
- y2="10.341"
- stroke="#000000"
- stroke-width="0.010"
- id="line92"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.274"
- y1="10.232"
- x2="8.309"
- y2="10.232"
- stroke="#000000"
- stroke-width="0.010"
- id="line94"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.309"
- y1="10.123"
- x2="10.274"
- y2="10.123"
- stroke="#000000"
- stroke-width="0.010"
- id="line96"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.274"
- y1="10.013"
- x2="8.309"
- y2="10.013"
- stroke="#000000"
- stroke-width="0.010"
- id="line98"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.309"
- y1="9.9040003"
- x2="10.274"
- y2="9.9040003"
- stroke="#000000"
- stroke-width="0.010"
- id="line100"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.274"
- y1="9.7950001"
- x2="8.309"
- y2="9.7950001"
- stroke="#000000"
- stroke-width="0.010"
- id="line102"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.309"
- y1="9.6859999"
- x2="10.274"
- y2="9.6859999"
- stroke="#000000"
- stroke-width="0.010"
- id="line104"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.274"
- y1="9.5769997"
- x2="8.309"
- y2="9.5769997"
- stroke="#000000"
- stroke-width="0.010"
- id="line106"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.309"
- y1="9.467"
- x2="10.274"
- y2="9.467"
- stroke="#000000"
- stroke-width="0.010"
- id="line108"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.274"
- y1="9.3579998"
- x2="8.309"
- y2="9.3579998"
- stroke="#000000"
- stroke-width="0.010"
- id="line110"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.309"
- y1="9.2489996"
- x2="10.274"
- y2="9.2489996"
- stroke="#000000"
- stroke-width="0.010"
- id="line112"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.274"
- y1="9.1400003"
- x2="8.309"
- y2="9.1400003"
- stroke="#000000"
- stroke-width="0.010"
- id="line114"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="8.309"
- y1="9.0310001"
- x2="10.274"
- y2="9.0310001"
- stroke="#000000"
- stroke-width="0.010"
- id="line116"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="10.274"
- y1="8.9219999"
- x2="8.309"
- y2="8.9219999"
- stroke="#000000"
- stroke-width="0.010"
- id="line118"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="4.9000001"
- y="5.6999998"
- id="text120"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Primary</text>
- <text
- x="4.9000001"
- y="6.5"
- id="text122"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Domain</text>
- <text
- x="4.9000001"
- y="7.3000002"
- id="text124"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Controller</text>
- <rect
- width="2.6359999"
- height="5.2709999"
- x="1.7"
- y="9.1000004"
- id="rect126"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.6359999"
- height="5.2709999"
- x="1.7"
- y="9.1000004"
- id="rect128"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.6359999"
- height="5.2709999"
- x="1.7"
- y="9.1000004"
- id="rect130"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="2.108"
- height="2.108"
- x="1.964"
- y="9.3640003"
- id="rect132"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.108"
- height="2.108"
- x="1.964"
- y="9.3640003"
- id="rect134"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.108"
- height="2.108"
- x="1.964"
- y="9.3640003"
- id="rect136"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.072"
- y1="9.8909998"
- x2="1.964"
- y2="9.8909998"
- stroke="#000000"
- stroke-width="0.010"
- id="line138"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.964"
- y1="10.418"
- x2="4.072"
- y2="10.418"
- stroke="#000000"
- stroke-width="0.010"
- id="line140"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.072"
- y1="10.813"
- x2="1.964"
- y2="10.813"
- stroke="#000000"
- stroke-width="0.010"
- id="line142"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.45"
- height="0.79100001"
- x="1.964"
- y="11.736"
- id="rect144"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.45"
- height="0.79100001"
- x="1.964"
- y="11.736"
- id="rect146"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.45"
- height="0.79100001"
- x="1.964"
- y="11.736"
- id="rect148"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.7"
- y1="12.658"
- x2="4.336"
- y2="12.658"
- stroke="#000000"
- stroke-width="0.010"
- id="line150"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.132"
- height="0.132"
- x="2.8859999"
- y="12.922"
- id="rect152"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.132"
- height="0.132"
- x="2.8859999"
- y="12.922"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.132"
- height="0.132"
- x="2.8859999"
- y="12.922"
- id="rect156"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.132"
- height="0.132"
- x="3.4130001"
- y="12.922"
- id="rect158"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.132"
- height="0.132"
- x="3.4130001"
- y="12.922"
- id="rect160"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.132"
- height="0.132"
- x="3.4130001"
- y="12.922"
- id="rect162"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.132"
- height="0.132"
- x="3.9400001"
- y="12.922"
- id="rect164"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.132"
- height="0.132"
- x="3.9400001"
- y="12.922"
- id="rect166"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.132"
- height="0.132"
- x="3.9400001"
- y="12.922"
- id="rect168"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.264"
- height="0.132"
- x="3.8080001"
- y="12.131"
- id="rect170"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.264"
- height="0.132"
- x="3.8080001"
- y="12.131"
- id="rect172"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.264"
- height="0.132"
- x="3.8080001"
- y="12.131"
- id="rect174"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.964"
- y1="12.131"
- x2="3.4130001"
- y2="12.131"
- stroke="#000000"
- stroke-width="0.010"
- id="line176"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.39500001"
- height="0.39500001"
- x="1.964"
- y="12.79"
- id="rect178"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.39500001"
- height="0.39500001"
- x="1.964"
- y="12.79"
- id="rect180"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.39500001"
- height="0.39500001"
- x="1.964"
- y="12.79"
- id="rect182"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.845"
- height="0.132"
- x="2.095"
- y="10.945"
- id="rect184"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.845"
- height="0.132"
- x="2.095"
- y="10.945"
- id="rect186"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.845"
- height="0.132"
- x="2.095"
- y="10.945"
- id="rect188"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.095"
- y1="11.867"
- x2="3.2809999"
- y2="11.867"
- stroke="#000000"
- stroke-width="0.010"
- id="line190"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.2809999"
- y1="11.999"
- x2="3.1500001"
- y2="11.999"
- stroke="#000000"
- stroke-width="0.010"
- id="line192"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.095"
- y1="11.999"
- x2="2.227"
- y2="11.999"
- stroke="#000000"
- stroke-width="0.010"
- id="line194"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.65899998"
- height="0.132"
- x="2.359"
- y="11.867"
- id="rect196"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.65899998"
- height="0.132"
- x="2.359"
- y="11.867"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.65899998"
- height="0.132"
- x="2.359"
- y="11.867"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.095"
- y1="11.208"
- x2="2.227"
- y2="11.208"
- stroke="#000000"
- stroke-width="0.010"
- id="line202"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="2.359"
- y1="11.208"
- x2="2.4909999"
- y2="11.208"
- stroke="#000000"
- stroke-width="0.010"
- id="line204"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="3.677"
- y1="11.208"
- x2="3.9400001"
- y2="11.208"
- stroke="#000000"
- stroke-width="0.010"
- id="line206"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.204"
- y1="14.239"
- x2="1.832"
- y2="14.239"
- stroke="#000000"
- stroke-width="0.010"
- id="line208"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.832"
- y1="14.108"
- x2="4.204"
- y2="14.108"
- stroke="#000000"
- stroke-width="0.010"
- id="line210"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.204"
- y1="13.976"
- x2="1.832"
- y2="13.976"
- stroke="#000000"
- stroke-width="0.010"
- id="line212"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.832"
- y1="13.844"
- x2="4.204"
- y2="13.844"
- stroke="#000000"
- stroke-width="0.010"
- id="line214"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.204"
- y1="13.712"
- x2="1.832"
- y2="13.712"
- stroke="#000000"
- stroke-width="0.010"
- id="line216"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="1.832"
- y1="13.58"
- x2="4.204"
- y2="13.58"
- stroke="#000000"
- stroke-width="0.010"
- id="line218"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="4.204"
- y1="13.449"
- x2="1.832"
- y2="13.449"
- stroke="#000000"
- stroke-width="0.010"
- id="line220"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="3.5"
- y="15.5"
- id="text222"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Backup Domain</text>
- <text
- x="3.5"
- y="16.299999"
- id="text224"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Controller 1</text>
- <rect
- width="2.6359999"
- height="5.2709999"
- x="13.6"
- y="13.5"
- id="rect226"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.6359999"
- height="5.2709999"
- x="13.6"
- y="13.5"
- id="rect228"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.6359999"
- height="5.2709999"
- x="13.6"
- y="13.5"
- id="rect230"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="2.108"
- height="2.108"
- x="13.864"
- y="13.764"
- id="rect232"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.108"
- height="2.108"
- x="13.864"
- y="13.764"
- id="rect234"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.108"
- height="2.108"
- x="13.864"
- y="13.764"
- id="rect236"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.972"
- y1="14.291"
- x2="13.864"
- y2="14.291"
- stroke="#000000"
- stroke-width="0.010"
- id="line238"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.864"
- y1="14.818"
- x2="15.972"
- y2="14.818"
- stroke="#000000"
- stroke-width="0.010"
- id="line240"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.972"
- y1="15.213"
- x2="13.864"
- y2="15.213"
- stroke="#000000"
- stroke-width="0.010"
- id="line242"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.45"
- height="0.79100001"
- x="13.864"
- y="16.136"
- id="rect244"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="1.45"
- height="0.79100001"
- x="13.864"
- y="16.136"
- id="rect246"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.45"
- height="0.79100001"
- x="13.864"
- y="16.136"
- id="rect248"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.6"
- y1="17.058001"
- x2="16.236"
- y2="17.058001"
- stroke="#000000"
- stroke-width="0.010"
- id="line250"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.132"
- height="0.132"
- x="14.786"
- y="17.322001"
- id="rect252"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.132"
- height="0.132"
- x="14.786"
- y="17.322001"
- id="rect254"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.132"
- height="0.132"
- x="14.786"
- y="17.322001"
- id="rect256"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.132"
- height="0.132"
- x="15.313"
- y="17.322001"
- id="rect258"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.132"
- height="0.132"
- x="15.313"
- y="17.322001"
- id="rect260"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.132"
- height="0.132"
- x="15.313"
- y="17.322001"
- id="rect262"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.132"
- height="0.132"
- x="15.84"
- y="17.322001"
- id="rect264"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.132"
- height="0.132"
- x="15.84"
- y="17.322001"
- id="rect266"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.132"
- height="0.132"
- x="15.84"
- y="17.322001"
- id="rect268"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.264"
- height="0.132"
- x="15.708"
- y="16.531"
- id="rect270"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.264"
- height="0.132"
- x="15.708"
- y="16.531"
- id="rect272"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.264"
- height="0.132"
- x="15.708"
- y="16.531"
- id="rect274"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.864"
- y1="16.531"
- x2="15.313"
- y2="16.531"
- stroke="#000000"
- stroke-width="0.010"
- id="line276"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.39500001"
- height="0.39500001"
- x="13.864"
- y="17.190001"
- id="rect278"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.39500001"
- height="0.39500001"
- x="13.864"
- y="17.190001"
- id="rect280"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.39500001"
- height="0.39500001"
- x="13.864"
- y="17.190001"
- id="rect282"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.845"
- height="0.132"
- x="13.995"
- y="15.345"
- id="rect284"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.845"
- height="0.132"
- x="13.995"
- y="15.345"
- id="rect286"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.845"
- height="0.132"
- x="13.995"
- y="15.345"
- id="rect288"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.995"
- y1="16.267"
- x2="15.181"
- y2="16.267"
- stroke="#000000"
- stroke-width="0.010"
- id="line290"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.181"
- y1="16.399"
- x2="15.05"
- y2="16.399"
- stroke="#000000"
- stroke-width="0.010"
- id="line292"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.995"
- y1="16.399"
- x2="14.127"
- y2="16.399"
- stroke="#000000"
- stroke-width="0.010"
- id="line294"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.65899998"
- height="0.132"
- x="14.259"
- y="16.267"
- id="rect296"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.65899998"
- height="0.132"
- x="14.259"
- y="16.267"
- id="rect298"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.65899998"
- height="0.132"
- x="14.259"
- y="16.267"
- id="rect300"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.995"
- y1="15.608"
- x2="14.127"
- y2="15.608"
- stroke="#000000"
- stroke-width="0.010"
- id="line302"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="14.259"
- y1="15.608"
- x2="14.391"
- y2="15.608"
- stroke="#000000"
- stroke-width="0.010"
- id="line304"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="15.577"
- y1="15.608"
- x2="15.84"
- y2="15.608"
- stroke="#000000"
- stroke-width="0.010"
- id="line306"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.104"
- y1="18.639"
- x2="13.732"
- y2="18.639"
- stroke="#000000"
- stroke-width="0.010"
- id="line308"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.732"
- y1="18.507999"
- x2="16.104"
- y2="18.507999"
- stroke="#000000"
- stroke-width="0.010"
- id="line310"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.104"
- y1="18.375999"
- x2="13.732"
- y2="18.375999"
- stroke="#000000"
- stroke-width="0.010"
- id="line312"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.732"
- y1="18.243999"
- x2="16.104"
- y2="18.243999"
- stroke="#000000"
- stroke-width="0.010"
- id="line314"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.104"
- y1="18.112"
- x2="13.732"
- y2="18.112"
- stroke="#000000"
- stroke-width="0.010"
- id="line316"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="13.732"
- y1="17.98"
- x2="16.104"
- y2="17.98"
- stroke="#000000"
- stroke-width="0.010"
- id="line318"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="16.104"
- y1="17.849001"
- x2="13.732"
- y2="17.849001"
- stroke="#000000"
- stroke-width="0.010"
- id="line320"
- style="stroke:#000000;stroke-width:0.01" />
- <text
- x="16.9"
- y="14.7"
- id="text322"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Backup Domain</text>
- <text
- x="16.9"
- y="15.5"
- id="text324"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Controller 2</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.336,11.736 4.336,12.000 9.292,12.000 9.292,10.450 "
- id="polyline326"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="14.918,13.500 14.918,11.975 9.292,11.975 9.292,10.450 "
- id="polyline328"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.3000002"
- height="1.767"
- x="17.4"
- y="4.9000001"
- id="rect330"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="5.3000002"
- height="1.767"
- x="17.4"
- y="4.9000001"
- id="rect332"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.3000002"
- height="1.767"
- x="17.4"
- y="4.9000001"
- id="rect334"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="2.0190001"
- height="1.01"
- x="20.555"
- y="5.4050002"
- id="rect336"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.0190001"
- height="1.01"
- x="20.555"
- y="5.4050002"
- id="rect338"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.0190001"
- height="1.01"
- x="20.555"
- y="5.4050002"
- id="rect340"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="22.573999"
- y1="5.9099998"
- x2="20.555"
- y2="5.9099998"
- stroke="#000000"
- stroke-width="0.010"
- id="line342"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.37900001"
- height="1.388"
- x="20.049999"
- y="5.026"
- id="rect344"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.37900001"
- height="1.388"
- x="20.049999"
- y="5.026"
- id="rect346"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.37900001"
- height="1.388"
- x="20.049999"
- y="5.026"
- id="rect348"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.126"
- height="0.126"
- x="18.662001"
- y="5.152"
- id="rect350"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.126"
- height="0.126"
- x="18.662001"
- y="5.152"
- id="rect352"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.126"
- height="0.126"
- x="18.662001"
- y="5.152"
- id="rect354"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.126"
- height="0.126"
- x="18.914"
- y="5.152"
- id="rect356"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.126"
- height="0.126"
- x="18.914"
- y="5.152"
- id="rect358"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.126"
- height="0.126"
- x="18.914"
- y="5.152"
- id="rect360"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.126"
- height="0.126"
- x="19.167"
- y="5.152"
- id="rect362"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.126"
- height="0.126"
- x="19.167"
- y="5.152"
- id="rect364"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.126"
- height="0.126"
- x="19.167"
- y="5.152"
- id="rect366"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.252"
- height="0.252"
- x="19.545"
- y="5.026"
- id="rect368"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.252"
- height="0.252"
- x="19.545"
- y="5.026"
- id="rect370"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.252"
- height="0.252"
- x="19.545"
- y="5.026"
- id="rect372"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.37900001"
- height="0.37900001"
- x="17.652"
- y="5.026"
- id="rect374"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.37900001"
- height="0.37900001"
- x="17.652"
- y="5.026"
- id="rect376"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.37900001"
- height="0.37900001"
- x="17.652"
- y="5.026"
- id="rect378"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.767"
- height="0.126"
- x="20.681"
- y="6.0359998"
- id="rect380"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.767"
- height="0.126"
- x="20.681"
- y="6.0359998"
- id="rect382"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.767"
- height="0.126"
- x="20.681"
- y="6.0359998"
- id="rect384"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.176001"
- y1="5.152"
- x2="20.176001"
- y2="6.2880001"
- stroke="#000000"
- stroke-width="0.010"
- id="line386"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.126"
- height="0.63099998"
- x="20.176001"
- y="5.4050002"
- id="rect388"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.126"
- height="0.63099998"
- x="20.176001"
- y="5.4050002"
- id="rect390"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.126"
- height="0.63099998"
- x="20.176001"
- y="5.4050002"
- id="rect392"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="22.195"
- y1="6.2880001"
- x2="22.448"
- y2="6.2880001"
- stroke="#000000"
- stroke-width="0.010"
- id="line394"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.525999"
- y1="5.783"
- x2="19.798"
- y2="5.783"
- stroke="#000000"
- stroke-width="0.010"
- id="line396"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.798"
- y1="5.9099998"
- x2="17.525999"
- y2="5.9099998"
- stroke="#000000"
- stroke-width="0.010"
- id="line398"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.525999"
- y1="6.0359998"
- x2="19.798"
- y2="6.0359998"
- stroke="#000000"
- stroke-width="0.010"
- id="line400"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.798"
- y1="6.414"
- x2="17.525999"
- y2="6.414"
- stroke="#000000"
- stroke-width="0.010"
- id="line402"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.525999"
- y1="6.2880001"
- x2="19.798"
- y2="6.2880001"
- stroke="#000000"
- stroke-width="0.010"
- id="line404"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.798"
- y1="6.1620002"
- x2="17.525999"
- y2="6.1620002"
- stroke="#000000"
- stroke-width="0.010"
- id="line406"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.681"
- y1="6.2880001"
- x2="20.806999"
- y2="6.2880001"
- stroke="#000000"
- stroke-width="0.010"
- id="line408"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.933001"
- y1="6.2880001"
- x2="21.059999"
- y2="6.2880001"
- stroke="#000000"
- stroke-width="0.010"
- id="line410"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.302"
- y1="6.2880001"
- x2="20.302"
- y2="6.1620002"
- stroke="#000000"
- stroke-width="0.010"
- id="line412"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.302"
- y1="5.2789998"
- x2="20.302"
- y2="5.152"
- stroke="#000000"
- stroke-width="0.010"
- id="line414"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="5.4000001"
- height="1.8"
- x="17.4"
- y="7.4000001"
- id="rect416"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="5.4000001"
- height="1.8"
- x="17.4"
- y="7.4000001"
- id="rect418"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.4000001"
- height="1.8"
- x="17.4"
- y="7.4000001"
- id="rect420"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="2.0569999"
- height="1.029"
- x="20.614"
- y="7.914"
- id="rect422"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.0569999"
- height="1.029"
- x="20.614"
- y="7.914"
- id="rect424"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.0569999"
- height="1.029"
- x="20.614"
- y="7.914"
- id="rect426"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="22.671"
- y1="8.4289999"
- x2="20.614"
- y2="8.4289999"
- stroke="#000000"
- stroke-width="0.010"
- id="line428"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.38600001"
- height="1.414"
- x="20.1"
- y="7.5289998"
- id="rect430"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.38600001"
- height="1.414"
- x="20.1"
- y="7.5289998"
- id="rect432"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.38600001"
- height="1.414"
- x="20.1"
- y="7.5289998"
- id="rect434"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="18.686001"
- y="7.6570001"
- id="rect436"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="18.686001"
- y="7.6570001"
- id="rect438"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="18.686001"
- y="7.6570001"
- id="rect440"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="18.943001"
- y="7.6570001"
- id="rect442"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="18.943001"
- y="7.6570001"
- id="rect444"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="18.943001"
- y="7.6570001"
- id="rect446"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="19.200001"
- y="7.6570001"
- id="rect448"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="19.200001"
- y="7.6570001"
- id="rect450"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.12899999"
- height="0.12899999"
- x="19.200001"
- y="7.6570001"
- id="rect452"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.257"
- height="0.257"
- x="19.586"
- y="7.5289998"
- id="rect454"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.257"
- height="0.257"
- x="19.586"
- y="7.5289998"
- id="rect456"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.257"
- height="0.257"
- x="19.586"
- y="7.5289998"
- id="rect458"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.38600001"
- height="0.38600001"
- x="17.657"
- y="7.5289998"
- id="rect460"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.38600001"
- height="0.38600001"
- x="17.657"
- y="7.5289998"
- id="rect462"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.38600001"
- height="0.38600001"
- x="17.657"
- y="7.5289998"
- id="rect464"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.8"
- height="0.12899999"
- x="20.743"
- y="8.5570002"
- id="rect466"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.8"
- height="0.12899999"
- x="20.743"
- y="8.5570002"
- id="rect468"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.8"
- height="0.12899999"
- x="20.743"
- y="8.5570002"
- id="rect470"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.229"
- y1="7.6570001"
- x2="20.229"
- y2="8.8140001"
- stroke="#000000"
- stroke-width="0.010"
- id="line472"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.12899999"
- height="0.64300001"
- x="20.229"
- y="7.914"
- id="rect474"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.12899999"
- height="0.64300001"
- x="20.229"
- y="7.914"
- id="rect476"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.12899999"
- height="0.64300001"
- x="20.229"
- y="7.914"
- id="rect478"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="22.285999"
- y1="8.8140001"
- x2="22.542999"
- y2="8.8140001"
- stroke="#000000"
- stroke-width="0.010"
- id="line480"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.528999"
- y1="8.3000002"
- x2="19.843"
- y2="8.3000002"
- stroke="#000000"
- stroke-width="0.010"
- id="line482"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.843"
- y1="8.4289999"
- x2="17.528999"
- y2="8.4289999"
- stroke="#000000"
- stroke-width="0.010"
- id="line484"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.528999"
- y1="8.5570002"
- x2="19.843"
- y2="8.5570002"
- stroke="#000000"
- stroke-width="0.010"
- id="line486"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.843"
- y1="8.9429998"
- x2="17.528999"
- y2="8.9429998"
- stroke="#000000"
- stroke-width="0.010"
- id="line488"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.528999"
- y1="8.8140001"
- x2="19.843"
- y2="8.8140001"
- stroke="#000000"
- stroke-width="0.010"
- id="line490"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.843"
- y1="8.6859999"
- x2="17.528999"
- y2="8.6859999"
- stroke="#000000"
- stroke-width="0.010"
- id="line492"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.743"
- y1="8.8140001"
- x2="20.871"
- y2="8.8140001"
- stroke="#000000"
- stroke-width="0.010"
- id="line494"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21"
- y1="8.8140001"
- x2="21.129"
- y2="8.8140001"
- stroke="#000000"
- stroke-width="0.010"
- id="line496"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.357"
- y1="8.8140001"
- x2="20.357"
- y2="8.6859999"
- stroke="#000000"
- stroke-width="0.010"
- id="line498"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.357"
- y1="7.7859998"
- x2="20.357"
- y2="7.6570001"
- stroke="#000000"
- stroke-width="0.010"
- id="line500"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="5.4499998"
- height="1.817"
- x="17.5"
- y="9.8000002"
- id="rect502"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="5.4499998"
- height="1.817"
- x="17.5"
- y="9.8000002"
- id="rect504"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.4499998"
- height="1.817"
- x="17.5"
- y="9.8000002"
- id="rect506"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="2.076"
- height="1.038"
- x="20.743999"
- y="10.319"
- id="rect508"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="2.076"
- height="1.038"
- x="20.743999"
- y="10.319"
- id="rect510"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="2.076"
- height="1.038"
- x="20.743999"
- y="10.319"
- id="rect512"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="22.82"
- y1="10.838"
- x2="20.743999"
- y2="10.838"
- stroke="#000000"
- stroke-width="0.010"
- id="line514"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.389"
- height="1.427"
- x="20.225"
- y="9.9300003"
- id="rect516"
- style="fill:#d9d9cd;stroke:none;stroke-width:0" />
- <rect
- width="0.389"
- height="1.427"
- x="20.225"
- y="9.9300003"
- id="rect518"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.389"
- height="1.427"
- x="20.225"
- y="9.9300003"
- id="rect520"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.13"
- height="0.13"
- x="18.798"
- y="10.06"
- id="rect522"
- style="fill:#00cd00;stroke:none;stroke-width:0" />
- <rect
- width="0.13"
- height="0.13"
- x="18.798"
- y="10.06"
- id="rect524"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.13"
- height="0.13"
- x="18.798"
- y="10.06"
- id="rect526"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.13"
- height="0.13"
- x="19.056999"
- y="10.06"
- id="rect528"
- style="fill:#cdcd00;stroke:none;stroke-width:0" />
- <rect
- width="0.13"
- height="0.13"
- x="19.056999"
- y="10.06"
- id="rect530"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.13"
- height="0.13"
- x="19.056999"
- y="10.06"
- id="rect532"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.13"
- height="0.13"
- x="19.316999"
- y="10.06"
- id="rect534"
- style="fill:#cd0000;stroke:none;stroke-width:0" />
- <rect
- width="0.13"
- height="0.13"
- x="19.316999"
- y="10.06"
- id="rect536"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.13"
- height="0.13"
- x="19.316999"
- y="10.06"
- id="rect538"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.25999999"
- height="0.25999999"
- x="19.705999"
- y="9.9300003"
- id="rect540"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.25999999"
- height="0.25999999"
- x="19.705999"
- y="9.9300003"
- id="rect542"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.25999999"
- height="0.25999999"
- x="19.705999"
- y="9.9300003"
- id="rect544"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.389"
- height="0.389"
- x="17.76"
- y="9.9300003"
- id="rect546"
- style="fill:#cdcdbd;stroke:none;stroke-width:0" />
- <rect
- width="0.389"
- height="0.389"
- x="17.76"
- y="9.9300003"
- id="rect548"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.389"
- height="0.389"
- x="17.76"
- y="9.9300003"
- id="rect550"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.817"
- height="0.13"
- x="20.874001"
- y="10.968"
- id="rect552"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="1.817"
- height="0.13"
- x="20.874001"
- y="10.968"
- id="rect554"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.817"
- height="0.13"
- x="20.874001"
- y="10.968"
- id="rect556"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.355"
- y1="10.06"
- x2="20.355"
- y2="11.227"
- stroke="#000000"
- stroke-width="0.010"
- id="line558"
- style="stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.13"
- height="0.64899999"
- x="20.355"
- y="10.319"
- id="rect560"
- style="fill:#cdcdc1;stroke:none;stroke-width:0" />
- <rect
- width="0.13"
- height="0.64899999"
- x="20.355"
- y="10.319"
- id="rect562"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="0.13"
- height="0.64899999"
- x="20.355"
- y="10.319"
- id="rect564"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <line
- x1="22.431"
- y1="11.227"
- x2="22.690001"
- y2="11.227"
- stroke="#000000"
- stroke-width="0.010"
- id="line566"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.629999"
- y1="10.708"
- x2="19.965"
- y2="10.708"
- stroke="#000000"
- stroke-width="0.010"
- id="line568"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.965"
- y1="10.838"
- x2="17.629999"
- y2="10.838"
- stroke="#000000"
- stroke-width="0.010"
- id="line570"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.629999"
- y1="10.968"
- x2="19.965"
- y2="10.968"
- stroke="#000000"
- stroke-width="0.010"
- id="line572"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.965"
- y1="11.357"
- x2="17.629999"
- y2="11.357"
- stroke="#000000"
- stroke-width="0.010"
- id="line574"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="17.629999"
- y1="11.227"
- x2="19.965"
- y2="11.227"
- stroke="#000000"
- stroke-width="0.010"
- id="line576"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="19.965"
- y1="11.098"
- x2="17.629999"
- y2="11.098"
- stroke="#000000"
- stroke-width="0.010"
- id="line578"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.874001"
- y1="11.227"
- x2="21.004"
- y2="11.227"
- stroke="#000000"
- stroke-width="0.010"
- id="line580"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="21.132999"
- y1="11.227"
- x2="21.263"
- y2="11.227"
- stroke="#000000"
- stroke-width="0.010"
- id="line582"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.485001"
- y1="11.227"
- x2="20.485001"
- y2="11.098"
- stroke="#000000"
- stroke-width="0.010"
- id="line584"
- style="stroke:#000000;stroke-width:0.01" />
- <line
- x1="20.485001"
- y1="10.189"
- x2="20.485001"
- y2="10.06"
- stroke="#000000"
- stroke-width="0.010"
- id="line586"
- style="stroke:#000000;stroke-width:0.01" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="9.300,12.000 13.992,12.000 13.992,5.783 17.400,5.783 "
- id="polyline588"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="17.400,8.300 14.000,8.300 14.000,12.000 10.200,12.000 "
- id="polyline590"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="17.500,10.708 14.000,10.708 14.000,12.000 10.300,12.000 "
- id="polyline592"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="17.700001"
- y="4.3000002"
- id="text594"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Workstation A</text>
- <text
- x="23.799999"
- y="8.6000004"
- id="text596"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Workstation B</text>
- <text
- x="23.799999"
- y="10.9"
- id="text598"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Workstation C</text>
- <text
- x="13.1"
- y="1.7"
- id="text600"
- style="font-size:1.20000005px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">DOMAIN</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="24.174cm"
- height="19.486cm"
- viewBox="-0.49 0.171 23.684 19.657"
- id="svg2">
- <defs
- id="defs97" />
- <path
- d="M 3.333,0.221 L 5.667,0.221 C 5.989,0.221 6.25,0.626 6.25,1.125 C 6.25,1.624 5.989,2.029 5.667,2.029 L 3.333,2.029 C 3.011,2.029 2.75,1.624 2.75,1.125 C 2.75,0.626 3.011,0.221 3.333,0.221"
- id="path4"
- style="fill:#c9c9c9;stroke:none;stroke-width:0.1" />
- <path
- d="M 3.333,0.221 L 5.667,0.221 C 5.989,0.221 6.25,0.626 6.25,1.125 C 6.25,1.624 5.989,2.029 5.667,2.029 L 3.333,2.029 C 3.011,2.029 2.75,1.624 2.75,1.125 C 2.75,0.626 3.011,0.221 3.333,0.221"
- id="path6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3.7609999"
- y="1.303"
- id="text8"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">GID</text>
- <line
- x1="4.5040002"
- y1="5.5"
- x2="4.5019999"
- y2="6.1500001"
- stroke="#000000"
- stroke-width="0.100"
- id="line10"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.102,6.149 4.5,6.95 4.902,6.151 4.102,6.149 "
- id="polygon12"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 5.883,16.8 L 9.117,16.8 C 9.564,16.8 9.926,17.428 9.926,18.204 C 9.926,18.979 9.564,19.607 9.117,19.607 L 5.883,19.607 C 5.436,19.607 5.074,18.979 5.074,18.204 C 5.074,17.428 5.436,16.8 5.883,16.8"
- id="path14"
- style="fill:#d5d5d5;stroke:none;stroke-width:0.1" />
- <path
- d="M 5.883,16.8 L 9.117,16.8 C 9.564,16.8 9.926,17.428 9.926,18.204 C 9.926,18.979 9.564,19.607 9.117,19.607 L 5.883,19.607 C 5.436,19.607 5.074,18.979 5.074,18.204 C 5.074,17.428 5.436,16.8 5.883,16.8"
- id="path16"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.2859998"
- y="17.881001"
- id="text18"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">group</text>
- <text
- x="6.7989998"
- y="18.881001"
- id="text20"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
- <path
- d="M 16.083,11.65 L 18.417,11.65 C 18.739,11.65 19,12.055 19,12.554 C 19,13.053 18.739,13.457 18.417,13.457 L 16.083,13.457 C 15.761,13.457 15.5,13.053 15.5,12.554 C 15.5,12.055 15.761,11.65 16.083,11.65"
- id="path22"
- style="fill:#dbd8d8;stroke:none;stroke-width:0.1" />
- <path
- d="M 16.083,11.65 L 18.417,11.65 C 18.739,11.65 19,12.055 19,12.554 C 19,13.053 18.739,13.457 18.417,13.457 L 16.083,13.457 C 15.761,13.457 15.5,13.053 15.5,12.554 C 15.5,12.055 15.761,11.65 16.083,11.65"
- id="path24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="16.525999"
- y="12.731"
- id="text26"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
- <line
- x1="13"
- y1="12.5"
- x2="14.65"
- y2="12.5"
- stroke="#000000"
- stroke-width="0.100"
- id="line28"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="14.65,12.9 15.45,12.5 14.65,12.1 14.65,12.9 "
- id="polygon30"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="11,11 13,12.5 11,14 9,12.5 11,11 "
- id="polygon32"
- style="fill:#abfafe;stroke:none;stroke-width:0.1" />
- <polygon
- points="11,11 13,12.5 11,14 9,12.5 11,11 "
- id="polygon34"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="9.5229998"
- y="12.75"
- id="text36"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
- <text
- x="11.531"
- y="15"
- id="text38"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <line
- x1="10.989"
- y1="9.3999996"
- x2="10.994"
- y2="10.15"
- stroke="#000000"
- stroke-width="0.100"
- id="line40"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="10.594,10.153 11,10.95 11.394,10.147 10.594,10.153 "
- id="polygon42"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="13.104"
- y="12.25"
- id="text44"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="7.5"
- y1="15.25"
- x2="7.5"
- y2="15.95"
- stroke="#000000"
- stroke-width="0.100"
- id="line46"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.1,15.95 7.5,16.75 7.9,15.95 7.1,15.95 "
- id="polygon48"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.5,7 6.5,8.5 4.5,10 2.5,8.5 4.5,7 "
- id="polygon50"
- style="fill:#c5effb;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.5,7 6.5,8.5 4.5,10 2.5,8.5 4.5,7 "
- id="polygon52"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3.0220001"
- y="8.75"
- id="text54"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
- <text
- x="5.0310001"
- y="10.75"
- id="text56"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <line
- x1="4.5"
- y1="2.029"
- x2="4.5009999"
- y2="2.55"
- stroke="#000000"
- stroke-width="0.100"
- id="line58"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.101,2.551 4.503,3.35 4.901,2.549 4.101,2.551 "
- id="polygon60"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="6.6040001"
- y="8.25"
- id="text62"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="6.5"
- y1="8.5"
- x2="8.1499996"
- y2="8.5"
- stroke="#000000"
- stroke-width="0.100"
- id="line64"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="8.15,8.9 8.95,8.5 8.15,8.1 8.15,8.9 "
- id="polygon66"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="8.7440004"
- y="7.4000001"
- id="rect68"
- style="fill:#d5d5d5;stroke:none;stroke-width:0" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="8.7440004"
- y="7.4000001"
- id="rect70"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="9.2939997"
- y="8.6280003"
- id="text72"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
- <line
- x1="13.25"
- y1="8.75"
- x2="15.25"
- y2="9.5"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="13.25"
- y1="8.25"
- x2="15.25"
- y2="7.5"
- stroke="#000000"
- stroke-width="0.050"
- id="line76"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="8"
- height="2"
- x="15.5"
- y="7.5"
- id="rect78"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="8"
- height="2"
- x="15.5"
- y="7.5"
- id="rect80"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="15.316"
- y="8.25"
- id="text82"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
- <text
- x="17.761999"
- y="9.25"
- id="text84"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
- <line
- x1="23.5"
- y1="8.5"
- x2="15.5"
- y2="8.5"
- stroke="#000000"
- stroke-width="0.050"
- id="line86"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="9.8870001"
- height="2.0999999"
- x="-0.44"
- y="3.4000001"
- id="rect88"
- style="fill:#dcdcdc;stroke:none;stroke-width:0" />
- <rect
- width="9.8870001"
- height="2.0999999"
- x="-0.44"
- y="3.4000001"
- id="rect90"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="0.11"
- y="4.6269999"
- id="text92"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">groupmap_idmap.tdb</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.500,10.000 4.500,15.250 11.000,15.250 11.000,14.000 "
- id="polyline94"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="9.6999998cm"
- height="17.848cm"
- viewBox="2.95 0.95 12.65 18.798"
- id="svg2">
- <defs
- id="defs49" />
- <text
- x="3.7"
- y="1.9"
- id="text4"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Grou</text>
- <text
- x="3.7"
- y="2"
- id="text6"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">group</text>
- <rect
- width="9.6000004"
- height="3"
- x="3"
- y="1"
- id="rect8"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="9.6000004"
- height="3"
- x="3"
- y="1"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="9.5500002"
- height="3.3"
- x="3"
- y="15.4"
- id="rect12"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="9.5500002"
- height="3.3"
- x="3"
- y="15.4"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="9.5500002"
- height="3.5"
- x="3"
- y="8"
- id="rect16"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="9.5500002"
- height="3.5"
- x="3"
- y="8"
- id="rect18"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3.75"
- y="2.05"
- id="text20"
- style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">group_mapping tdb</text>
- <text
- x="3.6500001"
- y="3.5"
- id="text22"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">contains samba groups</text>
- <text
- x="5.5999999"
- y="9.0620003"
- id="text24"
- style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">idmap gid</text>
- <text
- x="4.25"
- y="10.25"
- id="text26"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">maps UNIX groups to</text>
- <text
- x="4.25"
- y="11.05"
- id="text28"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">samba groups</text>
- <text
- x="5.0500002"
- y="16.5"
- id="text30"
- style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">UNIX groups</text>
- <text
- x="4.8499999"
- y="17.6"
- id="text32"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">/etc/group or other</text>
- <text
- x="4.8499999"
- y="18.4"
- id="text34"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">NSS backend</text>
- <polygon
- points="7.183,6.963 7.183,5.01 6.694,5.01 7.671,4.034 8.647,5.01 8.159,5.01 8.159,6.963 8.647,6.963 7.671,7.939 6.694,6.963 7.183,6.963 "
- id="polygon36"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="7.183,6.963 7.183,5.01 6.694,5.01 7.671,4.034 8.647,5.01 8.159,5.01 8.159,6.963 8.647,6.963 7.671,7.939 6.694,6.963 7.183,6.963 "
- id="polygon38"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.183,6.963 7.183,5.01 6.694,5.01 7.671,4.034 8.647,5.01 8.159,5.01 8.159,6.963 8.647,6.963 7.671,7.939 6.694,6.963 7.183,6.963 "
- id="polygon40"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="7.196,14.421 7.196,12.521 6.721,12.521 7.671,11.571 8.621,12.521 8.146,12.521 8.146,14.421 8.621,14.421 7.671,15.371 6.721,14.421 7.196,14.421 "
- id="polygon42"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="7.196,14.421 7.196,12.521 6.721,12.521 7.671,11.571 8.621,12.521 8.146,12.521 8.146,14.421 8.621,14.421 7.671,15.371 6.721,14.421 7.196,14.421 "
- id="polygon44"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.196,14.421 7.196,12.521 6.721,12.521 7.671,11.571 8.621,12.521 8.146,12.521 8.146,14.421 8.621,14.421 7.671,15.371 6.721,14.421 7.196,14.421 "
- id="polygon46"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="23.674999cm"
- height="19.329cm"
- viewBox="-0.492 0 23.184 19.329"
- id="svg2">
- <defs
- id="defs97" />
- <path
- d="M 6.333,17.471 L 8.667,17.471 C 8.989,17.471 9.25,17.876 9.25,18.375 C 9.25,18.874 8.989,19.279 8.667,19.279 L 6.333,19.279 C 6.011,19.279 5.75,18.874 5.75,18.375 C 5.75,17.876 6.011,17.471 6.333,17.471"
- id="path4"
- style="fill:#dcdcdc;stroke:none;stroke-width:0.1" />
- <path
- d="M 6.333,17.471 L 8.667,17.471 C 8.989,17.471 9.25,17.876 9.25,18.375 C 9.25,18.874 8.989,19.279 8.667,19.279 L 6.333,19.279 C 6.011,19.279 5.75,18.874 5.75,18.375 C 5.75,17.876 6.011,17.471 6.333,17.471"
- id="path6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.7610002"
- y="18.552"
- id="text8"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">GID</text>
- <line
- x1="4.5019999"
- y1="6"
- x2="4.5009999"
- y2="6.6500001"
- stroke="#000000"
- stroke-width="0.100"
- id="line10"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.101,6.649 4.5,7.45 4.901,6.651 4.101,6.649 "
- id="polygon12"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 2.883,0.05 L 6.117,0.05 C 6.564,0.05 6.926,0.678 6.926,1.454 C 6.926,2.229 6.564,2.857 6.117,2.857 L 2.883,2.857 C 2.436,2.857 2.074,2.229 2.074,1.454 C 2.074,0.678 2.436,0.05 2.883,0.05"
- id="path14"
- style="fill:#cfcfcf;stroke:none;stroke-width:0.1" />
- <path
- d="M 2.883,0.05 L 6.117,0.05 C 6.564,0.05 6.926,0.678 6.926,1.454 C 6.926,2.229 6.564,2.857 6.117,2.857 L 2.883,2.857 C 2.436,2.857 2.074,2.229 2.074,1.454 C 2.074,0.678 2.436,0.05 2.883,0.05"
- id="path16"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3.286"
- y="1.131"
- id="text18"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">group</text>
- <text
- x="3.799"
- y="2.131"
- id="text20"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
- <path
- d="M 15.181,12.15 L 17.435,12.15 C 17.746,12.15 17.999,12.555 17.999,13.054 C 17.999,13.553 17.746,13.957 17.435,13.957 L 15.181,13.957 C 14.869,13.957 14.617,13.553 14.617,13.054 C 14.617,12.555 14.869,12.15 15.181,12.15"
- id="path22"
- style="fill:#dcdcdc;stroke:none;stroke-width:0.1" />
- <path
- d="M 15.181,12.15 L 17.435,12.15 C 17.746,12.15 17.999,12.555 17.999,13.054 C 17.999,13.553 17.746,13.957 17.435,13.957 L 15.181,13.957 C 14.869,13.957 14.617,13.553 14.617,13.054 C 14.617,12.555 14.869,12.15 15.181,12.15"
- id="path24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="15.584"
- y="13.231"
- id="text26"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
- <line
- x1="12.5"
- y1="13"
- x2="13.9"
- y2="13"
- stroke="#000000"
- stroke-width="0.100"
- id="line28"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="13.9,13.4 14.7,13 13.9,12.6 13.9,13.4 "
- id="polygon30"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.5,11.5 12.5,13 10.5,14.5 8.5,13 10.5,11.5 "
- id="polygon32"
- style="fill:#bef2ff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.5,11.5 12.5,13 10.5,14.5 8.5,13 10.5,11.5 "
- id="polygon34"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="9.0229998"
- y="13.25"
- id="text36"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
- <text
- x="11.031"
- y="15.5"
- id="text38"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <line
- x1="10.489"
- y1="10"
- x2="10.494"
- y2="10.65"
- stroke="#000000"
- stroke-width="0.100"
- id="line40"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="10.094,10.653 10.5,11.45 10.894,10.647 10.094,10.653 "
- id="polygon42"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="12.604"
- y="12.75"
- id="text44"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="7.5"
- y1="15.75"
- x2="7.5"
- y2="16.65"
- stroke="#000000"
- stroke-width="0.100"
- id="line46"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.1,16.65 7.5,17.45 7.9,16.65 7.1,16.65 "
- id="polygon48"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.5,7.5 6.5,9 4.5,10.5 2.5,9 4.5,7.5 "
- id="polygon50"
- style="fill:#acedff;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.5,7.5 6.5,9 4.5,10.5 2.5,9 4.5,7.5 "
- id="polygon52"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="3.0220001"
- y="9.25"
- id="text54"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
- <text
- x="5.0310001"
- y="11.25"
- id="text56"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <line
- x1="4.5"
- y1="2.8570001"
- x2="4.5"
- y2="3.05"
- stroke="#000000"
- stroke-width="0.100"
- id="line58"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.1,3.051 4.502,3.85 4.9,3.049 4.1,3.051 "
- id="polygon60"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="6.6040001"
- y="8.75"
- id="text62"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="6.5"
- y1="9"
- x2="7.6500001"
- y2="9"
- stroke="#000000"
- stroke-width="0.100"
- id="line64"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="7.65,9.4 8.45,9 7.65,8.6 7.65,9.4 "
- id="polygon66"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="8.2440004"
- y="7.9000001"
- id="rect68"
- style="fill:#dcdcdc;stroke:none;stroke-width:0" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="8.2440004"
- y="7.9000001"
- id="rect70"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="8.7939997"
- y="9.1280003"
- id="text72"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
- <line
- x1="12.75"
- y1="9.25"
- x2="14.75"
- y2="10"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="12.75"
- y1="8.75"
- x2="14.75"
- y2="8"
- stroke="#000000"
- stroke-width="0.050"
- id="line76"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="8"
- height="2"
- x="15"
- y="8"
- id="rect78"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="8"
- height="2"
- x="15"
- y="8"
- id="rect80"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="14.816"
- y="8.75"
- id="text82"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
- <text
- x="17.261999"
- y="9.75"
- id="text84"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
- <line
- x1="23"
- y1="9"
- x2="15"
- y2="9"
- stroke="#000000"
- stroke-width="0.050"
- id="line86"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="9.8870001"
- height="2.0999999"
- x="-0.442"
- y="3.9000001"
- id="rect88"
- style="fill:#d3d3d3;stroke:none;stroke-width:0" />
- <rect
- width="9.8870001"
- height="2.0999999"
- x="-0.442"
- y="3.9000001"
- id="rect90"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="0.108"
- y="5.1269999"
- id="text92"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">groupmap_idmap.tdb</text>
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="4.500,10.500 4.500,15.500 10.500,15.500 10.500,14.500 "
- id="polyline94"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="33.234001cm"
- height="20.391001cm"
- viewBox="0.066 0.921 33.3 21.312"
- id="svg2">
- <defs
- id="defs121" />
- <line
- x1="12.5"
- y1="2.779"
- x2="12.5"
- y2="4.9000001"
- stroke="#000000"
- stroke-width="0.100"
- id="line4"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.1,4.9 12.5,5.7 12.9,4.9 12.1,4.9 "
- id="polygon6"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
- id="path8"
- style="fill:#d9d9d9;stroke:none;stroke-width:0.1" />
- <path
- d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
- id="path10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="11.799"
- y="2.053"
- id="text12"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
- <polygon
- points="12.5,5.75 15.5,7.75 12.5,9.75 9.5,7.75 12.5,5.75 "
- id="polygon14"
- style="fill:#aff3f6;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.5,5.75 15.5,7.75 12.5,9.75 9.5,7.75 12.5,5.75 "
- id="polygon16"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="9.8459997"
- y="8"
- id="text18"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Our Domain?</text>
- <line
- x1="15.5"
- y1="7.75"
- x2="17.65"
- y2="7.75"
- stroke="#000000"
- stroke-width="0.100"
- id="line20"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="17.65,8.15 18.45,7.75 17.65,7.35 17.65,8.15 "
- id="polygon22"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="16.031"
- y="7.5"
- id="text24"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <line
- x1="12.5"
- y1="9.75"
- x2="12.493"
- y2="11.55"
- stroke="#000000"
- stroke-width="0.100"
- id="line26"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.093,11.548 12.49,12.35 12.893,11.552 12.093,11.548 "
- id="polygon28"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <text
- x="12.854"
- y="10.75"
- id="text30"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="16.5"
- y1="15.25"
- x2="16.5"
- y2="17.4"
- stroke="#000000"
- stroke-width="0.100"
- id="line32"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="16.1,17.4 16.5,18.2 16.9,17.4 16.1,17.4 "
- id="polygon34"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 21.833,18.9 L 24.167,18.9 C 24.489,18.9 24.75,19.305 24.75,19.804 C 24.75,20.303 24.489,20.707 24.167,20.707 L 21.833,20.707 C 21.511,20.707 21.25,20.303 21.25,19.804 C 21.25,19.305 21.511,18.9 21.833,18.9"
- id="path36"
- style="fill:#d9d9d9;stroke:none;stroke-width:0.1" />
- <path
- d="M 21.833,18.9 L 24.167,18.9 C 24.489,18.9 24.75,19.305 24.75,19.804 C 24.75,20.303 24.489,20.707 24.167,20.707 L 21.833,20.707 C 21.511,20.707 21.25,20.303 21.25,19.804 C 21.25,19.305 21.511,18.9 21.833,18.9"
- id="path38"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="22.264999"
- y="19.981001"
- id="text40"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">UID</text>
- <polygon
- points="16.5,18.25 18.5,19.75 16.5,21.25 14.5,19.75 16.5,18.25 "
- id="polygon42"
- style="fill:#a1fdfb;stroke:none;stroke-width:0.1" />
- <polygon
- points="16.5,18.25 18.5,19.75 16.5,21.25 14.5,19.75 16.5,18.25 "
- id="polygon44"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="15.023"
- y="20"
- id="text46"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
- <text
- x="18.781"
- y="19.5"
- id="text48"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <text
- x="13.354"
- y="19.5"
- id="text50"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="18.5"
- y1="19.75"
- x2="20.4"
- y2="19.75"
- stroke="#000000"
- stroke-width="0.100"
- id="line52"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="20.4,20.15 21.2,19.75 20.4,19.35 20.4,20.15 "
- id="polygon54"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="14.5"
- y1="19.75"
- x2="12.6"
- y2="19.75"
- stroke="#000000"
- stroke-width="0.100"
- id="line56"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.6,19.35 11.8,19.75 12.6,20.15 12.6,19.35 "
- id="polygon58"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 8.833,18.9 L 11.167,18.9 C 11.489,18.9 11.75,19.305 11.75,19.804 C 11.75,20.303 11.489,20.707 11.167,20.707 L 8.833,20.707 C 8.511,20.707 8.25,20.303 8.25,19.804 C 8.25,19.305 8.511,18.9 8.833,18.9"
- id="path60"
- style="fill:#d7d7d7;stroke:none;stroke-width:0.1" />
- <path
- d="M 8.833,18.9 L 11.167,18.9 C 11.489,18.9 11.75,19.305 11.75,19.804 C 11.75,20.303 11.489,20.707 11.167,20.707 L 8.833,20.707 C 8.511,20.707 8.25,20.303 8.25,19.804 C 8.25,19.305 8.511,18.9 8.833,18.9"
- id="path62"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="9.276"
- y="19.981001"
- id="text64"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
- <rect
- width="4.1399999"
- height="2.0999999"
- x="18.419001"
- y="6.6500001"
- id="rect66"
- style="fill:#d9d6d6;stroke:none;stroke-width:0" />
- <rect
- width="4.1399999"
- height="2.0999999"
- x="18.419001"
- y="6.6500001"
- id="rect68"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="18.969"
- y="7.8779998"
- id="text70"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">PassDB</text>
- <line
- x1="22.75"
- y1="6.5"
- x2="25"
- y2="5.25"
- stroke="#000000"
- stroke-width="0.050"
- id="line72"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="22.75"
- y1="8.75"
- x2="25"
- y2="10"
- stroke="#000000"
- stroke-width="0.050"
- id="line74"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="8"
- height="5.25"
- x="25.25"
- y="5"
- id="rect76"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="8"
- height="5.25"
- x="25.25"
- y="5"
- id="rect78"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="28.089001"
- y="5.75"
- id="text80"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">guest</text>
- <text
- x="26.85"
- y="6.75"
- id="text82"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">smbpasswd</text>
- <text
- x="27.709"
- y="7.75"
- id="text84"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">tdbsam</text>
- <text
- x="27.511999"
- y="8.75"
- id="text86"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
- <text
- x="25.799999"
- y="9.75"
- id="text88"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam_compat</text>
- <line
- x1="25.25"
- y1="6"
- x2="33.25"
- y2="6"
- stroke="#000000"
- stroke-width="0.050"
- id="line90"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="25.25"
- y1="7"
- x2="33.25"
- y2="7"
- stroke="#000000"
- stroke-width="0.050"
- id="line92"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="25.25"
- y1="8"
- x2="33.25"
- y2="8"
- stroke="#000000"
- stroke-width="0.050"
- id="line94"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="25.25"
- y1="9"
- x2="33.25"
- y2="9"
- stroke="#000000"
- stroke-width="0.050"
- id="line96"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="10.244"
- y="12.4"
- id="rect98"
- style="fill:#d7d7d7;stroke:none;stroke-width:0" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="10.244"
- y="12.4"
- id="rect100"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="10.794"
- y="13.628"
- id="text102"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
- <rect
- width="7.5"
- height="2.75"
- x="0.5"
- y="12"
- id="rect104"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="7.5"
- height="2.75"
- x="0.5"
- y="12"
- id="rect106"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="0.066"
- y="13"
- id="text108"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
- <text
- x="2.513"
- y="14.25"
- id="text110"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
- <line
- x1="8"
- y1="13.375"
- x2="0.5"
- y2="13.375"
- stroke="#000000"
- stroke-width="0.050"
- id="line112"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="8.25"
- y1="12"
- x2="10.25"
- y2="12.75"
- stroke="#000000"
- stroke-width="0.050"
- id="line114"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="8.25"
- y1="14.75"
- x2="10.25"
- y2="14"
- stroke="#000000"
- stroke-width="0.050"
- id="line116"
- style="stroke:#000000;stroke-width:0.05" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="12.489,14.500 12.489,15.500 20.489,15.500 20.489,8.750 "
- id="polyline118"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="26.294001cm"
- height="2.4000001cm"
- viewBox="0.45 1.35 26.744 3.75"
- id="svg2">
- <defs
- id="defs41" />
- <path
- d="M 13.02,1.721 L 15.23,1.721 C 15.535,1.721 15.782,2.126 15.782,2.625 C 15.782,3.124 15.535,3.529 15.23,3.529 L 13.02,3.529 C 12.715,3.529 12.468,3.124 12.468,2.625 C 12.468,2.126 12.715,1.721 13.02,1.721"
- id="path4"
- style="fill:#d7d7d7;stroke:none;stroke-width:0.1" />
- <path
- d="M 13.02,1.721 L 15.23,1.721 C 15.535,1.721 15.782,2.126 15.782,2.625 C 15.782,3.124 15.535,3.529 15.23,3.529 L 13.02,3.529 C 12.715,3.529 12.468,3.124 12.468,2.625 C 12.468,2.126 12.715,1.721 13.02,1.721"
- id="path6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="13.424"
- y="2.803"
- id="text8"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
- <path
- d="M 1.083,1.65 L 3.417,1.65 C 3.739,1.65 4,2.055 4,2.554 C 4,3.053 3.739,3.457 3.417,3.457 L 1.083,3.457 C 0.761,3.457 0.5,3.053 0.5,2.554 C 0.5,2.055 0.761,1.65 1.083,1.65"
- id="path10"
- style="fill:#d7d7d7;stroke:none;stroke-width:0.1" />
- <path
- d="M 1.083,1.65 L 3.417,1.65 C 3.739,1.65 4,2.055 4,2.554 C 4,3.053 3.739,3.457 3.417,3.457 L 1.083,3.457 C 0.761,3.457 0.5,3.053 0.5,2.554 C 0.5,2.055 0.761,1.65 1.083,1.65"
- id="path12"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="1.511"
- y="2.7309999"
- id="text14"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">GID</text>
- <line
- x1="16"
- y1="3"
- x2="18"
- y2="3.5"
- stroke="#000000"
- stroke-width="0.050"
- id="line16"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="16"
- y1="2"
- x2="18"
- y2="1.5"
- stroke="#000000"
- stroke-width="0.050"
- id="line18"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="4"
- y1="2.5539999"
- x2="11.65"
- y2="2.618"
- stroke="#000000"
- stroke-width="0.100"
- id="line20"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="11.647,3.018 12.45,2.625 11.653,2.218 11.647,3.018 "
- id="polygon22"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <rect
- width="6.9219999"
- height="2.0999999"
- x="4.572"
- y="1.4"
- id="rect24"
- style="fill:#d7d7d7;stroke:none;stroke-width:0" />
- <rect
- width="6.9219999"
- height="2.0999999"
- x="4.572"
- y="1.4"
- id="rect26"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="5.1220002"
- y="2.6270001"
- id="text28"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">net groupmap</text>
- <rect
- width="8.1999998"
- height="2.2"
- x="18.25"
- y="1.5"
- id="rect30"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="8.1999998"
- height="2.2"
- x="18.25"
- y="1.5"
- id="rect32"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="20.511999"
- y="2.25"
- id="text34"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
- <text
- x="17.955999"
- y="3.2"
- id="text36"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">groupmap_idmap.tdb</text>
- <line
- x1="26.549999"
- y1="2.45"
- x2="18.35"
- y2="2.45"
- stroke="#000000"
- stroke-width="0.050"
- id="line38"
- style="stroke:#000000;stroke-width:0.05" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="21.431cm"
- height="23.086cm"
- viewBox="10.369 0.921 31.8 24.007"
- id="svg2">
- <defs
- id="defs121" />
- <line
- x1="19.25"
- y1="12.75"
- x2="19.25"
- y2="14.15"
- stroke="#000000"
- stroke-width="0.100"
- id="line4"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="18.85,14.15 19.25,14.95 19.65,14.15 18.85,14.15 "
- id="polygon6"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="12.5"
- y1="2.779"
- x2="12.5"
- y2="4.6500001"
- stroke="#000000"
- stroke-width="0.100"
- id="line8"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.1,4.65 12.5,5.45 12.9,4.65 12.1,4.65 "
- id="polygon10"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
- id="path12"
- style="fill:#dcdcdc;stroke:none;stroke-width:0.1" />
- <path
- d="M 11.333,0.971 L 13.667,0.971 C 13.989,0.971 14.25,1.376 14.25,1.875 C 14.25,2.374 13.989,2.779 13.667,2.779 L 11.333,2.779 C 11.011,2.779 10.75,2.374 10.75,1.875 C 10.75,1.376 11.011,0.971 11.333,0.971"
- id="path14"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="11.765"
- y="2.053"
- id="text16"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">UID</text>
- <line
- x1="12.489"
- y1="7.5"
- x2="12.497"
- y2="9.6499996"
- stroke="#000000"
- stroke-width="0.100"
- id="line18"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="12.097,9.651 12.5,10.45 12.897,9.649 12.097,9.651 "
- id="polygon20"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 14.833,22.15 L 17.167,22.15 C 17.489,22.15 17.75,22.555 17.75,23.054 C 17.75,23.553 17.489,23.957 17.167,23.957 L 14.833,23.957 C 14.511,23.957 14.25,23.553 14.25,23.054 C 14.25,22.555 14.511,22.15 14.833,22.15"
- id="path22"
- style="fill:#d5d5d5;stroke:none;stroke-width:0.1" />
- <path
- d="M 14.833,22.15 L 17.167,22.15 C 17.489,22.15 17.75,22.555 17.75,23.054 C 17.75,23.553 17.489,23.957 17.167,23.957 L 14.833,23.957 C 14.511,23.957 14.25,23.553 14.25,23.054 C 14.25,22.555 14.511,22.15 14.833,22.15"
- id="path24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="15.299"
- y="23.231001"
- id="text26"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">SID</text>
- <polygon
- points="12.5,10.5 14.5,12 12.5,13.5 10.5,12 12.5,10.5 "
- id="polygon28"
- style="fill:#b8f5fc;stroke:none;stroke-width:0.1" />
- <polygon
- points="12.5,10.5 14.5,12 12.5,13.5 10.5,12 12.5,10.5 "
- id="polygon30"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="11.023"
- y="12.25"
- id="text32"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
- <text
- x="13.031"
- y="14.5"
- id="text34"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <text
- x="14.854"
- y="11.75"
- id="text36"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="14.5"
- y1="12"
- x2="16.4"
- y2="12"
- stroke="#000000"
- stroke-width="0.100"
- id="line38"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="16.4,12.4 17.2,12 16.4,11.6 16.4,12.4 "
- id="polygon40"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <line
- x1="16"
- y1="19.25"
- x2="16"
- y2="21.4"
- stroke="#000000"
- stroke-width="0.100"
- id="line42"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="15.6,21.4 16,22.2 16.4,21.4 15.6,21.4 "
- id="polygon44"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
- <path
- d="M 24.083,15.65 L 26.417,15.65 C 26.739,15.65 27,16.055 27,16.554 C 27,17.053 26.739,17.457 26.417,17.457 L 24.083,17.457 C 23.761,17.457 23.5,17.053 23.5,16.554 C 23.5,16.055 23.761,15.65 24.083,15.65"
- id="path46"
- style="fill:#d9d9d9;stroke:none;stroke-width:0.1" />
- <path
- d="M 24.083,15.65 L 26.417,15.65 C 26.739,15.65 27,16.055 27,16.554 C 27,17.053 26.739,17.457 26.417,17.457 L 24.083,17.457 C 23.761,17.457 23.5,17.053 23.5,16.554 C 23.5,16.055 23.761,15.65 24.083,15.65"
- id="path48"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="24.525999"
- y="16.731001"
- id="text50"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Fail</text>
- <rect
- width="4.1399999"
- height="2.0999999"
- x="10.419"
- y="5.4000001"
- id="rect52"
- style="fill:#dcd7d7;stroke:none;stroke-width:0" />
- <rect
- width="4.1399999"
- height="2.0999999"
- x="10.419"
- y="5.4000001"
- id="rect54"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="10.969"
- y="6.6279998"
- id="text56"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">PassDB</text>
- <line
- x1="14.75"
- y1="5.25"
- x2="17"
- y2="4"
- stroke="#000000"
- stroke-width="0.050"
- id="line58"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="14.75"
- y1="7.5"
- x2="17"
- y2="8.75"
- stroke="#000000"
- stroke-width="0.050"
- id="line60"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="8"
- height="5.25"
- x="17.25"
- y="3.75"
- id="rect62"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="8"
- height="5.25"
- x="17.25"
- y="3.75"
- id="rect64"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="20.089001"
- y="4.5"
- id="text66"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">guest</text>
- <text
- x="18.85"
- y="5.5"
- id="text68"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">smbpasswd</text>
- <text
- x="19.709"
- y="6.5"
- id="text70"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">tdbsam</text>
- <text
- x="19.511999"
- y="7.5"
- id="text72"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
- <text
- x="17.799999"
- y="8.5"
- id="text74"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam_compat</text>
- <line
- x1="17.25"
- y1="4.75"
- x2="25.25"
- y2="4.75"
- stroke="#000000"
- stroke-width="0.050"
- id="line76"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="17.25"
- y1="5.75"
- x2="25.25"
- y2="5.75"
- stroke="#000000"
- stroke-width="0.050"
- id="line78"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="17.25"
- y1="6.75"
- x2="25.25"
- y2="6.75"
- stroke="#000000"
- stroke-width="0.050"
- id="line80"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="17.25"
- y1="7.75"
- x2="25.25"
- y2="7.75"
- stroke="#000000"
- stroke-width="0.050"
- id="line82"
- style="stroke:#000000;stroke-width:0.05" />
- <polyline
- fill="none"
- stroke="#000000"
- stroke-width="0.100"
- points="12.500,13.500 12.500,19.000 19.250,19.000 19.250,18.000 "
- id="polyline84"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="16.993999"
- y="10.9"
- id="rect86"
- style="fill:#d7d7d7;stroke:none;stroke-width:0" />
- <rect
- width="4.4899998"
- height="2.0999999"
- x="16.993999"
- y="10.9"
- id="rect88"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="17.544001"
- y="12.128"
- id="text90"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Winbind</text>
- <line
- x1="21.5"
- y1="12.5"
- x2="23.5"
- y2="13.25"
- stroke="#000000"
- stroke-width="0.050"
- id="line92"
- style="stroke:#000000;stroke-width:0.05" />
- <line
- x1="21.5"
- y1="11.25"
- x2="23.5"
- y2="10.5"
- stroke="#000000"
- stroke-width="0.050"
- id="line94"
- style="stroke:#000000;stroke-width:0.05" />
- <rect
- width="7.6669998"
- height="2.75"
- x="23.75"
- y="10.5"
- id="rect96"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="7.6669998"
- height="2.75"
- x="23.75"
- y="10.5"
- id="rect98"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="23.433001"
- y="11.507"
- id="text100"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">winbindd_idmap.tdb</text>
- <text
- x="25.761999"
- y="12.75"
- id="text102"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">ldapsam</text>
- <line
- x1="31.417"
- y1="11.875"
- x2="23.75"
- y2="11.875"
- stroke="#000000"
- stroke-width="0.050"
- id="line104"
- style="stroke:#000000;stroke-width:0.05" />
- <polygon
- points="19.25,15 21.25,16.5 19.25,18 17.25,16.5 19.25,15 "
- id="polygon106"
- style="fill:#bcf9ff;stroke:none;stroke-width:0.1" />
- <polygon
- points="19.25,15 21.25,16.5 19.25,18 17.25,16.5 19.25,15 "
- id="polygon108"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="17.773001"
- y="16.75"
- id="text110"
- style="font-size:1px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:luxi sans">Found?</text>
- <text
- x="19.781"
- y="19"
- id="text112"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">Yes</text>
- <text
- x="21.604"
- y="16.25"
- id="text114"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:luxi sans">No</text>
- <line
- x1="21.25"
- y1="16.5"
- x2="22.65"
- y2="16.5"
- stroke="#000000"
- stroke-width="0.100"
- id="line116"
- style="stroke:#000000;stroke-width:0.1" />
- <polygon
- points="22.65,16.9 23.45,16.5 22.65,16.1 22.65,16.9 "
- id="polygon118"
- style="fill:#000000;stroke:none;stroke-width:0.1" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="8.1999998cm"
- height="17.198cm"
- viewBox="1.45 1.4 9.65 18.598"
- id="svg2">
- <defs
- id="defs45" />
- <rect
- width="7.3000002"
- height="2.5999999"
- x="1.5"
- y="1.7"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="7.3000002"
- height="2.5999999"
- x="1.5"
- y="1.7"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="5.9000001"
- height="2.7"
- x="2.3"
- y="8.5"
- id="rect8"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="5.9000001"
- height="2.7"
- x="2.3"
- y="8.5"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="2.7"
- y="2.8"
- id="text12"
- style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">passdb backend</text>
- <text
- x="1.7"
- y="3.7"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">contains samba users</text>
- <text
- x="4.5"
- y="9.3999996"
- id="text16"
- style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">idmap</text>
- <text
- x="3.3"
- y="10.2"
- id="text18"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">maps unix to</text>
- <text
- x="3.3"
- y="11"
- id="text20"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">samba users</text>
- <rect
- width="7.6999998"
- height="3"
- x="1.9"
- y="15.5"
- id="rect22"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="7.6999998"
- height="3"
- x="1.9"
- y="15.5"
- id="rect24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.675,7.35 4.675,5.45 4.2,5.45 5.15,4.5 6.1,5.45 5.625,5.45 5.625,7.35 6.1,7.35 5.15,8.3 4.2,7.35 4.675,7.35 "
- id="polygon26"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.675,7.35 4.675,5.45 4.2,5.45 5.15,4.5 6.1,5.45 5.625,5.45 5.625,7.35 6.1,7.35 5.15,8.3 4.2,7.35 4.675,7.35 "
- id="polygon28"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.675,7.35 4.675,5.45 4.2,5.45 5.15,4.5 6.1,5.45 5.625,5.45 5.625,7.35 6.1,7.35 5.15,8.3 4.2,7.35 4.675,7.35 "
- id="polygon30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="4.763,14.175 4.763,12.325 4.3,12.325 5.225,11.4 6.15,12.325 5.688,12.325 5.688,14.175 6.15,14.175 5.225,15.1 4.3,14.175 4.763,14.175 "
- id="polygon32"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="4.763,14.175 4.763,12.325 4.3,12.325 5.225,11.4 6.15,12.325 5.688,12.325 5.688,14.175 6.15,14.175 5.225,15.1 4.3,14.175 4.763,14.175 "
- id="polygon34"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="4.763,14.175 4.763,12.325 4.3,12.325 5.225,11.4 6.15,12.325 5.688,12.325 5.688,14.175 6.15,14.175 5.225,15.1 4.3,14.175 4.763,14.175 "
- id="polygon36"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="3.7"
- y="16.299999"
- id="text38"
- style="font-size:0.80000001px;font-style:normal;font-weight:700;text-anchor:start;fill:#000000;font-family:sans">Unix users</text>
- <text
- x="2.4000001"
- y="17.4"
- id="text40"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">/etc/passwd</text>
- <text
- x="2.4000001"
- y="18.200001"
- id="text42"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">or other NSS backend</text>
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="18.5cm"
- height="4.9990001cm"
- viewBox="5.85 2.808 24.35 7.807"
- id="svg2">
- <defs
- id="defs59" />
- <rect
- width="4.0999999"
- height="1"
- x="5.9000001"
- y="3"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.0999999"
- height="1"
- x="5.9000001"
- y="3"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.8039999"
- y="3.8"
- id="text8"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pdftops</text>
- <rect
- width="4.0999999"
- height="1"
- x="12.8"
- y="3"
- id="rect10"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.0999999"
- height="1"
- x="12.8"
- y="3"
- id="rect12"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="13.835"
- y="3.8"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
- <rect
- width="4.0999999"
- height="1"
- x="19.9"
- y="3"
- id="rect16"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.7609506"
- height="0.99263805"
- x="19.903681"
- y="3.0036809"
- id="rect18"
- style="fill:none;stroke:#000000;stroke-width:0.10736195" />
- <text
- x="20.409"
- y="3.8"
- id="text20"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstoraster</text>
- <polygon
- points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
- id="polygon22"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
- id="polygon24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
- id="polygon26"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
- id="polygon28"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
- id="polygon30"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
- id="polygon32"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="4.8000002"
- height="1"
- x="19.5"
- y="6.3000002"
- id="rect34"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="6.0224352"
- height="0.9886266"
- x="19.505686"
- y="6.305687"
- id="rect36"
- style="fill:none;stroke:#000000;stroke-width:0.11137342" />
- <text
- x="19.865999"
- y="7.0999999"
- id="text38"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">rastertoepson</text>
- <polygon
- points="21.6,4.4 21.6,5.2 21.2,5.2 22,6 22.8,5.2 22.4,5.2 22.4,4.4 21.6,4.4 "
- id="polygon40"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="21.6,4.4 21.6,5.2 21.2,5.2 22,6 22.8,5.2 22.4,5.2 22.4,4.4 21.6,4.4 "
- id="polygon42"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="21.6,4.4 21.6,5.2 21.2,5.2 22,6 22.8,5.2 22.4,5.2 22.4,4.4 21.6,4.4 "
- id="polygon44"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="4.0999999"
- height="1"
- x="12.5"
- y="6.3000002"
- id="rect46"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.0999999"
- height="1"
- x="12.5"
- y="6.3000002"
- id="rect48"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="13.979"
- y="7.0999999"
- id="text50"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">usb</text>
- <polygon
- points="18.886,6.422 18.043,6.422 18.043,6 17.2,6.843 18.043,7.686 18.043,7.265 18.886,7.265 18.886,6.422 "
- id="polygon52"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="18.886,6.422 18.043,6.422 18.043,6 17.2,6.843 18.043,7.686 18.043,7.265 18.886,7.265 18.886,6.422 "
- id="polygon54"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="18.886,6.422 18.043,6.422 18.043,6 17.2,6.843 18.043,7.686 18.043,7.265 18.886,7.265 18.886,6.422 "
- id="polygon56"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="18.200001cm"
- height="1.484cm"
- viewBox="5.85 2.808 24.05 4.292"
- id="svg2">
- <defs
- id="defs35" />
- <rect
- width="4.0999999"
- height="1"
- x="5.9000001"
- y="3"
- id="rect4"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.0999999"
- height="1"
- x="5.9000001"
- y="3"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="6.8039999"
- y="3.8"
- id="text8"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pdftops</text>
- <rect
- width="4.0999999"
- height="1"
- x="12.8"
- y="3"
- id="rect10"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.0999999"
- height="1"
- x="12.8"
- y="3"
- id="rect12"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="13.835"
- y="3.8"
- id="text14"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">pstops</text>
- <rect
- width="4.0999999"
- height="1"
- x="19.9"
- y="3"
- id="rect16"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="4.0999999"
- height="1"
- x="19.9"
- y="3"
- id="rect18"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <text
- x="20.959"
- y="3.8"
- id="text20"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">socket</text>
- <polygon
- points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
- id="polygon22"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
- id="polygon24"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="10.5,3.225 11.5,3.225 11.5,2.9 12.5,3.55 11.5,4.2 11.5,3.875 10.5,3.875 10.5,3.225 "
- id="polygon26"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
- id="polygon28"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
- id="polygon30"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="17.4,3.225 18.4,3.225 18.4,2.9 19.4,3.55 18.4,4.2 18.4,3.875 17.4,3.875 17.4,3.225 "
- id="polygon32"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns="http://www.w3.org/2000/svg"
- version="1.0"
- width="27.1cm"
- height="8.493cm"
- viewBox="6.95 1.958 34.05 10.45"
- id="svg2">
- <defs
- id="defs273" />
- <rect
- width="1.367"
- height="3.1900001"
- x="8.8730001"
- y="5"
- id="rect4"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.367"
- height="3.1900001"
- x="8.8730001"
- y="5"
- id="rect6"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.094"
- height="0.36500001"
- x="9.0100002"
- y="5.191"
- id="rect8"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.094"
- height="0.36500001"
- x="9.0100002"
- y="5.5560002"
- id="rect10"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.094"
- height="0.36500001"
- x="9.0100002"
- y="5.921"
- id="rect12"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.094"
- height="0.36500001"
- x="9.0100002"
- y="6.2849998"
- id="rect14"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.68400002"
- height="0.219"
- x="9.0100002"
- y="6.723"
- id="rect16"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="10.036"
- cy="6.7589998"
- rx="0.048"
- ry="0.048"
- id="ellipse18"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="10.036"
- cy="6.7589998"
- rx="0.048"
- ry="0.048"
- id="ellipse20"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="10.036"
- cy="6.9050002"
- rx="0.048"
- ry="0.048"
- id="ellipse22"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="10.036"
- cy="6.9050002"
- rx="0.048"
- ry="0.048"
- id="ellipse24"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.164"
- height="0.146"
- x="9.7620001"
- y="6.796"
- id="rect26"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.164"
- height="0.146"
- x="9.7620001"
- y="6.796"
- id="rect28"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.101,7.233 L 9.101,8.031"
- id="path30"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.329,7.233 L 9.329,8.031"
- id="path32"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.557,7.233 L 9.557,8.031"
- id="path34"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 9.785,7.233 L 9.785,8.031"
- id="path36"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.013,7.233 L 10.013,8.031"
- id="path38"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 10.241,7.233 L 10.241,8.031"
- id="path40"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="8.6,8.464 8.873,7.917 8.873,8.19 10.241,8.19 10.241,7.917 10.605,8.464 8.6,8.464 "
- id="polygon42"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="8.6,8.464 8.873,7.917 8.873,8.19 10.241,8.19 10.241,7.917 10.605,8.464 8.6,8.464 "
- id="polygon44"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="12.25"
- cy="6.6999998"
- rx="5.25"
- ry="3.5999999"
- id="ellipse46"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.365"
- height="3.1860001"
- x="11.273"
- y="5"
- id="rect48"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.365"
- height="3.1860001"
- x="11.273"
- y="5"
- id="rect50"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.092"
- height="0.36399999"
- x="11.41"
- y="5.191"
- id="rect52"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.092"
- height="0.36399999"
- x="11.41"
- y="5.5549998"
- id="rect54"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.092"
- height="0.36399999"
- x="11.41"
- y="5.9190001"
- id="rect56"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.092"
- height="0.36399999"
- x="11.41"
- y="6.2839999"
- id="rect58"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.68300003"
- height="0.21799999"
- x="11.41"
- y="6.7199998"
- id="rect60"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="12.434"
- cy="6.757"
- rx="0.048"
- ry="0.048"
- id="ellipse62"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="12.434"
- cy="6.757"
- rx="0.048"
- ry="0.048"
- id="ellipse64"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="12.434"
- cy="6.902"
- rx="0.048"
- ry="0.048"
- id="ellipse66"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="12.434"
- cy="6.902"
- rx="0.048"
- ry="0.048"
- id="ellipse68"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.164"
- height="0.146"
- x="12.161"
- y="6.7930002"
- id="rect70"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.164"
- height="0.146"
- x="12.161"
- y="6.7930002"
- id="rect72"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 11.501,7.23 L 11.501,8.027"
- id="path74"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 11.728,7.23 L 11.728,8.027"
- id="path76"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 11.956,7.23 L 11.956,8.027"
- id="path78"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 12.183,7.23 L 12.183,8.027"
- id="path80"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 12.411,7.23 L 12.411,8.027"
- id="path82"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 12.639,7.23 L 12.639,8.027"
- id="path84"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="11,8.459 11.273,7.913 11.273,8.186 12.639,8.186 12.639,7.913 13.003,8.459 11,8.459 "
- id="polygon86"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="11,8.459 11.273,7.913 11.273,8.186 12.639,8.186 12.639,7.913 13.003,8.459 11,8.459 "
- id="polygon88"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.322"
- height="3.086"
- x="13.764"
- y="5.0999999"
- id="rect90"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.322"
- height="3.086"
- x="13.764"
- y="5.0999999"
- id="rect92"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.058"
- height="0.35299999"
- x="13.897"
- y="5.2849998"
- id="rect94"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.058"
- height="0.35299999"
- x="13.897"
- y="5.638"
- id="rect96"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.058"
- height="0.35299999"
- x="13.897"
- y="5.9899998"
- id="rect98"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.058"
- height="0.35299999"
- x="13.897"
- y="6.3429999"
- id="rect100"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66100001"
- height="0.212"
- x="13.897"
- y="6.7659998"
- id="rect102"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="14.888"
- cy="6.8010001"
- rx="0.046"
- ry="0.046"
- id="ellipse104"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="14.888"
- cy="6.8010001"
- rx="0.046"
- ry="0.046"
- id="ellipse106"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="14.888"
- cy="6.9419999"
- rx="0.046"
- ry="0.046"
- id="ellipse108"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="14.888"
- cy="6.9419999"
- rx="0.046"
- ry="0.046"
- id="ellipse110"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.15899999"
- height="0.141"
- x="14.624"
- y="6.8369999"
- id="rect112"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.15899999"
- height="0.141"
- x="14.624"
- y="6.8369999"
- id="rect114"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 13.985,7.26 L 13.985,8.031"
- id="path116"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.205,7.26 L 14.205,8.031"
- id="path118"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.426,7.26 L 14.426,8.031"
- id="path120"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.646,7.26 L 14.646,8.031"
- id="path122"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 14.866,7.26 L 14.866,8.031"
- id="path124"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 15.087,7.26 L 15.087,8.031"
- id="path126"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="13.5,8.45 13.764,7.921 13.764,8.186 15.087,8.186 15.087,7.921 15.439,8.45 13.5,8.45 "
- id="polygon128"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="13.5,8.45 13.764,7.921 13.764,8.186 15.087,8.186 15.087,7.921 15.439,8.45 13.5,8.45 "
- id="polygon130"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="10.5"
- y="2.5"
- id="text132"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Domain A</text>
- <text
- x="27.299999"
- y="2.8"
- id="text134"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Domain B</text>
- <polygon
- points="18.5,6.5 20.6,6.5 20.6,6.2 22.7,6.8 20.6,7.4 20.6,7.1 18.5,7.1 18.5,6.5 "
- id="polygon136"
- style="fill:#ffffff;stroke:none;stroke-width:0.1" />
- <polygon
- points="18.5,6.5 20.6,6.5 20.6,6.2 22.7,6.8 20.6,7.4 20.6,7.1 18.5,7.1 18.5,6.5 "
- id="polygon138"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <polygon
- points="18.5,6.5 20.6,6.5 20.6,6.2 22.7,6.8 20.6,7.4 20.6,7.1 18.5,7.1 18.5,6.5 "
- id="polygon140"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <text
- x="19.299999"
- y="5.9000001"
- id="text142"
- style="font-size:0.80000001px;font-style:normal;font-weight:400;text-anchor:start;fill:#000000;font-family:sans">Trusts</text>
- <rect
- width="1.367"
- height="3.1900001"
- x="25.372999"
- y="5.0999999"
- id="rect144"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.367"
- height="3.1900001"
- x="25.372999"
- y="5.0999999"
- id="rect146"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.094"
- height="0.36500001"
- x="25.51"
- y="5.2909999"
- id="rect148"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.094"
- height="0.36500001"
- x="25.51"
- y="5.6560001"
- id="rect150"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.094"
- height="0.36500001"
- x="25.51"
- y="6.0209999"
- id="rect152"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.094"
- height="0.36500001"
- x="25.51"
- y="6.3850002"
- id="rect154"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.68400002"
- height="0.219"
- x="25.51"
- y="6.823"
- id="rect156"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="26.535999"
- cy="6.8590002"
- rx="0.048"
- ry="0.048"
- id="ellipse158"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="26.535999"
- cy="6.8590002"
- rx="0.048"
- ry="0.048"
- id="ellipse160"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="26.535999"
- cy="7.0050001"
- rx="0.048"
- ry="0.048"
- id="ellipse162"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="26.535999"
- cy="7.0050001"
- rx="0.048"
- ry="0.048"
- id="ellipse164"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.164"
- height="0.146"
- x="26.261999"
- y="6.8959999"
- id="rect166"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.164"
- height="0.146"
- x="26.261999"
- y="6.8959999"
- id="rect168"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 25.601,7.333 L 25.601,8.131"
- id="path170"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 25.829,7.333 L 25.829,8.131"
- id="path172"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 26.057,7.333 L 26.057,8.131"
- id="path174"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 26.285,7.333 L 26.285,8.131"
- id="path176"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 26.513,7.333 L 26.513,8.131"
- id="path178"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 26.741,7.333 L 26.741,8.131"
- id="path180"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="25.1,8.564 25.373,8.017 25.373,8.29 26.741,8.29 26.741,8.017 27.105,8.564 25.1,8.564 "
- id="polygon182"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="25.1,8.564 25.373,8.017 25.373,8.29 26.741,8.29 26.741,8.017 27.105,8.564 25.1,8.564 "
- id="polygon184"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="28.75"
- cy="6.8000002"
- rx="5.25"
- ry="3.5999999"
- id="ellipse186"
- style="fill:none;stroke:#000000;stroke-width:0.1" />
- <rect
- width="1.365"
- height="3.1860001"
- x="27.773001"
- y="5.0999999"
- id="rect188"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.365"
- height="3.1860001"
- x="27.773001"
- y="5.0999999"
- id="rect190"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.092"
- height="0.36399999"
- x="27.91"
- y="5.2909999"
- id="rect192"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.092"
- height="0.36399999"
- x="27.91"
- y="5.6550002"
- id="rect194"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.092"
- height="0.36399999"
- x="27.91"
- y="6.0190001"
- id="rect196"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.092"
- height="0.36399999"
- x="27.91"
- y="6.3839998"
- id="rect198"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.68300003"
- height="0.21799999"
- x="27.91"
- y="6.8200002"
- id="rect200"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="28.934"
- cy="6.8569999"
- rx="0.048"
- ry="0.048"
- id="ellipse202"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="28.934"
- cy="6.8569999"
- rx="0.048"
- ry="0.048"
- id="ellipse204"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="28.934"
- cy="7.0019999"
- rx="0.048"
- ry="0.048"
- id="ellipse206"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="28.934"
- cy="7.0019999"
- rx="0.048"
- ry="0.048"
- id="ellipse208"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.164"
- height="0.146"
- x="28.660999"
- y="6.8930001"
- id="rect210"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.164"
- height="0.146"
- x="28.660999"
- y="6.8930001"
- id="rect212"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 28.001,7.33 L 28.001,8.127"
- id="path214"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 28.228,7.33 L 28.228,8.127"
- id="path216"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 28.456,7.33 L 28.456,8.127"
- id="path218"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 28.683,7.33 L 28.683,8.127"
- id="path220"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 28.911,7.33 L 28.911,8.127"
- id="path222"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 29.139,7.33 L 29.139,8.127"
- id="path224"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="27.5,8.559 27.773,8.013 27.773,8.286 29.139,8.286 29.139,8.013 29.503,8.559 27.5,8.559 "
- id="polygon226"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="27.5,8.559 27.773,8.013 27.773,8.286 29.139,8.286 29.139,8.013 29.503,8.559 27.5,8.559 "
- id="polygon228"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.322"
- height="3.086"
- x="30.264"
- y="5.1999998"
- id="rect230"
- style="fill:#b3b3b3;stroke:none;stroke-width:0" />
- <rect
- width="1.322"
- height="3.086"
- x="30.264"
- y="5.1999998"
- id="rect232"
- style="fill:none;stroke:#000000;stroke-width:0.08" />
- <rect
- width="1.058"
- height="0.35299999"
- x="30.396999"
- y="5.3850002"
- id="rect234"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.058"
- height="0.35299999"
- x="30.396999"
- y="5.7379999"
- id="rect236"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.058"
- height="0.35299999"
- x="30.396999"
- y="6.0900002"
- id="rect238"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="1.058"
- height="0.35299999"
- x="30.396999"
- y="6.4429998"
- id="rect240"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.66100001"
- height="0.212"
- x="30.396999"
- y="6.8660002"
- id="rect242"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="31.388"
- cy="6.901"
- rx="0.046"
- ry="0.046"
- id="ellipse244"
- style="fill:#00ff00;stroke:none" />
- <ellipse
- cx="31.388"
- cy="6.901"
- rx="0.046"
- ry="0.046"
- id="ellipse246"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <ellipse
- cx="31.388"
- cy="7.0430002"
- rx="0.046"
- ry="0.046"
- id="ellipse248"
- style="fill:#ffff00;stroke:none" />
- <ellipse
- cx="31.388"
- cy="7.0430002"
- rx="0.046"
- ry="0.046"
- id="ellipse250"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <rect
- width="0.15899999"
- height="0.141"
- x="31.124001"
- y="6.9369998"
- id="rect252"
- style="fill:#ffffff;stroke:none;stroke-width:0" />
- <rect
- width="0.15899999"
- height="0.141"
- x="31.124001"
- y="6.9369998"
- id="rect254"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 30.485,7.36 L 30.485,8.131"
- id="path256"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 30.705,7.36 L 30.705,8.131"
- id="path258"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 30.926,7.36 L 30.926,8.131"
- id="path260"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 31.146,7.36 L 31.146,8.131"
- id="path262"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 31.366,7.36 L 31.366,8.131"
- id="path264"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <path
- d="M 31.587,7.36 L 31.587,8.131"
- id="path266"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
- <polygon
- points="30,8.55 30.264,8.021 30.264,8.286 31.587,8.286 31.587,8.021 31.939,8.55 30,8.55 "
- id="polygon268"
- style="fill:#999999;stroke:none;stroke-width:0.01" />
- <polygon
- points="30,8.55 30.264,8.021 30.264,8.286 31.587,8.286 31.587,8.021 31.939,8.55 30,8.55 "
- id="polygon270"
- style="fill:none;stroke:#000000;stroke-width:0.01" />
-</svg>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-
-<book id="Samba-HOWTO-Collection"
- xmlns:xi="http://www.w3.org/2003/XInclude">
-<title>The Official Samba 3.5.x HOWTO and Reference Guide</title>
-
-<bookinfo>
- <authorgroup>
- <editor>&person.jelmer;</editor>
- <editor>&person.jht;</editor>
- <editor>&person.jerry;</editor>
- </authorgroup>
- <pubdate><?latex \today ?></pubdate>
-</bookinfo>
-
- <?latex \setcounter{page}{5} ?>
-
- <xi:include href="TOSHARG-inside-cover.xml"/>
-
- <?latex \cleardoublepage ?>
-
- <xi:include href="../Samba3-HOWTO-attributions.xml">
- <xi:fallback/>
- </xi:include>
-
- <?latex \cleardoublepage ?>
-
-<!-- Contents -->
- <toc/>
-
- <?latex \cleardoublepage ?>
-
- <?latex \listofexamples ?>
-
- <?latex \cleardoublepage ?>
-
- <lot/>
-
- <xi:include href="TOSHARG-foreword-cargill.xml"/>
-
- <?latex \cleardoublepage ?>
-
- <xi:include href="TOSHARG-preface.xml"/>
-
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-IntroSMB.xml"/>
-
- <?latex \cleardoublepage ?>
-
-<!-- Chapters -->
-<part id="introduction">
-<title>General Installation</title>
-<?latex \pagenumbering{arabic} ?>
-
-<partintro>
-<title>Preparing Samba for Configuration</title>
-
-<para>
-This section of the Samba-HOWTO-Collection contains general info on how to install Samba
-and how to configure the parts of Samba you will most likely need.
-PLEASE read this.
-</para>
-
-</partintro>
-
- <?latex \cleardoublepage ?>
-
- <xi:include href="TOSHARG-Install.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-FastStart.xml"/>
- <?latex \cleardoublepage ?>
-
-</part>
-
-<part id="type">
-<title>Server Configuration Basics</title>
-<partintro>
-<title>First Steps in Server Configuration</title>
-
-<para>
-Samba can operate in various modes within SMB networks. This HOWTO section contains information on
-configuring Samba to function as the type of server your network requires. Please read this
-section carefully.
-</para>
-
-</partintro>
-
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-ServerType.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-PDC.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-BDC.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-DomainMember.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-StandAloneServer.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-WindowsClientConfig.xml"/>
- <?latex \cleardoublepage ?>
-
-</part>
-
-<part id="optional">
-<title>Advanced Configuration</title>
-<partintro>
-<title>Valuable Nuts and Bolts Information</title>
-
-<para>
-Samba has several features that you might want or might not want to use.
-The chapters in this part each cover specific Samba features.
-</para>
-
-</partintro>
-
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-ChangeNotes.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-NetworkBrowsing.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Passdb.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Group-Mapping.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-TheNetCommand.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-IDMAP.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-RightsAndPriviliges.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-AccessControls.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-locking.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Securing.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-InterdomainTrusts.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-msdfs.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Printing.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-CUPS-printing.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-VFS.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Winbind.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-AdvancedNetworkAdmin.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-PolicyMgmt.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-ProfileMgmt.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-PAM.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Integrating-with-Windows.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Unicode.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Backup.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-LargeFile.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-ConfigSmarts.xml"/>
- <?latex \cleardoublepage ?>
-
-</part>
-
-<part id="migration">
-<title>Migration and Updating</title>
-
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-NT4Migration.xml"/>
- <?latex \cleardoublepage ?>
-
-</part>
-
-<part id="troubleshooting">
-<title>Troubleshooting</title>
-
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Diagnosis.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Problems.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Bugs.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-TDBFiles.xml"/>
- <?latex \cleardoublepage ?>
-
-</part>
-
-<part id="Appendix">
-<title>Reference Section</title>
-
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Compiling.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-SecureLDAP.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-Support.xml"/>
- <?latex \cleardoublepage ?>
- <xi:include href="TOSHARG-DNS-DHCP-Configuration.xml"/>
- <?latex \cleardoublepage ?>
-</part>
-
-<!-- Comment out the following line to include the manpages.
- *Please* do not commit with the two lines below enabled! -->
-<!--
- <?latex \cleardoublepage ?>
- <xi:include href="manpages.xml"/>
--->
- <?latex \cleardoublepage ?>
-
-<xi:include href="gpl-3.0.xml"/>
-
- <?latex \cleardoublepage ?>
-<xi:include href="TOSHARG-glossary.xml"/>
-
- <?latex \cleardoublepage ?>
-<?latex \chaptermark{Subject index} ?>
-
-<index/>
-
-</book>
+++ /dev/null
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE reference PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
-<reference xmlns:xi="http://www.w3.org/2003/XInclude">
- <title>Manual pages</title>
-
- <para>This chapter contains most of the manual pages from the official Samba distribution.
- All manual pages have been written by members of
- <ulink url="http://www.samba.org/samba/team.html">the Samba Team</ulink>.</para>
-
- <xi:include href="../manpages/eventlogadm.8.xml"/>
- <xi:include href="../manpages/findsmb.1.xml"/>
- <xi:include href="../manpages/idmap_ad.8.xml"/>
- <xi:include href="../manpages/idmap_ldap.8.xml"/>
- <xi:include href="../manpages/idmap_nss.8.xml"/>
- <xi:include href="../manpages/idmap_rid.8.xml"/>
- <xi:include href="../manpages/idmap_tdb.8.xml"/>
- <xi:include href="../manpages/libsmbclient.7.xml"/>
- <xi:include href="../manpages/lmhosts.5.xml"/>
- <xi:include href="../manpages/log2pcap.1.xml"/>
- <xi:include href="../manpages/net.8.xml"/>
- <xi:include href="../manpages/nmbd.8.xml"/>
- <xi:include href="../manpages/nmblookup.1.xml"/>
- <xi:include href="../manpages/ntlm_auth.1.xml"/>
- <xi:include href="../manpages/pam_winbind.8.xml"/>
- <xi:include href="../manpages/pdbedit.8.xml"/>
- <xi:include href="../manpages/profiles.1.xml"/>
- <xi:include href="../manpages/rpcclient.1.xml"/>
- <xi:include href="../manpages/smbcacls.1.xml"/>
- <xi:include href="../manpages/smbclient.1.xml"/>
- <xi:include href="../manpages/smb.conf.5.xml"/>
- <xi:include href="../manpages/smbcontrol.1.xml"/>
- <xi:include href="../manpages/smbcquotas.1.xml"/>
- <xi:include href="../manpages/smbd.8.xml"/>
- <xi:include href="../manpages/smbget.1.xml"/>
- <xi:include href="../manpages/smbgetrc.5.xml"/>
- <xi:include href="../manpages/smbpasswd.5.xml"/>
- <xi:include href="../manpages/smbpasswd.8.xml"/>
- <xi:include href="../manpages/smbsh.1.xml"/>
- <xi:include href="../manpages/smbstatus.1.xml"/>
- <xi:include href="../manpages/smbtar.1.xml"/>
- <xi:include href="../manpages/smbtree.1.xml"/>
- <xi:include href="../manpages/smbumount.8.xml"/>
- <xi:include href="../manpages/swat.8.xml"/>
- <xi:include href="../manpages/tdbbackup.8.xml"/>
- <xi:include href="../manpages/tdbdump.8.xml"/>
- <xi:include href="../manpages/tdbtool.8.xml"/>
- <xi:include href="../manpages/testparm.1.xml"/>
- <xi:include href="../manpages/wbinfo.1.xml"/>
- <xi:include href="../manpages/winbindd.8.xml"/>
- <xi:include href="../manpages/vfs_audit.8.xml"/>
- <xi:include href="../manpages/vfs_cacheprime.8.xml"/>
- <xi:include href="../manpages/vfs_cap.8.xml"/>
- <xi:include href="../manpages/vfs_catia.8.xml"/>
- <xi:include href="../manpages/vfs_commit.8.xml"/>
- <xi:include href="../manpages/vfs_default_quota.8.xml"/>
- <xi:include href="../manpages/vfs_extd_audit.8.xml"/>
- <xi:include href="../manpages/vfs_fake_perms.8.xml"/>
- <xi:include href="../manpages/vfs_full_audit.8.xml"/>
- <xi:include href="../manpages/vfs_gpfs.8.xml"/>
- <xi:include href="../manpages/vfs_netatalk.8.xml"/>
- <xi:include href="../manpages/vfs_prealloc.8.xml"/>
- <xi:include href="../manpages/vfs_readahead.8.xml"/>
- <xi:include href="../manpages/vfs_readonly.8.xml"/>
- <xi:include href="../manpages/vfs_recycle.8.xml"/>
- <xi:include href="../manpages/vfs_shadow_copy.8.xml"/>
- <xi:include href="../manpages/vfstest.1.xml"/>
- <xi:include href="../manpages/wbinfo.1.xml"/>
- <xi:include href="../manpages/winbindd.8.xml"/>
-
-</reference>
+++ /dev/null
-<appendix label="A" id="SAMBA-AP-A">
-<title>Configuring Samba with SSL</title>
-
-
-
-
-<para>
-<indexterm id="appa-idx-990325-0" class="startofrange"><primary>configuring Samba</primary><secondary sortas="SSL">with SSL</secondary></indexterm>
-<indexterm id="appa-idx-990325-1" class="startofrange"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>configuring Samba with</secondary></indexterm>This appendix describes how to set up Samba to use secure connections between the Samba server and its clients. The protocol used here is Netscape's Secure Sockets Layer (SSL). For this example, we will establish a secure connection between a Samba server and a Windows NT workstation.</para>
-
-
-<para>Before we begin, we will assume that you are familiar with the fundamentals of public-key cryptography and X.509 certificates. If not, we highly recommend Bruce Schneier's <filename>Applied Cryptography, 2nd Edition</filename> (Wiley) as the premiere source for learning the many secret faces of cryptography.</para>
-
-
-<tip role="ora">
-<para>If you would like more information on Samba and SSL, be sure to look at the document <filename>SSLeay.txt</filename> in the <filename>docs/textdocs</filename> directory of the Samba distribution, which is the basis for this appendix.</para>
-
-</tip>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="A.1" id="appa-SECT-1">
-<title>About Certificates</title>
-
-
-<para>Here are a few quick questions and answers from the <filename>SSLeay.txt</filename> file in the Samba documentation, regarding the benefits of SSL and certificates. This text was written by Christian Starkjohann for the Samba projects.</para>
-
-
-<sect2 role="" label="A.1.1" id="appa-SECT-1.1">
-<title>What is a Certificate?</title>
-
-
-<para>A certificate is issued by an issuer, usually a <emphasis>Certification Authority</emphasis> (CA), who confirms something by issuing the certificate. The subject of this confirmation depends on the CA's policy. CAs for secure web servers (used for shopping malls, etc.) usually attest only that the given public key belongs the given domain name. Company-wide CAs might attest that you are an employee of the company, that you have permissions to use a server, and so on.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.1.2" id="appa-SECT-1.2">
-<title>What is an X.509 certificate, technically?</title>
-
-
-<para>Technically, the certificate is a block of data signed by the certificate issuer (the CA). The relevant fields are:</para>
-
-
-<itemizedlist>
-
-<listitem><para>
-Unique identifier (name) of the certificate issuer</para></listitem>
-
-<listitem><para>Time range during which the certificate is valid</para></listitem>
-
-<listitem><para>Unique identifier (name) of the certified object</para></listitem>
-
-<listitem><para>Public key of the certified object</para></listitem>
-
-<listitem><para>The issuer's signature over all the above</para></listitem>
-
-</itemizedlist>
-
-<para>If this certificate is to be verified, the verifier must have a table of the names and public keys of trusted CAs. For simplicity, these tables should list certificates issued by the respective CAs for themselves (self-signed certificates).</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.1.3" id="appa-SECT-1.3">
-<title>What are the implications of this certificate structure?</title>
-
-
-<para>Four implications follow:</para>
-
-
-<itemizedlist>
-
-<listitem><para>Because the certificate contains the subjects's public key, the certificate and the private key together are all that is needed to encrypt and decrypt.</para></listitem>
-
-<listitem><para>To verify certificates, you need the certificates of all CAs you trust.</para></listitem>
-
-<listitem><para>The simplest form of a dummy-certificate is one that is signed by the subject.</para></listitem>
-
-<listitem><para>A CA is needed. The client can't simply issue local certificates for servers it trusts because the server determines which certificate it presents.</para></listitem>
-
-</itemizedlist>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="A.2" id="appa-SECT-2">
-<title>Requirements</title>
-
-
-<para>
-<indexterm id="appa-idx-990348-0"><primary>configuring Samba</primary><secondary sortas="SSL">with SSL</secondary><tertiary>requirements for</tertiary></indexterm>
-<indexterm id="appa-idx-990348-1"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>configuring Samba with</secondary><tertiary>requirements for</tertiary></indexterm>To set up SSL connections, you will need to download two programs in addition to Samba:</para>
-
-
-<variablelist>
-<varlistentry><term>
-<indexterm id="appa-idx-990613-0" class="startofrange"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>SSLeay</secondary></indexterm>SSLeay</term>
-<listitem><para>Eric <indexterm id="appa-idx-990362-0"><primary>Young, Eric</primary></indexterm>Young's implementation of the Secure Socket's Layer (SSL) protocol as a series of Unix programming libraries</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="appa-idx-990357-0"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>SS Proxy</secondary></indexterm>SSL Proxy</term>
-<listitem><para>A freeware SSL application from Objective Development, which can be used to proxy a secure link on Unix or Windows NT platforms</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>These two products assist with the server and client side of the encrypted SSL connection. The SSLeay libraries are compiled and installed directly on the Unix system. SSL Proxy, on the other hand, can be downloaded and compiled (or downloaded in binary format) and located on the client side. If you intend to have a Windows NT client or a Samba client on the other end of the SSL connection, you will not require a special setup.</para>
-
-
-<para>SSL Proxy, however, does not work on Windows 95/98 machines. Therefore, if you want to have a secure connection between a Samba server and Windows 95/98 client, you will need to place either a Unix server or a Windows NT machine on the same subnet with the Windows 9<emphasis>x</emphasis> clients and route all network connections through the SSL-Proxy-enabled machine. See <link linkend="appa-89929">Figure 1.1</link>.</para>
-
-
-<figure label="A.1" id="appa-89929">
-<title>Two possible ways of proxying Windows 95/98 clients</title>
-
-<graphic width="502" depth="317" fileref="figs/sam.aa01.gif"></graphic>
-</figure>
-
-<para>For the purposes of this chapter, we will create a simple SSL connection between the Samba server and a Windows NT client. This configuration can be used to set up more complex networks at the administrator's discretion.</para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="A.3" id="appa-SECT-3">
-<title>Installing SSLeay</title>
-
-
-<para>Samba uses the SSLeay package, written by Eric Young, to provide Secure Sockets Layer support on the server side. Because of U.S. export law, however, the SSLeay package cannot be shipped with Samba distributions that are based in the United States. For that reason, the Samba creators decided to leave it as a separate package entirely. You can download the SSLeay distribution from any of the following sites:</para>
-
-
-<itemizedlist>
-
-<listitem><para><systemitem role="ftpurl">ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL/</systemitem></para></listitem>
-
-<listitem><para><systemitem role="ftpurl">ftp://ftp.uni-mainz.de/pub/internet/security/ssl</systemitem></para></listitem>
-
-<listitem><para><systemitem role="ftpurl">ftp://ftp.cert.dfn.de/pub/tools/crypt/sslapps</systemitem></para></listitem>
-
-<listitem><para><systemitem role="ftpurl">ftp://ftp.funet.fi/pub/crypt/mirrors/ftp.psy.uq.oz.au</systemitem></para></listitem>
-
-<listitem><para><systemitem role="ftpurl">ftp://ftp.sunet.se/ftp/pub/security/tools/crypt/ssleay</systemitem></para></listitem>
-
-</itemizedlist>
-
-<para>The latest version as of this printing is 0.9.0b. Download it to the same server as the Samba distribution, then uncompress and untar it. You should be left with a directory entitled <filename>SSLeay-0.9.0b</filename>. After changing to that directory, you will need to configure and build the SSL encryption package in the same way that you did with Samba.</para>
-
-
-<para>SSLeay uses a Perl-based <filename>configure</filename> script. This script modifies the Makefile that constructs the utilities and libraries of the SSLeay package. However, the default script is hardcoded to find Perl at <filename>/usr/local/bin/perl</filename>. You may need to change the <filename>configure</filename> script to point to the location of the Perl executable file on your Unix system. For example, you can type the following to locate the Perl executable:</para>
-
-
-<programlisting># <userinput>which perl</userinput>
-/usr/bin/perl</programlisting>
-
-
-<para>Then modify the first line of the <filename>configure</filename> script to force it to use the correct Perl executable. For example, on our Red Hat Linux system:</para>
-
-
-<programlisting>#!/usr/bin/perl
-#
-# see PROBLEMS for instructions on what sort of things to do
-# when tracking a bug -tjh
-...</programlisting>
-
-
-<para>After that, you need to run the <filename>configure</filename> script by specifying a target platform for the distribution. This target platform can be any of the following:</para>
-
-
-<programlisting>BC-16 BC-32 FreeBSD NetBSD-m86
-NetBSD-sparc NetBSD-x86 SINIX-N VC-MSDOS
-VC-NT VC-W31-16 VC-W31-32 VC-WIN16
-VC-WIN32 aix-cc aix-gcc alpha-cc
-alpha-gcc alpha400-cc cc cray-t90-cc
-debug debug-irix-cc debug-linux-elf dgux-R3-gcc
-dgux-R4-gcc dgux-R4-x86-gcc dist gcc
-hpux-cc hpux-gcc hpux-kr-cc irix-cc
-irix-gcc linux-aout linux-elf ncr-scde
-nextstep purify sco5-cc solaris-sparc-cc
-solaris-sparc-gcc solaris-sparc-sc4 solaris-usparc-sc4 solaris-x86-gcc
-sunos-cc sunos-gcc unixware-2.0 unixware</programlisting>
-
-
-<para>For our system, we would enter the following:</para>
-
-
-<programlisting># <userinput>./Configure linux-elf</userinput>
-CC =gcc
-CFLAG =-DL_ENDIAN -DTERMIO -DBN_ASM -O3 -fomit-frame-pointer
-EX_LIBS =
-BN_MULW =asm/bn86-elf.o
-DES_ENC =asm/dx86-elf.o asm/yx86-elf.o
-BF_ENC =asm/bx86-elf.o
-CAST_ENC =asm/cx86-elf.o
-RC4_ENC =asm/rx86-elf.o
-RC5_ENC =asm/r586-elf.o
-MD5_OBJ_ASM =asm/mx86-elf.o
-SHA1_OBJ_ASM =asm/sx86-elf.o
-RMD160_OBJ_ASM=asm/rm86-elf.o
-THIRTY_TWO_BIT mode
-DES_PTR used
-DES_RISC1 used
-DES_UNROLL used
-BN_LLONG mode
-RC4_INDEX mode</programlisting>
-
-
-<para>After the package has been configured, you can build it by typing <literal>make</literal>. If the build did not successfully complete, consult the documentation that comes with the distribution or the FAQ at <systemitem role="url">http://www.cryptsoft.com/ssleay/</systemitem> for more information on what may have happened. If the build did complete, type <literal>make</literal> <literal>install</literal> to install the libraries on the system. Note that the makefile installs the package in <filename>/usr/local/ssl</filename> by default. If you decide to install it in another directory, remember the directory when configuring Samba to use SSL.</para>
-
-
-<sect2 role="" label="A.3.1" id="appa-SECT-3.1">
-<title>Configuring SSLeay for Your System</title>
-
-
-<para>The first thing you need to do is to set the <literal>PATH</literal> environment variable on your system to include the <filename>/bin</filename> directory of the SSL distribution. This can be done with the following statement:</para>
-
-
-<programlisting>PATH=$PATH:/usr/local/ssl/bin</programlisting>
-
-
-<para>That's the easy part. Following that, you will need to create a random series of characters that will be used to prime SSLeay's random number generator. The random number generator will be used to create key pairs for both the clients and the server. You can create this random series by filling a text file of a long series of random characters. For example, you can use your favorite editor to create a text file with random characters, or use this command and enter arbitrary characters at the standard input:</para>
-
-
-<programlisting>cat >/tmp/private.txt</programlisting>
-
-
-<para>The Samba documentation recommends that you type characters for longer than a minute before interrupting the input stream by hitting Control-D. Try not to type only the characters that are under your fingers on the keyboard; throw in some symbols and numbers as well. Once you've completed the random file, you can prime the random number generator with the following command:</para>
-
-
-<programlisting># ssleay genrsa -rand /tmp/private.txt >/dev/null
-2451 semi-random bytes loaded
-Generating RSA private key, 512 bit long modulus
-..+++++
-.................................+++++
-e is 65537 (0x10001)</programlisting>
-
-
-<para>You can safely ignore the output of this command. After it has completed, remove the series of characters used to create the key because this could be used to recreate any private keys that were generated from this random number generator:</para>
-
-
-<programlisting>rm -f /tmp/private.txt</programlisting>
-
-
-<para>The result of this command is the hidden file .<emphasis>rnd</emphasis>, which is stored in your home directory. SSLeay will use this file when creating key pairs in the future.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.3.2" id="appa-SECT-3.2">
-<title>Configuring Samba to use SSL</title>
-
-
-<para>
-<indexterm id="appa-idx-990398-0"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>configuring Samba to use</secondary></indexterm>At this point, you can compile Samba to use SSL. Recall that in <link linkend="SAMBA-CH-2">Chapter 2</link>, we said you have to first run the configure script, which initializes the makefile, before you compile Samba. In order to use SSL with Samba, you will need to reconfigure the makefile:</para>
-
-
-<programlisting>./configure --with-ssl</programlisting>
-
-
-<para>After that, you can compile Samba with the following commands:</para>
-
-
-<programlisting># <userinput>make clean</userinput>
-# <userinput>make all</userinput></programlisting>
-
-
-<para>If you encounter an error that says the <filename>smbd</filename> executable is missing the file <filename>ssl.h</filename>, you probably didn't install SSLeay in the default directory. Use the configure option <literal>--with-sslinc</literal> to point to the base directory of the SSL distribution—in this case, the directory that contains <emphasis>include/ssl.h</emphasis>.</para>
-
-
-<para>On the other hand, if you have a clean compile, you're ready to move on to the next step: creating certificates.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.3.3" id="appa-62097">
-<title>Becoming a Certificate Authority</title>
-
-
-<para><firstterm></firstterm>
-<indexterm id="appa-idx-990405-0" class="startofrange"><primary>certificate authority</primary></indexterm>The SSL protocol requires the use of X.509 certificates in the protocol handshake to ensure that either one or both parties involved in the communication are indeed who they say they are. Certificates in real life, such as those use for SSL connections on public web sites, can cost in the arena of $300 a year. This is because the certificate must have a digital signature placed on it by a <firstterm>certificate authority</firstterm>. A certificate authority is an entity that vouches for the authenticity of a digital certificate by signing it with its own private key. This way, anyone who wishes to check the authenticity of the certificate can simply use the certificate authority's public key to check the signature.</para>
-
-
-<para>You are allowed to use a public certificate authority with SSLeay. However, you don't have to. Instead, SSLeay will allow you to declare yourself a trusted certificate authority—specifying which clients you choose to trust and which clients you do not. In order to do this, you will need to perform several tasks with the SSLeay distribution.</para>
-
-
-<para>The first thing you need to do is specify a secure location where the certificates of the clients and potentially the server will be stored. We have chosen <filename>/etc/certificates</filename> as our default. Execute the following commands as <literal>root</literal>:</para>
-
-
-<programlisting># <userinput>cd /etc</userinput>
-# <userinput>mkdir certificates</userinput>
-# <userinput>chmod 700 certificates</userinput></programlisting>
-
-
-<para>Note that we shut out all access to users other than <literal>root</literal> for this directory. This is very important.</para>
-
-
-<para>Next, you need to set up the SSLeay scripts and configuration files to use the certificates stored in this directory. In order to do this, first modify the <filename>CA.sh</filename> script located at <emphasis>/usr/local/ssl/bin/CA.sh</emphasis> to specify the location of the directory you just created. Find the line that contains the following entry:</para>
-
-
-<programlisting>CATOP=./demoCA</programlisting>
-
-
-<para>Then change it to:</para>
-
-
-<programlisting>CATOP=/etc/certificates</programlisting>
-
-
-<para>Next, you need to modify the <emphasis>/usr/local/ssl/lib/ssleay.cnf</emphasis> file to specify the same directory. Find the entry:</para>
-
-
-<programlisting>[ CA_default ]
-dir = ./demoCA # Where everything is kept</programlisting>
-
-
-<para>Then change it to:</para>
-
-
-<programlisting>[ CA_default ]
-dir = /etc/certificates # Where everything is kept</programlisting>
-
-
-<para>Next, run the certificate authority setup script, <filename>CA.sh</filename>, in order to create the certificates. Be sure to do this as the same user that you used to prime the random number generator above:</para>
-
-
-<programlisting>/usr/local/ssl/bin/CA.sh -newca
-mkdir: cannot make directory '/etc/certificates': File exists
-CA certificate filename (or enter to create)</programlisting>
-
-
-<para>Press the Enter key to create a certificate for the CA. You should then see:</para>
-
-
-<programlisting>Making CA certificate ...
-Using configuration from /usr/local/ssl/lib/ssleay.cnf
-Generating a 1024 bit RSA private key
-.............................+++++
-.....................+++++
-writing new private key to /etc/certificates/private/cakey.pem
-Enter PEM pass phrase:</programlisting>
-
-
-<para>Enter a new pass phrase for your certificate. You will need to enter it twice correctly before SSLeay will accept it:</para>
-
-
-<programlisting>Enter PEM pass phrase:
-Verifying password - Enter PEM pass phrase:</programlisting>
-
-
-<para>Be sure to remember this pass phrase. You will need it to sign the client certificates in the future. Once SSLeay has accepted the pass phrase, it will continue on with a series of questions for each of the fields in the X509 certificate:</para>
-
-
-<programlisting>You are about to be asked to enter information that will be
-incorporated into your certificate request.
-What you are about to enter is what is called a Distinguished
-Name or a DN.
-There are quite a few fields but you can leave some blank
-For some fields there will be a default value,
-If you enter '.', the field will be left blank.</programlisting>
-
-
-<para>Fill out the remainder of the fields with information about your organization. For example, our certificate looks like this:</para>
-
-
-<programlisting>Country Name (2 letter code) [AU]:<userinput>US</userinput>
-State or Province Name (full name) [Some-State]:<userinput>California</userinput>
-Locality Name (eg, city) []:<userinput>Sebastopol</userinput>
-Organization Name (eg, company) []:<userinput>O'Reilly</userinput>
-Organizational Unit Name (eg, section) []:<userinput>Books</userinput>
-Common Name (eg, YOUR name) []:<userinput>John Doe</userinput>
-Email Address []:<userinput>doe@ora.com</userinput></programlisting>
-
-
-<para>After that, SSLeay will be configured as a certificate authority and can be used to sign certificates for client machines that will be connecting to the Samba server.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.3.4" id="appa-SECT-3.4">
-<title>Creating Certificates for Clients</title>
-
-
-<para>It's simple to create a certificate for a client machine. First, you need to generate a public/private key pair for each entity, create a certificate request file, and then use <emphasis>SSLeay</emphasis> to sign the file as a trusted authority.</para>
-
-
-<para>For our example client <literal>phoenix</literal>, this boils down to three SSLeay commands. The first generates a key pair for the client and places it in the file <filename>phoenix.key</filename>. The private key will be encrypted, in this case using triple DES. Enter a pass phrase when requested below—you'll need it for the next step:</para>
-
-
-<programlisting># ssleay genrsa -des3 1024 >phoenix.key
-1112 semi-random bytes loaded
-Generating RSA private key, 1024 bit long modulus
-........................................+++++
-.............+++++
-e is 65537 (0x10001)
-Enter PEM pass phrase:
-Verifying password - Enter PEM pass phrase:</programlisting>
-
-
-<para>After that command has completed, type in the following command:</para>
-
-
-<programlisting># <userinput>ssleay req -new -key phoenix.key -out phoenix-csr</userinput>
-Enter PEM pass phrase:</programlisting>
-
-
-<para>Enter the pass phrase for the client certificate you just created (not the certificate authority). At this point, you will need to answer the questionnaire again, this time for the client machine. In addition, you must type in a challenge password and an optional company name—those do not matter here. When the command completes, you will have a certificate request in the file <emphasis>phoenix-csr.</emphasis></para>
-
-
-<para>Then, you must sign the certificate request as the trusted certificate authority. Type in the following command:</para>
-
-
-<programlisting># <userinput>ssleay ca -days 1000 -inflies phoenix-csr >phoenix.pem</userinput></programlisting>
-
-
-<para>This command will prompt you to enter the PEM pass phrase of the <emphasis>certificate authority</emphasis>. Be sure that you do not enter the PEM pass phrase of the client certificate that you just created. After entering the correct pass phrase, you should see the following:</para>
-
-
-<programlisting>Check that the request matches the signature
-Signature ok
-The Subjects Distinguished Name is as follows:
-...</programlisting>
-
-
-<para>This will be followed by the information that you just entered for the client certificate. If there is an error in the fields, the program will notify you. On the other hand, if everything is fine, SSLeay will confirm that it should sign the certificate and commit it to the database. This adds a record of the certificate to the <filename>/etc/certificates/newcerts</filename> directory.</para>
-
-
-<para>The operative files at the end of this exercise are the <emphasis>phoenix.key</emphasis> and <emphasis>phoenix.pem</emphasis> files, which reside in the current directory. These files will be passed off to the client with whom the SSL-enabled Samba server will interact, and will be used by SSL Proxy.<firstterm></firstterm>
-<indexterm id="appa-idx-990421-0" class="endofrange" startref="appa-idx-990405-0"/></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.3.5" id="appa-SECT-3.5">
-<title>Configuring the Samba Server</title>
-
-
-<para>The next step is to modify the Samba configuration file to include the following setup options. These options assume that you created the certificates directory for the certificate authority at <filename>/etc/certificates </filename>:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl server cert = /etc/certificates/cacert.pem
- ssl server key = /etc/certificates/private/cakey.pem
- ssl CA certDir = /etc/certificates</programlisting>
-
-
-<para>At this point, you will need to kill the Samba daemons and restart them manually:</para>
-
-
-<programlisting># <userinput>nmbd -D</userinput>
-# <userinput>smbd -D</userinput>
-Enter PEM pass phrase:</programlisting>
-
-
-<para>You will need to enter the PEM pass phrase of the certificate authority to start up the Samba daemons. Note that this may present a problem in terms of starting the program using ordinary means. However, you can get around this using advanced scripting languages, such as Expect or Python.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.3.6" id="appa-SECT-3.6">
-<title>Testing with smbclient</title>
-
-
-<para>A good way to test whether Samba is working properly is to use the <emphasis>smbclient</emphasis> program. On the Samba server, enter the following command, substituting the appropriate share and user for a connection:</para>
-
-
-<programlisting># <userinput>smbclient //hydra/data -U tom</userinput></programlisting>
-
-
-<para>You should see several debugging statements followed by a line indicating the negotiated cipher, such as:</para>
-
-
-<programlisting>SSL: negotiated cipher: DES-CBC3-SHA</programlisting>
-
-
-<para>After that, you can enter your password and connect to the share normally. If this works, you can be sure that Samba is correctly supporting SSL connections. Now, on to the client setup. <indexterm id="appa-idx-990386-0" class="endofrange" startref="appa-idx-990613-0"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="A.4" id="appa-SECT-4">
-<title>Setting Up SSL Proxy</title>
-
-
-<para>The <indexterm id="appa-idx-990393-0"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>SS Proxy</secondary><tertiary>setting up</tertiary></indexterm>SSL Proxy program is available as a standalone binary or as source code. You can download it from <systemitem role="url">http://obdev.at/Products/sslproxy.html</systemitem>.</para>
-
-
-<para>Once it is downloaded, you can configure and compile it like Samba. We will configure it on a Windows NT system. However, setting it up for a Unix system involves a nearly identical series of steps. Be sure that you are the superuser (administrator) for the next series of steps.</para>
-
-
-<para>If you downloaded the binary for Windows NT, you should have the following files in a directory:</para>
-
-
-<itemizedlist>
-
-<listitem><para><filename>cygwinb19.dll</filename></para></listitem>
-
-<listitem><para><filename>README.TXT</filename></para></listitem>
-
-<listitem><para><filename>sslproxy.exe</filename></para></listitem>
-
-<listitem><para><filename>dummyCert.pem</filename></para></listitem>
-
-</itemizedlist>
-
-<para>The only one that you will be interested in is the SSL Proxy executable. Copy over the <emphasis>phoenix.pem</emphasis> and <emphasis>phoenix.key</emphasis> files that you generated earlier for the client to the same directory as the SSL proxy executable. Make sure that the directory is secure from the prying eyes of other users.</para>
-
-
-<para>The next step is to ensure that the Windows NT machine can resolve the NetBIOS name of the Samba server. This means that you should either have a WINS server up and running (the Samba server can perform this task with the <literal>wins</literal> <literal>support</literal> <literal>=</literal> <literal>yes</literal> option) or have it listed in the appropriate <emphasis>hosts</emphasis> file of the system. See <link linkend="SAMBA-CH-7">Chapter 7</link>, for more information on WINS server.<footnote label="1" id="appa-pgfId-986801">
-
-
-<para>If you are running SSL Proxy on a Unix server, you should ensure that the DNS name of the Samba server can be resolved.</para>
-
-
-</footnote></para>
-
-
-<para>Finally, start up SSL Proxy with the following command. Here, we assume that <literal>hydra</literal> is the name of the Samba server:</para>
-
-
-<programlisting>#<userinput> C:\SSLProxy>sslproxy -l 139 -R hydra -r 139 -n -c phoenix.pem -k phoenix.key</userinput></programlisting>
-
-
-<para>This tells SSL Proxy to listen for connections to port 139 and relay those requests to port 139 on the NetBIOS machine <literal>hydra</literal>. It also instructs SSL Proxy to use the <filename>phoenix.pem</filename> and <filename>phoenix.key</filename> files to generate the certificate and keys necessary to initiate the SSL connection. SSL Proxy responds with:</para>
-
-
-<programlisting>Enter PEM pass phrase:</programlisting>
-
-
-<para>Enter the PEM pass phrase of the client keypair that you generated, <emphasis>not</emphasis> the certificate authority. You should then see the following output:</para>
-
-
-<programlisting>SSL: No verify locations, trying default
-proxy ready, listening for connections</programlisting>
-
-
-<para>That should take care of the client. You can place this command in a startup sequence on either Unix or Windows NT if you want this functionality available at all times. Be sure to set any clients you have connecting to the NT server (including the NT server itself) to point to this server instead of the Samba server.</para>
-
-
-<para>After you've completed setting this up, try to connect using clients that proxy through the NT server. You should find that it works almost transparently.</para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="A.5" id="appa-SECT-5">
-<title>SSL Configuration Options</title>
-
-
-<para>
-<indexterm id="appa-idx-990427-0" class="startofrange"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>configuration options for</secondary></indexterm><link linkend="appa-61150">Table 1.1</link> summarizes the configuration options introduced in the previous section for using SSL. Note that all of these options are global in scope; in other words, they must appear in the <literal>[global]</literal> section of the configuration file.</para>
-
-
-<table label="A.1" id="appa-61150">
-<title>SSL Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>ssl</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Indicates whether SSL mode is enabled with Samba.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl hosts</literal></para></entry>
-
-<entry colname="col2"><para>string (list of addresses)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of hosts that must always connect using SSL.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl hosts resign</literal></para></entry>
-
-<entry colname="col2"><para>string (list of addresses)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of hosts that never connect using SS.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl CA certDir</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the directory where the certificates are stored.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl CA certFile</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies a file that contains all of the certificates for Samba.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl server cert</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the location of the server's certificate.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl server key</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the location of the server's private key.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl client cert</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the location of the client's certificate.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl client key</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the location of the client's private key.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl require clientcert</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Indicates whether Samba should require each client to have a certificate.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl require servercert</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Indicates whether the server itself should have a certificate.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl ciphers</literal></para></entry>
-
-<entry colname="col2"><para>String</para></entry>
-
-<entry colname="col3"><para>Specifies the cipher suite to use during protocol negotiation.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl version</literal></para></entry>
-
-<entry colname="col2"><para><literal>ssl2or3</literal>, <literal>ssl3</literal>, or <literal>tls1</literal></para></entry>
-
-<entry colname="col3"><para>Specifies the version of SSL to use.</para></entry>
-
-<entry colname="col4"><para><literal>ssl2or3</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ssl compatibility</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Indicates whether compatibility with other implementations of SSL should be activated.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="A.5.1" id="appa-SECT-5.0.1">
-<indexterm id="appa-idx-990620-0"><primary>ssl option</primary></indexterm>
-<title>
-ssl</title>
-
-
-<para>This global option configures Samba to use SSL for communication between itself and clients. The default value of this option is <literal>no</literal>. You can reset it as follows:</para>
-
-
-<programlisting>[global]
- ssl = yes</programlisting>
-
-
-<para>Note that in order to use this option, you must have a proxy for Windows 95/98 clients, such as in the model presented earlier in this chapter.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.2" id="appa-SECT-5.0.2">
-<indexterm id="appa-idx-990625-0"><primary>ssl hosts option</primary></indexterm>
-<title>
-ssl hosts</title>
-
-
-<para>This option specifies the hosts that will be forced into using SSL. The syntax for specifying hosts and addresses is the same as the <literal>hosts</literal> <literal>allow</literal> and the <literal>hosts</literal> <literal>deny</literal> configuration options. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.</programlisting>
-
-
-<para>This example specifies that all hosts that fall into the 192.168.220 subnet must use SSL connections with the client. This type of structure is useful if you know that various connections will be made by a subnet that lies across an untrusted network, such as the Internet. If neither this option nor the <literal>ssl</literal> <literal>hosts</literal> <literal>resign</literal> option has been specified, and <literal>ssl</literal> is set to <literal>yes</literal>, Samba will allow only SSL connections from all clients.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.3" id="appa-SECT-5.0.3">
-<indexterm id="appa-idx-990628-0"><primary>ssl hosts resign option</primary></indexterm>
-<title>
-ssl hosts resign</title>
-
-
-<para>This option specifies the hosts that will <emphasis>not</emphasis> be forced into SSL mode. The syntax for specifying hosts and addresses is the same as the <literal>hosts</literal> <literal>allow</literal> and the <literal>hosts</literal> <literal>deny</literal> configuration options. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts resign = 160.2.310. 160.2.320.</programlisting>
-
-
-<para>This example specifies that all hosts that fall into the 160.2.310 or 160.2.320 subnets will not use SSL connections with the client. If neither this option nor the <literal>ssl</literal> <literal>hosts</literal> option has been specified, and <literal>ssl</literal> is set to <literal>yes</literal>, Samba will allow only SSL connections from all clients.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.4" id="appa-SECT-5.0.4">
-<indexterm id="appa-idx-990631-0"><primary>ssl CA certDir option</primary></indexterm>
-<title>
-ssl CA certDir</title>
-
-
-<para>This option specifies the directory containing the certificate authority's certificates that Samba will use to authenticate clients. There must be one file in this directory for each certificate authority, named as specified earlier in this chapter. Any other files in this directory are ignored. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certDir = /usr/local/samba/cert</programlisting>
-
-
-<para>There is no default for this option. You can alternatively use the option <literal>ssl</literal> <literal>CA</literal> <literal>certFile</literal> if you wish to place all the certificate authority information in the same file.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.5" id="appa-SECT-5.0.5">
-<indexterm id="appa-idx-990634-0"><primary>ssl CA certFile option</primary></indexterm>
-<title>
-ssl CA certFile</title>
-
-
-<para>This option specifies a file that contains the certificate authority's certificates that Samba will use to authenticate clients. This option differs from <literal>ssl</literal> <literal>CA</literal> <literal>certDir</literal> in that there is only one file used for all the certificate authorities. An example of its usage follows:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certFile = /usr/local/samba/cert/certFile</programlisting>
-
-
-<para>There is no default for this option. You can also use the option <literal>ssl</literal> <literal>CA</literal> <literal>certDir</literal> if you wish to have a separate file for each certificate authority that Samba trusts.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.6" id="appa-SECT-5.0.6">
-<indexterm id="appa-idx-990637-0"><primary>ssl server cert option</primary></indexterm>
-<title>
-ssl server cert</title>
-
-
-<para>This option specifies the location of the server's certificate. This option is mandatory; the server must have a certificate in order to use SSL. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certFile = /usr/local/samba/cert/certFile
- ssl server cert = /usr/local/samba/private/server.pem</programlisting>
-
-
-<para>There is no default for this option. Note that the certificate may contain the private key for the server.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.7" id="appa-SECT-5.0.7">
-<indexterm id="appa-idx-990640-0"><primary>ssl server key option</primary></indexterm>
-<title>
-ssl server key</title>
-
-
-<para>This option specifies the location of the server's private key. You should ensure that the location of the file cannot be accessed by anyone other than <literal>root</literal>. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certFile = /usr/local/samba/cert/certFile
- ssl server key = /usr/local/samba/private/samba.pem</programlisting>
-
-
-<para>There is no default for this option. Note that the private key may be contained in the certificate for the server.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.8" id="appa-SECT-5.0.8">
-<indexterm id="appa-idx-990643-0"><primary>ssl client cert option</primary></indexterm>
-<title>
-ssl client cert</title>
-
-
-<para>This option specifies the location of the client's certificate. The certificate may be requested by the Samba server with the <literal>ssl</literal> <literal>require</literal> <literal>clientcert</literal> option; the certificate is also used by <filename>smbclient</filename>. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certFile = /usr/local/samba/cert/certFile
- ssl server cert = /usr/local/ssl/private/server.pem
- ssl client cert= /usr/local/ssl/private/clientcert.pem</programlisting>
-
-
-<para>There is no default for this option.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.9" id="appa-SECT-5.0.9">
-<indexterm id="appa-idx-990646-0"><primary>ssl client key option</primary></indexterm>
-<title>
-ssl client key</title>
-
-
-<para>This option specifies the location of the client's private key. You should ensure that the location of the file cannot be accessed by anyone other than <literal>root</literal>. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certDir = /usr/local/samba/cert/
- ssl server key = /usr/local/ssl/private/samba.pem
- ssl client key = /usr/local/ssl/private/clients.pem</programlisting>
-
-
-<para>There is no default for this option. This option is only needed if the client has a certificate.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.10" id="appa-SECT-5.0.10">
-<indexterm id="appa-idx-990649-0"><primary>ssl require clientcert option</primary></indexterm>
-<title>
-ssl require clientcert</title>
-
-
-<para>This option specifies whether the client is required to have a certificate. The certificates listed with either the <literal>ssl</literal> <literal>CA</literal> <literal>certDir</literal> or the <literal>ssl</literal> <literal>CA</literal> <literal>certFile</literal> will be searched to confirm that the client has a valid certificate and is authorized to connect to the Samba server. The value of this option is a simple boolean. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certFile = /usr/local/samba/cert/certFile
- ssl require clientcert = yes</programlisting>
-
-
-<para>We recommend that you require certificates from all clients that could be connecting to the Samba server. The default value for this option is <literal>no</literal>.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.11" id="appa-SECT-5.0.11">
-<indexterm id="appa-idx-990652-0"><primary>ssl require servercert option</primary></indexterm>
-<title>
-ssl require servercert</title>
-
-
-<para>This option specifies whether the server is required to have a certificate. Again, this will be used by the <filename>smbclient</filename> program. The value of this option is a simple boolean. For example:</para>
-
-
-<programlisting>[global]
- ssl = yes
- ssl hosts = 192.168.220.
- ssl CA certFile = /usr/local/samba/cert/certFile
- ssl require clientcert = yes
- ssl require servercert = yes</programlisting>
-
-
-<para>Although we recommend that you require certificates from all clients that could be connecting to the Samba server, a server certificate is not required. It is, however, recommended. The default value for this option is <literal>no</literal>.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.12" id="appa-SECT-5.0.12">
-<indexterm id="appa-idx-990655-0"><primary>ssl ciphers option</primary></indexterm>
-<title>
-ssl ciphers</title>
-
-
-<para>This option sets the ciphers on which SSL will decide during the negotiation phase of the SSL connection. Samba can use any of the following ciphers:</para>
-
-
-<programlisting>DEFAULT
-DES-CFB-M1
-NULL-MD5
-RC4-MD5
-EXP-RC4-MD5
-RC2-CBC-MD5
-EXP-RC2-CBC-MD5
-IDEA-CBC-MD5
-DES-CBC-MD5
-DES-CBC-SHA
-DES-CBC3-MD5
-DES-CBC3-SHA
-RC4-64-MD5
-NULL</programlisting>
-
-
-<para>It is best not to set this option unless you are familiar with the SSL protocol and want to mandate a specific cipher suite.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.13" id="appa-SECT-5.0.13">
-<indexterm id="appa-idx-990658-0"><primary>ssl version option</primary></indexterm>
-<title>
-ssl version</title>
-
-
-<para>This global option specifies the version of SSL that Samba will use when handling encrypted connections. The default value is <literal>ssl2or3</literal>, which specifies that either version 2 or 3 of the SSL protocol can be used, depending on which version is negotiated in the handshake between the server and the client. However, if you want Samba to use only a specific version of the protocol, you can specify the following:</para>
-
-
-<programlisting>[global]
- ssl version = ssl3</programlisting>
-
-
-<para>Again, it is best not to set this option unless you are familiar with the SSL protocol and want to mandate a specific version.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="A.5.14" id="appa-SECT-5.0.14">
-<indexterm id="appa-idx-990661-0"><primary>ssl compatibility option</primary></indexterm>
-<title>
-ssl compatibility</title>
-
-
-<para>This global option specifies whether Samba should be configured to use other versions of SSL. However, because no other versions exist at this writing, the issue is moot and the variable should always be left at the<indexterm id="appa-idx-990431-0" class="endofrange" startref="appa-idx-990427-0"/> default.<indexterm id="appa-idx-990339-0" class="endofrange" startref="appa-idx-990325-0"/>
-<indexterm id="appa-idx-990339-1" class="endofrange" startref="appa-idx-990325-1"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-</appendix>
+++ /dev/null
-<appendix label="B" id="SAMBA-AP-B">
-<title>Samba Performance Tuning</title>
-
-
-
-
-<para>
-<indexterm id="appb-idx-959725-0" class="startofrange"><primary>Samba</primary><secondary>performance tuning</secondary></indexterm>
-<indexterm id="appb-idx-959725-1" class="startofrange"><primary>performance tuning</primary></indexterm>
-<indexterm id="appb-idx-959725-2" class="startofrange"><primary>configuring Samba</primary><secondary>performance tuning</secondary></indexterm>This appendix discusses various ways of performance tuning and system sizing with Samba. <firstterm>Performance tuning</firstterm> is the art of finding bottlenecks and adjusting to eliminate them. <emphasis>Sizing</emphasis> is the practice of eliminating bottlenecks by spending money to avoid having them in the first place. Normally, you won't have to worry about either with Samba. On a completely untuned server, Samba will happily support a small community of users. However, on a properly tuned server, Samba will support at least twice as many users. This chapter is devoted to outlining various performance-tuning and sizing techniques that you can use if you want to stretch your Samba server to the limit.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="B.1" id="appb-47134">
-<title>A Simple Benchmark</title>
-
-
-<para>
-<indexterm id="appb-idx-959739-0"><primary>Samba</primary><secondary>performance tuning</secondary><tertiary>benchmark for</tertiary></indexterm>
-<indexterm id="appb-idx-959739-1"><primary>performance tuning</primary><secondary>benchmark for</secondary></indexterm>
-<indexterm id="appb-idx-959739-2"><primary>configuring Samba</primary><secondary>performance tuning</secondary><tertiary>benchmark for</tertiary></indexterm>How do you know if you're getting reasonable performance? A simple benchmark is to compare Samba with FTP. <link linkend="appb-73167">Table 2.1</link> shows the throughput, in kilobytes per second, of a pair of servers: a medium-size Sun SPARC Ultra and a small Linux Pentium server. Numbers are reported in kilobytes per second (KB/s).</para>
-
-
-<table label="B.1" id="appb-73167">
-<title>Sample Benchmark Benchmarks </title>
-
-<tgroup cols="4">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Command</para></entry>
-
-<entry colname="col2"><para>FTP</para></entry>
-
-<entry colname="col3"><para>Untuned Samba</para></entry>
-
-<entry colname="col4"><para>Tuned Samba</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Sparc get</para></entry>
-
-<entry colname="col2"><para>1014.5</para></entry>
-
-<entry colname="col3"><para>645.3</para></entry>
-
-<entry colname="col4"><para>866.7</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Sparc put</para></entry>
-
-<entry colname="col2"><para>379.8</para></entry>
-
-<entry colname="col3"><para>386.1</para></entry>
-
-<entry colname="col4"><para>329.5</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Pentium get</para></entry>
-
-<entry colname="col2"><para>973.27</para></entry>
-
-<entry colname="col3"><para>N/A</para></entry>
-
-<entry colname="col4"><para>725</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Pentium put</para></entry>
-
-<entry colname="col2"><para>1014.5</para></entry>
-
-<entry colname="col3"><para>N/A</para></entry>
-
-<entry colname="col4"><para>1100</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>If you run the same tests on your server, you probably won't see the same numbers. However, you <emphasis>should</emphasis> see similar ratios of Samba to FTP, probably in the range of 68 to 80 percent. It's not a good idea to base <emphasis>all</emphasis> of Samba's throughput against FTP. The golden rule to remember is this: if Samba is much slower than FTP, it's time to tune it.</para>
-
-
-<para>You might think that an equivalent test would be to compare Samba to NFS. In reality, however, it's much less useful to compare their speeds. Depending entirely on whose version of NFS you have and how well it's tuned, Samba can be slower or faster than NFS. We usually find that Samba is faster, but watch out; NFS uses a different algorithm from Samba, so tuning options that are optimal for NFS may be detrimental for Samba. If you run Samba on a well-tuned NFS server, Samba may perform rather badly.</para>
-
-
-<para>A more popular benchmark is Ziff-Davis' <emphasis>NetBench,</emphasis> a simulation of many users on client machines running word processors and accessing data on the SMB server. It's not a prefect measure (each NetBench client does about ten times the work of a normal user on our site), but it is a fair comparison of similar servers. In tests performed by Jeremy Allison in November 1998, Samba 2.0 on a SGI multiprocessor outperformed NT Server 4.0 (Patch Level 2) on an equivalent high-end Compaq. This was confirmed and strengthened by a Sm@rt Reseller test of NT and Linux on identical hardware in February 1999.</para>
-
-
-<para>In April 1999, the Mindcraft test lab released a report about a test showing that Samba on a four-processor Linux machine was significantly slower than native file serving on the same machine running Windows NT. While the original report was slammed by the Open Source community because it was commissioned by Microsoft and tuned the systems to favor Windows NT, a subsequent test was fairer and generally admitted to reveal some areas where Linux needed to improve its performance, especially on multiprocessors. Little was said about Samba itself. Samba is known to scale well on multiprocessors, and exceeds 440MB/s on a four-processor SGI O200, beating Mindcraft's 310MB/s.</para>
-
-
-<para>Relative performance will probably change as NT and PC hardware get faster, of course, but Samba is improving as well. For example, Samba 1.9.18 was faster only with more than 35 clients. Samba 2.0, however, is faster regardless of the number of clients. In short, Samba is very competitive with the best networking software in the industry, and is only getting better.</para>
-
-
-<para>As we went to press, Andrew Tridgell released the alpha-test version suite of benchmarking programs for Samba and SMB networks. Expect even more work on performance from the Samba team in the future.</para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="B.2" id="appb-50295">
-<title>Samba Tuning</title>
-
-
-<para>
-<indexterm id="appb-idx-959765-0"><primary>tuning</primary><see>performance tuning</see></indexterm>That being said, let's discuss how you can take an already fast networking package and make it even faster.</para>
-
-
-<sect2 role="" label="B.2.1" id="appb-SECT-2.1">
-<title>Benchmarking</title>
-
-
-<para>
-<indexterm id="appb-idx-959749-0"><primary>Samba</primary><secondary>performance tuning</secondary><tertiary>benchmark for</tertiary></indexterm>
-<indexterm id="appb-idx-959749-1"><primary>performance tuning</primary><secondary>benchmark for</secondary></indexterm>
-<indexterm id="appb-idx-959749-2"><primary>configuring Samba</primary><secondary>performance tuning</secondary><tertiary>benchmark for</tertiary></indexterm>Benchmarking is an arcane and somewhat black art, but the level of expertise needed for simple performance tuning is fairly low. Since the Samba server's goal in life is to transfer files, we will examine only throughput, not response time to particular events, under the benchmarking microscope. After all, it's relatively easy to measure file transfer speed, and Samba doesn't suffer too badly from response-time problems that would require more sophisticated techniques.</para>
-
-
-<para>Our basic strategy for this work will be:</para>
-
-
-<itemizedlist>
-
-<listitem><para>Find a reasonably-sized file to copy and a program that reports on copy speeds, such as <filename>smbclient</filename>.</para></listitem>
-
-<listitem><para>Find a quiet (or typical) time to do the test.</para></listitem>
-
-<listitem><para>Pre-run each test a few times to preload buffers.</para></listitem>
-
-<listitem><para>Run tests several times and watch for unusual results.</para></listitem>
-
-<listitem><para>Record each run in detail.</para></listitem>
-
-<listitem><para>Compare the average of the valid runs to expected values.</para></listitem>
-
-</itemizedlist>
-
-<para>After establishing a baseline using this method, we can adjust a single parameter and do the measurements all over again. An empty table for your tests is provided at the end of this chapter.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="B.2.2" id="appb-SECT-2.2">
-<title>Things to Tweak</title>
-
-
-<para>There are literally thousands of Samba setting combinations that you can use in search of that perfect server. Those of us with lives outside of system administration, however, can narrow down the number of options to those listed in this section, which are the most likely to affect overall throughput. They are presented roughly in order of impact.</para>
-
-
-<sect3 role="" label="B.2.2.1" id="appb-SECT-2.2.1">
-<title>Log level</title>
-
-
-<para>
-<indexterm id="appb-idx-959753-0"><primary>log files/logging</primary><secondary>levels of</secondary><tertiary>tuning</tertiary></indexterm>This is an obvious one. Increasing the logging level (<literal>log</literal>
-<indexterm id="appb-idx-960330-0"><primary>log level option</primary></indexterm>
-<indexterm id="appb-idx-960330-1"><primary>debug level option</primary></indexterm> <literal>level</literal> or <literal>debug</literal> <literal>level</literal> configuration options) is a good way to debug a problem, unless you happen to be searching for a performance problem! As mentioned in <link linkend="ch04-21486">Chapter 4</link>, Samba produces a ton of debugging messages at level 3 and above, and writing them to disk or syslog is a slow operation. In our <filename>smbclient/ftp</filename> tests, raising the log level from 0 to 3 cut the untuned <literal>get</literal> <literal>speed</literal> from 645.3 to 622.2KB/s, or roughly 5 percent. Higher log levels were even worse.</para>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.2" id="appb-SECT-2.2.2">
-<title>Socket options</title>
-
-
-<para>The next thing to look at are the <literal>socket</literal>
-<indexterm id="appb-idx-960332-0"><primary>socket options configuration options</primary></indexterm> <literal>options</literal> configuration options. These are really host system tuning options, but they're set on a per-connection basis, and can be reset by Samba on the sockets it employs by adding <literal>socket</literal> <literal>options</literal> <literal>=</literal> <literal>option</literal> to the <literal>[global]</literal> section of your <filename>smb.conf </filename>file. Not all of these options are supported by all vendors; check your vendor's manual pages on <emphasis>setsockopt </emphasis>(1) or <emphasis>socket </emphasis>(5) for details.</para>
-
-
-<para>The main options are:</para>
-
-
-<variablelist>
-<varlistentry><term><literal>TCP_NODELAY</literal></term>
-<listitem><para>Have the server send as many packets as necessary to keep delay low. This is used on telnet connections to give good response time, and is used—somewhat counter-intuitively—to get good speed even when doing small requests or when acknowledgments are delayed (as seems to occur with Microsoft TCP/IP). This is worth a 30-50 percent speedup by itself. Incidentally, in Samba 2.0.4, <literal>socket</literal> <literal>options</literal> <literal>=</literal> <literal>TCP_NODELAY</literal> became the default value for that option.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>IPTOS_LOWDELAY</literal></term>
-<listitem><para>This is another option that trades off throughput for lower delay, but which affects routers and other systems, not the server. All the IPTOS options are new; they're not supported by all operating systems and routers. If they are supported, set <literal>IPTOS_LOWDELAY</literal> whenever you set <literal>TCP_NODELAY</literal>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>SO_SNDBUF</literal> <literal>and</literal> <literal>SO_RCVBUF</literal></term>
-<listitem><para>The send and receive buffers can often be the reset to a value higher than that of the operating system. This yields a marginal increase of speed (until it reaches a point of diminishing returns).</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>SO_KEEPALIVE</literal></term>
-<listitem><para>This initiates a periodic (four-hour) check to see if the client has disappeared. Expired connections are addressed somewhat better with Samba's <literal>keepalive</literal> and <literal>dead</literal> <literal>time</literal> options. All three eventually arrange to close dead connections, returning unused memory and process-table entries to the operating system.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>There are several other socket options you might look at, (e.g., <literal>SO_SNDLOWAT</literal>), but they vary in availability from vendor to vendor. You probably want to look at <citetitle>TCP/IP Illustrated</citetitle> if you're interested in exploring more of these options for performance tuning with Samba.</para>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.3" id="appb-SECT-2.2.3">
-<title>read raw and write raw</title>
-
-
-<para>
-<indexterm id="appb-idx-959754-0"><primary>read raw, tuning</primary></indexterm>
-<indexterm id="appb-idx-959754-1"><primary>write raw, tuning</primary></indexterm>These are important performance configuration options; they enable Samba to use large reads and writes to the network, of up to 64KB in a single SMB request. They also require the largest SMB packet structures, <literal>SMBreadraw</literal> and <literal>SMBwriteraw</literal>, from which the options take their names. Note that this is not the same as a Unix <emphasis>raw read</emphasis>. This Unix term usually refers to reading disks without using the files system, quite a different sense from the one described here for Samba.</para>
-
-
-<para>In the past, some client programs failed if you tried to use <literal>read</literal> <literal>raw</literal>. As far as we know, no client suffers from this problem any more. Read and write raw default to <literal>yes</literal>, and should be left on unless you find you have one of the buggy clients.</para>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.4" id="appb-SECT-2.2.4">
-<title>Opportunistic locking</title>
-
-
-<para>
-<indexterm id="appb-idx-959755-0"><primary>opportunistic locking</primary><secondary>tuning</secondary></indexterm>
-<indexterm id="appb-idx-959755-1"><primary>locks/locking files</primary><secondary>opportunistic locking</secondary><tertiary>tuning of</tertiary></indexterm>Opportunistic locks, or <emphasis>oplocks</emphasis>, allow clients to cache files locally, improving performance on the order of 30 percent. This option is now enabled by default. For read-only files, the <literal>fake</literal> <literal>oplocks</literal> provides the same functionality without actually doing any caching. If you have files that cannot be cached, <emphasis>oplocks</emphasis> can be turned off.</para>
-
-
-<para>Database files should never be cached, nor should any files that are updated both on the server and the client and whose changes must be immediately visible. For these files, the <literal>veto</literal> <literal>oplock</literal>
-<indexterm id="appb-idx-960336-0"><primary>oplock files option</primary></indexterm> <literal>files</literal> option allows you to specify a list of individual files or a pattern containing wildcards to avoid caching. <emphasis>oplocks</emphasis> can be turned off on a share-by-share basis if you have large groups of files you don't want cached on clients. See <link linkend="SAMBA-CH-5">Chapter 5</link>, for more information on opportunistic locks.</para>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.5" id="appb-SECT-2.2.5">
-<title>IP packet size (MTU)</title>
-
-
-<para>
-<indexterm id="appb-idx-959756-0"><primary>IP packet size, tuning</primary></indexterm>Networks generally set a limit to the size of an individual transmission or packet This is called the Maximum Segment Size, or if the packet header size is included, the <indexterm id="appb-idx-959757-0"><primary>Maximum Transport Unit (MTU)</primary></indexterm>
-<indexterm id="appb-idx-959757-1"><primary>MTU (Maximum Transport Unit)</primary></indexterm>Maximum Transport Unit (MTU). This MTU is not set by Samba, but Samba needs to use a <literal>max</literal> <literal>xmit</literal> (write size) bigger than the MTU, or throughput will be reduced. This is discussed in further detail in the following note. The MTU is normally preset to 1500 bytes on an Ethernet and 4098 bytes on FDDI. In general, having it too low cuts throughput, and having it too high causes a sudden performance dropoff due to fragmentation and retransmissions.</para>
-
-
-<tip role="ora">
-<para>If you are communicating over a router, some systems will assume the router is a serial link (e.g., a T1) and set the MTU to more or less 536 bytes. Windows 95 makes this mistake, which causes nearby clients to perform well, but clients on the other side of the router to be noticeably slower. If the client makes the opposite error and uses a large MTU on a link which demands a small one, the packets will be broken up into fragments. This slows transfers slightly, and any networking errors will cause multiple fragments to be retransmitted, which slows Samba significantly. Fortunately, you can modify the Windows MTU size to prevent either error. To understand this in more detail, see "The Windows 95 Networking Frequently Asked Questions (FAQ)" at <systemitem role="url">http://www.stanford.edu/~llurch/win95netbugs/faq.html</systemitem>, which explains how to override the Windows MTU and Window Size.</para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.6" id="appb-19919">
-<title>The TCP receive window</title>
-
-
-<para>
-<indexterm id="appb-idx-959758-0"><primary>TCP/IP networking protocol</primary><secondary>receive window, tuning</secondary></indexterm>TCP/IP works by breaking down data into small packets that can be transmitted from one machine to another. When each packet is transmitted, it contains a checksum that allows the receiver to check the packet data for potential errors in transmission. Theoretically, when a packet is received and verified, an acknowledgment packet should be sent back to the sender that essentially says, "Everything arrived intact: please continue."</para>
-
-
-<para>In order to keep things moving, however, TCP accepts a range (window) of packets that allows a sender to keep transmitting without having to wait for an acknowledgment of every single packet. (It can then bundle a group of acknowledgments and transmit them back to the sender at the same time.) In other words, this receive window is the number of bytes that the sender can transmit before it has to stop and wait for a receiver's acknowledgment. Like the MTU, it is automatically set based on the type of connection. Having the window too small causes a lot of unnecessary waiting for acknowledgment messages. Various operating systems set moderate buffer sizes on a per-socket basis to keep one program from hogging all the memory.</para>
-
-
-<para>The buffer sizes are assigned in bytes, such as <literal>SO_SNDBUF=8192</literal> in the <literal>socket</literal> <literal>options</literal> line. Thus, an example <literal>socket</literal> <literal>options</literal> configuration option is:</para>
-
-
-<programlisting>socket options = SO_SNDBUF=8192</programlisting>
-
-
-<para>Normally, one tries to set these socket options higher than the default: 4098 in SunOS 4.1.3 and SVR4, and 8192-16384 in AIX, Solaris, and BSD. 16384 has been suggested as a good starting point: in a non-Samba test mentioned in Stevens' book, it yielded a 40 percent improvement. You'll need to experiment, because performance will fall off again if you set the sizes too high. This is illustrated in <link linkend="appb-34738">Figure 2.1</link>, a test done on a particular Linux system.</para>
-
-
-<figure label="B.1" id="appb-34738">
-<title>SO_SNDBUF size and performance</title>
-
-<graphic width="502" depth="263" fileref="figs/sam.ab01.gif"></graphic>
-</figure>
-
-<para>Setting the socket options <literal>O_SNDBUF</literal> and <literal>SO_RCVBUF</literal> to less than the default is inadvisable. Setting them higher improves performance, up to a network-specific limit. However, once you exceed that limit, performance will abruptly level off.</para>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.7" id="appb-SECT-2.2.7">
-<indexterm id="appb-idx-960371-0"><primary>max xmit option</primary></indexterm>
-<title>
-max xmit</title>
-
-
-<para>
-<indexterm id="appb-idx-960373-0"><primary>write size, tuning</primary></indexterm>In Samba, the option that is directly related with the MTU and window size is <literal>max</literal> <literal>xmit</literal>. This option sets the largest block of data Samba will try to write at any one time. It's sometimes known as the <firstterm>write size</firstterm>, although that is not the name of the Samba configuration option.</para>
-
-
-<para>Because the percentage of each block required for overhead falls as the blocks get larger, max xmit is conventionally set as large as possible. It defaults to the protocol's upper limit, which is 64 kilobytes. The smallest value that doesn't cause significant slowdowns is 2048. If it is set low enough, it will limit the largest packet size that Samba will be able to negotiate. This can be used to simulate a small MTU if you need to test an unreliable network connection. However, such a test should not be used in production for reducing the effective MTU.</para>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.8" id="appb-SECT-2.2.8">
-<title>read size</title>
-
-
-<para>
-<indexterm id="appb-idx-959760-0"><primary>read size, tuning</primary></indexterm>If <literal>max</literal> <literal>xmit</literal> is commonly called the write size, you'd expect <literal>read</literal> <literal>size</literal> to be the maximum amount of data that Samba would want to read from the client via the network. Actually, it's not. In fact, it's an option to trigger <firstterm>write ahead</firstterm>
-<indexterm id="appb-idx-959764-0"><primary>write ahead, tuning</primary></indexterm>. This means that if Samba gets behind reading from the disk and writing to the network (or vice versa) by the specified amount, it will start overlapping network writes with disk reads (or vice versa).</para>
-
-
-<para>The read size doesn't have a big performance effect on Unix, unless you set its value quite small. At that point, it causes a detectable slowdown. For this reason, it defaults to 2048 and can't be set lower than 1024.</para>
-</sect3>
-
-
-
-<sect3 role="" label="B.2.2.9" id="appb-SECT-2.2.9">
-<title>read prediction </title>
-
-
-<para>
-<indexterm id="appb-idx-959766-0"><primary>read prediction, testing</primary></indexterm>Besides being counterintuitive, this option is also obsolete. It enables Samba to read ahead on files opened read only by the clients. The option is disabled in Samba 2.0 (and late 1.9) Because it interferes with opportunistic locking.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="B.2.3" id="appb-SECT-2.3">
-<title>Other Samba Options</title>
-
-
-<para>
-<indexterm id="appb-idx-959775-0" class="startofrange"><primary>Samba</primary><secondary>performance tuning</secondary><tertiary>other options for</tertiary></indexterm>
-<indexterm id="appb-idx-959775-1" class="startofrange"><primary>performance tuning</primary><secondary>other options for</secondary></indexterm>
-<indexterm id="appb-idx-959775-2" class="startofrange"><primary>configuring Samba</primary><secondary>performance tuning</secondary><tertiary>other options for</tertiary></indexterm>The following Samba options will affect performance if they're set incorrectly, much like the debug level. They're mentioned here so you will know what to look out for:</para>
-
-
-<variablelist>
-<varlistentry><term>
-<indexterm id="appb-idx-960358-0"><primary>hidden files</primary><secondary>options for</secondary></indexterm><literal>hide files</literal></term>
-<listitem><para>Providing a pattern to identify files hidden by the Windows client <literal>hide</literal> <literal>files</literal> will result in any file matching the pattern being passed to the client with the DOS hidden attribute set. It requires a pattern match per file when listing directories, and slows the server noticeably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>lpq cache time</literal>
-<indexterm id="appb-idx-960359-0"><primary>lpq cache time option</primary></indexterm></term>
-<listitem><para>If your <literal>lpq</literal> (printer queue contents) command takes a long time to complete, you should increase <literal>lpq</literal> <literal>cache</literal> <literal>time</literal> to a value higher than the actual time required for <literal>lpq</literal> to execute, so as to keep Samba from starting a new query when one's already running. The default is 10 seconds, which is reasonable.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>strict locking</literal>
-<indexterm id="appb-idx-960360-0"><primary>strict locking option</primary></indexterm></term>
-<listitem><para>Setting the <literal>strict</literal> <literal>locking</literal> option causes Samba to check for locks on every access, not just when asked to by the client. The option is primarily a bug-avoidance feature, and can prevent ill-behaved DOS and Windows applications from corrupting shared files. However, it is slow and should typically be avoided.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>strict sync</literal>
-<indexterm id="appb-idx-960361-0"><primary>strict sync option</primary></indexterm></term>
-<listitem><para>Setting <literal>strict</literal> <literal>sync</literal> will cause Samba to write each packet to disk and wait for the write to complete whenever the client sets the sync bit in a packet. Windows 98 Explorer sets the bit in all packets transmitted, so if you turn this on, anyone with Windows 98 will think Samba servers are horribly slow.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>sync always</literal>
-<indexterm id="appb-idx-960362-0"><primary>sync always option</primary></indexterm></term>
-<listitem><para>Setting <literal>sync</literal> <literal>always</literal> causes Samba to flush every write to disk. This is good if your server crashes constantly, but the performance costs are immense. SMB servers normally use oplocks and automatic reconnection to avoid the ill effects of crashes, so setting this option is not normally necessary.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="appb-idx-960363-0"><primary>wide links option</primary></indexterm><literal>wide links</literal></term>
-<listitem><para>Turning off <literal>wide</literal> <literal>links</literal> prevents Samba from following symbolic links in one file share to files that are not in the share. It is turned on by default, since following links in Unix is not a security problem. Turning it off requires extra processing on every file open. If you do turn off wide links, be sure to turn on <literal>getwd</literal> <literal>cache</literal> to cache some of the required data.</para>
-
-
-<para>There is also a <literal>follow</literal> <literal>symlinks</literal> option that can be turned off to prevent following any symbolic links at all. However, this option does not pose a performance problem.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="appb-idx-960364-0"><primary>getwd cache option</primary></indexterm><literal>getwd cache</literal></term>
-<listitem><para>This option caches the path to the current directory, avoiding long tree-walks to discover it. It's a nice performance improvement on a printer server or if you've turned off <literal>wide</literal> <literal>links</literal>.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="B.2.4" id="appb-SECT-2.4">
-<title>Our Recommendations </title>
-
-
-<para>
-<indexterm id="appb-idx-959782-0"><primary>performance tuning</primary><secondary>recommended enhancements</secondary></indexterm>Here's an <filename>smb.conf</filename> file that incorporates the recommended performance enhancements so far. Comments have been added on the right side.</para>
-
-
-<programlisting>[global]
- log level = 1 # Default is 0
- socket options = TCP_NODELAY IPTOS_LOWDELAY
- read raw = yes # Default
- write raw = yes # Default
- oplocks = yes # Default
- max xmit = 65535 # Default
- dead time = 15 # Default is 0
- getwd cache = yes
- lpq cache = 30
-[okplace]
- veto oplock files = this/that/theotherfile
-[badplace]
- oplocks = no</programlisting>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="B.3" id="appb-22511">
-<title>Sizing Samba Servers</title>
-
-
-<para>
-<indexterm id="appb-idx-959783-0" class="startofrange"><primary>Samba server</primary><secondary>sizing</secondary></indexterm>
-<indexterm id="appb-idx-959783-1" class="startofrange"><primary>sizing Samba servers</primary></indexterm>Sizing is a way to prevent bottlenecks before they occur. The preferred way to do this is to know how many requests per second or how many kilobytes per second the clients will need, and ensure that all the components of the server provide at least that many.</para>
-
-
-<sect2 role="" label="B.3.1" id="appb-SECT-3.1">
-<title>The Bottlenecks</title>
-
-
-<para>
-<indexterm id="appb-idx-959791-0" class="startofrange"><primary>bottlenecks</primary></indexterm>The <indexterm id="appb-idx-959799-0"><primary>bottlenecks</primary><secondary>types of</secondary></indexterm>three primary bottlenecks you should worry about are CPU, disk I/O, and the network. For most machines, CPUs are rarely a bottleneck. A single Sun SPARC 10 CPU can start (and complete) between 700 and 800 I/O operations a second, giving approximately 5,600 to 6,400KB/s of throughput when the data averages around 8KBs (a common buffer size). A single Intel Pentium 133 can do less only because of somewhat slower cache and bus interfaces, not due to lack of CPU power. Purpose-designed Pentium servers, like some Compaq servers, will be able to start 700 operations per CPUs, on up to four CPUs.</para>
-
-
-<para>Too little memory, on the other hand, can easily be a bottleneck; each Samba process will use between 600 and 800KB on Intel Linux, and more on RISC CPUs. Having less will cause an increase in virtual memory paging and therefore a performance hit. On Solaris, where it has been measured, <emphasis>smbd</emphasis> will use 2.6 MB for program and shared libraries, plus 768KB for each connected client. <emphasis>nmbd</emphasis> occupies 2.1 MB, plus 496KB extra for its (single) auxiliary process.</para>
-
-
-<para>Hard disks will always bottleneck at a specific number of I/O operations per second: for example, each 7200 RPM SCSI disk is capable of performing 70 operations per second, for a throughput of 560KB/s; a 4800 RPM disk will perform fewer than 50, for a throughput of 360KB/s. A single IDE disk will do still fewer. If the disks are independent, or striped together in a RAID 1 configuration, they will each peak out at 400 to 560KB/s and will scale linearly as you add more. Note that this is true only of RAID 1. RAID levels other than 1 (striping) add extra overhead.</para>
-
-
-<para>Ethernets (and other networks) are obvious bottleneck: a 10 Mb/s (mega<emphasis>bits</emphasis>/second) Ethernet will handle around 1100KB/s (kilo<emphasis>bytes</emphasis>/s) using 1500-byte packets A 100 Mb/s Fast Ethernet will bottleneck below 65,000KB/s with the same packet size. FDDI, at 155 Mb/s will top out at approximately 6,250KB/s, but gives good service at even 100 percent load and transmits much larger packets (4KB).</para>
-
-
-<para>ATM should be much better, but as of the writing of this book it was too new to live up to its potential; it seems to deliver around 7,125 Mb/s using 9KB packets.</para>
-
-
-<para>Of course, there can be other bottlenecks: more than one IDE disk per controller is not good, as are more than three 3600 SCSI-I disks per slow/narrow controller, or more than three 7200 SCSI-II disks per SCSI-II fast/wide controller. RAID 5 is also slow, as it requires twice as many writes as independent disks or RAID 1.</para>
-
-
-<para>After the second set of Ethernets and the second disk controller, start worrying about bus bandwidth, especially if you are using ISA/EISA buses.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="B.3.2" id="appb-SECT-3.2">
-<title>Reducing Bottlenecks </title>
-
-
-<para>
-<indexterm id="appb-idx-959800-0" class="startofrange"><primary>bottlenecks</primary><secondary>reducing</secondary></indexterm>From the information above we can work out a model that will tell us the maximum capability of a given machine. The data is mostly taken from <indexterm id="appb-idx-959815-0"><primary>Wong, Brian</primary></indexterm>
-<indexterm id="appb-idx-959815-1"><primary>resources for further information</primary><secondary>Solaris servers</secondary></indexterm>Brian Wong's <citetitle>Configuration and Capacity Planning for Solaris Servers</citetitle>,<citetitle>
-<footnote label="1" id="appb-pgfId-951214">
-
-
-<para>See Wong. Brian L, <emphasis>Configuration and Capacity Planning for Solaris Servers</emphasis>, Englewood Cliffs, NJ (Sun/Prentice-Hall), 1997, ISBN 0-13-349952-9.</para>
-
-
-</footnote></citetitle> so there is a slight Sun bias to our examples.</para>
-
-
-<para>A word of warning: this is not a complete model. Don't assume that this model will predict every bottleneck or even be within 10 percent in its estimates. A model to predict performance instead of one to warn you of bottlenecks would be much more complex and would contain rules like "not more than three disks per SCSI chain". (A good book on real models is Raj Jain's <citetitle>The Art of Computer Systems Performance Analysis</citetitle>.<footnote label="2" id="appb-pgfId-951230">
-
-
-<para>See Jain, Raj, <emphasis>The Art of Computer Systems Performance Analysis</emphasis>, New York, NY (John Wiley and Sons), 1991, ISBN 0-47-150336-3.</para>
-
-
-</footnote>) With that warning, we present the system in <link linkend="appb-98866">Figure 2.2</link>.</para>
-
-
-<figure label="B.2" id="appb-98866">
-<title>Data flow through a Samba server, with possible bottlenecks</title>
-
-<graphic width="502" depth="185" fileref="figs/sam.ab02.gif"></graphic>
-</figure>
-
-<para>The flow of data should be obvious. For example, on a read, data flows from the disk, across the bus, through or past the CPU, and to the network interface card (NIC). It is then broken up into packets and sent across the network. Our strategy here is to follow the data through the system and see what bottlenecks will choke it off. Believe it or not, it's rather easy to make a set of tables that list the maximum performance of common disks, CPUs, and network cards on a system. So that's exactly what we're going to do.</para>
-
-
-<para>Let's take a concrete example: a Linux Pentium 133 MHz machine with a single 7200 RPM data disk, a PCI bus, and a 10-Mb/s Ethernet card. This is a perfectly reasonable server. We start with <link linkend="appb-78077">Table 2.2</link>, which describes the hard drive—the first potential bottleneck in the system.</para>
-
-
-<table label="B.2" id="appb-78077">
-<title>Disk Throughput </title>
-
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Disk RPM</para></entry>
-
-<entry colname="col2"><para>I/O Operations/second</para></entry>
-
-<entry colname="col3"><para>KB/second</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>7200</para></entry>
-
-<entry colname="col2"><para>70</para></entry>
-
-<entry colname="col3"><para>560</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>4800</para></entry>
-
-<entry colname="col2"><para>60</para></entry>
-
-<entry colname="col3"><para>480</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>3600</para></entry>
-
-<entry colname="col2"><para>40</para></entry>
-
-<entry colname="col3"><para>320</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Disk throughput is the number of kilobytes of data that a disk can transfer per second. It is computed from the number of 8KB I/O operations per second a disk can perform, which in turn is strongly influenced by disk RPM and bit density. In effect, the question is: how much data can pass below the drive heads in one second? With a single 7200 RPM disk, the example server will give us 70 I/O operations per second at roughly 560KB/s.</para>
-
-
-<para>The second possible bottleneck is the CPU. The data doesn't actually flow through the CPU on any modern machines, so we have to compute throughput somewhat indirectly.</para>
-
-
-<para>The CPU has to issue I/O requests and handle the interrupts coming back, then transfer the data across the bus to the network card. From much past experimentation, we know that the overhead that dominates the processing is consistently in the filesystem code, so we can ignore the other software being run. We compute the throughput by just multiplying the (measured) number of file I/O operations per second that a CPU can process by the same 8K average request size. This gives us the results shown in <link linkend="appb-42029">Table 2.3</link>.</para>
-
-
-<table label="B.3" id="appb-42029">
-<title>CPU Throughput </title>
-
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>CPU</para></entry>
-
-<entry colname="col2"><para>I/O Operations/second</para></entry>
-
-<entry colname="col3"><para>KB/second</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Intel Pentium 133</para></entry>
-
-<entry colname="col2"><para>700</para></entry>
-
-<entry colname="col3"><para>5,600</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Dual Pentium 133</para></entry>
-
-<entry colname="col2"><para>1,200</para></entry>
-
-<entry colname="col3"><para>9,600</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Sun SPARC II</para></entry>
-
-<entry colname="col2"><para>660</para></entry>
-
-<entry colname="col3"><para>5,280</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Sun SPARC 10</para></entry>
-
-<entry colname="col2"><para>750</para></entry>
-
-<entry colname="col3"><para>6,000</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Sun Ultra 200</para></entry>
-
-<entry colname="col2"><para>2,650</para></entry>
-
-<entry colname="col3"><para>21,200</para></entry>
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Now we put the disk and the CPU together: in the Linux example, we have a single 7200 RPM disk, which can give us 560KB/s, and a CPU capable of starting 700 I/O operations, which could give us 5600KB/s. So far, as you would expect, our bottleneck is clearly going to be the hard disk.</para>
-
-
-<para>The last potential bottleneck is the network. If the network speed is below 100 Mb/s, the bottleneck will be the network speed. After that, the design of the network card is more likely to slow us down. <link linkend="appb-67604">Table 2.4</link> shows us the average throughput of many types of data networks. Although network speed is conventionally measured in bits per second, <link linkend="appb-67604">Table 2.4</link> lists bytes per second to make comparison with the disk and CPU (<link linkend="appb-78077">Table 2.2</link> and <link linkend="appb-42029">Table 2.3</link>) easier.</para>
-
-
-
-<table label="B.4" id="appb-67604">
-<title>Network Throughput </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Network Type</para></entry>
-
-<entry colname="col2"><para>KB/second</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para> ISDN</para></entry>
-
-<entry colname="col2"><para> 16</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para> T1</para></entry>
-
-<entry colname="col2"><para> 197</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para> Ethernet 10m</para></entry>
-
-<entry colname="col2"><para> 1,113</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para> Token ring</para></entry>
-
-<entry colname="col2"><para> 1,500</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para> FDDI</para></entry>
-
-<entry colname="col2"><para> 6,250</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para> Ethernet 100m</para></entry>
-
-<entry colname="col2"><para> 6,500<footnote label="3" id="appb-pgfId-960131">
-
-
-<para>These will increase. For example, Crays, Sun Ultras, and DEC/Compaq Alphas already have bettered these figures.</para>
-
-
-</footnote></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para> ATM 155</para></entry>
-
-<entry colname="col2"><para> 7,125a</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>In the running example, we have a bottleneck at 560KB/s due to the disk. <link linkend="appb-67604">Table 2.4</link> shows us that a standard 10 megabit per second Ethernet (1,113KB/s) is far faster than the disk. Therefore, the hard disk is still the limiting factor. (This scenario, by the way, is very common.) Just by looking at the tables, we can predict that small servers won't have CPU problems, and that large ones with multiple CPUs will support striping and multiple Ethernets long before they start running out of CPU power. This, in fact, is exactly what happens.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="B.3.3" id="appb-SECT-3.3">
-<title>Practical Examples</title>
-
-
-<para>An example from <emphasis>Configuration and Capacity Planning for Solaris Servers</emphasis> (Wong) shows that a dual-processor SPARCstation 20/712 with four Ethernets and six 2.1 GB disks will spend all its time waiting for the disks to return some data. If it was loaded with disks (Brian Wong suggests as many as 34 of them), it would still be held below 1,200KB/s by the Ethernet cards. To get the performance the machine is capable of, we would need to configure multiple Ethernets, 100 Mbps Fast Ethernet, or 155 Mbps FDDI.</para>
-
-
-<para>The progression you'd work through to get that conclusion looks something like <link linkend="appb-26613">Table 2.5</link>.</para>
-
-
-<table label="B.5" id="appb-26613">
-<title>Tuning a Medium-Sized Server </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Machine</para></entry>
-
-<entry colname="col2"><para>Disk Throughput</para></entry>
-
-<entry colname="col3"><para>CPU Throughput</para></entry>
-
-<entry colname="col4"><para>Network Throughput</para></entry>
-
-<entry colname="col5"><para>Actual Throughput</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Dual SPARC 10, 1 disk</para></entry>
-
-<entry colname="col2"><para>560</para></entry>
-
-<entry colname="col3"><para>6000</para></entry>
-
-<entry colname="col4"><para>1,113</para></entry>
-
-<entry colname="col5"><para>560</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Add 5 more disks</para></entry>
-
-<entry colname="col2"><para>3,360</para></entry>
-
-<entry colname="col3"><para>6000</para></entry>
-
-<entry colname="col4"><para>1,113</para></entry>
-
-<entry colname="col5"><para>1,113</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Add 3 more Ethernets</para></entry>
-
-<entry colname="col2"><para>3,360</para></entry>
-
-<entry colname="col3"><para>16000</para></entry>
-
-<entry colname="col4"><para>4,452</para></entry>
-
-<entry colname="col5"><para>3,360</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Change to using a 20-disk array</para></entry>
-
-<entry colname="col2"><para>11,200</para></entry>
-
-<entry colname="col3"><para>6000</para></entry>
-
-<entry colname="col4"><para>4,452</para></entry>
-
-<entry colname="col5"><para>4,452</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Use dual 100 Mbps ether</para></entry>
-
-<entry colname="col2"><para>11,200</para></entry>
-
-<entry colname="col3"><para>6000</para></entry>
-
-<entry colname="col4"><para>13,000</para></entry>
-
-<entry colname="col5"><para>11,200</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Initially, the bottleneck is the disk with only 560 MB/s of throughput available. Our solution is to add five more disks. This gives us more throughput on the disks than on the Ethernet, so then the Ethernet becomes the problem. Consequently, as we continue to expand, we go back and forth several times between these two. As you add disks, CPUs, and network cards, the bottleneck moves. Essentially, the strategy is to add more equipment to try to avoid each bottleneck until you reach your target performance, or (unfortunately) you either can't add any more or run out of money.</para>
-
-
-<para>Our experience bears out this kind of calculation; a large SPARC 10 file server that one author maintained was quite capable of saturating an Ethernet plus about a third of an FDDI ring when using two processors. It did nearly as well with a single processor, albeit with a fast operating system and judicious over-optimization.</para>
-
-
-<para>The same process applies to other brands of purpose-designed servers. We found the same rules applied to DECstation 2100s as to the newest Alphas or Compaqs, old MIPS 3350s and new SGI O2s. In general, a machine offering multi-CPU server configurations will have enough bus bandwidth and CPU power to reliably bottleneck on hard disk I/O when doing file service. As one would hope, considering the cost!</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="B.3.4" id="appb-SECT-3.4">
-<title>How Many Clients can Samba Handle?</title>
-
-
-<para>Well, that depends entirely on how much data each user consumes. A small server with three SCSI-1 disks, which can serve about 960KB/s of data, will support between 36 and 80 clients in an ordinary office environment where they are typically loading, and saving equal-sized spreadsheets or word processing documents (36 clients × 2.3 transfers/second × 12k file 1 MB/s).</para>
-
-
-<para>On the same server in a development environment with programmers running a fairly heavy edit-compile-test cycle, one can easily see requests for 1 MB/s, limiting the server to 25 or fewer clients. To take this a bit further, an imaging system whose clients each require 10 MB/s will perform poorly no matter how big a server is if they're all on a 10 MB/s Ethernet. And so on.</para>
-
-
-<para>If you don't know how much data an average user consumes, you can size your Samba servers by patterning them after existing NFS, Netware, or LAN Manager servers. You should be especially careful that the new servers have as many disks and disk controllers as the ones you've copied. This technique is appropriately called "punt and hope."</para>
-
-
-<para>If you know how many clients an existing server can support, you're in <emphasis>much</emphasis> better shape. You can analyze the server to see what its maximum capacity is and use that to estimate how much data they must be demanding. For example, if serving home directories to 30 PCs from a PC server with two IDE disks is just too slow, and 25 clients is about right, then you can safely assume you're bottlenecked on Ethernet I/O (approximately 375KB) rather than disk I/O (up to 640KB). If so, you can then conclude that the clients are demanding 15 (that is, 375/25)KB/s on average.</para>
-
-
-<para>Supporting a new lab of 75 clients will mean you'll need 1,125KB/s, spread over multiple (preferably three) Ethernets, and a server with at least three 7200 RPM disks and a CPU capable of keeping up. These requirements can be met by a Pentium 133 or above with the bus architecture to drive them all at full speed (e.g., PCI).</para>
-
-
-<para>A custom-built PC server or a multiprocessor-capable workstation like a Sun Sparc, a DEC/Compaq Alpha, an SGI, or the like, would scale up easier, as would a machine with fast Ethernet, plus a switching hub to drive the client machines on individual 10 MB/s Ethernets.</para>
-
-
-<sect3 role="" label="B.3.4.1" id="appb-SECT-3.4.1">
-<title>How to guess</title>
-
-
-<para>If you have no idea at all what you need, the best thing is to try to guess based on someone else's experience. Each individual client machine can average from less than 1 I/O per second (normal PC or Mac used for sales/accounting) to as much as 4 (fast workstation using large applications). A fast workstation running a compiler can happily average 3-4 MB/s in data transfer requests, and an imaging system can demand even more.</para>
-
-
-<para>Our recommendation? Spy on someone with a similar configuration and try to estimate their bandwidth requirements from their bottlenecks and the volume of the screams from their users. We also recommend Brian Wong's <citetitle>Configuration and Capacity Planning for Solaris Servers</citetitle>. While he uses Sun Solaris foremost in his examples, his bottlenecks are disks and network cards, which are common among all the major vendors. His tables for FTP servers also come very close to what we calculated for Samba servers, and make a good starting point.<indexterm id="appb-idx-959809-0" class="endofrange" startref="appb-idx-959800-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="B.3.5" id="appb-90359">
-<title>Measurement Forms</title>
-
-
-<para>
-<indexterm id="appb-idx-959816-0"><primary>measurement forms</primary></indexterm><link linkend="appb-82208">Table 2.6</link> and <link linkend="appb-34846">Table 2.7</link> are empty tables that you can use for copying and recording data. The bottleneck calculation in the previous example can be done in a spreadsheet, or manually with <link linkend="appb-51003">Table 2.8</link>. If Samba is as good as or better than FTP, and if there aren't any individual test runs that are much different from the average, you have a well-configured system. If loopback isn't much faster than anything else, you have a problem with your TCP/IP software. If both FTP and Samba are slow, you probably have a problem with your networking: a faulty Ethernet card will produce this, as will accidentally setting an Ethernet card to half-duplex when it's not connected to a half-duplex hub. Remember that CPU and disk speeds are commonly measured in bytes, network speeds in bits.</para>
-
-
-<para>We've included columns for both bytes and bits in the tables. In the last column, we compare results to 10 Mb/s because that's the speed of a traditional Ethernet.</para>
-
-
-<table label="B.6" id="appb-82208">
-<title>Ethernet Interface to Same Host: FTP </title>
-
-<tgroup cols="6">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<colspec colnum="6" colname="col6"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Run No</para></entry>
-
-<entry colname="col2"><para>Size in Bytes</para></entry>
-
-<entry colname="col3"><para>Time (sec)</para></entry>
-
-<entry colname="col4"><para>Bytes/sec</para></entry>
-
-<entry colname="col5"><para>Bits/sec</para></entry>
-
-<entry colname="col6"><para>% of 10 Mb/s</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>1</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>3</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>4</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>5</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Average:</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Deviation:</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<table label="B.7" id="appb-34846">
-<title>Ethernet Interface to Same Host: FTP </title>
-
-<tgroup cols="6">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<colspec colnum="6" colname="col6"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Run No</para></entry>
-
-<entry colname="col2"><para>Size in Bytes</para></entry>
-
-<entry colname="col3"><para>Time, sec</para></entry>
-
-<entry colname="col4"><para>Bytes/sec</para></entry>
-
-<entry colname="col5"><para>Bits/sec</para></entry>
-
-<entry colname="col6"><para>% of 10 Mb/s</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>1</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>3</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>4</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>5</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Average:</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Deviation:</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<table label="B.8" id="appb-51003">
-<title>Bottleneck Calculation Table</title>
-
-<tgroup cols="7">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<colspec colnum="6" colname="col6"/>
-<colspec colnum="7" colname="col7"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>CPU</para></entry>
-
-<entry colname="col2"><para>Throughput</para></entry>
-
-<entry colname="col3"><para>of Disks</para></entry>
-
-<entry colname="col4"><para>Disk Throughput</para></entry>
-
-<entry colname="col5"><para>Number of Networks</para></entry>
-
-<entry colname="col6"><para>Network Throughput</para></entry>
-
-<entry colname="col7"><para>Total Throughput</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-<entry colname="col7"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-<entry colname="col7"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-<entry colname="col7"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-<entry colname="col7"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-<entry colname="col7"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-<entry colname="col7"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-<entry colname="col7"></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>In <link linkend="appb-51003">Table 2.8</link>:</para>
-
-
-<itemizedlist>
-
-<listitem><para>CPU throughput = (KB/second from <link linkend="ch06-89804">Figure 6.5</link>) × (number of CPUs)</para></listitem>
-
-<listitem><para>Disk throughput = (KB/second from <link linkend="ch06-48609">Figure 6.4</link>) × (number of disks)</para></listitem>
-
-<listitem><para>Network throughput = (KB/second from <link linkend="ch06-71393">Figure 6.6</link>) × (number of networks)</para></listitem>
-
-<listitem><para>Total throughput = min (Disk, CPU, and Network throughput)</para></listitem>
-
-</itemizedlist>
-
-<para>A typical test, in this case for an FTP <literal>get</literal>, would be entered as in <link linkend="appb-37370">Table 2.9</link></para>
-
-
-<table label="B.9" id="appb-37370">
-<title>Ethernet Interface to Same Host: FTP </title>
-
-<tgroup cols="6">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<colspec colnum="6" colname="col6"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Run No</para></entry>
-
-<entry colname="col2"><para>Size in Bytes</para></entry>
-
-<entry colname="col3"><para>Time, sec</para></entry>
-
-<entry colname="col4"><para>Bytes/sec</para></entry>
-
-<entry colname="col5"><para>Bits/sec</para></entry>
-
-<entry colname="col6"><para>% of 10 Mb/s</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>1</para></entry>
-
-<entry colname="col2"><para>1812898</para></entry>
-
-<entry colname="col3"><para>2.3</para></entry>
-
-<entry colname="col4"><para>761580</para></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"><para>2.3</para></entry>
-
-<entry colname="col4"><para>767820</para></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>3</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"><para>2.4</para></entry>
-
-<entry colname="col4"><para>747420</para></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>4</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"><para>2.3</para></entry>
-
-<entry colname="col4"><para>760020</para></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>5</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"><para>2.3</para></entry>
-
-<entry colname="col4"><para>772700</para></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Average:</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"><para>2.32</para></entry>
-
-<entry colname="col4"><para>777310</para></entry>
-
-<entry colname="col5"><para>6218480</para></entry>
-
-<entry colname="col6"><para>62</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Deviation:</para></entry>
-
-<entry colname="col2"></entry>
-
-<entry colname="col3"><para>0.04</para></entry>
-
-<entry colname="col4"></entry>
-
-<entry colname="col5"></entry>
-
-<entry colname="col6"></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>The Sparc example we used earlier would look like <link linkend="SAMBA-AP-B-TBL-10">Table 2.10</link>.</para>
-
-
-<table label="B.10" id="SAMBA-AP-B-TBL-10">
-<title>Sparc 20 Example, Redux</title>
-
-<tgroup cols="7">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<colspec colnum="6" colname="col6"/>
-<colspec colnum="7" colname="col7"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>CPU</para></entry>
-
-<entry colname="col2"><para>CPU Throughput</para></entry>
-
-<entry colname="col3"><para>Number of Disks</para></entry>
-
-<entry colname="col4"><para>Disk Throughput</para></entry>
-
-<entry colname="col5"><para>Number of Networks</para></entry>
-
-<entry colname="col6"><para>Network Throughput</para></entry>
-
-<entry colname="col7"><para>Total Throughput</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"><para>6,000</para></entry>
-
-<entry colname="col3"><para>1</para></entry>
-
-<entry colname="col4"><para>560</para></entry>
-
-<entry colname="col5"><para>1 10base2</para></entry>
-
-<entry colname="col6"><para>1,113</para></entry>
-
-<entry colname="col7"><para>560</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"><para>6,000</para></entry>
-
-<entry colname="col3"><para>6</para></entry>
-
-<entry colname="col4"><para>3,360</para></entry>
-
-<entry colname="col5"><para>1</para></entry>
-
-<entry colname="col6"><para>1,113</para></entry>
-
-<entry colname="col7"><para>1,113</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"><para>6,000</para></entry>
-
-<entry colname="col3"><para>6</para></entry>
-
-<entry colname="col4"><para>3,360</para></entry>
-
-<entry colname="col5"><para>4 10base2</para></entry>
-
-<entry colname="col6"><para>4,452</para></entry>
-
-<entry colname="col7"><para>3,360</para></entry>
-
-</row>
-
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"><para>6,000</para></entry>
-
-<entry colname="col3"><para>20</para></entry>
-
-<entry colname="col4"><para>11,200</para></entry>
-
-<entry colname="col5"><para>4</para></entry>
-
-<entry colname="col6"><para>4,452</para></entry>
-
-<entry colname="col7"><para>4,452</para></entry>
-
-</row>
-
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"><para>6,000</para></entry>
-
-<entry colname="col3"><para>20</para></entry>
-
-<entry colname="col4"><para>11,200</para></entry>
-
-<entry colname="col5"><para>2 100base2</para></entry>
-
-<entry colname="col6"><para>13,000</para></entry>
-
-<entry colname="col7"><para>11,200</para></entry>
-
-</row>
-
-
-</tbody>
-</tgroup>
-</table>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-</appendix>
+++ /dev/null
-<appendix label="C" id="SAMBA-AP-C">
-<title>Samba Configuration Option Quick Reference</title>
-
-
-
-
-<para>The following pages list each of the Samba configuration
-options. If an option is applicable only to the global section,
-"[global]" will appear before its name. Any lists mentioned are space
-separated, except where noted. A glossary of terms follows the
-options.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="C.1" id="appc-SECT-1">
-<title>Configuration Options</title>
-
-
-<refentry id="appc-refentry-1">
-<refmeta>
-<refmiscinfo class="allowable values">user list</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>admin users = user list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of users who will be granted root permissions on the share by Samba.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-2">
-<refmeta>
-<refmiscinfo class="allowable values">any</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>allow hosts = host list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>hosts allow</literal>. List of machines that may connect to a share.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-3">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>alternate permissions = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Obsolete. Has no effect in Samba 2. Files will be shown as read-only if the owner can't write them. In Samba 1.9 and earlier, setting this option would set the DOS filesystem read-only attribute on any file the user couldn't read. This in turn required the <literal>delete readonly</literal> option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-6">
-<refmeta>
-<refmiscinfo class="allowable values">any shares</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] auto services = share list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of shares that will always appear in browse lists. A synonym is <literal>preload</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-7">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>available = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to NO, denies access to a share. Doesn't affect browsing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-8">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] bind interfaces only = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, shares and browsing will be provided only on interfaces in an interfaces list (see <literal>interfaces</literal>). New in Samba 1.9.18. If you set this option to YES, be sure to add 127.0.0.1 to the interfaces list to allow <emphasis>smbpasswd</emphasis> to connect to the local machine to change passwords. This is a convienence option; it does not improve security.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-9">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>browsable = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allows a share to be announced in browse lists.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-10">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>blocking locks = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, honors byte range lock requests with time limits for queuing the request and retrying it until the time period expires. New in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-11">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] browse list = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Turns on/off <literal>browse</literal> <literal>list</literal> from this server. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-12">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] case sensitive = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, uses exactly the case the client supplied when trying to resolve a filename. If NO, matches either upper- or lowercase name. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-13">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] case sig names = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>case sensitive</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-14">
-<refmeta>
-<refmiscinfo class="allowable values">positive number</refmiscinfo>
-<refmiscinfo class="default">60</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] change notify timeout = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the number of seconds between checks when a client asks for notification of changes in a directory. Introduced in Samba 2.0 to limit the performance cost of the checks. Avoid lowering.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-15">
-<refmeta>
-<refmiscinfo class="allowable values">ISO8859-1, ISO8859-2, ISO8859-5, KOI8-R</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>character set = name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set, translates from DOS code pages to the Western European (ISO8859-1), Eastern European (ISO8859-2), Russian Cyrillic (ISO8859-5), or Alternate Russian (KOI8-R) character set. The <literal>client code page</literal> must be set to 850.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-16">
-<refmeta>
-<refmiscinfo class="allowable values">See <link linkend="ch08-20815">Table 8.4</link></refmiscinfo>
-<refmiscinfo class="default">437 (US MS-DOS)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>client code page = name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the DOS code page explicitly, overriding any previous <literal>valid chars</literal> settings. Examples of values are 850 for European, 437 is the US standard, and 932 for Japanese Shift-JIS. Introduced in Samba 1.9.19.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-17">
-<refmeta>
-<refmiscinfo class="allowable values">euc, cap, hex, hexN, sjis, j8bb, j8bj, jis8, j8bh, j8@b, j8@j, j8@h, j7bb, j7bj, jis7, j7bh, j7@b, j7@j, j7@h, jubb, jubj, junet, jubh, ju@b, ju@j, ju@h</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>coding system = code</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the coding system used, notably for Kanji. This is employed for filenames and should correspond to the code page in use. The <literal>client code page</literal> option must be set to 932 (Japanese Shift-JIS). Introduced in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-18">
-<refmeta>
-<refmiscinfo class="allowable values">a text string or NULL</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>comment = text</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the comment that appears beside a share in a NET VIEW or the details list of a Microsoft directory window. See also the <literal>server string</literal> configuration option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-19">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] config file = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Selects an additional Samba configuration file to read instead of the current one. Used to relocate the configuration file, or used with %-variables to select custom configuration files for some users or machines.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-20">
-<refmeta>
-<refmiscinfo class="allowable values">existing section's name</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>copy = section name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Copies the configuration of a previously seen share into the share where it appears. Used with %-variables to select custom configurations for machines, architectures and users. The copied section must be earlier in the configuration file. Copied options are of lesser priority than those explicitly listed in the section.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-21">
-<refmeta>
-<refmiscinfo class="allowable values">octal permission bits, 0-0777</refmiscinfo>
-<refmiscinfo class="default">0744</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>create mask = octal value</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Also called <literal>create mode</literal>. Sets the maximum allowable permissions for new files (e.g., 0755). See also <literal>directory mask</literal>. To require certain permissions to be set, see <literal>force create mask/force directory mask</literal>. This option stopped affecting directories in Samba 1.9.17, and the default value changed in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-22">
-<refmeta>
-<refmiscinfo class="allowable values">octal permission bits, 0-0777</refmiscinfo>
-<refmiscinfo class="default">0744</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>create mode = octal permission bits</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>create mask</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-23">
-<refmeta>
-<refmiscinfo class="allowable values">minutes</refmiscinfo>
-<refmiscinfo class="default">0 </refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] deadtime = minutes</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>The time in minutes before an unused connection will be terminated. Zero means forever. Used to keep clients from tying up server resources forever. If used, clients will have to auto-reconnect after minutes of inactivity. See also <literal>keepalive</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-24">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] debug level = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the logging level used. Values of 3 or more slow Samba noticeably. A synonym is <literal>log level</literal>. Recommended value: 1.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-25">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] debug timestamp = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Timestamps all log messages. Can be turned off when it's not useful (e.g., in debugging). New in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-26">
-<refmeta>
-<refmiscinfo class="allowable values">share name</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] default = name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Also called <literal>default service</literal>. The name of a service (share) to provide if someone requests a service they don't have permission to use or which doesn't exist. As of Samba 1.9.14, the path will be set from the name the client specified, with any "_" characters changed to "/" characters, allowing access to any directory on the Samba server. Use is strongly discouraged.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-27">
-<refmeta>
-<refmiscinfo class="allowable values">LOWER, UPPER</refmiscinfo>
-<refmiscinfo class="default">LOWER</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>default case = case</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the case in which to store new filenames. LOWER indicates mixed case, UPPER indicates uppercase letters.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-28">
-<refmeta>
-<refmiscinfo class="allowable values">share name</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] default service = share name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>default</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-29">
-<refmeta>
-<refmiscinfo class="allowable values">NO, YES</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>delete readonly = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allow delete requests to remove read-only files. This is not allowed in DOS/Windows, but is normal in Unix, which has separate directory permissions. Used with programs like RCS, or with the older <literal>alternate permissions</literal> option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-30">
-<refmeta>
-<refmiscinfo class="allowable values">NO, YES</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>delete veto files = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allow delete requests for a directory containing files or subdirectories the user can't see due to the <literal>veto files</literal> option. If set to NO, the directory will not be deleted and will still contain invisible files.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-31">
-<refmeta>
-<refmiscinfo class="allowable values">host list</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>deny hosts = host list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>A synonym is <literal>hosts deny</literal>. Specifies a list of machines from which to refuse connections or shares.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-32">
-<refmeta>
-<refmiscinfo class="allowable values">shell command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] dfree command = command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>A command to run on the server to return disk free space. Not needed unless the OS command does not work properly.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-33">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>directory = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>path</literal>. A directory provided by a file share, or used by a printer share. Set automatically in the <literal>[homes]</literal> share to user's home directory, otherwise defaults to<filename> /tmp</filename>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-34">
-<refmeta>
-<refmiscinfo class="allowable values">octal value from 0 to 0777</refmiscinfo>
-<refmiscinfo class="default">0755</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>directory mask = octal permission bits</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Also called <literal>directory mode</literal>. Sets the maximum allowable permissions for newly created directories. To require certain permissions be set, see the <literal>force create mask</literal> and <literal>force directory mask</literal> options.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-35">
-<refmeta>
-<refmiscinfo class="allowable values">octal value from 0 to 0777</refmiscinfo>
-<refmiscinfo class="default">0755</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>directory mode = octal permission bits</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>directory mask</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-36">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] dns proxy = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, and if <literal>wins server = YES</literal>, look up hostnames in DNS if they are not found using WINS.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-37">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] domain logons = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allow Windows 95/98 or NT clients to log on to an NT-like domain.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-38">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] domain master = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Become a domain master browser list collector if possible for the entire workgroup/domain.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-39">
-<refmeta>
-<refmiscinfo class="allowable values">comma-separated list of paths</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>dont descend = comma-list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Does not allow a change directory or search in the directories specified. This is a browsing convenience option; it doesn't provide any extra security.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-40">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>dos filetimes = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allow non-owners to change file times if they can write to the file. See also <literal>dos filetime resolution</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-41">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>dos filetime resolution = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Set file times on Unix to match DOS standards (round to next even second). Recommended if using Visual C++ or a PC <emphasis>make</emphasis> program to avoid remaking the programs unnecesarily. Use with the <literal>dos filetimes</literal> option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-42">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] encrypt passwords = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Uses Windows NT-style password encryption. Requires an <filename>smbpasswd</filename> on the Samba server.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-43">
-<refmeta>
-<refmiscinfo class="allowable values">shell command</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>exec = command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym of <literal>preexec</literal>, a command to run as the user just before connecting to the share.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-44">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>fake directory create times = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Bug fix for users of Microsoft <emphasis>nmake</emphasis>. If set, Samba will set directory create times such that <emphasis>nmake</emphasis> won't remake all files every time.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-45">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>fake oplocks = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Return YES whenever a client asks if it can lock a file and cache it locally, but does not enforce lock on the server. Use only for read-only disks, as Samba now supports real <literal>oplocks</literal> and has per-file overrides. See also <literal>oplocks</literal> and <literal>veto oplock files</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-46">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>follow symlinks = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, Samba will follow symlinks in a file share or shares. See the <literal>wide links</literal> option if you want to restrict symlinks to just the current share.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-47">
-<refmeta>
-<refmiscinfo class="allowable values">octal value from 0 to 0777</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>force create mask = octal permission bits</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Provides bits that will be <literal>OR</literal>ed into the permissions of newly created files. Used with the <literal>create mode</literal> configuration option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-48">
-<refmeta>
-<refmiscinfo class="allowable values">octal value from 0 to 0777</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>force create mode = octal permission bits</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>force create mask</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-49">
-<refmeta>
-<refmiscinfo class="allowable values">octal value from 0 to 0777</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>force directory mask = octal permission bits</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Provides bits that will be <literal>OR</literal>ed into the permissions of newly created directories, forcing those bits to be set. Used with <literal>directory mode</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-50">
-<refmeta>
-<refmiscinfo class="allowable values">octal value from 0 to 0777</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>force directory mode = octal permission bits</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>force</literal> <literal>directory</literal> <literal>mask</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-51">
-<refmeta>
-<refmiscinfo class="allowable values">group</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>force group = unix group</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the effective group name assigned to all users accessing a share. Used to override user's normal groups.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-52">
-<refmeta>
-<refmiscinfo class="allowable values">username</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>force user = name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the effective username assigned to all users accessing a share. Discouraged.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-53">
-<refmeta>
-<refmiscinfo class="allowable values">NTFS, FAT, Samba</refmiscinfo>
-<refmiscinfo class="default">NTFS</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>fstype = string</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the filesystem type reported to the client.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-54">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] getwd cache = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Cache current directory for performance. Recommended with the <literal>wide links</literal> option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-55">
-<refmeta>
-<refmiscinfo class="allowable values">unix group</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>group = group</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>An obsolete form of <literal>force group</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-56">
-<refmeta>
-<refmiscinfo class="allowable values">username</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>guest account = user</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the name of the unprivileged Unix account to use for tasks like printing and for accessing shares marked with <literal>guest ok</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-57">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>guest ok = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, passwords are not needed for this share. Synonym of <literal>public</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-58">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>guest only = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Forces user of a share to do so as the guest account. Requires <literal>guest</literal> <literal>ok</literal> or <literal>public</literal> to be <literal>yes</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-59">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>hide dot files = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Treats files beginning with a dot in a share as if they had the DOS/Windows hidden attribute set.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-60">
-<refmeta>
-<refmiscinfo class="allowable values">list of patterns, separated by <literal>/</literal> characters</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>hide files = slash-separated list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of file or directory names to set the DOS hidden attribute on. Names may contain <literal>?</literal> or <literal>*</literal> pattern-characters and <literal>%</literal>-variables. See also <literal>hide</literal> <literal>dot</literal> <literal>files</literal> and <literal>veto</literal> <literal>files</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-61">
-<refmeta>
-<refmiscinfo class="allowable values">NIS map name</refmiscinfo>
-<refmiscinfo class="default">auto.home</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] homedir map = NIS map name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Used with <literal>nis homedir</literal> to locate user's Unix home directory from Sun NIS (not NIS+).</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-62">
-<refmeta>
-<refmiscinfo class="allowable values">list of hostnames</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>hosts allow = host list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym of <literal>allow hosts</literal>, a list of machines that can access a share or shares. If NULL (the default) any machine can access the share unless there is a <literal>hosts deny</literal> option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-63">
-<refmeta>
-<refmiscinfo class="allowable values">list of hostnames</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>hosts deny = host list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym of <literal>deny hosts</literal>, a list of machines that cannot connect to a share or shares.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-64">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] hosts equiv = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Path to a file of trusted machines from which password-less logins are allowed. Strongly discouraged, because Windows/NT users can always override the user name, the only security in this scheme.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-65">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>include = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Include the named file in <filename>smb.conf</filename> at the line where it appears. This option does not understand the variables <literal>%u</literal> (user), <literal>%P</literal> (current share's root directory), or <literal>%S</literal> (current share name), because they are not set at the time the file is read.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-66">
-<refmeta>
-<refmiscinfo class="allowable values">IP addresses separated by spaces</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] interfaces = interface list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the interfaces to which Samba will respond. The default is the machine's primary interface only. Recommended on multihomed machines or to override erroneous addresses and netmasks.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-67">
-<refmeta>
-<refmiscinfo class="allowable values">list of users</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>invalid users = user list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of users that will not be permitted access to a share or shares.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-68">
-<refmeta>
-<refmiscinfo class="allowable values">number of seconds</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] keepalive = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Number of seconds between checks for a crashed client. The default of 0 causes no checks to be performed. Recommended if you want checks more often than every four hours. 3600 (10 minutes) is reasonable. See also <literal>socket options</literal> for another approach.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-69">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">automatic</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] kernel oplocks = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Break oplock when a Unix process accesses an <emphasis>oplocked</emphasis> file, preventing corruption. Set to YES on operating systems supporting this, otherwise set to NO. New in Samba 2.0; supported on SGI, and hopefully soon on Linux and BSD. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-70">
-<refmeta>
-<refmiscinfo class="allowable values">various</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] ldap filter = various</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Options beginning with <literal>ldap</literal> are part of an experimental (circa Samba 2.0) use of the Lightweight Directory Access Protocol (LDAP) general directory/distributed database for user, name, and host information. This option is reserved for future use.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-71">
-<refmeta>
-<refmiscinfo class="allowable values">various</refmiscinfo>
-<refmiscinfo class="default">various</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] ldap port = various</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Options beginning with <literal>ldap</literal> are part of an experimental (circa Samba 2.0) use of the Lightweight Directory Access Protocol (LDAP) general directory/distributed database for user, name, and host information. This option is reserved for future use.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-72">
-<refmeta>
-<refmiscinfo class="allowable values">various</refmiscinfo>
-<refmiscinfo class="default">various</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] ldap root = various</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Options beginning with <literal>ldap</literal> are part of an experimental (circa Samba 2.0) use of the Lightweight Directory Access Protocol (LDAP) general directory/distributed database for user, name, and host information. This option is reserved for future use.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-73">
-<refmeta>
-<refmiscinfo class="allowable values">various</refmiscinfo>
-<refmiscinfo class="default">various</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] ldap server = various</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Options beginning with <literal>ldap</literal> are part of an experimental (circa Samba 2.0) use of the Lightweight Directory Access Protocol (LDAP) general directory/distributed database for user, name, and host information. This option is reserved for future use.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-74">
-<refmeta>
-<refmiscinfo class="allowable values">various</refmiscinfo>
-<refmiscinfo class="default">various</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] ldap suffix = various</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Options beginning with <literal>ldap</literal> are part of an experimental (circa Samba 2.0) use of the Lightweight Directory Access Protocol (LDAP) general directory/distributed database for user, name, and host information. This option is reserved for future use.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-75">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] load printers = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Load all printer names from the system printer capabilities into browse list. Uses configuration options from the <literal>[printers]</literal> section.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-76">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] local master = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Stands for election as the local master browser. See also <literal>domain master</literal> and <literal>os level</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-77">
-<refmeta>
-<refmiscinfo class="allowable values">AUTO, YES, NO</refmiscinfo>
-<refmiscinfo class="default">AUTO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] lm announce = value</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Produce OS/2 SMB broadcasts at an interval specified by the <literal>lm interval</literal> option. YES/NO turns them on/off unconditionally. AUTO causes the Samba server to wait for a LAN Manager announcement from another client before sending one out. Required for OS/2 client browsing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-78">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">60</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] lm interval = seconds</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the time period, in seconds, between OS/2 SMB broadcast announcements.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-79">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default"><emphasis>/usr/local/samba/var/locks</emphasis></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] lock directory = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Set a directory to keep lock files in. The directory must be writable by Samba, readable by everyone.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-80">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>locking = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Perform file locking. If set to NO, Samba will accept lock requests but will not actually lock resources. Recommended only for read-only file systems.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-81">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] log file = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Set name and location of the log file. Allows all %-variables.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-82">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] log level = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>A synonym of <literal>debug level</literal>. Sets the logging level used. Values of 3 or more slow the system noticeably.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-83">
-<refmeta>
-<refmiscinfo class="allowable values">DOS drive name</refmiscinfo>
-<refmiscinfo class="default">None</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] logon drive = drive</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the drive on Windows NT (only) of the <literal>logon path</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-84">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default"><emphasis>\\</emphasis><replaceable>%N </replaceable><emphasis>\</emphasis><replaceable>%U</replaceable></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] logon home = path</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the home directory of a Windows 95/98 or NT Workstation user. Allows <literal>NET</literal> <literal>USE</literal> <literal>H:/HOME</literal> from the command prompt.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-85">
-<refmeta>
-<refmiscinfo class="allowable values">Windows pathname</refmiscinfo>
-<refmiscinfo class="default"><emphasis>\\</emphasis><replaceable>%N </replaceable><emphasis>\</emphasis><replaceable>%U </replaceable><emphasis>\profile</emphasis></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] logon path = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets path to Windows profile directory. This contains <emphasis>USER.MAN</emphasis> and/or <emphasis>USER.DAT</emphasis> profile files and the Windows 95 Desktop, Start Menu, Network Neighborhood, and programs folders.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-86">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] logon script = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets pathname relative to <literal>[netlogin]</literal> share of a DOS/NT script to run on the client at login time. Allows all %-variables.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-87">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualfied Unix shell command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>lppause command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command to pause a print job. Honors the <literal>%p</literal> (printer name) and <literal>%j</literal> (job number) variables.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-88">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualified Unix shell command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>lpresume command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command to resume a paused print job. Honors the <literal>%p</literal> (printer name) and <literal>%j</literal> ( job number) variables.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-89">
-<refmeta>
-<refmiscinfo class="allowable values">number of seconds</refmiscinfo>
-<refmiscinfo class="default">10</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] lpq cache time = seconds</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets how long to keep print queue (<literal>lpq </literal>) status is cached, in seconds.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-90">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualfied Unix shell command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>lpq command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command used to get printer status. Usually initialized to a default value by the <literal>printing</literal> option. Honors the <literal>%p</literal> (printer name) variable.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-91">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualified Unix shell command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>lprm command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command to delete a print job. Usually initialized to a default value by the <literal>printing</literal> option. Honors the <literal>%p</literal> (printer name) and <literal>%j</literal> (job number) variables.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-92">
-<refmeta>
-<refmiscinfo class="allowable values">number of seconds</refmiscinfo>
-<refmiscinfo class="default">604,800</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>machine password timeout = seconds</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the period between (NT domain) machine password changes. Default is 1 week, or 604,800 seconds.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-93">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default"><emphasis>script.out</emphasis></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>magic output = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the output file for the discouraged <literal>magic scripts</literal> option. Default is the script name, followed by the extension <emphasis>.out</emphasis>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-94">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>magic script = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a filename for execution via a shell whenever the file is closed from the client, to allow clients to run commands on the server.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-95">
-<refmeta>
-<refmiscinfo class="allowable values"><emphasis>allowable values:</emphasis> YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>mangle case = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Mangle a name if it is in mixed case.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-96">
-<refmeta>
-<refmiscinfo class="allowable values">list of to-from pairs</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>mangled map = map list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Set up a table of names to remap (e.g., <emphasis>.html</emphasis> to <emphasis>.htm</emphasis>).</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-97">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>mangled names = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets Samba to abbreviate names that are too long or have unsupported characters to the DOS 8.3 style.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-98">
-<refmeta>
-<refmiscinfo class="allowable values">character</refmiscinfo>
-<refmiscinfo class="default">~</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>mangling char = character</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the unique mangling character used in all mangled names.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-99">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">50</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] mangled stack = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the size of a cache of recently-mangled filenames.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-100">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>map aliasname = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Points to a file of Unix group/NT group pairs, one per line. This is used to map NT aliases to Unix group names. See also the configuration options <literal>username</literal> <literal>map</literal> and <literal>map</literal> <literal>groupname</literal>. Introduced in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-101">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>map archive = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, Samba sets the executable-by-user (0100) bit on Unix files if the DOS archive attribute is set. Recommended: if used, the <literal>create mask</literal> must contain the 0100 bit.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-102">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>map hidden = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, sets executable-by-other (0001) bit on Unix files if the DOS hidden attribute is set. If used, the <literal>create mask</literal> option must contain the 0001 bit.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-103">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>map groupname = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Points to a file of Unix group/NT group, one per line. This is used to map NT group names to Unix group names. See also the configuration options <literal>username</literal> <literal>map</literal> and <literal>map</literal> <literal>aliasname</literal>. Introduced in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-104">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>map system = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, Samba sets the executable-by-group (0010) bit on Unix files if the DOS system attribute is set. If used, the <literal>create mask</literal> must contain the 0010 bit.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-105">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">0 (infinity)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>max connections = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Set maximum number of connections allowed to a share from each individual client machine.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-106">
-<refmeta>
-<refmiscinfo class="allowable values">size in MB</refmiscinfo>
-<refmiscinfo class="default">0 (unchanged)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max disk size = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets maximum disk size/free-space size (in megabytes) to return to client. Some clients or applications can't understand large maximum disk sizes.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-107">
-<refmeta>
-<refmiscinfo class="allowable values">size in KB</refmiscinfo>
-<refmiscinfo class="default">5000</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max log size = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the size (in kilobytes) at which Samba will start a new log file. The current log file will be renamed with an <emphasis>.old</emphasis> extension, replacing any previous file with that name.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-108">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">50</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max mux = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the number of simultaneous operations that Samba clients may make. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-109">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">N/A</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max packet = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>packet size</literal>. Obsolete as of Samba 1.7. Use <literal>max xmit</literal> instead.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-110">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">10,000</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max open files = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Limits the number of files a Samba process will try to keep open at one time. Samba allows you to set this to less than the Unix maximum. This option is a workaround for a separate problem. Avoid changing. This option was introduced in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-111">
-<refmeta>
-<refmiscinfo class="allowable values">time in seconds</refmiscinfo>
-<refmiscinfo class="default">14400 (4 hrs)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max ttl = seconds</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the time to keep NetBIOS names in <emphasis>nmbd</emphasis> cache while trying to perform a lookup on it. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-112">
-<refmeta>
-<refmiscinfo class="allowable values">time in seconds</refmiscinfo>
-<refmiscinfo class="default">259200 (3 days)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max wins ttl = seconds</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Limits time-to-live of a NetBIOS name in <emphasis>nmbd</emphasis> WINS cache, in seconds. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-113">
-<refmeta>
-<refmiscinfo class="allowable values">size in bytes</refmiscinfo>
-<refmiscinfo class="default">65535</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] max xmit = bytes</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets maximum packet size that will be negotiated by Samba. Tuning parameter for slow links and older client bugs. Values less than 2048 are discouraged.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-114">
-<refmeta>
-<refmiscinfo class="allowable values">shell command</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] message command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command on the server to run when a WinPopup message arrives from a client. The command must end in "<literal>&</literal>" to allow immediate return. Honors all %-variables except <literal>%u</literal> (user), and supports the extra variables <literal>%s</literal> (filename the message is in), <literal>%t</literal> (destination machine), and <literal>%f</literal> (from).</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-115">
-<refmeta>
-<refmiscinfo class="allowable values">space in KB</refmiscinfo>
-<refmiscinfo class="default">0 (unlimited)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>min print space = kilobytes</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets minimum spool space required before accepting a print request.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-116">
-<refmeta>
-<refmiscinfo class="allowable values">time in seconds</refmiscinfo>
-<refmiscinfo class="default">21600 (6 hrs)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] min wins ttl = seconds</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets minimum time-to-live of a NetBIOS name in <emphasis>nmbd</emphasis> WINS cache, in seconds. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-117">
-<refmeta>
-<refmiscinfo class="allowable values">list of lmhosts, wins, hosts and bcast</refmiscinfo>
-<refmiscinfo class="default">lmhosts wins hosts bcast</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>name resolve order = list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets order of lookup when trying to get IP address from names. The <literal>hosts</literal> parameter carrries out a regular name look up using the server's normal sources: <emphasis>/etc/hosts</emphasis>, DNS, NIS, or a combination of them. Introduced in Samba 1.9.18p4.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-118">
-<refmeta>
-<refmiscinfo class="allowable values">list of netbios names</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] netbios aliases = list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Adds additional NetBIOS names by which a Samba server will advertise itself.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-119">
-<refmeta>
-<refmiscinfo class="allowable values">host name</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>netbios name = hostname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the NetBIOS name by which a Samba server is known, or primary name if NetBIOS aliases exist.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-120">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] networkstation user login = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to NO, clients will not do a full login when <literal>security = server</literal>. Avoid changing. Turning it off is a temporary workaround (introduced in Samba 1.9.18p3) for NT trusted domains bug. Automatic correction was introduced in Samba 1.9.18p10; the parameter may eventually be removed.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-121">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] nis homedir = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, the <literal>homedir map</literal> will be used to look up the user's home-directory server name and return it to the client. The client will contact that machine to connect to the share. This avoids mounting from a machine that doesn't actually have the disk. The machine with the home directories must be an SMB server.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-122">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] nt pipe support = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allows turning off NT-specific pipe calls. This is a developer/benchmarking option and may be removed in the future. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-123">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] nt smb support = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, allow NT-specific SMBs to be used. This is a developer/benchmarking option and may be removed in the future. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-124">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] null passwords = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, allows access to accounts that have null passwords. Strongly discouraged.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-125">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>ole locking compatibility = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, locking ranges will be mapped to avoid Unix locks crashing when Windows uses locks above 32KB. You should avoid changing this option. Introduced in Samba 1.9.18p10.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-126">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>only guest = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>A synonym for <literal>guest only</literal>. Forces user of a share to login as the guest account.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-127">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>only user = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Requires that users of the share be on a <literal>username =</literal> list.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-128">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>oplocks = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, support local caching of <emphasis>opportunistic</emphasis> locked files on client. This option is recommended because it improves performance by about 30%. See also <literal>fake</literal> <literal>oplocks</literal> and <literal>veto</literal> <literal>oplock</literal> <literal>files</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-129">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] os level = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the candidacy of the server when electing a browse master. Used with the <literal>domain</literal> <literal>master</literal> or <literal>local</literal> <literal>master</literal> options. You can set a higher value than a competing operating system if you want Samba to win. Windows for Workgroups and Windows 95 use 1, Windows NT client uses 17, and Windows NT Server uses 33.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-130">
-<refmeta>
-<refmiscinfo class="allowable values">number in bytes</refmiscinfo>
-<refmiscinfo class="default">65535</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] packet size = bytes</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Obsolete. Discouraged synonym of <literal>max packet</literal>. See <literal>max xmit</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-131">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] passwd chat debug = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Logs an entire password chat, including passwords passed, with a log level of 100. For debugging only. Introduced in Samba 1.9.18p5.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-132">
-<refmeta>
-<refmiscinfo class="allowable values">Unix server commands</refmiscinfo>
-<refmiscinfo class="default">compiled-in value</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] passwd chat = command sequence</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command used to change passwords on the server. Supports the variables <literal>%o</literal> (old password) and <literal>%n</literal> (new password) and allows <literal>\r</literal> <literal>\n</literal> <literal>\t</literal> and <literal>\s</literal> (space) escapes in the sequence.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-133">
-<refmeta>
-<refmiscinfo class="allowable values">Unix server program</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] passwd program = program</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command used to change user's password. Will be run as <literal>root</literal>. Supports <literal>%u</literal> (user).</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-135">
-<refmeta>
-<refmiscinfo class="allowable values">list of NetBIOS names</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] password server = netbios names</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>A list of SMB servers that will validate passwords for you. Used with an NT password server (PDC or BDC) and the <literal>security</literal> <literal>=</literal> <literal>server</literal> or <literal>security</literal> <literal>=</literal> <literal>domain</literal> configuration options. Caution: an NT password server must allow logins from the Samba server.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-136">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualfied Unix shell command</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>panic action = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command to run when Samba panics. For Samba developers and testers, <literal>/usr/bin/X11/xterm -display :0 -e gdb /samba/bin/smbd %d</literal> is a possible value.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-137">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>path = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the path to the directory provided by a file share or used by a printer share. Set automatically in <literal>[homes]</literal> share to user's home directory, otherwise defaults to<filename> /tmp</filename>. Honors the <literal>%u</literal> (user) and <literal>%m</literal> (machine) variables.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-138">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualified Unix shell command</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>postexec = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a command to run as the user after disconnecting from the share. See also the options <literal>preexec</literal>, <literal>root preexec</literal>, and <literal>root postexec</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-139">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>postscript = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Flags a printer as PostScript to avoid a Windows bug by inserting <literal>%!</literal> as the first line. Works only if printer actually is PostScript compatible.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-140">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualified Unix shell command</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>preexec = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a command to run as the user before connecting to the share. See also the options <literal>postexec</literal>, <literal>root preexec</literal>, and <literal>root postexec</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-141">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] preferred master = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, Samba is preferred to become the master browser. Causes Samba to call a browsing election when it comes online.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-142">
-<refmeta>
-<refmiscinfo class="allowable values">list of services</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>preload = share list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym of <literal>auto</literal> <literal>services</literal>. Specifies a list of shares that will always appear in browse lists.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-143">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>preserve case = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, this option leaves filenames in the case sent by client. If no, it forces filenames to the case specified by the <literal>default</literal> <literal>case</literal> option. See also <literal>short preserve case</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-144">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualified Unix shell command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>print command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command used to send a spooled file to the printer. Usually initialized to a default value by the <literal>printing</literal> option. This option honors the <literal>%p</literal> (printer name), <literal>%s</literal> (spool file) and <literal>%f</literal> (spool file as a relative path) variables. Note that the command in the value of the option must include file deletion of the spool file.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-145">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>print ok = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym of <literal>printable</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-146">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>printable = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a share to be a print share. Required for all printers.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-147">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default"><emphasis>/etc/printcap</emphasis></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] printcap name = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the path to the printer capabilities file used by the <literal>[printers]</literal> share. The default value changes to <filename>/etc/qconfig</filename> under AIX and <filename>lpstat</filename> on System V.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-148">
-<refmeta>
-<refmiscinfo class="allowable values">printer name</refmiscinfo>
-<refmiscinfo class="default"><literal>lp</literal></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>printer = name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the name of the Unix printer.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-149">
-<refmeta>
-<refmiscinfo class="allowable values">exact printer driver string used by Windows</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>printer driver = printer driver name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the string to pass to Windows when asked what driver to use to prepare files for a printer share. Note that the value is case sensitive.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-150">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default"><emphasis>samba-lib/printers.def</emphasis></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] printer driver file = path</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the location of a <emphasis>msprint.def</emphasis> file, usable by Windows 95/98.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-151">
-<refmeta>
-<refmiscinfo class="allowable values">Windows network path</refmiscinfo>
-<refmiscinfo class="default"><emphasis>\\</emphasis><replaceable>server</replaceable><emphasis>\PRINTER$</emphasis></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>printer driver location = path</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the location of the driver for a particular printer. The value is a pathname for a share that stores the printer driver files.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-152">
-<refmeta>
-<refmiscinfo class="allowable values">name</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>printer name = name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym of <literal>printer</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-153">
-<refmeta>
-<refmiscinfo class="allowable values">bsd, sysv, hpux, aix, qnx, plp, lprng</refmiscinfo>
-<refmiscinfo class="default">bsd</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>printing = style</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets printing style to one of the above, instead of the compiled-in value. This sets initial values of at least the <literal>print</literal> <literal>command </literal>, <literal>print</literal> <literal>command </literal>, <literal>lpq</literal> <literal>command </literal>, and <literal>lprm</literal> <literal>command</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-154">
-<refmeta>
-<refmiscinfo class="allowable values">NT1, LANMAN2, LANMAN1, COREPLUS, CORE</refmiscinfo>
-<refmiscinfo class="default">NT1</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] protocol = protocol</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets SMB protocol version to one of the allowable
-values. Resetting is highly discouraged. Only for backwards
-compatibility with older-client bugs.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-155">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>public = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, passwords are not needed for this share. A synonym is <literal>guest ok</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-156">
-<refmeta>
-<refmiscinfo class="allowable values">valid Unix command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>queuepause command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command used to pause a print queue. Usually initialized to a default value by the <literal>printing</literal> option. Introduced in Samba 1.9.18p10.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-157">
-<refmeta>
-<refmiscinfo class="allowable values">valid Unix command</refmiscinfo>
-<refmiscinfo class="default">varies</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>queueresume command = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the command used to resume a print queue. Usually initialized to a default value by the <literal>printing</literal> option. Introduced in Samba 1.9.18p10.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-158">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>read bmpx = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Obsolete. Do not change.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-159">
-<refmeta>
-<refmiscinfo class="allowable values">comma-separated list of users</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>read list = comma-separated list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Specifies a list of users given read-only access to a writeable share.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-160">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>read only = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a share to read-only. Antonym of <literal>writable</literal> and <literal>write ok</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-161">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] read prediction = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Reads ahead data for read-only files. Obsolete; removed in Samba 2.0.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-162">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] read raw = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allows fast streaming reads over TCP using 64K buffers. Recommended.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-163">
-<refmeta>
-<refmiscinfo class="allowable values">size in bytes</refmiscinfo>
-<refmiscinfo class="default">2048</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] read size = bytes</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a buffering option for servers with mismatched disk and network speeds. Requires experimentation. Avoid changing. Should not exceed 65536.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-164">
-<refmeta>
-<refmiscinfo class="allowable values">list of remote addresses</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] remote announce = remote list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Adds workgroups to the list on which the Samba server will announce itself. Specified as IP address/workgroup (for instance, 192.168.220.215/SIMPLE) with multiple groups separated by spaces. Allows directed broadcasts. The server will appear on those workgroup's browse lists. Does not require WINS.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-165">
-<refmeta>
-<refmiscinfo class="allowable values">IP-address list</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] remote browse sync = address list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Enables Samba-only browse list synchronization with other Samba local master browsers. Addresses can be specific addresses or directed broadcasts (i.e., ###.###.###.255). The latter will cause Samba to hunt down the local master.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-166">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>revalidate = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, requires users to re-enter passwords even after a successful initial logon to a share with a password.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-167">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] root = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>root directory</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-168">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] root dir = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>root directory</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-169">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] root directory = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Specifies a directory to <literal>chroot()</literal> to before starting daemons. Prevents any access below that directory tree. See also the <literal>wide links</literal> configuration option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-170">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualified Unix shell command</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>root postexec = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a command to run as root after disconnecting from the share. See also <literal>preexec</literal>, <literal>postexec</literal>, and <literal>root</literal> <literal>preexec</literal> configuration options. Runs after the user's <literal>postexec</literal> command. Use with caution.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-171">
-<refmeta>
-<refmiscinfo class="allowable values">fully-qualified Unix shell command</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>root preexec = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a command to run as root before connecting to the share. See also <literal>preexec</literal>, <literal>postexec</literal>, and <literal>root</literal> <literal>postexec</literal> configuration options. Runs before the user's <literal>preexec</literal> command. Use with caution.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-172">
-<refmeta>
-<refmiscinfo class="allowable values">share, user, server, domain</refmiscinfo>
-<refmiscinfo class="default">share in Samba 1.0, user in 2.0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] security = value</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets password-security policy. If <literal>security</literal> <literal>=</literal> <literal>share</literal>, services have a shared password, available to everyone. If <literal>security</literal> <literal>=</literal> <literal>user</literal>, users have (Unix) accounts and passwords. If <literal>security</literal> <literal>=</literal> <literal>server</literal>, users have accounts and passwords and a separate machine authenticates them for Samba. If <literal>security</literal> <literal>=</literal> <literal>domain</literal>, full NT-domain authentication is done. See also the <literal>password server</literal> and <literal>encrypted passwords</literal> configuration options.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-173">
-<refmeta>
-<refmiscinfo class="allowable values">string</refmiscinfo>
-<refmiscinfo class="default">Samba <literal>%v</literal> in 2.0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] server string = text</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the name that appears beside a server in browse lists. Honors the <literal>%v</literal> (Samba version number) and <literal>%h</literal> (hostname) variables.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-174">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>set directory = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allows DEC Pathworks client to use the <emphasis>set dir</emphasis> command.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-175">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">113</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] shared file entries = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Obsolete; do not use.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-176">
-<refmeta>
-<refmiscinfo class="allowable values">size in bytes</refmiscinfo>
-<refmiscinfo class="default">102400</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>shared mem size = bytes</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If compiled with FAST_SHARE_MODES (mmap), sets the shared memory size in bytes. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-177">
-<refmeta>
-<refmiscinfo class="allowable values">Unix pathname</refmiscinfo>
-<refmiscinfo class="default"><filename>/usr/local/samba/private/smbpasswd</filename></refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] smb passwd file = path</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Overrides compiled-in path to password file if <literal>encrypted passwords</literal> <literal>=</literal> <literal>yes</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-178">
-<refmeta>
-<refmiscinfo class="allowable values">smbrun command</refmiscinfo>
-<refmiscinfo class="default">compiled-in value</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] smbrun = /absolute_ path/command</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Overrides compiled-in path to <filename>smbrun</filename> binary. Avoid changing.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-180">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>short preserve case = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, leaves mangled 8.3-style filenames in the case sent by client. If no, it forces the case to that specified by the <literal>default case</literal> option. See also <literal>preserve case</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-181">
-<refmeta>
-<refmiscinfo class="allowable values">IP address</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] socket address = IP address</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets address on which to listen for connections. Default is to listen to all addresses. Used to support multiple virtual interfaces on one server. Highly discouraged.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-182">
-<refmeta>
-<refmiscinfo class="allowable values">list</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] socket options = socket option list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets OS-specific socket options. <literal>SO_KEEPALIVE</literal> has TCP check clients every 4 hours to see if they are still accessible. <literal>TCP_NODELAY</literal> sends even tiny packets to keep delay low. Recommended wherever the operating system supports them. See <link linkend="SAMBA-AP-B">Appendix B</link>, for more information.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-183">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] status = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, logs connections to a file (or shared memory) accessible to <filename>smbstatus</filename>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-184">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>strict sync = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, Samba will synchronize to disk whenever the client sets the sync bit in a packet. If set to NO, Samba flushes data to disk whenever buffers fill. Defaults to NO because Windows 98 Explorer sets the bit (incorrectly) in all packets. Introduced in Samba 1.9.18p10.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-185">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>strict locking = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, Samba checks locks on every access, not just on demand and at open time. Not recommended.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-186">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] strip dot = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Removes trailing dots from filenames. Use <literal>mangled map</literal> instead.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-187">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">1</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] syslog = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets number of Samba log messages to send to <filename>syslog</filename>. Higher is more verbose. The <filename>syslog.conf</filename> file must have suitable logging enabled.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-188">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] syslog only = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, log only to <emphasis>syslog,</emphasis> not standard Samba log files.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-189">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>sync always = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, Samba calls <emphasis>fsync</emphasis>(3) after every write. Avoid except for debugging crashing servers.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-190">
-<refmeta>
-<refmiscinfo class="allowable values">minutes</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] time offset = minutes</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets number of minutes to add to system time zone calculation. Provided to fix a client daylight-savings bug; not recommended.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-191">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] time server = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If YES, <emphasis>nmbd</emphasis> will provide time service to its clients.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-192">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>unix password sync = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set, will attempt to change the user's Unix password whenever the user changes his or her SMB password. Used to ease synchronization of Unix and Microsoft password databases. Added in Samba 1.9.18p4. See also <literal>passwd chat</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-193">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>unix realname = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set, will provide the GCOS field of <filename>/etc/passwd</filename> to the client as the user's full name.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-195">
-<refmeta>
-<refmiscinfo class="allowable values">comma-separated list of user names</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>user = comma-separated list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym for <literal>username</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-196">
-<refmeta>
-<refmiscinfo class="allowable values">comma-separated list of user names</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>username = comma-separated list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets a list of users to try to log in as for a share or shares with share-level security. Synonyms are <literal>user</literal> and <literal>users</literal>. Discouraged. Use <literal>NET USE \\</literal><replaceable>server</replaceable><literal>\</literal><replaceable>share </replaceable><literal>%</literal><replaceable>user</replaceable> from the client instead.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-197">
-<refmeta>
-<refmiscinfo class="allowable values">number</refmiscinfo>
-<refmiscinfo class="default">0</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>username level = number</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Number of uppercase letter permutations allowed to match Unix usernames. Workaround for Windows feature (single-case usernames). Use is discouraged.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-198">
-<refmeta>
-<refmiscinfo class="allowable values">pathname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] username map = pathname</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Names a file of Unix-to-Windows name pairs; used to map different spellings of account names and those Windows usernames longer than eight characters.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-199">
-<refmeta>
-<refmiscinfo class="allowable values">list of numeric values</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>valid chars = list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Semi-obsolete. Adds national characters to a character set map. Overridden by <literal>client code page</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-200">
-<refmeta>
-<refmiscinfo class="allowable values">list of users</refmiscinfo>
-<refmiscinfo class="default">NULL (everyone)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>valid users = user list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of users that can log in to a share.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-201">
-<refmeta>
-<refmiscinfo class="allowable values">slash-separated list of filenames</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>veto files = slash-list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of files not to allow the client to see when listing a directory's contents. See also <literal>delete veto files</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-202">
-<refmeta>
-<refmiscinfo class="allowable values">slash-separated list of filenames</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>veto oplock files = slash-list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of files not to oplock (and cache on clients). See also <literal>oplocks</literal> and <literal>fake oplocks</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-203">
-<refmeta>
-<refmiscinfo class="allowable values">string</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>volume = share name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the volume label of a disk share, notably a CD-ROM.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-204">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>wide links = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, Samba will follow symlinks out of the current disk share(s). See also the <literal>root dir</literal> and <literal>follow symlinks</literal> options.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-205">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] wins proxy = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, <emphasis>nmbd</emphasis> will proxy resolution requests to WINS servers on behalf of old clients, which use broadcasts. WINS server is typically on another subnet.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-206">
-<refmeta>
-<refmiscinfo class="allowable values">hostname</refmiscinfo>
-<refmiscinfo class="default">NULL</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] wins server = host</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the DNS name or IP address of the WINS server.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-207">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">NO</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] wins support = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>If set to YES, Samba activates WINS service. The <literal>wins server</literal> option must not be set if <literal>wins support = yes</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-208">
-<refmeta>
-<refmiscinfo class="allowable values">workgroup name</refmiscinfo>
-<refmiscinfo class="default">compiled-in</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] workgroup = name</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Sets the workgroup to which things will be served. Overrides compiled-in value. Choosing a name other than <literal>WORKGROUP</literal> is strongly recommended.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-209">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>writable = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Antonym for <literal>read only</literal>; synonym of <literal>write ok</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-210">
-<refmeta>
-<refmiscinfo class="allowable values">comma-separated list of users</refmiscinfo>
-<refmiscinfo class="default">NULL (everyone)</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>write list = comma-separated list</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>List of users that are given read-write access to a read-only share. See also <literal>read list</literal>.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-211">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>write ok = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Synonym of the <literal>writable</literal> configuration option.</para>
-
-</refsynopsisdiv>
-</refentry>
-
-<refentry id="appc-refentry-212">
-<refmeta>
-<refmiscinfo class="allowable values">YES, NO</refmiscinfo>
-<refmiscinfo class="default">YES</refmiscinfo>
-</refmeta>
-<refnamediv>
-<refname>[global] write raw = boolean</refname>
-</refnamediv>
-<refsynopsisdiv>
-<para>Allows fast streaming writes over TCP, using 64KB buffers. Recommended.</para>
-
-</refsynopsisdiv>
-</refentry>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="C.2" id="appc-SECT-2">
-<title>Glossary of Configuration Values</title>
-
-
-<variablelist>
-<varlistentry><term>
-<indexterm id="appc-idx-990655-0"><primary>glossary</primary></indexterm>Address list</term>
-<listitem><para>A space-separated list of IP addresses in ###.###.###.### format.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Comma-separated list</term>
-<listitem><para>A list of items separated by commas.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Command</term>
-<listitem><para>A Unix command, with full path and parameters.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Host list</term>
-<listitem><para>A space-separated list of hosts. Allows IP addresses, address masks, domain names, ALL, and EXCEPT</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Interface list</term>
-<listitem><para>A space-separated list of interfaces, in either address/netmask or address/n-bits format. For example, 192.168.2.10/24 or 192.168.2.10/255.255.255.0</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Map list</term>
-<listitem><para>A space-separated list of file-remapping strings such as <literal>(*.html</literal> <literal>*.htm)</literal>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Remote list</term>
-<listitem><para>A space-separated list of subnet-broadcast-address/workgroup pairs. For example, 192.168.2.255/SERVERS 192.168.4.255/STAFF.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Service (share) list</term>
-<listitem><para>A space-separated list of share names, without the enclosing square brackets.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Slash-list</term>
-<listitem><para>A list of filenames, separated by "/" characters to allow embedded spaces. For example, <literal>/.*/fred</literal> <literal>flintstone/*.frk/</literal>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Text</term>
-<listitem><para>One line of text.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>User list</term>
-<listitem><para>A space-separated list of usernames. In Samba 1.9, <literal>@group-name</literal> will include everyone in Unix group <literal>group-name</literal>. In Samba 2.0, <literal>@group-name</literal> includes whomever is in the NIS netgroup <literal>group_name</literal> if one exists, otherwise whomever is in the Unix group <literal>group_name</literal>. In addition, +<literal>group_name</literal> is a Unix group, &<literal>group_name</literal> is an NIS netgroup, and &+ and +& cause an ordered search of both Unix and NIS groups.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="C.3" id="appc-SECT-3">
-<title>Configuration File Variables</title>
-
-
-<para><link linkend="appc-88529">Table 3.1</link> lists of Samba configuration file variables.</para>
-
-
-<table label="C.1" id="appc-88529">
-<title>Variables in Alphabetic Order </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Name</para></entry>
-
-<entry colname="col2"><para>Meaning</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>%a</literal></para></entry>
-
-<entry colname="col2"><para>Client's architecture (one of Samba, WfWg, WinNT, Win95, or UNKNOWN)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%d</literal></para></entry>
-
-<entry colname="col2"><para>Current server process's processID</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%f</literal></para></entry>
-
-<entry colname="col2"><para>Print-spool file as a relative path (printing only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%f</literal></para></entry>
-
-<entry colname="col2"><para>User from which a message was sent (messages only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%G</literal></para></entry>
-
-<entry colname="col2"><para>Primary group name of <literal>%U</literal> (requested username)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%g</literal></para></entry>
-
-<entry colname="col2"><para>Primary group name of <literal>%u</literal> (actual username)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%H</literal></para></entry>
-
-<entry colname="col2"><para>Home directory of <literal>%u</literal> (actual username)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%h</literal></para></entry>
-
-<entry colname="col2"><para>Samba server's (Internet) hostname</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%I</literal></para></entry>
-
-<entry colname="col2"><para>Client's IP address</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%j</literal></para></entry>
-
-<entry colname="col2"><para>Print job number (printing only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%L</literal></para></entry>
-
-<entry colname="col2"><para>Samba server's NetBIOS name (virtual servers have multiple names)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%M</literal></para></entry>
-
-<entry colname="col2"><para>Client's (Internet) hostname</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%m</literal></para></entry>
-
-<entry colname="col2"><para>Client's NetBIOS name</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%n</literal></para></entry>
-
-<entry colname="col2"><para>New password (password change only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%N</literal></para></entry>
-
-<entry colname="col2"><para>Name of the NIS home directory server (without NIS, same as <literal>%L</literal>)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%o</literal></para></entry>
-
-<entry colname="col2"><para>Old password (password change only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%P</literal></para></entry>
-
-<entry colname="col2"><para>Current share's root directory (actual)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%p</literal></para></entry>
-
-<entry colname="col2"><para>Current share's root directory (in an NIS homedir map)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%p</literal></para></entry>
-
-<entry colname="col2"><para>Print filename (printing only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%R</literal></para></entry>
-
-<entry colname="col2"><para>Protocol level in use (one of CORE, COREPLUS, LANMAN1, LANMAN2, or NT1)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%S</literal></para></entry>
-
-<entry colname="col2"><para>Current share's name</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%s</literal></para></entry>
-
-<entry colname="col2"><para>Filename the message is in (messages only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%s</literal></para></entry>
-
-<entry colname="col2"><para>Print-spool file name (printing only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%T</literal></para></entry>
-
-<entry colname="col2"><para>Current date and time</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%t</literal></para></entry>
-
-<entry colname="col2"><para>Destination machine (messages only)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%u</literal></para></entry>
-
-<entry colname="col2"><para>Current share's username</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%U</literal></para></entry>
-
-<entry colname="col2"><para>Requested username for current share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%v</literal></para></entry>
-
-<entry colname="col2"><para>Samba version</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect1>
-
-
-
-
-
-
-
-
-</appendix>
+++ /dev/null
-<appendix label="D" id="SAMBA-AP-D">
-<title>Summary of Samba Daemons and Commands</title>
-
-
-
-
-<para>This appendix is a reference listing of command-line options and other information to help you use the executables that come with Samba distribution.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="D.1" id="appd-SECT-1">
-<title>Samba Distribution Programs</title>
-
-
-<para>The following sections provide information about the command-line parameters for Samba programs.</para>
-
-
-<sect2 role="" label="D.1.1" id="appd-SECT-1.1">
-<title>smbd</title>
-
-
-<para>
-<indexterm id="appd-idx-993627-0" class="startofrange"><primary>smbd daemon</primary></indexterm>
-<indexterm id="appd-idx-993627-1" class="startofrange"><primary>daemons</primary></indexterm>The <emphasis>smbd</emphasis> program provides Samba's file and printer services, using one TCP/IP stream and one daemon per client. It is controlled from the default configuration file, <replaceable>samba_dir</replaceable><emphasis>/lib/smb.conf</emphasis>, and can be overridden by command-line options.</para>
-
-
-<para>The configuration file is automatically re-evaluated every minute. If it has changed, most new options are immediately effective. You can force Samba to immediately reload the configuration file if you send a SIGHUP to <emphasis>smbd</emphasis>. Reloading the configuration file, however, will not affect any clients that are already connected. To escape this "grandfather" configuration, a client would need to disconnect and reconnect, or the server itself would have to be restarted, forcing all clients to reconnect.</para>
-
-
-<sect3 role="" label="D.1.1.1" id="appd-SECT-1.1.1">
-<title>Other signals</title>
-
-
-<para>To shut down a <emphasis>smbd</emphasis> process, send it the termination signal SIGTERM (-15) which allows it to die gracefully instead of a SIGKILL (-9). To increment the debug logging level of <emphasis>smbd</emphasis> at runtime, send the program a SIGUSR1 signal. To decrement it at runtime, send the program a SIGUSR2 signal.</para>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.1.2" id="appd-SECT-1.1.2">
-<title>Command-line options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-D</literal></term>
-<listitem><para>The <emphasis>smbd</emphasis> program is run as a daemon. This is the recommended way to use <emphasis>smbd</emphasis> (it is also the default action). In addition, <emphasis>smbd</emphasis> can also be run from <emphasis>inetd</emphasis>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-d</literal> <replaceable>debuglevel</replaceable></term>
-<listitem><para>Sets the debug (sometimes called logging) level. The level can range from 0 all the way to 10. Specifying the value on the command line overrides the value specified in the <filename>smb.conf</filename> file. Debug level 0 logs only the most important messages; level 1 is normal; levels 3 and above are primarily for debugging and slow <emphasis>smbd</emphasis> considerably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-h</literal> </term>
-<listitem><para>Prints command-line usage information for the <filename>smbd</filename> program.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.1.3" id="appd-SECT-1.1.3">
-<title>Testing/debugging options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-a</literal></term>
-<listitem><para>If this is specified, each new connection to the Samba server will append all logging messages to the log file. This option is the opposite of <literal>-o</literal>, and is the default.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-i</literal> <replaceable>scope</replaceable></term>
-<listitem><para>This sets a NetBIOS scope identifier. Only machines with the same identifier will communicate with the server. The scope identifier was a predecessor to workgroups, and this option is included only for backwards compatibility.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-l</literal> <replaceable>log_file</replaceable></term>
-<listitem><para>Send the log messages to somewhere other than the location compiled in or specified in the <filename>smb.conf</filename> file. The default is often <filename>/usr/local/samba/var/log.smb</filename>, <filename>/usr/samba/var/log.smb,</filename> or <filename>/var/log/log.smb</filename>. The first two are strongly discouraged on Linux, where <filename>/usr</filename> may be a read-only filesystem.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-O</literal> <replaceable>socket_options</replaceable></term>
-<listitem><para>This sets the TCP/IP socket options, using the same parameters as the <literal>socket</literal> <literal>options</literal> configuration option. It is often used for performance tuning and testing.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-o</literal></term>
-<listitem><para>This option is the opposite of <literal>-a</literal>. It causes log files to be overwritten when opened. Using this option saves hunting for the right log entries if you are performing a series of tests and inspecting the log file each time.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-P</literal></term>
-<listitem><para>This option forces <filename>smbd</filename> not to send any network data out. This option is typically used only by Samba developers.<indexterm id="appd-idx-994096-0" class="endofrange" startref="appd-idx-993627-0"/></para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-P</literal></term>
-<listitem><para>This option forces <filename>smbd</filename> not to send any network data out. This option is typically used only by Samba developers. <indexterm id="appd-idx-994102-0" class="endofrange" startref="appd-idx-993627-0"/></para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-p</literal> <replaceable>port_number</replaceable></term>
-<listitem><para>This sets the TCP/IP port number that the server will accept requests from. Currently, all Microsoft clients send only to the default port: 139.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal> <replaceable>configuration_file</replaceable></term>
-<listitem><para>Specifies the location of the Samba configuration file. Although the file defaults to <filename>/usr/local/samba/lib/smb.conf</filename>, you can override it here on the command line, typically for debugging.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.2" id="appd-SECT-1.2">
-<title>nmbd</title>
-
-
-<para>
-<indexterm id="appd-idx-993645-0" class="startofrange"><primary>nmbd daemon</primary></indexterm>The <emphasis>nmbd</emphasis> program is Samba's NetBIOS name and browsing daemon. It replies to broadcast NetBIOS over TCP/IP (NBT) name-service requests from SMB clients and optionally to Microsoft's Windows Internet Name Service (WINS) requests. Both of these are versions of the name-to-address lookup required by SMB clients. The broadcast version uses UDP/IP broadcast on the local subnet only, while WINS uses TCP/IP, which may be routed. If running as a WINS server, <emphasis>nmbd</emphasis> keeps a current name and address database in the file <filename>wins.dat</filename> in the <literal>samba_dir</literal><filename>/var/locks</filename> directory.</para>
-
-
-<para>An active <emphasis>nmbd</emphasis> program can also respond to browsing protocol requests used by the Windows Network Neighborhood. Browsing is a combined advertising, service announcement, and active directory protocol. This protocol provides a dynamic directory of servers and the disks and printers that the servers are providing. As with WINS, this was initially done by making UDP/IP broadcasts on the local subnet. Now, with the concept of a local master browser, it is done by making TCP/IP connections to a server. If <emphasis>nmbd</emphasis> is acting as a local master browser, it stores the browsing database in the file <filename>browse.dat</filename> in the <literal>samba_dir</literal><filename>/var/locks</filename> directory.</para>
-
-
-<sect3 role="" label="D.1.2.1" id="appd-SECT-1.2.1">
-<title>Signals</title>
-
-
-<para>Like <emphasis>smbd</emphasis>, the <emphasis>nmbd</emphasis> program responds to several Unix signals. Sending <emphasis>nmbd</emphasis> a SIGHUP signal will cause it to dump the names it knows about to the file <filename>namelist.debug</filename> in the <literal>samba_dir</literal>/<emphasis>locks</emphasis> directory and its browsing database to the <filename>browse.dat </filename>file in the same directory. To shut down a <emphasis>nmbd</emphasis> process send it a SIGTERM (-15) signal instead of a SIGKILL (-9) to allow it to die gracefully. You can increment the debug logging level of <emphasis>nmbd</emphasis> by sending it a SIGUSR1 signal; you can decrement it by sending a SIGUSR2 signal.</para>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.2.2" id="appd-SECT-1.2.2">
-<title>Command-line options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-D</literal></term>
-<listitem><para>Instructs the <filename>nmbd</filename> program to run as a daemon. This is the recommended way to use <filename>nmbd</filename>. In addition, <filename>nmbd</filename> can also be run from <firstterm>inetd</firstterm>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-d</literal> <replaceable>debuglevel</replaceable></term>
-<listitem><para>Sets the debug (sometimes called logging) level. The level can range from 0, all the way to 10. Specifying the value on the command line overrides the value specified in the <filename>smb.conf</filename> file. Debug level 0 logs only the most important messages; level 1 is normal; level 3 and above are primarily for debugging, and slow <emphasis>nmbd</emphasis> considerably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-h</literal> </term>
-<listitem><para>Prints command-line usage information for the <filename>nmbd</filename> program (also <literal>-?</literal>).</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.2.3" id="appd-SECT-1.2.3">
-<title>Testing/debugging options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-a</literal></term>
-<listitem><para>If this is specified, each new connection to the Samba server will append all logging messages to the log file. This option is the opposite of <literal>-o</literal>, and is the default.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-H</literal> <replaceable>hosts_ file</replaceable></term>
-<listitem><para>This option loads a standard <emphasis>hosts</emphasis> file for name resolution.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-i</literal> <replaceable>scope</replaceable></term>
-<listitem><para>This sets a NetBIOS scope identifier. Only machines with the same identifier will communicate with the server. The scope identifier was a predecessor to workgroups, and this option is included only for backward<indexterm id="appd-idx-994134-0" class="endofrange" startref="appd-idx-993627-1"/> compatibility.<indexterm id="appd-idx-994135-0" class="endofrange" startref="appd-idx-993645-0"/></para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-l</literal> <replaceable>log_file</replaceable></term>
-<listitem><para>Sends the log messages to somewhere other than the location compiled-in or specified in the <filename>smb.conf</filename> file. The default is often <filename>/usr/local/samba/var/log.nmb</filename>, <filename>/usr/samba/var/log.nmb,</filename> or <filename>/var/log/log.nmb</filename>. The first two are strongly discouraged on Linux, where <filename>/usr</filename> may be a read-only filesystem.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-n</literal> <replaceable>NetBIOS_name</replaceable></term>
-<listitem><para>This option allows you to override the NetBIOS name by which the daemon will advertise itself. Specifying the option on the command line overrides the <literal>netbios</literal> <literal>name</literal> option in the Samba configuration file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-O</literal> <replaceable>socket_options</replaceable></term>
-<listitem><para>This sets the TCP/IP socket options, using the same parameters as the <literal>socket</literal> <literal>options</literal> configuration option. It is often used for performance tuning and testing.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-o</literal></term>
-<listitem><para>This option is the opposite of <literal>-a</literal>. It causes log files to be overwritten when opened. Using this option saves hunting for the right log entries if you are performing a series of tests and inspecting the log file each time.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-p</literal> <replaceable>port_number</replaceable></term>
-<listitem><para>This sets the UDP/IP port number from which the server will accept requests. Currently, all Microsoft clients send only to the default port: 137.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal> <replaceable>configuration_file</replaceable></term>
-<listitem><para>Specifies the location of the Samba configuration file. Although the file defaults to <filename>/usr/local/samba/lib/smb.conf</filename>, you can override it here on the command line, typically for debugging.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-v</literal></term>
-<listitem><para>This option prints the current version of Samba.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.3" id="appd-SECT-1.3">
-<title>Samba Startup File </title>
-
-
-<para>
-<indexterm id="appd-idx-993647-0"><primary>Samba</primary><secondary>startup file</secondary></indexterm>
-<indexterm id="appd-idx-993647-1"><primary>scripts</primary><secondary sortas="Samba startup file">for Samba startup file</secondary></indexterm>
-<indexterm id="appd-idx-993647-2"><primary>directories</primary><secondary sortas="Samba startup file">for Samba startup file</secondary></indexterm>Samba is normally started by running it from your Unix system's <filename>rc</filename> files at boot time. For systems with a System V-like set of <filename>/etc/rcN.d</filename> directories, this can be done by placing a suitably named script in the <filename>/rc</filename> directory. Usually, the script starting Samba is called <emphasis>S91samba</emphasis>, while the script stopping or "killing" Samba is called <emphasis>K91samba.</emphasis> On Linux, the usual subdirectory for the scripts is <filename>/etc/rc2.d.</filename> On Solaris, the directory is <filename>/etc/rc3.d</filename>. For machines with <filename>/etc/rc.local</filename> files, you would normally add the following lines to that file:</para>
-
-
-<programlisting>/usr/local/samba/bin/smbd -D
-/usr/local/samba/bin/nmbd -D</programlisting>
-
-
-<para>The following example script supports two extra commands, <literal>status</literal> and <literal>restart</literal>, in addition to the normal <literal>start</literal> and <literal>stop</literal> for System V machines:</para>
-
-
-<programlisting>#!/bin/sh
-#
-# /etc/rc2.d./S91Samba --manage the SMB server in a System V manner
-#
-OPTS="-D"
-#DEBUG=-d3
-PS="ps ax"
-SAMBA_DIR=/usr/local/samba
-case "$1" in
-'start')
- echo "samba "
- $SAMBA_DIR/bin/smbd $OPTS $DEBUG
- $SAMBA_DIR/bin/nmbd $OPTS $DEBUG
- ;;
-'stop')
- echo "Stopping samba"
- $PS | awk '/usr.local.samba.bin/ { print $1}' |\
- xargs kill
- ;;
-'status')
- x=`$PS | grep -v grep | grep '$SAMBA_DIR/bin'`
- if [ ! "$x" ]; then
- echo "No samba processes running"
- else
- echo " PID TT STAT TIME COMMAND"
- echo "$x"
- fi
- ;;
-'restart')
- /etc/rc2.d/S91samba stop
- /etc/rc2.d/S91samba start
- /etc/rc2.d/S91samba status
- ;;
-*)
- echo "$0: Usage error -- you must say $0 start, stop, status or restart ."
- ;;
-esac
-exit</programlisting>
-
-
-<para>You'll need to set the actual paths and <literal>ps</literal> options to suit the machine you're using. In addition, you might want to add additional commands to tell Samba to reload its <filename>smb.conf</filename> file or dump its <emphasis>nmbd</emphasis> tables, depending on your actual needs.</para>
-</sect2>
-
-
-
-
-
-<sect3 role="" label="D.1.4.1" id="appd-SECT-1.4.1">
-<title>Options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-d</literal> debuglevel</term>
-<listitem><para>Sets the debug (sometimes called logging) level. The level can range from 0, the default, all the way to 10. Debug level 0 logs only the most important messages; level 1 is normal; level 3 and above are primarily for debugging, and slow <emphasis>smbsh</emphasis> considerably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-l</literal> <replaceable>logfile</replaceable></term>
-<listitem><para>Sets the name of the logfile to use.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-P</literal> <replaceable>prefix</replaceable></term>
-<listitem><para>Sets the root directory to mount the SMB filesystem. The default is <filename>/smb</filename>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-R</literal> <replaceable>resolve order</replaceable></term>
-<listitem><para>Sets the resolve order of the name servers. This option is similar to the <literal>resolve order</literal> configuration option, and can take any of the four parameters, <literal>lmhosts</literal>, <literal>host</literal>, <literal>wins</literal>, and <literal>bcast</literal>, in any order.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-U</literal> <replaceable>user</replaceable></term>
-<listitem><para>Supports <replaceable>user%password.</replaceable></para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-W</literal> <replaceable>workgroup</replaceable></term>
-<listitem><para>Sets the NetBIOS workgroup to which the client will connect.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.5" id="appd-SECT-1.5">
-<title>smbclient</title>
-
-
-<para>The <emphasis>smbclient</emphasis>
-<indexterm id="appd-idx-993745-0" class="startofrange"><primary>smbclient program</primary></indexterm>
-<indexterm id="appd-idx-993745-1" class="startofrange"><primary>testing</primary><secondary>smbclient program</secondary></indexterm> program is the maid-of-all-work of the Samba suite. Initially intended as a testing tool, it has become a full command-line Unix client, with an FTP-like interactive client. Some of its options are still used for testing and tuning, and it makes a simple tool for ensuring that Samba is running on a server.</para>
-
-
-<para>It's convenient to look at <emphasis>smbclient</emphasis> as a suite of programs:</para>
-
-
-<itemizedlist>
-<listitem><para>FTP-like interactive file transfer program</para></listitem>
-<listitem><para>Interactive printing program</para></listitem>
-<listitem><para>Interactive tar program</para></listitem>
-<listitem><para>Command-line message program</para></listitem>
-<listitem><para>Command-line <emphasis>tar</emphasis> program (but see <emphasis>smbtar</emphasis> later)</para></listitem>
-<listitem><para>"What services do you have" query program</para></listitem>
-<listitem><para>Command-line debugging program</para></listitem>
-</itemizedlist>
-
-<sect3 role="" label="D.1.5.1" id="appd-SECT-1.5.1">
-<title>General command-line options</title>
-
-
-<para>The program has the usual set of <emphasis>smbd</emphasis>-like options, which apply to all the interactive and command-line use. The syntax is:</para>
-
-
-<programlisting>smbclient //<replaceable>server_name</replaceable>/<replaceable>share_name</replaceable> [<replaceable>password</replaceable>] [-<replaceable>options</replaceable>]</programlisting>
-
-
-<para>Here is an explanation of each of the command-line options:</para>
-
-
-<variablelist>
-<varlistentry><term><literal>-d</literal> <replaceable>debug_level</replaceable></term>
-<listitem><para>Sets the debug (logging) level, from 0 to 10, with <literal>A</literal> for all. Overrides the value in <filename>smb.conf</filename>. Debug level 0 logs only the most important messages; level 1 is normal; debug level 3 and above are for debugging, and slow <emphasis>smbclient</emphasis> considerably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-h</literal></term>
-<listitem><para>Prints the command-line help information (usage) for smbclient.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-n</literal> <replaceable>NetBIOS_name</replaceable></term>
-<listitem><para>Allows you to override the NetBIOS name by which the program will advertise itself.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.5.2" id="appd-SECT-1.5.2">
-<title>Smbclient operations</title>
-
-
-<para>Running <literal>smbclient</literal> <literal>//</literal><replaceable>server_name</replaceable><literal>/</literal><replaceable>share</replaceable> will cause it to prompt you for a username and password. If the login is successful, it will connect to the share and give you a prompt much like an FTP prompt (the backslash in the prompt will be replaced by the current directory within the share as you move around the filesystem):</para>
-
-
-<programlisting>smb:\></programlisting>
-
-
-<para>
-<indexterm id="appd-idx-994034-0" class="startofrange"><primary>commands for Samba</primary></indexterm>From this command line, you can use several FTP-like commands, as listed in <link linkend="appd-89417">Table 4.1</link>. Arguments in square brackets are optional.</para>
-
-
-<table label="D.1" id="appd-89417">
-<title>smbclient Commands </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Command</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>?</literal> <replaceable>command</replaceable></para></entry>
-
-<entry colname="col2"><para>Provides list of commands or help on specified command.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>help</literal> [<replaceable>command</replaceable>]</para></entry>
-
-<entry colname="col2"><para>Provides list of commands or help on specified command.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>!</literal> [<replaceable>command</replaceable>]</para></entry>
-
-<entry colname="col2"><para>If a command is specified, it will be run in a local shell. If not, you will be placed into a local shell on the client.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>dir</literal> [<replaceable>filename</replaceable>]</para></entry>
-
-<entry colname="col2"><para>Displays any files matching <replaceable>filename</replaceable> in the current directory on the server, or all files if <replaceable>filename</replaceable> is omitted.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ls</literal> [<replaceable>filename</replaceable>]</para></entry>
-
-<entry colname="col2"><para>Displays any files matching <replaceable>filename</replaceable> in the current directory on the server, or all files if <replaceable>filename</replaceable> is omitted.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>cd</literal> [<replaceable>directory</replaceable>]</para></entry>
-
-<entry colname="col2"><para>If <replaceable>directory</replaceable> is specified, changes to the specified directory on the remote server. If not, reports the current directory on the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lcd</literal> [<replaceable>director</replaceable><literal>y</literal>]</para></entry>
-
-<entry colname="col2"><para>If <replaceable>directory</replaceable> is specified, the current directory on the local machine will be changed. If not, the name of the current directory on the local machine will be reported.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>get</literal> <emphasis>remotefile</emphasis> [<replaceable>localfile</replaceable>]</para></entry>
-
-<entry colname="col2"><para>Copies the file <replaceable>remotefile</replaceable> to the local machine. If a <replaceable>localfile</replaceable> is specified, uses that name to copy the file to. Treats the file as binary; does <emphasis>not</emphasis> do LF to CR/LF conversions.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>put</literal> <emphasis>localfile</emphasis> [<replaceable>remotefile</replaceable>]</para></entry>
-
-<entry colname="col2"><para>Copies <replaceable>localfile</replaceable> to the remote machine. If a <replaceable>remotefile</replaceable> is specified, uses that as the name to copy to on the remote server. Treats the file as binary; does <emphasis>not</emphasis> do LF to CR/LF conversions.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mget</literal> <replaceable>pattern</replaceable></para></entry>
-
-<entry colname="col2"><para>Gets all files matching <replaceable>pattern</replaceable> from the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mput</literal><replaceable> pattern</replaceable></para></entry>
-
-<entry colname="col2"><para>Places all local files matching <replaceable>pattern</replaceable> on the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>prompt</literal></para></entry>
-
-<entry colname="col2"><para>Toggles interactive prompting on and off for <literal>mget</literal> and <literal>mput</literal>.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lowercase ON </literal>(or<literal> OFF </literal>)</para></entry>
-
-<entry colname="col2"><para>If lowercase is on, <emphasis>smbclient</emphasis> will convert filenames to lowercase during an <literal>mget</literal> or <literal>get</literal> (but not a <literal>mput</literal> or <literal>put</literal>).</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>del</literal> <replaceable>filename</replaceable></para></entry>
-
-<entry colname="col2"><para>Delete a file on the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>md</literal> <replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Create a directory on the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mkdir</literal> <replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Create a directory on the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>rd</literal> <replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Remove the specified directory on the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>rmdir</literal> <replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Remove the specified directory on the remote machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>setmode</literal> <replaceable>filename</replaceable> <literal>[+|-]rsha</literal></para></entry>
-
-<entry colname="col2"><para>Set DOS filesystem attribute bits, using Unix-like modes. <literal>r</literal> is read-only, <literal>s</literal> is system, <literal>h</literal> is hidden, and <literal>a</literal> is archive.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>exit</literal></para></entry>
-
-<entry colname="col2"><para>Exits <emphasis>smbclient</emphasis>.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>quit</literal></para></entry>
-
-<entry colname="col2"><para>Exits <emphasis>smbclient</emphasis>.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>There are also mask and recursive commands for large copies; see the <filename>smbclient</filename> manual page for details on how to use these. With the exception of mask, recursive, and the lack of an ASCII transfer mode, <emphasis>smbclient</emphasis> works exactly the same as FTP. Note that because it does binary transfers, Windows files copied to Unix will have lines ending in carriage-return and linefeed (<literal>\r\n</literal>), not Unix's linefeed (<literal>\n</literal>).</para>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.5.3" id="appd-SECT-1.5.3">
-<title>Printing commands</title>
-
-
-<para>The <emphasis>smbclient</emphasis> program can also be used for access to a printer by connecting to a print share. Once connected, the commands shown in <link linkend="appd-39300">Table 4.2</link> can be used to print.</para>
-
-
-<table label="D.2" id="appd-39300">
-<title>smbclient Printing Commands </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Command</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>print</literal><replaceable> filename</replaceable></para></entry>
-
-<entry colname="col2"><para>Prints the file by copying it from the local machine to the remote one and then submitting it as a print job there.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>printmode</literal> <replaceable>text </replaceable>|<replaceable> graphics</replaceable></para></entry>
-
-<entry colname="col2"><para>Instructs the server that the following files will be plain text (ASCII) or the binary graphics format that the printer requires. It's up to the user to ensure that the file is indeed the right kind.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>queue</literal></para></entry>
-
-<entry colname="col2"><para>Displays the queue for the print share you're connected to, showing job ID, name, size, and status.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Finally, to print from the <emphasis>smbclient</emphasis>, use the <literal>-c</literal> option:</para>
-
-
-<programlisting>cat <replaceable>printfile</replaceable> | smbclient //<replaceable>server</replaceable>/<replaceable>printer_name</replaceable> -c "print -"</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.5.4" id="appd-SECT-1.5.4">
-<title>Tar commands</title>
-
-
-<para><emphasis>smbclient</emphasis> can tar up files from a file share. This is normally done from the command line using the <emphasis>smbtar</emphasis> command, but the commands shown in <link linkend="appd-54517">Table 4.3</link> are also available interactively.</para>
-
-
-<table label="D.3" id="appd-54517">
-<title>smbclient Printing Commands </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Command</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>tar c|x[IXbgNa]</literal> <replaceable>operands</replaceable></para></entry>
-
-<entry colname="col2"><para>Performs a creation or extraction <emphasis>tar</emphasis> similar to the command-line program.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>blocksize</literal> <replaceable>size</replaceable></para></entry>
-
-<entry colname="col2"><para>Sets the block size to be used by <emphasis>tar</emphasis>, in 512-byte blocks.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>noreset</literal></para></entry>
-
-<entry colname="col2"><para>Makes <emphasis>tar</emphasis> pay attention to DOS archive bit for all following commands. In <literal>full</literal> mode (the default), <emphasis>tar</emphasis> will back up everything. In <literal>inc</literal> (incremental) mode, <emphasis>tar</emphasis> will back up only those files with the archive bit set. In <literal>reset</literal> mode, <emphasis>tar</emphasis> will reset the archive bit on all files it backs up. (this requires the share to be writable), and in <literal>noreset</literal> mode the archive bit will not be reset even after the file has been backed up.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.5.5" id="appd-SECT-1.5.5">
-<title>Command-line message program options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-M</literal> <replaceable>NetBIOS_machine_name</replaceable></term>
-<listitem><para>This option allows you to send immediate messages using the WinPopup protocol to another computer. Once a connection is established, you can type your message, pressing control-D to end. If WinPopup is not running on the receiving machine, the program returns an error.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-U</literal> <replaceable>user</replaceable> </term>
-<listitem><para>This<replaceable> </replaceable>option allows you to indirectly control the FROM part of the message.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.5.6" id="appd-SECT-1.5.6">
-<title>Command-line tar program options</title>
-
-
-<para>The <literal>-T</literal> (tar), <literal>-D</literal> (starting directory), and <literal>-c</literal> (command) options are used together to tar up files interactively. This is better done with <filename>smbtar</filename>, which will be discussed shortly. We don't recommend using <emphasis>smbclient</emphasis> directly as a <emphasis>tar</emphasis> program.</para>
-
-
-<variablelist>
-<varlistentry><term><literal>-D</literal> <replaceable>initial_directory</replaceable></term>
-<listitem><para>Changes to initial directory before starting.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-c</literal> <replaceable>command_string</replaceable> </term>
-<listitem><para>Passes a command string to the <emphasis>smbclient</emphasis> command interpreter, which treats it as a semicolon-separated list of commands to be executed. This is handy to say things such as <literal>tarmode</literal> <literal>inc</literal>, for example, which forces <literal>smbclient</literal> <literal>-T</literal> to back up only files with the archive bit set.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-T</literal> <replaceable>command filename</replaceable></term>
-<listitem><para>Runs the <emphasis>tar</emphasis> driver, which is <emphasis>gtar</emphasis> compatible. The two main commands are: <literal>c</literal> (create) and <literal>x</literal> (extract), which may be followed by any of:</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>a</literal></term>
-<listitem><para>Resets archive bits once files are saved.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>b</literal> <replaceable>size</replaceable></term>
-<listitem><para>Sets blocksize in 512-byte units.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>g</literal></term>
-<listitem><para>Backs up only files with the archive bit set.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>I</literal> <replaceable>file</replaceable></term>
-<listitem><para>Includes files and directories (this is the default). Does not do pattern-matching.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>N</literal> <replaceable>filename</replaceable></term>
-<listitem><para>Backs up only those files newer than <replaceable>filename.</replaceable></para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>q</literal></term>
-<listitem><para>Does not produce diagnostics.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>X</literal> <replaceable>file</replaceable></term>
-<listitem><para>Excludes files.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.5.7" id="appd-SECT-1.5.7">
-<title>Command-line query program</title>
-
-
-<para>If <filename>smbclient</filename> is run as:</para>
-
-
-<programlisting>smbclient -L <replaceable>server_name</replaceable></programlisting>
-
-
-<para>it will list the shares and other services that machine provides. This is handy if you don't have <filename>smbwrappers</filename>. It can also be helpful as a testing program in its own right.</para>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.5.8" id="appd-SECT-1.5.8">
-<title>Command-line debugging /diagnostic program options</title>
-
-
-<para>Any of the various modes of operation of <emphasis>smbclient</emphasis> can be used with the debugging and testing command-line options:</para>
-
-
-<variablelist>
-<varlistentry><term><literal>-B</literal> <replaceable>IP_addr</replaceable></term>
-<listitem><para>Sets the broadcast address.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-d</literal> <replaceable>debug_level</replaceable></term>
-<listitem><para>Sets the debug (sometimes called logging) level. The level can range from 0 all the way to 10. In addition, you can specify <literal>A</literal> for all debugging options. Debug level 0 logs only the most important messages; level 1 is normal; level 3 and above are primarily for debugging and slow operations considerably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-E</literal></term>
-<listitem><para>Sends all messages to stderr instead of stdout.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-I</literal> <replaceable>IP_address</replaceable> </term>
-<listitem><para>Sets the IP address of the server to which it connects.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-i</literal> <replaceable>scope</replaceable></term>
-<listitem><para>This sets a NetBIOS scope identifier. Only machines with the same identifier will communicate with the server. The scope identifier was a predecessor to workgroups, and this option is included only for backward compatibility.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-l</literal> <replaceable>log_file</replaceable></term>
-<listitem><para>Sends the log messages to the specified file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-N</literal></term>
-<listitem><para>Suppresses the password prompt. Unless a password is specified on the command line or this parameter is specified, the client will prompt for a password.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-n</literal> <replaceable>NetBIOS_name</replaceable></term>
-<listitem><para>This option allows you to override the NetBIOS name by which the daemon will advertise itself.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<variablelist>
-<varlistentry><term><literal>-O</literal> <replaceable>socket_options</replaceable></term>
-<listitem><para>Sets the TCP/IP socket options using the same parameters as the <literal>socket</literal> <literal>options</literal> configuration option. It is often used for performance tuning and testing.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-p</literal> <replaceable>port_number</replaceable></term>
-<listitem><para>Sets the port number from which the client will accept requests.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-R</literal> <replaceable>resolve_order</replaceable></term>
-<listitem><para>Sets the resolve order of the name servers. This option is similar to the <literal>resolve</literal> <literal>order</literal> configuration option, and can take any of the four parameters, <literal>lmhosts</literal>, <literal>host</literal>, <literal>wins</literal>, and <literal>bcast</literal>, in any order .</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal> <replaceable>configuration_file</replaceable></term>
-<listitem><para>Specifies the location of the Samba configuration file. Used for debugging.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-t</literal> <replaceable>terminal_code</replaceable></term>
-<listitem><para>Sets the terminal code for Asian languages.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-U</literal> <replaceable>username</replaceable></term>
-<listitem><para>Sets the username and optionally password (e.g., <literal>-U</literal> <literal>fred%secret</literal>).</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-W</literal> <replaceable>workgroup</replaceable></term>
-<listitem><para>Specifies the workgroup that you want the client to connect as.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>If you want to test a particular name service, run <emphasis>smbclient</emphasis> with <literal>-R</literal> and just the name of the service. This will force <emphasis>smbclient</emphasis> to use only the service you gave.<emphasis></emphasis>
-<indexterm id="appd-idx-993802-0" class="endofrange" startref="appd-idx-993745-0"/>
-<indexterm id="appd-idx-993802-1" class="endofrange" startref="appd-idx-993745-1"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.6" id="appd-SECT-1.6">
-<title>smbstatus</title>
-
-
-<para>The <filename>smbstatus</filename>
-<indexterm id="appd-idx-993754-0"><primary>smbstatus program</primary></indexterm>
-<indexterm id="appd-idx-993754-1"><primary>connections</primary><secondary>current, list of</secondary></indexterm> program lists the current connections on a Samba server. There are three separate sections. The first section lists various shares that are in use by specific users. The second section lists the locked files that Samba currently has on all of its shares. Finally, the third section lists the amount of memory usage for each of the shares. For example:</para>
-
-
-<programlisting># <emphasis role="bold">smbstatus</emphasis>
-Samba version 2.0.3
-Service uid gid pid machine
-----------------------------------------------
-network davecb davecb 7470 phoenix (192.168.220.101) Sun May 16
-network davecb davecb 7589 chimaera (192.168.220.102) Sun May 16
-
-Locked files:
-Pid DenyMode R/W Oplock Name
---------------------------------------------------
-7589 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/samba/quicken/inet/common/system/help.bmp
-Sun May 16 21:23:40 1999
-7470 DENY_WRITE RDONLY NONE /home/samba/word/office/findfast.exe
-Sun May 16 20:51:08 1999
-7589 DENY_WRITE RDONLY EXCLUSIVE+BATCH /home/samba/quicken/lfbmp70n.dll
-Sun May 16 21:23:39 1999
-7589 DENY_WRITE RDWR EXCLUSIVE+BATCH /home/samba/quicken/inet/qdata/runtime.dat
-Sun May 16 21:23:41 1999
-7470 DENY_WRITE RDONLY EXCLUSIVE+BATCH /home/samba/word/office/osa.exe
-Sun May 16 20:51:09 1999
-7589 DENY_WRITE RDONLY NONE /home/samba/quicken/qversion.dll
-Sun May 16 21:20:33 1999
-7470 DENY_WRITE RDONLY NONE /home/samba/quicken/qversion.dll
-Sun May 16 20:51:11 1999
-
-Share mode memory usage (bytes):
- 1043432(99%) free + 4312(0%) used + 832(0%) overhead = 1048576(100%) total</programlisting>
-
-
-<sect3 role="" label="D.1.6.1" id="appd-SECT-1.6.1">
-<title>Options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-b</literal></term>
-<listitem><para>Forces <filename>smbstatus</filename> to produce brief output. This includes the version of Samba and auditing information about the users that have logged into the server.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-d</literal></term>
-<listitem><para>Gives verbose output, including each of the three reporting sections listed in the previous example. This is the default.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-L</literal></term>
-<listitem><para>Forces <filename>smbstatus</filename> to print only the current file locks it has. This corresponds to the second section in a verbose output.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-p</literal></term>
-<listitem><para>Prints a list of <filename>smbd</filename> process IDs only. This is often used for scripts.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-S</literal></term>
-<listitem><para>Prints only a list of shares and their connections. This corresponds to the first section in a verbose output.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal> <replaceable>configuration_file</replaceable></term>
-<listitem><para>Sets the Samba configuration file to use when processing this command.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-u</literal> <replaceable>username</replaceable></term>
-<listitem><para>Limits the <filename>smbstatus</filename> report to the activity of a single user.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.7" id="appd-SECT-1.7">
-<title>smbtar</title>
-
-
-<para>The <emphasis>smbtar</emphasis>
-<indexterm id="appd-idx-993755-0"><primary>smbtar program</primary><secondary>tar operations and</secondary></indexterm>
-<indexterm id="appd-idx-993755-1"><primary>tar operations</primary></indexterm> program is a shell script on top of <emphasis>smbclient</emphasis> that gives the program more intelligible options when doing tar operations. Functionally, it is equivalent to the Unix <emphasis>tar</emphasis> program.</para>
-
-
-<sect3 role="" label="D.1.7.1" id="appd-SECT-1.7.1">
-<title>Options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-a</literal></term>
-<listitem><para>Resets the archive bit mode</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-b</literal> <replaceable>blocksize</replaceable></term>
-<listitem><para>Blocking size. Defaults to 20.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-d</literal> <replaceable>directory</replaceable></term>
-<listitem><para>Changes to initial directory before restoring or backing up files.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-i</literal></term>
-<listitem><para>Incremental mode; tar files are backed up only if they have the DOS archive bit set. The archive bit is reset after each file is read.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-l</literal> <replaceable>log_level</replaceable></term>
-<listitem><para> Sets the logging level.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-N</literal> <replaceable>filename</replaceable></term>
-<listitem><para>Backs up only the files newer than the last modification date of <replaceable>filename</replaceable>. For incremental backups.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-p</literal> <replaceable>password</replaceable></term>
-<listitem><para>Specifies the password to use to access a share.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-r</literal></term>
-<listitem><para>Restores files to the share from the tar file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal> <replaceable>server</replaceable></term>
-<listitem><para>Specifies the SMB/CIFS server in which the share resides.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-t</literal> <replaceable>tape</replaceable></term>
-<listitem><para>Tape device or file. Default is the value of the environment variable <literal>$TAPE</literal>, or <emphasis>tar.out</emphasis> if <literal>$TAPE</literal> isn't set.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-u</literal> <replaceable>user</replaceable></term>
-<listitem><para>Specifies the user to connect to the share as. You can specify the password as well, in the format <replaceable>username</replaceable><literal>%</literal><replaceable>password</replaceable>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-v</literal></term>
-<listitem><para>Specifies the use of verbose mode.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-X</literal> <replaceable>file</replaceable></term>
-<listitem><para>Tells <firstterm>smbtar</firstterm> to exclude the specified file from the <emphasis>tar</emphasis> create or restore.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-x</literal> <replaceable>share</replaceable></term>
-<listitem><para>States the share name on the server to connect to. The default is <literal>backup</literal>, which is a common share name to perform backups with.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>For example, a trivial backup command to archive the data for user <literal>sue</literal> is:</para>
-
-
-<programlisting># <emphasis role="bold">smbtar -s pc_name -x sue -u sue -p secret -t sue.tar</emphasis></programlisting>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.8" id="appd-SECT-1.8">
-<title>nmblookup</title>
-
-
-<para>The <filename>nmblookup</filename>
-<indexterm id="appd-idx-993756-0"><primary>nmblookup program</primary></indexterm>
-<indexterm id="appd-idx-993756-1"><primary>name services</primary><secondary>nmblookup program</secondary></indexterm> program is a client program that exercises the NetBIOS-over-UDP/IP name service for resolving NBT machine names into IP addresses. The command works by broadcasting its queries on the local subnet until a machine with that name responds. You can think of it as a Windows <emphasis>nslookup(1)</emphasis> or <emphasis>dig(1)</emphasis>. This is useful for looking up both normal NetBIOS names, and the odd ones like <literal>_ _MSBROWSE_ _</literal> that the Windows name services use to provide directory-like services. If you wish to query for a particular type of NetBIOS name, add the NetBIOS <literal><type></literal> to the end of the name.</para>
-
-
-<para>The command line is:</para>
-
-
-<programlisting>nmblookup [-options] <replaceable>name</replaceable></programlisting>
-
-
-<para>The options supported are:</para>
-
-
-<variablelist>
-<varlistentry><term><literal>-A</literal></term>
-<listitem><para>Interprets <replaceable>name</replaceable> as an IP address and do a node-status query on this address.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-B</literal> <replaceable>broadcast _address</replaceable></term>
-<listitem><para>Sends the query to the given broadcast address. The default is to send the query to the broadcast address of the primary network interface.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-d</literal> <replaceable>debuglevel</replaceable></term>
-<listitem><para>Sets the debug (sometimes called logging) level. The level can range from 0 all the way to 10. Debug level 0 logs only the most important messages; level 1 is normal; level 3 and above are primarily for debugging and slow the program considerably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-h</literal></term>
-<listitem><para>Prints command-line usage information for the program.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-i</literal> <replaceable>scope</replaceable></term>
-<listitem><para>Sets a NetBIOS scope identifier. Only machines with the same identifier will communicate with the server. The scope identifier was a predecessor to workgroups, and this option is included only for backward compatibility.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-M</literal></term>
-<listitem><para>Searches for a local master browser. This is done with a broadcast searching for a machine that will respond to the special name <literal>_ _MSBROWSE_ _ </literal>, and then asking that machine for information, instead of broadcasting the query itself.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-R</literal></term>
-<listitem><para>Sets the recursion desired bit in the packet. This will cause the machine that responds to try to do a WINS lookup and return the address and any other information the WINS server has saved.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-r</literal></term>
-<listitem><para>Use the root port of 137 for Windows 95 machines.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-S</literal></term>
-<listitem><para>Once the name query has returned an IP address, does a node status query as well. This returns all the resource types that the machine knows about, with their numeric attributes. For example:</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<programlisting>% <emphasis role="bold">nmblookup -d 4 -S elsbeth</emphasis>
-received 6 names
- ELSBETH <00> - <GROUP> B <ACTIVE>
- ELSBETH <03> - B <ACTIVE>
- ELSBETH <1d> - B <ACTIVE>
- ELSBETH <1e> - <GROUP> B <ACTIVE>
- ELSBETH <20> - B <ACTIVE>
- .._ _MSBROWSE_ _.. <01> - <GROUP> B <ACTIVE></programlisting>
-
-
-<variablelist>
-<varlistentry><term><literal>-s</literal> <replaceable>configuration_file</replaceable></term>
-<listitem><para>Specifies the location of the Samba configuration file. Although the file defaults to <filename>/usr/local/samba/lib/smb.conf</filename>, you can override it here on the command-line, normally for debugging.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-T</literal></term>
-<listitem><para>This option can be used to translate IP addresses into resolved names.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-U</literal> <replaceable>unicast_address</replaceable></term>
-<listitem><para>Performs a unicast query to the specified address. Used with <literal>-R</literal> to query WINS servers.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>Note that there is no workgroup option for <emphasis>nmblookup</emphasis> ; you can get around this by putting <literal>workgroup</literal> <literal>=</literal> <replaceable>workgroup_name </replaceable>in a file and passing it to <emphasis>nmblookup</emphasis> with the <literal>-s</literal> <replaceable>smb.conf_file</replaceable> option.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.9" id="appd-SECT-1.9">
-<title>smbpasswd</title>
-
-
-<para>The <emphasis>smbpasswd</emphasis>
-<indexterm id="appd-idx-993757-0"><primary>smbpasswd program</primary></indexterm>
-<indexterm id="appd-idx-993757-1"><primary>passwords</primary><secondary>smbpasswd program </secondary></indexterm> password has two distinct sets of functions. When run by users, it changes their encrypted passwords. When run by <literal>root</literal>, it updates the encrypted password file. When run by an ordinary user with no options, it connects to the primary domain controller and changes his or her Windows password.</para>
-
-
-<para>The program will fail if <emphasis>smbd</emphasis> is not operating, if the <literal>hosts</literal> <literal>allow</literal> or <literal>hosts</literal> <literal>deny</literal> configuration options will not permit connections from localhost (IP address 127.0.0.1), or the <literal>encrypted</literal> <literal>passwords</literal> <literal>=</literal> <literal>no</literal> option is set.</para>
-
-
-<sect3 role="" label="D.1.9.1" id="appd-SECT-1.9.1">
-<title>Regular user options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-D</literal> <replaceable>debug_level</replaceable></term>
-<listitem><para>Sets the debug (also called logging) level. The level can range from 0 to 10. Debug level 0 logs only the most important messages; level 1 is normal; level 3 and above are primarily for debugging and slow the program considerably.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-h</literal></term>
-<listitem><para>Prints command-line usage information for the program.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-r</literal> <replaceable>remote_machine_name</replaceable></term>
-<listitem><para>Specifies on which machine the password should change. The remote machine must be a primary domain controller (PDC).</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-R</literal> <replaceable>resolve_order</replaceable></term>
-<listitem><para>Sets the resolve order of the name servers. This option is similar to the <literal>resolve</literal> <literal>order</literal> configuration option, and can take any of the four parameters, <literal>lmhosts</literal>, <literal>host</literal>, <literal>wins</literal>, and <literal>bcast</literal>,<literal> </literal>in any order.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-U</literal> <replaceable>username</replaceable></term>
-<listitem><para>Used only with <literal>-r</literal>, to modify a username that is spelled differently on the remote machine.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-
-
-
-<sect3 role="" label="D.1.9.2" id="appd-SECT-1.9.2">
-<title>Root-only options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-a</literal> <replaceable>username</replaceable></term>
-<listitem><para>Adds a user to the encrypted password file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-d</literal> <replaceable>username</replaceable></term>
-<listitem><para>Disables a user in the encrypted password file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-e</literal> <replaceable>username</replaceable></term>
-<listitem><para>Enables a disabled user in the encrypted password file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-m</literal> <replaceable>machine_name</replaceable></term>
-<listitem><para>Changes a machine account's password. The machine accounts are used to authenticate machines when they connect to a primary or backup domain controller.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-j</literal> <replaceable>domain_name</replaceable></term>
-<listitem><para>Adds a Samba server to a Windows NT Domain.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-n</literal></term>
-<listitem><para>Sets no password for the user.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal> <replaceable>username</replaceable></term>
-<listitem><para>Causes <emphasis>smbpasswd</emphasis> to be silent and to read its old and new passwords from standard input, rather than from <filename>/dev/tty</filename>. This is useful for writing scripts.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.10" id="appd-SECT-1.10">
-<title>testparm</title>
-
-
-<para>The <emphasis>testparm</emphasis>
-<indexterm id="appd-idx-993999-0"><primary>testparm program</primary></indexterm>
-<indexterm id="appd-idx-993999-1"><primary>smb.conf (Samba configuration) file</primary><secondary>testparm program for</secondary></indexterm> program checks an <filename>smb.conf</filename> file for obvious errors and self-consistency. Its command line is:</para>
-
-
-<programlisting>testparm [options] <replaceable>configfile_name [hostname IP_addr]</replaceable></programlisting>
-
-
-<para>If the configuration file is not specified, the file at <replaceable>samba_dir</replaceable><filename>/lib/smb.conf</filename> is checked by default. If you specify a hostname and an IP address, an extra check will be made to ensure that the specified machine would be allowed to connect to Samba. If a hostname is specified, an IP address should be present as well.</para>
-
-
-<sect3 role="" label="D.1.10.1" id="appd-SECT-1.10.1">
-<title>Options</title>
-
-
-<variablelist>
-<varlistentry><term><literal>-h</literal></term>
-<listitem><para>Prints command-line information for the program.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-L</literal> server_name</term>
-<listitem><para>Resets the <literal>%L</literal> configuration variable to the specified server name.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal></term>
-<listitem><para>This option prevents the <emphasis>testparm</emphasis> program from prompting the user to press the Enter key before printing a list of the configuration options for the server.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.12" id="appd-SECT-1.12">
-<title>rpcclient</title>
-
-
-<para>This is a new client that exercises the <indexterm id="appd-idx-993762-0"><primary>RPC (remote procedure call)</primary></indexterm>
-<indexterm id="appd-idx-993762-1"><primary>remote procedure call (RPC)</primary></indexterm>RPC (remote procedure call) interfaces of an SMB server. Like <emphasis>smbclient</emphasis>, <emphasis>rpcclient</emphasis>
-<indexterm id="appd-idx-993763-0"><primary>rpcclient program</primary></indexterm> started its life as a test program for the Samba developers and will likely stay that way for a while. Its command line is:</para>
-
-
-<programlisting>rpcclient //<replaceable>server</replaceable>/<replaceable>share</replaceable></programlisting>
-
-
-<para>The command-line options are the same as the Samba 2.0 <emphasis>smbclient</emphasis>, and the operations you can try are listed in <link linkend="appd-65243">Table 4.4</link>.</para>
-
-
-<table label="D.4" id="appd-65243">
-<title>rpcclient commands </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Command</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>regenum keyname</literal></para></entry>
-
-<entry colname="col2"><para>Registry Enumeration (keys, values)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>regdeletekey keyname </literal></para></entry>
-
-<entry colname="col2"><para>Registry Key Delete</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>regcreatekey keyname [keyvalue]</literal></para></entry>
-
-<entry colname="col2"><para>Registry Key Create</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>regquerykey keyname</literal></para></entry>
-
-<entry colname="col2"><para>Registry Key Query</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>regdeleteval valname</literal></para></entry>
-
-<entry colname="col2"><para>Registry Value Delete</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>regcreateval valname valtype value</literal></para></entry>
-
-<entry colname="col2"><para>Registry Key Create</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>reggetsec keyname</literal></para></entry>
-
-<entry colname="col2"><para>Registry Key Security</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>regtestsec keyname</literal></para></entry>
-
-<entry colname="col2"><para>Test Registry Key Security</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ntlogin [username] [password]</literal></para></entry>
-
-<entry colname="col2"><para>NT Domain Login Test</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>wksinfo</literal></para></entry>
-
-<entry colname="col2"><para>Workstation Query Info</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>srvinfo</literal></para></entry>
-
-<entry colname="col2"><para>Server Query Info</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>srvsessions</literal></para></entry>
-
-<entry colname="col2"><para>List Sessions on a Server</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>srvshares</literal></para></entry>
-
-<entry colname="col2"><para>List shares on a server</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>srvconnections</literal></para></entry>
-
-<entry colname="col2"><para>List connections on a server</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>srvfiles</literal></para></entry>
-
-<entry colname="col2"><para>List files on a server</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lsaquery</literal></para></entry>
-
-<entry colname="col2"><para>Query Info Policy (domain member or server)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lookupsids</literal></para></entry>
-
-<entry colname="col2"><para>Resolve names from SIDs</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ntpass</literal></para></entry>
-
-<entry colname="col2"><para>NT SAM Password Change</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="D.1.13" id="appd-SECT-1.13">
-<title>tcpdump</title>
-
-
-<para>The <emphasis>tcpdump</emphasis>
-<indexterm id="appd-idx-993765-0"><primary>tcpdump utility</primary></indexterm>
-<indexterm id="appd-idx-993765-1"><primary>packets</primary><secondary>headers for, tcpdump utility and</secondary></indexterm> utility, a classic system administration tool, dumps all the packet headers it sees on an interface that match an expression. The version included in the Samba distribution is enhanced to understand the SMB protocol. The <emphasis>expression</emphasis> is a logical expression with "and," "or," and "not," although sometimes it's very simple. For example, <literal>host</literal> <literal>escrime</literal> would select every packet going to or from <literal>escrime</literal>. The expression is normally one or more of:</para>
-
-
-<itemizedlist>
-
-<listitem><para><literal>host</literal> <replaceable>name</replaceable></para></listitem>
-
-<listitem><para><literal>ne</literal>t <replaceable>network_number</replaceable></para></listitem>
-<listitem><para><literal>port</literal> <replaceable>number</replaceable></para></listitem>
-<listitem><para><literal>src</literal> <replaceable>name </replaceable></para></listitem>
-<listitem><para><literal>dst</literal> <replaceable>name</replaceable></para></listitem>
-</itemizedlist>
-
-<para>The most common options are <literal>src</literal> (source), <literal>dst</literal> (destination), and <literal>port</literal>. For example, in the book we used the command:</para>
-
-
-<programlisting>tcpdump port not telnet</programlisting>
-
-
-<para>This dumps all the packets except telnet; we were logged-in via telnet and wanted to see only the SMB packets.</para>
-
-
-<para>Another <emphasis>tcpdump</emphasis> example is selecting traffic between server and either <literal>sue</literal> or <literal>joe</literal>:</para>
-
-
-<programlisting>tcpdump host server and \( sue or joe \)</programlisting>
-
-
-<para>We recommend using the <literal>-s</literal> <literal>1500</literal> option so that you capture all of the SMB messages sent, instead of just the header information.</para>
-
-
-<sect3 role="" label="D.1.13.1" id="appd-SECT-1.13.1">
-<title>Options</title>
-
-
-<para>There are many options, and many other kinds of expressions that can be used with <emphasis>tcpdump</emphasis>. See the manual page for details on the advanced options. The most common options are as follows:</para>
-
-
-<variablelist>
-<varlistentry><term><literal>-c</literal> <replaceable>count</replaceable></term>
-<listitem><para>Forces the program to exit after receiving the specified number of packets.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-F</literal> <replaceable>file</replaceable></term>
-<listitem><para>Reads the expression from the specified file and ignores expressions on the command line.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-i</literal> <replaceable>interface</replaceable></term>
-<listitem><para>Forces the program to listen on the specified interface.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-r</literal> <replaceable>file</replaceable></term>
-<listitem><para>Reads packets from the specified file (captured with <literal>-w</literal>).</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-s</literal> <replaceable>length</replaceable></term>
-<listitem><para>Saves the specified number of bytes of data from each packet (rather than 68 bytes).</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>-w</literal> <replaceable>file</replaceable></term>
-<listitem><para>Writes the packets to the specified file.<indexterm id="appd-idx-993743-0" class="endofrange" startref="appd-idx-994034-0"/></para></listitem>
-</varlistentry>
-</variablelist>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-</appendix>
+++ /dev/null
-<appendix label="E" id="SAMBA-AP-E">
-<title>Downloading Samba with CVS</title>
-
-
-
-
-<para>
-<indexterm id="appe-idx-992918-0"><primary>downloads</primary><secondary>Samba</secondary><tertiary sortas="obtainedusing CVS">obtained using CVS</tertiary></indexterm>
-<indexterm id="appe-idx-992918-1"><primary>Samba</primary><secondary>downloading</secondary><tertiary>with CVS</tertiary></indexterm>This appendix contains information on how to download the latest source version of Samba using the C<indexterm id="appe-idx-992919-0"><primary>Concurrent Versions System (CVS)</primary></indexterm>
-<indexterm id="appe-idx-992919-1"><primary>CVS (Concurrent Versions Systems)</primary></indexterm>oncurrent Versions System (CVS). CVS is a freely available configuration management tool available from <indexterm id="appe-idx-992920-0"><primary>Cyclic Software</primary></indexterm>Cyclic Software and is distributed under the<indexterm id="appe-idx-992921-0"><primary>GNU General Public License (GPL)</primary></indexterm> GNU General Public License. You can download the latest copy from <systemitem role="url">http://www.cyclic.com/</systemitem>.<indexterm id="appe-idx-992922-0"><primary>URLs (uniform resource locators)</primary><secondary>Cyclic Software</secondary></indexterm></para>
-
-
-<para>CVS works on top of the GNU <indexterm id="appe-idx-992923-0"><primary>Revision Control System
-(RCS)</primary></indexterm>
-<indexterm id="appe-idx-992923-1"><primary>RCS (Revision Control
-System)</primary></indexterm>Revision Control System (RCS). Many Unix
-systems come preinstalled with RCS. However, if you want to download
-the latest version of RCS, you can find it at <indexterm id="appe-idx-992936-0"><primary>URLs (uniform resource
-locators)</primary><secondary>RCS (Revision Control
-System)</secondary></indexterm><systemitem role="url">http://ftp.gnu.org/gnu/rcs/</systemitem>.</para>
-
-
-<para>One of the nicest things about CVS is its ability to handle remote logins. This means that people across the globe on the Internet can download and update various source files for any project that uses a CVS repository. Such is the case with Samba. Once you have RCS and CVS installed on your system, you must first log in to the Samba source server with the following command:</para>
-
-
-<programlisting>cvs -d :pserver:cvs@cvs.samba.org:/cvsroot login</programlisting>
-
-
-<para>This tells CVS to connect to the CVS server at <filename>cvs.samba.org</filename>. Once you are connected, you can download the latest source tree with the following command:</para>
-
-
-<programlisting>cvs -d :pserver:cvs@cvs.samba.org:/cvsroot co samba</programlisting>
-
-
-<para>This will download the entire Samba distribution (file by file) into a directory entitled <filename>/samba</filename>, which it will create on your hard drive. This directory will have the same structure as the Samba source distribution described in <link linkend="SAMBA-CH-2">Chapter 2</link>. It includes source and header files, documentation, and sample configuration files to help get you started. After that is completed, you can follow the instructions in <link linkend="SAMBA-CH-2">Chapter 2</link> to configure and compile Samba on your server.</para>
-
-
-
-
-
-
-
-
-
-
-</appendix>
+++ /dev/null
-<appendix label="F" id="SAMBA-AP-F">
-<title>Sample Configuration File</title>
-
-
-
-
-<para>
-<indexterm id="appf-idx-993481-0" class="startofrange"><primary>configuration files</primary><secondary>sample of</secondary></indexterm>This appendix gives an example of a production <filename>smb.conf</filename> file and looks at how many of the options are used in practice. The following is a slightly disguised version of one we used at a corporation with five Linux servers, five Windows for Workgroups clients and three NT Workstation clients:</para>
-
-
-<programlisting># smb.conf -- File Server System for: 1 Example.COM BSC & Management Office
-[globals]
- workgroup = 1EG_BSC
- interfaces = 10.10.1.14/24</programlisting>
-
-
-<para>We provide this service on only one of the machine's interfaces. The <literal>interfaces</literal> option sets its address and netmask, where <literal>/24</literal> is the same as using the netmask 255.255.255.0:</para>
-
-
-<programlisting>comment = Samba ver. %v
- preexec = csh -c `echo /usr/samba/bin/smbclient \
- -M %m -I %I` &</programlisting>
-
-
-<para>We use the <command>preexec</command> command to log information about all connections by machine name (<literal>%m</literal>) and IP address (<literal>%I)</literal>:</para>
-
-
-<programlisting># smbstatus will output various info on current status
- status = yes
- browseable = yes
- printing = bsd
-
- # the username that will be used for access to services
- # specified with 'guest = ok'
- guest account = samba</programlisting>
-
-
-<para>The default guest account was <literal>nobody</literal>, uid -1, which produced log messages on one of our machines saying "your server is being unfriendly," so we created a specific Samba guest account for browsing and printing:</para>
-
-
-<programlisting># superuser account - admin privileges to shares, with no
- # restrictions
- # WARNING - use this with care: files can be modified,
- # regardless of file permissions
- admin users = root
-
- # who is NOT allowed to connect to ANY service
- invalid users = @wheel, mail, deamon, adt</programlisting>
-
-
-<para>Daemons can't use Samba, only people. The <literal>invalid</literal> <literal>users</literal> option closes a security hole; it prevents intruders from breaking in by pretending to be a daemon process.</para>
-
-
-<programlisting># hosts that are ALLOWED or DENIED from connecting to ANY service
- hosts allow = 10.10.1.
- hosts deny = 10.10.1.6
-
- # where the lock files will be located
- lock directory = /var/lock/samba/locks
-
- # debug log files
- # %m = separate log for each NetBIOS name (each machine)
- log file = /var/log/samba/log.%m
-
- # We send priority 0, 1 and 2 messages to the system logs
- syslog = 2
-
- # If a WinPopup message is sent to the server,
- # redirect it to a user via e-mail
-
- message command = /bin/mail -s 'message from #% on %m' \
- pkelly < %s; rm %s
-
-# ---------------------------------------------------
-# [globals] Performance Tuning
-# ---------------------------------------------------
-
- # caching algorithm to reduce time doing getwd() calls.
- getwd cache = yes
-
- socket options = TCP_NODELAY
-
- # tell the server whether the client is present and
- # responding in seconds
- keep alive = 60
-
- # num minutes of inactivity before a connection is
- # considered dead
- dead time = 30
-
- read prediction = yes
- max xmit = 17384
- read size = 512</programlisting>
-
-
-<para>The <literal>share</literal> <literal>modes</literal>, <literal>max</literal>, <literal>xinit</literal>, and <literal>read</literal> <literal>size</literal> options are machine-specific (see <link linkend="SAMBA-AP-B">Appendix B</link>):</para>
-
-
-<programlisting># locking is done by the server
- locking = yes
-
- # control whether dos style attributes should be mapped
- # to unix execute bits
- map hidden = yes
- map archive = yes
- map system = yes</programlisting>
-
-
-<para>The three <literal>map</literal> options will work only on shares with a create mode that includes the execute bits (0111). Our <literal>homes</literal> and <literal>printers</literal> shares won't honor them, but the [<literal>www]</literal> share will:</para>
-
-
-<programlisting># ---------------------------------------------------------
-# [globals] Security and Domain Logon Services
-# ---------------------------------------------------------
-# connections are made with UID and GID, not as shares
- security = user
-
-# boolean variable that controls whether passwords
-# will be encrypted
- encrypt passwords = yes
- passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"
- passwd program = /usr/bin/passwd %u
-
-# Always become the local master browser
- domain master = yes
- preferred master = yes
- os level = 34
-
-# For domain logons to work correctly. Samba acts as a
-# primary domain controller.
- domain logons = yes
-
-# Logon script to run for user off the server each time
-# username (%U) logs in. Set the time, connect to shares,
-# virus checks, etc.
- logon script = scripts\%U.bat
-
-[netlogon]
- comment = "Domain Logon Services"
- path = /u/netlogon
- writable = yes
- create mode = 444
- guest ok = no
- volume = "Network"</programlisting>
-
-
-<para>This share, discussed in <link linkend="SAMBA-CH-6">Chapter 6</link>, is required for Samba to work smoothly in a Windows NT domain:</para>
-
-
-<programlisting># -----------------------------------------------------------
-# [homes] User Home Directories
-# -----------------------------------------------------------
-[homes]
- comment = "Home Directory for : %u "
- path = /u/users/%u</programlisting>
-
-
-<para>The password file of the Samba server specifies each person's home directory as <emphasis>/home/</emphasis><replaceable>machine_name</replaceable><emphasis>/</emphasis><replaceable>person</replaceable>, which NFS converts to point to the actual physicl location under <emphasis>/u/users</emphasis>. The <literal>path</literal> option in the <literal>[homes]</literal> share tells Samba the actual (non-NFS) location:</para>
-
-
-<programlisting>guest ok = no
- read only = no
- create mode = 644
- writable = yes
- browseable = no
-
-# -----------------------------------------------------------
-# [printers] System Printers
-# -----------------------------------------------------------
-[printers]
- comment = "Printers"
- path = /var/spool/lpd/samba
- printcap name = /etc/printcap
- printable = yes
- public = no
- writable = no
-
- lpq command = /usr/bin/lpq -P%p
- lprm command = /usr/bin/lprm -P%p %j
- lppause command = /usr/sbin/lpc stop %p
- lpresume command = /usr/sbin/lpc start %p
-
- create mode = 0700
-
- browseable = no
- load printers = yes
-
-# -----------------------------------------------------------
-# Specific Descriptions: [programs] [data] [retail]
-# -----------------------------------------------------------
-[programs]
- comment = "Shared Programs %T"
- volume = "programs"</programlisting>
-
-
-<para>Shared Programs shows up in the Network Neighborhood, and <literal>programs</literal> is the volume name you specify when an installation program wants to know the label of the CD-ROM from which it thinks it's loading:</para>
-
-
-<programlisting>path = /u/programs
- public = yes
- writeable = yes
- printable = no
- create mode = 664
-[cdrom]
- comment = "Unix CDROM"
- path = /u/cdrom
- public = no
- writeable = no
- printable = no
- volume = "cdrom"
-
-[data]
- comment = "Data Directories %T"
- path = /u/data
- public = no
- create mode = 770
- writeable = yes
- volume = "data"
-
-[nt4]
- comment = "NT4 Server"
- path = /u/systems/nt4
- public = yes
- create mode = 770
- writeable = yes
- volume = "nt4_server"
-
-[www]
- comment = "WWW System"
- path = /usr/www/http
- public = yes
- create mode = 775
- writeable = yes
- volume = "www_system"</programlisting>
-
-
-<para>The <literal>[www]</literal> share is the directory used on the Unix server to serve web pages. Samba makes the directory available to local PC users so the art department can update web pages.</para>
-
-
-
-
-
-
-
-
-
-
-
-</appendix>
+++ /dev/null
-<?xml version="1.0"?>
-<!DOCTYPE book PUBLIC
-"-//O'Reilly//DTD DBLite Safari 1.0 XML//EN"
-"/usr/local/prod/sgml/dblite/safari_future.dtd"
-[
-<!ENTITY metadata SYSTEM "metadata.xml">
-<!-- Declare external file entities -->
-<!ENTITY appa SYSTEM "appa.xml">
-<!ENTITY appb SYSTEM "appb.xml">
-<!ENTITY appc SYSTEM "appc.xml">
-<!ENTITY appd SYSTEM "appd.xml">
-<!ENTITY appe SYSTEM "appe.xml">
-<!ENTITY appf SYSTEM "appf.xml">
-<!ENTITY ch00 SYSTEM "ch00.xml">
-<!ENTITY ch01 SYSTEM "ch01.xml">
-<!ENTITY ch02 SYSTEM "ch02.xml">
-<!ENTITY ch03 SYSTEM "ch03.xml">
-<!ENTITY ch04 SYSTEM "ch04.xml">
-<!ENTITY ch05 SYSTEM "ch05.xml">
-<!ENTITY ch06 SYSTEM "ch06.xml">
-<!ENTITY ch07 SYSTEM "ch07.xml">
-<!ENTITY ch08 SYSTEM "ch08.xml">
-<!ENTITY ch09 SYSTEM "ch09.xml">
-<!ENTITY colo1 SYSTEM "colo1.xml">
-<!ENTITY cpyrt SYSTEM "copy.xml">
-]>
-<!-- Document type description -->
-<book fpi="1565924495">
- <title>Using Samba</title>
- <!-- Book metadata -->
-&metadata;
-<!-- Reference the file entities -->
-&cpyrt;
-&ch00;
-&ch01;
-&ch02;
-&ch03;
-&ch04;
-&ch05;
-&ch06;
-&ch07;
-&ch08;
-&ch09;
-&appa;
-&appb;
-&appc;
-&appd;
-&appe;
-&appf;
-&colo1;
-</book>
+++ /dev/null
-<preface id="ch00">
-<title>Preface</title>
-
-
-
-
-<para>It's nine in the morning and you've just arrived at the computer center after a refreshing night's sleep. Your pager hasn't gone off in months. Life is pretty good as a system administrator — and why shouldn't it be, with the network you're running? Two hundred identical machines, all running the same operating system. All of the printers are networked, accessible from anywhere in the building, and the auto-configuration scripts that the manufacturer supplied ensure that everyone in the company has a consistent view of the shared disks you've set up. Yes, this is the good life. You lean back and take that first delicious sip of morning coffee . . . .</para>
-
-
-<para>And then, the alarm clock jolts you out of your blissful reverie. If you're like most system administrators, this could only be a dream. Your morning probably starts with a tireless struggle to get four different computer platforms running three different operating systems simply to talk to each other — that is, if the phone ever stops ringing. Most of your users don't understand why it's so hard to access a file on another computer or to send a job to a remote printer. The logs show that the backups are late. For some reason the PCs on the second floor can't find the tape server. With all these headaches, what's a network administrator to do?</para>
-
-
-<para>Easy: take the day off, read this book, and learn Samba!</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" id="ch00-SECT-1">
-<title>The Samba Suite</title>
-
-
-<para>Samba is a suite of tools for sharing resources such as printers and files across a network. This may be a bit of an oversimplification, but Samba is really designed to make your life easier. Samba uses the Server Message Block (SMB) protocol, which is endorsed jointly by Microsoft and IBM, to communicate low-level data between Windows clients and Unix servers on a TCP/IP network.</para>
-
-
-<para>
-<indexterm id="ch00-idx-941381-0"><primary>Samba</primary><secondary>features/uses</secondary></indexterm>Four features of Samba make it extremely attractive:</para>
-
-
-<itemizedlist>
-<listitem><para>Samba speaks the same SMB protocol that Microsoft and IBM operating systems have used as their standard since DOS 3.0. This means that almost all Windows machines already understand it and there is no extra client software to install.</para></listitem>
-<listitem><para>Samba runs on a variety of platforms, including most variants of Unix, OpenVMS, OS/2, AmigaDOS, and NetWare. This means that you can use a single program on the server to provide files and printers to a community of PCs.</para></listitem>
-<listitem><para>Samba is free. There are several commercial products that duplicate Samba's features, and some of them are quite expensive. Samba offers you an alternative to packages that could gobble up a significant portion of your IS budget. Samba is distributed under the GNU General Public License (GPL), and is considered by its authors to be <firstterm>Open Source</firstterm> software. In other words, you can freely download both the application and the accompanying source code to your computer, and even improve on the original Samba programs if you like.</para></listitem>
-<listitem><para>Samba administration is centralized on the server. You don't have to visit every one of your machines, floppy or CD-ROM in hand, to upgrade the client software.</para></listitem>
-</itemizedlist>
-
-<para>Samba is a complete solution for local area networks (LANs) of all sizes—everything from the two-computer home network to corporate installations with hundreds of nodes. Samba is simple to set up and to administer, and presents itself as a transparent network environment that offers users access to all of the resources they need to get their work done. Once you've set it up, Samba will let you:</para>
-
-
-<itemizedlist>
-<listitem><para>Serve Unix files to Windows, OS/2, and other OS clients</para></listitem>
-<listitem><para>Allow Unix clients to access PC files</para></listitem>
-<listitem><para>Serve network printers to Windows clients</para></listitem>
-<listitem><para>Provide name services (broadcast and WINS)</para></listitem>
-<listitem><para>Allow browsing of network resources from Windows clients</para></listitem>
-<listitem><para>Create Windows workgroups or domains</para></listitem>
-<listitem><para>Enforce username and password authentication of clients</para></listitem>
-</itemizedlist>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" id="ch00-SECT-2">
-<title>Audience for this Book</title>
-
-
-<para>The primary audience of this book is Unix administrators who need to support PCs on their network, and anyone who needs to provide a Unix server in a PC environment. But we don't want to burden you with an endless series of arcane system administration tools and vocabulary. While we assume you are familiar with basic Unix system administration, we will <emphasis>not</emphasis> assume you are a networking expert. We'll do our best along the way to help out with unusual definitions and terms.</para>
-
-
-<para>Because we don't assume a tremendous amount of experience with Microsoft Windows, we will go through the PC side of the installation task in considerable detail and give examples for both Windows 95/98 and Windows NT, which are subtly different. For the Unix side, we will give examples for common Unix operating systems, such as Linux 2.0 or Solaris 2.6.</para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" id="ch00-SECT-3">
-<title>Samba Installation Checklist</title>
-
-
-<para>Before you get started, you should have:</para>
-
-
-<itemizedlist>
-<listitem><para><indexterm id="ch00-idx-941383-0"><primary>Samba</primary><secondary>version 2.0.5</secondary></indexterm><indexterm id="ch00-idx-941383-1"><primary>Samba</primary><secondary>distribution</secondary></indexterm><indexterm id="ch00-idx-941383-2"><primary>URLs (uniform resource locators)</primary><secondary>Samba</secondary><tertiary>distribution</tertiary></indexterm>
-
-<!-- CD-ROM REFERENCE COMMENTED OUT FOR SAFARI VERSION OF THIS TITLE.
-
-Either the CD-ROM from this book (which contains both source and binary distributions of Samba 2.0.5) or the latest Samba distribution, which you can download directly off the Internet at <systemitem role="url">http://www.samba.org/</systemitem>. </para>
-
--->
-
-The latest Samba distribution, which you can download directly off the Internet at <systemitem role="url">http://www.samba.org/</systemitem>.</para></listitem>
-<listitem><para>The names and IP addresses of the servers and client machines you plan to use, the netmask of your network, and the names and IP addresses of your domain name (DNS) servers.</para></listitem>
-</itemizedlist>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" id="ch00-SECT-4">
-<title>Organization</title>
-
-
-<para>The book can be roughly divided into two sections: Samba installation (<link linkend="ch01-48078">Chapter 1</link> through <link linkend="SAMBA-CH-3">Chapter 3</link>) and Samba configuration and optimization (<link linkend="ch04-21486">Chapter 4</link> through <link linkend="SAMBA-CH-9">Chapter 9</link>). Here is a detailed breakdown of each of the chapters:</para>
-
-
-<variablelist>
-<varlistentry><term><link linkend="ch01-48078">Chapter 1</link></term>
-<listitem><para>This chapter introduces each of the Samba components and gives a brief overview of NetBIOS and Windows networking.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-CH-2">Chapter 2</link></term>
-<listitem><para>This chapter covers configuring, compiling, installing, and testing the Samba server on a Unix platform.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-CH-3">Chapter 3</link></term>
-<listitem><para>This chapter explains how to configure Microsoft Windows 95/98 and NT 4.0 clients to participate in an SMB network. It also gives a brief introduction to the SMB protocol in action.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="ch04-21486">Chapter 4</link></term>
-<listitem><para>This chapter gets you up to speed with the individual parts of the Samba configuration file and shows you how to configure disk services.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-CH-5">Chapter 5</link></term>
-<listitem><para>This chapter continues the discussion of disk options and examines browsing with Samba.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-CH-6">Chapter 6</link></term>
-<listitem><para>This chapter discusses how to set up users, introduces you to Samba security, and shows you how to work with encrypted and non-encrypted passwords. We also discuss how to set up Samba as a primary domain controller for Windows 95/98 and NT clients.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-CH-7">Chapter 7</link></term>
-<listitem><para>This chapter discusses printer and Windows Internet Naming Service (WINS) setup with Samba.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-CH-8">Chapter 8</link></term>
-<listitem><para>This chapter bundles several miscellaneous activities associated with Samba, such as configuring Samba shares for programmers, internationalization issues, and backing up with <emphasis>smbtar</emphasis>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-CH-9">Chapter 9</link></term>
-<listitem><para>If you have problems installing Samba, this comparatively large chapter is packed with troubleshooting hints and strategies as to what might be going wrong.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-AP-A">Appendix A</link></term>
-<listitem><para>This appendix shows you the nitty-gritty of setting up Samba with Secure Sockets Layers (SSL) connections between the server and its clients.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-AP-B">Appendix B</link></term>
-<listitem><para>This appendix discusses various techniques to optimize Samba processing on your network.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-AP-C">Appendix C</link></term>
-<listitem><para>This appendix covers each of the options used in the <filename>smb.conf</filename> file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-AP-D">Appendix D</link></term>
-<listitem><para>Each of the server daemons and tools that make up the Samba suite are covered in this appendix. In addition, we provide a list of mirror sites on the Internet from which Samba can be downloaded.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-AP-E">Appendix E</link></term>
-<listitem><para>This appendix explains how to download the latest version of Samba with CVS.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><link linkend="SAMBA-AP-F">Appendix F</link></term>
-<listitem><para>This appendix provides a large-scale Samba configuration file, which you might find in place at a large corporation. We have embedded comments in the file to explain the more arcane options.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" id="ch00-SECT-5">
-<title>Conventions</title>
-
-
-<para>The following font conventions are followed throughout this book:</para>
-
-
-<variablelist>
-<varlistentry><term>Italic </term>
-<listitem><para>Filenames, file extensions, URLs, Internet addresses, executable files, commands, and emphasis.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>Constant Width</literal> </term>
-<listitem><para>Samba configuration options and other code that appear in the text, and command-line information that should be typed verbatim on the screen.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><userinput>Bold Constant Width</userinput> </term>
-<listitem><para>Commands that are entered by the user, and new configuration options that we wish to bring to the attention of the reader.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><replaceable>Constant Width Italic</replaceable></term>
-<listitem><para>Replaceable content in code and command-line information.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<tip id="ch00-NOTE-0" role="ora">
-<para>This icon designates a note, which is an important aside to the nearby text.</para>
-
-</tip>
-
-<warning id="ch00-NOTE-1" role="ora">
-<para>This icon designates a warning related to the nearby text.</para>
-
-</warning>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" id="ch00-SECT-6">
-<title>Request for Comments</title>
-
-
-<para>As a reader of this book, you can help us to improve the next edition. If you find errors, inaccuracies, or typographical errors anywhere in the book, please let us at O'Reilly know about them. Also, if you find any misleading statements or confusing explanations, let us know that as well. Send all correspondence to:</para>
-
-
-<simplelist>
-
-<member>O'Reilly & Associates</member>
-
-<member>101 Morris Street</member>
-
-<member>Sebastopol, CA 95472</member>
-
-<member>1-800-998-9938 (in the U.S. or Canada)</member>
-
-<member>1-707-829-0515 (international/local)</member>
-
-<member>1-707-829-0104 (fax)</member>
-
-<member><email>bookquestions@ora.com</email></member>
-
-</simplelist>
-
-
-<para>Please let us know what we can do to make the book more helpful to you. We take your comments seriously, and will do whatever we can to make this book as useful as it can be.</para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" id="ch00-SECT-7">
-<title>Acknowledgments</title>
-
-
-<para>Robert Eckstein</para>
-
-
-<blockquote>
-<para>I'd first like to recognize Dave Collier-Brown and Peter Kelly for all their help in the creation of this book. I'd also like to thank each of the technical reviewers that helped polish this book into shape on such short notice: Matthew Temple, Jeremy Allison, and of course Andrew Tridgell. Andrew and Jeremy deserve special recognition, not only for creating such a wonderful product, but for providing a tireless amount of support in the final phase of this book—hats off to you, guys! A warm hug goes out to my wife Michelle, who once again put up with a husband loaded down with too much caffeine on a tight schedule. Thanks to Dave Sifry and the people at LinuxCare, San Francisco, for hosting me on such short notice for Andrew Tridgell's visit. And finally, a huge amount of thanks to our editor, Andy Oram, who (very) patiently helped guide this book through its many stages until we got it right.</para>
-</blockquote>
-
-
-<para>David Collier-Brown</para>
-
-
-<blockquote>
-<para>I'd especially like to thank Joyce, who put up with me during the sometimes exciting development of the book. My thanks to Andy Oram, who was kind enough to provide the criticism that allowed me to contribute; the crew at Opcom who humored the obvious madman in their midst; and Ian MacMillan, who voluntarily translated several of my early drafts from nerd to English. I would also like to give special thanks to Perry Donham, Drew Sullivan, and Jerry DeRoo.</para>
-</blockquote>
-
-
-<para>Peter Kelly</para>
-
-
-<blockquote>
-<para>A few people really made this book possible, and I have to bow to them. Dave Collier-Brown, and then Bob Eckstein, took over my part of this project with style and professionalism and I can't explain how much I owe them for the great work that came out of it. Editor Andy Oram is by far the most patient and pleasant person I have met. Also, I don't think that I would have been involved in this book without the help of Xavier Cazin from O'Reilly, who originally came to me asking for a proposal after reading my Linux Journal article. I also would like to thank all of the JDP.COM consultants ( Jerry, Peggyann, Drew, Gord, Jerome, Mark, Rick—too many to list!) for allowing me to continue to work with them. I thank the O'Reilly staff that I have worked with as well; they are a great bunch of people. Also, thanks to the Samba Team for making Samba in the first place. And most importantly, Kate McKay, for staying with me this long!</para>
-</blockquote>
-
-
-<para>We would especially like to give thanks to Perry Donham for helping mold the first draft of this book. Although Perry was unable to contribute to subsequent drafts, his material was essential to getting this book off on the right foot. In addition, some of the browsing material came from text originally written by Dan Shearer for O'Reilly.</para>
-
-
-<para>We are deeply indebted to the production department at O'Reilly for another fantastic job. Sarah Jane Shangraw worked long hours accommodating our seemingly endless edits, and Rob Romano tirelessly edited our images again and again until they were perfect. Special thanks also to Claire Cloutier LeBlanc, Rhon Porter, and Mike Sierra for their help—we couldn't have done it without any of them. It is largely through their collective efforts that this book arrived to you in November 1999 instead of November 2000.</para>
-</sect1>
-
-
-
-
-
-
-
-
-</preface>
+++ /dev/null
-<chapter label="1" id="ch01-48078">
-<title>Learning the Samba</title>
-
-
-
-
-<para>
-<indexterm id="ch01-idx-951466-0" class="startofrange"><primary>Samba</primary></indexterm>If you are a typical system administrator, then you know what it means to be <emphasis>swamped</emphasis> with work. Your daily routine is filled with endless hardware incompatibility issues, system outages, data backup problems, and a steady stream of angry users. So adding another program to the mix of tools that you have to maintain may sound a bit perplexing. However, if you're determined to reduce the complexity of your work environment, as well as the workload of keeping it running smoothly, Samba may be the tool you've been waiting for.</para>
-
-
-<para>A case in point: one of the authors of this book used to look after 70 Unix developers sharing 5 Unix servers. His neighbor administered 20 Windows 3.1 users and 5 OS/2 and Windows NT servers. To put it mildly, the Windows 3.1 administrator was swamped. When he finally left—and the domain controller melted—Samba was brought to the rescue. Our author quickly replaced the Windows NT and OS/2 servers with Samba running on a Unix server, and eventually bought PCs for most of the company developers. However, he did the latter without hiring a new PC administrator; the administrator now manages one centralized Unix application instead of fifty distributed PCs.</para>
-
-
-<para>If you know you're facing a problem with your network and you're sure there is a better way, we encourage you to start reading this book. Or, if you've heard about Samba and you want to see what it can do for you, this is also the place to start. We'll get you started on the path to understanding Samba and its potential. Before long, you can provide Unix services to all your Windows machines—all without spending tons of extra time or money. Sound enticing? Great, then let's get started.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.1" id="ch01-28119">
-<title>What is Samba?</title>
-
-
-<para>Samba is a suite of Unix applications that speak the <indexterm id="ch01-idx-951468-0"><primary>Server Message Block</primary><see>SMB</see></indexterm>
-<indexterm id="ch01-idx-951468-1"><primary>SMB (Server Message Block)</primary></indexterm>SMB (Server Message Block) protocol. Many operating systems, including Windows and OS/2, use SMB to perform client-server networking. By supporting this protocol, Samba allows Unix servers to get in on the action, communicating with the same networking protocol as Microsoft Windows products. Thus, a Samba-enabled Unix machine can masquerade as a server on your Microsoft network and offer the following services:</para>
-
-
-<itemizedlist>
-<listitem><para>
-<indexterm id="ch01-idx-951506-0"><primary>services</primary><secondary>performed by Samba</secondary></indexterm>Share one or more filesystems</para></listitem>
-<listitem><para>Share printers installed on both the server and its clients</para></listitem>
-<listitem><para>Assist clients with Network Neighborhood browsing</para></listitem>
-<listitem><para>Authenticate clients logging onto a Windows domain</para></listitem>
-<listitem><para>Provide or assist with WINS name server resolution</para></listitem>
-</itemizedlist>
-
-<para>Samba is the brainchild of <indexterm id="ch01-idx-951508-0"><primary>Tridgell, Andrew</primary></indexterm>Andrew Tridgell, who currently heads the Samba development team from his home of Canberra, Australia. The project was born in 1991 when Andrew created a fileserver program for his local network that supported an odd DEC protocol from Digital Pathworks. Although he didn't know it at the time, that protocol later turned out to be SMB. A few years later, he expanded upon his custom-made SMB server and began distributing it as a product on the Internet under the name SMB Server. However, Andrew couldn't keep that name—it already belonged to another company's product—so he tried the following Unix renaming approach:</para>
-
-<programlisting>grep -i 's.*m.*b' /usr/dict/words<indexterm id="ch01-idx-951514-0"><primary>Samba</primary><secondary>origin of name</secondary></indexterm></programlisting>
-
-
-<para>And the response was:</para>
-
-
-<programlisting>salmonberry samba sawtimber scramble</programlisting>
-
-
-<para>Thus, the name "Samba" was born.<footnote label="1" id="ch01-pgfId-946532">
-
-
-<para>Which is a good thing, because our marketing people highly doubt you would have picked up a book called "Using Salmonberry"!</para>
-
-
-</footnote></para>
-
-
-<para>Today, the Samba suite revolves around a pair of <indexterm id="ch01-idx-951515-0"><primary>Unix</primary><secondary>daemons</secondary></indexterm>
-<indexterm id="ch01-idx-951515-1"><primary>daemons</primary><secondary>Unix</secondary></indexterm>Unix daemons that provide <indexterm id="ch01-idx-951518-0"><primary>shared resources</primary><see>shares</see></indexterm>shared resources—or <firstterm>shares</firstterm>—to SMB clients on the network. (Shares are sometimes called <indexterm id="ch01-idx-951527-0"><primary>services</primary><seealso>shares</seealso></indexterm>s<firstterm>ervices</firstterm> as well.) These daemons are:</para>
-
-
-<variablelist>
-<varlistentry><term>smbd</term>
-<listitem><para>
-<indexterm id="ch01-idx-951528-0"><primary>smbd daemon</primary></indexterm>A daemon that allows file and printer sharing on an SMB network and provides authentication and authorization for SMB clients.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>nmbd</term>
-<listitem><para>
-<indexterm id="ch01-idx-951529-0"><primary>nmbd daemon</primary></indexterm>A daemon that looks after the <indexterm id="ch01-idx-951530-0"><primary>WINS (Windows Internet Name Service)</primary></indexterm>Windows Internet Name Service (WINS), and assists with browsing.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>Samba is currently maintained and extended by a group of volunteers under the active supervision of Andrew Tridgell. Like the Linux operating system, Samba is considered <firstterm>Open Source software </firstterm>
-<indexterm id="ch01-idx-951531-0"><primary>Open Source Software (OSS)</primary></indexterm>
-<indexterm id="ch01-idx-951531-1"><primary>OSS (Open Source Software)</primary></indexterm>(OSS) by its authors, and is distributed under the <indexterm id="ch01-idx-951532-0"><primary>GNU General Public License (GPL)</primary></indexterm>GNU General Public License (GPL). Since its inception, development of Samba has been sponsored in part by the <indexterm id="ch01-idx-951533-0"><primary>Australian National University</primary></indexterm>Australian National University, where Andrew Tridgell earned his Ph.D.<footnote label="2" id="ch01-pgfId-946542">
-
-
-<para>At the time of this printing, Andrew had completed his Ph.D. work and had joined San Francisco-based LinuxCare.</para>
-
-
-</footnote> In addition, some development has been sponsored by independent vendors such as <indexterm id="ch01-idx-951534-0"><primary>Whistle</primary></indexterm>Whistle and <indexterm id="ch01-idx-951535-0"><primary>SGI</primary></indexterm>SGI. It is a true testament to Samba that both commercial and non-commercial entities are prepared to spend money to support an Open Source effort.</para>
-
-
-<para>
-<indexterm id="ch01-idx-951536-0"><primary>Microsoft</primary></indexterm>Microsoft has also contributed materially by putting forward its definition of SMB and the Internet-savvy <indexterm id="ch01-idx-951537-0"><primary>CIFS (Common Internet File System)</primary></indexterm>
-<indexterm id="ch01-idx-951537-1"><primary>CIFS (Common Internet File System)</primary><seealso>SMB/CIFS protocol</seealso></indexterm>Common Internet File System (CIFS), as a public <indexterm id="ch01-idx-951538-0"><primary>Request for Comments (RFC)</primary></indexterm>
-<indexterm id="ch01-idx-951538-1"><primary>RFC (Request for Comments)</primary></indexterm>Request for Comments (RFC), a standards document. The CIFS protocol is Microsoft's renaming of future versions of the SMB protocol that will be used in Windows products—the two terms can be used interchangeably in this book. Hence, you will often see the protocol written as "<indexterm id="ch01-idx-951539-0"><primary>SMB/CIFS protocol</primary></indexterm>SMB/CIFS."</para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.2" id="ch01-SECT-2">
-<title>What Can Samba Do For Me?</title>
-
-
-<para>As explained earlier, Samba can help Windows and Unix machines coexist in the same network. However, there are some specific reasons why you might want to set up a Samba server on your network:</para>
-
-
-<itemizedlist>
-<listitem><para>
-<indexterm id="ch01-idx-951583-0"><primary>Samba</primary><secondary>reasons for using</secondary></indexterm>You don't want to pay for—or can't afford—a full-fledged Windows NT server, yet you still need the functionality that one provides.</para></listitem>
-<listitem><para>You want to provide a common area for data or user directories in order to transition from a Windows server to a Unix one, or vice versa.</para></listitem>
-<listitem><para>You want to be able to share printers across both Windows and Unix workstations.</para></listitem>
-<listitem><para>You want to be able to access NT files from a Unix server.</para></listitem>
-</itemizedlist>
-
-<para>Let's take a quick tour of Samba in action. Assume that we have the following basic network configuration: a Samba-enabled Unix machine, to which we will assign the name <literal>hydra</literal>, and a pair of Windows clients, to which we will assign the names <literal>phoenix</literal> and <literal>chimaera</literal>, all connected via a local area network (LAN). Let's also assume that <literal>hydra</literal> also has a local inkjet printer connected to it, <literal>lp</literal>, and a disk share named <literal>network</literal>—both of which it can offer to the other two machines. A graphic of this network is shown in <link linkend="ch01-45964">Figure 1.1</link>.</para>
-
-
-<figure label="1.1" id="ch01-45964">
-<title>A simple network setup with a Samba server</title>
-
-<graphic width="502" depth="209" fileref="figs/sam.0101.gif"></graphic>
-</figure>
-
-<para>In this network, each of the computers listed share the same <firstterm>workgroup</firstterm>
-<indexterm id="ch01-idx-951584-0"><primary>workgroups</primary></indexterm>. A workgroup is simply a group nametag that identifies an arbitrary collection of computers and their resources on an <indexterm id="ch01-idx-951585-0"><primary>SMB (Server Message Block)</primary><secondary>networks</secondary></indexterm>SMB network. There can be several workgroups on the network at any time, but for our basic network example, we'll have only one: the SIMPLE workgroup.</para>
-
-
-<sect2 role="" label="1.2.1" id="ch01-SECT-2.1">
-<title>Sharing a Disk Service</title>
-
-
-<para>
-<indexterm id="ch01-idx-951617-0" class="startofrange"><primary>disk shares</primary></indexterm>If <indexterm id="ch01-idx-951876-0"><primary>sharing</primary><secondary>disks</secondary><see>disk shares</see></indexterm>
-<indexterm id="ch01-idx-951876-1"><primary>sharing</primary><secondary>printers</secondary><see>print shares</see></indexterm>everything is properly configured, we should be able to see the Samba server, <literal>hydra</literal>, through the Network Neighborhood of the <literal>phoenix</literal> Windows desktop. In fact, <link linkend="ch01-60493">Figure 1.2</link> shows the Network Neighborhood of the <literal>phoenix</literal> computer, including <literal>hydra</literal> and each of the computers that reside in the SIMPLE workgroup. Note the Entire Network icon at the top of the list. As we just mentioned, there can be more than one workgroup on an SMB network at any given time. If a user clicks on the <indexterm id="ch01-idx-951586-0"><primary>Entire Network icon</primary></indexterm>Entire Network icon, he or she will see a list of all the workgroups that currently exist on the network.</para>
-
-
-<figure label="1.2" id="ch01-60493">
-<title>The Network Neighborhood directory</title>
-
-<graphic width="502" depth="174" fileref="figs/sam.0102.gif"></graphic>
-</figure>
-
-<para>We can take a closer look at the <literal>hydra</literal> server by double-clicking on its icon. This contacts <literal>hydra</literal> itself and requests a list of its <firstterm>shares</firstterm>—the file and printer resources—that the machine provides. In this case, there is a printer entitled <literal>lp</literal> and a disk share entitled <literal>network</literal> on the server, as shown in <link linkend="ch01-76011">Figure 1.3</link>. Note that the Windows display shows hostnames in mixed case (Hydra). <indexterm id="ch01-idx-951589-0"><primary>case sensitivity</primary><secondary>hostnames and</secondary></indexterm>Case is irrelevant in <indexterm id="ch01-idx-951588-0"><primary>hostnames</primary><secondary>case sensitivity and</secondary></indexterm>hostnames, so you may see hydra, Hydra, and HYDRA in various displays or command output, but they all refer to a single system. Thanks to Samba, Windows 98 sees the Unix server as a valid SMB server, and can access the <literal>network</literal> folder as if it were just another system folder.</para>
-
-
-<figure label="1.3" id="ch01-76011">
-<title>Shares available on the hydra sever as viewed from phoenix</title>
-
-<graphic width="502" depth="148" fileref="figs/sam.0103.gif"></graphic>
-</figure>
-
-<para>One popular feature of Windows 95/98/NT is that you can map a letter-drive to a known network directory using the <indexterm id="ch01-idx-951590-0"><primary>Map Network Drive option</primary></indexterm>
-<indexterm id="ch01-idx-951590-1"><primary>Windows Explorer, Map Network Drive option</primary></indexterm>
-<indexterm id="ch01-idx-951590-2"><primary>network drives, mapping</primary></indexterm>
-<indexterm id="ch01-idx-951590-3"><primary>mapping</primary><secondary>network drives</secondary></indexterm>Map Network Drive option in the Windows Explorer.<footnote label="3" id="ch01-pgfId-941061">
-
-
-<para>You can also right-click on the shared resource in the <indexterm id="ch01-idx-951603-0"><primary>Network Neighborhood window</primary><secondary> mapping network drives via</secondary></indexterm>Network Neighborhood, and then select the Map Network Drive menu item.</para>
-
-
-</footnote> Once you do so, your applications can access the folder across the network with a standard <indexterm id="ch01-idx-951592-0"><primary>drive letters, mapping</primary></indexterm>drive letter. Hence, you can store data on it, install and run programs from it, and even password-protect it against unwanted visitors. See <link linkend="ch01-55465">Figure 1.4</link> for an example of mapping a letter-drive to a network directory.</para>
-
-
-<figure label="1.4" id="ch01-55465">
-<title>Mapping a network drive to a Windows letter-drive</title>
-
-<graphic width="502" depth="336" fileref="figs/sam.0104.gif"></graphic>
-</figure>
-
-<para>Take a look at the Path: entry in the dialog box of <link linkend="ch01-55465">Figure 1.4</link>. An equivalent way to represent a directory on a network machine is by using two <indexterm id="ch01-idx-951593-0"><primary>backslashes, two (\\) in directories</primary></indexterm>
-<indexterm id="ch01-idx-951593-1"><primary>\\ (backslashes, two) in directories</primary></indexterm>backslashes, followed by the name of the networked machine, another backslash, and the networked directory of the machine, as shown below:</para>
-
-
-<programlisting><emphasis>\\</emphasis><replaceable>network-machine</replaceable><emphasis>\</emphasis><replaceable>directory</replaceable></programlisting>
-
-
-<para>This is known as the <firstterm>UNC</firstterm>
-<indexterm id="ch01-idx-951594-0"><primary>UNC (Universal Naming Convention)</primary></indexterm>
-<indexterm id="ch01-idx-951594-1"><primary>Universal Naming Convention (UNC)</primary></indexterm> (Universal Naming Convention) in the Windows world. For example, the dialog box in <link linkend="ch01-55465">Figure 1.4</link> represents the network directory on the <literal>hydra</literal> server as:</para>
-
-
-<programlisting>\\HYDRA\<replaceable>network</replaceable></programlisting>
-
-
-<para>If this looks somewhat familiar to you, you're probably thinking of <firstterm>uniform resource locators</firstterm>
-<indexterm id="ch01-idx-951607-0"><primary>uniform resource locators (URLs)</primary></indexterm>
-<indexterm id="ch01-idx-951607-1"><primary>URLs (uniform resource locators)</primary></indexterm> (URLs), which are addresses that web browsers such as Netscape Navigator and Internet Explorer use to resolve machines across the Internet. Be sure not to confuse the two: web browsers typically use <indexterm id="ch01-idx-951608-0"><primary>forward slashes in web browser addresses</primary></indexterm>forward slashes instead of back slashes, and they precede the initial slashes with the <indexterm id="ch01-idx-951611-0"><primary>data transfer protocol</primary></indexterm>data transfer protocol (i.e., <indexterm id="ch01-idx-951612-0"><primary>FTP (File Transfer Protocol)</primary></indexterm>ftp, <indexterm id="ch01-idx-951613-0"><primary>http</primary></indexterm>http) and a <indexterm id="ch01-idx-951610-0"><primary>colon (:) in web browser addresses</primary></indexterm>
-<indexterm id="ch01-idx-951610-1"><primary>: (colon)</primary></indexterm>colon (:). In reality, URLs and UNCs are two completely separate things.</para>
-
-
-<para>Once the network drive is set up, Windows and its programs will behave as if the networked directory was a fixed disk. If you have any applications that support <indexterm id="ch01-idx-952014-0"><primary>multi-user functionality, legal agreements and</primary></indexterm>
-<indexterm id="ch01-idx-952014-1"><primary>legal agreements covering multi-user functionality</primary></indexterm>multiuser functionality on a network, you can install those programs on the network drive.<footnote label="4" id="ch01-pgfId-952017">
-
-
-<para>Be warned that many end-user license agreements forbid installing a program on a network such that multiple clients can access it. Check the legal agreements that accompany the product to be absolutely sure.</para>
-
-
-</footnote> <link linkend="ch01-32686">Figure 1.5</link> shows the resulting network drive as it would appear with other storage devices in the Windows 98 client. Note the pipeline attachment in the icon for the G: drive; this indicates that it is a network drive instead of a fixed drive.</para>
-
-
-<figure label="1.5" id="ch01-32686">
-<title>The Network directory mapped to the client letter-drive G</title>
-
-<graphic width="502" depth="224" fileref="figs/sam.0105.gif"></graphic>
-</figure>
-
-<para>From our Windows NT Workstation machine, <literal>chimaera</literal>, Samba looks almost identical to Windows 98. <link linkend="ch01-29255">Figure 1.6</link> shows the same view of the <literal>hydra</literal> server from the Windows NT 4.0 Network Neighborhood. Setting up the network drive using the Map Network Drive option in Windows NT Workstation 4.0 would have identical results as well.</para>
-
-
-<figure label="1.6" id="ch01-29255">
-<indexterm id="ch01-idx-951618-0" class="endofrange" startref="ch01-idx-951617-0"/><title>Shares available on hydra (viewed from chimaera) </title>
-
-<graphic width="502" depth="141" fileref="figs/sam.0106.gif"></graphic>
-</figure>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.2.2" id="ch01-SECT-2.2">
-<title>Sharing a Printer</title>
-
-
-<para>
-<indexterm id="ch01-idx-951620-0" class="startofrange"><primary>print shares</primary></indexterm>
-<indexterm id="ch01-idx-951620-1"><primary>printers</primary><secondary>sharing</secondary><see>print shares</see></indexterm>You probably noticed that the printer <literal>lp</literal> appeared under the available shares for <literal>hydra</literal> in <link linkend="ch01-76011">Figure 1.3</link>. This indicates that the Unix server has a printer that can be shared by the various SMB clients in the workgroup. Data sent to the printer from any of the clients will be spooled on the Unix server and printed in the order it is received.</para>
-
-
-<para>
-<indexterm id="ch01-idx-951636-0"><primary>print shares</primary><secondary>setting up on Windows client</secondary></indexterm>Setting up a Samba-enabled printer on the Windows side is even easier than setting up a disk share. By double-clicking on the printer and identifying the manufacturer and model, you can install a driver for this printer on the Windows client. Windows can then properly format any information sent to the network printer and access it as if it were a local printer (we show you how to do this later in the chapter). <link linkend="ch01-46265">Figure 1.7</link> shows the resulting network printer in the Printers window of Windows 98. Again, note the pipeline attachment below the printer, which identifies it as being on a network.</para>
-
-
-<figure label="1.7" id="ch01-46265">
-<title>A network printer available on hydra (viewed from chimaera)</title>
-
-<graphic width="502" depth="223" fileref="figs/sam.0107.gif"></graphic>
-</figure>
-
-<sect3 role="" label="1.2.2.1" id="ch01-SECT-2.2.1">
-<title>Seeing things from the Unix side</title>
-
-
-<para>As mentioned earlier, Samba appears in Unix as a set of <indexterm id="ch01-idx-951638-0"><primary>daemons</primary><secondary>viewing</secondary></indexterm>
-<indexterm id="ch01-idx-951638-1"><primary>viewing daemons</primary></indexterm>
-<indexterm id="ch01-idx-951638-2"><primary>messages</primary><secondary sortas="daemons, reading">from daemons, reading</secondary></indexterm>
-<indexterm id="ch01-idx-951638-3"><primary>daemons</primary><secondary>messages generated by, reading</secondary></indexterm>daemon programs. You can view them with the Unix <literal>ps</literal> and <literal>netstat</literal> commands, you can read any messages they generate through custom debug files or the Unix <literal>syslog</literal> (depending on how Samba is set up), and you can configure it from a single Samba properties file: <emphasis>smb.conf</emphasis>
-<indexterm id="ch01-idx-951639-0"><primary>smb.conf (Samba configuration) file</primary></indexterm>. In addition, if you want to get an idea of what each of the <indexterm id="ch01-idx-951640-0"><primary>daemons</primary><secondary>status report</secondary></indexterm>
-<indexterm id="ch01-idx-951640-1"><primary>status report on Samba</primary></indexterm>daemons are doing, Samba has a program called <emphasis>smbstatus</emphasis>
-<indexterm id="ch01-idx-951641-0"><primary>smbstatus program</primary></indexterm> that will lay it all on the line. Here is how it works:</para>
-
-
-<programlisting># <emphasis role="bold">smbstatus</emphasis>
-Samba version 2.0.4
-Service uid gid pid machine
-----------------------------------------------
-network davecb davecb 7470 phoenix (192.168.220.101) Sun May 16
-network davecb davecb 7589 chimaera (192.168.220.102) Sun May 16
-
-Locked files:
-Pid DenyMode R/W Oplock Name
---------------------------------------------------
-7589 DENY_NONE RDONLY EXCLUSIVE+BATCH /home/samba/quicken/inet/common/system/help.bmp Sun May 16 21:23:40 1999
-7470 DENY_WRITE RDONLY NONE /home/samba/word/office/findfast.exe
-Sun May 16 20:51:08 1999
-7589 DENY_WRITE RDONLY EXCLUSIVE+BATCH /home/samba/quicken/lfbmp70n.dll Sun May 16 21:23:39 1999
-7589 DENY_WRITE RDWR EXCLUSIVE+BATCH /home/samba/quicken/inet/qdata/runtime.dat Sun May 16 21:23:41 1999
-7470 DENY_WRITE RDONLY EXCLUSIVE+BATCH /home/samba/word/office/osa.exe
-Sun May 16 20:51:09 1999
-7589 DENY_WRITE RDONLY NONE /home/samba/quicken/qversion.dll Sun May 16 21:20:33 1999
-7470 DENY_WRITE RDONLY NONE /home/samba/quicken/qversion.dll Sun May 16 20:51:11 1999
-
-Share mode memory usage (bytes):
- 1043432(99%) free + 4312(0%) used + 832(0%) overhead = 1048576(100%) total</programlisting>
-
-
-<para>The Samba status from this output provides three sets of data, each divided into separate sections. The first section tells which systems have <indexterm id="ch01-idx-951646-0"><primary>connected systems, status of</primary></indexterm>connected to the Samba server, identifying each client by its machine name (<literal>phoenix</literal> and <literal>chimaera</literal>) and IP address. The second section reports the name and status of the <indexterm id="ch01-idx-951647-0"><primary>files</primary><secondary sortas="use, status of">in use, status of</secondary></indexterm>files that are currently in use on a share on the server, including the read/write status and any <indexterm id="ch01-idx-951648-0"><primary>locks/locking files</primary></indexterm>locks on the files. Finally, Samba reports the amount of <indexterm id="ch01-idx-951649-0"><primary>memory, status of</primary></indexterm>memory it has currently allocated to the shares that it administers, including the amount actively used by the shares plus additional overhead. (Note that this is not the same as the total amount of memory that the <emphasis>smbd</emphasis> or <emphasis>nmbd</emphasis> processes are using.)</para>
-
-
-<para>Don't worry if you don't understand these statistics; they will become easier to understand as you move through the<indexterm id="ch01-idx-951621-0" class="endofrange" startref="ch01-idx-951620-0"/> book.<indexterm id="ch01-idx-951467-0" class="endofrange" startref="ch01-idx-951466-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.3" id="ch01-88536">
-<title>Getting Familiar with a SMB/CIFS Network</title>
-
-
-<para>
-<indexterm id="ch01-idx-951651-0" class="startofrange"><primary>SMB/CIFS protocol</primary><secondary>network and</secondary></indexterm>Now that you have had a brief tour of Samba, let's take some time to get familiar with Samba's adopted environment: an SMB/CIFS network. Networking with SMB is significantly different from working with a Unix <indexterm id="ch01-idx-951650-0"><primary>TCP/IP networking protocol</primary></indexterm>TCP/IP network, because there are several new concepts to learn and a lot of information to cover. First, we will discuss the basic concepts behind an SMB network, followed by some Microsoft implementations of it, and finally we will show you where a Samba server can and cannot fit into the picture.</para>
-
-
-<sect2 role="" label="1.3.1" id="ch01-SECT-3.1">
-<title>Understanding NetBIOS</title>
-
-
-<para>To begin, let's step back in time. In 1984, IBM authored a simple <indexterm id="ch01-idx-951659-0"><primary>API (application programming interface)</primary></indexterm>application programming interface (API) for networking its computers called the <firstterm>Network Basic Input/Output System </firstterm>
-<indexterm id="ch01-idx-951660-0"><primary>NetBIOS (Network Basic Input/Output System)</primary></indexterm>
-<indexterm id="ch01-idx-951660-1"><primary>Network Basic Input/Output System</primary><see>NetBIOS</see></indexterm>(NetBIOS). The NetBIOS API provided a rudimentary design for an application to connect and share data with other computers.</para>
-
-
-<para>It's helpful to think of the NetBIOS API as networking extensions to the standard BIOS API calls. With BIOS, each low-level call is confined to the hardware of the local machine and doesn't need any help traveling to its destination. NetBIOS, however, originally had to exchange instructions with computers across IBM PC or Token Ring networks. It therefore required a low-level transport protocol to carry its requests from one computer to the next.</para>
-
-
-<para>In late 1985, IBM released one such protocol, which it merged with the NetBIOS API to become the <firstterm>NetBIOS Extended User Interface</firstterm>
-<indexterm id="ch01-idx-951661-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>Extended User Interface</secondary><see>NetBEUI</see></indexterm>
-<indexterm id="ch01-idx-951661-1"><primary>NetBEUI (NetBIOS Extended User Interface)</primary></indexterm> (<emphasis>NetBEUI</emphasis>). NetBEUI was designed for small local area networks (LANs), and it let each machine claim a name (up to 15 characters) that wasn't already in use on the network. By a "small LAN," we mean fewer than 255 nodes on the network—which was considered a practical restriction in 1985!</para>
-
-
-<para>The NetBEUI protocol was very popular with networking applications, including those running under Windows for Workgroups. Later, implementations of NetBIOS over Novell's IPX networking protocols also emerged, which competed with NetBEUI. However, the networking protocols of choice for the burgeoning Internet community were TCP/IP and UDP/IP, and implementing the NetBIOS APIs over those protocols soon became a necessity.</para>
-
-
-<para>Recall that <indexterm id="ch01-idx-951666-0"><primary>TCP/IP networking protocol</primary><secondary>compared with NetBIOS</secondary></indexterm>TCP/IP uses numbers to represent computer addresses, such as 192.168.220.100, while <indexterm id="ch01-idx-951667-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>compared with TCP/IP</secondary></indexterm>
-<indexterm id="ch01-idx-951667-1"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>name</secondary><see>NetBIOS name</see></indexterm>NetBIOS uses only names. This was a major issue when trying to mesh the two protocols together. In 1987, the Internet Engineering Task Force (IETF) published a series of standardization documents, titled RFC 1001 and 1002, that outlined how NetBIOS would work over a TCP/UDP network. This set of documents still governs each of the implementations that exist today, including those provided by Microsoft with their Windows operating systems as well as the Samba suite.</para>
-
-
-<para>Since then, the standard this document governs has become known as <firstterm>NetBIOS over TCP/IP</firstterm>
-<indexterm id="ch01-idx-951668-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary sortas="TCP/IP">over TCP/IP</secondary></indexterm>
-<indexterm id="ch01-idx-951668-1"><primary>TCP/IP networking protocol</primary><secondary>NetBIOS over</secondary></indexterm>
-<indexterm id="ch01-idx-951668-2"><primary>NBT standard</primary></indexterm>, or NBT for short. The NBT standard (RFC 1001/1002) currently outlines a trio of services on a network:</para>
-
-
-<itemizedlist>
-<listitem><para>A name service</para></listitem>
-<listitem><para>Two communication services:</para>
-
-<itemizedlist>
-<listitem><para>Datagrams</para></listitem>
-<listitem><para>Sessions</para></listitem>
-</itemizedlist></listitem>
-</itemizedlist>
-
-<para>The <indexterm id="ch01-idx-951671-0"><primary>name services</primary></indexterm>name service solves the name-to-address problem mentioned earlier; it allows each computer to declare a specific name on the network that can be translated to a machine-readable IP address, much like today's DNS on the Internet. The <indexterm id="ch01-idx-951672-0"><primary>datagram service</primary></indexterm>
-<indexterm id="ch01-idx-951672-1"><primary>session service</primary></indexterm>datagram and session services are both secondary communication protocols used to transmit data back and forth from NetBIOS machines across the network.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.3.2" id="ch01-SECT-3.2">
-<title>Getting a Name</title>
-
-
-<para>
-<indexterm id="ch01-idx-951674-0" class="startofrange"><primary>naming</primary><secondary>machines on NetBIOS network</secondary></indexterm>
-<indexterm id="ch01-idx-951674-1" class="startofrange"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>network, naming machines on</secondary></indexterm>For a human being, getting a name is easy. However, for a machine on a NetBIOS network, it can be a little more complicated. Let's look at a few of the issues.</para>
-
-
-<para>In the NetBIOS world, when each machine comes online, it wants to claim a name for itself; this is called <firstterm>name registration</firstterm>
-<indexterm id="ch01-idx-951675-0"><primary>name registration</primary></indexterm>. However, no two machines in the same workgroup should be able to claim the same name; this would cause endless confusion for any machine that wanted to communicate with either machine. There are two different approaches to ensuring that this doesn't happen:</para>
-
-
-<itemizedlist>
-<listitem><para>Use a <firstterm>NetBIOS Name Server</firstterm>
-<indexterm id="ch01-idx-951677-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>name server (NBNS)</secondary></indexterm>
-<indexterm id="ch01-idx-951677-1"><primary>NBNS</primary><see>NetBIOS, name server</see></indexterm> (NBNS) to keep track of which hosts have registered a NetBIOS name.</para></listitem>
-<listitem><para>Allow each machine on the network to defend its name in the event that another machine attempts to use it.</para></listitem>
-</itemizedlist>
-
-<para><link linkend="ch01-86658">Figure 1.8</link> illustrates a (failed) name registration, with and without a NetBIOS Name Server.</para>
-
-
-<figure label="1.8" id="ch01-86658">
-<title>NBNS versus non-NBNS name registration</title>
-
-<graphic width="502" depth="391" fileref="figs/sam.0108.gif"></graphic>
-</figure>
-
-<para>In addition, there must be a way to resolve a NetBIOS name to a specific IP address as mentioned earlier; this is known as <firstterm>name resolution</firstterm>
-<indexterm id="ch01-idx-951679-0"><primary>name resolution</primary></indexterm>. There are two different approaches with NBT here as well:</para>
-
-
-<itemizedlist>
-<listitem><para>Have each machine report back its IP address when it "hears" a broadcast request for its NetBIOS name.</para></listitem>
-<listitem><para>Use the NBNS to help resolve NetBIOS names to IP addresses.</para></listitem>
-</itemizedlist>
-
-<para><link linkend="ch01-72484">Figure 1.9</link> illustrates the two types of name resolution.</para>
-
-
-<figure label="1.9" id="ch01-72484">
-<title>NBNS versus non-NBNS name resolution</title>
-
-<graphic width="502" depth="391" fileref="figs/sam.0109.gif"></graphic>
-</figure>
-
-<para>As you might expect, having an NBNS on your network can help out tremendously. To see exactly why, let's look at the non-NBNS method.</para>
-
-
-<para>Here, when a client machine boots, it will broadcast a message declaring that it wishes to register a specified NetBIOS name as its own. If nobody objects to the use of the name after multiple registration attempts, it keeps the name. On the other hand, if another machine on the local <indexterm id="ch01-idx-951896-0"><primary>subnets</primary></indexterm>subnet is currently using the requested name, it will send a message back to the requesting client that the name is already taken. This is known as <firstterm>defending</firstterm>
-<indexterm id="ch01-idx-951687-0"><primary>defending hostnames</primary></indexterm> the hostname. This type of system comes in handy when one client has unexpectedly dropped off the network—another can take its name unchallenged—but it does incur an inordinate amount of traffic on the network for something as simple as name registration.</para>
-
-
-<para>With an NBNS, the same thing occurs, except that the communication is confined to the requesting machine and the NBNS server. No broadcasting occurs when the machine wishes to register the name; the registration message is simply sent directly from the client to NBNS server and the NBNS server replies whether or not the name is already taken. This is known as <firstterm>point-to-point communication</firstterm>
-<indexterm id="ch01-idx-951688-0"><primary>point-to-point communication</primary></indexterm>, and is often beneficial on networks with more than one subnet. This is because routers are often preconfigured to block incoming packets that are broadcast to all machines in the subnet.</para>
-
-
-<para>The same principles apply to name resolution. Without an NBNS, NetBIOS name resolution would also be done with a broadcast mechanism. All request packets would be sent to each computer in the network, with the hope that one machine that might be affected will respond directly back to the machine that asked. At this point, it's clear that using an NBNS server and point-to-point communication for this purpose is far less taxing on the network than flooding the network with broadcasts for every name resolution request.<indexterm id="ch01-idx-951682-0" class="endofrange" startref="ch01-idx-951674-0"/>
-<indexterm id="ch01-idx-951682-1" class="endofrange" startref="ch01-idx-951674-1"/></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.3.3" id="ch01-SECT-3.3">
-<title>Node Types</title>
-
-
-<para>
-<indexterm id="ch01-idx-951690-0"><primary>node types</primary></indexterm>How can you tell what strategy each client on your network will use when performing name registration and resolution? Each machine on an NBT network earns one of the following designations, depending on how it handles name registration and resolution: <indexterm id="ch01-idx-951691-0"><primary>b-node</primary></indexterm>
-<indexterm id="ch01-idx-951691-1"><primary>p-node</primary></indexterm>
-<indexterm id="ch01-idx-951691-2"><primary>m-node</primary></indexterm>
-<indexterm id="ch01-idx-951691-3"><primary>h-node</primary></indexterm>b-node, p-node, m-node, and h-node. The behaviors of each type of node are summarized in <link linkend="ch01-91681">Table 1.1</link>.</para>
-
-
-<table label="1.1" id="ch01-91681">
-<title>NetBIOS Node Types </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Role</para></entry>
-
-<entry colname="col2"><para>Value</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>b-node</para></entry>
-
-<entry colname="col2"><para>Uses<indexterm id="ch01-idx-951692-0"><primary>broadcast registration</primary></indexterm>
-<indexterm id="ch01-idx-951692-1"><primary>broadcast resolution</primary></indexterm> broadcast registration and resolution only.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>p-node</para></entry>
-
-<entry colname="col2"><para>Uses <indexterm id="ch01-idx-951693-0"><primary>point-to-point registration/resolution</primary></indexterm>point-to-point registration and resolution only.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>m-node</para></entry>
-
-<entry colname="col2"><para>Uses broadcast for registration. If successful, it notifies the NBNS server of the result. Uses broadcast for resolution; uses NBNS server if broadcast is unsuccessful.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>h-node (hybrid)</para></entry>
-
-<entry colname="col2"><para>Uses NBNS server for registration and resolution; uses broadcast if the NBNS server is unresponsive or inoperative.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>In the case of Windows clients, you will usually find them listed as <firstterm>h-nodes</firstterm> or <firstterm>hybrid nodes</firstterm>. Incidentally, h-nodes were invented later by Microsoft, as a more fault-tolerant route, and do not appear in RFC 1001/1002.</para>
-
-
-<para>You can find out the node type of any Windows machine by typing the command <literal>ipconfig</literal> <literal>/all</literal> and searching for the line that says <literal>Node Type</literal>.</para>
-
-
-<programlisting><emphasis role="bold">C:\>ipconfig /all</emphasis>
-Windows 98 IP Configuration
-...
- Node Type . . . . . . . . . . : Hybrid
-...</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.3.4" id="ch01-SECT-3.4">
-<title>What's in a Name?</title>
-
-
-<para>The <indexterm id="ch01-idx-951695-0" class="startofrange"><primary>NetBIOS name</primary></indexterm>names NetBIOS uses are quite different from the DNS hostnames you might be familiar with. First, NetBIOS names exist in a <indexterm id="ch01-idx-951696-0"><primary>flat namespaces</primary></indexterm>flat namespace. In other words, there are no qualifiers such as <emphasis>ora.com</emphasis> or <emphasis>samba.org</emphasis> to section off hostnames; there is only a single unique name to represent each computer. Second, NetBIOS names are allowed to be only 15 characters, may not begin with an asterisk (*), and can consist only of standard alphanumeric characters (a-z, A-Z, 0-9) and the following:</para>
-
-
-<programlisting>! @ # $ % ^ & ( ) - ' { } . ~</programlisting>
-
-
-<para>Although you are allowed to use a period (.) in a NetBIOS name, we recommend against it because those names are not guaranteed to work in future versions of NetBIOS over TCP/IP.</para>
-
-
-<para>It's not a coincidence that all valid <indexterm id="ch01-idx-952041-0"><primary>DNS (Domain Name System)</primary><secondary>names</secondary><tertiary>NetBIOS names and</tertiary></indexterm>DNS names are also valid NetBIOS names. In fact, the DNS name for a Samba server is often reused as its NetBIOS name. For example, if you had a machine <literal>phoenix.ora.com </literal>, its NetBIOS name would likely be PHOENIX (followed by 8 blanks).</para>
-
-
-<sect3 role="" label="1.3.4.1" id="ch01-SECT-3.4.1">
-<title>Resource names and types</title>
-
-
-<para>With NetBIOS, a machine not only advertises its presence, but also tells others what types of services it offers. For example, <literal>phoenix</literal> can indicate that it's not just a workstation, but is also a file server and can receive WinPopup messages. This is done by adding a 16th byte to the end of the machine (<indexterm id="ch01-idx-951698-0"><primary>resource names</primary></indexterm>resource) name, called the <indexterm id="ch01-idx-951704-0"><primary>resource types</primary></indexterm><firstterm>resource type</firstterm>, and registering the name more than once. See <link linkend="ch01-74707">Figure 1.10</link>.</para>
-
-
-<figure label="1.10" id="ch01-74707">
-<title>The structure of NetBIOS names</title>
-
-<graphic width="502" depth="153" fileref="figs/sam.0110.gif"></graphic>
-</figure>
-
-<para>The one-byte resource type indicates a unique service the named machine provides. In this book, you will often see the resource type shown in <indexterm id="ch01-idx-951708-0"><primary>angled brackets (<>)</primary></indexterm>angled brackets (<indexterm id="ch01-idx-951709-0"><primary><\> (angled brackets)</primary></indexterm><>) after the NetBIOS name, such as:</para>
-
-
-<programlisting>PHOENIX<00></programlisting>
-
-
-<para>You can see which names are registered for a particular NBT machine using the Windows command-line <indexterm id="ch01-idx-951710-0"><primary>NBTSTAT utility</primary></indexterm>NBTSTAT utility. Because these services are unique (i.e., there cannot be more than one registered), you will see them listed as type UNIQUE in the output. For example, the following partial output describes the <literal>hydra</literal> server:</para>
-
-
-<programlisting><emphasis role="bold">D:\>NBTSTAT -a hydra</emphasis>
-
- NetBIOS Remote Machine Name Table
- Name Type Status
----------------------------------------------
-HYDRA <00> UNIQUE Registered
-HYDRA <03> UNIQUE Registered
-HYDRA <20> UNIQUE Registered
-...</programlisting>
-
-
-<para>This says the server has registered the NetBIOS name <literal>hydra</literal> as a <indexterm id="ch01-idx-951711-0"><primary>machine name, types</primary></indexterm>
-<indexterm id="ch01-idx-951711-1"><primary>naming</primary><secondary>machine name, types</secondary></indexterm>machine (workstation) name, a recipient of WinPopup messages, and a file server. Some possible attributes a name can have are listed in <link linkend="ch01-11471">Table 1.2</link>.</para>
-
-
-<table label="1.2" id="ch01-11471">
-<title>NetBIOS Unique Resource Types </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>
-<indexterm id="ch01-idx-951723-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>Unique Resource Types</secondary></indexterm>Named Resource</para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch01-idx-951735-0"><primary>Hexidecimal byte value</primary><secondary>for NetBIOS unique resource types</secondary></indexterm>Hexidecimal Byte Value</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Standard Workstation Service</para></entry>
-
-<entry colname="col2"><para>00</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Messenger Service (WinPopup)</para></entry>
-
-<entry colname="col2"><para>03</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>RAS Server Service</para></entry>
-
-<entry colname="col2"><para>06</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Domain Master Browser Service (associated with primary domain controller)</para></entry>
-
-<entry colname="col2"><para>1B</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Master Browser name</para></entry>
-
-<entry colname="col2"><para>1D</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>NetDDE Service</para></entry>
-
-<entry colname="col2"><para>1F</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Fileserver (including printer server)</para></entry>
-
-<entry colname="col2"><para>20</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>RAS Client Service</para></entry>
-
-<entry colname="col2"><para>21</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Network Monitor Agent</para></entry>
-
-<entry colname="col2"><para>BE</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Network Monitor Utility</para></entry>
-
-<entry colname="col2"><para>BF</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Note that because <indexterm id="ch01-idx-951737-0"><primary>DNS (Domain Name System)</primary><secondary>names</secondary><tertiary> resource types and</tertiary></indexterm>DNS names don't have resource types, the designers intentionally made hexadecimal value 20 (an ASCII space) default to the type for a file server.</para>
-</sect3>
-
-
-
-<sect3 role="" label="1.3.4.2" id="ch01-SECT-3.4.2">
-<title>Group names and types</title>
-
-
-<para>
-<indexterm id="ch01-idx-951786-0"><primary>groups</primary><secondary>names of</secondary></indexterm>
-<indexterm id="ch01-idx-951786-1"><primary>groups</primary><secondary>types of</secondary></indexterm>SMB also uses the concept of groups, with which machines can register themselves. Earlier, we mentioned that the machines in our example belonged to a <firstterm>workgroup</firstterm>, which is a partition of machines on the same network. For example, a business might very easily have an ACCOUNTING and a SALES workgroup, each with different servers and printers. In the Windows world, a workgroup and an SMB group are the same thing.</para>
-
-
-<para>Continuing our NBTSTAT example, the <literal>hydra</literal> Samba server is also a member of the SIMPLE workgroup (the GROUP attribute hex 00), and will stand for election as a browse master (GROUP attribute 1E). Here is the remainder of the NBTSTAT utility output:</para>
-
-
-<programlisting> NetBIOS Remote Machine Name Table, continued
- Name Type Status
----------------------------------------------
-SIMPLE <00> GROUP Registered
-SIMPLE <1E> GROUP Registered
-.._ _MSBROWSE_ _.<01> GROUP Registered</programlisting>
-
-
-<para>The possible group attributes a machine can have are illustrated in <link linkend="ch01-52395">Table 1.3</link>. More information is available in <indexterm id="ch01-idx-951787-0"><primary>resources for further information</primary><secondary>group attributes</secondary></indexterm><citetitle>Windows NT in a Nutshell</citetitle> by Eric Pearce, also published by O'Reilly.</para>
-
-
-<table label="1.3" id="ch01-52395">
-<title>NetBIOS Group Resource Types </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Named Resource</para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch01-idx-951781-0"><primary>Hexidecimal byte value</primary><secondary>for NetBIOS group resource types</secondary></indexterm>Hexidecimal Byte Value</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Standard Workstation group</para></entry>
-
-<entry colname="col2"><para>00</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Logon Server</para></entry>
-
-<entry colname="col2"><para>1C</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Master Browser name</para></entry>
-
-<entry colname="col2"><para>1D</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Normal Group name (used in browser elections)</para></entry>
-
-<entry colname="col2"><para>1E</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Internet Group name (administrative)</para></entry>
-
-<entry colname="col2"><para>20</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal><01><02>_ _MSBROWSE_ _<02></literal></para></entry>
-
-<entry colname="col2"><para>01</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>The final entry, <literal>_ _ MSBROWSE _ _ </literal>, is used to announce a group to other master browsers. The nonprinting characters in the name show up as dots in a NBTSTAT printout. Don't worry if you don't understand all of the resource or group types. Some of them you will not need with Samba, and others you will pick up as you move through the rest of the chapter. The important thing to remember here is the logistics of the naming mechanism.<indexterm id="ch01-idx-951790-0" class="endofrange" startref="ch01-idx-951695-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.3.5" id="ch01-SECT-3.5">
-<title>Datagrams and Sessions</title>
-
-
-<para><firstterm></firstterm>
-<indexterm id="ch01-idx-951800-0" class="startofrange"><primary>session service</primary></indexterm>
-<indexterm id="ch01-idx-951800-1" class="startofrange"><primary>datagram service</primary></indexterm>At this point, let's digress to introduce another responsibility of NBT: to provide connection services between two NetBIOS machines. There are actually two services offered by NetBIOS over TCP/IP: the <firstterm>session service</firstterm> and the <firstterm>datagram service</firstterm>. Understanding how these two services work is not essential to using Samba, but it does give you an idea of how NBT works and how to troubleshoot Samba when it doesn't work.</para>
-
-
-<para>The datagram service has no stable connection between one machine and another. Packets of data are simply sent or broadcast from one machine to another, without regard for the order that they arrive at the destination, or even if they arrive at all. The use of datagrams is not as network intensive as sessions, although they can bog down a network if used unwisely (remember broadcast name resolution earlier?) Datagrams, therefore, are used for quickly sending simple blocks of data to one or more machines. The datagram service communicates using the simple primitives shown in <link linkend="ch01-29352">Table 1.4</link>.</para>
-
-
-<table label="1.4" id="ch01-29352">
-<title>Datagram Primitives </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Primitive</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Send Datagram</para></entry>
-
-<entry colname="col2"><para>Send datagram packet to machine or groups of machines.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Send Broadcast Datagram</para></entry>
-
-<entry colname="col2"><para>Broadcast datagram to any machine waiting with a Receive Broadcast Datagram.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Receive Datagram</para></entry>
-
-<entry colname="col2"><para>Receive a datagram from a machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Receive Broadcast Datagram</para></entry>
-
-<entry colname="col2"><para>Wait for a broadcast datagram.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>The session service is more complex. Sessions are a communication method that, in theory, offers the ability to detect problematic or inoperable connections between two NetBIOS applications. It helps to think of an NBT session in terms of a telephone call.<footnote label="5" id="ch01-pgfId-946249">
-
-
-<para>As you can see in RFC 1001, the telephone analogy was strongly evident in the creation of the NBT service.</para>
-
-
-</footnote> A full-duplex connection is opened between a caller machine and a called machine, and it must remain open throughout the duration of their conversation. Each side knows who the caller and the called machine is, and can communicate with the simple primitives shown in <link linkend="ch01-75575">Table 1.5</link>.</para>
-
-
-<table label="1.5" id="ch01-75575">
-<title>Session Primitives </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Primitive</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Call</para></entry>
-
-<entry colname="col2"><para>Initiate a session with a machine listening under a specified name.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Listen</para></entry>
-
-<entry colname="col2"><para>Wait for a call from a known caller or any caller.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Hang-up</para></entry>
-
-<entry colname="col2"><para>Exit a call.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Send</para></entry>
-
-<entry colname="col2"><para>Send data to the other machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Receive</para></entry>
-
-<entry colname="col2"><para>Receive data from the other machine.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Session Status</para></entry>
-
-<entry colname="col2"><para>Get information on requested sessions.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Sessions are the backbone of resource sharing on an NBT network. They are typically used for establishing stable connections from client machines to disk or printer shares on a server. The client "calls" the server and starts trading information such as which files it wishes to open, which data it wishes to exchange, etc. These calls can last a long time—hours, even days—and all of this occurs within the context of a single connection. If there is an error, the session software (TCP) will retransmit until the data is received properly, unlike the "punt-and-pray" approach of the datagram service (UDP).</para>
-
-
-<para>In truth, while sessions are supposed to be able to handle problematic communications, they often don't. As you've probably already discovered when using Windows networks, this is a serious detriment to using NBT sessions. If the connection is interrupted for some reason, session information that is open between the two computers can easily become invalidated. If that happens, the only way to regain the session information is for the same two computers to call each other again and start over.</para>
-
-
-<para>If you want more information on each of these services, we recommend you look at RFC 1001. However, there are two important things to remember here:</para>
-
-
-<itemizedlist>
-<listitem><para>Sessions always occur between <emphasis>two</emphasis> NetBIOS machines—no more and no less. If a session service is interrupted, the client is supposed to store sufficient state information for it to re-establish the connection. However, in practice, this is rarely the case.</para></listitem>
-<listitem><para>Datagrams can be broadcast to multiple machines, but they are unreliable. In other words, there is no way for the source to know that the datagrams it sent have indeed arrived at their<firstterm></firstterm>
-<indexterm id="ch01-idx-951807-0" class="endofrange" startref="ch01-idx-951800-0"/>
-<indexterm id="ch01-idx-951807-1" class="endofrange" startref="ch01-idx-951800-1"/> destinations.<indexterm id="ch01-idx-951654-0" class="endofrange" startref="ch01-idx-951651-0"/></para></listitem>
-</itemizedlist>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.4" id="ch01-43359">
-<title>Microsoft Implementations</title>
-
-
-<para>
-<indexterm id="ch01-idx-951821-0" class="startofrange"><primary>implementations, Microsoft</primary></indexterm>
-<indexterm id="ch01-idx-951821-1" class="startofrange"><primary>Microsoft</primary><secondary>implementations</secondary></indexterm>With that amount of background, we can now talk about some of Microsoft's implementations of the preceding concepts in the CIFS/SMB networking world. And, as you might expect, there are some complex extensions to introduce as well.</para>
-
-
-<sect2 role="" label="1.4.1" id="ch01-SECT-4.1">
-<title>Windows Domains</title>
-
-
-<para>
-<indexterm id="ch01-idx-951815-0" class="startofrange"><primary>domains</primary></indexterm>Recall that a workgroup is a collection of SMB computers that all reside on a subnet and subscribe to the same SMB group. A <firstterm>Windows domain</firstterm> goes a step further. It is a workgroup of SMB machines that has one addition: a server acting as a <firstterm>domain controller</firstterm>. You must have a domain controller in order to have a Windows domain.<footnote label="6" id="ch01-pgfId-947021">
-
-
-<para>Windows domains are called <indexterm id="ch01-idx-953044-0"><primary>domains</primary><secondary>Windows</secondary></indexterm>
-<indexterm id="ch01-idx-953044-1"><primary>Windows NT</primary><secondary>domains</secondary></indexterm>"Windows NT domains" by Microsoft because they assume that Windows NT machines will take the role of the domain controller. However, because Samba can perform this function as well, we'll simply call them "Windows domains" to avoid confusion.</para>
-
-
-</footnote> Otherwise, it is only a workgroup. See <link linkend="ch01-96972">Figure 1.11</link>.</para>
-
-
-<figure label="1.11" id="ch01-96972">
-<title>A simple Windows domain</title>
-
-<graphic width="502" depth="209" fileref="figs/sam.0111.gif"></graphic>
-</figure>
-
-<para>
-<indexterm id="ch01-idx-951829-0" class="startofrange"><primary>domain controllers</primary><secondary sortas="Windows 95/98">for Windows 95/98</secondary></indexterm>
-<indexterm id="ch01-idx-951829-1" class="startofrange"><primary>Windows 95/98</primary><secondary>domain controllers for</secondary></indexterm>There are currently two separate protocols used by a domain controller (logon server): one for communicating with Windows 95/98 machines and one for communicating with Windows NT machines. While Samba currently implements the domain controller protocol for Windows 95/98 (which allows it to act as a domain controller for Windows 9<emphasis>x</emphasis> machines), it still does not fully support the protocol for Windows NT computers. However, the Samba team promises that support for the Windows NT domain controller protocol is forthcoming in Samba 2.1.</para>
-
-
-<tip id="ch01-NOTE-0" role="ora">
-<para>Why all the difficulty? The protocol that Windows domain controllers use to communicate with their clients and other domain controllers is proprietary and has not been released by Microsoft. This has forced the Samba development team to reverse-engineer the domain controller protocol to see which codes perform specific tasks.</para>
-
-</tip>
-
-<sect3 role="" label="1.4.1.1" id="ch01-SECT-4.1.1">
-<title>Domain controllers</title>
-
-
-<para>The domain controller is the nerve center of a Windows domain, much like an NIS server is the nerve center of the Unix network information service. Domain controllers have a variety of responsibilities. One responsibility that you need to be concerned with is <firstterm>authentication</firstterm>
-<indexterm id="ch01-idx-951839-0"><primary>authentication</primary></indexterm>. Authentication is the process of granting or denying a user access to a shared resource on another network machine, typically through the use of a password.</para>
-
-
-<para>Each domain controller uses a <firstterm>security account manager</firstterm>
-<indexterm id="ch01-idx-951840-0"><primary>security account manager (SAM)</primary></indexterm>
-<indexterm id="ch01-idx-951840-1"><primary>SAM (security account manager)</primary></indexterm> (SAM) to maintain a list of username-password combinations. The domain controller then forms a central repository of passwords that are tied to usernames (one password per user), which is more efficient than each client machine maintaining hundreds of passwords for every network resource available.</para>
-
-
-<para>On a Windows domain, when a non-authenticated client requests access to a server's shares, the server will turn around and ask the domain controller whether that user is authenticated. If it is, the server will establish a session connection with the access rights it has for that service and user. If not, the connection is denied. Once a user is authenticated by the domain controller, a special authenticated token will be returned to the client so that the user will not need to relogin to other resources on that domain. At this point, the user is considered "logged in" to the domain itself. See <link linkend="ch01-49344">Figure 1.12</link>.</para>
-
-
-<figure label="1.12" id="ch01-49344">
-<title>Using a domain controller for authentication</title>
-
-<graphic width="502" depth="242" fileref="figs/sam.0112.gif"></graphic>
-</figure>
-</sect3>
-
-
-
-<sect3 role="" label="1.4.1.2" id="ch01-SECT-4.1.2">
-<title>Primary and backup domain controllers</title>
-
-
-<para>
-<indexterm id="ch01-idx-951842-0"><primary>domain controllers</primary></indexterm>
-<indexterm id="ch01-idx-951842-1"><primary>backup domain controllers (BDCs)</primary></indexterm>
-<indexterm id="ch01-idx-951842-2"><primary>PDC (primary domain controller)</primary></indexterm>
-<indexterm id="ch01-idx-951842-3"><primary>BDCs (backup domain controllers)</primary></indexterm>
-<indexterm id="ch01-idx-951842-4"><primary>primary domain controller</primary><see>PDC</see></indexterm>Redundancy is a key idea behind a Windows domain. The domain controller that is currently active on a domain is called the <firstterm>primary domain controller</firstterm> (PDC). There can be one or more <firstterm>backup domain controllers</firstterm> (BDCs) in the domain as well, which will take over in the event that the primary domain controller fails or becomes inaccessible. BDCs frequently synchronize their SAM data with the primary domain controller so that, if the need arises, any one of them can perform DC services transparently without impacting its clients. Note that BDCs, however, have only read-only copies of the SAM; they can update their data only by synchronizing with a PDC. A server in a Windows domain can use the SAM of any primary or backup domain controller to authenticate a user who attempts to access its resources and logon to the domain.</para>
-
-
-<para>Note that in many aspects, the behaviors of a <indexterm id="ch01-idx-951844-0"><primary>workgroups</primary><secondary>Windows</secondary><tertiary>behaviors vs. Windows domain</tertiary></indexterm>
-<indexterm id="ch01-idx-951844-1"><primary>domains</primary><secondary>behavior vs. Windows workgroups</secondary></indexterm>Windows workgroup and a Windows domain overlap. This is not accidental since the concept of Windows domains did not evolve until Windows NT 3.5 was introduced, and Windows domains were forced to remain <indexterm id="ch01-idx-951873-0"><primary>backwards compatibility</primary><secondary>Windows domains and</secondary></indexterm>backwards compatible with the workgroups present in Windows for Workgroups 3.1. The key thing to remember here is that a Windows domain is simply a Windows workgroup with one or more domain controllers added.</para>
-
-
-<para>Samba can function as a primary domain controller for Windows 95/98 machines without any problems. However, <indexterm id="ch01-idx-951845-0"><primary>Samba</primary><secondary>version 2.0</secondary></indexterm>
-<indexterm id="ch01-idx-951845-1"><primary>Samba</primary><secondary>version 2.1</secondary></indexterm>Samba 2.0 can act as a primary domain controller only for authentication purposes; it currently cannot assume any other PDC responsibilities. (By the time you read this, Samba 2.1 may be available so you can use Samba as a PDC for NT clients.) Also, because of the closed protocol used by Microsoft to synchronize SAM data, Samba currently cannot serve as a backup domain<indexterm id="ch01-idx-951832-0" class="endofrange" startref="ch01-idx-951829-0"/>
-<indexterm id="ch01-idx-951832-1" class="endofrange" startref="ch01-idx-951829-1"/> controller.<indexterm id="ch01-idx-951820-0" class="endofrange" startref="ch01-idx-951815-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.4.2" id="ch01-SECT-4.2">
-<title>Browsing</title>
-
-
-<para>
-<indexterm id="ch01-idx-951846-0" class="startofrange"><primary>browsing</primary></indexterm>Browsing is a high-level answer to the user question: "What machines are out there on the Windows network?" Note that there is no connection with a World Wide Web browser, apart from the general idea of "discovering what's there." And, like the Web, what's out there can change without warning.</para>
-
-
-<para>Before browsing, users had to know the name of the specific computer they wanted to connect to on the network, and then manually enter a UNC such as the following into an application or file manager to access resources:</para>
-
-
-<programlisting>\\HYDRA\network\</programlisting>
-
-
-<para>With browsing, however, you can examine the contents of a machine using a standard point-and-click GUI—in this case, the<indexterm id="ch01-idx-951848-0"><primary>Network Neighborhood window</primary></indexterm> Network Neighborhood window in a Windows client.</para>
-
-
-<sect3 role="" label="1.4.2.1" id="ch01-SECT-4.2.1">
-<title>Levels of browsing</title>
-
-
-<para>As we hinted at the beginning of the chapter, there are actually two types of browsing that you will encounter in an SMB/CIFS network:</para>
-
-
-<itemizedlist>
-<listitem><para>Browsing a list of machines (with shared resources)</para></listitem>
-<listitem><para>Browsing the shared resources of a specific machine</para></listitem>
-</itemizedlist>
-
-<para>
-<indexterm id="ch01-idx-951851-0"><primary>browsing</primary><secondary>machines, list of</secondary></indexterm>Let's look at the first one. On each Windows workgroup (or domain) subnet, one computer has the responsibility of maintaining a list of the machines that are currently accessible through the network. This computer is called the <firstterm>local master browser</firstterm>
-<indexterm id="ch01-idx-951850-0"><primary>local master browser</primary></indexterm>
-<indexterm id="ch01-idx-951850-1"><primary>browse lists</primary></indexterm>, and the list that it maintains is called the <firstterm>browse list</firstterm>. Machines on a subnet use the browse list in order to cut down on the amount of network traffic generated while browsing. Instead of each computer dynamically polling to determine a list of the currently available machines, the computer can simply query the local master browser to obtain a complete, up-to-date list.</para>
-
-
-<para>
-<indexterm id="ch01-idx-951852-0" class="startofrange"><primary>browsing</primary><secondary>resources of a specific machine</secondary></indexterm>To browse the actual resources on a machine, a user must connect to the specific machine; this information cannot be obtained from the browse list. Browsing the list of resources on a machine can be done by clicking on the machine's icon when it is presented in the Network Neighborhood in Windows 95/98 or NT. As you saw at the opening of the chapter, the machine will respond with a list of shared resources that can be accessed if that user is successfully authenticated.</para>
-
-
-<para>Each of the servers on a Windows workgroup is required to announce its presence to the local master browser after it has registered a NetBIOS name, and (theoretically) announce that it is leaving the workgroup when it is shut down. It is the local master browser's responsibility to record what the servers have announced. Note that the local master browser is not necessarily the same machine as a NetBIOS name server (NBNS), which we discussed earlier.</para>
-
-
-<warning id="ch01-NOTE-1" role="ora">
-<para>The <indexterm id="ch01-idx-952154-0"><primary>Network Neighborhood window</primary></indexterm>Windows Network Neighborhood can behave oddly: until you select a particular machine to browse, the Network Neighborhood window may contain data that is not up-to-date. That means that the Network Neighborhood window can be showing machines that have crashed, or can be missing machines that haven't been noticed yet. Put succinctly, once you've selected a server and connected to it, you can be a lot more confident that the shares and printers really exist on the network.</para>
-
-</warning>
-
-<para>Unlike the roles you've seen earlier, almost any Windows machine (NT Server, NT Workstation, 98, 95, or Windows 3.1 for Workgroups) can act as a local master browser. As with the domain controller, the local master browser can have one or more <firstterm>backup browsers</firstterm>
-<indexterm id="ch01-idx-952161-0"><primary>backup browsers</primary><secondary>local master browser</secondary></indexterm> on the local subnet that will take over in the event that the local master browser fails or becomes inaccessible. To ensure fluid operation, the local backup browsers will frequently synchronize their browse list with the local master browser. Let's update our Windows domain diagram to include both a local master and local backup browser. The result is shown in <link linkend="ch01-77521">Figure 1.13</link>.</para>
-
-
-<figure label="1.13" id="ch01-77521">
-<title>A Windows domain with a local master and local backup browser</title>
-
-<graphic width="502" depth="209" fileref="figs/sam.0113.gif"></graphic>
-</figure>
-
-<para>Here is how to calculate the minimum number of <indexterm id="ch01-idx-951868-0"><primary>backup browsers</primary><secondary>maximum number per workgroup</secondary></indexterm>backup browsers that will be allocated on a workgroup:</para>
-
-
-<itemizedlist>
-<listitem><para>If there are between 1 and 32 Windows NT workstations on the network, or between 1 and 16 Windows 95/98 machines on the network, the local master browser allocates one backup browser in addition to the local master browser.</para></listitem>
-<listitem><para>If the number of Windows NT workstations falls between 33 and 64, or the number of Windows 95/98 workstations falls between 17 and 32, the local master browser allocates two backup browsers.</para></listitem>
-<listitem><para>For each group of 32 NT workstations or 16 Windows 95/98 machines beyond this, the local master browser allocates another backup browser.</para></listitem>
-</itemizedlist>
-
-<para>There is currently no upper limit on the number of <indexterm id="ch01-idx-951869-0"><primary>backup browsers</primary><secondary sortas="local master browser">per local master browser</secondary></indexterm>
-<indexterm id="ch01-idx-951869-1"><primary>master browsers</primary><see>local master browser; DMB; preferred master browser</see></indexterm>backup browsers that can be allocated by the local master browser.<indexterm id="ch01-idx-951855-0" class="endofrange" startref="ch01-idx-951852-0"/></para>
-</sect3>
-
-
-
-<sect3 role="" label="1.4.2.2" id="ch01-SECT-4.2.2">
-<title>Browsing elections</title>
-
-
-<para>Browsing is a critical aspect of any Windows workgroup. However, not everything runs perfectly on any network. For example, let's say that the Windows NT Server on the desk of a small company's CEO is the local master browser—that is, until he switches it off while plugging in his massage chair. At this point the Windows NT Workstation in the spare parts department might agree to take over the job. However, that computer is currently running a large, poorly written program that has brought its processor to its knees. The moral: browsing has to be very tolerant of servers coming and going. Because nearly every Windows machine can serve as a browser, there has to be a way of deciding at any time who will take on the job. This decision-making process is called an <firstterm>election</firstterm>
-<indexterm id="ch01-idx-951870-0"><primary>elections</primary></indexterm>
-<indexterm id="ch01-idx-951870-1"><primary>browsing</primary><secondary>elections</secondary></indexterm>.</para>
-
-
-<para>An election algorithm is built into nearly all Windows operating systems such that they can each agree who is going to be a local master browser and who will be local backup browsers. An election can be forced at any time. For example, let's assume that the CEO has finished his massage and reboots his server. As the server comes online, it will announce its presence and an election will take place to see if the PC in the spare parts department should still be the master browser.</para>
-
-
-<para>When an election is performed, each machine broadcasts via datagrams information about itself. This information includes the following:</para>
-
-
-<itemizedlist>
-<listitem><para>The version of the election protocol used</para></listitem>
-<listitem><para>The operating system on the machine</para></listitem>
-<listitem><para>The amount of time the client has been on the network</para></listitem>
-<listitem><para>The hostname of the client</para></listitem>
-</itemizedlist>
-
-<para>These values determine which operating system has seniority and will fulfill the role of the local master browser. (<link linkend="SAMBA-CH-6">Chapter 6</link>, describes the election process in more detail.) The architecture developed to achieve this is not elegant and has built-in security problems. While a browsing domain can be integrated with domain security, the election algorithm does not take into consideration which computers become browsers. Thus it is possible for any machine running a browser service to register itself as participating in the browsing election, and (after winning) being able to change the browse list. Nevertheless, browsing is a key feature of Windows networking and <indexterm id="ch01-idx-951871-0"><primary>backwards compatibility</primary><secondary>elections and</secondary></indexterm>backwards compatibility requirements will ensure that it is in use for years to come.<indexterm id="ch01-idx-951847-0" class="endofrange" startref="ch01-idx-951846-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.4.3" id="ch01-SECT-4.3">
-<title>Can a Windows Workgroup Span Multiple Subnets?</title>
-
-
-<para>
-<indexterm id="ch01-idx-951886-0"><primary>workgroups</primary><secondary>Windows</secondary><tertiary>spanning multiple subnets</tertiary></indexterm>
-<indexterm id="ch01-idx-951886-1"><primary>subnets</primary><secondary>multiple spanned by Windows workgroups</secondary></indexterm>
-<indexterm id="ch01-idx-951886-2"><primary>Windows workgroups</primary><see>workgroups, Windows</see></indexterm>Yes, but most people who have done it have had their share of headaches. Spanning multiple subnets was not part of the initial design of Windows NT 3.5 or Windows for Workgroups. As a result, a Windows domain that spans two or more subnets is, in reality, the "gluing" together of two or more workgroups that share an identical name. The good news is that you can still use a primary domain controller to control authentication across each of the subnets. The bad news is that things are not as simple with browsing.</para>
-
-
-<para>As mentioned previously, each subnet must have its own local master browser. When a Windows domain spans multiple subnets, a system administrator will have to assign one of the machines as the <firstterm>domain master browser</firstterm>. The domain master browser will keep a browse list for the entire Windows domain. This browse list is created by periodically synchronizing the browse lists of each of the local master browsers with the browse list of the domain master browser. After the synchronization, the local master browser and the domain master browser should contain identical entries. See <link linkend="ch01-52572">Figure 1.14</link> for an illustration.</para>
-
-
-<figure label="1.14" id="ch01-52572">
-<title>A workgroup that spans more than one subnet</title>
-
-<graphic width="502" depth="438" fileref="figs/sam.0114.gif"></graphic>
-</figure>
-
-<para>Sound good? Well, it's not quite nirvana for the following reasons:</para>
-
-
-<itemizedlist>
-<listitem><para>If it exists, a primary domain controller always plays the role of the domain master browser. By Microsoft design, the two always share the NetBIOS <indexterm id="ch01-idx-951898-0"><primary>resource types</primary><secondary sortas="primary domain controller vs. domain master browser">for primary domain controller vs. domain master browser</secondary></indexterm>
-<indexterm id="ch01-idx-951898-1"><primary>DMB (domain master browser)</primary><secondary>resource type</secondary></indexterm>resource type <1B>, and (unfortunately) cannot be separated.</para></listitem>
-<listitem><para>Windows 95/98 machines cannot become <emphasis>or</emphasis> <emphasis>even contact</emphasis> a domain master browser. The Samba group feels that this is a marketing decision from Microsoft that forces customers to have at least one Windows NT workstation (or Samba server) on each <indexterm id="ch01-idx-951900-0"><primary>subnets</primary><secondary>Windows NT workstations and</secondary></indexterm>subnet of a multi-subnet workgroup.</para></listitem>
-</itemizedlist>
-
-<para>Each subnet's local master browser continues to maintain the browse list for its subnet, for which it becomes authoritative. So if a computer wants to see a list of servers within its own subnet, the local master browser of that subnet will be queried. If a computer wants to see a list of servers outside the subnet, it can still go only as far as the local master browser. This works because, at appointed intervals, the authoritative browse list of a subnet's local master browser is synchronized with the domain master browser, which is synchronized with the local master browser of the other subnets in the domain. This is called <firstterm>browse list propagation</firstterm>
-<indexterm id="ch01-idx-951902-0"><primary>browse lists</primary><secondary>propagation</secondary></indexterm>
-<indexterm id="ch01-idx-951902-1"><primary>propagation, browse list</primary></indexterm>.</para>
-
-
-<para>Samba can act as a domain master browser on a Windows domain if required. In addition, it can also act as a local master browser for a Windows subnet, synchronizing its browse list with the domain master browser.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.4.4" id="ch01-SECT-4.4">
-<title>The Windows Internet Name Service (WINS)</title>
-
-
-<para>The <indexterm id="ch01-idx-951904-0"><primary>Windows Internet Name Service (see WINS)</primary></indexterm>
-<indexterm id="ch01-idx-951904-1"><primary>WINS (Windows Internet Name Service)</primary></indexterm>Windows Internet Name Service (WINS) is Microsoft's implementation of a <indexterm id="ch01-idx-951906-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>name server (NBNS)</secondary></indexterm>NetBIOS name server (NBNS). As such, WINS inherits much of NetBIOS's characteristics. First, WINS is <indexterm id="ch01-idx-951907-0"><primary>flat namespaces</primary></indexterm>flat; you can only have machines named <literal>fred</literal> or workgroups like CANADA or USA. In addition, WINS is dynamic: when a client first comes online, it is required to report its hostname, its address, and its workgroup to the local WINS server. This WINS server will retain the information so long as the client periodically refreshes its WINS registration, which indicates that it's still connected to the network. Note that <indexterm id="ch01-idx-951908-0"><primary>WINS (Windows Internet Name Service)</primary><secondary>servers</secondary></indexterm>WINS servers are not domain or workgroup specific; they can appear anywhere and serve anyone.</para>
-
-
-<para>Multiple WINS servers can be set to synchronize with each other after a specified amount of time. This allows entries for machines that come online and offline on the network to propagate from one WINS server to another. While in theory this seems efficient, it can quickly become cumbersome if there are several WINS servers covering a network. Because WINS services can cross multiple subnets (you'll either hardcode the address of a WINS server in each of your clients or obtain it via DHCP), it is often more efficient to have each Windows client, no matter how many Windows domains there are, point themselves to the same WINS server. That way, there will only be one authoritative WINS server with the correct information, instead of several WINS servers continually struggling to synchronize themselves with the most recent changes.</para>
-
-
-<para>The currently active WINS server is known as the <firstterm>primary WINS server</firstterm>
-<indexterm id="ch01-idx-951910-0"><primary>primary WINS server</primary></indexterm>
-<indexterm id="ch01-idx-951910-1"><primary>WINS (Windows Internet Name Service)</primary><secondary>WINS server</secondary><tertiary>primary/secondary</tertiary></indexterm>
-<indexterm id="ch01-idx-951910-2"><primary>secondary WINS server</primary></indexterm>. You can also install a secondary WINS server, which will take over in the event that the primary WINS server fails or becomes inaccessible. Note that there is no <indexterm id="ch01-idx-951912-0"><primary>elections</primary><secondary>WINS servers and</secondary></indexterm>election to determine which machine becomes a primary or backup WINS server—the choice of WINS servers is static and must be predetermined by the <indexterm id="ch01-idx-951913-0"><primary>system administrator, WINS server and</primary></indexterm>system administrator. Both the primary and any backup WINS servers will synchronize their address databases on a periodic basis.</para>
-
-
-<para>In the Windows family of operating systems, only an NT Workstation or an NT server can serve as a <firstterm></firstterm>
-<indexterm id="ch01-idx-951916-0"><primary>WINS (Windows Internet Name Service)</primary><secondary>Windows operating systems and</secondary></indexterm>WINS server. Samba can also function as a primary WINS server, but not a secondary WINS server.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.4.5" id="ch01-12452">
-<title>What Can Samba Do?</title>
-
-
-<para>
-<indexterm id="ch01-idx-951921-0"><primary>Samba</primary><secondary>roles in Windows domains/workgroups</secondary></indexterm>
-<indexterm id="ch01-idx-951921-1"><primary>domains</primary><secondary>roles in assumed by Samba</secondary></indexterm>
-<indexterm id="ch01-idx-951921-2"><primary>workgroups</primary><secondary>roles in assumed by Samba</secondary></indexterm>Whew! Bet you never thought Microsoft networks would be that complex, did you? Now, let's wrap up by showing where Samba can help out. <link linkend="ch01-14021">Table 1.6</link> summarizes which roles Samba can and cannot play in a Windows NT Domain or Windows workgroup. As you can see, because many of the NT domain protocols are proprietary and have not been documented by Microsoft, Samba cannot properly synchronize its data with a Microsoft server and cannot act as a backup in most roles. However, with version 2.0.<emphasis>x</emphasis>, Samba does have limited support for the primary domain controller's authentication protocols and is gaining more functionality every day.</para>
-
-
-<table label="1.6" id="ch01-14021">
-<title>Samba Roles (as of 2.0.4b) </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Role</para></entry>
-
-<entry colname="col2"><para>Can Perform?</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>File Server</para></entry>
-
-<entry colname="col2"><para>Yes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Printer Server</para></entry>
-
-<entry colname="col2"><para>Yes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Primary Domain Controller</para></entry>
-
-<entry colname="col2"><para>Yes (Samba 2.1 or higher recommended)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Backup Domain Controller</para></entry>
-
-<entry colname="col2"><para>No</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 95/98 Authentication</para></entry>
-
-<entry colname="col2"><para>Yes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Local Master Browser</para></entry>
-
-<entry colname="col2"><para>Yes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Local Backup Browser</para></entry>
-
-<entry colname="col2"><para>No</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Domain Master Browser</para></entry>
-
-<entry colname="col2"><para>Yes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Primary WINS Server</para></entry>
-
-<entry colname="col2"><para>Yes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Secondary WINS Server</para></entry>
-
-<entry colname="col2"><para>No<indexterm id="ch01-idx-951824-0" class="endofrange" startref="ch01-idx-951821-0"/>
-<indexterm id="ch01-idx-951824-1" class="endofrange" startref="ch01-idx-951821-1"/></para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.5" id="ch01-32691">
-<title>An Overview of the Samba Distribution</title>
-
-
-<para>As mentioned earlier, Samba actually contains several programs that serve different but related purposes. Let's introduce each of them briefly, and show how they work together. The majority of the programs that come with the Samba distribution center on its two daemons. Let's take a refined look at the responsibilities of each daemon:</para>
-
-
-<variablelist>
-<varlistentry><term><emphasis>smbd</emphasis></term>
-<listitem><para>The <emphasis>smbd</emphasis> daemon is responsible for managing the shared resources between the Samba server machine and its clients. It provides file, print, and browser services to <acronym>SMB</acronym> clients across one or more networks. <emphasis>smdb</emphasis> handles all notifications between the Samba server and the network clients. In addition, it is responsible for user authentication, resource locking, and data sharing through the <acronym>SMB</acronym> protocol.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><emphasis>nmbd</emphasis></term>
-<listitem><para>The <emphasis>nmbd</emphasis> daemon is a simple nameserver that mimics the WINS and NetBIOS name server functionality, as you might expect to encounter with the LAN Manager package. This daemon listens for nameserver requests and provides the appropriate information when called upon. It also provides browse lists for the Network Neighborhood and participates in browsing elections.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>The Samba distribution also comes with a small set of Unix command-line tools:</para>
-
-
-<variablelist>
-<varlistentry><term>smbclient</term>
-<listitem><para>An FTP-like Unix client that can be used to connect to Samba shares</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>smbtar</term>
-<listitem><para>A program for backing up data in shares, similar to the Unix <filename>tar</filename> command</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>nmblookup</term>
-<listitem><para>A program that provides NetBIOS over TCP/IP name lookups</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>smbpasswd</term>
-<listitem><para>A program that allows an administrator to change the encrypted passwords used by Samba</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>smbstatus</term>
-<listitem><para>A program for reporting the current network connections to the shares on a Samba server</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>testparm</term>
-<listitem><para>A simple program to validate the Samba configuration file</para></listitem>
-</varlistentry>
-
-
-<para>Each significant release of Samba goes through a significant exposure test before it's announced. In addition, it is quickly updated afterward if problems or unwanted side-effects are found. The latest stable distribution as of this writing is Samba 2.0.5, the long-awaited production version of Samba 2.0. This book focuses on the functionality supported in Samba 2.0, as opposed to the older 1.9.<emphasis>x</emphasis> versions of Samba, which are now obsolete.</para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.6" id="ch01-SECT-6">
-<title>How Can I Get Samba?</title>
-
-
-<para>
-<indexterm id="ch01-idx-951923-0"><primary>Samba</primary><secondary>distribution</secondary></indexterm>Samba is available in both binary and source format from a set of <indexterm id="ch01-idx-951925-0"><primary>mirror sites for Samba distribution</primary></indexterm>mirror sites across the Internet. The primary home site for Samba is located at <indexterm id="ch01-idx-951924-0"><primary>URLs (uniform resource locators)</primary><secondary>Samba</secondary></indexterm>
-<indexterm id="ch01-idx-951924-1"><primary>URLs (uniform resource locators)</primary><secondary>distribution</secondary></indexterm><systemitem role="url">http://www.samba.org/</systemitem>.</para>
-
-
-<para>However, if you don't want to wait for packets to arrive all the way from Australia, mirror sites for Samba can be found at any of several locations on the Internet. A list of mirrors is given at the primary Samba home page.</para>
-
-
-<!-- CD-ROM REFERENCE COMMENTED OUT FOR SAFARI VERSION OF THIS TITLE.
-
-<para>In addition, a <indexterm id="ch01-idx-951926-0"><primary>CD-ROM with this book</primary><secondary>Samba distribution</secondary></indexterm>CD-ROM distribution is available in the back of this book. We strongly encourage you to start with the CD-ROM if this is your first time using Samba. We've included source and binaries up to <indexterm id="ch01-idx-951927-0"><primary>Samba</primary><secondary>version 2.0.5</secondary></indexterm>Samba 2.0.5 with this book. In addition, several of the <indexterm id="ch01-idx-951928-0"><primary>CD-ROM with this book</primary><secondary>testing tools</secondary></indexterm>
-<indexterm id="ch01-idx-951928-1"><primary>testing</primary><secondary>tools for (CD-ROM with this book)</secondary></indexterm>testing tools that we refer to through the book are conveniently packaged on the CD-ROM.</para>
-
--->
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.7" id="ch01-40528">
-<title>What's New in Samba 2.0?</title>
-
-
-<para>
-<indexterm id="ch01-idx-951929-0"><primary>Samba</primary><secondary> version 2.0</secondary></indexterm>
-<indexterm id="ch01-idx-951929-1"><primary>software distribution</primary><see>Samba, distribution</see></indexterm>Samba 2.0 was an eagerly-awaited package. The big additions to Samba 2.0 are more concrete support for NT Domains and the new Samba Web Administration Tool (SWAT), a browser-based utility for configuring Samba. However, there are dozens of other improvements that were introduced in the summer and fall of 1998.</para>
-
-
-<sect2 role="" label="1.7.1" id="ch01-SECT-7.1">
-<title>NT Domains</title>
-
-
-<para>Samba's support for <indexterm id="ch01-idx-951930-0"><primary>domains</primary><secondary>Windows</secondary><tertiary>support for</tertiary></indexterm>
-<indexterm id="ch01-idx-951930-1"><primary>Windows NT</primary><secondary>domains</secondary></indexterm>NT Domains (starting with version 2.0.<emphasis>x</emphasis>) produced a big improvement: it allows SMB servers to use its authentication mechanisms, which is essential for future NT compatibility, and to support <firstterm>NT domain logons</firstterm>
-<indexterm id="ch01-idx-951931-0"><primary>domains</primary><secondary>Windows</secondary></indexterm>
-<indexterm id="ch01-idx-951931-1"><primary>domain logons</primary></indexterm>
-<indexterm id="ch01-idx-951931-2"><primary>domain logons</primary></indexterm>
-<indexterm id="ch01-idx-951931-3"><primary>logons</primary><see>domain logons</see></indexterm>. Domain logons allow a user to log in to a Windows NT domain and use all the computers in the domain without logging into them individually. Previous to version 2.0.0, Samba supported Windows 95/98 logon services, but not NT domain logons. Although domain logons support is not complete is Samba 2.0, it is partially implemented.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.7.2" id="ch01-SECT-7.2">
-<title>Ease of Administration</title>
-
-
-<para>
-<indexterm id="ch01-idx-951933-0"><primary>SWAT tool</primary></indexterm>SWAT, the <indexterm id="ch01-idx-951934-0"><primary>Samba Web Administration Tool</primary><see>SWAT tool</see></indexterm>Samba Web Administration Tool, makes it easy to set up a server and change its configuration, without giving up the simple text-based configuration file. SWAT provides a graphical interface to the resources that Samba shares with its clients. In addition, SWAT saves considerable experimentation and memory work in setting up or changing configurations across the network. You can even create an initial setup with SWAT and then modify the file later by hand, or vice versa. Samba will not complain.</para>
-
-
-<para>On the <indexterm id="ch01-idx-951935-0"><primary>compiling Samba</primary><secondary>in version 2.0</secondary></indexterm>compilation side, <indexterm id="ch01-idx-951936-0"><primary>GNU autoconf</primary></indexterm>GNU <filename>autoconf</filename> is now used to make the task of initial compilation and setup easier so you can get to SWAT quicker.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.7.3" id="ch01-SECT-7.3">
-<title>Performance</title>
-
-
-<para>There are major performance and scalability increases in Samba: the code has been reorganized and <emphasis>nmbd</emphasis>
-<indexterm id="ch01-idx-951937-0"><primary>nmbd daemon</primary></indexterm> (the Samba name service daemon) heavily rewritten:</para>
-
-
-<itemizedlist>
-<listitem><para>Name/browsing service now supports approximately 35,000 simultaneous clients.</para></listitem>
-<listitem><para>File and print services support 500 concurrent users from a single medium-sized server without noticeable performance degradation.</para></listitem>
-<listitem><para>
-<indexterm id="ch01-idx-951938-0"><primary>performance</primary></indexterm>Linux/Samba on identical hardware now consistently performs better than NT Server. And best of all, Samba is improving.</para></listitem>
-<listitem><para>Improved <indexterm id="ch01-idx-951939-0"><primary>opportunistic locking</primary></indexterm>
-<indexterm id="ch01-idx-951939-1"><primary>locks/locking files</primary><secondary>opportunistic locking</secondary></indexterm>
-<indexterm id="ch01-idx-951939-2"><primary>locks/locking files</primary><secondary>opportunistic locking</secondary><seealso>oplocks</seealso></indexterm>"opportunistic" locking allows client machines to cache entire files locally, greatly improving speed without running the risk of accidentally overwriting the cached files.</para></listitem>
-</itemizedlist>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.7.4" id="ch01-SECT-7.4">
-<title>More Features</title>
-
-
-<para>There are several additional features in Samba 2.0. You can now have multiple Samba <indexterm id="ch01-idx-951942-0"><primary>aliases</primary><secondary>multiple</secondary></indexterm>aliases on the same machine, each pretending to be a different server, a feature similar to <indexterm id="ch01-idx-951943-0"><primary>virtual hosts</primary></indexterm>virtual hosts in modern web servers. This allows a host to serve multiple departments and groups, or provide disk shares with normal username/password security while also providing printers to everyone without any security. Printing has been changed to make it easier for <indexterm id="ch01-idx-951944-0"><primary>Unix</primary><secondary>System V</secondary><tertiary>printing and</tertiary></indexterm>Unix System V owners: Samba can now find the available printers automatically, just as it does with Berkeley-style printing. In addition, Samba now has the capability to use <indexterm id="ch01-idx-951945-0"><primary>multiple code pages</primary></indexterm>
-<indexterm id="ch01-idx-951945-1"><primary>code pages</primary><secondary>multiple</secondary></indexterm>
-<indexterm id="ch01-idx-951945-2"><primary>non-European languages</primary></indexterm>
-<indexterm id="ch01-idx-951945-3"><primary>languages, non-European</primary></indexterm>multiple code pages, so it can be used with non-European languages, and to use the <indexterm id="ch01-idx-951946-0"><primary>SSL (Secure Sockets Layer) protocol</primary></indexterm>Secure Sockets Layer protocol (SSL) to encrypt all the data it sends across the Internet, instead of just passwords.<footnote label="7" id="ch01-pgfId-938280">
-
-
-<para>If you reside in the United States, there are some federal rules and regulations dealing with strong cryptography. We'll talk about his later when we set up Samba and SSL in <link linkend="SAMBA-AP-A">Appendix A</link>.</para>
-
-
-</footnote></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="1.7.5" id="ch01-SECT-7.5">
-<title>Compatibility Improvements</title>
-
-
-<para>At the same time as it's becoming more capable, Samba is also becoming more <indexterm id="ch01-idx-951947-0"><primary>Samba</primary><secondary>compatibility with Windows NT</secondary></indexterm>
-<indexterm id="ch01-idx-951947-1"><primary>compatibility, Samba with Windows NT</primary></indexterm>compatible with Windows NT. Samba has always supported Microsoft-style password encryption. It now provides tools and options for changing over to <indexterm id="ch01-idx-951948-0"><primary>Microsoft</primary><secondary>encryption</secondary></indexterm>
-<indexterm id="ch01-idx-951948-1"><primary>Samba</primary><secondary>Microsoft encryption and</secondary></indexterm>Microsoft encryption, and for keeping the Unix and Microsoft password files synchronized while doing so. Finally, a Samba master browser can be instructed to hunt down and synchronize itself with other SMB servers on different LANs, allowing <indexterm id="ch01-idx-951950-0"><primary>SMB (Server Message Block)</primary><secondary>seamless operation across networks</secondary></indexterm>SMB to work seamlessly across multiple networks. Samba uses a different method of accomplishing this from the Microsoft method, which is undocumented.</para>
-</sect2>
-
-
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="1.8" id="ch01-99818">
-<title>And That's Not All...</title>
-
-
-<para>Samba is a wonderful tool with potential for even the smallest SMB/CIFS network. This chapter presented you with a thorough introduction to what Samba is, and more importantly, how it fits into a Windows network. The next series of chapters will help you set up Samba on both the Unix server side, where its two daemons reside, as well as configure the Windows 95, 98, and NT clients to work with Samba. Before long, the aches and pains of your heterogeneous network may seem like a thing of the past. Welcome to the wonderful world of Samba!</para>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="2" id="SAMBA-CH-2">
-<title>Installing Samba on a Unix System</title>
-
-
-
-
-<para>
-<indexterm id="ch02-idx-947293-0" class="startofrange"><primary>installing Samba</primary></indexterm>
-<indexterm id="ch02-idx-947293-1"><primary>Samba</primary><secondary>installing</secondary><see>installing Samba</see></indexterm>Now that you know what Samba can do for you and your users, it's time to get your own network set up. Let's start with the installation of Samba itself on a Unix system. When dancing the samba, one learns by taking small steps. It's just the same when installing Samba; we need to teach it step by step. This chapter will help you to start off on the right foot.</para>
-
-
-<para>For illustrative purposes, we will be installing the 2.0.4 version of the Samba server on a <indexterm id="ch02-idx-947307-0"><primary>Linux</primary><secondary>installing Samba on Linux system</secondary></indexterm>Linux<footnote label="1" id="ch02-pgfId-939741">
-
-
-<para>If you haven't heard of Linux yet, then you're in for a treat. Linux is a freely distributed Unix-like operating system that runs on the Intel x86, Motorola PowerPC, and Sun Sparc platforms. The operating system is relatively easy to configure, extremely robust, and is gaining in popularity. You can get more information on the Linux operating system at <systemitem role="url">http://www.linux.org/</systemitem>.</para>
-
-
-</footnote> system running version 2.0.31 of the kernel. However, the installation steps are the same for all of the platforms that Samba supports. A typical installation will take about an <indexterm id="ch02-idx-947305-0"><primary>installing Samba</primary><secondary>time required</secondary></indexterm>hour to complete, including downloading the source files and compiling them, setting up the configuration files, and testing the server.</para>
-
-
-<para>
-<indexterm id="ch02-idx-947306-0"><primary>installing Samba</primary><secondary>steps in</secondary></indexterm>Here is an overview of the steps:</para>
-
-
-<orderedlist>
-<listitem><para>Download the source or binary files.</para></listitem>
-<listitem><para>Read the installation documentation.</para></listitem>
-<listitem><para>Configure a makefile.</para></listitem>
-<listitem><para>Compile the server code.</para></listitem>
-<listitem><para>Install the server files.</para></listitem>
-<listitem><para>Create a Samba configuration file.</para></listitem>
-<listitem><para>Test the configuration file.</para></listitem>
-<listitem><para>Start the Samba daemons.</para></listitem>
-<listitem><para>Test the Samba daemons.</para></listitem>
-</orderedlist>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="2.1" id="ch02-85028">
-<title>Downloading the Samba Distribution</title>
-
-
-<para>
-<indexterm id="ch02-idx-947308-0" class="startofrange"><primary>Samba</primary><secondary>downloading</secondary></indexterm>
-<indexterm id="ch02-idx-947308-1" class="startofrange"><primary>Samba</primary><secondary>distribution</secondary></indexterm>
-
-<!-- CD-ROM REFERENCE COMMENTED OUT FOR SAFARI VERSION OF THIS TITLE.
-
-If
-you want to get started quickly, the <indexterm
-id="ch02-idx-947316-0" id="IXT-2-126769"><primary>CD-ROM with this
-book</primary><secondary>Samba
-distribution</secondary></indexterm>CD-ROM packaged with this book
-contains both the sources and binaries of Samba that were available as
-this book went to print. The CD is a mirror image of the files and
-directories on the Samba download server: <systemitem
-role="url">ftp.samba.org</systemitem> <indexterm
-id="ch02-idx-947317-0" id="IXT-2-126770"><primary>FTP (File Transfer
-Protocol)</primary><secondary>sites for Samba
-downloads</secondary></indexterm> <indexterm
-id="ch02-idx-947317-1" id="IXT-2-126771"><primary>downloads</primary><secondary>Samba</secondary></indexterm>.</para>
-
-<para>On the other hand, if
-
---></para>
-
-
-<para>If you want to download the latest version, the primary web site
-for the Samba software is <indexterm id="ch02-idx-947318-0"><primary>URLs (uniform resource
-locators)</primary><secondary>Samba</secondary></indexterm><systemitem role="url">http://www.samba.org</systemitem>. Once connected to this
-page, you'll see links to several Samba mirror sites across the
-world, both for the standard Samba web pages and sites devoted
-exclusively to downloading Samba. For the best performance, choose a
-site that is closest to your own geographic location.</para>
-
-
-<para>The standard <indexterm id="ch02-idx-947320-0"><primary>Samba</primary><secondary>web
-site</secondary></indexterm> <indexterm id="ch02-idx-947320-1"><primary>resources for further
-information</primary><secondary>Samba</secondary></indexterm>Samba web
-sites have Samba documentation and tutorials, mailing list archives,
-and the latest Samba news, as well as source and binary distributions
-of Samba. The download sites (sometimes called <emphasis>FTP
-sites</emphasis>) have only the source and binary
-distributions. Unless you specifically want an older version of the
-Samba server or are going to install a binary distribution, download
-the latest source distribution from the closest mirror site. This
-distribution is always named:</para>
-
-
-<programlisting>samba-latest.tar.gz</programlisting>
-
-
-<!-- CD-ROM REFERENCE COMMENTED OUT FOR SAFARI VERSION OF THIS TITLE.
-
-<para>If you choose to use the version of Samba that is located on the
-CD-ROM packaged with this book, you should find the latest Samba
-distribution in the base directory.</para>
-
--->
-
-<sect2 role="" label="2.1.1" id="ch02-SECT-1.1">
-<title>Binary or Source?</title>
-
-
-<para>
-<indexterm id="ch02-idx-947323-0"><primary>binary vs. source files</primary></indexterm>
-<indexterm id="ch02-idx-947323-1"><primary>source vs. binary files</primary></indexterm>Precompiled packages are also available for a large number of Unix platforms. These packages contain binaries for each of the Samba executables as well as the standard Samba documentation. Note that while installing a binary distribution can save you a fair amount of trouble and time, there are a couple of issues that you should keep in mind when deciding whether to use the binary or compile the source yourself:</para>
-
-
-<itemizedlist>
-<listitem><para>The binary packages can lag behind the latest version
-of the software by one or two (maybe more) minor releases, especially
-after a series of small changes and for less popular
-platforms. Compare the release notes for the source and binary
-packages to make sure that there aren't any new features that
-you need on your platform.
-
-<!-- CD-ROM REFERENCE COMMENTED OUT FOR SAFARI VERSION OF THIS TITLE.
-
-This is especially true of the sources and
-binaries on the CD-ROM: at the time this book went to print, they were
-from the latest production release of Samba. However, development is
-ongoing, so the beta-test versions on the Internet will be
-newer.
-
---></para></listitem>
-<listitem><para>If you use a precompiled binary, you will need to ensure that you have the correct libraries required by the executables. On some platforms the executables are statically linked so this isn't an issue, but on modern Unix operating systems (e.g., Linux, SGI Irix, Solaris, HP-UX, etc.), libraries are often <indexterm id="ch02-idx-947325-0"><primary>dynamically linked libraries</primary></indexterm>dynamically linked. This means that the binary looks for the right version of each library on your system, so you may have to install a new version of a library. The <filename>README</filename> file or <filename>makefile</filename>
-<indexterm id="ch02-idx-947333-0"><primary>makefiles</primary></indexterm> that accompanies the binary distribution should list any special requirements.<footnote label="2" id="ch02-pgfId-943622">
-
-
-<para>This is especially true with programs that use <emphasis>glibc-2.1</emphasis> (which comes standard with Red Hat Linux 6). This library caused quite a consternation in the development community when it was released because it was incompatible with previous versions of <emphasis>g</emphasis><filename>libc</filename>.</para>
-
-
-</footnote></para>
-
-
-<para>Many machines with shared libraries come with a nifty tool called <emphasis>ldd</emphasis>
-<indexterm id="ch02-idx-947322-0"><primary>ldd tool</primary></indexterm>. This tool will tell you which libraries a specific binary requires and which libraries on the system satisfy that requirement. For example, checking the <emphasis>smbd</emphasis> program on our test machine gave us:</para></listitem>
-</itemizedlist>
-
-<programlisting>$ <emphasis role="bold">ldd smbd</emphasis>
-libreadline.so.3 => /usr/lib/libreadline.so.3
-libdl.so.2 => /lib/libdl.so.2
-libcrypt.so.1 => /lib/libcrypt.so.1
-libc.so.6 => /lib/libc.so.6
-libtermcap.so.2 => /lib/libtermcap.so.2
-/lib/ld-linux.so.2 => /lib/ld-linux.so.2</programlisting>
-
-
-<itemizedlist>
-<listitem><para>If there are any incompatibilities between Samba and specific libraries on your machine, the distribution-specific documentation should highlight those.</para></listitem>
-<listitem><para>Keep in mind that each binary distribution carries preset values about the target platform, such as default directories and configuration option values. Again, check the documentation and the makefile included in the source directory to see which directives and variables were used when the binary was compiled. In some cases, these will not be appropriate for your situation.</para>
-
-
-<para>A few configuration items can be reset with command-line options at runtime instead of at compile time. For example, if your binary tries to place any log, lock, or status files in the "wrong" place (for example, in <filename>/usr/local</filename> ), you can override this without recompiling.</para></listitem>
-</itemizedlist>
-
-<para>One point worth mentioning is that the Samba source requires an <indexterm id="ch02-idx-947324-0"><primary>ANSI C compilers</primary></indexterm>
-<indexterm id="ch02-idx-947324-1"><primary>non-ANSI compilers</primary></indexterm>
-<indexterm id="ch02-idx-947324-2"><primary>compilers</primary></indexterm>ANSI C compiler. If you are on a platform with a non-ANSI compiler, such as the <emphasis>cc</emphasis> compiler on SunOS version 4, you'll have to install an ANSI-compliant compiler such as <emphasis>gcc</emphasis> before you do anything else.<footnote label="3" id="ch02-pgfId-939049">
-
-
-<para><emphasis>gcc</emphasis> binaries are available for almost every modern machine. See <systemitem role="url">http://www.gnu.org/</systemitem> for a list of sites with <emphasis>gcc</emphasis> and other GNU software.</para>
-
-
-</footnote> If installing a compiler isn't something you want to wrestle with, you can start off with a binary package. However, for the most flexibility and compatibility on your system, we always recommend compiling from the latest source.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="2.1.2" id="ch02-SECT-1.2">
-<title>Read the Documentation</title>
-
-
-<para>
-<indexterm id="ch02-idx-947327-0"><primary>documentation for Samba</primary><secondary>importance of reading</secondary></indexterm>
-<indexterm id="ch02-idx-947327-1"><primary>reading documentation, importance of</primary></indexterm>
-<indexterm id="ch02-idx-947327-2"><primary>Samba</primary><secondary>documentation, importance of reading</secondary></indexterm>This sounds like an obvious thing to say, but there have probably been times where you have uncompressed a package, blindly typed <literal>configure</literal>, <literal>make</literal>, and <literal>make</literal> <literal>install</literal>, and walked away to get another cup of coffee. We'll be the first to admit that we do that, many more times than we should. It's a bad idea—especially when planning a network with Samba.</para>
-
-
-<para>Samba 2.0 automatically configures itself prior to compilation. This reduces the likelihood of a machine-specific problem, but there may be an option mentioned in the <filename>README</filename> file that you end up wishing for after Samba's been installed. With both source and binary packages you'll find a large number of documents in the <filename>docs</filename>
-<indexterm id="ch02-idx-947328-0"><primary>docs directory</primary></indexterm> directory, in a variety of formats. The most important files to look at in the distribution are:</para>
-
-
-<programlisting><indexterm id="ch02-idx-947329-0"><primary>Samba</primary><secondary>new features file</secondary></indexterm>
-<indexterm id="ch02-idx-947329-1"><primary>installing Samba</primary><secondary>common problems</secondary></indexterm>WHATSNEW.txt
-docs/textdocs/UNIX_INSTALL.txt</programlisting>
-
-
-<para>These files tell you what features you can expect in your Samba distribution, and will highlight common installation problems that you're likely to face. Be sure to look over both of them before you start the compilation process.<indexterm id="ch02-idx-947311-0" class="endofrange" startref="ch02-idx-947308-0"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="2.2" id="ch02-28558">
-<title>Configuring Samba</title>
-
-
-<para>
-<indexterm id="ch02-idx-947339-0" class="startofrange"><primary>configuring Samba</primary></indexterm>
-<indexterm id="ch02-idx-947339-1"><primary>configuring Samba</primary><secondary>configuration file</secondary><seealso>smb.conf (Samba configuration) file</seealso></indexterm>The <indexterm id="ch02-idx-947330-0"><primary>Samba</primary><secondary>configuring</secondary><see>configuring Samba</see></indexterm>source distribution of Samba 2.0 and above doesn't initially have a <indexterm id="ch02-idx-947337-0"><primary>makefiles</primary></indexterm>makefile. Instead, one is generated through a GNU <filename>configure</filename>
-<indexterm id="ch02-idx-947338-0"><primary>configuring Samba</primary><secondary>configure script</secondary><tertiary>GNU</tertiary></indexterm>
-<indexterm id="ch02-idx-947338-1"><primary>GNU configure script</primary></indexterm> script, which is located in the <filename>samba-2.0.x /source/</filename> directory. The <firstterm>configure</firstterm> script, which must be run as root, takes care of the machine-specific issues of building Samba. However, you still may want to decide on some global options. Global options can be set by passing options on the command-line:</para>
-
-
-<programlisting># ./configure --with-ssl</programlisting>
-
-
-<para>For example, this will configure the Samba makefile with support for the<indexterm id="ch02-idx-947347-0"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>support for</secondary></indexterm>
-<indexterm id="ch02-idx-947347-1"><primary>Secure Sockets Layer protocol</primary><see>SSL</see></indexterm> Secure Sockets Layer (SSL) encryption protocol. If you would like a complete list of <indexterm id="ch02-idx-947348-0" class="startofrange"><primary>configuring Samba</primary><secondary>options</secondary></indexterm>options, type the following:</para>
-
-
-<programlisting>#./configure --help</programlisting>
-
-
-<para>
-<indexterm id="ch02-idx-947349-0"><primary>enabling/disabling features</primary></indexterm>
-<indexterm id="ch02-idx-947349-1"><primary>disabling/enabling features</primary></indexterm>Each of these options enable or disable various features. You typically enable a feature by specifying the <literal>--with-</literal><replaceable>feature</replaceable> option, which will cause the feature to be compiled and installed. Likewise, if you specify a <literal>--without-</literal><replaceable>feature</replaceable> option, the feature will be disabled. As of Samba 2.0.5, each of the following features is disabled by default:</para>
-
-
-<varlistentry><term><literal>--with-afs</literal></term>
-<listitem><para>Include support of the <indexterm id="ch02-idx-947353-0"><primary>Andrew Filesystem</primary><see>AFS files</see></indexterm>Andrew Filesystem from <indexterm id="ch02-idx-947354-0"><primary>Carnegie Mellon University</primary></indexterm>Carnegie Mellon University. If you're going to serve <indexterm id="ch02-idx-947355-0"><primary>AFS files, support for</primary></indexterm>AFS files via Samba, we recommend compiling Samba once first without enabling this feature to ensure that everything runs smoothly. Once that version is working smoothly, recompile Samba with this feature enabled and compare any errors you might receive against the previous setup.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-dfs</literal></term>
-<listitem><para>Include support for <indexterm id="ch02-idx-947356-0"><primary>DFS, support for</primary></indexterm>DFS, a later version of AFS, used by <indexterm id="ch02-idx-947357-0"><primary>OSF/1 (Digital Unix)</primary></indexterm>OSF/1 (Digital Unix). Note that this is <emphasis>not</emphasis> the same as Microsoft DFS, which is an entirely different filesystem. Again, we recommend compiling Samba once first without this feature to ensure that everything runs smoothly, then recompile with this feature to compare any errors against the previous setup.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-krb4</literal>=<replaceable>base-directory</replaceable></term>
-<listitem><para>Include support for <indexterm id="ch02-idx-947358-0"><primary>Kerberos, support for</primary></indexterm>Kerberos version 4.0, explicitly specifying the base directory of the distribution. Kerberos is a network security protocol from <indexterm id="ch02-idx-947359-0"><primary>MIT</primary></indexterm>MIT that uses <indexterm id="ch02-idx-947360-0"><primary>private key cryptography</primary></indexterm>
-<indexterm id="ch02-idx-947360-1"><primary>cryptography, private key</primary></indexterm>private key cryptography to provide strong security between nodes. Incidentally, Microsoft has announced that Kerberos 5.0 will be the standard <indexterm id="ch02-idx-947362-0"><primary>authentication</primary><secondary>mechanisms for</secondary></indexterm>authentication mechanism for Microsoft Windows 2000 (NT 5.0). However, the Kerberos 5.0 authentication mechanisms are quite different from the Kerberos 4.0 <indexterm id="ch02-idx-947363-0"><primary>security</primary></indexterm>security mechanisms. If you have Kerberos version 4 on your system, the Samba team recommends that you upgrade and use the <literal>--with-krb5</literal> option (see the next item). You can find more information on <indexterm id="ch02-idx-947364-0"><primary>URLs (uniform resource locators)</primary><secondary>Kerberos</secondary></indexterm>Kerberos at <systemitem role="url">http://web.mit.edu/kerberos/www</systemitem>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-krb5</literal>=<replaceable>base-directory</replaceable></term>
-<listitem><para>Include support for Kerberos version 5.0, explicitly specifying the base directory of the distribution. Microsoft has announced that Kerberos 5.0 will be the standard authentication mechanism for Microsoft Windows 2000 (NT 5.0). However, there is no guarantee that Microsoft will not extend Kerberos for their own needs in the future. Currently, Samba's Kerberos support only uses a plaintext password interface and not an encrypted one. You can find more information on Kerberos at its home page: <systemitem role="url">http://web.mit.edu/kerberos/www</systemitem>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-automount</literal></term>
-<listitem><para>Include support for <indexterm id="ch02-idx-947365-0"><primary>automounter, support for</primary></indexterm>automounter, a feature often used on sites that offer NFS.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-pam</literal></term>
-<listitem><para>Include support for <indexterm id="ch02-idx-947368-0"><primary>pluggable authentication modules (PAM)</primary><secondary>support for</secondary></indexterm>
-<indexterm id="ch02-idx-947368-1"><primary>PAM (pluggable authentication modules)</primary><secondary>support for</secondary></indexterm>pluggable authentication modules (PAM), an authentication feature common in the Linux operating system.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-ldap</literal></term>
-<listitem><para>Include support for the <indexterm id="ch02-idx-947369-0"><primary>Lightweight Directory Access Protocol</primary><see>LDAP</see></indexterm>
-<indexterm id="ch02-idx-947369-1"><primary>LDAP (Lightweight Directory Access Protocol)</primary><secondary>support for</secondary></indexterm>Lightweight Directory Access Protocol (LDAP). A future version of LDAP will be used in the Windows 2000 (NT 5.0) operating system; this Samba support is experimental. LDAP is a flexible client-server directory protocol that can carry information such as certificates and group memberships.<footnote label="4" id="ch02-pgfId-943655">
-
-
-<para>By <emphasis>directory</emphasis>, we don't mean a directory in a file system, but instead an indexed directory (such as a phone directory). Information is stored and can be easily retrieved in a public LDAP system.</para>
-
-
-</footnote></para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-nis</literal></term>
-<listitem><para>Include support for getting password-file information from <indexterm id="ch02-idx-947370-0"><primary>NIS/NIS+ protocol</primary></indexterm>NIS (network yellow pages).</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-nisplus</literal></term>
-<listitem><para>Include support for obtaining password-file information from NIS+, the successor to NIS.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-ssl</literal></term>
-<listitem><para>Include experimental support for the <indexterm id="ch02-idx-947374-0"><primary>SSL (Secure Sockets Layer) protocol</primary><secondary>support for</secondary></indexterm>Secure Sockets Layer (SSL), which is used to provide encrypted connections from client to server. <link linkend="SAMBA-AP-A">Appendix A</link>, describes setting up Samba with SSL support.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-nisplus-home</literal></term>
-<listitem><para>Include support for locating which server contains a particular user's <indexterm id="ch02-idx-947380-0"><primary>home directory, user's</primary></indexterm>
-<indexterm id="ch02-idx-947380-1"><primary>users</primary><secondary>home directory</secondary></indexterm>home directory and telling the client to connect to it. Requires <literal>--with-nis</literal> and, usually, <literal>--with-automounter</literal>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-mmap</literal></term>
-<listitem><para>Include experimental<indexterm id="ch02-idx-947381-0"><primary>mmap code</primary></indexterm> memory mapping code. This is not required for <indexterm id="ch02-idx-947382-0"><primary>fast locking</primary></indexterm>fast locking, which already uses mmap or System V shared memory.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-syslog</literal></term>
-<listitem><para>Include support for using the <indexterm id="ch02-idx-947383-0"><primary>SYSLOG utility</primary><secondary>support for</secondary></indexterm>SYSLOG utility for logging information generated from the Samba server. There are a couple of Samba configuration options that you can use to enable SYSLOG support; <link linkend="ch04-21486">Chapter 4</link>, discusses these options.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-netatalk</literal></term>
-<listitem><para>Include experimental support for interoperating with the (Macintosh) <indexterm id="ch02-idx-947412-0"><primary>Netatalk (Macintosh), support for interoperating with</primary></indexterm>Netatalk file server.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><literal>--with-quotas</literal></term>
-<listitem><para>Include <indexterm id="ch02-idx-947413-0"><primary>disk quotas, support for</primary></indexterm>disk-quota support.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>Because each of these options is disabled by default, none of these features are essential to Samba. However, you may want to come back and build a modified version of Samba if you discover that you need one at a later time.</para>
-
-
-<para>In addition, <link linkend="ch02-85125">Table 2.1</link> shows some other parameters that you can give the <filename>configure</filename> script if you wish to store parts of the Samba distribution in different places, perhaps to make use of multiple disks or partitions. Note that the defaults sometimes refer to a prefix specified earlier in the table.</para>
-
-
-<table label="2.1" id="ch02-85125">
-<title>Additional Configure Options </title>
-
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Meaning</para></entry>
-
-<entry colname="col3"><para>Default</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>--prefix</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install architecture-independent files at the base directory specified.</para></entry>
-
-<entry colname="col3"><para><filename>/usr/local/samba</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--eprefix</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install architecture-dependent files at the base directory specified.</para></entry>
-
-<entry colname="col3"><para><filename>/usr/local/samba</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--bindir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install user executables in the directory specified.</para></entry>
-
-<entry colname="col3"><para><replaceable>eprefix</replaceable><filename>/bin</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--sbindir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install administrator executables in the directory specified.</para></entry>
-
-<entry colname="col3"><para><replaceable>eprefix</replaceable><filename>/bin</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--libexecdir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install program executables in the directory specified.</para></entry>
-
-<entry colname="col3"><para><replaceable>eprefix</replaceable><filename>/libexec</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--datadir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install read-only architecture independent data in the directory specified.</para></entry>
-
-<entry colname="col3"><para><replaceable>prefix</replaceable><filename>/share</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--libdir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install program libraries in the directory specified.</para></entry>
-
-<entry colname="col3"><para><replaceable>eprefix</replaceable><filename>/lib</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--includedir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install package include files in the directory specified.</para></entry>
-
-<entry colname="col3"><para><replaceable>prefix</replaceable><filename>/include</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--infodir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install additional information files in the directory specified.</para></entry>
-
-<entry colname="col3"><para><replaceable>prefix</replaceable><filename>/info</filename></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>--mandir</literal>=<replaceable>directory</replaceable></para></entry>
-
-<entry colname="col2"><para>Install manual pages in the directory specified.<indexterm id="ch02-idx-947428-0" class="endofrange" startref="ch02-idx-947348-0"/></para></entry>
-
-<entry colname="col3"><para><replaceable>prefix</replaceable><filename>/man</filename></para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Again, before running the <filename>configure</filename> script, it is important that you are the <indexterm id="ch02-idx-947433-0"><primary>root user</primary></indexterm>root user on the system. Otherwise, you may get a warning such as:</para>
-
-
-<programlisting>configure: warning: running as non-root will disable some tests</programlisting>
-
-
-<para>You don't want any test to be disabled when the Samba makefile is being created; this leaves the potential for errors down the road when compiling or running Samba on your system.</para>
-
-
-<para>Here is a sample execution of the <filename>configure</filename>
-<indexterm id="ch02-idx-947434-0"><primary>configuring Samba</primary><secondary>configure script</secondary><tertiary>sample execution</tertiary></indexterm> script, which creates a Samba 2.0.4 makefile for the Linux platform. Note that you must run the configure script in the <emphasis>source</emphasis> directory, and that several lines from the middle of the excerpt have been omitted:</para>
-
-
-<programlisting># cd samba-2.0.4b/source/
-# ./configure | tee mylog
-
-loading cache ./config.cache
-checking for gcc... (cached) gcc
-checking whether the C compiler (gcc -O ) works... yes
-checking whether the C compiler (gcc -O ) is a cross-compiler... no
-checking whether we are using GNU C... (cached) yes
-checking whether gcc accepts -g... (cached) yes
-checking for a BSD compatible install... (cached) /usr/bin/install -c
-
-<emphasis>...(content omitted)...</emphasis>
-
-checking configure summary
-configure OK
-creating ./config.status
-creating include/stamp-h
-creating Makefile
-creating include/config.h</programlisting>
-
-
-<para>In general, any message from <filename>configure</filename> that doesn't begin with the words <literal>checking</literal> or <literal>creating</literal> is an error; it often helps to redirect the output of the configure script to a file so you can quickly search for <indexterm id="ch02-idx-947435-0"><primary>errors</primary><secondary>searching for</secondary></indexterm>errors, as we did with the <literal>tee</literal> command above. If there was an error during configuration, more detailed information about it can be found in the <filename>config.log</filename> file, which is written to the local directory by the <filename>configure</filename> script.</para>
-
-
-<para>If the configuration works, you'll see a <literal>checking</literal> <literal>configure</literal> <literal>summary</literal> message followed by a <literal>configure</literal> <literal>OK</literal> message and four or five file creation messages. So far, so good.... Next step: compiling.<indexterm id="ch02-idx-947719-0" class="endofrange" startref="ch02-idx-947339-0"/></para>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="2.3" id="ch02-13217">
-<title>Compiling and Installing Samba</title>
-
-
-<para>
-<indexterm id="ch02-idx-947438-0" class="startofrange"><primary>compiling Samba</primary></indexterm>At <indexterm id="ch02-idx-947440-0"><primary>Samba</primary><secondary>compiling</secondary><see>compiling Samba</see></indexterm>this point you should be ready to build the Samba executables. Compiling is also easy: in the <filename>source</filename> directory, type <literal>make</literal> on the command line. The <filename>make</filename>
-<indexterm id="ch02-idx-947436-0"><primary>make utility</primary></indexterm> utility will produce a stream of explanatory and success messages, beginning with:</para>
-
-
-<programlisting>Using FLAGS = -O -Iinclude ...</programlisting>
-
-
-<para>This build includes compiles for both <emphasis>smbd</emphasis> and <emphasis>nmbd</emphasis>, and ends in a linking command for <filename>bin/make_ printerdef</filename>. For example, here is a sample make of Samba version 2.0.4 on a Linux server:</para>
-
-
-<programlisting># make
-Using FLAGS = -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -DSMBLOGFILE="/
-usr/local/samba/var/log.smb" -DNMBLOGFILE="/usr/local/samba/var/log.nmb" -
-DCONFIGFILE="/usr/local/samba/lib/smb.conf" -DLMHOSTSFILE="/usr/local/samba/lib/
-lmhosts" -DSWATDIR="/usr/local/samba/swat" -DSBINDIR="/usr/local/samba/bin" -
-DLOCKDIR="/usr/local/samba/var/locks" -DSMBRUN="/usr/local/samba/bin/smbrun" -
-DCODEPAGEDIR="/usr/local/samba/lib/codepages" -DDRIVERFILE="/usr/local/samba/lib/
-printers.def" -DBINDIR="/usr/local/samba/bin" -DHAVE_INCLUDES_H -DPASSWD_
-PROGRAM="/bin/passwd" -DSMB_PASSWD_FILE="/usr/local/samba/private/smbpasswd"
-Using FLAGS32 = -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -
-DSMBLOGFILE="/usr/local/samba/var/log.smb" -DNMBLOGFILE="/usr/local/samba/var/log.
-nmb" -DCONFIGFILE="/usr/local/samba/lib/smb.conf" -DLMHOSTSFILE="/usr/local/samba/
-lib/lmhosts" -DSWATDIR="/usr/local/samba/swat" -DSBINDIR="/usr/local/samba/bin"
--DLOCKDIR="/usr/local/samba/var/locks" -DSMBRUN="/usr/local/samba/bin/smbrun" -
-DCODEPAGEDIR="/usr/local/samba/lib/codepages" -DDRIVERFILE="/usr/local/samba/lib/
-printers.def" -DBINDIR="/usr/local/samba/bin" -DHAVE_INCLUDES_H -DPASSWD_
-PROGRAM="/bin/passwd" -DSMB_PASSWD_FILE="/usr/local/samba/private/smbpasswd"
-Using LIBS = -lreadline -ldl -lcrypt -lpam
-Compiling smbd/server.c
-Compiling smbd/files.c
-Compiling smbd/chgpasswd.c
-
-<emphasis>...(content omitted)...</emphasis>
-
-Compiling rpcclient/cmd_samr.c
-Compiling rpcclient/cmd_reg.c
-Compiling rpcclient/cmd_srvsvc.c
-Compiling rpcclient/cmd_netlogon.c
-Linking bin/rpcclient
-Compiling utils/smbpasswd.c
-Linking bin/smbpasswd
-Compiling utils/make_smbcodepage.c
-Linking bin/make_smbcodepage
-Compiling utils/nmblookup.c
-Linking bin/nmblookup
-Compiling utils/make_printerdef.c
-Linking bin/make_printerdef</programlisting>
-
-
-<para>If you encounter problems when compiling, check the Samba documentation to see if it is easily fixable. Another possibility is to search or post to the <indexterm id="ch02-idx-947437-0"><primary>mailing lists</primary><secondary>posting to</secondary></indexterm>Samba mailing lists, which are given at the end of <link linkend="SAMBA-AP-D">Appendix D</link>, and on the Samba home page. Most compilation issues are system specific and almost always easy to overcome.</para>
-
-
-<para>Now that the files have been compiled, you can install them into the directories you identified with the command:</para>
-
-
-<programlisting>#<userinput> make install</userinput></programlisting>
-
-
-<para>If you happen to be upgrading, your old Samba files will be saved with the extension <emphasis>.old</emphasis> <indexterm id="ch02-idx-947448-0"><primary sortas="old files">.old files</primary></indexterm>, and you can go back to that previous version with the command <literal>make</literal> <literal>revert</literal>. After doing a <literal>make</literal> <literal>install</literal>, you should copy the <emphasis>.old</emphasis> files (if they exist) to a new location or name. Otherwise, the next time you install Samba, the original <emphasis>.old</emphasis> will be overwritten without warning and you could lose your earlier version. If you configured Samba to use the default locations for files, the new files will be installed in the directories listed in <link linkend="SAMBA-CH-2-TBL-2.2">Table 2.2</link>. Remember that you need to perform the installation from an account that has <indexterm id="ch02-idx-947451-0"><primary>write privileges</primary></indexterm>write privileges on these target <indexterm id="ch02-idx-947452-0"><primary>directories</primary><secondary>target</secondary></indexterm>directories; this is typically the root account.</para>
-
-
-<table label="2.2" id="SAMBA-CH-2-TBL-2.2">
-<title>Samba Installation Directories </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Directory</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><emphasis>/usr/local/samba</emphasis></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch02-idx-947450-0"><primary>installing Samba</primary><secondary>installation directories</secondary></indexterm>
-<indexterm id="ch02-idx-947450-1"><primary>directories</primary><secondary>installation</secondary></indexterm>Main tree</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis>/usr/local/samba/bin</emphasis></para></entry>
-
-<entry colname="col2"><para>Binaries</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis>/usr/local/samba/lib</emphasis></para></entry>
-
-<entry colname="col2"><para><emphasis>smb.conf</emphasis>, <emphasis>lmhosts</emphasis>, configuration files, etc.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis>/usr/local/samba/man</emphasis></para></entry>
-
-<entry colname="col2"><para>Samba documentation</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis>/usr/local/samba/private</emphasis></para></entry>
-
-<entry colname="col2"><para>Samba encrypted password file</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis>/usr/local/samba/swat</emphasis></para></entry>
-
-<entry colname="col2"><para>SWAT files</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis>/usr/local/samba/var</emphasis></para></entry>
-
-<entry colname="col2"><para>Samba log files, lock files, browse list info, shared memory files, process ID files</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Throughout the remainder of the book, we occasionally refer to the location of the <indexterm id="ch02-idx-947454-0"><primary>main tree</primary></indexterm>main tree as <replaceable>samba_dir</replaceable>. In most configurations, this is the <indexterm id="ch02-idx-947479-0"><primary>base directory</primary></indexterm>base directory of the installed Samba package: <filename>/usr/local/samba </filename>
-<indexterm id="ch02-idx-947455-0"><primary sortas="usr/local/samba file">/usr/local/samba file</primary></indexterm>.</para>
-
-
-<warning role="ora">
-<para>Watch out if you've made <filename>/usr</filename> a <indexterm id="ch02-idx-947472-0"><primary>read-only partitions</primary></indexterm>read-only partition. You will want to put the logs, locks, and password files somewhere else.</para>
-
-</warning>
-
-<para>Here is the installation that we performed on our machine. You can see that we used <filename>/usr/local/samba</filename> as the base directory for the distribution (e.g., <replaceable>samba_dir</replaceable>):</para>
-
-
-<programlisting># <userinput>make install</userinput>
-Using FLAGS = -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -DSMBLOGFILE="/
-usr/local/samba/var/log.smb" -DNMBLOGFILE="/usr/local/samba/var/log.nmb" -
-DCONFIGFILE="/usr/local/samba/lib/smb.conf" -
-
-<lineannotation>...(content omitted)...</lineannotation>
-
-The binaries are installed. You may restore the old binaries
-(if there were any) using the command "make revert". You may
-uninstall the binaries using the command "make uninstallbin"
-or "make uninstall" to uninstall binaries, man pages and shell
-scripts.
-
-<lineannotation>...(content omitted)...</lineannotation>
-
-============================================================
-The SWAT files have been installed. Remember to read the
-README for information on enabling and using SWAT.
-============================================================</programlisting>
-
-
-<para>If the last message is about SWAT, you've successfully installed all the files. Congratulations! You now have Samba on your system!</para>
-
-
-<sect2 role="" label="2.3.1" id="ch02-SECT-3.1">
-<title>Final Installation Steps</title>
-
-
-<para>
-<indexterm id="ch02-idx-947480-0"><primary>installing Samba</primary><secondary>steps in</secondary><tertiary>final</tertiary></indexterm>There are a couple of final steps to perform. Specifically, add the <indexterm id="ch02-idx-947486-0"><primary>SWAT tool</primary><secondary>adding to configuration files</secondary></indexterm>
-<indexterm id="ch02-idx-947486-1"><primary>Samba Web Administration Tool</primary><see>SWAT tool</see></indexterm>Samba Web Administration Tool (SWAT) to the <filename>/etc/services</filename>
-<indexterm id="ch02-idx-947491-0"><primary sortas="etc.services configuration files">/etc/services configuration file, adding SWAT tool to</primary></indexterm> and <filename>/etc/inetd.conf</filename>
-<indexterm id="ch02-idx-947493-0"><primary sortas="etc/inetd.conf configuration file">/etc/inetd.conf configuration files</primary><secondary>adding SWAT tool to</secondary></indexterm> configuration files. SWAT runs as a daemon under <emphasis>inetd</emphasis> and provides a forms-based editor in your web browser for creating and modifying SMB configuration files.</para>
-
-
-<orderedlist>
-<listitem><para>To add SWAT, add the following line to the end of the <filename>/etc/services</filename> file:</para>
-
-<programlisting>swat 901/tcp</programlisting></listitem>
-
-<listitem><para>Add these lines to <filename>/etc/inetd.conf.</filename> (Check your <filename>inetd.conf</filename> manual page to see the exact format of the<filename> inetd.conf</filename> file if it differs from the following example.) Don't forget to change the path to the SWAT binary if you installed it in a different location from the default <filename>/usr/local/samba</filename>.</para>
-
-
-<programlisting>swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat</programlisting></listitem>
-</orderedlist>
-
-<para>And that's pretty much it for the installation. Before you can start up Samba, however, you need to create a configuration file for it.<indexterm id="ch02-idx-947442-0" class="endofrange" startref="ch02-idx-947438-0"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="2.4" id="ch02-13464">
-<title>A Basic Samba Configuration File</title>
-
-
-<para>The <indexterm id="ch02-idx-947692-0" class="startofrange"><primary>configuring Samba</primary><secondary>configuration file</secondary><tertiary>creating</tertiary></indexterm>key to configuring Samba is its lone configuration file: <filename>smb.conf</filename>
-<indexterm id="ch02-idx-947693-0"><primary>smb.conf (Samba configuration) file</primary></indexterm>. This configuration file can be very simple or extremely complex, and the rest of this book is devoted to helping you get deeply personal with this file. For now, however, we'll show you how to set up a single file service, which will allow you to fire up the Samba daemons and see that everything is running as it should be. In later chapters, you will see how to configure Samba for more complicated and interesting tasks.</para>
-
-
-<para>The installation process does not automatically create an <filename>smb.conf</filename> configuration file, although several example files are included in the Samba distribution. <indexterm id="ch02-idx-947541-0" class="startofrange"><primary>testing</primary><secondary>Samba</secondary></indexterm>To test the server software, though, we'll use the following file. It should be named <filename>smb.conf</filename> and placed in the <emphasis>/usr/local/samba/lib</emphasis> directory.<footnote label="5" id="ch02-pgfId-943223">
-
-
-<para>If you did not compile Samba, but instead downloaded a binary, check with the documentation for the package to find out where it expects the <filename>smb.conf</filename> file. If Samba came preinstalled with your Unix system, there is probably already an <filename>smb.conf</filename> file somewhere on your system.</para>
-
-
-</footnote></para>
-
-
-<programlisting>[global]
- workgroup = SIMPLE
-[test]
- comment = For testing only, please
- path = /export/samba/test
- read only = no
- guest ok = yes</programlisting>
-
-
-<para>This brief configuration file tells the Samba server to offer the directory <filename>/export/samba/test</filename>
-<indexterm id="ch02-idx-947498-0"><primary sortas="export/samba/test directory">/export/samba/test directory</primary></indexterm> on the server as an SMB/CIFS share called <indexterm id="ch02-idx-947499-0"><primary>test share</primary></indexterm><literal>test</literal>. The server also becomes part of the named workgroup SIMPLE, which each of the clients must also be a part of. (Use your own workgroup here if you already know what it is.) We'll use the <literal>[test]</literal> share in the next chapter to set up the Windows clients. For now, you can complete the setup by performing the following commands as root on your Unix server:</para>
-
-
-<programlisting># <userinput>mkdir /export/samba/test</userinput>
-# <userinput>chmod 777 /export/samba/test</userinput></programlisting>
-
-
-<para>We should point out that in terms of system security, this is the worst setup possible. For the moment, however, we only wish to test Samba, so we'll leave security out of the picture. In addition, there are some encrypted password issues that we will encounter with Windows clients later on, so this setup will afford us the least amount of headaches.</para>
-
-
-<tip role="ora">
-<para>If you are using Windows 98 or Windows NT Service Pack 3 or above, you must add the following entry to the <literal>[global]</literal> section of the Samba configuration file: <literal>encrypt passwords = yes</literal>. In addition, you must use the <filename>smbpassword</filename> program (typically located in <filename>/usr/local/samba/bin/ </filename>) to reenter the username/password combinations of those users on the Unix server who should be able to access shares into Samba's encrypted client database. For example, if you wanted to allow Unix user <literal>steve</literal> to access shares from an SMB client, you could type: <literal>smbpassword -a steve</literal>. The first time a user is added, the program will output an error saying that the encrypted password database does not exist. Don't worry, it will then create the database for you. Make sure that the username/password combinations that you add to the encrypted database match the usernames and passwords that you intend to use on the Windows client side.</para>
-
-</tip>
-
-<sect2 role="" label="2.4.1" id="ch02-SECT-4.1">
-<title>Using SWAT</title>
-
-
-<para>
-<indexterm id="ch02-idx-947510-0" class="startofrange"><primary>SWAT tool</primary><secondary>creating configuration file with</secondary></indexterm>With Samba 2.0, creating a configuration file is even easier than writing a configuration file by hand. You can use your browser to connect to <emphasis>http://localhost:901</emphasis>, and log on as the root account, as shown in <link linkend="ch02-60915">Figure 2.1</link>.</para>
-
-
-<figure label="2.1" id="ch02-60915">
-<title>SWAT login</title>
-
-<graphic width="502" depth="188" fileref="figs/sam.0201.gif"></graphic>
-</figure>
-
-<para>After logging in, press the GLOBALS button at the top of the screen. You should see the Global Variables page shown in <link linkend="ch02-49138">Figure 2.2</link>.</para>
-
-
-<figure label="2.2" id="ch02-49138">
-<title>SWAT Global Variables page</title>
-
-<graphic width="502" depth="455" fileref="figs/sam.0202.gif"></graphic>
-</figure>
-
-<para>In this example, set the workgroup field to SIMPLE and the security field to USER. The only other option you need to change from the menu is one determining which system on the LAN resolves NetBIOS addresses; this system is called the <emphasis>WINS server</emphasis>
-<indexterm id="ch02-idx-947528-0"><primary>WINS (Windows Internet Name Service)</primary><secondary>server</secondary></indexterm>. At the very bottom of the page, set the wins support field to Yes, unless you already have a WINS server on your network. If you do, put the WINS server's IP address in the wins server field instead. Then return to the top and press the Commit Changes button to write the changes out to the <emphasis>smb.conf</emphasis> file.</para>
-
-
-<figure label="2.3" id="ch02-29175">
-<title>SWAT Share Creation screen</title>
-
-<graphic width="502" depth="392" fileref="figs/sam.0203.gif"></graphic>
-</figure>
-
-<para>Next, press the Shares icon. You should see a page similar to <link linkend="ch02-29175">Figure 2.3</link>. Choose Test in the field beside the Choose Share button. You will see the Share Parameters screen, as shown in <link linkend="ch02-37186">Figure 2.4</link>. We added a comment to remind us that this is a test share in the <filename>smb.conf</filename> file. SWAT has copies of all that information here.</para>
-
-
-<figure label="2.4" id="ch02-37186">
-<title>SWAT Share Parameters screen</title>
-
-<graphic width="502" depth="407" fileref="figs/sam.0204.gif"></graphic>
-</figure>
-
-<para>If you press the View button, SWAT shows you the following <filename>smb.conf</filename> file:</para>
-
-
-<programlisting># Samba config file created using SWAT
-# from localhost (127.0.0.1)
-# Date: 1998/11/27 15:42:40
-
-# Global parameters
- workgroup = SIMPLE
-[test]
- comment = For testing only, please
- path = /export/samba/test
- read only = no
- guest ok = yes</programlisting>
-
-
-<para>Once this configuration file is completed, you can skip the next step because the output of SWAT is guaranteed to be syntactically correct.<indexterm id="ch02-idx-947704-0" class="endofrange" startref="ch02-idx-947692-0"/></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="2.4.2" id="ch02-SECT-4.2">
-<title>Testing the Configuration File</title>
-
-
-<para>
-<indexterm id="ch02-idx-947573-0"><primary>configuring Samba</primary><secondary>configuration file</secondary><tertiary>testing</tertiary></indexterm>
-<indexterm id="ch02-idx-947573-1"><primary>testing</primary><secondary>configuration file</secondary></indexterm>If you didn't use SWAT to create your configuration file, you should probably test it to ensure that it is syntactically correct. It may seem silly to run a test program against an eight-line configuration file, but it's good practice for the real ones that we'll be writing later on.</para>
-
-
-<para>The<indexterm id="ch02-idx-947577-0"><primary>test parser</primary></indexterm> test parser, <filename>testparm</filename>
-<indexterm id="ch02-idx-947578-0"><primary>testparm test parser</primary></indexterm>, examines an <filename>smb.conf</filename> file for <indexterm id="ch02-idx-947583-0"><primary>syntax errors</primary></indexterm>
-<indexterm id="ch02-idx-947583-1"><primary>errors</primary><secondary>syntax</secondary></indexterm>syntax errors and reports any it finds along with a list of the <indexterm id="ch02-idx-947579-0"><primary>services</primary><secondary>list of enabled on machine</secondary></indexterm>services enabled on your machine. An example follows; you'll notice that in our haste to get the server running we mistyped <literal>workgroup</literal> as <literal>workgrp</literal> (the output is often lengthy, so we recommend capturing the last parts with the <literal>tee</literal> command):</para>
-
-
-<programlisting>Load smb config files from smb.conf
-Unknown parameter encountered: "workgrp"
-Ignoring unknown parameter "workgrp"
-Processing section "[test]"
-Loaded services file OK.
-Press enter to see a dump of your service definitions
-# Global parameters
-[global]
- workgroup = WORKGROUP
- netbios name =
- netbios aliases =
- server string = Samba 2.0.5a
- interfaces =
- bind interfaces only = No
-
-<lineannotation>...(content omitted)...</lineannotation>
-
-[test]
- comment = For testing only, please
- path = /export/samba/test
- read only = No
- guest ok = Yes</programlisting>
-
-
-<para>The interesting parts are at the top and bottom. The top of the output will flag any syntax errors that you may have made, and the bottom lists the services that the server thinks it should offer. A word of advice: make sure that you and the server have the same expectations.<indexterm id="ch02-idx-947566-0" class="endofrange" startref="ch02-idx-947541-0"/></para>
-
-
-<para>If everything looks good, then you are ready to fire up the server daemons!</para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="2.5" id="ch02-29069">
-<title>Starting the Samba Daemons</title>
-
-
-<para>There <indexterm id="ch02-idx-947584-0" class="startofrange"><primary>daemons</primary><secondary>starting</secondary></indexterm>
-<indexterm id="ch02-idx-947584-1"><primary>Samba</primary><secondary>daemons</secondary><see>daemons</see></indexterm>are two Samba processes, <emphasis>smbd</emphasis>
-<indexterm id="ch02-idx-947586-0"><primary>smbd daemon</primary><secondary>starting</secondary></indexterm> and <emphasis>nmbd</emphasis>
-<indexterm id="ch02-idx-947587-0"><primary>nmbd daemon</primary><secondary>starting</secondary></indexterm>, that need to be running for Samba to work correctly. There are three ways to start:</para>
-
-
-<itemizedlist>
-<listitem><para>By hand</para></listitem>
-<listitem><para>As stand-alone daemons</para></listitem>
-<listitem><para>From <emphasis>inetd</emphasis></para></listitem>
-</itemizedlist>
-
-<sect2 role="" label="2.5.1" id="ch02-SECT-5.1">
-<title>Starting the Daemons by Hand</title>
-
-
-<para>If you're in a hurry, you can start the Samba daemons by hand. As root, simply enter the following commands:</para>
-
-
-<programlisting>#<userinput> /usr/local/samba/bin/smbd -D</userinput>
-#<userinput> /usr/local/samba/bin/nmbd -D</userinput></programlisting>
-
-
-<para>At this point, Samba will be running on your system and will be ready to accept connections.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="2.5.2" id="ch02-SECT-5.2">
-<title>Stand-alone Daemons</title>
-
-
-<para>To run the Samba processes as <indexterm id="ch02-idx-947591-0"><primary>stand-alone daemons</primary></indexterm>
-<indexterm id="ch02-idx-947591-1"><primary>daemons</primary><secondary>stand-alone</secondary></indexterm>stand-alone daemons, you need to add the commands listed in the previous section to your standard Unix startup scripts. This varies depending on whether you have a BSD-style <indexterm id="ch02-idx-947596-0"><primary>Unix</primary><secondary>System V</secondary></indexterm>Unix system or a System V Unix.</para>
-
-
-<sect3 role="" label="2.5.2.1" id="ch02-SECT-5.2.1">
-<title>BSD Unix</title>
-
-
-<para>WIth a <indexterm id="ch02-idx-947597-0"><primary>BSD-style Unix system</primary></indexterm>BSD-style Unix, you need to append the following code to the <filename>rc.local </filename>
-<indexterm id="ch02-idx-947598-0"><primary>rc.local file</primary></indexterm>file, which is typically found in the <filename>/etc</filename>
-<indexterm id="ch02-idx-947599-0"><primary sortas="etc directory">/etc directory</primary></indexterm>
-<indexterm id="ch02-idx-947599-1"><primary sortas="etc/rc/d directory">/etc/rc.d directory</primary></indexterm> or <filename>/etc/rc.d</filename> directories:</para>
-
-
-<programlisting>if [ -x /usr/local/samba/bin/smbd]; then
- echo "Starting smbd..."
- /usr/local/samba/bin/smbd -D
- echo "Starting nmbd..."
- /usr/local/samba/bin/nmbd -D
-fi</programlisting>
-
-
-<para>This code is very simple; it checks to see if the <filename>smbd</filename>
-<indexterm id="ch02-idx-947600-0"><primary>smbd daemon</primary><secondary>file</secondary></indexterm> file has <indexterm id="ch02-idx-947601-0"><primary>execute permissions</primary></indexterm>execute permissions on it, and if it does, it starts up each of the Samba daemons on system boot.</para>
-</sect3>
-
-
-
-<sect3 role="" label="2.5.2.2" id="ch02-SECT-5.2.2">
-<title>System V Unix</title>
-
-
-<para>With<indexterm id="ch02-idx-947602-0"><primary>System V Unix</primary></indexterm> System V, things can get a little more complex. System V typically uses scripts to start and stop daemons on the system. Hence, you need to instruct Samba how to operate when it starts and when it stops. You can modify the contents of the <filename>/etc/rc.local</filename> directory and add something similar to the following program entitled <filename>smb </filename>:</para>
-
-
-<programlisting>#!/bin/sh
-
-# Contains the "killproc" function on Red Hat Linux
-./etc/rc.d/init.d/functions
-
-PATH="/usr/local/samba/bin:$PATH"
-
-case $1 in
- 'start')
- echo "Starting smbd..."
- smbd -D
- echo "Starting nmbd..."
- nmbd -D
- ;;
- 'stop')
- echo "Stopping smbd and nmbd..."
- killproc smbd
- killproc nmbd
- rm -f /usr/local/samba/var/locks/smbd.pid
- rm -f /usr/local/samba/var/locks/nmbd.pid
- ;;
- *)
- echo "usage: smb {start|stop}"
- ;;
-esac</programlisting>
-
-
-<para>With this script, you can start and stop the SMB service with the following commands:</para>
-
-
-<programlisting># /etc/rc.local/smb start
-Starting smbd...
-Starting nmbd...
-# /etc/rc.local/smb stop
-Stopping smbd and nmbd...</programlisting>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="2.5.3" id="ch02-SECT-5.3">
-<title>Starting From Inetd</title>
-
-
-<para>The <emphasis>inetd</emphasis>
-<indexterm id="ch02-idx-947588-0"><primary>inetd daemon, starting other daemons from</primary></indexterm> daemon is a Unix system's Internet "super daemon." It listens on TCP ports defined in <filename>/etc/services</filename>
-<indexterm id="ch02-idx-947610-0"><primary sortas="etc.services configuration files">/etc/services configuration file, adding SWAT tool to</primary></indexterm> and executes the appropriate program for each port, which is defined in <filename>/etc/inetd.conf</filename>
-<indexterm id="ch02-idx-947618-0"><primary sortas="etc/inetd.conf configuration file">/etc/inetd.conf configuration files</primary></indexterm>. The advantage of this scheme is that you can have a large number of daemons ready to answer queries, but they don't all have to be running. Instead, the <emphasis>inetd</emphasis> daemon listens in places of all the others. The penalty is a small overhead cost of creating a new daemon process, and the fact that you need to edit two files rather than one to set things up. This is handy if you have only one or two users or your machine has too many daemons already. It's also easier to perform an upgrade without disturbing an existing connection.</para>
-
-
-<para>If you wish to start from <filename>inetd</filename>, first open <filename>/etc/services</filename> in your text editor. If you don't already have them defined, add the following two lines:</para>
-
-
-<programlisting>netbios-ssn 139/tcp
-netbios-ns 137/udp</programlisting>
-
-
-<para>Next, edit <filename>/etc/inetd.conf</filename>. Look for the following two lines and add them if they don't exist. If you already have <literal>smbd</literal> and <literal>nmbd</literal> lines in the file, edit them to point at the new <emphasis>smbd</emphasis> and <emphasis>nmbd</emphasis> you've installed. Your brand of Unix may use a slightly different syntax in this file; use the existing entries and the <filename>inetd.conf </filename><command> </command>manual page<command> </command>as a guide:</para>
-
-
-<programlisting>netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
-netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd</programlisting>
-
-
-<para>Finally, kill any <emphasis>smbd</emphasis>
-<indexterm id="ch02-idx-947623-0"><primary>smbd daemon</primary><secondary>killing</secondary></indexterm> or <emphasis>nmbd</emphasis>
-<indexterm id="ch02-idx-947634-0"><primary>nmbd daemon</primary><secondary>killing</secondary></indexterm>
-<indexterm id="ch02-idx-947634-1"><primary>daemons</primary><secondary>killing</secondary></indexterm> processes and send the <emphasis>inetd</emphasis> process a <indexterm id="ch02-idx-947624-0"><primary>hangup (HUP) signal</primary></indexterm>
-<indexterm id="ch02-idx-947624-1"><primary>HUP (hangup) signal</primary></indexterm>hangup (HUP) signal. (The <emphasis>inetd</emphasis> daemon rereads its configuration file on a HUP signal.) To do this, use the <literal>ps</literal> command to find its process ID, then signal it with the following command:</para>
-
-
-<programlisting># <userinput>kill -HUP process_id</userinput></programlisting>
-
-
-<para>After that, Samba should be up and running.<indexterm id="ch02-idx-947585-0" class="endofrange" startref="ch02-idx-947584-0"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="2.6" id="ch02-67898">
-<title>Testing the Samba Daemons</title>
-
-
-<para>
-<indexterm id="ch02-idx-947635-0"><primary>daemons</primary><secondary>testing</secondary></indexterm>
-<indexterm id="ch02-idx-947635-1"><primary>testing</primary><secondary>daemons</secondary></indexterm>It's hard to believe, but we're nearly done with the Samba server setup. All that's left to do is to make sure that everything is working as we think it should. A convenient way to do this is to use the <filename>smbclient</filename>
-<indexterm id="ch02-idx-947636-0"><primary>smbclient program</primary></indexterm> program to examine what the server is offering to the network. If everything is set up properly, you should be able to do the following:</para>
-
-
-<programlisting><userinput># smbclient -U% -L localhost</userinput>
-
-Added interface ip=192.168.220.100 bcast=192.168.220.255 nmask=255.255.255.0
-Domain=[SIMPLE] OS=[Unix] Server=[Samba 2.0.5a]
-
- Sharename Type Comment
- --------- ---- -------
- test Disk For testing only, please
- IPC$ IPC IPC Service (Samba 2.0.5a)
-
- Server Comment
- --------- -------
- HYDRA Samba 2.0.5a
-
- Workgroup Master
- --------- -------
- SIMPLE HYDRA</programlisting>
-
-
-<para>If there is a problem, don't panic! Try to start the daemons manually, and check the system output or the <indexterm id="ch02-idx-947637-0"><primary>debug files</primary></indexterm>debug files at <filename>/usr/local/samba/var/log.smb</filename>
-<indexterm id="ch02-idx-947638-0"><primary sortas="usr/local/samba/var/log.smb file">/usr/local/samba/var/log.smb file</primary></indexterm> to see if you can determine what happened. If you think it may be a more serious problem, skip to <link linkend="SAMBA-CH-7">Chapter 7</link>, for help on troubleshooting the Samba daemons.</para>
-
-
-<para>If it worked, congratulations! You now have successfully set up the Samba server with a <indexterm id="ch02-idx-947664-0"><primary>disk shares</primary></indexterm>disk share. It's a simple one, but we can use it to set up and test the Windows 95 and NT clients in the next chapter. Then we will start making it more interesting by adding services such as home directories, printers, and security, and seeing how to integrate the server into a larger Windows domain.<indexterm id="ch02-idx-947297-0" class="endofrange" startref="ch02-idx-947293-0"/></para>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="3" id="SAMBA-CH-3">
-<title>Configuring Windows Clients</title>
-
-
-
-
-<para>
-<indexterm id="ch03-idx-947918-0" class="startofrange"><primary>Windows clients</primary><secondary>configuring</secondary></indexterm>
-<indexterm id="ch03-idx-947918-1" class="startofrange"><primary>configuring Windows clients</primary></indexterm>You'll be glad to know that configuring Windows to use your new Samba server is quite simple. SMB is Microsoft's native language for resource sharing on a local area network, so much of the installation and setup on the Windows client side has been taken care of already. The primary issues that we will cover in this chapter involve communication and coordination between Windows and Unix, two completely different operating systems.</para>
-
-
-<para>Samba uses TCP/IP to talk to its clients on the network. If you aren't already using TCP/IP on your Windows computers, this chapter will show you how to install it. Then you'll need to configure your Windows machines to operate on a TCP/IP network. Once these two requirements have been taken care of, we can show how to access a shared disk on the Samba server.</para>
-
-
-<para>This chapter is divided into three sections. The first section covers setting up Windows 95/98 computers while the second covers Windows NT 4.0 machines. The final section provides some prerequisite information on how SMB connections are made from Windows clients and servers, which is useful as we move into the later chapters of the book.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="3.1" id="ch03-55770">
-<title>Setting Up Windows 95/98 Computers</title>
-
-
-<para>
-<indexterm id="ch03-idx-947927-0" class="startofrange"><primary>Windows clients</primary><secondary>configuring</secondary><tertiary>Windows95/98 computers</tertiary></indexterm>
-<indexterm id="ch03-idx-947927-1" class="startofrange"><primary>configuring Windows clients</primary><secondary>Windows 95/98 computers</secondary></indexterm>Unfortunately, Windows 95/98 wasn't designed for a PC to have more than one user; that concept is more inherent to a Unix operating system or Windows NT. However, <indexterm id="ch03-idx-947953-0"><primary>Windows 95/98</primary><secondary>multiple users, support for</secondary></indexterm>Windows 95/98 does have <emphasis>limited</emphasis> support for multiple users: if you tell it, the operating system will keep a separate <indexterm id="ch03-idx-947955-0"><primary>user profiles (Windows 95/98)</primary></indexterm>profile (desktop layout) and password file for each user. This is a far cry from true multiuser security. In other words, Windows 95/98 won't try to keep one user from destroying the work of another on the local hard drive like Unix, but profiles are a place to start.</para>
-
-
-<sect2 role="" label="3.1.1" id="ch03-SECT-1.1">
-<title>Accounts and Passwords</title>
-
-
-<para>
-<indexterm id="ch03-idx-947956-0" class="startofrange"><primary>accounts</primary></indexterm>
-<indexterm id="ch03-idx-947956-1" class="startofrange"><primary>passwords</primary><secondary>Windows 95/98</secondary></indexterm>
-<indexterm id="ch03-idx-947956-2" class="startofrange"><primary>usernames</primary><secondary>Windows 95/98</secondary></indexterm>The first thing we need to do is to tell Windows to keep user profiles separate, and to collect usernames and passwords to authenticate anyone trying to access a Samba share. We do so via the <indexterm id="ch03-idx-947957-0"><primary>Password settings (Windows 95/98)</primary></indexterm>Password settings in the Control Panel. If you are not familiar with the Windows Control Panel, you can access it by choosing the Settings menu item from the pop-up menu of the Start button in the lower-left corner of the screen. Alternatively, you'll find it as a folder under the icon in the upper-left corner that represents your computer and is typically labeled <indexterm id="ch03-idx-947958-0"><primary>My Computer (Windows 95/98)</primary></indexterm>My Computer.</para>
-
-
-<para>After selecting the Passwords icon in the Control Panel, click on the User Profiles tab on the far right. You should see the dialog box shown in <link linkend="ch03-84319">Figure 3.1</link>. Then click the lower of the two radio buttons that starts "Users can customize their preferences...." This causes Windows to store a separate profile for each user, and saves the username and password you provide, which it will use later when it connects to an SMB/CIFS server. Finally, check <emphasis>both</emphasis> the options under the User Profile Settings border, as shown in the figure.</para>
-
-
-<figure label="3.1" id="ch03-84319">
-<title>The Passwords Properties panel</title>
-
-<graphic width="502" depth="289" fileref="figs/sam.0301.gif"></graphic>
-</figure>
-
-<para>The next step is to select the Change Passwords tab on the left side of the dialog box. In order for Samba to allow you access to its shares, the username and password you give to Windows must match the account and password on the Samba server. If you don't have this tab in your dialog box, don't worry; it's probably because you haven't given yourself a Windows username and password yet. Simply click the OK button at the bottom and respond Yes when Windows asks to reboot. Then, skip down to <link linkend="ch03-57581">Section 3.1.1.2</link>.</para>
-
-
-<sect3 role="" label="3.1.1.1" id="ch03-SECT-1.1.1">
-<title>Changing the Windows password</title>
-
-
-<para>
-<indexterm id="ch03-idx-947966-0"><primary>passwords</primary><secondary>Windows 95/98</secondary><tertiary>changing</tertiary></indexterm>After selecting the Change Passwords tab, the dialog box in <link linkend="ch03-26778">Figure 3.2</link> will appear.</para>
-
-
-<figure label="3.2" id="ch03-26778">
-<title>The Change Passwords tab</title>
-
-<graphic width="502" depth="306" fileref="figs/sam.0302.gif"></graphic>
-</figure>
-
-<para>Select the Change Windows Password button. The <indexterm id="ch03-idx-947967-0"><primary>Change Windows Password dialog box</primary></indexterm>Change Windows Password dialog box should appear, as shown in <link linkend="ch03-97002">Figure 3.3</link>. From here, you can change your password to match the password of the account on the Samba server through which you intend to log in.</para>
-
-
-<figure label="3.3" id="ch03-97002">
-<title>The Change Windows Password dialog box</title>
-
-<graphic width="502" depth="135" fileref="figs/sam.0303.gif"></graphic>
-</figure>
-</sect3>
-
-
-
-<sect3 role="" label="3.1.1.2" id="ch03-57581">
-<title>Logging in for the first time</title>
-
-
-<para>
-<indexterm id="ch03-idx-947969-0"><primary>log files/logging</primary><secondary>in for the first time (Samba)</secondary></indexterm>
-<indexterm id="ch03-idx-947969-1"><primary>Samba</primary><secondary>logging in for the first time</secondary></indexterm>If you didn't have a Change Passwords tab in the Passwords Properties window, then after Windows has finished rebooting, it will ask you to log in with a username and a password. Give yourself the same username and password that you have on the Samba server. After confirming your new username and password, or if you already have one, Windows should ask you if you want to have a <indexterm id="ch03-idx-947970-0"><primary>profiles</primary><secondary>creating</secondary></indexterm>profile, using the dialog shown in <link linkend="ch03-48947">Figure 3.4</link>. <indexterm id="ch03-idx-947961-0" class="endofrange" startref="ch03-idx-947956-0"/>
-<indexterm id="ch03-idx-947961-1" class="endofrange" startref="ch03-idx-947956-1"/>
-<indexterm id="ch03-idx-947961-2" class="endofrange" startref="ch03-idx-947956-2"/></para>
-
-
-<figure label="3.4" id="ch03-48947">
-<title>Windows Networking profiles</title>
-
-<graphic width="502" depth="121" fileref="figs/sam.0304.gif"></graphic>
-</figure>
-
-<para>Answer Yes, upon which Windows will create a separate profile and password file for you and save a copy of your password in the file. Now when you connect to Samba, Windows will send its password, which will be used to authenticate you for each share. We won't worry about profiles for the moment; we'll cover them in <link linkend="SAMBA-CH-6">Chapter 6</link>. We should point out, however, that there is a small security risk: someone can steal the <indexterm id="ch03-idx-947972-0"><primary>password file, security and</primary></indexterm>password file and decrypt the passwords because it's weakly encrypted. Unfortunately, there isn't a solution to this with Windows 95/98. In Windows 2000 (NT 5.0), the password encryption should be replaced with a much better algorithm.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.1.2" id="ch03-36280">
-<title>Setting Up the Network</title>
-
-
-<para>
-<indexterm id="ch03-idx-947983-0" class="startofrange"><primary>networking</primary><secondary>setting up</secondary></indexterm>The next thing we need to do is make sure we have the <indexterm id="ch03-idx-947973-0"><primary>TCP/IP networking protocol</primary><secondary>checking setup</secondary></indexterm>TCP/IP networking protocol set up correctly. To do this, double-click on the <indexterm id="ch03-idx-947975-0"><primary>Network icon</primary><secondary>Windows 95/98</secondary></indexterm>Network icon in the Control Panel. You should see the network configuration dialog box, as shown in <link linkend="ch03-15320">Figure 3.5</link>.</para>
-
-
-<figure label="3.5" id="ch03-15320">
-<title>The Windows 95/98 Network panel</title>
-
-<graphic width="502" depth="371" fileref="figs/sam.0305.gif"></graphic>
-</figure>
-
-<para>Microsoft networking works by binding specific protocols, such as IPX or TCP/IP, to a specific hardware device, such as an <indexterm id="ch03-idx-947977-0"><primary>Ethernet adaptor cards</primary></indexterm>Ethernet card or a <indexterm id="ch03-idx-948013-0"><primary>dialup connection</primary></indexterm>dialup connection. By routing a <indexterm id="ch03-idx-947976-0"><primary>protocols</primary><secondary>routed through a hardware device</secondary></indexterm>protocol through a hardware device, the machine can act as a client or server for a particular type of network. For Samba, we are interested in binding the TCP/IP protocol through a networking device, making the machine a client for Microsoft networks. Thus, when the dialog box appears, you should see at least the Client for Microsoft Networks component installed on the machine, and hopefully a networking device (preferably an Ethernet card) bound to the TCP/IP protocol. If there is only one networking hardware device, you'll see the TCP/IP protocol listed below that device. If it appears similar to <link linkend="ch03-15320">Figure 3.5</link>, the protocol is bound to the device.</para>
-
-
-<para>You may also see <indexterm id="ch03-idx-947979-0"><primary sortas="File and Printer Sharing for Microsoft Networks">"File and Printer Sharing for Microsoft Networks"</primary></indexterm>"File and printer sharing for Microsoft Networks," which is useful. In addition, you might see <indexterm id="ch03-idx-947981-0"><primary>NetBEUI (NetBIOS Extended User Interface)</primary></indexterm>NetBEUI or <indexterm id="ch03-idx-947982-0"><primary>Novell Networking</primary></indexterm>Novell Networking, which are standard with Windows installations but undesirable when TCP/IP is running. Remove NetBEUI if you possibly can—it's unnecessary and makes debugging Windows browsing difficult. If you don't have any Novell servers on your network, you can remove Novell (IPX/SPX) as well.</para>
-
-
-<sect3 role="" label="3.1.2.1" id="ch03-SECT-1.2.1">
-<title>Adding TCP/IP</title>
-
-
-<para>
-<indexterm id="ch03-idx-947991-0" class="startofrange"><primary>TCP/IP networking protocol</primary><secondary>adding/configuring</secondary></indexterm>If you don't see TCP/IP listed at all, you'll need to install the protocol. If you already have TCP/IP, skip this section, and continue with <link linkend="ch03-48802">Section 3.1.3</link>, later in this chapter.</para>
-
-
-<para>Installing TCP/IP isn't difficult since Microsoft distributes its own version of TCP/IP for free on their installation CD-ROM. You can add the protocol by clicking on the Add button below the component window. Indicate that you wish to add a specific protocol by selecting Protocol and clicking Add... on the following dialog box, which should look similar to <link linkend="ch03-24245">Figure 3.6</link>.</para>
-
-
-<figure label="3.6" id="ch03-24245">
-<title>Selecting a protocol to install</title>
-
-<graphic width="502" depth="195" fileref="figs/sam.0306.gif"></graphic>
-</figure>
-
-<para>After that, select the protocol TCP/IP from manufacturer Microsoft, as shown in <link linkend="ch03-50801">Figure 3.7</link>, then click OK. After doing so, you will be returned to the network dialog. Click OK there to close the dialog box, upon which Windows will install the necessary components from disk and reboot the machine.</para>
-
-
-<figure label="3.7" id="ch03-50801">
-<title>Selecting a protocol to install</title>
-
-<graphic width="502" depth="296" fileref="figs/sam.0307.gif"></graphic>
-</figure>
-</sect3>
-
-
-
-<sect3 role="" label="3.1.2.2" id="ch03-SECT-1.2.2">
-<title>Configuring TCP/IP</title>
-
-
-<para>
-<indexterm id="ch03-idx-948011-0"><primary>configuring TCP/IP networking protocol</primary></indexterm>If you have more than one networking device (for example, both an <indexterm id="ch03-idx-948014-0"><primary>Ethernet adaptor cards</primary><secondary>linking to TCP/IP networking protocol</secondary></indexterm>Ethernet card and a dialup networking <indexterm id="ch03-idx-948015-0"><primary>modem, linking to TCP/IP networking protocol</primary></indexterm>modem), each appropriate hardware device should be "linked" to the TCP/IP protocol with an arrow, as shown in <link linkend="ch03-61576">Figure 3.8</link>. Select the TCP/IP protocol linked to the networking device that will be accessing the Samba network. When it is highlighted, click the<indexterm id="ch03-idx-948019-0"><primary>Properties button (Windows 95/98)</primary></indexterm> Properties button.</para>
-
-
-<figure label="3.8" id="ch03-61576">
-<title>Selecting the correct TCP/IP protocol</title>
-
-<graphic width="502" depth="389" fileref="figs/sam.0308.gif"></graphic>
-</figure>
-
-<para>After doing so, the <indexterm id="ch03-idx-948028-0"><primary>TCP/IP Properties panel (Windows 95/98)</primary></indexterm>TCP/IP Properties panel for that device is displayed, as shown in <link linkend="ch03-73526">Figure 3.9</link>.</para>
-
-
-<figure label="3.9" id="ch03-73526">
-<title>STCP/IP Properties panel</title>
-
-<graphic width="502" depth="303" fileref="figs/sam.0309.gif"></graphic>
-</figure>
-
-<para>There are seven tabs near the top of this panel, and you will need to configure four of them:</para>
-
-
-<itemizedlist>
-<listitem><para>IP address</para></listitem>
-<listitem><para>DNS configuration</para></listitem>
-<listitem><para>WINS configuration</para></listitem>
-<listitem><para>Bindings</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="3.1.2.3" id="ch03-SECT-1.2.3">
-<title>IP Address tab </title>
-
-
-<para>The <indexterm id="ch03-idx-948038-0"><primary>IP Address tab</primary><secondary>Windows 95/98</secondary></indexterm>
-<indexterm id="ch03-idx-948038-1"><primary>DHCP (Dynamic Host Configuration Protocol)</primary></indexterm>IP Address tab is shown in <link linkend="ch03-73526">Figure 3.9</link>. Press the "Specify an IP address" radio button and enter the client's address and subnet <indexterm id="ch03-idx-948214-0"><primary>masks</primary><secondary>subnet</secondary></indexterm>
-<indexterm id="ch03-idx-948214-1"><primary>subnets</primary><secondary>mask</secondary></indexterm>mask in the space provided. You or your network manager should have selected an address for the machine. The values should place the computer on the same subnet as the Samba server. For example, if the server's address is 192.168.236.86, and its network <indexterm id="ch03-idx-948217-0"><primary>masks</primary><secondary>netmasks</secondary></indexterm>
-<indexterm id="ch03-idx-948217-1"><primary>netmasks</primary></indexterm>
-<indexterm id="ch03-idx-948217-2"><primary>network masks</primary><see>netmasks</see></indexterm>mask 255.255.255.0, you might use address 192.168.236.10 (if it is available) for the Windows 98 computer, along with the same netmask as the server. If you already use DHCP on your network to provide IP addresses to Windows machines, select the "Obtain an IP address automatically" button.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.1.2.4" id="ch03-SECT-1.2.4">
-<title>DNS Configuration tab</title>
-
-
-<para>
-<indexterm id="ch03-idx-948039-0"><primary>DNS Configuration tab</primary></indexterm>Domain Name Service (<indexterm id="ch03-idx-948040-0"><primary>DNS (Domain Name System)</primary></indexterm>
-<indexterm id="ch03-idx-948040-1"><primary>Domain Name System</primary><see>DNS</see></indexterm>DNS) is responsible for translating Internet computer names such as <emphasis>hobbes.example.com</emphasis> into machine-readable IP addresses such as 192.168.236.10. There are two ways to accomplish this on a Windows 98 machine: you can specify a server to do the translation for you or you can keep a local list of name/address pairs to refer to.</para>
-
-
-<para>Networks that are connected to the Internet typically use a server, since the hosts files required would otherwise be huge. For an unconnected LAN, the list of possible hosts is small and well-known and might be kept on a Unix machine in the <emphasis>/etc/hosts</emphasis>
-<indexterm id="ch03-idx-948046-0"><primary sortas="etc/hosts file">/etc/hosts file</primary></indexterm> file. If you are in doubt as to whether a DNS server is being used, or what its address might be, look at the file <emphasis>/etc/resolv.conf</emphasis>
-<indexterm id="ch03-idx-948047-0"><primary sortas="etc/resolv.conf file">/etc/resolv.conf file </primary></indexterm> on your Unix servers. Any machine using DNS will have this file, which looks like:</para>
-
-
-<programlisting>#resolv.conf
-domain example.com
-nameserver 127.0.0.1
-nameserver 192.168.236.20</programlisting>
-
-
-<para>In the example shown, the second <literal>nameserver</literal> line in the list contains the IP address of another machine on the local network: 192.168.236.20. It's a good candidate for a DNS server.<footnote label="1" id="ch03-pgfId-942097">
-
-
-<para>We can disqualify the other address because every Unix machine has a localhost address of 127.0.0.1 whether it is connected to a network or not. This address is required for some system tools to operate correctly.</para>
-
-
-</footnote></para>
-
-
-<para>You must type the correct IP address of one or more DNS servers (note that you <emphasis>cannot</emphasis> use its Internet name, such as <emphasis>dns.oreilly.com</emphasis>) into the appropriate field in <link linkend="ch03-86883">Figure 3.10</link>. Be sure not to use 127.0.0.1—that will never be the correct DNS server address!</para>
-
-
-<para>Try to select addresses on your own network. Any name servers listed in <emphasis>/etc/resolv.conf</emphasis> should work, but you'll get better performance by using a server nearby. (If you don't find <emphasis>/etc/resolv.conf</emphasis> files on your Unix machines, just disable DNS until you can find the address of at least one DNS server.) Let's assume you only have one DNS server, and its address is 192.168.236.20. Click the Enable DNS radio button, as shown in <link linkend="ch03-86883">Figure 3.10</link>, and add the server's address to the top DNS Server Search Order field.</para>
-
-
-<figure label="3.10" id="ch03-86883">
-<title>The DNS Configuration tab</title>
-
-<graphic width="502" depth="360" fileref="figs/sam.0310.gif"></graphic>
-</figure>
-
-<para>Also, provide the name of the Windows 95/98 machine and the Internet domain you're in. You can safely ignore the Domain Suffix Search Order field for anything related to Samba.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.1.2.5" id="ch03-SECT-1.2.5">
-<title>WINS Configuration tab</title>
-
-
-<para>
-<indexterm id="ch03-idx-948063-0"><primary>WINS Configuration tab</primary></indexterm>WINS is the <indexterm id="ch03-idx-948065-0"><primary>WINS (Windows Internet Name Service)</primary></indexterm>
-<indexterm id="ch03-idx-948065-1"><primary>Windows Internet Name Service</primary><see>WINS</see></indexterm>Windows Internet Name Service, its version of a <indexterm id="ch03-idx-948066-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>name server (NBNS)</secondary></indexterm>NetBIOS name server. If you've enabled WINS on Samba, you must tell Windows the Samba server's address. If you are using WINS servers that are entirely Windows NT, enter each of them here as well. The dialog box shown after selecting the WINS Configuration tab is shown in <link linkend="ch03-95608">Figure 3.11</link>.</para>
-
-
-<figure label="3.11" id="ch03-95608">
-<title>The WINS Configuration tab</title>
-
-<graphic width="502" depth="389" fileref="figs/sam.0311.gif"></graphic>
-</figure>
-
-<warning role="ora">
-<para>Do <emphasis>not</emphasis> mix a Samba WINS server and a Windows NT server as a primary/backup combination in the WINS dialog. Because the two cannot replicate their databases, this will cause name resolution to perform incorrectly.</para>
-
-</warning>
-
-<para>From here, select Enable WINS Resolution and enter the <indexterm id="ch03-idx-948058-0"><primary>WINS (Windows Internet Name Service)</primary><secondary>servers</secondary></indexterm>WINS server's address in the space provided, then press Add. Do not enter anything in the Scope ID field.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.1.2.6" id="ch03-SECT-1.2.6">
-<title>Hosts files</title>
-
-
-<para>
-<indexterm id="ch03-idx-948067-0"><primary>hosts</primary><secondary>files (Windows 95/98)</secondary></indexterm>If you do not have either DNS or WINS, and you don't wish to use <indexterm id="ch03-idx-948070-0"><primary>broadcast resolution</primary></indexterm>broadcast resolution, you'll need to provide a table of IP addresses and hostnames, in the standard Unix <filename>/etc/hosts</filename> format. On a Windows machine, this goes in <indexterm id="ch03-idx-948075-0"><primary sortas="Windows/HOSTS directory">\WINDOWS\HOSTS directory</primary></indexterm>\WINDOWS\HOSTS under whichever drive you installed Windows on (typically C:\). A sample host file follows:</para>
-
-
-<programlisting># 127.0.0.1 localhost
-192.168.236.1 escrime.example.com escrime
-192.168.236.2 riposte.example.com riposte
-192.168.236.3 wizzin.example.com wizzin
-192.168.236.4 touche.example.com touche
-192.168.236.10 hobbes.example.com hobbes</programlisting>
-
-
-<para>You can copy this file directly from any of your Unix machines' <emphasis>/etc/hosts</emphasis> <indexterm id="ch03-idx-948074-0"><primary sortas="etc/hosts file">/etc/hosts file</primary></indexterm>; the format is identical. However, <emphasis>you should only use hosts files in Windows as a last resort for name resolution</emphasis>
-<indexterm id="ch03-idx-948069-0"><primary>name resolution</primary></indexterm>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.1.2.7" id="ch03-SECT-1.2.7">
-<title>Check the bindings</title>
-
-
-<para>The final tab to look at is <indexterm id="ch03-idx-948076-0"><primary>Bindings tab</primary></indexterm>Bindings, as shown in <link linkend="ch03-42906">Figure 3.12</link>.</para>
-
-
-<figure label="3.12" id="ch03-42906">
-<title>The Bindings tab</title>
-
-<graphic width="502" depth="249" fileref="figs/sam.0312.gif"></graphic>
-</figure>
-
-<para>You should have a check beside Client for Microsoft Networks, indicating that it's using TCP/IP. If you have <indexterm id="ch03-idx-948077-0"><primary sortas="File and Printer Sharing for Microsoft Networks">"File and Printer Sharing for Microsoft Networks"</primary></indexterm>"File and printer sharing for Microsoft Networks" in the dialog, it should also be checked, as shown in the figure.<indexterm id="ch03-idx-947986-0" class="endofrange" startref="ch03-idx-947983-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.1.3" id="ch03-48802">
-<title>Setting Your Name and Workgroup </title>
-
-
-<para>
-<indexterm id="ch03-idx-948082-0"><primary>naming</primary><secondary>TCP/IP networking protocol, setting machine name for</secondary></indexterm>
-<indexterm id="ch03-idx-948082-1"><primary>workgroups</primary><secondary>setting</secondary></indexterm>Finally, press the OK button in the TCP/IP configuration panel, and you'll be taken back to the Network Configuration screen. Then select the <indexterm id="ch03-idx-948078-0"><primary>Identification tab</primary></indexterm>Identification tab, which will take you to the dialog box shown in <link linkend="ch03-42408">Figure 3.13</link>.</para>
-
-
-<figure label="3.13" id="ch03-42408">
-<title>The Identification tab</title>
-
-<graphic width="502" depth="285" fileref="figs/sam.0313.gif"></graphic>
-</figure>
-
-<para>Here, for the second time, set your machine's name. This time, instead of your DNS hostname and domain, you're setting your <indexterm id="ch03-idx-948084-0"><primary>NetBIOS name</primary><secondary>setting</secondary><tertiary>Windows 95/98</tertiary></indexterm>NetBIOS name. However, it is best to make this the <emphasis>same</emphasis> as your hostname. Try not to make a <indexterm id="ch03-idx-948085-0"><primary>spelling, caution with</primary></indexterm>spelling mistake: it can be very confusing to configure a machine if TCP thinks it's <literal>fred</literal> and SMB thinks its <literal>ferd</literal> !</para>
-
-
-<para>You also set your workgroup name here. In our case, it's SIMPLE, but if you used a different one in <link linkend="SAMBA-CH-2">Chapter 2</link>, when creating the Samba configuration file, use that here as well. Try to avoid calling it WORKGROUP or you'll be in the same workgroup as every unconfigured (or ill-configured) machine in the world.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.1.4" id="ch03-13238">
-<title>Accessing the Samba Server</title>
-
-
-<para>
-<indexterm id="ch03-idx-948086-0"><primary>Samba server</primary><secondary>accessing</secondary></indexterm>
-<indexterm id="ch03-idx-948086-1"><primary>accessing Samba server</primary></indexterm>Click on the OK button to complete the configuration; you will need to reboot in order for your changes to take effect.</para>
-
-
-<para>Now for the big moment. Your Samba server is running, and you have set up your Windows 95/98 client to communicate with it. After rebooting, log in and double-click the <indexterm id="ch03-idx-948087-0"><primary>Network Neighborhood icon</primary></indexterm>Network Neighborhood icon on the desktop. You should see your Samba server listed as a member of the workgroup, as shown in <link linkend="ch03-88553">Figure 3.14</link>.</para>
-
-
-<figure label="3.14" id="ch03-88553">
-<title>Windows Network Neighborhood</title>
-
-<graphic width="502" depth="139" fileref="figs/sam.0314.gif"></graphic>
-</figure>
-
-<para>Double-clicking the server name will show the resources that the server is offering to the network, as shown in <link linkend="ch03-17463">Figure 3.15</link> (in this case a printer and the <emphasis>test</emphasis> directory).</para>
-
-
-<figure label="3.15" id="ch03-17463">
-<title>Shares on Server</title>
-
-<graphic width="502" depth="152" fileref="figs/sam.0315.gif"></graphic>
-</figure>
-
-<warning role="ora">
-<para>If you are presented with a dialog requesting the password for a user <literal>IPC$</literal>, then Samba did not accept the password that was sent from the client. In this case, the username and the password that were created on the client side <emphasis>must</emphasis> match the username/password combination on the Samba server. If you are using Windows 98 or Windows NT Service Pack 3 or above, this is probably because the client is sending encrypted passwords instead of plaintext passwords. You can remedy this situation by performing two steps on the Samba server. First, add the following entry to the <literal>[global]</literal> section of your Samba configuration file: <literal>encrypt password=yes</literal>. Second, find the <filename>smbpasswd</filename> program on the samba server (it is located in <filename>/usr/local/samba/bin</filename> by default) and use it to add an entry to Samba's encrypted password database. For example, to add user <literal>steve</literal> to Samba's encrypted password database, type <replaceable>smbpasswd -a steve</replaceable>. The first time you enter this password, the program will output an error message indicating that the password database does not exist; it will then create the database, which is typically stored in <filename>/usr/local/samba/private/smbpasswd</filename>.</para>
-
-</warning>
-
-<para>If you don't see the server listed, start Windows Explorer (not Internet Explorer!) and select <indexterm id="ch03-idx-948088-0"><primary>Map Network Drive option</primary></indexterm>Map Network Drive from the Tools menu. This will give you a dialog box into which you can type the name of your server and the share <literal>test </literal>in the <indexterm id="ch03-idx-948089-0"><primary>Windows UNC format</primary></indexterm>Windows UNC format: <filename>\\</filename><replaceable>server</replaceable><filename>\test</filename>, like we did in the first chapter. This should attempt to contact the Samba server and its temporary share. If things still aren't right, go to <link linkend="SAMBA-CH-9">Chapter 9</link>, for troubleshooting assistance.<indexterm id="ch03-idx-947933-0" class="endofrange" startref="ch03-idx-947927-0"/>
-<indexterm id="ch03-idx-947933-1" class="endofrange" startref="ch03-idx-947927-1"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="3.2" id="ch03-23093">
-<title>Setting Up Windows NT 4.0 Computers</title>
-
-
-<para>
-<indexterm id="ch03-idx-947940-0" class="startofrange"><primary>Windows clients</primary><secondary>configuring</secondary><tertiary>Windows NT 4.0 computers</tertiary></indexterm>
-<indexterm id="ch03-idx-947940-1" class="startofrange"><primary>configuring Windows clients</primary><secondary>Windows NT 4.0 computers</secondary></indexterm>Configuring Windows NT is a little different than configuring Windows 95/98. In order to use Samba with Windows NT, you will need both the Workstation service and the TCP/IP protocol. Both come standard with NT, but we'll work through installing and configuring them because they may not be configured correctly.</para>
-
-
-<para>There are six basic steps:</para>
-
-
-<orderedlist>
-<listitem><para>Assign the machine a name.</para></listitem>
-<listitem><para>Install the Workstation service.</para></listitem>
-<listitem><para>Install the TCP/IP protocol.</para></listitem>
-<listitem><para>Set the machine's name and IP address.</para></listitem>
-<listitem><para>Configure the DNS and WINS name services.</para></listitem>
-<listitem><para>Bind the protocol and service together.</para></listitem>
-</orderedlist>
-
-<sect2 role="" label="3.2.1" id="ch03-SECT-2.1">
-<title>Basic Configuration</title>
-
-
-<para>
-<indexterm id="ch03-idx-948108-0" class="startofrange"><primary>configuring Windows clients</primary><secondary>Windows NT 4.0 computers</secondary><tertiary>basic configuration</tertiary></indexterm>This section presents an outline of the steps to follow for getting Windows NT to cooperate with Samba. If you need more details on Windows NT network administration, refer to Craig Hunt and Robert Bruce Thompsom's <citetitle>Windows NT TCP/IP Network Administration </citetitle>(O'Reilly), an excellent guide. You should perform these steps as the "Administrator" user.</para>
-
-
-<sect3 role="" label="3.2.1.1" id="ch03-SECT-2.1.1">
-<title>Name the machine</title>
-
-
-<para>
-<indexterm id="ch03-idx-948120-0"><primary>naming</primary><secondary>NT computers</secondary></indexterm>
-<indexterm id="ch03-idx-948120-1"><primary>Windows NT</primary><secondary>naming, caution with</secondary></indexterm>The first thing you need to do is to give the machine a <indexterm id="ch03-idx-948122-0"><primary>NetBIOS name</primary><secondary>setting</secondary><tertiary>Windows NT</tertiary></indexterm>NetBIOS name. From the Control Panel, double click on the <indexterm id="ch03-idx-948123-0"><primary>Network icon</primary><secondary>Windows NT</secondary></indexterm>Network icon. This will take you to the <indexterm id="ch03-idx-948124-0"><primary>Network dialog box (Windows NT)</primary></indexterm>Network dialog box for the machine. The first tab in this dialog box should be the Identification tab, as illustrated in <link linkend="ch03-82592">Figure 3.16</link>.</para>
-
-
-<figure label="3.16" id="ch03-82592">
-<title>Network panel Identification tab</title>
-
-<graphic width="502" depth="260" fileref="figs/sam.0316.gif"></graphic>
-</figure>
-
-<para>Here, you need to identify your machine with a name (we use the name Artish here) and change the default workgroup to the one you specified in the <emphasis>smb.conf</emphasis>
-<indexterm id="ch03-idx-948125-0"><primary>smb.conf (Samba configuration) file</primary></indexterm> file of your Samba server. In this case, the workgroup name is SIMPLE. However, you cannot edit either name here (as you could in Windows 95/98), but instead must use the Change button below the two text fields. Pressing this button raises an <indexterm id="ch03-idx-948126-0"><primary>Identification Changes dialog box (Windows NT)</primary></indexterm>Identification Changes dialog box, where you can reset the workgroup and the machine name, as shown in <link linkend="ch03-67735">Figure 3.17</link>.</para>
-
-
-<figure label="3.17" id="ch03-67735">
-<title>Changing the identification</title>
-
-<graphic width="502" depth="360" fileref="figs/sam.0317.gif"></graphic>
-</figure>
-
-<para>
-<indexterm id="ch03-idx-948129-0"><primary>naming</primary><secondary>NT computers</secondary><tertiary>caution with</tertiary></indexterm>A word of warning: you will have to set the machine name again later while configuring TCP/IP, so be sure that the two names match. The name you set here is the NetBIOS name. You're allowed to make it different from the TCP/IP hostname, but doing so is usually not a good thing. Don't worry that Windows NT forces the computer name and the workgroup to be all capital letters; it's smart enough to figure out what you mean when it connects to the network.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.2.1.2" id="ch03-SECT-2.1.2">
-<title>Installing the TCP/IP protocol</title>
-
-
-<para>
-<indexterm id="ch03-idx-948143-0"><primary>TCP/IP networking protocol</primary><secondary>installing</secondary></indexterm>
-<indexterm id="ch03-idx-948143-1"><primary>installing TCP/IP protocol</primary></indexterm>Next, select the <indexterm id="ch03-idx-948150-0"><primary>Protocols tab</primary></indexterm>Protocols tab in the Network dialog box, and look to see if you have the TCP/IP protocol installed, as shown in <link linkend="ch03-66055">Figure 3.18</link>.</para>
-
-
-<figure label="3.18" id="ch03-66055">
-<title>The Protocols tab</title>
-
-<graphic width="502" depth="257" fileref="figs/sam.0318.gif"></graphic>
-</figure>
-
-<para>If the protocol is not installed, you need to add it. Press the Add button, which will display the <indexterm id="ch03-idx-948148-0"><primary>Select Network Protocol dialog box</primary></indexterm>Select Network Protocol dialog box shown in <link linkend="ch03-22321">Figure 3.19</link>. Unlike Windows 95/98, you should immediately see the TCP/IP protocol as one of the last protocols listed.</para>
-
-
-<figure label="3.19" id="ch03-22321">
-<title>Select Network Protocol dialog box</title>
-
-<graphic width="502" depth="285" fileref="figs/sam.0319.gif"></graphic>
-</figure>
-
-<para>Select TCP/IP<emphasis></emphasis> as the protocol and confirm it. If possible, install only the TCP/IP protocol. You usually do not want <indexterm id="ch03-idx-948149-0"><primary>NetBEUI (NetBIOS Extended User Interface)</primary><secondary>Windows NT computers and</secondary></indexterm>NetBEUI installed because this causes the machine to look for services under two different protocols, only one of which is likely in use.<footnote label="2" id="ch03-pgfId-943371">
-
-
-<para>A common occurrence: after looking at the unused protocol for a while, the machine will time out and try the good one. This fruitless searching gives you terrible performance and mysterious delays.</para>
-
-
-</footnote></para>
-</sect3>
-
-
-
-<sect3 role="" label="3.2.1.3" id="ch03-SECT-2.1.3">
-<title>Installing the Workstation service</title>
-
-
-<para>
-<indexterm id="ch03-idx-948151-0"><primary>Workstation service, installing</primary></indexterm>
-<indexterm id="ch03-idx-948151-1"><primary>installing Workstation service</primary></indexterm>
-<indexterm id="ch03-idx-948151-2"><primary>services</primary><secondary>Workstation</secondary></indexterm>After installing TCP/IP, press the <indexterm id="ch03-idx-948152-0"><primary>Services tab</primary></indexterm>Services tab in the Network panel and check that you have a Workstation service, as shown at the end of the list in <link linkend="ch03-97222">Figure 3.20</link>.</para>
-
-
-<figure label="3.20" id="ch03-97222">
-<title>Network Services panel dialog box</title>
-
-<graphic width="502" depth="289" fileref="figs/sam.0320.gif"></graphic>
-</figure>
-
-<para>This service is actually the <indexterm id="ch03-idx-948153-0"><primary>Microsoft Networking Client</primary></indexterm>Microsoft Networking Client, which allows the machine to access SMB services. The Workstation service is mandatory. The service is installed by default on both <indexterm id="ch03-idx-948154-0"><primary>Windows NT Workstation 4.0</primary></indexterm>
-<indexterm id="ch03-idx-948155-0"><primary>Windows NT Server 4.0</primary></indexterm>Windows NT Workstation 4.0 and <indexterm id="ch03-idx-948159-0"><primary>TCP/IP networking protocol</primary><secondary>installing</secondary></indexterm>
-<indexterm id="ch03-idx-948159-1"><primary>installing TCP/IP protocol</primary></indexterm>Server 4.0. If it's not there, you can install it much like TCP/IP. In this case you need to press the Add button and then select Workstation Service, as shown in <link linkend="ch03-40000">Figure 3.21</link>.</para>
-
-
-<figure label="3.21" id="ch03-40000">
-<indexterm id="ch03-idx-948115-0" class="endofrange" startref="ch03-idx-948108-0"/><title>Select Network Service dialog box </title>
-
-<graphic width="502" depth="285" fileref="figs/sam.0321.gif"></graphic>
-</figure>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.2.2" id="ch03-85837">
-<title>Configuring TCP/IP</title>
-
-
-<para>
-<indexterm id="ch03-idx-948163-0" class="startofrange"><primary>TCP/IP networking protocol</primary><secondary>configuring</secondary></indexterm>
-<indexterm id="ch03-idx-948163-1" class="startofrange"><primary>configuring TCP/IP networking protocol</primary></indexterm>After you've installed the Workstation service, return to the <indexterm id="ch03-idx-948172-0"><primary>Protocols tab</primary></indexterm>Protocols tab and select the TCP/IP Protocol entry in the window. Then click the Properties button below the window. The Microsoft TCP/IP Protocol panel will be displayed. There are five tabs on the Windows NT panel, and (like Windows 95/98) you will need to work on three of them:</para>
-
-
-<itemizedlist>
-<listitem><para>IP address</para></listitem>
-<listitem><para>DNS</para></listitem>
-<listitem><para>WINS address</para></listitem>
-</itemizedlist>
-
-<sect3 role="" label="3.2.2.1" id="ch03-SECT-2.2.1">
-<title>IP Address tab</title>
-
-
-<para>
-<indexterm id="ch03-idx-948191-0"><primary>IP Address tab</primary><secondary>Windows NT</secondary></indexterm>The IP Address tab is shown in <link linkend="ch03-97098">Figure 3.22</link>.</para>
-
-
-<figure label="3.22" id="ch03-97098">
-<title>Microsoft TCP/IP Properties for Windows NT</title>
-
-<graphic width="502" depth="380" fileref="figs/sam.0322.gif"></graphic>
-</figure>
-
-<para>
-<indexterm id="ch03-idx-948212-0"><primary>Windows NT</primary><secondary>IP address, setting</secondary></indexterm>
-<indexterm id="ch03-idx-948212-1"><primary>IP address</primary><secondary>setting for Windows NT computers</secondary></indexterm>Select the "Specify an IP address" radio button and enter the computer's address and <indexterm id="ch03-idx-948231-0"><primary>subnets</primary><secondary>mask</secondary></indexterm>
-<indexterm id="ch03-idx-948231-1"><primary>masks</primary><secondary>subnet</secondary></indexterm>subnet mask in the space provided for the proper adapter (Ethernet card). You or your network manager should have selected an address for the client on the same subnet (LAN) as the Samba server. For example, if the server's address is 192.168.236.86 and its network mask 255.255.255.0, you might use the address 192.168.236.10, if it is available, for the NT workstation, along with the same <indexterm id="ch03-idx-948235-0"><primary>netmasks</primary></indexterm>netmask. If you use <indexterm id="ch03-idx-948242-0"><primary>DHCP (Dynamic Host Configuration Protocol)</primary></indexterm>DHCP on your network, select the "Obtain an IP Address from a DHCP server" button.</para>
-
-
-<tip role="ora">
-<para>If you don't have an IP address to use, and you are on a network by yourself, steal ours, as the 192.168.<emphasis>x.x</emphasis> subnet is specifically reserved by the Internic for LANs. If you're not by yourself, see your system administrator for some available addresses on your network.</para>
-
-</tip>
-
-<para>The<indexterm id="ch03-idx-948244-0"><primary>gateway field</primary></indexterm> gateway field refers to a machine typically known as a <emphasis>router</emphasis>
-<indexterm id="ch03-idx-948243-0"><primary>routers, TCP/IP configuring and</primary></indexterm>. If you have routers connecting multiple networks, you should put in the IP address of the one on your subnet.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.2.2.2" id="ch03-SECT-2.2.2">
-<title>DNS tab</title>
-
-
-<para>
-<indexterm id="ch03-idx-948199-0"><primary>DNS (Domain Name System)</primary><secondary>tab</secondary></indexterm>Next we go to the tab for DNS, as shown in <link linkend="ch03-61878">Figure 3.23</link>. This brings up the DNS panel.</para>
-
-
-<figure label="3.23" id="ch03-61878">
-<title>The DNS panel</title>
-
-<graphic width="502" depth="407" fileref="figs/sam.0323.gif"></graphic>
-</figure>
-
-<para>The <indexterm id="ch03-idx-948248-0"><primary>DNS (Domain Name System)</primary><secondary>configuring</secondary></indexterm>
-<indexterm id="ch03-idx-948248-1"><primary>configuring DNS (Windows NT)</primary></indexterm>Domain Name System (DNS) is responsible for translating human-readable computer names such as <emphasis>atrish.example.com</emphasis> into IP addresses such as 192.168.236.10. There are two ways to accomplish this on a NT machine. First, you can specify a DNS server to do the translation for you, or you can keep a local list of name/address pairs for your workstation to refer to.</para>
-
-
-<para>For a LAN that's not on the Internet, the list of possible hosts is typically small and well known, and may be kept in a file locally. Networks that are connected to the Internet typically use DNS service since it isn't possible to guess ahead of time what addresses you might be accessing out on the net. If you are in doubt as to whether a DNS server is being used, or what its address might be, look at the file <emphasis>/etc/resolv.conf</emphasis> on your Samba server: any machine using DNS will have this file. It looks like the following:</para>
-
-
-<programlisting>#resolv.conf
-domain example.com
-nameserver 127.0.0.1
-nameserver 192.168.236.20</programlisting>
-
-
-<para>In this example, the first nameserver in the list is 127.0.0.1, which indicates that the Samba server is also a DNS server for this LAN.<footnote label="3" id="ch03-pgfId-946587">
-
-
-<para>The address 127.0.0.1 is known as the <emphasis>localhost</emphasis>
-<indexterm id="ch03-idx-948263-0"><primary>localhost</primary><secondary>address</secondary></indexterm> address, and always refers to itself. For example, if you type <literal>ping 127.0.0.1</literal> on a Unix server, you should always get a response, as you're pinging the host itself.</para>
-
-
-</footnote> In that case, you would use its network IP address (not 127.0.0.1, its localhost address) when filling in the DNS Configuration dialog box. Otherwise, use the other addresses you find in the lines beginning with <literal>nameserver</literal>. Try to select ones on your own network. Any name servers listed in <emphasis>/etc/resolv.conf</emphasis> should work, but you'll get better performance by using a server nearby.</para>
-
-
-<para>Finally, enter the machine name once more, making sure that it's the same one listed in the Identification tab of the Network dialog box (before the NetBIOS name). Also, enter the DNS domain on which this machine resides. For example, if your workstation has a domain name such as <emphasis>example.com</emphasis>, enter it here. You can safely ignore the other options.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.2.2.3" id="ch03-SECT-2.2.3">
-<title>WINS Address tab</title>
-
-
-<para>
-<indexterm id="ch03-idx-948207-0"><primary>WINS Address tab (Windows NT panel)</primary></indexterm>
-<indexterm id="ch03-idx-948207-1"><primary>WINS (Windows Internet Name Service)</primary><secondary>address, configuring</secondary></indexterm>
-<indexterm id="ch03-idx-948207-2"><primary>configuring WINS address</primary></indexterm>If you are not using a DNS server, you still need a way of translating NetBIOS names to addresses and back again. We recommend that you configure both DNS and WINS; <indexterm id="ch03-idx-948268-0"><primary>Windows NT</primary><secondary>WINS address and</secondary></indexterm>NT has a preference for WINS and WINS can use DNS as a fallback if it cannot resolve any machine address. The WINS Address tab is shown in <link linkend="ch03-20855">Figure 3.24</link>.</para>
-
-
-<figure label="3.24" id="ch03-20855">
-<title>The WINS Address tab</title>
-
-<graphic width="502" depth="342" fileref="figs/sam.0324.gif"></graphic>
-</figure>
-
-<para>If you have a WINS server, enter its address in the space marked Primary WINS Server. If your Samba server is providing WINS service (in other words, you have the line <literal>wins</literal> <literal>service</literal> <literal>=</literal> <literal>yes</literal> in the <emphasis>smb.conf</emphasis> file of your Samba server), provide the Samba server's IP address here. Otherwise, provide the address of another WINS server on your network.</para>
-
-
-<para>You probably noticed that there is a field here for the adaptor; this field must specify the <indexterm id="ch03-idx-948269-0"><primary>Ethernet adaptor cards</primary></indexterm>Ethernet adaptor that you're running TCP/IP on so that WINS will provide name service on the correct network. If you have both a LAN and a dialup adaptor, make sure you have the LAN's adaptor here.</para>
-
-
-<para>Finally, select the "Enable DNS for Windows Resolution" checkbox, so WINS will try <indexterm id="ch03-idx-948270-0"><primary>DNS (Domain Name System)</primary><secondary sortas="fallback for WINS address">as fallback for WINS address</secondary></indexterm>DNS as a fallback if it can't find a name. You can safely ignore the other options.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.2.2.4" id="ch03-SECT-2.2.4">
-<title>Hosts files</title>
-
-
-<para>
-<indexterm id="ch03-idx-948271-0"><primary>hosts</primary><secondary>files (Windows NT computers)</secondary></indexterm>If you don't have either DNS or WINS, and you don't wish to use broadcast name resolution, you'll need to provide a table of IP addresses and hosts names, in standard Unix <filename>/etc/hosts</filename> format. We recommend against this because maintenance of this file on any dynamic network is troublesome, but we will explain it just the same. The Windows host file should appear in the <emphasis>\WINDOWS\HOSTS</emphasis>
-<indexterm id="ch03-idx-948273-0"><primary sortas="WINDOWS\HOSTS directory">\WINDOWS\HOSTS directory</primary></indexterm> directory of whatever local drive Windows is installed on. A sample follows:</para>
-
-
-<programlisting>127.0.0.1 localhost
-192.168.236.1 escrime escrime.example.com
-192.168.236.2 riposte riposte.example.com
-192.168.236.3 wizzin wizzin.example.com
-192.168.236.4 touche touche.example.com
-192.168.236.5 gurgi gurgi.example.com
-192.168.236.6 jessiac jessiac.example.com
-192.168.236.7 skyline skyline.example.com</programlisting>
-
-
-<para>If you wish, you can copy the contents directly from the Samba server's<filename> /etc/hosts</filename>. The format is identical. This file will then serve the same purpose as the hosts file on the Unix server. Again, <emphasis>hosts</emphasis> files on Windows should only be used as a last resort.</para>
-</sect3>
-
-
-
-<sect3 role="" label="3.2.2.5" id="ch03-SECT-2.2.5">
-<title>Bindings</title>
-
-
-<para>The term <firstterm>bindings</firstterm>
-<indexterm id="ch03-idx-948274-0"><primary>bindings</primary></indexterm>
-<indexterm id="ch03-idx-948274-1"><primary>service bindings</primary></indexterm> is a way of saying "connected together at configuration time." It means that the TCP/IP protocol will channel through the Ethernet card (instead of, say, a dialup connection), and is actually connected properly. If you return to the Network dialog box and set the Show field to "all services" and click on all the + buttons in the tree, you should see a display similar to <link linkend="ch03-83060">Figure 3.25</link>.</para>
-
-
-<figure label="3.25" id="ch03-83060">
-<title>Service bindings</title>
-
-<graphic width="502" depth="332" fileref="figs/sam.0325.gif"></graphic>
-</figure>
-
-<para>This means that the Workstation, Server, and NetBIOS interface services are connected to the WINS client. This is the correct binding for Microsoft TCP/IP.<indexterm id="ch03-idx-948166-0" class="endofrange" startref="ch03-idx-948163-0"/>
-<indexterm id="ch03-idx-948166-1" class="endofrange" startref="ch03-idx-948163-1"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.2.3" id="ch03-SECT-2.3">
-<title>Connecting to the Samba Server</title>
-
-
-<para>
-<indexterm id="ch03-idx-948286-0"><primary>Samba server</primary><secondary>connecting to</secondary></indexterm>You can safely leave the default values for the remainder of the tabs in the Network dialog box. Click on the OK button to complete the configuration. Once the proper files are loaded (if any), you will need to reboot in order for your changes to take effect.</para>
-
-
-<para>Now for the big moment. Your Samba server is running and you have set up your NT client to communicate with it. After the machine reboots, login and double-click the <indexterm id="ch03-idx-948283-0"><primary>Network Neighborhood icon</primary><secondary>viewing Samba server</secondary></indexterm>
-<indexterm id="ch03-idx-948283-1"><primary>Samba server</primary><secondary>viewing via Network Neighborhood icon</secondary></indexterm>Network Neighborhood icon on the desktop, and you should see your Samba server listed as a member of the workgroup, as shown in <link linkend="ch03-50785">Figure 3.26</link>.</para>
-
-
-<figure label="3.26" id="ch03-50785">
-<title>Windows NT Network Neighborhood</title>
-
-<graphic width="502" depth="163" fileref="figs/sam.0326.gif"></graphic>
-</figure>
-
-<para>
-<indexterm id="ch03-idx-949153-0"><primary>Samba server</primary><secondary>resources offered</secondary></indexterm>Double-clicking the server name will show the resources that the server is offering to the network, as shown in <link linkend="ch03-89532">Figure 3.27</link>. In this case, the test and the default printer are offered to the Window NT workstation. For more information, see the warning under <link linkend="ch03-13238">Section 3.1.4</link> earlier in this chapter.</para>
-
-
-<figure label="3.27" id="ch03-89532">
-<title>Server's shares</title>
-
-<graphic width="502" depth="152" fileref="figs/sam.0327.gif"></graphic>
-</figure>
-
-<warning role="ora">
-<para>If you are presented with a dialog requesting the password for a user <literal>IPC$</literal>, then Samba did not accept the password that was sent from the client. In this case, the username and the password that were created on the client side <emphasis>must</emphasis> match the username/password combination on the Samba server. If you are using Windows 98 or Windows NT Service Pack 3 or above, this is probably because the client is sending encrypted passwords instead of plaintext passwords. You can remedy this situation by performing two steps on the Samba server. First, add the following entry to the <literal>[global]</literal> section of your Samba configuration file: <literal>encrypt password=yes</literal>. Second, find the <filename>smbpasswd</filename> program on the samba server (it is located in <filename>/usr/local/samba/bin</filename> by default) and use it to add an entry to Samba's encrypted password database. For example, to add user <literal>steve</literal> to Samba's encrypted password database, type <replaceable>smbpasswd -a steve</replaceable>. The first time you enter this password, the program will output an error message indicating that the password database does not exist; it will then create the database, which is typically stored in <filename>/usr/local/samba/private/smbpasswd</filename>.</para>
-
-</warning>
-
-<para>If you don't see the server listed, don't panic. Start the Windows NT Explorer (not Internet Explorer!) and select Map Network Drive from the Tools menu. A dialog box appears that allows you to type the name of your server and its share directory in Windows format. For example, you would enter <filename>\\</filename><replaceable>server</replaceable><filename>\temp</filename> if your server happened to be named "server." If things still aren't right, go directly to <link linkend="ch09-29538">Section 9.2</link> in <link linkend="SAMBA-CH-9">Chapter 9</link>, to see if you can troubleshoot what is wrong with the network.</para>
-
-
-<para>If it works, congratulations! Try writing to the server and sending data to the network printer. You will be pleasantly surprised how seamlessly everything works! Now that you've finished setting up the Samba server and its clients, we can starting talking about how Samba works and how to configure it to your liking. <indexterm id="ch03-idx-947946-0" class="endofrange" startref="ch03-idx-947940-0"/>
-<indexterm id="ch03-idx-947946-1" class="endofrange" startref="ch03-idx-947940-1"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="3.3" id="ch03-64069">
-<title>An Introduction to SMB/CIFS</title>
-
-
-<para>
-<indexterm id="ch03-idx-948288-0" class="startofrange"><primary>SMB (Server Message Block)</primary></indexterm>We'll wrap up this chapter with a short tutorial on SMB/CIFS. SMB/CIFS is the protocol that Windows 95/98 and NT machines use to communicate with the Samba server and each other. At a high level, the SMB protocol suite is relatively simple. It includes commands for all of the file and print operations that you might do on a local disk or printer, such as:</para>
-
-
-<itemizedlist>
-<listitem><para> Opening and closing a file</para></listitem>
-<listitem><para> Creating and deleting files and directories</para></listitem>
-<listitem><para> Reading and writing a file</para></listitem>
-<listitem><para> Searching for files</para></listitem>
-<listitem><para> Queueing and dequeueing files to a print spool</para></listitem>
-</itemizedlist>
-
-<para>Each of these operations can be encoded into an SMB message and transmitted to and from a server. The original name SMB comes from their data format: these are versions of the standard DOS system-call data structures, or <firstterm>Server Message Blocks</firstterm>, redesigned for transmitting to another machine across a network.</para>
-
-
-<sect2 role="" label="3.3.1" id="ch03-SECT-3.1">
-<title>SMB Format</title>
-
-
-<para>
-<indexterm id="ch03-idx-948317-0"><primary>SMB (Server Message Block)</primary><secondary>format of</secondary></indexterm>Richard <indexterm id="ch03-idx-948318-0"><primary>Sharpe, Richard</primary></indexterm>Sharpe of the Samba team defines SMB as a "request-response" protocol.<footnote label="4" id="ch03-pgfId-942928">
-
-
-<para>See <systemitem role="url">http://anu.samba.org/cifs/docs/what-is-smb.html</systemitem> for Richard's excellent summary of SMB.</para>
-
-
-</footnote> In effect, this means that a client sends an SMB request to a server, and the server sends an <indexterm id="ch03-idx-948320-0"><primary>SMB (Server Message Block)</primary><secondary>resources for further information</secondary></indexterm>
-<indexterm id="ch03-idx-948320-1"><primary>URLs (uniform resource locators)</primary><secondary>SMB (Server Message Block)</secondary></indexterm>SMB response back to the client. Rarely does a server send a message that is not in response to a client.</para>
-
-
-<para>An SMB message is not as complex as you might think. Let's take a closer look at the internal structure of such a message. It can be broken down into two parts: the <firstterm>header</firstterm>
-<indexterm id="ch03-idx-948321-0"><primary>header, SMB</primary></indexterm>, which is a fixed size, and the <firstterm>command string</firstterm>, whose size can vary dramatically based on the contents of the message.</para>
-
-
-<sect3 role="" label="3.3.1.1" id="ch03-SECT-3.1.1">
-<title>SMB header format</title>
-
-
-<para><link linkend="ch03-31015">Table 3.1</link> shows the format of an SMB header. SMB commands are not required to use all the fields in the SMB header. For example, when a client first attempts to connect to a server, it does not yet have a <indexterm id="ch03-idx-948332-0"><primary>tree identifier (TID)</primary></indexterm>
-<indexterm id="ch03-idx-948332-1"><primary>TID (tree identifier)</primary></indexterm>tree identifier (TID) value—one is assigned after it successfully connects—so a <indexterm id="ch03-idx-948333-0"><primary>null TID</primary></indexterm>null TID (0xFFFF) is placed in its header field. Other fields may be padded with zeros when not used.</para>
-
-
-<para>The fields of the SMB header are listed in <link linkend="ch03-31015">Table 3.1</link>.</para>
-
-
-<table label="3.1" id="ch03-31015">
-<title>SMB Header Fields </title>
-
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Field</para></entry>
-
-<entry colname="col2"><para>Size (bytes)</para></entry>
-
-<entry colname="col3"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>0xFF 'SMB'</literal></para></entry>
-
-<entry colname="col2"><para><literal>1</literal></para></entry>
-
-<entry colname="col3"><para>
-<indexterm id="ch03-idx-948337-0"><primary>SMB (Server Message Block)</primary><secondary>header</secondary></indexterm>Protocol identifier</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>COM</literal></para></entry>
-
-<entry colname="col2"><para><literal>1</literal></para></entry>
-
-<entry colname="col3"><para>Command code, from 0x00 to 0xFF</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>RCLS</literal></para></entry>
-
-<entry colname="col2"><para><literal>1</literal></para></entry>
-
-<entry colname="col3"><para>Error class</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>REH</literal></para></entry>
-
-<entry colname="col2"><para><literal>1</literal></para></entry>
-
-<entry colname="col3"><para>Reserved</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ERR</literal></para></entry>
-
-<entry colname="col2"><para><literal>2</literal></para></entry>
-
-<entry colname="col3"><para>Error code</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>REB</literal></para></entry>
-
-<entry colname="col2"><para><literal>1</literal></para></entry>
-
-<entry colname="col3"><para>Reserved</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>RES</literal></para></entry>
-
-<entry colname="col2"><para><literal>14</literal></para></entry>
-
-<entry colname="col3"><para>Reserved</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>TID</literal></para></entry>
-
-<entry colname="col2"><para><literal>2</literal></para></entry>
-
-<entry colname="col3"><para>Tree identifier; a unique ID for a resource in use by client</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>PID</literal></para></entry>
-
-<entry colname="col2"><para><literal>2</literal></para></entry>
-
-<entry colname="col3"><para>Caller process ID</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>UID</literal></para></entry>
-
-<entry colname="col2"><para><literal>2</literal></para></entry>
-
-<entry colname="col3"><para>User identifier</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>MID</literal></para></entry>
-
-<entry colname="col2"><para><literal>2</literal></para></entry>
-
-<entry colname="col3"><para>Multiplex identifier; used to route requests inside a process</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect3>
-
-
-
-<sect3 role="" label="3.3.1.2" id="ch03-SECT-3.1.2">
-<title>SMB command format</title>
-
-
-<para><firstterm></firstterm>
-<indexterm id="ch03-idx-948328-0"><primary>command string, SMB</primary></indexterm>Immediately after the header is a variable number of bytes that constitute an SMB command or reply. Each command, such as Open File (COM field identifier: <literal>SMBopen</literal>) or Get Print Queue (<literal>SMBsplretq </literal>), has its own set of parameters and data. Like the SMB header fields, not all of the command fields need to be filled, depending on the specific command. For example, the Get Server Attributes (<literal>SMBdskattr</literal>) command sets the WCT and BCC fields to zero. The fields of the command segment are shown in <link linkend="ch03-38178">Table 3.2</link>.</para>
-
-
-<table label="3.2" id="ch03-38178">
-<title>SMB Command Contents </title>
-
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Field</para></entry>
-
-<entry colname="col2"><para>Size in Bytes</para></entry>
-
-<entry colname="col3"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>WCT</literal></para></entry>
-
-<entry colname="col2"><para><literal>1</literal></para></entry>
-
-<entry colname="col3"><para><firstterm></firstterm>
-<indexterm id="ch03-idx-948340-0"><primary>SMB (Server Message Block)</primary><secondary>command string</secondary></indexterm>Word count</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>VWV</literal></para></entry>
-
-<entry colname="col2"><para>Variable</para></entry>
-
-<entry colname="col3"><para>Parameter words (size given by WCT)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>BCC</literal></para></entry>
-
-<entry colname="col2"><para><literal>2</literal></para></entry>
-
-<entry colname="col3"><para>Parameter byte count</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>DATA</literal></para></entry>
-
-<entry colname="col2"><para>Variable</para></entry>
-
-<entry colname="col3"><para>Data (size given by BCC)</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Don't worry if you don't understand each of these fields; they are not necessary for using Samba at an administrator level. However, they do come in handy when debugging system messages. We will show you some of the more common SMB messages that clients and servers send using a modified version of <filename>tcpdump</filename> later in this section. (If you would like an SMB sniffer with a graphical interface, try "ethereal," which uses the GTK libraries; see the Samba homepage for more information on this tool.)</para>
-
-
-<tip id="ch03-resources-for-further-information" role="ora">
-<para>If you would like more information on each of the commands for the SMB protocol, see the SMB/CIFS documentation at <systemitem role="ftpurl">ftp://ftp.microsoft.com/developr/drg/CIFS/</systemitem>.</para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="3.3.1.3" id="ch03-SECT-3.1.3">
-<title>SMB variations</title>
-
-
-<para>The SMB protocol has been extended with new commands several times since its inception. Each new version is backwards compatible with the previous versions. This makes it quite possible for a LAN to have various clients and servers running different versions of the SMB protocol at once.</para>
-
-
-<para><link linkend="ch03-67366">Table 3.3</link> outlines the major versions of the SMB protocol. Within each "dialect" of SMB are many sub-versions that include commands supporting particular releases of major operating systems. The ID string is used by clients and servers to determine what level of the protocol they will speak to each other.</para>
-
-
-<table label="3.3" id="ch03-67366">
-<title>SMB Protocol Dialects </title>
-
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Protocol Name</para></entry>
-
-<entry colname="col2"><para>ID String</para></entry>
-
-<entry colname="col3"><para>Used By</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>Core</para></entry>
-
-<entry colname="col2"><para><literal>PC NETWORK PROGRAM 1.0</literal></para></entry>
-
-<entry colname="col3"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Core Plus</para></entry>
-
-<entry colname="col2"><para><literal>MICROSOFT NETWORKS 1.03 </literal></para></entry>
-
-<entry colname="col3"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>LAN Manager 1.0</para></entry>
-
-<entry colname="col2"><para><literal>LANMAN1.0</literal></para></entry>
-
-<entry colname="col3"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>LAN Manager 2.0</para></entry>
-
-<entry colname="col2"><para><literal>LM1.2X002</literal></para></entry>
-
-<entry colname="col3"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>LAN Manager 2.1</para></entry>
-
-<entry colname="col2"><para><literal>LANMAN2.1</literal></para></entry>
-
-<entry colname="col3"></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>NT LAN Manager 1.0</para></entry>
-
-<entry colname="col2"><para><literal>NT LM 0.12</literal></para></entry>
-
-<entry colname="col3"><para>Windows NT 4.0</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Samba's NT LM 0.12</para></entry>
-
-<entry colname="col2"><para><literal>Samba</literal></para></entry>
-
-<entry colname="col3"><para>Samba</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Common Internet File System</para></entry>
-
-<entry colname="col2"><para><literal>CIFS 1.0</literal></para></entry>
-
-<entry colname="col3"><para>Windows 2000</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Samba implements the <literal>NT</literal> <literal>LM</literal> <literal>0.12</literal> specification for NT LAN Manager 1.0. It is backwards compatible with all of the other SMB variants. The CIFS specification is, in reality, LAN Manager 0.12 with a few specific additions.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.3.2" id="ch03-SECT-3.2">
-<title>SMB Clients and Servers</title>
-
-
-<para>As mentioned earlier, SMB is a client/server protocol. In the purest sense, this means that a client sends a request to a server, which acts on the request and returns a reply. However, the client/server roles can often be reversed, sometimes within the context of a single SMB session. For example, consider the two Windows 95/98 computers in <link linkend="ch03-69480">Figure 3.28</link>. The computer named WIZZIN shares a printer to the network, and the computer named ESCRIME shares a disk directory. WIZZIN is in the client role when accessing ESCRIME's network drive, and in the server role when printing a job for ESCRIME.</para>
-
-
-<figure label="3.28" id="ch03-69480">
-<title>Two computers that both have resources to share</title>
-
-<graphic width="502" depth="153" fileref="figs/sam.0328.gif"></graphic>
-</figure>
-
-<para>This brings out an important point in Samba terminology:</para>
-
-
-<itemizedlist>
-<listitem><para>A <firstterm>server</firstterm> is a machine with a resource to share.</para></listitem>
-<listitem><para>A <firstterm>client</firstterm> is a machine that wishes to use that resource.</para></listitem>
-<listitem><para>A server can be a client (of another computer's resource) at any given time.</para></listitem>
-</itemizedlist>
-
-<para>Note that there are no implications as to the amount of resources that make up a server, or whether it has a large disk space or fast processor. A server could be an old 486 with a printer attached to it, or it could be an UltraSparc station with a 10 gigabyte disk service.</para>
-
-
-<para>Microsoft Windows products have both the SMB client and server built in to the operating system. <indexterm id="ch03-idx-948356-0"><primary>Windows NT</primary><secondary>client/server and</secondary></indexterm>Wndows NT 4.0 uses a newer SMB protocol than Windows for Workgroups, and it offers an enhanced form of network security which will be discussed in <link linkend="SAMBA-CH-6">Chapter 6</link>. In addition, there are a large number of commercial <indexterm id="ch03-idx-948361-0"><primary>SMB (Server Message Block)</primary><secondary>commercial products for</secondary></indexterm>SMB server products available from companies such as Sun, Compaq, SCO, Hewlett-Packard, Syntax, and IBM. Unfortunately, on the client side there are far fewer offerings, limited mainly to Digital Equipment's Pathworks product, and of course, Samba.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.3.3" id="ch03-SECT-3.3">
-<title>A Simple SMB Connection</title>
-
-
-<para>
-<indexterm id="ch03-idx-948363-0"><primary>SMB (Server Message Block)</primary><secondary>making a simple connection</secondary></indexterm>
-<indexterm id="ch03-idx-948363-1"><primary>connections</primary><secondary>SMB</secondary></indexterm>Before we close this chapter, let's take a look at a simple SMB connection. This is some pretty technical data—which isn't really necessary to administer Samba—so you can skip over it if you like. We present this information largely as a way to help you get familiar with how the SMB protocol negotiates connections with other computers on the network.</para>
-
-
-<para>There are four steps that the client and server must complete in order to establish a connection to a resource:</para>
-
-
-<orderedlist>
-<listitem><para> Establish a virtual connection.</para></listitem>
-<listitem><para> Negotiate the protocol variant to speak.</para></listitem>
-<listitem><para> Set session parameters.</para></listitem>
-<listitem><para> Make a tree connection to a resource.</para></listitem>
-</orderedlist>
-
-<para>We will examine each of these steps through the eyes of a useful tool that we mentioned earlier: the modified <filename>tcpdump</filename>
-<indexterm id="ch03-idx-948362-0"><primary>tcpdump utility</primary></indexterm>
-<indexterm id="ch03-idx-948362-1"><primary>downloads</primary><secondary>tcpdump utility</secondary></indexterm> that is available from the Samba web site.</para>
-
-
-<tip role="ora">
-<para>You can download this program at <filename>samba.org</filename> in the <filename>samba/ftp/tcpdump-smb</filename> directory; the latest version as of this writing is 3.4-5. Use this program as you would use the standard <filename>tcpdump</filename> application, but add the <literal>-s 1500</literal> switch to ensure that you get the whole packet and not just the first few bytes.</para>
-
-</tip>
-
-<sect3 role="" label="3.3.3.1" id="ch03-SECT-3.3.1">
-<title>Establishing a virtual connection</title>
-
-
-<para>
-<indexterm id="ch03-idx-948365-0"><primary>connections</primary><secondary>virtual</secondary></indexterm>
-<indexterm id="ch03-idx-948365-1"><primary>virtual connection</primary></indexterm>When a user first makes a request to access a network disk or send a print job to a remote printer, NetBIOS takes care of making a connection at the <indexterm id="ch03-idx-948366-0"><primary>session layer, connection at</primary></indexterm>session layer. The result is a bidirectional virtual channel between the client and server. In reality, there are only two messages that the client and server need to establish this connection. This is shown in the following example session request and response, as captured by <filename>tcpdump</filename> :</para>
-
-
-<programlisting>>>> NBT Packet
-NBT Session Request
-Flags=0x81000044
-Destination=ESCRIME NameType=0x20 (Server)
-Source=WIZZIN NameType=0x00 (Workstation)
-
->>> NBT Packet
-NBT Session Granted
-Flags=0x82000000</programlisting>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.3.4" id="ch03-SECT-3.4">
-<title>Negotiating the Protocol Variant</title>
-
-
-<para>
-<indexterm id="ch03-idx-948367-0"><primary>protocols</primary><secondary>variant, negotiating</secondary></indexterm>At this point, there is an open channel between the client and server. Next, the client sends a message to the server to negotiate an SMB protocol. As mentioned earlier, the client sets its <indexterm id="ch03-idx-948373-0"><primary>tree identifier (TID)</primary></indexterm>
-<indexterm id="ch03-idx-948373-1"><primary>TID (tree identifier)</primary></indexterm>tree identifier (TID) field to zero, since it does not yet know what TID to use. A <emphasis>tree identifier</emphasis> is a number that represents a connection to a share on a server.</para>
-
-
-<para>The command in the message is <literal>SMBnegprot</literal>, a request to negotiate a protocol variant that will be used for the entire session. Note that the client sends to the server a list of all of the variants that it can speak, not vice versa.</para>
-
-
-<para>The server responds to the <literal>SMBnegprot</literal> request with an index into the list of variants that the client offered, starting with index 0, or with the value 0xFF if none of the protocol variants are acceptable. Continuing this example, the server responds with the value 5, which indicates that the <literal>NT</literal> <literal>LM</literal> <literal>0.12</literal> dialect will be used for the remainder of the session:</para>
-
-
-<programlisting>>>> NBT Packet
-NBT Session Packet
-Flags=0x0
-Length=154
-
-SMB PACKET: SMBnegprot (REQUEST)
-SMB Command = 0x72
-Error class = 0x0
-Error code = 0
-Flags1 = 0x0
-Flags2 = 0x0
-Tree ID = 0
-Proc ID = 5371
-UID = 0
-MID = 385
-Word Count = 0
-Dialect=PC NETWORK PROGRAM 1.0
-Dialect=MICROSOFT NETWORKS 3.0
-Dialect=DOS LM1.2X002
-Dialect=DOS LANMAN2.1
-Dialect=Windows for Workgroups 3.1a
-Dialect=NT LM 0.12
-
->>> NBT Packet
-NBT Session Packet
-Flags=0x0
-Length=69
-
-SMB PACKET: SMBnegprot (REPLY)
-SMB Command = 0x72
-Error class = 0x0
-Error code = 0
-Flags1 = 0x0
-Flags2 = 0x1
-Tree ID = 0
-Proc ID = 5371
-UID = 0
-MID = 385
-Word Count = 02
-[000] 05 00</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.3.5" id="ch03-SECT-3.5">
-<title>Set Session and Login Parameters</title>
-
-
-<para>
-<indexterm id="ch03-idx-948377-0"><primary>session parameters, setting</primary></indexterm>
-<indexterm id="ch03-idx-948377-1"><primary>login parameters, setting</primary></indexterm>The next step is to transmit session and login parameters for the session. This includes the account name and password (if there is one), the workgroup name, the maximum size of data that can be transferred, and the number of pending requests that may be in the queue at any one time.</para>
-
-
-<para>In the following example, the Session Setup command presented allows for an additional SMB command to be piggybacked onto it. The letter X at the end of the command name indicates this, and the hexadecimal code of the second command is given in the <literal>Com2</literal> field. In this case the command is <literal>0x75</literal>, which is the Tree Connect and X command. The <literal>SMBtconX</literal> message looks for the name of the resource in the <command>smb_buf</command> buffer. (This is the last field listed in the following request.) In this example, <command>smb_buf</command> contains the string <literal>\\ESCRIME\PUBLIC</literal>, which is the full pathname to a shared directory on node ESCRIME. Using the "and X" commands like this speeds up each transaction, since the server doesn't have to wait on the client to make a second request.</para>
-
-
-<para>Note that the <indexterm id="ch03-idx-948382-0"><primary>TID (tree identifier)</primary></indexterm>
-<indexterm id="ch03-idx-948382-1"><primary>tree identifier (TID)</primary></indexterm>TID is still zero. The server will provide a TID to the client once the session has been established and a connection has been made to the requested resource. In addition, note that the password is sent in the open. We can change this later using encrypted passwords:</para>
-
-
-<programlisting>>>> NBT Packet
-NBT Session Packet
-Flags=0x0
-Length=139
-
-SMB PACKET: SMBsesssetupX (REQUEST)
-SMB Command = 0x73
-Error class = 0x0
-Error code = 0
-Flags1 = 0x10
-Flags2 = 0x0
-Tree ID = 0
-Proc ID = 5371
-UID = 1
-MID = 385
-Word Count = 13
-Com2=0x75
-Res1=0x0
-Off2=106
-MaxBuffer=2920
-MaxMpx=2
-VcNumber=0
-SessionKey=0x1FF2
-CaseInsensitivePasswordLength=1
-CaseSensitivePasswordLength=1
-Res=0x0
-Capabilities=0x1
-Pass1&Pass2&Account&Domain&OS&LanMan=
- KRISTIN PARKSTR Windows 4.0 Windows 4.0
-PassLen=2
-Passwd&Path&Device=
-smb_bcc=22
-smb_buf[]=\\ESCRIME\PUBLIC</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="3.3.6" id="ch03-SECT-3.6">
-<title>Making Connection to a Resource</title>
-
-
-<para>
-<indexterm id="ch03-idx-948383-0"><primary>connections</primary><secondary>resources, connecting to</secondary></indexterm>
-<indexterm id="ch03-idx-948383-1"><primary>resources, connecting to</primary></indexterm>For the final step, the server returns a TID to the client, indicating that the user has been authorized access and that the resource is ready to be used. It also sets the <command>ServiceType</command> field to "A" to indicate that this is a file service. Available service types are:</para>
-
-
-<itemizedlist>
-<listitem><para> "A" for a disk or file</para></listitem>
-<listitem><para> "LPT1" for a spooled output</para></listitem>
-<listitem><para> "COMM" for a direct-connect printer or modem</para></listitem>
-<listitem><para> "IPC" for a named pipe</para></listitem>
-</itemizedlist>
-
-<para>The output is:</para>
-
-
-<programlisting>>>> NBT Packet
-NBT Session Packet
-Flags=0x0
-Length=78
-
-SMB PACKET: SMBsesssetupX (REPLY)
-SMB Command = 0x73
-Error class = 0x0
-Error code = 0
-Flags1 = 0x80
-Flags2 = 0x1
-Tree ID = 121
-Proc ID = 5371
-UID = 1
-MID = 385
-Word Count = 3
-Com2=0x75
-Off2=68
-Action=0x1
-[000] Unix Samba 1.9.1
-[010] PARKSTR
-
-SMB PACKET: SMBtconX (REPLY) (CHAINED)
-smbvwv[]=
-Com2=0xFF
-Off2=78
-smbbuf[]=
-ServiceType=A:</programlisting>
-
-
-<para>Now that a TID has been assigned, the client may issue any sort of command that it would use on a local disk drive. It can open files, read and write to them, delete them, create new files, search for filenames, and so<indexterm id="ch03-idx-948291-0" class="endofrange" startref="ch03-idx-948288-0"/> on.<indexterm id="ch03-idx-947921-0" class="endofrange" startref="ch03-idx-947918-0"/>
-<indexterm id="ch03-idx-947921-1" class="endofrange" startref="ch03-idx-947918-1"/></para>
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="4" id="ch04-21486">
-<title>Disk Shares </title>
-
-
-
-
-<para>
-<indexterm id="ch04-idx-967030-0" class="startofrange"><primary>disk shares</primary></indexterm>In the previous three chapters, we showed you how to install Samba on a Unix server and set up Windows clients to use a simple disk share. This chapter will show you how Samba can assume more productive roles on your network.</para>
-
-
-<para>Samba's <indexterm id="ch04-idx-967124-0"><primary>daemons</primary></indexterm>daemons, <emphasis>smbd</emphasis>
-<indexterm id="ch04-idx-967122-0"><primary>smbd daemon</primary></indexterm> and <emphasis>nmbd</emphasis>
-<indexterm id="ch04-idx-967123-0"><primary>nmbd daemon</primary></indexterm>, are controlled through a single ASCII file, <filename>smb.conf</filename>, that can contain over 200 unique options. These options define how Samba reacts to the network around it, including everything from simple permissions to encrypted connections and NT domains. The next five chapters are designed to help you get familiar with this file and its options. Some of these options you will use and change frequently; others you may never use—it all depends on how much functionality you want Samba to offer its clients.</para>
-
-
-<para>This chapter introduces the structure of the Samba configuration file and shows you how to use these options to create and modify disk shares. Subsequent chapters will discuss browsing, how to configure users, security, domains, and printers, and a host of other myriad topics that you can implement with Samba on your network.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.1" id="ch04-76968">
-<title>Learning the Samba Configuration File</title>
-
-
-<para><filename></filename>
-<indexterm id="ch04-idx-968372-0" class="startofrange"><primary>smb.conf (Samba configuration) file</primary></indexterm>Here is an <filename></filename>
-<indexterm id="ch04-idx-968374-0"><primary>smb.conf (Samba configuration) file</primary><secondary>example of</secondary></indexterm>example of a Samba configuration file. If you have worked with a Windows .INI file, the structure of the <filename>smb.conf </filename> file should look very familiar:</para>
-
-
-<programlisting>[global]
- log level = 1
- max log size = 1000
- socket options = TCP_NODELAY IPTOS_LOWDELAY
- guest ok = no
-[homes]
- browseable = no
- map archive = yes
-[printers]
- path = /usr/tmp
- guest ok = yes
- printable = yes
-[test]
- browseable = yes
- read only = yes
- guest ok = yes
- path = /export/samba/test</programlisting>
-
-
-<para>Although you may not understand the contents yet, this is a good configuration file to grab if you're in a hurry. (If you're not, we'll create a new one from scratch shortly.) In a nutshell, this configuration file sets up basic debug logging in a default log file not to exceed 1MB, optimizes TCP/IP socket connections between the Samba server and any SMB clients, and allows Samba to create a disk share for each user that has a standard Unix account on the server. In addition, each of the printers registered on the server will be publicly available, as will a single read-only share that maps to the <filename>/export/samba/test</filename> directory. The last part of this file is similar to the disk share you used to test Samba in <link linkend="SAMBA-CH-2">Chapter 2</link>.</para>
-
-
-<sect2 role="" label="4.1.1" id="ch04-52415">
-<title>Configuration File Structure</title>
-
-
-<para><filename></filename>
-<indexterm id="ch04-idx-967054-0" class="startofrange"><primary>smb.conf (Samba configuration) file</primary><secondary>structure of</secondary></indexterm>Let's take another look at this configuration file, this time from a higher level:</para>
-
-
-<programlisting>[global]
- ...
-[homes]
- ...
-[printers]
- ...
-[test]
- ...</programlisting>
-
-
-<para>The names inside the <indexterm id="ch04-idx-967103-0"><primary>square brackets</primary></indexterm>square brackets delineate unique sections of the <filename>smb.conf</filename> file; each <indexterm id="ch04-idx-967104-0"><primary>sections of smb.conf (Samba configuration) file</primary></indexterm>section names the <firstterm>share</firstterm>
-<indexterm id="ch04-idx-967105-0"><primary>shares</primary></indexterm> (or <indexterm id="ch04-idx-967106-0"><primary>services</primary></indexterm>service) that the section refers to. For example, the <literal>[test]</literal> and <literal>[homes]</literal> sections are each unique disk shares; they contain options that map to specific directories on the Samba server. The <literal>[printers]</literal> share contains options that map to various printers on the server. All the sections defined in the <filename>smb.conf</filename> file, with the exception of the <literal>[global]</literal> section, will be available as a disk or printer share to clients connecting to the Samba server.</para>
-
-
-<para>The remaining lines are individual configuration options unique to that share. These options will continue until a new bracketed section is encountered, or until the end of the file is reached. Each <indexterm id="ch04-idx-967107-0"><primary>configuration options</primary><secondary>format of</secondary></indexterm>
-<indexterm id="ch04-idx-967107-1"><primary>smb.conf (Samba configuration) file</primary><secondary>options for</secondary><tertiary>format of</tertiary></indexterm>configuration option follows a simple format:</para>
-
-
-<programlisting><replaceable>option</replaceable> = <replaceable>value</replaceable></programlisting>
-
-
-<para>Options in the <filename>smb.conf</filename> file are set by assigning a value to them. We should warn you up front that some of the <indexterm id="ch04-idx-967109-0"><primary>option names</primary></indexterm>option names in Samba are poorly chosen. For example, <literal>read</literal> <literal>only</literal> is self-explanatory, and is typical of many recent Samba options. <literal>public</literal> is an older option, and is vague; it now has a less-confusing synonym <literal>guest</literal> <literal>ok</literal> (may be accessed by guests). We describe some of the more common historical names in this chapter in sections that highlight each major task. In addition, <link linkend="SAMBA-AP-C">Appendix C</link>, contains an alphabetical index of all the configuration options and their meanings.</para>
-
-
-<sect3 role="" label="4.1.1.1" id="ch04-SECT-1.1.1">
-<title>Whitespaces, quotes, and commas</title>
-
-
-<para>An important item to remember about configuration options is that all <indexterm id="ch04-idx-967110-0"><primary>whitespaces in values</primary></indexterm>whitespaces in the <replaceable>value</replaceable> are significant. For example, consider the following option:</para>
-
-
-<programlisting>volume = The Big Bad Hard Drive Number 3543</programlisting>
-
-
-<para>Samba strips away the spaces between the final <literal>e</literal> in <literal>volume</literal> and the first <literal>T</literal> in <literal>The</literal>. These whitespaces are insignificant. The rest of the whitespaces are significant and will be recognized and preserved by Samba when reading in the file. Space is not significant in option names (such as <literal>guest</literal> <literal>ok</literal>), but we recommend you follow convention and keep spaces between the words of options.</para>
-
-
-<para>If you feel safer including <indexterm id="ch04-idx-967111-0"><primary>quotation marks in values</primary></indexterm>quotation marks at the beginning and ending of a configuration option's value, you may do so. Samba will ignore these quotation marks when it encounters them. Never use quotation marks around an option itself; Samba will treat this as an error.</para>
-
-
-<para>Finally, you can use whitespaces to separate a series of values in a list, or you can use commas. These two options are equivalent:</para>
-
-
-<programlisting>netbios aliases = sales, accounting, payroll
-netbios aliases = sales accounting payroll</programlisting>
-
-
-<para>In some values, however, you must use one form of separation—<indexterm id="ch04-idx-967367-0"><primary>spaces in values</primary></indexterm>spaces in some cases, <indexterm id="ch04-idx-967112-0"><primary>commas in values</primary></indexterm>commas in others.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.1.1.2" id="ch04-SECT-1.1.2">
-<title>Capitalization</title>
-
-
-<para>
-<indexterm id="ch04-idx-967113-0"><primary>capitalization</primary></indexterm>Capitalization is not important in the Samba configuration file except in locations where it would confuse the underlying operating system. For example, let's assume that you included the following option in a share that pointed to <filename>/export/samba/simple </filename>:</para>
-
-
-<programlisting>PATH = /EXPORT/SAMBA/SIMPLE</programlisting>
-
-
-<para>Samba would have no problem with the <literal>path</literal> configuration option appearing entirely in capital letters. However, when it tries to connect to the given directory, it would be unsuccessful because the Unix filesystem in the underlying operating system <emphasis>is</emphasis> case sensitive. Consequently, the path listed would not be found and clients would be unable to connect to the share.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.1.1.3" id="ch04-SECT-1.1.3">
-<title>Line continuation</title>
-
-
-<para>You can continue a <indexterm id="ch04-idx-967114-0"><primary>line contiinuation</primary></indexterm>line in the Samba configuration file using the <indexterm id="ch04-idx-967115-0"><primary>\ (backslash) in smb.conf file</primary></indexterm>
-<indexterm id="ch04-idx-967115-1"><primary>backslash (\) in smb.conf file</primary></indexterm>backslash, as follows:</para>
-
-
-<programlisting>comment = The first share that has the primary copies \
- of the new Teamworks software product.</programlisting>
-
-
-<para>Because of the backslash, these two lines will be treated as one line by Samba. The second line begins at the first non-whitespace character that Samba encounters; in this case, the <literal>o</literal> in <literal>of</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.1.1.4" id="ch04-SECT-1.1.4">
-<title>Comments</title>
-
-
-<para>You can insert <indexterm id="ch04-idx-967118-0"><primary>comments in smb.conf (Samba configuration) file</primary></indexterm>comments in the <filename>smb.conf</filename> configuration file by preceding a line with either a<indexterm id="ch04-idx-967119-0"><primary>hash mark (#) in comments</primary></indexterm>
-<indexterm id="ch04-idx-967119-1"><primary># (hash mark)</primary></indexterm> hash mark (#) or a<indexterm id="ch04-idx-967120-0"><primary>semicolon (;) in configuration file comments</primary></indexterm>
-<indexterm id="ch04-idx-967120-1"><primary>; (semicolon)</primary></indexterm> semicolon ( ; ). Both characters are equivalent. For example, the first three lines in the following example would be considered comments:</para>
-
-
-<programlisting># This is the printers section. We have given a minimum print
-; space of 2000 to prevent some errors that we've seen when
-; the spooler runs out of space.
-
-[printers]
- public = yes
- min print space = 2000</programlisting>
-
-
-<para>Samba will ignore all comment lines in its configuration file; there are no limitations to what can be placed on a comment line after the initial hash mark or semicolon. Note that the line <indexterm id="ch04-idx-967121-0"><primary>continuation character (\) in comments</primary></indexterm>
-<indexterm id="ch04-idx-967121-1"><primary>\ (continuation character)</primary></indexterm>continuation character (<literal>\</literal>) will <emphasis>not</emphasis> be honored on a commented line. Like the rest of the line, it is ignored.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.1.1.5" id="ch04-SECT-1.1.5">
-<title>Changes at runtime</title>
-
-
-<para>
-<indexterm id="ch04-idx-967126-0"><primary>changes at runtime</primary></indexterm>You can modify the <filename>smb.conf</filename> configuration file and any of its options at any time while the Samba daemons are running. By default, Samba checks the configuration file every 60 seconds for changes. If it finds any, the changes are immediately put into effect. If you don't wish to wait that long, you can force a reload by either sending a <indexterm id="ch04-idx-967127-0"><primary>SIGHUP signal</primary></indexterm>SIGHUP signal to the <emphasis>smbd</emphasis> and <emphasis>nmbd</emphasis> processes, or simply restarting the daemons.</para>
-
-
-<para>For example, if the <emphasis>smbd</emphasis> <indexterm id="ch04-idx-967128-0"><primary>processes</primary><see>daemons</see></indexterm>
-<indexterm id="ch04-idx-967128-1"><primary>daemons</primary><seealso>smbd daemon; nmbd daemon</seealso></indexterm>
-<indexterm id="ch04-idx-967128-2"><primary>nmbd daemon</primary></indexterm>process was 893, you could force it to reread the configuration file with the following command:</para>
-
-
-<programlisting># <emphasis role="bold">kill -SIGHUP 893</emphasis></programlisting>
-
-
-<para>Not all changes will be immediately recognized by clients. For example, changes to a share that is currently in use will not be registered until the client disconnects and reconnects to that share. In addition, server-specific parameters such as the workgroup or NetBIOS name of the server will not register immediately either. This keeps active clients from being suddenly disconnected or encountering unexpected access problems while a session is open.<filename></filename>
-<indexterm id="ch04-idx-967061-0" class="endofrange" startref="ch04-idx-967054-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="4.1.2" id="ch04-87365">
-<title>Variables</title>
-
-
-<para><filename></filename>
-<indexterm id="ch04-idx-967393-0" class="startofrange"><primary>smb.conf (Samba configuration) file</primary><secondary>variables for</secondary></indexterm>
-<indexterm id="ch04-idx-967393-1" class="startofrange"><primary>variables</primary></indexterm>Samba includes a complete set of variables for determining characteristics of the Samba server and the clients to which it connects. Each of these variables begins with a <indexterm id="ch04-idx-967129-0"><primary>percent sign (%) in variables</primary></indexterm>
-<indexterm id="ch04-idx-967129-1"><primary>% (percent sign)</primary></indexterm>percent sign, followed by a single uppercase or lowercase letter, and can be used only on the right side of a configuration option (e.g., after the equal sign):</para>
-
-
-<programlisting>[pub]
- path = /home/ftp/pub/%a</programlisting>
-
-
-<para>The <literal>%a</literal> stands for the client machine's architecture (e.g., <literal>WinNT</literal> for Windows NT, <literal>Win95</literal> for Windows 95 or 98, or <literal>WfWg</literal> for Windows for Workgroups). Because of this, Samba will assign a unique <indexterm id="ch04-idx-967130-0"><primary>paths, architecture-specific</primary></indexterm>path for the <literal>[pub]</literal> share to client machines running Windows NT, a different path for client machines running Windows 95, and another path for Windows for Workgroups. In other words, the paths that each client would see as its share differ according to the client's architecture, as follows:</para>
-
-
-<programlisting>/home/ftp/pub/WinNT
-/home/ftp/pub/Win95
-/home/ftp/pub/WfWg</programlisting>
-
-
-<para>Using variables in this manner comes in handy if you wish to have different users run custom configurations based on their own unique characteristics or conditions. Samba has 19 variables, as shown in <link linkend="ch04-10883">Table 4.1</link>.</para>
-
-
-<table label="4.1" id="ch04-10883">
-<title>Samba Variables </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Variable</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry namest="col1" nameend="col2"><para><emphasis role="bold">
-<indexterm id="ch04-idx-968086-0"><primary>client variables</primary></indexterm>Client variables</emphasis></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%a</literal></para></entry>
-
-<entry colname="col2"><para><filename></filename>
-<indexterm id="ch04-idx-968093-0"><primary>smb.conf (Samba configuration) file</primary><secondary>variables for</secondary><tertiary>list of</tertiary></indexterm>Client's architecture (e.g., Samba, WfWg, WinNT, Win95, or UNKNOWN)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%I</literal></para></entry>
-
-<entry colname="col2"><para>Client's IP address (e.g., 192.168.220.100)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%m</literal></para></entry>
-
-<entry colname="col2"><para>Client's NetBIOS name</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%M</literal></para></entry>
-
-<entry colname="col2"><para>Client's DNS name</para></entry>
-
-</row>
-
-<row>
-
-<entry namest="col1" nameend="col2"><para><emphasis role="bold">
-<indexterm id="ch04-idx-968108-0"><primary>user variables</primary></indexterm>User variables</emphasis></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%g</literal></para></entry>
-
-<entry colname="col2"><para>Primary group of <literal>%u</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%G</literal></para></entry>
-
-<entry colname="col2"><para>Primary group of <literal>%U</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%H</literal></para></entry>
-
-<entry colname="col2"><para>Home directory of <literal>%u</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%u</literal></para></entry>
-
-<entry colname="col2"><para>Current Unix username</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%U</literal></para></entry>
-
-<entry colname="col2"><para>Requested client username (not always used by Samba)</para></entry>
-
-</row>
-
-<row>
-
-<entry namest="col1" nameend="col2"><para><emphasis role="bold">Share variables</emphasis></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%p</literal></para></entry>
-
-<entry colname="col2"><para>Automounter's path to the share's root directory, if different from <literal>%P</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%P</literal></para></entry>
-
-<entry colname="col2"><para>Current share's root directory</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%S</literal></para></entry>
-
-<entry colname="col2"><para>Current share's name</para></entry>
-
-</row>
-
-<row>
-
-<entry namest="col1" nameend="col2"><para><emphasis role="bold">Server variables</emphasis></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%d</literal></para></entry>
-
-<entry colname="col2"><para>Current server process ID</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%h</literal></para></entry>
-
-<entry colname="col2"><para>Samba server's DNS hostname</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%L</literal></para></entry>
-
-<entry colname="col2"><para>Samba server's NetBIOS name</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%N</literal></para></entry>
-
-<entry colname="col2"><para>Home directory server, from the automount map</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%v</literal></para></entry>
-
-<entry colname="col2"><para>Samba version</para></entry>
-
-</row>
-
-<row>
-
-<entry namest="col1" nameend="col2"><para><emphasis role="bold">Miscellaneous variables</emphasis></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%R</literal></para></entry>
-
-<entry colname="col2"><para>The SMB protocol level that was negotiated</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%T</literal></para></entry>
-
-<entry colname="col2"><para>The current date and time</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>
-<indexterm id="ch04-idx-967143-0"><primary>configuration files</primary><secondary>machine-specific</secondary></indexterm>Here's another example of using variables: let's say that there are five clients on your network, but one client, <literal>fred</literal>, requires a slightly different <literal>[homes]</literal> configuration loaded when it connects to the Samba server. With Samba, it's simple to attack such a problem:</para>
-
-
-<programlisting>[homes]
- ...
- include = /usr/local/samba/lib/smb.conf.%m
- ...</programlisting>
-
-
-<para>The <literal>include</literal> option here causes a separate configuration file for each particular NetBIOS machine (<literal>%m</literal>) to be read in addition to the current file. If the hostname of the client machine is <literal>fred</literal>, and if a <filename>smb.conf.fred</filename> file exists in the <replaceable>samba_dir</replaceable><filename>/lib/</filename> directory (or whatever directory you've specified for your configuration files), Samba will insert that configuration file into the default one. If any configuration options are restated in <filename>smb.conf.fred</filename>, those values will override any options previously encountered in that share. Note that we say "previously." If any options are restated in the main configuration file after the <literal>include</literal> option, Samba will honor those restated values for the share in which they are defined.</para>
-
-
-<para>Here's the important part: if there is no such file, Samba will not generate an error. In fact, it won't do anything at all. This allows you to create only one extra configuration file for <literal>fred</literal> when using this strategy, instead of one for each NetBIOS machine that is on the network.</para>
-
-
-<para>Machine-specific configuration files can be used both to customize particular clients and to make debugging Samba easier. Consider the latter; if we have one client with a problem, we can use this approach to give it a private log file with a more verbose logging level. This allows us to see what Samba is doing without slowing down all the other clients or overflowing the disk with useless logs. Remember, with large networks you may not always have the option to restart the Samba server to perform debugging!</para>
-
-
-<para>You can use each of the variables in <link linkend="ch04-10883">Table 4.1</link> to give custom values to a variety of Samba options. We will highlight several of these options as we move through the next few chapters.<filename></filename>
-<indexterm id="ch04-idx-967084-0" class="endofrange" startref="ch04-idx-967393-0"/>
-<indexterm id="ch04-idx-967084-1" class="endofrange" startref="ch04-idx-967393-1"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.2" id="ch04-81402">
-<title>Special Sections</title>
-
-
-<para><filename></filename>
-<indexterm id="ch04-idx-967091-0" class="startofrange"><primary>smb.conf (Samba configuration) file</primary><secondary>special sections of</secondary></indexterm>
-<indexterm id="ch04-idx-967091-1" class="startofrange"><primary>special sections, smb.conf (Samba configuration) file</primary></indexterm>Now that we've gotten our feet wet with variables, there are a few special sections of the Samba configuration file that we should talk about. Again, don't worry if you do not understand each and every configuration options listed below; we'll go over each of them over the course of the upcoming chapters.</para>
-
-
-<sect2 role="" label="4.2.1" id="ch04-SECT-2.1">
-<title>The [globals] Section</title>
-
-
-<para>The <literal>[globals]</literal>
-<indexterm id="ch04-idx-967171-0"><primary sortas="globals section">[globals] section</primary></indexterm>
-<indexterm id="ch04-idx-967171-1"><primary>shares</primary><secondary sortas="globals section">[globals] section</secondary></indexterm> section appears in virtually every Samba configuration file, even though it is not mandatory to define one. Any option set in this section of the file will apply to all the other shares, as if the contents of the section were copied into the share itself. There is one catch: other sections can list the same option in their section with a new value; this has the effect of overriding the value specified in the <literal>[globals]</literal> section.</para>
-
-
-<para>To illustrate this, let's again look at the opening example of the chapter:</para>
-
-
-<programlisting>[global]
- log level = 1
- max log size = 1000
- socket options = TCP_NODELAY IPTOS_LOWDELAY
- guest ok = no
-[homes]
- browseable = no
- map archive = yes
-[printers]
- path = /usr/tmp
- guest ok = yes
- printable = yes
- min print space = 2000
-[test]
- browseable = yes
- read only = yes
- guest ok = yes
- path = /export/samba/test</programlisting>
-
-
-<para>In the previous example, if we were going to connect a client to the <literal>[test]</literal> share, Samba would first read in the <literal>[globals]</literal> section. At that point, it would set the option <literal>guest</literal> <literal>ok</literal> <literal>=</literal> <literal>no</literal> as the global default for each share it encounters throughout the configuration file. This includes the <literal>[homes]</literal> and <literal>[printers]</literal> shares. When it reads in the <literal>[test]</literal> share, however, it would then find the configuration option <literal>guest</literal> <literal>ok</literal> <literal>=</literal> <literal>yes</literal>, and override the default from the <literal>[globals]</literal> section with the value <literal>yes</literal> in the context of the <literal>[pub]</literal> share.</para>
-
-
-<para>Any option that appears outside of a section (before the first marked section) is also assumed to be a global option.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="4.2.2" id="ch04-SECT-2.2">
-<title>The [ homes] Section</title>
-
-
-<para>If a client attempts to connect to a share that doesn't appear in the <filename>smb.conf</filename> file, Samba will search for a <literal>[homes]</literal>
-<indexterm id="ch04-idx-967172-0"><primary sortas="homes share">[homes] share</primary></indexterm> share in the configuration file. If one exists, the unidentified share name is assumed to be a Unix username, which is queried in the password database of the Samba server. If that username appears, Samba assumes the client is a Unix user trying to connect to his or her home directory on the server.</para>
-
-
-<para>For example, assume a client machine is connecting to the Samba server <literal>hydra</literal> for the first time, and tries to connect to a share named [<literal>alice]</literal>. There is no <literal>[alice]</literal> share defined in the <filename>smb.conf</filename> file, but there is a <literal>[homes]</literal>, so Samba searches the password database file and finds an <literal>alice</literal> user account is present on the system. Samba then checks the password provided by the client against user <literal>alice</literal>'s Unix password—either with the password database file if it's using non-encrypted passwords, or Samba's <filename>smbpasswd</filename> file if encrypted passwords are in use. If the passwords match, then Samba knows it has guessed right: the user <literal>alice</literal> is trying to connect to her home directory. Samba will then create a share called <literal>[alice]</literal> for her.</para>
-
-
-<para>The process of using the <literal>[homes]</literal> section to create <indexterm id="ch04-idx-967175-0"><primary>users</primary><secondary>creating</secondary></indexterm>users (and dealing with their passwords) is discussed in more detail in the <link linkend="SAMBA-CH-6">Chapter 6</link>.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="4.2.3" id="ch04-SECT-2.3">
-<title>The [printers] Section</title>
-
-
-<para>The third special section is called <literal>[printers]</literal>
-<indexterm id="ch04-idx-967173-0"><primary>print shares</primary></indexterm> and is similar to <literal>[homes]</literal>. If a client attempts to connect to a share that isn't in the <filename>smb.conf</filename> file, and its name can't be found in the password file, Samba will check to see if it is a printer share. Samba does this by reading the <indexterm id="ch04-idx-967182-0"><primary>printer capabilities file</primary></indexterm>printer capabilities file (usually <filename>/etc/printcap</filename>) to see if the share name appears there.<footnote label="1" id="ch04-pgfId-960558">
-
-
-<para>Depending on your system, this file may not be <emphasis>/etc/printcap</emphasis>. You can use the <emphasis>testparm</emphasis> command that comes with Samba to determine the value of the <literal>printcap</literal> <literal>name</literal> configuration option; this was the default value chosen when Samba was compiled.</para>
-
-
-</footnote> If it does, Samba creates a share named after the printer.</para>
-
-
-<para>Like <literal>[homes]</literal>, this means you don't have to maintain a share for each of your system printers in the <filename>smb.conf</filename> file. Instead, Samba honors the Unix printer registry if you request it to, and provides the registered printers to the client machines. There is, however, an obvious limitation: if you have an account named <literal>fred</literal> and a printer named <literal>fred</literal>, Samba will always find the user account first, even if the client really needed to connect to the printer.</para>
-
-
-<para>The process of setting up the <literal>[printers]</literal>
-<indexterm id="ch04-idx-968220-0"><primary>print shares</primary></indexterm> share is discussed in more detail in <link linkend="SAMBA-CH-7">Chapter 7</link>.<filename></filename>
-<indexterm id="ch04-idx-968225-0"><primary>configuration files</primary><secondary>smb.conf (Samba configuration) file</secondary><see>smb.conf file</see></indexterm></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="4.2.4" id="ch04-SECT-2.4">
-<title>Configuration Options</title>
-
-
-<para><filename></filename>
-<indexterm id="ch04-idx-967407-0" class="startofrange"><primary>smb.conf (Samba configuration) file</primary><secondary>options for</secondary></indexterm>Options in the Samba configuration files fall into one of two categories: <firstterm>global</firstterm> or <firstterm>share</firstterm>. Each category dictates where an option can appear in the configuration file.</para>
-
-
-<variablelist>
-<varlistentry><term>Global</term>
-<listitem><para>
-<indexterm id="ch04-idx-967207-0"><primary>global options</primary></indexterm>Global options <emphasis>must</emphasis> appear in the <literal>[global]</literal> section and nowhere else. These are options that typically apply to the behavior of the Samba server itself, and not to any of its shares.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Share</term>
-<listitem><para>
-<indexterm id="ch04-idx-967209-0"><primary>share options</primary></indexterm>Share options can appear in specific shares, or they can appear in the <literal>[global]</literal> section. If they appear in the <literal>[global]</literal> section, they will define a default behavior for all shares, unless a share overrides the option with a value of its own.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>In addition, the values that a configuration option can take can be divided into four categories. They are as follows:</para>
-
-
-<variablelist>
-<varlistentry><term>Boolean</term>
-<listitem><para>
-<indexterm id="ch04-idx-967210-0"><primary>boolean type</primary></indexterm>These are simply yes or no values, but can be represented by any of the following: <literal>yes</literal>, <literal>no</literal>, <literal>true</literal>, <literal>false</literal>, <literal>0</literal>, <literal>1</literal>. The values are case insensitive: <literal>YES</literal> is the same as <literal>yes</literal>.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Numerical</term>
-<listitem><para>
-<indexterm id="ch04-idx-967220-0"><primary>numerical type</primary></indexterm>An integer, hexadecimal, or octal number. The standard <literal>0x</literal><emphasis>nn</emphasis> syntax is used for hexadecimal and <literal>0</literal><emphasis>nnn</emphasis> for octal.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>String</term>
-<listitem><para>A <indexterm id="ch04-idx-967222-0"><primary>string types</primary></indexterm>string of case-sensitive characters, such as a filename or a username.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Enumerated list</term>
-<listitem><para>A finite list of known values. In effect, a boolean is an <indexterm id="ch04-idx-967223-0"><primary>enumerated lists</primary></indexterm>enumerated list with only two values.<filename></filename>
-<indexterm id="ch04-idx-967166-0" class="endofrange" startref="ch04-idx-967091-0"/>
-<indexterm id="ch04-idx-967166-1" class="endofrange" startref="ch04-idx-967091-1"/></para></listitem>
-</varlistentry>
-</variablelist>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.3" id="ch04-46076">
-<title>Configuration File Options</title>
-
-
-<para>Samba has well over 200 configuration options at its disposal. So let's start off easy by introducing some of the options you can use to modify the configuration file itself.</para>
-
-
-<para>As we hinted earlier in the chapter, configuration files are by no means static. You can instruct Samba to include or even replace configuration options as it is processing them. The options to do this are summarized in <link linkend="ch04-94939">Table 4.2</link>.</para>
-
-
-<table label="4.2" id="ch04-94939">
-<title>Configuration File Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>config file</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified name)</para></entry>
-
-<entry colname="col3"><para>Sets the location of a configuration file to use instead of the current one.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>include</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified name)</para></entry>
-
-<entry colname="col3"><para>Specifies an additional segment of configuration options to be included at this point in the configuration file.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>copy</literal></para></entry>
-
-<entry colname="col2"><para>string (name of share)</para></entry>
-
-<entry colname="col3"><para>Allows you to clone the configuration options of another share in the current share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="4.3.1" id="ch04-SECT-3.0.1">
-<indexterm id="ch04-idx-968272-0"><primary>config file option</primary></indexterm>
-<title>
-config file</title>
-
-
-<para>The global <literal>config</literal> <literal>file</literal> option specifies a replacement configuration file that will be loaded when the option is encountered. If the target file exists, the remainder of the current configuration file, as well as the options encounter so far, will be discarded; Samba will configure itself entirely with the options in the new file. The <literal>config</literal> <literal>file</literal> option takes advantage of the variables above, which is useful in the event that you want load a special configuration file based on the machine name or user of the client that it connecting.</para>
-
-
-<para>For example, the following line instructs Samba to use a configuration file specified by the NetBIOS name of the client connecting, if such a file exists. If it does, options specified in the original configuration file are ignored. The following example attempts to lead a new configuration file based on the client's NetBIOS name:</para>
-
-
-<programlisting>[global]
- config file = /usr/local/samba/lib/smb.conf.%m</programlisting>
-
-
-<para>If the configuration file specified does not exist, the option is ignored and Samba will continue to configure itself based on the current file.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="4.3.2" id="ch04-SECT-3.0.2">
-<indexterm id="ch04-idx-968282-0"><primary>include option</primary></indexterm>
-<title>
-include</title>
-
-
-<para>This option, discussed in greater detail earlier, copies the target file into the current configuration file at the point specified, as shown in <link linkend="ch04-97340">Figure 4.1</link>. This option also takes advantage of the variables specified earlier in the chapter, which is useful in the event that you want load configuration options based on the machine name or user of the client that it connecting. You can use this option as follows:</para>
-
-
-<programlisting>[global]
- include = /usr/local/samba/lib/smb.conf.%m</programlisting>
-
-
-<para>If the configuration file specified does not exist, the option is ignored. Remember that any option specified previously is overridden. In <link linkend="ch04-97340">Figure 4.1</link>, all three options will override their previous values.</para>
-
-
-<figure label="4.1" id="ch04-97340">
-<title>The include option in a Samba configuration file</title>
-
-<graphic width="502" depth="232" fileref="figs/sam.0401.gif"></graphic>
-</figure>
-
-<para>The <literal>include</literal> option cannot understand the variables <literal>%u</literal> (user), <literal>%p</literal> (current share's rout directory), or <literal>%s</literal> (current share) because they are not set at the time the file is read.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="4.3.3" id="ch04-SECT-3.0.3">
-<indexterm id="ch04-idx-968285-0"><primary>copy option</primary></indexterm>
-<title>
-copy</title>
-
-
-<para>The <literal>copy</literal> configuration option allows you to clone the configuration options of the share name that you specify in the current share. The target share must appear earlier in the configuration file than the share that is performing the copy. For example:</para>
-
-
-<programlisting>[template]
- writable = yes
- browsable = yes
- valid users = andy, dave, peter
-
-[data]
- path = /usr/local/samba
- copy = template</programlisting>
-
-
-<para>Note that any options in the share that invoked the <literal>copy</literal> directive will override those in the cloned share; it does not matter whether they appear before or after the <literal>copy</literal><filename></filename>
-<indexterm id="ch04-idx-968230-0" class="endofrange" startref="ch04-idx-967407-0"/> directive.<filename></filename>
-<indexterm id="ch04-idx-967416-0" class="endofrange" startref="ch04-idx-968372-0"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.4" id="ch04-71382">
-<title>Server Configuration</title>
-
-
-<para>
-<indexterm id="ch04-idx-967242-0" class="startofrange"><primary>configuring Samba</primary><secondary>server</secondary></indexterm>Now it's time to begin configuring your Samba server. Let's introduce three basic configuration options that can appear in the <literal>[global]</literal> section of your <filename>smb.conf</filename> file:</para>
-
-
-<programlisting>[global]
- # Server configuration parameters
- netbios name = HYDRA
- server string = Samba %v on (%L)
- workgroup = SIMPLE</programlisting>
-
-
-<para>This configuration file is pretty simple; it advertises the Samba server on a NBT network under the NetBIOS name <literal>hydra</literal>. In addition, the machine belongs to the workgroup SIMPLE and displays a description to clients that includes the Samba version number as well as the NetBIOS name of the Samba server.</para>
-
-
-<tip role="ora">
-<para>If you had to enter <literal>encrypt passwords=yes</literal> in your earlier configuration file, you should do so here as well.</para>
-
-</tip>
-
-<para>Go ahead and try this configuration file. Create a file named <filename>smb.conf</filename>
-<indexterm id="ch04-idx-967246-0"><primary>smb.conf (Samba configuration) file</primary><secondary>creating</secondary></indexterm> under the <filename>/usr/local/samba/lib</filename> directory with the text listed above. Then reset the Samba server and use a Windows client to verify the results. Be sure that your Windows clients are in the SIMPLE workgroup as well. After clicking on the <indexterm id="ch04-idx-967247-0"><primary>Network Neighborhood icon</primary></indexterm>Network Neighborhood on a Windows client, you should see a window similar to <link linkend="ch04-38915">Figure 4.2</link>. (In this figure, <literal>phoenix</literal> and <literal>chimaera</literal> are our Windows clients.)</para>
-
-
-<figure label="4.2" id="ch04-38915">
-<title>Network Neighborhood showing the Samba server</title>
-
-<graphic width="502" depth="206" fileref="figs/sam.0402.gif"></graphic>
-</figure>
-
-<para>You can verify the <literal>server</literal> <literal>string</literal> by listing the details of the Network Neighborhood window (select the Details menu item under the View menu), at which point you should see a window similar to <link linkend="ch04-50900">Figure 4.3</link>.</para>
-
-
-<figure label="4.3" id="ch04-50900">
-<title>Network Neighborhood details listing</title>
-
-<graphic width="502" depth="220" fileref="figs/sam.0403.gif"></graphic>
-</figure>
-
-<para>If you were to click on the Hydra icon, a window should appear that shows the services that it provides. In this case, the window would be completely empty because there are no shares on the server yet.</para>
-
-
-<sect2 role="" label="4.4.1" id="ch04-SECT-4.1">
-<title>Server Configuration Options</title>
-
-
-<para>
-<indexterm id="ch04-idx-967248-0" class="startofrange"><primary>configuration options</primary><secondary>server</secondary></indexterm>
-<indexterm id="ch04-idx-967248-1" class="startofrange"><primary>server configuration options</primary></indexterm><link linkend="ch04-61150">Table 4.3</link> summarizes the server configuration options introduced previously. Note that all three of these options are global in scope; in other words, they must appear in the <literal>[global]</literal> section of the configuration file.</para>
-
-
-<table label="4.3" id="ch04-61150">
-<title>Server Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>netbios name</literal></para></entry>
-
-<entry colname="col2"><para>string</para></entry>
-
-<entry colname="col3"><para>Sets the primary NetBIOS name of the Samba server.</para></entry>
-
-<entry colname="col4"><para>Server DNS hostname</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>server string</literal></para></entry>
-
-<entry colname="col2"><para>string</para></entry>
-
-<entry colname="col3"><para>Sets a descriptive string for the Samba server.</para></entry>
-
-<entry colname="col4"><para><literal>Samba %v</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>workgroup</literal></para></entry>
-
-<entry colname="col2"><para>string</para></entry>
-
-<entry colname="col3"><para>Sets the NetBIOS group of machines that the server belongs to.</para></entry>
-
-<entry colname="col4"><para>Defined at compile time</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="4.4.1.1" id="ch04-SECT-4.1.1">
-<indexterm id="ch04-idx-968288-0"><primary>netbios name option</primary></indexterm>
-<title>
-netbios name</title>
-
-
-<para>The <literal>netbios</literal> <literal>name</literal> option allows you to set the NetBIOS name of the server. For example:</para>
-
-
-<programlisting>netbios name = YORKVM1</programlisting>
-
-
-<para>The default value for this configuration option is the server's hostname; that is, the first part of its complete DNS machine name. For example, a machine with the DNS name <literal>ruby.ora.com</literal> would be given the NetBIOS name <literal>RUBY</literal> by default. While you can use this option to restate the machine's NetBIOS name in the configuration file (as we did previously), it is more commonly used to assign the Samba server a NetBIOS name other than its current DNS name. Remember that the name given must follow the rules for valid NetBIOS machine names as outlines in <link linkend="ch01-48078">Chapter 1</link>.</para>
-
-
-<para>Changing the NetBIOS name of the server is not recommended unless you have a good reason. One such reason might be if the hostname of the machine is not unique because the LAN is divided over two or more DNS domains. For example, YORKVM1 is a good NetBIOS candidate for <emphasis>vm1.york.example.com</emphasis> to differentiate it from <emphasis>vm1.falkirk.example.com</emphasis>, which has the same hostname but resides in a different DNS domain.</para>
-
-
-<para>Another use of this option is for relocating SMB services from a dead or retired machine. For example, if <literal>SALES</literal> is the SMB server for the department, and it suddenly dies, you could immediately reset <literal>netbios</literal> <literal>name</literal> <literal>=</literal> <literal>SALES</literal> on a backup Samba machine that's taking over for it. Users won't have to change their drive mappings to a different machine; new connections to <literal>SALES</literal> will simply go to the new machine.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.4.1.2" id="ch04-SECT-4.1.2">
-<indexterm id="ch04-idx-968291-0"><primary>server string parameter</primary></indexterm>
-<title>
-server string</title>
-
-
-<para>The <literal>server</literal> <literal>string</literal> parameter defines a comment string that will appear next to the server name in both the Network Neighborhood (when shown with the Details menu) and the comment entry of the Microsoft Windows print manager. You can use the standard variables to provide information in the description. For example, our entry earlier was:</para>
-
-
-<programlisting>[global]
- server string = Samba %v on (%h)</programlisting>
-
-
-<para>The default for this option simply presents the current version of Samba and is equivalent to:</para>
-
-
-<programlisting>server string = Samba %v</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="4.4.1.3" id="ch04-SECT-4.1.3">
-<indexterm id="ch04-idx-968294-0"><primary>workgroup parameter</primary></indexterm>
-<title>
-workgroup</title>
-
-
-<para>The <literal>workgroup</literal> parameter sets the current workgroup where the Samba server will advertise itself. Clients that wish to access shares on the Samba server should be on the same NetBIOS workgroup. Remember that workgroups are really just NetBIOS group names, and must follow the standard NetBIOS naming conventions outlined in <link linkend="ch01-48078">Chapter 1</link>. For example:</para>
-
-
-<programlisting>[global]
- workgroup = SIMPLE</programlisting>
-
-
-<para>The default option for this parameter is set at compile time. If the entry is not changed in the makefile, it will be <literal>WORKGROUP</literal>. Because this tends to be the workgroup name of every unconfigured NetBIOS network, we recommend that you always set your workgroup name in the Samba configuration<indexterm id="ch04-idx-967252-0" class="endofrange" startref="ch04-idx-967248-0"/>
-<indexterm id="ch04-idx-967252-1" class="endofrange" startref="ch04-idx-967248-1"/> file.<footnote label="2" id="ch04-pgfId-962322">
-
-
-<para>We should also mention that it is an inherently bad idea to have a workgroup that shares the same name as a server.</para>
-
-
-</footnote>
-<indexterm id="ch04-idx-967243-0" class="endofrange" startref="ch04-idx-967242-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.5" id="ch04-14274">
-<title>Disk Share Configuration</title>
-
-
-<para>
-<indexterm id="ch04-idx-967244-0" class="startofrange"><primary>configuring disk shares</primary></indexterm>
-<indexterm id="ch04-idx-967244-1" class="startofrange"><primary>disk shares</primary><secondary>configuring</secondary></indexterm>We mentioned in the previous section that there were no disk shares on the <literal>hydra</literal> server. Let's continue with the configuration file and create an empty <indexterm id="ch04-idx-967268-0"><primary>disk shares</primary><secondary>creating</secondary></indexterm>disk share called [<literal>data</literal>]. Here are the additions that will do it:</para>
-
-
-<programlisting>[global]
- netbios name = HYDRA
- server string = Samba %v on (%L)
- workgroup = SIMPLE
-
-[data]
- path = /export/samba/data
- comment = Data Drive
- volume = Sample-Data-Drive
- writeable = yes
- guest ok = yes</programlisting>
-
-
-<para>The <literal>[data]</literal> share is typical for a Samba disk share. The share maps to a directory on the Samba server: <filename>/export/samba/data</filename>. We've also provided a comment that describes the share as a <literal>Data</literal> <literal>Drive</literal>, as well as a volume name for the share itself.</para>
-
-
-<para>The share is set to writeable so that users can write data to it; the default with Samba is to create a read-only share. As a result, this option needs to be explicitly set for each disk share you wish to make writeable.</para>
-
-
-<para>You may have noticed that we set the <literal>guest</literal> <literal>ok</literal> parameter to <literal>yes</literal>. While this isn't very security-conscious, there are some password issues that we need to understand before setting up individual users and authentication. For the moment, this will sidestep those issues and let anyone connect to the share.</para>
-
-
-<para>Go ahead and make these additions to your configuration file. In addition, create the <filename>/export/samba/data</filename> directory as root on your Samba machine with the following commands:</para>
-
-
-<programlisting># <emphasis role="bold">mkdir /export/samba/data</emphasis>
-# <emphasis role="bold">chmod 777 /export/samba/data</emphasis></programlisting>
-
-
-<para>Now, if you connect to the <literal>hydra</literal> server again (you can do this by clicking on its icon in the Windows Network Neighborhood), you should see a single share listed entitled <literal>data</literal>, as shown in <link linkend="ch04-13866">Figure 4.4</link>. This share should also have read/write access to it. Try creating or copying a file into the share. Or, if you're really feeling adventurous, you can even try mapping a network drive to it!</para>
-
-
-<figure label="4.4" id="ch04-13866">
-<title>The initial data share on the Samba server</title>
-
-<graphic width="502" depth="175" fileref="figs/sam.0404.gif"></graphic>
-</figure>
-
-<sect2 role="" label="4.5.1" id="ch04-SECT-5.1">
-<title>Disk Share Configuration Options</title>
-
-
-<para>
-<indexterm id="ch04-idx-967272-0" class="startofrange"><primary>configuration options</primary><secondary>disk share</secondary></indexterm>The basic Samba configuration options for disk shares previously introduced are listed in <link linkend="ch04-82964">Table 4.4</link>.</para>
-
-
-<table label="4.4" id="ch04-82964">
-<title>Basic Share Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>path (directory)</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix directory that will be provided for a disk share or used for spooling by a printer share</para></entry>
-
-<entry colname="col4"><para><literal>/tmp</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>guest ok (public)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, authentication is not needed to access this share</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>comment</literal></para></entry>
-
-<entry colname="col2"><para>string</para></entry>
-
-<entry colname="col3"><para>Sets the comment that appears with the share</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>volume</literal></para></entry>
-
-<entry colname="col2"><para>string</para></entry>
-
-<entry colname="col3"><para>Sets the volume name: the DOS name of the physical drive</para></entry>
-
-<entry colname="col4"><para>Share name</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>read only</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, allows read only access to a share.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>writeable (write ok)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>no</literal>, allows read only access to a share.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="4.5.1.1" id="ch04-SECT-5.1.1">
-<title>path</title>
-
-
-<para>
-<indexterm id="ch04-idx-967257-0"><primary>pathnames</primary><secondary>option for</secondary></indexterm>
-<indexterm id="ch04-idx-967257-1"><primary>shares</primary><secondary>file, path option for</secondary></indexterm>
-<indexterm id="ch04-idx-967257-2"><primary>print shares</primary><secondary>path option</secondary></indexterm>This option, which has the synonym <literal>directory</literal>, indicates the pathname at the root of the file or printing share. You can choose any path on the Samba server, so long as the owner of the Samba process that is connecting has read and write access to that directory. If the path is for a printing share, it should point to a temporary directory where files can be written on the server before being spooled to the target printer ( <filename> /tmp</filename> and <filename>/var/spool</filename> are popular choices). If this path is for a <indexterm id="ch04-idx-967258-0"><primary>disk shares</primary><secondary>path option</secondary></indexterm>disk share, the contents of the folder representing the share name on the client will match the content of the directory on the Samba server. For example, if we have the following disk share listed in our configuration file:</para>
-
-
-<programlisting>[network]
- path = /export/samba/network
- writable = yes
- guest ok = yes</programlisting>
-
-
-<para>And the contents of the directory <filename>/usr/local/network</filename> on the Unix side are:</para>
-
-
-<programlisting>$ <emphasis role="bold">ls -al /export/samba/network</emphasis>
-drwxrwxrwx 9 root nobody 1024 Feb 16 17:17 .
-drwxr-xr-x 9 nobody nobody 1024 Feb 16 17:17 ..
-drwxr-xr-x 9 nobody nobody 1024 Feb 16 17:17 quicken
-drwxr-xr-x 9 nobody nobody 1024 Feb 16 17:17 tax98
-drwxr-xr-x 9 nobody nobody 1024 Feb 16 17:17 taxdocuments</programlisting>
-
-
-<para>Then we should see the equivalent of <link linkend="ch04-88746">Figure 4.5</link> on the client side.</para>
-
-
-<figure label="4.5" id="ch04-88746">
-<title>Windows client view of a network filesystem specified by path</title>
-
-<graphic width="502" depth="155" fileref="figs/sam.0405.gif"></graphic>
-</figure>
-</sect3>
-
-
-
-<sect3 role="" label="4.5.1.2" id="ch04-SECT-5.1.2">
-<indexterm id="ch04-idx-968300-0"><primary>guest ok option</primary></indexterm>
-<title>
-guest ok</title>
-
-
-<para>This option (which has an older synonym <literal>public</literal>) allows or prohibits guest access to a share. The default value is <literal>no</literal>. If set to <literal>yes</literal>, it means that no username or password will be needed to connect to the share. When a user connects, the access rights will be equivalent to the designated guest user. The default account to which Samba offers the share is <literal>nobody</literal>. However, this can be reset with the <literal>guest</literal> <literal>account</literal> configuration option. For example, the following lines allow guest user access to the <literal>[accounting]</literal> share with the permissions of the <emphasis>ftp</emphasis> account:</para>
-
-
-<programlisting>[global]
- guest account = ftp
-[accounting]
- path = /usr/local/account
- guest ok = yes</programlisting>
-
-
-<para>Note that users can still connect to the share using a valid username/password combination. If successful, they will hold the access rights granted by their own account and not the guest account. If a user attempts to log in and fails, however, he or she will default to the access rights of the guest account. You can mandate that every user who attaches to the share will be using the guest account (and will have the permissions of the guest) by setting the option <literal>guest</literal> <literal>only</literal> <literal>=</literal> <literal>yes</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.5.1.3" id="ch04-SECT-5.1.3">
-<indexterm id="ch04-idx-968303-0"><primary>comment option</primary></indexterm>
-<title>
-comment</title>
-
-
-<para>The <literal>comment</literal> option allows you to enter a comment that will be sent to the client when it attempts to browse the share. The user can see the comment by listing Details on the share folder under the appropriate computer in the Windows Network Neighborhood, or type the command <literal>NET</literal> <literal>VIEW</literal> at an MS-DOS prompt. For example, here is how you might insert a comment for a <literal>[network]</literal> share:</para>
-
-
-<programlisting>[network]
- comment = Network Drive
- path = /export/samba/network</programlisting>
-
-
-<para>This yields a folder similar to <link linkend="ch04-34850">Figure 4.6</link> on the client side. Note that with the current configuration of Windows, this comment will not be shown once a share is mapped to a Windows network drive.</para>
-
-
-<figure label="4.6" id="ch04-34850">
-<title>Windows client view of a share comment</title>
-
-<graphic width="502" depth="135" fileref="figs/sam.0406.gif"></graphic>
-</figure>
-
-<para>Be sure not to confuse the <literal>comment</literal> option, which documents a Samba server's shares, with the <literal>server</literal> <literal>string</literal> option, which documents the server itself.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.5.1.4" id="ch04-SECT-5.1.4">
-<indexterm id="ch04-idx-968306-0"><primary>volume option</primary></indexterm>
-<title>
-volume</title>
-
-
-<para>This option allows you to specify the volume name of the share as reported by SMB. This normally resolves to the name of the share given in the <filename>smb.conf</filename> file. However, if you wish to name it something else (for whatever reason) you can do so with this option.</para>
-
-
-<para>For example, an installer program may check the volume name of a CD-ROM to make sure the right CD-ROM is in the drive before attempting to install it. If you copy the contents of the CD-ROM into a network share, and wish to install from there, you can use this option to get around the issue:</para>
-
-
-<programlisting>[network]
- comment = Network Drive
- volume = ASVP-102-RTYUIKA
- path = /home/samba/network</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="4.5.1.5" id="ch04-SECT-5.1.5">
-<indexterm id="ch04-idx-968309-0"><primary>read only option</primary></indexterm>
-<indexterm id="ch04-idx-968309-1"><primary>writeable/write ok option</primary></indexterm>
-<title>
-
-read only and writeable</title>
-
-
-<para>The options <literal>read</literal> <literal>only</literal> and <literal>writeable</literal> (or <literal>write</literal> <literal>ok </literal>) are really two ways of saying the same thing, but approached from opposite ends. For example, you can set either of the following options in the <literal>[global]</literal> section or in an individual share:</para>
-
-
-<programlisting>read only = yes
-writeable = no</programlisting>
-
-
-<para>If either option is set as shown, data can be read from a share, but cannot be written to it. You might think you would need this option only if you were creating a read-only share. However, note that this read-only behavior is the <emphasis>default</emphasis> action for shares; if you want to be able to write data to a share, you must explicitly specify one of the following options in the configuration file for each share:</para>
-
-
-<programlisting>read only = no
-writeable = yes</programlisting>
-
-
-<para>Note that if you specify more than one occurrence of either option, Samba will adhere to the last value it encounters for the<indexterm id="ch04-idx-967387-0" class="endofrange" startref="ch04-idx-967272-0"/> share.<indexterm id="ch04-idx-967245-0" class="endofrange" startref="ch04-idx-967244-0"/>
-<indexterm id="ch04-idx-967245-1" class="endofrange" startref="ch04-idx-967244-1"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.6" id="ch04-86705">
-<title>Networking Options with Samba</title>
-
-
-<para>
-<indexterm id="ch04-idx-967291-0" class="startofrange"><primary>networking</primary><secondary>options</secondary></indexterm>If you're running Samba on a multi-homed machine (that is, one on multiple subnets), or even if you want to implement a security policy on your own subnet, you should take a close look at the networking configuration options:</para>
-
-
-<para>For the purposes of this exercise, let's assume that our Samba server is connected to a network with more than one subnet. Specifically, the machine can access both the 192.168.220.* and 134.213.233.* subnets. Here are our additions to the ongoing configuration file for the networking configuration options:</para>
-
-
-<programlisting>[global]
- netbios name = HYDRA
- server string = Samba %v on (%L)
- workgroup = SIMPLE
-
- # Networking configuration options
- hosts allow = 192.168.220. 134.213.233. localhost
- hosts deny = 192.168.220.102
- interfaces = 192.168.220.100/255.255.255.0 \
- 134.213.233.110/255.255.255.0
- bind interfaces only = yes
-
-[data]
- path = /home/samba/data
- guest ok = yes
- comment = Data Drive
- volume = Sample-Data-Drive
- writeable = yes</programlisting>
-
-
-<para>
-<indexterm id="ch04-idx-967305-0"><primary>hosts</primary><secondary>networking option for connections</secondary></indexterm>Let's first talk about the <literal>hosts</literal> <literal>allow</literal> and <literal>hosts</literal> <literal>deny</literal> options. If these options sound familiar, you're probably thinking of the <filename>hosts.allow</filename> and <filename>hosts.deny</filename> files that are found in the <filename>/etc</filename> directories of many Unix systems. The purpose of these options is identical to those files; they provide a means of security by allowing or denying the connections of other hosts based on their IP addresses. Why not just use the <filename>hosts.allow</filename> and <filename>hosts.deny</filename> files themselves? Because there may be services on the server that you want others to access without giving them access Samba's disk or printer shares</para>
-
-
-<para>With the <literal>hosts</literal> <literal>allow</literal> option above, we've specified a cropped IP address: 192.168.220. (Note that there is still a third period; it's just missing the fourth number.) This is equivalent to saying: "All hosts on the 192.168.220 subnet." However, we've explicitly specified in a hosts deny line that 192.168.220.102 is not to be allowed access.</para>
-
-
-<para>You might be wondering: why will 192.168.220.102 be denied even though it is still in the subnet matched by the <literal>hosts</literal> <literal>allow</literal> option? Here is how Samba sorts out the rules specified by <literal>hosts</literal> <literal>allow</literal> and <literal>hosts</literal> <literal>deny </literal>:</para>
-
-
-<orderedlist>
-<listitem><para>If there are no <literal>allow</literal> or <literal>deny</literal> options defined anywhere in <filename>smb.conf</filename>, Samba will allow connections from any machine allowed by the system itself.</para></listitem>
-<listitem><para>If there are <literal>hosts</literal> <literal>allow</literal> or <literal>hosts</literal> <literal>deny</literal> options defined in the <literal>[global]</literal> section of <filename>smb.conf</filename>, they will apply to all shares, even if the shares have an overriding option defined.</para></listitem>
-<listitem><para>If there is only a <literal>hosts</literal> <literal>allow</literal> option defined for a share, only the hosts listed will be allowed to use the share. All others will be denied.</para></listitem>
-<listitem><para>If there is only a <literal>hosts</literal> <literal>deny</literal> option defined for a share, any machine which is not on the list will be able to use the share.</para></listitem>
-<listitem><para>If both a <literal>hosts</literal> <literal>allow</literal> and <literal>hosts</literal> <literal>deny</literal> option are defined, a host must appear in the allow list and not appear in the deny list (in any form) in order to access the share. Otherwise, the host will not be allowed.</para></listitem>
-</orderedlist>
-
-<warning role="ora"> <para>
-<indexterm id="ch04-idx-967307-0"><primary>hosts</primary><secondary>subnets and,
-caution with</secondary></indexterm>
-<indexterm id="ch04-idx-967307-1"><primary>subnets</primary><secondary>hosts and,
-caution with</secondary></indexterm>Take care that you don't explicitly
-allow a host to access a share, but then deny access to the entire
-subnet of which the host is part.</para>
-
-</warning>
-
-<para>Let's look at another example of that final item. Consider the following options:</para>
-
-
-<programlisting>hosts allow = 111.222.
-hosts deny = 111.222.333.</programlisting>
-
-
-<para>In this case, only the hosts that belong to the subnet 111.222.*.* will be allowed access to the Samba shares. However, if a client belongs to the 111.222.333.* subnet, it will be denied access, even though it still matches the qualifications outlined by <literal>hosts</literal> <literal>allow</literal>. The client must appear on the <literal>hosts</literal> <literal>allow</literal> list and <emphasis>must not</emphasis> appear on the <literal>hosts</literal> <literal>deny</literal> list in order to gain access to a Samba share. If a computer attempts to access a share to which it is not allowed access, it will receive an error message.</para>
-
-
-<para>The other two options that we've specified are the <literal>interfaces</literal> and the <literal>bind</literal> <literal>interface</literal> <literal>only</literal> address. Let's look at the <literal>interfaces</literal> option first. Samba, by default, sends data only from the primary network interface, which in our example is the 192.168.220.100 subnet. If we would like it to send data to more than that one <indexterm id="ch04-idx-967310-0"><primary>interfaces, networking options for</primary></indexterm>interface, we need to specify the complete list with the <literal>interfaces</literal> option. In the previous example, we've bound Samba to interface with both subnets (192.168.220 and 134.213.233) on which the machine is operating by specifying the other network interface address: 134.213.233.100. If you have more than one interface on your computer, you should always set this option as there is no guarantee that the primary interface that Samba chooses will be the right one.</para>
-
-
-<para>Finally, the <literal>bind</literal> <literal>interfaces</literal> <literal>only</literal> option instructs the <filename>nmbd</filename> process not to accept any broadcast messages other than those subnets specified with the <literal>interfaces</literal> option. Note that this is different from the <literal>hosts</literal> <literal>allow</literal> and <literal>hosts</literal> <literal>deny</literal> options, which prevent machines from making connections to services, but not from receiving broadcast messages. Using the <literal>bind</literal> <literal>interfaces</literal> <literal>only</literal> option is a way to shut out even datagrams from foreign subnets from being received by the Samba server. In addition, it instructs the <emphasis>smbd</emphasis> process to bind to only the interface list given by the <emphasis>interfaces</emphasis> option. This restricts the networks that Samba will serve.</para>
-
-
-<sect2 role="" label="4.6.1" id="ch04-SECT-6.1">
-<title>Networking Options</title>
-
-
-<para>
-<indexterm id="ch04-idx-967302-0"><primary>networking</primary><secondary>options</secondary><tertiary>list of</tertiary></indexterm>The networking options we introduced above are summarized in <link linkend="ch04-32963">Table 4.5</link>.</para>
-
-
-<table label="4.5" id="ch04-32963">
-<title>Networking Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>hosts allow (allow hosts)</literal></para></entry>
-
-<entry colname="col2"><para>string (list of hostnames)</para></entry>
-
-<entry colname="col3"><para>Specifies the machines that can connect to Samba.</para></entry>
-
-<entry colname="col4"><para>none</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>hosts deny (deny hosts)</literal></para></entry>
-
-<entry colname="col2"><para>string (list of hostnames)</para></entry>
-
-<entry colname="col3"><para>Specifies the machines that cannot connect to Samba.</para></entry>
-
-<entry colname="col4"><para>none</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>interfaces</literal></para></entry>
-
-<entry colname="col2"><para>string (list of IP/netmask combinations)</para></entry>
-
-<entry colname="col3"><para>Sets the network interfaces Samba will respond to. Allows correcting defaults.</para></entry>
-
-<entry colname="col4"><para>system-dependent</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>bind</literal></para>
-
-<para><literal>interfaces only</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, Samba will bind only to those interfaces specified by the <literal>interfaces</literal> option.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>socket</literal></para>
-
-<para><literal>address</literal></para></entry>
-
-<entry colname="col2"><para>string (IP address)</para></entry>
-
-<entry colname="col3"><para>Sets IP address to listen on, for use with multiple virtual interfaces on a server.</para></entry>
-
-<entry colname="col4"><para>none</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="4.6.1.1" id="ch04-SECT-6.1.1">
-<indexterm id="ch04-idx-968312-0"><primary>hosts allow option</primary></indexterm>
-<title>
-hosts allow</title>
-
-
-<para>
-<indexterm id="ch04-idx-967314-0"><primary>hosts</primary><secondary>networking option for connections</secondary></indexterm>The <literal>hosts</literal> <literal>allow</literal> option (sometimes written as <literal>allow</literal> <literal>hosts</literal>) specifies the machines that have permission to access shares on the Samba server, written as a comma- or space-separated list of names of machines or their IP addresses. You can gain quite a bit of security by simply placing your LAN's subnet address in this option. For example, we specified the following in our example:</para>
-
-
-<programlisting>hosts allow = 192.168.220. localhost</programlisting>
-
-
-<para>Note that we placed <literal>localhost</literal> after the subnet address. One of the most common mistakes when attempting to use the <literal>hosts</literal> <literal>allow</literal> option is to accidentally disallow the Samba server from communicating with itself. The <filename>smbpasswd</filename> program will occasionally need to connect to the Samba server as a client in order to change a user's encrypted password. In addition, local browsing propagation requires local host access. If this option is enabled and the localhost address is not specified, the locally-generated packets requesting the change of the encrypted password will be discarded by Samba, and browsing propagation will not work properly. To avoid this, explicitly allow the loopback address (either <literal>localhost</literal> or <literal>127.0.0.1</literal>) to be used.<footnote label="3" id="ch04-pgfId-965714">
-
-
-<para>Starting with Samba 2.0.5, <literal>localhost</literal> will automatically be allowed unless it is explicitly denied.</para>
-
-
-</footnote></para>
-
-
-<para>You can specify any of the following formats for this option:</para>
-
-
-<itemizedlist>
-<listitem><para>Hostnames, such as <literal>ftp.example.com </literal>.</para></listitem>
-<listitem><para>IP addresses, like <literal>130.63.9.252</literal>.</para></listitem>
-<listitem><para>Domain names, which can be differentiated from individual hostnames because they start with a dot. For example, <literal>.ora.com</literal> represents all machines within the <emphasis>ora.com</emphasis> domain.</para></listitem>
-<listitem><para>Netgroups, which start with an at-sign, such as <literal>@printerhosts</literal>. Netgroups are available on systems running yellow pages/NIS or NIS+, but rarely otherwise. If netgroups are supported on your system, there should be a <literal>netgroups</literal> manual page that describes them in more detail.</para></listitem>
-<listitem><para>Subnets, which end with a dot. For example, <literal>130.63.9.</literal> means all the machines whose IP addresses begin with 130.63.9.</para></listitem>
-<listitem><para>The keyword <literal>ALL</literal>, which allows any client access.</para></listitem>
-<listitem><para>The keyword <literal>EXCEPT</literal> followed by more one or more names, IP addresses, domain names, netgroups, or subnets. For example, you could specify that Samba allow all hosts except those on the 192.168.110 subnet with <literal>hosts</literal> <literal>allow</literal> <literal>=</literal> <literal>ALL</literal> <literal>EXCEPT</literal> <literal>192.168.110.</literal> (remember the trailing dot).</para></listitem>
-</itemizedlist>
-
-<para>Using the <literal>ALL</literal> keyword is almost always a bad idea, since it means that anyone on any network can browse your files if they guess the name of your server.</para>
-
-
-<para>Note that there is no default value for the <literal>hosts</literal> <literal>allow</literal> configuration option, although the default course of action in the event that neither option is specified is to allow access from all sources. In addition, if you specify this option in the <literal>[global]</literal> section of the configuration file, it will override any <literal>hosts</literal> <literal>allow</literal> options defined shares.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.6.1.2" id="ch04-SECT-6.1.2">
-<indexterm id="ch04-idx-968319-0"><primary>hosts deny option</primary></indexterm>
-<title>
-hosts deny</title>
-
-
-<para>The <literal>hosts</literal> <literal>deny</literal> option (also <literal>deny</literal> <literal>hosts</literal>) specifies machines that do not have permission to access a share, written as a comma- or space-separated list of machine names or their IP addresses. Use the same format as specifying clients as the <literal>hosts</literal> <literal>allow</literal> option above. For example, to restrict access to the server from everywhere but <filename>example.com</filename>, you could write:</para>
-
-
-<programlisting>hosts deny = ALL EXCEPT .example.com</programlisting>
-
-
-<para>Like <literal>hosts</literal> <literal>allow</literal>, there is no default value for the <literal>hosts</literal> <literal>deny</literal> configuration option, although the default course of action in the event that neither option is specified is to allow access from all sources. Also, if you specify this option in the <literal>[global]</literal> section of the configuration file, it will override any <literal>hosts</literal> <literal>deny</literal> options defined in shares. If you wish to deny <emphasis>hosts</emphasis> access to specific shares, omit both the <literal>hosts</literal> <literal>allow</literal> and <literal>hosts</literal> <literal>deny</literal> options in the <literal>[global]</literal> section of the configuration file.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.6.1.3" id="ch04-SECT-6.1.3">
-<indexterm id="ch04-idx-968322-0"><primary>interfaces option</primary></indexterm>
-<title>
-interfaces</title>
-
-
-<para>
-<indexterm id="ch04-idx-967320-0"><primary>hosts</primary><secondary>networking option for connections</secondary></indexterm>The <literal>interfaces</literal> option outlines the network addresses to which you want the Samba server to recognize and respond. This option is handy if you have a computer that resides on more than one network subnet. If this option is not set, Samba searches for the primary network interface of the server (typically the first Ethernet card) upon startup and configures itself to operate on only that subnet. If the server is configured for more than one subnet and you do not specify this option, Samba will only work on the first subnet it encounters. You must use this option to force Samba to serve the other subnets on your network.</para>
-
-
-<para>The value of this option is one or more sets of IP address/netmask pairs, such as the following:</para>
-
-
-<programlisting>interfaces = 192.168.220.100/255.255.255.0 192.168.210.30/255.255.255.0</programlisting>
-
-
-<para>You can optionally specify a CIDR format bitmask, as follows:</para>
-
-
-<programlisting>interfaces = 192.168.220.100/24 192.168.210.30/24</programlisting>
-
-
-<para>The bitmask number specifies the first number of bits that will be turned on in the netmask. For example, the number 24 means that the first 24 (of 32) bits will be activated in the bit mask, which is the same as saying 255.255.255.0. Likewise, 16 would be equal to 255.255.0.0, and 8 would be equal to 255.0.0.0.</para>
-
-
-<tip role="ora">
-<para>This option may not work correctly if you are using DHCP.</para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="4.6.1.4" id="ch04-SECT-6.1.4">
-<indexterm id="ch04-idx-968325-0"><primary>bind interfaces only option</primary></indexterm>
-<title>
-bind interfaces only</title>
-
-
-<para>The <literal>bind</literal> <literal>interfaces</literal> <literal>only</literal> option can be used to force the <emphasis>smbd</emphasis> and <emphasis>nmbd</emphasis> processes to serve SMB requests to only those addresses specified by the <literal>interfaces</literal> option. The <emphasis>nmbd</emphasis> process normally binds to the all addresses interface (0.0.0.0.) on ports 137 and 138, allowing it to receive broadcasts from anywhere. However, you can override this behavior with the following:</para>
-
-
-<programlisting>bind interfaces only = yes</programlisting>
-
-
-<para>This will cause both Samba processes to ignore any packets whose origination address does not match the broadcast address(es) specified by the <literal>interfaces</literal> option, including broadcast packets. With <emphasis>smbd</emphasis>, this option will cause Samba to not serve file requests to subnets other than those listed in the <literal>interfaces</literal> option. You should avoid using this option if you want to allow temporary network connections, such as those created through SLIP or PPP. It's very rare that this option is needed, and it should only be used by experts.</para>
-
-
-<tip role="ora">
-<para>If you set <literal>bind interfaces only</literal> to <literal>yes </literal>, you should add the localhost address (127.0.01) to the "interfaces" list. Otherwise, <emphasis>smbpasswd</emphasis> will be unable to connect to the server using its default mode in order to change a password.</para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="4.6.1.5" id="ch04-SECT-6.1.5">
-<indexterm id="ch04-idx-968328-0"><primary>socket address option</primary></indexterm>
-<title>
-socket address</title>
-
-
-<para>
-<indexterm id="ch04-idx-967324-0"><primary>addresses, networking option for</primary></indexterm>The <literal>socket</literal> <literal>address</literal> option dictates which of the addresses specified with the <literal>interfaces</literal> parameter Samba should listen on for connections. Samba accepts connections on all addresses specified by default. When used in an <filename>smb.conf</filename> file, this option will force Samba to listen on only one IP address. For example:</para>
-
-
-<programlisting>interfaces = 192.168.220.100/24 192.168.210.30/24
-socket address = 192.168.210.30</programlisting>
-
-
-<para>This option is a programmer's tool and we recommend that you do not use it.<indexterm id="ch04-idx-967297-0" class="endofrange" startref="ch04-idx-967291-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.7" id="ch04-16899">
-<title>Virtual Servers</title>
-
-
-<para>
-<indexterm id="ch04-idx-967325-0" class="startofrange"><primary>servers</primary><secondary>virtual</secondary></indexterm>
-<indexterm id="ch04-idx-967325-1" class="startofrange"><primary>virtual servers</primary></indexterm>Virtual servers are a technique for creating the illusion of multiple <indexterm id="ch04-idx-967337-0"><primary>NetBIOS (Network Basic Input/Output System)</primary><secondary>multiple servers</secondary><see>virtual servers</see></indexterm>NetBIOS servers on the network, when in reality there is only one. The technique is simple to implement: a machine simply registers more than one NetBIOS name in association with its IP address. There are tangible benefits to doing this.</para>
-
-
-<para>The accounting department, for example, might have an <literal>accounting</literal> server, and clients of it would see just the accounting disks and printers. The marketing department could have their own server, <literal>marketing</literal>, with their own reports, and so on. However, all the services would be provided by one medium-sized Unix workstation (and one relaxed administrator), instead of having one small server and one administrator per department.</para>
-
-
-<para>Samba will allow a Unix server to use more than one NetBIOS name with the <literal>netbios</literal> <literal>aliases</literal> option. See <link linkend="ch04-92259">Table 4.6</link>.</para>
-
-
-<table label="4.6" id="ch04-92259">
-<title>Virtual Server Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>netbios aliases</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch04-idx-967338-0"><primary>virtual servers</primary><secondary>options for</secondary></indexterm>
-<indexterm id="ch04-idx-967338-1"><primary>servers</primary><secondary>virtual</secondary><tertiary>options for</tertiary></indexterm>List of NetBIOS names</para></entry>
-
-<entry colname="col3"><para>Additional NetBIOS names to respond to, for use with multiple "virtual" Samba servers.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="4.7.1" id="ch04-SECT-7.0.1">
-<indexterm id="ch04-idx-968331-0"><primary>netbios aliases option</primary></indexterm>
-<title>
-netbios aliases</title>
-
-
-<para>The <literal>netbios</literal> <literal>aliases</literal> option can be used to give the Samba server more than one <indexterm id="ch04-idx-967339-0"><primary>NetBIOS name</primary><secondary>option for aliases</secondary></indexterm>
-<indexterm id="ch04-idx-967339-1"><primary>aliases</primary><secondary sortas="NetBIOS names">for NetBIOS names</secondary></indexterm>NetBIOS name. Each NetBIOS name listed as a value will be displayed in the Network Neighborhood of a browsing machine. When a connection is requested to any machine, however, it will connect to the same Samba server.</para>
-
-
-<para>This might come in handy, for example, if you're transferring three departments' data to a single Unix server with modern large disks, and are retiring or reallocating the old NT servers. If the three servers are called <literal>sales</literal>, <literal>accounting</literal>, and <literal>admin</literal>, you can have Samba represent all three servers with the following options:</para>
-
-
-<programlisting>[global]
- netbios aliases = sales accounting admin
- include = /usr/local/samba/lib/smb.conf.%L</programlisting>
-
-
-<para>See <link linkend="ch04-28393">Figure 4.7</link> for what the Network Neighborhood would display from a client.When a client attempts to connect to Samba, it will specify the name of the server that it's trying to connect to, which you can access through the <literal>%L</literal> variable. If the requested server is <literal>sales</literal>, Samba will include the <filename>/usr/local/samba/lib/smb.conf.sales</filename> file. This file might contain global and share declarations exclusively for the sales team, such as the following:</para>
-
-
-<programlisting>[global]
- workgroup = SALES
- hosts allow = 192.168.10.255
-
-[sales1998]
- path = /usr/local/samba/sales/sales1998/
-...</programlisting>
-
-
-<para>This particular example would set the workgroup to SALES as well, and set the IP address to allow connections only from the SALES subnet (192.168.10). In addition, it would offer shares specific to the sales department.</para>
-
-
-<figure label="4.7" id="ch04-28393">
-<indexterm id="ch04-idx-967332-0" class="endofrange" startref="ch04-idx-967325-0"/><indexterm id="ch04-idx-967332-1" class="endofrange" startref="ch04-idx-967325-1"/><title>Using NetBIOS aliases for a Samba server
- </title>
-
-<graphic width="502" depth="196" fileref="figs/sam.0407.gif"></graphic>
-</figure>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="4.8" id="ch04-29331">
-<title>Logging Configuration Options</title>
-
-
-<para>
-<indexterm id="ch04-idx-967340-0" class="startofrange"><primary>log files/logging</primary><secondary>configuration options</secondary></indexterm>
-<indexterm id="ch04-idx-967340-1" class="startofrange"><primary>log files/logging</primary><secondary>checking</secondary></indexterm>Occasionally, we need to find out what Samba is up to. This is especially true when Samba is performing an unexpected action or is not performing at all. To find out this information, we need to check Samba's log files to see exactly why it did what it did.</para>
-
-
-<para>Samba log files can be as brief or verbose as you like. Here is an example of what a Samba log file looks like:</para>
-
-
-<programlisting>[1999/07/21 13:23:25, 3] smbd/service.c:close_cnum(514)
- phoenix (192.168.220.101) closed connection to service IPC$
-[1999/07/21 13:23:25, 3] smbd/connection.c:yield_connection(40)
- Yielding connection to IPC$
-[1999/07/21 13:23:25, 3] smbd/process.c:process_smb(615)
- Transaction 923 of length 49
-[1999/07/21 13:23:25, 3] smbd/process.c:switch_message(448)
- switch message SMBread (pid 467)
-[1999/07/21 13:23:25, 3] lib/doscalls.c:dos_ChDir(336)
- dos_ChDir to /home/samba
-[1999/07/21 13:23:25, 3] smbd/reply.c:reply_read(2199)
- read fnum=4207 num=2820 nread=2820
-[1999/07/21 13:23:25, 3] smbd/process.c:process_smb(615)
- Transaction 924 of length 55
-[1999/07/21 13:23:25, 3] smbd/process.c:switch_message(448)
- switch message SMBreadbraw (pid 467)
-[1999/07/21 13:23:25, 3] smbd/reply.c:reply_readbraw(2053)
- readbraw fnum=4207 start=130820 max=1276 min=0 nread=1276
-[1999/07/21 13:23:25, 3] smbd/process.c:process_smb(615)
- Transaction 925 of length 55
-[1999/07/21 13:23:25, 3] smbd/process.c:switch_message(448)
- switch message SMBreadbraw (pid 467)</programlisting>
-
-
-<para>Many of these options are of use only to Samba programmers. However, we will go over the meaning of some of these entries in more detail in <link linkend="SAMBA-CH-9">Chapter 9</link>.</para>
-
-
-<para>Samba contains six options that allow users to describe how and where logging information should be written. Each of these options are global options and cannot appear inside a share definition. Here is an up-to-date configuration file that covers each of the share and logging options that we've seen so far:</para>
-
-
-<programlisting>[global]
- netbios name = HYDRA
- server string = Samba %v on (%I)
- workgroup = SIMPLE
-
- # Networking configuration options
- hosts allow = 192.168.220. 134.213.233. localhost
- hosts deny = 192.168.220.102
- interfaces = 192.168.220.100/255.255.255.0 \
- 134.213.233.110/255.255.255.0
- bind interfaces only = yes
-
- # Debug logging information
- log level = 2
- log file = /var/log/samba.log.%m
- max log size = 50
- debug timestamp = yes
-
-[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- comment = Data Drive
- volume = Sample-Data-Drive
- writeable = yes</programlisting>
-
-
-<para> Here, we've added a custom log file that reports information up to debug level 2. This is a relatively light debugging level. The logging level ranges from 1 to 10, where level 1 provides only a small amount of information and level 10 provides a plethora of low-level information. Level 2 will provide us with useful debugging information without wasting disk space on our server. In practice, you should avoid using log levels greater than 3 unless you are programming Samba.</para>
-
-
-<para>This file is located in the <filename>/var/log</filename> directory thanks to the <literal>log</literal> <literal>file</literal> configuration option. However, we can use variable substitution to create log files specifically for individual users or clients, such as with the <literal>%m</literal> variable in the following line:</para>
-
-
-<programlisting>log file = /usr/local/logs/samba.log.%m</programlisting>
-
-
-<para>Isolating the log messages can be invaluable in tracking down a network error if you know the problem is coming from a specific machine or user.</para>
-
-
-<para>We've added another precaution to the log files: no one log file can exceed 50 kilobytes in size, as specified by the <literal>max</literal> <literal>log</literal> <literal>size</literal> option. If a log file exceeds this size, the contents are moved to a file with the same name but with the suffix <emphasis>.old</emphasis> appended. If the <emphasis>.old</emphasis> file already exists, it is overwritten and its contents are lost. The original file is cleared, waiting to receive new logging information. This prevents the hard drive from being overwhelmed with Samba log files during the life of our daemons.</para>
-
-
-<para>For convenience, we have decided to leave the debug timestamp in the logs with the <literal>debug</literal> <literal>timestamp</literal> option, which is the default behavior. This will place a timestamp next to each message in the logging file. If we were not interested in this information, we could specify <literal>no</literal> for this option instead.</para>
-
-
-<sect2 role="" label="4.8.1" id="ch04-97929">
-<title>Using syslog</title>
-
-
-<para>If you wish to use the system logger (<filename>syslog </filename>
-<indexterm id="ch04-idx-967351-0"><primary>SYSLOG utility</primary></indexterm>) in addition to or in place of the standard Samba logging file, Samba provides options for this as well. However, to use <filename>syslog</filename>, the first thing you will have to do is make sure that Samba was built with the <literal>configure</literal> <literal>--with-syslog</literal> option. See <link linkend="SAMBA-CH-2">Chapter 2</link> for more information on configuring and compiling Samba.</para>
-
-
-<para>Once that is done, you will need to configure your <filename>/etc/syslog.conf</filename> to accept logging information from Samba. If there is not already a <literal>daemon.*</literal> entry in the <replaceable>/etc/syslog.conf</replaceable> file, add the following:</para>
-
-
-<programlisting>daemon.* /var/log/daemon.log</programlisting>
-
-
-<para>This specifies that any logging information from system daemons will be stored in the <filename>/var/log/daemon.log</filename> file. This is where the Samba information will be stored as well. From there, you can specify the following global option in your configuration file:</para>
-
-
-<programlisting>syslog = 2</programlisting>
-
-
-<para>This specifies that any logging messages with a level of 1 will be sent to both the <filename>syslog</filename> and the Samba logging files. (The mappings to <filename>syslog</filename> priorities are described in the upcoming <link linkend="ch04-78696">Section 4.8.2.5</link>.) Let's assume that we set the regular <literal>log</literal> <literal>level</literal> option above to 4. Any logging messages with a level of 2, 3, or 4 will be sent to the Samba logging files, but not to the <filename>syslog</filename>. Only level 1 logging messages will be sent to both. If the <literal>syslog</literal> value exceeds the <literal>log</literal> <literal>level</literal> value, nothing will be written to the <filename>syslog</filename>.</para>
-
-
-<para>If you want to specify that messages be sent only to <filename>syslog</filename>—and not to the standard Samba logging files—you can place this option in the configuration file:</para>
-
-
-<programlisting>syslog only = yes</programlisting>
-
-
-<para>If this is the case, any logging information above the number specified in the <literal>syslog</literal> option will be discarded, just like the <literal>log</literal> <literal>level</literal> option.</para>
-</sect2>
-
-
-
-
-<sect2 role="" label="4.8.2" id="ch04-SECT-8.1">
-<title>Logging Configuration Options</title>
-
-
-<para><link linkend="ch04-92838">Table 4.7</link> lists each of the<indexterm id="ch04-idx-967341-0"><primary>log files/logging</primary><secondary>configuration options</secondary><tertiary>list of</tertiary></indexterm> logging configuration options that Samba can use.</para>
-
-
-<table label="4.7" id="ch04-92838">
-<title>Global Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>log file</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified filename)</para></entry>
-
-<entry colname="col3"><para>Sets the name and location of the log file that Samba is to use. Uses standard variables.</para></entry>
-
-<entry colname="col4"><para>Specified in Samba makefile</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>log level</literal></para>
-
-<para><literal>(debug level)</literal></para></entry>
-
-<entry colname="col2"><para>numerical (0-10)</para></entry>
-
-<entry colname="col3"><para>Sets the amount of log/debug messages that are sent to the log file. 0 is none, 3 is considerable.</para></entry>
-
-<entry colname="col4"><para><literal>1</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max log size</literal></para></entry>
-
-<entry colname="col2"><para>numerical (size in KB)</para></entry>
-
-<entry colname="col3"><para>Sets the maximum size of log file. After the log exceeds this size, the file will be renamed to <emphasis>.bak</emphasis> and a new log file started.</para></entry>
-
-<entry colname="col4"><para><literal>5000</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>debug</literal></para>
-
-<para><literal>timestamp (timestamp logs)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If no, doesn't timestamp logs, making them easier to read during heavy debugging.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>syslog</literal></para></entry>
-
-<entry colname="col2"><para>numerical (0-10)</para></entry>
-
-<entry colname="col3"><para>Sets level of messages sent to <emphasis>syslog</emphasis>. Those levels below <literal>syslog level</literal> will be sent to the system logger.</para></entry>
-
-<entry colname="col4"><para><literal>1</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>syslog only</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If yes, uses <emphasis>syslog</emphasis> entirely and sends no output to the standard Samba log files.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="4.8.2.1" id="ch04-log-file-option">
-<title>log file</title>
-
-
-<para>On our server, Samba outputs log information to text files in the <filename>var</filename> subdirectory of the Samba home directory, as set by the makefile during the build. The <literal>log</literal> <literal>file</literal> option can be used to reset the name of the log file to another location. For example, to reset the name and location of the Samba log file to <filename>/usr/local/logs/samba.log</filename>, you could use the following:</para>
-
-
-<programlisting>[global]
- log file = /usr/local/logs/samba.log</programlisting>
-
-
-<para>You may use variable substitution to create log files specifically for individual users or clients.</para>
-
-
-<para>You can override the default log file location using the <literal>-l</literal> command-line switch when either daemon is started. However, this does not override the <literal>log</literal> <literal>file</literal> option. If you do specify this parameter, initial logging information will be sent to the file specified after <literal>-l</literal> (or the default specified in the Samba makefile) until the daemons have processed the <filename>smb.conf</filename> file and know to redirect it to a new log file.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.8.2.2" id="ch04-SECT-8.1.2">
-<indexterm id="ch04-idx-968338-0"><primary>log level option</primary></indexterm>
-<title>
-log level</title>
-
-
-<para>The <literal>log</literal> <literal>level</literal> option sets the amount of data to be logged. Normally this is left at 0 or 1. However, if you have a specific problem you may want to set it at 3, which provides the most useful debugging information you would need to track down a problem. Levels above 3 provide information that's primarily for the developers to use for chasing internal bugs, and slows down the server considerably. Therefore, we recommend that you avoid setting this option to anything above 3.</para>
-
-
-<programlisting>[global]
-log file = /usr/local/logs/samba.log.%m
-log level = 3</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="4.8.2.3" id="ch04-SECT-8.1.3">
-<indexterm id="ch04-idx-968341-0"><primary>max log size option</primary></indexterm>
-<title>
-max log size</title>
-
-
-<para>The <literal>max</literal> <literal>log</literal> <literal>size</literal> option sets the maximum size, in kilobytes, of the debugging log file that Samba keeps. When the log file exceeds this size, the current log file is renamed to add an <emphasis>.old</emphasis> extension (erasing any previous file with that name) and a new debugging log file is started with the original name. For example:</para>
-
-
-<programlisting>[global]
-log file = /usr/local/logs/samba.log.%m
-max log size = 1000</programlisting>
-
-
-<para>Here, if the size of any log file exceeds one megabyte in size, Samba renames the log file <emphasis>samba.log.</emphasis> <replaceable>machine-name</replaceable><emphasis>.old</emphasis> and a new log file is generated. If there was a file there previously with the <emphasis>.old</emphasis> extension, Samba deletes it. We highly recommend setting this option in your configuration files because debug logging (even at lower levels) can covertly eat away at your available disk space. Using this option protects unwary administrators from suddenly discovering that most of their disk space has been swallowed up by a single Samba log file.</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.8.2.4" id="ch04-SECT-8.1.4">
-<indexterm id="ch04-idx-968344-0"><primary>debug timestamp option</primary></indexterm>
-<indexterm id="ch04-idx-968344-1"><primary>timestamp logs option</primary></indexterm>
-<title>
-
-;debug timestamp or timestamp logs</title>
-
-
-<para>If you happen to be debugging a network problem and you find that the date-stamp and timestamp information within the Samba log lines gets in the way, you can turn it off by giving either the <literal>timestamp</literal> <literal>logs</literal> or the <literal>debug</literal> <literal>timestamp</literal> option (they're synonymous) a value of <literal>no</literal>. For example, a regular Samba log file presents its output in the following form:</para>
-
-
-<programlisting>12/31/98 12:03:34 hydra (192.168.220.101) connect to server network as user davecb</programlisting>
-
-
-<para>With a <literal>no</literal> value for this option, the output would appear without the datestamp or the timestamp:</para>
-
-
-<programlisting>hydra (192.168.220.101) connect to server network as user davecb</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="4.8.2.5" id="ch04-78696">
-<title>syslog</title>
-
-
-<para>
-<indexterm id="ch04-idx-967365-0"><primary>Unix</primary><secondary>options</secondary><tertiary sortas="system logger">for system logger</tertiary></indexterm>The <literal>syslog</literal>
-<indexterm id="ch04-idx-968349-0"><primary>syslog option</primary></indexterm> option causes Samba log messages to be sent to the Unix system logger. The type of log information to be sent is specified as the parameter for this argument. Like the <literal>log</literal> <literal>level</literal> option, it can be a number from 0 to 10. Logging information with a level less than the number specified will be sent to the system logger. However, debug logs equal to or above the <literal>syslog</literal> level, but less than log level, will still be sent to the standard Samba log files. To get around this, use the <literal>syslog</literal> <literal>only</literal> option. For example:</para>
-
-
-<programlisting>[global]
- log level = 3
- syslog = 1</programlisting>
-
-
-<para>With this, all logging information with a level of 0 would be sent to the standard Samba logs and the system logger, while information with levels 1, 2, and 3 would be sent only to the standard Samba logs. Levels above 3 are not logged at all. Note that all messages sent to the system logger are mapped to a priority level that the <emphasis>syslog</emphasis> process understands, as shown in <link linkend="ch04-80576">Table 4.8</link>. The default level is 1.</para>
-
-
-<table label="4.8" id="ch04-80576">
-<title>Syslog Priority Conversion </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Log Level</para></entry>
-
-<entry colname="col2"><para>Syslog Priority</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>0</para></entry>
-
-<entry colname="col2"><para><literal>LOG_ERR</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>1</para></entry>
-
-<entry colname="col2"><para><literal>LOG_WARNING</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>2</para></entry>
-
-<entry colname="col2"><para><literal>LOG_NOTICE</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>3</para></entry>
-
-<entry colname="col2"><para><literal>LOG_INFO</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>4 and above</para></entry>
-
-<entry colname="col2"><para><literal>LOG_DEBUG</literal></para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>If you wish to use <emphasis>syslog</emphasis>, you will have to run <literal>configure</literal> <literal>--with-syslog</literal> when compiling Samba, and you will need to configure your <filename>/etc/syslog.conf</filename> to suit. (See <link linkend="ch04-97929">Section 4.8.1</link> earlier in this chapter.)</para>
-</sect3>
-
-
-
-<sect3 role="" label="4.8.2.6" id="ch04-SECT-8.1.6">
-<indexterm id="ch04-idx-968350-0"><primary>syslog only option</primary></indexterm>
-<title>
-syslog only</title>
-
-
-<para>The <literal>syslog</literal> <literal>only</literal> option tells Samba not to use the regular logging files—the system logger only. To enable this, specify the following option in the global ection of the Samba configuration file:</para>
-
-
-<programlisting>[global]
- syslog only = <indexterm id="ch04-idx-967342-0" class="endofrange" startref="ch04-idx-967340-0"/>
-<indexterm id="ch04-idx-967342-1" class="endofrange" startref="ch04-idx-967340-1"/>yes<indexterm id="ch04-idx-967031-0" class="endofrange" startref="ch04-idx-967030-0"/></programlisting>
-</sect3>
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="5" id="SAMBA-CH-5">
-<title>Browsing and Advanced Disk Shares </title>
-
-
-
-
-<para>
-<indexterm id="ch05-idx-969559-0" class="startofrange"><primary>browsing</primary></indexterm>
-<indexterm id="ch05-idx-969559-1" class="startofrange"><primary>disk shares</primary><secondary>advanced</secondary></indexterm>This chapter continues our discussion of disk shares from the previous chapter. Here, we will discuss various differences between the Windows and Unix filesystems—and how Samba works to bridge the gap. There are a surprising number of inconsistencies between a DOS filesystem and a Unix filesystem. In addition, we will talk briefly about name mangling, file locking, and a relatively new feature for Samba: opportunistic locking, or oplocks. However, before we move into that territory, we should first discuss the somewhat arcane topic of browsing with Samba.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="5.1" id="ch05-23763">
-<title>Browsing</title>
-
-
-<para>Browsing is the ability to examine the servers and <indexterm id="ch05-idx-969575-0"><primary>shares</primary><secondary>viewing</secondary><see>browsing</see></indexterm>shares that are currently available on your network. On a Windows NT 4.0 or 95/98 client, a user can browse network servers through the Network Neighborhood folder. By double-clicking the icon representing the server, the user should be able to see the printer and disk share resources available on that machine as well. (If you have Windows NT 3.<emphasis>x</emphasis>, you can use the Disk-Connect Network Drive menu in the File Manager to display the available shares on a server.)</para>
-
-
-<para>From the Windows command line, you can also use the <literal>net</literal> <literal>view</literal> option to see which servers are currently on the network. Here is an example of the <literal>net</literal> <literal>view</literal> command in action:</para>
-
-
-<programlisting>C:\><userinput>net view</userinput>
-Servers available in workgroup SIMPLE
-Server name Remark
-----------------------------------------------------------
-\\CHIMAERA Windows NT 4.0
-\\HYDRA Samba 2.0.4 on (hydra)
-\\PHOENIX Windows 98</programlisting>
-
-
-<sect2 role="" label="5.1.1" id="ch05-SECT-1.1">
-<title>Preventing Browsing</title>
-
-
-<para>
-<indexterm id="ch05-idx-969576-0"><primary>browsing</primary><secondary>preventing</secondary></indexterm>
-<indexterm id="ch05-idx-969576-1"><primary>preventing browsing</primary></indexterm>
-<indexterm id="ch05-idx-969576-2"><primary>browse lists</primary><secondary>restricting shares from</secondary></indexterm>
-<indexterm id="ch05-idx-969576-3"><primary>shares</primary><secondary>contents, restricting view of</secondary></indexterm>You can restrict a share from being in a browse list by using the <literal>browseable</literal> option. This boolean option prevents a share from being seen in the Network Neighborhood at all. For example, to prevent the <literal>[data]</literal> share from the previous chapter from being visible, we could write:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = no
- guest ok = yes
- comment = Data Drive
- volume = Sample-Data-Drive
- writeable = yes</programlisting>
-
-
-<para>Although you typically don't want to do this to an ordinary disk share, the browseable option is useful in the event that you need to create a share with contents that you do not want others to see, such as a <literal>[netlogin]</literal> share for storing logon scripts for Windows domain control (see <link linkend="SAMBA-CH-6">Chapter 6</link> for more information on logon scripts).</para>
-
-
-<para>Another example is the <literal>[homes]</literal> share. This share is often marked non-browsable so that a share named <literal>[homes]</literal> won't appear when its machine's resources are browsed. However, if a user <literal>alice</literal> logs on and looks at the machine's shares, an <literal>[alice]</literal> share will appear under the machine. What if we wanted to make sure <literal>alice</literal>'s share appeared to everyone before she logs in? This could be done with the global <literal>auto</literal> <literal>services</literal> option. This option preloads shares into the browse list to ensure that they are always visible:</para>
-
-
-<programlisting>[global]
- ...
- auto services = alice
- ...</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.1.2" id="ch05-SECT-1.2">
-<title>Default Services</title>
-
-
-<para>In the event that a user cannot successfully connect to a share, you can specify a default <indexterm id="ch05-idx-969587-0"><primary>shares</primary><secondary>default</secondary></indexterm>
-<indexterm id="ch05-idx-969587-1"><primary>default services</primary></indexterm>share to which they can connect. Since you do not know who will default to this share at any time, you will probably want to set the <literal>guest</literal> <literal>ok</literal> option to <literal>yes</literal> for this share. Specifying a <literal>default</literal> <literal>service</literal> can be useful when sending the utterly befuddled to a directory of help files. For example:</para>
-
-
-<programlisting>[global]
- ...
- default service = helpshare
- ...
-
-[helpshare]
- path = /home/samba/helpshare/%S
- browseable = yes
- guest ok = yes
- comment = Default Share for Unsuccessful Connections
- volume = Sample-Data-Drive
- writeable = no</programlisting>
-
-
-<para>Note that we used the <literal>%S</literal> variable in the <literal>path</literal> option. If you use the <literal>%S</literal> variable, it will refer to the requested nonexistent share (the original share requested by the user), not the name of the resulting default share. This allows us to create different paths with the names of each server, which can provide more customized help files for users. In addition, any <indexterm id="ch05-idx-969588-0"><primary>underscore ( _ ) in shares</primary></indexterm>
-<indexterm id="ch05-idx-969588-1"><primary>_ underscore</primary></indexterm>underscores ( _ ) specified in the requested share will be converted to<indexterm id="ch05-idx-969589-0"><primary>slash (/)</primary><secondary>in shares</secondary></indexterm>
-<indexterm id="ch05-idx-969589-1"><primary>/ (slash) in shares</primary></indexterm> slashes ( / ) when the <literal>%S</literal> variable is used.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.1.3" id="ch05-SECT-1.3">
-<title>Browsing Elections</title>
-
-
-<para>
-<indexterm id="ch05-idx-969892-0" class="startofrange"><primary>browsing</primary><secondary>elections</secondary></indexterm>As mentioned in <link linkend="ch01-48078">Chapter 1</link>, one machine in each subnet always keeps a list of the currently active <indexterm id="ch05-idx-969897-0"><primary>servers</primary><secondary>active, list of</secondary></indexterm>machines. This list is called the <firstterm>browse list</firstterm>
-<indexterm id="ch05-idx-969898-0"><primary>browse lists</primary></indexterm> and the server that maintains it is called the <indexterm id="ch05-idx-970543-0" class="startofrange"><primary>local master browser</primary></indexterm><firstterm>local master browser</firstterm>. As machines come on and off the network, the local master browser continually updates the information in the browse list and provides it to any machine that requests it.</para>
-
-
-<para>A computer becomes a local master browser by holding a browsing election on the local subnet. Browsing elections can be called at any time. Samba can rig a browsing election for a variety of outcomes, including always becoming the local master browser of the subnet or never becoming it. For example, the following options, which we've added to the configuration file from <link linkend="ch04-21486">Chapter 4</link>, will ensure that Samba always wins the election for local master browser no matter which machines are also present:</para>
-
-
-<programlisting>[global]
- netbios name = HYDRA
- server string = Samba %v on (%L)
- workgroup = SIMPLE
-
- # Browsing election options
- os level = 34
- local master = yes
-
- # Networking configuration options
- hosts allow = 192.168.220. 134.213.233. localhost
- hosts deny = 192.168.220.102
- interfaces = 192.168.220.100/255.255.255.0 \
- 134.213.233.110/255.255.255.0
-
- # Debug logging information
- log level = 2
- log file = /var/log/samba.log.%m
- max log size = 50
- debug timestamp = yes
-
-[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- comment = Data Drive
- volume = Sample-Data-Drive
- writable = yes</programlisting>
-
-
-<para>However, what if we didn't always want to win the election? What if we wanted to yield browsing to a Windows NT Server if present? In order to do that, we need to learn how browsing elections work. As you already know, each machine that takes place in the election must broadcast information about itself. This information includes the following:</para>
-
-
-<itemizedlist>
-<listitem><para>The version of the election protocol used</para></listitem>
-<listitem><para>The operating system on the machine</para></listitem>
-<listitem><para>The amount of time the client has been on the network</para></listitem>
-<listitem><para>The hostname of the client</para></listitem>
-</itemizedlist>
-
-<para>Here is how the election is decided. Operating systems are assigned a binary value according to their version, as shown in <link linkend="ch05-51423">Table 5.1</link>.</para>
-
-
-<table label="5.1" id="ch05-51423">
-<title>Operating System Values in an Election </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Operating System</para></entry>
-
-<entry colname="col2"><para>Value</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>
-<indexterm id="ch05-idx-969634-0"><primary>operating systems</primary><secondary>values in elections</secondary></indexterm>
-<indexterm id="ch05-idx-969634-1"><primary>elections</primary><secondary>operating system values in</secondary></indexterm>Windows NT Server 4.0</para></entry>
-
-<entry colname="col2"><para>33</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows NT Server 3.51</para></entry>
-
-<entry colname="col2"><para>32</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows NT Workstation 4.0</para></entry>
-
-<entry colname="col2"><para>17</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows NT Workstation 3.51</para></entry>
-
-<entry colname="col2"><para>16</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 98</para></entry>
-
-<entry colname="col2"><para>2</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 95</para></entry>
-
-<entry colname="col2"><para>1</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 3.1 for Workgroups</para></entry>
-
-<entry colname="col2"><para>1</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Following that, each computer on the network is assigned a separate value according to its role, as shown in <link linkend="SAMBA-CH-5-TBL-5.2">Table 5.2</link>.</para>
-
-
-<table label="5.2" id="SAMBA-CH-5-TBL-5.2">
-<title>Computer Role Settings in an Election </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Role</para></entry>
-
-<entry colname="col2"><para>Value</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>
-<indexterm id="ch05-idx-969635-0"><primary>Windows clients</primary><secondary>role settings in elections</secondary></indexterm>
-<indexterm id="ch05-idx-969635-1"><primary>elections</primary><secondary>role settings in</secondary></indexterm>
-<indexterm id="ch05-idx-969635-2"><primary>role settings in elections</primary></indexterm>
-<indexterm id="ch05-idx-969635-3"><primary>role settings in elections</primary></indexterm>Primary Domain Controller</para></entry>
-
-<entry colname="col2"><para>128</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>WINS Client</para></entry>
-
-<entry colname="col2"><para>32</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Preferred Master Browser</para></entry>
-
-<entry colname="col2"><para>8</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Active Master Browser</para></entry>
-
-<entry colname="col2"><para>4</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Standby Browser</para></entry>
-
-<entry colname="col2"><para>2</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Active Backup Browser</para></entry>
-
-<entry colname="col2"><para>1</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>
-<indexterm id="ch05-idx-969637-0"><primary>elections</primary><secondary>order of decisions in</secondary></indexterm>Elections are decided in the following order:</para>
-
-
-<orderedlist>
-<listitem><para>The machine with the highest version of the election protocol will win. (So far, this is meaningless, as all Windows clients have version 1 of the election protocol.)</para></listitem>
-<listitem><para>The machine with the highest operating system value wins the election.</para></listitem>
-<listitem><para>If there is a tie, the machine with the setting of Preferred Master Browser (role 8) wins the election.</para></listitem>
-<listitem><para>If there is still a tie, the client who has been online the longest wins the election.</para></listitem>
-<listitem><para>And finally, if there is still a tie, the client name that comes first alphabetically wins.</para></listitem>
-<listitem><para>The machine that is the "runner-up" can become a backup browser.</para></listitem>
-</orderedlist>
-
-<para>As a result, if you want Samba to take the role of a local master browser, but only if there isn't a Windows NT Server (4.0 or 3.51) on the network, you could change the <literal>os</literal> <literal>level</literal> parameter in the previous example to:</para>
-
-
-<programlisting>os level = 31</programlisting>
-
-
-<para>This will cause Samba to immediately lose the election to a Windows NT 4.0 or Windows NT 3.5 Server, both of which have a higher operating systems level. On the other hand, if you wanted to decide the local master browser on the basis of the network role, such as which machine is the primary domain controller, you could set the <literal>os</literal> <literal>level</literal> to match the highest type of operating system on the network and let the election protocol fall down to the next level.</para>
-
-
-<para>
-<indexterm id="ch05-idx-969646-0"><primary>local master browser</primary><secondary>checking machines for</secondary></indexterm>How can you can tell if a machine is a local master browser? By using the <literal>nbtstat</literal> command. Place the NetBIOS name of the machine you wish to check after the <literal>-a</literal> option:</para>
-
-
-<programlisting>C:\><userinput>nbtstat -a hydra</userinput>
-
- NetBIOS Remote Machine Name Table
-
- Name Type Status
-----------------------------------------------------------
- HYDRA <00> UNIQUE Registered
- HYDRA <03> UNIQUE Registered
- HYDRA <20> UNIQUE Registered
- .._ _MSBROWSE_ _. <01> GROUP Registered
- SIMPLE <00> GROUP Registered
- SIMPLE <1D> UNIQUE Registered
- SIMPLE <1E> GROUP Registered
-
- MAC Address = 00-00-00-00-00-00</programlisting>
-
-
-<para>The resource entry that you're looking for is the <literal>.._ _MSBROWSE_ _.<01></literal>. This indicates that the server is currently acting as the local master browser for the current subnet. In addition, if the machine is a Samba server, you can check the Samba <filename>nmbd</filename> log file for an entry such as:</para>
-
-
-<programlisting>nmbd/nmbd_become_lmb.c:become_local_master_stage2(406)
-*****
-Samba name server HYDRA is now a local master browser for
-workgroup SIMPLE on subnet 192.168.220.100
-****</programlisting>
-
-
-<para>Finally, Windows NT servers serving as primary domain controllers contain a sneak that allows them to assume the role of the local master browser in certain conditions; this is called the <emphasis>preferred</emphasis>
-<indexterm id="ch05-idx-969647-0"><primary>preferred master browser</primary></indexterm> <emphasis>master browser</emphasis> bit. Earlier, we mentioned that Samba could set this bit on itself as well. You can enable it with the <literal>preferred</literal> <literal>master</literal> option:</para>
-
-
-<programlisting># Browsing election options
-os level = 33
-local master = yes
-preferred master = yes</programlisting>
-
-
-<para>If the preferred master bit is set, the machine will force a browsing election at startup. Of course, this is needed only if you set the <literal>os</literal> <literal>level</literal> option to match the Windows NT machine. We recommend that you don't use this option if another machine also has the role of preferred master, such as an NT server.<indexterm id="ch05-idx-969633-0" class="endofrange" startref="ch05-idx-969892-0"/></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.1.4" id="ch05-SECT-1.4">
-<title>Domain Master Browser</title>
-
-
-<para>
-<indexterm id="ch05-idx-969654-0" class="startofrange"><primary>DMB (domain master browser)</primary></indexterm>
-<indexterm id="ch05-idx-969654-1"><primary>domain master browser</primary><see>DMB</see></indexterm>
-<indexterm id="ch05-idx-969654-2"><primary>domains</primary><secondary>controllers</secondary><see>domain controllers</see></indexterm>In the opening chapter, we mentioned that in order for a Windows workgroup or domain to extend into multiple subnets, one machine would have to take the role of the <firstterm>domain master browser</firstterm>. The domain master browser propagates browse lists across each of the subnets in the workgroup. This works because each local master browser periodically synchronizes its browse list with the domain master browser. During this synchronization, the local master browser passes on any server that the domain master browser does not have in its browse list, and vice versa. In a perfect world, each local master browser would eventually have the browse list for the entire domain.</para>
-
-
-<para>Unlike the local master browser, there is no election to determine which machine assumes the role of the domain master browser. Instead, the administrator has to set it manually. By Microsoft design, however, the domain master browser and the primary domain controller (PDC) both register a resource type of <1B>, so the roles—and the machines—are inseparable.</para>
-
-
-<para>If you have a <indexterm id="ch05-idx-969663-0"><primary>Windows NT</primary><secondary>server, domain master browser and</secondary></indexterm>Windows NT server on the network acting as a PDC, we recommend that you do not use Samba to become the domain master browser. The reverse is true as well: if Samba is taking on the responsibilities of a <indexterm id="ch05-idx-969665-0"><primary>PDC (primary domain controller)</primary><secondary>domain master browser and</secondary></indexterm>PDC, we recommend making it the domain master browser as well. Although it is possible to split the roles with Samba, this is not a good idea. Using two different machines to serve as the PDC and the domain master browser can cause random errors to occur on a Windows workgroup.</para>
-
-
-<para>Samba can assume the role of a domain master browser for all subnets in the workgroup with the following option:</para>
-
-
-<programlisting>domain master = yes</programlisting>
-
-
-<para>You can verify that a Samba machine is in fact the domain master browser by checking the <emphasis>nmbd</emphasis> log file:</para>
-
-
-<programlisting>nmbd/nmbd_become_dmb.c:become_domain_master_stage2(118)
-*****
-Samba name server HYDRA is now a domain master browser for
-workgroup SIMPLE on subnet 192.168.220.100
-*****</programlisting>
-
-
-<para>Or you can use the <literal>nmblookup</literal> command that comes with the Samba distribution to query for a unique <1B> resource type in the workgroup:</para>
-
-
-<programlisting># <userinput>nmblookup SIMPLE#1B</userinput>
-Sending queries to 192.168.220.255
-192.168.220.100 SIMPLE<1b></programlisting>
-
-
-<sect3 role="" label="5.1.4.1" id="ch05-SECT-1.4.1">
-<title>Multiple subnets</title>
-
-
-<para>
-<indexterm id="ch05-idx-969667-0"><primary>multiple subnets</primary></indexterm>There are three rules that you must remember when creating a workgroup/domain that spans more than one subnet:</para>
-
-
-<itemizedlist>
-<listitem><para>You must have either a Windows NT or Samba machine acting as a local master browser on each subnet in the workgroup/domain. (If you have a domain master browser in a subnet, a local master browser is not needed.)</para></listitem>
-<listitem><para>You must have a Windows NT Server or a Samba machine acting as a domain master browser somewhere in the workgroup.</para></listitem>
-<listitem><para>Each local master browser must be instructed to synchronize with the domain master browser.</para></listitem>
-</itemizedlist>
-
-<para>Samba has a few other features in this arena in the event that you don't have or want a domain master browser on your network. Consider the subnets shown in <link linkend="ch05-15706">Figure 5.1</link>.</para>
-
-
-<figure label="5.1" id="ch05-15706">
-<title>Multiple subnets with Samba servers</title>
-
-<graphic width="502" depth="325" fileref="figs/sam.0501.gif"></graphic>
-</figure>
-
-<para>First, a Samba server that is a local master browser can use the <literal>remote</literal> <literal>announce</literal> configuration option to make sure that computers in different subnets are sent broadcast announcements about the server. This has the effect of ensuring that the Samba server appears in the browse lists of foreign subnets. To achieve this, however, the directed broadcasts must reach the local master browser on the other subnet. Be aware that many routers do not allow directed broadcasts by default; you may have to change this setting on the router for the directed broadcasts to get through to its subnet.</para>
-
-
-<para>With the <literal>remote</literal> <literal>announce</literal> option, list the subnets and the workgroup that should receive the broadcast. For example, to ensure that machines in the 192.168.221 and 192.168.222 subnets and SIMPLE workgroup are sent broadcast information from our Samba server, we could specify the following:</para>
-
-
-<programlisting># Browsing election options
-os level = 34
-local master = yes
-remote announce = 192.168.221.255/SIMPLE \
- 192.168.222.255/SIMPLE</programlisting>
-
-
-<para>In addition, you are allowed to specify the exact address to send broadcasts to if the local master browser on the foreign subnet is guaranteed to always have a fixed IP address.</para>
-
-
-<para>A Samba local master browser can synchronize its browse list directly with another Samba server acting as a local master browser on a different subnet. For example, let's assume that Samba is configured as a local master browser, and Samba local master browsers exist at 192.168.221.130 and 192.168.222.120. We can use the <literal>remote</literal> <literal>browse</literal> <literal>sync</literal> option to sync directly with the Samba servers, as follows:</para>
-
-
-<programlisting># Browsing election options
-os level = 34
-local master = yes
-remote browse sync = 192.168.221.130 192.168.222.120</programlisting>
-
-
-<para>In order for this to work, the other Samba machines must also be local master browsers. You can also use directed broadcasts with this option if you do not know specific IP addresses of local master browsers.<indexterm id="ch05-idx-969939-0" class="endofrange" startref="ch05-idx-969654-0"/>
-<indexterm id="ch05-idx-969940-0" class="endofrange" startref="ch05-idx-970543-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.1.5" id="ch05-SECT-1.5">
-<title>Browsing Options</title>
-
-
-<para>
-<indexterm id="ch05-idx-969668-0" class="startofrange"><primary>browsing</primary><secondary>configuration options for</secondary></indexterm>
-<indexterm id="ch05-idx-969668-1" class="startofrange"><primary>configuration options</primary><secondary>browsing</secondary></indexterm><link linkend="ch05-81028">Table 5.3</link> shows 14 options that define how Samba handles browsing tasks. We recommend the defaults for a site that prefers to be easy on its users with respect to locating shares and printers.</para>
-
-
-<table label="5.3" id="ch05-81028">
-<title>Browsing Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>browseable (browsable)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Allows share to be displayed in list of machine resources.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>browse list</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba will provide a browse list on this server.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>auto services (preload)</literal></para></entry>
-
-<entry colname="col2"><para>string (share list)</para></entry>
-
-<entry colname="col3"><para>Sets a list of shares that will always appear in the browse list.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>default service (default)</literal></para></entry>
-
-<entry colname="col2"><para>string (share name)</para></entry>
-
-<entry colname="col3"><para>Names a share (service) that will be provided if the client requests a share not listed in <emphasis>smb.conf.</emphasis></para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>local master</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba will try to become a master browser on the local subnet.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lm announce</literal></para></entry>
-
-<entry colname="col2"><para><literal>yes</literal> or <literal>no</literal> or <literal>auto</literal></para></entry>
-
-<entry colname="col3"><para>Enables or disables LAN Manager style host announcements.</para></entry>
-
-<entry colname="col4"><para><literal>auto</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lm interval</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Specifies the frequency in seconds that LAN Manager announcements will be made if activated.</para></entry>
-
-<entry colname="col4"><para><literal>60</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>preferred master (prefered master)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba will use the preferred master browser bit to attempt to become the local master browser.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>domain master</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba will try to become the main browser master for the workgroup.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>os level</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Sets the operating system level of Samba in an election for local master browser.</para></entry>
-
-<entry colname="col4"><para><literal>0</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>remote browse sync</literal></para></entry>
-
-<entry colname="col2"><para>string (list of IP addresses)</para></entry>
-
-<entry colname="col3"><para>Lists Samba servers to synchronize browse lists with.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>remote announce</literal></para></entry>
-
-<entry colname="col2"><para>string (IP address/ workgroup pairs)</para></entry>
-
-<entry colname="col3"><para>Lists subnets and workgroups to send directed broadcast packets to, allowing Samba to appear to browse lists.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="5.1.5.1" id="ch05-SECT-1.5.1">
-<indexterm id="ch05-idx-970552-0"><primary>announce as option</primary></indexterm>
-<title>
-announce as</title>
-
-
-<para>This global configuration option specifies the type of operating system that Samba will announce to other machines on the network. The default value for this option is <literal>N T</literal>, which represents a Windows NT operating system. Other possible values are <literal>Win95</literal>, which represents a Windows 95 operating system, and <literal>W f W</literal> for a Windows for Workgroup operating system. You can override the default value with the following:</para>
-
-
-<programlisting>[global]
- announce as = Win95</programlisting>
-
-
-<para>We recommend against changing the default value of this configuration option.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.2" id="ch05-SECT-1.5.2">
-<indexterm id="ch05-idx-970555-0"><primary>announce version option</primary></indexterm>
-<title>
-announce version</title>
-
-
-<para>This global option is frequently used with the <literal>announce</literal> <literal>as</literal> configuration option; it specifies the version of the operating system that Samba will announce to other machines on the network. The default value of this options is 4.2, which places itself above the current Windows NT version of 4.0. You can specify a new value with a global entry such as the following:</para>
-
-
-<programlisting>[global]
- announce version = 4.3</programlisting>
-
-
-<para>We recommend against changing the default value of this configuration option.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.3" id="ch05-38345">
-<title>browseable</title>
-
-
-<para>The <literal>browseable</literal> option (also spelled <literal>browsable</literal>) indicates whether the share referenced should appear in the list of available resources of the machine on which it resides. This option is always set to <literal>yes</literal> by default. If you wish to prevent the share from being seen in a client's browser, you can reset this option to <literal>no</literal>.</para>
-
-
-<para>Note that this does not prevent someone from accessing the share using other means, such as specifying a UNC location (<literal>//server/accounting)</literal> in Windows Explorer. It only prevents the share from being listed under the machine's resources when being browsed.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.4" id="ch05-SECT-1.5.4">
-<title>browse list</title>
-
-
-<para>
-<indexterm id="ch05-idx-969674-0"><primary>browse lists</primary><secondary>options for</secondary></indexterm>You should never need to change this parameter from its default value of <literal>yes</literal>. If your Samba server is acting as a local master browser (i.e., it has won the browsing election), you can use the global <literal>browse</literal> <literal>list</literal> option to instruct Samba to provide or withhold its browse list to all clients. By default, Samba always provides a browse list. You can withhold this information by specifying the following:</para>
-
-
-<programlisting>[global]
- browse list = no</programlisting>
-
-
-<para>If you disable the browse list, clients cannot browse the names of other machines, their services, and other domains currently available on the network. Note that this won't make any particular machine inaccessible; if someone knows a valid machine name/address and a share on that machine, they can still connect to it explicitly using NET USE or by mapping a drive letter to it using Windows Explorer. It simply prevents information in the browse list from being retrieved by any client that requests it.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.5" id="ch05-SECT-1.5.5">
-<title>auto services</title>
-
-
-<para>The global <literal>auto</literal>
-<indexterm id="ch05-idx-970563-0"><primary>auto services option</primary></indexterm> <literal>services</literal> option, which is also called <literal>preload </literal>, ensures that the specified shares are always visible in the browse list. One common use for this option is to advertise specific user or printer shares that are created by the <literal>[homes]</literal> or <literal>[printers]</literal> shares, but are not otherwise browsable.</para>
-
-
-<para>This option works best with disk shares. If you wish to force each of your system printers (i.e., those listed in the printer capabilities file) into the browse list using this option, we recommend using the <literal>load</literal> <literal>printers</literal> option instead. Any shares listed with the <literal>auto</literal> <literal>services</literal> option will not be displayed if the <literal>browse</literal> <literal>list</literal> option is set to <literal>no</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.6" id="ch05-SECT-1.5.6">
-<title>default service</title>
-
-
-<para>The global <literal>default</literal>
-<indexterm id="ch05-idx-970564-0"><primary>default services</primary><secondary>option for</secondary></indexterm> <literal>service</literal> option (sometimes called <literal>default</literal>) names a "last-ditch" share. If set to an existing share name, and a client requests a nonexistent disk or printer share, Samba will attempt to connect the user to the share specified by this option instead. The option is specified as follows:</para>
-
-
-<programlisting>default service = helpshare</programlisting>
-
-
-<para>Note that there are no braces surrounding the share name <literal>helpshare</literal>, even though the definition of the share later in the Samba configuration file will have braces. Also, if you use the <literal>%S</literal> variable in the share specified by this option, it will represent the requested, nonexistent share, not the default service. Any underscores ( <literal>_ </literal> ) specified in the request share will be converted to slashes (<literal>/</literal>) when the variable is used.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.7" id="ch05-SECT-1.5.7">
-<indexterm id="ch05-idx-970565-0"><primary>local master option</primary></indexterm>
-<title>
-local master</title>
-
-
-<para>
-<indexterm id="ch05-idx-969675-0"><primary>local master browser</primary><secondary>option for</secondary></indexterm>This global option specifies whether Samba will attempt to become the local master browser for the subnet when it starts up. If this option is set to <literal>yes</literal>, Samba will take place in elections. However, setting this option by itself does not guarantee victory. (Other parameters, such as <literal>preferred</literal> <literal>master</literal> and <literal>os</literal> <literal>level</literal> help Samba win browsing elections.) If this option is set to <literal>no</literal>, Samba will lose all browsing elections, no matter which values are specified by the other configuration options. The default value is <literal>yes</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.8" id="ch05-SECT-1.5.8">
-<title>lm announce</title>
-
-
-<para>The global <literal>lm</literal>
-<indexterm id="ch05-idx-970566-0"><primary>lm announce option</primary></indexterm> <literal>announce</literal> option tells Samba's <emphasis>nmbd</emphasis>
-<indexterm id="ch05-idx-969678-0"><primary>nmbd daemon</primary><secondary>browsing options for</secondary></indexterm> whether or not to send LAN Manager host announcements on behalf of the server. These host announcements may be required by older clients, such as IBM's OS/2 operating system. This announcement allows the server to be added to the browse lists of the client. If activated, Samba will announce itself repetitively at the number of seconds specified by the <literal>lm</literal> <literal>interval</literal> option.</para>
-
-
-<para>This configuration option takes the standard boolean values, <literal>yes</literal> and <literal>no</literal>, which engage or disengage LAN Manager announcements, respectively. In addition, there is a third option, <literal>auto</literal>, which causes <emphasis>nmbd</emphasis> to passively listen for LAN Manager announcements, but not send any of its own initially. If LAN Manager announcements are detected for another machine on the network, <emphasis>nmbd</emphasis> will start sending its own LAN Manager announcements to ensure that it is visible. You can specify the option as follows:</para>
-
-
-<programlisting>[global]
- lm announce = yes</programlisting>
-
-
-<para>The default value is <literal>auto</literal>. You probably won't need to change this value from its default.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.9" id="ch05-SECT-1.5.9">
-<indexterm id="ch05-idx-970567-0"><primary>lm interval option</primary></indexterm>
-<title>
-lm interval</title>
-
-
-<para>This option, which is used in conjunction with <literal>lm</literal> <literal>announce</literal>, indicates the number of seconds <emphasis>nmbd</emphasis> will wait before repeatedly broadcasting LAN Manager-style announcements. Remember that LAN Manager announcements must be activated in order for this option to be used. The default value is 60 seconds. If you set this value to 0, Samba will not send any LAN Manager host announcements, no matter what the value of the <literal>lm</literal> <literal>announce</literal> option. You can reset the value of this option as follows:</para>
-
-
-<programlisting>[global]
- lm interval = 90</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.10" id="ch05-SECT-1.5.10">
-<title>preferred master</title>
-
-
-<para>The <literal>preferred</literal>
-<indexterm id="ch05-idx-970568-0"><primary>preferred master option</primary></indexterm> <literal>master</literal> option requests that Samba set the preferred master bit when participating in an election. This gives the server a higher preferred status in the workgroup than other machines at the same operating system level. If you are configuring your Samba machine to become the local master browser, it is wise to set the following value:</para>
-
-
-<programlisting>[global]
- preferred master = yes</programlisting>
-
-
-<para>Otherwise, you should leave it set to its default, <literal>no</literal>. If Samba is configured as a preferred master browser, it will force an election when it first comes online.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.11" id="ch05-SECT-1.5.11">
-<title>os level</title>
-
-
-<para>The global <literal>os</literal>
-<indexterm id="ch05-idx-970569-0"><primary>os level option</primary></indexterm> <literal>level</literal> option dictates the operating system level at which Samba will masquerade during a browser election. If you wish to have Samba win an election and become the master browser, you can set the level above that of the operating system on your network with the highest current value. The values are shown in <link linkend="ch05-51423">Table 5.1</link> . The default level is 0, which means that Samba will lose all elections. If you wish Samba to win all elections, you can reset its value as follows:</para>
-
-
-<programlisting>os level = 34</programlisting>
-
-
-<para>This means that the server will vote for itself 34 times each time an election is called, which ensures a victory.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.12" id="ch05-SECT-1.5.12">
-<indexterm id="ch05-idx-970570-0"><primary>domain master option</primary></indexterm>
-<title>
-domain master</title>
-
-
-<para>If Samba is the primary domain controller for your workgroup or NT domain, it should also be the <indexterm id="ch05-idx-969682-0"><primary>DMB (domain master browser)</primary><secondary>option for</secondary></indexterm> domain master browser. The domain master browser is a special machine that has the NetBIOS resource type <1B> and is used to propagate browse lists to and from each of the local master browsers in individual subnets across the domain. To force Samba to become the domain master browser, set the following in the <literal>[global]</literal> section of the <filename>smb.conf</filename>:</para>
-
-
-<programlisting>[global]
- domain master = yes</programlisting>
-
-
-<para>If you have a Windows NT server on the network acting as a primary domain controller (PDC), we recommend that you do not use Samba to become the domain master browser. The reverse is true as well: if Samba is taking on the responsibilities of a PDC, we recommend making it the domain master browser. Splitting the PDC and the domain master browser will cause unpredictable errors to occur on the network.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.13" id="ch05-SECT-1.5.13">
-<title>remote browse sync</title>
-
-
-<para>The global <literal>remote</literal>
-<indexterm id="ch05-idx-970571-0"><primary>remote browse sync option</primary></indexterm> <literal>browse</literal> <literal>sync</literal> option specifies that Samba should synchronize its <indexterm id="ch05-idx-969683-0"><primary>browse lists</primary><secondary>options for</secondary></indexterm>browse lists with local master browsers in other subnets. However, the synchronization can occur only with other Samba servers, and not with Windows computers. For example, if your Samba server was a master browser on the subnet 192.168.235, and Samba local master browsers existed on other subnets at 192.168.234.92 and 192.168.236.2, you could specify the following:</para>
-
-
-<programlisting>remote browse sync = 192.168.234.92 192.168.236.2</programlisting>
-
-
-<para>The Samba server would then directly contact the other machines on the address list and synchronize browse lists. You can also say:</para>
-
-
-<programlisting>remote browse sync = 192.168.234.255 192.168.236.255</programlisting>
-
-
-<para>This forces Samba to broadcast queries to determine the IP addresses of the local master browser on each subnet, with which it will then synchronize browse lists. This only works, however, if your router doesn't block directed broadcast requests ending in 255.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.1.5.14" id="ch05-SECT-1.5.14">
-<title>remote announce</title>
-
-
-<para>Samba servers are capable of providing browse lists to foreign subnets with the <literal>remote</literal>
-<indexterm id="ch05-idx-970572-0"><primary>remote announce option</primary></indexterm> <literal>announce</literal> option. This is typically sent to the local master browser of the foreign subnet in question. However, if you do not know the address of the local master browser, you can do the following:</para>
-
-
-<programlisting>[global]
- remote announce = 192.168.234.255/ACCOUNTING \
- 192.168.236.255/ACCOUNTING</programlisting>
-
-
-<para>With this, Samba will broadcast host announcements to all machines on subnets 192.168.234 and 192.168.236, which will hopefully reach the local master browser of the<indexterm id="ch05-idx-969669-0" class="endofrange" startref="ch05-idx-969668-0"/>
-<indexterm id="ch05-idx-969669-1" class="endofrange" startref="ch05-idx-969668-1"/> subnet.<indexterm id="ch05-idx-969569-0" class="endofrange" startref="ch05-idx-969559-0"/> You can also specify exact IP addresses, if they are known.</para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="5.2" id="ch05-34221">
-<title>Filesystem Differences</title>
-
-
-<para>
-<indexterm id="ch05-idx-969684-0" class="startofrange"><primary>filesystems</primary><secondary>differences between</secondary></indexterm>One <indexterm id="ch05-idx-969692-0"><primary>filesystems</primary><seealso>files</seealso></indexterm>of the biggest issues for which Samba has to correct is the difference between Unix and non-Unix filesystems. This includes items such as handling symbolic links, hidden files, and dot files. In addition, file permissions can also be a headache if not accounted for properly. This section describes how to use Samba to make up for some of those annoying differences, and even how to add some new functionality of its own.</para>
-
-
-<sect2 role="" label="5.2.1" id="ch05-SECT-2.1">
-<title>Hiding and Vetoing Files</title>
-
-
-<para>
-<indexterm id="ch05-idx-969693-0"><primary>files</primary><secondary>hidden</secondary></indexterm>
-<indexterm id="ch05-idx-969693-1"><primary>hidden files</primary></indexterm>There are some cases when we need to ensure that a user cannot see or access a file at all. Other times, we don't want to keep a user from accessing a file—we just want to hide it when they view the contents of the directory. On Windows systems, an attribute of files allows them to be hidden from a folder listing. With Unix, the traditional way of hiding files in a directory is to precede them with a <indexterm id="ch05-idx-969701-0"><primary>dot (.) in hidden files</primary></indexterm>
-<indexterm id="ch05-idx-969701-1"><primary>. (dot)</primary></indexterm>dot (.). This prevents items such as configuration files or defaults from being seen when performing an ordinary <literal>ls</literal> command. Keeping a user from accessing a file at all, however, involves working with permissions on files and or directories.</para>
-
-
-<para>The first option we should discuss is the boolean <literal>hide</literal> <literal>dot</literal> <literal>files</literal>. This option does exactly what it says. When set to <literal>yes</literal>, the option treats files beginning with a <indexterm id="ch05-idx-969702-0"><primary>period (.)</primary></indexterm>
-<indexterm id="ch05-idx-969702-1"><primary>. (period)</primary></indexterm>period (.) as hidden. If set to <literal>no</literal>, those files are always shown. The important thing to remember is that the files are only hidden. If the user has chosen to show all hidden files while browsing (e.g., using the Folder Options menu item under the View menu in Windows 98), they will still be able to see the files, as shown in <link linkend="ch05-77260">Figure 5.2</link>.</para>
-
-
-<figure label="5.2" id="ch05-77260">
-<title>Hidden files in the [data] share</title>
-
-<graphic width="502" depth="210" fileref="figs/sam.0502.gif"></graphic>
-</figure>
-
-<para>Instead of simply hiding files beginning with a dot, you can also specify a string pattern to Samba for files to hide, using the <literal>hide</literal> <literal>files</literal> option. For example, let's assume that we specified the following in our example <literal>[data]</literal> share:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- case sensitive = no
- hide files = /*.java/*README*/</programlisting>
-
-
-<para>Each entry for this option must begin, end, or be separated from another with a <indexterm id="ch05-idx-969703-0"><primary>slash (/)</primary><secondary>character</secondary></indexterm>
-<indexterm id="ch05-idx-969703-1"><primary>/ (slash character)</primary></indexterm>slash ( / ) character, even if there is only one pattern listed. This convention allows spaces to appear in filenames. In this example, the share directory would appear as shown in <link linkend="ch05-19743">Figure 5.3</link>. Again, note that we have set the Windows 98 option to view hidden files for the window.</para>
-
-
-<figure label="5.3" id="ch05-19743">
-<title>Hiding files based on filename patterns</title>
-
-<graphic width="502" depth="210" fileref="figs/sam.0503.gif"></graphic>
-</figure>
-
-<para>
-<indexterm id="ch05-idx-969704-0" class="startofrange"><primary>veto files</primary></indexterm>
-<indexterm id="ch05-idx-969704-1" class="startofrange"><primary>files</primary><secondary>veto</secondary></indexterm>If we want to prevent users from seeing files at all, we can instead use the <literal>veto</literal> <literal>files</literal> option. This option, which takes the same syntax as the <literal>hide</literal> <literal>files</literal> option, specifies a list of files that should never be seen by the user. For example, let's change the <literal>[data]</literal> share to the following:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- case sensitive = no
- veto files = /*.java/*README*/</programlisting>
-
-
-<para>The syntax of this option is identical to the <literal>hide</literal> <literal>files</literal> configuration option: each entry must begin, end, or be separated from another with a slash (<literal>/</literal>) character, even if there is only one pattern listed. By doing so, the files <literal>hello.java</literal> and <literal>README</literal> will simply disappear from the directory, and the user will not be able to access them through SMB.</para>
-
-
-<para>There is one other question that we need to address. What happens if the user tries to delete a directory that contains vetoed files? This is where the <literal>delete</literal>
-<indexterm id="ch05-idx-969711-0"><primary>files</primary><secondary>deleting, option for</secondary></indexterm> <literal>veto</literal> <literal>files</literal> option comes in. If this boolean option is set to <literal>yes</literal>, the user is allowed to delete both the regular files and the vetoed files in the directory, and the directory itself will be removed. If the option is set to <literal>no</literal>, the user will not be able to delete the vetoed files, and consequently the directory will not be deleted either. From the user's perspective, the directory will appear to be empty, but cannot be removed.</para>
-
-
-<para>The <literal>dont</literal> <literal>descend</literal> directive specifies a list of <indexterm id="ch05-idx-969715-0"><primary>directories</primary><secondary>barring users from viewing contents</secondary></indexterm>directories whose contents Samba should not allow one to be visible. Note that we say <emphasis>contents</emphasis>, not the directory itself. Users will be able to enter a directory marked as such, but they are prohibited from descending the directory tree any farther—they will always see an empty folder. For example, let's use this option with a more basic form of the share that we defined earlier in the chapter:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- case sensitive = no
- dont descend = config defaults</programlisting>
-
-
-<para>In addition, let's assume that the <filename>/home/samba/data</filename> directory has the following contents:</para>
-
-
-<programlisting>drwxr-xr-x 6 tom users 1024 Jun 13 09:24 .
-drwxr-xr-x 8 root root 1024 Jun 10 17:53 ..
--rw-r--r-- 2 tom users 1024 Jun 9 11:43 README
-drwxr-xr-x 3 tom users 1024 Jun 13 09:28 config
-drwxr-xr-x 3 tom users 1024 Jun 13 09:28 defaults
-drwxr-xr-x 3 tom users 1024 Jun 13 09:28 market</programlisting>
-
-
-<para>If the user then connects to the share, he or she would see the directories shown in <link linkend="ch05-62659">Figure 5.4</link>. However, the contents of the <filename>/config</filename> and <filename>/defaults</filename> directories would appear empty to the user, even if other folders or files existed in them. In addition, users cannot write any data to the folder (which prevents them from creating a file or folder with the same name as one that is already there but invisible). If a user attempts to do so, he or she will receive an "Access Denied" message. <literal>dont</literal> <literal>descend</literal> is an administrative option, not a security option, and is not a substitute for good file permissions.</para>
-
-
-<figure label="5.4" id="ch05-62659">
-<indexterm id="ch05-idx-969696-0" class="endofrange" startref="ch05-idx-969684-0"/><indexterm id="ch05-idx-969696-1" class="endofrange" startref="ch05-idx-969704-0"/><indexterm id="ch05-idx-969696-2" class="endofrange" startref="ch05-idx-969704-1"/><title>Contents of the [data] share with dont descend
-
- </title>
-
-<graphic width="502" depth="210" fileref="figs/sam.0504.gif"></graphic>
-</figure>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.2.2" id="ch05-SECT-2.2">
-<title>Links</title>
-
-
-<para>
-<indexterm id="ch05-idx-969716-0"><primary>links</primary></indexterm>
-<indexterm id="ch05-idx-969716-1"><primary>filesystems</primary><secondary>links and</secondary></indexterm>DOS and NT filesystems don't have symbolic links; Windows 95/98/NT systems approximate this with "shortcuts" instead. Therefore, when a client tries to open a symbolic link on a Samba server share, Samba attempts to follow the link to find the real file and let the client open it, as if he or she were on a Unix machine. If you don't want to allow this, set the <literal>follow</literal> <literal>symlinks</literal> option:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- case sensitive = no
- follow symlinks = no</programlisting>
-
-
-<para>You can test this by creating a directory on the Unix server inside the share as the user that you are logging in with. Enter the following commands:</para>
-
-
-<programlisting>% <userinput>mkdir hello; cd hello</userinput>
-% <userinput>cat "This is a test" >hello.txt</userinput>
-% <userinput>ln -s hello.txt "Link to hello"</userinput></programlisting>
-
-
-<para>This results in the two files shown in the window in <link linkend="ch05-36377">Figure 5.5</link>. Normally, if you click on either one, you will receive a file which has the text "This is a test" inside of it. However, with the <literal>follow</literal> <literal>symlinks</literal> option set to <literal>no</literal>, you should receive an error similar to the dialog in <link linkend="ch05-36377">Figure 5.5</link> if you click on "Link to hello."</para>
-
-
-<figure label="5.5" id="ch05-36377">
-<title>An error dialog trying to follow symbolic links when forbidden by Samba</title>
-
-<graphic width="502" depth="149" fileref="figs/sam.0505.gif"></graphic>
-</figure>
-
-<para>Finally, let's discuss the <literal>wide</literal> <literal>links</literal> option. This option, if set to <literal>yes</literal>, allows the client user to follow symbolic links that point outside the shared directory tree, including files or directories at the other end of the link. For example, let's assume that we modified the <literal>[data]</literal> share as follows:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- case sensitive = no
- follow symlinks = yes
- wide links = yes</programlisting>
-
-
-<para>As long as the <literal>follow</literal> <literal>symlinks</literal> option is enabled, this will cause Samba to follow all symbolic links outside the current share tree. If we create a file outside the share (for example, in someone's home directory) and then create a link to it in the share as follows:</para>
-
-
-<programlisting>ln -s ~tom/datafile ./datafile</programlisting>
-
-
-<para>then you will be able to open the file in Tom's directory as per the target file's permissions.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.2.3" id="ch05-SECT-2.3">
-<title>Filesystem Options</title>
-
-
-<para>
-<indexterm id="ch05-idx-969717-0" class="startofrange"><primary>filesystems</primary><secondary>options for</secondary></indexterm><link linkend="ch05-48353">Table 5.4</link> shows a breakdown of the options we discussed earlier. We recommend the defaults for most, except those listed in the following descriptions.</para>
-
-
-<table label="5.4" id="ch05-48353">
-<title>Filesystem Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>unix realname</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Provides Unix user's full name to client.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>dont descend</literal></para></entry>
-
-<entry colname="col2"><para>string (list of directories)</para></entry>
-
-<entry colname="col3"><para>Indicates a list of directories whose contents Samba should make invisible to clients.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>follow symlinks</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>no</literal>, Samba will not honor symbolic links.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>getwd cache</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, Samba will use a cache for <literal>getwd( )</literal> calls.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>wide links</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, Samba will follow symbolic links outside the share.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>hide dot files</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, treats Unix hidden files as hidden files in Windows.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>hide files</literal></para></entry>
-
-<entry colname="col2"><para>string (list of files)</para></entry>
-
-<entry colname="col3"><para>List of file patterns to treat as hidden.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>veto files</literal></para></entry>
-
-<entry colname="col2"><para>string (list of files)</para></entry>
-
-<entry colname="col3"><para>List of file patterns to never show.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>delete veto files</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, will delete files matched by <literal>veto files</literal> when the directory they reside in is deleted.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="5.2.3.1" id="ch05-SECT-2.3.1">
-<indexterm id="ch05-idx-970574-0"><primary>unix realname option</primary></indexterm>
-<title>
-unix realname</title>
-
-
-<para>Some programs require a full username in order to operate. For example, a Windows email program often needs to associate a username with a given real name. If your system password file contains the real names of users in the GCOS field, the <literal>unix</literal> <literal>realname</literal> option instructs Samba to provide this information to clients. Without it, the name of the user will simply be his or her login ID. For example, if your Unix password file contains the following line:</para>
-
-
-<programlisting>rcollins:/KaBfco47Rer5:500:500:Robert Collins:
-/home/rcollins:/bin/ksh</programlisting>
-
-
-<para>And the option in the configuration file is:</para>
-
-
-<programlisting>[global]
- unix realname = yes</programlisting>
-
-
-<para>then the name Robert Collins will be provided to any client that requests the real name of user <literal>rcollins</literal>. You typically don't need to bother with this option.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.2" id="ch05-SECT-2.3.2">
-<title>dont descend</title>
-
-
-<para>The <literal>dont</literal>
-<indexterm id="ch05-idx-970575-0"><primary>dont descend option</primary></indexterm> <literal>descend</literal> option can be used to specify various <indexterm id="ch05-idx-969728-0"><primary>directories</primary><secondary>barring users from viewing contents</secondary></indexterm>directories that should appear empty to the client. Note that the directory itself will still appear. However, Samba will not show any of the contents of the directory to the client user. This is not a good option to use as a security feature (a user could probably find a way around it); it really is meant only as a convenience to keep client users from browsing into directories that might have sensitive files. See our example earlier in this section.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.3" id="ch05-SECT-2.3.3">
-<indexterm id="ch05-idx-970576-0"><primary>follow symlinks option</primary></indexterm>
-<title>
-follow symlinks</title>
-
-
-<para>
-<indexterm id="ch05-idx-969732-0"><primary>links</primary><secondary>option for</secondary></indexterm>This option, which is discussed in greater detail earlier, controls whether Samba will follow a symbolic link in the Unix operating system to the target, or if it should return an error to the client user. If the option is set to <literal>yes</literal>, the target of the link will be interpreted as the file.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.4" id="ch05-SECT-2.3.4">
-<indexterm id="ch05-idx-970577-0"><primary>getwd cache option</primary></indexterm>
-<title>
-getwd cache</title>
-
-
-<para>This global option specifies whether Samba should use a local cache for the Unix <literal>getwd()</literal> ( get current working directory) system call. You can override the default value of <literal>yes</literal> as follows:</para>
-
-
-<programlisting>[global]
- getwd cache = no</programlisting>
-
-
-<para>Setting this option to <literal>yes</literal> can significantly increase the time it takes to resolve the <indexterm id="ch05-idx-969733-0"><primary>working directory, option for</primary></indexterm>
-<indexterm id="ch05-idx-969733-1"><primary>directories</primary><secondary>working, option for</secondary></indexterm>working directory, especially if the <literal>wide</literal> <literal>links</literal> option is set to <literal>no</literal>. You should normally not need to alter this option.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.5" id="ch05-SECT-2.3.5">
-<indexterm id="ch05-idx-970578-0"><primary>wide links option</primary></indexterm>
-<title>
-wide links</title>
-
-
-<para>This option specifies whether the client user can follow symbolic links that point outside the shared directory tree. This includes any files or directories at the other end of the link, as long as the permissions are correct for the user. The default value for this option is <literal>yes</literal>. Note that this option will not be honored if the <literal>follow</literal> <literal>symlinks</literal> options is set to <literal>no</literal>. Setting this option to <literal>no</literal> slows <emphasis>smbd</emphasis> considerably.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.6" id="ch05-SECT-2.3.6">
-<title>hide files</title>
-
-
-<para>
-<indexterm id="ch05-idx-969738-0"><primary>files</primary><secondary>hidden</secondary><tertiary>options for</tertiary></indexterm>
-<indexterm id="ch05-idx-969738-1"><primary>hidden files</primary><secondary>options for</secondary></indexterm>The <literal>hide</literal> <literal>files</literal> option provides one or more directory or filename patterns to Samba. Any file matching this pattern will be treated as a hidden file from the perspective of the client. Note that this simply means that the DOS hidden attribute is set, which may or may not mean that the user can actually see it while browsing.</para>
-
-
-<para>Each entry in the list must begin, end, or be separated from another entry with a <indexterm id="ch05-idx-969734-0"><primary>slash (/)</primary><secondary>character</secondary></indexterm>
-<indexterm id="ch05-idx-969734-1"><primary>/ (slash character)</primary></indexterm>slash (<literal>/</literal>) character, even if there is only one pattern listed. This allows spaces to appear in the list. Asterisks can be used as a wildcard to represent zero or more characters. Questions marks can be used to represent exactly one character. For example:</para>
-
-
-<programlisting>hide files = /.jav*/README.???/</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.7" id="ch05-SECT-2.3.7">
-<title>hide dot files</title>
-
-
-<para>The <literal>hide</literal> <literal>dot</literal> <literal>files</literal> option hides any files on the server that begin with a <indexterm id="ch05-idx-969735-0"><primary>dot (.) in hidden files</primary></indexterm>
-<indexterm id="ch05-idx-969735-1"><primary>. (dot)</primary></indexterm>dot (.) character, in order to mimic the functionality behind several shell commands that are present on Unix systems. Like <literal>hide</literal> <literal>files</literal>, those files that begin with a dot have the DOS hidden attribute set, which doesn't necessarily guarantee that a client cannot view them. The default value for this option is <literal>yes</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.8" id="ch05-SECT-2.3.8">
-<indexterm id="ch05-idx-970581-0"><primary>veto files option</primary></indexterm>
-<title>
-veto files</title>
-
-
-<para>More stringent than the hidden files state is the state provided by the <literal>veto</literal> <literal>files</literal> configuration option. Samba won't even admit these files exist. You cannot list or open them from the client. In reality, this isn't a trustworthy security option. It is actually a mechanism to keep PC programs from deleting special files, such as ones used to store the resource fork of a Macintosh file on a Unix filesystem. If both Windows and Macs are sharing the same files, this can prevent ill-advised power users from removing files the Mac users need.</para>
-
-
-<para>The syntax of this option is identical to that of the <literal>hide</literal> <literal>files</literal> configuration option: each entry must begin, end, or be separated from another with a <indexterm id="ch05-idx-969758-0"><primary>slash (/)</primary><secondary>character</secondary></indexterm>
-<indexterm id="ch05-idx-969758-1"><primary>/ (slash character)</primary></indexterm>slash ( / ) character, even if only one pattern is listed. Asterisks can be used as a wildcard to represent zero or more characters. <indexterm id="ch05-idx-969762-0"><primary>question mark (?)</primary></indexterm>
-<indexterm id="ch05-idx-969762-1"><primary>? (question mark)</primary></indexterm>Questions marks can be used to represent exactly one character. For example:</para>
-
-
-<programlisting>veto files = /*config/*default?/</programlisting>
-
-
-<para>This option is primarily administrative—not a substitute for good file permissions.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.2.3.9" id="ch05-SECT-2.3.9">
-<indexterm id="ch05-idx-970582-0"><primary>delete veto files option</primary></indexterm>
-<title>
-delete veto files</title>
-
-
-<para>
-<indexterm id="ch05-idx-969768-0"><primary>veto files</primary><secondary>option for deleting</secondary></indexterm>
-<indexterm id="ch05-idx-969768-1"><primary>files</primary><secondary>veto</secondary><tertiary>option for deleting</tertiary></indexterm>This option tells Samba to delete vetoed files when a user attempts to delete the directory in which they reside. The default value is <literal>no</literal>. This means if a user tries to delete a directory that contains a vetoed file, the file (and the directory) will not be deleted. Instead, the directory will remain and appear to be empty from the perspective of the user. If set to <literal>yes</literal>, the directory and the vetoed files will be<indexterm id="ch05-idx-969721-0" class="endofrange" startref="ch05-idx-969717-0"/> deleted.</para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="5.3" id="ch05-34062">
-<title>File Permissions and Attributes on MS-DOS and Unix</title>
-
-
-<para>
-<indexterm id="ch05-idx-969769-0" class="startofrange"><primary>files</primary><secondary>permissions</secondary></indexterm>
-<indexterm id="ch05-idx-969769-1" class="startofrange"><primary>files</primary><secondary>attributes</secondary></indexterm>
-<indexterm id="ch05-idx-969769-2" class="startofrange"><primary>DOS file permissions and attributes</primary></indexterm>
-<indexterm id="ch05-idx-969769-3" class="startofrange"><primary>Unix</primary><secondary>file permissions and attributes</secondary></indexterm>DOS was never intended to be a multiuser, networked operating system. Unix, on the other hand, was designed that way from the start. Consequently, there are inconsistencies and gaps in coverage between the two filesystems that Samba must not only be aware of, but also provide solutions for. One of the biggest gaps is how Unix and DOS handle permissions with files.</para>
-
-
-<para>Let's take a look at how Unix assigns permissions. All Unix files have read, write, and execute bits for three classifications of users: <indexterm id="ch05-idx-969803-0"><primary>Unix</primary><secondary>user classifications</secondary></indexterm>owner, group, and world. These permissions can be seen at the extreme left-hand side when a <literal>ls</literal> <literal>-al</literal> command is issued in a Unix directory. For example:</para>
-
-
-<programlisting>-rwxr--r-- 1 tom users 2014 Apr 13 14:11 access.conf</programlisting>
-
-
-<para>Windows, on the other hand, has four principal bits that it uses with any file: read-only, system, hidden, and archive. You can view these bits by right-clicking on the file and choosing the Properties menu item. You should see a dialog similar to <link linkend="ch05-76568">Figure 5.6</link>.<footnote label="1" id="ch05-pgfId-964268">
-
-
-<para>The system checkbox will probably be greyed for your file. Don't worry about that—you should still be able to see when the box is checked and when it isn't.</para>
-
-
-</footnote></para>
-
-
-<figure label="5.6" id="ch05-76568">
-<title>DOS and Windows file properties</title>
-
-<graphic width="502" depth="435" fileref="figs/sam.0506.gif"></graphic>
-</figure>
-
-<para>The definition of each of those bits follows:</para>
-
-
-<variablelist>
-<varlistentry><term>
-<indexterm id="ch05-idx-969799-0"><primary>read-only files</primary></indexterm>
-<indexterm id="ch05-idx-969799-1"><primary>files</primary><secondary>read-only</secondary></indexterm>Read-only</term>
-<listitem><para>The file's contents can be read by a user but cannot be written to.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="ch05-idx-969800-0"><primary>system files</primary></indexterm>
-<indexterm id="ch05-idx-969800-1"><primary>files</primary><secondary>system</secondary></indexterm>System</term>
-<listitem><para>This file has a specific purpose required by the operating system.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="ch05-idx-969801-0"><primary>hidden files</primary></indexterm>
-<indexterm id="ch05-idx-969801-1"><primary>files</primary><secondary>hidden</secondary></indexterm>Hidden</term>
-<listitem><para>This file has been marked to be invisible to the user, unless the operating systems is explicitly set to show it.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="ch05-idx-969802-0"><primary>archive files</primary></indexterm>
-<indexterm id="ch05-idx-969802-1"><primary>files</primary><secondary>archive</secondary></indexterm>Archive</term>
-<listitem><para>This file has been touched since the last DOS backup was performed on it.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>Note that there is no bit to specify that a file is executable. DOS and Windows NT filesystems identify executable files by giving them the extensions .EXE, .COM, .CMD, or .BAT.</para>
-
-
-<para>Consequently, there is no use for any of the three Unix executable bits that are present on a file in a Samba disk share. DOS files, however, have their own attributes that need to be preserved when they are stored in a Unix environment: the archive, system, and hidden bits. Samba can preserve these bits by reusing the executable permission bits of the file on the Unix side—if it is instructed to do so. Mapping these bits, however, has an unfortunate side-effect: if a Windows user stores a file in a Samba share, and you view it on Unix with the <literal>ls</literal> <literal>-al</literal> command, some of the executable bits won't mean what you'd expect them to.</para>
-
-
-<para>Three Samba options decide whether the bits are mapped: <literal>map</literal> <literal>archive</literal>, <literal>map</literal> <literal>system </literal>, and <literal>map</literal> <literal>hidden</literal>. These options map the archive, system, and hidden attributes to the owner, group, and world execute bits of the file, respectively. You can add these options to the <literal>[data]</literal> share, setting each of their values as follows:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- map archive = yes
- map system = yes
- map hidden = yes</programlisting>
-
-
-<para>After that, try creating a file in the share under Unix—such as <literal>hello.java</literal>—and change the permissions of the file to 755. With these Samba options set, you should be able to check the permissions on the Windows side and see that each of the three values has been checked in the Properties dialog box. What about the read-only attribute? By default, Samba 2.0 sets this whenever a file does not have the Unix owner write permission bit set. In other words, you can set this bit by changing the permissions of the file to 555.</para>
-
-
-<para>We should warn you that the default value of the <literal>map</literal> <literal>archive</literal> option is <literal>yes</literal>, while the other two options have a default value of <literal>no</literal>. This is because many programs do not work properly if the archive bit is not stored correctly for DOS and Windows files. The system and hidden attributes, however, are not critical for a program's operation and are left to the discretion of the administrator.</para>
-
-
-<para><link linkend="ch05-56404">Figure 5.7</link> summarizes the Unix permission bits and illustrates how Samba maps those bits to DOS attributes. Note that the group read/write and world read/write bits do not directly translate to a DOS attribute, but they still retain their original Unix definitions on the Samba server.</para>
-
-
-<figure label="5.7" id="ch05-56404">
-<title>How Samba and Unix view the permissions of a file</title>
-
-<graphic width="502" depth="211" fileref="figs/sam.0507.gif"></graphic>
-</figure>
-
-<sect2 role="" label="5.3.1" id="ch05-SECT-3.0.1">
-<title>Creation masks</title>
-
-
-<para>Samba has several options to help with file <indexterm id="ch05-idx-969796-0"><primary>creation masks</primary></indexterm>
-<indexterm id="ch05-idx-969796-1"><primary>file creation masks</primary></indexterm>
-<indexterm id="ch05-idx-969796-2"><primary>masks</primary><secondary>creation</secondary></indexterm>
-<indexterm id="ch05-idx-969796-3"><primary>masks</primary><secondary>umasks</secondary></indexterm>creation masks. File creation masks (or <firstterm>umasks</firstterm>
-<indexterm id="ch05-idx-969797-0"><primary>umasks</primary></indexterm>) help to define the permissions a file or directory will receive at the time it is created. In Unix, this means that you can control what permissions a file or directory does not have when it is created. For files accessed from Windows, this means you can disable the read-only, archive, system, and hidden attributes of a file as well.</para>
-
-
-<para>For example, the <literal>create</literal> <literal>mask</literal> option will force the permissions of a file created by a Windows client to be at most 744:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- create mask = 744</programlisting>
-
-
-<para>while the <literal>directory</literal>
-<indexterm id="ch05-idx-970586-0"><primary>directory mask option</primary></indexterm> <literal>mask</literal> option shown here will force the permissions of a newly created directory to be at most 755:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
- directory mask = 755</programlisting>
-
-
-<para>Alternatively, you can also force various bits with the <literal>force</literal> <literal>create</literal> <literal>mode</literal> and <literal>force</literal> <literal>directory</literal> <literal>mode</literal> options. These options will perform a logical OR against the file and directory creation masks, ensuring that those bits that are specified will always be set. You would typically set these options globally in order to ensure that group and world read/write permissions have been set appropriately for new files or directories in each share.</para>
-
-
-<para>In the same spirit, if you wish to explicitly set the Unix user and group attributes of a file that is created on the Windows side, you can use the <literal>force</literal>
-<indexterm id="ch05-idx-970587-0"><primary>force user option</primary></indexterm>
-<indexterm id="ch05-idx-970587-1"><primary>force group option</primary></indexterm> <literal>user</literal> and <literal>force</literal> <literal>group</literal> options. For example:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
-
- create mask = 744
- directory mask = 755
- force user = joe
- force group = accounting</programlisting>
-
-
-<para>These options actually assign a static Unix user and group to each connection that is made to a share. However, this occurs <emphasis>after</emphasis> the client authenticates; it does not allow free access to a share. These options are frequently used for their side effects of assigning a specific user and group to each new file or directory that is created in a share. Use these options with discretion.</para>
-
-
-<para>Finally, one of the capabilities of Unix that DOS lacks is the ability to delete a read-only file from a writable directory. In Unix, if a directory is writable, a read-only file in that directory can still be removed. This could permit you to delete files in any of your directories, even if the file was left by someone else.</para>
-
-
-<para>DOS filesystems are not designed for multiple users, and so its designers decided that <indexterm id="ch05-idx-969808-0"><primary>read-only files</primary><secondary>deleting</secondary></indexterm>
-<indexterm id="ch05-idx-969808-1"><primary>files</primary><secondary>read-only</secondary><tertiary>deleting</tertiary></indexterm>read-only means "protected against accidental change, including deletion," rather than "protected against some other user on a single-user machine." So the designers of DOS prohibited removal of a read-only file. Even today, Windows file systems exhibit the same behavior.</para>
-
-
-<para>Normally, this is harmless. Windows programs don't try to remove read-only files because they know it's a bad idea. However, a number of source-code control programs—which were first written for Unix—run on Windows and require the ability to delete read-only files. Samba permits this behavior with the <literal>delete</literal>
-<indexterm id="ch05-idx-970588-0"><primary>delete readonly option</primary></indexterm> <literal>readonly</literal> option. In order to enable this functionality, set the option to <literal>yes</literal>:</para>
-
-
-<programlisting>[data]
- path = /home/samba/data
- browseable = yes
- guest ok = yes
- writeable = yes
-
- create mask = 744
- directory mask = 755
- force user = joe
- force group = accounting
- delete readonly = yes</programlisting>
-</sect2>
-
-
-
-
-<sect2 role="" label="5.3.2" id="ch05-SECT-3.1">
-<title>File and Directory Permission Options</title>
-
-
-<para>
-<indexterm id="ch05-idx-969813-0" class="startofrange"><primary>files</primary><secondary>permissions</secondary><tertiary>options for</tertiary></indexterm>
-<indexterm id="ch05-idx-969813-1" class="startofrange"><primary>directories</primary><secondary>permissions, options for</secondary></indexterm>
-<indexterm id="ch05-idx-969813-2" class="startofrange"><primary>permissions</primary><secondary>options for</secondary></indexterm>The options for file and directory permissions are summarized in <link linkend="ch05-96508">Table 5.5</link>; each option is then described in detail.</para>
-
-
-<table label="5.5" id="ch05-96508">
-<title>File and Directory Permission Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>map archive</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Preserve DOS archive attribute in user execute bit (0100).</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>map system</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Preserve DOS system attribute in group execute bit (0010).</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>map hidden</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Preserve DOS hidden attribute in world execute bit (0001).</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>create mask (create mode)</literal></para></entry>
-
-<entry colname="col2"><para>numeric</para></entry>
-
-<entry colname="col3"><para>Sets the maximum permissions for files created by Samba.</para></entry>
-
-<entry colname="col4"><para><literal>0744</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>directory mask (directory mode)</literal></para></entry>
-
-<entry colname="col2"><para>numeric</para></entry>
-
-<entry colname="col3"><para>Sets the maximum permissions for directories created by Samba.</para></entry>
-
-<entry colname="col4"><para><literal>0755</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>force create mode</literal></para></entry>
-
-<entry colname="col2"><para>numeric</para></entry>
-
-<entry colname="col3"><para>Forces the specified permissions (bitwise or) for directories created by Samba.</para></entry>
-
-<entry colname="col4"><para><literal>0000</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>force directory mode</literal></para></entry>
-
-<entry colname="col2"><para>numeric</para></entry>
-
-<entry colname="col3"><para>Forces the specified permissions (bitwise or) for directories created by Samba.</para></entry>
-
-<entry colname="col4"><para><literal>0000</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>force group (group)</literal></para></entry>
-
-<entry colname="col2"><para>string ( group name)</para></entry>
-
-<entry colname="col3"><para>Sets the effective group for a user accessing this share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>force user</literal></para></entry>
-
-<entry colname="col2"><para>string (username)</para></entry>
-
-<entry colname="col3"><para>Sets the effective username for a user accessing this share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>delete readonly</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Allows a user to delete a read-only file from a writable directory.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="5.3.2.1" id="ch05-SECT-3.1.1">
-<title>create mask</title>
-
-
-<para>The argument for this option is an octal number indicating which permission flags may be set at file creation by a client in a share. The default is 0755, which means the Unix owner can at most read, write, and optionally execute his or her own files, while members of the user's group and others can only read or execute them. If you need to change it for non-executable files, we recommend 0644, or <literal>rw-r--r--</literal>. Keep in mind that the execute bits may be used by the server to map certain DOS file attributes, as described earlier. If you're altering the <indexterm id="ch05-idx-969816-0"><primary>creation masks</primary><secondary>option for</secondary></indexterm>create mask, those bits have to be part of the create mask as well.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.2" id="ch05-SECT-3.1.2">
-<indexterm id="ch05-idx-970593-0"><primary>directory mask option</primary></indexterm>
-<title>
-directory mask</title>
-
-
-<para>The argument for this option is an octal number indicating which permission flags may be set at directory creation by a client in a share. The default is 0755, which allows everyone on the Unix side to at most read and traverse the directories, but allows only you to modify them. We recommend the mask 0750, removing access by world users.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.3" id="ch05-SECT-3.1.3">
-<indexterm id="ch05-idx-970594-0"><primary>force create mode option</primary></indexterm>
-<title>
-force create mode</title>
-
-
-<para>This option sets the permission bits that Samba will force to be set when a file permission change is made. It's often used to force group permissions, mentioned previously. It can also be used to preset any of the DOS attributes we mentioned: archive (0100), system (0010), or hidden (0001). This option always takes effect after the <literal>map</literal> <literal>archive</literal>, <literal>map</literal> <literal>system </literal>, <literal>map</literal> <literal>hidden</literal>, and <literal>create</literal> <literal>mask</literal> options.</para>
-
-
-<tip role="ora">
-<para>Many Windows applications rename their data files to <emphasis>datafile.bak</emphasis> and create new ones, thus changing their ownership and permissions so that members of the same Unix group can't edit them. Setting <literal>force create mask = 0660</literal> will keep the new file editable by members of the group.</para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.4" id="ch05-SECT-3.1.4">
-<indexterm id="ch05-idx-970595-0"><primary>force directory mode option</primary></indexterm>
-<title>
-force directory mode</title>
-
-
-<para>This option sets the permission bits which Samba will force when a directory permission change is made or a directory is created. It's often used to force group permissions, as mentioned previously. This option defaults to 0000, and can be used just like the <literal>force</literal> <literal>create</literal> <literal>mode</literal> to add group or other permissions if needed. This option always takes effect after the <literal>map</literal> <literal>archive</literal>, <literal>map</literal> <literal>system</literal>, <literal>map</literal> <literal>hidden</literal>, and <literal>directory</literal> <literal>mask</literal> options.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.5" id="ch05-SECT-3.1.5">
-<indexterm id="ch05-idx-970596-0"><primary>force group option</primary></indexterm>
-<title>
-force group</title>
-
-
-<para>This option, sometimes called <literal>group</literal>, assigns a static group ID that will be used on all connections to a service after the client has successfully authenticated. This assigns a specific group to each new file or directory created from an SMB client.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.6" id="ch05-SECT-3.1.6">
-<indexterm id="ch05-idx-970597-0"><primary>force user option</primary></indexterm>
-<title>
-force user</title>
-
-
-<para>The <literal>force</literal> <literal>user</literal> option assigns a static user ID that will be used on all connections to a service after the client has successfully authenticated. This assigns a specific user to each new file or directory created from an SMB client.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.7" id="ch05-SECT-3.1.7">
-<indexterm id="ch05-idx-970598-0"><primary>delete readonly option</primary></indexterm>
-<title>
-delete readonly</title>
-
-
-<para>
-<indexterm id="ch05-idx-969827-0"><primary>files</primary><secondary>read-only</secondary><tertiary>deleting</tertiary></indexterm>
-<indexterm id="ch05-idx-969827-1"><primary>read-only files</primary><secondary>deleting</secondary></indexterm>This option allows a user to delete a directory containing a read-only file. By default, DOS and Windows will not allow such an operation. You probably will want to leave this option turned off unless a program needs this capability; many Windows users would be appalled to find that they'd accidentally deleted a file which they had set read-only. In fact, even the Unix <literal>rm</literal> command will ask users if they really want to override the protection and delete read-only files. It's a good idea to have Samba be at least as cautious.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.8" id="ch05-SECT-3.1.8">
-<indexterm id="ch05-idx-970600-0"><primary>map archive option</primary></indexterm>
-<title>
-map archive</title>
-
-
-<para>The DOS archive bit is used to flag a file that has been changed since it was last archived (e.g., backed up with the DOS archive program.) Setting the Samba option <literal>map</literal> <literal>archive</literal> <literal>=</literal> <literal>yes</literal> causes the DOS archive flag to be mapped to the Unix execute-by-owner (0100) bit. It's best to leave this option on if your Windows users are doing their own backups, or are using programs that require the archive bit. Unix lacks the notion of an archive bit entirely. Backup programs typically keep a file that lists what files were backed up on what date, so comparing file modification dates serves the same purpose.</para>
-
-
-<para>Setting this option to <literal>yes</literal> causes an occasional surprise on Unix when a user notices that a data file is marked as executable, but rarely causes harm. If a user tries to run it, he or she will normally get a string of error messages as the shell tries to execute the first few lines as commands. The reverse is also possible; an executable Unix program looks like it hasn't been backed up recently on Windows. But again, this is rare, and is usually harmless.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.9" id="ch05-SECT-3.1.9">
-<indexterm id="ch05-idx-970601-0"><primary>map system option</primary></indexterm>
-<title>
-map system</title>
-
-
-<para>The DOS system attribute is used to indicate files that are required by the operating system, and should not be deleted, renamed, or moved without special effort. Set this option only if you need to store Windows system files on the Unix file server. Executable Unix programs will appear to be non-removable special Windows files when viewed from Windows clients. This may prove mildly inconvenient if you want to move or remove one. For most sites, however, this is fairly harmless.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.3.2.10" id="ch05-SECT-3.1.10">
-<indexterm id="ch05-idx-970602-0"><primary>map hidden option</primary></indexterm>
-<title>
-map hidden</title>
-
-
-<para>
-<indexterm id="ch05-idx-969828-0"><primary>hidden files</primary><secondary>options for</secondary></indexterm>DOS uses the hidden attribute to indicate that a file should not ordinarily be visible in directory listings. Unix doesn't have such a facility; it's up to individual programs (notably the shell) to decide what to display and what not to display. Normally, you won't have any DOS files that need to be hidden, so the best thing to do is to leave this option turned off.</para>
-
-
-<para>Setting this option to <literal>yes</literal> causes the server to map the hidden flag onto the executable-by-others bit (0001). This feature can produce a rather startling effect. Any Unix program that is executable by world seems to vanish when you look for it from a Windows client. If this option is not set, however, and a Windows user attempts to mark a file hidden on a Samba share, it will not work—Samba has no place to store the hidden attribute!<indexterm id="ch05-idx-969791-0" class="endofrange" startref="ch05-idx-969769-0"/>
-<indexterm id="ch05-idx-969791-1" class="endofrange" startref="ch05-idx-969769-1"/>
-<indexterm id="ch05-idx-969791-2" class="endofrange" startref="ch05-idx-969769-2"/>
-<indexterm id="ch05-idx-969791-3" class="endofrange" startref="ch05-idx-969769-3"/>
-<indexterm id="ch05-idx-969791-4" class="endofrange" startref="ch05-idx-969813-2"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="5.4" id="ch05-30534">
-<title>Name Mangling and Case</title>
-
-
-<para>
-<indexterm id="ch05-idx-969835-0" class="startofrange"><primary>name mangling</primary></indexterm>Back in the days of DOS and Windows 3.1, every filename was limited to eight upper-case characters, followed by a dot, and three more uppercase characters. This was known as the <firstterm>8.3 format</firstterm>
-<indexterm id="ch05-idx-969833-0"><primary>8.3 format</primary></indexterm>
-<indexterm id="ch05-idx-969833-1"><primary>filenames</primary><secondary>8.3 format</secondary></indexterm>, and was a huge nuisance. Windows 95/98, Windows NT, and Unix have since relaxed this problem by allowing many more case-sensitive characters to make up a filename. <link linkend="ch05-24354">Table 5.6</link> shows the current naming state of several popular operating systems.</para>
-
-
-<table label="5.6" id="ch05-24354">
-<title>Operating System Filename Limitations </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Operating System</para></entry>
-
-<entry colname="col2"><para>File Naming Rules</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>DOS 6.22 or below</para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch05-idx-969834-0"><primary>filenames</primary><secondary>limitations on</secondary></indexterm>Eight characters followed by a dot followed by a three-letter extension (8.3 format); case insensitive</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 3.1 for Workgroups</para></entry>
-
-<entry colname="col2"><para>Eight characters followed by a dot followed by a three-letter extension (8.3 format); case insensitive</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 95/98</para></entry>
-
-<entry colname="col2"><para>127 characters; case sensitive</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows NT</para></entry>
-
-<entry colname="col2"><para>127 characters; case sensitive</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Unix</para></entry>
-
-<entry colname="col2"><para>255 characters; case sensitive</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>
-<indexterm id="ch05-idx-969837-0"><primary>backwards compatibility</primary><secondary sortas="filenames">for filenames</secondary></indexterm>Samba still has to remain backwards compatible with network clients who store files only in the 8.3 format, such as Windows for Workgroups. If a user creates a file on a share called <emphasis>antidisestablishmentarianism.txt</emphasis>, a Windows for Workgroups client couldn't tell it apart from another file in the same directory called <emphasis>antidisease.txt</emphasis>. Like Windows 95/98 and Windows NT, Samba has to employ a special methodology of translating a long filename to an 8.3 filename in such a way that similar filenames will not cause collisions. This is called <firstterm>name mangling</firstterm>, and Samba deals with this in a manner that is similar, but not identical to, Windows 95 and its successors.</para>
-
-
-<sect2 role="" label="5.4.1" id="ch05-SECT-4.1">
-<title>The Samba Mangling Operation</title>
-
-
-<para>
-<indexterm id="ch05-idx-969840-0"><primary>name mangling</primary><secondary>steps in</secondary></indexterm>Here is how Samba mangles a long filename into an 8.3 filename:</para>
-
-
-<itemizedlist>
-<listitem><para>If the original filename does not begin with a dot, up to the first five alphanumeric characters that occur before the last dot (if there is one) are converted to uppercase. These characters are used as the first five characters of the 8.3 mangled filename.</para></listitem>
-<listitem><para>If the original filename begins with a dot, the dot is removed and up to the first five alphanumeric characters that occur before the last dot (if there is one) are converted to uppercase. These characters are used as the first five characters of the 8.3 mangled filename.</para></listitem>
-<listitem><para>These characters are immediately followed a special mangling character: by default, a tilde (~), although Samba allows you to change this character.</para></listitem>
-<listitem><para>The base of the long filename before the last period is hashed into a two-character code; parts of the name after the last dot may be used if necessary. This two character code is appended to the 8.3 filename after the mangling character.</para></listitem>
-<listitem><para>The first three characters after the last dot (if there is one) of the original filename are converted to uppercase and appended onto the mangled name as the extension. If the original filename began with a dot, three underscores ( <literal>_ _ _ </literal>) are used as the extension instead.</para></listitem>
-</itemizedlist>
-
-<para>Here are some examples:</para>
-
-
-<programlisting>virtuosity.dat VIRTU~F1.DAT
-.htaccess HTACC~U0._ _ _
-hello.java HELLO~1F.JAV
-team.config.txt TEAMC~04.TXT
-antidisestablishmentarianism.txt ANTID~E3.TXT
-antidiseast.txt ANTID~9K.TXT</programlisting>
-
-
-<para>Using these rules will allow Windows for Workgroups to differentiate the two files on behalf of the poor individual who is forced to see the network through the eyes of that operating system. Note that the same long filename should always hash to the same mangled name with Samba; this doesn't always happen with Windows. The downside of this approach is that there can still be collisions; however, the chances are greatly reduced.</para>
-
-
-<para>You generally want to use the mangling configuration options with only the oldest clients. We recommend doing this without disrupting other clients by adding an <literal>include</literal> directive to the <filename>smb.conf</filename> file:</para>
-
-
-<programlisting>[global]
- include = /ucsr/local/samba/lib/smb.conf.%m</programlisting>
-
-
-<para>This resolves to <filename>smb.conf.WfWg</filename> when a Window for Workgroups client attaches. Now you can create a file <filename>/usr/local/samba/lib/smb.conf.WfWg</filename> which might contain these options:</para>
-
-
-<programlisting>[global]
- case sensitive = no
- default case = upper
- preserve case = no
- short preserve case = no
- mangle case = yes
- mangled names= yes</programlisting>
-
-
-<para>If you are not using Windows for Workgroups 3.1, then you probably do not need to change any of these options from their defaults.</para>
-
-
-<sect3 role="" label="5.4.1.1" id="ch05-SECT-4.1.1">
-<title>Representing and resolving filenames with Samba</title>
-
-
-<para>
-<indexterm id="ch05-idx-969841-0"><primary>representing/resolving filenames</primary></indexterm>
-<indexterm id="ch05-idx-969841-1"><primary>filenames</primary><secondary>representing/resolving</secondary></indexterm>Another item that we should point out is that there is a difference between how an operating system <emphasis>represents</emphasis> a file and how it <emphasis>resolves</emphasis> it. For example, if you've used Windows 95/98/NT, you have likely run across a file called <filename>README.TXT</filename>. The file can be represented by the operating system entirely in uppercase letters. However, if you open an MS-DOS prompt and enter the command <literal>edit</literal> <literal>readme.txt</literal>, the all-caps file is loaded into the editing program, even though you typed the name in lowercase letters!</para>
-
-
-<para>This is because the Windows 95/98/NT family of operating systems resolves files in a case-insensitive manner, even though the files are represented it in a case-sensitive manner. Unix-based operating systems, on the other hand, always resolve files in a case-sensitive manner; if you try to edit <filename>README.TXT</filename> with the command <literal>vi</literal> <literal>readme.txt</literal>, you will likely be editing the empty buffer of a new file.</para>
-
-
-<para>Here is how Samba handles case: if the <literal>preserve</literal> <literal>case</literal> is set to <literal>yes</literal>, Samba will always use the case provided by the operating system for representing (not resolving) filenames. If it is set to <literal>no</literal>, it will use the case specified by the <literal>default</literal> <literal>case</literal> option. The same is true for <literal>short</literal> <literal>preserve</literal> <literal>case</literal>. If this option is set to <literal>yes</literal>, Samba will use the default case of the operating system for representing 8.3 filenames; otherwise it will use the case specified by the <literal>default</literal> <literal>case</literal> option. Finally, Samba will always resolve filenames in its shares based on the value of the <literal>case</literal> <literal>sensitive</literal> option.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.4.2" id="ch05-SECT-4.2">
-<title>Mangling Options</title>
-
-
-<para>
-<indexterm id="ch05-idx-969842-0" class="startofrange"><primary>name mangling</primary><secondary>options for</secondary></indexterm>Samba allows you to give it more refined instructions on how it should perform name mangling, including those controlling the case sensitivity, the character inserted to form a mangled name, and the ability to manually map filenames from one format to another. These options are shown in <link linkend="ch05-47431">Table 5.7</link>.</para>
-
-
-<table label="5.7" id="ch05-47431">
-<title>Name Mangling Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>case sensitive</literal></para>
-
-<para><literal>(casesignames)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba will treat filenames as case-sensitive (Windows doesn't).</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>default case</literal></para></entry>
-
-<entry colname="col2"><para>(<literal>upper</literal> or <literal>lower</literal>)</para></entry>
-
-<entry colname="col3"><para>Case to assume as default (only used when preserve case is <literal>no</literal>).</para></entry>
-
-<entry colname="col4"><para>Lower</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>preserve case</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, keep the case the client supplied (i.e., do not convert to <literal>default case</literal>).</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>short preserve case</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, preserve case of 8.3-format names that the client provides.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mangle case</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Mangle a name if it is mixed case.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mangled names</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>8.3 DOS format.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mangling char</literal></para></entry>
-
-<entry colname="col2"><para>string (single character)</para></entry>
-
-<entry colname="col3"><para>Gives mangling character.</para></entry>
-
-<entry colname="col4"><para><literal>~</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mangled stack</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Number of mangled names to keep on the local mangling stack.</para></entry>
-
-<entry colname="col4"><para><literal>50</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>mangled map</literal></para></entry>
-
-<entry colname="col2"><para>string (list of patterns)</para></entry>
-
-<entry colname="col3"><para>Allows mapping of filenames from one format into another.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="5.4.2.1" id="ch05-SECT-4.2.1">
-<title>case sensitive</title>
-
-
-<para>
-<indexterm id="ch05-idx-969856-0"><primary>case sensitivity</primary><secondary>options for</secondary></indexterm>This share-level option, which has the obtuse synonym <literal>casesignames</literal>, specifies whether Samba should preserve case when resolving filenames in a specific share. The default value for this option is <literal>no</literal>, which is how Windows handles file resolution. If clients are using an operating system that takes advantage of case-sensitive filenames, you can set this configuration option to <literal>yes</literal> as shown here:</para>
-
-
-<programlisting>[accounting]
- case sensitive = yes</programlisting>
-
-
-<para>Otherwise, we recommend that you leave this option set to its default.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.2" id="ch05-SECT-4.2.2">
-<title>default case</title>
-
-
-<para>The <literal>default</literal>
-<indexterm id="ch05-idx-970606-0"><primary>default case option</primary></indexterm> <literal>case</literal> option is used with <literal>preserve</literal> <literal>case</literal>. This specifies the default case (upper or lower) that Samba will use when it creates a file on one of its shares on behalf of a client. The default case is <literal>lower</literal>, which means that newly created files will use the mixed-case names given to them by the client. If you need to, you can override this global option by specifying the following:</para>
-
-
-<programlisting>[global]
- default case = upper</programlisting>
-
-
-<para>If you specify this value, the names of newly created files will be translated into uppercase, and cannot be overridden in a program. We recommend that you use the default value unless you are dealing with a Windows for Workgroups or other 8.3 client, in which case it should be <literal>upper</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.3" id="ch05-SECT-4.2.3">
-<indexterm id="ch05-idx-970607-0"><primary>preserve case option</primary></indexterm>
-<title>
-preserve case</title>
-
-
-<para>This option specifies whether a file created by Samba on behalf of the client is created with the case provided by the client operating system, or the case specified by the <literal>default</literal> <literal>case</literal> configuration option above. The default value is <literal>yes</literal>, which uses the case provided by the client operating system. If it is set to <literal>no</literal>, the value of the <literal>default</literal> <literal>case</literal> option is used.</para>
-
-
-<para>Note that this option does not handle 8.3 file requests sent from the client—see the <literal>short</literal> <literal>preserve</literal> <literal>case</literal> option below. You may want to set this option to <literal>yes</literal> if applications that create files on the Samba server are sensitive to the case used when creating the file. If you want to force Samba, for example, to mimic the behavior of a Windows NT filesystem, you can leave this option to its default, <literal>yes</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.4" id="ch05-SECT-4.2.4">
-<indexterm id="ch05-idx-970608-0"><primary>hort preserve case option</primary></indexterm>
-<title>short preserve case</title>
-
-
-<para>This option specifies whether an 8.3 filename created by Samba on behalf of the client is created with the default case of the client operating system, or the case specified by the <literal>default</literal> <literal>case</literal> configuration option. The default value is <literal>yes</literal>, which uses the case provided by the client operating system. You can let Samba choose the case through the <literal>default</literal> <literal>case</literal> option by setting it as follows:</para>
-
-
-<programlisting>[global]
- short preserve case = no</programlisting>
-
-
-<para>If you want to force Samba to mimic the behavior of a Windows NT filesystem, you can leave this option set to its default, <literal>yes</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.5" id="ch05-SECT-4.2.5">
-<indexterm id="ch05-idx-970609-0"><primary>mangled names option</primary></indexterm>
-<title>
-mangled names</title>
-
-
-<para>This share-level option specifies whether Samba will mangle filenames for 8.3 clients in that share. If the option is set to <literal>no</literal>, Samba will not mangle the names and (depending on the client), they will either be invisible or appear truncated to those using 8.3 operating systems. The default value is <literal>yes</literal>. You can override it per share as follows:</para>
-
-
-<programlisting>[data]
- mangled names = no</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.6" id="ch05-SECT-4.2.6">
-<indexterm id="ch05-idx-970610-0"><primary>mangle case option</primary></indexterm>
-<title>
-mangle case</title>
-
-
-<para>This option tells Samba whether it should mangle filenames that are not composed entirely of the case specified using the <literal>default</literal> <literal>case</literal> configuration option. The default for this option is <literal>no</literal>. If you set it to <literal>yes</literal>, you should be sure that all clients will be able to handle the mangled filenames that result. You can override it per share as follows:</para>
-
-
-<programlisting>[data]
- mangle case = yes</programlisting>
-
-
-<para>We recommend that you leave this option alone unless you have a well-justified need to change it.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.7" id="ch05-SECT-4.2.7">
-<indexterm id="ch05-idx-970611-0"><primary>mangling char option</primary></indexterm>
-<title>
-mangling char</title>
-
-
-<para>This share-level option specifies the mangling character used when Samba mangles filenames into the 8.3 format. The default character used is a tilde (~). You can reset it to whatever character you wish, for instance:</para>
-
-
-<programlisting>[data]
- mangling char = #</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.8" id="ch05-SECT-4.2.8">
-<indexterm id="ch05-idx-970612-0"><primary>mangled stack option</primary></indexterm>
-<title>
-mangled stack</title>
-
-
-<para>Samba maintains a local stack of recently mangled 8.3 filenames; this stack can be used to reverse map mangled filenames back to their original state. This is often needed by applications that create and save a file, close it, and need to modify it later. The default number of long filename/mangled filename pairs stored on this stack is 50. However, if you want to cut down on the amount of processor time used to mangle filenames, you can increase the size of the stack to whatever you wish, at the expense of memory and slightly slower file access.</para>
-
-
-<programlisting>[global]
- mangled stack = 100</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="5.4.2.9" id="ch05-SECT-4.2.9">
-<indexterm id="ch05-idx-970613-0"><primary>mangled map option</primary></indexterm>
-<title>
-mangled map</title>
-
-
-<para>If the default behavior of name mangling is not sufficient, you can give Samba further instructions on how to behave using the <literal>mangled</literal> <literal>map</literal> option. This option allows you to specify mapping patterns that can be used before or even in place of name mangling performed by Samba. For example:</para>
-
-
-<programlisting>[data]
- mangled map =(*.database *.db) (*.class *.cls)</programlisting>
-
-
-<para>Here, Samba is instructed to search each file it encounters for characters that match the first pattern specified in the parenthesis and convert them to the modified second pattern in the parenthesis for display on an 8.3 client. This is useful in the event that name mangling converts the filename incorrectly or to a format that the client cannot understand<indexterm id="ch05-idx-969851-0" class="endofrange" startref="ch05-idx-969842-0"/> readily. Patterns are separated by whitespaces.<indexterm id="ch05-idx-969845-0" class="endofrange" startref="ch05-idx-969835-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="5.5" id="ch05-75933">
-<title>Locks and Oplocks</title>
-
-
-<para>
-<indexterm id="ch05-idx-969857-0" class="startofrange"><primary>locks/locking files</primary></indexterm>
-<indexterm id="ch05-idx-969857-1" class="startofrange"><primary>oplocks</primary></indexterm>Concurrent writes to a single file are not desirable in any operating system. To prevent this, most operating systems use <firstterm>locks</firstterm> to guarantee that only one process can write to a file at a time. Operating systems traditionally lock entire files, although newer ones allow a range of bytes within a file to be locked. If another process attempts to write to a file (or section of one) that is already locked, it will receive an error from the operating system and will wait until the lock is released.</para>
-
-
-<para>Samba supports the standard DOS and NT filesystem (deny-mode) locking requests, which allow only one process to write to an entire file on a server at a give time, as well as byte-range locking. In addition, Samba supports a new locking mechanism known in the Windows NT world as <firstterm>opportunistic locking—</firstterm><emphasis>oplock</emphasis> for short.</para>
-
-
-<sect2 role="" label="5.5.1" id="ch05-SECT-5.1">
-<title>Opportunistic Locking</title>
-
-
-<para>Opportunistic locking allows a client to notify the Samba server that it will not only be the exclusive writer of a file, but will also cache its changes to that file on its own machine (and not on the Samba server) in order to speed up file access for that client. When Samba knows that a file has been opportunistically locked by a client, it marks its version as having an opportunistic lock and waits for the client to complete work on the file, at which point it expects the client to send the final changes back to the Samba server for synchronization.</para>
-
-
-<para>If a second client requests access to that file before the first client has finished working on it, Samba can send an <firstterm>oplock break</firstterm>
-<indexterm id="ch05-idx-969865-0"><primary>oplocks</primary><secondary>break requests</secondary></indexterm> request to the first client. This tells the client to stop caching its changes and return the current state of the file to the server so that the interrupting client can use it as it sees fit. An opportunistic lock, however, is not a replacement for a standard deny-mode lock. It is not unheard of for the interrupting process to be granted an oplock break only to discover that the original process also has a deny-mode lock on a file as well. <link linkend="ch05-74304">Figure 5.8</link> illustrates this opportunistic locking process.</para>
-
-
-<figure label="5.8" id="ch05-74304">
-<title>Opportunistic locking</title>
-
-<graphic width="502" depth="314" fileref="figs/sam.0508.gif"></graphic>
-</figure>
-
-<para>In terms of locks, we highly recommend using the defaults provided by Samba: standard DOS/Windows deny-mode locks for compatibility and oplocks for the extra performance that local caching allows. If your operating system can take advantage of oplocks, it should provide significant performance improvements. Unless you have a specific reason for changing any of these options, it's best to leave them as they are.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="5.5.2" id="ch05-SECT-5.2">
-<title>Unix and Locking</title>
-
-
-<para>
-<indexterm id="ch05-idx-969866-0"><primary>locks/locking files</primary><secondary>Unix and</secondary></indexterm>
-<indexterm id="ch05-idx-969866-1"><primary>Unix</primary><secondary>locks and</secondary></indexterm>Windows systems cooperate well to avoid overwriting each other's changes. But if a file stored on a Samba system is accessed by a Unix process, this process won't know a thing about Windows oplocks and could easily ride roughshod over a lock. Some Unix systems have been enhanced to understand the Windows oplocks maintained by Samba. Currently the support exists only in SGI Irix 6.5.2f and later; Linux and FreeBSD should soon follow.</para>
-
-
-<para>If you have a system that understands oplocks, set <literal>kernel</literal> <literal>oplocks</literal> <literal>=</literal> <literal>yes</literal> in the Samba configuration file. That should eliminate conflicts between Unix processes and Windows users.</para>
-
-
-<para>If your system does not support kernel oplocks, you could end up with corrupted data when somebody runs a Unix process that reads or writes a file that Windows users also access. However, Samba provides a rough protection mechanism in the absence of kernel oplocks: the <literal>veto</literal> <literal>oplock</literal> <literal>files</literal> option. If you can anticipate which Samba files are used by both Windows users and Unix users, set their names in a <literal>veto</literal> <literal>oplock</literal> <literal>files</literal> option. This will suppress the use of oplocks on matching filenames, which will supress client caching, and let the Windows and Unix programs use system locking or update times to detect competition for the same file. A sample option is:</para>
-
-
-<programlisting>veto oplock files = /*.dbm/</programlisting>
-
-
-<para>This option allows both Unix processes and Windows users to edit files ending in the suffix <emphasis>.dbm</emphasis>. Note that the syntax of this option is similar to <literal>veto</literal> <literal>files</literal>.</para>
-
-
-<para>Samba's options for locks and oplocks are given in <link linkend="ch05-53407">Table 5.8</link>.</para>
-
-
-<table label="5.8" id="ch05-53407">
-<title>Locks and Oplocks Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>share modes</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch05-idx-969867-0" class="startofrange"><primary>locks/locking files</primary><secondary>options for</secondary></indexterm>
-<indexterm id="ch05-idx-969867-1" class="startofrange"><primary>oplocks</primary><secondary>options for</secondary></indexterm>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, turns on support for DOS-style whole-file locks.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>locking</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, turns on byte-range locks.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>strict locking</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, denies access to an entire file if a byte-range lock exists in it.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>oplocks</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, turn on local caching of files on the client for this share.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>kernel oplocks</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, indicates that the kernel supports oplocks.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>fake oplocks</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, tells client the lock was obtained, but doesn't actually lock it.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>blocking locks </literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Allows lock requestor to wait for the lock to be granted.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>veto oplock files</literal></para></entry>
-
-<entry colname="col2"><para>string (list of filenames)</para></entry>
-
-<entry colname="col3"><para>Does not oplock specified files.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lock directory</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Sets the location where various Samba files, including locks, are stored.</para></entry>
-
-<entry colname="col4"><para>As specified in Samba makefile</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="5.5.2.1" id="ch05-SECT-5.2.1">
-<title>share modes</title>
-
-
-<para>The most primitive locks available to Samba are deny-mode locks, known as <firstterm>share modes</firstterm>
-<indexterm id="ch05-idx-969868-0"><primary>share modes</primary></indexterm>
-<indexterm id="ch05-idx-969868-1"><primary>SMB (Server Message Block)</primary><secondary>deny-mode locks</secondary></indexterm>, which are employed by programs such as text editors to avoid accidental overwriting of files. For reference, the deny-mode locks are listed in <link linkend="ch05-55885">Table 5.9</link>.</para>
-
-
-<table label="5.9" id="ch05-55885">
-<title>SMB Deny-Mode Locks </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Lock</para></entry>
-
-<entry colname="col2"><para>Description</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>DENY_NONE</literal></para></entry>
-
-<entry colname="col2"><para>Do not deny any other file requests.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>DENY_ALL</literal></para></entry>
-
-<entry colname="col2"><para>Deny all open requests on the current file.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>DENY_READ</literal></para></entry>
-
-<entry colname="col2"><para>Deny any read-only open requests on the current file.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>DENY_WRITE</literal></para></entry>
-
-<entry colname="col2"><para>Deny any write-only open requests on the current file.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>DENY_DOS</literal></para></entry>
-
-<entry colname="col2"><para>If opened for reading, others can read but cannot write to the file. If opened for writing, others cannot open the file at all.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>DENY_FCB</literal></para></entry>
-
-<entry colname="col2"><para>Obsolete.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.2" id="ch05-SECT-5.2.2">
-<title>locking</title>
-
-
-<para>The<indexterm id="ch05-idx-970616-0"><primary>locking option</primary></indexterm> <literal>locking</literal> option can be used to tell Samba to engage or disengage server-side byte-range locks on behalf of the client. Samba implements byte-range locks on the server side with normal Unix advisory locks and will consequently prevent other properly-behaved Unix processes from overwriting a locked byte range.</para>
-
-
-<para>This option can be specified per share as follows:</para>
-
-
-<programlisting>[accounting]
- locking = yes</programlisting>
-
-
-<para>If the <literal>locking</literal> option is set to <literal>yes</literal>, the requestor will be delayed until the holder of either type of lock releases it (or crashes). If, however, the option is set to <literal>no</literal>, no byte-range locks will be kept for the files, although requests to lock and unlock files will appear to succeed. The option is set to <literal>yes</literal> by default; however, you can turn this option off if you have read-only media.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.3" id="ch05-SECT-5.2.3">
-<indexterm id="ch05-idx-970617-0"><primary>strict locking option</primary></indexterm>
-<title>
-strict locking</title>
-
-
-<para>This option checks every file access for a byte-range lock on the range of bytes being accessed. This is typically not needed if a client adheres to all the locking mechanisms in place. This option is set to <literal>no</literal> by default; however, you can reset it per share as follows:</para>
-
-
-<programlisting>[accounting]
- strict locking = yes</programlisting>
-
-
-<para>If this option is set to <literal>yes</literal>, mandatory locks are enforced on any file with byte-range locks.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.4" id="ch05-SECT-5.2.4">
-<indexterm id="ch05-idx-970618-0"><primary>blocking locks option</primary></indexterm>
-<title>
-blocking locks</title>
-
-
-<para>Samba also supports <firstterm>blocking locks</firstterm>, a minor variant of range locks. Here, if the range of bytes is not available, the client specifies an amount of time that it's willing to wait. The server then caches the lock request, periodically checking to see if the file is available. If it is, it notifies the client; however, if time expires, Samba will tell the client that the request has failed. This strategy prevents the client from continually polling to see if the lock is available.</para>
-
-
-<para>You can disable this option per share as follows:</para>
-
-
-<programlisting>[accounting]
- blocking locks = no</programlisting>
-
-
-<para>When set to <literal>yes</literal>, blocking locks will be enforced on the file. If this option is set to <literal>no</literal>, Samba behaves as if normal locking mechanisms are in place on the file. The default is <literal>yes</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.5" id="ch05-SECT-5.2.5">
-<indexterm id="ch05-idx-970619-0"><primary>oplocks option</primary></indexterm>
-<title>
-oplocks</title>
-
-
-<para>This option enables or disables support for oplocks on the client. The option is enabled by default. However, you can disable it with the following command:</para>
-
-
-<programlisting>[data]
- oplocks = no</programlisting>
-
-
-<para>If you are in an extremely unstable network environment or have many clients that cannot take advantage of opportunistic locking, it may be better to shut this Samba feature off. Oplocks should be disabled if you are accessing the same files from both Unix applications (such as <emphasis>vi</emphasis> ) and SMB clients (unless you are lucky enough to have an operating system that supports kernel oplocks as discussed earlier).</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.6" id="ch05-SECT-5.2.6">
-<indexterm id="ch05-idx-970620-0"><primary>fake oplocks option</primary></indexterm>
-<title>
-fake oplocks</title>
-
-
-<para>Before opportunistic locking was available on Samba, the Samba daemons pretended to allow oplocks via the <literal>fake</literal> <literal>oplocks</literal> option. If this option was enabled, all clients were told that the file is available for opportunistic locking, and never warned of simultaneous access. This option is deprecated now that real oplocks are available on Samba.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.7" id="ch05-SECT-5.2.7">
-<indexterm id="ch05-idx-970621-0"><primary>kernel oplocks option</primary></indexterm>
-<title>
-kernel oplocks</title>
-
-
-<para>If a Unix application separate from Samba tries to update a file that Samba has oplocked to a Windows client, it will likely succeed (depending on the operating system) and both Samba and the client will never be aware of it. However, if the local Unix operating system supports it, Samba can warn it of oplocked files, which can suspend the Unix process, notify the client via Samba to write its copy back, and only then allow the open to complete. Essentially, this means that the operating system kernel on the Samba system has the ability to handle oplocks as well as Samba.</para>
-
-
-<para>You can enable this behavior with the <literal>kernel</literal> <literal>oplocks</literal> option, as follows:</para>
-
-
-<programlisting>[global]
- kernel oplocks = yes</programlisting>
-
-
-<para>Samba can automatically detect kernel oplocks and use them if present. At the time of this writing, this feature is supported only by SGI Irix 6.5.2f and later. However, Linux and FreeBSD support are expected in the near future. A system without kernel oplocks will allow the Unix process to update the file, but the client programs will notice the change only at a later time, if at all.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.8" id="ch05-SECT-5.2.8">
-<indexterm id="ch05-idx-970622-0"><primary>veto oplock files option</primary></indexterm>
-<title>
-veto oplock files</title>
-
-
-<para>You can provide a list of filenames that are never granted opportunistic locks with the <literal>veto</literal> <literal>oplock</literal> <literal>files</literal> option. This option can be set either globally or on a per-share basis. For example:</para>
-
-
-<programlisting>veto oplock files = /*.bat/*.htm/</programlisting>
-
-
-<para>The value of this option is a series of patterns. Each pattern entry must begin, end, or be separated from another with a slash ( / ) character, even if there is only one pattern listed. Asterisks can be used as a wildcard to represent zero or more characters. Questions marks can be used to represent exactly one character.</para>
-
-
-<para>We recommend that you disable oplocks on any files that are meant to be updated by Unix or are intended to be shared by several processes simultaneously.</para>
-</sect3>
-
-
-
-<sect3 role="" label="5.5.2.9" id="ch05-SECT-5.2.9">
-<indexterm id="ch05-idx-970623-0"><primary>lock directory option</primary></indexterm>
-<title>
-lock directory</title>
-
-
-<para>This option (sometimes called <literal>lock</literal> <literal>dir</literal>) specifies the location of a directory where Samba will store SMB deny-mode lock files. Samba stores other files in this directory as well, such as browse lists and its shared memory file. If WINS is enabled, the WINS database is written to this directory as well. The default for this option is specified in the Samba makefile; it is typically <filename>/usr/local/samba/var/locks</filename>. You can override this location as follows:</para>
-
-
-<programlisting>[global]
- lock directory = /usr/local/samba/locks</programlisting>
-
-
-<para>You typically would not need to override this option, unless you want to move the lock files to a more standardized location, such<indexterm id="ch05-idx-969871-0" class="endofrange" startref="ch05-idx-969867-0"/>
-<indexterm id="ch05-idx-969871-1" class="endofrange" startref="ch05-idx-969867-1"/> as<indexterm id="ch05-idx-969860-0" class="endofrange" startref="ch05-idx-969857-0"/>
-<indexterm id="ch05-idx-969860-1" class="endofrange" startref="ch05-idx-969857-1"/>
-<indexterm id="ch05-idx-969860-2"><primary>opportunistic locking</primary><seealso>oplocks</seealso></indexterm> <filename>/var/spool/locks</filename>.<indexterm id="ch05-idx-969562-0" class="endofrange" startref="ch05-idx-969559-1"/></para>
-</sect3>
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="6" id="SAMBA-CH-6">
-<title>Users, Security, and Domains </title>
-
-
-
-
-<para>This chapter discusses how to configure users with the Samba server. This topic may seem straightforward at first, but you'll soon discover that there are several ancillary problems that can crop up. One issue that Samba administrators have difficulty with is user authentication—password and security problems are by far the most common support questions on the Samba mailing lists. Learning why various authentication mechanisms work on certain architectures (and don't on others) can save you a tremendous amount of time testing and debugging Samba users in the future.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="6.1" id="ch06-92902">
-<title>Users and Groups</title>
-
-
-<para>
-<indexterm id="ch06-idx-967489-0" class="startofrange"><primary>users</primary></indexterm>
-<indexterm id="ch06-idx-967489-1" class="startofrange"><primary>groups</primary></indexterm>Before we start, we need to warn you up front that if you are connecting to Samba with a Windows 98 or NT 4.0 Workstation SP3, you need to configure your server for encrypted passwords before you can make a connection; otherwise, the clients will refuse to connect to the Samba server. This is because each of those Windows clients sends encrypted passwords, and Samba needs to be configured to expect and decrypt them. We'll show you how to set up Samba for this task later in the chapter, assuming you haven't already tackled this problem in <link linkend="SAMBA-CH-2">Chapter 2</link>.</para>
-
-
-<para>
-<indexterm id="ch06-idx-967590-0"><primary>users</primary><secondary>setting up</secondary></indexterm>
-<indexterm id="ch06-idx-967590-1"><primary>client users</primary><see>users</see></indexterm>Let's start with a single user. The easiest way to set up a client user is to create a Unix account (and <indexterm id="ch06-idx-967591-0"><primary>home directory, user's</primary></indexterm>home directory) for that individual on the server, and notify Samba of the user's existence. You can do the latter by creating a disk share that maps to the user's home directory in the Samba configuration file, and restricting access to that user with the <literal>valid</literal> <literal>users</literal> option. For example:</para>
-
-
-<programlisting>[dave]
- path = /home/dave
- comment = Dave's home directory
- writeable = yes
-<emphasis role="bold"> valid users = dave</emphasis></programlisting>
-
-
-<para>The <literal>valid</literal> <literal>users</literal> option lists the users that will be allowed to access the share. In this case, only the user <literal>dave</literal> is allowed to access the share. In the previous chapters, we specified that any user could access a disk share using the <literal>guest</literal> <literal>ok</literal> parameter. Because we don't wish to allow guest access, that option is absent here. We could grant both authenticated users and guest users access to a specific share if we wanted to. The difference between the two typically involves access rights for each of the files.</para>
-
-
-<para>Remember that you can abbreviate the user's home directory by using the <literal>%H</literal> variable. In addition, you can use the Unix username variable <literal>%u</literal> and/or the client username variable <literal>%U</literal> in your options as well. For example:</para>
-
-
-<programlisting>[dave]
- comment = %U home directory
- writeable = yes
- valid users = dave
- path = %H</programlisting>
-
-
-<para>Both of these examples work as long as the Unix user that Samba uses to represent the client has read/write access to the directory referenced by the <literal>path</literal> option. In other words, a client must first pass Samba's security mechanisms (e.g., encrypted passwords, the <literal>valid users</literal> option, etc.) as well as the normal Unix file and directory permissions of its Unix-side user <emphasis>before</emphasis> it can gain read/write access to a share.</para>
-
-
-<para>With a single user accessing a home directory, access permissions are taken care of when the operating system creates the user account. However, if you're creating a shared directory for group access, there are a few more steps you need to perform. Let's take a stab at a group share for the accounting department in the <emphasis>smb.conf</emphasis> file:</para>
-
-
-<programlisting>[accounting]
- comment = Accounting Department Directory
- writeable = yes
- valid users = @account
- path = /home/samba/accounting
- create mode = 0660
- directory mode = 0770</programlisting>
-
-
-<para>The first thing that you might notice we did differently is to specify <literal>@account</literal> as the valid user instead of one or more individual usernames. This is shorthand for saying that the valid users are represented by the Unix group <literal>account</literal>. These users will need to be added to the group entry <literal>account</literal> in the system group file ( <filename>/etc/group</filename> or equivalent) to be recognized as part of the group. Once they are, Samba will recognize those users as valid users for the share.</para>
-
-
-<para>In addition, you will need to create a <indexterm id="ch06-idx-967592-0"><primary>shares</primary><secondary>access to</secondary><tertiary>creating for groups</tertiary></indexterm>shared directory that the members of the group can access, which is pointed to by the <literal>path</literal> configuration option. Here are the Unix commands that create the shared directory for the accounting department (assuming <emphasis>/home/samba</emphasis> already exists):</para>
-
-
-<programlisting># <emphasis role="bold">mkdir /home/samba/accounting</emphasis># <emphasis role="bold">chgrp account /home/samba/accounting</emphasis># <emphasis role="bold">chmod 770 /home/samba/accounting</emphasis></programlisting>
-
-
-<para>There are two other options in this <filename>smb.conf</filename> example, both of which we saw in the previous chapter. These options are <literal>create</literal> <literal>mode</literal> and <literal>directory</literal> <literal>mode</literal>. These options set the maximum file and directory permissions that a new file or directory can have. In this case, we have denied all world access to the contents of this share. (This is reinforced by the <emphasis>chmod</emphasis> command, shown earlier.).</para>
-
-
-<sect2 role="" label="6.1.1" id="ch06-SECT-1.1">
-<title>The [ homes] Share</title>
-
-
-<para>Let's return to user shares for a moment. If we have several users to set up home directory shares for, we probably want to use the special <literal>[homes]</literal> share that we introduced in <link linkend="SAMBA-CH-5">Chapter 5</link>. With the <literal>[homes]</literal>
-<indexterm id="ch06-idx-967594-0"><primary sortas="homes share">[homes] share</primary></indexterm>
-<indexterm id="ch06-idx-967594-1"><primary>users</primary><secondary>shares for, setting up</secondary></indexterm> share, all we need to say is:</para>
-
-
-<programlisting>[homes]
- browsable = no
- writable = yes</programlisting>
-
-
-<para>The <literal>[homes]</literal> share is a special section of the Samba configuration file. If a user attempts to connect to an ordinary share that doesn't appear in the <filename>smb.conf</filename> file (such as specifying it with a UNC in Windows Explorer), Samba will search for a <literal>[homes]</literal> share. If one exists, the incoming share name is assumed to be a username and is queried as such in the password database ( <filename>/etc/passwd</filename> or equivalent) file of the Samba server. If it appears, Samba assumes the client is a Unix user trying to connect to his or her home directory.</para>
-
-
-<para>As an illustration, let's assume that <literal>sofia</literal> is attempting to connect to a share called [<literal>sofia]</literal> on the Samba server. There is no share by that name in the configuration file, but a <literal>[homes]</literal> share exists and user <literal>sofia</literal> is present in the password database, so Samba takes the following steps:</para>
-
-
-<orderedlist>
-<listitem><para>Samba creates a new disk share called <literal>[sofia]</literal> with the <literal>path</literal> specified in the <literal>[homes]</literal> section. If there is no <literal>path</literal> option specified in <literal>[homes]</literal>, Samba initializes it to her home directory.</para></listitem>
-<listitem><para>Samba initializes the new share's options from the defaults in <literal>[globals]</literal>, and any overriding options in <literal>[homes]</literal> with the exception of <literal>browseable</literal>.</para></listitem>
-<listitem><para>Samba connects <literal>sofia</literal>'s client to that share.</para></listitem>
-</orderedlist>
-
-<para>The <literal>[homes]</literal> share is a fast, painless way to create shares for your user community without having to duplicate the information from the password database file in the <filename>smb.conf</filename> file. It does have some peculiarities, however, that we need to point out:</para>
-
-
-<itemizedlist>
-<listitem><para>The <literal>[homes]</literal> section can represent any account on the machine, which isn't always desirable. For example, it can potentially create a share for <emphasis>root</emphasis>, <emphasis>bin</emphasis>, <emphasis>sys</emphasis>, <emphasis>uucp</emphasis>, and the like. (You can set a global <literal>invalid</literal> <literal>users</literal> option to protect against this.)</para></listitem>
-<listitem><para>The meaning of the <literal>browseable</literal> configuration option is different from other shares; it indicates only that a <literal>[homes]</literal> section won't show up in the local browse list, not that the <literal>[alice]</literal> share won't. When the <literal>[alice]</literal> section is created (after the initial connection), it will use the browsable value from the <literal>[globals]</literal> section for that share, not the value from <literal>[homes]</literal>.</para></listitem>
-</itemizedlist>
-
-<para>As we mentioned, there is no need for a path statement in <literal>[homes]</literal> if the users have Unix home directories in the server's <filename>/etc/passwd</filename> file. You should ensure that a valid home directory does exist, however, as Samba will not automatically create a home directory for a user, and will refuse a tree connect if the user's directory does not exist or is not accessible.<indexterm id="ch06-idx-967568-0" class="endofrange" startref="ch06-idx-967489-0"/>
-<indexterm id="ch06-idx-967568-1" class="endofrange" startref="ch06-idx-967489-1"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="6.2" id="ch06-27678">
-<title>Controlling Access to Shares</title>
-
-
-<para>
-<indexterm id="ch06-idx-967497-0" class="startofrange"><primary>shares</primary><secondary>access to</secondary><tertiary>controlling</tertiary></indexterm>
-<indexterm id="ch06-idx-967497-1" class="startofrange"><primary>security</primary><secondary>restricting access to shares</secondary></indexterm>Often you will need to restrict the users who can access a specific share for security reasons. This is very easy to do with Samba since it contains a wealth of options for creating practically any security configuration. Let's introduce a few configurations that you might want to use in your own Samba setup.</para>
-
-
-<warning role="ora">
-<para>Again, if you are connecting with Windows 98 or NT 4.0 with Service Pack 3 (or above), those clients will send encrypted passwords to the Samba server. If Samba is not configured for this, it will continually refuse the connection. This chapter describes how to set up Samba for encrypted passwords. See <link linkend="ch06-61393">Section 6.4</link>.</para>
-
-</warning>
-
-<para>We've seen what happens when you specify valid users. However, you are also allowed to specify a list of invalid <indexterm id="ch06-idx-967599-0"><primary>users</primary><secondary>invalid, specifying</secondary></indexterm>users—users who should never be allowed access to Samba or its shares. This is done with the <literal>invalid</literal> <literal>users</literal> option. We hinted at one frequent use of this option earlier: a global default with the <literal>[homes]</literal> section to ensure that various system users and superusers cannot be forged for access. For example:</para>
-
-
-<programlisting>[global]
- invalid users = root bin daemon adm sync shutdown \
- halt mail news uucp operator gopher
- auto services = dave peter bob
-
-[homes]
- browsable = no
- writeable = yes</programlisting>
-
-
-<para>The <literal>invalid</literal> <literal>users</literal> option, like <literal>valid</literal> <literal>users</literal>, can take group names as well as usernames. In the event that a user or group appears in both lists, the <literal>invalid</literal> <literal>users</literal> option takes precedence and the user or group will be denied access to the share.</para>
-
-
-<para>At the other end of the spectrum, you can explicitly specify users who will be allowed <indexterm id="ch06-idx-967600-0"><primary>root user</primary><secondary>access</secondary></indexterm>
-<indexterm id="ch06-idx-967600-1"><primary>users</primary><secondary>allowing superuser (root) access to</secondary></indexterm>
-<indexterm id="ch06-idx-967600-2"><primary>superuser</primary><see>root user</see></indexterm>superuser (root) access to a share with the <literal>admin</literal> <literal>users</literal> option. An example follows:</para>
-
-
-<programlisting>[sales]
- path = /home/sales
- comment = Fiction Corp Sales Data
- writeable = yes
- valid users = tom dick harry
- admin users = mike</programlisting>
-
-
-<para>This option takes both group names and usernames. In addition, you can specify NIS netgroups by preceding them with an <literal>@</literal> as well; if the netgroup is not found, Samba will assume that you are referring to a standard Unix group.</para>
-
-
-<para>Be careful if you assign an entire <indexterm id="ch06-idx-967601-0"><primary>groups</primary><secondary>administrative privileges for</secondary></indexterm>group administrative privileges to a share. The Samba team highly recommends you avoid using this option, as it essentially gives root access to the specified users or groups for that share.</para>
-
-
-<para>If you wish to force <indexterm id="ch06-idx-967602-0"><primary>read-only/read-write access</primary></indexterm>
-<indexterm id="ch06-idx-967602-1"><primary>users</primary><secondary>read-only/read-write access</secondary></indexterm>read-only or read-write access to users who access a share, you can do so with the <literal>read</literal> <literal>list</literal> and <literal>write</literal> <literal>list</literal> options, respectively. These options can be used on a per-share basis to restrict a writable share or grant write access to specific users in a read-only share, respectively. For example:</para>
-
-
-<programlisting>[sales]
- path = /home/sales
- comment = Fiction Corp Sales Data
- read only = yes
- write list = tom dick</programlisting>
-
-
-<para>The <literal>write</literal> <literal>list</literal> option cannot override <indexterm id="ch06-idx-968868-0"><primary>Unix</primary><secondary>permissions, share write access and</secondary></indexterm>Unix permissions. If you've created the share without giving the write-list user write permission on the Unix system, he or she will be denied write access regardless of the setting of <literal>write</literal> <literal>list</literal>.</para>
-
-
-<sect2 role="" label="6.2.1" id="ch06-SECT-2.1">
-<title>Guest Access</title>
-
-
-<para>
-<indexterm id="ch06-idx-967606-0" class="startofrange"><primary>guest access</primary></indexterm>As mentioned earlier, you can specify users who have guest access to a share. The options that control guest access are easy to work with. The first option, <literal>guest</literal> <literal>account</literal>, specifies the Unix account that guest users should be assigned when connecting to the Samba server. The default value for this is set during compilation, and is typically <literal>nobody</literal>. However, you may want to reset the guest user to <literal>ftp</literal> if you have trouble accessing various system services.</para>
-
-
-<para>If you wish to restrict access in a share only to guests—in other words, all clients connect as the guest account when accessing the share—you can use the <literal>guest</literal> <literal>only</literal> option in conjunction with the <literal>guest ok</literal> option, as shown in the following example:</para>
-
-
-<programlisting>[sales]
- path = /home/sales
- comment = Fiction Corp Sales Data
- writeable = yes
- guest ok = yes
- guest account = ftp
- guest only = yes</programlisting>
-
-
-<para>Make sure you specify <literal>yes</literal> for both <literal>guest only</literal> and <literal>guest ok</literal> in this scenario; otherwise, Samba will not use the guest acount that you specify.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.2.2" id="ch06-SECT-2.2">
-<title>Access Control Options</title>
-
-
-<para>
-<indexterm id="ch06-idx-967608-0" class="startofrange"><primary>access-control options (shares)</primary></indexterm><link linkend="ch06-28077">Table 6.1</link> summarizes the options that you can use to control access to shares.</para>
-
-
-<table label="6.1" id="ch06-28077">
-<title>Share-level Access Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>admin users</literal></para></entry>
-
-<entry colname="col2"><para>string (list of usernames)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of users who can perform operations as root.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>valid users</literal></para></entry>
-
-<entry colname="col2"><para>string (list of usernames)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of users that can connect to a share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>invalid users</literal></para></entry>
-
-<entry colname="col2"><para>string (list of usernames)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of users that will be denied access to a share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>read list</literal></para></entry>
-
-<entry colname="col2"><para>string (list of usernames)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of users that have read-only access to a writable share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>write list</literal></para></entry>
-
-<entry colname="col2"><para>string (list of usernames)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of users that have read-write access to a read-only share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max connections</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Indicates the maximum number of connections for a share at a given time.</para></entry>
-
-<entry colname="col4"><para><literal>0</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>guest only (only guest)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Specifies that this share allows only guest access.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>guest account</literal></para></entry>
-
-<entry colname="col2"><para>string (name of account)</para></entry>
-
-<entry colname="col3"><para>Names the Unix account that will be used for guest access.</para></entry>
-
-<entry colname="col4"><para><literal>nobody</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="6.2.2.1" id="ch06-SECT-2.2.1">
-<indexterm id="ch06-idx-969448-0"><primary>admin users option</primary></indexterm>
-<title>
-admin users</title>
-
-
-<para>This option specifies a list of users that perform file operations as if they were <literal>root</literal>. This means that they can modify or destroy any other user's work, no matter what the permissions. Any files that they create will have root ownership and will use the default group of the admin user. The <literal>admin</literal> <literal>users</literal> option is used to allow PC users to act as administrators for particular shares. We urge you to avoid this option.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.2.2.2" id="ch06-SECT-2.2.2">
-<indexterm id="ch06-idx-969449-0"><primary>alid users option</primary></indexterm>
-<indexterm id="ch06-idx-969449-1"><primary>invalid users option</primary></indexterm>
-<title>v
-alid users and invalid users</title>
-
-
-<para>These two options let you enumerate the users and groups who are granted or denied access to a particular share. You can enter a list of comma-delimited users, or indicate an NIS or Unix group name by prefixing the name with an at-sign (<literal>@</literal>).</para>
-
-
-<para>The important rule to remember with these options is that any name or group in the <literal>invalid</literal> <literal>users</literal> list will <emphasis>always</emphasis> be denied access, even if it is included (in any form) in the <literal>valid</literal> <literal>users</literal> list. By default, neither option has a value associated with it. If both options have no value, any user is allowed to access the share.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.2.2.3" id="ch06-SECT-2.2.3">
-<indexterm id="ch06-idx-969450-0"><primary>read list option</primary></indexterm>
-<indexterm id="ch06-idx-969450-1"><primary>write list option</primary></indexterm>
-<title>
-
-read list and write list</title>
-
-
-<para>Like the <literal>valid</literal> <literal>users</literal> <literal>and</literal> <literal>invalid</literal> <literal>users</literal> options, this pair of options specifies which users have read-only access to a writeable share and read-write access to a read-only share, respectively. The value of either options is a list of users. <literal>read</literal> <literal>list</literal> overrides any other Samba permissions granted—as well as Unix file permissions on the server system—to deny users write access. <literal>write</literal> <literal>list</literal> overrides other Samba permissions to grant write access, but cannot grant write access if the user lacks write permissions for the file on the Unix system. You can specify NIS or Unix group names by prefixing the name with an at sign (such as <literal>@users</literal>). Neither configuration option has a default value associated with it.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.2.2.4" id="ch06-SECT-2.2.4">
-<indexterm id="ch06-idx-969451-0"><primary>max connections option</primary></indexterm>
-<title>
-max connections</title>
-
-
-<para>This option specifies the maximum number of client connections that a share can have at any given time. Any connections that are attempted after the maximum is reached will be rejected. The default value is <literal>0</literal>, which means that an unlimited number of connections are allowed. You can override it per share as follows:</para>
-
-
-<programlisting>[accounting]
- max connections = 30</programlisting>
-
-
-<para>This option is useful in the event that you need to limit the number of users who are accessing a licensed program or piece of data concurrently.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.2.2.5" id="ch06-SECT-2.2.5">
-<indexterm id="ch06-idx-969452-0"><primary>guest only option</primary></indexterm>
-<title>
-guest only</title>
-
-
-<para>This share-level option (sometimes called <literal>only</literal> <literal>guest</literal>) forces a connection to a share to be performed with the user specified by the <literal>guest</literal> <literal>account</literal> option. The share to which this is applied must explicitly specify <literal>guest</literal> <literal>ok</literal> <literal>=</literal> <literal>yes</literal> in order for this option to be recognized by Samba. The default value for this option is <literal>no</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.2.2.6" id="ch06-SECT-2.2.6">
-<indexterm id="ch06-idx-969453-0"><primary>guest account option</primary></indexterm>
-<title>
-guest account</title>
-
-
-<para>This option specifies the name of account to be used for guest access to shares in Samba. The default for this option varies from system to system, but it is often set to <literal>nobody</literal>. Some default user accounts have trouble connecting as guest users. If that occurs on your system, the Samba team recommends using the ftp account as the guest<indexterm id="ch06-idx-967617-0" class="endofrange" startref="ch06-idx-967608-0"/> user.<indexterm id="ch06-idx-967607-0" class="endofrange" startref="ch06-idx-967606-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.2.3" id="ch06-SECT-2.3">
-<title>Username Options</title>
-
-
-<para>
-<indexterm id="ch06-idx-967622-0" class="startofrange"><primary>usernames</primary><secondary>options for</secondary></indexterm><link linkend="ch06-82964">Table 6.2</link> shows two additional options that Samba can use to correct for incompatibilities in usernames between Windows and Unix.</para>
-
-
-<table label="6.2" id="ch06-82964">
-<title>Username Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>username map</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Sets the name of the username mapping file.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>username level</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Indicates the number of capital letters to use when trying to match a username.</para></entry>
-
-<entry colname="col4"><para><literal>0</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="6.2.3.1" id="ch06-SECT-2.3.1">
-<indexterm id="ch06-idx-969456-0"><primary>username map option</primary></indexterm>
-<title>
-username map</title>
-
-
-<para>
-<indexterm id="ch06-idx-967632-0"><primary>usernames</primary><secondary>SMB vs. Unix networks</secondary></indexterm>
-<indexterm id="ch06-idx-967632-1"><primary>SMB (Server Message Block)</primary><secondary>networks</secondary><tertiary>usernames and</tertiary></indexterm>
-<indexterm id="ch06-idx-967632-2"><primary>Unix</primary><secondary>networks, usernames and</secondary></indexterm>Client usernames on an SMB network can be relatively large (up to 255 characters), while usernames on a Unix network often cannot be larger than eight characters. This means that an individual user may have one username on a client and another (shorter) one on the Samba server. You can get past this issue by<firstterm> mapping</firstterm> a free-form client username to a Unix username of eight or fewer characters. It is placed in a standard text file, using a format that we'll describe shortly. You can then specify the pathname to Samba with the global <literal>username</literal> <literal>map</literal> option. Be sure to restrict access to this file; make the root user the file's owner and deny write access to others. Otherwise, an untrusted user who can access the file can easily map their client username to the root user of the Samba server.</para>
-
-
-<para>You can specify this option as follows:</para>
-
-
-<programlisting>[global]
- username map = /etc/samba/usermap.txt</programlisting>
-
-
-<para>Each of the entries in the username map file should be listed as follows: the Unix username, followed by an equal sign (<literal>=</literal>), followed by one or more whitespace-separated SMB client usernames. Note that unless instructed otherwise, (i.e., a guest connection), Samba will expect both the client and the server user to have the same password. You can also map NT groups to one or more specific Unix groups using the <literal>@</literal> sign. Here are some examples:</para>
-
-
-<programlisting>jarwin = JosephArwin
-manderso = MarkAnderson
-users = @account</programlisting>
-
-
-<para>Also, you can use the asterisk to specify a wildcard that matches any free-form client username as an entry in the username map file:</para>
-
-
-<programlisting>nobody = *</programlisting>
-
-
-<para>Comments in the file can be specified as lines beginning with (#) and (<literal>;</literal>).</para>
-
-
-<para>Note that you can also use this file to redirect one Unix user to another user. Be careful if you do so because Samba and your client may not notify the user that the mapping has been made and Samba may be expecting a different password.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.2.3.2" id="ch06-SECT-2.3.2">
-<indexterm id="ch06-idx-969459-0"><primary>username level option</primary></indexterm>
-<title>
-username level</title>
-
-
-<para>
-<indexterm id="ch06-idx-967633-0"><primary>usernames</primary><secondary>case sensitivity and</secondary></indexterm>
-<indexterm id="ch06-idx-967633-1"><primary>case sensitivity</primary><secondary>usernames and</secondary></indexterm>SMB clients (such as Windows) will often send usernames in SMB connection requests entirely in capital letters; in other words, client usernames are not necessarily case sensitive. On a Unix server, however, usernames <emphasis>are</emphasis> case sensitive: the user <literal>ANDY</literal> is different from the user <literal>andy</literal>. By default, Samba attacks this problem by doing the following:</para>
-
-
-<orderedlist>
-<listitem><para>Checking for a user account with the exact name sent by the client</para></listitem>
-<listitem><para>Testing the username in all lowercase letters</para></listitem>
-<listitem><para>Testing the username in lowercase letters with only the first letter capitalized</para></listitem>
-</orderedlist>
-
-<para>If you wish to have Samba attempt more combinations of uppercase and lowercase letters, you can use the <literal>username</literal> <literal>level</literal> global configuration option. This option takes an integer value that specifies how many letters in the username should be capitalized when attempting to connect to a share. You can specify this options as follows:</para>
-
-
-<programlisting>[global]
- username level = 3</programlisting>
-
-
-<para>In this case, Samba will then attempt all permutations of usernames it can compute having three capital letters. The larger the number, the more computations Samba will have to perform to match the username and the longer the authentication wil<indexterm id="ch06-idx-967629-0" class="endofrange" startref="ch06-idx-967622-0"/>l take.<indexterm id="ch06-idx-967624-0" class="endofrange" startref="ch06-idx-967497-0"/>
-<indexterm id="ch06-idx-967624-1" class="endofrange" startref="ch06-idx-967497-1"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="6.3" id="ch06-88596">
-<title>Authentication Security</title>
-
-
-<para>
-<indexterm id="ch06-idx-967505-0" class="startofrange"><primary>authentication</primary></indexterm>
-<indexterm id="ch06-idx-967505-1" class="startofrange"><primary>security</primary></indexterm>At this point, we should discuss how Samba authenticates users. Each user who attempts to connect to a share that does not allow guest access must provide a password to make a successful connection. What Samba does with that password—and consequently the strategy Samba will use to handle user authentication—is the arena of the <literal>security</literal> configuration option. There are currently four <indexterm id="ch06-idx-967637-0"><primary>security</primary><secondary>levels of</secondary></indexterm>security levels that Samba supports on its network: <firstterm>share</firstterm>, <firstterm>user</firstterm>, <firstterm>server</firstterm>, and <firstterm>domain</firstterm>.</para>
-
-
-<variablelist>
-<varlistentry><term>
-<indexterm id="ch06-idx-967638-0"><primary>share-level security</primary></indexterm>Share-level security</term>
-<listitem><para>Each share in the workgroup has one or more passwords associated with it. Anyone who knows a valid password for the share can access it.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="ch06-idx-967639-0"><primary>user-level security</primary></indexterm>User-level security</term>
-<listitem><para>Each share in the workgroup is configured to allow access from certain users. With each initial tree connection, the Samba server verifies users and their passwords to allow them access to the share.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Server-level security</term>
-<listitem><para>This is the same as user-level security, except that the Samba server uses a separate SMB server to validate users and their passwords before granting access to the share.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>
-<indexterm id="ch06-idx-967641-0"><primary>domain-level security</primary></indexterm>Domain-level security</term>
-<listitem><para>Samba becomes a member of a Windows domain and uses the domain's <indexterm id="ch06-idx-967642-0"><primary>PDC (primary domain controller)</primary><secondary>domain-level security and</secondary></indexterm>primary domain controller (PDC) to perform authentication. Once authenticated, the user is given a special token that allows him or her access to any share with appropriate access rights. With this token, the PDC will not have to revalidate the user's password each time he or she attempts to access another share within the domain.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>Each of these security policies can be implemented with the global <literal>security</literal> option, as shown in <link linkend="ch06-73905">Table 6.3</link>.</para>
-
-
-<table label="6.3" id="ch06-73905">
-<title>Security Option </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>security</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch06-idx-968919-0"><primary>security</primary><secondary>options for</secondary></indexterm><literal>domain</literal>, <literal>server</literal>, <literal>share</literal>, or <literal>user</literal></para></entry>
-
-<entry colname="col3"><para>Indicates the type of security that the Samba server will use.</para></entry>
-
-<entry colname="col4"><para><literal>user</literal> (Samba 2.0) or <literal>share</literal> (Samba 1.9)</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="6.3.1" id="ch06-SECT-3.1">
-<title>Share-level Security</title>
-
-
-<para>
-<indexterm id="ch06-idx-967644-0" class="startofrange"><primary>share-level security</primary></indexterm>
-<indexterm id="ch06-idx-967644-1" class="startofrange"><primary>security</primary><secondary>share-level</secondary></indexterm>With share-level security, each share has one or more passwords associated with it. This differs from the other modes of security in that there are no restrictions as to whom can access a share, as long as that individual knows the correct password. Shares often have multiple passwords. For example, one password may grant read-only access, while another may grant read-write access, and so on. Security is maintained as long as unauthorized users do not discover the password for a share to which they shouldn't have access.</para>
-
-
-<para>
-<indexterm id="ch06-idx-967666-0"><primary>OS/2, support for share-level security</primary></indexterm>
-<indexterm id="ch06-idx-967666-1"><primary>Windows 95/98</primary><secondary>share-level security, support for</secondary></indexterm>OS/2 and Window 95/98 both support share-level security on their resources. You can set up share-level security with Windows 95/98 by first enabling share-level security using the Access Control tab of the Network Control Panel dialog. Then select the Share-level Access Control radio button (which deselects the user-level access control radio button), as shown in <link linkend="ch06-33100">Figure 6.1</link>, and press the OK button.</para>
-
-
-<figure label="6.1" id="ch06-33100">
-<title>Selecting share-level security on a Windows machine</title>
-
-<graphic width="502" depth="284" fileref="figs/sam.0601.gif"></graphic>
-</figure>
-
-<para>Next, right click on a resource—such as a hard drive or a CD-ROM—and select the Properties menu item. This will bring up the Resource Properties dialog box. Select the Sharing tab at the top of the dialog box and enable the resource as Shared As. From here, you can configure how the shared resource will appear to individual users, as well as assigning whether the resource will appear as read-only, read-write, or a mix, depending on the password that is supplied.</para>
-
-
-<para>You might be thinking that this security model is not a good fit for Samba—and you would be right. In fact, if you set the <literal>security</literal> <literal>=</literal> <literal>share</literal> option in the Samba configuration file, Samba will still reuse the username/passwords combinations in the system password files to authenticate access. More precisely, Samba will take the following steps when a client requests a connection using <indexterm id="ch06-idx-967667-0"><primary>share-level security</primary><secondary>steps in taken by Samba</secondary></indexterm>share-level security:</para>
-
-
-<orderedlist>
-<listitem><para>When a connection is requested, Samba will accept the password and (if sent) the username of the client.</para></listitem>
-<listitem><para>If the share is <literal>guest</literal> <literal>only </literal>, the user is immediately granted access to the share with the rights of the user specified by the <literal>guest</literal> <literal>account</literal> parameter; no password checking is performed.</para></listitem>
-<listitem><para>For other shares, Samba appends the username to a list of users who are allowed access to the share. It then attempts to validate the password given in association with that username. If successful, Samba grants the user access to the share with the rights assigned to that user. The user will not need to authenticate again unless a <literal>revalidate</literal> <literal>=</literal> <literal>yes</literal> option has been set inside the share.</para></listitem>
-<listitem><para>If the authentication is unsuccessful, Samba will attempt to validate the password against the list of users it has previously compiled throughout the attempted connections, as well as any specified under the share in the configuration file. If the password does not match any usernames (as specified in the system password file, typically <filename>/etc/passwd </filename>), the user is not granted access to the share under that username.</para></listitem>
-<listitem><para>However, if the share has a <literal>guest</literal> <literal>ok</literal> or <literal>public</literal> option set, the user will default to access with the rights of the user specified by the <literal>guest</literal> <literal>account</literal> option.</para></listitem>
-</orderedlist>
-
-<para>You can indicate in the configuration file which users should be initially placed on the share-level security user list by using the <literal>username</literal> configuration option, as shown below:</para>
-
-
-<programlisting>[global]
- security = share
-[accounting1]
- path = /home/samba/accounting1
- guest ok = no
- writable = yes
- username = davecb, pkelly, andyo</programlisting>
-
-
-<para>Here, when a user attempts to connect to a share, Samba will verify the password that was sent against each of the users in its own list, in addition to the passwords of users <literal>davecb</literal>, <literal>pkelly</literal>, and <literal>andyo</literal>. If any of the passwords match, the connection will be verified and the user will be allowed. Otherwise, connection to the specific share will fail.</para>
-
-
-<sect3 role="" label="6.3.1.1" id="ch06-SECT-3.1.1">
-<indexterm id="ch06-idx-967668-0"><primary>share-level security</primary><secondary>options for</secondary></indexterm>
-<indexterm id="ch06-idx-967668-1"><primary>security</primary><secondary>share-level</secondary><tertiary>options for</tertiary></indexterm>
-<title>
-
-Share Level Security Options</title>
-
-
-<para><link linkend="ch06-80998">Table 6.4</link> shows the options typically associated with share-level security.</para>
-
-
-<table label="6.4" id="ch06-80998">
-<title>Share-Level Access Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>only user</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Indicates whether usernames specified by <literal>username</literal> will be the only ones allowed.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>username </literal>(user or users)</para></entry>
-
-<entry colname="col2"><para>string (list of usernames)</para></entry>
-
-<entry colname="col3"><para>Specifies a list of users against which a client's password will be tested.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect3>
-
-
-
-<sect3 role="" label="6.3.1.2" id="ch06-SECT-3.1.2">
-<title>only user</title>
-
-
-<para>This boolean option indicates whether Samba will allow connections to a share using share-level security based solely on the individuals specified in the <literal>username</literal> option, instead of those users compiled on Samba's internal list. The default value for this option is <literal>no</literal>. You can override it per share as follows:</para>
-
-
-<programlisting>[global]
- security = share
-[data]
- username = andy, peter, valerie
- only user = yes</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="6.3.1.3" id="ch06-SECT-3.1.3">
-<indexterm id="ch06-idx-969462-0"><primary>username option</primary></indexterm>
-<title>
-username</title>
-
-
-<para>This option presents a list of users against which Samba will test a connection password to allow access. It is typically used with clients that have share-level security to allow connections to a particular service based solely on a qualifying password—in this case, one that matches a password set up for a specific user:</para>
-
-
-<programlisting>[global]
- security = share
-[data]
- username = andy, peter, terry</programlisting>
-
-
-<para>We recommend against using this option unless you are implementing a Samba server with share-level security.<indexterm id="ch06-idx-967645-0" class="endofrange" startref="ch06-idx-967644-0"/>
-<indexterm id="ch06-idx-967645-1" class="endofrange" startref="ch06-idx-967644-1"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.3.2" id="ch06-SECT-3.2">
-<title>User-level Security</title>
-
-
-<para>
-<indexterm id="ch06-idx-967646-0"><primary>user-level security</primary></indexterm>
-<indexterm id="ch06-idx-967646-1"><primary>security</primary><secondary>user-level</secondary></indexterm>The preferred mode of security with Samba is <firstterm>user-level security</firstterm>. With this method, each share is assigned specific users that can access it. When a user requests a connection to a share, Samba authenticates by validating the given username and password with the authorized users in the configuration file and the passwords in the password database of the Samba server. As mentioned earlier in the chapter, one way to isolate which users are allowed access to a specific <indexterm id="ch06-idx-967676-0"><primary>shares</primary><secondary>option for identifying users allowed access to</secondary></indexterm>share is by using the <literal>valid</literal> <literal>users</literal> option for each share:</para>
-
-
-<programlisting>[global]
- security = user
-[accounting1]
- writable = yes
- valid users = bob, joe, sandy</programlisting>
-
-
-<para>Each of the users listed will be allowed to connect to the share if the password provided matches the password stored in the system password database on the server. Once the initial authentication succeeds, the user will not need to re-enter a password again to access that share unless the <literal>revalidate</literal> <literal>=</literal> <literal>yes</literal> option has been set.</para>
-
-
-<para>
-<indexterm id="ch06-idx-967677-0"><primary>passwords</primary><secondary>user-level security and</secondary></indexterm>Passwords can be sent to the Samba server in either an encrypted or a non-encrypted format. If you have both types of systems on your network, you should ensure that the passwords represented by each user are stored both in a traditional account database and Samba's encrypted password database. This way, authorized users can gain access to their shares from any type of client.<footnote label="1" id="ch06-pgfId-968956">
-
-
-<para>Having both encrypted and non-encrypted password clients on your network is another reason why Samba allows you to include (or not include) various options in the Samba configuration file based on the client operating system or machine name variables.</para>
-
-
-</footnote> However, we recommend that you move your system to encrypted passwords and abandon non-encrypted passwords if security is an issue. <link linkend="ch06-61393">Section 6.4</link> in this chapter explains how to use encrypted as well as non-encrypted passwords.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.3.3" id="ch06-SECT-3.3">
-<title>Server-level Security</title>
-
-
-<para>
-<indexterm id="ch06-idx-967648-0"><primary>server-level security</primary></indexterm>
-<indexterm id="ch06-idx-967648-1"><primary>security</primary><secondary>server-level</secondary></indexterm>Server-level security is similar to user-level security. However, with server-level security, Samba delegates password authentication to another <indexterm id="ch06-idx-967679-0"><primary>SMB (Server Message Block)</primary><secondary>password server</secondary></indexterm>SMB password server, typically another Samba server or a Windows NT Server acting as a <indexterm id="ch06-idx-967680-0"><primary>PDC (primary domain controller)</primary><secondary>sever-level security and</secondary></indexterm>PDC on the network. Note that Samba still maintains its list of shares and their configuration in its <filename>smb.conf</filename> file. When a client attempts to make a connection to a particular share, Samba validates that the user is indeed authorized to connect to the share. Samba will then attempt to validate the password by contacting the SMB password server through a known protocol and presenting the username and password to the SMB password server. If the password is accepted, a session will be established with the client. See <link linkend="ch06-89929">Figure 6.2</link> for an illustration of this setup.</para>
-
-
-<figure label="6.2" id="ch06-89929">
-<title>A typical system setup using server level security</title>
-
-<graphic width="502" depth="177" fileref="figs/sam.0602.gif"></graphic>
-</figure>
-
-<para>You can configure Samba to use a separate password server under server-level security with the use of the <literal>password</literal> <literal>server</literal> global configuration option, as follows:</para>
-
-
-<programlisting>[global]
- security = server
- password server = PHOENIX120 HYDRA134</programlisting>
-
-
-<para>Note that you can specify more than one machine as the target of the <literal>password</literal> <literal>server </literal>; Samba will move down the list of servers in the event that its first choice is unreachable. The servers identified by the <literal>password</literal> <literal>server</literal> option are given as NetBIOS names, not their DNS names or equivalent IP addresses. Also, if any of the servers reject the given password, the connection will automatically fail—Samba will not attempt another server.</para>
-
-
-<para>One caveat: when using this option, you will still need an account representing that user on the regular Samba server. This is because the Unix operating system needs a username to perform various I/O operations. The preferable method of handling this is to give the user an account on the Samba server but disable the account's password by replacing it in the system password file (e.g., <filename>/etc/passwd </filename>) with an <indexterm id="ch06-idx-967681-0"><primary>asterisk (*), in system password file</primary></indexterm>
-<indexterm id="ch06-idx-967681-1"><primary>* (asterisk)</primary></indexterm>asterisk (*).</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.3.4" id="ch06-SECT-3.4">
-<title>Domain-level Security</title>
-
-
-<para>
-<indexterm id="ch06-idx-967649-0" class="startofrange"><primary>domain-level security</primary></indexterm>
-<indexterm id="ch06-idx-967649-1" class="startofrange"><primary>security</primary><secondary>domain-level</secondary></indexterm>Domain-level security is similar to server-level security. However, with domainlevel security, the Samba server is acting as a member of a Windows domain. Recall from <link linkend="ch01-48078">Chapter 1</link> that each domain has a <firstterm>domain controller</firstterm>
-<indexterm id="ch06-idx-967685-0"><primary>domain controllers</primary></indexterm>, which is usually a Windows NT server offering password authentication. Including these controllers provides the workgroup with a definitive password server. The domain controllers keep track of users and passwords in their own <indexterm id="ch06-idx-967688-0"><primary>SAM (security account manager)</primary></indexterm>
-<indexterm id="ch06-idx-967688-1"><primary>security account manager (SAM)</primary></indexterm>security authentication module (SAM), and authenticates each user when he or she first logs on and wishes to access another machine's shares.</para>
-
-
-<para>As mentioned earlier in this chapter, Samba has a similar ability to offer user-level security, but this option is Unix-centric and assumes that the authentication occurs via <indexterm id="ch06-idx-967689-0"><primary>Unix</primary><secondary>password files</secondary></indexterm>Unix password files. If the Unix machine is part of a <indexterm id="ch06-idx-967690-0"><primary>NIS/NIS+ protocol</primary></indexterm>NIS or NIS+ domain, Samba will authenticate the users transparently against a shared password file, in typical Unix fashion. Samba then provides access to the NIS or NIS+ domain from Windows. There is, of course, no relationship between the NIS concept of a domain and the Windows concept of a domain.</para>
-
-
-<para>
-<indexterm id="ch06-idx-967696-0"><primary>domains</primary><secondary>Windows</secondary><tertiary>authentication</tertiary></indexterm>
-<indexterm id="ch06-idx-967696-1"><primary>authentication</primary><secondary>NT domain</secondary></indexterm>With domain-level security, we now have the option of using the native NT mechanism. This has a number of advantages:</para>
-
-
-<itemizedlist>
-<listitem><para>It provides far better integration with NT: there are fewer "kludges" in the <filename>smb.conf</filename> options dealing with domains than with most Windows features. This allows more extensive use of NT management tools, such as the User Manager for Domains tool allowing PC support individuals to treat Samba servers as if they were large NT machines.</para></listitem>
-<listitem><para>With the better integration comes protocol and code cleanups, allowing the Samba team to track the evolving NT implementation. NT Service Pack 4 corrects several problems in the protocol, and Samba's better integration makes it easier to track and adapt to these changes.</para></listitem>
-<listitem><para>There is less overhead on the PDC because there is one less permanent network connection between it and the Samba server. Unlike the protocol used by the <literal>security</literal> <literal>=</literal> <literal>server</literal> option, the Samba server can make a Remote Procedure Call (RPC) call only when it needs authentication information. It can not keep a connection permanently up just for that.</para></listitem>
-<listitem><para>Finally, the NT domain authentication scheme returns the full set of user attributes, not just success or failure. The attributes include a longer, more network-oriented version of the Unix uid, NT groups, and other information. This includes:</para>
-
-<itemizedlist>
-<listitem><para>Username</para></listitem>
-<listitem><para>Full name</para></listitem>
-<listitem><para>Description</para></listitem>
-<listitem><para>Security identifier (a domain-wide extension of the Unix uid)</para></listitem>
-<listitem><para>NT group memberships</para></listitem>
-<listitem><para>Logon hours, and whether to force the user to log out immediately</para></listitem>
-<listitem><para>Workstations the user is allowed to use</para></listitem>
-<listitem><para>Account expiration date</para></listitem>
-<listitem><para>Home directory</para></listitem>
-<listitem><para>Login script</para></listitem>
-<listitem><para>Profile</para></listitem>
-<listitem><para>Account type</para></listitem>
-</itemizedlist></listitem>
-<listitem><para>The Samba developers used domain-level security in Samba version 2.0.4 to add and delete domain <indexterm id="ch06-idx-967702-0"><primary>users</primary><secondary>domain, semi-automatic deletion</secondary></indexterm>users on Samba servers semi-automatically. In addition, it adds room for other NT-like additions, such as supporting access control lists and changing permissions of files from the client.</para></listitem>
-</itemizedlist>
-
-<para>The advantage to this approach is less administration; there is only one authentication database to keep synchronized. The only local administration required on the Samba server will be creating directories for users to work in and <filename>/etc/passwd</filename> entries to keep their UIDs and groups in.</para>
-
-
-<sect3 role="" label="6.3.4.1" id="ch06-SECT-3.4.1">
-<title>Adding a Samba server to a Windows NT Domain</title>
-
-
-<para>If you already have an NT <indexterm id="ch06-idx-967704-0"><primary>domains</primary><secondary>adding Samba server to Windows NT domain</secondary></indexterm>domain, you can easily add a Samba server to it. First, you will need to stop the Samba daemons. Then, add the Samba server to the NT domain on the PDC using the <indexterm id="ch06-idx-967706-0"><primary>Windows NT Server Manager for Domains tool</primary></indexterm>"Windows NT Server Manager for Domains" tool. When it asks for the computer type, choose "Windows NT Workstation or Server," and give it the NetBIOS name of the Samba server. This creates the machine account on the NT server.</para>
-
-
-<para>Next, generate a Microsoft-format machine password using the <filename>smbpasswd</filename>
-<indexterm id="ch06-idx-967707-0"><primary>smbpasswd program</primary></indexterm> tool, which is explained in further detail in the next section. For example, if our domain is SIMPLE and the Windows NT PDC is <literal>beowulf</literal>, we could use the following command on the Samba server to accomplish this:</para>
-
-
-<programlisting>smbpasswd -j SIMPLE -r beowulf</programlisting>
-
-
-<para>Finally, add the following options to the <literal>[global]</literal> section of your <filename>smb.conf</filename> and restart the Samba daemons.</para>
-
-
-<programlisting>[global]
- security = domain
- domain logins = yes
- workgroup = SIMPLE
- password server = beowulf</programlisting>
-
-
-<para>Samba should now be configured for domain-level security. The <literal>domain</literal> <literal>logins</literal> option is explained in more detail later in this<indexterm id="ch06-idx-967657-0" class="endofrange" startref="ch06-idx-967649-0"/>
-<indexterm id="ch06-idx-967657-1" class="endofrange" startref="ch06-idx-967649-1"/> chapter.<indexterm id="ch06-idx-967506-0" class="endofrange" startref="ch06-idx-967505-0"/>
-<indexterm id="ch06-idx-967506-1" class="endofrange" startref="ch06-idx-967505-1"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="6.4" id="ch06-61393">
-<title>Passwords</title>
-
-
-<para>
-<indexterm id="ch06-idx-967574-0" class="startofrange"><primary>passwords</primary></indexterm>Passwords are a thorny issue with Samba. So much so, in fact, that they are almost always the first major problem that users encounter when they install Samba, and generate by far the most questions sent to Samba support groups. In previous chapters, we've gotten around the need for passwords by placing the <literal>guest</literal> <literal>ok</literal> option in each of our configuration files, which allows connections without authenticating passwords. However, at this point, we need to delve deeper into Samba to discover what is happening on the network.</para>
-
-
-<para>
-<indexterm id="ch06-idx-967709-0"><primary>passwords</primary><secondary>encrypted</secondary><tertiary sortas="non-encrypted">vs. non-encrypted</tertiary></indexterm>
-<indexterm id="ch06-idx-967709-1"><primary>encrypted passwords</primary></indexterm>Passwords sent from individual clients can be either encrypted or non-encrypted. Encrypted passwords are, of course, more secure. A <indexterm id="ch06-idx-967710-0"><primary>non-encrypted passwords</primary></indexterm>non-encrypted password can be easily read with a packet sniffing program, such as the modified <emphasis>tcpdump</emphasis>
-<indexterm id="ch06-idx-967712-0"><primary>tcpdump utility</primary><secondary>passwords, reading</secondary></indexterm> program for Samba that we used in <link linkend="SAMBA-CH-3">Chapter 3</link>. Whether passwords are encrypted depends on the operating system that the client is using to connect to the Samba server. <link linkend="ch06-75183">Table 6.5</link> lists which Windows operating systems encrypt their passwords before sending them to the primary domain controller for authentication. If your client is not Windows, check the system documentation to see if SMB passwords are encrypted.</para>
-
-
-<table label="6.5" id="ch06-75183">
-<title>Windows Operating Systems with Encrypted Passwords </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Operating System</para></entry>
-
-<entry colname="col2"><para>Encrypted or Non-encrypted</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal></literal>
-<indexterm id="ch06-idx-967714-0"><primary>operating systems</primary><secondary>encrypted/non-encrypted passwords</secondary></indexterm>Windows 95</para></entry>
-
-<entry colname="col2"><para>Non-encrypted</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 95 with SMB Update</para></entry>
-
-<entry colname="col2"><para>Encrypted</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows 98</para></entry>
-
-<entry colname="col2"><para>Encrypted</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows NT 3.<emphasis>x</emphasis></para></entry>
-
-<entry colname="col2"><para>Non-encrypted</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows NT 4.0 before SP 3</para></entry>
-
-<entry colname="col2"><para>Non-encrypted</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Windows NT 4.0 after SP 3</para></entry>
-
-<entry colname="col2"><para>Encrypted</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>There are actually two different encryption methods used: one for <indexterm id="ch06-idx-967715-0"><primary>Windows 95/98</primary><secondary>passwords, encrypted</secondary></indexterm>Windows 95 and 98 clients that reuses Microsoft's LAN Manager encryption style, and a separate one for <indexterm id="ch06-idx-967716-0"><primary>Windows NT</primary><secondary>passwords</secondary><tertiary>encrypted</tertiary></indexterm>Windows NT clients and servers. Windows 95 and 98 use an older encryption system inherited from the LAN Manager network software, while Windows NT clients and servers use a newer encryption system.</para>
-
-
-<para>If encrypted passwords are supported, Samba stores the encrypted passwords in a file called <filename>smbpasswd</filename>
-<indexterm id="ch06-idx-967717-0"><primary>smbpasswd file</primary></indexterm>
-<indexterm id="ch06-idx-967717-1"><primary>passwords</primary><secondary>stored by Samba</secondary></indexterm>. By default, this file is located in the <filename>private</filename>
-<indexterm id="ch06-idx-967719-0"><primary>private directory (Samba distribution)</primary></indexterm> directory of the Samba distribution (<filename>/usr/local/samba/private</filename>). At the same time, the client stores an encrypted version of a user's password on its own system. The plaintext password is never stored on either system. Each system encrypts the password automatically using a known algorithm when the password is set or changed.</para>
-
-
-<para>When a client requests a connection to an SMB server that supports encrypted passwords (such as Samba or Windows NT), the two computers undergo the following negotiations:</para>
-
-
-<orderedlist>
-<listitem><para>The client attempts to negotiate a protocol with the server.</para></listitem>
-<listitem><para>The server responds with a protocol and indicates that it supports encrypted passwords. At this time, it sends back a randomly-generated 8-byte challenge string.</para></listitem>
-<listitem><para>The client uses the challenge string as a key to encrypt its already encrypted password using an algorithm predefined by the negotiated protocol. It then sends the result to the server.</para></listitem>
-<listitem><para>The server does the same thing with the encrypted password stored in its database. If the results match, the passwords are equivalent and the user is authenticated.</para></listitem>
-</orderedlist>
-
-<para>Note that even though the original passwords are not involved in the authentication process, you need to be very careful that the encrypted passwords located inside of the <filename>smbpasswd</filename>
-<indexterm id="ch06-idx-967721-0"><primary>smbpasswd file</primary><secondary>caution with</secondary></indexterm> file are guarded from unauthorized users. If they are compromised, an unauthorized user can break into the system by replaying the steps of the previous algorithm. The <indexterm id="ch06-idx-967722-0"><primary>passwords</primary><secondary>encrypted</secondary><tertiary sortas="plaintext">vs. plaintext</tertiary></indexterm>
-<indexterm id="ch06-idx-967722-1"><primary>plaintext passwords</primary></indexterm>
-<indexterm id="ch06-idx-967722-2"><primary sortas="encryptes passwords">encrypted passwords</primary><secondary sortas="plaintext passwords">vs. plaintext passwords</secondary></indexterm>encrypted passwords are just as sensitive as the plaintext passwords—this is known as <firstterm>plaintext-equivalent</firstterm> data in the cryptography world. Of course, you should also ensure that the clients safeguard their plaintext-equivalent passwords as well.</para>
-
-
-<para>You can configure Samba to accept encrypted passwords with the following global additions to <filename>smb.conf</filename>. Note that we explicitly name the location of the Samba password file:</para>
-
-
-<programlisting>[global]
- security = user
- encrypt passwords = yes
- smb passwd file = /usr/local/samba/private/smbpasswd</programlisting>
-
-
-<para>Samba, however, will not accept any users until the <filename>smbpasswd</filename> file has been initialized.</para>
-
-
-<sect2 role="" label="6.4.1" id="ch06-SECT-4.0.1">
-<title>Disabling encrypted passwords on the client</title>
-
-
-<para>
-<indexterm id="ch06-idx-967724-0"><primary>passwords</primary><secondary>encrypted</secondary><tertiary>disabling on Windows computers</tertiary></indexterm>While Unix authentication has been in use for decades, including the use of <emphasis>telnet</emphasis> and <emphasis>rlogin</emphasis> access across the Internet, it embodies well-known security risks. Plaintext passwords are sent over the Internet and can be retrieved from TCP packets by malicious snoopers. However, if you feel that your network is secure and you wish to use standard Unix <filename>/etc/passwd</filename> authentication for all clients, you can do so, but you must disable encrypted passwords on those Windows clients that default to using them.</para>
-
-
-<para>In order to do this, you must modify the Windows registry by installing two files on each system. Depending on the platform involved, the files are either <filename>NT4_PlainPassword.reg</filename> or <filename>Win95_PlainPassword.reg</filename>. You can perform this installation by copying the appropriate <filename>.reg</filename> files from the Samba distribution's <filename>/docs</filename> directory to a DOS floppy, and running it from the Run menu item on the client's Start Menu button. Incidentally, the Windows 95 <filename>.reg</filename> file works fine on Windows 98 as well.</para>
-
-
-<para>After you reboot the machine, the client will not encrypt its hashed passwords before sending them to the server. This means that the plaintext-equivalent passwords can been seen in the TCP packets that are broadcast across the network. Again, we encourage you not to do this unless you are absolutely sure that your network is secure.</para>
-
-
-<para>If passwords are not encrypted, you can indicate as much in your Samba configuration file:</para>
-
-
-<programlisting>[global]
- security = user
- encrypt passwords = no</programlisting>
-</sect2>
-
-
-
-
-<sect2 role="" label="6.4.2" id="ch06-17782">
-<title>The smbpasswd File</title>
-
-
-<para><filename></filename>
-<indexterm id="ch06-idx-967731-0" class="startofrange"><primary>smbpasswd file</primary></indexterm>Samba stores its encrypted passwords in a file called <filename>smbpasswd</filename>, which by default resides in the <filename>/usr/local/samba/private</filename> directory. The <filename>smbpasswd</filename>
-<indexterm id="ch06-idx-967742-0"><primary>smbpasswd file</primary><secondary>caution with</secondary></indexterm> file should be guarded as closely as the <filename>passwd</filename> file; it should be placed in a directory to which only the root user has read/write access. All other users should not be able to read from the directory at all. In addition, the file should have all access closed off to all users except for root.</para>
-
-
-<para>Before you can use encrypted passwords, you will need to create an entry for each Unix user in the <filename>smbpasswd</filename> file. The structure of the file is somewhat similar to a Unix <filename>passwd</filename> file, but has different fields. <link linkend="ch06-54128">Figure 6.3</link> illustrates the layout of the <filename>smbpasswd</filename> file; the entry shown is actually one line in the file.</para>
-
-
-<figure label="6.3" id="ch06-54128">
-<title>Structure of the smbpasswd file entry (actually one line)</title>
-
-<graphic width="502" depth="177" fileref="figs/sam.0603.gif"></graphic>
-</figure>
-
-<para>Here is a breakdown of the individual fields:</para>
-
-
-<variablelist>
-<varlistentry><term>Username</term>
-<listitem><para>This is the username of the account. It is taken directly from the system password file.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>UID</term>
-<listitem><para>This is the user ID of the account. Like the username, it is taken directly from the system password file and must match the user it represents there.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>LAN Manager Password Hash</term>
-<listitem><para>This is a 32-bit hexadecimal sequence that represents the password Windows 95 and 98 clients will use. It is derived by encrypting the string <literal>KGS!@#$%</literal> with a 56-bit DES algorithm using the user's password (forced to 14 bytes and converted to capital letters) twice repeated as the key. If there is currently no password for this user, the first 11 characters of the hash will consist of the sequence <literal>NO</literal> <literal>PASSWORD</literal> followed by <literal>X</literal> characters for the remainder. Anyone can access the share with no password. On the other hand, if the password has been disabled, it will consist of 32 <literal>X</literal> characters. Samba will not grant access to a user without a password unless the <literal>null</literal> <literal>passwords</literal> option has been set.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>NT Password Hash</term>
-<listitem><para>This is a 32-bit hexadecimal sequence that represents the password Windows NT clients will use. It is derived by hashing the user's password (represented as a 16-bit little-endian Unicode sequence) with an MD4 hash. The password is not converted to uppercase letters first.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Account Flags</term>
-<listitem><para>This field consists of 11 characters between two braces ( [ ] ). Any of the following characters can appear in any order; the remaining characters should be spaces:</para>
-
-
-<variablelist>
-<varlistentry><term>U</term>
-<listitem><para>This account is a standard user account.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>D</term>
-<listitem><para>This account is currently disabled and Samba should not allow any logins.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>N</term>
-<listitem><para>This account has no password associated with it.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>W</term>
-<listitem><para>This is a workstation trust account that can be used to configure Samba as a primary domain controller (PDC) when allowing Windows NT machines to join its domain.</para></listitem>
-</varlistentry>
-</variablelist></listitem>
-</varlistentry>
-
-
-<varlistentry><term>Last Change Time</term>
-<listitem><para>This code consists of the characters <literal>LCT-</literal> followed by a hexadecimal representation of the amount of seconds since the epoch (midnight on January 1, 1970) that the entry was last changed.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<sect3 role="" label="6.4.2.1" id="ch06-SECT-4.1.1">
-<title>Adding entries to smbpasswd</title>
-
-
-<para><filename></filename>
-<indexterm id="ch06-idx-967757-0"><primary>smbpasswd file</primary><secondary>adding entries to</secondary></indexterm>There are a few ways you can add a new entry to the <filename>smbpasswd</filename> file:</para>
-
-
-<itemizedlist>
-<listitem><para>You can use the <firstterm>smbpasswd</firstterm> program with the <literal>-a</literal> option to automatically add any user that currently has a standard Unix system account on the server. This program resides in the <filename>/usr/local/samba/bin</filename> directory.</para></listitem>
-<listitem><para>You can use the <firstterm>addtosmbpass</firstterm>
-<indexterm id="ch06-idx-967763-0"><primary>addtosmbpass executable</primary></indexterm> executable inside the <firstterm>/usr/local/samba/bin</firstterm> directory. This is actually a simple <emphasis>awk</emphasis>
-<indexterm id="ch06-idx-967764-0"><primary>awk script</primary></indexterm> script that parses a system password file and extracts the username and UID of each entry you wish to add to the SMB password file. It then adds default fields for the remainder of the user's entry, which can be updated using the <filename>smbpasswd</filename> program later. In order to use this program, you will probably need to edit the first line of the file to correctly point to <emphasis>awk</emphasis> on your system.</para></listitem>
-<listitem><para>In the event that the neither of those options work for you, you can create a default entry by hand in the <filename>smbpasswd</filename> file. The entry should be entirely on one line. Each field should be colon-separated and should look similar to the following:</para>
-
-
-<programlisting>dave:500:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-00000000:</programlisting>
-
-
-<para>This consists of the username and the UID as specified in the system password file, followed by two sets of exactly 32 <literal>X</literal> characters, followed by the account flags and last change time as it appears above. After you've added this entry, you must use the <firstterm>smbpasswd</firstterm> program to change the password for the user.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.2.2" id="ch06-SECT-4.1.2">
-<title>Changing the encrypted password</title>
-
-
-<para>
-<indexterm id="ch06-idx-967765-0"><primary>passwords</primary><secondary>encrypted</secondary><tertiary>changing</tertiary></indexterm>If you need to change the encrypted password in the <filename>smbpasswd</filename> file, you can also use the <filename>smbpasswd</filename>
-<indexterm id="ch06-idx-967766-0"><primary>smbpasswd program</primary><secondary>changing encrypted passwords with</secondary></indexterm> program. Note that this program shares the same name as the encrypted password file itself, so be sure not to accidentally confuse the password file with the password-changing program.</para>
-
-
-<para>The <filename>smbpasswd</filename> program is almost identical to the <filename>passwd</filename> program that is used to change Unix account passwords. The program simply asks you to enter your old password (unless you're the root user), and duplicate entries of your new password. No password characters are shown on the screen.</para>
-
-
-<programlisting># <emphasis role="bold">smbpasswd dave</emphasis>
-Old SMB password:
-New SMB password:
-Retype new SMB password:
-Password changed for user dave</programlisting>
-
-
-<para>You can look at the <filename>smbpasswd</filename> file after this command completes to verify that both the LAN Manager and the NT hashes of the passwords have been stored in their respective positions. Once users have encrypted password entries in the database, they should be able to connect to shares using encrypted passwords!<filename></filename>
-<indexterm id="ch06-idx-967737-0" class="endofrange" startref="ch06-idx-967731-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.4.3" id="ch06-97004">
-<title>Password Synchronization</title>
-
-
-<para>
-<indexterm id="ch06-idx-967768-0" class="startofrange"><primary>passwords</primary><secondary>synchronizing</secondary></indexterm>
-<indexterm id="ch06-idx-967768-1" class="startofrange"><primary>synchronizing</primary><secondary>passwords</secondary></indexterm>Having a regular password and an encrypted version of the same password can be troublesome when you need to change both of them. Luckily, Samba affords you a limited ability to keep your passwords synchronized. Samba has a pair of configuration options that can be used to automatically update a user's regular Unix password when the encrypted password is changed on the system. The feature can be activated by specifying the <literal>unix</literal> <literal>password</literal> <literal>sync</literal> global configuration option:</para>
-
-
-<programlisting>[global]
- encrypt passwords = yes
- smb passwd file = /usr/local/samba/private/smbpasswd
-
- unix password sync = yes</programlisting>
-
-
-<para>With this option enabled, Samba will attempt to change the user's regular password (as <literal>root</literal>) when the encrypted version is changed with <filename>smbpasswd</filename>. However, there are two other options that have to be set correctly in order for this to work.</para>
-
-
-<para>The easier of the two is <literal>passwd</literal> <literal>program</literal>. This option simply specifies the Unix command used to change a user's standard system password. It is set to <literal>/bin/passw</literal>d <literal>%u</literal> by default. With some Unix systems, this is sufficient and you do not need to change anything. Others, such as Red Hat Linux, use <filename>/usr/bin/passwd</filename> instead. In addition, you may want to change this to another program or script at some point in the future. For example, let's assume that you want to use a script called <literal>changepass</literal> to change a user's password. Recall that you can use the variable <literal>%u</literal> to represent the current Unix username. So the example becomes:</para>
-
-
-<programlisting>[global]
- encrypt passwords = yes
- smb passwd file = /usr/local/samba/private/smbpasswd
-
- unix password sync = yes
- passwd program = changepass %u</programlisting>
-
-
-<para>Note that this program will be called as the <literal>root</literal> user when the <literal>unix</literal> <literal>password</literal> <literal>sync</literal> option is set to <literal>yes</literal>. This is because Samba does not necessarily have the plaintext old password of the user.</para>
-
-
-<para>The harder option to configure is <literal>passwd</literal> <literal>chat</literal>. The <literal>passwd</literal> <literal>chat</literal> option works like a Unix chat script. It specifies a series of strings to send as well as responses to expect from the program specified by the <literal>passwd</literal> <literal>program</literal> option. For example, this is what the default <literal>passwd</literal> <literal>chat</literal> looks like. The delimiters are the spaces between each groupings of characters:</para>
-
-
-<programlisting>passwd chat = *old*password* %o\n *new*password* %n\n *new*password* %n\n *changed*</programlisting>
-
-
-<para>The first grouping represents a response expected from the password-changing program. Note that it can contain <indexterm id="ch06-idx-967780-0"><primary>wildcards (*) in password changing program</primary></indexterm>
-<indexterm id="ch06-idx-967780-1"><primary>* wildcards</primary></indexterm>wildcards (*), which help to generalize the chat programs to be able to handle a variety of similar outputs. Here, <literal>*old*password*</literal> indicates that Samba is expecting any line from the password program containing the letters <literal>old</literal> followed by the letters <literal>password</literal>, without regard for what comes on either side or between them. Once instructed to, Samba will wait indefinitely for such a match. Is Samba does not receive the expected response, the password will fail.</para>
-
-
-<para>The second grouping indicates what Samba should send back once the data in the first grouping has been matched. In this case, you see <literal>%o\n</literal>. This response is actually two items: the variable <literal>%o</literal> represents the old password, while the <literal>\n</literal> is a newline character. So, in effect, this will "type" the old password into the standard input of the password changing program, and then "press" Enter.</para>
-
-
-<para>Following that is another response grouping, followed by data that will be sent back to the password changing program. (In fact, this response/send pattern continues indefinitely in any standard Unix <emphasis>chat</emphasis> script.) The script continues until the final pattern is matched.<footnote label="2" id="ch06-pgfId-969009">
-
-
-<para>This may not work under Red Hat Linux, as the password program typically responds "All authentication tokens updated successfully," instead of "Password changed." We provide a fix for this later in this section.</para>
-
-
-</footnote></para>
-
-
-<para>You can help match the response strings sent from the password program with the characters listed in <link linkend="ch06-77246">Table 6.6</link>. In addition, you can use the characters listed in <link linkend="ch06-38512">Table 6.7</link> to help formulate your response.</para>
-
-
-<table label="6.6" id="ch06-77246">
-<title>Password Chat Response Characters </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Character</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>*</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch06-idx-967781-0"><primary>passwords</primary><secondary>chat characters for</secondary></indexterm>
-<indexterm id="ch06-idx-967781-1"><primary>chat characters for passwords</primary></indexterm>Zero or more occurrences of any character.</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>" "</literal></para></entry>
-
-<entry colname="col2"><para>Allows you to include matching strings that contain spaces. Asterisks are still considered wildcards even inside of quotes, and you can represent a null response with empty quotes.</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<table label="6.7" id="ch06-38512">
-<title>Password Chat Send Characters </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Character</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>%o</literal></para></entry>
-
-<entry colname="col2"><para>The user's old password</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%n</literal></para></entry>
-
-<entry colname="col2"><para>The user's new password</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>\n</literal></para></entry>
-
-<entry colname="col2"><para>The linefeed character</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>\r</literal></para></entry>
-
-<entry colname="col2"><para>The carriage-return character</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>\t</literal></para></entry>
-
-<entry colname="col2"><para>The tab character</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>\s</literal></para></entry>
-
-<entry colname="col2"><para>A space</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>For example, you may want to change your password chat to the following entry. This will handle scenarios in which you do not have to enter the old password. In addition, this will also handle the new <literal>all</literal> <literal>tokens</literal> <literal>updated</literal> <literal>successfully</literal> string that Red Hat Linux sends:</para>
-
-
-<programlisting>passwd chat = *new password* %n\n *new password* %n\n *success*</programlisting>
-
-
-<para>Again, the default chat should be sufficient for many Unix systems. If it isn't, you can use the <literal>passwd</literal> <literal>chat</literal> <literal>debug</literal> global option to set up a new chat script for the password change program. The <literal>passwd</literal> <literal>chat</literal> <literal>debug</literal> option logs everything during a password chat. This option is a simple boolean, as shown below:</para>
-
-
-<programlisting>[global]
- encrypted passwords = yes
- smb passwd file = /usr/local/samba/private/smbpasswd
-
- unix password sync = yes
- passwd chat debug = yes
- log level = 100</programlisting>
-
-
-<para>After you activate the password chat debug feature, all I/O received by Samba through the password chat will be sent to the Samba logs with a debug level of 100, which is why we entered a new log level option as well. As this can often generate multitudes of error logs, it may be more efficient to use your own script, by setting the <literal>passwd</literal> <literal>program</literal> option, in place of <filename>/bin/passwd</filename> to record what happens during the exchange. Also, make sure to protect your log files with strict file permissions and to delete them as soon as you've grabbed the information you need, because they contain the passwords in plaintext.</para>
-
-
-<para>The operating system on which Samba is running may have strict requirements for valid passwords in order to make them more impervious to dictionary attacks and the like. Users should be made aware of these restrictions when changing their passwords.</para>
-
-
-<para>Earlier we said that password synchronization is limited. This is because there is no reverse synchronization of the encrypted <filename>smbpasswd</filename> file when a standard Unix password is updated by a user. There are various strategies to get around this, including NIS and freely available implementations of the <indexterm id="ch06-idx-967787-0"><primary>PAM (pluggable authentication modules)</primary></indexterm>
-<indexterm id="ch06-idx-967787-1"><primary>pluggable authentication modules (PAM)</primary></indexterm>pluggable authentication modules (PAM) standard, but none of them really solve all the problems yet. In the future, when Windows 2000 emerges, we will see more compliance with the <indexterm id="ch06-idx-967788-0"><primary>LDAP (Lightweight Directory Access Protocol)</primary><secondary>replacement for password snychronization</secondary></indexterm>Lightweight Directory Access Protocol (LDAP), which promises to make password synchronization a thing of the past.<indexterm id="ch06-idx-967772-0" class="endofrange" startref="ch06-idx-967768-0"/>
-<indexterm id="ch06-idx-967772-1" class="endofrange" startref="ch06-idx-967768-1"/></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.4.4" id="ch06-SECT-4.3">
-<title>Password Configuration Options</title>
-
-
-<para>The options in <link linkend="ch06-68460">Table 6.8</link> will help you work with passwords in Samba.</para>
-
-
-<table label="6.8" id="ch06-68460">
-<title>Password Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>encrypt passwords</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>
-<indexterm id="ch06-idx-969358-0" class="startofrange"><primary>passwords</primary><secondary>options for</secondary></indexterm>Turns on encrypted passwords.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>unix password sync </literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba updates the standard Unix password database when a user changes his or her encrypted password.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>passwd chat</literal></para></entry>
-
-<entry colname="col2"><para>string (chat commands)</para></entry>
-
-<entry colname="col3"><para>Sets a sequence of commands that will be sent to the password program.</para></entry>
-
-<entry colname="col4"><para>See earlier section on this option</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>passwd chat debug</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Sends debug logs of the password-change process to the log files with a level of 100.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>passwd program</literal></para></entry>
-
-<entry colname="col2"><para>string (Unix command)</para></entry>
-
-<entry colname="col3"><para>Sets the program to be used to change passwords.</para></entry>
-
-<entry colname="col4"><para><literal>/bin/passwd %u</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>null passwords</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba allows access for users with null passwords.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>smb passwd file</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the name of the encrypted password file.</para></entry>
-
-<entry colname="col4"><para><literal>/usr/local/samba/private/smbpasswd</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>hosts equiv</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the name of a file that contains hosts and users that can connect without using a password.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>use rhosts</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>.<emphasis>rhosts</emphasis> file that allows users to connect without using a password.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="6.4.4.1" id="ch06-SECT-4.3.1">
-<indexterm id="ch06-idx-969469-0"><primary>unix password sync option</primary></indexterm>
-<title>
-unix password sync</title>
-
-
-<para>The <literal>unix</literal> <literal>password</literal> <literal>sync</literal> global option allows Samba to update the standard Unix password file when a user changes his or her encrypted password. The encrypted password is stored on a Samba server in the <filename>smbpasswd</filename> file, which is located in <filename>/usr/local/samba/private</filename> by default. You can activate this feature as follows:</para>
-
-
-<programlisting>[global]
- unix password sync = yes</programlisting>
-
-
-<para>If this option is enabled, Samba changes the encrypted password and, in addition, attempts to change the standard Unix password by passing the username and new password to the program specified by the <literal>passwd</literal> <literal>program</literal> option (described earlier). Note that Samba does not necessarily have access to the plaintext password for this user, so the password changing program must be invoked as <literal>root</literal>.<footnote label="3" id="ch06-pgfId-959675">
-
-
-<para>This is because the Unix <emphasis>passwd</emphasis> program, which is the usual target for this operation, allows <literal>root</literal> to change a user's password without the security restriction that requests the old password of that user.</para>
-
-
-</footnote> If the Unix password change does not succeed, for whatever reason, the SMB password will not be changed either.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.2" id="ch06-SECT-4.3.2">
-<indexterm id="ch06-idx-969472-0"><primary>encrypt passwords option</primary></indexterm>
-<title>
-encrypt passwords</title>
-
-
-<para>
-<indexterm id="ch06-idx-967797-0"><primary>encrypted passwords</primary><secondary>option for</secondary></indexterm>The <literal>encrypt</literal> <literal>passwords</literal> global option switches Samba from using plaintext passwords to encrypted passwords for authentication. Encrypted passwords will be expected from clients if the option is set to <literal>yes</literal>:</para>
-
-
-<programlisting>encrypt passwords = yes</programlisting>
-
-
-<para>By default, Windows NT 4.0 with Service Pack 3 or above and Windows 98 transmit encrypted passwords over the network. If you are enabling encrypted passwords, you must have a valid <filename>smbpasswd</filename> file in place and populated with usernames that will authenticate with encrypted passwords. (See <link linkend="ch06-17782">Section 6.4.2</link> earlier in this chapter.) In addition, Samba must know the location of the <filename>smbpasswd</filename> file; if it is not in the default location (typically <filename>/usr/local/samba/private/smbpasswd</filename>), you can explicitly name it using the <literal>smb</literal> <literal>passwd</literal> <literal>file</literal> option.</para>
-
-
-<para>If you wish, you can use the <literal>update</literal> <literal>encrypted</literal> to force Samba to update the <filename>smbpasswd</filename> file with encrypted passwords each time a client connects to a non-encrypted password.</para>
-
-
-<para>A common strategy to ensure that hosts who need encrypted password authentication indeed receive it is with the <literal>include</literal> option. With this, you can create individual configuration files that will be read in based on OS-type (<literal>%a</literal>) or client name (<literal>%m</literal>). These host-specific or OS-specific configuration files can contain an <literal>encrypted</literal> <literal>passwords</literal> <literal>=</literal> <literal>yes</literal> option that will activate only when those clients are connecting to the server.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.3" id="ch06-SECT-4.3.3">
-<indexterm id="ch06-idx-969475-0"><primary>passwd program option</primary></indexterm>
-<title>
-passwd program</title>
-
-
-<para>The <literal>passwd</literal>
-<indexterm id="ch06-idx-967798-0"><primary>passwords</primary><secondary>passwd program</secondary></indexterm> <literal>program</literal> is used to specify a program on the Unix Samba server that Samba can use to update the standard system password file when the encrypted password file is updated. This option defaults to the standard <emphasis>passwd</emphasis> program, usually located in the <filename>/bin</filename> directory. The <literal>%u</literal> variable is typically used here as the requesting user when the command is executed. The actual handling of input and output to this program during execution is handled through the <literal>passwd</literal> <literal>chat</literal> option. <link linkend="ch06-97004">Section 6.4.3</link>, earlier in this chapter, covers this option in detail.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.4" id="ch06-SECT-4.3.4">
-<indexterm id="ch06-idx-969476-0"><primary>passwd chat option</primary></indexterm>
-<title>
-passwd chat</title>
-
-
-<para>This option specifies a series of send/response strings similar to a Unix chat script, which are used to interface with the password-changing program on the Samba server. <link linkend="ch06-97004">Section 6.4.3</link>, earlier in this chapter, covers this option in detail.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.5" id="ch06-SECT-4.3.5">
-<indexterm id="ch06-idx-969477-0"><primary>passwd chat debug option</primary></indexterm>
-<title>
-passwd chat debug</title>
-
-
-<para>If set to <literal>yes</literal>, the <literal>passwd</literal> <literal>chat</literal> <literal>debug</literal> global option logs everything sent or received by Samba during a password chat. All the I/O received by Samba through the password chat is sent to the Samba logs with a debug level of 100; you will need to specify <literal>log</literal> <literal>level</literal> <literal>=</literal> <literal>100</literal> in order for the information to be recorded. <link linkend="ch06-97004">Section 6.4.3</link> earlier in this chapter, describes this option in more detail. Be aware that if you do set this option, the plaintext passwords will be visible in the debugging logs, which could be a security hazard if they are not properly secured.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.6" id="ch06-SECT-4.3.6">
-<indexterm id="ch06-idx-969478-0"><primary>password level option</primary></indexterm>
-<title>
-password level</title>
-
-
-<para>With SMB, non-encrypted (or plaintext) passwords are sent with capital letters, just like the usernames mentioned previously. Many Unix users, however, choose passwords with both uppercase and lowercase letters. Samba, by default, only attempts to match the password entirely in lowercase letters, and not capitalizing the first letter.</para>
-
-
-<para>Like <literal>username</literal> <literal>level</literal>, there is a <literal>password</literal> <literal>level</literal> option that can be used to attempt various permutations of the password with capital letters. This option takes an integer value that specifies how many letters in the password should be capitalized when attempting to connect to a share. You can specify this options as follows:</para>
-
-
-<programlisting>[global]
- password level = 3</programlisting>
-
-
-<para>In this case, Samba will then attempt all permutations of the password it can compute having three capital letters. The larger the number, the more computations Samba will have to perform to match the password, and the longer a connection to a specific share may take.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.7" id="ch06-SECT-4.3.7">
-<title>null passwords</title>
-
-
-<para>This global option tells Samba whether or not to allow access from users that have <indexterm id="ch06-idx-967801-0"><primary>null passwords</primary></indexterm>
-<indexterm id="ch06-idx-967801-1"><primary>passwords</primary><secondary>null</secondary></indexterm>null passwords (encrypted or non-encrypted) set in their accounts. The default value is <literal>no</literal>. You can override it as follows:</para>
-
-
-<programlisting>null passwords = yes</programlisting>
-
-
-<para>We highly recommend against doing so unless you are familiar with the security risks this option can present to your system, including inadvertent access to system users (such as <filename>bin</filename>) in the system password file who have null passwords set.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.8" id="ch06-SECT-4.3.8">
-<indexterm id="ch06-idx-969483-0"><primary>smb passwd file option</primary></indexterm>
-<title>
-smb passwd file</title>
-
-
-<para>
-<indexterm id="ch06-idx-968245-0"><primary>smbpasswd file</primary><secondary>option for location of</secondary></indexterm>This global option identifies the location of the encrypted password database. By default, it is set to <filename>/usr/local/samba/private/smbpasswd</filename>. You can override it as follows:</para>
-
-
-<programlisting>[global]
- smb passwd file = /etc/smbpasswd</programlisting>
-
-
-<para>This location, for example, is common on many Red Hat distributions.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.9" id="ch06-SECT-4.3.9">
-<indexterm id="ch06-idx-969486-0"><primary>hosts equiv option</primary></indexterm>
-<title>
-hosts equiv</title>
-
-
-<para>This global option specifies the name of a standard Unix <filename>hosts.equiv</filename> file that will allow hosts or users to access shares without specifying a password. You can specify the location of such a file as follows:</para>
-
-
-<programlisting>[global]
- hosts equiv = /etc/hosts.equiv</programlisting>
-
-
-<para>The default value for this option does not specify any <filename>hosts.equiv</filename> file. Because using such a file is essentially a huge security risk, we highly recommend that you do not use this option unless you are confident in the security of your network.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.4.4.10" id="ch06-SECT-4.3.10">
-<indexterm id="ch06-idx-969487-0"><primary>use rhosts option</primary></indexterm>
-<title>
-use rhosts</title>
-
-
-<para>This global option specifies the name of a standard Unix user's <filename>.rhosts</filename> file that will allow foreign hosts to access <indexterm id="ch06-idx-967803-0"><primary>shares</primary><secondary>access to</secondary><tertiary sortas="foreign hosts, option for">by foreign hosts, option for</tertiary></indexterm>shares without specifying a password. You can specify the location of such a file as follows:</para>
-
-
-<programlisting>[global]
- use rhosts = /home/dave/.rhosts</programlisting>
-
-
-<para>The default value for this option does not specify any <filename>.rhosts</filename> file. Like the <literal>hosts</literal> <literal>equiv</literal> option above, using such a file is a security risk. We highly recommend that you do use this option unless you are confident in the security of<indexterm id="ch06-idx-968233-0" class="endofrange" startref="ch06-idx-969358-0"/> your network.<indexterm id="ch06-idx-968235-0" class="endofrange" startref="ch06-idx-967574-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="6.5" id="ch06-23084">
-<title>Windows Domains</title>
-
-
-<para>
-<indexterm id="ch06-idx-967533-0" class="startofrange"><primary>domains</primary><secondary>Windows</secondary></indexterm>
-<indexterm id="ch06-idx-967533-1" class="startofrange"><primary>Windows 95/98</primary><secondary>domains</secondary></indexterm>
-<indexterm id="ch06-idx-967533-2" class="startofrange"><primary>Windows NT</primary><secondary>domains</secondary></indexterm>Now that you are comfortable with users and passwords on a Samba server, we can show you how to set up Samba to become a <indexterm id="ch06-idx-967819-0"><primary>PDC (primary domain controller)</primary><secondary>Samba, setting up as</secondary></indexterm>primary domain controller for Windows 95/98 and NT machines. Why use domains? The answer probably isn't obvious until you look behind the scenes, especially with Windows 95/98.</para>
-
-
-<para>Recall that with traditional workgroups, Windows 95/98 simply accepts each username and password that you enter when logging on to the system. There are no unauthorized users with Windows 95/98; if a new user logs on, the operating system simply asks for a new password and authenticates the user against that password from then on. The only time that Windows 95/98 attempts to use the password you entered is when connecting to another share.</para>
-
-
-<para>
-<indexterm id="ch06-idx-967805-0"><primary>domain logons</primary></indexterm>Domain logons, on the other hand, are similar to Unix systems. In order to log on to the domain, a valid username and password must be presented at startup, which is then authenticated against the primary domain controller's password database. If the password is invalid, the user is immediately notified and they cannot log on to the domain.</para>
-
-
-<para>There's more good news: once you have successfully logged on to the domain, you can access any of the shares in the domain to which you have rights without having to reauthenticate yourself. More precisely, the primary domain controller returns a token to the client machine that allows it to access any share without consulting the PDC again. Although you probably won't notice the shift, this can be beneficial in cutting down network traffic. (You can disable this behavior if you wish by using the <literal>revalidate</literal> option.)</para>
-
-
-<sect2 role="" label="6.5.1" id="ch06-36822">
-<title>Configuring Samba for Windows Domain Logons</title>
-
-
-<para>If you wish to allow Samba to act as a domain controller, use the following sections to configure Samba and your clients to allow domain access.</para>
-
-
-<tip role="ora">
-<para>If you would like more information on how to set up domains, see the <filename>DOMAINS.TXT</filename> file that comes with the Samba distribution.</para>
-
-</tip>
-
-<sect3 role="" label="6.5.1.1" id="ch06-SECT-5.1.1">
-<title>Windows 95/98 clients</title>
-
-
-<para>
-<indexterm id="ch06-idx-967815-0"><primary>Windows 95/98</primary><secondary>domain logons, configuring</secondary></indexterm>Setting up Samba as a PDC for Windows 95/98 clients is somewhat anticlimactic. All you really need to do on the server side is ensure that:</para>
-
-
-<itemizedlist>
-<listitem><para>Samba is the only primary domain controller for the current workgroup.</para></listitem>
-<listitem><para>There is a <indexterm id="ch06-idx-967817-0"><primary>WINS (Windows Internet Name Service)</primary><secondary>server</secondary><tertiary>configuring Windows domain logons and</tertiary></indexterm>WINS server available on the network, either a Samba machine or a Windows NT server. (See <link linkend="SAMBA-CH-7">Chapter 7</link>, for more information on WINS.)</para></listitem>
-<listitem><para>Samba is using user-level security (i.e., it doesn't hand off password authentication to anyone else). You do not want to use domain-level security if Samba itself is acting as the PDC.</para></listitem>
-</itemizedlist>
-
-<para>At that point, you can insert the following options into your Samba configuration file:</para>
-
-
-<programlisting>[global]
- workgroup = SIMPLE
- domain logons = yes
-
-# Be sure to set user-level security!
-
- security = user
-
-# Be sure to become the primary domain controller!
-
- os level = 34
- local master = yes
- preferred master = yes
- domain master = yes</programlisting>
-
-
-<para>The <literal>domain</literal> <literal>logons</literal> option enables Samba to perform domain authentication on behalf of other clients that request it. The name of the domain will be the same as the workgroup listed in the Samba configuration file, in this case: SIMPLE.</para>
-
-
-<para>After that, you need to create a non-writable, non-public, non-browesable disk share called <literal>[netlogon]</literal> (it does not matter where this share points to as long as each Windows client can connect to it):</para>
-
-
-<programlisting>[netlogon]
- comment = The domain logon service
- path = /export/samba/logon
- public = no
- writeable = no
- browsable = no</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="6.5.1.2" id="ch06-SECT-5.1.2">
-<title>Windows NT clients</title>
-
-
-<para>
-<indexterm id="ch06-idx-967816-0"><primary>Windows NT</primary><secondary>configuring domain logons</secondary></indexterm>If you have Window NT clients on your system, there are a few more steps that need to be taken in order for Samba to act as their primary domain controller.</para>
-
-
-<warning role="ora">
-<para>You will need to use at least <indexterm id="ch06-idx-967821-0"><primary>Samba</primary><secondary>version 2.1</secondary><tertiary>PDC functionality and</tertiary></indexterm>
-<indexterm id="ch06-idx-967821-1"><primary>PDC (primary domain controller)</primary><secondary>Samba 2.1 and</secondary></indexterm>
-<indexterm id="ch06-idx-967821-2"><primary>Windows NT</primary><secondary>user authentication and</secondary></indexterm>Samba 2.1 to ensure that PDC functionality for Windows NT clients is present. Prior to Samba 2.1, only limited user authentication for NT clients was present. At the time this book went to press, Samba 2.0.5 was the latest version, but Samba 2.1 was available through CVS download. Instructions on downloading alpha versions of Samba are given in <link linkend="SAMBA-AP-E">Appendix E</link>.</para>
-
-</warning>
-
-<para>As before, you need to ensure that Samba is a primary domain controller for the current workgroup and is using user-level security. However, you must also ensure that Samba is using encrypted passwords. In other words, alter the <literal>[global]</literal> options the previous example to include the <literal>encrypted</literal> <literal>passwords</literal> <literal>=</literal> <literal>yes</literal> option, as shown here:</para>
-
-
-<programlisting>[global]
- workgroup = SIMPLE
- encrypted passwords = yes
- domain logons = yes
-
- security = user</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="6.5.1.3" id="ch06-SECT-5.1.3">
-<title>Creating trust accounts for NT clients</title>
-
-
-<para>This step is exclusively for Windows NT clients. All NT clients that connect to a primary domain controller make use of <firstterm>trust accounts</firstterm>
-<indexterm id="ch06-idx-967823-0"><primary>trust accounts, creating</primary></indexterm>. These accounts allow a machine to log in to the <indexterm id="ch06-idx-967824-0"><primary>PDC (primary domain controller)</primary><secondary>trust accounts and</secondary></indexterm>PDC itself (not one of its shares), which means that the PDC can trust any further connections from users on that client. For all intents and purposes, a trust account is identical to a user account. In fact, we will be using standard Unix user accounts to emulate trust accounts for the Samba server.</para>
-
-
-<para>The login name of a machine's trust account is the name of the machine with a dollar sign appended to it. For example, if our Windows NT machine is named <literal>chimaera</literal>, the login account would be <literal>chimaera$</literal>. The initial password of the account is simply the name of the machine in lowercase letters. In order to forge the trust account on the Samba server, you need to create a Unix account with the appropriate machine name, as well as an encrypted password entry in the <filename>smbpasswd</filename> database.</para>
-
-
-<para>Let's tackle the first part. Here, we only need to modify the <filename>/etc/passwd</filename> file to support the trust account; there is no need to create a home directory or assign a shell to the "user" because the only part we are interested in is whether a login is permitted. Therefore, we can create a "dummy" account with the following entry:</para>
-
-
-<programlisting>chimaera$:*:1000:900:Trust Account:/dev/null:/dev/null</programlisting>
-
-
-<para>Note that we have also disabled the password field by placing a <literal>*</literal> in it. This is because Samba will use the <filename>smbpasswd</filename> file to contain the password instead, and we don't want anyone to telnet into the machine using that account. In fact, the only value other than the account name that is used here is the UID of the account for the encrypted password database (1000). This number must map to a unique resource ID on the NT server and cannot conflict with any other resource IDs. Hence, no NT user or group should map to this number or a networking error will occur.</para>
-
-
-<para>Next, add the encrypted password using the <filename>smbpasswd</filename> command, as follows:</para>
-
-
-<programlisting># <userinput>smbpasswd -a -m chimaera</userinput>
-Added user chimaera$
-Password changed for user chimaera$</programlisting>
-
-
-<para>The <literal>-m</literal> option specifies that a machine trust account is being generated. The <filename>smbpasswd</filename> program will automatically set the initial encrypted password as the NetBIOS name of the machine in lowercase letters; you don't need to enter it. When specifying this option on the command line, do not put a dollar sign after the machine name—it will be appended automatically. Once the encrypted password has been added, Samba is ready to handle domain logins from a NT client.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.5.2" id="ch06-SECT-5.2">
-<title>Configuring Windows Clients for Domain Logons</title>
-
-
-<para>Once you have Samba configured for domain logons, you need to set up your Windows clients to log on to the domain at startup.</para>
-
-
-<sect3 role="" label="6.5.2.1" id="ch06-SECT-5.2.1">
-<title>Windows 95/98</title>
-
-
-<para>
-<indexterm id="ch06-idx-969407-0"><primary>domain logons</primary><secondary>configuring Windows 95/98 for</secondary></indexterm>
-<indexterm id="ch06-idx-969407-1"><primary>domains</primary><secondary>logons</secondary><see>domain logons</see></indexterm>With Windows 95/98, this can be done by raising the Network configuration dialog in the Windows Control Panel and selecting the Properties for "Client for Microsoft Networks." At this point, you should see a dialog box similar to <link linkend="ch06-48609">Figure 6.4</link>. Select the "Logon to Windows Domain" checkbox at the top of the dialog box, and enter the workgroup that is listed in the Samba configuration file as the Windows NT domain. Then click on OK and reboot the machine when asked.</para>
-
-
-<figure label="6.4" id="ch06-48609">
-<title>Configuring a Windows 95/98 client for domain logons</title>
-
-<graphic width="502" depth="359" fileref="figs/sam.0604.gif"></graphic>
-</figure>
-
-<warning role="ora">
-<para>If Windows complains that you are already logged into the domain, you probably have an active connection to a share in the workgroup (such as a mapped network drive). Simply disconnect the resource temporarily by right-clicking on its icon and choosing the Disconnect pop-up menu item.</para>
-
-</warning>
-
-<para>When Windows reboots, you should see the standard <indexterm id="ch06-idx-967825-0"><primary>login dialog box, domain logons</primary><secondary>Windows 95/98</secondary></indexterm>login dialog with an addition: a field for a domain. The domain name should already be filled in, so simply enter your password and click on the OK button. At this point, Windows should consult the primary domain controller (Samba) to see if the password is correct. (You can check the log files if you want to see this in action.) If it worked, congratulations! You have properly configured Samba to act as a domain controller for Windows 95/98 machines and your client is successfully connected.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.5.2.2" id="ch06-SECT-5.2.2">
-<title>Windows NT 4.0</title>
-
-
-<para>
-<indexterm id="ch06-idx-967826-0"><primary>domain logons</primary><secondary>configuring Windows NT 4.0 for</secondary></indexterm>To configure Windows NT for domain logons, open the Network configuration dialog in the Windows NT Control Panel. The first tab that you see should list the identification of the machine.</para>
-
-
-<para>Press the Change button and you should see the dialog box shown in <link linkend="ch06-89804">Figure 6.5</link>. In this dialog box, you can choose to have the Windows NT client become a member of the domain by selecting the radio button marked Domain in the "Member of " box. Then, type in the domain that you wish the client to login to; it should be the same as the workgroup that you specified in the Samba configuration file. Do not check the box marked "Create a Computer Account in the Domain"—Samba does not currently support this functionality.</para>
-
-
-<figure label="6.5" id="ch06-89804">
-<title>Configuring a Windows NT client for domain logons</title>
-
-<graphic width="502" depth="359" fileref="figs/sam.0605.gif"></graphic>
-</figure>
-
-<warning role="ora">
-<para>Like Windows 95/98, if NT complains that you are already logged in, you probably have an active connection to a share in the workgroup (such as a mapped network drive). Disconnect the resource temporarily by right-clicking on its icon and choosing the Disconnect pop-up menu item.</para>
-
-</warning>
-
-<para>After you press the OK button, Windows should present you with a small <indexterm id="ch06-idx-967838-0"><primary>login dialog box, domain logons</primary><secondary>Windows NT</secondary></indexterm>dialog box welcoming you to the domain. At this point, you will need to reset the Windows NT machine. Once it comes up again, the machine will automatically present you with a log on screen similar to the one for Windows 95/98 clients. You can now log in using any account that you have already on the Samba server that is configured to accept logins.</para>
-
-
-<warning role="ora">
-<para>Be sure to select the correct domain in the <indexterm id="ch06-idx-967844-0"><primary>domains</primary><secondary>Windows</secondary><tertiary>caution when selecting</tertiary></indexterm>
-<indexterm id="ch06-idx-967844-1"><primary>Windows NT</primary><secondary>domains</secondary><tertiary>caution when selecting</tertiary></indexterm>Windows NT logon dialog box. Once selected, it may take a moment for Windows NT to build the list of available domains.</para>
-
-</warning>
-
-<para>After you enter the password, Windows NT should consult the primary domain controller (Samba) to see if the password is correct. Again, you can check the log files if you want to see this in action. If it worked, you have successfully configured Samba to act as a domain controller for Windows NT machines.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.5.3" id="ch06-SECT-5.3">
-<title>Domain Options</title>
-
-
-<para><link linkend="ch06-53106">Table 6.9</link> shows the options that are commonly used in association with domain logons.</para>
-
-
-<table label="6.9" id="ch06-53106">
-<title>Windows 95/98 Domain Logon Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>domain logons</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Indicates whether Windows domain logons are to be used.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>domain group map</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Name of the file used to map Unix to Windows NT domain groups.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>domain user map</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Name of the file used to map Unix to Windows NT domain users.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>local group map</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Name of the file used to map Unix to Windows NT local groups.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>revalidate</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba forces users to authenticate themselves with each connection to a share.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="6.5.3.1" id="ch06-SECT-5.3.1">
-<indexterm id="ch06-idx-969495-0"><primary>domain logons option</primary></indexterm>
-<title>
-domain logons</title>
-
-
-<para>This option configures Samba to accept domain logons as a <indexterm id="ch06-idx-968113-0"><primary>PDC (primary domain controller)</primary><secondary>domain option for</secondary></indexterm>primary domain controller. When a client successfully logs on to the domain, Samba will return a special token to the client that allows the client to access domain shares without consulting the PDC again for authentication. Note that the Samba machine must be in user-level security (<literal>security</literal> <literal>=</literal> <literal>user</literal>) and must be the PDC in order for this option to function. In addition, Windows machines will expect a <literal>[netlogon]</literal> share to exist on the Samba server (see <link linkend="ch06-36822">Section 6.5.1</link> earlier in this chapter).</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.5.3.2" id="ch06-SECT-5.3.2">
-<indexterm id="ch06-idx-969498-0"><primary>domain group map option</primary></indexterm>
-<title>
-domain group map</title>
-
-
-<para>This option specifies the location of a <indexterm id="ch06-idx-968114-0"><primary>mapping</primary><secondary>files, options for location of</secondary></indexterm>mapping file designed to translate Windows NT domain group names to Unix group names. The file should reside on the Samba server. For example:</para>
-
-
-<programlisting>/usr/local/samba/private/groups.mapping</programlisting>
-
-
-<para>The file has a simple format:</para>
-
-
-<programlisting><replaceable>UnixGroup = NTGroup</replaceable></programlisting>
-
-
-<para>An example is:</para>
-
-
-<programlisting>admin = Administrative</programlisting>
-
-
-<para>The specified Unix group should be a valid group in the <filename>/etc/group</filename> file. The NT group should be the name to which you want the Unix group to map on an NT client. This option will work only with Windows NT clients.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.5.3.3" id="ch06-SECT-5.3.3">
-<indexterm id="ch06-idx-969499-0"><primary>domain user map option</primary></indexterm>
-<title>
-domain user map</title>
-
-
-<para>This option specifies the location of a mapping file designed to translate Unix usernames to Windows NT domain usernames. The file should reside on the Samba server. For example:</para>
-
-
-<programlisting>/usr/local/samba/private/domainuser.mapping</programlisting>
-
-
-<para>The file has a simple format:</para>
-
-
-<programlisting><replaceable>UnixUsername</replaceable> = [\\<replaceable>Domain</replaceable>\\]<replaceable>NTUserName</replaceable></programlisting>
-
-
-<para>An example entry is:</para>
-
-
-<programlisting>joe = Joseph Miller</programlisting>
-
-
-<para>The Unix name specified should be a valid username in the <filename>/etc/passwd</filename> file. The NT name should be the username to which you want to Unix username to map on an NT client. This option will work with Windows NT clients only.</para>
-
-
-<tip role="ora">
-<para>If you would like more information on how Windows NT uses domain usernames and local groups, we recommend Eric Pearce's <citetitle>Windows NT in a Nutshell</citetitle>, published by O'Reilly.</para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="6.5.3.4" id="ch06-SECT-5.3.4">
-<indexterm id="ch06-idx-969502-0"><primary>local group map option</primary></indexterm>
-<title>
-local group map</title>
-
-
-<para>This option specifies the location of a mapping file designed to translate Windows NT local group names to Unix group names. Local group names include those such as Administrator and Users. The file should reside on the Samba server. For example:</para>
-
-
-<programlisting>/usr/local/samba/private/localgroup.mapping</programlisting>
-
-
-<para>The file has a simple format:</para>
-
-
-<programlisting><replaceable>UnixGroup</replaceable> = [BUILTIN\]<replaceable>NTGroup</replaceable></programlisting>
-
-
-<para>An example entry is:</para>
-
-
-<programlisting>root = BUILTIN\Administrators</programlisting>
-
-
-<para>This option will work with Windows NT clients only. For more information, see Eric Pearce's <citetitle>Windows NT in a Nutshell</citetitle> (O'Reilly).</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.5.3.5" id="ch06-SECT-5.3.5">
-<title>revalidate</title>
-
-
-<para>This share-level option tells Samba to force users to authenticate with <indexterm id="ch06-idx-968116-0"><primary>passwords</primary><secondary>options for</secondary><tertiary>share-level</tertiary></indexterm>
-<indexterm id="ch06-idx-968116-1"><primary>authentication</primary><secondary>share-level option for</secondary></indexterm>
-<indexterm id="ch06-idx-968116-2"><primary>users</primary><secondary>share-level option for authentication of</secondary></indexterm>
-<indexterm id="ch06-idx-968116-3"><primary>revalidation of users</primary></indexterm>passwords each time they connect to a different share on a machine, no matter what level of security is in place on the Samba server. The default value is <literal>no</literal>, which allows users to be trusted once they successfully authenticate themselves. You can override it as:</para>
-
-
-<programlisting>revalidate = yes</programlisting>
-
-
-<para>You can use this option to increase security on your system. However, you should weigh it against the inconvenience of having users revalidate themselves to every share.<indexterm id="ch06-idx-968204-0" class="endofrange" startref="ch06-idx-967533-0"/>
-<indexterm id="ch06-idx-968204-1" class="endofrange" startref="ch06-idx-967533-1"/>
-<indexterm id="ch06-idx-968204-2" class="endofrange" startref="ch06-idx-967533-2"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="6.6" id="ch06-38153">
-<title>Logon Scripts</title>
-
-
-<para>
-<indexterm id="ch06-idx-967542-0" class="startofrange"><primary>logon scripts</primary></indexterm>
-<indexterm id="ch06-idx-967542-1" class="startofrange"><primary>scripts</primary><secondary>logon</secondary></indexterm>
-<indexterm id="ch06-idx-967542-2" class="startofrange"><primary>domain logons</primary><secondary>scripts for</secondary></indexterm>Samba supports the execution of Windows logon scripts, which are scripts (<indexterm id="ch06-idx-968119-0"><primary sortas="BAT scripts">.BAT scripts</primary></indexterm>
-<indexterm id="ch06-idx-968119-1"><primary sortas="CMD scripts"> .CMD scripts</primary></indexterm>.BAT or .CMD) that are executed on the client when a user logs on to a Windows domain. Note that these scripts are stored on the Unix side, but are transported across the network to the client side and executed once a user logs on. These scripts are invaluable for dynamically setting up network configurations for users when they log on. The downside is that because they run on Windows, they must use the <indexterm id="ch06-idx-968120-0"><primary>network configuration commands</primary></indexterm>
-<indexterm id="ch06-idx-968120-1"><primary>resources for further information</primary><secondary>Windows network configuration commands</secondary></indexterm>Windows network configuration commands.</para>
-
-
-<tip role="ora">
-<para>If you would like more information on NET commands, we recommend the following O'Reilly handbooks: <emphasis>Windows NT in a Nutshell</emphasis>, <emphasis>Windows 95 in a Nutshell</emphasis>, and <emphasis>Windows 98 in a Nutshell.</emphasis></para>
-
-</tip>
-
-<para>You can instruct Samba to use a logon script with the <literal>logon</literal> <literal>script</literal> option, as follows:</para>
-
-
-<programlisting>[global]
- domain logons = yes
- security = user
- workgroup = SIMPLE
-
- os level = 34
- local master = yes
- preferred master = yes
- domain master = yes
- logon script = %U.bat
-
-[netlogon]
- comment = The domain logon service
- path = /export/samba/logon
- public = no
- writeable = no
- browsable = no</programlisting>
-
-
-<para>Note that this example uses the <literal>%U</literal> variable, which will individualize the script based on the user that is logging in. It is common to customize logon scripts based on the user or machine name that is logging onto the domain. These scripts can then be used to configure individual settings for users or clients.</para>
-
-
-<para>Each logon script should be stored at the base of the <literal>[netlogon]</literal> share. For example, if the base of the <literal>[netlogon]</literal> share is <filename>/export/samba/logon</filename> and the logon script is <filename>jeff.bat</filename>, the file should be located at <filename>/export/samba/logon/jeff.bat</filename>. When a user logs on to a domain that contains a startup script, he or she will see a small dialog that informs them that the script is executing, as well as any output the script generates in an MS-DOS-like box.</para>
-
-
-<para>One warning: because these scripts are loaded by Windows and executed on the Windows side, they must consist of DOS formatted <indexterm id="ch06-idx-968122-0"><primary>carriage-returns for scripts</primary></indexterm>
-<indexterm id="ch06-idx-968122-1"><primary>DOS-formatted carriage returns</primary></indexterm>
-<indexterm id="ch06-idx-968122-2"><primary>Unix</primary><secondary> carriage returns</secondary></indexterm>carriage-return/linefeed characters instead of Unix carriage returns. It's best to use a DOS- or Windows-based editor to create them.</para>
-
-
-<para>Here is an example of a logon script that sets the current time to match that of the Samba server and maps two network drives, <literal>h</literal> and <literal>i</literal>, to individual shares on the server:</para>
-
-
-<programlisting># Reset the current time to that shown by the server.
-# We must have the "time server = yes" option in the
-# smb.conf for this to work.
-
-echo Setting Current Time...
-net time \\hydra /set /yes
-
-# Here we map network drives to shares on the Samba
-# server
-echo Mapping Network Drives to Samba Server Hydra...
-net use h: \\hydra\data
-net use i: \\hydra\network</programlisting>
-
-
-<sect2 role="" label="6.6.1" id="ch06-SECT-6.0.1">
-<title>Roaming profiles</title>
-
-
-<para><firstterm></firstterm>
-<indexterm id="ch06-idx-968132-0" class="startofrange"><primary>profiles</primary><secondary>roaming</secondary></indexterm>
-<indexterm id="ch06-idx-968132-1" class="startofrange"><primary>roaming profiles</primary></indexterm>In Windows 95 and NT, each user can have his or her own <firstterm>profile</firstterm>
-<indexterm id="ch06-idx-968123-0"><primary>profiles</primary></indexterm>. A profile bundles information such as: the appearance of a user's desktop, the applications that appear on the start menus, the background, and other miscellaneous items. If the profile is stored on a local disk, it's called a <firstterm>local profile</firstterm>
-<indexterm id="ch06-idx-968124-0"><primary>profiles</primary><secondary>local</secondary></indexterm>
-<indexterm id="ch06-idx-968124-1"><primary>local profiles</primary></indexterm>, since it describes what a user's environment is like on one machine. If the profile is stored on a server, on the other hand, the user can download the same profile to any client machine that is connected to the server. The latter is called a <firstterm>roaming profile</firstterm> because the user can roam around from machine to machine and still use the same profile. This makes it particularly convenient when someone might be logging in from his or her desk one day and from a portable in the field the next. <link linkend="ch06-71393">Figure 6.6</link> illustrates local and roaming profiles.</para>
-
-
-<figure label="6.6" id="ch06-71393">
-<title>Local profiles versus roaming profiles</title>
-
-<graphic width="502" depth="303" fileref="figs/sam.0606.gif"></graphic>
-</figure>
-
-<para>Samba will provide roaming profiles if it is configured for domain logons and you provide a tree of directories pointed to by the <literal>logon</literal> <literal>path</literal> option. This option is typically used with one of the user variables, as shown in this example:</para>
-
-
-<programlisting>[global]
- domain logons = yes
- security = user
- workgroup = SIMPLE
- os level = 34
- local master = yes
- preferred master = yes
- domain master = yes
-
- logon path = \\hydra\profile\%U</programlisting>
-
-
-<para>We need to create a new share to support the profiles, which is a basic disk share accessible only by the Samba process' user (<literal>root</literal>). This share must be writeable, but should not be browseable. In addition, we must create a directory for each user who wishes to log on (based on how we specified our <literal>logon</literal> <literal>path</literal> in the example above), which is accessible only by that user. For an added measure of security, we use the <literal>directory</literal> <literal>mode</literal> and <literal>create</literal> <literal>mode</literal> options to keep anyone who connects to it from viewing or altering the files created in those directories:</para>
-
-
-<programlisting>[profile]
- comment = User profiles
- path = /export/samba/profile
- create mode = 0600
- directory mode = 0700
- writable = yes
- browsable = no</programlisting>
-
-
-<para>Once a user initially logs on, the Windows client will create a <filename>user.dat</filename> or <filename>ntuser.dat</filename> file—depending on which operating system the client is running. The client then uploads the contents of the desktop, the Start Menu, the Network Neighborhood, and the programs folders in individual folders in the directory. When the user subsequently logs on, those contents will be downloaded from the server and activated for the client machine with which the user is logging on. When he or she logs off, those contents will be uploaded back on the server until the next time the user connects. If you look at the directory listing of a profile folder, you'll see the following:</para>
-
-
-<programlisting># ls -al
-
-total 321
-drwxrwxr-x 9 root simple Jul 21 20:44 .
-drwxrwxr-x 4 root simple Jul 22 14:32 ..
-drwxrwx--- 3 fred develope Jul 12 07:15 Application Data
-drwxrwx--- 3 fred develope Jul 12 07:15 Start Menu
-drwxrwx--- 2 fred develope Jul 12 07:15 cookies
-drwxrwx--- 2 fred develope Jul 12 07:15 desktop
-drwxrwx--- 7 fred develope Jul 12 07:15 history
-drwxrwx--- 2 fred develope Jul 12 07:15 nethood
-drwxrwx--- 2 fred develope Jul 19 21:05 recent
--rw------- 1 fred develope Jul 21 21:59 user.dat</programlisting>
-
-
-<para>The <filename>user.dat</filename> files are binary configuration files, created automatically by Windows. They can be edited with the Profile Editor on a Windows client, but they can be somewhat tricky to get correct. Samba supports them correctly for all clients up to NT 5.0 beta, but they're still relatively new<firstterm></firstterm>
-<indexterm id="ch06-idx-968138-0" class="endofrange" startref="ch06-idx-968132-0"/>
-<indexterm id="ch06-idx-968138-1" class="endofrange" startref="ch06-idx-968132-1"/>.</para>
-
-
-<tip role="ora">
-<para>Hints and HOWTOs for handling logon scripts are available in the Samba documentation tree, in both <filename>docs/textdocs/DOMAIN.txt</filename> and <filename>docs/textdocs/PROFILES.txt</filename>.<firstterm></firstterm>
-<indexterm id="ch06-idx-968148-0"><primary>profiles</primary><secondary>roaming</secondary></indexterm>
-<indexterm id="ch06-idx-968148-1"><primary>roaming profiles</primary></indexterm></para>
-
-</tip>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.6.2" id="ch06-SECT-6.0.2">
-<title>Mandatory profiles</title>
-
-
-<para>
-<indexterm id="ch06-idx-968144-0"><primary>profiles</primary><secondary>mandatory</secondary></indexterm>
-<indexterm id="ch06-idx-968144-1"><primary>mandatory profiles</primary></indexterm>Users can also have <firstterm>mandatory profiles</firstterm>, which are roaming profiles that they cannot change. For example, with a mandatory profile, if a user adds a command to the Start Menu on Tuesday, it will be gone when he or she logs in again on Wednesday. The mandatory profile is simply a <filename>user.dat</filename> file that has been renamed to <filename>user.man</filename> and made read-only on the Unix server. It normally contains settings that the administrator wishes to ensure the user always executes. For example, if an administrator wants to create a <indexterm id="ch06-idx-968145-0"><primary>fixed user configuration</primary></indexterm>fixed user configuration, he or she can do the following:</para>
-
-
-<orderedlist>
-<listitem><para>Create the read-write directory on the Samba server.</para></listitem>
-<listitem><para>Set the <literal>logon</literal> <literal>path</literal> option in the <emphasis>smb.conf</emphasis> file to point to this directory.</para></listitem>
-<listitem><para>Logon as the user from Windows 95/98 to have the client populate the directory.</para></listitem>
-<listitem><para>Rename the resulting <filename>user.dat</filename> to <filename>user.man</filename>.</para></listitem>
-<listitem><para>Make the directory and its contents read only.</para></listitem>
-</orderedlist>
-
-<para>Mandatory profiles are fairly unusual. Roaming profiles, on the other hand, are one of the more desirable features of Windows that Samba can support.</para>
-</sect2>
-
-
-
-
-<sect2 role="" label="6.6.3" id="ch06-SECT-6.1">
-<title>Logon Script Options</title>
-
-
-<para>
-<indexterm id="ch06-idx-968152-0" class="startofrange"><primary>logon scripts</primary><secondary>options for</secondary></indexterm><link linkend="ch06-46661">Table 6.10</link> summarizes the options commonly used in association with Windows domain logon scripts.</para>
-
-
-<table label="6.10" id="ch06-46661">
-<title>Logon Script Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>logon script</literal></para></entry>
-
-<entry colname="col2"><para>string (DOS path)</para></entry>
-
-<entry colname="col3"><para>Name of DOS/NT batch file</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>logon path</literal></para></entry>
-
-<entry colname="col2"><para>string (UNC server and share name)</para></entry>
-
-<entry colname="col3"><para>Location of roaming profile for user</para></entry>
-
-<entry colname="col4"><para><literal>\\%N\%U\profile</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>logon drive</literal></para></entry>
-
-<entry colname="col2"><para>string (drive letter)</para></entry>
-
-<entry colname="col3"><para>Specifies the logon drive for a home directory (NT only)</para></entry>
-
-<entry colname="col4"><para><literal>Z</literal>:</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>logon home</literal></para></entry>
-
-<entry colname="col2"><para>string (UNC server and share name)</para></entry>
-
-<entry colname="col3"><para>Specifies a location for home directories for clients logging on to the domain</para></entry>
-
-<entry colname="col4"><para><literal>\\%N\%U</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="6.6.3.1" id="ch06-SECT-6.1.1">
-<indexterm id="ch06-idx-969510-0"><primary>logon script option</primary></indexterm>
-<title>
-logon script</title>
-
-
-<para>This option specifies a Windows .BAT or .CMD file with lines ending in carriage-return/line feed that will be executed on the client after a user has logged on to the domain. Each logon script should be stored at the base of a share entitled <literal>[netlogin]</literal> (see <link linkend="ch06-36822">Section 6.5.1</link> for details.) This option frequently uses the <literal>%U</literal> or <literal>%m</literal> variables (user or NetBIOS name) to point to an individual script. For example:</para>
-
-
-<programlisting>logon script = %U.bat</programlisting>
-
-
-<para>will execute a script based on the username located at the base of the <literal>[netlogin]</literal> share. If the user who is connecting is <literal>fred</literal> and the path of the <literal>[netlogin]</literal> share maps to the directory <filename>/export/samba/netlogin</filename>, the script should be <filename>/export/samba/netlogin/fred.bat</filename>. Because these scripts are downloaded to the client and executed on the Windows side, they must consist of DOS formatted carriage-return/linefeed characters instead of Unix carriage returns.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.6.3.2" id="ch06-SECT-6.1.2">
-<indexterm id="ch06-idx-969513-0"><primary>logon path option</primary></indexterm>
-<title>
-logon path</title>
-
-
-<para>This option provides a location for <indexterm id="ch06-idx-968161-0"><primary>roaming profiles</primary><secondary>option for location of</secondary></indexterm>
-<indexterm id="ch06-idx-968161-1"><primary>profiles</primary><secondary>roaming</secondary><tertiary>option for location of</tertiary></indexterm>roaming profiles. When the user logs on, a roaming profile will be downloaded from the server to the client and activated for the user who is logging on. When the user logs off, those contents will be uploaded back on the server until the next time the user connects.</para>
-
-
-<para>It is often more secure to create a separate share exclusively for storing user profiles:</para>
-
-
-<programlisting>logon path = \\hydra\profile\%U</programlisting>
-
-
-<para>For more informaiton on this option, see <link linkend="ch06-38153">Section 6.6</link> earlier in this chapter.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.6.3.3" id="ch06-SECT-6.1.3">
-<indexterm id="ch06-idx-969514-0"><primary>logon drive option</primary></indexterm>
-<title>
-logon drive</title>
-
-
-<para>This option specifies the drive letter on an NT client to which the home directory specified with the <literal>logon</literal> <literal>home</literal> option will be mapped. Note that this option will work with Windows NT clients only. For example:</para>
-
-
-<programlisting>logon home = I:</programlisting>
-
-
-<para>You should always use drive letters that will not conflict with fixed drives on the client machine. The default is Z:, which is a good choice because it is as far away from A:, C:, and D: as possible.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.6.3.4" id="ch06-SECT-6.1.4">
-<indexterm id="ch06-idx-969517-0"><primary>logon home option</primary></indexterm>
-<title>
-logon home </title>
-
-
-<para>This option specifies the location of a user's <indexterm id="ch06-idx-968162-0"><primary>home directory, user's</primary><secondary>logon script option for location of</secondary></indexterm>
-<indexterm id="ch06-idx-968162-1"><primary>users</primary><secondary>home directory</secondary><tertiary>logon script option for location of</tertiary></indexterm>home directory for use by the DOS NET commands. For example, to specify a home directory as a share on a Samba server, use the following:</para>
-
-
-<programlisting>logon home = \\hydra\%U</programlisting>
-
-
-<para>Note that this works nicely with the <literal>[homes]</literal> service, although you can specify any directory you wish. Home directories can be mapped with a logon script using the following command:</para>
-
-
-<programlisting>NET USE I: /HOME</programlisting>
-
-
-<para>In addition, you can use the User Environment Profile under User Properties in the Windows NT User Manager to verify that the home directory has automatically been set.<indexterm id="ch06-idx-968155-0" class="endofrange" startref="ch06-idx-968152-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.6.4" id="ch06-SECT-6.2">
-<title>Other Connection Scripts</title>
-
-
-<para>
-<indexterm id="ch06-idx-968164-0"><primary>scripts</primary><secondary>connection</secondary></indexterm>
-<indexterm id="ch06-idx-968164-1"><primary>connections</primary><secondary>scripts for</secondary></indexterm>After a user successfully makes a connection to any Samba share, you may want the Samba server to execute a program on its side to prepare the share for use. Samba allows scripts to be executed before and after someone connects to a share. You do not need to be using Windows domains to take advantage of the options. <link linkend="ch06-67528">Table 6.11</link> introduces some of the configuration options provided for setting up users.</para>
-
-
-<table label="6.11" id="ch06-67528">
-<title>Connection Script Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>root preexec</literal></para></entry>
-
-<entry colname="col2"><para>string (Unix command)</para></entry>
-
-<entry colname="col3"><para>Sets a command to run as <literal>root</literal>, before connecting to the share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>preexec (exec)</literal></para></entry>
-
-<entry colname="col2"><para>string (Unix command)</para></entry>
-
-<entry colname="col3"><para>Sets a Unix command to run as the user before connecting to the share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>postexec</literal></para></entry>
-
-<entry colname="col2"><para>string (Unix command)</para></entry>
-
-<entry colname="col3"><para>Sets a Unix command to run as the user after disconnecting from the share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>root postexec</literal></para></entry>
-
-<entry colname="col2"><para>string (Unix command)</para></entry>
-
-<entry colname="col3"><para>Sets a Unix command to run as <literal>root</literal> after disconnecting from the share.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="6.6.4.1" id="ch06-SECT-6.2.1">
-<indexterm id="ch06-idx-969520-0"><primary>root preexec option</primary></indexterm>
-<title>
-root preexec</title>
-
-
-<para>The first form of the logon command is called <literal>root</literal> <literal>preexec</literal>. This option specifies a Unix command as its value that will be run <emphasis>as the root user</emphasis> before any connection to a share is completed. You should use this option specifically for performing actions that require <indexterm id="ch06-idx-968166-0"><primary>root user</primary></indexterm>
-<indexterm id="ch06-idx-968166-1"><primary>privileges, option for</primary></indexterm>root privilege. For example, <literal>root</literal> <literal>preexec</literal> can be used to mount CD-ROMs for a share that makes them available to the clients, or to create necessary directories. If no <literal>root</literal> <literal>preexec</literal> option is specified, there is no default action. Here is an example of how you can use the command to mount a CD-ROM:</para>
-
-
-<programlisting>[homes]
- browseable = no
- writeable = yes
- root preexec = /etc/mount /dev/cdrom2</programlisting>
-
-
-<para>Remember that these commands will be run as the root user. Therefore, in order to ensure security, users should never be able to modify the target of the <literal>root</literal> <literal>preexec</literal> command.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.6.4.2" id="ch06-SECT-6.2.2">
-<indexterm id="ch06-idx-969523-0"><primary>preexec option</primary></indexterm>
-<title>
-preexec</title>
-
-
-<para>The next option run before logon is the <literal>preexec</literal> option, sometimes just called <literal>exec</literal>. This is an ordinary unprivileged command run by Samba as the user specified by the variable <literal>%u</literal>. For example, a common use of this option is to perform <indexterm id="ch06-idx-968167-0"><primary>log files/logging</primary><secondary>options for</secondary></indexterm>logging, such as the following:</para>
-
-
-<programlisting>[homes]
-<userinput>preexec = echo "%u connected to %S from %m (%I)\" >>/tmp/.log</userinput></programlisting>
-
-
-<para>Be warned that any information the command sends to standard output will not be seen by the user, but is instead thrown away. If you intend to use a <literal>preexec</literal> script, you should ensure that it will run correctly before having Samba invoke it.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.6.4.3" id="ch06-SECT-6.2.3">
-<indexterm id="ch06-idx-969524-0"><primary>postexec option</primary></indexterm>
-<title>
-postexec</title>
-
-
-<para>Once the user disconnects from the share, the command specified with <literal>postexec</literal> is run as the user on the Samba server to do any necessary cleanup. This option is essentially the same as the <literal>preexec</literal> option. Again, remember that the command is run as the user represented by <literal>%u</literal> and any information sent to standard output will be ignored.</para>
-</sect3>
-
-
-
-<sect3 role="" label="6.6.4.4" id="ch06-SECT-6.2.4">
-<indexterm id="ch06-idx-969525-0"><primary>root postexec option</primary></indexterm>
-<title>
-root postexec</title>
-
-
-<para>Following the <literal>postexec</literal> option, the <literal>root</literal> <literal>postexec</literal> command is run, if one has been specified. Again, this option specifies a Unix command as its value that will be run <emphasis>as the</emphasis> <indexterm id="ch06-idx-968179-0"><primary>root user</primary></indexterm>
-<indexterm id="ch06-idx-968179-1"><primary>privileges, option for</primary></indexterm><emphasis>root user</emphasis> before disconnecting from a share. You should use this option specifically for performing actions that require root privilege.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="6.6.5" id="ch06-SECT-6.3">
-<title>Working with NIS and NFS</title>
-
-
-<para>Finally, Samba has the ability to work with <indexterm id="ch06-idx-968184-0"><primary>NIS/NIS+ protocol</primary><secondary>how Samba works with</secondary></indexterm>NIS and NIS+. If there is more than one file server, and each runs Samba, it may be desirable to have the SMB client connect to the server whose disks actually house the user's home directory. It isn't normally a good idea to ship files across the network once via NFS to a Samba server, only to be sent across the network once again to the client via SMB. (For one thing, it's slow—about 30 percent of normal Samba speed). Therefore, there are a pair of options to tell Samba that NIS knows the name of the right server and indicate in which NIS map the information lives.</para>
-
-
-<para><link linkend="ch06-27466">Table 6.12</link> introduces some of the other configuration options specifically for setting up users.</para>
-
-
-<table label="6.12" id="ch06-27466">
-<title>NIS Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>nis homedir</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, use NIS instead of <filename>/etc/passwd</filename> to look up the path of a user's home directory</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>homedir map</literal></para></entry>
-
-<entry colname="col2"><para>string (NIS map name)</para></entry>
-
-<entry colname="col3"><para>Sets the NIS map to use to look up a user's home directory</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="6.6.5.1" id="ch06-SECT-6.3.1">
-<title>nis homedir and homedir map</title>
-
-
-<para>The <literal>nis</literal>
-<indexterm id="ch06-idx-969528-0"><primary>nis homedir option</primary></indexterm>
-<indexterm id="ch06-idx-969528-1"><primary>homedir map option</primary></indexterm> <literal>homedir</literal> and <literal>homedir</literal> <literal>map</literal> options are for Samba servers on network sites where Unix home directories are provided using NFS, the automounter, and NIS (Yellow Pages).</para>
-
-
-<para>The <literal>nis</literal> <literal>homedir</literal> option indicates that the home directory server for the user needs to be looked up in NIS. The <literal>homedir</literal> <literal>map</literal> option tells Samba what NIS map to look in for the server that has the user's home directory. The server needs to be a Samba server, so the client can do an SMB connect to it, and the other Samba servers need to have NIS installed so they can do the lookup.</para>
-
-
-<para>For example, if user <literal>joe</literal> asks for a share called <literal>[joe]</literal>, and the <literal>nis</literal> <literal>homedir</literal> option is set to <literal>yes</literal>, Samba will look in the file specified by <literal>homedir</literal> <literal>map</literal> for a home directory for <literal>joe</literal>. If it finds one, Samba will return the associated machine name to the client. The client will then try to connect to <emphasis>that</emphasis> machine and get the share from there. Enabling NIS lookups looks<indexterm id="ch06-idx-967545-0" class="endofrange" startref="ch06-idx-967542-0"/>
-<indexterm id="ch06-idx-967545-1" class="endofrange" startref="ch06-idx-967542-1"/>
-<indexterm id="ch06-idx-967545-2" class="endofrange" startref="ch06-idx-967542-2"/> like the following:</para>
-
-
-<programlisting>[globals]
- nis homedir = yes
- homedir map = amd.map</programlisting>
-</sect3>
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="7" id="SAMBA-CH-7">
-<title>Printing and Name Resolution</title>
-
-
-
-
-<para>
-<indexterm id="ch07-idx-956351-0" class="startofrange"><primary>printing</primary></indexterm>This chapter tackles two Samba topics: setting up printers for use with a Samba server and configuring Samba to use or become a Windows Internet Name Service (WINS) server. Samba allows client machines to send documents to printers connected to the Samba server. In addition, Samba can also assist you with printing Unix documents to a printer on a Windows machine. In the first part of this chapter, we will discuss how to get printers configured to work on either side.</para>
-
-
-<para>In the second half of the chapter, we will introduce the Windows Internet Name Service, Microsoft's implementation of a NetBIOS Name Server (NBNS). As mentioned in <link linkend="ch01-48078">Chapter 1</link>, an NBNS allows machines to perform name resolution on a NetBIOS network without having to rely on broadcasts. Instead, each machine knows exactly where the WINS server is and can query it for the IP addresses of other machines on the network.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="7.1" id="ch07-61388">
-<title>Sending Print Jobs to Samba</title>
-
-
-<para>
-<indexterm id="ch07-idx-956360-0" class="startofrange"><primary>printing</primary><secondary sortas="Samba">through Samba</secondary></indexterm>A printer attached to the Samba server shows up in the list of shares offered in the Network Neighborhood. If the printer is registered on the client machine and the client has the correct printer driver installed, the client can effortlessly send print jobs to a printer attached to a Samba server. <link linkend="ch07-35075">Figure 7.1</link> shows a Samba printer as it appears in the Network Neighborhood of a Windows client.</para>
-
-
-<para>
-<indexterm id="ch07-idx-956377-0"><primary>printing</primary><secondary>on a network, steps in</secondary></indexterm>
-<indexterm id="ch07-idx-956377-1"><primary>networking</primary><secondary>printing on a network, steps in</secondary></indexterm>To administer printers with Samba, you should understand the basic process by which printing takes place on a network. Sending a print job to a printer on a Samba server involves four steps:</para>
-
-
-<orderedlist>
-<listitem><para>Opening and authenticating a connection to the printer share</para></listitem>
-<listitem><para>Copying the file over the network</para></listitem>
-<listitem><para>Closing the connection</para></listitem>
-<listitem><para>Printing and deleting the copy of the file</para>
-
-
-<figure label="7.1" id="ch07-35075">
-<title>A Samba printer in the Network Neighborhood</title>
-
-<graphic width="502" depth="171" fileref="figs/sam.0701.gif"></graphic>
-</figure></listitem>
-</orderedlist>
-
-<para>When a print job arrives at a Samba server, the print data is temporarily written to disk in the directory specified by the <literal>path</literal> option of the printer share. Samba then executes a Unix print command to send that data file to the printer. The job is printed as the authenticated user of the share. Note that this may be the guest user, depending on how the share is configured.</para>
-
-
-<sect2 role="" label="7.1.1" id="ch07-SECT-1.1">
-<title>Print Commands</title>
-
-
-<para>
-<indexterm id="ch07-idx-956378-0"><primary>printing</primary><secondary>commands</secondary></indexterm>In order to print the document, you'll need to tell Samba what the command is to print and delete a file. On Linux, such a command is:</para>
-
-
-<programlisting>lpr -r -P<replaceable>printer</replaceable> <replaceable>file</replaceable></programlisting>
-
-
-<para>This tells <literal>lpr</literal> to copy the document to a spool area, usually <filename>/var/spool</filename>, retrieve the name of the printer in the system configuration file (<filename>/etc/printcap</filename>), and interpret the rules it finds there to decide how to process the data and which physical device to send it to. Note that because the <literal>-r</literal> option has been listed, the file specified on the command line will be deleted after it has been printed. Of course, the file removed is just a copy stored on the Samba server; the original file on the client is unaffected.</para>
-
-
-<para>Linux uses a Berkeley (BSD) style of printing. However, the process is similar on System V Unix. Here, printing and deleting becomes a compound command:</para>
-
-
-<programlisting>lp -d<replaceable>printer</replaceable> -s <replaceable>file</replaceable>; rm <replaceable>file</replaceable></programlisting>
-
-
-<para>With System V, the <filename>/etc/printcap</filename> file is replaced with different set of configuration files hiding in <filename>/usr/spool/lp</filename>, and there is no option to delete the file. You have to do it yourself, which is why we have added the <literal>rm</literal> command afterward.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.1.2" id="ch07-SECT-1.2">
-<title>Printing Variables</title>
-
-
-<para>
-<indexterm id="ch07-idx-956380-0"><primary>printing</primary><secondary>variables for</secondary></indexterm>Samba provides four variables specifically for use with <indexterm id="ch07-idx-956450-0" class="startofrange"><primary>printing</primary><secondary>configuration options</secondary></indexterm>printing configuration options. They are shown in <link linkend="ch07-29758">Table 7.1</link>.</para>
-
-
-<table label="7.1" id="ch07-29758">
-<title>Printing Variables </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Variable</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>%s</literal></para></entry>
-
-<entry colname="col2"><para>The full pathname of the file on the Samba server to be printed</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%f</literal></para></entry>
-
-<entry colname="col2"><para>The name of the file itself (without the preceding path) on the Samba server to be printed</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%p</literal></para></entry>
-
-<entry colname="col2"><para>The name of the Unix printer to use</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%j</literal></para></entry>
-
-<entry colname="col2"><para>The number of the print job (for use with <literal>lprm</literal>, <literal>lppause</literal>, and <literal>lpresume</literal>)</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.1.3" id="ch07-SECT-1.3">
-<title>A Minimal Printing Setup</title>
-
-
-<para>
-<indexterm id="ch07-idx-956382-0" class="startofrange"><primary>printing</primary><secondary>configuration, minimal</secondary></indexterm>Let's start with a simple but illustrative printing share. Assuming that you're on a Linux system and you have a printer called <literal>lp</literal> listed in the printer capabilities file, the following addition to your <filename>smb.conf</filename>
-<indexterm id="ch07-idx-956439-0"><primary>smb.conf (Samba configuration) file</primary><secondary>configuring printers</secondary></indexterm> file will make the printer accessible through the network:</para>
-
-
-<programlisting>[printer1]
- printable = yes
- print command = /usr/bin/lpr -r %s
- printer = lp
- printing = BSD
- read only = yes
- guest ok = yes</programlisting>
-
-
-<para>This configuration allows anyone to send data to the printer, something we may want to change later. For the moment, what's important to understand is that the variable <literal>%s</literal> in the <literal>print</literal> <literal>command</literal> option will be replaced with the name of the file to be printed when Samba executes the command. Changing the <literal>print command</literal> to reflect a different style of Unix machine typically involves only replacing the right side of the <literal>print</literal> <literal>command</literal> option with whatever command you need for your system and changing the target of the <literal>printing</literal> option.</para>
-
-
-<para>Let's look at the commands for a <indexterm id="ch07-idx-956440-0"><primary>System V Unix</primary><secondary>printer configuration for</secondary></indexterm>
-<indexterm id="ch07-idx-956440-1"><primary>Unix</primary><secondary>System V</secondary><tertiary>printer configuration for</tertiary></indexterm>System V Unix. With variable substitution, the System V Unix command becomes:</para>
-
-
-<programlisting>print command = lp -d%p -s %s; rm %s</programlisting>
-
-
-<para>As mentioned earlier, the <literal>%p</literal> variable resolves to the name of the printer, while the <literal>%s</literal> variable resolves to the name of the file. After that, you can change the <literal>printing</literal> option to reflect that you're using a System V architecture:</para>
-
-
-<programlisting>printing = SYSV</programlisting>
-
-
-<para>If you are using <indexterm id="ch07-idx-956441-0"><primary>share-level security</primary><secondary>printing and guest accounts</secondary></indexterm>share-level security, pay special attention to the guest account used by Samba. The typical setting, <literal>nobody</literal>, may not be allowed to print by the operating system. If that's true for your operating system, you should place a <literal>guest</literal> <literal>account</literal> option under the <indexterm id="ch07-idx-956445-0"><primary>print shares</primary></indexterm>printing share (or even perhaps the global share) specifying an account that can. A popular candidate with the Samba authors is the <literal>ftp</literal> account, which is often preconfigured to be safe for untrusted guest users. You can set it with the following command:</para>
-
-
-<programlisting>guest account = ftp</programlisting>
-
-
-<para>Another common printing issue is that clients may need to request the status of a <indexterm id="ch07-idx-956443-0"><primary>printing</primary><secondary>print jobs</secondary></indexterm>print job sent to the Samba server. Samba will not reject a document from being sent to an already busy printer share. Consequently, Samba needs the ability to communicate not only the status of the current printing job to the client, but also which documents are currently waiting to be printed on that printer. Samba also has to provide the client the ability to pause print jobs, resume print jobs, and remove print jobs from the printing queue. Samba provides options for each of these tasks. As you might expect, they borrow functionality from existing Unix commands. The options are:</para>
-
-
-<itemizedlist>
-<listitem><para><literal>lpq command</literal></para></listitem>
-<listitem><para><literal>lprm command</literal></para></listitem>
-<listitem><para><literal>lppause command</literal></para></listitem>
-<listitem><para><literal>lpresume command</literal></para></listitem>
-</itemizedlist>
-
-<para>We will cover these options in more detail below. For the most part, however, the value of the <literal>printing</literal> configuration option will determine their values, and you should not need to alter the default values of these options.</para>
-
-
-<para>Here are a few important items to remember about printing shares:</para>
-
-
-<itemizedlist>
-<listitem><para>You must put <literal>printable</literal> <literal>=</literal> <literal>yes</literal> in all printer shares (even <literal>[printers]</literal>), so that Samba will know that they are printer shares. If you forget, the shares will not be usable for printing and will instead be treated as disk shares.</para></listitem>
-<listitem><para>If you set the <literal>path</literal> configuration option in the printer section, any files sent to the printer(s) will be copied to the directory you specify instead of to the default location of <filename>/tmp</filename>. As the amount of disk space allocated to <filename>/tmp</filename> can be relatively small in some Unix operating systems, many administrators opt to use <filename>/var/spool</filename> or some other directory instead.</para></listitem>
-<listitem><para>The <literal>read only</literal> option is ignored for printer shares.</para></listitem>
-<listitem><para>If you set <literal>guest</literal> <literal>ok</literal> <literal>=</literal> <literal>yes</literal> in a printer share and Samba is configured for share-level security, it will allow anyone to send data to the printer as the <literal>guest</literal> <literal>account</literal> user.</para></listitem>
-</itemizedlist>
-
-<para>Using one or more Samba machines as a print server gives you a great deal of flexibility on your LAN. You can easily partition your available printers, restricting some to members of one department, or you can maintain a bank of printers available to all. In addition, you can restrict a printer to a selected few by adding the trusty <literal>valid</literal> <literal>users</literal> option to its share definition:</para>
-
-
-<programlisting>[deskjet]
- printable = yes
- path = /var/spool/samba/print
- valid users = gail sam</programlisting>
-
-
-<para>All of the other share accessibility options defined in the previous chapter should work for printing shares as well. Since the printers themselves are accessed through Samba by name, it's also simple to delegate print services among several servers using familiar Unix commands for tasks such as load balancing or maintenance.<indexterm id="ch07-idx-956385-0" class="endofrange" startref="ch07-idx-956382-0"/></para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.1.4" id="ch07-SECT-1.4">
-<title>The [printers] Share</title>
-
-
-<para>
-<indexterm id="ch07-idx-956390-0"><primary>print shares</primary></indexterm><link linkend="ch04-21486">Chapter 4</link>, briefly introduced <literal>[printers]</literal>, a special share for automatically creating printing services. Let's review how it works: if you create a share named <literal>[printers]</literal> in the configuration file, Samba will automatically read in your printer capabilities file and create a printing share for each printer that appears in the file. For example, if the Samba server had <literal>lp</literal>, <literal>pcl</literal> and <literal>ps</literal> printers in its printer capabilities file, Samba would provide three printer shares with those names, each configured with the options in the <literal>[printers]</literal> share.</para>
-
-
-<para>
-<indexterm id="ch07-idx-956509-0"><primary>print shares</primary><secondary>created by Samba</secondary></indexterm>Recall that Samba obeys following rules when a client requests a share that has not been created through the <filename>smb.conf</filename> file:</para>
-
-
-<itemizedlist>
-<listitem><para>If the share name matches a username in the system password file and a <literal>[homes]</literal> share exists, a new share is created with the name of the user and is initialized using the values given in the <literal>[homes]</literal> and <literal>[global]</literal> sections.</para></listitem>
-<listitem><para>Otherwise, if the name matches a printer in the system printer capabilities file, and a <literal>[printers]</literal> share exists, a new share is created with the name of the printer and initialized using the values given in the <literal>[printers]</literal> section. (Variables in the <literal>[global]</literal> section do not apply here.)</para></listitem>
-<listitem><para>If neither of those succeed, Samba looks for a <literal>default</literal> <literal>service</literal> share. If none is found, it returns an error.</para></listitem>
-</itemizedlist>
-
-<para>This brings to light an important point: be careful that you do not give a <indexterm id="ch07-idx-956508-0"><primary>printers</primary><secondary>names</secondary><tertiary>caution with</tertiary></indexterm>printer the same name as a user. Otherwise, you will end up connecting to a disk share when you may have wanted a printer share instead.</para>
-
-
-<para>Here is an example <literal>[printers]</literal> share for a Linux (BSD) system. Some of these options are already defaults; however, we have listed them anyway for illustrative purposes:</para>
-
-
-<programlisting>[global]
- printing = BSD
- print command = /usr/bin/lpr -P%p -r %s
- printcap file = /etc/printcap
- min print space = 2000
-
-[printers]
- path = /usr/spool/public
- printable = true
- guest ok = true
- guest account = pcguest</programlisting>
-
-
-<para>Here, we've given Samba global options that specify the printing type (BSD), a print command to send data to the printer and remove a temporary file, our default printer capabilities file, and a minimum printing space of 2 megabytes.</para>
-
-
-<para>In addition, we've created a <literal>[printers]</literal> share for each of the system printers. Our temporary spooling directory is specified by the <literal>path</literal> option: <filename>/usr/spool/public</filename>. Each of the shares is marked as printable—this is necessary, even in the <literal>[printers]</literal> section. The two <literal>guest</literal> options are useful in the event that Samba is using share-level security: we allow guest access to the printer and we specify the guest user that Samba should use to execute print commands.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.1.5" id="ch07-SECT-1.5">
-<title>Test Printing</title>
-
-
-<para>
-<indexterm id="ch07-idx-956391-0"><primary>printing</primary><secondary>test for</secondary></indexterm>Here is how you can test printing from the Samba server. Let's assume the most complex case and use a guest account. First, run the Samba <emphasis>testparm</emphasis> command on your configuration file that contains the print shares, as we did in <link linkend="SAMBA-CH-2">Chapter 2</link>. This will tell you if there are any syntactical problems with the configuration file. For example, here is what you would see if you left out the <literal>path</literal> configuration option in the previous example:</para>
-
-
-<programlisting># testparm
-Load smb config files from /usr/local/samba/lib/smb.conf
-Processing configuration file "/usr/local/samba/lib/smb.conf"
-Processing section "[global]"
-Processing section "[homes]"
-Processing section "[data]"
-Processing section "[printers]"
-No path in service printers - using /tmp
-Loaded services file OK.
-Press enter to see a dump of your service definitions
-Global parameters:
- load printers: Yes
- printcap name: /etc/printcap
-Default service parameters:
- guest account: ftp
- min print space: 0
- print command: lpr -r -P%p %s
- lpq command: lpq -P%p
- lprm command: lprm -P%p %j
-lppause command:
- lpresume command:
- Service parameters [printers]:
- path: /tmp
- print ok: Yes
- read only: true
- public: true</programlisting>
-
-
-<para>Next, log on as the guest user, go to the spooling directory, and ensure that you can print using the same command that <emphasis>testparm</emphasis> says Samba will use. As mentioned before, this will tell you if you need to change the guest account, as the default account may not be allowed to print.</para>
-
-
-<para>Finally, print something to the Samba server via <literal>smbclient</literal>, and see if the following actions occur:</para>
-
-
-<itemizedlist>
-<listitem><para>The job appears (briefly) in the Samba spool directory specified by the path.</para></listitem>
-<listitem><para>The job shows up in your print systems spool directory.</para></listitem>
-<listitem><para>The job disappears from the spool directory that Samba used.</para></listitem>
-</itemizedlist>
-
-<para>If <emphasis>smbclient</emphasis> cannot print, you can reset the <literal>print</literal> <literal>command</literal> option to collect debugging information:</para>
-
-
-<programlisting>print command = /bin/cat %s >>/tmp/printlog; rm %s</programlisting>
-
-
-<para>or:</para>
-
-
-<programlisting>print command = echo "printed %s on %p" >>/tmp/printlog</programlisting>
-
-
-<para>A common problem with Samba printer configuration is forgetting to use the full <indexterm id="ch07-idx-956511-0"><primary>pathnames</primary><secondary>printer configuration and</secondary></indexterm>
-<indexterm id="ch07-idx-956511-1"><primary>printing</primary><secondary>pathnames used in commands for</secondary></indexterm>pathnames for commands; simple commands often don't work because the guest account's PATH doesn't include them. Another frequent problem is not having the correct <indexterm id="ch07-idx-956512-0"><primary>permissions</primary><secondary sortas="printing">for printing</secondary></indexterm>
-<indexterm id="ch07-idx-956512-1"><primary>printing</primary><secondary>permissions for</secondary></indexterm>permissions on the spooling directory.<indexterm id="ch07-idx-956494-0" class="endofrange" startref="ch07-idx-956450-0"/></para>
-
-
-<tip role="ora">
-<para>
-<indexterm id="ch07-idx-956514-0"><primary>resources for further information</primary><secondary>printers, debuggiing</secondary></indexterm>
-<indexterm id="ch07-idx-956514-1"><primary>printing</primary><secondary>resources for information on debugging</secondary></indexterm>There is more information on debugging printers in the Samba documentation (<filename>Printing.txt</filename>). In addition, the Unix print systems are covered in detail in AEleen Frisch's <emphasis>Essential Systems Administration</emphasis> (published by O'Reilly).</para>
-
-</tip>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.1.6" id="ch07-SECT-1.6">
-<title>Setting Up and Testing a Windows Client</title>
-
-
-<para>
-<indexterm id="ch07-idx-956392-0"><primary>printing</primary><secondary>Windows client printers</secondary><tertiary>setting up and testing</tertiary></indexterm>
-<indexterm id="ch07-idx-956392-1"><primary>Windows clients</primary><secondary>printers for, setting up and testing</secondary></indexterm>Now that Samba is offering a workable printer, you need to set it up on a Windows client. Look at the Samba server in the Network Neighborhood. It should now show each of the printers that are available. For example, in <link linkend="ch07-35075">Figure 7.1</link>, we saw a printer called <literal>lp</literal>.</para>
-
-
-<para>Next, you need to have the Windows client recognize the printer. Double-click on the printer icon to get started. If you try to select an uninstalled printer (as you just did), Windows will ask you if it should help configure it for the Windows system. Respond "Yes," which will open the Printer Wizard.</para>
-
-
-<para>The first thing the wizard will ask is whether you need to print from DOS. Let's assume you don't, so choose No and press the Next button to get to the manufacturer/model window as shown in <link linkend="ch07-60084">Figure 7.2</link>.</para>
-
-
-<figure label="7.2" id="ch07-60084">
-<title>A printer in the Network Neighborhood</title>
-
-<graphic width="502" depth="128" fileref="figs/sam.0702.gif"></graphic>
-</figure>
-
-<para>In this dialog box, you should see a large list of manufacturers and models for almost every printer imaginable. If you don't see your printer on the list, but you know it's a PostScript printer, select Apple as the manufacturer and Apple LaserWriter as the model. This will give you the most basic Postscript printer setup, and arguably one of the most reliable. If you already have any Postscript printers attached, you will be asked about replacing or reusing the existing driver. Be aware that if you replace it with a new one, you may make your other printers fail. Therefore, we recommend you keep using your existing printer drivers as long as they're working properly.</para>
-
-
-<para>Following that, the Printer Wizard will ask you to name the printer. <link linkend="ch07-69466">Figure 7.3</link> shows this example, where the name has defaulted to our second laserwriter. Here, you rename it from Apple Laserwriter (Copy 2) to "ps on Samba server," so you know where to look for the printouts. In reality, you can name the printer anything you want.</para>
-
-
-<figure label="7.3" id="ch07-69466">
-<title>Printer manufacturers and models</title>
-
-<graphic width="502" depth="296" fileref="figs/sam.0703.gif"></graphic>
-</figure>
-
-<para>Finally, the Printing Wizard asks if it should print a test page. Click on Yes, and you should be presented with the dialog in <link linkend="ch07-43374">Figure 7.4</link>.</para>
-
-
-<figure label="7.4" id="ch07-43374">
-<title>Printing successfully completed</title>
-
-<graphic width="502" depth="232" fileref="figs/sam.0704.gif"></graphic>
-</figure>
-
-<para>If the test printing was unsuccessful, press the No button in <link linkend="ch07-43374">Figure 7.4</link> and the Printing Wizard will walk you through some debugging steps for the client side of the process. If the test printing does work, congratulations! The remote printer will now be available to all your PC applications through the File and Print menu items.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.1.7" id="ch07-30008">
-<title>Automatically Setting Up Printer Drivers</title>
-
-
-<para>
-<indexterm id="ch07-idx-956393-0" class="startofrange"><primary>printing</primary><secondary>drivers for, setting up</secondary></indexterm>The previous section described how to manually configure a printer driver for your Windows system. As a system administrator, however, you can't always guarantee that users can perform such a process without making mistakes. Luckily, however, you can ask Samba to automatically set up the printer drivers for a specific printer.</para>
-
-
-<para>Samba has three options that can be used to automatically set up printer drivers for clients who are connecting for the first time. These options are <literal>printer</literal> <literal>driver</literal>, <literal>printer</literal> <literal>driver</literal> <literal>file</literal>, and <literal>printer</literal> <literal>driver</literal> <literal>location</literal>. This section explains how to use these options to allow users to skip over the Manufacturer dialog in the Add Printer Wizard above.</para>
-
-
-<tip role="ora">
-<para>For more information on how to do this, see the <filename>PRINTER_DRIVER.TXT</filename> file in the Samba distribution documentation.</para>
-
-</tip>
-
-<para>There are four major steps:</para>
-
-
-<orderedlist>
-<listitem><para>Install the drivers for the printer on a Windows client (the printer need not be attached).</para></listitem>
-<listitem><para>Create a printer definition file from the information on a Windows machine.</para></listitem>
-<listitem><para>Create a <literal>PRINTER$</literal> share where the resulting driver files can be placed.</para></listitem>
-<listitem><para>Modify the Samba configuration file accordingly.</para></listitem>
-</orderedlist>
-
-<para>Let's go over each of the four steps in greater detail.</para>
-
-
-<sect3 role="" label="7.1.7.1" id="ch07-SECT-1.7.1">
-<title>Install the drivers on a windows client</title>
-
-
-<para>Use <indexterm id="ch07-idx-956517-0"><primary>Windows 95/98</primary><secondary>printer drivers, installing</secondary></indexterm>Windows 95/98 for this step. It doesn't matter which client you choose, as long as it has the ability to load the appropriate drivers for the printer. In fact, you don't even need to have the printer attached to the machine. All you're interested in here is getting the appropriate driver files into the Windows directory. First, go to the Printers window of My Computer and double-click on the Add Printer icon, as shown in <link linkend="ch07-52397">Figure 7.5</link>.</para>
-
-
-<figure label="7.5" id="ch07-52397">
-<title>The Printers window</title>
-
-<graphic width="502" depth="223" fileref="figs/sam.0705.gif"></graphic>
-</figure>
-
-<para>At this point, you can follow the Add Printer Wizard dialogs through to select the manufacturer and model of the printer in question. If it asks you if you want to print from MS-DOS, answer No. Windows should load the appropriate driver resources from its CD-ROM and ask you if you want to print a test page. Again, respond No and close the Add Printer Wizard dialog.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.1.7.2" id="ch07-SECT-1.7.2">
-<title>Create a printer definition file</title>
-
-
-<para>You can create a <indexterm id="ch07-idx-956518-0"><primary>printing</primary><secondary>printer definition file</secondary></indexterm>printer definition file by using the <filename>make_ printerdef</filename> script in the <filename>/usr/local/samba/bin</filename> directory. In order to use this script, you need to copy over the following four files from a Windows client:<footnote label="1" id="ch07-pgfId-951615">
-
-
-<para>Older Windows 95 clients may have only the first two files.</para>
-
-
-</footnote></para>
-
-
-<simplelist>
-
-<member><emphasis>C:\WINDOWS\INF\MSPRINT.INF</emphasis></member>
-
-<member><emphasis>C:\WINDOWS\INF\MSPRINT2.INF</emphasis></member>
-
-<member><emphasis>C:\WINDOWS\INF\MSPRINT3.INF</emphasis></member>
-
-<member><emphasis>C:\WINDOWS\INF\MSPRINT4.INF</emphasis></member>
-
-</simplelist>
-
-
-<para>Once you have the four files, you can create a printer definition file using the appropriate printer driver and its .INF file. If the printer driver starts with the letters A-K, use either the <emphasis>MSPRINT.INF</emphasis> file or the <emphasis>MSPRINT3.INF</emphasis> file. If it begins with the letters L-Z, use the <emphasis>MSPRINT2.INF</emphasis> file or the <emphasis>MSPRINT4.INF</emphasis> file. You may need to <emphasis>grep</emphasis> through each of the files to see where your specific driver is. For the following example, we have located our driver in <emphasis>MSPRINT3.INF</emphasis> and created a printer definition file for a HP DeskJet 560C printer:</para>
-
-
-<programlisting>$grep "HP DeskJet 560C Printer" MSPRINT.INF MSPRINT3.INF
-MSPRINT3.INF: "HP DeskJet 560C Printer"=DESKJETC.DRV,HP_DeskJet_ ...
-
-$make_printerdef MSPRINT3.INF "HP DeskJet 560C Printer" >printers.def
-FOUND:DESKJETC.DRV
-End of section found
-CopyFiles: DESKJETC,COLOR_DESKJETC
-Datasection: (null)
-Datafile: DESKJETC.DRV
-Driverfile: DESKJETC.DRV
-Helpfile: HPVDJC.HLP
-LanguageMonitor: (null)
-
-Copy the following files to your printer$ share location:
-DESKJETC.DRV
-HPVCM.HPM
-HPVIOL.DLL
-HPVMON.DLL
-HPVRES.DLL
-HPCOLOR.DLL
-HPVUI.DLL
-HPVDJCC.HLP
-color\HPDESK.ICM</programlisting>
-
-
-<para>Note the files that the script asks you to copy. You'll need those for the next step.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.1.7.3" id="ch07-SECT-1.7.3">
-<title>Create a PRINTER$ share</title>
-
-
-<para>
-<indexterm id="ch07-idx-956525-0"><primary>PRINTER$ share, creating</primary></indexterm>This part is relatively easy. Create a share called <literal>[PRINTER$]</literal> in your <filename>smb.conf</filename> that points to an empty directory on the Samba server. Once that is done, copy over the files that the <filename>make_ printerdef</filename> script requested of you into the location of the <literal>path</literal> configuration option for the <literal>[PRINTER$]</literal> share. For example, you can put the following in your configuration file:</para>
-
-
-<programlisting>[PRINTER$]
- path = /usr/local/samba/print
- read only = yes
- browsable = no
- guest ok = yes</programlisting>
-
-
-<para>The files requested by the <filename>make_ printerdef</filename> script are typically located in the <emphasis>C:\WINDOWS\SYSTEM</emphasis> directory, although you can use the following commands to find out exactly where they are:</para>
-
-
-<programlisting>cd C:\WINDOWS
-dir <replaceable>filename</replaceable> /s</programlisting>
-
-
-<para>In this case, each of the files needs to be copied to the <filename>/usr/local/samba/print</filename> directory on the Samba server. In addition, copy the <filename>printers.def</filename> file that you created over to that share as well. Once you've done that, you're almost ready to go.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.1.7.4" id="ch07-SECT-1.7.4">
-<title>Modify the Samba configuration file</title>
-
-
-<para><filename></filename>
-<indexterm id="ch07-idx-956532-0"><primary>smb.conf (Samba configuration) file</primary><secondary>modifying for printer drivers</secondary></indexterm>The last step is to modify the Samba configuration file by adding the following three options:</para>
-
-
-<itemizedlist>
-<listitem><para><literal>printer</literal> <literal>driver</literal></para></listitem>
-<listitem><para><literal>printer</literal> <literal>driver</literal> <literal>file</literal></para></listitem>
-<listitem><para><literal>printer</literal> <literal>driver</literal> <literal>location</literal></para></listitem>
-</itemizedlist>
-
-<para>The <literal>printer</literal> <literal>driver</literal> <literal>file</literal> is a global option that points to the <filename>printers.def</filename> file; place that option in your <literal>[global]</literal> section. The other options should be set in the printer share for which you wish to automatically configure the drivers. The value for <literal>printer</literal> <literal>driver</literal> should match the string that shows up in the Printer Wizard on the Windows system. The value of the <literal>printer</literal> <literal>driver</literal> <literal>location</literal> is the pathname of the PRINTER$ share you set up, not the Unix pathname on the server. Thus, you could use the following:</para>
-
-
-<programlisting>[global]
- printer driver file = /usr/local/samba/print/printers.def
-[hpdeskjet]
- path = /var/spool/samba/printers
- printable = yes
-
- printer driver = HP DeskJet 560C Printer
- printer driver location = \\%L\PRINTER$</programlisting>
-
-
-<para>Now you're ready to test it out. At this point, remove the Windows printer that you "set up" in the first step from the list of printers in the Printers window of My Computer. If Samba asks you to delete unneeded files, do so. These files will be replaced shortly on the client, as they now exist on the Samba server.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.1.7.5" id="ch07-SECT-1.7.5">
-<title>Testing the configuration</title>
-
-
-<para>Restart the Samba daemons and look for the <literal>[hpdeskjet]</literal> share under the machine name in the Network Neighborhood. At this point, if you click on the printer icon, you should begin the printer setup process and come to the dialog shown in <link linkend="ch07-60108">Figure 7.6</link>.</para>
-
-
-<para>This is different from the dialog you saw earlier when setting up a printer. Essentially, the dialog is asking if you wish to accept the driver that is "already installed"—in other words, offered by Samba. Go ahead and keep the existing driver, and press the Next button. At this point, you can give the printer a name and print out a test page. If it works, the setup should be complete. You should be able to repeat the process now from any Windows<indexterm id="ch07-idx-956413-0" class="endofrange" startref="ch07-idx-956393-0"/> client. <indexterm id="ch07-idx-956407-0" class="endofrange" startref="ch07-idx-956360-0"/></para>
-
-
-<figure label="7.6" id="ch07-60108">
-<title>Automatically configuring the printer driver</title>
-
-<graphic width="502" depth="296" fileref="figs/sam.0706.gif"></graphic>
-</figure>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="7.2" id="ch07-31526">
-<title>Printing to Windows Client Printers</title>
-
-
-<para>
-<indexterm id="ch07-idx-956368-0" class="startofrange"><primary>printing</primary><secondary>Windows client printers</secondary><tertiary>printing to</tertiary></indexterm>If you have printers connected to clients running Windows 95/98 or NT 4.0, those printers can also be accessed from Samba. Samba comes equipped with a tool called <emphasis>smbprint</emphasis>
-<indexterm id="ch07-idx-956539-0"><primary>smbprint tool, spooling print jobs</primary></indexterm>
-<indexterm id="ch07-idx-956539-1"><primary>printing</primary><secondary>print jobs</secondary><tertiary>spooling with smbprint tool</tertiary></indexterm> that can be used to spool print jobs to Windows-based printers. In order to use this, however, you need to set up the printer as a shared resource on the client machine. If you haven't already done this, you can reset this from the Printers window, reached from the Start button, as shown in <link linkend="ch07-32814">Figure 7.7</link>.</para>
-
-
-<figure label="7.7" id="ch07-32814">
-<title>The Printers window</title>
-
-<graphic width="502" depth="273" fileref="figs/sam.0707.gif"></graphic>
-</figure>
-
-<para>Select a printer that's locally connected (for example, ours is the Canon printer), press the right mouse button to bring up a menu, and select Sharing. This will give you the Sharing tab of the Printer Properties frame, as shown in <link linkend="ch07-92021">Figure 7.8</link>. If you want it available to everybody on your LAN as the Windows guest user, enter a blank password.</para>
-
-
-<figure label="7.8" id="ch07-92021">
-<title>The Sharing tab of the printer</title>
-
-<graphic width="502" depth="273" fileref="figs/sam.0708.gif"></graphic>
-</figure>
-
-<para>Once you've got this working, you can add your printer to the list of standard printers and Samba can make it available to all the other PCs in the workgroup. To make installation on Unix easier, the Samba distribution provides two sample scripts: <filename>smbprint</filename> and <filename>smbprint.sysv</filename>. The first works with BSD-style printers; the second is designed for System V printers.</para>
-
-
-<sect2 role="" label="7.2.1" id="ch07-SECT-2.0.1">
-<title>BSD printers</title>
-
-
-<para>
-<indexterm id="ch07-idx-956540-0"><primary>printers</primary><secondary>BSD</secondary></indexterm>There are two steps you need to have a BSD Unix recognize a remote printer:</para>
-
-
-<orderedlist>
-<listitem><para>Place an entry for the printer in the <filename>/etc/printcap</filename> file (or equivalent).</para></listitem>
-<listitem><para>Place a configuration file in the <filename>/var/spool</filename> directory for the printer.</para></listitem>
-</orderedlist>
-
-<para>First, edit your <filename>/etc/printcap</filename> file and add an entry for the remote printer. Note that the input filter (<literal>if</literal>) entry needs to point to the <emphasis>smbprint</emphasis> program if the machine is on Windows 95/98. The following set of lines will accomplish on a Linux machine, for example:</para>
-
-
-<programlisting>laserjet:\
- :sd=/var/spool/lpd/laser:\ <replaceable># spool directory</replaceable>
- :mx#0:\ <replaceable># maximum file size (none)</replaceable>
- :sh:\ <replaceable># surpress burst header (no)</replaceable>
- :if=/usr/local/samba/bin/smbprint: <replaceable># text filter</replaceable></programlisting>
-
-
-<para>After that, you need to create a configuration file in the spool directory that you specified with the <literal>sd</literal> parameter above. (You may need to create that directory.) The file must have the name <emphasis>.config</emphasis> and should contain the following information:</para>
-
-
-<itemizedlist>
-<listitem><para>The NetBIOS name of the Windows machine with the printer</para></listitem>
-<listitem><para>The service name that represents the printer</para></listitem>
-<listitem><para>The password used to access that service</para></listitem>
-</itemizedlist>
-
-<para>The last two parameters were set up in the Sharing dialog for the requested resource on the Windows machine. In this case, the <emphasis>.config</emphasis> file would have three lines:</para>
-
-
-<programlisting>server = phoenix
-service = CANON
-password = ""</programlisting>
-
-
-<para>After you've done that, reset the Samba server machine and try printing to it using any standard Unix program.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.2.2" id="ch07-SECT-2.0.2">
-<title>System V printers</title>
-
-
-<para>
-<indexterm id="ch07-idx-956541-0"><primary>printers</primary><secondary>System V</secondary></indexterm>Sending print jobs from a System V Unix system is a little easier. Here, you need to get obtain the <filename>smbprint.sysv</filename> script in the <filename>/usr/local/samba/examples/printing</filename> directory and do the following:</para>
-
-
-<orderedlist>
-<listitem><para>Change the <literal>server</literal>, <literal>service</literal>, and <literal>password</literal> parameters in the script to match the NetBIOS machine, its shared printer service, and its password, respectively. For example, the following entries would be correct for the service in the previous example:</para>
-
-
-<programlisting>server = phoenix
-service = CANON
-password = ""</programlisting></listitem>
-
-<listitem><para>Run the following commands, which create a reference for the printer in the printer capabilities file. Note that the new Unix printer entry <literal>canon_ printer</literal> is named:</para>
-
-
-<programlisting># lpadmin -p canon_printer -v /dev/null -i./smbprint.sysv
-# enable canon_printer
-# accept canon_printer</programlisting></listitem>
-</orderedlist>
-
-<para>After you've done that, restart the Samba daemons and try printing to it using any standard Unix program. You should now be able to send data to a printer on a Windows client across the network.</para>
-</sect2>
-
-
-
-
-<sect2 role="" label="7.2.3" id="ch07-SECT-2.1">
-<title>Samba Printing Options</title>
-
-
-<para>
-<indexterm id="ch07-idx-956419-0" class="startofrange"><primary>printing</primary><secondary>options for</secondary></indexterm><link linkend="ch07-19361">Table 7.2</link> summarizes the Samba printing options.</para>
-
-
-<table label="7.2" id="ch07-19361">
-<title>Printing Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>printing</literal></para></entry>
-
-<entry colname="col2"><para><literal>bsd</literal>, <literal>sysv</literal>, <literal>hpux</literal>, <literal>aix</literal>, <literal>qnx</literal>, <literal>plp</literal>, <literal>softq</literal>, or <literal>lprng</literal></para></entry>
-
-<entry colname="col3"><para>Sets the print system type for your Unix system.</para></entry>
-
-<entry colname="col4"><para>System dependent</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>printable (print ok)</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Marks a share as a printing share.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>printer (printer name)</literal></para></entry>
-
-<entry colname="col2"><para>string (Unix printer name)</para></entry>
-
-<entry colname="col3"><para>Sets the name of the printer to be shown to clients.</para></entry>
-
-<entry colname="col4"><para>System dependent</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>printer driver</literal></para></entry>
-
-<entry colname="col2"><para>string (printer driver name)</para></entry>
-
-<entry colname="col3"><para>Sets the driver name that should be used by the client to send data to the printer.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>printer driver file</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Sets the name of the printer driver file.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>printer driver location</literal></para></entry>
-
-<entry colname="col2"><para>string (network pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the pathname of the share for the printer driver file.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lpq cache time</literal></para></entry>
-
-<entry colname="col2"><para>numeric (time in seconds)</para></entry>
-
-<entry colname="col3"><para>Sets the amount of time in seconds that Samba will cache the lpq status.</para></entry>
-
-<entry colname="col4"><para><literal>10</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>postscript</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Treats all print jobs sent as postscript by prepending <literal>%!</literal> at the beginning of each file.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>load printers</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Automatically loads each of the printers in the <emphasis>printcap</emphasis> file as printing shares.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>print command</literal></para></entry>
-
-<entry colname="col2"><para>string (shell command)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix command to perform printing.</para></entry>
-
-<entry colname="col4"><para>See below</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lpq command</literal></para></entry>
-
-<entry colname="col2"><para>string (shell command)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix command to return the status of the printing queue.</para></entry>
-
-<entry colname="col4"><para>See below</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lprm command</literal></para></entry>
-
-<entry colname="col2"><para>string (shell command)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix command to remove a job from the printing queue.</para></entry>
-
-<entry colname="col4"><para>See below</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lppause command</literal></para></entry>
-
-<entry colname="col2"><para>string (shell command)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix command to pause a job on the printing queue.</para></entry>
-
-<entry colname="col4"><para>See below</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lpresume command</literal></para></entry>
-
-<entry colname="col2"><para>string (shell command)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix command to resume a paused job on the printing queue.</para></entry>
-
-<entry colname="col4"><para>See below</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>printcap name</literal></para>
-
-<para><literal>(printcap)</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Specifies the location of the printer capabilities file.</para></entry>
-
-<entry colname="col4"><para>System dependent</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>min print space</literal></para></entry>
-
-<entry colname="col2"><para>numeric (size in kilobytes)</para></entry>
-
-<entry colname="col3"><para>Sets the minimum amount of disk free space that must be present to print.</para></entry>
-
-<entry colname="col4"><para><literal>0</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>queuepause command</literal></para></entry>
-
-<entry colname="col2"><para>string (shell command)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix command to pause a queue.</para></entry>
-
-<entry colname="col4"><para>See below</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>queueresume command</literal></para></entry>
-
-<entry colname="col2"><para>string (shell command)</para></entry>
-
-<entry colname="col3"><para>Sets the Unix command to resume a queue.</para></entry>
-
-<entry colname="col4"><para>See below</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="7.2.3.1" id="ch07-SECT-2.1.1">
-<title>printing</title>
-
-
-<para>The <literal>printing</literal>
-<indexterm id="ch07-idx-958423-0"><primary>printing configuration option</primary></indexterm> configuration option tells Samba a little about your Unix printing system, in this case which printing parser to use. With Unix, there are several different families of commands to control printing and print statusing. Samba supports seven different types, as shown in <link linkend="ch07-28758">Table 7.3</link>.</para>
-
-
-<table label="7.3" id="ch07-28758">
-<title>Printing Types </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Variable</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>BSD</para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch07-idx-956545-0"><primary>printing</primary><secondary>types</secondary></indexterm>Berkeley Unix system</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>SYSV</para></entry>
-
-<entry colname="col2"><para>System V</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>AIX</para></entry>
-
-<entry colname="col2"><para>AIX Operating System (IBM)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>HPUX</para></entry>
-
-<entry colname="col2"><para>Hewlett-Packard Unix</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>QNX</para></entry>
-
-<entry colname="col2"><para>QNX Realtime Operating System (QNX)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>LPRNG</para></entry>
-
-<entry colname="col2"><para>LPR Next Generation (Powell)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>SOFTQ</para></entry>
-
-<entry colname="col2"><para>SOFTQ system</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>PLP</para></entry>
-
-<entry colname="col2"><para>Portable Line Printer (Powell)</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>The value for this optio.n will be one of these seven options. For example:</para>
-
-
-<programlisting>printing = SYSV</programlisting>
-
-
-<para>The default value of this option is system dependent and is configured when Samba is first compiled. For most systems, the <filename>configure</filename> script will automatically detect the printing system to be used and configure it properly in the Samba makefile. However, if your system is a PLP, LPRNG, or QNX printing system, you will need to explicitly specify this in the makefile or the printing share.</para>
-
-
-<para>The most common system types are BSD and SYSV. Each of the printers on a BSD Unix server are described in the printer capabilities file—normally <filename>/etc/printcap</filename>.</para>
-
-
-<para>Setting the <literal>printing</literal> configuration option automatically sets at least three other printing options for the service in question: <literal>print</literal> <literal>command</literal>, <literal>lpq</literal> <literal>command</literal>, and <literal>lprm</literal> <literal>command</literal>. If you are running Samba on a system that doesn't support any of these printing styles, simply set the commands for each of these manually.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.2" id="ch07-SECT-2.1.2">
-<title>printable</title>
-
-
-<para>The <indexterm id="ch07-idx-958426-0"><primary>printable option</primary></indexterm>printable option must be set to <literal>yes</literal> in order to flag a share as a printing service. If this option is not set, the share will be treated as a disk share instead. You can set the option as follows:</para>
-
-
-<programlisting>[printer1]
- printable = yes</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.3" id="ch07-SECT-2.1.3">
-<title>printer</title>
-
-
-<para>
-<indexterm id="ch07-idx-957248-0" class="startofrange"><primary>printers</primary><secondary>option for</secondary></indexterm>The <indexterm id="ch07-idx-958427-0"><primary>printer option</primary></indexterm>option, sometimes called <literal>printer</literal> <literal>name</literal>, specifies the name of the printer on the server to which the share points. This option has no default and should be set explicitly in the configuration file, even though Unix systems themselves often recognize a default name such as <literal>lp</literal> for a printer. For example:</para>
-
-
-<programlisting>[deskjet]
- printer = hpdkjet1</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.4" id="ch07-SECT-2.1.4">
-<title>printer driver</title>
-
-
-<para>The <literal>printer</literal>
-<indexterm id="ch07-idx-958428-0"><primary>printer driver option</primary></indexterm> <literal>driver</literal> option sets the string that Samba uses to tell Windows what the printer is. If this option is set correctly, the Windows Printer Wizard will already know what the printer is, making installation easier for end users by giving them one less dialog to worry about. The string given should match the string that shows up in the Printer Wizard, as shown in <link linkend="ch07-46183">Figure 7.9</link>. For example, an Apple LaserWriter typically uses <literal>Apple</literal> <literal>LaserWriter</literal>; a Hewlett Packard Deskjet 560C uses <literal>HP</literal> <literal>DeskJet</literal> <literal>560C</literal> <literal>Printer</literal>.</para>
-
-
-<figure label="7.9" id="ch07-46183">
-<title>The Add Printer Wizard dialog box in Windows 98</title>
-
-<graphic width="502" depth="296" fileref="figs/sam.0709.gif"></graphic>
-</figure>
-
-<para>Automatically configuring printer drivers with Samba is explained in greater detail in <link linkend="ch07-30008">Section 7.1.7</link> earlier in this chapter.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.5" id="ch07-SECT-2.1.5">
-<indexterm id="ch07-idx-958429-0"><primary>printer driver file option</primary></indexterm>
-<title>
-printer driver file</title>
-
-
-<para>This global option gives the location of the Windows 95/98 printer driver definition file, which is needed to give printer drivers to clients using a Samba printer. The default value of this option is <filename>/usr/local/samba/lib/printers.def</filename>. You can override this default as shown below:</para>
-
-
-<programlisting>[deskjet]
- printer driver file = /var/printers/printers.def</programlisting>
-
-
-<para>This option is explained in greater detail in <link linkend="ch07-30008">Section 7.1.7</link> earlier in this chapter.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.6" id="ch07-SECT-2.1.6">
-<indexterm id="ch07-idx-958432-0"><primary>printer driver location option</primary></indexterm>
-<title>
-printer driver location</title>
-
-
-<para>This option specifies a specific share that contains Windows 95 and 98 printer driver and definition files. There is no default parameter for this value. You can specify the location as a network pathname. A frequent approach is to use a share on your own machine, as shown here:</para>
-
-
-<programlisting>[deskjet]
- printer driver location = \\%L\PRINTER$</programlisting>
-
-
-<para>This option is also explained in greater detail in <link linkend="ch07-30008">Section 7.1.7</link> earlier in this chapter.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.7" id="ch07-SECT-2.1.7">
-<indexterm id="ch07-idx-958433-0"><primary>lpq cache time option</primary></indexterm>
-<title>
-lpq cache time</title>
-
-
-<para>
-<indexterm id="ch07-idx-956564-0"><primary>cache time (printers), option for</primary></indexterm>The global <literal>lpq</literal> <literal>cache</literal> <literal>time</literal> option allows you to set the number of seconds that Samba will remember the current printer status. After this time elapses, Samba will issue an <emphasis>lpq</emphasis> command (or whatever command you specify with the <literal>lpq</literal> <literal>command</literal> option) to get a more up-to-date status. This defaults to 10 seconds, but can be increased if your <literal>lpq</literal> <literal>command</literal> takes an unusually long time to run or you have lots of clients. The following example resets the time to 30 seconds:</para>
-
-
-<programlisting>[deskjet]
- lpq cache time = 30</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.8" id="ch07-SECT-2.1.8">
-<title>postscript</title>
-
-
-<para>The<indexterm id="ch07-idx-958438-0"><primary>postscript option</primary></indexterm> <literal>postscript</literal> option forces the printer to treat all data sent to it as Postscript. It does this by prepending the characters <literal>%!</literal> at the beginning of the first line of each job. It is normally used with PCs that insert a <literal>^D</literal> (control-D or "end-of-file mark) in front of the first line of a PostScript file. It will not, obviously, turn a non-PostScript printer into a PostScript one. The default value of this options is <literal>no</literal>. You can override it as follows:<indexterm id="ch07-idx-957258-0" class="endofrange" startref="ch07-idx-957248-0"/></para>
-
-
-<programlisting>[deskjet]
- postscript = yes</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.9" id="ch07-SECT-2.1.9">
-<indexterm id="ch07-idx-958439-0"><primary>print command option</primary></indexterm>
-<indexterm id="ch07-idx-958439-1"><primary>lpq command option</primary></indexterm>
-<indexterm id="ch07-idx-958439-2"><primary>lprm command option</primary></indexterm>
-<indexterm id="ch07-idx-958439-3"><primary>lppause command option</primary></indexterm>
-<indexterm id="ch07-idx-958439-4"><primary>lpresume command option</primary></indexterm>
-<title>
-
-
-
-
-print command, lpq command, lprm command, lppause command, lpresume command</title>
-
-
-<para>
-<indexterm id="ch07-idx-956566-0"><primary>Unix</primary><secondary>options</secondary><tertiary sortas="print commands">for print commands</tertiary></indexterm>These options tell Samba which Unix commands used to control and send data to the printer. The Unix commands involved are: <emphasis>lpr</emphasis> (send to Line PRinter), <emphasis>lpq</emphasis> (List Printer Queue), <emphasis>lprm</emphasis> (Line printer ReMove), and optionally <emphasis>lppause</emphasis> and <emphasis>lpresume</emphasis>. Samba provides an option named after each of these commands, in case you need to override any of the system defaults. For example, consider:</para>
-
-
-<programlisting>lpq command = /usr/ucb/lpq %p</programlisting>
-
-
-<para>This would set the <literal>lpq command</literal> to use <filename>/usr/ucb/lpq</filename>. Similarly:</para>
-
-
-<programlisting>lprm command = /usr/local/lprm -P%p %j</programlisting>
-
-
-<para>would set the Samba printer remove command to <filename>/usr/local/lprm</filename>, and provide it the print job number using the <literal>%j</literal> variable.</para>
-
-
-<para>The default values for each of these options are dependent on the value of the <literal>printing</literal> option. <link linkend="ch07-82964">Table 7.4</link> shows the default commands for each of the printing options. The most popular printing system is BSD.</para>
-
-
-<table label="7.4" id="ch07-82964">
-<title>Default Commands for Various Printing Commands </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>BSD, AIX, PLP, LPRNG</para></entry>
-
-<entry colname="col3"><para>SYSV, HPUX</para></entry>
-
-<entry colname="col4"><para>QNX</para></entry>
-
-<entry colname="col5"><para>SOFTQ</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>print command</literal></para></entry>
-
-<entry colname="col2"><para><literal>lpr -r -P%p %s</literal>
-<indexterm id="ch07-idx-958518-0"><primary>printing</primary><secondary>commands</secondary><tertiary>default commands for</tertiary></indexterm></para></entry>
-
-<entry colname="col3"><para><literal>lp -c -d%p %s; rm %s</literal></para></entry>
-
-<entry colname="col4"><para><literal>lp -r -P%p %s</literal></para></entry>
-
-<entry colname="col5"><para><literal>lp -d%p -s %s; rm %s</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lpq command</literal></para></entry>
-
-<entry colname="col2"><para><literal>lpq -P%p</literal></para></entry>
-
-<entry colname="col3"><para><literal>lpstat -o%p</literal></para></entry>
-
-<entry colname="col4"><para><literal>lpq -P%p</literal></para></entry>
-
-<entry colname="col5"><para><literal>lpstat -o%p</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lprm command</literal></para></entry>
-
-<entry colname="col2"><para><literal>lprm -P%p %j</literal></para></entry>
-
-<entry colname="col3"><para><literal>cancel %p-%j</literal></para></entry>
-
-<entry colname="col4"><para><literal>cancel %p-%j</literal></para></entry>
-
-<entry colname="col5"><para><literal>cancel %p-%j</literal></para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lppause command</literal></para></entry>
-
-<entry colname="col2"><para><literal>lp -i %p-%j -H hold </literal></para>
-
-<para>(SYSV only)</para></entry>
-
-<entry colname="col3"><para>None</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>None</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>lpresume command</literal></para></entry>
-
-<entry colname="col2"><para><literal>lp -i %p-%j -H resume</literal></para>
-
-<para>(SYSV only)</para></entry>
-
-<entry colname="col3"><para>None</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para><literal>qstat -s -j%j -r</literal></para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>It is typically not necessary to reset these options in Samba, with the possible exception of <literal>print</literal> <literal>command</literal>. This option may need to be explicitly set if your printing system doesn't have a <literal>-r</literal> (remove after printing) option on the printing command. For example:</para>
-
-
-<programlisting>/usr/local/lpr -P%p %s; /bin/rm %s</programlisting>
-
-
-<para>With a bit of judicious programming, these <filename>smb.conf</filename> options can also used for debugging:</para>
-
-
-<programlisting>print command = cat %s >>/tmp/printlog; lpr -r -P%p %s</programlisting>
-
-
-<para>For example, this configuration can verify that files are actually being delivered to the Samba server. If they are, their contents will show up in the <filename>/tmp/printlog</filename> file.</para>
-
-
-<para>After BSD, the next most popular kind of printing system is SYSV (or System V) printing, plus some SYSV variants for IBM's AIX and Hewlett-Packard's HP-UX. These system do not have an <filename>/etc/printcap</filename> file. Instead, the <literal>printcap</literal> <literal>file</literal> option can be set to an appropriate <emphasis>lpstat</emphasis> command for the system. This tells Samba to get a list of printers from the <emphasis>lpstat</emphasis> command. Alternatively, you can set the global configuration option <literal>printcap</literal> <literal>name</literal> to the name of a dummy <filename>printcap</filename> file you provide. In the latter case, the file must contain a series of lines such as:</para>
-
-
-<programlisting>lp|print1|My Printer 1
-print2|My Printer 2
-print3|My Printer 3</programlisting>
-
-
-<para>Each line names a printer, and provides aliases for it. In this example, the first printer is called <literal>lp</literal>, <literal>print1</literal>, or <literal>My</literal> <literal>Printer</literal> <literal>1</literal>, whichever the user prefers to use. The first name will be used in place of <literal>%p</literal> in any command Samba executes for that printer.</para>
-
-
-<para>Two additional printer types are also supported by Samba: LPRNG (LPR New Generation) and PLP (Public Line Printer). These are public domain and Open Source printing systems, and are used by many sites to overcome problems with vendor-supplied software. In addition, the SOFTQ and QNX realtime operating systems are supported by Samba.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.10" id="ch07-SECT-2.1.10">
-<title>load printers</title>
-
-
-<para>
-<indexterm id="ch07-idx-956568-0"><primary>print shares</primary><secondary>options for</secondary></indexterm>The <literal>load</literal>
-<indexterm id="ch07-idx-958440-0"><primary>load printers option</primary></indexterm> <literal>printers</literal> option tells Samba to create shares for all known printer names and load those shares into the browse list. Samba will create and list a printer share for each printer name in <filename>/etc/printcap</filename> (or system equivalent). For example, if your <filename>printcap</filename> file looks like this:<footnote label="2" id="ch07-pgfId-950654">
-
-
-<para>We have placed annotated comments off to the side in case you've never dealt with this file before.</para>
-
-
-</footnote></para>
-
-
-<programlisting>lp:\
- :sd=/var/spool/lpd/lp:\ <replaceable># spool directory</replaceable>
- :mx#0:\ <replaceable># maximum file size (none)</replaceable>
- :sh:\ <replaceable># surpress burst header (no)</replaceable>
- :lp=/dev/lp1:\ <replaceable># device name for output</replaceable>
- :if=/var/spool/lpd/lp/filter: <replaceable># text filter</replaceable>
-
-laser:\
- :sd=/var/spool/lpd/laser:\ <replaceable># spool directory</replaceable>
- :mx#0:\ <replaceable># maximum file size (none)</replaceable>
- :sh:\ <replaceable># surpress burst header (no)</replaceable>
- :lp=/dev/laser:\ <replaceable># device name for output</replaceable>
- :if=/var/spool/lpd/lp/filter: <replaceable># text filter</replaceable></programlisting>
-
-
-<para>and you specify:</para>
-
-
-<programlisting>load printers = yes</programlisting>
-
-
-<para>the shares <literal>[lp]</literal> and <literal>[laser]</literal> will automatically be created as valid print shares when Samba is started. Both shares will borrow the configuration options specified in the <literal>[printers]</literal> section to configure themselves, and will be available in the browse list for the Samba server.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.11" id="ch07-SECT-2.1.11">
-<title>printcap name</title>
-
-
-<para>If the <literal>printcap</literal>
-<indexterm id="ch07-idx-958442-0"><primary>printcap name option</primary></indexterm> <literal>name</literal> option (also called <literal>printcap</literal>) appears in a printing share, Samba will use the file specified as the system printer capabilities file. This is normally <filename>/etc/printcap</filename>. However, you can reset it to a file consisting of only the printers you want to share over the network. The value must be a fully-qualified filename of a printer capabilities file on the server:</para>
-
-
-<programlisting>[deskjet]
- printcap name = /usr/local/printcap</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.12" id="ch07-SECT-2.1.12">
-<title>min print space</title>
-
-
-<para>The <literal>min</literal>
-<indexterm id="ch07-idx-958443-0"><primary>min print space option</primary></indexterm> <literal>print</literal> <literal>space</literal> option sets the amount of <indexterm id="ch07-idx-956570-0"><primary>spool space, options for</primary></indexterm>spool space that must be available on the disk before printing is allowed. Setting it to zero (the default) turns the check off; setting it to any other number sets the amount of free space in kilobytes required. This option helps avoid having print jobs fill up the remaining disk space on the server, which may cause other processes to fail:</para>
-
-
-<programlisting>[deskjet]
- min print space = 4000</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.13" id="ch07-SECT-2.1.13">
-<indexterm id="ch07-idx-958444-0"><primary>queuepause command option</primary></indexterm>
-<title>
-queuepause command</title>
-
-
-<para>This configuration option specifies a command that tells Samba how to pause a <indexterm id="ch07-idx-956571-0"><primary>print queue, options for</primary></indexterm>print queue entirely, as opposed to a single job on the queue. The default value depends on the printing type chosen. You should not need to alter this option.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.2.3.14" id="ch07-SECT-2.1.14">
-<indexterm id="ch07-idx-958445-0"><primary>queueresume command option</primary></indexterm>
-<title>
-queueresume command</title>
-
-
-<para>This configuration option specifies a command that tells Samba how to resume a paused print queue, as opposed to resuming a single job on the print queue. The default value depends on the printing type chosen. You should not need to alter<indexterm id="ch07-idx-956423-0" class="endofrange" startref="ch07-idx-956419-0"/> this<indexterm id="ch07-idx-956372-0" class="endofrange" startref="ch07-idx-956368-0"/> option.<indexterm id="ch07-idx-956352-0" class="endofrange" startref="ch07-idx-956351-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="7.3" id="ch07-12219">
-<title>Name Resolution with Samba</title>
-
-
-<para>
-<indexterm id="ch07-idx-956353-0" class="startofrange"><primary>name resolution</primary></indexterm>Before NetBIOS Name Servers (NBNS) came about, name resolution worked entirely by broadcast. If you needed a machine's address, you simply <indexterm id="ch07-idx-956574-0"><primary>broadcasting</primary><seealso>browsing; name resolution</seealso></indexterm>broadcast its name across the network and, in theory, the machine itself would reply. This approach is still possible: anyone looking for a machine named <literal>fred</literal> can still broadcast a query and find out if it exists and what its IP address is. (We use this capability to troubleshoot Samba name services with the <literal>nmblookup</literal> command in <link linkend="SAMBA-CH-9">Chapter 9</link>.)</para>
-
-
-<para>As you saw in the first chapter, however, broadcasting—whether it be browsing or name registration and resolution—does not pass easily across multiple subnets. In addition, many broadcasts tend to bog down networks. To solve this problem, Microsoft now provides the <indexterm id="ch07-idx-956577-0"><primary>WINS (Windows Internet Name Service)</primary><secondary>name resolution and</secondary></indexterm>Windows Internet Naming Service (WINS), a cross-subnet NBNS, which Samba supports. With it, an administrator can designate a single machine to act as a WINS server, and can then provide each client that requires name resolution the address of the WINS server. Consequently, name registration and resolution requests can be directed to a single machine from any point on the network, instead of broadcast.</para>
-
-
-<para>WINS and broadcasting are not the only means of name resolution, however. There are actually four mechanisms that can be used with Samba:</para>
-
-
-<itemizedlist>
-<listitem><para>WINS</para></listitem>
-<listitem><para>Broadcasting</para></listitem>
-<listitem><para>Unix <filename>/etc/hosts</filename> or NIS/NIS+ matches</para></listitem>
-<listitem><para><emphasis>LMHOSTS</emphasis> file</para></listitem>
-</itemizedlist>
-
-<para>Samba can use any or all of these name resolution methods in the order that you specify in the Samba configuration file using the <literal>name</literal> <literal>resolve</literal> <literal>order</literal> parameter. However, before delving into configuration options, let's discuss the one that you've probably not encountered before: the <filename>LMHOSTS</filename> file.</para>
-
-
-<sect2 role="" label="7.3.1" id="ch07-SECT-3.1">
-<title>The LMHOSTS File</title>
-
-
-<para><filename>LMHOSTS</filename>
-<indexterm id="ch07-idx-956428-0"><primary>LMHOSTS file</primary></indexterm> is the standard LAN Manager <emphasis>hosts</emphasis> file used to resolve names into IP addresses on the system. It is the NBT equivalent of the <filename>/etc/hosts</filename> file that is standard on all Unix systems. By default, the file is usually stored as <filename>/usr/local/samba/lib/LMHOSTS</filename> and shares a format similar to <filename>/etc/hosts</filename>. For example:</para>
-
-
-<programlisting>192.168.220.100 hydra
-192.168.220.101 phoenix</programlisting>
-
-
-<para>The only difference is that the names on the right side of the entries are NetBIOS names instead of DNS names. Because they are NetBIOS names, you can assign resource types to them as well:</para>
-
-
-<programlisting>192.168.220.100 hydra#20
-192.168.220.100 simple#1b
-192.168.220.101 phoenix#20</programlisting>
-
-
-<para>Here, we've assigned the <literal>hydra</literal> machine to be the primary domain controller of the <literal>SIMPLE</literal> domain, as indicated by the resource type <1B> assigned to the name after <literal>hydra</literal>'s IP address in the second line. The other two are standard workstations.</para>
-
-
-<para>If you wish to place an <emphasis>LMHOSTS</emphasis> file somewhere other than the default location, you will need to notify the <emphasis>nmbd</emphasis> process upon start up, as follows:</para>
-
-
-<programlisting>nmbd -H /etc/samba/lmhosts -D</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.3.2" id="ch07-SECT-3.2">
-<title>Setting Up Samba to Use Another WINS Server</title>
-
-
-<para>
-<indexterm id="ch07-idx-956595-0"><primary>Samba</primary><secondary>WINS server and</secondary></indexterm>
-<indexterm id="ch07-idx-956595-1"><primary>WINS (Windows Internet Name Service) server</primary><secondary>setting up Sambato use</secondary></indexterm>You can set up Samba to use a WINS server somewhere else on the network by simply pointing it to the IP address of the WINS server. This is done with the global <literal>wins</literal> <literal>server</literal> configuration option, as shown here:</para>
-
-
-<programlisting>[global]
- wins server = 192.168.200.122</programlisting>
-
-
-<para>With this option enabled, Samba will direct all WINS requests to the server at 192.168.200.122. Note that because the request is directed at a single machine, we don't have to worry about any of the problems inherent to broadcasting. However, though you have specified an IP address for a WINS server in the configuration file, Samba will not necessarily use the WINS server before other forms of name resolution. The order in which Samba attempts various name-resolution techniques is given with the <literal>name</literal> <literal>resolve</literal> <literal>order</literal> configuration option, which we will discuss shortly.</para>
-
-
-<para>If you have a Samba server on a subnet that still uses broadcasting and the Samba server knows the correct location of a WINS server on another subnet, you can configure the Samba server to forward any name resolution requests with the <literal>wins</literal> <literal>proxy</literal> option:</para>
-
-
-<programlisting>[global]
- wins server = 192.168.200.12
- wins proxy = yes</programlisting>
-
-
-<para>Use this only in situations where the WINS server resides on another subnet. Otherwise, the broadcast will reach the WINS server regardless of any proxying.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.3.3" id="ch07-83429">
-<title>Setting Up Samba as a WINS Server</title>
-
-
-<para>
-<indexterm id="ch07-idx-956600-0"><primary>WINS (Windows Internet Name Service) server</primary><secondary>setting up Samba as</secondary></indexterm>You can set up Samba as a WINS server by setting two global options in the configuration file, as shown below:</para>
-
-
-<programlisting>[global]
- wins support = yes
- name resolve order = wins lmhosts hosts bcast</programlisting>
-
-
-<para>The <literal>wins</literal> <literal>support</literal> option turns Samba into a WINS server. Believe it or not, that's all you need to do! Samba handles the rest of the details behind the scenes, leaving you a relaxed administrator. The <literal>wins</literal> <literal>support=yes</literal> and the <literal>wins</literal> <literal>server</literal> option are mutually exclusive; you cannot simultaneously offer Samba as the WINS server and point to another system as the server.</para>
-
-
-<para>If Samba is acting as a WINS server, you should probably get familiar with the <literal>name</literal> <literal>resolve</literal> <literal>order</literal> option mentioned earlier. This option tells Samba the order of methods in which it tries to resolve a NetBIOS name. It can take up to four values:</para>
-
-
-<variablelist>
-<varlistentry><term>lmhosts</term>
-<listitem><para>Uses a LAN Manager <emphasis>LMHOSTS</emphasis> file</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>hosts</term>
-<listitem><para>Uses the standard name resolution methods of the Unix system, <emphasis>/etc/hosts</emphasis>, DNS, NIS, or a combination (as configured for the system)</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>wins</term>
-<listitem><para>Uses the WINS server</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>bcast</term>
-<listitem><para>Uses a broadcast method</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>The order in which you specify them in the value is the order in which Samba will attempt name resolution when acting as a WINS server. For example, let's look at the value specified previously:</para>
-
-
-<programlisting>name resolve order = wins lmhosts hosts bcast</programlisting>
-
-
-<para>This means that Samba will attempt to use its WINS entries first for name resolution, followed by the LAN Manager <emphasis>LMHOSTS</emphasis> file on its system. Next, the hosts value causes it to use Unix name resolution methods. The word <literal>hosts</literal> may be misleading; it covers not only the <filename>/etc/hosts</filename> file, but also the use of DNS or NIS (as configured on the Unix host). Finally, if those three do not work, it will use a broadcast to try to locate the correct machine.</para>
-
-
-<para>Finally, you can instruct a Samba server that is acting as a WINS server to check with the system's DNS server if a requested host cannot be found in its WINS database. With a typical Linux system, for example, you can find the IP address of the DNS server by searching the <filename>/etc/resolv.conf</filename> file. In it, you might see an entry such as the following:</para>
-
-
-<programlisting>nameserver 127.0.0.1
-nameserver 192.168.200.192</programlisting>
-
-
-<para>This tells us that a DNS server is located at 192.168.220.192. (The 127.0.0.1 is the localhost address and is never a valid DNS server address.)</para>
-
-
-<para>Use the global <literal>dns</literal> <literal>proxy</literal> option to alert Samba to use the configured DNS server:</para>
-
-
-<programlisting>[global]
- wins support = yes
- name resolve order = wins lmhosts hosts bcast
- dns proxy = yes</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="7.3.4" id="ch07-SECT-3.4">
-<title>Name Resolution Configuration Options</title>
-
-
-<para>
-<indexterm id="ch07-idx-956430-0" class="startofrange"><primary>name resolution</primary><secondary>options for</secondary></indexterm>Samba's WINS options are shown in <link linkend="ch07-82331">Table 7.5</link>.</para>
-
-
-<table label="7.5" id="ch07-82331">
-<title>WINS Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>wins support</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, Samba will act as a WINS server.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>wins server</literal></para></entry>
-
-<entry colname="col2"><para>string (IP address or DNS name)</para></entry>
-
-<entry colname="col3"><para>Identifies a WINS server for Samba to use for name registration and resolution.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>wins proxy</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Allows Samba to act as a proxy to a WINS server on another subnet.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>dns proxy</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If set to <literal>yes</literal>, a Samba WINS server will search DNS if it cannot find a name in WINS.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>name resolve order</literal></para></entry>
-
-<entry colname="col2"><para><literal>lmhosts</literal>, <literal>hosts</literal>, <literal>wins</literal>, or <literal>bcast</literal></para></entry>
-
-<entry colname="col3"><para>Specifies an order of the methods used to resolve NetBIOS names.</para></entry>
-
-<entry colname="col4"><para><literal>lmhosts hosts wins bcast</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max ttl</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Specifies the maximum time-to-live in seconds for a requested NetBIOS names.</para></entry>
-
-<entry colname="col4"><para><literal>259200</literal>( 3 days)</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max wins ttl</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Specifies the maximum time-to-live in seconds for NetBIOS names given out by Samba as a WINS server.</para></entry>
-
-<entry colname="col4"><para><literal>518400</literal>(6 days)</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>min wins ttl</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Specifies the minimum time-to-live in seconds for NetBIOS names given out by Samba as a WINS server.</para></entry>
-
-<entry colname="col4"><para><literal>21600</literal>(6 hours)</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect3 role="" label="7.3.4.1" id="ch07-SECT-3.4.1">
-<indexterm id="ch07-idx-958447-0"><primary>wins support option</primary></indexterm>
-<title>
-wins support</title>
-
-
-<para>Samba will provide <indexterm id="ch07-idx-956607-0"><primary>WINS (Windows Internet Name Service)</primary><secondary>options for</secondary></indexterm>WINS name service to all machines in the network if you set the following in the <literal>[global]</literal> section of the <filename>smb.conf</filename> file:</para>
-
-
-<programlisting>[global]
- wins support = yes</programlisting>
-
-
-<para>The default value is <literal>no</literal>, which is typically used to allow another Windows NT server to become a WINS server. If you do enable this option, remember that a Samba WINS server currently cannot exchange data with any backup WINS servers. If activated, this option is mutually exclusive with the <literal>wins</literal> <literal>server</literal> parameter; you cannot set both to <literal>yes</literal> at the same time or Samba will flag an error.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.3.4.2" id="ch07-SECT-3.4.2">
-<indexterm id="ch07-idx-958448-0"><primary>wins server option</primary></indexterm>
-<title>
-wins server</title>
-
-
-<para>Samba will use an existing WINS server on the network if you specify the <literal>wins</literal> <literal>server</literal> global option in your configuration file. The value of this option is either the IP address or DNS name (not NetBIOS name) of the WINS server. For example:</para>
-
-
-<programlisting>[global]
- wins server = 192.168.220.110</programlisting>
-
-
-<para>or:</para>
-
-
-<programlisting>[global]
- wins server = wins.example.com</programlisting>
-
-
-<para>In order for this option to work, the <literal>wins</literal> <literal>support</literal> option must be set to <literal>no</literal> (the default). Otherwise, Samba will report an error. You can specify only one WINS server using this option.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.3.4.3" id="ch07-SECT-3.4.3">
-<indexterm id="ch07-idx-958449-0"><primary>wins proxy option</primary></indexterm>
-<title>
-wins proxy</title>
-
-
-<para>This option allows Samba to act as a proxy to another WINS server, and thus relay name registration and resolution requests from itself to the real WINS server, often outside the current subnet. The WINS server can be indicated through the <literal>wins</literal> <literal>server</literal> option. The proxy will then return the WINS response back to the client. You can enable this option by specifying the following in the <literal>[global]</literal> section:</para>
-
-
-<programlisting>[global]
- wins proxy = yes</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="7.3.4.4" id="ch07-SECT-3.4.4">
-<indexterm id="ch07-idx-958450-0"><primary>dns proxy option</primary></indexterm>
-<title>
-dns proxy</title>
-
-
-<para>If you want the <indexterm id="ch07-idx-956608-0"><primary>DNS (Domain Name System)</primary><secondary>option for</secondary></indexterm>domain name service (DNS) to be used if a name isn't found in WINS, you can set the following option:</para>
-
-
-<programlisting>[global]
- dns proxy = yes</programlisting>
-
-
-<para>This will cause <filename>nmbd</filename> to query for machine names using the server's standard domain name service. You may wish to deactivate this option if you do not have a permanent connection to your DNS server. Despite this option, we recommend using a WINS server. If you don't already have any WINS servers on your network, make one Samba machine a WINS server. Do not, however, make two Samba machines WINS servers (one primary and one backup) as they currently cannot exchange WINS databases.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.3.4.5" id="ch07-SECT-3.4.5">
-<indexterm id="ch07-idx-958451-0"><primary>name resolve order option</primary></indexterm>
-<title>
-name resolve order</title>
-
-
-<para>The global <literal>name</literal> <literal>resolve</literal> <literal>order</literal> option specifies the order of services that Samba will use in attempting name resolution. The default order is to use the <emphasis>LMHOSTS</emphasis> file, followed by standard Unix name resolution methods (some combination of <filename>/etc/hosts</filename>, DNS, and NIS), then query a WINS server, and finally use broadcasting to determine the address of a NetBIOS name. You can override this option by specifying something like the following:</para>
-
-
-<programlisting>[global]
- name resolve order = lmhosts wins hosts bcast</programlisting>
-
-
-<para>This causes resolution to use the <emphasis>LMHOSTS</emphasis> file first, followed by a query to a WINS server, the system password file, and finally broadcasting. You need not use all four options if you don't want to. This option is covered in more detail in <link linkend="ch07-83429">Section 7.3.3</link> earlier in this chapter.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.3.4.6" id="ch07-SECT-3.4.6">
-<indexterm id="ch07-idx-958452-0"><primary>max ttl option</primary></indexterm>
-<title>
-max ttl</title>
-
-
-<para>This option gives the maximum t<indexterm id="ch07-idx-956610-0"><primary>TTL (time to live), options for</primary></indexterm>
-<indexterm id="ch07-idx-956610-1"><primary>time to live (TTL), options for</primary></indexterm>ime to live (T T L) during which a NetBIOS name registered with the Samba server will remain active. You should never need to alter this value.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.3.4.7" id="ch07-SECT-3.4.7">
-<indexterm id="ch07-idx-958453-0"><primary>max wins ttl option</primary></indexterm>
-<title>
-max wins ttl</title>
-
-
-<para>This option give the maximum time to live (T T L) during which a NetBIOS name resolved from a WINS server will remain active. You should never need to change this value from its default.</para>
-</sect3>
-
-
-
-<sect3 role="" label="7.3.4.8" id="ch07-SECT-3.4.8">
-<indexterm id="ch07-idx-958454-0"><primary>min wins ttl option</primary></indexterm>
-<title>
-min wins ttl</title>
-
-
-<para>This option give the minimum time to live (T T L) during which a NetBIOS name resolved from a WINS server will remain active. You should never need to alter this value from its<indexterm id="ch07-idx-956431-0" class="endofrange" startref="ch07-idx-956430-0"/> default.<indexterm id="ch07-idx-956354-0" class="endofrange" startref="ch07-idx-956353-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="8" id="SAMBA-CH-8">
-<title>Additional Samba Information </title>
-
-
-
-
-<para>This chapter wraps up our coverage of the <filename>smb.conf</filename> configuration file with some miscellaneous options that can perform a variety of tasks. We will talk briefly about options for supporting programmers, internationalization, messages, and common Windows bugs. For the most part, you will use these options only in isolated circumstances. We also cover performing automated backups with the <filename>smbtar</filename> command at the end of this chapter. So without further ado, let's jump into our first subject: options to help programmers.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="8.1" id="ch08-56646">
-<title>Supporting Programmers</title>
-
-
-<para>
-<indexterm id="ch08-idx-965254-0" class="startofrange"><primary>programmers, support for</primary></indexterm>If <indexterm id="ch08-idx-965351-0" class="startofrange"><primary>smb.conf (Samba configuration) file</primary><secondary>options for</secondary><tertiary>supporting programmers</tertiary></indexterm>you have programmers accessing your Samba server, you'll want to be aware of the special options listed in <link linkend="ch08-73167">Table 8.1</link>.</para>
-
-
-<table label="8.1" id="ch08-73167">
-<title>Programming Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>time server</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, <emphasis>nmbd</emphasis> announces itself as a SMB time service to Windows clients.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>time offset</literal></para></entry>
-
-<entry colname="col2"><para>numerical (number of minutes)</para></entry>
-
-<entry colname="col3"><para>Adds a specified number of minutes to the reported time.</para></entry>
-
-<entry colname="col4"><para><literal>0</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>dos filetimes</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Allows non-owners of a file to change its time if they can write to it.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>dos filetime</literal></para>
-
-<para><literal>resolution</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Causes file times to be rounded to the next even second.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>fake directory create times</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Sets directory times to avoid a MS <emphasis>nmake</emphasis> bug.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="8.1.1" id="ch08-SECT-1.1">
-<title>Time Synchronization</title>
-
-
-<para>
-<indexterm id="ch08-idx-965360-0"><primary>synchronizing</primary><secondary>time, options for</secondary></indexterm>
-<indexterm id="ch08-idx-965360-1"><primary>time snychronization, options for</primary></indexterm>Time synchronization can be very important to programmers. Consider the following options:</para>
-
-
-<programlisting>time service = yes
-dos filetimes = yes
-fake directory create times = yes
-dos filetime resolution = yes
-delete readonly = yes</programlisting>
-
-
-<para>If you set these options, Samba shares will provide the kind of compatible file times that Visual C++, <emphasis>nmake</emphasis>, and other Microsoft programming tools require. Otherwise, PC <emphasis>make</emphasis> programs will tend to think that all the files in a directory need to be recompiled every time. Obviously, this is not the behavior you want.</para>
-
-
-<sect3 role="" label="8.1.1.1" id="ch08-SECT-1.1.1">
-<title>time server</title>
-
-
-<para>If your Samba server has an accurate clock, or if it's a client of one of the Unix network time servers, you can instruct it to advertise itself as an SMB time server by setting the<indexterm id="ch08-idx-965946-0"><primary>time server option</primary></indexterm> <literal>time</literal> <literal>server</literal> option as follows:</para>
-
-
-<programlisting>[global]
- time service = yes</programlisting>
-
-
-<para>The client will still have to request the correct time with the following DOS command, substituting the Samba server name in at the appropriate point:</para>
-
-
-<programlisting>C:\NET TIME \\<replaceable>server</replaceable> /YES /SET</programlisting>
-
-
-<para>This command can be placed in a Windows logon script (see <link linkend="SAMBA-CH-6">Chapter 6</link>).</para>
-
-
-<para>By default, the <literal>time</literal> <literal>server</literal> option is normally set to <literal>no</literal>. If you turn this service on, you can use the command above to keep the client clocks from drifting. Time synchronization is important to clients using programs such as <emphasis>make</emphasis>, which compile based on the last time the file was changed. Incorrectly synchronized times can cause such programs to either remake all files in a directory, which wastes time, or not recompile a source file that was just modified because of a slight clock drift.</para>
-</sect3>
-
-
-
-<sect3 role="" label="8.1.1.2" id="ch08-SECT-1.1.2">
-<title>time offset</title>
-
-
-<para>To deal with clients that don't process daylight savings time properly, Samba provides the <literal>time</literal> <literal>offset</literal> option. If set, it adds the specified number of minutes to the current time. This is handy if you're in Newfoundland and Windows doesn't know about the 30-minute time difference there:</para>
-
-
-<programlisting>[global]
- time offset = 30</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="8.1.1.3" id="ch08-SECT-1.1.3">
-<title>dos filetimes</title>
-
-
-<para>Traditionally, only the root user and the owner of a file can change its last-modified date on a Unix system. The share-level <literal>dos</literal> <literal>filetimes</literal> option allows the Samba server to mimic the characteristics of a DOS/Windows machine: any user can change the last modified date on a file in that share if he or she has write permission to it. In order to do this, Samba uses its root privileges to modify the timestamp on the file.</para>
-
-
-<para>By default, this option is disabled. Setting this option to <literal>yes</literal> is often necessary to allow PC <emphasis>make</emphasis> programs to work properly. Without it, they cannot change the last-modified date themselves. This often results in the program thinking <emphasis>all</emphasis> files need recompiling when they really don't.</para>
-</sect3>
-
-
-
-<sect3 role="" label="8.1.1.4" id="ch08-SECT-1.1.4">
-<title>dos filetime resolution</title>
-
-
-<para><literal>dos</literal>
-<indexterm id="ch08-idx-965949-0"><primary>os filetime resolution option</primary></indexterm> <literal>filetime</literal> <literal>resolution</literal> is share-level option. If set to <literal>yes</literal>, Samba will arrange to have the file times rounded to the closest two-second boundary. This option exists primarily to satisfy a quirk in Windows that prevents Visual C++ from correctly recognizing that a file has not changed. You can enable it as follows:</para>
-
-
-<programlisting>[data]
- dos filetime resolution = yes</programlisting>
-
-
-<para>We recommend using this option only if you are using Microsoft Visual C++ on a Samba share that supports opportunistic locking.</para>
-</sect3>
-
-
-
-<sect3 role="" label="8.1.1.5" id="ch08-SECT-1.1.5">
-<title>fake directory create times</title>
-
-
-<para>The <literal>fake</literal>
-<indexterm id="ch08-idx-965950-0"><primary>fake directory create times option</primary></indexterm> <literal>directory</literal> <literal>create</literal> <literal>times</literal> option exists to keep PC <emphasis>make</emphasis> programs sane. VFAT and NTFS filesystems record the creation date of a specific directory while Unix does not. Without this option, Samba takes the earliest recorded date it has for the directory (often the last-modified date of a file) and returns it to the client. If this is not sufficient, set the following option under a share definition:</para>
-
-
-<programlisting>[data]
- fake directory create times = yes</programlisting>
-
-
-<para>If set, Samba will adjust the directory create time it reports to the hardcoded value January 1st, 1980. This is primarily used to convince the Visual C++ <emphasis>nmake</emphasis> program that any object files in its build directories are indeed younger than the creation date of the directory itself and need to be recompiled.<indexterm id="ch08-idx-965924-0" class="endofrange" startref="ch08-idx-965351-0"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="8.2" id="ch08-79987">
-<title>Magic Scripts</title>
-
-
-<para>
-<indexterm id="ch08-idx-965216-0"><primary>magic scripts</primary></indexterm>
-<indexterm id="ch08-idx-965216-1"><primary>scripts</primary><secondary>magic</secondary></indexterm>The following options deal with <firstterm>magic scripts</firstterm> on the Samba server. Magic scripts are a method of running programs on Unix and redirecting the output back to the <indexterm id="ch08-idx-965385-0"><primary>SMB (Server Message Block)</primary><secondary>magic scripts</secondary></indexterm>SMB client. These are essentially an experimental hack. However, some users and their programs still rely on these two options for their programs to function correctly. Magic scripts are not widely trusted and their use is highly discouraged by the Samba team. See <link linkend="ch08-33693">Table 8.2</link> for more information.</para>
-
-
-<table label="8.2" id="ch08-33693">
-<title>Networking Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>magic script</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch08-idx-965386-0"><primary>networking</primary><secondary>options</secondary><tertiary>magic script</tertiary></indexterm>string (fully-qualified filename)</para></entry>
-
-<entry colname="col3"><para>Sets the name of a file to be executed by Samba, as the logged-on user, when closed.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>magic output</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified filename)</para></entry>
-
-<entry colname="col3"><para>Sets a file to log output from the magic file.</para></entry>
-
-<entry colname="col4"><para><emphasis>scriptname.out</emphasis></para></entry>
-
-<entry colname="col5"><para>Share</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="8.2.1" id="ch08-SECT-2.0.1">
-<title>magic script</title>
-
-
-<para>If the <literal>magic</literal>
-<indexterm id="ch08-idx-965952-0"><primary>magic script option</primary></indexterm> <literal>script</literal> option is set to a filename and the client creates a file by that name in that share, Samba will run the file as soon as the user has opened and closed it. For example, let's assume that the following option was created in the share <literal>[accounting]</literal>:</para>
-
-
-<programlisting>[accounting]
- magic script = tally.sh</programlisting>
-
-
-<para>Samba continually monitors the files in that share. If one by the name of <emphasis>tally.sh</emphasis> is closed (after being opened) by a user, Samba will execute the contents of that file locally. The file will be passed to the shell to execute; it must therefore be a legal Unix shell script. This means that it must have newline characters as line endings instead of Windows CR/LFs. In addition, it helps if you use the <literal>#!</literal> directive at the beginning of the file to indicate under which shell the script should run.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.2.2" id="ch08-SECT-2.0.2">
-<indexterm id="ch08-idx-965953-0"><primary>magic output option</primary></indexterm>
-<title>
-magic output</title>
-
-
-<para>This option specifies an output file that the script specified by the <literal>magic</literal> <literal>script</literal> option will send output to. You must specify a filename in a writable directory:</para>
-
-
-<programlisting>[accounting]
- magic script = tally.sh
- magic output = /var/log/magicoutput</programlisting>
-
-
-<para>If this option is omitted, the default output file is the name of the script (as stated in the <literal>magic</literal> <literal>script</literal> option) with the extension <emphasis>.out</emphasis> appended onto it.<indexterm id="ch08-idx-965526-0" class="endofrange" startref="ch08-idx-965254-0"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="8.3" id="ch08-91233">
-<title>Internationalization</title>
-
-
-<para>
-<indexterm id="ch08-idx-965219-0" class="startofrange"><primary>internationalization</primary></indexterm>
-<indexterm id="ch08-idx-965219-1" class="startofrange"><primary>foreign-language characters</primary></indexterm>
-<indexterm id="ch08-idx-965219-2" class="startofrange"><primary>localization</primary></indexterm>Samba has a limited ability to speak foreign tongues: if you need to deal with characters that aren't in standard ASCII, some options that can help you are shown in <link linkend="ch08-40870">Table 8.3</link>. Otherwise, you can skip over this section.</para>
-
-
-<table label="8.3" id="ch08-40870">
-<title>Networking Configuration Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>client code page</literal></para></entry>
-
-<entry colname="col2"><para>Described in this section</para></entry>
-
-<entry colname="col3"><para>Sets a code page to expect from clients</para></entry>
-
-<entry colname="col4"><para>850</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>character set</literal></para></entry>
-
-<entry colname="col2"><para>Described in this section</para></entry>
-
-<entry colname="col3"><para>Translates code pages into alternate UNIX character sets</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>coding system</literal></para></entry>
-
-<entry colname="col2"><para>Described in this section</para></entry>
-
-<entry colname="col3"><para>Translates code page 932 into an Asian character set</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>valid chars</literal></para></entry>
-
-<entry colname="col2"><para>string (set of characters)</para></entry>
-
-<entry colname="col3"><para>Obsolete: formerly added individual characters to a code page, and had to be used after setting client code page</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="8.3.1" id="ch08-17721">
-<indexterm id="ch08-idx-965956-0"><primary>client code page option</primary></indexterm>
-<title>
-client code page</title>
-
-
-<para>The character sets on Windows platforms hark back to the original concept of a <emphasis>code page</emphasis>
-<indexterm id="ch08-idx-965388-0"><primary>code pages</primary></indexterm>. These code pages are used by DOS and Windows clients to determine rules for mapping lowercase letters to uppercase letters. Samba can be instructed to use a variety of code pages through the use of the global <literal>client</literal> <literal>code</literal> <literal>page</literal> option in order to match the corresponding code page in use on the client. This option loads a code-page definition file, and can take the values specified in <link linkend="ch08-20815">Table 8.4</link>.</para>
-
-
-<table label="8.4" id="ch08-20815">
-<title>Valid Code Pages with Samba 2.0 </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Code Page</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>437</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch08-idx-965389-0"><primary>Samba</primary><secondary>version 2.0</secondary><tertiary>code pages for</tertiary></indexterm>MS-DOS Latin (United States)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>737</literal></para></entry>
-
-<entry colname="col2"><para>Windows 95 Greek</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>850</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Latin 1 (Western European)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>852</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Latin 2 (Eastern European)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>861</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Icelandic</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>866</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Cyrillic (Russian)</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>932</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Japanese Shift-JIS</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>936</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Simplified Chinese</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>949</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Korean Hangul</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>950</literal></para></entry>
-
-<entry colname="col2"><para>MS-DOS Traditional Chinese</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>You can set the client code page as follows:</para>
-
-
-<programlisting>[global]
- client code page = 852</programlisting>
-
-
-<para>The default value of this option is 850. You can use the <emphasis>make_smbcodepage</emphasis> tool that comes with Samba (by default in <filename>/usr/local/samba/bin</filename> ) to create your own SMB code pages, in the event that those listed earlier are not sufficient.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.3.2" id="ch08-SECT-3.0.2">
-<title>character set</title>
-
-
-<para>The global <literal>character</literal> <literal>set</literal> option can be used to convert filenames offered through a DOS code page (see the previous section, <link linkend="ch08-17721">Section 8.3.1</link>) to equivalents that can be represented by Unix character sets other than those in the United States. For example, if you want to convert the Western European MS-DOS character set on the client to a Western European Unix character set on the server, you can use the following in your configuration file:</para>
-
-
-<programlisting>[global]
- client code page = 850
- character set = ISO8859-1</programlisting>
-
-
-<para>Note that you must include a <literal>client</literal> <literal>code</literal> <literal>page</literal> option to specify the character set from which you are converting. The valid character sets (and their matching code pages) that Samba 2.0 accepts are listed in <link linkend="ch08-14126">Table 8.5</link>:</para>
-
-
-<table label="8.5" id="ch08-14126">
-<title>Valid Character Sets with Samba 2.0 </title>
-
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Character Set</para></entry>
-
-<entry colname="col2"><para>Matching Code Page</para></entry>
-
-<entry colname="col3"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>ISO8859-1</literal></para></entry>
-
-<entry colname="col2"><para><literal>850</literal>
-<indexterm id="ch08-idx-965390-0"><primary>Samba</primary><secondary>version 2.0</secondary><tertiary>character sets</tertiary></indexterm></para></entry>
-
-<entry colname="col3"><para>Western European Unix</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ISO8859-2</literal></para></entry>
-
-<entry colname="col2"><para><literal>852</literal></para></entry>
-
-<entry colname="col3"><para>Eastern European Unix</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ISO8859-5</literal></para></entry>
-
-<entry colname="col2"><para><literal>866</literal></para></entry>
-
-<entry colname="col3"><para>Russian Cyrillic Unix</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>KOI8-R</literal></para></entry>
-
-<entry colname="col2"><para><literal>866</literal></para></entry>
-
-<entry colname="col3"><para>Alternate Russian Cyrillic Unix</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>Normally, the <literal>character</literal> <literal>set</literal> option is disabled completely.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.3.3" id="ch08-SECT-3.0.3">
-<title>coding system</title>
-
-
-<para>The <literal>coding</literal>
-<indexterm id="ch08-idx-965965-0"><primary>coding system option</primary></indexterm> <literal>system</literal> option is similar to the <literal>character</literal> <literal>set</literal> option. However, its purpose is to determine how to convert a Japanese Shift JIS code page into an appropriate Unix character set. In order to use this option, the <literal>client</literal> <literal>code</literal> <literal>page</literal> option described previously must be set to page 932. The valid coding systems that Samba 2.0 accepts are listed in <link linkend="ch08-57476">Table 8.6</link>.</para>
-
-
-<table label="8.6" id="ch08-57476">
-<title>Valid Coding System Parameters with Samba 2.0 </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Character Set</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>SJIS</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch08-idx-965393-0"><primary>Samba</primary><secondary>version 2.0</secondary><tertiary>coding system parameters</tertiary></indexterm>Standard Shift JIS</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JIS8</literal></para></entry>
-
-<entry colname="col2"><para>Eight-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J8BB</literal></para></entry>
-
-<entry colname="col2"><para>Eight-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J8BH</literal></para></entry>
-
-<entry colname="col2"><para>Eight-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J8@B</literal></para></entry>
-
-<entry colname="col2"><para>Eight-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J8@J</literal></para></entry>
-
-<entry colname="col2"><para>Eight-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J8@H</literal></para></entry>
-
-<entry colname="col2"><para>Eight-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JIS7</literal></para></entry>
-
-<entry colname="col2"><para>Seven-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J7BB</literal></para></entry>
-
-<entry colname="col2"><para>Seven-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J7BH</literal></para></entry>
-
-<entry colname="col2"><para>Seven-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J7@B</literal></para></entry>
-
-<entry colname="col2"><para>Seven-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J7@J</literal></para></entry>
-
-<entry colname="col2"><para>Seven-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>J7@H</literal></para></entry>
-
-<entry colname="col2"><para>Seven-bit JIS codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JUNET</literal></para></entry>
-
-<entry colname="col2"><para>JUNET codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JUBB</literal></para></entry>
-
-<entry colname="col2"><para>JUNET codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JUBH</literal></para></entry>
-
-<entry colname="col2"><para>JUNET codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JU@B</literal></para></entry>
-
-<entry colname="col2"><para>JUNET codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JU@J</literal></para></entry>
-
-<entry colname="col2"><para>JUNET codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>JU@H</literal></para></entry>
-
-<entry colname="col2"><para>JUNET codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>EUC</literal></para></entry>
-
-<entry colname="col2"><para>EUC codes</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>HEX</literal></para></entry>
-
-<entry colname="col2"><para>Three-byte hexadecimal code</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>CAP</literal></para></entry>
-
-<entry colname="col2"><para>Three-byte hexadecimal code (Columbia Appletalk Program)</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.3.4" id="ch08-SECT-3.0.4">
-<title>valid chars</title>
-
-
-<para>The <literal>valid</literal>
-<indexterm id="ch08-idx-965969-0"><primary>valid chars option</primary></indexterm> <literal>chars</literal> option is an older Samba feature that will add individual characters to a code page. However, this option is being phased out in favor of more modern coding systems. You can use this option as follows:</para>
-
-
-<programlisting>valid chars = Î
-valid chars = 0450:0420 0x0A20:0x0A00
-valid chars = A:a</programlisting>
-
-
-<para>Each of the characters in the list specified should be separated by spaces. If there is a colon between two characters or their numerical equivalents, the data to the left of the colon is considered an uppercase character, while the data to the right is considered the lowercase character. You can represent characters both by literals (if you can type them) and by octal, hexadecimal, or decimal Unicode equivalents.</para>
-
-
-<para>We recommend against using this option. Instead, go with one of the standard code pages listed earlier in this section. If you do use this option, however, it must be listed after the <literal>client</literal> <literal>code</literal> <literal>page</literal> to which you wish to add the character. Otherwise, the characters will not be added.<indexterm id="ch08-idx-965533-0" class="endofrange" startref="ch08-idx-965219-0"/>
-<indexterm id="ch08-idx-965533-1" class="endofrange" startref="ch08-idx-965219-1"/>
-<indexterm id="ch08-idx-965533-2" class="endofrange" startref="ch08-idx-965219-2"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="8.4" id="ch08-82569">
-<title>WinPopup Messages</title>
-
-
-<para>
-<indexterm id="ch08-idx-965227-0"><primary>WinPopup tool</primary></indexterm>
-<indexterm id="ch08-idx-965227-1"><primary>Windows 95/98</primary><secondary>WinPopup tool</secondary></indexterm>
-<indexterm id="ch08-idx-965227-2"><primary>messages</primary><secondary>WinPopup</secondary></indexterm>You can use the WinPopup tool (<filename>WINPOPUP.EXE </filename> ) in Windows to send messages to users, machines, or entire workgroups on the network. This tool is provided with Windows 95 OSR2 and comes standard with Windows 98. With either Windows 95 or 98, however, you need to be running WinPopup to receive and send WinPopup messages. With Windows NT, you can still receive messages without starting such a tool; they will automatically appear in a small dialog box on the screen when received. The WinPopup application is shown in <link linkend="ch08-66444">Figure 8.1</link>.</para>
-
-
-<figure label="8.1" id="ch08-66444">
-<title>The WinPopup application</title>
-
-<graphic width="502" depth="360" fileref="figs/sam.0801.gif"></graphic>
-</figure>
-
-<para>Samba has a single WinPopup messaging option, <literal>message</literal> <literal>command</literal>, as shown in <link linkend="ch08-18671">Table 8.7</link>.</para>
-
-
-<table label="8.7" id="ch08-18671">
-<title>WinPopup Configuration Option </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameter</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>message command</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch08-idx-965394-0"><primary>Unix</primary><secondary>options</secondary><tertiary sortas="messaging">for messaging</tertiary></indexterm>
-<indexterm id="ch08-idx-965394-1"><primary>locks/locking files</primary><secondary>messaging option for</secondary></indexterm>
-<indexterm id="ch08-idx-965394-2"><primary>oplocks</primary><secondary>messaging option for</secondary></indexterm>string (fully-qualified pathname)</para></entry>
-
-<entry colname="col3"><para>Sets a command to run on Unix when a WinPopup message is received.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="8.4.1" id="ch08-SECT-4.0.1">
-<title>message command</title>
-
-
-<para>Samba's <literal>message</literal>
-<indexterm id="ch08-idx-965971-0"><primary>message command option</primary></indexterm> <literal>command</literal> option sets the path to a program that will run on the server when a Windows popup message arrives at the server. The command will be executed using the <literal>guest</literal> <literal>account</literal> user. What to do with one of these is questionable since it's probably for the Samba administrator, and Samba doesn't know his or her name. If you know there's a human using the console, the Samba team once suggested the following:</para>
-
-
-<programlisting>[global]
- message command = /bin/csh -c 'xedit %s; rm %s' &</programlisting>
-
-
-<para>Note the use of variables here. The <literal>%s</literal> variable will become the file that the message is in. This file should be deleted when the command is finished with it; otherwise, there will be a buildup of pop-up files collecting on the Samba server. In addition, the command must fork its own process (note the & after the command); otherwise the client may suspend and wait for notification that the command was sent successfully before continuing.</para>
-
-
-<para>In addition to the standard variables, <link linkend="ch08-29758">Table 8.8</link> shows the three unique variables that you can use in a <literal>message</literal> <literal>command</literal>.</para>
-
-
-<table label="8.8" id="ch08-29758">
-<title>Message Command Variables </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Variable</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>%s</literal></para></entry>
-
-<entry colname="col2"><para>The name of the file in which the message resides</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%</literal>f</para></entry>
-
-<entry colname="col2"><para>The name of the client that sent the message</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>%t</literal></para></entry>
-
-<entry colname="col2"><para>The name of the machine that is the destination of the message</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="8.5" id="ch08-SECT-5">
-<title>Recently Added Options</title>
-
-
-<para>
-<indexterm id="ch08-idx-965236-0"><primary>Samba</primary><secondary>version 2.0</secondary><tertiary>new options</tertiary></indexterm>Samba has several options that appeared around the time of Samba 2.0, but are not entirely supported. However, we will give you a brief overview of their workings in this section. These options are shown in <link linkend="ch08-72538">Table 8.9</link>.</para>
-
-
-<table label="8.9" id="ch08-72538">
-<title>Recently Added Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>change notify timeout</literal></para></entry>
-
-<entry colname="col2"><para>numerical (number of seconds)</para></entry>
-
-<entry colname="col3"><para>Sets the interval between checks when a client asks to wait for a change in a specified directory.</para></entry>
-
-<entry colname="col4"><para><literal>60</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>machine password timeout</literal></para></entry>
-
-<entry colname="col2"><para>numerical (number of seconds)</para></entry>
-
-<entry colname="col3"><para>Sets the renewal interval for NT domain machine passwords.</para></entry>
-
-<entry colname="col4"><para><literal>604,800</literal> (1 week )</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>stat cache</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, Samba will cache recent name mappings.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>stat cache size</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Sets the size of the stat cache.</para></entry>
-
-<entry colname="col4"><para><literal>50</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="8.5.1" id="ch08-SECT-5.0.1">
-<title>change notify timeout</title>
-
-
-<para>The <literal>change</literal>
-<indexterm id="ch08-idx-965973-0"><primary>change notify timeout option</primary></indexterm> <literal>notify</literal> <literal>timeout</literal> global option emulates a Windows NT SMB feature called <firstterm>change notification</firstterm>
-<indexterm id="ch08-idx-965415-0"><primary>change notification, new option for (Samba version 2.0)</primary></indexterm>. This allows a client to request that a Windows NT server periodically monitor a specific directory on a share for any changes. If any changes occur, the server will notify the client.</para>
-
-
-<para>As of version 2.0, Samba will perform this function for its clients. However, performing these checks too often can slow the server down considerably. This option sets the time period that Samba should wait between such checks. The default is one minute (60 seconds); however, you can use this option to specify an alternate time that Samba should wait between performing checks:</para>
-
-
-<programlisting>[global]
- change notify timeout = 30</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.5.2" id="ch08-SECT-5.0.2">
-<title>machine password timeout</title>
-
-
-<para>The <literal>machine</literal>
-<indexterm id="ch08-idx-965974-0"><primary>machine password timeout option</primary></indexterm> <literal>password</literal> <literal>timeout</literal> global option sets a retention period for NT <indexterm id="ch08-idx-965417-0"><primary>domains</primary><secondary>new option for password timeout (Samba version 2.0)</secondary></indexterm>
-<indexterm id="ch08-idx-965417-1"><primary>Windows NT</primary><secondary>passwords</secondary><tertiary>new option for timeout (Samba version 2.0)</tertiary></indexterm>domain machine passwords. The default is currently set to the same time period that Windows NT 4.0 uses: 604,800 seconds (one week). Samba will periodically attempt to change the <firstterm>machine account password</firstterm>, which is a password used specifically by another server to report changes to it. This option specifies the number of seconds that Samba should wait before attempting to change that password. The following example changes it to a single day, by specifying the following:</para>
-
-
-<programlisting>[global]
- machine password timeout = 86400</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.5.3" id="ch08-SECT-5.0.3">
-<title>stat cache</title>
-
-
-<para>The <literal>stat</literal>
-<indexterm id="ch08-idx-965977-0"><primary>stat cache option</primary></indexterm> <literal>cache</literal> global option turns on caching of recent case-insensitive name mappings. The default is <literal>yes</literal>. The Samba team recommends that you never change this parameter.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.5.4" id="ch08-SECT-5.0.4">
-<title>stat cache size</title>
-
-
-<para>
-<indexterm id="ch08-idx-965418-0"><primary>cache size, new option for (Samba version 2.0)</primary></indexterm>The <literal>stat</literal>
-<indexterm id="ch08-idx-965978-0"><primary>stat cache size option</primary></indexterm> <literal>cache</literal> <literal>size</literal> global option sets the size of the cache entries to be used for the <literal>stat</literal> <literal>cache</literal> option. The default here is 50. Again, the Samba team recommends that you never change this parameter.</para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="8.6" id="ch08-70923">
-<title>Miscellaneous Options</title>
-
-
-<para>
-<indexterm id="ch08-idx-965426-0"><primary>operating systems</primary><secondary>miscellaneous options for</secondary></indexterm>
-<indexterm id="ch08-idx-965426-1"><primary>Windows 95/98</primary><secondary>miscellaneous options for</secondary></indexterm>
-<indexterm id="ch08-idx-965426-2"><primary>Unix</primary><secondary>options</secondary><tertiary>miscellaneous</tertiary></indexterm>Many Samba options are present to deal with operating system issues on either Unix or Windows. The options shown in <link linkend="ch08-83566">Table 8.10</link> deal specifically with some of these known problems. We usually don't change these and we recommend the same to you.</para>
-
-
-<table label="8.10" id="ch08-83566">
-<title>Miscellaneous Options </title>
-
-<tgroup cols="5">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<colspec colnum="4" colname="col4"/>
-<colspec colnum="5" colname="col5"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Option</para></entry>
-
-<entry colname="col2"><para>Parameters</para></entry>
-
-<entry colname="col3"><para>Function</para></entry>
-
-<entry colname="col4"><para>Default</para></entry>
-
-<entry colname="col5"><para>Scope</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><literal>deadtime</literal></para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch08-idx-965429-0" class="startofrange"><primary>bug avoidance options</primary></indexterm>numerical (<indexterm id="ch08-idx-965437-0" class="startofrange"><primary>bug avoidance options</primary><secondary>list of</secondary></indexterm>number of minutes)</para></entry>
-
-<entry colname="col3"><para>Specifies the number of minutes of inactivity before a connection should be terminated.</para></entry>
-
-<entry colname="col4"><para><literal>0</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>dfree command</literal></para></entry>
-
-<entry colname="col2"><para>string (command)</para></entry>
-
-<entry colname="col3"><para>Used to provide a command that returns disk free space in a format recognized by Samba.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>fstype</literal></para></entry>
-
-<entry colname="col2"><para><literal>NTFS</literal>, <literal>FAT</literal>, or <literal>Samba</literal></para></entry>
-
-<entry colname="col3"><para>Sets the filesystem type reported by the server to the client.</para></entry>
-
-<entry colname="col4"><para><literal>NTFS</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>keep alive</literal></para></entry>
-
-<entry colname="col2"><para>seconds</para></entry>
-
-<entry colname="col3"><para>Sets the number of seconds between checks for an inoperative client.</para></entry>
-
-<entry colname="col4"><para>(none)</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max disk size</literal></para></entry>
-
-<entry colname="col2"><para>numerical (size in MB)</para></entry>
-
-<entry colname="col3"><para>Sets the largest disk size to return to a client, some of which have limits. Does not affect actual operations on the disk.</para></entry>
-
-<entry colname="col4"><para>(infinity)</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max mux</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Sets the maximum number of simultaneous SMB operations that clients may make.</para></entry>
-
-<entry colname="col4"><para><literal>50</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max open files</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Limits number of open files to be below Unix limits.</para></entry>
-
-<entry colname="col4"><para><literal>10,000</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>max xmit</literal></para></entry>
-
-<entry colname="col2"><para>numerical</para></entry>
-
-<entry colname="col3"><para>Specifies the maximum packet size that Samba will send.</para></entry>
-
-<entry colname="col4"><para><literal>65,535</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>nt pipe support</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Turns off an experimental NT feature, for benchmarking or in case of an error.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>nt smb support</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Turns off an experimental NT feature, for benchmarking or in case of an error.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>ole locking compatib-ility</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>Remaps out-of-range lock requests used on Windows to fit in allowable range on Unix. Turning it off causes Unix lock errors.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>panic action</literal></para></entry>
-
-<entry colname="col2"><para>command</para></entry>
-
-<entry colname="col3"><para>Program to run if Samba server fails; for debugging.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>set directory</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, allows VMS clients to issue <literal>set</literal> <literal>dir</literal> commands.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>smbrun</literal></para></entry>
-
-<entry colname="col2"><para>string (fully-qualified command)</para></entry>
-
-<entry colname="col3"><para>Sets the command Samba uses as a wrapper for shell commands.</para></entry>
-
-<entry colname="col4"><para>None</para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>status</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, allows Samba to monitor status for <literal>smbstatus</literal> command.</para></entry>
-
-<entry colname="col4"><para><literal>yes</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>strict sync</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>no</literal>, ignores Windows applications requests to perform a sync-to-disk.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>sync always</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, forces all client writes to be committed to disk before returning from the call.</para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><literal>strip dot</literal></para></entry>
-
-<entry colname="col2"><para>boolean</para></entry>
-
-<entry colname="col3"><para>If <literal>yes</literal>, strips trailing dots from Unix filenames.<indexterm id="ch08-idx-965441-0" class="endofrange" startref="ch08-idx-965437-0"/></para></entry>
-
-<entry colname="col4"><para><literal>no</literal></para></entry>
-
-<entry colname="col5"><para>Global</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<sect2 role="" label="8.6.1" id="ch08-SECT-6.0.1">
-<indexterm id="ch08-idx-965979-0"><primary>deadtime option</primary></indexterm>
-<title>
-deadtime</title>
-
-
-<para>This global option sets the number of minutes that Samba will wait for an inactive client before closing its session with the Samba server. A client is considered inactive when it has no open files and there is no data being sent from it. The default value for this option is 0, which means that Samba never closes any connections no matter how long they have been inactive. You can override it as follows:</para>
-
-
-<programlisting>[global]
- deadtime = 10</programlisting>
-
-
-<para>This tells Samba to terminate any inactive client sessions after 10 minutes. For most networks, setting this option as such will work because reconnections from the client are generally performed transparently to the user.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.2" id="ch08-SECT-6.0.2">
-<indexterm id="ch08-idx-965980-0"><primary>dfree command option</primary></indexterm>
-<title>
-dfree command</title>
-
-
-<para>
-<indexterm id="ch08-idx-965466-0"><primary>free space on disk, option for</primary></indexterm>This global option is used on systems that incorrectly determine the free space left on the disk. So far, the only confirmed system that needs this option set is Ultrix. There is no default value for this option, which means that Samba already knows how to compute the free disk space on its own and the results are considered reliable. You can override it as follows:</para>
-
-
-<programlisting>[global]
- dfree command = /usr/local/bin/dfree</programlisting>
-
-
-<para>This option should point to a script that should return the total disk space in a block, and the number of available blocks. The Samba documentation recommends the following as a usable script:</para>
-
-
-<programlisting>#!/bin/sh
-df $1 | tail -1 | awk '{print $2" "$4}'</programlisting>
-
-
-<para>On System V machines, the following will work:</para>
-
-
-<programlisting>#!/bin/sh
-/usr/bin/df $1 | tail -1 | awk '{print $3" "$5}'</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.3" id="ch08-SECT-6.0.3">
-<indexterm id="ch08-idx-965983-0"><primary>fstype option</primary></indexterm>
-<title>
-fstype</title>
-
-
-<para>This share-level option sets the type of <indexterm id="ch08-idx-965467-0"><primary>filesystems</primary><secondary>reporting on by Samba, option for</secondary></indexterm>filesystem that Samba reports when queried by the client. There are three strings that can be used as a value to this configuration option, as listed in <link linkend="ch08-80519">Table 8.11</link>.</para>
-
-
-<table label="8.11" id="ch08-80519">
-<title>Filesystem Types </title>
-
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Variable</para></entry>
-
-<entry colname="col2"><para>Definition</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>NTFS</para></entry>
-
-<entry colname="col2"><para>
-<indexterm id="ch08-idx-965468-0"><primary>filesystems</primary><secondary>types</secondary></indexterm>Microsoft Windows NT filesystem</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>FAT</para></entry>
-
-<entry colname="col2"><para>DOS FAT filesystem</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>Samba</para></entry>
-
-<entry colname="col2"><para>Samba filesystem</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-
-<para>The default value for this option is <literal>NTFS</literal>, which represents a Windows NT filesystem. There probably isn't a need to specify any other type of filesystem. However, if you need to, you can override it per share as follows:</para>
-
-
-<programlisting>[data]
- fstype = FAT</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.4" id="ch08-SECT-6.0.4">
-<title>keep alive</title>
-
-
-<para>
-<indexterm id="ch08-idx-965469-0"><primary>keep-alive packets, option for</primary></indexterm>This global option specifies the number of seconds that Samba waits between sending NetBIOS <emphasis>keep-alive packets</emphasis>. These packets are used to ping a client to detect whether it is still alive and on the network. The default value for this option is <literal>0</literal>, which means that Samba will not send any such packets at all. You can override it as follows:</para>
-
-
-<programlisting>[global]
- keep alive = 10</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.5" id="ch08-SECT-6.0.5">
-<indexterm id="ch08-idx-965985-0"><primary>max disk size option</primary></indexterm>
-<title>
-max disk size</title>
-
-
-<para>
-<indexterm id="ch08-idx-965470-0"><primary>disk shares</primary><secondary>maximum size of, option for</secondary></indexterm>This global option specifies an illusory limit, in megabytes, for each of the shares that Samba is using. You would typically set this option to prevent clients with older operating systems from incorrectly processing large disk spaces, such as those over one gigabyte.</para>
-
-
-<para>The default value for this option is <literal>0</literal>, which means there is no upper limit at all. You can override it as follows:</para>
-
-
-<programlisting>[global]
- max disk size = 1000</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.6" id="ch08-SECT-6.0.6">
-<indexterm id="ch08-idx-965986-0"><primary>max mux option</primary></indexterm>
-<title>
-max mux</title>
-
-
-<para>
-<indexterm id="ch08-idx-965471-0"><primary>SMB (Server Message Block)</primary><secondary>maximum number of operations, option for</secondary></indexterm>This global option specifies the maximum number of concurrent SMB operations that Samba allows. The default value for this option is <literal>50</literal>. You can override it as follows:</para>
-
-
-<programlisting>[global]
- max mux = 100</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.7" id="ch08-SECT-6.0.7">
-<indexterm id="ch08-idx-965987-0"><primary>max open files option</primary></indexterm>
-<title>
-max open files</title>
-
-
-<para>
-<indexterm id="ch08-idx-965478-0"><primary>files</primary><secondary>open, option for maximum number of</secondary></indexterm>This global option specifies the maximum number of open files that Samba should allow at any given time for all processes. This value must be equal to or less than the amount allowed by the operating system, which varies from system to system. The default value for this option is <literal>10,000</literal>. You can override it as follows:</para>
-
-
-<programlisting>[global]
- max open files = 8000</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.8" id="ch08-SECT-6.0.8">
-<indexterm id="ch08-idx-965988-0"><primary>max xmit option</primary></indexterm>
-<title>
-max xmit</title>
-
-
-<para>
-<indexterm id="ch08-idx-965482-0"><primary>packets</primary><secondary>maximum size of, option for</secondary></indexterm>This global option sets the maximum size of packets that Samba exchanges with a client. In some cases, setting a smaller maximum packet size can increase performance, especially with Windows for Workgroups. The default value for this option is <literal>65535</literal>. You can override it as follows:</para>
-
-
-<programlisting>[global]
- max xmit = 4096</programlisting>
-
-
-<para><link linkend="appb-19919">Section 2.2.2.6</link> in <link linkend="SAMBA-AP-B">Appendix B</link>," shows some uses for this option.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.9" id="ch08-SECT-6.0.9">
-<indexterm id="ch08-idx-965989-0"><primary>nt pipe support option</primary></indexterm>
-<title>
-nt pipe support</title>
-
-
-<para>
-<indexterm id="ch08-idx-965483-0"><primary>Windows NT</primary><secondary>pipes, option for</secondary></indexterm>This global option is used by developers to allow or disallow Windows NT clients the ability to make connections to the NT SMB-specific IPC$ pipes. As a user, you should never need to override the default:</para>
-
-
-<programlisting>[global]
- nt pipe support = yes</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.10" id="ch08-SECT-6.0.10">
-<indexterm id="ch08-idx-965990-0"><primary>nt smb support option</primary></indexterm>
-<title>
-nt smb support</title>
-
-
-<para>
-<indexterm id="ch08-idx-965484-0"><primary>Windows NT</primary><secondary>SMB, option for</secondary></indexterm>
-<indexterm id="ch08-idx-965484-1"><primary>SMB (Server Message Block)</primary><secondary>option for NT-specific options</secondary></indexterm>This global option is used by developers to negotiate NT-specific SMB options with Windows NT clients. The Samba team has discovered that slightly better performance comes from setting this value to <literal>no</literal>. However, as a user, you should probably not override the default:</para>
-
-
-<programlisting>[global]
- nt smb support = yes</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.11" id="ch08-SECT-6.0.11">
-<indexterm id="ch08-idx-965991-0"><primary>ole locking compatibility option</primary></indexterm>
-<title>
-ole locking compatibility</title>
-
-
-<para>This global option turns off Samba's internal byte-range locking manipulation in files, which gives compatibility with Object Linking and Embedding (OLE) applications that use high byte-range locks as a method of interprocess communication. The default value for this option is <literal>yes</literal>. If you trust your Unix locking mechanisms, you can override it as follows:</para>
-
-
-<programlisting>[global]
- ole locking compatibility = no</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.12" id="ch08-SECT-6.0.12">
-<indexterm id="ch08-idx-965992-0"><primary>panic action option</primary></indexterm>
-<title>
-panic action</title>
-
-
-<para>
-<indexterm id="ch08-idx-965492-0"><primary>fatal error, option for</primary></indexterm>This global option specifies a command to execute in the event that Samba itself encounters a fatal error when loading or running. There is no default value for this option. You can specify an action as follows:</para>
-
-
-<programlisting>[global]
- panic action = /bin/csh -c
- 'xedit < "Samba has shutdown unexpectedly!'</programlisting>
-</sect2>
-
-
-<sect2 role="" label="8.6.13" id="ch08-SECT-6.0.14">
-<indexterm id="ch08-idx-965994-0"><primary>smbrun option</primary></indexterm>
-<title>
-smbrun</title>
-
-
-<para>This option sets the location of the <emphasis>smbrun</emphasis> executable, which Samba uses as a wrapper to run shell commands. The default value for this option is automatically configured by Samba when it is compiled. If you did not install Samba to the standard directory, you can specify where the binary is as follows:</para>
-
-
-<programlisting>[global]
- smbrun = /usr/local/bin/smbrun</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.14" id="ch08-SECT-6.0.15">
-<indexterm id="ch08-idx-965995-0"><primary>status option</primary></indexterm>
-<title>
-status</title>
-
-
-<para>This global option indicates whether Samba should log all <indexterm id="ch08-idx-965499-0"><primary>active connections, option for</primary></indexterm>
-<indexterm id="ch08-idx-965499-1"><primary>connections</primary><secondary>active, option for</secondary></indexterm>active connections to a status file. This file is used only by the <emphasis>smbstatus</emphasis> command. If you have no intentions of using this command, you can set this option to <literal>no</literal>, which can result in a small increase of speed on the server. The default value for this option is <literal>yes</literal>. You can override it as follows:</para>
-
-
-<programlisting>[global]
- status = no</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.15" id="ch08-SECT-6.0.16">
-<indexterm id="ch08-idx-965996-0"><primary>strict sync option</primary></indexterm>
-<title>
-strict sync</title>
-
-
-<para>This share-level option determines whether Samba honors all requests to perform a <indexterm id="ch08-idx-965500-0"><primary>disk sync, options for</primary></indexterm>disk sync when requested to do so by a client. Many clients request a disk sync when they are really just trying to flush data to their own open files. As a result, this can substantially slow a Samba server down. The default value for this option is <literal>no</literal>. You can override it as follows:</para>
-
-
-<programlisting>[data]
- strict sync = yes</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.16" id="ch08-SECT-6.0.17">
-<indexterm id="ch08-idx-965997-0"><primary>sync always option</primary></indexterm>
-<title>
-sync always</title>
-
-
-<para>This share-level option decides whether every write to disk should be followed by a disk synchronization before the write call returns control to the client. Even if the value of this option is <literal>no</literal>, clients can request a disk synchronization; see the <literal>strict</literal> <literal>sync</literal> option above. The default value for this option is <literal>no</literal>. You can override it per share as follows:</para>
-
-
-<programlisting>[data]
- sync always = yes</programlisting>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="8.6.17" id="ch08-SECT-6.0.18">
-<indexterm id="ch08-idx-965998-0"><primary>strip dot option</primary></indexterm>
-<title>
-strip dot</title>
-
-
-<para>This global option determines whether to remove the <indexterm id="ch08-idx-965502-0"><primary>trailing dot, option for</primary></indexterm>
-<indexterm id="ch08-idx-965502-1"><primary>filenames</primary><secondary>Unix, option for</secondary></indexterm>
-<indexterm id="ch08-idx-965502-2"><primary>Unix</primary><secondary>filenames, option for</secondary></indexterm>trailing dot from Unix filenames that are formatted with a dot at the end. The default value for this option is <literal>no</literal>. You can override it per share as follows:</para>
-
-
-<programlisting>[global]
- strip dot = yes</programlisting>
-
-
-<para>This option is now considered obsolete; the user should use the <literal>mangled</literal> <literal>map</literal> option insead.<indexterm id="ch08-idx-965454-0" class="endofrange" startref="ch08-idx-965429-0"/></para>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="8.7" id="ch08-74829">
-<title>Backups with smbtar</title>
-
-
-<para>
-<indexterm id="ch08-idx-965244-0" class="startofrange"><primary>smbtar program</primary></indexterm>
-<indexterm id="ch08-idx-965244-1" class="startofrange"><primary>backups, with smbtar program</primary></indexterm>Our final topic in this chapter is the <filename>smbtar</filename> tool. One common problem with modem PCs is that floppies and even CD-ROMs are often too small to use for backups. However, buying one tape drive per machine would also be silly. Consequently, many sites don't back up their PCs at all. Instead, they reinstall them using floppy disks and CD-ROMs when they fail.</para>
-
-
-<para>Thankfully, Samba provides us with another option: you can back up PCs' data using the <filename>smbtar</filename> tool. This can be done on a regular basis if you keep user data on your Samba system, or only occasionally, to save the local applications and configuration files and thus make repairs and reinstallations quicker.</para>
-
-
-<para>To back up PCs from a <indexterm id="ch08-idx-965519-0"><primary>Unix</primary><secondary>servers, backing up computers from</secondary></indexterm>Unix server, you need to do three things:</para>
-
-
-<orderedlist>
-<listitem><para>Ensure that File and Printer Sharing is installed on the PC and is bound to the TCP/IP protocol.</para></listitem>
-<listitem><para>Explicitly share a disk on the PC so it can be read from the server.</para></listitem>
-<listitem><para>Set up the backup scripts on the server.</para></listitem>
-</orderedlist>
-
-<para>We'll use Windows 95/98 to illustrate the first two steps. Go to the Networking icon in the Control Panel window, and check that <indexterm id="ch08-idx-965520-0"><primary sortas="File and Printer Sharing for Microsoft Networks">"File and Printer Sharing for Microsoft Networks"</primary></indexterm>File and Printer Sharing for Microsoft Networks is currently listed in the top window, as shown in <link linkend="ch08-18303">Figure 8.2</link>.</para>
-
-
-<figure label="8.2" id="ch08-18303">
-<title>The Networking window</title>
-
-<graphic width="502" depth="368" fileref="figs/sam.0802.gif"></graphic>
-</figure>
-
-<para>If "File and printer sharing for Microsoft Networks" isn't installed, you can install it by clicking on the Add button on the Network panel. After pressing it, you will be asked what service to add. Select Service and move forward, and you will be asked for a vendor and a service to install. Finally, select "File and printer sharing for Microsoft Networks," and click on Done to install the service.</para>
-
-
-<para>Once you've installed "File and printer sharing for Microsoft Networks," return to the Network panel and select the TCP/IP protocol that is tied to your Samba network adapter. Then, click on the Properties button and choose the Bindings tab at the top. You should see a dialog box similar to <link linkend="ch08-41042">Figure 8.3</link>. Here, you'll need to verify that the "File and Printer Sharing" checkbox is checked, giving it access to TCP/IP. At this point you can share disks with other machines on the net.</para>
-
-
-<figure label="8.3" id="ch08-41042">
-<title>TCP/IP Bindings</title>
-
-<graphic width="502" depth="248" fileref="figs/sam.0803.gif"></graphic>
-</figure>
-
-<para>The next step is to share the disk you want to back up with the tape server. Go to My Computer and select, for example, the My Documents directory. Then right-click on the icon and select its Properties. This should yield the dialog box in <link linkend="ch08-64918">Figure 8.4</link>.</para>
-
-
-<figure label="8.4" id="ch08-64918">
-<title>My Documents Properties</title>
-
-<graphic width="502" depth="352" fileref="figs/sam.0804.gif"></graphic>
-</figure>
-
-<para>Select the Sharing tab and turn file sharing on. You now have the choice to share the disk as read-only, read-write (Full), or either, each with separate password. This is the Windows 95/98 version, so it provides only share-level security. In this example, we made it read/write and set a password, as shown in <link linkend="ch08-29192">Figure 8.5</link>. When you enter the password and click on OK, you'll be prompted to re-enter it. After that, you have finished the second step.</para>
-
-
-<figure label="8.5" id="ch08-29192">
-<title>MyFiles Properties as shared</title>
-
-<graphic width="502" depth="374" fileref="figs/sam.0805.gif"></graphic>
-</figure>
-
-<para>Finally, the last step is to set up a backup script on the tape server, using the <filename>smbtar</filename> program. The simplest script might contain only a single line and would be something like the following:</para>
-
-
-<programlisting>smbtar -s client -t /dev/rst0 -x "My Documents" -p <replaceable>password</replaceable></programlisting>
-
-
-<para>This unconditionally backs up the <emphasis>//client/My Documents</emphasis> share to the device <filename>/dev/rst0</filename>. Of course, this is excessively simple and quite insecure. What you will want to do will depend on your existing backup scheme.</para>
-
-
-<para>However, to whet your appetite, here are some possibilities of what <filename>smbtar</filename> can do:</para>
-
-
-<itemizedlist>
-<listitem><para>Back up files incrementally using the DOS archive bit (the <literal>-i</literal> option). This requires the client share to be accessed read-write so the bit can be cleared by <filename>smbtar</filename></para></listitem>
-<listitem><para>Back up only files that have changed since a specified date (using the <literal>-N</literal> <replaceable>filename </replaceable>option)</para></listitem>
-<listitem><para>Back up entire PC drives, by sharing all of C: or D:, for example, and backing that up</para></listitem>
-</itemizedlist>
-
-<para>Except for the first example, each of these can be done with the PC sharing set to read-only, reducing the security risk of having passwords in scripts and passing them on the command line.<indexterm id="ch08-idx-965514-0" class="endofrange" startref="ch08-idx-965244-0"/>
-<indexterm id="ch08-idx-965514-1" class="endofrange" startref="ch08-idx-965244-1"/></para>
-</sect1>
-</chapter>
+++ /dev/null
-<chapter label="9" id="SAMBA-CH-9">
-<title>Troubleshooting Samba</title>
-
-
-
-
-<para>
-<indexterm id="ch09-idx-953453-0" class="startofrange"><primary>troubleshooting</primary></indexterm>Samba is extremely robust. Once you've got everything set up the way you want, you'll probably forget that it is running. When trouble occurs, it's typically during installation or when you're trying to add something new to the server. Fortunately, there are a wide variety of resources that you can use to diagnose these troubles. While we can't describe in detail the solution to every problem that you might encounter, you should be able to get a good start at a resolution by following the advice given in this chapter.</para>
-
-
-<para>The first section of the chapter lists the tool bag, a collection of tools available for troubleshooting Samba; the second section is a detailed how-to, and the last section lists extra resources you may need to track down particularly stubborn problems.</para>
-
-
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="9.1" id="ch09-36385">
-<title>The Tool Bag</title>
-
-
-<para>
-<indexterm id="ch09-idx-953455-0"><primary>troubleshooting</primary><secondary>where to start</secondary></indexterm>Sometimes Unix seems to be made up of a handful of applications and tools. There are tools to troubleshoot tools. And of course, there are several ways to accomplish the same task. When you are trying to solve a problem related to Samba, a good plan of attack is to check the following:</para>
-
-
-<orderedlist>
-<listitem><para>Samba logs</para></listitem>
-<listitem><para>Fault tree</para></listitem>
-<listitem><para>Unix utilities</para></listitem>
-<listitem><para>Samba test utilities</para></listitem>
-<listitem><para>Documentation and FAQs</para></listitem>
-<listitem><para>Searchable archives</para></listitem>
-<listitem><para>Samba newsgroups</para></listitem>
-</orderedlist>
-
-<para>Let's go over each of these one by one in the following sections.</para>
-
-
-<sect2 role="" label="9.1.1" id="ch09-SECT-1.1">
-<title>Samba Logs</title>
-
-
-<para>
-<indexterm id="ch09-idx-953456-0" class="startofrange"><primary>log files/logging</primary><secondary>troubleshooting from</secondary></indexterm>Your first line of attack should always be to check the log files. The Samba log files can help diagnose the vast majority of the problems that beginning to intermediate Samba administrators are likely to face. Samba is quite flexible when it comes to logging. You can set up the server to log as little or as much as you want. Substitution variables that allow you to isolate individual logs for each machine, share, or combination thereof.</para>
-
-
-<para>By default, logs are placed in <replaceable>samba_directory</replaceable><emphasis>/var/smbd.log</emphasis> and <replaceable>samba_directory</replaceable><emphasis>/var/nmbd.log</emphasis>, where <literal>samba_directory</literal> is the location where Samba was installed (typically, <filename>/usr/local/samba</filename>). As we mentioned in <link linkend="ch04-21486">Chapter 4</link>, you can override the location and name using the <literal>log</literal> <literal>file</literal> configuration option in <filename>smb.conf</filename>. This option accepts all of the substitution variables mentioned in <link linkend="SAMBA-CH-2">Chapter 2</link>, so you could easily have the server keep a separate log for each connecting client by specifying the following in the <literal>[global]</literal> section of <filename>smb.conf </filename>:</para>
-
-
-<programlisting>log file = %m.log</programlisting>
-
-
-<para>Alternatively, you can specify a log directory to use with the <literal>-l</literal> flag on the command line. For example:</para>
-
-
-<programlisting>smbd -l /usr/local/var/samba</programlisting>
-
-
-<para>Another useful trick is to have the server keep a log for each service (share) that is offered, especially if you suspect a particular share is causing trouble. Use the <literal>%S</literal> variable to set this up in the <literal>[global]</literal> section of the configuration file:</para>
-
-
-<programlisting>log file = %S.log</programlisting>
-
-
-<sect3 role="" label="9.1.1.1" id="ch09-28969">
-<title>Log levels</title>
-
-
-<para>
-<indexterm id="ch09-idx-953457-0" class="startofrange"><primary>log files/logging</primary><secondary>levels of</secondary><tertiary>setting</tertiary></indexterm>The level of logging that Samba uses can be set in the <filename>smb.conf</filename> file using the global <literal>log</literal>
-<indexterm id="ch09-idx-954135-0"><primary>log level option</primary></indexterm>
-<indexterm id="ch09-idx-954135-1"><primary>debug level option</primary></indexterm> <literal>level</literal> or <literal>debug</literal> <literal>level</literal> option; they are equivalent. The logging level is an integer which ranges from 0 (no logging), and increases the logging to voluminous by <literal>log</literal> <literal>level</literal> <literal>=</literal> <literal>3</literal>. For example, let's assume that we are going to use a Windows client to browse a directory on a Samba server. For a small amount of log information, you can use <literal>log</literal> <literal>level</literal> <literal>=</literal> <literal>1</literal>, which instructs Samba to show only cursory information, in this case only the connection itself:</para>
-
-
-<programlisting>105/25/98 22:02:11 server (192.168.236.86) connect to service public as user pcguest (uid=503,gid=100) (pid 3377)</programlisting>
-
-
-<para>Higher debug levels produce more detailed information. Usually you won't need any more than level 3; this is more than adequate for most Samba administrators. Levels above 3 are for use by the developers and dump enormous amounts of cryptic information.</para>
-
-
-<para>Here is example output at levels 2 and 3 for the same operation. Don't worry if you don't understand the intricacies of an SMB connection; the point is simply to show you what types of information are shown at the different logging levels:</para>
-
-
-<programlisting>/* Level 2 */
-Got SIGHUP
-Processing section "[homes]"
-Processing section "[public]"
-Processing section "[temp]"
-Allowed connection from 192.168.236.86 (192.168.236.86) to IPC$
-Allowed connection from 192.168.236.86 (192.168.236.86) to IPC/
-
-
-/* Level 3 */
-05/25/98 22:15:09 Transaction 63 of length 67
-switch message SMBtconX (pid 3377)
-Allowed connection from 192.168.236.86 (192.168.236.86) to IPC$
-ACCEPTED: guest account and guest ok
-found free connection number 105
-Connect path is /tmp
-chdir to /tmp
-chdir to /
-05/25/98 22:15:09 server (192.168.236.86) connect to service IPC$ as user pcguest (uid=503,gid=100) (pid 3377)
-05/25/98 22:15:09 tconX service=ipc$ user=pcguest cnum=105
-05/25/98 22:15:09 Transaction 64 of length 99
-switch message SMBtrans (pid 3377)
-chdir to /tmp
-trans <\PIPE\LANMAN> data=0 params=19 setup=0
-Got API command 0 of form <WrLeh> <B13BWz> (tdscnt=0,tpscnt=19,mdrcnt=4096,mprcnt=8)
-Doing RNetShareEnum
-RNetShareEnum gave 4 entries of 4 (1 4096 126 4096)
-05/25/98 22:15:11 Transaction 65 of length 99
-switch message SMBtrans (pid 3377)
-chdir to /
-chdir to /tmp
-trans <\PIPE\LANMAN> data=0 params=19 setup=0
-Got API command 0 of form <WrLeh> <B13BWz> (tdscnt=0,tpscnt=19,mdrcnt=4096,mprcnt=8)
-Doing RNetShareEnum
-RNetShareEnum gave 4 entries of 4 (1 4096 126 4096)
-05/25/98 22:15:11 Transaction 66 of length 95
-switch message SMBtrans2 (pid 3377)
-chdir to /
-chdir to /pcdisk/public
-call_trans2findfirst: dirtype = 0, maxentries = 6, close_after_first=0, close_if_end = 0 requires_resume_key = 0 level = 260, max_data_bytes = 2432
-unix_clean_name [./DESKTOP.INI]
-unix_clean_name [desktop.ini]
-unix_clean_name [./]
-creating new dirptr 1 for path ./, expect_close = 1
-05/25/98 22:15:11 Transaction 67 of length 53
-switch message SMBgetatr (pid 3377)
-chdir to /
-
-[...]</programlisting>
-
-
-<para>We cut off this listing after the first packet because it runs on for many pages. However, you should be aware that log levels above 3 will quickly fill your disk with megabytes of excruciating detail concerning Samba internal operations. Log level 3 is extremely useful for following exactly what the server is doing, and most of the time it will be obvious where an error is occurring by glancing through the log file.</para>
-
-
-<para>A word of warning: using a high log level (3 or above) will <emphasis>seriously</emphasis> slow down the Samba server. Remember that every log message generated causes a write to disk (an inherently slow operation) and log levels greater than 2 produce massive amounts of data. Essentially, you should turn on logging level 3 only when you're actively tracking a problem in the Samba server.<indexterm id="ch09-idx-953461-0" class="endofrange" startref="ch09-idx-953457-0"/></para>
-</sect3>
-
-
-
-<sect3 role="" label="9.1.1.2" id="ch09-SECT-1.1.2">
-<title>Activating and deactivating logging</title>
-
-
-<para>
-<indexterm id="ch09-idx-953474-0"><primary>log files/logging</primary><secondary>activating/deactivating</secondary></indexterm>To turn logging on and off, set the appropriate level in the <literal>[global]</literal> section of <filename>smb.conf</filename>. Then, you can either restart Samba, or force the current daemon to reprocess the configuration file. You also can send the <emphasis>smbd</emphasis> process a SIGUSR1 signal to increase its log level by one while it's running, and a SIGUSR2 signal to decrease it by one:</para>
-
-
-<programlisting># Increase the logging level by 1
-kill -SIGUSR1 1234
-
-# Decrease the logging level by 1
-kill -SIGUSR2 1234</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="9.1.1.3" id="ch09-34448">
-<title>Logging by individual client machines or users</title>
-
-
-<para>
-<indexterm id="ch09-idx-953475-0"><primary>Windows clients</primary><secondary>individual configuration files for</secondary></indexterm>
-<indexterm id="ch09-idx-953475-1"><primary>configuration files</primary><secondary sortas="individual clients">for individual clients</secondary></indexterm>An effective way to diagnose problems without hampering other users is to assign different log levels for different machines in <literal>[global]</literal> section of the <filename>smb.conf</filename> file. We can do this by building on the strategy we presented earlier:</para>
-
-
-<programlisting>[global]
- log level = 0
- log file = /usr/local/samba/lib/log.%m
- include = /usr/local/samba/lib/smb.conf.%m</programlisting>
-
-
-<para>These options instruct Samba to use unique configuration and log files for each client that connects. Now all you have to do is create an <filename>smb.conf</filename>
-<indexterm id="ch09-idx-953477-0"><primary>smb.conf (Samba configuration) file</primary><secondary>creating</secondary><tertiary sortas="each client">for each client</tertiary></indexterm> file for a specific client machine with a <literal>log</literal> <literal>level</literal> <literal>=</literal> <literal>3</literal> entry in it (the others will pick up the default log level of 0) and use that log file to track down the problem.</para>
-
-
-<para>Similarly, if only particular users are experiencing a problem, and it travels from machine to machine with them, you can isolate logging to a specific user by adding the following to the <filename>smb.conf</filename> file:</para>
-
-
-<programlisting>[global]
- log level = 0
- log file = /usr/local/samba/lib/log.%u
- include = /usr/local/samba/lib/smb.conf.%u</programlisting>
-
-
-<para>Then you can create a unique <filename>smb.conf</filename> file for each user (e.g., <filename>/usr/local/samba/lib/smb.conf.tim</filename>) files containing the configuration option <literal>log</literal> <literal>level</literal> <literal>=</literal> <literal>3</literal> and only those users will get more detailed logging.<indexterm id="ch09-idx-953469-0" class="endofrange" startref="ch09-idx-953456-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.1.2" id="ch09-SECT-1.2">
-<title>Samba Test Utilities</title>
-
-
-<para>
-<indexterm id="ch09-idx-953478-0" class="startofrange"><primary>Samba</primary><secondary>test utilities</secondary></indexterm>
-<indexterm id="ch09-idx-953478-1" class="startofrange"><primary>testing</primary><secondary>test utilities for Samba</secondary></indexterm>A rigorous set of tests that exercise the major parts of Samba are described in various files in the <emphasis>/docs/textdocs</emphasis>
-<indexterm id="ch09-idx-953497-0"><primary>docs directory</primary><secondary>test utilities</secondary></indexterm> directory of the Samba distribution kit, starting with <emphasis>DIAGNOSIS.TXT.</emphasis> The fault tree in this chapter is a more detailed version of the basic tests suggested by the Samba team, but covers only installation and reconfiguration diagnosis, like <emphasis>DIAGNOSIS.TXT.</emphasis> The other files in the <emphasis>/docs</emphasis> subdirectoryies address specific problems (such as Windows NT clients) and instruct you how to troubleshoot items not included in this book. If the fault tree doesn't suffice, be sure to look at <emphasis>DIAGNOSIS.TXT</emphasis> and its friends.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.1.3" id="ch09-SECT-1.3">
-<title>Unix Utilities</title>
-
-
-<para>
-<indexterm id="ch09-idx-953505-0"><primary>Unix</primary><secondary>troubleshooting utilities</secondary></indexterm>Sometimes it's useful to use a tool outside of the Samba suite to examine what's happening inside the server. Unix has always been a "kitchen-sink" operating system. Two diagnostic tools can be of particular help in debugging Samba troubles: <emphasis>trace</emphasis> and <emphasis>tcpdump</emphasis>.</para>
-
-
-<sect3 role="" label="9.1.3.1" id="ch09-SECT-1.3.1">
-<indexterm id="ch09-idx-953506-0"><primary>trace utility</primary></indexterm>
-<title>Using trace</title>
-
-
-<para>The <emphasis>trace</emphasis> command masquerades under several different names, depending on the operating system that you are using. On Linux it will be <emphasis>strace</emphasis>, on Solaris you'll use <emphasis>truss</emphasis>, and SGI will have <emphasis>padc</emphasis> and <emphasis>par</emphasis>. All have essentially the same function, which is to display each operating system function call as it is executed. This allows you to follow the execution of a program, such as the Samba server, and will often pinpoint the exact call that is causing the difficulty.</para>
-
-
-<para>One problem that <emphasis>trace</emphasis> can highlight is the location of an incorrect version of a dynamically linked library. This can happen if you've downloaded prebuilt binaries of Samba. You'll typically see the offending call at the end of the <emphasis>trace</emphasis>, just before the program terminates.</para>
-
-
-<para>A sample <literal>strace</literal> output for the Linux operating system follows. This is a small section of a larger file created during the opening of a directory on the Samba server. Each line is a system-call name, and includes its parameters and the return value. If there was an error, the error value (e.g., <literal>ENOENT</literal>) and its explanation are also shown. You can look up the parameter types and the errors that can occur in the appropriate <literal>trace</literal> manual page for the operating system that you are using.</para>
-
-
-<programlisting>chdir("/pcdisk/public") = 0
-stat("mini/desktop.ini", 0xbffff7ec) = -1 ENOENT (No such file or directory)
-stat("mini", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
-stat("mini/desktop.ini", 0xbffff7ec) = -1 ENOENT (No such file or directory)
-open("mini", O_RDONLY) = 5
-fcntl(5, F_SETFD, FD_CLOEXEC) = 0
-fstat(5, {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0
-lseek(5, 0, SEEK_CUR) = 0
-SYS_141(0x5, 0xbfffdbbc, 0xedc, 0xbfffdbbc, 0x80ba708) = 196
-lseek(5, 0, SEEK_CUR) = 1024
-SYS_141(0x5, 0xbfffdbbc, 0xedc, 0xbfffdbbc, 0x80ba708) = 0
-close(5) = 0
-stat("mini/desktop.ini", 0xbffff86c) = -1 ENOENT (No such file or directory)
-write(3, "\0\0\0#\377SMB\10\1\0\2\0\200\1\0"..., 39) = 39
-SYS_142(0xff, 0xbffffc3c, 0, 0, 0xbffffc08) = 1
-read(3, "\0\0\0?", 4) = 4
-read(3, "\377SMBu\0\0\0\0\0\0\0\0\0\0\0\0"..., 63) = 63
-time(NULL) = 896143871</programlisting>
-
-
-<para>This example shows several <literal>stat</literal> calls failing to find the files they were expecting. You don't have to be a expert to see that the file <emphasis>desktop.ini</emphasis> is missing from that directory. In fact, many difficult problems can be identified by looking for obvious, repeatable errors with <emphasis>trace</emphasis>. Often, you need not look farther than the last message before a crash.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.1.3.2" id="ch09-SECT-1.3.2">
-<title>Using tcpdump</title>
-
-
-<para>The <emphasis>tcpdump</emphasis>
-<indexterm id="ch09-idx-953802-0" class="startofrange"><primary>tcpdump utility</primary></indexterm> program, written by <indexterm id="ch09-idx-953803-0"><primary>Jacobson, Van</primary></indexterm>
-<indexterm id="ch09-idx-953803-1"><primary>Leres, Craig</primary></indexterm>
-<indexterm id="ch09-idx-953803-2"><primary>McCanne, Steven</primary></indexterm>
-<indexterm id="ch09-idx-953803-3"><primary>Tridgell, Andrew</primary></indexterm>Van Jacobson, Craig Leres, and Steven McCanne, and extended by Andrew Tridgell, allows you to monitor network traffic in real time. A variety of output formats are available and you can filter the output to look at only a particular type of traffic. The <emphasis>tcpdump</emphasis> program lets you examine all conversations between client and server, including SMB and NMB <indexterm id="ch09-idx-953805-0"><primary>broadcasting</primary><secondary>troubleshooting with tcpdump utility</secondary></indexterm>broadcast messages. While its troubleshooting capabilities lie mainly at the OSI network layer, you can still use its output to get a general idea of what the server and client are attempting to accomplish.</para>
-
-
-<para>A sample <emphasis>tcpdump</emphasis> log follows. In this instance, the client has requested a directory listing and the server has responded appropriately, giving the directory names <literal>homes</literal>, <literal>public</literal>, <literal>IPC$</literal>, and <literal>temp</literal> (we've added a few explanations on the right):</para>
-
-
-<programlisting>$<userinput>tcpdump -v -s 255 -i eth0 port not telnet</userinput>
-SMB PACKET: SMBtrans (REQUEST) <replaceable>Request packet</replaceable>
-SMB Command = 0x25 <replaceable>Request was ls or dir</replaceable>.
-
-[000] 01 00 00 10 ....
-
-
->>> NBT Packet
-<replaceable>Outer frame of SMB packe</replaceable>t
-NBT Session Packet
-Flags=0x0
-Length=226
-[lines skipped]
-
-SMB PACKET: SMBtrans (REPLY) <replaceable>Beginning of a reply to request </replaceable>
-SMB Command = 0x25 <replaceable>Command was an ls or dir</replaceable>
-Error class = 0x0
-Error code = 0
-<replaceable>No errors</replaceable>
-Flags1 = 0x80
-Flags2 = 0x1
-Tree ID = 105
-Proc ID = 6075
-UID = 100
-MID = 30337
-Word Count = 10
-TotParamCnt=8
-TotDataCnt=163
-Res1=0
-ParamCnt=8
-ParamOff=55
-Res2=0
-DataCnt=163
-DataOff=63
-Res3=0
-Lsetup=0
-Param Data: (8 bytes)
-[000] 00 00 00 00 05 00 05 00 ........
-
-Data Data: (135 bytes)
-<replaceable>Actual directory contents:</replaceable>
-[000] 68 6F 6D 65 73 00 00 00 00 00 00 00 00 00 00 00 homes... ........
-[010] 64 00 00 00 70 75 62 6C 69 63 00 00 00 00 00 00 d...publ ic......
-[020] 00 00 00 00 75 00 00 00 74 65 6D 70 00 00 00 00 ....u... temp....
-[030] 00 00 00 00 00 00 00 00 76 00 00 00 49 50 43 24 ........ v...IPC$
-[040] 00 00 00 00 00 00 00 00 00 00 03 00 77 00 00 00 ........ ....w...
-[050] 64 6F 6E 68 61 6D 00 00 00 00 00 00 00 00 00 00 donham.. ........
-[060] 92 00 00 00 48 6F 6D 65 20 44 69 72 65 63 74 6F ....Home Directo
-[070] 72 69 65 73 00 00 00 49 50 43 20 53 65 72 76 69 ries...I PC Servi
-[080] 63 65 20 28 53 61 6D ce (Sam</programlisting>
-
-
-<para>This is more of the same debugging session as with the <emphasis>trace</emphasis> command; the listing of a directory. The options we used were <literal>-v</literal> (verbose), <literal>-i</literal> <literal>eth0</literal> to tell <emphasis>tcpdump</emphasis> the interface to listen on (an Ethernet port), and <literal>-s</literal> <literal>255</literal> to tell it to save the first 255 bytes of each packet instead of the default: the first 68. The option <literal>port</literal>
-<indexterm id="ch09-idx-954174-0"><primary>port not telnet option</primary></indexterm> <literal>not</literal> <literal>telnet</literal> is used to avoid screens of telnet traffic, since we were logged in to the server remotely. The <emphasis>tcpdump</emphasis> program actually has quite a number of options to filter just the traffic you want to look at. If you've used <emphasis>snoop</emphasis> or <emphasis>etherdump</emphasis>, they'll look vaguely familiar.</para>
-
-
-<para>You can download the modified <emphasis>tcpdump</emphasis>
-<indexterm id="ch09-idx-953518-0"><primary>downloads</primary><secondary>tcpdump utility</secondary></indexterm> from the Samba FTP server at <systemitem role="ftpurl">ftp://samba.anu.edu.au/pub/samba/tcpdump-smb</systemitem>. Other versions don't include support for the SMB protocol; if you don't see output such as that shown in the example, you'll need to<emphasis></emphasis>
-<indexterm id="ch09-idx-953513-0" class="endofrange" startref="ch09-idx-953802-0"/> use the SMB-enabled version.<indexterm id="ch09-idx-953481-0" class="endofrange" startref="ch09-idx-953478-0"/>
-<indexterm id="ch09-idx-953481-1" class="endofrange" startref="ch09-idx-953478-1"/></para>
-</sect3>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="9.2" id="ch09-29538">
-<title>The Fault Tree</title>
-
-
-<para>
-<indexterm id="ch09-idx-953543-0" class="startofrange"><primary>fault tree</primary></indexterm>
-<indexterm id="ch09-idx-953543-1" class="startofrange"><primary>how-tos, fault tree</primary></indexterm>The fault tree is for diagnosing and fixing problems that occur when you're installing and reconfiguring Samba. It's an expanded form of a trouble and diagnostic document that is part of the Samba distribution.</para>
-
-
-<para>
-<indexterm id="ch09-idx-953548-0"><primary>troubleshooting</primary><secondary>information to have on hand</secondary></indexterm>Before you set out to troubleshoot any part of the Samba suite, you should know the following information:</para>
-
-
-<itemizedlist>
-<listitem><para> Your client IP address (we use 192.168.236.10)</para></listitem>
-<listitem><para> Your server IP address (we use 192.168.236.86)</para></listitem>
-<listitem><para> The netmask for your network (typically 255.255.255.0)</para></listitem>
-<listitem><para> Whether the machines are all on the same subnet (ours are)</para></listitem>
-</itemizedlist>
-
-<para>For clarity, we've renamed the server in the following examples to <emphasis>server.example.com</emphasis>, and the client machine to <emphasis>client.example.com</emphasis>.</para>
-
-
-<sect2 role="" label="9.2.1" id="ch09-SECT-2.1">
-<title>How to use the fault tree</title>
-
-
-<para>
-<indexterm id="ch09-idx-953549-0"><primary>fault tree</primary><secondary>how to use</secondary></indexterm>Start the tests here, without skipping forward; it won't take long (about five minutes) and may actually save you time backtracking. Whenever a test succeeds, you will be given a section name and page number to which you can safely skip.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.2" id="ch09-SECT-2.2">
-<title>Troubleshooting Low-level IP </title>
-
-
-<para>
-<indexterm id="ch09-idx-953556-0" class="startofrange"><primary>services</primary><secondary>testing low-level</secondary></indexterm>The first series of tests is that of the low-level services that Samba needs in order to run. The tests in this section will verify that:</para>
-
-
-<itemizedlist>
-<listitem><para> The IP software works</para></listitem>
-<listitem><para> The Ethernet hardware works</para></listitem>
-<listitem><para> Basic name service is in place</para></listitem>
-</itemizedlist>
-
-<para>Subsequent sections will add TCP software, the Samba daemons <emphasis>smbd</emphasis> and <emphasis>nmbd</emphasis>, host-based access control, authentication and per-user access control, file services, and browsing. The tests are described in considerable detail in order to make them understandable by both technically oriented end users and experienced systems and network administrators.</para>
-
-
-<sect3 role="" label="9.2.2.1" id="ch09-SECT-2.2.1">
-<title>Testing the networking software with ping </title>
-
-
-<para>The first command to enter on both the server and the client is <literal>ping 127.0.0.1</literal>. This is the <firstterm>loopback</firstterm> <emphasis>address</emphasis> and testing it will indicate whether any networking support is functioning at all. On Unix, you can use <literal>ping</literal> <literal>127.0.0.1</literal> with the statistics option and interrupt it after a few lines. On Sun workstations, the command is typically <literal>/usr/etc/ping</literal> <literal>-s</literal> <literal>127.0.0.1</literal>; on Linux, just <literal>ping</literal> <literal>127.0.0.1</literal>. On Windows clients, run <literal>ping</literal> <literal>127.0.0.1</literal> in an MS-DOS window and it will stop by itself after four lines.</para>
-
-
-<para>Here is an example on a Linux server:</para>
-
-
-<programlisting>server% <emphasis role="bold">ping 127.0.0.1</emphasis>
-PING localhost: 56 data bytes 64 bytes from localhost (127.0.0.1):
-icmp-seq=0. time=1. ms 64 bytes from localhost (127.0.0.1):
-icmp-seq=1. time=0. ms 64 bytes from localhost (127.0.0.1):
-icmp-seq=2. time=1. ms ^C
-----127.0.0.1 PING Statistics----
-3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms)
-min/avg/max = 0/0/1</programlisting>
-
-
-<para>If you get "ping: no answer from..." or "100% packet loss," you have no IP networking at all installed on the machine. The address <literal>127.0.0.1</literal> is the internal loopback address and doesn't depend on the computer being physically connected to a network. If this test fails, you have a serious local problem. TCP/IP either isn't installed or is seriously misconfigured. See your operating system documentation if it is a Unix server. If it is a Windows client, follow the instructions in <link linkend="SAMBA-CH-3">Chapter 3</link>, to install networking support.</para>
-
-
-<tip role="ora">
-<para>If <emphasis>you're</emphasis> the network manager, some good references are Craig Hunt's <emphasis>TCP/IP Network Administration</emphasis>, Chapter 11, and Craig Hunt & Robert Bruce Thompson's new book, <emphasis>Windows NT TCP/IP Network Administration,</emphasis> both published by O'Reilly.</para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.2.2" id="ch09-20350">
-<title>Testing local name services with ping </title>
-
-
-<para>
-<indexterm id="ch09-idx-953658-0"><primary>name services</primary><secondary>testing</secondary></indexterm>Next, try to ping <literal>localhost</literal> on the Samba server. <literal>localhost</literal> is the conventional hostname for the 127.0.0.1 loopback, and it should resolve to that address. After typing <literal>ping</literal> <literal>localhost</literal>, you should see output similar to the following:</para>
-
-
-<programlisting>server% <emphasis role="bold">ping localhost</emphasis>
-PING localhost: 56 data bytes 64 bytes from localhost (127.0.0.1):
-icmp-seq=0. time=0. ms 64 bytes from localhost (127.0.0.1):
-icmp-seq=1. time=0. ms 64 bytes from localhost (127.0.0.1):
-icmp-seq=2. time=0. ms ^C</programlisting>
-
-
-<para>If this succeeds, try the same test on the client. Otherwise:</para>
-
-
-<itemizedlist>
-<listitem><para>If you get "unknown host: localhost," there is a problem resolving the host name localhost into a valid IP address. (This may be as simple as a missing entry in a local <emphasis>hosts</emphasis> file.) From here, skip down to <link linkend="ch09-23768">Section 9.2.8</link>.</para></listitem>
-<listitem><para>If you get "ping: no answer," or "100% packet loss," but pinging 127.0.0.1 worked, then name services is resolving to an address, but it isn't the correct one. Check the file or database (typically <filename>/etc/hosts</filename> on a Unix system) that the name service is using to resolve addresses to ensure that the entry is corrected.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.2.3" id="ch09-SECT-2.2.3">
-<title>Testing the networking hardware with ping </title>
-
-
-<para>
-<indexterm id="ch09-idx-953666-0"><primary>networking</primary><secondary>hardware for, testing</secondary></indexterm>Next, ping the server's network IP address from itself. This should get you exactly the same results as pinging 127.0.0.1:</para>
-
-
-<programlisting>server% <emphasis role="bold">ping 192.168.236.86</emphasis>
-PING 192.168.236.86: 56 data bytes 64 bytes from 192.168.236.86 (192.168.236.86):
-icmp-seq=0. time=1. ms 64 bytes from 192.168.236.86 (192.168.236.86):
-icmp-seq=1. time=0. ms 64 bytes from 192.168.236.86 (192.168.236.86):
-icmp-seq=2. time=1. ms ^C
-----192.168.236.86 PING Statistics----
-3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms)
-min/avg/max = 0/0/1</programlisting>
-
-
-<para>If this works on the server, repeat it for the client. Otherwise:</para>
-
-
-<itemizedlist>
-<listitem><para>If <literal>ping</literal> <replaceable>network_ip</replaceable> fails on either the server or client, but ping 127.0.0.1 works on that machine, you have a TCP/IP problem that is specific to the Ethernet network interface card on the computer. Check with the documentation for the network card or the host operating system to determine how to correctly configure it. However, be aware that on some operating systems, the <emphasis>ping</emphasis> command appears to work even if the network is disconnected, so this test doesn't always diagnose all hardware problems.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.2.4" id="ch09-84079">
-<title>Testing connections with ping</title>
-
-
-<para>
-<indexterm id="ch09-idx-953831-0" class="startofrange"><primary>connections</primary><secondary>testing</secondary></indexterm>Now, ping the server by name (instead of its IP address), once from the server and once from the client. This is the general test for working network hardware:</para>
-
-
-<programlisting>server% <emphasis role="bold">ping server</emphasis>
-PING server.example.com: 56 data bytes 64 bytes from server.example.com (192.168.236.86):
-icmp-seq=0. time=1. ms 64 bytes from server.example.com (192.168.236.86):
-icmp-seq=1. time=0. ms 64 bytes from server.example.com (192.168.236.86):
-icmp-seq=2. time=1. ms ^C
-----server.example.com PING Statistics----
-3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms)
-min/avg/max = 0/0/1</programlisting>
-
-
-<para>On Microsoft Windows, a ping of the server would look like <link linkend="ch09-91668">Figure 9.1</link>.</para>
-
-
-<figure label="9.1" id="ch09-91668">
-<title>Pinging the Samba server from a Windows client</title>
-
-<graphic width="502" depth="285" fileref="figs/sam.0901.gif"></graphic>
-</figure>
-
-<para>If successful, this test tells us five things:</para>
-
-
-<orderedlist>
-<listitem><para>The hostname (e.g., "server") is being found by your local nameserver.</para></listitem>
-<listitem><para>The hostname has been expanded to the full name (e.g., <emphasis>server.example.com</emphasis>).</para></listitem>
-<listitem><para>Its address is being returned (192.168.236.86).</para></listitem>
-<listitem><para>The client has sent the Samba server four 56-byte UDP/IP packets.</para></listitem>
-<listitem><para>The Samba server has replied to all four packets.</para></listitem>
-</orderedlist>
-
-<para>If this test isn't successful, there can be one of several things wrong with the network:</para>
-
-
-<itemizedlist>
-<listitem><para>First, if you get "ping: no answer," or "100% packet loss," you're not connecting to the network, the other machine isn't connecting, or one of the addresses is incorrect. Check the addresses that the <literal>ping</literal> command reports on each machine, and ensure that they match the ones you set up initially.</para>
-
-
-<para>If not, there is at least one mismatched address between the two machines. Try entering the command <literal>arp</literal> <literal>-a</literal>, and see if there is an entry for the other machine. The <literal>arp</literal> command stands for the Address Resolution Protocol. The <literal>arp</literal> <literal>-a</literal> command lists all the addresses known on the local machine. Here are some things to try:</para>
-
-
-<itemizedlist>
-<listitem><para>If you receive a message like "192.168.236.86 at (incomplete)," the Ethernet address of 192.168.236.86 is unknown. This indicates a complete lack of connectivity, and you're likely having a problem at the very bottom of the TCP/IP Network Administration protocol stack, at the Ethernet-interface layer. This is discussed in Chapters 5 and 6 of <citetitle>TCP/IP Network Administration </citetitle>(O'Reilly).</para></listitem>
-<listitem><para>If you receive a response similar to "server (192.168.236.86) at 8:0:20:12:7c:94," then the server has been reached at some time, or another machine is answering on its behalf. However, this means that <emphasis>ping</emphasis> should have worked: you may have an intermittent networking or ARP problem.</para></listitem>
-<listitem><para>If the IP address from ARP doesn't match the addresses you expected, investigate and correct the addresses manually.</para></listitem>
-</itemizedlist></listitem>
-<listitem><para>If each machine can ping itself but not another, something is wrong on the network between them.</para></listitem>
-<listitem><para>If you get "ping: network unreachable" or "ICMP Host Unreachable," then you're not receiving an answer and there is likely more than one network involved.</para>
-
-
-<para>In principle, you shouldn't try to troubleshoot SMB clients and servers on different networks. Try to test a server and client on the same network. The three tests that follow assume you might be testing between two networks:</para>
-
-
-<orderedlist>
-<listitem><para>First, perform the tests for no answer described earlier in this section. If this doesn't identify the problem, the remaining possibilities are the following: an address is wrong, your netmask is wrong, a network is down, or just possibly you've been stopped by a firewall.</para></listitem>
-<listitem><para>Check both the address and the netmasks on source and destination machines to see if something is obviously wrong. Assuming both machines really are on the same network, they both should have the same netmasks and <emphasis>ping</emphasis> should report the correct addresses. If the addresses are wrong, you'll need to correct them. If they're right, the programs may be confused by an incorrect netmask. See <link linkend="ch09-21203">Section 9.2.9.1</link>, later in this chapter.</para></listitem>
-<listitem><para>If the commands are still reporting that the network is unreachable and neither of the previous two conditions is in error, one network really may be unreachable from the other. This, too, is a network manager issue.</para></listitem>
-</orderedlist></listitem>
-
-<listitem><para>If you get "ICMP Administratively Prohibited," you've struck a firewall of some sort or a misconfigured router. You will need to speak to your network security officer.</para></listitem>
-<listitem><para>If you get "ICMP Host redirect," and <emphasis>ping</emphasis> reports packets getting through, this is generally harmless: you're simply being rerouted over the network.</para></listitem>
-<listitem><para>If you get a host redirect and no <emphasis>ping</emphasis> responses, you are being redirected, but no one is responding. Treat this just like the "Network unreachable" response and check your addresses and netmasks.</para></listitem>
-<listitem><para>If you get "ICMP Host Unreachable from gateway <emphasis>gateway_name</emphasis>," ping packets are being routed to another network, but the other machine isn't responding and the router is reporting the problem on its behalf. Again, treat this like a "Network unreachable" response and start checking addresses and netmasks.</para></listitem>
-<listitem><para>If you get "ping: unknown host <emphasis>hostname</emphasis>," your machine's name is not known. This tends to indicate a name-service problem, which didn't affect <literal>localhost</literal>. Have a look at <link linkend="ch09-23768">Section 9.2.8</link>," later in this chapter.</para></listitem>
-<listitem><para>If you get a partial success, with some pings failing but others succeeding, you either have an intermittent problem between the machines or an overloaded network. Ping for longer, and see if more than about 3 percent of the packets fail. If so, check it with your network manager: a problem may just be starting. However, if only a few fail, or if you happen to know some massive network program is running, don't worry unduly. Ping's ICMP (and UDP) are designed to drop occasional packets.</para></listitem>
-<listitem><para>If you get a response like "smtsvr.antares.net is alive" when you actually pinged <emphasis>client.example.com</emphasis>, you're either using someone else's address or the machine has multiple names and addresses. If the address is wrong, name service is clearly the culprit; you'll need to change the address in the name service database to refer to the right machine. This is discussed in <link linkend="ch09-23768">Section 9.2.8</link>," later in this chapter.</para>
-
-
-<para>Server machines are often <emphasis>multihomed</emphasis> : connected to more than one network, with different names on each net. If you are getting a response from an unexpected name on a multihomed server, look at the address and see if it's on your network (see <link linkend="ch09-21203">Section 9.2.9.1</link> later in this chapter). If so, you should use that address, rather than one on a different network, for both performance and reliability reasons.</para>
-
-
-<para>Servers may also have multiple names for a single Ethernet address, especially if they are web servers. This is harmless, if otherwise startling. You probably will want to use the official (and permanent) name, rather than an alias which may change.</para></listitem>
-<listitem><para>If everything works, but the IP address reported is 127.0.0.1, you have a name service error. This typically occurs when a operating system installation program generates an <filename>/etc/hosts</filename> line similar to <literal>127.0.0.1</literal> <literal>localhost</literal> <emphasis>hostnamedomainname</emphasis>. The localhost line should say <literal>127.0.0.1</literal> <literal>localhost</literal> or <literal>127.0.0.1</literal> <literal>localhost</literal> <literal>loghost</literal>. Correct it, lest it cause failures to negotiate who is the master browse list holder and who is the master browser. It can, also cause (ambiguous) errors in later tests.</para></listitem>
-</itemizedlist>
-
-<para>If this worked from the server, repeat it from the<indexterm id="ch09-idx-953672-0" class="endofrange" startref="ch09-idx-953831-0"/> client.<indexterm id="ch09-idx-953563-0" class="endofrange" startref="ch09-idx-953556-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.3" id="ch09-SECT-2.3">
-<title>Troubleshooting TCP</title>
-
-
-<para>
-<indexterm id="ch09-idx-953568-0"><primary>TCP/IP networking protocol</primary><secondary>TCP, troubleshooting</secondary></indexterm>Now that you've tested IP, UDP, and a name service with <emphasis>ping</emphasis>, it's time to test TCP. <emphasis>ping</emphasis> and browsing use ICMP and UDP; file and print services (shares) use TCP. Both depend on IP as a lower layer and all four depend on name services. Testing TCP is most conveniently done using the FTP (file transfer protocol) program.</para>
-
-
-<sect3 role="" label="9.2.3.1" id="ch09-78512">
-<title>Testing TCP with FTP </title>
-
-
-<para>Try connecting via FTP, once from the server to itself, and once from the client to the server:</para>
-
-
-<programlisting>server% <userinput>ftp server</userinput>
-Connected to server.example.com.
-220 server.example.com FTP server (Version 6.2/OpenBSD/Linux-0.10) ready.
- Name (server:davecb):
-331 Password required for davecb.
-Password:
-230 User davecb logged in.
- ftp><userinput> quit </userinput>
-221 Goodbye.</programlisting>
-
-
-<para>If this worked, skip to <link linkend="ch09-88968">Section 9.2.4</link>. Otherwise:</para>
-
-
-<itemizedlist>
-<listitem><para>If you received the message "server: unknown host," then nameservice has failed. Go back to the corresponding <emphasis>ping</emphasis> step, <link linkend="ch09-20350">Section 9.2.2.2</link>," and rerun those tests to see why name lookup failed.</para></listitem>
-<listitem><para>If you received "ftp: connect: Connection refused," the machine isn't running an FTP daemon. This is mildly unusual on Unix servers. Optionally, you might try this test by connecting to the machine using telnet instead of FTP; the messages are very similar and telnet uses TCP as well.</para></listitem>
-<listitem><para>If there was a long pause, then "ftp: connect: Connection timed out," the machine isn't reachable. Return to <link linkend="ch09-84079">Section 9.2.2.4</link>.</para></listitem>
-<listitem><para>If you received "530 Logon Incorrect," you connected successfully, but you've just found a different problem. You likely provided an incorrect username or password. Try again, making sure you use your username from the Unix server and type your password correctly.</para></listitem>
-</itemizedlist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.4" id="ch09-88968">
-<title>Troubleshooting Server Daemons</title>
-
-
-<para>
-<indexterm id="ch09-idx-953569-0" class="startofrange"><primary>daemons</primary><secondary>troubleshooting</secondary></indexterm>Once you've confirmed that TCP networking is working properly, the next step is to make sure the daemons are running on the server. This takes three separate tests because no single one of the following will decisively prove that they're working correctly.</para>
-
-
-<para>To be sure they're running, you need to find out if:</para>
-
-
-<orderedlist>
-<listitem><para>The daemon has started</para></listitem>
-<listitem><para>The daemons are registered or bound to a TCP/IP port by the operating system</para></listitem>
-<listitem><para>They're actually paying attention</para></listitem>
-</orderedlist>
-
-<sect3 role="" label="9.2.4.1" id="ch09-SECT-2.4.1">
-<title>Before you start</title>
-
-
-<para>First, check the logs. If you've started the daemons, the message "smbd version <emphasis>some_number</emphasis> started" should appear. If it doesn't, you will need to restart the Samba daemons.</para>
-
-
-<para>If the daemon reports that it has indeed started, look out for "bind failed on port 139 socket_addr=0 (Address already in use)". This means another daemon has been started on port 139 (<emphasis>smbd</emphasis> ). Also, <emphasis>nmbd</emphasis> will report a similar failure if it cannot bind to port 137. Either you've started them twice, or the <emphasis>inetd</emphasis> server has tried to provide a daemon for you. If it's the latter, we'll diagnose that in a moment.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.4.2" id="ch09-49239">
-<title>Looking for daemon processes with ps</title>
-
-
-<para>Next, you need to see if the daemons have been started. Use the <literal>ps</literal> command on the server with the <literal>long</literal> option for your machine type (commonly <literal>ps</literal> <literal>ax</literal> or <literal>ps</literal> <literal>-ef</literal>), and see if you have either <emphasis>smbd</emphasis> and <emphasis>nmbd</emphasis> already running. This often looks like the following:</para>
-
-
-<programlisting>server% <emphasis role="bold">ps ax</emphasis>
- PID TTY STAT TIME COMMAND
- 1 ? S 0:03 init [2]
- 2 ? SW 0:00 (kflushd)
-<emphasis>(...many lines of processes...)</emphasis>
- 234 ? S 0:14 nmbd -D3
- 237 ? S 0:11 smbd -D3
-<emphasis>(...more lines, possibly including more smbd lines...)</emphasis></programlisting>
-
-
-<para>This example illustrates that <emphasis>smbd</emphasis> and <emphasis>nmbd</emphasis> have already started as stand-alone daemons (the <literal>-D</literal> option) at log level 3.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.4.3" id="ch09-SECT-2.4.3">
-<title>Looking for daemons bound to ports</title>
-
-
-<para>Next, the daemons have to be registered with the operating system so they can get access to TCP/IP ports. The <literal>netstat</literal> command will tell you if this has been done. Run the command <literal>netstat</literal> <literal>-a</literal> on the server, and look for lines mentioning <literal>netbios</literal>, <literal>137</literal> or <literal>139</literal>:</para>
-
-
-<programlisting>server% <emphasis role="bold">netstat -a</emphasis>
-Active Internet connections (including servers)
-Proto Recv-Q Send-Q Local Address Foreign Address (state)
-udp 0 0 *.netbios- *.*
-tcp 0 0 *.netbios- *.*
-LISTEN
-tcp 8370 8760 server.netbios- client.1439
-ESTABLISHED</programlisting>
-
-
-<para>or:</para>
-
-
-<programlisting>server% <emphasis role="bold">netstat -a</emphasis>
-Active Internet connections (including servers)
-Proto Recv-Q Send-Q Local Address Foreign Address (state)
-udp 0 0 *.137 *.*
-tcp 0 0 *.139 *.*
-LISTEN
-tcp 8370 8760 server.139 client.1439
-ESTABLISHED</programlisting>
-
-
-<para>Among many similar lines, there should be at least one UDP line for <literal>*.netbios-</literal> or <literal>*.137</literal>. This indicates that the <emphasis>nmbd</emphasis> server is registered and (we hope) is waiting to answer requests. There should also be at least one TCP line mentioning <literal>*.netbios-</literal> or <literal>*.139</literal>, and it will probably be in the LISTENING state. This means that <emphasis>smbd</emphasis> is up and listening for connections.</para>
-
-
-<para>There may be other TCP lines indicating connections from <emphasis>smbd</emphasis> to clients, one for each client. These are usually in the ESTABLISHED state. If there are <emphasis>smbd</emphasis> lines in the ESTABLISHED state, <emphasis>smbd</emphasis> is definitely running. If there is only one line in the LISTENING state, we're not sure yet. If both of the lines is missing, a daemon has not succeeded in starting, so it's time to check the logs and then go back to <link linkend="SAMBA-CH-2">Chapter 2</link>.</para>
-
-
-<para>If there is a line for each client, it may be coming either from a Samba daemon or from the master IP daemon, <emphasis>inetd</emphasis>. It's quite possible that your <emphasis>inetd</emphasis> startup file contains lines that start Samba daemons without your realizing it; for instance, the lines may have been placed there if you installed Samba as part of a Linux distribution. The daemons started by <emphasis>inetd</emphasis> prevent ours from running. This problem typically produces log messages such as "bind failed on port 139 socket_addr=0 (Address already in use)."</para>
-
-
-<para>Check your <filename>/etc/inetd.conf</filename> ; unless you're intentionally starting the daemons from there, there <emphasis>must not</emphasis> be any <literal>netbios-ns</literal> (udp port 137) or <literal>netbios-ssn</literal> (tcp port 139) servers mentioned there. <emphasis>inetd</emphasis> is a daemon that provides numerous services, controlled by entries in <emphasis>/etc/inetd.conf</emphasis>. If your system is providing an SMB daemon via <emphasis>inetd</emphasis>, there will be lines like the following in the file:</para>
-
-
-<programlisting>netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
-netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd</programlisting>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.4.4" id="ch09-SECT-2.4.4">
-<title>Checking smbd with telnet</title>
-
-
-<para>Ironically, the easiest way to test that the <emphasis>smbd</emphasis>
-<indexterm id="ch09-idx-953678-0"><primary>smbd server, checking with telnet</primary></indexterm> server is actually working is to send it a meaningless message and see if it rejects it. Try something like the following:</para>
-
-
-<programlisting><userinput>echo hello | telnet localhost 139</userinput></programlisting>
-
-
-<para>This sends an erroneous but harmless message to <emphasis>smbd</emphasis>. The <literal>hello</literal> message is important. Don't try telneting to the port and typing just anything; you'll probably just hang your process. <literal>hello</literal>, however, is generally a harmless message.</para>
-
-
-<programlisting>server% <emphasis role="bold">echo "hello" | telnet localhost 139</emphasis>
-Trying
-Trying 192.168.236.86 ...
-Connected to localhost. Escape character is '^]'.
-Connection closed by foreign host.</programlisting>
-
-
-<para>If you get a "Connected" message followed by a "Connection closed" message, the test was a success. You have an <emphasis>smbd</emphasis> daemon listening on the port and rejecting improper connection messages. On the other hand, if you get "telnet: connect: Connection refused," there is probably no daemon present. Check the logs and go back to <link linkend="SAMBA-CH-2">Chapter 2</link>.</para>
-
-
-<para>Regrettably, there isn't an easy test for <emphasis>nmbd</emphasis>. If the <literal>telnet</literal> test and the <literal>netstat</literal> test both say that there is an <emphasis>smbd</emphasis> running, there is a good chance that <literal>netstat</literal> will also be correct about <emphasis>nmbd</emphasis> running.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.4.5" id="ch09-67494">
-<title>Testing daemons with testparm</title>
-
-
-<para>
-<indexterm id="ch09-idx-953679-0"><primary>daemons</primary><secondary>testing</secondary><tertiary>with testparm</tertiary></indexterm>Once you know there's a daemon, you should always run <literal>testparm</literal>, in hopes of getting:</para>
-
-
-<programlisting>server% <emphasis role="bold">testparm</emphasis>
-Load smb config files from /opt/samba/lib/smb.conf
-Processing section "[homes]"
-Processing section "[printers]" ...
-Processing section "[tmp]"
-Loaded services file OK. ...</programlisting>
-
-
-<para>The <literal>testparm</literal> program normally reports processing a series of sections, and responds with "Loaded services file OK" if it succeeds. If not, it will report one or more of the following messages, which will also appear in the logs as noted:</para>
-
-
-<variablelist>
-<varlistentry><term><emphasis>"Allow/Deny connection from account (n) to service"</emphasis></term>
-<listitem><para>A <emphasis>testparm</emphasis>-only message produced if you have valid/invalid user options set in your <emphasis>smb.conf</emphasis>. You will want to make sure that you are on the valid user list, and that root, bin, etc., are on the invalid user list. If you don't, you will not be able to connect, or folks who shouldn't <emphasis>will</emphasis> be able to.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><emphasis>"Warning: You have some share names that are longer than eight chars"</emphasis></term>
-<listitem><para>For anyone using Windows for Workgroups and older clients. They will fail to connect to shares with long names, producing an overflow message that sounds confusingly like a memory overflow.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"Warning: [name] service MUST be printable!"</term>
-<listitem><para>A printer share lacks a <literal>printable</literal> <literal>=</literal> <literal>yes</literal> option.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"No path in service name using [name]"</term>
-<listitem><para>A file share doesn't know which directory to provide to the user, or a print share doesn't know which directory to use for spooling. If no path is specified, the service will try to run with a path of <emphasis>/tmp</emphasis>, which may not be what you want.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"Note: Servicename is flagged unavailable"</term>
-<listitem><para>Just a reminder that you have used the <literal>available</literal> <literal>=</literal> <literal>no</literal> option in a share.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"Can't find include file [name]" </term>
-<listitem><para>A configuration file referred to by an <literal>include</literal> option did not exist. If you were including the file unconditionally, this is an error and probably a serious one: the share will not have the configuration you intended. If you were including it based one of the <literal>%</literal> variables, such as <literal>%a</literal> (architecture), you will need to decide if, for example, a missing Windows for Workgroups configuration file is a problem. It often isn't.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"Can't copy service name, unable to copy to itself"</term>
-<listitem><para>You tried to copy a <filename>smb.conf</filename> section into itself.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"Unable to copy service—source not found: [name]"</term>
-<listitem><para>Indicates a missing or misspelled section in a <literal>copy</literal> <literal>=</literal> option.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"Ignoring unknown parameter name" </term>
-<listitem><para>Typically indicates an obsolete, misspelled or unsupported option.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term>"Global parameter name found in service section" </term>
-<listitem><para>Indicates a global-only parameter has been used in an individual share. Samba will ignore the parameter.</para></listitem>
-</varlistentry>
-</variablelist>
-
-
-<para>After the <literal>testparm</literal> test, repeat it with (exactly) three parameters: the name of your <filename>smb.conf</filename> file, the name of your client, and its IP address:</para>
-
-
-<programlisting>testparm <replaceable>samba_directory</replaceable>/lib/smb.conf client 192.168.236.10</programlisting>
-
-
-<para>This will run one more test that checks the host name and address against <literal>host</literal> <literal>allow</literal> and <literal>host</literal> <literal>deny</literal> options and may produce the "Allow/Deny connection from account account_name" to service message for the client machine. This message indicates you have valid/invalid host options in your <filename>smb.conf</filename>, and they prohibit access from the client machine. Entering <literal>testparm</literal> <literal>/usr/local/lib/experimental.conf</literal> is also an effective way to test an experimental <filename>smb.conf</filename> file before putting it into production.<indexterm id="ch09-idx-953573-0" class="endofrange" startref="ch09-idx-953569-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.5" id="ch09-SECT-2.5">
-<title>Troubleshooting SMB Connections</title>
-
-
-<para>
-<indexterm id="ch09-idx-953578-0" class="startofrange"><primary>SMB (Server Message Block)</primary><secondary>troubleshooting connections</secondary></indexterm>Now that you know the servers are up, you need to make sure that they're running properly. We start with the <filename>smb.conf</filename> file in the <replaceable>samba_directory</replaceable><filename>/lib</filename> directory.</para>
-
-
-<sect3 role="" label="9.2.5.1" id="ch09-67928">
-<title>A minimal smb.conf file</title>
-
-
-<para>In the following tests, we assume you have a <literal>[temp]</literal> share suitable for testing, plus at least one account. An <filename>smb.conf</filename> file that includes just these is:</para>
-
-
-<programlisting>[global]
- workgroup = <replaceable>EXAMPLE</replaceable>
- security = user
- browsable = yes
- local master = yes
-[homes]
- guest ok = no
- browseble = no
-[temp]
- path = /tmp
- public = yes</programlisting>
-
-
-<para>A word of warning: the <literal>public</literal> <literal>=</literal> <literal>yes</literal> option in the <literal>[temp]</literal> share is just for testing. You probably don't want people without accounts to be able to store things on your Samba server, so you should comment it out when you're done.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.5.2" id="ch09-40595">
-<title>Testing locally with smbclient</title>
-
-
-<para>
-<indexterm id="ch09-idx-953682-0"><primary>SMB (Server Message Block)</primary><secondary>troubleshooting connections</secondary><tertiary>testing locally</tertiary></indexterm>The first test is to ensure the server can list its own services (shares). Run the command <literal>smbclient</literal> with a <literal>-L</literal> option of <literal>localhost</literal> to connect to itself, and a <literal>-U</literal> option of just <literal>%</literal> to specify the guest user. You should see the following:</para>
-
-
-<programlisting>server% <userinput>smbclient -L localhost -U% </userinput>
-Server time is Wed May 27 17:57:40 1998 Timezone is UTC-4.0
-Server=[localhost]
-User=[davecb]
-Workgroup=[EXAMPLE]
-Domain=[EXAMPLE]
- Sharename Type Comment
- --------- ----- ----------
- temp Disk
- IPC$ IPC IPC Service (Samba 1.9.18)
- homes Disk Home directories
-This machine does not have a browse list</programlisting>
-
-
-<para>If you received this output, move on to the next test, <link linkend="ch09-77154">Section 9.2.5.3</link>." On the other hand, if you receive an error, check the following:</para>
-
-
-<itemizedlist>
-<listitem><para>If you get "Get_hostbyname: unknown host localhost," either you've spelled its name wrong or there actually is a problem (which should have been seen back in <link linkend="ch09-20350">Section 9.2.2.2</link>) In the latter case, move on to <link linkend="ch09-23768">Section 9.2.8</link>.</para></listitem>
-<listitem><para>If you get "Connect error: Connection refused," the server machine was found, but it wasn't running an <emphasis>nmbd</emphasis> daemon. Skip back to <link linkend="ch09-88968">Section 9.2.4</link>," and retest the daemons.</para></listitem>
-<listitem><para>If you get the message "Your server software is being unfriendly," the initial session request packet got a garbage response from the server. The server may have crashed or started improperly. The common causes of this can be discovered by scanning the logs for:</para>
-
-
-<itemizedlist>
-<listitem><para>Invalid command-line parameters to <emphasis>smbd</emphasis>; see the <emphasis>smbd</emphasis> manual page.</para></listitem>
-<listitem><para>A fatal problem with the <filename>smb.conf</filename> file that prevents the startup of <emphasis>smbd</emphasis>. Always check your changes, as was done in <link linkend="ch09-67494">Section 9.2.4.5</link>.</para></listitem>
-<listitem><para>The directories where Samba keeps its log and lock files are missing.</para></listitem>
-<listitem><para>There is already a server on the port (139 for <emphasis>smbd</emphasis>, 137 for <emphasis>nmbd </emphasis>), preventing it from starting.</para></listitem>
-</itemizedlist></listitem>
-<listitem><para>If you're using <emphasis>inetd</emphasis> instead of stand-alone daemons, check your <filename>/etc/inetd.conf</filename> and <filename>/etc/services</filename> entries against their manual pages for errors as well.</para></listitem>
-<listitem><para>If you get a <literal>Password:</literal> prompt, your guest account is not set up properly. The <literal>%U</literal> option tells <emphasis>smbclient</emphasis> to do a "null login," which requires that the guest account be present but does not require it to have any privileges.</para></listitem>
-<listitem><para>If you get the message "SMBtconX failed. ERRSRV—ERRaccess," you aren't permitted access to the server. This normally means you have a <literal>valid</literal> <literal>hosts</literal> option that doesn't include the server, or an <literal>invalid</literal> <literal>hosts</literal> option that does. Recheck with the command <literal>testparm</literal> <literal>smb.conf</literal> <replaceable>your_hostname</replaceable> <replaceable>your_ip_address</replaceable> (see <link linkend="ch09-67494">Section 9.2.4.5</link>) and correct any unintended prohibitions.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.5.3" id="ch09-77154">
-<title>Testing connections with smbclient</title>
-
-
-<para>
-<indexterm id="ch09-idx-953689-0"><primary>SMB (Server Message Block)</primary><secondary>troubleshooting connections</secondary><tertiary>testing with smbclient</tertiary></indexterm>Run the command <literal>smbclient</literal> <literal>\\</literal><replaceable>server</replaceable><literal>\temp</literal>, which connects to your server's <filename>/tmp</filename> share, to see if you can connect to a file service. You should get the following response:</para>
-
-
-<programlisting>server% <emphasis role="bold">smbclient '\\server\temp'</emphasis>
-Server time is Tue May 5 09:49:32 1998 Timezone is UTC-4.0 Password:
-smb: \> <emphasis role="bold">quit</emphasis></programlisting>
-
-
-<itemizedlist>
-<listitem><para>If you get "Get_Hostbyname: Unknown host name," "Connect error: Connection refused," or "Your server software is being unfriendly," see <link linkend="ch09-40595">Section 9.2.5.2</link> for the diagnoses.</para></listitem>
-<listitem><para>If you get the message "servertemp: Not enough `\' characters in service," you likely didn't quote the address, so Unix stripped off backslashes. You can also write the command:</para>
-
-
-<programlisting>smbclient \\\\<replaceable>server</replaceable>\\temp</programlisting>
-
-
-<para>or:</para>
-
-
-<programlisting>smbclient //<replaceable>server</replaceable>/temp</programlisting></listitem>
-</itemizedlist>
-
-<para>Now, provide your Unix account password to the <literal>Password</literal> prompt. If you then get an <literal>smb\></literal> prompt, it worked. Enter <literal>quit</literal>, and continue on to <link linkend="ch09-97081">Section 9.2.5.4</link>." If you then get "SMBtconX failed. ERRSRV—ERRinvnetname," the problem can be any of the following:</para>
-
-
-<itemizedlist>
-<listitem><para>A wrong share name: you may have spelled it wrong, it may be too long, it may be in mixed case, or it may not be available. Check that it's what you expect with testparm (see <link linkend="ch09-67494">Section 9.2.4.5</link>.)</para></listitem>
-<listitem><para><literal>security</literal> <literal>=</literal> <literal>share</literal>, in which you may have to add <replaceable>-U your_account</replaceable> to the <emphasis>smbclient</emphasis> command, or know the password of a Unix account named temp.</para></listitem>
-<listitem><para>An erroneous username.</para></listitem>
-<listitem><para>An erroneous password.</para></listitem>
-<listitem><para>An <literal>invalid</literal> <literal>users</literal> or <literal>valid</literal> <literal>users</literal> option in your <emphasis>smb.conf</emphasis> file that doesn't allow your account to connect. Recheck with <literal>testparm</literal> <literal>smb.conf</literal> <replaceable>your_hostname your_ip_address</replaceable> (see <link linkend="ch09-67494">Section 9.2.4.5</link>).</para></listitem>
-<listitem><para>A <literal>valid</literal> <literal>hosts</literal> option that doesn't include the server, or an <literal>invalid</literal> <literal>hosts</literal> option that does. Also test this with <emphasis>testparm</emphasis>.</para></listitem>
-<listitem><para>A problem in authentication, such as if shadow passwords or the PAM (Password Authentication Module) is used on the server, but Samba is not compiled to use it. This is rare, but occasionally happens when a SunOS 4 Samba binary (no shadow passwords) is run without recompilation on a Solaris system (with shadow passwords).</para></listitem>
-<listitem><para>The <literal>encrypted</literal> <literal>passwords</literal> <literal>=</literal> <literal>yes</literal> option in the configuration file, but no password for your account in the <emphasis>smbpasswd</emphasis> file.</para></listitem>
-<listitem><para>You have a null password entry, either in Unix <filename>/etc/passwd</filename> or in the <emphasis>smbpasswd</emphasis> file.</para></listitem>
-<listitem><para>You are connecting to <literal>[temp]</literal>, and you do not have the <literal>guest</literal> <literal>ok</literal> <literal>=</literal> <literal>yes</literal> option in the <literal>[temp]</literal> section of the <emphasis>smb.conf</emphasis> file.</para></listitem>
-<listitem><para>You are connecting to <literal>[temp]</literal> before connecting to your home directory, and your guest account isn't set up correctly. If you can connect to your home directory and then connect to <literal>[temp]</literal>, that's the problem. See <link linkend="SAMBA-CH-2">Chapter 2</link> for more information on creating a basic Samba configuration file.</para>
-
-
-<para>A bad guest account will also prevent you from printing or browsing until after you've logged in to your home directory.</para></listitem>
-</itemizedlist>
-
-<para>There is one more reason for this failure that has nothing at all to do with passwords: the <literal>path</literal> <literal>=</literal> line in your <filename>smb.conf</filename> file may point somewhere that doesn't exist. This will not be diagnosed by <emphasis>testparm</emphasis>, and most SMB clients can't tell it from other types of bad user accounts. You will have to check it manually.</para>
-
-
-<para>Once you have connected to <literal>[temp]</literal> successfully, repeat the test, this time logging in to your home directory (e.g., map network drive <replaceable>server</replaceable><literal>\davecb</literal>) looking for failures in doing that. If you have to change anything to get that to work, re-test <literal>[temp]</literal> again afterwards.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.5.4" id="ch09-97081">
-<title>Testing connections with NET USE</title>
-
-
-<para>
-<indexterm id="ch09-idx-953696-0" class="startofrange"><primary>SMB (Server Message Block)</primary><secondary>troubleshooting connections</secondary><tertiary>testing with NET USE</tertiary></indexterm>Run the command <literal>net</literal> <literal>use</literal> <literal>*</literal> <literal>\</literal><replaceable>server</replaceable><literal>\temp</literal> on the DOS or Windows client to see if it can connect to the server. You should be prompted for a password, then receive the response "The command was completed successfully," as shown in <link linkend="ch09-99328">Figure 9.2</link>.</para>
-
-
-<figure label="9.2" id="ch09-99328">
-<title>Results of the NET USE command</title>
-
-<graphic width="502" depth="471" fileref="figs/sam.0902.gif"></graphic>
-</figure>
-
-<para>If that succeeded, continue with the steps in <link linkend="ch09-57065">Section 9.2.5.5</link>. Otherwise:</para>
-
-
-<itemizedlist>
-<listitem><para>If you get "The specified shared directory cannot be found," or "Cannot locate specified share name," the directory name is either misspelled or not in the <emphasis>smb.conf</emphasis> file. This message can also warn of a name in mixed case, including spaces, or is longer than eight characters.</para></listitem>
-<listitem><para>If you get "The computer name specified in the network path cannot be located," or "Cannot locate specified computer," the directory name has been misspelled, the name service has failed, there is a networking problem, or the <literal>hosts</literal> <literal>deny</literal> <literal>=</literal> option includes your host.</para>
-
-
-<itemizedlist>
-<listitem><para>If it is not a spelling mistake, you need to double back to at least <link linkend="ch09-77154">Section 9.2.5.3</link>, to investigate why it doesn't connect.</para></listitem>
-<listitem><para>If <emphasis>smbclient</emphasis> does work, it's a name service problem with the client name service, and you need to go forward to <link linkend="ch09-12446">Section 9.2.6.2</link>, and see if you can look up both client and server with <emphasis>nmblookup</emphasis>.</para></listitem>
-</itemizedlist></listitem>
-<listitem><para>If you get "The password is invalid for <literal>\</literal><replaceable>server</replaceable><literal>\</literal><replaceable>username</replaceable>," your locally cached copy on the client doesn't match the one on the server. You will be prompted for a replacement.</para></listitem>
-</itemizedlist>
-
-<tip role="ora">
-<para>Windows 95 and 98 clients keep a local <emphasis>password</emphasis> file, but it's really just a cached copy of the password it sends to Samba and NT servers to authenticate you. That's what is being prompted for here. You can still log on to a Windows machine without a password (but not to NT).</para>
-
-</tip>
-
-<itemizedlist>
-<listitem><para>
-If you provide your password, and it still fails, your password is not being matched on the server, you have a <literal>valid</literal> <literal>users</literal> or <literal>invalid</literal> <literal>users</literal> list denying you permission, NetBEUI is interfering, or the encrypted password problem described in the next paragraph exists.</para></listitem>
-<listitem><para>If your client is NT 4.0, NT 3.5 with Patch 3, Windows 95 with Patch 3, Windows 98 or any of these with Internet Explorer 4.0, these default to using Microsoft encryption for passwords (discussed in <link linkend="SAMBA-CH-6">Chapter 6</link>'s <link linkend="ch06-61393">Section 6.4</link>, along with the alternatives). In general, if you have installed a major Microsoft product recently, you may have applied an update and turned on encrypted passwords.</para></listitem>
-</itemizedlist>
-
-<tip role="ora">
-<para>Because of Internet Explorer's willingness to honor URLs such as <filename>file://somehost/somefile</filename> by making SMB connections, clients up to and including Windows 95 Patch Level 2 would happily send your password, in plaintext, to SMB servers anywhere on the Internet. This was considered a bad idea, and Microsoft quite promptly switched to using only encrypted passwords in the SMB protocol. All subsequent releases of their products have included this correction. Encrypted passwords aren't actually needed unless you're using Internet Explorer 4.0 without a firewall, so it's reasonable to keep using unencrypted passwords on your own networks.</para>
-
-</tip>
-
-<itemizedlist>
-<listitem><para>If you have a mixed-case password on Unix, the client is probably sending it in all one case. If changing your password to all one case works, this was the problem. Regrettably, all but the oldest clients support uppercase passwords, so Samba will try once with it in uppercase and once in lower case. If you wish to use mixed-case passwords, see the <literal>password</literal> <literal>level</literal> option in <link linkend="SAMBA-CH-6">Chapter 6</link> for a workaround.</para></listitem>
-<listitem><para>You may have a <literal>valid</literal> <literal>users</literal> problem, as tested with <emphasis>smbclient</emphasis> (see <link linkend="ch09-77154">Section 9.2.5.3</link>).</para></listitem>
-<listitem><para>You may have the NetBEUI protocol bound to the Microsoft client. This often produces long timeouts and erratic failures, and is known to have caused failures to accept passwords in the past.</para></listitem>
-</itemizedlist>
-
-<tip role="ora">
-<para>The term "bind" is used to mean connecting a piece of software to another in this case. The Microsoft SMB client is "bound to" TCP/IP in the bindings section of the TCP/IP properties panel under the Windows 95/98 Network icon in the Control Panel. TCP/IP in turn is bound to an Ethernet card. This is not the same sense of the word as binding an SMB daemon to a TCP/IP port.<indexterm id="ch09-idx-953703-0" class="endofrange" startref="ch09-idx-953696-0"/></para>
-
-</tip>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.5.5" id="ch09-57065">
-<title>Testing connections with Windows Explorer</title>
-
-
-<para>
-<indexterm id="ch09-idx-953710-0" class="startofrange"><primary>SMB (Server Message Block)</primary><secondary>troubleshooting connections</secondary><tertiary>testing withWindows Explorer</tertiary></indexterm>Start Windows Explorer or NT Explorer (not Internet Explorer), select Tools→Map Network Drive and specify \\<replaceable>server</replaceable>\<literal>temp</literal> to see if you can make Explorer connect to the <filename>/tmp</filename> directory. You should see a screen similar to the one in <link linkend="ch09-74414">Figure 9.3</link>. If so, you've succeeded and can skip to <link linkend="ch09-23573">Section 9.2.6</link>."</para>
-
-
-<figure label="9.3" id="ch09-74414">
-<title>Accessing the /tmp directory with Windows Explorer</title>
-
-<graphic width="502" depth="336" fileref="figs/sam.0903.gif"></graphic>
-</figure>
-
-<para>A word of caution: Windows Explorer and NT Explorer are rather poor as diagnostic tools: they do tell you that something's wrong, but rarely what it is. If you get a failure, you'll need to track it down with the NET USE command, which has far superior error reporting:</para>
-
-
-<itemizedlist>
-<listitem><para>If you get "The password for this connection that is in your password file is no longer correct," you may have any of the following:</para>
-
-
-<itemizedlist>
-<listitem><para>Your locally cached copy on the client doesn't match the one on the server.</para></listitem>
-<listitem><para>You didn't provide a username and password when logging on to the client. Most Explorers will continue to send a username and password of null, even if you provide a password.</para></listitem>
-<listitem><para>You have misspelled the password.</para></listitem>
-<listitem><para>You have an <literal>invalid</literal> <literal>users</literal> or <literal>valid</literal> <literal>users</literal> list denying permission.</para></listitem>
-<listitem><para>Your client is NT 4.0, NT 3.5 with Patch 3, Windows 95 with Patch 3, Windows 98, or any of these with Internet Explorer 4. They will all want encrypted passwords.</para></listitem>
-<listitem><para>You have a mixed-case password, which the client is supplying in all one case.</para></listitem>
-</itemizedlist></listitem>
-<listitem><para>If you get "The network name is either incorrect, or a network to which you do not have full access," or "Cannot locate specified computer," you may have any of the following:</para>
-
-
-<itemizedlist>
-<listitem><para> Misspelled name</para></listitem>
-<listitem><para> Malfunctioning service</para></listitem>
-<listitem><para> Failed share</para></listitem>
-<listitem><para> Networking problem</para></listitem>
-<listitem><para> Bad <literal>path</literal> line</para></listitem>
-<listitem><para> <literal>hosts</literal> <literal>deny</literal> line that excludes you</para></listitem>
-</itemizedlist></listitem>
-<listitem><para>If you get "You must supply a password to make this connection," the password on the client is out of synchronization with the server, or this is the first time you've tried from this client machine and the client hasn't cached it locally yet.</para></listitem>
-<listitem><para>If you get "Cannot locate specified share name," you have a wrong share name or a syntax error in specifying it, a share name longer than eight characters, or one containing spaces or in mixed case.</para></listitem>
-</itemizedlist>
-
-<para>Once you can reliably connect to the <literal>[temp]</literal> directory, try once again, this time using your home directory. If you have to change something to get home directories working, then retest with <literal>[temp]</literal>, and vice versa, as we showed in <link linkend="ch09-97081">Section 9.2.5.4</link>. As always, if Explorer fails, drop back to that section and debug it<indexterm id="ch09-idx-953717-0" class="endofrange" startref="ch09-idx-953710-0"/> there.<indexterm id="ch09-idx-953581-0" class="endofrange" startref="ch09-idx-953578-0"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.6" id="ch09-23573">
-<title>Troubleshooting Browsing </title>
-
-
-<para>
-<indexterm id="ch09-idx-953586-0" class="startofrange"><primary>browsing</primary><secondary>troubleshooting</secondary></indexterm>Finally, we come to browsing. This was left to last, not because it is hardest, but because it's both optional and partially dependent on a protocol that doesn't guarantee delivery of a packet. Browsing is hard to diagnose if you don't already know all the other services are running.</para>
-
-
-<para>Browsing is purely optional: it's just a way to find the servers on your net and the shares that they provide. Unix has nothing of the sort and happily does without. Browsing also assumes all your machines are on a local area network (LAN) where broadcasts are allowable.</para>
-
-
-<para>First, the browsing mechanism identifies a machine using the unreliable UDP protocol; then it makes a normal (reliable) TCP/IP connection to list the shares the machine provides.</para>
-
-
-<sect3 role="" label="9.2.6.1" id="ch09-96207">
-<title>Testing browsing with smbclient </title>
-
-
-<para>
-<indexterm id="ch09-idx-953724-0" class="startofrange"><primary>browsing</primary><secondary>troubleshooting</secondary><tertiary>with smbclient</tertiary></indexterm>We'll start with testing the reliable connection first. From the server, try listing its own shares via <emphasis>smbclient</emphasis> with a <literal>-L</literal> option of your server's name. You should get:</para>
-
-
-<programlisting>server% <userinput>smbclient -L server</userinput>
-Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0 Server time is Tue Apr 28 09:57:28 1998 Timezone is UTC-4.0
-Password:
-Domain=[EXAMPLE]
-OS=[Unix]
-Server=[Samba 1.9.18]
-Server=[server]
-User=[davecb]
-Workgroup=[EXAMPLE]
-Domain=[EXAMPLE]
- Sharename Type Comment
- --------- ---- -------
- cdrom Disk CD-ROM
- cl Printer Color Printer 1
- davecb Disk Home Directories
-
- This machine has a browse list:
- Server Comment
- --------- -------
- SERVER Samba 1.9.18
-
- This machine has a workgroup list:
- Workgroup Master
- --------- -------
- EXAMPLE SERVER</programlisting>
-
-
-<itemizedlist>
-<listitem><para>If you didn't get a Sharename list, the server is not allowing you to browse any shares. This should not be the case if you've tested any of the shares with Windows Explorer or the NET USE command. If you haven't done the <literal>smbclient</literal> <literal>-L</literal> <literal>localhost</literal> <literal>-U%</literal> test yet (see <link linkend="ch09-40595">Section 9.2.5.2</link>), do it now. An erroneous guest account can prevent the shares from being seen. Also, check the <filename>smb.conf</filename> file to make sure you do not have the option <literal>browsable</literal> <literal>=</literal> <literal>no</literal> anywhere in it: we suggest a minimal <filename>smb.conf</filename> file (see <link linkend="ch09-67928">Section 9.2.5.1</link>) for you to steal from. You need to have <literal>browseable</literal> enabled in order to be able to see at least the <literal>[temp]</literal> share.</para></listitem>
-<listitem><para>If you didn't get a browse list, the server is not providing information about the machines on the network. At least one machine on the net must support browse lists. Make sure you have <literal>local</literal> <literal>master</literal> <literal>=</literal> <literal>yes</literal> in the <filename>smb.conf</filename> file if you want Samba be the local master browser.</para></listitem>
-<listitem><para>If you got a browse list but didn't get <emphasis>/tmp</emphasis>, you probably have a <filename>smb.conf</filename> problem. Go back to <link linkend="ch09-67494">Section 9.2.4.5</link>."</para></listitem>
-<listitem><para>If you didn't get a workgroup list with your workgroup name in it, it is possible that your workgroup is set incorrectly in the <filename>smb.conf</filename> file.</para></listitem>
-<listitem><para>If you didn't get a workgroup list at all, ensure that <literal>workgroup</literal> <literal>=EXAMPLE</literal> is present in the <filename>smb.conf</filename> file.</para></listitem>
-<listitem><para>If you get nothing, try once more with the options <literal>-I</literal> <replaceable>ip_address</replaceable> <literal>-n</literal> <replaceable>netbios_name</replaceable> <literal>-W</literal> <replaceable>workgroup</replaceable> <literal>-d3</literal> with the NetBIOS and workgroup name in uppercase. (The <literal>-d</literal> <literal>3</literal> option sets the log /debugging level to 3.)</para></listitem>
-</itemizedlist>
-
-<para>If you're still getting nothing, you shouldn't have gotten this far. Double back to at least <link linkend="ch09-78512">Section 9.2.3.1</link>," or perhaps <link linkend="ch09-84079">Section 9.2.2.4</link>." On the other hand:</para>
-
-
-<itemizedlist>
-<listitem><para>If you get "SMBtconX failed. ERRSRV—ERRaccess," you aren't permitted access to the server. This normally means you have a <literal>valid</literal> <literal>hosts</literal> option that doesn't include the server, or an invalid hosts option that does.</para></listitem>
-<listitem><para> If you get "Bad password," then you presumably have one of the following:</para>
-
-
-<itemizedlist>
-
-<listitem><para> An incorrect <literal>hosts</literal> <literal>allow</literal> or <literal>hosts</literal> <literal>deny</literal> line</para></listitem>
-<listitem><para> An incorrect <literal>invalid</literal> <literal>users</literal> or <literal>valid</literal> <literal>users</literal> line</para></listitem>
-<listitem><para> A lowercase password and OS/2 or Windows for Workgroups clients</para></listitem>
-<listitem><para> A missing or invalid guest account</para></listitem>
-</itemizedlist>
-<para>Check what your guest account is (see <link linkend="ch09-40595">Section 9.2.5.2</link>) and verify your <filename>smb.conf</filename> file with <literal>testparm</literal> <literal>smb.conf</literal> <replaceable>your_hostname your_ip_address</replaceable> (see <link linkend="ch09-67494">Section 9.2.4.5</link>) and change or comment out any <literal>hosts</literal> <literal>allow</literal>, <literal>hosts</literal> <literal>deny</literal>, <literal>valid</literal> <literal>users</literal> or <literal>invalid</literal> <literal>users</literal> lines.</para></listitem>
-<listitem><para>If you get "Connection refused," the <emphasis>smbd</emphasis> server is not running or has crashed. Check that it's up, running, and listening to the network with <emphasis>netstat</emphasis>, see step <link linkend="ch09-67494">Section 9.2.4.5</link>."</para></listitem>
-<listitem><para>If you get "Get_Hostbyname: Unknown host name," you've made a spelling error, there is a mismatch between Unix and NetBIOS hostname, or there is a name service problem. Start nameservice debugging with <link linkend="ch09-97081">Section 9.2.5.4</link>." If this works, suspect a name mismatch and go to step <link linkend="ch09-35552">Section 9.2.10</link>."</para></listitem>
-<listitem><para>If you get "Session request failed," the server refused the connection. This usually indicates an internal error, such as insufficient memory to fork a process.</para></listitem>
-<listitem><para>If you get "Your server software is being unfriendly," the initial session request packet received a garbage response from the server. The server may have crashed or started improperly. Go back to <link linkend="ch09-40595">Section 9.2.5.2</link>," where the problem is first analyzed.</para></listitem>
-<listitem><para>If you suspect the server is not running, go back to <link linkend="ch09-49239">Section 9.2.4.2</link> to see why the server daemon isn't responding.<indexterm id="ch09-idx-953731-0" class="endofrange" startref="ch09-idx-953724-0"/></para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.6.2" id="ch09-12446">
-<title>Testing the server with nmblookup</title>
-
-
-<para>This will test the "advertising" system used for Windows name services and browsing. Advertising works by broadcasting one's presence or willingness to provide services. It is the part of browsing that uses an unreliable protocol (UDP), and works only on broadcast networks like Ethernets. The <emphasis>nmblookup</emphasis>
-<indexterm id="ch09-idx-953736-0"><primary>servers</primary><secondary>testing with nmblookup program</secondary></indexterm> program broadcasts name queries for the hostname you provide, and returns its IP address and the name of the machine, much like <emphasis>nslookup</emphasis> does with DNS. Here, the <literal>-d</literal> (debug- or log-level) option, and the <literal>-B</literal> (broadcast address) options direct queries to specific machines.</para>
-
-
-<para>First, we check the server from itself. Run <emphasis>nmblookup</emphasis> with a <literal>-B</literal> option of your server's name to tell it to send the query to the Samba server, and a parameter of <literal>_ _SAMBA_ _</literal> as the symbolic name to look up. You should get:</para>
-
-
-<programlisting>server% <emphasis role="bold">nmblookup -B</emphasis><replaceable>server</replaceable><emphasis role="bold"> _ _SAMBA_ _</emphasis>
-Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0
-Sending queries to 192.168.236.86 192.168.236.86 _ _SAMBA_ _</programlisting>
-
-
-<para>You should get the IP address of the server, followed by the name <literal>_ _SAMBA_ _ </literal>, which means that the server has successfully advertised that it has a service called <literal>_ _SAMBA_ _ </literal>, and therefore at least part of NetBIOS nameservice works.</para>
-
-
-<itemizedlist>
-<listitem><para>If you get "Name_query failed to find name _ _SAMBA_ _" you may have specified the wrong address to the <literal>-B</literal> option, or <emphasis>nmbd</emphasis> is not running. The <literal>-B</literal> option actually takes a broadcast address: we're using a machine-name to get a unicast address, and to ask server if it has claimed <literal>_ _SAMBA_ _</literal>.</para></listitem>
-<listitem><para>Try again with <literal>-B</literal><replaceable> ip_address</replaceable>, and if that fails too, <emphasis>nmbd</emphasis> isn't claiming the name. Go back briefly to "Testing daemons with testparm" to see if <emphasis>nmbd</emphasis> is running. If so, it may not claiming names; this means that Samba is not providing the browsing service—a configuratiuon problem. If that is the case, make sure that <filename>smb.conf</filename> doesn't contain the option <literal>browsing</literal> <literal>=</literal> <literal>no</literal>.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.6.3" id="ch09-32122">
-<title>Testing the client with nmblookup</title>
-
-
-<para>Next, check the IP address of the client from the server with <emphasis>nmblookup</emphasis>
-<indexterm id="ch09-idx-953737-0"><primary>clients, testing with nmblookup program</primary></indexterm> using <literal>-B</literal> option for the client's name and a parameter of <literal>'*'</literal> meaning "anything," as shown here:</para>
-
-
-<programlisting>server% <emphasis role="bold">nmblookup -B client '*'</emphasis>
-Sending queries to 192.168.236.10 192.168.236.10 *
-Got a positive name query response from 192.168.236.10 (192.168.236.10)</programlisting>
-
-
-<itemizedlist>
-<listitem><para>If you receive "Name-query failed to find name *," you have made a spelling mistake, or the client software on the PC isn't installed, started, or bound to TCP/IP. Double back to <link linkend="SAMBA-CH-2">Chapter 2</link> or <link linkend="SAMBA-CH-3">Chapter 3</link> and ensure you have a client installed and listening to the network.</para></listitem>
-</itemizedlist>
-
-<para>Repeat the command with the following options if you had any failures:</para>
-
-
-<itemizedlist>
-<listitem><para>If <literal>nmblookup</literal> <literal>-B</literal> <replaceable>client_IP_address</replaceable> succeeds but <literal>-B</literal> <replaceable>client_name</replaceable> fails, there is a name service problem with the client's name; go to <link linkend="ch09-23768">Section 9.2.8</link>."</para></listitem>
-<listitem><para>If <literal>nmblookup</literal> <literal>-B</literal> <literal>127.0.0.1'*'</literal> succeeds, but <literal>-B</literal> <replaceable>client_IP_address</replaceable> fails, there is a hardware problem and ping should have failed. See your network manager.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.6.4" id="ch09-98123">
-<title>Testing the network with nmblookup</title>
-
-
-<para>Run the command <emphasis>nmblookup</emphasis>
-<indexterm id="ch09-idx-953741-0" class="startofrange"><primary>networking</primary><secondary>nmblookup program, testing with</secondary></indexterm>
-<indexterm id="ch09-idx-953741-1" class="startofrange"><primary>nmblookup program</primary><secondary>networks, testing with</secondary></indexterm> again with a <literal>-d</literal> option (debug level) of 2 and a parameter of <literal>'*'</literal> again. This time we are testing the ability of programs (such as <emphasis>nmbd</emphasis> ) to use broadcast. It's essentially a connectivity test, done via a broadcast to the default broadcast address.</para>
-
-
-<para>A number of NetBIOS/TCP-IP hosts on the network should respond with "got a positive name query response" messages. Samba may not catch all of the responses in the short time it listens, so you won't always see all the SMB clients on the network. However, you should see most of them:</para>
-
-
-<programlisting>server% <emphasis role="bold">nmblookup -d 2 '*'</emphasis>
-Added interface ip=192.168.236.86 bcast=192.168.236.255 nmask=255.255.255.0 Sending queries to 192.168.236.255
-Got a positive name query response from 192.168.236.191 (192.168.236.191)
-Got a positive name query response from 192.168.236.228 (192.168.236.228)
-Got a positive name query response from 192.168.236.75 (192.168.236.75)
-Got a positive name query response from 192.168.236.79 (192.168.236.79)
-Got a positive name query response from 192.168.236.206 (192.168.236.206)
-Got a positive name query response from 192.168.236.207 (192.168.236.207)
-Got a positive name query response from 192.168.236.217 (192.168.236.217)
-Got a positive name query response from 192.168.236.72 (192.168.236.72) 192.168.236.86 *</programlisting>
-
-
-<para>However:</para>
-
-
-<itemizedlist>
-<listitem><para>If this doesn't give at least the client address you previously tested, the default broadcast address is wrong. Try <literal>nmblookup</literal> <literal>-B</literal> <literal>255.255.255.255</literal> <literal>-d</literal> <literal>2</literal> <literal>'*'</literal>, which is a last-ditch variant (a broadcast address of all ones). If this draws responses, the broadcast address you've been using before is wrong. Troubleshooting these is discussed in the <link linkend="ch09-45060">Section 9.2.9.2</link>, later in this chapter.</para></listitem>
-<listitem><para>If the address 255.255.255.255 fails too, check your notes to see if your PC and server are on different subnets, as discovered in <link linkend="ch09-84079">Section 9.2.2.4</link>." You should try to diagnose this with a server and client on the same subnet, but if you can't, you can try specifying the remote subnet's broadcast address with <literal>-B</literal>. Finding that address is discussed in the same place as troubleshooting broadcast addresses, in <link linkend="ch09-45060">Section 9.2.9.2</link>s," later in this chapter. The <literal>-B</literal> option will work if your router supports directed broadcasts; if it doesn't, you may be forced to test with a client on the same network.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.6.5" id="ch09-SECT-2.6.5">
-<title>Testing client browsing with net view</title>
-
-
-<para>
-<indexterm id="ch09-idx-953742-0"><primary>browsing</primary><secondary>client-side, testing with net view</secondary></indexterm>On the client, run the command <replaceable>net view \\server</replaceable> in a DOS window to see if you can connect to the client and ask what shares it provides. You should get back a list of available shares on the server, as shown in <link linkend="ch09-83710">Figure 9.4</link>.</para>
-
-
-<figure label="9.4" id="ch09-83710">
-<title>Using the net view command</title>
-
-<graphic width="502" depth="206" fileref="figs/sam.0904.gif"></graphic>
-</figure>
-
-<para>If you received this, continue with <link linkend="ch09-21713">Section 9.2.7</link>."</para>
-
-
-<itemizedlist>
-<listitem><para>If you get "Network name not found" for the name you just tested in <link linkend="ch09-32122">Section 9.2.6.3</link>," there is a problem with the client software itself. Double-check this by running <emphasis>nmblookup</emphasis> on the client; if it works and NET VIEW doesn't, the client is at fault.</para></listitem>
-<listitem><para>Of course, if <emphasis>nmblookup</emphasis> fails, there is a NetBIOS nameservice problem, as discussed in <link linkend="ch09-35552">Section 9.2.10</link>."</para></listitem>
-<listitem><para>If you get "You do not have the necessary access rights," or "This server is not configured to list shared resources," either your guest account is misconfigured (see <link linkend="ch09-40595">Section 9.2.5.2</link>), or you have a <literal>hosts</literal> <literal>allow</literal> or <literal>hosts</literal> <literal>deny</literal> line that prohibits connections from your machine. These problems should have been detected by the <emphasis>smbclient</emphasis> tests starting in <link linkend="ch09-96207">Section 9.2.6.1</link>."</para></listitem>
-<listitem><para>If you get "The specified computer is not receiving requests," you have misspelled the name, the machine is unreachable by broadcast (tested in "Testing the network with nmblookup"), or it's not running <emphasis>nmbd</emphasis>.</para></listitem>
-<listitem><para>If you get "Bad password error," you're probably encountering the Microsoft-encrypted password problem, as discussed in <link linkend="SAMBA-CH-6">Chapter 6</link>, with its corrections.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.6.6" id="ch09-SECT-2.6.6">
-<title>Browsing the server from the client</title>
-
-
-<para>
-<indexterm id="ch09-idx-953743-0"><primary>browsing</primary><secondary>server from client</secondary></indexterm>From the Network Neighborhood (File Manager in older releases), try to browse the server. Your Samba server should appear in the browse list of your local workgroup. You should be able to double click on the name of the server and get a list of shares, as illustrated in <link linkend="ch09-60004">Figure 9.5</link>.</para>
-
-
-<figure label="9.5" id="ch09-60004">
-<title>List of shares on a server</title>
-
-<graphic width="502" depth="202" fileref="figs/sam.0905.gif"></graphic>
-</figure>
-
-<itemizedlist>
-<listitem><para>If you get an "Invalid password" error with NT 4.0, NT 3.5 with Patch 3, Windows 95 with Patch 3, Windows 98 or any of these with Internet Explorer 4.0, it's most likely the encryption problem again. All of these clients default to using Microsoft encryption for passwords (see <link linkend="SAMBA-CH-6">Chapter 6</link>).</para></listitem>
-<listitem><para>If you receive an "Unable to browse the network" error, one of the following has ocurred:</para>
-
-
-<itemizedlist>
-<listitem><para>You have looked too soon, before the broadcasts and updates have completed; try waiting 30 seconds before re-attempting.</para></listitem>
-<listitem><para>There is a network problem you've not yet diagnosed.</para></listitem>
-<listitem><para>There is no browse master. Add the configuration option <literal>local</literal> <literal>master</literal> <literal>=</literal> <literal>yes</literal> to your <emphasis>smb.conf</emphasis> file.</para></listitem>
-<listitem><para>No shares are marked <literal>browsable</literal> in the <emphasis>smb.conf</emphasis> file.</para></listitem>
-
-</itemizedlist></listitem>
-
-<listitem><para>If you receive the message "\\server is not accessible," then:</para>
-
-
-<itemizedlist>
-<listitem><para> You have the encrypted password problem</para></listitem>
-<listitem><para> The machine really isn't accessible</para></listitem>
-<listitem><para> The machine doesn't support browsing<indexterm id="ch09-idx-953589-0" class="endofrange" startref="ch09-idx-953586-0"/></para></listitem>
-</itemizedlist></listitem>
-</itemizedlist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.7" id="ch09-21713">
-<title>Other Things that Fail </title>
-
-
-<para>If you've made it here, either the problem is solved or it's not one we've seen. The next sections cover troubleshooting tasks that are required to have the infrastructure to run Samba, not Samba itself.</para>
-
-
-<sect3 role="" label="9.2.7.1" id="ch09-SECT-2.7.1">
-<title>Not logging on</title>
-
-
-<para>
-<indexterm id="ch09-idx-953594-0"><primary>log files/logging</primary><secondary>troubleshooting</secondary></indexterm>An occasional problem is forgetting to log in to the client or logging in as a wrong (account-less) person. The former is not diagnosed at all: Windows tries to be friendly and lets you on. Locally! The only warning of the latter is that Windows welcomes you and asks about your new account. Either of these leads to repeated refusals to connect and endless requests for passwords. If nothing else seems to work, try logging out or shutting down and logging in again.</para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.8" id="ch09-23768">
-<title>Troubleshooting Name Services</title>
-
-
-<para>
-<indexterm id="ch09-idx-953595-0" class="startofrange"><primary>name services</primary><secondary>troubleshooting</secondary></indexterm>This section looks at simple troubleshooting of all the name services that you will encounter, but only for the common problems that affect Samba.</para>
-
-
-<para>There are several good references for troubleshooting particular name services: Paul Albitz and Cricket Liu's <emphasis>DNS and Bind</emphasis> covers the Domain Name Service (DNS), Hal Stern's <emphasis>NFS and NIS</emphasis> (both from O'Reilly) covers NIS ("Yellow pages") while WINS (Windows Internet Name Service), <filename>hosts/LMHOSTS</filename> files and NIS+ are best covered by their respective vendor's manuals.</para>
-
-
-<para>The problems addressed in this section are:</para>
-
-
-<itemizedlist>
-<listitem><para>Identifying name services</para></listitem>
-<listitem><para>A hostname can't be looked up</para></listitem>
-<listitem><para>The long (FQDN) form of a hostname works but the short form doesn't</para></listitem>
-<listitem><para>The short form of the name works, but the long form doesn't</para></listitem>
-<listitem><para>A long delay ocurrs before the expected result</para></listitem>
-</itemizedlist>
-
-<sect3 role="" label="9.2.8.1" id="ch09-SECT-2.8.1">
-<title>Identifying what's in use</title>
-
-
-<para>
-<indexterm id="ch09-idx-953744-0"><primary>name services</primary><secondary>identifying what is in use</secondary></indexterm>First, see if both the server and the client are using DNS, WINS, NIS, or <filename>hosts</filename> files to look up IP addresses when you give them a name. Each kind of machine will have a different preference:</para>
-
-
-<itemizedlist>
-<listitem><para>Windows 95 and 98 machines will look in WINS and <filename>LMHOSTS</filename> files first, then broadcast, and finally try DNS and <filename>hosts</filename> files.</para></listitem>
-<listitem><para>NT will look in WINS, then broadcast, LMHOSTS files, and finally <filename>hosts</filename> and DNS.</para></listitem>
-<listitem><para>Windows programs using the WINSOCK standard (like PC-NFSs) will use hosts files, DNS, WINS, and then broadcast. Don't assume that if a different program's name service works, the SMB client program's name service will!</para></listitem>
-<listitem><para>Samba daemons will use <filename>LMHOSTS</filename>, WINS, the Unix host's preference, and then broadcast.</para></listitem>
-<listitem><para>Unix hosts can be configured to use any combination of DNS, <filename>hosts</filename> files, and NIS and NIS+, generally in any order.</para></listitem>
-</itemizedlist>
-
-<para>We recommend that the client machines be configured to use WINS and DNS, the Samba daemons to use WINS and DNS, and the Unix server to use DNS. You'll have to look at your notes and the actual machines to see which is in use.</para>
-
-
-<para>On the clients, the name services are all set in the TCP/IP Properties panel of the Networking Control Panel, as discussed in <link linkend="SAMBA-CH-3">Chapter 3</link>. You may need to check there to see what you've actually turned on. On the server, see if an <filename>/etc/resolv.conf</filename> file exists. If it does, you're using DNS. You may be using the others as well, though. You'll need to check for NIS and combinations of services.</para>
-
-
-<para>Check for an <filename>/etc/nsswitch.conf</filename> file on Solaris and other System V Unix operating systems. If you have one, look for a line that begins <literal>host</literal>:, followed by one or more of <literal>files</literal>, <literal>bind</literal>, <literal>nis</literal> or <literal>nis+</literal>. These are the name services to use, in order, with optional extra material in square brackets. <emphasis>files</emphasis> stands for using <emphasis>hosts</emphasis> files, while <emphasis>bind</emphasis> (the Berkeley Internet Name Daemon) stands for using DNS.</para>
-
-
-<para>If the client and server differ, the first thing to do is to get them in sync. Clients can only use only DNS, WINS, <emphasis>hosts</emphasis> files and <emphasis>lmhosts</emphasis> files, not NIS or NIS+. Servers can use <emphasis>hosts</emphasis> files, DNS, and NIS or NIS+, but not WINS—even if your Samba server provides WINS services. If you can't get all the systems to use the same services, you'll have to carefully check the server and the client for the same data.</para>
-
-
-<para>Samba 2.0 (and late 1.9 versions) added a <literal>-R</literal><option> </option>(resolve order) option to <emphasis>smbclient</emphasis>. If you want to troubleshoot WINS, for example, you'd say:</para>
-
-
-<programlisting>smbclient -L <replaceable>server</replaceable> -R wins</programlisting>
-
-
-<para>The possible settings are <literal>hosts</literal> (which means whatever the Unix machine is using, not just<filename> /etc/hosts</filename> files), <literal>lmhosts</literal>, <literal>wins</literal> and <literal>bcast</literal> (broadcast).</para>
-
-
-<para>In the following sections, we use the term <emphasis>long name</emphasis> for a fully-qualified domain name (FQDN), like <literal>server.example.com </literal>, and the term <emphasis>short name</emphasis> for the host part of a FQDN, like <literal>server</literal>.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.8.2" id="ch09-SECT-2.8.2">
-<title>Cannot look up hostnames</title>
-
-
-<para> <indexterm id="ch09-idx-953745-0"><primary>hostnames</primary><secondary>troubleshooting</secondary><tertiary>lookup</tertiary></indexterm>Try the following:</para>
-
-
-<itemizedlist>
-<listitem><para>In DNS:</para>
-
-
-<para>Run <literal>nslookup</literal> <replaceable>name</replaceable>. If this fails, look for a <filename>resolv.conf</filename> error, a downed DNS server, or a short/long name problem (see the next section). Try the following:</para>
-
-
-<itemizedlist>
-<listitem><para>Your <filename>/etc/resolv.conf</filename> should contain one or more name-server lines, each with an IP address. These are the addresses of your DNS servers.</para></listitem>
-<listitem><para>ping each of the server addresses you find. If this fails for one, suspect the machine. If it fails for each, suspect your network.</para></listitem>
-<listitem><para>Retry the lookup using the full domain name (e.g., <emphasis>server.example.com</emphasis>) if you tried the short name first, or the short name if you tried the long name first. If results differ, skip to the next section.</para></listitem>
-</itemizedlist></listitem>
-<listitem><para>In Broadcast/ WINS:</para>
-
-
-<para>Broadcast/ WINS does only short names such as <literal>server</literal>, (not long ones, such as <literal>server.example.com)</literal>. Run <literal>nmblookup</literal> <literal>-S</literal> <replaceable>server</replaceable>.<replaceable> </replaceable>This reports everything broadcast has registered for the name. In our example, it looks like this:</para></listitem>
-</itemizedlist>
-
-<programlisting>Looking up status of 192.168.236.86
-received 10 names
- SERVER <00> - M <ACTIVE>
- SERVER <03> - M <ACTIVE>
- SERVER <1f> - M <ACTIVE>
- SERVER <20> - M <ACTIVE>
- .._ _MSBROWSE_ _.<01> - <GROUP> M <ACTIVE>
- MYGROUP <00> - <GROUP> M <ACTIVE>
- MYGROUP <1b> - M <ACTIVE>
- MYGROUP <1c> - <GROUP> M <ACTIVE>
- MYGROUP <1d> - M <ACTIVE>
- MYGROUP <1e> - <GROUP> M <ACTIVE></programlisting>
-
-
-<itemizedlist>
-<listitem><para>
-The required entry is <literal>SERVER</literal> <literal><00></literal>, which identifies <replaceable>server</replaceable> as being this machine's NetBIOS name. You should also see your workgroup mentioned one or more times. If these lines are missing, Broadcast/WINS cannot look up names and will need attention.</para></listitem>
-</itemizedlist>
-
-<tip role="ora">
-<para>The numbers in angle brackets in the previous output identify NetBIOS names as being workgroups, workstations, and file users of the messenger service, master browsers, domain master browsers, domain controllers and a plethora of others. We primarily use <literal><00></literal> to identify machine and workgroup names and <literal><20></literal> to identify machines as servers. The complete list is available at <systemitem role="url">http://support.microsoft.com/support/kb/articles/q163/4/09.asp</systemitem>.</para>
-
-</tip>
-
-<itemizedlist>
-<listitem><para>In NIS:</para>
-
-
-<para>Try <literal>ypmatch</literal> <literal>name</literal> <literal>hosts</literal>. If this fails, NIS is down. Find out the NIS server's name by running <emphasis>ypwhich</emphasis>, and ping the machine it to see if it's accessible.</para></listitem>
-<listitem><para>In NIS+:</para>
-
-
-<para>If you're running NIS+, try <literal>nismatch</literal> <literal>name</literal> <literal>hosts</literal>. If this fails, NIS is down. Find out the NIS server's name by running <emphasis>niswhich</emphasis>, and ping that machine to see if it's accessible.</para></listitem>
-<listitem><para>In <filename>hosts</filename> files:</para>
-
-
-<para>Inspect <filename>/etc/hosts</filename> on the client (<literal>C:\WINDOWS\HOSTS</literal>). Each line should have an IP number and one or more names, the primary name first, then any optional aliases. An example follows:</para></listitem>
-</itemizedlist>
-
-<programlisting>127.0.0.1 localhost
- 192.168.236.1 dns.svc.example.com
- 192.168.236.10 client.example.com client
- 192.168.236.11 backup.example.com loghost
- 192.168.236.86 server.example.com server
- 192.168.236.254 router.svc.example.com</programlisting>
-
-
-<itemizedlist>
-<listitem><para>
-On Unix, <literal>localhost</literal> should always be 127.0.0.1, although it may be just an alias for a hostname on the PC. On the client, check that there are no <literal>#XXX</literal> directives at the ends of the lines; these are LAN Manager/NetBIOS directives, and should appear only in <emphasis>LMHOSTS</emphasis> files (<literal>C:\WINDOWS\LMHOSTS</literal>).</para></listitem>
-<listitem><para>In <emphasis>LMHOSTS</emphasis> files:</para>
-
-
-<para>This file is a local source for LAN Manager (NetBIOS) names. It has a format very similar to <filename>/etc/hosts</filename> files, but does not support long-form domain names (e.g., <literal>server.example.com</literal>), and may have a number of optional <literal>#XXX</literal> directives following the names. Note there usually is a <emphasis>lmhosts.sam</emphasis> (for sample) file in <literal>C:\WINDOWS</literal>, but it's not used unless renamed to <literal>C:\WINDOWS\LMHOSTS</literal>.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.8.3" id="ch09-SECT-2.8.3">
-<title>Long and short hostnames</title>
-
-
-<para>
-<indexterm id="ch09-idx-953754-0"><primary>hostnames</primary><secondary>troubleshooting</secondary><tertiary>long/short</tertiary></indexterm>Where the long (FQDN) form of a hostname works but the short name doesn't (for example, <literal>client.example.com</literal> works but <literal>client</literal> doesn't), consider the following:</para>
-
-
-<itemizedlist>
-<listitem><para>DNS:</para>
-
-
-<para>This usually indicates there is no default domain in which to look up the short names. Look for a <literal>default</literal> line in <filename>/etc/resolv.conf</filename> on the Samba server with your domain in it, or a <literal>search</literal> line with one or more domains in it. One or the other may need to be present to make short names usable; which one depends on vendor and version of the DNS resolver. Try adding <literal>domain</literal> <replaceable>your domain</replaceable> to <filename>resolv.conf</filename> and ask your network or DNS administrator what should have been in the file.</para></listitem>
-<listitem><para>Broadcast/WINS:</para>
-
-
-<para>Broadcast/WINS doesn't support long names; it won't suffer from this problem.</para></listitem>
-<listitem><para>NIS:</para>
-
-
-<para>Try the command <literal>ypmatch</literal> <literal>hostname</literal> <literal>hosts</literal>. If you don't get a match, your tables don't include short names. Speak to your network manager; short names may be missing by accident, or may be unsupported as a matter of policy. Some sites don't ever use (ambiguous) short names.</para></listitem>
-<listitem><para>NIS+ :</para>
-
-
-<para>Try <literal>nismatch</literal> <replaceable>hostname</replaceable> <literal>hosts</literal>, and treat failure exactly as with NIS above.</para></listitem>
-<listitem><para><emphasis>hosts:</emphasis></para>
-
-
-<para>If the short name is not in <filename>/etc/hosts</filename>, consider adding it as an alias. Avoid, if you can, short names as primary names (the first one on a line). Have them as aliases if your system permits.</para></listitem>
-<listitem><para><filename>LMHOSTS</filename>:</para>
-
-
-<para>LAN Manager doesn't support long names, so it won't suffer from this problem.</para></listitem>
-</itemizedlist>
-
-<para>On the other hand, if the short form of the name works and the long doesn't, consider the following:</para>
-
-
-<itemizedlist>
-<listitem><para>DNS:</para>
-
-
-<para>This is bizarre; see your network or DNS administrator, as this is probably a DNS setup bug.</para></listitem>
-<listitem><para>Broadcast/WINS:</para>
-
-
-<para>This is a normal bug; Broadcast/WINS can't use the long form. Optionally, consider DNS. Microsoft has stated that they will switch to DNS, though it's not providing name types like <00>.</para></listitem>
-<listitem><para>NIS:</para>
-
-
-<para>If you can use <literal>ypmatch</literal> to look up the short form but not the long, consider adding the long form to the table as at least an alias.</para></listitem>
-<listitem><para>NIS+:</para>
-
-
-<para>Same as NIS, except you use <literal>nismatch</literal> instead of <literal>ypmatch</literal> to look up names.</para></listitem>
-<listitem><para><filename>hosts:</filename></para>
-
-
-<para>Add the long name as at least an alias, and preferably as the primary form. Also consider using DNS if it's practical.</para></listitem>
-<listitem><para><filename>LMHOSTS</filename>:</para>
-
-
-<para>This is a normal bug. LAN Manager can't use the long form; consider switching to DNS or <filename>hosts</filename>.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.8.4" id="ch09-SECT-2.8.4">
-<title>Unusual delays</title>
-
-
-<para>
-<indexterm id="ch09-idx-953755-0"><primary>delays, troubleshooting</primary></indexterm>When there is a long delay before the expected result:</para>
-
-
-<itemizedlist>
-<listitem><para>DNS:</para>
-
-
-<para>Test the same name with the <command>nslookup</command> command on the machine (client or server) that is slow. If <command>nslookup</command> is also slow, you have a DNS problem. If it's slower on a client, you have too many protocols bound to the Ethernet card. Eliminate NetBEUI, which is infamously slow, and optionally, Novel, assuming you don't need them. This is especially important on Windows 95, which is particularly sensitive to excess protocols.</para></listitem>
-<listitem><para>Broadcast/ WINS:</para>
-
-
-<para>Test the client using <literal>nmblookup</literal>, and if it's faster, you probably have the protocols problem as mentioned in the previous item.</para></listitem>
-<listitem><para>NIS:</para>
-
-
-<para>Try <literal>ypmatch</literal>, and if it's slow, report the problem to your network manager.</para></listitem>
-<listitem><para>NIS+:</para>
-
-
-<para>Try <literal>nismatch</literal>, similarly.</para></listitem>
-<listitem><para><emphasis>hosts</emphasis>:</para>
-
-
-<para><emphasis>hosts</emphasis> files, if of reasonable size, are always fast. You probably have the protocols problem mentioned under DNS, above.</para></listitem>
-<listitem><para><emphasis>LMHOSTS</emphasis>:</para>
-
-
-<para>This is not a name lookup problem; <emphasis>LMHOSTS</emphasis> files are as fast as <emphasis>hosts</emphasis> files.</para></listitem>
-</itemizedlist>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.8.5" id="ch09-SECT-2.8.5">
-<title>Localhost issues</title>
-
-
-<para>
-<indexterm id="ch09-idx-953756-0"><primary>localhost</primary><secondary>troubleshooting</secondary></indexterm>When a localhost isn't 127.0.0.1, try the following:</para>
-
-
-<itemizedlist>
-<listitem><para>DNS:</para>
-
-
-<para>There is probably no record for <literal>localhost.</literal> <literal>A</literal> <literal>127.0.0.1</literal>. Arrange to add one, and a reverse entry, <literal>1.0.0.127.IN-ADDR.ARPA</literal> <literal>PTR</literal> <literal>127.0.0.1</literal>.</para></listitem>
-<listitem><para>Broadcast/WINS:</para>
-
-
-<para>Not applicable.</para></listitem>
-<listitem><para>NIS:</para>
-
-
-<para>If <literal>localhost</literal> isn't in the table, add it.</para></listitem>
-<listitem><para>NIS+:</para>
-
-
-<para>If <literal>localhost</literal> isn't in the table, add it.</para></listitem>
-<listitem><para><filename>hosts:</filename></para>
-
-
-<para>Add a line is the <emphasis>hosts</emphasis> file that says <literal>127.0.0.1</literal> <literal>localhost</literal></para></listitem>
-<listitem><para><filename>LMHOSTS</filename>:</para>
-
-
-<para>Not applicable.<indexterm id="ch09-idx-953603-0" class="endofrange" startref="ch09-idx-953595-0"/></para></listitem>
-</itemizedlist>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.9" id="ch09-SECT-2.9">
-<title>Troubleshooting Network Addresses</title>
-
-
-<para>A number of common problems are caused by incorrect Internet address routing or the incorrect assignment of addresses. This section helps you determine what your addresses are.</para>
-
-
-<sect3 role="" label="9.2.9.1" id="ch09-21203">
-<title>Netmasks</title>
-
-
-<para>
-<indexterm id="ch09-idx-953973-0" class="startofrange"><primary>network addresses</primary><secondary>troubleshooting</secondary></indexterm>
-<indexterm id="ch09-idx-953973-1" class="startofrange"><primary>IP address</primary></indexterm>
-<indexterm id="ch09-idx-953973-2" class="startofrange"><primary>troubleshooting</primary><secondary>network addresses</secondary></indexterm>The <indexterm id="ch09-idx-953974-0"><primary>netmasks</primary><secondary>troubleshooting</secondary></indexterm>netmasks tell each machine which addresses can be reached directly (are on your local network) and which addresses require forwarding packets through a router. If the netmask is wrong, the machines will make one of two mistakes. One is to try to route local packets via a router, which is an expensive way to waste time—it may work reasonably fast, it may run slowly, or it may fail utterly. The second mistake is to fail to send packets for a remote machine to the router, which will prevent them from being forwarded to the remote machine.</para>
-
-
-<para>The netmask is a number like an IP address, with one-bits for the network part of an address and zero-bits for the host portion. The netmask is literally used to mask off parts of the address inside the TCP/IP code. If the mask is 255.255.0.0, the first 2 bytes are the network part and the last 2 are the host part. More common is 255.255.255.0, in which the first 3 bytes are the network part and the last one is the host part.</para>
-
-
-<para>For example, let's say your IP address is 192.168.0.10 and the Samba server is 192.168.236.86. If your netmask happens to be 255.255.255.0, the network part of the addresses is the first 3 bytes and the host part is the last byte. In this case, the network parts are different, and the machines are on different networks:</para>
-
-
-<informaltable>
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Network Part</para></entry>
-
-<entry colname="col2"><para>Host Part</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>192 168 000</para></entry>
-
-<entry colname="col2"><para>10</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>192 168 235</para></entry>
-
-<entry colname="col2"><para>86</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>If your netmask happens to be 255.255.0.0, the network part is just the first two bytes. In this case, the network parts match and so the two machines are on the same network:</para>
-
-
-
-<informaltable>
-<tgroup cols="2">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<thead>
-<row>
-
-<entry colname="col1"><para>Network Part</para></entry>
-
-<entry colname="col2"><para>Host Part</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para>192 168</para></entry>
-
-<entry colname="col2"><para>000 10</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para>192 168</para></entry>
-
-<entry colname="col2"><para>236 86</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>Of course, if your netmask says one thing and your network manager says another, the netmask is wrong.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.9.2" id="ch09-45060">
-<title>Broadcast addresses</title>
-
-
-<para>The <indexterm id="ch09-idx-953758-0"><primary>broadcast addresses, troubleshooting</primary></indexterm>broadcast address is a normal address, with the hosts part all one-bits. It means "all hosts on your network." You can compute it easily from your netmask and address: take the address and put one-bits in it for all the bits that are zero at the end of the netmask (the host part). The following table illustrates this:</para>
-
-
-<informaltable>
-<tgroup cols="3">
-<colspec colnum="1" colname="col1"/>
-<colspec colnum="2" colname="col2"/>
-<colspec colnum="3" colname="col3"/>
-<thead>
-<row>
-
-<entry colname="col1"></entry>
-
-<entry colname="col2"><para>Network Part</para></entry>
-
-<entry colname="col3"><para>Host Part</para></entry>
-
-</row>
-
-</thead>
-
-<tbody>
-<row>
-
-<entry colname="col1"><para><emphasis role="bold">IP address</emphasis></para></entry>
-
-<entry colname="col2"><para>192 168 236</para></entry>
-
-<entry colname="col3"><para>86</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis role="bold">Netmask</emphasis></para></entry>
-
-<entry colname="col2"><para>255 255 255</para></entry>
-
-<entry colname="col3"><para>000</para></entry>
-
-</row>
-
-<row>
-
-<entry colname="col1"><para><emphasis role="bold">Broadcast</emphasis></para></entry>
-
-<entry colname="col2"><para>192 168 236</para></entry>
-
-<entry colname="col3"><para>255</para></entry>
-
-</row>
-
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>In this example, the broadcast address on the 192.168.236 network is 192.168.236.255. There is also an old "universal" broadcast address, 255.255.255.255. Routers are prohibited from forwarding these, but most machines on your local network will respond to broadcasts to this address.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.9.3" id="ch09-SECT-2.9.3">
-<title>Network address ranges</title>
-
-
-<para>
-<indexterm id="ch09-idx-953762-0"><primary>networking</primary><secondary>network address ranges</secondary></indexterm>A number of address ranges have been reserved for testing and for non-connected networks; we use one of these for the book. If you don't have an address yet, feel free to use one of these to start with. They include one class A (large) network, 10.*.*.*, and 254 class C (smaller) networks, 192.168.1.* through to 192.168.254.*. In this book we use one of the latter, 192.168.236.*. The domain <filename>example.com</filename> is also reserved for unconnected networks, explanatory examples, and books.</para>
-
-
-<para>If you're actually connecting to the Internet, you'll need to get a real network and a domain name, probably through the same company that provides your connection.</para>
-</sect3>
-
-
-
-<sect3 role="" label="9.2.9.4" id="ch09-SECT-2.9.4">
-<title>Finding your network address</title>
-
-
-<para>
-<indexterm id="ch09-idx-953761-0"><primary>network addresses</primary><secondary>finding</secondary></indexterm>If you haven't recorded your IP address, it will be displayed by the <command>ifconfig</command> command on Unix or by the IPCONFIG command on Windows 95 and NT. (Check your manual pages for any options required by your brand of Unix: Sun wants <literal>ifconfig</literal> <literal>-a</literal>). You should see output similar to the following:</para>
-
-
-<programlisting>server% ifconfig -a
-le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING >
- inet 192.168.236.11 netmask ffffff00 broadcast 192.168.236.255
-lo0: flags=49<&lt>UP,LOOPBACK,RUNNING<&gt>
- inet 127.0.0.1 netmask ff000000</programlisting>
-
-
-<para>One of the interfaces will be loopback (in our examples <literal>lo0</literal>), and the other will be the regular IP interface. The flags should show that the interface is running, and Ethernet interfaces will also say they support broadcasts (PPP interfaces don't). The other places to look for IP addresses are <filename>/etc/hosts</filename> files, Windows <emphasis>HOSTS</emphasis> files, Windows <emphasis>LMHOSTS</emphasis> files, NIS, NIS+ and DNS.<indexterm id="ch09-idx-953611-0" class="endofrange" startref="ch09-idx-953973-0"/>
-<indexterm id="ch09-idx-953611-1" class="endofrange" startref="ch09-idx-953973-1"/>
-<indexterm id="ch09-idx-953611-2" class="endofrange" startref="ch09-idx-953973-2"/></para>
-</sect3>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.2.10" id="ch09-35552">
-<title>Troubleshooting NetBIOS Names</title>
-
-
-<para>
-<indexterm id="ch09-idx-953616-0"><primary>NetBIOS name</primary><secondary>troubleshooting</secondary></indexterm>Historically, SMB protocols have depended on the NetBIOS name system, also called the LAN Manager name system. This was a simple scheme where each machine had a unique 20-character name and broadcast it on the LAN for everyone to know. With TCP/IP, we tend to use names like <emphasis>client.example.com</emphasis> stored in <filename>/etc/hosts</filename> files, through DNS or WINS.</para>
-
-
-<para>The usual mapping to domain names such as <emphasis>server.example.com</emphasis> simply uses the <emphasis>server</emphasis> part as the NetBIOS name and converts it to uppercase. Alas, this doesn't always work, especially if you have a machine with a 21-character name; not everyone uses the same NetBIOS and DNS names. For example, <emphasis>corpvm1</emphasis> along with <emphasis>vm1.corp.com</emphasis> is not unusual.</para>
-
-
-<para>A machine with a different NetBIOS name and domain name is confusing when you're troubleshooting; we recommend that you try to avoid this wherever possible. NetBIOS names are discoverable with <emphasis>smbclient</emphasis> :</para>
-
-
-<itemizedlist>
-<listitem><para>If you can list shares on your Samba server with <emphasis>smbclient</emphasis> and a <literal>-L</literal> option (list shares) of <replaceable>short_name_of_server</replaceable>, the short name is the NetBIOS name.</para></listitem>
-<listitem><para>If you get "Get_Hostbyname: Unknown host name," there is probably a mismatch. Check in the <filename>smb.conf</filename> file to see if the NetBIOS name is explicitly set.</para></listitem>
-<listitem><para>Try again, specifying <literal>-I</literal> and the IP address of the Samba server (e.g., <literal>smbclient</literal> <literal>-L</literal> <literal>server</literal> <literal>-I</literal> <literal>192.168.236.86</literal>). This overrides the name lookup and forces the packets to go to the IP address. If this works, there was a mismatch.</para></listitem>
-<listitem><para>Try with <literal>-I</literal> and the full domain name of the server (e.g., <literal>smbclient</literal> <literal>-L</literal> <literal>server</literal> <literal>-I</literal> <literal>server.example.com</literal>). This tests the lookup of the domain name, using whatever scheme the Samba server uses (e.g., DNS). If it fails, you have a name service problem. You should reread <link linkend="ch09-23768">Section 9.2.8</link> after you finish troubleshooting the NetBIOS names.</para></listitem>
-<listitem><para>Try with <literal>-n</literal> (NetBIOS name) and the name you expect to work (e.g., <literal>smbclient</literal> <literal>-n</literal> <literal>server</literal> <literal>-L</literal> <literal>server-12</literal>) but without overriding the IP address through <literal>-I</literal>. If this works, the name you specified with <literal>-n</literal> is the actual NetBIOS name of the server. If you receive "Get-Hostbyname: Unknown host MARY," it's not the right server yet.</para></listitem>
-<listitem><para>If nothing is working so far, repeat the tests specifying <literal>-U</literal> <replaceable>username</replaceable> and <literal>-W</literal> <replaceable>workgroup</replaceable>, with the username and workgroup in uppercase, to make sure you're not being derailed by a user or workgroup mismatch.</para></listitem>
-<listitem><para>If nothing works still and you had evidence of a name service problem, troubleshoot name service in <link linkend="ch09-23768">Section 9.2.8</link>," and then return to NetBIOS name<indexterm id="ch09-idx-953533-0" class="endofrange" startref="ch09-idx-953543-0"/>
-<indexterm id="ch09-idx-953533-1" class="endofrange" startref="ch09-idx-953543-1"/> service.<indexterm id="ch09-idx-953526-0" class="endofrange" startref="ch09-idx-953453-0"/></para></listitem>
-</itemizedlist>
-</sect2>
-</sect1>
-
-
-
-
-
-
-
-
-
-<sect1 role="" label="9.3" id="ch09-49719">
-<title>Extra Resources</title>
-
-
-<para>
-<indexterm id="ch09-idx-953618-0" class="startofrange"><primary>resources for further information</primary></indexterm>
-<indexterm id="ch09-idx-953618-1" class="startofrange"><primary>Samba</primary><secondary>resources for further information</secondary></indexterm>At some point during your Samba career, you will want to turn to online or printed resources for news, updates, and aid.</para>
-
-
-<sect2 role="" label="9.3.1" id="ch09-SECT-3.1">
-<title>Documentation and FAQs</title>
-
-
-<para>
-<indexterm id="ch09-idx-953626-0"><primary>documentation for Samba</primary></indexterm>
-<indexterm id="ch09-idx-953626-1"><primary>FAQ, Samba</primary></indexterm>It's okay to read the documentation. Really. Nobody can see you, and we won't tell. In fact, Samba ships with a large set of documentation files, and it is well worth the effort to at least browse through them, either in the distribution directory on your computer under <filename>/docs</filename>, or online at the Samba web site: <indexterm id="ch09-idx-953628-0"><primary>URLs (uniform resource locators)</primary><secondary>Samba</secondary><tertiary>web site</tertiary></indexterm>
-<indexterm id="ch09-idx-953628-1"><primary>Samba</primary><secondary>web site</secondary></indexterm><systemitem role="url">http://samba.anu.edu.au/samba/</systemitem>. The most current FAQ list, bug information, and distribution locations are located at the web site, with links to all of the Samba manual pages and HOW-TOs.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.3.2" id="ch09-SECT-3.2">
-<title>Samba Newsgroups</title>
-
-
-<para>
-<indexterm id="ch09-idx-953634-0"><primary>newsgroups for Samba</primary></indexterm>Usenet newsgroups have always been a great place to get advice on just about any topic. In the past few years, though, this vast pool of knowledge has developed something that has made it into an invaluable resource: a memory. Archival and search sites such as DejaNews (<systemitem role="url">http://www.dejanews.com</systemitem>) have made sifting through years of valuable solutions on a topic as simple as a few mouse clicks.</para>
-
-
-<para>The primary newsgroup for Samba is <emphasis>comp.protocols.smb</emphasis>. This should always be your first stop when there's a problem. More often than not, spending five minutes researching an error here will save hours of frustration while trying to debug something yourself.</para>
-
-
-<para>When searching a newsgroup, try to be as specific as possible, but not too wordy. Searching on actual error messages is best. If you don't find an answer immediately in the newsgroup, resist the temptation to post a request for help until you've done a bit more work on the problem. You may find that the answer is in a FAQ or one of the many documentation files that ships with Samba, or a solution might become evident when you run one of Samba's diagnostic tools. If nothing works, post a request in <emphasis>comp.protocols.smb</emphasis>, and be as specific as possible about what you have tried and what you are seeing. Include any error messages that appear. It may be several days before you receive help, so be patient and keep trying things while you wait.</para>
-
-
-<para>Once you post a request for help, keep poking at the problem yourself. Most of us have had the experience of posting a Usenet article containing hundreds of lines of intricate detail, only to solve the problem an hour later after the article has blazed its way across several continents. The rule of thumb goes something like this: the more folks who have read your request, the simpler the solution. Usually this means that once everyone in the Unix community has seen your article, the solution will be something simple like, "Plug the computer into the wall socket."</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.3.3" id="ch09-SECT-3.3">
-<title>Samba Mailing Lists</title>
-
-
-<para>
-<indexterm id="ch09-idx-953635-0"><primary>mailing lists</primary><secondary sortas="Samba">for Samba</secondary></indexterm>The following are mailing lists for support with Samba. See the Samba homepage, <systemitem role="url">http://www.samba.org/</systemitem> for information on subscribing and unsubscribing to these mailing lists:</para>
-
-
-<varlistentry><term><email>samba-technical@lists.samba.org</email></term>
-<listitem><para>This mailing list maintains debate about where the future of Samba is headed.</para></listitem>
-</varlistentry>
-
-
-<varlistentry><term><email>samba@lists.samba.org</email></term>
-<listitem><para>This is the primary Samba mailing list that contains general questions and HOW-TO information on Samba.</para></listitem>
-</varlistentry>
-</variablelist>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.3.4" id="ch09-SECT-3.4">
-<title>Samba Discussion Archives</title>
-
-
-<para>
-<indexterm id="ch09-idx-953640-0"><primary>discussion archives for Samba</primary></indexterm>There is a search service for the primary Samba mailing list. At the time this book was written, it was listed under "searchable" in the Sources paragraph on the first page of the Samba site and its mirrors, <systemitem role="url">http://samba.anu.edu.au/listproc/ghindex.html</systemitem>.</para>
-</sect2>
-
-
-
-
-
-<sect2 role="" label="9.3.5" id="ch09-SECT-3.5">
-<title>Further Reading</title>
-
-
-<para>
-<indexterm id="ch09-idx-953645-0"><primary>TCP/IP networking
-protocol</primary><secondary>resources for further
-information</secondary></indexterm>Hunt, Craig; <citetitle>TCP/IP
-Network Administration: 2nd Edition</citetitle>. Sebastopol, CA:
-O'Reilly and Associates, 1997 (ISBN 1-56592-322-7).</para>
-
-
-<para>Hunt, Craig, and Robert Bruce Thompson; <citetitle>Windows NT
-TCP/IP Network Administration</citetitle>. Sebastopol, CA: O'Reilly
-and Associates, 1998 (ISBN 1-56592-377-4).</para>
-
-
-<para>
-<indexterm id="ch09-idx-953646-0"><primary>DNS (ISBN Domain Name
-System)</primary><secondary>resources for further
-information</secondary></indexterm>Albitz, Paul, and Cricket Liu;
-<citetitle>DNS and Bind, 3rd Edition</citetitle>. Sebastopol, CA:
-O'Reilly and Associates, 1998 (ISBN 1-56592-512-2).</para>
-
-
-<para>
-<indexterm id="ch09-idx-953653-0"><primary>NFS (Network File
-System)</primary><secondary>resources for further
-information</secondary></indexterm>
-<indexterm id="ch09-idx-953653-1"><primary>Network File
-System</primary><secondary>resources for further
-information</secondary></indexterm>
-<indexterm id="ch09-idx-953653-2"><primary>resources for further
-information</primary><secondary>NFS (Network File
-System)</secondary></indexterm>
-<indexterm id="ch09-idx-953657-0"><primary>NIS/NIS+
-protocol</primary><secondary>resources for further
-information</secondary></indexterm>Stern, Hal; <citetitle>Managing NFS
-and NIS</citetitle>. Sebastopol, CA: O'Reilly and Associates, 1991
-(ISBN 0-937175-75-7).<indexterm id="ch09-idx-953621-0" class="endofrange" startref="ch09-idx-953618-0"/> <indexterm id="ch09-idx-953621-1" class="endofrange" startref="ch09-idx-953618-1"/></para>
-</sect2>
-</sect1>
-</chapter>
+++ /dev/null
-<colophon id="colophon">
-<title>Colophon</title>
-
-
-
-
-<para>Our look is the result of reader comments, our own
-experimentation, and feedback from distribution channels. Distinctive
-covers complement our distinctive approach to technical topics,
-breathing personality and life into potentially dry subjects.</para>
-
-
-<para>The animal on the cover of <citetitle>Using Samba</citetitle> is
-a African ground hornbill (<foreignphrase>Bucorvus
-cafer</foreignphrase>). This type of bird is one of fifty hornbill
-species. The African ground hornbill is a medium to large sized bird
-characterized by a bright red waddle under a very long beak,
-dark-colored body and wings, long eyelashes, and short legs. Like all
-hornbills, it has a casque, a large but lightweight growth on the top
-of its beak, which grows more folds as the bird ages. It is the only
-ground-dwelling species of hornbill, though it is able to fly when
-necessary. It lives in the grasslands of southern and eastern Africa,
-and nests in the foliage of dense trees, not in nest holes in the
-ground as other hornbills do. Its diet includes mostly fruit, as well
-as large insects and small mammals. The African ground hornbill is
-considered to be sacred by many Africans, and as such this bird is
-part of many legends and superstitions.</para>
-
-
-<para>Sarah Jane Shangraw was the production editor and proofreader
-for <citetitle>Using Samba</citetitle>. Sarah Lemaire copyedited the
-text. Maureen Dempsey and Claire Cloutier LeBlanc provided quality
-control. Brenda Miller wrote the index.</para>
-
-
-<para>Edie Freedman designed the cover of this book based on her own
-series design. The cover image of an African ground hornbill is a
-19th-century engraving from the Dover Pictorial Archive. Kathleen
-Wilson produced the cover layout with QuarkXPress 3.32 using Adobe's
-ITC Garamond font. Kathleen Wilson also created the CD design.</para>
-
-
-<para>Alicia Cech designed the interior layout based on a series
-design by Nancy Priest. Mike Sierra implemented the design in
-FrameMaker 5.5. The text and heading fonts are ITC Garamond Light and
-Garamond Book. The illustrations that appear in the book were produced
-by Robert Romano and Rhon Porter using Macromedia FreeHand 8 and Adobe
-Photoshop 5. Interior composition was done by Sarah Jane Shangraw,
-Sebastian Banker, Jeff Holcolmb, and Abigail Myers. This colophon was
-written by Nicole Arigo.</para>
-
-
-
-
-
-
-
-
-
-
-
-<para>The online edition of this book was created by the Safari
-production group (John Chodacki, Becki Maisch, and Madeleine Newell)
-using a set of Frame-to-XML conversion and cleanup tools written and
-maintained by Erik Ray, Benn Salter, John Chodacki, and Jeff
-Liggett.</para>
-</colophon>
+++ /dev/null
-<preface id="copyright" role="copyrightpg">
-
-
-
-
-<para>Copyright © 2000 O'Reilly & Associates, Inc. All rights reserved. This material may be redistributed only under the terms of the Open Content
-License. For information on the Open Content License under which the
-contents of this book are licensed, see <systemitem role="url">http://www.oreilly.com/catalog/samba/</systemitem>.</para>
-
-
-<para>Printed in the United States of America.</para>
-
-
-<para>Published by O'Reilly & Associates, Inc., 101 Morris Street,
-Sebastopol, CA 95472.</para>
-
-
-
-
-
-
-
-
-
-
-
-
-
-<para>The O'Reilly logo is a registered trademark of O'Reilly &
-Associates, Inc. Many of the designations used by manufacturers and
-sellers to distinguish their products are claimed as trademarks.
-Where those designations appear in this book, and O'Reilly &
-Associates, Inc. was aware of a trademark claim, the designations have
-been printed in caps or initial caps. The association between the
-image of the North African ground hornbill and the topic of Samba is
-a trademark of O'Reilly & Associates, Inc.</para>
-
-
-
-
-
-
-
-
-
-
-
-
-
-<para>While every precaution has been taken in the preparation of this
-book, the publisher assumes no responsibility for errors or omissions,
-or for damages resulting from the use of the information contained
-herein.</para>
-
-
-
-
-
-
-
-
-
-
-</preface>
git.samba.org / samba.git / commitdiff
