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.7"><LINK
11 HREF=
"samba-faq.html"><LINK
13 TITLE=
"General Information"
14 HREF=
"faq-general.html"><LINK
16 TITLE=
"Configuration problems"
17 HREF=
"faq-config.html"></HEAD
28 SUMMARY=
"Header navigation table"
45 HREF=
"faq-general.html"
59 HREF=
"faq-config.html"
74 >Chapter
2. Compiling and installing Samba on a Unix host
</H1
81 >2.1. I can't see the Samba server in any browse lists!
</A
84 >See Browsing.html in the docs directory of the samba source
85 for more information on browsing.
</P
87 >If your GUI client does not permit you to select non-browsable
88 servers, you may need to do so on the command line. For example, under
89 Lan Manager you might connect to the above service as disk drive M:
92 CLASS=
"PROGRAMLISTING"
93 > net use M: \\mary\fred
</PRE
95 The details of how to do this and the specific syntax varies from
96 client to client - check your client's documentation.
</P
104 >2.2. Some files that I KNOW are on the server don't show up when I view the files from my client!
</A
107 >See the next question.
</P
115 >2.3. Some files on the server show up with really wierd filenames when I view the files from my client!
</A
118 >If you check what files are not showing up, you will note that they
119 are files which contain upper case letters or which are otherwise not
120 DOS-compatible (ie, they are not legal DOS filenames for some reason).
</P
122 >The Samba server can be configured either to ignore such files
123 completely, or to present them to the client in
"mangled" form. If you
124 are not seeing the files at all, the Samba server has most likely been
125 configured to ignore them. Consult the man page smb.conf(
5) for
126 details of how to change this - the parameter you need to set is
127 "mangled names = yes".
</P
135 >2.4. My client reports
"cannot locate specified computer" or similar
</A
138 >This indicates one of three things: You supplied an incorrect server
139 name, the underlying TCP/IP layer is not working correctly, or the
140 name you specified cannot be resolved.
</P
142 >After carefully checking that the name you typed is the name you
143 should have typed, try doing things like pinging a host or telnetting
144 to somewhere on your network to see if TCP/IP is functioning OK. If it
145 is, the problem is most likely name resolution.
</P
147 >If your client has a facility to do so, hardcode a mapping between the
148 hosts IP and the name you want to use. For example, with Lan Manager
149 or Windows for Workgroups you would put a suitable entry in the file
150 LMHOSTS. If this works, the problem is in the communication between
151 your client and the netbios name server. If it does not work, then
152 there is something fundamental wrong with your naming and the solution
153 is beyond the scope of this document.
</P
155 >If you do not have any server on your subnet supplying netbios name
156 resolution, hardcoded mappings are your only option. If you DO have a
157 netbios name server running (such as the Samba suite's nmbd program),
158 the problem probably lies in the way it is set up. Refer to Section
159 Two of this FAQ for more ideas.
</P
161 >By the way, remember to REMOVE the hardcoded mapping before further
170 >2.5. My client reports
"cannot locate specified share name" or similar
</A
173 >This message indicates that your client CAN locate the specified
174 server, which is a good start, but that it cannot find a service of
175 the name you gave.
</P
177 >The first step is to check the exact name of the service you are
178 trying to connect to (consult your system administrator). Assuming it
179 exists and you specified it correctly (read your client's docs on how
180 to specify a service name correctly), read on:
</P
188 >Many clients cannot accept or use service names longer than eight characters.
</TD
192 >Many clients cannot accept or use service names containing spaces.
</TD
196 >Some servers (not Samba though) are case sensitive with service names.
</TD
200 >Some clients force service names into upper case.
</TD
213 >2.6. Printing doesn't work
</A
216 >Make sure that the specified print command for the service you are
217 connecting to is correct and that it has a fully-qualified path (eg.,
218 use
"/usr/bin/lpr" rather than just
"lpr").
</P
220 >Make sure that the spool directory specified for the service is
221 writable by the user connected to the service. In particular the user
222 "nobody" often has problems with printing, even if it worked with an
223 earlier version of Samba. Try creating another guest user other than
226 >Make sure that the user specified in the service is permitted to use
229 >Check the debug log produced by smbd. Search for the printer name and
230 see if the log turns up any clues. Note that error messages to do with
231 a service ipc$ are meaningless - they relate to the way the client
232 attempts to retrieve status information when using the LANMAN1
235 >If using WfWg then you need to set the default protocol to TCP/IP, not
236 Netbeui. This is a WfWg bug.
</P
238 >If using the Lanman1 protocol (the default) then try switching to
239 coreplus. Also not that print status error messages don't mean
240 printing won't work. The print status is received by a different
249 >2.7. My client reports
"This server is not configured to list shared resources"</A
252 >Your guest account is probably invalid for some reason. Samba uses the
253 guest account for browsing in smbd. Check that your guest account is
256 >See also 'guest account' in smb.conf man page.
</P
264 >2.8. Log message
"you appear to have a trapdoor uid system"</A
267 >This can have several causes. It might be because you are using a uid
268 or gid of
65535 or -
1. This is a VERY bad idea, and is a big security
269 hole. Check carefully in your /etc/passwd file and make sure that no
270 user has uid
65535 or -
1. Especially check the
"nobody" user, as many
271 broken systems are shipped with nobody setup with a uid of
65535.
</P
273 >It might also mean that your OS has a trapdoor uid/gid system :-)
</P
275 >This means that once a process changes effective uid from root to
276 another user it can't go back to root. Unfortunately Samba relies on
277 being able to change effective uid from root to non-root and back
278 again to implement its security policy. If your OS has a trapdoor uid
279 system this won't work, and several things in Samba may break. Less
280 things will break if you use user or server level security instead of
281 the default share level security, but you may still strike
284 >The problems don't give rise to any security holes, so don't panic,
285 but it does mean some of Samba's capabilities will be unavailable.
286 In particular you will not be able to connect to the Samba server as
287 two different uids at once. This may happen if you try to print as a
288 "guest" while accessing a share as a normal user. It may also affect
289 your ability to list the available shares as this is normally done as
292 >Complain to your OS vendor and ask them to fix their system.
</P
294 >Note: the reason why
65535 is a VERY bad choice of uid and gid is that
295 it casts to -
1 as a uid, and the setreuid() system call ignores (with
296 no error) uid changes to -
1. This means any daemon attempting to run
297 as uid
65535 will actually run as root. This is not good!
</P
305 >2.9. Why are my file's timestamps off by an hour, or by a few hours?
</A
308 >This is from Paul Eggert eggert@twinsun.com.
</P
310 >Most likely it's a problem with your time zone settings.
</P
312 >Internally, Samba maintains time in traditional Unix format,
313 namely, the number of seconds since
1970-
01-
01 00:
00:
00 Universal Time
314 (or ``GMT''), not counting leap seconds.
</P
316 >On the server side, Samba uses the Unix TZ variable to convert
317 internal timestamps to and from local time. So on the server side, there are
318 two things to get right.
326 >The Unix system clock must have the correct Universal time. Use the shell command
"sh -c 'TZ=UTC0 date'" to check this.
</TD
330 >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
338 >TZ must have the correct value.
</P
340 >If possible, use geographical time zone settings
341 (e.g. TZ='America/Los_Angeles' or perhaps
342 TZ=':US/Pacific'). These are supported by most
343 popular Unix OSes, are easier to get right, and are
344 more accurate for historical timestamps. If your
345 operating system has out-of-date tables, you should be
346 able to update them from the public domain time zone
348 HREF=
"ftp://elsie.nci.nih.gov/pub/"
350 >ftp://elsie.nci.nih.gov/pub/
</A
353 >If your system does not support geographical timezone
354 settings, you must use a Posix-style TZ strings, e.g.
355 TZ='PST8PDT,M4.1
.0/
2,M10.5
.0/
2' for US Pacific time.
356 Posix TZ strings can take the following form (with optional
359 CLASS=
"PROGRAMLISTING"
360 > StdOffset[Dst[Offset],Date/Time,Date/Time]
</PRE
371 >`Std' is the standard time designation (e.g. `PST').
</TD
375 >`Offset' is the number of hours behind UTC (e.g. `
8').
376 Prepend a `-' if you are ahead of UTC, and
377 append `:
30' if you are at a half-hour offset.
378 Omit all the remaining items if you do not use
379 daylight-saving time.
</TD
383 >`Dst' is the daylight-saving time designation
388 >The optional second `Offset' is the number of
389 hours that daylight-saving time is behind UTC.
390 The default is
1 hour ahead of standard time.
</TD
394 >`Date/Time,Date/Time' specify when daylight-saving
395 time starts and ends. The format for a date is
396 `Mm.n.d', which specifies the dth day (
0 is Sunday)
397 of the nth week of the mth month, where week
5 means
398 the last such day in the month. The format for a
399 time is [h]h[:mm[:ss]], using a
24-hour clock.
</TD
407 >Other Posix string formats are allowed but you don't want
408 to know about them.
</P
410 >On the client side, you must make sure that your client's clock and
411 time zone is also set appropriately. [[I don't know how to do this.]]
412 Samba traditionally has had many problems dealing with time zones, due
413 to the bizarre ways that Microsoft network protocols handle time
422 >2.10. How do I set the printer driver name correctly?
</A
428 >" On NT, I opened "Printer Manager
" and "Connect to Printer
".
429 Enter ["\\ptdi270\ps1
"] in the box of printer. I got the
430 following error message
435 CLASS=
"PROGRAMLISTING"
436 > You do not have sufficient access to your machine
437 to connect to the selected printer, since a driver
438 needs to be installed locally.
445 >In the more recent versions of Samba you can now set the
"printer
446 driver" in smb.conf. This tells the client what driver to use. For
450 CLASS=
"PROGRAMLISTING"
451 > printer driver = HP LaserJet
4L</PRE
454 >With this, NT knows to use the right driver. You have to get this string
457 >To find the exact string to use, you need to get to the dialog box in
458 your client where you select which printer driver to install. The
459 correct strings for all the different printers are shown in a listbox
460 in that dialog box.
</P
468 SUMMARY=
"Footer navigation table"
479 HREF=
"faq-general.html"
488 HREF=
"samba-faq.html"
497 HREF=
"faq-config.html"
507 >General Information
</TD
517 >Configuration problems
</TD