2 Paul Blackman, i
\bic
\bct
\bti
\bin
\bnu
\bus
\bs@
\b@l
\bla
\bak
\bke
\be.
\b.c
\bca
\ban
\bnb
\bbe
\ber
\brr
\bra
\ba.
\b.e
\bed
\bdu
\bu.
\b.a
\bau
\bu
5 This is the Frequently Asked Questions (FAQ) document for Samba, the
6 free and very popular SMB server product. An SMB server allows file
7 and printer connections from clients such as Windows, OS/2, Linux and
8 others. Current to version 1.9.17. Please send any corrections to the
11 1
\b1.
\b. G
\bGe
\ben
\bne
\ber
\bra
\bal
\bl I
\bIn
\bnf
\bfo
\bor
\brm
\bma
\bat
\bti
\bio
\bon
\bn
15 All about Samba - what it is, how to get it, related sources of
16 information, how to understand the version numbering scheme, pizza
20 1
\b1.
\b.1
\b1.
\b. W
\bWh
\bha
\bat
\bt i
\bis
\bs S
\bSa
\bam
\bmb
\bba
\ba?
\b?
24 Samba is a suite of programs which work together to allow clients to
25 access to a server's filespace and printers via the SMB (Server
26 Message Block) protocol. Initially written for Unix, Samba now also
27 runs on Netware, OS/2 and VMS.
29 In practice, this means that you can redirect disks and printers to
30 Unix disks and printers from Lan Manager clients, Windows for
31 Workgroups 3.11 clients, Windows NT clients, Linux clients and OS/2
32 clients. There is also a generic Unix client program supplied as part
33 of the suite which allows Unix users to use an ftp-like interface to
34 access filespace and printers on any other SMB servers. This gives the
35 capability for these operating systems to behave much like a LAN
36 Server or Windows NT Server machine, only with added functionality and
37 flexibility designed to make life easier for administrators.
39 The components of the suite are (in summary):
42 · smbd, the SMB server. This handles actual connections from clients,
43 doing all the file, permission and username work
45 · nmbd, the Netbios name server, which helps clients locate servers,
46 doing the browsing work and managing domains as this capability is
47 being built into Samba
49 · smbclient, the Unix-hosted client program
51 · smbrun, a little 'glue' program to help the server run external
54 · testprns, a program to test server access to printers
56 · testparms, a program to test the Samba configuration file for
59 · smb.conf, the Samba configuration file
61 · smbprint, a sample script to allow a Unix host to use smbclient to
62 print to an SMB server
64 · documentation! DON'T neglect to read it - you will save a great
67 The suite is supplied with full source (of course!) and is GPLed.
69 The primary creator of the Samba suite is Andrew Tridgell. Later
70 versions incorporate much effort by many net.helpers. The man pages
71 and this FAQ were originally written by Karl Auer.
74 1
\b1.
\b.2
\b2.
\b. W
\bWh
\bha
\bat
\bt i
\bis
\bs t
\bth
\bhe
\be c
\bcu
\bur
\brr
\bre
\ben
\bnt
\bt v
\bve
\ber
\brs
\bsi
\bio
\bon
\bn o
\bof
\bf S
\bSa
\bam
\bmb
\bba
\ba?
\b?
78 At time of writing, the current version was 1.9.16. If you want to be
79 sure check the bottom of the change-log file.
80 <f
\bft
\btp
\bp:
\b:/
\b//
\b/s
\bsa
\bam
\bmb
\bba
\ba.
\b.a
\ban
\bnu
\bu.
\b.e
\bed
\bdu
\bu.
\b.a
\bau
\bu/
\b/p
\bpu
\bub
\bb/
\b/s
\bsa
\bam
\bmb
\bba
\ba/
\b/a
\bal
\blp
\bph
\bha
\ba/
\b/c
\bch
\bha
\ban
\bng
\bge
\be-
\b-l
\blo
\bog
\bg>
82 For more information see ``What do the version numbers mean?''
85 1
\b1.
\b.3
\b3.
\b. W
\bWh
\bhe
\ber
\bre
\be c
\bca
\ban
\bn I
\bI g
\bge
\bet
\bt i
\bit
\bt?
\b?
89 The Samba suite is available via anonymous ftp from samba.anu.edu.au.
90 The latest and greatest versions of the suite are in the directory:
94 Development (read "alpha") versions, which are NOT necessarily stable
95 and which do NOT necessarily have accurate documentation, are
96 available in the directory:
100 Note that binaries are NOT included in any of the above. Samba is
101 distributed ONLY in source form, though binaries may be available from
102 other sites. Recent versions of some Linux distributions, for example,
103 do contain Samba binaries for that platform.
106 1
\b1.
\b.4
\b4.
\b. W
\bWh
\bha
\bat
\bt d
\bdo
\bo t
\bth
\bhe
\be v
\bve
\ber
\brs
\bsi
\bio
\bon
\bn n
\bnu
\bum
\bmb
\bbe
\ber
\brs
\bs m
\bme
\bea
\ban
\bn?
\b?
110 It is not recommended that you run a version of Samba with the word
111 "alpha" in its name unless you know what you are doing and are willing
112 to do some debugging. Many, many people just get the latest
113 recommended stable release version and are happy. If you are brave, by
114 all means take the plunge and help with the testing and development -
115 but don't install it on your departmental server. Samba is typically
116 very stable and safe, and this is mostly due to the policy of many
119 How the scheme works:
121 1. when major changes are made the version number is increased. For
122 example, the transition from 1.9.15 to 1.9.16. However, this
123 version number will not appear immediately and people should
124 continue to use 1.9.15 for production systems (see next point.)
126 2. just after major changes are made the software is considered
127 unstable, and a series of alpha releases are distributed, for
128 example 1.9.16alpha1. These are for testing by those who know what
129 they are doing. The "alpha" in the filename will hopefully scare
130 off those who are just looking for the latest version to install.
133 3. when Andrew thinks that the alphas have stabilised to the point
134 where he would recommend new users install it, he renames it to the
135 same version number without the alpha, for example 1.9.16.
137 4. inevitably bugs are found in the "stable" releases and minor patch
138 levels are released which give us the pXX series, for example
141 So the progression goes:
143 1.9.15p7 (production)
144 1.9.15p8 (production)
145 1.9.16alpha1 (test sites only)
147 1.9.16alpha20 (test sites only)
149 1.9.16p1 (production)
152 The above system means that whenever someone looks at the samba ftp
153 site they will be able to grab the highest numbered release without an
154 alpha in the name and be sure of getting the current recommended ver
158 1
\b1.
\b.5
\b5.
\b. W
\bWh
\bha
\bat
\bt p
\bpl
\bla
\bat
\btf
\bfo
\bor
\brm
\bms
\bs a
\bar
\bre
\be s
\bsu
\bup
\bpp
\bpo
\bor
\brt
\bte
\bed
\bd?
\b?
162 Many different platforms have run Samba successfully. The platforms
163 most widely used and thus best tested are Linux and SunOS.
165 At time of writing, the Makefile claimed support for:
169 · Linux with shadow passwords
171 · Linux without shadow passwords
175 · SOLARIS 2.2 and above (aka SunOS 5)
183 · OSF1 with NIS and Fast Crypt (alpha only)
185 · OSF1 V2.0 Enhanced Security (alpha only)
213 · ISC SVR3V4 (POSIX mode)
215 · ISC SVR3V4 (iBCS2 mode)
219 · SCO with shadow passwords.
221 · SCO with shadow passwords, without YP.
223 · SCO with TCB passwords
225 · SCO 3.2v2 (ODT 1.1) with TCP passwords
231 · Apollo Domain/OS sr10.3 (BSD4.3)
234 1
\b1.
\b.6
\b6.
\b. H
\bHo
\bow
\bw c
\bca
\ban
\bn I
\bI f
\bfi
\bin
\bnd
\bd o
\bou
\but
\bt m
\bmo
\bor
\bre
\be a
\bab
\bbo
\bou
\but
\bt S
\bSa
\bam
\bmb
\bba
\ba?
\b?
238 There are two mailing lists devoted to discussion of Samba-related
239 matters. There is also the newsgroup, comp.protocols.smb, which has a
240 great deal of discussion on Samba. There is also a WWW site 'SAMBA Web
241 Pages' at <h
\bht
\btt
\btp
\bp:
\b:/
\b//
\b/s
\bsa
\bam
\bmb
\bba
\ba.
\b.c
\bca
\ban
\bnb
\bbe
\ber
\brr
\bra
\ba.
\b.e
\bed
\bdu
\bu.
\b.a
\bau
\bu/
\b/p
\bpu
\bub
\bb/
\b/s
\bsa
\bam
\bmb
\bba
\ba/
\b/s
\bsa
\bam
\bmb
\bba
\ba.
\b.h
\bht
\btm
\bml
\bl>, under
242 which there is a comprehensive survey of Samba users. Another useful
243 resource is the hypertext archive of the Samba mailing list.
245 Send email to listproc@samba.anu.edu.au. Make sure the subject line is
246 blank, and include the following two lines in the body of the message:
250 subscribe samba Firstname Lastname
251 subscribe samba-announce Firstname Lastname
256 Obviously you should substitute YOUR first name for "Firstname" and
257 YOUR last name for "Lastname"! Try not to send any signature stuff, it
258 sometimes confuses the list processor.
260 The samba list is a digest list - every eight hours or so it
261 regurgitates a single message containing all the messages that have
262 been received by the list since the last time and sends a copy of this
263 message to all subscribers.
265 If you stop being interested in Samba, please send another email to
266 listproc@samba.anu.edu.au. Make sure the subject line is blank, and
267 include the following two lines in the body of the message:
272 unsubscribe samba-announce
277 The F
\bFr
\bro
\bom
\bm:
\b: line in your message _
\bM_
\bU_
\bS_
\bT be the same address you used when
281 1
\b1.
\b.7
\b7.
\b. S
\bSo
\bom
\bme
\bet
\bth
\bhi
\bin
\bng
\bg'
\b's
\bs g
\bgo
\bon
\bne
\be w
\bwr
\bro
\bon
\bng
\bg -
\b- w
\bwh
\bha
\bat
\bt s
\bsh
\bho
\bou
\bul
\bld
\bd I
\bI d
\bdo
\bo?
\b?
285 #
\b# *
\b**
\b**
\b* I
\bIM
\bMP
\bPO
\bOR
\bRT
\bTA
\bAN
\bNT
\bT!
\b! *
\b**
\b**
\b* #
\b#
287 DO NOT post messages on mailing lists or in newsgroups until you have
288 carried out the first three steps given here!
290 Firstly, see if there are any likely looking entries in this FAQ! If
291 you have just installed Samba, have you run through the checklist in
292 DIAGNOSIS.txt <f
\bft
\btp
\bp:
\b:/
\b//
\b/s
\bsa
\bam
\bmb
\bba
\ba.
\b.a
\ban
\bnu
\bu.
\b.e
\bed
\bdu
\bu.
\b.a
\bau
\bu/
\b/p
\bpu
\bub
\bb/
\b/s
\bsa
\bam
\bmb
\bba
\ba/
\b/D
\bDI
\bIA
\bAG
\bGN
\bNO
\bOS
\bSI
\bIS
\bS.
\b.t
\btx
\bxt
\bt>? It can
293 save you a lot of time and effort.
295 Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
296 topics that relate to what you are trying to do.
298 Thirdly, if there is no obvious solution to hand, try to get a look at
299 the log files for smbd and/or nmbd for the period during which you
300 were having problems. You may need to reconfigure the servers to
301 provide more extensive debugging information - usually level 2 or
302 level 3 provide ample debugging info. Inspect these logs closely,
303 looking particularly for the string "Error:".
305 Fourthly, if you still haven't got anywhere, ask the mailing list or
306 newsgroup. In general nobody minds answering questions provided you
307 have followed the preceding steps. It might be a good idea to scan the
308 archives of the mailing list, which are available through the Samba
309 web site described in the previous section.
311 If you successfully solve a problem, please mail the FAQ maintainer a
312 succinct description of the symptom, the problem and the solution, so
313 I can incorporate it in the next version.
315 If you make changes to the source code, _please_ submit these patches
316 so that everyone else gets the benefit of your work. This is one of
317 the most important aspects to the maintainence of Samba. Send all
318 patches to samba-bugs@samba.anu.edu.au, not Andrew Tridgell or any
319 other individual and not the samba team mailing list.
322 1
\b1.
\b.8
\b8.
\b. P
\bPi
\biz
\bzz
\bza
\ba s
\bsu
\bup
\bpp
\bpl
\bly
\by d
\bde
\bet
\bta
\bai
\bil
\bls
\bs
326 Those who have registered in the Samba survey as "Pizza Factory" will
327 already know this, but the rest may need some help. Andrew doesn't ask
328 for payment, but he does appreciate it when people give him pizza.
329 This calls for a little organisation when the pizza donor is twenty
330 thousand kilometres away, but it has been done.
331 Method 1: Ring up your local branch of an international pizza chain
332 and see if they honour their vouchers internationally. Pizza Hut do,
333 which is how the entire Canberra Linux Users Group got to eat pizza
334 one night, courtesy of someone in the US
336 Method 2: Ring up a local pizza shop in Canberra and quote a credit
337 card number for a certain amount, and tell them that Andrew will be
338 collecting it (don't forget to tell him.) One kind soul from Germany
341 Method 3: Purchase a pizza voucher from your local pizza shop that has
342 no international affiliations and send it to Andrew. It is completely
343 useless but he can hang it on the wall next to the one he already has
346 Method 4: Air freight him a pizza with your favourite regional
347 flavours. It will probably get stuck in customs or torn apart by
348 hungry sniffer dogs but it will have been a noble gesture.
351 2
\b2.
\b. C
\bCo
\bom
\bmp
\bpi
\bil
\bli
\bin
\bng
\bg a
\ban
\bnd
\bd i
\bin
\bns
\bst
\bta
\bal
\bll
\bli
\bin
\bng
\bg S
\bSa
\bam
\bmb
\bba
\ba o
\bon
\bn a
\ba U
\bUn
\bni
\bix
\bx h
\bho
\bos
\bst
\bt
356 2
\b2.
\b.1
\b1.
\b. I
\bI c
\bca
\ban
\bn'
\b't
\bt s
\bse
\bee
\be t
\bth
\bhe
\be S
\bSa
\bam
\bmb
\bba
\ba s
\bse
\ber
\brv
\bve
\ber
\br i
\bin
\bn a
\ban
\bny
\by b
\bbr
\bro
\bow
\bws
\bse
\be l
\bli
\bis
\bst
\bts
\bs!
\b!
359 See BROWSING.txt <f
\bft
\btp
\bp:
\b:/
\b//
\b/s
\bsa
\bam
\bmb
\bba
\ba.
\b.a
\ban
\bnu
\bu.
\b.e
\bed
\bdu
\bu.
\b.a
\bau
\bu/
\b/p
\bpu
\bub
\bb/
\b/s
\bsa
\bam
\bmb
\bba
\ba/
\b/B
\bBR
\bRO
\bOW
\bWS
\bSI
\bIN
\bNG
\bG.
\b.t
\btx
\bxt
\bt> for
360 more information on browsing. Browsing.txt can also be found in the
361 docs directory of the Samba source.
363 If your GUI client does not permit you to select non-browsable
364 servers, you may need to do so on the command line. For example, under
365 Lan Manager you might connect to the above service as disk drive M:
370 The details of how to do this and the specific syntax varies from
371 client to client - check your client's documentation.
374 2
\b2.
\b.2
\b2.
\b. S
\bSo
\bom
\bme
\be f
\bfi
\bil
\ble
\bes
\bs t
\bth
\bha
\bat
\bt I
\bI K
\bKN
\bNO
\bOW
\bW a
\bar
\bre
\be o
\bon
\bn t
\bth
\bhe
\be s
\bse
\ber
\brv
\bve
\ber
\br d
\bdo
\boe
\bes
\bsn
\bn'
\b't
\bt s
\bsh
\bho
\bow
\bw u
\bup
\bp w
\bwh
\bhe
\ben
\bn I
\bI
375 v
\bvi
\bie
\bew
\bw t
\bth
\bhe
\be f
\bfi
\bil
\ble
\bes
\bs f
\bfr
\bro
\bom
\bm m
\bmy
\by c
\bcl
\bli
\bie
\ben
\bnt
\bt!
\b!
380 2
\b2.
\b.3
\b3.
\b. S
\bSo
\bom
\bme
\be f
\bfi
\bil
\ble
\bes
\bs o
\bon
\bn t
\bth
\bhe
\be s
\bse
\ber
\brv
\bve
\ber
\br s
\bsh
\bho
\bow
\bw u
\bup
\bp w
\bwi
\bit
\bth
\bh r
\bre
\bea
\bal
\bll
\bly
\by w
\bwi
\bie
\ber
\brd
\bd f
\bfi
\bil
\ble
\ben
\bna
\bam
\bme
\bes
\bs
381 w
\bwh
\bhe
\ben
\bn I
\bI v
\bvi
\bie
\bew
\bw t
\bth
\bhe
\be f
\bfi
\bil
\ble
\bes
\bs f
\bfr
\bro
\bom
\bm m
\bmy
\by c
\bcl
\bli
\bie
\ben
\bnt
\bt!
\b!
385 If you check what files are not showing up, you will note that they
386 are files which contain upper case letters or which are otherwise not
387 DOS-compatible (ie, they are not legal DOS filenames for some reason).
389 The Samba server can be configured either to ignore such files
390 completely, or to present them to the client in "mangled" form. If you
391 are not seeing the files at all, the Samba server has most likely been
392 configured to ignore them. Consult the man page smb.conf(5) for
393 details of how to change this - the parameter you need to set is
394 "mangled names = yes".
397 2
\b2.
\b.4
\b4.
\b. M
\bMy
\by c
\bcl
\bli
\bie
\ben
\bnt
\bt r
\bre
\bep
\bpo
\bor
\brt
\bts
\bs "
\b"c
\bca
\ban
\bnn
\bno
\bot
\bt l
\blo
\boc
\bca
\bat
\bte
\be s
\bsp
\bpe
\bec
\bci
\bif
\bfi
\bie
\bed
\bd c
\bco
\bom
\bmp
\bpu
\but
\bte
\ber
\br"
\b" o
\bor
\br s
\bsi
\bim
\bmi
\bil
\bla
\bar
\br
401 This indicates one of three things: You supplied an incorrect server
402 name, the underlying TCP/IP layer is not working correctly, or the
403 name you specified cannot be resolved.
405 After carefully checking that the name you typed is the name you
406 should have typed, try doing things like pinging a host or telnetting
407 to somewhere on your network to see if TCP/IP is functioning OK. If it
408 is, the problem is most likely name resolution.
410 If your client has a facility to do so, hardcode a mapping between the
411 hosts IP and the name you want to use. For example, with Man Manager
412 or Windows for Workgroups you would put a suitable entry in the file
413 LMHOSTS. If this works, the problem is in the communication between
414 your client and the netbios name server. If it does not work, then
415 there is something fundamental wrong with your naming and the solution
416 is beyond the scope of this document.
418 If you do not have any server on your subnet supplying netbios name
419 resolution, hardcoded mappings are your only option. If you DO have a
420 netbios name server running (such as the Samba suite's nmbd program),
421 the problem probably lies in the way it is set up. Refer to Section
422 Two of this FAQ for more ideas.
424 By the way, remember to REMOVE the hardcoded mapping before further
428 2
\b2.
\b.5
\b5.
\b. M
\bMy
\by c
\bcl
\bli
\bie
\ben
\bnt
\bt r
\bre
\bep
\bpo
\bor
\brt
\bts
\bs "
\b"c
\bca
\ban
\bnn
\bno
\bot
\bt l
\blo
\boc
\bca
\bat
\bte
\be s
\bsp
\bpe
\bec
\bci
\bif
\bfi
\bie
\bed
\bd s
\bsh
\bha
\bar
\bre
\be n
\bna
\bam
\bme
\be"
\b" o
\bor
\br s
\bsi
\bim
\bmi
\bi
\b
433 This message indicates that your client CAN locate the specified
434 server, which is a good start, but that it cannot find a service of
437 The first step is to check the exact name of the service you are
438 trying to connect to (consult your system administrator). Assuming it
439 exists and you specified it correctly (read your client's doco on how
440 to specify a service name correctly), read on:
443 · Many clients cannot accept or use service names longer than eight
446 · Many clients cannot accept or use service names containing spaces.
448 · Some servers (not Samba though) are case sensitive with service
451 · Some clients force service names into upper case.
454 2
\b2.
\b.6
\b6.
\b. o
\bon
\bn t
\bto
\bo t
\bth
\bhe
\be n
\bne
\bet
\btw
\bwo
\bor
\brk
\bk"
\b" o
\bor
\br s
\bsi
\bim
\bmi
\bil
\bla
\bar
\br M
\bMy
\by c
\bcl
\bli
\bie
\ben
\bnt
\bt r
\bre
\bep
\bpo
\bor
\brt
\bts
\bs "
\b"c
\bca
\ban
\bnn
\bno
\bot
\bt f
\bfi
\bin
\bnd
\bd
455 d
\bdo
\bom
\bma
\bai
\bin
\bn c
\bco
\bon
\bnt
\btr
\bro
\bol
\bll
\ble
\ber
\br"
\b",
\b, "
\b"c
\bca
\ban
\bnn
\bno
\bot
\bt l
\blo
\bog
\bg
459 Nothing is wrong - Samba does not implement the primary domain name
460 controller stuff for several reasons, including the fact that the
461 whole concept of a primary domain controller and "logging in to a
462 network" doesn't fit well with clients possibly running on multiuser
463 machines (such as users of smbclient under Unix). Having said that,
464 several developers are working hard on building it in to the next
465 major version of Samba. If you can contribute, send a message to
468 Seeing this message should not affect your ability to mount redirected
469 disks and printers, which is really what all this is about.
471 For many clients (including Windows for Workgroups and Lan Manager),
472 setting the domain to STANDALONE at least gets rid of the message.
475 2
\b2.
\b.7
\b7.
\b. P
\bPr
\bri
\bin
\bnt
\bti
\bin
\bng
\bg d
\bdo
\boe
\bes
\bsn
\bn'
\b't
\bt w
\bwo
\bor
\brk
\bk :
\b:-
\b-(
\b(
479 Make sure that the specified print command for the service you are
480 connecting to is correct and that it has a fully-qualified path (eg.,
481 use "/usr/bin/lpr" rather than just "lpr").
483 Make sure that the spool directory specified for the service is
484 writable by the user connected to the service. In particular the user
485 "nobody" often has problems with printing, even if it worked with an
486 earlier version of Samba. Try creating another guest user other than
489 Make sure that the user specified in the service is permitted to use
492 Check the debug log produced by smbd. Search for the printer name and
493 see if the log turns up any clues. Note that error messages to do with
494 a service ipc$ are meaningless - they relate to the way the client
495 attempts to retrieve status information when using the LANMAN1
498 If using WfWg then you need to set the default protocol to TCP/IP, not
499 Netbeui. This is a WfWg bug.
501 If using the Lanman1 protocol (the default) then try switching to
502 coreplus. Also not that print status error messages don't mean
503 printing won't work. The print status is received by a different
507 2
\b2.
\b.8
\b8.
\b. M
\bMy
\by p
\bpr
\bro
\bog
\bgr
\bra
\bam
\bms
\bs i
\bin
\bns
\bst
\bta
\bal
\bll
\bl o
\bon
\bn t
\bth
\bhe
\be s
\bse
\ber
\brv
\bve
\ber
\br O
\bOK
\bK,
\b, b
\bbu
\but
\bt r
\bre
\bef
\bfu
\bus
\bse
\be t
\bto
\bo w
\bwo
\bor
\brk
\bk p
\bpr
\bro
\bop
\bp
\b
511 There are numerous possible reasons for this, but one MAJOR
512 possibility is that your software uses locking. Make sure you are
513 using Samba 1.6.11 or later. It may also be possible to work around
514 the problem by setting "locking=no" in the Samba configuration file
515 for the service the software is installed on. This should be regarded
516 as a strictly temporary solution.
518 In earlier Samba versions there were some difficulties with the very
519 latest Microsoft products, particularly Excel 5 and Word for Windows
520 6. These should have all been solved. If not then please let Andrew
521 Tridgell know via email at samba-bugs@anu.edu.au.
524 2
\b2.
\b.9
\b9.
\b. M
\bMy
\by "
\b"s
\bse
\ber
\brv
\bve
\ber
\br s
\bst
\btr
\bri
\bin
\bng
\bg"
\b" d
\bdo
\boe
\bes
\bsn
\bn'
\b't
\bt s
\bse
\bee
\bem
\bm t
\bto
\bo b
\bbe
\be r
\bre
\bec
\bco
\bog
\bgn
\bni
\bis
\bse
\bed
\bd
527 my client reports the default setting, eg. "Samba 1.9.15p4", instead
528 of what I have changed it to in the smb.conf file.
529 You need to use the -C option in nmbd. The "server string" affects
530 what smbd puts out and -C affects what nmbd puts out. Current
531 versions of Samba (1.9.16p11 +) have combined these options into the
532 "server string" field of smb.conf, -C for nmbd is now obsolete.
535 2
\b2.
\b.1
\b10
\b0.
\b. r
\bre
\bes
\bso
\bou
\bur
\brc
\bce
\bes
\bs"
\b" M
\bMy
\by c
\bcl
\bli
\bie
\ben
\bnt
\bt r
\bre
\bep
\bpo
\bor
\brt
\bts
\bs "
\b"T
\bTh
\bhi
\bis
\bs s
\bse
\ber
\brv
\bve
\ber
\br i
\bis
\bs n
\bno
\bot
\bt c
\bco
\bon
\bnf
\bfi
\big
\bgu
\bur
\bre
\bed
\bd t
\bto
\bo
536 l
\bli
\bis
\bst
\bt s
\bsh
\bha
\bar
\bre
\bed
\bd
540 Your guest account is probably invalid for some reason. Samba uses the
541 guest account for browsing in smbd. Check that your guest account is
544 See also 'guest account' in smb.conf man page.
547 2
\b2.
\b.1
\b11
\b1.
\b. L
\bLo
\bog
\bg m
\bme
\bes
\bss
\bsa
\bag
\bge
\be "
\b"y
\byo
\bou
\bu a
\bap
\bpp
\bpe
\bea
\bar
\br t
\bto
\bo h
\bha
\bav
\bve
\be a
\ba t
\btr
\bra
\bap
\bpd
\bdo
\boo
\bor
\br u
\bui
\bid
\bd s
\bsy
\bys
\bst
\bte
\bem
\bm"
\b"
550 This can have several causes. It might be because you are using a uid
551 or gid of 65535 or -1. This is a VERY bad idea, and is a big security
552 hole. Check carefully in your /etc/passwd file and make sure that no
553 user has uid 65535 or -1. Especially check the "nobody" user, as many
554 broken systems are shipped with nobody setup with a uid of 65535.
556 It might also mean that your OS has a trapdoor uid/gid system :-)
558 This means that once a process changes effective uid from root to
559 another user it can't go back to root. Unfortunately Samba relies on
560 being able to change effective uid from root to non-root and back
561 again to implement its security policy. If your OS has a trapdoor uid
562 system this won't work, and several things in Samba may break. Less
563 things will break if you use user or server level security instead of
564 the default share level security, but you may still strike problems.
566 The problems don't give rise to any security holes, so don't panic,
567 but it does mean some of Samba's capabilities will be unavailable. In
568 particular you will not be able to connect to the Samba server as two
569 different uids at once. This may happen if you try to print as a
570 "guest" while accessing a share as a normal user. It may also affect
571 your ability to list the available shares as this is normally done as
574 Complain to your OS vendor and ask them to fix their system.
576 Note: the reason why 65535 is a VERY bad choice of uid and gid is that
577 it casts to -1 as a uid, and the setreuid() system call ignores (with
578 no error) uid changes to -1. This means any daemon attempting to run
579 as uid 65535 will actually run as root. This is not good!
582 3
\b3.
\b. C
\bCo
\bom
\bmm
\bmo
\bon
\bn c
\bcl
\bli
\bie
\ben
\bnt
\bt q
\bqu
\bue
\bes
\bst
\bti
\bio
\bon
\bns
\bs
587 3
\b3.
\b.1
\b1.
\b. A
\bAr
\bre
\be a
\ban
\bny
\by M
\bMa
\bac
\bci
\bin
\bnt
\bto
\bos
\bsh
\bh c
\bcl
\bli
\bie
\ben
\bnt
\bts
\bs f
\bfo
\bor
\br S
\bSa
\bam
\bmb
\bba
\ba
591 lkcl - update 09mar97 - the answer is "Yes!". Thursby now have a CIFS
592 Client / Server - see <h
\bht
\btt
\btp
\bp:
\b:/
\b//
\b/w
\bww
\bww
\bw.
\b.t
\bth
\bhu
\bur
\brs
\bsb
\bby
\by.
\b.c
\bco
\bom
\bm/
\b/>. They test it
593 against Windows 95, Windows NT and samba for compatibility issues. At
594 present, DAVE is at version 1.0.0. DAVE version 1.0.1 is in beta, and
595 will be released in April 97 (the speed of finder copies has been
596 greatly enhanced, and there are bug-fixes included).
598 Alternatives - There are two free implementations of AppleTalk for
599 several kinds of UNIX machnes, and several more commercial ones.
600 These products allow you to run file services and print services
601 natively to Macintosh users, with no additional support required on
602 the Macintosh. The two free omplementations are Netatalk,
603 <h
\bht
\btt
\btp
\bp:
\b:/
\b//
\b/w
\bww
\bww
\bw.
\b.u
\bum
\bmi
\bic
\bch
\bh.
\b.e
\bed
\bdu
\bu/
\b/~
\b~r
\brs
\bsu
\bug
\bg/
\b/n
\bne
\bet
\bta
\bat
\bta
\bal
\blk
\bk/
\b/>, and CAP,
604 <h
\bht
\btt
\btp
\bp:
\b:/
\b//
\b/w
\bww
\bww
\bw.
\b.c
\bcs
\bs.
\b.m
\bmu
\bu.
\b.o
\boz
\bz.
\b.a
\bau
\bu/
\b/a
\bap
\bpp
\bpl
\ble
\bet
\bta
\bal
\blk
\bk/
\b/a
\bat
\bta
\bal
\blk
\bk.
\b.h
\bht
\btm
\bml
\bl>. What Samba offers MS
605 Windows users, these packages offer to Macs. For more info on these
606 packages, Samba, and Linux (and other UNIX-based systems) see
607 <h
\bht
\btt
\btp
\bp:
\b:/
\b//
\b/w
\bww
\bww
\bw.
\b.e
\bea
\bat
\bts
\bs.
\b.c
\bco
\bom
\bm/
\b/l
\bli
\bin
\bnu
\bux
\bx_
\b_m
\bma
\bac
\bc_
\b_w
\bwi
\bin
\bn.
\b.h
\bht
\btm
\bml
\bl>
610 3
\b3.
\b.2
\b2.
\b. S
\bSe
\bes
\bss
\bsi
\bio
\bon
\bn r
\bre
\beq
\bqu
\bue
\bes
\bst
\bt f
\bfa
\bai
\bil
\ble
\bed
\bd (
\b(1
\b13
\b31
\b1,
\b,1
\b13
\b30
\b0)
\b)"
\b" e
\ber
\brr
\bro
\bor
\br
614 The following answer is provided by John E. Miller:
616 I'll assume that you're able to ping back and forth between the
617 machines by IP address and name, and that you're using some security
618 model where you're confident that you've got user IDs and passwords
619 right. The logging options (-d3 or greater) can help a lot with that.
620 DNS and WINS configuration can also impact connectivity as well.
622 Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network
623 configuration (I'm too much of an NT bigot to know where it's located
624 in the Win95 setup, but I'll have to learn someday since I teach for a
625 Microsoft Solution Provider Authorized Tech Education Center - what an
626 acronym...) Note: It's under Control Panel | Network | TCP/IP | WINS
627 Configuration there's a little text entry field called something like
629 This field essentially creates 'invisible' sub-workgroups on the same
630 wire. Boxes can only see other boxes whose Scope IDs are set to the
631 exact same value - it's sometimes used by OEMs to configure their
632 boxes to browse only other boxes from the same vendor and, in most
633 environments, this field should be left blank. If you, in fact, have
634 something in this box that EXACT value (case-sensitive!) needs to be
635 provided to smbclient and nmbd as the -i (lowercase) parameter. So, if
636 your Scope ID is configured as the string 'SomeStr' in Win95 then
637 you'd have to use smbclient -iSomeStr otherparms in connecting to it.
640 3
\b3.
\b.3
\b3.
\b. H
\bHo
\bow
\bw d
\bdo
\bo I
\bI s
\bsy
\byn
\bnc
\bch
\bhr
\bro
\bon
\bni
\bis
\bse
\be m
\bmy
\by P
\bPC
\bC'
\b's
\bs c
\bcl
\blo
\boc
\bck
\bk w
\bwi
\bit
\bth
\bh m
\bmy
\by S
\bSa
\bam
\bmb
\bba
\ba s
\bse
\ber
\brv
\bve
\ber
\br?
\b?
643 To syncronize your PC's clock with your Samba server:
646 · Copy timesync.pif to your windows directory
648 · timesync.pif can be found at:
649 <h
\bht
\btt
\btp
\bp:
\b:/
\b//
\b/s
\bsa
\bam
\bmb
\bba
\ba.
\b.c
\bca
\ban
\bnb
\bbe
\ber
\brr
\bra
\ba.
\b.e
\bed
\bdu
\bu.
\b.a
\bau
\bu/
\b/p
\bpu
\bub
\bb/
\b/s
\bsa
\bam
\bmb
\bba
\ba/
\b/b
\bbi
\bin
\bna
\bar
\bri
\bie
\bes
\bs/
\b/m
\bmi
\bis
\bsc
\bce
\bel
\bll
\bla
\ban
\bne
\beo
\bou
\bus
\bs/
\b/t
\bti
\bim
\bme
\bes
\bsy
\byn
\bnc
\bc.
\b.p
\bpi
\bif
\bf>
651 · Add timesync.pif to your 'Start Up' group/folder
653 · Open the properties dialog box for the program/icon
655 · Make sure the 'Run Minimized' option is set in program 'Properties'
657 · Change the command line section that reads \sambahost to reflect
658 the name of your server.
661 · Close the properties dialog box by choosing 'OK'
663 Each time you start your computer (or login for Win95) your PC will
664 synchronize it's clock with your Samba server.
666 Alternativley, if you clients support Domain Logons, you can setup
667 Domain Logons with Samba - see: BROWSING.txt
668 <f
\bft
\btp
\bp:
\b:/
\b//
\b/s
\bsa
\bam
\bmb
\bba
\ba.
\b.a
\ban
\bnu
\bu.
\b.e
\bed
\bdu
\bu.
\b.a
\bau
\bu/
\b/p
\bpu
\bub
\bb/
\b/s
\bsa
\bam
\bmb
\bba
\ba/
\b/d
\bdo
\boc
\bcs
\bs/
\b/B
\bBR
\bRO
\bOW
\bWS
\bSI
\bIN
\bNG
\bG.
\b.t
\btx
\bxt
\bt> *** for more
674 NET TIME \\%L /SET /YES
679 as one of the lines in the logon script.
681 3
\b3.
\b.4
\b4.
\b. P
\bPr
\bro
\bob
\bbl
\ble
\bem
\bms
\bs w
\bwi
\bit
\bth
\bh W
\bWi
\bin
\bnD
\bDD
\bD,
\b, N
\bNT
\bTr
\bri
\big
\bgu
\bue
\be,
\b, W
\bWi
\bin
\bnC
\bCe
\ben
\bnt
\bte
\ber
\brP
\bPr
\bro
\bo e
\bet
\btc
\bc
684 All of the above programs are applications that sit on an NT box and
685 allow multiple users to access the NT GUI applications from remote
686 workstations (often over X).
688 What has this got to do with Samba? The problem comes when these users
689 use filemanager to mount shares from a Samba server. The most common
690 symptom is that the first user to connect get correct file permissions
691 and has a nice day, but subsequent connections get logged in as the
692 same user as the first person to login. They find that they cannot
693 access files in their own home directory, but that they can access
694 files in the first users home directory (maybe not such a nice day
697 Why does this happen? The above products all share a common heritage
698 (and code base I believe). They all open just a single TCP based SMB
699 connection to the Samba server, and requests from all users are piped
700 over this connection. This is unfortunate, but not fatal.
702 It means that if you run your Samba server in share level security
703 (the default) then things will definately break as described above.
704 The share level SMB security model has no provision for multiple user
705 IDs on the one SMB connection. See security_level.txt in the docs for
706 more info on share/user/server level security.
708 If you run in user or server level security then you have a chance,
709 but only if you have a recent version of Samba (at least 1.9.15p6). In
710 older versions bugs in Samba meant you still would have had problems.
712 If you have a trapdoor uid system in your OS then it will never work
713 properly. Samba needs to be able to switch uids on the connection and
714 it can't if your OS has a trapdoor uid system. You'll know this
715 because Samba will note it in your logs.
717 Also note that you should not use the magic "homes" share name with
718 products like these, as otherwise all users will end up with the same
719 home directory. Use \serversername instead.
722 3
\b3.
\b.5
\b5.
\b. P
\bPr
\bro
\bob
\bbl
\ble
\bem
\bm w
\bwi
\bit
\bth
\bh p
\bpr
\bri
\bin
\bnt
\bte
\ber
\brs
\bs u
\bun
\bnd
\bde
\ber
\br N
\bNT
\bT
727 This info from Stefan Hergeth hergeth@f7axp1.informatik.fh-muenchen.de
730 A network-printer (with ethernetcard) is connected to the NT-Clients
731 via our UNIX-Fileserver (SAMBA-Server), like the configuration told by
732 Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
734 1. If a user has choosen this printer as the default printer in his
735 NT-Session and this printer is not connected to the network (e.g.
736 switched off) than this user has a problem with the SAMBA-
737 connection of his filesystems. It's very slow.
739 2. If the printer is connected to the network everything works fine.
741 3. When the smbd ist started with debug level 3, you can see that the
742 NT spooling system try to connect to the printer many times. If the
743 printer ist not connected to the network this request fails and the
744 NT spooler is wasting a lot of time to connect to the printer
745 service. This seems to be the reason for the slow network
748 4. Maybe it's possible to change this behaviour by setting different
749 printer properties in the Print-Manager-Menu of NT, but i didn't
753 3
\b3.
\b.6
\b6.
\b. W
\bWh
\bhy
\by a
\bar
\bre
\be m
\bmy
\by f
\bfi
\bil
\ble
\be'
\b's
\bs t
\bti
\bim
\bme
\bes
\bst
\bta
\bam
\bmp
\bps
\bs o
\bof
\bff
\bf b
\bby
\by a
\ban
\bn h
\bho
\bou
\bur
\br,
\b, o
\bor
\br b
\bby
\by a
\ba f
\bfe
\bew
\bw h
\bho
\bou
\bur
\brs
\bs?
\b?
756 This is from Paul Eggert eggert@twinsun.com.
758 Most likely it's a problem with your time zone settings.
760 Internally, Samba maintains time in traditional Unix format, namely,
761 the number of seconds since 1970-01-01 00:00:00 Universal Time (or
762 ``GMT''), not counting leap seconds.
764 On the server side, Samba uses the Unix TZ variable to convert
765 internal timestamps to and from local time. So on the server side,
766 there are two things to get right.
768 1. The Unix system clock must have the correct Universal time. Use
769 the shell command "sh -c 'TZ=UTC0 date'" to check this.
771 2. The TZ environment variable must be set on the server before Samba
772 is invoked. The details of this depend on the server OS, but
773 typically you must edit a file whose name is /etc/TIMEZONE or
774 /etc/default/init, or run the command `zic -l'.
776 3. TZ must have the correct value.
778 a. If possible, use geographical time zone settings (e.g.
779 TZ='America/Los_Angeles' or perhaps TZ=':US/Pacific'). These
780 are supported by most popular Unix OSes, are easier to get
781 right, and are more accurate for historical timestamps. If your
782 operating system has out-of-date tables, you should be able to
783 update them from the public domain time zone tables at
784 <f
\bft
\btp
\bp:
\b:/
\b//
\b/e
\bel
\bls
\bsi
\bie
\be.
\b.n
\bnc
\bci
\bi.
\b.n
\bni
\bih
\bh.
\b.g
\bgo
\bov
\bv/
\b/p
\bpu
\bub
\bb/
\b/>.
786 b. If your system does not support geographical timezone settings,
787 you must use a Posix-style TZ strings, e.g.
788 TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. Posix TZ
789 strings can take the following form (with optional items in
793 StdOffset[Dst[Offset],Date/Time,Date/Time]
798 · `Std' is the standard time designation (e.g. `PST').
800 · `Offset' is the number of hours behind UTC (e.g. `8'). Prepend
801 a `-' if you are ahead of UTC, and append `:30' if you are at a
802 half-hour offset. Omit all the remaining items if you do not
803 use daylight-saving time.
805 · `Dst' is the daylight-saving time designation (e.g. `PDT').
807 The optional second `Offset' is the number of hours that
808 daylight-saving time is behind UTC. The default is 1 hour ahead
811 · `Date/Time,Date/Time' specify when daylight-saving time starts
812 and ends. The format for a date is `Mm.n.d', which specifies
813 the dth day (0 is Sunday) of the nth week of the mth month,
814 where week 5 means the last such day in the month. The format
815 for a time is hh:mm[:ss], using a 24-hour clock.
817 Other Posix string formats are allowed but you don't want to
820 On the client side, you must make sure that your client's clock and
821 time zone is also set appropriately. [I don't know how to do
822 this.] Samba traditionally has had many problems dealing with time
823 zones, due to the bizarre ways that Microsoft network protocols
824 handle time zones. A common symptom is for file timestamps to be
825 off by an hour. To work around the problem, try disconnecting from
826 your Samba server and then reconnecting to it; or upgrade your
827 Samba server to 1.9.16alpha10 or later.
830 3
\b3.
\b.7
\b7.
\b. H
\bHo
\bow
\bw d
\bdo
\bo I
\bI s
\bse
\bet
\bt t
\bth
\bhe
\be p
\bpr
\bri
\bin
\bnt
\bte
\ber
\br d
\bdr
\bri
\biv
\bve
\ber
\br n
\bna
\bam
\bme
\be c
\bco
\bor
\brr
\bre
\bec
\bct
\btl
\bly
\by?
\b?
833 Question: On NT, I opened "Printer Manager" and "Connect to Printer".
835 in the box of printer. I got the following error message:
838 You do not have sufficient access to your machine
839 to connect to the selected printer, since a driver
840 needs to be installed locally.
847 In the more recent versions of Samba you can now set the "printer
848 driver" in smb.conf. This tells the client what driver to use. For
852 printer driver = HP LaserJet 4L
857 and NT knows to use the right driver. You have to get this string
859 To find the exact string to use, you need to get to the dialog box in
860 your client where you select which printer driver to install. The
861 correct strings for all the different printers are shown in a listbox
864 You could also try setting the driver to NULL like this:
867 printer driver = NULL
872 this is effectively what older versions of Samba did, so if that
873 worked for you then give it a go. If this does work then let me know
874 and I'll make it the default. Currently the default is a 0 length
878 4
\b4.
\b. S
\bSp
\bpe
\bec
\bci
\bif
\bfi
\bic
\bc c
\bcl
\bli
\bie
\ben
\bnt
\bt a
\bap
\bpp
\bpl
\bli
\bic
\bca
\bat
\bti
\bio
\bon
\bn p
\bpr
\bro
\bob
\bbl
\ble
\bem
\bms
\bs
883 4
\b4.
\b.1
\b1.
\b. M
\bMS
\bS O
\bOf
\bff
\bfi
\bic
\bce
\be S
\bSe
\bet
\btu
\bup
\bp r
\bre
\bep
\bpo
\bor
\brt
\bts
\bs "
\b"C
\bCa
\ban
\bnn
\bno
\bot
\bt c
\bch
\bha
\ban
\bng
\bge
\be p
\bpr
\bro
\bop
\bpe
\ber
\brt
\bti
\bie
\bes
\bs o
\bof
\bf "
\b"M
\bMS
\bSO
\bOF
\bF
\b
884 F
\bFI
\bIC
\bCE
\bEU
\bUP
\bP.
\b.I
\bIN
\bNI
\bI"
\b"
888 When installing MS Office on a Samba drive for which you have admin
889 user permissions, ie. admin users = username, you will find the setup
890 program unable to complete the installation.
892 To get around this problem, do the installation without admin user
893 permissions The problem is that MS Office Setup checks that a file is
894 rdonly by trying to open it for writing.
896 Admin users can always open a file for writing, as they run as root.
897 You just have to install as a non-admin user and then use "chown -R"
901 5
\b5.
\b. M
\bMi
\bis
\bsc
\bce
\bel
\bll
\bla
\ban
\bne
\beo
\bou
\bus
\bs