<HR>
<H2><A NAME="s2">2. Compiling and installing Samba on a Unix host</A></H2>
-<P>
+<P>
<A NAME="unix_install"></A>
</P>
<P>
<A NAME="no_browse"></A>
-</P>
-<P>*** Until the FAQ can be updated, please check the file:
-*** ftp://samba.anu.edu.au/pub/samba/BROWSING.txt
-*** for more information on browsing.</P>
+
+See
+<A HREF="ftp://samba.org/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>
-<H2><A NAME="ss2.2">2.2 Some files that I KNOW are on the server doesn't show up when I</A>view the files from my client!</H2>
+<H2><A NAME="ss2.2">2.2 Some files that I KNOW are on the server doesn't show up when I view the files from my client! </A></H2>
<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</A>I view the files from my client!</H2>
+<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
<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
tests :-) </P>
-<H2><A NAME="ss2.5">2.5 My client reports "cannot locate specified share name" or</A>similar</H2>
+<H2><A NAME="ss2.5">2.5 My client reports "cannot locate specified share name" or similar</A></H2>
<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
trying to connect to (consult your system administrator). Assuming it
exists and you specified it correctly (read your client's doco on how
to specify a service name correctly), read on:</P>
-<P>* Many clients cannot accept or use service names longer than
-eight
-characters.
-* Many clients cannot accept or use service names containing
-spaces.
-* Some servers (not Samba though) are case sensitive with service
-names.
-* Some clients force service names into upper case.</P>
+<P>
+<UL>
+<LI> Many clients cannot accept or use service names longer than eight characters.</LI>
+<LI> Many clients cannot accept or use service names containing spaces.</LI>
+<LI> Some servers (not Samba though) are case sensitive with service names.</LI>
+<LI> Some clients force service names into upper case.</LI>
+</UL>
+</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@samba.org">samba-bugs@samba.org</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),
<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
<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
<P>In earlier Samba versions there were some difficulties with the very
latest Microsoft products, particularly Excel 5 and Word for Windows
6. These should have all been solved. If not then please let Andrew
-Tridgell know.</P>
+Tridgell know via email at
+<A HREF="mailto:samba-bugs@samba.org">samba-bugs@samba.org</A>.</P>
<H2><A NAME="ss2.9">2.9 My "server string" doesn't seem to be recognised</A></H2>
<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. In a future
-version these will probably be combined and -C will be removed, but
-for now use -C</P>
+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>
<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
git.samba.org / samba.git / blobdiff