| blob | 411656bc76cbaa13752c56585de5b416b7de946e |
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2. Compiling and installing Samba on a Unix host</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-general.html" title="Chapter 1. General Information"><link rel="next" href="FAQ-Config.html" title="Chapter 3. Configuration problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Compiling and installing Samba on a Unix host</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-Config.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-Install"></a>Chapter 2. Compiling and installing Samba on a Unix host</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Install.html#id2808542">I can't see the Samba server in any browse lists!</a></dt><dt><a href="FAQ-Install.html#id2811456">Some files that I KNOW are on the server don't show up when I view the files from my client!</a></dt><dt><a href="FAQ-Install.html#id2811470">Some files on the server show up with really wierd filenames when I view the files from my client!</a></dt><dt><a href="FAQ-Install.html#id2860743">My client reports "cannot locate specified computer" or similar</a></dt><dt><a href="FAQ-Install.html#id2860797">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2806029">Printing doesn't work</a></dt><dt><a href="FAQ-Install.html#id2807904">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="FAQ-Install.html#id2807925">Log message "you appear to have a trapdoor uid system" </a></dt><dt><a href="FAQ-Install.html#id2807990">Why are my file's timestamps off by an hour, or by a few hours?</a></dt><dt><a href="FAQ-Install.html#id2811127">How do I set the printer driver name correctly?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808542"></a>I can't see the Samba server in any browse lists!</h2></div></div><p>
3 See Browsing.html in the docs directory of the samba source
4 for more information on browsing.
5 </p><p>
6 If your GUI client does not permit you to select non-browsable
7 servers, you may need to do so on the command line. For example, under
8 Lan Manager you might connect to the above service as disk drive M:
9 thusly:
11 net use M: \\mary\fred
12 </pre><p>
13 The details of how to do this and the specific syntax varies from
14 client to client - check your client's documentation.
15 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811456"></a>Some files that I KNOW are on the server don't show up when I view the files from my client!</h2></div></div><p>See the next question.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811470"></a>Some files on the server show up with really wierd filenames when I view the files from my client!</h2></div></div><p>
16 If you check what files are not showing up, you will note that they
17 are files which contain upper case letters or which are otherwise not
18 DOS-compatible (ie, they are not legal DOS filenames for some reason).
19 </p><p>
20 The Samba server can be configured either to ignore such files
22 are not seeing the files at all, the Samba server has most likely been
23 configured to ignore them. Consult the man page smb.conf(5) for
24 details of how to change this - the parameter you need to set is
26 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860743"></a>My client reports "cannot locate specified computer" or similar</h2></div></div><p>
27 This indicates one of three things: You supplied an incorrect server
28 name, the underlying TCP/IP layer is not working correctly, or the
29 name you specified cannot be resolved.
30 </p><p>
31 After carefully checking that the name you typed is the name you
32 should have typed, try doing things like pinging a host or telnetting
33 to somewhere on your network to see if TCP/IP is functioning OK. If it
34 is, the problem is most likely name resolution.
35 </p><p>
36 If your client has a facility to do so, hardcode a mapping between the
37 hosts IP and the name you want to use. For example, with Lan Manager
38 or Windows for Workgroups you would put a suitable entry in the file
39 LMHOSTS. If this works, the problem is in the communication between
40 your client and the netbios name server. If it does not work, then
41 there is something fundamental wrong with your naming and the solution
42 is beyond the scope of this document.
43 </p><p>
44 If you do not have any server on your subnet supplying netbios name
45 resolution, hardcoded mappings are your only option. If you DO have a
46 netbios name server running (such as the Samba suite's nmbd program),
47 the problem probably lies in the way it is set up. Refer to Section
48 Two of this FAQ for more ideas.
49 </p><p>
50 By the way, remember to REMOVE the hardcoded mapping before further
51 tests :-)
52 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860797"></a>My client reports "cannot locate specified share name" or similar</h2></div></div><p>
53 This message indicates that your client CAN locate the specified
54 server, which is a good start, but that it cannot find a service of
55 the name you gave.
56 </p><p>
57 The first step is to check the exact name of the service you are
58 trying to connect to (consult your system administrator). Assuming it
59 exists and you specified it correctly (read your client's docs on how
60 to specify a service name correctly), read on:
61 </p><table class="simplelist" border="0" summary="Simple list"><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></table></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2806029"></a>Printing doesn't work</h2></div></div><p>
62 Make sure that the specified print command for the service you are
63 connecting to is correct and that it has a fully-qualified path (eg.,
65 </p><p>
66 Make sure that the spool directory specified for the service is
67 writable by the user connected to the service. In particular the user
69 earlier version of Samba. Try creating another guest user other than
71 </p><p>
72 Make sure that the user specified in the service is permitted to use
73 the printer.
74 </p><p>
75 Check the debug log produced by smbd. Search for the printer name and
76 see if the log turns up any clues. Note that error messages to do with
77 a service ipc$ are meaningless - they relate to the way the client
78 attempts to retrieve status information when using the LANMAN1
79 protocol.
80 </p><p>
81 If using WfWg then you need to set the default protocol to TCP/IP, not
82 Netbeui. This is a WfWg bug.
83 </p><p>
84 If using the Lanman1 protocol (the default) then try switching to
85 coreplus. Also not that print status error messages don't mean
86 printing won't work. The print status is received by a different
87 mechanism.
88 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807904"></a>My client reports "This server is not configured to list shared resources"</h2></div></div><p>
89 Your guest account is probably invalid for some reason. Samba uses the
90 guest account for browsing in smbd. Check that your guest account is
91 valid.
92 </p><p>See also 'guest account' in smb.conf man page.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807925"></a>Log message "you appear to have a trapdoor uid system" </h2></div></div><p>
93 This can have several causes. It might be because you are using a uid
95 hole. Check carefully in your /etc/passwd file and make sure that no
97 broken systems are shipped with nobody setup with a uid of 65535.
99 This means that once a process changes effective uid from root to
100 another user it can't go back to root. Unfortunately Samba relies on
101 being able to change effective uid from root to non-root and back
102 again to implement its security policy. If your OS has a trapdoor uid
103 system this won't work, and several things in Samba may break. Less
104 things will break if you use user or server level security instead of
105 the default share level security, but you may still strike
106 problems.
107 </p><p>
108 The problems don't give rise to any security holes, so don't panic,
109 but it does mean some of Samba's capabilities will be unavailable.
110 In particular you will not be able to connect to the Samba server as
111 two different uids at once. This may happen if you try to print as a
113 your ability to list the available shares as this is normally done as
114 the guest user.
115 </p><p>
116 Complain to your OS vendor and ask them to fix their system.
117 </p><p>
118 Note: the reason why 65535 is a VERY bad choice of uid and gid is that
119 it casts to -1 as a uid, and the setreuid() system call ignores (with
120 no error) uid changes to -1. This means any daemon attempting to run
121 as uid 65535 will actually run as root. This is not good!
122 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807990"></a>Why are my file's timestamps off by an hour, or by a few hours?</h2></div></div><p>
123 This is from Paul Eggert eggert@twinsun.com.
124 </p><p>
125 Most likely it's a problem with your time zone settings.
126 </p><p>
127 Internally, Samba maintains time in traditional Unix format,
129 (or ``GMT''), not counting leap seconds.
130 </p><p>
131 On the server side, Samba uses the Unix TZ variable to convert
132 internal timestamps to and from local time. So on the server side, there are
133 two things to get right.
134 </p><table class="simplelist" border="0" summary="Simple list"><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></table><p>
136 If possible, use geographical time zone settings
137 (e.g. TZ='America/Los_Angeles' or perhaps
138 TZ=':US/Pacific'). These are supported by most
139 popular Unix OSes, are easier to get right, and are
140 more accurate for historical timestamps. If your
141 operating system has out-of-date tables, you should be
142 able to update them from the public domain time zone
143 tables at <a href="ftp://elsie.nci.nih.gov/pub/" target="_top">ftp://elsie.nci.nih.gov/pub/</a>.
144 </p><p>If your system does not support geographical timezone
145 settings, you must use a Posix-style TZ strings, e.g.
147 Posix TZ strings can take the following form (with optional
148 items in brackets):
150 StdOffset[Dst[Offset],Date/Time,Date/Time]
151 </pre><p>
152 where:
153 </p><table class="simplelist" border="0" summary="Simple list"><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').
154 Prepend a `-' if you are ahead of UTC, and
155 append `:30' if you are at a half-hour offset.
156 Omit all the remaining items if you do not use
157 daylight-saving time.</td></tr><tr><td>`Dst' is the daylight-saving time designation
158 (e.g. `PDT').</td></tr><tr><td>The optional second `Offset' is the number of
159 hours that daylight-saving time is behind UTC.
160 The default is 1 hour ahead of standard time.
161 </td></tr><tr><td>`Date/Time,Date/Time' specify when daylight-saving
162 time starts and ends. The format for a date is
163 `Mm.n.d', which specifies the dth day (0 is Sunday)
164 of the nth week of the mth month, where week 5 means
165 the last such day in the month. The format for a
166 time is [h]h[:mm[:ss]], using a 24-hour clock.
167 </td></tr></table><p>
168 </p><p>
169 Other Posix string formats are allowed but you don't want
170 to know about them.</p><p>
171 On the client side, you must make sure that your client's clock and
172 time zone is also set appropriately. [[I don't know how to do this.]]
173 Samba traditionally has had many problems dealing with time zones, due
174 to the bizarre ways that Microsoft network protocols handle time
175 zones.
176 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811127"></a>How do I set the printer driver name correctly?</h2></div></div><p>Question:
179 following error message
182 You do not have sufficient access to your machine
183 to connect to the selected printer, since a driver
184 needs to be installed locally.
185 </pre><p>
187 driver" in smb.conf. This tells the client what driver to use. For
189 printer driver = HP LaserJet 4L
190 </pre><p>With this, NT knows to use the right driver. You have to get this string
191 exactly right.</p><p>To find the exact string to use, you need to get to the dialog box in
192 your client where you select which printer driver to install. The
193 correct strings for all the different printers are shown in a listbox
194 in that dialog box.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-Config.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. General Information </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Configuration problems</td></tr></table></div></body></html>