Samba FAQ
- Paul Blackman, ictinus@lake.canberra.edu.au
- , v 0.5
+ Paul Blackman, ictinus@samba.org
+ v 0.8, June '97
This is the Frequently Asked Questions (FAQ) document for Samba, the
free and very popular SMB server product. An SMB server allows file
and printer connections from clients such as Windows, OS/2, Linux and
- others. Current to version 1.9.16. Please send any corrections to the
+ others. Current to version 1.9.17. Please send any corrections to the
author.
______________________________________________________________________
1.6. How can I find out more about Samba?
- 1.7. Something's gone wrong - what should I do?
+ 1.7. How do I subscribe to the Samba Mailing Lists?
- 1.8. Pizza supply details
+ 1.8. Something's gone wrong - what should I do?
+
+ 1.9. Pizza supply details
2. Compiling and installing Samba on a Unix host
3. Common client questions
- 3.1. Are any Macintosh clients for Samba
+ 3.1. Are there any Macintosh clients for Samba?
3.2. "Session request failed (131,130)" error
3.7. How do I set the printer driver name correctly?
+ 3.8. I've applied NT 4.0 SP3, and now I can't access Samba shares,
+ Why?
+
4. Specific client application problems
4.1. MS Office Setup reports "Cannot change properties of
- "MSOFFICEUP.INI"
+ 'MSOFFICEUP.INI'"
5. Miscellaneous
+
+ 5.1. Is Samba Year 2000 compliant?
______________________________________________________________________
- 1. General Information
+ 1\b1.\b. G\bGe\ben\bne\ber\bra\bal\bl I\bIn\bnf\bfo\bor\brm\bma\bat\bti\bio\bon\bn
+
+
All about Samba - what it is, how to get it, related sources of
information, how to understand the version numbering scheme, pizza
details
- 1.1. What is Samba?
+
+ 1\b1.\b.1\b1.\b. W\bWh\bha\bat\bt i\bis\bs S\bSa\bam\bmb\bba\ba?\b?
+
Samba is a suite of programs which work together to allow clients to
access to a server's filespace and printers via the SMB (Server
The components of the suite are (in summary):
- o smbd, the SMB server. This handles actual connections from clients,
+
+ +\bo s\bsm\bmb\bbd\bd, the SMB server. This handles actual connections from clients,
doing all the file, permission and username work
- o nmbd, the Netbios name server, which helps clients locate servers,
+ +\bo n\bnm\bmb\bbd\bd, the Netbios name server, which helps clients locate servers,
doing the browsing work and managing domains as this capability is
being built into Samba
- o smbclient, the Unix-hosted client program
- o smbrun, a little 'glue' program to help the server run external
+ +\bo s\bsm\bmb\bbc\bcl\bli\bie\ben\bnt\bt, the Unix-hosted client program
+
+ +\bo s\bsm\bmb\bbr\bru\bun\bn, a little 'glue' program to help the server run external
programs
- o testprns, a program to test server access to printers
+ +\bo t\bte\bes\bst\btp\bpr\brn\bns\bs, a program to test server access to printers
- o testparms, a program to test the Samba configuration file for
+ +\bo t\bte\bes\bst\btp\bpa\bar\brm\bms\bs, a program to test the Samba configuration file for
correctness
- o smb.conf, the Samba configuration file
+ +\bo s\bsm\bmb\bb.\b.c\bco\bon\bnf\bf, the Samba configuration file
- o smbprint, a sample script to allow a Unix host to use smbclient to
+ +\bo s\bsm\bmb\bbp\bpr\bri\bin\bnt\bt, a sample script to allow a Unix host to use smbclient to
print to an SMB server
- o documentation! DON'T neglect to read it - you will save a great
+ +\bo D\bDo\boc\bcu\bum\bme\ben\bnt\bta\bat\bti\bio\bon\bn!\b! DON'T neglect to read it - you will save a great
deal of time!
The suite is supplied with full source (of course!) and is GPLed.
versions incorporate much effort by many net.helpers. The man pages
and this FAQ were originally written by Karl Auer.
- 1.2. What is the current version of Samba?
- At time of writing, the current version was 1.9.16. If you want to be
+ 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?
+
+
+ At time of writing, the current version was 1.9.17. If you want to be
sure check the bottom of the change-log file.
- <ftp://samba.anu.edu.au/pub/samba/alpha/change-log>
+ <ftp://samba.org/pub/samba/alpha/change-log>
For more information see ``What do the version numbers mean?''
- 1.3. Where can I get it?
- The Samba suite is available via anonymous ftp from samba.anu.edu.au.
+ 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?
+
+
+ The Samba suite is available via anonymous ftp from samba.org.
The latest and greatest versions of the suite are in the directory:
/pub/samba/
other sites. Recent versions of some Linux distributions, for example,
do contain Samba binaries for that platform.
- 1.4. What do the version numbers mean?
+
+ 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?
+
It is not recommended that you run a version of Samba with the word
"alpha" in its name unless you know what you are doing and are willing
but don't install it on your departmental server. Samba is typically
very stable and safe, and this is mostly due to the policy of many
public releases.
-
How the scheme works:
- 1) when major changes are made the version number is increased. For
- example, the transition from 1.9.15 to 1.9.16. However, this version
- number will not appear immediately and people should continue to use
- 1.9.15 for production systems (see next point.)
+ 1. When major changes are made the version number is increased. For
+ example, the transition from 1.9.15 to 1.9.16. However, this
+ version number will not appear immediately and people should
+ continue to use 1.9.15 for production systems (see next point.)
+
+ 2. Just after major changes are made the software is considered
+ unstable, and a series of alpha releases are distributed, for
+ example 1.9.16alpha1. These are for testing by those who know what
+ they are doing. The "alpha" in the filename will hopefully scare
+ off those who are just looking for the latest version to install.
- 2) just after major changes are made the software is considered
- unstable, and a series of alpha releases are distributed, for example
- 1.9.16alpha1. These are for testing by those who know what they are
- doing. The "alpha" in the filename will hopefully scare off those who
- are just looking for the latest version to install.
+ 3. When Andrew thinks that the alphas have stabilised to the point
+ where he would recommend new users install it, he renames it to the
+ same version number without the alpha, for example 1.9.16.
- 3) when Andrew thinks that the alphas have stabilised to the point
- where he would recommend new users install it, he renames it to the
- same version number without the alpha, for example 1.9.16.
+ 4. Inevitably bugs are found in the "stable" releases and minor patch
+ levels are released which give us the pXX series, for example
+ 1.9.16p2.
- 4) inevitably bugs are found in the "stable" releases and minor patch
- levels are released which give us the pXX series, for example
- 1.9.16p2.
+ So the progression goes:
- So the progression goes:
+ 1.9.15p7 (production)
+ 1.9.15p8 (production)
+ 1.9.16alpha1 (test sites only)
+ :
+ 1.9.16alpha20 (test sites only)
+ 1.9.16 (production)
+ 1.9.16p1 (production)
- 1.9.15p7 (production) 1.9.15p8 (production) 1.9.16alpha1
- (test sites only) : 1.9.16alpha20 (test sites only) 1.9.16
- (production) 1.9.16p1 (production)
The above system means that whenever someone looks at the samba ftp
site they will be able to grab the highest numbered release without an
- alpha in the name and be sure of getting the current recommended
- version.
+ alpha in the name and be sure of getting the current recommended ver-
+ sion.
+
+
+ 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?
- 1.5. What platforms are supported?
Many different platforms have run Samba successfully. The platforms
most widely used and thus best tested are Linux and SunOS.
At time of writing, the Makefile claimed support for:
- * SunOS * Linux with shadow passwords * Linux without shadow passwords
- * SOLARIS * SOLARIS 2.2 and above (aka SunOS 5) * SVR4 * ULTRIX * OSF1
- (alpha only) * OSF1 with NIS and Fast Crypt (alpha only) * OSF1 V2.0
- Enhanced Security (alpha only) * AIX * BSDI * NetBSD * NetBSD 1.0 *
- SEQUENT * HP-UX * SGI * SGI IRIX 4.x.x * SGI IRIX 5.x.x * FreeBSD *
- NeXT 3.2 and above * NeXT OS 2.x * NeXT OS 3.0 * ISC SVR3V4 (POSIX
- mode) * ISC SVR3V4 (iBCS2 mode) * A/UX 3.0 * SCO with shadow
- passwords. * SCO with shadow passwords, without YP. * SCO with TCB
- passwords * SCO 3.2v2 (ODT 1.1) with TCP passwords * intergraph * DGUX
- * Apollo Domain/OS sr10.3 (BSD4.3)
-
- 1.6. How can I find out more about Samba?
-
- There are two mailing lists devoted to discussion of Samba-related
- matters. There is also the newsgroup, comp.protocols.smb, which has a
- great deal of discussion on Samba. There is also a WWW site 'SAMBA Web
- Pages' at http://samba.canberra.edu.au/pub/samba/samba.html, under
- which there is a comprehensive survey of Samba users. Another useful
- resource is the hypertext archive of the Samba mailing list.
-
- Send email to listproc@samba.anu.edu.au. Make sure the subject line is
+ +\bo A/UX 3.0
+
+ +\bo AIX
+
+ +\bo Altos Series 386/1000
+
+ +\bo Amiga
+
+ +\bo Apollo Domain/OS sr10.3
+
+ +\bo BSDI
+
+ +\bo B.O.S. (Bull Operating System)
+
+ +\bo Cray, Unicos 8.0
+
+ +\bo Convex
+
+ +\bo DGUX.
+
+ +\bo DNIX.
+
+ +\bo FreeBSD
+
+ +\bo HP-UX
+
+ +\bo Intergraph.
+
+ +\bo Linux with/without shadow passwords and quota
+
+ +\bo LYNX 2.3.0
+
+ +\bo MachTen (a unix like system for Macintoshes)
+
+ +\bo Motorola 88xxx/9xx range of machines
+
+ +\bo NetBSD
+
+ +\bo NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for
+ Mach).
+
+ +\bo OS/2 using EMX 0.9b
+
+ +\bo OSF1
+
+ +\bo QNX 4.22
+
+ +\bo RiscIX.
+
+ +\bo RISCOs 5.0B
+
+ +\bo SEQUENT.
+
+ +\bo SCO (including: 3.2v2, European dist., OpenServer 5)
+
+ +\bo SGI.
+
+ +\bo SMP_DC.OSx v1.1-94c079 on Pyramid S series
+
+ +\bo SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
+
+ +\bo SUNOS 4
+
+ +\bo SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
+
+ +\bo Sunsoft ISC SVR3V4
+
+ +\bo SVR4
+
+ +\bo System V with some berkely extensions (Motorola 88k R32V3.2).
+
+ +\bo ULTRIX.
+
+ +\bo UNIXWARE
+
+ +\bo UXP/DS
+
+
+ 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?
+
+
+ There are a number of places to look for more information on Samba,
+ including:
+
+ +\bo Two mailing lists devoted to discussion of Samba-related matters.
+
+ +\bo The newsgroup, comp.protocols.smb, which has a great deal of
+ discussion on Samba.
+
+ +\bo The WWW site 'SAMBA Web Pages' at <http://samba.edu.au/samba/>
+ includes:
+
+ +\bo Links to man pages and documentation, including this FAQ
+
+ +\bo A comprehensive survey of Samba users.
+
+ +\bo A searchable hypertext archive of the Samba mailing list.
+
+ +\bo Links to Samba source code, binaries, and mirrors of both.
+
+ +\bo The long list of topic documentation. These files can be found in
+ the 'docs' directory of the Samba source, or at
+ <ftp://samba.org/pub/samba/docs/>
+
+ +\bo Application_Serving.txt
+ <ftp://samba.org/pub/samba/docs/Application_Serving.txt>
+
+ +\bo BROWSING.txt <ftp://samba.org/pub/samba/docs/BROWSING.txt>
+
+ +\bo BUGS.txt <ftp://samba.org/pub/samba/docs/BUGS.txt>
+
+ +\bo DIAGNOSIS.txt <ftp://samba.org/pub/samba/docs/DIAGNOSIS.txt>
+
+ +\bo DNIX.txt <ftp://samba.org/pub/samba/docs/DNIX.txt>
+
+ +\bo DOMAIN.txt <ftp://samba.org/pub/samba/docs/DOMAIN.txt>
+
+ +\bo CONTROL.txt
+ <ftp://samba.org/pub/samba/docs/DOMAIN_CONTROL.txt>
+
+ +\bo ENCRYPTION.txt
+ <ftp://samba.org/pub/samba/docs/ENCRYPTION.txt>
+
+ +\bo Faxing.txt <ftp://samba.org/pub/samba/docs/Faxing.txt>
+
+ +\bo GOTCHAS.txt <ftp://samba.org/pub/samba/docs/GOTCHAS.txt>
+
+ +\bo HINTS.txt <ftp://samba.org/pub/samba/docs/HINTS.txt>
+
+ +\bo INSTALL.sambatar
+ <ftp://samba.org/pub/samba/docs/INSTALL.sambatar>
+
+ +\bo INSTALL.txt <ftp://samba.org/pub/samba/docs/INSTALL.txt>
+
+ +\bo MIRRORS <ftp://samba.org/pub/samba/docs/MIRRORS>
+
+ +\bo NetBIOS.txt <ftp://samba.org/pub/samba/docs/NetBIOS.txt>
+
+ +\bo OS2.txt <ftp://samba.org/pub/samba/docs/OS2.txt>
+
+ +\bo PROJECTS <ftp://samba.org/pub/samba/docs/PROJECTS>
+
+ +\bo Passwords.txt <ftp://samba.org/pub/samba/docs/Passwords.txt>
+
+ +\bo Printing.txt <ftp://samba.org/pub/samba/docs/Printing.txt>
+
+ +\bo README.DCEDFS <ftp://samba.org/pub/samba/docs/README.DCEDFS>
+
+ +\bo README.OS2 <ftp://samba.org/pub/samba/docs/README.OS2>
+
+ +\bo README.jis <ftp://samba.org/pub/samba/docs/README.jis>
+
+ +\bo README.sambatar
+ <ftp://samba.org/pub/samba/docs/README.sambatar>
+
+ +\bo SCO.txt <ftp://samba.org/pub/samba/docs/SCO.txt>
+
+ +\bo SMBTAR.notes <ftp://samba.org/pub/samba/docs/SMBTAR.notes>
+
+ +\bo Speed.txt <ftp://samba.org/pub/samba/docs/Speed.txt>
+
+ +\bo Support.txt <ftp://samba.org/pub/samba/docs/Support.txt>
+
+ +\bo THANKS <ftp://samba.org/pub/samba/docs/THANKS>
+
+ +\bo Tracing.txt <ftp://samba.org/pub/samba/docs/Tracing.txt>
+
+ +\bo SMB.txt <ftp://samba.org/pub/samba/docs/UNIX-SMB.txt>
+
+ +\bo Warp.txt <ftp://samba.org/pub/samba/docs/Warp.txt>
+
+ +\bo WinNT.txt <ftp://samba.org/pub/samba/docs/WinNT.txt>
+
+ +\bo history <ftp://samba.org/pub/samba/docs/history>
+
+ +\bo level.txt
+ <ftp://samba.org/pub/samba/docs/security_level.txt>
+
+ +\bo slip.htm <ftp://samba.org/pub/samba/docs/wfw_slip.htm>
+
+
+ 1\b1.\b.7\b7.\b. H\bHo\bow\bw d\bdo\bo I\bI s\bsu\bub\bbs\bsc\bcr\bri\bib\bbe\be t\bto\bo t\bth\bhe\be S\bSa\bam\bmb\bba\ba M\bMa\bai\bil\bli\bin\bng\bg L\bLi\bis\bst\bts\bs?\b?
+
+
+ Send email to listproc@samba.org. Make sure the subject line is
blank, and include the following two lines in the body of the message:
- subscribe samba Firstname Lastname subscribe samba-announce Firstname
- Lastname
+
+ subscribe samba Firstname Lastname
+ subscribe samba-announce Firstname Lastname
+
+
+
Obviously you should substitute YOUR first name for "Firstname" and
YOUR last name for "Lastname"! Try not to send any signature stuff, it
message to all subscribers.
If you stop being interested in Samba, please send another email to
- listproc@samba.anu.edu.au. Make sure the subject line is blank, and
+ listproc@samba.org. Make sure the subject line is blank, and
include the following two lines in the body of the message:
- unsubscribe samba unsubscribe samba-announce
- The From: line in your message MUST be the same address you used when
+ unsubscribe samba
+ unsubscribe samba-announce
+
+
+
+
+ The F\bFr\bro\bom\bm:\b: line in your message _\bM_\bU_\bS_\bT be the same address you used when
you subscribed.
- 1.7. Something's gone wrong - what should I do?
- # *** IMPORTANT! *** # DO NOT post messages on mailing lists or in
- newsgroups until you have carried out the first three steps given
- here!
+ 1\b1.\b.8\b8.\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?
+
+
+ #\b# *\b**\b**\b* I\bIM\bMP\bPO\bOR\bRT\bTA\bAN\bNT\bT!\b! *\b**\b**\b* #\b#
+
+ DO NOT post messages on mailing lists or in newsgroups until you have
+ carried out the first three steps given here!
Firstly, see if there are any likely looking entries in this FAQ! If
you have just installed Samba, have you run through the checklist in
- DIAGNOSIS.txt? It can save you a lot of time and effort.
+ DIAGNOSIS.txt <ftp://samba.org/pub/samba/DIAGNOSIS.txt>? It can
+ save you a lot of time and effort. DIAGNOSIS.txt can also be found in
+ the docs directory of the Samba distribution.
Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
topics that relate to what you are trying to do.
If you make changes to the source code, _please_ submit these patches
so that everyone else gets the benefit of your work. This is one of
the most important aspects to the maintainence of Samba. Send all
- patches to samba-bugs@samba.anu.edu.au, not Andrew Tridgell or any
- other individual and not the samba team mailing list.
+ patches to samba-bugs@samba.org. Do not send patches to Andrew
+ Tridgell or any other individual, they may be lost if you do.
+
+
+ 1\b1.\b.9\b9.\b. P\bPi\biz\bzz\bza\ba s\bsu\bup\bpp\bpl\bly\by d\bde\bet\bta\bai\bil\bls\bs
- 1.8. Pizza supply details
Those who have registered in the Samba survey as "Pizza Factory" will
already know this, but the rest may need some help. Andrew doesn't ask
useless but he can hang it on the wall next to the one he already has
from Germany :-)
+
Method 4: Air freight him a pizza with your favourite regional
flavours. It will probably get stuck in customs or torn apart by
hungry sniffer dogs but it will have been a noble gesture.
- 2. Compiling and installing Samba on a Unix host
- 2.1. I can't see the Samba server in any browse lists!
+ 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
+
+
- *** Until the FAQ can be updated, please check the file: ***
- ftp://samba.anu.edu.au/pub/samba/BROWSING.txt *** for more information
- on browsing.
+ 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!
+
+
+ See BROWSING.txt <ftp://samba.org/pub/samba/BROWSING.txt> for
+ more information on browsing. Browsing.txt can also be found in the
+ docs directory of the Samba source.
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:
- net use M: \maryed
+
+ net use M: \\mary\fred
+
+
+
The details of how to do this and the specific syntax varies from
client to client - check your client's documentation.
- 2.2. view the files from my client! Some files that I KNOW are on
- the server doesn't show up when I
- 2.3. I view the files from my client! Some files on the server show
- up with really wierd filenames when
+ 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
+ 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!
+
+
+ See the next question.
+
+ 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
+ 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!
+
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
details of how to change this - the parameter you need to set is
"mangled names = yes".
- 2.4. My client reports "cannot locate specified computer" or similar
+
+ 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
+
This indicates one of three things: You supplied an incorrect server
name, the underlying TCP/IP layer is not working correctly, or the
to somewhere on your network to see if TCP/IP is functioning OK. If it
is, the problem is most likely name resolution.
+
If your client has a facility to do so, hardcode a mapping between the
hosts IP and the name you want to use. For example, with Man Manager
or Windows for Workgroups you would put a suitable entry in the file
By the way, remember to REMOVE the hardcoded mapping before further
tests :-)
- 2.5. similar My client reports "cannot locate specified share name"
- or
+
+ 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-
+ l\bla\bar\br
+
This message indicates that your client CAN locate the specified
server, which is a good start, but that it cannot find a service of
exists and you specified it correctly (read your client's doco on how
to specify a service name correctly), read on:
- * 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.
- 2.6. on to the network" or similar My client reports "cannot find
- domain controller", "cannot log
+ +\bo Many clients cannot accept or use service names longer than eight
+ characters.
+
+ +\bo Many clients cannot accept or use service names containing spaces.
+
+ +\bo Some servers (not Samba though) are case sensitive with service
+ names.
+
+ +\bo Some clients force service names into upper case.
+
+
+ 2\b2.\b.6\b6.\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 f\bfi\bin\bnd\bd 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
+ 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
+
Nothing is wrong - Samba does not implement the primary domain name
controller stuff for several reasons, including the fact that the
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!
+ samba-bugs@samba.org !
Seeing this message should not affect your ability to mount redirected
disks and printers, which is really what all this is about.
For many clients (including Windows for Workgroups and Lan Manager),
setting the domain to STANDALONE at least gets rid of the message.
- 2.7. Printing doesn't work :-(
+
+
+
+
+ 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(
+
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.,
printing won't work. The print status is received by a different
mechanism.
- 2.8. My programs install on the server OK, but refuse to work prop-
- erly
+
+ 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-
+ e\ber\brl\bly\by
+
There are numerous possible reasons for this, but one MAJOR
possibility is that your software uses locking. Make sure you are
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.
+ Tridgell know via email at samba-bugs@samba.org.
- 2.9. My "server string" doesn't seem to be recognised
- my client reports the default setting, eg. "Samba 1.9.15p4", instead
- of what I have changed it to in the smb.conf file.
+ 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
+
+
+ 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.
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
+ what smbd puts out and -C affects what nmbd puts out.
+
+ 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.
+
+
+ 2\b2.\b.1\b10\b0.\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 l\bli\bis\bst\bt s\bsh\bha\bar\bre\bed\bd
+ r\bre\bes\bso\bou\bur\brc\bce\bes\bs"\b"
- 2.10. resources" My client reports "This server is not configured to
- list shared
Your guest account is probably invalid for some reason. Samba uses the
guest account for browsing in smbd. Check that your guest account is
See also 'guest account' in smb.conf man page.
- 2.11. Log message "you appear to have a trapdoor uid system"
+
+ 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"
+
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
no error) uid changes to -1. This means any daemon attempting to run
as uid 65535 will actually run as root. This is not good!
- 3. Common client questions
- 3.1. Are any Macintosh clients for Samba
+ 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
- In Rob Newberry's words (rob@eats.com, Sun, 4 Dec 1994):
- The answer is "No." Samba speaks SMB, the protocol used for Microsoft
- networks. The Macintosh has ALWAYS spoken Appletalk. Even with
- Microsoft "services for Macintosh", it has been a matter of making the
- server speak Appletalk. It is the same for Novell Netware and the
- Macintosh, although I believe Novell has (VERY LATE) released an
- extension for the Mac to let it speak IPX.
- In future Apple System Software, you may see support for other
- protocols, such as SMB -- Applet is working on a new networking
- architecture that will --> -- make it easier to support additional
- protocols. But it's not here yet.
- Now, the nice part is that if you want your Unix machine to speak
- Appletalk, there are several options. "Netatalk" and "CAP" are free,
- and available on the net. There are also several commercial options,
- such as "PacerShare" and "Helios" (I think). In any case, you'll have
- to look around for a server, not anything for the Mac.
+ 3\b3.\b.1\b1.\b. A\bAr\bre\be t\bth\bhe\ber\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?\b?
- Depending on you OS, some of these may not help you. I am currently
- coordinating the effort to get CAP working with Native Ethertalk under
- Linux, but we're not done yet.
- lkcl - update 09mar97 - the answer is "Yes!". Thursby now have a
- CIFS Client / Server - see www.thursby.com. They test it against
- Windows 95, Windows NT and samba for compatibility issues. At
- present, DAVE is at version 1.0.0. DAVE version 1.0.1 is in beta,
- and will be released in April 97 (the speed of finder copies has
+ Yes! Thursby now have a CIFS Client / Server called DAVE - see
+ <http://www.thursby.com/>. They test it against Windows 95, Windows
+ NT and samba for compatibility issues. At the time of writing, DAVE
+ was at version 1.0.1. The 1.0.0 to 1.0.1 update is available as a free
+ download from the Thursby web site (the speed of finder copies has
been greatly enhanced, and there are bug-fixes included).
- 3.2. Session request failed (131,130)" error
+ Alternatives - There are two free implementations of AppleTalk for
+ several kinds of UNIX machnes, and several more commercial ones.
+ These products allow you to run file services and print services
+ natively to Macintosh users, with no additional support required on
+ the Macintosh. The two free omplementations are Netatalk,
+ <http://www.umich.edu/~rsug/netatalk/>, and CAP,
+ <http://www.cs.mu.oz.au/appletalk/atalk.html>. What Samba offers MS
+ Windows users, these packages offer to Macs. For more info on these
+ packages, Samba, and Linux (and other UNIX-based systems) see
+ <http://www.eats.com/linux_mac_win.html>
+ 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
+
The following answer is provided by John E. Miller:
your Scope ID is configured as the string 'SomeStr' in Win95 then
you'd have to use smbclient -iSomeStr otherparms in connecting to it.
- 3.3. How do I synchronise my PC's clock with my Samba server?
+
+ 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?
+
To syncronize your PC's clock with your Samba server:
- * Copy timesync.pif to your windows directory * timesync.pif can be
- found at:
- http://samba.canberra.edu.au/pub/samba/binaries/miscellaneous/timesync.pif
- * Add timesync.pif to your 'Start Up' group/folder * Open the
- properties dialog box for the program/icon * Make sure the 'Run
- Minimized' option is set in program * Change the command line section
- that reads \sambahost to reflect the name of your server. * Close the
- properties dialog box by choosing 'OK'
+ +\bo Copy timesync.pif to your windows directory
+
+ +\bo timesync.pif can be found at:
+ <http://samba.org/samba/binaries/miscellaneous/timesync.pif>
+
+ +\bo Add timesync.pif to your 'Start Up' group/folder
+
+ +\bo Open the properties dialog box for the program/icon
+
+ +\bo Make sure the 'Run Minimized' option is set in program 'Properties'
+
+ +\bo Change the command line section that reads \sambahost to reflect
+ the name of your server.
+
+ +\bo Close the properties dialog box by choosing 'OK'
+
+ Each time you start your computer (or login for Win95) your PC will
+ synchronize its clock with your Samba server.
+
+ Alternativley, if you clients support Domain Logons, you can setup
+ Domain Logons with Samba - see: BROWSING.txt
+ <ftp://samba.org/pub/samba/docs/BROWSING.txt> *** for more
+ information.
+
+ Then add
+
+
+ NET TIME \\%L /SET /YES
- Each time you start your computer (or login for Win95) your PC will
- synchronize it's clock with your Samba server.
- Alternatively, you can set up domain logons - see:
- ftp://samba.anu.edu.au/pub/samba/BROWSING.txt *** for more information.
- Then, add NET TIME \\%L /SET /YES as one of the lines in the logon script.
- 3.4. Problems with WinDD, NTrigue, WinCenterPro etc
+ as one of the lines in the logon script.
+
+ 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
+
All of the above programs are applications that sit on an NT box and
allow multiple users to access the NT GUI applications from remote
It means that if you run your Samba server in share level security
(the default) then things will definately break as described above.
The share level SMB security model has no provision for multiple user
- IDs on the one SMB connection. See security_level.txt in the docs for
- more info on share/user/server level security.
+ IDs on the one SMB connection. See security_level.txt
+ <ftp://samba.org/pub/samba/docs/security_level.txt> in the docs
+ for more info on share/user/server level security.
If you run in user or server level security then you have a chance,
but only if you have a recent version of Samba (at least 1.9.15p6). In
products like these, as otherwise all users will end up with the same
home directory. Use \serversername instead.
- 3.5. Problem with printers under NT
+
+ 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
+
This info from Stefan Hergeth hergeth@f7axp1.informatik.fh-muenchen.de
may be useful:
via our UNIX-Fileserver (SAMBA-Server), like the configuration told by
Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
- 1.) If a user has choosen this printer as the default printer in his
- NT-Session and this printer is not connected to the network (e.g.
- switched off) than this user has a problem with the SAMBA- connection
- of his filesystems. It's very slow.
+ 1. If a user has choosen this printer as the default printer in his
+ NT-Session and this printer is not connected to the network (e.g.
+ switched off) than this user has a problem with the SAMBA-
+ connection of his filesystems. It's very slow.
- 2.) If the printer is connected to the network everything works fine.
+ 2. If the printer is connected to the network everything works fine.
- 3.) When the smbd ist started with debug level 3, you can see that the
- NT spooling system try to connect to the printer many times. If the
- printer ist not connected to the network this request fails and the NT
- spooler is wasting a lot of time to connect to the printer service.
- This seems to be the reason for the slow network connection.
+ 3. When the smbd ist started with debug level 3, you can see that the
+ NT spooling system try to connect to the printer many times. If the
+ printer ist not connected to the network this request fails and the
+ NT spooler is wasting a lot of time to connect to the printer
+ service. This seems to be the reason for the slow network
+ connection.
- 4.) Maybe it's possible to change this behaviour by setting different
- printer properties in the Print-Manager-Menu of NT, but i didn't try
- it yet.
+ 4. Maybe it's possible to change this behaviour by setting different
+ printer properties in the Print-Manager-Menu of NT, but i didn't
+ try it yet.
+
+
+ 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?
- 3.6. Why are my file's timestamps off by an hour, or by a few hours?
This is from Paul Eggert eggert@twinsun.com.
internal timestamps to and from local time. So on the server side,
there are two things to get right.
- 1. The Unix system clock must have the correct Universal time. Use
- the shell command "sh -c 'TZ=UTC0 date'" to check this.
+ 1. The Unix system clock must have the correct Universal time. Use
+ the shell command "sh -c 'TZ=UTC0 date'" to check this.
+
+ 2. 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'.
+
+ 3. TZ must have the correct value.
+
+ a. If possible, use geographical time zone settings (e.g.
+ TZ='America/Los_Angeles' or perhaps TZ=':US/Pacific'). These
+ are supported by most popular Unix OSes, are easier to get
+ right, and are more accurate for historical timestamps. If your
+ operating system has out-of-date tables, you should be able to
+ update them from the public domain time zone tables at
+ <ftp://elsie.nci.nih.gov/pub/>.
+
+ b. If your system does not support geographical timezone settings,
+ you must use a Posix-style TZ strings, e.g.
+ TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. Posix TZ
+ strings can take the following form (with optional items in
+ brackets):
+
+ StdOffset[Dst[Offset],Date/Time,Date/Time]
+
+
+ where:
+
+ +\bo `Std' is the standard time designation (e.g. `PST').
+
+ +\bo `Offset' is the number of hours behind UTC (e.g. `8'). Prepend
+ a `-' if you are ahead of UTC, and append `:30' if you are at a
+ half-hour offset. Omit all the remaining items if you do not
+ use daylight-saving time.
- 2. 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'.
+ +\bo `Dst' is the daylight-saving time designation (e.g. `PDT').
- 3. TZ must have the correct value.
+ The optional second `Offset' is the number of hours that
+ daylight-saving time is behind UTC. The default is 1 hour ahead
+ of standard time.
- 3a. If possible, use geographical time zone settings (e.g.
- TZ='America/Los_Angeles' or perhaps TZ=':US/Pacific'). These are
- supported by most popular Unix OSes, are easier to get right, and are
- more accurate for historical timestamps. If your operating system has
- out-of-date tables, you should be able to update them from the public
- domain time zone tables at URL:ftp://elsie.nci.nih.gov/pub/.
+ +\bo `Date/Time,Date/Time' specify when daylight-saving time starts
+ and ends. The format for a date is `Mm.n.d', which specifies
+ the dth day (0 is Sunday) of the nth week of the mth month,
+ where week 5 means the last such day in the month. The format
+ for a time is hh:mm[:ss], using a 24-hour clock.
- 3b. If your system does not support geographical time zone settings,
- you must use a Posix-style TZ strings, e.g.
- TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. Posix TZ strings
- can take the following form (with optional items in brackets):
+ Other Posix string formats are allowed but you don't want to
+ know about them.
- StdOffsetDst[Offset,Date/Time,Date/Time]
+ On the client side, you must make sure that your client's clock and
+ time zone is also set appropriately. [I don't know how to do
+ this.] Samba traditionally has had many problems dealing with time
+ zones, due to the bizarre ways that Microsoft network protocols
+ handle time zones. A common symptom is for file timestamps to be
+ off by an hour. To work around the problem, try disconnecting from
+ your Samba server and then reconnecting to it; or upgrade your
+ Samba server to 1.9.16alpha10 or later.
- where:
- `Std' is the standard time designation (e.g. `PST').
+ 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?
- `Offset' is the number of hours behind UTC (e.g. `8'). Prepend a `-'
- if you are ahead of UTC, and append `:30' if you are at a half-hour
- offset. Omit all the remaining items if you do not use daylight-
- saving time.
- `Dst' is the daylight-saving time designation (e.g. `PDT').
+ Question: On NT, I opened "Printer Manager" and "Connect to Printer".
+ Enter "\ptdi270s1"
+ in the box of printer. I got the following error message:
- The optional second `Offset' is the number of hours that daylight-
- saving time is behind UTC. The default is 1 hour ahead of standard
- time.
- `Date/Time,Date/Time' specify when daylight-saving time starts and
- ends. The format for a date is `Mm.n.d', which specifies the dth day
- (0 is Sunday) of the nth week of the mth month, where week 5 means the
- last such day in the month. The format for a time is hh:mm[:ss],
- using a 24-hour clock.
- Other Posix string formats are allowed but you don't want to know
- about them.
+ You do not have sufficient access to your machine
+ to connect to the selected printer, since a driver
+ needs to be installed locally.
- On the client side, you must make sure that your client's clock and
- time zone is also set appropriately. [I don't know how to do this.]
- Samba traditionally has had many problems dealing with time zones, due
- to the bizarre ways that Microsoft network protocols handle time
- zones. A common symptom is for file timestamps to be off by an hour.
- To work around the problem, try disconnecting from your Samba server
- and then reconnecting to it; or upgrade your Samba server to
- 1.9.16alpha10 or later.
- 3.7. How do I set the printer driver name correctly?
- Question: > On NT, I opened "Printer Manager" and "Connect to
- Printer". > Enter "\ptdi270s1"
- in the box of printer. I got the > following error message: > >
- You do not have sufficient access to your machine > to connect to
- the selected printer, since a driver > needs to be installed
- locally.
Answer:
In the more recent versions of Samba you can now set the "printer
driver" in smb.conf. This tells the client what driver to use. For
- example, I have:
+ example:
- printer driver = HP LaserJet 4L
- and NT knows to use the right driver. You have to get this string
- exactly right.
+ printer driver = HP LaserJet 4L
+
+
+
+
+ with this, NT knows to use the right driver. You have to get this
+ string exactly right.
To find the exact string to use, you need to get to the dialog box in
your client where you select which printer driver to install. The
You could also try setting the driver to NULL like this:
- printer driver = NULL
+
+ printer driver = NULL
+
+
+
this is effectively what older versions of Samba did, so if that
- worked for you then give it a go. If this does work then let me know
- and I'll make it the default. Currently the default is a 0 length
- string.
+ worked for you then give it a go. If this does work then let us know
+ via samba-bugs@samba.org, and we'll make it the default. Cur-
+ rently the default is a 0 length string.
+
+
+ 3\b3.\b.8\b8.\b. I\bI'\b'v\bve\be a\bap\bpp\bpl\bli\bie\bed\bd N\bNT\bT 4\b4.\b.0\b0 S\bSP\bP3\b3,\b, a\ban\bnd\bd n\bno\bow\bw I\bI c\bca\ban\bn'\b't\bt a\bac\bcc\bce\bes\bss\bs S\bSa\bam\bmb\bba\ba s\bsh\bha\bar\bre\bes\bs,\b,
+ W\bWh\bhy\by?\b?
+
+
+ As of SP3, Microsoft has decided that they will no longer default to
+ passing clear text passwords over the network. To enable access to
+ Samba shares from NT 4.0 SP3, you must do O\bON\bNE\bE of two things:
+
+ 1. Set the Samba configuration option 'security = user' and implement
+ all of the stuff detailed in ENCRYPTION.txt
+ <ftp://samba.org/pub/samba/docs/ENCRYPTION.txt>.
+
+ 2. Follow Microsoft's directions for setting your NT box to allow
+ plain text passwords. see Knowledge Base Article Q166730
+ <http://www.microsoft.com/kb/articles/q166/7/30.htm>
- 4. Specific client application problems
- 4.1. MS Office Setup reports "Cannot change properties of "MSOF-
- FICEUP.INI"
+ 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
+
+
+
+
+ 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-
+ F\bFI\bIC\bCE\bEU\bUP\bP.\b.I\bIN\bNI\bI'\b'"\b"
+
When installing MS Office on a Samba drive for which you have admin
user permissions, ie. admin users = username, you will find the setup
You just have to install as a non-admin user and then use "chown -R"
to fix the owner.
- 5. Miscellaneous
+
+ 5\b5.\b. M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs
+
+
+
+ 5\b5.\b.1\b1.\b. I\bIs\bs S\bSa\bam\bmb\bba\ba Y\bYe\bea\bar\br 2\b20\b00\b00\b0 c\bco\bom\bmp\bpl\bli\bia\ban\bnt\bt?\b?
+
+
+ The CIFS protocol that Samba implements negotiates times in various
+ formats, all of which are able to cope with dates beyond 2000.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
git.samba.org / jra / samba / .git / blobdiff