From 9b5af2ad79448acc97cd44d9446d4ede9dcdd4b8 Mon Sep 17 00:00:00 2001
From: Samba Release Account <samba-bugs@samba.org>
Date: Sun, 8 Jun 1997 14:44:43 +0000
Subject: FAQ Update Tidied up some entries with incorrect casing Added NT SP3
 entry Updated list of ported systems Updated More Info entry with more web
 site details and list of all doco files Moved mailing list subscriptions to
 separate entry Removed reference to 'samba team mailing list' just in case
 people guessed Updated nmbd -C entry, indicating obsolete. General cleanup of
 document with indented lists. Added url links where needed. Web docs will not
 show urls but will link, text files will show file names AND urls Fixed
 missing info where '\\' was being interpreted as '\' (used [\\])

If I get a warning before 1.9.17 is released, I'll clean up blank lines
from the text faq.  Don't want to do them now as I may modify the sgml again.

For those who don't know, we now maintain the FAQ as an sgml document,
and convert/create html and txt FAQs from that. We use LinuxDoc which is
now called SGMLtools.

Paul.
(This used to be commit 37214555db739a7f4ef683d287fe2febe85fee19)
---
 docs/faq/sambafaq-2.html | 67 ++++++++++++++++++++++++++----------------------
 1 file changed, 36 insertions(+), 31 deletions(-)

(limited to 'docs/faq/sambafaq-2.html')

diff --git a/docs/faq/sambafaq-2.html b/docs/faq/sambafaq-2.html
index 9f350052f6..38fec3d2c4 100644
--- a/docs/faq/sambafaq-2.html
+++ b/docs/faq/sambafaq-2.html
@@ -9,7 +9,7 @@
 <HR>
 <H2><A NAME="s2">2. Compiling and installing Samba on a Unix host</A></H2>
 
-<P> 
+<P>
 <A NAME="unix_install"></A> 
 </P>
 
@@ -17,17 +17,22 @@
 
 <P>
 <A NAME="no_browse"></A> 
-</P>
-<P>See 
+
+See 
 <A HREF="ftp://samba.anu.edu.au/pub/samba/BROWSING.txt">BROWSING.txt</A>
 for more information on browsing.  Browsing.txt can also be found
 in the docs directory of the Samba source.</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:</P>
-<P>net use M: \\mary\fred</P>
-<P>The details of how to do this and the specific syntax varies from
+thusly:
+<BLOCKQUOTE><CODE>
+<PRE>
+   net use M: \\mary\fred
+</PRE>
+</CODE></BLOCKQUOTE>
+
+The details of how to do this and the specific syntax varies from
 client to client - check your client's documentation.</P>
 
 
@@ -35,15 +40,15 @@ client to client - check your client's documentation.</P>
 
 <P> 
 <A NAME="missing_files"></A> 
-</P>
 
+See the next question.</P>
 
 <H2><A NAME="ss2.3">2.3 Some files on the server show up with really wierd filenames when I view the files from my client! </A></H2>
 
 <P> 
 <A NAME="strange_filenames"></A> 
-</P>
-<P>If you check what files are not showing up, you will note that they
+
+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
@@ -56,10 +61,10 @@ details of how to change this - the parameter you need to set is
 
 <H2><A NAME="ss2.4">2.4 My client reports "cannot locate specified computer" or similar</A></H2>
 
-<P> 
+<P>
 <A NAME="cant_see_server"></A> 
-</P>
-<P>This indicates one of three things: You supplied an incorrect server
+
+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
@@ -86,8 +91,8 @@ tests :-)     </P>
 
 <P> 
 <A NAME="cant_see_share"></A> 
-</P>
-<P>This message indicates that your client CAN locate the specified
+
+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
@@ -104,19 +109,19 @@ to specify a service name correctly), read on:</P>
 </P>
 
 
-<H2><A NAME="ss2.6">2.6 My client reports "cannot find domain controller", "cannot log</A>on to the network" or similar </H2>
+<H2><A NAME="ss2.6">2.6 My client reports "cannot find domain controller", "cannot log on to the network" or similar </A></H2>
 
 <P> 
 <A NAME="cant_see_net"></A> 
-</P>
-<P>Nothing is wrong - Samba does not implement the primary domain name
+
+Nothing is wrong - Samba does not implement the primary domain name
 controller stuff for several reasons, including the fact that the
 whole concept of a primary domain controller and "logging in to a
 network" doesn't fit well with clients possibly running on multiuser
 machines (such as users of smbclient under Unix). Having said that,
 several developers are working hard on building it in to the next
 major version of Samba. If you can contribute, send a message to
-samba-bugs!</P>
+<A HREF="mailto:samba-bugs@anu.edu.au">samba-bugs@anu.edu.au</A> !</P>
 <P>Seeing this message should not affect your ability to mount redirected
 disks and printers, which is really what all this is about.</P>
 <P>For many clients (including Windows for Workgroups and Lan Manager),
@@ -127,8 +132,8 @@ setting the domain to STANDALONE at least gets rid of the message.</P>
 
 <P> 
 <A NAME="no_printing"></A> 
-</P>
-<P>Make sure that the specified print command for the service you are
+
+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
@@ -155,8 +160,8 @@ mechanism.</P>
 
 <P>
 <A NAME="programs_wont_run"></A> 
-</P>
-<P>There are numerous possible reasons for this, but one MAJOR
+
+There are numerous possible reasons for this, but one MAJOR
 possibility is that your software uses locking. Make sure you are
 using Samba 1.6.11 or later. It may also be possible to work around
 the problem by setting "locking=no" in the Samba configuration file
@@ -173,21 +178,21 @@ Tridgell know via email at
 
 <P>
 <A NAME="bad_server_string"></A> 
-</P>
-<P>my client reports the default setting, eg. "Samba 1.9.15p4", instead
+
+OR My client reports the default setting, eg. "Samba 1.9.15p4", instead
 of what I have changed it to in the smb.conf file.</P>
 <P>You need to use the -C option in nmbd. The "server string" affects
-what smbd puts out and -C affects what nmbd puts out. 
-Current versions of Samba (1.9.16p11 +) have combined these options into
+what smbd puts out and -C affects what nmbd puts out.</P>
+<P>Current versions of Samba (1.9.16 +) have combined these options into
 the "server string" field of smb.conf, -C for nmbd is now obsolete.</P>
 
 
-<H2><A NAME="ss2.10">2.10 My client reports "This server is not configured to list shared</A>resources" </H2>
+<H2><A NAME="ss2.10">2.10 My client reports "This server is not configured to list shared resources" </A></H2>
 
 <P> 
 <A NAME="cant_list_shares"></A> 
-</P>
-<P>Your guest account is probably invalid for some reason. Samba uses the
+
+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>
@@ -197,8 +202,8 @@ valid.</P>
 
 <P>
 <A NAME="trapdoor_uid"></A> 
-</P>
-<P>This can have several causes. It might be because you are using a uid
+
+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
-- 
cgit