1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Compiling and installing Samba on a Unix host</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
12 HREF="samba-faq.html"><LINK
14 TITLE="General Information"
15 HREF="general.html"><LINK
17 TITLE="Configuration problems"
18 HREF="config.html"></HEAD
29 SUMMARY="Header navigation table"
73 NAME="INSTALL">Chapter 2. Compiling and installing Samba on a Unix host</H1
79 NAME="AEN84">2.1. I can't see the Samba server in any browse lists!</H1
81 >See Browsing.html in the docs directory of the samba source
82 for more information on browsing.</P
84 >If your GUI client does not permit you to select non-browsable
85 servers, you may need to do so on the command line. For example, under
86 Lan Manager you might connect to the above service as disk drive M:
89 CLASS="PROGRAMLISTING"
90 > net use M: \\mary\fred</PRE
92 The details of how to do this and the specific syntax varies from
93 client to client - check your client's documentation.</P
100 NAME="AEN89">2.2. Some files that I KNOW are on the server doesn't show up when I view the files from my client!</H1
102 >See the next question.</P
109 NAME="AEN92">2.3. Some files on the server show up with really wierd filenames when I view the files from my client!</H1
111 >If you check what files are not showing up, you will note that they
112 are files which contain upper case letters or which are otherwise not
113 DOS-compatible (ie, they are not legal DOS filenames for some reason).</P
115 >The Samba server can be configured either to ignore such files
116 completely, or to present them to the client in "mangled" form. If you
117 are not seeing the files at all, the Samba server has most likely been
118 configured to ignore them. Consult the man page smb.conf(5) for
119 details of how to change this - the parameter you need to set is
120 "mangled names = yes".</P
127 NAME="AEN96">2.4. My client reports "cannot locate specified computer" or similar</H1
129 >This indicates one of three things: You supplied an incorrect server
130 name, the underlying TCP/IP layer is not working correctly, or the
131 name you specified cannot be resolved.</P
133 >After carefully checking that the name you typed is the name you
134 should have typed, try doing things like pinging a host or telnetting
135 to somewhere on your network to see if TCP/IP is functioning OK. If it
136 is, the problem is most likely name resolution.</P
138 >If your client has a facility to do so, hardcode a mapping between the
139 hosts IP and the name you want to use. For example, with Lan Manager
140 or Windows for Workgroups you would put a suitable entry in the file
141 LMHOSTS. If this works, the problem is in the communication between
142 your client and the netbios name server. If it does not work, then
143 there is something fundamental wrong with your naming and the solution
144 is beyond the scope of this document.</P
146 >If you do not have any server on your subnet supplying netbios name
147 resolution, hardcoded mappings are your only option. If you DO have a
148 netbios name server running (such as the Samba suite's nmbd program),
149 the problem probably lies in the way it is set up. Refer to Section
150 Two of this FAQ for more ideas.</P
152 >By the way, remember to REMOVE the hardcoded mapping before further
160 NAME="AEN103">2.5. My client reports "cannot locate specified share name" or similar</H1
162 >This message indicates that your client CAN locate the specified
163 server, which is a good start, but that it cannot find a service of
164 the name you gave.</P
166 >The first step is to check the exact name of the service you are
167 trying to connect to (consult your system administrator). Assuming it
168 exists and you specified it correctly (read your client's docs on how
169 to specify a service name correctly), read on:</P
177 >Many clients cannot accept or use service names longer than eight characters.</TD
181 >Many clients cannot accept or use service names containing spaces.</TD
185 >Some servers (not Samba though) are case sensitive with service names.</TD
189 >Some clients force service names into upper case.</TD
201 NAME="AEN112">2.6. Printing doesn't work</H1
203 >Make sure that the specified print command for the service you are
204 connecting to is correct and that it has a fully-qualified path (eg.,
205 use "/usr/bin/lpr" rather than just "lpr").</P
207 >Make sure that the spool directory specified for the service is
208 writable by the user connected to the service. In particular the user
209 "nobody" often has problems with printing, even if it worked with an
210 earlier version of Samba. Try creating another guest user other than
213 >Make sure that the user specified in the service is permitted to use
216 >Check the debug log produced by smbd. Search for the printer name and
217 see if the log turns up any clues. Note that error messages to do with
218 a service ipc$ are meaningless - they relate to the way the client
219 attempts to retrieve status information when using the LANMAN1
222 >If using WfWg then you need to set the default protocol to TCP/IP, not
223 Netbeui. This is a WfWg bug.</P
225 >If using the Lanman1 protocol (the default) then try switching to
226 coreplus. Also not that print status error messages don't mean
227 printing won't work. The print status is received by a different
235 NAME="AEN120">2.7. My client reports "This server is not configured to list shared resources"</H1
237 >Your guest account is probably invalid for some reason. Samba uses the
238 guest account for browsing in smbd. Check that your guest account is
241 >See also 'guest account' in smb.conf man page.</P
248 NAME="AEN124">2.8. Log message "you appear to have a trapdoor uid system"</H1
250 >This can have several causes. It might be because you are using a uid
251 or gid of 65535 or -1. This is a VERY bad idea, and is a big security
252 hole. Check carefully in your /etc/passwd file and make sure that no
253 user has uid 65535 or -1. Especially check the "nobody" user, as many
254 broken systems are shipped with nobody setup with a uid of 65535.</P
256 >It might also mean that your OS has a trapdoor uid/gid system :-)</P
258 >This means that once a process changes effective uid from root to
259 another user it can't go back to root. Unfortunately Samba relies on
260 being able to change effective uid from root to non-root and back
261 again to implement its security policy. If your OS has a trapdoor uid
262 system this won't work, and several things in Samba may break. Less
263 things will break if you use user or server level security instead of
264 the default share level security, but you may still strike
267 >The problems don't give rise to any security holes, so don't panic,
268 but it does mean some of Samba's capabilities will be unavailable.
269 In particular you will not be able to connect to the Samba server as
270 two different uids at once. This may happen if you try to print as a
271 "guest" while accessing a share as a normal user. It may also affect
272 your ability to list the available shares as this is normally done as
275 >Complain to your OS vendor and ask them to fix their system.</P
277 >Note: the reason why 65535 is a VERY bad choice of uid and gid is that
278 it casts to -1 as a uid, and the setreuid() system call ignores (with
279 no error) uid changes to -1. This means any daemon attempting to run
280 as uid 65535 will actually run as root. This is not good!</P
287 NAME="AEN132">2.9. Why are my file's timestamps off by an hour, or by a few hours?</H1
289 >This is from Paul Eggert eggert@twinsun.com.</P
291 >Most likely it's a problem with your time zone settings.</P
293 >Internally, Samba maintains time in traditional Unix format,
294 namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
295 (or ``GMT''), not counting leap seconds.</P
297 >On the server side, Samba uses the Unix TZ variable to convert
298 internal timestamps to and from local time. So on the server side, there are
299 two things to get right.
307 >The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</TD
311 >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
319 >TZ must have the correct value.</P
321 >If possible, use geographical time zone settings
322 (e.g. TZ='America/Los_Angeles' or perhaps
323 TZ=':US/Pacific'). These are supported by most
324 popular Unix OSes, are easier to get right, and are
325 more accurate for historical timestamps. If your
326 operating system has out-of-date tables, you should be
327 able to update them from the public domain time zone
329 HREF="ftp://elsie.nci.nih.gov/pub/"
331 >ftp://elsie.nci.nih.gov/pub/</A
334 >If your system does not support geographical timezone
335 settings, you must use a Posix-style TZ strings, e.g.
336 TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
337 Posix TZ strings can take the following form (with optional
340 CLASS="PROGRAMLISTING"
341 > StdOffset[Dst[Offset],Date/Time,Date/Time]</PRE
352 >`Std' is the standard time designation (e.g. `PST').</TD
356 >`Offset' is the number of hours behind UTC (e.g. `8').
357 Prepend a `-' if you are ahead of UTC, and
358 append `:30' if you are at a half-hour offset.
359 Omit all the remaining items if you do not use
360 daylight-saving time.</TD
364 >`Dst' is the daylight-saving time designation
369 >The optional second `Offset' is the number of
370 hours that daylight-saving time is behind UTC.
371 The default is 1 hour ahead of standard time.</TD
375 >`Date/Time,Date/Time' specify when daylight-saving
376 time starts and ends. The format for a date is
377 `Mm.n.d', which specifies the dth day (0 is Sunday)
378 of the nth week of the mth month, where week 5 means
379 the last such day in the month. The format for a
380 time is [h]h[:mm[:ss]], using a 24-hour clock.</TD
388 >Other Posix string formats are allowed but you don't want
389 to know about them.</P
391 >On the client side, you must make sure that your client's clock and
392 time zone is also set appropriately. [[I don't know how to do this.]]
393 Samba traditionally has had many problems dealing with time zones, due
394 to the bizarre ways that Microsoft network protocols handle time
402 NAME="AEN155">2.10. How do I set the printer driver name correctly?</H1
407 >" On NT, I opened "Printer Manager" and "Connect to Printer".
408 Enter ["\\ptdi270\ps1"] in the box of printer. I got the
409 following error message
414 CLASS="PROGRAMLISTING"
415 > You do not have sufficient access to your machine
416 to connect to the selected printer, since a driver
417 needs to be installed locally.
424 >In the more recent versions of Samba you can now set the "printer
425 driver" in smb.conf. This tells the client what driver to use. For
429 CLASS="PROGRAMLISTING"
430 > printer driver = HP LaserJet 4L</PRE
433 >With this, NT knows to use the right driver. You have to get this string
436 >To find the exact string to use, you need to get to the dialog box in
437 your client where you select which printer driver to install. The
438 correct strings for all the different printers are shown in a listbox
439 in that dialog box.</P
447 SUMMARY="Footer navigation table"
467 HREF="samba-faq.html"
486 >General Information</TD
496 >Configuration problems</TD
git.samba.org / kai / samba.git / blob