Add generated files for FAQ

(This used to be commit fd9854d45dee6697e1d1515e7e1729a3237093ca)
author: Jelmer Vernooij <jelmer@samba.org> 2002-10-03 18:43:39 +0000
committer: Jelmer Vernooij <jelmer@samba.org> 2002-10-03 18:43:39 +0000
commit: 62d14a17da0cef9f5369f5009dc7b229b0af1547 (patch)
tree: 6992f960181bf650bcf37672873b346b33c26c40 /docs
parent: 06606d2e290fc9d578d4cb30b640c3ce52939663 (diff)
download: samba-62d14a17da0cef9f5369f5009dc7b229b0af1547.tar.gz
samba-62d14a17da0cef9f5369f5009dc7b229b0af1547.tar.bz2
samba-62d14a17da0cef9f5369f5009dc7b229b0af1547.zip
4 files changed, 1346 insertions, 0 deletions
diff --git a/docs/faq/clientapp.html b/docs/faq/clientapp.html
new file mode 100644
index 0000000000..d2ba0a08b5
--- /dev/null
+++ b/docs/faq/clientapp.html
@@ -0,0 +1,146 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Specific client application problems</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Compiling and installing Samba on a Unix host"
+HREF="install.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="install.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+>&nbsp;</TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="CLIENTAPP"
+></A
+>Chapter 3. Specific client application problems</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN170"
+></A
+>3.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</H1
+><P
+>When installing MS Office on a Samba drive for which you have admin
+user permissions, ie. admin users = username, you will find the
+setup program unable to complete the installation.</P
+><P
+>To get around this problem, do the installation without admin user
+permissions The problem is that MS Office Setup checks that a file is
+rdonly by trying to open it for writing.</P
+><P
+>Admin users can always open a file for writing, as they run as root.
+You just have to install as a non-admin user and then use "chown -R"
+to fix the owner.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="install.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>&nbsp;</TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Compiling and installing Samba on a Unix host</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>&nbsp;</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
+\ No newline at end of file
diff --git a/docs/faq/general.html b/docs/faq/general.html
new file mode 100644
index 0000000000..5a42678cb6
--- /dev/null
+++ b/docs/faq/general.html
@@ -0,0 +1,450 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>General Information</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="NEXT"
+TITLE="Compiling and installing Samba on a Unix host"
+HREF="install.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="GENERAL"
+></A
+>Chapter 1. General Information</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN12"
+></A
+>1.1. Where can I get it?</H1
+><P
+>The Samba suite is available at the <A
+HREF="http://samba.org/"
+TARGET="_top"
+>samba website</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN16"
+></A
+>1.2. What do the version numbers mean?</H1
+><P
+>It is not recommended that you run a version of Samba with the word
+"alpha" in its name unless you know what you are doing and are willing
+to do some debugging. Many, many people just get the latest
+recommended stable release version and are happy. If you are brave, by
+all means take the plunge and help with the testing and development -
+but don't install it on your departmental server. Samba is typically
+very stable and safe, and this is mostly due to the policy of many
+public releases.</P
+><P
+>How the scheme works:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>When major changes are made the version number is increased. For
+example, the transition from 1.9.15 to 1.9.16. However, this version
+number will not appear immediately and people should continue to use
+1.9.15 for production systems (see next point.)</TD
+></TR
+><TR
+><TD
+>Just after major changes are made the software is considered
+unstable, and a series of alpha releases are distributed, for example
+1.9.16alpha1. These are for testing by those who know what they are
+doing.  The "alpha" in the filename will hopefully scare off those who
+are just looking for the latest version to install.</TD
+></TR
+><TR
+><TD
+>When Andrew thinks that the alphas have stabilised to the point
+where he would recommend new users install it, he renames it to the
+same version number without the alpha, for example 1.9.16.</TD
+></TR
+><TR
+><TD
+>Inevitably bugs are found in the "stable" releases and minor patch
+levels are released which give us the pXX series, for example 1.9.16p2.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>&#13;</P
+><P
+>So the progression goes:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>1.9.15p7	(production)
+1.9.15p8	(production)
+1.9.16alpha1	(test sites only)
+:
+1.9.16alpha20	(test sites only)
+1.9.16		(production)
+1.9.16p1	(production)</PRE
+></P
+><P
+>The above system means that whenever someone looks at the samba ftp
+site they will be able to grab the highest numbered release without an
+alpha in the name and be sure of getting the current recommended
+version.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN28"
+></A
+>1.3. What platforms are supported?</H1
+><P
+>Many different platforms have run Samba successfully. The platforms
+most widely used and thus best tested are Linux and SunOS.</P
+><P
+>At time of writing, there is support (or has been support for in earlier 
+versions):</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>A/UX 3.0</TD
+></TR
+><TR
+><TD
+>AIX</TD
+></TR
+><TR
+><TD
+>Altos Series 386/1000</TD
+></TR
+><TR
+><TD
+>Amiga</TD
+></TR
+><TR
+><TD
+>Apollo Domain/OS sr10.3</TD
+></TR
+><TR
+><TD
+>BSDI </TD
+></TR
+><TR
+><TD
+>B.O.S. (Bull Operating System)</TD
+></TR
+><TR
+><TD
+>Cray, Unicos 8.0</TD
+></TR
+><TR
+><TD
+>Convex</TD
+></TR
+><TR
+><TD
+>DGUX. </TD
+></TR
+><TR
+><TD
+>DNIX.</TD
+></TR
+><TR
+><TD
+>FreeBSD</TD
+></TR
+><TR
+><TD
+>HP-UX</TD
+></TR
+><TR
+><TD
+>Intergraph. </TD
+></TR
+><TR
+><TD
+>Linux with/without shadow passwords and quota</TD
+></TR
+><TR
+><TD
+>LYNX 2.3.0</TD
+></TR
+><TR
+><TD
+>MachTen (a unix like system for Macintoshes)</TD
+></TR
+><TR
+><TD
+>Motorola 88xxx/9xx range of machines</TD
+></TR
+><TR
+><TD
+>NetBSD</TD
+></TR
+><TR
+><TD
+>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</TD
+></TR
+><TR
+><TD
+>OS/2 using EMX 0.9b</TD
+></TR
+><TR
+><TD
+>OSF1</TD
+></TR
+><TR
+><TD
+>QNX 4.22</TD
+></TR
+><TR
+><TD
+>RiscIX. </TD
+></TR
+><TR
+><TD
+>RISCOs 5.0B</TD
+></TR
+><TR
+><TD
+>SEQUENT. </TD
+></TR
+><TR
+><TD
+>SCO (including: 3.2v2, European dist., OpenServer 5)</TD
+></TR
+><TR
+><TD
+>SGI.</TD
+></TR
+><TR
+><TD
+>SMP_DC.OSx v1.1-94c079 on Pyramid S series</TD
+></TR
+><TR
+><TD
+>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</TD
+></TR
+><TR
+><TD
+>SUNOS 4</TD
+></TR
+><TR
+><TD
+>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</TD
+></TR
+><TR
+><TD
+>Sunsoft ISC SVR3V4</TD
+></TR
+><TR
+><TD
+>SVR4</TD
+></TR
+><TR
+><TD
+>System V with some berkely extensions (Motorola 88k R32V3.2).</TD
+></TR
+><TR
+><TD
+>ULTRIX.</TD
+></TR
+><TR
+><TD
+>UNIXWARE</TD
+></TR
+><TR
+><TD
+>UXP/DS</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN71"
+></A
+>1.4. How do I subscribe to the Samba Mailing Lists?</H1
+><P
+>Look at <A
+HREF="http://samba.org/samba/archives.html"
+TARGET="_top"
+>the samba mailing list page</A
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN75"
+></A
+>1.5. Pizza supply details</H1
+><P
+>Those who have registered in the Samba survey as "Pizza Factory" will
+already know this, but the rest may need some help. Andrew doesn't ask
+for payment, but he does appreciate it when people give him
+pizza. This calls for a little organisation when the pizza donor is
+twenty thousand kilometres away, but it has been done.&#13;</P
+><P
+>Method 1: Ring up your local branch of an international pizza chain
+and see if they honour their vouchers internationally. Pizza Hut do,
+which is how the entire Canberra Linux Users Group got to eat pizza
+one night, courtesy of someone in the US.</P
+><P
+>Method 2: Ring up a local pizza shop in Canberra and quote a credit
+card number for a certain amount, and tell them that Andrew will be
+collecting it (don't forget to tell him.) One kind soul from Germany
+did this.</P
+><P
+>Method 3: Purchase a pizza voucher from your local pizza shop that has
+no international affiliations and send it to Andrew. It is completely
+useless but he can hang it on the wall next to the one he already has
+from Germany :-)</P
+><P
+>Method 4: Air freight him a pizza with your favourite regional
+flavours. It will probably get stuck in customs or torn apart by
+hungry sniffer dogs but it will have been a noble gesture.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba FAQ</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Compiling and installing Samba on a Unix host</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
+\ No newline at end of file
diff --git a/docs/faq/install.html b/docs/faq/install.html
new file mode 100644
index 0000000000..f9ecac1384
--- /dev/null
+++ b/docs/faq/install.html
@@ -0,0 +1,525 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Compiling and installing Samba on a Unix host</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="General Information"
+HREF="general.html"><LINK
+REL="NEXT"
+TITLE="Specific client application problems"
+HREF="clientapp.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="general.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="clientapp.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="INSTALL"
+></A
+>Chapter 2. Compiling and installing Samba on a Unix host</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN84"
+></A
+>2.1. I can't see the Samba server in any browse lists!</H1
+><P
+>See Browsing.html in the docs directory of the samba source
+for more information on browsing.</P
+><P
+>If your GUI client does not permit you to select non-browsable
+servers, you may need to do so on the command line. For example, under
+Lan Manager you might connect to the above service as disk drive M:
+thusly:
+<PRE
+CLASS="PROGRAMLISTING"
+>   net use M: \\mary\fred</PRE
+>
+The details of how to do this and the specific syntax varies from
+client to client - check your client's documentation.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN89"
+></A
+>2.2. Some files that I KNOW are on the server doesn't show up when I view the files from my client!</H1
+><P
+>See the next question.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN92"
+></A
+>2.3. Some files on the server show up with really wierd filenames when I view the files from my client!</H1
+><P
+>If you check what files are not showing up, you will note that they
+are files which contain upper case letters or which are otherwise not
+DOS-compatible (ie, they are not legal DOS filenames for some reason).</P
+><P
+>The Samba server can be configured either to ignore such files
+completely, or to present them to the client in "mangled" form. If you
+are not seeing the files at all, the Samba server has most likely been
+configured to ignore them.  Consult the man page smb.conf(5) for
+details of how to change this - the parameter you need to set is
+"mangled names = yes".</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN96"
+></A
+>2.4. My client reports "cannot locate specified computer" or similar</H1
+><P
+>This indicates one of three things: You supplied an incorrect server
+name, the underlying TCP/IP layer is not working correctly, or the
+name you specified cannot be resolved.</P
+><P
+>After carefully checking that the name you typed is the name you
+should have typed, try doing things like pinging a host or telnetting
+to somewhere on your network to see if TCP/IP is functioning OK. If it
+is, the problem is most likely name resolution.</P
+><P
+>If your client has a facility to do so, hardcode a mapping between the
+hosts IP and the name you want to use. For example, with Lan Manager
+or Windows for Workgroups you would put a suitable entry in the file
+LMHOSTS. If this works, the problem is in the communication between
+your client and the netbios name server. If it does not work, then
+there is something fundamental wrong with your naming and the solution
+is beyond the scope of this document.</P
+><P
+>If you do not have any server on your subnet supplying netbios name
+resolution, hardcoded mappings are your only option. If you DO have a
+netbios name server running (such as the Samba suite's nmbd program),
+the problem probably lies in the way it is set up. Refer to Section
+Two of this FAQ for more ideas.</P
+><P
+>By the way, remember to REMOVE the hardcoded mapping before further
+tests :-)</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN103"
+></A
+>2.5. My client reports "cannot locate specified share name" or similar</H1
+><P
+>This message indicates that your client CAN locate the specified
+server, which is a good start, but that it cannot find a service of
+the name you gave.</P
+><P
+>The first step is to check the exact name of the service you are
+trying to connect to (consult your system administrator). Assuming it
+exists and you specified it correctly (read your client's docs on how
+to specify a service name correctly), read on:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Many clients cannot accept or use service names longer than eight characters.</TD
+></TR
+><TR
+><TD
+>Many clients cannot accept or use service names containing spaces.</TD
+></TR
+><TR
+><TD
+>Some servers (not Samba though) are case sensitive with service names.</TD
+></TR
+><TR
+><TD
+>Some clients force service names into upper case.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN112"
+></A
+>2.6. Printing doesn't work</H1
+><P
+>Make sure that the specified print command for the service you are
+connecting to is correct and that it has a fully-qualified path (eg.,
+use "/usr/bin/lpr" rather than just "lpr").</P
+><P
+>Make sure that the spool directory specified for the service is
+writable by the user connected to the service. In particular the user
+"nobody" often has problems with printing, even if it worked with an
+earlier version of Samba. Try creating another guest user other than
+"nobody".</P
+><P
+>Make sure that the user specified in the service is permitted to use
+the printer.</P
+><P
+>Check the debug log produced by smbd. Search for the printer name and
+see if the log turns up any clues. Note that error messages to do with
+a service ipc$ are meaningless - they relate to the way the client
+attempts to retrieve status information when using the LANMAN1
+protocol.</P
+><P
+>If using WfWg then you need to set the default protocol to TCP/IP, not
+Netbeui. This is a WfWg bug.</P
+><P
+>If using the Lanman1 protocol (the default) then try switching to
+coreplus.  Also not that print status error messages don't mean
+printing won't work. The print status is received by a different
+mechanism.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN120"
+></A
+>2.7. My client reports "This server is not configured to list shared resources"</H1
+><P
+>Your guest account is probably invalid for some reason. Samba uses the
+guest account for browsing in smbd.  Check that your guest account is
+valid.</P
+><P
+>See also 'guest account' in smb.conf man page.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN124"
+></A
+>2.8. Log message "you appear to have a trapdoor uid system"</H1
+><P
+>This can have several causes. It might be because you are using a uid
+or gid of 65535 or -1. This is a VERY bad idea, and is a big security
+hole. Check carefully in your /etc/passwd file and make sure that no
+user has uid 65535 or -1. Especially check the "nobody" user, as many
+broken systems are shipped with nobody setup with a uid of 65535.</P
+><P
+>It might also mean that your OS has a trapdoor uid/gid system :-)</P
+><P
+>This means that once a process changes effective uid from root to
+another user it can't go back to root. Unfortunately Samba relies on
+being able to change effective uid from root to non-root and back
+again to implement its security policy. If your OS has a trapdoor uid
+system this won't work, and several things in Samba may break. Less
+things will break if you use user or server level security instead of
+the default share level security, but you may still strike
+problems.</P
+><P
+>The problems don't give rise to any security holes, so don't panic,
+but it does mean some of Samba's capabilities will be unavailable.
+In particular you will not be able to connect to the Samba server as
+two different uids at once. This may happen if you try to print as a
+"guest" while accessing a share as a normal user. It may also affect
+your ability to list the available shares as this is normally done as
+the guest user.</P
+><P
+>Complain to your OS vendor and ask them to fix their system.</P
+><P
+>Note: the reason why 65535 is a VERY bad choice of uid and gid is that
+it casts to -1 as a uid, and the setreuid() system call ignores (with
+no error) uid changes to -1. This means any daemon attempting to run
+as uid 65535 will actually run as root. This is not good!</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN132"
+></A
+>2.9. Why are my file's timestamps off by an hour, or by a few hours?</H1
+><P
+>This is from Paul Eggert eggert@twinsun.com.</P
+><P
+>Most likely it's a problem with your time zone settings.</P
+><P
+>Internally, Samba maintains time in traditional Unix format,
+namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
+(or ``GMT''), not counting leap seconds.</P
+><P
+>On the server side, Samba uses the Unix TZ variable to convert
+internal timestamps to and from local time.  So on the server side, there are
+two things to get right.
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</TD
+></TR
+><TR
+><TD
+>The TZ environment variable must be set on the server before Samba is invoked.  The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><P
+>TZ must have the correct value.</P
+><P
+>If possible, use geographical time zone settings
+(e.g. TZ='America/Los_Angeles' or perhaps
+ TZ=':US/Pacific').  These are supported by most
+popular Unix OSes, are easier to get right, and are
+more accurate for historical timestamps.  If your
+operating system has out-of-date tables, you should be
+able to update them from the public domain time zone
+tables at <A
+HREF="ftp://elsie.nci.nih.gov/pub/"
+TARGET="_top"
+>ftp://elsie.nci.nih.gov/pub/</A
+>.</P
+><P
+>If your system does not support geographical timezone
+settings, you must use a Posix-style TZ strings, e.g.
+TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
+Posix TZ strings can take the following form (with optional
+											  items in brackets):
+<PRE
+CLASS="PROGRAMLISTING"
+>	StdOffset[Dst[Offset],Date/Time,Date/Time]</PRE
+>
+                where:</P
+><P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>`Std' is the standard time designation (e.g. `PST').</TD
+></TR
+><TR
+><TD
+>`Offset' is the number of hours behind UTC (e.g. `8').
+Prepend a `-' if you are ahead of UTC, and
+append `:30' if you are at a half-hour offset.
+Omit all the remaining items if you do not use
+daylight-saving time.</TD
+></TR
+><TR
+><TD
+>`Dst' is the daylight-saving time designation
+(e.g. `PDT').</TD
+></TR
+><TR
+><TD
+>The optional second `Offset' is the number of
+hours that daylight-saving time is behind UTC.
+The default is 1 hour ahead of standard time.</TD
+></TR
+><TR
+><TD
+>`Date/Time,Date/Time' specify when daylight-saving
+time starts and ends.  The format for a date is
+`Mm.n.d', which specifies the dth day (0 is Sunday)
+of the nth week of the mth month, where week 5 means
+the last such day in the month.  The format for a
+time is [h]h[:mm[:ss]], using a 24-hour clock.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><P
+>Other Posix string formats are allowed but you don't want
+to know about them.</P
+><P
+>On the client side, you must make sure that your client's clock and
+time zone is also set appropriately.  [[I don't know how to do this.]]
+Samba traditionally has had many problems dealing with time zones, due
+to the bizarre ways that Microsoft network protocols handle time
+zones.  </P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN155"
+></A
+>2.10. How do I set the printer driver name correctly?</H1
+><P
+>Question:</P
+><P
+><SPAN
+CLASS="QUOTE"
+>" On NT, I opened "Printer Manager" and "Connect to Printer".
+ Enter ["\\ptdi270\ps1"] in the box of printer. I got the
+ following error message
+ "</SPAN
+>
+ </P
+><P
+> <PRE
+CLASS="PROGRAMLISTING"
+>     You do not have sufficient access to your machine
+     to connect to the selected printer, since a driver
+     needs to be installed locally.
+ </PRE
+>
+ </P
+><P
+>Answer:</P
+><P
+>In the more recent versions of Samba you can now set the "printer
+driver" in smb.conf. This tells the client what driver to use. For
+example:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>     printer driver = HP LaserJet 4L</PRE
+></P
+><P
+>With this, NT knows to use the right driver. You have to get this string
+exactly right.</P
+><P
+>To find the exact string to use, you need to get to the dialog box in
+your client where you select which printer driver to install. The
+correct strings for all the different printers are shown in a listbox
+in that dialog box.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="general.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="clientapp.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>General Information</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Specific client application problems</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
+\ No newline at end of file
diff --git a/docs/faq/samba-faq.html b/docs/faq/samba-faq.html
new file mode 100644
index 0000000000..9623dc9a7c
--- /dev/null
+++ b/docs/faq/samba-faq.html
@@ -0,0 +1,225 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Samba FAQ</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="NEXT"
+TITLE="General Information"
+HREF="general.html"></HEAD
+><BODY
+CLASS="BOOK"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="BOOK"
+><A
+NAME="SAMBA-FAQ"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+><A
+NAME="SAMBA-FAQ"
+></A
+>Samba FAQ</H1
+><H3
+CLASS="AUTHOR"
+><A
+NAME="AEN4"
+></A
+>Samba Team</H3
+><HR></DIV
+><H1
+><A
+NAME="AEN7"
+></A
+>Dedication</H1
+><P
+>This is the Frequently Asked Questions (FAQ) document for
+Samba, the free and very popular SMB server product. An SMB server
+allows file and printer connections from clients such as Windows,
+OS/2, Linux and others. Current to version 3.0. Please send any
+corrections to the samba documentation mailinglist at
+<A
+HREF="mailto:samba-doc@samba.org"
+TARGET="_top"
+>samba-doc@samba.org</A
+>. 
+This FAQ is based on the old Samba FAQ by Dan Shearer and Paul Blackman.</P
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>1. <A
+HREF="general.html"
+>General Information</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="general.html#AEN12"
+>Where can I get it?</A
+></DT
+><DT
+>1.2. <A
+HREF="general.html#AEN16"
+>What do the version numbers mean?</A
+></DT
+><DT
+>1.3. <A
+HREF="general.html#AEN28"
+>What platforms are supported?</A
+></DT
+><DT
+>1.4. <A
+HREF="general.html#AEN71"
+>How do I subscribe to the Samba Mailing Lists?</A
+></DT
+><DT
+>1.5. <A
+HREF="general.html#AEN75"
+>Pizza supply details</A
+></DT
+></DL
+></DD
+><DT
+>2. <A
+HREF="install.html"
+>Compiling and installing Samba on a Unix host</A
+></DT
+><DD
+><DL
+><DT
+>2.1. <A
+HREF="install.html#AEN84"
+>I can't see the Samba server in any browse lists!</A
+></DT
+><DT
+>2.2. <A
+HREF="install.html#AEN89"
+>Some files that I KNOW are on the server doesn't show up when I view the files from my client!</A
+></DT
+><DT
+>2.3. <A
+HREF="install.html#AEN92"
+>Some files on the server show up with really wierd filenames when I view the files from my client!</A
+></DT
+><DT
+>2.4. <A
+HREF="install.html#AEN96"
+>My client reports "cannot locate specified computer" or similar</A
+></DT
+><DT
+>2.5. <A
+HREF="install.html#AEN103"
+>My client reports "cannot locate specified share name" or similar</A
+></DT
+><DT
+>2.6. <A
+HREF="install.html#AEN112"
+>Printing doesn't work</A
+></DT
+><DT
+>2.7. <A
+HREF="install.html#AEN120"
+>My client reports "This server is not configured to list shared resources"</A
+></DT
+><DT
+>2.8. <A
+HREF="install.html#AEN124"
+>Log message "you appear to have a trapdoor uid system"</A
+></DT
+><DT
+>2.9. <A
+HREF="install.html#AEN132"
+>Why are my file's timestamps off by an hour, or by a few hours?</A
+></DT
+><DT
+>2.10. <A
+HREF="install.html#AEN155"
+>How do I set the printer driver name correctly?</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="clientapp.html"
+>Specific client application problems</A
+></DT
+><DD
+><DL
+><DT
+>3.1. <A
+HREF="clientapp.html#AEN170"
+>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="general.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>General Information</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
+\ No newline at end of file
author	Jelmer Vernooij <jelmer@samba.org>	2002-10-03 18:43:39 +0000
committer	Jelmer Vernooij <jelmer@samba.org>	2002-10-03 18:43:39 +0000
commit	62d14a17da0cef9f5369f5009dc7b229b0af1547 (patch)
tree	6992f960181bf650bcf37672873b346b33c26c40 /docs
parent	06606d2e290fc9d578d4cb30b640c3ce52939663 (diff)
download	samba-62d14a17da0cef9f5369f5009dc7b229b0af1547.tar.gz samba-62d14a17da0cef9f5369f5009dc7b229b0af1547.tar.bz2 samba-62d14a17da0cef9f5369f5009dc7b229b0af1547.zip