Filled in from current text faq
v 0.7 1 June 1997 Paul
Replicated changes in txt faq to sgml faq
+ 9 June 1997 Paul
+ Lots of changes, added doco list, updated compatible systems list
+ added NT SP3 entry, added Year 2000 entry, Getting ready for 1.9.17
-->
<article>
<author>Paul Blackman, <tt>ictinus@lake.canberra.edu.au</tt>
-<date>, v 0.7
+<date>v 0.7, June '97
<abstract> This is the Frequently Asked Questions (FAQ) document for
Samba, the free and very popular SMB server product. An SMB server
details
<sect1> What is Samba? <p> <label id="introduction">
-
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
Message Block) protocol. Initially written for Unix, Samba now also
The components of the suite are (in summary):
<itemize>
-
-<item> smbd, the SMB server. This handles actual connections from
-clients, doing all the file, permission and username work
-<item>nmbd, the Netbios name server, which helps clients locate
-servers, doing the browsing work and managing domains as this
-capability is being built into Samba
-<item>smbclient, the Unix-hosted client program
-<item>smbrun, a little 'glue' program to help the server run external
-programs
-<item>testprns, a program to test server access to printers
-<item>testparms, a program to test the Samba configuration file for
-correctness
-<item>smb.conf, the Samba configuration file
-<item> smbprint, a sample script to allow a Unix host to use smbclient
-to print to an SMB server
-<item> documentation! DON'T neglect to read it - you will save a great
-deal of time!
+<item><bf>smbd</bf>, the SMB server. This handles actual connections from clients, doing all the file, permission and username work
+<item><bf>nmbd</bf>, the Netbios name server, which helps clients locate servers, doing the browsing work and managing domains as this capability is being built into Samba
+<item><bf>smbclient</bf>, the Unix-hosted client program
+<item><bf>smbrun</bf>, a little 'glue' program to help the server run external programs
+<item><bf>testprns</bf>, a program to test server access to printers
+<item><bf>testparms</bf>, a program to test the Samba configuration file for correctness
+<item><bf>smb.conf</bf>, the Samba configuration file
+<item><bf>smbprint</bf>, a sample script to allow a Unix host to use smbclient to print to an SMB server
+<item><bf>Documentation!</bf> DON'T neglect to read it - you will save a great deal of time!
</itemize>
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.
-<sect1> What is the current version of Samba? <p> <label id="current_version">
-
-At time of writing, the current version was 1.9.16. If you want to be
-sure check the bottom of the change-log file. <url
-url="ftp://samba.anu.edu.au/pub/samba/alpha/change-log">
+<sect1> What is the current version of Samba? <p><label id="current_version">
+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. <url url="ftp://samba.anu.edu.au/pub/samba/alpha/change-log">
For more information see <ref id="version_nums" name="What do the
version numbers mean?">
<sect1> Where can I get it? <p> <label id="where">
-
The Samba suite is available via anonymous ftp from
samba.anu.edu.au. The latest and greatest versions of the suite are in
the directory:
do contain Samba binaries for that platform.
<sect1> What do the version numbers mean? <p> <label id="version_nums">
-
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
to do some debugging. Many, many people just get the latest
How the scheme works:
<enum>
-<item>when major changes are made the version number is increased. For
+<item>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.)
-<item>just after major changes are made the software is considered
+<item>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.
-<item>when Andrew thinks that the alphas have stabilised to the point
+<item>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.
-<item>inevitably bugs are found in the "stable" releases and minor patch
+<item>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.
</enum>
So the progression goes:
<verb>
- 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)
</verb>
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
version.
<sect1> What platforms are supported? <p> <label id="platforms">
-
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:
<itemize>
-<item> SunOS
-<item> Linux with shadow passwords
-<item> Linux without shadow passwords
-<item> SOLARIS
-<item> SOLARIS 2.2 and above (aka SunOS 5)
-<item> SVR4
-<item> ULTRIX
-<item> OSF1 (alpha only)
-<item> OSF1 with NIS and Fast Crypt (alpha only)
-<item> OSF1 V2.0 Enhanced Security (alpha only)
+<item> A/UX 3.0
<item> AIX
-<item> BSDI
-<item> NetBSD
-<item> NetBSD 1.0
-<item> SEQUENT
-<item> HP-UX
-<item> SGI
-<item> SGI IRIX 4.x.x
-<item> SGI IRIX 5.x.x
+<item> Altos Series 386/1000
+<item> Amiga
+<item> Apollo Domain/OS sr10.3
+<item> BSDI
+<item> B.O.S. (Bull Operating System)
+<item> Cray, Unicos 8.0
+<item> Convex
+<item> DGUX.
+<item> DNIX.
<item> FreeBSD
-<item> NeXT 3.2 and above
-<item> NeXT OS 2.x
-<item> NeXT OS 3.0
-<item> ISC SVR3V4 (POSIX mode)
-<item> ISC SVR3V4 (iBCS2 mode)
-<item> A/UX 3.0
-<item> SCO with shadow passwords.
-<item> SCO with shadow passwords, without YP.
-<item> SCO with TCB passwords
-<item> SCO 3.2v2 (ODT 1.1) with TCP passwords
-<item> intergraph
-<item> DGUX
-<item> Apollo Domain/OS sr10.3 (BSD4.3)
+<item> HP-UX
+<item> Intergraph.
+<item> Linux with/without shadow passwords and quota
+<item> LYNX 2.3.0
+<item> MachTen (a unix like system for Macintoshes)
+<item> Motorola 88xxx/9xx range of machines
+<item> NetBSD
+<item> NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).
+<item> OS/2 using EMX 0.9b
+<item> OSF1
+<item> QNX 4.22
+<item> RiscIX.
+<item> RISCOs 5.0B
+<item> SEQUENT.
+<item> SCO (including: 3.2v2, European dist., OpenServer 5)
+<item> SGI.
+<item> SMP_DC.OSx v1.1-94c079 on Pyramid S series
+<item> SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
+<item> SUNOS 4
+<item> SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
+<item> Sunsoft ISC SVR3V4
+<item> SVR4
+<item> System V with some berkely extensions (Motorola 88k R32V3.2).
+<item> ULTRIX.
+<item> UNIXWARE
+<item> UXP/DS
</itemize>
<sect1> How can I find out more about Samba? <p> <label id="more">
+There are a number of places to look for more information on Samba, including:
+<itemize>
+<item>Two mailing lists devoted to discussion of Samba-related matters.
+<item>The newsgroup, comp.protocols.smb, which has a great deal of discussion on Samba.
+<item>The WWW site 'SAMBA Web Pages' at <url url="http://samba.canberra.edu.au/pub/samba/samba.html"> includes:
+ <itemize>
+ <item>Links to man pages and documentation, including this FAQ
+ <item>A comprehensive survey of Samba users.
+ <item>A searchable hypertext archive of the Samba mailing list.
+ <item>Links to Samba source code, binaries, and mirrors of both.
+ </itemize>
+<item>The long list of topic documentation. These files can be found in the 'docs' directory of the Samba source, or at <url url="ftp://samba.anu.edu.au/pub/samba/docs/">
+ <itemize>
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Application_Serving.txt" name="Application_Serving.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/BROWSING.txt" name="BROWSING.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/BUGS.txt" name="BUGS.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/DIAGNOSIS.txt" name="DIAGNOSIS.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/DNIX.txt" name="DNIX.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/DOMAIN.txt" name="DOMAIN.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/DOMAIN_CONTROL.txt" name="CONTROL.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/ENCRYPTION.txt" name="ENCRYPTION.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Faxing.txt" name="Faxing.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/GOTCHAS.txt" name="GOTCHAS.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/HINTS.txt" name="HINTS.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/INSTALL.sambatar" name="INSTALL.sambatar">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/INSTALL.txt" name="INSTALL.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/MIRRORS" name="MIRRORS">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/NetBIOS.txt" name="NetBIOS.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/OS2.txt" name="OS2.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/PROJECTS" name="PROJECTS">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Passwords.txt" name="Passwords.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Printing.txt" name="Printing.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/README.DCEDFS" name="README.DCEDFS">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/README.OS2" name="README.OS2">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/README.jis" name="README.jis">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/README.sambatar" name="README.sambatar">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/SCO.txt" name="SCO.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/SMBTAR.notes" name="SMBTAR.notes">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Speed.txt" name="Speed.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Support.txt" name="Support.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/THANKS" name="THANKS">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Tracing.txt" name="Tracing.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/UNIX-SMB.txt" name="SMB.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/Warp.txt" name="Warp.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/WinNT.txt" name="WinNT.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/history" name="history">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/security_level.txt" name="level.txt">
+ <item><url url="ftp://samba.anu.edu.au/pub/samba/docs/wfw_slip.htm" name="slip.htm">
+ </itemize>
+</itemize>
-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 <url url="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.
-
+<sect1>How do I subscribe to the Samba Mailing Lists?<p><label id="mailinglist">
Send email to <htmlurl url="mailto:listproc@samba.anu.edu.au" name="listproc@samba.anu.edu.au">. Make sure the subject line is
blank, and include the following two lines in the body of the message:
-
<tscreen><verb>
subscribe samba Firstname Lastname
subscribe samba-announce Firstname Lastname
</verb></tscreen>
-
Obviously you should substitute YOUR first name for "Firstname" and
YOUR last name for "Lastname"! Try not to send any signature stuff, it
sometimes confuses the list processor.
If you stop being interested in Samba, please send another email to
<htmlurl url="mailto:listproc@samba.anu.edu.au" name="listproc@samba.anu.edu.au">. Make sure the subject line is blank, and
include the following two lines in the body of the message:
-
<tscreen><verb>
unsubscribe samba
unsubscribe samba-announce
</verb></tscreen>
-
The <bf>From:</bf> line in your message <em>MUST</em> be the same address you used when
you subscribed.
<sect1> Something's gone wrong - what should I do? <p> <label id="wrong">
-
<bf>[#] *** IMPORTANT! *** [#]</bf>
<p>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
<url url="ftp://samba.anu.edu.au/pub/samba/DIAGNOSIS.txt" name="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 <htmlurl url="mailto:samba-bugs@samba.anu.edu.au" name="samba-bugs@samba.anu.edu.au">, not Andrew Tridgell or any
-other individual and not the samba team mailing list.
+patches to <htmlurl url="mailto:samba-bugs@samba.anu.edu.au" name="samba-bugs@samba.anu.edu.au">. Do not send patches to Andrew Tridgell or any
+other individual, they may be lost if you do.
<sect1> Pizza supply details <p> <label id="pizza">
-
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
for payment, but he does appreciate it when people give him
flavours. It will probably get stuck in customs or torn apart by
hungry sniffer dogs but it will have been a noble gesture.
-<sect>Compiling and installing Samba on a Unix host<p>
-<label id="unix_install">
-
-<sect1>I can't see the Samba server in any browse lists!<p>
-<label id="no_browse">
+<sect>Compiling and installing Samba on a Unix host<p><label id="unix_install">
+<sect1>I can't see the Samba server in any browse lists!<p><label id="no_browse">
See <url url="ftp://samba.anu.edu.au/pub/samba/BROWSING.txt" name="BROWSING.txt">
for more information on browsing. Browsing.txt can also be found
in the docs directory of the Samba source.
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:
-
+<tscreen><verb>
net use M: \\mary\fred
-
+</verb></tscreen>
The details of how to do this and the specific syntax varies from
client to client - check your client's documentation.
<sect1>Some files that I KNOW are on the server doesn't show up when I view the files from my client! <p> <label id="missing_files">
-
+See the next question.
<sect1>Some files on the server show up with really wierd filenames when I view the files from my client! <p> <label id="strange_filenames">
-
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
DOS-compatible (ie, they are not legal DOS filenames for some reason).
details of how to change this - the parameter you need to set is
"mangled names = yes".
-<sect1>My client reports "cannot locate specified computer" or similar<p>
-<label id="cant_see_server">
-
+<sect1>My client reports "cannot locate specified computer" or similar<p><label id="cant_see_server">
This indicates one of three things: You supplied an incorrect server
name, the underlying TCP/IP layer is not working correctly, or the
name you specified cannot be resolved.
tests :-)
<sect1>My client reports "cannot locate specified share name" or similar<p> <label id="cant_see_share">
-
This message indicates that your client CAN locate the specified
server, which is a good start, but that it cannot find a service of
the name you gave.
<item> Some clients force service names into upper case.
</itemize>
-<sect1>My client reports "cannot find domain controller", "cannot log
-on to the network" or similar <p> <label id="cant_see_net">
-
+<sect1>My client reports "cannot find domain controller", "cannot log on to the network" or similar <p> <label id="cant_see_net">
Nothing is wrong - Samba does not implement the primary domain name
controller stuff for several reasons, including the fact that the
whole concept of a primary domain controller and "logging in to a
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!
+<htmlurl url="mailto:samba-bugs@anu.edu.au" name="samba-bugs@anu.edu.au"> !
Seeing this message should not affect your ability to mount redirected
disks and printers, which is really what all this is about.
setting the domain to STANDALONE at least gets rid of the message.
<sect1>Printing doesn't work :-(<p> <label id="no_printing">
-
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.,
use "/usr/bin/lpr" rather than just "lpr").
printing won't work. The print status is received by a different
mechanism.
-<sect1>My programs install on the server OK, but refuse to work properly<p>
-<label id="programs_wont_run">
-
+<sect1>My programs install on the server OK, but refuse to work properly<p><label id="programs_wont_run">
There are numerous possible reasons for this, but one MAJOR
possibility is that your software uses locking. Make sure you are
using Samba 1.6.11 or later. It may also be possible to work around
6. These should have all been solved. If not then please let Andrew
Tridgell know via email at <htmlurl url="mailto:samba-bugs@anu.edu.au" name="samba-bugs@anu.edu.au">.
-<sect1>My "server string" doesn't seem to be recognised<p>
-<label id="bad_server_string">
-
-my client reports the default setting, eg. "Samba 1.9.15p4", instead
+<sect1>My "server string" doesn't seem to be recognised<p><label id="bad_server_string">
+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.
-Current versions of Samba (1.9.16p11 +) have combined these options into
+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.
-<sect1>My client reports "This server is not configured to list shared
-resources" <p> <label id="cant_list_shares">
-
+<sect1>My client reports "This server is not configured to list shared resources" <p> <label id="cant_list_shares">
Your guest account is probably invalid for some reason. Samba uses the
guest account for browsing in smbd. Check that your guest account is
valid.
See also 'guest account' in smb.conf man page.
-<sect1>Log message "you appear to have a trapdoor uid system" <p>
-<label id="trapdoor_uid">
-
+<sect1>Log message "you appear to have a trapdoor uid system" <p><label id="trapdoor_uid">
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
hole. Check carefully in your /etc/passwd file and make sure that no
<sect>Common client questions<p> <label id="client_questions">
-<sect1>Are any Macintosh clients for Samba<p> <label id="mac_clients">
-
-lkcl - update 09mar97 - the answer is "Yes!". Thursby now have a
-CIFS Client / Server - see <url url="http://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
+<sect1>Are there any Macintosh clients for Samba?<p> <label id="mac_clients">
+Yes! Thursby now have a CIFS Client / Server called DAVE - see <url url="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).
Alternatives - There are two free implementations of AppleTalk for
see <url url="http://www.eats.com/linux_mac_win.html">
<sect1>"Session request failed (131,130)" error<p> <label id="sess_req_fail">
-
The following answer is provided by John E. Miller:
I'll assume that you're able to ping back and forth between the
you'd have to use smbclient -iSomeStr [otherparms] in connecting to
it.
-<sect1>How do I synchronise my PC's clock with my Samba server? <p>
-<label id="synchronise_clock">
-
+<sect1>How do I synchronise my PC's clock with my Samba server? <p><label id="synchronise_clock">
To syncronize your PC's clock with your Samba server:
-
<itemize>
<item> Copy timesync.pif to your windows directory
<item> timesync.pif can be found at:
<item> Add timesync.pif to your 'Start Up' group/folder
<item> Open the properties dialog box for the program/icon
<item> Make sure the 'Run Minimized' option is set in program 'Properties'
-<iteM> Change the command line section that reads \\sambahost to reflect the name of your server.
+<iteM> Change the command line section that reads [\\sambahost] to reflect the name of your server.
<item> Close the properties dialog box by choosing 'OK'
</itemize>
-
Each time you start your computer (or login for Win95) your PC will
synchronize it's clock with your Samba server.
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
+multiple user IDs on the one SMB connection. See <url url="ftp://samba.anu.edu.au/pub/samba/docs/security_level.txt" name="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,
Also note that you should not use the magic "homes" share name with
products like these, as otherwise all users will end up with the same
-home directory. Use \\server\username instead.
+home directory. Use [\\server\username] instead.
<sect1>Problem with printers under NT<p> <label id="nt_printers">
-
This info from Stefan Hergeth
hergeth@f7axp1.informatik.fh-muenchen.de may be useful:
printer properties in the Print-Manager-Menu of NT, but i didn't try it yet.
</enum>
-<sect1>Why are my file's timestamps off by an hour, or by a few hours?<p>
-<label id="dst_bugs">
-
+<sect1>Why are my file's timestamps off by an hour, or by a few hours?<p><label id="dst_bugs">
This is from Paul Eggert eggert@twinsun.com.
Most likely it's a problem with your time zone settings.
Posix TZ strings can take the following form (with optional
items in brackets):
<verb>
- StdOffset[Dst[Offset],Date/Time,Date/Time]
+ StdOffset[Dst[Offset],Date/Time,Date/Time]
</verb>
where:
<itemize>
and then reconnecting to it; or upgrade your Samba server to
1.9.16alpha10 or later.
-<sect1> How do I set the printer driver name correctly? <p>
-<label id="printer_driver_name">
-
+<sect1> How do I set the printer driver name correctly? <p><label id="printer_driver_name">
Question:
On NT, I opened "Printer Manager" and "Connect to Printer".
- Enter "\\ptdi270\ps1" in the box of printer. I got the
+ Enter ["\\ptdi270\ps1"] in the box of printer. I got the
following error message:
<tscreen><verb>
You do not have sufficient access to your machine
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:
<tscreen><verb>
printer driver = HP LaserJet 4L
</verb></tscreen>
-and NT knows to use the right driver. You have to get this string
+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
printer driver = NULL
</verb></tscreen>
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
+worked for you then give it a go. If this does work then let us know via <htmlurl url="mailto:samba-bugs@anu.edu.au" name="samba-bugs@anu.edu.au">,
+and we'll make it the default. Currently the default is a 0 length
string.
-<sect>Specific client application problems<p> <label id="client_problems">
+<sect1>I've applied NT 4.0 SP3, and now I can't access Samba shares, Why?<p><label id="NT_SP3_FIX">
+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 <bf>ONE</bf> of two things:
+<enum>
+<item> Set the Samba configuration option 'security = user' and implement all of the stuff detailed in <url url="ftp://samba.anu.edu.au/pub/samba/docs/ENCRYPTION.txt" name="ENCRYPTION.txt">.
+<item> Follow Microsoft's directions for setting your NT box to allow plain text passwords. see <url url="http://www.microsoft.com/kb/articles/q166/7/30.htm" name="Knowledge Base Article Q166730">
+</enum>
-<sect1>MS Office Setup reports "Cannot change properties of "\MSOFFICE\SETUP.INI"<p>
-<label id="cant_change_properties">
+<sect>Specific client application problems<p> <label id="client_problems">
+<sect1>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"<p> <label id="cant_change_properties">
When installing MS Office on a Samba drive for which you have admin
user permissions, ie. admin users = username, you will find the
setup program unable to complete the installation.
to fix the owner.
<sect>Miscellaneous<p> <label id="miscellaneous">
-
+<sect1>Is Samba Year 2000 compliant?<p><label id="Year2000Compliant">
+The CIFS protocol that Samba implements
+negotiates times in various formats, all of which
+are able to cope with dates beyond 2000.
</article>
git.samba.org / samba.git / blobdiff